draft-ietf-idr-rtc-no-rt-05.txt | draft-ietf-idr-rtc-no-rt-06.txt | |||
---|---|---|---|---|
IDR Working Group E. Rosen, Ed. | IDR Working Group E. Rosen, Ed. | |||
Internet-Draft Juniper Networks, Inc. | Internet-Draft Juniper Networks, Inc. | |||
Updates: 4684 (if approved) K. Patel | Updates: 4684 (if approved) K. Patel | |||
Intended status: Standards Track Cisco Systems, Inc. | Intended status: Standards Track Arccus | |||
Expires: November 10, 2016 J. Haas | Expires: May 18, 2017 J. Haas | |||
Juniper Networks, Inc. | Juniper Networks, Inc. | |||
R. Raszuk | R. Raszuk | |||
Bloomberg LP | Bloomberg LP | |||
May 9, 2016 | November 14, 2016 | |||
Route Target Constrained Distribution of Routes with no Route Targets | Route Target Constrained Distribution of Routes with no Route Targets | |||
draft-ietf-idr-rtc-no-rt-05.txt | draft-ietf-idr-rtc-no-rt-06.txt | |||
Abstract | Abstract | |||
There are a variety of BGP-enabled services in which the originator | There are a variety of BGP-enabled services in which the originator | |||
of a BGP route may attach one or more "Route Targets" to the route. | of a BGP route may attach one or more "Route Targets" to the route. | |||
By means of a procedure known as "RT Constrained Distribution" (RTC), | By means of a procedure known as "RT Constrained Distribution" (RTC), | |||
a given BGP speaker (call it "B") can announce the set of RTs in | a given BGP speaker (call it "B") can announce the set of RTs in | |||
which it has interest. The implication is that if a particular route | which it has interest. The implication is that if a particular route | |||
(call it "R") carries any RTs at all, BGP speaker B wants to receive | (call it "R") carries any RTs at all, BGP speaker B wants to receive | |||
route R if and only if B has announced interest in one of the RTs | route R if and only if B has announced interest in one of the RTs | |||
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 November 10, 2016. | This Internet-Draft will expire on May 18, 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 7, line 4 ¶ | skipping to change at page 6, line 47 ¶ | |||
Authors' Addresses | Authors' Addresses | |||
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 | |||
Keyur Patel | ||||
Cisco Systems, Inc. | ||||
170 Tasman Drive | ||||
San Jose, California 95134 | ||||
United States | ||||
Email: keyupate@cisco.com | Keyur Patel | |||
Arccus | ||||
Email: keyur@arccus.com | ||||
Jeffrey Haas | Jeffrey Haas | |||
Juniper Networks, Inc. | Juniper Networks, Inc. | |||
1194 N. Mathilda Ave. | 1194 N. Mathilda Ave. | |||
Sunnyvale, California 94089 | Sunnyvale, California 94089 | |||
United States | United States | |||
Email: jhaas@juniper.net | Email: jhaas@juniper.net | |||
Robert Raszuk | Robert Raszuk | |||
Bloomberg LP | Bloomberg LP | |||
End of changes. 7 change blocks. | ||||
11 lines changed or deleted | 8 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/ |