draft-ietf-6man-rfc6434-bis-07.txt   draft-ietf-6man-rfc6434-bis-08.txt 
Internet Engineering Task Force T. Chown Internet Engineering Task Force T. Chown
Internet-Draft Jisc Internet-Draft Jisc
Obsoletes: 6434 (if approved) J. Loughney Obsoletes: 6434 (if approved) J. Loughney
Intended status: Best Current Practice Intel Intended status: Best Current Practice Intel
Expires: September 4, 2018 T. Winters Expires: September 20, 2018 T. Winters
UNH-IOL UNH-IOL
March 3, 2018 March 19, 2018
IPv6 Node Requirements IPv6 Node Requirements
draft-ietf-6man-rfc6434-bis-07 draft-ietf-6man-rfc6434-bis-08
Abstract Abstract
This document defines requirements for IPv6 nodes. It is expected This document defines requirements for IPv6 nodes. It is expected
that IPv6 will be deployed in a wide range of devices and situations. that IPv6 will be deployed in a wide range of devices and situations.
Specifying the requirements for IPv6 nodes allows IPv6 to function Specifying the requirements for IPv6 nodes allows IPv6 to function
well and interoperate in a large number of situations and well and interoperate in a large number of situations and
deployments. deployments.
This document obsoletes RFC 6434, and in turn RFC 4294. This document obsoletes RFC 6434, and in turn RFC 4294.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 September 4, 2018. This Internet-Draft will expire on September 20, 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 3, line 23 skipping to change at page 3, line 23
13.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 21 13.1. Requirements . . . . . . . . . . . . . . . . . . . . . . 21
13.2. Transforms and Algorithms . . . . . . . . . . . . . . . 21 13.2. Transforms and Algorithms . . . . . . . . . . . . . . . 21
14. Router-Specific Functionality . . . . . . . . . . . . . . . . 22 14. Router-Specific Functionality . . . . . . . . . . . . . . . . 22
14.1. IPv6 Router Alert Option - RFC 2711 . . . . . . . . . . 22 14.1. IPv6 Router Alert Option - RFC 2711 . . . . . . . . . . 22
14.2. Neighbor Discovery for IPv6 - RFC 4861 . . . . . . . . . 22 14.2. Neighbor Discovery for IPv6 - RFC 4861 . . . . . . . . . 22
14.3. Stateful Address Autoconfiguration (DHCPv6) - RFC 3315 . 22 14.3. Stateful Address Autoconfiguration (DHCPv6) - RFC 3315 . 22
14.4. IPv6 Prefix Length Recommendation for Forwarding - BCP 14.4. IPv6 Prefix Length Recommendation for Forwarding - BCP
198 . . . . . . . . . . . . . . . . . . . . . . . . . . 23 198 . . . . . . . . . . . . . . . . . . . . . . . . . . 23
15. Constrained Devices . . . . . . . . . . . . . . . . . . . . . 23 15. Constrained Devices . . . . . . . . . . . . . . . . . . . . . 23
16. Network Management . . . . . . . . . . . . . . . . . . . . . 23 16. Network Management . . . . . . . . . . . . . . . . . . . . . 23
16.1. Management Information Base (MIB) Modules . . . . . . . 24 16.1. Management Information Base (MIB) Modules . . . . . . . 23
16.1.1. IP Forwarding Table MIB . . . . . . . . . . . . . . 24 16.1.1. IP Forwarding Table MIB . . . . . . . . . . . . . . 24
16.1.2. Management Information Base for the Internet 16.1.2. Management Information Base for the Internet
Protocol (IP) . . . . . . . . . . . . . . . . . . . 24 Protocol (IP) . . . . . . . . . . . . . . . . . . . 24
16.1.3. Interface MIB . . . . . . . . . . . . . . . . . . . 24 16.1.3. Interface MIB . . . . . . . . . . . . . . . . . . . 24
16.2. YANG Data Models . . . . . . . . . . . . . . . . . . . . 24 16.2. YANG Data Models . . . . . . . . . . . . . . . . . . . . 24
16.2.1. IP Management YANG Model . . . . . . . . . . . . . . 24 16.2.1. IP Management YANG Model . . . . . . . . . . . . . . 24
16.2.2. Interface Management YANG Model . . . . . . . . . . 24 16.2.2. Interface Management YANG Model . . . . . . . . . . 24
17. Security Considerations . . . . . . . . . . . . . . . . . . . 24 17. Security Considerations . . . . . . . . . . . . . . . . . . . 24
18. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 18. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
19. Authors and Acknowledgments . . . . . . . . . . . . . . . . . 25 19. Authors and Acknowledgments . . . . . . . . . . . . . . . . . 25
19.1. Authors and Acknowledgments (Current Document) . . . . . 25 19.1. Authors and Acknowledgments (Current Document) . . . . . 25
19.2. Authors and Acknowledgments from RFC 6434 . . . . . . . 25 19.2. Authors and Acknowledgments from RFC 6434 . . . . . . . 25
19.3. Authors and Acknowledgments from RFC 4294 . . . . . . . 25 19.3. Authors and Acknowledgments from RFC 4294 . . . . . . . 25
20. Appendix: Changes from RFC 6434 . . . . . . . . . . . . . . . 25 20. Appendix: Changes from RFC 6434 . . . . . . . . . . . . . . . 25
21. Appendix: Changes from RFC 4294 . . . . . . . . . . . . . . . 27 21. Appendix: Changes from RFC 4294 . . . . . . . . . . . . . . . 27
22. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 22. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
22.1. Normative References . . . . . . . . . . . . . . . . . . 28 22.1. Normative References . . . . . . . . . . . . . . . . . . 28
22.2. Informative References . . . . . . . . . . . . . . . . . 35 22.2. Informative References . . . . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
skipping to change at page 22, line 12 skipping to change at page 22, line 12
MUST conform to the requirements in [RFC8247] and/or any future MUST conform to the requirements in [RFC8247] and/or any future
updates or replacements to [RFC8247]. updates or replacements to [RFC8247].
14. Router-Specific Functionality 14. Router-Specific Functionality
This section defines general host considerations for IPv6 nodes that This section defines general host considerations for IPv6 nodes that
act as routers. Currently, this section does not discuss detailed act as routers. Currently, this section does not discuss detailed
routing-specific requirements. For the case of typical home routers, routing-specific requirements. For the case of typical home routers,
[RFC7084] defines basic requirements for customer edge routers. [RFC7084] defines basic requirements for customer edge routers.
Further recommendations on router-specific functionality can be found
in [I-D.ietf-v6ops-ipv6rtr-reqs].
14.1. IPv6 Router Alert Option - RFC 2711 14.1. IPv6 Router Alert Option - RFC 2711
The IPv6 Router Alert Option [RFC2711] is an optional IPv6 Hop-by-Hop The IPv6 Router Alert Option [RFC2711] is an optional IPv6 Hop-by-Hop
Header that is used in conjunction with some protocols (e.g., RSVP Header that is used in conjunction with some protocols (e.g., RSVP
[RFC2205] or Multicast Listener Discovery (MLDv2) [RFC3810]). The [RFC2205] or Multicast Listener Discovery (MLDv2) [RFC3810]). The
Router Alert option will need to be implemented whenever such Router Alert option will need to be implemented whenever such
protocols that mandate its use are implemented. See Section 5.11. protocols that mandate its use are implemented. See Section 5.11.
14.2. Neighbor Discovery for IPv6 - RFC 4861 14.2. Neighbor Discovery for IPv6 - RFC 4861
skipping to change at page 27, line 4 skipping to change at page 26, line 50
19. Added a Unique IPv6 Prefix per Host to support currently 19. Added a Unique IPv6 Prefix per Host to support currently
deployed IPv6 networks deployed IPv6 networks
20. Clarified RFC7066 was snapshot for 3GPP 20. Clarified RFC7066 was snapshot for 3GPP
21. Updated 4191 as a MUST, SHOULD for Type C Host as it helps solve 21. Updated 4191 as a MUST, SHOULD for Type C Host as it helps solve
multi-prefix problem multi-prefix problem
22. Removed IPv6 over ATM since there aren't many deployments 22. Removed IPv6 over ATM since there aren't many deployments
23. Added a note in Section 6.6 for RFC6724 Section 5.5/
23. Added a note in Section 6.6 for RFC6724 Section 5.5/
24. Added MUST for BCP 198 for forwarding IPv6 packets 24. Added MUST for BCP 198 for forwarding IPv6 packets
25. Added reference to draft-ietf-v6ops-ipv6rtr-reqs as it has more 25. Added reference to RFC8064 for stable address creation.
recommendations for a Router
26. Added reference to RFC8064 for stable address creation.
27. Added text on protection from excessive EH options 26. Added text on protection from excessive EH options
28. Added text on dangers of 1280 MTU UDP, esp. wrt DNS traffic 27. Added text on dangers of 1280 MTU UDP, esp. wrt DNS traffic
29. Added text to clarify RFC8200 behaviour for unrecognized EHs or 28. Added text to clarify RFC8200 behaviour for unrecognized EHs or
unrecognized ULPs unrecognized ULPs
30. Removed dated email addresses from design team acknowledgements 29. Removed dated email addresses from design team acknowledgements
for RFC 4294. for RFC 4294.
21. Appendix: Changes from RFC 4294 21. Appendix: Changes from RFC 4294
There have been many editorial clarifications as well as significant There have been many editorial clarifications as well as significant
additions and updates. While this section highlights some of the additions and updates. While this section highlights some of the
changes, readers should not rely on this section for a comprehensive changes, readers should not rely on this section for a comprehensive
list of all changes. list of all changes.
1. Updated the Introduction to indicate that this document is an 1. Updated the Introduction to indicate that this document is an
skipping to change at page 35, line 25 skipping to change at page 35, line 25
RFC 8247, DOI 10.17487/RFC8247, September 2017, RFC 8247, DOI 10.17487/RFC8247, September 2017,
<https://www.rfc-editor.org/info/rfc8247>. <https://www.rfc-editor.org/info/rfc8247>.
[RFC8311] Black, D., "Relaxing Restrictions on Explicit Congestion [RFC8311] Black, D., "Relaxing Restrictions on Explicit Congestion
Notification (ECN) Experimentation", RFC 8311, Notification (ECN) Experimentation", RFC 8311,
DOI 10.17487/RFC8311, January 2018, DOI 10.17487/RFC8311, January 2018,
<https://www.rfc-editor.org/info/rfc8311>. <https://www.rfc-editor.org/info/rfc8311>.
22.2. Informative References 22.2. Informative References
[I-D.ietf-v6ops-ipv6rtr-reqs]
Kahn, Z., Brzozowski, J., and R. White, "Requirements for
IPv6 Routers", draft-ietf-v6ops-ipv6rtr-reqs-01 (work in
progress), January 2018.
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, [RFC0793] Postel, J., "Transmission Control Protocol", STD 7,
RFC 793, DOI 10.17487/RFC0793, September 1981, RFC 793, DOI 10.17487/RFC0793, September 1981,
<https://www.rfc-editor.org/info/rfc793>. <https://www.rfc-editor.org/info/rfc793>.
[RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S. [RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, DOI 10.17487/RFC2205, Functional Specification", RFC 2205, DOI 10.17487/RFC2205,
September 1997, <https://www.rfc-editor.org/info/rfc2205>. September 1997, <https://www.rfc-editor.org/info/rfc2205>.
[RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet
 End of changes. 15 change blocks. 
23 lines changed or deleted 12 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/