[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC 5006 status

This showed up as a requirement in the survey leading to
draft-carpenter-v6ops-isp-scenarios-01:

"Simple automatic distribution of DNS server details is essential;
RFC 5006 support is needed."

Only one ISP out of 30 mentioned this explicitly, although seven stated
an intention to support SLAAC (often combined with DHCPv6). However, it
does seem like the one essential feature for an all-SLAAC deployment.

Regards
   Brian Carpenter




On 2010-03-18 04:18, Fred Baker wrote:
> This is a structured question for the community.
> 
> Jari Arkko tells us that he is getting requests from various sources to take RFC 5006 to Proposed Standard. It is now experimental.
> 
> http://www.ietf.org/rfc/rfc5006.txt
> 5006 IPv6 Router Advertisement Option for DNS Configuration. J. Jeong,
>     Ed., S. Park, L. Beloeil, S. Madanapalli. September 2007. (Format:
>     TXT=26136 bytes) (Status: EXPERIMENTAL)
> 
> (1) Please take a look at the document in the next few days; if you have comments on it (eg, you think it should be changed in some way), please comment to v6ops.
> 
> (2) Vendors, please advise on implementations. Are there any? Has interoperability been demonstrated?
> 
> (3) Operators, enterprise and/or service provider, please advise on deployment experience.
> 
> 
> I'm adding a brief discussion to the agenda Monday morning with a view to getting a quick thumbs-up/thumbs-down to advise Jari, who can then take that to 6man later in the week if appropriate.
> 
> 
> 
> BTW, I have had a flurry of email related to the agenda. The current agenda may be found at http://www.ietf.org/proceedings/10mar/agenda/v6ops.html
>