Return-Path: X-Original-To: tls@ietfa.amsl.com Delivered-To: tls@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A7E21A1A5D for ; Mon, 17 Aug 2015 07:21:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 P_18lqxGpRI5 for ; Mon, 17 Aug 2015 07:20:58 -0700 (PDT) Received: from 4.mo69.mail-out.ovh.net (4.mo69.mail-out.ovh.net [46.105.42.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC28D1A1A3D for ; Mon, 17 Aug 2015 07:20:57 -0700 (PDT) Received: from mail190.ha.ovh.net (b9.ovh.net [213.186.33.59]) by mo69.mail-out.ovh.net (Postfix) with SMTP id 0C4E61000959 for ; Mon, 17 Aug 2015 16:20:55 +0200 (CEST) Received: from localhost (HELO queueout) (127.0.0.1) by localhost with SMTP; 17 Aug 2015 16:20:55 +0200 Received: from 130.163-14-84.ripe.coltfrance.com (HELO ?10.41.51.97?) (contact@simonbernard.eu@84.14.163.130) by ns0.ovh.net with SMTP; 17 Aug 2015 16:20:53 +0200 Message-ID: <55D1EDC5.1010106@simonbernard.eu> Date: Mon, 17 Aug 2015 16:20:53 +0200 From: Simon Bernard User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: Eric Rescorla , tls@ietf.org References: <55BB88FD.4060901@simonbernard.eu> <55BBA7DA.8000806@simonbernard.eu> In-Reply-To: Content-Type: multipart/alternative; boundary="------------050104010105010402070700" X-Ovh-Tracer-Id: 17133100358165346546 X-Ovh-Remote: 84.14.163.130 (130.163-14-84.ripe.coltfrance.com) X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) X-OVH-SPAMSTATE: OK X-OVH-SPAMSCORE: 0 X-OVH-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeekfedrgedvucetufdoteggucfrrhhofhhilhgvmecuqfggjfenuceurghilhhouhhtmecufedttdenuc X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeekfedrgedvucetufdoteggucfrrhhofhhilhgvmecuqfggjfenuceurghilhhouhhtmecufedttdenuc Archived-At: Subject: Re: [TLS] DTLS epoch and resume session/handshake X-BeenThere: tls@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Aug 2015 14:21:00 -0000 This is a multi-part message in MIME format. --------------050104010105010402070700 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit I'm sorry to insist, but What did you mean by transport level connection ? For me UDP was a connectionless protocol. Simon Le 31/07/2015 18:53, Eric Rescorla a écrit : > > > On Fri, Jul 31, 2015 at 6:52 PM, Simon Bernard > > wrote: > > Thx. > What did you mean by connection ? > > > transport level connection. > > A resume handshake is a new connection ? > > > You can also resume when you renegotiate. > > -Ekr > > > Le 31/07/2015 16:54, Eric Rescorla a écrit : > > The epoch is set to 0 at the start of each connection and then > incremented > with each handshake on that connection. > > -Ekr > > On Fri, Jul 31, 2015 at 4:41 PM, Simon Bernard > > >> wrote: > > Hi, > > I search in DTLS RFC 6347 if the epoch should be (re)set > to 0 > when we start a resume handshake, or if we keep the last used > value, or the last used value+1 ? I can not any clue of > that in > the spec. > Any idea ? > > Thx > Simon > > _______________________________________________ > TLS mailing list > TLS@ietf.org > > https://www.ietf.org/mailman/listinfo/tls > > > > --------------050104010105010402070700 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit I'm sorry to insist, but What did you mean by transport level connection ? For me UDP was a connectionless protocol.

Simon

Le 31/07/2015 18:53, Eric Rescorla a écrit :


On Fri, Jul 31, 2015 at 6:52 PM, Simon Bernard <contact@simonbernard.eu> wrote:
Thx.
What did you mean by connection ?

transport level connection.

 
A resume handshake is a new connection ?

You can also resume when you renegotiate.

-Ekr


Le 31/07/2015 16:54, Eric Rescorla a écrit :
The epoch is set to 0 at the start of each connection and then incremented
with each handshake on that connection.

-Ekr

 On Fri, Jul 31, 2015 at 4:41 PM, Simon Bernard <contact@simonbernard.eu <mailto:contact@simonbernard.eu>> wrote:

    Hi,

      I search in DTLS RFC 6347 if the epoch should be (re)set to 0
    when we start a resume handshake, or if we keep the last used
    value, or the last used value+1 ? I can not any clue of that in
    the spec.
      Any idea ?

    Thx
    Simon

    _______________________________________________
    TLS mailing list
     TLS@ietf.org <mailto:TLS@ietf.org>
    https://www.ietf.org/mailman/listinfo/tls





--------------050104010105010402070700--