From peter@denic.de Sun Feb 2 05:25: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 7A3611A00D2 for ; Sun, 2 Feb 2014 05:25:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.586 X-Spam-Level: X-Spam-Status: No, score=-1.586 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.535] 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 9SswKbLjZ-MC for ; Sun, 2 Feb 2014 05:25:11 -0800 (PST) Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::3]) by ietfa.amsl.com (Postfix) with ESMTP id 1E6CE1A00D1 for ; Sun, 2 Feb 2014 05:25:10 -0800 (PST) Received: from x27.adm.denic.de (x28.fra2.if.denic.de [10.122.64.17]) by office.denic.de with esmtp id 1W9x2n-0007Sx-7P; Sun, 02 Feb 2014 14:25:05 +0100 Received: from localhost by x27.adm.denic.de with local id 1W9x2n-0000pZ-3S; Sun, 02 Feb 2014 14:25:05 +0100 Date: Sun, 2 Feb 2014 14:25:05 +0100 From: Peter Koch To: weirds@ietf.org Message-ID: <20140202132505.GD22148@x28.adm.denic.de> Mail-Followup-To: weirds@ietf.org References: <20140131131752.GD11869@mx1.yitter.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Sender: Peter Koch Subject: Re: [weirds] Question: Nameserver data looked up by IP address 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, 02 Feb 2014 13:25:13 -0000 On Fri, Jan 31, 2014 at 04:45:21PM +0000, Andy Newton wrote: > >I suppose, but it's a little strange. NS records only contain names, > >and an IP address might be the A/AAAA RDATA at several names. How > >would you know which nameserver you were talking about? > > I agree. This more like a search than a lookup. indeed, therefore it should be optional - at most. Many queries of this kind would result in multiple (sometimes even "many") objects being returned. -Peter From kambe@jprs.co.jp Sun Feb 2 21:05:25 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 D93431A0145 for ; Sun, 2 Feb 2014 21:05:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.773 X-Spam-Level: ** X-Spam-Status: No, score=2.773 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.535, 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 k5cPHgp2RBf3 for ; Sun, 2 Feb 2014 21:05:25 -0800 (PST) Received: from off-send01.tyo.jprs.co.jp (off-send01.tyo.jprs.co.jp [IPv6:2001:df0:8:17::10]) by ietfa.amsl.com (Postfix) with ESMTP id BED361A00F4 for ; Sun, 2 Feb 2014 21:05:24 -0800 (PST) Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send01.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id s13551Kx000593 for ; Mon, 3 Feb 2014 14:05:19 +0900 X-AuditID: ac120820-b7f196d00000167f-e7-52ef238fbaa8 Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id 5C.BE.05759.F832FE25; Mon, 3 Feb 2014 14:05:19 +0900 (JST) Date: Mon, 03 Feb 2014 14:03:47 +0900 (JST) Message-Id: <20140203.140347.229731469.kambe@jprs.co.jp> To: weirds@ietf.org From: Naoki Kambe In-Reply-To: <20140131.144009.59661735.kambe@jprs.co.jp> References: <20140131.144009.59661735.kambe@jprs.co.jp> 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+NgFjrOIsWRmVeSWpSXmKPExsWyRoiFT7df+X2QwemXhhbzu46zODB6LFny kymAMYrLJiU1J7MstUjfLoEro2HnNZaCS8wVty99ZmxgfMTUxcjJISFgIrFg9ip2CFtM4sK9 9WxdjFwcQgInGSUurJrO2MXIwcEioC1x52cSSA2vgIXEnu1tYL0iAsISi1++YwEpERZwl9i9 RB8kzCagIrHs3mawEk6g8js7nrOC2EIC5hIvbraxg5TzC+hLTG1KgdhqJ9H0F2IKr4CgxN8d wiBhZgEtiZ4Zj9khbHmJ7W/nME9g5J+FUDULSdUsJFULGJlXMcrkp6XpFqfmpRTnphsY6pVU 5utlFRQV6yWD6E2M4HDjUNjBOOOUwSFGAQ5GJR5epuPvgoRYE8uKK3MPMUpyMCmJ8qopvQ8S 4kvKT6nMSCzOiC8qzUktPsQowcGsJMLbLQCU401JrKxKLcqHSUlzsCiJ8x7/cyZQSCA9sSQ1 OzW1ILUIJivDwaEkwftLEahRsCg1PbUiLTOnBCHNxMEJMpwHaLgYyGLe4oLE3OLMdIj8KUZJ KXHevyDNAiCJjNI8uN5XjOJALwjzPgTJ8gBTB1zXK6CBTEADew68BhlYkoiQkmpg3PszcvMa 95Ycvdrl+skcu29VSqtOlVy3/TNHxtF+nS3y7d8f9FRO3labm9htVrhdU3+LnlHwxBNaigf5 m7aqWsrxi859EOJpprb0YqbZgqmihevDr21cY5sifPHmj4mnCyMcys8Hf/ntXpZ3cbbcn3Kp 1Q9j6z52PXE5v0HQ5Jhbv9rrc6GnlViKMxINtZiLihMBVFS84toCAAA= Subject: Re: [weirds] Question: Nameserver data looked up by IP address 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, 03 Feb 2014 05:05:26 -0000 Thank you for answering my question. I currently understand like the followings: - How to look up nameserver data by an IP address is not currently supported on the current RDAP I-Ds. - If we do, we have to consider a new case returning multiple nameserver objects which would match the specific IP address. Because there might be the multiple server names assigned to one IP address on the DNR repository. Regards, Naoki Kambe From shollenbeck@verisign.com Mon Feb 3 10:51:16 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 106CC1A016D for ; Mon, 3 Feb 2014 10:51:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.702 X-Spam-Level: X-Spam-Status: No, score=-3.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, 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 OjCNcNzkJenW for ; Mon, 3 Feb 2014 10:51:14 -0800 (PST) Received: from exprod6og125.obsmtp.com (exprod6og125.obsmtp.com [64.18.1.218]) by ietfa.amsl.com (Postfix) with ESMTP id A9D271A01AD for ; Mon, 3 Feb 2014 10:51:12 -0800 (PST) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob125.postini.com ([64.18.5.12]) with SMTP ID DSNKUu/lIJAueAulV4h0v/6wWPHKLP+iY9Eu@postini.com; Mon, 03 Feb 2014 10:51:14 PST Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id s13IpBQN024959 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 3 Feb 2014 13:51:11 -0500 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Mon, 3 Feb 2014 13:51:11 -0500 From: "Hollenbeck, Scott" To: Andy Newton , Andrew Sullivan , "weirds@ietf.org" Thread-Topic: [weirds] Question: Nameserver data looked up by IP address Thread-Index: AQHPHkda+NJyATz2I0Gvqq07a9IVOpqeyptAgABaWACAADn4gIAEgalw Date: Mon, 3 Feb 2014 18:51:11 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F4933E539@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <20140131131752.GD11869@mx1.yitter.info> 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="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] Question: Nameserver data looked up by IP address 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, 03 Feb 2014 18:51:16 -0000 > -----Original Message----- > From: weirds [mailto:weirds-bounces@ietf.org] On Behalf Of Andy Newton > Sent: Friday, January 31, 2014 11:45 AM > To: Andrew Sullivan; weirds@ietf.org > Subject: Re: [weirds] Question: Nameserver data looked up by IP address >=20 > On 1/31/14 8:17 AM, "Andrew Sullivan" wrote: >=20 > >On Fri, Jan 31, 2014 at 01:06:26PM +0000, Hollenbeck, Scott wrote: > >k about adding it, though. Should we? It doesn't seem unreasonable. > >Examples: > >> > >> nameserver/192.0.2.0 > >> nameserver/2001:db8::0 > > > >I suppose, but it's a little strange. NS records only contain names, > >and an IP address might be the A/AAAA RDATA at several names. How > >would you know which nameserver you were talking about? >=20 > I agree. This more like a search than a lookup. >=20 > If we want to support this, it should be /nameservers?ip=3DX where X is > either an IPv4 or IPv6 address. Does anyone have any issues with adding this as a search option? Should thi= s be interpreted as "search for domain names delegated to a server at this = address" or "search for name server names that resolve to this address"? Scott From andy@arin.net Mon Feb 3 11:05:05 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59E7C1A01F8 for ; Mon, 3 Feb 2014 11:05:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.936 X-Spam-Level: X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, RP_MATCHES_RCVD=-0.535] 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 dLEEWO8YGkKH for ; Mon, 3 Feb 2014 11:05:02 -0800 (PST) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id BE3741A01CA for ; Mon, 3 Feb 2014 11:05:02 -0800 (PST) Received: by smtp2.arin.net (Postfix, from userid 323) id B8C032134EA; Mon, 3 Feb 2014 14:05:02 -0500 (EST) Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id 412D0213618; Mon, 3 Feb 2014 14:05:02 -0500 (EST) Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.342.3; Mon, 3 Feb 2014 14:05:02 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.174]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0347.000; Mon, 3 Feb 2014 14:05:01 -0500 From: Andy Newton To: "Hollenbeck, Scott" , Andrew Sullivan , "weirds@ietf.org" Thread-Topic: [weirds] Question: Nameserver data looked up by IP address Thread-Index: AQHPHkdd4s5XDGGdZkaFe1AKjNMPmpqfIcEAgAADMgD//+YjAIAFLfyA//+wB4A= Date: Mon, 3 Feb 2014 19:05:00 +0000 Message-ID: In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4933E539@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] Content-Type: text/plain; charset="us-ascii" Content-ID: <522467751A98A7469FF0FFFC191831D6@corp.arin.net> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] Question: Nameserver data looked up by IP address 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, 03 Feb 2014 19:05:05 -0000 On 2/3/14 1:51 PM, "Hollenbeck, Scott" wrote: >Does anyone have any issues with adding this as a search option? Should >this be interpreted as "search for domain names delegated to a server at >this address" or "search for name server names that resolve to this >address"? I have no problem adding the latter. The former does seem useful, but if it is currently not a requirement then it can be added later. -andy From shollenbeck@verisign.com Mon Feb 3 11:24:39 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 D2CBE1A0162 for ; Mon, 3 Feb 2014 11:24:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.702 X-Spam-Level: X-Spam-Status: No, score=-3.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, 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 wIFJqyirbWjD for ; Mon, 3 Feb 2014 11:24:37 -0800 (PST) Received: from exprod6og108.obsmtp.com (exprod6og108.obsmtp.com [64.18.1.21]) by ietfa.amsl.com (Postfix) with ESMTP id 699301A010F for ; Mon, 3 Feb 2014 11:24:35 -0800 (PST) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob108.postini.com ([64.18.5.12]) with SMTP ID DSNKUu/s879fMzsY20dwpJhDMEkZLk0Nu5At@postini.com; Mon, 03 Feb 2014 11:24:37 PST Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s13JOYdv026987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 3 Feb 2014 14:24:34 -0500 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Mon, 3 Feb 2014 14:24:34 -0500 From: "Hollenbeck, Scott" To: Andy Newton , Andrew Sullivan , "weirds@ietf.org" Thread-Topic: [weirds] Question: Nameserver data looked up by IP address Thread-Index: AQHPHkda+NJyATz2I0Gvqq07a9IVOpqeyptAgABaWACAADn4gIAEgalwgABcWgD//62ZUA== Date: Mon, 3 Feb 2014 19:24:32 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F4933E628@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <831693C2CDA2E849A7D7A712B24E257F4933E539@BRN1WNEXMBX01.vcorp.ad.vrsn.com> 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="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] Question: Nameserver data looked up by IP address 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, 03 Feb 2014 19:24:39 -0000 > -----Original Message----- > From: Andy Newton [mailto:andy@arin.net] > Sent: Monday, February 03, 2014 2:05 PM > To: Hollenbeck, Scott; Andrew Sullivan; weirds@ietf.org > Subject: Re: [weirds] Question: Nameserver data looked up by IP address >=20 > On 2/3/14 1:51 PM, "Hollenbeck, Scott" > wrote: >=20 > >Does anyone have any issues with adding this as a search option? > Should > >this be interpreted as "search for domain names delegated to a server > >at this address" or "search for name server names that resolve to this > >address"? >=20 > I have no problem adding the latter. The former does seem useful, but > if it is currently not a requirement then it can be added later. I just read through one of the new ICANN registry agreements to see what th= e text actually says. Unfortunately, it does not specifically describe the = response to a name server query by IP address. Here's an example from the .= beer TLD agreement (http://www.icann.org/sites/default/files/tlds/beer/beer= -agmt-html-09jan14-en.htm): 1.7. Nameserver Data: 1.7.1 Query format: whois "NS1.EXAMPLE.TLD", whois "nameserver (nameserver= name)", or whois "nameserver (IP Address)" 1.7.2 Response format: Server Name: NS1.EXAMPLE.TLD=20 IP Address: 192.0.2.123=20 IP Address: 2001:0DB8::1=20 Registrar: Example Registrar, Inc. WHOIS Server: whois.example-registrar.tld=20 Referral URL: http://www.example-registrar.tld=20 >>> Last update of WHOIS database: 2009-05-29T20:15:00Z <<< This response looks like an answer to the latter question. The text does sa= y that "The fields specified below set forth the minimum output requirement= s. Registry Operator may output data fields in addition to those specified= below, subject to approval by ICANN, which approval shall not be unreasona= bly withheld" - which appears to be consistent with Andy's suggestion. We c= ould do "search for name server names that resolve to this address" (to hel= p people meet the requirement) and leave "search for domain names delegated= to a server at this address" for "in addition to those specified". Scott From andy@arin.net Mon Feb 3 12:58:16 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 444AF1A01DA for ; Mon, 3 Feb 2014 12:58:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.936 X-Spam-Level: X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, RP_MATCHES_RCVD=-0.535] 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 8H8R0_tgz20H for ; Mon, 3 Feb 2014 12:58:15 -0800 (PST) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 5B1801A015A for ; Mon, 3 Feb 2014 12:58:15 -0800 (PST) Received: by smtp2.arin.net (Postfix, from userid 323) id 4F832213640; Mon, 3 Feb 2014 15:58:15 -0500 (EST) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp2.arin.net (Postfix) with ESMTP id BB259213625; Mon, 3 Feb 2014 15:58:14 -0500 (EST) Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.342.3; Mon, 3 Feb 2014 15:58:14 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.174]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0347.000; Mon, 3 Feb 2014 15:57:58 -0500 From: Andy Newton To: "Hollenbeck, Scott" , Andrew Sullivan , "weirds@ietf.org" Thread-Topic: [weirds] Question: Nameserver data looked up by IP address Thread-Index: AQHPHkdd4s5XDGGdZkaFe1AKjNMPmpqfIcEAgAADMgD//+YjAIAFLfyA//+wB4CAAFlLAP//xkWA Date: Mon, 3 Feb 2014 20:57:58 +0000 Message-ID: In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4933E628@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] Content-Type: text/plain; charset="us-ascii" Content-ID: <1EB36379927BD24393CF5AB9D84EA563@corp.arin.net> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] Question: Nameserver data looked up by IP address 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, 03 Feb 2014 20:58:16 -0000 On 2/3/14 2:24 PM, "Hollenbeck, Scott" wrote: >This response looks like an answer to the latter question. The text does >say that "The fields specified below set forth the minimum output >requirements. Registry Operator may output data fields in addition to >those specified below, subject to approval by ICANN, which approval shall >not be unreasonably withheld" - which appears to be consistent with >Andy's suggestion. We could do "search for name server names that resolve >to this address" (to help people meet the requirement) and leave "search >for domain names delegated to a server at this address" for "in addition >to those specified". This seems reasonable to me. -andy From amikkelsen@verisign.com Tue Feb 4 01:08:05 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 575C21A03A1 for ; Tue, 4 Feb 2014 01:08:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.702 X-Spam-Level: X-Spam-Status: No, score=-3.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, 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 bCcJEn-fbNeS for ; Tue, 4 Feb 2014 01:08:02 -0800 (PST) Received: from exprod6og114.obsmtp.com (exprod6og114.obsmtp.com [64.18.1.33]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD2B1A039E for ; Tue, 4 Feb 2014 01:08:00 -0800 (PST) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob114.postini.com ([64.18.5.12]) with SMTP ID DSNKUvCt8CE7BjUG6XHTs6Bu2ez+SI3h7F+a@postini.com; Tue, 04 Feb 2014 01:08:02 PST Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s1497xHR021395 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 4 Feb 2014 04:07:59 -0500 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Tue, 4 Feb 2014 04:07:59 -0500 From: "Mikkelsen, Asbjorn" To: "Hollenbeck, Scott" , Andy Newton , Andrew Sullivan , "weirds@ietf.org" Thread-Topic: [weirds] Question: Nameserver data looked up by IP address Thread-Index: AQHPHkda82lARMoRNk+HS4K1UmkZF5qfIcEAgAADMgCAADn4gIAE2ieAgAAD3ACAAAV2AIAAkA0A Date: Tue, 4 Feb 2014 09:07:58 +0000 Message-ID: References: <831693C2CDA2E849A7D7A712B24E257F4933E539@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F4933E628@BRN1WNEXMBX01.vcorp.ad.vrsn.com> In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4933E628@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.173.152.4] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] Question: Nameserver data looked up by IP address 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, 04 Feb 2014 09:08:05 -0000 The DotName ICANN agreement includes language about IP-address lookups: "Nameserver ("nameserver"): Search only by nameserver objects. The input st= ring is searched in the nameserver field or the IP address field." ( http://www.icann.org/en/about/agreements/registries/name/appendix-05-01de= c12-en.htm ) If you go to http://whois.nic.name and do a NAMESERVER lookup for 8.8.8.8 i= t returns the out-of-zone name server with name "8.8.8.8" and two in-zone n= ame servers with the associated IP-address "8.8.8.8": Name Server ID: 2473998_HOST_NAME-VRSN Name Server Name: 8.8.8.8 Name Server Status: ok Name Server Registrar ID: 69_REGISTRAR_NAME-VRSN Name Server Registrar: Tucows Domains Inc. Created On: 2013-10-03T07:51:09Z Updated On: 2013-10-03T07:51:09Z Name Server ID: 1918975_HOST_NAME-VRSN Name Server Name: 0.MICHAEL.KROPAT.NAME Name Server Status: ok IP Address Associated: 8.8.8.8 IP Address Associated: 66.220.0.213 Name Server Registrar ID: 5235_REGISTRAR_NAME-VRSN Name Server Registrar: Dynamic Network Services, Inc Created On: 2010-11-21T22:51:38Z Updated On: 2010-11-21T22:52:18Z Name Server ID: 2442158_HOST_NAME-VRSN Name Server Name: N.T4K.NAME Name Server Status: ok IP Address Associated: 8.8.8.8 Name Server Registrar ID: 74_REGISTRAR_NAME-VRSN Name Server Registrar: Online SAS Created On: 2013-07-24T03:34:38Z Updated On: 2013-07-24T03:34:38Z Regards, Asbjorn -----Original Message----- From: weirds [mailto:weirds-bounces@ietf.org] On Behalf Of Hollenbeck, Scot= t Sent: Monday, February 03, 2014 20:25 To: Andy Newton; Andrew Sullivan; weirds@ietf.org Subject: Re: [weirds] Question: Nameserver data looked up by IP address > -----Original Message----- > From: Andy Newton [mailto:andy@arin.net] > Sent: Monday, February 03, 2014 2:05 PM > To: Hollenbeck, Scott; Andrew Sullivan; weirds@ietf.org > Subject: Re: [weirds] Question: Nameserver data looked up by IP address >=20 > On 2/3/14 1:51 PM, "Hollenbeck, Scott" > wrote: >=20 > >Does anyone have any issues with adding this as a search option? > Should > >this be interpreted as "search for domain names delegated to a server > >at this address" or "search for name server names that resolve to this > >address"? >=20 > I have no problem adding the latter. The former does seem useful, but > if it is currently not a requirement then it can be added later. I just read through one of the new ICANN registry agreements to see what th= e text actually says. Unfortunately, it does not specifically describe the = response to a name server query by IP address. Here's an example from the .= beer TLD agreement (http://www.icann.org/sites/default/files/tlds/beer/beer= -agmt-html-09jan14-en.htm): 1.7. Nameserver Data: 1.7.1 Query format: whois "NS1.EXAMPLE.TLD", whois "nameserver (nameserver= name)", or whois "nameserver (IP Address)" 1.7.2 Response format: Server Name: NS1.EXAMPLE.TLD=20 IP Address: 192.0.2.123=20 IP Address: 2001:0DB8::1=20 Registrar: Example Registrar, Inc. WHOIS Server: whois.example-registrar.tld=20 Referral URL: http://www.example-registrar.tld=20 >>> Last update of WHOIS database: 2009-05-29T20:15:00Z <<< This response looks like an answer to the latter question. The text does sa= y that "The fields specified below set forth the minimum output requirement= s. Registry Operator may output data fields in addition to those specified= below, subject to approval by ICANN, which approval shall not be unreasona= bly withheld" - which appears to be consistent with Andy's suggestion. We c= ould do "search for name server names that resolve to this address" (to hel= p people meet the requirement) and leave "search for domain names delegated= to a server at this address" for "in addition to those specified". Scott _______________________________________________ weirds mailing list weirds@ietf.org https://www.ietf.org/mailman/listinfo/weirds From internet-drafts@ietf.org Tue Feb 4 05:13: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 C23601A041F; Tue, 4 Feb 2014 05:13:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TXfXYsN1mJyw; Tue, 4 Feb 2014 05:13:30 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF761A042A; Tue, 4 Feb 2014 05:13:29 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140204131329.17500.22686.idtracker@ietfa.amsl.com> Date: Tue, 04 Feb 2014 05:13:29 -0800 Cc: weirds@ietf.org Subject: [weirds] I-D Action: draft-ietf-weirds-rdap-query-10.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 13:13:32 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web Extensible Internet Registration Data Service Working Group of the IETF. Title : Registration Data Access Protocol Query Format Authors : Andrew Lee Newton Scott Hollenbeck Filename : draft-ietf-weirds-rdap-query-10.txt Pages : 17 Date : 2014-02-04 Abstract: This document describes uniform patterns to construct HTTP URLs that may be used to retrieve registration information from registries (including both Regional Internet Registries (RIRs) and Domain Name Registries (DNRs)) using "RESTful" web access patterns. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-weirds-rdap-query/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-weirds-rdap-query-10 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-weirds-rdap-query-10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From shollenbeck@verisign.com Tue Feb 4 05:15: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 ADC4C1A042A for ; Tue, 4 Feb 2014 05:15:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.702 X-Spam-Level: X-Spam-Status: No, score=-3.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, 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 Em4o4PyNGpdG for ; Tue, 4 Feb 2014 05:15:39 -0800 (PST) Received: from exprod6og104.obsmtp.com (exprod6og104.obsmtp.com [64.18.1.187]) by ietfa.amsl.com (Postfix) with ESMTP id F36851A0429 for ; Tue, 4 Feb 2014 05:15:38 -0800 (PST) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob104.postini.com ([64.18.5.12]) with SMTP ID DSNKUvDn+v8hhGmyjpWZbaGn9Hfyb1hqs6gz@postini.com; Tue, 04 Feb 2014 05:15:39 PST Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id s14DFcF7007160 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 4 Feb 2014 08:15:38 -0500 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Tue, 4 Feb 2014 08:15:37 -0500 From: "Hollenbeck, Scott" To: "weirds@ietf.org" Thread-Topic: [weirds] Question: Nameserver data looked up by IP address Thread-Index: AQHPHkdd+NJyATz2I0Gvqq07a9IVOpqfIcEAgAADMgD//+YjAIAFLfyA//+wB4CAAFlLAP//xkWAACIdJXA= Date: Tue, 4 Feb 2014 13:15:37 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F4933EE5D@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <831693C2CDA2E849A7D7A712B24E257F4933E628@BRN1WNEXMBX01.vcorp.ad.vrsn.com> 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="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] Question: Nameserver data looked up by IP address 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, 04 Feb 2014 13:15:40 -0000 I just submitted rdap-query-10 with additional text to include name server = search by IP address. Scott From internet-drafts@ietf.org Tue Feb 4 08:36:30 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 4FB3C1A0215; Tue, 4 Feb 2014 08:36:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KoT3RgoYEexF; Tue, 4 Feb 2014 08:36:27 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C8061A0217; Tue, 4 Feb 2014 08:36:24 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140204163624.13921.83340.idtracker@ietfa.amsl.com> Date: Tue, 04 Feb 2014 08:36:24 -0800 Cc: weirds@ietf.org Subject: [weirds] I-D Action: draft-ietf-weirds-using-http-08.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 16:36:30 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web Extensible Internet Registration Data Service Working Group of the IETF. Title : HTTP usage in the Registration Data Access Protocol (RDAP) Authors : Andrew Lee Newton Byron J. Ellacott Ning Kong Filename : draft-ietf-weirds-using-http-08.txt Pages : 14 Date : 2014-02-04 Abstract: This document is one of a collection that together describe the Registration Data Access Protocol (RDAP). It describes how RDAP is transported using the Hypertext Transfer Protocol (HTTP). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-weirds-using-http/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-weirds-using-http-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-weirds-using-http-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From andy@arin.net Tue Feb 4 08:37:39 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 559C01A021A for ; Tue, 4 Feb 2014 08:37:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.936 X-Spam-Level: X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, RP_MATCHES_RCVD=-0.535] 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 tdLuNQfl_k86 for ; Tue, 4 Feb 2014 08:37:33 -0800 (PST) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id CB2AD1A0217 for ; Tue, 4 Feb 2014 08:37:33 -0800 (PST) Received: by smtp2.arin.net (Postfix, from userid 323) id 7CD8E213664; Tue, 4 Feb 2014 11:37:33 -0500 (EST) Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id 0114C21362B for ; Tue, 4 Feb 2014 11:37:33 -0500 (EST) 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, 4 Feb 2014 11:37:32 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.174]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0328.009; Tue, 4 Feb 2014 11:37:30 -0500 From: Andy Newton To: "weirds@ietf.org" Thread-Topic: New Version Notification for draft-ietf-weirds-using-http-08.txt Thread-Index: AQHPIcdF/zkSnRZBp0ewCf0IYw2FXpqlSzaA Date: Tue, 4 Feb 2014 16:37:29 +0000 Message-ID: In-Reply-To: <20140204163624.13921.25644.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] Content-Type: text/plain; charset="us-ascii" Content-ID: <9233004769F8FB499B9137FD9EFB23E5@corp.arin.net> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [weirds] FW: New Version Notification for draft-ietf-weirds-using-http-08.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, 04 Feb 2014 16:37:39 -0000 Simply a keep alive version. No need to panic. :) On 2/4/14 11:36 AM, "internet-drafts@ietf.org" wrote: > >A new version of I-D, draft-ietf-weirds-using-http-08.txt >has been successfully submitted by Andrew Lee Newton and posted to the >IETF repository. > >Name: draft-ietf-weirds-using-http >Revision: 08 >Title: HTTP usage in the Registration Data Access Protocol (RDAP) >Document date: 2014-02-04 >Group: weirds >Pages: 14 >URL: =20 >http://www.ietf.org/internet-drafts/draft-ietf-weirds-using-http-08.txt >Status: =20 >https://datatracker.ietf.org/doc/draft-ietf-weirds-using-http/ >Htmlized: http://tools.ietf.org/html/draft-ietf-weirds-using-http-08 >Diff: =20 >http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-weirds-using-http-08 > >Abstract: > This document is one of a collection that together describe the > Registration Data Access Protocol (RDAP). It describes how RDAP is > transported using the Hypertext Transfer Protocol (HTTP). > > =20 > =20 > > >Please note that it may take a couple of minutes from the time of >submission >until the htmlized version and diff are available at tools.ietf.org. > >The IETF Secretariat > > From kambe@jprs.co.jp Tue Feb 4 17:27:16 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 8731F1A0190 for ; Tue, 4 Feb 2014 17:27:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.572 X-Spam-Level: X-Spam-Status: No, score=0.572 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.535, 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 fGCqmz528dQm for ; Tue, 4 Feb 2014 17:27:15 -0800 (PST) Received: from off-send01.tyo.jprs.co.jp (off-send01.tyo.jprs.co.jp [IPv6:2001:df0:8:17::10]) by ietfa.amsl.com (Postfix) with ESMTP id 323AE1A016C for ; Tue, 4 Feb 2014 17:27:15 -0800 (PST) Received: from off-sendsmg01.tyo.jprs.co.jp (off-sendsmg01.tyo.jprs.co.jp [172.18.8.32]) by off-send01.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id s151RDxH018612 for ; Wed, 5 Feb 2014 10:27:14 +0900 X-AuditID: ac120820-b7f196d00000167f-df-52f19371b9f0 Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg01.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id C7.9B.05759.17391F25; Wed, 5 Feb 2014 10:27:13 +0900 (JST) Date: Wed, 05 Feb 2014 10:27:00 +0900 (JST) Message-Id: <20140205.102700.267973128.kambe@jprs.co.jp> To: weirds@ietf.org From: Naoki Kambe In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4933EE5D@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <831693C2CDA2E849A7D7A712B24E257F4933E628@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F4933EE5D@BRN1WNEXMBX01.vcorp.ad.vrsn.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+NgFjrOIsWRmVeSWpSXmKPExsWyRoiFT7do8scgg01TmCzmdx1ncWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxoTfU1gKzjBXtNzUbmD8xdTFyMEhIWAi8W6ZbhcjJ5ApJnHh 3nq2LkYuDiGBk4wSC1edYAdJsAhoS7zdtZARxOYVsJA4MfcZWFxEQFhi8ct3LCBzhAXcJXYv 0QcJswmoSCy7t5kJxOYUCJfYtO4/I8TMI4wSG76+Zgep5xfQl5jalAKx106i6S/EGF4BQYm/ O4RBwswCWhI9Mx6zQ9jyEtvfzmGewMg/C6FqFpKqWUiqFjAyr2KUyU9L0y1OzUspzk03MNQr qczXyyooKtZLBtGbGMHhxqGwg3HGKYNDjAIcjEo8vNNEPwYJsSaWFVfmHmKU5GBSEuV9OwEo xJeUn1KZkVicEV9UmpNafIhRgoNZSYQ3sRsox5uSWFmVWpQPk5LmYFES5z3+50ygkEB6Yklq dmpqQWoRTFaGg0NJgvfHRKBGwaLU9NSKtMycEoQ0EwcnyHAeoOFak0CGFxck5hZnpkPkTzFK SonzPgNpFgBJZJTmwfW+YhQHekGYVwikjQeYOuC6XgENZAIauM71PcjAkkSElFQDY9fxGXci cs0jlG6tu5hjlZduH6O/u0QopdPuq4DJosvV2Ue/X7G53prudSM81eC9SpuIdKOLxYOl0xZe uLBwz7SrVdtb11QmWk5/c06z4oDJdrfHXHob01Kqz3/r/uR7q1C79Ir/0tPyF2YYhL1PPfDz ppdflUbES3G7ltjthmbGYhrPEmczKrEUZyQaajEXFScCAOT4qCjaAgAA Subject: Re: [weirds] Question: Nameserver data looked up by IP address 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, 05 Feb 2014 01:27:16 -0000 From: "Hollenbeck, Scott" Date: Tue, 4 Feb 2014 13:15:37 +0000 > I just submitted rdap-query-10 with additional text to include name server search by IP address. Thank you for submitting but I have a simple question. What if querying this with a wild card? For example, /nameservers&ip=192.0.2.* /nameservers&ip=2001:db8::* Although these formats don't exactly conform to RFC1166 or RFC5952. Regards, Naoki Kambe From shollenbeck@verisign.com Wed Feb 5 04:01:47 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9AC21A00F7 for ; Wed, 5 Feb 2014 04:01:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.702 X-Spam-Level: X-Spam-Status: No, score=-3.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, 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 RQAVUjIoWcH8 for ; Wed, 5 Feb 2014 04:01:46 -0800 (PST) Received: from exprod6og118.obsmtp.com (exprod6og118.obsmtp.com [64.18.1.233]) by ietfa.amsl.com (Postfix) with ESMTP id 30EE71A00F6 for ; Wed, 5 Feb 2014 04:01:44 -0800 (PST) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob118.postini.com ([64.18.5.12]) with SMTP ID DSNKUvIoJz0PloFFtuCg1uZvWLcXBmgZe2qm@postini.com; Wed, 05 Feb 2014 04:01:45 PST Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id s15C1gAJ030478 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Feb 2014 07:01:42 -0500 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Wed, 5 Feb 2014 07:01:41 -0500 From: "Hollenbeck, Scott" To: Naoki Kambe , "weirds@ietf.org" Thread-Topic: [weirds] Question: Nameserver data looked up by IP address Thread-Index: AQHPIhFqt55lXzLiTUS0giiK8Wkhb5qmj8uw Date: Wed, 5 Feb 2014 12:01:41 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F4933FD17@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <831693C2CDA2E849A7D7A712B24E257F4933E628@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F4933EE5D@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <20140205.102700.267973128.kambe@jprs.co.jp> In-Reply-To: <20140205.102700.267973128.kambe@jprs.co.jp> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.173.152.4] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] Question: Nameserver data looked up by IP address 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, 05 Feb 2014 12:01:47 -0000 > -----Original Message----- > From: weirds [mailto:weirds-bounces@ietf.org] On Behalf Of Naoki Kambe > Sent: Tuesday, February 04, 2014 8:27 PM > To: weirds@ietf.org > Subject: Re: [weirds] Question: Nameserver data looked up by IP address >=20 > From: "Hollenbeck, Scott" > Date: Tue, 4 Feb 2014 13:15:37 +0000 > > I just submitted rdap-query-10 with additional text to include name > server search by IP address. >=20 > Thank you for submitting but I have a simple question. > What if querying this with a wild card? For example, >=20 > /nameservers&ip=3D192.0.2.* > /nameservers&ip=3D2001:db8::* >=20 > Although these formats don't exactly conform to RFC1166 or RFC5952. Wildcard searches aren't included. Scott From johnl@taugh.com Fri Feb 7 15:43:41 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14A941AD6C1 for ; Fri, 7 Feb 2014 15:43:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.343 X-Spam-Level: ** X-Spam-Status: No, score=2.343 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_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 dqa01vOvK2jy for ; Fri, 7 Feb 2014 15:43:39 -0800 (PST) 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 E56281AD72A for ; Fri, 7 Feb 2014 15:43:38 -0800 (PST) Received: (qmail 77757 invoked from network); 7 Feb 2014 23:43:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent:cleverness; s=12fbc.52f56fa9.k1402; i=johnl-iecc.com@submit.iecc.com; bh=RUdQzSJfZTnhdSxkB/7qAB9ZudvLvBwvOk1nqq4itkI=; b=ka+uwqATrN8WuRuYoDXaV10FNwChZFuSnvaRKvCj1jok293vnuPtrWFUPnVtzkVkYTRdjyWO10jTm1qxDP14O1wmgltsQhd6X76qjwmYOdHKO6AqMx5dm7E5Jwrdvtwl8rCcHwXmDZ4giTdkwoGK7ylxbsCnkr5lK9xHTXKiKncfWXUcUxrSZjYocFtAGzB+c8I80v7E823g/40HOSUUVg2bbkBVJJcgBsWs/EhR/Of4u0s4OYU9JXYNex3JMFuX DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent:cleverness; s=12fbc.52f56fa9.k1402; olt=johnl-iecc.com@submit.iecc.com; bh=RUdQzSJfZTnhdSxkB/7qAB9ZudvLvBwvOk1nqq4itkI=; b=WQH0WJalc+1CQ5E/MiYSfZw1VgZCIpRzVT6ag2U0ge1v16nvxliiBWvybXsMDZi9Q8JwbdCdb+S9hu6H1mhEHFwqQCmF4gBdfGbb+6iD/yU2dajfgile3vX1mYFfVYEQpxS7hBbHg2UH5T9xPxZDya+Z9LOZ0QRyYAcjYpHZIWIF22paQxB3OM/n/mvegUtiIEINKjQR/WIr/LBhaGV+RrEzjfdp+08tnmhRAhDmbRWHPJTvY+sZlbnZmeIToUih Received: from joyce.lan ([24.59.92.2]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 07 Feb 2014 23:43:37 -0000 Date: 7 Feb 2014 18:43:36 -0500 Message-ID: From: "John R Levine" To: weirds@ietf.org User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Cleverness: None detected MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3825401791-1693810035-1391816617=:5389" Subject: [weirds] ICANN News Alert -- Request for Information on Contact Data Validation and Verification Systems Available Until 7 March 2014) (fwd) 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, 07 Feb 2014 23:43:41 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3825401791-1693810035-1391816617=:5389 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT This doesn't directly affect WEIRDS, but it gives a hint of what ICANN might be planning to do with it. The EWG is a mysterious cabal. A few members are on the WIERDS list. Regards, John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. ---------- Forwarded message ---------- [http://www.icann.org/images/gradlogo_bow.jpg] News Alert http://www.icann.org/en/news/announcements/announcement-07feb14-en.htm ________________________________ Request for Information on Contact Data Validation and Verification Systems (Available Until 7 March 2014) 7 February 2014 ICANN is publishing a Request for Information (RFI) [PDF, 395 KB] to identify any commercially-available services and software that might be capable of validating or verifying domain name registration contact data (such as WHOIS). This RFI is intended to inform two distinct ICANN projects that require address validation and verification. The first project relates to a near-term need for postal address cross-field validation services arising out of requirements applicable to those registrars who have signed the new 2013 Registrar Accreditation Agreement (RAA Project). In addition, ICANN is seeking similar information for a separate longer term project in connection with Expert Working Group on Next Generation gTLD Directory Services ("EWG") recommendations to identify a replacement to the current WHOIS system. The EWG is now developing recommendations for a new system that could better meet global Internet community needs for domain name registration data while offering greater privacy, accuracy, and accountability (EWG Project). Purpose of RFI The purpose of this RFI is purely informational – that is, to inform the development of policies and procedures that may follow both of these initiatives. As a result, potential Respondents responding to any future RFP for either the RAA Project or the EWG Project will not be bound by the estimates, prices, or other information provided in response to this RFI. RFI Attributes * RFI Availability Date: 7 February 2014 * The Requirements and Instructions are more fully described in the RFI [PDF, 395 KB] * RFI Close Date: 7 March 2014, 23:59 UTC * RFI Language: English only * Responses should be submitted via email to rfi-response@icann.org ICANN greatly appreciates any insights on this topic from those commercial providers interested in sharing information about their services. Background on the RAA Project Registrars who are accredited under the 2013 RAA are currently required to perform limited validation of registration contact data. The agreement envisions that registrars will also perform cross-field validation of address data (e.g., the house number exists on the street, which exists in the city and province, and the postal code is correct). This cross-field validation requirement becomes effective 6 months after ICANN and a working group of registrar volunteers have agreed that cross-field validation is technically and commercially feasible. ICANN has convened the registrar working group that is exploring address validation service options. The RFI published today intended to help inform that working group's work. Background on the EWG Project In December 2012, ICANN announced the creation of an Expert Working Group (EWG) on next-generation gTLD Registration Directory Services, as a first step in fulfilling the ICANN Board's directive to help redefine the purpose and provision of gTLD registration data. The EWG's findings are expected to serve as a foundation to help the GNSO create a new global policy for the provision of gTLD registration data. A significant milestone was reached on 24 June 2013 with the publication of the Expert Working Group on gTLD Directory Services (EWG)'s Initial Report and FAQs, opening a consultation period with the ICANN community. The Initial Report [PDF, 1.70 MB] enumerated the users, purposes, data elements, recommended principles and features, and proposed model to guide the development of a next generation Registration Directory Service (RDS) to replace WHOIS. Prior to the ICANN Meeting in Buenos Aires, the EWG published its Status Update Report [PDF, 2.26 MB] to highlight the EWG's thinking on these and many other key issues. It also provides a great deal more detail on the analysis that lay behind the Initial Report [PDF, 1.70 MB]. The EWG is currently in its research and information gathering phase. This RFI is one of several research efforts that the EWG is currently undertaking to ensure that its final recommendations are supported by facts and informed by current practices. The EWG expects to complete its recommendations in 2014, informed by Community feedback and in-depth analysis of selected areas, including the responses to this RFI. The EWG plans to reconvene in March 2014 to derive fact-based recommendations after carefully examining the results of its research, and expects to deliver its final report to the ICANN Board by June 2014. Questions If questions arise about the RFI regarding the EWG Project, please contact Margie Milam, or Mike Zupke regarding the RAA Project. Any such inquiries should be sent to PP-EWG-Survey@icann.org. --3825401791-1693810035-1391816617=:5389-- From shollenbeck@verisign.com Mon Feb 10 04:35: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 678DF1A05ED for ; Mon, 10 Feb 2014 04:35:29 -0800 (PST) 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 RPh5k3aHVr3O for ; Mon, 10 Feb 2014 04:35:27 -0800 (PST) Received: from exprod6og119.obsmtp.com (exprod6og119.obsmtp.com [64.18.1.234]) by ietfa.amsl.com (Postfix) with ESMTP id EEED41A05E1 for ; Mon, 10 Feb 2014 04:35:11 -0800 (PST) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob119.postini.com ([64.18.5.12]) with SMTP ID DSNKUvjHf5W+Pg1BsjtWkRPB4XIFP2DXSc7i@postini.com; Mon, 10 Feb 2014 04:35:27 PST Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s1ACZBDJ030664 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 10 Feb 2014 07:35:11 -0500 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Mon, 10 Feb 2014 07:35:10 -0500 From: "Hollenbeck, Scott" To: John R Levine , "weirds@ietf.org" Thread-Topic: [weirds] ICANN News Alert -- Request for Information on Contact Data Validation and Verification Systems Available Until 7 March 2014) (fwd) Thread-Index: AQHPJF5xWmO1rZRiTU62eygBnVMKEZquY+CA Date: Mon, 10 Feb 2014 12:35:10 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F493454BE@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 Subject: Re: [weirds] ICANN News Alert -- Request for Information on Contact Data Validation and Verification Systems Available Until 7 March 2014) (fwd) 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, 10 Feb 2014 12:35:29 -0000 PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiB3ZWlyZHMgW21haWx0bzp3ZWly ZHMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEpvaG4gUg0KPiBMZXZpbmUNCj4gU2Vu dDogRnJpZGF5LCBGZWJydWFyeSAwNywgMjAxNCA2OjQ0IFBNDQo+IFRvOiB3ZWlyZHNAaWV0Zi5v cmcNCj4gU3ViamVjdDogW3dlaXJkc10gSUNBTk4gTmV3cyBBbGVydCAtLSBSZXF1ZXN0IGZvciBJ bmZvcm1hdGlvbiBvbg0KPiBDb250YWN0IERhdGEgVmFsaWRhdGlvbiBhbmQgVmVyaWZpY2F0aW9u IFN5c3RlbXMgQXZhaWxhYmxlIFVudGlsIDcNCj4gTWFyY2ggMjAxNCkgKGZ3ZCkNCj4gDQo+IFRo aXMgZG9lc24ndCBkaXJlY3RseSBhZmZlY3QgV0VJUkRTLCBidXQgaXQgZ2l2ZXMgYSBoaW50IG9m IHdoYXQgSUNBTk4NCj4gbWlnaHQgYmUgcGxhbm5pbmcgdG8gZG8gd2l0aCBpdC4NCj4gDQo+IFRo ZSBFV0cgaXMgYSBteXN0ZXJpb3VzIGNhYmFsLiAgQSBmZXcgbWVtYmVycyBhcmUgb24gdGhlIFdJ RVJEUyBsaXN0Lg0KDQpNeXN0ZXJpb3VzIGNhYmFsPyBJIGFtIGEgbWVtYmVyIG9mIHRoZSBFV0cu IFdoaWxlIHRoZSBncm91cCBtaWdodCBiZSBteXN0ZXJpb3VzIHRvIHRob3NlIHdobyBkb24ndCBm b2xsb3cgYWxvbmcsIGFsbCBvZiB0aGUgc2VjcmV0cyAobW9kdWxvIHJlY2VudCB1cGRhdGVzIHRo YXQgaGF2ZW4ndCB5ZXQgYmVlbiBwb3N0ZWQpIHRoaXMgImNhYmFsIiBpcyBwcm9kdWNpbmcgY2Fu IGJlIGZvdW5kIGhlcmU6DQoNCmh0dHBzOi8vY29tbXVuaXR5LmljYW5uLm9yZy9wYWdlcy92aWV3 cGFnZS5hY3Rpb24/cGFnZUlkPTQwMTc1MTg5DQoNClRoZXJlIGFyZSBjb25zdGl0dWVuY2llcyB3 aXRoaW4gSUNBTk4gd2hvIGJlbGlldmUgdGhhdCBib2d1cyBhZGRyZXNzL2NvbnRhY3QgaW5mb3Jt YXRpb24gaXMgYW4gaXNzdWUuIFRoZSBwdXJwb3NlIG9mIHRoZSBSRkkgaXMgdG8gZ2FpbiAgYW4g dW5kZXJzdGFuZGluZyBvZiB0aGUgY29zdHMgYXNzb2NpYXRlZCB3aXRoIGRhdGEgdmFsaWRhdGlv biBhbmQgdmVyaWZpY2F0aW9uLiBXZSdyZSB0cnlpbmcgdG8gZG8gb3VyIGhvbWV3b3JrLCB3ZSdy ZSBhc2tpbmcgZm9yIGhlbHAsIGFuZCB3ZSdyZSBkb2luZyBpdCBwdWJsaWNseS4NCg0KU2NvdHQN Cg== From internet-drafts@ietf.org Mon Feb 10 04:52:41 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AF831A05DF; Mon, 10 Feb 2014 04:52:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRu8rG09soz5; Mon, 10 Feb 2014 04:52:39 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AB55A1A00BC; Mon, 10 Feb 2014 04:52:39 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140210125239.16122.4932.idtracker@ietfa.amsl.com> Date: Mon, 10 Feb 2014 04:52:39 -0800 Cc: weirds@ietf.org Subject: [weirds] I-D Action: draft-ietf-weirds-rdap-sec-06.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 12:52:41 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web Extensible Internet Registration Data Service Working Group of the IETF. Title : Security Services for the Registration Data Access Protocol Authors : Scott Hollenbeck Ning Kong Filename : draft-ietf-weirds-rdap-sec-06.txt Pages : 11 Date : 2014-02-10 Abstract: The Registration Data Access Protocol (RDAP) provides "RESTful" web services to retrieve registration metadata from domain name and regional internet registries. This document describes information security services including authentication, authorization, availability, data confidentiality, and data integrity for RDAP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-weirds-rdap-sec/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-weirds-rdap-sec-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-weirds-rdap-sec-06 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From shollenbeck@verisign.com Mon Feb 10 04:54:54 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 999B51A0606 for ; Mon, 10 Feb 2014 04:54:54 -0800 (PST) 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 Q516aZI3R8Us for ; Mon, 10 Feb 2014 04:54:53 -0800 (PST) Received: from exprod6og126.obsmtp.com (exprod6og126.obsmtp.com [64.18.1.77]) by ietfa.amsl.com (Postfix) with ESMTP id F1B3E1A05FA for ; Mon, 10 Feb 2014 04:54:52 -0800 (PST) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob126.postini.com ([64.18.5.12]) with SMTP ID DSNKUvjMHYMWzD1n2enAH0Om/6xwTLZElsx/@postini.com; Mon, 10 Feb 2014 04:54:53 PST 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 s1ACsq9H029765 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 10 Feb 2014 07:54:52 -0500 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Mon, 10 Feb 2014 07:54:52 -0500 From: "Hollenbeck, Scott" To: "weirds@ietf.org" Thread-Topic: I-D Action: draft-ietf-weirds-rdap-sec-06.txt Thread-Index: AQHPJl8FXEaw6M8iFU+ZaUGaJy7TlJqucZ5w Date: Mon, 10 Feb 2014 12:54:51 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F493457D3@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <20140210125239.16122.4932.idtracker@ietfa.amsl.com> In-Reply-To: <20140210125239.16122.4932.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.173.152.4] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] I-D Action: draft-ietf-weirds-rdap-sec-06.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, 10 Feb 2014 12:54:54 -0000 > -----Original Message----- > From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of > internet-drafts@ietf.org > Sent: Monday, February 10, 2014 7:53 AM > To: i-d-announce@ietf.org > Cc: weirds@ietf.org > Subject: I-D Action: draft-ietf-weirds-rdap-sec-06.txt >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Web Extensible Internet Registration > Data Service Working Group of the IETF. >=20 > Title : Security Services for the Registration Data > Access Protocol > Authors : Scott Hollenbeck > Ning Kong > Filename : draft-ietf-weirds-rdap-sec-06.txt > Pages : 11 > Date : 2014-02-10 This is just a keepalive refresh. Scott From michele@blacknight.com Mon Feb 10 06:22: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 0F4D11A0843 for ; Mon, 10 Feb 2014 06:22:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.102 X-Spam-Level: X-Spam-Status: No, score=-0.102 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_LOW=-0.7, 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 SqIG3OElmpIm for ; Mon, 10 Feb 2014 06:22:53 -0800 (PST) Received: from exchange.blacknight.ie (exchange.blacknight.ie [81.17.243.252]) by ietfa.amsl.com (Postfix) with ESMTP id EEE501A02FA for ; Mon, 10 Feb 2014 06:22:52 -0800 (PST) Received: from BK-EXCHMBX01.blacknight.local ([fe80::a9c8:c46:8f4d:f8c8]) by bkexchhubcas01.blacknight.local ([fe80::994e:1bb8:df56:f591%15]) with mapi id 14.02.0342.003; Mon, 10 Feb 2014 14:22:51 +0000 From: Michele Neylon - Blacknight To: John R Levine , "weirds@ietf.org" Thread-Topic: [weirds] ICANN News Alert -- Request for Information on Contact Data Validation and Verification Systems Available Until 7 March 2014) (fwd) Thread-Index: AQHPJF54FWuUwYNWhkGwt5waoLSThJquje5g Date: Mon, 10 Feb 2014 14:22:50 +0000 Message-ID: References: <20140207234358.D50D159C001@merlin.blacknight.ie> In-Reply-To: <20140207234358.D50D159C001@merlin.blacknight.ie> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [81.17.243.251] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Subject: Re: [weirds] ICANN News Alert -- Request for Information on Contact Data Validation and Verification Systems Available Until 7 March 2014) (fwd) 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, 10 Feb 2014 14:22:56 -0000 Sm9obg0KDQpJJ20gYWxzbyBhIG1lbWJlciBvZiB0aGUgRVdHIGFuZCBJJ20gaGFyZGx5IHRoYXQg bXlzdGVyaW91cyBvciBhbnl0aGluZyBuZWFybHkgdGhhdCBleGNpdGluZyAtIHRob3VnaCBJJ2Qg bGlrZSB0byBiZSA6KSANCg0KQXMgU2NvdHQgaGFzIHNhaWQsIHByZXR0eSBtdWNoIGV2ZXJ5dGhp bmcgeW91IHdhbnQgdG8ga25vdyBpcyBhbHJlYWR5IG9ubGluZSBhbmQgcHVibGljDQoNCklmIHRo ZXJlJ3MgYW55dGhpbmcgdGhhdCB5b3Ugb3IgYW55b25lIGVsc2Ugd291bGQgbGlrZSB1cyB0byBh ZGRyZXNzIC8gZXhwbGFpbiBvciBjbGFyaWZ5IGluIGFueSB3YXkgYWxsIHlvdSBoYXZlIHRvIGRv IGlzIGFzayA6KQ0KDQpSZWdhcmRzDQoNCk1pY2hlbGUNCg0KDQoNCi0tDQpNciBNaWNoZWxlIE5l eWxvbg0KQmxhY2tuaWdodCBTb2x1dGlvbnMNCkhvc3RpbmcgJiBDb2xvY2F0aW9uLCBEb21haW5z DQpodHRwOi8vd3d3LmJsYWNrbmlnaHQuY28vDQpodHRwOi8vYmxvZy5ibGFja25pZ2h0LmNvbS8N Cmh0dHA6Ly93d3cudGVjaG5vbG9neS5pZQ0KSW50bC4gKzM1MyAoMCkgNTkgIDkxODMwNzINCkxv Y2FsbDogMTg1MCA5MjkgOTI5DQpEaXJlY3QgRGlhbDogKzM1MyAoMCk1OSA5MTgzMDkwDQpGYXgu ICszNTMgKDApIDEgNDgxMSA3NjMNClR3aXR0ZXI6IGh0dHA6Ly90d2l0dGVyLmNvbS9tbmV5bG9u DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpCbGFja25pZ2h0IEludGVybmV0IFNv bHV0aW9ucyBMdGQsIFVuaXQgMTJBLEJhcnJvd3NpZGUgQnVzaW5lc3MgUGFyayxTbGVhdHkNClJv YWQsR3JhaWd1ZWN1bGxlbixDYXJsb3csSXJlbGFuZCAgQ29tcGFueSBOby46IDM3MDg0NQ0K From andy@arin.net Wed Feb 12 11:26: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 468D21A0548 for ; Wed, 12 Feb 2014 11:26:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.252 X-Spam-Level: X-Spam-Status: No, score=0.252 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.548] 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 HYn9VhvTQ3qC for ; Wed, 12 Feb 2014 11:26:09 -0800 (PST) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id A48661A062C for ; Wed, 12 Feb 2014 11:26:09 -0800 (PST) Received: by smtp2.arin.net (Postfix, from userid 323) id 7016921367E; Wed, 12 Feb 2014 14:26:08 -0500 (EST) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp2.arin.net (Postfix) with ESMTP id 0C12F21360D for ; Wed, 12 Feb 2014 14:26:08 -0500 (EST) 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; Wed, 12 Feb 2014 14:26:07 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.174]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0328.009; Wed, 12 Feb 2014 14:26:07 -0500 From: Andy Newton To: "weirds@ietf.org" Thread-Topic: Useful and Unuseful Searches Thread-Index: AQHPKChGg+zr3JpoCU+ymicpvh/z8Q== Date: Wed, 12 Feb 2014 19:26:06 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <204431C2CD9EB247AB3EE61C40EB8A03@corp.arin.net> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [weirds] Useful and Unuseful Searches 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, 12 Feb 2014 19:26:11 -0000 In looking at our implementation, it occurred to me that there are two useful searches we do not include: 1) Search of domain names by nameserver name It could look something like /domains?nsLdhName=3DXXXXX 2) Search of domain names by nameserver IP address It could look something like /domains?nsIp=3DYYYYY This answers the age old question, =B3Which domains are served by nameserve= r BLAH?=B2 I don=B9t think all registries can support both styles (we can=B9t= do #2 because we don=B9t collect A records). However, these are questions that seems immensely useful. On the other hand, we have /entities?handle=3DXXXX where a user can search on partial matches for registry handles. As handles are unique Ids defined by registries and are completely synthetic, I tend to wonder how useful this query will be. I think it should be taken out. -andy From fergdawgster@mykolab.com Wed Feb 12 11:27:59 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB3B1A0631 for ; Wed, 12 Feb 2014 11:27:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.148 X-Spam-Level: X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548, 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 ZPVNDULIc8Xj for ; Wed, 12 Feb 2014 11:27:57 -0800 (PST) Received: from mx04.mykolab.com (mx01.mykolab.com [95.128.36.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55E971A062C for ; Wed, 12 Feb 2014 11:27:57 -0800 (PST) X-Virus-Scanned: amavisd-new at kolabsys.net Sender: fergdawgster@mykolab.com Message-ID: <52FBCB36.10607@mykolab.com> Date: Wed, 12 Feb 2014 11:27:50 -0800 From: Paul Ferguson Organization: Clowns R. Mofos To: Andy Newton References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: "weirds@ietf.org" Subject: Re: [weirds] Useful and Unuseful Searches X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: fergdawgster@mykolab.com 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, 12 Feb 2014 19:28:00 -0000 Andy: On 2/12/2014 11:26 AM, Andy Newton wrote: > In looking at our implementation, it occurred to me that there are two > useful searches we do not include: > > 1) Search of domain names by nameserver name > It could look something like /domains?nsLdhName=XXXXX > > 2) Search of domain names by nameserver IP address > It could look something like /domains?nsIp=YYYYY > Speaking for myself, I would find both of these search criterion *very* useful indeed. - ferg > This answers the age old question, ³Which domains are served by nameserver > BLAH?² I don¹t think all registries can support both styles (we can¹t do > #2 because we don¹t collect A records). However, these are questions that > seems immensely useful. > > On the other hand, we have /entities?handle=XXXX where a user can search > on partial matches for registry handles. As handles are unique Ids defined > by registries and are completely synthetic, I tend to wonder how useful > this query will be. I think it should be taken out. > > -andy > -- Paul Ferguson VP Threat Intelligence, IID PGP Public Key ID: 0x54DC85B2 From simon.perreault@viagenie.ca Wed Feb 12 11:38:50 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE051A0631 for ; Wed, 12 Feb 2014 11:38:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.449 X-Spam-Level: X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, 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 Oy9GG2osr0yI for ; Wed, 12 Feb 2014 11:38:46 -0800 (PST) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id C4E101A04E0 for ; Wed, 12 Feb 2014 11:38:46 -0800 (PST) Received: from porto.nomis80.org (ringo.viagenie.ca [IPv6:2620:0:230:c000:3e97:eff:fe0b:dd8a]) by jazz.viagenie.ca (Postfix) with ESMTPSA id C8EEB403CB for ; Wed, 12 Feb 2014 14:38:45 -0500 (EST) Message-ID: <52FBCDC5.6090706@viagenie.ca> Date: Wed, 12 Feb 2014 14:38:45 -0500 From: Simon Perreault User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: weirds@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: [weirds] Useful and Unuseful Searches 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, 12 Feb 2014 19:38:50 -0000 Le 2014-02-12 14:26, Andy Newton a écrit : > In looking at our implementation, it occurred to me that there are two > useful searches we do not include: > > 1) Search of domain names by nameserver name > It could look something like /domains?nsLdhName=XXXXX > > 2) Search of domain names by nameserver IP address > It could look something like /domains?nsIp=YYYYY Is the second one necessary? Wouldn't it be possible to do the equivalent in two steps? 1) /nameservers?ip=YYYY, then 2) /domains?nsLdhName=XXXXX with the result from step 1. Other than that, yes, makes total sense. Simon -- DTN made easy, lean, and smart --> http://postellation.viagenie.ca NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca STUN/TURN server --> http://numb.viagenie.ca From andy@arin.net Wed Feb 12 11:55:16 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 C70471A0641 for ; Wed, 12 Feb 2014 11:55:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 tpKnq7s-dc6h for ; Wed, 12 Feb 2014 11:55:15 -0800 (PST) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 566411A062C for ; Wed, 12 Feb 2014 11:55:15 -0800 (PST) Received: by smtp2.arin.net (Postfix, from userid 323) id 73A71213673; Wed, 12 Feb 2014 14:55:14 -0500 (EST) Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id 094A521360D; Wed, 12 Feb 2014 14:55:14 -0500 (EST) Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.342.3; Wed, 12 Feb 2014 14:55:13 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.174]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0347.000; Wed, 12 Feb 2014 14:55:13 -0500 From: Andy Newton To: Simon Perreault , "weirds@ietf.org" Thread-Topic: [weirds] Useful and Unuseful Searches Thread-Index: AQHPKChGg+zr3JpoCU+ymicpvh/z8ZqyV5aA//+wxoA= Date: Wed, 12 Feb 2014 19:55:12 +0000 Message-ID: In-Reply-To: <52FBCDC5.6090706@viagenie.ca> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] Useful and Unuseful Searches 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, 12 Feb 2014 19:55:16 -0000 On 2/12/14, 2:38 PM, "Simon Perreault" wrote: >Is the second one necessary? Wouldn't it be possible to do the >equivalent in two steps? 1) /nameservers?ip=3DYYYY, then 2) >/domains?nsLdhName=3DXXXXX with the result from step 1. Yes, that is possible. But it reduces load for everybody to do it in one step. -andy From AMaitland@Commerco.Com Wed Feb 12 12:00: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 E0B821A06F1 for ; Wed, 12 Feb 2014 12:00:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.191 X-Spam-Level: X-Spam-Status: No, score=-1.191 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HELO_MISMATCH_NET=0.611, 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 e_LnOjPrIxhs for ; Wed, 12 Feb 2014 12:00:34 -0800 (PST) Received: from MS1.MailSys.Net (MS1.MailSys.Net [66.135.47.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3F5AF1A06BC for ; Wed, 12 Feb 2014 12:00:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=mailsys; d=Commerco.Com; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:x-fromip:x-fromcountry; b=wKIbEf7DGs38ZdoecIQxEOr4nD/2whhwde8NMe28AeN+lXo/wcjrXtE+908NVuQJKoaZZCcC/rO9O1gxVdCZ7gjB+FaAeLJhz28kKFB8CZNDTlxVBhntClftQd1RO1QFYEJNKgQsHmTIc/ZLGzla2U6dU42UOf58n823u/zSrZ8= Received: from [71.216.84.59] by MS1.MailSys.Net (ArGoSoft Mail Server .NET v.1.0.8.6) with ESMTP (EHLO [127.0.0.1]); Wed, 12 Feb 2014 20:00:17 +0000 Message-ID: <52FBD2CB.4030406@Commerco.Com> Date: Wed, 12 Feb 2014 13:00:11 -0700 From: Alan Maitland User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: fergdawgster@mykolab.com, Andy Newton References: <52FBCB36.10607@mykolab.com> In-Reply-To: <52FBCB36.10607@mykolab.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-FromIP: 71.216.84.59 X-FromCountry: US Cc: "weirds@ietf.org" Subject: Re: [weirds] Useful and Unuseful Searches 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, 12 Feb 2014 20:00:36 -0000 +1 On 2/12/2014 12:27 PM, Paul Ferguson wrote: > Andy: > > On 2/12/2014 11:26 AM, Andy Newton wrote: > >> In looking at our implementation, it occurred to me that there are two >> useful searches we do not include: >> >> 1) Search of domain names by nameserver name >> It could look something like /domains?nsLdhName=XXXXX >> >> 2) Search of domain names by nameserver IP address >> It could look something like /domains?nsIp=YYYYY >> > > Speaking for myself, I would find both of these search criterion *very* > useful indeed. > > - ferg > >> This answers the age old question, ³Which domains are served by nameserver >> BLAH?² I don¹t think all registries can support both styles (we can¹t do >> #2 because we don¹t collect A records). However, these are questions that >> seems immensely useful. >> >> On the other hand, we have /entities?handle=XXXX where a user can search >> on partial matches for registry handles. As handles are unique Ids defined >> by registries and are completely synthetic, I tend to wonder how useful >> this query will be. I think it should be taken out. >> >> -andy >> > > From johnl@iecc.com Thu Feb 13 05:50: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 BABE81A01CF for ; Thu, 13 Feb 2014 05:50:19 -0800 (PST) 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 DeiUj-nRpsY9 for ; Thu, 13 Feb 2014 05:50:18 -0800 (PST) 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 2CF1F1A024D for ; Thu, 13 Feb 2014 05:50:06 -0800 (PST) Received: (qmail 80271 invoked from network); 13 Feb 2014 13:50:05 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 13 Feb 2014 13:50:05 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52fccd8e.xn--i8sz2z.k1402; i=johnl@user.iecc.com; bh=MV+UsOJU7rCCdBq/2GYaVAbPp3l1LeSa1LA3V2OuMIQ=; b=xLaJU70huwZxJWOJcYEUFDMQYm6XFVh5SvtcbR3yNyPdG3URniVXn4ueORF5H27TO5pli2L2MAkc5BbC8FPWhpQvC58VvFp5gbeCluDMEziaDuYf/uzCNe5nDNvCCsF8Y4afwHU08tRx25wyuWWPIqZNc3sORGYrnkaVe78jGUlmLgkCBl2AAYBxhg81r1a/9TE8yu3gzYD8OfPVaOfTAAdHQd5EKlXexNpkkAJk8csLR7Z+t/M3ci008k+5pTVe 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=52fccd8e.xn--i8sz2z.k1402; bh=MV+UsOJU7rCCdBq/2GYaVAbPp3l1LeSa1LA3V2OuMIQ=; b=FoeVVGZ9bd/qZCyIODiJ4UlSo0ZHR7y7w7fM/rEqZnI3Skef66rGMWMVHJQKqHePFQCpj6LmO03VNfcyGFYdNMYvNLhAhpccmwNQIKkcIXphhHffqNZ1vr0DBkHUZ7A3HAXSVbFTfATWSZRKBaBK6FU6+2FEi7A17THiE1sbiHWUOFCEP3MvROMk/Mg8wT2SUI0ZRlPi1JkSg0qyJ2CHk31jfFVr6npgJrmDC4CsEsY1CB7XChwriWwPDJxHGh6T Date: 13 Feb 2014 13:49:43 -0000 Message-ID: <20140213134943.2126.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 Subject: Re: [weirds] Useful and Unuseful Searches 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, 13 Feb 2014 13:50:19 -0000 >1) Search of domain names by nameserver name > It could look something like /domains?nsLdhName=XXXXX > >2) Search of domain names by nameserver IP address > It could look something like /domains?nsIp=YYYYY They sound swell, but I would be reluctant to add them until we hear from a registry that plans to implement them. I don't think current versions of WHOIS do it. For ICANN TLDs, you can fake it by downloading the zone file and using grep. R's, John From andy@arin.net Thu Feb 13 06:12: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 3FE761A026C for ; Thu, 13 Feb 2014 06:12:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 6a9izt62yTWD for ; Thu, 13 Feb 2014 06:12:26 -0800 (PST) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8801A027A for ; Thu, 13 Feb 2014 06:12:26 -0800 (PST) Received: by smtp2.arin.net (Postfix, from userid 323) id 352D221366F; Thu, 13 Feb 2014 09:12:25 -0500 (EST) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp2.arin.net (Postfix) with ESMTP id AE44321366C; Thu, 13 Feb 2014 09:12:22 -0500 (EST) 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; Thu, 13 Feb 2014 09:12:16 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.174]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0328.009; Thu, 13 Feb 2014 09:12:16 -0500 From: Andy Newton To: John Levine , "weirds@ietf.org" Thread-Topic: [weirds] Useful and Unuseful Searches Thread-Index: AQHPKChGg+zr3JpoCU+ymicpvh/z8ZqziGaA//+ydgA= Date: Thu, 13 Feb 2014 14:12:15 +0000 Message-ID: In-Reply-To: <20140213134943.2126.qmail@joyce.lan> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <7E9267BC5166DD48A4B315EC90E9B708@corp.arin.net> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] Useful and Unuseful Searches 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, 13 Feb 2014 14:12:28 -0000 On 2/13/14, 8:49 AM, "John Levine" wrote: >They sound swell, but I would be reluctant to add them until we hear >from a registry that plans to implement them. Well, I plan to implement #1. However, we already know that not all registries will be able to implement all searches or lookups. So I think our best judgement should be used as to what to put into our docs vs. what ICANN requires or somebody has/has not implemented over port 43. As I noted, the search by entity handle doesn=B9t make much sense, but it is in our docs because somebody has implemented it over 43. Certainly ICANN requirements and current implementations should inform our decisions but those should not be the final criteria. -andy From johnl@taugh.com Thu Feb 13 06:17: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 D26C11A02A5 for ; Thu, 13 Feb 2014 06:17:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.357 X-Spam-Level: X-Spam-Status: No, score=-0.357 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_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 nakSdJ1IJm7F for ; Thu, 13 Feb 2014 06:17:28 -0800 (PST) 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 C47651A0290 for ; Thu, 13 Feb 2014 06:17:25 -0800 (PST) Received: (qmail 85240 invoked from network); 13 Feb 2014 14:17:24 -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=14cf7.52fcd3f4.k1402; i=johnl-iecc.com@submit.iecc.com; bh=HmRH3OuhNVAuqiYGX4G1MYUzXU1PzxvzM8GDnHFG6gM=; b=KV44DQ4zxa5xYf7XEizNAdHIhzUiodedy3UJJBoBlWK8uQwlmuDR5o5coFM+AExqGGcg4rTDBSg6d6OADl8OG2+5OW0D0VeVqyw5q/qCR1H/crA5n2mKRhZLhYh2zxJvX9dYQJeMWAjk/hvWNU4XNuFtyDjwdx/9H1MPe+2zV6hFbhWjznJAwozuX0OFcMW8H5Ep2PudO8pWj1uCAJ1fr1HtHN+EnWJDDl0HKC7sLhANnNExp3Xb9Jp00q7pBmh/ 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=14cf7.52fcd3f4.k1402; olt=johnl-iecc.com@submit.iecc.com; bh=HmRH3OuhNVAuqiYGX4G1MYUzXU1PzxvzM8GDnHFG6gM=; b=mxtC5ye7vMWlJccgdNarRGEv8jwXKdldcMLrf1RClOX/utZo8RNi8kPusq0KYGQmOSEhywHqqhFK5Stj322wZFDa+a8aoj9xI5/bt8Dl6X7WQPfNSZCl6JNOf3A3J6oydIouDT5E80w1nm5luVzm9P5/i/5sMwUAcvj/47ulAnFhbjU1eDSpVVh5BFvS8R2l3G+eREWpsqD7vd7J8yewyu8JUL5xuW7WenH/3ZWU9mTnFt3iXQPtbN7emMXcy/op Received: from [10.255.254.1] ([76.71.216.36]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 13 Feb 2014 14:17:24 -0000 Date: 13 Feb 2014 09:17:22 -0500 Message-ID: From: "John R Levine" To: "Andy Newton" In-Reply-To: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Cleverness: None detected MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "weirds@ietf.org" Subject: Re: [weirds] Useful and Unuseful Searches 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, 13 Feb 2014 14:17:30 -0000 >> They sound swell, but I would be reluctant to add them until we hear >> from a registry that plans to implement them. > > Well, I plan to implement #1. > > However, we already know that not all registries will be able to implement > all searches or lookups. Oh, sure. I just don't want to put stuff into the spec that nobody at all will do. Regards, John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. From andy@arin.net Thu Feb 13 06:29:17 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 965711A0293 for ; Thu, 13 Feb 2014 06:29:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 bXwITf8IDyWM for ; Thu, 13 Feb 2014 06:29:15 -0800 (PST) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 3A0771A0237 for ; Thu, 13 Feb 2014 06:29:15 -0800 (PST) Received: by smtp1.arin.net (Postfix, from userid 323) id 0AE2D16553C; Thu, 13 Feb 2014 09:29:14 -0500 (EST) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp1.arin.net (Postfix) with ESMTP id 8EA92165534; Thu, 13 Feb 2014 09:29:13 -0500 (EST) 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; Thu, 13 Feb 2014 09:29:13 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.174]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0347.000; Thu, 13 Feb 2014 09:29:06 -0500 From: Andy Newton To: John R Levine Thread-Topic: [weirds] Useful and Unuseful Searches Thread-Index: AQHPKChGg+zr3JpoCU+ymicpvh/z8ZqziGaA//+ydgCAAFVEAP//r3UA Date: Thu, 13 Feb 2014 14:29:06 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "weirds@ietf.org" Subject: Re: [weirds] Useful and Unuseful Searches 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, 13 Feb 2014 14:29:17 -0000 On 2/13/14, 9:17 AM, "John R Levine" wrote: >Oh, sure. I just don't want to put stuff into the spec that nobody at all >will do. Totally agree! -andy From nobody Thu Feb 13 10:06:21 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C08A1A039F for ; Thu, 13 Feb 2014 10:06:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.826 X-Spam-Level: X-Spam-Status: No, score=-1.826 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, 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 g20W3y0PWXyk for ; Thu, 13 Feb 2014 10:06:16 -0800 (PST) Received: from outbound.afilias.info (outbound.afilias.info [66.199.183.4]) by ietfa.amsl.com (Postfix) with ESMTP id 983671A03A4 for ; Thu, 13 Feb 2014 10:06:16 -0800 (PST) Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.72) (envelope-from ) id 1WE0fv-0005cY-4A for weirds@ietf.org; Thu, 13 Feb 2014 18:06:15 +0000 Received: from mail-lb0-f169.google.com ([209.85.217.169]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1WE0fv-0001rJ-3Z for weirds@ietf.org; Thu, 13 Feb 2014 18:06:15 +0000 Received: by mail-lb0-f169.google.com with SMTP id q8so8656957lbi.0 for ; Thu, 13 Feb 2014 10:06:08 -0800 (PST) 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=hIGmNgml8rVhe13yTMUQ35a3CTUAq7Zs7LtKwyycs0M=; b=L7hiXyB7qQEJSNoIloJEcYAbbCM7PNxQRDvvrztnwUv7T0KNLvvmNJMMfAet258Kua EVgSAyDTWDoZR93MZfOZ1P4XK6PIh0KRh2Yu3c9P1e1VkuGSunxm7Sc48AjnrlX23W6k 73m8MzpU5rv5QT0CXnWFRP35oFg2K6jlZN58UskLlt8hcK3CmjkTAyG7vEemD+/yZHMd dG3b9es7DUztidY2Fo18OgqGSE7FBMe834GNWYRmcX0kRfYkx/htbDllbF2a+PhSohsM F6tWosvkpvmARAcJsKRi0F8xnVMSk+X6HYoSJuyMX2EswWS5xsTzcpU7uGULe0SDiCIs 4fMQ== X-Gm-Message-State: ALoCoQl0I7UZAiFFoO8EltTfiFPg8v7KGVKrVmNWzFF4o3IeQvWdfB7Of6ZVybJ7tUQdZNWQ5nH9WtmGSQSBch7ryb3x1gCuJ3wL3fN2B+oE/0OZlVImhFoIJ0kDn5T5bxY2R74TOv7g X-Received: by 10.112.134.38 with SMTP id ph6mr1909024lbb.16.1392314768822; Thu, 13 Feb 2014 10:06:08 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.134.38 with SMTP id ph6mr1909011lbb.16.1392314768649; Thu, 13 Feb 2014 10:06:08 -0800 (PST) Received: by 10.112.158.233 with HTTP; Thu, 13 Feb 2014 10:06:08 -0800 (PST) In-Reply-To: References: Date: Thu, 13 Feb 2014 13:06:08 -0500 Message-ID: From: Ernie Dainow To: Andy Newton Content-Type: multipart/alternative; boundary=047d7b3a894633910504f24d8b2d Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/FnH5_DCpGYQ1Cyqu3j66-sS8u4w Cc: "weirds@ietf.org" Subject: Re: [weirds] Useful and Unuseful Searches 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, 13 Feb 2014 18:06:19 -0000 --047d7b3a894633910504f24d8b2d Content-Type: text/plain; charset=ISO-8859-1 On Wed, Feb 12, 2014 at 2:26 PM, Andy Newton wrote: > ... On the other hand, we have /entities?handle=XXXX where a user can search > on partial matches for registry handles. As handles are unique Ids defined > by registries and are completely synthetic, I tend to wonder how useful > this query will be. I think it should be taken out. > > http://www.ietf.org/mail-archive/web/weirds/current/msg03215.html -Ernie --047d7b3a894633910504f24d8b2d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Wed, Feb 12, 2014 at 2:26 PM, Andy Newton <= andy@arin.net> wrote:
...=A0
On the other hand, we have /entities?handle=3DXXXX where a user can search<= br> on partial matches for registry handles. As handles are unique Ids defined<= br> by registries and are completely synthetic, I tend to wonder how useful
this query will be. I think it should be taken out.



-Ernie=A0
--047d7b3a894633910504f24d8b2d-- From nobody Thu Feb 13 10:50: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 134FA1A03B5 for ; Thu, 13 Feb 2014 10:50:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.447 X-Spam-Level: X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548] 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 KKHb3NntZIqQ for ; Thu, 13 Feb 2014 10:50:03 -0800 (PST) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 230131A039F for ; Thu, 13 Feb 2014 10:50:03 -0800 (PST) Received: by smtp1.arin.net (Postfix, from userid 323) id E356E16562C; Thu, 13 Feb 2014 13:50:01 -0500 (EST) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp1.arin.net (Postfix) with ESMTP id 33D161655F9; Thu, 13 Feb 2014 13:50:01 -0500 (EST) 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; Thu, 13 Feb 2014 13:50:00 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.174]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0328.009; Thu, 13 Feb 2014 13:50:00 -0500 From: Andy Newton To: Ernie Dainow Thread-Topic: [weirds] Useful and Unuseful Searches Thread-Index: AQHPKChGg+zr3JpoCU+ymicpvh/z8Zqz0AoA//+4cwA= Date: Thu, 13 Feb 2014 18:50:00 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] Content-Type: multipart/alternative; boundary="_000_CF227C7B2C7A4andyarinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/8CfqAdwCza4HyqsPV8Smbn1HcDE Cc: "weirds@ietf.org" Subject: Re: [weirds] Useful and Unuseful Searches 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, 13 Feb 2014 18:50:07 -0000 --_000_CF227C7B2C7A4andyarinnet_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable From: Ernie Dainow > Date: Thursday, February 13, 2014 at 1:06 PM To: Andrew Newton > Cc: "weirds@ietf.org" > Subject: Re: [weirds] Useful and Unuseful Searches On Wed, Feb 12, 2014 at 2:26 PM, Andy Newton > wrote: ... On the other hand, we have /entities?handle=3DXXXX where a user can search on partial matches for registry handles. As handles are unique Ids defined by registries and are completely synthetic, I tend to wonder how useful this query will be. I think it should be taken out. http://www.ietf.org/mail-archive/web/weirds/current/msg03215.html -Ernie As a handle can reference a particular instance of a registration (example.= com registered between 1/1/1991 and 1/2/1992 would have a different handle = than example.com registered between 1/1/2001 and 1/2/2002), a lookup by han= dle seems useful. We have handles on AS and IP registrations for disambigua= tion purposes. However, there does not seem to be a utility for searches by= handle, especially entity handles. -andy --_000_CF227C7B2C7A4andyarinnet_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
From: Ernie Dainow <edainow@afilias.info>
Date: Thursday, February 13, 2014 a= t 1:06 PM
To: Andrew Newton <andy@arin.net>
Cc: "weirds@ietf.org" <= weirds@ietf.org>
Subject: Re: [weirds] Useful and Un= useful Searches


On Wed, Feb 12, 2014 at 2:26 PM, Andy Newton <andy@arin.net>= ; wrote:
... 
On the other hand, we have /entities?handle=3DXXXX where a user can search<= br> on partial matches for registry handles. As handles are unique Ids defined<= br> by registries and are completely synthetic, I tend to wonder how useful
this query will be. I think it should be taken out.



-Ernie 

As a handle can reference a particular instance of a registration (exa= mple.com registered between 1/1/1991 and 1/2/1992 would have a different ha= ndle than example.com registered between 1/1/2001 and 1/2/2002), a lookup b= y handle seems useful. We have handles on AS and IP registrations for disambiguation purposes. However, there doe= s not seem to be a utility for searches by handle, especially entity handle= s.

-andy
--_000_CF227C7B2C7A4andyarinnet_-- From nobody Thu Feb 13 11:28:24 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BB8C1A0406; Thu, 13 Feb 2014 11:28:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gYWAq3Xnt9ts; Thu, 13 Feb 2014 11:28:19 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 884631A0350; Thu, 13 Feb 2014 11:28:19 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140213192819.26372.59699.idtracker@ietfa.amsl.com> Date: Thu, 13 Feb 2014 11:28:19 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/shlfhG5rPNtvwZBgL_XPhIlaiJ8 Cc: weirds@ietf.org Subject: [weirds] I-D Action: draft-ietf-weirds-bootstrap-01.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 19:28:21 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web Extensible Internet Registration Data Service Working Group of the IETF. Title : Finding the Authoritative Registration Data (RDAP) Service Author : Marc Blanchet Filename : draft-ietf-weirds-bootstrap-01.txt Pages : 8 Date : 2014-02-13 Abstract: This document specifies a method to find which Registration Data Access Protocol (RDAP) server is authoritative to answer queries for a requested scope, such as domain names, IP addresses or Autonomous System numbers, using data available in IANA registries. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-weirds-bootstrap/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-weirds-bootstrap-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-weirds-bootstrap-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Feb 13 11:31: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 CC2121A03E0 for ; Thu, 13 Feb 2014 11:31:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, 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 vn1qGSSingqe for ; Thu, 13 Feb 2014 11:31:30 -0800 (PST) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id B79741A0404 for ; Thu, 13 Feb 2014 11:31:30 -0800 (PST) Received: from [IPv6:2620:0:230:2002::1001] (unknown [IPv6:2620:0:230:2002::1001]) by jazz.viagenie.ca (Postfix) with ESMTPSA id EF08E403D5 for ; Thu, 13 Feb 2014 14:31:28 -0500 (EST) From: Marc Blanchet Content-Type: multipart/alternative; boundary="Apple-Mail=_D2C51752-2CBF-4921-8098-3F7495412DD9" Date: Thu, 13 Feb 2014 14:31:26 -0500 References: <20140213192819.26372.59699.idtracker@ietfa.amsl.com> To: "" Message-Id: <831C0F88-20A5-4386-B4E8-E83A3AE726FA@viagenie.ca> Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/kVMZi6Q9rtq3zZP-_SdRfLwRPeQ Subject: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-01.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: Thu, 13 Feb 2014 19:31:34 -0000 --Apple-Mail=_D2C51752-2CBF-4921-8098-3F7495412DD9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 New version based on comments: - more text on the "longest match" - more text on entities - more text on advice to clients It does not touch the recent comments discussed in apps-discuss. Still = waiting for resolution on this. Regards, Marc. D=E9but du message r=E9exp=E9di=E9 : > De: internet-drafts@ietf.org > Objet: I-D Action: draft-ietf-weirds-bootstrap-01.txt > Date: 13 f=E9vrier 2014 14:28:19 HNE > =C0: i-d-announce@ietf.org > Cc: weirds@ietf.org > R=E9pondre =E0: internet-drafts@ietf.org >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Web Extensible Internet Registration = Data Service Working Group of the IETF. >=20 > Title : Finding the Authoritative Registration Data = (RDAP) Service > Author : Marc Blanchet > Filename : draft-ietf-weirds-bootstrap-01.txt > Pages : 8 > Date : 2014-02-13 >=20 > Abstract: > This document specifies a method to find which Registration Data > Access Protocol (RDAP) server is authoritative to answer queries for > a requested scope, such as domain names, IP addresses or Autonomous > System numbers, using data available in IANA registries. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-weirds-bootstrap/ >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-weirds-bootstrap-01 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-weirds-bootstrap-01 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt --Apple-Mail=_D2C51752-2CBF-4921-8098-3F7495412DD9 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 New = version based on comments:
- more text on the "longest = match"
- more text on entities
- more text on advice = to clients

It does not touch the recent = comments discussed in apps-discuss. Still waiting for resolution on = this.

Regards, Marc.

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

Objet: = I-D Action: = draft-ietf-weirds-bootstrap-01.txt
Date: 13 f=E9vrier 2014 14:28:19 = HNE
R=E9pondre =E0: internet-drafts@ietf.org
<= /span>


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

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

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


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

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

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

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

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

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

=
= --Apple-Mail=_D2C51752-2CBF-4921-8098-3F7495412DD9-- From julian.reschke@gmx.de Thu Feb 13 08:41: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 716C21A035F for ; Thu, 13 Feb 2014 08:41:19 -0800 (PST) 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, FREEMAIL_FROM=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 usRMCv-bc99u for ; Thu, 13 Feb 2014 08:41:15 -0800 (PST) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 503AB1A033F for ; Thu, 13 Feb 2014 08:41:15 -0800 (PST) Received: from [192.168.1.103] ([217.91.35.233]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MfF6I-1VqGV11Ijq-00Op0c for ; Thu, 13 Feb 2014 17:41:13 +0100 Message-ID: <52FCF5AA.8080407@gmx.de> Date: Thu, 13 Feb 2014 17:41:14 +0100 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: weirds@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:tnZSjROI/OT5msOwiXj5d5ExHwKIUmWvtNEzYTOPOawFNlaLDrF Xyw//CpquDEntNrz9Y1xwPzesjWtMZeXvmrr+lDRsjGzarVlA2t30LdrQ6Xc9FWoJWzeUyo +OCf4Ygkv1ZlZepSLtpv8Yp3i6qJ0kO7rq/nPTFKLremaoPEN+M/HkMk22E7lQDkANXO2e9 37oHp9eHeUXKci3dsxWtw== X-Mailman-Approved-At: Thu, 13 Feb 2014 21:47:43 -0800 Subject: [weirds] Mail regarding draft-ietf-weirds-using-http 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, 13 Feb 2014 16:41:19 -0000 Hi there. Nits: 1) Please update all references to RFC2616 to HTTPbis-P1. 2) It appears that the HTTP response examples have broken status lines. 3) Does application/rdap+json really have a charset parameter? application/json does not. Best regards, Julian From nobody Fri Feb 14 00:57:57 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 955BD1A01D3 for ; Fri, 14 Feb 2014 00:57:54 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 9zoy0GCHEWHG for ; Fri, 14 Feb 2014 00:57:52 -0800 (PST) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 9D1AC1A01AD for ; Fri, 14 Feb 2014 00:57:51 -0800 (PST) X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn Received: from unknown127.0.0.1 (HELO lenovo95e6383c) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 14 Feb 2014 16:57:46 +0800 From: "Linlin Zhou" To: "'Andy Newton'" , References: In-Reply-To: Date: Fri, 14 Feb 2014 16:57:45 +0800 Message-ID: <00b801cf2962$d3d047d0$7b70d770$@cn> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AQHPKChGg+zr3JpoCU+ymicpvh/z8Zq0dJoA Content-Language: zh-cn Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/Sw05-6_2m5kA8fHzxFjZ372wEv0 Subject: Re: [weirds] Useful and Unuseful Searches 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, 14 Feb 2014 08:57:54 -0000 > -----Original Message----- > From: weirds [mailto:weirds-bounces@ietf.org] On Behalf Of Andy Newton > Sent: Thursday, February 13, 2014 3:26 AM > To: weirds@ietf.org > Subject: [weirds] Useful and Unuseful Searches > > In looking at our implementation, it occurred to me that there are two useful > searches we do not include: > > 1) Search of domain names by nameserver name > It could look something like /domains?nsLdhName=XXXXX > > 2) Search of domain names by nameserver IP address > It could look something like /domains?nsIp=YYYYY > We don't have plan to implement these two searches. Regards, Linlin From nobody Fri Feb 14 04:33:14 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B117F1A0221 for ; Fri, 14 Feb 2014 04:33:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 nJZE79p8OkOw for ; Fri, 14 Feb 2014 04:33:11 -0800 (PST) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id E7AAE1A020D for ; Fri, 14 Feb 2014 04:33:10 -0800 (PST) Received: by smtp1.arin.net (Postfix, from userid 323) id 727DF16555E; Fri, 14 Feb 2014 07:33:09 -0500 (EST) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp1.arin.net (Postfix) with ESMTP id E531A165558; Fri, 14 Feb 2014 07:33:08 -0500 (EST) 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; Fri, 14 Feb 2014 07:33:08 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.174]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0328.009; Fri, 14 Feb 2014 07:33:08 -0500 From: Andy Newton To: Julian Reschke , "weirds@ietf.org" Thread-Topic: Mail regarding draft-ietf-weirds-using-http Thread-Index: AQHPKNp5db4pEg4vekKvMNmmrh90G5q0sCkA Date: Fri, 14 Feb 2014 12:33:07 +0000 Message-ID: In-Reply-To: <52FCF5AA.8080407@gmx.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] 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/uNh7e5hODVvPffxo2ZtYm1wxxu4 Subject: Re: [weirds] Mail regarding draft-ietf-weirds-using-http 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, 14 Feb 2014 12:33:12 -0000 Thanks Julian. -andy On 2/13/14, 11:41 AM, "Julian Reschke" wrote: >Hi there. > >Nits: > >1) Please update all references to RFC2616 to HTTPbis-P1. > >2) It appears that the HTTP response examples have broken status lines. > >3) Does application/rdap+json really have a charset parameter? >application/json does not. > >Best regards, Julian > From nobody Fri Feb 14 13:05:27 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB661A03E7; Fri, 14 Feb 2014 13:05:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YIo2nTsx482L; Fri, 14 Feb 2014 13:05:20 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A3F691A0351; Fri, 14 Feb 2014 13:05:17 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140214210517.18338.89487.idtracker@ietfa.amsl.com> Date: Fri, 14 Feb 2014 13:05:17 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/dbpL7uxs_zutxV6R21nHKaPEj0Y Cc: weirds@ietf.org Subject: [weirds] I-D Action: draft-ietf-weirds-redirects-03.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 21:05:22 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web Extensible Internet Registration Data Service Working Group of the IETF. Title : Redirection Service for Registration Data Access Protocol Authors : Carlos M. Martinez Linlin Zhou Gerardo Rada Filename : draft-ietf-weirds-redirects-03.txt Pages : 10 Date : 2014-02-14 Abstract: The traditional WHOIS protocol has several important shortcomings, and over the past few years several approaches to a better Registration Data Access Protocol (RDAP) have been discussed and proposed. It is worth noting that the term WHOIS is sometimes used interchangeably to mean either (a) the registration data itself or (b) the protocol used to access registration data Among these shortcomings, different registries operate different WHOIS services. For users this means that several WHOIS queries to different registries may be necessary in order to obtain data for a given resource. This document describes a redirection service for RDAP queries. This service allows clients to query a single RDAP service and expect either an authoritative answer or a redirection hint pointing to another, possibly authoritative, RDAP server. The solution implemented proposed here applies to Regional Internet Registries(RIRs) and Domain Name Registries(DNRs). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-weirds-redirects/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-weirds-redirects-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-weirds-redirects-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Feb 14 13:13: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 D97421A0411 for ; Fri, 14 Feb 2014 13:13:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.729 X-Spam-Level: X-Spam-Status: No, score=-0.729 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, MISSING_HEADERS=1.021, 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 KT5WbbvgLZgY for ; Fri, 14 Feb 2014 13:13:03 -0800 (PST) Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 58BF81A0397 for ; Fri, 14 Feb 2014 13:13:02 -0800 (PST) Received: by mail-pa0-f44.google.com with SMTP id kq14so12813361pab.31 for ; Fri, 14 Feb 2014 13:13:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=SqqqJcwrZ+ocbQvLYRG3vOn+VL3/TIrUsDs1FbgCgQE=; b=H1YYz/pijm0N77+vCNEpy+1TrrXUHgBn4x2lAOW3ITvn5yAjgMC1eG66ImjMbA4qxQ mJvtZjNOw7YTBK7Ifzgpv0xeS18F7csicPyp0GYVQeeRGP/m1n+qC5xPJCEMd3/sCl9R NTTWeGUo+dOxUtohtMGHmNWz/Y1HVC97Wy5JeYWp2CInJtEjB9aNKHdek/3L8TNFKesy hR3w1Q8owFcl0AZUrOWN6FVAMPFWGjKQw97BP3ijB6GYKbBuoI0zCc+z8U/zU8f+/GrP Y4dgTdd1La92zty38MLgjTCSCdguYgdL0B46gw2b6wqUf2FUGwaTqLg2oITu25k243Wk SZSQ== X-Received: by 10.68.12.74 with SMTP id w10mr11635560pbb.39.1392412380891; Fri, 14 Feb 2014 13:13:00 -0800 (PST) Received: from Carloss-MacBook-Pro.local ([12.217.29.66]) by mx.google.com with ESMTPSA id ss2sm49334048pab.8.2014.02.14.13.12.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 14 Feb 2014 13:13:00 -0800 (PST) Message-ID: <52FE86D9.7080002@gmail.com> Date: Fri, 14 Feb 2014 13:12:57 -0800 From: "Carlos M. Martinez" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 CC: weirds@ietf.org References: <20140214210517.18338.89487.idtracker@ietfa.amsl.com> In-Reply-To: <20140214210517.18338.89487.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/1-qRxo1AiufEH83kskPtuM1RHEg Subject: Re: [weirds] I-D Action: draft-ietf-weirds-redirects-03.txt X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: carlos@lacnic.net 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, 14 Feb 2014 21:13:05 -0000 Mostly a keepalive version, some minor editorial corrections. My target is to get this mostly done on/after London. regards ~Carlos On 2/14/14, 1:05 PM, internet-drafts@ietf.org wrote: > > 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 : Redirection Service for Registration Data Access Protocol > Authors : Carlos M. Martinez > Linlin Zhou > Gerardo Rada > Filename : draft-ietf-weirds-redirects-03.txt > Pages : 10 > Date : 2014-02-14 > > Abstract: > The traditional WHOIS protocol has several important shortcomings, > and over the past few years several approaches to a better > Registration Data Access Protocol (RDAP) have been discussed and > proposed. > > It is worth noting that the term WHOIS is sometimes used > interchangeably to mean either (a) the registration data itself or > (b) the protocol used to access registration data > > Among these shortcomings, different registries operate different > WHOIS services. For users this means that several WHOIS queries to > different registries may be necessary in order to obtain data for a > given resource. > > This document describes a redirection service for RDAP queries. This > service allows clients to query a single RDAP service and expect > either an authoritative answer or a redirection hint pointing to > another, possibly authoritative, RDAP server. > > The solution implemented proposed here applies to Regional Internet > Registries(RIRs) and Domain Name Registries(DNRs). > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-weirds-redirects/ > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-weirds-redirects-03 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-weirds-redirects-03 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds > From nobody Tue Feb 18 23:08:52 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 34D8F1A055E for ; Tue, 18 Feb 2014 23:08:51 -0800 (PST) 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 N6qrxYjACunE for ; Tue, 18 Feb 2014 23:08:49 -0800 (PST) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id BBA301A036C for ; Tue, 18 Feb 2014 23:08:48 -0800 (PST) Received: by mail-wg0-f48.google.com with SMTP id a1so4086458wgh.27 for ; Tue, 18 Feb 2014 23:08:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=q4UZqxwDBxzlj0UK/Fm6JTo3BD2hMv6MOG82C+JLxO8=; b=sZ7F77QszKjO/NCpLU4QKLni29H976Rjo13K4e9Yg3JqMRCezH0e8o8S5fbU1Fcgz4 Z/UD5Nk4DLI8/QP0SzLnaOIONxyhhXxyzlYNj9dlYcKZ+dKdf1VrklvWvFFcswYHj0nc 6dnedtcK47iw5GepnIADsklURmr3uf3hkz1sPAwtmXQlb5mfYCAvXHW6pvyXrepZ//cv jfaYJwq0kkC8l/Ikq+s7mKAP5bCf2LeUKpg3TAG9ygUcbu6G42iItDO6X6HtpF4wzEdu gxheoKriGscheFlb8fZ7FCIiaZLDEZgraygai565Ryma5K8kusXkUTTbbpCUZBEnKW/q kmiA== MIME-Version: 1.0 X-Received: by 10.194.86.200 with SMTP id r8mr11122318wjz.49.1392793725196; Tue, 18 Feb 2014 23:08:45 -0800 (PST) Received: by 10.180.90.132 with HTTP; Tue, 18 Feb 2014 23:08:45 -0800 (PST) In-Reply-To: <52D988D0.7020308@viagenie.ca> References: <52D988D0.7020308@viagenie.ca> Date: Tue, 18 Feb 2014 23:08:45 -0800 Message-ID: From: "Murray S. Kucherawy" To: Simon Perreault Content-Type: multipart/alternative; boundary=089e010d86123c5de804f2bd0f8c Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/e-nssr_Y16KDXx2j1JWK9CcY0kk Cc: "weirds@ietf.org" Subject: Re: [weirds] IETF 89 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, 19 Feb 2014 07:08:51 -0000 --089e010d86123c5de804f2bd0f8c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Colleagues, The draft agenda is a bit overdue. So far the agenda contains a 15 minute session for interop results discussion and a 20 minute session for talking about bootstrapping, plus a few minutes for administrivia up front. We have a 2.5 hour slot allocated, leaving 110 minutes for "any other business". Do we need time to talk about the .well-known/templates/etc. issue this time, or is that pretty much resolved (debate on apps-discuss notwithstanding)? Are there any open issues on any of the other documents, or are they all ready for WGLC (except for bootstrapping)? I'll upload the agenda sometime tomorrow evening based on the feedback I get here (or not). -MSK On Fri, Jan 17, 2014 at 11:47 AM, Simon Perreault < simon.perreault@viagenie.ca> wrote: > Le 2014-01-17 14:02, Murray S. Kucherawy a =E9crit : > > Please propose agenda items for London. >> > > 15 minutes for discussion of interop results. > > Thanks, > Simon > -- > DTN made easy, lean, and smart --> http://postellation.viagenie.ca > NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca > STUN/TURN server --> http://numb.viagenie.ca > > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds > --089e010d86123c5de804f2bd0f8c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Colleagues,

The draft agenda is a bit ove= rdue.=A0 So far the agenda contains a 15 minute session for interop results= discussion and a 20 minute session for talking about bootstrapping, plus a= few minutes for administrivia up front.=A0 We have a 2.5 hour slot allocat= ed, leaving 110 minutes for "any other business".

Do we need time to talk about the .well-known/templates/etc. issue this= time, or is that pretty much resolved (debate on apps-discuss notwithstand= ing)?

Are there any open issues on any of the other documents,= or are they all ready for WGLC (except for bootstrapping)?

I'll upload the agenda sometime tomorrow evening based o= n the feedback I get here (or not).

-MSK



On Fri, Jan 17, 2014 = at 11:47 AM, Simon Perreault <simon.perreault@viagenie.ca>= ; wrote:
Le 2014-01-17 14:02, Murray S. Kucherawy a = =E9crit :

Please propose agenda items for London.

15 minutes for discussion of interop results.

Thanks,
Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source =A0 =A0 =A0 =A0--> http://ecdysis.viagenie.ca
STUN/TURN server =A0 =A0 =A0 =A0 =A0 =A0 =A0 --> http://numb.viagenie.ca

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

--089e010d86123c5de804f2bd0f8c-- From nobody Wed Feb 19 04:04: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 721911A0593 for ; Wed, 19 Feb 2014 04:04:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7u2d4apyuzgr for ; Wed, 19 Feb 2014 04:04:39 -0800 (PST) Received: from exprod6og118.obsmtp.com (exprod6og118.obsmtp.com [64.18.1.233]) by ietfa.amsl.com (Postfix) with ESMTP id BD0121A0481 for ; Wed, 19 Feb 2014 04:04:36 -0800 (PST) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob118.postini.com ([64.18.5.12]) with SMTP ID DSNKUwSd0X5EQZk2IAt1YJvn8RNzrTxqy9Ez@postini.com; Wed, 19 Feb 2014 04:04:36 PST 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 s1JC4WXu008587 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Feb 2014 07:04:32 -0500 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Wed, 19 Feb 2014 07:04:32 -0500 From: "Hollenbeck, Scott" To: "Murray S. Kucherawy" , Simon Perreault Thread-Topic: [weirds] IETF 89 scheduling Thread-Index: AQHPLUFyVuzvUm4660aua98rH6rAfZq8en1g Date: Wed, 19 Feb 2014 12:04:31 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F4934E3F2@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <52D988D0.7020308@viagenie.ca> 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: multipart/alternative; boundary="_000_831693C2CDA2E849A7D7A712B24E257F4934E3F2BRN1WNEXMBX01vc_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/bDPxtuzX5MDb6TyoTCjQVntqAZ8 Cc: "weirds@ietf.org" Subject: Re: [weirds] IETF 89 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, 19 Feb 2014 12:04:42 -0000 --_000_831693C2CDA2E849A7D7A712B24E257F4934E3F2BRN1WNEXMBX01vc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable From: weirds [mailto:weirds-bounces@ietf.org] On Behalf Of Murray S. Kucher= awy Sent: Wednesday, February 19, 2014 2:09 AM To: Simon Perreault Cc: weirds@ietf.org Subject: Re: [weirds] IETF 89 scheduling Colleagues, The draft agenda is a bit overdue. So far the agenda contains a 15 minute = session for interop results discussion and a 20 minute session for talking = about bootstrapping, plus a few minutes for administrivia up front. We hav= e a 2.5 hour slot allocated, leaving 110 minutes for "any other business". Do we need time to talk about the .well-known/templates/etc. issue this tim= e, or is that pretty much resolved (debate on apps-discuss notwithstanding)= ? If it's been resolved I'm unaware of the resolution and no one has suggeste= d that changes need to be made to rdap-query, which still includes .well-kn= own. I'd very much like to see this on the agenda. Scott --_000_831693C2CDA2E849A7D7A712B24E257F4934E3F2BRN1WNEXMBX01vc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

From: weirds [= mailto:weirds-bounces@ietf.org] On Behalf Of Murray S. Kucherawy
Sent: Wednesday, February 19, 2014 2:09 AM
To: Simon Perreault
Cc: weirds@ietf.org
Subject: Re: [weirds] IETF 89 scheduling

 

Colleagues,

The draft agenda is a bit overdue.  So far the agenda contains a 15 mi= nute session for interop results discussion and a 20 minute session for tal= king about bootstrapping, plus a few minutes for administrivia up front.&nb= sp; We have a 2.5 hour slot allocated, leaving 110 minutes for "any other business".

Do we need time to talk about the .well-known/templates/etc. issue this tim= e, or is that pretty much resolved (debate on apps-discuss notwithstanding)= ?

If it’= ;s been resolved I’m unaware of the resolution and no one has suggest= ed that changes need to be made to rdap-query, which still includes .well-k= nown. I’d very much like to see this on the agenda.

Scott<= /o:p>

--_000_831693C2CDA2E849A7D7A712B24E257F4934E3F2BRN1WNEXMBX01vc_-- From nobody Wed Feb 19 05:14:58 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 6B8141A047A for ; Wed, 19 Feb 2014 05:14:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, 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 0BJIVymjJ3Fa for ; Wed, 19 Feb 2014 05:14:54 -0800 (PST) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id B328F1A03E4 for ; Wed, 19 Feb 2014 05:14:54 -0800 (PST) Received: from h195.viagenie.ca (h195.viagenie.ca [206.123.31.195]) by jazz.viagenie.ca (Postfix) with ESMTPSA id EA3AD41172; Wed, 19 Feb 2014 08:14:50 -0500 (EST) Content-Type: multipart/alternative; boundary="Apple-Mail=_93388825-72F6-488D-B499-4404AF042283" Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Marc Blanchet In-Reply-To: Date: Wed, 19 Feb 2014 08:14:49 -0500 Message-Id: <6399D67E-2C8F-4282-8285-6D6F27A02EF1@viagenie.ca> References: <52D988D0.7020308@viagenie.ca> To: "Murray S. Kucherawy" X-Mailer: Apple Mail (2.1827) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/QHlRYLs8mnXlz2IbqSLls4RDJf4 Cc: "weirds@ietf.org" Subject: Re: [weirds] IETF 89 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, 19 Feb 2014 13:14:57 -0000 --Apple-Mail=_93388825-72F6-488D-B499-4404AF042283 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Le 2014-02-19 =E0 02:08, Murray S. Kucherawy a = =E9crit : > Colleagues, >=20 > The draft agenda is a bit overdue. So far the agenda contains a 15 = minute session for interop results discussion and a 20 minute session = for talking about bootstrapping, plus a few minutes for administrivia up = front. We have a 2.5 hour slot allocated, leaving 110 minutes for "any = other business". >=20 > Do we need time to talk about the .well-known/templates/etc. issue = this time, or is that pretty much resolved (debate on apps-discuss = notwithstanding)? My take: - all specs are pretty stable and "done". bootstrap included. - but: the .well-known/template that affects both bootstrap and query is = on-going. This should be our top priority to resolve. When resolved (and = whatever doc updated if needed), then I think we should go LC for all of = them. therefore, I think we should spend as much time needed to resolve the = .well-known-template-uri discussion. Maybe by making sure the = appropriate parties are in the room... hint to the chairs... Regards, Marc. >=20 > Are there any open issues on any of the other documents, or are they = all ready for WGLC (except for bootstrapping)? >=20 > I'll upload the agenda sometime tomorrow evening based on the feedback = I get here (or not). >=20 > -MSK >=20 >=20 >=20 > On Fri, Jan 17, 2014 at 11:47 AM, Simon Perreault = wrote: > Le 2014-01-17 14:02, Murray S. Kucherawy a =E9crit : >=20 > Please propose agenda items for London. >=20 > 15 minutes for discussion of interop results. >=20 > Thanks, > Simon > --=20 > DTN made easy, lean, and smart --> http://postellation.viagenie.ca > NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca > STUN/TURN server --> http://numb.viagenie.ca >=20 > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds >=20 > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds --Apple-Mail=_93388825-72F6-488D-B499-4404AF042283 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Le = 2014-02-19 =E0 02:08, Murray S. Kucherawy <superuser@gmail.com> a =E9crit = :

Colleagues,

The draft = agenda is a bit overdue.  So far the agenda contains a 15 minute = session for interop results discussion and a 20 minute session for = talking about bootstrapping, plus a few minutes for administrivia up = front.  We have a 2.5 hour slot allocated, leaving 110 minutes for = "any other business".

Do we need time to talk about the .well-known/templates/etc. issue = this time, or is that pretty much resolved (debate on apps-discuss = notwithstanding)?

My= take:
- all specs are pretty stable and "done". bootstrap = included.
- but: the .well-known/template that affects both = bootstrap and query is on-going. This should be our top priority to = resolve. When resolved (and whatever doc updated if needed), then I = think we should go LC for all of = them.

therefore, I think we should spend as = much time needed to resolve the .well-known-template-uri discussion. = Maybe by making sure the appropriate parties are in the room... hint to = the chairs...

Regards, = Marc.


Are there any open issues on any of the = other documents, or are they all ready for WGLC (except for = bootstrapping)?

I'll upload the agenda sometime tomorrow evening based on = the feedback I get here (or not).

-MSK



On Fri, Jan 17, = 2014 at 11:47 AM, Simon Perreault <simon.perreault@viagenie.ca> wrote:
Le 2014-01-17 14:02, = Murray S. Kucherawy a =E9crit :

Please propose agenda items for London.

15 minutes for discussion of interop results.

Thanks,
Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> = http://numb.viagenie.ca

_______________________________________________
weirds mailing list
weirds@ietf.org
https://www.ietf.org/mailman/listinfo/weirds<= br>

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

= --Apple-Mail=_93388825-72F6-488D-B499-4404AF042283-- From nobody Wed Feb 19 06:07: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 3EC641A03E8 for ; Wed, 19 Feb 2014 06:07:33 -0800 (PST) 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 euH5kftnbgPd for ; Wed, 19 Feb 2014 06:07:31 -0800 (PST) Received: from exprod6og106.obsmtp.com (exprod6og106.obsmtp.com [64.18.1.191]) by ietfa.amsl.com (Postfix) with ESMTP id 7012D1A05D2 for ; Wed, 19 Feb 2014 06:07:16 -0800 (PST) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob106.postini.com ([64.18.5.12]) with SMTP ID DSNKUwS6kdq5YqkHtrOnI8Szli+dPO8UWc8k@postini.com; Wed, 19 Feb 2014 06:07:28 PST 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 s1JE7Cs8012131 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Feb 2014 09:07:12 -0500 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Wed, 19 Feb 2014 09:07:12 -0500 From: "Hollenbeck, Scott" To: John Levine , "weirds@ietf.org" Thread-Topic: [weirds] Useful and Unuseful Searches Thread-Index: AQHPKChGg+zr3JpoCU+ymicpvh/z8ZqziGaAgAkdi/A= Date: Wed, 19 Feb 2014 14:07:11 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F4934E744@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <20140213134943.2126.qmail@joyce.lan> In-Reply-To: <20140213134943.2126.qmail@joyce.lan> 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/M8xw4miEiCwkdFLOlCJBlUWKNKc Subject: Re: [weirds] Useful and Unuseful Searches 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, 19 Feb 2014 14:07:33 -0000 > -----Original Message----- > From: weirds [mailto:weirds-bounces@ietf.org] On Behalf Of John Levine > Sent: Thursday, February 13, 2014 8:50 AM > To: weirds@ietf.org > Subject: Re: [weirds] Useful and Unuseful Searches >=20 > >1) Search of domain names by nameserver name > > It could look something like /domains?nsLdhName=3DXXXXX > > > >2) Search of domain names by nameserver IP address > > It could look something like /domains?nsIp=3DYYYYY >=20 > They sound swell, but I would be reluctant to add them until we hear > from a registry that plans to implement them. It's too early for me to say anything publicly about Verisign's implementat= ion plans. I did, however, run this by the appropriate development manager = and he didn't run away screaming. I'm inclined to include them as long as w= e can place limits on the number of records returned. Scott From nobody Wed Feb 19 09:01: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 CB04B1A040F for ; Wed, 19 Feb 2014 09:01:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 hLlaWHnaZbYc for ; Wed, 19 Feb 2014 09:01:40 -0800 (PST) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id BF5E81A0241 for ; Wed, 19 Feb 2014 09:01:40 -0800 (PST) Received: by smtp1.arin.net (Postfix, from userid 323) id 70E151652C9; Wed, 19 Feb 2014 12:01:37 -0500 (EST) Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp1.arin.net (Postfix) with ESMTP id 9514C1652C6; Wed, 19 Feb 2014 12:01:36 -0500 (EST) 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; Wed, 19 Feb 2014 12:01:28 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0328.009; Wed, 19 Feb 2014 12:01:24 -0500 From: Andy Newton To: "Hollenbeck, Scott" , John Levine , "weirds@ietf.org" Thread-Topic: [weirds] Useful and Unuseful Searches Thread-Index: AQHPKChGg+zr3JpoCU+ymicpvh/z8ZqziGaAgAkdi/CAADInAA== Date: Wed, 19 Feb 2014 17:01:23 +0000 Message-ID: In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4934E744@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/ErrUaIokv6D9UouPjaQ7PQf_748 Subject: Re: [weirds] Useful and Unuseful Searches 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, 19 Feb 2014 17:01:43 -0000 On 2/19/14, 9:07 AM, "Hollenbeck, Scott" wrote: >> -----Original Message----- >> From: weirds [mailto:weirds-bounces@ietf.org] On Behalf Of John Levine >> Sent: Thursday, February 13, 2014 8:50 AM >> To: weirds@ietf.org >> Subject: Re: [weirds] Useful and Unuseful Searches >>=20 >> >1) Search of domain names by nameserver name >> > It could look something like /domains?nsLdhName=3DXXXXX >> > >> >2) Search of domain names by nameserver IP address >> > It could look something like /domains?nsIp=3DYYYYY >>=20 >> They sound swell, but I would be reluctant to add them until we hear >> from a registry that plans to implement them. > >It's too early for me to say anything publicly about Verisign's >implementation plans. I did, however, run this by the appropriate >development manager and he didn't run away screaming. I'm inclined to >include them as long as we can place limits on the number of records >returned. As with any search, yes you can. FYI, the ARIN server now implements #1 (we don=B9t collect A records, so we can=B9t do #2). It was fairly trivial to implement. Also, NicInfo was updated to support both #1 and #2. That was also fairly trivial once the /domains?name=3DXXXX search was implemented. -andy From nobody Wed Feb 19 09:09: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 B97151A05BB for ; Wed, 19 Feb 2014 09:09:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.447 X-Spam-Level: X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548] 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 2QiNdg7LDBPR for ; Wed, 19 Feb 2014 09:09:13 -0800 (PST) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 2E58D1A0209 for ; Wed, 19 Feb 2014 09:09:13 -0800 (PST) Received: by smtp2.arin.net (Postfix, from userid 323) id CBBD121365F; Wed, 19 Feb 2014 12:09:09 -0500 (EST) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp2.arin.net (Postfix) with ESMTP id 36685213506; Wed, 19 Feb 2014 12:09:09 -0500 (EST) 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, 19 Feb 2014 12:09:08 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0347.000; Wed, 19 Feb 2014 12:09:08 -0500 From: Andy Newton To: Marc Blanchet , "Murray S. Kucherawy" Thread-Topic: [weirds] IETF 89 scheduling Thread-Index: AQHPE7a/B39iq4ksWkGcd1m/2Vu5JZqJpksAgDMI9ICAAGZHgP//7aEA Date: Wed, 19 Feb 2014 17:09:08 +0000 Message-ID: In-Reply-To: <6399D67E-2C8F-4282-8285-6D6F27A02EF1@viagenie.ca> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] Content-Type: multipart/alternative; boundary="_000_CF2A4DA42C972andyarinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/iVKk5nGF6kd_WuoSkZfMwLQte5U Cc: "weirds@ietf.org" Subject: Re: [weirds] IETF 89 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, 19 Feb 2014 17:09:16 -0000 --_000_CF2A4DA42C972andyarinnet_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable From: Marc Blanchet > Date: Wednesday, February 19, 2014 at 8:14 AM To: "Murray S. Kucherawy" > Cc: "weirds@ietf.org" > Subject: Re: [weirds] IETF 89 scheduling - but: the .well-known/template that affects both bootstrap and query is on= -going. This should be our top priority to resolve. When resolved (and what= ever doc updated if needed), then I think we should go LC for all of them. I agree that this should be our top priority. Reviewers on the apps-discuss= list mentioned that we could drop .well-known and that met with no objecti= ons. So I think .well-known can be dropped from rdap-query. Now the templates discussion is another issue entirely. On the apps-discuss= list I noted that the architectural issue was that they wanted us to avoid= URI collisions and that templates were just one method for doing so. Since= our bootstrap method allows for arbitrary base URIs, RDAP does not suffer = from URI collisions. So far that assertion has not been challenged on apps-= discuss. However, it most likely needs to be explicitly discussed at the me= eting (and on THIS list). -andy --_000_CF2A4DA42C972andyarinnet_ Content-Type: text/html; charset="us-ascii" Content-ID: <8945976573403B49B318FADB374B89AE@corp.arin.net> Content-Transfer-Encoding: quoted-printable
From: Marc Blanchet <marc.blanchet@viagenie.ca>
Date: Wednesday, February 19, 2014 = at 8:14 AM
To: "Murray S. Kucherawy"= <superuser@gmail.com>
Cc: "weirds@ietf.org" <= weirds@ietf.org>
Subject: Re: [weirds] IETF 89 sched= uling

- but: the .well-known/template that affects both bootstrap and query is on-= going. This should be our top priority to resolve. When resolved (and whate= ver doc updated if needed), then I think we should go LC for all of them.

I agree that this should be our top priority. Reviewers on the apps-di= scuss list mentioned that we could drop .well-known and that met with no ob= jections. So I think .well-known can be dropped from rdap-query.

Now the templates discussion is another issue entirely. On the apps-di= scuss list I noted that the architectural issue was that they wanted us to = avoid URI collisions and that templates were just one method for doing so. = Since our bootstrap method allows for arbitrary base URIs, RDAP does not suffer from URI collisions. So far = that assertion has not been challenged on apps-discuss. However, it most li= kely needs to be explicitly discussed at the meeting (and on THIS list).

-andy
--_000_CF2A4DA42C972andyarinnet_-- From nobody Wed Feb 19 09:49: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 852421A051B for ; Wed, 19 Feb 2014 09:49:29 -0800 (PST) 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 EVZzg2GRSzFt for ; Wed, 19 Feb 2014 09:49:28 -0800 (PST) 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 D0F931A03CE for ; Wed, 19 Feb 2014 09:49:27 -0800 (PST) Received: (qmail 30566 invoked from network); 19 Feb 2014 17:49: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:references:mime-version:content-type:user-agent:cleverness; s=7765.5304eea3.k1402; i=johnl-iecc.com@submit.iecc.com; bh=xVq5VctB3k0hgXhW73Wks9+46m/ZpRujaaPIyN2dV7k=; b=OdI+ruEM4yyHUfA9jgNsFUGn3Os7I/z134+3K315gu91wCYSeovREqE0g5eKzuJuxIn4fIs0oQED4oaODTZFL1XE52YJ9AKwJc27/Fkk8kxJ/Simi4ObXrq3jl6Ks9GcD4AWly5xRdV8HvanAV/MJckDghbYpZh6zy8Pokno5g7XKHm0/bwSaR6rj4/h9lIybNg9w5coQE+48Ax0Go5avAqU0A7UKZZItHkTRd6Lh8ynX5HVM0PCYHQ8NTVjR384 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=7765.5304eea3.k1402; olt=johnl-iecc.com@submit.iecc.com; bh=xVq5VctB3k0hgXhW73Wks9+46m/ZpRujaaPIyN2dV7k=; b=qTGzL4fo3hNd/3ftiXLtw9CJBUCT5jK+FkRsDkxlDMkIKkhFXGHnUTLU/U5Jf+EL+3pTXHbPglE2el5S+J4Tw5OHGyfSI5aIGTj+sZ/meBtSvoA9TavPWQNmnuuD8zknO76tuxL3KzASnsfG5PgF3VTm9k0rB50KZ+tdN3uK6vDwcetZ8St0tk6RzPRkwllOTZyroWxFPSkyugvOJR3Ca2wqhUJvrPjIQRubbG7DRHV6XffrsLBE5Gwr02X1efpx Received: from [192.168.0.102] ([109.62.74.131]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 19 Feb 2014 17:49:22 -0000 Date: 19 Feb 2014 13:49:20 -0400 Message-ID: From: "John R Levine" To: "Andy Newton" In-Reply-To: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) Cleverness: None detected MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3825401791-1378911030-1392832163=:2137" Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/RviQO9XliSbyn0rou4bEcp1ZZHk Cc: "weirds@ietf.org" Subject: Re: [weirds] Useful and Unuseful Searches 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, 19 Feb 2014 17:49:29 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3825401791-1378911030-1392832163=:2137 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT >>>> 1) Search of domain names by nameserver name >>>> It could look something like /domains?nsLdhName=XXXXX >>>> >>>> 2) Search of domain names by nameserver IP address >>>> It could look something like /domains?nsIp=YYYYY >> It's too early for me to say anything publicly about Verisign's >> implementation plans. I did, however, run this by the appropriate >> development manager and he didn't run away screaming. I'm inclined to >> include them as long as we can place limits on the number of records >> returned. > > As with any search, yes you can. > > FYI, the ARIN server now implements #1 (we don¹t collect A records, so we > can¹t do #2). It was fairly trivial to implement. > Also, NicInfo was updated to support both #1 and #2. That was also fairly > trivial once the /domains?name=XXXX search was implemented. Sounds like there's plenty of interest to merit adding them. This is just the kind of confirmation I was looking for. Tnx. R's de Guadeloupe, John --3825401791-1378911030-1392832163=:2137-- From nobody Wed Feb 19 10:23:39 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 4D3FA1A04F1 for ; Wed, 19 Feb 2014 10:23:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 dgqfu_u3ig9x for ; Wed, 19 Feb 2014 10:23:35 -0800 (PST) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 014FF1A04CC for ; Wed, 19 Feb 2014 10:23:35 -0800 (PST) Received: by smtp2.arin.net (Postfix, from userid 323) id AD81021367C; Wed, 19 Feb 2014 13:23:31 -0500 (EST) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp2.arin.net (Postfix) with ESMTP id 48A142135FF for ; Wed, 19 Feb 2014 13:23:31 -0500 (EST) 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, 19 Feb 2014 13:23:31 -0500 Received: from CHAXCH01.corp.arin.net ([169.254.1.88]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0347.000; Wed, 19 Feb 2014 13:23:30 -0500 From: Andy Newton To: "weirds@ietf.org" Thread-Topic: bootstrapping Thread-Index: AQHPLZ+wlro1GEXGpUiRy2PZ8tcHpw== Date: Wed, 19 Feb 2014 18:23:29 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.7.130812 x-originating-ip: [10.1.30.36] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/vdCkJiRERNpkEn37pTCXWoXVVd0 Subject: [weirds] bootstrapping 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, 19 Feb 2014 18:23:37 -0000 Section 6 of the current draft says that clients are fetching an XML file. Why can=B9t it be a JSON file? And while we are at it, why can=B9t the registry use the =B3links=B2 data structure from Section 5.2 of json-respon= se? Since clients already have to know how to parse this, it would be less work for them. Using the links structure, each link object could be constructed as follows: 1) value is the domain name, v4 or v6 address, or the asn 2) rel is a relationship specifying the query type supported (so each .EXAMPLE might have multiple entries, one for each query type they support. E.g. =B3domainlookup=B2 for /domain, =B3domainsearchbyname=B2 for /domains?name=3Dxxx, etc...) 3) href is the base URI for RDAP 4) hreflang and title are optional but the registry can put whatever they want 5) media is best left out I guess 6) type should be =B3application/rdap+json=B2 -andy From nobody Wed Feb 19 11:26:24 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D1F31A05E1 for ; Wed, 19 Feb 2014 11:26:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.449 X-Spam-Level: X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, 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 iYQ6jqs_tNW8 for ; Wed, 19 Feb 2014 11:26:21 -0800 (PST) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 50D141A01F0 for ; Wed, 19 Feb 2014 11:26:21 -0800 (PST) Received: from [IPv6:2620:0:230:2002::1001] (unknown [IPv6:2620:0:230:2002::1001]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 1D436403C0; Wed, 19 Feb 2014 14:26:16 -0500 (EST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Marc Blanchet In-Reply-To: Date: Wed, 19 Feb 2014 14:26:15 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Andy Newton X-Mailer: Apple Mail (2.1827) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/rFe8HpS4ZA8NK4kabBLJ_kSDudI Cc: "weirds@ietf.org" Subject: Re: [weirds] bootstrapping 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, 19 Feb 2014 19:26:23 -0000 Le 2014-02-19 =E0 13:23, Andy Newton a =E9crit : > Section 6 of the current draft says that clients are fetching an XML = file. >=20 > Why can=B9t it be a JSON file? - good question. The default was the current structured format used by = all IANA registries. - it could be both: i.e. an XML normative format and an XSLT that = convert its to json, and both formats being offered by IANA. I think = that is doable and can be asked to=20 IANA. I'll chat with IANA about that. > And while we are at it, why can=B9t the > registry use the =B3links=B2 data structure from Section 5.2 of = json-response? > Since clients already have to know how to parse this, it would be less > work for them. >=20 > Using the links structure, each link object could be constructed as > follows: > 1) value is the domain name, v4 or v6 address, or the asn > 2) rel is a relationship specifying the query type supported (so each > .EXAMPLE might have multiple entries, one for each query type they > support. E.g. =B3domainlookup=B2 for /domain, =B3domainsearchbyname=B2 = for > /domains?name=3Dxxx, etc...) > 3) href is the base URI for RDAP > 4) hreflang and title are optional but the registry can put whatever = they > want > 5) media is best left out I guess > 6) type should be =B3application/rdap+json=B2 >=20 > -andy >=20 > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds From nobody Wed Feb 19 12:40:41 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63F1D1A04D6 for ; Wed, 19 Feb 2014 12:40:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.747 X-Spam-Level: X-Spam-Status: No, score=-4.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548] 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 TV13i14nA3Dk for ; Wed, 19 Feb 2014 12:40:38 -0800 (PST) Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id C4F831A022E for ; Wed, 19 Feb 2014 12:40:38 -0800 (PST) Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Wed, 19 Feb 2014 12:40:35 -0800 From: Kim Davies To: Marc Blanchet Date: Wed, 19 Feb 2014 12:41:01 -0800 Thread-Topic: [weirds] bootstrapping Thread-Index: Ac8tstaZp1mQSr3bRU+Yi8CkEHxaRA== Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_D6BA74DF53DA4F4999820217AFCC410Ficannorg_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/qdNjCBG5NlCGejKqF-PJfb0v-wM Cc: "weirds@ietf.org" Subject: Re: [weirds] bootstrapping 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, 19 Feb 2014 20:40:40 -0000 --_000_D6BA74DF53DA4F4999820217AFCC410Ficannorg_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Feb 19, 2014, at 11:26 AM, Marc Blanchet > wrote: Le 2014-02-19 =E0 13:23, Andy Newton > = a =E9crit : Section 6 of the current draft says that clients are fetching an XML file. Why can=B9t it be a JSON file? - good question. The default was the current structured format used by all = IANA registries. - it could be both: i.e. an XML normative format and an XSLT that convert i= ts to json, and both formats being offered by IANA. I think that is doable = and can be asked to IANA. I'll chat with IANA about that. It should be no problem. Our preference is not to need to support a prolife= ration of differing formats, but this seems relatively straightforward to m= aintain. kim --_000_D6BA74DF53DA4F4999820217AFCC410Ficannorg_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
On Feb 19,= 2014, at 11:26 AM, Marc Blanchet <marc.blanchet@viagenie.ca> wrote:

Le 2014-02-19 =E0 13:23, Andy Newton <andy@arin.net> a =E9crit :

Section 6 of the current draft says that clients are fet= ching an XML file.

Why can=B9t it be a JSON file?
- good question. The default was the current structured format used by al= l IANA registries.
- it could be both: i.e. an XML normative format and = an XSLT that convert its to json, and both formats being offered by IANA. I= think that is doable and can be asked to 
IANA. I'll chat with IANA about that.

It should be no problem. Our preference is not to need to = support a proliferation of differing formats, but this seems relatively str= aightforward to maintain.

kim

= --_000_D6BA74DF53DA4F4999820217AFCC410Ficannorg_-- From nobody Fri Feb 21 00:26: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 5D3E41A0006 for ; Fri, 21 Feb 2014 00:26:41 -0800 (PST) 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 6neW2ugK7yNV for ; Fri, 21 Feb 2014 00:26:39 -0800 (PST) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE621A04E1 for ; Fri, 21 Feb 2014 00:26:38 -0800 (PST) Received: by mail-wg0-f47.google.com with SMTP id k14so2248263wgh.2 for ; Fri, 21 Feb 2014 00:26:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+8CZ1ePXqS75aPfb9ub0aLY0FieyRrbrYhH8/xGU6tI=; b=fw3Cu6oTuQlxdcyecwrr4PfBFZ3r0DI3Kdss2WK4lzMHXyExgrWZ+m0glHKGkB+1GJ M5liaof/pje6w1dbJvETV31wbs8Cs6zYu8Dk1LFL/5RCsY4RO6m0gnjD3rEKqaRK1tX7 /Imf7n2tzFu3L4H36gelrDzr+WI/moHwgmQB+r59HzFkrlLFU2dvPhaEKl6CxkK30shp fccblnDuuYXRQ+n6pQdhe5oG8gLeDEhSVQJBLGqSEXl7BMhnAYssC2CyLSpPjOacsPdU ql8Op46EdUErzF4L/CrUI0usRxBySyn4YvLdSw1BHMWt4LDxnypfJteTULP/k73ORx/e gCTg== MIME-Version: 1.0 X-Received: by 10.180.187.237 with SMTP id fv13mr2037620wic.26.1392971194838; Fri, 21 Feb 2014 00:26:34 -0800 (PST) Received: by 10.180.90.132 with HTTP; Fri, 21 Feb 2014 00:26:34 -0800 (PST) In-Reply-To: References: <6399D67E-2C8F-4282-8285-6D6F27A02EF1@viagenie.ca> Date: Fri, 21 Feb 2014 00:26:34 -0800 Message-ID: From: "Murray S. Kucherawy" To: Andy Newton Content-Type: multipart/alternative; boundary=001a11c25a9c4034be04f2e661d7 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/DMtqS2GYYLToUJ_EauBufVb3pH8 Cc: "weirds@ietf.org" Subject: Re: [weirds] IETF 89 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: Fri, 21 Feb 2014 08:26:41 -0000 --001a11c25a9c4034be04f2e661d7 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Feb 19, 2014 at 9:09 AM, Andy Newton wrote: > > I agree that this should be our top priority. Reviewers on the > apps-discuss list mentioned that we could drop .well-known and that met > with no objections. So I think .well-known can be dropped from rdap-query. > Just back from a short vacation and I'm a bit behind, so I'll have to dig this up (though it's great to hear!). I recall Mark saying in Vancouver that .well-known was just one possible solution to the issue at hand, so it's no surprise that dropping it is acceptable so long as we still don't land on a solution that the web folk find objectionable, or we're back to where we started. But I think you've touched on that here: > > Now the templates discussion is another issue entirely. On the > apps-discuss list I noted that the architectural issue was that they wanted > us to avoid URI collisions and that templates were just one method for > doing so. Since our bootstrap method allows for arbitrary base URIs, RDAP > does not suffer from URI collisions. So far that assertion has not been > challenged on apps-discuss. However, it most likely needs to be explicitly > discussed at the meeting (and on THIS list). > > This is pretty much in line with my (at present, hazy) understanding of the issue and our approach to solving it for WEIRDS. I'll invite Mark to attend our session. Given that this is our only major topic, and it doesn't appear we're in conflict with httpbis or other web-specific WGs, the odds might be in our favor that we can settle the matter at long last. -MSK --001a11c25a9c4034be04f2e661d7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Wed, Feb 19, 2014 at 9:09 AM, Andy Newton <andy@arin.net> wrote:

I agree that this should be our top priority. = Reviewers on the apps-discuss list mentioned that we could drop .well-known= and that met with no objections. So I think .well-known can be dropped fro= m rdap-query.

Just back from a short vacation and = I'm a bit behind, so I'll have to dig this up (though it's grea= t to hear!).

I recall Mark saying in Vancouver that .well= -known was just one possible solution to the issue at hand, so it's no = surprise that dropping it is acceptable so long as we still don't land = on a solution that the web folk find objectionable, or we're back to wh= ere we started.=A0 But I think you've touched on that here:
=A0

Now the templates discussion is another issue entirely. On the apps-di= scuss list I noted that the architectural issue was that they wanted us to = avoid URI collisions and that templates were just one method for doing so. = Since our bootstrap method allows for arbitrary base URIs, RDAP does not suffer from URI collisions. So far = that assertion has not been challenged on apps-discuss. However, it most li= kely needs to be explicitly discussed at the meeting (and on THIS list).


This is= pretty much in line with my (at present, hazy) understanding of the issue = and our approach to solving it for WEIRDS.

I'll invit= e Mark to attend our session.=A0 Given that this is our only major topic, a= nd it doesn't appear we're in conflict with httpbis or other web-sp= ecific WGs, the odds might be in our favor that we can settle the matter at= long last.

-MSK
--001a11c25a9c4034be04f2e661d7-- From nobody Fri Feb 21 09:47: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 358DC1A01BF for ; Fri, 21 Feb 2014 09:47:08 -0800 (PST) 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 pB7N_L26BhMl for ; Fri, 21 Feb 2014 09:47:05 -0800 (PST) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 5242B1A019C for ; Fri, 21 Feb 2014 09:47:05 -0800 (PST) Received: by mail-wi0-f169.google.com with SMTP id e4so1121526wiv.0 for ; Fri, 21 Feb 2014 09:47:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=m94gOjsOoXoMQ/BcE8z8o685kR+2XgA0WWvxP1jZhIQ=; b=m+ueKx01WfbEJyxSPMCst+sRrgLEzcwtelzorpY94kiQiBif9+x21Ib1EoKPpWcyui KIqAz47oxmQ0PSBMd+W2VTgjfzOpW9fdo+v/AS5MzFhGWLNlhpRKrPXr/Y9gUfywK1rS G9NTPqJyCW1QOSipmkPtMXqHIhGZYiSAFGpIH51wtukneCh2Jd+d6S+cN7igkmD4lcZm Ue8NrcAMf9Ul3nubTHBEdRCnBKSGKQJPKiHemwr41tajmkkkYBWZ35vE0woglDh4kUpM BH7Jg7A5La+1dyzvEzwnMG0vW1AmnEYowpV1GsJRcBz5R25ZHXPW21MBX2483qy1g9ql q8Sw== MIME-Version: 1.0 X-Received: by 10.194.77.7 with SMTP id o7mr8245122wjw.35.1393004820729; Fri, 21 Feb 2014 09:47:00 -0800 (PST) Received: by 10.180.90.132 with HTTP; Fri, 21 Feb 2014 09:47:00 -0800 (PST) In-Reply-To: References: <6399D67E-2C8F-4282-8285-6D6F27A02EF1@viagenie.ca> Date: Fri, 21 Feb 2014 09:47:00 -0800 Message-ID: From: "Murray S. Kucherawy" To: Andy Newton Content-Type: multipart/alternative; boundary=047d7bfd05fc82993704f2ee358b Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/PVQqhlfyOPTmCLvw7S2JbDJigY8 Cc: "weirds@ietf.org" Subject: Re: [weirds] IETF 89 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: Fri, 21 Feb 2014 17:47:08 -0000 --047d7bfd05fc82993704f2ee358b Content-Type: text/plain; charset=ISO-8859-1 The draft agenda is now available here: http://www.ietf.org/proceedings/89/minutes/minutes-89-weirds It's pretty straightforward. If there are any other topics that need face time in London, please let us know ASAP as the final agenda is due on Monday. -MSK On Fri, Feb 21, 2014 at 12:26 AM, Murray S. Kucherawy wrote: > On Wed, Feb 19, 2014 at 9:09 AM, Andy Newton wrote: > >> >> I agree that this should be our top priority. Reviewers on the >> apps-discuss list mentioned that we could drop .well-known and that met >> with no objections. So I think .well-known can be dropped from rdap-query. >> > > Just back from a short vacation and I'm a bit behind, so I'll have to dig > this up (though it's great to hear!). > > I recall Mark saying in Vancouver that .well-known was just one possible > solution to the issue at hand, so it's no surprise that dropping it is > acceptable so long as we still don't land on a solution that the web folk > find objectionable, or we're back to where we started. But I think you've > touched on that here: > > >> >> Now the templates discussion is another issue entirely. On the >> apps-discuss list I noted that the architectural issue was that they wanted >> us to avoid URI collisions and that templates were just one method for >> doing so. Since our bootstrap method allows for arbitrary base URIs, RDAP >> does not suffer from URI collisions. So far that assertion has not been >> challenged on apps-discuss. However, it most likely needs to be explicitly >> discussed at the meeting (and on THIS list). >> >> > This is pretty much in line with my (at present, hazy) understanding of > the issue and our approach to solving it for WEIRDS. > > I'll invite Mark to attend our session. Given that this is our only major > topic, and it doesn't appear we're in conflict with httpbis or other > web-specific WGs, the odds might be in our favor that we can settle the > matter at long last. > > -MSK > --047d7bfd05fc82993704f2ee358b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
The draft agenda is now available here: http://www.ietf= .org/proceedings/89/minutes/minutes-89-weirds

It's pretty st= raightforward.=A0 If there are any other topics that need face time in Lond= on, please let us know ASAP as the final agenda is due on Monday.

-MSK


On Fri, Feb 21, 2014 at 12:26 AM, Murray S. Kucherawy <super= user@gmail.com> wrote:
On Wed, Feb= 19, 2014 at 9:09 AM, Andy Newton <andy@arin.net> wrote:

I agree that this should be our top priority. = Reviewers on the apps-discuss list mentioned that we could drop .well-known= and that met with no objections. So I think .well-known can be dropped fro= m rdap-query.

Just back from a short vacatio= n and I'm a bit behind, so I'll have to dig this up (though it'= s great to hear!).

I recall Mark saying in Vancouver that= .well-known was just one possible solution to the issue at hand, so it'= ;s no surprise that dropping it is acceptable so long as we still don't= land on a solution that the web folk find objectionable, or we're back= to where we started.=A0 But I think you've touched on that here:
=A0

Now the templates discussion is another issue entirely. On the apps-di= scuss list I noted that the architectural issue was that they wanted us to = avoid URI collisions and that templates were just one method for doing so. = Since our bootstrap method allows for arbitrary base URIs, RDAP does not suffer from URI collisions. So far = that assertion has not been challenged on apps-discuss. However, it most li= kely needs to be explicitly discussed at the meeting (and on THIS list).


T= his is pretty much in line with my (at present, hazy) understanding of the = issue and our approach to solving it for WEIRDS.

I'll= invite Mark to attend our session.=A0 Given that this is our only major to= pic, and it doesn't appear we're in conflict with httpbis or other = web-specific WGs, the odds might be in our favor that we can settle the mat= ter at long last.

-MSK

--047d7bfd05fc82993704f2ee358b-- From nobody Fri Feb 21 10:13: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 4C8A51A0564 for ; Fri, 21 Feb 2014 10:13:12 -0800 (PST) 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 baMbWQgoPt2Q for ; Fri, 21 Feb 2014 10:13:09 -0800 (PST) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 3DE071A055E for ; Fri, 21 Feb 2014 10:13:09 -0800 (PST) Received: by mail-wg0-f41.google.com with SMTP id l18so1035380wgh.0 for ; Fri, 21 Feb 2014 10:13:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GrlETHRUKq5LgufmiY4NydHh4Qi5S3WMSTt/1fIox3k=; b=EpgkPHvaNKUFhTrMkczZ0Ct2TNb5Lr+oq97QMLsDe5S8R6DR4Lx7O9dyb9iHgnZxtq iMS+ljLwDUMBLrh1GTlrf9EVDeiVGInsRhmg25NHVEz/cmv/F4XJRpHn6fdaR86+ipcP nTwHfSnUXARWFngzaUPDkB8DR6UBnOEXG167fzKeuF1MAtTUH+UPFbd1i3ioEJHNxT/s Phsnz4XQ0OSJQ+Mm9FKUk+uRDKoJlFjdGWvyGCuYplWNJmrcGg2Jg+DOnYEs3S8V4l9A aKLEeb/StCGxBi8kb8mPT/aBCLQSawySdrLzBMgUewJJL/1c8saxoFLeAto1p+icwxnF u4+Q== MIME-Version: 1.0 X-Received: by 10.180.187.237 with SMTP id fv13mr4389376wic.26.1393006384851; Fri, 21 Feb 2014 10:13:04 -0800 (PST) Received: by 10.180.90.132 with HTTP; Fri, 21 Feb 2014 10:13:04 -0800 (PST) In-Reply-To: References: <6399D67E-2C8F-4282-8285-6D6F27A02EF1@viagenie.ca> Date: Fri, 21 Feb 2014 10:13:04 -0800 Message-ID: From: "Murray S. Kucherawy" To: Andy Newton Content-Type: multipart/alternative; boundary=001a11c25a9cbd322a04f2ee92e1 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/3ShqJSJYt9UsYi3JN1UAQT3vjUk Cc: "weirds@ietf.org" Subject: Re: [weirds] IETF 89 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: Fri, 21 Feb 2014 18:13:12 -0000 --001a11c25a9cbd322a04f2ee92e1 Content-Type: text/plain; charset=ISO-8859-1 Yes, I uploaded the agenda as minutes. We're trying something Jeopardy-like this time where we post the minutes, and then you all have to execute the meeting that leads us back to the as-yet-unspecified agenda. I'm clearly too decaffeinated. The agenda is now here: http://www.ietf.org/proceedings/89/agenda/agenda-89-weirds. Sorry about that. -MSK On Fri, Feb 21, 2014 at 9:47 AM, Murray S. Kucherawy wrote: > The draft agenda is now available here: > http://www.ietf.org/proceedings/89/minutes/minutes-89-weirds > > It's pretty straightforward. If there are any other topics that need face > time in London, please let us know ASAP as the final agenda is due on > Monday. > > -MSK > > > On Fri, Feb 21, 2014 at 12:26 AM, Murray S. Kucherawy > wrote: > >> On Wed, Feb 19, 2014 at 9:09 AM, Andy Newton wrote: >> >>> >>> I agree that this should be our top priority. Reviewers on the >>> apps-discuss list mentioned that we could drop .well-known and that met >>> with no objections. So I think .well-known can be dropped from rdap-query. >>> >> >> Just back from a short vacation and I'm a bit behind, so I'll have to dig >> this up (though it's great to hear!). >> >> I recall Mark saying in Vancouver that .well-known was just one possible >> solution to the issue at hand, so it's no surprise that dropping it is >> acceptable so long as we still don't land on a solution that the web folk >> find objectionable, or we're back to where we started. But I think you've >> touched on that here: >> >> >>> >>> Now the templates discussion is another issue entirely. On the >>> apps-discuss list I noted that the architectural issue was that they wanted >>> us to avoid URI collisions and that templates were just one method for >>> doing so. Since our bootstrap method allows for arbitrary base URIs, RDAP >>> does not suffer from URI collisions. So far that assertion has not been >>> challenged on apps-discuss. However, it most likely needs to be explicitly >>> discussed at the meeting (and on THIS list). >>> >>> >> This is pretty much in line with my (at present, hazy) understanding of >> the issue and our approach to solving it for WEIRDS. >> >> I'll invite Mark to attend our session. Given that this is our only >> major topic, and it doesn't appear we're in conflict with httpbis or other >> web-specific WGs, the odds might be in our favor that we can settle the >> matter at long last. >> >> -MSK >> > > --001a11c25a9cbd322a04f2ee92e1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Yes, I uploaded the agenda as minutes.=A0 We're t= rying something Jeopardy-like this time where we post the minutes, and then= you all have to execute the meeting that leads us back to the as-yet-unspe= cified agenda.

I'm clearly too decaffeinated.=A0 The agenda is now here: http://= www.ietf.org/proceedings/89/agenda/agenda-89-weirds.=A0 Sorry about tha= t.

-MSK


On Fri, Feb 21, 2014 at 9:47 AM, Murray S. Kucherawy <superuser@gma= il.com> wrote:
The draft agenda is no= w available here: http://www.ietf.org/proceedings/89/minute= s/minutes-89-weirds

It's pretty straightforward.=A0 If there are any other topics that = need face time in London, please let us know ASAP as the final agenda is du= e on Monday.

-MSK=


On Fri, Feb 21, 2014 at= 12:26 AM, Murray S. Kucherawy <superuser@gmail.com> wrote= :
On Wed, Feb 19, 2014 a= t 9:09 AM, Andy Newton <andy@arin.net> wrote:

I agree that this should be our top priority. = Reviewers on the apps-discuss list mentioned that we could drop .well-known= and that met with no objections. So I think .well-known can be dropped fro= m rdap-query.

Just back from a short vacatio= n and I'm a bit behind, so I'll have to dig this up (though it'= s great to hear!).

I recall Mark saying in Vancouver that= .well-known was just one possible solution to the issue at hand, so it'= ;s no surprise that dropping it is acceptable so long as we still don't= land on a solution that the web folk find objectionable, or we're back= to where we started.=A0 But I think you've touched on that here:
=A0

Now the templates discussion is another issue entirely. On the apps-di= scuss list I noted that the architectural issue was that they wanted us to = avoid URI collisions and that templates were just one method for doing so. = Since our bootstrap method allows for arbitrary base URIs, RDAP does not suffer from URI collisions. So far = that assertion has not been challenged on apps-discuss. However, it most li= kely needs to be explicitly discussed at the meeting (and on THIS list).


T= his is pretty much in line with my (at present, hazy) understanding of the = issue and our approach to solving it for WEIRDS.

I'll= invite Mark to attend our session.=A0 Given that this is our only major to= pic, and it doesn't appear we're in conflict with httpbis or other = web-specific WGs, the odds might be in our favor that we can settle the mat= ter at long last.

-MSK


--001a11c25a9cbd322a04f2ee92e1--