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

Re: RFC 5006 status



Fred Baker <fred@cisco.com>, 2010-03-17 16:18 (+0100):

> 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)
>
> (2) Vendors, please advise on implementations. Are there any? Has
> interoperability been demonstrated?

Implementations of RFC 5006 known to me:

  - Server side: radvd,

    http://www.litech.org/radvd/

  - Client side:

    My own radns, slowly getting there, 
    http://hack.org/mc/hacks/radns/

    rdnssd, now maintained as a part of ndisc6: 
    http://rdnssd.linkfanel.net
    http://www.remlab.net/ndisc6/

radvd works well with both radns and rdnssd.

> (3) Operators, enterprise and/or service provider, please advise on
> deployment experience.

I have so far only used this with a manual configuration in radvd, but I
think this will typically be used in a home or SOHO environment where
the ISP gives addresses to DNS resolvers to a home/small office router
with DHCPv6 and that router, in turn, sends this information to end
nodes with the RDNSS option in RA.

-- 
http://hack.org/mc/
Use plain text e-mail, please. OpenPGP welcome, 0xE4C92FA5.