Hi Yoav, 

Can you please clarify which "stuff" in 5739 you are referring to? 

The draft updates RFC7296 because it updates the behavior specified in Section 
3.15.4 of that RFC. 

Cheers,
Med

> -----Message d'origine-----
> De : IPsec [mailto:[email protected]] De la part de Yoav Nir
> Envoyé : samedi 13 octobre 2018 15:48
> À : Tero Kivinen
> Cc : [email protected]
> Objet : Re: [IPsec] Call for WG Adoptation for draft-boucadair-ipsecme-ipv6-
> ipv4-codes
> 
> 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 <[email protected]> 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/
> > --
> > [email protected]
> >
> > _______________________________________________
> > IPsec mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/ipsec
> 
> _______________________________________________
> IPsec mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ipsec
_______________________________________________
IPsec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipsec

Reply via email to