Re: [IPsec] Starting two week working group adoptation call for draft-mglt-ipsecme-implicit-iv

2017-03-29 Thread Daniel Migault
Hi, I am also supporting the draft as a co-author. Yours, Daniel On Wed, Mar 29, 2017 at 5:03 PM, David Schinazi wrote: > Hello all, > > I strongly support adoption of this document. > I have read it and implemented it. > The document reads well, and allows independent implementations. > I per

[IPsec] Quantum Resistance SK_d, SK_pi, SK_pr etc mixing

2017-03-29 Thread Tero Kivinen
So I have proposed earlier that we should mix the ppk to SK_d, SK_pi, and SK_pr, i.e., something like this: SKEYSEED = prf(Ni | Nr, g^ir) {SK_d' | SK_ai | SK_ar | SK_ei | SK_er | SK_pi' | SK_pr'} = prf+ (SKEYSEED, Ni | Nr | SPIi | SPIr) If no

[IPsec] Preleminary minutes of the IPsecME meeting

2017-03-29 Thread Tero Kivinen
Here are the preliminary minutes of the IPsecME meeting in Chicago. Send corrections, and additions etc to me. Thanks to Michael and Tommy for taking the minutes. -- IPSECme meeting. IETF98. Tero and David as Chairs. Room Montreu

[IPsec] IPsecME document status

2017-03-29 Thread Tero Kivinen
Here is the current status of the working group documents: -- Document Status: - draft-ietf-ipsecme-rfc4307bis (David) Approved. Revised ID already done. - draft-ietf-ipsecme-rfc7321bis (David) Approved. Revised ID needed.

Re: [IPsec] Starting two week working group adoptation call for draft-mglt-ipsecme-implicit-iv

2017-03-29 Thread David Schinazi
Hello all, I strongly support adoption of this document. I have read it and implemented it. The document reads well, and allows independent implementations. I personally think Implicit IV is a great step forward for IKEv2/IPsec, even outside of IoT. Regards, David Schinazi > On Mar 29, 2017, a

Re: [IPsec] Starting two week working group adoptation call for draft-mglt-ipsecme-implicit-iv

2017-03-29 Thread Yoav Nir
Not surprising (me being a co-author) but I support adoption. > On 29 Mar 2017, at 16:44, Tero Kivinen wrote: > > As discussed in the meeting, we are starting two week working group > adoptation call for the draft-mglt-ipsecme-implicit-iv. > > Please read the draft and send your comments to thi

[IPsec] Starting two week working group adoptation call for draft-mglt-ipsecme-implicit-iv

2017-03-29 Thread Tero Kivinen
As discussed in the meeting, we are starting two week working group adoptation call for the draft-mglt-ipsecme-implicit-iv. Please read the draft and send your comments to this list, and also tell if you support adoptation of this draft as WG draft. The document is available at https://datatracke

Re: [IPsec] The IPSECME WG has placed draft-mglt-ipsecme-implicit-iv in state "Call For Adoption By WG Issued"

2017-03-29 Thread David Schinazi
Hello all, I strongly support the WG adoption of this draft. Regards, David Schinazi > On Mar 29, 2017, at 14:17, IETF Secretariat > wrote: > > > The IPSECME WG has placed draft-mglt-ipsecme-implicit-iv in state > Call For Adoption By WG Issued (entered by Tero Kivinen) > > The document i

[IPsec] The IPSECME WG has placed draft-mglt-ipsecme-implicit-iv in state "Call For Adoption By WG Issued"

2017-03-29 Thread IETF Secretariat
The IPSECME WG has placed draft-mglt-ipsecme-implicit-iv in state Call For Adoption By WG Issued (entered by Tero Kivinen) The document is available at https://datatracker.ietf.org/doc/draft-mglt-ipsecme-implicit-iv/ ___ IPsec mailing list IPsec@ietf.

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

2017-03-29 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

[IPsec] Code

2017-03-29 Thread Kathleen Moriarty
Hello, If you have an implementation to standards or drafts for this WG, please considering entering them into CodeStand. Listing can be to open source or proprietary implementations, where the open source ones would link to code repositories. Before entering your code project, check to see if t

Re: [IPsec] Comments on draft-mglt-ipsecme-implicit-iv-02.tx

2017-03-29 Thread Eric Rescorla
This LGTM On Wed, Mar 29, 2017 at 11:07 AM, Daniel Migault < daniel.miga...@ericsson.com> wrote: > I am planning to add this reference.Let me know if you prefer another > reference. > > Rizzo, J. and T. Duong. "Here come the xor ninjas", 2011. > http://netifera.com/research/beast/beast_DRAFT_062

Re: [IPsec] Comments on draft-mglt-ipsecme-implicit-iv-02.tx

2017-03-29 Thread Daniel Migault
I am planning to add this reference.Let me know if you prefer another reference. Rizzo, J. and T. Duong. "Here come the xor ninjas", 2011. http://netifera.com/research/beast/beast_DRAFT_0621.pdf. Thanks for the feed back. Yours, Daniel On Wed, Mar 29, 2017 at 10:54 AM, Eric Rescorla wrote: >

Re: [IPsec] Comments on draft-mglt-ipsecme-implicit-iv-02.tx

2017-03-29 Thread Eric Rescorla
I think Yoav's suggestion to cite BEAST as evidence that predictable IVs are bad is a good plan. -Ekr On Wed, Mar 29, 2017 at 10:52 AM, Daniel Migault < daniel.miga...@ericsson.com> wrote: > Hi Eric, > > Thank you for the review and comments. Do you have any preference on what > we should cite

Re: [IPsec] Comments on draft-mglt-ipsecme-implicit-iv-02.tx

2017-03-29 Thread Daniel Migault
Hi Eric, Thank you for the review and comments. Do you have any preference on what we should cite for the chosen clear text attack?: Our local version currently refers to Security Consideration of RFC3602. The sentence in the terminology section mentioning that IV are usually unpredictable has b