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 5056, "On the Use of Channel Bindings to Secure Channels", November 2007

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

Errata ID: 3247
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Sujing Zhou
Date Reported: 2012-06-06
Rejected by: Sean Turner
Date Rejected: 2012-07-02

Section 2 says:

there are no MITMs between the two end-points at that higher 
network layer.  

It should say:

there are no MITMs between the two end-points at that lower 
network layer.  

Notes:

Typo in definition

--VERIFIER NOTES--
From the RFC:

Generally, some data that "names" a channel or one or both of its end-points such that if this data can be shown, at a higher network layer, to be the same at both ends of a channel, then there are no MITMs between the two end-points at that higher network layer. This term is used as a noun.

Report New Errata