I propose retiring A6, DNAME, and ip6.arpa. The procedure for this is specified in RFC 2026, section 6.4: we ask the IESG to change the status of the specifications to Historic. Clients and servers will go on happily using AAAA and ip6.int. See http://cr.yp.to/djbdns/killa6.html if you missed the discussion of why A6 and DNAME are a bad idea. ---Dan -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
- Re: The case against A6 and DNAME Ian Jackson
- Re: The case against A6 and DNAME Matt Crawford
- RE: The case against A6 and DNAME Jim . Bound
- RE: The case against A6 and DNAME Christian Huitema
- Re: The case against A6 and DNAME Bill Sommerfeld
- The cost of signing records D. J. Bernstein
- Re: The case against A6 and DNAME Nathan Lutchansky
- Re: The case against A6 and DNAME Matt Crawford
- RE: The case against A6 and DNAME Jim . Bound
- Re: The case against A6 and DNAME D. J. Bernstein
- RE: The case against A6 and DNAME D. J. Bernstein
- RE: The case against A6 and DNAME Jim . Bound
- Re: The case against A6 and DNAME JIM FLEMING
- RE: The case against A6 and DNAME David R. Conrad
- Re: The case against A6 and DNAME D. J. Bernstein
- Re: The case against A6 and DNAME David R. Conrad
- Re: The case against A6 and DNAME D. J. Bernstein
- Re: The case against A6 and DNAME Robert Elz
- Re: The case against A6 and DNAME Niels M�ller
