Re: RS sending in draft-ietf-v6ops-ipv6-cpe-router-04

[Wojciech Dec <wdec@cisco.com>]

On 15/04/2010 17:04, "Philip Homburg" <pch-v6ops@u-1.phicoh.com> wrote:

> In your letter dated Thu, 15 Apr 2010 16:02:49 +0200 you wrote:
>> Given that RS triggered access appears to be gaining ground (based on the
>> latest  draft-krishnan-rs-mark) it would appear that the CPE router draft
>> specify a bit more tightly the form of RS messages a CPE sends when
>> connecting to a network.
>> RFC4861 section 6.3.7 states:
>> " A host sends Router Solicitations to the all-routers multicast
>>   address.  The IP source address is set to either one of the
>>   interface's unicast addresses or the unspecified address."
>> 
>> Now, since the source address is very likely to be one of the identifier
>> keys for a CPE used for authorization, I would like to propose that an RS
>> sending rule be added to the CPE spec which would ensure that the IP source
>> address is NEVER the unspecified address, eg:
>> 
>> The IPv6 CE router MUST use one of its WAN interface unicast addresses when
>> sending RS messages.
> 
> Does that mean that if you use your neighbor's mac address, you will get
> your neighbors prefix?

Well, I meant "MUST use of its WAN interface *IPv6* unicast addresses...

> 
> draft-krishnan-6man-rs-mark-03 talks about a LIO option. Which should be
> enough to identify the customer.

The LIO is one key, however the LL and unicast IP addresses of a CE need to
be correlated to that key, hence they are essential pieces of info.

-Woj.
> 
>