I believe the final document should address the stuff in RFC 5739. Also, I’m not sure you need to update 7296 to add some new code points.
Neither of these is a barrier for adoption. I have read the draft and support its adoption. Yoav > On 13 Oct 2018, at 3:09, Tero Kivinen <kivi...@iki.fi> wrote: > > Our new charter has been approved and that includes item: > > RFC7296 defines a generic notification code that is related to a > failure to handle an internal address failure. That code does not > explicitly allow an initiator to determine why a given address > family is not assigned, nor whether it should try using another > address family. The Working Group will specify a set of more > specific notification codes that will provide sufficient > information to the IKEv2 initiator about the encountered failure. > A possible starting pointing is > draft-boucadair-ipsecme-ipv6-ipv4-codes. > > So this email will start one week long WG adoptation call for that > document [1] for WG adoptation. > > Send your comments to this list before the 2018-10-21. > > [1] https://datatracker.ietf.org/doc/draft-boucadair-ipsecme-ipv6-ipv4-codes/ > -- > kivi...@iki.fi > > _______________________________________________ > IPsec mailing list > IPsec@ietf.org > https://www.ietf.org/mailman/listinfo/ipsec _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec
