draft-ietf-idr-rfc4760bis-01.txt   draft-ietf-idr-rfc4760bis-02.txt 
Network Working Group Tony Bates (Skype) Network Working Group Tony Bates (Skype)
Internet Draft Ravi Chandra (Cisco Systems) Internet Draft Ravi Chandra (Cisco Systems)
Expiration Date: September 2011 Dave Katz (Juniper Networks) Expiration Date: February 2012 Dave Katz (Juniper Networks)
Yakov Rekhter (Juniper Networks) Intended Status: Proposed Standard Yakov Rekhter (Juniper Networks)
March 28, 2011 Obsoletes: RFC4760 August 15, 2011
Multiprotocol Extensions for BGP-4 Multiprotocol Extensions for BGP-4
draft-ietf-idr-rfc4760bis-01.txt draft-ietf-idr-rfc4760bis-02.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. 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), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 11, line 5 skipping to change at page 10, line 46
11. Comparison with RFC4760 11. Comparison with RFC4760
This document explicitly spells out that receiving an UPDATE message This document explicitly spells out that receiving an UPDATE message
that carried MP_REACH_NLRI or MP_UNREACH_NLRI attribute, with the that carried MP_REACH_NLRI or MP_UNREACH_NLRI attribute, with the
attribute carrying no NLRI, must not be treated as an error. attribute carrying no NLRI, must not be treated as an error.
This document also recommends that that the MP_REACH_NLRI and This document also recommends that that the MP_REACH_NLRI and
MP_UNREACH_NLRI attributes be placed as the very first path MP_UNREACH_NLRI attributes be placed as the very first path
attributes in an UPDATE in this case. attributes in an UPDATE in this case.
This document adds rules for redistribution from one <AFI, SAFI> to
another.
12. Comparison with RFC2858 12. Comparison with RFC2858
This document makes the use of the next hop information consistent This document makes the use of the next hop information consistent
with the information carried in the NEXT_HOP BGP path attribute. with the information carried in the NEXT_HOP BGP path attribute.
This document removes the definition of SAFI 3, and deprecates SAFI This document removes the definition of SAFI 3, and deprecates SAFI
3. 3.
This document changes partitioning of the SAFI space. Specifically, This document changes partitioning of the SAFI space. Specifically,
in RFC 2858 SAFI values 128 through 240 were part of the "private in RFC 2858 SAFI values 128 through 240 were part of the "private
 End of changes. 3 change blocks. 
4 lines changed or deleted 7 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/