Re: [mdnsext] Discussion of BoF during Berlin IETF

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 11 June 2013 20:44 UTC

Return-Path: <mcr@sandelman.ca>
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 14CB821F8904 for <mdnsext@ietfa.amsl.com>; Tue, 11 Jun 2013 13:44:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.558
X-Spam-Level:
X-Spam-Status: No, score=-2.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599]
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 OcZ75BfTMztz for <mdnsext@ietfa.amsl.com>; Tue, 11 Jun 2013 13:44:22 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 7D64F21F8D79 for <mdnsext@ietf.org>; Tue, 11 Jun 2013 13:44:21 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id D861F2017C for <mdnsext@ietf.org>; Tue, 11 Jun 2013 16:57:35 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 663FF63A8C; Tue, 11 Jun 2013 16:43:24 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 57A1B639DF for <mdnsext@ietf.org>; Tue, 11 Jun 2013 16:43:24 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "mdnsext@ietf.org" <mdnsext@ietf.org>
In-Reply-To: <CABOxzu3hkjXgr5p8MLMtgjoy=zpjFP8OwCP=_KybwegDzdKczA@mail.gmail.com>
References: <14CE323C-0BCC-4B7F-976C-10070E156046@gmail.com> <783F7CF8-7FDB-4F93-82C2-4291E329F844@gmail.com> <19956.1370353531@sandelman.ca> <E36F274013087B4EA05E08EB5037503901820D@DEFTHW99EK5MSX.ww902.siemens.net> <22635.1370439768@sandelman.ca> <51B63B07.5070802@umn.edu> <19621.1370909460@sandelman.ca> <CABOxzu3JYjpiVxP8Bv5bw-SHmOzW07KfoagWpyv2MfCYxg2wOw@mail.gmail.com> <51B71517.4080700@umn.edu> <13345.1370971891@sandelman.ca> <CABOxzu3hkjXgr5p8MLMtgjoy=zpjFP8OwCP=_KybwegDzdKczA@mail.gmail.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 11 Jun 2013 16:43:24 -0400
Message-ID: <16227.1370983404@sandelman.ca>
Sender: mcr@sandelman.ca
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: Tue, 11 Jun 2013 20:44:27 -0000

>>>>> "Kerry" == Kerry Lynn <kerlyn@ieee.org> writes:
    >> Kerry, many **enterprises** do *not* have any mDNS traffic, because they
    >> won't let any non-IT person plug ANYTHING in.
    >> 
    Kerry> How does an IT person disable intrinsic mDNS probing/announcing/responding
    Kerry> behavior in a commercial printer?  I guess those same enterprises also ban
    Kerry> OS X
    Kerry> entirely?

Yes, and mDNS would be an excuse for them to continue to do so.
WINS resolution can be turned off by group policy, I'm told.

    Kerry> It seems to me that to carry this conversation forward we need to a) define
    Kerry> sdnssd requirements for Enterprise, which I think we've already hinted we're
    Kerry> not well qualified to do, and b) rank those requirements against those of
    Kerry> homenet and higher ed, which we arguably know much better.

*my* original point was that I was glad that we split off Enterprise as
a separate use case, ask if we really a clue what it might mean, and
point one at least one knob that we may need to include.

I don't think the enterprise IT-clueless people care (or even
understand) about multicast traffic. What they care about is controlling
the namespace(s) that can be seen by internal devices.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [