Re: [dnssd] I-D Action: draft-ietf-dnssd-mdns-relay-02.txt

"Jan Komissar (jkomissa)" <jkomissa@cisco.com> Fri, 22 March 2019 22:27 UTC

Return-Path: <jkomissa@cisco.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54A03124408 for <dnssd@ietfa.amsl.com>; Fri, 22 Mar 2019 15:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=iiQR2MRR; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=LJhlVwkf
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 8kJXLv4E2hOs for <dnssd@ietfa.amsl.com>; Fri, 22 Mar 2019 15:27:07 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6220713158D for <dnssd@ietf.org>; Fri, 22 Mar 2019 15:27:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5966; q=dns/txt; s=iport; t=1553293627; x=1554503227; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=XHOtS6Ja+iU9nMg35d9F5R7Ys0YiCHqxZabMuMhKUUU=; b=iiQR2MRRfKpE7bHAU90a7iHHr3T1xHsdd0/bwTWq1CoxlvGFYUqnvBbM YglPBZCOJuBYU0pazvrCK5ivoJx++zQX8j8f725WLRw0D1FFAP/fDjM4S l8Eet1hOj90OEdERlN6T81iYRsBxyjoqzpA0/GywBWdwU1m/W3m2+00PH k=;
IronPort-PHdr: =?us-ascii?q?9a23=3Amf+mRxcBaJGynCHH8jY8NZRnlGMj4e+mNxMJ6p?= =?us-ascii?q?chl7NFe7ii+JKnJkHE+PFxlwGQD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFn?= =?us-ascii?q?pnwd4TgxRmBceEDUPhK/u/bS89GcVZT1ZN9HCgOk8TE8H7NBXf?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A+AADBYJVc/4YNJK1jHQEBBQEHBQG?= =?us-ascii?q?BUQgBCwGBPVADaHQECycKhASDRwOEUopXSoFoly+BLoEkA1QNAQEYCwmEQAI?= =?us-ascii?q?XhGUiNAkNAQEDAQEJAQMCbRwBC4VLAgQBASERDAEBLAwPAgEIGgImAgICJQs?= =?us-ascii?q?VEAIEE4MiAYFdAxUBDp4UAooUcYEvgngBAQWBNQIOQUGCQBiCDAiBCyQBizE?= =?us-ascii?q?XgUA/gREnDBOCTD6CYQEBAgEBFoFHgwoxgiaKKoJGhDmTZwkCh2GLVRmCAlu?= =?us-ascii?q?FIYt+ixiGAo0iAgQCBAUCDgEBBYFNOCiBLnAVGiEqAYJBCYIBg26FFIU/coE?= =?us-ascii?q?ojEABgR4BAQ?=
X-IronPort-AV: E=Sophos;i="5.60,256,1549929600"; d="scan'208";a="541860244"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 22 Mar 2019 22:27:05 +0000
Received: from XCH-ALN-010.cisco.com (xch-aln-010.cisco.com [173.36.7.20]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x2MMR513022541 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <dnssd@ietf.org>; Fri, 22 Mar 2019 22:27:06 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-010.cisco.com (173.36.7.20) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 22 Mar 2019 17:27:05 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 22 Mar 2019 17:27:04 -0500
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 22 Mar 2019 17:27:04 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XHOtS6Ja+iU9nMg35d9F5R7Ys0YiCHqxZabMuMhKUUU=; b=LJhlVwkf6DyIkkyHE0e8TyXogZH2JoqR+ytEoMvAoK0YRuEaGmbsHpb4hd1PuydgO3v4aBZqHY1/t2R9eieq3+m/wIhEpaYG6EhsvwBAwbJy6oh8w8nd0LShDkb8D6OruVJNEth+RZJvSeoajNDMnyBocYmtzzAJDztIRhm6C1o=
Received: from BN6PR11MB4035.namprd11.prod.outlook.com (10.255.129.225) by BN6PR11MB1505.namprd11.prod.outlook.com (10.172.22.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1730.15; Fri, 22 Mar 2019 22:27:03 +0000
Received: from BN6PR11MB4035.namprd11.prod.outlook.com ([fe80::8d84:c318:ef41:7fc6]) by BN6PR11MB4035.namprd11.prod.outlook.com ([fe80::8d84:c318:ef41:7fc6%5]) with mapi id 15.20.1709.017; Fri, 22 Mar 2019 22:27:03 +0000
From: "Jan Komissar (jkomissa)" <jkomissa@cisco.com>
To: "dnssd@ietf.org" <dnssd@ietf.org>
Thread-Topic: [dnssd] I-D Action: draft-ietf-dnssd-mdns-relay-02.txt
Thread-Index: AQHU2FYhYXRaIta0zEm0sHdf24UajKYYCQMA
Date: Fri, 22 Mar 2019 22:27:03 +0000
Message-ID: <477BD308-DFAB-4324-9065-FB71E017D7F5@cisco.com>
References: <155234154246.23050.13050613828512015781@ietfa.amsl.com>
In-Reply-To: <155234154246.23050.13050613828512015781@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.17.0.190309
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jkomissa@cisco.com;
x-originating-ip: [173.38.117.94]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3a732e5b-54ac-4b28-04d3-08d6af158278
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600127)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:BN6PR11MB1505;
x-ms-traffictypediagnostic: BN6PR11MB1505:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <BN6PR11MB15056918512344F7D4331BC6CB430@BN6PR11MB1505.namprd11.prod.outlook.com>
x-forefront-prvs: 09840A4839
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(346002)(39860400002)(376002)(396003)(136003)(189003)(199004)(2501003)(2616005)(5660300002)(446003)(305945005)(486006)(66574012)(97736004)(229853002)(6486002)(6116002)(82746002)(3846002)(11346002)(476003)(68736007)(14454004)(7736002)(478600001)(25786009)(86362001)(71190400001)(83716004)(5024004)(36756003)(26005)(8936002)(966005)(6306002)(66066001)(33656002)(1730700003)(76176011)(58126008)(6506007)(106356001)(71200400001)(102836004)(105586002)(6436002)(5640700003)(186003)(6246003)(6916009)(2351001)(81166006)(81156014)(316002)(8676002)(99286004)(6512007)(256004)(53936002)(2906002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR11MB1505; H:BN6PR11MB4035.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: YbfZe0cPqFljfIv2CPms1tkvmF5a5KYL44SQ4Dd7sOaOO3+945gooqi14Pn7VmUOg60Iw7QTK6A7MPSIhPIvXSxrGJsbqgvUZ2oC7KANwpW6qgJ7i0cSIYr1Irz3htgiaeXngWfdMqImRLAsn+rdPdCwq0+V7MZJxeGasVbnesmgKWe3gtOzetVALXDiK6qIkbY/QNK1S5VY8UUn9olRt6NZyBlINaletb7EJTwuYXgeISwNuYvNIN8FD4/+yUzfP7XiUxS9CjoK2R8EIbXliorDUaV7dFrT9UzReNhKz47uyjiGgZe6Zx5D17VnDvpsbpYYgpOsh/Wg8eAUUnz/pjPvUjtkkG+pZUV3oVvIexqKPW2/HZ7dEjN9hmZD4tcPEZNW/kZ4CSyQLRUWqUsKauTJ2tEPQMNPhx6vfne7K9I=
Content-Type: text/plain; charset="utf-8"
Content-ID: <C4877DC45B01A24C87B6C2C8626F1336@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3a732e5b-54ac-4b28-04d3-08d6af158278
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Mar 2019 22:27:03.6240 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1505
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.20, xch-aln-010.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/H5g67sQvCb5PIKf9P4IFaZHznuI>
Subject: Re: [dnssd] I-D Action: draft-ietf-dnssd-mdns-relay-02.txt
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Mar 2019 22:27:11 -0000

Hi,

A few comments on this draft:

Section 2 Terminology (pg. 4)
========================
Nit: I would insert this phrase, just be very clear:
Discovery Relay		A network service, as specified by this document, which...

multicast link:
It seems kind of odd that this paragraph contains part of the rationale for the creation of this new service discovery infrastructure. Might it not be better placed elsewhere in the document?

Section 4: Pg 9:
=============
First para: Line 3: … FQDN as *an* Authentication…

Section 8 DSP TLVs, pg 14
=====================
Nit: This document defines the largest number of DSO TLVs of any document so far. I suggest dropping the word "modest."

Section 8.2 mDNS Link Data Discontinue, pg 14
=======================================
Para 1, Line 4, nit: Remove the first instance of "32-bit." (See Secs 8.1 & 8.3)

Section 8.10 Link Prefix, pg 17
=====================
Last line: Should "secondary TLV" be "additional TLV?"

Section 9.1.1 Multicast Link
=====================
Pg 19
Under link-identifier: I would prefer that the link identifiers are unique within each Relay. A Relay SHOULD assign permanent identifiers as links are created, stored in non-volatile memory or generated using a repeatable algorithm. The Discovery Proxy could prefix the link identifier with the Relay name or an internal Relay id. It could be useful to include a TLV to query a Relay for a table of all the links and their on-device defined names (preferably names that can be easily mapped to physical interfaces and/or appear in its user interfaces' representation thereof) and possible some indication of bandwidth. See section 9.1.3, pg 22, last para (before 9.2).

Under hr-name: Does "rich text" mean UTF-8? (like in draft-ietf-dnssd-hybrid-09, sec 5.1, pg. 9 etc.)

Section 9.1.3 Discovery Relay
=====================
pg 22, last para (before 9.2): Although "the details of this sort of configuration are not specified…," maybe it should define a method to extract its results. See comments to link-identifier, above.

Section 9.2 Configuration Files
=====================
pg 23
In Links upstairs-wifi & downstairs-wifi, should "name" be "hr-name"?

Following my comments to 9.1.1 link-identifier, the Link configurations could look like:
Link upstairs-wifi
  id upstairs.en0
  hr-name Upstairs Wifi

Link upstairs-wired
  id upstairs.en1
  hr-name Upstairs Wired

=======

Regards,

Jan.


On 3/11/19, 6:02 PM, "dnssd on behalf of internet-drafts@ietf.org" <dnssd-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote:

    
    A New Internet-Draft is available from the on-line Internet-Drafts directories.
    This draft is a work item of the Extensions for Scalable DNS Service Discovery WG of the IETF.
    
            Title           : Multicast DNS Discovery Relay
            Authors         : Ted Lemon
                              Stuart Cheshire
    	Filename        : draft-ietf-dnssd-mdns-relay-02.txt
    	Pages           : 29
    	Date            : 2019-03-11
    
    Abstract:
       This document complements the specification of the Discovery Proxy
       for Multicast DNS-Based Service Discovery.  It describes a
       lightweight relay mechanism, a Discovery Relay, which, when present
       on a link, allows remote clients, not attached to that link, to
       perform mDNS discovery operations on that link.
    
    
    The IETF datatracker status page for this draft is:
    https://datatracker.ietf.org/doc/draft-ietf-dnssd-mdns-relay/
    
    There are also htmlized versions available at:
    https://tools.ietf.org/html/draft-ietf-dnssd-mdns-relay-02
    https://datatracker.ietf.org/doc/html/draft-ietf-dnssd-mdns-relay-02
    
    A diff from the previous version is available at:
    https://www.ietf.org/rfcdiff?url2=draft-ietf-dnssd-mdns-relay-02
    
    
    Please note that it may take a couple of minutes from the time of submission
    until the htmlized version and diff are available at tools.ietf.org.
    
    Internet-Drafts are also available by anonymous FTP at:
    ftp://ftp.ietf.org/internet-drafts/
    
    _______________________________________________
    dnssd mailing list
    dnssd@ietf.org
    https://www.ietf.org/mailman/listinfo/dnssd