[homenet] simple-naming-03: terminology

"STARK, BARBARA H" <bs7652@att.com> Wed, 07 November 2018 06:24 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 3388312785F for <homenet@ietfa.amsl.com>; Tue, 6 Nov 2018 22:24:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.602
X-Spam-Level:
X-Spam-Status: No, score=-0.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=1.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no 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 ydhAtYmYka1v for <homenet@ietfa.amsl.com>; Tue, 6 Nov 2018 22:24:54 -0800 (PST)
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 DCE90127333 for <homenet@ietf.org>; Tue, 6 Nov 2018 22:24:54 -0800 (PST)
Received: from pps.filterd (m0049287.ppops.net [127.0.0.1]) by m0049287.ppops.net-00191d01. (8.16.0.22/8.16.0.22) with SMTP id wA73PXAI014554 for <homenet@ietf.org>; Tue, 6 Nov 2018 22:32:02 -0500
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049287.ppops.net-00191d01. with ESMTP id 2nkn4kw49f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <homenet@ietf.org>; Tue, 06 Nov 2018 22:32:01 -0500
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 wA73W05T019015 for <homenet@ietf.org>; Tue, 6 Nov 2018 22:32:00 -0500
Received: from zlp30486.vci.att.com (zlp30486.vci.att.com [135.47.91.177]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id wA73VsG2018893 for <homenet@ietf.org>; Tue, 6 Nov 2018 22:31:54 -0500
Received: from zlp30486.vci.att.com (zlp30486.vci.att.com [127.0.0.1]) by zlp30486.vci.att.com (Service) with ESMTP id 1F6BC4048B5B for <homenet@ietf.org>; Wed, 7 Nov 2018 03:31:54 +0000 (GMT)
Received: from GAALPA1MSGHUBAC.ITServices.sbc.com (unknown [130.8.218.152]) by zlp30486.vci.att.com (Service) with ESMTPS id 09ED24048B5A for <homenet@ietf.org>; Wed, 7 Nov 2018 03:31:54 +0000 (GMT)
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.253]) by GAALPA1MSGHUBAC.ITServices.sbc.com ([130.8.218.152]) with mapi id 14.03.0415.000; Tue, 6 Nov 2018 22:31:53 -0500
From: "STARK, BARBARA H" <bs7652@att.com>
To: HOMENET <homenet@ietf.org>
Thread-Topic: simple-naming-03: terminology
Thread-Index: AdR1us7WDaNZjG+gSyqmbejgHEuKyA==
Date: Wed, 7 Nov 2018 03:31:53 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E6114DF1E98E@GAALPA1MSGUSRBF.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.221.245]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-07_03:, , 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 mlxscore=0 impostorscore=0 mlxlogscore=485 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1811070029
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/YeH4hqWU6zMrim0aVWiIwUC4Ndc>
Subject: [homenet] simple-naming-03: terminology
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 07 Nov 2018 06:24:56 -0000

I've done an individual review of simple-naming-03. I'm splitting the comments up into several emails, just in case there's anything to discuss related to each topic. It'll take me some time to get all the emails written (in between doing other things).

This email has all of my comments related to terminology.

Section 2
Name: a forward domain  under which information about local services will be published
<bhs> What is a forward domain? I can't find a definition for this term. There's forward DNS (as a process that is followed for domain name resolution), but not forward domain. It seems like this is just a domain. Maybe: 
Name: a domain name space that can be used to resolve queries for information about local (inside the homenet) services

Authority: a name server that is authoritative for at least one
      forward domain and one or two reverse domains  that are applicable
      to that network and is capable of signing and publishing the zones
      using DNSSEC
<bhs> I can't find the definition of "reverse domain", either.  Include DNSSEC reference. Could this be:
Authority: a name server that signs its DNS responses using DNSSEC [RFC4035], is authoritative for the local services domain name and for domains used for reverse DNS queries of IPv4 and IPv6 addresses of devices inside the homenet, and maintains SOA records for all zones within the local services domain

Resolution: a full-service caching DNS resolver that fully
      supports EDNS(0)  and queries with the DO  bit set
<bhs> Needs references: "... supports EDNS(0)  [RFC6891] and queries with the DNSSEC OK bit [RFC3225] set"

"publish"
<bhs> "publish" is widely used in the draft in various contexts, but I can't find a good definition of what is really meant by "publish" wrt DNS. Is there a different term that is used in DNS-related RFCs? I notice the DNS-SD RFC and dnssd roadmap don't use the term "publish".

Section 3 Terminology
<bhs> Put this before Requirements (directly after Introduction)?

HNR Homenet Router
<bhs> Should this maybe be "Homenet Router [RFC7368]"?

SHNR
<bhs> Term isn't used. But maybe it should be used in many places where "HNR" is used? And maybe it should be "Homenet Router that implements the requirements in this document".

AHNR
<bhs> Not used in document and not needed. Delete? Alternately, include reference to where AHNR is defined.

Forward Mapping  A mapping between a host name or service name and
      some information about that host or service.
<bhs> "some information" is very vague. Could this be "resource records"? And can we be explicit as to which RR is used to achieve the forward mapping? PTR?

Reverse Mapping  A mapping between an IP address and the host that
      has that IP address.
<bhs> Fuzzy definition. This is also done with PTR RR?

Homenet Domain  A domain name that is used for publishing the names
      of devices and services that are present on the homenet.  By
      default, 'home.arpa.'
<bhs> Reference at end to [RFC8375] ?

"root" and other "tree" language
There's a lot of DNS structure terminology in this doc that general readers may not be familiar with, such as "root", "tree", etc. Maybe include a reference where people can go to understand this terminology (pointed to from inside the terminology section)? I don't think you need to explain it here -- just tell people where to go.

" HNRs implementing this specification  "
<bhs> SHNR ?

stateless name service, stateful name service
<bhs> I'm not completely sure what "stateful" and "stateless" mean in the context of name services. Include in terminology with pointers to docs that define them? Is "stateful name server" the same as a name server that does DNS over TCP = RFC7766? And stateless means it doesn't do DNS over TCP? Or something else?

Name service for reverse mapping subdomains is only provided if one
   or more HNRs can provide stateful service.  If no such server is
   present, the reverse mapping subdomains are not served.  If stateful
   servers are present, the primary and secondary servers for these
   subdomains will be the same as for the homenet domain.
<bhs> I really didn't understand this paragraph. Not sure if it's a terminology issue for me.

5.2.  Link Names ...
These names are determined using HNCP .
<bhs> include reference: "...HNCP [RFC7788]"

7. Publication
Reverse mappings are published
   using Homenet Reverse Mapping Update Protocol Section 7.2.
<bhs> Include reference to draft?

8.  Host Configuration
   Each HNR provides a Homenet DNS Proxy .  
<bhs> What is a "Homenet DNS Proxy" and how does it differ from a Discovery Proxy for Multicast DNS-Based Service Discovery [draft-ietf-dnssd-hybrid]?
<bhs> nit: s/ descried  / described  /

14.  Management Considerations ...
   simply using the DNS Service Discovery
   protocol.
<bhs> Is DNS-SD really a protocol? I never thought of it as one.