draft-ietf-mpls-gach-adv-03.txt   draft-ietf-mpls-gach-adv-04.txt 
MPLS D. Frost, Ed. MPLS D. Frost, Ed.
Internet-Draft S. Bryant, Ed. Internet-Draft S. Bryant, Ed.
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: April 25, 2013 M. Bocci, Ed. Expires: June 9, 2013 M. Bocci, Ed.
Alcatel-Lucent Alcatel-Lucent
October 22, 2012 December 6, 2012
MPLS Generic Associated Channel (G-ACh) Advertisement Protocol MPLS Generic Associated Channel (G-ACh) Advertisement Protocol
draft-ietf-mpls-gach-adv-03 draft-ietf-mpls-gach-adv-04
Abstract Abstract
The MPLS Generic Associated Channel (G-ACh) provides an auxiliary The MPLS Generic Associated Channel (G-ACh) provides an auxiliary
logical data channel associated with a Label Switched Path (LSP), a logical data channel associated with a Label Switched Path (LSP), a
pseudowire, or a section (link) over which a variety of protocols may pseudowire, or a section (link) over which a variety of protocols may
flow. These protocols are commonly used to provide Operations, flow. These protocols are commonly used to provide Operations,
Administration, and Maintenance (OAM) mechanisms associated with the Administration, and Maintenance (OAM) mechanisms associated with the
primary data channel. This document specifies simple procedures by primary data channel. This document specifies simple procedures by
which an endpoint of an LSP, pseudowire, or section may inform the which an endpoint of an LSP, pseudowire, or section may inform the
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on April 25, 2013. This Internet-Draft will expire on June 9, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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
skipping to change at page 8, line 18 skipping to change at page 8, line 18
should be used. should be used.
4. G-ACh Advertisement Protocol TLVs 4. G-ACh Advertisement Protocol TLVs
The GAP supports several TLV objects related to its own operation via The GAP supports several TLV objects related to its own operation via
the Application ID 0x0000. These objects represent metadata and the Application ID 0x0000. These objects represent metadata and
processing instructions rather than static data that is meant to be processing instructions rather than static data that is meant to be
retained. When an ADB element for the GAP is present in a GAP retained. When an ADB element for the GAP is present in a GAP
message, it MUST precede other elements. message, it MUST precede other elements.
Any application using the GAP inherits the ability to use facilities
provide by Application 0x0000.
4.1. Source Address TLV 4.1. Source Address TLV
The Source Address object identifies the sending device and possibly The Source Address object identifies the sending device and possibly
the transmitting interface and the channel; it has the following the transmitting interface and the channel; it has the following
format: format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Reserved | Length | | Type | Reserved | Length |
skipping to change at page 16, line 19 skipping to change at page 16, line 19
authentication procedures are specified in this document that enable authentication procedures are specified in this document that enable
receivers to ensure the authenticity and integrity of GAP messages. receivers to ensure the authenticity and integrity of GAP messages.
These procedures include the means to protect against replay attacks, These procedures include the means to protect against replay attacks,
in which a third party captures a legitimate message and "replays" it in which a third party captures a legitimate message and "replays" it
to a receiver at some later time. to a receiver at some later time.
9. IANA Considerations 9. IANA Considerations
9.1. Associated Channel Type Allocation 9.1. Associated Channel Type Allocation
This document requests that IANA allocate an entry in the Pseudowire This document requests that IANA allocate an entry in the "Pseudowire
Associated Channel Types registry [RFC5586] for the G-ACh Associated Channel Types" registry [RFC5586] (currently located
Advertisement Protocol, as follows: within the "Pseudowire Name Spaces (PWE3)" registry) for the "G-ACh
Advertisement Protocol", as follows:
Value Description TLV Follows Reference Value Description TLV Follows Reference
----- ---------------------------- ----------- ------------ ----- ---------------------------- ----------- ------------
(TBD) G-ACh Advertisement Protocol No (this draft) (TBD) G-ACh Advertisement Protocol No (this draft)
9.2. Allocation of Address Family Numbers 9.2. Allocation of Address Family Numbers
This document requests that IANA allocate three entries in the IANA is requested to allocate three entries from the Standards Track
Address Family Numbers registry for MPLS-TP Section, LSP, and range in the "Address Family Numbers" registry for MPLS-TP Section,
Pseudowire endpoint identifiers, per Section 4.1. The allocations LSP, and Pseudowire endpoint identifiers, per Section 4.1. The
are: allocations are:
Number Description Reference Number Description Reference
------ -------------------------------------- ------------ ------ -------------------------------------- ------------
(TBD) MPLS-TP Section Endpoint Identifier (this draft) (TBD) MPLS-TP Section Endpoint Identifier (this draft)
(TBD) MPLS-TP LSP Endpoint Identifier (this draft) (TBD) MPLS-TP LSP Endpoint Identifier (this draft)
(TBD) MPLS-TP Pseudowire Endpoint Identifier (this draft) (TBD) MPLS-TP Pseudowire Endpoint Identifier (this draft)
9.3. Creation of G-ACh Advertisement Protocol Application Registry 9.3. Creation of G-ACh Advertisement Protocol Application Registry
This document requests that IANA create a new registry, "G-ACh This document requests that IANA create a new registry, "G-ACh
Advertisement Protocol Applications", with fields and initial Advertisement Protocol Applications" in the "Pseudowire Name Spaces
allocations as follows: (PWE3)" registry, with fields and initial allocations as follows:
Application ID Description Reference Application ID Description Reference
-------------- ---------------------------- ------------ -------------- ---------------------------- ------------
0x0000 G-ACh Advertisement Protocol (this draft) 0x0000 G-ACh Advertisement Protocol (this draft)
The range of the Application ID field is 0x0000 - 0xFFFF. The range of the Application ID field is 0x0000 - 0xFFFF.
The allocation policy for this registry is Specification Required. The allocation policy for this registry is IETF Review.
9.4. Creation of G-ACh Advertisement Protocol TLV Registry 9.4. Creation of G-ACh Advertisement Protocol TLV Registry
This document requests that IANA create a new registry, "G-ACh This document requests that IANA create a new registry, "G-ACh
Advertisement Protocol: GAP TLV Objects (Application ID 0)", with Advertisement Protocol: GAP TLV Objects (Application ID 0)" in the
fields and initial allocations as follows: "Pseudowire Name Spaces (PWE3)" registry, with fields and initial
allocations as follows:
Type Name Type ID Reference Type Name Type ID Reference
------------------ ------- ------------ ------------------ ------- ------------
Source Address 0 (this draft) Source Address 0 (this draft)
GAP Request 1 (this draft) GAP Request 1 (this draft)
GAP Flush 2 (this draft) GAP Flush 2 (this draft)
GAP Suppress 3 (this draft) GAP Suppress 3 (this draft)
GAP Authentication 4 (this draft) GAP Authentication 4 (this draft)
The range of the Type ID field is 0 - 255. The range of the Type ID field is 0 - 255.
skipping to change at page 18, line 10 skipping to change at page 18, line 10
[RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive [RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive
Connectivity Verification, Continuity Check, and Remote Connectivity Verification, Continuity Check, and Remote
Defect Indication for the MPLS Transport Profile", Defect Indication for the MPLS Transport Profile",
RFC 6428, November 2011. RFC 6428, November 2011.
10.2. Informative References 10.2. Informative References
[I-D.ietf-karp-crypto-key-table] [I-D.ietf-karp-crypto-key-table]
Housley, R., Polk, T., Hartman, S., and D. Zhang, Housley, R., Polk, T., Hartman, S., and D. Zhang,
"Database of Long-Lived Symmetric Cryptographic Keys", "Database of Long-Lived Symmetric Cryptographic Keys",
draft-ietf-karp-crypto-key-table-03 (work in progress), draft-ietf-karp-crypto-key-table-04 (work in progress),
June 2012. October 2012.
[I-D.ietf-mpls-tp-ethernet-addressing] [I-D.ietf-mpls-tp-ethernet-addressing]
Frost, D., Bryant, S., and M. Bocci, "MPLS-TP Next-Hop Frost, D., Bryant, S., and M. Bocci, "MPLS-TP Next-Hop
Ethernet Addressing", Ethernet Addressing",
draft-ietf-mpls-tp-ethernet-addressing-01 (work in draft-ietf-mpls-tp-ethernet-addressing-02 (work in
progress), May 2012. progress), November 2012.
[LLDP] IEEE, "Station and Media Access Control Connectivity [LLDP] IEEE, "Station and Media Access Control Connectivity
Discovery (802.1AB)", September 2009. Discovery (802.1AB)", September 2009.
[RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or [RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or
converting network protocol addresses to 48.bit Ethernet converting network protocol addresses to 48.bit Ethernet
address for transmission on Ethernet hardware", STD 37, address for transmission on Ethernet hardware", STD 37,
RFC 826, November 1982. RFC 826, November 1982.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
 End of changes. 12 change blocks. 
20 lines changed or deleted 25 lines changed or added

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