Hi all,

I just to highlight that RFC6145 (a normative reference to RFC7599) which is 
obsoleted by RFC7915 covers this in detail.  They very appropriately have 
assigned a SHOULD on the calculation function of zero checksum IPv4 traffic.   
I also want to point out that rfc6936 addresses tunneling protocol rather than 
a header translation based softwire and therefore should not be included as any 
kind of reference to RFC7599.

I am very much opposed to making it a MUST as it has significant performance 
implications on the BR.  It makes more sense on the CE for outgoing traffic as 
it has significant implications for IPv4-mapped IPv6 address traffic.

Sincerely,

Jordan

From: Softwires <[email protected]> On Behalf Of Overcash, Michael 
(CCI-Atlanta)
Sent: Friday, November 4, 2022 7:44 AM
To: [email protected]
Subject: [EXTERNAL] [Softwires] MAP-T issue - UDP packets with zero checksum

CAUTION: The e-mail below is from an external source. Please exercise caution 
before opening attachments, clicking links, or following guidance.
Hi,

IPv4 packets are allowed to have a zero checksum, but IPv6 packets are not. The 
problem of tunnelling zero checksum IPv4 packets through IPv6 tunnels is 
described in RFC 6935.

Currently RFC 7599 doesn't address this issue, and as a result we've found that 
some existing BR and CE implementations don't handle zero checksum UDP IPv4 
packets correctly.

I think it would be helpful to add RFC 6935 as a normative reference and add a 
new section 8.5 to discuss the issue. Something like the following would help:
8.5. UDP Checksum Considerations
IPv4 UDP packets arriving at the BR or CE are can have a checksum value of 
zero, indicating no checksum was calculated. Historically, a zero checksum 
value is not
permitted in IPv6 UDP datagrams, and some implementations will discard these 
packets. The MAP-T CE and BR MUST translate and forward zero checksum UDP
datagrams in both the IPv4 and IPv6 domains as described in [RFC6935].

The text above could use some wordsmithing, but hopefully you get the idea.

Michael Overcash
Principal Architect, Premises Technology
C 678.637.5649

[cid:[email protected]]

_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires

Reply via email to