Re: [apps-discuss] Looking at Webfinger

John Bradley <ve7jtb@ve7jtb.com> Tue, 11 September 2012 15:49 UTC

Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 629DB21F87AB for <apps-discuss@ietfa.amsl.com>; Tue, 11 Sep 2012 08:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Level:
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id amuytOWFX7aA for <apps-discuss@ietfa.amsl.com>; Tue, 11 Sep 2012 08:49:38 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 57EF521F87A8 for <apps-discuss@ietf.org>; Tue, 11 Sep 2012 08:49:38 -0700 (PDT)
Received: by yenm5 with SMTP id m5so121427yen.31 for <apps-discuss@ietf.org>; Tue, 11 Sep 2012 08:49:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=NkLghtdmP1sUB7bm6d9qEL6kX1l/5wskO65eiZRng7o=; b=WOXHkYO4q8HZx7BRWJTD9AwKwLFXBxBy0d4Xs4ywjJ4H048AYId1Q+UcCV7hiJHIxY pJpz7M9qPrrmJCX0JMUxOTh0bd0PUymy69lkb76LN4T+5fwx8a2Psh9EKlQF4q2674eZ fIGSZc19T5IVNPZuDpfd4XBWsZKnvVUFGWsJ8QxPY598ZyoWGuC3VkngbZqJtHsMvtPQ fPQsgvDjCtJyJXsps3qFUDcDRL8VcclT8HEbWgNlI956LD0phXL4TZSO7RUc0AkgMm4P xRtEJ9XWmfc5tMnPEsMHi9BJ+JcRH0UHpZ4AUwL0Bhh3uWAszoAJXx7eBtkpZWu7+ygM 9vPQ==
Received: by 10.236.108.194 with SMTP id q42mr16520546yhg.3.1347378577651; Tue, 11 Sep 2012 08:49:37 -0700 (PDT)
Received: from [192.168.1.211] ([190.20.45.140]) by mx.google.com with ESMTPS id i3sm14704809anl.0.2012.09.11.08.49.29 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Sep 2012 08:49:35 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_E2F8ADCD-07F1-4C32-A7D4-52BA3720ACBB"; protocol="application/pkcs7-signature"; micalg="sha1"
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <CABzCy2BTcr0FZK7i-UmzUkLonYS3NOgtxzXM5zm51+bdUPU-sQ@mail.gmail.com>
Date: Tue, 11 Sep 2012 12:49:22 -0300
Message-Id: <EE204055-91B0-4A30-B27D-C001814EDE98@ve7jtb.com>
References: <F80C8C9C-7AB8-4B7E-BFD2-4D69499D21A1@mnot.net> <4E1F6AAD24975D4BA5B168042967394366574F93@TK5EX14MBXC283.redmond.corp.microsoft.com> <CABP7RbfNXx8HtsRBcVf=AVaDTyg=xQYHWAyCkHWx1n+JBQ8=Zw@mail.gmail.com> <CAMm+Lwg20rfr=P66=vZadL8Ga5KDXmfizZE5v6dXiZMTvZKY=Q@mail.gmail.com> <44C43601-A355-44B7-8C8E-1F435E4E567A@ve7jtb.com> <CAMm+LwgM57++oqE-5meECxE0S=kU2kVHJLumyDSBciJ13QvuoA@mail.gmail.com> <CABP7RbctkibSKr6r_Ay34z4Wr67tU6qG5G5gLCZovGx_hWYHYQ@mail.gmail.com> <DF4591C5-A5AE-4D2A-BB3A-FF4DAFBBD98A@ve7jtb.com> <CABP7RbefS9Sy2m0GsiSx2VZopf78DhqU1fjfsDn5z926Q_--GA@mail.gmail.com> <CAJu8rwUeAKEtAS-g6X3xJqyu-Xy6yQnfdeNj3mGC__D3zijwzA@mail.gmail.com> <35550AA9-E003-4917-B08C-93CB6CC2CB07@mnot.net> <CAJu8rwWKa7ehr+k=zDWD=OMzPTEt56inPW0tvZaNUmdcL3ygoQ@mail.gmail.com> <503CDF26.8050000@aol.com> <02a301cd8551$be7ab390$3b701ab0$@packetizer.com> <3BE24613-9CA0-4B2C-AB33-274026D534FB@ve7jtb.com> <032d01cd8597$aac7f740$0057e5c0$@packetizer.com> <CAJu8rwX=F8o8U2tv3vJbL+p2dnGVGDtccKOk+ ukn4jtSXNwDxg@mail.gmail.com> <04f001cd8627$092727e0$1b7577a0$@packetizer.com> <90420743-8FE8-4EDB-98EF-D717D5346397@frobbit.se> <1346306587.53748.YahooMailNeo@web31804.mail.mud.yahoo.com> <E5BBDB94-2D62-4A35-860A-22A466F88F5F@frobbit.se> <251A4741-1E52-41D3-B4C8-43BEDE5C79B7@ve7jtb.com> <CABzCy2BTcr0FZK7i-UmzUkLonYS3NOgtxzXM5zm51+bdUPU-sQ@mail.gmail.com>
To: Nat Sakimura <sakimura@gmail.com>
X-Mailer: Apple Mail (2.1486)
X-Gm-Message-State: ALoCoQmdtwlOxj2zDhYL6us789+TuPLr/EoxLkoJRFBURhRGeyQNCaGAJr1XA1iDnTeBBwddpqHU
Cc: Mark Nottingham <mnot@mnot.net>, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Looking at Webfinger
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 15:49:39 -0000

Nat,

TuCows supports SRV records at least for openSRS.   Some of there resellers may be using other things to manage DNS recodes and just using them for registration, so it would be hard to make a blanket statement.

I think using a SRV record introduces other security issues that would have to be looked at without DNSsec.

John B.

On 2012-08-31, at 11:19 PM, Nat Sakimura <sakimura@gmail.com> wrote:

> I think it is not the problem of the clients. Any decent scripting
> language has the ability to query SRV records in DNS.
> 
> It is the problem of the DNS service provider, which always have GUI
> for A and CNAME records but not necessarily TXT or SRV records.
> 
> Having said that, have we done the reality check on the above claim
> that those providers do not support them? Quick check reveals the
> following about top domain registrar's support SRV records (market
> share is from http://collegefallout.com/list-of-top-10-domain-name-registrars/
> which may not be correct) :
> 
> - Regstrar Name (market share) Support of SRV record
> 
> - GoDaddy (31%)YES
> - enom.com (8.5%) YES
> - TuCows (6.6%) ???
> - NetworkSolutions (5.4%) YES
> - Schlund+Partner (4.3%) NO
> - melbourneit (3.6%) NO
> - Wild West Domains (2.8%) YES
> - moniker.com (2.4%) ???
> - ResellerClub (2.2%) YES
> - REGISTER.com (2.0%) YES
> 
> It is actually better than I thought. The world may be changing...
> 
> Nat
> 
> 
> On Fri, Aug 31, 2012 at 6:00 AM, John Bradley <ve7jtb@ve7jtb.com> wrote:
>> I agree that doing it via DNS would be the proper way.
>> 
>> The reality is that not all clients can easily access DNS directly.  Doing anything more than a http get reduces adoption.
>> 
>> Not all DNS providers support srv records.  I think your draft on DNS records has expired, and I know of no support for it.
>> http://tools.ietf.org/html/draft-faltstrom-uri-06
>> 
>> Something like DNS records would be the answer, I just don't think protocols like Webfinger are likely to wait for wide deployment of that as a underlying technology.
>> 
>> John B.
>> On 2012-08-30, at 2:44 AM, Patrik Fältström <paf@frobbit.se> wrote:
>> 
>>> First, I did not talk about SRV records, but URI records.
>>> 
>>> Secondly, I think it is fascinating that people that love new things like "the web" and new HTML5 features are the most conservative ones regarding other protocols like DNS.
>>> 
>>> With that attitude, we have no evolution, and no innovation.
>>> 
>>> Providers that do not support such features will die. It is that simple.
>>> 
>>>  Patrik
>>> 
>>> On 30 aug 2012, at 08:03, William Mills <wmills@yahoo-inc.com> wrote:
>>> 
>>>> There are a few folks that feel that SRV records are not really an option for hosting situatiosn where the users don't currently have the ability to configure SRV records.
>>>> 
>>>> From: Patrik Fältström <paf@frobbit.se>
>>>> To: Paul E. Jones <paulej@packetizer.com>
>>>> Cc: 'Mark Nottingham' <mnot@mnot.net>; 'IETF Apps Discuss' <apps-discuss@ietf.org>
>>>> Sent: Wednesday, August 29, 2012 8:01 PM
>>>> Subject: Re: [apps-discuss] Looking at Webfinger
>>>> 
>>>> On 29 aug 2012, at 22:44, Paul E. Jones <paulej@packetizer.com> wrote:
>>>> 
>>>>> 1) TXT records (e.g., _webfinger.packetizer.com IN TXT “https://packetizer.webfinger-provider.com/”)
>>>> 
>>>> Please see URI Resource Record, for example:
>>>> 
>>>> _webfinger._tcp.packetizer.com. IN URI 0 0 “https://packetizer.webfinger-provider.com/”
>>>> 
>>>> Patrik
>>>> 
>>>> _______________________________________________
>>>> apps-discuss mailing list
>>>> apps-discuss@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> apps-discuss mailing list
>>> apps-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>> 
>> 
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>> 
> 
> 
> 
> -- 
> Nat Sakimura (=nat)
> Chairman, OpenID Foundation
> http://nat.sakimura.org/
> @_nat_en