Network Working Group                                        G. Tsirtsis
Internet-Draft                                               G. Giarreta
Intended status: Standards Track                                Qualcomm
Expires: January 30, May 13, 2010                                         H. Soliman
                                                    Elevate Technologies
                                                            N. Montavont
                                                                   IT/TB
                                                           July 29,
                                                        November 9, 2009

                    Binary

                  Traffic Selectors for FB
                    draft-ietf-mext-binary-ts-00.txt Flow Bindings
                    draft-ietf-mext-binary-ts-01.txt

Abstract

   This document defines binary formats for IPv4 and IPv6 traffic
   selectors to be used in conjuction with flow bindings for Mobile
   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/ietf/1id-abstracts.txt.

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

   This Internet-Draft will expire on January 30, May 13, 2010.

Copyright Notice

   Copyright (c) 2009 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 (http://trustee.ietf.org/license-info). document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

Abstract

   This  Code Components extracted from this document defines binary format for IPv4 must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and IPv6 traffic
   selectors to be used are provided without warranty as
   described in conjuction with flow bindings for Mobile
   IPv6. the BSD License.

Table of Contents

   1.  Requirements notation  . . . . . . . . . . . . . . . . . . . .  3
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Traffic Selector Sub-Options . . . . . . . . . . . . . . . . .  5
     3.1.  IPv4 binary traffic selector . . . . . . . . . . . . . . .  5
     3.2.  IPv6 binary traffic selector . . . . . . . . . . . . . . .  7  8
   4.  Flow Identification Status codes . . . . . . . . . . . . . . . 11
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   6. 14
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 13
   7. 15
   6.  Aknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 14
   8. 16
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     8.1. 17
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 15
     8.2. 17
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 15 17
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 18

1.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Introduction

   This document defines binary formats for IPv4 and IPv6 Traffic
   Selector sub-options as defined in [I-D.ietf-mext-flow-binding].

   The binary traffic selector sub-options defined here, allow efficient
   identification of flow(s) based on well known fields in IPv4, IPv6, IPv4
   [RFC0791], IPv6 [RFC2460], and transport layer headers. headers like TCP
   [RFC0793] and UDP [RFC0768].

3.  Traffic Selector Sub-Options

   [I-D.ietf-mext-flow-binding] defines the format for the traffic
   selector sub-option.

   The following values of the sub-option Type TS Format field, are reserved defined in this
   specification for binary traffic selectors selectors.

   TS Format:

      TBD IPv4 binary traffic selector

      TBD IPv6 binary traffic selector

3.1.  IPv4 binary traffic selector

   If the Type TS Format field of the traffic selector sub-option indicates
   "IPv4 binary traffic selector", then the traffic selector is
   formatted as
   follows: shown below.

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |A|B|C|D|E|F|G|H|I|K|L|  Resvd
       |Sub-opt Type   |  Sub-Opt Len  |   TS Format   |   Reserved    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |A|B|C|D|E|F|G|H|I|J|K|L|M|N|          Reserved                 |     (A)DS
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       | (B)Protocol                 (A)Start Source Address                       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                    (C)Source                 (B)End Source Address                         |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                 (D)Destination                 (C)Start Destination Address                  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |(E)S. PrefLeng |(F)D. PrefLeng
       |   (G)Source port - Low                 (D)End Destination Address                    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                          (E)Start SPI                         |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                          (F)End SPI                           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |   (H)Source   (G)Start Source port - High        |      (I)Dst   (H)End Source port - Low          |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |   (K)Dst   (I)Start Destination port - High   |          (L)SPI   (J)End Destination port     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |          (L)SPI  (K)Start DS  |  (L)End DS    |(M)Start Prot. | (N) End Prot. |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                  Figure 1: IPv4 binary traffic selector

   Flags (A-L) (A-N)

      Each flag indicates whether the corresponding field is present in
      the message

   (A)DS - Differential Services

      The Differential Services (DS)

   (A)Start Source Address

      This field in identifies the first source address, from the range of
      32-bit IPv4 addresses to be matched, on data packet packets as seen by
      the home agent.  Note that  In other words this is called Type one of Service field in
      [RFC0791].  [RFC3260] then clarified that the field has been
      redefined as 6 bits DS field and 2 bits reserved, later claimed by
      Explicit Congestion Notification (ECN) [RFC3168].  For the purpose addresses of this specification
      the DS field is 8bit long, were the 6 most
      significant bits indicating the DS field correspondent node.

   (B)End Source Address

      If more than one contiguous source addresses need to be matched and the 2
      list significant bits MUST mached
      then this field can be set used to 0 by the sender and ignored
      by the receiver.

   (B)Protocol

      An 8-bit unsigned integer representing indicate the end value of a range
      starting from the transport
      protocol number associated with value of the port numbers in data packets.

   (C)Source Start Source Address field.  This
      field identifies the source address of data packets as seen
      by MUST NOT be included unless the home agent that is, Start Source Address field
      is included.  When this field is included the 32-bit IPv4 address receiver will match
      all of the
      correspondent node.

   (D)Destination addresses between fields (A) and (B), inclusive of (A)
      and (B).

   (C)Start Destination Address

      This field identifies the first destination address address, from the
      range of 32-bit IPv4 addresses to be matched, on data packets as
      seen by the home agent.  When included  In other words this field must is one of the
      registered home addresses of the mobile node.  It is a 32-bit IPv4
      address.

   (E)Source Prefix Length

      This

   (D)End Destination Address

      If more than one contiguous destination addresses need to be
      mached then this field includes can be used to indicate the prefix length for end value of a
      range starting from the source address. value of the Start Destination Address
      field.  This field can only MUST NOT be included if unless the Source Start
      Destination Address field is included.  When this field is
      included the receiver will match all of the addresses in the subnet identified by this field.

   (F)Destination Prefix Length between
      fields (C) and (D), inclusive of (C) and (D).

   (E)Start SPI - Security Parameter Index

      This field includes identifies the prefix length for first 32-bit SPI value, from the destination address.
      If The Destination Address range
      of SPI values to be matched, on data packets as seen by the home
      agent.  This field is included defined in [RFC4303]

   (F)End SPI - Security Parameter Index
      If more than one contiguous SPI values need to be mached then it refers this
      field can be used to
      that indicate the end value of a range starting
      from the value of the Start SPI field.  This field MUST NOT be
      included unless the Start SPI field is included.  When this field
      is included the receiver will match all of the addresses in the subnet identified by this field.

   (G)Source SPI values between
      fields (E) and (F), inclusive of (E) and (F).

   (G)Start Source Port - Low

      This field identifies the lowest first 16-bit source port number within a number, from
      the range of port numbers that will to be used in matched, on data packets, packets as seen
      by the home agent.

   (H)Source

   (H)End Source Port - High
      This field identifies the highest

      If more than one contiguous source port number within a
      range of port numbers that will need to be used in data packets, as seen
      by the home agent.  This mached
      then this field MUST NOT can be included if used to indicate the Source
      Port - Low field is not includede.  If end value of a single port is indicated
      then this range
      starting from the value of the Start Source Port field.  This
      field MUST NOT be included unless the Start Source Port field is
      included.  When it this field is included it MUST
      be set to the value larger than that receiver will match all
      of Source Port - Low field.

   (I)Destination the port numbers between fields (G) and (H), inclusive of (G)
      and (H).

   (I)Start Destination Port - Low

      This field identifies the lowest first 16-bit destination port number within a number,
      from the range of port numbers that will to be used in matched, on data packets as
      seen by the home agent.

   (K)Destination

   (J)End Destination Port - High

      This field identifies the highest

      If more than one contiguous destination port number within a
      range of port numbers that will need to be
      mached then this field can be used in data packets, as seen
      by to indicate the home agent. end value of a
      range starting from the value of the Start Destination Port field.
      This field MUST NOT be included if unless the Start Destination Port - Low
      field is not includede.  If a single port
      is indicated then this field MUST NOT be included.  When it this field is included it MUST be set to the value larger than that receiver will
      match all of
      Destination Port - Low field.

   (L)SPI the port numbers between fields (I) and (K),
      inclusive of (I) and (J).

   (K)Start DS - Security Parameter Index

      The SPI Differential Services

      This field in identifies the first differential services value, from
      the range of differential services values to be matched, on data packet
      packets as seen by the home agent.

   Resved

      Reserved for future use.  These  Note that this field is called
      Type of Service field in [RFC0791].  [RFC3260] then clarified that
      the field has been redefined as 6 bits DS field and 2 bits
      reserved, later claimed by Explicit Congestion Notification (ECN)
      [RFC3168].  For the purpose of this specification the DS field is
      8bit long, were the 6 most significant bits indicating the DS
      field to be matched and the 2 list significant bits MUST be set to zero
      0 by the sender and ignored by the receiver.

3.2.  IPv6 binary traffic selector

   (L)End DS - Differential Services

      If the Type more than one contiguous DS values need to be mached then this
      field of can be used to indicate the traffic end value of a range starting
      from the value of the Start DS field.  This field MUST NOT be
      included unless the Start DS field is included.  When this field
      is included the receiver will match all of the values between
      fields (K) and (L), inclusive of (K) and (L).

   (M)Start Protocol

      This field identifies the first 8-bit protocol value, from the
      range of protocol values to be matched, on data packets as seen by
      the home agent.

   (N)End Protocol

      If more than one contiguous protocol values need to be mached then
      this field can be used to indicate the end value of a range
      starting from the value of the Start Protocol field.  This field
      MUST NOT be included unless the Start Protocol field is included.
      When this field is included the receiver will match all of the
      values between fields (M) and (N), inclusive of (M) and (N).

   Reserved

      Reserved for future use.  These bits MUST be set to zero by the
      sender and ignored by the receiver.

3.2.  IPv6 binary traffic selector

   If the TS Format field of the traffic selector sub-option indicates
   "IPv6 binary traffic selector", then the traffic selector is
   formatted as follows:

         0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |A|B|C|D|E|F|G|H|I|K|L|M| Resvd
       |Sub-opt Type   |  Sub-Opt Len  |     (A)DS   TS Format   | (B)Protocol   Reserved    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|          Reserved             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                                                               |
       +                                                               +
       |                                                               |
       +                    (C)Source                  (A)Start Source Address                      +
       |                                                               |
       +                                                               +
       |                                                               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                                                               |
       +                                                               +
       |                                                               |
       +                 (D)Destination                  (B)End Source Address                        +
       |                                                               |
       +                                                               +
       |                                                               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |(E)S. PrefLeng |(F)D. PrefLeng
       |   (G)Source port - Low                                                               |
       +                                                               +
       |                                                               |
       +               (C)Start Destination Address                    +
       |                                                               |
       +                                                               +
       |                                                               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                                                               |
       +                                                               +
       |                                                               |
       +                (D)End Destination Address                     +
       |                                                               |
       +                                                               +
       |                                                               |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                          (E)Start SPI                         |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                          (F)End SPI                           |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                      (G)Start Flow Label                      |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                       (H)End Flow Label                       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |   (H)Source   (I)Start Source port - High        |      (I)Dst   (J)End Source port - Low          |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |   (K)Dst   (K)Start Destination port - High   |          (L)SPI   (L)End Destination port     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |          (L)SPI  (M)Start DS  |     (M)Flow Label  (N)End DS    |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ (O)Start NH   | (M)Flow Label (P) End NH    |
     +-+-+-+-+-+-+-+-+
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                  Figure 2: IPv6 binary traffic selector

   Flags (A-M) (A-P)
      Each flag indicates whether the corresponding corresponding field is present in
      the message

   (A)Start Source Address

      This field identifies the first source address, from the range of
      128-bit IPv6 addresses to be matched, on data packets as seen by
      the home agent.  In other words this is one of the addresses of
      the correspondent node.

   (B)End Source Address

      If more than one contiguous source addresses need to be mached
      then this field can be used to indicate the end value of a range
      starting from the value of the Start Source Address field.  This
      field MUST NOT be included unless the Start Source Address field
      is included.  When this field is included the receiver will match
      all of the addresses between fields (A) and (B), inclusive of (A)
      and (B).

   (C)Start Destination Address

      This field identifies the first destination address, from the
      range of 128-bit IPv6 addresses to be matched, on data packets as
      seen by the home agent.  In other words this is one of the
      registered addresses of the mobile node.

   (D)End Destination Address

      If more than one contiguous destination addresses need to be
      mached then this field can be used to indicate the end value of a
      range starting from the value of the Start Destination Address
      field.  This field MUST NOT be included unless the Start
      Destination Address field is included.  When this field is
      included the receiver will match all of the addresses between
      fields (C) and (D), inclusive of (C) and (D).

   (E)Start SPI - Security Parameter Index

      This field identifies the first 32-bit SPI value, from the range
      of SPI values to be matched, on data packets as seen by the home
      agent.

   (F)End SPI - Security Parameter Index

      If more than one contiguous SPI values need to be mached then this
      field can be used to indicate the end value of a range starting
      from the value of the Start SPI field.  This field MUST NOT be
      included unless the Start SPI field is included.  When this field
      is included the receiver will match all of the SPI values between
      fields (E) and (F), inclusive of (E) and (F).

   (G)Start Flow Label

      This field identifies the first flow label value, from the range
      of flow label values to be matched, on data packets as seen by the
      home agent.  According to [RFC2460] the flow label is 24-bit long.
      For the purpose of this specification the sender of this options
      MUST prefix flow label values with 8-bits of "0" before inserting
      it in this field.  The receive SHOULD ignore the first 8-bits of
      this field.

   (H)End Flow Label

      If more than one contiguous flow label values need to be mached
      then this field can be used to indicate the end value of a range
      starting from the value of the Start Flow Label field.  This field
      MUST NOT be included unless the Start Flow Label field is
      included.  When this field is included the receiver will match all
      of the flow label values between fields (G) and (H), inclusive of
      (G) and (H).

   (I)Start Source Port

      This field identifies the first 16-bit source port number, from
      the range of port numbers to be matched, on data packets as seen
      by the home agent.

   (J)End Source Port

      If more than one contiguous source port numbers need to be mached
      then this field can be used to indicate the end value of a range
      starting from the value of the Start Source Port field.  This
      field MUST NOT be included unless the Start Source Port field is
      included.  When this field is included the receiver will match all
      of the port numbers between fields (I) and (J), inclusive of (I)
      and (J).

   (K)Start Destination Port

      This field identifies the first 16-bit destination port number,
      from the range of port numbers to be matched, on data packets as
      seen by the home agent.

   (L)End Destination Port
      If more than one contiguous destination port numbers need to be
      mached then this field can be used to indicate the end value of a
      range starting from the value of the Start Destination Port field.
      This field MUST NOT be included unless the Start Destination Port
      field is present in included.  When this field is included the message

   (A) receiver will
      match all of the port numbers between fields (K) and (L),
      inclusive of (K) and (L).

   (M)Start DS - Differential Services

      The Differential Services (DS)

      This field in identifies the first differential services value, from
      the range of differential services values to be matched, on data packet
      packets as seen by the home agent.  Note that this field is called Traffic Class
      Type of Service field in
      [RFC2460]. [RFC0791].  [RFC3260] then clarified that
      the field has been redefined as 6 bits DS field and 2 bits
      reserved, later claimed by Explicit Congestion Notification (ECN) in
      [RFC3168].  For the purpose of this specification the DS field is
      8bit long, were the 6 most significant bits indicating the DS
      field to be matched and the 2 list significant bits MUST be set to
      0 by the sender and ignored by the receiver.

   (B)Protocol

      An 8-bit unsigned integer representing value of the transport
      protocol number associated with the port numbers in data packets.

   (C)Source Address

      This field identifies the source address of data packets as seen
      by the home agent.  That is, the address of the correspondent node
      and it is a 128-bit IPv6 address.

   (D)Destination Address

      This field identifies the destination address of the data packet
      as seen by the home agent.  When included this field must be set
      to either

   (N)End DS - Differential Services

      If more than one of the registered home addresses of the mobile node
      or contiguous DS values need to an address that falls under one of the mobile's home network
      prefixes.  The value of this fild is 128-bit IPv6 address.

   (E)Source Prefix Length

      This field includes the prefix for the source address.  This field
      MUST NOT be included if the Source Address field is not included.
      When this field is included the receiver will match all of the
      addresses in the subnet identified by this field.

   (F)Destination Prefix Length

      This field includes the prefix for the destination address.  This
      field MUST NOT be included if the Source Address field is not
      included.  When this field is included the receiver will match all
      of the addresses in the subnet identified by this field.

   (G)Source Port - Low

      This field identifies the lowest source port number within a range
      of port numbers that will be used in data packets, as seen by the
      home agent.

   (H)Source Port - High

      This mached then this
      field identifies can be used to indicate the highest source port number within end value of a range starting
      from the value of port numbers that will be used in data packets, as seen
      by the home agent. Start DS field.  This field MUST NOT be
      included if unless the Source
      Port - Low Start DS field is not includede.  If a single port is indicated
      then this field MUST NOT be included.  When it this field
      is included it MUST
      be set to the value larger than that receiver will match all of Source Port - Low field.

   (I)Destination Port the values between
      fields (M) and (N), inclusive of (M) and (N).

   (O)Start NH - Low Next Header

      This field identifies the lowest destination port number within a first 8-bit next header value, from the
      range of port numbers that will next header values to be used in matched, on data packets as seen
      by the home agent.

   (K)Destination Port

   (P)End NH - High

      This Next Header

      If more than one contiguous next header values need to be mached
      then this field identifies can be used to indicate the highest destination port number within end value of a range
      starting from the value of port numbers that will be used in data packets, as seen
      by the home agent. Start NH field.  This field MUST
      NOT be included if unless the
      Destination Port - Low Start next header field is not includede.  If a single port
      is indicated then this field MUST NOT be included.
      When it this field is included it the receiver will match all of the
      values between fields (O) and (P), inclusive of (O) and (P).

   Reserved
      Reserved for future use.  These bits MUST be set to the value larger than that of
      Destination Port - Low field.

   (L)SPI - Security Parameter Index

      The SPI field in the data packet as seen zero by the home agent.

   (M)Flow Label

      The Flow Label field in the data packet as seen
      sender and ignored by the home agent.

   Resved

      Reserved for future use. receiver.

4.  Flow Identification Status codes

   TBD

5.  Security Considerations

   This draft defines the format of traffic selector sub-options defined
   in the flow bindings [I-D.ietf-mext-flow-binding].  The authors have
   not identified any security concenrs pertaining to this draft beyond
   what is already identified in [I-D.ietf-mext-flow-binding].

6.

5.  IANA Considerations

   TBD

7.

   1) New TS format values from the "Traffic Selector Format" namespace
   for the Traffic Selector sub-option defined in
   [I-D.ietf-mext-flow-binding].  Values are requested for the
   following:

      IPv4 Binary Traffic Selector

      IPv6 Binary Traffic Selector

6.  Aknowledgements

   TBD

8.

   The authors would like to thank Patrick Stupar and Julien Laganier
   for their contributions to this document.

7.  References

8.1.

7.1.  Normative References

   [I-D.ietf-mext-flow-binding]
              Soliman, H., Montavont, N., and K. Kuladinithi, "Flow
              Bindings in Mobile IPv6 and NEMO Basic Support",
              draft-ietf-mext-flow-binding-03 (work in progress),
              July 2009.

   [RFC0768]  Postel, J., "User Datagram Protocol", STD 6, RFC 768,
              August 1980.

   [RFC0791]  Postel, J., "Internet Protocol", STD 5, RFC 791,
              September 1981.

   [RFC0793]  Postel, J., "Transmission Control Protocol", STD 7,
              RFC 793, September 1981.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2460]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
              (IPv6) Specification", RFC 2460, December 1998.

   [RFC3168]  Ramakrishnan, K., Floyd, S., and D. Black, "The Addition
              of Explicit Congestion Notification (ECN) to IP",
              RFC 3168, September 2001.

8.2.

   [RFC4303]  Kent, S., "IP Encapsulating Security Payload (ESP)",
              RFC 4303, December 2005.

7.2.  Informative References

   [RFC3260]  Grossman, D., "New Terminology and Clarifications for
              Diffserv", RFC 3260, April 2002.

Authors' Addresses

   George Tsirtsis
   Qualcomm

   Email: tsirtsis@gmail.com

   Gerardo Giarreta
   Qualcomm

   Email: gerardog@qualcomm.com

   Hesham Soliman
   Elevate Technologies

   Email: hesham@elevatemobile.com

   Nicolas Montavont
   Institut Telecom / Telecom Bretagne
   2, rue de la chataigneraie
   Cesson Sevigne  35576
   France

   Phone: (+33) 2 99 12 70 23
   Email: nicolas.montavont@telecom-bretagne.eu
   URI:   http://www.rennes.enst-bretagne.fr/~nmontavo//