draft-ietf-bess-ir-04.txt | draft-ietf-bess-ir-05.txt | |||
---|---|---|---|---|
BESS Working Group E. Rosen, Ed. | BESS Working Group E. Rosen, Ed. | |||
Internet-Draft Juniper Networks, Inc. | Internet-Draft Juniper Networks, Inc. | |||
Updates: 6513,6514 (if approved) K. Subramanian | Updates: 6513,6514 (if approved) K. Subramanian | |||
Intended status: Standards Track Cisco Systems, Inc. | Intended status: Standards Track Sproute Networks | |||
Expires: February 6, 2017 Z. Zhang | Expires: February 16, 2017 Z. Zhang | |||
Juniper Networks, Inc. | Juniper Networks, Inc. | |||
August 5, 2016 | August 15, 2016 | |||
Ingress Replication Tunnels in Multicast VPN | Ingress Replication Tunnels in Multicast VPN | |||
draft-ietf-bess-ir-04 | draft-ietf-bess-ir-05 | |||
Abstract | Abstract | |||
RFCs 6513, 6514, and other RFCs describe procedures by which a | RFCs 6513, 6514, and other RFCs describe procedures by which a | |||
Service Provider may offer Multicast VPN service to its customers. | Service Provider may offer Multicast VPN service to its customers. | |||
These procedures create point-to-multipoint (P2MP) or multipoint-to- | These procedures create point-to-multipoint (P2MP) or multipoint-to- | |||
multipoint trees across the Service Provider's backbone. One type of | multipoint trees across the Service Provider's backbone. One type of | |||
P2MP tree that may be used is known as an "Ingress Replication (IR) | P2MP tree that may be used is known as an "Ingress Replication (IR) | |||
tunnel". In an IR tunnel, a parent node need not be "directly | tunnel". In an IR tunnel, a parent node need not be "directly | |||
connected" to its child nodes. When a parent node has to send a | connected" to its child nodes. When a parent node has to send a | |||
skipping to change at page 1, line 48 ¶ | skipping to change at page 1, line 48 ¶ | |||
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 February 6, 2017. | This Internet-Draft will expire on February 16, 2017. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2016 IETF Trust and the persons identified as the | Copyright (c) 2016 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 11, line 38 ¶ | skipping to change at page 11, line 38 ¶ | |||
Rest of the Leaf A-D Route". The route key of the Leaf A-D route has | Rest of the Leaf A-D Route". The route key of the Leaf A-D route has | |||
the form of the "S-PMSI Route-Type Specific NLRI" in this case, and | the form of the "S-PMSI Route-Type Specific NLRI" in this case, and | |||
that should be considered to be the IR P-tunnel identifier. Note | that should be considered to be the IR P-tunnel identifier. Note | |||
that the procedure for finding the UMH is different in this case; the | that the procedure for finding the UMH is different in this case; the | |||
UMH is the next hop of the best UMH-eligible route towards the | UMH is the next hop of the best UMH-eligible route towards the | |||
"ingress PE". See the section of that document entitled "Determining | "ingress PE". See the section of that document entitled "Determining | |||
the Upstream ABR/PE/ASBR (Upstream Node)". | the Upstream ABR/PE/ASBR (Upstream Node)". | |||
5. The PTA's 'Tunnel Identifier' Field | 5. The PTA's 'Tunnel Identifier' Field | |||
As previously specified, when the "Tunnel Type" field of a PTA is set | As discussed in Section 1, when the "Tunnel Type" field of a PTA is | |||
to "IR", the "Tunnel Identifier" field of that PTA does not contain | set to "IR", the "Tunnel Identifier" field of that PTA does not | |||
the IR P-tunnel identifier. This section specifies the procedures | contain the IR P-tunnel identifier. This section (Section 5) | |||
for setting the "Tunnel Identifier" field of the PTA when the "Tunnel | specifies the procedures for setting the "Tunnel Identifier" field of | |||
Type" field of the PTA is set to "IR". | the PTA when the "Tunnel Type" field of the PTA is set to "IR". | |||
If the "Tunnel Type" field of a PTA is set to "IR", its "Tunnel | If the "Tunnel Type" field of a PTA is set to "IR", its "Tunnel | |||
Identifier" field is significant only when one of the following two | Identifier" field is significant only when one of the following two | |||
conditions holds: | conditions holds: | |||
o The PTA is carried by a Leaf A-D route, or | o The PTA is carried by a Leaf A-D route, or | |||
o The "Leaf Information Required" bit of the "Flags" field of the | o The "Leaf Information Required" bit of the "Flags" field of the | |||
PTA is not set. | PTA is not set. | |||
skipping to change at page 22, line 38 ¶ | skipping to change at page 22, line 38 ¶ | |||
Eric C. Rosen (editor) | Eric C. Rosen (editor) | |||
Juniper Networks, Inc. | Juniper Networks, Inc. | |||
10 Technology Park Drive | 10 Technology Park Drive | |||
Westford, Massachusetts 01886 | Westford, Massachusetts 01886 | |||
United States | United States | |||
Email: erosen@juniper.net | Email: erosen@juniper.net | |||
Karthik Subramanian | Karthik Subramanian | |||
Cisco Systems, Inc. | Sproute Networks | |||
170 Tasman Drive | ||||
San Jose, California 95134 | Email: karthik@sproute.com | |||
United States | ||||
Email: kartsubr@cisco.com | ||||
Zhaohui Zhang | Zhaohui Zhang | |||
Juniper Networks, Inc. | Juniper Networks, Inc. | |||
10 Technology Park Drive | 10 Technology Park Drive | |||
Westford, Massachusetts 01886 | Westford, Massachusetts 01886 | |||
United States | United States | |||
Email: zzhang@juniper.net | Email: zzhang@juniper.net | |||
End of changes. 7 change blocks. | ||||
15 lines changed or deleted | 13 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |