RFC Errata
RFC 4303, "IP Encapsulating Security Payload (ESP)", December 2005
Source of RFC: ipsec (sec)
Errata ID: 859
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-03-01
Held for Document Update by: Pasi Eronen
The 'version numbering' issue (as reported as item (6) for RFC 4302) I would have appreciated the introduction of an explicit version numbering for ESP, e.g. rename: ESP as per RFC 1827 to ESPv1, ESP as per RFC 2406 to ESPv2 or ESPv2.0, and ESP as per RFC 4303 to ESPv3 or ESPv2.1 (or similar). This would make it easier to specify / identify versions and/or version specific behaviour in implementations, without having to refer to the RFC numbers explicitely. (Similar numbering has proven very useful with protocols like BGP, SNMP, IMAP, POP, etc.)
Notes:
from pending