Re: NGtrans closing procedures

Alain,

....
> Support for Multicast over 6to4 Networks (6TO4-MULTICAST)
> is ngtrans ID
> <http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6to4-multicast-01.txt>
> 
> becomes personal ID
> <http://www.ietf.org/internet-drafts/draft-thaler-ngtrans-6to4-multicast-01.txt>

I don't understand this proposal. Since 6to4 is on the menu for v6ops, it 
makes no sense to cut this draft loose as an individual submission.
The 6to4 solution is incomplete without multicast.

The same argument applies to

draft-ietf-ngtrans-6to4-dns-01.txt (expired, but something's needed)
draft-savola-ngtrans-6to4-security-01.txt (no consensus yet, but needed)

One option of course would be to spin up a 6to4 WG narrowly focussed
on these three drafts plus any updates to RFC 3056 - but it seems like
a lot of overhead rather than just taking these items in v6ops.

   Brian