Hi, Please find an updated version of the draft describing how initiators and responders can notify each other of the DSCP values considered for the agreed SA. We do not involve any more the TS but only involve an Notify payload. We rename the draft to reflect that change which explain why we have a 00 draft. We believe we have addressed all concerned raised so far. In our opinion the draft is ready to be adopted.
Yours, Daniel ________________________________________ From: internet-dra...@ietf.org <internet-dra...@ietf.org> Sent: Friday, October 6, 2023 11:04 AM To: Ulf Parkholm X; Harold Liu; Daniel Migault; Joel Halpern Subject: New Version Notification for draft-mglt-ipsecme-dscp-np-00.txt A new version of Internet-Draft draft-mglt-ipsecme-dscp-np-00.txt has been successfully submitted by Daniel Migault and posted to the IETF repository. Name: draft-mglt-ipsecme-dscp-np Revision: 00 Title: Differentiated Services Field Codepoints Internet Key Exchange version 2 Notification Date: 2023-10-06 Group: Individual Submission Pages: 8 URL: https://www.ietf.org/archive/id/draft-mglt-ipsecme-dscp-np-00.txt Status: https://datatracker.ietf.org/doc/draft-mglt-ipsecme-dscp-np/ HTMLized: https://datatracker.ietf.org/doc/html/draft-mglt-ipsecme-dscp-np Abstract: IPsec supports "classifier" mechanism to send traffic with specific Differentiated Services Field Codepoints (DSCP) over different tunnels. However, such classification is not explicitly notified to the other peer. This document specifies the DSCP Notification Payload, which, in a CREATE_CHILD_SA Exchange, explicitly mentions which DSCP code points will be tunneled in the newly created tunnel. The IETF Secretariat _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
