| rfc8992v2.txt | rfc8992.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) S. Jiang, Ed. | Internet Engineering Task Force (IETF) S. Jiang, Ed. | |||
| Request for Comments: 8992 Huawei Technologies Co., Ltd | Request for Comments: 8992 Huawei Technologies Co., Ltd | |||
| Category: Informational Z. Du | Category: Informational Z. Du | |||
| ISSN: 2070-1721 China Mobile | ISSN: 2070-1721 China Mobile | |||
| B. Carpenter | B. Carpenter | |||
| Univ. of Auckland | Univ. of Auckland | |||
| Q. Sun | Q. Sun | |||
| China Telecom | China Telecom | |||
| April 2021 | May 2021 | |||
| Autonomic IPv6 Edge Prefix Management in Large-Scale Networks | Autonomic IPv6 Edge Prefix Management in Large-Scale Networks | |||
| Abstract | Abstract | |||
| This document defines two autonomic technical objectives for IPv6 | This document defines two autonomic technical objectives for IPv6 | |||
| prefix management at the edge of large-scale ISP networks, with an | prefix management at the edge of large-scale ISP networks, with an | |||
| extension to support IPv4 prefixes. An important purpose of this | extension to support IPv4 prefixes. An important purpose of this | |||
| document is to use it for validation of the design of various | document is to use it for validation of the design of various | |||
| components of the Autonomic Networking Infrastructure. | components of the Autonomic Networking Infrastructure. | |||
| skipping to change at line 462 ¶ | skipping to change at line 462 ¶ | |||
| requirements. However, the logging and reporting process is out of | requirements. However, the logging and reporting process is out of | |||
| scope for this document. | scope for this document. | |||
| 5. Autonomic Prefix Management Objectives | 5. Autonomic Prefix Management Objectives | |||
| This section defines the GRASP technical objective options that are | This section defines the GRASP technical objective options that are | |||
| used to support autonomic prefix management. | used to support autonomic prefix management. | |||
| 5.1. Edge Prefix Objective Option | 5.1. Edge Prefix Objective Option | |||
| The PrefixManager Objective option is a GRASP objective option | The PrefixManager Objective option is a GRASP Objective option | |||
| conforming to the GRASP specification [RFC8990]. Its name is | conforming to the GRASP specification [RFC8990]. Its name is | |||
| "PrefixManager" (see Section 8), and it carries the following data | "PrefixManager" (see Section 8), and it carries the following data | |||
| items as its value: the prefix length and the actual prefix bits. | items as its value: the prefix length and the actual prefix bits. | |||
| Since GRASP is based on CBOR (Concise Binary Object Representation) | Since GRASP is based on CBOR (Concise Binary Object Representation) | |||
| [RFC8949], the format of the PrefixManager Objective option is | [RFC8949], the format of the PrefixManager Objective option is | |||
| described in the Concise Data Definition Language (CDDL) [RFC8610] as | described in the Concise Data Definition Language (CDDL) [RFC8610] as | |||
| follows: | follows: | |||
| objective = ["PrefixManager", objective-flags, loop-count, | objective = ["PrefixManager", objective-flags, loop-count, | |||
| [length, ?prefix]] | [length, ?prefix]] | |||
| skipping to change at line 665 ¶ | skipping to change at line 665 ¶ | |||
| "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", | "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", | |||
| RFC 8415, DOI 10.17487/RFC8415, November 2018, | RFC 8415, DOI 10.17487/RFC8415, November 2018, | |||
| <https://www.rfc-editor.org/info/rfc8415>. | <https://www.rfc-editor.org/info/rfc8415>. | |||
| [RFC8610] Birkholz, H., Vigano, C., and C. Bormann, "Concise Data | [RFC8610] Birkholz, H., Vigano, C., and C. Bormann, "Concise Data | |||
| Definition Language (CDDL): A Notational Convention to | Definition Language (CDDL): A Notational Convention to | |||
| Express Concise Binary Object Representation (CBOR) and | Express Concise Binary Object Representation (CBOR) and | |||
| JSON Data Structures", RFC 8610, DOI 10.17487/RFC8610, | JSON Data Structures", RFC 8610, DOI 10.17487/RFC8610, | |||
| June 2019, <https://www.rfc-editor.org/info/rfc8610>. | June 2019, <https://www.rfc-editor.org/info/rfc8610>. | |||
| [RFC8990] Bormann, C., Carpenter, B., Ed., and B. Liu, Ed., "A | [RFC8990] Bormann, C., Carpenter, B., Ed., and B. Liu, Ed., "GeneRic | |||
| GeneRic Autonomic Signaling Protocol (GRASP)", RFC 8990, | Autonomic Signaling Protocol (GRASP)", RFC 8990, | |||
| DOI 10.17487/RFC8990, April 2021, | DOI 10.17487/RFC8990, May 2021, | |||
| <https://www.rfc-editor.org/info/rfc8990>. | <https://www.rfc-editor.org/info/rfc8990>. | |||
| [RFC8994] Eckert, T., Ed., Behringer, M., Ed., and S. Bjarnason, "An | [RFC8994] Eckert, T., Ed., Behringer, M., Ed., and S. Bjarnason, "An | |||
| Autonomic Control Plane (ACP)", RFC 8994, | Autonomic Control Plane (ACP)", RFC 8994, | |||
| DOI 10.17487/RFC8994, April 2021, | DOI 10.17487/RFC8994, May 2021, | |||
| <https://www.rfc-editor.org/info/rfc8994>. | <https://www.rfc-editor.org/info/rfc8994>. | |||
| [RFC8995] Pritikin, M., Richardson, M., Eckert, T., Behringer, M., | [RFC8995] Pritikin, M., Richardson, M., Eckert, T., Behringer, M., | |||
| and K. Watsen, "Bootstrapping Remote Secure Key | and K. Watsen, "Bootstrapping Remote Secure Key | |||
| Infrastructure (BRSKI)", RFC 8995, DOI 10.17487/RFC8995, | Infrastructure (BRSKI)", RFC 8995, DOI 10.17487/RFC8995, | |||
| April 2021, <https://www.rfc-editor.org/info/rfc8995>. | May 2021, <https://www.rfc-editor.org/info/rfc8995>. | |||
| 9.2. Informative References | 9.2. Informative References | |||
| [CORE-YANG-CBOR] | [CORE-YANG-CBOR] | |||
| Veillette, M., Ed., Petrov, I., Ed., and A. Pelov, "CBOR | Veillette, M., Ed., Petrov, I., Ed., and A. Pelov, "CBOR | |||
| Encoding of Data Modeled with YANG", Work in Progress, | Encoding of Data Modeled with YANG", Work in Progress, | |||
| Internet-Draft, draft-ietf-core-yang-cbor-15, 24 January | Internet-Draft, draft-ietf-core-yang-cbor-15, 24 January | |||
| 2021, <https://tools.ietf.org/html/draft-ietf-core-yang- | 2021, <https://tools.ietf.org/html/draft-ietf-core-yang- | |||
| cbor-15>. | cbor-15>. | |||
| [DHCP-YANG-MODEL] | [DHCP-YANG-MODEL] | |||
| Liu, B., Ed., Lou, K., and C. Chen, "Yang Data Model for | Liu, B., Ed., Lou, K., and C. Chen, "Yang Data Model for | |||
| DHCP Protocol", Work in Progress, Internet-Draft, draft- | DHCP Protocol", Work in Progress, Internet-Draft, draft- | |||
| liu-dhc-dhcp-yang-model-07, 11 October 2018, | liu-dhc-dhcp-yang-model-07, 12 October 2018, | |||
| <https://tools.ietf.org/html/draft-liu-dhc-dhcp-yang- | <https://tools.ietf.org/html/draft-liu-dhc-dhcp-yang- | |||
| model-07>. | model-07>. | |||
| [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G. | [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G. | |||
| J., and E. Lear, "Address Allocation for Private | J., and E. Lear, "Address Allocation for Private | |||
| Internets", BCP 5, RFC 1918, DOI 10.17487/RFC1918, | Internets", BCP 5, RFC 1918, DOI 10.17487/RFC1918, | |||
| February 1996, <https://www.rfc-editor.org/info/rfc1918>. | February 1996, <https://www.rfc-editor.org/info/rfc1918>. | |||
| [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, | [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, | |||
| "Remote Authentication Dial In User Service (RADIUS)", | "Remote Authentication Dial In User Service (RADIUS)", | |||
| skipping to change at line 743 ¶ | skipping to change at line 743 ¶ | |||
| Datastores over RESTCONF", RFC 8650, DOI 10.17487/RFC8650, | Datastores over RESTCONF", RFC 8650, DOI 10.17487/RFC8650, | |||
| November 2019, <https://www.rfc-editor.org/info/rfc8650>. | November 2019, <https://www.rfc-editor.org/info/rfc8650>. | |||
| [RFC8949] Bormann, C. and P. Hoffman, "Concise Binary Object | [RFC8949] Bormann, C. and P. Hoffman, "Concise Binary Object | |||
| Representation (CBOR)", STD 94, RFC 8949, | Representation (CBOR)", STD 94, RFC 8949, | |||
| DOI 10.17487/RFC8949, December 2020, | DOI 10.17487/RFC8949, December 2020, | |||
| <https://www.rfc-editor.org/info/rfc8949>. | <https://www.rfc-editor.org/info/rfc8949>. | |||
| [RFC8993] Behringer, M., Ed., Carpenter, B., Eckert, T., Ciavaglia, | [RFC8993] Behringer, M., Ed., Carpenter, B., Eckert, T., Ciavaglia, | |||
| L., and J. Nobre, "A Reference Model for Autonomic | L., and J. Nobre, "A Reference Model for Autonomic | |||
| Networking", RFC 8993, DOI 10.17487/RFC8993, April 2021, | Networking", RFC 8993, DOI 10.17487/RFC8993, May 2021, | |||
| <https://www.rfc-editor.org/info/rfc8993>. | <https://www.rfc-editor.org/info/rfc8993>. | |||
| Appendix A. Deployment Overview | Appendix A. Deployment Overview | |||
| This appendix includes logical deployment models and explanations of | This appendix includes logical deployment models and explanations of | |||
| the target deployment models. Its purpose is to help in | the target deployment models. Its purpose is to help in | |||
| understanding the mechanism described in this document. | understanding the mechanism described in this document. | |||
| This appendix includes two subsections: Appendix A.1 for the two most | This appendix includes two subsections: Appendix A.1 for the two most | |||
| common DHCP deployment models and Appendix A.2 for the PD deployment | common DHCP deployment models and Appendix A.2 for the PD deployment | |||
| End of changes. 7 change blocks. | ||||
| 9 lines changed or deleted | 9 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||