< draft-templin-6man-dhcpv6-ndopt-07.txt   draft-templin-6man-dhcpv6-ndopt-08.txt >
Network Working Group F. Templin, Ed. Network Working Group F. Templin, Ed.
Internet-Draft Boeing Research & Technology Internet-Draft Boeing Research & Technology
Intended status: Informational December 17, 2018 Intended status: Informational June 24, 2019
Expires: June 20, 2019 Expires: December 26, 2019
A Unified Stateful/Stateless Configuration Service for IPv6 A Unified Stateful/Stateless Configuration Service for IPv6
draft-templin-6man-dhcpv6-ndopt-07.txt draft-templin-6man-dhcpv6-ndopt-08.txt
Abstract Abstract
IPv6 Neighbor Discovery (IPv6ND) specifies a control message set for IPv6 Neighbor Discovery (IPv6ND) specifies a control message set for
nodes to discover neighbors, routers, prefixes and other services on nodes to discover neighbors, routers, prefixes and other services on
the link. It also supports a manner of StateLess Address the link. It also supports a manner of StateLess Address
AutoConfiguration (SLAAC), while the Dynamic Host Configuration AutoConfiguration (SLAAC), while the Dynamic Host Configuration
Protocol for IPv6 (DHCPv6) specifies a separate stateful service. Protocol for IPv6 (DHCPv6) specifies a separate stateful service.
This document presents IPv6ND extensions for providing a unified This document presents IPv6ND extensions for providing a unified
stateful/stateless configuration service. stateful/stateless configuration service.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 June 20, 2019. This Internet-Draft will expire on December 26, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 36 skipping to change at page 2, line 36
5.1. Out-of-Band Network Login . . . . . . . . . . . . . . . . 10 5.1. Out-of-Band Network Login . . . . . . . . . . . . . . . . 10
5.2. Out-of-Band Network Login Usage . . . . . . . . . . . . . 10 5.2. Out-of-Band Network Login Usage . . . . . . . . . . . . . 10
5.3. Stateful Provisioning Requirements . . . . . . . . . . . 11 5.3. Stateful Provisioning Requirements . . . . . . . . . . . 11
5.4. Implementation Considerations . . . . . . . . . . . . . . 11 5.4. Implementation Considerations . . . . . . . . . . . . . . 11
6. Implementation Status . . . . . . . . . . . . . . . . . . . . 11 6. Implementation Status . . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
8. Security Considerations . . . . . . . . . . . . . . . . . . . 11 8. Security Considerations . . . . . . . . . . . . . . . . . . . 11
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
10.1. Normative References . . . . . . . . . . . . . . . . . . 12 10.1. Normative References . . . . . . . . . . . . . . . . . . 12
10.2. Informative References . . . . . . . . . . . . . . . . . 13 10.2. Informative References . . . . . . . . . . . . . . . . . 12
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 13 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
IPv6 Neighbor Discovery (IPv6ND) [RFC4861] specifies a control IPv6 Neighbor Discovery (IPv6ND) [RFC4861] specifies a control
message set for nodes to discover neighbors, routers, prefixes and message set for nodes to discover neighbors, routers, prefixes and
other services on the link. It also supports a manner of StateLess other services on the link. It also supports a manner of StateLess
Address AutoConfiguration (SLAAC). The Dynamic Host Configuration Address AutoConfiguration (SLAAC). The Dynamic Host Configuration
Protocol for IPv6 (DHCPv6) specifies a separate service for Protocol for IPv6 (DHCPv6) specifies a separate service for
delegation of prefixes, addresses and any other stateful information delegation of prefixes, addresses and any other stateful information
[RFC3315][RFC3633]. This document presents IPv6ND extensions for [RFC8415]. This document presents IPv6ND extensions for providing a
providing a unified stateful/stateless configuration service. unified stateful/stateless configuration service.
If the network can provide such a unified service, multi-message If the network can provide such a unified service, multi-message
procedures can be condensed into a single and concise message procedures can be condensed into a single and concise message
exchange. This would ease network management as well as simplify exchange. This would ease network management as well as simplify
host and router operations. It would further accommodate both host and router operations. It would further accommodate both
stateless and stateful services in a way that combines the best stateless and stateful services in a way that combines the best
aspects of both. The operating model is based on harnessing the IPv6 aspects of both. The operating model is based on harnessing the IPv6
ND Router Solicitation (RS) / Router Advertisement (RA) functions to ND Router Solicitation (RS) / Router Advertisement (RA) functions to
provide all configuration information in a single message exchange. provide all configuration information in a single message exchange.
skipping to change at page 4, line 30 skipping to change at page 4, line 30
these approaches. these approaches.
2. DHCPv6 Options in IPv6 ND Messages 2. DHCPv6 Options in IPv6 ND Messages
The first method entails the inclusion of DHCPv6 messages within The first method entails the inclusion of DHCPv6 messages within
IPv6ND RS and RA messages, as discussed in the following sections. IPv6ND RS and RA messages, as discussed in the following sections.
2.1. The DHCPv6 Option 2.1. The DHCPv6 Option
The DHCPv6 option is a new IPv6ND option that simply embeds a The DHCPv6 option is a new IPv6ND option that simply embeds a
standard DHCPv6 message per section 6 of [RFC3315], beginning with standard DHCPv6 message per section 6 of [RFC8415], beginning with
the 'msg-type' followed by the 'transaction-id' and all DHCPv6 the 'msg-type' followed by the 'transaction-id' and all DHCPv6
'options'. The format of the option is as follows: 'options'. The format of the option is as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type = TBD | Length | Pad | Reserved | | Type = TBD | Length | Pad | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| msg-type | transaction-id | | msg-type | transaction-id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 5 skipping to change at page 5, line 5
. (variable) ................... . (variable) ...................
| . Padding (0-7) . | . Padding (0-7) .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: IPv6 ND DHCPv6 Option Format Figure 1: IPv6 ND DHCPv6 Option Format
In this format, 'Type' and 'Length' are exactly as defined in In this format, 'Type' and 'Length' are exactly as defined in
Section 4.6 of [RFC4861], 'Pad' is a 3-bit integer that encodes the Section 4.6 of [RFC4861], 'Pad' is a 3-bit integer that encodes the
padding length, 'Reserved' is included for alignment and future use, padding length, 'Reserved' is included for alignment and future use,
and the rest of the option is formatted as specified in Section 6 of and the rest of the option is formatted as specified in Section 6 of
[RFC3315] except with trailing null padding added as necessary for 8 [RFC8415] except with trailing null padding added as necessary for 8
octet alignment. The length of the full DHCPv6 message is determined octet alignment. The length of the full DHCPv6 message is determined
by ((('Length' * 8) - 4) - 'Pad'), for a maximum message length of by ((('Length' * 8) - 4) - 'Pad'), for a maximum message length of
2036 octets. 2036 octets.
The 'Reserved' field MUST be set to 0 on transmission and ignored on The 'Reserved' field MUST be set to 0 on transmission and ignored on
reception. Future specifications MAY define new uses for these bits. reception. Future specifications MAY define new uses for these bits.
2.2. DHCPv6 Option Usage 2.2. DHCPv6 Option Usage
When a node first comes onto the link, it creates an RS message When a node first comes onto the link, it creates an RS message
skipping to change at page 9, line 20 skipping to change at page 9, line 20
further details. further details.
4.1. Embedded Prefix Assertion 4.1. Embedded Prefix Assertion
In this method, the node is pre-provisioned with the prefix it will In this method, the node is pre-provisioned with the prefix it will
use on its downstream networks (e.g., through network management, use on its downstream networks (e.g., through network management,
manual configuration, etc.). To invoke this method, the node manual configuration, etc.). To invoke this method, the node
includes its pre-provisioned prefix in the link-local source address includes its pre-provisioned prefix in the link-local source address
of its RS message according to the AERO address format of its RS message according to the AERO address format
[I-D.templin-6man-aeroaddr]. For example, if the node is pre- [I-D.templin-6man-aeroaddr]. For example, if the node is pre-
provisioned with the prefix 2001:db8:1000:2000, it creates its IPv6 provisioned with the prefix 2001:db8:1000:2000::/64, it creates its
link-local source address as fe80::2001:db8:1000:2000. IPv6 link-local source address as fe80::2001:db8:1000:2000.
4.2. Embedded Prefix Usage 4.2. Embedded Prefix Usage
When a node that wishes to assert a prefix first comes onto the link, When a node that wishes to assert a prefix first comes onto the link,
it statelessly configures an AERO address based on its pre- it statelessly configures an AERO address based on its pre-
provisioned prefix. The node then includes the AERO address as the provisioned prefix. The node then includes the AERO address as the
source address of a standard RS message. If a router that receives source address of a standard RS message. If a router that receives
the RS message has a way of verifying that the node is authorized to the RS message has a way of verifying that the node is authorized to
receive the solicited prefix, the router injects the prefix into the receive the solicited prefix, the router injects the prefix into the
routing system and returns a standard RA message. When the node routing system and returns a standard RA message. When the node
skipping to change at page 11, line 46 skipping to change at page 11, line 46
The IANA is instructed to assign an IPv6ND option Type value TBD for The IANA is instructed to assign an IPv6ND option Type value TBD for
the DHCPv6 option. the DHCPv6 option.
The IANA is instructed to create a registry for the DHCPv6 option The IANA is instructed to create a registry for the DHCPv6 option
"Reserved" field (with no initial assignments) so that future uses of "Reserved" field (with no initial assignments) so that future uses of
the field can be coordinated. the field can be coordinated.
8. Security Considerations 8. Security Considerations
Security considerations for IPv6 Neighbor Discovery [RFC4861] and Security considerations for IPv6 Neighbor Discovery [RFC4861] and
DHCPv6 [RFC3315][RFC3633] apply to this document. DHCPv6 [RFC8415] apply to this document.
SEcure Neighbor Discovery (SEND) [RFC3971] can provide authentication SEcure Neighbor Discovery (SEND) [RFC3971] can provide authentication
for IPv6 ND messages with no need for additional securing mechanisms. for IPv6 ND messages with no need for additional securing mechanisms.
9. Acknowledgements 9. Acknowledgements
This work was motivated by discussions on the 6man and v6ops list. This work was motivated by discussions on the 6man and v6ops list.
Those individuals who provided encouragement and critical review are Those individuals who provided encouragement and critical review are
acknowledged. acknowledged.
The following individuals provided useful comments that improved the The following individuals provided useful comments that improved the
document: Mikael Abrahamsson, Fred Baker, Ron Bonica, Naveen document: Mikael Abrahamsson, Fred Baker, Ron Bonica, Yucel Guven,
Kottapalli, Ole Troan, Bernie Volz. Naveen Kottapalli, Ole Troan, Bernie Volz.
The following individuals developed IPv6ND and DHCPv6 extensions for The following individuals developed IPv6ND and DHCPv6 extensions for
OpenVPN: Kyle Bae, Wayne Benson, Eric Yeh. OpenVPN: Kyle Bae, Wayne Benson, Eric Yeh.
This work is aligned with the NASA Safe Autonomous Systems Operation This work is aligned with the NASA Safe Autonomous Systems Operation
(SASO) program under NASA contract number NNA16BD84C. (SASO) program under NASA contract number NNA16BD84C.
This work is aligned with the FAA as per the SE2025 contract number This work is aligned with the FAA as per the SE2025 contract number
DTFAWA-15-D-00030. DTFAWA-15-D-00030.
This work is aligned with the Boeing Information Technology (BIT) This work is aligned with the Boeing Information Technology (BIT)
MobileNet program and the Boeing Research & Technology (BR&T) MobileNet program and the Boeing Research & Technology (BR&T)
enterprise autonomy program. enterprise autonomy program.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
C., and M. Carney, "Dynamic Host Configuration Protocol
for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July
2003, <https://www.rfc-editor.org/info/rfc3315>.
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
Host Configuration Protocol (DHCP) version 6", RFC 3633,
DOI 10.17487/RFC3633, December 2003,
<https://www.rfc-editor.org/info/rfc3633>.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
DOI 10.17487/RFC4861, September 2007, DOI 10.17487/RFC4861, September 2007,
<https://www.rfc-editor.org/info/rfc4861>. <https://www.rfc-editor.org/info/rfc4861>.
[RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", STD 86, RFC 8200, (IPv6) Specification", STD 86, RFC 8200,
DOI 10.17487/RFC8200, July 2017, DOI 10.17487/RFC8200, July 2017,
<https://www.rfc-editor.org/info/rfc8200>. <https://www.rfc-editor.org/info/rfc8200>.
[RFC8415] Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A.,
Richardson, M., Jiang, S., Lemon, T., and T. Winters,
"Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
RFC 8415, DOI 10.17487/RFC8415, November 2018,
<https://www.rfc-editor.org/info/rfc8415>.
10.2. Informative References 10.2. Informative References
[I-D.naveen-slaac-prefix-management] [I-D.naveen-slaac-prefix-management]
Kottapalli, N., "IPv6 Stateless Prefix Management", draft- Kottapalli, N., "IPv6 Stateless Prefix Management", draft-
naveen-slaac-prefix-management-00 (work in progress), naveen-slaac-prefix-management-00 (work in progress),
November 2018. November 2018.
[I-D.pioxfolks-6man-pio-exclusive-bit] [I-D.pioxfolks-6man-pio-exclusive-bit]
Kline, E. and M. Abrahamsson, "IPv6 Router Advertisement Kline, E. and M. Abrahamsson, "IPv6 Router Advertisement
Prefix Information Option eXclusive Flag", draft- Prefix Information Option eXclusive Flag", draft-
pioxfolks-6man-pio-exclusive-bit-02 (work in progress), pioxfolks-6man-pio-exclusive-bit-02 (work in progress),
March 2017. March 2017.
[I-D.templin-6man-aeroaddr] [I-D.templin-6man-aeroaddr]
Templin, F., "The AERO Address", draft-templin-6man- Templin, F., "The AERO Address", draft-templin-6man-
aeroaddr-03 (work in progress), November 2018. aeroaddr-04 (work in progress), December 2018.
[RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander, [RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander,
"SEcure Neighbor Discovery (SEND)", RFC 3971, "SEcure Neighbor Discovery (SEND)", RFC 3971,
DOI 10.17487/RFC3971, March 2005, DOI 10.17487/RFC3971, March 2005,
<https://www.rfc-editor.org/info/rfc3971>. <https://www.rfc-editor.org/info/rfc3971>.
[RFC6221] Miles, D., Ed., Ooghe, S., Dec, W., Krishnan, S., and A. [RFC6221] Miles, D., Ed., Ooghe, S., Dec, W., Krishnan, S., and A.
Kavanagh, "Lightweight DHCPv6 Relay Agent", RFC 6221, Kavanagh, "Lightweight DHCPv6 Relay Agent", RFC 6221,
DOI 10.17487/RFC6221, May 2011, DOI 10.17487/RFC6221, May 2011,
<https://www.rfc-editor.org/info/rfc6221>. <https://www.rfc-editor.org/info/rfc6221>.
Appendix A. Change Log Appendix A. Change Log
<< RFC Editor - remove prior to publication >> << RFC Editor - remove prior to publication >>
Changes from -07 to -08:
o Changed DHCPv6 reference to RFC8415 - deprecates RFC3315 and
RFC3633
o added prefix length to example in Section 4.1.
Changes from -06 to -07: Changes from -06 to -07:
o Added "unsolicited DHCPv6 Reply" considerations o Added "unsolicited DHCPv6 Reply" considerations
o Added refeence to new IPv6ND-based PD proposal. o Added refeence to new IPv6ND-based PD proposal.
o No longer associate the term "autoconfiguration" with the term o No longer associate the term "autoconfiguration" with the term
"stateful". "stateful".
o Added URL for implementation. o Added URL for implementation.
 End of changes. 16 change blocks. 
27 lines changed or deleted 30 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/