| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 01:19:06 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=oag7nnth5lmdva3e8ujhietie2; path=/
set-cookie: __cf_bm=VRdMZp2434BcyDZW8QCDMZ22pxWWxbvFn2fsGD9T9tc-1760145546-1.0.1.1-i0J7Gzg2SonYC0sPYDemDmzpFtGotrTGZawjHr1e3AQPxwDaIJPNnz3cIyW76N_kVmD2FeLUgjNdtO7R1nxEkFfHyWTfmdsgjmPzAR3nhN0; path=/; expires=Sat, 11-Oct-25 01:49:06 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 98ca86f8fd838087-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
Area Assignment: sec
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
RFC 5056, "On the Use of Channel Bindings to Secure Channels", November 2007
Source of RFC: IETF - NON WORKING GROUPArea 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.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us