Skip to main content

Last Call Review of draft-rsalz-2028bis-05
review-rsalz-2028bis-05-rtgdir-lc-vainshtein-2022-02-28-00

Request Review of draft-rsalz-2028bis
Requested revision No specific revision (document currently at 07)
Type Last Call Review
Team Routing Area Directorate (rtgdir)
Deadline 2022-03-07
Requested 2022-02-09
Requested by Lars Eggert
Authors Rich Salz
I-D last updated 2022-02-28
Completed reviews Genart Last Call review of -05 by Vijay K. Gurbani (diff)
Iotdir Last Call review of -05 by Ted Lemon (diff)
Rtgdir Last Call review of -05 by Sasha Vainshtein (diff)
Tsvart Last Call review of -05 by David L. Black (diff)
I18ndir Last Call review of -05 by John R. Levine (diff)
Comments
We're trying to maximize the reviews for documents associated with the change in the RFC Editor model. Hence the request to review these pretty short documents, even though they may not need a review from a technical perspective.
Assignment Reviewer Sasha Vainshtein
State Completed
Request Last Call review on draft-rsalz-2028bis by Routing Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/rtg-dir/MQ_Z6R3OS915IFeMxzkdFvNL9wI
Reviewed revision 05 (document currently at 07)
Result Has issues
Completed 2022-02-28
review-rsalz-2028bis-05-rtgdir-lc-vainshtein-2022-02-28-00
Hello,

I have been selected as the Routing Directorate reviewer for this draft. The
Routing Directorate seeks to review all routing or routing-related drafts as
they pass through IETF last call and IESG review, and sometimes on special
request. The purpose of the review is to provide assistance to the Routing ADs.
For more information about the Routing Directorate, please see
​http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir<http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir>

Although these comments are primarily for the use of the Routing ADs, it would
be helpful if you could consider them along with any other IETF Last Call
comments that you receive, and strive to resolve them through discussion or by
updating the draft.

Document: draft-rsalz-2028bis-05
Reviewer: Alexander (|”Sasha”) Vainshtein
Review Date: 28-Feb-22
IETF LC End Date: 07-Mar-22
Intended Status: Nest Current Practice

Summary:

I have some minor concerns about this document that I think should be resolved
before publication. Comments: The draft describes entities involved in the IETF
standards process. It is easy to read. To the best of my understanding its
purpose is alignment with the current structure of the Internet Society and its
affiliated organizations (IETF, IANA, RFC Production center (nee RFC Editor)
etc.  The previous document describing these entities has been published as RFC
2028 in 1996. The author of the draft and I have exchanged a few emails
regarding my concerns. We did not reach the agreement, but in any case I would
like to than the author for responsiveness and cooperation.

Major Issues: None found

Minor Issues:

These days it is quite common in the IETF process to differentiate between
document Authors and Contributors, especially when  many persons have been
actively involved with development of the technical aspects of the document. 
The number of Authors is usually limited to no more than 5, and their names
appear on the title page of the document, while Contributors (if any) are only
listed in a dedicated section within the document. At the same time the
Contributors have a well-defined role in the process, e.g. they must report
about any non-disclosed IPR related to the document (or lack of any such IPR)
both during adoption of the document as a WG document and also during the WG
Last Call.

The draft mentioned Editors and Authors of the document (and explains that
these terms are interchangeable), but it does not mention Contributors at all.

I have raised this issue with the author of the draft, and IMHO we have “agreed
to disagree” on this point.

Regards,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@rbbn.com<mailto:Alexander.Vainshtein@rbbn.com>

Regards,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@rbbn.com

Notice: This e-mail together with any attachments may contain information of
Ribbon Communications Inc. and its Affiliates that is confidential and/or
proprietary for the sole use of the intended recipient. Any review, disclosure,
reliance or distribution by others or forwarding without express permission is
strictly prohibited. If you are not the intended recipient, please notify the
sender immediately and then delete all copies, including any attachments.