Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt

On 10 February 2016 at 06:13, 神明達哉 <jinmei@wide.ad.jp> wrote:
> At Sat, 6 Feb 2016 08:22:28 +1300,
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>
>> >>>   I'm not sure if I can understand the "or a Default Router List"
>> >>>   part.  If it means 'Router Advertisement may contain...a Default
>> >>>   Router List', it doesn't make sense since an RA (or any of its
>> >>>   options) doesn't contain such a list (Default Router List is
>> >>>   something that a host maintains based on the content of RA).
>> >>
>> >> I think you're correct.
>> >
>> > Then I guess the sentence will have to be revised, but I can't suggest
>> > anything specific as I don't understand the original intent.  Does
>> > this "Default Router List" perhaps actually means the source IPv6
>> > address of the RA (which will be maintained in the Default Router List
>> > of the receiving host)?
>>
>> I think we should simply delete ", or a Default Router List". That list
>> is created and maintained by the host, as you say.
>
> Okay, then my personal suggestion for the entire paragraph would be:
>
>    As described in [RFC4191] and [RFC4861], a Router Advertisement may
>    contain zero or more Prefix information Options (PIOs), or zero or more
>    Route Information Options (RIOs).  In their
>    original intent, these indicate general information to a host: "this
>    is your default router",

Actually, only the router lifetime field indicates that the RA is
coming from a default router or not.

>"you might create an address in this
>    prefix", or "this router would be a good place to
>    send traffic directed to a given destination prefix".  In a multi-
>    homed network implementing source/destination routing, the
>    interpretation of default router or an RIO has to be modified
>    with the words "if the source address is in one of the prefixes I
>    advertise in a PIO".  Additionally, the PIO must be reinterpreted to
>    also imply that the advertising router would be a reasonable first
>    hop for any packet using a source address in any advertised prefix.
>

> --
> JINMEI, Tatuya
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------