Hi,
In DTLS 1.2 over UDP, I would like to know what is the
recommendation about using HELLO_VERIFY_REQUEST during an abbreviated
handshake.
Should we send it all the time ? or could we avoid to send it if
SESSION ID is known ?
Thx,
Simon
On Wed, Oct 03, 2018 at 05:29:33AM -0700, internet-dra...@ietf.org wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Transport Layer Security WG of the IETF.
>
> Title : TLS Certificate Compression
>
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Layer Security WG of the IETF.
Title : TLS Certificate Compression
Authors : Alessandro Ghedini
Victor Vasiliev
Yoav and I (two of the three designated experts) approve the assignment of 26
for TLS-LTS.
Sorry for the delays in getting the workflow worked out, Peter.
On 9/25/18, 2:32 PM, "Peter Gutmann" wrote:
>Now that RFC 8447 is published, I'd like to request the addition of
extension
>ID
On Wed, Oct 03, 2018 at 06:17:09AM +, Peter Gutmann wrote:
> [CC'd back to the TLS list because this affects other TLS work as well]
(I responded privately to Peter about this already.)
> Benjamin Kaduk writes:
>
> >Having looked a bit harder, it seems that perhaps I need to point out
> On Oct 3, 2018, at 08:36, Alessandro Ghedini wrote:
>
> On Wed, Oct 03, 2018 at 05:29:33AM -0700, internet-dra...@ietf.org wrote:
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Transport Layer Security WG of the
> On Oct 3, 2018, at 02:17, Peter Gutmann wrote:
>
> [CC'd back to the TLS list because this affects other TLS work as well]
>
> Benjamin Kaduk writes:
>
>> Having looked a bit harder, it seems that perhaps I need to point out that,
>> if you want IANA to allocate a value, you need to *ask
Hi all,
We've registered the following TLS ExtensionType Value:
Value: 26
Extension Name: tls_lts
TLS 1/3: -
Recommended: N
Reference: [draft-gutmann-tls-lts]
Please see
https://www.iana.org/assignments/tls-extensiontype-values
Our preference is that the contents of the "TLS 1.3" and
Actually, I submitted a request to IANA while this RFC was in process which got
sent to the tls-reg-review alias for approval. There was apparently a hiccup,
where the alias members did not receive the request from IANA, but did receive
my follow-up e-mail asking if anyone had looked at it.
[CC'd back to the TLS list because this affects other TLS work as well]
Benjamin Kaduk writes:
>Having looked a bit harder, it seems that perhaps I need to point out that,
>if you want IANA to allocate a value, you need to *ask IANA for it*. The
>tls-reg-rev...@ietf.org list is not a supported
Sean Turner writes:
>The “panel” is not secret. The experts were identified when
>draft-ietf-tls-tls13 and draft-ietf-tls-iana-registry-updates were
>approved [0][1] and are/were enshrined in the IANA registry [2][3].
Ah, OK. When I checked, the membership of tls-reg-rev...@ietf.org
was
Benjamin Kaduk writes:
>if you think you have followed the proper procedure, why did you not act on
>the escalation procedure I pointed out to you previously, rather than
>continuing to complain on the TLS WG list?
Because I wanted to get it fixed for others who may be going down the same
Salz, Rich writes:
>Sorry for the delays in getting the workflow worked out, Peter.
No problem, someone had to be the beta tester :-).
Peter.
___
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
13 matches
Mail list logo
