Hi, On 2022-8-25, at 20:29, Christian Hopps <cho...@chopps.org> wrote: > > [[RFC3168]] and [[RFC4301]], updated by [[RFC6040]] defines behaviors for > marking > the outer ECN field value based on the ECN field of the inner packet. > As AGGFRAG mode may have multiple inner packets present in a single > outer packet, and there is no obvious correct way to map these > multiple values to the single outer packet ECN field value, the > tunnel ingress endpoint SHOULD operate in the "compatibility" mode > rather than the "default" mode from RFC6040. In particular this means > that the ingress (sending) endpoint of the tunnel always sets the > newly constructed outer encapsulating packet header ECN field > to Not-ECT [[RFC6040]]. > > We have a couple more ADs with ECN as a DISCUSS: > > - Lars - You wanted us to be explicit about what to do with ECN field based > on RFC6040. The propsed text above satisfies this requirement I beleive. > Agreed?
yes, possibly with the addition Martin later suggested ("unless all inner packets have the same marking"). Thanks, Lars
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec