Re: [Netconf] Benjamin Kaduk's Discuss on draft-ietf-netconf-zerotouch-25: (with DISCUSS and COMMENT)

Dave Crocker <dcrocker@bbiw.net> Thu, 10 January 2019 17:26 UTC

Return-Path: <dcrocker@bbiw.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18879130EC1; Thu, 10 Jan 2019 09:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=bbiw.net
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 qREgmKyal5x0; Thu, 10 Jan 2019 09:26:36 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 ACD69128D52; Thu, 10 Jan 2019 09:26:36 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id x0AHRa0Z024045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 10 Jan 2019 09:27:37 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bbiw.net; s=default; t=1547141258; bh=6HjfQaDEX/dKUSmO/4IKOPph2u+RlDDTy4IPdJ6vsYc=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Ksbve6fTHVr5OwSNw13hYnuwzFpWwxqMLtmlmFBPSahggxNwfg2p/DkOxjPQFwi7E SpwcVLP/D6RXjm+5yEYJ/2xctmZMjt82Uva295IUufNZTjoWMYidSwHCWEQ+mfgPdU kzUkbrD1ZEl3qPu1dWDvl5cW5G156G2lTavVlBGI=
To: Kent Watsen <kwatsen@juniper.net>, Dave Crocker <dcrocker@bbiw.net>, Adam Roach <adam@nostrum.com>, Alexey Melnikov <aamelnikov@fastmail.fm>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-netconf-zerotouch@ietf.org" <draft-ietf-netconf-zerotouch@ietf.org>, "netconf-chairs@ietf.org" <netconf-chairs@ietf.org>, "netconf@ietf.org" <netconf@ietf.org>, Benjamin Kaduk <kaduk@mit.edu>
References: <154390493154.31734.13025584839857369253.idtracker@ietfa.amsl.com> <F526DA60-77EC-45D6-ADE0-B345020A89BF@juniper.net> <20181230003002.GC57547@kduck.kaduk.org> <5DCD6C74-7918-45AB-BEA7-2C1A020B4411@juniper.net> <20190106050255.GJ28515@kduck.kaduk.org> <35A436B3-5D57-4015-A51E-5F9A1E349D31@juniper.net> <DAC627AC-8453-41D2-B95C-BC25746E66C1@juniper.net> <cc5adc78-6751-fabf-03d2-e0c65f8a6c91@bbiw.net> <F844EDFB-3E15-47FB-A714-06363B996FC2@juniper.net>
From: Dave Crocker <dcrocker@bbiw.net>
Message-ID: <42cddba1-9f59-f19f-176f-197f0c0c0c96@bbiw.net>
Date: Thu, 10 Jan 2019 09:26:22 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <F844EDFB-3E15-47FB-A714-06363B996FC2@juniper.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/N6HmspeEEJo_FEE0NtPPxhyOWkg>
Subject: Re: [Netconf] Benjamin Kaduk's Discuss on draft-ietf-netconf-zerotouch-25: (with DISCUSS and COMMENT)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2019 17:26:38 -0000

On 1/9/2019 1:12 PM, Kent Watsen wrote:
> Thanks for your prompt reply and, yeah, sometimes the IETF-aliases are wonky.

Seems to have mostly worked for/with me in the past.  I hadn't heard 
that it is inconsistent.  Hmmm...  Might be worth getting ietf sysadmin 
involved to look at logs.

> Your response makes sense to me, but it immediately conjured the question of *why* is _sztp under _tcp, for this case?  This question isn't specifically to you, though your input would be appereciated.

Having no history of the group's activity, and merely looking at the 
relevant draft spec text, I'd assume it merely seemed natural, given 
that (entirely appropriate) use of _tcp for the corresponding SRV record 
-- on its own it certainly looks natural to me, especially given the 
long history of no registration discipline for use of TXT RRsets.

> To clarify, the draft uses DNS in two ways:
>
> 1) the first is for traditional SRV records, for which being under _tcp makes sense.

+1
> 2) the second is for TXT records that, of and in themselves, are not describing a TCP service, so much as providing bootstrapping data, that may or may not cause the device to initiate a subsequent connection (TCP or otherwise).   For this case, we also have the _sztp record under _tcp, but *should* it be under the TLD instead?

Absent deep involvement in the work of the spec, and just basing my view 
on the small bits of the spec I've read, I'd suggest dropping use of 
_tcp for the TXT and just using _sztp as a globally-scoped attrleaf node 
name, registering it in the new attrleaf registry.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net