draft-ietf-grow-mrt-add-paths-00.txt   draft-ietf-grow-mrt-add-paths-01.txt 
Global Routing Operations C. Petrie Global Routing Operations C. Petrie
Internet-Draft RIPE NCC Internet-Draft RIPE NCC
Intended status: Standards Track T. King Intended status: Standards Track T. King
Expires: July 8, 2016 DE-CIX Management GmbH Expires: January 9, 2017 DE-CIX Management GmbH
January 5, 2016 July 8, 2016
Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format
with BGP Additional Paths Extensions with BGP Additional Paths Extensions
draft-ietf-grow-mrt-add-paths-00 draft-ietf-grow-mrt-add-paths-01
Abstract Abstract
This document updates the Multi-threaded Routing Toolkit (MRT) export This document updates the Multi-threaded Routing Toolkit (MRT) export
format for Border Gateway Protocol (BGP) routing information by format for Border Gateway Protocol (BGP) routing information by
extending it to support the Advertisement of Multiple Paths in BGP extending it to support the Advertisement of Multiple Paths in BGP
extensions. extensions.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 July 8, 2016. This Internet-Draft will expire on January 9, 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 4, line 46 skipping to change at page 4, line 46
This adds a field to the RIB Entries record, to store the path This adds a field to the RIB Entries record, to store the path
identifier, when used with the RIB_IPV4_UNICAST_ADDPATH, identifier, when used with the RIB_IPV4_UNICAST_ADDPATH,
RIB_IPV4_MULTICAST_ADDPATH, RIB_IPV6_UNICAST_ADDPATH and RIB_IPV4_MULTICAST_ADDPATH, RIB_IPV6_UNICAST_ADDPATH and
RIB_IPV6_MULTICAST_ADDPATH subtypes. RIB_IPV6_MULTICAST_ADDPATH subtypes.
5.2. RIB_GENERIC_ADDPATH Subtype 5.2. RIB_GENERIC_ADDPATH Subtype
The fields of this subtype are identical to the equivalent non- The fields of this subtype are identical to the equivalent non-
additional-path versions specified in section 4.3.3 [RFC6396]. These additional-path versions specified in section 4.3.3 [RFC6396]. These
fields continue to encapsulate the raw and addtional-path enabled fields continue to encapsulate the raw and additional-path enabled
AFI/SAFI/NLRI in the record, and the raw attributes in the RIB AFI/SAFI/NLRI in the record, and the raw attributes in the RIB
Entries. Entries.
For clarity, the RIB Entries in this subtype are not redefined. For clarity, the RIB Entries in this subtype are not redefined.
6. IANA Considerations 6. IANA Considerations
This document requests that IANA assign the following subtype codes This document requests that IANA assign the following subtype codes
to the MRT name space [1]: to the MRT name space [1]:
skipping to change at page 6, line 18 skipping to change at page 6, line 18
paths within its networks. The BGP peer should consider any and all paths within its networks. The BGP peer should consider any and all
implications of exposing this additional data. implications of exposing this additional data.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-idr-add-paths] [I-D.ietf-idr-add-paths]
Walton, D., Retana, A., Chen, E., and J. Scudder, Walton, D., Retana, A., Chen, E., and J. Scudder,
"Advertisement of Multiple Paths in BGP", draft-ietf-idr- "Advertisement of Multiple Paths in BGP", draft-ietf-idr-
add-paths-13 (work in progress), December 2015. add-paths-15 (work in progress), May 2016.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC6396] Blunk, L., Karir, M., and C. Labovitz, "Multi-Threaded [RFC6396] Blunk, L., Karir, M., and C. Labovitz, "Multi-Threaded
Routing Toolkit (MRT) Routing Information Export Format", Routing Toolkit (MRT) Routing Information Export Format",
RFC 6396, DOI 10.17487/RFC6396, October 2011, RFC 6396, DOI 10.17487/RFC6396, October 2011,
<http://www.rfc-editor.org/info/rfc6396>. <http://www.rfc-editor.org/info/rfc6396>.
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 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/