Internet-Draft draft-geng-idr-bgp-ls-enhanced-detnet-00 July 2022
Geng, et al. Expires 12 January 2023 [Page]
Workgroup:
IDR Working Group
Internet-Draft:
draft-geng-idr-bgp-ls-enhanced-detnet-00
Published:
Intended Status:
Standards Track
Expires:
Authors:
X. Geng
Huawei
Z. Li
Huawei
T. Zhou
Huawei

BGP - Link State (BGP-LS) Advertisement of IGP DetNet Extensions

Abstract

This document defines extensions to BGP-LS to distribute the enhanced DetNet information

Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 12 January 2023.

▲

Table of Contents

1. Introduction

DetNet[RFC8655] provides the capability to carry specified unicast or multicast data flows with extremely low data loss rates and bounded end-to-end latency within a network domain. Three primary goals of DetNet QoS are defined in section 3.1 of [RFC8655];

This document defines extensions to BGP-LS to distribute the inforamtion for bounded latency(enhanced DetNet) .

BGP - Link State (BGP-LS)[RFC7752] defines Network Layer Reachability Information (NLRI) and attributes in order to carry link-state information. New BGP-LS Link Attribute TLVs for enhanced DetNet information are required in order to carry the Traffic Engineering Metric Extensions defined in [draft-geng-lsr-isis-extension-enhanced-detnet] .

2. Terminology

All the DetNet related terminologies used in this document conform to the [RFC8655].

3.1. Max DetNet Reservable Bandwidth Sub-TLV

This sub-TLV specifies the maximum amount of bandwidth that is reserved for DetNet on this link. Note that this value SHOULD be smaller than the value of Maximum Reservable Link Bandwidth [RFC5305].

The format of this sub-TLV is shown in the following diagram:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |            Type(TBD1)         |           Length(4)           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   RESERVED    |      Maximum DetNet Reservable Bandwidth      |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Type field is 2 octets in length, and the value is TBD2.

The Length field is 2 octets in length and its value is 4.

The RESERVED field is reserved for future use. It MUST be set to 0 when sent and MUST be ignored when received.

This Maximum DetNet Reservable Bandwidth field is 3 octets in length and presents the maximum bandwidth that may be reserved for DetNet. The units are bytes per second.

3.2. DetNet Available Bandwidth Sub-TLV

This sub-TLV specifies the available bandwidth that can be reserved for DetNet flow on this link for now. It is different from the Unreserved Bandwidth sub-TLV defined in [RFC5305] referring to section 3.3.

The format of this sub-TLV is shown in the following diagram:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |        Type(TBD2)             |       Length(4)               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   RESERVED    |          Available DetNet Bandwidth           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Type field is 2 octets in length, and the value is TBD1.

The Length field is 2 octets in length and its value is 4.

The RESERVED field is reserved for future use. It MUST be set to 0 when sent and MUST be ignored when received.

This Available DetNet Bandwidth field is 3 octets in length and presents the available bandwidth for DetNet in this link. The units are bytes per second.

3.3. DetNet Time Resource Sub-TLV

Time resource ID represent different types of identifiers used to indicate the capability of underlying bounded latency mechanisms. When the underlying technique is a logical queue based scheduling mechanisms, it represents a queue ID (There may different technologies for implementing logical queues, for example QoS, Flex-E, etc.). When the underlying technique is a time scheduling based mechanisms, it represents a time slot ID.(Cyclic queuing mechanisms could be considered as a special form of time scheduling, whose time slot is with equal length)

There are 2 types of Time Resource Sub-TLV: Time Resource for Logical queues sub-TLV and Time Resource for Time Scheduling sub-TLV:

The format of Time Resource for Logical queues sub-TLV is shown in the following diagram:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |        Type(TBD3)             |          Length(10)           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                    Time resource ID                           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   RESERVED   |             Queue Buffer Size                  |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   RESERVED   |           Queue Bandwidth Volume               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   RESERVED   |            Maximum Queuing Delay               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   RESERVED   |            Minimum Queuing Delay               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   RESERVED   |        Maximum Queuing Delay Variation         |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Type field is 2 octets in length, and the value is TBD3.

The Length field is 2 octets in length and its value is 24.

Time resource ID for Logical Queues is 3 octets in length, and specifies the identifier of a logical queue.

The queue The Queue Buffer Size field is 3 octets in length, and specifies the size of a queue with unit of bytes.

Queue Bandwidth Volume: is 3 octets in length, and carries maximum bandwidth could be put into the queue to provide the latency boundary. It is encoded in G bps encoded as an integer value.

Minimum Queuing Delay is 3 octets in length, and carries minimum queuing delay value (in microseconds) encoded as an integer value. Implementations may also add this to the value of Min Delay Unidirectional Link Delay Sub-TLV [RFC7471] in order to advertise the minimum delay of this link. Min Queuing Delay can be the same with the Max Queuing Delay.

Maximum Queuing Delay is 3 octets in length, and carries the maximum queuing delay value (in microseconds) encoded as an integer value. Implementations may also add this to the value of Max Delay Unidirectional Link Delay Sub-TLV[RFC7471] in order to advertise the maximum delay of this link.

Maximum Queuing Delay variation is 3 octets in length, and carries the maximum queuing delay variation value (in microseconds) encoded as an integer value.

The RESERVED field is reserved for future use. It MUST be set to 0 when sent and MUST be ignored when received.

The format of Time Resource for Time Scheduling sub-TLV is shown in the following diagram:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |        Type(TBD4)             |          Length(16)           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |           Time resource ID for Time Slot                      |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   RESERVED   |            Time Slot Length                    |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   RESERVED   |           Time Slot Start Time                 |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   RESERVED   |             Time Slot End Time                 |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Type field is 2 octets in length, and the value is TBD4.

The Length field is 2 octets in length and its value is 16.

Time Resource ID for Time Slot is 4 octets in length, and specifies the identifier of a time slot.

The Time Slot Length field is 3 octets in length, and specifies the length of time slot value (in microseconds) encoded as an integer value. When it is based on IEEE 802.1 Qch, time slot granularity presents cycle length.

The Time Slot Start Time field is 3 octets in length, and specifies the start time of the time slot in the time scheduling (in microseconds) encoded as an integer value.

The Time Slot End Time field is 3 octets in length, and specifies the end time of the time slot in the time scheduling (in microseconds) encoded as an integer value.

The RESERVED field is reserved for future use. It MUST be set to 0 when sent and MUST be ignored when received.

4. Node Attribute TLVs for Enhanced Detnet

4.1. DetNet Processing Delay Sub-TLV

In the scope of DetNet, packet processing delay, which begins after the packet goes into the input port and ends before the packet arrives the output buffer, can expected in a known range, and the value of the delay bound is specified in this sub-TLV, including:

The format of this sub-TLV is shown in the following diagram:

  0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |        Type(TBD5)             |          Length(10)           |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |   RESERVED    |      Minimum DetNet Processing Delay          |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |   RESERVED    |      Maximum DetNet Processing Delay          |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |   RESERVED    |   Maximum DetNet Processing Delay Variation   |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The Type field is 2 octets in length, and the value is TBD5.

The Length field is 2 octets in length and its value is 8.

The RESERVED field is reserved for future use. It MUST be set to 0 when sent and MUST be ignored when received.

The Minimum DetNet Processing Delay is 3 octets in length and presents the minimum delay for a DetNet flow in the device, excluding the queuing delay in output port. The units are microsecond.

The Maximum DetNet Processing Delay is 3 octets in length and presents the maximum delay for a DetNet flow in the device, excluding the queuing delay in output port. The units are microsecond.

The Maximum DetNet Processing Delay Variation is 3 octets in length and presents the maximum delay variation for a DetNet flow in the device, excluding the queuing delay in output port. The units are microsecond.

5. IANA Considerations

IANA has made assignments in the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs" registry for the new Link Attribute TLVs as listed below:

         Type        Description
         ----        ------------------------------
         TBD1         Maximum DetNet Reservable Bandwidth
         TBD2         DetNet Available Bandwidth
         TBD3         Time Resource ID for Logical Queue
         TBD4         Time Resource ID for Time Slot
         TBD5        Packet Processing Delay

6. Security Considerations

This document does not introduce security issues beyond those discussed in [RFC7471] and [RFC7810].

7. Acknowledgements

8. References

8.1. Normative References

[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC5786]
Aggarwal, R. and K. Kompella, "Advertising a Router's Local Addresses in OSPF Traffic Engineering (TE) Extensions", RFC 5786, DOI 10.17487/RFC5786, , <https://www.rfc-editor.org/info/rfc5786>.
[RFC7471]
Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. Previdi, "OSPF Traffic Engineering (TE) Metric Extensions", RFC 7471, DOI 10.17487/RFC7471, , <https://www.rfc-editor.org/info/rfc7471>.
[RFC7752]
Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and S. Ray, "North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP", RFC 7752, DOI 10.17487/RFC7752, , <https://www.rfc-editor.org/info/rfc7752>.
[RFC7810]
Previdi, S., Ed., Giacalone, S., Ward, D., Drake, J., and Q. Wu, "IS-IS Traffic Engineering (TE) Metric Extensions", RFC 7810, DOI 10.17487/RFC7810, , <https://www.rfc-editor.org/info/rfc7810>.
[RFC7981]
Ginsberg, L., Previdi, S., and M. Chen, "IS-IS Extensions for Advertising Router Information", RFC 7981, DOI 10.17487/RFC7981, , <https://www.rfc-editor.org/info/rfc7981>.
[RFC8655]
Finn, N., Thubert, P., Varga, B., and J. Farkas, "Deterministic Networking Architecture", RFC 8655, DOI 10.17487/RFC8655, , <https://www.rfc-editor.org/info/rfc8655>.

8.2. Informative References

[IEEE802.1Q-2014]
"MAC Bridges and VLANs (IEEE 802.1Q-2014)", .
[IEEE802.1Qch]
IEEE, "Cyclic Queuing and Forwarding", .
[IEEE802.1Qcr]
IEEE, "Asynchronous Traffic Shaping", .
[IIEEE802.1Qbv]
IEEE, "Enhancements for Scheduled Traffic", .
[RFC3630]
Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering (TE) Extensions to OSPF Version 2", RFC 3630, DOI 10.17487/RFC3630, , <https://www.rfc-editor.org/info/rfc3630>.
[RFC5305]
Li, T. and H. Smit, "IS-IS Extensions for Traffic Engineering", RFC 5305, DOI 10.17487/RFC5305, , <https://www.rfc-editor.org/info/rfc5305>.
[RFC5316]
Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316, , <https://www.rfc-editor.org/info/rfc5316>.
[RFC7310]
Lindsay, J. and H. Foerster, "RTP Payload Format for Standard apt-X and Enhanced apt-X Codecs", RFC 7310, DOI 10.17487/RFC7310, , <https://www.rfc-editor.org/info/rfc7310>.

Authors' Addresses

Xuesong Geng
Huawei
Zhenbin Li
Huawei
Tianran Zhou
Huawei