Re: [mdnsext] mDNSext features/requirements rollup

peter van der Stok <stokcons@xs4all.nl> Tue, 29 January 2013 09:25 UTC

Return-Path: <stokcons@xs4all.nl>
X-Original-To: mdnsext@ietfa.amsl.com
Delivered-To: mdnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4546621F8BD4 for <mdnsext@ietfa.amsl.com>; Tue, 29 Jan 2013 01:25:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.154
X-Spam-Level:
X-Spam-Status: No, score=-0.154 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fJuUWtVgNqmB for <mdnsext@ietfa.amsl.com>; Tue, 29 Jan 2013 01:25:33 -0800 (PST)
Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by ietfa.amsl.com (Postfix) with ESMTP id 895E121F8B13 for <mdnsext@ietf.org>; Tue, 29 Jan 2013 01:25:33 -0800 (PST)
Received: from roundcube.xs4all.nl (roundcube8.xs4all.net [194.109.20.206]) by smtp-vbr12.xs4all.nl (8.13.8/8.13.8) with ESMTP id r0T9PVAQ054389 for <mdnsext@ietf.org>; Tue, 29 Jan 2013 10:25:32 +0100 (CET) (envelope-from stokcons@xs4all.nl)
Received: from AMontpellier-654-1-228-183.w92-145.abo.wanadoo.fr ([92.145.51.183]) by roundcube.xs4all.nl with HTTP (HTTP/1.1 POST); Tue, 29 Jan 2013 10:25:31 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Tue, 29 Jan 2013 10:25:31 +0100
From: peter van der Stok <stokcons@xs4all.nl>
To: mdnsext@ietf.org
Organization: vanderstok consultancy
Mail-Reply-To: <consultancy@vanderstok.org>
In-Reply-To: <D99048ACAF96354EBFD6A811E3C65ACD1095901E@CH1PRD0811MB407.namprd08.prod.outlook.com>
References: <D99048ACAF96354EBFD6A811E3C65ACD1095901E@CH1PRD0811MB407.namprd08.prod.outlook.com>
Message-ID: <72004462c199494ac7bc486bd95c66ab@xs4all.nl>
X-Sender: stokcons@xs4all.nl (fur7QRI5dVqS3W9ojGdZm2UlhAL3mgvK)
User-Agent: XS4ALL Webmail
X-Virus-Scanned: by XS4ALL Virus Scanner
Subject: Re: [mdnsext] mDNSext features/requirements rollup
X-BeenThere: mdnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: consultancy@vanderstok.org
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <mdnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mdnsext>
List-Post: <mailto:mdnsext@ietf.org>
List-Help: <mailto:mdnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 09:25:34 -0000

Hi Kerry and Stuart,

I went through the req. document

A typo in section 1 line 4:
... find that mDNS does NOT work across routers.  << NOT added by me >>

I do miss the following use case (also missing in hybrid-01 document), 
expected for control networks in building at intallation time.

Devices are connected to a mesh network that is not connected to an 
edge router. These devices can do service disovery as suggested in 
hybrid-1 document, but no DNS server, no DHCP server and no edge router 
are accessible. A DNS proxy can be present. DNS proxy can be configured 
off-line or with specially designed tools on-line.

After connection of this mesh network to an edge router and 
accompanying connection to DNS server, applications in devices are 
expected to use same domain names and be discoverable over edge router.

I hope this case can be made explicit in section 3 point (E) of req 
document, by citing that mesh network can be (temporarily) stand-alone 
without edge router accessibility.
In REQ2: add use case E to cases A and B
In REQ3: add use case E to cases C and D.

Peter van der Stok