Re: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt

Ray Bellis <ray@bellis.me.uk> Fri, 08 July 2016 16:30 UTC

Return-Path: <ray@bellis.me.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C907612D7C4; Fri, 8 Jul 2016 09:30:41 -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, RCVD_IN_DNSWL_NONE=-0.0001] 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 ewcpNAPLbYWN; Fri, 8 Jul 2016 09:30:35 -0700 (PDT)
Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23D1612D783; Fri, 8 Jul 2016 09:30:17 -0700 (PDT)
Received: from [46.227.151.81] (port=53253 helo=rays-mbp-3.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1bLYfN-0006cL-7d (Exim 4.72) (return-path <ray@bellis.me.uk>); Fri, 08 Jul 2016 17:30:13 +0100
To: Ralph Droms <rdroms.ietf@gmail.com>, draft-ietf-homenet-hncp-bis.all@ietf.org
References: <20160708142002.32180.68068.idtracker@ietfa.amsl.com> <71A6404B-544A-4A9F-8EB6-E9CC3E8EC3EF@gmail.com>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <c70dc87c-395e-db96-a51e-362b58a2f92e@bellis.me.uk>
Date: Fri, 8 Jul 2016 17:30:15 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <71A6404B-544A-4A9F-8EB6-E9CC3E8EC3EF@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/7prJ5G24cbTHboCKMoGoSDjpl6w>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-hncp-bis-00.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2016 16:30:42 -0000


On 08/07/2016 17:25, Ralph Droms wrote:
> I took a quick look at draft-ietf-homenet-hncp-bis-00, including a
> diff; seems the only change is to solve the .home problem.  I don't
> think I quite understand the new text and here's a suggested
> clarification:
> 
> OLD:
> 
> A default value for this TLV MUST be set, although the default value
> of the Domain-Name TLV (Section 10.6) is out of scope of this
> document, and an administrator MAY configure the announcement of a
> Domain-Name TLV for the network.
> 
> NEW:
> 
> The administrator MUST configure the announcement of a network-wide 
> zone suffix through the Domain-Name TLV.
> 
> As far as I can tell, draft-ietf-homenet-hncp-bis-00 does not address
> errata 4718.  While this errata has not yet been verified, in my
> opinion *something* has to be done to correct the text around
> "Multicast DNS Proxy".  If "Multicast DNS Proxy" is intended to refer
> to "Hybrid Proxy" in draft-ietf-dnssd-hybrid-03, the appropriate
> normative reference will constitute a downref in
> draft-ietf-homenet-hncp-bis-00.

The instruction to the authors were to incorporate the original .home
errata verbatim, and also to fix the error with options 37/38 being the
wrong way around in two diagrams.

If there is to be further wordsmithing on that we'd need to take that up
with our AD.

As for errata 4718, I fully expect that it will be incorporated in a
further revision just as soon as it has been verified (and subject to a
resolution of any resulting downref issue).

kind regards,

Ray