Just some questions about AH/ESP here:
What actually is (so far, without your draft) the technical benefits
and/or differences of ESP and AH in IPv6 being classified as IPv6
extension headers, as opposed in IPv4, where they are currently
defined as "yet another (next level) Protocol ?
Any difference in APIs for example ? I guess i might be able to implement
ESP/AH in IPv6 in user-level because i can expose extension header
to user-level UDP sockets (not 100% sure), whereas in IPv4 i would need
a (raw) IP socket to get them up to userland ??
Any other functional differences ? Aka: i couldn't find a simple:
"If i want to define a new protocol header, should i call it an
extension header or an ipv6 extension header - for Dummies" ?
(at least for those examined only on the receiver obviously. HBH i do get.
I think you did not write it explicitly, but i would assume the IANA
Assigned Internet Protocols Numbers column "IPv6 Extension Header" would
be renamed to "IP/IPv6 Extension Header". But when this was done
to AH/ESP, and there actually is a functional difference expressed by
this extension header (as opposed to non-extension header) status, then
what be the imapct of this ? Aka: I upgrade my linux kernel to extension
header and all my AH/ESP breaks ? Or i do get the benefit of above
(userland access) ?
Would there be any (backward compatibility) reason to have new codepoints in
IPv4 for ESP/AH
with this extension header status and leave the existing (non extension
header) codepoints alone ?
Cheers
Toerless
On Thu, Feb 22, 2024 at 05:40:31PM -0800, Tom Herbert wrote:
> Hi,
>
> I updated the IPv4 extension headers draft. I structured it to be
> self-contained without any normative references for IPv6 RFCs. It's a
> little bigger, but about 80% of the text is cut-and-paste from other
> RFCs and drafts.
>
> Comments are appreciated!
>
> Tom
>
> ---------- Forwarded message ---------
> From: <[email protected]>
> Date: Thu, Feb 22, 2024 at 5:29 PM
> Subject: New Version Notification for draft-herbert-ipv4-eh-03.txt
> To: Tom Herbert <[email protected]>
>
>
> A new version of Internet-Draft draft-herbert-ipv4-eh-03.txt has been
> successfully submitted by Tom Herbert and posted to the
> IETF repository.
>
> Name: draft-herbert-ipv4-eh
> Revision: 03
> Title: IPv4 Extension Headers and Flow Label
> Date: 2024-02-23
> Group: Individual Submission
> Pages: 47
> URL: https://www.ietf.org/archive/id/draft-herbert-ipv4-eh-03.txt
> Status: https://datatracker.ietf.org/doc/draft-herbert-ipv4-eh/
> HTMLized: https://datatracker.ietf.org/doc/html/draft-herbert-ipv4-eh
> Diff: https://author-tools.ietf.org/iddiff?url2=draft-herbert-ipv4-eh-03
>
> Abstract:
>
> This specification defines extension headers for IPv4 and an IPv4
> flow label. The goal is to provide a uniform and feasible method of
> extensibility that is common between IPv4 and IPv6.
>
>
>
> The IETF Secretariat
>
--
---
[email protected]
_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area
