< draft-geng-detnet-info-distribution-03.txt   draft-geng-detnet-info-distribution-04.txt >
Interdomain Routing Working Group X. Geng Interdomain Routing Working Group X. Geng
Internet-Draft M. Chen Internet-Draft M. Chen
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: April 25, 2019 Z. Li Expires: January 9, 2020 Z. Li
F. Qin
China Mobile China Mobile
October 22, 2018 L. Qiang
July 8, 2019
IGP-TE Extensions for DetNet Information Distribution IGP-TE Extensions for DetNet Information Distribution
draft-geng-detnet-info-distribution-03 draft-geng-detnet-info-distribution-04
Abstract Abstract
This document extends the IGP-TE, including OSPF-TE and ISIS-TE, to This document extends the IGP-TE, including OSPF-TE and ISIS-TE, to
support DetNet by specifying new information that can be placed in support DetNet by specifying new information that can be placed in
Link State Protocol Data Units (LSP). This information describes Link State Protocol Data Units (LSP). This information describes
additional details regarding the state of the network that are useful additional details regarding the state of the network that are useful
for DetNet computations. for DetNet computations.
Requirements Language Requirements Language
skipping to change at page 1, line 42 skipping to change at page 1, line 44
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 25, 2019. This Internet-Draft will expire on January 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 37 skipping to change at page 2, line 42
3.2.4. Queuing Algorithm Capability Sub-TLV . . . . . . . . 9 3.2.4. Queuing Algorithm Capability Sub-TLV . . . . . . . . 9
3.2.5. DetNet Queue Sub-TLV . . . . . . . . . . . . . . . . 10 3.2.5. DetNet Queue Sub-TLV . . . . . . . . . . . . . . . . 10
4. DetNet Extensions to ISIS TE . . . . . . . . . . . . . . . . 12 4. DetNet Extensions to ISIS TE . . . . . . . . . . . . . . . . 12
4.1. DetNet Node Attributes Advertisement . . . . . . . . . . 12 4.1. DetNet Node Attributes Advertisement . . . . . . . . . . 12
4.1.1. DetNet Processing Delay Sub-TLV . . . . . . . . . . . 12 4.1.1. DetNet Processing Delay Sub-TLV . . . . . . . . . . . 12
4.1.2. PREOF Capability Sub-TLV . . . . . . . . . . . . . . 13 4.1.2. PREOF Capability Sub-TLV . . . . . . . . . . . . . . 13
4.2. DetNet Link Attributes Advertisement . . . . . . . . . . 14 4.2. DetNet Link Attributes Advertisement . . . . . . . . . . 14
4.2.1. Max DetNet Reservable Bandwidth Sub-TLV . . . . . . . 14 4.2.1. Max DetNet Reservable Bandwidth Sub-TLV . . . . . . . 14
4.2.2. DetNet Available Bandwidth Sub-TLV . . . . . . . . . 15 4.2.2. DetNet Available Bandwidth Sub-TLV . . . . . . . . . 15
4.2.3. PREOF Capability Sub-TLV . . . . . . . . . . . . . . 16 4.2.3. PREOF Capability Sub-TLV . . . . . . . . . . . . . . 16
4.2.4. Queuing Algorithm Capability Sub-TLV . . . . . . . . 16 4.2.4. Queuing Algorithm Capability Sub-TLV . . . . . . . . 17
4.2.5. DetNet Queue Sub-TLV . . . . . . . . . . . . . . . . 17 4.2.5. DetNet Queue Sub-TLV . . . . . . . . . . . . . . . . 17
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
5.1. Sub-TLVs for OSPF Node Attribute TLV . . . . . . . . . . 19 5.1. Sub-TLVs for OSPF Node Attribute TLV . . . . . . . . . . 19
5.2. Sub-TLVs for OSPF Link TLV . . . . . . . . . . . . . . . 19 5.2. Sub-TLVs for OSPF Link TLV . . . . . . . . . . . . . . . 19
5.3. Sub-TLVs for ISIS Router Capability TLV . . . . . . . . . 20 5.3. Sub-TLVs for ISIS Router Capability TLV . . . . . . . . . 20
5.4. Sub-TLVs for IS-IS TLVs 22, 23, 141, 222, and 223 . . . 20 5.4. Sub-TLVs for IS-IS TLVs 22, 23, 141, 222, and 223 . . . 20
6. Security Considerations . . . . . . . . . . . . . . . . . . . 20 6. Security Considerations . . . . . . . . . . . . . . . . . . . 20
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
8.1. Normative References . . . . . . . . . . . . . . . . . . 20 8.1. Normative References . . . . . . . . . . . . . . . . . . 20
skipping to change at page 6, line 31 skipping to change at page 6, line 31
The Flags field is 1 octet in length, and it is designed as follows: The Flags field is 1 octet in length, and it is designed as follows:
0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|R|E|O| | |R|E|O| |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
where: where:
o R-flag: replication-capability flag, which indicates whether a o R-flag: replication-capability flag, which indicates whether a
link has the packet replication capability. node has the packet replication capability.
o E-flag: elimination-capability flag, which indicates whether a o E-flag: elimination-capability flag, which indicates whether a
link has the packet elimination capability node has the packet elimination capability
o O-flag: in-order-capability, which indicates whether a LTP has the o O-flag: in-order-capability, which indicates whether a LTP has the
in-order delivery capability in-order delivery capability
Maximum out-of-order Packet Number field is 3 octet in length, and Maximum out-of-order Packet Number field is 3 octet in length, and
presents the maximum number of out-of-order packets that this link presents the maximum number of out-of-order packets that this link
can support, it depends on the reserved buffer size for packet can support, it depends on the reserved buffer size for packet
reordering. This value is valid only when the O-flag is set. reordering. This value is valid only when the O-flag is set.
Editor' note: Maximum Replicated Copies number may be added in the
future version.
3.2. DetNet Link Attributtes Advertisement 3.2. DetNet Link Attributtes Advertisement
New OSPF DetNet sub-TLVs for Link TLV are defined to distribute New OSPF DetNet sub-TLVs for Link TLV are defined to distribute
DetNet information of a link. These sub-TLVs include: DetNet information of a link. These sub-TLVs include:
______________________________________________________________ ______________________________________________________________
| Type | Length | Value | | Type | Length | Value |
|------------------------------------------------------------| |------------------------------------------------------------|
| TBD2 | 4 | Max DetNet Reservable Bandwidth | | TBD2 | 4 | Max DetNet Reservable Bandwidth |
| TBD3 | 4 | DetNet Available Bandwidth | | TBD3 | 4 | DetNet Available Bandwidth |
skipping to change at page 14, line 19 skipping to change at page 14, line 19
The Flags field is 1 octet in length, and it is designed as follows: The Flags field is 1 octet in length, and it is designed as follows:
0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|R|E|O| | |R|E|O| |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
where: where:
o R-flag: replication-capability flag, which indicates whether a o R-flag: replication-capability flag, which indicates whether a
link has the packet replication capability. node has the packet replication capability.
o E-flag: elimination-capability flag, which indicates whether a o E-flag: elimination-capability flag, which indicates whether a
link has the packet elimination capability node has the packet elimination capability
o O-flag: in-order-capability, which indicates whether a LTP has the o O-flag: in-order-capability, which indicates whether a LTP has the
in-order delivery capability in-order delivery capability
Maximum out-of-order Packet Number field is 3 octets in length and Maximum out-of-order Packet Number field is 3 octets in length and
presents the maximum number of out-of-order packets that this link presents the maximum number of out-of-order packets that this link
can support, it depends on the reserved buffer size for packet can support, it depends on the reserved buffer size for packet
reordering. This value is valid only when the O-flag is set. reordering. This value is valid only when the O-flag is set.
Editor' note: Maximum Replicated Copies number may be added in the
future version.
4.2. DetNet Link Attributes Advertisement 4.2. DetNet Link Attributes Advertisement
This document defines new IS-IS TE sub-TLVs that can be announced in This document defines new IS-IS TE sub-TLVs that can be announced in
the TLVs 22, 23, 141, 222, and 223 in order to distribute DetNet the TLVs 22, 23, 141, 222, and 223 in order to distribute DetNet
information. The sub-TLV extensions below build on the ones provided information. The sub-TLV extensions below build on the ones provided
in [RFC5305], [RFC5316]and [RFC7310] in [RFC5305], [RFC5316]and [RFC7310]
4.2.1. Max DetNet Reservable Bandwidth Sub-TLV 4.2.1. Max DetNet Reservable Bandwidth Sub-TLV
This sub-TLV specifies the maximum amount of bandwidth that is This sub-TLV specifies the maximum amount of bandwidth that is
skipping to change at page 16, line 48 skipping to change at page 16, line 48
link has the packet elimination capability link has the packet elimination capability
o O-flag: in-order-capability, which indicates whether a LTP has the o O-flag: in-order-capability, which indicates whether a LTP has the
in-order delivery capability in-order delivery capability
Maximum out-of-order Packet Number field is 3 octets in length and Maximum out-of-order Packet Number field is 3 octets in length and
presents the maximum number of out-of-order packets that this link presents the maximum number of out-of-order packets that this link
can support, it depends on the reserved buffer size for packet can support, it depends on the reserved buffer size for packet
reordering. This value is valid only when the O-flag is set. reordering. This value is valid only when the O-flag is set.
Editor' note: Maximum Replicated Copies number may be added in the
future version.
4.2.4. Queuing Algorithm Capability Sub-TLV 4.2.4. Queuing Algorithm Capability Sub-TLV
This sub-TLV specifies queuing management algorithms capabilities to This sub-TLV specifies queuing management algorithms capabilities to
gaurante bounded queuing latency [I-D.finn-detnet-bounded-latency]. gaurante bounded queuing latency [I-D.finn-detnet-bounded-latency].
The format of this sub-TLV is shown in the following diagram: The format of this sub-TLV is shown in the following diagram:
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 20, line 40 skipping to change at page 20, line 40
This document does not introduce security issues beyond those This document does not introduce security issues beyond those
discussed in [RFC7471] and [RFC7810]. discussed in [RFC7471] and [RFC7810].
7. Acknowledgements 7. Acknowledgements
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.finn-detnet-bounded-latency] [I-D.finn-detnet-bounded-latency]
Finn, N., Boudec, J., Mohammadpour, E., Varga, B., and J. Finn, N., Boudec, J., Mohammadpour, E., Zhang, J., Varga,
Farkas, "DetNet Bounded Latency", draft-finn-detnet- B., and J. Farkas, "DetNet Bounded Latency", draft-finn-
bounded-latency-01 (work in progress), July 2018. detnet-bounded-latency-04 (work in progress), June 2019.
[I-D.ietf-detnet-architecture] [I-D.ietf-detnet-architecture]
Finn, N., Thubert, P., Varga, B., and J. Farkas, Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", draft-ietf- "Deterministic Networking Architecture", draft-ietf-
detnet-architecture-08 (work in progress), September 2018. detnet-architecture-13 (work in progress), May 2019.
[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,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5786] Aggarwal, R. and K. Kompella, "Advertising a Router's [RFC5786] Aggarwal, R. and K. Kompella, "Advertising a Router's
Local Addresses in OSPF Traffic Engineering (TE) Local Addresses in OSPF Traffic Engineering (TE)
Extensions", RFC 5786, DOI 10.17487/RFC5786, March 2010, Extensions", RFC 5786, DOI 10.17487/RFC5786, March 2010,
<https://www.rfc-editor.org/info/rfc5786>. <https://www.rfc-editor.org/info/rfc5786>.
skipping to change at page 21, line 31 skipping to change at page 21, line 31
for Advertising Router Information", RFC 7981, for Advertising Router Information", RFC 7981,
DOI 10.17487/RFC7981, October 2016, DOI 10.17487/RFC7981, October 2016,
<https://www.rfc-editor.org/info/rfc7981>. <https://www.rfc-editor.org/info/rfc7981>.
8.2. Informative References 8.2. Informative References
[IEEE802.1Q-2014] [IEEE802.1Q-2014]
"MAC Bridges and VLANs (IEEE 802.1Q-2014)", 2014. "MAC Bridges and VLANs (IEEE 802.1Q-2014)", 2014.
[IEEE802.1Qch] [IEEE802.1Qch]
"Cyclic Queuing and Forwarding", 2016. IEEE, "Cyclic Queuing and Forwarding", 2016.
[IEEE802.1Qcr] [IEEE802.1Qcr]
"Asynchronous Traffic Shaping", 2016. IEEE, "Asynchronous Traffic Shaping", 2016.
[IIEEE802.1Qbv] [IIEEE802.1Qbv]
"Enhancements for Scheduled Traffic", 2016. IEEE, "Enhancements for Scheduled Traffic", 2016.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, (TE) Extensions to OSPF Version 2", RFC 3630,
DOI 10.17487/RFC3630, September 2003, DOI 10.17487/RFC3630, September 2003,
<https://www.rfc-editor.org/info/rfc3630>. <https://www.rfc-editor.org/info/rfc3630>.
[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
Engineering", RFC 5305, DOI 10.17487/RFC5305, October Engineering", RFC 5305, DOI 10.17487/RFC5305, October
2008, <https://www.rfc-editor.org/info/rfc5305>. 2008, <https://www.rfc-editor.org/info/rfc5305>.
skipping to change at page 22, line 22 skipping to change at page 22, line 22
Xuesong Geng Xuesong Geng
Huawei Huawei
Email: gengxuesong@huawei.com Email: gengxuesong@huawei.com
Mach(Guoyi) Chen Mach(Guoyi) Chen
Huawei Huawei
Email: mach.chen@huawei.com Email: mach.chen@huawei.com
Zhenqiang Zhenqiang Li
China Mobile China Mobile
Email: lizhenqiang@chinamobile.com Email: lizhenqiang@chinamobile.com
Fengwei Qin
China Mobile
Email: qinfengwei@chinamobile.com
Li Qiang
 End of changes. 20 change blocks. 
18 lines changed or deleted 29 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/