Re: [IPsec] FW: New Version Notification fordraft-mglt-ipsecme-implicit-iv-01.txt

2016-10-20 Thread Tobias Guggemos
Hey Valery, Thanks for the clarification, we'll add this statement in the draft! Just because I'm interested: For me, this seems to be a general problem for implementing counter ciphers in multicast scenarios, regardless of implicit-iv or not. Do you know how the IV is usually chosen in multicast

Re: [IPsec] FW: New Version Notification fordraft-mglt-ipsecme-implicit-iv-01.txt

2016-10-20 Thread Valery Smyslov
Hi Tobias, > Hey Valery, > Thanks for the clarification, we'll add this statement in the draft! Thank you. > Just because I'm interested: For me, this seems to be a general problem for > implementing counter ciphers > in multicast scenarios, regardless of implicit-iv or not. > Do you know how t

Re: [IPsec] [saag] trapdoor'ed DH (and RFC-5114 again)

2016-10-20 Thread Antonio Sanso
hi Peter, (one of the authors here) thanks a lot for you comments. As for the case with Nikos we take on board and well appreciate comments/feedbacks. Will pass the message. Thanks a lot and regards antonio On Oct 20, 2016, at 2:13 AM, Peter Gutmann wrote: > Nikos Mavrogiannopoulos writes: >

[IPsec] I-D Action: draft-ietf-ipsecme-rfc4307bis-15.txt

2016-10-20 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Security Maintenance and Extensions of the IETF. Title : Algorithm Implementation Requirements and Usage Guidance for IKEv2 Authors : Yoav Nir

Re: [IPsec] I-D Action: draft-ietf-ipsecme-rfc4307bis-15.txt

2016-10-20 Thread Paul Wouters
On Thu, 20 Oct 2016, internet-dra...@ietf.org wrote: A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Security Maintenance and Extensions of the IETF. Title : Algorithm Implementation Requirements and Usage Gu

[IPsec] [IANA #932374] Protocol Action: 'Curve25519 and Curve448 for IKEv2 Key Agreement' to Proposed Standard (draft-ietf-ipsecme-safecurves-05.txt)

2016-10-20 Thread Amanda Baber via RT
Dear Authors: ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED We've completed the registry actions for the following RFC-to-be: draft-ietf-ipsecme-safecurves-05 We've added the following entries to the Transform Type 4 - Diffie-Hellman Group Transform ID registry: Number NameRec

Re: [IPsec] [IANA #932374] Protocol Action: 'Curve25519 and Curve448 for IKEv2 Key Agreement' to Proposed Standard (draft-ietf-ipsecme-safecurves-05.txt)

2016-10-20 Thread Yoav Nir
Hi, Amanda This seems correct. Thanks. Yoav > On 20 Oct 2016, at 22:43, Amanda Baber via RT > wrote: > > Dear Authors: > > ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED > > We've completed the registry actions for the following RFC-to-be: > > draft-ietf-ipsecme-safecurves-05 > > We've

[IPsec] ID Tracker State Update Notice:

2016-10-20 Thread IETF Secretariat
IANA action state changed to Waiting on Authors ID Tracker URL: https://datatracker.ietf.org/doc/draft-ietf-ipsecme-safecurves/ ___ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec

[IPsec] ID Tracker State Update Notice:

2016-10-20 Thread IETF Secretariat
IANA action state changed to Waiting on RFC Editor ID Tracker URL: https://datatracker.ietf.org/doc/draft-ietf-ipsecme-safecurves/ ___ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec

[IPsec] ID Tracker State Update Notice:

2016-10-20 Thread IETF Secretariat
IANA action state changed to RFC-Ed-Ack ID Tracker URL: https://datatracker.ietf.org/doc/draft-ietf-ipsecme-safecurves/ ___ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec