> -----Original Message-----
> From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of 
> Suresh Krishnan
> Sent: Wednesday, January 13, 2010 3:12 PM
> To: Ole Troan
> Cc: ipv6@ietf.org
> Subject: Re: Question: Detecting routers on a link
> 
> Hi Ole,
> 
> On 10-01-12 12:50 PM, Ole Troan wrote:
> > hi,
> >
> > a question arose from work I'm doing with the BBF and their CPE 
> > requirements document (TR-124/WT-
> 192). an issue has been raised with regards to a requirement about CPE 
> routers automatically offering
> ULA addresses on the LAN. in the case of multiple CPE routers on a link, the 
> suggestion is the
> following two requirements:
> >
> > LAN.ADDRESSv6.      3       The device MUST send a Router Solicitation to 
> > the LAN, to determine if there
> >                                                 are other routers present.  
> > MUST
> > LAN.ADDRESSv6.      4       If the device determines other routers are 
> > present in the LAN, and that
> another
> >                                                 router is advertising a ULA 
> > prefix, the device MUST
> be configurable to
> >                                                 automatically use this 
> > information to decide not to
> advertise its own
> >                                                 ULA prefix. MUST
> 
> The IPv6 router implementations that I have worked on do not send RSs on
> their advertising interfaces but I did not find this behavior prohibited
> by RFC4861. So I think you can get away with doing it and still be
> compliant.
> 
> On the idea itself, I think this is probably overkill. I can see the
> intent of these requirements (avoid multiple ULA prefixes in the "LAN")
> but I do not know why this restriction is needed. I cannot see any
> issues if both the routers advertise different ULAs and hosts configure
> multiple ULA addresses (one out of each prefix).

This matches my understanding of how router and prefix
discovery should work when there are multiple routers
on the link advertising different prefixes.

Fred
fred.l.temp...@boeing.com

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

Reply via email to