Hi Zahed, Thank you for the comment.
> However, this specification relaxes constrains imposed by RFC8598 > but > references it informatively. I think it should reference RFC8598 > as normative > reference and also should clearly indicate that in the document > header and > abstract. I am assuming this is an oversight but want to discuss > it. This is not an oversight. We are following a convention in ipsecme WG which is to not add the Update header if implementations are clearly able to distinguish the cases when an extension is being used even if the extension would change the behavior defined in the existing RFCs. Please refer to this thread for a detailed discussion on the rationale/assessment: https://mailarchive.ietf.org/arch/msg/ipsec/fCsmv6FNZsys5zRnZ05RS7H1K2c/ Cheers, Med > -----Message d'origine----- > De : Zaheduzzaman Sarker via Datatracker <[email protected]> > Envoyé : jeudi 27 avril 2023 01:15 > À : The IESG <[email protected]> > Cc : [email protected]; [email protected]; > [email protected]; [email protected]; [email protected] > Objet : Zaheduzzaman Sarker's Discuss on draft-ietf-ipsecme-add- > ike-11: (with DISCUSS) > > Zaheduzzaman Sarker has entered the following ballot position for > draft-ietf-ipsecme-add-ike-11: Discuss > > > > ------------------------------------------------------------------ > ---- > DISCUSS: > ------------------------------------------------------------------ > ---- > > Thanks for working on this specification. > > I don't have transport related issues on this specification. > > However, this specification relaxes constrains imposed by RFC8598 > but > references it informatively. I think it should reference RFC8598 > as normative > reference and also should clearly indicate that in the document > header and > abstract. I am assuming this is an oversight but want to discuss > it. > > > > _________________________________________________________________________________________________________________________ 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
