draft-ietf-i2rs-rib-data-model-13.txt | draft-ietf-i2rs-rib-data-model-14.txt | |||
---|---|---|---|---|
skipping to change at page 1, line 18 ¶ | skipping to change at page 1, line 18 ¶ | |||
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 7, 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-13 | draft-ietf-i2rs-rib-data-model-14 | |||
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", "MAY", and "OPTIONAL" in this | |||
skipping to change at page 66, line 27 ¶ | skipping to change at page 66, line 27 ¶ | |||
7. Acknowledgements | 7. Acknowledgements | |||
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] | ||||
Bahadur, N., Kini, S., and J. Medved, "Routing Information | ||||
Base Info Model", draft-ietf-i2rs-rib-info-model-16 (work | ||||
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>. | |||
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security | [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security | |||
skipping to change at page 67, line 28 ¶ | skipping to change at page 67, line 32 ¶ | |||
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 | |||
[I-D.ietf-i2rs-rib-info-model] | ||||
Bahadur, N., Kini, S., and J. Medved, "Routing Information | ||||
Base Info Model", draft-ietf-i2rs-rib-info-model-16 (work | ||||
in progress), May 2018. | ||||
[I-D.ietf-i2rs-usecase-reqs-summary] | [I-D.ietf-i2rs-usecase-reqs-summary] | |||
Hares, S. and M. Chen, "Summary of I2RS Use Case | Hares, S. and M. Chen, "Summary of I2RS Use Case | |||
Requirements", draft-ietf-i2rs-usecase-reqs-summary-03 | Requirements", draft-ietf-i2rs-usecase-reqs-summary-03 | |||
(work in progress), November 2016. | (work in progress), November 2016. | |||
[RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. | [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. | |||
Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, | Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, | |||
DOI 10.17487/RFC2784, March 2000, | DOI 10.17487/RFC2784, March 2000, | |||
<https://www.rfc-editor.org/info/rfc2784>. | <https://www.rfc-editor.org/info/rfc2784>. | |||
End of changes. 3 change blocks. | ||||
6 lines changed or deleted | 6 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/ |