Re: [mdnsext] dnssdext charter

Alf Watt <> Wed, 28 August 2013 01:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 05D1121E80FE for <>; Tue, 27 Aug 2013 18:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 66K9ZTZX9Pim for <>; Tue, 27 Aug 2013 18:12:02 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 6C13721E80FD for <>; Tue, 27 Aug 2013 18:12:01 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server id; Wed, 28 Aug 2013 01:12:00 +0000
Received: from mail72-am1 (localhost []) by (Postfix) with ESMTP id 8FF312C0073; Wed, 28 Aug 2013 01:12:00 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:; KIP:(null); UIP:(null); IPV:NLI;; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zzbb2dI98dI9371I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL186068h8275bh8275dh1de097hz2fh2a8h839h944he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1fe8h1ff5h1155h)
Received-SPF: pass (mail72-am1: domain of designates as permitted sender) client-ip=;; ; ;
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(479174003)(377454003)(24454002)(199002)(189002)(51704005)(81542001)(49866001)(47976001)(50986001)(47736001)(81342001)(76796001)(4396001)(76786001)(81686001)(56816003)(77096001)(69226001)(81816001)(74366001)(51856001)(83322001)(63696002)(19580405001)(19580395003)(36756003)(76176001)(46102001)(74876001)(80022001)(66066001)(65816001)(80976001)(74502001)(74662001)(74706001)(47446002)(31966008)(53806001)(54356001)(77982001)(54316002)(59766001)(56776001)(83072001)(79102001)(76482001); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR08MB085;; CLIP:; RD:InfoNoRecords; A:1; MX:1; LANG:en;
Received: from mail72-am1 (localhost.localdomain []) by mail72-am1 (MessageSwitch) id 1377652316869835_23745; Wed, 28 Aug 2013 01:11:56 +0000 (UTC)
Received: from (unknown []) by (Postfix) with ESMTP id D067C2E015A; Wed, 28 Aug 2013 01:11:56 +0000 (UTC)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Wed, 28 Aug 2013 01:11:56 +0000
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.16.347.3; Wed, 28 Aug 2013 01:11:47 +0000
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.745.25; Wed, 28 Aug 2013 01:11:46 +0000
Received: from ([]) by ([]) with mapi id 15.00.0745.000; Wed, 28 Aug 2013 01:11:46 +0000
From: Alf Watt <>
To: "Ralph Droms (rdroms)" <>, "" <>
Thread-Topic: [mdnsext] dnssdext charter
Thread-Index: AQHOon7CNNwOvc1wFkGcFaSQRAQGyJmpXNeA
Date: Wed, 28 Aug 2013 01:11:45 +0000
Message-ID: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
x-forefront-prvs: 09525C61DB
Content-Type: text/plain; charset="us-ascii"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mdnsext] dnssdext charter
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 28 Aug 2013 01:12:08 -0000

I'd like to make sure we don't loose track of the 'A' Personal Area
Networks scenario, +1 for including that in the charter.


On 8/26/13 10:07 AM, "Ralph Droms (rdroms)" <> wrote:

>I'm revising the draft dnssdext charter according to the discussion
>during the BoF in Berlin.  One issue that occurs to me that we didn't
>explicitly discuss during the BoF is the list of the deployment scenarios
>to be considered by the WG.  The draft charter includes a list of four
>   a) Commercial enterprise networks
>   b) Academic/educational/university campus networks
>   c) Multi-link home networks, such as those envisaged by the
>      HOMENET WG 
>   d) Multi-link/single subnet (mesh) networks, such as those
>      described by the ZigBee Alliance Z-IP specification
>while draft-lynn-mdnsext-requirements includes a list of six scenarios:
>   (A) Personal Area networks, e.g., one laptop and one printer.
>   This is the simplest example of an mDNS network.
>   (B) Home networks, consisting of:
>   * Single exit router: the network may have multiple upstream
>     providers or networks, but all outgoing and incoming trafic goes
>     through a single router.
>   * One level depth: all links on the network are connected to the
>     same default router.
>   * Single administrative domain: all nodes under the same admin
>     entity.
>   (C) Like B but may have a tree of links behind the single exit
>   router.  However, the forwarding nodes are almost self-configured
>   and do not require routing protocol administrators.
>   (D) Enterprise networks, consisting of:
>   * Any depth of the forwarding tree, under a single administrative
>     domain.  The large majority of the forwarding and security
>     devices are configured.
>   (E) Higher Education networks, consisting of:
>   * Any depth of the forwarding tree, core network under a central
>     administrative domain but leaf networks under multiple
>     administrative entities.  The large majority of the forwarding
>     and security devices are configured.
>   (F) Mesh networks such as RPL/6LoWPAN, multi-link but single prefix
>   networks.
>The list of scenarios from draft-lynn-mdnsext-requirements was the basis
>for discussion of requirements during the BoF.
>We likely need to coordinate the list of requirements in the charter with
>the list in the draft-lynn-mdnsext-requirements.  The two lists are
>actually not that far apart; the requirements docs includes (A) which is
>not in the draft charter, and (B) and (C) could perhaps be combined into
>one scenario, matching c) from the charter.
>I'm looking for consensus about how to proceed:
>* Modify the charter to align with draft-lynn-mdnsext-requirements
>* Modify draft-lynn-mdnsext-requirements to align with the charter
>* Replace the specific list of scenarios from the charter with a pointer
>to the requirements document
>* Modify both draft-lynn-mdnsext-requirements and the charter to bring
>them into alignment
>Note that I'm deferring consideration of specific edits to the scenarios,
>such as s/tree of links/arbitrary topology/ in (C) from
>- Ralph
>mdnsext mailing list