[Emu] Call for agenda items for IETF 120

[Peter Yee]

Please let the chairs know if you have any agenda items for the EMU meeting at 
IETF 120. As a reminder, EMU is shown in the preliminary agenda as meeting on 
Tuesday from 13:00 to 15:00.

Thanks,

Joe and Peter


___
Emu mailing list -- emu@ietf.org
To unsubscribe send an email to emu-le...@ietf.org

[Emu] Please consider volunteering for the 2024/2025 IETF NomCom

[Peter Yee]

Dear EMU WG members,

Please pardon this interruption with a non-EMU topic.

The NomCom chair has asked that WG members be informed of the following 
snafu that means there are far fewer NomCom volunteers than would normally be 
in the pool. If you are at all interested in serving on the NomCom, then please 
read the information below so that you can verify if you are indeed in the 
pool. Basically, a datatracker bug tanked the current pool. As a former NomCom 
member and chair, I can tell you that it's highly enlightening in several ways 
to serve on the NomCom. The upcoming NomCom generally kicks off at the July 
IETF meeting, so now is the time to volunteer.

Thank you for your time and attention.

Kind regards,
-Peter

The IETF tools development team identified an error in the interface between 
the IETF registration system and the datatracker that mistakenly marked people 
as volunteers for the 2024 NomCom. (Please note that volunteering via the 
registration system is not offered for IETF 120 registration.)

This error was corrected, and the fix was deployed on June 4. The correction 
for the bug can be viewed at 
https://github.com/ietf-tools/datatracker/pull/7484.

We have removed the incorrect volunteer records as of June 5. However, this has 
led to a severely reduced number of eligible volunteers. Please review your 
status and consider volunteering for NomCom 2024-2025. Please check your status 
at https://datatracker.ietf.org/accounts/profile/ after signing in under the 
"NomCom Eligible" section. If you have already explicitly volunteered using the 
datatracker, you will see "You have volunteered for the Nominating Committee 
2024/2025.” If you are not yet volunteered, you will see a Volunteer button.

You can also volunteer via
CLICK HERE TO VOLUNTEER: https://datatracker.ietf.org/nomcom/volunteer

or directly emailing Dean Bogdanovic at nomcom-chair-2...@ietf.org

Thanks to everyone who has volunteered so far. However, we currently have only 
eligible 100 volunteers. We need many more. So, please, please volunteer.

Dean Bogdanovic
nomcom-chair-2...@ietf.org



___
Emu mailing list -- emu@ietf.org
To unsubscribe send an email to emu-le...@ietf.org

[Emu] Re: Murray Kucherawy's No Objection on charter-ietf-emu-06-00: (with COMMENT)

[Peter Yee]

Thanks for the comment, Murray. The milestones are there only for the new items 
being added to charter. The other items are either relatively recently finished 
or in their final stages, so we retained them for continuity. We could remove 
the published items from the charter if they cause any confusion. 

Kind regards,
-Peter

On 5/15/24, 7:03 AM, "Murray Kucherawy via Datatracker" mailto:nore...@ietf.org>> wrote:


Murray Kucherawy has entered the following ballot position for
charter-ietf-emu-06-00: No Objection


When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)






The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-emu/ 







--
COMMENT:
--


There are nine "shall produce" items, but only three milestones. Do we need to 
worry about this?






___
Emu mailing list -- emu@ietf.org 
To unsubscribe send an email to emu-le...@ietf.org 




___
Emu mailing list -- emu@ietf.org
To unsubscribe send an email to emu-le...@ietf.org

[Emu] Re: Adoption call for eap.arpa

[Peter Yee]

Joe reminded me that I did not indicate the conclusion of the adoption call for 
draft-dekok-emu-eap-arpa. Let me rectify that now by declaring it adopted, 
subject to the EMU recharter[1] granting us the right to place the document in 
scope of the WG. There were no objections during the call and quite to the 
contrary, we already have some helpful input from Mohit Sethi that led to a 
useful discussion. Thank you to everyone who provided input.

-Peter

[1] https://datatracker.ietf.org/doc/charter-ietf-emu/ now shows "Start 
Chartering/Rechartering (Internal Steering Group/IAB Review)".

On 3/7/24, 2:38 PM, "Peter Yee" mailto:pe...@akayla.com>> 
wrote:


This is an adoption call for the eap.arpa Internet-Draft
(draft-dekok-emu-eap-arpa). This is an ancillary draft that Alan
DeKok briefed during the Prague (IETF 118) meeting. Seeing as
it primarily exists as a forward-looking extraction of certain
descriptive material and IAB .arpa domanrequests from other
EMU documents, we consider it within the scope of the WG
charter. Alan did a recent minor update to the document and
will speak briefly about it during IETF 119.


With that said, your WG chairs would appreciate hearing your
feedback on whether this document is adopted or not. While
it's not critical to adopt, it really simplifies the domain
registration for things like TLS-POK and would have been
great back when we did EAP-NOOB.


We are particularly interested in hearing from parties who are
willing to review the specification. So, if you've got interest in
seeing the work adopted, please formalize that by responding
to the EMU mailing list with your position. 


The deadline for feedback is March 21st. Yes, that's during IETF
119 but after the EMU time slot, so hopefully you will have 
formed an opinion by then, if not sooner. We hope to hear
from lots of you!


Joe and Peter


1) https://datatracker.ietf.org/doc/draft-dekok-emu-eap-arpa/ 
<https://datatracker.ietf.org/doc/draft-dekok-emu-eap-arpa/>




___
Emu mailing list -- emu@ietf.org
To unsubscribe send an email to emu-le...@ietf.org

[Emu] Adoption call for eap.arpa

[Peter Yee]

This is an adoption call for the eap.arpa Internet-Draft
(draft-dekok-emu-eap-arpa). This is an ancillary draft that Alan
DeKok briefed during the Prague (IETF 118) meeting. Seeing as
it primarily exists as a forward-looking extraction of certain
descriptive material and IAB .arpa domanrequests from other
EMU documents, we consider it within the scope of the WG
charter. Alan did a recent minor update to the document and
will speak briefly about it during IETF 119.

With that said, your WG chairs would appreciate hearing your
feedback on whether this document is adopted or not. While
it's not critical to adopt, it really simplifies the domain
registration for things like TLS-POK and would have been
great back when we did EAP-NOOB.

We are particularly interested in hearing from parties who are
willing to review the specification. So, if you've got interest in
seeing the work adopted, please formalize that by responding
to the EMU mailing list with your position. 

The deadline for feedback is March 21st. Yes, that's during IETF
119 but after the EMU time slot, so hopefully you will have 
formed an opinion by then, if not sooner. We hope to hear
from lots of you!

Joe and Peter

1) https://datatracker.ietf.org/doc/draft-dekok-emu-eap-arpa/


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

[Emu] Updated EMU charter

[Peter Yee]

I've drafted an update to the EMU charter to give us room to work on EAP-EDHOC 
and EAP-FIDO (or whatever we end up calling it). I'd appreciate the WG looking 
over the updated charter 
(https://github.com/emu-wg/charter/blob/master/emu-charter.md) and replying to 
the list with any thoughts you might have on it. I propose to stop taking input 
on the charter one week from today unless there's active discussion taking 
place on the list. That way I can get the revised charter over to Paul Wouters 
(as the relevant Security AD) soon as the next step to getting it approved.

Questions and input most welcome!

-Peter




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

Re: [Emu] Adoption call for EAP-EDHOC

[Peter Yee]

Off-by-one-bug. That deadline is December 13th!

-Peter

On 11/29/23, 9:13 AM, "Peter Yee" mailto:pe...@akayla.com>> 
wrote:


This is an adoption call for EAP-EDHOC (draft-ingles-eap-edhoc) [1].
This draft was originally briefed in Yokohama and while it didn't 
receive strong backing at that time, a short re-airing in Prague
showed that there's distinct interest in taking on this work. While
this work is not currently in scope for the EMU WG, it’s definitely
something we could take on under a rechartering of the WG.


So, if you've got interest in seeing the work adopted, please
formalize that by responding to the EMU mailing list with your
position. We are particularly interested in hearing from parties
who are willing to review and/or contribute to the development
of the specification.


The deadline for feedback is November 13th. We hope to hear
from lots of you.


Joe and Peter


1) https://datatracker.ietf.org/doc/draft-ingles-eap-edhoc/ 
<https://datatracker.ietf.org/doc/draft-ingles-eap-edhoc/>
















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

[Emu] Adoption call for EAP-EDHOC

[Peter Yee]

This is an adoption call for EAP-EDHOC (draft-ingles-eap-edhoc) [1].
This draft was originally briefed in Yokohama and while it didn't 
receive strong backing at that time, a short re-airing in Prague
showed that there's distinct interest in taking on this work. While
this work is not currently in scope for the EMU WG, it’s definitely
something we could take on under a rechartering of the WG.

So, if you've got interest in seeing the work adopted, please
formalize that by responding to the EMU mailing list with your
position. We are particularly interested in hearing from parties
who are willing to review and/or contribute to the development
of the specification.

The deadline for feedback is November 13th. We hope to hear
from lots of you.

Joe and Peter

1) https://datatracker.ietf.org/doc/draft-ingles-eap-edhoc/








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

[Emu] Publication has been requested for draft-ietf-emu-rfc7170bis-14

[Peter Yee via Datatracker]

Peter Yee has requested publication of draft-ietf-emu-rfc7170bis-14 as Proposed 
Standard on behalf of the EMU working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-emu-rfc7170bis/


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

Re: [Emu] eap.arpa domain in draft-ietf-emu-bootstrapped-tls

[Peter Yee]

Alan,
I've also sent an inquiry to the IAB on the matter to see if they have 
any thoughts. I'll post to the list if they come back with any opinions. Your 
draft will also be helpful either way as we can decide whether to incorporate 
their thoughts (if they've some concrete and coherent to offer) or we can use 
the draft as the start of a wider discussion on the topic. Thanks for posting 
it!

-Peter

On 8/30/23, 10:48 AM, "Emu on behalf of Alan DeKok" mailto:emu-boun...@ietf.org> on behalf of al...@deployingradius.com 
> wrote:


On Aug 30, 2023, at 6:29 AM, Owen Friel (ofriel) 
mailto:40cisco@dmarc.ietf.org>> wrote:
> 
> Hi EMU Chairs,
> 
> I was looking to see if any minor updates are needed to 
> draft-ietf-emu-bootstrapped-tls-03 before IETF 118 and WGLC.
> 
> There was one outstanding action from IETF 117:
> 
> Do we want to say there is an eap.arpa domain? Yes, but
> not clear this draft is place to do that. Chairs to ask IAB to do
> this.


I had discussed this off-line with the chairs, and they were waiting for me to 
do something. I've bene trying to get TEAP out of the way, but I've just posted 
an "eap.arpa" draft now.


It's still very rough, but the idea is "use someth...@eap.arp 
". And then fill in some suggestions.


A new version of Internet-Draft draft-dekok-emu-eap-arpa-00.txt has been
successfully submitted by Alan DeKok and posted to the
IETF repository.


Name: draft-dekok-emu-eap-arpa
Revision: 00
Title: The eap.arpa domain and EAP provisioning
Date: 2023-08-30
Group: Individual Submission
Pages: 13
URL: https://www.ietf.org/archive/id/draft-dekok-emu-eap-arpa-00.txt 

Status: https://datatracker.ietf.org/doc/draft-dekok-emu-eap-arpa/ 

HTML: https://www.ietf.org/archive/id/draft-dekok-emu-eap-arpa-00.html 

HTMLized: https://datatracker.ietf.org/doc/html/draft-dekok-emu-eap-arpa 





Abstract:


This document defines the eap.arpa domain as a way for EAP peers to
signal to EAP servers that they wish to obtain limited, and
unauthenticated, network access. EAP peers leverage user identifier
portion of the Network Access Identifier (NAI) format of RFC7542 in
order to describe what kind of provisioning they need. A table of
identifiers and meanings is defined.






The IETF Secretariat


___
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] eap.arpa domain in draft-ietf-emu-bootstrapped-tls

[Peter Yee]

That one’s on me, gents. I have the action to inquire and will do so ASAP.

 

    -Peter

 

On 8/30/23, 3:29 AM, "Owen Friel (ofriel)"  wrote:

 

Hi EMU Chairs,

 

I was looking to see if any minor updates are needed to 
draft-ietf-emu-bootstrapped-tls-03 before IETF 118 and WGLC.

 

There was one outstanding action from IETF 117:

 

Do we want to say there is an eap.arpa domain? Yes, but

not clear this draft is place to do that. Chairs to ask IAB to do

this.

 

Is there any clarity on this yet?

Thanks,

Owen+Dan

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

[Emu] EMU agenda for IETF 117 posted

[Peter Yee]

The agenda for the EMU session at IETF 117 has been posted as
https://datatracker.ietf.org/meeting/117/materials/agenda-117-emu-00. Let us
know if you have any questions about it or you would like to be added to the
agenda - we still have time available, even for non-WG documents.

 

Cheers,

Joe and Peter

 

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

[Emu] Call for EMU agenda items for IETF 117

[Peter Yee]

IETF 117 in San Francisco is approaching and this is the call for agenda
items. The EMU session is set for Friday afternoon (yeah, I know). Please
submit your requests for time on the agenda to the chairs.

Presumably, we will have 7170bis wrapped up before the meeting, otherwise
there might need to be an agenda item for "REALLY final discussion of TEAP
and 7170bis". ;-)

Thanks,
Joe and Peter



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

[Emu] IETF 116 EMU agenda presentations

[Peter Yee]

The current agenda for the IETF 116 EMU meeting can be found at:

https://datatracker.ietf.org/meeting/116/materials/agenda-116-emu-02

For those of you who have requested presentation time, please upload
your slides soon. We've received 1 of 5 presentations so far and we're
exactly one week out from the meeting.

Thank you and see you in Yokohama!

Joe and Peter

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

[Emu] Call for EMU agenda items for IETF 116

[Peter Yee]

We are now about one month out from IETF 116. Please inform the chairs if you 
have items for discussion before the EMU WG at the upcoming meeting in Yokohama.

Cheers,

Joe and Peter


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

[Emu] Publication has been requested for draft-ietf-emu-aka-pfs-10

[Peter Yee via Datatracker]

Peter Yee has requested publication of draft-ietf-emu-aka-pfs-10 as 
Informational on behalf of the EMU working group.

Please verify the document's state at 
https://datatracker.ietf.org/doc/draft-ietf-emu-aka-pfs/


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

Re: [Emu] I-D Action: draft-ietf-emu-aka-pfs-09.txt

[Peter Yee]

Thanks for updating the document, John. I’ll be generating the shepherd
write-up shortly to get the process moving.

 

-Peter

 

From: Emu  On Behalf Of John Mattsson
Sent: Saturday, January 21, 2023 7:19 AM
To: emu@ietf.org
Subject: Re: [Emu] I-D Action: draft-ietf-emu-aka-pfs-09.txt

 

Hi,

 

We submitted -09 addressing the comments during the second WGLC. We also
made some smaller editorial changes:

- Scalable Vector Graphics (SVG) versions for all figures have been added so
the draft looks nice in HTML. The figures have been slightly modified to
render nicely with aasvg (as suggested by Michael Richardson). 

- Corrections and clarifications were made in the IANA considerations.  The
table in the IANA section has been made into a proper xml table so that it
also looks nice in HTML. 

- A reference has been added to the Section in SEC1 describing how to do
decompression. There was already a reference to SEC1 for how to do
compression.

- The strengthened identity protection requirement is now mentioned in the
introduction.

- Reference updates.

- Various editorial improvements.

As discussed on the list, no changes were needed due to the Wi-Fi privacy
specification mentioned by Heikki Vatiainen.

Please move forward in the publication process as decided
https://mailarchive.ietf.org/arch/msg/emu/-asKK3jV5sNrpJXQMqcjsLMGAGE/

Cheers,
John

 

From: Emu mailto:emu-boun...@ietf.org> > on behalf of
internet-dra...@ietf.org 
mailto:internet-dra...@ietf.org> >
Date: Saturday, 21 January 2023 at 16:04
To: i-d-annou...@ietf.org 
mailto:i-d-annou...@ietf.org> >
Cc: emu@ietf.org   mailto:emu@ietf.org>
>
Subject: [Emu] I-D Action: draft-ietf-emu-aka-pfs-09.txt


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   : Forward Secrecy for the Extensible Authentication
Protocol Method for Authentication and Key Agreement (EAP-AKA' FS)
Authors : Jari Arkko
  Karl Norrman
  Vesa Torvinen
  John Preuß Mattsson
  Filename: draft-ietf-emu-aka-pfs-09.txt
  Pages   : 32
  Date: 2023-01-21

Abstract:
   Many different attacks have been reported as part of revelations
   associated with pervasive surveillance.  Some of the reported attacks
   involved compromising the smart card supply chain, such as attacking
   SIM card manufacturers and operators in an effort to compromise
   shared secrets stored on these cards.  Since the publication of those
   reports, manufacturing and provisioning processes have gained much
   scrutiny and have improved.  However, the danger of resourceful
   attackers for these systems is still a concern.  Always assuming
   breach such as key compromise and minimizing the impact of breach are
   essential zero-trust principles.

   This specification updates RFC 9048, the EAP-AKA' authentication
   method, with an optional extension.  Similarly, this specification
   also updates the earlier version of the EAP-AKA' specification in RFC
   5448.  The extension, when negotiated, provides Forward Secrecy for
   the session key generated as a part of the authentication run in EAP-
   AKA'.  This prevents an attacker who has gained access to the long-
   term pre-shared secret in a SIM card from being able to decrypt any
   past communications.  In addition, if the attacker stays merely a
   passive eavesdropper, the extension prevents attacks against future
   sessions.  This forces attackers to use active attacks instead.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-emu-aka-pfs/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-emu-aka-pfs-09

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-emu-aka-pfs-09


Internet-Drafts are also available by rsync at
rsync.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

Re: [Emu] Second WG Last Call for EAP-AKA' PFS

[Peter Yee]

Based on the previous WGLC and feedback received on this WGLC, I believe
there's consensus in the WG to forward this document on to the IESG. Thank
you everyone who supplied input and to the authors for getting the document
this far.

Peter and Joe

-- Original message:

This is a second working group last call for EAP-AKA' PFS
(draft-ietf-emu-aka-pfs-08)[1]. As you will recall, this document had its
original WGLC in August. Feedback was minimal but positive. As briefed
during IETF 115[2], Jari and his colleagues have updated the document in
several key areas[3]. We agreed during the meeting that a WGLC was
reasonable and there have been no updates since then. So, please review the
document and respond to the list indicating if the document is or is not
ready for publication. This call will end on December 29, 2022, when you
probably couldn't care less because of the holidays. Nonetheless, your
feedback would be greatly appreciated. Even a "looks good" would be helpful.

As before, please note that the document is targeted at the Informational
track and has IPR declarations[4]. 

Thanks,

Peter and Joe

[1] https://datatracker.ietf.org/doc/draft-ietf-emu-aka-pfs/
[2]
https://datatracker.ietf.org/meeting/115/materials/slides-115-emu-eap-aka-fs
-updates-00
[3] https://author-tools.ietf.org/iddiff?url2=draft-ietf-emu-aka-pfs-08
[4]
https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-emu-aka-
pfs


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

Re: [Emu] Adoption call for RFC 7170bis

[Peter Yee]

Based on the supportive and engaged feedback on the mailing list, the chairs
are declaring rfc7170bis adopted by the WG. It looks like we're already
getting into a discussion of the content of the draft, which is fine.

Alan, please submit a WG version of the document for approval. From there,
the WG can build on the discussion already underway as well as the other
topics we have before such as errata and extensions.

Thank you everyone.

Peter and Joe


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

[Emu] Second WG Last Call for EAP-AKA' PFS

[Peter Yee]

This is a second working group last call for EAP-AKA' PFS
(draft-ietf-emu-aka-pfs-08)[1]. As you will recall, this document had its
original WGLC in August. Feedback was minimal but positive. As briefed
during IETF 115[2], Jari and his colleagues have updated the document in
several key areas[3]. We agreed during the meeting that a WGLC was
reasonable and there have been no updates since then. So, please review the
document and respond to the list indicating if the document is or is not
ready for publication. This call will end on December 29, 2022, when you
probably couldn't care less because of the holidays. Nonetheless, your
feedback would be greatly appreciated. Even a "looks good" would be helpful.

As before, please note that the document is targeted at the Informational
track and has IPR declarations[4]. 

Thanks,

Peter and Joe

[1] https://datatracker.ietf.org/doc/draft-ietf-emu-aka-pfs/
[2]
https://datatracker.ietf.org/meeting/115/materials/slides-115-emu-eap-aka-fs
-updates-00
[3] https://author-tools.ietf.org/iddiff?url2=draft-ietf-emu-aka-pfs-08
[4]
https://datatracker.ietf.org/ipr/search/?submit=draft=draft-ietf-emu-aka-
pfs


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

[Emu] Adoption call for RFC 7170bis

[Peter Yee]

This is an adoption call for RFC 7170bis (draft-dekok-emu-rfc7170bis-00)[1].
I'd call this mostly a formality since it's pretty clear the WG is
interested in updating TEAP and TEAP was already adopted by the WG (back in
May 2011). With Alan having generated a new working version to host the
update and even preparing a Git repository[2] to that end, I believe we're
in a good place to revise RFC 7170. That said, if anyone has an objection to
starting off from Alan's kind offering, please let us know by December 22,
2022. 

Joe and Peter

1) https://datatracker.ietf.org/doc/draft-dekok-emu-rfc7170bis/
2) https://github.com/alandekok/rfc7170-bis.git



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

Re: [Emu] [EXTERNAL] Re: More TEAP issues

[Peter Yee]

Joe and I have been discussing an interim that would probably be held in
January. December seems less likely given holiday schedules and vacations.
We'll probably have a Doodle poll out sometime soon to gauge the date and
time that works for the most participants.

 

-Peter

 

From: Emu  On Behalf Of Alexander Clouter
Sent: Friday, December 02, 2022 1:04 AM
To: EMU WG 
Subject: Re: [Emu] [EXTERNAL] Re: More TEAP issues

 

On Thu, 1 Dec 2022, at 05:41, Eliot Lear wrote:

No, but I would ask that we still have an interim to close the errata.

 

It was that Errata (stalled effort on GitHub) that helped me over the line
in implementing TEAP, so this definitely gets my nod of approval.

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

[Emu] Minutes from IETF 115 are available

[Peter Yee]

The minutes from the IETF 115 EMU session have been published at
https://datatracker.ietf.org/meeting/115/materials/minutes-115-emu-202211071
530-00.

 

Thanks so much to Janfred Rieckers for the in-meeting notetaking. It's
greatly appreciated and crucial to a successful meeting.

 

Cheers,

Peter and Joe

 

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

[Emu] Call for EMU agenda Items for IETF 115

[Peter Yee]

Seeing as how we are less than a month away from IETF 115, please inform the
chairs if you have items for discussion at the upcoming meeting in London.

Cheers,

Joe and Peter


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

Re: [Emu] Adoption call for EAP-DPP

[Peter Yee]

Based on the additional feedback on the mailing list, the chairs believe
that there is sufficient support for the WG to adopt EAP-DPP. Given its
alignment with the charter and the level of interest, we're declaring the
document adopted. 

The authors are requested to submit EAP-DPP in its initial WG version.
Please incorporate the feedback garnered during the call for adoption.

Thanks,

Peter and Joe

-Original Message-
From: Emu  On Behalf Of Peter Yee
Sent: Wednesday, September 07, 2022 9:58 PM
To: emu@ietf.org
Subject: Re: [Emu] Adoption call for EAP-DPP

In retrospect, sending the call for adoption at the height of August
vacation season may not have guaranteed the most responses. To be honest,
the level of responses to this call has been a little light, so Joe and I
have decided to extend the call for adoption for one week from today. 

We would really like to hear from anyone else who is interested in reviewing
and/or contributing to this specification or anyone who feels that it should
not be adopted. Please speak up by the 14th either way. This specification
would seemingly fit within the WG's existing charter, so let your voice be
heard!

Thanks,

Peter and Joe

-Original Message-
From: Peter Yee 
Sent: Tuesday, August 16, 2022 1:12 PM
To: 'emu@ietf.org' 
Subject: Adoption call for EAP-DPP

This is an adoption call for EAP-DPP (draft-friel-tls-eap-dpp-05)[1]. This
document aligns with the charter item to "Define mechanisms by which EAP
methods can support creation of long-term credentials for the peer based on
initial limited-use credentials." The latest revision incorporates feedback
from both the TLS and EMU working groups. Please review and respond to the
list if you think this document is or is not an appropriate working group
item for EMU by September 1, 2022.

Thanks,

Peter and Joe

[1] https://datatracker.ietf.org/doc/draft-friel-tls-eap-dpp/


___
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] Adoption call for EAP-DPP

[Peter Yee]

In retrospect, sending the call for adoption at the height of August
vacation season may not have guaranteed the most responses. To be honest,
the level of responses to this call has been a little light, so Joe and I
have decided to extend the call for adoption for one week from today. 

We would really like to hear from anyone else who is interested in reviewing
and/or contributing to this specification or anyone who feels that it should
not be adopted. Please speak up by the 14th either way. This specification
would seemingly fit within the WG's existing charter, so let your voice be
heard!

Thanks,

Peter and Joe

-Original Message-
From: Peter Yee  
Sent: Tuesday, August 16, 2022 1:12 PM
To: 'emu@ietf.org' 
Subject: Adoption call for EAP-DPP

This is an adoption call for EAP-DPP (draft-friel-tls-eap-dpp-05)[1]. This
document aligns with the charter item to "Define mechanisms by which EAP
methods can support creation of long-term credentials for the peer based on
initial limited-use credentials." The latest revision incorporates feedback
from both the TLS and EMU working groups. Please review and respond to the
list if you think this document is or is not an appropriate working group
item for EMU by September 1, 2022.

Thanks,

Peter and Joe

[1] https://datatracker.ietf.org/doc/draft-friel-tls-eap-dpp/


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

[Emu] Adoption call for EAP-DPP

[Peter Yee]

This is an adoption call for EAP-DPP (draft-friel-tls-eap-dpp-05)[1]. This
document aligns with the charter item to "Define mechanisms by which EAP
methods can support creation of long-term credentials for the peer based on
initial limited-use credentials." The latest revision incorporates feedback
from both the TLS and EMU working groups. Please review and respond to the
list if you think this document is or is not an appropriate working group
item for EMU by September 1, 2022.

Thanks,

Peter and Joe

[1] https://datatracker.ietf.org/doc/draft-friel-tls-eap-dpp/


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

[Emu] Genart last call review of draft-ietf-emu-eap-session-id-04

[Peter Yee via Datatracker]

Reviewer: Peter Yee
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-emu-eap-session-id-04
Reviewer: Peter Yee
Review Date: 2020-06-03
IETF LC End Date: 2020-05-27
IESG Telechat date: 2020-06-11

Summary: This draft adds the definition of EAP Session-ID for EAP-SIM and
EAP-AKA when using fast re-authentication. Those changes look fine, but one
other change should be better highlighted. [Ready with Issues]

Major issues: None

Minor issues:

Page 4, Section 1, 3rd paragraph. Aside from correcting the deficiencies in the
fast re-authentication cases, you also have updated the EAP-SIM full
authentication Session-ID derivation as well. This really ought to be mentioned
here in the introduction because that change goes beyond the purported scope of
the document (dealing with fast re-authentication). I believe the change you
have made (substituting the RAND values from the first two authentication
triplets for the RAND in AT_RAND) is fine, although I dislike RAND1 and RAND2
which are not specified in RFC 4186 (or in this draft) except by usage in an
example in the test vectors annex. While that's not really your problem, it
would be good if it were there were prescriptive text that explain what RAND1
and RAND2 mean.

Nits/editorial comments:

Page 4, 2nd paragraph, 1st sentence: change "is defining" to "has defined".
IEEE 802.11ai completed the FILS specification several years ago.

Page 7, Section 3, 1st paragraph, 1st sentence: change "define" to "provide a",
just so we aren't defining a definition.


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