IETF Logo Mail Archive

Re: [core] Question reg. draft-fossati-tls-iot-optimizations-00

Simon Bernard <contact@simonbernard.eu> Thu, 03 November 2016 10:30 UTC

Return-Path: <contact@simonbernard.eu>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D08C129550 for <core@ietfa.amsl.com>; Thu, 3 Nov 2016 03:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z0MJLtc4qa4M for <core@ietfa.amsl.com>; Thu, 3 Nov 2016 03:30:03 -0700 (PDT)
Received: from 10.mo3.mail-out.ovh.net (10.mo3.mail-out.ovh.net [87.98.165.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 475B1129849 for <core@ietf.org>; Thu, 3 Nov 2016 03:30:02 -0700 (PDT)
Received: from player772.ha.ovh.net (b7.ovh.net [213.186.33.57]) by mo3.mail-out.ovh.net (Postfix) with ESMTP id 5EA2258F49 for <core@ietf.org>; Thu, 3 Nov 2016 11:30:00 +0100 (CET)
Received: from [10.41.51.97] (130.163-14-84.ripe.coltfrance.com [84.14.163.130]) (Authenticated sender: contact@simonbernard.eu) by player772.ha.ovh.net (Postfix) with ESMTPSA id 362E34C0096; Thu, 3 Nov 2016 11:29:59 +0100 (CET)
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, core@ietf.org
References: <D43F60A9.74AFB%thomas.fossati@alcatel-lucent.com> <BC36447FF5C62E46BEF3F124D3C1E8925E1F5F6B@imbpw2exd01.bosch-si.com> <607f8720-8e86-90f6-83fd-299939c298ae@simonbernard.eu> <fcd2be95-5acf-00b4-64a1-d5cec67f27a2@gmx.net>
From: Simon Bernard <contact@simonbernard.eu>
Message-ID: <8eb7103a-5ca2-f1d0-683a-d85a4985c7eb@simonbernard.eu>
Date: Thu, 03 Nov 2016 11:29:58 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0
MIME-Version: 1.0
In-Reply-To: <fcd2be95-5acf-00b4-64a1-d5cec67f27a2@gmx.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Ovh-Tracer-Id: 1272266896140744871
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: -100
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeelvddrkeeigddugecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Z194DYp5DxKPk8QFdUsnkh_i_NA>
Subject: Re: [core] Question reg. draft-fossati-tls-iot-optimizations-00
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2016 10:30:05 -0000

If this is really about linking independent TLS sessions. I think there 
is no problem here.

Because "Sessions define a set of cryptographic security parameters that 
can be shared among multiple connections." (RFC 5246)

So a connection is alway linked to only 1 sessions, So a CID is alway 
linked to 1 sessions.

This means CID can not be used to linked independent TLS sessions.

Le 02/11/2016 à 19:25, Hannes Tschofenig a écrit :
> Hi Simon,
>
> On 11/02/2016 05:08 PM, Simon Bernard wrote:
>> I would like to understand which privacy concern we would like to
>> achieve exactly ?
> The privacy concern is correlation by linking independent TLS sessions
> together (see RFC 6973).
>
>
> Ciao
> Hannes
>
>

v2.23.0 | Report a Bug | By Email