CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 14:11:24 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=05jqk4c5qrul68slbrrr10qnog; path=/
set-cookie: __cf_bm=LKx7_HkZaoPJaHe1jof.GDgvIHhfIGx_avMN_345aDw-1760191884-1.0.1.1-eY2AgckDuiN5o3AMW8lcRAimM64v62Iv5pWsRTkVvVs7DO_vLcsUeKEZIG16J4xCCW4YvAUV2_jGSrS6l1eJwZZvNyXMIHaVYm._9_nW4Kg; path=/; expires=Sat, 11-Oct-25 14:41:24 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: 98cef243fe5ef424-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
RFC 4306, "Internet Key Exchange (IKEv2) Protocol", December 2005
Note: This RFC has been obsoleted by RFC 5996
Note: This RFC has been updated by RFC 5282
Source of RFC: ipsec (sec)
Errata ID: 2191
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Constantin Hagemeier
Date Reported: 2010-04-28
Held for Document Update by: Sean Turner
Section 3.2. says:
whose type code appears in the first octet. The reasoning behind not setting the critical bit for payloads defined in this document is that all implementations MUST understand all payload types defined in this document and therefore must ignore the Critical bit's value. Skipped payloads are expected to have valid Next
It should say:
?
Notes:
Difficult to understand. More explanation needed:
An implementation of IKE which is older than 2.0 does not know about the
critical bit and will skip an unknown payload. This behaviour fits to
cleared critical bit.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us