Service token option for IPv6
draft-herbert-ipv6-service-token-option-00

Document Type Active Internet-Draft (individual)
Last updated 2017-05-12
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT                                                T. Herbert
Intended Status: Standard                                     Quantonium
Expires: November 2017                                                  
                                                                        
                                                            May 12, 2017

                     Service token option for IPv6
               draft-herbert-ipv6-service-token-option-00

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.   

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

 

T. Herbert             Expires November 13, 2017                [Page 1]
INTERNET DRAFT    draft-herbert-ipv6-service-tokens-00      May 12, 2017

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1 Current solutions  . . . . . . . . . . . . . . . . . . . . .  3
     1.2 SPUD and PLUS solution . . . . . . . . . . . . . . . . . . .  3
     1.3 Emerging use cases . . . . . . . . . . . . . . . . . . . . .  4
   2  Architecture  . . . . . . . . . . . . . . . . . . . . . . . . .  5
     2.1 Example packet flow  . . . . . . . . . . . . . . . . . . . .  6
     2.2 Requirements . . . . . . . . . . . . . . . . . . . . . . . .  7
   3  Packet format . . . . . . . . . . . . . . . . . . . . . . . . .  7
     3.1 Option format  . . . . . . . . . . . . . . . . . . . . . . .  8
     3.2 Option types . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.3 Service token  . . . . . . . . . . . . . . . . . . . . . . .  9
   4  Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     4.1 Origin application operation . . . . . . . . . . . . . . . . 10
     4.2 Origin network processing  . . . . . . . . . . . . . . . . . 10
     4.3 Peer processing  . . . . . . . . . . . . . . . . . . . . . . 11
     4.4 Handling dropped extension headers . . . . . . . . . . . . . 11
       4.4.1 Mitigations for dropped extension headers  . . . . . . . 11
       4.4.2 Fallback for dropped extension headers . . . . . . . . . 11
   5  Implementation considerations . . . . . . . . . . . . . . . . . 12
     5.1 Origin applications  . . . . . . . . . . . . . . . . . . . . 12
     5.2 Reflection . . . . . . . . . . . . . . . . . . . . . . . . . 12
   6  Security Considerations . . . . . . . . . . . . . . . . . . . . 13
   7  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 13
   8  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     8.1  Normative References  . . . . . . . . . . . . . . . . . . . 14
     8.2  Informative References  . . . . . . . . . . . . . . . . . . 14
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14

 

T. Herbert             Expires November 13, 2017                [Page 2]
Show full document text