[dnssd] LF comments on a new document

"Aggarwal, Ashutosh" <aaggarwa@qce.qualcomm.com> Wed, 09 July 2014 21:02 UTC

Return-Path: <aaggarwa@qce.qualcomm.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 E8D771B27A9 for <dnssd@ietfa.amsl.com>; Wed, 9 Jul 2014 14:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] 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 8Q8X4wPtjZ4E for <dnssd@ietfa.amsl.com>; Wed, 9 Jul 2014 14:02:48 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A9F01A0007 for <dnssd@ietf.org>; Wed, 9 Jul 2014 14:02:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qce.qualcomm.com; i=@qce.qualcomm.com; q=dns/txt; s=qcdkim; t=1404939769; x=1436475769; h=from:to:cc:subject:date:message-id:mime-version; bh=0bGMt74Ysn0D1M88y4IsLCCsox8YGTVGhQ9YnE0v17c=; b=QMEqcGUwyihqUIfTbFzlGR2thkujSOMLNl5cdNd6CGJc/6rDCMkFX3Zb TCji8tnbA8H1RHr12+CN8xSNMKyALT39anyfU/52VIjuPejd0N48hg2EI q+VKDfCNMoLV1r6aVyUyub0/QrrqkJTmgOOHv/gEDjoQGvZXRS9lxR/tT k=;
X-IronPort-AV: E=McAfee;i="5600,1067,7494"; a="69363866"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth01.qualcomm.com with ESMTP; 09 Jul 2014 14:02:49 -0700
X-IronPort-AV: E=Sophos;i="5.01,633,1400050800"; d="scan'208,217";a="763990882"
Received: from nasanexhc11.na.qualcomm.com ([172.30.39.6]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Jul 2014 14:02:47 -0700
Received: from NASANEXD02B.na.qualcomm.com ([169.254.2.249]) by nasanexhc11.na.qualcomm.com ([172.30.39.6]) with mapi id 14.03.0181.006; Wed, 9 Jul 2014 14:02:47 -0700
From: "Aggarwal, Ashutosh" <aaggarwa@qce.qualcomm.com>
To: "dnssd@ietf.org" <dnssd@ietf.org>
Thread-Topic: LF comments on a new document
Thread-Index: Ac+buSKBjw6KylVcT8y7xxWlLWNetg==
Date: Wed, 09 Jul 2014 21:02:46 +0000
Message-ID: <4ADFCA4A44B18946883BA96F64773E0150E101EB@NASANEXD02B.na.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.230.6]
Content-Type: multipart/alternative; boundary="_000_4ADFCA4A44B18946883BA96F64773E0150E101EBNASANEXD02Bnaqu_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/5ntLPMrLVvgT4YJe6M1kKO4Cj4A
X-Mailman-Approved-At: Thu, 10 Jul 2014 03:59:46 -0700
Cc: "Resnick, Pete" <presnick@qti.qualcomm.com>
Subject: [dnssd] LF comments on a new document
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: Wed, 09 Jul 2014 21:06:06 -0000

Dear members,

I have submitted a new draft document proposing an optimization to the DNS-SD query mechanism to make it more scalable. I have been in discussions with Dave Thaler during the formulation of the draft and would like to request for comments from the community.

Abstract:
DNS-SD allows a client to find a list of named instances of a service
 name over a particular transport within a domain of interest using
 standard DNS queries.  As the number of potential responders
 increases, DNS-SD based discovery doesn't scale well.  To mitigate
 the scaling issues, schemes to narrow down the search context would
 be needed.  The document proposes to include key/value pairs in the
 form of a DNS TXT record along with the service name in the DNS query
 to assist with the discovery process.  The DNS TXT record can be
 placed in the additional section of the query without requiring any
 changes to the structure of DNS messages.

Link to the document:
http://datatracker.ietf.org/doc/draft-aggarwal-dnssd-optimize-query/

Thanks,
Ashutosh