From nobody Mon Jun 2 11:19:14 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC011A037B for ; Mon, 2 Jun 2014 11:19:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETuekWuNe6mH for ; Mon, 2 Jun 2014 11:19:11 -0700 (PDT) Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78C861A0032 for ; Mon, 2 Jun 2014 11:19:11 -0700 (PDT) Received: by mail-wg0-f43.google.com with SMTP id l18so5440210wgh.26 for ; Mon, 02 Jun 2014 11:19:05 -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=b+lP0uqkTIWKAmBBBrwkrE4dpjP6GyUKi8v3le2yYGc=; b=b+Po5SoeYIagGXAQ9+Xnri6FgBHN4WNO9I/+HDqOo21vFGdPgmWk315AuDMgYpaIXa 3G4muOOgGaxPnn746KUMk3gfY34VF8CuNw2Q9dwgzooyZyfYt/QLXms+EtZ19SihNmYr 7YI8eIY1BY8glGBxS5qzCLC/u9fS4ZZXCVl5jR0lnqLvbx1gYnl+jffYdMlZJVgwcfZB yBHFfmSRZ2q0FDbEXGxSzQvSEk28ZKFwICaiEHQHuJbflaPKJgAElrFl+yEiO1Ysqglb VIvlAc5N8oey3e4ihAWjkTprDPGi30zbUkg214wh3uLssYoKfxvIjhhu9ut0u5wIfC8p ZTyw== MIME-Version: 1.0 X-Received: by 10.180.75.102 with SMTP id b6mr24589283wiw.26.1401733143409; Mon, 02 Jun 2014 11:19:03 -0700 (PDT) Received: by 10.180.210.194 with HTTP; Mon, 2 Jun 2014 11:19:03 -0700 (PDT) In-Reply-To: References: Date: Mon, 2 Jun 2014 11:19:03 -0700 Message-ID: From: "Murray S. Kucherawy" To: Andy Newton Content-Type: multipart/alternative; boundary=f46d0438915515389404fade6eb0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/9OKfF4I-xiSCf_M7WkdEv_5U2Sg Cc: "weirds@ietf.org" Subject: Re: [weirds] IETF 90 scheduling X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2014 18:19:13 -0000 --f46d0438915515389404fade6eb0 Content-Type: text/plain; charset=UTF-8 So only two items so far. Does anyone think a 1.5 hour meeting is too long? Too short? The meeting request is due Friday. -MSK On Wed, May 28, 2014 at 7:03 AM, Andy Newton wrote: > A couple of us have started talking about an extension for routing > objects. Hopefully we can have something ready by IETF 90. > > -andy > > On May 27, 2014, at 10:28 AM, Murray S. Kucherawy > wrote: > > > Colleagues, > > > > The window is open for us to request a meeting slot for Toronto. > Contrary to our expectations, it doesn't appear we'll be finished before > then. Thus, we need to determine the size of the time slot we should > request. > > > > Please propose agenda items for this meeting in response to this thread. > If you are working on a document in WEIRDS that requires face time to > resolve some issues, or would like to make or request a presentation on a > particular topic, please let us know ASAP. > > > > Document authors: If you have any updates pending for your drafts, > please post them as soon as possible. This will help the WG decide what > things (if any) need to be discussed in Toronto. > > > > We need to submit our time slot request next Friday, June 6th, and our > preliminary agenda is due to the Secretariat on Friday, June 20th. > > > > -MSK, WEIRDS co-chair > > _______________________________________________ > > weirds mailing list > > weirds@ietf.org > > https://www.ietf.org/mailman/listinfo/weirds > > --f46d0438915515389404fade6eb0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
So only two items so far.=C2=A0 Does anyone think a 1.5 ho= ur meeting is too long?=C2=A0 Too short?=C2=A0 The meeting request is due F= riday.

-MSK


On Wed, May 28, 2014 at 7:03 AM, Andy Newton <andy@arin.net> wrote:
A couple of us have started talking about an= extension for routing objects. Hopefully we can have something ready by IE= TF 90.

-andy

On May 27, 2014, at 10:28 AM, Murray S. Kucherawy <superuser@gmail.com> wrote:

> Colleagues,
>
> The window is open for us to request a meeting slot for Toronto. =C2= =A0Contrary to our expectations, it doesn't appear we'll be finishe= d before then. =C2=A0Thus, we need to determine the size of the time slot w= e should request.
>
> Please propose agenda items for this meeting in response to this threa= d. =C2=A0If you are working on a document in WEIRDS that requires face time= to resolve some issues, or would like to make or request a presentation on= a particular topic, please let us know ASAP.
>
> Document authors: If you have any updates pending for your drafts, ple= ase post them as soon as possible. =C2=A0This will help the WG decide what = things (if any) need to be discussed in Toronto.
>
> We need to submit our time slot request next Friday, June 6th, and our= preliminary agenda is due to the Secretariat on Friday, June 20th.
>
> -MSK, WEIRDS co-chair
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds


--f46d0438915515389404fade6eb0-- From nobody Mon Jun 2 12:22:34 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 103F11A0223 for ; Mon, 2 Jun 2014 12:22:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.55 X-Spam-Level: X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gVsXSfqStCYG for ; Mon, 2 Jun 2014 12:22:23 -0700 (PDT) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id CC7061A0346 for ; Mon, 2 Jun 2014 12:22:22 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id 7AD0D16526F; Mon, 2 Jun 2014 15:22:17 -0400 (EDT) Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id B6A1F165247; Mon, 2 Jun 2014 15:22:16 -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.342.3; Mon, 2 Jun 2014 15:22:16 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0328.009; Mon, 2 Jun 2014 15:22:16 -0400 From: Andy Newton To: "Murray S. Kucherawy" Thread-Topic: [weirds] IETF 90 scheduling Thread-Index: AQHPebgCra/esIiU30yYU+NZW9yNXJtWStmAgAgjCICAABGqAA== Date: Mon, 2 Jun 2014 19:22:14 +0000 Message-ID: <98C117E0-02AC-4113-AE89-B9CEBABB5B2D@arin.net> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.30.37] Content-Type: multipart/alternative; boundary="_000_98C117E002AC4113AE89B9CEBABB5B2Darinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/qCiIr2p9sQvPPDi5Ppp12Fw9nnM Cc: "weirds@ietf.org" Subject: Re: [weirds] IETF 90 scheduling X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2014 19:22:29 -0000 --_000_98C117E002AC4113AE89B9CEBABB5B2Darinnet_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I=92m gonna go with just right. -andy On Jun 2, 2014, at 2:19 PM, Murray S. Kucherawy > wrote: So only two items so far. Does anyone think a 1.5 hour meeting is too long= ? Too short? The meeting request is due Friday. -MSK On Wed, May 28, 2014 at 7:03 AM, Andy Newton > wrote: A couple of us have started talking about an extension for routing objects.= Hopefully we can have something ready by IETF 90. -andy On May 27, 2014, at 10:28 AM, Murray S. Kucherawy > wrote: > Colleagues, > > The window is open for us to request a meeting slot for Toronto. Contrar= y to our expectations, it doesn't appear we'll be finished before then. Th= us, we need to determine the size of the time slot we should request. > > Please propose agenda items for this meeting in response to this thread. = If you are working on a document in WEIRDS that requires face time to reso= lve some issues, or would like to make or request a presentation on a parti= cular topic, please let us know ASAP. > > Document authors: If you have any updates pending for your drafts, please= post them as soon as possible. This will help the WG decide what things (= if any) need to be discussed in Toronto. > > We need to submit our time slot request next Friday, June 6th, and our pr= eliminary agenda is due to the Secretariat on Friday, June 20th. > > -MSK, WEIRDS co-chair > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds --_000_98C117E002AC4113AE89B9CEBABB5B2Darinnet_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable
I=92m gonna go with just right.

-andy

On Jun 2, 2014, at 2:19 PM, Murray S. Kucherawy <superuser@gmail.com> wrote:

So only two items so far.  Does anyone think a 1.5 ho= ur meeting is too long?  Too short?  The meeting request is due F= riday.

-MSK


On Wed, May 28, 2014 at 7:03 AM, Andy Newton <andy@arin.net>= ; wrote:
A couple of us have started talking about an extension for routing objects.= Hopefully we can have something ready by IETF 90.

-andy

On May 27, 2014, at 10:28 AM, Murray S. Kucherawy <superuser@gmail.com> wrote:

> Colleagues,
>
> The window is open for us to request a meeting slot for Toronto.  = ;Contrary to our expectations, it doesn't appear we'll be finished before t= hen.  Thus, we need to determine the size of the time slot we should r= equest.
>
> Please propose agenda items for this meeting in response to this threa= d.  If you are working on a document in WEIRDS that requires face time= to resolve some issues, or would like to make or request a presentation on= a particular topic, please let us know ASAP.
>
> Document authors: If you have any updates pending for your drafts, ple= ase post them as soon as possible.  This will help the WG decide what = things (if any) need to be discussed in Toronto.
>
> We need to submit our time slot request next Friday, June 6th, and our= preliminary agenda is due to the Secretariat on Friday, June 20th.
>
> -MSK, WEIRDS co-chair
> _______________________________________________
> weirds mailing list
> weirds@ietf.org
> https://www.ietf.org/mailman/listinfo/weirds



--_000_98C117E002AC4113AE89B9CEBABB5B2Darinnet_-- From nobody Mon Jun 2 18:52:23 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5A21A0010 for ; Mon, 2 Jun 2014 18:52:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.856 X-Spam-Level: * X-Spam-Status: No, score=1.856 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Woehltcd61Lj for ; Mon, 2 Jun 2014 18:52:21 -0700 (PDT) Received: from off-send01.tyo.jprs.co.jp (off-send01.tyo.jprs.co.jp [IPv6:2001:df0:8:17::10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 162CF1A000E for ; Mon, 2 Jun 2014 18:52:20 -0700 (PDT) Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send01.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id s531qEtw027650 for ; Tue, 3 Jun 2014 10:52:14 +0900 X-AuditID: ac120820-b7f638e000000e09-b7-538d2a4e76b3 Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id 8C.24.03593.E4A2D835; Tue, 3 Jun 2014 10:52:14 +0900 (JST) Date: Tue, 03 Jun 2014 10:51:54 +0900 (JST) Message-Id: <20140603.105154.209984651.kambe@jprs.co.jp> To: weirds@ietf.org From: Naoki Kambe In-Reply-To: <79DE5F32-00CB-4AB9-8B99-121AB2412B32@viagenie.ca> References: <79DE5F32-00CB-4AB9-8B99-121AB2412B32@viagenie.ca> Organization: Japan Registry Services Co., Ltd. X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJIsWRmVeSWpSXmKPExsWyRoiFT9dPqzfYYPFkRYv5XcdZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CV0XdmLXvBI96KAy1nWBoYt/B2MXJySAiYSKz8M5EZwhaTuHBv PVsXIxeHkMBJRonnfbPZQRIsAtoSX45eYgKxeQUsJL5f+csCYosICEssfvkOzBYWMJNYfq4L rJ5NQEVi2b3NYPWcAvYSy87vZgWxhQTsJE7+vANkc3DwC+hLTG1KgdhrJ9H0F2QMB9B4QYm/ O4RBwswC6hKfV39lhrAVJaZ0P2SfwMg/C6FqFpKqWUiqFjAyr2KUyU9L0y1OzUspzk03MNQr qczXyyooKtZLBtGbGMEhx6Gwg3HGKYNDjAIcjEo8vCsO9QQLsSaWFVfmHmKU5GBSEuWNVugN FuJLyk+pzEgszogvKs1JLT7EKMHBrCTCa/ANqJw3JbGyKrUoHyYlzcGiJM57/M+ZQCGB9MSS 1OzU1ILUIpisDAeHkgTvew2goYJFqempFWmZOSUIaSYOTpDhPEDD5TWBaniLCxJzizPTIfKn GCWlxHkPgzQLgCQySvPgel8xigO9IMxrDdLGA0wfcF2vgAYyAQ18W9UJMrAkESEl1cB4cFfC V4ESTbadSxdqN/VUvlvQ+GON/XuFzMzVjR3vw/KslCZXPu7TT571xjeFJ2de6iL1fTKn/q6O cpOpmKT96XPdWUnLBnt1lTUMuYe2dlXMWrzhj/W/VvVXgps2nVpZ//vxCaM7q9e/SPFwvSmj sfe0waydO/89c+qauEX0W9lVw1UTZHYdUGIpzkg01GIuKk4EAJwfDYTcAgAA Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/wPbh1NhAzu4_D0_NqvB6FfmlYIM Subject: Re: [weirds] bootstrap json registry proposal X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 01:52:22 -0000 SGVsbG8sDQoNClRoYW5rIHlvdSBmb3IgdGhlIGJvb3RzdHJhcCBwcm9wb3NhbC4gSGVyZSBhcmUg bXkgcXVpY2sgY29tbWVudHMuDQoNCkZyb206IE1hcmMgQmxhbmNoZXQgPG1hcmMuYmxhbmNoZXRA dmlhZ2VuaWUuY2E+DQpEYXRlOiBTYXQsIDMxIE1heSAyMDE0IDExOjAxOjAwIC0wNDAwDQo+ID09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQo+IElBTkEgUkRBUCBET01BSU4gQk9P VFNUUkFQIFJFR0lTVFJZDQo+ID09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQo+ IHsNCj4gICDigJxyZGFwLmJvb3RzdHJhcOKAnTogew0KPiAgICAg4oCcZG9tYWluIjogew0KPiAg ICAgICDigJxteWV4YW1wbGV0bGQu4oCdOiB7DQo+ICAgICAgICAgImhvc3QiOiAicmRhcC5leGFt cGxlLm9yZyIsDQo+ICAgICAgIH0sDQo+ICAgICAgICJteWV4YW1wbGUydGxkLiI6IHsNCj4gICAg ICAgICAiaG9zdCI6ICJyZGFwLmV4YW1wbGUubmV0IiwNCj4gICAgICAgICAicHJvdG9zIjogWyAi aHR0cCIgXSwNCj4gICAgICAgICAicHJvdG8iOiBbICJodHRwIiBdLA0KPiAgICAgICAgICJwcmVm aXgiOiAiIiwNCj4gICAgICAgfSwNCj4gICAgIH0sDQo+ICAgfSwNCj4gfQ0KDQpJIHRoaW5rIGEg bXVsdGlwbGUgaG9zdHMgY2hvaWNlIG1pZ2h0IGJlIHByZWZlcnJlZC4gIFNvbWUgVExEDQpyZWdp c3RyaWVzIG1pZ2h0IHdhbnQgdG8gcHJvdmlkZSBhIFJEQVAgc2VydmljZSBhdCBkaWZmZXJlbnQg bmFtZXMuDQpGb3IgZXhhbXBsZSwNCg0KICAiaG9zdHMiOiBbDQogICAgInJkYXAxLmV4YW1wbGUu bmV0IiwNCiAgICAicmRhcDIuZXhhbXBsZS5uZXQiDQogIF0sIC4uDQoNCkhvdyBjYW4gd2UgcmVw cmVzZW50IGEgVVJMIHRlbXBsZXRlIHdoZW4gc3BlY2lmeWluZyBhbiBhcmJpdHJhcnkgcG9ydA0K bnVtYmVyIGluIHRoaXMgYm9vdHN0cmFwPyBGb3IgZXhhbXBsZSwgaWYgd2UgcHJvdmlkZSBhIFJE QVAgc2VydmljZSBhdA0KDQogIGh0dHA6Ly9yZGFwLmV4YW1wbGUudGxkOjgwODAvcmRhcA0KDQpI b3cgZG8gd2UgZGlzdHJpYnV0ZSB0aGVzZSBib290c3RyYXAgcmVnaXN0cmllcz8gIEZvciBleGFt cGxlLCBpcyBhbg0KSUFOQSBVUkwgbGlrZSB0aGlzPw0KDQogIGh0dHA6Ly9leGFtcGxlLmlhbmEu b3JnL3JkYXAvZG9tYWluDQogID0+IHsNCiAgICAgICAicmRhcC5ib290c3RyYXAiOiB7DQogICAg ICAgICAiZG9tYWluIjogew0KICAgICAgICAgICAuLg0KICAgICAgICAgfQ0KICAgICAgIH0NCiAg ICAgfQ0KDQpSZWdhcmRzLA0KDQpOYW9raSBLYW1iZQ0K From nobody Wed Jun 4 09:07:46 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9597C1A02D9 for ; Wed, 4 Jun 2014 09:07:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.852 X-Spam-Level: X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HrnS9W0rUlLi for ; Wed, 4 Jun 2014 09:07:41 -0700 (PDT) Received: from outbound.afilias.info (outbound.afilias.info [66.199.183.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA55A1A02E2 for ; Wed, 4 Jun 2014 09:07:40 -0700 (PDT) Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.72) (envelope-from ) id 1WsDiv-0002yS-5z for weirds@ietf.org; Wed, 04 Jun 2014 16:07:33 +0000 Received: from mail-ie0-f174.google.com ([209.85.223.174]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1WsDiv-0000MU-5h for weirds@ietf.org; Wed, 04 Jun 2014 16:07:33 +0000 Received: by mail-ie0-f174.google.com with SMTP id lx4so7490264iec.33 for ; Wed, 04 Jun 2014 09:07:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=IRLk9KaQCimSXaSfhClLL7tfI8cvBPr7nSGLqtku1xo=; b=JUE2lb8ZS/APnTFV9yjETKFAfxH+YfXWp6x63Dx96vYBcdeBhLmMUJqqRer7kFiCB9 phm3m1C1KzqafiSdMkyR2HY9egO5As2Meo3ot+hKMEkASAklNRy3XRJHUm4Epp3ITsHv mhev7JXnrdolZtHuWGrxM/01nQFqX5ZRWr71l/78VybvzGtsjSN3NOfmXlITHsWgpyWr Lbt54miIj/VOHFD0K2zMVICx4AQ4nayh3tRxS/OEaS3PE0qmxIjJzIY5tmow5D41B5zL Iphal5Q7N2LX5IYpr0k82xSdb40rVS7M4BjKMO25cEofNOqdnigU8VL8GtivTmuUMYuj T/hw== X-Gm-Message-State: ALoCoQni+YC7MJt1ypHjeDlyZzlsfqFVhY3BYpQ507dnwyKChT/a5beiZ2rJO40X7OJDlU4WRMyxyvVl/vIDIQ0OAPaBWugNFuG24eWd0JM0Znb8VgvKFWE= X-Received: by 10.50.114.194 with SMTP id ji2mr8646722igb.21.1401898048378; Wed, 04 Jun 2014 09:07:28 -0700 (PDT) X-Received: by 10.50.114.194 with SMTP id ji2mr8646709igb.21.1401898048288; Wed, 04 Jun 2014 09:07:28 -0700 (PDT) Received: from [192.168.2.12] ([70.50.211.183]) by mx.google.com with ESMTPSA id o2sm5051754igp.12.2014.06.04.09.07.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Jun 2014 09:07:27 -0700 (PDT) Message-ID: <538F443B.2070507@afilias.info> Date: Wed, 04 Jun 2014 12:07:23 -0400 From: Ernie Dainow User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "Hollenbeck, Scott" , "weirds@ietf.org" References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/p9uVrwzohY3S2LSEF7Fn2wYm8-k Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London - handles X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 16:07:42 -0000 On 2014-05-12 12:53 PM, Hollenbeck, Scott wrote: > 10. Handle Search (http://trac.tools.ietf.org/wg/weirds/trac/ticket/10#) > > I vaguely recall Ernie Dainow suggesting that this search was useful, but I'm inclined to remove it per Andy's suggestion > I suggested that handles should be removed altogether from all RDAP queries and responses, both lookup and search. draft-ietf-weirds-json-response specifies that Each object class contains a "links" array ... (section 6. Object Classes) A link is a more convenient way to get the details of say an entity than having to do a lookup by handle. Handles are leftover from WHOIS which needs them since links are not provided. If we are to have handles in RDAP for consistency with WHOIS, then we should have search by handles, which is supported by WHOIS. -Ernie From nobody Wed Jun 4 09:10:17 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA861A02D9 for ; Wed, 4 Jun 2014 09:10:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.852 X-Spam-Level: X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnP8QamXg1gz for ; Wed, 4 Jun 2014 09:10:11 -0700 (PDT) Received: from outbound.afilias.info (outbound.afilias.info [66.199.183.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4966F1A0302 for ; Wed, 4 Jun 2014 09:10:11 -0700 (PDT) Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.72) (envelope-from ) id 1WsDlM-0003CB-6R for weirds@ietf.org; Wed, 04 Jun 2014 16:10:05 +0000 Received: from mail-ie0-f169.google.com ([209.85.223.169]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1WsDlM-0000SD-60 for weirds@ietf.org; Wed, 04 Jun 2014 16:10:04 +0000 Received: by mail-ie0-f169.google.com with SMTP id rp18so6261556iec.0 for ; Wed, 04 Jun 2014 09:09:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=YZjWvMDs5CyL7DakR4/6IJBGbrL+JMTPQO9tBxwyGP8=; b=UqNhP1JXrDKYAdONfcdmTipJYKlAclApYGfW+iH8zVSZN+Na3JQm16qNCQlJWff0/N 3aslpI1odtC05qeHD0CxgNtkGEXjZ/6A77yk6ooQxwhHkft3NTrpQQNYk+Dj5VKRLgp4 vSEjHKw1FqGkOFdcj2zbq19zQFc0bucYEjdGshaxiKlnjTNdQwoPYxOGOiufRmm2xZyS WOB8FebsFr2ZD4waxQ3TupVst4zr/yLfd9MvsxsXobaAGbgJzdJQ4orNYYr0OblXcQA7 nbGP+JAokyr8Sq7PJ5iJzkm1auFtV2XzNcXpkUqWDLka2r5B+TObyWnzNo8QPLl/sP8l IUIg== X-Gm-Message-State: ALoCoQlhJCzJPT1zPfzl0stjYHMC9FWUZn6RpiDrJZUKTswdtQSMe7gtDth+fJWBMarO8s6uVmXM/V+aWOxWvmbSyNyQ9ufE6XYj3mU9yCSQFNfdI+TbQLU= X-Received: by 10.50.109.202 with SMTP id hu10mr8886010igb.1.1401898199445; Wed, 04 Jun 2014 09:09:59 -0700 (PDT) X-Received: by 10.50.109.202 with SMTP id hu10mr8885998igb.1.1401898199380; Wed, 04 Jun 2014 09:09:59 -0700 (PDT) Received: from [192.168.2.12] ([70.50.211.183]) by mx.google.com with ESMTPSA id hy3sm10797183igb.1.2014.06.04.09.09.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Jun 2014 09:09:58 -0700 (PDT) Message-ID: <538F44D3.3050209@afilias.info> Date: Wed, 04 Jun 2014 12:09:55 -0400 From: Ernie Dainow User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "Hollenbeck, Scott" , "weirds@ietf.org" References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/rCqQkkP4OV0l9UxZ0Ih95yBiNfA Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 16:10:14 -0000 On 2014-05-12 12:53 PM, Hollenbeck, Scott wrote: > 25. Clarify what is done with unsupported queries (http://trac.tools.ietf.org/wg/weirds/trac/ticket/25#) > > Text will be added to say that the server should return a 400 (Bad Request) error code. > > This is already covered in draft-ietf-weirds-using-http-08 5.4 Malformed Queries If a server receives a query which it cannot interpret as an RDAP query, it returns a 400 response code. Optionally, it MAY include additional information regarding this negative answer in the HTTP entity body. I'm not sure we should repeat the same requirement in another document. However, it would be worth expanding on this in the query doc by showing that /domains?name=XXXX returns a 404 if XXXX does not exist in the registry, but /domains?names=XXXX returns 400, since it has an invalid query parameter. -Ernie From nobody Wed Jun 4 09:20:41 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8C961A02D9 for ; Wed, 4 Jun 2014 09:20:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QAqmgFI4BE3q for ; Wed, 4 Jun 2014 09:20:38 -0700 (PDT) Received: from exprod6og101.obsmtp.com (exprod6og101.obsmtp.com [64.18.1.181]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0F321A0381 for ; Wed, 4 Jun 2014 09:20:16 -0700 (PDT) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob101.postini.com ([64.18.5.12]) with SMTP ID DSNKU49HO8Y89MSQ68v/m+fApYLq2f6+33c5@postini.com; Wed, 04 Jun 2014 09:20:32 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 s54GKAje007320 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Jun 2014 12:20:10 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 4 Jun 2014 12:20:09 -0400 From: "Hollenbeck, Scott" To: Ernie Dainow , "weirds@ietf.org" Thread-Topic: [weirds] WEIRDS inactivity, and issues raised in London Thread-Index: AQHPa65e8lpUhYtXiU+BtiUf/JlMBps9I46QgCRm/ID//73hEA== Date: Wed, 4 Jun 2014 16:20:09 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F49412C4F@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F44D3.3050209@afilias.info> In-Reply-To: <538F44D3.3050209@afilias.info> 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 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/lETolV-FP1otVqDI64Lw0l5z3FE Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 16:20:39 -0000 > -----Original Message----- > From: Ernie Dainow [mailto:edainow@afilias.info] > Sent: Wednesday, June 04, 2014 12:10 PM > To: Hollenbeck, Scott; weirds@ietf.org > Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London >=20 >=20 > On 2014-05-12 12:53 PM, Hollenbeck, Scott wrote: > > 25. Clarify what is done with unsupported queries > (http://trac.tools.ietf.org/wg/weirds/trac/ticket/25#) > > > > Text will be added to say that the server should return a 400 (Bad > Request) error code. > > > > >=20 > This is already covered in draft-ietf-weirds-using-http-08 > 5.4 Malformed Queries > If a server receives a query which it cannot interpret as an RDAP > query, it returns a 400 response code. Optionally, it MAY include > additional information regarding this negative answer in the HTTP > entity body. >=20 > I'm not sure we should repeat the same requirement in another document. Agreed. I was planning to cite the using-http text to avoid replication. > However, it would be worth expanding on this in the query doc by > showing > that > /domains?name=3DXXXX > returns a 404 if XXXX does not exist in the registry, but >=20 > /domains?names=3DXXXX > returns 400, since it has an invalid query parameter. Describing a subset of the possible error conditions will only lead to ques= tions about the errors we don't explicitly identify. I'd rather not do this= . Scott From nobody Wed Jun 4 16:03:28 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 353971A037F for ; Wed, 4 Jun 2014 16:03:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.137 X-Spam-Level: X-Spam-Status: No, score=-1.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FU5dizWPsPyp for ; Wed, 4 Jun 2014 16:03:24 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57B271A0362 for ; Wed, 4 Jun 2014 16:03:24 -0700 (PDT) Received: (qmail 1587 invoked from network); 4 Jun 2014 23:03:17 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 4 Jun 2014 23:03:17 -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; s=1496d.538fa5b5.k1406; i=johnl@user.iecc.com; bh=Q45EHFod5lA/GuhMr7zBdzhYgKNVgJHPWrQI/h/9OL4=; b=wzXk7SRJtcETiSxvWDldi4slZ2GI6bPIwpTuUg9w3gnnZBZtubWQbLXfOFzkfONL2Q+q0Op4KhicnM+2jHXbryg7f/h5yCSmVJjownT6zBHq2EA1aornhLqSgxpF0E8sNV3fADJkMlTNxRpkpRS+lrVbnk0DoVG4bK6QfpY1C+BiYm71I88/RS1PSo8VzWAbTWFldZmyZUNi01h7C2t4oUfk6cWxIJbR+gfqFh0Xuz7Y514yGqC15fJRo96RLZQk 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; s=1496d.538fa5b5.k1406; olt=johnl@user.iecc.com; bh=Q45EHFod5lA/GuhMr7zBdzhYgKNVgJHPWrQI/h/9OL4=; b=mj+8ouRGigfFddh6AbWpuThY//6Lq94+Z+qO1i6YuWpZ+KVT5o6Xzt4913HqNCBEG6agqWyCysqhUdZiQ/tuNH7mRgDOHJSyZkAFs+VpgZm4QE+uwLNN2xpyZpLx+WpssvRa7L7cmVopw5GaY+YX2TaUp8n7L3gB+m927NbCvlzg20rzVwMFrU9CFlNpu/nZkVMjQAzUdg6qpA9lvC3Lo7Ml+u9H6V79HmAm168hm9WjePhkHt7Z2LKeVUiUAJYQ Date: 4 Jun 2014 23:02:55 -0000 Message-ID: <20140604230255.84332.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/qKtUso56767QxU2T-ObFB8Mxag4 Subject: Re: [weirds] IETF 90 scheduling X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 23:03:25 -0000 In article you write: >-=-=-=-=-=- >-=-=-=-=-=- > >So only two items so far. Does anyone think a 1.5 hour meeting is too >long? Too short? The meeting request is due Friday. It seems reasonable. I expect we can waste the entire slot rehashing the bootstrap arguments if you let us. Ernie's recent suggestion that we get rid of handles in favor of links is also worth thinking about if we don't have it resolved one way or the other by then. R's, John From nobody Tue Jun 10 08:37:17 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B684B1A01C4 for ; Tue, 10 Jun 2014 08:37:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ipz6dpCshJTQ for ; Tue, 10 Jun 2014 08:37:13 -0700 (PDT) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 0A04C1A01A0 for ; Tue, 10 Jun 2014 08:37:13 -0700 (PDT) Received: by smtp2.arin.net (Postfix, from userid 323) id 8BE0421367B; Tue, 10 Jun 2014 11:37:12 -0400 (EDT) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp2.arin.net (Postfix) with ESMTP id DEF80213671; Tue, 10 Jun 2014 11:37:11 -0400 (EDT) Received: from CHACAS01.corp.arin.net (10.1.30.107) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.342.3; Tue, 10 Jun 2014 11:37:11 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS01.corp.arin.net ([fe80::a98b:1e52:e85a:5979%13]) with mapi id 14.03.0181.006; Tue, 10 Jun 2014 11:37:11 -0400 From: Andy Newton To: Ernie Dainow Thread-Topic: [weirds] WEIRDS inactivity, and issues raised in London - handles Thread-Index: AQHPgA8cKCCxhA8LbEyganarF3He/Jtqxp8A Date: Tue, 10 Jun 2014 15:37:10 +0000 Message-ID: References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F443B.2070507@afilias.info> In-Reply-To: <538F443B.2070507@afilias.info> 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="Windows-1252" Content-ID: <22E94CDA72523E43BB0B9E1C4D7FA1A0@corp.arin.net> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/zAKYnll_NruealSXtIhPP-WdbrA Cc: "weirds@ietf.org" Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London - handles X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2014 15:37:14 -0000 On Jun 4, 2014, at 1:07 PM, Ernie Dainow wrote: >=20 > On 2014-05-12 12:53 PM, Hollenbeck, Scott wrote: >> 10. Handle Search (http://trac.tools.ietf.org/wg/weirds/trac/ticket/10#) >>=20 >> I vaguely recall Ernie Dainow suggesting that this search was useful, bu= t I'm inclined to remove it per Andy's suggestion >>=20 >=20 > I suggested that handles should be removed altogether from all RDAP queri= es and responses, both lookup and search. >=20 I strongly disagree. Handles are identifiers found in many registries used= a surrogate keys where a natural key does not make sense. I realize that f= or DNRs they seem less important, but they have important significance in t= he RIR world. > draft-ietf-weirds-json-response specifies that > Each object class contains a "links" array ... (section 6. Object Clas= ses) > A link is a more convenient way to get the details of say an entity than = having to do a lookup by handle. Handles are leftover from WHOIS which need= s them since links are not provided. I don=92t see the point here. Handles are, in many cases, the identifier th= at will be used to construct the links. > If we are to have handles in RDAP for consistency with WHOIS, then we sho= uld have search by handles, which is supported by WHOIS. Lookups by handles are perfectly reasonable, but searches by handle do not = make much sense as there is no defined structure for a handle other than th= ey are suppose to be unique per registry. We shouldn=92t use consistency as= a reason to drop data registries currently have or to carry forward someth= ing that doesn=92t make sense. -andy From nobody Tue Jun 10 08:41:05 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 756581A0202 for ; Tue, 10 Jun 2014 08:41:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.55 X-Spam-Level: X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tTXaYan-Q6fj for ; Tue, 10 Jun 2014 08:41: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 D3D1F1A01F6 for ; Tue, 10 Jun 2014 08:41:02 -0700 (PDT) Received: by smtp2.arin.net (Postfix, from userid 323) id 906EB2135CF; Tue, 10 Jun 2014 11:41:02 -0400 (EDT) Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp2.arin.net (Postfix) with ESMTP id 0C70B2135A9; Tue, 10 Jun 2014 11:41:02 -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.342.3; Tue, 10 Jun 2014 11:41:01 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0347.000; Tue, 10 Jun 2014 11:41:01 -0400 From: Andy Newton To: Scott Hollenbeck Thread-Topic: [weirds] WEIRDS inactivity, and issues raised in London Thread-Index: AQHPa65h2C4aSNLkvUmB4sqh8fp0uJs9cP+AgCQZi4CAAALcgIAJYw0A Date: Tue, 10 Jun 2014 15:41:00 +0000 Message-ID: <1017AC76-A38F-45FC-A302-2684C1824309@arin.net> References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F44D3.3050209@afilias.info> <831693C2CDA2E849A7D7A712B24E257F49412C4F@BRN1WNEXMBX01.vcorp.ad.vrsn.com> In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F49412C4F@BRN1WNEXMBX01.vcorp.ad.vrsn.com> 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: multipart/alternative; boundary="_000_1017AC76A38F45FCA3022684C1824309arinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/iZ0viJ2JgARBSmwtjLx2SeMIfaI Cc: "weirds@ietf.org" Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2014 15:41:04 -0000 --_000_1017AC76A38F45FCA3022684C1824309arinnet_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Jun 4, 2014, at 1:20 PM, Hollenbeck, Scott > wrote: However, it would be worth expanding on this in the query doc by showing that /domains?name=3DXXXX returns a 404 if XXXX does not exist in the registry, but /domains?names=3DXXXX returns 400, since it has an invalid query parameter. Describing a subset of the possible error conditions will only lead to ques= tions about the errors we don't explicitly identify. I'd rather not do this= . I agree with Scott on this. -andy --_000_1017AC76A38F45FCA3022684C1824309arinnet_ Content-Type: text/html; charset="us-ascii" Content-ID: <5BF3740CAD23F24DAD900C6F83B7FA60@corp.arin.net> Content-Transfer-Encoding: quoted-printable
On Jun 4, 2014, at 1:20 PM, Hollenbeck, Scott <shollenbeck@verisign.com> wrote:

However, it would be worth expanding on this in t= he query doc by
showing
that
/domains?name=3DXXXX
returns a 404 if XXXX does not exist in the registry, but

/domains?names=3DXXXX
returns 400, since it has an invalid query parameter.

Describing a subset of the possible error conditions will only lead to ques= tions about the errors we don't explicitly identify. I'd rather not do this= .

I agree with Scott on this.

-andy
--_000_1017AC76A38F45FCA3022684C1824309arinnet_-- From nobody Tue Jun 10 12:37:27 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE5C51A02AA for ; Tue, 10 Jun 2014 12:36:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4DjZkFK-e8dp for ; Tue, 10 Jun 2014 12:36:44 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id A04721A02A6 for ; Tue, 10 Jun 2014 12:36:43 -0700 (PDT) Received: from h229.viagenie.ca (h229.viagenie.ca [206.123.31.229]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 7AD36403C9; Tue, 10 Jun 2014 15:36:42 -0400 (EDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_DED0614F-5A2A-4507-9156-697D969D3BD6" Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: JF Tremblay In-Reply-To: Date: Tue, 10 Jun 2014 15:36:40 -0400 Message-Id: <2EAE9632-B065-4FEC-9AA4-9796EFD46CB0@viagenie.ca> References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F443B.2070507@afilias.info> To: "weirds@ietf.org" X-Mailer: Apple Mail (2.1878.2) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/qQXzo7z1VZEfQx6EtRt5PT9gp3g Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London - handles X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2014 19:36:50 -0000 --Apple-Mail=_DED0614F-5A2A-4507-9156-697D969D3BD6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Jun 10, 2014, at 11:37 AM, Andy Newton wrote: >> I suggested that handles should be removed altogether from all RDAP = queries and responses, both lookup and search. >>=20 >=20 > I strongly disagree. Handles are identifiers found in many registries = used a surrogate keys where a natural key does not make sense. I realize = that for DNRs they seem less important, but they have important = significance in the RIR world. Speaking as the former =93registry-guy=94 at a large ISP (ARIN region), = handle lookups and searches have been very useful to me in the past to = track the tree structure of different ORG-IDs and resources. We had = multiple organization handles from legacy (merger and al) and a fair = number of POCs assigned to different internal groups.=20 I second Andy in voicing support for handle queries, both lookup and = searches.=20 >> If we are to have handles in RDAP for consistency with WHOIS, then we = should have search by handles, which is supported by WHOIS. >=20 > Lookups by handles are perfectly reasonable, but searches by handle do = not make much sense as there is no defined structure for a handle other = than they are suppose to be unique per registry. We shouldn=92t use = consistency as a reason to drop data registries currently have or to = carry forward something that doesn=92t make sense. >=20 > -andy Although there isn=92t a mandated structure in handles, wildcard = searches are sometimes useful when memory fails and you only remember = the beginning of a handle, or when it wasn=92t noted properly in an = external system such as an IP management software (speaking of = experience). =20 JF Tremblay Viag=E9nie= --Apple-Mail=_DED0614F-5A2A-4507-9156-697D969D3BD6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
On Jun 10, 2014, at 11:37 AM, Andy Newton = <andy@arin.net> = wrote:

I = suggested that handles should be removed altogether from all RDAP = queries and responses, both lookup and search.


I strongly disagree.  Handles are identifiers found in = many registries used a surrogate keys where a natural key does not make = sense. I realize that for DNRs they seem less important, but they have = important significance in the RIR world.

Speaking as the former = =93registry-guy=94 at a large ISP (ARIN region), handle lookups and = searches have been very useful to me in the past to track the tree = structure of different ORG-IDs and resources. We had multiple = organization handles from legacy (merger and al) and a fair number of = POCs assigned to different internal = groups. 

I second Andy in voicing support = for handle queries, both lookup and searches. 

If we are to have handles in RDAP for consistency with WHOIS, then = we should have search by handles, which is supported by = WHOIS.

Lookups by handles are perfectly reasonable, but searches = by handle do not make much sense as there is no defined structure for a = handle other than they are suppose to be unique per registry. We = shouldn=92t use consistency as a reason to drop data registries = currently have or to carry forward something that doesn=92t make = sense.

-andy

Although there = isn=92t a mandated structure in handles, wildcard searches are sometimes = useful when memory fails and you only remember the beginning of a = handle, or when it wasn=92t noted properly in an external system such as = an IP management software (speaking of experience). =  

JF = Tremblay
Viag=E9nie
= --Apple-Mail=_DED0614F-5A2A-4507-9156-697D969D3BD6-- From nobody Tue Jun 10 19:20:43 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60E7C1A042D for ; Tue, 10 Jun 2014 19:20:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.043 X-Spam-Level: X-Spam-Status: No, score=-0.043 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PqXY_hC6nKvb for ; Tue, 10 Jun 2014 19:20:41 -0700 (PDT) Received: from off-send01.tyo.jprs.co.jp (off-send01.tyo.jprs.co.jp [IPv6:2001:df0:8:17::10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32CB11A03D9 for ; Tue, 10 Jun 2014 19:20:41 -0700 (PDT) Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send01.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id s5B2KW9J019000 for ; Wed, 11 Jun 2014 11:20:39 +0900 X-AuditID: ac120820-b7f638e000000e09-26-5397bcf6f5db Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id E5.40.03593.6FCB7935; Wed, 11 Jun 2014 11:20:38 +0900 (JST) Date: Wed, 11 Jun 2014 11:19:23 +0900 (JST) Message-Id: <20140611.111923.104059051.kambe@jprs.co.jp> To: weirds@ietf.org From: Naoki Kambe In-Reply-To: <1017AC76-A38F-45FC-A302-2684C1824309@arin.net> References: <538F44D3.3050209@afilias.info> <831693C2CDA2E849A7D7A712B24E257F49412C4F@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <1017AC76-A38F-45FC-A302-2684C1824309@arin.net> Organization: Japan Registry Services Co., Ltd. X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOIsWRmVeSWpSXmKPExsWyRoiFT/f7nunBBqceCFrM7zrO4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujCNzu1kKdnFWrL6ykLGB8SJ7FyMnh4SAicSsfQfYIGwxiQv3 1gPZXBxCAicZJVr2P2MESbAIaEvMfnSQtYuRg4NXwELiQE8lSFhEQFhi8ct3LCC2sICLxIoL q5lAbDYBFYll9zYzgZRzCthI3NvtDhIWEljFKPFzswpImF9AX2JqUwrEVjuJpr8gU0CGC0r8 3SEMEmYW0JLomfGYHcKWl9j+dg7zBEb+WQhVs5BUzUJStYCReRWjTH5amm5xal5KcW66gaFe SWW+XlZBUbFeMojexAgONw6FHYwzThkcYhTgYFTi4e0wmh4sxJpYVlyZe4hRkoNJSZTXcydQ iC8pP6UyI7E4I76oNCe1+BCjBAezkggvH0iONyWxsiq1KB8mJc3BoiTOy2zcGywkkJ5Ykpqd mlqQWgSTleHgUJLgDd0N1ChYlJqeWpGWmVOCkGbi4AQZzgM0PAykhre4IDG3ODMdIn+KUVJK nDcXJCEAksgozYPrfcUoDvSCMK87SJYHmDrgul4BDWQCGvjaE2xgSSJCSqqBUdjibmFdSICZ dOhxvrVtfs8fH/26ueRV8vRnnr6rc7d/cnpYbnikf56kksabzrUR20pYy5/6Z+3pi22fMjm9 g9//Qrfvik1+u17ot03cv8Y+7sp+aaMty7r1tt/wsORZfth+5q036R5vkq9919fsFpqa8Ufe P1V3w1W37m22k99pbE7L1LM5r8RSnJFoqMVcVJwIABq/l4TaAgAA Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/e11ejsq7zYsWUm0ui3wBehtUffQ Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 02:20:42 -0000 From: Andy Newton Date: Tue, 10 Jun 2014 15:41:00 +0000 > > On Jun 4, 2014, at 1:20 PM, Hollenbeck, Scott > wrote: > > However, it would be worth expanding on this in the query doc by > showing > that > /domains?name=XXXX > returns a 404 if XXXX does not exist in the registry, but > > /domains?names=XXXX > returns 400, since it has an invalid query parameter. > > Describing a subset of the possible error conditions will only lead to questions about the errors we don't explicitly identify. I'd rather not do this. > > I agree with Scott on this. I'm not sure this is directly related to this topic, but I have a further question. If it receives a query like the followings: /domains?name=example1.tld&name=example2.com&name=example3.com .. /nameservers?name=ns.example1.com&name=ns.example2.com&ip=192.0.2.1&ip=192.0.2.2 .. should it return all matching results or a 400 error? If the former case is correct, should it return results matching any of the conditions or matching all of the conditions? And should we explicitly document something about it? Regards, Naoki Kambe From nobody Tue Jun 10 19:57:09 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CAF01A035E for ; Tue, 10 Jun 2014 19:57:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.738 X-Spam-Level: *** X-Spam-Status: No, score=3.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HhI0ARfZE6kS for ; Tue, 10 Jun 2014 19:57:05 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 7253F1A032E for ; Tue, 10 Jun 2014 19:57:04 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: jiashuo@cnnic.cn Received: from unknown218.241.103.147 (HELO cnnic) (218.241.103.147) by 218.241.118.7 with SMTP; Wed, 11 Jun 2014 10:56:58 +0800 From: =?gb2312?B?vNbLtg==?= To: "'Naoki Kambe'" , References: <538F44D3.3050209@afilias.info> <831693C2CDA2E849A7D7A712B24E257F49412C4F@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <1017AC76-A38F-45FC-A302-2684C1824309@arin.net> <20140611.111923.104059051.kambe@jprs.co.jp> In-Reply-To: <20140611.111923.104059051.kambe@jprs.co.jp> Date: Wed, 11 Jun 2014 10:57:08 +0800 Message-ID: <019f01cf8520$d5d00060$81700120$@cnnic.cn> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQHT0EkcCmLO0mvIuUYqsZRFWF2SygHt2g2xAjp+js0CW9z5SZsuffrw Content-Language: zh-cn Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/o_4jDQedsH75p_JGxpBeF9LDy9g Subject: [weirds] =?gb2312?b?tPC4tDogIFdFSVJEUyBpbmFjdGl2aXR5LCBhbmQgaXNz?= =?gb2312?b?dWVzIHJhaXNlZCBpbiBMb25kb24=?= X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 02:57:07 -0000 I think we should only handle the first parameter, and ignore other parameters. If we really need more complex condition, it may be better by extending search pattern, such as add 'OR' in conditions:=20 /domains?name=3Dexample1*.com OR example2*.com Regards=20 jiashuo -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: weirds [mailto:weirds-bounces@ietf.org] =B4=FA=B1=ED = Naoki Kambe =B7=A2=CB=CD=CA=B1=BC=E4: 2014=C4=EA6=D4=C211=C8=D5 10:19 =CA=D5=BC=FE=C8=CB: weirds@ietf.org =D6=F7=CC=E2: Re: [weirds] WEIRDS inactivity, and issues raised in = London From: Andy Newton Date: Tue, 10 Jun 2014 15:41:00 +0000 >=20 > On Jun 4, 2014, at 1:20 PM, Hollenbeck, Scott > wrote: >=20 > However, it would be worth expanding on this in the query doc by=20 > showing that /domains?name=3DXXXX returns a 404 if XXXX does not exist = > in the registry, but >=20 > /domains?names=3DXXXX > returns 400, since it has an invalid query parameter. >=20 > Describing a subset of the possible error conditions will only lead to questions about the errors we don't explicitly identify. I'd rather not = do this. >=20 > I agree with Scott on this. I'm not sure this is directly related to this topic, but I have a = further question. If it receives a query like the followings: /domains?name=3Dexample1.tld&name=3Dexample2.com&name=3Dexample3.com = .. =20 /nameservers?name=3Dns.example1.com&name=3Dns.example2.com&ip=3D192.0.2.1= &ip=3D192.0 .2.2 .. should it return all matching results or a 400 error? If the former case is correct, should it return results matching any of = the conditions or matching all of the conditions? And should we explicitly document something about it? Regards, Naoki Kambe _______________________________________________ weirds mailing list weirds@ietf.org https://www.ietf.org/mailman/listinfo/weirds From nobody Tue Jun 10 20:54:10 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7814C1A0358 for ; Tue, 10 Jun 2014 20:54:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.55 X-Spam-Level: X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lRulijQsCdDE for ; Tue, 10 Jun 2014 20:53:56 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 0F08D1A0356 for ; Tue, 10 Jun 2014 20:53:43 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn Received: from unknown127.0.0.1 (HELO user-think) (127.0.0.1) by 127.0.0.1 with SMTP; Wed, 11 Jun 2014 11:53:39 +0800 Date: Wed, 11 Jun 2014 11:54:10 +0800 From: "Linlin Zhou" To: "Naoki Kambe" , weirds References: <538F44D3.3050209@afilias.info>, <831693C2CDA2E849A7D7A712B24E257F49412C4F@BRN1WNEXMBX01.vcorp.ad.vrsn.com>, <1017AC76-A38F-45FC-A302-2684C1824309@arin.net>, <20140611.111923.104059051.kambe@jprs.co.jp> X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7, 2, 5, 140[cn] Mime-Version: 1.0 Message-ID: <2014061111540996545014@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart108284414824_=----" Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/9MAa5PoAx4Uo8eMmxFRZ98wodxE Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 03:54:07 -0000 This is a multi-part message in MIME format. ------=_001_NextPart108284414824_=---- Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: base64 SSB0aGluayB0aGlzIGEgY2FzZSBvZiB1bmtub3duIHBhcmFtZXRlcnMgZGVzY3JpYmVkIGluIHNl Y3Rpb24gNC4yIG9mIGh0dHAgZHJhZnQuIA0KVGhlIGZpcnN0IHBhcmFtZXRlciBjYW4gYmUgaWRl bnRpZmllZCBhbmQgb3RoZXIgdW5rbm93biBwYXJhbWV0ZXJzIHNob3VsZCBiZSBpZ25vcmVkLg0K DQpSZWdhcmRzLA0KDQoNCkxpbmxpbiBaaG91DQogDQpGcm9tOiBOYW9raSBLYW1iZQ0KRGF0ZTog MjAxNC0wNi0xMSAxMDoxOQ0KVG86IHdlaXJkcw0KU3ViamVjdDogUmU6IFt3ZWlyZHNdIFdFSVJE UyBpbmFjdGl2aXR5LCBhbmQgaXNzdWVzIHJhaXNlZCBpbiBMb25kb24NCkZyb206IEFuZHkgTmV3 dG9uIDxhbmR5QGFyaW4ubmV0Pg0KRGF0ZTogVHVlLCAxMCBKdW4gMjAxNCAxNTo0MTowMCArMDAw MA0KIA0KPiANCj4gT24gSnVuIDQsIDIwMTQsIGF0IDE6MjAgUE0sIEhvbGxlbmJlY2ssIFNjb3R0 IDxzaG9sbGVuYmVja0B2ZXJpc2lnbi5jb208bWFpbHRvOnNob2xsZW5iZWNrQHZlcmlzaWduLmNv bT4+IHdyb3RlOg0KPiANCj4gSG93ZXZlciwgaXQgd291bGQgYmUgd29ydGggZXhwYW5kaW5nIG9u IHRoaXMgaW4gdGhlIHF1ZXJ5IGRvYyBieQ0KPiBzaG93aW5nDQo+IHRoYXQNCj4gL2RvbWFpbnM/ bmFtZT1YWFhYDQo+IHJldHVybnMgYSA0MDQgaWYgWFhYWCBkb2VzIG5vdCBleGlzdCBpbiB0aGUg cmVnaXN0cnksIGJ1dA0KPiANCj4gL2RvbWFpbnM/bmFtZXM9WFhYWA0KPiByZXR1cm5zIDQwMCwg c2luY2UgaXQgaGFzIGFuIGludmFsaWQgcXVlcnkgcGFyYW1ldGVyLg0KPiANCj4gRGVzY3JpYmlu ZyBhIHN1YnNldCBvZiB0aGUgcG9zc2libGUgZXJyb3IgY29uZGl0aW9ucyB3aWxsIG9ubHkgbGVh ZCB0byBxdWVzdGlvbnMgYWJvdXQgdGhlIGVycm9ycyB3ZSBkb24ndCBleHBsaWNpdGx5IGlkZW50 aWZ5LiBJJ2QgcmF0aGVyIG5vdCBkbyB0aGlzLg0KPiANCj4gSSBhZ3JlZSB3aXRoIFNjb3R0IG9u IHRoaXMuDQogDQpJJ20gbm90IHN1cmUgdGhpcyBpcyBkaXJlY3RseSByZWxhdGVkIHRvIHRoaXMg dG9waWMsIGJ1dCBJIGhhdmUgYQ0KZnVydGhlciBxdWVzdGlvbi4NCiANCklmIGl0IHJlY2VpdmVz IGEgcXVlcnkgbGlrZSB0aGUgZm9sbG93aW5nczoNCiANCiAgL2RvbWFpbnM/bmFtZT1leGFtcGxl MS50bGQmbmFtZT1leGFtcGxlMi5jb20mbmFtZT1leGFtcGxlMy5jb20gLi4NCiANCiAgL25hbWVz ZXJ2ZXJzP25hbWU9bnMuZXhhbXBsZTEuY29tJm5hbWU9bnMuZXhhbXBsZTIuY29tJmlwPTE5Mi4w LjIuMSZpcD0xOTIuMC4yLjIgLi4NCiANCnNob3VsZCBpdCByZXR1cm4gYWxsIG1hdGNoaW5nIHJl c3VsdHMgb3IgYSA0MDAgZXJyb3I/DQogDQpJZiB0aGUgZm9ybWVyIGNhc2UgaXMgY29ycmVjdCwg c2hvdWxkIGl0IHJldHVybiByZXN1bHRzIG1hdGNoaW5nIGFueQ0Kb2YgdGhlIGNvbmRpdGlvbnMg b3IgbWF0Y2hpbmcgYWxsIG9mIHRoZSBjb25kaXRpb25zPw0KIA0KQW5kIHNob3VsZCB3ZSBleHBs aWNpdGx5IGRvY3VtZW50IHNvbWV0aGluZyBhYm91dCBpdD8NCiANClJlZ2FyZHMsDQogDQpOYW9r aSBLYW1iZQ0KIA0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18NCndlaXJkcyBtYWlsaW5nIGxpc3QNCndlaXJkc0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0 Zi5vcmcvbWFpbG1hbi9saXN0aW5mby93ZWlyZHMNCg== ------=_001_NextPart108284414824_=---- Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable =0A
I think this a case of unknown parameters describ= ed in section 4.2 of http draft. 
The first parameter can b= e identified and other unknown parameters should be ignored.
=0A
Regards,
=0A
Linlin Zhou
=0A
 
Fr= om: Naoki Kambe
Date: 2014-06-11 10:19
To: weirds
Subject: Re: = [weirds] WEIRDS inactivity, and issues raised in London
<= div>
From: Andy Newton <andy@arin.net>
=0A
Date: Tue, 1= 0 Jun 2014 15:41:00 +0000
=0A
 
=0A
>
=0A<= div>> On Jun 4, 2014, at 1:20 PM, Hollenbeck, Scott <shollenbeck@ver= isign.com<mailto:shollenbeck@verisign.com>> wrote:=0A
&= gt;
=0A
> However, it would be worth expanding on this in the= query doc by
=0A
> showing
=0A
> that
=0A> /domains?name=3DXXXX=0A
> returns a 404 if XXXX does n= ot exist in the registry, but
=0A
>
=0A
> /domain= s?names=3DXXXX
=0A
> returns 400, since it has an invalid quer= y parameter.
=0A
>
=0A
> Describing a subset of t= he possible error conditions will only lead to questions about the errors = we don't explicitly identify. I'd rather not do this.
=0A
> =0A
> I agree with Scott on this.
=0A
 
=0A<= div>I'm not sure this is directly related to this topic, but I have a=0A
further question.
=0A
 
=0A
If it receives= a query like the followings:
=0A
 
=0A
  /dom= ains?name=3Dexample1.tld&name=3Dexample2.com&name=3Dexample3.com .= .
=0A
 
=0A
  /nameservers?name=3Dns.example1.= com&name=3Dns.example2.com&ip=3D192.0.2.1&ip=3D192.0.2.2 ..=0A
 
=0A
should it return all matching results or a = 400 error?
=0A
 
=0A
If the former case is correct,= should it return results matching any
=0A
of the conditions or m= atching all of the conditions?
=0A
 
=0A
And should= we explicitly document something about it?
=0A
 
=0ARegards,
=0A
 
=0A
Naoki Kambe
=0A
&nbs= p;
=0A
_______________________________________________
=0Aweirds mailing list
=0A
weirds@ietf.org
=0A
https://w= ww.ietf.org/mailman/listinfo/weirds
=0A=0A<= /html> ------=_001_NextPart108284414824_=------ From nobody Wed Jun 11 06:01:45 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBBD31A00BF for ; Wed, 11 Jun 2014 06:01:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.55 X-Spam-Level: X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UkRKX-2GQwcf for ; Wed, 11 Jun 2014 06:01:43 -0700 (PDT) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id D0EEB1A00AA for ; Wed, 11 Jun 2014 06:01:42 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id 8C952165349; Wed, 11 Jun 2014 09:01:42 -0400 (EDT) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id 194251652AC; Wed, 11 Jun 2014 09:01: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.342.3; Wed, 11 Jun 2014 09:01:41 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0347.000; Wed, 11 Jun 2014 09:01:41 -0400 From: Andy Newton To: JF Tremblay Thread-Topic: [weirds] WEIRDS inactivity, and issues raised in London - handles Thread-Index: AQHPhOSfQ0dOlNCtiUurlNutSVawwptsI9YA Date: Wed, 11 Jun 2014 13:01:40 +0000 Message-ID: <5C052399-AFD9-48A9-9A64-5E97649BC774@arin.net> References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F443B.2070507@afilias.info> <2EAE9632-B065-4FEC-9AA4-9796EFD46CB0@viagenie.ca> In-Reply-To: <2EAE9632-B065-4FEC-9AA4-9796EFD46CB0@viagenie.ca> 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: multipart/alternative; boundary="_000_5C052399AFD948A99A645E97649BC774arinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/VK1k5GYgSC30FzQF4C9MDC4N2ac Cc: "weirds@ietf.org" Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London - handles X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 13:01:44 -0000 --_000_5C052399AFD948A99A645E97649BC774arinnet_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable On Jun 10, 2014, at 4:36 PM, JF Tremblay > wrote: Although there isn=92t a mandated structure in handles, wildcard searches a= re sometimes useful when memory fails and you only remember the beginning o= f a handle, or when it wasn=92t noted properly in an external system such a= s an IP management software (speaking of experience). Ok. That is a use case I had not thought imagined. Thanks. :) -andy --_000_5C052399AFD948A99A645E97649BC774arinnet_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable
On Jun 10, 2014, at 4:36 PM, JF Tremblay <jean-francois.tremblay@viagenie.ca> wro= te:

Although there isn=92t a mandated structure in handles, wildcard searches are somet= imes useful when memory fails and you only remember the beginning of a hand= le, or when it wasn=92t noted properly in an external system such as an IP = management software (speaking of experience).

Ok. That is a use case I had not thought imagined. Thanks. :)

-andy
--_000_5C052399AFD948A99A645E97649BC774arinnet_-- From nobody Wed Jun 11 06:31:50 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B34371A0088 for ; Wed, 11 Jun 2014 06:31:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CiunnrqyEBb4 for ; Wed, 11 Jun 2014 06:31:43 -0700 (PDT) Received: from exprod6og113.obsmtp.com (exprod6og113.obsmtp.com [64.18.1.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C40EC1A009E for ; Wed, 11 Jun 2014 06:31:40 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob113.postini.com ([64.18.5.12]) with SMTP ID DSNKU5haPF3qcqH92aSe/iMlV7sg6azq4pk1@postini.com; Wed, 11 Jun 2014 06:31:42 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 s5BDVdhq012759 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 11 Jun 2014 09:31:39 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 11 Jun 2014 09:31:38 -0400 From: "Hollenbeck, Scott" To: Andy Newton , JF Tremblay Thread-Topic: [weirds] WEIRDS inactivity, and issues raised in London - handles Thread-Index: AQHPhMHafBE9gOVaLkav+DtRU5//GptsI9YA///E3qA= Date: Wed, 11 Jun 2014 13:31:38 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F4941BDD6@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F443B.2070507@afilias.info> <2EAE9632-B065-4FEC-9AA4-9796EFD46CB0@viagenie.ca> <5C052399-AFD9-48A9-9A64-5E97649BC774@arin.net> In-Reply-To: <5C052399-AFD9-48A9-9A64-5E97649BC774@arin.net> 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: multipart/alternative; boundary="_000_831693C2CDA2E849A7D7A712B24E257F4941BDD6BRN1WNEXMBX01vc_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/PYp0V97Ui4ILpjcOl54kMoM0pVg Cc: "weirds@ietf.org" Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London - handles X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 13:31:47 -0000 --_000_831693C2CDA2E849A7D7A712B24E257F4941BDD6BRN1WNEXMBX01vc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable From: weirds [mailto:weirds-bounces@ietf.org] On Behalf Of Andy Newton Sent: Wednesday, June 11, 2014 9:02 AM To: JF Tremblay Cc: weirds@ietf.org Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London - hand= les On Jun 10, 2014, at 4:36 PM, JF Tremblay > wrote: Although there isn't a mandated structure in handles, wildcard searches are= sometimes useful when memory fails and you only remember the beginning of = a handle, or when it wasn't noted properly in an external system such as an= IP management software (speaking of experience). Ok. That is a use case I had not thought imagined. Thanks. :) [SAH] So do you think this is something we should add, Andy? Scott --_000_831693C2CDA2E849A7D7A712B24E257F4941BDD6BRN1WNEXMBX01vc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

From: weirds [= mailto:weirds-bounces@ietf.org] On Behalf Of Andy Newton
Sent: Wednesday, June 11, 2014 9:02 AM
To: JF Tremblay
Cc: weirds@ietf.org
Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London= - handles

 

 

On Jun 10, 2014, at 4:36 PM, JF Tremblay <jean-francois.tremblay@viage= nie.ca> wrote:



Although there isn’t a mandated = structure in handles, wildcard searches are sometimes useful when memory fa= ils and you only remember the beginning of a handle, or when it wasn’t noted properly in an external system such as an IP management= software (speaking of experience).

 

Ok. That is a use case I had not thought imagined. T= hanks. :)

 

[SAH] So do you think this is something we= should add, Andy?

Scott

--_000_831693C2CDA2E849A7D7A712B24E257F4941BDD6BRN1WNEXMBX01vc_-- From nobody Wed Jun 11 11:59:20 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B8C31A025A for ; Wed, 11 Jun 2014 11:59:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.55 X-Spam-Level: X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6W3n-UmpjbvP for ; Wed, 11 Jun 2014 11:59: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 355D41B2809 for ; Wed, 11 Jun 2014 11:59:04 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id E3E7F1653B4; Wed, 11 Jun 2014 14:59:03 -0400 (EDT) Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id DF6EE1653A9; Wed, 11 Jun 2014 14:59:02 -0400 (EDT) Received: from CHACAS01.corp.arin.net (10.1.30.107) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.342.3; Wed, 11 Jun 2014 14:59:02 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS01.corp.arin.net ([fe80::a98b:1e52:e85a:5979%13]) with mapi id 14.03.0181.006; Wed, 11 Jun 2014 13:05:30 -0400 From: Andy Newton To: Scott Hollenbeck Thread-Topic: [weirds] WEIRDS inactivity, and issues raised in London - handles Thread-Index: AQHPhXl8V0f8hzcDI0yUhVrHN32A55tsZs6A Date: Wed, 11 Jun 2014 17:05:30 +0000 Message-ID: <0F70B8A2-18AE-4DEA-A67B-8231E00D293B@arin.net> References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F443B.2070507@afilias.info> <2EAE9632-B065-4FEC-9AA4-9796EFD46CB0@viagenie.ca> <5C052399-AFD9-48A9-9A64-5E97649BC774@arin.net> <831693C2CDA2E849A7D7A712B24E257F4941BDD6@BRN1WNEXMBX01.vcorp.ad.vrsn.com> In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4941BDD6@BRN1WNEXMBX01.vcorp.ad.vrsn.com> 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: multipart/alternative; boundary="_000_0F70B8A218AE4DEAA67B8231E00D293Barinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/XLPpAVLIPYU0xRn3bL2kgT_svTw Cc: "weirds@ietf.org" Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London - handles X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2014 18:59:17 -0000 --_000_0F70B8A218AE4DEAA67B8231E00D293Barinnet_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable On Jun 11, 2014, at 10:31 AM, Hollenbeck, Scott > wrote: From: weirds [mailto:weirds-bounces@ietf.org] On Behalf Of Andy Newton Sent: Wednesday, June 11, 2014 9:02 AM To: JF Tremblay Cc: weirds@ietf.org Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London - hand= les On Jun 10, 2014, at 4:36 PM, JF Tremblay > wrote: Although there isn=92t a mandated structure in handles, wildcard searches a= re sometimes useful when memory fails and you only remember the beginning o= f a handle, or when it wasn=92t noted properly in an external system such a= s an IP management software (speaking of experience). Ok. That is a use case I had not thought imagined. Thanks. :) [SAH] So do you think this is something we should add, Andy? Scott Or more specifically, leave it in. We already have entity searches by handl= e. -andy --_000_0F70B8A218AE4DEAA67B8231E00D293Barinnet_ Content-Type: text/html; charset="Windows-1252" Content-ID: <83E3762DA6DBB446943EA8AFEEBB09E7@corp.arin.net> Content-Transfer-Encoding: quoted-printable
On Jun 11, 2014, at 10:31 AM, Hollenbeck, Scott <shollenbeck@verisign.com> wrote:


Or more specifically, leave it in. We already have entity searches by = handle.

-andy
--_000_0F70B8A218AE4DEAA67B8231E00D293Barinnet_-- From nobody Fri Jun 13 03:17:47 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4BBC1B2792 for ; Fri, 13 Jun 2014 03:17:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.851 X-Spam-Level: X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bG3jEKaTz4T1 for ; Fri, 13 Jun 2014 03:17:44 -0700 (PDT) Received: from outbound.afilias.info (outbound.afilias.info [66.199.183.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F00DC1A0460 for ; Fri, 13 Jun 2014 03:17:43 -0700 (PDT) Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.72) (envelope-from ) id 1WvOYI-0005Zw-4a for weirds@ietf.org; Fri, 13 Jun 2014 10:17:42 +0000 Received: from mail-ig0-f175.google.com ([209.85.213.175]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1WvOYI-0001e9-4B for weirds@ietf.org; Fri, 13 Jun 2014 10:17:42 +0000 Received: by mail-ig0-f175.google.com with SMTP id uq10so417393igb.2 for ; Fri, 13 Jun 2014 03:17:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=711cmJ2lFXRVkyT9UzCsVtBlhtO2f3lH/wKF1HBL+ZQ=; b=S/P7mQnvvV0NB7a2w1a5znsQAWfHZGtWtwz0VocQvTFNKlWuoas6nz7ZPXdsCJMbmv vXHYaTIyMXaL2E96EG2iD6hlkh3t/vn/6WNu7nQyNvzCkHs2nbS9h0UTX//MaST0Uzvh SDUOp2PY3kDobRuHZ41MR8GBvPNLZuFg+c4CU9cnIlfAFqLjCvxgFIT5MzciHJJyAXlc 3R2ERS4+owh6PYRGT368ikHU0ZZRvDOxdE4um1ahyLyuiaOrQ2I4rqUbMAhKzieXsPg2 5OnZzjzLce+NMdzuG12/kG6o/yc5yxaPgzkZvDhfjk/no+5jM83mkBKXW8LOse6kxJOo TCvA== X-Gm-Message-State: ALoCoQmmurk+XGTmM7ASIFRzvDlRu272vboJyJdrsi+YJDMA+ikTyHxD+whMqK6TzWqRtB96IM2lZ8gq/1Ox/LdmKqLfb66To9kbEFurGvZF8cCRLTS+7A8= X-Received: by 10.50.25.133 with SMTP id c5mr3140089igg.47.1402654656785; Fri, 13 Jun 2014 03:17:36 -0700 (PDT) X-Received: by 10.50.25.133 with SMTP id c5mr3140030igg.47.1402654656325; Fri, 13 Jun 2014 03:17:36 -0700 (PDT) Received: from [192.168.2.12] ([70.50.211.183]) by mx.google.com with ESMTPSA id cl7sm2191627igc.9.2014.06.13.03.17.34 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Jun 2014 03:17:35 -0700 (PDT) Message-ID: <539ACFBC.2000803@afilias.info> Date: Fri, 13 Jun 2014 06:17:32 -0400 From: Ernie Dainow User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Andy Newton , Scott Hollenbeck References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F44D3.3050209@afilias.info> <831693C2CDA2E849A7D7A712B24E257F49412C4F@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <1017AC76-A38F-45FC-A302-2684C1824309@arin.net> In-Reply-To: <1017AC76-A38F-45FC-A302-2684C1824309@arin.net> Content-Type: multipart/alternative; boundary="------------070605020304010008020705" Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/-t7-4UMrdDMrrTmOQtVSm93b8sE Cc: "weirds@ietf.org" Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2014 10:17:45 -0000 This is a multi-part message in MIME format. --------------070605020304010008020705 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 2014-06-10 11:41 AM, Andy Newton wrote: > > On Jun 4, 2014, at 1:20 PM, Hollenbeck, Scott > > wrote: > >>> However, it would be worth expanding on this in the query doc by >>> showing >>> that >>> /domains?name=XXXX >>> returns a 404 if XXXX does not exist in the registry, but >>> >>> /domains?names=XXXX >>> returns 400, since it has an invalid query parameter. >> >> Describing a subset of the possible error conditions will only lead >> to questions about the errors we don't explicitly identify. I'd >> rather not do this. > > I agree with Scott on this. > The argument to avoid "describing a subset of the possible error conditions" is contradicted by what is already in draft-ietf-weirds-using-http. Section 5 contains several sections covering a subset of HTTP errors, including 400 and 404. Without further guidelines, there will be a lot of inconsistencies between implementations. In the last inter-op test there were a number of cases where XXXX was an invalid name (such as example...com) or an invalid UTF-8 representation. Some believed that 400 should be returned, others interpreted 404 as the proper error. I suggest a statement to the effect that if the error is related to an invalid value of the parameter, 404 should be returned; but if the error is syntax or semantic (such as an invalid parameter), then 400 is returned. If 400/404 are used consistently, this provides useful feedback to help diagnose the problem. 404 is due to the user input, whereas 400 is generally a fault in the client implementation. -Ernie --------------070605020304010008020705 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 2014-06-10 11:41 AM, Andy Newton wrote:


However, it would be worth expanding on this in the query doc by
showing
that
/domains?name=XXXX
returns a 404 if XXXX does not exist in the registry, but

/domains?names=XXXX
returns 400, since it has an invalid query parameter.

Describing a subset of the possible error conditions will only lead to questions about the errors we don't explicitly identify. I'd rather not do this.

I agree with Scott on this.


The argument to avoid "describing a subset of the possible error conditions" is contradicted by what is already in draft-ietf-weirds-using-http. Section 5 contains several sections covering a subset of HTTP errors, including 400 and 404.
 
Without further guidelines, there will be a lot of inconsistencies between implementations. In the last inter-op test there were a number of cases where XXXX was an invalid name (such as example...com) or an invalid UTF-8 representation. Some believed that 400 should be returned, others interpreted 404 as the proper error.

I suggest a statement to the effect that if the error is related to an invalid value of the parameter, 404 should be returned; but if the error is syntax or semantic (such as an invalid parameter), then 400 is returned.

If 400/404 are used consistently, this provides useful feedback to help diagnose the problem. 404 is due to the user input, whereas 400 is generally a fault in the client implementation.

-Ernie

--------------070605020304010008020705-- From nobody Fri Jun 13 03:58:40 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2DE71B27F0 for ; Fri, 13 Jun 2014 03:58:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mifjd_JYvFLL for ; Fri, 13 Jun 2014 03:58:38 -0700 (PDT) Received: from exprod6og113.obsmtp.com (exprod6og113.obsmtp.com [64.18.1.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04D9D1A04AC for ; Fri, 13 Jun 2014 03:58:15 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob113.postini.com ([64.18.5.12]) with SMTP ID DSNKU5rZR7tQbwHOWdiZBmIt7a1NvnntvMJT@postini.com; Fri, 13 Jun 2014 03:58:37 PDT Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s5DAwEGK007357 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Jun 2014 06:58:14 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Fri, 13 Jun 2014 06:58:14 -0400 From: "Hollenbeck, Scott" To: Ernie Dainow , Andy Newton Thread-Topic: [weirds] WEIRDS inactivity, and issues raised in London Thread-Index: AQHPa65e8lpUhYtXiU+BtiUf/JlMBps9I46QgDHmhCeAAAsGEA== Date: Fri, 13 Jun 2014 10:58:13 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F4941F398@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F44D3.3050209@afilias.info> <831693C2CDA2E849A7D7A712B24E257F49412C4F@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <1017AC76-A38F-45FC-A302-2684C1824309@arin.net> <539ACFBC.2000803@afilias.info> In-Reply-To: <539ACFBC.2000803@afilias.info> 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: multipart/alternative; boundary="_000_831693C2CDA2E849A7D7A712B24E257F4941F398BRN1WNEXMBX01vc_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/FWpg-wUMVMF4zssciit7Sk7ySb8 Cc: "weirds@ietf.org" Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2014 10:58:39 -0000 --_000_831693C2CDA2E849A7D7A712B24E257F4941F398BRN1WNEXMBX01vc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable From: Ernie Dainow [mailto:edainow@afilias.info] Sent: Friday, June 13, 2014 6:18 AM To: Andy Newton; Hollenbeck, Scott Cc: weirds@ietf.org Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London On 2014-06-10 11:41 AM, Andy Newton wrote: On Jun 4, 2014, at 1:20 PM, Hollenbeck, Scott > wrote: However, it would be worth expanding on this in the query doc by showing that /domains?name=3DXXXX returns a 404 if XXXX does not exist in the registry, but /domains?names=3DXXXX returns 400, since it has an invalid query parameter. Describing a subset of the possible error conditions will only lead to ques= tions about the errors we don't explicitly identify. I'd rather not do this= . I agree with Scott on this. The argument to avoid "describing a subset of the possible error conditions= " is contradicted by what is already in draft-ietf-weirds-using-http. Secti= on 5 contains several sections covering a subset of HTTP errors, including = 400 and 404. Without further guidelines, there will be a lot of inconsistencies between = implementations. In the last inter-op test there were a number of cases whe= re XXXX was an invalid name (such as example...com) or an invalid UTF-8 rep= resentation. Some believed that 400 should be returned, others interpreted = 404 as the proper error. I suggest a statement to the effect that if the error is related to an inva= lid value of the parameter, 404 should be returned; but if the error is syn= tax or semantic (such as an invalid parameter), then 400 is returned. If 400/404 are used consistently, this provides useful feedback to help dia= gnose the problem. 404 is due to the user input, whereas 400 is generally a= fault in the client implementation. [SAH] Then maybe this is an action for using-http, and not rdap-query. Scott --_000_831693C2CDA2E849A7D7A712B24E257F4941F398BRN1WNEXMBX01vc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

From: Ernie Dainow [mailto:edainow@afilias.info]
Sent: Friday, June 13, 2014 6:18 AM
To: Andy Newton; Hollenbeck, Scott
Cc: weirds@ietf.org
Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London=

 

 

On 2014-06-10 11:41 AM, Andy Newton wrote:

 

On Jun 4, 2014, at 1:20 PM, Hollenbeck, Scott <shollenbeck@verisign.com> = wrote:



However, it would be= worth expanding on this in the query doc by

showing
that
/domains?name=3DXXXX
returns a 404 if XXXX does not exist in the registry, but

/domains?names=3DXXXX
returns 400, since it has an invalid query parameter.


Describing a subset of the possible error conditions will only lead to ques= tions about the errors we don't explicitly identify. I'd rather not do this= .

 

I agree with Scott on this.

 


The argument to avoid "describing a subset of the possible error condi= tions" is contradicted by what is already in draft-ietf-weirds-using-h= ttp. Section 5 contains several sections covering a subset of HTTP errors, = including 400 and 404.
 
Without further guidelines, there will be a lot of inconsistencies between = implementations. In the last inter-op test there were a number of cases whe= re XXXX was an invalid name (such as example...com) or an invalid UTF-8 rep= resentation. Some believed that 400 should be returned, others interpreted 404 as the proper error.

I suggest a statement to the effect that if the error is related to an inva= lid value of the parameter, 404 should be returned; but if the error is syn= tax or semantic (such as an invalid parameter), then 400 is returned.

If 400/404 are used consistently, this provides useful feedback to help dia= gnose the problem. 404 is due to the user input, whereas 400 is generally a= fault in the client implementation.

[SAH] Then = maybe this is an action for using-http, and not rdap-query.

Scott<= /o:p>

--_000_831693C2CDA2E849A7D7A712B24E257F4941F398BRN1WNEXMBX01vc_-- From nobody Mon Jun 16 05:30:18 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A738F1A0004 for ; Mon, 16 Jun 2014 05:30:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.651 X-Spam-Level: X-Spam-Status: No, score=-0.651 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yH7LdCZ9aGP9 for ; Mon, 16 Jun 2014 05:30:16 -0700 (PDT) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC731A0002 for ; Mon, 16 Jun 2014 05:30:16 -0700 (PDT) Received: by smtp2.arin.net (Postfix, from userid 323) id 29A1021364C; Mon, 16 Jun 2014 08:30:16 -0400 (EDT) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp2.arin.net (Postfix) with ESMTP id 8A86A21362B; Mon, 16 Jun 2014 08:30:15 -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.342.3; Mon, 16 Jun 2014 08:30:09 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0347.000; Mon, 16 Jun 2014 08:30:09 -0400 From: Andy Newton To: Scott Hollenbeck Thread-Topic: [weirds] WEIRDS inactivity, and issues raised in London Thread-Index: AQHPa65h2C4aSNLkvUmB4sqh8fp0uJs9I46QgDHmhCeAAAsGEIAFFAWA Date: Mon, 16 Jun 2014 12:30:09 +0000 Message-ID: <8A3D6209-45F4-4E8F-A388-D26E67E669AE@arin.net> References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F44D3.3050209@afilias.info> <831693C2CDA2E849A7D7A712B24E257F49412C4F@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <1017AC76-A38F-45FC-A302-2684C1824309@arin.net> <539ACFBC.2000803@afilias.info> <831693C2CDA2E849A7D7A712B24E257F4941F398@BRN1WNEXMBX01.vcorp.ad.vrsn.com> In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4941F398@BRN1WNEXMBX01.vcorp.ad.vrsn.com> 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: multipart/alternative; boundary="_000_8A3D620945F44E8FA388D26E67E669AEarinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/ruDLgFtotxoAfbplKBxm2PJcgUo Cc: "weirds@ietf.org" Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 12:30:17 -0000 --_000_8A3D620945F44E8FA388D26E67E669AEarinnet_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable On Jun 13, 2014, at 7:58 AM, Hollenbeck, Scott > wrote: Then maybe this is an action for using-http, and not rdap-query. I=92m fine with that. But as the text in using-http regarding this issue ha= s been wordsmithed over and over again, I=92m gonna request a =93send text= =94 for any mods to that draft. -andy --_000_8A3D620945F44E8FA388D26E67E669AEarinnet_ Content-Type: text/html; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable
On Jun 13, 2014, at 7:58 AM, Hollenbeck, Scott <shollenbeck@verisign.com> wrote:

Then maybe this is an action for using-http, and not rdap-query.


I=92m fine with that. But as the text in using-http regarding this iss= ue has been wordsmithed over and over again, I=92m gonna request a =93send = text=94 for any mods to that draft.

-andy
--_000_8A3D620945F44E8FA388D26E67E669AEarinnet_-- From nobody Mon Jun 16 08:36:21 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91C001A0086 for ; Mon, 16 Jun 2014 08:36:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.229 X-Spam-Level: X-Spam-Status: No, score=-4.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s9gRfrAXPUcG for ; Mon, 16 Jun 2014 08:36:17 -0700 (PDT) Received: from outbound.afilias.info (outbound.afilias.info [66.199.183.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B04501A007E for ; Mon, 16 Jun 2014 08:36:17 -0700 (PDT) Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.72) (envelope-from ) id 1WwYxE-0003mk-6G for weirds@ietf.org; Mon, 16 Jun 2014 15:36:16 +0000 Received: from mail-la0-f41.google.com ([209.85.215.41]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1WwYxE-0007tX-5O for weirds@ietf.org; Mon, 16 Jun 2014 15:36:16 +0000 Received: by mail-la0-f41.google.com with SMTP id hz20so3157049lab.0 for ; Mon, 16 Jun 2014 08:36:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=PFPcEhWbzL9EEzULxmXOIa8LTeS2Qkp7ISsx9IOd6VY=; b=TcVg4bGkRRhVXlcBajmnmvUbUrpyiJ4ySHLOBSEmWvl7FEKD/fxwogCAX+MNE/49lt n+30ccap0F1vYt2tiJddf5aFwEe5xIrXth9FFzFF1EEhKsyqBhRx8yrUKrspMDvWFcD6 DG9mQz3hGUWhMF3uJ6KF9PeDdMuG100K9xiJzzHfTEiff0STsspxTY/4pRnNnJPb+cTA Qp5MVlmMe/6SN9oZmeS8soCJlnKQWAaBL8+3MNEsvlDNk5k0DA7JUuTtuWl8i3Eyp6Jh h0eLPCAN6EKdLVHrtd6GfuDhohBGaBXRrmSonswZZMrEtpmIT8sGmBI5hz0PEKsrtZdr MZKQ== X-Gm-Message-State: ALoCoQnlOgo8lTFiu+UxnSv/OgTxZMdYCgkjUcIztgiv10f3SJ0WC2HLajVD41j0ylj2lW8T+dX9y7vXckssFR6g5qIbI9RiA8VQR5qjND2PE+fYjSR4Rtk= X-Received: by 10.112.164.97 with SMTP id yp1mr2058360lbb.56.1402932970295; Mon, 16 Jun 2014 08:36:10 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.164.97 with SMTP id yp1mr2058352lbb.56.1402932970158; Mon, 16 Jun 2014 08:36:10 -0700 (PDT) Received: by 10.112.225.39 with HTTP; Mon, 16 Jun 2014 08:36:10 -0700 (PDT) In-Reply-To: <8A3D6209-45F4-4E8F-A388-D26E67E669AE@arin.net> References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F44D3.3050209@afilias.info> <831693C2CDA2E849A7D7A712B24E257F49412C4F@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <1017AC76-A38F-45FC-A302-2684C1824309@arin.net> <539ACFBC.2000803@afilias.info> <831693C2CDA2E849A7D7A712B24E257F4941F398@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <8A3D6209-45F4-4E8F-A388-D26E67E669AE@arin.net> Date: Mon, 16 Jun 2014 11:36:10 -0400 Message-ID: From: Ernie Dainow To: Andy Newton Content-Type: multipart/alternative; boundary=001a11c33c98549bd504fbf5c955 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/asM1BEhgR-hIXL6C-YepaS2Z7e8 Cc: "weirds@ietf.org" Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2014 15:36:19 -0000 --001a11c33c98549bd504fbf5c955 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Here is suggested wording for Section 5.4 containing one added paragraph. 5.4. Malformed Queries If a server receives a query which it cannot interpret as an RDAP query, it returns a 400 response code. Optionally, it MAY include additional information regarding this negative answer in the HTTP entity body. A 400 response code is returned to indicate a syntax or semantic error in the query, such as an invalid parameter. If the error is related to an invalid value of a parameter, such as an invalid DNS name, 404 is returned. -Ernie On Mon, Jun 16, 2014 at 8:30 AM, Andy Newton wrote: > > On Jun 13, 2014, at 7:58 AM, Hollenbeck, Scott > wrote: > > Then maybe this is an action for using-http, and not rdap-query. > > > > I=E2=80=99m fine with that. But as the text in using-http regarding this= issue > has been wordsmithed over and over again, I=E2=80=99m gonna request a =E2= =80=9Csend text=E2=80=9D > for any mods to that draft. > > -andy > --001a11c33c98549bd504fbf5c955 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Here is suggested wording for Section 5.4 containing one a= dded paragraph.

5.4. =C2=A0Malformed Queries
<= div>
If a server receives a query which it cannot interpret a= s an RDAP query, it returns a 400 response code. =C2=A0Optionally, it MAY i= nclude additional information regarding this negative answer in the HTTP en= tity body.=C2=A0
=C2=A0 =C2=A0
A 400 response code is returned to indicate a = syntax or semantic error in the query, such as an invalid parameter. =C2=A0= If the error is related to an invalid value of a parameter, such as an inva= lid DNS name, 404 is returned.

-Ernie


<= div class=3D"gmail_extra">

On Mon, Jun 16= , 2014 at 8:30 AM, Andy Newton <andy@arin.net> wrote:

On Jun 13, 2014, at 7:58 AM, Hollenbeck, Scott <shollenbeck@verisign.com>= wrote:

Then maybe this is an action for using-http, and not rdap-query.


I=E2=80=99m fine with that. But as the text in using-http regard= ing this issue has been wordsmithed over and over again, I=E2=80=99m gonna = request a =E2=80=9Csend text=E2=80=9D for any mods to that draft.

-andy

--001a11c33c98549bd504fbf5c955-- From nobody Mon Jun 16 19:30:41 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3100F1A0318 for ; Mon, 16 Jun 2014 19:30:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.131 X-Spam-Level: * X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CDmLjj0A1O7z for ; Mon, 16 Jun 2014 19:30:37 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 2DA891A0313 for ; Mon, 16 Jun 2014 19:30:36 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn Received: from unknown127.0.0.1 (HELO user-think) (127.0.0.1) by 127.0.0.1 with SMTP; Tue, 17 Jun 2014 10:30:33 +0800 Date: Tue, 17 Jun 2014 10:31:11 +0800 From: "Linlin Zhou" To: weirds X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7, 2, 5, 140[cn] Mime-Version: 1.0 Message-ID: <2014061710311065468713@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart354161117880_=----" Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/F9XVkV3MxKMb9XQyrONvWoEO0EE Subject: [weirds] reverse domain example in response draft X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 02:30:39 -0000 This is a multi-part message in MIME format. ------=_001_NextPart354161117880_=---- Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: base64 SW4gc2VjdGlvbiA2IG9mIHJlc3BvbnNlIGRyYWZ0LCAgSSB0aGluayB0aGVyZSdzIGEgbml0LiBU aGUgbGRoTmFtZSBpcyBhIGlwdjQgcmV2ZXJzZSBkb21haW4gd2hpbGUgdGhlIG5ldHdvcmsgb2Jq ZWN0IHNob3dzIGlwdjYgc3RhcnRBZGRyZXNzIGFuZCBlbmRBZGRyZXNzLg0KDQp7CiAgICAgImhh bmRsZSIgOiAiWFhYWCIsCiAgICAgImxkaE5hbWUiIDogIjE5Mi5pbi1hZGRyLmFycGEiLCAgICAg Li4uICAgICAibmV0d29yayIgOiAgICAgewogICAgICAgImhhbmRsZSIgOiAiWFhYWC1SSVIiLAog ICAgICAgInN0YXJ0QWRkcmVzcyIgOiAiMjAwMTpkYjg6OjAiLAogICAgICAgImVuZEFkZHJlc3Mi IDogIjIwMDE6ZGI4OjowOkZGRkY6RkZGRjpGRkZGOkZGRkY6RkZGRiIsCiAgICAgICAiaXBWZXJz aW9uIiA6ICJ2NiIsCiAgICAgICAibmFtZSI6ICJORVQtUlRSLTEiLAogICAgICAgInR5cGUiIDog IkRJUkVDVCBBTExPQ0FUSU9OIiwKICAgICAgICJjb3VudHJ5IiA6ICJBVSIsCiAgICAgICAicGFy ZW50SGFuZGxlIiA6ICJZWVlZLVJJUiIsCiAgICAgICAic3RhdHVzIiA6IFsgImFsbG9jYXRlZCIg XQogICAgIH0KIH0NClJlZ2FyZHMsDQoNCg0KTGlubGluIFpob3UNCg== ------=_001_NextPart354161117880_=---- Content-Type: text/html; charset="GB2312" Content-Transfer-Encoding: quoted-printable =0A
In section 6 of response draft= ,  I think there's a nit. The ldhName is a ipv4 reverse domain while = the network object shows ipv6 startAddress and endAddress.

<= /div>
{=0A=
     "handle" : "XXXX",=0A     "ldhName" : "192.in-addr.arpa",
   =
  ...
     "networ=
k" :
     {=0A       "handle" : "XXXX-RIR",=0A       "startAddress" : "2001:=
db8::0",=0A       "endAddress" : "2001:db8::0:FFFF:FFFF:FFFF:FFFF:FFFF",=
=0A       "ipVersion" : "v6",=0A       "name": "NET-RTR-1",=0A       "type=
" : "DIRECT ALLOCATION",=0A       "country" : "AU",=0A       "parentHandle=
" : "YYYY-RIR",=0A       "status" : [ "allocated" ]=0A     }=0A }

Regards,
=0A
Linlin Zhou
=0A ------=_001_NextPart354161117880_=------ From nobody Tue Jun 17 05:13:33 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE8AB1A035B for ; Tue, 17 Jun 2014 05:13:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.569 X-Spam-Level: X-Spam-Status: No, score=-1.569 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o1-m5tnK4GDw for ; Tue, 17 Jun 2014 05:13:27 -0700 (PDT) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 0248A1A035D for ; Tue, 17 Jun 2014 05:13:26 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id A0A191651EB; Tue, 17 Jun 2014 08:13:26 -0400 (EDT) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id 43A721651E4; Tue, 17 Jun 2014 08:13:22 -0400 (EDT) Received: from CHACAS02.corp.arin.net (10.1.30.108) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.342.3; Tue, 17 Jun 2014 08:13:22 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS02.corp.arin.net ([fe80::54ae:f9de:2f8b:1072%12]) with mapi id 14.03.0181.006; Tue, 17 Jun 2014 08:13:21 -0400 From: Andy Newton To: Linlin Zhou Thread-Topic: [weirds] reverse domain example in response draft Thread-Index: AQHPidQjXcR5bKraAEaJn0AgLXCUI5t1enMA Date: Tue, 17 Jun 2014 12:13:20 +0000 Message-ID: <0FD95E98-8B17-4465-A359-0556F157F545@arin.net> References: <2014061710311065468713@cnnic.cn> In-Reply-To: <2014061710311065468713@cnnic.cn> 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: multipart/alternative; boundary="_000_0FD95E988B174465A3590556F157F545arinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/16VxpWH66M8ATr2ad2p_739thQw Cc: "weirds@ietf.org" Subject: Re: [weirds] reverse domain example in response draft X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 12:13:32 -0000 --_000_0FD95E988B174465A3590556F157F545arinnet_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 WXVwLCBkZWZpbml0ZWx5IG5vdCBhIGdvb2QgZXhhbXBsZS4gVGhhbmtzIGZvciBwb2ludGluZyBp dCBvdXQuDQoNCi1hbmR5DQoNCk9uIEp1biAxNiwgMjAxNCwgYXQgMTE6MzEgUE0sIExpbmxpbiBa aG91IDx6aG91bGlubGluQGNubmljLmNuPG1haWx0bzp6aG91bGlubGluQGNubmljLmNuPj4gd3Jv dGU6DQoNCkluIHNlY3Rpb24gNiBvZiByZXNwb25zZSBkcmFmdCwgIEkgdGhpbmsgdGhlcmUncyBh IG5pdC4gVGhlIGxkaE5hbWUgaXMgYSBpcHY0IHJldmVyc2UgZG9tYWluIHdoaWxlIHRoZSBuZXR3 b3JrIG9iamVjdCBzaG93cyBpcHY2IHN0YXJ0QWRkcmVzcyBhbmQgZW5kQWRkcmVzcy4NCg0KDQp7 DQogICAgICJoYW5kbGUiIDogIlhYWFgiLA0KICAgICAibGRoTmFtZSIgOiAiMTkyLmluLWFkZHIu YXJwYSIsDQoNCiAgICAgLi4uDQoNCiAgICAgIm5ldHdvcmsiIDoNCg0KICAgICB7DQogICAgICAg ImhhbmRsZSIgOiAiWFhYWC1SSVIiLA0KICAgICAgICJzdGFydEFkZHJlc3MiIDogIjIwMDE6ZGI4 OjowIiwNCiAgICAgICAiZW5kQWRkcmVzcyIgOiAiMjAwMTpkYjg6OjA6RkZGRjpGRkZGOkZGRkY6 RkZGRjpGRkZGIiwNCiAgICAgICAiaXBWZXJzaW9uIiA6ICJ2NiIsDQogICAgICAgIm5hbWUiOiAi TkVULVJUUi0xIiwNCiAgICAgICAidHlwZSIgOiAiRElSRUNUIEFMTE9DQVRJT04iLA0KICAgICAg ICJjb3VudHJ5IiA6ICJBVSIsDQogICAgICAgInBhcmVudEhhbmRsZSIgOiAiWVlZWS1SSVIiLA0K ICAgICAgICJzdGF0dXMiIDogWyAiYWxsb2NhdGVkIiBdDQogICAgIH0NCiB9DQoNCg0KUmVnYXJk cywNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkxpbmxpbiBaaG91DQpfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Kd2VpcmRzIG1haWxp bmcgbGlzdA0Kd2VpcmRzQGlldGYub3JnPG1haWx0bzp3ZWlyZHNAaWV0Zi5vcmc+DQpodHRwczov L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3dlaXJkcw0KDQo= --_000_0FD95E988B174465A3590556F157F545arinnet_ Content-Type: text/html; charset="gb2312" Content-ID: Content-Transfer-Encoding: quoted-printable
Yup, definitely not a good example. Thanks for pointing it out.

-andy

On Jun 16, 2014, at 11:31 PM, Linlin Zhou <zhoulinlin@cnnic.cn> wrote:

In section 6 of response draft,  I think there's a n= it. The ldhName is a ipv4 reverse domain while the network object shows ipv= 6 startAddress and endAddress.

{
     "handle" : "XXXX",
     "ldhName" : "192.in-addr.arpa",
  &nb=
sp;  ...
  &nb=
sp; =
 "network" :
     {
       "handle" : "XXXX-RIR",
       "startAddress" : "2001:db8::0",
       "endAddress" : "2001:db8::0:FFFF:FFFF:FFFF:FFFF:FFFF&=
quot;,
       "ipVersion" : "v6",
       "name": "NET-RTR-1",
       "type" : "DIRECT ALLOCATION",
       "country" : "AU",
       "parentHandle" : "YYYY-RIR",
       "status" : [ "allocated" ]
     }
 }

Regards,
Linlin = Zhou
_______________________________________________
weirds mailing list
weirds@ietf.org
https://www.ietf.o= rg/mailman/listinfo/weirds

--_000_0FD95E988B174465A3590556F157F545arinnet_-- From nobody Sun Jun 22 16:03:09 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82B601A03FB for ; Sun, 22 Jun 2014 16:03:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.258 X-Spam-Level: X-Spam-Status: No, score=0.258 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EMiy34cmddzd for ; Sun, 22 Jun 2014 16:03:05 -0700 (PDT) Received: from ao-mailgw.apnic.net (ao-mailgw.apnic.net [IPv6:2001:dd8:8:701::25]) by ietfa.amsl.com (Postfix) with SMTP id A5CD71A03C3 for ; Sun, 22 Jun 2014 16:03:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=c3po; h=received:received:received:date:from:to:cc:subject:message-id: mail-followup-to:references:mime-version:content-type:content-disposition: in-reply-to:user-agent:return-path; bh=qwO5js4mu1NVFnUEgo+/izbLSPHIKQVKX+jdgo5gaKc=; b=3kG1UrcWokF7X3E/Dmf2/GACVZ304KIE7JSPZYoKCW24E4+6kC6Me99lseyFdlDsvjZtmp3WebOZx CN8St+8BqEv2+t8Ga46Cxmd5rT0VD5ASV7EZS1uB7auHD+k+nsfrv8COvBQN9ZDiyZrq0DxhF2EsMl YSOrU1tazYmWsF2g= Received: from NXMDA1.org.apnic.net (unknown [203.119.101.249]) by ao-mailgw.apnic.net (Halon Mail Gateway) with ESMTP; Mon, 23 Jun 2014 09:03:00 +1000 (EST) Received: from main (203.119.101.249) by NXMDA1.org.apnic.net (203.119.107.11) with Microsoft SMTP Server (TLS) id 14.1.218.12; Mon, 23 Jun 2014 09:03:00 +1000 Received: from tomh by main with local (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1Wyqmq-000DpC-2N; Mon, 23 Jun 2014 09:03:00 +1000 Date: Mon, 23 Jun 2014 09:03:00 +1000 From: Tom Harrison To: Ernie Dainow Message-ID: <20140622230300.GA44375@main> Mail-Followup-To: Ernie Dainow , weirds@ietf.org References: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <538F44D3.3050209@afilias.info> <831693C2CDA2E849A7D7A712B24E257F49412C4F@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <1017AC76-A38F-45FC-A302-2684C1824309@arin.net> <539ACFBC.2000803@afilias.info> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <539ACFBC.2000803@afilias.info> User-Agent: Mutt/1.5.23 (2014-03-12) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/ux5RUKEQ30rqfhXfds6rStCWlfY Cc: weirds@ietf.org Subject: Re: [weirds] WEIRDS inactivity, and issues raised in London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2014 23:03:07 -0000 On Fri, Jun 13, 2014 at 06:17:32AM -0400, Ernie Dainow wrote: > The argument to avoid "describing a subset of the possible error conditions" > is contradicted by what is already in draft-ietf-weirds-using-http. Section > 5 contains several sections covering a subset of HTTP errors, including 400 > and 404. > > Without further guidelines, there will be a lot of inconsistencies between > implementations. In the last inter-op test there were a number of cases > where XXXX was an invalid name (such as example...com) or an invalid UTF-8 > representation. Some believed that 400 should be returned, others > interpreted 404 as the proper error. > > I suggest a statement to the effect that if the error is related to an > invalid value of the parameter, 404 should be returned; but if the error is > syntax or semantic (such as an invalid parameter), then 400 is returned. > > If 400/404 are used consistently, this provides useful feedback to help > diagnose the problem. 404 is due to the user input, whereas 400 is generally > a fault in the client implementation. I think using 400 for all client errors is the better approach. Most servers will return a description of the error in the body of the response (as per json-response), so the interactive use case is covered regardless of the error code, since the client program can display that error description to the user. However, in the case where the access is scripted/automated, or any other situation where the only thing from the response that can be depended on is the status code, it's more useful for 404 to be limited to the "valid query but there's no record" scenario. For example, a user might have a scheduled script that fetches a series of domain names, some being non-IDNs and some being IDNs. If the script is not encoding the IDNs properly, then all of the IDN requests would yield "not found", which would be quite a different meaning in this case from any "not found" returned for a non-IDN. More insidious would be a change in how the server processes queries on the server side, such that a previously-valid request, returning a "not found 404" or a successful response, starts returning a "client error 404". -Tom From nobody Sun Jun 22 22:21:59 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB81D1B2991 for ; Sun, 22 Jun 2014 22:21:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.599 X-Spam-Level: X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l_xmJd-AVp1T for ; Sun, 22 Jun 2014 22:21:56 -0700 (PDT) Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1758B1B286A for ; Sun, 22 Jun 2014 22:21:55 -0700 (PDT) Received: by mail-we0-f169.google.com with SMTP id t60so6346953wes.0 for ; Sun, 22 Jun 2014 22:21:54 -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=GSP65gWQ9i9idxGHaorQBhKWflX6Gm/r1tojvVLz3O8=; b=GOUdLlfPvQzAloZytwn4F84KE6qt+640SZdaY2E1MWVOVGadJdufCTl1XDb4oPJGtO jNo1pm0BNq1uUlIqeU+2LGLll3IHGFWsgvY8K31zVJ1NT0yU0X572xItdJvtf1nEbsVb GyEeMATDeEUCTNyNsYlCdtbc3B+NLuQcyxrwr3l5Mdx6tyTv8bULEs0ehpHNL9AN8YI6 JxAftT7qxG/+AqEOdCZApEtroURE7hZVTvfBxG4oO7+reJWcEqVtet8Gnu+5iReK2bhA r8JgiLD/5/4D+I4OOQLehy/dfK89SlystPyAl+LegSbIWnpmxhZInyB/lTQp96YWMJPV wO0A== MIME-Version: 1.0 X-Received: by 10.180.75.212 with SMTP id e20mr22767606wiw.5.1403500914684; Sun, 22 Jun 2014 22:21:54 -0700 (PDT) Received: by 10.180.19.73 with HTTP; Sun, 22 Jun 2014 22:21:54 -0700 (PDT) Date: Sun, 22 Jun 2014 22:21:54 -0700 Message-ID: From: "Murray S. Kucherawy" To: "weirds@ietf.org" Content-Type: multipart/alternative; boundary=f46d043890a57638c804fc7a05a7 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/d0_Kk0gOr5ukvkND-UN3BXdxYIg Subject: [weirds] Draft cutoff coming up X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 05:21:57 -0000 --f46d043890a57638c804fc7a05a7 Content-Type: text/plain; charset=UTF-8 Just a friendly reminder: If you have any document edits made but not posted, or plan to make some, the cutoff for document submission prior to the Toronto meeting is July 4th. Submit early, submit often. -MSK --f46d043890a57638c804fc7a05a7 Content-Type: text/html; charset=UTF-8
Just a friendly reminder:

If you have any document edits made but not posted, or plan to make some, the cutoff for document submission prior to the Toronto meeting is July 4th.

Submit early, submit often.

-MSK
--f46d043890a57638c804fc7a05a7-- From nobody Mon Jun 23 05:43:32 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 486691B2935; Mon, 23 Jun 2014 05:43:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tZBm5sSeyPtE; Mon, 23 Jun 2014 05:43:26 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DB3D61B28FE; Mon, 23 Jun 2014 05:43:26 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.5.0.p3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140623124326.21967.4986.idtracker@ietfa.amsl.com> Date: Mon, 23 Jun 2014 05:43:26 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/-rRsFZLCjuDQxOuSM3O2kVrU6kA Cc: weirds@ietf.org Subject: [weirds] I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 12:43:28 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web Extensible Internet Registration Data Service Working Group of the IETF. Title : Finding the Authoritative Registration Data (RDAP) Service Author : Marc Blanchet Filename : draft-ietf-weirds-bootstrap-02.txt Pages : 11 Date : 2014-06-23 Abstract: This document specifies a method to find which Registration Data Access Protocol (RDAP) server is authoritative to answer queries for a requested scope, such as domain names, IP addresses or Autonomous System numbers. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-weirds-bootstrap/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-weirds-bootstrap-02 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-weirds-bootstrap-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Jun 23 05:59:24 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA7811B2939 for ; Mon, 23 Jun 2014 05:59:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CROepF2LbcDz for ; Mon, 23 Jun 2014 05:59:17 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2DD771B2AB6 for ; Mon, 23 Jun 2014 05:59:17 -0700 (PDT) Received: from h194.viagenie.ca (h194.viagenie.ca [206.123.31.194]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 61FD646A68 for ; Mon, 23 Jun 2014 08:59:16 -0400 (EDT) From: Marc Blanchet Content-Type: multipart/alternative; boundary="Apple-Mail=_FBE416AC-60DC-496B-B5B8-AB32219ED2DA" Date: Mon, 23 Jun 2014 13:59:11 +0100 References: <20140623124326.21967.4986.idtracker@ietfa.amsl.com> To: weirds@ietf.org Message-Id: Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) X-Mailer: Apple Mail (2.1878.2) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/Z4amuEHqEKHopcSVt7K6qxiPJ_w Subject: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 12:59:20 -0000 --Apple-Mail=_FBE416AC-60DC-496B-B5B8-AB32219ED2DA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hello, here is a new version of the bootstrap document. This is a major = rewrite based on the various concensus points during last meeting and = followup, such as: JSON, using templates, IANA section rewrite, .... = After some mailing list discussions and discussions with rdap-query = authors, this draft hopefully covers the direction of the wg. One can look at the diffs, but I'm not sure it is that valuable given = major rewrite. Regards, Marc. D=E9but du message r=E9exp=E9di=E9 : > De: internet-drafts@ietf.org > Objet: I-D Action: draft-ietf-weirds-bootstrap-02.txt > Date: 23 juin 2014 13:43:26 UTC+1 > =C0: i-d-announce@ietf.org > Cc: weirds@ietf.org > R=E9pondre =E0: internet-drafts@ietf.org >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Web Extensible Internet Registration = Data Service Working Group of the IETF. >=20 > Title : Finding the Authoritative Registration Data = (RDAP) Service > Author : Marc Blanchet > Filename : draft-ietf-weirds-bootstrap-02.txt > Pages : 11 > Date : 2014-06-23 >=20 > Abstract: > This document specifies a method to find which Registration Data > Access Protocol (RDAP) server is authoritative to answer queries for > a requested scope, such as domain names, IP addresses or Autonomous > System numbers. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-weirds-bootstrap/ >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-weirds-bootstrap-02 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-weirds-bootstrap-02 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt --Apple-Mail=_FBE416AC-60DC-496B-B5B8-AB32219ED2DA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Hello,
 here is a new version of the = bootstrap document. This is a major rewrite based on the various = concensus points during last meeting and followup, such as: JSON, using = templates, IANA section rewrite, .... After some mailing list = discussions and discussions with rdap-query authors, this draft = hopefully covers the direction of the wg.
 One can look = at the diffs, but I'm not sure it is that valuable given major = rewrite.

Regards, = Marc.

D=E9but du message r=E9exp=E9di=E9 = :

Objet: = I-D Action: = draft-ietf-weirds-bootstrap-02.txt
Date: 23 juin 2014 13:43:26 = UTC+1
R=E9pondre =E0: internet-drafts@ietf.org
<= /span>


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

       Title =           : Finding = the Authoritative Registration Data (RDAP) Service
=        Author =          : Marc = Blanchet
= Filename        : = draft-ietf-weirds-bootstrap-02.txt
Pages =           : = 11
= Date =            : = 2014-06-23

Abstract:
  This document specifies a = method to find which Registration Data
  Access Protocol = (RDAP) server is authoritative to answer queries for
  a = requested scope, such as domain names, IP addresses or Autonomous
=   System numbers.


The IETF datatracker status page = for this draft is:
htt= ps://datatracker.ietf.org/doc/draft-ietf-weirds-bootstrap/

Ther= e's also a htmlized version available = at:
http://tools.ietf.org/html/draft-ietf-weirds-bootstrap-02

A = diff from the previous version is available = at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-weirds-bootstrap-02

Please note that it may take a couple of minutes from the time = of submission
until the htmlized version and diff are available at = tools.ietf.org.

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

________________________= _______________________
I-D-Announce mailing = list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d= -announce
Internet-Draft directories: = http://www.ietf.org/shadow.html
or = ftp://ftp.ietf.org/ietf/1shadow-sites.txt

=
= --Apple-Mail=_FBE416AC-60DC-496B-B5B8-AB32219ED2DA-- From nobody Mon Jun 23 17:51:24 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B50A11A04FA for ; Mon, 23 Jun 2014 17:51:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.442 X-Spam-Level: X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UUvwR00-xQzr for ; Mon, 23 Jun 2014 17:51:19 -0700 (PDT) Received: from ao-mailgw.apnic.net (ao-mailgw.apnic.net [IPv6:2001:dd8:8:701::25]) by ietfa.amsl.com (Postfix) with SMTP id DFD361A04E7 for ; Mon, 23 Jun 2014 17:51:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=c3po; h=received:received:received:date:from:to:cc:subject:message-id: mail-followup-to:references:mime-version:content-type:content-disposition: in-reply-to:user-agent:return-path; bh=k8v5udeVOfVxb+nhJQJe8NIhthXQJf9OGu/421JDJPE=; b=mATN5xbMvO2Pdaxf5rL+yqTkB37wdCnMaLLwwp/ul+btflsCplxzlowXboCoPauwX51Gos1d1FLuk BtlWfEbkxL1F2KDoh5pe2We+AueXAbgtStfdPPo3YVVN8LiaglFpK/4oFJq3KkuuVhsqWsMr0cOAVX PuArhbrlWmj3hyCg= Received: from NXMDA1.org.apnic.net (unknown [203.119.101.249]) by ao-mailgw.apnic.net (Halon Mail Gateway) with ESMTP; Tue, 24 Jun 2014 10:51:14 +1000 (EST) Received: from main (203.119.101.249) by NXMDA1.org.apnic.net (203.119.107.11) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 24 Jun 2014 10:51:14 +1000 Received: from tomh by main with local (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1WzEx9-0001Wv-BX; Tue, 24 Jun 2014 10:51:15 +1000 Date: Tue, 24 Jun 2014 10:51:15 +1000 From: Tom Harrison To: Marc Blanchet Message-ID: <20140624005115.GA3669@main> Mail-Followup-To: Marc Blanchet , weirds@ietf.org References: <20140623124326.21967.4986.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/90757KaSksvJQuXL5CSxdaNR6fw Cc: weirds@ietf.org Subject: Re: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 00:51:21 -0000 On Mon, Jun 23, 2014 at 01:59:11PM +0100, Marc Blanchet wrote: > Hello, > here is a new version of the bootstrap document. This is a major rewrite based on the various concensus points during last meeting and followup, such as: JSON, using templates, IANA section rewrite, .... After some mailing list discussions and discussions with rdap-query authors, this draft hopefully covers the direction of the wg. > One can look at the diffs, but I'm not sure it is that valuable given major rewrite. > "services": [ > ["entry1", "entry2", "entry3"]: { > "template": "{proto}://registry.example.com/myrdap/{resource}", > "proto": [ https ], > }, > ["entry4"]: { > "template": "{proto}://example.org/{resource}", > }, > ], This is using arrays, instead of strings, as keys. Given that "services" is not an object, but an array, is the structure meant to be like this: "services": [ [ ["entry1", "entry2", "entry3"], { "template": "{proto}://registry.example.com/myrdap/{resource}", "proto": [ "https" ] } ], [ ["entry4"], { "template": "{proto}://example.org/{resource}" } ] ] instead? > For example, a domain RDAP query for a.b.example.com matches the com > entry in one of the arrays of the registry. Following the example > above, the base RDAP URL for this query is > "https://registry.example.com/myrdap/". The {resource} specified in > [I-D.ietf-weirds-rdap-query] is then appended to the base URL to > complete the query. The complete query is then > "https://registry.example.com/myrdap/domain/a.b.example.com". This > example is not normative. This limits implementations to path-based lookup, since the object type and the query value don't have separate variables. This isn't in keeping with draft-ietf-appsawg-uri-get-off-my-lawn-05 [2.3], since an implementation might prefer to use query processing instead. Should there be text in the document explaining why this is OK in this case? -Tom From nobody Mon Jun 23 18:35:14 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 002081A0547 for ; Mon, 23 Jun 2014 18:35:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.856 X-Spam-Level: * X-Spam-Status: No, score=1.856 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XYhZH7LZ8_TW for ; Mon, 23 Jun 2014 18:35:11 -0700 (PDT) Received: from off-send01.tyo.jprs.co.jp (off-send01.tyo.jprs.co.jp [IPv6:2001:df0:8:17::10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 740951A053B for ; Mon, 23 Jun 2014 18:35:11 -0700 (PDT) Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send01.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id s5O1ZAKQ002543 for ; Tue, 24 Jun 2014 10:35:10 +0900 X-AuditID: ac120820-b7f638e000000e09-40-53a8d5cdfcec Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id A8.B1.03593.DC5D8A35; Tue, 24 Jun 2014 10:35:09 +0900 (JST) Date: Tue, 24 Jun 2014 10:34:16 +0900 (JST) Message-Id: <20140624.103416.77335965.kambe@jprs.co.jp> To: weirds@ietf.org From: Naoki Kambe In-Reply-To: <20140624005115.GA3669@main> References: <20140623124326.21967.4986.idtracker@ietfa.amsl.com> <20140624005115.GA3669@main> Organization: Japan Registry Services Co., Ltd. X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOIsWRmVeSWpSXmKPExsWyRoiFT/fs1RXBBq+vW1jM7zrO4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujAunywoOclfcWHiDrYHxDkcXIyeHhICJxK6d59khbDGJC/fW s4HYQgInGSVa9piB2CwC2hJH3n5kArF5Bcwlbm95BlYvIiAssfjlOxYQW1jAU+L7yV9gcTYB FYll9zaD1XMKaEqsa9sONXMKo8TJ7+FdjBwc/AL6ElObUiDW2kk0/QUZwwE0XlDi7w5hkDCz gJZEz4zH7BC2vMT2t3OYJzDyz0KomoWkahaSqgWMzKsYZfLT0nSLU/NSinPTDQz1Sirz9bIK ior1kkH0JkZwuHEo7GCcccrgEKMAB6MSDy9H2IpgIdbEsuLK3EOMkhxMSqK8/84DhfiS8lMq MxKLM+KLSnNSiw8xSnAwK4nwBm4AyvGmJFZWpRblw6SkOViUxHmZjXuDhQTSE0tSs1NTC1KL YLIyHBxKEryhV4AaBYtS01Mr0jJzShDSTBycIMN5gIZ3gtTwFhck5hZnpkPkTzFKSonz5oAk BEASGaV5cL2vGMWBXhDmnQSS5QGmDriuV0ADmYAGstctAxlYkoiQkmpgbFZMf5WxsUBQ9Yh+ Zhi/qUmaeaHUvcT0i94bNO0nBT7mlkg0//i7/vjyfd+6v5w9otz+49q5337n3RLPriw5e/iR fPq315ObXC9PkjhSv7dYZ1qELf/NzaoMnWJ20xvWt3+8XPPGW7+3JuExu1ZjgvkPwQU3H687 nq1cp3XX/LXDfq/giKi3SizFGYmGWsxFxYkAH1H19NoCAAA= Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/PFsR9dtiSWEPq2HUIb1dKAhuplQ Subject: Re: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 01:35:13 -0000 Hello, Here are my comments related to the JSON syntax. From: Tom Harrison Date: Tue, 24 Jun 2014 10:51:15 +1000 > > "services": [ > > ["entry1", "entry2", "entry3"]: { > > "template": "{proto}://registry.example.com/myrdap/{resource}", > > "proto": [ https ], > > }, > > ["entry4"]: { > > "template": "{proto}://example.org/{resource}", > > }, > > ], > > This is using arrays, instead of strings, as keys. Given that > "services" is not an object, but an array, is the structure meant to > be like this: > > "services": [ > [ ["entry1", "entry2", "entry3"], > { "template": "{proto}://registry.example.com/myrdap/{resource}", > "proto": [ "https" ] } ], > [ ["entry4"], > { "template": "{proto}://example.org/{resource}" } ] > ] Also I've found some errors by using JSONLint . I've directly copied and pasted the examples from the draft. Please check this. I think a JSON object should always start with '{' and end with '}'. The examples on the draft seems to start with the string "rdap.bootstrap". And I'm not sure that an array-type key like the following can be allowed to be used in JSON: "services": [ | ["1.0.0.0/8", "192.0.0.0/8"]: { "template": "https://rir1.example.com/myrdap/{resource}", I think some of RDAP clients might fail to parse such examples. Regards, Naoki Kambe From nobody Mon Jun 23 19:16:45 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 497871B27C5 for ; Mon, 23 Jun 2014 19:16:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.563 X-Spam-Level: * X-Spam-Status: No, score=1.563 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3F6sWiBDRqsz for ; Mon, 23 Jun 2014 19:16:41 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA0BA1A0515 for ; Mon, 23 Jun 2014 19:16:40 -0700 (PDT) Received: (qmail 52798 invoked from network); 24 Jun 2014 02:16:39 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 24 Jun 2014 02:16:39 -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; s=2698.53a8df87.k1406; i=johnl@user.iecc.com; bh=hVNA5CR+pjQIrS4uW+oqWlngjtwC3i1noMVzQRYp40E=; b=n+/RrDnkElOXtr+9nbz/vbodoaqEe21xs5ywZLu3paucxct8c/A9bujDvVKg3QjkJEKy6RHBG55XWy1uFoQfxswCsrxCpZUC6/+DmZWSlJN7VTDs+Dc0Eweo6+AzARt8p7lhu+QIa+yfz7IgnX/DNAykrkNJ/+LSLnUy6155WnHPPIIxHsFF+IBovQeAW5PgoqOpXtGqeRRau+fzE6Pocvs0Ogi/ks2qvNXTxi2HfB+VeTkPNL0oy+XPvSO57nks 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; s=2698.53a8df87.k1406; olt=johnl@user.iecc.com; bh=hVNA5CR+pjQIrS4uW+oqWlngjtwC3i1noMVzQRYp40E=; b=BbUq1j4bBuCjaIXZToMHnyCkAsnacPAQ1GsSuHNLxKgmtX9zu3lVIuvBc/LvBpeu/u9ZvVBIjXExMCA9dliCUf/VVMlUqPpgvXA0b1ty9+on+EB1nFP962l7kr42GmnfwK+baiLN3ITVWI11GnDTsu38lNXrUZXnJAwQXqoyrQkdcyikxiEp1ghcQA/W7wzqPgv5uuWgrPY2EQdvr0dy9nlbOgtHbBAnOqhP12GN+5OdFRSEoTNBhpFBgn58Nt6F Date: 24 Jun 2014 02:16:17 -0000 Message-ID: <20140624021617.9879.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/y3rX8xC28_4Hz7Ksxto6eOpW2N0 Subject: Re: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 02:16:42 -0000 It's closer, but of course I have some suggestions to simplify and improve it. I note that the only two macros are {proto} and {resource}. I propose getting rid of both of them, for different reasons. The problem with "proto" is that it doesn't do what it needs to do, unless the only possible protos are http and https on default ports. The "resource" as currently specified only makes sense at the end of the template, so you might as well leave it out. As others have noted, the tags in objects can only be strings, not arrays, so make the list of tags and templates an array. Change the template to remove the proto, and instead have an array of URL prefixes. Since the templates are now the only thing in the object, they doesn't need to be wrapped in an object: "domain": [ [ ["wtf"], [ "https://example.net/rdapwtf/", "http://example.net:8080/rdapwtf/", "ftp://rdap@example.net/pub/file/rdapwtf/" ] ], [ ["net", "com"], [ "https://registry.example.com/myrdap/" ] ] ] For ASNs, it's just cruel to store the numbers as strings. Make them either a single number or a two-element array for a range: "asn": [ [ [2045, [20116,20117]], [ "https://rir2.example.com/myrdap/" ] ], [ [[10000,12000], [65900,66000]], [ "https://example.org/", "http://example.org/" ] ], [ [[65512,65534]], [ "http://example.net/rdaprir2/", "https://example.net/rdaprir2/" ] ] ] I understand that the point of making the key-like bit an array is to make the bootstrap smaller for the relatively common case that a single provider handles multiple keys, but it's not obvious to me that the added complexity is worth it, compared to having one name-like thing (domain name, CIDR, or ASN range) and a template, and just expand out the duplicates. I concur with the note that providing prefixes rather than full templates may make the URL lawn police unhappy, but we seem to have a clear consensus that the syntax in rdap-query meets the needs of any plausible RDAP server. R's, John From nobody Tue Jun 24 07:36:01 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E67391B2AB8 for ; Tue, 24 Jun 2014 07:35:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RtKVHuUfJIfD for ; Tue, 24 Jun 2014 07:35:49 -0700 (PDT) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 4FF511B2AAF for ; Tue, 24 Jun 2014 07:35:49 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id 0144416512D; Tue, 24 Jun 2014 10:35:48 -0400 (EDT) Received: from chaedge02.corp.arin.net (chaedge02.corp.arin.net [192.149.252.119]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id 5695B165126; Tue, 24 Jun 2014 10:35:48 -0400 (EDT) Received: from CHACAS01.corp.arin.net (10.1.30.107) by chaedge02.corp.arin.net (192.149.252.119) with Microsoft SMTP Server (TLS) id 14.3.181.6; Tue, 24 Jun 2014 10:35:58 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS01.corp.arin.net ([fe80::a98b:1e52:e85a:5979%13]) with mapi id 14.03.0181.006; Tue, 24 Jun 2014 10:35:46 -0400 From: Andy Newton To: Tom Harrison Thread-Topic: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt Thread-Index: AQHPjuL3knlBlwI8MEmTJhNqGrMjg5t/shWAgADmXgA= Date: Tue, 24 Jun 2014 14:35:46 +0000 Message-ID: References: <20140623124326.21967.4986.idtracker@ietfa.amsl.com> <20140624005115.GA3669@main> In-Reply-To: <20140624005115.GA3669@main> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.0.64] Content-Type: text/plain; charset="Windows-1252" Content-ID: <58E0F6A4D3F1824D9D3653FCFF41D47E@corp.arin.net> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/HwlGOkp1yZTUwKVFpz6BWuVqmic Cc: "weirds@ietf.org" Subject: Re: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 14:35:53 -0000 On Jun 23, 2014, at 8:51 PM, Tom Harrison wrote: >> For example, a domain RDAP query for a.b.example.com matches the com >> entry in one of the arrays of the registry. Following the example >> above, the base RDAP URL for this query is >> "https://registry.example.com/myrdap/". The {resource} specified in >> [I-D.ietf-weirds-rdap-query] is then appended to the base URL to >> complete the query. The complete query is then >> "https://registry.example.com/myrdap/domain/a.b.example.com". This >> example is not normative. >=20 > This limits implementations to path-based lookup, since the object > type and the query value don't have separate variables. This isn't in > keeping with draft-ietf-appsawg-uri-get-off-my-lawn-05 [2.3], since an > implementation might prefer to use query processing instead. Should > there be text in the document explaining why this is OK in this case? Perhaps the draft should say the template is =93https://registry.example.co= m/myrdap/{resource}=94 and that {resource} is substituted for a.b.example.c= om. But I think what is being proposed does allow for query use instead of path= use, and the object type is implicit in the bootstrap registry type. For d= omains, the DNR could submit {proto}://example.com/blahblah?domain=3D{resou= rce} just as easily as {proto}://example.com/blahblah/{resource}. BTW, if we are to stick with the proto array, we should really rename it. I= n URI/URL speak, it is =93scheme=94 not protocol. -andy= From nobody Tue Jun 24 07:47:53 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 847BB1B2A36 for ; Tue, 24 Jun 2014 07:47:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.15 X-Spam-Level: X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.651, WEIRD_PORT=0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0atRb2HgWtjg for ; Tue, 24 Jun 2014 07:47:51 -0700 (PDT) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 33E5A1B2ADE for ; Tue, 24 Jun 2014 07:47:39 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id E1D301651A1; Tue, 24 Jun 2014 10:47:38 -0400 (EDT) Received: from chaedge01.corp.arin.net (chaedge01.corp.arin.net [192.149.252.118]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id 2491E165194; Tue, 24 Jun 2014 10:47:38 -0400 (EDT) Received: from CHACAS02.corp.arin.net (10.1.30.108) by chaedge01.corp.arin.net (192.149.252.118) with Microsoft SMTP Server (TLS) id 14.3.181.6; Tue, 24 Jun 2014 10:47:34 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS02.corp.arin.net ([fe80::54ae:f9de:2f8b:1072%12]) with mapi id 14.03.0181.006; Tue, 24 Jun 2014 10:47:37 -0400 From: Andy Newton To: John Levine Thread-Topic: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt Thread-Index: AQHPjuL3knlBlwI8MEmTJhNqGrMjg5t/ydeAgADR6gA= Date: Tue, 24 Jun 2014 14:47:36 +0000 Message-ID: References: <20140624021617.9879.qmail@joyce.lan> In-Reply-To: <20140624021617.9879.qmail@joyce.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.0.64] Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/TqsVpXMxcyIHdXV3IIY2YSr27K0 Cc: "weirds@ietf.org" Subject: Re: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 14:47:53 -0000 On Jun 23, 2014, at 10:16 PM, John Levine wrote: > Change the template to remove the proto, and instead have an array of > URL prefixes. Since the templates are now the only thing in the > object, they doesn't need to be wrapped in an object: >=20 > "domain": [ > [ ["wtf"], [ > "https://example.net/rdapwtf/", > "http://example.net:8080/rdapwtf/", > "ftp://rdap@example.net/pub/file/rdapwtf/" > ] > ], > [ ["net", "com"], [ > "https://registry.example.com/myrdap/" > ] > ] > ] >=20 Requiring the use of default ports does seem odd. So I think an array of UR= Ls is a better solution. However, I think it would be better as an object w= ith two properties, =93secure=94 and =93non-secure=94: { =93secure=94: =93https://example.com:4443/slslsls/{resource}=94, =93non-secure=94: =93https://example.com:8080/slslsl/{resource}=94 } > For ASNs, it's just cruel to store the numbers as strings. Make them > either a single number or a two-element array for a range: >=20 I agree with this. > I understand that the point of making the key-like bit an array is to > make the bootstrap smaller for the relatively common case that a > single provider handles multiple keys, but it's not obvious to me that > the added complexity is worth it, compared to having one name-like > thing (domain name, CIDR, or ASN range) and a template, and just expand o= ut > the duplicates. I don=92t think it is added complexity, and keeping it smaller does improve= performance. For my client there is a noticeable difference between parsin= g the ASN registry vs the NET or domain registry because the ASN registry i= s much, much longer because it has lots of little allocations. > I concur with the note that providing prefixes rather than full > templates may make the URL lawn police unhappy, but we seem to have a > clear consensus that the syntax in rdap-query meets the needs of any > plausible RDAP server. Do we really want to keep fighting this battle? I think parsing a URL templ= ate and only substituting {resource} for the object lookup key is doable ev= en without a full-blown URL template library. -andy= From nobody Tue Jun 24 07:51:59 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E30ED1B2AD8 for ; Tue, 24 Jun 2014 07:51:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.55 X-Spam-Level: X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4fnVoqwN2syd for ; Tue, 24 Jun 2014 07:51: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 A53481B2ACA for ; Tue, 24 Jun 2014 07:51:56 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id 63A86165111; Tue, 24 Jun 2014 10:51:56 -0400 (EDT) Received: from chaedge01.corp.arin.net (chaedge01.corp.arin.net [192.149.252.118]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id AB939165107; Tue, 24 Jun 2014 10:51:55 -0400 (EDT) Received: from CHACAS01.corp.arin.net (10.1.30.107) by chaedge01.corp.arin.net (192.149.252.118) with Microsoft SMTP Server (TLS) id 14.3.181.6; Tue, 24 Jun 2014 10:51:52 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS01.corp.arin.net ([fe80::a98b:1e52:e85a:5979%13]) with mapi id 14.03.0181.006; Tue, 24 Jun 2014 10:51:55 -0400 From: Andy Newton To: Marc Blanchet Thread-Topic: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt Thread-Index: AQHPjuL3knlBlwI8MEmTJhNqGrMjg5uAnPaA Date: Tue, 24 Jun 2014 14:51:54 +0000 Message-ID: References: <20140623124326.21967.4986.idtracker@ietfa.amsl.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.0.64] Content-Type: multipart/alternative; boundary="_000_F7EF74A8BD9A4A50B3A99C158AA4F889arinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/Rz195MFypd3RwB4RLICe5OItWlw Cc: "weirds@ietf.org" Subject: Re: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 14:51:58 -0000 --_000_F7EF74A8BD9A4A50B3A99C158AA4F889arinnet_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable On Jun 23, 2014, at 8:59 AM, Marc Blanchet > wrote: Hello, here is a new version of the bootstrap document. This is a major rewrite b= ased on the various concensus points during last meeting and followup, such= as: JSON, using templates, IANA section rewrite, .... After some mailing l= ist discussions and discussions with rdap-query authors, this draft hopeful= ly covers the direction of the wg. One can look at the diffs, but I'm not sure it is that valuable given majo= r rewrite. Section 3 should probably have text stating that any unknown/unspecified JS= ON object properties or values should be ignored by implementers. This make= s future expansion of the registry easier. And given that, I think the =93version=94 property should indicate the form= at version and not the publication version. To indicate the date of publica= tion, it would make more sense to use =93publication=94 or something like t= hat. -andy --_000_F7EF74A8BD9A4A50B3A99C158AA4F889arinnet_ Content-Type: text/html; charset="Windows-1252" Content-ID: <44F76DFEBE9ADD45B1719D2B885E9306@corp.arin.net> Content-Transfer-Encoding: quoted-printable
On Jun 23, 2014, at 8:59 AM, Marc Blanchet <marc.blanchet@viagenie.ca> wrote:

Hello,
 here is a new version of the bootstrap document. This is a major= rewrite based on the various concensus points during last meeting and foll= owup, such as: JSON, using templates, IANA section rewrite, .... After some= mailing list discussions and discussions with rdap-query authors, this draft hopefully covers the direction of the = wg.
 One can look at the diffs, but I'm not sure it is that valuable = given major rewrite.

Section 3 should probably have text stating that any unknown/unspecifi= ed JSON object properties or values should be ignored by implementers. This= makes future expansion of the registry easier.

And given that, I think the =93version=94 property should indicate the= format version and not the publication version. To indicate the date of pu= blication, it would make more sense to use =93publication=94 or something l= ike that.

-andy

--_000_F7EF74A8BD9A4A50B3A99C158AA4F889arinnet_-- From nobody Tue Jun 24 09:13:08 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 643B81B2B16 for ; Tue, 24 Jun 2014 09:13:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.563 X-Spam-Level: * X-Spam-Status: No, score=1.563 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ZKr6p8IjO_O for ; Tue, 24 Jun 2014 09:13:03 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA8331B2B4A for ; Tue, 24 Jun 2014 09:11:57 -0700 (PDT) Received: (qmail 2831 invoked from network); 24 Jun 2014 16:11:56 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 24 Jun 2014 16:11: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; s=484b.53a9a34c.k1406; i=johnl@user.iecc.com; bh=GrryWBauYBpj0uldKHf/r0tebzbctkO4CD7ggs0i55c=; b=LVSXfYGUdVChmDwKW6rHlrHVO2Aypwfy+eGM4E2cjLYeTHI2JwzOF55QFljZ0JqBw6S0/BsGX6g4zveg8ai9hE8E/kRwM6XDsnmNhXaolC8HQFjUVZM/B7I9eBSZAWCUXLp/62a59BDmktYSen6ytrEj1fbOOXF0Lt0e1T8lpBOCuKcUCYHAyUvq5zOixbcYPcHgoY+V8C2izmNnfzeBwTronnRPdHFo3nxBwAIPoYtk/Zu9pdxpmEO6VGVame2P 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; s=484b.53a9a34c.k1406; olt=johnl@user.iecc.com; bh=GrryWBauYBpj0uldKHf/r0tebzbctkO4CD7ggs0i55c=; b=Vn8UboacNgSjEcd63J6dsZafcPrhx/uvZP3JFk/vCUuvF7dLPhWdQi/KkA4kRborzFp8y4HxfZvkxsEsDfkFVKG5EqyP2qp2QgnOREi82WhgxDpsA9PR+/PLa+NHM0wpUe2CvzFQ6FSJlX5pfEHtJErGr6Auds2faEOlvEeOqQLCUQP69PtDesLhXkZR6WontdS/N0pTI0nsFiokFTsueh4353h3Y0erUdvz5CPuMe6xP90qhQcLMPYghPADDSBp Date: 24 Jun 2014 16:11:34 -0000 Message-ID: <20140624161134.18506.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/Po9ye4LzEsHxsbmHeAHlyp_-0H4 Subject: Re: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 16:13:04 -0000 >implicit in the bootstrap registry type. For domains, the DNR could submit >{proto}://example.com/blahblah?domain={resource} just as easily as >{proto}://example.com/blahblah/{resource}. Except that in rdap-query, some of the resources are paths and some are queries: .../rdap/domain/example.wtf .../domains?name=example* If we're forced to be fully lawn-compatible, the stuff in the bootstrap has to be the URL of the template, and we accept a 100% query overhead since every query has to be preceded by a template fetch. (The templates can often be cached, but that assumes you're using a client with a persistent cache.) Or else we bloat up the bootstrap with separate patterns for every query type which would make it an order of magnitude bigger and a nightmare to maintain. I'm reasonably sure I heard Mark say that URL prefixes (remember when we added /.well-known ?) are adequate to satisfy the lawn concerns, since they avoid globally reserved URL segments. Let's just say they're prefixes and leave it at that. R's, John From nobody Tue Jun 24 09:17:12 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 021C31A0383 for ; Tue, 24 Jun 2014 09:17:12 -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=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qZraqeS3oGkh for ; Tue, 24 Jun 2014 09:17:10 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 977D91B2971 for ; Tue, 24 Jun 2014 09:17:10 -0700 (PDT) Received: (qmail 3884 invoked from network); 24 Jun 2014 16:17:09 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 24 Jun 2014 16:17: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; s=486a.53a9a485.k1406; i=johnl@user.iecc.com; bh=qP4GaSgY87LqSbqCZGHdibBMLQNK4GeiVddNhqyebO4=; b=oFzY28Do88QD/fbv+qtGzKjgVk2RpFS1IJ0sGgM6ny29/YH5wpktDCofrKRzUIn9ElPx0SoX0K2sjfPMVlihKPOBlyuFT7fo8eNpgv+UeER6BFx7RiFzIDOVVCRqyYf+YAbVrF81TP/8JNk+VIEZgWRmKjPJ54IxvONwz8Kmi9+zTZ30RLLq8AykHzbQgvE7pGsCP3kQyVmEntPU8fzkcTOIGC78xR1OnY0KHQL9nKzbiK+fgX8nd+KaF8J9hvV5 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; s=486a.53a9a485.k1406; olt=johnl@user.iecc.com; bh=qP4GaSgY87LqSbqCZGHdibBMLQNK4GeiVddNhqyebO4=; b=qE72Gws6r3OXlQshw0UsJx7VqOW9Wt1RB4snR4DUkeFln3Bj4x+yjuhpEb9GCty7DPVg12EBqSVFLW/uy4Q0t8R9OxvxHiYjrITlgpBKCsZrrGKSI4lVSgCiT+QVilKIdU6q/yKiLaNoU1aKcr1mA2hB2bPh3bCDIqx6kT72+g0csBe6+t5NFN/UulUJEzKsqKDe5UoxE+tCU/6iMZKicbdfa4KKhd2ycjV3o+P2If4MS80GJTnj+MvtP0o5vSHH Date: 24 Jun 2014 16:16:47 -0000 Message-ID: <20140624161647.18537.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/MrSiZmFKu8nY2ssmSBJvip2U2Zc Subject: Re: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 16:17:12 -0000 >> [ ["wtf"], [ >> "https://example.net/rdapwtf/", >> "http://example.net:8080/rdapwtf/", >> "ftp://rdap@example.net/pub/file/rdapwtf/" >> ] >> ], >However, I think it would be better as an object with two properties, “secure” and “non-secure”: > >{ > “secure”: “https://example.com:4443/slslsls/{resource}”, > “non-secure”: “https://example.com:8080/slslsl/{resource}” >} My example was intended to say try these in order until you find one that works. In your case, I am concerned about semantic overload. What does this mean? { "secure": "http://example.com:80/slslsls/{resource}", "non-secure": "https://example.com:443/slslsl/{resource}" } (Or to put it another way, if people want https, they presumably know how to spell it.) >> I understand that the point of making the key-like bit an array is to >> make the bootstrap smaller ... >I don’t think it is added complexity, and keeping it smaller does improve performance. For my client there >is a noticeable difference between parsing the ASN registry vs the NET or domain registry because the ASN >registry is much, much longer because it has lots of little allocations. Egad, actual data? If it makes a real difference, then never mind, that's fine. R's, John From nobody Tue Jun 24 09:27:12 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC9721B2B43 for ; Tue, 24 Jun 2014 09:27:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LystDOozkzwZ for ; Tue, 24 Jun 2014 09:27: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 AB9CD1B2AE1 for ; Tue, 24 Jun 2014 09:27:10 -0700 (PDT) Received: by smtp2.arin.net (Postfix, from userid 323) id 68AFD2136E9; Tue, 24 Jun 2014 12:27:10 -0400 (EDT) Received: from chaedge02.corp.arin.net (chaedge02.corp.arin.net [192.149.252.119]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp2.arin.net (Postfix) with ESMTP id AA1A521367E; Tue, 24 Jun 2014 12:27:09 -0400 (EDT) Received: from CHACAS01.corp.arin.net (10.1.30.107) by chaedge02.corp.arin.net (192.149.252.119) with Microsoft SMTP Server (TLS) id 14.3.181.6; Tue, 24 Jun 2014 12:27:19 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS01.corp.arin.net ([fe80::a98b:1e52:e85a:5979%13]) with mapi id 14.03.0181.006; Tue, 24 Jun 2014 12:27:09 -0400 From: Andy Newton To: John Levine Thread-Topic: [weirds] I-D Action: draft-ietf-weirds-bootstrap-02.txt Thread-Index: AQHPj8kk8ShGvTykl0WYRD+U7hDgMw== Date: Tue, 24 Jun 2014 16:27:08 +0000 Message-ID: References: <20140624161134.18506.qmail@joyce.lan> In-Reply-To: <20140624161134.18506.qmail@joyce.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.0.64] Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/MUreRXUwyXjbyYMJYcSEFYh3DeE Cc: "weirds@ietf.org" Subject: Re: [weirds] I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 16:27:12 -0000 On Jun 24, 2014, at 12:11 PM, John Levine wrote: >> implicit in the bootstrap registry type. For domains, the DNR could subm= it >> {proto}://example.com/blahblah?domain=3D{resource} just as easily as >> {proto}://example.com/blahblah/{resource}. >=20 > Except that in rdap-query, some of the resources are paths and some > are queries:=20 >=20 > .../rdap/domain/example.wtf > .../domains?name=3Dexample* >=20 >=20 > If we're forced to be fully lawn-compatible, the stuff in the > bootstrap has to be the URL of the template, and we accept a 100% > query overhead since every query has to be preceded by a template > fetch. (The templates can often be cached, but that assumes you're > using a client with a persistent cache.) Or else we bloat up the > bootstrap with separate patterns for every query type which would make > it an order of magnitude bigger and a nightmare to maintain. >=20 Can you explain this further? Why wouldn=92t the bootstrap just contain the= URL templates? Why do we need a fetch of the template? > I'm reasonably sure I heard Mark say that URL prefixes (remember when > we added /.well-known ?) are adequate to satisfy the lawn concerns, > since they avoid globally reserved URL segments. Let's just say > they're prefixes and leave it at that. My understanding is that ANY structure defined by the working group in the = URL is forbidden by the lawn mowers. -andy= From nobody Tue Jun 24 09:27:15 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E229D1B2B0B for ; Tue, 24 Jun 2014 09:27:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.55 X-Spam-Level: X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, WEIRD_PORT=0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E-_jjAtaHYxd for ; Tue, 24 Jun 2014 09:27: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 1FBBF1B2B44 for ; Tue, 24 Jun 2014 09:27:12 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id 706E8165301; Tue, 24 Jun 2014 12:27:11 -0400 (EDT) Received: from chaedge02.corp.arin.net (chaedge02.corp.arin.net [192.149.252.119]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.arin.net (Postfix) with ESMTP id DD27D1652EB; Tue, 24 Jun 2014 12:27:10 -0400 (EDT) Received: from CHACAS02.corp.arin.net (10.1.30.108) by chaedge02.corp.arin.net (192.149.252.119) with Microsoft SMTP Server (TLS) id 14.3.181.6; Tue, 24 Jun 2014 12:27:20 -0400 Received: from CHAMBX01.corp.arin.net ([fe80::1cef:1d7:cca9:5953]) by CHACAS02.corp.arin.net ([fe80::54ae:f9de:2f8b:1072%12]) with mapi id 14.03.0181.006; Tue, 24 Jun 2014 12:27:09 -0400 From: Andy Newton To: John Levine Thread-Topic: [weirds] I-D Action: draft-ietf-weirds-bootstrap-02.txt Thread-Index: AQHPj8kk60D9OsBiTEmdJh6eFMLFVg== Date: Tue, 24 Jun 2014 16:27:08 +0000 Message-ID: <317336CF-F78F-401D-B2E5-86142BA92B28@arin.net> References: <20140624161647.18537.qmail@joyce.lan> In-Reply-To: <20140624161647.18537.qmail@joyce.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.0.64] Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/3uPgyGWYCdKvhjJVebUPHkGe8FQ Cc: "weirds@ietf.org" Subject: Re: [weirds] I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 16:27:14 -0000 DQpPbiBKdW4gMjQsIDIwMTQsIGF0IDEyOjE2IFBNLCBKb2huIExldmluZSA8am9obmxAdGF1Z2gu Y29tPiB3cm90ZToNCg0KPj4+ICBbIFsid3RmIl0sIFsNCj4+PiAJCSJodHRwczovL2V4YW1wbGUu bmV0L3JkYXB3dGYvIiwNCj4+PiAJCSJodHRwOi8vZXhhbXBsZS5uZXQ6ODA4MC9yZGFwd3RmLyIs DQo+Pj4gCQkiZnRwOi8vcmRhcEBleGFtcGxlLm5ldC9wdWIvZmlsZS9yZGFwd3RmLyINCj4+PiAJ ICAgICAgIF0NCj4+PiAgXSwNCj4gDQo+PiBIb3dldmVyLCBJIHRoaW5rIGl0IHdvdWxkIGJlIGJl dHRlciBhcyBhbiBvYmplY3Qgd2l0aCB0d28gcHJvcGVydGllcywg77+9c2VjdXJl77+9IGFuZCDv v71ub24tc2VjdXJl77+9Og0KPj4gDQo+PiB7DQo+PiDvv71zZWN1cmXvv706IO+/vWh0dHBzOi8v ZXhhbXBsZS5jb206NDQ0My9zbHNsc2xzL3tyZXNvdXJjZX3vv70sDQo+PiDvv71ub24tc2VjdXJl 77+9OiDvv71odHRwczovL2V4YW1wbGUuY29tOjgwODAvc2xzbHNsL3tyZXNvdXJjZX3vv70NCj4+ IH0NCj4gDQo+IE15IGV4YW1wbGUgd2FzIGludGVuZGVkIHRvIHNheSB0cnkgdGhlc2UgaW4gb3Jk ZXIgdW50aWwgeW91IGZpbmQgb25lDQo+IHRoYXQgd29ya3MuICBJbiB5b3VyIGNhc2UsIEkgYW0g Y29uY2VybmVkIGFib3V0IHNlbWFudGljIG92ZXJsb2FkLg0KPiBXaGF0IGRvZXMgdGhpcyBtZWFu Pw0KPiANCj4gew0KPiAic2VjdXJlIjogImh0dHA6Ly9leGFtcGxlLmNvbTo4MC9zbHNsc2xzL3ty ZXNvdXJjZX0iLA0KPiAibm9uLXNlY3VyZSI6ICJodHRwczovL2V4YW1wbGUuY29tOjQ0My9zbHNs c2wve3Jlc291cmNlfSINCj4gfQ0KPiANCj4gKE9yIHRvIHB1dCBpdCBhbm90aGVyIHdheSwgaWYg cGVvcGxlIHdhbnQgaHR0cHMsIHRoZXkgcHJlc3VtYWJseSBrbm93IGhvdyB0byBzcGVsbCBpdC4p DQoNCkZhaXIgZW5vdWdoLiBZb3VyIHdheSB3b3JrcyBmb3IgbWUgdG9vIHRoZW4uDQoNCi1hbmR5 From nobody Tue Jun 24 10:28:55 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B26B1B2DE4 for ; Tue, 24 Jun 2014 10:28:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.563 X-Spam-Level: * X-Spam-Status: No, score=1.563 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wDbKbP7wUGnh for ; Tue, 24 Jun 2014 10:28:50 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 269F61B2B64 for ; Tue, 24 Jun 2014 10:28:49 -0700 (PDT) Received: (qmail 19388 invoked from network); 24 Jun 2014 17:28:48 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 24 Jun 2014 17:28: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; s=496f.53a9b550.k1406; i=johnl@user.iecc.com; bh=epWCOc8yhRCrxliUNoIQ3qVC0oHD6D5crm9Xj1RQSMM=; b=ivmlVG691QLP1zUO1vcrQ539H0O0SKoJhbFdn9iNesCmLrJuOHHshC/s1apq9TtnWyWb5OBZdGyIKOL1Pmaw5FEAGA1BjyBSIC36OnU5++nHoKv7sebhxGDAZXA9FZl3XlCC9yKIo45WyTDUocSaoUrAyIpF6Fcb4o87ne5Q5H1YGA3cfj7N0m7Is+sTsJteSbOk1ff7P/3i5Zu3x62LqWWX8vmzepIWig5eSdWg/KuslK1Dxp4Kzd6O09Dzonql 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; s=496f.53a9b550.k1406; olt=johnl@user.iecc.com; bh=epWCOc8yhRCrxliUNoIQ3qVC0oHD6D5crm9Xj1RQSMM=; b=HhXvT9SG1KiTH2Jzd4OAL2joHLmlhIyiEXusRWKJdZaPM5l8VmMyggLkmwBIYV+5Lce1DEvtUGQyD9UGjfYPtthbw71D4AzMCgzrmgQPwvYRt9zS6MnJoYkGW73qOSiiCSy9xFKJxCw19pn/fWlnn3McVDnUcbEXSGhQTWogJHESNDHUfLZnw4OtXYzLXUvb2Ojyw+4r7RFsxRdNr/lfC5o8nr0dy3+3MJFva1hU+OnOwjJT1FmzCYtC6wssEq7t Date: 24 Jun 2014 17:28:26 -0000 Message-ID: <20140624172826.18798.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/YMUvms6n-egN-4bckPOjaF2-ZKM Subject: Re: [weirds] I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 17:28:51 -0000 >Can you explain this further? Why wouldn’t the bootstrap just contain the URL templates? Why do we need a >fetch of the template? I count six lookup types and about six searches in rdap-query. As I understand it, if we're doing templates, that's 12 URL templates per bootstrap entry. >My understanding is that ANY structure defined by the working group in the URL is forbidden by the lawn mowers. That can't be right. They were OK with /.well-known/rdap/whatever. R's, John From nobody Tue Jun 24 10:40:23 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E53201B2E63 for ; Tue, 24 Jun 2014 10:40:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k67EUj6aUOQA for ; Tue, 24 Jun 2014 10:40:19 -0700 (PDT) Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D6EF1B2E55 for ; Tue, 24 Jun 2014 10:40:19 -0700 (PDT) Received: by mail-oa0-f45.google.com with SMTP id o6so741264oag.32 for ; Tue, 24 Jun 2014 10:40:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=LbtEkb2g3avd8IUo6c6pqRScqgx02uibNr3F4Wn6IXE=; b=gVUVEy520CnfNvnOagEbmxvhcriaKTfNupunPlGnxA+QOen9bXzeS+eC410u88SFoD Y2hdWo7mtKIKIulb8GjmUcWjeybXEZJe06/rV9NQXJ9LKwmBW/LUG0dLnsJjpxkGAKnK RGSYK4Q7VOoQDJorcCiTQL5AnJ1LiSN+UDWYHE/ZviI5LmpiSA3dYN6gyi8i1JLB3a0o 8QBhQrNABlnXPVCtCtT9GU6DD2TSxnj+sexA+YXeDAdXN0mjzUwRGNWV+fOQ+lIRJ3DU j0w8OO5pph8QpDlba58UxKQ1BQTB4HRyezGOExqb8QzbFZ2SNch2jwDWAQOTMBCNQ+Eg BTCQ== X-Gm-Message-State: ALoCoQmDPZw31y2PQ/owYaMGmU+Ufgvyvdqn2wCYS0ussHT+Bpyn4JT4T3nozKd09gZ5K/t+aUn5 MIME-Version: 1.0 X-Received: by 10.182.91.4 with SMTP id ca4mr2607638obb.26.1403631618890; Tue, 24 Jun 2014 10:40:18 -0700 (PDT) Received: by 10.76.153.66 with HTTP; Tue, 24 Jun 2014 10:40:18 -0700 (PDT) X-Originating-IP: [192.149.252.11] In-Reply-To: <20140624172826.18798.qmail@joyce.lan> References: <20140624172826.18798.qmail@joyce.lan> Date: Tue, 24 Jun 2014 14:40:18 -0300 Message-ID: From: Andrew Newton To: John Levine Content-Type: text/plain; charset=UTF-8 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/c-aBaMiQogIs-ed3_izBLT17WCM Cc: "weirds@ietf.org" Subject: Re: [weirds] I-D Action: draft-ietf-weirds-bootstrap-02.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 17:40:22 -0000 On Tue, Jun 24, 2014 at 2:28 PM, John Levine wrote: > I count six lookup types and about six searches in rdap-query. As I > understand it, if we're doing templates, that's 12 URL templates per > bootstrap entry. Yes, but only domain, ip address, and as lookup are applicable to bootstrapping. > >>My understanding is that ANY structure defined by the working group in the URL is forbidden by the lawn mowers. > > That can't be right. They were OK with /.well-known/rdap/whatever. Because .well-known is an acceptable vice in their particular religion. -andy From nobody Sat Jun 28 09:17:37 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 810901A0370; Sat, 28 Jun 2014 09:17:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kqpMQ5n5EJRP; Sat, 28 Jun 2014 09:17:34 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 036461A0369; Sat, 28 Jun 2014 09:17:34 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.5.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140628161734.24370.69152.idtracker@ietfa.amsl.com> Date: Sat, 28 Jun 2014 09:17:34 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/x6nwRkXb0ZOLgY_1XE5vgxopXDs Cc: weirds@ietf.org Subject: [weirds] I-D Action: draft-ietf-weirds-bootstrap-03.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2014 16:17:35 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web Extensible Internet Registration Data Service Working Group of the IETF. Title : Finding the Authoritative Registration Data (RDAP) Service Author : Marc Blanchet Filename : draft-ietf-weirds-bootstrap-03.txt Pages : 11 Date : 2014-06-28 Abstract: This document specifies a method to find which Registration Data Access Protocol (RDAP) server is authoritative to answer queries for a requested scope, such as domain names, IP addresses or Autonomous System numbers. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-weirds-bootstrap/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-weirds-bootstrap-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-weirds-bootstrap-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sat Jun 28 09:23:28 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E6671A036C for ; Sat, 28 Jun 2014 09:23:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nLJKz9xr70eJ for ; Sat, 28 Jun 2014 09:23:25 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2269B1A0372 for ; Sat, 28 Jun 2014 09:23:20 -0700 (PDT) Received: from [192.168.1.164] (modemcable060.86-160-184.mc.videotron.ca [184.160.86.60]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 700A740406 for ; Sat, 28 Jun 2014 12:23:19 -0400 (EDT) From: Marc Blanchet Content-Type: multipart/alternative; boundary="Apple-Mail=_F3509A56-0F8B-4641-91E1-DC5B49B37A7D" Date: Sat, 28 Jun 2014 12:23:18 -0400 References: <20140628161734.24370.69152.idtracker@ietfa.amsl.com> To: "" Message-Id: <2DE9E999-648C-46D3-AF12-29542284AC7B@viagenie.ca> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) X-Mailer: Apple Mail (2.1878.2) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/XaxC_bhT3qKTTgyIa8npAAtdUv0 Subject: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-03.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2014 16:23:27 -0000 --Apple-Mail=_F3509A56-0F8B-4641-91E1-DC5B49B37A7D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hello, this is an interim snapshot for the main purpose of introducing a = co-author who will be continuing the work in the near future. Some = recent comments were integrated but not all. There is really no need to = further comment this version, until a new version (-04) is published = which should address all the (good) comments received in the last week = or so. Regards, Marc. D=C3=A9but du message r=C3=A9exp=C3=A9di=C3=A9 : > De: internet-drafts@ietf.org > Objet: I-D Action: draft-ietf-weirds-bootstrap-03.txt > Date: 28 juin 2014 12:17:34 UTC=E2=88=924 > =C3=80: i-d-announce@ietf.org > Cc: weirds@ietf.org > R=C3=A9pondre =C3=A0: internet-drafts@ietf.org >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Web Extensible Internet Registration = Data Service Working Group of the IETF. >=20 > Title : Finding the Authoritative Registration Data = (RDAP) Service > Author : Marc Blanchet > Filename : draft-ietf-weirds-bootstrap-03.txt > Pages : 11 > Date : 2014-06-28 >=20 > Abstract: > This document specifies a method to find which Registration Data > Access Protocol (RDAP) server is authoritative to answer queries for > a requested scope, such as domain names, IP addresses or Autonomous > System numbers. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-weirds-bootstrap/ >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-weirds-bootstrap-03 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-weirds-bootstrap-03 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt --Apple-Mail=_F3509A56-0F8B-4641-91E1-DC5B49B37A7D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hello,
 this is an interim snapshot for the = main purpose of introducing a co-author who will be continuing the work = in the near future. Some recent comments were integrated but not all. = There is really no need to further comment this version, until a new = version (-04) is published which should address all the (good) comments = received in the last week or so.

Regards, = Marc.

D=C3=A9but du message r=C3=A9exp=C3=A9di=C3=A9 = :

Objet: = I-D Action: = draft-ietf-weirds-bootstrap-03.txt
Date: 28 juin 2014 12:17:34 = UTC=E2=88=924
R=C3=A9pondre =C3=A0: internet-drafts@ietf.org
<= /span>


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

       Title =           : Finding = the Authoritative Registration Data (RDAP) Service
=        Author =          : Marc = Blanchet
= Filename        : = draft-ietf-weirds-bootstrap-03.txt
Pages =           : = 11
= Date =            : = 2014-06-28

Abstract:
  This document specifies a = method to find which Registration Data
  Access Protocol = (RDAP) server is authoritative to answer queries for
  a = requested scope, such as domain names, IP addresses or Autonomous
=   System numbers.


The IETF datatracker status page = for this draft is:
htt= ps://datatracker.ietf.org/doc/draft-ietf-weirds-bootstrap/

Ther= e's also a htmlized version available = at:
http://tools.ietf.org/html/draft-ietf-weirds-bootstrap-03

A = diff from the previous version is available = at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-weirds-bootstrap-03

Please note that it may take a couple of minutes from the time = of submission
until the htmlized version and diff are available at = tools.ietf.org.

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

________________________= _______________________
I-D-Announce mailing = list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d= -announce
Internet-Draft directories: = http://www.ietf.org/shadow.html
or = ftp://ftp.ietf.org/ietf/1shadow-sites.txt

=
= --Apple-Mail=_F3509A56-0F8B-4641-91E1-DC5B49B37A7D--