A good document. Here are some comments:
Section 2.3 says "the AD will schedule an IETF last call (when needed)" but my understanding is that all IETF stream documents now require IETF consensus so there is always an IETF last call.
Section 3.7: "the products these RGs are" -> "the products of these RGs are"
Section 3.9 says "patent suits" but I think it would be clearer to say "patent lawsuits".
Thanks,
Donald
===============================
Donald E. Eastlake 3rd +1-508-333-2270 (cell)
2386 Panoramic Circle, Apopka, FL 32703 USA
d3e3e3@xxxxxxxxx
Donald
===============================
Donald E. Eastlake 3rd +1-508-333-2270 (cell)
2386 Panoramic Circle, Apopka, FL 32703 USA
d3e3e3@xxxxxxxxx
On Mon, Feb 7, 2022 at 1:16 PM The IESG <iesg-secretary@xxxxxxxx> wrote:
The IESG has received a request from an individual submitter to consider the
following document: - 'Entities Involved in the IETF Standards Process'
<draft-rsalz-2028bis-05.txt> as Best Current Practice
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@xxxxxxxx mailing lists by 2022-03-07. Exceptionally, comments may
be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.
Abstract
This document describes the individuals and organizations involved in
the IETF standards process, as described in IETF BCP 9. It includes
brief descriptions of the entities involved, and the role they play
in the standards process. This document obsoletes RFC 2028.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-rsalz-2028bis/
No IPR declarations have been submitted directly on this I-D.
_______________________________________________
IETF-Announce mailing list
IETF-Announce@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf-announce
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
