IETF Logo Mail Archive

Re: [dnssd] Genart last call review of draft-ietf-dnssd-push-20

Tom Pusateri <pusateri@bangj.com> Tue, 02 July 2019 19:42 UTC

Return-Path: <pusateri@bangj.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C258C12076B; Tue, 2 Jul 2019 12:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 KVaiNEu25vNe; Tue, 2 Jul 2019 12:42:14 -0700 (PDT)
Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C51F4120738; Tue, 2 Jul 2019 12:42:14 -0700 (PDT)
Received: from [172.16.10.104] (mta-107-13-246-59.nc.rr.com [107.13.246.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id C7EE333ADE; Tue, 2 Jul 2019 15:42:13 -0400 (EDT)
From: Tom Pusateri <pusateri@bangj.com>
Message-Id: <886A4A9E-E986-477B-9681-2740E20EBAA2@bangj.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A415CF69-52F4-45F1-B5EE-262AF91680EB"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3560.7\))
Date: Tue, 02 Jul 2019 15:42:12 -0400
In-Reply-To: <CAPDSy+7om=cBW51cyuPea9nabgJuRV3M+++gA7sy8VzfNpkn6Q@mail.gmail.com>
Cc: Robert Sparks <rjsparks@nostrum.com>, draft-ietf-dnssd-push.all@ietf.org, DNSSD <dnssd@ietf.org>
To: David Schinazi <dschinazi.ietf@gmail.com>
References: <156175221593.21875.9525138908968318905@ietfa.amsl.com> <9E6DE124-9262-4870-A920-4E707A38DC08@bangj.com> <CAPDSy+7om=cBW51cyuPea9nabgJuRV3M+++gA7sy8VzfNpkn6Q@mail.gmail.com>
X-Mailer: Apple Mail (2.3560.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/jjS5cCOdcCrPQb8Au3hGSNSmVBY>
Subject: Re: [dnssd] Genart last call review of draft-ietf-dnssd-push-20
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2019 19:42:23 -0000

Thanks David.

The only other transport I could see being relevant in the future is QUIC. But there are lots of unknowns about DNS over QUIC at present so I think we can safely assume that would require a new PUSH draft to specify the behavior.

So I think your suggestion is a good one.

Tom


> On Jul 2, 2019, at 3:36 PM, David Schinazi <dschinazi.ietf@gmail.com> wrote:
> 
> Hi Tom,
> 
> If the protocol is restricted to TLS over TCP, it should send a TLS close_notify, not a TCP RST.
> TLS close_notify is cryptographically guaranteed to originate from the peer,
> whereas TCP RST can be injected by an on-path entity to cause truncation attacks.
> 
> Thanks,
> David
> 
> 
> > Page 23, top of page: Since section 4 restricts this protocol to TLS over TCP,
> > the "(or equivalent for other protocols)" phrase should be removed.
> 
> Good catch. I removed all instances of "(or equivalent for other protocols)”

v2.23.0 | Report a Bug | By Email