IETF Logo Mail Archive

Re: [dnssd] Last Call: <draft-ietf-dnssd-requirements-04.txt> (Requirements for Scalable DNS-SD/mDNS Extensions) to Informational RFC

Markus Stenberg <markus.stenberg@iki.fi> Mon, 05 January 2015 11:44 UTC

Return-Path: <markus.stenberg@iki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E6F41A3BA4; Mon, 5 Jan 2015 03:44:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Level:
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 SmTAuBxq0XQS; Mon, 5 Jan 2015 03:44:31 -0800 (PST)
Received: from kirsi1.inet.fi (mta-out1.inet.fi [62.71.2.203]) by ietfa.amsl.com (Postfix) with ESMTP id D21DC1A2130; Mon, 5 Jan 2015 03:44:29 -0800 (PST)
Received: from poro.lan (80.220.64.126) by kirsi1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 546BDD4B053732D9; Mon, 5 Jan 2015 13:44:28 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Subject: Re: [dnssd] Last Call: <draft-ietf-dnssd-requirements-04.txt> (Requirements for Scalable DNS-SD/mDNS Extensions) to Informational RFC
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <20141217201155.19208.95569.idtracker@ietfa.amsl.com>
Date: Mon, 05 Jan 2015 13:44:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <90A26CE2-87CC-4C8C-BEF9-FDF021C4FE97@iki.fi>
References: <20141217201155.19208.95569.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gsHU_Vdi7AFM7BzKUNs1Y_8H_s0
X-Mailman-Approved-At: Mon, 05 Jan 2015 08:09:52 -0800
Cc: dnssd@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jan 2015 11:44:33 -0000

(Sorry about the late reply, too much vacation.. *grin*)

Comments:

- in e.g. section 2, I find use of ‘DNS-SD/mDNS framework’ confusing. DNS-SD works across links just fine; it is plain DNS. I would also omit the framework. Alternatively, perhaps DNS-SD+mDNS would convey the meaning better. section 6.5 uses ‘DNS-SD + mDNS implementation’ once.

- use case F: is it really justified? it is just mentioned in REQ14. based on my reading, if it was just added to C’s list of link technologies, it would be also inherited by D and E..

- REQ2: Does it apply to C? Small business/homenet + scopes - what would be the example?

- REQ5: I am not sure what ‘integrate’ means here. Unidirectional access (SSD -> DNS-SD/mDNS? SSD <- DNS-SD/mDNS?)? Bidirectional?

Cheers,

-Markus

v2.23.0 | Report a Bug | By Email