Request to advance rfc4214(bis) to standards-track through AD sponsorship

["Templin, Fred L" <Fred.L.Templin@boeing.com>]

This whole exercise reminds me of what volleyball players
call a "campfire defense" - everyone stands around in a
circle and the ball drops to the floor in the middle...

Just to sum up, this discussion got started on the 'ram'
mailing list and then moved over to 'v6ops' where the bulk
of the discussion took place (hence I am posting only to
'v6ops'). Meanwhile, discussion on the 'ipv6' list turned
up some points for clarification that could potentially
be addressed in an rfc4214(bis) document. Finally, there
was some brief mention of the 'softwire' wg, but there
seems to be no clear way forward for wg adoption.

So, I seem to be left with the decision of just letting
it go or seeking publication as an individual submission
through AD sponsorship as outlined in "ION: Guidance on
Area Director Sponsoring of Documents". By my own judgement,
there seems to be sufficient interest on the various mailing
lists such that the latter option would seem to be in the
best interest of the community so I would like to now
request advancement of rfc4214(bis) to standards-track
through AD sponsorship.

Perhaps someone can correct me if I'm wrong, but the "ION:
Guidance..." document seems to leave it up to the individual
as to which AD to select as sponsor. That being the case, I
have to look at the past history of rfc4214 and note that it
was published through AD sponsorship by an operations area
AD. So, I would like to request that Ron Bonica from the
operations area take on advancement of this document
as the sponsoring AD.

If for some reason Ron must decline, I would then ask that
Mark Townsley from the Internet area take on the sponsorship
responsibility since a good bit of the discussion and technical
input have come from the Internet area. Please note that the
selection of Ron and Mark was that (again, by my own judgement)
they seem to have the most experience with tunneling mechanisms
based on their RFC publication record; it was not intended as
a snub to the other ADs.

Please advise as to next-steps,

Fred L. Templin
fred.l.templin@boeing.com