[Gen-art] Gen-ART LC review of draft-ietf-grow-route-leak-problem-definition-04

2016-03-21 Thread Pete Resnick
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at

Re: [Gen-art] IANA and AUTH48 (Was: Re: Gen-ART LC review of draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-02)

2016-03-21 Thread Romascanu, Dan (Dan)
Of course. It's just that sometimes ADs (maybe not nowadays, but I may have sinned once or more when I was an AD) leave 'simple' edits to the RFC Editor. Which should be fine unless you forget to mention these in the RFC Editor notes :-) Regards, Dan > -Original Message- > From:

Re: [Gen-art] IANA and AUTH48 (Was: Re: Gen-ART LC review of draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-02)

2016-03-21 Thread joel jaeggli
On 3/21/16 8:39 AM, Romascanu, Dan (Dan) wrote: > Hi, > > Obviously, an explicit RFC Editor note would solve the problem in the > majority if not all the foreseeable cases. The burden is on the AD > and to some extent to the IESG who should minute the decision as > 'Approved. RFC Editor Note.'

Re: [Gen-art] IANA and AUTH48 (Was: Re: Gen-ART LC review of draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-02)

2016-03-21 Thread Romascanu, Dan (Dan)
Hi, Obviously, an explicit RFC Editor note would solve the problem in the majority if not all the foreseeable cases. The burden is on the AD and to some extent to the IESG who should minute the decision as 'Approved. RFC Editor Note.' and maybe add 'IANA-related edit' in the minutes to make