[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Distributing, period, was: Re: Distributing site-wide RFC 3484 policy
On 25-jul-2007, at 17:40, Marc Blanchet wrote:
Once you have connectivity,
well, but the policy will enable you to have that connectivity. If
the policy the node currently have is wrong, then the node might
not reach the server you are talking about.
Quite right. That would be the "finding the light switch in the dark"
problem. :-)
However, I don't think RFC 3484 policy information is so essential
that finding a (presumably) local server to get that information from
in the absence of said information would be impossible even after
several retries.
So this mechanism would apply to all information that is not
essential to base connectivity.
downloading data of arbitrary size, providing information of an
arbitrary nature, is trivial through well-known mechanisms such as
HTTP. The only missing piece is the name/address of a small set of
servers that are initially queried for this information. And this
is something that will fit in a DHCP or RA message.
ok, so you agree on the idea, but you prefer another method than
DHCP or RA. Maybe you should write a draft on the method you are
proposing?
I guess I should. But not this week...
IPv6 book: Migrating to IPv6, Wiley, 2006, http://www.ipv6book.ca
Mine is Running IPv6, Apress, 2005, http://www.runningipv6.net/