On 17-feb-05, at 23:17, Jeroen Massar wrote:
Then to think someone who will remain nameless to protect the guilty wanted to obsolete ip6.int last year, less than a year after the publication of RFC 3596...
I meant "shut down".
You didn't see:
http://www.ietf.org/internet-drafts/ draft-huston-ip6-int-01.txt
yet?
Nope... 5648 unread messages in my ietf-announce box. :-)
What is the purpose of this document anyway? ip6.int is deprecated, no need to beat a dead horse.
the agreement is there, people are using ip6.arpa, just use it.
Sure. Wasn't there talk that Cisco still did ip6.int? But unless I'm very much mistaken my little ADSL Cisco running 12.3 does ip6.arpa.
Now if the makers of host and nslookup throw out the bit labels I'd be very happy. (Weird how these programs are completely anonymous: no way to find out where they come from or what version they are.)
Nothing to change about it, if you, me or any number of people don't like it. It is for the good anyway, ever checked the state of ip6.int ? :)
No, how would I do something like that? I don't want to start a whole big thing (well, not another one anyway) but it would make a lot of sense to me to just continue to run ip6.int. That's bound to be less trouble than trying to remove it. If nobody wants delegations, then keeping it around is no trouble. If lots of people want delegations, then apparently it still serves some purpose so removing it wouldn't be good. In either case, no upside to removing it at this point in time.
And yes, I'm keeping 3ffe:2500:310::/48 for as long as I can hold on to it, too. :-)
P.S.: http://a6.muada.nl/ (ducking)
_______________________________________________ 6bone mailing list [email protected] http://mailman.isi.edu/mailman/listinfo/6bone
