On Tue, Apr 2, 2024 at 10:36 PM Watson Ladd wrote:
>
> On Tue, Apr 2, 2024, 5:08 PM Eric Rescorla wrote:
>
>> Adoption should not be required to register a code point [0], as the
>> policy is Specification Required.
>>
>> I'm mildly negative on adopting this document. What is the reason we need
* Well, don't we want to say how this is supposed to work somewhere? I
doubt this will take much time.
The authors may want to, but could this be an independent submission, rather
than WG item? It seems that the real goal here is to enable a specific scenario
between a cloud provider and a
Internet-Draft draft-ietf-tls-tls12-frozen-00.txt is now available. It is a
work item of the Transport Layer Security (TLS) WG of the IETF.
Title: TLS 1.2 is in Feature Freeze
Authors: Rich Salz
Nimrod Aviram
Name:draft-ietf-tls-tls12-frozen-00.txt
Pages: 7
> The attitude I am trying to get away from is that the TLS WG has to
be involved in every extension to TLS. Rather, we should decide what things
are important and spend time on them and then let others extend TLS
independently
in areas we don't think are important.
This is probably a worthwhile
Hey,
I'm writing this in my capacity as owner for NSS[1], not as a draft author.
The chairs asked that I formally indicate that Mozilla and the NSS project
are willing to transfer ownership of the SSLKEYLOGFILE format[2]. Though
it might be obvious to some of us that submitting an
It would be great to here from Jonathan (the author) if RFC 7250 is already
sufficient for this use case.
On Tue, Apr 2, 2024 at 10:23 PM Mohit Sethi wrote:
> Please see my earlier comment regarding this draft:
> https://mailarchive.ietf.org/arch/msg/tls/g3tImSVXO8AEmPH1UlwRB1c1TLs/
>
> In
Noted in the Shepherd write-up.
spt
> On Apr 2, 2024, at 20:30, Stephen Farrell wrote:
>
>
> Hiya,
>
> This is basically for the record and not an objection to proceeding.
>
> On 02/04/2024 17:34, Sean Turner wrote:
>> This WGLC has concluded. There is consensus to move this document
Martin,
Thanks for this. This was noted in the Shepherd write-up for the IESG to find
during their deliberations.
Cheers,
spt
> On Apr 3, 2024, at 23:14, Martin Thomson wrote:
>
> Hey,
>
> I'm writing this in my capacity as owner for NSS[1], not as a draft author.
>
> The chairs asked that
Sean Turner has requested publication of draft-ietf-tls-keylogfile-01 as
Informational on behalf of the TLS working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-tls-keylogfile/
___
TLS mailing list
