From nobody Mon May 5 02:02:11 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 283BB1A029A for ; Mon, 5 May 2014 02:02:10 -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=unavailable 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 X3dXi1RiBPtF for ; Mon, 5 May 2014 02:02:07 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 0E27E1A0284 for ; Mon, 5 May 2014 02:02:06 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: jiashuo@cnnic.cn Received: from unknown218.241.103.136 (HELO cnnic) (218.241.103.136) by 218.241.118.7 with SMTP; Mon, 05 May 2014 17:02:01 +0800 From: =?gb2312?B?vNbLtg==?= To: , References: <20140430222306.17013.83001.idtracker@ietfa.amsl.com> In-Reply-To: <20140430222306.17013.83001.idtracker@ietfa.amsl.com> Date: Mon, 5 May 2014 17:02:01 +0800 Message-ID: <00ef01cf6840$ade9cc90$09bd65b0$@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: AQJAaFGFw2XUjfRFkKmjsVRoENcDhJpPpk+A Content-Language: zh-cn Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/R6Mrx_eXtBc0VSum6OnRmVucLk4 Cc: weirds@ietf.org Subject: [weirds] =?gb2312?b?tPC4tDogIEktRCBBY3Rpb246IGRyYWZ0LWlldGYtd2Vp?= =?gb2312?b?cmRzLWpzb24tcmVzcG9uc2UtMDcudHh0?= 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, 05 May 2014 09:02:10 -0000 Dear : About 'Add networks and autnums to the entity object class', my question: Network and autnum object also contain entity object, so it contains a circle: entities - network - entities -... Does it mean that nested 'networks and autnums' will not contain entities? and they should only be added to 'top' entity object ? = Thanks Regards 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 internet-drafts@ietf.org =B7=A2=CB=CD=CA=B1=BC=E4: 2014=C4=EA5=D4=C21=C8=D5 6:23 =CA=D5=BC=FE=C8=CB: i-d-announce@ietf.org =B3=AD=CB=CD: weirds@ietf.org =D6=F7=CC=E2: [weirds] I-D Action: = draft-ietf-weirds-json-response-07.txt 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 : JSON Responses for the Registration Data = Access Protocol (RDAP) Authors : Andrew Lee Newton Scott Hollenbeck Filename : draft-ietf-weirds-json-response-07.txt Pages : 83 Date : 2014-04-30 Abstract: This document describes JSON data structures representing registration information maintained by Regional Internet Registries (RIRs) and Domain Name Registries (DNRs). These data structures are used to form Registration Data Access Protocol (RDAP) query responses. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-weirds-json-response/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-weirds-json-response-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-weirds-json-response-07 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/ _______________________________________________ weirds mailing list weirds@ietf.org https://www.ietf.org/mailman/listinfo/weirds From nobody Mon May 5 07:51: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 2A3D01A0087 for ; Mon, 5 May 2014 07:51:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.199 X-Spam-Level: X-Spam-Status: No, score=0.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Ke4zMuA2tjJu for ; Mon, 5 May 2014 07:51:28 -0700 (PDT) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id ABF121A00A2 for ; Mon, 5 May 2014 07:51:28 -0700 (PDT) Received: by smtp2.arin.net (Postfix, from userid 323) id 4A171213664; Mon, 5 May 2014 10:51:25 -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 B0C7921365E; Mon, 5 May 2014 10:51:24 -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, 5 May 2014 10:51:24 -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, 5 May 2014 10:51:24 -0400 From: Andy Newton To: =?gb2312?B?vNbLtg==?= Thread-Topic: [weirds] I-D Action: draft-ietf-weirds-json-response-07.txt Thread-Index: AQHPaHF7jlMrCf0BsESi1WAuu8Ghsw== Date: Mon, 5 May 2014 14:51:23 +0000 Message-ID: References: <20140430222306.17013.83001.idtracker@ietfa.amsl.com> <00ef01cf6840$ade9cc90$09bd65b0$@cnnic.cn> In-Reply-To: <00ef01cf6840$ade9cc90$09bd65b0$@cnnic.cn> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.30.36] Content-Type: text/plain; charset="gb2312" Content-ID: <93507AE132D9AF4EB0C15BAC7858A164@corp.arin.net> Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/ZCBPK04kQ19KBuIjMiRjgC22SA0 Cc: "weirds@ietf.org" Subject: Re: [weirds] I-D Action: draft-ietf-weirds-json-response-07.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, 05 May 2014 14:51:30 -0000 DQoNCk9uIE1heSA1LCAyMDE0LCBhdCA1OjAyIEFNLCC81su2IDxqaWFzaHVvQGNubmljLmNuPiB3 cm90ZToNCg0KPiBEZWFyIDoNCj4gCUFib3V0ICdBZGQgbmV0d29ya3MgYW5kIGF1dG51bXMgdG8g dGhlIGVudGl0eSBvYmplY3QgY2xhc3MnLCBteQ0KPiBxdWVzdGlvbjoNCj4gCQlOZXR3b3JrIGFu ZCBhdXRudW0gb2JqZWN0IGFsc28gY29udGFpbiBlbnRpdHkgb2JqZWN0LCBzbyBpdA0KPiBjb250 YWlucyBhIGNpcmNsZTogZW50aXRpZXMgLSBuZXR3b3JrIC0gZW50aXRpZXMgLS4uLg0KPiAJCURv ZXMgaXQgbWVhbiB0aGF0ICBuZXN0ZWQgJ25ldHdvcmtzIGFuZCBhdXRudW1zJyB3aWxsIG5vdA0K PiBjb250YWluIGVudGl0aWVzPyBhbmQgdGhleSBzaG91bGQgb25seSBiZSBhZGRlZCB0byAndG9w JyBlbnRpdHkgb2JqZWN0ID8gDQo+IAkJVGhhbmtzDQo+IA0KPiBSZWdhcmRzDQo+IEppYXNodW8N Cg0KV2VsbCwgaXQgZG9lc26hr3QgbWFrZSBzZW5zZSB0byBpbmNsdWRlIHRoZSBlbnRpdGllcyBp biB0aGUgbmV0d29yayBvciBhdXRudW1zIGFzIHRoZWlyIHByZXNlbmNlIGluc2lkZSBhbiBlbnRp dHkgaXMgaW5kaWNhdGl2ZSBvZiB0aGF0IGFzc29jaWF0aW9uLg0KDQpXZSBjYW4gcHV0IHNvbWUg U0hPVUxEIGxhbmd1YWdlIGFib3V0IG5vdCBkb2luZyB0aGF0IGZvciB0aGUgc2VydmVycywgYW5k IHNvbWUgTVVTVCBsYW5ndWFnZSBmb3IgY2xpZW50cyB0byBiZSByZWFkeSB0byBhY2NlcHQgc3Vj aCBzaXR1YXRpb24gaWYgc2VydmVycyB2aW9sYXRlIHRoZSBTSE9VTEQuDQoNClRoYW5rcyBmb3Ig dGhlIGlucHV0Lg0KDQotYW5keQ== From nobody Mon May 5 17:55:42 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 15D421A0564 for ; Mon, 5 May 2014 17:55:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 fAxo98yF-fJs for ; Mon, 5 May 2014 17:55:40 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id ABB0E1A04A6 for ; Mon, 5 May 2014 17:55:37 -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, 06 May 2014 08:55:28 +0800 Date: Tue, 6 May 2014 08:55:30 +0800 From: "Linlin Zhou" To: "Andy Newton" , jiashuo References: <20140430222306.17013.83001.idtracker@ietfa.amsl.com>, <00ef01cf6840$ade9cc90$09bd65b0$@cnnic.cn>, X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7, 2, 5, 140[cn] Mime-Version: 1.0 Message-ID: <201405060855291969985@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart340618714231_=----" Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/A7S0KPpq7QrwohTosbac99HD8dE Cc: weirds Subject: Re: [weirds] I-D Action: draft-ietf-weirds-json-response-07.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, 06 May 2014 00:55:42 -0000 This is a multi-part message in MIME format. ------=_001_NextPart340618714231_=---- Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: base64 V2hhdCBpZiB0aGUgbmV0d29yayBvciBhdXRudW0gb2JqZWN0cyBpbmNsdWRlIGVudGl0aWVzIGJl c2lkZXMgdGhlIGVudGl0eSBpbiB0aGUgdG9wIGxldmVsPyBUaGlzIHNpdHVhdGlvbiBtYXkgYWxz byBjYXVzZSB0aGlzIHByb2JsZW0uDQoNClJlZ2FyZHMNCg0KDQpMaW5saW4gWmhvdQ0KIA0Kt6K8 /sjLo7ogQW5keSBOZXd0b24NCreiy83Ksbzko7ogMjAxNC0wNS0wNSAyMjo1MQ0KytW8/sjLo7og vNbLtg0Ks63LzaO6IHdlaXJkc0BpZXRmLm9yZw0K1vfM4qO6IFJlOiBbd2VpcmRzXSBJLUQgQWN0 aW9uOiBkcmFmdC1pZXRmLXdlaXJkcy1qc29uLXJlc3BvbnNlLTA3LnR4dA0KIA0KIA0KT24gTWF5 IDUsIDIwMTQsIGF0IDU6MDIgQU0sILzWy7YgPGppYXNodW9AY25uaWMuY24+IHdyb3RlOg0KIA0K PiBEZWFyIDoNCj4gQWJvdXQgJ0FkZCBuZXR3b3JrcyBhbmQgYXV0bnVtcyB0byB0aGUgZW50aXR5 IG9iamVjdCBjbGFzcycsIG15DQo+IHF1ZXN0aW9uOg0KPiBOZXR3b3JrIGFuZCBhdXRudW0gb2Jq ZWN0IGFsc28gY29udGFpbiBlbnRpdHkgb2JqZWN0LCBzbyBpdA0KPiBjb250YWlucyBhIGNpcmNs ZTogZW50aXRpZXMgLSBuZXR3b3JrIC0gZW50aXRpZXMgLS4uLg0KPiBEb2VzIGl0IG1lYW4gdGhh dCAgbmVzdGVkICduZXR3b3JrcyBhbmQgYXV0bnVtcycgd2lsbCBub3QNCj4gY29udGFpbiBlbnRp dGllcz8gYW5kIHRoZXkgc2hvdWxkIG9ubHkgYmUgYWRkZWQgdG8gJ3RvcCcgZW50aXR5IG9iamVj dCA/IA0KPiBUaGFua3MNCj4gDQo+IFJlZ2FyZHMNCj4gSmlhc2h1bw0KIA0KV2VsbCwgaXQgZG9l c26hr3QgbWFrZSBzZW5zZSB0byBpbmNsdWRlIHRoZSBlbnRpdGllcyBpbiB0aGUgbmV0d29yayBv ciBhdXRudW1zIGFzIHRoZWlyIHByZXNlbmNlIGluc2lkZSBhbiBlbnRpdHkgaXMgaW5kaWNhdGl2 ZSBvZiB0aGF0IGFzc29jaWF0aW9uLg0KIA0KV2UgY2FuIHB1dCBzb21lIFNIT1VMRCBsYW5ndWFn ZSBhYm91dCBub3QgZG9pbmcgdGhhdCBmb3IgdGhlIHNlcnZlcnMsIGFuZCBzb21lIE1VU1QgbGFu Z3VhZ2UgZm9yIGNsaWVudHMgdG8gYmUgcmVhZHkgdG8gYWNjZXB0IHN1Y2ggc2l0dWF0aW9uIGlm IHNlcnZlcnMgdmlvbGF0ZSB0aGUgU0hPVUxELg0KIA0KVGhhbmtzIGZvciB0aGUgaW5wdXQuDQog DQotYW5keQ0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N CndlaXJkcyBtYWlsaW5nIGxpc3QNCndlaXJkc0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5v cmcvbWFpbG1hbi9saXN0aW5mby93ZWlyZHMNCg== ------=_001_NextPart340618714231_=---- Content-Type: text/html; charset="GB2312" Content-Transfer-Encoding: quoted-printable =0A
I just supp= ose there may be a possible situation as below:

{=
    "entities" :
               &nbs= p;    {
&n= bsp;          &= nbsp;    "handle": "ABC-entity",= 
      "roles": [ "technical" ],
      ...
 &nbs=
p;    "networks": 
            {
  =
;  =
            "handle": "XXXX-RIR",
                ...
&nbs=
p;               "entities" :
         [
                   &nbs=
p; &nbs=
p;  "handle": "XYZ-entity",
   &n=
bsp; &nb=
sp;              ...
                   &nbs=
p; &nbs=
p;  "networks":
    <=
span style=3D"background-color: rgba(0, 0, 0, 0); font-family: =CE=A2=C8=
=ED=D1=C5=BA=DA; font-size: 10.5pt; line-height: 1.5;">   &=
nbsp; &n=
bsp;              {
 &=
nbsp;                      <=
/span>  &=
nbsp; &n=
bsp;...
              &nbs=
p;  =
;       }
                <=
/span>  ]=
 
    =
   &=
nbsp; &n=
bsp;  }  &n=
bsp; &nb=
sp;   
   },
= 
   ...
]
}
 "handle": "ABC-entity" and =  "handle": "XYZ-entity" are different entities.= "XYZ-entity" could appear in the second level of entity object, and maybe= there's a third or fourth level.

=0A
=
<= div>Linlin Zhou
=0A
 
=B7=A2=BC=FE=C8=CB=A3=BA Andy Newton
=B7=A2=CB=CD=CA=B1=BC=E4=A3= =BA 2014-05-06 21:33
=CA=D5=BC=FE=C8=CB=A3=BA Linlin Zhou
<= b>=B3=AD=CB=CD=A3=BA jiashuo<= /a>; weirds@ietf.org
= =D6=F7=CC=E2=A3=BA Re: [weirds] I-D Action: draft-ietf-weirds-jso= n-response-07.txt
=0A
=0A
=0A
On May 5, 2014, at 8:55 PM, Linlin Zhou <= ;zhoulinlin@cnnic.cn> wrote:=
=0A
=0A
=0A
To: "weirds@ietf.org" Content-Type: multipart/alternative; boundary=001a11c26ab4d4536d04f8fb26d9 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/D1a9J0lFtNRSNthA9tMBFPcdgGg Subject: [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, 09 May 2014 17:44:46 -0000 --001a11c26ab4d4536d04f8fb26d9 Content-Type: text/plain; charset=UTF-8 Colleagues, We've opened tracker items to cover the issues raised during the somewhat spirited discussions that took place in London. Since doing so, there has been nearly zero activity in terms of resolving them. Many of these issues were raised by people I know are on this list. Unfortunately, it seems like many of the participants here only put time into the work right before we go to meetings, or at the microphone. We need to make progress here. Your co-chairs had hoped we had enough momentum to need no meeting in Toronto. Accordingly, please take some time check out the open tracker items, which should have corresponding threads on this list, to support your concerns and hash them out with the working group. The authors need to resolve these issues in order for us to proceed toward our milestones, so this is your opportunity to make your concerns stick. We request the editors to post resolutions to the issues as they see fit and will assume that if there are no objections to them within two weeks, those resolutions have consensus. We need to deliver or dissolve. Thanks, -Murray & Olaf, WEIRDS co-chairs --001a11c26ab4d4536d04f8fb26d9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

=
Colleagues,

We've opened tracker items to cover the issues = raised during the somewhat spirited discussions that took place in London.= =C2=A0 Since doing so, there has been nearly zero activity in terms of reso= lving them.

Many of these issues were raised by people I know are on this lis= t.=C2=A0 Unfortunately, it seems like many of the participants here only pu= t time into the work right before we go to meetings, or at the microphone.<= br>
We need to make progress here.=C2=A0 Your co-chairs had hoped we had en= ough momentum to need no meeting in Toronto.=C2=A0 Accordingly, please take= some time check out the open tracker items, which should have correspondin= g threads on this list, to support your concerns and hash them out with the= working group.=C2=A0 The authors need to resolve these issues in order for= us to proceed toward our milestones, so this is your opportunity to make y= our concerns stick.

We request the editors to post resolutions to the issues as they= =20 see fit and will assume that if there are no objections to them within two = weeks,=20 those resolutions have consensus.

We need to deliver or = dissolve.

Thanks,
-Murray & Olaf, WEIRDS co-chairs

--001a11c26ab4d4536d04f8fb26d9-- From nobody Fri May 9 18: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 9839A1A0163 for ; Fri, 9 May 2014 18:43:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.542 X-Spam-Level: * X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_40=-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_NEUTRAL=0.779] 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 ez-Vl17x-JrB for ; Fri, 9 May 2014 18:43:29 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 561BE1A0079 for ; Fri, 9 May 2014 18:43:29 -0700 (PDT) Received: (qmail 54914 invoked from network); 10 May 2014 01:43:23 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 10 May 2014 01:43:23 -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=d755.536d843b.k1405; i=johnl@user.iecc.com; bh=KfiGqYi37V/w9lrT7WP65VTtEh7aYaCBg0tQ70GsLIA=; b=IKm7Qgvxsp8KVCEfVQ+utj8wyAZUuIvhbGCFmVTXrjol+PFzS0ABtdONImXcXLc1mFpn364iVnwHnVdu7hzDjHmdz82BiET6L6b+JsFw2NAozH6tmMlH3H4ZKAUTvGkYRyBaLHFZdXZUi5ztFYNoZxfWAecQ3ECN/J3hs/7WPD3qB9iHuLmbJOu/7mxRvry74IfWA/tEyCFm41a8N5IemNPt0PkmLssN4rDu5cfR1H4oiFT+ef/kgOYIVMeOD5MR 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=d755.536d843b.k1405; olt=johnl@user.iecc.com; bh=KfiGqYi37V/w9lrT7WP65VTtEh7aYaCBg0tQ70GsLIA=; b=k/JbI2qzQ891aEfidf1xntOtt6fAXqy7HmbsS3qRfM5/WHFHLMd16gOF4M12GjhkoGbJcnDe4vKMIIxtHqXf29dChpAPOkJSy5r0qjRVbS2+7LMm4lVj2KZiRH0Cz5DbzcjNguNWNjy4laH+LehllPbH79zXNXyERHLG7Sc8VmLVXwQJztN1oH0DXPsz9xxQd5TUnAJDrrr56aZG/phUJbhBilrplAsA9VMOAmCJ191oSnNIDomKOOWSdhIN5PHs Date: 10 May 2014 01:42:59 -0000 Message-ID: <20140510014259.55124.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/TBrR-bpNA7hnEALzxUXZKfKILaU 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: Sat, 10 May 2014 01:43:30 -0000 If Marc doesn't have time to do the new complicated bootstrap stuff, I can take a whack at it in the next week or two. R's, John From nobody Mon May 12 00:15:13 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 57E601A041D for ; Mon, 12 May 2014 00:15:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.582 X-Spam-Level: *** X-Spam-Status: No, score=3.582 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_FONT_FACE_BAD=0.981, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, 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 65ustIZKre2n for ; Mon, 12 May 2014 00:15:07 -0700 (PDT) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id EEB5A1A041A for ; Mon, 12 May 2014 00:15:06 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id 1559B165167; Mon, 12 May 2014 03:14:59 -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 43000164F73; Mon, 12 May 2014 03:14:56 -0400 (EDT) Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.342.3; Mon, 12 May 2014 03:14:56 -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, 12 May 2014 03:14:55 -0400 From: Andy Newton To: Linlin Zhou Thread-Topic: [weirds] I-D Action: draft-ietf-weirds-json-response-07.txt Thread-Index: AQHPbbHfU1poHh9eOUehx7MbcNDWxw== Date: Mon, 12 May 2014 07:14:54 +0000 Message-ID: References: <20140430222306.17013.83001.idtracker@ietfa.amsl.com>, <00ef01cf6840$ade9cc90$09bd65b0$@cnnic.cn>, , <201405060855291969985@cnnic.cn>, <2014050710472507014427@cnnic.cn> In-Reply-To: <2014050710472507014427@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_F27748A274E34F7A8E957DD749CDEF46arinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/9dV9pmVoYWVpijYDQaTAbQ-xzvQ Cc: "weirds@ietf.org" Subject: Re: [weirds] I-D Action: draft-ietf-weirds-json-response-07.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, 12 May 2014 07:15:10 -0000 --_000_F27748A274E34F7A8E957DD749CDEF46arinnet_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SSB3YXMgbG9va2luZyBmb3IgYSByZWFsLXdvcmxkIHNjZW5hcmlvLiBCdXQgdG8geW91ciBwb2lu dCwgcGVvcGxlIGNhbiBnZXQgaW52ZW50aXZlIGluIHRoZSBmdXR1cmUuIEmhr2xsIGluY2x1ZGUg c29tZSBsYW5ndWFnZSBhYm91dCBub3QgcmVwZWF0aW5nIG9iamVjdHMgYXMgdG8gYXZvaWQgbG9v cHMuDQoNCi1hbmR5DQoNCk9uIE1heSA3LCAyMDE0LCBhdCA0OjQ3IEFNLCBMaW5saW4gWmhvdSA8 emhvdWxpbmxpbkBjbm5pYy5jbjxtYWlsdG86emhvdWxpbmxpbkBjbm5pYy5jbj4+IHdyb3RlOg0K DQpJIGp1c3Qgc3VwcG9zZSB0aGVyZSBtYXkgYmUgYSBwb3NzaWJsZSBzaXR1YXRpb24gYXMgYmVs b3c6DQoNCnsNCiAgICAiZW50aXRpZXMiIDoNCiAgICAgICAgWw0KICAgICAgICAgICAgew0KICAg ICAgICAgICAgICAgICJoYW5kbGUiOiAiQUJDLWVudGl0eSIsDQoNCiAgICAgICJyb2xlcyI6IFsg InRlY2huaWNhbCIgXSwNCg0KICAgICAgLi4uDQoNCiAgICAgICJuZXR3b3JrcyI6DQoNCiAgICAg ICAgICAgIHsNCg0KICAgICAgICAgICAgICAgICJoYW5kbGUiOiAiWFhYWC1SSVIiLA0KDQogICAg ICAgICAgICAgICAgLi4uDQoNCiAgICAgICAgICAgICAgICAiZW50aXRpZXMiIDoNCg0KICAgICAg ICAgWw0KDQogICAgICAgICAgICAgICAgICAgICAgICAiaGFuZGxlIjogIlhZWi1lbnRpdHkiLA0K DQogICAgICAgICAgICAgICAgICAgICAgICAuLi4NCg0KICAgICAgICAgICAgICAgICAgICAgICAg Im5ldHdvcmtzIjoNCg0KICAgICAgICAgICAgICAgICAgICAgICAgew0KDQogICAgICAgICAgICAg ICAgICAgICAgICAgICAgIC4uLg0KDQogICAgICAgICAgICAgICAgICAgICAgICB9DQoNCiAgICAg ICAgICAgICAgICAgIF0NCg0KICAgICAgICAgICAgfQ0KDQogICB9LA0KDQogICAuLi4NCg0KXQ0K DQp9DQogImhhbmRsZSI6ICJBQkMtZW50aXR5IiBhbmQgICJoYW5kbGUiOiAiWFlaLWVudGl0eSIg YXJlIGRpZmZlcmVudCBlbnRpdGllcy4gIlhZWi1lbnRpdHkiIGNvdWxkIGFwcGVhciBpbiB0aGUg c2Vjb25kIGxldmVsIG9mIGVudGl0eSBvYmplY3QsIGFuZCBtYXliZSB0aGVyZSdzIGEgdGhpcmQg b3IgZm91cnRoIGxldmVsLg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KTGlu bGluIFpob3UNCg0Kt6K8/sjLo7ogQW5keSBOZXd0b248bWFpbHRvOmFuZHlAYXJpbi5uZXQ+DQq3 osvNyrG85KO6IDIwMTQtMDUtMDYgMjE6MzMNCsrVvP7Iy6O6IExpbmxpbiBaaG91PG1haWx0bzp6 aG91bGlubGluQGNubmljLmNuPg0Ks63LzaO6IGppYXNodW88bWFpbHRvOmppYXNodW9AY25uaWMu Y24+OyB3ZWlyZHNAaWV0Zi5vcmc8bWFpbHRvOndlaXJkc0BpZXRmLm9yZz4NCtb3zOKjuiBSZTog W3dlaXJkc10gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi13ZWlyZHMtanNvbi1yZXNwb25zZS0wNy50 eHQNCg0KT24gTWF5IDUsIDIwMTQsIGF0IDg6NTUgUE0sIExpbmxpbiBaaG91IDx6aG91bGlubGlu QGNubmljLmNuPG1haWx0bzp6aG91bGlubGluQGNubmljLmNuPj4gd3JvdGU6DQoNCldoYXQgaWYg dGhlIG5ldHdvcmsgb3IgYXV0bnVtIG9iamVjdHMgaW5jbHVkZSBlbnRpdGllcyBiZXNpZGVzIHRo ZSBlbnRpdHkgaW4gdGhlIHRvcCBsZXZlbD8gVGhpcyBzaXR1YXRpb24gbWF5IGFsc28gY2F1c2Ug dGhpcyBwcm9ibGVtLg0KDQpDYW4geW91IGRlc2NyaWJlIGFuIGFjdHVhbCBzY2VuYXJpbyB0aGF0 IHdvdWxkIGNhdXNlIHRoaXM/DQoNCi1hbmR5DQoNCg== --_000_F27748A274E34F7A8E957DD749CDEF46arinnet_ Content-Type: text/html; charset="gb2312" Content-ID: <83ECFECEB6D1434EA2F1FF9F96731DE7@corp.arin.net> Content-Transfer-Encoding: quoted-printable
I was looking for a real-world scenario. But to your point, people can= get inventive in the future. I=A1=AFll include some language about not rep= eating objects as to avoid loops.

-andy

On May 7, 2014, at 4:47 AM, Linlin Zhou <zhoulinlin@cnnic.cn> wrote:

I just suppose there may be a possible situation as below= :

{
    "entities" :
        [
            {
                "handle"= : "ABC-entity",
      "roles": [ "technical" ],
      ...
      "networks=
": 
            {

  &nb=
sp;  =
           "handle": "XXXX-RIR",


  &nb=
sp;  =
           ...


  &nb=
sp;  =
           "enti=
ties" :


         [


           =
;  &n=
bsp;          "handle": "XYZ-entity"=
;,


=
                        ...


=
                        "=
;networks":


=
                        {


=
                           &n=
bsp; ...


=
                        }


           =
;  &n=
bsp;    ] 


            }        

   },
   ...
]
}
 "handle": "ABC-entity" and=   "handle": "XYZ-entity" are different entities. "XYZ-entity" coul= d appear in the second level of entity object, and maybe there's a third or= fourth level.

Linlin = Zhou
 
=B7=A2=BC=FE=C8=CB=A3=BA = Andy Newton
=B7=A2=CB=CD=CA=B1=BC=E4=A3=BA 2014-05-06 21:33
=CA=D5=BC=FE=C8=CB=A3=BA Linlin Zhou
=B3=AD=CB=CD=A3=BA jia= shuo; weirds@ietf.org
=D6=F7=CC=E2=A3=BA Re: [weirds] I-D Action: draft-ietf-wei= rds-json-response-07.txt

On May 5, 2014, at 8:55 PM, Linlin Zhou <zhoulinlin@cnnic.cn> wrote:

What if the network or autnum objects include entities besides= the entity in the top level? This situation may also cause this problem.

Can you describe an actual scenario that would cause this?

-andy

--_000_F27748A274E34F7A8E957DD749CDEF46arinnet_-- From nobody Mon May 12 01:53:35 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 074411A0564 for ; Mon, 12 May 2014 01:53:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.663 X-Spam-Level: * X-Spam-Status: No, score=1.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 Fz1CB5Q8C41D for ; Mon, 12 May 2014 01:53:33 -0700 (PDT) Received: from smtp.centralnic.com (mail-7.fnb.uk.centralnic.net [5.44.25.120]) by ietfa.amsl.com (Postfix) with ESMTP id 0FC661A0549 for ; Mon, 12 May 2014 01:53:33 -0700 (PDT) Received: from Gavins-MacBook-Pro.local (unknown [217.138.20.162]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.centralnic.com (Postfix) with ESMTPSA id 93DF89D93 for ; Mon, 12 May 2014 08:53:26 +0000 (UTC) Message-ID: <53708C06.80002@centralnic.com> Date: Mon, 12 May 2014 09:53:26 +0100 From: Gavin Brown Organization: CentralNic Ltd User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: weirds@ietf.org X-Enigmail-Version: 1.6 OpenPGP: id=F923B4CE Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vnbO9F7IIO0hoXDoNRCgap6XetxnCGKRC" Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/yD_tScsU3LnllIQakLOwbR2d5Ds Subject: [weirds] Endpoint-centric RDAP bootstrap format 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, 12 May 2014 08:53:34 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --vnbO9F7IIO0hoXDoNRCgap6XetxnCGKRC Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all, One of the optimizations I suggested at IETF89 was that the bootstrap file define RDAP servers as first-order objects, and then map zones in the DNS to those servers. I had a stab at designing syntax that would implement this, which is at the link below. It also has a few other nice features, such as inheritanc= e. https://gist.github.com/jodrell/246faa9b1eb4ca617c9f Regards, --=20 Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for ccTLD, gTLD and private domain name registries https://www.centralnic.com/ CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR. --vnbO9F7IIO0hoXDoNRCgap6XetxnCGKRC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlNwjAYACgkQ6H45IPkjtM6lSwCdGhzuN4RChPy7V2rHIHj2iO1k YScAniTjgc5jm+iQwPxAiKH/X/hW4rWC =xU5I -----END PGP SIGNATURE----- --vnbO9F7IIO0hoXDoNRCgap6XetxnCGKRC-- From nobody Mon May 12 05:06:42 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 66BDB1A067E for ; Mon, 12 May 2014 05:06:39 -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 BWYSLg4QawIi for ; Mon, 12 May 2014 05:06:37 -0700 (PDT) Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com [209.85.220.41]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC0B1A067B for ; Mon, 12 May 2014 05:06:37 -0700 (PDT) Received: by mail-pa0-f41.google.com with SMTP id lj1so8434266pab.28 for ; Mon, 12 May 2014 05:06:31 -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=44ZhnMk3DB5mYXPBFPRwkG4bCD6iY1mYGGIgwSxwc4A=; b=S/SfMOOP3t1h//MxrmYJJry4ijqhX0dFRKyRfRERGf2U7RbbcMT/LrcC01oAakFXce +bNt0p5IvKgjyXiNWzipavAyu1OcNujo9CMZek8DthuIwAARPcuVhvSXKBx5sxzMqiV/ TtT/Bs/lPwF8jr3aCumuNDHkvx2cvvbpWZYiC15qGqIK95cJetwxZOUg7B5fN8hWEZ3u OzLaqHT8quloYvSZf8m3z7dZUlexKBCEMzFEPTZjRW4T3tnfKFDJ71Pw4q0ksre7178D UruWkoKcKLrY4917M9cbvDb5paJFJ0Qz877Qg3ajMv0t0CT51fUzpesJoupcbDSt4wF0 yzeA== X-Gm-Message-State: ALoCoQk6b/7a7c3pBJwZ/8lS+FYApTUYOX9OPYFsZPfHM9GpBr4WhVDT84UxIYBDbSIO9Y1qAxtx MIME-Version: 1.0 X-Received: by 10.66.65.169 with SMTP id y9mr54824698pas.145.1399896391457; Mon, 12 May 2014 05:06:31 -0700 (PDT) Received: by 10.66.16.200 with HTTP; Mon, 12 May 2014 05:06:31 -0700 (PDT) X-Originating-IP: [2001:67c:64:42:5d58:fa56:3beb:413e] In-Reply-To: <53708C06.80002@centralnic.com> References: <53708C06.80002@centralnic.com> Date: Mon, 12 May 2014 14:06:31 +0200 Message-ID: From: Andrew Newton To: Gavin Brown Content-Type: text/plain; charset=UTF-8 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/bSTnDJE5uP1jwfzsBrGLvdYk6EU Cc: "weirds@ietf.org" Subject: Re: [weirds] Endpoint-centric RDAP bootstrap format 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, 12 May 2014 12:06:39 -0000 Looks good. Here are a few suggestions: 1. There needs to be examples for the RIR use cases for IP addresses and autnums. 2. Have you considered adding structures for RDAP conformance identifiers (section 5.1 of json-response) and JSON prefixes (section 6 of using-http)? -andy On Mon, May 12, 2014 at 10:53 AM, Gavin Brown wrote: > Hi all, > > One of the optimizations I suggested at IETF89 was that the bootstrap > file define RDAP servers as first-order objects, and then map zones in > the DNS to those servers. > > I had a stab at designing syntax that would implement this, which is at > the link below. It also has a few other nice features, such as inheritance. > > https://gist.github.com/jodrell/246faa9b1eb4ca617c9f > > Regards, > > -- > Gavin Brown > Chief Technology Officer > CentralNic Group plc (LSE:CNIC) > Innovative, Reliable and Flexible Registry Services > for ccTLD, gTLD and private domain name registries > https://www.centralnic.com/ > > CentralNic Group plc is a company registered in England and Wales with > company number 8576358. Registered Offices: 35-39 Moorgate, London, > EC2R 6AR. > > > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds > From nobody Mon May 12 09:15:04 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 1218B1A0757 for ; Mon, 12 May 2014 09:14:50 -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 CDj773LGaaXK for ; Mon, 12 May 2014 09:14:47 -0700 (PDT) Received: from exprod6og112.obsmtp.com (exprod6og112.obsmtp.com [64.18.1.29]) by ietfa.amsl.com (Postfix) with ESMTP id EE2A31A0760 for ; Mon, 12 May 2014 09:14:45 -0700 (PDT) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob112.postini.com ([64.18.5.12]) with SMTP ID DSNKU3DzbxkQCy7KE6U9e60oxtB2wbreYpo/@postini.com; Mon, 12 May 2014 09:14:42 PDT Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id s4CGEdhx023055 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 12 May 2014 12:14:39 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 12 May 2014 12:14:39 -0400 From: "Hollenbeck, Scott" To: Gavin Brown , "weirds@ietf.org" Thread-Topic: [weirds] Endpoint-centric RDAP bootstrap format Thread-Index: AQHPbb+mJ+NKQRfJ7EiaDITqFvl1N5s9Gv+A Date: Mon, 12 May 2014 16:14:38 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F493E89E5@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <53708C06.80002@centralnic.com> In-Reply-To: <53708C06.80002@centralnic.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.173.152.4] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/zFZ4cWmDuf043wYlyAIJwdvEERQ Subject: Re: [weirds] Endpoint-centric RDAP bootstrap format 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, 12 May 2014 16:14:50 -0000 PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiB3ZWlyZHMgW21haWx0bzp3ZWly ZHMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEdhdmluIEJyb3duDQo+IFNlbnQ6IE1v bmRheSwgTWF5IDEyLCAyMDE0IDQ6NTMgQU0NCj4gVG86IHdlaXJkc0BpZXRmLm9yZw0KPiBTdWJq ZWN0OiBbd2VpcmRzXSBFbmRwb2ludC1jZW50cmljIFJEQVAgYm9vdHN0cmFwIGZvcm1hdA0KPiAN Cj4gSGkgYWxsLA0KPiANCj4gT25lIG9mIHRoZSBvcHRpbWl6YXRpb25zIEkgc3VnZ2VzdGVkIGF0 IElFVEY4OSB3YXMgdGhhdCB0aGUgYm9vdHN0cmFwDQo+IGZpbGUgZGVmaW5lIFJEQVAgc2VydmVy cyBhcyBmaXJzdC1vcmRlciBvYmplY3RzLCBhbmQgdGhlbiBtYXAgem9uZXMgaW4NCj4gdGhlIERO UyB0byB0aG9zZSBzZXJ2ZXJzLg0KPiANCj4gSSBoYWQgYSBzdGFiIGF0IGRlc2lnbmluZyBzeW50 YXggdGhhdCB3b3VsZCBpbXBsZW1lbnQgdGhpcywgd2hpY2ggaXMgYXQNCj4gdGhlIGxpbmsgYmVs b3cuIEl0IGFsc28gaGFzIGEgZmV3IG90aGVyIG5pY2UgZmVhdHVyZXMsIHN1Y2ggYXMNCj4gaW5o ZXJpdGFuY2UuDQo+IA0KPiBodHRwczovL2dpc3QuZ2l0aHViLmNvbS9qb2RyZWxsLzI0NmZhYTli MWViNGNhNjE3YzlmDQoNCkkgdGhpbmsgdGhpcyBjb3VsZCB3b3JrLiBVc2luZyByZGFwLXF1ZXJ5 IGFzIGFuIGV4YW1wbGUsIEkgd291bGQgcmUtd3JpdGUgMy4xLjMsIHRoZSBEb21haW4gUGF0aCBT ZWdtZW50IFNwZWNpZmljYXRpb24sIGxpa2UgdGhpczoNCg0KPFNvbWV3aGVyZSBJJ2Qgd3JpdGUg c29tZSBuZXcgdGV4dCB0byBub3RlIHRoYXQgdGhlIHZhbHVlcyBvZiB0aGUge3Byb3RvKSBhbmQg e2hvc3R9IHBhcmFtZXRlcnMgYXJlIGRldGVybWluZWQgdGhyb3VnaCB0aGUgYm9vdHN0cmFwIHBy b2Nlc3M+DQoNCiJEb21haW4gcGF0aCBzZWdtZW50cyBhcmUgY29uc3RydWN0ZWQgdXNpbmcgdGhl IGRvbWFpbiBsb29rdXAgdGVtcGxhdGUgc3BlY2lmaWVkIGluIFtib290c3RyYXAgcmVmZXJlbmNl XS4gVGhlIHRlbXBsYXRlIHBhcmFtZXRlcnMgTVVTVCBiZSByZXBsYWNlZCBhcyBmb2xsb3dzOg0K DQp7b2JqZWN0fTogZG9tYWluDQp7aWRlbnRpZmllcn06IDxkb21haW4gbmFtZT4NCg0Kd2hlcmUg PGRvbWFpbiBuYW1lPiBpcyBhIGZ1bGx5LXF1YWxpZmllZCAocmVsYXRpdmUgdG8gdGhlIHJvb3Qp IGRvbWFpbiBuYW1lLi4uIg0KDQpTZWFyY2ggd291bGQgYmUgc2ltaWxhcjoNCg0KIkRvbWFpbiBz ZWFyY2ggcGF0aCBzZWdtZW50cyBhcmUgY29uc3RydWN0ZWQgdXNpbmcgdGhlIGRvbWFpbiBzZWFy Y2ggdGVtcGxhdGUgc3BlY2lmaWVkIGluIFtib290c3RyYXAgcmVmZXJlbmNlXS4gVGhlIHRlbXBs YXRlIHBhcmFtZXRlcnMgTVVTVCBiZSByZXBsYWNlZCBhcyBmb2xsb3dzOg0KDQp7ZG9tYWlufTog PGRvbWFpbiBuYW1lPg0KDQp3aGVyZSA8ZG9tYWluIG5hbWU+IGlzIGEgc2VhcmNoIHBhdHRlcm4g cmVwcmVzZW50aW5nIGEgZG9tYWluIG5hbWUuLi4iDQoNClNjb3R0DQo= From nobody Mon May 12 09:53:22 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 D30161A0733 for ; Mon, 12 May 2014 09:53:20 -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 fvWhtSdxJ8hI for ; Mon, 12 May 2014 09:53:19 -0700 (PDT) Received: from exprod6og103.obsmtp.com (exprod6og103.obsmtp.com [64.18.1.185]) by ietfa.amsl.com (Postfix) with ESMTP id E02E91A072D for ; Mon, 12 May 2014 09:53:17 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob103.postini.com ([64.18.5.12]) with SMTP ID DSNKU3D8d36Q6A2eQwty7vYeXaBzZ43oBOpX@postini.com; Mon, 12 May 2014 09:53:13 PDT Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s4CGrB69018062 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 12 May 2014 12:53:11 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 12 May 2014 12:53:10 -0400 From: "Hollenbeck, Scott" To: "Murray S. Kucherawy" , "weirds@ietf.org" Thread-Topic: [weirds] WEIRDS inactivity, and issues raised in London Thread-Index: AQHPa65e8lpUhYtXiU+BtiUf/JlMBps9I46Q Date: Mon, 12 May 2014 16:53:09 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F493E8A61@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: In-Reply-To: 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="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/-2yk01xP4misyLQyMq1u7n3vQnU 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, 12 May 2014 16:53:21 -0000 PiBXZSByZXF1ZXN0IHRoZSBlZGl0b3JzIHRvIHBvc3QgcmVzb2x1dGlvbnMgdG8gdGhlIGlzc3Vl cyBhcyB0aGV5IHNlZSBmaXQgYW5kIHdpbGwgYXNzdW1lIHRoYXQgaWYgdGhlcmUgYXJlIG5vIG9i amVjdGlvbnMgdG8gdGhlbSB3aXRoaW4gdHdvIHdlZWtzLCB0aG9zZSByZXNvbHV0aW9ucyBoYXZl IGNvbnNlbnN1cy4NCg0KVGhlcmUgd2VyZSAxMSB0aWNrZXRzIG9wZW4gZm9yIHJkYXAtcXVlcnku IEEgY29tbW9uIHRocmVhZCBhbW9uZyB0aGUgbWFueSBzdWdnZXN0aW9ucyBpcyB0aGF0IHRoZXJl IGhhcyBiZWVuIHZlcnkgbGl0dGxlIGRpc2N1c3Npb24gb2YgdGhlIHByb3Bvc2Fscy4gUGxlYXNl IGNvcnJlY3QgYW55IG9mIG15IG1pcy1yZWNvbGxlY3Rpb25zIG9mIGxpc3QgZGlzY3Vzc2lvbjoN Cg0KNy4gUXVlcnkgUGF0dGVybiBGb3JtYXRzIChodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy93 Zy93ZWlyZHMvdHJhYy90aWNrZXQvNyMpDQoNClRleHQgd2lsbCBiZSBtb2RpZmllZCB0byBkZXNj cmliZSB0aGUgcGF0dGVybnMgYXMgUE9TSVggcmVndWxhciBleHByZXNzaW9ucy4NCg0KOC4gU2Vh cmNoIG9mIGRvbWFpbiBuYW1lcyBieSBuYW1lc2VydmVyIG5hbWUgKGh0dHA6Ly90cmFjLnRvb2xz LmlldGYub3JnL3dnL3dlaXJkcy90cmFjL3RpY2tldC84IykNCg0KSSBkb24ndCByZWNhbGwgc2Vl aW5nIGFueSBvYmplY3Rpb24gdG8gdGhpcyBzdWdnZXN0aW9uLiBJJ20gaW5jbGluZWQgdG8gaW5j bHVkZSBpdCBpbiB0aGUgbmV4dCB2ZXJzaW9uLg0KDQo5LiBTZWFyY2ggb2YgZG9tYWluIG5hbWVz IGJ5IG5hbWVzZXJ2ZXIgSVAgYWRkcmVzcyAoaHR0cDovL3RyYWMudG9vbHMuaWV0Zi5vcmcvd2cv d2VpcmRzL3RyYWMvdGlja2V0LzkjKQ0KDQpUaGlzIGFwcGVhcnMgdG8gYmUgYSBkdXBsaWNhdGUg b2YgIzI5LiBTZWUgYmVsb3cuDQoNCjEwLiBIYW5kbGUgU2VhcmNoIChodHRwOi8vdHJhYy50b29s cy5pZXRmLm9yZy93Zy93ZWlyZHMvdHJhYy90aWNrZXQvMTAjKQ0KDQpJIHZhZ3VlbHkgcmVjYWxs IEVybmllIERhaW5vdyBzdWdnZXN0aW5nIHRoYXQgdGhpcyBzZWFyY2ggd2FzIHVzZWZ1bCwgYnV0 IEknbSBpbmNsaW5lZCB0byByZW1vdmUgaXQgcGVyIEFuZHkncyBzdWdnZXN0aW9uDQoNCjExLiBR dWVyeSBvcHRpb25hbCBwYXJhbWV0ZXIgZm9yIGV4aXN0ZW5jZSBvZiByZWNvcmQgKGh0dHA6Ly90 cmFjLnRvb2xzLmlldGYub3JnL3dnL3dlaXJkcy90cmFjL3RpY2tldC8xMSMpDQoNCkknbSBpbmNs aW5lZCB0byBub3QgaW1wbGVtZW50IHRoaXMgc3VnZ2VzdGlvbiBkdWUgdG8gdGhlIGxhY2sgb2Yg cG9zaXRpb25zIGV4cHJlc3Npbmcgc3VwcG9ydCBmb3IgdGhlIGlkZWEuDQoNCjEzLiBVcGRhdGUg SlNPTiBSZWZlcmVuY2UgKGh0dHA6Ly90cmFjLnRvb2xzLmlldGYub3JnL3dnL3dlaXJkcy90cmFj L3RpY2tldC8xMyMpDQoNClJlZmVyZW5jZXMgdG8gUkZDIDQ2Mjcgd2lsbCBiZSByZXBsYWNlZCB3 aXRoIHJlZmVyZW5jZXMgdG8gUkZDIDcxNTguDQoNCjE1LiBSZW1vdmUgLndlbGwta25vd24gYW5k IFJlcGxhY2Ugd2l0aCBUZW1wbGF0ZSBVc2UgRGVzY3JpcHRpb24gKGh0dHA6Ly90cmFjLnRvb2xz LmlldGYub3JnL3dnL3dlaXJkcy90cmFjL3RpY2tldC8xNSMpDQoNCk91dGNvbWUgcGVuZGluZyBi b290c3RyYXAgdXBkYXRlIHdpdGggYSBwcm9wb3NhbCBmb3IgY29uc2lkZXJhdGlvbi4NCg0KMTYu IFVzZSBib290c3RyYXAgdGVtcGxhdGVzIChodHRwOi8vdHJhYy50b29scy5pZXRmLm9yZy93Zy93 ZWlyZHMvdHJhYy90aWNrZXQvMTYjKQ0KDQpUaGlzIGFwcGVhcnMgdG8gYmUgYSBkdXBsaWNhdGUg b2YgaXNzdWUgIzE1LiBJIGhhdmUgbWFya2VkIGl0IGFzIGEgZHVwbGljYXRlIGFuZCBjbG9zZWQg dGhlIHRpY2tldC4NCg0KMTkuIFVwZGF0ZSBIVFRQIFJlZmVyZW5jZSAoaHR0cDovL3RyYWMudG9v bHMuaWV0Zi5vcmcvd2cvd2VpcmRzL3RyYWMvdGlja2V0LzE5IykNCg0KUmVmZXJlbmNlcyB0byBS RkMgMjYxNiB3aWxsIGJlIHJlcGxhY2VkIHdpdGggcmVmZXJlbmNlcyB0byB3aGF0ZXZlciBSRkNz IGRyYWZ0LWlldGYtaHR0cGJpcy1odHRwMiAoc3RpbGwgd2l0aCB0aGUgV0cpIGFuZCBkcmFmdC1p ZXRmLWh0dHBiaXMtcDItc2VtYW50aWNzIChpbiBBVVRINDgpIGJlY29tZS4gQm90aCBtYXkgZW5k IHVwIGJlaW5nIGRvbmUgYnkgdGhlIFJGQyBFZGl0b3IgZGVwZW5kaW5nIG9uIHRpbWluZy4NCg0K MjUuIENsYXJpZnkgd2hhdCBpcyBkb25lIHdpdGggdW5zdXBwb3J0ZWQgcXVlcmllcyAoaHR0cDov L3RyYWMudG9vbHMuaWV0Zi5vcmcvd2cvd2VpcmRzL3RyYWMvdGlja2V0LzI1IykNCg0KVGV4dCB3 aWxsIGJlIGFkZGVkIHRvIHNheSB0aGF0IHRoZSBzZXJ2ZXIgc2hvdWxkIHJldHVybiBhIDQwMCAo QmFkIFJlcXVlc3QpIGVycm9yIGNvZGUuDQoNCjI5LiBDbGFyaWZ5IHRleHQgYWJvdXQgcXVlcnlp bmcgZm9yIGRvbWFpbnMgYnkgbmFtZXNlcnZlciBJUCAoaHR0cDovL3RyYWMudG9vbHMuaWV0Zi5v cmcvd2cvd2VpcmRzL3RyYWMvdGlja2V0LzI5IykNCg0KVGhpcyBhcHBlYXJzIHRvIGJlIGEgZHVw bGljYXRlIG9mIGlzc3VlICM5LiBJIGRvbid0IGhhdmUgYSBjbGVhciBzZW5zZSBvZiB3aGV0aGVy IG9yIG5vdCB0aGlzIHNob3VsZCBiZSBpbmNsdWRlZC4gTGlzdCBhbmQgaW4tcm9vbSBkaXNjdXNz aW9uIHdhcyBtaXhlZC4NCg0KU2NvdHQNCg0K From nobody Mon May 12 11:18: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 DE59A1A0756 for ; Mon, 12 May 2014 11:18:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.542 X-Spam-Level: * X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_40=-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_NEUTRAL=0.779] 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 6QSWPQUkaOr9 for ; Mon, 12 May 2014 11:18:32 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id AE06E1A074E for ; Mon, 12 May 2014 11:18:31 -0700 (PDT) Received: (qmail 14789 invoked from network); 12 May 2014 18:18:23 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 12 May 2014 18:18:23 -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=121dd.5371106f.k1405; i=johnl@user.iecc.com; bh=uNAhhCpNyZZqiWRERpanCfBAN7Og31A2Of6emF6f8hM=; b=QIpU9Xn735zjtxmhz8x2WaFPsKAR8GtgdgCV0zxiMOlcbLyvYFA9xCaSW1Df2zbp4izsV3zDyZA6dphIrTF7Jm5sPQRsoFS9KQDTZMBWKmeOQg7xv/ZMnvLM8psU7a4aP3LwZjESykoog5cB1uafY+wpQ5phxwsjZrmZRKMBoCvKohvVhQd2oqgQCKx/AsQPGjTPBY1JF/DmGIXQLCRtqd05469oPAVp1qU+kU0m2tZWZYwSu8QA5MA4fozsANQx 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=121dd.5371106f.k1405; olt=johnl@user.iecc.com; bh=uNAhhCpNyZZqiWRERpanCfBAN7Og31A2Of6emF6f8hM=; b=cn2yyY/rXWDKuRWlvR4ObQJu4iddUdxUIwLOY1w5fnjoe3WzWcR48j7RGN5bquqL8eRnFTIr0VThpu05bZ+OeEwVLXOeGOwC06uJ3asnGlhgaOIzD/pqoJRxHNpYj4RLfyxoM5d7TEnw5Hrb2Cbg8wCVY82DzEZHs26+/Jb9LT/+gznI70zNNDFI48ZIOFUyHO7j/JvaDHdiyh/qUNakno4uQU0bOYW5O0LnopgwsxaB6FzOdvfd0xt90fCM/YWF Date: 12 May 2014 18:18:00 -0000 Message-ID: <20140512181800.74204.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: <53708C06.80002@centralnic.com> 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/Vyh8g8qdNI9DoZrm-ylBuVA14l4 Cc: gavin.brown@centralnic.com Subject: Re: [weirds] Endpoint-centric RDAP bootstrap format 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, 12 May 2014 18:18:33 -0000 >One of the optimizations I suggested at IETF89 was that the bootstrap >file define RDAP servers as first-order objects, and then map zones in >the DNS to those servers. I'm not thrilled by this. It makes the minimum client much more complicated, and makes the bootstrap more fragile. Remember that there will be many more clients than servers, so given a choice, the complexity belongs in the server. If the bootstrap file is somewhat long and redundant, I don't see that as a problem, since we have grep. If you have a regular internal structure to your URLs (which in fact we do, and all agreed that we do before the get off my lawn detour), can't you use a a script at your end to generate all the bootstrap bits and ship them off to IANA? R's, John From nobody Mon May 12 19:18:36 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 2CD911A081F for ; Mon, 12 May 2014 19:18:34 -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 3fgXGg0kaHry for ; Mon, 12 May 2014 19:18:32 -0700 (PDT) Received: from off-send02.tyo.jprs.co.jp (off-send02.tyo.jprs.co.jp [IPv6:2001:df0:8:17::20]) by ietfa.amsl.com (Postfix) with ESMTP id 63EEB1A081E for ; Mon, 12 May 2014 19:18:32 -0700 (PDT) Received: from off-sendsmg02.tyo.jprs.co.jp (off-sendsmg02.tyo.jprs.co.jp [172.18.8.33]) by off-send02.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id s4D2IHSM012561; Tue, 13 May 2014 11:18:18 +0900 X-AuditID: ac120821-b7f4d6d000000d4f-89-537180e90447 Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg02.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id 42.6E.03407.9E081735; Tue, 13 May 2014 11:18:17 +0900 (JST) Date: Tue, 13 May 2014 11:18:15 +0900 (JST) Message-Id: <20140513.111815.116637487.kambe@jprs.co.jp> To: gavin.brown@centralnic.com From: Naoki Kambe In-Reply-To: <53708C06.80002@centralnic.com> References: <53708C06.80002@centralnic.com> 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+NgFrrHIsWRmVeSWpSXmKPExsWyRoiFT/dlQ2Gwwbs9BhYdC3awWczvOs7i wOSxavJaNo8lS34yBTBFcdmkpOZklqUW6dslcGU0v1Ar+M9XsWTuN9YGxvdcXYycHBICJhJX dx9ihLDFJC7cW8/WxcjFISRwklGi8+IVVpAEi4C2xM4VD5lBbF4BC4mJqyayg9giAnISPz4s YQKxmQWEJXa8eMkGYgsL2Ehs+dUL1ssmoCKx7N5msBpOAR2JjdeegS0TApq558lDIJuDg19A X2JqUwrEDXYSTX/fsYCEeQUEJf7uEIaYriXRM+MxO4QtL7H97RzmCYwCsxCqZiGpmoWkagEj 8ypGmfy0NN3i1LyU4tx0AyO9ksp8vayComK9ZBC9iREcnByKOxgf7TQ4xCjAwajEw8v5oSBY iDWxrLgy9xCjJAeTkijv7fzCYCG+pPyUyozE4oz4otKc1OJDjBIczEoivD3FQDnelMTKqtSi fJiUNAeLkjjv2jdnAoUE0hNLUrNTUwtSi2CyMhwcShK8+fVAjYJFqempFWmZOSUIaSYOTpDh PEDDv4HU8BYXJOYWZ6ZD5E8xSkqJ81aCJARAEhmleXC9rxjFgV4Q5l0CkuUBJhq4rldAA5mA BlpJ54MMLElESEk1MArtu8N3asHDPWb/Xn0umXIqN/DVutZqgR2RhvfY85Ue20ed/fh6l/Xa 9LoXFz+Ehqh//sJvJ1zhubRwV9pUvimWAacnb9shmLya6fYcr1juCWHMnjZGOXf2rFqo0aRq o7+Ji6HyA+f5EM3bKXO3ux0+2t00XXN/fDnDpEPyZRdruc8ULLSyeanEUpyRaKjFXFScCAAl iuG18QIAAA== Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/xFrBtm3ROy9lUEoltFcyALCFsuA Cc: weirds@ietf.org Subject: Re: [weirds] Endpoint-centric RDAP bootstrap format 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, 13 May 2014 02:18:34 -0000 From: Gavin Brown Date: Mon, 12 May 2014 09:53:26 +0100 > One of the optimizations I suggested at IETF89 was that the bootstrap > file define RDAP servers as first-order objects, and then map zones in > the DNS to those servers. > > I had a stab at designing syntax that would implement this, which is at > the link below. It also has a few other nice features, such as inheritance. > > https://gist.github.com/jodrell/246faa9b1eb4ca617c9f Thank you for the interesting example. Here are my quick comments inline: | // this structure maps DNS zones to RDAP endpoints: | "zones": { | "com" => "VRSN-THIN", | "net" => "VRSN-THIN", | "tv" => "VRSN", | "wiki" => "CNIC", | "la" => "CNIC", | "us.com" => "CNIC", | }, Are the above delimiters "=>" typo of ":"? | "us.com" => "CNIC", I think the "us.com" rdap server would be also resolved by the "com" rdap server. Should this bootstrap file contain SLD information? | // definition of global templates: | "templates": { | "default": "{proto}://{host}/{object}/{identifer}" | }, Do we also need a default search-type template here? | // definition of an RDAP endpoint: | "servers": [ | { ... | // supported protocols | "protos": [ "http", "https" ], I think "https" should be preferred than "http". It would be better that the order is reverse. | // URI templates | "templates": { ... | // templates for lookups | "lookup": { ... | // this one is a "custom" template | "host": "{proto}://{host}/nameserver/{host}", Two "{host}" variables seem to be used at the different meanings. This might be confusion. Could you rename either one or replace the former one with the actual name? Regards, Naoki Kambe From nobody Mon May 12 23:45:07 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 AF1C01A07D0 for ; Mon, 12 May 2014 23:45:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.037 X-Spam-Level: X-Spam-Status: No, score=-1.037 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 zCNOL6aA9DbV for ; Mon, 12 May 2014 23:45:02 -0700 (PDT) Received: from smtp.centralnic.com (mail-7.fnb.uk.centralnic.net [5.44.25.120]) by ietfa.amsl.com (Postfix) with ESMTP id F00661A0409 for ; Mon, 12 May 2014 23:45:01 -0700 (PDT) Received: from [192.168.43.58] (unknown [31.68.130.56]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.centralnic.com (Postfix) with ESMTPSA id 217499E81; Tue, 13 May 2014 06:44:52 +0000 (UTC) Message-ID: <5371BF5F.80002@centralnic.com> Date: Tue, 13 May 2014 07:44:47 +0100 From: Gavin Brown Organization: CentralNic Ltd User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Naoki Kambe References: <53708C06.80002@centralnic.com> <20140513.111815.116637487.kambe@jprs.co.jp> In-Reply-To: <20140513.111815.116637487.kambe@jprs.co.jp> X-Enigmail-Version: 1.6 OpenPGP: id=F923B4CE Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fmRI5GKRcWnn0sl7VProBBGUGuTtlqhW1" Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/sGQbUkEBEv_WLg4XL-54EQScHoA Cc: weirds@ietf.org Subject: Re: [weirds] Endpoint-centric RDAP bootstrap format 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, 13 May 2014 06:45:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --fmRI5GKRcWnn0sl7VProBBGUGuTtlqhW1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 13/05/2014 03:18, Naoki Kambe wrote: > Thank you for the interesting example. Here are my quick comments > inline: >=20 > | // this structure maps DNS zones to RDAP endpoints: > | "zones": { > | "com" =3D> "VRSN-THIN", > | "net" =3D> "VRSN-THIN", > | "tv" =3D> "VRSN", > | "wiki" =3D> "CNIC", > | "la" =3D> "CNIC", > | "us.com" =3D> "CNIC", > | }, >=20 > Are the above delimiters "=3D>" typo of ":"? Yes - my brain was still thinking in Perl. > | "us.com" =3D> "CNIC", >=20 > I think the "us.com" rdap server would be also resolved by the "com" > rdap server. Should this bootstrap file contain SLD information? Other than the fact that Verisign delegates us.com from com, the .us.com registry is unrelated to the .com registry, and will have a different RDAP endpoint. I certainly hope that SLDs such as us.com have a place in this file. > | // definition of global templates: > | "templates": { > | "default": "{proto}://{host}/{object}/{identifer}" > | }, >=20 > Do we also need a default search-type template here? Yes - the example is not complete but shows a minimal set of options. > | // supported protocols > | "protos": [ "http", "https" ], >=20 > I think "https" should be preferred than "http". It would be better > that the order is reverse. The order isn't meant to be meaningful, and I imagine that most clients would choose which protocol they prefer. > | // this one is a "custom" template > | "host": "{proto}://{host}/nameserver/{host}", >=20 > Two "{host}" variables seem to be used at the different meanings. This > might be confusion. Could you rename either one or replace the > former one with the actual name? Agreed - the second one should probably be {nameserver}. G. --=20 Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for ccTLD, gTLD and private domain name registries https://www.centralnic.com/ CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR. --fmRI5GKRcWnn0sl7VProBBGUGuTtlqhW1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlNxv18ACgkQ6H45IPkjtM7M4wCbBebt6YnV3J2xfFFwp6YPxHLN KhEAnRGK2SWTCQQvpSePAOngH/rNRjfX =9eqP -----END PGP SIGNATURE----- --fmRI5GKRcWnn0sl7VProBBGUGuTtlqhW1-- From nobody Tue May 13 03:55: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 9FE501A0051 for ; Tue, 13 May 2014 03:55:03 -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 pTM31bIDLEc6 for ; Tue, 13 May 2014 03:55:02 -0700 (PDT) Received: from off-send02.tyo.jprs.co.jp (off-send02.tyo.jprs.co.jp [IPv6:2001:df0:8:17::20]) by ietfa.amsl.com (Postfix) with ESMTP id 54D4F1A0037 for ; Tue, 13 May 2014 03:55:02 -0700 (PDT) Received: from off-sendsmg02.tyo.jprs.co.jp (off-sendsmg02.tyo.jprs.co.jp [172.18.8.33]) by off-send02.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id s4DAspZh012090; Tue, 13 May 2014 19:54:51 +0900 X-AuditID: ac120821-b7f4d6d000000d4f-94-5371f9fb2889 Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg02.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id 4C.11.03407.BF9F1735; Tue, 13 May 2014 19:54:51 +0900 (JST) Date: Tue, 13 May 2014 19:54:20 +0900 (JST) Message-Id: <20140513.195420.207480959.kambe@jprs.co.jp> To: gavin.brown@centralnic.com From: Naoki Kambe In-Reply-To: <5371BF5F.80002@centralnic.com> References: <53708C06.80002@centralnic.com> <20140513.111815.116637487.kambe@jprs.co.jp> <5371BF5F.80002@centralnic.com> 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+NgFrrPIsWRmVeSWpSXmKPExsWyRoiFT/f3z8Jgg3OL1Cw6Fuxgs5jfdZzF gclj1eS1bB5LlvxkCmCK4rJJSc3JLEst0rdL4MqYuHEPa8Fytop/C9ayNjD+Yuli5OSQEDCR 6Pr1lR3CFpO4cG89WxcjF4eQwElGiYe7ZrGBJFgEtCWufLoGVsQrYCFx7NYRVhBbREBO4seH JUwgNrOAsMSOFy/B6oUFbCS2/OoFq2ETUJFYdm8zWA2ngI7E/MdbwWqEBGokftz+CnQEBwe/ gL7E1KYUiBvsJJr+vgML8woISvzdIQwxXUuiZ8ZjdghbXmL72znMExgFZiFUzUJSNQtJ1QJG 5lWMMvlpabrFqXkpxbnpBkZ6JZX5elkFRcV6ySB6EyM4PDkUdzA+2mlwiFGAg1GJh5fzQ0Gw EGtiWXFl7iFGSQ4mJVHeri+FwUJ8SfkplRmJxRnxRaU5qcWHGCU4mJVEeN0/AeV4UxIrq1KL 8mFS0hwsSuK8a9+cCRQSSE8sSc1OTS1ILYLJynBwKEnwTvkB1ChYlJqeWpGWmVOCkGbi4AQZ zgM0fAVIDW9xQWJucWY6RP4Uo6SUOG8xSEIAJJFRmgfX+4pRHOgFYd61IFkeYKqB63oFNJAJ aKCVdD7IwJJEhJRUA+Mcq32/BH20QtZMVA6/pSn8d5vsMsvL23cW7YqfXX3/15GW6GWCOyu6 NRbctHvX2ynqv/FSzCP71BXrIyynzA6R8ZqQeui3LsvpgsfsLav7upaFShTOXxa3welduHPJ jCcWqdMXmWs/n3+BzXPvcamJlrYeNtu9q7R2icfN1snJt3kd+3zXQ2YlluKMREMt5qLiRABX h4S68gIAAA== Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/iCh932HmFiwbm_SYxg9qgv-Q9-M Cc: weirds@ietf.org Subject: Re: [weirds] Endpoint-centric RDAP bootstrap format 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, 13 May 2014 10:55:04 -0000 From: Gavin Brown Date: Tue, 13 May 2014 07:44:47 +0100 > > | "us.com" => "CNIC", > > > > I think the "us.com" rdap server would be also resolved by the "com" > > rdap server. Should this bootstrap file contain SLD information? > > Other than the fact that Verisign delegates us.com from com, the .us.com > registry is unrelated to the .com registry, and will have a different > RDAP endpoint. I certainly hope that SLDs such as us.com have a place in > this file. That's right, but I'm just afraid that the file might be so big and it might be hard for RDAP clients to parse it. In addition to such SLDs case, hundreds of new gtlds are being delegated from now. I'm just suspicious about whether this might be scalable well. Regards, Naoki Kambe From nobody Tue May 13 05:57: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 09D2C1A00B2 for ; Tue, 13 May 2014 05:57:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.142 X-Spam-Level: ** X-Spam-Status: No, score=2.142 tagged_above=-999 required=5 tests=[BAYES_40=-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, J_CHICKENPOX_66=0.6, SPF_NEUTRAL=0.779] 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 pn8D5RlxUrtT for ; Tue, 13 May 2014 05:57:43 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id E9B1B1A00A8 for ; Tue, 13 May 2014 05:57:41 -0700 (PDT) Received: (qmail 98401 invoked from network); 13 May 2014 12:57:35 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 13 May 2014 12:57:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=14c41.537216be.k1405; i=johnl@user.iecc.com; bh=etglG2CwbYEOxh5+vZb/1U3cPqpp032NI0lTfrfJWe8=; b=WKcxXkky2lh2AW5EG3c+xwRZqi6xRXwzdPdrSjRYUlvsP4PzAdig4z3wKVUQ6AyJ2EREqUehfQ5iXY8LjqWW3SNGd8s1eSykSDwvOaIiaE5M8kU73ws0xT//Dr0OU7kxGe+ezBd1tqKhnH+vBvmwgvxxr+tTJYk4qJYzF+I94PiJL+lr6H4NnUGZDZ1cl+Z4uh6AqN+QmlUnfhWKU1hNvBVVYcux5G6WnFHYVPQqN6hsRCSLrxVMXeA7bR4X9khJ DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=14c41.537216be.k1405; olt=johnl@user.iecc.com; bh=etglG2CwbYEOxh5+vZb/1U3cPqpp032NI0lTfrfJWe8=; b=fBjYRLI8YObEd6mDj/N0ShVobUo9Y2WZdmrYf+WxKz3Lo2W7mxqKNTyTwaz0QhKPio3oKLHb5wmjBrw6BP8XBg2LZWzHt3W+o6bdFtZjQgiTZnx/E9ozi05q5gIH5e9g0cNoKgYXIcELn818RM9j57wCQcYm7L/jtI8SpDKmx8RkzNITf00rDA0sd5TLk5d1X4amDAUHpnxDzBa0ZADLMll1tgu64SnRVDUTpD2aGUdwVxoA8KnZAzzG+r/GX/Pa Date: 13 May 2014 12:57:12 -0000 Message-ID: <20140513125712.85056.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: <20140513.195420.207480959.kambe@jprs.co.jp> 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/H9ONauro-z8zLwoT2zcnIjSVBxI Subject: Re: [weirds] A bootstrap, not a directory, was Endpoint-centric RDAP bootstrap format 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, 13 May 2014 12:57:45 -0000 >That's right, but I'm just afraid that the file might be so big and it >might be hard for RDAP clients to parse it. In addition to such SLDs >case, hundreds of new gtlds are being delegated from now. I'm just >suspicious about whether this might be scalable well. The more I think about this proposal, the more it looks like's an administrative nightmare, as well as . It adds a new name space, a server directory that someone would have to manage. If two organizations both send in a server named FOONIC, who wins? (Keep in mind that ccTLDs can feel strongly about things like this.) If there's an existing definition of FOONIC, and someone sends in a new one, how do you handle it? If the list of zones isn't the same as the old list do you merge them? If there are names missing from the new list, do you keep the old server definition around as FOONIC-OLD? If the new one adds new names and changes the server definition, do you assume they meant to update the existing names? IANA will make its own policies about what zones are eligible for the bootstrap server, but if an update includes a mixture of zones they handle because they're delegated directly (TLDs) and zones they don't (ac.uk, us.com), do they reject the whole thing? Skip the bad ones? It's also relatively difficult to verify the validity of a bootstrap in this format, since you need to do a tree walk from every listed zone to make sure there is a server with a working inheritance path, and that the zone names with the servers match the names in the directory. If there's a server with no zones, is that a bug? In my experience, the point of a bootstrap is to provide the simplest startup path for whatever software is using it. While this plan is an elegant way to store the information, it's not a good bootstrap. If you want, store it this way internally, but for the actual bootstrap, we need to flatten it so that if I want to find the contacts for, say, CHEESE.HOCKEY, I can get the entry for .HOCKEY and it's got the URLs I need. Earlier I said the bootstrap might have a single global default. That's probably still a reasonable idea, because in practice I expect every server will use the URI syntax in the draft, and only the prefix will vary. R's, John PS: I sure hope there aren't separate VRSN-THIN and VRSN-THICK bootstraps. One of the points of RDAP is that these are unified, and a thin registry does a 302 redirect to the registrar that can answer the question. From nobody Wed May 14 11:22:38 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 666611A0183 for ; Wed, 14 May 2014 11:22:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.141 X-Spam-Level: X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 R5rtQgsG7PP4 for ; Wed, 14 May 2014 11:22:33 -0700 (PDT) Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 9081C1A016C for ; Wed, 14 May 2014 11:22:33 -0700 (PDT) Received: from mx1.yitter.info (nat-07-mht.dyndns.com [216.146.45.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 92B3A8A031 for ; Wed, 14 May 2014 18:22:26 +0000 (UTC) Date: Wed, 14 May 2014 14:22:21 -0400 From: Andrew Sullivan To: weirds@ietf.org Message-ID: <20140514182220.GO3295@mx1.yitter.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/HEMxRKLcIB-fP9717IJJFWq-CF8 Subject: [weirds] bootstrap: Figure out a way to handle sub-TLD registry entries (#27) 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, 14 May 2014 18:22:35 -0000 Hi, Ticket 27 says that we need a way to include subordinate domains in the IANA registry. I don't understand why. Why shouldn't these be simple referrals from the top level RDAP system? (That this problem would crop up, by the way, is why I thought an IANA registry for this bootstrapping purpose was a bad idea. SRV records in the DNS would IMO still be better.) A PS: I didn't put this in the trac, because apparently the credentials for the trac are not what I thought they are, and the computer that knows about those credentials is in my apartment & not at this office. Hurray for passwords! -- Andrew Sullivan ajs@anvilwalrusden.com From nobody Wed May 14 11:27: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 E956E1A013E for ; Wed, 14 May 2014 11:27:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.141 X-Spam-Level: X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 Cfg4sDsAszKY for ; Wed, 14 May 2014 11:27:38 -0700 (PDT) Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 08F631A013C for ; Wed, 14 May 2014 11:27:37 -0700 (PDT) Received: from mx1.yitter.info (nat-07-mht.dyndns.com [216.146.45.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id E22618A031 for ; Wed, 14 May 2014 18:27:30 +0000 (UTC) Date: Wed, 14 May 2014 14:27:29 -0400 From: Andrew Sullivan To: weirds@ietf.org Message-ID: <20140514182729.GP3295@mx1.yitter.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/xI5cu4WTE8VMybZ81LpBzq56Y54 Subject: [weirds] rdap-query: Query Pattern Formats (ticket 7) 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, 14 May 2014 18:27:39 -0000 Hi, Ticket 7 is confusing to me. I'm trying to be sure I understand: are we trying to anchor searches around label boundaries in DNS names, or not? I think it will be surprising if not. Best regards, A -- Andrew Sullivan ajs@anvilwalrusden.com From nobody Wed May 14 11:38:56 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 763811A016C for ; Wed, 14 May 2014 11:38:54 -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 CFchfIsG-q3c for ; Wed, 14 May 2014 11:38:53 -0700 (PDT) Received: from exprod6og121.obsmtp.com (exprod6og121.obsmtp.com [64.18.1.237]) by ietfa.amsl.com (Postfix) with ESMTP id D77671A017F for ; Wed, 14 May 2014 11:38:51 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob121.postini.com ([64.18.5.12]) with SMTP ID DSNKU3O4NU1rpzahiLv4aXx95j5hXBXuHj+B@postini.com; Wed, 14 May 2014 11:38:46 PDT Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s4EIciVV015502 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 14 May 2014 14:38:44 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 14 May 2014 14:38:43 -0400 From: "Hollenbeck, Scott" To: Andrew Sullivan Thread-Topic: [weirds] rdap-query: Query Pattern Formats (ticket 7) Thread-Index: AQHPb6IuTZT/HH37ek+nP7LNGEP5/ZtAZnFg Date: Wed, 14 May 2014 18:38:43 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F493EBDCF@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <20140514182729.GP3295@mx1.yitter.info> In-Reply-To: <20140514182729.GP3295@mx1.yitter.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/PbEigAnkRpLimu2tHBjU3Z9D2pE Cc: "weirds@ietf.org" Subject: Re: [weirds] rdap-query: Query Pattern Formats (ticket 7) 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, 14 May 2014 18:38:54 -0000 > -----Original Message----- > From: weirds [mailto:weirds-bounces@ietf.org] On Behalf Of Andrew > Sullivan > Sent: Wednesday, May 14, 2014 2:27 PM > To: weirds@ietf.org > Subject: [weirds] rdap-query: Query Pattern Formats (ticket 7) >=20 > Hi, >=20 > Ticket 7 is confusing to me. I'm trying to be sure I understand: are > we trying to anchor searches around label boundaries in DNS names, or > not? I think it will be surprising if not. In the case of DNS names, yes, but we also have entity patterns to consider= . That's why the text in the ticket describes a regex approach to make the = intention clear instead of focusing on label boundaries in DNS names. Entit= ies aren't DNS names. Scott From nobody Wed May 14 11:51: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 30D751A0147 for ; Wed, 14 May 2014 11:51:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.141 X-Spam-Level: X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 9TZtcsYw6sSC for ; Wed, 14 May 2014 11:51:41 -0700 (PDT) Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 4A1C31A02C5 for ; Wed, 14 May 2014 11:51:41 -0700 (PDT) Received: from mx1.yitter.info (nat-07-mht.dyndns.com [216.146.45.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 193C08A031 for ; Wed, 14 May 2014 18:51:34 +0000 (UTC) Date: Wed, 14 May 2014 14:51:32 -0400 From: Andrew Sullivan To: weirds@ietf.org Message-ID: <20140514185132.GT3295@mx1.yitter.info> References: <20140514182729.GP3295@mx1.yitter.info> <831693C2CDA2E849A7D7A712B24E257F493EBDCF@BRN1WNEXMBX01.vcorp.ad.vrsn.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F493EBDCF@BRN1WNEXMBX01.vcorp.ad.vrsn.com> User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/gRTi5m4nSftFiIpuG-rLY59vJI4 Subject: Re: [weirds] rdap-query: Query Pattern Formats (ticket 7) 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, 14 May 2014 18:51:42 -0000 On Wed, May 14, 2014 at 06:38:43PM +0000, Hollenbeck, Scott wrote: > In the case of DNS names, yes, but we also have entity patterns to > consider. I got that part. > That's why the text in the ticket describes a regex > approach to make the intention clear instead of focusing on label > boundaries in DNS names. What was confusing to me was that the example _was_ using a DNS name, and indeed the implementation described there did the wrong thing. (I think that might have been the point, but I wasn't sure.) Anyway, as long as we keep this distinction, I'm happy. Thanks. A -- Andrew Sullivan ajs@anvilwalrusden.com From nobody Wed May 14 19:51:44 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 D00CD1A01C7 for ; Wed, 14 May 2014 19:51:41 -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 S-4Rnj8HUv-f for ; Wed, 14 May 2014 19:51:40 -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 5AA0B1A01BD for ; Wed, 14 May 2014 19:51:39 -0700 (PDT) Received: (qmail 20720 invoked from network); 15 May 2014 02:51:31 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 15 May 2014 02:51:31 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1498b.53742bb3.k1405; i=johnl@user.iecc.com; bh=TUcUyoymYSn3CU1V0k9Lzeqg82xzoO5Qh6g0fUIoXm8=; b=XTN3HPZcmz1bxCgyEdpn5ibHyA0U1yVyGa8IbKooVj9GbMDzuIskvO8Xk2fwHA+Or+WAEd21BQCd9+zP0ximYSjqOqBMBq+IOEiQ2IYY2tzIYLoHytH5Q0ZEwmhkGmEMLTEYRTmaVyMwFIcRvTSOmLaoUbuQ3INNrj0+zF6MW6baGjn33O7l7vHiDWbQ111Hz5Lh3me/KHkvtbS9mxfeZt8MGmK8zKlqXxn5eHH+qlLwzAIlw6U14TBHhUwixjLO 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=1498b.53742bb3.k1405; olt=johnl@user.iecc.com; bh=TUcUyoymYSn3CU1V0k9Lzeqg82xzoO5Qh6g0fUIoXm8=; b=oujNbCLYqT6zmJw8kFlIKNjbQSf7P3sDktTsCuxxKd1YTRBo6fVRXbLC8AOfZfr6HD+2cyC+EfV92rML9cZLDcIvZBhqfKhF8j0TyqaGxx6Rb0WTVE4PIP28hAaD+4Y3obtuGSyAp41En0w2jmWKwLFVUItMAhuOh25FnJJaVEuVy1LmzzDQpqpMvLqBlrQqizCLrhqrTiHBUeiIuFp4fLqj8hfhqhEAfgRPZSghH27zuJnJxU/Quvm7At0Z8bJU Date: 15 May 2014 02:51:09 -0000 Message-ID: <20140515025109.84362.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: <20140514182220.GO3295@mx1.yitter.info> 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/rPMvwzQ9QAgBcrtqcYE2q85GsBY Subject: Re: [weirds] bootstrap: Figure out a way to handle sub-TLD registry entries (#27) 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: Thu, 15 May 2014 02:51:42 -0000 >Ticket 27 says that we need a way to include subordinate domains in >the IANA registry. I don't understand why. Why shouldn't these be >simple referrals from the top level RDAP system? There are two administrative situations here, exemplified by ac.uk and uk.com. The ac.uk tree is run by Janet, while the rest of .uk is run by Nominet. When I brought this up, people said that Nominet would likely do the referral to Janet, because of their longstanding relationship. The uk.com tree is run by Centralnic, and nobody I know thinks Verisign is likely to do referrals other than to the registrars for thin registries. This impresses me as the sort of administrative issue that the IETF should not try to specify. If IANA runs the bootstrap site, they'll decide who qualifies to add entries to it. I realize this won't make everyone happy, but it's hard to imagine anything that the IETF could do here that would be unambiguously better. R's, John From nobody Wed May 14 20:36:04 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 3F2E41A021B for ; Wed, 14 May 2014 20:36:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.758 X-Spam-Level: * X-Spam-Status: No, score=1.758 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 8wA767ym6xjn for ; Wed, 14 May 2014 20:36:01 -0700 (PDT) Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B24A1A01EB for ; Wed, 14 May 2014 20:36:00 -0700 (PDT) Received: from mx1.yitter.info (c-76-118-173-172.hsd1.nh.comcast.net [76.118.173.172]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 183CE8A031 for ; Thu, 15 May 2014 03:35:53 +0000 (UTC) Date: Wed, 14 May 2014 23:35:47 -0400 From: Andrew Sullivan To: weirds@ietf.org Message-ID: <20140515033542.GA5935@mx1.yitter.info> References: <20140514182220.GO3295@mx1.yitter.info> <20140515025109.84362.qmail@joyce.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140515025109.84362.qmail@joyce.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/5bMtKch2NB5BII2fOQKh63Bnb8g Subject: Re: [weirds] bootstrap: Figure out a way to handle sub-TLD registry entries (#27) 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: Thu, 15 May 2014 03:36:02 -0000 On Thu, May 15, 2014 at 02:51:09AM -0000, John Levine wrote: > This impresses me as the sort of administrative issue that the IETF > should not try to specify. If IANA runs the bootstrap site, they'll > decide who qualifies to add entries to it. I realize this won't make > everyone happy, but it's hard to imagine anything that the IETF could > do here that would be unambiguously better. It's hard to think of anything the IETF could do that would be unambiguously worse, too. What you are proposing is to dump the (mostly political) problem of (in effect) what constitutes a public suffix onto a protocol parameters registry operated by IANA. I thought we got rid of that kind of problem by hiving it off to ICANN. This is going to introduce it again through the back door. The reason I always liked using SRV or some such records is because they are certain to work for the top-most level, they could be made to work for levels under that (but referrals will work just as well) when there is co-operation across the parts of the DNS tree, and if the client wanted to look for them they would work at every level. At the same time, the ability to publish the record would be fully aligned with control over the DNS name in question; and since this is supposed to be a registry data service for things that can be so nicely represented in the DNS, that seems a nice bit of symmetry. A central registry requires a central policy for what gets into the registry, which inevitably invites a fight about how to handle disputes, national regulations on what is permitted, &c. &c. If you don't believe me, I have months of (other) mailing list archives I will cheerfully send your way. I don't think we should paint that sort of target on the IANA protocol parameters registries. Best regards, A -- Andrew Sullivan ajs@anvilwalrusden.com From nobody Wed May 14 21:17: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 E2DF21A03B5 for ; Wed, 14 May 2014 21:17:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.062 X-Spam-Level: *** X-Spam-Status: No, score=3.062 tagged_above=-999 required=5 tests=[BAYES_40=-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, MANGLED_SPAM=2.3, 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 MBDPpW_FRr8t for ; Wed, 14 May 2014 21:17:25 -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 AD3041A03A9 for ; Wed, 14 May 2014 21:17:24 -0700 (PDT) Received: (qmail 27791 invoked from network); 15 May 2014 04:17:17 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 15 May 2014 04:17: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=14b06.53743fcd.k1405; i=johnl@user.iecc.com; bh=Aw8kcePAl25c3yxX7j+JuCsP+VlQw3tRSt7pcNctlOs=; b=NcU/d3v16IOSvtgQtb57uiXkOXjpNCa49FOa18OYiixbGk9WF1JdF+azhj8pR6FZq1pu7UYzwQRfsf8xPic25kInB12Al0Io0C4Wv86BG2ZnJwfqxqDDNI9Axvf2rL3IJ3EPa8JN4e2Oh2uy8uKVVEggQf5Wj5OBtM7/xt5CSAoz+8j1J0D2wlIGXBU+PfaZJr8/sVHTNN1TmZHyOHrtCA7gJWcgSTBKW+DpFjPbS+6UkkPGqzIqkHWMOtD8O4wJ 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=14b06.53743fcd.k1405; olt=johnl@user.iecc.com; bh=Aw8kcePAl25c3yxX7j+JuCsP+VlQw3tRSt7pcNctlOs=; b=ZOSi1cw7DVOYQFOvXdvSR+Hlo+1DGtcV2aXNuiFIMdTdvtDWqf2W0mtd1DMl1qeqUhI2HRTiAhrbDGTp/kjqDxUMTGkzvXXK1WELuA6qsSwzMT2t3ZeM64TquvhAw3lazmX+SD5f/vDrrgTvyX1B+mh7Ekj8yhkyeF4BPR2vQ+yfExsMkqF8u+CEoxoL6JGY/NyTo7zIHGuNr/WSGy9/8WRu+0OdtmfVjjyMjLv3HvNbK5bTS9c9hzZ8H+A2JktW Date: 15 May 2014 04:16:54 -0000 Message-ID: <20140515041654.84741.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: <20140515033542.GA5935@mx1.yitter.info> 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/zZXW63vwZm2XMPPlo-BGxtHuGUo Subject: Re: [weirds] bootstrap: Figure out a way to handle sub-TLD registry entries (#27) 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: Thu, 15 May 2014 04:17:26 -0000 >It's hard to think of anything the IETF could do that would be >unambiguously worse, too. What you are proposing is to dump the >(mostly political) problem of (in effect) what constitutes a public >suffix onto a protocol parameters registry operated by IANA. Not really. Remember, this is WEIRDS, not DBOUND. IANA currently publishes its Root Zone Database here: http://www.iana.org/domains/root/db Each entry in that database is a TLD, and most of them include the name of the WHOIS server for the TLD. I certainly don't speak for IANA, but my working assumption has been that the same entities that provide their WHOIS servers there will provide their WEIRDS bootstrap info. R's, John PS: I scrape the WHOIS server info every day into .ws.sp.am, like whois-servers.net but more up to date. From nobody Fri May 16 06:02: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 618C21A0230 for ; Fri, 16 May 2014 06:02:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.097 X-Spam-Level: * X-Spam-Status: No, score=1.097 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, 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 J8zCsvEDIT1X for ; Fri, 16 May 2014 06:02:18 -0700 (PDT) Received: from clone.registro.br (clone.registro.br [IPv6:2001:12ff:0:2::4]) by ietfa.amsl.com (Postfix) with ESMTP id AAB9C1A0186 for ; Fri, 16 May 2014 06:02:18 -0700 (PDT) Received: by clone.registro.br (Postfix, from userid 1000) id 7DC9324BE4F; Fri, 16 May 2014 10:02:10 -0300 (BRT) Date: Fri, 16 May 2014 10:02:10 -0300 From: Frederico A C Neves To: John Levine Message-ID: <20140516130210.GB59459@registro.br> References: <20140514182220.GO3295@mx1.yitter.info> <20140515025109.84362.qmail@joyce.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140515025109.84362.qmail@joyce.lan> Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/vDI7Go_9urJ7fq30YCvl8jgUG8Y Cc: weirds@ietf.org Subject: Re: [weirds] bootstrap: Figure out a way to handle sub-TLD registry entries (#27) 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, 16 May 2014 13:02:19 -0000 On Thu, May 15, 2014 at 02:51:09AM -0000, John Levine wrote: ... > This impresses me as the sort of administrative issue that the IETF > should not try to specify. If IANA runs the bootstrap site, they'll > decide who qualifies to add entries to it. I realize this won't make > everyone happy, but it's hard to imagine anything that the IETF could > do here that would be unambiguously better. This is a good reason on why we should keep it simple and specify only the bootstrap of the first level. Further indirection should be handled by redirects and policy along the publishing of then is a future work for ccTLDs policy bodies or the GNSO in the case of ICANN. Fred From nobody Sun May 18 09:33:38 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 BF64F1A010B for ; Sun, 18 May 2014 09:33:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.063 X-Spam-Level: *** X-Spam-Status: No, score=3.063 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, MANGLED_SPAM=2.3, 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 p7f9BUvwjGm2 for ; Sun, 18 May 2014 09:33:34 -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 569061A00D7 for ; Sun, 18 May 2014 09:33:34 -0700 (PDT) Received: (qmail 40810 invoked from network); 18 May 2014 16:33:31 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 18 May 2014 16:33:31 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=771a.5378e0db.k1405; i=johnl@user.iecc.com; bh=uPv0UGgo6+MEnKKEpQnw5F0cwgFa5PODwTo82mxTtdM=; b=bYsyvFlEpYD8LiNh2MHsvG6JetPxSxLAxkRls/mA7qcsVK6ohBIwjkb8gsxc5dkVU8f/CY2KgUQRix4V5E1vVradLq6lrGY4rwkx2saV9KxdtzN/5DS4Wc8SYLTd7AvQGqKGBSWWen2UxG3e6illOchyWXNxgbdAPC75VGaXU2dQStfcd70NY7bMMzqV8MCOTp3mSFq/XkW0IQmbEORUSlrABwJGMP1Dfp8nGTKeD0Dn4hYxzBMeRNGo80W0bHJT 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=771a.5378e0db.k1405; olt=johnl@user.iecc.com; bh=uPv0UGgo6+MEnKKEpQnw5F0cwgFa5PODwTo82mxTtdM=; b=tzWt4a2tJdYj/B4JifAFumXsA3Cr7Op2DwUSzDnD6E8MlEhIXUQZlhNDRlcoe4bO+gcKXTbPe59YvsQexZyqbD5M3OW5KR+yCt3VrEevKXYVjHzHUoOn9IZGjVs5TogUxUDjfawziuN6hlJ+Rb7LG2EHnDxpGVypTunEpYHw27TkBxrHlPdIMrKzKA3WUUq7Npak+dLIP/tMQaLPA4EA646VhU/PPneQ9Zhl5au9RsZSHEbVfNFJNvTDmKnnOD7o Date: 18 May 2014 16:33:07 -0000 Message-ID: <20140518163307.30489.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: <20140515041654.84741.qmail@joyce.lan> 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/QfvdfgwMnTUvu3Yas5Y1V23_qPQ Cc: johnl@taugh.com Subject: Re: [weirds] bootstrap: Figure out a way to handle sub-TLD registry entries (#27) 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, 18 May 2014 16:33:36 -0000 In article <20140515041654.84741.qmail@joyce.lan> you write: >>It's hard to think of anything the IETF could do that would be >>unambiguously worse, too. What you are proposing is to dump the >>(mostly political) problem of (in effect) what constitutes a public >>suffix onto a protocol parameters registry operated by IANA. > >Not really. Remember, this is WEIRDS, not DBOUND. ... Assuming IANA just publishes the bootstraps for TLDs for which they currently publish WHOIS servers, we're roughly where we are now. You can do a WHOIS lookup for a domain whose WHOIS server isn't in the IANA list, but you have to find the server some other way. This is already an issue, since there are a fair number of TLDs that have WHOIS servers but for whatever reason aren't in the IANA WHOIS database. (I have a manual exception list I use for my ws.sp.am hack.) If we publish a standard bootstrap format, there's nothing keeping other parties from publishing their own bootstrap lists that add more entries to the IANA list. R's, John From nobody Mon May 19 10:43:49 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 A263F1A02B9 for ; Mon, 19 May 2014 10:43:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.345 X-Spam-Level: * X-Spam-Status: No, score=1.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 uY6tlEXsV7CF for ; Mon, 19 May 2014 10:43:42 -0700 (PDT) Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FF4A1A007C for ; Mon, 19 May 2014 10:43:41 -0700 (PDT) Received: from crankycanuck.ca (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 3BF218A031 for ; Mon, 19 May 2014 17:43:41 +0000 (UTC) Date: Mon, 19 May 2014 13:43:40 -0400 From: Andrew Sullivan To: weirds@ietf.org Message-ID: <20140519174339.GF9558@crankycanuck.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140518163307.30489.qmail@joyce.lan> <20140515041654.84741.qmail@joyce.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/QPToKL6lNvfC7BCkX-6UHZ1i500 Subject: Re: [weirds] bootstrap: Figure out a way to handle sub-TLD registry entries (#27) 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, 19 May 2014 17:43:43 -0000 On Thu, May 15, 2014 at 04:16:54AM -0000, John Levine wrote: > > IANA currently publishes its Root Zone Database here: > > http://www.iana.org/domains/root/db > > Each entry in that database is a TLD By definition, yes. > name of the WHOIS server for the TLD. I certainly don't speak for > IANA, but my working assumption has been that the same entities that > provide their WHOIS servers there will provide their WEIRDS bootstrap > info. Right. And from there, the RDAP server can provide a referral to the next level down, in case that's appropriate. Otherwise, IANA needs to make up some sort of policy about what further levels go in. The original point, I thought, was that attempting to deal with either "co.uk" or "uk.com" is going to be problematic. I still think that is true, and I don't want to get IANA into that mess. You seemed to be arguing that those things ought to be coped with in the IANA repository; I believe doing so would be a mistake. > Assuming IANA just publishes the bootstraps for TLDs for which they > currently publish WHOIS servers, we're roughly where we are now. You > can do a WHOIS lookup for a domain whose WHOIS server isn't in the > IANA list, but you have to find the server some other way. Sure. The fact that you have to keep these extra lists on scraps of paper or whatever, however, seems like a problem with the existing system, not something that should be enshrined permanently. Which is why I at least preferred the DNS-based approach. I get it that the WG didn't select that approach, and I'm not trying to reopen that discussion. But IMO rejecting that approach meant that we also rejected publishing stuff _except_ the top level servers, and therefore I think this ticket should be closed "will not fix". Best regards, A -- Andrew Sullivan ajs@crankycanuck.ca From nobody Mon May 19 14:12:51 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 CCD231A038B for ; Mon, 19 May 2014 14:12:47 -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 a0bd_aSYAGgS for ; Mon, 19 May 2014 14:12:46 -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 EC6041A0417 for ; Mon, 19 May 2014 14:12:44 -0700 (PDT) Received: (qmail 35338 invoked from network); 19 May 2014 21:12:43 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 19 May 2014 21:12:43 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=c03.537a73cb.k1405; i=johnl@user.iecc.com; bh=GkFvjrHjus8wswbyqH66pn/L2MMkvBap/O4B9x4axeE=; b=LO/lXWD54N+Sd6Ah1qmHsPBk9wqQgLLnWmpxDr45pnc8nWsHAyst1nqhFQDqNTrTyODJrwvqMVyIqqut55JDc1uacwn0C0ahD7TCIoY8h6if9WlkIah0h2oz+XRQpVI9PqGHg2gzUMef0nrcRnq8/uI0DYHi82l78TUiD0eatUzoh2EsHtdeol9EbKVeTgqVDhr6BpYqdhs1ZGK2JKjntPniSSie3MZKmiVjuvhwEsC5YUJtpbZv298NYOqp7XdP 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=c03.537a73cb.k1405; olt=johnl@user.iecc.com; bh=GkFvjrHjus8wswbyqH66pn/L2MMkvBap/O4B9x4axeE=; b=wfdBeHmSBjYPJKfEmc3o0fRWahKAmraag9WDOOdyRZZfwZrBzhaH89FMSuRQNOcNCiLkl3XE/NmPOwZPIhhthit9lk0vYiRVg9teujSBKWsZ2BMsEgFqrtKZSjsf/qkKZSCCCz7RbHFRb1JFFmI3q0HkcW8Eji3IGtNZUSe9nZQNsWQCIxHhSveTqcKl5Uvn8HK7AG29E5cMQVPTy6ZgQ6+4w4awSKN6PSqeQLCdV9kT/0AQkxYOewI3hUhwSgWH Date: 19 May 2014 21:12:21 -0000 Message-ID: <20140519211221.3074.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: <20140519174339.GF9558@crankycanuck.ca> 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/-22edYvUMrITotgPTklJpfQEvRs Subject: Re: [weirds] bootstrap: Figure out a way to handle sub-TLD registry entries (#27) 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, 19 May 2014 21:12:48 -0000 >The original point, I thought, was that attempting to deal with either >"co.uk" or "uk.com" is going to be problematic. Not quite. Dealing with co.uk is not a problem, because it's run by the same people who run .uk. Dealing with ac.uk is probably not a problem because of the long relationship Janet (ac.uk) has with Nominet (uk). Dealing with uk.com is a problem, because Centralnic (uk.com) has no relationship with Verisign other than the one that the rest of the 100,000,000 registrants do. > I still think that is >true, and I don't want to get IANA into that mess. You seemed to be >arguing that those things ought to be coped with in the IANA >repository; I believe doing so would be a mistake. Oh, no, we agree. IANA publishes what it publishes, we don't attempt to make rules for what they include, only what the syntax and query scheme is. R's, John From nobody Tue May 20 00:46:48 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 047561A02F4 for ; Tue, 20 May 2014 00:46:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.663 X-Spam-Level: * X-Spam-Status: No, score=1.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 9xaKJVHtuIcF for ; Tue, 20 May 2014 00:46:45 -0700 (PDT) Received: from smtp.centralnic.com (mail-7.fnb.uk.centralnic.net [5.44.25.120]) (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 506B71A0290 for ; Tue, 20 May 2014 00:46:45 -0700 (PDT) Received: from [192.168.43.58] (unknown [31.68.134.117]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.centralnic.com (Postfix) with ESMTPSA id 52D399DF6; Tue, 20 May 2014 07:46:42 +0000 (UTC) Message-ID: <537B0861.7020509@centralnic.com> Date: Tue, 20 May 2014 08:46:41 +0100 From: Gavin Brown Organization: CentralNic Ltd User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: John Levine , weirds@ietf.org References: <20140518163307.30489.qmail@joyce.lan> In-Reply-To: <20140518163307.30489.qmail@joyce.lan> X-Enigmail-Version: 1.6 OpenPGP: id=F923B4CE Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="smTIrp9QVoLPcGUX85e8JdwVdlfT7OfDh" Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/mJnRkIrs-SdUFJJELKKx2avXcto Subject: Re: [weirds] bootstrap: Figure out a way to handle sub-TLD registry entries (#27) 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, 20 May 2014 07:46:47 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --smTIrp9QVoLPcGUX85e8JdwVdlfT7OfDh Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 18/05/2014 17:33, John Levine wrote: > If we publish a standard bootstrap format, there's nothing keeping > other parties from publishing their own bootstrap lists that add more > entries to the IANA list. Wouldn't that defeat the whole point of having a bootstrap? Instead of a single authoritative list of endpoints, the use of which is enshrined in an interoperable standard, there would be instead be multiple different lists, and different clients would be trained to use a different subset of those lists, resulting in exactly the sort of crappy user experience that whois provides now. As the operator of a registry service under a number of ccTLDs, newly delegated gTLDs and second-level domains, we see operational issues every day that are caused by the lack of an interoperable bootstrap mechanism for whois: transfer authorisation emails, SSL certificate authorisations and abuse takedown requests are regularly mis-addressed because there is a whois client somewhere that doesn't know where to query for a .wiki or a .uk.com. It would be a shame to propagate this state of affairs to the new protocol. G. --=20 Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for ccTLD, gTLD and private domain name registries https://www.centralnic.com/ CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR. --smTIrp9QVoLPcGUX85e8JdwVdlfT7OfDh Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlN7CGEACgkQ6H45IPkjtM5UjwCdH739GrIfmqaqHAj9G89cNqCw MlcAoImc4KbXQ5gN6mDwqvjd/lpxJo1l =g6Ai -----END PGP SIGNATURE----- --smTIrp9QVoLPcGUX85e8JdwVdlfT7OfDh-- From nobody Tue May 20 06:33:13 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 D59A31A070E for ; Tue, 20 May 2014 06:33:11 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 WSc-Hj1e2OBZ for ; Tue, 20 May 2014 06:33:10 -0700 (PDT) Received: from smtp89.ord1c.emailsrvr.com (smtp89.ord1c.emailsrvr.com [108.166.43.89]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 430E51A06EF for ; Tue, 20 May 2014 06:33:10 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 3C7EF140315 for ; Tue, 20 May 2014 09:33:09 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id F2BAB140D90 for ; Tue, 20 May 2014 09:33:08 -0400 (EDT) From: Olafur Gudmundsson Content-Type: multipart/alternative; boundary="Apple-Mail=_283473A3-ED89-4EAD-B555-F68CAED0B791" Date: Tue, 20 May 2014 09:33:06 -0400 References: 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/3j8R1LppeVPSwYjkbcADl0VTtko Subject: [weirds] weirds historical records Fwd: [apps-discuss] Time bound DNS names. 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, 20 May 2014 13:33:12 -0000 --Apple-Mail=_283473A3-ED89-4EAD-B555-F68CAED0B791 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I agree that if Information about domain is made public it is reasonable = to make history of=20 the domain public as well.=20 Should this be a requirement or extension? Olafur Begin forwarded message: > From: ht@inf.ed.ac.uk (Henry S. Thompson) > Subject: Re: [apps-discuss] Time bound DNS names. > Date: May 20, 2014 at 4:08:18 AM EDT > To: Phillip Hallam-Baker > Cc: apps-discuss@ietf.org >=20 > Phillip Hallam-Baker writes: >=20 >> . . . >=20 >> http://www.cnn.com.2010/whatever.html >> http://www.cnn.com.1.2010/whatever.html >> http://www.cnn.com.1.1.2010/whatever.html >=20 > This reminds me of one of the rather odd failings of the Internet > infrastructure: There is as far as I know no where to go to find the > answer to questions of the form implicit in the above proposal, that > is "Who was the owner of the cnn.com domain on 2010_01_01?". >=20 > We really ought to get a requirement of public archiving of domain > name 'ownership' records into the contractual requirements on > registrars. . . >=20 > ht > --=20 > Henry S. Thompson, School of Informatics, University of = Edinburgh > 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 = 650-4440 > Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk > URL: http://www.ltg.ed.ac.uk/~ht/ > [mail from me _always_ has a .sig like this -- mail without it is = forged spam] >=20 > _______________________________________________ > apps-discuss mailing list > apps-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/apps-discuss --Apple-Mail=_283473A3-ED89-4EAD-B555-F68CAED0B791 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

I agree that if Information = about domain is made public it is reasonable to make history = of 
the domain public as well. 
Should this be = a requirement or extension?

= Olafur


Begin forwarded = message:

From: = ht@inf.ed.ac.uk (Henry S. = Thompson)
Subject: = Re: = [apps-discuss] Time bound DNS names.
Date: May 20, 2014 at 4:08:18 AM = EDT
To: = Phillip Hallam-Baker = <phill@hallambaker.com>

Phillip Hallam-Baker writes:

. . .

http://www.cnn.com.2010/wha= tever.html
http://www.cnn.com.1.2010/whatever.html
http://www.cn= n.com.1.1.2010/whatever.html

This reminds me of one = of the rather odd failings of the Internet
infrastructure: There is = as far as I know no where to go to find the
answer to questions of = the form implicit in the above proposal, that
is "Who was the owner = of the cnn.com domain on = 2010_01_01?".

We really ought to get a requirement of public = archiving of domain
name 'ownership' records into the contractual = requirements on
registrars. . .

ht
--
=       Henry S. Thompson, School of = Informatics, University of Edinburgh
=      10 Crichton Street, Edinburgh EH8 9AB, = SCOTLAND -- (44) 131 650-4440
=             &n= bsp;  Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
=             &n= bsp;         URL: http://www.ltg.ed.ac.uk/~ht/
= [mail from me _always_ has a .sig like this -- mail without it is = forged = spam]

_______________________________________________
apps-discu= ss mailing list
apps-discuss@ietf.org
https:/= /www.ietf.org/mailman/listinfo/apps-discuss
= --Apple-Mail=_283473A3-ED89-4EAD-B555-F68CAED0B791-- From nobody Tue May 20 07:35: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 BEDA91A06F4 for ; Tue, 20 May 2014 07:35:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.422 X-Spam-Level: * X-Spam-Status: No, score=1.422 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPOOF_COM2OTH=2.723] 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 c5Xbw3eix3pt for ; Tue, 20 May 2014 07:35:05 -0700 (PDT) Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB77C1A0346 for ; Tue, 20 May 2014 07:35:04 -0700 (PDT) Received: from [IPv6:2001:1488:fffe:2:1aa9:5ff:fef6:7aa9] (unknown [IPv6:2001:1488:fffe:2:1aa9:5ff:fef6:7aa9]) by mail.nic.cz (Postfix) with ESMTPSA id 40F9013F634 for ; Tue, 20 May 2014 16:35:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.cz; s=default; t=1400596503; bh=mDPJ6ZsY+L5U6mtTGRHPzk/G6yZn4BXvqK4iEdRklis=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type; b=tNIWyGvTM54S27fpEdur4gQi/3MzFdxdAtzd1NLdwQ2km+qr1JTtzh/gxXLDz7ojm f2/PYUIck6OwaMhlVfLsuZC0tauPnJ1oSPqrXRfzrjTvdAze7llopkF7dt0ZeRt7NL yPrqTRXgAIaAbp9xg42jXFh5ztZG6ydgC81B/nHs= Message-ID: <537B6817.6000608@nic.cz> Date: Tue, 20 May 2014 16:35:03 +0200 From: "jan.korous@nic.cz" Organization: nic.cz User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.4.0 MIME-Version: 1.0 To: weirds@ietf.org References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------080908070202040602060805" X-Virus-Scanned: clamav-milter 0.97.8 at mail X-Virus-Status: Clean Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/GHhIWrbiq6p0r_efBJ7zCWhPmn0 Subject: Re: [weirds] weirds historical records Fwd: [apps-discuss] Time bound DNS names. 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, 20 May 2014 14:35:06 -0000 This is a multi-part message in MIME format. --------------080908070202040602060805 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I am not sure that rdap standard is the right place for public archiving requirements on DNRs. From my point of view it's unrelated isssue. Best regards Jan Korous On 05/20/2014 03:33 PM, Olafur Gudmundsson wrote: > > I agree that if Information about domain is made public it is > reasonable to make history of > the domain public as well. > Should this be a requirement or extension? > > Olafur > > > Begin forwarded message: > >> *From: *ht@inf.ed.ac.uk (Henry S. Thompson) >> *Subject: **Re: [apps-discuss] Time bound DNS names.* >> *Date: *May 20, 2014 at 4:08:18 AM EDT >> *To: *Phillip Hallam-Baker > > >> *Cc: *apps-discuss@ietf.org >> >> Phillip Hallam-Baker writes: >> >>> . . . >> >>> http://www.cnn.com.2010/whatever.html >>> http://www.cnn.com.1.2010/whatever.html >>> http://www.cnn.com.1.1.2010/whatever.html >> >> This reminds me of one of the rather odd failings of the Internet >> infrastructure: There is as far as I know no where to go to find the >> answer to questions of the form implicit in the above proposal, that >> is "Who was the owner of the cnn.com domain on >> 2010_01_01?". >> >> We really ought to get a requirement of public archiving of domain >> name 'ownership' records into the contractual requirements on >> registrars. . . >> >> ht >> -- >> Henry S. Thompson, School of Informatics, University of Edinburgh >> 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 >> Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk >> >> URL: http://www.ltg.ed.ac.uk/~ht/ >> >> [mail from me _always_ has a .sig like this -- mail without it is >> forged spam] >> >> _______________________________________________ >> apps-discuss mailing list >> apps-discuss@ietf.org >> https://www.ietf.org/mailman/listinfo/apps-discuss > > > > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds -- Jan Korous CZ.NIC Americka 23 120 00 Prague Czech Republic --------------080908070202040602060805 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
I am not sure that rdap standard is the right place for public archiving requirements on DNRs. From my point of view it's unrelated isssue.

Best regards

Jan Korous

On 05/20/2014 03:33 PM, Olafur Gudmundsson wrote:

I agree that if Information about domain is made public it is reasonable to make history of 
the domain public as well. 
Should this be a requirement or extension?

Olafur


Begin forwarded message:

From: ht@inf.ed.ac.uk (Henry S. Thompson)
Subject: Re: [apps-discuss] Time bound DNS names.
Date: May 20, 2014 at 4:08:18 AM EDT
To: Phillip Hallam-Baker <phill@hallambaker.com>

Phillip Hallam-Baker writes:

. . .

http://www.cnn.com.2010/whatever.html
http://www.cnn.com.1.2010/whatever.html
http://www.cnn.com.1.1.2010/whatever.html

This reminds me of one of the rather odd failings of the Internet
infrastructure: There is as far as I know no where to go to find the
answer to questions of the form implicit in the above proposal, that
is "Who was the owner of the cnn.com domain on 2010_01_01?".

We really ought to get a requirement of public archiving of domain
name 'ownership' records into the contractual requirements on
registrars. . .

ht
--
      Henry S. Thompson, School of Informatics, University of Edinburgh
     10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
               Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                      URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss



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



-- 

Jan Korous

CZ.NIC
Americka 23
120 00 Prague
Czech Republic
--------------080908070202040602060805-- From nobody Tue May 20 07:39:51 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 A7B6F1A0346 for ; Tue, 20 May 2014 07:39:50 -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 xrcDZ-5UUUnV for ; Tue, 20 May 2014 07:39:45 -0700 (PDT) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id A77D71A0395 for ; Tue, 20 May 2014 07:39:43 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id 232E316507E; Tue, 20 May 2014 10:39:43 -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 4D74216507B; Tue, 20 May 2014 10:39:42 -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; Tue, 20 May 2014 10:39:36 -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; Tue, 20 May 2014 10:39:36 -0400 From: Andy Newton To: Olafur Gudmundsson Thread-Topic: [weirds] weirds historical records Fwd: [apps-discuss] Time bound DNS names. Thread-Index: AQHPdDAOiKnP0CGwnkmeHoAdra355ZtJzVUA Date: Tue, 20 May 2014 14:39:35 +0000 Message-ID: <62AD30BA-C187-49EB-A722-F75C03A21F81@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_62AD30BAC18749EBA722F75C03A21F81arinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/rjJbi7i-3pAfLUHCpbaayGrFIm0 Cc: "weirds@ietf.org" Subject: Re: [weirds] weirds historical records Fwd: [apps-discuss] Time bound DNS names. 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, 20 May 2014 14:39:50 -0000 --_000_62AD30BAC18749EBA722F75C03A21F81arinnet_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I thought we ruled it out of scope. I don=92t mind rechartering to cover th= ese issues=85 once we get our current work done. But at present we all seem= to be halted on bootstrapping. -andy On May 20, 2014, at 9:33 AM, Olafur Gudmundsson > wrote: I agree that if Information about domain is made public it is reasonable to= make history of the domain public as well. Should this be a requirement or extension? Olafur Begin forwarded message: From: ht@inf.ed.ac.uk (Henry S. Thompson) Subject: Re: [apps-discuss] Time bound DNS names. Date: May 20, 2014 at 4:08:18 AM EDT To: Phillip Hallam-Baker > Cc: apps-discuss@ietf.org Phillip Hallam-Baker writes: . . . http://www.cnn.com.2010/whatever.html http://www.cnn.com.1.2010/whatever.html http://www.cnn.com.1.1.2010/whatever.html This reminds me of one of the rather odd failings of the Internet infrastructure: There is as far as I know no where to go to find the answer to questions of the form implicit in the above proposal, that is "Who was the owner of the cnn.com domain on 2010_01_01?= ". We really ought to get a requirement of public archiving of domain name 'ownership' records into the contractual requirements on registrars. . . ht -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail from me _always_ has a .sig like this -- mail without it is forged sp= am] _______________________________________________ apps-discuss mailing list apps-discuss@ietf.org https://www.ietf.org/mailman/listinfo/apps-discuss _______________________________________________ weirds mailing list weirds@ietf.org https://www.ietf.org/mailman/listinfo/weirds --_000_62AD30BAC18749EBA722F75C03A21F81arinnet_ Content-Type: text/html; charset="Windows-1252" Content-ID: <3C8C72BEEF61A248ADDE916A98E56C19@corp.arin.net> Content-Transfer-Encoding: quoted-printable
I thought we ruled it out of scope. I don=92t mind rechartering to cov= er these issues=85 once we get our current work done. But at present we all= seem to be halted on bootstrapping.

-andy

On May 20, 2014, at 9:33 AM, Olafur Gudmundsson <ogud@ogud.com> wrote:


I agree that if Information about domain is made public it is reasonab= le to make history of 
the domain public as well. 
Should this be a requirement or extension?

Olafur=


Begin forwarded message:

From: ht@inf.ed.ac.u= k (Henry S. Thompson)
Subject: Re: [apps-discuss] Time bound DNS names.
Date: May 20, 2014 at 4:08:18 AM EDT
To: Phillip Hallam-Baker <phill@hallambaker.com>

Phillip Hallam-Baker writes:

. . .

http://www.cnn.com.2010/whatever.html
http://www.cnn.com.1.20= 10/whatever.html
http://www.cnn.com.1.1.2010/whatever.html

This reminds me of one of the rather odd failings of the Internet
infrastructure: There is as far as I know no where to go to find the
answer to questions of the form implicit in the above proposal, that
is "Who was the owner of the cnn.com d= omain on 2010_01_01?".

We really ought to get a requirement of public archiving of domain
name 'ownership' records into the contractual requirements on
registrars. . .

ht
--
      Henry S. Thompson, School of Informatic= s, University of Edinburgh
     10 Crichton Street, Edinburgh EH8 9AB, SCOTLA= ND -- (44) 131 650-4440
            &nb= sp;  Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
            &nb= sp;         URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged sp= am]

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.= ietf.org/mailman/listinfo/apps-discuss

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

--_000_62AD30BAC18749EBA722F75C03A21F81arinnet_-- From nobody Tue May 20 08:16:13 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 B5A671A071C for ; Tue, 20 May 2014 08:16:09 -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 mxN63tBLT-nR for ; Tue, 20 May 2014 08:16:04 -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 42C461A0731 for ; Tue, 20 May 2014 08:15:51 -0700 (PDT) Received: (qmail 40140 invoked from network); 20 May 2014 15:15:49 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=9cca.537b71a5.k1405; bh=7SCLWohk+sk7QzBEWSJdRe4j5PWN60CRjOQMrUJjKzs=; b=AnVrShtOr19eTtZTrPixV0IoINmbMJnXytEKZY3MefUFjkq2Yo9KO+fmUkZfuBqeqe/GP8W+jNzyw1QOLvUKfSG5pU59WYSpZEp0eh5zL2BrULCuK7QXI/qCvgpcotbwe6gJ/s7HKBptMFtUCjFk1nNUa9OCo98aGJZjTA9QKtMPl8pY6bAX9Oo47M1Qss36WjxkHWFHX35p6XWUQNRzV36Baj7vVAl4lP+qgzW9amxMrQbKR9QpMAifEo2gML7g DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=9cca.537b71a5.k1405; bh=7SCLWohk+sk7QzBEWSJdRe4j5PWN60CRjOQMrUJjKzs=; b=QWQE6oK1e9hGRzgwCcfH1/WvPWdCYw9XQxhuue8Yk+V8ZGPt5sPZQVQtmiLWYOkpBTR9OMTFiRv6WgloTqX3x4qKrBESHReOLUN/nwOntBbJyobovfglHAUzbIlTyywST6TNRE+pK2kYEZaK1sPfRaEizTqu9qapiV3M/QWnhhXlMiPB12hIcdG1Hgk4EbwQY8pfsGCW3nGCwwY9wf/6/I68gntjjDWqsIJhi066htDtyt0cLzJzDLGNJdqfVQUp Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 20 May 2014 15:15:49 -0000 Date: 20 May 2014 11:15:48 -0400 Message-ID: From: "John R Levine" To: "Gavin Brown" In-Reply-To: <537B0861.7020509@centralnic.com> References: <20140518163307.30489.qmail@joyce.lan> <537B0861.7020509@centralnic.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Cleverness: None detected MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/Eo6OHfF7_vg3fIqT60L9eT0_pV4 Cc: weirds@ietf.org Subject: Re: [weirds] bootstrap: Figure out a way to handle sub-TLD registry entries (#27) 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, 20 May 2014 15:16:09 -0000 > On 18/05/2014 17:33, John Levine wrote: >> If we publish a standard bootstrap format, there's nothing keeping >> other parties from publishing their own bootstrap lists that add more >> entries to the IANA list. > > Wouldn't that defeat the whole point of having a bootstrap? Instead of a > single authoritative list of endpoints, ... The problem is the word "authoritative". I expect that IANA considers its list to be authoritiative, even though it contains neither uk.com, nor watkins-glen.ny.us. (The previous .us registry delegated it and several other locality registries to me over a decade ago, and I doubt that Neustar has thought about whether they'll do RDAP redirects.) The IETF is pretty good at building mechanism, and totally unable to build policy, since all of our standards are voluntary. When WEIRDS was new, some people demanded that each domain's RDAP entry MUST contain full unredacted contact info. While I sympathize with their goals, that's not how MUST works, and I told them so. We've now been around the bootstrap issue enough times that it seems unlikely there's any mechanism we've missed. For domains, it's either someone collects the bootstrap info in one place and publishes it, or the registries publish the info in the DNS, probably using DDDS and NAPTR. (I'd be OK with SRV but I expect the URI police would not.) I don't see any plausible way to look for NAPTR other than the two options of only look at the TLD, or do a tree walk of every name suffix, which the DNS crowd would hate, and would likely lead to chaos since not everyone who might purport to sell subdomains would do it as responsibly as you do. Regards, John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. From nobody Tue May 20 15:19: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 51E0E1A02B7 for ; Tue, 20 May 2014 15:19:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.762 X-Spam-Level: X-Spam-Status: No, score=0.762 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] 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 xEkGsrkrtSQR for ; Tue, 20 May 2014 15:19:05 -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 254671A018D for ; Tue, 20 May 2014 15:19:04 -0700 (PDT) Received: (qmail 98453 invoked from network); 20 May 2014 22:19:02 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 20 May 2014 22:19:02 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=2fb8.537bd4d6.k1405; i=johnl@user.iecc.com; bh=Os08RBcI2zFlA3C4rBXjPsEUJ1z+WB268f2hw7hI6Kc=; b=CCJgge4HjSK99M29tPoFjyfKpBsjUvphEGsGMXojtgBLJc6halXpLJ/WIXHtF0fQ+Yh8ylaDpPcukX2BOsY1x2R09YypvE0hfOSAvHInCqyV9PRRbKfdzytgI7immimgLg1MUbrKSqRuyW6ulDlTHwoQgrxGYiJifykuK0vrCNUBw9g8VszUxZAdh5TlnoMm0OGIjVp/5Izv94XtCBL2KP+P1hU3jDJGNDPIkQQEBguFGKdNbs5ivBarMOSzIbEd 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=2fb8.537bd4d6.k1405; olt=johnl@user.iecc.com; bh=Os08RBcI2zFlA3C4rBXjPsEUJ1z+WB268f2hw7hI6Kc=; b=ERNUFOtMaJsBrtkvKO/M7BkyY0B+e+CeO3Q+lUJM6NIOryjcSvKzJxfgAkSfe53f/0eJo1vW1jI/+lwqUqxyWEqZiN6I4omhzRNX9OaNwG5rgC15R0aeAZ89D7Esviqy+kDSbV/dbbWvKibvWOCrwOw9E95xJxU+AkD10UQf9amCDqddpFkHhxuHB73k5diHBL6OIgIFX0jHJRTjvNiB/8GjM/YAfPbl8xS/yXUcuGT0QWtn+j36Tz7Zc9u3pQrB Date: 20 May 2014 22:18:40 -0000 Message-ID: <20140520221840.12215.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/zjXY_6-ShVoUSDfP9gdP-xVt6ro Subject: Re: [weirds] weirds historical records Fwd: [apps-discuss] Time bound DNS names. 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, 20 May 2014 22:19:06 -0000 >I agree that if Information about domain is made public it is reasonable to make history of >the domain public as well. >Should this be a requirement or extension? We're the IETF, we can't make requirements on implementers, only tell them how to interoperate. If some of the domain registries say they'd implement a WHOWAS extension to RDAP, I suppose we could recharter and work on it after the current work is done. Otherwise I don't see any point. R's, John From nobody Tue May 27 07:29:03 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 496C41A0424 for ; Tue, 27 May 2014 07:29:02 -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 0toWurz1eurg for ; Tue, 27 May 2014 07:29:00 -0700 (PDT) Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72B4E1A011D for ; Tue, 27 May 2014 07:29:00 -0700 (PDT) Received: by mail-we0-f180.google.com with SMTP id q58so805763wes.25 for ; Tue, 27 May 2014 07:28:56 -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=JWTgH8OpcMCYco3vKJoBxv8WwUrrkn1vwms500BZb+0=; b=KzJ5GB2jEA94knt4ylIxEL5ftd+0f3J99uYMqhOXAn35zvG6Ssa5HD0qmqCwvCco2f E2X5RwypQt+2S8hTCT9LBlwNdYN+GMSdsedC0VUfrXd5WeOUQEX3fHp2S2dl/sNVj2c+ MgaN/nDa7IwemXvxHWln19jsgHmlVUAnww7OvB0AIzNMPBAzMF/0aYhs7JqTwdHXsCYr CRrFtgBqMUMIIhQO8kCrbLrYV4iDP36s79JT5zemOSg/N0EF122vUmi053g68UKJ40tm TVjSOtG4K9ycazlk9yYyei1kMPPAG6VcawNaaWGsJ2ZjXfogHyZSV+ePrC/pwz3Yf446 /nDA== MIME-Version: 1.0 X-Received: by 10.180.84.129 with SMTP id z1mr38103840wiy.8.1401200935568; Tue, 27 May 2014 07:28:55 -0700 (PDT) Received: by 10.180.210.194 with HTTP; Tue, 27 May 2014 07:28:55 -0700 (PDT) Date: Tue, 27 May 2014 07:28:55 -0700 Message-ID: From: "Murray S. Kucherawy" To: "weirds@ietf.org" Content-Type: multipart/alternative; boundary=f46d043bdec0060f5804fa6284d8 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/mZlT_ZSzwdydEUSkSfklzWHEMRg Subject: [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: Tue, 27 May 2014 14:29:02 -0000 --f46d043bdec0060f5804fa6284d8 Content-Type: text/plain; charset=UTF-8 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 --f46d043bdec0060f5804fa6284d8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Colleagues,

The window is open= for us to=20 request a meeting slot for Toronto.=C2=A0 Contrary to our expectations, it = doesn't appear we'll be finished before then.=C2=A0 Thus, we need t= o determine the size of the time slot we should request.

Pleas= e propose agenda items for this meeting in response to this thread.=C2=A0 If= you are=20 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 u= pdates pending for your drafts, please post them as soon as possible.=C2=A0= 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=20 Secretariat on Friday, June 20th.

-MSK, WEIRDS co-chair
--f46d043bdec0060f5804fa6284d8-- From nobody Tue May 27 11:18:19 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 A72711A0573 for ; Tue, 27 May 2014 11:18:17 -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 6wT6vQO7SjxU for ; Tue, 27 May 2014 11:18:16 -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 8F5B71A056D for ; Tue, 27 May 2014 11:18:16 -0700 (PDT) Received: (qmail 77001 invoked from network); 27 May 2014 18:18:10 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 27 May 2014 18:18:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=28e1.5384d6e2.k1405; i=johnl@user.iecc.com; bh=ri7rT+D5PZYkjnnwwQcREXn07a3iBtPv0L4MBNPWSB8=; b=gXflk/PDHcHKfS2yFVvXAHHEwVHBHkEwZgFrNvM+zVH/y5ciTTmC8R3fGs22i5u2/HdWFvCFa8xJzQLhV/23DWsIlLWL1YofpEl6+mMhW3ePf7pzTI3ZhGxl6V3Vzz1DwcBykP8pdVqoAXIAgyFlDo2DxiYF+F/ubNsY3rqbi+3KhEmmB8IeioY9x3tzHYbot9Qz+cbQtu8UFKDIIdB049SCbDhPkFurNHMd/dFaIRYkvlTa9XZ5XuJ1xfS3l72W 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=28e1.5384d6e2.k1405; olt=johnl@user.iecc.com; bh=ri7rT+D5PZYkjnnwwQcREXn07a3iBtPv0L4MBNPWSB8=; b=ro+7pOtBcXBJ+iii/I1VlJdfvF4jfJ4NRDCISc+DG4hSRkzW4SZX3M4Eclbb2SCfa58MWWVropgiBSkWv4qoU/hWv19oIjep6Fd5ovDzBdc6Xn2k54YnDAPzNeXVpTKSJ7BMOkaAXNdITCckxqUmuhznqgyIvkYorkR6C1rKhPl3Dt8H7ADKbRW6b5ifd0I6x1RMzZ57zYkk85uOCG3ZLPll4V6R1WvLsNnWwc8xx7Gmga6qMmSFQNQ6gIjSpZsG Date: 27 May 2014 18:17:47 -0000 Message-ID: <20140527181747.10464.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/qkzRQVVoPa8Pae5vywh-ufx1SxI 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: Tue, 27 May 2014 18:18:17 -0000 >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. We've made no progress on the lawn-compatible boostrap, so we probably will need to see where we are. From nobody Wed May 28 07:03: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 03FBE1A0125 for ; Wed, 28 May 2014 07:03:42 -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 5Hj09u67MQLu for ; Wed, 28 May 2014 07:03:40 -0700 (PDT) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 1DEA11A09A2 for ; Wed, 28 May 2014 07:03:40 -0700 (PDT) Received: by smtp2.arin.net (Postfix, from userid 323) id 8E65D213666; Wed, 28 May 2014 10:03:36 -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 DA91F21365F; Wed, 28 May 2014 10:03:35 -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, 28 May 2014 10:03:35 -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, 28 May 2014 10:03:35 -0400 From: Andy Newton To: "Murray S. Kucherawy" Thread-Topic: [weirds] IETF 90 scheduling Thread-Index: AQHPebgCra/esIiU30yYU+NZW9yNXJtWStmA Date: Wed, 28 May 2014 14:03:34 +0000 Message-ID: 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: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/3amLjul7l-CmPNJfk0nDgDiORDk 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: Wed, 28 May 2014 14:03:42 -0000 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 wro= te: > Colleagues, >=20 > 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. >=20 > 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. >=20 > 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. >=20 > 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. >=20 > -MSK, WEIRDS co-chair > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds From nobody Sat May 31 08:01: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 D79061A08E9 for ; Sat, 31 May 2014 08:01:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.552 X-Spam-Level: X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 TRYg9LosyPCy for ; Sat, 31 May 2014 08:01:06 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id B094E1A08DD for ; Sat, 31 May 2014 08:01:06 -0700 (PDT) Received: from [10.122.188.243] (66-46-89-74.dedicated.allstream.net [66.46.89.74]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B283A40371 for ; Sat, 31 May 2014 11:01:01 -0400 (EDT) From: Marc Blanchet Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Message-Id: <79DE5F32-00CB-4AB9-8B99-121AB2412B32@viagenie.ca> Date: Sat, 31 May 2014 11:01:00 -0400 To: "" 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/Nn87kERrVfU79rSw1khQPTVqbX0 Subject: [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: Sat, 31 May 2014 15:01:09 -0000 Hello, I've been working on the new version of the bootstrap draft. Given the = new wg direction, it becomes a pretty important rewrite. I'm currently = finishing the text around the new "design", but wanted to have some = input from the wg about the design direction. So here is some = considerations and then actual code example, for your review. - separate registries for each realm (domain, ipv4, ipv6, autnum), since = the registration policies are most likely going to be different, and = that clients may only need to look at a specific registry (clients for = ip addresses don't need to fetch the 2500+ domains...) - however, from a protocol point of view (and therefore on the template = point of view), there are all using the same URI structure. Therefore, a = "global across rdap registries" default for the default template.=20 - tried to cover what could be the most common case as straightforward = as possible to ease clients, while providing flexibility for less common = cases - template below provide a way for a registry to specify which protocols = (http, https) are supported (via the protos array), while providing a = "global" default and a registry default. The global default would be = https given the IETF direction of everything encrypted, but leave the = registry the possibility to overwrite it, per tld/address block if = desired. - the {querypath} would land into the draft-ietf-weirds-rdap-query spec. - below are examples Please comment. Regards, Marc. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D IANA RDAP DEFAULTS REGISTRY =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=20 { "rdap.bootstrap": { "resources": [ "ip",=20 "autnum",=20 "domain",=20 "nameserver",=20 "entity",=20 "help",=20 "domains",=20 "nameservers",=20 "entities", ], =20 "defaults": { "query" : "{proto}://{host}/{prefix}/{querypath}", "prefix" : "rdap", "proto" : "https", "protos" : [ "https", "http" ], "host" : "example.com", }, },=20 } =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D IANA RDAP DOMAIN BOOTSTRAP REGISTRY =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D { =93rdap.bootstrap=94: { =93domain": { =93myexampletld.=94: { "host": "rdap.example.org", }, "myexample2tld.": { "host": "rdap.example.net", "protos": [ "http" ], "proto": [ "http" ], "prefix": "", }, }, }, } =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D IANA RDAP IPv4 BOOTSTRAP REGISTRY =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D { =93rdap.bootstrap=94: { =93ip4": { =933.0.0.0/8=94: { "host": "rdap.arin.net", "prefix": "rdap/ip4", }, }, }, } =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D IANA RDAP IPv6 BOOTSTRAP REGISTRY =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D { =93rdap.bootstrap=94: { =93ip6": { =932001:0200::/23=94: { "host": "apnic.net", "prefix": "rdap/ipv6" "protos": [ "https" ], "proto": [ "https" ], }, }, }, } =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D IANA RDAP AUTNUM BOOTSTRAP REGISTRY =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D { =93rdap.bootstrap=94: { =93autnum": { =9320116-20117=94: { "host": "rdap.lacnic.net", }, }, }, } From nobody Sat May 31 09:53: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 CF63E1A0026 for ; Sat, 31 May 2014 09:52:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.762 X-Spam-Level: X-Spam-Status: No, score=0.762 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] 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 M-xCnsgaIJfK for ; Sat, 31 May 2014 09:52:58 -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 7B6771A0016 for ; Sat, 31 May 2014 09:52:58 -0700 (PDT) Received: (qmail 9739 invoked from network); 31 May 2014 16:52:49 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 31 May 2014 16:52:49 -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=5ff0.538a08e1.k1405; i=johnl@user.iecc.com; bh=uFEQ0rKr4EgtYcLqo4Dm9FNqR56nL2P83HROdYg8Eyc=; b=eoOgsojMA9+VYLpoH2am3Mt4IIY3NKHznVTwJPNXQ5KM/DcEj04Ip4vzBXzT+SU/u9whi1LVC6/KpEonN09gQfxXZMrdy0y+730D/PKG2K+b3RamB6XFYIl4+3uWhDehfbiSQSP+4wDtJ1AYufMC4zV4j9pSDeroWRFKygtUo94UPcTnzjBLN3QR7I6so6srSfDi6tUeKC4yFGZE/UX8vGSOs/UqW8YxIm5bbO52aljtmCkjwwleKw0fcz4s1jWj 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=5ff0.538a08e1.k1405; olt=johnl@user.iecc.com; bh=uFEQ0rKr4EgtYcLqo4Dm9FNqR56nL2P83HROdYg8Eyc=; b=A0Ik4dH8F+9kIxxorsnWKNo8oJswX49HQQzPbLUN7xElODzNtEa64CB/X1cuKO6wSV137t81WOP3LEgNCv3PQU83d8NoZlT23Fl8mXRqku/Ac1xUBeE+u2J6/qV2dYdpxPVksL/PQf6vJ9o0a9sqkgM+icii0V1GLB9VPSObi5omPkpI1usONUxV1zlO8sIs8M3fM3zmwAB8uZeYg6iTyDInljmHXVKUpj/pIroUEPa+KKIlcnlJvQHM+Iu992Y7 Date: 31 May 2014 16:52:26 -0000 Message-ID: <20140531165226.24559.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: <79DE5F32-00CB-4AB9-8B99-121AB2412B32@viagenie.ca> 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/cp2AqJAn-QUM5zg-mhpqKmqRdCE 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: Sat, 31 May 2014 16:53:00 -0000 Let's take a look. >{ > "rdap.bootstrap": { > "resources": [ > "ip", > "autnum", > "domain", > "nameserver", > "entity", > "help", > "domains", > "nameservers", > "entities", > ], What is the purpose of this list? What happens if it doesn't match the actual tags used in the rest of the file? > "defaults": { > "query" : "{proto}://{host}/{prefix}/{querypath}", > "prefix" : "rdap", Nit; I expect the most common prefix will be null, in which case this puts a double slash in the path. Also, can you suggest a plausible scenario in which the query would be something other than this? Bootstraps are supposed to be minimal, so I would prefer not to include features just in case someone might think of a use case later. If it's a fixed query, we can say as a special case that a null prefix doesn't have a slash after it. > "proto" : "https", > "protos" : [ "https", "http" ], A JSON array is ordered, so why not just say you try the protos in order? That also avoids the undefined case where the proto isn't in the protos. >{ > “rdap.bootstrap”: { > “autnum": { > “20116-20117”: { > "host": "rdap.lacnic.net", > }, > }, > }, >} This requires that clients parse the label to see if it matches, and since you don't know what the ranges are, the client has to iterate over the whole object and try them all. Since you have to iterate anyway, how about making it an array with the numbers as numbers? >{ > “rdap.bootstrap”: { > “autnum": [ [ "minasn": 20116, "maxasn": 20117, "host": "rdap.lacnic.net", ], [ "minasn": 261, "maxasn": 261, "host": "rdap.ripe.net", ], > ], > }, > }, For all of the domains and IPs, is the plan to use the first one that matches, or read the whole thing and take the longest match? Note that those could be equivalent if it were an array sorted in an appropriate order. R's, John From nobody Sat May 31 12:29:29 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 D643B1A007F for ; Sat, 31 May 2014 12:29:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.148 X-Spam-Level: X-Spam-Status: No, score=0.148 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 trKmCa7sg8bp for ; Sat, 31 May 2014 12:29: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 E75D51A0073 for ; Sat, 31 May 2014 12:29:24 -0700 (PDT) Received: from [192.168.1.101] (modemcable060.86-160-184.mc.videotron.ca [184.160.86.60]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E15C0403C2; Sat, 31 May 2014 15:29:19 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) From: Marc Blanchet In-Reply-To: <20140531165226.24559.qmail@joyce.lan> Date: Sat, 31 May 2014 15:29:19 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140531165226.24559.qmail@joyce.lan> To: John Levine X-Mailer: Apple Mail (2.1878.2) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/2e8SVp6F6ng1zJmea_lu-KeYSmk Cc: weirds@ietf.org 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: Sat, 31 May 2014 19:29:27 -0000 Le 2014-05-31 =C3=A0 12:52, John Levine a =C3=A9crit : > Let's take a look. >=20 >> { >> "rdap.bootstrap": { >> "resources": [ >> "ip",=20 >> "autnum",=20 >> "domain",=20 >> "nameserver",=20 >> "entity",=20 >> "help",=20 >> "domains",=20 >> "nameservers",=20 >> "entities", >> ], >=20 > What is the purpose of this list? see ticket #26. > What happens if it doesn't match > the actual tags used in the rest of the file? >=20 >> "defaults": { >> "query" : "{proto}://{host}/{prefix}/{querypath}", >> "prefix" : "rdap", >=20 > Nit; I expect the most common prefix will be null, in which case this > puts a double slash in the path. =20 good point. >=20 > Also, can you suggest a plausible scenario in which the query would be > something other than this? I'm not sure I understand your question. anyway. > Bootstraps are supposed to be minimal, so > I would prefer not to include features just in case someone might > think of a use case later. If it's a fixed query, we can say as a > special case that a null prefix doesn't have a slash after it. To avoid the double slash and simplify, we could reduce the template to: "query" : "{proto}://{prefix}/{querypath}", where prefix could be either: host.example.com or = host.example.com/rdap. Separating the host part may be interesting. The other way would be to force at registration (by IANA checking) that = the prefix (from the initial proposal) must have a "/" and then = concatenating the two without a "/", such as {prefix}{querypath}. tradeoffs. >=20 >> "proto" : "https", >> "protos" : [ "https", "http" ], >=20 > A JSON array is ordered, so why not just say you try the protos in > order? That also avoids the undefined case where the proto isn't in > the protos. right. I know. I thought it would be more straight forward for clients = for the basic cases. It is a tradeoff. >=20 >> { >> =EF=BF=BDrdap.bootstrap=EF=BF=BD: { >> =EF=BF=BDautnum": { >> =EF=BF=BD20116-20117=EF=BF=BD: { >> "host": "rdap.lacnic.net", >> }, >> }, >> }, >> } >=20 > This requires that clients parse the label to see if it matches, and > since you don't know what the ranges are, the client has to iterate > over the whole object and try them all. Since you have to iterate > anyway, how about making it an array with the numbers as numbers? - this is nothing new here from the previous bootstrap documents. We = said before that the AS ranges were possible.=20 - so if I understand you well, for the legacy AS numbers, that would = mean a 65K array expanding to a 4G array when including 4bytes AS = numbers. really want to do that? The current space is not super = compressed but still. My take is that a client can easily parse this. = Moreover, if the ranges are ordered (which is expected as all IANA = registries containing numbers are and as the current AS registry is, = then the client does not have to iterate through the whole thing. it = stops when the range is the right one. >=20 >> { >> =EF=BF=BDrdap.bootstrap=EF=BF=BD: { >> =EF=BF=BDautnum": [ > [ > "minasn": 20116, > "maxasn": 20117, > "host": "rdap.lacnic.net", > ], Is this your proposal? an array of 3 different objects? looks strange to = me. I'm not sure I understand your proposal. I think this is invalid JSON syntax.=20 > [ > "minasn": 261, > "maxasn": 261, > "host": "rdap.ripe.net", > ], >> ], >> }, >> }, >=20 > For all of the domains and IPs, is the plan to use the first one that > matches, or read the whole thing and take the longest match? in the current versions of the bootstrap documents, one can read that we = have been stating longest match. We don't want to constraint the = allocations to be of fixed sizes. > Note > that those could be equivalent if it were an array sorted in an > appropriate order. >=20 > R's, > John From nobody Sat May 31 19:00: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 0421E1A015C for ; Sat, 31 May 2014 19:00:42 -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 MlgMXZ5qEdPp for ; Sat, 31 May 2014 19:00: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 92D8B1A015A for ; Sat, 31 May 2014 19:00:38 -0700 (PDT) Received: (qmail 93746 invoked from network); 1 Jun 2014 02:00:33 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=16e30.538a8941.k1405; bh=6a14NHx6Imxq8yOEdzPaFBywdbksvHEC7Ydl1R7iaXc=; b=J6Ue4Lo+pw+rEGO7bHB1ApG5iJGGazRDKep+c9B22T+VQsjNbArF1tcJeEL0OpkJudJz3pFg3NpDWw55Cbj4Ei9eke/RGX1kBOZ/z+ZQzKvn4SRDODeG0JftcxG4ilJ/bbGCbZFsPGXCMp9Iz4ON1QA8kPT5mI5mcRZUXag2LxofiPJpPyGm5Qql+tLLh7UW+3Wo3Egx1SItw/8SctkxxYxFd18zkwuIcFwIW9j+bhlnnklBF8LsYxvd4uk3f1/9 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=16e30.538a8941.k1405; bh=6a14NHx6Imxq8yOEdzPaFBywdbksvHEC7Ydl1R7iaXc=; b=ywAZ0ANxrcm1hDve3YLcBDoTvoVsaYq/Jchr+7C6jgkhtyOsScFyrSsZ0VfFXLmpH1BXusHJHVn0oV++N5IZWdVqdbG18h35qu8fZsbzwU35s/RDrPLHaW+/pgf7GWpj6YkdD8SfIvonx4Ik7LgfItRM9prbt+/j6RaGPyTHpgiytGHelDSH77rFtljmEtlDcQynbFr+ZPfSMbzgsek4KiR4/y8Bl//9qEgZVg54Ygy9U8njNp0nWtp31JlTXfOy Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 01 Jun 2014 02:00:32 -0000 Date: 31 May 2014 22:00:32 -0400 Message-ID: From: "John R Levine" To: "Marc Blanchet" In-Reply-To: References: <20140531165226.24559.qmail@joyce.lan> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Cleverness: None detected MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/Sqq3rkXuHGnF9gUWK2V8WolyH50 Cc: weirds@ietf.org 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: Sun, 01 Jun 2014 02:00:44 -0000 >> Let's take a look. >> >>> { >>> "rdap.bootstrap": { >>> "resources": [ >>> "ip", >>> "autnum", >>> "domain", >>> "nameserver", >>> "entity", >>> "help", >>> "domains", >>> "nameservers", >>> "entities", >>> ], >> >> What is the purpose of this list? > > see ticket #26. I see that it wants an IANA registry, to avoid collsions and multiple names for the same thing, but I don't see why it'd be put into the downloaded bootstrap. >> Also, can you suggest a plausible scenario in which the query would be >> something other than this? > > I'm not sure I understand your question. anyway. > "query" : "{proto}://{host}/{prefix}/{querypath}", Given that we have parameters for proto, host, prefix, and query path, is there a plausible circumstance in which they would be assembled in any other way than that? I don't immediately see one. >>> "proto" : "https", >>> "protos" : [ "https", "http" ], >> >> A JSON array is ordered, so why not just say you try the protos in >> order? That also avoids the undefined case where the proto isn't in >> the protos. > > right. I know. I thought it would be more straight forward for clients > for the basic cases. It is a tradeoff. It's hard to see a lot of difference between the code for proto and for protos[0]. >>> { >>> "rdap.bootstrap": { >>> "autnum": [ >> { >> "minasn": 20116, >> "maxasn": 20117, >> "host": "rdap.lacnic.net", >> }, >> { >> "minasn": 261, >> "maxasn": 261, >> "host": "rdap.ripe.net", >> }, >>> ], > > Is this your proposal? an array of 3 different objects? looks strange to me. I'm not sure I understand your proposal. > I think this is invalid JSON syntax. Sorry, it's supposed to be an array of objects, each of which describes a range of ASNs assigned to a registry. Regards, John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail.