From nobody Sun Nov 1 19:20:12 2015 Return-Path: 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 57BF91B325C for ; Sun, 1 Nov 2015 19:20:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.511 X-Spam-Level: X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 qjZ_vu3E2wYS for ; Sun, 1 Nov 2015 19:20:10 -0800 (PST) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25BD71B325B for ; Sun, 1 Nov 2015 19:20:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1464; q=dns/txt; s=iport; t=1446434410; x=1447644010; h=from:to:subject:date:message-id:mime-version; bh=fkdAy4B0PEdj2+Uo1YTSn/JMQ6MH5VoVF/wPu0pts9w=; b=g9TYp0jbv1RAp6UI5gapWJuBMrzA6e17V7uz7Xh0wxUl8gRhN1ZvdSc8 5tTIRL442Qv5pRo0gMK7kjIkCitW1yFwSC8/uUUwFN0GmIpKZhfPvHNeJ /Ti/LZUH1aZzeKVnYEexLHJy+g8OEKS8RqNVs0fkfdOTIHoR9F68YjtRu I=; X-Files: signature.asc : 841 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0CtAgBz1TZW/5NdJa1egzuBSL80DoFah0E4FAEBAQEBAQF/C4Q8gQsBgQAnBCGIIqBjoEUBAQEBAQUBAQEBAQEBARIJhneCEIsagRQFlkMBe4FWgWGIcpw5AR8BQ4QEhWmBBwEBAQ X-IronPort-AV: E=Sophos;i="5.20,232,1444694400"; d="asc'?scan'208";a="204009315" Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-7.cisco.com with ESMTP; 02 Nov 2015 03:20:09 +0000 Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id tA23K9YJ031243 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Mon, 2 Nov 2015 03:20:09 GMT Received: from xch-aln-016.cisco.com (173.36.7.26) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Sun, 1 Nov 2015 21:20:08 -0600 Received: from xch-aln-016.cisco.com ([173.36.7.26]) by XCH-ALN-016.cisco.com ([173.36.7.26]) with mapi id 15.00.1104.000; Sun, 1 Nov 2015 21:20:08 -0600 From: "Ralph Droms (rdroms)" To: "dnssd@ietf.org" Thread-Topic: Meeting materials Thread-Index: AQHRFR1gObRj82xppk+OsbmbgFCwhg== Date: Mon, 2 Nov 2015 03:20:08 +0000 Message-ID: <7075D4B0-D3DD-4207-AC9E-11A0A80C8BF8@cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.82.228.61] Content-Type: multipart/signed; boundary="Apple-Mail=_1507D7DE-6B6D-4A51-A330-530F0C5CB6BF"; protocol="application/pgp-signature"; micalg=pgp-sha256 MIME-Version: 1.0 Archived-At: Subject: [dnssd] Meeting materials 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2015 03:20:11 -0000 --Apple-Mail=_1507D7DE-6B6D-4A51-A330-530F0C5CB6BF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii The agenda has been updated and all of the presentation materials have = been posted for this afternoon's meeting. - Ralph --Apple-Mail=_1507D7DE-6B6D-4A51-A330-530F0C5CB6BF Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJWNtZoAAoJEINeeBNmFjV5dmIP/RlUYR8upRiq21xtMf3tLAZN tjdumemBIJ0UYWFdLha2dYGxrave35orm+YTogR4ELDnob3gSjqo+pBx0cPVDiuk TrqF4BQRM+QNDP4/U0ryKfgvqJJehwFYxnPOXGYV13i/xCvYksdL3Hi4rU2mATtX 5WcVhRRM920NDjhjKpYNRvjgrhc8sG5gSYPEu1aD71iV3Xp4RVGWYsClDDPLDTll Oy/hJsG3UjPxlqUl4DV/GRQEWXSCdNecJSr7utyGcQxkTMBPcPFQDTWKB1TBXcro ql/teywAZ6O2ZrlYbC2v9ylbyX3BozzevLmaKVuMe9ZR7bcf7SRgfZarGRNbmgrl L3L43SsAr+rUtVjyxS+0BtsJe884wEScfvyJSp1ja7R22Mw69ojGxgtmcO/CwPN9 +vMhJMfOX5SYDMRQjjElxyp5ZW41vk1j/btRUdjDOfstaFxOwEV4mh7wv4iFv3eE tCObl8OOM9IaFvXXlDPrCPKRqgWf2ScAsOS4qr+PF/E0U2jhEGBg7dXie3bGI1j8 H+dxHWMDlnlRSTsDX+IryqWvFvusRHetc7AX6bcNytPrrpvAJEyNnhCatCJg0WTG 4onhAXG9B0iDQg07cdk3R/B/dJsdT/CeNucKrNaAe6zFvbCKq7VVO+CqGX43F90i NzhDRmlz6icX59kYm29Z =gqyT -----END PGP SIGNATURE----- --Apple-Mail=_1507D7DE-6B6D-4A51-A330-530F0C5CB6BF-- From nobody Sun Nov 1 20:07:40 2015 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C9861B4433; Sun, 1 Nov 2015 20:07:38 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.7.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20151102040738.1146.98238.idtracker@ietfa.amsl.com> Date: Sun, 01 Nov 2015 20:07:38 -0800 Archived-At: Cc: dnssd@ietf.org Subject: [dnssd] I-D Action: draft-ietf-dnssd-mdns-dns-interop-02.txt X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 02 Nov 2015 04:07:38 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Extensions for Scalable DNS Service Discovery Working Group of the IETF. Title : On Interoperation of Labels Between DNS and Other Resolution Systems Author : Andrew Sullivan Filename : draft-ietf-dnssd-mdns-dns-interop-02.txt Pages : 11 Date : 2015-11-01 Abstract: Despite its name, DNS-Based Service Discovery can use naming systems other than the Domain Name System when looking for services. Moreover, when it uses the DNS, DNS-Based Service Discovery uses the full capability of DNS, rather than using a subset of available octets. In order for DNS-SD to be used effectively in environments where multiple different name systems and conventions for their operation are in use, it is important to attend to differences in the underlying technology and operational environment. This memo presents an outline of the requirements for selection of labels for conventional DNS and other resolution systems when they are expected to interoperate in this manner. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dnssd-mdns-dns-interop/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-dnssd-mdns-dns-interop-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnssd-mdns-dns-interop-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sun Nov 1 21:41:55 2015 Return-Path: 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 7CA681B4758 for ; Sun, 1 Nov 2015 21:41:53 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 HZnALrqY7JGT for ; Sun, 1 Nov 2015 21:41:52 -0800 (PST) Received: from mx2.yitter.info (mx2.yitter.info [IPv6:2600:3c03::f03c:91ff:fedf:cfab]) by ietfa.amsl.com (Postfix) with ESMTP id 221421B4756 for ; Sun, 1 Nov 2015 21:41:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id BB85910744 for ; Mon, 2 Nov 2015 05:41:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xwRjyZvQAudO for ; Mon, 2 Nov 2015 05:41:51 +0000 (UTC) Received: from mx2.yitter.info (t20010c4000003024c178f0e5b720c90d.v6.meeting.ietf94.jp [IPv6:2001:c40:0:3024:c178:f0e5:b720:c90d]) by mx2.yitter.info (Postfix) with ESMTPSA id A251C10741 for ; Mon, 2 Nov 2015 05:41:50 +0000 (UTC) Date: Mon, 2 Nov 2015 00:41:46 -0500 From: Andrew Sullivan To: dnssd@ietf.org Message-ID: <20151102054146.GC876@mx2.yitter.info> References: <20151102040738.1146.98238.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151102040738.1146.98238.idtracker@ietfa.amsl.com> User-Agent: Mutt/1.5.23 (2014-03-12) Archived-At: Subject: Re: [dnssd] I-D Action: draft-ietf-dnssd-mdns-dns-interop-02.txt 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2015 05:41:53 -0000 Hi, On Sun, Nov 01, 2015 at 08:07:38PM -0800, internet-drafts@ietf.org wrote: > > Title : On Interoperation of Labels Between DNS and Other Resolution Systems > Author : Andrew Sullivan > Filename : draft-ietf-dnssd-mdns-dns-interop-02.txt > Pages : 11 > Date : 2015-11-01 This is the upload I said I'd make. Again, apologies for the failure after Prague. If anyone wants to beat me up in the hall over any of this, I am prepared to have that discussion, but I don't expect to discuss it in any meeting here. Best regards, A -- Andrew Sullivan ajs@anvilwalrusden.com From nobody Sun Nov 1 21:48:05 2015 Return-Path: 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 D41A51B4797 for ; Sun, 1 Nov 2015 21:48:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 Nh1r9-oPpeIF for ; Sun, 1 Nov 2015 21:48:02 -0800 (PST) Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86AAD1B4796 for ; Sun, 1 Nov 2015 21:48:02 -0800 (PST) Received: by pasz6 with SMTP id z6so137588472pas.2 for ; Sun, 01 Nov 2015 21:48:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=X2UdlEDDqnBAidj2cUSXPt0tbdHcTbTiyCsNO8tOlcI=; b=WbJbL4Qn0dFmnHsquphOFFvSrrTMo7199IAMuY50ii8zkuBW6LwB+D8He+1vDd67rs C13qG74n115+3jmoenQcXnUID4w3dabtCFU1/1ZrhYP7tHivb3YiRBofZcl0ysynqp6k UHCz9GAPUo1flNSejx/Q51rRLomwn150qYVrzERZI2xenNUWGTZnagEvh2PcXBT3QAyA eEVWUGjnwajDGasmy/OrKVOppowgmjiNsTkHN/KVYMweZRDcq26+mMMGUpX14V4DnJ2u wLRuCA9M6Ohk17LDOY5W8PpTDjq7w7ERkbIdkQtFWlHGZIhsMGtqTkmxtR2uYAMQPV82 ViYg== X-Received: by 10.68.183.228 with SMTP id ep4mr25319584pbc.54.1446443282205; Sun, 01 Nov 2015 21:48:02 -0800 (PST) Received: from US-DOUGO-MAC.local (t20010c4000003024805bc335a35fa6e8.v6.meeting.ietf94.jp. [2001:c40:0:3024:805b:c335:a35f:a6e8]) by smtp.googlemail.com with ESMTPSA id qf2sm18677403pbb.3.2015.11.01.21.48.00 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Nov 2015 21:48:01 -0800 (PST) To: dnssd@ietf.org References: <9440F960-C332-43D8-930B-66345A158104@cisco.com> <562585AA.4090900@gmail.com> From: Douglas Otis X-Enigmail-Draft-Status: N1110 Message-ID: <5636F9B3.6030600@gmail.com> Date: Mon, 2 Nov 2015 14:50:43 +0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Archived-At: Subject: [dnssd] Issues just noted for draft-otis-dnssd-scalable-dns-sd-threats-02 that will be included in future update 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2015 05:48:04 -0000 Dear dnssd wg; Based on last minute feedback, corrections are needed. The term sitelocal was used incorrectly. Based on prior definitions, this implies addresses having a common prefix, which was not the intent. This term arose from RFC7368 that offered an example of a site-local name 'sitelocal'. This should be changed in the threats draft to inter-site addresses to ensure against possible confusion. Section 2.1.1 Was: The scheme supporting DNS should ensure queries against a sitelocal namespace is not forwarded to the Internet and to global root servers. Change to: The scheme supporting DNS should ensure queries against a locally defined namespace is not forwarded to the Internet and to global root servers. Was: 2.1.3. Restricted Distribution of Sitelocal Addresses Change to: 2.1.3. Restricted Distribution of Inter-site Addresses Note: term is used in RFC4193 Section 4.1. Will add a section with a focus on what addresses should be placed into global DNS. Will add reference to draft-ietf-dnssd-mdns-dns-interop. Sorry for the omission. Regards, Douglas Otis From nobody Mon Nov 2 14:37:02 2015 Return-Path: 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 8B59E1A8A0F for ; Mon, 2 Nov 2015 14:36:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 v7mJjFexjRSw for ; Mon, 2 Nov 2015 14:36:58 -0800 (PST) Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 247FD1A8A0E for ; Mon, 2 Nov 2015 14:36:58 -0800 (PST) Received: by padec8 with SMTP id ec8so51952323pad.1 for ; Mon, 02 Nov 2015 14:36:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=f+xPl6XRrdGH+kFhvAa7Z6Lvxj44D27QdF+vT95kkLo=; b=QYfNd0l/TtSj2HDjU6MRl//aBzAHqSAHv0hEzkS3DNBDz7aaDSxcqT6yvgBrhTFAPS f65+Jc5RfMLhyowUUX2Tf1lIV/5/RzR0lD0aFeGX2xJ6gYRuC+w3NVAMYZXNtkXs+vir kBHVuQ20srTJgQt2MI7C8UuXlIqrTb7RclTYOichAC3LTVLmrEumkHnMa359VBql6ug0 nI4FARCA/CaBv+PQDtPt6m/slBq77W3v4SHvjnTLKjesUiVtNEM/cfgSnM3hiVF76lqX 8y3zWRckUq4BxsKGHEbJLSSWBl2GOLUDxBIm0lec06hCm49k6Z8NPwoeHAe8n93wLiZM Cg6A== X-Received: by 10.68.165.194 with SMTP id za2mr29688024pbb.72.1446503817797; Mon, 02 Nov 2015 14:36:57 -0800 (PST) Received: from US-DOUGO-MAC.local ([101.110.53.38]) by smtp.googlemail.com with ESMTPSA id pn8sm25919028pbb.16.2015.11.02.14.36.55 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Nov 2015 14:36:57 -0800 (PST) To: dnssd@ietf.org References: <20151102040738.1146.98238.idtracker@ietfa.amsl.com> <20151102054146.GC876@mx2.yitter.info> From: Douglas Otis X-Enigmail-Draft-Status: N1110 Message-ID: <5637E62E.2050105@gmail.com> Date: Tue, 3 Nov 2015 07:39:42 +0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151102054146.GC876@mx2.yitter.info> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Archived-At: Subject: [dnssd] draft-ietf-dnssd-mdns-dns-interop and draft-otis-dnssd-scalable-dns-sd-threats 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2015 22:36:59 -0000 Dear Andrew, Your revised version would have been helpful. My understanding of what you wish avoided in the threat review, humorously referred to as advice on juggling spinning knives, differs from WG agreements reached at the last meeting. This covers exceptions made by domain owners who are not prohibited nor assured produce negative answers. Such exceptions clearly demarcated with the use of DNS-SD conventions permit more liberal repertoires to convey locally defined network space under current protocol conventions which may be published globally. Most of these conventions have or are now undergoing last call. There was no mention of a parallel A-label namespace to be created, nor expectations of negative answers becoming the norm. You assert DNS-SD conventions will result in a significant increase in DNS lookup traffic of no value. Further you assert that since adoption of RFC6763, increased use of IDNA makes the situation worse. As such, your view is to rule out considerations regarding this namespace. The Portion of the Service Instance Name includes what the DNS-SD Scalable Threats document describes as-- ._._... is described in RFC6763 as which encourages use of a more liberal repertoire. At the last meeting, it seemed agreement had been reached regarding exceptions for the portion of the namespace. The modicum of advice was to use '_' in place of punctuation or spaces to reduce errors in administrative review or those caused by code expecting neither space or punctuation. This advice can be removed if the WG considers it not warranted. After all, since RFC6763 was written, applications have become far better at handling UTF-8. The domain owner will be impacted by any additional queries caused by erroneous handling of DNS-SD resources and can assess the value of allowing more liberal repertoires. RFC6763 states in section 7.2. Service Name Length Limits ,-- Typically, DNS-SD service records are placed into subdomains of their own beneath a company's existing domain name. Since these subdomains are intended to be accessed through graphical user interfaces, not typed on a command line, they are frequently long and descriptive. Including the length byte, the user-visible service domain may be up to 64 bytes. '-- RFC6763 further states in section 4.1.3. Domain Names ,-- Because Service Instance Names are not host names, they are not constrained by the usual rules for host names [RFC1033] [RFC1034] [RFC1035], and rich-text service subdomains are allowed and encouraged, for example: Building 2, 1st Floor . example . com . ... In cases where the DNS server returns a negative response for the name in question, client software MAY choose to retry the query using the "Punycode" algorithm [RFC3492] to convert the UTF-8 name to an IDNA "A-label" [RFC5890], beginning with the top-level label, then issuing the query repeatedly, with successively more labels translated to IDNA A-labels each time, and giving up if it has converted all labels to IDNA A-labels and the query still fails. '-- The interop draft overlooks existing conventions surrounding DNS-SD and offers far less guidance than that given in the threat review. If your assertions are correct about the risk, much more needs to be said and not less. Regards, Douglas Otis From nobody Tue Nov 3 10:00:50 2015 Return-Path: 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 20E741B3414 for ; Tue, 3 Nov 2015 10:00:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.999 X-Spam-Level: X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 C_7gP3kSvC7z for ; Tue, 3 Nov 2015 10:00:46 -0800 (PST) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EC1E1B3416 for ; Tue, 3 Nov 2015 10:00:36 -0800 (PST) Received: by pabfh17 with SMTP id fh17so24783477pab.0 for ; Tue, 03 Nov 2015 10:00:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:subject:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-type; bh=HTXzOu5MgZ6FD+8NN8I4LZZkJAFoI0Re4a+Pz5peIRk=; b=pui5TW0B1gLr4PXwmnfogfy7AAsQmUejzxpf0ALaktm2xTThnWw4UPQHkZo7Kv/nh2 nNuz2qeRv4zD4kMg89FzR9tDNSjbdnDzrf6DgGxxGJgL+xGCX9oLQ6oggzc1dj4Wk1vt IbTkZ/dpQjcOPOCUYpp61ZDHenuZdcbAyHths7+N8apue2wnrAFnq4buHPml+remdWD+ WMAW40f0YhWXxOautGSvGOYgt4zQ5nxNNY6FevVxAl0yFkRjPNsk0jGCBkO7USx3vwi9 BZROSxa3EwDEE81NGkENkbKR8pR2pHofTAFNjm0P6o2tto99Xpmn6w+QszM5miSG0cBU k0DA== X-Received: by 10.68.179.228 with SMTP id dj4mr35213801pbc.112.1446573636025; Tue, 03 Nov 2015 10:00:36 -0800 (PST) Received: from twicinski-ltm.internal.salesforce.com ([204.14.239.106]) by smtp.googlemail.com with ESMTPSA id yi8sm30763039pab.22.2015.11.03.10.00.33 for (version=TLSv1/SSLv3 cipher=OTHER); Tue, 03 Nov 2015 10:00:34 -0800 (PST) References: To: dnssd@ietf.org From: Tim Wicinski X-Forwarded-Message-Id: Message-ID: <5638F63F.6040406@gmail.com> Date: Wed, 4 Nov 2015 03:00:31 +0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="------------050300080009020202090407" Archived-At: Subject: [dnssd] Fwd: [DNSOP] Request for Comments on I-D about IoT DNS Name Autoconf 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Nov 2015 18:00:48 -0000 This is a multi-part message in MIME format. --------------050300080009020202090407 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit All, This request came into DNSOP for us to attend 6man. In looking at their presentation, it appears to be more of a dns-sd type of solution looking for a problem. I dug up the slides, because they show how this is different/better than mDNS. https://tools.ietf.org/html/draft-jeong-6man-iot-dns-autoconf-00 https://www.ietf.org/proceedings/94/slides/slides-94-6man-1.pdf tim #2 --------------050300080009020202090407 Content-Type: message/rfc822; name="[DNSOP] Request for Comments on I-D about IoT DNS Name Autoconf.eml" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0="[DNSOP] Request for Comments on I-D about IoT DNS Name Autoc"; filename*1="onf.eml" Delivered-To: tjw.ietf@gmail.com Received: by 10.27.51.11 with SMTP id z11csp1709836wlz; Tue, 3 Nov 2015 01:55:30 -0800 (PST) X-Received: by 10.68.220.194 with SMTP id py2mr32159720pbc.37.1446544530469; Tue, 03 Nov 2015 01:55:30 -0800 (PST) Return-Path: Received: from mail.ietf.org (mail.ietf.org. [2001:1900:3001:11::2c]) by mx.google.com with ESMTPS id my1si41052466pbc.186.2015.11.03.01.55.29 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Nov 2015 01:55:30 -0800 (PST) Received-SPF: pass (google.com: domain of dnsop-bounces@ietf.org designates 2001:1900:3001:11::2c as permitted sender) client-ip=2001:1900:3001:11::2c; Authentication-Results: mx.google.com; spf=pass (google.com: domain of dnsop-bounces@ietf.org designates 2001:1900:3001:11::2c as permitted sender) smtp.mailfrom=dnsop-bounces@ietf.org; dkim=pass header.i=@ietf.org; dkim=neutral (body hash did not verify) header.i=@gmail.com; dmarc=fail (p=NONE dis=NONE) header.from=gmail.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BEAE31B3143; Tue, 3 Nov 2015 01:52:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1446544324; bh=U1jQIn9RCDTNCf6UxZUdvlqWhyVsrDIq3DdVuq4UI/U=; h=MIME-Version:Date:Message-ID:From:To:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Sender; b=uGIlNcTTwCQR8FoIRUGQr9Lr10HB7J3JM7a7Rq0FM4slnI+APMfNIvFLym+o1yKm7 N1+FjZzXdi37f4WNdcWFHizlbXI/AOXxUeRbjuXpcLuk1uPksWruhmtTtDOZAjmuWl 896BADZVO3hvV+9lTrK95BSBm51ewF+eXHwJqUTc= X-Original-To: dnsop@ietfa.amsl.com Delivered-To: dnsop@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25B661B30B8; Tue, 3 Nov 2015 01:52:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 2DRdHEsd6Vz8; Tue, 3 Nov 2015 01:51:58 -0800 (PST) Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D76D1B3124; Tue, 3 Nov 2015 01:51:57 -0800 (PST) Received: by ykba4 with SMTP id a4so10049952ykb.3; Tue, 03 Nov 2015 01:51:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=kp6lzWK8uhgWLdPSRYGRQn3NJ3RFwKqfys1+5bcbkEA=; b=UWC8vsl8ONEVVpOhpKhM7TYhrjPaaC62m1btM+45qqmIV0iRAVW632OAwQE6MEhQm7 aMvwS/CpnNpKGe/mRyX2dcpTT4zX09rXD+7vdy6UgihRf7p3WMR2XIWjZ+OUexUL9yBR xpnfRluJ4bzJ8QqbMwdN9lelMZCWgfRAJYDC1gLxl61CT3K0Hakj2WgsgzbDvyhqpxCC h6mDsb9CfshIR+1OaQCMQg4QFS4/LJVeDNJpRPx5n7mZVzDVhkdcG9dqKgtXMCsf7qix Viinyi2HMhY8KuDMUjjsM/lbS2peQhRfNNCQr8wSj9djK0rEpobj883E8ZhQfZdl2RXB X1jA== MIME-Version: 1.0 X-Received: by 10.129.157.12 with SMTP id u12mr11430530ywg.258.1446544316482; Tue, 03 Nov 2015 01:51:56 -0800 (PST) Received: by 10.129.109.68 with HTTP; Tue, 3 Nov 2015 01:51:56 -0800 (PST) Date: Tue, 3 Nov 2015 18:51:56 +0900 Message-ID: From: "Mr. Jaehoon Paul Jeong" To: IETF IPv6 Mailing List , 6lo@ietf.org, dnsop@ietf.org Archived-At: Cc: Ted Hardie , Hyunjong Jeon , Myung-Ki Shin , Chris Shen , Brian Haberman , Jung-Soo Park , joel jaeggli , Kyemyung Jung , Sejun Lee , "Mr. Jaehoon Paul Jeong" Subject: [DNSOP] Request for Comments on I-D about IoT DNS Name Autoconf X-BeenThere: dnsop@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: IETF DNSOP WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4396025533398845640==" Errors-To: dnsop-bounces@ietf.org Sender: "DNSOP" --===============4396025533398845640== Content-Type: multipart/alternative; boundary=94eb2c0b8f0022cf7e05239fd85e --94eb2c0b8f0022cf7e05239fd85e Content-Type: text/plain; charset=UTF-8 Hi 6man, 6lo and dnsop folks, There will be a talk about IoT DNS Name Autoconfiguration in 6man WG's morning session tomorrow, 11/4/2015. Title: DNS Name Autoconfiguration for Internet of Things Devices https://tools.ietf.org/html/draft-jeong-6man-iot-dns-autoconf-00 I hope we discuss how to configure the DNS names of IoT devices in networks, such as home network, enterprise network, road network, and factory network with the minimum configuration effort. Imagining that you have hundreds of IoT devices in your network, will you configure their DNS names manually one by one? To prepare for the new wave of IoT networks based on IPv6, we need to think of the DNS naming and auto-registration into DNS for IoT devices. We (SKKU and Jubix) implemented a prototype for a smart grid with electric meters Korea Electric Power Corporation (KEPCO) that is the main power delivery company in South Korea. Our meters are running on IPv6/6lo/Wi-SUN (IEEE 802.15.4g). Since I have 5 minutes for the presentation tomorrow, I will shortly introduce the motivation, the DNS name format based on the ITU-T/ISO object identifier, and our protocol. Please read my draft and slides in the 6man agenda link: https://datatracker.ietf.org/meeting/94/agenda.html The slides has the backup slides (as Appendix slides) that explain the implementation and demonstration, and also the comparison with mDNS. Thanks for reading this email. Best Regards, Paul =========================== Mr. Jaehoon (Paul) Jeong, Ph.D. Assistant Professor Department of Software Sungkyunkwan University Office: +82-31-299-4957 Email: jaehoon.paul@gmail.com, pauljeong@skku.edu Personal Homepage: http://cpslab.skku.edu/people-jaehoon-jeong.php --94eb2c0b8f0022cf7e05239fd85e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi 6man, 6lo and dnsop folks,

There will be a= talk about IoT DNS Name Autoconfiguration=C2=A0
in 6man WG's= morning session tomorrow, 11/4/2015.

Title: = DNS Name Autoconfiguration for Internet of Things Devices
=

I hope we discuss how to configure the DNS names o= f IoT devices in networks,=C2=A0
such as home network, enterprise= network, road network, and factory network
with the minimum conf= iguration effort.

Imagining that you have hundreds= of IoT devices in your network,
will you configure their DNS nam= es manually one by one?

To prepare for the new wav= e of IoT networks based on IPv6,
we need to think of the DNS nami= ng and auto-registration into DNS for IoT devices.

We (SKKU and Jubix) implemented a prototype for a smart grid with el= ectric meters
Korea Electric Power Corporation (KEPCO) that is th= e main power delivery company in South Korea.=C2=A0
Our meters ar= e running on IPv6/6lo/Wi-SUN (IEEE 802.15.4g).

Sin= ce I have 5 minutes for the presentation tomorrow, I will shortly introduce= the motivation,
the DNS name format based on the ITU-T/ISO o= bject identifier, and our protocol.

Please read my= draft and slides in the 6man agenda link:

The slides has the backup s= lides (as Appendix slides) that explain
the implementation and de= monstration, and also the comparison with mDNS.

Th= anks for reading this email.

Best Regards,
Paul =C2=A0
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
Mr. Jaehoon (Paul) Jeong, Ph.D.
Assistant= Professor
Department of Software
Sungkyunkwan University
Office: = +82-31-299-4957
Email: jaehoon.paul@gmail.com,=C2=A0pauljeong@skku.edu=
Personal Homepage: http://cpslab.skku.edu/people-jaehoon-jeong.php
--94eb2c0b8f0022cf7e05239fd85e-- --===============4396025533398845640== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop --===============4396025533398845640==-- --------------050300080009020202090407-- From nobody Wed Nov 4 14:37:28 2015 Return-Path: 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 E940E1B34E1 for ; Wed, 4 Nov 2015 14:37:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 tHOXukUWuBTK for ; Wed, 4 Nov 2015 14:37:25 -0800 (PST) Received: from mx2.yitter.info (mx2.yitter.info [50.116.54.116]) by ietfa.amsl.com (Postfix) with ESMTP id 5A2A61B34DA for ; Wed, 4 Nov 2015 14:37:25 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mx2.yitter.info (Postfix) with ESMTP id 1283110685 for ; Wed, 4 Nov 2015 22:37:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca Received: from mx2.yitter.info ([127.0.0.1]) by localhost (mx2.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dnh2y1ulal12 for ; Wed, 4 Nov 2015 22:37:21 +0000 (UTC) Received: from mx2.yitter.info (dhcp-28-138.meeting.ietf94.jp [133.93.28.138]) by mx2.yitter.info (Postfix) with ESMTPSA id F29B810647 for ; Wed, 4 Nov 2015 22:37:20 +0000 (UTC) Date: Wed, 4 Nov 2015 17:37:18 -0500 From: Andrew Sullivan To: dnssd@ietf.org Message-ID: <20151104223718.GA3933@mx2.yitter.info> References: <20151102040738.1146.98238.idtracker@ietfa.amsl.com> <20151102054146.GC876@mx2.yitter.info> <5637E62E.2050105@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5637E62E.2050105@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Archived-At: Subject: Re: [dnssd] draft-ietf-dnssd-mdns-dns-interop and draft-otis-dnssd-scalable-dns-sd-threats 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2015 22:37:28 -0000 Hi Doug, I continue to think that you and I are divided here by a common language. I do also think that split-brain DNS is, when also mixing namespaces, dangerous (and yes, the "spinning knives" remark was intended to lighten a discussion that can otherwise get heated). But it sounds like we need to sit down at some point and see whether I can better understand how you want this draft to change. It'll be very difficult this week, though if you want to talk during bits & bytes this evening I'll be around. Alternatively, maybe we need to plan to talk once everyone has made it back home. We can try to co-ordinate off-list? Best regards, A On Tue, Nov 03, 2015 at 07:39:42AM +0900, Douglas Otis wrote: > > Dear Andrew, > > Your revised version would have been helpful. My > understanding of what you wish avoided in the threat review, > humorously referred to as advice on juggling spinning > knives, differs from WG agreements reached at the last meeting. > > This covers exceptions made by domain owners who are not > prohibited nor assured produce negative answers. Such > exceptions clearly demarcated with the use of DNS-SD > conventions permit more liberal repertoires to convey > locally defined network space under current protocol > conventions which may be published globally. Most of these > conventions have or are now undergoing last call. > > There was no mention of a parallel A-label namespace to be > created, nor expectations of negative answers becoming the norm. > > You assert DNS-SD conventions will result in a significant > increase in DNS lookup traffic of no value. Further you > assert that since adoption of RFC6763, increased use of IDNA > makes the situation worse. As such, your view is to rule > out considerations regarding this namespace. > > The Portion of the Service Instance Name includes > what the DNS-SD Scalable Threats document describes as-- > > ._._... > > is described in RFC6763 as which > encourages use of a more liberal repertoire. At the last > meeting, it seemed agreement had been reached regarding > exceptions for the portion of the namespace. > > The modicum of advice was to use '_' in place of punctuation > or spaces to reduce errors in administrative review or those > caused by code expecting neither space or punctuation. This > advice can be removed if the WG considers it not warranted. > After all, since RFC6763 was written, applications have > become far better at handling UTF-8. The domain owner will > be impacted by any additional queries caused by erroneous > handling of DNS-SD resources and can assess the value of > allowing more liberal repertoires. > > RFC6763 states in section > 7.2. Service Name Length Limits > ,-- > Typically, DNS-SD service records are placed into subdomains > of their own beneath a company's existing domain name. > Since these subdomains are intended to be accessed through > graphical user interfaces, not typed on a command line, they > are frequently long and descriptive. Including the length > byte, the user-visible service domain may be up > to 64 bytes. > '-- > > RFC6763 further states in section > 4.1.3. Domain Names > ,-- > Because Service Instance Names are not host names, they are > not constrained by the usual rules for host names [RFC1033] > [RFC1034] [RFC1035], and rich-text service subdomains are > allowed and encouraged, for example: > > Building 2, 1st Floor . example . com . > ... > > In cases where the DNS server returns a negative response > for the name in question, client software MAY choose to > retry the query using the "Punycode" algorithm [RFC3492] to > convert the UTF-8 name to an IDNA "A-label" [RFC5890], > beginning with the top-level label, then issuing the query > repeatedly, with successively more labels translated to IDNA > A-labels each time, and giving up if it has converted all > labels to IDNA A-labels and the query still fails. > '-- > > The interop draft overlooks existing conventions surrounding > DNS-SD and offers far less guidance than that given in the > threat review. If your assertions are correct about the > risk, much more needs to be said and not less. > > Regards, > Douglas Otis > > _______________________________________________ > dnssd mailing list > dnssd@ietf.org > https://www.ietf.org/mailman/listinfo/dnssd -- Andrew Sullivan ajs@anvilwalrusden.com From nobody Thu Nov 5 01:58:10 2015 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BC2B1A9141; Thu, 5 Nov 2015 01:58:08 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.8.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20151105095808.15958.27458.idtracker@ietfa.amsl.com> Date: Thu, 05 Nov 2015 01:58:08 -0800 Archived-At: Cc: dnssd@ietf.org Subject: [dnssd] I-D Action: draft-ietf-dnssd-hybrid-02.txt X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.15 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: Thu, 05 Nov 2015 09:58:08 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Extensions for Scalable DNS Service Discovery Working Group of the IETF. Title : Hybrid Unicast/Multicast DNS-Based Service Discovery Author : Stuart Cheshire Filename : draft-ietf-dnssd-hybrid-02.txt Pages : 25 Date : 2015-11-05 Abstract: Performing DNS-Based Service Discovery using purely link-local Multicast DNS enables discovery of services that are on the local link, but not (without some kind of proxy or similar special support) discovery of services that are outside the local link. Using a very large local link with thousands of hosts facilitates service discovery, but at the cost of large amounts of multicast traffic. Performing DNS-Based Service Discovery using purely Unicast DNS is more efficient and doesn't require excessively large multicast domains, but requires that the relevant data be available in the Unicast DNS namespace. This can be achieved by manual DNS configuration (as has been done for many years at IETF meetings to advertise the IETF Terminal Room printer) but this is labor intensive, error prone, and requires a reasonable degree of DNS expertise. The Unicast DNS namespace can be populated with the required data automatically by the devices themselves, but that requires configuration of DNS Update keys on the devices offering the services, which has proven onerous and impractical for simple devices like printers and network cameras. Hence, to facilitate efficient and reliable DNS-Based Service Discovery, a compromise is needed that combines the ease-of-use of Multicast DNS with the efficiency and scalability of Unicast DNS. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dnssd-hybrid/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-dnssd-hybrid-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnssd-hybrid-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Nov 5 02:10:40 2015 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B0C861A916D; Thu, 5 Nov 2015 02:10:37 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.8.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20151105101037.26973.72144.idtracker@ietfa.amsl.com> Date: Thu, 05 Nov 2015 02:10:37 -0800 Archived-At: Cc: dnssd@ietf.org Subject: [dnssd] I-D Action: draft-ietf-dnssd-push-03.txt X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.15 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: Thu, 05 Nov 2015 10:10:37 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Extensions for Scalable DNS Service Discovery Working Group of the IETF. Title : DNS Push Notifications Authors : Tom Pusateri Stuart Cheshire Filename : draft-ietf-dnssd-push-03.txt Pages : 24 Date : 2015-11-05 Abstract: The Domain Name System (DNS) was designed to return matching records efficiently for queries for data that is relatively static. When those records change frequently, DNS is still efficient at returning the updated results when polled. But there exists no mechanism for a client to be asynchronously notified when these changes occur. This document defines a mechanism for a client to be notified of such changes to DNS records, called DNS Push Notifications. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dnssd-push/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-dnssd-push-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnssd-push-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Nov 11 06:01:07 2015 Return-Path: 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 F2FC51ACE76; Wed, 11 Nov 2015 06:01:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 aTlU53iIsH6b; Wed, 11 Nov 2015 06:01:00 -0800 (PST) Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3AF91ACE73; Wed, 11 Nov 2015 06:01:00 -0800 (PST) Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 94873880E6; Wed, 11 Nov 2015 06:01:00 -0800 (PST) Received: from clemson.jhuapl.edu (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 9DC73328081A; Wed, 11 Nov 2015 06:00:59 -0800 (PST) References: <20151110204646.14504.87111.idtracker@ietfa.amsl.com> To: "ipv6@ietf.org" , mboned@ietf.org, pim@ietf.org, IPv6 Operations , "int-area@ietf.org" , "6lo@ietf.org" <6lo@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>, dnssd@ietf.org, homenet@ietf.org From: Brian Haberman X-Forwarded-Message-Id: <20151110204646.14504.87111.idtracker@ietfa.amsl.com> Message-ID: <56434A0F.2070407@innovationslab.net> Date: Wed, 11 Nov 2015 09:00:47 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151110204646.14504.87111.idtracker@ietfa.amsl.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="IFJ7NbECJQGqSn59wSnwBW2BwEQHsKC4C" Archived-At: Subject: [dnssd] Fwd: New Non-WG Mailing List: Mcast-wifi -- Discussions related to issues with multicast in 802.11 Wi-Fi networks & solutions/optimizations targeted at resolving these issues. 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Nov 2015 14:01:03 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --IFJ7NbECJQGqSn59wSnwBW2BwEQHsKC4C Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable All, Apologies for the spam, but I think this is relevant to a number of WGs. If you have an interest in the interactions between IP multicast and 802.11 networks, please join the list and contribute to the discussio= n. Regards, Brian -------- Forwarded Message -------- Subject: New Non-WG Mailing List: Mcast-wifi -- Discussions related to issues with multicast in 802.11 Wi-Fi networks & solutions/optimizations targeted at resolving these issues. Date: Tue, 10 Nov 2015 12:46:46 -0800 From: IETF Secretariat Reply-To: ietf@ietf.org To: IETF Announcement List CC: mcast-wifi@ietf.org A new IETF non-working group email list has been created. List address: mcast-wifi@ietf.org Archive: https://mailarchive.ietf.org/arch/search/?email_list=3Dmcast-wif= i To subscribe: https://www.ietf.org/mailman/listinfo/mcast-wifi Purpose: This list is used for discussions related to issues with multicast in 802.11 Wi-Fi networks as well as solutions/optimizations targeted at resolving these issues. Related working groups are 6lo/6man/6tisch/intarea/mboned/pim/v6ops. For additional information, please contact the list administrators. --IFJ7NbECJQGqSn59wSnwBW2BwEQHsKC4C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2 iQEcBAEBCAAGBQJWQ0oaAAoJEBOZRqCi7goqTNcH/3ovB093WMtbbeSJpfa7SPku C18dvDbyzJDdoChnaVPmp5IB9xrin7y52SW2ul5V89I+Cr/U19WCmRweEAZahy2E k11y3Mfec+8cip4vBkyo4GR5CETAAgMT1+60XB6lsFOdLe8Q8TT/A4A+nvrDg4Ey TBAFAYBKQuJRyUDtPAEi/b1JbrBDdx49Zvr3JL9mkyJeO6czi4/IjqIo+yPT7u1F 75XSEqUeoh9fdudVKYH1pD/k/AqKqlINSjmm9PbsE+hwOJ1NebVLXCj6g+jm0uOe coojsJ5PJkcSLpvwrfnqERG+EzTpgjLpDxEZ27JTRWHd5ds6vFJK3mBHlp8gGSg= =k+pk -----END PGP SIGNATURE----- --IFJ7NbECJQGqSn59wSnwBW2BwEQHsKC4C-- From nobody Thu Nov 19 07:04:33 2015 Return-Path: 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 DC4B11B2B2C; Thu, 19 Nov 2015 07:04:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 rLOktiZKoBCb; Thu, 19 Nov 2015 07:04:23 -0800 (PST) Received: from hydrogen.portfast.net (hydrogen.portfast.net [188.246.200.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7E901B2AED; Thu, 19 Nov 2015 07:04:16 -0800 (PST) Received: from [46.227.151.81] (port=64894 helo=Rays-MacBook-Pro.local) by hydrogen.portfast.net ([188.246.200.2]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1ZzQkv-0006yA-G7 (Exim 4.72) (return-path ); Thu, 19 Nov 2015 15:04:13 +0000 To: HOMENET From: Ray Bellis X-Enigmail-Draft-Status: N1110 Message-ID: <564DE4F8.5060500@bellis.me.uk> Date: Thu, 19 Nov 2015 15:04:24 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Cc: dnssd@ietf.org Subject: [dnssd] Homenet Naming and Service Discovery architecture 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Nov 2015 15:04:26 -0000 During the IETF 94 session the Homenet WG discussed the proposal that we should produce a detailed architecture document that puts together *all* of the Naming and Service Discovery components for Homenet as a coherent system. To that end I'd like to formally request volunteers to help put that document together. Contributors need to be familiar with normal DNS and with the work going on in the DNSSD working group. It should be assumed that the existing Homenet WG documents for Frontend Naming Delegation shall be a part of the architecture (albeit limited to the question of how to autonomously setup zone transfers from an in-home device to an off-net DNS server). I know that Doug Otis already volunteered, and I think Stuart Cheshire indicated that he might. I think a total of around four authors should provide a good mix. thanks, Ray From nobody Fri Nov 20 11:05:13 2015 Return-Path: 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 03E4D1B3D19 for ; Fri, 20 Nov 2015 11:05:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -15.086 X-Spam-Level: X-Spam-Status: No, score=-15.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 ugp0BtvKZQfT for ; Fri, 20 Nov 2015 11:05:10 -0800 (PST) Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC8141B3D16 for ; Fri, 20 Nov 2015 11:05:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1557; q=dns/txt; s=iport; t=1448046310; x=1449255910; h=from:to:subject:date:message-id:mime-version; bh=cBDJg3GChYevY/ii7+C6AbbdIWm/+BaJBp/QWA+l59M=; b=OG+E2DSSxH6ZcPsZK4PSwikSakkjr/rVXn5uYKx0m4E4sj3fUprolwJD 0w1mjC5epzorcuUkc0KZ53hcqlSTvuUkTI5qPrBShHLXB8Sa1rcsK00O+ mWtUXZRi7OUFYLA7NY8+94x/HNT+7DL41soJWF6yqgpb0VV7YCIFXvAi0 k=; X-Files: signature.asc : 841 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DhAgAIbk9W/4cNJK1egztTdbxwghoOg?= =?us-ascii?q?WUhhWQCgVI4FAEBAQEBAQF/C4Q7gQsBgQAnBCGIIA2gWaAZAQEBAQEBBAEBAQE?= =?us-ascii?q?BAQEBAREFBIZUAYIPixKBFQWWTAGCV4FhiHaBXYRAhzWOeQEfAUOEBIUWgQcBA?= =?us-ascii?q?QE?= X-IronPort-AV: E=Sophos;i="5.20,323,1444694400"; d="asc'?scan'208";a="209759527" Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Nov 2015 19:05:09 +0000 Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id tAKJ59H2016778 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Fri, 20 Nov 2015 19:05:10 GMT Received: from xch-aln-016.cisco.com (173.36.7.26) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 20 Nov 2015 13:05:09 -0600 Received: from xch-aln-016.cisco.com ([173.36.7.26]) by XCH-ALN-016.cisco.com ([173.36.7.26]) with mapi id 15.00.1104.000; Fri, 20 Nov 2015 13:05:09 -0600 From: "Ralph Droms (rdroms)" To: "dnssd@ietf.org" Thread-Topic: IETF-94 meeting minutes Thread-Index: AQHRI8ZgQj4KGN+f9U6vvTgw7eBtGQ== Date: Fri, 20 Nov 2015 19:05:09 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.131.118.56] Content-Type: multipart/signed; boundary="Apple-Mail=_0E7727AC-1ED2-4F74-9691-C06C43CA4FBA"; protocol="application/pgp-signature"; micalg=pgp-sha256 MIME-Version: 1.0 Archived-At: Subject: [dnssd] IETF-94 meeting minutes 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 19:05:12 -0000 --Apple-Mail=_0E7727AC-1ED2-4F74-9691-C06C43CA4FBA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I've posted minutes from the dnssd WG meeting in Yokohama: = https://www.ietf.org/proceedings/94/minutes/minutes-94-dnssd Please review and let me know if you find anything you think should be = changed. - Ralph --Apple-Mail=_0E7727AC-1ED2-4F74-9691-C06C43CA4FBA Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJWT27kAAoJEINeeBNmFjV5ofAQAMUGZ9s+4uC9Kl4BNIoGFBMS N0CClSYb+3AnNOqtaLLjPeCXl4MY3B7g5F4zG/okSSasuwofg5JTc6ux1PWjxjf3 ywvQLvi4AwkLcb8r/zuDip8wVJaSrMNkJDxqQpW7ddmAuxrlVnTh69vIhgPX9BrL 98elnc5WJgS0CsdFc8/FzCY748M5fKGClGVPk+nN8EoHWCVQkvz19luDT9KicyiD W8qnweycBCOlawNU3YJ4T4EgJeQIX6btMQNBORpgleYAzVvOYKPP16rbO7/hPfdf defFz7hJlaWw7JuY/gtOWHiaPmfABkbjn9FCAiFtyoKWDV+sa93Mu8xV6A4gZysM kR6JYCRFLpL5kdq8vn+AdYjomwGcg4rNUSaxeHHKZt3j7RPk21sHwyHrXx/g44Je 9NDtAWrtR0weVg88lottaAhI7YHlQnouo9PhZt55ivhvqwH5kN/JY99F71od7F0S Lda7Z1CqlfDzEUZ2QJk6xvHiV1djFXWOUm1p9j963BK2b8oVKpIlhSab7/2PJ3UQ V8nY16J3lkK2l4F6gKsrHcdgXI731ihg02WF2M3rRmzdwuWn+r96AVqByb5KADHX pGY9lK0SkYb8mCRqzuxsQhmoQXc7PUo0QkRXFVFhxeApkK1AbIRTfAI/8Okgpnvy E1BXSZci3vZtgSId2OJs =jMxT -----END PGP SIGNATURE----- --Apple-Mail=_0E7727AC-1ED2-4F74-9691-C06C43CA4FBA--