draft status, BoF, replies to issues

[George Jones <gmj@pobox.com>]

OK.  It's been quite here.  Status of things is the -03 draft went to
IESG last call.  There have bee a number of comments in the id tracker
(https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=10387&rfc_flag=0)
as well as in other fora (routing-discuss mailing list, etc.) and
private mail to me.  I'm going to try to clear out the backlog and
respond to all issues raised, CCing this list with all responses.

The doc apparently got a very mixed reception and there was enough
concern in the IESG that they've scheduled a BoF to discuss what to do.
Likely options seem to be (in no particular order): nothing, spin up a
working group, publish current doc (with revisions) as an info RFC and
spin up a working group, revise current draft and publish as BCP rfc.

As I've said all along, I will do whatever the wise Area Directors,
IESG, etc. see best.  I'm in this to produce useful substance in
whatever form makes sense.

I will not be @ the BoF (though I might be able to do Jabber or AIM if
someone who will be there sets it up.)

Thanks to all who have read the draft and provided feedback

Responses to follow.

George M. Jones    |  Gulta cavat lapidem non vi sed saepe cadendo ("The drop
                   |  hollows the stone not by force but by often falling")
                   |
                   |      Ovid (Latimer, 7th sermon)