draft-ietf-mpls-tp-ach-tlv-00.txt   draft-ietf-mpls-tp-ach-tlv-01.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: December 7, 2009 G . Swallow Expires: August 6, 2010 G . Swallow
D. Ward D. Ward
Cisco Systems Cisco Systems
June 5, 2009 February 2, 2010
Definition of ACH TLV Structure Definition of ACH TLV Structure
draft-ietf-mpls-tp-ach-tlv-00 draft-ietf-mpls-tp-ach-tlv-01
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 December 7, 2009.
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 in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
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" The following notes (up until the start of "Requirements Language"
will be deleted before Working Group Last Call will be deleted before Working Group Last Call
skipping to change at page 3, line 5 skipping to change at page 1, line 46
for some time. When the Working Groups consider that we have for some time. When the Working Groups consider that we have
captured the majority of the TLVs we will close the document and captured the majority of the TLVs we will close the document and
submit for publication. 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
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 August 6, 2010.
Copyright Notice
Copyright (c) 2010 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 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. Source Address . . . . . . . . . . . . . . . . . . . . . . 5
2.3. Destination Address . . . . . . . . . . . . . . . . . . . 5 2.3. Destination Address . . . . . . . . . . . . . . . . . . . 5
2.4. Label Switched Path Identifier (LSPI) . . . . . . . . . . 6 2.4. Label Switched Path Identifier (LSPI) . . . . . . . . . . 6
2.5. Pseudowire Identifier (PWI) . . . . . . . . . . . . . . . 6 2.5. Pseudowire Identifier (PWI) . . . . . . . . . . . . . . . 6
3. ACH Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 3. ACH Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. IPv4 Address . . . . . . . . . . . . . . . . . . . . . . . 7 3.1. IPv4 Address . . . . . . . . . . . . . . . . . . . . . . . 7
3.2. IPv6 Address . . . . . . . . . . . . . . . . . . . . . . . 8 3.2. IPv6 Address . . . . . . . . . . . . . . . . . . . . . . . 8
4. ACH Protocol ID TLV . . . . . . . . . . . . . . . . . . . . . 8 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 6.1. Normative References . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . . 9 6.2. Informative References . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
The MPLS generic associated channel header specification [7] (GACH) The MPLS generic associated channel header specification [7] (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 [8], [9]. One use of
these TLVs to identify the source and/or intended destination of the these TLVs to identify the source and/or intended destination of the
ACH payload for use in transport networks. However the use of this ACH payload for use in transport networks. However the use of this
skipping to change at page 8, line 27 skipping to change at page 8, line 27
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 | | AdrType = 2 | Length = 16 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ IPv6 Address | ~ IPv6 Address |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This address TLV contains an IPv6 address as defined in [4] This address TLV contains an IPv6 address as defined in [4]
4. ACH Protocol ID TLV 4. Security Considerations
The ACH Protocol ID TLV is used to identify the payload protocol type
for a message carried on the GACH. The TLV is OPTIONAL in the GACH
header, but MUST be present for the Data Communications Network (DCN)
[10] .
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AchTLVType = 5 | Length = 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The value of the Protocol Identifier field is taken from PPP DLL
Protocol Number Registry [5], [6].
5. 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.
6. IANA Considerations 5. IANA Considerations
IANA is requested to create two new registries in the pseudowire name IANA is requested to create two new registries in the pseudowire name
spaces: the ACH TLV Registry and the ACH Address Type Registry. spaces: the ACH TLV Registry and the ACH Address Type 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
skipping to change at page 9, line 32 skipping to change at page 9, line 24
The ACH Address Type Registry should be initialized with the The ACH Address Type Registry should be initialized with the
following entries. The allocation policy for this registry is IETF following entries. The allocation policy for this registry is IETF
consensus. consensus.
Name Type Length Description Reference Name Type Length Description Reference
(octets) (octets)
Null 0 Reserved Null 0 Reserved
IPv4 1 4 IPv4 Address This Draft IPv4 1 4 IPv4 Address This Draft
IPv6 2 16 IPv6 Address This Draft IPv6 2 16 IPv6 Address This Draft
7. References 6. References
7.1. Normative References 6.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Kompella, K. and G. Swallow, "Detecting Multi-Protocol Label [2] Kompella, K. and G. Swallow, "Detecting Multi-Protocol Label
Switched (MPLS) Data Plane Failures", RFC 4379, February 2006. Switched (MPLS) Data Plane Failures", RFC 4379, February 2006.
[3] Postel, J., "Internet Protocol", STD 5, RFC 791, [3] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981. September 1981.
[4] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) [4] 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, [5] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51,
RFC 1661, July 1994. RFC 1661, July 1994.
[6] Schryver, V., "IANA Considerations for the Point-to-Point [6] Schryver, V., "IANA Considerations for the Point-to-Point
Protocol (PPP)", BCP 88, RFC 3818, June 2004. Protocol (PPP)", BCP 88, RFC 3818, June 2004.
7.2. Informative References 6.2. Informative References
[7] Bocci, M., Vigoureux, M., Bryant, S., Swallow, G., Ward, D., [7] Bocci, M., Vigoureux, M., Bryant, S., Swallow, G., Ward, D.,
and R. Aggarwal, "MPLS Generic Associated Channel", and R. Aggarwal, "MPLS Generic Associated Channel",
draft-ietf-mpls-tp-gach-gal-06 (work in progress), May 2009. draft-ietf-mpls-tp-gach-gal-06 (work in progress), May 2009.
[8] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., and [8] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., and
S. Ueno, "MPLS-TP Requirements", S. Ueno, "MPLS-TP Requirements",
draft-ietf-mpls-tp-requirements-08 (work in progress), draft-ietf-mpls-tp-requirements-10 (work in progress),
May 2009. August 2009.
[9] Bocci, M., Bryant, S., and L. Levrau, "A Framework for MPLS in [9] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, "A
Transport Networks", draft-ietf-mpls-tp-framework-00 (work in Framework for MPLS in Transport Networks",
progress), November 2008. draft-ietf-mpls-tp-framework-09 (work in progress),
January 2010.
[10] Beller, D. and A. Farrel, "An Inband Data Communication Network [10] Beller, D. and A. Farrel, "An Inband Data Communication Network
For the MPLS Transport Profile", draft-ietf-mpls-tp-gach-dcn-03 For the MPLS Transport Profile", draft-ietf-mpls-tp-gach-dcn-06
(work in progress), May 2009. (work in progress), September 2009.
Authors' Addresses Authors' Addresses
Sami Boutros Sami Boutros
Cisco Systems Cisco Systems
Phone: Phone:
Fax: Fax:
Email: sboutros@cisco.com Email: sboutros@cisco.com
URI: URI:
 End of changes. 13 change blocks. 
73 lines changed or deleted 59 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/