Re: [DNSOP] [dnssd] Working Group Last Call - draft-ietf-dnsop-session-signal

Ted Lemon <mellon@fugue.com> Wed, 21 February 2018 18:50 UTC

Return-Path: <mellon@fugue.com>
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 A655B12D965 for <dnsop@ietfa.amsl.com>; Wed, 21 Feb 2018 10:50:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 SEz-WXNac_sy for <dnsop@ietfa.amsl.com>; Wed, 21 Feb 2018 10:50:06 -0800 (PST)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A299129C59 for <dnsop@ietf.org>; Wed, 21 Feb 2018 10:50:06 -0800 (PST)
Received: by mail-qt0-x236.google.com with SMTP id g14so3216718qti.2 for <dnsop@ietf.org>; Wed, 21 Feb 2018 10:50:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=J868/+Sec3ctRcZ4ExhQns6ABafSqjVuH8036kuxLTU=; b=QnUqGq/lWKiGrchXhCVCAZRKl7It0Hl397GWK8SpRM78+Nk2rCiZumiuwydiIU+L6M LxuP27OrpESi9JYk1sikIloruBr0c+SOeBcjI7I185bEs0qxsHSjPdrwttHbL7JnileB grht6FAjFCpDp9gDDcSZWQhU2eUi51kqH9gkmpLWrN88T9ImbLndsxv3Ky+uvTQt+gio +pn+Ox7097Ku3Y5lOBFnvIdcqyuPykPC+mnXIiyp3PN3alHFpWbwNN1c8oFInztWUEiI 9NT8/UXyHLG0vwdQXHEz4mUs7Jkp3UyPN8PLW6nqufaMUxUiO1g8C6u7I5lJ029Qdi+d RfdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=J868/+Sec3ctRcZ4ExhQns6ABafSqjVuH8036kuxLTU=; b=ZpPSElM49/JeSwDgjEp0QVeiEcg3tvFlUqk19Mr1hIH6xW+EkDh+5ULxENDpe8YrV6 zJw7/hVoYIj4zlW5juaEOaqBwHSYlVHk8v3UtByfZqzOn5VpLsYtp6QEEq/jR7yOzkEF el/rpS4hlfkXEhyuTPKuTVT+2rIiQAmz1wW24CtIEIEllDVz29HkRrMZyDju1G09p2fp ABFceJXMK6QZ2xYAPva+dnVKwSAg/jPvgI4PoUe3b3tkm3vVxpthGCMhtLydnkw6BM5m DnqI1+XRXq2tYI+QCgljjN7qDwmDsOPrWuJamztkYg2+Ox8vrvD9mUG4qaMCPz6USXsw /fdw==
X-Gm-Message-State: APf1xPDW0n2Od7sBF+P762RJOvrxBhATRSoX+/4gjOcHN/0j8yuNFenJ +Wix7Cy5rPJj1gtf2erIvOL1GHdrnD0=
X-Google-Smtp-Source: AH8x224Sf0eIXwcU5qrykdhAmZtEhFliNwdvETCiXJr2s3usx+6BwjLpU09KEmVWNkNQodeRAud39w==
X-Received: by 10.237.47.165 with SMTP id m34mr7089387qtd.51.1519239005408; Wed, 21 Feb 2018 10:50:05 -0800 (PST)
Received: from [192.168.1.147] (c-24-60-163-103.hsd1.ma.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id q34sm5666619qkh.73.2018.02.21.10.50.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Feb 2018 10:50:04 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ted Lemon <mellon@fugue.com>
X-Mailer: iPad Mail (15A372)
In-Reply-To: <8225F726-323C-4078-9CB5-C6672025494B@apple.com>
Date: Wed, 21 Feb 2018 13:50:03 -0500
Cc: "Jan Komissar (jkomissa)" <jkomissa@cisco.com>, "dnssd@ietf.org" <dnssd@ietf.org>, dnsop <dnsop@ietf.org>, "doh@ietf.org" <doh@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D820F924-A463-49A1-9168-5FE4F4B8A153@fugue.com>
References: <CADyWQ+GsU9dL8D58Eko0w9mVRMMTZ7f9NQKx3a0XS7oUGHjniQ@mail.gmail.com> <91E3DCED-7A40-4454-9809-EBF68E942DB0@vpnc.org> <02FF7C21-3421-40C5-A530-BE1D814237B2@cisco.com> <976312C8-4424-4642-A150-21F25FB137EE@fugue.com> <5AFBBFBE-CF5A-4F7A-9AC9-F7E0040BBABD@cisco.com> <8225F726-323C-4078-9CB5-C6672025494B@apple.com>
To: Stuart Cheshire <cheshire@apple.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kahy3Q4LHSKDnCEn20QKm4o4f4g>
Subject: Re: [DNSOP] [dnssd] Working Group Last Call - draft-ietf-dnsop-session-signal
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 21 Feb 2018 18:50:23 -0000

On Feb 21, 2018, at 1:39 PM, Stuart Cheshire <cheshire@apple.com> wrote:
> I think Jan makes a good point.
> 
> Suppose there’s a server that supports DNS over TCP, and DSO signaling, and Push Notifications, and DNS Update, and maybe other things.
> 
> Now suppose a client connects to that server. The server doesn’t know what that client is going to do. The client may do queries over TCP, or DNS updates. It may do queries over TCP and use the DSO signaling to request a longer inactivity timeout. It may request Push Notifications (which are currently specified to require TLS). It may do all of those.
> 
> When the server receives an incoming TCP connection request from a client, what are the first bytes received over that TCP connection? Are they a DNS header and message body? Are they a TLS handshake message? Can it be either? How does the server know?

Doesn’t dns over tls use a different port?