| < draft-bourbaki-6man-classless-ipv6-05.txt | draft-bourbaki-6man-classless-ipv6-06.txt > | |||
|---|---|---|---|---|
| 6man N. Bourbaki | 6man N. Bourbaki | |||
| Internet-Draft The Intertubes | Internet-Draft The Intertubes | |||
| Updates: 4291 (if approved) April 17, 2019 | Updates: 4291 (if approved) 18 April 2022 | |||
| Intended status: Standards Track | Intended status: Standards Track | |||
| Expires: October 19, 2019 | Expires: 20 October 2022 | |||
| IPv6 is Classless | IPv6 is Classless | |||
| draft-bourbaki-6man-classless-ipv6-05 | draft-bourbaki-6man-classless-ipv6-06 | |||
| Abstract | Abstract | |||
| Over the history of IPv6, various classful address models have been | Over the history of IPv6, various classful address models have been | |||
| proposed, none of which has withstood the test of time. The last | proposed, none of which has withstood the test of time. The last | |||
| remnant of IPv6 classful addressing is a rigid network interface | remnant of IPv6 classful addressing is a rigid network interface | |||
| identifier boundary at /64. This document removes the fixed position | identifier boundary at /64. This document removes the fixed position | |||
| of that boundary for interface addressing. | of that boundary for interface addressing. | |||
| Status of This Memo | Status of This Memo | |||
| skipping to change at page 1, line 35 ¶ | skipping to change at page 1, line 35 ¶ | |||
| 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 October 19, 2019. | This Internet-Draft will expire on 20 October 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2022 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/ | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | license-info) in effect on the date of publication of this document. | |||
| publication of this document. Please review these documents | Please review these documents carefully, as they describe your rights | |||
| carefully, as they describe your rights and restrictions with respect | and restrictions with respect to this document. Code Components | |||
| to this document. Code Components extracted from this document must | extracted from this document must include Revised BSD License text as | |||
| include Simplified BSD License text as described in Section 4.e of | described in Section 4.e of the Trust Legal Provisions and are | |||
| the Trust Legal Provisions and are provided without warranty as | provided without warranty as described in the Revised BSD License. | |||
| described in the Simplified BSD License. | ||||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 2. Suggested Reading . . . . . . . . . . . . . . . . . . . . . . 2 | 2. Suggested Reading . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 3. Problems Reinforced by Classful Addressing . . . . . . . . . 3 | 3. Problems Reinforced by Classful Addressing . . . . . . . . . 3 | |||
| 4. Identifier and Subnet Length Statements . . . . . . . . . . . 4 | 4. Identifier and Subnet Length Statements . . . . . . . . . . . 4 | |||
| 5. Recommendations . . . . . . . . . . . . . . . . . . . . . . . 4 | 5. Recommendations . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 | |||
| 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 | |||
| skipping to change at page 5, line 52 ¶ | skipping to change at page 5, line 52 ¶ | |||
| Chris Morrow <morrowc@ops-netman.net>, Google, Inc. | Chris Morrow <morrowc@ops-netman.net>, Google, Inc. | |||
| Job Snijders <job@net.net>, NTT Communications | Job Snijders <job@net.net>, NTT Communications | |||
| 9. References | 9. References | |||
| 9.1. Normative References | 9.1. Normative References | |||
| [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 | [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 | |||
| (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, | (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, | |||
| December 1998, <http://www.rfc-editor.org/info/rfc2460>. | December 1998, <https://www.rfc-editor.org/info/rfc2460>. | |||
| [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing | [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing | |||
| Architecture", RFC 4291, DOI 10.17487/RFC4291, February | Architecture", RFC 4291, DOI 10.17487/RFC4291, February | |||
| 2006, <http://www.rfc-editor.org/info/rfc4291>. | 2006, <https://www.rfc-editor.org/info/rfc4291>. | |||
| [RFC7217] Gont, F., "A Method for Generating Semantically Opaque | [RFC7217] Gont, F., "A Method for Generating Semantically Opaque | |||
| Interface Identifiers with IPv6 Stateless Address | Interface Identifiers with IPv6 Stateless Address | |||
| Autoconfiguration (SLAAC)", RFC 7217, | Autoconfiguration (SLAAC)", RFC 7217, | |||
| DOI 10.17487/RFC7217, April 2014, | DOI 10.17487/RFC7217, April 2014, | |||
| <http://www.rfc-editor.org/info/rfc7217>. | <https://www.rfc-editor.org/info/rfc7217>. | |||
| [RFC8064] Gont, F., Cooper, A., Thaler, D., and W. Liu, | [RFC8064] Gont, F., Cooper, A., Thaler, D., and W. Liu, | |||
| "Recommendation on Stable IPv6 Interface Identifiers", | "Recommendation on Stable IPv6 Interface Identifiers", | |||
| RFC 8064, DOI 10.17487/RFC8064, February 2017, | RFC 8064, DOI 10.17487/RFC8064, February 2017, | |||
| <http://www.rfc-editor.org/info/rfc8064>. | <https://www.rfc-editor.org/info/rfc8064>. | |||
| 9.2. Informative References | 9.2. Informative References | |||
| [I-D.hinden-6man-rfc2464bis] | [I-D.hinden-6man-rfc2464bis] | |||
| Crawford, M. and R. Hinden, "Transmission of IPv6 Packets | Crawford, M. and R. M. Hinden, "Transmission of IPv6 | |||
| over Ethernet Networks", draft-hinden-6man-rfc2464bis-02 | Packets over Ethernet Networks", Work in Progress, | |||
| (work in progress), March 2017. | Internet-Draft, draft-hinden-6man-rfc2464bis-02, 13 March | |||
| 2017, <https://www.ietf.org/archive/id/draft-hinden-6man- | ||||
| rfc2464bis-02.txt>. | ||||
| [I-D.ietf-6man-rfc4291bis] | [I-D.ietf-6man-rfc4291bis] | |||
| Hinden, R. and S. Deering, "IP Version 6 Addressing | Hinden, R. M. and S. E. Deering, "IP Version 6 Addressing | |||
| Architecture", draft-ietf-6man-rfc4291bis-09 (work in | Architecture", Work in Progress, Internet-Draft, draft- | |||
| progress), July 2017. | ietf-6man-rfc4291bis-09, 3 July 2017, | |||
| <https://www.ietf.org/archive/id/draft-ietf-6man- | ||||
| rfc4291bis-09.txt>. | ||||
| [I-D.jinmei-6man-prefix-clarify] | [I-D.jinmei-6man-prefix-clarify] | |||
| Jinmei, T., "Clarifications on On-link and Subnet IPv6 | Jinmei, T., "Clarifications on On-link and Subnet IPv6 | |||
| Prefixes", draft-jinmei-6man-prefix-clarify-00 (work in | Prefixes", Work in Progress, Internet-Draft, draft-jinmei- | |||
| progress), March 2017. | 6man-prefix-clarify-00, 13 March 2017, | |||
| <https://www.ietf.org/archive/id/draft-jinmei-6man-prefix- | ||||
| clarify-00.txt>. | ||||
| [RFC2450] Hinden, R., "Proposed TLA and NLA Assignment Rule", | [RFC2450] Hinden, R., "Proposed TLA and NLA Assignment Rule", | |||
| RFC 2450, DOI 10.17487/RFC2450, December 1998, | RFC 2450, DOI 10.17487/RFC2450, December 1998, | |||
| <http://www.rfc-editor.org/info/rfc2450>. | <https://www.rfc-editor.org/info/rfc2450>. | |||
| [RFC3587] Hinden, R., Deering, S., and E. Nordmark, "IPv6 Global | [RFC3587] Hinden, R., Deering, S., and E. Nordmark, "IPv6 Global | |||
| Unicast Address Format", RFC 3587, DOI 10.17487/RFC3587, | Unicast Address Format", RFC 3587, DOI 10.17487/RFC3587, | |||
| August 2003, <http://www.rfc-editor.org/info/rfc3587>. | August 2003, <https://www.rfc-editor.org/info/rfc3587>. | |||
| [RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing | [RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing | |||
| (CIDR): The Internet Address Assignment and Aggregation | (CIDR): The Internet Address Assignment and Aggregation | |||
| Plan", BCP 122, RFC 4632, DOI 10.17487/RFC4632, August | Plan", BCP 122, RFC 4632, DOI 10.17487/RFC4632, August | |||
| 2006, <http://www.rfc-editor.org/info/rfc4632>. | 2006, <https://www.rfc-editor.org/info/rfc4632>. | |||
| [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless | [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless | |||
| Address Autoconfiguration", RFC 4862, | Address Autoconfiguration", RFC 4862, | |||
| DOI 10.17487/RFC4862, September 2007, | DOI 10.17487/RFC4862, September 2007, | |||
| <http://www.rfc-editor.org/info/rfc4862>. | <https://www.rfc-editor.org/info/rfc4862>. | |||
| [RFC6164] Kohno, M., Nitzan, B., Bush, R., Matsuzaki, Y., Colitti, | [RFC6164] Kohno, M., Nitzan, B., Bush, R., Matsuzaki, Y., Colitti, | |||
| L., and T. Narten, "Using 127-Bit IPv6 Prefixes on Inter- | L., and T. Narten, "Using 127-Bit IPv6 Prefixes on Inter- | |||
| Router Links", RFC 6164, DOI 10.17487/RFC6164, April 2011, | Router Links", RFC 6164, DOI 10.17487/RFC6164, April 2011, | |||
| <http://www.rfc-editor.org/info/rfc6164>. | <https://www.rfc-editor.org/info/rfc6164>. | |||
| [RFC7136] Carpenter, B. and S. Jiang, "Significance of IPv6 | [RFC7136] Carpenter, B. and S. Jiang, "Significance of IPv6 | |||
| Interface Identifiers", RFC 7136, DOI 10.17487/RFC7136, | Interface Identifiers", RFC 7136, DOI 10.17487/RFC7136, | |||
| February 2014, <http://www.rfc-editor.org/info/rfc7136>. | February 2014, <https://www.rfc-editor.org/info/rfc7136>. | |||
| [RFC7608] Boucadair, M., Petrescu, A., and F. Baker, "IPv6 Prefix | [RFC7608] Boucadair, M., Petrescu, A., and F. Baker, "IPv6 Prefix | |||
| Length Recommendation for Forwarding", BCP 198, RFC 7608, | Length Recommendation for Forwarding", BCP 198, RFC 7608, | |||
| DOI 10.17487/RFC7608, July 2015, | DOI 10.17487/RFC7608, July 2015, | |||
| <http://www.rfc-editor.org/info/rfc7608>. | <https://www.rfc-editor.org/info/rfc7608>. | |||
| [RFC7707] Gont, F. and T. Chown, "Network Reconnaissance in IPv6 | [RFC7707] Gont, F. and T. Chown, "Network Reconnaissance in IPv6 | |||
| Networks", RFC 7707, DOI 10.17487/RFC7707, March 2016, | Networks", RFC 7707, DOI 10.17487/RFC7707, March 2016, | |||
| <http://www.rfc-editor.org/info/rfc7707>. | <https://www.rfc-editor.org/info/rfc7707>. | |||
| [RFC7721] Cooper, A., Gont, F., and D. Thaler, "Security and Privacy | [RFC7721] Cooper, A., Gont, F., and D. Thaler, "Security and Privacy | |||
| Considerations for IPv6 Address Generation Mechanisms", | Considerations for IPv6 Address Generation Mechanisms", | |||
| RFC 7721, DOI 10.17487/RFC7721, March 2016, | RFC 7721, DOI 10.17487/RFC7721, March 2016, | |||
| <http://www.rfc-editor.org/info/rfc7721>. | <https://www.rfc-editor.org/info/rfc7721>. | |||
| Author's Address | Author's Address | |||
| Nicolas Bourbaki | Nicolas Bourbaki | |||
| The Intertubes | The Intertubes | |||
| 42 Rue du Jour | 42 Rue du Jour | |||
| Sophia-Antipolis ::1 | ::1 Sophia-Antipolis | |||
| FR | France | |||
| Email: bourbaki@bogus.com | Email: bourbaki@bogus.com | |||
| End of changes. 23 change blocks. | ||||
| 37 lines changed or deleted | 41 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/ | ||||