lain once where it shouldn't.
> (The thing in the [] should be RFC7235, not 4):
>> [RFC7234] Fielding, R., and J. Reschke, "Hypertext Transfer Protocol
>> (HTTP/1.1): Authentication", RFC 7235, June 2014.
>>
>
>
>
>
>
>
>
_
Michael Sweet, Senior Printing System Engineer, PWG Chair
___
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art
IETF RFC formally updating one of their
> documents, that's their process, not ours, no?
And FWIW, the sections in question currently reference RFC 3510 along with the
various TLS RFCs. At some point in the next year we will be updating IPP/2.0
to full IEEE standard, at which point
t; or "example.net" in the URL. Consider:
>
> (404) http://ftp.example.com/pub/ipp-model-v11-990510.pdf
This is actually a real link to an (old) archived draft of the original RFC
2911, but I can update it to be a fake example.com URL...
> In Section 5.3.7, the reference
ay "in a special position as described in Section
> 3.1.1".
Works for me, changed.
> Nits/editorial comments:
>
> * idnits complains that this document is attempting to reference
> "rfc2910bis" (this document) without declaring the reference.
> Thes
