31.08.2011 8:09, Murray S. Kucherawy wrote:
-----Original Message-----
From: ietf-bounces@xxxxxxxx [mailto:ietf-bounces@xxxxxxxx] On Behalf Of Mykyta Yevstifeyev
Sent: Tuesday, August 30, 2011 9:05 PM
To: ietf@xxxxxxxx
Subject: Re: Limitations in RFC Errata mechanism
I think given the current mechanism I would just submit such things
under "Editorial".
This is an option; but doing so makes work of RFC Editor when
incorporating metadata errata harder. If we have such thing as Metadata
erratum type, and if such erratum gets verified, RFC Editor will be
capable of noticing and acting quickly (I doubt RFC Editor pays much
attention to Editorial errata when submitted/verified).
I'm sure the RFC Editor appreciates people in the IETF trying to make their work easier, but since so far they haven't complained about this in particular, I'm not sure it's something that actually needs fixing.
Usually, when metadata erratum is reported, and some AD verifies it,
this AD is to report this change to RFC Editor manually, despite the
fact the verification notification is cc'ed to
rfc-editor@xxxxxxxxxxxxxx; also note that processing such errata may
take additional time because the whole IESG may be necessary to be
consulted, and so on. At least one step of this process may be
simplified simply.
I was able to type "Appendix A" just now into that section without
difficulty. The preview page shows "Section Appendix A says:", but
that hardly seems a difficulty.
This limitation makes submitters find the way to put what they want in
this field whose entity, I think, should be limited to digits and ".".
This issue is probably of aesthetic importance.
As a submitter, I didn't find typing "Appendix A" into that box and decoding the output to be at all inconvenient. It may not be perfect, but it's not terribly broken either.
So this, as already mentioned, is an aesthetic question. However,
"Section TOC" or "Section Appendix A" don't look nice.
Typically a working group discusses an erratum when it is raised, and
then it sits in limbo until a document update occurs. Isn't the right
place for discussion about a particular one the mailing list of that
working group or, if it's disbanded, the main IETF list?
Well, there are AD-sponsored Individual Submissions, which have no
associated WG, and IAB, IRTF and Independent docs which IETF community
might have a limited interest in. If we had the lists where errata
for:
[...]
I still don't see this as evidence that we need to have a forum specifically for discussing errata. I would have to subscribe to that list just in case there's ever any erratum opened for an RFC that interests me, and deal with the (possibly huge) amount of traffic that is not of interest. It seems to me that ietf@xxxxxxxx is just fine for this purpose, and most of us already are on that one.
I didn't see, for instance, any errata report against apps-related RFCs
coming to apps-discuss list. This would only happen if such RFC was
produced is appsawg WG. I didn't notice errata reports on genarea RFCs
coming on IETF Discussion list, which would be logical. There may be
more examples.
Else, errata system should be configured to copy all notifications to
specific area lists, which exists in all areas, which it currently isn't.
I also haven't seen any demand prior to this for a special forum where errata are discussed, separate from the list(s) we already have.
Discussing errata on IETF Discussion list will increase our traffic and
will soon bore many people who aren't particularly interested in a
variety of topics errata are submitted on.
As far as I can tell, that's where this happens now, and I don't see it being much of a burden.
Have we ever seen any errata coming on IETF Discussion?
Mykyta Yevstifeyev
I could be wrong, but I don't see much evidence that any of this stuff is broken enough to warrant a bunch of form changes, new mailing lists, or other new infrastructure. If it ain't broke, don't fix it.
-MSK
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf