
From superuser@gmail.com  Sun Jul  1 20:37:48 2012
Return-Path: <superuser@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 814B211E814F for <weirds@ietfa.amsl.com>; Sun,  1 Jul 2012 20:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level: 
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=-0.847, BAYES_20=-0.74, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BMGzbLRaBTha for <weirds@ietfa.amsl.com>; Sun,  1 Jul 2012 20:37:47 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4B79D11E8140 for <weirds@ietf.org>; Sun,  1 Jul 2012 20:37:47 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so7611872lbb.31 for <weirds@ietf.org>; Sun, 01 Jul 2012 20:37:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=fAAc5ae4jdEkJ65/KqO/dJyeJQHvr6nZ7wWsByjK/xo=; b=nLDgQATOkV7x3JbVHtFrnYoFgFgUTaweAeZu8YY+Ttts1DwGlzOyzvnvpW3jA7CsPK Ajt7hJ+9uC41keFllmjXH7K1/ulPcolx4334xbxKXjHSsYacEQEvVLBirj4XmgwrRGpp HJJlsRTVCmeBqiDyAwwpr0Q6lbDle/4Vsi8iTTOdrNOGpjYaPEQsqZN0JxUUnftzwSKj lPAr5Qb2/BrvI7YFD8zSYtEksCzPykaWeyioGRYZx8QhXfc2mkgzWYY5gzhRQ0hVrx0u 88RaUL24Wd+9BFJnLv6jS1bAE1HCTBVMciIALOKMP+B2iWTvbN78TIe8TwwZgVwyy0ds 8HHQ==
MIME-Version: 1.0
Received: by 10.152.104.47 with SMTP id gb15mr11016864lab.45.1341200267661; Sun, 01 Jul 2012 20:37:47 -0700 (PDT)
Received: by 10.112.89.3 with HTTP; Sun, 1 Jul 2012 20:37:47 -0700 (PDT)
Date: Sun, 1 Jul 2012 20:37:47 -0700
Message-ID: <CAL0qLwbse3=ArBD4Y63POwO=6ybP8SaUtQkaYqcWV3JP72JKsQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: weirds@ietf.org
Content-Type: multipart/alternative; boundary=f46d0421824d86d00c04c3d0859b
Subject: [weirds] WEIRDS WG meeting scheduled
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 03:37:48 -0000

--f46d0421824d86d00c04c3d0859b
Content-Type: text/plain; charset=ISO-8859-1

We have been scheduled for a 2.5 hour session Wednesday, from 9am-11:30am,
in room "Regency F".

See you all there!

-- your friendly neighbourhood WEIRDS co-chairs

--f46d0421824d86d00c04c3d0859b
Content-Type: text/html; charset=ISO-8859-1

We have been scheduled for a 2.5 hour session Wednesday, from 9am-11:30am, in room &quot;Regency F&quot;.<br><br>See you all there!<br><br>-- your friendly neighbourhood WEIRDS co-chairs<br><br>

--f46d0421824d86d00c04c3d0859b--

From superuser@gmail.com  Sun Jul  1 20:39:48 2012
Return-Path: <superuser@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EF9E21F8565 for <weirds@ietfa.amsl.com>; Sun,  1 Jul 2012 20:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.497
X-Spam-Level: 
X-Spam-Status: No, score=-3.497 tagged_above=-999 required=5 tests=[AWL=0.101,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ls2LHjsr85FM for <weirds@ietfa.amsl.com>; Sun,  1 Jul 2012 20:39:48 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id D846821F8559 for <weirds@ietf.org>; Sun,  1 Jul 2012 20:39:47 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so7613179lbb.31 for <weirds@ietf.org>; Sun, 01 Jul 2012 20:39:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=m65UF88xgN7Y3kLivAd7ps0x89BC1K2+wHZg7mQX6kg=; b=ty0HiOsF4ZqmQjfvEoO2uCdaJig5umCvMBa9Yu+zOGDHP2R+MLa5bJmmn+Fnxn++ym /vP72EjrMZcRipZW5JEP7LQ1VAwMraXUmBTsfPoZIrsu4xbAK+C5tcinxioYLuQWgpY6 O5bKZTnG5wMmOzZ/gd3wKYxaPF+6u/xVI9EgHB71Pmx9f6EUTrzttOxpHxhFVB0wUaad Nm4tNbNX6B6Q7KZJiK7zlZUwxvPNdUenP2/KMcdDdnnHN7Sw7iu6Q/PadDHPsHfHJGZo QgDI1W1hj0dFBUCDr/mkiTM5aKyYwUjfzkjQA1Ab3Y96IFus+iOSJO8SY7Co08Rz7zHi o6Zg==
MIME-Version: 1.0
Received: by 10.152.112.233 with SMTP id it9mr11018412lab.40.1341200390863; Sun, 01 Jul 2012 20:39:50 -0700 (PDT)
Received: by 10.112.89.3 with HTTP; Sun, 1 Jul 2012 20:39:50 -0700 (PDT)
In-Reply-To: <55DAEBB6-6911-4F52-AB98-8F66FBA84F6E@nlnetlabs.nl>
References: <55DAEBB6-6911-4F52-AB98-8F66FBA84F6E@nlnetlabs.nl>
Date: Sun, 1 Jul 2012 20:39:50 -0700
Message-ID: <CAL0qLwYEe3T2SOooj4tGuAc8vD_qoXgY8S4Zh6RoDqy-X5c7zQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Olaf Kolkman <olaf@nlnetlabs.nl>
Content-Type: multipart/alternative; boundary=f46d040838d3debcb004c3d08c2f
Cc: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Subject: Re: [weirds] FYI: Weirds WG slot at IETF84
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 03:39:48 -0000

--f46d040838d3debcb004c3d08c2f
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Jun 29, 2012 at 1:36 AM, Olaf Kolkman <olaf@nlnetlabs.nl> wrote:

> The weirds WG session is scheduled for:
> Wednesday, Morning Session I 0900-1130
> Room Name: Regency F
>
>
Sorry, I only saw this after sending my note.  Carry on. :-)

-MSK

--f46d040838d3debcb004c3d08c2f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 29, 2012 at 1:36 AM, Olaf Kolkman <span dir=3D"ltr">&lt;<a href=
=3D"mailto:olaf@nlnetlabs.nl" target=3D"_blank">olaf@nlnetlabs.nl</a>&gt;</=
span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The weirds WG session is scheduled for:<br>
Wednesday, Morning Session I 0900-1130<br>
Room Name: Regency F<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br>Sorry, I only saw this after sending my note.=A0 Carry on. :-)<=
br><br>-MSK <br></div></div><br>

--f46d040838d3debcb004c3d08c2f--

From avri@acm.org  Tue Jul  3 15:19:26 2012
Return-Path: <avri@acm.org>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E12E821F86AA for <weirds@ietfa.amsl.com>; Tue,  3 Jul 2012 15:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.288
X-Spam-Level: 
X-Spam-Status: No, score=-106.288 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g3bo-hWbsAhH for <weirds@ietfa.amsl.com>; Tue,  3 Jul 2012 15:19:26 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 47E7521F864D for <weirds@ietf.org>; Tue,  3 Jul 2012 15:19:26 -0700 (PDT)
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1]) by psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <avri@acm.org>) id 1SmBRW-000GEP-Uw for weirds@ietf.org; Tue, 03 Jul 2012 22:19:35 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
From: Avri Doria <avri@acm.org>
In-Reply-To: <4FDB2BFB.9020602@mnt.se>
Date: Tue, 3 Jul 2012 18:19:33 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <AE4733AB-540C-4AFF-8489-ABA404CC0884@acm.org>
References: <C0EA2C65-78A2-4960-B727-4E50627F942E@NLnetLabs.nl> <58F25160-28BC-4F35-BE96-5AC22D35BF00@hxr.us> <4FDB2BFB.9020602@mnt.se>
To: weirds@ietf.org
X-Mailer: Apple Mail (2.1278)
Subject: Re: [weirds] For transparency purposes.
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2012 22:19:27 -0000

+1

On 15 Jun 2012, at 08:35, Leif Johansson wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 06/15/2012 02:22 PM, Andy Newton wrote:
>> Involvement of NLnet Labs and SIDN, especially from an
>> implementation perspective, is a good thing in my opinion. And I
>> trust Olaf to compartmentalize his roles.
> 
> yep
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iEYEARECAAYFAk/bK/sACgkQ8Jx8FtbMZncJKwCeK++vqjRRZ6bFN2qfWwjZjNdU
> vHcAnjdO2D9/9TWfi/f9VFud9FxDAp9g
> =sXAf
> -----END PGP SIGNATURE-----
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds
> 


From carlosm3011@gmail.com  Fri Jul  6 09:11:14 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2947B21F866D for <weirds@ietfa.amsl.com>; Fri,  6 Jul 2012 09:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fBWJwpAHoOPV for <weirds@ietfa.amsl.com>; Fri,  6 Jul 2012 09:11:13 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 366A921F87A9 for <weirds@ietf.org>; Fri,  6 Jul 2012 09:11:13 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so9630293ggn.31 for <weirds@ietf.org>; Fri, 06 Jul 2012 09:11:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=FggilnLwC++ipyYhiy/lDMVRkwXP6Qaz/jMfl0QO7DE=; b=bl3b4qzgzkeCVQuTZVj7r7XKuK2Ao0uHOVCBA+uuONpfO+WXdJopIaT589u6TmRj4U 8E/ZAqwGIm8TVo7vXfEpTPMpdXKqllGjVGl8w68+glhqubYMc0OSJXOPO035273vn3Ym J9uI/0DhiEQ3ruIhuKXRWNmNWJCM+2kGWSb9wytuKfURFAGtSXig5rwecbFb3xYL7GC6 4sbA4viSRpTheJNUmMYt3fcCjs470YMc4YCwrze45mAsnib2T8gnpYDun81Zb3XP2hUR KhIFrQ8dK/R/6SUWMj9I7pEOUu963b7Z1eceFwGzMWvUcW4UFNLCbZYXRzRpeOUDbEJ/ jfBg==
Received: by 10.236.109.229 with SMTP id s65mr36510555yhg.10.1341591089444; Fri, 06 Jul 2012 09:11:29 -0700 (PDT)
Received: from pandora.local ([2001:13c7:7001:5128:c5b4:b134:760e:62ee]) by mx.google.com with ESMTPS id a64sm48171664yhe.11.2012.07.06.09.11.26 (version=SSLv3 cipher=OTHER); Fri, 06 Jul 2012 09:11:28 -0700 (PDT)
Message-ID: <4FF70E2C.9070104@gmail.com>
Date: Fri, 06 Jul 2012 13:11:24 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "<weirds@ietf.org>" <weirds@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 16:11:14 -0000

Hello all,

We submitted a few weeks ago a weirds document
(draft-lacnic-weirds-restwhois-redirects [1]) that documents a piece of
running code we wrote at LACNIC that performs single-point redirection
of RESTful WHOIS queries. The intent of the document, besides
documenting running code, was to spur discussion on the topic of redirects.

At this point, and with the -00 deadline fast approaching, I'll try to
summarize the different view points and possible ways forward.

In any redirection scheme at least one server needs to have a database
that maps resources to authoritative WEIRDS servers, as "200/8 =>
lacnic_weirds, 1/8 => apnic_weirds", etc. There are at least two
possible approaches, one with a set of central redirect-only servers and
a mesh, flat model where weirds servers directly redirect to each other.

Our prototype ([1], [2]) implements the hierarchical model and the
database is fed from IANA's IPv4, IPv6 and ASN registries. We are aware
of the limitations of this approach, mostly in the case of IPv4, but as
this work is intended only to be a quick proof-of-concept this provided
a quick and painless way to build the db.

So, here are the open issues:

1- Is the topic of building the mapping database in the scope of the WG
? We did this for numbers but we must also consider the case of names.

2- Do the hierarchical vs mesh model alternatives need to be documented ?

3- Does the topic need its own draft(s) ?

>From feedback I've received, if the answer to (1) is 'no' then the topic
of redirects should probably be included as simple section (return 30x
pointing to such and such in case of  in other document, probably in the
HTTP draft. If, on the other hand, the answer to (1) is 'yes', then
there is a lot of ground to cover in a one or perhaps, two, documents
(names and numbers) 

Share your thoughts!

Warm regards

Carlos

[1]
http://tools.ietf.org/html/draft-lacnic-weirds-restwhois-redirects-00.txt
[2] http://www.labs.lacnic.net/site/restful-whois (in Spanish, but links
work anyways)

From johnl@iecc.com  Fri Jul  6 16:19:53 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D058B21F8596 for <weirds@ietfa.amsl.com>; Fri,  6 Jul 2012 16:19:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.113
X-Spam-Level: 
X-Spam-Status: No, score=-111.113 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwCK3c7vxS+i for <weirds@ietfa.amsl.com>; Fri,  6 Jul 2012 16:19:53 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id D104E21F8595 for <weirds@ietf.org>; Fri,  6 Jul 2012 16:19:52 -0700 (PDT)
Received: (qmail 9015 invoked from network); 6 Jul 2012 23:20:07 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 6 Jul 2012 23:20:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ff772a7.xn--i8sz2z.k1207; i=johnl@user.iecc.com; bh=qW53xgaP8nLzdJyV4SlVYZ9QTmp8b45NlTJUUdWhaxY=; b=CvrjPC3HSRnCvAU85wWX1XWcCGYLs3cmXFvMfk8ThpzWCIPcEUJdL1i3dZ6EfpwC65AVR1Yz0dIEtXolbRox8x6sxgzMqV4ubJ4Rg9N+g6cZ7mntgh3GYjdAxNOuQH2rbArxgW0TLXGD/KmQTMUdGLnR5bCItaim5K/zq1h/BQA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ff772a7.xn--i8sz2z.k1207; olt=johnl@user.iecc.com; bh=qW53xgaP8nLzdJyV4SlVYZ9QTmp8b45NlTJUUdWhaxY=; b=cEgXWOyPn3dnNuRy4qGkqg2toHjX5O/38LK62AFJBq3mfiriRk5meoKwI4rHVHTRsvjsSL5Gd8vcdjxFdDaNzySIsz1b/lh3LlB70h/tzMF1akdVbm5pW+sW4AjfC2fdmPGdAO0bFcyQ2NKYvgirZa7skafeVnZWDbrViArzwYk=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 6 Jul 2012 23:19:45 -0000
Message-ID: <20120706231945.92055.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <4FF70E2C.9070104@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 23:19:54 -0000

>1- Is the topic of building the mapping database in the scope of the WG
>? We did this for numbers but we must also consider the case of names.
>
>2- Do the hierarchical vs mesh model alternatives need to be documented ?
>
>3- Does the topic need its own draft(s) ?

I don't think it would be a good idea to try to build a top level map
into the spec.  For both names and numbers, the data for a top level
map resides (or reasonably would reside) at IANA, but this group can't
tell IANA what to do.

Also, for names, one could imagine some kludges to bootstrap the map.
A totally unofficial but widely used hack is whois-servers.net, who
publish CNAMES as <tld>.whois-servers.net that point at the servers
for all the TLD WHOIS servers they know.  It's a kludge, but I
wouldn't rule something like that out, since it's a lot lower overhead
than a top level WHOIS server that would likely get a zillion hits
every second.

And of course in the number space the two models coexist, due
to legacy delegations.  Just document the 30x redirect and note
that there has to be some way to pick an initial server for
a query.

R's,
John



From superuser@gmail.com  Sat Jul  7 19:59:00 2012
Return-Path: <superuser@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8033321F8596 for <weirds@ietfa.amsl.com>; Sat,  7 Jul 2012 19:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.554
X-Spam-Level: 
X-Spam-Status: No, score=-3.554 tagged_above=-999 required=5 tests=[AWL=0.044,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cODUTX5IHM-9 for <weirds@ietfa.amsl.com>; Sat,  7 Jul 2012 19:58:59 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 20D1521F855B for <weirds@ietf.org>; Sat,  7 Jul 2012 19:58:58 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so16048709lbb.31 for <weirds@ietf.org>; Sat, 07 Jul 2012 19:59:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=pIm2p+hTyHagV3zevAFTJmBLwTcUV5BXMHvFYzz0wo0=; b=t8IIwgCAC3JnBLChCp0lfQwAdPwEsqqqiTuuYUbAGQhImzFD8EBMoG2is652S4Rz1F DbXNqM6DUOUL701WmvRAXRA8uj72qUhegFqBGjC9AA1jgqfojVslWRK/Of0Iz5apExkL h3qIA4kkLz/uAv/AeCXMof38yPoVxZzmur6ESyTx4pjB6plg7D1fQ2kQrmZX8uUEiIHk HM2l+iqvgY5YpirHT8Us+kLzHIZ0a46CdhKoo55GjzmBPEr7ThZTgxwehoxZV7U1ciSr hJJv1k3Rpynv4BSboeSo7tA+wb3+l2DBdfjRsc+MSoDK9VMG4Z/wyWDmIfgxe+C6SfUd rIEQ==
MIME-Version: 1.0
Received: by 10.112.49.100 with SMTP id t4mr16000992lbn.10.1341716358916; Sat, 07 Jul 2012 19:59:18 -0700 (PDT)
Received: by 10.112.89.3 with HTTP; Sat, 7 Jul 2012 19:59:18 -0700 (PDT)
In-Reply-To: <20120706211533.3449.10225.idtracker@ietfa.amsl.com>
References: <20120706211533.3449.10225.idtracker@ietfa.amsl.com>
Date: Sat, 7 Jul 2012 19:59:18 -0700
Message-ID: <CAL0qLwb4UaFc9wkhwUJX-f=aSLgRjQ9Us_Ghuj+RRr5Hv4Wbfw@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: weirds@ietf.org
Content-Type: multipart/alternative; boundary=bcaec554d63cf66a9804c448aec8
Subject: [weirds] Fwd: NomCom 2012-13 Call for Volunteers
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Jul 2012 02:59:00 -0000

--bcaec554d63cf66a9804c448aec8
Content-Type: text/plain; charset=ISO-8859-1

---------- Forwarded message ----------
From: NomCom Chair <nomcom-chair@ietf.org>
Date: Fri, Jul 6, 2012 at 2:15 PM
Subject: NomCom 2012-13 Call for Volunteers
To: IETF Announcement List <ietf-announce@ietf.org>


The IETF nominating committee process for 2012-13 has begun. The IETF
nominating committee appoints folks to fill the open slots on the
IAOC, the IAB, and the IESG. The 10 nominating committee members are
selected randomly from a pool of volunteers. The more volunteers, the
better chance we have of choosing a random yet representative cross
section of the IETF population.  The details of the operation of the
nomcom can be found in RFC 3777.

To be eligible, volunteers for the nomcom need to have attended 3 of
the past 5 IETF meetings as of the time this announcement goes out.
That is, 3 meetings from IETF 79 (Beijing) - IETF 83 (Paris). If you
qualify, and if you will not be seeking appointment to any of the open
positions that this nomcom will be filling, please consider
volunteering.

The list of people whose terms end with the March 2013 IETF meeting,
and thus the positions for which the nominating committee is
responsible for filling, are as follows:

IAOC:
--------
Dave Crocker

IAB:
--------
Alissa Cooper
Joel Halpern
David Kessens
Danny McPherson
Jon Peterson
Dave Thaler

IESG:
--------
Russ Housley (General Area)
Pete Resnick (Applications Area)
Ralph Droms (Internet Area)
Ronald Bonica (Operations and Management Area)
Robert Sparks (Real-Time Applications and Infrastructure Area)
Adrian Farrel (Routing Area)
Stephen Farrell (Security Area)
Wesley Eddy (Transport Area)

The primary activity for this nomcom will begin in August 2012 and
should be completed in January 2013. The nomcom will be collecting
requirements from the community, as well as talking to candidates and
obtaining feedback from community members about candidates. There will
be regularly scheduled conference calls to ensure progress. Thus,
being a nomcom member does require some time commitment.

Please volunteer by sending an email before 11:59 pm EDT (UTC - 4
hours) August 5, 2012 as follows:

To: mlepinski.ietf@gmail.com
Subject: Nomcom 2012-13 Volunteer

Please include the following information in the body:

<Your Full Name>  // As you enter in the IETF Registration Form,
                    // First/Given name followed by Last/Family Name
<Current Primary Affiliation>
                // typically what goes in the Company field
                //  in the IETF Registration Form
[<all email addresses used to Register for the past 5 IETF meetings>]
<Preferred email address>  //
<Telephone number>         // For confirmation if selected

Please expect an email response from me within 3 business days stating
whether or not you are qualified.  If you don't receive a response,
please re-send your email with the tag "RESEND:" added to the subject
line.

If you are not yet sure you would like to volunteer, please consider
that nomcom members play a very important role in shaping the
leadership of the IETF.  Ensuring the leadership of the IETF is fair
and balanced and comprised of those who can lead the IETF in the right
direction is an important responsibility that rests on the IETF
participants at large. Volunteering for the nomcom is a good way of
contributing toward that goal.

I will be publishing a more detailed timetable for nomcom activities,
as well as details of the randomness seeds to be used for the RFC 3797
selection process, within the next couple weeks.

Thank you,
Matthew Lepinski
mlepinski.ietf@gmail.com
nomcom-chair@ietf.org

--bcaec554d63cf66a9804c448aec8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">---------- Forwarded message ----------<=
br>From: <b class=3D"gmail_sendername">NomCom Chair</b> <span dir=3D"ltr">&=
lt;<a href=3D"mailto:nomcom-chair@ietf.org">nomcom-chair@ietf.org</a>&gt;</=
span><br>
Date: Fri, Jul 6, 2012 at 2:15 PM<br>Subject: NomCom 2012-13 Call for Volun=
teers<br>To: IETF Announcement List &lt;<a href=3D"mailto:ietf-announce@iet=
f.org">ietf-announce@ietf.org</a>&gt;<br><br><br>The IETF nominating commit=
tee process for 2012-13 has begun. The IETF<br>

nominating committee appoints folks to fill the open slots on the<br>
IAOC, the IAB, and the IESG. The 10 nominating committee members are<br>
selected randomly from a pool of volunteers. The more volunteers, the<br>
better chance we have of choosing a random yet representative cross<br>
section of the IETF population. =A0The details of the operation of the<br>
nomcom can be found in RFC 3777.<br>
<br>
To be eligible, volunteers for the nomcom need to have attended 3 of<br>
the past 5 IETF meetings as of the time this announcement goes out.<br>
That is, 3 meetings from IETF 79 (Beijing) - IETF 83 (Paris). If you<br>
qualify, and if you will not be seeking appointment to any of the open<br>
positions that this nomcom will be filling, please consider<br>
volunteering.<br>
<br>
The list of people whose terms end with the March 2013 IETF meeting,<br>
and thus the positions for which the nominating committee is<br>
responsible for filling, are as follows:<br>
<br>
IAOC:<br>
--------<br>
Dave Crocker<br>
<br>
IAB:<br>
--------<br>
Alissa Cooper<br>
Joel Halpern<br>
David Kessens<br>
Danny McPherson<br>
Jon Peterson<br>
Dave Thaler<br>
<br>
IESG:<br>
--------<br>
Russ Housley (General Area)<br>
Pete Resnick (Applications Area)<br>
Ralph Droms (Internet Area)<br>
Ronald Bonica (Operations and Management Area)<br>
Robert Sparks (Real-Time Applications and Infrastructure Area)<br>
Adrian Farrel (Routing Area)<br>
Stephen Farrell (Security Area)<br>
Wesley Eddy (Transport Area)<br>
<br>
The primary activity for this nomcom will begin in August 2012 and<br>
should be completed in January 2013. The nomcom will be collecting<br>
requirements from the community, as well as talking to candidates and<br>
obtaining feedback from community members about candidates. There will<br>
be regularly scheduled conference calls to ensure progress. Thus,<br>
being a nomcom member does require some time commitment.<br>
<br>
Please volunteer by sending an email before 11:59 pm EDT (UTC - 4<br>
hours) August 5, 2012 as follows:<br>
<br>
To: <a href=3D"mailto:mlepinski.ietf@gmail.com">mlepinski.ietf@gmail.com</a=
><br>
Subject: Nomcom 2012-13 Volunteer<br>
<br>
Please include the following information in the body:<br>
<br>
&lt;Your Full Name&gt; =A0// As you enter in the IETF Registration Form,<br=
>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 // First/Given name followed by Las=
t/Family Name<br>
&lt;Current Primary Affiliation&gt;<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 // typically what goes in the Company field=
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 // =A0in the IETF Registration Form<br>
[&lt;all email addresses used to Register for the past 5 IETF meetings&gt;]=
<br>
&lt;Preferred email address&gt; =A0//<br>
&lt;Telephone number&gt; =A0 =A0 =A0 =A0 // For confirmation if selected<br=
>
<br>
Please expect an email response from me within 3 business days stating<br>
whether or not you are qualified. =A0If you don&#39;t receive a response,<b=
r>
please re-send your email with the tag &quot;RESEND:&quot; added to the sub=
ject<br>
line.<br>
<br>
If you are not yet sure you would like to volunteer, please consider<br>
that nomcom members play a very important role in shaping the<br>
leadership of the IETF. =A0Ensuring the leadership of the IETF is fair<br>
and balanced and comprised of those who can lead the IETF in the right<br>
direction is an important responsibility that rests on the IETF<br>
participants at large. Volunteering for the nomcom is a good way of<br>
contributing toward that goal.<br>
<br>
I will be publishing a more detailed timetable for nomcom activities,<br>
as well as details of the randomness seeds to be used for the RFC 3797<br>
selection process, within the next couple weeks.<br>
<br>
Thank you,<br>
Matthew Lepinski<br>
<a href=3D"mailto:mlepinski.ietf@gmail.com">mlepinski.ietf@gmail.com</a><br=
>
<a href=3D"mailto:nomcom-chair@ietf.org">nomcom-chair@ietf.org</a><br>
</div><br>

--bcaec554d63cf66a9804c448aec8--

From hsalgado@nic.cl  Mon Jul  9 07:38:30 2012
Return-Path: <hsalgado@nic.cl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E56F11E80AD for <weirds@ietfa.amsl.com>; Mon,  9 Jul 2012 07:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5q2F-yb39ywv for <weirds@ietfa.amsl.com>; Mon,  9 Jul 2012 07:38:30 -0700 (PDT)
Received: from mail.nic.cl (mail.nic.cl [IPv6:2001:1398:1::6008]) by ietfa.amsl.com (Postfix) with ESMTP id CDC6D11E80A6 for <weirds@ietf.org>; Mon,  9 Jul 2012 07:38:26 -0700 (PDT)
Received: from mail.nic.cl (localhost.localdomain [127.0.0.1]) by mail.nic.cl (Postfix) with ESMTP id A82FB248031 for <weirds@ietf.org>; Mon,  9 Jul 2012 10:38:49 -0400 (CLT)
Received: from vulcano.intra.nic.cl (unknown [IPv6:2001:1398:4:1:172:30:10:58]) by mail.nic.cl (Postfix) with ESMTP id 855FE24803C for <weirds@ietf.org>; Mon,  9 Jul 2012 10:38:49 -0400 (CLT)
Message-ID: <4FFAECF9.80606@nic.cl>
Date: Mon, 09 Jul 2012 10:38:49 -0400
From: Hugo Salgado <hsalgado@nic.cl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: weirds@ietf.org
References: <20120706231945.92055.qmail@joyce.lan>
In-Reply-To: <20120706231945.92055.qmail@joyce.lan>
X-Enigmail-Version: 1.4.2
OpenPGP: id=B525FA6E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP on Mon Jul 9 10:38:49 2012 -0400 (CLT)
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 14:38:30 -0000

On 07/06/2012 07:19 PM, John Levine wrote:
>> 1- Is the topic of building the mapping database in the scope of the WG
>> ? We did this for numbers but we must also consider the case of names.
>>
>> 2- Do the hierarchical vs mesh model alternatives need to be documented ?
>>
>> 3- Does the topic need its own draft(s) ?
> 
> I don't think it would be a good idea to try to build a top level map
> into the spec.  For both names and numbers, the data for a top level
> map resides (or reasonably would reside) at IANA, but this group can't
> tell IANA what to do.
> 
> Also, for names, one could imagine some kludges to bootstrap the map.
> A totally unofficial but widely used hack is whois-servers.net, who

Or rather one maintained by those responsible (RFC2782):
  $ dig _nicname._tcp.cl srv +short
  10 0 43 whois.nic.cl.

Hugo

From Ray.Bellis@nominet.org.uk  Mon Jul  9 10:17:05 2012
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A710111E8140 for <weirds@ietfa.amsl.com>; Mon,  9 Jul 2012 10:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.572
X-Spam-Level: 
X-Spam-Status: No, score=-10.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VuhagI33kJna for <weirds@ietfa.amsl.com>; Mon,  9 Jul 2012 10:17:04 -0700 (PDT)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id 80A9C11E80C8 for <weirds@ietf.org>; Mon,  9 Jul 2012 10:17:04 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Received:From:To:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=Zgo5Wpp5WUWZVifliqEiZv+/Co7bzesP5icxndkKlZJNoosIIeMxDFCJ wV0aPglFxLF00J8BOr+8A/yLuaQZ64lp+pRR+2+/fS8HW6G3oUl3GZBPI I1kqrK5cQ1vfQiY;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1341854250; x=1373390250; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[weirds]=20Redirection=20in=20the=20RES Tful=20WHOIS=20world|Date:=20Mon,=209=20Jul=202012=2017:1 7:33=20+0000|Message-ID:=20<43B5C782-63F0-4203-BE91-51D58 EBA1F38@nominet.org.uk>|To:=20"weirds@ietf.org"=20<weirds @ietf.org>|MIME-Version:=201.0|Content-Transfer-Encoding: =20quoted-printable|Content-ID:=20<85bae0eb-6a95-4f6b-ba6 7-f061bfd68fda>|In-Reply-To:=20<4FFAECF9.80606@nic.cl> |References:=20<20120706231945.92055.qmail@joyce.lan>=20< 4FFAECF9.80606@nic.cl>; bh=PEd62H8dr4ac91hupC7e12DVYBKiBLXCYdLkR4Weec8=; b=BKuwmVHcGvUFASHHpxa+PP5FkVCTquKlLdzKMJ0GVcCCNdDxqOmhip3d ic7uoxgfN6cWZxZL2bwzb5OgUMbZxo73myFHhD1Sruc0eDKpK64wrRJuV MR3vS/wF+m5jr17;
X-IronPort-AV: E=Sophos;i="4.77,553,1336345200"; d="scan'208";a="34059596"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 09 Jul 2012 18:17:28 +0100
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%19]) with mapi; Mon, 9 Jul 2012 18:17:27 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "weirds@ietf.org" <weirds@ietf.org>
Thread-Topic: [weirds] Redirection in the RESTful WHOIS world
Thread-Index: AQHNW5IG7509tt6HgUKHzJnpVa2f9pcc08CAgAQlc4CAACxZgA==
Date: Mon, 9 Jul 2012 17:17:33 +0000
Message-ID: <43B5C782-63F0-4203-BE91-51D58EBA1F38@nominet.org.uk>
References: <20120706231945.92055.qmail@joyce.lan> <4FFAECF9.80606@nic.cl>
In-Reply-To: <4FFAECF9.80606@nic.cl>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <85bae0eb-6a95-4f6b-ba67-f061bfd68fda>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 17:17:05 -0000

On 9 Jul 2012, at 15:38, Hugo Salgado wrote:

> Or rather one maintained by those responsible (RFC2782):
>  $ dig _nicname._tcp.cl srv +short
>  10 0 43 whois.nic.cl.

Did anyone ever solve the "top down" vs "bottom up" problem with _nicname._=
tcp ?

For example, we probably wouldn't want _nicname._tcp.example.co.uk to take =
precedence over _nicname._tcp.co.uk  [ or should that be _nicname._tcp.uk -=
 how does a client decide? ]

At the same time, we might want _some_ subdomains to have that authority (e=
.g. ac.uk).

Is the public suffix list sufficient, or is something more fine-grained req=
uired?

Ray


From pawal@blipp.com  Mon Jul  9 12:12:49 2012
Return-Path: <pawal@blipp.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86DB621F85E1 for <weirds@ietfa.amsl.com>; Mon,  9 Jul 2012 12:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05J1VtO5nTmt for <weirds@ietfa.amsl.com>; Mon,  9 Jul 2012 12:12:48 -0700 (PDT)
Received: from vic20.blipp.com (vic20.blipp.com [213.115.13.25]) by ietfa.amsl.com (Postfix) with ESMTP id F13AA21F85E3 for <weirds@ietf.org>; Mon,  9 Jul 2012 12:12:47 -0700 (PDT)
Received: from [192.168.0.139] (fh218n1-asp-a13.ias.bredband.telia.com [212.181.174.218]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by vic20.blipp.com (Postfix) with ESMTPSA id 939AB3809E; Mon,  9 Jul 2012 21:13:09 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: multipart/signed; boundary="Apple-Mail=_A7E8441C-A903-4B7E-9143-448C51960892"; protocol="application/pgp-signature"; micalg=pgp-sha1
From: =?iso-8859-1?Q?Patrik_Wallstr=F6m?= <pawal@blipp.com>
In-Reply-To: <43B5C782-63F0-4203-BE91-51D58EBA1F38@nominet.org.uk>
Date: Mon, 9 Jul 2012 21:13:04 +0200
Message-Id: <105EB723-7860-411F-9AD4-184E1E294F27@blipp.com>
References: <20120706231945.92055.qmail@joyce.lan> <4FFAECF9.80606@nic.cl> <43B5C782-63F0-4203-BE91-51D58EBA1F38@nominet.org.uk>
To: Ray Bellis <Ray.Bellis@nominet.org.uk>
X-Mailer: Apple Mail (2.1280)
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 19:12:49 -0000

--Apple-Mail=_A7E8441C-A903-4B7E-9143-448C51960892
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jul 9, 2012, at 7:17 PM, Ray Bellis wrote:
>=20
> On 9 Jul 2012, at 15:38, Hugo Salgado wrote:
>=20
>> Or rather one maintained by those responsible (RFC2782):
>> $ dig _nicname._tcp.cl srv +short
>> 10 0 43 whois.nic.cl.
>=20
> Did anyone ever solve the "top down" vs "bottom up" problem with =
_nicname._tcp ?
>=20
> For example, we probably wouldn't want _nicname._tcp.example.co.uk to =
take precedence over _nicname._tcp.co.uk  [ or should that be =
_nicname._tcp.uk - how does a client decide? ]
>=20
> At the same time, we might want _some_ subdomains to have that =
authority (e.g. ac.uk).
>=20
> Is the public suffix list sufficient, or is something more =
fine-grained required?


Another record at the parent level stating that no more redirection =
should happen? That would work with the "top down" model.

I don't recall the exact details of the cookies and public suffix list, =
but that kind of parent level record could solve that problem as well. =
(Is there a condensed discussion on the problem statement somewhere?)


--Apple-Mail=_A7E8441C-A903-4B7E-9143-448C51960892
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-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)

iEYEARECAAYFAk/7LUQACgkQXP9l7Jnf3xXoMwCfT8k94QPBWnlLfAoeqUVexgJP
N+sAniz0wc9G7PXW/I2vKuWCmt6jQ18V
=zOiJ
-----END PGP SIGNATURE-----

--Apple-Mail=_A7E8441C-A903-4B7E-9143-448C51960892--

From johnl@iecc.com  Mon Jul  9 15:25:24 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B97621F8668 for <weirds@ietfa.amsl.com>; Mon,  9 Jul 2012 15:25:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.374
X-Spam-Level: 
X-Spam-Status: No, score=-110.374 tagged_above=-999 required=5 tests=[AWL=-0.664, BAYES_05=-1.11, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XO2ojh5BkJt for <weirds@ietfa.amsl.com>; Mon,  9 Jul 2012 15:25:23 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 5AADD21F85F4 for <weirds@ietf.org>; Mon,  9 Jul 2012 15:25:23 -0700 (PDT)
Received: (qmail 18321 invoked from network); 9 Jul 2012 22:25:48 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 9 Jul 2012 22:25:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffb5a6c.xn--3zv.k1207; i=johnl@user.iecc.com; bh=HECiXf5FUHlSMAotV8RdkTVLJUvrqQfMPHOq2PsEeAM=; b=pKQQ6fyCIsvmkj57tlhZ5WzbVZggAQdDASuUGYOxybhZu3HQD2r99uA9AgRLDek4S2RSofeQD5lZhFHAEL1+kDjOscnytcpDG3g9/nqYTlfgnFHpf7tEWQlSM2h0MB0ke+dI8rHf/+DzbpKaT7ox4zW7KaOyK8aukhsxuf9iX40=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffb5a6c.xn--3zv.k1207; olt=johnl@user.iecc.com; bh=HECiXf5FUHlSMAotV8RdkTVLJUvrqQfMPHOq2PsEeAM=; b=cHGgLEogU/1uPYXNDEkzthpdNaELfAxO4jt1n7iLNWgdcG0lG66qPVr78DRYnOs7JZL5VpShW8Ac2axVC7bnFJh+uXggF6bqSakn1BIGoPhI/KdfzXWRpXAi+q+KTfEnYxOHF3+2HAqUohnnpYiPndljKlm7MdcV9i7ruClbELo=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 9 Jul 2012 22:25:26 -0000
Message-ID: <20120709222526.28976.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <43B5C782-63F0-4203-BE91-51D58EBA1F38@nominet.org.uk>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 22:25:24 -0000

>Is the public suffix list sufficient, or is something more fine-grained required?

The public suffix list is a crock.  If we want to do SRV records, I
wouldn't be looking at them other than for the TLD.  Surely the various
bits of .UK can figure out how to run a joint referral server if that's
what's needed.

R's,
John

From zhoulinlin@cnnic.cn  Mon Jul  9 19:37:58 2012
Return-Path: <zhoulinlin@cnnic.cn>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B26B011E80C1 for <weirds@ietfa.amsl.com>; Mon,  9 Jul 2012 19:37:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZaQFme61sBj8 for <weirds@ietfa.amsl.com>; Mon,  9 Jul 2012 19:37:58 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id 72C0311E80A1 for <weirds@ietf.org>; Mon,  9 Jul 2012 19:37:56 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn
Received: from unknown127.0.0.1 (HELO lenovo95e6383c) (127.0.0.1) by 127.0.0.1 with SMTP; Tue, 10 Jul 2012 10:38:14 +0800
From: "Linlin Zhou" <zhoulinlin@cnnic.cn>
To: "'Carlos M. Martinez'" <carlosm3011@gmail.com>, <weirds@ietf.org>
References: <4FF70E2C.9070104@gmail.com>
In-Reply-To: <4FF70E2C.9070104@gmail.com>
Date: Tue, 10 Jul 2012 10:38:14 +0800
Message-ID: <005101cd5e45$0e65f650$2b31e2f0$@cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1bkgWLVKH7zhyDQtelOpqHrpBbmgCsRUsg
Content-Language: zh-cn
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 02:37:58 -0000

> -----Original Message-----
> From: weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On Behalf
Of
> Carlos M. Martinez
> Sent: Saturday, July 07, 2012 12:11 AM
> To: <weirds@ietf.org>
> Subject: [weirds] Redirection in the RESTful WHOIS world
> 
> Hello all,
> 
> We submitted a few weeks ago a weirds document
> (draft-lacnic-weirds-restwhois-redirects [1]) that documents a piece of
running
> code we wrote at LACNIC that performs single-point redirection of RESTful
> WHOIS queries. The intent of the document, besides documenting running
code,
> was to spur discussion on the topic of redirects.
> 
> At this point, and with the -00 deadline fast approaching, I'll try to
summarize
> the different view points and possible ways forward.
> 
> In any redirection scheme at least one server needs to have a database
that
> maps resources to authoritative WEIRDS servers, as "200/8 =>
lacnic_weirds,
> 1/8 => apnic_weirds", etc. There are at least two possible approaches, one
> with a set of central redirect-only servers and a mesh, flat model where
weirds
> servers directly redirect to each other.
> 
> Our prototype ([1], [2]) implements the hierarchical model and the
database is
> fed from IANA's IPv4, IPv6 and ASN registries. We are aware of the
limitations
> of this approach, mostly in the case of IPv4, but as this work is intended
only to
> be a quick proof-of-concept this provided a quick and painless way to
build the
> db.
> 
> So, here are the open issues:
> 
> 1- Is the topic of building the mapping database in the scope of the WG ?
We
> did this for numbers but we must also consider the case of names.
> 
I don't think this is included in the WG scope. In my personal point of
view, it is just the mapping details, whether build a database or other RR
to find the URI.

> 2- Do the hierarchical vs mesh model alternatives need to be documented ?
> 

IMHO, it's better to explain these two models, or I'm a little confused with
the text and figure.

> 3- Does the topic need its own draft(s) ?
> 
> From feedback I've received, if the answer to (1) is 'no' then the topic
of
> redirects should probably be included as simple section (return 30x
pointing to
> such and such in case of  in other document, probably in the HTTP draft.
If, on
> the other hand, the answer to (1) is 'yes', then there is a lot of ground
to cover
> in a one or perhaps, two, documents (names and numbers)
> 

> Share your thoughts!
> 
> Warm regards
> 
> Carlos
> 
> [1]
> http://tools.ietf.org/html/draft-lacnic-weirds-restwhois-redirects-00.txt
> [2] http://www.labs.lacnic.net/site/restful-whois (in Spanish, but links
work
> anyways) _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds


From Ray.Bellis@nominet.org.uk  Tue Jul 10 01:19:12 2012
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58DFC21F8666 for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 01:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.576
X-Spam-Level: 
X-Spam-Status: No, score=-10.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nUrss14M2WdT for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 01:19:11 -0700 (PDT)
Received: from mx3.nominet.org.uk (mail.nominet.org.uk [213.248.199.23]) by ietfa.amsl.com (Postfix) with ESMTP id A758621F8652 for <weirds@ietf.org>; Tue, 10 Jul 2012 01:19:09 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:Received:Received:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=0l9U2+C9FjPXh9IjrLBj5Mb9BghKgLWG4nbZvP8DIZ8+g5DrDgY8ckdb ymQvgtErNjTIj3yfMNTox9uZuLn5gc9z0ZCWK0Zwk6O3RICBpoNVsjzVN I5bcm1WzqRr/Db8;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1341908378; x=1373444378; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[weirds]=20Redirection=20in=20the=20RES Tful=20WHOIS=20world|Date:=20Tue,=2010=20Jul=202012=2008: 19:34=20+0000|Message-ID:=20<811DF250-437C-4456-B11E-C518 F67D5D10@nominet.org.uk>|To:=20John=20Levine=20<johnl@tau gh.com>|CC:=20"weirds@ietf.org"=20<weirds@ietf.org> |MIME-Version:=201.0|Content-Transfer-Encoding:=20quoted- printable|Content-ID:=20<dd98f4e3-d773-4639-89ab-fcae0818 e15b>|In-Reply-To:=20<20120709222526.28976.qmail@joyce.la n>|References:=20<20120709222526.28976.qmail@joyce.lan>; bh=hCsMFPmp8Omh2w05PeEOlEU2QeEwRmT4YQ3Cy5DKaoU=; b=C620op41v0Dcbpl+vLyeim6u/EBZhnmAnvU4nXTcGnuQPzCowJwA7HyO ttRuqGaCDoQURAhw9uars+UXXN2NtDAkytwmI1l6GwmD0vWyJuUXJGJfS gspfKi40eFxhXAt;
X-IronPort-AV: E=Sophos;i="4.77,559,1336345200"; d="scan'208";a="41465074"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx3.nominet.org.uk with ESMTP; 10 Jul 2012 09:19:35 +0100
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%19]) with mapi; Tue, 10 Jul 2012 09:19:34 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: John Levine <johnl@taugh.com>
Thread-Topic: [weirds] Redirection in the RESTful WHOIS world
Thread-Index: AQHNW5IG7509tt6HgUKHzJnpVa2f9pcc08CAgAQlc4CAACxZgIAAVgYAgACl/wA=
Date: Tue, 10 Jul 2012 08:19:34 +0000
Message-ID: <811DF250-437C-4456-B11E-C518F67D5D10@nominet.org.uk>
References: <20120709222526.28976.qmail@joyce.lan>
In-Reply-To: <20120709222526.28976.qmail@joyce.lan>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <dd98f4e3-d773-4639-89ab-fcae0818e15b>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 08:19:12 -0000

On 9 Jul 2012, at 23:25, John Levine wrote:

> The public suffix list is a crock.

I couldn't possibly comment.

> If we want to do SRV records, I wouldn't be looking at them other than fo=
r the TLD.

OK, so start at the top, and stay there :)

> Surely the various bits of .UK can figure out how to run a joint referral=
 server if that's
> what's needed.

Yup, at least with WEIRDS we will finally have an opportunity to implement =
a standard referral mechanism.

Ray


From ajs@anvilwalrusden.com  Tue Jul 10 03:59:36 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E734821F8770 for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 03:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.597
X-Spam-Level: 
X-Spam-Status: No, score=-1.597 tagged_above=-999 required=5 tests=[AWL=-0.757, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kq6YhE+9MWk6 for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 03:59:36 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC3221F8742 for <weirds@ietf.org>; Tue, 10 Jul 2012 03:59:36 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id E182C8A031 for <weirds@ietf.org>; Tue, 10 Jul 2012 10:59:58 +0000 (UTC)
Date: Tue, 10 Jul 2012 06:59:54 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: weirds@ietf.org
Message-ID: <20120710105953.GA79014@mail.yitter.info>
References: <20120706231945.92055.qmail@joyce.lan> <4FFAECF9.80606@nic.cl> <43B5C782-63F0-4203-BE91-51D58EBA1F38@nominet.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43B5C782-63F0-4203-BE91-51D58EBA1F38@nominet.org.uk>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 10:59:37 -0000

On Mon, Jul 09, 2012 at 05:17:33PM +0000, Ray Bellis wrote:
> Is the public suffix list sufficient

Heck, no, but this sort of issue is what I'm hoping to tackle with
draft-sullivan-domain-origin-assert.  I've had some comments and am
working on an -01 to appear before the deadline.  A notable problem in
-00 is that it works by name only, and the feedback I had was that it
needs to work by {name, port, scheme}.  More explanations of why I'm
on the completely wrong track would help me abandon this windmill-tilting.

Best,

A 

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sm@resistor.net  Tue Jul 10 04:00:23 2012
Return-Path: <sm@resistor.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CF6521F8770 for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 04:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kIvlDcNJ8dKa for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 04:00:19 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E337F21F8742 for <weirds@ietf.org>; Tue, 10 Jul 2012 04:00:18 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q6AB0fHg024617 for <weirds@ietf.org>; Tue, 10 Jul 2012 04:00:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1341918045; bh=vvhWICJl51HeneQ+I47B6c3ZSULaXPWl2/ZZGN5FzEs=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=RKpU+bSfMYHOl6Hvs2ctVGF3eFHyw+ZlajKhVnkNgwof+52rwRDaAoHWSD1FOKEA/ a8sTGBIN6GwbD876f7FlE7LL1w8/AF8XfK+S3OxMUOA5Lniwe9lqYJ0/pYrtnLAiPI UzocMR6PBq6VLEPNPFEsyKLcPsI76LnncapT1KqA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1341918045; i=@resistor.net; bh=vvhWICJl51HeneQ+I47B6c3ZSULaXPWl2/ZZGN5FzEs=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=j0yVPR32XlMv4qLESB2x9BUfCsg+USmjc8Rzzse3jaZ1Y827ctSBIe5sgGHi6mjvk v/DRmjAL0Ngta9fCeyxjJrP52U7Bu7x5264UprUfdmYbV4mqzyhzMJEQYD0Wsxpqus 008ecRi1oV69vGNzhLc/9/CR8HRhH6R59GqHLm50=
Message-Id: <6.2.5.6.2.20120710034326.09fcc758@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 10 Jul 2012 04:00:10 -0700
To: weirds@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <20120709222526.28976.qmail@joyce.lan>
References: <43B5C782-63F0-4203-BE91-51D58EBA1F38@nominet.org.uk> <20120709222526.28976.qmail@joyce.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 11:00:23 -0000

At 15:25 09-07-2012, John Levine wrote:
>The public suffix list is a crock.  If we want to do SRV records, I

:-)

At 01:19 10-07-2012, Ray Bellis wrote:
>OK, so start at the top, and stay there :)

Well, the top is out of scope. :-)  It's easy to define what the top 
is.  It's difficult to decide on who to talk to about the top because 
every body wants to be at the top.  if you stay at the top there 
isn't any delegation.  If the top decides to delegate I am not sure 
whether it would it/they would find devolution palatable.

Regards,
-sm 


From carlosm3011@gmail.com  Tue Jul 10 07:05:34 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EAD021F8790 for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 07:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15eu1LpgHWMP for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 07:05:33 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8E3C221F8789 for <weirds@ietf.org>; Tue, 10 Jul 2012 07:05:33 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so5782ggn.31 for <weirds@ietf.org>; Tue, 10 Jul 2012 07:06:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=dCxp6QwnyFT6hAAKjMwUxddB8tSfP73wfihRNnVenbI=; b=bwqI3boFRRCS+5oVLWpd+sjR3j82nnVfLSXyMqFd1yrq+zdohlSm2EnCUS7k363K+I ec83d60BEbjJ4/j1P4FeTT2G5nkm5P2tUYFprBkTv54paihGjQVptW4ibbYb678+rsml PP87sa692FC0Ye2fpWCywVLxSE53F/CKoCDrbIjN9+yVIIFqAOue4peXKQJgRilgO90v 2+qLEkrBj1jW5ROV2dmIPNJc7Wj+X3KP0x2QRG6XPHAHvGLjFpzaTiHufKbQB4rR+Y9M oH1ad+IMPLZksyLNrp7LndSLDaFWKGC49kJLl4nXuwa03qjGyQwOd6U/qdJYWTfgKRip NNEw==
Received: by 10.236.79.103 with SMTP id h67mr15213598yhe.70.1341929161186; Tue, 10 Jul 2012 07:06:01 -0700 (PDT)
Received: from europa.local (r190-135-36-21.dialup.adsl.anteldata.net.uy. [190.135.36.21]) by mx.google.com with ESMTPS id q10sm32804462anm.16.2012.07.10.07.05.58 (version=SSLv3 cipher=OTHER); Tue, 10 Jul 2012 07:06:00 -0700 (PDT)
Message-ID: <4FFC36C4.4010104@gmail.com>
Date: Tue, 10 Jul 2012 11:05:56 -0300
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: weirds@ietf.org
References: <43B5C782-63F0-4203-BE91-51D58EBA1F38@nominet.org.uk> <20120709222526.28976.qmail@joyce.lan> <6.2.5.6.2.20120710034326.09fcc758@resistor.net>
In-Reply-To: <6.2.5.6.2.20120710034326.09fcc758@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 14:05:34 -0000

Hello all,

I did not submit a -00 in the end, but I definitely sense that there is
a problem to solve here.

I believe we need to frame this problem, which i'm also starting to
believe that is fundamentally different for names and numbers.

cheers!

Carlos

On 7/10/12 8:00 AM, SM wrote:
> At 15:25 09-07-2012, John Levine wrote:
>> The public suffix list is a crock.  If we want to do SRV records, I
>
> :-)
>
> At 01:19 10-07-2012, Ray Bellis wrote:
>> OK, so start at the top, and stay there :)
>
> Well, the top is out of scope. :-)  It's easy to define what the top
> is.  It's difficult to decide on who to talk to about the top because
> every body wants to be at the top.  if you stay at the top there isn't
> any delegation.  If the top decides to delegate I am not sure whether
> it would it/they would find devolution palatable.
>
> Regards,
> -sm
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds



From andy@arin.net  Tue Jul 10 10:00:48 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B00EB21F86E3 for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 10:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Zv35xaJCg7x for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 10:00:48 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id EDD7821F86DF for <weirds@ietf.org>; Tue, 10 Jul 2012 10:00:47 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id 69708165045; Tue, 10 Jul 2012 13:01:15 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp1.arin.net (Postfix) with ESMTP id 19D59164FD7 for <weirds@ietf.org>; Tue, 10 Jul 2012 13:01:15 -0400 (EDT)
Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Tue, 10 Jul 2012 13:00:59 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0298.004; Tue, 10 Jul 2012 13:01:07 -0400
From: Andy Newton <andy@arin.net>
To: "weirds@ietf.org" <weirds@ietf.org>
Thread-Topic: [weirds] Redirection in the RESTful WHOIS world
Thread-Index: AQHNW5IHZp05Hg+U/kiz3QFYlCIyNpcdJ5KAgAQlcoCAACxagIAAVgUAgAE3uIA=
Date: Tue, 10 Jul 2012 17:01:07 +0000
Message-ID: <33972B17-E899-42BE-9139-63F99321770A@arin.net>
References: <20120709222526.28976.qmail@joyce.lan>
In-Reply-To: <20120709222526.28976.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.1.56]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C4260CDCE4CB4547A9FA221DDC3588A5@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 17:00:48 -0000

On Jul 9, 2012, at 6:25 PM, John Levine wrote:

> If we want to do SRV records

I sure hope we aren't suggesting this on the client end. There are two comp=
lications.

1) It makes the clients that much more insane to write. Please let us keep =
the client requirements simple. However, if the idea is to use DNS records =
so that servers can synthesize HTTP redirects, that is better. Putting the =
complexity into the servers is the better choice.

2) SRVs are not enough. HTTP uses URLs and not just domain names, so NAPTR =
records would be more suitable. U-NAPTR comes to mind.

But for the big picture, standardizing the referral hierarchy is probably a=
 world of hurt. More doable is probably an Informational on what one might =
expect to see.

-andy=

From johnl@iecc.com  Tue Jul 10 14:20:26 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CCB411E80FC for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 14:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.077
X-Spam-Level: 
X-Spam-Status: No, score=-111.077 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qynAwDfv9BsG for <weirds@ietfa.amsl.com>; Tue, 10 Jul 2012 14:20:25 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 6B9F111E80CC for <weirds@ietf.org>; Tue, 10 Jul 2012 14:20:24 -0700 (PDT)
Received: (qmail 92024 invoked from network); 10 Jul 2012 21:20:51 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 10 Jul 2012 21:20:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffc9cb3.xn--btvx9d.k1207; i=johnl@user.iecc.com; bh=Wo92gOSNojgJOTzQHpnba+kiIQfNUKiPDJtuPxDQwKU=; b=YAyA3MHDgfCblvw7q7NJiTkFYRiMjCJ9ISZGTbly0bOS+ZnTni0vkx8x2UEmIhm+clLKh4p/M2yk8nNDJeUOZcKAgdvDG9WkBaSanog1eAswn9emGJa4b1cfl4TeW7yaIgYfJ8cLDbvkyunjWRL5zNM4E/OFcjV0FXFMF9nQP8o=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffc9cb3.xn--btvx9d.k1207; olt=johnl@user.iecc.com; bh=Wo92gOSNojgJOTzQHpnba+kiIQfNUKiPDJtuPxDQwKU=; b=Cp2u0AO4m9SR0107Pg4AMhAPfYVQsYZvI02Hk6L5+l2JmFRdUlZu4ycun7C2TLqB8Ziah0HZBCxl4BBzzHyeiek7amHqgMl/tztakujW10So+k5rj8L90NeYX3xGODe7V8pEu54G8xnjSVzQ2kP1fEZ0QzxYWttnHaGmve0X3v4=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 10 Jul 2012 21:20:29 -0000
Message-ID: <20120710212029.77643.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <33972B17-E899-42BE-9139-63F99321770A@arin.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 21:20:26 -0000

In article <33972B17-E899-42BE-9139-63F99321770A@arin.net> you write:
>
>On Jul 9, 2012, at 6:25 PM, John Levine wrote:
>
>> If we want to do SRV records
>
>I sure hope we aren't suggesting this on the client end. There are two complications.
>
>1) It makes the clients that much more insane to write. Please let us keep the client requirements simple. ...

In case it wasn't clear, I was just thinking of using the DNS to
bootstrap the query process.  Take the TLD of a name, the high octet
of an IPv4 address or the high 12 bits (give or take) of an IPv6
address, use the DNS to find an initial server, and then do the
RESTful query which might do further redirections.

The alternative would be a top level redirect server, which would have
to be run by IANA or someone they delegate.  There's nothing wrong
with that if IANA offers to do so, but it'd be a lot of work since it
would presumably get a vast amount of traffic.  The DNS bootstrap
approach would generally have the hints published by people who are
running a WEIRDS server in DNS zones they control, so IANA would stay
out of it.

R's,
John

From vesely@tana.it  Wed Jul 11 00:00:30 2012
Return-Path: <vesely@tana.it>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B969811E80D1 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 00:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.559
X-Spam-Level: 
X-Spam-Status: No, score=-4.559 tagged_above=-999 required=5 tests=[AWL=0.160,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PgTTo+1N+ZaQ for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 00:00:25 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id D038711E8086 for <weirds@ietf.org>; Wed, 11 Jul 2012 00:00:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1341990052; bh=iUN119Ka16MjPbj5IQ2NBtzsigUZbIczWxZBueZOOkc=; l=653; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=ZIXC4D2tVaKv2fgHaZDnRo4RUL1bKhvOAESEJa05GDwegStPnFojVvYGrPe+WJ/+U ULz67+IjRVs7gLw96V1kJfML2upkQER7Bvponk6L0l9oQp0NBWhwZW9sJ6V+ZV6R1A LfbNGsCfmuADoU1IEcmwhhaDqn3hdjTSaMSgWMvw=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Wed, 11 Jul 2012 09:00:52 +0200 id 00000000005DC044.000000004FFD24A4.000055E4
Message-ID: <4FFD24A4.8010900@tana.it>
Date: Wed, 11 Jul 2012 09:00:52 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: weirds@ietf.org
References: <20120710212029.77643.qmail@joyce.lan>
In-Reply-To: <20120710212029.77643.qmail@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 07:00:30 -0000

On Tue 10/Jul/2012 23:20:29 +0200 John Levine wrote:
> 
> The alternative would be a top level redirect server, which would
> have to be run by IANA or someone they delegate.  There's nothing
> wrong with that if IANA offers to do so,

It was already said that this group can't tell IANA what to do.  Can
it ask, at least?

> but it'd be a lot of work since it would presumably get a vast
> amount of traffic.

What traffic increment do we expect as a consequence of establishing a
sound, simple way to learn operators' details?  For instance, will
there be a query for each loaded web page, only for shopping ones, or
none at all like now?


From andy@arin.net  Wed Jul 11 03:04:28 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF7CE21F8579 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 03:04:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2A9Te4Vw98c5 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 03:04:28 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 1D0DA21F856C for <weirds@ietf.org>; Wed, 11 Jul 2012 03:04:28 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id C2AE816524A; Wed, 11 Jul 2012 06:04:57 -0400 (EDT)
Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp1.arin.net (Postfix) with ESMTP id 58879165247; Wed, 11 Jul 2012 06:04:57 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 11 Jul 2012 06:04:11 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0247.003; Wed, 11 Jul 2012 06:04:51 -0400
From: Andy Newton <andy@arin.net>
To: John Levine <johnl@taugh.com>
Thread-Topic: [weirds] Redirection in the RESTful WHOIS world
Thread-Index: AQHNW5IHZp05Hg+U/kiz3QFYlCIyNpcdJ5KAgAQlcoCAACxagIAAVgUAgAE3uICAAEh4gIAA1Y4A
Date: Wed, 11 Jul 2012 10:04:49 +0000
Message-ID: <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net>
References: <20120710212029.77643.qmail@joyce.lan>
In-Reply-To: <20120710212029.77643.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.35.156]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4BB2FDF359F96844AB013103E3830731@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 10:04:29 -0000

On Jul 10, 2012, at 5:20 PM, John Levine wrote:

> In case it wasn't clear, I was just thinking of using the DNS to
> bootstrap the query process.  Take the TLD of a name, the high octet
> of an IPv4 address or the high 12 bits (give or take) of an IPv6
> address, use the DNS to find an initial server, and then do the
> RESTful query which might do further redirections.
>=20
> The alternative would be a top level redirect server, which would have
> to be run by IANA or someone they delegate.  There's nothing wrong
> with that if IANA offers to do so, but it'd be a lot of work since it
> would presumably get a vast amount of traffic.  The DNS bootstrap
> approach would generally have the hints published by people who are
> running a WEIRDS server in DNS zones they control, so IANA would stay
> out of it.

Does the location of whois servers change frequently? For the most part thi=
s is static information and engineering this type of bootstrap process seem=
s to be overkill. To the other point, running a top level redirect server d=
oesn't sound that onerous; though I'd prefer this type of solution to allow=
 any interested party into running such a service, not just IANA. (BTW, IAN=
A does operate a top level Whois server today.)

For redirection, there are more interesting cases other than bootstrap -- s=
pecifically ERX space in the number registries.

-andy=

From ajs@anvilwalrusden.com  Wed Jul 11 04:57:52 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31E9421F8625 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 04:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RbbkOGnzrHjl for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 04:57:51 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id AB0EB21F8623 for <weirds@ietf.org>; Wed, 11 Jul 2012 04:57:51 -0700 (PDT)
Received: from mail.yitter.info (bas1-malton22-1167905092.dsl.bell.ca [69.156.209.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 442628A031 for <weirds@ietf.org>; Wed, 11 Jul 2012 11:58:20 +0000 (UTC)
Date: Wed, 11 Jul 2012 07:58:16 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: weirds@ietf.org
Message-ID: <20120711115816.GA82178@mail.yitter.info>
References: <20120710212029.77643.qmail@joyce.lan> <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 11:57:52 -0000

On Wed, Jul 11, 2012 at 10:04:49AM +0000, Andy Newton wrote:
> 
> Does the location of whois servers change frequently? For the most
> part this is static information and engineering this type of
> bootstrap process seems to be overkill.

Except when it isn't.  When .org was redelegated, I recall dealing
with complaints about "bad whois responses" as late as 2 years after
the redelegation, because people's clients had the Verisign server
name baked into them.  Given the expansion of the root (and the
sometimes, um, optimistic revenue assumptions of prospective registry
operators), I think we can expect redelegations to happen at least
often enough in future that it will be worth having a way to learn the
correct server to ask.

> running such a service, not just IANA. (BTW, IANA does operate a top
> level Whois server today.)

Indeed, and the WHOIS Review Team report that was released not so long
ago (and mentioned on this list) calls for that operation to get a
much larger, with at least a full-service rwhois proxy.

> For redirection, there are more interesting cases other than bootstrap -- specifically ERX space in the number registries.
> 

Yes.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From warren@kumari.net  Wed Jul 11 07:45:43 2012
Return-Path: <warren@kumari.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A10021F8608 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 07:45:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.482
X-Spam-Level: 
X-Spam-Status: No, score=-106.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZJ3yFscYzFRW for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 07:45:42 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id AD39D21F8532 for <weirds@ietf.org>; Wed, 11 Jul 2012 07:45:42 -0700 (PDT)
Received: from [192.168.0.105] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 093C81B40B83; Wed, 11 Jul 2012 10:46:12 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <20120711115816.GA82178@mail.yitter.info>
Date: Wed, 11 Jul 2012 10:46:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <37FB8CB6-B97C-472A-9CFC-6C046A9D0C73@kumari.net>
References: <20120710212029.77643.qmail@joyce.lan> <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net> <20120711115816.GA82178@mail.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1278)
Cc: weirds@ietf.org
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 14:45:43 -0000

On Jul 11, 2012, at 7:58 AM, Andrew Sullivan wrote:

> On Wed, Jul 11, 2012 at 10:04:49AM +0000, Andy Newton wrote:
>>=20
>> Does the location of whois servers change frequently?

Nope, not frequently at all (in the current world).. But, when they do, =
hilarity ensues...

>> For the most
>> part this is static information and engineering this type of
>> bootstrap process seems to be overkill.
>=20

The big issue is that this sort of thing will get baked into binaries =
and packages that almost never get updated=85.


> Except when it isn't.  When .org was redelegated, I recall dealing
> with complaints about "bad whois responses" as late as 2 years after
> the redelegation, because people's clients had the Verisign server
> name baked into them.  Given the expansion of the root (and the
> sometimes, um, optimistic revenue assumptions of prospective registry
> operators), I think we can expect redelegations to happen at least
> often enough in future that it will be worth having a way to learn the
> correct server to ask.
>=20

Yup -- there are a large collection of new gTLDs, and (to me at least) =
many of the business plans seem, um, interesting=85

I think it is prudent to assume that there will be a number of failures =
that will require redelegation and so (probably) movement of the whois =
servers=85

Ain't this fun?!

W


>> running such a service, not just IANA. (BTW, IANA does operate a top
>> level Whois server today.)
>=20
> Indeed, and the WHOIS Review Team report that was released not so long
> ago (and mentioned on this list) calls for that operation to get a
> much larger, with at least a full-service rwhois proxy.
>=20
>> For redirection, there are more interesting cases other than =
bootstrap -- specifically ERX space in the number registries.
>>=20
>=20
> Yes.
>=20
> A
>=20
> --=20
> Andrew Sullivan
> ajs@anvilwalrusden.com
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds
>=20

--
"Let's just say that if complete and utter chaos was lightning, he'd be =
the sort to stand on a hilltop in a thunderstorm wearing wet copper =
armour and shouting 'All gods are bastards'."

    -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of =
Magic)



From johnl@taugh.com  Wed Jul 11 08:57:01 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E62511E8091 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 08:57:01 -0700 (PDT)
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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QyoZM6j9nswr for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 08:57:00 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id B2D1C11E8085 for <weirds@ietf.org>; Wed, 11 Jul 2012 08:56:59 -0700 (PDT)
Received: (qmail 72023 invoked from network); 11 Jul 2012 15:57:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=11956.4ffda269.k1207; bh=pnHbVLKcn29a2HZ83QrRpzU0XsSQLnsyrILjzb45x8c=; b=giQuG8KCwsCghgsWHnfjmd9h2b58FH4KiWsMNH/soeWadHv4SztELvACg6NAUbq+kBRCw7vzq9H0bZY2JkWBCaivYnE1iITIjNjIPYgMbWEQKfoyN2Gx0q5gp03wOiqu+Pidp3XTr5U8G0K+ceiylxzSa3i+eO8Pvzef0tOcxZQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=11956.4ffda269.k1207; bh=pnHbVLKcn29a2HZ83QrRpzU0XsSQLnsyrILjzb45x8c=; b=JoeWgZrPa+GIXVJlHNnKE6A/UsJT4C/4uqf8mSBm6DBQzReK51m38YQOWckY6JA4q7QZvu0YeXl30uNVPfFe8/EccKb4llMnD9ciVrhn1WTryDy858UwGiuBBlvJbv8dI4bbqDIrrhzRk4r66Bnl8YqbnRGBQV8Cl9Wo/QuZw8E=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 11 Jul 2012 15:57:07 -0000
Date: 11 Jul 2012 11:57:29 -0400
Message-ID: <alpine.BSF.2.00.1207111105280.36659@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Andy Newton" <andy@arin.net>
In-Reply-To: <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net>
References: <20120710212029.77643.qmail@joyce.lan> <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 15:57:01 -0000

> Does the location of whois servers change frequently? For the most part 
> this is static information and engineering this type of bootstrap 
> process seems to be overkill.

The location of any particular WHOIS server won't change very often.  On 
the other hand, if ICANN goes through with the plan to have thousands of 
TLDs, every week something will change.  Even in the IP space, as people 
use more IPv6 space, IANA will allocate new chunks to the RIRs.  You seem 
to be suggesting that we use the equivalent of HOSTS.TXT, which is, well, 
quaint.

> To the other point, running a top level redirect server doesn't sound 
> that onerous; though I'd prefer this type of solution to allow any 
> interested party into running such a service, not just IANA. (BTW, IANA 
> does operate a top level Whois server today.)

You're missing the key problem, the phenomenal load that a toplevel WEIRDS 
server would get.

Among the clever bits of design in the DNS is that zone cuts let it do 
what one might call prefix caching.  If I do a DNS lookup for aaa.bbb.com, 
my local cache remembers the name servers for .COM so that when I look up 
ccc.ddd.com, it already knows the .com server and doesn't have to ask 
again.

Although there are certainly web caches, they only cache exact matches, 
not prefixes.  So if IANA or whoever runs a top level redirector, I'm 
going to point all of my WHOIS lookups there, with local cache hits only 
if I've made the same exact query before.  The .COM WHOIS servers get 
about 1500 queries/second, a rather significant amount of traffic for IANA 
or anyone who's not already running WHOIS at scale to take on.  Yes, IANA 
runs WHOIS for the tiny root and INT zones, but that's hardly the same 
thing.

That's why I want the bootstrap to be in the DNS; it's the only existing 
infrastructure that can handle the load.

> For redirection, there are more interesting cases other than bootstrap 
> -- specifically ERX space in the number registries.

Of course, but I would expect that to be handled by http redirects from 
the old registry.

There are lots of redirects in the name space.  One of particular interest 
to me is that the .US domain still has subregistries for many geographic 
domains, and the subregistry agreement requires that we provide WHOIS.  I 
run one of those subregistries, but have never bothered to provide WHOIS 
because if I did, there would be no way for anyone to find it.  This was 
brought home to me last week when I started getting confirmation mail from 
Godaddy for SSL certificates that one of my registrants had bought.  Here 
in upstate NY things are pretty informal, and five minutes after the first 
message arrived, the phone rang and it was the registrant (the government 
of a nearby county) telling me that they'd ordered them so could I please 
approve them.  But that doesn't scale too well.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

PS: The whois.iana.org server has both an IPv4 address and an IPv6 
address, but the IPv6 address doesn't work, as in I can't connect, can't 
ping, and traceroutes get lost somewhere in NTT's network.  I'd think that 
if anyone actually used it, someone would have noticed and fixed this by 
now.

From andy@arin.net  Wed Jul 11 11:02:16 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1290511E8101 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 11:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JtX2rSezkwpW for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 11:02:15 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 0108211E80CD for <weirds@ietf.org>; Wed, 11 Jul 2012 11:02:14 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id 919F11652E9; Wed, 11 Jul 2012 14:02:45 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp1.arin.net (Postfix) with ESMTP id D4FFD16520B; Wed, 11 Jul 2012 14:02:44 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 11 Jul 2012 14:02:18 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Wed, 11 Jul 2012 14:02:30 -0400
From: Andy Newton <andy@arin.net>
To: John R Levine <johnl@taugh.com>
Thread-Topic: [weirds] Redirection in the RESTful WHOIS world
Thread-Index: AQHNW5IHZp05Hg+U/kiz3QFYlCIyNpcdJ5KAgAQlcoCAACxagIAAVgUAgAE3uICAAEh4gIAA1Y4AgABiiICAACLsgA==
Date: Wed, 11 Jul 2012 18:02:29 +0000
Message-ID: <B32EF1A5-3969-4479-AF9B-A75475F66307@arin.net>
References: <20120710212029.77643.qmail@joyce.lan> <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net> <alpine.BSF.2.00.1207111105280.36659@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1207111105280.36659@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.1.56]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6212A1511160414C96407A765B8C0F31@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 18:02:16 -0000

On Jul 11, 2012, at 11:57 AM, John R Levine wrote:

>=20
> The location of any particular WHOIS server won't change very often.  On =
the other hand, if ICANN goes through with the plan to have thousands of TL=
Ds, every week something will change.  Even in the IP space, as people use =
more IPv6 space, IANA will allocate new chunks to the RIRs.  You seem to be=
 suggesting that we use the equivalent of HOSTS.TXT, which is, well, quaint=
.

I seem to recall a bunch of /8s added into the Whois recently without need =
of any such mechanism. But I am enjoying the juxtaposition of you arguing t=
hat we base a major protocol component on the unfinished plans of ICANN. :)

>> To the other point, running a top level redirect server doesn't sound th=
at onerous; though I'd prefer this type of solution to allow any interested=
 party into running such a service, not just IANA. (BTW, IANA does operate =
a top level Whois server today.)
>=20
> You're missing the key problem, the phenomenal load that a toplevel WEIRD=
S server would get.

No, I understand.

> Among the clever bits of design in the DNS is that zone cuts let it do wh=
at one might call prefix caching.  If I do a DNS lookup for aaa.bbb.com, my=
 local cache remembers the name servers for .COM so that when I look up ccc=
.ddd.com, it already knows the .com server and doesn't have to ask again.
>=20
> Although there are certainly web caches, they only cache exact matches, n=
ot prefixes.  So if IANA or whoever runs a top level redirector, I'm going =
to point all of my WHOIS lookups there, with local cache hits only if I've =
made the same exact query before.  The .COM WHOIS servers get about 1500 qu=
eries/second, a rather significant amount of traffic for IANA or anyone who=
's not already running WHOIS at scale to take on.  Yes, IANA runs WHOIS for=
 the tiny root and INT zones, but that's hardly the same thing.
>=20
> That's why I want the bootstrap to be in the DNS; it's the only existing =
infrastructure that can handle the load.

For this problem, no it isn't.

Many Whois operators have had SRV records for years, yet the Whois clients =
that make use of them are in the minority. Using DNS has it problems, and i=
n this instance it is the lack of useful client libraries. We should not ig=
nore that client implementers have thus far steered away from this availabl=
e solution.

I can easily think of a bootstrap mechanism easier to implement with tools =
already required for RESTful Whois than using DNS. A "root" redirect server=
 is only one of them.

> PS: The whois.iana.org server has both an IPv4 address and an IPv6 addres=
s, but the IPv6 address doesn't work, as in I can't connect, can't ping, an=
d traceroutes get lost somewhere in NTT's network.  I'd think that if anyon=
e actually used it, someone would have noticed and fixed this by now.

I don't speak for the people running this service, but I would not characte=
rize a class of service on one problem report, especially one that could ea=
sily be out of their control.

-andy=

From johnl@taugh.com  Wed Jul 11 11:49:06 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C4BE21F85A5 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 11:49:06 -0700 (PDT)
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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f6OV8Nq8xfUj for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 11:49:05 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9E42A21F8554 for <weirds@ietf.org>; Wed, 11 Jul 2012 11:49:03 -0700 (PDT)
Received: (qmail 14044 invoked from network); 11 Jul 2012 18:49:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=36db.4ffdcabc.k1207; bh=cGypl/SkBSSe+0XLuRnzxAfTbhQy948/QihpyfOnzVE=; b=JEUEmRThSNj6Av+IhGaIzEHZi6iFATbX8Zhri7dx1UG4YQ55B8109W+PTXxmcR00eoSL5qDcRCZ9g/T+Av3frKugni9IBozjqYSonGxjFdrtEpDGo5EpkhrXvOphVG5kuAW27ykawBvOwSjCXY+fTFMm2DFVKKWGzby19kr8bAk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=36db.4ffdcabc.k1207; bh=cGypl/SkBSSe+0XLuRnzxAfTbhQy948/QihpyfOnzVE=; b=WqrlGIgphMK+87GDa5EmvM4biIqvvYXMVsdpxZNHzjNaTTWLfLiQce6UW4BUdS9b8xSZWHysPvcoRABDFp3RmQw4fcLETT+equAA6w/ieWZqVccZmQC+M4qXLHCtsPWTHqIoGeXJ9OqKZSBSYDWDOPwE4AkZy7bsp17/v8PQV2I=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 11 Jul 2012 18:49:10 -0000
Date: 11 Jul 2012 14:49:30 -0400
Message-ID: <alpine.BSF.2.00.1207111422000.36659@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Andy Newton" <andy@arin.net>
In-Reply-To: <B32EF1A5-3969-4479-AF9B-A75475F66307@arin.net>
References: <20120710212029.77643.qmail@joyce.lan> <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net> <alpine.BSF.2.00.1207111105280.36659@joyce.lan> <B32EF1A5-3969-4479-AF9B-A75475F66307@arin.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 18:49:06 -0000

> I seem to recall a bunch of /8s added into the Whois recently without 
> need of any such mechanism.

I had to hand edit all seven of last year's /8's into my scripts as I 
noted that lookups were failing.  It was a pain.  But, ...

> But I am enjoying the juxtaposition of you arguing that we base a major 
> protocol component on the unfinished plans of ICANN. :)

Aw, come on.  I would prefer that ICANN admit that the giant TLD expansion 
is a mistake, but it's $300 million too late for that.  It seems more 
likely than not that sometime this decade they'll start adding at least 
hundreds of new TLDs every year, which is not something I would want to 
track by hand.  I agree that the problem is considerably less for IPs, but 
since we need to invent something for names, it might as well work 
everywhere.

> Many Whois operators have had SRV records for years, yet the Whois 
> clients that make use of them are in the minority. Using DNS has it 
> problems, and in this instance it is the lack of useful client libraries.

I don't think it's client libraries, SRV is old enough that support for it 
is pretty good.  I checked for SRV records for the 313 TLDs, and found 35, 
of which 32 were for ccTLDs, and one, .gr, pointed at . presumably to say 
they have no WHOIS.  The only gTLDs were .BIZ and .TRAVEL.  People don't 
look for SRV records because the only spec is a draft that expired in 
2003, and that most TLDs don't implement.  I note that .US has one, so 
I'll try putting up a server for my subdomains and see if anyone finds it.

> I can easily think of a bootstrap mechanism easier to implement with 
> tools already required for RESTful Whois than using DNS. A "root" 
> redirect server is only one of them.

Well, OK. Keeping in mind the scaling issue, what do you suggest?

R's,
John

From andy@arin.net  Wed Jul 11 12:14:38 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4773911E8101 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 12:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d1aTp-BpwsRT for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 12:14:37 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 6993E11E80DB for <weirds@ietf.org>; Wed, 11 Jul 2012 12:14:37 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 516992136AF; Wed, 11 Jul 2012 15:15:08 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id D1DBA2136A3; Wed, 11 Jul 2012 15:15:07 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 11 Jul 2012 15:14:34 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Wed, 11 Jul 2012 15:14:46 -0400
From: Andy Newton <andy@arin.net>
To: John R Levine <johnl@taugh.com>
Thread-Topic: [weirds] Redirection in the RESTful WHOIS world
Thread-Index: AQHNW5IHZp05Hg+U/kiz3QFYlCIyNpcdJ5KAgAQlcoCAACxagIAAVgUAgAE3uICAAEh4gIAA1Y4AgABiiICAACLsgIAADSMAgAAG9QA=
Date: Wed, 11 Jul 2012 19:14:24 +0000
Message-ID: <5555FE9B-9747-4CD1-87BD-0459B7C86C2E@arin.net>
References: <20120710212029.77643.qmail@joyce.lan> <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net> <alpine.BSF.2.00.1207111105280.36659@joyce.lan> <B32EF1A5-3969-4479-AF9B-A75475F66307@arin.net> <alpine.BSF.2.00.1207111422000.36659@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1207111422000.36659@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.1.56]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7DE992901756A241BC20AB72671C6490@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 19:14:38 -0000

On Jul 11, 2012, at 2:49 PM, John R Levine wrote:

> I would prefer that ICANN admit that the giant TLD expansion is a mistake=
, but it's $300 million too late for that.

Sounds like a beer topic for Vancouver. :)

> I don't think it's client libraries, SRV is old enough that support for i=
t is pretty good.  I checked for SRV records for the 313 TLDs, and found 35=
, of which 32 were for ccTLDs, and one, .gr, pointed at . presumably to say=
 they have no WHOIS.  The only gTLDs were .BIZ and .TRAVEL.  People don't l=
ook for SRV records because the only spec is a draft that expired in 2003, =
and that most TLDs don't implement.  I note that .US has one, so I'll try p=
utting up a server for my subdomains and see if anyone finds it.

I would suspect that any DNS library that does more than simple name resolu=
tion would do SRV and NAPTR. But the issue is that most client implementers=
 do not have or do not want to use them. They require special knowledge of =
DNS, fail in strange and different ways, and are outside the mainstream of =
what most Internet programmers play with. In short, it does not meet the cr=
iteria of reasonably doable in a bash script.

>> I can easily think of a bootstrap mechanism easier to implement with too=
ls already required for RESTful Whois than using DNS. A "root" redirect ser=
ver is only one of them.
>=20
> Well, OK. Keeping in mind the scaling issue, what do you suggest?

Off the top of my head: a JSON-based, HTTP-fetched hints file with a TTL.

Also, I would not discount redirect servers. I'm sure enterprising individu=
als would love to provide a service that captures those XHTML eyeballs.

-andy=

From johnl@iecc.com  Wed Jul 11 12:48:21 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C347511E80EB for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 12:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.084
X-Spam-Level: 
X-Spam-Status: No, score=-111.084 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GuNeyhmkgVCy for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 12:48:19 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 0659211E80C8 for <weirds@ietf.org>; Wed, 11 Jul 2012 12:48:17 -0700 (PDT)
Received: (qmail 26346 invoked from network); 11 Jul 2012 19:48:47 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Jul 2012 19:48:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffdd89f.xn--hew.k1207; i=johnl@user.iecc.com; bh=EeCArEHo/PDB8ZdNmVktsyJJRM9/fPgAqb9nhq94Y6Y=; b=wxXCxMcXTTwKlagNxJ6EUAP1/w2O7L9glQyiKxPmnHtX86P7riRNyhvP/KOqMMtJAvlUMR1YQSGKlJHwzeHMQu5tvF4AzSjnmjHEXPxEKlisO2nbYijCyt6WZvffl4EJnrgxGjuSqitVvruEgb+AfffUdJKhZ5qxg1DIKly6Ygo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffdd89f.xn--hew.k1207; olt=johnl@user.iecc.com; bh=EeCArEHo/PDB8ZdNmVktsyJJRM9/fPgAqb9nhq94Y6Y=; b=ZCzLKfzZ4SFYOLG7XpoN39egKPBKaC5QDDyEUCPHCHQwJUd/L6+MAG27Ug2R0WFtQEvh8Eldnsja7JYzZxcVZU2uuaYj0Jh2DFld/J0P+2ZQToPi6eQ+nSFsDV/P8fkj2dvWs0VyFXzX01H9KOx1/9uas2b5/Ek4wA4HESapjg8=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 11 Jul 2012 19:48:25 -0000
Message-ID: <20120711194825.47350.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <5555FE9B-9747-4CD1-87BD-0459B7C86C2E@arin.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 19:48:21 -0000

PS:

> In short, it does not meet the criteria of reasonably doable in a bash script.

I don't claim this is beautiful, but it does look up a TLD's SRV
record and call the appropriate server in nine lines of bash.

-------------------------------------
#!/bin/bash

: "${1:?'need domain to look up'}"

a=$(host -t SRV _nicname._tcp."${1##*.}")

case "$a" in
     *"not found"*) echo Cannot find server, you lose; exit 1 ;;
     *"has SRV record"*)
	eval $(echo "$a" | sed -e 's/.* \([0-9][0-9]*\) \(..*\)/port=\1 host=\2/')
	whois -h $host -p $port "$1"
	;;
esac
-------------------------------------

From carlosm3011@gmail.com  Wed Jul 11 12:48:27 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B309911E8142 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 12:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.29
X-Spam-Level: 
X-Spam-Status: No, score=-3.29 tagged_above=-999 required=5 tests=[AWL=-0.310,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u+Csybu5QJwv for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 12:48:27 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2236611E812D for <weirds@ietf.org>; Wed, 11 Jul 2012 12:48:27 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so1759817ghb.31 for <weirds@ietf.org>; Wed, 11 Jul 2012 12:48:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=YpoyMGZ2tWgXhTkvLKBVwOnIcixRayVhJEgRKQOZt7o=; b=Hi+0L0zihC+YVr5CvErCLdgiSqQuuPlFrTAYHpMRZvNcgWiNIik/iQaDuqgX2k2/Ru 8iBrh+0AlkhqSXJg77lyyTHFPy0B1hSIai/y691ddmAYygmJN1RzNMQGNOH8TMKS0yQg QPI6jGMCUG1MSDK0reqpxoTQEg1zhiYq7pFNOCKONyVtmRkPHJVOmWbzt7/Zag6Sw8Dz c/X7KmIyT2JZm1yUqVZMmgFF0j0wZN13CGSvYxGEoEPeMtECh6/71V1jTYDOZdTzvt99 05bd0aBkrF4f8PG+rZcMPHFbLMuH6pNyiq10jEbVH3HMqJpksz8o1AB4igVhoIitcmdG nxrA==
Received: by 10.236.78.39 with SMTP id f27mr57195605yhe.121.1342036138173; Wed, 11 Jul 2012 12:48:58 -0700 (PDT)
Received: from europa.local (r190-135-33-229.dialup.adsl.anteldata.net.uy. [190.135.33.229]) by mx.google.com with ESMTPS id w4sm2462443anh.19.2012.07.11.12.48.55 (version=SSLv3 cipher=OTHER); Wed, 11 Jul 2012 12:48:57 -0700 (PDT)
Message-ID: <4FFDD8A9.4040308@gmail.com>
Date: Wed, 11 Jul 2012 16:48:57 -0300
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: weirds@ietf.org
References: <20120710212029.77643.qmail@joyce.lan> <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net> <alpine.BSF.2.00.1207111105280.36659@joyce.lan> <B32EF1A5-3969-4479-AF9B-A75475F66307@arin.net> <alpine.BSF.2.00.1207111422000.36659@joyce.lan> <5555FE9B-9747-4CD1-87BD-0459B7C86C2E@arin.net>
In-Reply-To: <5555FE9B-9747-4CD1-87BD-0459B7C86C2E@arin.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 19:48:27 -0000

Hi!

On 7/11/12 4:14 PM, Andy Newton wrote:
>
> I would suspect that any DNS library that does more than simple name resolution would do SRV and NAPTR. But the issue is that most client implementers do not have or do not want to use them. They require special knowledge of DNS, fail in strange and different ways, and are outside the mainstream of what most Internet programmers play with. In short, it does not meet the criteria of reasonably doable in a bash script.
Well, I think it is doable on a bash script and using "dig +short" :=)

I can't say anything on the failure side though. I don't have enough
experience in using these records to have an opinion.

While I heartily support the use of non-specialized clients, I don't
think we have to restrict ourselves to what the normal 'Joe SixPack
Programmer' would do.

I believe that after they realize the pain of to manually tracking
1000ths of WHOIS servers by hand, they will do a little reading on those
nifty NAPTRs or SVRs.

Bootstraping via DNS has a lot of nice properties including the
possibility of delegating the authority over the WHOIS data to
operators, DNSSEC signing and of course, caching.
>>> I can easily think of a bootstrap mechanism easier to implement with tools already required for RESTful Whois than using DNS. A "root" redirect server is only one of them.
>> Well, OK. Keeping in mind the scaling issue, what do you suggest?
> Off the top of my head: a JSON-based, HTTP-fetched hints file with a TTL.
Agreed, it could also work. Maybe we need to work a little bit further
on the pros and cons of each approach.
> Also, I would not discount redirect servers. I'm sure enterprising individuals would love to provide a service that captures those XHTML eyeballs.
Well, that was our first approach, documented on
draft-lacnic-weirds-redirects... but well, I received a some  negative
feedback on the idea.
>
> -andy
~Carlos
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds



From olaf@nlnetlabs.nl  Wed Jul 11 13:11:03 2012
Return-Path: <olaf@nlnetlabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63CE221F852C for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wf5C90+Es9nG for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:11:02 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E8BC21F852B for <weirds@ietf.org>; Wed, 11 Jul 2012 13:11:01 -0700 (PDT)
Received: from [192.168.178.34] (peer.kolkman.org [82.95.132.144]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6BKBUaE017664 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <weirds@ietf.org>; Wed, 11 Jul 2012 22:11:31 +0200 (CEST) (envelope-from olaf@nlnetlabs.nl)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1342037491; bh=b1wKd8dBlpBNm4fJiQ2AOlnw1/QLW15OsIa+Uyx+JDU=; h=From:Subject:Date:To; b=DQMZYETKtfLvvLHtPCEKr2BzHEza9R0DvuoixRp8SUCn8AR9cOGIP/QicBbZz3phZ OgDxiT/ljV8bvAAedeGrfUf5Y9DdonsXBN/tjDuU6lVRXQzh4AtInTNec1vo5HoDEO jVfmUmMivQTkx6I4KqX6cFX6Fedk5Oc/TJLARkAw=
From: Olaf Kolkman <olaf@nlnetlabs.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_21642B2B-0AD3-4BC4-9623-9210010F46A0"; protocol="application/pgp-signature"; micalg=pgp-sha1
Date: Wed, 11 Jul 2012 22:11:29 +0200
Message-Id: <CA1018D4-6AA9-4EE1-B85A-F1D7D3BF5A69@nlnetlabs.nl>
To: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Wed, 11 Jul 2012 22:11:31 +0200 (CEST)
Subject: [weirds] Setting the WEIRDS IETF 84 agenda
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 20:11:03 -0000

--Apple-Mail=_21642B2B-0AD3-4BC4-9623-9210010F46A0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii




Dear Colleagues,


We are preparing the agenda for the Vancouver meeting and invite =
requests for agenda slots. But first a few thoughts about the meeting =
and the current agenda.

=3D=3D General agenda/meeting guidelines.

During this meeting and going forward we would like to stick to a few =
guidelines (I am using the word guidelines instead of principles; we do =
not intend to be rigid, only strict with a touch of pragmatism.):

* Agenda items should have associated goals that are actionable for the =
working group and working group participants; the request for an agenda =
item should state that goal and, if possible an expected outcome.

* Working group participants are expected to have an Internet connection =
and come prepared.

In other words, if you are asking for agenda time then please try to =
define what you want to get out of the working group; advice, a =
decision, etc. Also, try to think about what the working group =
participants need in order to drive that decision. It is useful to =
sketch an expected outcome, or describe the alternatives in advance, so =
participants can prepare.  The agenda should contain sufficient =
information so that participants can gather context in a few hours =
preparation time.


=3D=3D First half of the first meeting.

During the first half of the first meeting we would like to try to get =
towards asking and answering ourselves a set of questions that will help =
us organize the work and give us some guidance in the future.

Below is a sketch of the story we want the meeting to tell. In order to =
start a discussion on list I will post separate mails with their own =
subject so that we can summarize discussion that occurred at the =
meeting. The final agenda will provide context through links to the =
archives.

The story begins with building a general understanding what support will =
mean in the context of the data model;  we want to make sure that the =
working group is in sync when we say that the protocol MUST support a =
certain object. There is a potential of talking past each other when we =
are not aligned and that would be impractical, to say the least. (See =
mail with Subject "Supporting Objects")

The second question at hand is service differentiation. Suppose an =
object contains elements that are sensitive and for which the service =
provider has different policies based on authentication (e.g. a CONTACT =
object has a telephone number as element, which according to a local =
policy Law Enforcement must have access to and the general public must =
not have access to). What is a good way to deal with this in a RESTful =
way? The question is an engineering question, answering the general =
approach early on will help us when we are designing the details. (See =
mail with Subject "REST-pect-ful")

The third topic is trying to allow us to define a base-spec and define =
the general approach to version and extend it. Creating a =
base-specificiation with objects that MUST be supported (see first =
topic), which allows for extensions might be useful as it allows us to =
defer the definition of more contentious resources to a version 2 of the =
protocol. Supposing that we want to create extendibility, how do we go =
about it. (This hooks into a thread with Subject "extensibility in =
weirds" and a mail with subject "Category of Objects".)

Fourth, Objects... objects... objects. We need an approach to define =
supported resources. We have already dome some work on making an =
inventory of what is 'out there' (see Subject "Divide and Conquer"). We =
want to show the working group which data has been collected and walk =
away with a definition of the next step.


Fifth, mapping and mapping metadata. Where do clients know where to =
start their lookups? Is this a topic for the working group to consider =
and if so what is a good way. (See mails with Subject "Redirection in =
the RESTful WHOIS world").



=3D=3D Agenda so far=20

This is the agenda as it currently stands can be found at:
http://www.ietf.org/proceedings/84/agenda/agenda-84-weirds





-------

Please send your request for agenda items, possibly fitting within the =
above framework, with a short explanation of what is actionable and what =
is the goal of the agenda item to weirds-chairs@tools.ietf.org.




--Olaf, co-chair


_______________________________________________________=20
Olaf Kolkman -- NLnet Labs
http://www.nlnetlabs.nl/








--Apple-Mail=_21642B2B-0AD3-4BC4-9623-9210010F46A0
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-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQIcBAEBAgAGBQJP/d3xAAoJEFRqER47aqpkohkP/0mUCGar5p0rc0ZrPCRwTc9x
XVRFBo093WN3k6l2J2nntK6Xt/TE80mykzf95lLqRDluVvdBDKu/vvQca3BfOwlY
eiQh+I/Vg4Y8miRNX9es+9mvKxa40p2CLW3lkYb3OOzn0cLsjtSGa/FDXt5BON/l
P9YogriTlyzLuf44xvE3D6kZ1912gGmos4zk+bOuGS55tZYlXJQePYcLgJeu2irO
jUjk3NMu9+OoWBrfHaeIO9iysRApMdNm/b2X1cSbzkfK2kF9XG/XKHzazuNIL0fh
hl8Rv0SpITFVsnay4nevqH0MRt53fY0kh1UDvpTPcS5LCLNAbye2yC4Hl3eiTZxa
7Zqvfieol/55Avf8hxbyLFINTRUA44PULbPEJNsXtqNrtRVNj1kOK4/7kW/8J3my
YXOAtD5DznpnyJ92q4AGyszmjdyadKTE6lMXLJL+dzc12K4sQDV1/yg6y5xuOs7L
u2OqKIJ3GUqGTtCf2lmAM6+nE+yDit5sT6gcH3vppUPtTWKZdO9DP0IRGUEMrZVU
Yq7ECv2I/JTNHiSxe0qZQWeqJPFH0hcQIi/GurWgEAMQENCLx+KalcC8K4iuZdtj
XtIx/pVvll61BPUOHpsCz6t6noM1omGLYeMEWHM9KhTTJk3N4zbULIxYSovvWsfD
C049GHTRCjHq9S61ij9X
=3S+y
-----END PGP SIGNATURE-----

--Apple-Mail=_21642B2B-0AD3-4BC4-9623-9210010F46A0--

From olaf@nlnetlabs.nl  Wed Jul 11 13:11:21 2012
Return-Path: <olaf@nlnetlabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5C1911E80EB for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qF3BbD475mMX for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:11:21 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0566811E80E7 for <weirds@ietf.org>; Wed, 11 Jul 2012 13:11:20 -0700 (PDT)
Received: from [192.168.178.34] (peer.kolkman.org [82.95.132.144]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6BKBUaF017664 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <weirds@ietf.org>; Wed, 11 Jul 2012 22:11:50 +0200 (CEST) (envelope-from olaf@nlnetlabs.nl)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1342037510; bh=LLu6CGpiJnuVcWSisXirxAr4bkDsmEEZ7w/IqqKQe0E=; h=From:Subject:Date:To; b=Ko+qaR1wxnpng2S1amGPuU9RiLm2py2bUETJA+pLkDZ1kytkRHtjbdpAMKoikPyq9 5jAqnKzw/9ArzE3i0LMHZrKanEg3wueBUQln4fK2BpU18NM5cc0SyoYLksnpGFZ5y9 yV1cucq/x6DtaJD15PPd17X+3EnXL5lD6ZfkCqHg=
From: Olaf Kolkman <olaf@nlnetlabs.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_21EA23A1-0D27-4AE5-9FC6-990C2086D43F"; protocol="application/pgp-signature"; micalg=pgp-sha1
Date: Wed, 11 Jul 2012 22:11:39 +0200
Message-Id: <E4291B20-E1ED-4E5C-A0A1-FC96FAF98A0D@nlnetlabs.nl>
To: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Wed, 11 Jul 2012 22:11:50 +0200 (CEST)
Subject: [weirds] Supporting Objects
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 20:11:21 -0000

--Apple-Mail=_21EA23A1-0D27-4AE5-9FC6-990C2086D43F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


Colleagues,

(Also see mail with subject: "Setting the WEIRDS IETF 84 agenda")

When we talk about supporting objects in the context of Weirds it seems =
useful to be in sync about what that means.

I propose that in the context of WEIRDs we talk about MUST support then:
 * the query format is defined
 * the resource format is defined
 * servers MUST be able to parse the request
 * clients MUST be able to parse the answer

However, supporting does not mean that in all cases the objects are =
passed over the wire. Any of the objects may, depending on local policy, =
be refused.

What we are set out to do is to define a data model that supports a =
useful set of objects that can serve environments from the most liberal =
to the most strict local policy.

Is there consensus on the above, does the above need refinement, or is =
this not useful at al?


--Olaf, WEIRDs co-chair



_______________________________________________________=20
Olaf Kolkman -- NLnet Labs
http://www.nlnetlabs.nl/








--Apple-Mail=_21EA23A1-0D27-4AE5-9FC6-990C2086D43F
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-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQIcBAEBAgAGBQJP/d37AAoJEFRqER47aqpk0aEP/jd1PbetJQIqE8yQWUVySV4F
skLk1INTHD+nG3SUJzy1GNT4zmUqBlD3Xc46JO+5czCGbw+iBsy08UkYPbkYroma
txFFSr+3bHy9jioOF6THCotGD8I7XPsb8v264ejWfTYI5Z9+abQYrA7u+HhhGHrY
eRn3Oi2avuLYWNXnG3mvxqy/1Fu0USOvFtEiKJlDDfs295bHfv+L2wU8tLnRz8yw
4Xx+KWArbomrBLPUIbhvdgww4Rk8KJj2OAwRe+Va5zmMKTy5z5f6VEu6zYhy0Qlt
2Mp0xvfgEsaPiotiMFSq3ZSyVDCj5+Z1yiX+c2/MyqILa+dyHTbonxAvswofEdCH
bRpxdeiOEt6QzGfg+gky2DYmwxy1XkyYoGzY5Gn3v1JniedFlj9AIWh/xFh2CIFc
i1VGBEwHpxkyFQhaX2L6AVupM7hTmRuR+8nnPo+Ok6bwnUranfmGcVTXIT+sqCBP
3JsnQCCpEzD7JeXg6y+fl/w1+HSxRIsD1UeQFjZ/LFILcTmAU+urEHrhT2UZoc++
nfNQ1h8AOIf58RQ9ciRXI5v8jjJKQWdK9UdFmcuNGGEBzl2uwQmJcjUvO3exQonv
2VYRHkSzDULQhsVxn8zulxNVHLU0cGThnbJei7FGjxRlp2OEVftUIBl5PHYaRVEP
1AgkEXHUHYu9FBOYjzHf
=PmhC
-----END PGP SIGNATURE-----

--Apple-Mail=_21EA23A1-0D27-4AE5-9FC6-990C2086D43F--

From olaf@nlnetlabs.nl  Wed Jul 11 13:11:43 2012
Return-Path: <olaf@nlnetlabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C264721F852B for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6zGHMFlVkWpD for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:11:43 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B141E21F852C for <weirds@ietf.org>; Wed, 11 Jul 2012 13:11:41 -0700 (PDT)
Received: from [192.168.178.34] (peer.kolkman.org [82.95.132.144]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6BKBUaG017664 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <weirds@ietf.org>; Wed, 11 Jul 2012 22:12:08 +0200 (CEST) (envelope-from olaf@nlnetlabs.nl)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1342037529; bh=K4hTvqTQpmNzYme26ddX6OOAzNwklru3mtJbUdEr+es=; h=From:Subject:Date:To; b=hZGD9TWuzltZMY4uliOn9f9AE8YETXDD8MonKcsb72Ve85HseqQfZSa0OvfsvB3pM XL9rS4C8cyvR5663ms8G81SnyqHrKGb/Y3RsgcjV5fNxmgyhPSHVf1SesTtEKo2vuX ekNpOC4rb6dJlYvidZODj5ceImDdkKaCaAZdpaBY=
From: Olaf Kolkman <olaf@nlnetlabs.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_7BC73EFB-6EE5-45B4-B1CD-6BFE8F6CF091"; protocol="application/pgp-signature"; micalg=pgp-sha1
Date: Wed, 11 Jul 2012 22:11:47 +0200
Message-Id: <1CF8D124-F26C-4F7F-8A05-12C3C2B9BAC3@NLnetLabs.nl>
To: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Wed, 11 Jul 2012 22:12:08 +0200 (CEST)
Subject: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 20:11:43 -0000

--Apple-Mail=_7BC73EFB-6EE5-45B4-B1CD-6BFE8F6CF091
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


(Also see mail with subject: "Setting the WEIRDS IETF 84 agenda")

Colleagues,

I believe that sorting out how to do service differentiation during an =
early stage of protocol development is useful.

What I can see is that at some point there is a resource, an object with =
several elements, for which a local policy of a data provider is that =
some of its clients are required to have access to that information =
while others are required to not gain access. A typical example being =
Contact information whereby a telephone number needs to be made =
available to law-enforcement, while in general that sort of information =
is considered privacy sensitive and is not to be shipped to the general =
public. Note this is an example of a local policy that is not unlikely.

The premise is that we want the protocol to support these sort of policy =
choices (Who sets the policy is not within scope of the working group).

The other premise is that we "use standard features of HTTP to support =
differential service levels to different classes of user." [Charter]

The question is what approach do we take, in general, in order to =
respect the RESTful approach and still differentiate.

It seems that draft-kong-dnrd-ap-response-json section 3.3 uses a =
mechanism that we can base a straw-man on:=20

The resource that is returned as for a query for a contact returns a =
general identifier with elements that contain URIs for the address, =
phone number and other person information. If you want to resolve those =
elements in more detail you will have to do a new query. That query =
might be refused based on authentication.

I wonder if this approach makes sense, and whether there are better =
alternatives being considered.

Anther method I thought of is serve up all elements but fill in =
'REFUSED', or another magic string or code that indicates the client is =
not allowed to see those elements. But that doesn't seem very RESTful =
and I dismissed it.

Questions to the group.

Is the approach as described above (and worked out in Kong et al.'s =
Internet Draft) an approach we can consent on? Are there alternatives? =
Are there issues with this approach that need further thought.

Since the answer to this question sets direction

--Olaf














The output of this discussion could end up in =
draft-designteam-weirds-using-http



_______________________________________________________=20
Olaf Kolkman -- NLnet Labs
http://www.nlnetlabs.nl/








--Apple-Mail=_7BC73EFB-6EE5-45B4-B1CD-6BFE8F6CF091
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-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQIcBAEBAgAGBQJP/d4EAAoJEFRqER47aqpktJsP/1KKtuvofbzjh64g2pDB4k4N
frEPmFl0GwcM3ljHlYGvnONfz74TStCxZMQ1j+8mc8DItpvHMTvl10QWcbWM6Yw2
KyXyl7KUIfZ0wmsYyBl7fwMvymxpiKk6vkBUJPgedb9LGKGfYVaeuRv9i0MSGrwl
0yKMZkYDaq+O9Eq7ku6f09cK7N39N8QnRJy7eIi7vUJuTS8+ozlxhEtec781g8D+
zZQhywmVe+bqpRTIekubsLLwMXx3kuVZfoVDRy5ZWo1Yd25YSvoe99o1q9oZgjBM
BGhN1mLhQ54R9VoWmbceSqxXq2prrsvfrS3I/ia2d1EEcyQnAYzaZXRFgjfRnpDw
Uk1ZYhhZ5fd/dirwMm5VReOG1YrHRvDpctpUBK2qMn2YgZWlWzLiJgrRA6x2AWY0
4CmEis+jilkckm48Qv3/r9XMucqcyF/io8sO0ONO1vIAuiAlKwvpYVuqNylymmnD
wtZ2Y05A3CHbdEXiZsOGbkhEanrnWDruEbRDtUemlHcsIEIkHl2ZMQelbqECxAKf
4XjnCvl7Xg7koz3rWyiYFsTuoXiVPdiauabtosqpPA0LUEmdH0bCdeRBud07esV+
s8RfHJ2SH4CrTWyuMI3AVk6zueSfSaPMoXliRBB84PdVDwsYHoOPFqtPtGrUSH06
DeXddqYeHuHFHtLeo2eC
=9Q/x
-----END PGP SIGNATURE-----

--Apple-Mail=_7BC73EFB-6EE5-45B4-B1CD-6BFE8F6CF091--

From olaf@nlnetlabs.nl  Wed Jul 11 13:11:57 2012
Return-Path: <olaf@nlnetlabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45A6B21F853E for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BRCljOQaMIF5 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:11:56 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F12F21F852B for <weirds@ietf.org>; Wed, 11 Jul 2012 13:11:56 -0700 (PDT)
Received: from [192.168.178.34] (peer.kolkman.org [82.95.132.144]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6BKBUaH017664 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <weirds@ietf.org>; Wed, 11 Jul 2012 22:12:25 +0200 (CEST) (envelope-from olaf@nlnetlabs.nl)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1342037546; bh=m+ZH1Fumm8ri36igPWWLDfdz9tnNqONhg7VvVHPUm8A=; h=From:Subject:Date:To; b=tkn+q2r1fGW/85BfAL4+9ZlSU2VTM0mGCB+gF8E+SCLXcwZtSZcH1ZR5ei8/SJL4j LURQIUUAY3f8rJY6jCPz5QFMuc3SzBfm4fHemVnz21Krg18XzxhH+rXsx4v5dEmDkc nTq4kyIqiMyGyDogz4Ok0CnWMcUMMwU2EeCwjhFM=
From: Olaf Kolkman <olaf@nlnetlabs.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_FC92EB02-DFB1-456B-A103-855AAC09EA5A"; protocol="application/pgp-signature"; micalg=pgp-sha1
Date: Wed, 11 Jul 2012 22:11:54 +0200
Message-Id: <52117471-DC5A-480A-9466-7F48BD0599BF@nlnetlabs.nl>
To: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Wed, 11 Jul 2012 22:12:25 +0200 (CEST)
Subject: [weirds] Category of Objects
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 20:11:57 -0000

--Apple-Mail=_FC92EB02-DFB1-456B-A103-855AAC09EA5A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


Colleagues,

(Also see mail with subject: "Setting the WEIRDS IETF 84 agenda")

The thread on extensibility[1] got me thinking. I am trying to work out =
how the WG approach this problem and get to guiding principles. I do not =
care what the guiding principles are but I would want to prevent a =
situation where we redo the same discussion each time the extensibility =
issue comes to the table.=20

So why don't we try to make a qualification of objects, we can later try =
to map various objects into these classes.

I can think of tree or four types of objects:

* Core Objects.

The types of objects that are supported by the 'core protocol'. One can =
think in terms of MUST and MAYs, if not in the RFC2119 sense than at =
least in the sense that you may reasonably expect them to be implemented =
to have a usable protocol in the first place.

You may want to version the protocol (e.g. through mediatype) if the set =
of core objects changes.=20


* Standardized Extension Objects.

This is the type of object that might not be in wide use but for which =
global standardization is useful. The social media handle comes to mind, =
those are objects with similar semantics that might benefit from uniform =
and standardized representation (e.g. all having the same =
internationalization properties).


* Private Extension Objects (accessible and inaccessible).

If the sender and receiver are part of a small set of users that have =
knowledge of each other than they might want to use extensions that are =
locally defined, lets's call those private extensions for which there is =
no direct need for globally accessible documentation.=20

If the specification is not globally accessible than you may want to =
consider pointers from a global repository (e.g. IANA) to that =
specification. If the specification is non-existent or not accessible =
then just claiming the object name to avoid confusion is useful. That =
could be done in an IANA registry, or with a standardized private naming =
scheme.


If the WG things this is a useful qualification we can work out how to =
deal with these different classes.

--Olaf
  WEIRDS CO-Chair.



[1] http://www.ietf.org/mail-archive/web/weirds/current/msg01225.html


_______________________________________________________=20
Olaf Kolkman -- NLnet Labs
http://www.nlnetlabs.nl/








--Apple-Mail=_FC92EB02-DFB1-456B-A103-855AAC09EA5A
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-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQIcBAEBAgAGBQJP/d4KAAoJEFRqER47aqpk9hQP/26uawbs75fdcUdSUbfB7MJF
aAeqpgBXMTVy3SwMuP4VMcO6yY7TR/ykKBRoaT0Owt49YXw4Lgs9UPckAgRij0NE
beju7gQcaw+q2V1l/Lm6sK6Hs3ui2ayoH2itMUesIPLb94djn92u3tOud1nyEcmM
ZlKu/EPu2nXJMgOlLCNFzf/JY9A9D7FNLz0DZJG714x3SQX2gdv9kPQ1gfvNbT8f
f2WxAO91gCwQyIj1aVKJJ6xEBLJmbVFO8JEsBUCsd1mwwSnjI6NiDxl5KZ5x3DCD
G0JlF5azzPB8mRVF29LhSWLbYwnuqmseuyHw0fn2DKX9lILdHjOlEnTJBF7/IuvO
wG8RVvfFMS7E102il+xvcGIBT1PYk3zt+eg4+lgH81QLzsQm2ly3GmHS1ggTZ0RB
3iZskrfBaEHebLOoZ9/qOvyy8a5iPyBfws01jG8WZG6Pzv0atqphHHFWL00ZOB3E
vMWfEm0yM4Il7/g1DcYeKa5FNMqr44CTL2PFbzeCh+08FTbxBcbKd1SVDJzLrGZA
e5nEW07gdXMVeeJJfrwPP1XK8qHcqk/i/H11mKCsukJvSFuBxLh88jDtrUlyRlvc
KwBvP1aafMZ6Prg12w1WgxRGNU+ti4PmxdmBggs7hQkx8fmUP3kVFS6aOfFM8UoR
XJ/WM1Q5aSdm0+83IPZ7
=nVTU
-----END PGP SIGNATURE-----

--Apple-Mail=_FC92EB02-DFB1-456B-A103-855AAC09EA5A--

From andy@arin.net  Wed Jul 11 13:17:03 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87F9321F859A for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEYpYsGTumti for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:17:03 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id D082621F8598 for <weirds@ietf.org>; Wed, 11 Jul 2012 13:17:02 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id DB7202136A1; Wed, 11 Jul 2012 16:17:33 -0400 (EDT)
Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp2.arin.net (Postfix) with ESMTP id 829AD213650; Wed, 11 Jul 2012 16:17:33 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 11 Jul 2012 16:16:50 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Wed, 11 Jul 2012 16:17:31 -0400
From: Andy Newton <andy@arin.net>
To: John Levine <johnl@taugh.com>
Thread-Topic: [weirds] Redirection in the RESTful WHOIS world
Thread-Index: AQHNW5IHZp05Hg+U/kiz3QFYlCIyNpcdJ5KAgAQlcoCAACxagIAAVgUAgAE3uICAAEh4gIAA1Y4AgABiiICAACLsgIAADSMAgAAG9QCAAAmBgIAACCKA
Date: Wed, 11 Jul 2012 20:17:30 +0000
Message-ID: <33030350-FD89-4C1C-8A8C-34AFA8833F79@arin.net>
References: <20120711194825.47350.qmail@joyce.lan>
In-Reply-To: <20120711194825.47350.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.149.252.97]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BFC0598866300B4886D0B91F5D060292@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 20:17:03 -0000

On Jul 11, 2012, at 3:48 PM, John Levine wrote:

>> In short, it does not meet the criteria of reasonably doable in a bash s=
cript.
>=20
> I don't claim this is beautiful, but it does look up a TLD's SRV
> record and call the appropriate server in nine lines of bash.
>=20
> -------------------------------------
> #!/bin/bash
>=20
> : "${1:?'need domain to look up'}"
>=20
> a=3D$(host -t SRV _nicname._tcp."${1##*.}")
>=20
> case "$a" in
>     *"not found"*) echo Cannot find server, you lose; exit 1 ;;
>     *"has SRV record"*)
> 	eval $(echo "$a" | sed -e 's/.* \([0-9][0-9]*\) \(..*\)/port=3D\1 host=
=3D\2/')
> 	whois -h $host -p $port "$1"
> 	;;
> esac
> -------------------------------------

I said "reasonable". You should evaluate $? instead of the case statement. =
:)

But that's not the complete picture, as HTTP uses URLs and not just domain/=
port pairs. So either incorporate NAPTR or use URI templates. See where thi=
s is going?

-andy=

From johnl@iecc.com  Wed Jul 11 13:17:28 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D40421F8597 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:17:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.091
X-Spam-Level: 
X-Spam-Status: No, score=-111.091 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQtF9J20lXxc for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:17:27 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id B70DF21F8595 for <weirds@ietf.org>; Wed, 11 Jul 2012 13:17:26 -0700 (PDT)
Received: (qmail 33374 invoked from network); 11 Jul 2012 20:17:56 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Jul 2012 20:17:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffddf74.xn--i8sz2z.k1207; i=johnl@user.iecc.com; bh=bdY/z2tj/GR7gkWXoGij3yAtSBLTU9NE6o8AjwFNSmo=; b=UC0man1hbgiKxXv48TW/ErJK/W3XpN3/UAOsr1nVleN7vDESzdEvvF9qLpi5MWDxjIQfei/9TLNzz5Pc6pp0YfUAFCVzlXBdw9YgC2xzBRumIRL5OOXYpjgT/kaGi8povvsX+yfVnn37RxgAP1jms/xyFWXv9G6pl9L5ILzORdc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffddf74.xn--i8sz2z.k1207; olt=johnl@user.iecc.com; bh=bdY/z2tj/GR7gkWXoGij3yAtSBLTU9NE6o8AjwFNSmo=; b=q9MZSDSbMKTHy0qrLqpbzdOUlKarQ5obuXYAUt98XHy4f1IF6W68nlW6BasEjfVo/jwD8ZUcun1E4yFu7b0PzaXl2lY+JIecXFHklV6VjXQmTDYbCgr3bPPX4kaS/3CxLag0l8p67/OUCEwka2KBhGRSts/kAtJc5wYCw0olLMY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 11 Jul 2012 20:17:34 -0000
Message-ID: <20120711201734.48396.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <1CF8D124-F26C-4F7F-8A05-12C3C2B9BAC3@NLnetLabs.nl>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 20:17:28 -0000

 The resource that is returned as for a query for a contact returns a
 general identifier with elements that contain URIs for the address,
 phone number and other person information. If you want to resolve
 those elements in more detail you >will have to do a new query. That
 query might be refused based on authentication.

That could certainly work, but what was one query could now be a
dozen, which seems like a poor idea.

 Anther method I thought of is serve up all elements but fill in
 'REFUSED', or another magic string or code that indicates the client
 is not allowed to see those elements. But that doesn't seem very
 RESTful and I dismissed it.

It's not as elegant, but it seems more practical.

R's,
John

From andy@arin.net  Wed Jul 11 13:18:03 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A0D021F8595 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:18:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GZ9R-kTwOviB for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:18:02 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 933ED21F8593 for <weirds@ietf.org>; Wed, 11 Jul 2012 13:18:02 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 9D6182136A2; Wed, 11 Jul 2012 16:18:33 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id 578F8213650; Wed, 11 Jul 2012 16:18:33 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 11 Jul 2012 16:18:19 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Wed, 11 Jul 2012 16:18:31 -0400
From: Andy Newton <andy@arin.net>
To: "<carlos@lacnic.net>" <carlos@lacnic.net>
Thread-Topic: [weirds] Redirection in the RESTful WHOIS world
Thread-Index: AQHNW5IHZp05Hg+U/kiz3QFYlCIyNpcdJ5KAgAQlcoCAACxagIAAVgUAgAE3uICAAEh4gIAA1Y4AgABiiICAACLsgIAADSMAgAAG9QCAAAmogIAACEKA
Date: Wed, 11 Jul 2012 20:18:30 +0000
Message-ID: <08308387-ED56-42D1-9C63-3BA301C3055F@arin.net>
References: <20120710212029.77643.qmail@joyce.lan> <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net> <alpine.BSF.2.00.1207111105280.36659@joyce.lan> <B32EF1A5-3969-4479-AF9B-A75475F66307@arin.net> <alpine.BSF.2.00.1207111422000.36659@joyce.lan> <5555FE9B-9747-4CD1-87BD-0459B7C86C2E@arin.net> <4FFDD8A9.4040308@gmail.com>
In-Reply-To: <4FFDD8A9.4040308@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.149.252.97]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F4E2FE0168407041992C22AC93B2B7F1@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 20:18:03 -0000

On Jul 11, 2012, at 3:48 PM, Carlos Martinez-Cagnazzo wrote:

>> Also, I would not discount redirect servers. I'm sure enterprising indiv=
iduals would love to provide a service that captures those XHTML eyeballs.
> Well, that was our first approach, documented on
> draft-lacnic-weirds-redirects... but well, I received a some  negative
> feedback on the idea.

As in the Internet should not be commercialized, or was it a technical obje=
ction?

-andy=

From johnl@iecc.com  Wed Jul 11 13:32:36 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BBA911E809A for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.096
X-Spam-Level: 
X-Spam-Status: No, score=-111.096 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3qfBHj1LhXOX for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:32:35 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id AA46F21F85EF for <weirds@ietf.org>; Wed, 11 Jul 2012 13:32:34 -0700 (PDT)
Received: (qmail 36396 invoked from network); 11 Jul 2012 20:33:05 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Jul 2012 20:33:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffde300.xn--3zv.k1207; i=johnl@user.iecc.com; bh=Lwk56UwWUwAP/srFnj+OvugW/BnfRs2a87hAykjdPZo=; b=lr7yknRcqc2xnQ92lXT3a9OlHAhak+e//MkxvK+5Me3PluXXnK/dgCZuGw7Dg7RLtb6+1GH/C3E8hH7bEbDiTHrNqR0W4w5J50vTz/5R2+VLtTad+ZUbqkt1jMIHPavACZpHcqmFsa5VyXo8Xiq7p8RDxnDd1VUJAy8AoKw90Zs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffde300.xn--3zv.k1207; olt=johnl@user.iecc.com; bh=Lwk56UwWUwAP/srFnj+OvugW/BnfRs2a87hAykjdPZo=; b=epVOZnsjzKcF9C1RMNQsOAvapz6bai5Xb4LGjCJfjTWlM5C8oowxwKTq9UTMuzSNvaZNQo3tDDTlkZ39Ao1aVjWHHiPqdhGS7yIrYVwUVyvX7zty1tRDLcjYGcK+1mIDMhDiZzwHq79kyJgGBi22bvIU1AfhFW0lxRRyhcqg3Xs=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 11 Jul 2012 20:32:42 -0000
Message-ID: <20120711203242.48919.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <33030350-FD89-4C1C-8A8C-34AFA8833F79@arin.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 20:32:36 -0000

>> -------------------------------------
>> #!/bin/bash
>> 
>> : "${1:?'need domain to look up'}"
>> 
>> a=$(host -t SRV _nicname._tcp."${1##*.}")
>> 
>> case "$a" in
>>     *"not found"*) echo Cannot find server, you lose; exit 1 ;;
>>     *"has SRV record"*)
>> 	eval $(echo "$a" | sed -e 's/.* \([0-9][0-9]*\) \(..*\)/port=\1 host=\2/')
>> 	whois -h $host -p $port "$1"
>> 	;;
>> esac
>> -------------------------------------
>
>I said "reasonable". You should evaluate $? instead of the case statement. :)

Tsk, tsk. you didn't try it.  The host command returns 0 either way,
so you have to parse what it says.  If you think this is an
unreasonable bash script, you haven't looked at many bash scripts.

The whole bash thing is a red herring, since if WEIRDS is at all
successful, people will use opaque clients where you just put in the
question and it gives you the answer.  We currently wrap rococo shell
scripts around whois commands, but that's only because it's an
underspecified mess, something that with any luck we will fix.

> But that's not the complete picture, as HTTP uses URLs and not just
> domain/port pairs. So either incorporate NAPTR or use URI templates.
> See where this is going?

Down the black hole of excess complexity?  It is perfectly reasonable
for us to specify that all WEIRDS servers accept the same set of query
URLs for the queries they can answer, and respond on port 80, so the
only thing you need to bootstrap is the host name of the server.  That
also makes redirects a lot more straightforward.

Using URI templates would be adding complication only for the sake of
adding complication, since there is no installed base of incompatible
existing RESTful servers that need to be papered over.  Ditto NAPTR.

R's,
John

From johnl@iecc.com  Wed Jul 11 13:34:24 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 359F011E80DB for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:34:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.101
X-Spam-Level: 
X-Spam-Status: No, score=-111.101 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nrFKrFWMtIkI for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:34:23 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 293A711E80A2 for <weirds@ietf.org>; Wed, 11 Jul 2012 13:34:17 -0700 (PDT)
Received: (qmail 36880 invoked from network); 11 Jul 2012 20:34:48 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Jul 2012 20:34:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffde368.xn--btvx9d.k1207; i=johnl@user.iecc.com; bh=bafj7Ht3z1hAf/DxYvB9grxMR61WNw7vUo9EYw1si5g=; b=BWNHEanw/ZCXwkUoWNNg5g+IGM8gOw8ZHJLx6VwVR1iZzd+IaYjSWdV81G9zVQ7YJN5IXf1csz9RhY7aJu9+NecWBFWnMTz/Fn7ov1932pE2up4WJkXuuq6ifbujypU66DIWbhvAmXGCoDMvfKgjc94ce8hhC9MxehQ1krrwKL0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4ffde368.xn--btvx9d.k1207; olt=johnl@user.iecc.com; bh=bafj7Ht3z1hAf/DxYvB9grxMR61WNw7vUo9EYw1si5g=; b=Bq1MhPkmB4wWEw+yK6SJ4NWimhanDRJoAFTm53pHny4scE1bCZJzqgMhN3d6ghKpX3lhvDdaVay9wIi9Snu2Bsg6876YVi+6jAU+3OxKmZ8Vjjyw5HQeD18sH1WElWSBPCP5OfjlRmSAWf4FKvF+k02Hs93eFBsjF2vSjSBKeAQ=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 11 Jul 2012 20:34:26 -0000
Message-ID: <20120711203426.48999.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <08308387-ED56-42D1-9C63-3BA301C3055F@arin.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 20:34:24 -0000

>>> Also, I would not discount redirect servers. I'm sure enterprising individuals would love to provide a service that
>captures those XHTML eyeballs.
>> Well, that was our first approach, documented on
>> draft-lacnic-weirds-redirects... but well, I received a some  negative
>> feedback on the idea.
>
>As in the Internet should not be commercialized, or was it a technical objection?

Perhaps as in, it would be nice if everyone who asked the same question got the
same answer.

Hey, I have a great idea!  I bet a lot of enterprising people would love to provide
an alternative DNS root server, too.

R's,
John


From andy@arin.net  Wed Jul 11 13:38:56 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 509DE21F8636 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:38:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0C5HSYZPtoN for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:38:55 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id DA78A21F8628 for <weirds@ietf.org>; Wed, 11 Jul 2012 13:38:49 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id C8F681651A1; Wed, 11 Jul 2012 16:39:20 -0400 (EDT)
Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp1.arin.net (Postfix) with ESMTP id 6E92516515A; Wed, 11 Jul 2012 16:39:20 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 11 Jul 2012 16:38:37 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Wed, 11 Jul 2012 16:39:19 -0400
From: Andy Newton <andy@arin.net>
To: John Levine <johnl@taugh.com>
Thread-Topic: [weirds] REST-pect-ful
Thread-Index: AQHNX6F71F8aVuhTGkWUHYArFUAeHZckyDQAgAAGEwA=
Date: Wed, 11 Jul 2012 20:39:18 +0000
Message-ID: <D3D8582E-BE04-4BCF-88D9-B73A3813003E@arin.net>
References: <20120711201734.48396.qmail@joyce.lan>
In-Reply-To: <20120711201734.48396.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.149.252.97]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E64F45E55E930B44975B40D8BE25FBDF@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 20:38:56 -0000

On Jul 11, 2012, at 4:17 PM, John Levine wrote:

> The resource that is returned as for a query for a contact returns a
> general identifier with elements that contain URIs for the address,
> phone number and other person information. If you want to resolve
> those elements in more detail you >will have to do a new query. That
> query might be refused based on authentication.
>=20
> That could certainly work, but what was one query could now be a
> dozen, which seems like a poor idea.

I agree with this. Not only does it add load to the service, but experience=
 has shown people don't like requiring for the same information.

> Anther method I thought of is serve up all elements but fill in
> 'REFUSED', or another magic string or code that indicates the client
> is not allowed to see those elements. But that doesn't seem very
> RESTful and I dismissed it.
>=20
> It's not as elegant, but it seems more practical.

I lean more toward this approach as well. Though filling strings with "REFU=
SED" just leads some to think that a persons last name might be "REFUSED", =
a notice somewhere in the response noting information has been redacted and=
 pointing toward a policy document is fairly helpful.

-andy=

From andy@arin.net  Wed Jul 11 13:58:29 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9947B21F852E for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BrwUCDtsAkbs for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 13:58:29 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id D9D9A21F852D for <weirds@ietf.org>; Wed, 11 Jul 2012 13:58:28 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id EC0902136A3; Wed, 11 Jul 2012 16:58:59 -0400 (EDT)
Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp2.arin.net (Postfix) with ESMTP id 7394321363C; Wed, 11 Jul 2012 16:58:59 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 11 Jul 2012 16:58:10 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Wed, 11 Jul 2012 16:58:52 -0400
From: Andy Newton <andy@arin.net>
To: John Levine <johnl@taugh.com>
Thread-Topic: [weirds] Redirection in the RESTful WHOIS world
Thread-Index: AQHNW5IHZp05Hg+U/kiz3QFYlCIyNpcdJ5KAgAQlcoCAACxagIAAVgUAgAE3uICAAEh4gIAA1Y4AgABiiICAACLsgIAADSMAgAAG9QCAAAmBgIAACCKAgAAEPgCAAAdOgA==
Date: Wed, 11 Jul 2012 20:58:50 +0000
Message-ID: <9FC1FEF3-EE0D-4CF4-BA6E-DE2A12ACB092@arin.net>
References: <20120711203242.48919.qmail@joyce.lan>
In-Reply-To: <20120711203242.48919.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.149.252.97]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <DB9C7E5532BD964087F789639D220818@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 20:58:29 -0000

On Jul 11, 2012, at 4:32 PM, John Levine wrote:

> Tsk, tsk. you didn't try it.  The host command returns 0 either way,
> so you have to parse what it says.

Not on my system.

>  If you think this is an
> unreasonable bash script, you haven't looked at many bash scripts.

touch=E9!

> The whole bash thing is a red herring, since if WEIRDS is at all
> successful, people will use opaque clients where you just put in the
> question and it gives you the answer.  We currently wrap rococo shell
> scripts around whois commands, but that's only because it's an
> underspecified mess, something that with any luck we will fix.

No, I don't think so. That's not how Whois works today, and I have an apach=
e log file of user agents against our RESTful Whois service that clearly sh=
ows people are using all sorts of languages to script these things=85 the b=
iggest being Javascript. My use of the bash script example is to make peopl=
e think before adding complexity into the protocol.

BTW, are there in-brower Javascript DNS solutions? I've not looked into tha=
t.

>> But that's not the complete picture, as HTTP uses URLs and not just
>> domain/port pairs. So either incorporate NAPTR or use URI templates.
>> See where this is going?
>=20
> Down the black hole of excess complexity?  It is perfectly reasonable
> for us to specify that all WEIRDS servers accept the same set of query
> URLs for the queries they can answer, and respond on port 80, so the
> only thing you need to bootstrap is the host name of the server.  That
> also makes redirects a lot more straightforward.

What about port 443? What about hosting this on the same cluster as my othe=
r web systems?

> Using URI templates would be adding complication only for the sake of
> adding complication, since there is no installed base of incompatible
> existing RESTful servers that need to be papered over.  Ditto NAPTR.

No each solves the URL mapping problem given to us by SRV records.

-andy=

From johnl@taugh.com  Wed Jul 11 14:43:40 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8AD921F862A for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 14:43:40 -0700 (PDT)
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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UxN14cSb4BGt for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 14:43:39 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 30BBF21F8607 for <weirds@ietf.org>; Wed, 11 Jul 2012 14:43:38 -0700 (PDT)
Received: (qmail 50835 invoked from network); 11 Jul 2012 21:44:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=c692.4ffdf3a9.k1207; bh=mp9GGBIwVbBNjLwV8j89OL7J9TPli81kl2Z1pI1j3VQ=; b=a6qCVEIpiCqStFCFz+PJxv2IzglgK6o5az2s8jbJHedAX7SMQq/DIMkFFNYvYxd2/jybtBlRgI0Ex17q8R1z7qwj6OaM+YEIkQOcsbOCkpfgCTULPZl0rBPe3gg0NPI/T+vI5Z408bOAbqXrKmp8UyozrGfaAcKu9F2Cz9QwtEg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=c692.4ffdf3a9.k1207; bh=mp9GGBIwVbBNjLwV8j89OL7J9TPli81kl2Z1pI1j3VQ=; b=Q6Udtxak4wKcCQs5CDuO8lFi4B8zALMzw17+32fCOS1H1IqWp4Wg/zDetpqkUEBlO8VXBR8HiADKaUF0AGsjPNsP8gF2cowyb94JiYRoI+lu6y6jeop3ZDu2eyu11QFSt+ahcCVVFdcFEQf8B4ORKTVEkiLbx6mTXj5ayUY8pPc=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 11 Jul 2012 21:43:47 -0000
Date: 11 Jul 2012 17:44:09 -0400
Message-ID: <alpine.BSF.2.00.1207111728450.47528@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Andy Newton" <andy@arin.net>
In-Reply-To: <9FC1FEF3-EE0D-4CF4-BA6E-DE2A12ACB092@arin.net>
References: <20120711203242.48919.qmail@joyce.lan> <9FC1FEF3-EE0D-4CF4-BA6E-DE2A12ACB092@arin.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="3825401791-128788950-1342043049=:47528"
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 21:43:40 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-128788950-1342043049=:47528
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

>> Tsk, tsk. you didn't try it.  The host command returns 0 either way,
>> so you have to parse what it says.
>
> Not on my system.

Gotta love that portability.

> No, I don't think so. That's not how Whois works today, and I have an apa=
che log file of user agents against our RESTful Whois service that clearly =
shows people are using all sorts of languages to script these things=E2=80=
=A6 the biggest being Javascript. My use of the bash script example is to m=
ake people think before adding complexity into the protocol.

> BTW, are there in-brower Javascript DNS solutions? I've not looked into t=
hat.

Hmmn, a little googlage suggests that there aren't. You'd have to call
out to some web site that will do the lookup for you which rather
defeats the purpose.  I suppose one could use a CNAME kludge of
<tld>.wierdsservers.net or <1.2.3.4.5.6>.weirdsservers.net, analogous
to Rodney's whoisservers.net, that doesn't require a lookup before the
http query.  I don't unalterably hate a daily or weekly pull of a
master JSON file, but it seems more fragile, particularly if we hope that
clients will cache it reasonably, i.e., for more than one query, but not
forever.

>> Down the black hole of excess complexity?  It is perfectly reasonable
>> for us to specify that all WEIRDS servers accept the same set of query
>> URLs for the queries they can answer, and respond on port 80, so the
>> only thing you need to bootstrap is the host name of the server.  That
>> also makes redirects a lot more straightforward.
>
> What about port 443?

Sorry, 443 is better.

> What about hosting this on the same cluster as my other web systems?

So get another IP.  The going price is $1/month.  It's hard for me to
imagine an organization large enough that it's worth publishing WHOIS
info, yet so tiny that they can't find a spare IP.

> No each solves the URL mapping problem given to us by SRV records.

What URL mapping problem?  You look up the domain or high bits of the
IP, plug the server host name you get back into the URL, and make your
query.  That server might redirect you, but we know how to deal with
that.

There will be a thousand times as many WIERDS clients as servers, so
given a tradeoff between making it easier to set up a server and
making it easier to do a query, I'll pick the easier query every time.

R's,
John
--3825401791-128788950-1342043049=:47528--

From james.mitchell@ausregistry.com.au  Wed Jul 11 20:06:27 2012
Return-Path: <james.mitchell@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3034A11E80A1 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 20:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zkIhpHdBY6ug for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 20:06:26 -0700 (PDT)
Received: from mx02.ausregistry.net.au (mx02.ausregistry.net.au [202.65.15.42]) by ietfa.amsl.com (Postfix) with ESMTP id AE84711E80DC for <weirds@ietf.org>; Wed, 11 Jul 2012 20:06:18 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron02.off08.stkildard.vic.ausregistry.com.au with ESMTP; 12 Jul 2012 13:06:48 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Thu, 12 Jul 2012 13:06:35 +1000
From: James Mitchell <james.mitchell@ausregistry.com.au>
To: Andy Newton <andy@arin.net>, John Levine <johnl@taugh.com>
Date: Thu, 12 Jul 2012 13:06:45 +1000
Thread-Topic: [weirds] REST-pect-ful
Thread-Index: Ac1f21ha9wrta1uzTdGaE9Iqoa6z2A==
Message-ID: <CC245AB3.12E9B%james.mitchell@ausregistry.com.au>
In-Reply-To: <D3D8582E-BE04-4BCF-88D9-B73A3813003E@arin.net>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 03:06:27 -0000

+1 to the notice concept for the reasons Andy raised.

Using .au whois as an example, only registrant and technical contact name
and email are available via whois-like interfaces (port-43 and web),
however email is withheld to port-43 clients. Administrative and billing
contacts are never returned, nor is any specific data relating to the
registrant or tech contacts (phone, fax, address etc).

There a distinction between data that is never available and data has been
withheld from a specific interface. DENIC also has similar behaviours IIRC.

James


On 12/07/12 6:39 AM, "Andy Newton" <andy@arin.net> wrote:

>
>On Jul 11, 2012, at 4:17 PM, John Levine wrote:
>
>> The resource that is returned as for a query for a contact returns a
>> general identifier with elements that contain URIs for the address,
>> phone number and other person information. If you want to resolve
>> those elements in more detail you >will have to do a new query. That
>> query might be refused based on authentication.
>>=20
>> That could certainly work, but what was one query could now be a
>> dozen, which seems like a poor idea.
>
>I agree with this. Not only does it add load to the service, but
>experience has shown people don't like requiring for the same information.
>
>> Anther method I thought of is serve up all elements but fill in
>> 'REFUSED', or another magic string or code that indicates the client
>> is not allowed to see those elements. But that doesn't seem very
>> RESTful and I dismissed it.
>>=20
>> It's not as elegant, but it seems more practical.
>
>I lean more toward this approach as well. Though filling strings with
>"REFUSED" just leads some to think that a persons last name might be
>"REFUSED", a notice somewhere in the response noting information has been
>redacted and pointing toward a policy document is fairly helpful.
>
>-andy
>_______________________________________________
>weirds mailing list
>weirds@ietf.org
>https://www.ietf.org/mailman/listinfo/weirds


From patrick@vande-walle.eu  Wed Jul 11 23:19:46 2012
Return-Path: <patrick@vande-walle.eu>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D86F21F8722 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 23:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IuZ6V9EvABr2 for <weirds@ietfa.amsl.com>; Wed, 11 Jul 2012 23:19:45 -0700 (PDT)
Received: from lucifer.abilit.eu (lucifer.abilit.eu [85.93.218.208]) by ietfa.amsl.com (Postfix) with ESMTP id E918021F871D for <weirds@ietf.org>; Wed, 11 Jul 2012 23:19:44 -0700 (PDT)
Received: from mail2.isoc.lu (ISOC.abilit.eu [10.10.13.199]) by lucifer.abilit.eu (Postfix) with ESMTPS id 875E53408F2 for <weirds@ietf.org>; Thu, 12 Jul 2012 08:20:14 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail2.isoc.lu (Postfix) with ESMTP id 6EF0E300551 for <weirds@ietf.org>; Thu, 12 Jul 2012 08:20:14 +0200 (CEST)
Received: from mail2.isoc.lu ([127.0.0.1]) by localhost (mail2.isoc.lu [127.0.0.1]) (maiad, port 10024) with ESMTP id 19337-08 for <weirds@ietf.org>; Thu, 12 Jul 2012 08:19:58 +0200 (CEST)
Received: from Cioran.vande-walle.eu (cl-310.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:135::2]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: patrick@vande-walle.eu) by mail2.isoc.lu (Postfix) with ESMTPSA id F05733004A3 for <weirds@ietf.org>; Thu, 12 Jul 2012 08:19:56 +0200 (CEST)
VBR-Info: md=vande-walle.eu; mc=all; mv=dwl.spamhaus.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=vande-walle.eu; s=Sig; t=1342073997; bh=teUf1z4GA/BIsXiFqyfciq3atV+qNjIUQryP+H7AkEY=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=Q9zgjMTr0UtjFRYkSb1UMWWY7ARdJBla/xcQe1QxQRwqOCVF5DbCF/oNs+3xUU/jN Lcia4C1c4NJfWo6+KXxSro1X6hzDPxuilnQQm5aMMepMunu97Fc5lCrnaWRyjQmfKB 5MUv0IE1b+rA99yatFPm+Y1kJOgb3oWbHTW1y9Y4=
Received: from [127.0.0.1] (localhost [127.0.0.1]) by Cioran.vande-walle.eu (Postfix) with ESMTP id E0923240C4B for <weirds@ietf.org>; Thu, 12 Jul 2012 08:19:50 +0200 (CEST)
Message-ID: <4FFE6C86.8040504@vande-walle.eu>
Date: Thu, 12 Jul 2012 08:19:50 +0200
From: Patrick Vande Walle <patrick@vande-walle.eu>
Organization: My own disorganization
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: "<weirds@ietf.org>" <weirds@ietf.org>
References: <20120711201734.48396.qmail@joyce.lan> <D3D8582E-BE04-4BCF-88D9-B73A3813003E@arin.net>
In-Reply-To: <D3D8582E-BE04-4BCF-88D9-B73A3813003E@arin.net>
X-Enigmail-Version: 1.4.2
Content-Type: multipart/alternative; boundary="------------070705060202010409070508"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.3.4 (mail2.isoc.lu [0.0.0.0]); Thu, 12 Jul 2012 08:19:57 +0200 (CEST)
X-Virus-Scanned: Maia Mailguard 1.0.3
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: patrick@vande-walle.eu
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 06:19:46 -0000

This is a multi-part message in MIME format.
--------------070705060202010409070508
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Agree with Andy   and others that multiple queries may  cause additional
load that could possibly be avoided. 

On 11/07/12 22:39, Andy Newton wrote:
> I lean more toward this approach as well. Though filling strings with
> "REFUSED" just leads some to think that a persons last name might be
> "REFUSED",

Indeed. Especially if that person's name happens to be "Refused", which
could happen.  I do not like the idea of having magic strings in lieu of
field data. 
In the case of a field whose content should be hidden by policy, I
suggest the field data should  be empty, but we could add an optional
sub-structure related to policy.

I just made up the example below for the purpose of demonstration: 

{
    "BillingTelNum": {
        "Description": "Billing Contact phone number",
        "TelNum":
              "Data": "",    
            "Policy": {
                "Status": "REDACTED",
                "Info": "See http://www.example.org/weirds-policy"
                }}}}}

Patrick Vande Walle


--------------070705060202010409070508
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000066">
    Agree with Andy&nbsp;&nbsp; and others that multiple queries may&nbsp; cause
    additional load that could possibly be avoided.&nbsp; <br>
    <br>
    <div class="moz-cite-prefix">On 11/07/12 22:39, Andy Newton wrote:<br>
    </div>
    <blockquote cite="mid:D3D8582E-BE04-4BCF-88D9-B73A3813003E@arin.net"
      type="cite">I lean more toward this approach as well. Though
      filling strings with "REFUSED" just leads some to think that a
      persons last name might be "REFUSED",</blockquote>
    <br>
    Indeed. Especially if that person's name happens to be "Refused",
    which could happen.&nbsp; I do not like the idea of having magic strings
    in lieu of field data.&nbsp; <br>
    In the case of a field whose content should be hidden by policy, I
    suggest the field data should&nbsp; be empty, but we could add an
    optional sub-structure related to policy.<br>
    <br>
    I just made up the example below for the purpose of demonstration:&nbsp;
    <br>
    <br>
    {<br>
    &nbsp;&nbsp;&nbsp; "BillingTelNum": {<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "Description": "Billing Contact phone number",<br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; "TelNum": <br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "Data": "",&nbsp;&nbsp;&nbsp;&nbsp; <br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; "Policy": {<br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; "Status": "REDACTED",<br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; "Info": "See <a class="moz-txt-link-freetext"
      href="http://www.example.org/weirds-policy">http://www.example.org/weirds-policy</a>"<br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; }}}}}<br>
    <br>
    Patrick Vande Walle<br>
    <br>
  </body>
</html>

--------------070705060202010409070508--

From sm@resistor.net  Thu Jul 12 01:18:20 2012
Return-Path: <sm@resistor.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBBAF21F8596 for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 01:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LoG4jEo4mCGB for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 01:18:16 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C353921F8496 for <weirds@ietf.org>; Thu, 12 Jul 2012 01:18:10 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q6C8IbrC001117 for <weirds@ietf.org>; Thu, 12 Jul 2012 01:18:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1342081121; bh=r4OwugceOV8bFaFWL2UU0YxkNuWJyDr2RmUVEXM290M=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=u3WzmZYRLi90eAil9aACVsKnNevapezXy8Qn/x9jH1gbcu31F7OQcAiwnsSrjhcfp 6TRFjG0q+JH+duHxb+oihc6KpSpisba4Mw5Kr79KXuIULQdAsRxob5uG5aDHlndxJ3 yPVc7jt3I9qPaRz1HZnmtnYpBZENGtA9dnDRBVHE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1342081121; i=@resistor.net; bh=r4OwugceOV8bFaFWL2UU0YxkNuWJyDr2RmUVEXM290M=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=nUTKO9JnxnO9oFJBts6i2nyXGTwHziPoXYdx2nrSIK2+vonxXjutcj01GcX/lBPc6 QW1B9S3F8DylylX1+Rd6B8Y7adahqOMq3+mWABPQgWPpobt12RY44QE7c15xeXvrZm 1Hz3z8F9S4PgVyOcaED8sZwKcUtRRJ/2lfTRi6ow=
Message-Id: <6.2.5.6.2.20120712002759.095d8d68@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 12 Jul 2012 01:18:31 -0700
To: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
From: SM <sm@resistor.net>
In-Reply-To: <CA1018D4-6AA9-4EE1-B85A-F1D7D3BF5A69@nlnetlabs.nl>
References: <CA1018D4-6AA9-4EE1-B85A-F1D7D3BF5A69@nlnetlabs.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [weirds] Setting the WEIRDS IETF 84 agenda
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 08:18:20 -0000

At 13:11 11-07-2012, Olaf Kolkman wrote:
>The second question at hand is service differentiation. Suppose an 
>object contains elements that are sensitive and for which the 
>service provider has different policies based on authentication 
>(e.g. a CONTACT object has a telephone number as element, which 
>according to a local policy Law Enforcement must have access to and 
>the general public must not have access to). What is a good way to 
>deal with this in a RESTful way? The

I am not suggesting this subject for IETF 84.  I stumbled across the 
following gem: A mobile phone number on its own is not classed as 
"personally identifying information" ( 
http://www.guardian.co.uk/technology/2012/jan/25/02-mobile-phone-users-privacy-breach-website 
) some time back.

Would an analysis of the information identified in the WEIRDS 
specification (e.g. CONTACT object) be required or can the rodent 
hole be avoided?  Note that the question is from an IETF perspective.

regards,
-sm 


From olaf@NLnetLabs.nl  Thu Jul 12 01:57:24 2012
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63B6921F87B0 for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 01:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t+GSLSu-lpIA for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 01:57:23 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BABC521F87AB for <weirds@ietf.org>; Thu, 12 Jul 2012 01:57:22 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14] ([IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6C8voYV086214 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 12 Jul 2012 10:57:51 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1342083473; bh=DXkQrtMtwuacwgTW+tYbvgN9BvdTcDtXU++viJ93yKo=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=aJee2lrfbIDhZMmKkivm0pyKyaRXMUJnE/31VFth5xZILo0O6KXVQe2wjaCqDVSQY icFZ8Hv+samHCCSoMp/iEazQ/q+NsVhH7HtK02JFcffH5vsgbL6+nDrw37Y+SSttOC vL8628ZndqxdLvM9AidnLCYY1yNgHJ3rULXaKLKM=
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_042D7F4A-41C5-49BC-A316-705F5CF00033"; protocol="application/pgp-signature"; micalg=pgp-sha1
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <6.2.5.6.2.20120712002759.095d8d68@resistor.net>
Date: Thu, 12 Jul 2012 10:57:50 +0200
Message-Id: <37C79CAA-7BB3-448B-A5F7-BC368EDF3A98@NLnetLabs.nl>
References: <CA1018D4-6AA9-4EE1-B85A-F1D7D3BF5A69@nlnetlabs.nl> <6.2.5.6.2.20120712002759.095d8d68@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Thu, 12 Jul 2012 10:57:52 +0200 (CEST)
Cc: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Subject: Re: [weirds] Setting the WEIRDS IETF 84 agenda
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 08:57:24 -0000

--Apple-Mail=_042D7F4A-41C5-49BC-A316-705F5CF00033
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_9F02AC9F-080D-45BA-8853-2D2C914A5BF5"


--Apple-Mail=_9F02AC9F-080D-45BA-8853-2D2C914A5BF5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jul 12, 2012, at 10:18 AM, SM wrote:

> At 13:11 11-07-2012, Olaf Kolkman wrote:
>> The second question at hand is service differentiation. Suppose an =
object contains elements that are sensitive and for which the service =
provider has different policies based on authentication (e.g. a CONTACT =
object has a telephone number as element, which according to a local =
policy Law Enforcement must have access to and the general public must =
not have access to). What is a good way to deal with this in a RESTful =
way? The
>=20
> I am not suggesting this subject for IETF 84.  I stumbled across the =
following gem: A mobile phone number on its own is not classed as =
"personally identifying information" =
(http://www.guardian.co.uk/technology/2012/jan/25/02-mobile-phone-users-pr=
ivacy-breach-website ) some time back.
>=20
> Would an analysis of the information identified in the WEIRDS =
specification (e.g. CONTACT object) be required or can the rodent hole =
be avoided?  Note that the question is from an IETF perspective.


For now the question is how to deal with the situation where some =
elements of an object might be privacy sensitive. In other words, lets =
define the general mechanism first.


Later on, I am sure, we may see differences of opinions about what =
elements in objects might be interpreted as privacy sensitive. That is =
where we have to find a careful balance between the protocol enforcing =
policy and allowing policy to be enforced.

<wg-participant co-chair-hat=3Doff opinion=3Dpersonal>
If the protocol enforces an element in an object to be served in all =
cases then the protocol might not be deployable under certain policy =
regimes and we loose. Allowing for the policy tussle to be played out =
during deployment is probably a better model.
</wg-participant>

Being my optimistic self I think that there will be rough consensus on =
which elements are privacy sensitive and thus more likely subject to =
differential service: when it looks, smells and feels like privacy =
sensitive, it probably is. Trying to answer your question: I would like =
to postpone the analysis because it might happen more or less implicit =
during the process, and might be easier once we sort out how to engineer =
the differentiation.

--Olaf

NLnet
Labs
Olaf M. Kolkman

www.NLnetLabs.nl
olaf@NLnetLabs.nl

Science Park 400, 1098 XH Amsterdam, The Netherlands




--Apple-Mail=_9F02AC9F-080D-45BA-8853-2D2C914A5BF5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 12, 2012, at 10:18 AM, SM wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Monaco; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">At 13:11 =
11-07-2012, Olaf Kolkman wrote:<br><blockquote type=3D"cite">The second =
question at hand is service differentiation. Suppose an object contains =
elements that are sensitive and for which the service provider has =
different policies based on authentication (e.g. a CONTACT object has a =
telephone number as element, which according to a local policy Law =
Enforcement must have access to and the general public must not have =
access to). What is a good way to deal with this in a RESTful way? =
The<br></blockquote><br>I am not suggesting this subject for IETF 84. =
&nbsp;I stumbled across the following gem: A mobile phone number on its =
own is not classed as "personally identifying information" (<a =
href=3D"http://www.guardian.co.uk/technology/2012/jan/25/02-mobile-phone-u=
sers-privacy-breach-website">http://www.guardian.co.uk/technology/2012/jan=
/25/02-mobile-phone-users-privacy-breach-website</a><span =
class=3D"Apple-converted-space">&nbsp;</span>) some time =
back.<br><br>Would an analysis of the information identified in the =
WEIRDS specification (e.g. CONTACT object) be required or can the rodent =
hole be avoided? &nbsp;Note that the question is from an IETF =
perspective.</span></blockquote><br></div><div><br></div><div>For now =
the question is how to deal with the situation where some elements of an =
object might be privacy sensitive. In other words, lets define the =
general mechanism first.</div><div><br></div><div><br></div><div>Later =
on, I am sure, we may see differences of opinions about what elements in =
objects might be interpreted as privacy sensitive. That is where we have =
to find a careful balance between the protocol enforcing policy and =
allowing policy to be =
enforced.</div><div><br></div><div>&lt;wg-participant co-chair-hat=3Doff =
opinion=3Dpersonal&gt;</div><div>If the protocol enforces an element in =
an object to be served in all cases then the protocol might not be =
deployable under certain policy regimes and we loose. Allowing for the =
policy tussle to be played out during deployment is probably a better =
model.</div><div>&lt;/wg-participant&gt;</div><div><br></div><div>Being =
my optimistic self I think that there will be rough consensus on which =
elements are privacy sensitive and thus more likely subject to =
differential service: when it looks, smells and feels like privacy =
sensitive, it probably is. Trying to answer your question:&nbsp;I would =
like to postpone the analysis because it might happen more or less =
implicit during the process, and might be easier once we sort out how to =
engineer the differentiation.</div><div><br></div><div>--Olaf</div><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Helvetica; font-size: =
12px; "><br class=3D"Apple-interchange-newline"><table cellspacing=3D"0" =
cellpadding=3D"0" style=3D"background-color: rgb(255, 255, 255); =
border-collapse: collapse; "><tbody><tr><td rowspan=3D"2" valign=3D"top" =
style=3D"width: 97.8px; height: 56.3px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; text-align: right; font: normal normal normal =
19px/normal 'Gill Sans'; "><font class=3D"Apple-style-span" =
color=3D"#777777"><span style=3D"letter-spacing: 0px; =
"><b>NLnet<br></b></span><span style=3D"font: normal normal normal =
24px/normal 'Gill Sans'; letter-spacing: 0px; =
">Labs</span></font></div></td><td valign=3D"top" style=3D"width: =
114.5px; height: 18.1px; border-top-style: solid; border-right-style: =
solid; border-bottom-style: solid; border-left-style: solid; =
border-top-width: 1px; border-right-width: 0px; border-bottom-width: =
1px; border-left-width: 0px; border-top-color: rgb(180, 180, 180); =
border-right-color: transparent; border-bottom-color: rgb(202, 202, =
202); border-left-color: transparent; padding-top: 5px; padding-right: =
5px; padding-bottom: 5px; padding-left: 5px; "><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 12px/normal Helvetica; "><span =
style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Olaf M. Kolkman</font></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 18.1px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 1px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: rgb(202, 202, 202); border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td valign=3D"top" =
style=3D"width: 114.5px; height: 27.2px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"http://www.NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">www.NLnetLabs.nl</font></a></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"mailto:olaf@NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">olaf@NLnetLabs.nl</font></a></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 27.2px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td colspan=3D"3" =
valign=3D"top" style=3D"width: 234.6px; height: 13.2px; padding-top: =
5px; padding-right: 5px; padding-bottom: 5px; padding-left: 5px; "><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Science Park 400, 1098 XH Amsterdam, The =
Netherlands</font></span></div></td></tr></tbody></table><div =
style=3D"color: rgb(158, 158, 158); margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_9F02AC9F-080D-45BA-8853-2D2C914A5BF5--

--Apple-Mail=_042D7F4A-41C5-49BC-A316-705F5CF00033
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-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQIcBAEBAgAGBQJP/pGOAAoJEFRqER47aqpkZ4oP/RzlsfmBYRC2MGcbiSQ+sh55
W34r4q81q0A2qr/mRI3U3uC6oPiXsjdSbfW3X5ejc6GRRNc841IJNLqILntTItgc
aUGckx3Wgzp8mDlbixTXHRIokpZBpoTfoEIx2sFQgQIm9ctZU5VVGaAzCZpUSCgx
17HFbmIVbLP8x+ntIdFDDkbd2kpWfMeMs3ectMhM6dFqjdbCiaUOZ2GATKdhXmIT
DxtyAoe/mGJBttaR6nA2Nkub35ZadLPcrkDv1IBvjeoExCLqvFq1KQLJPpNKiWeG
BQnPvqvBB628RoCqTPmD3BPfvcLHwnZcE8wR/H2Y8zAr6Yzj5iTc4+wG3Lzykuqx
5KeA6uALRgu6+fD8L4qOIvPc3K6mybrkjtpQ62CsvtcZpNPVuMhgT7LQoDM0ndMz
jFkWTLBhAac9K8K8QuVo82anrBLUsapKgK5mD3WGSs+OSxjclFZSc/AS/IAR92uD
8ew7NUiIbvH4fPS0xddrWvRTBYBHFtF48gRSlmEo4X87iSKIG0rArDW+OYlY4iwv
wXx7spUZ5wpkoCYFQFMyjfye+dI4TrkSvw2GUUwffYFp6xTDgj28y4LIcEhsVGlJ
LddV3SN0wyHopHiQCU30iWQPmY1WV1lv5WEZypJDsvHdiTFbdWfcn1kmsX+T6EkT
sAuOEjEPKLaiTKUlGZWa
=yGJH
-----END PGP SIGNATURE-----

--Apple-Mail=_042D7F4A-41C5-49BC-A316-705F5CF00033--

From andy@arin.net  Thu Jul 12 02:12:11 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 686BD21F878E for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 02:12:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hs-PqJ14B33s for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 02:12:10 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 5107521F877D for <weirds@ietf.org>; Thu, 12 Jul 2012 02:12:10 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 4BA5421377E; Thu, 12 Jul 2012 05:12:42 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id BF726213775; Thu, 12 Jul 2012 05:12:41 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Thu, 12 Jul 2012 05:12:14 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Thu, 12 Jul 2012 05:12:27 -0400
From: Andy Newton <andy@arin.net>
To: John R Levine <johnl@taugh.com>
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: AQHNX65QpJoDeMyMZUyzRwJlYVqyVZck9d2A
Date: Thu, 12 Jul 2012 09:12:26 +0000
Message-ID: <BB77C35A-CAC7-4E11-A4EF-CC8AFCEB438D@arin.net>
References: <20120711203242.48919.qmail@joyce.lan> <9FC1FEF3-EE0D-4CF4-BA6E-DE2A12ACB092@arin.net> <alpine.BSF.2.00.1207111728450.47528@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1207111728450.47528@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.34.162]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C48AFE75A85F894E8B9D81605DA33F12@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 09:12:11 -0000

On Jul 11, 2012, at 5:44 PM, John R Levine wrote:

>> BTW, are there in-brower Javascript DNS solutions? I've not looked into =
that.
>=20
> Hmmn, a little googlage suggests that there aren't. You'd have to call
> out to some web site that will do the lookup for you which rather
> defeats the purpose.  I suppose one could use a CNAME kludge of
> <tld>.wierdsservers.net or <1.2.3.4.5.6>.weirdsservers.net, analogous
> to Rodney's whoisservers.net, that doesn't require a lookup before the
> http query.

Interesting. Why not XXXX.weirds.arpa?

> There will be a thousand times as many WIERDS clients as servers, so
> given a tradeoff between making it easier to set up a server and
> making it easier to do a query, I'll pick the easier query every time.

Agreed.

-andy=

From galvin+weirds@elistx.com  Thu Jul 12 06:29:00 2012
Return-Path: <galvin+weirds@elistx.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2553E21F876F for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 06:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pmjz-imTm+cT for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 06:28:59 -0700 (PDT)
Received: from ee01.elistx.com (ee01.elistx.com [67.155.182.182]) by ietfa.amsl.com (Postfix) with ESMTP id 2DE1821F8629 for <weirds@ietf.org>; Thu, 12 Jul 2012 06:28:59 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31965) with ESMTP id <0M71006EAUSSMP@elistx.com> for weirds@ietf.org; Thu, 12 Jul 2012 09:29:16 -0400 (EDT)
Date: Thu, 12 Jul 2012 09:29:33 -0400
From: Jim Galvin <galvin+weirds@elistx.com>
In-reply-to: <20120711201734.48396.qmail@joyce.lan>
To: weirds@ietf.org
Message-id: <AB213C46F8456F4C18954A1D@James-Galvin-2.local>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <20120711201734.48396.qmail@joyce.lan>
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 13:29:00 -0000

-- On July 11, 2012 8:17:34 PM +0000 John Levine <johnl@taugh.com> 
wrote regarding Re: [weirds] REST-pect-ful --

>  The resource that is returned as for a query for a contact returns a
>  general identifier with elements that contain URIs for the address,
>  phone number and other person information. If you want to resolve
>  those elements in more detail you >will have to do a new query. That
>  query might be refused based on authentication.
>
> That could certainly work, but what was one query could now be a
> dozen, which seems like a poor idea.
>
>  Anther method I thought of is serve up all elements but fill in
>  'REFUSED', or another magic string or code that indicates the client
>  is not allowed to see those elements. But that doesn't seem very
>  RESTful and I dismissed it.
>
> It's not as elegant, but it seems more practical.

While I agree that forcing people to make more than one query is 
undesirable if not impractical, I see a practical purpose for doing 
exactly that.

If you just say "REFUSED" then you're done.  There's no opportunity for 
further attempts when it's possible you're entitled to the information. 
How about doing both?

The use case I'm imagining is as follows.  You have a "public" service 
that offers whatever information any random visitor is entitled to. 
For other information it is tagged in some way as "REFUSED" but in 
addition you get the "redirect" for where to get that information. 
Implicit in the redirect is that there will be authentication required, 
which means if you're entitled to the information you'll know how to 
authenticate.  If you're not then you're wasting your time querying.

This seems both practical and elegant to me.

Jim


From michele@blacknight.ie  Thu Jul 12 06:38:06 2012
Return-Path: <michele@blacknight.ie>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2640D21F867E for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 06:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.305
X-Spam-Level: 
X-Spam-Status: No, score=-2.305 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_FROM_NONAME=1.294]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7KCvH7B1l3yB for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 06:38:05 -0700 (PDT)
Received: from exchange.blacknight.ie (exchange.blacknight.ie [81.17.243.252]) by ietfa.amsl.com (Postfix) with ESMTP id D7BAE21F8550 for <weirds@ietf.org>; Thu, 12 Jul 2012 06:38:04 -0700 (PDT)
Received: from BKEXCHMBX01.blacknight.local ([fe80::c1ec:f7c1:47fd:ad30]) by bkexchhubcas01.blacknight.local ([fe80::3ca9:6bf1:bd5d:24b%15]) with mapi id 14.02.0309.002; Thu, 12 Jul 2012 14:35:48 +0100
From: "\"Michele Neylon :: Blacknight\"" <michele@blacknight.ie>
To: James Mitchell <james.mitchell@ausregistry.com.au>
Thread-Topic: [weirds] REST-pect-ful
Thread-Index: AQHNX6Eh+XItskg2WE2+U1JKgKgKG5ckdGMAgAAGEwCAAGxBgIAAwIRA
Date: Thu, 12 Jul 2012 13:38:36 +0000
Message-ID: <D2B72B87-99D7-4C46-92EE-B844303A72B6@blacknight.com>
References: <D3D8582E-BE04-4BCF-88D9-B73A3813003E@arin.net>, <CC245AB3.12E9B%james.mitchell@ausregistry.com.au>
In-Reply-To: <CC245AB3.12E9B%james.mitchell@ausregistry.com.au>
Accept-Language: en-IE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John Levine <johnl@taugh.com>, "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 13:38:06 -0000

A lot of ccTLDs do this
.eu only provides minimal data via port 43. To get more data via port 80 yo=
u have to get past a catcha and you have limited access to data of private =
individuals (which is good thing (tm) )

Mr. Michele Neylon
Blacknight
http://Blacknight.tel

Via iPhone so excuse typos and brevity

On 12 Jul 2012, at 05:12, "James Mitchell" <james.mitchell@ausregistry.com.=
au> wrote:

> +1 to the notice concept for the reasons Andy raised.
>=20
> Using .au whois as an example, only registrant and technical contact name
> and email are available via whois-like interfaces (port-43 and web),
> however email is withheld to port-43 clients. Administrative and billing
> contacts are never returned, nor is any specific data relating to the
> registrant or tech contacts (phone, fax, address etc).
>=20
> There a distinction between data that is never available and data has bee=
n
> withheld from a specific interface. DENIC also has similar behaviours IIR=
C.
>=20
> James
>=20
>=20
> On 12/07/12 6:39 AM, "Andy Newton" <andy@arin.net> wrote:
>=20
>>=20
>> On Jul 11, 2012, at 4:17 PM, John Levine wrote:
>>=20
>>> The resource that is returned as for a query for a contact returns a
>>> general identifier with elements that contain URIs for the address,
>>> phone number and other person information. If you want to resolve
>>> those elements in more detail you >will have to do a new query. That
>>> query might be refused based on authentication.
>>>=20
>>> That could certainly work, but what was one query could now be a
>>> dozen, which seems like a poor idea.
>>=20
>> I agree with this. Not only does it add load to the service, but
>> experience has shown people don't like requiring for the same informatio=
n.
>>=20
>>> Anther method I thought of is serve up all elements but fill in
>>> 'REFUSED', or another magic string or code that indicates the client
>>> is not allowed to see those elements. But that doesn't seem very
>>> RESTful and I dismissed it.
>>>=20
>>> It's not as elegant, but it seems more practical.
>>=20
>> I lean more toward this approach as well. Though filling strings with
>> "REFUSED" just leads some to think that a persons last name might be
>> "REFUSED", a notice somewhere in the response noting information has bee=
n
>> redacted and pointing toward a policy document is fairly helpful.
>>=20
>> -andy
>> _______________________________________________
>> weirds mailing list
>> weirds@ietf.org
>> https://www.ietf.org/mailman/listinfo/weirds
>=20
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds

From andy@arin.net  Thu Jul 12 07:07:40 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1CCC21F8847 for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 07:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03VafsyFTKoZ for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 07:07:39 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id B01BD21F883B for <weirds@ietf.org>; Thu, 12 Jul 2012 07:07:38 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id 86B631651E5; Thu, 12 Jul 2012 10:08:04 -0400 (EDT)
Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp1.arin.net (Postfix) with ESMTP id E79771651D5; Thu, 12 Jul 2012 10:08:03 -0400 (EDT)
Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.283.3; Thu, 12 Jul 2012 10:07:13 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0298.004; Thu, 12 Jul 2012 10:07:57 -0400
From: Andy Newton <andy@arin.net>
To: "<patrick@vande-walle.eu>" <patrick@vande-walle.eu>
Thread-Topic: [weirds] REST-pect-ful
Thread-Index: AQHNX6F71F8aVuhTGkWUHYArFUAeHZckyDQAgAAGEwCAAKIzAIAAecKA
Date: Thu, 12 Jul 2012 14:07:56 +0000
Message-ID: <B7F3A589-86A5-45D1-9AA2-02EE91C59B60@arin.net>
References: <20120711201734.48396.qmail@joyce.lan> <D3D8582E-BE04-4BCF-88D9-B73A3813003E@arin.net> <4FFE6C86.8040504@vande-walle.eu>
In-Reply-To: <4FFE6C86.8040504@vande-walle.eu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.149.252.96]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E5390ADA375EE74E8A611C48D861B478@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 14:07:41 -0000

On Jul 12, 2012, at 2:19 AM, Patrick Vande Walle wrote:

> Agree with Andy   and others that multiple queries may  cause additional =
load that could possibly be avoided. =20
>=20
> On 11/07/12 22:39, Andy Newton wrote:
>> I lean more toward this approach as well. Though filling strings with "R=
EFUSED" just leads some to think that a persons last name might be "REFUSED=
",
>=20
> Indeed. Especially if that person's name happens to be "Refused", which c=
ould happen.  I do not like the idea of having magic strings in lieu of fie=
ld data. =20
> In the case of a field whose content should be hidden by policy, I sugges=
t the field data should  be empty, but we could add an optional sub-structu=
re related to policy.
>=20
> I just made up the example below for the purpose of demonstration: =20
>=20
> {
>     "BillingTelNum": {
>         "Description": "Billing Contact phone number",
>         "TelNum":=20
>               "Data": "",    =20
>             "Policy": {
>                 "Status": "REDACTED",
>                 "Info": "See http://www.example.org/weirds-policy"
>                 }}}}}
>=20
> Patrick Vande Walle
>=20


>From the soon-to-be draft-designteam-weirds-using-http-01

9.  Common Data Structures

   This section defines two common data structures to be used by
   DNRD-AP, NRRD-AP, and other RD-AP protocols.  As such, the names
   identifying these data structures are not to be redefined by any
   registry specific RD-AP specifications.  Each of these datatypes MAY
   appear within any other data object of a response, but the intended
   purpose is that they will be mostly used in the top-most data object
   of a response.

   The first data structure is named "rdapConformance" and is simply an
   array of strings, each providing a hint as to the specifications used
   in the construction of the response.

   An example rdapConformance data structure.


     "rdapConformance" : [
       "nrrdap_level_0"
     ]


                                 Figure 9

   The second data structure is named "notices" and is an array of
   "notice" objects.  Each "notice" object contains a "title" string
   representing the title of the notice object, an array of strings
   named "description" for the purposes of conveying any descriptive
   text about the notice, and a "uri" string holding a URI referencing
   any a service that may provide additional information about the
   notice.

   An exmaple of the notices data structure.


     "notices" : [
       "notice" : {
         "title" : "Terms of Use",
         "description" : [
           "This service is subject to The Registry of the Moons",
           "terms of service."
         ],
         "uri" : "http://example.com/our-terms-of-use"
       }
     ]


                                 Figure 10



   This is an example response with both rdapConformance and notices
   embedded.


     {
       "rdapConformance" : [
         "nrrdap_level_0"
       ]
       "notices" : [
         "notice" : {
           "title" : "Content Redacted",
           "description" : [
             "Without full authorization, content has been redacted.",
             "Sorry, dude!"
           ],
           "uri" : "http://example.com/our-redaction-policies"
         }
       ]
       "startAddress" : "10.0.0.0",
       "endAddress" : "10.0.0.255",
       "remarks" : [
         "she sells seas shells",
         "down by the seashore"
       ],
       "uris" : [
         {
           "type" : "source",
           "uri" : "http://whois-rws.net/network/xxxx"
         },
         {
           "type" : "parent",
           "uri" : "http://whois-rws.net/network/yyyy"
         }
       ]
     }

-andy=

From johnl@taugh.com  Thu Jul 12 07:08:23 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 359C321F858F for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 07:08:23 -0700 (PDT)
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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iC3LJ2hCHdqJ for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 07:08:22 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 2932E21F8570 for <weirds@ietf.org>; Thu, 12 Jul 2012 07:08:21 -0700 (PDT)
Received: (qmail 38603 invoked from network); 12 Jul 2012 14:08:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=96c8.4ffeda76.k1207; bh=wBvcOmgLnqoFIMojBW9ZUZLo8NgvWZHfDERjBujkS/8=; b=qN+eVxLwGg2z9H58h3gDEo4LXPSuMLomuIGa2jbdtYddrA9rFmY1Zqh71IGCg8EkCpF/6jVkTwzvRIvZ0/GnLL3ictQ1G3wPB3maynKRPTqkaIwtc7BCP/sx259/t1lBWeSSAc4Dpi72YTCekkVNwUqqctov4WL7tjC6aRgSKWk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=96c8.4ffeda76.k1207; bh=wBvcOmgLnqoFIMojBW9ZUZLo8NgvWZHfDERjBujkS/8=; b=U+AjrckGS4xYf500K6EaDXsesKTBjDP3Evfg1nTLlZeATWFgcu6Reh6WmHKZbHe7b/yzab+h/ebex8/DyNK/olouSGMuMc+eli9ZQiOe8Z4LlX9FRsTTLrkWdyTHKtpKzoVdHXktJzA7IvC+PsK6V0fo9je3OJR9UzdGhSIKH+s=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 12 Jul 2012 14:08:32 -0000
Date: 12 Jul 2012 10:08:53 -0400
Message-ID: <alpine.BSF.2.00.1207120959530.60846@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Andy Newton" <andy@arin.net>
In-Reply-To: <BB77C35A-CAC7-4E11-A4EF-CC8AFCEB438D@arin.net>
References: <20120711203242.48919.qmail@joyce.lan> <9FC1FEF3-EE0D-4CF4-BA6E-DE2A12ACB092@arin.net> <alpine.BSF.2.00.1207111728450.47528@joyce.lan> <BB77C35A-CAC7-4E11-A4EF-CC8AFCEB438D@arin.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 14:08:23 -0000

>> defeats the purpose.  I suppose one could use a CNAME kludge of
>> <tld>.wierdsservers.net or <1.2.3.4.5.6>.weirdsservers.net, analogous
>> to Rodney's whoisservers.net, that doesn't require a lookup before the
>> http query.
>
> Interesting. Why not XXXX.weirds.arpa?

Uh, because I wasn't thinking far enough ahead?  That would involve IANA, 
but in a pretty benign way.  They'd have to update their processes to 
allow entities that have been delegated a TLD or a top level IP range to 
register and update WEIRDS servers, but it'd be no more work than 
maintaining the in-addr zone which they do now.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From galvin+weirds@elistx.com  Thu Jul 12 08:27:41 2012
Return-Path: <galvin+weirds@elistx.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B8421F87EA for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 08:27:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vi8L2RPdvvYd for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 08:27:40 -0700 (PDT)
Received: from ee01.elistx.com (ee01.elistx.com [67.155.182.182]) by ietfa.amsl.com (Postfix) with ESMTP id CF5C721F876F for <weirds@ietf.org>; Thu, 12 Jul 2012 08:27:40 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31965) with ESMTP id <0M720015V0AM9B@elistx.com> for weirds@ietf.org; Thu, 12 Jul 2012 11:27:58 -0400 (EDT)
Date: Thu, 12 Jul 2012 11:28:15 -0400
From: Jim Galvin <galvin+weirds@elistx.com>
In-reply-to: <E4291B20-E1ED-4E5C-A0A1-FC96FAF98A0D@nlnetlabs.nl>
To: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Message-id: <F0F1E2CB046B73610B2C2404@James-Galvin-2.local>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <E4291B20-E1ED-4E5C-A0A1-FC96FAF98A0D@nlnetlabs.nl>
Subject: Re: [weirds] Supporting Objects
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 15:27:41 -0000

-- On July 11, 2012 10:11:39 PM +0200 Olaf Kolkman <olaf@nlnetlabs.nl> 
wrote regarding [weirds] Supporting Objects --

> What we are set out to do is to define a data model that supports a
> useful set of objects that can serve environments from the most
> liberal to the most strict local policy.

I'm not sure this working group is the right place to define *the* data 
model.  We already have numbers versus names and we know that there is 
different information in each of those.

Could we instead define a framework for the data model (e.g., I like 
the category of objects discussion and maybe we just give examples in 
each)?  This would let each of the communities that would use the 
weirds protocol to define the specifics of its own data model.

Jim


From johnl@iecc.com  Thu Jul 12 10:42:00 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 748D311E80C0 for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 10:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.114
X-Spam-Level: 
X-Spam-Status: No, score=-111.114 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32luurU2sD7j for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 10:41:59 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id B3E5911E8098 for <weirds@ietf.org>; Thu, 12 Jul 2012 10:41:58 -0700 (PDT)
Received: (qmail 89880 invoked from network); 12 Jul 2012 17:42:31 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 12 Jul 2012 17:42:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4fff0c87.xn--btvx9d.k1207; i=johnl@user.iecc.com; bh=2nGTyG1PdsZtz5CEYp3zrY6SZelpjjpRZZcGX50viKQ=; b=Fqd0TB6tKL/+FPHjVKvtxZOIWwEdIqkgi8XBLkBF5Nv1HHwA2BjIxw4adtw8riLoTDdRTrqeErRt+0f7mNVbsZI0QjWAf0pCWNeW6LgZ0NQEecJy7jOqKrNc/SNEvco+MiqLkb8U7HahozAlpHnrsJef/YP4S+MvEaR51qobuhg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4fff0c87.xn--btvx9d.k1207; olt=johnl@user.iecc.com; bh=2nGTyG1PdsZtz5CEYp3zrY6SZelpjjpRZZcGX50viKQ=; b=AR11X8Tar3wzY6G+OUZzEgZ4oR8ZIf+YdMb0CV2/DGw1onw357DwSvcowEQ6mZux/b+D84gTozECN6SPm3abCrGngvhPLWs/4GFD4gsais5L1MKvMpLW7SYIVp5SwceeVdSnZqdTkTIvGVx9kjup7lHyi9qzyHbU5e9KPcd1m68=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 12 Jul 2012 17:42:09 -0000
Message-ID: <20120712174209.34670.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <AB213C46F8456F4C18954A1D@James-Galvin-2.local>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 17:42:00 -0000

>The use case I'm imagining is as follows.  You have a "public" service 
>that offers whatever information any random visitor is entitled to. 
>For other information it is tagged in some way as "REFUSED" but in 
>addition you get the "redirect" for where to get that information. 
>Implicit in the redirect is that there will be authentication required, 
>which means if you're entitled to the information you'll know how to 
>authenticate.  If you're not then you're wasting your time querying.
>
>This seems both practical and elegant to me.

Why would that be better than sending your credentials along with the
initial request so you get all the data on the first try?

R's,
John

From johnl@iecc.com  Thu Jul 12 10:47:32 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ECC111E8083 for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 10:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.118
X-Spam-Level: 
X-Spam-Status: No, score=-111.118 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jvx8dC6CSPqK for <weirds@ietfa.amsl.com>; Thu, 12 Jul 2012 10:47:31 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id EE06B11E807F for <weirds@ietf.org>; Thu, 12 Jul 2012 10:47:30 -0700 (PDT)
Received: (qmail 91154 invoked from network); 12 Jul 2012 17:48:04 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 12 Jul 2012 17:48:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4fff0dd4.xn--i8sz2z.k1207; i=johnl@user.iecc.com; bh=w3NPCAUZv3yN780Q8G5djPmG/6U4CdYiZm6LyfJeZi4=; b=GVSLoDE8HsLTb4Fkk6afWoeMbme4etdHHdg879zx4cUGv/tfFPK3fE/WvZSNlM0m7o0GLg/6maztbA7cC3Sro5tVMZJUZ66JtfAwzB1SVoO+8ApMikrA80aE2fICQQ9ziTA5zC7dK9FPsRa/2ZNLvPID3lT1C6yFK9nJGmNdUkM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4fff0dd4.xn--i8sz2z.k1207; olt=johnl@user.iecc.com; bh=w3NPCAUZv3yN780Q8G5djPmG/6U4CdYiZm6LyfJeZi4=; b=lX03m26qELyQraemeevq5L3HExvIP1u+8gX/nwug/KOyYg2554/x1EAsKb0AgM4DIhZBlhL5lB0oM7CIib1ZmBNQlXfA9Ok7cKH/IHiBMG4U8puUlMVqFDNBPjZuLfhk5hUaKHhxmBSBiy35dyHhXSU6h+ZPgBSZqoBtY326QcY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 12 Jul 2012 17:47:41 -0000
Message-ID: <20120712174741.36209.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <F0F1E2CB046B73610B2C2404@James-Galvin-2.local>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Supporting Objects
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 17:47:32 -0000

>Could we instead define a framework for the data model 

Not if our goal is to produce something useful.  While it is
true that the models for names and numbers will be different,
it is absolutely essential that we nail down, for each side,
what the query syntax is, and how to parse the results.

The numbers side is mostly done, since they have several
working prototypes that are nearly the same.  If the names
side can't agree on a model, the numbers work will go ahead
separately.

R's,
John

PS: Don't argue, there is specific language in the charter
that anticipates this situation.


From shollenbeck@verisign.com  Fri Jul 13 06:59:38 2012
Return-Path: <shollenbeck@verisign.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B5AF21F867C for <weirds@ietfa.amsl.com>; Fri, 13 Jul 2012 06:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xRCbjquPGbJl for <weirds@ietfa.amsl.com>; Fri, 13 Jul 2012 06:59:36 -0700 (PDT)
Received: from exprod6ob113.obsmtp.com (exprod6ob113.obsmtp.com [64.18.1.30]) by ietfa.amsl.com (Postfix) with ESMTP id 4FF5921F867A for <weirds@ietf.org>; Fri, 13 Jul 2012 06:59:33 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob113.postini.com ([64.18.5.12]) with SMTP ID DSNKUAAp6GQrgDbDz6m+ZJxEj64apxqKBHDP@postini.com; Fri, 13 Jul 2012 07:00:09 PDT
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id q6DE07pd013876 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <weirds@ietf.org>; Fri, 13 Jul 2012 10:00:07 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0247.003; Fri, 13 Jul 2012 10:00:07 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "weirds@ietf.org" <weirds@ietf.org>
Thread-Topic: Prototype DNRD Service at Verisign
Thread-Index: Ac1g/86C//jQC5RNRpeR1x5H636zjA==
Date: Fri, 13 Jul 2012 14:00:06 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F0D6437C5@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [weirds] Prototype DNRD Service at Verisign
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 13:59:38 -0000

I have a prototype server up and running at dnrd.verisignlabs.com that is c=
apable of processing queries for a subset of the Verisign-managed TLDs (.cc=
, .tv, .jobs). Given the current state of our specifications you should NOT=
 expect this service to conform to anything, but having said that the query=
 format should be pretty close to what's specified in draft-hollenbeck-dnrd=
-query. We will update the service as the specifications evolve. Feel free =
to play with it.

A help page:

http://dnrd.verisignlabs.com/dnrd-ap/help/

A sample domain query:

http://dnrd.verisignlabs.com/dnrd-ap/domain/verisigninc.cc

A UI for queries and searches:

http://dnrd.verisignlabs.com/dnrd-ap/

Scott

From internet-drafts@ietf.org  Fri Jul 13 10:43:53 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CCB721F8668; Fri, 13 Jul 2012 10:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Level: 
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7mlHEesqwyB; Fri, 13 Jul 2012 10:43:52 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EE6521F866B; Fri, 13 Jul 2012 10:43:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.30p3
Message-ID: <20120713174352.16055.13544.idtracker@ietfa.amsl.com>
Date: Fri, 13 Jul 2012 10:43:52 -0700
Cc: weirds@ietf.org
Subject: [weirds] I-D Action: draft-designteam-weirds-using-http-01.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 17:43:53 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Web Extensible Internet Registration Data=
 Service Working Group of the IETF.

	Title           : Using HTTP for RESTful Whois Services by Internet Regist=
ries
	Author(s)       : Andrew Lee Newton
                          Kaveh Ranjbar
                          Arturo L. Servin
                          Byron J. Ellacott
                          Scott Hollenbeck
                          Steve Sheng
                          Francisco Arias
                          Ning Kong
                          Francisco Obispo
	Filename        : draft-designteam-weirds-using-http-01.txt
	Pages           : 26
	Date            : 2012-07-13

Abstract:
   This document describes the use of HTTP in Whois services using
   RESTful web methodologies.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-designteam-weirds-using-http

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-designteam-weirds-using-http-01

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-designteam-weirds-using-http-01


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From internet-drafts@ietf.org  Fri Jul 13 10:44:07 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADB1821F8668; Fri, 13 Jul 2012 10:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level: 
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cL1QC-3y61pC; Fri, 13 Jul 2012 10:44:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D5C21F87B8; Fri, 13 Jul 2012 10:44:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.30p3
Message-ID: <20120713174407.16055.74766.idtracker@ietfa.amsl.com>
Date: Fri, 13 Jul 2012 10:44:07 -0700
Cc: weirds@ietf.org
Subject: [weirds] I-D Action: draft-newton-et-al-weirds-rir-query-02.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 17:44:08 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Web Extensible Internet Registration Data=
 Service Working Group of the IETF.

	Title           : A Uniform RESTful URL Query Pattern for RIRs
	Author(s)       : Andrew Lee Newton
                          Kaveh Ranjbar
                          Arturo L. Servin
                          Byron J. Ellacott
	Filename        : draft-newton-et-al-weirds-rir-query-02.txt
	Pages           : 10
	Date            : 2012-07-13

Abstract:
   This document describes uniform patterns for which to construct HTTP
   URLs that may be used to retreive information from Regional Internet
   Registries (RIRs) using "RESTful" web access patterns.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-newton-et-al-weirds-rir-query

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-newton-et-al-weirds-rir-query-02

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-newton-et-al-weirds-rir-query-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From internet-drafts@ietf.org  Fri Jul 13 10:44:22 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A899921F8792; Fri, 13 Jul 2012 10:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YxD48Y+zJs0g; Fri, 13 Jul 2012 10:44:22 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E009421F87B8; Fri, 13 Jul 2012 10:44:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.30p3
Message-ID: <20120713174421.16002.89304.idtracker@ietfa.amsl.com>
Date: Fri, 13 Jul 2012 10:44:21 -0700
Cc: weirds@ietf.org
Subject: [weirds] I-D Action: draft-newton-et-al-weirds-rir-json-response-02.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 17:44:23 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Web Extensible Internet Registration Data=
 Service Working Group of the IETF.

	Title           : JSON Responses to RESTful URL Queries for RIRs
	Author(s)       : Andrew Lee Newton
                          Kaveh Ranjbar
                          Arturo L. Servin
                          Byron J. Ellacott
	Filename        : draft-newton-et-al-weirds-rir-json-response-02.txt
	Pages           : 17
	Date            : 2012-07-13

Abstract:
   This document describes responses in the JSON format to the RESTful
   queries described in draft-newton-et-al-weirds-rir-query.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-newton-et-al-weirds-rir-json-response

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-newton-et-al-weirds-rir-json-response-02

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-newton-et-al-weirds-rir-json-res=
ponse-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From andy@arin.net  Fri Jul 13 10:52:57 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8DD321F87C8 for <weirds@ietfa.amsl.com>; Fri, 13 Jul 2012 10:52:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tEUU+kLsZv8a for <weirds@ietfa.amsl.com>; Fri, 13 Jul 2012 10:52:57 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 0016B21F87B0 for <weirds@ietf.org>; Fri, 13 Jul 2012 10:52:56 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 5A2D1214690; Fri, 13 Jul 2012 13:53:33 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id B0476214687 for <weirds@ietf.org>; Fri, 13 Jul 2012 13:53:32 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Fri, 13 Jul 2012 13:53:11 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Fri, 13 Jul 2012 13:53:32 -0400
From: Andy Newton <andy@arin.net>
To: "weirds@ietf.org" <weirds@ietf.org>
Thread-Topic: New Version Notification for draft-designteam-weirds-using-http-01.txt
Thread-Index: AQHNYR8oqmIas+UNQUaxA16Oyhd+yA==
Date: Fri, 13 Jul 2012 17:53:31 +0000
Message-ID: <1D7ACAB8-EFA3-4118-8D41-807FD10D942E@arin.net>
References: <20120713174352.16055.89253.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.34.156]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D901E00901B32D4AB7E51AD15432E24C@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [weirds] Fwd: New Version Notification for draft-designteam-weirds-using-http-01.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 17:52:58 -0000

Change log below...

Begin forwarded message:

> A new version of I-D, draft-designteam-weirds-using-http-01.txt
> has been successfully submitted by Andrew Lee Newton and posted to the
> IETF repository.
>=20
> Filename:	 draft-designteam-weirds-using-http
> Revision:	 01
> Title:		 Using HTTP for RESTful Whois Services by Internet Registries
> Creation date:	 2012-07-12
> WG ID:		 weirds
> Number of pages: 26
> URL:             http://www.ietf.org/internet-drafts/draft-designteam-wei=
rds-using-http-01.txt
> Status:          http://datatracker.ietf.org/doc/draft-designteam-weirds-=
using-http
> Htmlized:        http://tools.ietf.org/html/draft-designteam-weirds-using=
-http-01
> Diff:            http://tools.ietf.org/rfcdiff?url2=3Ddraft-designteam-we=
irds-using-http-01
>=20
> Abstract:
>   This document describes the use of HTTP in Whois services using
>   RESTful web methodologies.

Changes:

1) Introduction section overhauled.

2) Section 4.1 on Accept and Content-Type headers has been changed to stabi=
lize the media type and use the level parameter to signify version complian=
ce.

3) Section 4.2 simplified as per Julian Reschke's feedback. Cache busting m=
oved to appendix A.

4) Section 6.2 on JSON naming modified to better show how extensibility wor=
ks.

5) Section 7.2 updated to incorporate XML feedback from Julian Reschke.

6) Section 9 on common data structures added.

7) IANA considerations section added for registering media types.

-andy=

From andy@arin.net  Fri Jul 13 10:54:13 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF7F11E80A3 for <weirds@ietfa.amsl.com>; Fri, 13 Jul 2012 10:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Ff1oOSO9xxf for <weirds@ietfa.amsl.com>; Fri, 13 Jul 2012 10:54:12 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 4828A11E8087 for <weirds@ietf.org>; Fri, 13 Jul 2012 10:54:12 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id 88F3A164EDD; Fri, 13 Jul 2012 13:54:46 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp1.arin.net (Postfix) with ESMTP id F09EB164EDA for <weirds@ietf.org>; Fri, 13 Jul 2012 13:54:45 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Fri, 13 Jul 2012 13:54:25 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Fri, 13 Jul 2012 13:54:45 -0400
From: Andy Newton <andy@arin.net>
To: "weirds@ietf.org" <weirds@ietf.org>
Thread-Topic: New Version Notification for draft-newton-et-al-weirds-rir-query-02.txt
Thread-Index: AQHNYR8xQZHkQmjKFUuLtcQGTZGMyw==
Date: Fri, 13 Jul 2012 17:54:44 +0000
Message-ID: <03C3472B-A528-4D20-A607-1FC1C184A4ED@arin.net>
References: <20120713174407.16055.73591.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.34.156]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <26E45F5C66230E4199A4D45D98BE90F7@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [weirds] Fwd: New Version Notification for	draft-newton-et-al-weirds-rir-query-02.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 17:54:13 -0000

Changes to bring this in-line with draft-designteam-weirds-using-http-01.

-andy

Begin forwarded message:

> A new version of I-D, draft-newton-et-al-weirds-rir-query-02.txt
> has been successfully submitted by Andrew Lee Newton and posted to the
> IETF repository.
>=20
> Filename:	 draft-newton-et-al-weirds-rir-query
> Revision:	 02
> Title:		 A Uniform RESTful URL Query Pattern for RIRs
> Creation date:	 2012-07-12
> WG ID:		 weirds
> Number of pages: 10
> URL:             http://www.ietf.org/internet-drafts/draft-newton-et-al-w=
eirds-rir-query-02.txt
> Status:          http://datatracker.ietf.org/doc/draft-newton-et-al-weird=
s-rir-query
> Htmlized:        http://tools.ietf.org/html/draft-newton-et-al-weirds-rir=
-query-02
> Diff:            http://tools.ietf.org/rfcdiff?url2=3Ddraft-newton-et-al-=
weirds-rir-query-02
>=20
> Abstract:
>   This document describes uniform patterns for which to construct HTTP
>   URLs that may be used to retreive information from Regional Internet
>   Registries (RIRs) using "RESTful" web access patterns.


From andy@arin.net  Fri Jul 13 10:54:45 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5843D11E80A5 for <weirds@ietfa.amsl.com>; Fri, 13 Jul 2012 10:54:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0fwWWpvfWldY for <weirds@ietfa.amsl.com>; Fri, 13 Jul 2012 10:54:44 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 7FFBF11E80A3 for <weirds@ietf.org>; Fri, 13 Jul 2012 10:54:44 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id E8DB3214660; Fri, 13 Jul 2012 13:55:20 -0400 (EDT)
Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp2.arin.net (Postfix) with ESMTP id 14A4021464F for <weirds@ietf.org>; Fri, 13 Jul 2012 13:55:20 -0400 (EDT)
Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.283.3; Fri, 13 Jul 2012 13:55:15 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0298.004; Fri, 13 Jul 2012 13:55:19 -0400
From: Andy Newton <andy@arin.net>
To: "weirds@ietf.org" <weirds@ietf.org>
Thread-Topic: New Version Notification for draft-newton-et-al-weirds-rir-json-response-02.txt
Thread-Index: AQHNYR86tQfS6awTZEyJzkEERs1VtQ==
Date: Fri, 13 Jul 2012 17:55:18 +0000
Message-ID: <2C9306F0-BD64-421E-BFCF-DED2DB547C8E@arin.net>
References: <20120713174422.16002.39862.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.34.156]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <340FFACFFE1C4D4DB07613476244F034@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [weirds] Fwd: New Version Notification for	draft-newton-et-al-weirds-rir-json-response-02.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 17:54:45 -0000

Changes to bring this in-line with draft-designteam-weirds-using-http-01.

-andy

Begin forwarded message:

> A new version of I-D, draft-newton-et-al-weirds-rir-json-response-02.txt
> has been successfully submitted by Andrew Lee Newton and posted to the
> IETF repository.
>=20
> Filename:	 draft-newton-et-al-weirds-rir-json-response
> Revision:	 02
> Title:		 JSON Responses to RESTful URL Queries for RIRs
> Creation date:	 2012-07-12
> WG ID:		 weirds
> Number of pages: 17
> URL:             http://www.ietf.org/internet-drafts/draft-newton-et-al-w=
eirds-rir-json-response-02.txt
> Status:          http://datatracker.ietf.org/doc/draft-newton-et-al-weird=
s-rir-json-response
> Htmlized:        http://tools.ietf.org/html/draft-newton-et-al-weirds-rir=
-json-response-02
> Diff:            http://tools.ietf.org/rfcdiff?url2=3Ddraft-newton-et-al-=
weirds-rir-json-response-02
>=20
> Abstract:
>   This document describes responses in the JSON format to the RESTful
>   queries described in draft-newton-et-al-weirds-rir-query.


From nkong@cnnic.cn  Sun Jul 15 23:56:58 2012
Return-Path: <nkong@cnnic.cn>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 235C311E8089 for <weirds@ietfa.amsl.com>; Sun, 15 Jul 2012 23:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oM95lFg1CxMY for <weirds@ietfa.amsl.com>; Sun, 15 Jul 2012 23:56:57 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id D08A411E8079 for <weirds@ietf.org>; Sun, 15 Jul 2012 23:56:56 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: nkong@cnnic.cn
Received: from unknown127.0.0.1 (HELO naptrthink) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 16 Jul 2012 14:57:35 +0800
From: "Ning Kong" <nkong@cnnic.cn>
To: "'John Levine'" <johnl@taugh.com>, <weirds@ietf.org>
References: <AB213C46F8456F4C18954A1D@James-Galvin-2.local> <20120712174209.34670.qmail@joyce.lan>
In-Reply-To: <20120712174209.34670.qmail@joyce.lan>
Date: Mon, 16 Jul 2012 14:57:32 +0800
Message-ID: <026101cd6320$45e41050$d1ac30f0$@cnnic.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIvRVLqR9CwRPLBPe46Hrnnq5HMwZZnfu2w
Content-Language: zh-cn
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 06:56:58 -0000

> >The use case I'm imagining is as follows.  You have a "public" service
> >that offers whatever information any random visitor is entitled to.
> >For other information it is tagged in some way as "REFUSED" but in
> >addition you get the "redirect" for where to get that information.
> >Implicit in the redirect is that there will be authentication required,
> >which means if you're entitled to the information you'll know how to
> >authenticate.  If you're not then you're wasting your time querying.
> >
> >This seems both practical and elegant to me.
> 
> Why would that be better than sending your credentials along with the
initial
> request so you get all the data on the first try?
I wonder how you can make sure what credentials are needed on your first
try. Furthermore, in some cases maybe you don't have the appropriate
credential on your first try, but you can acquire one according to the
response. For example, the response might tell you that if you want to
access the non-public data, you MUST register an account from a specific
service provider.

Cheers,
Ning


From johnl@taugh.com  Mon Jul 16 00:08:32 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7BA721F84B9 for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 00:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.591
X-Spam-Level: 
X-Spam-Status: No, score=-2.591 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aGrwr1BN1PV7 for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 00:08:30 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 7352B21F84E2 for <weirds@ietf.org>; Mon, 16 Jul 2012 00:08:30 -0700 (PDT)
Received: (qmail 41315 invoked from network); 16 Jul 2012 07:09:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=a162.5003be0e.k1207; bh=ptjE6ZugsAfMWv20lVtcXbB9kAMOjf8mHLME7HAp5l8=; b=qbWoqyEFVDKfu4VI/aSLaxgtkpP5GiK0vRxVfLecOWwHxnFk3m5XldekHs2JpB/cbwdX386XC6Gs0kxSGNn/5skT23cwHyvNfxW22clYPNnPCOwgQBaS4/BxO1RTNgb9ex8vdZ7Q0psTBmiTkdwHD0v8JV/YILhtLLXTcA0jjvY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=a162.5003be0e.k1207; bh=ptjE6ZugsAfMWv20lVtcXbB9kAMOjf8mHLME7HAp5l8=; b=F57SgYLr7BlGnRNY9kxsFx+UDB4/bAUkC1uf19WN72H1RmbkHJIzundwl/qAVv+Hpyv2aNAyHvU+P5hLSW0SRhs+4KKvMnkXgc7PFKFVa924A9c1FqQe4kE1D4/Q/ztVi1UCX75LA29i1BoKh89X9IGUYJQDzpFdodHsAtmRfEU=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 16 Jul 2012 07:08:40 -0000
Date: 16 Jul 2012 03:08:59 -0400
Message-ID: <alpine.BSF.2.00.1207160306580.38251@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Ning Kong" <nkong@cnnic.cn>
In-Reply-To: <026101cd6320$45e41050$d1ac30f0$@cnnic.cn>
References: <AB213C46F8456F4C18954A1D@James-Galvin-2.local> <20120712174209.34670.qmail@joyce.lan> <026101cd6320$45e41050$d1ac30f0$@cnnic.cn>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: weirds@ietf.org
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 07:08:32 -0000

>> Why would that be better than sending your credentials along with the
>> initial request so you get all the data on the first try?

> I wonder how you can make sure what credentials are needed on your first
> try.

I'd send whatever credentials I had for that server.  Do you expect an 
individual user to have multiple sets of credentials for a single WEIRDS 
server?

> Furthermore, in some cases maybe you don't have the appropriate
> credential on your first try, but you can acquire one according to the
> response. For example, the response might tell you that if you want to
> access the non-public data, you MUST register an account from a specific
> service provider.

In that case, you could register the account, then make the same request 
with the account's credentials.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From zhoulinlin@cnnic.cn  Mon Jul 16 00:52:23 2012
Return-Path: <zhoulinlin@cnnic.cn>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83C9621F85AD for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 00:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level: 
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FrLy2EkLCv+u for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 00:52:22 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id 4356A21F8617 for <weirds@ietf.org>; Mon, 16 Jul 2012 00:52:20 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn
Received: from unknown127.0.0.1 (HELO lenovo95e6383c) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 16 Jul 2012 15:52:59 +0800
From: "Linlin Zhou" <zhoulinlin@cnnic.cn>
To: "'Jim Galvin'" <galvin+weirds@elistx.com>, "'Web Extensible Internet Registration Data Service Working Group'" <weirds@ietf.org>
References: <E4291B20-E1ED-4E5C-A0A1-FC96FAF98A0D@nlnetlabs.nl> <F0F1E2CB046B73610B2C2404@James-Galvin-2.local>
In-Reply-To: <F0F1E2CB046B73610B2C2404@James-Galvin-2.local>
Date: Mon, 16 Jul 2012 15:53:02 +0800
Message-ID: <00a901cd6328$0721f500$1565df00$@cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1gQvlIFE82jtbNSSKl9uBjF9y7aAC5FVJQ
Content-Language: zh-cn
Subject: Re: [weirds] Supporting Objects
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 07:52:23 -0000

> -----Original Message-----
> From: weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On Behalf
Of
> Jim Galvin
> Sent: Thursday, July 12, 2012 11:28 PM
> To: Web Extensible Internet Registration Data Service Working Group
> Subject: Re: [weirds] Supporting Objects
> 
> 
> 
> -- On July 11, 2012 10:11:39 PM +0200 Olaf Kolkman <olaf@nlnetlabs.nl>
wrote
> regarding [weirds] Supporting Objects --
> 
> > What we are set out to do is to define a data model that supports a
> > useful set of objects that can serve environments from the most
> > liberal to the most strict local policy.
> 
> I'm not sure this working group is the right place to define *the* data
model.
> We already have numbers versus names and we know that there is different
> information in each of those.
> 
> Could we instead define a framework for the data model (e.g., I like the
> category of objects discussion and maybe we just give examples in each)?
> This would let each of the communities that would use the weirds protocol
to
> define the specifics of its own data model.
> 
I think at least we should have a data element set that are commonly used by
different registries, the other extensions can be defined on its own.

> Jim
> 
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds


From nkong@cnnic.cn  Mon Jul 16 01:13:13 2012
Return-Path: <nkong@cnnic.cn>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B763A21F85D6 for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 01:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.357
X-Spam-Level: 
X-Spam-Status: No, score=-2.357 tagged_above=-999 required=5 tests=[AWL=0.242,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jM5LCOYOSYmj for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 01:13:13 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id D549721F84E7 for <weirds@ietf.org>; Mon, 16 Jul 2012 01:13:07 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: nkong@cnnic.cn
Received: from unknown127.0.0.1 (HELO naptrthink) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 16 Jul 2012 16:13:46 +0800
From: "Ning Kong" <nkong@cnnic.cn>
To: "'John R Levine'" <johnl@taugh.com>
References: <AB213C46F8456F4C18954A1D@James-Galvin-2.local> <20120712174209.34670.qmail@joyce.lan> <026101cd6320$45e41050$d1ac30f0$@cnnic.cn> <alpine.BSF.2.00.1207160306580.38251@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1207160306580.38251@joyce.lan>
Date: Mon, 16 Jul 2012 16:13:43 +0800
Message-ID: <026c01cd632a$ea73b440$bf5b1cc0$@cnnic.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF0iLqKQqGaWVOpdd1+y1FYCgG4YwIvRVLqARvlXmcCsIaIQ5etWO+g
Content-Language: zh-cn
Cc: weirds@ietf.org
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 08:13:14 -0000

> > I wonder how you can make sure what credentials are needed on your
> > first try.
> 
> I'd send whatever credentials I had for that server.  Do you expect an
> individual user to have multiple sets of credentials for a single WEIRDS
server?
I'm just afraid that maybe the different data within a single WEIRDS server
require different credentials. For example, the billing contact name is only
opened to the registered users, but the billing contact phone is only opened
to the specific users who have signed a special agreement or who have gotten
a grant by the domain owner.

There is another possible scenario. WEIRDS service A you are querying has
set up alliances with WEIRDS service B and a famous authentication service
C. So the non-public data within WEIRDS service A might be opened to
registered users of WEIRDS service A, WEIRDS service B, or authentication
service C.

I'm not sure the above use cases are likely or not. IMO, the requirements of
WEIRDS authentication needs to be confirmed at first.

> > Furthermore, in some cases maybe you don't have the appropriate
> > credential on your first try, but you can acquire one according to the
> > response. For example, the response might tell you that if you want to
> > access the non-public data, you MUST register an account from a
> > specific service provider.
> 
> In that case, you could register the account, then make the same request
with
> the account's credentials.
The "specific service provider" I mentioned above is not the same WEIRDS
service you queried. So it might be another WEIRDS service within an
alliance or a specific authentication service. In that case, you have to
make the first request in order to know what credential for the requested
data is needed.

Cheers,
Ning


From aservin@lacnic.net  Mon Jul 16 01:54:29 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15D9421F84A5 for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 01:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.91
X-Spam-Level: 
X-Spam-Status: No, score=0.91 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_DIALUP=0.862, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ubNuveJNxDPg for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 01:54:28 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 4387321F84E1 for <weirds@ietf.org>; Mon, 16 Jul 2012 01:54:28 -0700 (PDT)
Received: from [192.168.1.133] (r186-48-219-110.dialup.adsl.anteldata.net.uy [186.48.219.110]) by mail.lacnic.net.uy (Postfix) with ESMTP id 848A130843E; Mon, 16 Jul 2012 05:55:03 -0300 (UYT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <026c01cd632a$ea73b440$bf5b1cc0$@cnnic.cn>
Date: Mon, 16 Jul 2012 05:55:02 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <7AA05DA6-6D1C-48B3-93DF-3887C0FCA5EE@lacnic.net>
References: <AB213C46F8456F4C18954A1D@James-Galvin-2.local> <20120712174209.34670.qmail@joyce.lan> <026101cd6320$45e41050$d1ac30f0$@cnnic.cn> <alpine.BSF.2.00.1207160306580.38251@joyce.lan> <026c01cd632a$ea73b440$bf5b1cc0$@cnnic.cn>
To: Ning Kong <nkong@cnnic.cn>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: 'John R Levine' <johnl@taugh.com>, weirds@ietf.org
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 08:54:29 -0000

Ning,

	I think that your scenarios are valid. e.g. a weirds operator =
using open-id to provide access to its data.

	IMHO it would depend on the local policy of the weirds sever to =
decide what data to serve.

	The first step I think would be to decide which authentication =
and authorization methods we would like to have in this protocol.

Cheers,
as


On 16 Jul 2012, at 05:13, Ning Kong wrote:

>>> I wonder how you can make sure what credentials are needed on your
>>> first try.
>>=20
>> I'd send whatever credentials I had for that server.  Do you expect =
an
>> individual user to have multiple sets of credentials for a single =
WEIRDS
> server?
> I'm just afraid that maybe the different data within a single WEIRDS =
server
> require different credentials. For example, the billing contact name =
is only
> opened to the registered users, but the billing contact phone is only =
opened
> to the specific users who have signed a special agreement or who have =
gotten
> a grant by the domain owner.
>=20
> There is another possible scenario. WEIRDS service A you are querying =
has
> set up alliances with WEIRDS service B and a famous authentication =
service
> C. So the non-public data within WEIRDS service A might be opened to
> registered users of WEIRDS service A, WEIRDS service B, or =
authentication
> service C.
>=20
> I'm not sure the above use cases are likely or not. IMO, the =
requirements of
> WEIRDS authentication needs to be confirmed at first.
>=20
>>> Furthermore, in some cases maybe you don't have the appropriate
>>> credential on your first try, but you can acquire one according to =
the
>>> response. For example, the response might tell you that if you want =
to
>>> access the non-public data, you MUST register an account from a
>>> specific service provider.
>>=20
>> In that case, you could register the account, then make the same =
request
> with
>> the account's credentials.
> The "specific service provider" I mentioned above is not the same =
WEIRDS
> service you queried. So it might be another WEIRDS service within an
> alliance or a specific authentication service. In that case, you have =
to
> make the first request in order to know what credential for the =
requested
> data is needed.
>=20
> Cheers,
> Ning
>=20
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds


From carlos@sherpawebstudios.com  Fri Jul 13 11:09:14 2012
Return-Path: <carlos@sherpawebstudios.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3E8421F85F2 for <weirds@ietfa.amsl.com>; Fri, 13 Jul 2012 11:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4xUQ5Hgubrr for <weirds@ietfa.amsl.com>; Fri, 13 Jul 2012 11:09:12 -0700 (PDT)
Received: from mfe4.modwest.com (mfe4.modwest.com [204.11.245.168]) by ietfa.amsl.com (Postfix) with ESMTP id 078AC21F85F7 for <weirds@ietf.org>; Fri, 13 Jul 2012 11:09:11 -0700 (PDT)
Received: from pandora.local (unknown [200.7.85.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mfe4.modwest.com (Postfix) with ESMTPSA id 4D99FC13D0; Fri, 13 Jul 2012 12:09:41 -0600 (MDT)
Message-ID: <50006467.80205@sherpawebstudios.com>
Date: Fri, 13 Jul 2012 15:09:43 -0300
From: "Carlos M. Martinez" <carlos@sherpawebstudios.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
References: <20120710212029.77643.qmail@joyce.lan> <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net> <20120711115816.GA82178@mail.yitter.info> <37FB8CB6-B97C-472A-9CFC-6C046A9D0C73@kumari.net>
In-Reply-To: <37FB8CB6-B97C-472A-9CFC-6C046A9D0C73@kumari.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Modwest-MailScanner-ID: 4D99FC13D0.A100C
X-Modwest-MailScanner: Found to be clean
X-Modwest-MailScanner-From: carlos@sherpawebstudios.com
X-Mailman-Approved-At: Mon, 16 Jul 2012 02:13:48 -0700
Cc: weirds@ietf.org
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 18:28:38 -0000

Well,, now I regret I did not send this email a few days earlier. I was
locked up in some meetings. You will see the mentions to .arpa below :-)

cheers!

Carlos

------------- earlier draft -------------------

Hi,

Rather than redirection the issue seems to be how to bootstrap the whole
RESTful WHOIS tree so redirections can be performed in the most 'cheap'
(meaning both quick and light on requirements) way.

I've read some negative opinions about putting this information on the
DNS, but, I have to say, it really looks like a tempting option.

For numbers it could be very easy, something like putting a specific
record (SRV seems a good match) on the apexes of every reverse zone
operated by each RIR. In our case, for example:

191/8 -> 191.in-addr.arpa.
_restfulwhois._tcp.lacnic.net.    IN SRV    10 60 80
restwhois.labs.lacnic.net.

164.73/16 -> 73.164.in-addr.arpa.
_restfulwhois._tcp.lacnic.net.    IN    SRV 10 60 80   
restwhois.labs.lacnic.net.

For names (and you know it's not my cup of tea and I can be very
foolish, naive or just plain st**d in what I write):

Option #1: Trusting each zone's operator to put a similar record. IMO, a
recipe for failure.

Option #2: Adding SRV records to the tld. zone hand in hand with the NS
records ? Bad: increase tld zone size.

Option #3: Extending the arpa (via something like tld.restwhois.arpa, it
could be _any_ other service zone for that matter.) tree to include SRV
records for names:

carlos.com, registered at ElCheapoDomains -> com.restwhois.arpa.
_restfulwhois._tcp.carlos.com.restwhois.arpa.    IN    SRV    10 60
80    restwhois.elcheaporegistrar.net.
  


Option #3 obviously needs a lot of work on the part of ICANN in order to
allow registrars to update these SRV registries, or manage them
themselves. Maybe there are other similar approaches that could simplify
this work.

This approach has some interesting advantages, like taking advantage of

On 7/11/12 11:46 AM, Warren Kumari wrote:
> On Jul 11, 2012, at 7:58 AM, Andrew Sullivan wrote:
>
>> On Wed, Jul 11, 2012 at 10:04:49AM +0000, Andy Newton wrote:
>>> Does the location of whois servers change frequently?
> Nope, not frequently at all (in the current world).. But, when they do, hilarity ensues...
>
>>> For the most
>>> part this is static information and engineering this type of
>>> bootstrap process seems to be overkill.
> The big issue is that this sort of thing will get baked into binaries and packages that almost never get updated….
>
>
>> Except when it isn't.  When .org was redelegated, I recall dealing
>> with complaints about "bad whois responses" as late as 2 years after
>> the redelegation, because people's clients had the Verisign server
>> name baked into them.  Given the expansion of the root (and the
>> sometimes, um, optimistic revenue assumptions of prospective registry
>> operators), I think we can expect redelegations to happen at least
>> often enough in future that it will be worth having a way to learn the
>> correct server to ask.
>>
> Yup -- there are a large collection of new gTLDs, and (to me at least) many of the business plans seem, um, interesting…
>
> I think it is prudent to assume that there will be a number of failures that will require redelegation and so (probably) movement of the whois servers…
>
> Ain't this fun?!
>
> W
>
>
>>> running such a service, not just IANA. (BTW, IANA does operate a top
>>> level Whois server today.)
>> Indeed, and the WHOIS Review Team report that was released not so long
>> ago (and mentioned on this list) calls for that operation to get a
>> much larger, with at least a full-service rwhois proxy.
>>
>>> For redirection, there are more interesting cases other than bootstrap -- specifically ERX space in the number registries.
>>>
>> Yes.
>>
>> A
>>
>> -- 
>> Andrew Sullivan
>> ajs@anvilwalrusden.com
>> _______________________________________________
>> weirds mailing list
>> weirds@ietf.org
>> https://www.ietf.org/mailman/listinfo/weirds
>>
> --
> "Let's just say that if complete and utter chaos was lightning, he'd be the sort to stand on a hilltop in a thunderstorm wearing wet copper armour and shouting 'All gods are bastards'."
>
>     -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of Magic)
>
>
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds



From olaf@NLnetLabs.nl  Mon Jul 16 02:22:04 2012
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 725CC21F86C4 for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 02:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q3HcGRoO9DXn for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 02:22:03 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0728B21F86B8 for <weirds@ietf.org>; Mon, 16 Jul 2012 02:22:02 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14] ([IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6G9McOT086883 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 16 Jul 2012 11:22:39 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1342430561; bh=pA6/z+GU9m5hpUYjgI+k7mTQf4a7LsZxorKXZmxakwQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=GlaMhxIWv/5dMVGP8vNzfcaU8Z9fYUjaeIz+z5+NlTGVkfcW11tCOglXTSxZ82jQI m7Zybztymf2bbmql6xFxpBHJOppT/qUWJ9PTNvgonX+TsbJQVGmS+xzaFu37ckR9Oa tnvLSxTVH/BLlpPXhwsp5XLZ0hhcFcAou9JpXfsM=
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_C346C548-7E08-4688-BF22-774F6E394B6A"; protocol="application/pgp-signature"; micalg=pgp-sha1
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <026c01cd632a$ea73b440$bf5b1cc0$@cnnic.cn>
Date: Mon, 16 Jul 2012 11:22:26 +0200
Message-Id: <3753D45C-5A51-47E5-A9B5-C918374CCA4D@NLnetLabs.nl>
References: <AB213C46F8456F4C18954A1D@James-Galvin-2.local> <20120712174209.34670.qmail@joyce.lan> <026101cd6320$45e41050$d1ac30f0$@cnnic.cn> <alpine.BSF.2.00.1207160306580.38251@joyce.lan> <026c01cd632a$ea73b440$bf5b1cc0$@cnnic.cn>
To: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Mon, 16 Jul 2012 11:22:40 +0200 (CEST)
Subject: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 09:22:04 -0000

--Apple-Mail=_C346C548-7E08-4688-BF22-774F6E394B6A
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_20607132-72D1-432E-9D24-51B9811E73E5"


--Apple-Mail=_20607132-72D1-432E-9D24-51B9811E73E5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

[This warrants a new thread]

> I'm just afraid that maybe the different data within a single WEIRDS =
server
> require different credentials. For example, the billing contact name =
is only
> opened to the registered users, but the billing contact phone is only =
opened
> to the specific users who have signed a special agreement or who have =
gotten
> a grant by the domain owner.
>=20
> There is another possible scenario. WEIRDS service A you are querying =
has
> set up alliances with WEIRDS service B and a famous authentication =
service
> C. So the non-public data within WEIRDS service A might be opened to
> registered users of WEIRDS service A, WEIRDS service B, or =
authentication
> service C.
>=20
> I'm not sure the above use cases are likely or not. IMO, the =
requirements of
> WEIRDS authentication needs to be confirmed at first.



Can we work from the assumption that authentication is through features =
offered by HTTP?

What would we be closing the door on if we require that we only rely on =
features offered by HTTP?


--Olaf


NLnet
Labs
Olaf M. Kolkman

www.NLnetLabs.nl
olaf@NLnetLabs.nl

Science Park 400, 1098 XH Amsterdam, The Netherlands




--Apple-Mail=_20607132-72D1-432E-9D24-51B9811E73E5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">[This =
warrants a new thread]<br><div><div><br></div><blockquote =
type=3D"cite"><div>I'm just afraid that maybe the different data within =
a single WEIRDS server<br>require different credentials. For example, =
the billing contact name is only<br>opened to the registered users, but =
the billing contact phone is only opened<br>to the specific users who =
have signed a special agreement or who have gotten<br>a grant by the =
domain owner.<br><br>There is another possible scenario. WEIRDS service =
A you are querying has<br>set up alliances with WEIRDS service B and a =
famous authentication service<br>C. So the non-public data within WEIRDS =
service A might be opened to<br>registered users of WEIRDS service A, =
WEIRDS service B, or authentication<br>service C.<br><br>I'm not sure =
the above use cases are likely or not. IMO, the requirements =
of<br>WEIRDS authentication needs to be confirmed at =
first.<br></div></blockquote></div><div><br></div><div><br></div><div>Can =
we work from the assumption that authentication is through features =
offered by HTTP?</div><div><br></div><div>What would we be closing the =
door on if we require that we only rely on features offered by =
HTTP?</div><div><br></div><div><br></div><div>--Olaf</div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Helvetica; font-size: =
12px; "><br class=3D"Apple-interchange-newline"><table cellspacing=3D"0" =
cellpadding=3D"0" style=3D"background-color: rgb(255, 255, 255); =
border-collapse: collapse; "><tbody><tr><td rowspan=3D"2" valign=3D"top" =
style=3D"width: 97.8px; height: 56.3px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; text-align: right; font: normal normal normal =
19px/normal 'Gill Sans'; "><font class=3D"Apple-style-span" =
color=3D"#777777"><span style=3D"letter-spacing: 0px; =
"><b>NLnet<br></b></span><span style=3D"font: normal normal normal =
24px/normal 'Gill Sans'; letter-spacing: 0px; =
">Labs</span></font></div></td><td valign=3D"top" style=3D"width: =
114.5px; height: 18.1px; border-top-style: solid; border-right-style: =
solid; border-bottom-style: solid; border-left-style: solid; =
border-top-width: 1px; border-right-width: 0px; border-bottom-width: =
1px; border-left-width: 0px; border-top-color: rgb(180, 180, 180); =
border-right-color: transparent; border-bottom-color: rgb(202, 202, =
202); border-left-color: transparent; padding-top: 5px; padding-right: =
5px; padding-bottom: 5px; padding-left: 5px; "><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 12px/normal Helvetica; "><span =
style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Olaf M. Kolkman</font></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 18.1px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 1px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: rgb(202, 202, 202); border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td valign=3D"top" =
style=3D"width: 114.5px; height: 27.2px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"http://www.NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">www.NLnetLabs.nl</font></a></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"mailto:olaf@NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">olaf@NLnetLabs.nl</font></a></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 27.2px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td colspan=3D"3" =
valign=3D"top" style=3D"width: 234.6px; height: 13.2px; padding-top: =
5px; padding-right: 5px; padding-bottom: 5px; padding-left: 5px; "><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Science Park 400, 1098 XH Amsterdam, The =
Netherlands</font></span></div></td></tr></tbody></table><div =
style=3D"color: rgb(158, 158, 158); margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_20607132-72D1-432E-9D24-51B9811E73E5--

--Apple-Mail=_C346C548-7E08-4688-BF22-774F6E394B6A
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-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQIcBAEBAgAGBQJQA91SAAoJEFRqER47aqpkV7AP/iWy25Xn76Ed+zbXIc8n6scE
cl/WS+ugIi5cARcP1ZxS8b+tdriE90CDDV5sEKq3+xnZPo5jUPjT+Yu30WjuWI4d
JNvQSM+Jr18gNDyZ5qAV+J1UB+0gOvFZjIIexmCVzaqON2TSPM2vELUqgIJI4wmP
0brM8DsC+FPm+O2dIDg2JhrIzOjeZ2i6O68SoYVbzeUDAQwmtCUbCDXBIDQzwDK2
01R3JG1shJKQSq5HsT6e9YNfedVaidfepevdK573+q1tkpdkVD5mYD1bm6BLnaVa
SJvpAoshL+WoNcbkiwiXg8dyW3WcCTS7ueQjFVDoCbJi8Z+K4cJ2Jr/SeOW1pGMM
73deRd7tyJYQazUWGz4tzhkr0uKe9ivI0qDAU2Lo+6VlVcyfWGi4+pJOho54QmIb
cotPxo6xO2run5irCTB5h8Pk79DOzgiS5g4kP+uSHkOYlHlLc6buS13fWL1rn1SF
UyIX+Vm3seyxT7KyC5aicKqmmi/GRVg2xm6nH9MlXtPNsSr9Mn8Oq8cRLeq447b/
bJxBVQ0eLdWacRB8hA2GlYZqdflj3eBcWnDrRxnY+JI2xA7FTKjMXGqtUYTN398E
BMQLias+TdqSLOyCQMeP1rS/ntBe+9c6cDz0RB2rG+J4HjjLAboUcDyS2O18H9Fm
pK7sxmO5AUUgIZW8EWRa
=W97/
-----END PGP SIGNATURE-----

--Apple-Mail=_C346C548-7E08-4688-BF22-774F6E394B6A--

From nkong@cnnic.cn  Mon Jul 16 02:23:50 2012
Return-Path: <nkong@cnnic.cn>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81E4321F86D9 for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 02:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[AWL=0.201,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XYPIVABGb9Uy for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 02:23:49 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id B2CF121F86C4 for <weirds@ietf.org>; Mon, 16 Jul 2012 02:23:48 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: nkong@cnnic.cn
Received: from unknown127.0.0.1 (HELO naptrthink) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 16 Jul 2012 17:24:25 +0800
From: "Ning Kong" <nkong@cnnic.cn>
To: "'Arturo Servin'" <aservin@lacnic.net>
References: <AB213C46F8456F4C18954A1D@James-Galvin-2.local> <20120712174209.34670.qmail@joyce.lan> <026101cd6320$45e41050$d1ac30f0$@cnnic.cn> <alpine.BSF.2.00.1207160306580.38251@joyce.lan> <026c01cd632a$ea73b440$bf5b1cc0$@cnnic.cn> <7AA05DA6-6D1C-48B3-93DF-3887C0FCA5EE@lacnic.net>
In-Reply-To: <7AA05DA6-6D1C-48B3-93DF-3887C0FCA5EE@lacnic.net>
Date: Mon, 16 Jul 2012 17:24:22 +0800
Message-ID: <027901cd6334$c96aa0b0$5c3fe210$@cnnic.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF0iLqKQqGaWVOpdd1+y1FYCgG4YwIvRVLqARvlXmcCsIaIQwGwnE6qAbvirFGXkg/3cA==
Content-Language: zh-cn
Cc: 'John R Levine' <johnl@taugh.com>, weirds@ietf.org
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 09:23:51 -0000

> 	I think that your scenarios are valid. e.g. a weirds operator using
open-id
> to provide access to its data.
Good to know.

> 	IMHO it would depend on the local policy of the weirds sever to
decide
> what data to serve.
I agree.

> 	The first step I think would be to decide which authentication and
> authorization methods we would like to have in this protocol.
I hope the "A.2. Service Differentiation in a REST-pect-ful way" of the
coming WEIRDS meeting can help us make sure the authentication requirements
and feasible mechnisms.

Cheers,
Ning

> On 16 Jul 2012, at 05:13, Ning Kong wrote:
> 
> >>> I wonder how you can make sure what credentials are needed on your
> >>> first try.
> >>
> >> I'd send whatever credentials I had for that server.  Do you expect
> >> an individual user to have multiple sets of credentials for a single
> >> WEIRDS
> > server?
> > I'm just afraid that maybe the different data within a single WEIRDS
> > server require different credentials. For example, the billing contact
> > name is only opened to the registered users, but the billing contact
> > phone is only opened to the specific users who have signed a special
> > agreement or who have gotten a grant by the domain owner.
> >
> > There is another possible scenario. WEIRDS service A you are querying
> > has set up alliances with WEIRDS service B and a famous authentication
> > service C. So the non-public data within WEIRDS service A might be
> > opened to registered users of WEIRDS service A, WEIRDS service B, or
> > authentication service C.
> >
> > I'm not sure the above use cases are likely or not. IMO, the
> > requirements of WEIRDS authentication needs to be confirmed at first.
> >
> >>> Furthermore, in some cases maybe you don't have the appropriate
> >>> credential on your first try, but you can acquire one according to
> >>> the response. For example, the response might tell you that if you
> >>> want to access the non-public data, you MUST register an account
> >>> from a specific service provider.
> >>
> >> In that case, you could register the account, then make the same
> >> request
> > with
> >> the account's credentials.
> > The "specific service provider" I mentioned above is not the same
> > WEIRDS service you queried. So it might be another WEIRDS service
> > within an alliance or a specific authentication service. In that case,
> > you have to make the first request in order to know what credential
> > for the requested data is needed.
> >
> > Cheers,
> > Ning
> >
> > _______________________________________________
> > weirds mailing list
> > weirds@ietf.org
> > https://www.ietf.org/mailman/listinfo/weirds


From olaf@NLnetLabs.nl  Mon Jul 16 02:33:17 2012
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5237021F85DF for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 02:33:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DHmVtLfEuEMf for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 02:33:16 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 27DE721F85D1 for <weirds@ietf.org>; Mon, 16 Jul 2012 02:33:16 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14] ([IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6G9Xu0c002612 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 16 Jul 2012 11:33:57 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1342431238; bh=aG99NA4rldovey/gUJYahN350dbVsJWyS5YhDO0qmfU=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=oSpbGBv6JFB1UFRPPw3YS5DHjNrg1FpP2Cx9P8cLZO9WnPRD/ct6zixp+aF5YnK2t N3XbjCd4wD7vUrxMIAu/ryrq6dfmxE30enXzQJbPioxKRZDl7ipMe9zCIfFhNpnL3M n+z8M0X8+HZ1QDK5z4+mUhhYJpnq+ld/ny7UfO9w=
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_D529841D-ACA6-4EAE-969F-ABAA6AE6EB93"; protocol="application/pgp-signature"; micalg=pgp-sha1
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <4FFD24A4.8010900@tana.it>
Date: Mon, 16 Jul 2012 11:33:53 +0200
Message-Id: <92335A19-ADC6-4F9D-9E54-1B6D81261211@NLnetLabs.nl>
References: <20120710212029.77643.qmail@joyce.lan> <4FFD24A4.8010900@tana.it>
To: Alessandro Vesely <vesely@tana.it>
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Mon, 16 Jul 2012 11:33:58 +0200 (CEST)
Cc: weirds@ietf.org
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 09:33:17 -0000

--Apple-Mail=_D529841D-ACA6-4EAE-969F-ABAA6AE6EB93
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_3F383142-CD8B-447D-B7BD-28D438DB9A6E"


--Apple-Mail=_3F383142-CD8B-447D-B7BD-28D438DB9A6E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jul 11, 2012, at 9:00 AM, Alessandro Vesely wrote:

>> The alternative would be a top level redirect server, which would
>> have to be run by IANA or someone they delegate.  There's nothing
>> wrong with that if IANA offers to do so,
>=20
> It was already said that this group can't tell IANA what to do.  Can
> it ask, at least?

I don't see why not.=20

I don't know where the "can't tell IANA what to do comes from" (where =
was it said?)


No hats,

--Olaf




NLnet
Labs
Olaf M. Kolkman

www.NLnetLabs.nl
olaf@NLnetLabs.nl

Science Park 400, 1098 XH Amsterdam, The Netherlands




--Apple-Mail=_3F383142-CD8B-447D-B7BD-28D438DB9A6E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 11, 2012, at 9:00 AM, Alessandro Vesely =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Monaco; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
"><div><blockquote type=3D"cite">The alternative would be a top level =
redirect server, which would<br></blockquote><blockquote =
type=3D"cite">have to be run by IANA or someone they delegate. =
&nbsp;There's nothing<br></blockquote><blockquote type=3D"cite">wrong =
with that if IANA offers to do so,<br></blockquote><br>It was already =
said that this group can't tell IANA what to do. &nbsp;Can<br>it ask, at =
least?<br></div></span></blockquote><br></div><div>I don't see why =
not.&nbsp;</div><div><br></div><div>I don't know where the "can't tell =
IANA what to do comes from" (where was it =
said?)</div><div><br></div><div><br></div><div>No =
hats,</div><div><br></div><div>--Olaf</div><div><br></div><div><br></div><=
br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Helvetica; font-size: =
12px; "><br class=3D"Apple-interchange-newline"><table cellspacing=3D"0" =
cellpadding=3D"0" style=3D"background-color: rgb(255, 255, 255); =
border-collapse: collapse; "><tbody><tr><td rowspan=3D"2" valign=3D"top" =
style=3D"width: 97.8px; height: 56.3px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; text-align: right; font: normal normal normal =
19px/normal 'Gill Sans'; "><font class=3D"Apple-style-span" =
color=3D"#777777"><span style=3D"letter-spacing: 0px; =
"><b>NLnet<br></b></span><span style=3D"font: normal normal normal =
24px/normal 'Gill Sans'; letter-spacing: 0px; =
">Labs</span></font></div></td><td valign=3D"top" style=3D"width: =
114.5px; height: 18.1px; border-top-style: solid; border-right-style: =
solid; border-bottom-style: solid; border-left-style: solid; =
border-top-width: 1px; border-right-width: 0px; border-bottom-width: =
1px; border-left-width: 0px; border-top-color: rgb(180, 180, 180); =
border-right-color: transparent; border-bottom-color: rgb(202, 202, =
202); border-left-color: transparent; padding-top: 5px; padding-right: =
5px; padding-bottom: 5px; padding-left: 5px; "><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 12px/normal Helvetica; "><span =
style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Olaf M. Kolkman</font></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 18.1px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 1px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: rgb(202, 202, 202); border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td valign=3D"top" =
style=3D"width: 114.5px; height: 27.2px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"http://www.NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">www.NLnetLabs.nl</font></a></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"mailto:olaf@NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">olaf@NLnetLabs.nl</font></a></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 27.2px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td colspan=3D"3" =
valign=3D"top" style=3D"width: 234.6px; height: 13.2px; padding-top: =
5px; padding-right: 5px; padding-bottom: 5px; padding-left: 5px; "><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Science Park 400, 1098 XH Amsterdam, The =
Netherlands</font></span></div></td></tr></tbody></table><div =
style=3D"color: rgb(158, 158, 158); margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_3F383142-CD8B-447D-B7BD-28D438DB9A6E--

--Apple-Mail=_D529841D-ACA6-4EAE-969F-ABAA6AE6EB93
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-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQIcBAEBAgAGBQJQA+ABAAoJEFRqER47aqpkFBAQAIUJwDTjR13HePRhhAKiBMBM
n5YnwQsOxNeUqs+0j8SXFUFub68VVsQuH27JyTzrvDYYYThBi1Tt/QxlztEgEnDa
9sxvdXMDrCZJBoNOo31flSgxsM7CLbXGTAcZdI7yrb7xv5QvGb+Y5Syn+3/ZyhDK
LHgGRcxvqOkASNl94D5DqU1Hzut1kK3Kj9iNaZJjtm/8xpn1d3GZDDzkNo1+wqyv
Fy+lqHVlB1DJr/ciKRmXVmPJfydzc96m84Nza3IAkV/Zzn0FEGv7uYBeQUzUgt3C
cXEGxvVB8sAirAIUCdF9cM8d2zSY0aR0YDsBkGnzIn+gxd4FrEet2xm7S2RNkLf8
Y78x1DR7k7s1hiV6CucOGoKtI+05LHOwgNWPASt/a1LNTzOi5Yy+mlTzwcweSm4B
9ihptuH3lGoZia0ka7iFV3h55xHPmgEOBBPK7hBgbWBjrqmiT7QhYVlVvQmrFrjq
zxF4RkCb4PdAO+6xXOzYnj6OVmrgX7rcKZjB8P87QWeIE+pbEcj0hPQi7Y/r31K/
/A5gHAgyKrWxK2N8ZhO7kY4cmgw00Lx+rf/8dX1KLnyfhdIQX5g9xdTIlv9i+EAE
KaRvve7IB9DfyYdW3PYynH1veoXCZpiMRr2LK+aGOCNvN4z+Oavc9n+oJNF/g+ys
669GRoVkxJzWa6Si2CET
=LnuN
-----END PGP SIGNATURE-----

--Apple-Mail=_D529841D-ACA6-4EAE-969F-ABAA6AE6EB93--

From aservin@lacnic.net  Mon Jul 16 02:43:47 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9714421F86E2 for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 02:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.91
X-Spam-Level: 
X-Spam-Status: No, score=0.91 tagged_above=-999 required=5 tests=[AWL=-0.001,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_DIALUP=0.862, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8W-pfm5rrFET for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 02:43:46 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 2825C21F86C4 for <weirds@ietf.org>; Mon, 16 Jul 2012 02:43:46 -0700 (PDT)
Received: from [192.168.1.133] (r186-48-219-110.dialup.adsl.anteldata.net.uy [186.48.219.110]) by mail.lacnic.net.uy (Postfix) with ESMTP id E55CE308447; Mon, 16 Jul 2012 06:44:21 -0300 (UYT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_84458B2D-D751-40E5-B874-71C16D97F32B"
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <92335A19-ADC6-4F9D-9E54-1B6D81261211@NLnetLabs.nl>
Date: Mon, 16 Jul 2012 06:44:21 -0300
Message-Id: <EB537EE1-FE65-42AE-96C3-2AE7D9263E0E@lacnic.net>
References: <20120710212029.77643.qmail@joyce.lan> <4FFD24A4.8010900@tana.it> <92335A19-ADC6-4F9D-9E54-1B6D81261211@NLnetLabs.nl>
To: Olaf Kolkman <olaf@NLnetLabs.nl>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: weirds@ietf.org, Alessandro Vesely <vesely@tana.it>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 09:43:47 -0000

--Apple-Mail=_84458B2D-D751-40E5-B874-71C16D97F32B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


	They even have some data!   =3D)

	http://www.iana.org/domains/root/db/

	=
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml

	=
http://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xml

	=
http://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unic=
ast-address-assignments.xml

	This allow to use IANA as top-down solution to find the correct =
weirds sever, however I must said that after reading some ideas about =
using DNS, I am tempted.=20

Cheers,
as

On 16 Jul 2012, at 06:33, Olaf Kolkman wrote:

>=20
> On Jul 11, 2012, at 9:00 AM, Alessandro Vesely wrote:
>=20
>>> The alternative would be a top level redirect server, which would
>>> have to be run by IANA or someone they delegate.  There's nothing
>>> wrong with that if IANA offers to do so,
>>=20
>> It was already said that this group can't tell IANA what to do.  Can
>> it ask, at least?
>=20
> I don't see why not.=20
>=20
> I don't know where the "can't tell IANA what to do comes from" (where =
was it said?)
>=20
>=20
> No hats,
>=20
> --Olaf
>=20
>=20
>=20
>=20
> NLnet
> Labs
> Olaf M. Kolkman
>=20
> www.NLnetLabs.nl
> olaf@NLnetLabs.nl
>=20
> Science Park 400, 1098 XH Amsterdam, The Netherlands
>=20
>=20
>=20
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds


--Apple-Mail=_84458B2D-D751-40E5-B874-71C16D97F32B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>They even have some data! &nbsp; =
=3D)</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><a =
href=3D"http://www.iana.org/domains/root/db/">http://www.iana.org/domains/=
root/db/</a></div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><a =
href=3D"http://www.iana.org/assignments/ipv4-address-space/ipv4-address-sp=
ace.xml">http://www.iana.org/assignments/ipv4-address-space/ipv4-address-s=
pace.xml</a></div><div><br></div><div><a =
href=3D"http://www.iana.org/assignments/ipv6-address-space/ipv6-address-sp=
ace.xml"><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>http://www.iana.org/assignments/ipv6-address-space/ipv6-address-spa=
ce.xml</a></div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><a =
href=3D"http://www.iana.org/assignments/ipv6-unicast-address-assignments/i=
pv6-unicast-address-assignments.xml">http://www.iana.org/assignments/ipv6-=
unicast-address-assignments/ipv6-unicast-address-assignments.xml</a></div>=
<div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>This allow to use IANA as =
top-down solution to find the correct weirds sever, however I must said =
that after reading some ideas about using DNS, I am =
tempted.&nbsp;</div><div><br></div><div>Cheers,</div><div>as</div><br><div=
><div>On 16 Jul 2012, at 06:33, Olaf Kolkman wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Jul 11, 2012, =
at 9:00 AM, Alessandro Vesely wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"font-family: Monaco; "><blockquote type=3D"cite">The =
alternative would be a top level redirect server, which =
would<br></blockquote><blockquote type=3D"cite">have to be run by IANA =
or someone they delegate. &nbsp;There's =
nothing<br></blockquote><blockquote type=3D"cite">wrong with that if =
IANA offers to do so,<br></blockquote><br>It was already said that this =
group can't tell IANA what to do. &nbsp;Can<br>it ask, at =
least?<br></div></blockquote><br></div><div>I don't see why =
not.&nbsp;</div><div><br></div><div>I don't know where the "can't tell =
IANA what to do comes from" (where was it =
said?)</div><div><br></div><div><br></div><div>No =
hats,</div><div><br></div><div>--Olaf</div><div><br></div><div><br></div><=
br><div>
<span class=3D"Apple-style-span" style=3D"font-size: 12px; "><br =
class=3D"Apple-interchange-newline"></span><table cellspacing=3D"0" =
cellpadding=3D"0" style=3D"background-color: rgb(255, 255, 255); =
border-collapse: collapse; font-size: 12px; "><tbody><tr><td rowspan=3D"2"=
 valign=3D"top" style=3D"width: 97.8px; height: 56.3px; =
border-top-style: solid; border-right-style: solid; border-bottom-style: =
solid; border-left-style: solid; border-top-width: 1px; =
border-right-width: 0px; border-bottom-width: 0px; border-left-width: =
0px; border-top-color: rgb(180, 180, 180); border-right-color: =
transparent; border-bottom-color: transparent; border-left-color: =
transparent; padding-top: 5px; padding-right: 5px; padding-bottom: 5px; =
padding-left: 5px; "><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; text-align: right; font: normal =
normal normal 19px/normal 'Gill Sans'; "><font class=3D"Apple-style-span" =
color=3D"#777777"><span style=3D"letter-spacing: 0px; =
"><b>NLnet<br></b></span><span style=3D"font: normal normal normal =
24px/normal 'Gill Sans'; letter-spacing: 0px; =
">Labs</span></font></div></td><td valign=3D"top" style=3D"width: =
114.5px; height: 18.1px; border-top-style: solid; border-right-style: =
solid; border-bottom-style: solid; border-left-style: solid; =
border-top-width: 1px; border-right-width: 0px; border-bottom-width: =
1px; border-left-width: 0px; border-top-color: rgb(180, 180, 180); =
border-right-color: transparent; border-bottom-color: rgb(202, 202, =
202); border-left-color: transparent; padding-top: 5px; padding-right: =
5px; padding-bottom: 5px; padding-left: 5px; "><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 12px/normal Helvetica; "><span =
style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Olaf M. Kolkman</font></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 18.1px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 1px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: rgb(202, 202, 202); border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td valign=3D"top" =
style=3D"width: 114.5px; height: 27.2px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"http://www.NLnetLabs.nl/"><font class=3D"Apple-style-span" =
color=3D"#777777">www.NLnetLabs.nl</font></a></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"mailto:olaf@NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">olaf@NLnetLabs.nl</font></a></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 27.2px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td colspan=3D"3" =
valign=3D"top" style=3D"width: 234.6px; height: 13.2px; padding-top: =
5px; padding-right: 5px; padding-bottom: 5px; padding-left: 5px; "><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Science Park 400, 1098 XH Amsterdam, The =
Netherlands</font></span></div></td></tr></tbody></table><div =
style=3D"color: rgb(158, 158, 158); margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; font-size: 12px; =
"><br></div><br class=3D"Apple-interchange-newline">
</div>
<br></div>_______________________________________________<br>weirds =
mailing list<br><a =
href=3D"mailto:weirds@ietf.org">weirds@ietf.org</a><br>https://www.ietf.or=
g/mailman/listinfo/weirds<br></blockquote></div><br></body></html>=

--Apple-Mail=_84458B2D-D751-40E5-B874-71C16D97F32B--

From sm@resistor.net  Mon Jul 16 05:12:55 2012
Return-Path: <sm@resistor.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1D321F878A for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 05:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R-Lsrh2lhXDr for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 05:12:52 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A019921F87C7 for <weirds@ietf.org>; Mon, 16 Jul 2012 05:12:52 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q6GCDV1h019045 for <weirds@ietf.org>; Mon, 16 Jul 2012 05:13:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1342440816; bh=hB3JxhO8WUEnaKD0+MqC+EQLxWtxAoKpaKj03Vp9K5Q=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=rS6+IpUc4W5EnItXuQ6HV1b4hgGTxe41DA37O7tFOYky+2XaECfKSMFE1oU1WZS6k URmTStL8s0JJn54F89xttZ4iDGNPOW8yaQ0olH0DW8Z0qgXp9FYRAU53eLJGw4Aq1h ++Rqi0S4Os3HmlcXxJkghRir7Lrx2OiyE1TSlnvk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1342440816; i=@resistor.net; bh=hB3JxhO8WUEnaKD0+MqC+EQLxWtxAoKpaKj03Vp9K5Q=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=gAIIvlx7OpmcGH2AaEGr49J++/hD1vkZ4HZnyU181olwrAPs2vtdVYNBA4gH8v/46 e8LajuSF0kA74WKRaskl8M4SNFAZslFk/D+vtVxOTb1EAGI6jPejZ4TEfRii37AqK7 2MAtbkB0xmr2HGp0YJY/fNU1cGrtrMcS+Co7zuu4=
Message-Id: <6.2.5.6.2.20120716033630.09b49748@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 16 Jul 2012 03:47:19 -0700
To: weirds@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <EB537EE1-FE65-42AE-96C3-2AE7D9263E0E@lacnic.net>
References: <20120710212029.77643.qmail@joyce.lan> <4FFD24A4.8010900@tana.it> <92335A19-ADC6-4F9D-9E54-1B6D81261211@NLnetLabs.nl> <EB537EE1-FE65-42AE-96C3-2AE7D9263E0E@lacnic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 12:12:55 -0000

At 02:44 16-07-2012, Arturo Servin wrote:

>They even have some data!   =)
>
>http://www.iana.org/domains/root/db/
>
>http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml
>
>http://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xml
>
>http://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unicast-address-assignments.xml
>
>This allow to use IANA as top-down solution to find the correct 
>weirds sever, however I

Yes.

The above, or some existing procedure, can be used by the six 
(number) operators who require the data.

Regards,
-sm 


From sm@resistor.net  Mon Jul 16 05:13:03 2012
Return-Path: <sm@resistor.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9857321F842F for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 05:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gomb2Vr+DqGl for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 05:12:59 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 911EE21F87EE for <weirds@ietf.org>; Mon, 16 Jul 2012 05:12:59 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q6GCDV1j019045; Mon, 16 Jul 2012 05:13:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1342440820; bh=Qx2uOBxqsdPPGM8lQtY6nwuEvVCoAqOYOfMrOB/V2rk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qw8M2WLcNRHlXdwALdFBQpdpszj2pbOFA3+wBWNvOApvwfr+QUXzZOotmosCmhBpu AzppQIYIH6SsoGyf5MDZOhxLUOWJ23jYJc52m2s5V2b+AO2fcebvIGu0O6Y3WpyiHE 9DTeb0rN13/gZ5Wn2CnG4HfuoV3BjiDzZ3vE6kHk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1342440820; i=@resistor.net; bh=Qx2uOBxqsdPPGM8lQtY6nwuEvVCoAqOYOfMrOB/V2rk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=XjjXoGW2W4zL1cWDisboeUu0NUsYcSX9gPzML8Om0PMLh5CGmKcHsD+4irEkGgfyE qA7UxFXy4+3FMDY3bugOv+IbV3h5+VBD3ccB4BViV8tn42zBD5pTOUxnKqSGvek7An SX9Bet89uFE+qu+2ZXyK0PbfUCPkNSqJSzCKt470=
Message-Id: <6.2.5.6.2.20120716034824.08edd928@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 16 Jul 2012 05:10:53 -0700
To: "Ning Kong" <nkong@cnnic.cn>
From: SM <sm@resistor.net>
In-Reply-To: <027901cd6334$c96aa0b0$5c3fe210$@cnnic.cn>
References: <AB213C46F8456F4C18954A1D@James-Galvin-2.local> <20120712174209.34670.qmail@joyce.lan> <026101cd6320$45e41050$d1ac30f0$@cnnic.cn> <alpine.BSF.2.00.1207160306580.38251@joyce.lan> <026c01cd632a$ea73b440$bf5b1cc0$@cnnic.cn> <7AA05DA6-6D1C-48B3-93DF-3887C0FCA5EE@lacnic.net> <027901cd6334$c96aa0b0$5c3fe210$@cnnic.cn>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: weirds@ietf.org
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 12:13:03 -0000

At 02:24 16-07-2012, Ning Kong wrote:
>I hope the "A.2. Service Differentiation in a REST-pect-ful way" of the
>coming WEIRDS meeting can help us make sure the authentication requirements
>and feasible mechnisms.

There are different ways, e.g. OAuth2, for authentication.  The 
initial requirements, from what I understand, is to offer different 
information if the client is authorized to access the 
information.  The questions would be:

   (a) which authentication mechanism must be implemented

   (b) which response codes, for example, to send

   (c) whether the client should be able to request a different class
       of service

John Levine mentioned doing the authentication on the first query 
instead of having more than one query [1].  In terms of access to the 
resource there isn't much of an argument to prohibit that.   If a 
client can access a resource anonymously it does not make sense not 
to prohibit that if the client is authenticated.

It seems to me that it may provide alternatives to resolve 
non-technical problems if the people want to solve them (in other 
venues).  Item (3) is not a requirement [2].  John Levine mentions 
that "Not if our goal is to produce something useful" in a comment 
about supporting objects [3].  All of the above can be done with MAYs 
if the objective is design a paper tiger.  Some people might disagree 
that it is not a real tiger.  If RESTful is useful people will use it [4].

Regards,
-sm

1. I am ignoring some details.
2. If authorization is determined in other venues
3. http://www.ietf.org/mail-archive/web/weirds/current/msg01306.html
4. http://www.ietf.org/mail-archive/web/weirds/current/msg01045.html 


From galvin+weirds@elistx.com  Mon Jul 16 05:22:31 2012
Return-Path: <galvin+weirds@elistx.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1528921F87CD for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 05:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QsCWwibTwMku for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 05:22:30 -0700 (PDT)
Received: from ee01.elistx.com (ee01.elistx.com [67.155.182.182]) by ietfa.amsl.com (Postfix) with ESMTP id 7F2B021F87E0 for <weirds@ietf.org>; Mon, 16 Jul 2012 05:22:30 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31965) with ESMTP id <0M790045G6DVZY@elistx.com> for weirds@ietf.org; Mon, 16 Jul 2012 08:22:43 -0400 (EDT)
Date: Mon, 16 Jul 2012 08:23:21 -0400
From: Jim Galvin <galvin+weirds@elistx.com>
In-reply-to: <3753D45C-5A51-47E5-A9B5-C918374CCA4D@NLnetLabs.nl>
To: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Message-id: <EF4B6E94ADD391DEA4D19255@James-Galvin-2.local>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <AB213C46F8456F4C18954A1D@James-Galvin-2.local> <20120712174209.34670.qmail@joyce.lan> <026101cd6320$45e41050$d1ac30f0$@cnnic.cn> <alpine.BSF.2.00.1207160306580.38251@joyce.lan> <026c01cd632a$ea73b440$bf5b1cc0$@cnnic.cn> <3753D45C-5A51-47E5-A9B5-C918374CCA4D@NLnetLabs.nl>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 12:22:31 -0000

-- On July 16, 2012 11:22:26 AM +0200 Olaf Kolkman <olaf@NLnetLabs.nl> 
wrote regarding [weirds] Authentication Methods --

> Can we work from the assumption that authentication is through
> features offered by HTTP?

Yes.


> What would we be closing the door on if we require that we only rely
> on features offered by HTTP?

If there is a redirection there is the question of what responsibility 
we have for the services at that destination.  I think it's out of 
scope but I wanted to mention it for completeness.

Jim


From aservin@lacnic.net  Mon Jul 16 06:04:54 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D3F121F87FD for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 06:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.033
X-Spam-Level: 
X-Spam-Status: No, score=0.033 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_DIALUP=0.862, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPYn6LnQ93uz for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 06:04:53 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 1904521F87FF for <weirds@ietf.org>; Mon, 16 Jul 2012 06:04:53 -0700 (PDT)
Received: from [192.168.189.87] (r186-52-129-45.dialup.adsl.anteldata.net.uy [186.52.129.45]) by mail.lacnic.net.uy (Postfix) with ESMTP id F0FC9308437; Mon, 16 Jul 2012 10:05:34 -0300 (UYT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <6.2.5.6.2.20120716033630.09b49748@resistor.net>
Date: Mon, 16 Jul 2012 10:05:35 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D354ED5-ED5D-461A-9A0A-5642FFDFE509@lacnic.net>
References: <20120710212029.77643.qmail@joyce.lan> <4FFD24A4.8010900@tana.it> <92335A19-ADC6-4F9D-9E54-1B6D81261211@NLnetLabs.nl> <EB537EE1-FE65-42AE-96C3-2AE7D9263E0E@lacnic.net> <6.2.5.6.2.20120716033630.09b49748@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: weirds@ietf.org
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 13:04:54 -0000

	And possibly names:

>> http://www.iana.org/domains/root/db/

	But not sure about that.

Regards
as


On 16 Jul 2012, at 07:47, SM wrote:

> At 02:44 16-07-2012, Arturo Servin wrote:
>=20
>> They even have some data!   =3D)
>>=20
>> http://www.iana.org/domains/root/db/
>>=20
>> =
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml
>>=20
>> =
http://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xml
>>=20
>> =
http://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unic=
ast-address-assignments.xml
>>=20
>> This allow to use IANA as top-down solution to find the correct =
weirds sever, however I
>=20
> Yes.
>=20
> The above, or some existing procedure, can be used by the six (number) =
operators who require the data.
>=20
> Regards,
> -sm=20
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds


From sm@resistor.net  Mon Jul 16 09:14:19 2012
Return-Path: <sm@resistor.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 015A821F8675 for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 09:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id imsIULJff6lX for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 09:14:16 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E6F721F867C for <weirds@ietf.org>; Mon, 16 Jul 2012 09:14:16 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q6GGEsic005316; Mon, 16 Jul 2012 09:14:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1342455300; bh=m1AYswglWmIWCdv36ylKjqmRtHBnO+J1ugZ2336sSxU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=LpBeVpIYnCD6jtPkD9cPQerRTTCk9KUTFscm6cghBR6B94QI1AF174OdmaFfbHT4E lRRPgi89DE0KsPRhFJcQW7P8Tr5ThsnkSNMnVw6dcIzTfvvfQjhaBiVxHv9j+PPjjt u/O2VxzkpEkBV90cRTNTx/AIPwtMqR8b5PekQy9E=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1342455300; i=@resistor.net; bh=m1AYswglWmIWCdv36ylKjqmRtHBnO+J1ugZ2336sSxU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=a8G4yfk1kU06BtwB6dhXmM6ITUQXwBMdQOOwFED/j/KJuBcP3U1mQR8QrELE6m8B5 xHZief320JFVffoP1D96WQx+bGjX51LseYe1JNAy4O+XUPv6nPmwX1TCpauG0uWXnW h81cJEmcLPZpIDg6kaeSZGAkIs+Xrlb7fXJIsZPY=
Message-Id: <6.2.5.6.2.20120716080339.07f4cb50@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 16 Jul 2012 08:28:39 -0700
To: Arturo Servin <aservin@lacnic.net>
From: SM <sm@resistor.net>
In-Reply-To: <6D354ED5-ED5D-461A-9A0A-5642FFDFE509@lacnic.net>
References: <20120710212029.77643.qmail@joyce.lan> <4FFD24A4.8010900@tana.it> <92335A19-ADC6-4F9D-9E54-1B6D81261211@NLnetLabs.nl> <EB537EE1-FE65-42AE-96C3-2AE7D9263E0E@lacnic.net> <6.2.5.6.2.20120716033630.09b49748@resistor.net> <6D354ED5-ED5D-461A-9A0A-5642FFDFE509@lacnic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: weirds@ietf.org
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 16:14:19 -0000

At 06:05 16-07-2012, Arturo Servin wrote:
>         And possibly names:
> >> http://www.iana.org/domains/root/db/

I should have removed that link in my previous message.  There are 
significant differences in the approach adopted by numbers and 
names.  The names part can be described as an intractable problem.

>         But not sure about that.

Yes.

Regards,
-sm 


From johnl@iecc.com  Mon Jul 16 22:16:15 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B652321F85C7 for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 22:16:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.138
X-Spam-Level: 
X-Spam-Status: No, score=-111.138 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kPYfpu9CLCRC for <weirds@ietfa.amsl.com>; Mon, 16 Jul 2012 22:16:15 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id D4F6E21F85C6 for <weirds@ietf.org>; Mon, 16 Jul 2012 22:16:14 -0700 (PDT)
Received: (qmail 89243 invoked from network); 17 Jul 2012 05:17:01 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 17 Jul 2012 05:17:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5004f54d.xn--30v786c.k1207; i=johnl@user.iecc.com; bh=3TMB/eB2ucefy7CypWpExnfzySYWTOkcDt21fax240Y=; b=b6dcC6Yyx/Yarmkbwj58bueKyG4Xmd1b70fi/o3SKbnwwuevBY3jXOX0R4XupGGqCBBoaBWhm0wl6ps64MqeW2t6vVKFGPAjilCf7YdStNN0myR6LQGijGrg+jMGwJaDrnuQEuL0J/6BPyIkXw66u5KgiakPuOccLnVHJYPUYd4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5004f54d.xn--30v786c.k1207; olt=johnl@user.iecc.com; bh=3TMB/eB2ucefy7CypWpExnfzySYWTOkcDt21fax240Y=; b=vPJxonjuG60F+HXzC7B/xB8OxWuJP/vaU2VLud8MuO0p59RDRvmxS3V8bOOQVBDaIbbw/YrxR8bpRoUahL0QPNIWIhcxc/O+tOvpd/MdjMMwPgGJz10mQyyU0ilEMN9c6UhiC1A76bC9w6yIjtOLO5aMcrtdNoLFapJ+FoanOiU=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 17 Jul 2012 05:16:38 -0000
Message-ID: <20120717051638.13798.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <92335A19-ADC6-4F9D-9E54-1B6D81261211@NLnetLabs.nl>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 05:16:15 -0000

>I don't know where the "can't tell IANA what to do comes from" (where was it said?)

Probably me.  RFCs can certainly tell IANA to add stuff to protocol registries.

But I don't see any process for the IETF to tell IANA to run a WEIRDS
server, particularly one that's likely to get an enormous amount of
traffic, unlike their current WHOIS server, and would require significant
amounts of both software development and ongoing ops activity.

R's,
John

From olaf@NLnetLabs.nl  Tue Jul 17 00:28:52 2012
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D99B221F85AF for <weirds@ietfa.amsl.com>; Tue, 17 Jul 2012 00:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bhq7bIRAZl2H for <weirds@ietfa.amsl.com>; Tue, 17 Jul 2012 00:28:44 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2175821F85C5 for <weirds@ietf.org>; Tue, 17 Jul 2012 00:28:43 -0700 (PDT)
Received: from dhcp-91.nlnetlabs.nl (dhcp-91.nlnetlabs.nl [213.154.224.91]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6H7TOE7057309 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 17 Jul 2012 09:29:25 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1342510167; bh=Yy+zuhrXjd+w8b3E08L7Fv405f3HOTkdLjiuoD64MKI=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=LloGH5S/iK5kj3Gpvif+stpSv3fKyQgO/UNCLNlUw0yi3W9jNJpAkwanGPOG9R9dy TSXCfbpFRCXHKn/8HeXuDBvUjImERa0sTXtIMX1qzR7c+dpZzqDm0j8lTsjeoDVLgd x6u2dHfI2wux9pPVW70rysyVdewGAX8V1fk6Y7H0=
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_95C0E185-0E11-488A-AAB6-1E51BF76C99D"; protocol="application/pgp-signature"; micalg=pgp-sha1
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <20120717051638.13798.qmail@joyce.lan>
Date: Tue, 17 Jul 2012 09:29:24 +0200
Message-Id: <0F716BD9-2E24-4AD9-9547-188B99EFF6BD@NLnetLabs.nl>
References: <20120717051638.13798.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Tue, 17 Jul 2012 09:29:25 +0200 (CEST)
Cc: weirds@ietf.org
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 07:28:53 -0000

--Apple-Mail=_95C0E185-0E11-488A-AAB6-1E51BF76C99D
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_A27D5A0E-75A9-499E-9547-2F36C2307E10"


--Apple-Mail=_A27D5A0E-75A9-499E-9547-2F36C2307E10
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jul 17, 2012, at 7:16 AM, John Levine wrote:

> But I don't see any process for the IETF to tell IANA to run a WEIRDS
> server, particularly one that's likely to get an enormous amount of
> traffic, unlike their current WHOIS server, and would require =
significant
> amounts of both software development and ongoing ops activity.


If the IETF thinks running such service is the best engineering solution =
then I am sure we can work it out. That said, operational considerations =
(such aligning operational costs with those that benefit) might come =
into the equation of what is the 'best solution'.

As your WG chair I'd be happy to coordinate once we are a little closer =
to figuring if establishing a WEIRDs server is a plausible wish of the =
working group. I am not sure we are there yet.

--Olaf




NLnet
Labs
Olaf M. Kolkman

www.NLnetLabs.nl
olaf@NLnetLabs.nl

Science Park 400, 1098 XH Amsterdam, The Netherlands




--Apple-Mail=_A27D5A0E-75A9-499E-9547-2F36C2307E10
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 17, 2012, at 7:16 AM, John Levine wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Monaco; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">But I don't =
see any process for the IETF to tell IANA to run a WEIRDS<br>server, =
particularly one that's likely to get an enormous amount of<br>traffic, =
unlike their current WHOIS server, and would require =
significant<br>amounts of both software development and ongoing ops =
activity.<br></span></blockquote><br></div><div><br></div><div>If the =
IETF thinks running such service is the best engineering solution then I =
am sure we can work it out. That said, operational considerations (such =
aligning operational costs with those that benefit) might come into the =
equation of what is the 'best solution'.</div><div><br></div><div>As =
your WG chair I'd be happy to coordinate once we are a little closer to =
figuring if establishing a WEIRDs server is a plausible wish of the =
working group. I am not sure we are there =
yet.</div><div><br></div><div>--Olaf</div><div><br></div><div><br></div><b=
r><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Helvetica; font-size: =
12px; "><br class=3D"Apple-interchange-newline"><table cellspacing=3D"0" =
cellpadding=3D"0" style=3D"background-color: rgb(255, 255, 255); =
border-collapse: collapse; "><tbody><tr><td rowspan=3D"2" valign=3D"top" =
style=3D"width: 97.8px; height: 56.3px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; text-align: right; font: normal normal normal =
19px/normal 'Gill Sans'; "><font class=3D"Apple-style-span" =
color=3D"#777777"><span style=3D"letter-spacing: 0px; =
"><b>NLnet<br></b></span><span style=3D"font: normal normal normal =
24px/normal 'Gill Sans'; letter-spacing: 0px; =
">Labs</span></font></div></td><td valign=3D"top" style=3D"width: =
114.5px; height: 18.1px; border-top-style: solid; border-right-style: =
solid; border-bottom-style: solid; border-left-style: solid; =
border-top-width: 1px; border-right-width: 0px; border-bottom-width: =
1px; border-left-width: 0px; border-top-color: rgb(180, 180, 180); =
border-right-color: transparent; border-bottom-color: rgb(202, 202, =
202); border-left-color: transparent; padding-top: 5px; padding-right: =
5px; padding-bottom: 5px; padding-left: 5px; "><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 12px/normal Helvetica; "><span =
style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Olaf M. Kolkman</font></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 18.1px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 1px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: rgb(202, 202, 202); border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td valign=3D"top" =
style=3D"width: 114.5px; height: 27.2px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"http://www.NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">www.NLnetLabs.nl</font></a></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"mailto:olaf@NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">olaf@NLnetLabs.nl</font></a></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 27.2px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td colspan=3D"3" =
valign=3D"top" style=3D"width: 234.6px; height: 13.2px; padding-top: =
5px; padding-right: 5px; padding-bottom: 5px; padding-left: 5px; "><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Science Park 400, 1098 XH Amsterdam, The =
Netherlands</font></span></div></td></tr></tbody></table><div =
style=3D"color: rgb(158, 158, 158); margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_A27D5A0E-75A9-499E-9547-2F36C2307E10--

--Apple-Mail=_95C0E185-0E11-488A-AAB6-1E51BF76C99D
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-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQIcBAEBAgAGBQJQBRRUAAoJEFRqER47aqpkdNsP/RtErTr1XL+zlCSVSr6//ZAr
L3Gs9TZ49JeD2xgxMmCgJbasgeGrjCswiQQXo9bv1sV9w9VePxwDssw675lbBDgG
WsYYjVJPEotjvB1ETrYfYewy6mJc3JjZJIAB+ZlmNBTXDIZZZ3nvxFG0EPJu9mQl
8L/yHwxt38CxS5yFBSsyAS9ahZAHZ/GCjCMgdGhV2jFp7err1PsrdVS93KglGXu4
oJi7iWOCaeUIAEyD3Kwx/rmQryZ0c1kSaFHAiX17mvUpDOyGcWPS/cHjct0RZnvE
8r1vwOsvUNV/Li34gqQU/FdPo1MY+6AryW30Li7qtnrA2k9Vv7oEIUX49OgqpiUZ
Hmnio+XOZOeibNiz6w/Uf6GLyykmWTcJl1TDYlX66PI4vDBdWu2THiZbQca8Ylwf
S92PVX92nx4sR5wB9cPcv66601rx4+WdtetsvfZmdyMjRaUFiO1PGi1z+Jpa6ogF
XFsV6K88i683FdBRSbYv5Ydf+uY3n4T1MqwHlKm0hU9M8WF7VZ6bjnXqAtXwWfgZ
wzZtZ1Z3nds7VRN1Kf2AK6DK9ajvVR73XyGib5gi3/cwn5J4thNk1SRTPSwmcsIX
tBimTNrVzGqjjZ+tC2KmvwQTXNOXyEdzUUgk8zNmRzzg5iB5KG1fxxlyVhb9ITrx
u7PGG/kB48sYb5nyG7FN
=+OlZ
-----END PGP SIGNATURE-----

--Apple-Mail=_95C0E185-0E11-488A-AAB6-1E51BF76C99D--

From nkong@cnnic.cn  Tue Jul 17 00:56:23 2012
Return-Path: <nkong@cnnic.cn>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6794321F85FD for <weirds@ietfa.amsl.com>; Tue, 17 Jul 2012 00:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.426
X-Spam-Level: 
X-Spam-Status: No, score=-2.426 tagged_above=-999 required=5 tests=[AWL=0.173,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id flhadJin+TDW for <weirds@ietfa.amsl.com>; Tue, 17 Jul 2012 00:56:22 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id 52B3721F8594 for <weirds@ietf.org>; Tue, 17 Jul 2012 00:56:22 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: nkong@cnnic.cn
Received: from unknown127.0.0.1 (HELO naptrthink) (127.0.0.1) by 127.0.0.1 with SMTP; Tue, 17 Jul 2012 15:57:03 +0800
From: "Ning Kong" <nkong@cnnic.cn>
To: "'Jim Galvin'" <galvin+weirds@elistx.com>, "'Web Extensible Internet Registration Data Service Working Group'" <weirds@ietf.org>
References: <AB213C46F8456F4C18954A1D@James-Galvin-2.local>	<20120712174209.34670.qmail@joyce.lan>	<026101cd6320$45e41050$d1ac30f0$@cnnic.cn>	<alpine.BSF.2.00.1207160306580.38251@joyce.lan>	<026c01cd632a$ea73b440$bf5b1cc0$@cnnic.cn>	<3753D45C-5A51-47E5-A9B5-C918374CCA4D@NLnetLabs.nl> <EF4B6E94ADD391DEA4D19255@James-Galvin-2.local>
In-Reply-To: <EF4B6E94ADD391DEA4D19255@James-Galvin-2.local>
Date: Tue, 17 Jul 2012 15:56:58 +0800
Message-ID: <033b01cd63f1$bdd651a0$3982f4e0$@cnnic.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF0iLqKQqGaWVOpdd1+y1FYCgG4YwIvRVLqARvlXmcCsIaIQwGwnE6qAofg0tUC+byEZJd1Xtng
Content-Language: zh-cn
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 07:56:23 -0000

> > What would we be closing the door on if we require that we only rely
> > on features offered by HTTP?
> 
> If there is a redirection there is the question of what responsibility we
have
> for the services at that destination.  I think it's out of scope but I
wanted to
> mention it for completeness.

I wonder whether the OAuth 2.0 can be considered as a possible
authentication method for WEIRDS based on the assumption that we only rely
on features offered by HTTP.

Cheers,
Ning


From andy@arin.net  Tue Jul 17 06:05:57 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34D2D21F86F2 for <weirds@ietfa.amsl.com>; Tue, 17 Jul 2012 06:05:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_64=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yk+eeTAxFxQW for <weirds@ietfa.amsl.com>; Tue, 17 Jul 2012 06:05:56 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 3D43B21F86EE for <weirds@ietf.org>; Tue, 17 Jul 2012 06:05:56 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id 094D21651AF; Tue, 17 Jul 2012 09:06:43 -0400 (EDT)
Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp1.arin.net (Postfix) with ESMTP id 7EA2B164FD5; Tue, 17 Jul 2012 09:06:42 -0400 (EDT)
Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.283.3; Tue, 17 Jul 2012 09:06:32 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0298.004; Tue, 17 Jul 2012 09:06:42 -0400
From: Andy Newton <andy@arin.net>
To: Olaf Kolkman <olaf@NLnetLabs.nl>
Thread-Topic: [weirds] Redirection in the RESTful WHOIS world
Thread-Index: AQHNW5IHZp05Hg+U/kiz3QFYlCIyNpcdJ5KAgAQlcoCAACxagIAAVgUAgAE3uICAAEh4gIAAoigAgAgGaYCAAUp1AIAAJRgAgABeFIA=
Date: Tue, 17 Jul 2012 13:06:40 +0000
Message-ID: <E8E92ABB-ED46-436E-877F-A67A00EF5E4B@arin.net>
References: <20120717051638.13798.qmail@joyce.lan> <0F716BD9-2E24-4AD9-9547-188B99EFF6BD@NLnetLabs.nl>
In-Reply-To: <0F716BD9-2E24-4AD9-9547-188B99EFF6BD@NLnetLabs.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.149.252.96]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3634E2DBE944B646A563B27447C4C8CC@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John Levine <johnl@taugh.com>, "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 13:05:57 -0000

On Jul 17, 2012, at 3:29 AM, Olaf Kolkman wrote:

>=20
> On Jul 17, 2012, at 7:16 AM, John Levine wrote:
>=20
>> But I don't see any process for the IETF to tell IANA to run a WEIRDS
>> server, particularly one that's likely to get an enormous amount of
>> traffic, unlike their current WHOIS server, and would require significan=
t
>> amounts of both software development and ongoing ops activity.
>=20
>=20
> If the IETF thinks running such service is the best engineering solution =
then I am sure we can work it out. That said, operational considerations (s=
uch aligning operational costs with those that benefit) might come into the=
 equation of what is the 'best solution'.
>=20
> As your WG chair I'd be happy to coordinate once we are a little closer t=
o figuring if establishing a WEIRDs server is a plausible wish of the worki=
ng group. I am not sure we are there yet.

Given the bootstrapping method John outlined using CNAMEs or delegations in=
 weirds.arpa in the "bootstrapping" thread, I don't think anything beyond t=
heir normal services is needed of IANA from a server standpoint.

-andy=

From andy@arin.net  Tue Jul 17 06:09:24 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4388211E8095 for <weirds@ietfa.amsl.com>; Tue, 17 Jul 2012 06:09:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level: 
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SEIAQlyTlB1K for <weirds@ietfa.amsl.com>; Tue, 17 Jul 2012 06:09:23 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 5A36611E8091 for <weirds@ietf.org>; Tue, 17 Jul 2012 06:09:23 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 7656E2157AF; Tue, 17 Jul 2012 09:10:10 -0400 (EDT)
Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp2.arin.net (Postfix) with ESMTP id 19696214412; Tue, 17 Jul 2012 09:10:10 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.283.3; Tue, 17 Jul 2012 09:10:00 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Tue, 17 Jul 2012 09:10:09 -0400
From: Andy Newton <andy@arin.net>
To: John R Levine <johnl@taugh.com>
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: AQHNX65QpJoDeMyMZUyzRwJlYVqyVZck9d2AgAD9kICAB8s+AA==
Date: Tue, 17 Jul 2012 13:10:07 +0000
Message-ID: <E9EBF95B-56DB-4964-A00D-643DA069393E@arin.net>
References: <20120711203242.48919.qmail@joyce.lan> <9FC1FEF3-EE0D-4CF4-BA6E-DE2A12ACB092@arin.net> <alpine.BSF.2.00.1207111728450.47528@joyce.lan> <BB77C35A-CAC7-4E11-A4EF-CC8AFCEB438D@arin.net> <alpine.BSF.2.00.1207120959530.60846@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1207120959530.60846@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.149.252.96]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4F6FF307A1A0F44194F65AB597043AB7@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 13:09:24 -0000

On Jul 12, 2012, at 10:08 AM, John R Levine wrote:

>>> defeats the purpose.  I suppose one could use a CNAME kludge of
>>> <tld>.wierdsservers.net or <1.2.3.4.5.6>.weirdsservers.net, analogous
>>> to Rodney's whoisservers.net, that doesn't require a lookup before the
>>> http query.
>>=20
>> Interesting. Why not XXXX.weirds.arpa?
>=20
> Uh, because I wasn't thinking far enough ahead?  That would involve IANA,=
 but in a pretty benign way.  They'd have to update their processes to allo=
w entities that have been delegated a TLD or a top level IP range to regist=
er and update WEIRDS servers, but it'd be no more work than maintaining the=
 in-addr zone which they do now.

I think this is workable and strikes the right balance for the needs of the=
 clients vs. distributed bootstrapping.

-andy=

From Ray.Bellis@nominet.org.uk  Wed Jul 18 01:52:29 2012
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97F7A21F8604 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 01:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.578
X-Spam-Level: 
X-Spam-Status: No, score=-10.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZpXx03eraIW for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 01:52:28 -0700 (PDT)
Received: from mx3.nominet.org.uk (mx3.nominet.org.uk [213.248.199.23]) by ietfa.amsl.com (Postfix) with ESMTP id 674FE21F84C5 for <weirds@ietf.org>; Wed, 18 Jul 2012 01:52:28 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:Received:Received:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=cJK1h6hprvEs8pzcSvRLGHEN/qgrS6U6zW5sG/wlcRUqpHJOrPBFOCtK SjnbZN3fnkaLF0Sgde0bik5sHOxX8yG77BNFc6LeOyy8Z/Q0e964ghHnq jHhmL3vvcuy6Uq8;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1342601598; x=1374137598; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[weirds]=20Authentication=20Methods |Date:=20Wed,=2018=20Jul=202012=2008:53:16=20+0000 |Message-ID:=20<4483E6EE-7E4E-442C-9ADD-2E8B9D549B54@nomi net.org.uk>|To:=20Olaf=20Kolkman=20<olaf@NLnetLabs.nl> |CC:=20Web=20Extensible=20Internet=20Registration=20Data =20Service=20Working=20Group=0D=0A=09<weirds@ietf.org> |MIME-Version:=201.0|Content-Transfer-Encoding:=20quoted- printable|Content-ID:=20<6cd4d3d6-c839-4c04-a3a8-8c991ac0 43d6>|In-Reply-To:=20<3753D45C-5A51-47E5-A9B5-C918374CCA4 D@NLnetLabs.nl>|References:=20<AB213C46F8456F4C18954A1D@J ames-Galvin-2.local>=0D=0A=20<20120712174209.34670.qmail@ joyce.lan>=0D=0A=20<026101cd6320$45e41050$d1ac30f0$@cnnic .cn>=0D=0A=20<alpine.BSF.2.00.1207160306580.38251@joyce.l an>=0D=0A=20<026c01cd632a$ea73b440$bf5b1cc0$@cnnic.cn>=0D =0A=20<3753D45C-5A51-47E5-A9B5-C918374CCA4D@NLnetLabs.nl>; bh=be1r+4bfGykyeP9cO8gUiT8dj4JYLVdFEZbBnpMLM4A=; b=pbVp1qVdY0mbYpRO3YqPJ14DYLZDQmb3AP873xNWy15Vm5fuGIKIckUm Y9ES+HZqH7F8fA0SzYZiRe9rQ4nY96pzy58I7LHff21+orJtbFdvnQP5X 7pvv4pGikIGIvUB;
X-IronPort-AV: E=Sophos;i="4.77,609,1336345200"; d="scan'208";a="41644108"
Received: from wds-exc1.okna.nominet.org.uk ([213.248.197.144]) by mx3.nominet.org.uk with ESMTP; 18 Jul 2012 09:53:17 +0100
Received: from WDS-EXC2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4]) by wds-exc1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f%19]) with mapi; Wed, 18 Jul 2012 09:53:15 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Olaf Kolkman <olaf@NLnetLabs.nl>
Thread-Topic: [weirds] Authentication Methods
Thread-Index: AQHNYzSVaT5sUZ9lAki+OrM4ADgQbpcurl0A
Date: Wed, 18 Jul 2012 08:53:16 +0000
Message-ID: <4483E6EE-7E4E-442C-9ADD-2E8B9D549B54@nominet.org.uk>
References: <AB213C46F8456F4C18954A1D@James-Galvin-2.local> <20120712174209.34670.qmail@joyce.lan> <026101cd6320$45e41050$d1ac30f0$@cnnic.cn> <alpine.BSF.2.00.1207160306580.38251@joyce.lan> <026c01cd632a$ea73b440$bf5b1cc0$@cnnic.cn> <3753D45C-5A51-47E5-A9B5-C918374CCA4D@NLnetLabs.nl>
In-Reply-To: <3753D45C-5A51-47E5-A9B5-C918374CCA4D@NLnetLabs.nl>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6cd4d3d6-c839-4c04-a3a8-8c991ac043d6>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 08:52:29 -0000

On 16 Jul 2012, at 10:22, Olaf Kolkman wrote:

> Can we work from the assumption that authentication is through features o=
ffered by HTTP?

Yes, please!

Ray



From johnl@iecc.com  Wed Jul 18 07:26:32 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E43121F876D for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 07:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.14
X-Spam-Level: 
X-Spam-Status: No, score=-111.14 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxcLKaZWGWpk for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 07:26:31 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id C948721F877D for <weirds@ietf.org>; Wed, 18 Jul 2012 07:26:30 -0700 (PDT)
Received: (qmail 31355 invoked from network); 18 Jul 2012 14:27:19 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 18 Jul 2012 14:27:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5006c7c7.xn--btvx9d.k1207; i=johnl@user.iecc.com; bh=9X9/podiYHjMImzj6lMDbsVL77DYVWbK6OuOFpips+g=; b=uKDdU4rcSPb0o23MSa8cEdfbShaz6x+Y4EYWj+Dg/4Fn3/vzu+NmW7nXzTq2il83r3gjkH7yWRL8UAydiOcHx2tVJyIGlJW05M6nze3Ag15dUsBKA9tOqTteGSrhbElfYE3c6oWJa5Xb/PqIYOe8GBCcdckU1uxidT9qzmHfDu4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5006c7c7.xn--btvx9d.k1207; olt=johnl@user.iecc.com; bh=9X9/podiYHjMImzj6lMDbsVL77DYVWbK6OuOFpips+g=; b=ZPmq/4NVfCk0Lg5lzfiESCcKX6+FsZnfT7QhTOAeYz2S/fMGS+XQEt3pVzeYdUruDjPaRdSJBTDofrgvUeo6vFAhW8TB72xTqPfs5XRXy9f1zTgog3ykwfcMs/4HyB87HKJjom5LutxLTIS/iFgbPHImtP5uYlAy6Dl1zWryhEU=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 18 Jul 2012 14:26:57 -0000
Message-ID: <20120718142657.26067.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <4483E6EE-7E4E-442C-9ADD-2E8B9D549B54@nominet.org.uk>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 14:26:32 -0000

>> Can we work from the assumption that authentication is through features
>offered by HTTP?
>
>Yes, please!

So long as that includes stuff like a cookie set by some earlier login
negotiations, I don't see any problem with that.

I presume it also includes the authentication schemes in RFC 2617, oauth
in rfc 5849, and client SSL certs.

What all of these have in common is that we don't have to say anything
about them other than to refer people to the existing definitions.

R's,
John

From peter@denic.de  Wed Jul 18 07:35:17 2012
Return-Path: <peter@denic.de>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7EE521F87A1 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 07:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RcOniUhWw1jT for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 07:35:17 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::3]) by ietfa.amsl.com (Postfix) with ESMTP id D2A0021F879D for <weirds@ietf.org>; Wed, 18 Jul 2012 07:35:16 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.17]) by office.denic.de with esmtp  id 1SrVMD-0003ps-Sr; Wed, 18 Jul 2012 16:36:05 +0200
Received: from localhost by x27.adm.denic.de with local  id 1SrVMD-0000E0-PC; Wed, 18 Jul 2012 16:36:05 +0200
Date: Wed, 18 Jul 2012 16:36:05 +0200
From: Peter Koch <pk@DENIC.DE>
To: weirds@ietf.org
Message-ID: <20120718143605.GY24669@x28.adm.denic.de>
References: <4483E6EE-7E4E-442C-9ADD-2E8B9D549B54@nominet.org.uk> <20120718142657.26067.qmail@joyce.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120718142657.26067.qmail@joyce.lan>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 14:35:18 -0000

On Wed, Jul 18, 2012 at 02:26:57PM +0000, John Levine wrote:
> >> Can we work from the assumption that authentication is through features
> >offered by HTTP?
> >
> >Yes, please!
> 
> So long as that includes stuff like a cookie set by some earlier login
> negotiations, I don't see any problem with that.

indeed.  While this is strictly about authorization rather than authentication,
in the context of single object vs. basket of objects there might be
scenarios where a, say, person object, should only be retrievable
as a followup to an inet or domain object, to avoid personal data hervesting.
Cookies might help there, even though they'd not necessarily
identify the requestor.

-Peter

From vesely@tana.it  Wed Jul 18 08:24:51 2012
Return-Path: <vesely@tana.it>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA5821F8691 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 08:24:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.622
X-Spam-Level: 
X-Spam-Status: No, score=-4.622 tagged_above=-999 required=5 tests=[AWL=0.097,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gpF2TiO7chdf for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 08:24:50 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id AC70C21F8762 for <weirds@ietf.org>; Wed, 18 Jul 2012 08:24:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1342625138; bh=gC9XKd1pJhQOBO8RNytk84xQtE0l7uqnby9ANClOwoo=; l=903; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=Ib4Rf174+rujTxVUSO4CNuKLxAuHmWiilaisOqv94MBNzDXRqvYHBqh64EL0q8BNy VEvq3klGLNmwEV7MAcXFL7mpYDNKtVIBCgoSLIq5shGfEGa3bFNV+VWnNaAQcv2Daw UQZCkkP/vbEkbKJN5+8X18HL2HI0ynVaaju3xInc=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Wed, 18 Jul 2012 17:25:38 +0200 id 00000000005DC039.000000005006D572.00004256
Message-ID: <5006D572.5080702@tana.it>
Date: Wed, 18 Jul 2012 17:25:38 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: weirds@ietf.org
References: <20120711203242.48919.qmail@joyce.lan> <9FC1FEF3-EE0D-4CF4-BA6E-DE2A12ACB092@arin.net> <alpine.BSF.2.00.1207111728450.47528@joyce.lan> <BB77C35A-CAC7-4E11-A4EF-CC8AFCEB438D@arin.net> <alpine.BSF.2.00.1207120959530.60846@joyce.lan> <E9EBF95B-56DB-4964-A00D-643DA069393E@arin.net>
In-Reply-To: <E9EBF95B-56DB-4964-A00D-643DA069393E@arin.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 15:24:51 -0000

On Tue 17/Jul/2012 15:10:07 +0200 Andy Newton wrote:
> On Jul 12, 2012, at 10:08 AM, John R Levine wrote:
> 
>>>> I suppose one could use a CNAME kludge of 
>>>> <tld>.wierdsservers.net or <1.2.3.4.5.6>.weirdsservers.net,
>>>> analogous to Rodney's whoisservers.net, that doesn't require
>>>> a lookup before the http query.
>>> 
>>> Interesting. Why not XXXX.weirds.arpa?
>> 
>> Uh, because I wasn't thinking far enough ahead?  That would
>> involve IANA, but in a pretty benign way.  They'd have to update
>> their processes to allow entities that have been delegated a TLD
>> or a top level IP range to register and update WEIRDS servers,
>> but it'd be no more work than maintaining the in-addr zone which
>> they do now.
> 
> I think this is workable and strikes the right balance for the
> needs of the clients vs. distributed bootstrapping.

+1, I'll hum for it if it goes in A.5.2

From andy@arin.net  Wed Jul 18 08:51:15 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A497921F8713 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 08:51:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level: 
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QzlfCqdsIlYG for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 08:51:14 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id CFD7121F86FA for <weirds@ietf.org>; Wed, 18 Jul 2012 08:51:14 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id DCDF3214998; Wed, 18 Jul 2012 11:52:04 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id 3E80A214999; Wed, 18 Jul 2012 11:52:03 -0400 (EDT)
Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 18 Jul 2012 11:51:51 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0298.004; Wed, 18 Jul 2012 11:52:03 -0400
From: Andy Newton <andy@arin.net>
To: John Levine <johnl@taugh.com>
Thread-Topic: [weirds] Authentication Methods
Thread-Index: AQHNYzSuspt33xZIm0e2t0ykhwl7c5cvAi8AgABdO4CAABfFAA==
Date: Wed, 18 Jul 2012 15:52:01 +0000
Message-ID: <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net>
References: <20120718142657.26067.qmail@joyce.lan>
In-Reply-To: <20120718142657.26067.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.1.56]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23CBFBA957CA654EA0747BCC3E299E22@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 15:51:15 -0000

On Jul 18, 2012, at 10:26 AM, John Levine wrote:

> So long as that includes stuff like a cookie set by some earlier login
> negotiations, I don't see any problem with that.
>=20
> I presume it also includes the authentication schemes in RFC 2617, oauth
> in rfc 5849, and client SSL certs.
>=20
> What all of these have in common is that we don't have to say anything
> about them other than to refer people to the existing definitions.

What are we saying here? That ALL weirds clients and servers must support c=
ooking passing, OAuth, client SSL, etc.. even though no policy may ever be =
passed by any operator or community that uses them?

-andy=

From johnl@taugh.com  Wed Jul 18 09:17:03 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECF1321F8795 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 09:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.592
X-Spam-Level: 
X-Spam-Status: No, score=-2.592 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bqxIzdBuIBB6 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 09:17:03 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id F2F3D21F87B3 for <weirds@ietf.org>; Wed, 18 Jul 2012 09:17:02 -0700 (PDT)
Received: (qmail 3988 invoked from network); 18 Jul 2012 16:17:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=f93.5006e1b1.k1207; bh=qWPkCtpkDSA06HoGpl883BCFLheU4djwbrbHXHlzuj0=; b=hHDO+HS/sLo74HMAg181LJOxManpA3ZTpoyzlPimZcYAowXCaJXjdeel6Ip/GKXTKliLG0eodKVJWNzwbPlHSmXsXp1uauDFS8ApUEzZOjxuIj/sD/NWUFIHVvvUXLc1bh7Air6OlImbQcKen0RPXAVD+hlkOoMeXv0l96VxGxY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=f93.5006e1b1.k1207; bh=qWPkCtpkDSA06HoGpl883BCFLheU4djwbrbHXHlzuj0=; b=bvcc21MA0uyDV4mhbW95PEfxMbXuLrLc3zr/uSYKPBIBGhvHyA5cVwrwNCXi8Ijjo1mJDZ7+dtjRipxpvQhljz4KQdF5GDDWpYkpPTc9t9yf1RCQLQC9smbB5vuJoeAicrnHEf7EkJTj/WzammBvhwUlf/7/47InF31Ui3wdBGE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 18 Jul 2012 16:17:30 -0000
Date: 18 Jul 2012 12:17:52 -0400
Message-ID: <alpine.BSF.2.00.1207181206150.53701@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Andy Newton" <andy@arin.net>
In-Reply-To: <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 16:17:04 -0000

>> What all of these have in common is that we don't have to say anything
>> about them other than to refer people to the existing definitions.
>
> What are we saying here? That ALL weirds clients and servers must 
> support cooking passing, OAuth, client SSL, etc.. even though no policy 
> may ever be passed by any operator or community that uses them?

Servers don't have to support any auth at all, if they're willing to give 
the same answer to everyone.  Clients have to support whatever auth is 
needed to persuade the server to give up the goods.

It would be fine with me to limit the set that servers can use, but I 
suspect you'll find consitutuencies for all of them.  OAuth is too 
complex, but it has the valuable ability to validate referrals, i.e., if 
you're authenticated to server A, and it refers you to server B, then B 
can consult A to find out what you're allowed to do without A giving B 
your credentials.

These are all widely implemented. Even the horrors of OAuth are buried in 
perl, PHP, and python libraries.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From andy@arin.net  Wed Jul 18 09:25:47 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 380EB11E80AA for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 09:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level: 
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WI6Eho3k9cA1 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 09:25:45 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 309D811E809B for <weirds@ietf.org>; Wed, 18 Jul 2012 09:25:45 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 95748214A44; Wed, 18 Jul 2012 12:26:35 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id 0737F214A3A; Wed, 18 Jul 2012 12:26:35 -0400 (EDT)
Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 18 Jul 2012 12:26:22 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0298.004; Wed, 18 Jul 2012 12:26:34 -0400
From: Andy Newton <andy@arin.net>
To: John R Levine <johnl@taugh.com>
Thread-Topic: [weirds] Authentication Methods
Thread-Index: AQHNYzSuspt33xZIm0e2t0ykhwl7c5cvAi8AgABdO4CAABfFAIAABzgAgAACbgA=
Date: Wed, 18 Jul 2012 16:26:33 +0000
Message-ID: <42F12CD9-55E3-47DE-8909-307FB3E9567D@arin.net>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <alpine.BSF.2.00.1207181206150.53701@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1207181206150.53701@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.1.56]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D2C8A1617AC5BD40B3E1DC116E0A692D@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 16:25:47 -0000

On Jul 18, 2012, at 12:17 PM, John R Levine wrote:

>>> What all of these have in common is that we don't have to say anything
>>> about them other than to refer people to the existing definitions.
>>=20
>> What are we saying here? That ALL weirds clients and servers must suppor=
t cooking passing, OAuth, client SSL, etc.. even though no policy may ever =
be passed by any operator or community that uses them?
>=20
> Servers don't have to support any auth at all, if they're willing to give=
 the same answer to everyone.  Clients have to support whatever auth is nee=
ded to persuade the server to give up the goods.

Let me ask this a different way. Will this working group produce RFCs that =
say OAuth, client SSL, etc.. is a MUST to implement? Keep in mind there are=
 people intending to write generic weirds clients and there is a project to=
 write a generic weirds server for the names registries.

-andy=

From johnl@taugh.com  Wed Jul 18 09:36:28 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD4AE11E8106 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 09:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level: 
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P4ZFwrZS3kjt for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 09:36:28 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id AFCC211E80ED for <weirds@ietf.org>; Wed, 18 Jul 2012 09:36:27 -0700 (PDT)
Received: (qmail 36595 invoked from network); 18 Jul 2012 16:37:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=8ef2.5006e63b.k1207; bh=vMtdF9/s0prFvuczxTOSftfgVyq14vV0mThRWcoA5qM=; b=gxbXfX3Mf2DgNOXaqNI2dy7U1HSYUe1Y7z1jMrX7x7YrBbBzdtJA8El/jNpTRVGnTugAJmDw5eERxA+jjrWQrpFTk5Ny7MxN/bwywiSktBSZItBGaMGK6axlNSmSvW7ktnDjvppLdUCtS5I+EwGLepP+VA9Srps/0BZ64sz1Lsc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=8ef2.5006e63b.k1207; bh=vMtdF9/s0prFvuczxTOSftfgVyq14vV0mThRWcoA5qM=; b=YSZ6szb5yphCzlZV53lHz5OY9yw/BIGBFhpDWz6JH4rYQY5jnm6RjrIqFOyLbEYmBsMk+tUNBe552kHi4BH3UJutrHdORObbQ4kkhHrKe02QctSTRL/BTVtE++KWRzpsdyvFycbyxdDeRK50oOpzVmxEI4NsaEvLO8O9m/KvZjA=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 18 Jul 2012 16:36:53 -0000
Date: 18 Jul 2012 12:37:15 -0400
Message-ID: <alpine.BSF.2.00.1207181236520.53701@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Andy Newton" <andy@arin.net>
In-Reply-To: <42F12CD9-55E3-47DE-8909-307FB3E9567D@arin.net>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <alpine.BSF.2.00.1207181206150.53701@joyce.lan> <42F12CD9-55E3-47DE-8909-307FB3E9567D@arin.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 16:36:29 -0000

> Let me ask this a different way. Will this working group produce RFCs that say OAuth, client SSL, etc.. is a MUST to implement? Keep in mind there are people intending to write generic weirds clients and there is a project to write a generic weirds server for the names registries.

Good question.  I suppose that as a strawman we can pick one or two and 
see who objects.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From ajs@anvilwalrusden.com  Wed Jul 18 09:43:52 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BE6D11E80D9 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 09:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.417
X-Spam-Level: 
X-Spam-Status: No, score=-1.417 tagged_above=-999 required=5 tests=[AWL=-0.577, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KVSOjOp8XvOc for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 09:43:51 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 4B1F311E80AA for <weirds@ietf.org>; Wed, 18 Jul 2012 09:43:51 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 585418A031 for <weirds@ietf.org>; Wed, 18 Jul 2012 16:44:41 +0000 (UTC)
Date: Wed, 18 Jul 2012 12:44:39 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: weirds@ietf.org
Message-ID: <20120718164439.GI340@mail.yitter.info>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <alpine.BSF.2.00.1207181206150.53701@joyce.lan> <42F12CD9-55E3-47DE-8909-307FB3E9567D@arin.net> <alpine.BSF.2.00.1207181236520.53701@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1207181236520.53701@joyce.lan>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 16:43:52 -0000

On Wed, Jul 18, 2012 at 12:37:15PM -0400, John R Levine wrote:
> 
> Good question.  I suppose that as a strawman we can pick one or two
> and see who objects.

Why isn't the right answer to say that they're all MAY and then see
what people actually implement?  I think being prescriptive here is a
waste of time.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From johnl@iecc.com  Wed Jul 18 15:03:13 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE3911E8157 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 15:03:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.142
X-Spam-Level: 
X-Spam-Status: No, score=-111.142 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SgzzOXWgbnJ4 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 15:03:12 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 3331A11E8087 for <weirds@ietf.org>; Wed, 18 Jul 2012 15:03:12 -0700 (PDT)
Received: (qmail 2274 invoked from network); 18 Jul 2012 22:04:02 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 18 Jul 2012 22:04:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=500732d2.xn--hew.k1207; i=johnl@user.iecc.com; bh=0QBJzsXl5fiOGqmldzYi0SvbAlBc22av/DMfkuFbpew=; b=tApti0Pv8F9QRYnsa5xv5rqeTy94ictZzNRZp7BvTiTscnqdqHM9XhJl4grQIKmHQ/NMXm3q4z0dUS9nhsNBvkHy7yICQOgb8TCk3BIa90m/EX3aANMAXlbcXRFlYlALblwjy2slza3+OGNf+1TptA/eHu4m4e/JFGkBIye56dQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=500732d2.xn--hew.k1207; olt=johnl@user.iecc.com; bh=0QBJzsXl5fiOGqmldzYi0SvbAlBc22av/DMfkuFbpew=; b=Pf/E6vTcRrdGSyk/UR95T9h7orO3CGiw6cseYNVlga332BnQOETIJxvFP2NZ5aPBqQuxOnSqaYH2i57pFVOLuh62VC7gKKVqM7n0448oFoo1ZdrcdApL+bdvflFFlUcbIoBo6FIZH0EmPvLjVSEiTLH9cc5U0goufjrea9tXfyQ=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 18 Jul 2012 22:03:40 -0000
Message-ID: <20120718220340.65326.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <20120718164439.GI340@mail.yitter.info>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 22:03:13 -0000

>> Good question.  I suppose that as a strawman we can pick one or two
>> and see who objects.
>
>Why isn't the right answer to say that they're all MAY and then see
>what people actually implement?  I think being prescriptive here is a
>waste of time.

That doesn't strike me as a very good way to get things to
interoperate.  You write a client and decide that nobody uses client
certs, I write a server that expects client certs.  Now what?

R's,
John

From avri@acm.org  Wed Jul 18 18:27:32 2012
Return-Path: <avri@acm.org>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A28EC21F850F for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 18:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.288
X-Spam-Level: 
X-Spam-Status: No, score=-106.288 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cyz3SdFqGug5 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 18:27:31 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id CB25B21F850D for <weirds@ietf.org>; Wed, 18 Jul 2012 18:27:31 -0700 (PDT)
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1]) by psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <avri@acm.org>) id 1SrfXS-000JBF-VE for weirds@ietf.org; Thu, 19 Jul 2012 01:28:23 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
From: Avri Doria <avri@acm.org>
In-Reply-To: <20120718164439.GI340@mail.yitter.info>
Date: Wed, 18 Jul 2012 21:28:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <817CDB07-EB97-4BB6-B73F-737866BC11EA@acm.org>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <alpine.BSF.2.00.1207181206150.53701@joyce.lan> <42F12CD9-55E3-47DE-8909-307FB3E9567D@arin.net> <alpine.BSF.2.00.1207181236520.53701@joyce.lan> <20120718164439.GI340@mail.yitter.info>
To: weirds@ietf.org
X-Mailer: Apple Mail (2.1278)
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 01:27:32 -0000

Hi,

I suggest a SHOULD.   =20

Not quite a MUST because there might be a set of good reasons for not =
doing OAuth, client SSL, etc.. that could be listed in the rfc, but that =
in the absence of a good reason for not doing so, yes one SHOULD.

avri

On 18 Jul 2012, at 12:44, Andrew Sullivan wrote:

> On Wed, Jul 18, 2012 at 12:37:15PM -0400, John R Levine wrote:
>>=20
>> Good question.  I suppose that as a strawman we can pick one or two
>> and see who objects.
>=20
> Why isn't the right answer to say that they're all MAY and then see
> what people actually implement?  I think being prescriptive here is a
> waste of time.
>=20
> Best,
>=20
> A
>=20
> --=20
> Andrew Sullivan
> ajs@anvilwalrusden.com
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds
>=20


From ajs@anvilwalrusden.com  Wed Jul 18 18:43:59 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0BCA21F8674 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 18:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.407
X-Spam-Level: 
X-Spam-Status: No, score=-1.407 tagged_above=-999 required=5 tests=[AWL=-0.567, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CAeX5SYNOruw for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 18:43:59 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 7AA7921F8621 for <weirds@ietf.org>; Wed, 18 Jul 2012 18:43:59 -0700 (PDT)
Received: from crankycanuck.ca (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id E01AC8A031 for <weirds@ietf.org>; Thu, 19 Jul 2012 01:44:50 +0000 (UTC)
Date: Wed, 18 Jul 2012 21:44:49 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: weirds@ietf.org
Message-ID: <20120719014449.GC1323@crankycanuck.ca>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <alpine.BSF.2.00.1207181206150.53701@joyce.lan> <42F12CD9-55E3-47DE-8909-307FB3E9567D@arin.net> <alpine.BSF.2.00.1207181236520.53701@joyce.lan> <20120718164439.GI340@mail.yitter.info> <817CDB07-EB97-4BB6-B73F-737866BC11EA@acm.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <817CDB07-EB97-4BB6-B73F-737866BC11EA@acm.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 01:44:00 -0000

On Wed, Jul 18, 2012 at 09:28:21PM -0400, Avri Doria wrote:
> 
> Not quite a MUST because there might be a set of good reasons for not doing OAuth, client SSL, etc.. that could be listed in the rfc, but that in the absence of a good reason for not doing so, yes one SHOULD.
> 

That doesn't address Andy's (quite reasonable) observation that many
clients won't want to implement all that.  What interoperability
problem are we trying to solve with SHOULD?  MAY permits people to do
this, makes it clear what the methods would be, and then lets both
ends work out what they mutually support.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From zhoulinlin@cnnic.cn  Wed Jul 18 18:46:29 2012
Return-Path: <zhoulinlin@cnnic.cn>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9388721F8678 for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 18:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VT1T-7UrlcQI for <weirds@ietfa.amsl.com>; Wed, 18 Jul 2012 18:46:28 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id 5CE0421F8674 for <weirds@ietf.org>; Wed, 18 Jul 2012 18:46:27 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn
Received: from unknown127.0.0.1 (HELO lenovo95e6383c) (127.0.0.1) by 127.0.0.1 with SMTP; Thu, 19 Jul 2012 09:47:16 +0800
From: "Linlin Zhou" <zhoulinlin@cnnic.cn>
To: "'Andy Newton'" <andy@arin.net>, "'John Levine'" <johnl@taugh.com>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net>
In-Reply-To: <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net>
Date: Thu, 19 Jul 2012 09:47:14 +0800
Message-ID: <002701cd6550$6c1a3ba0$444eb2e0$@cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHNYzSuspt33xZIm0e2t0ykhwl7c5cvAi8AgABdO4CAABfFAIAAXrLQ
Content-Language: zh-cn
Cc: weirds@ietf.org
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 01:46:29 -0000

> -----Original Message-----
> From: weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On Behalf
Of
> Andy Newton
> Sent: Wednesday, July 18, 2012 11:52 PM
> To: John Levine
> Cc: <weirds@ietf.org>
> Subject: Re: [weirds] Authentication Methods
> 
> 
> On Jul 18, 2012, at 10:26 AM, John Levine wrote:
> 
> > So long as that includes stuff like a cookie set by some earlier login
> > negotiations, I don't see any problem with that.
> >
> > I presume it also includes the authentication schemes in RFC 2617,
> > oauth in rfc 5849, and client SSL certs.
> >
> > What all of these have in common is that we don't have to say anything
> > about them other than to refer people to the existing definitions.
> 
> What are we saying here? That ALL weirds clients and servers must support
> cooking passing, OAuth, client SSL, etc.. even though no policy may ever
be
> passed by any operator or community that uses them?
> 

I think we should define which authentication scenarios are included in the
scope of this working group. Then select authentication mechanisms that are
suitable for corresponding scenarios. 
Some may not supported or implemented, but reasons and explanations are
listed.

> -andy
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds


From Ray.Bellis@nominet.org.uk  Thu Jul 19 01:05:31 2012
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCD9721F86C9 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 01:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.58
X-Spam-Level: 
X-Spam-Status: No, score=-10.58 tagged_above=-999 required=5 tests=[AWL=0.018,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WkfqvGA1EoX7 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 01:05:30 -0700 (PDT)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id 1C3DC21F86B6 for <weirds@ietf.org>; Thu, 19 Jul 2012 01:05:29 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Received:From:To:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:Content-Type: MIME-Version; b=bcikWT2X6GKaiz4FK/nx5OI6csq8UFsEjC/WHkgMmcZhkUBsKarSA/6Y tM2639QmZaKr+C19m8SVEHHHT18HcKxdZlu6H2a+vKCZraKVixsErLlD8 5dAIvQZJKv6dXh6;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1342685183; x=1374221183; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[weirds]=20Authentication=20Methods |Date:=20Thu,=2019=20Jul=202012=2008:06:20=20+0000 |Message-ID:=20<B5F40D70-914D-4696-A6F6-A6C02E63F82B@nomi net.org.uk>|To:=20Web=20Extensible=20Internet=20Registrat ion=20Data=20Service=20Working=20Group=0D=0A=09<weirds@ie tf.org>|MIME-Version:=201.0|In-Reply-To:=20<002701cd6550$ 6c1a3ba0$444eb2e0$@cn>|References:=20<20120718142657.2606 7.qmail@joyce.lan>=0D=0A=20<8152AEFC-9398-47E7-9DEE-A662F 0E64E28@arin.net>=0D=0A=20<002701cd6550$6c1a3ba0$444eb2e0 $@cn>; bh=RfHHXI5cxSWNVlXGU8lWbuDSYuTzQKRA7nrOoIZTyOI=; b=kCVgdcoHdXyqGtdwCx5e01iY6nlE/Mc5A9ihUhTu23IhzeEKkWTr2hf4 jWRqPIJ/HM2p+MO3kfVcuk4qHSvz1btw6tq6rR69xubDaaQeZMX/kFaZG R9UehOkkr7YC2wN;
X-IronPort-AV: E=Sophos;i="4.77,615,1336345200"; d="scan'208,217";a="34227615"
Received: from wds-exc1.okna.nominet.org.uk ([213.248.197.144]) by mx4.nominet.org.uk with ESMTP; 19 Jul 2012 09:06:21 +0100
Received: from WDS-EXC2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4]) by wds-exc1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f%19]) with mapi; Thu, 19 Jul 2012 09:06:20 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Thread-Topic: [weirds] Authentication Methods
Thread-Index: AQHNYzSVaT5sUZ9lAki+OrM4ADgQbpcurl0AgABdO4CAABfFgIAApk0AgABp6wA=
Date: Thu, 19 Jul 2012 08:06:20 +0000
Message-ID: <B5F40D70-914D-4696-A6F6-A6C02E63F82B@nominet.org.uk>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <002701cd6550$6c1a3ba0$444eb2e0$@cn>
In-Reply-To: <002701cd6550$6c1a3ba0$444eb2e0$@cn>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_B5F40D70914D4696A6F6A6C02E63F82Bnominetorguk_"
MIME-Version: 1.0
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 08:05:31 -0000

--_000_B5F40D70914D4696A6F6A6C02E63F82Bnominetorguk_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


On 19 Jul 2012, at 02:47, Linlin Zhou wrote:

I think we should define which authentication scenarios are included in the
scope of this working group. Then select authentication mechanisms that are
suitable for corresponding scenarios.
Some may not supported or implemented, but reasons and explanations are
listed.


The trouble with (HTTP authentication) standards is that there's _so_ many =
of them to choose from;-)

Ray


--_000_B5F40D70914D4696A6F6A6C02E63F82Bnominetorguk_
Content-Type: text/html; charset="us-ascii"
Content-ID: <1b749824-0433-4427-aa8d-e58e79cc9eb2>
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -we=
bkit-line-break: after-white-space; "><br><div><div>On 19 Jul 2012, at 02:4=
7, Linlin Zhou wrote:</div><blockquote type=3D"cite"><div><font class=3D"Ap=
ple-style-span" color=3D"#000000"><br></font>I think we should define which=
 authentication scenarios are included in the<br>scope of this working grou=
p. Then select authentication mechanisms that are<br>suitable for correspon=
ding scenarios. <br>Some may not supported or implemented, but reasons and =
explanations are<br>listed.<br></div></blockquote></div><br><div><br></div>=
<div>The trouble with (HTTP authentication) standards is that there's _so_ =
many of them to choose from;-)</div><div><br></div><div>Ray</div><div><br><=
/div></body></html>=

--_000_B5F40D70914D4696A6F6A6C02E63F82Bnominetorguk_--

From chris@ausregistry.com.au  Thu Jul 19 05:35:41 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDBA821F872A for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 05:35:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UdkHBQQEaFBk for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 05:35:41 -0700 (PDT)
Received: from mx01.ausregistry.net.au (mx01.ausregistry.net.au [202.65.15.41]) by ietfa.amsl.com (Postfix) with ESMTP id 154BA21F8720 for <weirds@ietf.org>; Thu, 19 Jul 2012 05:35:38 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron01.off08.stkildard.vic.ausregistry.com.au with ESMTP; 19 Jul 2012 22:36:30 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Thu, 19 Jul 2012 22:36:17 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: Alessandro Vesely <vesely@tana.it>, "weirds@ietf.org" <weirds@ietf.org>
Date: Thu, 19 Jul 2012 22:36:26 +1000
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: Ac1lqxbe7Ce0RMmkQoGhAe2GyGOOJw==
Message-ID: <CC2E3BAC.33F74%chris@ausregistry.com.au>
In-Reply-To: <5006D572.5080702@tana.it>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 12:35:42 -0000

Why not a DNS Resource Record that lives in the tld zone file? No need to
have IANA involved then and TLD manager can update as required.

dig -t WEIRDS tad returns URL of weirds service

Or we could potentially use existing records like SRV or NAPTR ?

Thanks

Chris

On 19/07/12 1:25 AM, "Alessandro Vesely" <vesely@tana.it> wrote:

>On Tue 17/Jul/2012 15:10:07 +0200 Andy Newton wrote:
>> On Jul 12, 2012, at 10:08 AM, John R Levine wrote:
>>=20
>>>>> I suppose one could use a CNAME kludge of
>>>>> <tld>.wierdsservers.net or <1.2.3.4.5.6>.weirdsservers.net,
>>>>> analogous to Rodney's whoisservers.net, that doesn't require
>>>>> a lookup before the http query.
>>>>=20
>>>> Interesting. Why not XXXX.weirds.arpa?
>>>=20
>>> Uh, because I wasn't thinking far enough ahead?  That would
>>> involve IANA, but in a pretty benign way.  They'd have to update
>>> their processes to allow entities that have been delegated a TLD
>>> or a top level IP range to register and update WEIRDS servers,
>>> but it'd be no more work than maintaining the in-addr zone which
>>> they do now.
>>=20
>> I think this is workable and strikes the right balance for the
>> needs of the clients vs. distributed bootstrapping.
>
>+1, I'll hum for it if it goes in A.5.2
>_______________________________________________
>weirds mailing list
>weirds@ietf.org
>https://www.ietf.org/mailman/listinfo/weirds


From carlosm3011@gmail.com  Thu Jul 19 07:46:45 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEDAE21F86FD for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 07:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DEAzrLBl876u for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 07:46:44 -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 84BA021F86F3 for <weirds@ietf.org>; Thu, 19 Jul 2012 07:46:44 -0700 (PDT)
Received: by yenq13 with SMTP id q13so3143567yen.31 for <weirds@ietf.org>; Thu, 19 Jul 2012 07:47:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=/hGbQUnpo9N3XaBjQuIrUS/yasgGuQWZH9T01lljvBw=; b=BG3iO9O4hLHw7+cs5TzM2KXw9Ob8+o/HaQnNt9iPykZjZs2KWUC4s0/sCNShfQvv3w Pu0FwJkDty61dVY1hG7KQThEByyh6YIxRTq0OMBDoglsKNX598wP80/z93yk2DkULt3w fYshDLodFfwBR5eV3Jeet2uZ41vUTsnfF33VPkY8PGZV0R63lHKgCJeBdkeDxNQXi1Qq KNaXoPGcVrzwH4hohlHXBUKRUkJiN3msNMM89MKeQ8LlwNxkpQQYeBXu+Ht4GR8H9yjd imH1ghnuZxzP0cqNWhWqprS8kCBQh5z2J9aNPsFXVcSsxCTjGMiQ38JDw/IW60r0djM6 Nrdw==
Received: by 10.236.117.97 with SMTP id i61mr1697944yhh.73.1342709257657; Thu, 19 Jul 2012 07:47:37 -0700 (PDT)
Received: from europa.local ([190.115.129.45]) by mx.google.com with ESMTPS id q10sm1967552anm.16.2012.07.19.07.47.34 (version=SSLv3 cipher=OTHER); Thu, 19 Jul 2012 07:47:35 -0700 (PDT)
Message-ID: <50081E0D.7060309@gmail.com>
Date: Thu, 19 Jul 2012 10:47:41 -0400
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Chris Wright <chris@ausregistry.com.au>
References: <CC2E3BAC.33F74%chris@ausregistry.com.au>
In-Reply-To: <CC2E3BAC.33F74%chris@ausregistry.com.au>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "weirds@ietf.org" <weirds@ietf.org>, Alessandro Vesely <vesely@tana.it>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 14:46:46 -0000

I thought about that, but decided against it on the grounds that it will
increase zone size by a sizeable factor, which might not be an issue for
some operators but definitely will hurt others like .com

thoughts?

regards

Carlos

On 7/19/12 8:36 AM, Chris Wright wrote:
> Why not a DNS Resource Record that lives in the tld zone file? No need to
> have IANA involved then and TLD manager can update as required.
>
> dig -t WEIRDS tad returns URL of weirds service
>
> Or we could potentially use existing records like SRV or NAPTR ?
>
> Thanks
>
> Chris
>
> On 19/07/12 1:25 AM, "Alessandro Vesely" <vesely@tana.it> wrote:
>
>> On Tue 17/Jul/2012 15:10:07 +0200 Andy Newton wrote:
>>> On Jul 12, 2012, at 10:08 AM, John R Levine wrote:
>>>
>>>>>> I suppose one could use a CNAME kludge of
>>>>>> <tld>.wierdsservers.net or <1.2.3.4.5.6>.weirdsservers.net,
>>>>>> analogous to Rodney's whoisservers.net, that doesn't require
>>>>>> a lookup before the http query.
>>>>> Interesting. Why not XXXX.weirds.arpa?
>>>> Uh, because I wasn't thinking far enough ahead?  That would
>>>> involve IANA, but in a pretty benign way.  They'd have to update
>>>> their processes to allow entities that have been delegated a TLD
>>>> or a top level IP range to register and update WEIRDS servers,
>>>> but it'd be no more work than maintaining the in-addr zone which
>>>> they do now.
>>> I think this is workable and strikes the right balance for the
>>> needs of the clients vs. distributed bootstrapping.
>> +1, I'll hum for it if it goes in A.5.2
>> _______________________________________________
>> weirds mailing list
>> weirds@ietf.org
>> https://www.ietf.org/mailman/listinfo/weirds
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds



From hsalgado@nic.cl  Thu Jul 19 07:58:18 2012
Return-Path: <hsalgado@nic.cl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5676421F8620 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 07:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WeZbfbLG4UHM for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 07:58:17 -0700 (PDT)
Received: from mail.nic.cl (mail.nic.cl [IPv6:2001:1398:1::6008]) by ietfa.amsl.com (Postfix) with ESMTP id A3D2E21F85DB for <weirds@ietf.org>; Thu, 19 Jul 2012 07:58:16 -0700 (PDT)
Received: from mail.nic.cl (localhost.localdomain [127.0.0.1]) by mail.nic.cl (Postfix) with ESMTP id 70F24248003 for <weirds@ietf.org>; Thu, 19 Jul 2012 10:59:08 -0400 (CLT)
Received: from vulcano.intra.nic.cl (unknown [IPv6:2001:1398:4:1:172:30:10:58]) by mail.nic.cl (Postfix) with ESMTP id 594B0248001 for <weirds@ietf.org>; Thu, 19 Jul 2012 10:59:08 -0400 (CLT)
Message-ID: <500820BC.3060500@nic.cl>
Date: Thu, 19 Jul 2012 10:59:08 -0400
From: Hugo Salgado <hsalgado@nic.cl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: weirds@ietf.org
References: <CC2E3BAC.33F74%chris@ausregistry.com.au> <50081E0D.7060309@gmail.com>
In-Reply-To: <50081E0D.7060309@gmail.com>
X-Enigmail-Version: 1.4.3
OpenPGP: id=B525FA6E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP on Thu Jul 19 10:59:08 2012 -0400 (CLT)
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 14:58:18 -0000

On 07/19/2012 10:47 AM, Carlos Martinez-Cagnazzo wrote:
> I thought about that, but decided against it on the grounds that it will
> increase zone size by a sizeable factor, which might not be an issue for
> some operators but definitely will hurt others like .com
> 
> thoughts?

The .com zone will only get 1 extra WEIRDS/SRV/NAPTR RR (plus some
RRSIGs and NSEC*).

This mechanism is only to bootstrap the first level. After that, .com
will redirect to weirds servers below its hierarchy using the standard
weirds-restful http redirect, when its needed.

Hugo


> 
> regards
> 
> Carlos
> 
> On 7/19/12 8:36 AM, Chris Wright wrote:
>> Why not a DNS Resource Record that lives in the tld zone file? No need to
>> have IANA involved then and TLD manager can update as required.
>>
>> dig -t WEIRDS tad returns URL of weirds service
>>
>> Or we could potentially use existing records like SRV or NAPTR ?
>>
>> Thanks
>>
>> Chris
>>
>> On 19/07/12 1:25 AM, "Alessandro Vesely" <vesely@tana.it> wrote:
>>
>>> On Tue 17/Jul/2012 15:10:07 +0200 Andy Newton wrote:
>>>> On Jul 12, 2012, at 10:08 AM, John R Levine wrote:
>>>>
>>>>>>> I suppose one could use a CNAME kludge of
>>>>>>> <tld>.wierdsservers.net or <1.2.3.4.5.6>.weirdsservers.net,
>>>>>>> analogous to Rodney's whoisservers.net, that doesn't require
>>>>>>> a lookup before the http query.
>>>>>> Interesting. Why not XXXX.weirds.arpa?
>>>>> Uh, because I wasn't thinking far enough ahead?  That would
>>>>> involve IANA, but in a pretty benign way.  They'd have to update
>>>>> their processes to allow entities that have been delegated a TLD
>>>>> or a top level IP range to register and update WEIRDS servers,
>>>>> but it'd be no more work than maintaining the in-addr zone which
>>>>> they do now.
>>>> I think this is workable and strikes the right balance for the
>>>> needs of the clients vs. distributed bootstrapping.
>>> +1, I'll hum for it if it goes in A.5.2
>>> _______________________________________________
>>> weirds mailing list
>>> weirds@ietf.org
>>> https://www.ietf.org/mailman/listinfo/weirds
>> _______________________________________________
>> weirds mailing list
>> weirds@ietf.org
>> https://www.ietf.org/mailman/listinfo/weirds
> 
> 
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds
> 


From andy@arin.net  Thu Jul 19 08:19:45 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7312921F8736 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 08:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZtrtIj3hJUtY for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 08:19:44 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id A667F21F8713 for <weirds@ietf.org>; Thu, 19 Jul 2012 08:19:44 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id 50F0B165363; Thu, 19 Jul 2012 11:20:37 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp1.arin.net (Postfix) with ESMTP id EB423164FC5; Thu, 19 Jul 2012 11:20:36 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Thu, 19 Jul 2012 11:20:03 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Thu, 19 Jul 2012 11:20:18 -0400
From: Andy Newton <andy@arin.net>
To: Ray Bellis <Ray.Bellis@nominet.org.uk>
Thread-Topic: [weirds] Authentication Methods
Thread-Index: AQHNYzSuspt33xZIm0e2t0ykhwl7c5cvAi8AgABdO4CAABfFAIAAXrLQgACxhgCAAHk+gA==
Date: Thu, 19 Jul 2012 15:20:17 +0000
Message-ID: <F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <002701cd6550$6c1a3ba0$444eb2e0$@cn> <B5F40D70-914D-4696-A6F6-A6C02E63F82B@nominet.org.uk>
In-Reply-To: <B5F40D70-914D-4696-A6F6-A6C02E63F82B@nominet.org.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.1.56]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E15F7239DA0F224089E652AB2CD6BA5B@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 15:19:45 -0000

On Jul 19, 2012, at 4:06 AM, Ray Bellis wrote:

>=20
> On 19 Jul 2012, at 02:47, Linlin Zhou wrote:
>>=20
>> I think we should define which authentication scenarios are included in =
the
>> scope of this working group. Then select authentication mechanisms that =
are
>> suitable for corresponding scenarios.=20
>> Some may not supported or implemented, but reasons and explanations are
>> listed.
>=20
>=20
> The trouble with (HTTP authentication) standards is that there's _so_ man=
y of them to choose from;-)

We need to be careful here. If we define so many MUSTs (or even MAYs), ther=
e will be push back that this is a heavyweight specification and some will =
use that to avoid implementation.

I think the question ought to be asked, does any Whois operator today have =
differentiated access, either via port 43 or other Whois-type services, or =
does any Whois operator have plans in the works to implement some type of d=
ifferentiated access. Getting answers to such questions would limit the sco=
pe.

-andy=

From andy@arin.net  Thu Jul 19 08:21:41 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4299321F87B7 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 08:21:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8q6eX+Bwwmz for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 08:21:40 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 9194921F8736 for <weirds@ietf.org>; Thu, 19 Jul 2012 08:21:40 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 9B182214A4A; Thu, 19 Jul 2012 11:22:31 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id B56F8214A51; Thu, 19 Jul 2012 11:22:30 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Thu, 19 Jul 2012 11:22:15 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Thu, 19 Jul 2012 11:22:30 -0400
From: Andy Newton <andy@arin.net>
To: Chris Wright <chris@ausregistry.com.au>
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: AQHNX65QpJoDeMyMZUyzRwJlYVqyVZck9d2AgAD9kICAB8s+AIABuDEAgAFjDwCAAC5jAA==
Date: Thu, 19 Jul 2012 15:22:29 +0000
Message-ID: <AEFA87F9-347C-4C5D-ADE5-B1DE427DE2AD@arin.net>
References: <CC2E3BAC.33F74%chris@ausregistry.com.au>
In-Reply-To: <CC2E3BAC.33F74%chris@ausregistry.com.au>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.1.56]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D24961CB179B244397429638EC0188DD@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "weirds@ietf.org" <weirds@ietf.org>, Alessandro Vesely <vesely@tana.it>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 15:21:41 -0000

On Jul 19, 2012, at 8:36 AM, Chris Wright wrote:

> Why not a DNS Resource Record that lives in the tld zone file? No need to
> have IANA involved then and TLD manager can update as required.
>=20
> dig -t WEIRDS tad returns URL of weirds service
>=20
> Or we could potentially use existing records like SRV or NAPTR ?

As previously discussed in this thread, many client implementations operate=
 in an environment that does not have access to this type of information.

-andy=

From johnl@iecc.com  Thu Jul 19 08:54:49 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8318721F871A for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 08:54:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.143
X-Spam-Level: 
X-Spam-Status: No, score=-111.143 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7O4ThWAdooZ for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 08:54:48 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 68F3C21F86FA for <weirds@ietf.org>; Thu, 19 Jul 2012 08:54:48 -0700 (PDT)
Received: (qmail 64510 invoked from network); 19 Jul 2012 15:55:40 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 19 Jul 2012 15:55:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50082dfc.xn--i8sz2z.k1207; i=johnl@user.iecc.com; bh=1XXjLyqpYvGIlKMUNJHlXnyynevHciBA0piF4c8NJFU=; b=m1A6iKfSaiKVhcy08ISmd98rQoUeYkM7WcCstLCGUhaqOM6ME0hfrqkgXdJYhNgTkQCtCP4exouUGty0pxNpV/+xvQX5QZS3UJ7QBXPkTG+eERioO4CZ2AU0KYIWydYZx9TQmro2MnNzrYvc98YEbQzSklcwvmHCw0lZeEweDRE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50082dfc.xn--i8sz2z.k1207; olt=johnl@user.iecc.com; bh=1XXjLyqpYvGIlKMUNJHlXnyynevHciBA0piF4c8NJFU=; b=Fuub7YJ/BF8j3Xbc4R8CK9+UD0KeUKaOQzxm+pLk1DYfB12sjGFbXw9Wm/IZCCrc/U7lS1GP30QHBAJdETHsGu5LHq288tJHkrUQ68jjidLSvC8+1y1Vqu0CqBRqJg5uk4NnB8A9OP2AVNm3HcfcQj5Td78J66PhfkFSQP8Ybck=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 19 Jul 2012 15:55:18 -0000
Message-ID: <20120719155518.53016.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 15:54:49 -0000

>I think the question ought to be asked, does any Whois operator today
>have differentiated access, either via port 43 or other Whois-type
>services, ...

On the numbers side, you can probably answer that as well as anyone.

On the names side, I can report from experience that every WHOIS
server does rate limiting, and there is usually some secret way to get
the limit for your IP raised if you know who to ask.

When you hit the limit, different providers do different things.  Some
redact the data (Godaddy notably).  Some return a message saying
you're over your limit.  Some just don't accept connections, or accept
and don't respond.

So, yes, on the names side at least, differentiated access is universal.

R's,
John

From ajs@anvilwalrusden.com  Thu Jul 19 08:55:21 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E99B421F8794 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 08:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.36
X-Spam-Level: 
X-Spam-Status: No, score=-1.36 tagged_above=-999 required=5 tests=[AWL=-0.520,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AjvfX3+L355q for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 08:55:21 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 63CE521F878A for <weirds@ietf.org>; Thu, 19 Jul 2012 08:55:21 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 71DCB8A031 for <weirds@ietf.org>; Thu, 19 Jul 2012 15:56:14 +0000 (UTC)
Date: Thu, 19 Jul 2012 11:56:12 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: weirds@ietf.org
Message-ID: <20120719155612.GG2231@mail.yitter.info>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <002701cd6550$6c1a3ba0$444eb2e0$@cn> <B5F40D70-914D-4696-A6F6-A6C02E63F82B@nominet.org.uk> <F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 15:55:22 -0000

On Thu, Jul 19, 2012 at 03:20:17PM +0000, Andy Newton wrote:
> 
> I think the question ought to be asked, does any Whois operator
> today have differentiated access, either via port 43 or other
> Whois-type services

Yes.  Almost all the name registries have a special non-rate-limited
address you can talk to.  Most of them require the IP address from
which you are coming to get to it, and it's available to you at their
discretion.  This is normally offered to registrars, who frequently
need the full non-rate-limited access in order to comply with various
requirements of ICANN agreements, or as part of their business logic.

Moreover, a significant justification for this work was differential
access.  If we're not going to offer it, we're not in keeping with our
charter.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From warren@kumari.net  Thu Jul 19 10:59:58 2012
Return-Path: <warren@kumari.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E47E21F8611 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 10:59:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rh2SKyqp0XFK for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 10:59:56 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id EED1621F85E0 for <weirds@ietf.org>; Thu, 19 Jul 2012 10:59:55 -0700 (PDT)
Received: from [172.26.33.237] (unknown [72.14.228.1]) by vimes.kumari.net (Postfix) with ESMTPSA id 230E11B40115; Thu, 19 Jul 2012 14:00:49 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <20120719014449.GC1323@crankycanuck.ca>
Date: Thu, 19 Jul 2012 14:00:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <21C8E709-5D9F-42D1-9666-5E6A46AA8770@kumari.net>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <alpine.BSF.2.00.1207181206150.53701@joyce.lan> <42F12CD9-55E3-47DE-8909-307FB3E9567D@arin.net> <alpine.BSF.2.00.1207181236520.53701@joyce.lan> <20120718164439.GI340@mail.yitter.info> <817CDB07-EB97-4BB6-B73F-737866BC11EA@acm.org> <20120719014449.GC1323@crankycanuck.ca>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1278)
Cc: weirds@ietf.org
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 17:59:58 -0000

On Jul 18, 2012, at 9:44 PM, Andrew Sullivan wrote:

> On Wed, Jul 18, 2012 at 09:28:21PM -0400, Avri Doria wrote:
>>=20
>> Not quite a MUST because there might be a set of good reasons for not =
doing OAuth, client SSL, etc.. that could be listed in the rfc, but that =
in the absence of a good reason for not doing so, yes one SHOULD.
>>=20
>=20
> That doesn't address Andy's (quite reasonable) observation that many
> clients won't want to implement all that. =20

And that is perfectly fine -- my shiny web-browser implements digest =
auth, TLS and the ability to see dancing hamsters ( =
http://www.webhamster.com/ ) not because of any MUST or SHOULD, but =
because that is what the users are (apparently) asking for.
If I connect to a web server that doesn't require these things I am free =
to use a much simpler client (AKA "telnet to port 80"!).

Both ways have their pros and cons, but if I need to connect to a system =
that needs "advanced" features, I go pull out an "advanced" client. As =
long as the specification is clear on how the base functionality works, =
how the optional features work , and which are which, client developers =
can support what they need to...


> What interoperability
> problem are we trying to solve with SHOULD?  MAY permits people to do
> this, makes it clear what the methods would be, and then lets both
> ends work out what they mutually support.

Well, sort of -- clients that don't implement $foo obviously won't be =
able to get content that requires $foo. Unless both sides announce their =
capabilities[0] it may be tricky (short of probing / testing) to know =
what all capabilities are supported.=20

W
[0]: I'm not suggesting this!

>=20
> Best,
>=20
> A
>=20
> --=20
> Andrew Sullivan
> ajs@anvilwalrusden.com
>=20
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds
>=20

--=20
No man is an island, But if you take a bunch of dead guys and tie them =
together, they make a pretty good raft.
                --Anon.



From peter@denic.de  Thu Jul 19 11:04:51 2012
Return-Path: <peter@denic.de>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 241C721F864F for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 11:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rurjDLeFPdtA for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 11:04:50 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6571821F85E0 for <weirds@ietf.org>; Thu, 19 Jul 2012 11:04:50 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.17]) by office.denic.de with esmtp  id 1Srv6c-0004a2-Fj; Thu, 19 Jul 2012 20:05:42 +0200
Received: from localhost by x27.adm.denic.de with local  id 1Srv6c-0008KI-BX; Thu, 19 Jul 2012 20:05:42 +0200
Date: Thu, 19 Jul 2012 20:05:42 +0200
From: Peter Koch <pk@DENIC.DE>
To: weirds@ietf.org
Message-ID: <20120719180542.GF24669@x28.adm.denic.de>
References: <D3D8582E-BE04-4BCF-88D9-B73A3813003E@arin.net> <CC245AB3.12E9B%james.mitchell@ausregistry.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CC245AB3.12E9B%james.mitchell@ausregistry.com.au>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 18:04:51 -0000

On Thu, Jul 12, 2012 at 01:06:45PM +1000, James Mitchell wrote:

> Using .au whois as an example, only registrant and technical contact name
> and email are available via whois-like interfaces (port-43 and web),
> however email is withheld to port-43 clients. Administrative and billing
> contacts are never returned, nor is any specific data relating to the
> registrant or tech contacts (phone, fax, address etc).
> 
> There a distinction between data that is never available and data has been
> withheld from a specific interface. DENIC also has similar behaviours IIRC.

true. The admin contact is unavailable over port 43 and some contact details
may only be visible as instructed by the registrant.  And there is overall
rate limiting.

In those cases where an object or an attribute is withheld I do not
think it would be either proper protocol design to add a magic string
(as opposed to an extra alphabetical token) or within the purpose
of the limited visibility to disclose the presence of the data.

-Peter

From chris@ausregistry.com.au  Thu Jul 19 17:01:15 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FA2311E80A6 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 17:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5osjAa2z32HX for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 17:01:14 -0700 (PDT)
Received: from mx02.ausregistry.net.au (mx02.ausregistry.net.au [202.65.15.42]) by ietfa.amsl.com (Postfix) with ESMTP id 2FD3011E80A0 for <weirds@ietf.org>; Thu, 19 Jul 2012 17:01:11 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron02.off08.stkildard.vic.ausregistry.com.au with ESMTP; 20 Jul 2012 10:02:04 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Fri, 20 Jul 2012 10:01:51 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: "carlos@lacnic.net" <carlos@lacnic.net>
Date: Fri, 20 Jul 2012 10:02:01 +1000
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: Ac1lvWweFPZWGnm9TMu/IWsw5ZLupAATVkRA
Message-ID: <8CEF048B9EC83748B1517DC64EA130FB729CD7209B@off-win2003-01.ausregistrygroup.local>
References: <CC2E3BAC.33F74%chris@ausregistry.com.au> <50081E0D.7060309@gmail.com>
In-Reply-To: <50081E0D.7060309@gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "weirds@ietf.org" <weirds@ietf.org>, Alessandro Vesely <vesely@tana.it>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 00:01:15 -0000

SSdtIG5vdCBzdXJlIHlvdSB1bmRlcnN0b29kIHRoZSBpZGVhLCANCg0KVGhlcmUgd291bGQgb25s
eSBiZSBvbmUgcmVjb3JkIGluIHRoZSB6b25lIGZpbGUgKG9yIG1heWJlIGEgZmV3IGZvciByZWR1
bmRhbmN5IHJlYXNvbnMpLCBpdOKAmXMgYSBib290c3RyYXAgcG9pbnRlciBub3QgYSBwb2ludGVy
IGZvciBldmVyeSBkb21haW4uDQoNClNvIEkgZG9u4oCZdCB0aGluayB0aGVyZSB3b3VsZCBiZSBh
bnkgaXNzdWUuDQoNClRoYW5rcw0KDQpDaHJpcw0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQpGcm9tOiBDYXJsb3MgTWFydGluZXotQ2FnbmF6em8gW21haWx0bzpjYXJsb3NtMzAxMUBn
bWFpbC5jb21dIA0KU2VudDogRnJpZGF5LCAyMCBKdWx5IDIwMTIgMTI6NDggQU0NClRvOiBDaHJp
cyBXcmlnaHQNCkNjOiBBbGVzc2FuZHJvIFZlc2VseTsgd2VpcmRzQGlldGYub3JnDQpTdWJqZWN0
OiBSZTogW3dlaXJkc10gdGhlIGJvb3RzdHJhcCBwcm9ibGVtLCBSZWRpcmVjdGlvbiBpbiB0aGUg
UkVTVGZ1bCBXSE9JUyB3b3JsZA0KDQpJIHRob3VnaHQgYWJvdXQgdGhhdCwgYnV0IGRlY2lkZWQg
YWdhaW5zdCBpdCBvbiB0aGUgZ3JvdW5kcyB0aGF0IGl0IHdpbGwgaW5jcmVhc2Ugem9uZSBzaXpl
IGJ5IGEgc2l6ZWFibGUgZmFjdG9yLCB3aGljaCBtaWdodCBub3QgYmUgYW4gaXNzdWUgZm9yIHNv
bWUgb3BlcmF0b3JzIGJ1dCBkZWZpbml0ZWx5IHdpbGwgaHVydCBvdGhlcnMgbGlrZSAuY29tDQoN
CnRob3VnaHRzPw0KDQpyZWdhcmRzDQoNCkNhcmxvcw0KDQpPbiA3LzE5LzEyIDg6MzYgQU0sIENo
cmlzIFdyaWdodCB3cm90ZToNCj4gV2h5IG5vdCBhIEROUyBSZXNvdXJjZSBSZWNvcmQgdGhhdCBs
aXZlcyBpbiB0aGUgdGxkIHpvbmUgZmlsZT8gTm8gbmVlZCANCj4gdG8gaGF2ZSBJQU5BIGludm9s
dmVkIHRoZW4gYW5kIFRMRCBtYW5hZ2VyIGNhbiB1cGRhdGUgYXMgcmVxdWlyZWQuDQo+DQo+IGRp
ZyAtdCBXRUlSRFMgdGFkIHJldHVybnMgVVJMIG9mIHdlaXJkcyBzZXJ2aWNlDQo+DQo+IE9yIHdl
IGNvdWxkIHBvdGVudGlhbGx5IHVzZSBleGlzdGluZyByZWNvcmRzIGxpa2UgU1JWIG9yIE5BUFRS
ID8NCj4NCj4gVGhhbmtzDQo+DQo+IENocmlzDQo+DQo+IE9uIDE5LzA3LzEyIDE6MjUgQU0sICJB
bGVzc2FuZHJvIFZlc2VseSIgPHZlc2VseUB0YW5hLml0PiB3cm90ZToNCj4NCj4+IE9uIFR1ZSAx
Ny9KdWwvMjAxMiAxNToxMDowNyArMDIwMCBBbmR5IE5ld3RvbiB3cm90ZToNCj4+PiBPbiBKdWwg
MTIsIDIwMTIsIGF0IDEwOjA4IEFNLCBKb2huIFIgTGV2aW5lIHdyb3RlOg0KPj4+DQo+Pj4+Pj4g
SSBzdXBwb3NlIG9uZSBjb3VsZCB1c2UgYSBDTkFNRSBrbHVkZ2Ugb2YgPHRsZD4ud2llcmRzc2Vy
dmVycy5uZXQgDQo+Pj4+Pj4gb3IgPDEuMi4zLjQuNS42Pi53ZWlyZHNzZXJ2ZXJzLm5ldCwgYW5h
bG9nb3VzIHRvIFJvZG5leSdzIA0KPj4+Pj4+IHdob2lzc2VydmVycy5uZXQsIHRoYXQgZG9lc24n
dCByZXF1aXJlIGEgbG9va3VwIGJlZm9yZSB0aGUgaHR0cCANCj4+Pj4+PiBxdWVyeS4NCj4+Pj4+
IEludGVyZXN0aW5nLiBXaHkgbm90IFhYWFgud2VpcmRzLmFycGE/DQo+Pj4+IFVoLCBiZWNhdXNl
IEkgd2Fzbid0IHRoaW5raW5nIGZhciBlbm91Z2ggYWhlYWQ/ICBUaGF0IHdvdWxkIGludm9sdmUg
DQo+Pj4+IElBTkEsIGJ1dCBpbiBhIHByZXR0eSBiZW5pZ24gd2F5LiAgVGhleSdkIGhhdmUgdG8g
dXBkYXRlIHRoZWlyIA0KPj4+PiBwcm9jZXNzZXMgdG8gYWxsb3cgZW50aXRpZXMgdGhhdCBoYXZl
IGJlZW4gZGVsZWdhdGVkIGEgVExEIG9yIGEgdG9wIA0KPj4+PiBsZXZlbCBJUCByYW5nZSB0byBy
ZWdpc3RlciBhbmQgdXBkYXRlIFdFSVJEUyBzZXJ2ZXJzLCBidXQgaXQnZCBiZSANCj4+Pj4gbm8g
bW9yZSB3b3JrIHRoYW4gbWFpbnRhaW5pbmcgdGhlIGluLWFkZHIgem9uZSB3aGljaCB0aGV5IGRv
IG5vdy4NCj4+PiBJIHRoaW5rIHRoaXMgaXMgd29ya2FibGUgYW5kIHN0cmlrZXMgdGhlIHJpZ2h0
IGJhbGFuY2UgZm9yIHRoZSBuZWVkcyANCj4+PiBvZiB0aGUgY2xpZW50cyB2cy4gZGlzdHJpYnV0
ZWQgYm9vdHN0cmFwcGluZy4NCj4+ICsxLCBJJ2xsIGh1bSBmb3IgaXQgaWYgaXQgZ29lcyBpbiBB
LjUuMg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cj4+IHdlaXJkcyBtYWlsaW5nIGxpc3QNCj4+IHdlaXJkc0BpZXRmLm9yZw0KPj4gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby93ZWlyZHMNCj4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gd2VpcmRzIG1haWxpbmcgbGlzdA0KPiB3
ZWlyZHNAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby93
ZWlyZHMNCg0KDQo=

From chris@ausregistry.com.au  Thu Jul 19 17:02:57 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F23C11E80A6 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 17:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOvO2lfOm6Mo for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 17:02:57 -0700 (PDT)
Received: from mx02.ausregistry.net.au (mx02.ausregistry.net.au [202.65.15.42]) by ietfa.amsl.com (Postfix) with ESMTP id AE4D211E80A0 for <weirds@ietf.org>; Thu, 19 Jul 2012 17:02:56 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron02.off08.stkildard.vic.ausregistry.com.au with ESMTP; 20 Jul 2012 10:03:50 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Fri, 20 Jul 2012 10:03:37 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: Andy Newton <andy@arin.net>
Date: Fri, 20 Jul 2012 10:03:47 +1000
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: AQHNX65QpJoDeMyMZUyzRwJlYVqyVZck9d2AgAD9kICAB8s+AIABuDEAgAFjDwCAAC5jAIAATiKw
Message-ID: <8CEF048B9EC83748B1517DC64EA130FB729CD7209C@off-win2003-01.ausregistrygroup.local>
References: <CC2E3BAC.33F74%chris@ausregistry.com.au> <AEFA87F9-347C-4C5D-ADE5-B1DE427DE2AD@arin.net>
In-Reply-To: <AEFA87F9-347C-4C5D-ADE5-B1DE427DE2AD@arin.net>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "weirds@ietf.org" <weirds@ietf.org>, Alessandro Vesely <vesely@tana.it>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 00:02:57 -0000

SW0gc29ycnkgQW5keSwgSSBkb27igJl0IHVuZGVyc3RhbmQgeW91ciBwb2ludC4uLg0KDQpBcmUg
eW91IHNheWluZyB0aGF0IGNsaWVudHMgd2lsbCBvcGVyYXRlIGluIGFuIGVudmlyb25tZW50IHdo
ZXJlIHRoZXkgY2FuIG1ha2UgYSBIVFRQIHJlcXVlc3QgYnV0IGNhbid0IGRvIEROUyByZXNvbHV0
aW9uPyBUaGF0IG1ha2VzIGFic29sdXRlbHkgbm8gc2Vuc2UgdG8gbWUuDQoNCkJlc2lkZSB0aGUg
YWx0ZXJuYXRpdmUgYXBwcm9hY2ggYmVpbmcgZGlzY3Vzc2VkIGlzIHRvIGhhdmUgJ3JlY29yZHMn
IGluIFhYWFgud2VpcmRzLmFycGEuIElmIHRoZSBjbGllbnQgY2FuIGxvb2t1cCBETlMgcmVjb3Jk
cyBpbiB0aGF0IHpvbmUsIHdoeSBjYW50IHRoZXkgbG9vayB0aGVtIHVwIGluIHRoZSBUTEQgem9u
ZT8NCg0KQ2FuIHlvdSBleHBhbmQgb24geW91ciBpc3N1ZSBhIGxpdHRsZSBtb3JlIHNvIHRoYXQg
SSB1bmRlcnN0YW5kIGl0Lg0KDQpUaGFua3MNCg0KYy4NCg0KDQotLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KRnJvbTogQW5keSBOZXd0b24gW21haWx0bzphbmR5QGFyaW4ubmV0XSANClNlbnQ6
IEZyaWRheSwgMjAgSnVseSAyMDEyIDE6MjIgQU0NClRvOiBDaHJpcyBXcmlnaHQNCkNjOiBBbGVz
c2FuZHJvIFZlc2VseTsgd2VpcmRzQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW3dlaXJkc10gdGhl
IGJvb3RzdHJhcCBwcm9ibGVtLCBSZWRpcmVjdGlvbiBpbiB0aGUgUkVTVGZ1bCBXSE9JUyB3b3Js
ZA0KDQoNCk9uIEp1bCAxOSwgMjAxMiwgYXQgODozNiBBTSwgQ2hyaXMgV3JpZ2h0IHdyb3RlOg0K
DQo+IFdoeSBub3QgYSBETlMgUmVzb3VyY2UgUmVjb3JkIHRoYXQgbGl2ZXMgaW4gdGhlIHRsZCB6
b25lIGZpbGU/IE5vIG5lZWQgDQo+IHRvIGhhdmUgSUFOQSBpbnZvbHZlZCB0aGVuIGFuZCBUTEQg
bWFuYWdlciBjYW4gdXBkYXRlIGFzIHJlcXVpcmVkLg0KPiANCj4gZGlnIC10IFdFSVJEUyB0YWQg
cmV0dXJucyBVUkwgb2Ygd2VpcmRzIHNlcnZpY2UNCj4gDQo+IE9yIHdlIGNvdWxkIHBvdGVudGlh
bGx5IHVzZSBleGlzdGluZyByZWNvcmRzIGxpa2UgU1JWIG9yIE5BUFRSID8NCg0KQXMgcHJldmlv
dXNseSBkaXNjdXNzZWQgaW4gdGhpcyB0aHJlYWQsIG1hbnkgY2xpZW50IGltcGxlbWVudGF0aW9u
cyBvcGVyYXRlIGluIGFuIGVudmlyb25tZW50IHRoYXQgZG9lcyBub3QgaGF2ZSBhY2Nlc3MgdG8g
dGhpcyB0eXBlIG9mIGluZm9ybWF0aW9uLg0KDQotYW5keQ0K

From johnl@iecc.com  Thu Jul 19 18:10:21 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3578811E80CE for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 18:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.131
X-Spam-Level: 
X-Spam-Status: No, score=-111.131 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sUaXaMSlcLFO for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 18:10:15 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 89AA811E80A6 for <weirds@ietf.org>; Thu, 19 Jul 2012 18:10:15 -0700 (PDT)
Received: (qmail 67528 invoked from network); 20 Jul 2012 01:11:09 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Jul 2012 01:11:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5008b02d.xn--9vv.k1207; i=johnl@user.iecc.com; bh=nsWENIScRfuqf05o1ZIiVUn26SNDrBw82YAd5jhUbuw=; b=PWwMZkQwAC1quNY3/gBzrIQ+dKmF6ge7+82HC4RfwaKRoRMGPfGxPvPFvOVEmthZ44opwukb3Bix6LcjtXyK5hQaA4exiSFae7dwtkOOsohEI/Zap6WD6bcfrs8WZ+x/3gzl2dEma2eoMuMRELy8tVoFJOnN80jR0Pxjdpq2UIw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5008b02d.xn--9vv.k1207; olt=johnl@user.iecc.com; bh=nsWENIScRfuqf05o1ZIiVUn26SNDrBw82YAd5jhUbuw=; b=kX8ixpFKs14PUP9mKak/st/eANXO/wEVkl5XFIPS9ejI59eqPlq2pOD8KtpswnH/GjwpgSDtzsWZbiD0dyt+u76P+ycN8Us1nQPzHIpZ6XVr3pZ3AJr3b2voQXDwVby1Vg7aIQLhdiosfp7kU0arQpevdBhw3QrUW4aYZtVR1Rg=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 20 Jul 2012 01:10:46 -0000
Message-ID: <20120720011046.96838.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <8CEF048B9EC83748B1517DC64EA130FB729CD7209B@off-win2003-01.ausregistrygroup.local>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 01:10:21 -0000

>I'm not sure you understood the idea,
>
>There would only be one record in the zone file

Um, IP addresses don't have zone files.

R's,
John

From chris@ausregistry.com.au  Thu Jul 19 18:59:33 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE40021F85A0 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 18:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.695
X-Spam-Level: 
X-Spam-Status: No, score=0.695 tagged_above=-999 required=5 tests=[AWL=-2.591,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_64=0.6, NORMAL_HTTP_TO_IP=0.001, SARE_SPOOF_COM2COM=2.536, SPOOF_COM2OTH=2.044]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id noOivi8VPETT for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 18:59:30 -0700 (PDT)
Received: from mx02.ausregistry.net.au (mx02.ausregistry.net.au [202.65.15.42]) by ietfa.amsl.com (Postfix) with ESMTP id B573021F84DC for <weirds@ietf.org>; Thu, 19 Jul 2012 18:59:29 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron02.off08.stkildard.vic.ausregistry.com.au with ESMTP; 20 Jul 2012 12:00:22 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Fri, 20 Jul 2012 12:00:09 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: John Levine <johnl@taugh.com>, "weirds@ietf.org" <weirds@ietf.org>
Date: Fri, 20 Jul 2012 12:00:19 +1000
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: Ac1mFIoVxrxvL/ZMTyWUTd8kMKTxQwAAJWgg
Message-ID: <8CEF048B9EC83748B1517DC64EA130FB729CD72111@off-win2003-01.ausregistrygroup.local>
References: <8CEF048B9EC83748B1517DC64EA130FB729CD7209B@off-win2003-01.ausregistrygroup.local> <20120720011046.96838.qmail@joyce.lan>
In-Reply-To: <20120720011046.96838.qmail@joyce.lan>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 01:59:33 -0000

VGhleSBkbyBpZiB5b3UgdHVybiB0aGVtIGludG8gdGhlaXIgcmV2ZXJzZSBETlMgZm9ybS4gSXQg
d29ya3MgZmluZS4NCg0KVGhlIG9ubHkgdGhpbmcgdG8gY29uc2lkZXIgaXMgZG8gd2Ugd2FudCB0
byBkbyB0b3AgZG93biBvciBib3R0b20gdXAgc2VhcmNoaW5nLi4NCg0KRm9yIGV4YW1wbGUgaW4g
LmF1IHdlIGhhdmUgcmVnaXN0cmF0aW9ucyBhdCB0aGUgdGhpcmQgbGV2ZWwgZm9vLmNvbS5hdSBh
bmQgZXZlbiA0dGggbGV2ZWwgZm9vLnZpYy5nb3YuYXUNCg0KSWYgeW91IGRpZCBpdCB0b3AgZG93
biB5b3Ugd291bGQgZ2V0IHRoZSB3ZWlyZHMgVVJMIGZyb20gdGhlIHRsZCBETlMgYW5kIHRoZW4g
YmUgcmVkaXJlY3RlZCBieSBIVFRQIGRvd24gdGhlIGNoYWluLg0KDQpJZiB5b3UgZGlkIGl0IGJv
dHRvbSB1cCB5b3Ugd291bGQgY2hvcCBvZmYgb25lIGxhYmVsIGZyb20gdGhlIGxlZnQgYXQgYSB0
aW1lLCB1bnRpbCB5b3UgZm91bmQgdGhlIHpvbmUgZmlsZSB3aXRoIHRoZSB3ZWlyZHMgcmVzb3Vy
Y2UgcmVjb3JkICh3aGljaGV2ZXIgb25lIHRoYXQgaXMpIGluIGl0IGFuZCB0aGVuIGhhdmUgdGhl
IFVSTCB0byBkbyB0aGUgcXVlcnkuDQoNCkknbSBub3Qgc3VyZSB0aGF0IGVpdGhlciBvZiB0aG9z
ZSBhcmUgZmF2b3VyYWJsZSBzbyBJIG9mZmVyIGFub3RoZXIgc29sdXRpb24gdGhhdCBidWlsZHMg
b24gdGhlIGV4aXN0aW5nIG9uZS4NCg0KV2hhdCBpZiB0aGUgYm9vdHN0cmFwIGFsZ29yaXRobSB3
ZW50IHNvbWV0aGluZyBsaWtlIHRoaXM6DQoNCklmIElQIGFkZHJlc3MgdGhlbiB0dXJuIGludG8g
cmV2ZXJzZSByZXNvbHZlIEROUyBzdHJpbmcgZWxzZSB0aGUgZG9tYWluIG5hbWUgaXMgdGhlIERO
UyBzdHJpbmcNCkFwcGVuZCBhIGtub3duIHN0cmluZyB0byB0aGUgRE5TIHN0cmluZyAoZWcuICd3
ZWlyZHMuYXJwYScpYW5kIGZvcm0gdGhlICdsb29rdXAgc3RyaW5nJw0KTG9va3VwIHRoZSBDTkFN
RSwgTkFQVFIsIFNSViBvciB3aGljaGV2ZXIgcmVzb3VyY2UgcmVjb3JkIHVzaW5nIHRoZSAnbG9v
a3VwIHN0cmluZycgYXMgdGhlIGRvbWFpbiBuYW1lIHRvIGxvb2t1cA0KVGhlIEROUyB3aWxsIHJl
dHVybiBlaXRoZXIgdGhlIFVSTCBvciBhIENOQU1FIHRvIHRoZSBzZXJ2ZXIgKHdoaWNoZXZlciB3
YXkgd2Ugd2FudCBpdCB0byB3b3JrKQ0KVGhlIHF1ZXJ5IHByb2NlZWRzDQoNCk5vdyBhdCBmaXJz
dCBnbGFuY2UgdGhpcyBtYXkgc2VlbSBsaWtlIHlvdSBuZWVkIHRvIGZpbGwgdGhlIHdlaXJkcy5h
cnBhIHpvbmUgd2l0aCBtYW55IHJlY29yZHMsIGJ1dCBub3QgaWYgeW91IGNvbnNpZGVyIHVzaW5n
IHdpbGRjYXJkcy4NCg0KU28gaWYgdGhlIGNvbSBUTEQgb25seSBhbGxvd3MgcmVnaXN0cmF0aW9u
cyBhdCB0aGUgMm5kIGxldmVsLCB0aGV5IGNvdWxkIGFzayB0byBoYXZlDQogICouY29tIE5BUFRS
IDxVUkw+DQpJbiB0aGUgd2VpcmRzLmFycGEgem9uZSBmaWxlLg0KRm9yIGF1IHdlIENPVUxEIHB1
dCB0aGVzZSByZWNvcmRzIGluDQogICAqLmF1IE5BUFRSIDxVUkw+DQogICAqLmNvbS5hdSBOQVBU
UiA8VVJMPg0KICAgKi5uZXQuYXUgIE5BUFRSIDxVUkw+DQpPciB3ZSBDT1VMRCBvbmx5IHB1dCB0
aGUgYXUgcmVjb3JkIGluIGFuZCBhbGxvdyB0aGUgYXUgV2hvSXMgdG8gZG8gSFRUUCByZWRpcmVj
dHMgdG8gY2hpbGRyZW4NCkkgYmVsaWV2ZSB0aGlzIGFwcHJvYWNoIGNvdWxkIGJlIHVzZWQgZm9y
IElQIGFkZHJlc3NlcyBXaG9JcyB0b28uDQoNClNvIGlmIEkgd2FzIGZhY2VkIHdpdGggYm9vdHN0
cmFwcGluZyBhIHJlcXVlc3QgZm9yIA0KDQpleGFtcGxlLmNvbS5hdQ0KSSB3b3VsZCBsb29rIHVw
IHRoZSB3ZWlyZHMgcmVjb3JkIGZvciBleGFtcGxlLmNvbS5hdS53ZWlyZHMuYXJwYQ0KQW5kIHRo
ZSBETlMgd291bGQgbWF0Y2ggYXBwcm9wcmlhdGVseSBiYXNlZCBvbiB3aGF0IHdhcyBjb25maWd1
cmVkLCBhbmQgdGhlbiB0aGUgaHR0cHMgc2VydmljZSBjb3VsZCByZWRpcmVjdCBpZiAvYXMgcmVx
dWlyZWQuIEl0IGlzIGEgdmVyeSBmbGV4aWFibGUgc29sdXRpb24uDQoNCklmIEkgd2FzIGZhY2Vk
IHdpdGggYm9vdHN0cmFwcGluZyBhIHJlcXVlc3QgZm9yIDIwMy4xOC41Ni4xMQ0KSSB3b3VsZCBs
b29rIHVwIHRoZSB3ZWlyZHMgcmVjb3JkIGZvciAxMS41Ni4xOC4yMDMuaW4tYWRkci5hcnBhLndl
aXJkcy5hcnBhDQpBbmQgc28gZm9ydGguLg0KDQpXaGF0IGRvIHlvdSBndXlzIHRoaW5rPw0KDQpU
aGFua3MNCg0KQ2hyaXMNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSm9o
biBMZXZpbmUgW21haWx0bzpqb2hubEB0YXVnaC5jb21dIA0KU2VudDogRnJpZGF5LCAyMCBKdWx5
IDIwMTIgMTE6MTEgQU0NClRvOiB3ZWlyZHNAaWV0Zi5vcmcNCkNjOiBDaHJpcyBXcmlnaHQNClN1
YmplY3Q6IFJlOiBbd2VpcmRzXSB0aGUgYm9vdHN0cmFwIHByb2JsZW0sIFJlZGlyZWN0aW9uIGlu
IHRoZSBSRVNUZnVsIFdIT0lTIHdvcmxkDQoNCj5JJ20gbm90IHN1cmUgeW91IHVuZGVyc3Rvb2Qg
dGhlIGlkZWEsDQo+DQo+VGhlcmUgd291bGQgb25seSBiZSBvbmUgcmVjb3JkIGluIHRoZSB6b25l
IGZpbGUNCg0KVW0sIElQIGFkZHJlc3NlcyBkb24ndCBoYXZlIHpvbmUgZmlsZXMuDQoNClIncywN
CkpvaG4NCg==

From chris@ausregistry.com.au  Thu Jul 19 19:02:33 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A29221F85A0 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 19:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.343
X-Spam-Level: *
X-Spam-Status: No, score=1.343 tagged_above=-999 required=5 tests=[AWL=-1.943,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_64=0.6, NORMAL_HTTP_TO_IP=0.001, SARE_SPOOF_COM2COM=2.536, SPOOF_COM2OTH=2.044]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YPcpB-KWvCtm for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 19:02:29 -0700 (PDT)
Received: from mx02.ausregistry.net.au (mx02.ausregistry.net.au [202.65.15.42]) by ietfa.amsl.com (Postfix) with ESMTP id 60CDC11E80C7 for <weirds@ietf.org>; Thu, 19 Jul 2012 19:02:29 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron02.off08.stkildard.vic.ausregistry.com.au with ESMTP; 20 Jul 2012 12:03:23 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Fri, 20 Jul 2012 12:03:10 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: Chris Wright <chris@ausregistry.com.au>
Date: Fri, 20 Jul 2012 12:04:03 +1000
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: Ac1mG8/JkSPgJ/b2T5+BgXYzTFgjhw==
Message-ID: <C416A6E6-215E-4A43-A70C-C43A74F561A8@ausregistry.com.au>
References: <8CEF048B9EC83748B1517DC64EA130FB729CD7209B@off-win2003-01.ausregistrygroup.local> <20120720011046.96838.qmail@joyce.lan> <8CEF048B9EC83748B1517DC64EA130FB729CD72111@off-win2003-01.ausregistrygroup.local>
In-Reply-To: <8CEF048B9EC83748B1517DC64EA130FB729CD72111@off-win2003-01.ausregistrygroup.local>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John Levine <johnl@taugh.com>, "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 02:02:33 -0000

FYI the 'they do if you turn them into their reverse DNS form' was in reply=
 to the IP addresses don't have zone files comment.

Thanks

c.

On 20/07/2012, at 12:00, "Chris Wright" <chris@ausregistry.com.au> wrote:

> They do if you turn them into their reverse DNS form. It works fine.
>=20
> The only thing to consider is do we want to do top down or bottom up sear=
ching..
>=20
> For example in .au we have registrations at the third level foo.com.au an=
d even 4th level foo.vic.gov.au
>=20
> If you did it top down you would get the weirds URL from the tld DNS and =
then be redirected by HTTP down the chain.
>=20
> If you did it bottom up you would chop off one label from the left at a t=
ime, until you found the zone file with the weirds resource record (whichev=
er one that is) in it and then have the URL to do the query.
>=20
> I'm not sure that either of those are favourable so I offer another solut=
ion that builds on the existing one.
>=20
> What if the bootstrap algorithm went something like this:
>=20
> If IP address then turn into reverse resolve DNS string else the domain n=
ame is the DNS string
> Append a known string to the DNS string (eg. 'weirds.arpa')and form the '=
lookup string'
> Lookup the CNAME, NAPTR, SRV or whichever resource record using the 'look=
up string' as the domain name to lookup
> The DNS will return either the URL or a CNAME to the server (whichever wa=
y we want it to work)
> The query proceeds
>=20
> Now at first glance this may seem like you need to fill the weirds.arpa z=
one with many records, but not if you consider using wildcards.
>=20
> So if the com TLD only allows registrations at the 2nd level, they could =
ask to have
>  *.com NAPTR <URL>
> In the weirds.arpa zone file.
> For au we COULD put these records in
>   *.au NAPTR <URL>
>   *.com.au NAPTR <URL>
>   *.net.au  NAPTR <URL>
> Or we COULD only put the au record in and allow the au WhoIs to do HTTP r=
edirects to children
> I believe this approach could be used for IP addresses WhoIs too.
>=20
> So if I was faced with bootstrapping a request for=20
>=20
> example.com.au
> I would look up the weirds record for example.com.au.weirds.arpa
> And the DNS would match appropriately based on what was configured, and t=
hen the https service could redirect if /as required. It is a very flexiabl=
e solution.
>=20
> If I was faced with bootstrapping a request for 203.18.56.11
> I would look up the weirds record for 11.56.18.203.in-addr.arpa.weirds.ar=
pa
> And so forth..
>=20
> What do you guys think?
>=20
> Thanks
>=20
> Chris
>=20
>=20
> -----Original Message-----
> From: John Levine [mailto:johnl@taugh.com]=20
> Sent: Friday, 20 July 2012 11:11 AM
> To: weirds@ietf.org
> Cc: Chris Wright
> Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful W=
HOIS world
>=20
>> I'm not sure you understood the idea,
>>=20
>> There would only be one record in the zone file
>=20
> Um, IP addresses don't have zone files.
>=20
> R's,
> John
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds

From johnl@taugh.com  Thu Jul 19 20:36:06 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8921D11E80EA for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 20:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level: 
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8jJQsw37b5T9 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 20:36:05 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 6CF6B11E8072 for <weirds@ietf.org>; Thu, 19 Jul 2012 20:36:04 -0700 (PDT)
Received: (qmail 88241 invoked from network); 20 Jul 2012 03:36:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=158b0.5008d25a.k1207; bh=TLmdzbovbgfwNVZrhxxuWaggL8mzZ5hcumjRBD8V6gU=; b=dy9K7tb8Ldj922dS1KWYo+9isVOj1UBvp5xAlqTI6XEdqaaIlpWOzGgcPktW6BZ0qT7dokZY2MU7ZRQRjzK8zo4Z2C+zMAZ+Jg9+mup1tNio9C3ChtLkNaoHO2G6tMOVnQK9jouIfuhvunwr339DyWDq+FSsFf6rCImIouL82cw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=158b0.5008d25a.k1207; bh=TLmdzbovbgfwNVZrhxxuWaggL8mzZ5hcumjRBD8V6gU=; b=D22sP61Iq/Ke2MYBgnGCXBZOpnZbxRjRscM8b9yrHcUpDCTIcJc1ZIJ4eYckAIK8smEHBLco879sQeDPqMQ7A/y9W/uAN049R0VElmLAfhr+tankh+EdXSc8m21xo6mE80TGGPK4gjB+vHiocRF3Vl8OfFKabwcjLd6x8LQOfy0=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 20 Jul 2012 03:36:36 -0000
Date: 19 Jul 2012 23:36:57 -0400
Message-ID: <alpine.BSF.2.00.1207192308240.19001@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Chris Wright" <chris@ausregistry.com.au>
In-Reply-To: <8CEF048B9EC83748B1517DC64EA130FB729CD72111@off-win2003-01.ausregistrygroup.local>
References: <8CEF048B9EC83748B1517DC64EA130FB729CD7209B@off-win2003-01.ausregistrygroup.local> <20120720011046.96838.qmail@joyce.lan> <8CEF048B9EC83748B1517DC64EA130FB729CD72111@off-win2003-01.ausregistrygroup.local>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 03:36:06 -0000

> They do if you turn them into their reverse DNS form. It works fine.

Two points.  One is that rDNS zones have never had anything in them other 
than NS, CNAME, and PTR.  You'd hope that nothing strange would happen if 
you put in other stuff, but I wouldn't want to try it without some 
significant testing first.

I thought SRV was a swell idea until Andy reported that a lot of the 
queries to the existing WEIRDS prototype are coming from Javascript 
programs that are running in web browsers.  There is no way to do a DNS 
lookup from Javascript other than the implicit A and AAAA lookup that 
happens when it fetches a URL.  That makes any DNS hack beyond one that 
gives predictable CNAMEs to servers a complete non-starter.

> If IP address then turn into reverse resolve DNS string else the domain 
> name is the DNS string. Append a known string to the DNS string (eg. 
> 'weirds.arpa') and form the 'lookup string' [ and then do something with 
> wildcards ]

> What do you guys think?

Having written my share of DNS client and server software, it's vastly 
overcomplicated.

For names, a CNAME pointing to the server at <tld>.weirds.arpa would work. 
If your ccTLD is subdivided at the second or third level, it's your job to 
set up appropriate referral servers.

For IPv4, <nnn>.weirds.arpa, where NNN is the high octet of the address 
will also work.  IANA has already assigned each /8 to an RIR for WHOIS 
management, nothing new there.

IPv6 is a little tricker, since IANA's allocations were originally /23 and 
have since grown to /12.  If we do x.x.x.x.x.x.weirds.arpa, where the x's 
are the first six hex digits of the address, a zone with an entry for all 
of the allocated space would have about 21K entries.  That's a factor of 
10 bigger than the TLD list (assuming ICANN allocates most of the 1500 
TLDs applied for) but still not ridiculous.  I realize you could shrink 
the zone by using reversing the digits and using wildcards, but then it'd 
refer queries for addresses that aren't allocated to servers that aren't 
expecting them, which doesn't strike me as a good idea.

R's,
John

From chris@ausregistry.com.au  Thu Jul 19 21:16:04 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5264421F85C0 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 21:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.859
X-Spam-Level: 
X-Spam-Status: No, score=-0.859 tagged_above=-999 required=5 tests=[AWL=1.036,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DZ377Nrr8nTu for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 21:16:03 -0700 (PDT)
Received: from mx02.ausregistry.net.au (mx02.ausregistry.net.au [202.65.15.42]) by ietfa.amsl.com (Postfix) with ESMTP id 2863621F85B8 for <weirds@ietf.org>; Thu, 19 Jul 2012 21:16:02 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron02.off08.stkildard.vic.ausregistry.com.au with ESMTP; 20 Jul 2012 14:16:56 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Fri, 20 Jul 2012 14:16:43 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: John R Levine <johnl@taugh.com>
Date: Fri, 20 Jul 2012 14:16:53 +1000
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: Ac1mLnfsc1F99qsTQAK557wqmM9GfQ==
Message-ID: <CC2F1666.34047%chris@ausregistry.com.au>
In-Reply-To: <alpine.BSF.2.00.1207192308240.19001@joyce.lan>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 04:16:04 -0000

Thanks John,

On 20/07/12 1:36 PM, "John R Levine" <johnl@taugh.com> wrote:

>> They do if you turn them into their reverse DNS form. It works fine.
>
>Two points.  One is that rDNS zones have never had anything in them other
>than NS, CNAME, and PTR.  You'd hope that nothing strange would happen if
>you put in other stuff, but I wouldn't want to try it without some
>significant testing first.
>
>I thought SRV was a swell idea until Andy reported that a lot of the
>queries to the existing WEIRDS prototype are coming from Javascript
>programs that are running in web browsers.  There is no way to do a DNS
>lookup from Javascript other than the implicit A and AAAA lookup that
>happens when it fetches a URL.  That makes any DNS hack beyond one that
>gives predictable CNAMEs to servers a complete non-starter.
>

Im not sure that we should dismiss a workable solution simply because one
technology doesn't support it, and it is solvable in that technology, it
would simply need to call to a web service first that 'figured out' what
the correct URL is to send the lookup to. (I.e. some service side script).
That=B9s no better or worse of a 'workaround' than the one that was
suggested for the CNAME  / Virtual hosting issue (which seems to be just
use more IPs). If you really want to solve the Javascript problem you just
need a central http starting point to redirect people the right way, but
that=B9s ugly (and can you say single point of failure) and I dunno, to me
it just doesn't make sense to design an internet protocol around a
restriction in one piece of technology, which could change in the future
anyway.

I digress though as I still prefer the wildcard solution which would still
allow CNAMES to be used anyway.

As for the 2nd level registrations vs 3rd level registrations, I am fine
having the TLD server redirect further down, was just pointing out that if
we weren't fine with that, the DNS method could be used too. (In fact they
are not mutely exclusive so why not leave it as a choice).

Thanks

Chris


From johnl@iecc.com  Thu Jul 19 21:37:09 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 807F821F85D0 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 21:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.132
X-Spam-Level: 
X-Spam-Status: No, score=-111.132 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cuCHNasqmGp5 for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 21:37:05 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 231E821F85D3 for <weirds@ietf.org>; Thu, 19 Jul 2012 21:37:04 -0700 (PDT)
Received: (qmail 96542 invoked from network); 20 Jul 2012 04:37:59 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Jul 2012 04:37:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5008e0a7.xn--i8sz2z.k1207; i=johnl@user.iecc.com; bh=NuQQeAbYBTjge4Ob1Ss16FjboYhHeGjL4iFdVvcEPZ0=; b=n3FXSq+oaN5vR/va5y0zWlu7DUH77FYlLgo3MSwpLcVTuIYkLyAcAGKwIGqun1aXue5zGVhCnQ8wY7KbOAdtSAO3QZSZJTkXMOpjE4BjZCEUBpN0z7Gq4WTpV/CgTnOdbgjpJC8gwYxxzrCMN4qNVUILbTlrZl0W/S0pTYtRZ4s=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5008e0a7.xn--i8sz2z.k1207; olt=johnl@user.iecc.com; bh=NuQQeAbYBTjge4Ob1Ss16FjboYhHeGjL4iFdVvcEPZ0=; b=lUhmKofRA2UftIX71qD7v+9R0XpqPjp2258xq4A/2C5NXnmieGY8zwWMJ72oHtkj/0Vbttzbc/2Iw5nbNlnoBntmRTjIfRWG0S/m5PDSX2mdL81etPHAh9z1ii08CCz4z1bnAcRTfOBvt5nrjfMSJYyAR3XwyvvP/YDmWiPA+3k=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 20 Jul 2012 04:37:37 -0000
Message-ID: <20120720043737.60219.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <CC2F1666.34047%chris@ausregistry.com.au>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 04:37:09 -0000

>Im not sure that we should dismiss a workable solution simply because one
>technology doesn't support it

There's going to be a thousand times as many WEIRDS clients as WEIRDS
servers.  Given a choice between adding more complexity to the clients
and adding it to the servers, the correct choice is clearly to do the
work in the servers.

We need some way to bootstrap the queries and find an initial server,
but the simpler the bootstrap the better.  Once the client has found
an initial server, the servers know how to do referrals.

> it would simply need to call to a web service first that 'figured out' what
>the correct URL is to send the lookup to.

A web service?  That would be the initial WEIRDS server found via a
CNAME, and the URL would be returned as a referral.  What would be the
advantage of inventing another web service that sort of does what
WEIRDS already can do?

R's,
John

From Ray.Bellis@nominet.org.uk  Thu Jul 19 23:45:27 2012
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCECA21F850F for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 23:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.581
X-Spam-Level: 
X-Spam-Status: No, score=-10.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zFxc3wFfxLSH for <weirds@ietfa.amsl.com>; Thu, 19 Jul 2012 23:45:27 -0700 (PDT)
Received: from mx4.nominet.org.uk (mx4.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id C35E721F8642 for <weirds@ietf.org>; Thu, 19 Jul 2012 23:45:25 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:Received:Received:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:Content-Type: Content-Transfer-Encoding:MIME-Version; b=PWvl+HnZN6P4KO35tghsD6E55Z3C+tkZ6X6a5I0EQuIKsHidBVapupji kPra8eYk8BZfdJz7Kr4K2ycdGsr3wxWGB8K+nFlBhrgiAwIp+g4mhZTFD wMmNvXWHwguLGic;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1342766782; x=1374302782; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20RE:=20[weirds]=20Authentication=20Methods |Date:=20Fri,=2020=20Jul=202012=2006:39:42=20+0000 |Message-ID:=20<8B7F972437853B40865000D86857B1D1010721B7E 3@wds-exc2.okna.nominet.org.uk>|To:=20Andy=20Newton=20<an dy@arin.net>|CC:=20Web=20Extensible=20Internet=20Registra tion=20Data=20Service=20Working=20Group=0D=0A=09<weirds@i etf.org>|MIME-Version:=201.0|Content-Transfer-Encoding: =20quoted-printable|In-Reply-To:=20<F2D61449-F5B4-44E4-B0 A3-630B9E47FBD0@arin.net>|References:=20<20120718142657.2 6067.qmail@joyce.lan>=0D=0A=20<8152AEFC-9398-47E7-9DEE-A6 62F0E64E28@arin.net>=0D=0A=20<002701cd6550$6c1a3ba0$444eb 2e0$@cn>=0D=0A=20<B5F40D70-914D-4696-A6F6-A6C02E63F82B@no minet.org.uk>,<F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin. net>; bh=Wn/MQBWKD3fh6cgEHbtlbnCMRj8WnZ1Nza3eQQ5ZWC8=; b=ES2wZDixWBpQVnvGK4K58u5eLsKqJPPLXifpA8ownrCn7JPVbiqwucG+ lKVl1pzo2VkxWvo5jLIxe1wN81Yi4OHB5QdOCIYtsKYRrx+Ym0Q+vamXB elegU8geMhb6Af0;
X-IronPort-AV: E=Sophos;i="4.77,621,1336345200"; d="scan'208";a="34239094"
Received: from wds-exc1.okna.nominet.org.uk ([213.248.197.144]) by mx4.nominet.org.uk with ESMTP; 20 Jul 2012 07:46:19 +0100
Received: from WDS-EXC2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4]) by wds-exc1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f%19]) with mapi; Fri, 20 Jul 2012 07:46:18 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Andy Newton <andy@arin.net>
Thread-Topic: [weirds] Authentication Methods
Thread-Index: AQHNYzSVaT5sUZ9lAki+OrM4ADgQbpcurl0AgABdO4CAABfFgIAApk0AgABp6wCAAHk/gIABEaU1
Date: Fri, 20 Jul 2012 06:39:42 +0000
Message-ID: <8B7F972437853B40865000D86857B1D1010721B7E3@wds-exc2.okna.nominet.org.uk>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <002701cd6550$6c1a3ba0$444eb2e0$@cn> <B5F40D70-914D-4696-A6F6-A6C02E63F82B@nominet.org.uk>, <F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net>
In-Reply-To: <F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 06:45:28 -0000

> We need to be careful here. If we define so many MUSTs (or even MAYs), th=
ere will be push back that this is a heavyweight specification and some wil=
l use that to avoid implementation.=0A=
=0A=
IMHO we should restrict our stronger 2119 keywords for those authentication=
 methods that are universally supported in HTTP library APIs (e.g. basic au=
th, TLS client certs) and none of those new-fangled end-user-centric method=
s (e.g. OpenID).=0A=
=0A=
Ray=0A=

From Ray.Bellis@nominet.org.uk  Fri Jul 20 03:17:38 2012
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB7721F8525 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 03:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.582
X-Spam-Level: 
X-Spam-Status: No, score=-10.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hRekSNxtBI9R for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 03:17:37 -0700 (PDT)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id 57D2D21F8522 for <weirds@ietf.org>; Fri, 20 Jul 2012 03:17:36 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:Received:Received:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=PhkR3TX6mxUtC+ZlgYZlGCFODtXJx4yuzI90TMXKN4PM5qQM7YxpnrQX L6K502MF1lz+5UAI7MfqfnU3LkuH8mINJQUxgZ9Ux2zmHqXCZb00ZMTO5 smKf9IevcZmtSoj;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1342779513; x=1374315513; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[weirds]=20REST-pect-ful|Date:=20Fri, =2020=20Jul=202012=2010:18:29=20+0000|Message-ID:=20<3292 9BD0-0604-4C5F-BDC2-30313A1D1AB9@nominet.org.uk>|To:=20Pe ter=20Koch=20<pk@DENIC.DE>|CC:=20"<weirds@ietf.org>"=20<w eirds@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<63eb46eb-4b11-4925-a4f9-6d93d464e3b4> |In-Reply-To:=20<20120719180542.GF24669@x28.adm.denic.de> |References:=20<D3D8582E-BE04-4BCF-88D9-B73A3813003E@arin .net>=0D=0A=20<CC245AB3.12E9B%james.mitchell@ausregistry. com.au>=0D=0A=20<20120719180542.GF24669@x28.adm.denic.de>; bh=FuCRy7sW3IcmBCvMKj+EHge1X+cifV8SzF7Hp1A5iDY=; b=R2IYudAg64YcKZ4ebhfQOvj/9G0fD1umORknCP99bUO2RPqffiZwrlMY tJjJ3hnij02Rr9O8+IGFz5Q4cm21Vxibfdk8Qi6LIZNLi4AQHkbz0Wpe/ zo6SZewLJZb243H;
X-IronPort-AV: E=Sophos;i="4.77,622,1336345200"; d="scan'208";a="34243963"
Received: from wds-exc1.okna.nominet.org.uk ([213.248.197.144]) by mx4.nominet.org.uk with ESMTP; 20 Jul 2012 11:18:30 +0100
Received: from WDS-EXC2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4]) by wds-exc1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f%19]) with mapi; Fri, 20 Jul 2012 11:18:29 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Peter Koch <pk@DENIC.DE>
Thread-Topic: [weirds] REST-pect-ful
Thread-Index: AQHNX6F5WbKwdHS6fEepy8hgOHL685ckdGMAgAAGEgCAAGxBgIAL+3wAgAEPyoA=
Date: Fri, 20 Jul 2012 10:18:29 +0000
Message-ID: <32929BD0-0604-4C5F-BDC2-30313A1D1AB9@nominet.org.uk>
References: <D3D8582E-BE04-4BCF-88D9-B73A3813003E@arin.net> <CC245AB3.12E9B%james.mitchell@ausregistry.com.au> <20120719180542.GF24669@x28.adm.denic.de>
In-Reply-To: <20120719180542.GF24669@x28.adm.denic.de>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <63eb46eb-4b11-4925-a4f9-6d93d464e3b4>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] REST-pect-ful
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 10:17:38 -0000

On 19 Jul 2012, at 19:05, Peter Koch wrote:

> In those cases where an object or an attribute is withheld I do not
> think it would be either proper protocol design to add a magic string
> (as opposed to an extra alphabetical token) or within the purpose
> of the limited visibility to disclose the presence of the data.

+1 - I see no benefit in informing the client about data that exists but ha=
s been omitted.

Ray


From vesely@tana.it  Fri Jul 20 03:44:29 2012
Return-Path: <vesely@tana.it>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7754F21F859B for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 03:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.626
X-Spam-Level: 
X-Spam-Status: No, score=-4.626 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XyWuJQdgqRga for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 03:44:28 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id B08F221F8575 for <weirds@ietf.org>; Fri, 20 Jul 2012 03:44:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1342781121; bh=BjtB9/Py/5x1PU7Bh/CzulSQ7OE36vOoegAweEGGzz4=; l=789; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=erlSvVM+9C38IlJUDjGYpL/JkJ6tFSPmZIuIdKPJZUCeUsZ+i4i9YRFW2HytYG9I1 4WMc2jaesdQfk+Whir/ba2EDG576fMowz5lffdCgbVh0TyqxVRlo3b+04yS8eSkJlp 0zexFhwtAO2FjEKReu03Eu1U8W4uysx6n2ROvPRI=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Fri, 20 Jul 2012 12:45:21 +0200 id 00000000005DC047.00000000500936C1.000015EB
Message-ID: <500936C1.60109@tana.it>
Date: Fri, 20 Jul 2012 12:45:21 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: weirds@ietf.org
References: <8CEF048B9EC83748B1517DC64EA130FB729CD7209B@off-win2003-01.ausregistrygroup.local> <20120720011046.96838.qmail@joyce.lan> <8CEF048B9EC83748B1517DC64EA130FB729CD72111@off-win2003-01.ausregistrygroup.local> <alpine.BSF.2.00.1207192308240.19001@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1207192308240.19001@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 10:44:29 -0000

On Fri 20/Jul/2012 05:36:57 +0200 John R Levine wrote:
> 
> IPv6 is a little tricker, since IANA's allocations were originally /23
> and have since grown to /12.  If we do x.x.x.x.x.x.weirds.arpa, where
> the x's are the first six hex digits of the address, a zone with an
> entry for all of the allocated space would have about 21K entries. 
> That's a factor of 10 bigger than the TLD list (assuming ICANN
> allocates most of the 1500 TLDs applied for) but still not
> ridiculous.  I realize you could shrink the zone by using reversing
> the digits and using wildcards, but then it'd refer queries for
> addresses that aren't allocated to servers that aren't expecting them,
> which doesn't strike me as a good idea.

Would using DNAMEs yield workable practices in this case?


From dk@hostmaster.ua  Fri Jul 20 04:40:54 2012
Return-Path: <dk@hostmaster.ua>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD1621F85AD for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 04:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a9F8CXu2tpRk for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 04:40:52 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 5194D21F85A3 for <weirds@ietf.org>; Fri, 20 Jul 2012 04:40:52 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 4BA71209A3; Fri, 20 Jul 2012 07:41:47 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Fri, 20 Jul 2012 07:41:47 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=NW8ePgxUCwNRT0TIbiDz8RK/joA=; b=IG DKhLuARzC6WpFcbzx69djmjq4MnYTbPFHglte/hV6j5yIn6nXJnz2JUIe7ZEFdJo 1MwpYcuPKyiv43pGgOGE9OB2zwDkaea0CEW+NWel2OZdixLvYkc9Q3ifqTbDuohK Q861wZDG/cxzJMPuPKQQVwX4N6LYbn0kzVRluJaLo=
X-Sasl-enc: f42bPYjpBDKl0eN44MF0bE8oY/Pwo9L/H6oA9HuroON7 1342784506
Received: from dhcp156.hostmaster.ua (unknown [109.70.104.123]) by mail.messagingengine.com (Postfix) with ESMTPA id 6F3388E01FC; Fri, 20 Jul 2012 07:41:46 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Dmitry Kohmanyuk <dk@hostmaster.ua>
In-Reply-To: <alpine.BSF.2.00.1207111105280.36659@joyce.lan>
Date: Fri, 20 Jul 2012 14:41:44 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <8225CDBD-8543-49B7-8D0C-6F71B58C7056@hostmaster.ua>
References: <20120710212029.77643.qmail@joyce.lan> <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net> <alpine.BSF.2.00.1207111105280.36659@joyce.lan>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1278)
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 11:40:54 -0000

On Jul 11, 2012, at 6:57 PM, John R Levine wrote:

>=20
> There are lots of redirects in the name space.  One of particular =
interest to me is that the .US domain still has subregistries for many =
geographic domains, and the subregistry agreement requires that we =
provide WHOIS.  I run one of those subregistries, but have never =
bothered to provide WHOIS because if I did, there would be no way for =
anyone to find it.  This was brought home to me last week when I started =
getting confirmation mail from Godaddy for SSL certificates that one of =
my registrants had bought.  Here in upstate NY things are pretty =
informal, and five minutes after the first message arrived, the phone =
rang and it was the registrant (the government of a nearby county) =
telling me that they'd ordered them so could I please approve them.  But =
that doesn't scale too well.

in UA ccTLD (which I help to run) we have whois.ua server automagically =
redirect whois queries to various sub registries when needed.   sample:

% request from 2001:4130::3544:bb73:25bf:6a1e
% This is the Ukrainian Whois query server #F.
% The Whois is subject to Terms of use
% See https://hostmaster.ua/services/
%

% The object shown below is NOT in the UANIC database.
% It has been obtained by querying a remote server:
% (whois.dp.ua) at port 43.
%
% REDIRECT BEGIN

% This is the Dnepropetrovsk Whois query server.
%

domain:           whois.dp.ua
[=85]

Our approach does not scale well (as central whois server for UA has =
50-something public delegations) but it works fine in ccTLD space.

I would consider using _nicname._tcp.domain.ua approach for those who =
want to get whois server information directly from delegated domain.

> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> "I dropped the toothpaste", said Tom, crestfallenly.
>=20
> PS: The whois.iana.org server has both an IPv4 address and an IPv6 =
address, but the IPv6 address doesn't work, as in I can't connect, can't =
ping, and traceroutes get lost somewhere in NTT's network.  I'd think =
that if anyone actually used it, someone would have noticed and fixed =
this by now.

you must have some problems with your IPv6 connectivity in upstate NY - =
here in Ukraine, IPv6 address of whois.iana.org works just fine:

$ telnet -6 whois.iana.org nicname
Trying 2620:0:2830:200::59...
Connected to ianawhois.vip.icann.org.
Escape character is '^]'.
ua
% IANA WHOIS server
% for more information on IANA, visit http://www.iana.org
% This query returned 1 object

domain:       UA

organisation: Communication Systems Ltd
address:      vul Vavilovykh 18
address:      Kyiv  04060
address:      Ukraine
[=85]=

From fneves@registro.br  Fri Jul 20 04:56:11 2012
Return-Path: <fneves@registro.br>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B752E21F8570 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 04:56:11 -0700 (PDT)
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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKOvXY5KaiFV for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 04:56:11 -0700 (PDT)
Received: from clone.registro.br (clone.registro.br [IPv6:2001:12ff:0:2::4]) by ietfa.amsl.com (Postfix) with ESMTP id 2CFB421F8569 for <weirds@ietf.org>; Fri, 20 Jul 2012 04:56:11 -0700 (PDT)
Received: by clone.registro.br (Postfix, from userid 1000) id 28EB5E042F; Fri, 20 Jul 2012 08:57:06 -0300 (BRT)
Date: Fri, 20 Jul 2012 08:57:06 -0300
From: Frederico A C Neves <fneves@registro.br>
To: John R Levine <johnl@taugh.com>
Message-ID: <20120720115706.GG85645@registro.br>
References: <8CEF048B9EC83748B1517DC64EA130FB729CD7209B@off-win2003-01.ausregistrygroup.local> <20120720011046.96838.qmail@joyce.lan> <8CEF048B9EC83748B1517DC64EA130FB729CD72111@off-win2003-01.ausregistrygroup.local> <alpine.BSF.2.00.1207192308240.19001@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1207192308240.19001@joyce.lan>
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 11:56:11 -0000

On Thu, Jul 19, 2012 at 11:36:57PM -0400, John R Levine wrote:
> > They do if you turn them into their reverse DNS form. It works fine.
> 
> Two points.  One is that rDNS zones have never had anything in them other 
> than NS, CNAME, and PTR.  You'd hope that nothing strange would happen if 
> you put in other stuff, but I wouldn't want to try it without some 
> significant testing first.

This is a red herring, these zones are not special and any RR
supported or not (3597) works just fine. The IP -> ARPA conversion is
done at the DNS client code or stub resolver library level.

> I thought SRV was a swell idea until Andy reported that a lot of the 
> queries to the existing WEIRDS prototype are coming from Javascript 
> programs that are running in web browsers.  There is no way to do a DNS 
> lookup from Javascript other than the implicit A and AAAA lookup that 

So that said _weirds._tcp.TLD IN A works just fine for a limited
bootstrap as long as we could live with a fixed the port. This looks
like a reasonable compromise for simplicity sake.

Fred

From fneves@registro.br  Fri Jul 20 05:06:59 2012
Return-Path: <fneves@registro.br>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA34121F85D5 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 05:06:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, J_CHICKENPOX_52=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hjhDy8rBDgZO for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 05:06:59 -0700 (PDT)
Received: from clone.registro.br (clone.registro.br [IPv6:2001:12ff:0:2::4]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8FF21F85D1 for <weirds@ietf.org>; Fri, 20 Jul 2012 05:06:59 -0700 (PDT)
Received: by clone.registro.br (Postfix, from userid 1000) id 875F8E0511; Fri, 20 Jul 2012 09:07:54 -0300 (BRT)
Date: Fri, 20 Jul 2012 09:07:54 -0300
From: Frederico A C Neves <fneves@registro.br>
To: Dmitry Kohmanyuk <dk@hostmaster.ua>
Message-ID: <20120720120754.GH85645@registro.br>
References: <20120710212029.77643.qmail@joyce.lan> <4AC81C86-BF30-4201-977A-CD19D808E1C9@arin.net> <alpine.BSF.2.00.1207111105280.36659@joyce.lan> <8225CDBD-8543-49B7-8D0C-6F71B58C7056@hostmaster.ua>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8225CDBD-8543-49B7-8D0C-6F71B58C7056@hostmaster.ua>
Cc: John R Levine <johnl@taugh.com>, "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 12:07:00 -0000

Dimitry,

On Fri, Jul 20, 2012 at 02:41:44PM +0300, Dmitry Kohmanyuk wrote:
> 
> On Jul 11, 2012, at 6:57 PM, John R Levine wrote:
> 
...
> 
> in UA ccTLD (which I help to run) we have whois.ua server automagically redirect whois queries to various sub registries when needed.   sample:
> 
> % request from 2001:4130::3544:bb73:25bf:6a1e
> % This is the Ukrainian Whois query server #F.
> % The Whois is subject to Terms of use
> % See https://hostmaster.ua/services/
> %
> 
> % The object shown below is NOT in the UANIC database.
> % It has been obtained by querying a remote server:
> % (whois.dp.ua) at port 43.
> %
> % REDIRECT BEGIN
> 
> % This is the Dnepropetrovsk Whois query server.
> %
> 
> domain:           whois.dp.ua
> [?]
> 
> Our approach does not scale well (as central whois server for UA has 50-something public delegations) but it works fine in ccTLD space.
> 
> I would consider using _nicname._tcp.domain.ua approach for those who want to get whois server information directly from delegated domain.
> 

Strictly speaking this is actually not a redirection but a proxy whois
server intermediating the query. A RESTFul architecture will provide
us with all the required tools to easily build more scalable systems
with smarter clients.

Fred

From galvin+weirds@elistx.com  Fri Jul 20 05:37:47 2012
Return-Path: <galvin+weirds@elistx.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9CE21F85E3 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 05:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQ+gyG8wBAJu for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 05:37:46 -0700 (PDT)
Received: from ee01.elistx.com (ee01.elistx.com [67.155.182.182]) by ietfa.amsl.com (Postfix) with ESMTP id 6A09521F85E1 for <weirds@ietf.org>; Fri, 20 Jul 2012 05:37:46 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by elistx.com (PMDF V6.3-2x2 #31965) with ESMTP id <0M7G0002ILR6A2@elistx.com> for weirds@ietf.org; Fri, 20 Jul 2012 08:37:55 -0400 (EDT)
Date: Fri, 20 Jul 2012 08:38:51 -0400
From: Jim Galvin <galvin+weirds@elistx.com>
In-reply-to: <F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net>
To: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Message-id: <9C034D938509E4DDB82B536D@James-Galvin-2.local>
MIME-version: 1.0
X-Mailer: Mulberry/4.0.8 (Mac OS X)
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <002701cd6550$6c1a3ba0$444eb2e0$@cn> <B5F40D70-914D-4696-A6F6-A6C02E63F82B@nominet.org.uk> <F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 12:37:47 -0000

-- On July 19, 2012 3:20:17 PM +0000 Andy Newton <andy@arin.net> wrote 
regarding Re: [weirds] Authentication Methods --

> I think the question ought to be asked, does any Whois operator today
> have differentiated access, either via port 43 or other Whois-type
> services, or does any Whois operator have plans in the works to
> implement some type of differentiated access. Getting answers to such
> questions would limit the scope.

Could the differentiated access be one of two things: here's some 
public information I'll give to anybody versus if you want complete or 
specific information you have to provide the right credentials.

If I'm the server motivated by the policies that manage the information 
I'm making available, I simply do whatever I have to do.  If all 
authentication methods are "MAY" I choose the one or more that works 
best for me.  Any client who wants my information will need to meet my 
requirements.

If I'm the user behind the client, I have to choose to use a client 
that supports the credentials I need to have available.  That could be 
no authentication is supported, in which case I get only the "public" 
information.

It was Ray Bellis who pointed out that there are so many HTTP 
Authentication Methods to choose from.  Why is it our job to fix that? 
If we're building this on top of HTTP then let's leave that problem for 
HTTP "to fix".

I agree with Andrew Sullivan who said make everything a "MAY".  I think 
our energy is better directed towards being able to respond with 
minimal information at all times or perhaps a "standard" response of 
some sort that includes a referral or at least a designation of the 
credentials you need and where you can go to get instructions on 
obtaining them.

Jim


From Ray.Bellis@nominet.org.uk  Fri Jul 20 06:00:42 2012
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B18321F8630 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 06:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.526
X-Spam-Level: 
X-Spam-Status: No, score=-10.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1mu3Bzd24Wwy for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 06:00:41 -0700 (PDT)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id A201021F862B for <weirds@ietf.org>; Fri, 20 Jul 2012 06:00:41 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:Received:Received:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=QFuT3BXG+RxEtzCdbT8g77hf06GwjZO4KoOko6v/3lL8A+dG/emAkE9+ +wV2VEYZclcXDc3ZZQu1btsvA0tTkKYqgwwlwCU6CSJW1nMeMqw0sR2nN Fog9lxsl9tf6zVq;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1342789298; x=1374325298; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[weirds]=20Authentication=20Methods |Date:=20Fri,=2020=20Jul=202012=2013:01:36=20+0000 |Message-ID:=20<083F850A-CA48-4A24-85AD-AF73492B5D3D@nomi net.org.uk>|To:=20Jim=20Galvin=20<galvin+weirds@elistx.co m>|CC:=20Web=20Extensible=20Internet=20Registration=20Dat a=20Service=20Working=20Group=0D=0A=09<weirds@ietf.org> |MIME-Version:=201.0|Content-Transfer-Encoding:=20quoted- printable|Content-ID:=20<f066e259-12ac-4d58-96fd-b24c5dae 8c28>|In-Reply-To:=20<9C034D938509E4DDB82B536D@James-Galv in-2.local>|References:=20<20120718142657.26067.qmail@joy ce.lan>=0D=0A=20<8152AEFC-9398-47E7-9DEE-A662F0E64E28@ari n.net>=0D=0A=20<002701cd6550$6c1a3ba0$444eb2e0$@cn>=0D=0A =20<B5F40D70-914D-4696-A6F6-A6C02E63F82B@nominet.org.uk> =0D=0A=20<F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net> =0D=0A=20<9C034D938509E4DDB82B536D@James-Galvin-2.local>; bh=KyzyiYMJjYBNGAGI2C1WueWDdrxEXO0m9sx+gmhwmQU=; b=jv1ehy/28cM6ppi0HYG8rKMTt6tKzEwPUZsWLBYRr1zay/o+OQGr3qKP RjHFd2lV6JcJT31TjArqmPz2bHDJdziHzcI5qa7aaDLL/Z+/awt4gouq6 fTCRN9onQqNUveF;
X-IronPort-AV: E=Sophos;i="4.77,623,1336345200"; d="scan'208";a="34245288"
Received: from wds-exc1.okna.nominet.org.uk ([213.248.197.144]) by mx4.nominet.org.uk with ESMTP; 20 Jul 2012 14:01:37 +0100
Received: from WDS-EXC2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4]) by wds-exc1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f%19]) with mapi; Fri, 20 Jul 2012 14:01:36 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Jim Galvin <galvin+weirds@elistx.com>
Thread-Topic: [weirds] Authentication Methods
Thread-Index: AQHNYzSVaT5sUZ9lAki+OrM4ADgQbpcurl0AgABdO4CAABfFgIAApk0AgABp6wCAAHk/gIABZTqAgAAGWwA=
Date: Fri, 20 Jul 2012 13:01:36 +0000
Message-ID: <083F850A-CA48-4A24-85AD-AF73492B5D3D@nominet.org.uk>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <002701cd6550$6c1a3ba0$444eb2e0$@cn> <B5F40D70-914D-4696-A6F6-A6C02E63F82B@nominet.org.uk> <F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net> <9C034D938509E4DDB82B536D@James-Galvin-2.local>
In-Reply-To: <9C034D938509E4DDB82B536D@James-Galvin-2.local>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <f066e259-12ac-4d58-96fd-b24c5dae8c28>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 13:00:42 -0000

On 20 Jul 2012, at 13:38, Jim Galvin wrote:

>=20
> It was Ray Bellis who pointed out that there are so many HTTP Authenticat=
ion Methods to choose from.

It was :)

> Why is it our job to fix that? If we're building this on top of HTTP then=
 let's leave that problem for HTTP "to fix".

But I didn't intend to propose that we fix that.

I do think (as I posted later) that we should actively avoid any authentica=
tion method that involves multiple interactions between client and server, =
i.e. cookies, OpenID, etc.

Those methods are designed for authenticating end users (i.e. someone sat a=
t a browser).  They are not intended for "machine to machine" authenticatio=
n.

I am slightly puzzled by Andy's observation of the high number of browser g=
enerated queries at the ARIN server.  I can only surmise that those are "pr=
oof of concept" implementations.

For the kinds of differentiated access we have in mind here, I'm fairly sur=
e that authorising individual end users sat at a browser talking directly t=
o the server via AJAX are not amongst them.  Those users will just get the =
default minimum view.

Ray


From johnl@iecc.com  Fri Jul 20 07:46:37 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93B4621F8608 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 07:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.134
X-Spam-Level: 
X-Spam-Status: No, score=-111.134 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lmMIdo+jsPH5 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 07:46:35 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 37D0821F85A4 for <weirds@ietf.org>; Fri, 20 Jul 2012 07:46:35 -0700 (PDT)
Received: (qmail 82048 invoked from network); 20 Jul 2012 14:47:27 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Jul 2012 14:47:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50096f7f.xn--hew.k1207; i=johnl@user.iecc.com; bh=eIgi/eEIh/9bk7YxXLlBzoW6sZSXr69Yk6QUoov7jOY=; b=YvTJKPqfgylV5RSyqyNTuDh15bxWrAWwpi2oM1Pnrg9LY1ktrKnluiDbG9FmyB/ffKV0sdsVB0nFfU5TFhovwzfcU+JjwFO8l6xdYGYBN7rvkN4Izr8qDpHYr93MAA9aw6lTjfyfViC8CLoDRkxT9wLXMoQySPqNjXXGdMqCGpk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50096f7f.xn--hew.k1207; olt=johnl@user.iecc.com; bh=eIgi/eEIh/9bk7YxXLlBzoW6sZSXr69Yk6QUoov7jOY=; b=pR/X+doHclVAkUwJRwoXAXuNlklNA1+RDo9O+hDIq7kWn/9646iK/rOffrDQdd/MmBVXINRzLEKtrTDDc+9uF++RC/H1gevjS7bw2FkEkWYCNcCSiR50i9ovTpTl3C66jkRweaQnXPconifrQ4WhHoAdyuSkrVnL/pL479pAzaQ=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 20 Jul 2012 14:47:05 -0000
Message-ID: <20120720144705.73747.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <8B7F972437853B40865000D86857B1D1010721B7E3@wds-exc2.okna.nominet.org.uk>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:46:38 -0000

> IMHO we should restrict our stronger 2119 keywords for those
> authentication methods that are universally supported in HTTP library
> APIs (e.g. basic auth, TLS client certs) and none of those new-fangled
> end-user-centric methods (e.g. OpenID).

OK.  How do you feel about oauth?

R's,
John

From johnl@iecc.com  Fri Jul 20 07:49:15 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D307D21F8495 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 07:49:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.135
X-Spam-Level: 
X-Spam-Status: No, score=-111.135 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DARMqR4E0L9p for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 07:49:15 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id AE62821F8494 for <weirds@ietf.org>; Fri, 20 Jul 2012 07:49:14 -0700 (PDT)
Received: (qmail 82672 invoked from network); 20 Jul 2012 14:50:10 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Jul 2012 14:50:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50097022.xn--3zv.k1207; i=johnl@user.iecc.com; bh=RGC7FsUzylvJPRIzFu0PS/s9QQMEDlFUz4V4M7gdnMc=; b=prq4doBCSDoj9oPV/wC5fYj4Sf/QZXftdEkw5524e9M4DKi2UJaweriZMMLSsFsNB6Cve6a/rDnpb1KR+sL51F0Ct5jDY0i3Z3ABwMKdODHEiNZbRySRtBjMPshe7IFTsCLv2DMLdcXW5oeEKDOCPonjS/2DZGVyFY/V0I2paCg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50097022.xn--3zv.k1207; olt=johnl@user.iecc.com; bh=RGC7FsUzylvJPRIzFu0PS/s9QQMEDlFUz4V4M7gdnMc=; b=SYp/wW9//a/68SUfBpKsFwcMIXT7xliqEMaXZR7pjm0Q8zPTDc9Vct0ekNQzuZnFo1Zb1A45h2R/DGl2I+qo12Iaf3IqQRBDvAz2CTrSvS6bEfqzUe4S7B2VthhUpHMP/2bhpQ4qsdvyhIphayE0N1yAeFHnJ1C9CgbNH1xtuQg=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 20 Jul 2012 14:49:48 -0000
Message-ID: <20120720144948.74504.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <20120720115706.GG85645@registro.br>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:49:16 -0000

>> Two points.  One is that rDNS zones have never had anything in them other 
>> than NS, CNAME, and PTR.  You'd hope that nothing strange would happen if 
>> you put in other stuff, but I wouldn't want to try it without some 
>> significant testing first.
>
>This is a red herring, these zones are not special and any RR
>supported or not (3597) works just fine. The IP -> ARPA conversion is
>done at the DNS client code or stub resolver library level.

We all know that's the theory.  Since there have never been A or
SRV records in rDNS zones, how much are you willing to wager that
all the existing client libraries will properly disregard them?

>So that said _weirds._tcp.TLD IN A works just fine for a limited
>bootstrap as long as we could live with a fixed the port.

Since that's not a valid hostname, I think I can pretty much
guarantee that it won't work from Javascript.

R's,
John

From carlosm3011@gmail.com  Fri Jul 20 07:51:50 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6BC921F866D for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 07:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hynwQ8IRhA4v for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 07:51:49 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9820B21F8669 for <weirds@ietf.org>; Fri, 20 Jul 2012 07:51:49 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so4447149ghb.31 for <weirds@ietf.org>; Fri, 20 Jul 2012 07:52:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=m1v1Tps2oBzuZ5xhY1NWherN6/Pje3Uz+oT+KMBeZ6E=; b=BkGHbB3kc8lxXjvrWUDNFL5WvWnDoOabohERgbvA8OwluEW+am139sbJU4f+2JSlv/ QnfJVQQaj1H5xLgf/4nygTtwOg7qIieG3UnGc5L840h4H2Jg9BdXxH8GE+cRBFrzOvmP fkbqp1wOmiK8J2lWtbEih/XLRDPpP7GNMTZ6Ao4TEOLtagrzEVYY0gVup/GoZtf92vM1 E8XOJvCL/+wpvWEZvQh6UI6RrJ5ZeaODvh2/9cxYBA8KEcn+lsSuqShvLCUKq1GKxeqo vXzZfNPDvm2Ck1qLBKaGfhQCEk9yqubWYL3estHqHTcPZeL0KBoI4vwo+dON2Lg20crc QOUA==
Received: by 10.236.75.232 with SMTP id z68mr5891415yhd.90.1342795965540; Fri, 20 Jul 2012 07:52:45 -0700 (PDT)
Received: from europa.local ([190.115.129.45]) by mx.google.com with ESMTPS id l49sm9834645yhk.15.2012.07.20.07.52.42 (version=SSLv3 cipher=OTHER); Fri, 20 Jul 2012 07:52:43 -0700 (PDT)
Message-ID: <500970B9.7060809@gmail.com>
Date: Fri, 20 Jul 2012 10:52:41 -0400
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Chris Wright <chris@ausregistry.com.au>
References: <CC2E3BAC.33F74%chris@ausregistry.com.au> <50081E0D.7060309@gmail.com> <8CEF048B9EC83748B1517DC64EA130FB729CD7209B@off-win2003-01.ausregistrygroup.local>
In-Reply-To: <8CEF048B9EC83748B1517DC64EA130FB729CD7209B@off-win2003-01.ausregistrygroup.local>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: "carlos@lacnic.net" <carlos@lacnic.net>, "weirds@ietf.org" <weirds@ietf.org>, Alessandro Vesely <vesely@tana.it>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:51:51 -0000

I'm not sure I get what he meant then. Maybe a longish explanation would
help.


On 7/19/12 8:02 PM, Chris Wright wrote:
> I'm not sure you understood the idea, 
>
> There would only be one record in the zone file (or maybe a few for redundancy reasons), itâ€™s a bootstrap pointer not a pointer for every domain.
>
> So I donâ€™t think there would be any issue.
>
> Thanks
>
> Chris
>
>
> -----Original Message-----
> From: Carlos Martinez-Cagnazzo [mailto:carlosm3011@gmail.com] 
> Sent: Friday, 20 July 2012 12:48 AM
> To: Chris Wright
> Cc: Alessandro Vesely; weirds@ietf.org
> Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
>
> I thought about that, but decided against it on the grounds that it will increase zone size by a sizeable factor, which might not be an issue for some operators but definitely will hurt others like .com
>
> thoughts?
>
> regards
>
> Carlos
>
> On 7/19/12 8:36 AM, Chris Wright wrote:
>> Why not a DNS Resource Record that lives in the tld zone file? No need 
>> to have IANA involved then and TLD manager can update as required.
>>
>> dig -t WEIRDS tad returns URL of weirds service
>>
>> Or we could potentially use existing records like SRV or NAPTR ?
>>
>> Thanks
>>
>> Chris
>>
>> On 19/07/12 1:25 AM, "Alessandro Vesely" <vesely@tana.it> wrote:
>>
>>> On Tue 17/Jul/2012 15:10:07 +0200 Andy Newton wrote:
>>>> On Jul 12, 2012, at 10:08 AM, John R Levine wrote:
>>>>
>>>>>>> I suppose one could use a CNAME kludge of <tld>.wierdsservers.net 
>>>>>>> or <1.2.3.4.5.6>.weirdsservers.net, analogous to Rodney's 
>>>>>>> whoisservers.net, that doesn't require a lookup before the http 
>>>>>>> query.
>>>>>> Interesting. Why not XXXX.weirds.arpa?
>>>>> Uh, because I wasn't thinking far enough ahead?  That would involve 
>>>>> IANA, but in a pretty benign way.  They'd have to update their 
>>>>> processes to allow entities that have been delegated a TLD or a top 
>>>>> level IP range to register and update WEIRDS servers, but it'd be 
>>>>> no more work than maintaining the in-addr zone which they do now.
>>>> I think this is workable and strikes the right balance for the needs 
>>>> of the clients vs. distributed bootstrapping.
>>> +1, I'll hum for it if it goes in A.5.2
>>> _______________________________________________
>>> weirds mailing list
>>> weirds@ietf.org
>>> https://www.ietf.org/mailman/listinfo/weirds
>> _______________________________________________
>> weirds mailing list
>> weirds@ietf.org
>> https://www.ietf.org/mailman/listinfo/weirds
>
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds



From Ray.Bellis@nominet.org.uk  Fri Jul 20 07:53:43 2012
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38EED21F8566 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 07:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.53
X-Spam-Level: 
X-Spam-Status: No, score=-10.53 tagged_above=-999 required=5 tests=[AWL=0.069,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x2iRcb1v1JzZ for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 07:53:41 -0700 (PDT)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id 7F2E621F84E6 for <weirds@ietf.org>; Fri, 20 Jul 2012 07:53:39 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:Received:Received:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=ZrfTWWGvJllo7c7wPA4egC5vhPWr2rbmVX+ap2oTAzY9CdGLP1L1k7tX DDmPemo1dXhwHoQpMdgW1gsIRQ80Gs01fSIjYlFCIzSyerR8vwKABnp6f iI2kXRj1htm5fM8;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1342796078; x=1374332078; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[weirds]=20Authentication=20Methods |Date:=20Fri,=2020=20Jul=202012=2014:54:33=20+0000 |Message-ID:=20<B412C3D4-FB26-41D3-80D1-D64DD4966E4D@nomi net.org.uk>|To:=20John=20Levine=20<johnl@taugh.com>|CC: =20Web=20Extensible=20Internet=20Registration=20Data=20Se rvice=20Working=20Group=0D=0A=09<weirds@ietf.org> |MIME-Version:=201.0|Content-Transfer-Encoding:=20quoted- printable|Content-ID:=20<a9e1d74e-73cf-426a-b45d-204a68f5 6b0d>|In-Reply-To:=20<20120720144705.73747.qmail@joyce.la n>|References:=20<20120720144705.73747.qmail@joyce.lan>; bh=7IHiVM6bjw/l/9qXmURh5cwf6JE92TpZkm6SKtgKbak=; b=ld8wSQfQ+MOPMY87iXsR3znNWzJbKiNd2UHM/tSO8e5bgVDMY83WMbvM 5tn2z6Mt0NLOzrjAfVJxh4u43aCcHwWuz0elSCHehfPCCMwQPcroyUofN /n6FmhviAcM2by3;
X-IronPort-AV: E=Sophos;i="4.77,623,1336345200"; d="scan'208";a="34247996"
Received: from wds-exc1.okna.nominet.org.uk ([213.248.197.144]) by mx4.nominet.org.uk with ESMTP; 20 Jul 2012 15:54:35 +0100
Received: from WDS-EXC2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4]) by wds-exc1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f%19]) with mapi; Fri, 20 Jul 2012 15:54:34 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: John Levine <johnl@taugh.com>
Thread-Topic: [weirds] Authentication Methods
Thread-Index: AQHNYzSVaT5sUZ9lAki+OrM4ADgQbpcurl0AgABdO4CAABfFgIAApk0AgABp6wCAAHk/gIABEaU1gAB3aYCAAAIWgA==
Date: Fri, 20 Jul 2012 14:54:33 +0000
Message-ID: <B412C3D4-FB26-41D3-80D1-D64DD4966E4D@nominet.org.uk>
References: <20120720144705.73747.qmail@joyce.lan>
In-Reply-To: <20120720144705.73747.qmail@joyce.lan>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <a9e1d74e-73cf-426a-b45d-204a68f56b0d>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:53:43 -0000

On 20 Jul 2012, at 15:47, John Levine wrote:

> OK.  How do you feel about oauth?

I'm not experienced in OAuth.  Is it suited for machine-to-machine authenti=
cation?

Ray


From carlosm3011@gmail.com  Fri Jul 20 08:03:02 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 021AA21F86A4 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 08:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6sYF5--W8IR5 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 08:03:01 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 12BDC21F86A1 for <weirds@ietf.org>; Fri, 20 Jul 2012 08:03:01 -0700 (PDT)
Received: by yhq56 with SMTP id 56so4461053yhq.31 for <weirds@ietf.org>; Fri, 20 Jul 2012 08:03:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=9MzVn7J/n0LEGj/FL74TubRJJhp/a7B5UYcXiO3i5Hw=; b=Dj5zYDbcEBH1ZdkbMTHp221zlJYV/4p3RVgQeM1Z8Gy665XUtTUWPHy6NfJP9XWPd4 ilrdox4RWslaXDWvzzbn5Np4gT7UzsJyNNnz5w5TH5I771nOTm754S0/UrdiggR98Y2/ W0+s+rti+pfR0cK1b+hPj8V14pXSYNrAWLUqc3YihYCkZlVUBbyuK4AUrCLp3DECB1DS AgYnQk6ZZfqt9KpF4sUNXOTQaCF0OAceepHEpvKY6anFHm3yqlBFpxddeohZqcScOBNz GYiDr2LxoXKd8VSIisCJraZ8BFA6CnBjPlkMl/rZ7YeXcZqL89dXKpnTyfF6tFYLq3ip i8Dg==
Received: by 10.236.79.74 with SMTP id h50mr5756909yhe.104.1342796637005; Fri, 20 Jul 2012 08:03:57 -0700 (PDT)
Received: from europa.local ([190.115.129.45]) by mx.google.com with ESMTPS id e24sm9903415yhh.4.2012.07.20.08.03.54 (version=SSLv3 cipher=OTHER); Fri, 20 Jul 2012 08:03:55 -0700 (PDT)
Message-ID: <50097358.4040107@gmail.com>
Date: Fri, 20 Jul 2012 11:03:52 -0400
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: weirds@ietf.org
References: <CC2E3BAC.33F74%chris@ausregistry.com.au> <AEFA87F9-347C-4C5D-ADE5-B1DE427DE2AD@arin.net>
In-Reply-To: <AEFA87F9-347C-4C5D-ADE5-B1DE427DE2AD@arin.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 15:03:02 -0000

Is it a requirement that a pure JavaScript implementation of a WEIRDS
client must  be possible? If so, we have a pretty strong restriction
that will limit what we can / cannot do.

I believe we should clarify this point before continuing the discussion.

On the other hand, how difficult / heavy to operate would it be to run a
'helper' webservice that basically gives the SRV record to those pesky
pure JS implementations ? Who would run such a service ? All queries /
answers would be very short, right ? And if the information resides in
the DNS, anyone could operate one of these services (i'm not making any
statements here, just popping questions up so we can discuss them)

Looking forward to Vancouver !

Carlos

On 7/19/12 11:22 AM, Andy Newton wrote:
> On Jul 19, 2012, at 8:36 AM, Chris Wright wrote:
>
>> Why not a DNS Resource Record that lives in the tld zone file? No need to
>> have IANA involved then and TLD manager can update as required.
>>
>> dig -t WEIRDS tad returns URL of weirds service
>>
>> Or we could potentially use existing records like SRV or NAPTR ?
> As previously discussed in this thread, many client implementations operate in an environment that does not have access to this type of information.
>
> -andy
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds



From ajs@anvilwalrusden.com  Fri Jul 20 08:30:51 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C6F221F8616 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 08:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.263
X-Spam-Level: 
X-Spam-Status: No, score=-1.263 tagged_above=-999 required=5 tests=[AWL=-0.423, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53HNm6L+qkcC for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 08:30:51 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 15BF321F849C for <weirds@ietf.org>; Fri, 20 Jul 2012 08:30:51 -0700 (PDT)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id E50F68A031 for <weirds@ietf.org>; Fri, 20 Jul 2012 15:31:46 +0000 (UTC)
Date: Fri, 20 Jul 2012 11:31:45 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: weirds@ietf.org
Message-ID: <20120720153144.GL3594@mail.yitter.info>
References: <20120720144705.73747.qmail@joyce.lan> <B412C3D4-FB26-41D3-80D1-D64DD4966E4D@nominet.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B412C3D4-FB26-41D3-80D1-D64DD4966E4D@nominet.org.uk>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 15:30:51 -0000

On Fri, Jul 20, 2012 at 02:54:33PM +0000, Ray Bellis wrote:
> 
> I'm not experienced in OAuth.  Is it suited for machine-to-machine authentication?

Why is that the only criterion?  For the kinds of problems law
enforcement people keep bringing up, they don't need
machine-to-machine things to work.  They need for a person to be able
to get all the information necessarty. OAuth would be an excellent
mechanism for that, because the WEIRDS provider could negotiate with
some law-enforcement authenticator, which would then hand the
necessary credentials to the WEIRDS service when a request was
inbound.  This puts the onus for vouching that a particular law
enforcement request is legitimate (along with the relevant paperwork,
logs, &c) onto the parties who can make that determination.  

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From johnl@iecc.com  Fri Jul 20 09:15:28 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 257F121F8616 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 09:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.138
X-Spam-Level: 
X-Spam-Status: No, score=-111.138 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zXr1Apo2UiBy for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 09:15:27 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 024B421F85F2 for <weirds@ietf.org>; Fri, 20 Jul 2012 09:15:26 -0700 (PDT)
Received: (qmail 210 invoked from network); 20 Jul 2012 16:16:22 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Jul 2012 16:16:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50098456.xn--hew.k1207; i=johnl@user.iecc.com; bh=bf6JZv5wtpdLtGjIiyb26NT5U1es/pvywu1bKmKbjs4=; b=fNKGloZEcV8okFE3S9/fuzl37tal6h4W2yAEbZLCYp3hYjmmy6ED/1is4mUrTa8DhAw+j7QkfoKKoAEEQzBw/lYoCMjD+MVG5b6aMGhJ3jTuteTW5NJLgUcfI7if+Kfjc2xqCEpPTX0PSnPUCqbx/x6AEK87VPReJMDh329PIWA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50098456.xn--hew.k1207; olt=johnl@user.iecc.com; bh=bf6JZv5wtpdLtGjIiyb26NT5U1es/pvywu1bKmKbjs4=; b=bVx6a3+YG5bQ7kncbI8OZ/yKmwf7vVqraKA2s2lRv4a1+f8BN6KbbJyuABKGJ/c1r+LDCBiyGo0BHz4C140s2o0XgxHSOfAWrnDQRtctEPsp1uWQFPr0ynj1ZdRgzQjWqEXESz0kfV9of4SKFQVL6f39dnn2SX4LDcOKcxcpytY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 20 Jul 2012 16:16:00 -0000
Message-ID: <20120720161600.98121.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <50097358.4040107@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: carlos@lacnic.net
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 16:15:28 -0000

>Is it a requirement that a pure JavaScript implementation of a WEIRDS
>client must  be possible? If so, we have a pretty strong restriction
>that will limit what we can / cannot do.

Given that Andy's told us that many, perhaps most, of the existing
users of the existing prototype are using Javascript, it'd be a cruel
joke to say that won't work any more.

>On the other hand, how difficult / heavy to operate would it be to run a
>'helper' webservice that basically gives the SRV record to those pesky
>pure JS implementations ?

Could you explain exactly how a "helper" that received an http query
from a web client and returned the hostname for the appropriate server
would be different from a top level WEIRDS server that received an http
query from a web client and returned the URL (including the hostname)
for the appropriate server?

R's,
John

From johnl@iecc.com  Fri Jul 20 09:16:04 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8521B21F8616 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 09:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.14
X-Spam-Level: 
X-Spam-Status: No, score=-111.14 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U+LMC7TyK+hj for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 09:16:04 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9E5CA21F85F2 for <weirds@ietf.org>; Fri, 20 Jul 2012 09:16:03 -0700 (PDT)
Received: (qmail 305 invoked from network); 20 Jul 2012 16:16:59 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Jul 2012 16:16:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5009847b.xn--btvx9d.k1207; i=johnl@user.iecc.com; bh=ioIoBpaxatIQgzAHCe3AvqiwDUvr+JN+W9L3Li41kq4=; b=ES7Rcdw3DXLu9XYqODIibwd6kRaIdeFapexL7mCQuY9w6TinSJ7GCe3CMwIPSUxd6zEu54vFIwi0+RalgTrGkYKVh6dbEzjvfZjlOKvE+kQhCoylu3/rO2Az84XdVIMdoyUrr88l5bX3nBkj5T6mjEk7+1HxGhWkMv56WsrK9Cc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5009847b.xn--btvx9d.k1207; olt=johnl@user.iecc.com; bh=ioIoBpaxatIQgzAHCe3AvqiwDUvr+JN+W9L3Li41kq4=; b=sLPrsyldIgkX5pRE1fAW8S8Fur3ph4+dMXkRnFdWv8Fb7hhMu9o8Hj6SIMZiHYtuXFtxXOTLWHfJikGhhiOFwvBodzyW6YHEfSR+4dlY1j5kxe9MwcootE2YPUgBM+qRIF215xFMNOHYcMQzYxBZKvFEJ8Ej4z2OajClWQGlTNQ=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 20 Jul 2012 16:16:37 -0000
Message-ID: <20120720161637.98307.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <B412C3D4-FB26-41D3-80D1-D64DD4966E4D@nominet.org.uk>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 16:16:04 -0000

>> OK.  How do you feel about oauth?
>
>I'm not experienced in OAuth.  Is it suited for machine-to-machine authentication?

That's all I've ever used it for, doing tweets from perl scripts.

R's,
John

From carlosm3011@gmail.com  Fri Jul 20 09:50:45 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF8C721F85D7 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 09:50:44 -0700 (PDT)
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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cmswIPmzZ0UR for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 09:50:44 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id A80C421F85D5 for <weirds@ietf.org>; Fri, 20 Jul 2012 09:50:44 -0700 (PDT)
Received: by yhq56 with SMTP id 56so4592504yhq.31 for <weirds@ietf.org>; Fri, 20 Jul 2012 09:51:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Yaud/KNVg9bJvP3tf9AtHonaowFDi/BaiiBL/U4G4lw=; b=O33RtGWU9VuWI7YQ96+iXe9kKO/RnN/5oSmw6boskd9gWZo66iwEwKONxIDNSGqzpx nWa2KIqpX3cNBfcqO/adPVkxXJKo0WNZ/zRk15l4l10MnvsJVkqjT1yNuA6Aqzc2aNK2 rSFOlpf1vV8dyzgsHn3gYu2BOAoSrVDqBIKulgESUkYYtQGRsxpZ9a8jfUN2yuf7DSJ9 LyxKP0KDxpblO5994RLxVRBgbKOk2nARmivZqx7sI8+DUn1YAO2GQs0Tt/IMcRQxq4JC ZRzCGQUXiYQmkyTSbG3EFIxoFLzUtPfukYzVXxML9eMtZErFTKtfzYfRVq+x0G4FDhPQ 4rfg==
Received: by 10.236.115.103 with SMTP id d67mr6063459yhh.103.1342803100874; Fri, 20 Jul 2012 09:51:40 -0700 (PDT)
Received: from europa.local ([190.115.129.45]) by mx.google.com with ESMTPS id y10sm9442981yhd.6.2012.07.20.09.51.38 (version=SSLv3 cipher=OTHER); Fri, 20 Jul 2012 09:51:39 -0700 (PDT)
Message-ID: <50098C98.9080805@gmail.com>
Date: Fri, 20 Jul 2012 12:51:36 -0400
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: weirds@ietf.org
References: <20120720161600.98121.qmail@joyce.lan>
In-Reply-To: <20120720161600.98121.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 16:50:45 -0000

Hi, see inline

--
Carlos Martinez-Cagnazzo
R+D Engineer
http://www.labs.lacnic.net

On 7/20/12 12:16 PM, John Levine wrote:
>> Is it a requirement that a pure JavaScript implementation of a WEIRDS
>> client must  be possible? If so, we have a pretty strong restriction
>> that will limit what we can / cannot do.
> Given that Andy's told us that many, perhaps most, of the existing
> users of the existing prototype are using Javascript, it'd be a cruel
> joke to say that won't work any more.
I don't think we're saying that their clients won't work anymore. The
queries will work as always.
>
>> On the other hand, how difficult / heavy to operate would it be to run a
>> 'helper' webservice that basically gives the SRV record to those pesky
>> pure JS implementations ?
> Could you explain exactly how a "helper" that received an http query
> from a web client and returned the hostname for the appropriate server
> would be different from a top level WEIRDS server that received an http
> query from a web client and returned the URL (including the hostname)
> for the appropriate server?
It would provide comparable service, and (hopefully) would provide a
more palatable approach to those folks who are not comfortable with the
idea of a single, top-level WEIRDS referral service. It would allow
bootstrapping the WEIRDS tree without relying on a centralized database.

As I mentioned in earlier emails, I originally wrote about a fully
hierarchical WEIRDS tree, but then I received some well fundamented
negative feedback on the idea.

regards

Carlos
>
> R's,
> John



From peter@denic.de  Fri Jul 20 09:59:42 2012
Return-Path: <peter@denic.de>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D15A21F85C2 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 09:59:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G6ntvUckNiEm for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 09:59:42 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::3]) by ietfa.amsl.com (Postfix) with ESMTP id C929221F857D for <weirds@ietf.org>; Fri, 20 Jul 2012 09:59:41 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.17]) by office.denic.de with esmtp  id 1SsGZB-00049v-Od; Fri, 20 Jul 2012 19:00:37 +0200
Received: from localhost by x27.adm.denic.de with local  id 1SsGZB-0003lF-LF; Fri, 20 Jul 2012 19:00:37 +0200
Date: Fri, 20 Jul 2012 19:00:37 +0200
From: Peter Koch <pk@DENIC.DE>
To: weirds@ietf.org
Message-ID: <20120720170037.GO24669@x28.adm.denic.de>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <002701cd6550$6c1a3ba0$444eb2e0$@cn> <B5F40D70-914D-4696-A6F6-A6C02E63F82B@nominet.org.uk> <F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net> <9C034D938509E4DDB82B536D@James-Galvin-2.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9C034D938509E4DDB82B536D@James-Galvin-2.local>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 16:59:42 -0000

On Fri, Jul 20, 2012 at 08:38:51AM -0400, Jim Galvin wrote:

> If I'm the server motivated by the policies that manage the information 
> I'm making available, I simply do whatever I have to do.  If all 
> authentication methods are "MAY" I choose the one or more that works 
> best for me.  Any client who wants my information will need to meet my 
> requirements.

this seems to confuse advice to implementers (opportunity to interoperate)
with advice to operators/service providers (operational/policy decision).

-Peter

From johnl@iecc.com  Fri Jul 20 11:03:00 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFF2711E8097 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 11:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.142
X-Spam-Level: 
X-Spam-Status: No, score=-111.142 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p4nh4FjGODYi for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 11:02:59 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC0E11E8099 for <weirds@ietf.org>; Fri, 20 Jul 2012 11:02:58 -0700 (PDT)
Received: (qmail 18595 invoked from network); 20 Jul 2012 18:03:54 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Jul 2012 18:03:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50099d8a.xn--btvx9d.k1207; i=johnl@user.iecc.com; bh=yAMwjBsI93crrg8JtvhYnU/2vFJBmZo/BeSjO2zQ73U=; b=Y+Gh0K9GTgTUn1iiw/OEJkGeGCcVpg6CRhVa/thHmVyA3qGH2v53ff/nPdjp1lsLV+uXbrKBYd83Td5SQTUFM+0yN04V8vhjXO8yQbxzlNdJPhAyN/DXl7KA+WCjku+UhZKBheuXpb+P4MkA1owESR4xhb0Ef2vWdtVD1momGmY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50099d8a.xn--btvx9d.k1207; olt=johnl@user.iecc.com; bh=yAMwjBsI93crrg8JtvhYnU/2vFJBmZo/BeSjO2zQ73U=; b=Z000WrxtYxbdlOqQv5b6d/QlYS1ykSV1we8GediJX09ZrBIpW/sCBTppQ5yeU0kGUKYfe4kjiffxPafbspDlrm+utA9tMXgj8eYcOtcuxDCAKwlm22V+M4SkxLfWj9vwcCcDE0yWjoKAD31NChI6Grf579LvUelxZZsOzB/jBJI=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 20 Jul 2012 18:03:31 -0000
Message-ID: <20120720180331.27999.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <50098C98.9080805@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: carlos@lacnic.net
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 18:03:00 -0000

>> Could you explain exactly how a "helper" that received an http query
>> from a web client and returned the hostname for the appropriate server
>> would be different from a top level WEIRDS server that received an http
>> query from a web client and returned the URL (including the hostname)
>> for the appropriate server?
>It would provide comparable service, and (hopefully) would provide a
>more palatable approach to those folks who are not comfortable with the
>idea of a single, top-level WEIRDS referral service. It would allow
>bootstrapping the WEIRDS tree without relying on a centralized database.

I'm still not getting this.  How is the helper server not a
centralized database abd a single top-level referral service?  All
bajillion javascript clients would hit it for every query.  Probably
other clients, too, if they have cruddy DNS client libraries that like
the ones in Javascript.

>As I mentioned in earlier emails, I originally wrote about a fully
>hierarchical WEIRDS tree, but then I received some well fundamented
>negative feedback on the idea.

Right, it has horrible scaling problems.  That's why we want to put
the bootstrap in the DNS, which we know can handle the load.  Needless
to say, putting it in the DNS means that the clients have to make
their own DNS queries.  If they all go through a "helper", the helper
is the bottleneck with the scaling problems.

Conversely, what's the advantage of a helper over CNAMEs in tld.weirds.arpa?

R's,
John

From carlosm3011@gmail.com  Fri Jul 20 11:22:02 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6FC511E80BE for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 11:22:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uSiyxoHDMV+w for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 11:22:00 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 77A5811E80BD for <weirds@ietf.org>; Fri, 20 Jul 2012 11:22:00 -0700 (PDT)
Received: by yhq56 with SMTP id 56so4692945yhq.31 for <weirds@ietf.org>; Fri, 20 Jul 2012 11:22:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=nVBIvaGJK7til9IOSUlc1fd5JC1bo8en5UkrjX9Orbw=; b=yuT03SDnb+WfxwuVhXN6p4o7XXxcMVbHkeMuAWdPiajWbnpwNsTCuAiSD0BRiUTW4r XM85RatTcjKIAGULRNbmNE+SHmXYkeAC1HFo93P2kkpYegh6lJxykJBZoIJIP8oI2Ave yPdUO4gzf7T8Oer1q5T6d57rD4uEYAWLRe4HgmdwJzOkOCGuEX4XGQWXhjikDW8z9U8I yHCOMbgS0bttl5bL01awECyDvj1VIzqeWfaVWiVPsWbtuMomGlv24yr7/eKup4yUNIpQ O3aPJlCXMrHO3TsjHsF2crpavZDp9t8i9E3k9/8kk8dFhr2ZS9J8oZScEpGgKaKLiTZ3 CvEg==
Received: by 10.101.180.40 with SMTP id h40mr1929725anp.47.1342808576751; Fri, 20 Jul 2012 11:22:56 -0700 (PDT)
Received: from europa.local ([190.115.129.45]) by mx.google.com with ESMTPS id l13sm5634622ann.2.2012.07.20.11.22.55 (version=SSLv3 cipher=OTHER); Fri, 20 Jul 2012 11:22:55 -0700 (PDT)
Message-ID: <5009A1FD.3030806@gmail.com>
Date: Fri, 20 Jul 2012 14:22:53 -0400
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
References: <20120720180331.27999.qmail@joyce.lan>
In-Reply-To: <20120720180331.27999.qmail@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: carlos@lacnic.net, weirds@ietf.org
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 18:22:02 -0000

Hi,

On 7/20/12 2:03 PM, John Levine wrote:
>>> Could you explain exactly how a "helper" that received an http query
>>> from a web client and returned the hostname for the appropriate server
>>> would be different from a top level WEIRDS server that received an http
>>> query from a web client and returned the URL (including the hostname)
>>> for the appropriate server?
>> It would provide comparable service, and (hopefully) would provide a
>> more palatable approach to those folks who are not comfortable with the
>> idea of a single, top-level WEIRDS referral service. It would allow
>> bootstrapping the WEIRDS tree without relying on a centralized database.
> I'm still not getting this.  How is the helper server not a
> centralized database abd a single top-level referral service?  All
> bajillion javascript clients would hit it for every query.  Probably
> other clients, too, if they have cruddy DNS client libraries that like
> the ones in Javascript.
The 'helper' would not have a database, would just perform DNS queries
and return the results in some format to be agreed.
>
>> As I mentioned in earlier emails, I originally wrote about a fully
>> hierarchical WEIRDS tree, but then I received some well fundamented
>> negative feedback on the idea.
> Right, it has horrible scaling problems.  That's why we want to put
> the bootstrap in the DNS, which we know can handle the load.  Needless
> to say, putting it in the DNS means that the clients have to make
> their own DNS queries.  If they all go through a "helper", the helper
> is the bottleneck with the scaling problems.
'My' helper so to speak would do very little, and there could be many of
them (since there is no database needed). So I guess it would be
possible to operate such a service in a highly distributed way.
>
> Conversely, what's the advantage of a helper over CNAMEs in tld.weirds.arpa?
Maybe none other than the more refined semantics of the SRV/NAPTR
records. Can you provide some pseudo code of how a JS client would use
these CNAMEs ?

cheers!

Carlos
>
> R's,
> John
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds



From fneves@registro.br  Fri Jul 20 11:52:39 2012
Return-Path: <fneves@registro.br>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE62511E807F for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 11:52:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XOJqwEj8JfOl for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 11:52:38 -0700 (PDT)
Received: from clone.registro.br (clone.registro.br [IPv6:2001:12ff:0:2::4]) by ietfa.amsl.com (Postfix) with ESMTP id 077A011E8099 for <weirds@ietf.org>; Fri, 20 Jul 2012 11:52:38 -0700 (PDT)
Received: by clone.registro.br (Postfix, from userid 1000) id B8EA7E0467; Fri, 20 Jul 2012 15:53:31 -0300 (BRT)
Date: Fri, 20 Jul 2012 15:53:31 -0300
From: Frederico A C Neves <fneves@registro.br>
To: John Levine <johnl@taugh.com>
Message-ID: <20120720185331.GA98395@registro.br>
References: <20120720115706.GG85645@registro.br> <20120720144948.74504.qmail@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120720144948.74504.qmail@joyce.lan>
Cc: weirds@ietf.org
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 18:52:39 -0000

On Fri, Jul 20, 2012 at 02:49:48PM -0000, John Levine wrote:
> >> Two points.  One is that rDNS zones have never had anything in them other 
> >> than NS, CNAME, and PTR.  You'd hope that nothing strange would happen if 
> >> you put in other stuff, but I wouldn't want to try it without some 
> >> significant testing first.
> >
> >This is a red herring, these zones are not special and any RR
> >supported or not (3597) works just fine. The IP -> ARPA conversion is
> >done at the DNS client code or stub resolver library level.
> 
> We all know that's the theory.  Since there have never been A or
> SRV records in rDNS zones, how much are you willing to wager that

This is not true RIR have seen in the past requests for glue records
at delegation point on the basis that the reverse tree doesn't depend
on other zones. 

Another prof is that recently we've seen ip6.arpa and in-addr.arpa
delegated to servers below in-addr-servers.arpa and ip6-servers.arpa.

There is nothing special on the protocol or on resolvers libraries
regarding this zones.

> all the existing client libraries will properly disregard them?
>
> >So that said _weirds._tcp.TLD IN A works just fine for a limited
> >bootstrap as long as we could live with a fixed the port.
> 
> Since that's not a valid hostname, I think I can pretty much
> guarantee that it won't work from Javascript.

Right ECMA-262 point to 2396 definition clearly disallow this but
anyway I preferer this as distributed as possible, so we could use a
namespace hack, to prevent namespace conflicts, ala the idna prefix,
ws--weirds.TLD A, instead of a new central database published at an
arpa zone.

> R's,
> John

Regards,
Fred

From johnl@taugh.com  Fri Jul 20 11:54:09 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E6A511E80BD for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 11:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level: 
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cBOyFrMVs7dh for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 11:54:09 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE9A11E807F for <weirds@ietf.org>; Fri, 20 Jul 2012 11:54:08 -0700 (PDT)
Received: (qmail 26744 invoked from network); 20 Jul 2012 18:55:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=6877.5009a988.k1207; bh=2LNZSMM1RRm3xEofg2Qiqbyo7oExDjHZZwMW406BxnU=; b=YoeI+x30tIIZUORSUJPJAD+HurfCm9acIMvg/rgcOSJJZgvlbUlXn7Fvbzye0uDlFNuwWgdNqIa1iFtX+vN5Pm1UZFEtmTGnhVtboKCuhvBCFVuZrmDEzC8BSKigIYEG+sUEwZXJNYFHkIJk+ZNO5VbbkSLC8/RGI4g6vEM2OOU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=6877.5009a988.k1207; bh=2LNZSMM1RRm3xEofg2Qiqbyo7oExDjHZZwMW406BxnU=; b=O5mAZYe2b7teLr9Pj2b9/P5COq+lY01sttn2U+B/NSLrZBAFPdWqg4pGJJOC7nKIxQql0wiUbqPenzkDOj+x1Jg0fyzDFgXWS8O5pgSPUk7KAO8xx5XeygK5i+ePpROZYGbdYXyLguREX4VIdafJrmxgljVekwrY0xPJ4BRew6U=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 20 Jul 2012 18:54:42 -0000
Date: 20 Jul 2012 14:55:04 -0400
Message-ID: <alpine.BSF.2.00.1207201451500.9846@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: carlos@lacnic.net
In-Reply-To: <5009A1FD.3030806@gmail.com>
References: <20120720180331.27999.qmail@joyce.lan> <5009A1FD.3030806@gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: weirds@ietf.org
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 18:54:09 -0000

> Maybe none other than the more refined semantics of the SRV/NAPTR
> records. Can you provide some pseudo code of how a JS client would use
> these CNAMEs ?

To do a lookup for info about xyz.tld, it does a simple string 
transformation to create the URL http://tld.weirds.arpa/xyz.tld/whatever 
(where the xyz.tld/whatever is the restful part of the query) and fetches 
it.  This requires that the server answer on port 80, which I do not think 
is an unreasonable restriction.  If the server would prefer https, it can 
return a redirect to that.  If it's delegated that domain to another 
server, it returns a redirect to the other server.

IP lookups would do roughly the same thing, e.g., to look up information 
about 11.22.33.44 it would look up

http://11.weirds.arpa/11.22.33.44/whatever

Really, this isn't complicated.  It is true that SRV and NAPTR would allow 
us to introduce a great deal of added complexity into clients, but I see 
no benefit from that in this case where there is no installed base of 
WEIRDS server that we have to work around.

R's,
John



From andy@arin.net  Fri Jul 20 11:57:57 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88EB711E80BE for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 11:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.287
X-Spam-Level: 
X-Spam-Status: No, score=-2.287 tagged_above=-999 required=5 tests=[AWL=-0.288, BAYES_00=-2.599, J_CHICKENPOX_64=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B+OwiN8yIn1S for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 11:57:56 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 9801111E807F for <weirds@ietf.org>; Fri, 20 Jul 2012 11:57:55 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id B4B2F1654A7; Fri, 20 Jul 2012 14:58:51 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp1.arin.net (Postfix) with ESMTP id 573B91654A4; Fri, 20 Jul 2012 14:58:51 -0400 (EDT)
Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Fri, 20 Jul 2012 14:58:25 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0298.004; Fri, 20 Jul 2012 14:58:44 -0400
From: Andy Newton <andy@arin.net>
To: "weirds@ietf.org" <weirds@ietf.org>
Thread-Topic: [weirds] the bootstrap problem: a DNS compromise
Thread-Index: AQHNZqmvfV2e+41qg06WhduUnVTZ7A==
Date: Fri, 20 Jul 2012 18:58:44 +0000
Message-ID: <FCC29D58-4A70-42C2-BD2B-BEA7C8B11F27@arin.net>
References: <20120720043737.60219.qmail@joyce.lan>
In-Reply-To: <20120720043737.60219.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.1.56]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <527A736F384B1542923813AE834B45E9@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John Levine <johnl@taugh.com>
Subject: Re: [weirds] the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 18:57:57 -0000

Let me propose a compromise on the DNS bootstrapping. It requires a bit mor=
e work of the zone maintenance by IANA, but supports both the clients with =
basic name resolution capabilities and those with advanced resolution capab=
ilities.

The current CNAME proposal is to allow RESTful Whois service operators to r=
egister CNAME records under weirds.arpa (or similar). For example, com.weir=
ds.arpa could have a CNAME pointing to VeriSign's shiny new service. If the=
 powers-that-be allow it, John could have ny.us.weirds.arpa CNAME records r=
egistered.

Here is the compromise:

Instead of using CNAME records, we allow the registration of A, AAAA, and R=
FC 4848 u-flag constrained NAPTR records. A service operator would have to =
register all three types. But that would allow bootstrapping with both basi=
c resolution (using the A/AAAA records) and advanced resolution (using the =
NAPTR records).

And note, I've restricted the NAPTR registration to RFC 4848 compliant usin=
g the u-flag only.

-andy=

From sm@resistor.net  Fri Jul 20 13:01:44 2012
Return-Path: <sm@resistor.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E69C311E80E7 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 13:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H8VJ16mLBvVV for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 13:01:40 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9292F11E80EE for <weirds@ietf.org>; Fri, 20 Jul 2012 13:01:20 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q6KK2Aui027350; Fri, 20 Jul 2012 13:02:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1342814535; bh=/dEa1h6z6UrP4QzXbjPcERyYY2vxwLtnmUYZQkA55S0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=q5/aKxYD035ry0Z3R6FnuTePCSZCfF6cVT1MEC6EtgruOjhLIYS3LUCc0EmDFUals 4rduOtastArwK/RqFLsJk7r9tKSQwHGxSqLRnWZDRORNQha4pfLBIcL5yo8iTv0Tep LRwXeQ/bnrgZfPdeYKdEZeiitBUPVzh18PG+Uo+U=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1342814535; i=@resistor.net; bh=/dEa1h6z6UrP4QzXbjPcERyYY2vxwLtnmUYZQkA55S0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hJYRQTYCQRyUr1MqWINnx30QsvXLP3YcpvsLUF9Ow2jFnAOMfFyCPo+rAKxi4EMHB 8xCdlZcn2i9//FQCgsaFcYNgL0ULTdf4zzqfZBRm/mbL4JVdxodgJlX36cD9kcWkJx EMA65tBOeaOppoFRK/QpQy5QGdYApjqhztYpjYJI=
Message-Id: <6.2.5.6.2.20120720121817.05ba5358@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 20 Jul 2012 13:02:05 -0700
To: Web Extensible Internet Registration Data Service Working Group <weirds@ietf.org>
From: SM <sm@resistor.net>
In-Reply-To: <9C034D938509E4DDB82B536D@James-Galvin-2.local>
References: <20120718142657.26067.qmail@joyce.lan> <8152AEFC-9398-47E7-9DEE-A662F0E64E28@arin.net> <002701cd6550$6c1a3ba0$444eb2e0$@cn> <B5F40D70-914D-4696-A6F6-A6C02E63F82B@nominet.org.uk> <F2D61449-F5B4-44E4-B0A3-630B9E47FBD0@arin.net> <9C034D938509E4DDB82B536D@James-Galvin-2.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [weirds] Authentication Methods
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 20:01:45 -0000

At 05:38 20-07-2012, Jim Galvin wrote:
>Could the differentiated access be one of two things: here's some 
>public information I'll give to anybody versus if you want complete 
>or specific information you have to provide the right credentials.
>
>If I'm the server motivated by the policies that manage the 
>information I'm making available, I simply do whatever I have to 
>do.  If all authentication methods are "MAY" I choose the one or 
>more that works best for me.  Any client who wants my information 
>will need to meet my requirements.
>
>If I'm the user behind the client, I have to choose to use a client 
>that supports the credentials I need to have available.  That could 
>be no authentication is supported, in which case I get only the 
>"public" information.
>
>It was Ray Bellis who pointed out that there are so many HTTP 
>Authentication Methods to choose from.  Why is it our job to fix 
>that? If we're building this on top of HTTP then let's leave that 
>problem for HTTP "to fix".
>
>I agree with Andrew Sullivan who said make everything a "MAY".  I 
>think our energy is better directed towards being able to respond 
>with minimal information at all times or perhaps a "standard" 
>response of some sort that includes a referral or at least a 
>designation of the credentials you need and where you can go to get 
>instructions on obtaining them.

In an ideal world one would use a "MAY" and leave it to people to go 
and write code and come back.    Options and Recommendations are then 
fine tuned and you end with a standard.  That line may also apply for 
"differential service levels to different classes of users".  The 
questions one might ask are:

   (a) Does differential service levels require interoperability?

   (b) Does different classes of users require interoperability?

The above does not preclude applying different policies.  A server 
gets to do whatever it wants to do.  If client X has to meet 
different requirements for servers D to Z, one might as well forget 
about interoperability.  It might require less energy to sort out the 
minimal information than to find answers to the above questions.

Regards,
-sm 


From johnl@iecc.com  Fri Jul 20 13:40:47 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86DC411E8080 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 13:40:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.843
X-Spam-Level: 
X-Spam-Status: No, score=-110.843 tagged_above=-999 required=5 tests=[AWL=-0.244, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, J_CHICKENPOX_64=0.6, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ga0vFD0FhjmY for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 13:40:46 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id C4B8611E8088 for <weirds@ietf.org>; Fri, 20 Jul 2012 13:40:45 -0700 (PDT)
Received: (qmail 43146 invoked from network); 20 Jul 2012 20:41:40 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Jul 2012 20:41:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5009c284.xn--btvx9d.k1207; i=johnl@user.iecc.com; bh=RxtqwszHGRUQe3k8A+e5EfTs10Ry8+90KLQLSjtdKnY=; b=Zuxok4DdfbLmEWS7OZhDDSZvhPtcaYkA+WMi8Me68S7V+92RN6Wn6gNoGznRo85JkfZn3dJ67KYmWtp66hR85fc+sNWRCK/5gGyI21xKILiTAdmFqgm3oJZ4GQdRTmBiajOq+AkqgU22tVs0s2kRiooCD62Dyj0hAK+PSBjPxmk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5009c284.xn--btvx9d.k1207; olt=johnl@user.iecc.com; bh=RxtqwszHGRUQe3k8A+e5EfTs10Ry8+90KLQLSjtdKnY=; b=eMsfzY7VKc6C+yWRuKVii5NhqrQ/DMc2pk9xdIH6iw/8B32ygzZVeEcSkkhtgZQHAdEcOZTEk9S4dptYAXoOHBSDRmFGBflTkw26ZRJjmLBMdOClnigdjoyS45yZ6gE+53tmFpat/gfqfTejlVvSZmKwXXEogXH7Uphb3tYkKrA=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 20 Jul 2012 20:41:18 -0000
Message-ID: <20120720204118.70594.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <FCC29D58-4A70-42C2-BD2B-BEA7C8B11F27@arin.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 20:40:47 -0000

Sorry to seem intransigent, but this still seems to miss some
important points.

My theory is that we need enough of a bootstrap that clients can find
an initial server that is reasonably close to the final server.  By
reasonably close, I mean that it's likely to be the the final server,
or run by the organization that's delegated a subtree to the final
server and so knows where it is.

I'm also concerned about load management.  One WHOIS server (.COM and
.NET) gets 200 queries/second while others like .INT and .MUSEUM
probably don't get 200 queries/week.  Anything that's going to be in
the path to the 200 q/s server has to be run by the same people who
run that server, since they're already prepared to deal with the load,
or else we need a good reason to think that the load on the
intermediate steps will be lower, with the main reason being DNS
caches.

With that in mind:

>The current CNAME proposal is to allow RESTful Whois service operators to
>register CNAME records under weirds.arpa (or similar). For example,
>com.weirds.arpa could have a CNAME pointing to VeriSign's shiny new service.
>If the powers-that-be allow it, John could have ny.us.weirds.arpa CNAME
>records registered.

That last bit is no good, that blows up the DNS caches.  I
deliberately proposed only looking up the last component of a domain
name or the first octet of the IPv4 address, because that will cache
well.  No matter how many .COM names you look up, the client fetches
com.weirds.arpa once from the .arpa servers, and thereafter from the
cache.

The delegation structure of DNS names is extremely irregular.  In my
case, for example, foo.watkins-glen.ny.us would be delegated to me,
but foo.ithaca.ny.us is handled directly by Neustar, with the reasons
for each delegation or non-delegation lost in the mists of history.
In .CA, most names are registered with CIRA at the second level
(foo.ca), but there are plenty at the third (foo.on.ca) and a fair
number at the fourth (foo.toronto.on.ca.)  This is widespread in
ccTLDs and in a few gTLDs like .name.

If you expect to find delegations below the top level via the DNS,
you're pretty much requiring that every WEIRDS query start with a
lookup of the full name in .arpa, which isn't going to cache.  It also
asks the TLDs to publish their delegation tree in the DNS which I
suspect many won't want to do.

I think looking up the first component will get you close enough. (And
I hereby withdraw my proposal to look up the first six digits of IPv6
addresses, see below.)

>Instead of using CNAME records, we allow the registration of A, AAAA, and RFC
>4848 u-flag constrained NAPTR records.

Nope, breaks load management.  The aforementioned 200 q/s WHOIS server
is actually many different servers with different IP addresses.  Look
up whois.crsnic.net or whois.verisign-grs.com and you'll find six name
servers that return a rotating set of A records with 1 second TTL for
the WHOIS servers.  That works fine with a CNAME, but not at all if
you demand that they import the A records into .arpa.  The A records
for the whois servers don't cache, but that's Verisign's decision and
they're bearing the load themselves.

I just don't see the advantage of making the DNS bootrap more
complicated than a CNAME for the first component, and a lot of
disadvantages.

R's,
John

PS: Oh, yeah, about IPv6, with its irregular delegation structure from
IANA.  If your client doesn't happen to have the IANA delegation table
handy it just queries the closest RIR, and each RIR knows how to find
the others.  Given that there are only five RIRs, and the IPv6
delegation table contains only 37 entries and hasn't added a new entry
since 2006, I think that for IPv6, that's reasonable.  We can say that
high volume query clients SHOULD use the table to select a server, and
SHOULD download a new copy of it every year, just in case.

From andy@arin.net  Fri Jul 20 14:03:17 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A46FC21F84C4 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 14:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.277
X-Spam-Level: 
X-Spam-Status: No, score=-2.277 tagged_above=-999 required=5 tests=[AWL=-0.278, BAYES_00=-2.599, J_CHICKENPOX_64=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xilz9Fnje0hz for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 14:03:16 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9C121F848B for <weirds@ietf.org>; Fri, 20 Jul 2012 14:03:16 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id 1DA141654C6; Fri, 20 Jul 2012 17:04:13 -0400 (EDT)
Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp1.arin.net (Postfix) with ESMTP id 2997D1654C2; Fri, 20 Jul 2012 17:04:12 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.283.3; Fri, 20 Jul 2012 17:03:49 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Fri, 20 Jul 2012 17:04:11 -0400
From: Andy Newton <andy@arin.net>
To: John Levine <johnl@taugh.com>
Thread-Topic: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
Thread-Index: AQHNZrgkY5OCIYwPw0C8kEn5i0xCKpcy7AaA
Date: Fri, 20 Jul 2012 21:04:09 +0000
Message-ID: <33B293F8-4285-4C28-942D-29F7EAFD10CB@arin.net>
References: <20120720204118.70594.qmail@joyce.lan>
In-Reply-To: <20120720204118.70594.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.1.56]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6813119EDBE55A449F96FC3587F702D8@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 21:03:17 -0000

On Jul 20, 2012, at 4:41 PM, John Levine wrote:

> With that in mind:
>=20
>> The current CNAME proposal is to allow RESTful Whois service operators t=
o
>> register CNAME records under weirds.arpa (or similar). For example,
>> com.weirds.arpa could have a CNAME pointing to VeriSign's shiny new serv=
ice.
>> If the powers-that-be allow it, John could have ny.us.weirds.arpa CNAME
>> records registered.
>=20
> That last bit is no good, that blows up the DNS caches.  I
> deliberately proposed only looking up the last component of a domain
> name or the first octet of the IPv4 address, because that will cache
> well.  No matter how many .COM names you look up, the client fetches
> com.weirds.arpa once from the .arpa servers, and thereafter from the
> cache.

Ok. I hadn't quite digested that point.

> The delegation structure of DNS names is extremely irregular.  In my
> case, for example, foo.watkins-glen.ny.us would be delegated to me,
> but foo.ithaca.ny.us is handled directly by Neustar, with the reasons
> for each delegation or non-delegation lost in the mists of history.
> In .CA, most names are registered with CIRA at the second level
> (foo.ca), but there are plenty at the third (foo.on.ca) and a fair
> number at the fourth (foo.toronto.on.ca.)  This is widespread in
> ccTLDs and in a few gTLDs like .name.
>=20
> If you expect to find delegations below the top level via the DNS,
> you're pretty much requiring that every WEIRDS query start with a
> lookup of the full name in .arpa, which isn't going to cache.  It also
> asks the TLDs to publish their delegation tree in the DNS which I
> suspect many won't want to do.
>=20
> I think looking up the first component will get you close enough. (And
> I hereby withdraw my proposal to look up the first six digits of IPv6
> addresses, see below.)

I'm fine with "close enough" in the bootstrap process.

>> Instead of using CNAME records, we allow the registration of A, AAAA, an=
d RFC
>> 4848 u-flag constrained NAPTR records.
>=20
> Nope, breaks load management.  The aforementioned 200 q/s WHOIS server
> is actually many different servers with different IP addresses.  Look
> up whois.crsnic.net or whois.verisign-grs.com and you'll find six name
> servers that return a rotating set of A records with 1 second TTL for
> the WHOIS servers.  That works fine with a CNAME, but not at all if
> you demand that they import the A records into .arpa.  The A records
> for the whois servers don't cache, but that's Verisign's decision and
> they're bearing the load themselves.

I didn't mean to imply just one A or AAAA. They could register multiple.

> I just don't see the advantage of making the DNS bootrap more
> complicated than a CNAME for the first component, and a lot of
> disadvantages.

Remember, this is one of those things we call a "compromise". We know we ha=
ve one when nobody is completely satisfied with the solution.

> R's,
> John
>=20
> PS: Oh, yeah, about IPv6, with its irregular delegation structure from
> IANA.  If your client doesn't happen to have the IANA delegation table
> handy it just queries the closest RIR, and each RIR knows how to find
> the others.  Given that there are only five RIRs, and the IPv6
> delegation table contains only 37 entries and hasn't added a new entry
> since 2006, I think that for IPv6, that's reasonable.  We can say that
> high volume query clients SHOULD use the table to select a server, and
> SHOULD download a new copy of it every year, just in case.

I'm fine with this. Not only does that happen with IPv6 today, it also happ=
ens with the much more common IPv4 queries.

-andy


From sm@resistor.net  Fri Jul 20 14:25:29 2012
Return-Path: <sm@resistor.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D334121F849D for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 14:25:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P3napC94jxNi for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 14:25:25 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E3DE121F847E for <weirds@ietf.org>; Fri, 20 Jul 2012 14:25:24 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q6KLQENg015586 for <weirds@ietf.org>; Fri, 20 Jul 2012 14:26:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1342819578; bh=pTJB9hilHxTm+W8oact5ikZgza47jTFWqW4x8MSaM2o=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=hOL/YvZ8q9HW2IDWFvU5Eb2DpB6u0ecOkV6QBZucaLjR/feZM9zlAtUnFgLzcwE4b AebNbSVLDCOsSXkxCZak/ZnC2JHFw3LqZlKfxPB5bVkRVmmn/7bTifJW9cpJn7jX5Q rUVYnvW3jT5AfSXSXbKRhfE9ZnFFOWh1JsHEYCtI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1342819578; i=@resistor.net; bh=pTJB9hilHxTm+W8oact5ikZgza47jTFWqW4x8MSaM2o=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=hqrUjIO+piRO5XWVZbgzdzteZaHVobG/ULgV49nKIZdhEKUqzt5SStGc3UvWRYVGN ahRPpR8ttqOi5d71IwKqRjH+S/9T/VuWr/kvkoo45QAxMPS1qroGPc1dgnYZbY34y5 Pmuy1XDwEJijGNG5HYjQqHEfHmCQ1TsyvVL/bXas=
Message-Id: <6.2.5.6.2.20120720135931.086fce20@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 20 Jul 2012 14:26:10 -0700
To: weirds@ietf.org
From: SM <sm@resistor.net>
In-Reply-To: <FCC29D58-4A70-42C2-BD2B-BEA7C8B11F27@arin.net>
References: <20120720043737.60219.qmail@joyce.lan> <FCC29D58-4A70-42C2-BD2B-BEA7C8B11F27@arin.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [weirds] the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 21:25:30 -0000

At 11:58 20-07-2012, Andy Newton wrote:
>Here is the compromise:
>
>Instead of using CNAME records, we allow the registration of A, 
>AAAA, and RFC 4848 u-flag constrained NAPTR records. A service 
>operator would have to register all three types. But that would 
>allow bootstrapping with both basic resolution (using the A/AAAA 
>records) and advanced resolution (using the NAPTR records).

I don't think that providing two ways to do the same things is the 
better answer.

Regards,
-sm 


From johnl@taugh.com  Fri Jul 20 14:38:08 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60CDE21F8513 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 14:38:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.594
X-Spam-Level: 
X-Spam-Status: No, score=-2.594 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id grLO9A2VHKUP for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 14:38:07 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 69B7021F84F3 for <weirds@ietf.org>; Fri, 20 Jul 2012 14:38:07 -0700 (PDT)
Received: (qmail 51453 invoked from network); 20 Jul 2012 21:39:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=c8fc.5009cff7.k1207; bh=KTEtwfUur3yGS5iF8IhCFiOqyogV6yvYyETwTKrswf4=; b=JjtAdCiFuSRcZBTisDQJ8/iA9U+iTRcpP+KFb7MZ+uSyYjW+1+kqdlTgDXUoqDXj6DPBQJrBY1LDTYObrK3fLEOgZfMuSDU9tRRPkUpRz/5rBcSDBU1s/PMi+urVAQlBd6rd9RfvQLLcv+M7bLP5lu4S4q9JkYdpgdYNZHztH6Q=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=c8fc.5009cff7.k1207; bh=KTEtwfUur3yGS5iF8IhCFiOqyogV6yvYyETwTKrswf4=; b=KZWWYAoRDdbdBJyQumUN3wZCnkVnNi/XfRwezjbvUxe/Q6RT0V80Dw9Xc8/hv6gTvYEnXRGtVNxuNuwnzJpL0xwXvooRsSZL2/h/+XyeumUMR8l1NaUPSrciku2dmlalWMH/uOKqm03LCB0TlptRHVCFjSzS+BfpGtIhnFq3UP8=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 20 Jul 2012 21:38:41 -0000
Date: 20 Jul 2012 17:39:03 -0400
Message-ID: <alpine.BSF.2.00.1207201734160.82811@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Andy Newton" <andy@arin.net>
In-Reply-To: <33B293F8-4285-4C28-942D-29F7EAFD10CB@arin.net>
References: <20120720204118.70594.qmail@joyce.lan> <33B293F8-4285-4C28-942D-29F7EAFD10CB@arin.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 21:38:08 -0000

> I didn't mean to imply just one A or AAAA. They could register multiple.

Not the same thing.  Verisign is handing out a different A record with a 
one second TTL for each DNS lookup, presumably doing load balancing to 
send traffic to less busy servers.  As I said, works great with a CNAME, 
not with imported A's.

What's the advantage of importing A's rather than using a CNAME?  The 
CNAMEs should cache well, after all, and they let the server operators to 
do internal reconfiguration without needing to involve IANA.

>> I just don't see the advantage of making the DNS bootrap more
>> complicated than a CNAME for the first component, and a lot of
>> disadvantages.
>
> Remember, this is one of those things we call a "compromise". We know we have one when nobody is completely satisfied with the solution.

I'm not opposed to compromises, but I'm still not seeing any benefit at 
all from more complicated proposals.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From andy@arin.net  Fri Jul 20 15:14:48 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 860A521F8476 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 15:14:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEXxcaEJ0HoG for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 15:14:48 -0700 (PDT)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id C4C4911E808C for <weirds@ietf.org>; Fri, 20 Jul 2012 15:14:47 -0700 (PDT)
Received: by smtp1.arin.net (Postfix, from userid 323) id 87A601654B8; Fri, 20 Jul 2012 18:15:34 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp1.arin.net (Postfix) with ESMTP id 0DEF51654AE; Fri, 20 Jul 2012 18:15:34 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Fri, 20 Jul 2012 18:15:01 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Fri, 20 Jul 2012 18:15:20 -0400
From: Andy Newton <andy@arin.net>
To: John R Levine <johnl@taugh.com>
Thread-Topic: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
Thread-Index: AQHNZrgkY5OCIYwPw0C8kEn5i0xCKpcy7AaAgAAJwYCAAAoigA==
Date: Fri, 20 Jul 2012 22:15:20 +0000
Message-ID: <A747D5D0-D08D-4E64-A5C9-DB59D2D1420E@arin.net>
References: <20120720204118.70594.qmail@joyce.lan> <33B293F8-4285-4C28-942D-29F7EAFD10CB@arin.net> <alpine.BSF.2.00.1207201734160.82811@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1207201734160.82811@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.149.252.97]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <678DA4A43B0AFE439887CBF6D1577D1C@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 22:14:48 -0000

On Jul 20, 2012, at 5:39 PM, John R Levine wrote:

>> I didn't mean to imply just one A or AAAA. They could register multiple.
>=20
> Not the same thing.  Verisign is handing out a different A record with a =
one second TTL for each DNS lookup, presumably doing load balancing to send=
 traffic to less busy servers.  As I said, works great with a CNAME, not wi=
th imported A's.

ah!

> What's the advantage of importing A's rather than using a CNAME?  The CNA=
MEs should cache well, after all, and they let the server operators to do i=
nternal reconfiguration without needing to involve IANA.

The reason for A/AAAA is because CNAME will not co-habitate with NAPTR or a=
ny other records on the same name. A fix to that is to use one name for CNA=
ME and another for NAPTR.

>>> I just don't see the advantage of making the DNS bootrap more
>>> complicated than a CNAME for the first component, and a lot of
>>> disadvantages.
>>=20
>> Remember, this is one of those things we call a "compromise". We know we=
 have one when nobody is completely satisfied with the solution.
>=20
> I'm not opposed to compromises, but I'm still not seeing any benefit at a=
ll from more complicated proposals.

Honestly, if we have to do either "basic" or "advanced" and cannot do a com=
promise, I lean toward "basic".

The only thing that bugs me about the basic solution is that we are doing i=
t in response to clients operating in a limited environment, and I'm unsure=
 of what other limitations we are not taking into consideration.

-andy=

From johnl@taugh.com  Fri Jul 20 15:46:16 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4E6A11E80B7 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 15:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.594
X-Spam-Level: 
X-Spam-Status: No, score=-2.594 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6Z7J58hUVtr for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 15:46:15 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 48DE311E8098 for <weirds@ietf.org>; Fri, 20 Jul 2012 15:46:15 -0700 (PDT)
Received: (qmail 59758 invoked from network); 20 Jul 2012 22:47:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=e96d.5009dfee.k1207; bh=B8rnOfRA1T61ACufxj32+jj8wMMIt9rRVq1eh7h1N0o=; b=wpEk0nWx34xiwv2JIa1kYZ8PQg6XeL0OMkVCC7F3c0llwmdg61UY3vYyMTeK2YbNyMf2dXI/6PlDzDSjWl/8zBvnKusBo+HTzs6WqGgtNn/+7NDCkId1SCncjgRvffN4/4NpUaN0iImrTQUy4+7ouJ5nfmtrEbNENN7EpnSciBs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=e96d.5009dfee.k1207; bh=B8rnOfRA1T61ACufxj32+jj8wMMIt9rRVq1eh7h1N0o=; b=eXnvmF+C4RumGELm2TO0FLzj9Q4sg+BZaj7KK1pDV89isTs/gOo/egMhKZJDa7CQ4nnQugW7brCuJ/JWqDZFI+neO2LwTH3VMzpkzaRBkE/bed6BOGUlrkzn9Lq0TJiHFKDWwZG7oKbotj6IN1Ru5t5dCwRY3YH64WvlHZNQ+jk=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 20 Jul 2012 22:46:48 -0000
Date: 20 Jul 2012 18:47:09 -0400
Message-ID: <alpine.BSF.2.00.1207201842090.82811@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Andy Newton" <andy@arin.net>
In-Reply-To: <A747D5D0-D08D-4E64-A5C9-DB59D2D1420E@arin.net>
References: <20120720204118.70594.qmail@joyce.lan> <33B293F8-4285-4C28-942D-29F7EAFD10CB@arin.net> <alpine.BSF.2.00.1207201734160.82811@joyce.lan> <A747D5D0-D08D-4E64-A5C9-DB59D2D1420E@arin.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 22:46:16 -0000

> The reason for A/AAAA is because CNAME will not co-habitate with NAPTR or any other records on the same name. A fix to that is to use one name for CNAME and another for NAPTR.

Well, OK, but now the question is what problem NAPTR solves.  I think I 
understand what it does in an environment where there are a lot of not 
quite compatible legacy servers serving irregular parts of the name space 
with mutually hostile managers.

But there's no legacy servers here, it's all going to be shiny new WEIRDS 
all of which will take exactly the same URLs, and on the name side, 
everything is strictly delegated from the top down.  What am I missing?

> The only thing that bugs me about the basic solution is that we are 
> doing it in response to clients operating in a limited environment, and 
> I'm unsure of what other limitations we are not taking into 
> consideration.

That's a reasonable concern, but I'd rather address it by building stuff 
out of the most widely available building blocks.  There's a lot more 
client stuff that understands CNAMEs than stuff that understands NAPTR.

R's,
John

From andy@arin.net  Fri Jul 20 16:33:32 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5683011E8087 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 16:33:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level: 
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[AWL=0.031,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FC7scpvRvDJ8 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 16:33:31 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 97A4621F8476 for <weirds@ietf.org>; Fri, 20 Jul 2012 16:33:31 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 6487B214E5A; Fri, 20 Jul 2012 19:34:26 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id DBEC8214E54; Fri, 20 Jul 2012 19:34:25 -0400 (EDT)
Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Fri, 20 Jul 2012 19:33:59 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0298.004; Fri, 20 Jul 2012 19:34:18 -0400
From: Andy Newton <andy@arin.net>
To: John R Levine <johnl@taugh.com>
Thread-Topic: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
Thread-Index: AQHNZrgkY5OCIYwPw0C8kEn5i0xCKpcy7AaAgAAJwYCAAAoigIAACOWAgAANKgA=
Date: Fri, 20 Jul 2012 23:34:16 +0000
Message-ID: <F89A4601-3841-43D4-8BE9-A9ABD7AADAC9@arin.net>
References: <20120720204118.70594.qmail@joyce.lan> <33B293F8-4285-4C28-942D-29F7EAFD10CB@arin.net> <alpine.BSF.2.00.1207201734160.82811@joyce.lan> <A747D5D0-D08D-4E64-A5C9-DB59D2D1420E@arin.net> <alpine.BSF.2.00.1207201842090.82811@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1207201842090.82811@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.35.153]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <814C01E0424B664F9C2E7CC9EDE2D0BA@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 23:33:32 -0000

On Jul 20, 2012, at 6:47 PM, John R Levine wrote:

> Well, OK, but now the question is what problem NAPTR solves.  I think I u=
nderstand what it does in an environment where there are a lot of not quite=
 compatible legacy servers serving irregular parts of the name space with m=
utually hostile managers.
>=20
> But there's no legacy servers here, it's all going to be shiny new WEIRDS=
 all of which will take exactly the same URLs, and on the name side, everyt=
hing is strictly delegated from the top down.  What am I missing?

Really only two things that I see: 1) allows for hosting the service on a n=
on-fixed path, and 2) allows the specification of HTTPS.

I personally am not swayed by these issues. Perhaps other have better reaso=
ning.

>> The only thing that bugs me about the basic solution is that we are doin=
g it in response to clients operating in a limited environment, and I'm uns=
ure of what other limitations we are not taking into consideration.
>=20
> That's a reasonable concern, but I'd rather address it by building stuff =
out of the most widely available building blocks.  There's a lot more clien=
t stuff that understands CNAMEs than stuff that understands NAPTR.

This strikes me as a reasonable argument.

-andy=

From johnl@iecc.com  Fri Jul 20 18:15:37 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 333D721F84A2 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 18:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.138
X-Spam-Level: 
X-Spam-Status: No, score=-111.138 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IIvdc1-pA1Gi for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 18:15:36 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id E966621F84AF for <weirds@ietf.org>; Fri, 20 Jul 2012 18:15:35 -0700 (PDT)
Received: (qmail 77849 invoked from network); 21 Jul 2012 01:16:32 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 21 Jul 2012 01:16:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=500a02f0.xn--hew.k1207; i=johnl@user.iecc.com; bh=b42x8jbpFTrd2n1HCw1D/NHKc0mIKKfq8rJWlQo6SyE=; b=fPBvBcBfejuqUh6L17/Q8OAasr63LyTF223T0/Kv7aRuUotxVPG0YcXY9G02funYZImT2KzwmTLB7//KT65q/TvxUlFr+rfsLmnTT0uXIJXMblcsITYwTGLneZQ51DZYxo7osBMaLmpddOqP3XQKTofHucct5v1uz753TX2itMc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=500a02f0.xn--hew.k1207; olt=johnl@user.iecc.com; bh=b42x8jbpFTrd2n1HCw1D/NHKc0mIKKfq8rJWlQo6SyE=; b=okdbLNBEQiXbyZUKkMy53HALLDz1YU6j8GbTDEw4Midgzr3YdEoYxwSE64yXb1z/+ml/j8GOu+z5JkVIu5lSeJL0e+mcBbuSAIMhm1NjBEU65z7aO8jAF/KbiIB96iyODpte8ZuPcb/7SXsmcQpl4TVnBcNJg8N3dZg/fBJtadI=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 21 Jul 2012 01:16:10 -0000
Message-ID: <20120721011610.37781.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <F89A4601-3841-43D4-8BE9-A9ABD7AADAC9@arin.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 01:15:37 -0000

>Really only two things that I see: 1) allows for hosting the service on a
>non-fixed path, and 2) allows the specification of HTTPS.
>
>I personally am not swayed by these issues. Perhaps other have better reasoning.

HTTPS is a sensible concern.  One possibility would be to say that all
WEIRDS servers run over HTTPS, or if people really hate that, we could
have tld.weirds.arpa for the normal server and tld.sweirds.arpa for
the secure one.  Personally, I prefer all HTTPS all the time.

R's,
John

From carlos@lacnic.net  Fri Jul 20 09:48:16 2012
Return-Path: <carlos@lacnic.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C186821F84B4 for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 09:48:16 -0700 (PDT)
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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y3OMqIv5qXuk for <weirds@ietfa.amsl.com>; Fri, 20 Jul 2012 09:48:15 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 4828921F848B for <weirds@ietf.org>; Fri, 20 Jul 2012 09:48:13 -0700 (PDT)
Received: from europa.local (unknown [IPv6:2001:470:5:ba9:5b1:1feb:3261:d677]) by mail.lacnic.net.uy (Postfix) with ESMTP id 559C330841C for <weirds@ietf.org>; Fri, 20 Jul 2012 13:49:06 -0300 (UYT)
Message-ID: <50098C00.2090000@lacnic.net>
Date: Fri, 20 Jul 2012 12:49:04 -0400
From: Carlos Martinez-Cagnazzo <carlos@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: weirds@ietf.org
References: <20120720161600.98121.qmail@joyce.lan>
In-Reply-To: <20120720161600.98121.qmail@joyce.lan>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: carlos@lacnic.net
X-Mailman-Approved-At: Sat, 21 Jul 2012 02:50:03 -0700
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 16:48:17 -0000

Hi, see inline

--
Carlos Martinez-Cagnazzo
R+D Engineer
http://www.labs.lacnic.net

On 7/20/12 12:16 PM, John Levine wrote:
>> Is it a requirement that a pure JavaScript implementation of a WEIRDS
>> client must  be possible? If so, we have a pretty strong restriction
>> that will limit what we can / cannot do.
> Given that Andy's told us that many, perhaps most, of the existing
> users of the existing prototype are using Javascript, it'd be a cruel
> joke to say that won't work any more.
I don't think we're saying that their clients won't work anymore. The
queries will work as always.
>
>> On the other hand, how difficult / heavy to operate would it be to run a
>> 'helper' webservice that basically gives the SRV record to those pesky
>> pure JS implementations ?
> Could you explain exactly how a "helper" that received an http query
> from a web client and returned the hostname for the appropriate server
> would be different from a top level WEIRDS server that received an http
> query from a web client and returned the URL (including the hostname)
> for the appropriate server?
It would provide comparable service, and (hopefully) would provide a
more palatable approach to those folks who are not comfortable with the
idea of a single, top-level WEIRDS referral service. It would allow
bootstrapping the WEIRDS tree without relying on a centralized database.

As I mentioned in earlier emails, I originally wrote about a fully
hierarchical WEIRDS tree, but then I received some well fundamented
negative feedback on the idea.

regards

Carlos
>
> R's,
> John



From chris@ausregistry.com.au  Sat Jul 21 06:31:12 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACEAA21F86D4 for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 06:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.732
X-Spam-Level: 
X-Spam-Status: No, score=-0.732 tagged_above=-999 required=5 tests=[AWL=0.564,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_64=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hEnUFDSXy3Qx for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 06:31:11 -0700 (PDT)
Received: from mx02.ausregistry.net.au (mx02.ausregistry.net.au [202.65.15.42]) by ietfa.amsl.com (Postfix) with ESMTP id 722FC21F86D1 for <weirds@ietf.org>; Sat, 21 Jul 2012 06:31:09 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron02.off08.stkildard.vic.ausregistry.com.au with ESMTP; 21 Jul 2012 23:32:06 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Sat, 21 Jul 2012 23:31:53 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: John Levine <johnl@taugh.com>, "weirds@ietf.org" <weirds@ietf.org>
Date: Sat, 21 Jul 2012 23:32:06 +1000
Thread-Topic: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
Thread-Index: Ac1nRTCBgsMsqWoWRTmx9rFXsl8nrQ==
Message-ID: <CC30E975.34112%chris@ausregistry.com.au>
In-Reply-To: <20120721011610.37781.qmail@joyce.lan>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 13:31:13 -0000

I like the idea of trying to maintain a secure path from bootstrap to
response. So with the "CNAME to well know port 80, which can then redirect
to 443 for HTTPs if the provider wants" proposal I don't like the insecure
hop in the chain (if we are to seriously think about security).

An easy fix for this is make all required to run over HTTPs instead of
HTTP, but the issues with this (asides from forcing secure) is that if I
run a registry for 100s of TLDs (which AusRegistry will be for example) I
don't want to have to get 100s of SSL certs. I would prefer to be able to
run the weirds service at something like say
"https://weirds.ausregistry.net" for all the TLDs we operate. Also I
couldn't get a wildcard cert for *.weirds.arpa because that would mean I
could pretend to be other TLDs, oh and finally, how will I get a cert at
all? What CA will give me a cert for au.weirds.arpa?

So this leads me to preferred solution

SOLUTION 2
NAPTR for TLD under weirds.arpa to a URL (DNSSEC protects the DNS query,
HTTPs (if I use it in the URL) protects the HTTP - no break in security)
and this means one SSL certificate to manage and everything is nice and
clean. It also means I can use NAPTR records with varying attributes to
support load distribution and 'failover' etc. Its a really good clean
solution that only has the one disadvantage as far as I can tell and
that=B9s that it can't be used by Javascript - which firstly can be solved
by the person implementing the java script client making a call back to a
server side script (which they host) to do the DNS lookup - as others have
discussed, and secondly I am very worried that we start to look at things
like 'this can't be done in javascript' as a constraint on our protocol
design.

Thanks

Chris

On 21/07/12 11:16 AM, "John Levine" <johnl@taugh.com> wrote:

>>Really only two things that I see: 1) allows for hosting the service on a
>>non-fixed path, and 2) allows the specification of HTTPS.
>>
>>I personally am not swayed by these issues. Perhaps other have better
>>reasoning.
>
>HTTPS is a sensible concern.  One possibility would be to say that all
>WEIRDS servers run over HTTPS, or if people really hate that, we could
>have tld.weirds.arpa for the normal server and tld.sweirds.arpa for
>the secure one.  Personally, I prefer all HTTPS all the time.
>
>R's,
>John
>_______________________________________________
>weirds mailing list
>weirds@ietf.org
>https://www.ietf.org/mailman/listinfo/weirds


From chris@ausregistry.com.au  Sat Jul 21 06:49:30 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32C6121F8609 for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 06:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.064
X-Spam-Level: 
X-Spam-Status: No, score=0.064 tagged_above=-999 required=5 tests=[AWL=-0.394,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_64=0.6, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R1QQAWOsA3+R for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 06:49:29 -0700 (PDT)
Received: from mx02.ausregistry.net.au (mx02.ausregistry.net.au [202.65.15.42]) by ietfa.amsl.com (Postfix) with ESMTP id D825721F85F4 for <weirds@ietf.org>; Sat, 21 Jul 2012 06:49:28 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron02.off08.stkildard.vic.ausregistry.com.au with ESMTP; 21 Jul 2012 23:50:26 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Sat, 21 Jul 2012 23:50:13 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: Chris Wright <chris@ausregistry.com.au>, John Levine <johnl@taugh.com>, "weirds@ietf.org" <weirds@ietf.org>
Date: Sat, 21 Jul 2012 23:50:25 +1000
Thread-Topic: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
Thread-Index: Ac1nR8ACOIzfxFSzQcyzqBRta2b65Q==
Message-ID: <CC30EFCD.3412F%chris@ausregistry.com.au>
In-Reply-To: <CC30E975.34112%chris@ausregistry.com.au>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="euc-kr"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 13:49:30 -0000

QWN0dWFsbHkgSSB3b3VsZCBsaWtlIHRvIGFkZCB0byBteSBwcmVmZXJyZWQgc29sdXRpb24gYmVs
b3cgdGhhdCBpdCBhbHNvDQp3b3JrcyBlcXVhbGx5IHdlbGwgYXMgYSB3ZWxsIGtub3duIE5BUFRS
IHJlY29yZCBpbiB0aGUgVExEIHpvbmUgZmlsZQ0KaXRzZWxmLCBhbmQgdGhpcyBpcyBldmVuIGJl
dHRlciBhcyB0aGVuIHRoZXJlIGlzIG5vIG5lZWQgdG8gZ2V0IElBTkENCmludm9sdmVkIGZvciBj
aGFuZ2VzLiBUaG91Z2ggd2UgbWF5IG5lZWQgdG8gdGhpbmsgYWJvdXQgaG93IHRoaXMgd291bGQN
CndvcmsgZm9yIElQIGFkZHJlc3MgbG9va3VwcywgYWx0aG91Z2ggSSBhbSBub3Qgc3VyZSB0aGF0
IGl0IGlzIGVudGlyZWx5DQpyZXF1aXJlZCB0aGF0IElQIGFkZHJlc3NlcyBhbmQgZG9tYWluIG5h
bWUgbG9va3VwcyBuZWVkIHRoZSBleGFjdCBzYW1lDQpib290c3RyYXAuDQoNCklQIGJvb3RzdHJh
cCBjb3VsZCBiZSByZXZlcnNlIHJlc29sdmUgZWcuIDIwMy4xOC41Ni4xIGFuZCBsb29rIHVwIHRo
ZQ0KMjAzLmluLWFkZHIuYXJhcCB6b25lIGZpbGUgZm9yIHRoZSByZWNvcmQgKGFuZCBzaW1pbGFy
IGZvciBJUHY2KS4NCg0KVGhhbmtzDQoNCkNocmlzDQoNCk9uIDIxLzA3LzEyIDExOjMyIFBNLCAi
Q2hyaXMgV3JpZ2h0IiA8Y2hyaXNAYXVzcmVnaXN0cnkuY29tLmF1PiB3cm90ZToNCg0KPkkgbGlr
ZSB0aGUgaWRlYSBvZiB0cnlpbmcgdG8gbWFpbnRhaW4gYSBzZWN1cmUgcGF0aCBmcm9tIGJvb3Rz
dHJhcCB0bw0KPnJlc3BvbnNlLiBTbyB3aXRoIHRoZSAiQ05BTUUgdG8gd2VsbCBrbm93IHBvcnQg
ODAsIHdoaWNoIGNhbiB0aGVuIHJlZGlyZWN0DQo+dG8gNDQzIGZvciBIVFRQcyBpZiB0aGUgcHJv
dmlkZXIgd2FudHMiIHByb3Bvc2FsIEkgZG9uJ3QgbGlrZSB0aGUgaW5zZWN1cmUNCj5ob3AgaW4g
dGhlIGNoYWluIChpZiB3ZSBhcmUgdG8gc2VyaW91c2x5IHRoaW5rIGFib3V0IHNlY3VyaXR5KS4N
Cj4NCj5BbiBlYXN5IGZpeCBmb3IgdGhpcyBpcyBtYWtlIGFsbCByZXF1aXJlZCB0byBydW4gb3Zl
ciBIVFRQcyBpbnN0ZWFkIG9mDQo+SFRUUCwgYnV0IHRoZSBpc3N1ZXMgd2l0aCB0aGlzIChhc2lk
ZXMgZnJvbSBmb3JjaW5nIHNlY3VyZSkgaXMgdGhhdCBpZiBJDQo+cnVuIGEgcmVnaXN0cnkgZm9y
IDEwMHMgb2YgVExEcyAod2hpY2ggQXVzUmVnaXN0cnkgd2lsbCBiZSBmb3IgZXhhbXBsZSkgSQ0K
PmRvbid0IHdhbnQgdG8gaGF2ZSB0byBnZXQgMTAwcyBvZiBTU0wgY2VydHMuIEkgd291bGQgcHJl
ZmVyIHRvIGJlIGFibGUgdG8NCj5ydW4gdGhlIHdlaXJkcyBzZXJ2aWNlIGF0IHNvbWV0aGluZyBs
aWtlIHNheQ0KPiJodHRwczovL3dlaXJkcy5hdXNyZWdpc3RyeS5uZXQiIGZvciBhbGwgdGhlIFRM
RHMgd2Ugb3BlcmF0ZS4gQWxzbyBJDQo+Y291bGRuJ3QgZ2V0IGEgd2lsZGNhcmQgY2VydCBmb3Ig
Ki53ZWlyZHMuYXJwYSBiZWNhdXNlIHRoYXQgd291bGQgbWVhbiBJDQo+Y291bGQgcHJldGVuZCB0
byBiZSBvdGhlciBUTERzLCBvaCBhbmQgZmluYWxseSwgaG93IHdpbGwgSSBnZXQgYSBjZXJ0IGF0
DQo+YWxsPyBXaGF0IENBIHdpbGwgZ2l2ZSBtZSBhIGNlcnQgZm9yIGF1LndlaXJkcy5hcnBhPw0K
Pg0KPlNvIHRoaXMgbGVhZHMgbWUgdG8gcHJlZmVycmVkIHNvbHV0aW9uDQo+DQo+U09MVVRJT04g
Mg0KPk5BUFRSIGZvciBUTEQgdW5kZXIgd2VpcmRzLmFycGEgdG8gYSBVUkwgKEROU1NFQyBwcm90
ZWN0cyB0aGUgRE5TIHF1ZXJ5LA0KPkhUVFBzIChpZiBJIHVzZSBpdCBpbiB0aGUgVVJMKSBwcm90
ZWN0cyB0aGUgSFRUUCAtIG5vIGJyZWFrIGluIHNlY3VyaXR5KQ0KPmFuZCB0aGlzIG1lYW5zIG9u
ZSBTU0wgY2VydGlmaWNhdGUgdG8gbWFuYWdlIGFuZCBldmVyeXRoaW5nIGlzIG5pY2UgYW5kDQo+
Y2xlYW4uIEl0IGFsc28gbWVhbnMgSSBjYW4gdXNlIE5BUFRSIHJlY29yZHMgd2l0aCB2YXJ5aW5n
IGF0dHJpYnV0ZXMgdG8NCj5zdXBwb3J0IGxvYWQgZGlzdHJpYnV0aW9uIGFuZCAnZmFpbG92ZXIn
IGV0Yy4gSXRzIGEgcmVhbGx5IGdvb2QgY2xlYW4NCj5zb2x1dGlvbiB0aGF0IG9ubHkgaGFzIHRo
ZSBvbmUgZGlzYWR2YW50YWdlIGFzIGZhciBhcyBJIGNhbiB0ZWxsIGFuZA0KPnRoYXSp9nMgdGhh
dCBpdCBjYW4ndCBiZSB1c2VkIGJ5IEphdmFzY3JpcHQgLSB3aGljaCBmaXJzdGx5IGNhbiBiZSBz
b2x2ZWQNCj5ieSB0aGUgcGVyc29uIGltcGxlbWVudGluZyB0aGUgamF2YSBzY3JpcHQgY2xpZW50
IG1ha2luZyBhIGNhbGwgYmFjayB0byBhDQo+c2VydmVyIHNpZGUgc2NyaXB0ICh3aGljaCB0aGV5
IGhvc3QpIHRvIGRvIHRoZSBETlMgbG9va3VwIC0gYXMgb3RoZXJzIGhhdmUNCj5kaXNjdXNzZWQs
IGFuZCBzZWNvbmRseSBJIGFtIHZlcnkgd29ycmllZCB0aGF0IHdlIHN0YXJ0IHRvIGxvb2sgYXQg
dGhpbmdzDQo+bGlrZSAndGhpcyBjYW4ndCBiZSBkb25lIGluIGphdmFzY3JpcHQnIGFzIGEgY29u
c3RyYWludCBvbiBvdXIgcHJvdG9jb2wNCj5kZXNpZ24uDQo+DQo+VGhhbmtzDQo+DQo+Q2hyaXMN
Cj4NCj5PbiAyMS8wNy8xMiAxMToxNiBBTSwgIkpvaG4gTGV2aW5lIiA8am9obmxAdGF1Z2guY29t
PiB3cm90ZToNCj4NCj4+PlJlYWxseSBvbmx5IHR3byB0aGluZ3MgdGhhdCBJIHNlZTogMSkgYWxs
b3dzIGZvciBob3N0aW5nIHRoZSBzZXJ2aWNlIG9uDQo+Pj5hDQo+Pj5ub24tZml4ZWQgcGF0aCwg
YW5kIDIpIGFsbG93cyB0aGUgc3BlY2lmaWNhdGlvbiBvZiBIVFRQUy4NCj4+Pg0KPj4+SSBwZXJz
b25hbGx5IGFtIG5vdCBzd2F5ZWQgYnkgdGhlc2UgaXNzdWVzLiBQZXJoYXBzIG90aGVyIGhhdmUg
YmV0dGVyDQo+Pj5yZWFzb25pbmcuDQo+Pg0KPj5IVFRQUyBpcyBhIHNlbnNpYmxlIGNvbmNlcm4u
ICBPbmUgcG9zc2liaWxpdHkgd291bGQgYmUgdG8gc2F5IHRoYXQgYWxsDQo+PldFSVJEUyBzZXJ2
ZXJzIHJ1biBvdmVyIEhUVFBTLCBvciBpZiBwZW9wbGUgcmVhbGx5IGhhdGUgdGhhdCwgd2UgY291
bGQNCj4+aGF2ZSB0bGQud2VpcmRzLmFycGEgZm9yIHRoZSBub3JtYWwgc2VydmVyIGFuZCB0bGQu
c3dlaXJkcy5hcnBhIGZvcg0KPj50aGUgc2VjdXJlIG9uZS4gIFBlcnNvbmFsbHksIEkgcHJlZmVy
IGFsbCBIVFRQUyBhbGwgdGhlIHRpbWUuDQo+Pg0KPj5SJ3MsDQo+PkpvaG4NCj4+X19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+d2VpcmRzIG1haWxpbmcg
bGlzdA0KPj53ZWlyZHNAaWV0Zi5vcmcNCj4+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby93ZWlyZHMNCj4NCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KPndlaXJkcyBtYWlsaW5nIGxpc3QNCj53ZWlyZHNAaWV0Zi5vcmcNCj5odHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3dlaXJkcw0KDQo=

From johnl@taugh.com  Sat Jul 21 08:33:40 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0550321F8567 for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 08:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.294
X-Spam-Level: 
X-Spam-Status: No, score=-2.294 tagged_above=-999 required=5 tests=[AWL=-0.294, BAYES_00=-2.599, J_CHICKENPOX_64=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vPwswU7MiAbg for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 08:33:39 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id DBF5821F855E for <weirds@ietf.org>; Sat, 21 Jul 2012 08:33:38 -0700 (PDT)
Received: (qmail 45677 invoked from network); 21 Jul 2012 15:34:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=b26c.500acc0c.k1207; bh=a9QKZ/CJfJVwY8nc3TwvdwGtVOjn7uNbe6uEG3zHPc4=; b=JSF1TPOTSYbxJiUjTeERSgqc3gEug8MNn0T0oP+tOw0X6P/x4znDB7qyjMZlmRzMtf0bQndZvYyENEVQH0bIsGHLst5UwndLWsw9QWjCxx3xi3wXoQBgy3VKUgEDl2VJKmQPhxO2++N8LYMDKTsKFgmrsBiivtb+5FMYlSi9XR8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=b26c.500acc0c.k1207; bh=a9QKZ/CJfJVwY8nc3TwvdwGtVOjn7uNbe6uEG3zHPc4=; b=D2lH9gzedTOWezYQhJlfdHBMh/UdOFbtJtMXIj6FxioWIFVHFEUIFhAW3Ukxc42uOg5ThdsPf9IBdvmWnQ7TKiQO6sqsDc+wTkKYQ/XTuG4+lO2N35ALIPpfn/K1TIy6Z/AGbry2ibJq0SNV5Bf3jw6Gd16TXwWxUFz9DSr7VsE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 21 Jul 2012 15:34:14 -0000
Date: 21 Jul 2012 11:34:36 -0400
Message-ID: <alpine.BSF.2.00.1207211117490.52171@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Chris Wright" <chris@ausregistry.com.au>
In-Reply-To: <CC30E975.34112%chris@ausregistry.com.au>
References: <CC30E975.34112%chris@ausregistry.com.au>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 15:33:40 -0000

> An easy fix for this is make all required to run over HTTPs instead of
> HTTP, but the issues with this (asides from forcing secure) is that if I
> run a registry for 100s of TLDs (which AusRegistry will be for example) I
> don't want to have to get 100s of SSL certs.

Your new TLD customers will each have paid ICANN $185,000 to apply for 
their new TLDs, and $50,000 maintenance every year.  You will I hope 
excuse us if we have limited sympathy for complaints that joining the 
gravy train might involve some extra work.

> What CA will give me a cert for au.weirds.arpa?

The obvious answer is that whoever runs weirds.arpa (most likely IANA) 
will arrange for SSL certs for the entities that register CNAMEs in it, or 
at least have agreements with a few SSL vendors to approve applications 
from the registrants.

> SOLUTION 2
> NAPTR ...

Didn't we just spent a week noting that a large fraction of WEIRDS clients 
will probably be unable to handle NAPTR?

R's,
John

From johnl@iecc.com  Sat Jul 21 09:14:01 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DFE621F8675 for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 09:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.395
X-Spam-Level: 
X-Spam-Status: No, score=-110.395 tagged_above=-999 required=5 tests=[AWL=-0.685, BAYES_05=-1.11, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Gs3eA3cRAxN for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 09:14:00 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE3D21F866D for <weirds@ietf.org>; Sat, 21 Jul 2012 09:13:59 -0700 (PDT)
Received: (qmail 56357 invoked from network); 21 Jul 2012 16:14:57 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 21 Jul 2012 16:14:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=500ad581.xn--btvx9d.k1207; i=johnl@user.iecc.com; bh=pGl+ubzKYEyaQQL2tsaO8QlPH7oK2fEpAMW2oAwxG3c=; b=hU/iC/vaCq10iqzZyk14kVqtzLonKxvm7pSdrfDnP6oWoy4ehealXX839INQQiZkpiuVfgXSXt+JJmNgLaXRlRO1wGiXzFLvHIo3qmQt3OE7n+PZqDMVRtQfef0C+kkKm3uLUOcQMmvyu4s1wTiiqVInWGzEanTdGo4dgtj6hRw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=500ad581.xn--btvx9d.k1207; olt=johnl@user.iecc.com; bh=pGl+ubzKYEyaQQL2tsaO8QlPH7oK2fEpAMW2oAwxG3c=; b=VQnFaHY6b3kk3vop8RTJ7s8Kc7FSUiO9HW8BNv7f69jfHtg+4gRGk9kNPwohvaI16pFRtEfOkZCxMpnsoDAYLoTHnzT6Tn9vxauCvqiThkykSpKCZs69QBw6S1uLPsegO/FmGZwTapIv4WfummidaAAmPcsg4q/PD26uoyJhHP8=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 21 Jul 2012 16:14:34 -0000
Message-ID: <20120721161434.67542.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <50098C00.2090000@lacnic.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: carlos@lacnic.net
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 16:14:01 -0000

>> Could you explain exactly how a "helper" that received an http query
>> from a web client and returned the hostname for the appropriate server
>> would be different from a top level WEIRDS server ...

>It would provide comparable service, and (hopefully) would provide a
>more palatable approach to those folks who are not comfortable with the
>idea of a single, top-level WEIRDS referral service. It would allow
>bootstrapping the WEIRDS tree without relying on a centralized database.

It occurs to me that for people who care about security, unless there
is a single well known master helper server (which has the same
scaling problem as a top level redirect server) this enables a
gigantic man in the middle attack that no amount of DNSSEC or HTTPS
will fix.

For the umpteenth time, CNAMEs do everything a bootstrap needs to to.
Really.

R's,
John

From chris@ausregistry.com.au  Sat Jul 21 17:45:10 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2229E21F8567 for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 17:45:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.763
X-Spam-Level: 
X-Spam-Status: No, score=-0.763 tagged_above=-999 required=5 tests=[AWL=0.532,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_64=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mSO48d3SDgZj for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 17:45:09 -0700 (PDT)
Received: from mx01.ausregistry.net.au (mx01.ausregistry.net.au [202.65.15.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0C02C21F8534 for <weirds@ietf.org>; Sat, 21 Jul 2012 17:45:06 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron01.off08.stkildard.vic.ausregistry.com.au with ESMTP; 22 Jul 2012 10:46:05 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Sun, 22 Jul 2012 10:45:51 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: John R Levine <johnl@taugh.com>
Date: Sun, 22 Jul 2012 10:46:00 +1000
Thread-Topic: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
Thread-Index: Ac1no1dsBWGttuvNS6S8KgtzT2iPEw==
Message-ID: <CC318679.3414A%chris@ausregistry.com.au>
In-Reply-To: <alpine.BSF.2.00.1207211117490.52171@joyce.lan>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 00:45:10 -0000

Thanks John,=20

I notice you have conveniently ignored responding to the keeping the chain
secure argument? What are you thoughts on that? And how would you solve it
in your proposed model?

Response to your other comments below:

On 22/07/12 1:34 AM, "John R Levine" <johnl@taugh.com> wrote:

>> An easy fix for this is make all required to run over HTTPs instead of
>> HTTP, but the issues with this (asides from forcing secure) is that if I
>> run a registry for 100s of TLDs (which AusRegistry will be for example)
>>I
>> don't want to have to get 100s of SSL certs.
>
>Your new TLD customers will each have paid ICANN $185,000 to apply for
>their new TLDs, and $50,000 maintenance every year.  You will I hope
>excuse us if we have limited sympathy for complaints that joining the
>gravy train might involve some extra work.

What ever personal opinions you have about new gTLDs and the amount of
money that is or is not involved (I didn't know you were privy to any of
our back end contracts? So Im fairly confident you DO NOT know how much we
are charging for Registry services), they are not an argument for
designing a system in a way that is unnecessarily expensive to implement.


>
>> What CA will give me a cert for au.weirds.arpa?
>
>The obvious answer is that whoever runs weirds.arpa (most likely IANA)
>will arrange for SSL certs for the entities that register CNAMEs in it,
>or=20
>at least have agreements with a few SSL vendors to approve applications
>from the registrants.

Operationally I do not like not being in control of my own destiny. SSL
certificates have to be 'renewed' every year, I do not want to be reliant
on someone from IANA doing this to ensure my WEIRDS service keeps
functioning correctly, further there will surely be a cost to this, to
date I am not aware of anything IANA charges for, this would be either
something IANA would have to operationally absorb, or they would have to
add 'functionality' to start charging for these things, neither of which I
believe is a good thing to be asking IANA to do (without damn good reason
- which I am sorry but I (and others it seems) disagree with you that
Javascript is a damn good reason).

>
>> SOLUTION 2
>> NAPTR ...
>
>Didn't we just spent a week noting that a large fraction of WEIRDS
>clients=20
>will probably be unable to handle NAPTR?

No, you spent a week saying that and I (and others) said so what? Why
should the constraints of a particular programming language dictate our
protocol specification (especially when we have shown perfect viable,
cheap and easy ways to work around those constraints). What happens if in
the next version of java script they now introduce the ability to do DNS
lookups? I am sure if it is that big of a deal for the large fraction of
implementations already out there (cmon really, later fraction of
implementations already out there for a standard that doesn't yet exist,
they are in a test bed?) then someone will add the appropriate support to
the language. Finally, the implementation at the moment is just that, an
experiment, nothing more.

I am all for considering the Javascript use case and making sure we do not
do something that will mean it is impossible to implement a client using
javascript, but that simply is not the case. As above we have shown that a
simple call back to the server (the one that served the javascript in the
first place) can do the DNS resolution, there is lots of examples of
javascript code doing this on the web already (just google it) there are
even javascript libraries with corresponding server side scripts to handle
just this case!

So I for one (and I have seen others), am yet to be convinced that the
constraint is justified - you seem to think it is, but last time I checked
IETF processes where rough consensus not dictatorship.

>
>R's,
>John


From johnl@taugh.com  Sat Jul 21 17:55:16 2012
Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BED921F855E for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 17:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.583
X-Spam-Level: 
X-Spam-Status: No, score=-2.583 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L6rRMxP-Lfzs for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 17:55:15 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 2C88821F855D for <weirds@ietf.org>; Sat, 21 Jul 2012 17:55:15 -0700 (PDT)
Received: (qmail 62015 invoked from network); 22 Jul 2012 00:56:14 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=f23d.500b4fae.k1207; bh=PjI6sMfEsKjiZUjtsPTg+KoUcw2YaJwGJ6ehkxs5rA0=; b=HHv1dkoTpPEpvY3i9ut7HjIidtFNIwjnpftyfB0QfxjsYcCfWQODpMNyPeCwX/TXKB78WoAHoraC3KuR1Q5aOwqKHek9/EMLhjLKSk8tLKRNEUq45ae15v64v16Vb/LG2eitNvDTBoXSEJq6gGDABeqRJXoBEiMHVT9Equ3Ajro=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=f23d.500b4fae.k1207; bh=PjI6sMfEsKjiZUjtsPTg+KoUcw2YaJwGJ6ehkxs5rA0=; b=LPN1HwBLwmJf2+Z1KcLAyXi87FKC47QgYbndReZIDlOdOBO2GarPAmrpJbZkgRkfq9XXwoGEWWfEsLc01qb6s17OBLpAosZTKpYsrjmitr5svWrc++1gV+cfxM4Aa0vPY0+qbGq5gCPtZx5KyNJGeTVn8ccUsw9MrOLNNPIXHj0=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 22 Jul 2012 00:55:52 -0000
Date: 21 Jul 2012 20:56:14 -0400
Message-ID: <alpine.BSF.2.00.1207212055430.51317@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Chris Wright" <chris@ausregistry.com.au>
In-Reply-To: <CC318679.3414A%chris@ausregistry.com.au>
References: <CC318679.3414A%chris@ausregistry.com.au>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] bootstrap complication, was the bootstrap problem: a DNS compromise
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 00:55:16 -0000

> So I for one (and I have seen others), am yet to be convinced that the
> constraint is justified - you seem to think it is, but last time I checked
> IETF processes where rough consensus not dictatorship.

Good point.  So before I respond to your screed, let's see if anyone else 
agrees with some of your surprising assertions.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From chris@ausregistry.com.au  Sat Jul 21 17:58:43 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA50321F852C for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 17:58:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.122
X-Spam-Level: 
X-Spam-Status: No, score=-1.122 tagged_above=-999 required=5 tests=[AWL=0.773,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8rio0jlJK6JA for <weirds@ietfa.amsl.com>; Sat, 21 Jul 2012 17:58:43 -0700 (PDT)
Received: from mx01.ausregistry.net.au (mx01.ausregistry.net.au [202.65.15.41]) by ietfa.amsl.com (Postfix) with ESMTP id 7270021F847E for <weirds@ietf.org>; Sat, 21 Jul 2012 17:58:39 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron01.off08.stkildard.vic.ausregistry.com.au with ESMTP; 22 Jul 2012 10:59:39 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Sun, 22 Jul 2012 10:59:25 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: John Levine <johnl@taugh.com>, "weirds@ietf.org" <weirds@ietf.org>
Date: Sun, 22 Jul 2012 10:59:35 +1000
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: Ac1npTyK+MaT0XUjRtOahIRptuFvHw==
Message-ID: <CC318B37.3417A%chris@ausregistry.com.au>
In-Reply-To: <20120721161434.67542.qmail@joyce.lan>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "carlos@lacnic.net" <carlos@lacnic.net>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 00:58:43 -0000

John,=20

Again see below.

On 22/07/12 2:14 AM, "John Levine" <johnl@taugh.com> wrote:

>>> Could you explain exactly how a "helper" that received an http query
>>> from a web client and returned the hostname for the appropriate server
>>> would be different from a top level WEIRDS server ...
>
>>It would provide comparable service, and (hopefully) would provide a
>>more palatable approach to those folks who are not comfortable with the
>>idea of a single, top-level WEIRDS referral service. It would allow
>>bootstrapping the WEIRDS tree without relying on a centralized database.
>
>It occurs to me that for people who care about security, unless there
>is a single well known master helper server (which has the same
>scaling problem as a top level redirect server) this enables a
>gigantic man in the middle attack that no amount of DNSSEC or HTTPS
>will fix.


Can you please explain how a secure DNS lookup done via DNSSEC, which
returns a HTTPs URL, which is then resolved again using DNSSEC, which you
finally then connect to using SSL is vulnerable to a man in the middle
attack, and then if so how a single HTTPs starting point solves that
problem? I just don't see your point, sorry if I am too stupid to see it,
but can you help me understand.


>
>For the umpteenth time, CNAMEs do everything a bootstrap needs to to.

The argument is not whether CNAMES server the purpose of bootstrap, I
concede that they do, but they come with several operational concerns
which are valid:

> the fixing the port problem (granted - a minor concern)
> the do we use HTTP vs HTTPs problem (securing end to end)
> the cost of purchasing, managing and so forth large volumes of SSL
>certificates (which the number registries, if they care about ssl, will
>need to do to)
> the ability to get those certificates (having IANA in the chain and what
>that means for IANA)
> the unnecessary IP address consumption (again, may be a minor concern)

Where as NAPTR records ALSO serve the purpose of bootstrap (I haven't
heard anyone say they don't) and so far they seem to be simpler and the
only argument any one has come up with is:

> they can't be used directly in javascript

And I am sorry that I appear to be frustrating you, but at the moment I
don't really hear anyone else weighing in on the discussion one way or the
other, perhaps I am not clear in how the process is supposed to work, if I
don't agree with what you saying, Im just supposed to give up? Throw my
hands up in the air and walk away in frustration?

>Really.
>
>R's,
>John
>_______________________________________________
>weirds mailing list
>weirds@ietf.org
>https://www.ietf.org/mailman/listinfo/weirds


From warren@kumari.net  Sun Jul 22 18:13:58 2012
Return-Path: <warren@kumari.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9456521F85A5 for <weirds@ietfa.amsl.com>; Sun, 22 Jul 2012 18:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.272
X-Spam-Level: 
X-Spam-Status: No, score=-106.272 tagged_above=-999 required=5 tests=[AWL=0.327, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A2wgmcGYaoLy for <weirds@ietfa.amsl.com>; Sun, 22 Jul 2012 18:13:58 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id D37C121F859A for <weirds@ietf.org>; Sun, 22 Jul 2012 18:13:54 -0700 (PDT)
Received: from [5.5.8.21] (vpn.snozzages.com [204.194.22.7]) by vimes.kumari.net (Postfix) with ESMTPSA id C1D7D1B40792; Sun, 22 Jul 2012 21:13:53 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CC318B37.3417A%chris@ausregistry.com.au>
Date: Sun, 22 Jul 2012 21:13:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <628895A6-6977-4923-8C03-30BC7B24D239@kumari.net>
References: <CC318B37.3417A%chris@ausregistry.com.au>
To: Chris Wright <chris@ausregistry.com.au>
X-Mailer: Apple Mail (2.1278)
Cc: John Levine <johnl@taugh.com>, "carlos@lacnic.net" <carlos@lacnic.net>, "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 01:13:58 -0000

On Jul 21, 2012, at 8:59 PM, Chris Wright wrote:

> John,=20
>=20
> Again see below.
>=20
> On 22/07/12 2:14 AM, "John Levine" <johnl@taugh.com> wrote:
>=20
>>>> Could you explain exactly how a "helper" that received an http =
query
>>>> from a web client and returned the hostname for the appropriate =
server
>>>> would be different from a top level WEIRDS server ...
>>=20
>>> It would provide comparable service, and (hopefully) would provide a
>>> more palatable approach to those folks who are not comfortable with =
the
>>> idea of a single, top-level WEIRDS referral service. It would allow
>>> bootstrapping the WEIRDS tree without relying on a centralized =
database.
>>=20
>> It occurs to me that for people who care about security, unless there
>> is a single well known master helper server (which has the same
>> scaling problem as a top level redirect server) this enables a
>> gigantic man in the middle attack that no amount of DNSSEC or HTTPS
>> will fix.
>=20
>=20
> Can you please explain how a secure DNS lookup done via DNSSEC, which
> returns a HTTPs URL, which is then resolved again using DNSSEC, which =
you
> finally then connect to using SSL is vulnerable to a man in the middle
> attack,

Please sir, how does an app know that the DNS lookups were "done via =
DNSSEC"? In the real world? =46rom <insert favorite language here>? =
(This isn't really specific to the helper discussion=85)


> and then if so how a single HTTPs starting point solves that
> problem? I just don't see your point, sorry if I am too stupid to see =
it,
> but can you help me understand.
>=20
>=20
>>=20
>> For the umpteenth time, CNAMEs do everything a bootstrap needs to to.
>=20
> The argument is not whether CNAMES server the purpose of bootstrap, I
> concede that they do, but they come with several operational concerns
> which are valid:
>=20
>> the fixing the port problem (granted - a minor concern)
>> the do we use HTTP vs HTTPs problem (securing end to end)
>> the cost of purchasing, managing and so forth large volumes of SSL
>> certificates (which the number registries, if they care about ssl, =
will
>> need to do to)
>> the ability to get those certificates (having IANA in the chain and =
what
>> that means for IANA)
>> the unnecessary IP address consumption (again, may be a minor =
concern)
>=20
> Where as NAPTR records ALSO serve the purpose of bootstrap (I haven't
> heard anyone say they don't) and so far they seem to be simpler and =
the
> only argument any one has come up with is:
>=20
>> they can't be used directly in javascript

Or a number of other languages...

>=20
> And I am sorry that I appear to be frustrating you, but at the moment =
I
> don't really hear anyone else weighing in on the discussion one way or =
the
> other,

Ok, I'll weigh in -- as much as I dislike agreeing with John[0], I too =
believe that having this easy to do in Javascript (and php and vbscript =
and  rexx and asp and=85) is really important.=20

> perhaps I am not clear in how the process is supposed to work, if I
> don't agree with what you saying, Im just supposed to give up? Throw =
my
> hands up in the air and walk away in frustration?

No, but toning it down a little might be nice=85

W

[0]: Just on principle...

>=20
>> Really.
>>=20
>> R's,
>> John
>> _______________________________________________
>> weirds mailing list
>> weirds@ietf.org
>> https://www.ietf.org/mailman/listinfo/weirds
>=20
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds
>=20

--
What our ancestors would really be thinking, if they were alive today, =
is: "Why is it so dark in here?"

    -- (Terry Pratchett, Pyramids)



From chris@ausregistry.com.au  Sun Jul 22 18:44:41 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6A1021F8647 for <weirds@ietfa.amsl.com>; Sun, 22 Jul 2012 18:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.199
X-Spam-Level: 
X-Spam-Status: No, score=-1.199 tagged_above=-999 required=5 tests=[AWL=0.696,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZXtGVZfwzCs5 for <weirds@ietfa.amsl.com>; Sun, 22 Jul 2012 18:44:41 -0700 (PDT)
Received: from mx02.ausregistry.net.au (mx02.ausregistry.net.au [202.65.15.42]) by ietfa.amsl.com (Postfix) with ESMTP id 9BCA021F8646 for <weirds@ietf.org>; Sun, 22 Jul 2012 18:44:40 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron02.off08.stkildard.vic.ausregistry.com.au with ESMTP; 23 Jul 2012 11:44:36 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Mon, 23 Jul 2012 11:44:23 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: Warren Kumari <warren@kumari.net>
Date: Mon, 23 Jul 2012 11:44:33 +1000
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: Ac1odK8YmRYcdogyQJyGW4XjK0a5OA==
Message-ID: <CC32E466.341EE%chris@ausregistry.com.au>
In-Reply-To: <628895A6-6977-4923-8C03-30BC7B24D239@kumari.net>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "carlos@lacnic.net" <carlos@lacnic.net>, John Levine <johnl@taugh.com>, "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 01:44:42 -0000

Thanks Warren

Comments below.

On 23/07/12 11:13 AM, "Warren Kumari" <warren@kumari.net> wrote:

>
>Please sir, how does an app know that the DNS lookups were "done via
>DNSSEC"? In the real world? From <insert favorite language here>? (This
>isn't really specific to the helper discussion=8A)

If the app is not willing to trust its local resolver then it can retrieve
the DNS records from the DNS directly itself. Yes this is problematic as
the app will need to have the root public key embedded in it, and then be
updated when it changes, but its not impossible. This begs the larger
question about whats the point of DNSSEC at all if this is really a
problem? Given that DNSSEC came from the IETF, when we are producing new
protocols we probably should be advocating the use of DNSSEC to help
encouraging adoption?

I guess its good that we can offer a client the option of putting in the
work and remaining 'secure', but it still works if they don't have to.
However as John has pointed out it is possible to achieve end to end
security by requiring that the CNAME record be accessed over HTTPs and if
we are prepared to accept that the security argument for one way or the
other comes off the table.

>
>Ok, I'll weigh in -- as much as I dislike agreeing with John[0], I too
>believe that having this easy to do in Javascript (and php and vbscript
>and  rexx and asp and=8A) is really important.

Great, thanks for weighing in, its good to see that there is more support
for one way over another (regardless of which way that is). For the record
though:

Php =3D dns_get_record -
http://us2.php.net/manual/en/function.dns-get-record.php
Vbscript and ASP/ASP.net can load objects using windows com object model,
there are many many com DNS objects around



>
>No, but toning it down a little might be nice=8A

Understood, I will attempt to be 'nicer' in my emails, for the record
though, nothing in my emails is meant to be attacking or negative towards
anyone in any way and I apologise if any one has taken it as such. I am
simply eager to understands others views and getting them to backup the
assertions they are making. I will look over past emails and see where I
have gone wrong here. If you could help me out by pointing out to me the
emails of concern to me would be appreciated.

>
>W
>
>[0]: Just on principle...
>
>>=20
>>> Really.
>>>=20
>>> R's,
>>> John
>>> _______________________________________________
>>> weirds mailing list
>>> weirds@ietf.org
>>> https://www.ietf.org/mailman/listinfo/weirds
>>=20
>> _______________________________________________
>> weirds mailing list
>> weirds@ietf.org
>> https://www.ietf.org/mailman/listinfo/weirds
>>=20
>
>--
>What our ancestors would really be thinking, if they were alive today,
>is: "Why is it so dark in here?"
>
>    -- (Terry Pratchett, Pyramids)
>
>


From warren@kumari.net  Sun Jul 22 19:16:06 2012
Return-Path: <warren@kumari.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C6C721F863D for <weirds@ietfa.amsl.com>; Sun, 22 Jul 2012 19:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.327
X-Spam-Level: 
X-Spam-Status: No, score=-106.327 tagged_above=-999 required=5 tests=[AWL=0.272, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dRHwcHYXUA4p for <weirds@ietfa.amsl.com>; Sun, 22 Jul 2012 19:16:05 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 3E06921F84B5 for <weirds@ietf.org>; Sun, 22 Jul 2012 19:16:05 -0700 (PDT)
Received: from [5.5.8.21] (vpn.snozzages.com [204.194.22.7]) by vimes.kumari.net (Postfix) with ESMTPSA id 540271B405FA; Sun, 22 Jul 2012 22:16:04 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CC32E466.341EE%chris@ausregistry.com.au>
Date: Sun, 22 Jul 2012 22:16:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <15BE2D22-33E6-45CE-9D88-92CC6E1BFE9B@kumari.net>
References: <CC32E466.341EE%chris@ausregistry.com.au>
To: Chris Wright <chris@ausregistry.com.au>
X-Mailer: Apple Mail (2.1278)
Cc: John Levine <johnl@taugh.com>, "carlos@lacnic.net" <carlos@lacnic.net>, "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 02:16:06 -0000

I started writing this as an [off-list], but then realized an on-list =
response is probably more appropriate...
On Jul 22, 2012, at 9:44 PM, Chris Wright wrote:

> Thanks Warren
>=20
> Comments below.
>=20
> On 23/07/12 11:13 AM, "Warren Kumari" <warren@kumari.net> wrote:
>=20
>>=20
>> Please sir, how does an app know that the DNS lookups were "done via
>> DNSSEC"? In the real world? =46rom <insert favorite language here>? =
(This
>> isn't really specific to the helper discussion=8A)
>=20
> If the app is not willing to trust its local resolver then it can =
retrieve
> the DNS records from the DNS directly itself. Yes this is problematic =
as
> the app will need to have the root public key embedded in it, and then =
be
> updated when it changes, but its not impossible. This begs the larger
> question about whats the point of DNSSEC at all if this is really a
> problem? Given that DNSSEC came from the IETF, when we are producing =
new
> protocols we probably should be advocating the use of DNSSEC to help
> encouraging adoption?

Yes, yes we should, but at the moment, there (unfortunately) isn't a =
good (generic) way of apps to *know* if the response was DNSSEC =
validated, even if they trust their browser=85 There *is* work underway =
in various places to try fix this issue by exposing / defining a =
standard API...

>=20
> I guess its good that we can offer a client the option of putting in =
the
> work and remaining 'secure', but it still works if they don't have to.
> However as John has pointed out it is possible to achieve end to end
> security by requiring that the CNAME record be accessed over HTTPs and =
if
> we are prepared to accept that the security argument for one way or =
the
> other comes off the table.

Ok.
>=20
>>=20
>> Ok, I'll weigh in -- as much as I dislike agreeing with John[0], I =
too
>> believe that having this easy to do in Javascript (and php and =
vbscript
>> and  rexx and asp and=8A) is really important.
>=20
> Great, thanks for weighing in, its good to see that there is more =
support
> for one way over another (regardless of which way that is). For the =
record
> though:
>=20
> Php =3D dns_get_record -
> http://us2.php.net/manual/en/function.dns-get-record.php
> Vbscript and ASP/ASP.net can load objects using windows com object =
model,
> there are many many com DNS objects around
>=20

Ok, also fair 'nuff -- obviously enough I'm not a php / vbscript person =
(for which I thank the good lord every day!), I'm a python / c person.

>=20
>=20
>>=20
>> No, but toning it down a little might be nice=8A
>=20
> Understood, I will attempt to be 'nicer' in my emails, for the record
> though, nothing in my emails is meant to be attacking or negative =
towards
> anyone in any way and I apologise if any one has taken it as such.
> I am
> simply eager to understands others views and getting them to backup =
the
> assertions they are making. I will look over past emails and see where =
I
> have gone wrong here. If you could help me out by pointing out to me =
the
> emails of concern to me would be appreciated.

Ok -- I found the bit just above where I inserted this to be snotty / =
passive aggressive=85 but then again, I was writing this while sitting =
on a plane with a *really* annoying seatmate who kept leaning over to =
look at my screen, bumping my armrest and explaining his views on =
politics, so it is more than possible that I was being overly sensitive=85=
=20
<we can now hug and make up>.

W

>=20
>>=20
>> W
>>=20
>> [0]: Just on principle...
>>=20
>>>=20
>>>> Really.
>>>>=20
>>>> R's,
>>>> John
>>>> _______________________________________________
>>>> weirds mailing list
>>>> weirds@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/weirds
>>>=20
>>> _______________________________________________
>>> weirds mailing list
>>> weirds@ietf.org
>>> https://www.ietf.org/mailman/listinfo/weirds
>>>=20
>>=20
>> --
>> What our ancestors would really be thinking, if they were alive =
today,
>> is: "Why is it so dark in here?"
>>=20
>>   -- (Terry Pratchett, Pyramids)
>>=20
>>=20
>=20

--
Life is a concentration camp.  You're stuck here and there's no way out =
and you can only rage impotently against your persecutors.
                -- Woody Allen





From chris@ausregistry.com.au  Sun Jul 22 22:20:13 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6530E21F86D3 for <weirds@ietfa.amsl.com>; Sun, 22 Jul 2012 22:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.263
X-Spam-Level: 
X-Spam-Status: No, score=-1.263 tagged_above=-999 required=5 tests=[AWL=0.633,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yIS2XWLQ7pY2 for <weirds@ietfa.amsl.com>; Sun, 22 Jul 2012 22:20:12 -0700 (PDT)
Received: from mx02.ausregistry.net.au (mx02.ausregistry.net.au [202.65.15.42]) by ietfa.amsl.com (Postfix) with ESMTP id D3B4821F866C for <weirds@ietf.org>; Sun, 22 Jul 2012 22:20:10 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron02.off08.stkildard.vic.ausregistry.com.au with ESMTP; 23 Jul 2012 15:20:09 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Mon, 23 Jul 2012 15:19:55 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: Warren Kumari <warren@kumari.net>
Date: Mon, 23 Jul 2012 15:20:07 +1000
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: Ac1oeRfgmwUHQ9cZSUCqM18N3+WyTwAD5BWA
Message-ID: <8CEF048B9EC83748B1517DC64EA130FB729CE5F066@off-win2003-01.ausregistrygroup.local>
References: <CC32E466.341EE%chris@ausregistry.com.au> <15BE2D22-33E6-45CE-9D88-92CC6E1BFE9B@kumari.net>
In-Reply-To: <15BE2D22-33E6-45CE-9D88-92CC6E1BFE9B@kumari.net>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "carlos@lacnic.net" <carlos@lacnic.net>, John Levine <johnl@taugh.com>, "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 05:20:13 -0000

QWxsLA0KDQpUaGlzIGlzIG15IGxhc3QgZW1haWwgb24gdGhpcyBzdWJqZWN0IChhcHBsYXVzZSBJ
IGFtIHN1cmUpLCBhbmQgSSBhbSBhdHRlbXB0aW5nIHRvIGJlIGFzIGNsZWFyIGFuZCBjb25jaXNl
IGFzIHBvc3NpYmxlLiBJIHdpbGwgaGFwcGlseSBjb250aW51ZSB0byBkaXNjdXNzIGFueSBvZiB0
aGlzIHdpdGggYW55b25lIG9mZiBsaXN0IHNob3VsZCB5b3Ugd2FudC4NCg0KSm9obiBoYXMgYXNz
ZXJ0ZWQgdGhhdCB0aGVyZSB3aWxsIGJlIG1vcmUgY2xpZW50cyB0aGFuIHNlcnZlcnMgYW5kIHRo
dXMgdGhlIHByaW5jaXBhbCBzaG91bGQgYmUgdG8gZG8gd2hhdCBpcyBiZXR0ZXIgZm9yIGNsaWVu
dHMgcmF0aGVyIHRoYW4gc2VydmVycy4gSW4gcHJpbmNpcGFsIEkgaGF2ZSBubyBpc3N1ZSB3aXRo
IHRoaXMgc2VudGltZW50Lg0KDQpPYnZpb3VzbHkgSSBhbSBzcGVha2luZyBhcyBhIGRvbWFpbiBu
YW1lIFJlZ2lzdHJ5IGFuZCB3ZSBhcmUgZGlyZWN0bHkgYWZmZWN0ZWQgYnkgdGhlIGJvb3RzdHJh
cHBpbmcgcHJvY2Vzc2VzLiBGb3Igbm93IEkgYW0gaWdub3JpbmcgdGhlIElQIGFkZHJlc3MgcmVn
aXN0cnkgc2lkZSBvZiB0aGluZ3MsIGFzIGlmIHRoZSBib290c3RyYXAgcHJvY2VzcyBmb3IgdGhl
IHR3byBpcyBub3QgY29uc2lzdGVudCBJIGRvbuKAmXQgdGhpbmsgaXQgaXMgYSBiaWcgZGVhbCAo
YW5kIG90aGVycyBoYXZlIHNhaWQgYXMgbXVjaCBhcyB3ZWxsKS4NCg0KQXMgZmFyIGFzIEkgY2Fu
IHRlbGwgdGhlcmUgYXJlIHR3byBwb3RlbnRpYWwgc29sdXRpb25zIGZvciBkb21haW4gbmFtZSBi
b290c3RyYXBwaW5nIG9uIHRoZSB0YWJsZSBhdCB0aGUgbW9tZW50IHRoYXQgbWFrZSBzZW5zZToN
Cg0Kd2VpcmRzLXNlcnZlci48dGxkPiBbU1JWfE5BVFBSXSBYWFhYWFhYDQoNCm9yDQoNCndlaXJk
cy1zZXJ2ZXIuPHRsZD4gW0F8QUFBQXxDTkFNRXxOU10gWFhYWFhYWFgNCg0KSm9obiBhbmQgSSBo
YXZlIGNvbnRpbnVlZCBhIGRpc2N1c3Npb24gb2ZmIGxpc3QsIGFuZCBoZSBoYXMgY29udmluY2Vk
IG1lIG9mIHRoZSBmb2xsb3dpbmc6DQoNCi0gYSBzZWN1cmUgYm9vdHN0cmFwIGNhbiBiZSBpbXBs
ZW1lbnRlZCBpbiBib3RoIG1vZGVscw0KLSB0aGUgU1NMIGNlcnRpZmljYXRlIHBlciBJUCBhZGRy
ZXNzZXMgaXNzdWUgaXMgc29sdmVkIGluIHByaW5jaXBhbCBieSBTZXJ2ZXIgTmFtZSBJbmRpY2F0
aW9uIChSRkM2MDY2KSAobW9yZSBvbiB0aGlzIGJlbG93KQ0KDQpTbyB0aGlzIGxlYXZlcyBtZSB3
aXRoIHRoZSBmb2xsb3dpbmcgY29tbWVudHMgZm9yIG90aGVycyB0byBjb25zaWRlcjoNCg0KLSB0
aGVyZSBpcyBubyBjbGllbnQgaW1wbGVtZW50YXRpb24gaXNzdWUgd2l0aCB1c2luZyBTUlYgb3Ig
TkFQVFIgcmVjb3JkczoNCkZvciBqYXZhc2NyaXB0IHJ1bm5pbmcgaW4gdGhlIGJyb3dzZXIsIHRo
ZSBjbGllbnQgY2FuIGNhbGwgYmFjayB0byB0aGUgc2VydmVyIHdoZXJlIGl0IGdvdCB0aGUgamF2
YXNjcmlwdCBjb2RlIHRvIHJ1biBpbiB0aGUgZmlyc3QgcGxhY2UgLSB0aGVyZSBpcyBubyBzZWN1
cml0eSBvciBhbnkgb3RoZXIgaXNzdWUgd2l0aCB0aGlzIC0gZm9yIHRob3NlIGludGVyZXN0ZWQg
SSBjYW4gc2VuZCB5b3UgcHJvb2Ygb2YgdGhpcy4gRm9yIHNlcnZlciBzaWRlIGphdmFzY3JpcHQg
dXNlICh3aGljaCB3YXMgd2hhdCB3YXMgYm91Z2h0IHVwIHRvIG1lIGFzIHRoZSAnb3RoZXInIGph
dmFzY3JpcHQgcmVhc29uIHdoeSB3ZSBjYW4ndCBkbyB0aGlzKSwgbW9zdCBpZiBub3QgYWxsIHNl
cnZlci1zaWRlIGphdmFzY3JpcHQgaW1wbGVtZW50YXRpb25zIGFyZSBhZGRpbmcgc2NyaXB0aW5n
IHN1cHBvcnQgdG8gb3RoZXIgbGFuZ3VhZ2VzIGFuZCB0aHVzIGNhbiBtYWtlIGNhbGxzIG91dCB0
byB0aGF0IHVuZGVybHlpbmcgbGFuZ3VhZ2Ugd2l0aG91dCBpc3N1ZS4gTm9kZS5qcyAodGhlIG9u
bHkgc3RhbmRhbG9uZSBqYXZhc2NyaXB0IGZyYW1ld29yayBJIGNvdWxkIGZpbmQpIGhhcyBzb2Nr
ZXQgYmFzZWQgQVBJcyBhbmQgRE5TIGJhc2VkIEFQSXMgYnVpbHQgaW50byBpdC4gVGhlcmUgaXMg
bm8gbGltaXRhdGlvbiBvZiB0aGUgSmF2YXNjcmlwdCBsYW5ndWFnZSB0aGF0IG1ha2VzIGltcGxl
bWVudGluZyBhIFNSViBvciBOQVBUUiBsb29rdXAgaW1wb3NzaWJsZSAob3IgZXZlbiBkaWZmaWN1
bHQpLg0KDQpUaGVyZSB3YXMgYW4gaXNzdWUgcmFpc2VkIHRoYXQgeW91IGNhbid0IGRvIEROUyBs
b29rdXBzIGluIG90aGVyIGxhbmd1YWdlcywgYnV0IHRoaXMgaXMgYWxzbyBpbmNvcnJlY3QgZm9y
IGFsbCBleGFtcGxlcyByYWlzZWQgdG8gZGF0ZSwgYW5kIGZ1cnRoZXIgdG8gdGhpcywgd2hhdCBp
cyB0aGUgcmVsZXZhbmNlIC0gaWYgdGhlcmUgd2FzIG9ubHkgb25lIGxhbmd1YWdlIHdoZXJlIHdl
IGNvdWxkIGRvIEROUyBsb29rdXBzIHRoZW4geWVzIHJlcXVpcmluZyBhIEROUyBsb29rdXAgd291
bGQgYmUgcHJvYmxlbWF0aWMsIGJ1dCBpdCBzZWVtcyB0aGF0IGZvciBldmVyeSBtYWpvciBwcm9n
cmFtbWluZyBsYW5ndWFnZSBvdXQgdGhlcmUsIEROUyBsb29rdXBzIGFyZSBub3QgYW4gaXNzdWUu
IFdyaXRpbmcgYSBXRUlSRFMgY2xpZW50IGluIEhBU0tFTCBvciBQUk9MT0cgd2lsbCBiZSBkaWZm
aWN1bHQgYXQgYmVzdCwgYW5kIG1heWJlIG5vdCBldmVuIHBvc3NpYmxlLCBidXQgaWYgSSB3ZXJl
IHRvIHN1Z2dlc3Qgd2UgYnJpbmcgdGhvc2UgY29uc3RyYWludHMgb250byBvdXIgcHJvdG9jb2wg
ZGV2ZWxvcG1lbnQgeW91IHdvdWxkIGFsbCwgcmlnaHRseSBzbywgbGF1Z2ggYXQgbWUgYW5kIHRl
bGwgbWUgdG8gc29kIG9mZi4NCg0KTmV4dCwgaWYgd2UgYXJlIHRvIGNvbnNpZGVyIGluIGJyb3dz
ZXIgZXhlY3V0aW5nIGphdmFzY3JpcHQgYXMgYW4gaXNzdWUsIG1vc3Qgb2YgeW91ciBhdXRoZW50
aWNhdGlvbiBtZWNoYW5pc21zIGFyZSBub3QgZ29pbmcgdG8gYmUgc3RyYWlnaHQgZm9yd2FyZCBp
ZiBwb3NzaWJsZSBhdCBhbGwuIFNvIHRoZSBpbiBicm93c2VyIGphdmFzY3JpcHQgY2xpZW50IHdp
bGwgZ2VuZXJhbGx5IG9ubHkgYmUgYWJsZSB0byBkbyB1bmF1dGhlbnRpY2F0ZWQgbG9va3Vwcywg
d2hpY2ggbWVhbnMgbW9zdCBtb3JlIHRoYW4gYmFzaWNhbGx5IHVzZWZ1bCBjbGllbnRzIHdpbGwg
bmVlZCB0byBiZSB3cml0dGVuIGluIG90aGVyIGxhbmd1YWdlcyBhbnl3YXkuIEN1cnJlbnRseSB3
ZSBhcmUgZGlzY3Vzc2luZyBtYWtpbmcgYSBkZXNpZ24gdHJhZGUgb2ZmIGRlY2lzaW9uIGFib3V0
IG91ciBwcm90b2NvbCBvbiBhIHZlcnkgbGltaXRlZCBkYXRhIHNldCAob25lIHdoaWNoIEknbSB3
b25kZXJpbmcgaG93IGl0IHdhcyBjb2xsZWN0ZWQgaW4gdGhlIGZpcnN0IHBsYWNlIC0gYW5vdGhl
ciBjb252ZXJzYXRpb24gZm9yIG9mZiBsaXN0KSwgdGhlcmUgaXMgbm8gcmVhbCBldmlkZW5jZSB0
aGF0IG9uY2UgV0VJUkRTIGlzIGluIHdpZGVzcHJlYWQgdXNlIHRoYXQgSmF2YXNjcmlwdCB3aWxs
IGJlIHRoZSBsYW5ndWFnZSBvZiBjaG9pY2UgZm9yIGltcGxlbWVudGluZyBhIHJlYWwgY2xpZW50
LCBJIHdpbGwgYXNzZXJ0IHRoYXQgcGVvcGxlIHdpbGwgd3JpdGUgY2xpZW50cyBpbiBKYXZhLCBD
L0MrKywgUGVybCBhbmQgUEhQIGF0IGxlYXN0Lg0KDQotIHRoZXJlIGlzIGEgcmVhbCBvcGVyYXRp
b25hbCBpc3N1ZSBlbmNvdW50ZXJlZCBieSBmb3JjaW5nIHJlZ2lzdHJpZXMgcmVzcG9uc2libGUg
Zm9yIG9wZXJhdGluZyBtdWx0aXBsZSBUTERzIHRvIG5lZWQgdG8gc3VwcG9ydCBhbiBTU0wgc2l0
ZSAoYW5kIGNvcnJlc3BvbmRpbmcgY2VydGlmaWNhdGUpIGZvciBlYWNoIFRMRCBpdCBvcGVyYXRl
cw0KWWVzIGFyZ3VhYmx5IGl0IGlzIG1hbmFnZWFibGUsIGJ1dCBpZiB3ZSBoYXZlIGEgd2F5IHRv
IG5vdCBoYXZlIHRvIGluY3VyIHRoaXMgcmlzayB0aGVuIHdoeSBtYWtlIHVzPyBJZiB0aGVyZSBp
cyBhIGp1c3RpZmlhYmxlIHJlYXNvbiBmb3IgbWUgdG8gaGF2ZSB0byBkbyB0aGlzLCB0aGVuIHNv
IGJlIGl0IEkgd2lsbCBkbyBpdCwgYnV0IHRoZSBKYXZhc2NyaXB0IHJlYXNvbiBpcyBwdXJlIGZp
Y3Rpb24gKEkgaGF2ZSBwcmVzZW50ZWQgbXVjaCBldmlkZW5jZSB0byB0aGlzIGZhY3QgKGNvbnRh
Y3QgbWUgb2ZmIGxpc3QgYW5kIEkgd2lsbCBzZW5kIHlvdSBtb3JlIGlmIHJlcXVpcmVkKSAtIG5v
IG9uZSBoYXMgcHJlc2VudGVkIGFueSBldmlkZW5jZSBwcm92aW5nIG90aGVyd2lzZSkgYW5kIHRo
aXMgaXMgdGhlIGJhc2VzIG9mIG15IHByb2JsZW0uIEkgYW0gYWxsIGZvciBtYWtpbmcgdGhpbmdz
IGJldHRlciBmb3IgY2xpZW50cyBhbmQgc2VydmVycyB0YWtpbmcgb24gbW9yZSByZXNwb25zaWJp
bGl0eSwgaG93ZXZlciBvbmx5IHdoZW4ganVzdGlmaWVkLiBPcGVyYXRpb25hbGx5IGZvcmNpbmcg
bWUgdG8gZG8gdGhpcyBtZWFucyBhIGxhcmdlciBudW1iZXIgb2YgY2VydGlmaWNhdGVzIHRvIG1h
bmFnZSBhbmQgcmVuZXcgKG1vcmUgdGhpbmdzIHRvIGdvIHdyb25nKSBhbmQgaXQgd2lsbCBiZSBh
Y3R1YWxseSBmb3JjaW5nIG1lIHRvIG1vdmUgYXdheSBmcm9tIEphdmEgKHRoYXTigJlzIHJpZ2h0
IEphdmEpIG9yIGVhdCBsb3RzIG9mIElQcyEgQ3VycmVudGx5IHRoZSBvbmx5IGphdmEgYXBwbGlj
YXRpb24gY29udGFpbmVyIEkgY2FuIGZpbmQgdGhhdCBzdXBwb3J0cyBTZXJ2ZXIgTmFtZSBJbmRp
Y2F0aW9uIChSRkM2MDY2KSBpcyB0aGUgbGF0ZXN0IHZlcnNpb24gb2YgVG9tY2F0IGFuZCBldmVu
IHRoZW4gb25seSB3aGVuIHJ1bm5pbmcgb24gSmF2YSA3LiBOb3cgdGhlcmUgYXJlIG1hbnkgb3Jn
YW5pc2F0aW9ucyAob3VycyBpbmNsdWRlZCkgd2hvIHdvbid0IHVzZSBKYXZhNyBpbiBwcm9kdWN0
aW9uIGp1c3QgeWV0IHVudGlsIGl0IGRlbW9uc3RyYXRlcyBpdHNlbGYgdG8gYmUgc3RhYmxlLCBh
bmQgd2hvIGhhdmUgbGFyZ2UgYXBwbGljYXRpb25zIChyZWdpc3RyaWVzKSB0aGF0IHVzZSBkaWZm
ZXJlbnQgSmF2YSBhcHBsaWNhdGlvbiBjb250YWluZXJzIHRoYXQgZG9u4oCZdCBzdXBwb3J0IHRo
ZSByZXF1aXJlZCBTTkkgdGVjaG5vbG9neSB5ZXQuIEdyYW50ZWQgdGhpcyBpcyBvdXIgcHJvYmxl
bSB0byBzb2x2ZSwgYW5kIEkgd2lsbCBzb2x2ZSBpdCBpZiBJIG5lZWQgdG8sIGJ1dCBJIGFtIG5v
dCBzZWVpbmcgdGhlIHJlYXNvbiB5ZXQgd2h5IHlvdSBhcmUgZm9yY2luZyBtZSB0byBzb2x2ZSBp
dC4NCg0KLSB0aGUgU1JWL05BUFRSIGFwcHJvYWNoIGlzIHNpbXBseSBtb3JlIGZsZXhpYmxlDQog
bnVmZiBzYWlkIC0gaXQgc2ltcGx5IGlzDQoNClNvIHRoYXTigJlzIGl0LCBJIGFzayB5b3UgYWxs
IHRvIGNvbnNpZGVyIHRoZXNlIHRoaW5ncyBhbmQgc3BlYWsgdXAgb25lIHdheSBvciB0aGUgb3Ro
ZXIsIEkgd2lsbCBsaXZlIHdpdGggdGhlIEEvQUFBQS9DTkFNRS9OUyBzb2x1dGlvbiBpZiBwZW9w
bGUgdHJ1bHkgYmVsaWV2ZSBpdCBpcyBqdXN0aWZpZWQsIGJ1dCBJIGZvciBvbmUgY2FuJ3Qgc2Vl
IGhvdywgYW5kIGVuY291cmFnZSB0aG9zZSBvdGhlcnMgb24gdGhlIGxpc3QgdGhhdCB3aWxsIGJl
IGFmZmVjdGVkIGJ5IHRoYXQgZGVjaXNpb24gdG8gc3BlYWsgdXAuDQoNCkhhcHB5IHRvIGRpc2N1
c3MgZnVydGhlciB3aXRoIGFueW9uZSBvZmYgbGlzdC4NCg0KVGhhbmtzDQoNCkNocmlzDQoNCg0K

From andy@arin.net  Mon Jul 23 10:01:56 2012
Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AFD111E808E for <weirds@ietfa.amsl.com>; Mon, 23 Jul 2012 10:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0OIwVEtbEgie for <weirds@ietfa.amsl.com>; Mon, 23 Jul 2012 10:01:55 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 8369811E80BD for <weirds@ietf.org>; Mon, 23 Jul 2012 10:01:52 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id 7CD962135F0; Mon, 23 Jul 2012 13:01:51 -0400 (EDT)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id 00EA921355C; Mon, 23 Jul 2012 13:01:51 -0400 (EDT)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Mon, 23 Jul 2012 13:01:45 -0400
Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0298.004; Mon, 23 Jul 2012 13:01:50 -0400
From: Andy Newton <andy@arin.net>
To: Chris Wright <chris@ausregistry.com.au>
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: AQHNaJMF8CWsNCcwXUmdcJe3DayQBJc3W5qA
Date: Mon, 23 Jul 2012 17:01:49 +0000
Message-ID: <584D09FE-7347-46EF-BE7A-B2852E0A07F4@arin.net>
References: <CC32E466.341EE%chris@ausregistry.com.au> <15BE2D22-33E6-45CE-9D88-92CC6E1BFE9B@kumari.net> <8CEF048B9EC83748B1517DC64EA130FB729CE5F066@off-win2003-01.ausregistrygroup.local>
In-Reply-To: <8CEF048B9EC83748B1517DC64EA130FB729CE5F066@off-win2003-01.ausregistrygroup.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.1.56]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <681C6B9965922F48A0C970E05AB0A0A2@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "carlos@lacnic.net" <carlos@lacnic.net>, "weirds@ietf.org" <weirds@ietf.org>, John Levine <johnl@taugh.com>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 17:01:56 -0000

On Jul 23, 2012, at 1:20 AM, Chris Wright wrote:

> John and I have continued a discussion off list, and he has convinced me =
of the following:
>=20
> - a secure bootstrap can be implemented in both models

I think this is true. However, I want to push back against the notion that =
ALL interactions have to be secured. Certainly we should support it, but if=
 people wish to do lookups insecurely that should be their option. We've be=
en running our service now for over two years and in that time have never r=
eceived a request to do it over HTTPS.

> - there is no client implementation issue with using SRV or NAPTR records=
:

And there is nothing stopping us from forcing clients to implement DNSSEC o=
r X.509 DER parsing or the necessary crypto or any of that. But just becaus=
e we can does not mean we should. Reducing complexity of the clients is par=
amount.

> For javascript running in the browser, the client can call back to the se=
rver where it got the javascript code to run in the first place - there is =
no security or any other issue with this - for those interested I can send =
you proof of this.

This sounds reasonable to me, btw. And it maybe the difference between what=
 has been called a centralized redirector and a helper in these threads. If=
 you dynamically execute code from a website, then you are already dependen=
t on that website and there is no extra security issue with trusting them f=
or help in the bootstrap.

It should also be noted that from a client complexity point of view, a help=
er site means that bootstrapping is no different than simply following redi=
rects and therefore it reduces client complexity.

> Currently the only java application container I can find that supports Se=
rver Name Indication (RFC6066) is the latest version of Tomcat and even the=
n only when running on Java 7.

This is an aside, but I'd think using Apache httpd to front your Java conta=
iners would solve this problem.

> - the SRV/NAPTR approach is simply more flexible
> nuff said - it simply is

I've yet to hear a reason why SRV/NAPTR is more appropriate than U-NAPTR.

-andy=

From johnl@iecc.com  Mon Jul 23 11:52:47 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D291021F84EF for <weirds@ietfa.amsl.com>; Mon, 23 Jul 2012 11:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.134
X-Spam-Level: 
X-Spam-Status: No, score=-111.134 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kewydbxm-kO0 for <weirds@ietfa.amsl.com>; Mon, 23 Jul 2012 11:52:46 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 2FB7A21F850B for <weirds@ietf.org>; Mon, 23 Jul 2012 11:52:44 -0700 (PDT)
Received: (qmail 32035 invoked from network); 23 Jul 2012 18:52:43 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 23 Jul 2012 18:52:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=500d9d7a.xn--yuvv84g.k1207; i=johnl@user.iecc.com; bh=m1Vt2dxShi4GPTgkhQypyVazCQ/uk81UjClnH/nUMQo=; b=XKUVBMQs8XHYKU6+8Tu85XYyTHMxakmT91sg6g391f7KMRgB7fL+u99auT5Hs3iiPR315qQX5+Ny331dB/3Q5ZargZEdIPs7Ls7vKs4Bl/5wtLZdiQnXNr9s4YgfQjCXDkCLugnpbnbEXWdYQ6h3k7QLMQWu/ld9sanNnSN1Sug=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=500d9d7a.xn--yuvv84g.k1207; olt=johnl@user.iecc.com; bh=m1Vt2dxShi4GPTgkhQypyVazCQ/uk81UjClnH/nUMQo=; b=lGZ5wHg8UFUEl4a4RRwl1BrAzYAwEYuOGv9RyyHryWlk3c1rRIbbJMaBOcW1nPpKpzs7FpEXmTwNfEKCQ+SQOCIVHFYYjRujrHIKQ3pEbQM/tRrYel+VjanhnpnZYOHR35VLLsXDeFD1qiVpypj9BlF62NCX+Gb8rPUFpmNKgBI=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 23 Jul 2012 18:52:20 -0000
Message-ID: <20120723185220.90066.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <584D09FE-7347-46EF-BE7A-B2852E0A07F4@arin.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 18:52:48 -0000

>> - the SRV/NAPTR approach is simply more flexible
>> nuff said - it simply is
>
>I've yet to hear a reason why SRV/NAPTR is more appropriate than U-NAPTR.

Given that some cruddy client libraries still don't support NAPTR, and
that most of the things people are proposing to do for bootstraps can
be done with slightly more CNAME records, I don't understand why we
need NAPTR at all.

R's,
John

PS: When designing a standard, extra flexibility is often a bug.

From bje@apnic.net  Mon Jul 23 20:42:17 2012
Return-Path: <bje@apnic.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7473811E810E for <weirds@ietfa.amsl.com>; Mon, 23 Jul 2012 20:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, J_CHICKENPOX_64=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-pLGw4mhuOW for <weirds@ietfa.amsl.com>; Mon, 23 Jul 2012 20:42:17 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 8DFAD11E810B for <weirds@ietf.org>; Mon, 23 Jul 2012 20:42:15 -0700 (PDT)
Received: from [IPv6:2001:dc0:a000:4:71d3:fbbe:4015:793f] (unknown [IPv6:2001:dc0:a000:4:71d3:fbbe:4015:793f]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 0FAAAB66BE for <weirds@ietf.org>; Tue, 24 Jul 2012 13:42:12 +1000 (EST)
From: Byron Ellacott <bje@apnic.net>
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_5AB37EB2-A777-43CB-A53E-C4CDF758D5CD"; protocol="application/pkcs7-signature"; micalg=sha1
Date: Tue, 24 Jul 2012 13:42:11 +1000
In-Reply-To: <20120723185220.90066.qmail@joyce.lan>
To: weirds@ietf.org
References: <20120723185220.90066.qmail@joyce.lan>
Message-Id: <348E4548-FEFE-494B-AE41-ADF807927DC2@apnic.net>
X-Mailer: Apple Mail (2.1278)
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 03:42:17 -0000

--Apple-Mail=_5AB37EB2-A777-43CB-A53E-C4CDF758D5CD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi all,

On 24/07/2012, at 4:52 AM, John Levine wrote:

>>> - the SRV/NAPTR approach is simply more flexible
>>> nuff said - it simply is
>>=20
>> I've yet to hear a reason why SRV/NAPTR is more appropriate than =
U-NAPTR.
>=20
> Given that some cruddy client libraries still don't support NAPTR, and
> that most of the things people are proposing to do for bootstraps can
> be done with slightly more CNAME records, I don't understand why we
> need NAPTR at all.


There's a trade-off between client complexity for NAPTR, and server =
complexity to support SNI or manage multiple CA certs.  Both issues are =
"real" in that someone would have to deal with them.  Both issues are =
not intractable.  I favour putting the complexity on the server side.  I =
favour this particularly because adding the processing required to go =
from a set of NAPTR records fetched, to connecting to the right server, =
would be as much as or more processing than is required to go from =
connecting to the right server to having a parsed weirds response in =
memory.  It would not be a doubling of complexity to support SNI on the =
server side, nor to manage 100 SSL certs.

I'd like to note that the ability to host web content, including =
javascript, is different to the ability to host web server scripts; =
there would be a set of users who could include a weirds script on their =
page, but not put a DNS resolver service on their web host.  I think =
this would be a less common issue than just the complexity of processing =
NAPTRs, but when it is an issue, it's effectively an intractable =
problem: changing web host providers is a non-solution, IMO.

I'm curious about how strong the perceived need is for channel security, =
too.  Is it something we should consider mandatory, something that =
should be optional at service operator discretion, or perhaps related to =
differential access class needs?

Also, there's a taxonomy invented by ICANN for these services, though =
they sadly forgot what the first "N" in ICANN stands for.  Rather than =
weirds.arpa, I would prefer us to use rd-ds.arpa, taking the "DNRD-DS" =
taxonomy and dropping the "DN" part :-)

  Byron


--Apple-Mail=_5AB37EB2-A777-43CB-A53E-C4CDF758D5CD
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIEBjCCBAIw
ggLqoAMCAQICCCoPITf60ZNDMA0GCSqGSIb3DQEBBQUAMHMxETAPBgNVBAMMCHN0YWZmLWNhMRIw
EAYDVQQLDAlUZWNobmljYWwxFjAUBgNVBAoMDUFQTklDIFB0eSBMdGQxETAPBgNVBAcMCEJyaXNi
YW5lMRIwEAYKCZImiZPyLGQBGRYCY2ExCzAJBgNVBAYTAkFVMB4XDTExMTEyODAxNTEzNloXDTEy
MTEyNzAxNTEzNlowgZIxGTAXBgoJkiaJk/IsZAEBDAliamUtc3RhZmYxEjAQBgNVBAMMCWJqZS1z
dGFmZjEOMAwGA1UEKgwFQnlyb24xETAPBgNVBAQMCEVsbGFjb3R0MQ8wDQYDVQQLDAZQZW9wbGUx
FjAUBgNVBAoMDUFQTklDIFB0eSBMdGQxFTATBgoJkiaJk/IsZAEZFgVzdGFmZjCCASIwDQYJKoZI
hvcNAQEBBQADggEPADCCAQoCggEBANVQo/BOmY5CCWNeAldlgoWZKOzIZpOsFzD6NB2oAErtclDu
uiZsXfl+L97UOwUlhu1eGlY5gKuAhGcrEBvDgTT1eEr3vkdKILhJw78s5n8eLOWrmhPKBnW8gSn9
7MbAxVQx3V1/RpToKAF8cR4il03Z7mveaBQbaivM2jReHcgfJPt9w0qhTVZO2POLuVClRcExaNt1
h+QdMLa6VU5x7rJo9JFqjTAvJzMApW+WY/7oumR9+4a9ZGThlETI2b83XAMrrJ7DHm237Jskgl+X
FGILIq8zOhNiAbhEg+gAyJ8bOzwwydDY+ggWQ466duZZq4wxmr1+YhxVf51v2R5MSicCAwEAAaN6
MHgwHQYDVR0OBBYEFIQXSivz3cLpaFy23DdhpGhyyo5pMAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgw
FoAU4D23klvuLqOyPnnbRaswQi8BS6wwDgYDVR0PAQH/BAQDAgHyMBgGA1UdEQQRMA+BDWJqZUBh
cG5pYy5uZXQwDQYJKoZIhvcNAQEFBQADggEBAEk9zi8BTUEY4rqDGEIFDNIpmX/yS3fTah39Mele
pV93sRsjqLy2G47vhhnkgSTEWV2jJOD7tjzjswxtWUL6KG36dUDVL3XbQ1OObxkiDJbqje4BoWrd
a8/5PoIPC0hkSDXGoitvoXkL8Pd9x9Y+kyMlKo1C0lk5bCUG4yjk5wVLuSSm5m+KZ3+YVdPp6dKp
C0DRhvFdsrz2zIOT/sWheCQO0HRU300UYngB/xoqc1KWH2dROIUhLqwtyoCQbQKQjW9C+JMMw2Ij
vfVXJZGMWjbp5l8RQeUSJ+0vVJXJbIL6PfEsyQupUV3AJsSTRmtllqzCBCz2Abd14xyeqw0eJfwx
ggMtMIIDKQIBATB/MHMxETAPBgNVBAMMCHN0YWZmLWNhMRIwEAYDVQQLDAlUZWNobmljYWwxFjAU
BgNVBAoMDUFQTklDIFB0eSBMdGQxETAPBgNVBAcMCEJyaXNiYW5lMRIwEAYKCZImiZPyLGQBGRYC
Y2ExCzAJBgNVBAYTAkFVAggqDyE3+tGTQzAJBgUrDgMCGgUAoIIBgzAYBgkqhkiG9w0BCQMxCwYJ
KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjA3MjQwMzQyMTFaMCMGCSqGSIb3DQEJBDEWBBQD
MJNlqJ1SnpnbwM+JJesaW6WFrzCBjwYJKwYBBAGCNxAEMYGBMH8wczERMA8GA1UEAwwIc3RhZmYt
Y2ExEjAQBgNVBAsMCVRlY2huaWNhbDEWMBQGA1UECgwNQVBOSUMgUHR5IEx0ZDERMA8GA1UEBwwI
QnJpc2JhbmUxEjAQBgoJkiaJk/IsZAEZFgJjYTELMAkGA1UEBhMCQVUCCCoPITf60ZNDMIGRBgsq
hkiG9w0BCRACCzGBgaB/MHMxETAPBgNVBAMMCHN0YWZmLWNhMRIwEAYDVQQLDAlUZWNobmljYWwx
FjAUBgNVBAoMDUFQTklDIFB0eSBMdGQxETAPBgNVBAcMCEJyaXNiYW5lMRIwEAYKCZImiZPyLGQB
GRYCY2ExCzAJBgNVBAYTAkFVAggqDyE3+tGTQzANBgkqhkiG9w0BAQEFAASCAQAKgm8IB7EK0xYA
z9jLhjwwn9MMlBhMtZcqwRn0IVZuE6BvCjinnUxYMj3/QVK/vvGRqfKO5OTOPd33GDC9LfGafxDO
HBJ/gqQ7BtEtv7QKehZL/8hCbvFWP6nnq7m+X34xVX/kVki8sKPeBW6HTl5NzNVLAlNxipj09awK
MSvmvYH+bF+r99GFp88Yac3CrMgWEfhaZGxTzj4LWhx1wAVjhax70LbJQLyBoHPGrN6BEAUS2PRW
j/Lin1UPodtdZLxGeIDRgmxFxKQgRqBR2/yHfDeTWCHBKG+5/kAJO91wh9l4IMKlEWQYOH1fglAN
XA4v3yGNSHDJA2+q9odDNKrUAAAAAAAA

--Apple-Mail=_5AB37EB2-A777-43CB-A53E-C4CDF758D5CD--

From olaf@NLnetLabs.nl  Tue Jul 24 05:19:40 2012
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB9AC21F8636 for <weirds@ietfa.amsl.com>; Tue, 24 Jul 2012 05:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.812
X-Spam-Level: 
X-Spam-Status: No, score=-102.812 tagged_above=-999 required=5 tests=[AWL=-0.212, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WiAKd-nenyFK for <weirds@ietfa.amsl.com>; Tue, 24 Jul 2012 05:19:39 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 09EC721F8629 for <weirds@ietf.org>; Tue, 24 Jul 2012 05:19:38 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14] ([IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6OCJTOL042816 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 24 Jul 2012 14:19:31 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
X-DKIM: OpenDKIM Filter v2.5.2 open.nlnetlabs.nl q6OCJTOL042816
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1343132374; bh=fk8GbG67RlWw93Riv3kL5G77EgRCWhAUNAMXtoVn76w=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=oT8UwwQvHfnZxskCMBd2SwCUVn48eITxw9zaIe6NU9nvW5Lov8XPap53sCVg/WQci 45LzY+INTyG2CDTbtj+q2JpuNhXtKLaA2lhXWEsU9dY19yi3SHbiiLLespYcc8Nizv whLkiwDIFeA58JX7vj0Wjn8vH23/aJE7PbOV6Cgg=
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_CD20E1D3-60F3-4232-A4F4-8FA23FFD53F3"; protocol="application/pgp-signature"; micalg=pgp-sha1
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <E9EBF95B-56DB-4964-A00D-643DA069393E@arin.net>
Date: Tue, 24 Jul 2012 14:19:21 +0200
Message-Id: <D34B0140-28F6-4E14-8B9C-C18B1D6A5903@NLnetLabs.nl>
References: <20120711203242.48919.qmail@joyce.lan> <9FC1FEF3-EE0D-4CF4-BA6E-DE2A12ACB092@arin.net> <alpine.BSF.2.00.1207111728450.47528@joyce.lan> <BB77C35A-CAC7-4E11-A4EF-CC8AFCEB438D@arin.net> <alpine.BSF.2.00.1207120959530.60846@joyce.lan> <E9EBF95B-56DB-4964-A00D-643DA069393E@arin.net>
To: Andy Newton <andy@arin.net>
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Tue, 24 Jul 2012 14:19:31 +0200 (CEST)
Cc: John R Levine <johnl@taugh.com>, "<weirds@ietf.org>" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 12:19:40 -0000

--Apple-Mail=_CD20E1D3-60F3-4232-A4F4-8FA23FFD53F3
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_CA4957F6-8755-44B6-82D0-6E141A35BB17"


--Apple-Mail=_CA4957F6-8755-44B6-82D0-6E141A35BB17
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jul 17, 2012, at 3:10 PM, Andy Newton wrote:

>>>>=20
>>>> defeats the purpose.  I suppose one could use a CNAME kludge of
>>>> <tld>.wierdsservers.net or <1.2.3.4.5.6>.weirdsservers.net, =
analogous
>>>> to Rodney's whoisservers.net, that doesn't require a lookup before =
the
>>>> http query.
>>>=20
>>> Interesting. Why not XXXX.weirds.arpa?
>>=20
>> Uh, because I wasn't thinking far enough ahead?  That would involve =
IANA, but in a pretty benign way.  They'd have to update their processes =
to allow entities that have been delegated a TLD or a top level IP range =
to register and update WEIRDS servers, but it'd be no more work than =
maintaining the in-addr zone which they do now.
>=20
> I think this is workable and strikes the right balance for the needs =
of the clients vs. distributed bootstrapping.



What is 'this' in the sentence above: xxx.weirds.arpa of =
xxx.weirdsservers.net ?

NLnet
Labs
Olaf M. Kolkman

www.NLnetLabs.nl
olaf@NLnetLabs.nl

Science Park 400, 1098 XH Amsterdam, The Netherlands




--Apple-Mail=_CA4957F6-8755-44B6-82D0-6E141A35BB17
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 17, 2012, at 3:10 PM, Andy Newton wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Monaco; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite"><br =
class=3D"Apple-interchange-newline">defeats the purpose. &nbsp;I suppose =
one could use a CNAME kludge =
of<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">&lt;tld&gt;.wierdsservers.net or =
&lt;1.2.3.4.5.6&gt;.weirdsservers.net, =
analogous<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">to =
Rodney's<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"http://whoisservers.net/">whoisservers.net</a>, that doesn't =
require a lookup before =
the<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">http =
query.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Interesting. Why not =
XXXX.weirds.arpa?<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Uh, because I =
wasn't thinking far enough ahead? &nbsp;That would involve IANA, but in =
a pretty benign way. &nbsp;They'd have to update their processes to =
allow entities that have been delegated a TLD or a top level IP range to =
register and update WEIRDS servers, but it'd be no more work than =
maintaining the in-addr zone which they do now.<br></blockquote><br>I =
think this is workable and strikes the right balance for the needs of =
the clients vs. distributed =
bootstrapping.<br></span></blockquote></div><div><br></div><div><br></div>=
What is 'this' in the sentence above: xxx.weirds.arpa of <a =
href=3D"http://xxx.weirdsservers.net">xxx.weirdsservers.net</a> =
?<div><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Helvetica; font-size: =
12px; "><br class=3D"Apple-interchange-newline"><table cellspacing=3D"0" =
cellpadding=3D"0" style=3D"background-color: rgb(255, 255, 255); =
border-collapse: collapse; "><tbody><tr><td rowspan=3D"2" valign=3D"top" =
style=3D"width: 97.8px; height: 56.3px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; text-align: right; font: normal normal normal =
19px/normal 'Gill Sans'; "><font class=3D"Apple-style-span" =
color=3D"#777777"><span style=3D"letter-spacing: 0px; =
"><b>NLnet<br></b></span><span style=3D"font: normal normal normal =
24px/normal 'Gill Sans'; letter-spacing: 0px; =
">Labs</span></font></div></td><td valign=3D"top" style=3D"width: =
114.5px; height: 18.1px; border-top-style: solid; border-right-style: =
solid; border-bottom-style: solid; border-left-style: solid; =
border-top-width: 1px; border-right-width: 0px; border-bottom-width: =
1px; border-left-width: 0px; border-top-color: rgb(180, 180, 180); =
border-right-color: transparent; border-bottom-color: rgb(202, 202, =
202); border-left-color: transparent; padding-top: 5px; padding-right: =
5px; padding-bottom: 5px; padding-left: 5px; "><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 12px/normal Helvetica; "><span =
style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Olaf M. Kolkman</font></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 18.1px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 1px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: rgb(202, 202, 202); border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td valign=3D"top" =
style=3D"width: 114.5px; height: 27.2px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"http://www.NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">www.NLnetLabs.nl</font></a></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"mailto:olaf@NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">olaf@NLnetLabs.nl</font></a></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 27.2px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td colspan=3D"3" =
valign=3D"top" style=3D"width: 234.6px; height: 13.2px; padding-top: =
5px; padding-right: 5px; padding-bottom: 5px; padding-left: 5px; "><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Science Park 400, 1098 XH Amsterdam, The =
Netherlands</font></span></div></td></tr></tbody></table><div =
style=3D"color: rgb(158, 158, 158); margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail=_CA4957F6-8755-44B6-82D0-6E141A35BB17--

--Apple-Mail=_CD20E1D3-60F3-4232-A4F4-8FA23FFD53F3
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-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQIcBAEBAgAGBQJQDpLKAAoJEFRqER47aqpkQ34P/17BrMHa1lq1Dk5s35ys4z12
4i7LUMUY7z7U9MCEyRPUNTUUK63NGok6DkpI32fltK/NxgavkUT7E0T7UhoKKaJl
D23GunVHoclU1OpcVNElGnYlOCEsjok+143aaAwDBYo1Gn06ehhu34iPa/DwqHkX
PftewMtVB59ANkuj7q0QUV1nwUEhJMFgewA30AA0w5rR8T15ecsn2Mu2Pad8Fc1D
bFMprV3702wpGX5ayVXIKqs5LvaVi7uPJCG+wn4WY3HgyJKQKUHarfhF8PdA2s+n
kAPWOuqVYdMuoWZTj7Z7BIizYR1AdXuN+lsBy8zQL0s8yWqGISwXh7ayjsGjh+oN
r354dHfNXLvfXkuPUJEVroF2fQh8p6FbAvsBvCMkNTG8TjLBCiwDKtJYyyquTD3j
kgIuzgtQtQy1TnUtr7LjbZVECYFH8npIXxeHLJYzlU9avjaXJgq5fnwUSd2mImP5
c3cFzvyXYumNSxMrtci+C17E91SbuD+56zrpDx9N84pfaR4thEICcXUixdkzERnK
o5w/MK7E+hXYAdTJJMx01YIdEwS0JWMDV5KxqIRrbrZYqvC0qrH9InqEBI92rpFZ
mxkaLFe+YsN5J2YVNqX3xM6BupoZsbojL5xJqb/fw6cC37KulC4BcjnMbA+th4Oq
VuaVxN4HJJe3u1KZ8hpf
=glC2
-----END PGP SIGNATURE-----

--Apple-Mail=_CD20E1D3-60F3-4232-A4F4-8FA23FFD53F3--

From olaf@NLnetLabs.nl  Tue Jul 24 05:35:55 2012
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 353FC21F8628 for <weirds@ietfa.amsl.com>; Tue, 24 Jul 2012 05:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.769
X-Spam-Level: 
X-Spam-Status: No, score=-102.769 tagged_above=-999 required=5 tests=[AWL=-0.170, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9YaPA7AJ8mXD for <weirds@ietfa.amsl.com>; Tue, 24 Jul 2012 05:35:53 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E735321F8624 for <weirds@ietf.org>; Tue, 24 Jul 2012 05:35:52 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14] ([IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6OCZgma072748 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 24 Jul 2012 14:35:42 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
X-DKIM: OpenDKIM Filter v2.5.2 open.nlnetlabs.nl q6OCZgma072748
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1343133346; bh=dc0NksBpEYpdQrn7rsH+6xBJaR6W5iUsy01WxHzEn+E=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=DnA++YlJ/dt1xv4Rb8ncMLKMm+fdAY4oQk1LeQdDc+8JXHLZOCoIjfMrK5+gHwDoX iSZqCp79gzYI9t5824hzCucU7YiavSQhrM+NPqTqUr8nYDGwM5y1SH2JgwkgCgxiyK Qxe3KKTN6O4XLtqxePx8za/ClrtV55a4gR7E2UOM=
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_10174190-7145-4DF8-870A-69EEBCB5C14F"; protocol="application/pgp-signature"; micalg=pgp-sha1
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <alpine.BSF.2.00.1207192308240.19001@joyce.lan>
Date: Tue, 24 Jul 2012 14:35:28 +0200
Message-Id: <6D3E6026-4DAE-4DBB-B659-960FAA38BA4E@NLnetLabs.nl>
References: <8CEF048B9EC83748B1517DC64EA130FB729CD7209B@off-win2003-01.ausregistrygroup.local> <20120720011046.96838.qmail@joyce.lan> <8CEF048B9EC83748B1517DC64EA130FB729CD72111@off-win2003-01.ausregistrygroup.local> <alpine.BSF.2.00.1207192308240.19001@joyce.lan>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Tue, 24 Jul 2012 14:35:44 +0200 (CEST)
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 12:35:55 -0000

--Apple-Mail=_10174190-7145-4DF8-870A-69EEBCB5C14F
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_18454F1F-9827-4800-898F-894605F0178D"


--Apple-Mail=_18454F1F-9827-4800-898F-894605F0178D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jul 20, 2012, at 5:36 AM, John R Levine wrote:

>> They do if you turn them into their reverse DNS form. It works fine.
>=20
> Two points.  One is that rDNS zones have never had anything in them =
other than NS, CNAME, and PTR.  You'd hope that nothing strange would =
happen if you put in other stuff, but I wouldn't want to try it without =
some significant testing first.


A reverse zone is just a zone with records served by normal DNS servers. =
The DNS doesn't care about the namespace it coughs up, recursive name =
servers have no clue about the fact that they query a special-purpose =
namespace, and applications call libraries that will turn the IP =
addresses into in-addr.arpa based domain names and query for PTR =
records.  If there is other information in the zone it will only be =
served when asked for.

In absence of any clear indication that there is a significant and =
severely corrupt implementation out there I wouldn't want to dismiss =
rDNS on this particular ground.

OH, and as a case in point. About a decade ago I was around when a bunch =
of new records got thrown into the reverse zones served at the RIPE NCC, =
and while DNS clients need to set a special bit in order to retrieve =
those records I have not seen on heard any breakage because of the =
DNSKEY, RRSIG, DS and NSEC RRs that were introduced way back when.

Note that I am not giving a +1, 0, or -1 to rDNS. Only a -1 to your =
first argument.

--Olaf (no hats)


NLnet
Labs
Olaf M. Kolkman

www.NLnetLabs.nl
olaf@NLnetLabs.nl

Science Park 400, 1098 XH Amsterdam, The Netherlands




--Apple-Mail=_18454F1F-9827-4800-898F-894605F0178D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 20, 2012, at 5:36 AM, John R Levine =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Monaco; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
"><div><blockquote type=3D"cite">They do if you turn them into their =
reverse DNS form. It works fine.<br></blockquote><br>Two points. =
&nbsp;One is that rDNS zones have never had anything in them other than =
NS, CNAME, and PTR. &nbsp;You'd hope that nothing strange would happen =
if you put in other stuff, but I wouldn't want to try it without some =
significant testing =
first.</div></span></blockquote></div><div><br></div><div>A reverse zone =
is just a zone with records served by normal DNS servers. The DNS =
doesn't care about the namespace it coughs up, recursive name servers =
have no clue about the fact that they query a special-purpose namespace, =
and applications call libraries that will turn the IP addresses into =
in-addr.arpa based domain names and query for PTR records. &nbsp;If =
there is other information in the zone it will only be served when asked =
for.</div><div><br></div><div>In absence of any clear indication that =
there is a significant and severely corrupt implementation out there I =
wouldn't want to dismiss rDNS on this particular =
ground.</div><div><br></div><div>OH, and as a case in point. About a =
decade ago I was around when a bunch of new records got thrown into the =
reverse zones served at the RIPE NCC, and while DNS clients need to set =
a special bit in order to retrieve those records I have not seen on =
heard any breakage because of the DNSKEY, RRSIG, DS and NSEC RRs that =
were introduced way back when.</div><div><br></div><div>Note that I am =
not giving a +1, 0, or -1 to rDNS. Only a -1 to your first =
argument.</div><div><br></div><div>--Olaf (no =
hats)</div><div><br></div><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: Helvetica; font-size: =
12px; "><br class=3D"Apple-interchange-newline"><table cellspacing=3D"0" =
cellpadding=3D"0" style=3D"background-color: rgb(255, 255, 255); =
border-collapse: collapse; "><tbody><tr><td rowspan=3D"2" valign=3D"top" =
style=3D"width: 97.8px; height: 56.3px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; text-align: right; font: normal normal normal =
19px/normal 'Gill Sans'; "><font class=3D"Apple-style-span" =
color=3D"#777777"><span style=3D"letter-spacing: 0px; =
"><b>NLnet<br></b></span><span style=3D"font: normal normal normal =
24px/normal 'Gill Sans'; letter-spacing: 0px; =
">Labs</span></font></div></td><td valign=3D"top" style=3D"width: =
114.5px; height: 18.1px; border-top-style: solid; border-right-style: =
solid; border-bottom-style: solid; border-left-style: solid; =
border-top-width: 1px; border-right-width: 0px; border-bottom-width: =
1px; border-left-width: 0px; border-top-color: rgb(180, 180, 180); =
border-right-color: transparent; border-bottom-color: rgb(202, 202, =
202); border-left-color: transparent; padding-top: 5px; padding-right: =
5px; padding-bottom: 5px; padding-left: 5px; "><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: =
normal normal normal 12px/normal Helvetica; "><span =
style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Olaf M. Kolkman</font></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 18.1px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 1px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: rgb(202, 202, 202); border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td valign=3D"top" =
style=3D"width: 114.5px; height: 27.2px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"http://www.NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">www.NLnetLabs.nl</font></a></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"mailto:olaf@NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">olaf@NLnetLabs.nl</font></a></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 27.2px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td colspan=3D"3" =
valign=3D"top" style=3D"width: 234.6px; height: 13.2px; padding-top: =
5px; padding-right: 5px; padding-bottom: 5px; padding-left: 5px; "><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Science Park 400, 1098 XH Amsterdam, The =
Netherlands</font></span></div></td></tr></tbody></table><div =
style=3D"color: rgb(158, 158, 158); margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div></span></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_18454F1F-9827-4800-898F-894605F0178D--

--Apple-Mail=_10174190-7145-4DF8-870A-69EEBCB5C14F
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-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQIcBAEBAgAGBQJQDpaRAAoJEFRqER47aqpkL90QAKRqdTMX6lYjTXPV3Lq6NZRQ
au4XMWGK2V1KqOYGxHOMivqWehU18dbWHumiXOyZVUHqKLfwru4pkypMfOSFZ2C9
+6y67+gZbomjZxXF/c8MyJ32nNIeCnKoNvow8Dh9RDYWVvBAwdR5Xi5co2pP30O0
P52LL3TlGtgva1iGDd0t//+zoEpFf35zaaNRPNk9ItskRkOvCaHWqRTUV7jONBWd
PPSkT+XdpRjBSaz6cg5u9kKSYLUlnbVY6JkmcGjo5fc76a+ejzR30cJbpDuQYEgL
rJ/90+qbzhXYC007dDLV5ukD4/UsTBKnzM9PbbWgFe0QyNmhoShBixjQN4eo710B
6rmHetoQ62Z9wzTsdVTy4gqnGFDtap2lZqh1tvOFcFJ2Wm7q7AL0KRmjab/S8QSx
71bpvAlb2STClc2Rkkx2MYF6MzJvWA08fSGx8gAO9aD+BAKCpK+W62b6Ts2jJwMZ
UDaOO5n5JqsObZLRm2deZ7NpK1q7bMp83O0ZwdpCwzDGHTuM/RKi/CuB4hrp17B0
teSChBs9CiU40H0rjErfc0QvhNxPePNsw3mHLDPJKLwMXqhC3r/WwspXBG6T+02t
fFTNZA6t/G3Cg8hGlmrCiZEh2/RHLNB8KI5plYUaTzBqVQFJi6KtL/D/ax5YInK2
vJ1+R10uLS9gfTRheXWI
=RwyS
-----END PGP SIGNATURE-----

--Apple-Mail=_10174190-7145-4DF8-870A-69EEBCB5C14F--

From johnl@iecc.com  Tue Jul 24 07:20:53 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A3421F8655 for <weirds@ietfa.amsl.com>; Tue, 24 Jul 2012 07:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.135
X-Spam-Level: 
X-Spam-Status: No, score=-111.135 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JGIbSI0Jo-rQ for <weirds@ietfa.amsl.com>; Tue, 24 Jul 2012 07:20:53 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 93D7021F8645 for <weirds@ietf.org>; Tue, 24 Jul 2012 07:20:52 -0700 (PDT)
Received: (qmail 86525 invoked from network); 24 Jul 2012 14:20:50 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 24 Jul 2012 14:20:50 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=500eaf42.xn--btvx9d.k1207; i=johnl@user.iecc.com; bh=PD3zXOXWFgfqUzGgaw3DsObx5FTSQZ8vYrDgpGsGW9w=; b=MBOuVVLc+wh7/EELMMufXVRANXpl1yRV8AdE/9xxzgwFcO9bXXZ5u8fq/th6Y4GTD/w8R2lslkUhz1aeUQkKuusFm1jjYTNYmfJJLnPiymRZP//7+I/39B5i5uhIb07WbHtnaBRJZ6tbqtxSjFMZeWpswMvkP+GRKkTdjfhvTXw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=500eaf42.xn--btvx9d.k1207; olt=johnl@user.iecc.com; bh=PD3zXOXWFgfqUzGgaw3DsObx5FTSQZ8vYrDgpGsGW9w=; b=D/IkPHzD8E5debzfqk72wErzF93/Dn4HAF0RsWUvewjAVcCkj50gK/xRu/8sOeQSrI1Fab30iQAHFxTJoPK9MQkZP4XNcVMnUTV0Tg8y8PB7dC4+GE0hMXKNa884x1+DvQHgYfLABgnTSzPhlcn+JFhVzHaRcQ3q0/hT93dHXX0=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 24 Jul 2012 14:20:27 -0000
Message-ID: <20120724142027.35461.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <D34B0140-28F6-4E14-8B9C-C18B1D6A5903@NLnetLabs.nl>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 14:20:54 -0000

>What is 'this' in the sentence above: xxx.weirds.arpa of xxx.weirdsservers.net ?

>From my point of view, it could equally well be either.  If we decide
to bootstrap number queries a different way (e.g., start at your
closest RIR if you don't have a local copy of the IANA table), it
could be weirds.<tld> which would likely make the administration
somewhat easier.

R's,
John

From carlosm3011@gmail.com  Wed Jul 25 06:27:03 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31FE921F851E for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 06:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BMhYWurBtGrc for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 06:27:02 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9CE6521F84E2 for <weirds@ietf.org>; Wed, 25 Jul 2012 06:27:02 -0700 (PDT)
Received: by yhq56 with SMTP id 56so783891yhq.31 for <weirds@ietf.org>; Wed, 25 Jul 2012 06:27:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=S2yP1kbqMHpNI8m2XxXVQ/ajFVlbkr+FlU4oo0eQ/ts=; b=PQGXD1P2YX+tKWh8O1UXxNCUiagSoHRDBOJOLsS49g2M5/RKT7p9wDTcNtIgJ6gD/U SL9DTCRQ2HKdGvvngv2cPsv4evA2Mhz55SQCxSPjOGqJ8Ah88PjCgU/F69JtiBuhKwBG RCqvZBd0WYv83n7Gl9PVitRVdtcRaC7GpQDayCRaXTYYr6XERHdHLwoi1Eg8ORz4P4S0 /pbAfk+WF+CRPDIht2NxhwxVaUJ4oVQdJ5q3+dqAbkFequRgP3s+6RbT8w4JmJMTeiAi hgEls9/n9jm4NMMxqR+8yzNo8li7AxE474vGlEQeRfWIY25ymZ7aWmliY4w5idIgB7pW IKxA==
Received: by 10.236.75.229 with SMTP id z65mr13314870yhd.7.1343222822053; Wed, 25 Jul 2012 06:27:02 -0700 (PDT)
Received: from europa.local ([200.7.85.155]) by mx.google.com with ESMTPS id z19sm18357907anh.22.2012.07.25.06.26.59 (version=SSLv3 cipher=OTHER); Wed, 25 Jul 2012 06:27:00 -0700 (PDT)
Message-ID: <500FF421.4040509@gmail.com>
Date: Wed, 25 Jul 2012 09:26:57 -0400
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "weirds@ietf.org" <weirds@ietf.org>
References: <CC32E466.341EE%chris@ausregistry.com.au> <15BE2D22-33E6-45CE-9D88-92CC6E1BFE9B@kumari.net> <8CEF048B9EC83748B1517DC64EA130FB729CE5F066@off-win2003-01.ausregistrygroup.local> <584D09FE-7347-46EF-BE7A-B2852E0A07F4@arin.net>
In-Reply-To: <584D09FE-7347-46EF-BE7A-B2852E0A07F4@arin.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jul 2012 13:27:03 -0000

Hi! see inline:

On 7/23/12 1:01 PM, Andy Newton wrote:
>
>> - the SRV/NAPTR approach is simply more flexible
>> nuff said - it simply is
> I've yet to hear a reason why SRV/NAPTR is more appropriate than U-NAPTR.
In my mind I tend to group NAPTR and U-NAPTR as the same thing :-) But
you're right, U-NAPTR seems to me the perfect match here, since what we
need to specify is actually a mapping {name_resource, number_resource}
-> {uri_weirds_server}.

Cheers!

~Carlos

>
> -andy
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds



From Ray.Bellis@nominet.org.uk  Wed Jul 25 06:39:40 2012
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1712021F85D5 for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 06:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.533
X-Spam-Level: 
X-Spam-Status: No, score=-10.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TaNihbOGgXTw for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 06:39:39 -0700 (PDT)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id 3164F21F85D1 for <weirds@ietf.org>; Wed, 25 Jul 2012 06:39:38 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:Received:Received:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=BKUP8mo7oiSYXKtcMz3E6c7mjkLg4V62cjwtG7PHDLjBFPMMpCg+gY8e BTEqvF7kk5UsFvloWjaVGLsSHeMITXqHcJ4dA60Bv/wYQQ+rRJCbbydta Q/9IliOhqXVmI/O;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1343223579; x=1374759579; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[weirds]=20the=20bootstrap=20problem, =09Redirection=20in=20the=20RESTful=0D=0A=20WHOIS=20world |Date:=20Wed,=2025=20Jul=202012=2013:39:38=20+0000 |Message-ID:=20<603013B9-871C-4C93-B1DA-805FA16E4E2C@nomi net.org.uk>|To:=20John=20Levine=20<johnl@taugh.com>|CC: =20"weirds@ietf.org"=20<weirds@ietf.org>|MIME-Version:=20 1.0|Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<197526de-89ca-4b08-a915-d2e4dc90b7f6> |In-Reply-To:=20<20120724142027.35461.qmail@joyce.lan> |References:=20<20120724142027.35461.qmail@joyce.lan>; bh=EmaEqKNiNeFAxCPcnSdcPxBLe98gRheFLVR1StnfZwE=; b=Pp5hVUZNoOWHswWiMPBPqWDLXzfjUmJjUOmUVG5575cv2Mh72paNrvwu yHzBnmelzltfcvuYaEfzdiGCZRjDJ4S1kykefqsbYmCiOojhww88pTLx5 bbCDNSG/TjwM2ep;
X-IronPort-AV: E=Sophos;i="4.77,653,1336345200"; d="scan'208";a="34327164"
Received: from wds-exc1.okna.nominet.org.uk ([213.248.197.144]) by mx4.nominet.org.uk with ESMTP; 25 Jul 2012 14:39:36 +0100
Received: from WDS-EXC2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4]) by wds-exc1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f%19]) with mapi; Wed, 25 Jul 2012 14:39:35 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: John Levine <johnl@taugh.com>
Thread-Topic: [weirds] the bootstrap problem,	Redirection in the RESTful WHOIS world
Thread-Index: AQHNaZadpRK24Y6woUuWGpW0Hywr+Zc4awCAgAGG7gA=
Date: Wed, 25 Jul 2012 13:39:38 +0000
Message-ID: <603013B9-871C-4C93-B1DA-805FA16E4E2C@nominet.org.uk>
References: <20120724142027.35461.qmail@joyce.lan>
In-Reply-To: <20120724142027.35461.qmail@joyce.lan>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <197526de-89ca-4b08-a915-d2e4dc90b7f6>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jul 2012 13:39:40 -0000

On 24 Jul 2012, at 15:20, John Levine wrote:

> From my point of view, it could equally well be either.  If we decide
> to bootstrap number queries a different way (e.g., start at your
> closest RIR if you don't have a local copy of the IANA table), it
> could be weirds.<tld> which would likely make the administration
> somewhat easier.

That presupposes that weirds.<tld> hasn't already been registered by a norm=
al
registrant.

Ray


From olaf@NLnetLabs.nl  Wed Jul 25 07:16:20 2012
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB8521F8585 for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 07:16:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.693
X-Spam-Level: 
X-Spam-Status: No, score=-102.693 tagged_above=-999 required=5 tests=[AWL=-0.094, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iwEu21FDPkI9 for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 07:16:19 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 647F621F85DB for <weirds@ietf.org>; Wed, 25 Jul 2012 07:16:18 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14] ([IPv6:2001:7b8:206:1:ba8d:12ff:fe04:cd14]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6PEGBEb045434 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 25 Jul 2012 16:16:12 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
X-DKIM: OpenDKIM Filter v2.5.2 open.nlnetlabs.nl q6PEGBEb045434
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1343225772; bh=mY3teJniIxNy1sv+iIBtSwcfifSnalH54cAKSyKcYCA=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=y7tfoRxV3wG9IZXUXh7W/e1xLUkM7zXIQTdvEMjaAFoFtojJOu1cS4nw5s0cPtd5r cCgCcdln0dxZIdBY5j65yBCatPoVGuvBt/gbmUBlv+6UW06kQNoici86fPLXdAvWmA jNf3C3iTdtwxwI9kPE7+f139Iwom3RW/TM9/COxY=
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/signed; boundary="Apple-Mail=_57A80B37-0E81-4B84-B364-608DA25BE6D2"; protocol="application/pgp-signature"; micalg=pgp-sha1
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <500FF421.4040509@gmail.com>
Date: Wed, 25 Jul 2012 16:16:10 +0200
Message-Id: <1AEBCDE2-5DBF-49B7-85F7-34565A43EBDF@NLnetLabs.nl>
References: <CC32E466.341EE%chris@ausregistry.com.au> <15BE2D22-33E6-45CE-9D88-92CC6E1BFE9B@kumari.net> <8CEF048B9EC83748B1517DC64EA130FB729CE5F066@off-win2003-01.ausregistrygroup.local> <584D09FE-7347-46EF-BE7A-B2852E0A07F4@arin.net> <500FF421.4040509@gmail.com>
To: carlos@lacnic.net
X-Mailer: Apple Mail (2.1278)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::53]); Wed, 25 Jul 2012 16:16:12 +0200 (CEST)
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jul 2012 14:16:20 -0000

--Apple-Mail=_57A80B37-0E81-4B84-B364-608DA25BE6D2
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_7D58556A-FCE0-4CE1-BF89-90D97A857E12"


--Apple-Mail=_7D58556A-FCE0-4CE1-BF89-90D97A857E12
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jul 25, 2012, at 3:26 PM, Carlos Martinez-Cagnazzo wrote:

> Hi! see inline:
>=20
> On 7/23/12 1:01 PM, Andy Newton wrote:
>>=20
>>> - the SRV/NAPTR approach is simply more flexible
>>> nuff said - it simply is
>> I've yet to hear a reason why SRV/NAPTR is more appropriate than =
U-NAPTR.
> In my mind I tend to group NAPTR and U-NAPTR as the same thing :-) But
> you're right, U-NAPTR seems to me the perfect match here, since what =
we
> need to specify is actually a mapping {name_resource, number_resource}
> -> {uri_weirds_server}.


The URI RR might even suffice =
(http://tools.ietf.org/html/draft-faltstrom-uri-06)

Note that the specification of the RR is stable: the code point for the =
RR TYPE has been allocated already see =
http://www.iana.org/assignments/dns-parameters





NLnet
Labs
Olaf M. Kolkman

www.NLnetLabs.nl
olaf@NLnetLabs.nl

Science Park 400, 1098 XH Amsterdam, The Netherlands




--Apple-Mail=_7D58556A-FCE0-4CE1-BF89-90D97A857E12
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jul 25, 2012, at 3:26 PM, Carlos Martinez-Cagnazzo =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi! see inline:<br><br>On 7/23/12 1:01 PM, Andy =
Newton wrote:<br><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">- the SRV/NAPTR approach is =
simply more flexible<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">nuff said - it simply =
is<br></blockquote></blockquote><blockquote type=3D"cite">I've yet to =
hear a reason why SRV/NAPTR is more appropriate than =
U-NAPTR.<br></blockquote>In my mind I tend to group NAPTR and U-NAPTR as =
the same thing :-) But<br>you're right, U-NAPTR seems to me the perfect =
match here, since what we<br>need to specify is actually a mapping =
{name_resource, number_resource}<br>-&gt; =
{uri_weirds_server}.<br></div></blockquote></div><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><br></span></div><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; ">The URI RR might even suffice =
(<a =
href=3D"http://tools.ietf.org/html/draft-faltstrom-uri-06">http://tools.ie=
tf.org/html/draft-faltstrom-uri-06</a>)</span></div><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><br></span></div><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; ">Note that the specification of =
the RR is stable: the code point for the RR TYPE has been allocated =
already see&nbsp;<a =
href=3D"http://www.iana.org/assignments/dns-parameters">http://www.iana.or=
g/assignments/dns-parameters</a></span></div><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><br></span></div><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><br></span></div><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><br></span></div><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><br></span></div><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><br =
class=3D"Apple-interchange-newline"><table cellspacing=3D"0" =
cellpadding=3D"0" style=3D"font-family: Helvetica; font-size: 12px; =
background-color: rgb(255, 255, 255); border-collapse: collapse; =
"><tbody><tr><td rowspan=3D"2" valign=3D"top" style=3D"width: 97.8px; =
height: 56.3px; border-top-style: solid; border-right-style: solid; =
border-bottom-style: solid; border-left-style: solid; border-top-width: =
1px; border-right-width: 0px; border-bottom-width: 0px; =
border-left-width: 0px; border-top-color: rgb(180, 180, 180); =
border-right-color: transparent; border-bottom-color: transparent; =
border-left-color: transparent; padding-top: 5px; padding-right: 5px; =
padding-bottom: 5px; padding-left: 5px; "><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; text-align: =
right; font: normal normal normal 19px/normal 'Gill Sans'; "><font =
class=3D"Apple-style-span" color=3D"#777777"><span =
style=3D"letter-spacing: 0px; "><b>NLnet<br></b></span><span =
style=3D"font: normal normal normal 24px/normal 'Gill Sans'; =
letter-spacing: 0px; ">Labs</span></font></div></td><td valign=3D"top" =
style=3D"width: 114.5px; height: 18.1px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 1px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: rgb(202, 202, 202); border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
"><span style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Olaf M. Kolkman</font></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 18.1px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 1px; border-left-width: 0px; border-top-color: =
rgb(180, 180, 180); border-right-color: transparent; =
border-bottom-color: rgb(202, 202, 202); border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td valign=3D"top" =
style=3D"width: 114.5px; height: 27.2px; border-top-style: solid; =
border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"http://www.NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">www.NLnetLabs.nl</font></a></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"text-decoration: underline; letter-spacing: 0px; "><a =
href=3D"mailto:olaf@NLnetLabs.nl"><font class=3D"Apple-style-span" =
color=3D"#777777">olaf@NLnetLabs.nl</font></a></span></div></td><td =
valign=3D"top" style=3D"width: 2.3px; height: 27.2px; border-top-style: =
solid; border-right-style: solid; border-bottom-style: solid; =
border-left-style: solid; border-top-width: 1px; border-right-width: =
0px; border-bottom-width: 0px; border-left-width: 0px; border-top-color: =
rgb(202, 202, 202); border-right-color: transparent; =
border-bottom-color: transparent; border-left-color: transparent; =
padding-top: 5px; padding-right: 5px; padding-bottom: 5px; padding-left: =
5px; "><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><font class=3D"Apple-style-span" =
color=3D"#777777"><br></font></div></td></tr><tr><td colspan=3D"3" =
valign=3D"top" style=3D"width: 234.6px; height: 13.2px; padding-top: =
5px; padding-right: 5px; padding-bottom: 5px; padding-left: 5px; "><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 9px/normal Helvetica; =
"><span style=3D"letter-spacing: 0px; "><font class=3D"Apple-style-span" =
color=3D"#777777">Science Park 400, 1098 XH Amsterdam, The =
Netherlands</font></span></div></td></tr></tbody></table><div =
style=3D"font-family: Helvetica; font-size: 12px; color: rgb(158, 158, =
158); margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><br></div></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></body></html>=

--Apple-Mail=_7D58556A-FCE0-4CE1-BF89-90D97A857E12--

--Apple-Mail=_57A80B37-0E81-4B84-B364-608DA25BE6D2
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-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)

iQIcBAEBAgAGBQJQD/+rAAoJEFRqER47aqpkjkwP+gP+enlFAQ6b+5uNjI97aPa/
FatJGltT1olT2435qQ2+kt2Ue4GBMlF9syfrcIZBhgRrGz1IT5ato0oQfedoCYod
yS29aXsQRcea1unTVetzdBSGhlrHD/ZssIkxWea0op8+CdT9b8t2YIPS3RXzwE4H
vm12Qn36X6ncprUe8eZ3UR84PUXZU7Ul7LjBca5wtYelkW9hUt9thkSZhBrPOAAN
B0LPhzMOFb/jMzjcEjUb8yUArxQwTrkJ24/Ov5LjStbj8vPrDq8CbLmVK2Dgzj+W
DQ+7fu+UG5au3vZTyZaUV0rO9QhQSbEGzWA7a71M6/uhabxW/tcNvEWVIqva5x7v
iCpyKyEXvRpryDCxln1EYbR25f3pMg9ZSUi8Gv+NUjLDfw4mCdOFqD0moOTUpHkh
FbaXYQzDVJtjyJ9wB1sKL8hRcUeHeLwPqGpLVBt+ArFffXJ79spUSREhk+JtpsKb
2SbaLsylJ5ufFSPNRcpYn+FEY3oYqWqhf5pnnA19GBI7ATMcPDRz9oWYOlt+xau2
2aw+cUHpmhQxMa0qeum6jfGG8m4E4KjYTkxSsmYFx5WqlDOUhy6XqKSczDUxhZWC
10JMNjQAYuawX9Oyri9AAmutbDsk49NsdPGO+0sSGkXNvFXnkndKyicsluU0aeew
TPA1DvDrmOFMjIE3XoDr
=cu4w
-----END PGP SIGNATURE-----

--Apple-Mail=_57A80B37-0E81-4B84-B364-608DA25BE6D2--

From johnl@iecc.com  Wed Jul 25 08:33:40 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7E9121F85F2 for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 08:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.136
X-Spam-Level: 
X-Spam-Status: No, score=-111.136 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Gw94qivqaBN for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 08:33:40 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id B0B4E21F857A for <weirds@ietf.org>; Wed, 25 Jul 2012 08:33:39 -0700 (PDT)
Received: (qmail 73232 invoked from network); 25 Jul 2012 15:33:37 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 25 Jul 2012 15:33:37 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=501011d1.xn--hew.k1207; i=johnl@user.iecc.com; bh=vEP18dl6FDF2Hu6AMLY6QHLE6Yp8cD3MXZX1UDTLsUQ=; b=NwzJX8FbyQGx89m1YlZgQih303ImefS4X8VX2nNddlLZlyqpPfXh5NiwvMIu/RNYZFqLx/R9TTkkxPe0qTJQqYXIxImZzGjqR6KwBIPgnIuLqFChXTqfgT7Arask5WgrFwN1yCQ5IFY0Cnzd5WP+Id+LMa5B+GAbA/K+xhzF9F8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=501011d1.xn--hew.k1207; olt=johnl@user.iecc.com; bh=vEP18dl6FDF2Hu6AMLY6QHLE6Yp8cD3MXZX1UDTLsUQ=; b=WCHYoxHyMp8iaOeuxQnbF/tRAROdwwu+qVKqiGegBZckbf1UGYPrVGewGeEI8t1i2RPJfT62d95UFip6UoDYdN05y7W3rLz6OOuOPBChRz7BBkRFdN/agV7SMpdu7O9nT/ZWShS75OJK2YP9i6lS6Ty/ZCut/gKXN1Fg0iYQrAM=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 25 Jul 2012 15:33:15 -0000
Message-ID: <20120725153315.21135.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <603013B9-871C-4C93-B1DA-805FA16E4E2C@nominet.org.uk>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jul 2012 15:33:41 -0000

>That presupposes that weirds.<tld> hasn't already been registered by a normal
>registrant.

Of course it has, in .com, .net, .org, and .info, but I don't think it
would be a big problem to find a name like
whois-information-server.<tld> that we can be reasonably sure is
available across all the TLDs that are likely to implement WEIRDS.

While you're here, how hard would it be to add another 2LD in .UK, with
CNAME or NS records at whois-information-server.uk (or whatever it
is)?

R's,
John

From carlosm3011@gmail.com  Wed Jul 25 13:38:17 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 868ED21F86E4 for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 13:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QowDrArw+QCH for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 13:38:16 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 51EA621F86D1 for <weirds@ietf.org>; Wed, 25 Jul 2012 13:38:16 -0700 (PDT)
Received: by qadz3 with SMTP id z3so2829858qad.10 for <weirds@ietf.org>; Wed, 25 Jul 2012 13:38:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=hzDrWmlVvdaG5SLh55T3FTCB6HAY+G6B5kqO+V6sgQQ=; b=DfpqSI34jIw/8zNrCBp0ypSdrYHWq5n/Kr+zybeOjUVxkhrISa5OU7ZGRW8jdQ6pPk 179jVBGLMZipDIoYKgA9t5hrz7Q/hn8TBFC56zJdr4XvZCxiWupSlt/a3qtRKI7/GX/f tvRfH+q8WcJllUwpwLlPIhDVecO4BuxyiAaUvJGR2eIeGjMq3olyKwXV6hPO0emgbYKN b2KXJ7LjxuKng1ApvSEPNCDmi7KUKg2+36YmLcBNIlJtc8M6bKRjoL7TvCzFuF3TIDgt XP9bdoFO7ve8fRCcIy2JfRBEwhlmqidB6UQZhRlN8Am0wN9pBepqIskfD1WEvIIPRqkG 3rtg==
Received: by 10.224.203.197 with SMTP id fj5mr39948383qab.98.1343248695817; Wed, 25 Jul 2012 13:38:15 -0700 (PDT)
Received: from europa.local ([200.7.85.155]) by mx.google.com with ESMTPS id bo5sm17973027qab.1.2012.07.25.13.38.13 (version=SSLv3 cipher=OTHER); Wed, 25 Jul 2012 13:38:14 -0700 (PDT)
Message-ID: <50105933.80209@gmail.com>
Date: Wed, 25 Jul 2012 17:38:11 -0300
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Byron Ellacott <bje@apnic.net>
References: <20120723185220.90066.qmail@joyce.lan> <348E4548-FEFE-494B-AE41-ADF807927DC2@apnic.net>
In-Reply-To: <348E4548-FEFE-494B-AE41-ADF807927DC2@apnic.net>
Content-Type: multipart/alternative; boundary="------------070003010805030905040305"
Cc: weirds@ietf.org
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jul 2012 20:38:17 -0000

This is a multi-part message in MIME format.
--------------070003010805030905040305
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hello all, see inline:

On 7/23/12 11:42 PM, Byron Ellacott wrote:
> Hi all,
>
> On 24/07/2012, at 4:52 AM, John Levine wrote:
>
>>>> - the SRV/NAPTR approach is simply more flexible
>>>> nuff said - it simply is
>>> I've yet to hear a reason why SRV/NAPTR is more appropriate than U-NAPTR.
>> Given that some cruddy client libraries still don't support NAPTR, and
>> that most of the things people are proposing to do for bootstraps can
>> be done with slightly more CNAME records, I don't understand why we
>> need NAPTR at all.
>
> There's a trade-off between client complexity for NAPTR, and server complexity to support SNI or manage multiple CA certs.  Both issues are "real" in that someone would have to deal with them.  Both issues are not intractable.  I favour putting the complexity on the server side.  I favour this particularly because adding the processing required to go from a set of NAPTR records fetched, to connecting to the right server, would be as much as or more processing than is required to go from connecting to the right server to having a parsed weirds response in memory.  It would not be a doubling of complexity to support SNI on the server side, nor to manage 100 SSL certs.
Agreed!
>
> I'd like to note that the ability to host web content, including javascript, is different to the ability to host web server scripts; there would be a set of users who could include a weirds script on their page, but not put a DNS resolver service on their web host.  I think this would be a less common issue than just the complexity of processing NAPTRs, but when it is an issue, it's effectively an intractable problem: changing web host providers is a non-solution, IMO.
It's of course true that you can host JS w/o the ability to run
server-side scripts. However, I'm afraid we are piling restrictions up
upon the bootstrap problem (and maybe others) without a clear direction.
I'm afraid that we could end up here choosing a worse technical solution
in the name of a restriction that ends up being incompatible with other
stuff we decide later on.

Summing it up: I think we need to get our restrictions and border
conditions clear and documented first. Note that I'm NOT taking position
here either for or against Byron's comment here, just making an
observation on the path (I think) we should follow.

IMO, U-NAPTR or URI records (see Olaf's email) plus helpers (local or
3rd party) for those JS-only implementations is a reasonable bootstrap
implementation, but again, in order to decide, we need to get a clear
picture of ALL the restrictions applied to our current problem space.


> I'm curious about how strong the perceived need is for channel security, too.  Is it something we should consider mandatory, something that should be optional at service operator discretion, or perhaps related to differential access class needs?
IMO there should be a relationship/correspondence between access class
and channel security requirements. The highest access class levels
should probably require not only a server-side cert but a client-side
one as well (which would provide a nice way of implementing / enforcing
Bulk WHOIS agreements, something which is currently are done in kludgy ways)

Lowest access class probably could be server over plain HTTP, with a
protection level similar to current port 43 service (that is, no
protection at all :-) )
>
> Also, there's a taxonomy invented by ICANN for these services, though they sadly forgot what the first "N" in ICANN stands for.  Rather than weirds.arpa, I would prefer us to use rd-ds.arpa, taking the "DNRD-DS" taxonomy and dropping the "DN" part :-)
Didn't know about that, thanks!
>
>   Byron
cheers!

~Carlos
>
>
>
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds



--------------070003010805030905040305
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hello all, see inline:<br>
    <br>
    <div class="moz-cite-prefix">On 7/23/12 11:42 PM, Byron Ellacott
      wrote:<br>
    </div>
    <blockquote
      cite="mid:348E4548-FEFE-494B-AE41-ADF807927DC2@apnic.net"
      type="cite">
      <pre wrap="">Hi all,

On 24/07/2012, at 4:52 AM, John Levine wrote:

</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <blockquote type="cite">
            <pre wrap="">- the SRV/NAPTR approach is simply more flexible
nuff said - it simply is
</pre>
          </blockquote>
          <pre wrap="">
I've yet to hear a reason why SRV/NAPTR is more appropriate than U-NAPTR.
</pre>
        </blockquote>
        <pre wrap="">
Given that some cruddy client libraries still don't support NAPTR, and
that most of the things people are proposing to do for bootstraps can
be done with slightly more CNAME records, I don't understand why we
need NAPTR at all.
</pre>
      </blockquote>
      <pre wrap="">

There's a trade-off between client complexity for NAPTR, and server complexity to support SNI or manage multiple CA certs.  Both issues are "real" in that someone would have to deal with them.  Both issues are not intractable.  I favour putting the complexity on the server side.  I favour this particularly because adding the processing required to go from a set of NAPTR records fetched, to connecting to the right server, would be as much as or more processing than is required to go from connecting to the right server to having a parsed weirds response in memory.  It would not be a doubling of complexity to support SNI on the server side, nor to manage 100 SSL certs.</pre>
    </blockquote>
    Agreed!<br>
    <blockquote
      cite="mid:348E4548-FEFE-494B-AE41-ADF807927DC2@apnic.net"
      type="cite">
      <pre wrap="">

I'd like to note that the ability to host web content, including javascript, is different to the ability to host web server scripts; there would be a set of users who could include a weirds script on their page, but not put a DNS resolver service on their web host.  I think this would be a less common issue than just the complexity of processing NAPTRs, but when it is an issue, it's effectively an intractable problem: changing web host providers is a non-solution, IMO.
</pre>
    </blockquote>
    It's of course true that you can host JS w/o the ability to run
    server-side scripts. However, I'm afraid we are piling restrictions
    up upon the bootstrap problem (and maybe others) without a clear
    direction. I'm afraid that we could end up here choosing a worse
    technical solution in the name of a restriction that ends up being
    incompatible with other stuff we decide later on.<br>
    <br>
    Summing it up: I think we need to get our restrictions and border
    conditions clear and documented first. Note that I'm NOT taking
    position here either for or against Byron's comment here, just
    making an observation on the path (I think) we should follow.<br>
    <br>
    IMO, U-NAPTR or URI records (see Olaf's email) plus helpers (local
    or 3rd party) for those JS-only implementations is a reasonable
    bootstrap implementation, but again, in order to decide, we need to
    get a clear picture of ALL the restrictions applied to our current
    problem space.<br>
    <br>
    <br>
    <blockquote
      cite="mid:348E4548-FEFE-494B-AE41-ADF807927DC2@apnic.net"
      type="cite">
      <pre wrap="">
I'm curious about how strong the perceived need is for channel security, too.  Is it something we should consider mandatory, something that should be optional at service operator discretion, or perhaps related to differential access class needs?</pre>
    </blockquote>
    IMO there should be a relationship/correspondence between access
    class and channel security requirements. The highest access class
    levels should probably require not only a server-side cert but a
    client-side one as well (which would provide a nice way of
    implementing / enforcing Bulk WHOIS agreements, something which is
    currently are done in kludgy ways)<br>
    <br>
    Lowest access class probably could be server over plain HTTP, with a
    protection level similar to current port 43 service (that is, no
    protection at all :-) )<br>
    <blockquote
      cite="mid:348E4548-FEFE-494B-AE41-ADF807927DC2@apnic.net"
      type="cite">
      <pre wrap="">

Also, there's a taxonomy invented by ICANN for these services, though they sadly forgot what the first "N" in ICANN stands for.  Rather than weirds.arpa, I would prefer us to use rd-ds.arpa, taking the "DNRD-DS" taxonomy and dropping the "DN" part :-)</pre>
    </blockquote>
    Didn't know about that, thanks!<br>
    <blockquote
      cite="mid:348E4548-FEFE-494B-AE41-ADF807927DC2@apnic.net"
      type="cite">
      <pre wrap="">

  Byron</pre>
    </blockquote>
    cheers!<br>
    <br>
    ~Carlos<br>
    <blockquote
      cite="mid:348E4548-FEFE-494B-AE41-ADF807927DC2@apnic.net"
      type="cite">
      <pre wrap="">

</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
weirds mailing list
<a class="moz-txt-link-abbreviated" href="mailto:weirds@ietf.org">weirds@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/weirds">https://www.ietf.org/mailman/listinfo/weirds</a>
</pre>
    </blockquote>
    <br>
    <br>
  </body>
</html>

--------------070003010805030905040305--

From chris@ausregistry.com.au  Wed Jul 25 18:04:15 2012
Return-Path: <chris@ausregistry.com.au>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F384A21F8607 for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 18:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.015
X-Spam-Level: 
X-Spam-Status: No, score=-1.015 tagged_above=-999 required=5 tests=[AWL=0.279,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, HTML_MESSAGE=0.001, J_CHICKENPOX_64=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2TdtaQsQUutQ for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 18:04:13 -0700 (PDT)
Received: from mx02.ausregistry.net.au (mx02.ausregistry.net.au [202.65.15.42]) by ietfa.amsl.com (Postfix) with ESMTP id 7A14921F860B for <weirds@ietf.org>; Wed, 25 Jul 2012 18:04:08 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron02.off08.stkildard.vic.ausregistry.com.au with ESMTP; 26 Jul 2012 11:04:04 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Thu, 26 Jul 2012 11:03:49 +1000
From: Chris Wright <chris@ausregistry.com.au>
To: "carlos@lacnic.net" <carlos@lacnic.net>, Byron Ellacott <bje@apnic.net>
Date: Thu, 26 Jul 2012 11:04:02 +1000
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: Ac1qpWhR/f0Q0N6yQ+qNUf5bZo5a7QAI9wug
Message-ID: <8CEF048B9EC83748B1517DC64EA130FB729CE5F571@off-win2003-01.ausregistrygroup.local>
References: <20120723185220.90066.qmail@joyce.lan> <348E4548-FEFE-494B-AE41-ADF807927DC2@apnic.net> <50105933.80209@gmail.com>
In-Reply-To: <50105933.80209@gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: multipart/alternative; boundary="_000_8CEF048B9EC83748B1517DC64EA130FB729CE5F571offwin200301a_"
MIME-Version: 1.0
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 01:04:15 -0000

--_000_8CEF048B9EC83748B1517DC64EA130FB729CE5F571offwin200301a_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSBrbm93IEkgc2FpZCBJIHdhc27igJl0IGdvaW5nIHRvIGNvbW1lbnQgb24gdGhpcyBhbnltb3Jl
LCBidXQgb25lIG1vcmUgdmVyeSBpbXBvcnRhbnQgdGhpbmcgb2NjdXJyZWQgdG8gbWUgbGFzdCBu
aWdodCB0aGF0IEkgdGhpbmsgaXMgd29ydGggc2hhcmluZyB3aXRoIGFsbC4gSSByZW1lbWJlcmVk
IHRoYXQgd2UgYWxyZWFkeSBoYXZlIGFuIFNSViByZWNvcmQgaW4gdGhlIC5hdSB6b25lIHRvIHN1
cHBvcnQgdGhpcyB2ZXJ5IHRoaW5nLiBUaGVyZSBpcyBwcmVjZWRlbnQgZm9yIHdoYXQgaXMgYmVp
bmcgZGlzY3Vzc2VkIGFscmVhZHksIG5vdyBncmFudGVkIGl04oCZcyBub3QgYW4gUkZDLCBidXQg
aXQgaXMgYSBjb252ZW50aW9uIHRoYXQgbWFueSBoYXZlIGFkb3B0ZWQgKEkgaGF2ZW7igJl0IHNl
YXJjaGVkIGFsbCBUTERzIGp1c3QgY2hlY2tlZCB0aGUgb25lcyByZWZlcmVuY2VkIGluIHRoZSBh
cnRpY2xlIGJlbG93KS4NCg0KDQojIGRpZyArc2hvcnQgLXQgU1JWIF9uaWNuYW1lLl90Y3Aue2F1
LGF0LGRrLGZyLGRlLGh1LGllLGxpLGx1LG5vLHJlLHNpLHNlLGNoLHVrfQ0KMCAwIDQzIHdob2lz
LmF1c3JlZ2lzdHJ5LmNvbS5hdS4NCjEwIDAgNDMgd2hvaXMubmljLmF0Lg0KMCAwIDQzIHdob2lz
LmRrLWhvc3RtYXN0ZXIuZGsuDQowIDAgNDMgd2hvaXMubmljLmZyLg0KMCAwIDQzIHdob2lzLmRl
bmljLmRlLg0KMCAwIDQzIHdob2lzLm5pYy5odS4NCjEwIDAgNDMgd2hvaXMuZG9tYWlucmVnaXN0
cnkuaWUuDQowIDEgNDMgd2hvaXMubmljLmNoLg0KMCAwIDQzIHdob2lzLmRucy5sdS4NCjAgMCA0
MyB3aG9pcy5ub3JpZC5uby4NCjAgMCA0MyB3aG9pcy5uaWMucmUuDQoxMCAwIDQzIHdob2lzLmFy
bmVzLnNpLg0KMCAwIDQzIHdob2lzLm5pYy1zZS5zZS4NCjAgMSA0MyB3aG9pcy5uaWMuY2guDQow
IDAgNDMgd2hvaXMubmljLnVrLg0KDQpTZWUgaGVyZSBmb3IgbW9yZSBpbmZvcm1hdGlvbjoNCg0K
aHR0cDovL2Jsb2cubm9taW5ldC5vcmcudWsvdGVjaC8yMDA3LzA0LzE3L19uaWNuYW1lLXNydi1y
ZWNvcmQvDQoNClNvIHdlIGNhbiB0YWxrIGFib3V0IHdoZXRoZXIgaXQgc2hvdWxkIGJlIGFuIFNS
ViBvciBhIE5BUFRSL1UtTkFQVFIgcmVjb3JkIGFuZCB0aGUgcHJvcyBhbmQgY29ucyBvZiB0aG9z
ZSwgYnV0IEkgdGhpbmsgaXQgaXMgY2xlYXIgdGhhdCBsb29raW5nIHVwIHRoZSBsb2NhdGlvbiBv
ZiB0aGUgV2hvSXMgKG9yIGluZGVlZCB0aGUgV2hvSXMgcmVwbGFjZW1lbnQgc2VydmljZSkgaW4g
dGhlIEROUyBpcyBub3QgdW5wcmVjZWRlbnRlZC4NCg0KVGhhbmtzDQoNCmMuDQoNCkZyb206IHdl
aXJkcy1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86d2VpcmRzLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZiBPZiBDYXJsb3MgTWFydGluZXotQ2FnbmF6em8NClNlbnQ6IFRodXJzZGF5LCAyNiBK
dWx5IDIwMTIgNjozOCBBTQ0KVG86IEJ5cm9uIEVsbGFjb3R0DQpDYzogd2VpcmRzQGlldGYub3Jn
DQpTdWJqZWN0OiBSZTogW3dlaXJkc10gdGhlIGJvb3RzdHJhcCBwcm9ibGVtLCBSZWRpcmVjdGlv
biBpbiB0aGUgUkVTVGZ1bCBXSE9JUyB3b3JsZA0KDQpIZWxsbyBhbGwsIHNlZSBpbmxpbmU6DQpP
biA3LzIzLzEyIDExOjQyIFBNLCBCeXJvbiBFbGxhY290dCB3cm90ZToNCg0KSGkgYWxsLA0KDQoN
Cg0KT24gMjQvMDcvMjAxMiwgYXQgNDo1MiBBTSwgSm9obiBMZXZpbmUgd3JvdGU6DQoNCg0KDQot
IHRoZSBTUlYvTkFQVFIgYXBwcm9hY2ggaXMgc2ltcGx5IG1vcmUgZmxleGlibGUNCg0KbnVmZiBz
YWlkIC0gaXQgc2ltcGx5IGlzDQoNCg0KDQpJJ3ZlIHlldCB0byBoZWFyIGEgcmVhc29uIHdoeSBT
UlYvTkFQVFIgaXMgbW9yZSBhcHByb3ByaWF0ZSB0aGFuIFUtTkFQVFIuDQoNCg0KDQpHaXZlbiB0
aGF0IHNvbWUgY3J1ZGR5IGNsaWVudCBsaWJyYXJpZXMgc3RpbGwgZG9uJ3Qgc3VwcG9ydCBOQVBU
UiwgYW5kDQoNCnRoYXQgbW9zdCBvZiB0aGUgdGhpbmdzIHBlb3BsZSBhcmUgcHJvcG9zaW5nIHRv
IGRvIGZvciBib290c3RyYXBzIGNhbg0KDQpiZSBkb25lIHdpdGggc2xpZ2h0bHkgbW9yZSBDTkFN
RSByZWNvcmRzLCBJIGRvbid0IHVuZGVyc3RhbmQgd2h5IHdlDQoNCm5lZWQgTkFQVFIgYXQgYWxs
Lg0KDQoNCg0KDQoNClRoZXJlJ3MgYSB0cmFkZS1vZmYgYmV0d2VlbiBjbGllbnQgY29tcGxleGl0
eSBmb3IgTkFQVFIsIGFuZCBzZXJ2ZXIgY29tcGxleGl0eSB0byBzdXBwb3J0IFNOSSBvciBtYW5h
Z2UgbXVsdGlwbGUgQ0EgY2VydHMuICBCb3RoIGlzc3VlcyBhcmUgInJlYWwiIGluIHRoYXQgc29t
ZW9uZSB3b3VsZCBoYXZlIHRvIGRlYWwgd2l0aCB0aGVtLiAgQm90aCBpc3N1ZXMgYXJlIG5vdCBp
bnRyYWN0YWJsZS4gIEkgZmF2b3VyIHB1dHRpbmcgdGhlIGNvbXBsZXhpdHkgb24gdGhlIHNlcnZl
ciBzaWRlLiAgSSBmYXZvdXIgdGhpcyBwYXJ0aWN1bGFybHkgYmVjYXVzZSBhZGRpbmcgdGhlIHBy
b2Nlc3NpbmcgcmVxdWlyZWQgdG8gZ28gZnJvbSBhIHNldCBvZiBOQVBUUiByZWNvcmRzIGZldGNo
ZWQsIHRvIGNvbm5lY3RpbmcgdG8gdGhlIHJpZ2h0IHNlcnZlciwgd291bGQgYmUgYXMgbXVjaCBh
cyBvciBtb3JlIHByb2Nlc3NpbmcgdGhhbiBpcyByZXF1aXJlZCB0byBnbyBmcm9tIGNvbm5lY3Rp
bmcgdG8gdGhlIHJpZ2h0IHNlcnZlciB0byBoYXZpbmcgYSBwYXJzZWQgd2VpcmRzIHJlc3BvbnNl
IGluIG1lbW9yeS4gIEl0IHdvdWxkIG5vdCBiZSBhIGRvdWJsaW5nIG9mIGNvbXBsZXhpdHkgdG8g
c3VwcG9ydCBTTkkgb24gdGhlIHNlcnZlciBzaWRlLCBub3IgdG8gbWFuYWdlIDEwMCBTU0wgY2Vy
dHMuDQpBZ3JlZWQhDQoNCg0KDQoNCg0KDQpJJ2QgbGlrZSB0byBub3RlIHRoYXQgdGhlIGFiaWxp
dHkgdG8gaG9zdCB3ZWIgY29udGVudCwgaW5jbHVkaW5nIGphdmFzY3JpcHQsIGlzIGRpZmZlcmVu
dCB0byB0aGUgYWJpbGl0eSB0byBob3N0IHdlYiBzZXJ2ZXIgc2NyaXB0czsgdGhlcmUgd291bGQg
YmUgYSBzZXQgb2YgdXNlcnMgd2hvIGNvdWxkIGluY2x1ZGUgYSB3ZWlyZHMgc2NyaXB0IG9uIHRo
ZWlyIHBhZ2UsIGJ1dCBub3QgcHV0IGEgRE5TIHJlc29sdmVyIHNlcnZpY2Ugb24gdGhlaXIgd2Vi
IGhvc3QuICBJIHRoaW5rIHRoaXMgd291bGQgYmUgYSBsZXNzIGNvbW1vbiBpc3N1ZSB0aGFuIGp1
c3QgdGhlIGNvbXBsZXhpdHkgb2YgcHJvY2Vzc2luZyBOQVBUUnMsIGJ1dCB3aGVuIGl0IGlzIGFu
IGlzc3VlLCBpdCdzIGVmZmVjdGl2ZWx5IGFuIGludHJhY3RhYmxlIHByb2JsZW06IGNoYW5naW5n
IHdlYiBob3N0IHByb3ZpZGVycyBpcyBhIG5vbi1zb2x1dGlvbiwgSU1PLg0KSXQncyBvZiBjb3Vy
c2UgdHJ1ZSB0aGF0IHlvdSBjYW4gaG9zdCBKUyB3L28gdGhlIGFiaWxpdHkgdG8gcnVuIHNlcnZl
ci1zaWRlIHNjcmlwdHMuIEhvd2V2ZXIsIEknbSBhZnJhaWQgd2UgYXJlIHBpbGluZyByZXN0cmlj
dGlvbnMgdXAgdXBvbiB0aGUgYm9vdHN0cmFwIHByb2JsZW0gKGFuZCBtYXliZSBvdGhlcnMpIHdp
dGhvdXQgYSBjbGVhciBkaXJlY3Rpb24uIEknbSBhZnJhaWQgdGhhdCB3ZSBjb3VsZCBlbmQgdXAg
aGVyZSBjaG9vc2luZyBhIHdvcnNlIHRlY2huaWNhbCBzb2x1dGlvbiBpbiB0aGUgbmFtZSBvZiBh
IHJlc3RyaWN0aW9uIHRoYXQgZW5kcyB1cCBiZWluZyBpbmNvbXBhdGlibGUgd2l0aCBvdGhlciBz
dHVmZiB3ZSBkZWNpZGUgbGF0ZXIgb24uDQoNClN1bW1pbmcgaXQgdXA6IEkgdGhpbmsgd2UgbmVl
ZCB0byBnZXQgb3VyIHJlc3RyaWN0aW9ucyBhbmQgYm9yZGVyIGNvbmRpdGlvbnMgY2xlYXIgYW5k
IGRvY3VtZW50ZWQgZmlyc3QuIE5vdGUgdGhhdCBJJ20gTk9UIHRha2luZyBwb3NpdGlvbiBoZXJl
IGVpdGhlciBmb3Igb3IgYWdhaW5zdCBCeXJvbidzIGNvbW1lbnQgaGVyZSwganVzdCBtYWtpbmcg
YW4gb2JzZXJ2YXRpb24gb24gdGhlIHBhdGggKEkgdGhpbmspIHdlIHNob3VsZCBmb2xsb3cuDQoN
CklNTywgVS1OQVBUUiBvciBVUkkgcmVjb3JkcyAoc2VlIE9sYWYncyBlbWFpbCkgcGx1cyBoZWxw
ZXJzIChsb2NhbCBvciAzcmQgcGFydHkpIGZvciB0aG9zZSBKUy1vbmx5IGltcGxlbWVudGF0aW9u
cyBpcyBhIHJlYXNvbmFibGUgYm9vdHN0cmFwIGltcGxlbWVudGF0aW9uLCBidXQgYWdhaW4sIGlu
IG9yZGVyIHRvIGRlY2lkZSwgd2UgbmVlZCB0byBnZXQgYSBjbGVhciBwaWN0dXJlIG9mIEFMTCB0
aGUgcmVzdHJpY3Rpb25zIGFwcGxpZWQgdG8gb3VyIGN1cnJlbnQgcHJvYmxlbSBzcGFjZS4NCg0K
DQoNCg0KDQoNCkknbSBjdXJpb3VzIGFib3V0IGhvdyBzdHJvbmcgdGhlIHBlcmNlaXZlZCBuZWVk
IGlzIGZvciBjaGFubmVsIHNlY3VyaXR5LCB0b28uICBJcyBpdCBzb21ldGhpbmcgd2Ugc2hvdWxk
IGNvbnNpZGVyIG1hbmRhdG9yeSwgc29tZXRoaW5nIHRoYXQgc2hvdWxkIGJlIG9wdGlvbmFsIGF0
IHNlcnZpY2Ugb3BlcmF0b3IgZGlzY3JldGlvbiwgb3IgcGVyaGFwcyByZWxhdGVkIHRvIGRpZmZl
cmVudGlhbCBhY2Nlc3MgY2xhc3MgbmVlZHM/DQpJTU8gdGhlcmUgc2hvdWxkIGJlIGEgcmVsYXRp
b25zaGlwL2NvcnJlc3BvbmRlbmNlIGJldHdlZW4gYWNjZXNzIGNsYXNzIGFuZCBjaGFubmVsIHNl
Y3VyaXR5IHJlcXVpcmVtZW50cy4gVGhlIGhpZ2hlc3QgYWNjZXNzIGNsYXNzIGxldmVscyBzaG91
bGQgcHJvYmFibHkgcmVxdWlyZSBub3Qgb25seSBhIHNlcnZlci1zaWRlIGNlcnQgYnV0IGEgY2xp
ZW50LXNpZGUgb25lIGFzIHdlbGwgKHdoaWNoIHdvdWxkIHByb3ZpZGUgYSBuaWNlIHdheSBvZiBp
bXBsZW1lbnRpbmcgLyBlbmZvcmNpbmcgQnVsayBXSE9JUyBhZ3JlZW1lbnRzLCBzb21ldGhpbmcg
d2hpY2ggaXMgY3VycmVudGx5IGFyZSBkb25lIGluIGtsdWRneSB3YXlzKQ0KDQpMb3dlc3QgYWNj
ZXNzIGNsYXNzIHByb2JhYmx5IGNvdWxkIGJlIHNlcnZlciBvdmVyIHBsYWluIEhUVFAsIHdpdGgg
YSBwcm90ZWN0aW9uIGxldmVsIHNpbWlsYXIgdG8gY3VycmVudCBwb3J0IDQzIHNlcnZpY2UgKHRo
YXQgaXMsIG5vIHByb3RlY3Rpb24gYXQgYWxsIDotKSApDQoNCg0KDQoNCg0KDQpBbHNvLCB0aGVy
ZSdzIGEgdGF4b25vbXkgaW52ZW50ZWQgYnkgSUNBTk4gZm9yIHRoZXNlIHNlcnZpY2VzLCB0aG91
Z2ggdGhleSBzYWRseSBmb3Jnb3Qgd2hhdCB0aGUgZmlyc3QgIk4iIGluIElDQU5OIHN0YW5kcyBm
b3IuICBSYXRoZXIgdGhhbiB3ZWlyZHMuYXJwYSwgSSB3b3VsZCBwcmVmZXIgdXMgdG8gdXNlIHJk
LWRzLmFycGEsIHRha2luZyB0aGUgIkROUkQtRFMiIHRheG9ub215IGFuZCBkcm9wcGluZyB0aGUg
IkROIiBwYXJ0IDotKQ0KRGlkbid0IGtub3cgYWJvdXQgdGhhdCwgdGhhbmtzIQ0KDQoNCg0KDQoN
Cg0KICBCeXJvbg0KY2hlZXJzIQ0KDQp+Q2FybG9zDQoNCg0KDQoNCg0KDQoNCg0KDQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQp3ZWlyZHMgbWFpbGlu
ZyBsaXN0DQoNCndlaXJkc0BpZXRmLm9yZzxtYWlsdG86d2VpcmRzQGlldGYub3JnPg0KDQpodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3dlaXJkcw0KDQo=

--_000_8CEF048B9EC83748B1517DC64EA130FB729CE5F571offwin200301a_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0
aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQt
ZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLCJzZXJpZiI7DQoJY29sb3I6YmxhY2s7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGlu
aw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRp
b246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1
bmRlcmxpbmU7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGlu
azoiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9t
Oi4wMDAxcHQ7DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXci
Ow0KCWNvbG9yOmJsYWNrO30NCnNwYW4uSFRNTFByZWZvcm1hdHRlZENoYXINCgl7bXNvLXN0eWxl
LW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQiOw0KCWZvbnQtZmFtaWx5OkNvbnNv
bGFzOw0KCWNvbG9yOmJsYWNrO30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1zdHlsZS10eXBl
OnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJ
Y29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQt
b25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYx
Mi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRp
di5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lm
IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9
IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxv
OnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIx
IiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPjwvaGVhZD48Ym9keSBiZ2Nv
bG9yPXdoaXRlIGxhbmc9RU4tQVUgbGluaz1ibHVlIHZsaW5rPXB1cnBsZT48ZGl2IGNsYXNzPVdv
cmRTZWN0aW9uMT48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5JIGtu
b3cgSSBzYWlkIEkgd2FzbuKAmXQgZ29pbmcgdG8gY29tbWVudCBvbiB0aGlzIGFueW1vcmUsIGJ1
dCBvbmUgbW9yZSB2ZXJ5IGltcG9ydGFudCB0aGluZyBvY2N1cnJlZCB0byBtZSBsYXN0IG5pZ2h0
IHRoYXQgSSB0aGluayBpcyB3b3J0aCBzaGFyaW5nIHdpdGggYWxsLiBJIHJlbWVtYmVyZWQgdGhh
dCB3ZSBhbHJlYWR5IGhhdmUgYW4gU1JWIHJlY29yZCBpbiB0aGUgLmF1IHpvbmUgdG8gc3VwcG9y
dCB0aGlzIHZlcnkgdGhpbmcuIFRoZXJlIGlzIHByZWNlZGVudCBmb3Igd2hhdCBpcyBiZWluZyBk
aXNjdXNzZWQgYWxyZWFkeSwgbm93IGdyYW50ZWQgaXTigJlzIG5vdCBhbiBSRkMsIGJ1dCBpdCBp
cyBhIGNvbnZlbnRpb24gdGhhdCBtYW55IGhhdmUgYWRvcHRlZCAoSSBoYXZlbuKAmXQgc2VhcmNo
ZWQgYWxsIFRMRHMganVzdCBjaGVja2VkIHRoZSBvbmVzIHJlZmVyZW5jZWQgaW4gdGhlIGFydGlj
bGUgYmVsb3cpLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4g
c3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
Ijtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJp
Iiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
PjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPiMgZGlnICtzaG9ydCAt
dCBTUlYgX25pY25hbWUuX3RjcC57YXUsYXQsZGssZnIsZGUsaHUsaWUsbGksbHUsbm8scmUsc2ks
c2UsY2gsdWt9PG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBz
dHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYi
O2NvbG9yOiMxRjQ5N0QnPjAgMCA0MyB3aG9pcy5hdXNyZWdpc3RyeS5jb20uYXUuPG86cD48L286
cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjEw
IDAgNDMgd2hvaXMubmljLmF0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3Jt
YWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJz
YW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4wIDAgNDMgd2hvaXMuZGstaG9zdG1hc3Rlci5kay48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFG
NDk3RCc+MCAwIDQzIHdob2lzLm5pYy5mci48bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9
TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxp
YnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+MCAwIDQzIHdob2lzLmRlbmljLmRlLjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0
OTdEJz4wIDAgNDMgd2hvaXMubmljLmh1LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1N
c29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4xMCAwIDQzIHdob2lzLmRvbWFpbnJlZ2lz
dHJ5LmllLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtj
b2xvcjojMUY0OTdEJz4wIDEgNDMgd2hvaXMubmljLmNoLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48
cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz4wIDAgNDMgd2hvaXMuZG5z
Lmx1LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9
J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xv
cjojMUY0OTdEJz4wIDAgNDMgd2hvaXMubm9yaWQubm8uPG86cD48L286cD48L3NwYW4+PC9wPjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjAgMCA0MyB3aG9pcy5uaWMu
cmUuPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0n
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9y
OiMxRjQ5N0QnPjEwIDAgNDMgd2hvaXMuYXJuZXMuc2kuPG86cD48L286cD48L3NwYW4+PC9wPjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjAgMCA0MyB3aG9pcy5uaWMt
c2Uuc2UuPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHls
ZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2Nv
bG9yOiMxRjQ5N0QnPjAgMSA0MyB3aG9pcy5uaWMuY2guPG86cD48L286cD48L3NwYW4+PC9wPjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjAgMCA0MyB3aG9pcy5uaWMu
dWsuPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0n
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9y
OiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+
PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjtjb2xvcjojMUY0OTdEJz5TZWUgaGVyZSBmb3IgbW9yZSBpbmZvcm1hdGlvbjo8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3
RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48YSBocmVm
PSJodHRwOi8vYmxvZy5ub21pbmV0Lm9yZy51ay90ZWNoLzIwMDcvMDQvMTcvX25pY25hbWUtc3J2
LXJlY29yZC8iPmh0dHA6Ly9ibG9nLm5vbWluZXQub3JnLnVrL3RlY2gvMjAwNy8wNC8xNy9fbmlj
bmFtZS1zcnYtcmVjb3JkLzwvYT48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFG
NDk3RCc+U28gd2UgY2FuIHRhbGsgYWJvdXQgd2hldGhlciBpdCBzaG91bGQgYmUgYW4gU1JWIG9y
IGEgTkFQVFIvVS1OQVBUUiByZWNvcmQgYW5kIHRoZSBwcm9zIGFuZCBjb25zIG9mIHRob3NlLCBi
dXQgSSB0aGluayBpdCBpcyBjbGVhciB0aGF0IGxvb2tpbmcgdXAgdGhlIGxvY2F0aW9uIG9mIHRo
ZSBXaG9JcyAob3IgaW5kZWVkIHRoZSBXaG9JcyByZXBsYWNlbWVudCBzZXJ2aWNlKSBpbiB0aGUg
RE5TIGlzIG5vdCB1bnByZWNlZGVudGVkLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1N
c29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGli
cmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5UaGFua3M8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFG
NDk3RCc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3Bh
biBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2Vy
aWYiO2NvbG9yOiMxRjQ5N0QnPmMuPG86cD48L286cD48L3NwYW4+PC9wPjwvZGl2PjxwIGNsYXNz
PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2Fs
aWJyaSIsInNhbnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD48ZGl2PjxkaXYgc3R5bGU9J2JvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRE
RiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtJz48cCBjbGFzcz1Nc29Ob3JtYWw+PGI+
PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiVGFo
b21hIiwic2Fucy1zZXJpZiI7Y29sb3I6d2luZG93dGV4dCc+RnJvbTo8L3NwYW4+PC9iPjxzcGFu
IGxhbmc9RU4tVVMgc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IlRhaG9tYSIs
InNhbnMtc2VyaWYiO2NvbG9yOndpbmRvd3RleHQnPiB3ZWlyZHMtYm91bmNlc0BpZXRmLm9yZyBb
bWFpbHRvOndlaXJkcy1ib3VuY2VzQGlldGYub3JnXSA8Yj5PbiBCZWhhbGYgT2YgPC9iPkNhcmxv
cyBNYXJ0aW5lei1DYWduYXp6bzxicj48Yj5TZW50OjwvYj4gVGh1cnNkYXksIDI2IEp1bHkgMjAx
MiA2OjM4IEFNPGJyPjxiPlRvOjwvYj4gQnlyb24gRWxsYWNvdHQ8YnI+PGI+Q2M6PC9iPiB3ZWly
ZHNAaWV0Zi5vcmc8YnI+PGI+U3ViamVjdDo8L2I+IFJlOiBbd2VpcmRzXSB0aGUgYm9vdHN0cmFw
IHByb2JsZW0sIFJlZGlyZWN0aW9uIGluIHRoZSBSRVNUZnVsIFdIT0lTIHdvcmxkPG86cD48L286
cD48L3NwYW4+PC9wPjwvZGl2PjwvZGl2PjxwIGNsYXNzPU1zb05vcm1hbD48bzpwPiZuYnNwOzwv
bzpwPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9J21hcmdpbi1ib3R0b206MTIuMHB0Jz5I
ZWxsbyBhbGwsIHNlZSBpbmxpbmU6PG86cD48L286cD48L3A+PGRpdj48cCBjbGFzcz1Nc29Ob3Jt
YWw+T24gNy8yMy8xMiAxMTo0MiBQTSwgQnlyb24gRWxsYWNvdHQgd3JvdGU6PG86cD48L286cD48
L3A+PC9kaXY+PGJsb2NrcXVvdGUgc3R5bGU9J21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRv
bTo1LjBwdCc+PHByZT5IaSBhbGwsPG86cD48L286cD48L3ByZT48cHJlPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wcmU+PHByZT5PbiAyNC8wNy8yMDEyLCBhdCA0OjUyIEFNLCBKb2huIExldmluZSB3cm90
ZTo8bzpwPjwvbzpwPjwvcHJlPjxwcmU+PG86cD4mbmJzcDs8L286cD48L3ByZT48YmxvY2txdW90
ZSBzdHlsZT0nbWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Jz48YmxvY2txdW90
ZSBzdHlsZT0nbWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Jz48YmxvY2txdW90
ZSBzdHlsZT0nbWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Jz48cHJlPi0gdGhl
IFNSVi9OQVBUUiBhcHByb2FjaCBpcyBzaW1wbHkgbW9yZSBmbGV4aWJsZTxvOnA+PC9vOnA+PC9w
cmU+PHByZT5udWZmIHNhaWQgLSBpdCBzaW1wbHkgaXM8bzpwPjwvbzpwPjwvcHJlPjwvYmxvY2tx
dW90ZT48cHJlPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+PHByZT5JJ3ZlIHlldCB0byBoZWFyIGEg
cmVhc29uIHdoeSBTUlYvTkFQVFIgaXMgbW9yZSBhcHByb3ByaWF0ZSB0aGFuIFUtTkFQVFIuPG86
cD48L286cD48L3ByZT48L2Jsb2NrcXVvdGU+PHByZT48bzpwPiZuYnNwOzwvbzpwPjwvcHJlPjxw
cmU+R2l2ZW4gdGhhdCBzb21lIGNydWRkeSBjbGllbnQgbGlicmFyaWVzIHN0aWxsIGRvbid0IHN1
cHBvcnQgTkFQVFIsIGFuZDxvOnA+PC9vOnA+PC9wcmU+PHByZT50aGF0IG1vc3Qgb2YgdGhlIHRo
aW5ncyBwZW9wbGUgYXJlIHByb3Bvc2luZyB0byBkbyBmb3IgYm9vdHN0cmFwcyBjYW48bzpwPjwv
bzpwPjwvcHJlPjxwcmU+YmUgZG9uZSB3aXRoIHNsaWdodGx5IG1vcmUgQ05BTUUgcmVjb3Jkcywg
SSBkb24ndCB1bmRlcnN0YW5kIHdoeSB3ZTxvOnA+PC9vOnA+PC9wcmU+PHByZT5uZWVkIE5BUFRS
IGF0IGFsbC48bzpwPjwvbzpwPjwvcHJlPjwvYmxvY2txdW90ZT48cHJlPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wcmU+PHByZT48bzpwPiZuYnNwOzwvbzpwPjwvcHJlPjxwcmU+VGhlcmUncyBhIHRyYWRl
LW9mZiBiZXR3ZWVuIGNsaWVudCBjb21wbGV4aXR5IGZvciBOQVBUUiwgYW5kIHNlcnZlciBjb21w
bGV4aXR5IHRvIHN1cHBvcnQgU05JIG9yIG1hbmFnZSBtdWx0aXBsZSBDQSBjZXJ0cy7CoCBCb3Ro
IGlzc3VlcyBhcmUgJnF1b3Q7cmVhbCZxdW90OyBpbiB0aGF0IHNvbWVvbmUgd291bGQgaGF2ZSB0
byBkZWFsIHdpdGggdGhlbS7CoCBCb3RoIGlzc3VlcyBhcmUgbm90IGludHJhY3RhYmxlLsKgIEkg
ZmF2b3VyIHB1dHRpbmcgdGhlIGNvbXBsZXhpdHkgb24gdGhlIHNlcnZlciBzaWRlLsKgIEkgZmF2
b3VyIHRoaXMgcGFydGljdWxhcmx5IGJlY2F1c2UgYWRkaW5nIHRoZSBwcm9jZXNzaW5nIHJlcXVp
cmVkIHRvIGdvIGZyb20gYSBzZXQgb2YgTkFQVFIgcmVjb3JkcyBmZXRjaGVkLCB0byBjb25uZWN0
aW5nIHRvIHRoZSByaWdodCBzZXJ2ZXIsIHdvdWxkIGJlIGFzIG11Y2ggYXMgb3IgbW9yZSBwcm9j
ZXNzaW5nIHRoYW4gaXMgcmVxdWlyZWQgdG8gZ28gZnJvbSBjb25uZWN0aW5nIHRvIHRoZSByaWdo
dCBzZXJ2ZXIgdG8gaGF2aW5nIGEgcGFyc2VkIHdlaXJkcyByZXNwb25zZSBpbiBtZW1vcnkuwqAg
SXQgd291bGQgbm90IGJlIGEgZG91Ymxpbmcgb2YgY29tcGxleGl0eSB0byBzdXBwb3J0IFNOSSBv
biB0aGUgc2VydmVyIHNpZGUsIG5vciB0byBtYW5hZ2UgMTAwIFNTTCBjZXJ0cy48bzpwPjwvbzpw
PjwvcHJlPjwvYmxvY2txdW90ZT48cCBjbGFzcz1Nc29Ob3JtYWw+QWdyZWVkITxicj48YnI+PG86
cD48L286cD48L3A+PHByZT48bzpwPiZuYnNwOzwvbzpwPjwvcHJlPjxwcmU+PG86cD4mbmJzcDs8
L286cD48L3ByZT48cHJlPkknZCBsaWtlIHRvIG5vdGUgdGhhdCB0aGUgYWJpbGl0eSB0byBob3N0
IHdlYiBjb250ZW50LCBpbmNsdWRpbmcgamF2YXNjcmlwdCwgaXMgZGlmZmVyZW50IHRvIHRoZSBh
YmlsaXR5IHRvIGhvc3Qgd2ViIHNlcnZlciBzY3JpcHRzOyB0aGVyZSB3b3VsZCBiZSBhIHNldCBv
ZiB1c2VycyB3aG8gY291bGQgaW5jbHVkZSBhIHdlaXJkcyBzY3JpcHQgb24gdGhlaXIgcGFnZSwg
YnV0IG5vdCBwdXQgYSBETlMgcmVzb2x2ZXIgc2VydmljZSBvbiB0aGVpciB3ZWIgaG9zdC7CoCBJ
IHRoaW5rIHRoaXMgd291bGQgYmUgYSBsZXNzIGNvbW1vbiBpc3N1ZSB0aGFuIGp1c3QgdGhlIGNv
bXBsZXhpdHkgb2YgcHJvY2Vzc2luZyBOQVBUUnMsIGJ1dCB3aGVuIGl0IGlzIGFuIGlzc3VlLCBp
dCdzIGVmZmVjdGl2ZWx5IGFuIGludHJhY3RhYmxlIHByb2JsZW06IGNoYW5naW5nIHdlYiBob3N0
IHByb3ZpZGVycyBpcyBhIG5vbi1zb2x1dGlvbiwgSU1PLjxvOnA+PC9vOnA+PC9wcmU+PHAgY2xh
c3M9TXNvTm9ybWFsPkl0J3Mgb2YgY291cnNlIHRydWUgdGhhdCB5b3UgY2FuIGhvc3QgSlMgdy9v
IHRoZSBhYmlsaXR5IHRvIHJ1biBzZXJ2ZXItc2lkZSBzY3JpcHRzLiBIb3dldmVyLCBJJ20gYWZy
YWlkIHdlIGFyZSBwaWxpbmcgcmVzdHJpY3Rpb25zIHVwIHVwb24gdGhlIGJvb3RzdHJhcCBwcm9i
bGVtIChhbmQgbWF5YmUgb3RoZXJzKSB3aXRob3V0IGEgY2xlYXIgZGlyZWN0aW9uLiBJJ20gYWZy
YWlkIHRoYXQgd2UgY291bGQgZW5kIHVwIGhlcmUgY2hvb3NpbmcgYSB3b3JzZSB0ZWNobmljYWwg
c29sdXRpb24gaW4gdGhlIG5hbWUgb2YgYSByZXN0cmljdGlvbiB0aGF0IGVuZHMgdXAgYmVpbmcg
aW5jb21wYXRpYmxlIHdpdGggb3RoZXIgc3R1ZmYgd2UgZGVjaWRlIGxhdGVyIG9uLjxicj48YnI+
U3VtbWluZyBpdCB1cDogSSB0aGluayB3ZSBuZWVkIHRvIGdldCBvdXIgcmVzdHJpY3Rpb25zIGFu
ZCBib3JkZXIgY29uZGl0aW9ucyBjbGVhciBhbmQgZG9jdW1lbnRlZCBmaXJzdC4gTm90ZSB0aGF0
IEknbSBOT1QgdGFraW5nIHBvc2l0aW9uIGhlcmUgZWl0aGVyIGZvciBvciBhZ2FpbnN0IEJ5cm9u
J3MgY29tbWVudCBoZXJlLCBqdXN0IG1ha2luZyBhbiBvYnNlcnZhdGlvbiBvbiB0aGUgcGF0aCAo
SSB0aGluaykgd2Ugc2hvdWxkIGZvbGxvdy48YnI+PGJyPklNTywgVS1OQVBUUiBvciBVUkkgcmVj
b3JkcyAoc2VlIE9sYWYncyBlbWFpbCkgcGx1cyBoZWxwZXJzIChsb2NhbCBvciAzcmQgcGFydHkp
IGZvciB0aG9zZSBKUy1vbmx5IGltcGxlbWVudGF0aW9ucyBpcyBhIHJlYXNvbmFibGUgYm9vdHN0
cmFwIGltcGxlbWVudGF0aW9uLCBidXQgYWdhaW4sIGluIG9yZGVyIHRvIGRlY2lkZSwgd2UgbmVl
ZCB0byBnZXQgYSBjbGVhciBwaWN0dXJlIG9mIEFMTCB0aGUgcmVzdHJpY3Rpb25zIGFwcGxpZWQg
dG8gb3VyIGN1cnJlbnQgcHJvYmxlbSBzcGFjZS48YnI+PGJyPjxicj48YnI+PG86cD48L286cD48
L3A+PHByZT48bzpwPiZuYnNwOzwvbzpwPjwvcHJlPjxwcmU+SSdtIGN1cmlvdXMgYWJvdXQgaG93
IHN0cm9uZyB0aGUgcGVyY2VpdmVkIG5lZWQgaXMgZm9yIGNoYW5uZWwgc2VjdXJpdHksIHRvby7C
oCBJcyBpdCBzb21ldGhpbmcgd2Ugc2hvdWxkIGNvbnNpZGVyIG1hbmRhdG9yeSwgc29tZXRoaW5n
IHRoYXQgc2hvdWxkIGJlIG9wdGlvbmFsIGF0IHNlcnZpY2Ugb3BlcmF0b3IgZGlzY3JldGlvbiwg
b3IgcGVyaGFwcyByZWxhdGVkIHRvIGRpZmZlcmVudGlhbCBhY2Nlc3MgY2xhc3MgbmVlZHM/PG86
cD48L286cD48L3ByZT48cCBjbGFzcz1Nc29Ob3JtYWw+SU1PIHRoZXJlIHNob3VsZCBiZSBhIHJl
bGF0aW9uc2hpcC9jb3JyZXNwb25kZW5jZSBiZXR3ZWVuIGFjY2VzcyBjbGFzcyBhbmQgY2hhbm5l
bCBzZWN1cml0eSByZXF1aXJlbWVudHMuIFRoZSBoaWdoZXN0IGFjY2VzcyBjbGFzcyBsZXZlbHMg
c2hvdWxkIHByb2JhYmx5IHJlcXVpcmUgbm90IG9ubHkgYSBzZXJ2ZXItc2lkZSBjZXJ0IGJ1dCBh
IGNsaWVudC1zaWRlIG9uZSBhcyB3ZWxsICh3aGljaCB3b3VsZCBwcm92aWRlIGEgbmljZSB3YXkg
b2YgaW1wbGVtZW50aW5nIC8gZW5mb3JjaW5nIEJ1bGsgV0hPSVMgYWdyZWVtZW50cywgc29tZXRo
aW5nIHdoaWNoIGlzIGN1cnJlbnRseSBhcmUgZG9uZSBpbiBrbHVkZ3kgd2F5cyk8YnI+PGJyPkxv
d2VzdCBhY2Nlc3MgY2xhc3MgcHJvYmFibHkgY291bGQgYmUgc2VydmVyIG92ZXIgcGxhaW4gSFRU
UCwgd2l0aCBhIHByb3RlY3Rpb24gbGV2ZWwgc2ltaWxhciB0byBjdXJyZW50IHBvcnQgNDMgc2Vy
dmljZSAodGhhdCBpcywgbm8gcHJvdGVjdGlvbiBhdCBhbGwgOi0pICk8YnI+PGJyPjxvOnA+PC9v
OnA+PC9wPjxwcmU+PG86cD4mbmJzcDs8L286cD48L3ByZT48cHJlPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wcmU+PHByZT5BbHNvLCB0aGVyZSdzIGEgdGF4b25vbXkgaW52ZW50ZWQgYnkgSUNBTk4gZm9y
IHRoZXNlIHNlcnZpY2VzLCB0aG91Z2ggdGhleSBzYWRseSBmb3Jnb3Qgd2hhdCB0aGUgZmlyc3Qg
JnF1b3Q7TiZxdW90OyBpbiBJQ0FOTiBzdGFuZHMgZm9yLsKgIFJhdGhlciB0aGFuIHdlaXJkcy5h
cnBhLCBJIHdvdWxkIHByZWZlciB1cyB0byB1c2UgcmQtZHMuYXJwYSwgdGFraW5nIHRoZSAmcXVv
dDtETlJELURTJnF1b3Q7IHRheG9ub215IGFuZCBkcm9wcGluZyB0aGUgJnF1b3Q7RE4mcXVvdDsg
cGFydCA6LSk8bzpwPjwvbzpwPjwvcHJlPjxwIGNsYXNzPU1zb05vcm1hbD5EaWRuJ3Qga25vdyBh
Ym91dCB0aGF0LCB0aGFua3MhPGJyPjxicj48bzpwPjwvbzpwPjwvcD48cHJlPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wcmU+PHByZT48bzpwPiZuYnNwOzwvbzpwPjwvcHJlPjxwcmU+wqAgQnlyb248bzpw
PjwvbzpwPjwvcHJlPjxwIGNsYXNzPU1zb05vcm1hbD5jaGVlcnMhPGJyPjxicj5+Q2FybG9zPGJy
Pjxicj48bzpwPjwvbzpwPjwvcD48cHJlPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+PHByZT48bzpw
PiZuYnNwOzwvbzpwPjwvcHJlPjxwIGNsYXNzPU1zb05vcm1hbD48YnI+PGJyPjxicj48bzpwPjwv
bzpwPjwvcD48cHJlPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fPG86cD48L286cD48L3ByZT48cHJlPndlaXJkcyBtYWlsaW5nIGxpc3Q8bzpwPjwvbzpwPjwv
cHJlPjxwcmU+PGEgaHJlZj0ibWFpbHRvOndlaXJkc0BpZXRmLm9yZyI+d2VpcmRzQGlldGYub3Jn
PC9hPjxvOnA+PC9vOnA+PC9wcmU+PHByZT48YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3dlaXJkcyI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby93ZWlyZHM8L2E+PG86cD48L286cD48L3ByZT48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9
J21hcmdpbi1ib3R0b206MTIuMHB0Jz48bzpwPiZuYnNwOzwvbzpwPjwvcD48L2Rpdj48L2JvZHk+
PC9odG1sPg==

--_000_8CEF048B9EC83748B1517DC64EA130FB729CE5F571offwin200301a_--

From johnl@iecc.com  Wed Jul 25 21:02:25 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0697A11E8088 for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 21:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.137
X-Spam-Level: 
X-Spam-Status: No, score=-111.137 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xmgg79ztcQgL for <weirds@ietfa.amsl.com>; Wed, 25 Jul 2012 21:02:24 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id E62B121F849B for <weirds@ietf.org>; Wed, 25 Jul 2012 21:02:23 -0700 (PDT)
Received: (qmail 40232 invoked from network); 26 Jul 2012 04:02:21 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 26 Jul 2012 04:02:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5010c14d.xn--yuvv84g.k1207; i=johnl@user.iecc.com; bh=izUSJq+G8gfEG/iSmBam9w2NrX3i4TzRHn3OsZmTsmk=; b=hJ3HD3y362WwXGNCGYgg/cpgr+dD0dwMVcyxzFgxVJuAI4dUg3NHka5FsN9g8X9Kl2ksVpCuK7PF5/A5DVqFdSWKHJjFVqT2dgjoBtA2xPkKE3Q6yUWuysAteg4Bk1k86f4+a947owRmmU6+iW755MvvTGrvcWKkEL49VBctjpI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5010c14d.xn--yuvv84g.k1207; olt=johnl@user.iecc.com; bh=izUSJq+G8gfEG/iSmBam9w2NrX3i4TzRHn3OsZmTsmk=; b=YK9yeLTKlD6eiqDvsaufpWGnyDlz/Za9IUmFooVOC0NKx9PLBs2CqidkOjnZbEVPObatIiCwHG6e8+shH1pGlOy28QOHVSZk6bZs0v2ggq91iX7mFv1FZ4RfsATekYAaztms1WXZPJgdiffoiBqa+qE0OsRSK2AkJ//XmBuZdJw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 26 Jul 2012 04:01:59 -0000
Message-ID: <20120726040159.25253.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <8CEF048B9EC83748B1517DC64EA130FB729CE5F571@off-win2003-01.ausregistrygroup.local>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] SRV record stats
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 04:02:25 -0000

Since some data is generally better than no data, I did a quick survey
of TLD SRV records.

There are currently 314 TLDs in the root.

Of those, 36 have SRV records at _nicname._tcp.<tld>.  One (.gr)
points nowhere, presumably because they don't have WHOIS, the other 35
refer to port 43 on hosts whose names look like WHOIS servers.

268 return NXDOMAIN, meaning they publish nothing at that name.

The surprising part is that 9 returned NOERROR, meaning there
is something other than a SRV record there.  Eight of those
nine (kr, mp, ph, st, sy, tk, to, ws) have an A record.

The ones with A are wildcards: kr, ph, st, sy, tk, to.  *.mp is not a
wildcard, but *.<random string>.mp is.  Go figure.

One, _nicname._tcp.mil, returns NOERROR to every query I give it,
suggesting there may be some name defined below that, but it's not
a wildcard.

The award for the most creative misuse of the DNS goes to
Vietnam:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20716
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 4

;; QUESTION SECTION:
;_nicname._tcp.vn.		IN	A

;; ANSWER SECTION:
_nicname._tcp.vn.	53	IN	CNAME	wildcard.vnnic.net.vn.
wildcard.vnnic.net.vn.	42461	IN	A	203.162.57.28

;; AUTHORITY SECTION:
vnnic.net.vn.		42461	IN	NS	dns2.vnnic.net.vn.
vnnic.net.vn.		42461	IN	NS	dns3.vnnic.net.vn.
vnnic.net.vn.		42461	IN	NS	dns4.vnnic.net.vn.

;; ADDITIONAL SECTION:
dns2.vnnic.net.vn.	2861	IN	A	203.119.8.108
dns3.vnnic.net.vn.	42461	IN	A	203.119.36.107
dns4.vnnic.net.vn.	42461	IN	A	203.119.8.70
dns4.vnnic.net.vn.	42461	IN	AAAA	2001:dc8:5::70

Turns out that there's also a wildcard at *.vn.

So SRV records aren't unused, but they aren't exactly well-established
or consistently published, either.

R's,
John

From dk@hostmaster.ua  Thu Jul 26 01:24:03 2012
Return-Path: <dk@hostmaster.ua>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D64E21F8734 for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 01:24:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.307
X-Spam-Level: 
X-Spam-Status: No, score=-2.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zjM8JUfJPI3m for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 01:24:02 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 9D42821F85B4 for <weirds@ietf.org>; Thu, 26 Jul 2012 01:24:02 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 124E6207DD; Thu, 26 Jul 2012 04:24:01 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 26 Jul 2012 04:24:01 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references; s=smtpout; bh=x6Xayh39txGFQmdBFgzs9MHbBJQ=; b=CTw3B 3cJFtJrELrXAfCaX3kztV+V3Flnx0QQA9p8B+WmuNmTf/2ZfqEFoDlAalm+o6kPM BpenkpqBiig9cifmAGJECeld+dO7SVhCuNnSLQhHOpC3OclqtTOph8QWrSZz0OAM BV947bkV857Ga3CGual1mMN/IaPHsf082b87NE=
X-Sasl-enc: Lrim16/LPHgv4hmtaIdeGWNNC6ulOmoUlX30IkuDTvDS 1343291040
Received: from [192.168.82.108] (unknown [93.72.133.129]) by mail.messagingengine.com (Postfix) with ESMTPA id 6840F4824E5; Thu, 26 Jul 2012 04:24:00 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Dmitry Kohmanyuk <dk@hostmaster.ua>
In-Reply-To: <20120725153315.21135.qmail@joyce.lan>
Date: Thu, 26 Jul 2012 11:24:01 +0300
Cc: weirds@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5A46737-4E05-4FD8-9343-AC9E055D3068@hostmaster.ua>
References: <20120725153315.21135.qmail@joyce.lan>
X-Mailer: Apple Mail (2.1278)
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 08:24:03 -0000

On Jul 25, 2012, at 6:33 PM, John Levine wrote:

>> That presupposes that weirds.<tld> hasn't already been registered by =
a normal
>> registrant.
>=20
> Of course it has, in .com, .net, .org, and .info, but I don't think it
> would be a big problem to find a name like
> whois-information-server.<tld> that we can be reasonably sure is
> available across all the TLDs that are likely to implement WEIRDS.

this is not a good way to do it -- first, not all TLDs allow addition of =
arbitrary names just like that
(for example, some allow only third-level registrations, e.g. =
company.{com,org}.tld).

Moreover, even if TLD has no problem reserving such a name, there is a =
always (slight) possibility
of squatting the name just for purpose of exerting money.  Getting the =
message across to 300+ TLDs
would also be difficult (with more coming by next year if ICANN executes =
on their strategy.)

Therefore I proposed name with underscores in it, similar to SRV records =
for whois some TLDs have.

This may be not the best idea, but I suggest we do not pick any "magic" =
names - either reserved namespace
under .arpa.  SRV record for TLD itself would also work (or NAPTR =
record, or URI record.) =20

> While you're here, how hard would it be to add another 2LD in .UK, =
with
> CNAME or NS records at whois-information-server.uk (or whatever it
> is)?


What if <some country> government have to approve any "special" =
subdomain creation?=

From olaf@NLnetLabs.nl  Thu Jul 26 03:32:21 2012
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7075321F867D for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 03:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c27HHCm7lNFT for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 03:32:20 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 15DD721F8675 for <weirds@ietf.org>; Thu, 26 Jul 2012 03:32:19 -0700 (PDT)
Received: from dhcp-91.nlnetlabs.nl (dhcp-91.nlnetlabs.nl [213.154.224.91]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.5/8.14.4) with ESMTP id q6QAWEW0061973 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <weirds@ietf.org>; Thu, 26 Jul 2012 12:32:14 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
X-DKIM: OpenDKIM Filter v2.5.2 open.nlnetlabs.nl q6QAWEW0061973
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1343298737; bh=5VrO5WGJpQJANZ6NreiPzJzV/8Z72NTH6hyxFXSN6gY=; h=From:Subject:Date:To; b=VfNCvgeC0TUFSMRc1exnS0uxUWCyREzDHy/2UypapS2rKkpxJ6Fx8Wh03oMl4Ij45 dKKzTMOjBgbZqC1CcvaiJ++OleQw3FOlc6ves+KBVDac1K18LD91Ti38t/rCGEv2cO ieLsndQ88hf0iGMMXwiRvyyXM/RSfwXXuArTLpP4=
From: Olaf Kolkman <olaf@NLnetLabs.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_253283C4-6D73-42E0-99BF-FB1474955B82"; protocol="application/pkcs7-signature"; micalg=sha1
Message-Id: <6B2A6141-A0E7-4ED8-8482-503AA96F3976@NLnetLabs.nl>
Date: Thu, 26 Jul 2012 12:32:16 +0200
To: "weirds@ietf.org Working Group" <weirds@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
X-Mailer: Apple Mail (2.1485)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (open.nlnetlabs.nl [213.154.224.1]); Thu, 26 Jul 2012 12:32:15 +0200 (CEST)
Subject: [weirds] Updated Agenda for WEIRDS IETF 84
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 10:32:21 -0000

--Apple-Mail=_253283C4-6D73-42E0-99BF-FB1474955B82
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



Dear Colleagues,

Please find the updated agenda (revision 1.6) at:
http://www.ietf.org/proceedings/84/agenda/agenda-84-weirds

The agenda contains a note:
currently there are no specific documents that are being discussed. The =
assumption is that all  potential working group documents, the ones =
listed on http://tools.ietf.org/wg/weirds/, have been read as there may =
be references made to them.

That note is specifically relevant for Part. C. on the Agenda. Murray =
and myself will be preparing that part of the agenda during the IETF and =
may come with proposals shortly before or even during the meeting.

--Olaf



_______________________________________________________=20
Olaf Kolkman -- NLnet Labs
http://www.nlnetlabs.nl/








--Apple-Mail=_253283C4-6D73-42E0-99BF-FB1474955B82
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFZTCCBWEw
ggNJoAMCAQICAwsLCDANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQL
ExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3Jp
dHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0xMTEyMDIxOTAzMjVaFw0x
MzEyMDExOTAzMjVaMFsxGDAWBgNVBAMTD0NBY2VydCBXb1QgVXNlcjEdMBsGCSqGSIb3DQEJARYO
b2xhZkBkYWNodC5uZXQxIDAeBgkqhkiG9w0BCQEWEW9sYWZAbmxuZXRsYWJzLm5sMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAu9+4/QDUSUBbyo9F/2AdyNMy3AAKxCDo0yS+oZcEB6kP
jXJ4nbGVg9D/FPs9Ptc7v7U3SQJyFW1MoaW3LYHrosrN4QttWF71F72sbQbiLu21COYzGnjqaW9W
3dyB64BUV6z7iBNtfXrCvR6haG4rycrjXK3miN3QqA/NFgfx3PlKHghpxoxslB4eEIBwG/9m/P+n
mwciLj2HQvyuYVNi8GYbt1SIM/Pu2zcokMGFGqvZ1OetE/PJnXW4DcE9ZWweCVPMGfIzim6ztB87
4b/XmeXWjtvsMEPhFAxTLcbzzyqk4/lnvoV+jdfSR0q+G2su5WjtYPSpH1MgYWN9jl8wrQIDAQAB
o4IBDjCCAQowDAYDVR0TAQH/BAIwADBWBglghkgBhvhCAQ0ESRZHVG8gZ2V0IHlvdXIgb3duIGNl
cnRpZmljYXRlIGZvciBGUkVFIGhlYWQgb3ZlciB0byBodHRwOi8vd3d3LkNBY2VydC5vcmcwQAYD
VR0lBDkwNwYIKwYBBQUHAwQGCCsGAQUFBwMCBgorBgEEAYI3CgMEBgorBgEEAYI3CgMDBglghkgB
hvhCBAEwMgYIKwYBBQUHAQEEJjAkMCIGCCsGAQUFBzABhhZodHRwOi8vb2NzcC5jYWNlcnQub3Jn
MCwGA1UdEQQlMCOBDm9sYWZAZGFjaHQubmV0gRFvbGFmQG5sbmV0bGFicy5ubDANBgkqhkiG9w0B
AQUFAAOCAgEAd/4gIMiP30NkhMKcm0CxIouebiGjihb44a7EjW/P5TRtJMJRhU3mAgAECMismUGm
qxOM6EBc7BwKnj2ckOiPEdyvrVcC3dpOVZy5PGjIEHKNFRpIBz96JVr1Q2ZoJFZXNBYC8JraQxk3
gdfI0bIfr9ID09KrJbLqmr6Qnwku2e82ltO3gZ3Q4ff50AIbiJHlvdOG9UrZc7E6y46LOlzhZlAU
uw23b3QS8JP3HbT6OG6KS/OnOBZrhnJq19XLDtlDCNv4TAURBN7otVmVkTLbOzuQ6Lhkrb8TPybJ
sPxTPx1GfnD+PcjH+MQNS4bLb6Ta7DgLCwbkFd34XblRpJr8v3f1/pvKS450T+/D9vkrWR0gg9r4
ZF77O7GiIfsSygsGYHz793B4TX5I+BFqndxhNOEnpcEE7GYTMSP7+NqQhEETUGrpe189o8Ws2Tnw
NM5rJ2EeqFi/QbwlxtmZJd837005fNJXliDy8qBu7ziq/2Ikm0Z2GaDEa60vsZe4f0AacswcZdTq
XygyEymjikhHVsUl6cUvoaOLSGvOJ4RCL1xev2RQod1VeS0S/5tmxaEq93MzPp23bvxQ+MIRoK6U
nAqskkCbuujlNUsGfyVq1SCHMUztKuuGrVvxs9NftOyPmBS6hbbvSGK+pWiqViRnL2K3bhdDH21u
ToDRHoqdxe4xggMzMIIDLwIBATCBgDB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQLExVodHRw
Oi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAf
BgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDCwsIMAkGBSsOAwIaBQCgggGHMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDcyNjEwMzIxNlowIwYJKoZI
hvcNAQkEMRYEFJR0DlBcH/q38s62U/FmgXw4ZFQKMIGRBgkrBgEEAYI3EAQxgYMwgYAweTEQMA4G
A1UEChMHUm9vdCBDQTEeMBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlD
QSBDZXJ0IFNpZ25pbmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5v
cmcCAwsLCDCBkwYLKoZIhvcNAQkQAgsxgYOggYAweTEQMA4GA1UEChMHUm9vdCBDQTEeMBwGA1UE
CxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25pbmcgQXV0aG9y
aXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcCAwsLCDANBgkqhkiG9w0BAQEF
AASCAQA4cvQ+W6uTLXo89/yRuNoPtYdt9V6YAVgKun+lmCxAYKBsia1/IgaGjg1xARYnJqZWlFes
uXJb7Hfd0xhJMM+Ey8fm//GLeTMgdKezH+kKoNPHLjVowz3JchZywE7WnTyHqQkFH6sFIv62RbXW
FbCRwrZE0GtqxguUk40FEMx/KtqKIxC78bzVhTQerlzVunT/O7tsLDiNAcD8nEnl/FF+WcWhghS8
PPJ65inSY+2yJ9KKOz/GZduK7mbUrMFyIZ3SPPnZ02Q/2m2HXbThihES1w5PxnUeb/+SGsHvheWs
KOdZiYLOlBwhuthK3lqXcsAOYtROafavMCKq87pdnMdRAAAAAAAA

--Apple-Mail=_253283C4-6D73-42E0-99BF-FB1474955B82--

From carlosm3011@gmail.com  Thu Jul 26 08:27:58 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 448EC21F86EA for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 08:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_64=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id atXjOGsFuXvj for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 08:27:57 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9FC3E21F86E5 for <weirds@ietf.org>; Thu, 26 Jul 2012 08:27:57 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so2295213ggn.31 for <weirds@ietf.org>; Thu, 26 Jul 2012 08:27:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=UOMFnh2/VsPZl/O9EGMnbPgFKYyB/KkGdtzRRTKHKI0=; b=Z4g41uX1z4ncL22PKuGx8tM1X+FkLdYbnQsNWxsf1gP5jUKgh6KBXDp+7CEk/SzAJK MYonsmNXTcdALwg1qDI67QeNSg1/9z1Uqio7SLjMONjDVnRljJioa8xSYEijAN60bYug tHwmNFYjhmX2huEpiE6aP4wzt+HEzYxMjCDqAVT5zJr+SAk4imcw/sPI/4APLYJrJi1c pcp8iFCQg7NPuHh8kef/h4VYMpMv4Yd9SJvbFUIlNw3u1VM8ow0mx5JbOeJTW8tKtWeY ImdG+y5rhNV39kpALmqzH4XHYD5XXsS/DwjZf4vNw33quhymaZ9CJtbLvcDix2Sn0dNp eg1g==
Received: by 10.236.46.229 with SMTP id r65mr28258946yhb.13.1343316477161; Thu, 26 Jul 2012 08:27:57 -0700 (PDT)
Received: from europa.local ([2001:13c7:7001:5128:d4d0:b94b:1ac0:3da4]) by mx.google.com with ESMTPS id b2sm8150456yhm.5.2012.07.26.08.27.54 (version=SSLv3 cipher=OTHER); Thu, 26 Jul 2012 08:27:55 -0700 (PDT)
Message-ID: <501161F8.4070106@gmail.com>
Date: Thu, 26 Jul 2012 12:27:52 -0300
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Dmitry Kohmanyuk <dk@hostmaster.ua>
References: <20120725153315.21135.qmail@joyce.lan> <C5A46737-4E05-4FD8-9343-AC9E055D3068@hostmaster.ua>
In-Reply-To: <C5A46737-4E05-4FD8-9343-AC9E055D3068@hostmaster.ua>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: weirds@ietf.org
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 15:27:58 -0000

Personally I love the idea of having all 'special purpose' or 'system'
domains kind of 'hidden' under '.arpa'. I'd rather have IANA delegate
weirds.arpa or host it themselves than us going around registering
domains under .com or any other general purpose {g,cc}TLD.

Again, thats IMO only.

cheers,

~Carlos

On 7/26/12 5:24 AM, Dmitry Kohmanyuk wrote:
> On Jul 25, 2012, at 6:33 PM, John Levine wrote:
>
>>> That presupposes that weirds.<tld> hasn't already been registered by a normal
>>> registrant.
>> Of course it has, in .com, .net, .org, and .info, but I don't think it
>> would be a big problem to find a name like
>> whois-information-server.<tld> that we can be reasonably sure is
>> available across all the TLDs that are likely to implement WEIRDS.
> this is not a good way to do it -- first, not all TLDs allow addition of arbitrary names just like that
> (for example, some allow only third-level registrations, e.g. company.{com,org}.tld).
>
> Moreover, even if TLD has no problem reserving such a name, there is a always (slight) possibility
> of squatting the name just for purpose of exerting money.  Getting the message across to 300+ TLDs
> would also be difficult (with more coming by next year if ICANN executes on their strategy.)
>
> Therefore I proposed name with underscores in it, similar to SRV records for whois some TLDs have.
>
> This may be not the best idea, but I suggest we do not pick any "magic" names - either reserved namespace
> under .arpa.  SRV record for TLD itself would also work (or NAPTR record, or URI record.)  
>
>> While you're here, how hard would it be to add another 2LD in .UK, with
>> CNAME or NS records at whois-information-server.uk (or whatever it
>> is)?
>
> What if <some country> government have to approve any "special" subdomain creation?
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds


From vesely@tana.it  Thu Jul 26 09:36:14 2012
Return-Path: <vesely@tana.it>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C6E621F85AD for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 09:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.606
X-Spam-Level: 
X-Spam-Status: No, score=-4.606 tagged_above=-999 required=5 tests=[AWL=0.113,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f07PbFnEN1qp for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 09:36:13 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 62BD721F85C7 for <weirds@ietf.org>; Thu, 26 Jul 2012 09:36:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1343320571; bh=buKWfr9jFNISomOTNPuvAZFbgMU8Q9JJlO8gpyGeUvQ=; l=1184; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=PtUYAJSELucoO7goykHKJX3Jb+WozrF9amkxKfcj39sG4+sWtlsH7VlPzLcNe4TbB FJvfVqlUAB2k0Q8IbQpXFlMK7bdjkxYpAI2ah0UA+L6E1ClEGoq8KD+lW9kIlw8jeL lbUssGxNhaMm4EBXmaBnswLMyWjidylOjGiRAaO8=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Thu, 26 Jul 2012 18:36:11 +0200 id 00000000005DC03F.00000000501171FB.0000366A
Message-ID: <501171FB.3040803@tana.it>
Date: Thu, 26 Jul 2012 18:36:11 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: weirds@ietf.org
References: <20120723185220.90066.qmail@joyce.lan> <348E4548-FEFE-494B-AE41-ADF807927DC2@apnic.net> <50105933.80209@gmail.com>
In-Reply-To: <50105933.80209@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [weirds] Channel security, was the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 16:36:14 -0000

Not sure on subject: "REST-pect-ful" vs "Redirection in the RESTful
WHOIS world".

On Wed 25/Jul/2012 22:38:11 +0200 Carlos Martinez-Cagnazzo wrote:
> On 7/23/12 11:42 PM, Byron Ellacott wrote:
> 
>> I'm curious about how strong the perceived need is for channel
>> security, too.  Is it something we should consider mandatory,
>> something that should be optional at service operator discretion,
>> or perhaps related to differential access class needs?
>
> IMO there should be a relationship/correspondence between access class
> and channel security requirements. The highest access class levels
> should probably require not only a server-side cert but a client-side
> one as well (which would provide a nice way of implementing /
> enforcing Bulk WHOIS agreements, something which is currently are done
> in kludgy ways)
> 
> Lowest access class probably could be server over plain HTTP, with a
> protection level similar to current port 43 service (that is, no
> protection at all :-) )

+1, TCP's triple handshake is enough of a protection.  For people
seeking an abuse-mailbox, which can often be done with a single DNS
query, it may be overkill already.

From johnl@iecc.com  Thu Jul 26 15:14:22 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B95E011E80BF for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 15:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.138
X-Spam-Level: 
X-Spam-Status: No, score=-111.138 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lak70lcIJRkL for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 15:14:22 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id A36ED11E80BD for <weirds@ietf.org>; Thu, 26 Jul 2012 15:14:21 -0700 (PDT)
Received: (qmail 53408 invoked from network); 26 Jul 2012 22:14:20 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 26 Jul 2012 22:14:20 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5011c13c.xn--30v786c.k1207; i=johnl@user.iecc.com; bh=0aTnbDE26GeUwsgJKPkDYW0DqjcgFIm5TQR7mWyiNfs=; b=XIC0bAWN4Pd/SLXKBw37ScTInU2QLof6fZg/wmohKRYZPouhQnyfIZXpxQIOwqu1dclK2D24RQos1Mp+RIxWyYDIfEkOoSZSas/j8H+Plut9hBHEnVA+mMN8h2OJH/ptbh8UjLYHcLRTaDy8UHhgOs0u6U87NuZYkyzaAIKq4/Y=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5011c13c.xn--30v786c.k1207; olt=johnl@user.iecc.com; bh=0aTnbDE26GeUwsgJKPkDYW0DqjcgFIm5TQR7mWyiNfs=; b=gDT92d1xwllGc7/HBgQoEuAhZ/0WfnuTAjNIhV2N7PHFQkv2xvA5zN0qJWFRT0K7iBsOx6vexTKrdvvu3YsWueUWr6zbz4BvAmH2r2hR06HukDCbmfmts/eHdHVvcUaMX4J+JGE5LN11REMAsnkbET5EphKAiaSHsj1hDA9vkME=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 26 Jul 2012 22:13:57 -0000
Message-ID: <20120726221357.63362.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <C5A46737-4E05-4FD8-9343-AC9E055D3068@hostmaster.ua>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 22:14:23 -0000

>> whois-information-server.<tld> that we can be reasonably sure is
>> available across all the TLDs that are likely to implement WEIRDS.
>
>this is not a good way to do it -- first, not all TLDs allow addition of arbitrary names just like that
>(for example, some allow only third-level registrations, e.g. company.{com,org}.tld).

But it isn't a registration, it's part of a service.

>This may be not the best idea, but I suggest we do not pick any "magic" names - either reserved namespace
>under .arpa.  SRV record for TLD itself would also work (or NAPTR record, or URI record.)  

That's not how SRV records work.  They have prefixes, it would be _nicname._tcp.<tld>.

If it's a problem to add a name for whois-information-server.<tld>, I expect the SRV name
would be just as bad.

>What if <some country> government have to approve any "special" subdomain creation?

I assume that means it might take a while before you could publish
your CNAME.  If it's a widespread problem, we could revisit
<tld>.WEIRDS.ARPA, but that has its own administrative issues.

We have over 300 TLDs managed by over 200 different entities.
Anything we do will cause some administrative problem for someone.  My
goal, at least, is to minimize the problems for WEIRDS clients, which
will vastly outnumber WEIRDS servers, and be technically
straightforward for servers to implement.

R's,
John

From johnl@iecc.com  Thu Jul 26 15:17:35 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 975C021F8491 for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 15:17:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.139
X-Spam-Level: 
X-Spam-Status: No, score=-111.139 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AzHw+pqZCGi0 for <weirds@ietfa.amsl.com>; Thu, 26 Jul 2012 15:17:35 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id B926021F848B for <weirds@ietf.org>; Thu, 26 Jul 2012 15:17:34 -0700 (PDT)
Received: (qmail 54635 invoked from network); 26 Jul 2012 22:17:34 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 26 Jul 2012 22:17:34 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5011c1fe.xn--i8sz2z.k1207; i=johnl@user.iecc.com; bh=bj9lTkiceEitUHGu/Bt2d2TmBhAOTCVP+2hKRcUZzww=; b=rgbt1NbfmvqEiUM21HtuzE8V220RrCTSRPszx5FfiCySW4iFXWimhHN6q5qE4IkQFgjAbkY2lmtJF7NpGuh0iXnCSRM3sP/qH2yI9W8cijfZmlmpgJrc2EHEfOlPDgN+aM8kcEx24Ze6R18SdP+ZGR+y0BwAFHmdctiqXa5iUIg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5011c1fe.xn--i8sz2z.k1207; olt=johnl@user.iecc.com; bh=bj9lTkiceEitUHGu/Bt2d2TmBhAOTCVP+2hKRcUZzww=; b=CpMplSzgVPbmJDHxboF2bUNs9bhJv+tGybFdMF6a1mIB71HDGGC/Qw8fKQQOWxawvfTAY1AbEsNnJ1AGxTpeV9gcy+sJrlXlQCqKeXoQLE6lij5kiAw2ArBs48k9RpSI56UPOodr/4AQLKUSr6Liaovo/I08uY5eMAZ+HSjMcjc=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 26 Jul 2012 22:17:12 -0000
Message-ID: <20120726221712.64258.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <501161F8.4070106@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: carlos@lacnic.net
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 22:17:35 -0000

>Personally I love the idea of having all 'special purpose' or 'system'
>domains kind of 'hidden' under '.arpa'. I'd rather have IANA delegate
>weirds.arpa or host it themselves than us going around registering
>domains under .com or any other general purpose {g,cc}TLD.

One concern is that if your WEIRDS server supports SSL, which it
probably would, then IANA would have to be involved in any request for
an SSL cert for <TLD>.WEIRDS.ARPA or whatever.  It might be just
validation requests from random SSL vendors as they go by, or it could mean
that they buy or issue the SSL certs on behalf of the TLDs.

If that were the case, do you think it would be a problem for the TLDs
you're familiar with?

R's,
John

From vesely@tana.it  Fri Jul 27 00:52:45 2012
Return-Path: <vesely@tana.it>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF6121F8618 for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 00:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.608
X-Spam-Level: 
X-Spam-Status: No, score=-4.608 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JmB9opPILVo3 for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 00:52:44 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 591BA21F8615 for <weirds@ietf.org>; Fri, 27 Jul 2012 00:52:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1343375562; bh=wFVQVGxX/IGSaFDOB03bInnRKutb08oKQEOenaw29/k=; l=1222; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=Uidwuyua4yDZ2sAZAzWQB0Zquq2SCE7U6aDHabmdoGwOyDlgBZwAdyjHq6xDJ17EC 1mRfBn60HCPN7D4+N+U9rPZrhsPjTK3GBiedsgXVZoqY2OA8HNeu0uFc1acRJgTLAd r6WHWmmWheuaFUOgjpY0yEmyyPqOsr8WHMd3GUQY=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Fri, 27 Jul 2012 09:52:42 +0200 id 00000000005DC039.00000000501248CA.000018A2
Message-ID: <501248CA.8070602@tana.it>
Date: Fri, 27 Jul 2012 09:52:42 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: weirds@ietf.org
References: <20120726221357.63362.qmail@joyce.lan>
In-Reply-To: <20120726221357.63362.qmail@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 07:52:45 -0000

On Fri 27/Jul/2012 00:13:57 +0200 John Levine wrote:
> 
> If it's a problem to add a name for whois-information-server.<tld>,
> I expect the SRV name would be just as bad.
> 
>> What if <some country> government have to approve any "special"
>> subdomain creation?
> 
> I assume that means it might take a while before you could publish
> your CNAME.  If it's a widespread problem, we could revisit
> <tld>.WEIRDS.ARPA, but that has its own administrative issues.

As a prospect user of such service, I would prefer the .ARPA
alternative.  However trusty TLD operators may be, IANA is seen as the
global authority on such issues, the most trustworthy of all.

In this respect, it would be a valuable source of order if IANA signed
SSL certificates to TLD operators.  Having the CA flag set on such
certificates would enable them to certificate their clients in turn.
That is to say, it would make more sense if the entities who issue
domain names also certify them, rather than the opposite way around.

Could such activity yield the income to operate WEIRDS servers?

> We have over 300 TLDs managed by over 200 different entities. 
> Anything we do will cause some administrative problem for someone.


From shollenbeck@verisign.com  Fri Jul 27 05:39:29 2012
Return-Path: <shollenbeck@verisign.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B1C821F865C for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 05:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k1rsrw2tB5ap for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 05:39:29 -0700 (PDT)
Received: from exprod6og116.obsmtp.com (exprod6og116.obsmtp.com [64.18.1.37]) by ietfa.amsl.com (Postfix) with ESMTP id 8942721F850D for <weirds@ietf.org>; Fri, 27 Jul 2012 05:39:22 -0700 (PDT)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob116.postini.com ([64.18.5.12]) with SMTP ID DSNKUBKL+epNJad2bu4vIWMgO6Xpi5IxBmZj@postini.com; Fri, 27 Jul 2012 05:39:25 PDT
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id q6RCdGMf011973 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 27 Jul 2012 08:39:17 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0247.003; Fri, 27 Jul 2012 08:39:17 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Alessandro Vesely <vesely@tana.it>, "weirds@ietf.org" <weirds@ietf.org>
Thread-Topic: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
Thread-Index: AQHNa8zRyk5NIRz2DUedYgTOs6931pc9ETTg
Date: Fri, 27 Jul 2012 12:39:15 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F0D659187@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <20120726221357.63362.qmail@joyce.lan> <501248CA.8070602@tana.it>
In-Reply-To: <501248CA.8070602@tana.it>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 12:39:29 -0000

> -----Original Message-----
> From: weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On
> Behalf Of Alessandro Vesely
> Sent: Friday, July 27, 2012 3:53 AM
> To: weirds@ietf.org
> Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful
> WHOIS world

[snip]

> In this respect, it would be a valuable source of order if IANA signed
> SSL certificates to TLD operators.  Having the CA flag set on such
> certificates would enable them to certificate their clients in turn.
> That is to say, it would make more sense if the entities who issue
> domain names also certify them, rather than the opposite way around.

Whole companies have been formed to provide CA services. It might be a stre=
tch for IANA to do it unless the scope is limited.

Scott

From carlosm3011@gmail.com  Fri Jul 27 06:23:13 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B61B721F8691 for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 06:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qkydDXYdgs2r for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 06:23:13 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2432921F8688 for <weirds@ietf.org>; Fri, 27 Jul 2012 06:23:13 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so3454032ghb.31 for <weirds@ietf.org>; Fri, 27 Jul 2012 06:23:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=BXysh7xmNHqGL0KTSnmOKs7Y3UCKp697oS1DHxdswzw=; b=zDck8ZZyPk3/y5Qgm1NmIYnlZjw2AIWk/1G8hEaxw0RcV1y8ZiZ2Yc2PiOn492XsO6 RhXz5WljukEDBXid6rnAU8B+8JGCHLS4/kCpm08VMACCCnpo40Q4Z5PbmT0LY64CNHaO ZdLOru/uI3KZu5RGKINFN7uIM9uS4ptpO2hRziWpjAWzQIjO5SPQho4hyG3jU4XTKnZC o63w6Z2mpljhtN5tylY5+8a2Mg2rvmj4wfxWAueXH+cx2j7s+Fie0WsJIE+YRTh0VsLH op6edbGJfAvIxRgHTdiHq9UsnNkvDnhGofLFs3rXM9+tV/4fjVhI2Pm8At8Dppye0AeD h3Bw==
Received: by 10.236.197.5 with SMTP id s5mr2211967yhn.114.1343395392747; Fri, 27 Jul 2012 06:23:12 -0700 (PDT)
Received: from europa.local ([200.7.85.155]) by mx.google.com with ESMTPS id e19sm1951623ann.10.2012.07.27.06.23.09 (version=SSLv3 cipher=OTHER); Fri, 27 Jul 2012 06:23:11 -0700 (PDT)
Message-ID: <5012963B.6020806@gmail.com>
Date: Fri, 27 Jul 2012 10:23:07 -0300
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
References: <20120726221357.63362.qmail@joyce.lan> <501248CA.8070602@tana.it> <831693C2CDA2E849A7D7A712B24E257F0D659187@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F0D659187@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "weirds@ietf.org" <weirds@ietf.org>, Alessandro Vesely <vesely@tana.it>
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 13:23:13 -0000

I like the idea of IANA issuing SSL certs only for limited purposes, and
with the CA bit on. I think this ties nicely with some concerns raised
earlier in this thread about the proliferation of potentially hundreds
of certs for multiple-domain registrars.

IANA already has been issuing certs for limited/specific purposes, so
this won't represent a huge leap into the unknown for them.

~Carlos

On 7/27/12 9:39 AM, Hollenbeck, Scott wrote:
>> -----Original Message-----
>> From: weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On
>> Behalf Of Alessandro Vesely
>> Sent: Friday, July 27, 2012 3:53 AM
>> To: weirds@ietf.org
>> Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful
>> WHOIS world
> [snip]
>
>> In this respect, it would be a valuable source of order if IANA signed
>> SSL certificates to TLD operators.  Having the CA flag set on such
>> certificates would enable them to certificate their clients in turn.
>> That is to say, it would make more sense if the entities who issue
>> domain names also certify them, rather than the opposite way around.
> Whole companies have been formed to provide CA services. It might be a stretch for IANA to do it unless the scope is limited.
>
> Scott
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds


From ajs@anvilwalrusden.com  Fri Jul 27 06:27:29 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9312321F8645 for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 06:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.252
X-Spam-Level: 
X-Spam-Status: No, score=-1.252 tagged_above=-999 required=5 tests=[AWL=-0.412, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m7QjGWdgRvts for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 06:27:29 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 2C07A21F862F for <weirds@ietf.org>; Fri, 27 Jul 2012 06:27:29 -0700 (PDT)
Received: from crankycanuck.ca (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 9A2CC8A031 for <weirds@ietf.org>; Fri, 27 Jul 2012 13:27:27 +0000 (UTC)
Date: Fri, 27 Jul 2012 09:27:25 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: weirds@ietf.org
Message-ID: <20120727132725.GB10573@crankycanuck.ca>
References: <20120726221357.63362.qmail@joyce.lan> <501248CA.8070602@tana.it> <831693C2CDA2E849A7D7A712B24E257F0D659187@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <5012963B.6020806@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5012963B.6020806@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 13:27:29 -0000

On Fri, Jul 27, 2012 at 10:23:07AM -0300, Carlos Martinez-Cagnazzo wrote:
> I like the idea of IANA issuing SSL certs only for limited purposes, and
> with the CA bit on. 

I don't think a protocol-development working group should go so deep
into the weeds of IANA operations.

Best,

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From carlosm3011@gmail.com  Fri Jul 27 06:43:47 2012
Return-Path: <carlosm3011@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F104521F86C5 for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 06:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCzI3nw7H5iA for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 06:43:47 -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 6934321F86C3 for <weirds@ietf.org>; Fri, 27 Jul 2012 06:43:47 -0700 (PDT)
Received: by yenq13 with SMTP id q13so3482743yen.31 for <weirds@ietf.org>; Fri, 27 Jul 2012 06:43:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=hfsZcCpFK2QPftTHubXVleDYX3pyEX3Y5eAQVQAjPN4=; b=SiRq9IrPnRlBvp00J9CsHREJR/AMU1ndIstbvaAfJQC3HrmIkKNcKMli2JeucwDXlY ZM57xWaW7bYAzO0txxiSUn6HWU0FCXwgq/rZA+nHn7WSDSUTvnmjZI+ccvts3PGZ9VCB BgqlXfmbIMUhsV96WLEjK759AvcioAk6aAR6UfOJZ27N7mtZewMgBZSjHaGpjdrOwpjQ RJ/j64/dR+VM5Z/ptYJHVqezdW12Sbp6zCP5yxvjDpZa0vGk84WrcsmIC+pHOq5KKjlD LDP0VYvdHeJWi3+BVwIxZveK7+Z5B+MIU0wlO2oSFTfQbWUbZZciqVo1k+SmlmSP/C3J CMtA==
Received: by 10.236.130.240 with SMTP id k76mr2469011yhi.20.1343396627065; Fri, 27 Jul 2012 06:43:47 -0700 (PDT)
Received: from europa.local ([200.7.85.155]) by mx.google.com with ESMTPS id r22sm2001808anh.6.2012.07.27.06.43.42 (version=SSLv3 cipher=OTHER); Fri, 27 Jul 2012 06:43:44 -0700 (PDT)
Message-ID: <50129B0C.3090803@gmail.com>
Date: Fri, 27 Jul 2012 10:43:40 -0300
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
References: <20120726221357.63362.qmail@joyce.lan> <501248CA.8070602@tana.it> <831693C2CDA2E849A7D7A712B24E257F0D659187@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <5012963B.6020806@gmail.com> <20120727132725.GB10573@crankycanuck.ca>
In-Reply-To: <20120727132725.GB10573@crankycanuck.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: weirds@ietf.org
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 13:43:48 -0000

Definitely not. But we can toy with the idea and if we think it has
merit, then have it processed through the appropriate channels.

~carlos

On 7/27/12 10:27 AM, Andrew Sullivan wrote:
> On Fri, Jul 27, 2012 at 10:23:07AM -0300, Carlos Martinez-Cagnazzo wrote:
>> I like the idea of IANA issuing SSL certs only for limited purposes, and
>> with the CA bit on. 
> I don't think a protocol-development working group should go so deep
> into the weeds of IANA operations.
>
> Best,
>
> A
>
>


From johnl@iecc.com  Fri Jul 27 10:49:10 2012
Return-Path: <johnl@iecc.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C08FC21F864E for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 10:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.14
X-Spam-Level: 
X-Spam-Status: No, score=-111.14 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9ogRPhv0TE3 for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 10:49:10 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id C6D3821F8648 for <weirds@ietf.org>; Fri, 27 Jul 2012 10:49:09 -0700 (PDT)
Received: (qmail 87514 invoked from network); 27 Jul 2012 17:49:07 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 27 Jul 2012 17:49:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5012d493.xn--hew.k1207; i=johnl@user.iecc.com; bh=xNgY6LqGTkpZ9vstIvAEwyma22BapOEhPdGwVXEKTCs=; b=fJkG8T3mofc+WYekqIcjHjJBormWVRN4FKwe0JK+GVzlSmqg8TIHjQHk9nDQj6udGvl+FgAF/Zd3q0je7Grgxu4du5ElbfX6GxwIer6IUKkZLkhyLd1eUTjrm0zZAQOi75tnswtgtIXkBsnGdAHdQEACqSwAHDKbpUZWRx6uWuI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5012d493.xn--hew.k1207; olt=johnl@user.iecc.com; bh=xNgY6LqGTkpZ9vstIvAEwyma22BapOEhPdGwVXEKTCs=; b=oSe+1C9cbug5hdloao4RH6lO1/x8vcw/N3oQ4Xn8w3sF6QZUaaIlYpm1UAwiL5ptRrZTOO4JgbzVsLBqXqJj63hI9SkxtsQ5BH5lKD4ikXKJ9MQKFrOI0XzF7Vk5Xxcd9Sc9yoe1HC8aljXsHY8UxuRSGcb054O9H2BUP/6mAs8=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 27 Jul 2012 17:48:45 -0000
Message-ID: <20120727174845.90687.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <501248CA.8070602@tana.it>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: vesely@tana.it
Subject: Re: [weirds] the bootstrap problem, Redirection in the RESTful WHOIS world
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 17:49:10 -0000

>In this respect, it would be a valuable source of order if IANA signed
>SSL certificates to TLD operators.

Since IANA's signing cert is unlikely to be in the list in anyone's
browser, this strikes me as an impressively user-hostile suggestion.

Technically, signging SSL certs is trivial.  (If you'd like your cert
signed by the extremely reputable Network Abuse Clearinghouse
authority, just ask.)  In practice, if your cert isn't in people's
browsers, it's worse than useless.

R's,
John


From alexandrsergeyev@gmail.com  Fri Jul 27 10:51:48 2012
Return-Path: <alexandrsergeyev@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F63711E80A1 for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 10:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level: 
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-1, WEIRD_PORT=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3QioV5J+4z8D for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 10:51:47 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 84E2E11E80B8 for <weirds@ietf.org>; Fri, 27 Jul 2012 10:51:47 -0700 (PDT)
Received: by wibhm11 with SMTP id hm11so6013467wib.13 for <weirds@ietf.org>; Fri, 27 Jul 2012 10:51:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=zgZM0wbdr5WE+Bit5bshq62UKhhD7R9muX2sl5g9EMU=; b=PxJKBmFv+t5KT8W68Jq0uXkXq2D3GnJwsq5/+nlhPTh8uXDOGO0/vYRSsHxKWX05w1 UrD2mrb9CYRvLIz4VnH2sT9I4kf1SZYJ4nMQIe8o73Z8eqMK2hhdgb1+TIK9dFLCG6Q4 jLDDCvuNGY8t1uE6AOIze1Ex4mer8ZW/cUv/7gICUbiNIpoSbfibvDH4KaOUW4BG6Icm PLmic8rZnAXQ8njmBEJK/Un8mT5CpQW9lyFjGKjLc8wwfve//RWr9drKchBet6AocNPb ZMKfvGz2hxL2oOygO0RoX0kYAaT6c27W3Stw6E4Bpl7bgaiWNBuiTGH/7XfFd1ktKk2a W5KA==
MIME-Version: 1.0
Received: by 10.180.79.229 with SMTP id m5mr8040627wix.13.1343411506692; Fri, 27 Jul 2012 10:51:46 -0700 (PDT)
Sender: alexandrsergeyev@gmail.com
Received: by 10.216.230.158 with HTTP; Fri, 27 Jul 2012 10:51:46 -0700 (PDT)
Date: Fri, 27 Jul 2012 13:51:46 -0400
X-Google-Sender-Auth: kJb_RVcTPtohgQmUGg3UT8QSHvI
Message-ID: <CAJbypPoc_BB7xBdbn-eCURFkU4-ti99=bg-q-KrQUxwRtfznZw@mail.gmail.com>
From: Alex Sergeyev <abc@alexsergeyev.com>
To: weirds@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [weirds] Service and software libraries from Dyn Labs
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 17:51:48 -0000

Hi Everyone,

We were playing with ideas to make our own WERIDS service for Dyn, and
I would like to share them with this list.

Few upfront notes:
* we don't know what proposal will be used to create standard on JSON
structures, we just use something that we felt is "ok for now" (easy
to change too)
* I'm just pointing you to the domain name links below but we intend
to use it for Dynamic DNS hosts, and other services too
* HTTPS uses self-signed cert, sorry about inconveniences

Here is domain registration info:

https://whois.dyndns.com:8043/domain/dyn.com

Subsequently you might ask "who is really that user" and use test:test
Basic authentication to see more.

(note that it's hard to instrument in browser, so I made link
https://whois.dyndns.com:8043/domain/dyn.com?private that will require
authentication via HTTP 401, same way
to make given auth have no effect and show "public data" again, you'd
need to use https://whois.dyndns.com:8043/domain/dyn.com?public
because once 401 was seen browsers will be sending auth all the time
:( .... I'm not sure if this should be solved somehow or no)

We wanted to make something more than just service and released simple
library that we built:

https://github.com/dyninc/flask-weirds

It's an extension to Python Flask framework, which is very easy to
understand web-framework. Our tool does not include any UI or client
part. We decided to check concepts of authenticated data access and
tool that implements "basic WEIRDS concepts", like JSON-XML output,
e.g. to get XML for previous domain, please use:

https://whois.dyndns.com:8043/domain/dyn.com.xml

I'm open to your opinions and comments, it's nice to see WEIRDS ideas
become reality.


Thank you.


Alex.

From alexandrsergeyev@gmail.com  Fri Jul 27 12:17:29 2012
Return-Path: <alexandrsergeyev@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85D2911E80C0 for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 12:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.828
X-Spam-Level: 
X-Spam-Status: No, score=-2.828 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RgsRjomY9WOY for <weirds@ietfa.amsl.com>; Fri, 27 Jul 2012 12:17:29 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id DA4B811E80C1 for <weirds@ietf.org>; Fri, 27 Jul 2012 12:17:28 -0700 (PDT)
Received: by weyu54 with SMTP id u54so2540375wey.31 for <weirds@ietf.org>; Fri, 27 Jul 2012 12:17:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=wwQ/a5lQ8SNIqOZmx71hz+Aoa32Ph3dut0x4116tFak=; b=fHrr81WIOZtAu7osbTcB6XQY7SJVGV2dVZiG9hqIDR7EqisowVF/LWolZgVv6se/oB bOEqzScNmrc4kAVxwQ8jkYlMtLIW2O8axTWiSCGxs1Z6EvG33ImPRKmMLJIlAU88xq+Q teaNLtAkF7nQbzO2roSd01yod1jkVEd2Qe7mi4lcH6fromOVaSc2/Usj6YIUDSmfKyIv Vw2UzynGcrWObJoXoVxAKYnVhLdO4bgIFVNz0D1hrJw5WF1WqmZAVZoBcL8aeYdj4AgI X886Zb4z4ETYMNW65d2/HNt8rm9SjGUScfHoZapht/X84awFSq4tDVNmfTgDbMwvO7V6 R1Zg==
MIME-Version: 1.0
Received: by 10.180.90.207 with SMTP id by15mr24088648wib.22.1343416647606; Fri, 27 Jul 2012 12:17:27 -0700 (PDT)
Sender: alexandrsergeyev@gmail.com
Received: by 10.216.230.158 with HTTP; Fri, 27 Jul 2012 12:17:27 -0700 (PDT)
In-Reply-To: <CAJbypPoc_BB7xBdbn-eCURFkU4-ti99=bg-q-KrQUxwRtfznZw@mail.gmail.com>
References: <CAJbypPoc_BB7xBdbn-eCURFkU4-ti99=bg-q-KrQUxwRtfznZw@mail.gmail.com>
Date: Fri, 27 Jul 2012 15:17:27 -0400
X-Google-Sender-Auth: F16BltvxKyAjQzV-pi4meJH9KG4
Message-ID: <CAJbypPp-q=8jm3sM3UBeKN4hP6-FpYr1f+5LWs6GhR261DHdYQ@mail.gmail.com>
From: Alex Sergeyev <abc@alexsergeyev.com>
To: weirds@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: Re: [weirds] Service and software libraries from Dyn Labs
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 19:17:29 -0000

Apologies for whoever tried my link it and received timeout,
apparently firewall rules were only letting our internal addresses to
access that and now it should be available to everyone. :)

From superuser@gmail.com  Tue Jul 31 16:05:11 2012
Return-Path: <superuser@gmail.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 210CC21F8781 for <weirds@ietfa.amsl.com>; Tue, 31 Jul 2012 16:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.664
X-Spam-Level: 
X-Spam-Status: No, score=-3.664 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBnLUaRchR+g for <weirds@ietfa.amsl.com>; Tue, 31 Jul 2012 16:05:10 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 33A3D21F8764 for <weirds@ietf.org>; Tue, 31 Jul 2012 16:05:09 -0700 (PDT)
Received: by lagv3 with SMTP id v3so4523331lag.31 for <weirds@ietf.org>; Tue, 31 Jul 2012 16:05:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=A9Ii6/OvEkC8yPY4J7tf+HwWH8b4CHHda5hrGUi7f0c=; b=ulAP9FLwfncY/I/5Vsf8bRzzbM3NVOe8N/tBgHFY311XRasoniWGXmKKgKmc9yCacX zydbcUHuy82hz6MiNCzAXWnbNbR6kveVMTWfQsT1VycUlcaVbaBg/l4bNfT+2/n8kfLq ecX1UKnTxprdioa25cewpGhEfNfAXhgDxpMJ80zHhJwJO68um/jYKSw4Ynl/srLpmrls Aai/NebMYUWzEX2eta1Pouhy51nmdaefvVK+8Y85VLlkABAPhDmMPOzxDGkmtgVKOIdr riTUS59uUIADXWXSZV+ymZrcB62kEmyh0WuwtShJ637wEtHHc/DAZosYO3bhHVoJebmz ar8Q==
MIME-Version: 1.0
Received: by 10.112.83.169 with SMTP id r9mr7167078lby.66.1343775909149; Tue, 31 Jul 2012 16:05:09 -0700 (PDT)
Received: by 10.112.89.3 with HTTP; Tue, 31 Jul 2012 16:05:09 -0700 (PDT)
Date: Tue, 31 Jul 2012 16:05:09 -0700
Message-ID: <CAL0qLwY8=qdGeREFQRV68WfVRpoHTE2WBd0h8SYJQztOfZJk5A@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: weirds@ietf.org
Content-Type: multipart/alternative; boundary=f46d0401fc43b8fdcf04c62835a6
Subject: [weirds] Slides posted
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 23:05:11 -0000

--f46d0401fc43b8fdcf04c62835a6
Content-Type: text/plain; charset=ISO-8859-1

Dear weirdos,

I have uploaded what I believe are the most recent copies of the slide
decks we've been sent in preparation for tomorrow morning's session.  If
you sent us some, please take a moment to confirm what you sent made it to
the downloads page and that I've posted the latest version.

The agenda and download links: http://tools.ietf.org/wg/weirds/agenda

See you tomorrow,
-MSK

--f46d0401fc43b8fdcf04c62835a6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear weirdos,<br><br>I have uploaded what I believe are the most recent cop=
ies of the slide decks we&#39;ve been sent in preparation for tomorrow morn=
ing&#39;s session.=A0 If you sent us some, please take a moment to confirm =
what you sent made it to the downloads page and that I&#39;ve posted the la=
test version.<br>
<br>The agenda and download links: <a href=3D"http://tools.ietf.org/wg/weir=
ds/agenda">http://tools.ietf.org/wg/weirds/agenda</a><br><br>See you tomorr=
ow,<br>-MSK<br>

--f46d0401fc43b8fdcf04c62835a6--
