RE: Prefix delegation based on standard IPv6 ND messaging

Hi Brian,

Those drafts go back a few years, and I did not see them. My draft proposes
four different possibilities for IPv6 ND-based prefix delegation (see below).
Please let me know your thoughts.

Fred
fred.l.templin@boeing.com

---

2.  DHCPv6 Options in IPv6 ND Messages

- in this section, the design of a new NDP option is proposed, where the option is
  identical to a DHCPv6 message. The DHCPv6 message option is included in RS
  messages to solicit a prefix and in RA messages to delegate a prefix. All other
  DHCPv6 messages (Renew/Rebind/Release/etc.) are supported through their
  inclusion in RS/RA messages. I have not seen other documents suggest including
  a DHCPv6 message within an IPv6 ND message.

3.  PIO Options in RS Messages

- In this section, it is proposed to include a PIO option with the "X" bit set within an
  RS message to solicit a prefix delegation from a router acting as specified in
  'draft-pioxfolks-6man-pio-exclusive-bit'. I have not seen other documents
  suggest including a PIO option with the X bit set in RS messages.

4.  Embedded Prefix Assertion

- In this section, it proposes to include an IPv6 prefix embedded within the interface
   identifier within the link-local source address of an RS message. The delegating
   router examines the link-local source address to determine the IPv6 prefix, and
   injects the prefix into the routing system. Neither the RS nor the RA carry any
   options pertaining to the prefix delegation.

5.  Out-of-Band Network Login Messaging

- This section suggests a Layer 2 (L2) message exchange between the requesting
   router and the network, which causes the delegating router to return an RA.
   No options pertaining to prefix delegation are included in the RA message.

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Brian Haberman
> Sent: Tuesday, October 02, 2018 7:33 AM
> To: ipv6@ietf.org
> Subject: Re: Prefix delegation based on standard IPv6 ND messaging
> 
> Hi Fred,
>      Would be curious about views as to how this approach differs
> significantly from previous attempts to create a non-DHCP-based prefix
> delegation protocol.
> 
> https://tools.ietf.org/html/draft-kaiser-nd-pd-01
> https://tools.ietf.org/html/draft-bykim-ipv6-hpd-01
> https://tools.ietf.org/html/draft-haberman-ipngwg-auto-prefix-02
> 
> None of those are mentioned in your draft.
> 
> Regards,
> Brian
> 
> On 9/26/18 3:54 PM, Templin (US), Fred L wrote:
> > Hi, we have come up with a "new" way of coordinating prefix delegation without
> > DHCPv6 messaging and without requiring any new IPv6 ND options nor modifications
> > to existing options or messages. The method applies only to environments where a
> > node has been administratively assigned an IPv6 prefix by the administrative authority
> > for the network. The prefix length must also be the same (e.g., /56, /60, etc.) for all
> > nodes that connect to the network.
> >
> > Given the above requirements, the node can insert its network prefix into the
> > IPv6 source address of a Router Solicitation (RS) using the AERO address format.
> > In this format, if the node holds the prefix 2001:db8:1:2::/64 then the corresponding
> > AERO address is fe80::2001:db8:1:2. The node then sends the RS to either the
> > all-routers multicast address or to the unicast address of a specific router.
> >
> > When the router(s) receives the RS message, it first determines the node's
> > authority to use its claimed prefix. The router(s) then injects the prefix
> > 2001:db8:1:2/64 into the routing system and returns an RA message to
> > the node.
> >
> > When the node receives the RA message, it uses the default router lifetime
> > as the time before which it must perform an additional RS/RA message in
> > order for the network to retain its routing state. Everything is coordinated
> > by standard RS/RA messaging.
> >
> > This system is documented in Section 4 of the following document:
> >
> > https://datatracker.ietf.org/doc/draft-templin-6man-dhcpv6-ndopt/
> >
> > We are interested in receiving your comments.
> >
> > Fred
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >