draft-ietf-idr-te-pm-bgp-16.txt   draft-ietf-idr-te-pm-bgp-17.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: June 16, 2019 Q. Wu Expires: June 17, 2019 Q. Wu
Huawei Huawei
J. Tantsura J. Tantsura
Apstra, Inc. Apstra, Inc.
C. Filsfils C. Filsfils
Cisco Systems, Inc. Cisco Systems, Inc.
December 13, 2018 December 14, 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-16 draft-ietf-idr-te-pm-bgp-17
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 the IS-IS and OSPF Traffic Engineering Extensions defined in the IS-IS and OSPF
protocols. protocols.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 June 16, 2019. This Internet-Draft will expire on June 17, 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 21 skipping to change at page 2, line 21
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Link Attribute TLVs for TE Metric Extensions . . . . . . . . 2 2. Link Attribute TLVs for TE Metric Extensions . . . . . . . . 2
2.1. Unidirectional Link Delay TLV . . . . . . . . . . . . . . 3 2.1. Unidirectional Link Delay TLV . . . . . . . . . . . . . . 3
2.2. Min/Max Unidirectional Link Delay TLV . . . . . . . . . . 3 2.2. Min/Max Unidirectional Link Delay TLV . . . . . . . . . . 3
2.3. Unidirectional Delay Variation TLV . . . . . . . . . . . 4 2.3. Unidirectional Delay Variation TLV . . . . . . . . . . . 4
2.4. Unidirectional Link Loss TLV . . . . . . . . . . . . . . 5 2.4. Unidirectional Link Loss TLV . . . . . . . . . . . . . . 5
2.5. Unidirectional Residual Bandwidth TLV . . . . . . . . . . 5 2.5. Unidirectional Residual Bandwidth TLV . . . . . . . . . . 5
2.6. Unidirectional Available Bandwidth TLV . . . . . . . . . 5 2.6. Unidirectional Available Bandwidth TLV . . . . . . . . . 5
2.7. Unidirectional Utilized Bandwidth TLV . . . . . . . . . . 6 2.7. Unidirectional Utilized Bandwidth TLV . . . . . . . . . . 6
3. Security Considerations . . . . . . . . . . . . . . . . . . . 6 2.8. Mappings to IGP Source sub-TLVs . . . . . . . . . . . . . 6
3. Security Considerations . . . . . . . . . . . . . . . . . . . 7
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 8
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Normative References . . . . . . . . . . . . . . . . . . 8 7.1. Normative References . . . . . . . . . . . . . . . . . . 8
7.2. Informative References . . . . . . . . . . . . . . . . . 8 7.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 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
in [I-D.ietf-lsr-isis-rfc7810bis] and [RFC7471]. in [I-D.ietf-lsr-isis-rfc7810bis] and [RFC7471].
2. Link Attribute TLVs for TE Metric Extensions 2. Link Attribute TLVs for TE Metric Extensions
skipping to change at page 6, line 44 skipping to change at page 6, line 44
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Figure 5 Figure 5
Type: 1120 Type: 1120
Length: 4. Length: 4.
2.8. Mappings to IGP Source sub-TLVs
This section documents the mappings between the Link Attribute TLVs
defined in this document and the corresponding advertisements sourced
by the IGPs.
For OSPFv2 and OSPFv3 the advertisements are defined in [RFC7471] .
For IS-IS the advertisements are defined in
[I-D.ietf-lsr-isis-rfc7810bis] .
+---------------------------------------+----------+----------------+
| Attribute Name | IS-IS | OSPFv2/OSPFv3 |
| | sub-TLV | sub-TLV |
+---------------------------------------+----------+----------------+
| Unidirectional Link Delay | 33 | 27 |
+---------------------------------------+----------+----------------+
| Min/Max Unidirectional Link Delay | 34 | 28 |
+---------------------------------------+----------+----------------+
| Unidirectional Delay Variation | 35 | 29 |
+---------------------------------------+----------+----------------+
| Unidirectional Link Loss | 36 | 30 |
+---------------------------------------+----------+----------------+
| Unidirectional Residual Bandwidth | 37 | 31 |
+---------------------------------------+----------+----------------+
| Unidirectional Available Bandwidth | 38 | 32 |
+---------------------------------------+----------+----------------+
| Unidirectional Bandwidth Utilization | 39 | 33 |
+---------------------------------------+----------+----------------+
3. Security Considerations 3. 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 Security considerations for acquiring and distributing BGP-LS
information are discussed in [RFC7752]. 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
 End of changes. 8 change blocks. 
8 lines changed or deleted 38 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/