Re: [dnsext] SRV and wildcard CNAME

Phillip Hallam-Baker <hallam@gmail.com> Mon, 21 February 2011 13:31 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DBB2D3A6FCF; Mon, 21 Feb 2011 05:31:30 -0800 (PST)
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 291C83A6FCF for <dnsext@core3.amsl.com>; Mon, 21 Feb 2011 05:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.549
X-Spam-Level:
X-Spam-Status: No, score=-3.549 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YdMYCu8vGwJz for <dnsext@core3.amsl.com>; Mon, 21 Feb 2011 05:31:28 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id DD74A3A6F99 for <dnsext@ietf.org>; Mon, 21 Feb 2011 05:31:27 -0800 (PST)
Received: by iwl42 with SMTP id 42so3022696iwl.31 for <dnsext@ietf.org>; Mon, 21 Feb 2011 05:32:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=DUrlgjHex/SG+aj30Tz1KkloRbSc1iHj3TxKWnzG6aM=; b=SbFC0KMu5PfM87fFpLfg3lwsjaA48HFeyE9AIuwPxaeyRBlAMfJBHHUgUJXxv6mllZ pCvYFAHugm3DpIvZSp6vhp8HaHjg9GAvOPrgxD05kv+TyoaOTGGoIEQHz5r3hE+TkuRM 1yrN3i6HCDIo346oTAV/I6cYPBYtTwTqyqSsw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=keMpDqyLwvfspvTm2FwrGv/+QUsyqAHPlKyHS4toMxK5z0FbfkPO0ChY+UOXBeeWbp cHu9c9DtJKB8f7bDCt0BmsexlEjs6FfuzXIrFJBppPd2lpaviSQROeYhVE1NV/UyR7Gm Rd8FSZfDH94cyVJDjTDYYPQTugmad/e9hZvG8=
MIME-Version: 1.0
Received: by 10.42.223.70 with SMTP id ij6mr1964534icb.70.1298295129384; Mon, 21 Feb 2011 05:32:09 -0800 (PST)
Received: by 10.42.211.138 with HTTP; Mon, 21 Feb 2011 05:32:09 -0800 (PST)
In-Reply-To: <4D61EE10.6050309@necom830.hpcl.titech.ac.jp>
References: <20110216032120.43474.qmail@joyce.lan> <alpine.LSU.2.00.1102161143180.5244@hermes-1.csi.cam.ac.uk> <20110216212930.57D64A3F344@drugs.dv.isc.org> <4D5D24F3.70206@gis.net> <20110217231720.1FCF3A49096@drugs.dv.isc.org> <4D5E08E4.8060106@necom830.hpcl.titech.ac.jp> <AANLkTikjBvndD91q1jQeU9Q45qZyJbBs8t_wZkFezSfa@mail.gmail.com> <4D61B702.7060902@necom830.hpcl.titech.ac.jp> <20110221011731.F0FE0A6B00F@drugs.dv.isc.org> <4D61C45E.7000506@necom830.hpcl.titech.ac.jp> <20110221022950.BE88CA6B2DD@drugs.dv.isc.org> <4D61D194.9040804@necom830.hpcl.titech.ac.jp> <4D61D350.9040401@maxqe.com> <4D61E272.1050600@necom830.hpcl.titech.ac.jp> <AANLkTik8YQYd82vYt6A_j+gDBBSmntju+xh5BQeTX+H5@mail.gmail.com> <4D61EE10.6050309@necom830.hpcl.titech.ac.jp>
Date: Mon, 21 Feb 2011 05:32:09 -0800
Message-ID: <AANLkTim=T3z6uzbFVRK9pJzHgtsuLtTnBfHwaTHjB2f2@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: dnsext@ietf.org
Subject: Re: [dnsext] SRV and wildcard CNAME
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0976191809=="
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

2011/2/20 Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>

> Phillip Hallam-Baker wrote:
>
> >>> When the protocols used at the domain are http and https only,
> >>> nothing break.
>
> > Mark is quite correct here.
>
> Neither your example "_null._random.example.com" nor Mark's
> example "_foo._tcp.bar.example.com" is applicable to the case
> of "protocols used at the domain are http and https only",
> because you are assuming protocols "null" or "foo" is used
> at the domain.
>
> > In other words the domain is advertising
> > services it does not support, this is a failure for a discovery
> mechanism.
>
> That's fine.
>
> Lazy users do not mind if they advertise non existent services.
>


But competent people mind a very great deal. If the client is attempting to
discover which GPS protocols are supported at a site and choose the best,
the wildcard scheme fails because it will advertise everything as being on
offer.

Now I do have some experience in Web Services that is rather relevant here.


Like many protocol design issues, these are very easy if you only deal with
some of the use cases. They become much harder when you actually take into
account all the constraints.


-- 
Website: http://hallambaker.com/
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext