Re: [homenet] Adam Roach's No Objection on draft-ietf-homenet-dot-12: (with COMMENT)

Ted Lemon <ted.lemon@nominum.com> Mon, 28 August 2017 22:29 UTC

Return-Path: <Ted.Lemon@nominum.com>
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 22DE9132139; Mon, 28 Aug 2017 15:29:46 -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 54cslXnTL-1y; Mon, 28 Aug 2017 15:29:44 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 81D24132113; Mon, 28 Aug 2017 15:29:41 -0700 (PDT)
Received: from mail.nominum.com (sjc1-exch01.win.nominum.com [IPv6:2620:0:b60:fab4:1026:2045:f02a:5f75]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id C6AB874003F; Mon, 28 Aug 2017 22:29:10 +0000 (UTC)
Received: from cavall.ether.lede.home (24.60.163.103) by SJC1-EXCH01.WIN.NOMINUM.COM (64.89.235.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1034.26; Mon, 28 Aug 2017 15:29:06 -0700
From: Ted Lemon <ted.lemon@nominum.com>
Message-ID: <6A42DD6D-CE4C-4172-BE83-C0A259A4368D@nominum.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_90859136-B7B9-47F8-B226-95F264D42F68"
MIME-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 28 Aug 2017 18:29:08 -0400
In-Reply-To: <150395805175.13203.12325524217824839037.idtracker@ietfa.amsl.com>
CC: The IESG <iesg@ietf.org>, draft-ietf-homenet-dot@ietf.org, Ray Bellis <ray@bellis.me.uk>, homenet-chairs@ietf.org, homenet@ietf.org
To: Adam Roach <adam@nostrum.com>
References: <150395805175.13203.12325524217824839037.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3273)
X-Originating-IP: [24.60.163.103]
X-ClientProxiedBy: SJC1-EXCH02.WIN.NOMINUM.COM (64.89.235.69) To SJC1-EXCH01.WIN.NOMINUM.COM (64.89.235.83)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/m2-u5Zlv3WyTrq6VrIDIcRgeI40>
Subject: Re: [homenet] Adam Roach's No Objection on draft-ietf-homenet-dot-12: (with COMMENT)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 28 Aug 2017 22:29:46 -0000

El Aug 28, 2017, a les 6:07 PM, Adam Roach <adam@nostrum.com> va escriure:
> Section 4 contains a list that it describes as defining "the behavior of [DNS]
> systems". Item number 7 seems to be something else: I don't know what code or
> configuration would result from this statement. Maybe move this item to section
> 3?

This is the format that RFC 6761 requires us to follow, which is why it's being done this way.   I think the text makes sense if you read it with the RFC 6761 list of criteria in section 5 in mind.   So I don't think it makes sense to move it, although I agree it scans a bit strangely. :)

> With the explanation in section 6:
> 
>   it may be useful for the resolver to identify different
>   homenets on which it has resolved names
> 
> Doesn't this mitigation in the security section require name resolution
> libraries to recognize names that end in ".home.arpa." as special so that it
> can treat them differently?

Section 6 is talking about future work.   If we come up with a way to do this, then it would update this document, changing the normative requirement.