Hi John,
At 18:13 27-05-2011, John C Klensin wrote:
p.s. A general observation about the state of YAM... To me,
4409bis is not only worth doing in and of itself, it is a bit of
a test case as to whether we can actually open up documents and
clean them up as needed to advance them in the Standard Track
(or just clean them up) without taking the opportunity to
reexamine the protocol, various bits of advice, etc. If we
cannot do that with 4409bis, I think the WG will need to look
very carefully at the value proposition associated with other
specs, especially if a two-step standards process is adopted and
essentially just redefines all of the YAM document repertoire
into full standards.
This working group has been inactive since the end of last year. Due
to circumstances beyond the control of YAM WG, it has known a
difficult start. YAM was formed in May 2009. The WG has only
produced one Internet Standard up to now. WG participants may have
different ideas of what fits within the scope of changes for an
Internet Standard or what's an Internet Standard meant to be. I'll
highlight a sentence from the YAM Charter:
"If an existing protocol implementation is conforming to the Draft Standard
version of the protocol specification, it must also be conforming to the
resulting Full Standard version."
The YAM WG adopted a two-stage process where it does any evaluation
which identifies the list of changes first
(draft-ietf-yam-4409bis-submit-pre-evaluation-00). The next step is
for the editors of 4409bis to incorporate these changes in a draft
(draft-ietf-yam-rfc4409bis). There are some new changes that have
been suggested during this second step. I suggest leaving the
discussion about those changes open for a few days. I'll post a
summary of the discussion after that. Let's see whether we can get
some form of agreement on what fits within the scope of changes
instead of the WG Chairs taking a heavy-handed approach. Please note
that this is not an invitation to rewrite the protocol. :-)
Regards,
S. Moonesamy
_______________________________________________
yam mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/yam
