[{"author": "Mohit Sethi", "text": "Notes: https://notes.ietf.org/notes-ietf-113-emu
", "time": "2022-03-22T12:02:30Z"}, {"author": "Russ Housley", "text": "I do not see any slides in the Meetecho folder
", "time": "2022-03-22T12:05:35Z"}, {"author": "Meetecho", "text": "Russ: checking
", "time": "2022-03-22T12:05:47Z"}, {"author": "Meetecho", "text": "Russ: for the materials, there's a refresh button you can use when the materials list is empty
", "time": "2022-03-22T12:06:28Z"}, {"author": "Russ Housley", "text": "Thanks
", "time": "2022-03-22T12:06:49Z"}, {"author": "Meetecho", "text": "We just refreshed that, the slide deck seem all imported though
", "time": "2022-03-22T12:06:51Z"}, {"author": "Meetecho", "text": "Please let us know if there's something missing
", "time": "2022-03-22T12:06:56Z"}, {"author": "Roman Danyliw", "text": "I see all of the slides after a refresh
", "time": "2022-03-22T12:15:39Z"}, {"author": "John Preu\u00df Mattsson", "text": "Most existing libraries expect the 65 byte SECG encoding. 3GPP SUCI use the 33 byte SECG encoding (point compression). 32 (compact representation) or 33 (point compression) does not really matter in this case (Diffie-Hellaman). 3GPP devices implementing SUCI would work fine with either 32 or 33 byte encoding, so no need to use the 65 byte encoding. The extra byte does not simplify anything, but does not hurt much either.
", "time": "2022-03-22T12:18:21Z"}, {"author": "Jan-Frederik Rieckers", "text": "If anyone could help taking notes, I'd appreciate it.
", "time": "2022-03-22T12:21:26Z"}, {"author": "jhoyla", "text": "With a session resumption what's the client authentication status?
", "time": "2022-03-22T12:21:34Z"}, {"author": "Eliot Lear", "text": "i can help
", "time": "2022-03-22T12:22:09Z"}, {"author": "jhoyla", "text": "(From a TLS perspective)
", "time": "2022-03-22T12:24:03Z"}, {"author": "Alan DeKok", "text": "jhoyla: for the error case of TTLS+PAP and session resumption, the client treats the session ticket as an EAP Failure.
", "time": "2022-03-22T12:33:20Z"}, {"author": "Alan DeKok", "text": "I'll discuss it on the list
", "time": "2022-03-22T12:34:30Z"}, {"author": "Eliot Lear", "text": "Russ it was difficult to understand you
", "time": "2022-03-22T12:38:19Z"}, {"author": "Massimiliano Pala", "text": "Are there any IP concerns on this bootstrapping certificate re-provisioning that you are aware of?
", "time": "2022-03-22T12:38:37Z"}, {"author": "Russ Housley", "text": "Could go forward as Experimental if TLS is not willing to advance RFC 8773.
", "time": "2022-03-22T12:43:31Z"}, {"author": "Christopher Wood", "text": "@Russ, what do you mean by \"advance\" here?
", "time": "2022-03-22T12:45:37Z"}, {"author": "Eliot Lear", "text": "@Chris- it's a downref for a PS to ref exp
", "time": "2022-03-22T12:46:50Z"}, {"author": "cabo", "text": "SO make this one exp too
", "time": "2022-03-22T12:47:14Z"}, {"author": "jhoyla", "text": "@Alan DeKok_web_904 I was actually asking about the authentication status of the resumed session. Does the draft assume that if the client was authenticated in the previous session then it is authenticated in the resumed session?
", "time": "2022-03-22T12:47:16Z"}, {"author": "cabo", "text": "And advance them to PS after that
", "time": "2022-03-22T12:47:23Z"}, {"author": "Christopher Wood", "text": "I understand that, but I'm not sure what you're looking for here. Bumping 8773 to PS?
", "time": "2022-03-22T12:47:26Z"}, {"author": "Eliot Lear", "text": "@Chris, yes that would be good.
", "time": "2022-03-22T12:48:02Z"}, {"author": "Christopher Wood", "text": "Well, I think the better outcome would be to make this draft experimental. It's less work overall and won't change the outcomes.
", "time": "2022-03-22T12:48:24Z"}, {"author": "Eliot Lear", "text": "And it doesn't have to happen fast.
", "time": "2022-03-22T12:48:24Z"}, {"author": "Eliot Lear", "text": "Just at the time that this draft is finished...
", "time": "2022-03-22T12:48:35Z"}, {"author": "Russ Housley", "text": "@chris: Yes, advance from experimental to standards-track
", "time": "2022-03-22T12:49:33Z"}, {"author": "Eliot Lear", "text": "If there's an issue with moving the other from exp it would be good to understand that.
", "time": "2022-03-22T12:50:56Z"}, {"author": "Christopher Wood", "text": "We can discuss it. In general, my view is that we shouldn't do work for the sake of doing work.
", "time": "2022-03-22T12:53:07Z"}, {"author": "jhoyla", "text": "IMO A draft should be sufficiently clear that it can't be read wrong.
", "time": "2022-03-22T12:54:17Z"}, {"author": "Massimiliano Pala", "text": "Besides the provided use case where security is provided via the network authentication and subsequent encryption, in other environments the same security can be achieved by tunneling EAP-CREDS via an authenticated and encrypted mechanism (i.e., EAP-TLS/EAP-TEAP).
", "time": "2022-03-22T13:02:12Z"}, {"author": "Alan DeKok", "text": "CBRSA-TS-1003-V3.0.0 mentions using EAP-CREDS. Has it been implemented / deployed? What's the EAP type number being used?
", "time": "2022-03-22T13:03:23Z"}, {"author": "Jonathan Hammell", "text": "Re EAP-UTE question about referring to hash algorithms in COSE, draft-ietf-cose-hash-algs is in AUTH48 and will establish an IANA hash algorithm registry.
", "time": "2022-03-22T13:03:29Z"}, {"author": "Eliot Lear", "text": "bye!
", "time": "2022-03-22T13:03:56Z"}, {"author": "Eliot Lear", "text": "thanks chairs!
", "time": "2022-03-22T13:03:59Z"}, {"author": "Eliot Lear", "text": "and scribe!
", "time": "2022-03-22T13:04:03Z"}, {"author": "chenmeiling", "text": "thanks
", "time": "2022-03-22T13:04:06Z"}]