Re: [Emu] I-D Action: draft-ietf-emu-tls-eap-types-03.txt

2022-01-17 Thread Alan DeKok
On Jan 15, 2022, at 5:53 AM, John Mattsson 
 wrote:
> 
> On Oct 18, 2021, Alan DeKok wrote:
>  
> >Implementors are doing final interoperability testing on client && server
> >implementations.  We hope to have updates within a few weeks,
>  
> Any updates on this? I think this is a very important draft. TLS 1.2 is 
> obsolete and NIST requires use of TLS 1.3 everywhere from January 2024. Would 
> be good if the draft could at least be resubmitted. It expired in December. 
> People outside of the IETF sometimes thinks that means it is no longer worked 
> on.

  I'll issue an update shortly.  There will be minor typo fixes, and an 
implementation report section added.

  The main blocker at this point is content / testing for EAP-FAST and TEAP.  
EAP-TLS, TTLS, and PEAP are widely implemented, and tested to be interoperable.

  If the WG decides that the document can go ahead without an implementation 
report for FAST / TEAP, then I would suggest starting a WG last call as soon as 
the next revision is issued.

  Alan DeKok.

___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu


Re: [Emu] I-D Action: draft-ietf-emu-tls-eap-types-03.txt

2022-01-15 Thread John Mattsson
On Oct 18, 2021, Alan DeKok wrote:

>Implementors are doing final interoperability testing on client && server
>implementations.  We hope to have updates within a few weeks,

Any updates on this? I think this is a very important draft. TLS 1.2 is 
obsolete and NIST requires use of TLS 1.3 everywhere from January 2024. Would 
be good if the draft could at least be resubmitted. It expired in December. 
People outside of the IETF sometimes thinks that means it is no longer worked 
on.

Cheers,
John



___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu


Re: [Emu] I-D Action: draft-ietf-emu-tls-eap-types-03.txt

2021-10-18 Thread Alan DeKok
On Oct 18, 2021, at 2:46 PM, John Mattsson 
 wrote:
> 
> What is the status and plan for this document? To me it still seems like it 
> is more or less done and ready for WGLC.

  Implementors are doing final interoperability testing on client && server 
implementations.  We hope to have updates within a few weeks,

>  I agree with Alan that it would be good if it is published quite soon after 
> EAP-TLS 1.3. It is important to begin transitioning all the TLS based EAP 
> methods to TLS 1.3.

  I agree.

  Alan DeKok.

___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu


Re: [Emu] I-D Action: draft-ietf-emu-tls-eap-types-03.txt

2021-10-18 Thread John Mattsson
What is the status and plan for this document? To me it still seems like it is 
more or less done and ready for WGLC. I agree with Alan that it would be good 
if it is published quite soon after EAP-TLS 1.3. It is important to begin 
transitioning all the TLS based EAP methods to TLS 1.3.

Cheers,
John

From: John Mattsson 
Date: Wednesday, 23 June 2021 at 10:39
To: Alan DeKok , EMU WG 
Subject: Re: [Emu] I-D Action: draft-ietf-emu-tls-eap-types-03.txt
I agree that the document is ready for WG last call.

John

From: Emu  on behalf of Alan DeKok 

Date: Tuesday, 22 June 2021 at 15:10
To: EMU WG 
Subject: Re: [Emu] I-D Action: draft-ietf-emu-tls-eap-types-03.txt
  This is to address John's review, and to do some minor cleanups and textual 
fixes.

  I think the document should be ready for last call.  There are multiple 
interoperable implementations (client and server).  I believe it's important to 
publish this document at the same time as updates to EAP-TLS.

> On Jun 22, 2021, at 9:07 AM, 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 EAP Method Update WG of the IETF.
>
>Title   : TLS-based EAP types and TLS 1.3
>Author  : Alan DeKok
>Filename: draft-ietf-emu-tls-eap-types-03.txt
>Pages   : 15
>Date: 2021-06-22
>
> Abstract:
>   EAP-TLS [RFC5216] is being updated for TLS 1.3 in [EAPTLS].  Many
>   other EAP [RFC3748] and [RFC5247] types also depend on TLS, such as
>   FAST [RFC4851], TTLS [RFC5281], TEAP [RFC7170], and possibly many
>   vendor specific EAP methods.  This document updates those methods in
>   order to use the new key derivation methods available in TLS 1.3.
>   Additional changes necessitated by TLS 1.3 are also discussed.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-emu-tls-eap-types/
>
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-emu-tls-eap-types-03
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-emu-tls-eap-types-03
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
> ___
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu

___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu
___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu


Re: [Emu] I-D Action: draft-ietf-emu-tls-eap-types-03.txt

2021-06-23 Thread John Mattsson
I agree that the document is ready for WG last call.

John

From: Emu  on behalf of Alan DeKok 

Date: Tuesday, 22 June 2021 at 15:10
To: EMU WG 
Subject: Re: [Emu] I-D Action: draft-ietf-emu-tls-eap-types-03.txt
  This is to address John's review, and to do some minor cleanups and textual 
fixes.

  I think the document should be ready for last call.  There are multiple 
interoperable implementations (client and server).  I believe it's important to 
publish this document at the same time as updates to EAP-TLS.

> On Jun 22, 2021, at 9:07 AM, 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 EAP Method Update WG of the IETF.
>
>Title   : TLS-based EAP types and TLS 1.3
>Author  : Alan DeKok
>Filename: draft-ietf-emu-tls-eap-types-03.txt
>Pages   : 15
>Date: 2021-06-22
>
> Abstract:
>   EAP-TLS [RFC5216] is being updated for TLS 1.3 in [EAPTLS].  Many
>   other EAP [RFC3748] and [RFC5247] types also depend on TLS, such as
>   FAST [RFC4851], TTLS [RFC5281], TEAP [RFC7170], and possibly many
>   vendor specific EAP methods.  This document updates those methods in
>   order to use the new key derivation methods available in TLS 1.3.
>   Additional changes necessitated by TLS 1.3 are also discussed.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-emu-tls-eap-types/
>
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-emu-tls-eap-types-03
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-emu-tls-eap-types-03
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
> ___
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu

___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu
___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu


Re: [Emu] I-D Action: draft-ietf-emu-tls-eap-types-03.txt

2021-06-22 Thread Alan DeKok
  This is to address John's review, and to do some minor cleanups and textual 
fixes.

  I think the document should be ready for last call.  There are multiple 
interoperable implementations (client and server).  I believe it's important to 
publish this document at the same time as updates to EAP-TLS.

> On Jun 22, 2021, at 9:07 AM, 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 EAP Method Update WG of the IETF.
> 
>Title   : TLS-based EAP types and TLS 1.3
>Author  : Alan DeKok
>   Filename: draft-ietf-emu-tls-eap-types-03.txt
>   Pages   : 15
>   Date: 2021-06-22
> 
> Abstract:
>   EAP-TLS [RFC5216] is being updated for TLS 1.3 in [EAPTLS].  Many
>   other EAP [RFC3748] and [RFC5247] types also depend on TLS, such as
>   FAST [RFC4851], TTLS [RFC5281], TEAP [RFC7170], and possibly many
>   vendor specific EAP methods.  This document updates those methods in
>   order to use the new key derivation methods available in TLS 1.3.
>   Additional changes necessitated by TLS 1.3 are also discussed.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-emu-tls-eap-types/
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-emu-tls-eap-types-03
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-emu-tls-eap-types-03
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> ___
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu

___
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu