draft-ietf-i2rs-rib-data-model-14.txt | draft-ietf-i2rs-rib-data-model-15.txt | |||
---|---|---|---|---|
Network Working Group L. Wang | Network Working Group L. Wang | |||
Internet-Draft Individual | Internet-Draft Individual | |||
Intended status: Standards Track M. Chen | Intended status: Standards Track M. Chen | |||
Expires: November 8, 2018 Huawei | Expires: November 15, 2018 Huawei | |||
A. Dass | A. Dass | |||
Ericsson | Ericsson | |||
H. Ananthakrishnan | H. Ananthakrishnan | |||
Packet Design | Packet Design | |||
S. Kini | S. Kini | |||
Individual | Individual | |||
N. Bahadur | N. Bahadur | |||
Bracket Computing | Bracket Computing | |||
May 7, 2018 | May 14, 2018 | |||
A YANG Data Model for Routing Information Base (RIB) | A YANG Data Model for Routing Information Base (RIB) | |||
draft-ietf-i2rs-rib-data-model-14 | draft-ietf-i2rs-rib-data-model-15 | |||
Abstract | Abstract | |||
This document defines a YANG data model for the Routing Information | This document defines a YANG data model for the Routing Information | |||
Base (RIB) that aligns with the I2RS RIB information model. | Base (RIB) that aligns with the I2RS RIB information model. | |||
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", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
document are to be interpreted as described in RFC 2119 [RFC2119]. | "OPTIONAL" in this document are to be interpreted as described in BCP | |||
14 [RFC2119] [RFC8174] when, and only when, they appear in all | ||||
capitals, as shown here. | ||||
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 | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
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 November 8, 2018. | This Internet-Draft will expire on November 15, 2018. | |||
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 13, line 21 ¶ | skipping to change at page 13, line 21 ¶ | |||
| | | | | +--rw ttl? uint8 | | | | | | +--rw ttl? uint8 | |||
| | | | | +--rw dscp? uint8 | | | | | | +--rw dscp? uint8 | |||
| | | | +--:(ipv6) | | | | | +--:(ipv6) | |||
| | | | +--rw src-ipv6-address inet:ipv6-address | | | | | +--rw src-ipv6-address inet:ipv6-address | |||
| | | | +--rw dest-ipv6-address inet:ipv6-address | | | | | +--rw dest-ipv6-address inet:ipv6-address | |||
| | | | +--rw next-header uint8 | | | | | +--rw next-header uint8 | |||
| | | | +--rw traffic-class? uint8 | | | | | +--rw traffic-class? uint8 | |||
| | | | +--rw flow-label? inet:ipv6-flow-label | | | | | +--rw flow-label? inet:ipv6-flow-label | |||
| | | | +--rw hop-limit? uint8 | | | | | +--rw hop-limit? uint8 | |||
| | | +--rw virtual-subnet-id uint32 | | | | +--rw virtual-subnet-id uint32 | |||
| | | +--rw flow-id? uint16 | | | | +--rw flow-id? uint8 | |||
| | +--:(vxlan) {vxlan-tunnel}? | | | +--:(vxlan) {vxlan-tunnel}? | |||
| | +--rw vxlan-header | | | +--rw vxlan-header | |||
| | +--rw (vxlan-type)? | | | +--rw (vxlan-type)? | |||
| | | +--:(ipv4) | | | | +--:(ipv4) | |||
| | | | +--rw src-ipv4-address inet:ipv4-address | | | | | +--rw src-ipv4-address inet:ipv4-address | |||
| | | | +--rw dest-ipv4-address inet:ipv4-address | | | | | +--rw dest-ipv4-address inet:ipv4-address | |||
| | | | +--rw protocol uint8 | | | | | +--rw protocol uint8 | |||
| | | | +--rw ttl? uint8 | | | | | +--rw ttl? uint8 | |||
| | | | +--rw dscp? uint8 | | | | | +--rw dscp? uint8 | |||
| | | +--:(ipv6) | | | | +--:(ipv6) | |||
skipping to change at page 66, line 29 ¶ | skipping to change at page 66, line 29 ¶ | |||
The authors would like to thank Chris Bowers, John Scudder, Tom | The authors would like to thank Chris Bowers, John Scudder, Tom | |||
Petch, Mike McBride and Ebben Aries for his review, suggestion and | Petch, Mike McBride and Ebben Aries for his review, suggestion and | |||
comments to this document. | comments to this document. | |||
8. References | 8. References | |||
8.1. Normative References | 8.1. Normative References | |||
[I-D.ietf-i2rs-rib-info-model] | [I-D.ietf-i2rs-rib-info-model] | |||
Bahadur, N., Kini, S., and J. Medved, "Routing Information | Bahadur, N., Kini, S., and J. Medved, "Routing Information | |||
Base Info Model", draft-ietf-i2rs-rib-info-model-16 (work | Base Info Model", draft-ietf-i2rs-rib-info-model-17 (work | |||
in progress), May 2018. | in progress), May 2018. | |||
[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>. | |||
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, | |||
DOI 10.17487/RFC3688, January 2004, | DOI 10.17487/RFC3688, January 2004, | |||
<https://www.rfc-editor.org/info/rfc3688>. | <https://www.rfc-editor.org/info/rfc3688>. | |||
skipping to change at page 67, line 21 ¶ | skipping to change at page 67, line 21 ¶ | |||
<https://www.rfc-editor.org/info/rfc6991>. | <https://www.rfc-editor.org/info/rfc6991>. | |||
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", | [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", | |||
RFC 7950, DOI 10.17487/RFC7950, August 2016, | RFC 7950, DOI 10.17487/RFC7950, August 2016, | |||
<https://www.rfc-editor.org/info/rfc7950>. | <https://www.rfc-editor.org/info/rfc7950>. | |||
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF | [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF | |||
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, | Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, | |||
<https://www.rfc-editor.org/info/rfc8040>. | <https://www.rfc-editor.org/info/rfc8040>. | |||
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | ||||
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | ||||
May 2017, <https://www.rfc-editor.org/info/rfc8174>. | ||||
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration | [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration | |||
Access Control Model", STD 91, RFC 8341, | Access Control Model", STD 91, RFC 8341, | |||
DOI 10.17487/RFC8341, March 2018, | DOI 10.17487/RFC8341, March 2018, | |||
<https://www.rfc-editor.org/info/rfc8341>. | <https://www.rfc-editor.org/info/rfc8341>. | |||
[RFC8344] Bjorklund, M., "A YANG Data Model for IP Management", | [RFC8344] Bjorklund, M., "A YANG Data Model for IP Management", | |||
RFC 8344, DOI 10.17487/RFC8344, March 2018, | RFC 8344, DOI 10.17487/RFC8344, March 2018, | |||
<https://www.rfc-editor.org/info/rfc8344>. | <https://www.rfc-editor.org/info/rfc8344>. | |||
8.2. Informative References | 8.2. Informative References | |||
End of changes. 8 change blocks. | ||||
8 lines changed or deleted | 14 lines changed or added | |||
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |