Service token option for IPv6
draft-herbert-ipv6-service-token-option-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tom Herbert | ||
| Last updated | 2017-11-13 (Latest revision 2017-05-12) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes the service token option in IPv6. The service token option expresses to the network the services that should be applied to a packet. The service token allows network infrastructure to map packets to a service class for processing in the network. The contents of service tokens are not globally defined, their meaning and semantics are defined for individual networks. Applications request service tokens from their network provider for the services they wish to be applied. The service tokens are sent in either Destination options or a Hop-By-Hop options IPv6.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)