Re: [homenet] Status of draft-tldm-simple-homenet-naming CFA

"STARK, BARBARA H" <bs7652@att.com> Fri, 11 August 2017 13:32 UTC

Return-Path: <bs7652@att.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 BA78A1324A7 for <homenet@ietfa.amsl.com>; Fri, 11 Aug 2017 06:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 jTx4ehxur-FX for <homenet@ietfa.amsl.com>; Fri, 11 Aug 2017 06:32:42 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 06A24132488 for <homenet@ietf.org>; Fri, 11 Aug 2017 06:32:42 -0700 (PDT)
Received: from pps.filterd (m0049295.ppops.net [127.0.0.1]) by m0049295.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v7BDPOBW030876; Fri, 11 Aug 2017 09:32:26 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049295.ppops.net-00191d01. with ESMTP id 2c9cdqtdk7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 11 Aug 2017 09:32:26 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v7BDWOgs013429; Fri, 11 Aug 2017 09:32:24 -0400
Received: from alpi134.aldc.att.com (alpi134.aldc.att.com [130.8.217.4]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v7BDWIZk013314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 11 Aug 2017 09:32:18 -0400
Received: from GAALPA1MSGHUBAE.ITServices.sbc.com (GAALPA1MSGHUBAE.itservices.sbc.com [130.8.218.154]) by alpi134.aldc.att.com (RSA Interceptor); Fri, 11 Aug 2017 13:32:03 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.30]) by GAALPA1MSGHUBAE.ITServices.sbc.com ([130.8.218.154]) with mapi id 14.03.0319.002; Fri, 11 Aug 2017 09:32:02 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: Ted Lemon <mellon@fugue.com>, Andrew Sullivan <ajs@anvilwalrusden.com>
CC: HOMENET <homenet@ietf.org>
Thread-Topic: [homenet] Status of draft-tldm-simple-homenet-naming CFA
Thread-Index: AdMSExv6TskYwTm0TxW2ixuYvce/UAAJxMKAAABdugAAGQAhYA==
Date: Fri, 11 Aug 2017 13:32:02 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DBF7F5C@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <2D09D61DDFA73D4C884805CC7865E6114DBF5904@GAALPA1MSGUSRBF.ITServices.sbc.com> <20170810203843.xq7wxdxp27vqt4pz@mx4.yitter.info> <CAPt1N1k=KPxA2GX8K=jW6VucbVuGNox4NWc-y5Az1APfU-m7qQ@mail.gmail.com>
In-Reply-To: <CAPt1N1k=KPxA2GX8K=jW6VucbVuGNox4NWc-y5Az1APfU-m7qQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.233.7]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-08-11_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1708110215
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/9oTMpb31Gieqfzmq7SJFPk2wa_8>
Subject: Re: [homenet] Status of draft-tldm-simple-homenet-naming CFA
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: Fri, 11 Aug 2017 13:32:44 -0000

> From: Ted Lemon
> Barbara, I seem to recall that you were enthusiastic about the work when it was discussed in the meeting.   You're allowed to be one of the people who's in favor of it, despite being chair.   Indeed, as > chair, you can just adopt it by fiat if you want.   I actually agree with Ray and Michael that Juliusz reasoning was flawed, and am definitely in favor of adopting it and working on it.   I also agree with 
> Andrew that it shouldn't be the final word on naming in the homenet.

Here are my non-chair thoughts.
I do think there is value in defining a home network naming / DNS architecture. I (enthusiastically) support adoption of the concept.
The non-boilerplate part of the table of contents is about "Name Resolution", with headers for "Configuring Resolvers", "Configuring Service Discovery", "Resolution of local names", "DNSSEC Validation", "Support for Multiple Provisioning Domains", "Using the Local Namespace While Away From Home". I support these as a good initial set of headers for a table of contents.
I don't like requiring DNS proxy in all homenet routers and would like to explore other options. But the DNS resolver does have to be somewhere in the premises.
I'd like to actually explore what we could for DNSSEC in the context of some holistic home network "key" architecture, and maybe we could discuss some more even while agreeing it's out of scope for this doc. 
I agree with scoping to internal resolution and not dealing with external resolution. But I recognize others might want to discuss more.
I fully agree with this being a separate "provisioning domain", but I'm not fully convinced the proposed solution is the right one. 

Conclusion: As long as we can keep discussion alive and healthy, and not go to WGLC prematurely, I'm in favor of adoption.
The main reason I hesitated to lend support is from bad experience in other groups where authors have tried to object to comments on the basis of "you supported adoption, this text was in the draft when it was adopted, and you didn't object to this text prior to adoption". But so long as the chairs don't tolerate this sort of attitude, I think we'll be fine. BTW, I've never seen that attitude from Ted or Daniel. And I have confidence in the chairs' ability to be intolerant.

Barbara