Re: Last Call: <draft-thaler-iftype-reg-05.txt> (Guidelines and Registration Procedures for Interface Types and Tunnel Types) to Proposed Standard

[S Moonesamy <[e-mail]>]

Hello,
At 09:11 AM 10-10-2019, The IESG wrote:
>The IESG has received a request from an individual submitter to consider the
>following document: - 'Guidelines and Registration Procedures for Interface
>Types and Tunnel
>    Types'
>   <draft-thaler-iftype-reg-05.txt> as Proposed Standard
>
>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
>[e-mail] mailing lists by 2019-11-07. Exceptionally, comments may be

RFC 2863 is a Draft Standard which states that it specifies a 
protocol.  draft-thaler-iftype-reg is about guidance for registration 
requests.  The write-up does not explain why the intended status of 
the document is "Proposed Standard".  That is an usual (intended) 
status when a document is about procedures (e.g. Section 6.1).

Section 6.3.1 states that "A link to some document is required".  The 
requirement is phrased in such a way that it leaves a lot of room for 
interpretation.  Does the person reviewing those (future) requests 
wish to deal with that?

Regards,
S. Moonesamy