Return-Path: <soohongp@gmail.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 6262221F96FD for <mdnsext@ietfa.amsl.com>; Fri, 31 May 2013 02:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.149
X-Spam-Level: 
X-Spam-Status: No, score=-0.149 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45,  NO_RELAYS=-0.001]
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 illAr8piB4vi for <mdnsext@ietfa.amsl.com>; Fri, 31 May 2013 02:18:50 -0700 (PDT)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id B19E821F96F7 for <mdnsext@ietf.org>; Fri, 31 May 2013 02:18:45 -0700 (PDT)
Received: by mail-ie0-f180.google.com with SMTP id b11so3307170iee.39 for <mdnsext@ietf.org>; Fri, 31 May 2013 02:18:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iKkCl0Ry1bINHBYw6yEysFCoHQDRgw/lzzEWayCCk98=; b=TDa0m1TkDDAB36hWQcd0/O44jPFssRCpJiVoDy6B7OztUaUSM/lUKM+uuQ2wCw1rRL slhtlnnRJI12RZKekYnPpKMsts5ghUBri98LszIXeriNR5RZdro2SbIobnBgk/6FBNyS AtsfvISP8OaE1OBicRhYslskXcWIuV1nOwLh8n+vvSCCiTk1H8h8aSs+0oslRYNp1o7p lHQjUSCIoZJ7hev8h6n5Zf3UA/wGzK3r3ksNgVlorp0VJIMmGXg4tN9AI5zt9lb1nYT2 iESGe0cTqDt/oAEOVl301vXcwNRiMFGbKqf1S4A9j52ySytpq/TXWuDJb+cMcLsNzQWB dL5A==
MIME-Version: 1.0
X-Received: by 10.50.115.34 with SMTP id jl2mr1336938igb.24.1369991925301; Fri, 31 May 2013 02:18:45 -0700 (PDT)
Received: by 10.50.60.67 with HTTP; Fri, 31 May 2013 02:18:45 -0700 (PDT)
Received: by 10.50.60.67 with HTTP; Fri, 31 May 2013 02:18:45 -0700 (PDT)
In-Reply-To: <783F7CF8-7FDB-4F93-82C2-4291E329F844@gmail.com>
References: <14CE323C-0BCC-4B7F-976C-10070E156046@gmail.com> <783F7CF8-7FDB-4F93-82C2-4291E329F844@gmail.com>
Date: Fri, 31 May 2013 18:18:45 +0900
Message-ID: <CAHSr+v1cCQkMkJn1DsH4_2yHYAm-nZCmw=eP5-c6p-dx5e2MAg@mail.gmail.com>
From: Daniel Park <soohongp@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=089e011842a80d8aa604de001aa1
Cc: "mdnsext@ietf.org" <mdnsext@ietf.org>
Subject: Re: [mdnsext] Discussion of BoF during Berlin IETF
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: Fri, 31 May 2013 09:18:51 -0000

--089e011842a80d8aa604de001aa1
Content-Type: text/plain; charset=EUC-KR
Content-Transfer-Encoding: quoted-printable

Just curious why mDNS was originally developed for a single link? Any
special reasons from the beginning?

Soohong Daniel Park
2013. 5. 31. =BF=C0=C8=C4 12:26=BF=A1 "Ralph Droms" <rdroms.ietf@gmail.com>=
=B4=D4=C0=CC =C0=DB=BC=BA:

> REMINDER!!!!
>
> I'm looking for review and discussion of the BoF proposal and draft
> charter here:
> http://www.ietf.org/mail-archive/web/mdnsext/current/msg00149.html
>
> The mailing list has been quiet (0 responses so far).  Is there still
> interest in taking on this work?
>
> - Ralph
>
> _______________________________________________
> mdnsext mailing list
> mdnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/mdnsext
>

--089e011842a80d8aa604de001aa1
Content-Type: text/html; charset=EUC-KR
Content-Transfer-Encoding: quoted-printable

<p>Just curious why mDNS was originally developed for a single link? Any sp=
ecial reasons from the beginning?</p>
<p>Soohong Daniel Park</p>
<div class=3D"gmail_quote">2013. 5. 31. =BF=C0=C8=C4 12:26=BF=A1 &quot;Ralp=
h Droms&quot; &lt;<a href=3D"mailto:rdroms.ietf@gmail.com">rdroms.ietf@gmai=
l.com</a>&gt;=B4=D4=C0=CC =C0=DB=BC=BA:<br type=3D"attribution"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">
REMINDER!!!!<br>
<br>
I&#39;m looking for review and discussion of the BoF proposal and draft cha=
rter here: <a href=3D"http://www.ietf.org/mail-archive/web/mdnsext/current/=
msg00149.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/mdnse=
xt/current/msg00149.html</a><br>

<br>
The mailing list has been quiet (0 responses so far). &nbsp;Is there still =
interest in taking on this work?<br>
<br>
- Ralph<br>
<br>
_______________________________________________<br>
mdnsext mailing list<br>
<a href=3D"mailto:mdnsext@ietf.org">mdnsext@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mdnsext" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/mdnsext</a><br>
</blockquote></div>

--089e011842a80d8aa604de001aa1--

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 8D89C21F96ED for <mdnsext@ietfa.amsl.com>; Thu, 30 May 2013 23:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.243
X-Spam-Level: *
X-Spam-Status: No, score=1.243 tagged_above=-999 required=5 tests=[AWL=1.747,  BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
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 OkevKa-g93RE for <mdnsext@ietfa.amsl.com>; Thu, 30 May 2013 23:24:33 -0700 (PDT)
Received: from smtp-vbr14.xs4all.nl (smtp-vbr14.xs4all.nl [194.109.24.34]) by ietfa.amsl.com (Postfix) with ESMTP id 7002621F9678 for <mdnsext@ietf.org>; Thu, 30 May 2013 23:24:30 -0700 (PDT)
Received: from roundcube.xs4all.nl (roundcube11.xs4all.net [194.109.20.209]) by smtp-vbr14.xs4all.nl (8.13.8/8.13.8) with ESMTP id r4V6OTst033388 for <mdnsext@ietf.org>; Fri, 31 May 2013 08:24:29 +0200 (CEST) (envelope-from stokcons@xs4all.nl)
Received: from a82-95-140-48.adsl.xs4all.nl ([82.95.140.48]) by roundcube.xs4all.nl with HTTP (HTTP/1.1 POST); Fri, 31 May 2013 08:24:28 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 31 May 2013 08:24:28 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: <mdnsext@ietf.org>
Organization: vanderstok consultancy
Mail-Reply-To: <consultancy@vanderstok.org>
In-Reply-To: <783F7CF8-7FDB-4F93-82C2-4291E329F844@gmail.com>
References: <14CE323C-0BCC-4B7F-976C-10070E156046@gmail.com> <783F7CF8-7FDB-4F93-82C2-4291E329F844@gmail.com>
Message-ID: <5c24b7358f8e4adb71187a17df9fc6bb@xs4all.nl>
X-Sender: stokcons@xs4all.nl (lRh8LcV/ZgNS9PSE+x5/m13w064dxh+R)
User-Agent: XS4ALL Webmail
X-Virus-Scanned: by XS4ALL Virus Scanner
Subject: Re: [mdnsext] Discussion of BoF during Berlin IETF
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: Fri, 31 May 2013 06:24:42 -0000

Ralph,

I am certainly interested in this work and agree with the charter, 
which has improved with respect to the former version.
 From the point of view of building control, it is essential to do 
disovery on a multilink stand-alone network, and not needing to change 
the applications when the network is connected to a backbone with access 
to DNS. From the outside the resources on the now connected network 
should be visible with the same names, possibly suffixed with additional 
domain name information.

In the past I have commented on the requirements and I am looking 
forward to a new version.

Peter van der Stok.

Ralph Droms schreef op 2013-05-31 05:24:
> REMINDER!!!!
> 
> I'm looking for review and discussion of the BoF proposal and draft
> charter here:
> http://www.ietf.org/mail-archive/web/mdnsext/current/msg00149.html
> 
> The mailing list has been quiet (0 responses so far).  Is there still
> interest in taking on this work?
> 
> - Ralph
> 
> _______________________________________________
> mdnsext mailing list
> mdnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/mdnsext


Return-Path: <rdroms.ietf@gmail.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 D16EE21F9814 for <mdnsext@ietfa.amsl.com>; Thu, 30 May 2013 20:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 6vgjYIVcMSy9 for <mdnsext@ietfa.amsl.com>; Thu, 30 May 2013 20:26:05 -0700 (PDT)
Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) by ietfa.amsl.com (Postfix) with ESMTP id 9247E21F919D for <mdnsext@ietf.org>; Thu, 30 May 2013 20:26:02 -0700 (PDT)
Received: by mail-vc0-f181.google.com with SMTP id lf11so705514vcb.40 for <mdnsext@ietf.org>; Thu, 30 May 2013 20:26:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=yhv2+TOv5Dl3Wu77jKn/T0qmHdH10YYMWp1IrKrG2kM=; b=ijkQEiAs5Ztgiuoa4Ggv9DeeDaP54h9EWMJ0NcMnbjEaM7AviVkgIen+mdUTY9qPcM Xv/FvqfKUUuWrzs9tAsBsPGCJitxehYgXvrEFEslZ97Ip8Nht5cblLGTnAit2vhYfsCj /T4gMg9wwbbmkfwZnipUSMaYSK8PNVKG73nQ1uUtgYabCiy6xxZFjV0qD6oIVNZ56hD8 +e+vpi/WTT4lO3biXjRr21xNUadsGVMtsyKa888d7dT4ylq9QwzvDInw03EVyuq0M7mQ Tdl2wtVjwJhmBgjhMTP/udfHiIg/Wag2bb0mv/+zBWtfFRp+GWms6A9QsVWP7eT7KVWi 40ig==
X-Received: by 10.52.117.16 with SMTP id ka16mr6868977vdb.43.1369970762106; Thu, 30 May 2013 20:26:02 -0700 (PDT)
Received: from ?IPv6:2001:420:2481:20:5101:c012:3ce4:58bb? ([2001:420:2481:20:5101:c012:3ce4:58bb]) by mx.google.com with ESMTPSA id ww6sm16845587vec.5.2013.05.30.20.26.00 for <mdnsext@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 20:26:01 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <14CE323C-0BCC-4B7F-976C-10070E156046@gmail.com>
Date: Thu, 30 May 2013 23:24:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <783F7CF8-7FDB-4F93-82C2-4291E329F844@gmail.com>
References: <14CE323C-0BCC-4B7F-976C-10070E156046@gmail.com>
To: "mdnsext@ietf.org" <mdnsext@ietf.org>
X-Mailer: Apple Mail (2.1503)
Subject: Re: [mdnsext] Discussion of BoF during Berlin IETF
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: Fri, 31 May 2013 03:26:09 -0000

REMINDER!!!!

I'm looking for review and discussion of the BoF proposal and draft =
charter here: =
http://www.ietf.org/mail-archive/web/mdnsext/current/msg00149.html

The mailing list has been quiet (0 responses so far).  Is there still =
interest in taking on this work?

- Ralph



Return-Path: <rklauck@informatik.tu-cottbus.de>
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 39E4C21F8EE8 for <mdnsext@ietfa.amsl.com>; Thu, 23 May 2013 06:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 m-qf+CkhvIw8 for <mdnsext@ietfa.amsl.com>; Thu, 23 May 2013 06:46:25 -0700 (PDT)
Received: from crow.informatik.tu-cottbus.de (crow.informatik.tu-cottbus.de [141.43.3.8]) by ietfa.amsl.com (Postfix) with ESMTP id 261C621F8A6B for <mdnsext@ietf.org>; Thu, 23 May 2013 06:46:24 -0700 (PDT)
Received: from borkum.informatik.tu-cottbus.de (borkum.informatik.tu-cottbus.de [141.43.202.208]) (authenticated bits=0) by crow.informatik.tu-cottbus.de (8.13.8/8.13.8) with ESMTP id r4NDkMPW025796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <mdnsext@ietf.org>; Thu, 23 May 2013 15:46:22 +0200
Date: Thu, 23 May 2013 15:46:21 +0200
From: Ronny Klauck <rklauck@informatik.tu-cottbus.de>
To: "mdnsext@ietf.org" <mdnsext@ietf.org>
Message-ID: <20130523154621.02cad357@borkum.informatik.tu-cottbus.de>
X-Mailer: Claws Mail 3.3.1 (GTK+ 2.10.4; x86_64-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: [mdnsext] Enhanced DNS Message Compression - Optimizing mDNS/DNS-SD for the Use in 6LoWPANs
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: Thu, 23 May 2013 13:46:30 -0000

With the integration of smart objects into the
Internet with the help of tiny IP stacks, a direct connection
between these objects and ordinary computational devices can be
realized at the IP layer. As IP alone cannot ensure an automatic
integration at the higher layers, an homogeneous access via
services (e.g., discovery, self-configuration) for the Internet of
Things vision should be provided for all connected device types.
Multicast DNS and DNS Service Discovery are established
and widely used standards in current IP-based networks to
enable the discovery of devices and services at the application
layer with DNS messages. To comply with the current Internet
infrastructure, the lightweight implementation uBonjour makes
mDNS and DNS-SD available on smart objects. As DNS does not
meet the requirements of low data rate smart object networks,
we propose to extend DNS with enhanced message compression
mechanisms to effectively reduce the number of exchanged IP
packets in 6LoWPANs while ensuring backward compatibility.

Keywords-Internet of Things, mDNS/DNS-SD, Contiki

The article can be downloaded from here:
https://www-rnks.informatik.tu-cottbus.de/content/unrestricted/staff/mk/Publications/PerCom_2013-PerSeNS-Klauck_Kirsche.pdf


Best regards,
-- 
Dipl.-Inf. Ronny Klauck
Brandenburg University of Technology Cottbus
Computer Networks Group
http://www-rnks.informatik.tu-cottbus.de/~rklauck


Return-Path: <rdroms.ietf@gmail.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 0993A21F96E9 for <mdnsext@ietfa.amsl.com>; Wed, 22 May 2013 10:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
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 HSBpq5mCOjsR for <mdnsext@ietfa.amsl.com>; Wed, 22 May 2013 10:58:43 -0700 (PDT)
Received: from mail-gg0-x236.google.com (mail-gg0-x236.google.com [IPv6:2607:f8b0:4002:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB9721F96DD for <mdnsext@ietf.org>; Wed, 22 May 2013 10:58:43 -0700 (PDT)
Received: by mail-gg0-f182.google.com with SMTP id q2so794371ggc.27 for <mdnsext@ietf.org>; Wed, 22 May 2013 10:58:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version:x-mailer; bh=U8l3BQ8tjlZJKKogWIhYsGqDbh879WORmwjxOgaRBv4=; b=swQ3nrcPJiRR+u1edIqEhtc0n13aN53/f12ODF9Kk2HBFMPHniuRq9jDszaViJ//FY 8qO99/WrO3UlY6Og6X2+Aqn/vRfe4O7hw5iR+dk9x9xBjl5CqO7a50LyPQNhs29co3CA pXDRSXFuDLd+sfoQuyXTiOhbuO1iyHy383zz7243pv5+8NRU3F8RLac5iB9rUvmqRyFV Tc9nMqWSqDPV81NtBBlRO7BSS6f7Ohg9XeqWHvI0XAnqMIH8tgEJv10+grqxaqjGsQzQ wrdMiuSNxPXBLsU44dZmO/jxYFBjs1iDsOv8kgCqHCMzMZ1J7+neUDR4OhUtoEO5c0Vh lCkw==
X-Received: by 10.236.145.136 with SMTP id p8mr6347893yhj.74.1369245522683; Wed, 22 May 2013 10:58:42 -0700 (PDT)
Received: from [10.86.245.46] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id u69sm12363061yhf.23.2013.05.22.10.58.40 for <mdnsext@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 May 2013 10:58:41 -0700 (PDT)
From: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <14CE323C-0BCC-4B7F-976C-10070E156046@gmail.com>
Date: Wed, 22 May 2013 20:58:38 +0300
To: "mdnsext@ietf.org" <mdnsext@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Subject: [mdnsext] Discussion of BoF during Berlin IETF
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, 22 May 2013 17:58:44 -0000

After a pretty good discussion of requirements and related =
considerations, traffic on the mailing list has been pretty quiet.  =
Looking ahead to a request for a BoF in Berlin, I've updated the draft =
request and charter (only a little) and included them below.

What we need now is careful review and discussion of the text below, and =
explicit expressions of interest in the topic and support for the =
specific direction laid out in the BoF request and charter.

Perhaps the most obvious change I suggest is to change the name from =
mdnsext to sadnssd (scalable, autonomous DNS-SD).  This change follows =
the direction of the earlier mailing list discussion away from =
extensions to mDNS to higher level consideration of scalable DNS-SD.

- Ralph

BoF scheduling information:

a. Scalable, Autonomous DNS-Based Service Discovery (sadnssd)

b. Internet Area

c. Conflicts: 6man homenet dhc apparea appsawg intarea sdnrg v6ops dnsop =
and dnsext

d. Expected Attendance: 200 (at least 164 attended at IETF85)

e. Special requests: None

f. Number of sessions: 1

g. Length of session: 2 hours=20


Draft agenda:
--------------------

1. Administravia (Chairs, 5 mins)  =20
    Note Well and agenda bashing

2. Goals of the BoF (Chairs, 15 mins)
    Review of IETF 85 mdsnext BoF and progress since then

3. Requirements (Kerry Lynn, 30 mins)
    draft-lynn-sadnssd-requirements-01

4. Open discussion (Chairs, 40 mins)
    Open mic; includes draft charter and deliverables
 =20
5. Key questions (Chairs, 30 mins)
    Are we ready to form a WG with the agreed charter, subject to mail
      list confirmation? =20
    Note RFC5434 section 1.


Draft charter:
-------------------

Currently, zeroconf networking protocols are generally used to
discover services within the scope of a single link. In particular,
the Bonjour protocols suite, comprising mDNS (RFC 6762) and DNS-SD
(RFC 6763), are widely used for discovery and resolution of services
and names on a single link.

The Bonjour protocol suite is commonly used in many scenarios,
including home networks, commercial and campus enterprise networks,
and may be of use in certain mesh networks.  However, the multicast
Bonjour protocols are constrained to link-local scope, so can only be
used to discover services on the same link. In a typical current home
network, which is a single link, users should experience the desired
discovery behavior. However, in future multi-link home networks (as
envisaged by the homenet WG) and in routed campus or enterprise
networks, devices and thus users can only discover services on the
same link, which is a significant limitation. Such limitations have
led to calls, such as those by the Educause petition, to develop an
appropriate solution to span multiple links, or to perform discovery
across a wide area (not necessarily on directly connected links).

In addition, the ZigBee Alliance Smart Energy Profile 2.0 commercial
standard currently under development has specified the Bonjour
protocols as its method of zero configuration discovery. However, its
use of wireless mesh multi-link subnets and its use across traditional
routed networks will require extensions to the Bonjour protocols to
allow operation across multiple links.

As demand for service discovery across wider area routed networks
grows, some vendors are beginning to ship their own early
solutions. It is thus both timely and important that efforts to
develop improved, scalable, autonomous service discovery solutions for
routed networks are coordinated towards producing a single, standards-
based solution.

Goals

To that end, the primary goals of the sadnssd WG are as follows:

1. To document a set of requirements for scalable, autonomous
   DNS-based service discovery in routed, multi-link networks in the
   following 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=20
    d) Multi-link/single subnet (mesh) networks, such as those
       described by the ZigBee Alliance Z-IP specification

2. To develop an improved, scalable solution for wide-area service
   discovery that can operate in multi-link networks, applicable to
   the scenarios above.

3. To develop a BCP for the coexistence of zeroconf (mDNS) and unicast
   (global DNS) name services in such multi-link networks, which
   should include consideration of both the name resolution mechanism
   and the namespace.

It is important that the sadnssd WG takes input from stakeholders in
the scenarios it is considering. For example, the homenet WG is
currently evaluating its own requirements for naming and service
discovery; it is up to the homenet WG as to whether it wishes to
recommend adoption of the solution developed in the mdsnext WG, and
thus coordination between the WGs is desirable.

Deliverables

The WG will produce three documents: an Informational RFC on the
requirements for wide-area service discovery protocols; a Standards
Track RFC documenting a wide-area service discovery solution that is
applicable to those scenarios; and a BCP document describing the most
effective method to integrate mDNS and global DNS name services.

Milestones

Sep 2013 Formation of the WG
Oct 2013 Adopt requirements draft as WG document
Nov 2013 Submit requirements draft to the IESG as an Informational RFC
Mar 2014 Adopt wide-area service discovery solution draft as WG
         document=20
Mar 2014 Adopt zeroconf and unicast DNS integration BCP draft as WG
         document=20
Sep 2014 Submit wide-area service discovery solution draft to the IESG
         as Standards Track RFC=20
Sep 2014 Submit zeroconf and unicast DNS integration solution draft to
         the IESG as BCP=20



Return-Path: <farmer@umn.edu>
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 ECF3F21F89BA for <mdnsext@ietfa.amsl.com>; Thu,  2 May 2013 12:19:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_75=0.6, RCVD_IN_DNSWL_MED=-4]
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 pT6subHGHUHn for <mdnsext@ietfa.amsl.com>; Thu,  2 May 2013 12:19:45 -0700 (PDT)
Received: from vs-w.tc.umn.edu (vs-w.tc.umn.edu [134.84.135.88]) by ietfa.amsl.com (Postfix) with ESMTP id C18A921F89AF for <mdnsext@ietf.org>; Thu,  2 May 2013 12:19:38 -0700 (PDT)
Received: from mail-ob0-f200.google.com (mail-ob0-f200.google.com [209.85.214.200]) by vs-w.tc.umn.edu (UMN smtpd) with ESMTP for <mdnsext@ietf.org>; Thu, 2 May 2013 14:19:28 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ob0-f200.google.com [209.85.214.200] #+LO+TR
X-Umn-Classification: local
Received: by mail-ob0-f200.google.com with SMTP id v19so4741185obq.7 for <mdnsext@ietf.org>; Thu, 02 May 2013 12:19:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding:x-gm-message-state; bh=zWPuJljlbMxJzRQfH45irOv4aq9Euku8ZyR1jnGhM3Y=; b=AVL3ui/QWvls1CMjT7RiNN5FtTwPLAUqAiFQN/SRDn/seUst7G/UW/+3jfIwq4mrR+ bXADCc3CZo/z9MLDmhXlhrOWjOVoKehL1TXsercSKnphNi5q7Mc+7s0q/cwaB8m4EP0N 8CPet53rt/hhcW/og98v8czc5PVv8QJemi8soJxK25EBTNAqmDS6d/GXINS5ENIwnyTB QvjgplAzV7ncxPq1JXqCfJf5mj5dSEY6kT7txPyf5AZZ3DH0qUYqB+OV8BU8WY19oi7K YyHbWLmB4krAn66LYoZIoWzR/9iH65Yf7KAxeyAzFbCrAmMygRykQsJv8hk4dZv17ipp QYPA==
X-Received: by 10.50.49.7 with SMTP id q7mr4332548ign.6.1367522367113; Thu, 02 May 2013 12:19:27 -0700 (PDT)
X-Received: by 10.50.49.7 with SMTP id q7mr4332544ign.6.1367522367043; Thu, 02 May 2013 12:19:27 -0700 (PDT)
Received: from x-134-84-88-100.nts.umn.edu ([2607:ea00:101:2001:c142:525f:2855:8f5b]) by mx.google.com with ESMTPSA id wn10sm32843161igb.2.2013.05.02.12.19.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 May 2013 12:19:26 -0700 (PDT)
Message-ID: <5182BC3D.3010902@umn.edu>
Date: Thu, 02 May 2013 14:19:25 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Alf Watt <alf.watt@ruckuswireless.com>
References: <CDA6C351.7B03%alf.watt@ruckuswireless.com>
In-Reply-To: <CDA6C351.7B03%alf.watt@ruckuswireless.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQm67d8U9JxFSWdS3CgFZtGSzaa/mqTR17Vx8Ntg+viWJxs2BtenU9j4hpFlHp45tArvYt3t4RZ7dd2NNzq+Xeg+UEyhJpX3bjSK9fPu2s927igfn8CmTZaxABjN/1C3eeYHkb5E
Cc: "mdnsext@ietf.org" <mdnsext@ietf.org>, David Farmer <farmer@umn.edu>
Subject: Re: [mdnsext] .local vs msftdomain.local
X-BeenThere: mdnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
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: Thu, 02 May 2013 19:19:50 -0000

At least for Active Directory best practices Microsoft gives 
contradictory advice on the issue.  See;

http://technet.microsoft.com/en-us/library/bb727085.aspx

The problem is this leaves users having to decide which advice to 
believe.  I have no idea how to get Microsoft to clarify the issue.

-----

1. Identify your organization's DNS owner and determine what registered 
DNS names you have available on the network that will host Active Directory.

Keep in mind that the names available on this network may be distinct 
from the names that your company exposes on the Internet. For example, 
the name your organization uses on the Internet might be 
contosopharma.com and the name used on your internal corporate network 
might be contoso.com. In this case the name that you select is contoso.com
If you do not have a registered domain name, you should register a name 
with an Internet DNS registration authority.
Note: As a best practice use DNS names registered with an Internet 
authority in the Active Directory namespace. Only registered names are 
guaranteed to be globally unique. If another organization later 
registers the same DNS domain name, or if your organization merges with, 
acquires, or is acquired by other company that uses the same DNS names 
then the two infrastructures can never interact with one another.
Add a prefix that is not currently in use to the registered DNS name to 
create a new subordinate name. For example, if your DNS root name were 
contoso.com then you should create an Active Directory forest root 
domain name such as concorp.contoso.com, where the namespace 
concorp.contoso.com is not already in use on the network. This new 
branch of the namespace will be dedicated to Active Directory and 
Windows 2000 and can easily be integrated with the existing DNS 
implementation. The rules for selecting a prefix are listed in Table 9.



On 5/1/13 15:14 , Alf Watt wrote:
> Much to my personal and professional embarrassment our internal IT
> department here uses 'machine.ourdomain.local' as a private unicast domain
> name as recommended some time ago by microsoft[1]. In particular KB 296250
> [2] makes the following suggestions regarding private domain names:
>
> "Make the name a private domain name that is used for name resolution on
> the internal Small Business Server network. This name is usually
> configured with the first-level domain of .local. At the present time, the
> .local domain name is not registered on the Internet."
>
> "The natural separation of internal and external networks occurs because
> of the use of a separate internal namespace. A client query generated from
> the Internet for www.contoso.local does not return any valid domain
> information because .local, at the present time, is not a registered
> domain name."
>
> "Name resolution problems that are created by using a publicly registered
> domain name can be avoided by planning the private namespace around a
> .local first-level domain so that, in this example, Contoso.com and
> Contoso.local are both available to internal clients, but Contoso.com is
> only available to external internet clients. "
>
> Any suggestions from the group on how to combat this misconfiguration?
> Particularly, how do we get MSFT to renounce their previous tech-notes and
> update their suggested practices around this?
>
> Thanks,
> Alf
>
> [1] http://en.wikipedia.org/wiki/.local#Microsoft_recommendations
> [2] http://support.microsoft.com/kb/296250
>
>
> _______________________________________________
> mdnsext mailing list
> mdnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/mdnsext
>


-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================


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 51A1721F9B20 for <mdnsext@ietfa.amsl.com>; Wed,  1 May 2013 13:14:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_75=0.6, 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 hfjKDHYNpC+v for <mdnsext@ietfa.amsl.com>; Wed,  1 May 2013 13:14:48 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe001.messaging.microsoft.com [216.32.180.184]) by ietfa.amsl.com (Postfix) with ESMTP id 507EF21F9AF2 for <mdnsext@ietf.org>; Wed,  1 May 2013 13:14:48 -0700 (PDT)
Received: from mail190-co1-R.bigfish.com (10.243.78.233) by CO1EHSOBE021.bigfish.com (10.243.66.84) with Microsoft SMTP Server id 14.1.225.23; Wed, 1 May 2013 20:14:47 +0000
Received: from mail190-co1 (localhost [127.0.0.1])	by mail190-co1-R.bigfish.com (Postfix) with ESMTP id 5F97F8C0470	for <mdnsext@ietf.org>; Wed,  1 May 2013 20:14:47 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.85; KIP:(null); UIP:(null); IPV:NLI; H:CH1PRD0811HT003.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -6
X-BigFish: PS-6(zz4015Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz17326ah186M18602eh8275bh8275dhz2fh2a8h668h839h944he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d0ch1d2eh1d3fh1155h)
Received-SPF: pass (mail190-co1: domain of ruckuswireless.com designates 157.56.245.85 as permitted sender) client-ip=157.56.245.85; envelope-from=alf.watt@ruckuswireless.com; helo=CH1PRD0811HT003.namprd08.prod.outlook.com ; .outlook.com ; 
Received: from mail190-co1 (localhost.localdomain [127.0.0.1]) by mail190-co1 (MessageSwitch) id 1367439284588711_5073; Wed,  1 May 2013 20:14:44 +0000 (UTC)
Received: from CO1EHSMHS009.bigfish.com (unknown [10.243.78.235])	by mail190-co1.bigfish.com (Postfix) with ESMTP id 8DD12B2004A	for <mdnsext@ietf.org>; Wed,  1 May 2013 20:14:44 +0000 (UTC)
Received: from CH1PRD0811HT003.namprd08.prod.outlook.com (157.56.245.85) by CO1EHSMHS009.bigfish.com (10.243.66.19) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 1 May 2013 20:14:43 +0000
Received: from CH1PRD0811MB407.namprd08.prod.outlook.com ([169.254.8.251]) by CH1PRD0811HT003.namprd08.prod.outlook.com ([10.255.155.38]) with mapi id 14.16.0305.001; Wed, 1 May 2013 20:14:37 +0000
From: Alf Watt <alf.watt@ruckuswireless.com>
To: "mdnsext@ietf.org" <mdnsext@ietf.org>
Thread-Topic: .local vs msftdomain.local
Thread-Index: AQHORqiAVWQFQ4x12Ua5ze3J73JxTw==
Date: Wed, 1 May 2013 20:14:37 +0000
Message-ID: <CDA6C351.7B03%alf.watt@ruckuswireless.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [10.255.91.132]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1EC5635B1A11B84AA134C643E63363F2@namprd08.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ruckuswireless.com
Subject: [mdnsext] .local vs msftdomain.local
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, 01 May 2013 20:14:53 -0000

Much to my personal and professional embarrassment our internal IT
department here uses 'machine.ourdomain.local' as a private unicast domain
name as recommended some time ago by microsoft[1]. In particular KB 296250
[2] makes the following suggestions regarding private domain names:

"Make the name a private domain name that is used for name resolution on
the internal Small Business Server network. This name is usually
configured with the first-level domain of .local. At the present time, the
.local domain name is not registered on the Internet."

"The natural separation of internal and external networks occurs because
of the use of a separate internal namespace. A client query generated from
the Internet for www.contoso.local does not return any valid domain
information because .local, at the present time, is not a registered
domain name."

"Name resolution problems that are created by using a publicly registered
domain name can be avoided by planning the private namespace around a
.local first-level domain so that, in this example, Contoso.com and
Contoso.local are both available to internal clients, but Contoso.com is
only available to external internet clients. "

Any suggestions from the group on how to combat this misconfiguration?
Particularly, how do we get MSFT to renounce their previous tech-notes and
update their suggested practices around this?

Thanks,
Alf

[1] http://en.wikipedia.org/wiki/.local#Microsoft_recommendations
[2] http://support.microsoft.com/kb/296250