On Tue, Mar 12, 2024 at 10:20 PM Raghu Saxena wrote:
>
> Are comments restricted strictly to members of the working group? If so,
> please ignore this E-Mail.
>
> I'd previously tried to raise an issue regarding requirements of a
> public_name in the ECHConfig in the mailing list [0], and when I d
I have risen similar discussion before and have tried to suggest some
solutions, but none of them got any support.
Here is the previous discuss thread, just FYI
https://mailarchive.ietf.org/arch/msg/tls/HlwYX16Y4W2BevKTpI6a81eO1JE/
> On Mar 13, 2024, at 13:20, Raghu Saxena wrote:
>
> Are comm
Are comments restricted strictly to members of the working group? If so,
please ignore this E-Mail.
I'd previously tried to raise an issue regarding requirements of a
public_name in the ECHConfig in the mailing list [0], and when I didn't
get much response there, even on Github [1], where I wa
LGTM
On Tue, Mar 12, 2024 at 7:58 AM Sean Turner wrote:
>
> This is the working group last call for the SSLKEYLOGFILE Format for TLS
> Internet-Draft [1]. Please indicate if you think the I-D is ready to progress
> to the IESG and send any comments to the list by 31 March 2024.
>
> The GH repo
On Tue, Mar 12, 2024 at 4:04 PM Stephen Farrell
wrote:
>
> I'll argue just a little more then shut up...
>
> On 12/03/2024 22:55, Martin Thomson wrote:
> >
> >> Sorry also for a late suggestion, but how'd we feel about adding
> >> some text like this to 1.1?
> >>
> >> "An implementation, esp. a s
I'll argue just a little more then shut up...
On 12/03/2024 22:55, Martin Thomson wrote:
Sorry also for a late suggestion, but how'd we feel about adding
some text like this to 1.1?
"An implementation, esp. a server, emitting a log file such as this
in a production environment where the TLS
On Wed, Mar 13, 2024 at 09:55:10AM +1100, Martin Thomson wrote:
>
>
> On Wed, Mar 13, 2024, at 08:39, Stephen Farrell wrote:
>
> > Another thought occurred to me that I don't recall being mentioned
> > before: given we're defining a mime type, that suggests sending
> > these files by mail or in
On Wed, Mar 13, 2024, at 08:39, Stephen Farrell wrote:
> (Apologies to Martin for the grudging acceptance of
> his worthy effort;-)
No apology needed. Nose-holding is expected :)
> Sorry also for a late suggestion, but how'd we feel about adding
> some text like this to 1.1?
>
> "An imple
On Tue, Mar 12, 2024 at 3:45 PM Stephen Farrell
wrote:
>
>
> On 12/03/2024 22:06, Eric Rescorla wrote:
> > I don't think we should make statements about regulatory requirements
> > in this kind of specification. That's not our lane.
>
> I'd weakly disagree about making statements such as suggeste
🚢 Ship it.
On Tue, Mar 12, 2024, at 09:00, Joseph Salowey wrote:
> This is the working group last call for TLS Encrypted Client Hello [1].
> Please indicate if you think the draft is ready to progress to the
> IESG and send any comments to the list by 31 March 2024. The comments
> sent by Wat
On 12/03/2024 22:06, Eric Rescorla wrote:
I don't think we should make statements about regulatory requirements
in this kind of specification. That's not our lane.
I'd weakly disagree about making statements such as suggested,
while agreeing with "not out lane." I don't think the text I
sugge
On Tue, Mar 12, 2024 at 2:40 PM Stephen Farrell
wrote:
>
> Hiya,
>
> On 12/03/2024 14:57, Sean Turner wrote:
> > This is the working group last call for the SSLKEYLOGFILE Format for
> > TLS Internet-Draft [1]. Please indicate if you think the I-D is ready
> > to progress to the IESG and send any
Hiya,
On 12/03/2024 14:57, Sean Turner wrote:
This is the working group last call for the SSLKEYLOGFILE Format for
TLS Internet-Draft [1]. Please indicate if you think the I-D is ready
to progress to the IESG and send any comments to the list by 31 March
2024.
This is not my fav thing, but I
Ship it.
From: TLS on behalf of Salz, Rich
Date: Tuesday, 12 March 2024 at 16:00
To: Sean Turner , TLS List
Subject: Re: [TLS] Working Group Last Call for SSLKEYLOG File
> This is the working group last call for the SSLKEYLOGFILE Format for TLS
> Internet-Draft [1]. Please indicate if you thi
> This is the working group last call for the SSLKEYLOGFILE Format for TLS
> Internet-Draft [1]. Please indicate if you think the I-D is ready to progress
> to the IESG and send any comments to the list by 31 March 2024.
No notes.
Ship it.
___
TLS ma
This is the working group last call for the SSLKEYLOGFILE Format for TLS
Internet-Draft [1]. Please indicate if you think the I-D is ready to progress
to the IESG and send any comments to the list by 31 March 2024.
The GH repo for the I-D can be found at [2].
Thanks,
Joe, Deirdre, and Sean
[1
Hi! I submitted two PRs on this I-D:
1. One updates the discussions about the Recommended column values to refer to
draft-ietf-tls-rfc8447bis that John raised:
https://github.com/tlswg/tls-flags/pull/33
2. One updatesRFC 8446 references to draft-ietf-tls-rfc8446bis:
https://github.com/tlswg/tls-
I also support seeing the document moving forward.
On Tue, Mar 12, 2024, 16:37 Salz, Rich
wrote:
> I support advancing this document.
>
> ___
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>
__
+1
will do my best to help within the timeline
From: TLS on behalf of Salz, Rich
Date: Tuesday, 12 March 2024 at 13:37
To: Stephen Farrell , Rob Sayre
Cc: tls@ietf.org
Subject: Re: [TLS] Working Group Last Call for ECH
I support advancing this document.
_
I support advancing this document.
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
20 matches
Mail list logo
