--- 1/draft-ietf-idr-legacy-rtc-05.txt 2015-10-16 15:15:16.287218422 -0700 +++ 2/draft-ietf-idr-legacy-rtc-06.txt 2015-10-16 15:15:16.315219113 -0700 @@ -1,23 +1,23 @@ Network Working Group P. Mohapatra Internet-Draft Sproute Networks Intended status: Standards Track A. Sreekantiah -Expires: November 29, 2015 K. Patel +Expires: April 18, 2016 K. Patel B. Pithawala Cisco Systems A. Lo Arista Networks - May 28, 2015 + October 16, 2015 Automatic Route Target Filtering for legacy PEs - draft-ietf-idr-legacy-rtc-05.txt + draft-ietf-idr-legacy-rtc-06 Abstract This document describes a simple procedure that allows "legacy" BGP speakers to exchange route target membership information in BGP without using mechanisms specified in [RFC4684]. The intention of the proposed technique is to help in partial deployment scenarios and is not meant to replace [RFC4684]. Status of This Memo @@ -28,21 +28,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on November 29, 2015. + This Internet-Draft will expire on April 18, 2016. Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -309,36 +309,43 @@ 9. Security Considerations There are no additional security risks introduced by this design. 10. References 10.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, March 1997. + Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ + RFC2119, March 1997, + . - [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway - Protocol 4 (BGP-4)", RFC 4271, January 2006. + [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A + Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI + 10.17487/RFC4271, January 2006, + . [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended - Communities Attribute", RFC 4360, February 2006. + Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, + February 2006, . [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private - Networks (VPNs)", RFC 4364, February 2006. + Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February + 2006, . [RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk, R., Patel, K., and J. Guichard, "Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual - Private Networks (VPNs)", RFC 4684, November 2006. + Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684, + November 2006, . 10.2. Informational References [I-D.chen-bgp-ext-community-orf] Chen, E., Lo, A., and K. Patel, "Extended Community Based Outbound Route Filter for BGP-4", draft-chen-bgp-ext- community-orf-02 (work in progress), December 2011. [I-D.keyur-bgp-af-specific-rt-constrain] Patel, K., Raszuk, R., Djernaes, M., Dong, J., and M.