Re: [mdnsext] dnssdext charter

Alf Watt <alf.watt@ruckuswireless.com> Wed, 28 August 2013 01:12 UTC

Return-Path: <alf.watt@ruckuswireless.com>
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 05D1121E80FE for <mdnsext@ietfa.amsl.com>; Tue, 27 Aug 2013 18:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66K9ZTZX9Pim for <mdnsext@ietfa.amsl.com>; Tue, 27 Aug 2013 18:12:02 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe003.messaging.microsoft.com [213.199.154.206]) by ietfa.amsl.com (Postfix) with ESMTP id 6C13721E80FD for <mdnsext@ietf.org>; Tue, 27 Aug 2013 18:12:01 -0700 (PDT)
Received: from mail72-am1-R.bigfish.com (10.3.201.250) by AM1EHSOBE001.bigfish.com (10.3.204.21) with Microsoft SMTP Server id 14.1.225.22; Wed, 28 Aug 2013 01:12:00 +0000
Received: from mail72-am1 (localhost [127.0.0.1]) by mail72-am1-R.bigfish.com (Postfix) with ESMTP id 8FF312C0073; Wed, 28 Aug 2013 01:12:00 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.241.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0810HT002.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zzbb2dI98dI9371I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL186068h8275bh8275dh1de097hz2fh2a8h839h944he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1fe8h1ff5h1155h)
Received-SPF: pass (mail72-am1: domain of ruckuswireless.com designates 157.56.241.101 as permitted sender) client-ip=157.56.241.101; envelope-from=alf.watt@ruckuswireless.com; helo=BL2PRD0810HT002.namprd08.prod.outlook.com ; .outlook.com ;
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; H:BLUPR08MB087.namprd08.prod.outlook.com; CLIP:12.217.161.130; RD:InfoNoRecords; A:1; MX:1; LANG:en;
Received: from mail72-am1 (localhost.localdomain [127.0.0.1]) by mail72-am1 (MessageSwitch) id 1377652316869835_23745; Wed, 28 Aug 2013 01:11:56 +0000 (UTC)
Received: from AM1EHSMHS004.bigfish.com (unknown [10.3.201.232]) by mail72-am1.bigfish.com (Postfix) with ESMTP id D067C2E015A; Wed, 28 Aug 2013 01:11:56 +0000 (UTC)
Received: from BL2PRD0810HT002.namprd08.prod.outlook.com (157.56.241.101) by AM1EHSMHS004.bigfish.com (10.3.207.104) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 28 Aug 2013 01:11:56 +0000
Received: from BLUPR08MB085.namprd08.prod.outlook.com (10.242.188.145) by BL2PRD0810HT002.namprd08.prod.outlook.com (10.255.110.37) with Microsoft SMTP Server (TLS) id 14.16.347.3; Wed, 28 Aug 2013 01:11:47 +0000
Received: from BLUPR08MB087.namprd08.prod.outlook.com (10.242.188.149) by BLUPR08MB085.namprd08.prod.outlook.com (10.242.188.145) with Microsoft SMTP Server (TLS) id 15.0.745.25; Wed, 28 Aug 2013 01:11:46 +0000
Received: from BLUPR08MB087.namprd08.prod.outlook.com ([169.254.13.48]) by BLUPR08MB087.namprd08.prod.outlook.com ([169.254.13.48]) with mapi id 15.00.0745.000; Wed, 28 Aug 2013 01:11:46 +0000
From: Alf Watt <alf.watt@ruckuswireless.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>, "mdnsext@ietf.org" <mdnsext@ietf.org>
Thread-Topic: [mdnsext] dnssdext charter
Thread-Index: AQHOon7CNNwOvc1wFkGcFaSQRAQGyJmpXNeA
Date: Wed, 28 Aug 2013 01:11:45 +0000
Message-ID: <CE429B27.16C93%alf.watt@ruckuswireless.com>
In-Reply-To: <4518F39EB578034D8C99A9B7776CDBA301ABFCB8@xmb-aln-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [12.217.161.130]
x-forefront-prvs: 09525C61DB
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A1E247EA4524A845826632C5E04A86DF@namprd08.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ruckuswireless.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [mdnsext] dnssdext charter
X-BeenThere: mdnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: 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.

Best,
Alf

On 8/26/13 10:07 AM, "Ralph Droms (rdroms)" <rdroms@cisco.com> 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
>scenarios:
>
>   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
>draft-lynn-mdnsext-requirements.
>
>- Ralph
>
>_______________________________________________
>mdnsext mailing list
>mdnsext@ietf.org
>https://www.ietf.org/mailman/listinfo/mdnsext
>