IETF Logo Mail Archive

Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices

Ted Lemon <Ted.Lemon@nominum.com> Fri, 21 November 2014 13:38 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E0DD1A0371 for <dnssd@ietfa.amsl.com>; Fri, 21 Nov 2014 05:38:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.494
X-Spam-Level:
X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.594] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id okmjzLAyxJGR for <dnssd@ietfa.amsl.com>; Fri, 21 Nov 2014 05:38:50 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEFF01A037D for <dnssd@ietf.org>; Fri, 21 Nov 2014 05:37:16 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 10D1ADA02E8 for <dnssd@ietf.org>; Fri, 21 Nov 2014 13:37:45 +0000 (UTC)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 88E1953E07B; Fri, 21 Nov 2014 05:36:46 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 21 Nov 2014 05:36:46 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAPK2DewfxsfEh1fJCfGbWjeU92Bu8VH1W7Os+wwyJ0U+86gxdQ@mail.gmail.com>
Date: Fri, 21 Nov 2014 08:36:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <71A17712-B6C3-436D-840F-D32F654F04C9@nominum.com>
References: <CAPK2DeyuABqSbH5dtdtScYWnE-vkmGO642xFb6FZehu-5MTaAA@mail.gmail.com> <436692B4-978D-4E62-868E-78FA8AF3F26F@nominum.com> <CAPK2Deys6VU83R0hfv_8svNKuaSBEfu_dGqnGkoN_pQ9zE_6HQ@mail.gmail.com> <F61ADDF8-6BC1-4C9E-B80A-32F3EF186E3D@istumbler.net> <CAPK2DeyCToF6MwQOpnbW=tY+uU_iEsgOS0WSe1NYpxGq6kC+3Q@mail.gmail.com> <F158B437-8DAB-469E-B957-745CDBB3AB41@istumbler.net> <CAPK2DexC=YH_pjMnHw2ubsKe-4LqWm+BM10JwR_AxRm2k9Tudg@mail.gmail.com> <12750388-E313-4364-8D42-9DF75C91D91C@istumbler.net> <CAPK2DewfxsfEh1fJCfGbWjeU92Bu8VH1W7Os+wwyJ0U+86gxdQ@mail.gmail.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/lFNFHmmWZq9FV_97VbqpFMjVgik
Cc: Brian Haberman <brian@innovationslab.net>, Myung-Ki Shin <mkshin@etri.re.kr>, "dnssd@ietf.org" <dnssd@ietf.org>, Jung-Soo Park <pjs@etri.re.kr>, Sejun Lee <prosejun14@gmail.com>
Subject: Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Nov 2014 13:38:51 -0000

I think we still haven't heard a clear explanation for why this new protocol work is needed.   That would be the key discussion to have.   Discussions about what the protocol work would entail, or how it would integrate with other work, are premature until that discussion has reached a conclusion.

v2.23.0 | Report a Bug | By Email