On 17/07/2019, 17:42, "Thomas Fossati" wrote:
> My suggestion is we move that section back and point to RRC for the
> "final" solution. This doesn't give complete internal coherency to
> conn-id -- which is indeed suboptimal -- but the recommendation to
> provide peer address update call-backs
On 17/07/2019, 16:33, "TLS on behalf of Martin Thomson" wrote:
> I'm really concerned about shipping a protocol that enables the sorts
> of attacks that connection IDs enable. I think that we should discuss
> that issue when we meet. I know that Hannes' new draft is an attempt
> to tackle this
These changes look fine. Mostly.
I'm really concerned about shipping a protocol that enables the sorts of
attacks that connection IDs enable. I think that we should discuss that issue
when we meet. I know that Hannes' new draft is an attempt to tackle this
issue, but that's a long way from
Engineering Cloud Services 4 Bosch IoT Hub (INST/ECS4)
Von: TLS Im Auftrag von Joseph Salowey
Gesendet: Montag, 15. Juli 2019 19:19
An:
Betreff: [TLS] WGLC for draft-ietf-tls-dtls-connection-id-06
This the working group last call for draft-ietf-tls-dtls-connection-id-06. The
This the working group last call for draft-ietf-tls-dtls-connection-id-06.
The diff between the version that was last called (-03) and the current
version can be found here:
https://tools.ietf.org/rfcdiff?url2=draft-ietf-tls-dtls-connection-id-06.txt=draft-ietf-tls-dtls-connection-id-03
Please
On Mon, Mar 4, 2019 at 4:43 PM Joseph Salowey wrote:
> This is a working group last call for draft-ietf-tls-dtls-connection-id-03.
> The last working group last call resulted in some issues. The authors worked
> with the reviewers to publish a new draft to address these issue. Please
> focus
LGTM.
I would strike ", if these privacy properties are important in a given
deployment" from the acknowledgments section (which is an odd place for the
accompanying statement.
I would add an explicit note about the lack of CID update making this
unsuitable for mobility scenarios. That's a
This is a working group last call
for draft-ietf-tls-dtls-connection-id-03. The last working group last call
resulted in some issues. The authors worked with the reviewers to publish
a new draft to address these issue. Please focus your review on the changes
since the previous last call. You
The WGLC for draft-ietf-tls-dtls-connection-id has completed. There were
some minor issued raised that require a new revision of the draft before
progressing to the ISEG.
Thanks,
Chris, Joe, and Sean
On Thu, Dec 6, 2018 at 6:08 AM Kraus Achim (INST/ECS4) <
achim.kr...@bosch-si.com>
Cc:
Subject: Re: [TLS] WGLC for draft-ietf-tls-dtls-connection-id
On Thu, Dec 6, 2018 at 12:19 AM Kraus Achim (INST/ECS4)
<mailto:achim.kr...@bosch-si.com> wrote:
Hi List,
I put some comments and question on the github page,
https://github.com/tlswg/dtls-conn-id/issues/15
Thi
gt;
> *From:* TLS *On Behalf Of * Salz, Rich
> *Sent:* Mittwoch, 5. Dezember 2018 19:15
> *To:* Joseph Salowey ;
> *Subject:* Re: [TLS] WGLC for draft-ietf-tls-dtls-connection-id
>
>
>
> Still stuck in that five-day-behind timezone, but I read this doc and have
> no problem
8411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr.
Stefan Ferber, Michael Hahn, Dr. Aleksandar Mitrovic
From: TLS On Behalf Of Salz, Rich
Sent: Mittwoch, 5. Dezember 2018 19:15
To: Joseph Salowey ;
Subject: Re: [TLS] WGLC for draft-ietf-tls-dtls-connection-id
Still stuck in tha
Still stuck in that five-day-behind timezone, but I read this doc and have no
problems. Advance it.
From: Joseph Salowey
Date: Wednesday, November 7, 2018 at 2:40 AM
To: "tls@ietf.org"
Subject: [TLS] WGLC for draft-ietf-tls-dtls-connection-id
This is the working group
On Wed, 2018-11-07 at 14:39 +0700, Joseph Salowey wrote:
> This is the working group last call for the "Connection Identifiers
> for DTLS 1.2" draft available at
> https://datatracker.ietf.org/doc/draft-ietf-tls-dtls-connection-id/.
> Please review the document and send your comments to the list
Comments and PRs in GitHub:
https://github.com/tlswg/dtls-conn-id/issues?utf8=%E2%9C%93=is%3Aopen+author%3Amartinthomson+
One thing I didn't add as an issue, but is worth considering: This
makes zero mention of DTLS 1.3 and the vastly superior design that is
available there. I think that it
This is the working group last call for the "Connection Identifiers for
DTLS 1.2" draft available at
https://datatracker.ietf.org/doc/draft-ietf-tls-dtls-connection-id/. Please
review the document and send your comments to the list by 2359 UTC on 30
November 2018.
Thanks,
Chris, Joe, and Sean
16 matches
Mail list logo
