draft-ietf-idr-bgp-bestpath-selection-criteria-06.txt   draft-ietf-idr-bgp-bestpath-selection-criteria-07.txt 
IDR Working Group Rajiv Asati IDR Working Group Rajiv Asati
Internet Draft Cisco Systems Internet Draft Cisco Systems
Intended status: Standards Track Intended status: Standards Track
Expires: August 25, 2013 Expires: October 5, 2017
February 25, 2013 April 5, 2017
BGP Bestpath Selection Criteria Enhancement BGP Bestpath Selection Criteria Enhancement
draft-ietf-idr-bgp-bestpath-selection-criteria-06.txt draft-ietf-idr-bgp-bestpath-selection-criteria-07.txt
Abstract Abstract
BGP specification [RFC4271] prescribes 'BGP next-hop reachability' BGP specification (RFC4271) prescribes 'BGP next-hop reachability'
as one of the key 'Route Resolvability Condition' that must be as one of the key 'Route Resolvability Condition' that must be
satisfied before the BGP bestpath candidate selection. This satisfied before the BGP bestpath candidate selection. This
condition, however, may not be sufficient (as explained in the condition, however, may not be sufficient (as explained in the
Appendix section) and desire further granularity. Appendix section) and desire further granularity.
This document defines enhances the "Route Resolvability Condition" This document defines enhances the "Route Resolvability Condition"
to facilitate the next-hop to be resolved in the chosen data plane. to facilitate the next-hop to be resolved in the chosen data plane.
Status of this Memo Status of this Memo
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 August 25, 2013. This Internet-Draft will expire on October 5, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2017 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
skipping to change at page 8, line 6 skipping to change at page 8, line 6
transport IPv6 packets over the MPLS network. transport IPv6 packets over the MPLS network.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [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, March 1997.
[RFC4364] Rosen E. and Rekhter Y., "BGP/MPLS IP Virtual Private [RFC4364] Rosen E. and Rekhter Y., "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC4364, February 2006. Networks (VPNs)", RFC4364, March 2006.
[RFC4271] Rekhter, Y., Li T., and Hares S.(editors), "A Border [RFC4271] Rekhter, Y., Li T., and Hares S.(editors), "A Border
Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006 Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006
9.2. Informative References 9.2. Informative References
[RFC3031] Rosen, et al., "Multiprotocol Label Switching [RFC3031] Rosen, et al., "Multiprotocol Label Switching
Architecture", RFC3031, Jan 2001. Architecture", RFC3031, Jan 2001.
[RFC5512] Rosen, E., Mohapatra, P., "BGP Encapsulation SAFI and BGP [RFC5512] Rosen, E., Mohapatra, P., "BGP Encapsulation SAFI and BGP
 End of changes. 6 change blocks. 
7 lines changed or deleted 7 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/