[radext] Ben Campbell's Discuss on draft-ietf-radext-coa-proxy-05: (with DISCUSS and COMMENT)

[Ben Campbell <[e-mail]>]

Ben Campbell has entered the following ballot position for
draft-ietf-radext-coa-proxy-05: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-radext-coa-proxy/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

(This is a procedural DISCUSS. Hopefully it can be resolved easily, but I do
think it needs to be resolved prior to publication..)

This draft is standards track, yet it primarily serves to extend RFC 5176. That
RFC is informational. The shepherd writeup argues that this is okay because it
seems like 5176 should have been standards track. But the applicability
statement RFC 5176 explains why it was informational, and the reasons seem
convincing. Therefore I do not think it is appropriate to publish this draft as
Standards Track. I think it would be fine to progress it as Informational (or
even Experimental) if it included an applicability statement explaining why in
order to avoid the appearance of a standard masquerading as an Informational
RFC.


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

(My review is not yet complete; I wanted to get the DISUSS point out with as
much discussion time as possible. I expect to follow up with an update sometime
before the telechat.)