[dnssd] Pete Resnick's Discuss on draft-ietf-dnssd-requirements-05: (with DISCUSS)
"Pete Resnick" <presnick@qti.qualcomm.com> Fri, 13 March 2015 17:47 UTC
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8451A1AC1; Fri, 13 Mar 2015 10:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level:
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2] autolearn=ham
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 rP65Zf28BmAM; Fri, 13 Mar 2015 10:47:49 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C27841A0145; Fri, 13 Mar 2015 10:47:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150313174749.2435.7999.idtracker@ietfa.amsl.com>
Date: Fri, 13 Mar 2015 10:47:49 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnssd/N2R6NyGeQDD_gheJnGIosWZ0Ezc>
Cc: draft-ietf-dnssd-requirements.all@ietf.org, dnssd@ietf.org, dnssd-chairs@ietf.org, tjc@ecs.soton.ac.uk
Subject: [dnssd] Pete Resnick's Discuss on draft-ietf-dnssd-requirements-05: (with DISCUSS)
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 13 Mar 2015 17:47:55 -0000
Pete Resnick has entered the following ballot position for draft-ietf-dnssd-requirements-05: Discuss 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 http://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: http://datatracker.ietf.org/doc/draft-ietf-dnssd-requirements/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- [Updating to reflect that the IPR disclosure issue is addressed. There is an IPR disclosure that appears for this document, but it was a mistakenly filed disclosure that still remains in the system. We will deal with that issue separately.] Section 5: OLD Devices on different links may have the same mDNS name (perhaps due to vendor defaults), because link-local mDNS names are only guaranteed to be unique on a per-link basis. Also, even devices that are on the same link may have similar-looking names, such as one device with the name "Bill" and another device using the similar- looking name "Bi11" (using the digit "1" in place of the letter "l"). This may lead to a local label disambiguation problem between presented results. SSD should support rich internationalized labels within Service Instance Names, as DNS-SD/mDNS does today. SSD must not negatively impact the global DNS namespace or infrastructure. The part about name collisions is fine, and should be said. The part about disambiguating similar characters is a rat's nest I really think you need to avoid. We can discuss this further, but the i18n community is dealing with this issue right now and it's a mess you really don't want to get into. I think you should simply stick to something like this: NEW Devices on different links may have the same mDNS name (perhaps due to vendor defaults), because link-local mDNS names are only guaranteed to be unique on a per-link basis. SSD needs to deal with name collisions beyond local link considerations. SSD should support rich internationalized labels within Service Instance Names, as DNS-SD/mDNS does today and should look to work in using internationalize strings in application protocols [soon-to-be-RFC-draft-ietf-precis-framework]. SSD must not negatively impact the global DNS namespace or infrastructure.
- [dnssd] Pete Resnick's Discuss on draft-ietf-dnss… Pete Resnick
- Re: [dnssd] Pete Resnick's Discuss on draft-ietf-… Ted Lemon
- Re: [dnssd] Pete Resnick's Discuss on draft-ietf-… Pete Resnick
- Re: [dnssd] Pete Resnick's Discuss on draft-ietf-… Ted Lemon
- Re: [dnssd] Pete Resnick's Discuss on draft-ietf-… Tim Chown
- [dnssd] Further IPR disclosures on draft-ietf-dns… Tim Chown
- Re: [dnssd] Further IPR disclosures on draft-ietf… Daniel Migault
- Re: [dnssd] Further IPR disclosures on draft-ietf… Marc Blanchet
- Re: [dnssd] Further IPR disclosures on draft-ietf… Lynn, Kerry E
- Re: [dnssd] Further IPR disclosures on draft-ietf… Marc Blanchet
- Re: [dnssd] Further IPR disclosures on draft-ietf… Ted Lemon
- Re: [dnssd] Further IPR disclosures on draft-ietf… Tim Chown
- Re: [dnssd] Further IPR disclosures on draft-ietf… Ted Lemon
- Re: [dnssd] Further IPR disclosures on draft-ietf… Stuart Cheshire
- [dnssd] Pete Resnick's Discuss on draft-ietf-dnss… Pete Resnick
- Re: [dnssd] Further IPR disclosures on draft-ietf… Tim Chown
- Re: [dnssd] Pete Resnick's Discuss on draft-ietf-… Kerry Lynn
- Re: [dnssd] Pete Resnick's Discuss on draft-ietf-… Kerry Lynn
- Re: [dnssd] Pete Resnick's Discuss on draft-ietf-… Pete Resnick
- Re: [dnssd] Pete Resnick's Discuss on draft-ietf-… Kerry Lynn
- Re: [dnssd] Pete Resnick's Discuss on draft-ietf-… Pete Resnick