Hi all, 

This document is already in AUTH48-DONE but still not published yet because of 
a normative dependency (see more about the cluster at  
https://www.rfc-editor.org/auth48/C461).

A late issue was raised about the encoding of the service parameters 
(representation format vs wire format). A summary can be found at: 
https://mailarchive.ietf.org/arch/msg/add/qU_TaosKNhojs3h3ojUb0B_bpXg/.

In order to be consistent with the consensus in ADD, I suggest we update 
RFC-to-be 9464 as follows: 

OLD:
   Service Parameters (SvcParams) (variable) -  Specifies a set of
      service parameters that are encoded following the rules in
      Section 2.1 of [RFC9460].  

NEW:
   Service Parameters (SvcParams) (variable) -  Specifies a set of
      service parameters that are encoded following the same rules
      for encoding SvcParams using the wire format specified
      in Section 2.2 of [RFC9460]. 

The text may seem verbose but the intent is to avoid ambiguity and be explicit 
about which part of Section 2.2 of [RFC9460].

Unless we hear an objection by the end of the week, we will request the RFC 
Editor to make this change. 

Cheers,
Med
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Reply via email to