Subject: Re: I-D Action: draft-sarikaya-6man-next-hop-ra-02.txt

From: Brian E Carpenter <[email-masked]>
Date: Mon, 09 Jun 2014 15:32:14 +1200

Hi,

I believe we have a problem to which this is one of the two solutions.
(More on that later.)

I only have two technical queries about this version, both on the same
sentence:

>    Next Hop Address with
>    Route Prefix option MUST be followed by a Source Prefix option
>    defined in Section 10 to indicate that any source addresses derived
>    from the source prefix will not be subject to ingress filtering on
>    these routes supported by these next hops.

1. Does this mean "MUST be immediately followed"? I think this
is necessary.

2. What if a given Next Hop Address with Route Prefix allows
packets with several different source prefixes? Must the
couple {Next Hop Address with Route Prefix, Source Prefix}
be repeated several times, or can we somehow use
{Next Hop Address with Route Prefix, Source Prefix 1, Source Prefix 2...} ?

Now about the two solutions. Some people want to achieve this with
RA. Some people want to achieve it with DHCPv6. We can continue that
argument for ever, or we can choose sanity and do both. That's why I
rather liked draft-arifumi-ipv6-nd-source-address-select and
draft-hirotaka-dhc-source-address-selection-opt 9 years ago. They
attempted to use strictly identical formats for RA and DHCPv6
messages for this purpose.

Incidentally, there is work to be done on how host stacks
and the socket API handle all this. Just define RA and DHCPv6
messages is only the start.

Regards
   Brian Carpenter

On 04/06/2014 04:26, [email-masked] wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : IPv6 RA Options for Next Hop Routes
>         Author          : Behcet Sarikaya
> 	Filename        : draft-sarikaya-6man-next-hop-ra-02.txt
> 	Pages           : 13
> 	Date            : 2014-06-03
> 
> Abstract:
>    This document proposes new Router Advertisement options for
>    configuring next hop routes on the mobile or fixed nodes.  Using
>    these options, an operator can easily configure nodes with multiple
>    interfaces (or otherwise multi-homed) to enable them to select the
>    routes to a destination.  Each option is defined together with
>    definitions of host and router behaviors.  This document also
>    proposes the router advertisement extensions for source address
>    dependent routing.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-sarikaya-6man-next-hop-ra/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-sarikaya-6man-next-hop-ra-02
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-sarikaya-6man-next-hop-ra-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>