Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsop-session-signal-00.txt

Ray Bellis <ray@isc.org> Wed, 06 July 2016 22:33 UTC

Return-Path: <ray@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7ACA12B017 for <dnsop@ietfa.amsl.com>; Wed, 6 Jul 2016 15:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.327
X-Spam-Level:
X-Spam-Status: No, score=-8.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, 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 qfnK_GVs8Zt0 for <dnsop@ietfa.amsl.com>; Wed, 6 Jul 2016 15:33:02 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) (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 66952128E18 for <dnsop@ietf.org>; Wed, 6 Jul 2016 15:33:02 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 11FFB1FCAB3; Wed, 6 Jul 2016 22:32:59 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id DF14616009E; Wed, 6 Jul 2016 22:32:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id CA9ED16009D; Wed, 6 Jul 2016 22:32:57 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id d_N-HbmUjsdV; Wed, 6 Jul 2016 22:32:57 +0000 (UTC)
Received: from rays-mbp-3.local (unknown [46.227.151.81]) by zmx1.isc.org (Postfix) with ESMTPSA id 39970160042; Wed, 6 Jul 2016 22:32:57 +0000 (UTC)
To: Ted Lemon <mellon@fugue.com>
References: <20160706221423.26712.42026.idtracker@ietfa.amsl.com> <33bde57f-3160-acc3-e483-605eb13aa283@isc.org> <CAPt1N1m=BTj+AqOr51LGm6J1Gjgxq_67JQ2wGbJE6-FxMPGqjA@mail.gmail.com>
From: Ray Bellis <ray@isc.org>
Message-ID: <7162f924-2af7-3bcd-6318-f36b3da5f406@isc.org>
Date: Wed, 06 Jul 2016 23:32:55 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <CAPt1N1m=BTj+AqOr51LGm6J1Gjgxq_67JQ2wGbJE6-FxMPGqjA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ebsgw7jx3LIYTEQ6L4Saq7nTwZU>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsop-session-signal-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2016 22:33:04 -0000

On 06/07/2016 23:28, Ted Lemon wrote:
> Hm, you seem to have left out a definition of what a "session" is.   Do
> you mean a TCP connection?   Are you referring to something that's
> already defined in a document that I have, lamentably, not read?  (In
> which case, a reference would be helpful).

See the editorial note at the end of §3:

  << RB: OSI Layer 5 session analog?  This is obviously intended for
   TCP "sessions" which aren't distinct from Layer 4, but is this also
   applicable to DNS-o-DTLS, or DNS over UDP with an EDNS cookie - I
   think probably "yes" for the former, but "no" for the latter.  I'm
   wondering whether "session" is even the right term to be using
   here >>

So, yes, our start point is TCP, but it might apply to other protocols
that give the effect of a single end-to-end connection.  That's TBD.

Ray