I’m also interested in helping here for potential applicability for IoT device
onboarding.
From: TLS On Behalf Of Eric Rescorla
Sent: 21 January 2020 14:52
To: Jonathan Hoyland
Cc: Björn Haase ; TLS List ; Mohit
Sethi M
Subject: Re: [TLS] External PSK design team
I am willing to contribute
Von: Eric Rescorla
Gesendet: Dienstag, 21. Januar 2020 15:52
An: Jonathan Hoyland
Cc: Mohit Sethi M ; Björn Haase
; TLS List
Betreff: Re: [TLS] External PSK design team
I am willing to contribute.
-Ekr
On Tue, Jan 21, 2020 at 2:50 AM Jonathan Hoyland
wrote:
Hi All,
This is something I'm v
t?
>
> Yours,
>
> Björn
>
> Von: Eric Rescorla
> Gesendet: Dienstag, 21. Januar 2020 15:52
> An: Jonathan Hoyland
> Cc: Mohit Sethi M ; Björn Haase
> ; TLS List
> Betreff: Re: [TLS] External PSK design team
>
> I am willing to contribute.
>
> -
ntract offer, a contract
> amendment, or an acceptance of a contract offer unless explicitly and
> conspicuously designated or stated as such.
>
>
>
> -Ursprüngliche Nachricht-
> Von: TLS mailto:tls-boun...@ietf.org>> Im Auftrag von
> Mohit Sethi M
> Gese
Sean:
I can help with this design team.
Russ
> On Jan 20, 2020, at 11:01 PM, Sean Turner wrote:
>
> At IETF 106, we discussed forming a design team to focus on external PSK
> management and usage for TLS. The goal of this team would be to produce a
> document that discusses considerations f
rial. Any review, retransmission, dissemination or other use
>> of, or taking of any action in reliance upon, this information by persons
>> or entities other than the intended recipient is prohibited. If you receive
>> this in error, please contact the sender and delete the mat
Just to clarify myself further, I would not want us to change the TLS
1.3 protocol. I would rather have this design team produce an
informational document that discusses considerations when using external
PSKs in different settings, as well as, privacy of PSK identities and
possible mitigations
Thanks for clarifying. I would still like that this design team to have
a narrow scope. As Sean said in his initial email:
> forming a design team to focus on external PSK management and usage for TLS
--Mohit
On 1/21/20 12:40 PM, Björn Haase wrote:
>> Mohit Sethi M wrote:
>> I would let CFRG d
sons
> or entities other than the intended recipient is prohibited. If you receive
> this in error, please contact the sender and delete the material from any
> computer. This e-mail does not constitute a contract offer, a contract
> amendment, or an acceptance of a contract offer unless
> Mohit Sethi M wrote:
> I would let CFRG deal with the PAKE selection process:
> and not have this design team spend time and energy on designing PAKEs.
That was not what I was suggesting. Instead, I was suggesting to *incorporate*
the results of the selection process into TLS, such that there
, please contact the sender and delete the material from any
> computer. This e-mail does not constitute a contract offer, a contract
> amendment, or an acceptance of a contract offer unless explicitly and
> conspicuously designated or stated as such.
>
>
>
> -----Ursprüng
ed or stated as such.
-Ursprüngliche Nachricht-
Von: TLS Im Auftrag von Mohit Sethi M
Gesendet: Dienstag, 21. Januar 2020 10:45
An: Colm MacCárthaigh ; Sean Turner
Cc: TLS List
Betreff: Re: [TLS] External PSK design team
I am certainly interested and willing to contribute. We need
I am certainly interested and willing to contribute. We need some
consensus on whether PSKs can be shared with more than 2 parties,
whether the parties can switch roles, etc.
EMU is going to work on EAP-TLS-PSK and the question of
privacy/identities will pop-up there too.
--Mohit
On 1/21/20 7
Interested, as it happens - this is something I've been working on at Amazon.
On Mon, Jan 20, 2020 at 8:01 PM Sean Turner wrote:
>
> At IETF 106, we discussed forming a design team to focus on external PSK
> management and usage for TLS. The goal of this team would be to produce a
> document th
On Mon, Jan 20, 2020 at 8:01 PM Sean Turner wrote:
> At IETF 106, we discussed forming a design team to focus on external PSK
> management and usage for TLS. The goal of this team would be to produce a
> document that discusses considerations for using external PSKs, privacy
> concerns (and possi
At IETF 106, we discussed forming a design team to focus on external PSK
management and usage for TLS. The goal of this team would be to produce a
document that discusses considerations for using external PSKs, privacy
concerns (and possible mitigations) for stable identities, and more developed
16 matches
Mail list logo
