Re: [dnsext] we need help to make names the same, was draft-yao-dnsext-identical-resolution-02 comment

Patrik Fältström <paf@cisco.com> Fri, 18 February 2011 07:18 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 8ECA13A6D4F; Thu, 17 Feb 2011 23:18:32 -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 D0CD53A69D0 for <dnsext@core3.amsl.com>; Thu, 17 Feb 2011 23:18:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.939
X-Spam-Level:
X-Spam-Status: No, score=-9.939 tagged_above=-999 required=5 tests=[AWL=0.359, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, WEIRD_PORT=0.001]
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 aTmfMf3ew1L0 for <dnsext@core3.amsl.com>; Thu, 17 Feb 2011 23:18:30 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 925BE3A6CE5 for <dnsext@ietf.org>; Thu, 17 Feb 2011 23:18:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=paf@cisco.com; l=964; q=dns/txt; s=amsiport01001; t=1298013544; x=1299223144; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Uc5Jp8hioHyrkWVD5dIEjEyNw9Z8v785IZN5DVkmP+I=; b=ACkzo22TvINav1KDlkHpk7tb9t+h+Lcr3Lo7HsnchCQrqs3Bc6hu+kEa X7NJIe2vNdjZ2Zc/DBfi1cnHNWJtNeacEv70jW89GsvijUJ87/xVCLU6E Lx8Q+G8cwfEJmNqF0XzlBIb76OAjsAGwJSZfUjQ1QI6sNbS7p7cKOZ+tI o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEEAKqsXU2Q/khLgWdsb2JhbACmIBUBARYiJKBumzeFXgSMEYwE
X-IronPort-AV: E=Sophos;i="4.62,185,1297036800"; d="scan'208";a="76645105"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 18 Feb 2011 07:18:55 +0000
Received: from dhcp-10-61-107-153.cisco.com (dhcp-10-61-107-153.cisco.com [10.61.107.153]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p1I7ItSg025491; Fri, 18 Feb 2011 07:18:55 GMT
Mime-Version: 1.0 (Apple Message framework v1082)
From: Patrik Fältström <paf@cisco.com>
In-Reply-To: <4D5E1704.4030905@necom830.hpcl.titech.ac.jp>
Date: Fri, 18 Feb 2011 08:18:54 +0100
Message-Id: <B87CE68E-64CA-4E08-B00E-11A62BB5029C@cisco.com>
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> <A0714F29-3676-4142-9A99-C350ED28A3B9@cisco.com> <4D5E1704.4030905@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
X-Mailer: Apple Mail (2.1082)
Cc: dnsext@ietf.org
Subject: Re: [dnsext] we need help to make names the same, was draft-yao-dnsext-identical-resolution-02 comment
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

On 18 feb 2011, at 07.51, Masataka Ohta wrote:

> wrote:
> 
>> I just saw an acceptance of the by me suggested URI RR-Type, and
>> this is one of the usages I was thinking of, although it was
>> not a "main goal".
>> 
>> For example:
>> 
>> _http._tcp.example.com.  URI 1 1 http://example.hostingcompany.com/
>> _https._tcp.example.com. URI 1 1 https://example.hostingcompany.com:444/
> 
> Isn't an original request "http://example.com/filename" converted
> to "http://example.hostingcompany.com/" by URIs?

Or maybe to http://example.hostingcompany.com/filename?

And then the next question is of course what DN to compare with in the SSL cert?

And then the question is whether SRV RR should be used for example.hostingcompany.com?

I.e. what I see this discussion is boiling down to is that what I think we need is a document that clearly describe one as "simple" thing as "how to resolve a HTTP URI".

   Patrik

_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext