Hi Tim,

I don't know much about RFC3484, but do you mean that the STB in my example
can choose the expected prefix/address via the Policy Table?
What is in the Policy Table and how to configure it? Manually (maybe not
acceptable for SLAAC case) or automatically?

Thanks!

Best regards,
Fortune


-----Original Message-----
From: Tim Chown [mailto:t...@ecs.soton.ac.uk] 
Sent: Tuesday, June 08, 2010 4:53 PM
To: Fortune HUANG
Cc: 'JOSHI, SHRINIVAS ASHOK (SHRINIVAS ASHOK)'; ipv6@ietf.org
Subject: Re: Question about SLAAC: how the host determines the prefixes
allocated from different prefix pools


On 8 Jun 2010, at 09:44, Fortune HUANG wrote:

> 
> I don't have any preference to use RA over DHCPv6, but I would be 
> grateful if you could tell me the guidance to decide whether to deploy 
> SLAAC or DHCPv6.
> Obviously, SLAAC can not work as expected in the scenario in my 
> example. So this seems be to a restriction to the deployment of SLAAC 
> at least for the time being (any possibility for the SLAAC/RA to 
> support multiple prefix pools for different services in the future?).
> 


In principle if each prefix is used with a service that is served from that
prefix, then if the device implements RFC3484 address selection your
multi-addressed hosts should use the correct source addresses.    The device
would prefer the longest matching prefix.    It's also possible to use
policy tables with address selection to influence address selection
decisions.

Note though that RFC3484 has some open issues that are hopefully to be
resolved with an update soon (many implementors have already reflected these
updates in their products) but also that at least one major operating system
(Mac OSX) as yet has no support for the feature.   A method to distribute
policy tables (by DHCPv6) is also on the table.

Tim=

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

Reply via email to