On 05/03/2018, 00:27, "Eric Rescorla" mailto:e...@rtfm.com>>
wrote:
I genuinely can't see what advantage we get by not having its
presence explicitly signalled. Could you elaborate a bit on that?
Well, you're making every packet 1 byte bigger, for starters.
If the cost of having simple, straigh
Op 01-03-18 om 22:50 schreef Viktor Dukhovni:
>
>
>> On Mar 1, 2018, at 2:13 PM, Shumon Huque wrote:
>>
>>> On Wed, Feb 28, 2018 at 3:07 PM, Nico Williams
>>> wrote:
>>> IF there's an objection to modifying the extension in order to add a
>>> pin-to-DANE TTL field, I would propose the followin
Op 26-02-18 om 15:26 schreef Paul Wouters:
> On Thu, 22 Feb 2018, Shumon Huque wrote:
>
>> On Wed, Feb 21, 2018 at 2:48 PM, Paul Wouters wrote:
>> On Wed, 21 Feb 2018, Shumon Huque wrote:
>>
>> Okay, got it. For people that have already implemented
>> this, I think
>>
Should the TLS 1.3 draft request a new registry for psk_key_exchange_modes?
Initially, I thought that there was no way to extend it, but the email below
from
Martin Thomson suggests adding a new codepoint, so I thought it best to check
that this wasn't an oversight in the draft.
-- Tony
-Or
The double “the” got fixed, but the double and didn’t I submitted a PR so we
don’t forget this.
spt
> On Mar 4, 2018, at 22:52, M K Saravanan wrote:
>
> Hi,
>
> In TLSv1.3, draft 26, there is a small typographical error. It needs
> to be corrected.
>
>
> (1)
>
> Appendix D. Backward Comp
Spoke too soon I got the double the in the following PR:
https://github.com/tlswg/tls13-spec/pull/1164
spt
> On Mar 5, 2018, at 08:30, Sean Turner wrote:
>
> The double “the” got fixed, but the double and didn’t I submitted a PR so we
> don’t forget this.
>
> spt
>
>> On Mar 4, 2018, at 22:5
> On Mar 5, 2018, at 4:32 AM, Willem Toorop wrote:
>
>> Therefore, any long-term caching of a destination's support for the extension
>> should require server opt-in, and must have a maximum duration.
>
> How do you (all) feel about using the expiry date on the RRSIG for the
> TLSA to be used
On Mon, 5 Mar 2018, Viktor Dukhovni wrote:
On Mar 5, 2018, at 4:32 AM, Willem Toorop wrote:
Therefore, any long-term caching of a destination's support for the extension
should require server opt-in, and must have a maximum duration.
How do you (all) feel about using the expiry date on the
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 : Exported Authenticators in TLS
Author : Nick Sullivan
Filename: draft-ietf-tls-expor
Hi folks,
Here's another entry in the DH-only pile.
I've just posted:
draft-rescorla-tls13-semistatic-dh-00
This implements a semi-static DH exchange mostly borrowed from
OPTLS [0]. There are obviously connections with draft-putman, but
this is more oriented towards implementing a 1-RTT style
All,
I have just submitted a draft outlining enterprise use cases for
out-of-band TLS decryption.
Please review.
Thanks
Steve Fenter
-- Forwarded message --
From:
Date: Mon, Mar 5, 2018 at 1:05 PM
Subject: New Version Notification for draft-fenter-tls-decryption-00.txt
To: St
FYI, I've published an updated version of exported authenticators
incorporating into account the changes discussed at IETF 100 and on the
list.
-- Forwarded message -
From:
Date: Mon, Mar 5, 2018 at 12:28 PM
Subject: New Version Notification for
draft-ietf-tls-exported-authenticat
12 matches
Mail list logo
