The following errata report has been submitted for RFC6874, "Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".
-------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3631 -------------------------------------- Type: Technical Reported by: Michael Sweet <msw...@apple.com> Section: 4 Original Text ------------- An HTTP client, proxy, or other intermediary MUST remove any ZoneID attached to an outgoing URI, as it has only local significance at the sending host. Corrected Text -------------- An HTTP client, proxy, or other intermediary MUST retain any ZoneID attached to an outgoing URI, as it will be the only way for an HTTP server to return a URI containing a link-local address that can subsequently be used by the HTTP client. Notes ----- The original advice ignores a very real issue: HTTP Servers that generate URIs from the client's Host: need to include the Client's zoneid in order for the link local address to be usable/routable. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC6874 (draft-ietf-6man-uri-zoneid-06) -------------------------------------- Title : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers Publication Date : February 2013 Author(s) : B. Carpenter, S. Cheshire, R. Hinden Category : PROPOSED STANDARD Source : IPv6 Maintenance Area : Internet Stream : IETF Verifying Party : IESG -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
