draft-ietf-mpls-ldp-typed-wildcard-06.txt   draft-ietf-mpls-ldp-typed-wildcard-07.txt 
MPLS Working Group Rajiv Asati MPLS Working Group Rajiv Asati
Internet Draft Cisco Systems Internet Draft Cisco Systems
Intended status: Standards Track Intended status: Standards Track
Expires: July 2010 Ina Minei Expires: July 2010 Ina Minei
Juniper Networks Juniper Networks
Bob Thomas Bob Thomas
February 24, 2010 March 4, 2010
LDP Typed Wildcard FEC Label Distribution Protocol (LDP) 'Typed Wildcard' Forward
draft-ietf-mpls-ldp-typed-wildcard-06.txt Equivalence Class (FEC)
draft-ietf-mpls-ldp-typed-wildcard-07.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 36 skipping to change at page 1, line 37
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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 July 24, 2010. This Internet-Draft will expire on July 4, 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 carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the BSD License. warranty as described in the BSD License.
Abstract Abstract
The Label Distribution Protocol (LDP) specification for the Wildcard The Label Distribution Protocol (LDP) specification for the Wildcard
FEC element has several limitations. This document addresses those Forward Equivalence Class (FEC) element has several limitations.
limitations by defining a Typed Wildcard FEC element and associated This document addresses those limitations by defining a Typed
procedures. In addition, it defines a new LDP capability to address Wildcard FEC element and associated procedures. In addition, it
backward compatibility. defines a new LDP capability to address backward compatibility.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
2. Specification Language.........................................4 2. Specification Language.........................................4
3. The Typed Wildcard FEC Element.................................4 3. The Typed Wildcard FEC Element.................................4
4. Procedures for the Typed Wildcard FEC Element..................5 4. Procedures for the Typed Wildcard FEC Element..................5
5. Typed Wildcard FEC Capability..................................6 5. Typed Wildcard FEC Capability..................................6
6. Typed Wildcard FEC Element for Prefix FEC Element..............7 6. Typed Wildcard FEC Element for Prefix FEC Element..............7
7. Typed Wildcard FEC Element for Host and Wildcard FEC Elements..8 7. Typed Wildcard FEC Element for Host and Wildcard FEC Elements..8
skipping to change at page 8, line 7 skipping to change at page 8, line 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Typed Wcard | Type = Prefix | Len = 2 | Address... | | Typed Wcard | Type = Prefix | Len = 2 | Address... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ...Family | | ...Family |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Figure 3 Format of Prefix FEC Element using Typed Wildcard Figure 3 Format of Prefix FEC Element using Typed Wildcard
Where: Where:
FEC Element Type : "Prefix" FEC Element (value=2, per RFC5036). FEC Element Type : "Prefix" FEC Element (0x02, per RFC5036).
Len FEC Type Info : Two octets (=2). Len FEC Type Info : Two octets (=0x02).
Address Family : Two octet quantity containing a value from Address Family : Two octet quantity containing a value from
ADDRESS FAMILY NUMBERS in [IANA-AF]. ADDRESS FAMILY NUMBERS in [IANA-AF].
The procedures described in Section 4 apply to the Prefix FEC The procedures described in Section 4 apply to the Prefix FEC
Wildcard processing. Wildcard processing.
7. Typed Wildcard FEC Element for Host and Wildcard FEC Elements 7. Typed Wildcard FEC Element for Host and Wildcard FEC Elements
There is no need to specify Typed Wildcard FEC Elements for the Host There is no need to specify Typed Wildcard FEC Elements for the Host
skipping to change at page 8, line 42 skipping to change at page 8, line 42
The 'Typed Wildcard' FEC Element requires a code point from the The 'Typed Wildcard' FEC Element requires a code point from the
LDP FEC Type Name Space. [RFC5036] partitions the FEC Type Name LDP FEC Type Name Space. [RFC5036] partitions the FEC Type Name
Space into 3 regions: IETF Consensus region, First Come First Space into 3 regions: IETF Consensus region, First Come First
Served region, and Private Use region. The authors recommend Served region, and Private Use region. The authors recommend
that the code point 0x05 from the IETF Consensus range be that the code point 0x05 from the IETF Consensus range be
assigned to the 'Typed Wildcard' FEC Element. assigned to the 'Typed Wildcard' FEC Element.
The 'Typed Wildcard FEC' Capability requires a code point from The 'Typed Wildcard FEC' Capability requires a code point from
the TLV Type name space. [RFC5036] partitions the TLV TYPE name the TLV Type name space. [RFC5036] partitions the TLV TYPE name
space into 3 regions: IETF Consensus region, First Come First space into 3 regions: IETF Consensus region, Vendor Private Use
Served region, and Private Use region. The authors recommend region, and Experimental Use region. The authors recommend that
that a code point from the IETF Consensus range be assigned to a code point from the IETF Consensus range be assigned to the
the 'Typed Wildcard FEC' Capability. 'Typed Wildcard FEC' Capability.
9. Security Considerations 9. Security Considerations
No security considerations beyond those that apply to the base LDP No security considerations beyond those that apply to the base LDP
specification [RFC5036] and further described in [MPLSsec] apply to specification [RFC5036] and further described in [MPLSsec] apply to
use of the Typed Wildcard FEC Elements as described in this use of the Typed Wildcard FEC Elements as described in this
document. document.
One could deduce that the security exposure is reduced by this One could deduce that the security exposure is reduced by this
document, since an LDP speaker using Typed Wildcard FEC Element document, since an LDP speaker using Typed Wildcard FEC Element
 End of changes. 7 change blocks. 
14 lines changed or deleted 15 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/