Re: [Emu] Fixes and suggestions for draft-ietf-emu-tls-eap-types-09

2023-01-04 Thread Alan DeKok
On Nov 18, 2022, at 8:50 AM, Heikki Vatiainen wrote: > > Please find below some fixes and suggestions for > draft-ietf-emu-tls-eap-types-09 > > Apart from the first item (TEAP label), which could also be considered a > typo, I think these are clarifications, not functional changes. I agree.

Re: [Emu] draft-ietf-emu-rfc7170bis-01 - few more comments

2023-01-04 Thread Alan DeKok
On Jan 4, 2023, at 11:45 AM, Oleg Pekar wrote: > > Hi all, > Few more comments: > 1) Section "3.3.4. Protected Termination and Acknowledged Result Indication" > > Except as noted below, the Crypto-Binding TLV MUST be >exchanged and verified before the final Result TLV exchange, >regardl

[Emu] draft-ietf-emu-rfc7170bis-01 - few more comments

2023-01-04 Thread Oleg Pekar
Hi all, Few more comments: 1) Section "3.3.4. Protected Termination and Acknowledged Result Indication" Except as noted below, the Crypto-Binding TLV MUST be exchanged and verified before the final Result TLV exchange, regardless of whether or not there is an inner EAP method authenticat

Re: [Emu] RFC 7170bis Issue 4: do we want to keep PAC/PAC-Ackonwledgment?

2023-01-04 Thread Alan DeKok
On Jan 4, 2023, at 5:09 AM, Eliot Lear wrote: > > We have discussed not adding a lot into TEAP, but it might be good to > consider removing some stuff. PAC tops the list of things I'd like to see > removed. This is relevant to Erratum 5844 in that the example given contains > a PAC/PAC-Acknow

Re: [Emu] RFC 7170bis: More small potatoes: use Obsoletes

2023-01-04 Thread Alan DeKok
On Jan 4, 2023, at 3:20 AM, Eliot Lear wrote: > > This document is a complete specification, and as such should obsolete RFC > 7170 (if approved). Address in https://github.com/emu-wg/rfc7170bis/commit/225cd8a0ce908febf12f1e4c16ab2eae3db3ce5f Alan DeKok. _

Re: [Emu] RFC 7170bis: Small potatoes: IANA registry

2023-01-04 Thread Alan DeKok
On Jan 4, 2023, at 3:18 AM, Eliot Lear wrote: > > This is almost editorial. > > The TLV registry and the various registrations should now be pointed to this > document as the authority rather than RFC 7170, and we should retain the > registration policy statement for TLVs here. Frankly, specif

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

2023-01-04 Thread Alexander Clouter
On Wed, 4 Jan 2023, at 09:17, Alexander Clouter wrote: > > For TEAP (and similarly for FAST) we need to do more than just state > "PACs are dead use NewSessionTicket"[1]. Looks like I jumped at this too quickly, there is some text from the original RFC7170: https://datatracker.ietf.org/doc/html

[Emu] RFC 7170bis Issue 4: do we want to keep PAC/PAC-Ackonwledgment?

2023-01-04 Thread Eliot Lear
We have discussed not adding a lot into TEAP, but it might be good to consider removing some stuff. PAC tops the list of things I'd like to see removed.  This is relevant to Erratum 5844 in that the example given contains a PAC/PAC-Acknowledgment.  This also, has bearing on whether or not we bu

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

2023-01-04 Thread Alexander Clouter
On Tue, 27 Sep 2022, at 13:25, 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

[Emu] RFC 7170bis: More small potatoes: use Obsoletes

2023-01-04 Thread Eliot Lear
This document is a complete specification, and as such should obsolete RFC 7170 (if approved). Eliot ___ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu

[Emu] RFC 7170bis: Small potatoes: IANA registry

2023-01-04 Thread Eliot Lear
This is almost editorial. The TLV registry and the various registrations should now be pointed to *this* document as the authority rather than RFC 7170, and we should retain the registration policy statement for TLVs here. Frankly, specification required is just a little thin. We probably shou