draft-ietf-mpls-ldp-ipv6-03.txt   draft-ietf-mpls-ldp-ipv6-04.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Updates: 5036 (if approved) Updates: 5036 (if approved)
Intended status: Standards Track Rajiv Papneja Intended status: Standards Track Rajiv Papneja
Expires: September 2011 Isocore Expires: September 2011 Isocore
Rajiv Asati Rajiv Asati
Cisco Cisco
Carlos Pignataro Carlos Pignataro
Cisco Cisco
May 12, 2011 May 17, 2011
Updates to LDP for IPv6 Updates to LDP for IPv6
draft-ietf-mpls-ldp-ipv6-03 draft-ietf-mpls-ldp-ipv6-04
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). 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 Internet-Drafts are draft documents valid for a maximum of six
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."
This Internet-Draft will expire on November 12, 2011. This Internet-Draft will expire on November 17, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 4, line 37 skipping to change at page 4, line 37
of two routers getting connected via an additional single-stack of two routers getting connected via an additional single-stack
interface (IPv6, say), even though the IPv4 LDP session may already interface (IPv6, say), even though the IPv4 LDP session may already
be established between the LSRs over the existing interface. be established between the LSRs over the existing interface.
2. Specification Language 2. Specification 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]. document are to be interpreted as described in [RFC2119].
LDP - Label Distribution Protocol Abbreviations:
LDPv6 - Label Distribution Protocol using IPv6 transport address
family
FEC - Forwarding Equivalence Class LDP - Label Distribution Protocol
TLV - Type Length Value LDPv4 - LDP for enabling IPv4 MPLS forwarding
LSR - Label Switch Router LDPv6 - LDP for enabling IPv6 MPLS forwarding
LDPoIPv4 - LDP over IPv4 transport session
LSP - Label Switched Path LDPoIPv6 - LDP over IPv6 transport session
FEC - Forwarding Equivalence Class
TLV - Type Length Value
LSR - Label Switch Router
LSP - Label Switched Path
3. LSP Mapping 3. LSP Mapping
Section 2.1 of [RFC5036] specifies the procedure for mapping a Section 2.1 of [RFC5036] specifies the procedure for mapping a
particular packet to a particular LSP using three rules. Quoting the particular packet to a particular LSP using three rules. Quoting the
3rd rule from RFC5036: 3rd rule from RFC5036:
"If it is known that a packet must traverse a particular egress "If it is known that a packet must traverse a particular egress
router, and there is an LSP that has an Address Prefix FEC element router, and there is an LSP that has an Address Prefix FEC element
that is a /32 address of that router, then the packet is mapped to that is a /32 address of that router, then the packet is mapped to
 End of changes. 8 change blocks. 
10 lines changed or deleted 17 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/