[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ietf
Subject:    Re: Genart last call review of draft-nottingham-rfc5988bis-05
From:       Mark Nottingham <mnot () mnot ! net>
Date:       2017-05-24 22:16:25
Message-ID: 178E5CCA-3FA4-4AD1-AF6E-CB1E609CB363 () mnot ! net
[Download RAW message or body]

Hi Stewart,

Thanks for the review. Responses below.

> Minor issues:
> I found the IANA considerations confusing. Specifically it looks like
> Section 4.1 refers to 
> https://www.iana.org/assignments/message-headers/message-headers.xhtml
> although it does not say so in so many words.

It says 

> This specification updates the Message Header registry entry for "Link" in HTTP \
> [RFC3864] to refer to this document.

Are you suggesting that it be updated to say "Permanent Message Header Field Names \
registry", or something else?


> Assuming that to be the case the IANA text in section 4.1 (which copies the text \
> from RFC5688) does not line up column by column with the text in the registry. I \
> assume that  [RFC&rfc.number;] means [This RFC],

Yes; already fixed in source.

> but do not see where Author/Change control fits in the registry.

It's required by the registration template in RFC3864.


> Nits/editorial comments: 
> 
> In the intro and the abstract the text "a model for indicate the
> relationships" is not good grammar.

Already fixed in source.

Thanks again!


--
Mark Nottingham   https://www.mnot.net/


[prev in list] [next in list] [prev in thread] [next in thread]