draft-ietf-mpls-tp-ach-tlv-01.txt   draft-ietf-mpls-tp-ach-tlv-02.txt 
MPLS S. Boutros MPLS S. Boutros
Internet-Draft S. Bryant, Ed. Internet-Draft S. Bryant, Ed.
Intended status: Standards Track S. Sivabalan Intended status: Standards Track S. Sivabalan
Expires: August 6, 2010 G . Swallow Expires: September 6, 2010 G . Swallow
D. Ward
Cisco Systems Cisco Systems
February 2, 2010 D. Ward
Juniper Networks
V. Manral
IP Infusion Inc.
March 5, 2010
Definition of ACH TLV Structure Definition of ACH TLV Structure
draft-ietf-mpls-tp-ach-tlv-01 draft-ietf-mpls-tp-ach-tlv-02
Abstract Abstract
In some application of the associated channel header (ACH), it is In some application of the associated channel header (ACH), it is
necessary to have the ability to include a set of TLVs to provide necessary to have the ability to include a set of TLVs to provide
additional context information for the ACH payload. This document additional context information for the ACH payload. This document
defines a number of TLV types. defines a number of TLV types.
The following notes (up until the start of "Requirements Language" This document is a product of a joint Internet Engineering Task Force
will be deleted before Working Group Last Call (IETF) / International Telecommunications Union Telecommunications
Standardization Sector (ITU-T) effort to include an MPLS Transport
NOTE the family of Address Types is known to be incomplete. The Profile within the IETF MPLS and PWE3 architectures to support the
authors request that members of the MPLS-TP community provide details capabilities and functionalities of a packet transport network as
of their required address formats in the form of text for the defined by the ITU-T.
creation of an additional sections similar to Section 3.1.
NOTE other TLV types will be added in further revisions of this
document. The authors request that members if the MPLS-TP community
requiring new TLVs to complete there MPLS-TP specifications provide
details of their required TLV in the form of text for the creation of
additional sections similar to Section 2.2.
NOTE The intension is to keep this document as a living list of TLVs
for some time. When the Working Groups consider that we have
captured the majority of the TLVs we will close the document and
submit for publication.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [1]. document are to be interpreted as described in RFC2119 [1].
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
skipping to change at page 2, line 21 skipping to change at page 2, line 12
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 6, 2010. This Internet-Draft will expire on September 6, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. ACH TLV Object Definitions . . . . . . . . . . . . . . . . . . 4 2. ACH TLV Object Definitions . . . . . . . . . . . . . . . . . . 4
2.1. The Null TLV Object . . . . . . . . . . . . . . . . . . . 4 2.1. The Null TLV Object . . . . . . . . . . . . . . . . . . . . 4
2.2. Source Address . . . . . . . . . . . . . . . . . . . . . . 5 2.2. IPv4 Source Address . . . . . . . . . . . . . . . . . . . . 4
2.3. Destination Address . . . . . . . . . . . . . . . . . . . 5 2.3. IPv6 Source Address . . . . . . . . . . . . . . . . . . . . 5
2.4. Label Switched Path Identifier (LSPI) . . . . . . . . . . 6 2.4. ITU-T Carrier Code . . . . . . . . . . . . . . . . . . . . 5
2.5. Pseudowire Identifier (PWI) . . . . . . . . . . . . . . . 6 2.5. Global Identifier . . . . . . . . . . . . . . . . . . . . . 6
3. ACH Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 2.6. Network Interface Identifier . . . . . . . . . . . . . . . 6
3.1. IPv4 Address . . . . . . . . . . . . . . . . . . . . . . . 7 2.7. Authentication . . . . . . . . . . . . . . . . . . . . . . 7
3.2. IPv6 Address . . . . . . . . . . . . . . . . . . . . . . . 8 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.1. Normative References . . . . . . . . . . . . . . . . . . . 8
6.1. Normative References . . . . . . . . . . . . . . . . . . . 9 5.2. Informative References . . . . . . . . . . . . . . . . . . 8
6.2. Informative References . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
The MPLS generic associated channel header specification [7] (GACH) The MPLS generic associated channel header specification [6] (GACH)
describes a TLV structure that is used to provide additional context describes a TLV structure that is used to provide additional context
information for the ACH payload. This document defines a number of information for the ACH payload. This document defines a number of
TLVs that are required by the MPLS-TP design [8], [9]. One use of TLVs that are required by the MPLS-TP design [7], [8].
these TLVs to identify the source and/or intended destination of the
ACH payload for use in transport networks. However the use of this
construct is not limited to providing addressing information nor is
the applicability restricted to transport network applications.
Additionally TLVs from defined in this document may be used as sub-
TLVs in the construction of compound TLV structures.
2. ACH TLV Object Definitions 2. ACH TLV Object Definitions
This section provides the definition for a number of ACH TLV objects. This section provides the definition for a number of ACH TLV objects.
In each case the length in the TLV header is the length of just the In each case the length in the TLV header is the length of only the
value component. value component.
2.1. The Null TLV Object 2.1. The Null TLV Object
The Null TLV provides an OPTIONAL mechanism of restoring 32bit The Null TLV provides an OPTIONAL mechanism of restoring 32bit
alignment of the following element in the packet and also provides an alignment of the following element in the packet and also provides an
OPTIONAL mechanism to reserve space in the packet to be used by TLV OPTIONAL mechanism to reserve space in the packet to be used by TLV
objects that will be written by LSR that perform some operation on objects that will be written by LSR that perform some operation on
the packet at a later time. For security reasons the value must be the packet at a later time. For security reasons the value must be
zero. zero.
skipping to change at page 5, line 5 skipping to change at page 4, line 38
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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 0 | Length | | AchTlvType = 0 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Value = 0 ~ ~ Value = 0 ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: Null TLV Object Figure 1: Null TLV Object
2.2. Source Address 2.2. IPv4 Source Address
This TLV specifies the source address (SA) of an ACH packet. This TLV specifies the IPv4 [2] source address (SAv4) of an ACH
packet.
Where the packet is associated with a maintenance request/response Where the packet is associated with a maintenance request/response
operation it refers to the requester of the operation, i.e. It is operation it refers to the requester of the operation, i.e. It is
the address of the Maintenance End Point that initiated the operation the address of the Maintenance End Point that initiated the operation
being either requested, or being responded to. being either requested, or is being responded to.
The address is an ACH address as described in Section 3.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 1 | Length | | AchTlvType = 1 | Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Address | | IPv4 Address |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Source Address Figure 2: IPv4 Source Address
2.3. Destination Address 2.3. IPv6 Source Address
This TLV specifies the destination address (DA) of an ACH packet. This TLV specifies the IPv6 [3] source address (SAv6) of an ACH
packet.
Where the packet is associated with a maintenance request/response Where the packet is associated with a maintenance request/response
operation it refers to the target of the operation, i.e. It is the operation it refers to the requester of the operation, i.e. It is
address of the Maintenance End Point or Maintenance Intermediate the address of the Maintenance End Point that initiated the operation
Point that has been requested to execute the operation being either being either requested, or is being responded to.
requested, or being responded to.
The address is an ACH address as described in Section 3.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 2 | Length | | AchTlvType = 2 | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Address | ~ IPv6 Address |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Destination Address Figure 3: IPv4 Source Address
2.4. Label Switched Path Identifier (LSPI) 2.4. ITU-T Carrier Code
This TLV is used to identify a Label Switched Path (LSP). This TLV is used to carry an ITU-T Carrier Code Identifier (ICC) as
defined in M.1400 [4].
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 3 | Length | | AchTlvType = 3 | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ TBD |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ICC |
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Label Switched Path Identifier Figure 4: ITU-T Carrier Code
This will draw on the contents of [2]. Further material will be The ICC is encoded in ASCII in a fixed format 6 byte field, with
added in a future version of this document. unused trailing bytes set to NULL (0).
2.5. Pseudowire Identifier (PWI) 2.5. Global Identifier
This TLV is used to identify a pseudowire. This TLV is used to carry a Global Identifier (Global_ID) [5] .
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTlvType = 4 | Length | | AchTlvType = 4 | Length = 4 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ TBD | | Global ID |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Pseudowire Identifier Figure 5: Global_ID TLV
This will draw on the contents of [2]. Further material will be
added in a future version of this document.
3. ACH Addresses
This section is incomplete. Definitions of other address types will 2.6. Network Interface Identifier
be provided in a future version of this document. The authors would
like to take input from other members of the MPLS-TP design community
as to the required additional addressing types and the correct way to
represent them in this framework.
Addresses are expressed in the following TLV format. This This TLV is used to carry Network Interface ID (IF_ID) [5] . As
representation allows ACH TLVs to be specified in a format that is defined in [5], an IF_ID consists of a node identifier (Node_ID) and
independent of the address that are to be used in the TV instance. a Logical Interface Handle (LIH), both or which are 32 bit
Although many address types are of fixed length, and some which are identifiers.
not incorporate a length indicator, this may not always be the case
and hence a length field is incorporated in the address TLV.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AdrType | Length | | AchTlvType = 5 | Length = 8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Address |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
3.1. IPv4 Address
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AdrType = 1 | Length = 4 | | Node_ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address | | LIH |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This address TLV contains an IPv4 address as defined in [3]. Figure 6: IF_ID TLV
3.2. IPv6 Address 2.7. Authentication
0 1 2 3 The structure of the ACH authentication (auth) TLV is 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AdrType = 2 | Length = 16 | | AchTlvType = 6 | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ IPv6 Address | | Auth Type | Auth Len | Authentication Data... |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This address TLV contains an IPv6 address as defined in [4] The authentication proceedures and data format used is the same as
that defined in Sections 4.1, 4.2, 4.3 and 4.4 of [9] .
4. Security Considerations Each document which defines a channel type needs to define whether an
authentication TLV is required, permitted, or disallowed, and the
actions to be taken in normal and error situations.
An application not supporting data origin authentication MAY use this
mechanism instead of defining its own proprietery mechanism.
3. Security Considerations
This specification defines a mechanism to identify a set of protocol This specification defines a mechanism to identify a set of protocol
parameters. The necessary security considerations will be described parameters. The necessary security considerations will be described
in the definition of the protocols that uses these parameters. in the definition of the protocols that uses these parameters.
5. IANA Considerations 4. IANA Considerations
IANA is requested to create two new registries in the pseudowire name IANA is requested to create a new registry in the pseudowire name
spaces: the ACH TLV Registry and the ACH Address Type Registry. spaces: the ACH TLV Registry.
The ACH TLV Registry should be initialized with the following The ACH TLV Registry should be initialized with the following
entries. The allocation policy for this registry is IETF consensus. entries. The allocation policy for this registry is IETF consensus.
Name Type Length Description Reference Name Type Length Description Reference
(octets) (octets)
Null 0 3 Null TLV This Draft Null 0 3 Null TLV This Draft
SA 1 var Source Addr This Draft SAv4 1 4 IPv4 Source Address This Draft
DA 2 var Dest Addr This Draft SAv6 2 16 IPv6 Source Address This Draft
LSPI 3 var LSP Identifier This Draft ICC 3 6 ITU-T Carrier Code This Draft
PWI 4 var PW Identifier This Draft Global_ID 4 4 Global Identifier This Draft
PID 5 2 ACH Protocol ID This Draft IF_ID 5 8 Network Interface ID This Draft
Auth 6 var Authentication This Draft
The ACH Address Type Registry should be initialized with the
following entries. The allocation policy for this registry is IETF
consensus.
Name Type Length Description Reference
(octets)
Null 0 Reserved
IPv4 1 4 IPv4 Address This Draft
IPv6 2 16 IPv6 Address This Draft
6. References
6.1. Normative References 5. References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 5.1. Normative References
Levels", BCP 14, RFC 2119, March 1997.
[2] Kompella, K. and G. Swallow, "Detecting Multi-Protocol Label [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Switched (MPLS) Data Plane Failures", RFC 4379, February 2006. Levels", BCP 14, RFC 2119, March 1997.
[3] Postel, J., "Internet Protocol", STD 5, RFC 791, [2] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981.
September 1981.
[4] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) [3] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)
Specification", RFC 2460, December 1998. Specification", RFC 2460, December 1998.
[5] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51, [4] "ITU-T Recommendation M.1400, "Designations for interconnections
RFC 1661, July 1994. among operators' networks"", 2006.
[6] Schryver, V., "IANA Considerations for the Point-to-Point [5] Bocci, M. and G. Swallow, "MPLS-TP Identifiers",
Protocol (PPP)", BCP 88, RFC 3818, June 2004. draft-ietf-mpls-tp-identifiers-00 (work in progress),
November 2009.
6.2. Informative References 5.2. Informative References
[7] Bocci, M., Vigoureux, M., Bryant, S., Swallow, G., Ward, D., [6] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic
and R. Aggarwal, "MPLS Generic Associated Channel", Associated Channel", RFC 5586, June 2009.
draft-ietf-mpls-tp-gach-gal-06 (work in progress), May 2009.
[8] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., and [7] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., and S.
S. Ueno, "MPLS-TP Requirements", Ueno, "Requirements of an MPLS Transport Profile", RFC 5654,
draft-ietf-mpls-tp-requirements-10 (work in progress), September 2009.
August 2009.
[9] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, "A [8] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, "A
Framework for MPLS in Transport Networks", Framework for MPLS in Transport Networks",
draft-ietf-mpls-tp-framework-09 (work in progress), draft-ietf-mpls-tp-framework-10 (work in progress),
January 2010. February 2010.
[10] Beller, D. and A. Farrel, "An Inband Data Communication Network [9] Katz, D. and D. Ward, "Bidirectional Forwarding Detection",
For the MPLS Transport Profile", draft-ietf-mpls-tp-gach-dcn-06 draft-ietf-bfd-base-11 (work in progress), January 2010.
(work in progress), September 2009.
Authors' Addresses Authors' Addresses
Sami Boutros Sami Boutros
Cisco Systems Cisco Systems
Phone:
Fax:
Email: sboutros@cisco.com Email: sboutros@cisco.com
URI:
Stewart Bryant (editor) Stewart Bryant (editor)
Cisco Systems Cisco Systems
Phone:
Fax:
Email: stbryant@cisco.com Email: stbryant@cisco.com
URI:
Siva Sivabalan Siva Sivabalan
Cisco Systems Cisco Systems
Phone:
Fax:
Email: msiva@cisco.com Email: msiva@cisco.com
URI:
George Swallow George Swallow
Cisco Systems Cisco Systems
Phone:
Fax:
Email: swallow@cisco.com Email: swallow@cisco.com
URI:
David Ward David Ward
Cisco Systems Juniper Networks
Phone: Email: dward@Juniper.net
Fax:
Email: dward@cisco.com Vishwas Manral
URI: IP Infusion Inc.
Bamankhola,
Bansgali,, Almora, Uttaranchal 263601
India
Email: vishwas.ietf@gmail.com
 End of changes. 69 change blocks. 
180 lines changed or deleted 122 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/