Errata Search
RFC Number:		Errata ID:
Source of RFC		Status:	All/Any Verified+Reported Verified Reported Held for Document Update Rejected
Area Acronym:	All/Any app art gen int ops rai rtg sec tsv wit	Type:	All/Any Editorial Technical
WG Acronym:		Submitter Name:
Other:	All/Any IAB INDEPENDENT IRTF Legacy Editorial	Date Submitted:
Summary Table Full Records

Found 1 record.

Status: Rejected (1)

RFC 4084, "Terminology for Describing Internet Connectivity", May 2005

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: ops

Errata ID: 4054
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Mark Nottingham
Date Reported: 2014-07-17
Rejected by: joel jaeggli
Date Rejected: 2014-10-22

Section 2 says:

The provider may impose a filtering Web proxy on the 
connections; that proxy may change and redirect URLs 
to other sites than the one originally specified by the 
user or embedded link.

It should say:

The provider may require a HTTP proxy to be used.

Notes:

RFC7230 Section 2 defines a Web proxy as being nominated by the client, not the network operator; operator-imposed proxies (so-called "interception" proxies) are not legitimate in HTTP, even if they are not uncommon.

Furthermore, RFC7230 section 5.7.2 defines the constraints on the transformations HTTP proxies can make, not this document.
--VERIFIER NOTES--
the original is not wrong in the sense that it's historically appropriate. We should consider revising this document but lodging this as erratum doesn't change the intention of the original text.

Report New Errata