Hi all,

 

I have reviewed review of draft-leiba-3967upd-downref-00 as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review.  Document editors and WG chairs should treat these comments just like any other last call comments.

 

“RFC 3967 specifies a process for allowing normative references to documents at lower maturity levels ("downrefs"), which involves calling out the downref explicitly in the last call notice.  That requirement has proven to be unnecessarily strict, and this document updates RFC 3967, allowing the IESG more flexibility in accepting downrefs in Standards Track documents.”

 

My overall view of the document is Ready for publication.

 

Just some discussions(not specific about this document):

Publishing a document on Standards Track or BCP requires IETF consensus. Informational docs as Std Track or BCP, which in a sense could override the IETF community decision to publish such document as Informational. I'm not sure whether this is appropriate…My 0.02.

 

Regards,

Will (Shucheng LIU)

----------------------------------------------------------------------------------------------

Shucheng LIU (刘树成Will), Ph.D.

Senior Researcher & Standard Representative, Project Manager

Huawei Technologies Co.,Ltd

liushucheng at huawei.com

http://www.linkedin.com/in/shucheng

----------------------------------------------------------------------------------------------