[dnssd] Alexey Melnikov's No Objection on draft-ietf-dnssd-hybrid-07: (with COMMENT)

Alexey Melnikov <aamelnikov@fastmail.fm> Wed, 29 November 2017 17:58 UTC

Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: dnssd@ietf.org
Delivered-To: dnssd@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 369C51288A9; Wed, 29 Nov 2017 09:58:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dnssd-hybrid@ietf.org, Tim Chown <tim.chown@jisc.ac.uk>, dnssd-chairs@ietf.org, tim.chown@jisc.ac.uk, dnssd@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151197830321.8005.13053135592991202256.idtracker@ietfa.amsl.com>
Date: Wed, 29 Nov 2017 09:58:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/Xt8-daZDQePohYg0xFC8vPXNwyA>
Subject: [dnssd] Alexey Melnikov's No Objection on draft-ietf-dnssd-hybrid-07: (with COMMENT)
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 29 Nov 2017 17:58:23 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-dnssd-hybrid-07: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


This is a well written document. I have a few clarifying questions which I
think will improve the document.

In 5.3:

   To accomodate this difference in allowable characters, a Discovery
   Proxy SHOULD support having two separate subdomains delegated to it
   for each link it serves, one whose name is allowed to contain
   arbitrary Net-Unicode text [RFC5198], and a second more constrained
   subdomain whose name is restricted to contain only letters, digits,
   and hyphens, to be used for host name records (names of 'A' and

Am I correct that Punicode encoded A-Labels are still valid here? It would be
good to say so.

   'AAAA' address records).

5.5.4.  No Text Encoding Translation

   A Discovery Proxy does no translation between text encodings.
   Specifically, a Discovery Proxy does no translation between Punycode

Punycode needs an Informative reference.

   and UTF-8,