OK, folks, so I see two possibilities mentioned here.

(1) Retract the iana-objects draft, update it wrt prefix status changes, and send it back to the RFC-Editor to wait until and if the IESG approves the 6to4-to-historic draft.

(2) Let the iana-objects draft progress, begin work on a -bis immediately. (The -bis could introduce a registry, if that looks like a good option.)

As I see it, process wise:

(1) eliminates the half-skip step of publishing an RFC known to be facing obsolesence in short order but induces a delay in IANA actions for these iana objects.

(2) avoids the planned obsolesence but does not impede IANA actions for these iana objects.

Comments from the group, please, as soon as possible.

--Sandy, speaking as wg chair

P.S. Note that there is an option (2+) which would produce the -bis so fast (and with care to be compatible with any IESG decision on 6to4) that it would overtake the iana-objects draft on the RFC Editor queue. :-)

On Tue, 7 Jun 2011, Randy Bush wrote:

The question I have is about trying to intrude on the RFC-Editor queue
now, while the iana-objects is having all the boxes ticked and is well
ahead of draft-ietf-v6ops-6to4-to-historic-04, or wait for publication
of v6ops-6to4-to-historic and (as already covered in iana-objects)
issue an update.

if you are asking this question, perhaps you should be asking why it is
not a registry.

randy

_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to