draft-ietf-idr-rfc7752bis-03.txt   draft-ietf-idr-rfc7752bis-04.txt 
Inter-Domain Routing K. Talaulikar, Ed. Inter-Domain Routing K. Talaulikar, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Obsoletes: 7752 (if approved) March 5, 2020 Obsoletes: 7752 (if approved) September 4, 2020
Intended status: Standards Track Intended status: Standards Track
Expires: September 6, 2020 Expires: March 8, 2021
Distribution of Link-State and Traffic Engineering Information Using BGP Distribution of Link-State and Traffic Engineering Information Using BGP
draft-ietf-idr-rfc7752bis-03 draft-ietf-idr-rfc7752bis-04
Abstract Abstract
In a number of environments, a component external to a network is In a number of environments, a component external to a network is
called upon to perform computations based on the network topology and called upon to perform computations based on the network topology and
current state of the connections within the network, including current state of the connections within the network, including
Traffic Engineering (TE) information. This is information typically Traffic Engineering (TE) information. This is information typically
distributed by IGP routing protocols within the network. distributed by IGP routing protocols within the network.
This document describes a mechanism by which link-state and TE This document describes a mechanism by which link-state and TE
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 September 6, 2020. This Internet-Draft will expire on March 8, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 19, line 11 skipping to change at page 19, line 11
The format and semantics of the Value fields in most Link Descriptor The format and semantics of the Value fields in most Link Descriptor
TLVs correspond to the format and semantics of Value fields in IS-IS TLVs correspond to the format and semantics of Value fields in IS-IS
Extended IS Reachability sub-TLVs, defined in [RFC5305], [RFC5307], Extended IS Reachability sub-TLVs, defined in [RFC5305], [RFC5307],
and [RFC6119]. Although the encodings for Link Descriptor TLVs were and [RFC6119]. Although the encodings for Link Descriptor TLVs were
originally defined for IS-IS, the TLVs can carry data sourced by originally defined for IS-IS, the TLVs can carry data sourced by
either IS-IS or OSPF. either IS-IS or OSPF.
The following TLVs are defined as Link Descriptors in the Link NLRI: The following TLVs are defined as Link Descriptors in the Link NLRI:
+-----------+---------------------+--------------+------------------+ +-----------+---------------------+--------------+------------------+
| TLV Code | Description | IS-IS TLV | Reference | | TLV Code | Description | IS-IS | Reference |
| Point | | /Sub-TLV | (RFC/Section) | | Point | | TLV/Sub-TLV | (RFC/Section) |
+-----------+---------------------+--------------+------------------+ +-----------+---------------------+--------------+------------------+
| 258 | Link Local/Remote | 22/4 | [RFC5307] / 1.1 | | 258 | Link Local/Remote | 22/4 | [RFC5307] / 1.1 |
| | Identifiers | | | | | Identifiers | | |
| 259 | IPv4 interface | 22/6 | [RFC5305] / 3.2 | | 259 | IPv4 interface | 22/6 | [RFC5305] / 3.2 |
| | address | | | | | address | | |
| 260 | IPv4 neighbor | 22/8 | [RFC5305] / 3.3 | | 260 | IPv4 neighbor | 22/8 | [RFC5305] / 3.3 |
| | address | | | | | address | | |
| 261 | IPv6 interface | 22/12 | [RFC6119] / 4.2 | | 261 | IPv6 interface | 22/12 | [RFC6119] / 4.2 |
| | address | | | | | address | | |
| 262 | IPv6 neighbor | 22/13 | [RFC6119] / 4.3 | | 262 | IPv6 neighbor | 22/13 | [RFC6119] / 4.3 |
skipping to change at page 28, line 6 skipping to change at page 28, line 6
Extended IS Reachability sub-TLVs, defined in [RFC5305] and Extended IS Reachability sub-TLVs, defined in [RFC5305] and
[RFC5307]. Other Link Attribute TLVs are defined in this document. [RFC5307]. Other Link Attribute TLVs are defined in this document.
Although the encodings for Link Attribute TLVs were originally Although the encodings for Link Attribute TLVs were originally
defined for IS-IS, the TLVs can carry data sourced by either IS-IS or defined for IS-IS, the TLVs can carry data sourced by either IS-IS or
OSPF. OSPF.
The following Link Attribute TLVs are defined for the BGP-LS The following Link Attribute TLVs are defined for the BGP-LS
Attribute associated with a Link NLRI: Attribute associated with a Link NLRI:
+-----------+---------------------+--------------+------------------+ +-----------+---------------------+--------------+------------------+
| TLV Code | Description | IS-IS TLV | Reference | | TLV Code | Description | IS-IS | Reference |
| Point | | /Sub-TLV | (RFC/Section) | | Point | | TLV/Sub-TLV | (RFC/Section) |
+-----------+---------------------+--------------+------------------+ +-----------+---------------------+--------------+------------------+
| 1028 | IPv4 Router-ID of | 134/--- | [RFC5305] / 4.3 | | 1028 | IPv4 Router-ID of | 134/--- | [RFC5305] / 4.3 |
| | Local Node | | | | | Local Node | | |
| 1029 | IPv6 Router-ID of | 140/--- | [RFC6119] / 4.1 | | 1029 | IPv6 Router-ID of | 140/--- | [RFC6119] / 4.1 |
| | Local Node | | | | | Local Node | | |
| 1030 | IPv4 Router-ID of | 134/--- | [RFC5305] / 4.3 | | 1030 | IPv4 Router-ID of | 134/--- | [RFC5305] / 4.3 |
| | Remote Node | | | | | Remote Node | | |
| 1031 | IPv6 Router-ID of | 140/--- | [RFC6119] / 4.1 | | 1031 | IPv6 Router-ID of | 140/--- | [RFC6119] / 4.1 |
| | Remote Node | | | | | Remote Node | | |
| 1088 | Administrative | 22/3 | [RFC5305] / 3.1 | | 1088 | Administrative | 22/3 | [RFC5305] / 3.1 |
skipping to change at page 32, line 28 skipping to change at page 32, line 28
of IGP attributes (such as metric, route tags, etc.) that are of IGP attributes (such as metric, route tags, etc.) that are
advertised in the BGP-LS Attribute with Prefix NLRI types 3 and 4. advertised in the BGP-LS Attribute with Prefix NLRI types 3 and 4.
The following Prefix Attribute TLVs are defined for the BGP-LS The following Prefix Attribute TLVs are defined for the BGP-LS
Attribute associated with a Prefix NLRI: Attribute associated with a Prefix NLRI:
+---------------+-----------------------+----------+----------------+ +---------------+-----------------------+----------+----------------+
| TLV Code | Description | Length | Reference | | TLV Code | Description | Length | Reference |
| Point | | | | | Point | | | |
+---------------+-----------------------+----------+----------------+ +---------------+-----------------------+----------+----------------+
| 1152 | IGP Flags | 1 | Section | | 1152 | IGP Flags | 1 | Section 4.3.3. |
| | | | 4.3.3.1 | | | | | 1 |
| 1153 | IGP Route Tag | 4*n | [RFC5130] | | 1153 | IGP Route Tag | 4*n | [RFC5130] |
| 1154 | IGP Extended Route | 8*n | [RFC5130] | | 1154 | IGP Extended Route | 8*n | [RFC5130] |
| | Tag | | | | | Tag | | |
| 1155 | Prefix Metric | 4 | [RFC5305] | | 1155 | Prefix Metric | 4 | [RFC5305] |
| 1156 | OSPF Forwarding | 4 | [RFC2328] | | 1156 | OSPF Forwarding | 4 | [RFC2328] |
| | Address | | | | | Address | | |
| 1157 | Opaque Prefix | variable | Section | | 1157 | Opaque Prefix | variable | Section 4.3.3. |
| | Attribute | | 4.3.3.6 | | | Attribute | | 6 |
+---------------+-----------------------+----------+----------------+ +---------------+-----------------------+----------+----------------+
Table 10: Prefix Attribute TLVs Table 10: Prefix Attribute TLVs
4.3.3.1. IGP Flags TLV 4.3.3.1. IGP Flags TLV
The IGP Flags TLV contains IS-IS and OSPF flags and bits originally The IGP Flags TLV contains IS-IS and OSPF flags and bits originally
assigned to the prefix. The IGP Flags TLV is encoded as follows: assigned to the prefix. The IGP Flags TLV is encoded as follows:
0 1 2 3 0 1 2 3
skipping to change at page 56, line 8 skipping to change at page 56, line 8
Multi-Instance", RFC 8202, DOI 10.17487/RFC8202, June Multi-Instance", RFC 8202, DOI 10.17487/RFC8202, June
2017, <https://www.rfc-editor.org/info/rfc8202>. 2017, <https://www.rfc-editor.org/info/rfc8202>.
[RFC8654] Bush, R., Patel, K., and D. Ward, "Extended Message [RFC8654] Bush, R., Patel, K., and D. Ward, "Extended Message
Support for BGP", RFC 8654, DOI 10.17487/RFC8654, October Support for BGP", RFC 8654, DOI 10.17487/RFC8654, October
2019, <https://www.rfc-editor.org/info/rfc8654>. 2019, <https://www.rfc-editor.org/info/rfc8654>.
12.2. Informative References 12.2. Informative References
[I-D.ietf-idr-bgpls-inter-as-topology-ext] [I-D.ietf-idr-bgpls-inter-as-topology-ext]
Wang, A., Chen, H., Talaulikar, K., Zhuang, S., and S. Ma, Wang, A., Chen, H., Talaulikar, K., and S. Zhuang, "BGP-LS
"BGP-LS Extension for Inter-AS Topology Retrieval", draft- Extension for Inter-AS Topology Retrieval", draft-ietf-
ietf-idr-bgpls-inter-as-topology-ext-07 (work in idr-bgpls-inter-as-topology-ext-08 (work in progress),
progress), September 2019. April 2020.
[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
and E. Lear, "Address Allocation for Private Internets", and E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996,
<https://www.rfc-editor.org/info/rfc1918>. <https://www.rfc-editor.org/info/rfc1918>.
[RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis",
RFC 4272, DOI 10.17487/RFC4272, January 2006, RFC 4272, DOI 10.17487/RFC4272, January 2006,
<https://www.rfc-editor.org/info/rfc4272>. <https://www.rfc-editor.org/info/rfc4272>.
 End of changes. 9 change blocks. 
16 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/