In message
<22F6318E46E26B498ABC828879B08D4F1D272D(_at_)TK5EX14MBXW651(_dot_)wingroup(_dot_)windeploy(_dot_)ntdev(_dot_)microsoft(_dot_)com>,
Christian Huitema writes
:
After some discussion, the IESG is attempting to determine whether there is
IETF consensus to do the following:
- add a new section to draft-ietf-v6ops-6to4-to-historic
- publish draft-ietf-v6ops-6to4-to-historic as INFORMATIONAL
draft-ietf-v6ops-6to4-to-historic will obsolete RFCs 3056 and 3068 and
convert their status to HISTORIC. It will also contain >
a new section describing what it means for RFCs 3056 and 3068 to be
classified as HISTORIC. The new section will say that:
I do not think this is a good idea, and I am certainly not part of the
"consensus."
Seconded.
-- Christian Huitema
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka(_at_)isc(_dot_)org
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf