- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Wed, 9 Nov 2022 00:32:48 -0800 (PST)
- To: julian.reschke@gmx.de, sludin@akamai.com, mnot@fastly.com, nick@cloudflare.com
- Cc: francesca.palombini@ericsson.com, iesg@ietf.org, ietf-http-wg@w3.org, iana@iana.org, rfc-editor@rfc-editor.org
The following errata report has been verified for RFC8586, "Loop Detection in Content Delivery Networks (CDNs)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid5704 -------------------------------------- Status: Verified Type: Technical Reported by: Julian Reschke <julian.reschke@gmx.de> Date Reported: 2019-04-25 Verified by: Francesca Palombini (IESG) Section: 1.2 Original Text ------------- This specification uses the Augmented Backus-Naur Form (ABNF) notation of [RFC5234] with a list extension, defined in Section 7 of [RFC7230], that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates repetition). Additionally, it uses a token (OWS), uri-host, and port rules from [RFC7230] and the parameter rule from [RFC7231]. Corrected Text -------------- This specification uses the Augmented Backus-Naur Form (ABNF) notation of [RFC5234] with a list extension, defined in Section 7 of [RFC7230], that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates repetition). Additionally, it uses the token, OWS, uri-host and port rules from [RFC7230] and the parameter rule from [RFC7231]. Notes ----- The last sentence apparently was mangled during AUTH48. The correct version is from draft-ietf-httpbis-cdn-loop-02. "token", "OWS", "uri-host" and "port" are all ABNF rules. -------------------------------------- RFC8586 (draft-ietf-httpbis-cdn-loop-02) -------------------------------------- Title : Loop Detection in Content Delivery Networks (CDNs) Publication Date : April 2019 Author(s) : S. Ludin, M. Nottingham, N. Sullivan Category : PROPOSED STANDARD Source : HTTP Area : Applications and Real-Time Stream : IETF Verifying Party : IESG
Received on Wednesday, 9 November 2022 08:33:02 UTC