| draft-ietf-idr-te-pm-bgp-13.txt | draft-ietf-idr-te-pm-bgp-14.txt | |||
|---|---|---|---|---|
| Networking Working Group L. Ginsberg, Ed. | Networking Working Group L. Ginsberg, Ed. | |||
| Internet-Draft Cisco Systems, Inc. | Internet-Draft Cisco Systems, Inc. | |||
| Intended status: Standards Track S. Previdi | Intended status: Standards Track S. Previdi | |||
| Expires: April 12, 2019 Q. Wu | Expires: April 24, 2019 Q. Wu | |||
| Huawei | Huawei | |||
| J. Tantsura | J. Tantsura | |||
| Apstra, Inc. | Apstra, Inc. | |||
| C. Filsfils | C. Filsfils | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| October 9, 2018 | October 21, 2018 | |||
| BGP-LS Advertisement of IGP Traffic Engineering Performance Metric | BGP-LS Advertisement of IGP Traffic Engineering Performance Metric | |||
| Extensions | Extensions | |||
| draft-ietf-idr-te-pm-bgp-13 | draft-ietf-idr-te-pm-bgp-14 | |||
| Abstract | Abstract | |||
| This document defines new BGP-LS TLVs in order to carry the IGP | This document defines new BGP-LS TLVs in order to carry the IGP | |||
| Traffic Engineering Extensions defined in IS-IS and OSPF protocols. | Traffic Engineering Extensions defined in IS-IS and OSPF protocols. | |||
| Requirements Language | Requirements Language | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
| skipping to change at page 1, line 46 ¶ | skipping to change at page 1, line 46 ¶ | |||
| 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 April 12, 2019. | This Internet-Draft will expire on April 24, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 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 2, line 35 ¶ | skipping to change at page 2, line 35 ¶ | |||
| 3.1. Unidirectional Link Delay TLV . . . . . . . . . . . . . . 3 | 3.1. Unidirectional Link Delay TLV . . . . . . . . . . . . . . 3 | |||
| 3.2. Min/Max Unidirectional Link Delay TLV . . . . . . . . . . 3 | 3.2. Min/Max Unidirectional Link Delay TLV . . . . . . . . . . 3 | |||
| 3.3. Unidirectional Delay Variation TLV . . . . . . . . . . . 4 | 3.3. Unidirectional Delay Variation TLV . . . . . . . . . . . 4 | |||
| 3.4. Unidirectional Link Loss TLV . . . . . . . . . . . . . . 4 | 3.4. Unidirectional Link Loss TLV . . . . . . . . . . . . . . 4 | |||
| 3.5. Unidirectional Residual Bandwidth TLV . . . . . . . . . . 5 | 3.5. Unidirectional Residual Bandwidth TLV . . . . . . . . . . 5 | |||
| 3.6. Unidirectional Available Bandwidth TLV . . . . . . . . . 5 | 3.6. Unidirectional Available Bandwidth TLV . . . . . . . . . 5 | |||
| 3.7. Unidirectional Utilized Bandwidth TLV . . . . . . . . . . 6 | 3.7. Unidirectional Utilized Bandwidth TLV . . . . . . . . . . 6 | |||
| 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | 4. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | |||
| 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 | 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 | 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 | 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 | 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 8.1. Normative References . . . . . . . . . . . . . . . . . . 8 | 8.1. Normative References . . . . . . . . . . . . . . . . . . 8 | |||
| 8.2. Informative References . . . . . . . . . . . . . . . . . 8 | 8.2. Informative References . . . . . . . . . . . . . . . . . 8 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 | |||
| 1. Introduction | 1. Introduction | |||
| BGP-LS ([RFC7752]) defines NLRI and attributes in order to carry | BGP-LS ([RFC7752]) defines NLRI and attributes in order to carry | |||
| link-state information. New BGP-LS Link-Attribute TLVs are required | link-state information. New BGP-LS Link-Attribute TLVs are required | |||
| in order to carry the Traffic Engineering Metric Extensions defined | in order to carry the Traffic Engineering Metric Extensions defined | |||
| skipping to change at page 6, line 49 ¶ | skipping to change at page 6, line 49 ¶ | |||
| Type: 1120 | Type: 1120 | |||
| Length: 4. | Length: 4. | |||
| 4. Security Considerations | 4. Security Considerations | |||
| Procedures and protocol extensions defined in this document do not | Procedures and protocol extensions defined in this document do not | |||
| affect the BGP security model. See the 'Security Considerations' | affect the BGP security model. See the 'Security Considerations' | |||
| section of [RFC4271] for a discussion of BGP security. Also refer to | section of [RFC4271] for a discussion of BGP security. Also refer to | |||
| [RFC4272] and [RFC6952] for analysis of security issues for BGP. | [RFC4272] and [RFC6952] for analysis of security issues for BGP. | |||
| Security considerations for acquiring and distributing BGP-LS | ||||
| information are discussed in [RFC7752]. | ||||
| The TLVs introduced in this document are used to propagate IGP | The TLVs introduced in this document are used to propagate IGP | |||
| defined information ([RFC7810] and [RFC7471].) These TLVs represent | defined information ([RFC7810] and [RFC7471].) These TLVs represent | |||
| the state and resources availability of the IGP link. The IGP | the state and resources availability of the IGP link. The IGP | |||
| instances originating these TLVs are assumed to have all the required | instances originating these TLVs are assumed to have all the required | |||
| security and authentication mechanism (as described in [RFC7810] and | security and authentication mechanism (as described in [RFC7810] and | |||
| [RFC7471]) in order to prevent any security issue when propagating | [RFC7471]) in order to prevent any security issue when propagating | |||
| the TLVs into BGP-LS. | the TLVs into BGP-LS. The advertisement of the link attribute | |||
| information defined in this document presents no additional risk | ||||
| beyond that associated with the existing set of link attribute | ||||
| information already supported in [RFC7752]. | ||||
| 5. IANA Considerations | 5. IANA Considerations | |||
| This document requests assigning code-points from the registry "BGP- | This document requests assigning code-points from the registry "BGP- | |||
| LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute | LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute | |||
| TLVs" for the new Link Attribute TLVs defined in the table below: | TLVs" for the new Link Attribute TLVs defined in the table below: | |||
| TLV code-point Value | TLV code-point Value | |||
| -------------------------------------------------------- | -------------------------------------------------------- | |||
| 1114 Unidirectional Link Delay | 1114 Unidirectional Link Delay | |||
| End of changes. 7 change blocks. | ||||
| 6 lines changed or deleted | 11 lines changed or added | |||
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||