From nobody Sun Apr 13 23:48: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 D61D11A0101 for ; Sun, 13 Apr 2014 23:48:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 JQ8deQJH8ZBo for ; Sun, 13 Apr 2014 23:48:26 -0700 (PDT) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id 827C11A00EA for ; Sun, 13 Apr 2014 23:48:26 -0700 (PDT) Received: by mail-wi0-f181.google.com with SMTP id hm4so3513478wib.14 for ; Sun, 13 Apr 2014 23:48:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=g/Eifwfsdnq1VjvyQDPowVauZHBjN/VXc9Mc9d2q6MQ=; b=T/K4kJ/UmDjQ6bLQa6xv3YzUVW4ecYnBrLK1+M/U3YBqq9rciU6UILDLWp/o8ygb8O 88h4Gh+L2rkftjqspRuhajJyg29jg8hBI/lLtowdVCLKk4yhmyEr2yCVBnctZIQCfMpS 7aSaOHG7NQgtQZfqj1vdr8bEEcJ2HjGmnUDu7aP/ei7SuAW1iknT/LAEWOoa2gl5ODWc /M3qSR25DuPVCwMDsTYc5KejiYdW22UrQweXrlg7vQHy/jCLbK0bFgX1T8hgK2lKOh2R BDT/ZB1WP5xOCB1gcp9O7amJNm69YdiIE+Mv/MrqeqHnvP6l6nxMPTIn0em3BWuh3nh9 omfA== MIME-Version: 1.0 X-Received: by 10.180.10.66 with SMTP id g2mr8215158wib.5.1397458103662; Sun, 13 Apr 2014 23:48:23 -0700 (PDT) Received: by 10.180.90.140 with HTTP; Sun, 13 Apr 2014 23:48:23 -0700 (PDT) Date: Sun, 13 Apr 2014 23:48:23 -0700 Message-ID: From: "Murray S. Kucherawy" To: "weirds@ietf.org" Content-Type: multipart/alternative; boundary=001a11c25d58db7d9904f6fb1172 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/FWxwjeWfcq5OFW-4ZiD1z5_mSgs Subject: [weirds] Remaining issues from London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Apr 2014 06:48:28 -0000 --001a11c25d58db7d9904f6fb1172 Content-Type: text/plain; charset=ISO-8859-1 Colleagues, A number of issues were raised during the London meeting, especially with the bootstrapping and query topics. We need to discuss and resolve these so the documents can move forward. There hasn't been much activity since London, which is at odds with the chairs' hope that we would be done by the time of the Toronto meeting. I'm going to open tracker items and email threads on this list for each of the items identified during the London meeting. For each of them, we need to come to a rough (or better) consensus resolution before we can proceed, so I encourage everyone to participate in as many of them as is practicable. We can create design teams as needed, assuming we can get people to volunteer for the ones we decide we need. If you don't see a tracker item and email thread start for an issue you'd like to see resolved, please contact the co-chairs or post to the list to get it on the record for discussion. Let's get going! -MSK --001a11c25d58db7d9904f6fb1172 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Colleagues,

A number of issues= were raised during the London meeting, especially with the bootstrapping a= nd query topics.=A0 We need to discuss and resolve these so the documents c= an move forward.=A0 There hasn't been much activity since London, which= is at odds with the chairs' hope that we would be done by the time of = the Toronto meeting.

I'm going to open tracker items and email threads on this list for = each of the items identified during the London meeting.=A0 For each of them= , we need to come to a rough (or better) consensus resolution before we can= proceed, so I encourage everyone to participate in as many of them as is p= racticable.=A0 We can create design teams as needed, assuming we can get pe= ople to volunteer for the ones we decide we need.

If you don't see a tracker item and email thread start f= or an issue you'd like to see resolved, please contact the co-chairs or= post to the list to get it on the record for discussion.

Let's get going!

-MSK
--001a11c25d58db7d9904f6fb1172-- From nobody Sun Apr 13 23:58:45 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D5EC1A0387 for ; Sun, 13 Apr 2014 23:58:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 7FboUDWsHN1K for ; Sun, 13 Apr 2014 23:58:42 -0700 (PDT) Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id D78061A0394 for ; Sun, 13 Apr 2014 23:58:41 -0700 (PDT) Received: by mail-wg0-f43.google.com with SMTP id x13so7620043wgg.26 for ; Sun, 13 Apr 2014 23:58:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=nTefzl54YYl9cPC4VZBx4J6k5WV9ff0OVDNRRm1UaBY=; b=ul1HTKSXdkuSBDMg+AaqXnSavBx8OxX4hUTJHAjnl2zq+Q0BSBzJElio16JlZShj6z 1MH4nvyMjqw0GOv+MvIoTA/IZlsGKP9l8ITFkgTY21Z0vQIIFWY+axlbTe/KViO3kaK4 hAcAyVeOe8W+J7LSBO4LtnOvYM6hfBgStzzfCj0p54aYM+Bgbr4v7roJzRHV9y3WbvTm 8yo+AJ1KWqBZ/eUhiCITZk03YPSaQcLmbv5q3hd88757RRl8WwCpLa05XgXv2+jpJadL OUfw8tjjQpmkvuTr0M1ZzFN71ndonCIdXtG9hL6ulDY4zUsSTssIeVW6gsyA144gpb98 f5Wg== MIME-Version: 1.0 X-Received: by 10.180.10.66 with SMTP id g2mr8248882wib.5.1397458719116; Sun, 13 Apr 2014 23:58:39 -0700 (PDT) Received: by 10.180.90.140 with HTTP; Sun, 13 Apr 2014 23:58:38 -0700 (PDT) In-Reply-To: <070.1e858905b72708ef0e9b07e3a3446cf7@tools.ietf.org> References: <055.978debfe1f4cb817a25526fad04ef5c4@tools.ietf.org> <070.1e858905b72708ef0e9b07e3a3446cf7@tools.ietf.org> Date: Sun, 13 Apr 2014 23:58:38 -0700 Message-ID: From: "Murray S. Kucherawy" To: "weirds@ietf.org" Content-Type: multipart/alternative; boundary=001a11c25d588a917504f6fb3628 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/o4hCyezXpNAYsojRCB53E_MWtMo Subject: Re: [weirds] #12 (bootstrap): Bootstrap templates 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, 14 Apr 2014 06:58:44 -0000 --001a11c25d588a917504f6fb3628 Content-Type: text/plain; charset=ISO-8859-1 This ticket is (I believe) for settling the format of the deserialized IANA registry content. The last thing I had on the whiteboard in London looked like this: { "weirds": { "DEFAULT": { "ip": "template-for-IP-query", "entity": "template-for-entity", "domain": "template-for-domain", }, "ca": { "ip": null, "entity": "specific-template-for-ca-entity", "domain": "template-for-ca-domain", }, }, } So for a lookup matching ".ca" (anything in that zone, since there's nothing more specific), a domain lookup would use the template "template-for-ca-domain", and a lookup for an entity would use the template "template-for-ca-entity"; a lookup for an IP address doesn't make sense inside ".ca", so it's null here. If any of those were undefined, it would fall back to the corresponding entry in the DEFAULT record. We would need to identify some number of substitution tokens to be used in each type of query. The obvious ones are "{domain}" for domain queries and "{entity}" for entity queries. The RIR folks will need to make some suggestions about what lookup keys would look like for their RDAP servers so they can be included. Are there other query types we need to support? Does this format look reasonable, or could it be optimized some other way? I think there were some suggestions at the mic in London. -MSK --001a11c25d588a917504f6fb3628 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
This ticket is (I believe) for settlin= g the format of the deserialized IANA registry content.

The last thi= ng I had on the whiteboard in London looked like this:

{
=A0=A0= =A0 "weirds": {
=A0=A0=A0 =A0=A0=A0 "DEFAULT": {
=A0=A0=A0 =A0=A0=A0 =A0=A0=A0= "ip": "template-for-IP-query",
=A0=A0=A0 =A0=A0=A0 = =A0=A0=A0 "entity": "template-for-entity",
=A0=A0=A0= =A0=A0=A0 =A0=A0=A0 "domain": "template-for-domain", =A0=A0=A0 =A0=A0=A0 },
=A0=A0=A0 =A0=A0=A0 "ca": {
=A0=A0= =A0 =A0=A0=A0 =A0=A0=A0 "ip": null,
=A0=A0=A0 =A0=A0=A0 =A0=A0= =A0 "entity": "specific-template-for-ca-entity",
=A0= =A0=A0 =A0=A0=A0 =A0=A0=A0 "domain": "template-for-ca-domain= ",
=A0=A0=A0 =A0=A0=A0 },
=A0=A0=A0 },
}

So for a lookup ma= tching ".ca" (anything in that zone, since there's nothing mo= re specific), a domain lookup would use the template "template-for-ca-= domain", and a lookup for an entity would use the template "templ= ate-for-ca-entity"; a lookup for an IP address doesn't make sense = inside ".ca", so it's null here.=A0 If any of those were unde= fined, it would fall back to the corresponding entry in the DEFAULT record.=

We would need to identify some number of substitution tokens to b= e used in each type of query.=A0 The obvious ones are "{domain}" = for domain queries and "{entity}" for entity queries.=A0 The RIR = folks will need to make some suggestions about what lookup keys would look = like for their RDAP servers so they can be included.

Are there other query types we need to support?

Does this = format look reasonable, or could it be optimized some other way?=A0 I think= there were some suggestions at the mic in London.

-MSK
--001a11c25d588a917504f6fb3628-- From nobody Mon Apr 14 00:37: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 1AD201A0220 for ; Mon, 14 Apr 2014 00:37:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6hrNDtApJrhT for ; Mon, 14 Apr 2014 00:37:06 -0700 (PDT) Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 244B91A038E for ; Mon, 14 Apr 2014 00:37:05 -0700 (PDT) Received: by mail-we0-f174.google.com with SMTP id t60so7834112wes.33 for ; Mon, 14 Apr 2014 00:37:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=VcmHnhQvS0wZJhCUJcMfenCRf9MbWde7ODlfebuEzZ8=; b=0cQ3kwNoYx4j6f9+gVUUDuRXbhi21gBh+T8dk0YDbMBEpqrGRE9Zkom4TDRiMHlLqr B6WvnDEUsZrmCnbNrH3ntE9Y1+LTAc+abg4ynAgUpAPktkc0ziV8gZQqFSED8V7h0bBx 1h637QLqduNdAzoQPZJRWybbU4OtgoMCopCYd/KQmlPCwE0UR6txtDGptRvDV/7pycpQ rLAiV9kWEXnorNwD+FCfadrvegBGEDn71i6yBnWwuxUbKrprGKHgzq1AEpQ2HDL65chd S0KTyBeo3bnJaXazv4PCPNS0hLl0AEewBOPdhO75n2fIQPmk/d4hBAzb/cxTAlPTDWuH Hp+w== MIME-Version: 1.0 X-Received: by 10.194.205.161 with SMTP id lh1mr15670435wjc.40.1397461023185; Mon, 14 Apr 2014 00:37:03 -0700 (PDT) Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 00:37:03 -0700 (PDT) In-Reply-To: References: Date: Mon, 14 Apr 2014 00:37:03 -0700 Message-ID: From: "Murray S. Kucherawy" To: "weirds@ietf.org" Content-Type: multipart/alternative; boundary=047d7b6d9502dfe35904f6fbbf46 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/1tr340RQLNWpVEp5mMFHOlNOR0c Subject: Re: [weirds] Remaining issues from London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Apr 2014 07:37:08 -0000 --047d7b6d9502dfe35904f6fbbf46 Content-Type: text/plain; charset=ISO-8859-1 On Sun, Apr 13, 2014 at 11:48 PM, Murray S. Kucherawy wrote: > I'm going to open tracker items and email threads on this list for each of > the items identified during the London meeting. For each of them, we need > to come to a rough (or better) consensus resolution before we can proceed, > so I encourage everyone to participate in as many of them as is > practicable. We can create design teams as needed, assuming we can get > people to volunteer for the ones we decide we need. > > If you don't see a tracker item and email thread start for an issue you'd > like to see resolved, please contact the co-chairs or post to the list to > get it on the record for discussion. > As you can see, these are now open. I just noticed that several others were opened during the London meeting by other participants. If there are any duplicates, please mark them as such so the work doesn't get confused. If any have been mis-assigned, please let us know and we can get them adjusted. The full set of open items is here: http://trac.tools.ietf.org/wg/weirds/trac/report/1 Let's get some discussions going! -MSK --047d7b6d9502dfe35904f6fbbf46 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Sun, Apr 13, 2014 at 11:48 PM, Murray S. Kucherawy <= superuser@gmail.com> wrote:
I'm going to open tracker items and email threads on this list for ea= ch of the items identified during the London meeting.=A0 For each of them, = we need to come to a rough (or better) consensus resolution before we can p= roceed, so I encourage everyone to participate in as many of them as is pra= cticable.=A0 We can create design teams as needed, assuming we can get peop= le to volunteer for the ones we decide we need.

If you don't see a tracker item and email thread start f= or an issue you'd like to see resolved, please contact the co-chairs or= post to the list to get it on the record for discussion.

As you can see, these are now open.= =A0 I just noticed that several others were opened during the London meetin= g by other participants.=A0 If there are any duplicates, please mark them a= s such so the work doesn't get confused.=A0 If any have been mis-assign= ed, please let us know and we can get them adjusted.

The full set of open items is here:

http://trac.tools.ietf.org/wg/weirds/tra= c/report/1

Let's get some discussions going!

-MSK
--047d7b6d9502dfe35904f6fbbf46-- From nobody Mon Apr 14 00:40:43 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC0F41A0395 for ; Mon, 14 Apr 2014 00:40:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FpD-6FlO5XaE for ; Mon, 14 Apr 2014 00:40:31 -0700 (PDT) Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5E1B61A039B for ; Mon, 14 Apr 2014 00:40:12 -0700 (PDT) Received: by mail-wg0-f46.google.com with SMTP id b13so7661478wgh.17 for ; Mon, 14 Apr 2014 00:40:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=skjm8GO1DJTxligPnKAUPn5AIbLg+SR82qM/KbxgyD4=; b=xen4lqXnn0q5cBKrH8C+huTzxCzXsd+MuXH1HerbXOTEi138e9Z/Wagdg8No+GTB9G bknmtU8pJp7NE+RauMVk9VnT2d/InGvYLVBZOqc668Vf+TNKL+fGpqaUpZsp4LmFORmr M2JnNhckyx++H7OdSwD12IOLIhVE2cNMIc46wbh368RlJGWggrGfwLeUvk+fiVOacNuf Jlm/kMSD9mnqC8Kcojx6Gmw01dbPTzSa9Z8l2qkk1qT1bUfNgaN2ym6TEVfGaQ8SDzDY Q5PgNKIRko4GmNSJgLNjqtmlgy00sH8N5ECd5T75HMma474S2UsF+y5qNuutC4g5rOkp /DtA== MIME-Version: 1.0 X-Received: by 10.195.12.33 with SMTP id en1mr31318439wjd.31.1397461209440; Mon, 14 Apr 2014 00:40:09 -0700 (PDT) Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 00:40:09 -0700 (PDT) In-Reply-To: References: <20140319004950.10409.qmail@joyce.lan> Date: Mon, 14 Apr 2014 00:40:09 -0700 Message-ID: From: "Murray S. Kucherawy" To: "Hollenbeck, Scott" Content-Type: multipart/alternative; boundary=047d7bfcf28cf9e74c04f6fbcaae Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/h-w2uXWra4Ph99l6aXzwEnSv_jQ Cc: John Levine , "weirds@ietf.org" Subject: Re: [weirds] Inter-Op discrepancy with specs: Search patterns 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, 14 Apr 2014 07:40:40 -0000 --047d7bfcf28cf9e74c04f6fbcaae Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Mar 19, 2014 at 12:37 AM, Hollenbeck, Scott < shollenbeck@verisign.com> wrote: > (Sorry for top posting) > > What Andy said below is correct. > > Scott > > > On Mar 19, 2014, at 10:03 AM, "Andy Newton" wrote: > > > > On 3/18/14, 8:49 PM, "John Levine" wrote: > > > >>> The spec gives an explicit example for xxx*: > >>> the search pattern "exam*" will match "example.com" and > >>> "example.net". > >> > >> If that's what the spec says, the spec needs to be fixed. > >> > >> The intention is to match what current WHOIS servers do, which is a > >> prefix match on whatever data the server handles. Nobody expects it > >> to go searching other servers. > > > > I don=B9t think searching other servers was ever the intent. The purpos= e of > > this is to allow one query to search both .com and .net (or whatever) i= f > > that server handles both .com and .net (or whatever). > Is there a text change that needs to be made here to clarify this? Or do we agree it's fine as-is? -MSK --047d7bfcf28cf9e74c04f6fbcaae Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Wed, Mar 19, 2014 at 12:37 AM, Hollenbeck, Scott <shollenbeck@verisign.com> wrote:
(Sorry for top posting)

What Andy said below is correct.

Scott

> On Mar 19, 2014, at 10:03 AM, "Andy Newton" <andy@arin.net> wrote:
>
> On 3/18/14, 8:49 PM, "John Levine" <johnl@taugh.com> wrote:
>
>>> The spec gives an explicit example for xxx*:
>>> =A0 =A0 the search pattern "exam*" will match "= example.com" and<= br> >>> "example= .net".
>>
>> If that's what the spec says, the spec needs to be fixed.
>>
>> The intention is to match what current WHOIS servers do, which is = a
>> prefix match on whatever data the server handles. =A0Nobody expect= s it
>> to go searching other servers.
>
> I don=B9t think searching other servers was ever the intent. The purpo= se of
> this is to allow one query to search both .com and .net (or whatever) = if
> that server handles both .com and .net (or whatever).
<= /blockquote>

Is there a text change that needs to be mad= e here to clarify this?=A0 Or do we agree it's fine as-is?

-MSK
--047d7bfcf28cf9e74c04f6fbcaae-- From nobody Mon Apr 14 03:52:33 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 872311A0185 for ; Mon, 14 Apr 2014 03:52:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HfUxnnBgI3DI for ; Mon, 14 Apr 2014 03:52:27 -0700 (PDT) Received: from exprod6og110.obsmtp.com (exprod6og110.obsmtp.com [64.18.1.25]) by ietfa.amsl.com (Postfix) with ESMTP id 46BFF1A02B2 for ; Mon, 14 Apr 2014 03:52:09 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob110.postini.com ([64.18.5.12]) with SMTP ID DSNKU0u91jFdVEfEEVFWKvT/xZuiE5zYzF9e@postini.com; Mon, 14 Apr 2014 03:52:25 PDT Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s3EAq5WE004466 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 14 Apr 2014 06:52:05 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 14 Apr 2014 06:52:05 -0400 From: "Hollenbeck, Scott" To: "Murray S. Kucherawy" Thread-Topic: [weirds] Inter-Op discrepancy with specs: Search patterns Thread-Index: AQHPV7TEUXM08Dfc5UibxJPYEQrHtZsQ73Hw Date: Mon, 14 Apr 2014 10:52:04 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F493A019D@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <20140319004950.10409.qmail@joyce.lan> 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_831693C2CDA2E849A7D7A712B24E257F493A019DBRN1WNEXMBX01vc_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/Bz18zgQnHZClQZYFOPK6N9xGPWc Cc: John Levine , "weirds@ietf.org" Subject: Re: [weirds] Inter-Op discrepancy with specs: Search patterns 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, 14 Apr 2014 10:52:31 -0000 --_000_831693C2CDA2E849A7D7A712B24E257F493A019DBRN1WNEXMBX01vc_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable From: Murray S. Kucherawy [mailto:superuser@gmail.com] Sent: Monday, April 14, 2014 3:40 AM To: Hollenbeck, Scott Cc: Andy Newton; John Levine; weirds@ietf.org Subject: Re: [weirds] Inter-Op discrepancy with specs: Search patterns On Wed, Mar 19, 2014 at 12:37 AM, Hollenbeck, Scott > wrote: (Sorry for top posting) What Andy said below is correct. Scott > On Mar 19, 2014, at 10:03 AM, "Andy Newton" > wrote: > > On 3/18/14, 8:49 PM, "John Levine" > wrote: > >>> The spec gives an explicit example for xxx*: >>> the search pattern "exam*" will match "example.com" and >>> "example.net". >> >> If that's what the spec says, the spec needs to be fixed. >> >> The intention is to match what current WHOIS servers do, which is a >> prefix match on whatever data the server handles. Nobody expects it >> to go searching other servers. > > I don=B9t think searching other servers was ever the intent. The purpose = of > this is to allow one query to search both .com and .net (or whatever) if > that server handles both .com and .net (or whatever). Is there a text change that needs to be made here to clarify this? Or do w= e agree it's fine as-is? [SAH] I should probably change the text. I'll do that when I get in there t= o make the changes needed after the bootstrap document is updated to descri= be query patterns. Scott --_000_831693C2CDA2E849A7D7A712B24E257F493A019DBRN1WNEXMBX01vc_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

From: Murray S= . Kucherawy [mailto:superuser@gmail.com]
Sent: Monday, April 14, 2014 3:40 AM
To: Hollenbeck, Scott
Cc: Andy Newton; John Levine; weirds@ietf.org
Subject: Re: [weirds] Inter-Op discrepancy with specs: Search patter= ns

 

On Wed, Mar 19, 2014 at 12:37 AM, Hollenbeck, Scott = <shollenbe= ck@verisign.com> wrote:

(Sorry for top posting)

What Andy said below is correct.

Scott


> On Mar 19, 2014, at 10:03 AM, "Andy Newton" <andy@arin.net> wrote:
>
> On 3/18/14, 8:49 PM, "John Levine" <johnl@taugh.com> wrote:
>
>>> The spec gives an explicit example for xxx*:
>>>     the search pattern "exam*" will match = "example.com"= ; and
>>> "example= .net".
>>
>> If that's what the spec says, the spec needs to be fixed.
>>
>> The intention is to match what current WHOIS servers do, which is = a
>> prefix match on whatever data the server handles.  Nobody exp= ects it
>> to go searching other servers.
>
> I don=B9t think searching other servers was ever the intent. The purpo= se of
> this is to allow one query to search both .com and .net (or whatever) = if
> that server handles both .com and .net (or whatever).

 

Is there a text chang= e that needs to be made here to clarify this?  Or do we agree it's fin= e as-is?

[SAH] I should probabl= y change the text. I’ll do that when I get in there to make the chang= es needed after the bootstrap document is updated to describe query pattern= s.

 

Scott

--_000_831693C2CDA2E849A7D7A712B24E257F493A019DBRN1WNEXMBX01vc_-- From nobody Mon Apr 14 03:57: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 5E5FF1A02AE for ; Mon, 14 Apr 2014 03:57:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wi4iF0V5kWPS for ; Mon, 14 Apr 2014 03:57:12 -0700 (PDT) Received: from exprod6og117.obsmtp.com (exprod6og117.obsmtp.com [64.18.1.39]) by ietfa.amsl.com (Postfix) with ESMTP id F0EA41A0185 for ; Mon, 14 Apr 2014 03:57:11 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob117.postini.com ([64.18.5.12]) with SMTP ID DSNKU0u/BcnZ0T2iHOve2EeBP8NCtmlcfxai@postini.com; Mon, 14 Apr 2014 03:57:10 PDT Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s3EAv9sd004586 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 14 Apr 2014 06:57:09 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 14 Apr 2014 06:57:08 -0400 From: "Hollenbeck, Scott" To: "weirds@ietf.org" Thread-Topic: [weirds] #25 (rdap-query): Clarify what is done with unsupported queries Thread-Index: AQHPV7H5bGteZtfWgEGG0kPDsiHCipsQ8M3g Date: Mon, 14 Apr 2014 10:57:08 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F493A020C@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <060.b2ab04d2716ada34d0a26f7de381d988@tools.ietf.org> In-Reply-To: <060.b2ab04d2716ada34d0a26f7de381d988@tools.ietf.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.173.152.4] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/z5kTdNiqk5RQ1uzTnOlAq8dq-u0 Subject: Re: [weirds] #25 (rdap-query): Clarify what is done with unsupported queries 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, 14 Apr 2014 10:57:16 -0000 PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiB3ZWlyZHMgaXNzdWUgdHJhY2tl ciBbbWFpbHRvOnRyYWMrd2VpcmRzQHRvb2xzLmlldGYub3JnXQ0KPiBTZW50OiBNb25kYXksIEFw cmlsIDE0LCAyMDE0IDM6MjAgQU0NCj4gVG86IGRyYWZ0LWlldGYtd2VpcmRzLXJkYXAtcXVlcnlA dG9vbHMuaWV0Zi5vcmc7IHN1cGVydXNlckBnbWFpbC5jb20NCj4gQ2M6IHdlaXJkc0BpZXRmLm9y Zw0KPiBTdWJqZWN0OiBbd2VpcmRzXSAjMjUgKHJkYXAtcXVlcnkpOiBDbGFyaWZ5IHdoYXQgaXMg ZG9uZSB3aXRoDQo+IHVuc3VwcG9ydGVkIHF1ZXJpZXMNCj4gDQo+ICMyNTogQ2xhcmlmeSB3aGF0 IGlzIGRvbmUgd2l0aCB1bnN1cHBvcnRlZCBxdWVyaWVzDQo+IA0KPiAgSXNzdWUgcmFpc2VkIGlu IExvbmRvbjoNCj4gDQo+ICBUaGUgcXVlcnkgZG9jdW1lbnQgc2hvdWxkIGV4cGxhaW4gd2hhdCBh IHNlcnZlciBkb2VzIHdoZW4gaXQgcmVjZWl2ZXMNCj4gYQ0KPiAgcXVlcnkgaXQgZG9lc24ndCB1 bmRlcnN0YW5kICh1bnN1cHBvcnRlZCBxdWVyeSB0eXBlPykuDQoNCldvdWxkIGl0IGJlIHN1ZmZp Y2llbnQgdG8gcHJvdmlkZSBhIHJlZmVyZW5jZSB0byB0aGlzIHRleHQgZnJvbSB0aGUgdXNpbmct aHR0cCBkb2N1bWVudD8NCg0KIjUuNC4gIE1hbGZvcm1lZCBRdWVyaWVzDQoNCiAgIElmIGEgc2Vy dmVyIHJlY2VpdmVzIGEgcXVlcnkgd2hpY2ggaXQgY2Fubm90IGludGVycHJldCBhcyBhbiBSREFQ DQogICBxdWVyeSwgaXQgcmV0dXJucyBhIDQwMCByZXNwb25zZSBjb2RlLiAgT3B0aW9uYWxseSwg aXQgTUFZIGluY2x1ZGUNCiAgIGFkZGl0aW9uYWwgaW5mb3JtYXRpb24gcmVnYXJkaW5nIHRoaXMg bmVnYXRpdmUgYW5zd2VyIGluIHRoZSBIVFRQDQogICBlbnRpdHkgYm9keS4iDQoNClNjb3R0DQo= From nobody Mon Apr 14 04:03:12 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB06F1A02AF for ; Mon, 14 Apr 2014 04:03:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 93DLWsr3bLF1 for ; Mon, 14 Apr 2014 04:03:08 -0700 (PDT) Received: from exprod6og103.obsmtp.com (exprod6og103.obsmtp.com [64.18.1.185]) by ietfa.amsl.com (Postfix) with ESMTP id CB6211A03C2 for ; Mon, 14 Apr 2014 04:03:06 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob103.postini.com ([64.18.5.12]) with SMTP ID DSNKU0vAaBrDfGGtb+cAXboS2x7iE9RMBPWP@postini.com; Mon, 14 Apr 2014 04:03:05 PDT Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02.vcorp.ad.vrsn.com [10.173.152.206]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id s3EB33T7004773 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 14 Apr 2014 07:03:04 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 14 Apr 2014 07:03:03 -0400 From: "Hollenbeck, Scott" To: "Murray S. Kucherawy" , "weirds@ietf.org" Thread-Topic: [weirds] #12 (bootstrap): Bootstrap templates Thread-Index: AQHPV6771OxEGmdbWEi/vncpcMnHhJsQ8f2Q Date: Mon, 14 Apr 2014 11:03:03 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F493A0222@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <055.978debfe1f4cb817a25526fad04ef5c4@tools.ietf.org> <070.1e858905b72708ef0e9b07e3a3446cf7@tools.ietf.org> 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_831693C2CDA2E849A7D7A712B24E257F493A0222BRN1WNEXMBX01vc_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/oc0Ri6Z8uB-iiB48xpquQKEzeHw Subject: Re: [weirds] #12 (bootstrap): Bootstrap templates 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, 14 Apr 2014 11:03:11 -0000 --_000_831693C2CDA2E849A7D7A712B24E257F493A0222BRN1WNEXMBX01vc_ 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: Monday, April 14, 2014 2:59 AM To: weirds@ietf.org Subject: Re: [weirds] #12 (bootstrap): Bootstrap templates This ticket is (I believe) for settling the format of the deserialized IANA= registry content. The last thing I had on the whiteboard in London looked like this: { "weirds": { "DEFAULT": { "ip": "template-for-IP-query", "entity": "template-for-entity", "domain": "template-for-domain", }, "ca": { "ip": null, "entity": "specific-template-for-ca-entity", "domain": "template-for-ca-domain", }, }, } So for a lookup matching ".ca" (anything in that zone, since there's nothin= g more specific), a domain lookup would use the template "template-for-ca-d= omain", and a lookup for an entity would use the template "template-for-ca-= entity"; a lookup for an IP address doesn't make sense inside ".ca", so it'= s null here. If any of those were undefined, it would fall back to the cor= responding entry in the DEFAULT record. We would need to identify some number of substitution tokens to be used in = each type of query. The obvious ones are "{domain}" for domain queries and= "{entity}" for entity queries. The RIR folks will need to make some sugge= stions about what lookup keys would look like for their RDAP servers so the= y can be included. Are there other query types we need to support? [SAH] I'd much rather use "rdap" instead of the weirds working group name i= n the template. The query types are listed in rdap-query: ip, autnum, domain, nameserver, e= ntity, and help. Scott --_000_831693C2CDA2E849A7D7A712B24E257F493A0222BRN1WNEXMBX01vc_ 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: Monday, April 14, 2014 2:59 AM
To: weirds@ietf.org
Subject: Re: [weirds] #12 (bootstrap): Bootstrap templates

 

This ticket is (I bel= ieve) for settling the format of the deserialized IANA registry content.
The last thing I had on the whiteboard in London looked like this:

{
    "weirds": {
        "DEFAULT": {
            "ip": &q= uot;template-for-IP-query",
            "entity"= : "template-for-entity",
            "domain"= : "template-for-domain",
        },
        "ca": {
            "ip": nu= ll,
            "entity"= : "specific-template-for-ca-entity",
            "domain"= : "template-for-ca-domain",
        },
    },
}

So for a lookup match= ing ".ca" (anything in that zone, since there's nothing more spec= ific), a domain lookup would use the template "template-for-ca-domain&= quot;, and a lookup for an entity would use the template "template-for-ca-entity"; a lookup for an IP address doesn't mak= e sense inside ".ca", so it's null here.  If any of those we= re undefined, it would fall back to the corresponding entry in the DEFAULT = record.

We would need to iden= tify some number of substitution tokens to be used in each type of query.&n= bsp; The obvious ones are "{domain}" for domain queries and "= ;{entity}" for entity queries.  The RIR folks will need to make some suggestions about what lookup keys would look like for their = RDAP servers so they can be included.

Are there other query types we need to support?

[SAH] IR= 17;d much rather use “rdap” instead of the weirds working group= name in the template.

The query t= ypes are listed in rdap-query: ip, autnum, domain, nameserver, entity, and = help.

Scott<= /o:p>

--_000_831693C2CDA2E849A7D7A712B24E257F493A0222BRN1WNEXMBX01vc_-- From nobody Mon Apr 14 08:30: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 204051A01D9 for ; Mon, 14 Apr 2014 08:30:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.542 X-Spam-Level: * X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IcTx6087bjs4 for ; Mon, 14 Apr 2014 08:30:28 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id DF8061A02CF for ; Mon, 14 Apr 2014 08:30:27 -0700 (PDT) Received: (qmail 84276 invoked from network); 14 Apr 2014 15:30:24 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 14 Apr 2014 15:30: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:mime-version:content-type:content-transfer-encoding; s=7886.534bff10.k1404; i=johnl@user.iecc.com; bh=SqYOBXq/7K8X3+WFl+qavPgUzDTcOctj/HmSV1EHU3Q=; b=JlIa8nTOMpKEGXOqpogHZiqwNSiboar0pqFwnEGxW87uODM7UU7FJ0WzKMsUKIVGscrWRIA5JDiItZRFnkWbmz7eHnTwhze595JriQGPTV9B6rNUdeMlAk5qr74d1RXXsXOPBNWhYgwM6HxnlR//7Si+GDXcTj+YG5VpnQ8HrV6Jv87GmXksd00EuY/lqwvPe1A3GMh/gVY2OYK+wxv8m8EJcHRh83UypYQyZso5pRqrce56kCTa7nBsC+hHsUrX 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=7886.534bff10.k1404; olt=johnl@user.iecc.com; bh=SqYOBXq/7K8X3+WFl+qavPgUzDTcOctj/HmSV1EHU3Q=; b=PeutzYNCehFA7benP/H+eQSgeTmQkYxEZrdX4eikRZeG7OeRcLTNbGCKBF9XQp81l5AEgnTTDdzIIWvFQp65HwCHFBueCy7B7yF8LqyYFJIkb8kLsfebUhWDj45E88o4w5ZMTXYJnlXjmy7tUQMA2guFUvuh/8ICXy+FkHhbC+StrL2RAsgLNviBDxVMCWFbchs45TQRZ0F1PRc+nxi7n8E2YpunrtBO8ccb9ReRv49jYKhzXikBpyck/MUNKX2O Date: 14 Apr 2014 15:30:02 -0000 Message-ID: <20140414153002.30853.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/NbRhO-eJDJ0us9Z2Tw7kWJVCFdo Subject: Re: [weirds] #12 (bootstrap): Bootstrap templates 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, 14 Apr 2014 15:30:33 -0000 >We would need to identify some number of substitution tokens to be used in >each type of query. The obvious ones are "{domain}" for domain queries and >"{entity}" for entity queries. The RIR folks will need to make some >suggestions about what lookup keys would look like for their RDAP servers >so they can be included. The keys are all in draft-ietf-weirds-rdap-query-10. Lookup: ip autnum domain nameserver entity help Search: domains nameservers entities I'd suggest doing it this way: { "DEFAULT": { "prefix": "http://rdap.nic.{domain}", "lookup": "/{type}/{value}", "search": "/{type}?{subtype}={value}" }, "ca": { "prefix": "http://rdap.cira.ca" # uses the default paths }, "hockey": { # no prefix, included in the patterns "lookup": "http://rdap.donuts.co/hockey?{type}={value}", "search": "http://rdap.donuts.co/hockey/search/{type}?{subtype}={value}" }, } There's a separate list of lookup and search types and subtypes: Lookup types and values: ------------------------ ip IP or CIDR autnum ASN domain Domain name nameserver Nameserver name entity Entity handle help Help text, value is optional Search types, subtypes, and values: ----------------------------------- domains name Search for domains by name prefix nameservers name Search for nameservers by name prefix nameservers ip Search for nameservers by IP entities fn Search for entities by full name entities handle Search for entities by handle R's, John From nobody Mon Apr 14 11:05:38 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E8AE1A06D7 for ; Mon, 14 Apr 2014 11:05:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3-w53Xm81O_8 for ; Mon, 14 Apr 2014 11:05:30 -0700 (PDT) Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id E4C661A06CC for ; Mon, 14 Apr 2014 11:05:29 -0700 (PDT) Received: by mail-wg0-f49.google.com with SMTP id a1so8547414wgh.20 for ; Mon, 14 Apr 2014 11:05:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2Y1OzzzEaYpjXlKH5h9Mq7vwJOWQS08AfBhe8P6HyFM=; b=o0HLFgQ1XDoqmQvbaDzbeWOAox2Uz+Ds9TjfO6bPL+Pu7WYQnlBtzGfF6X8+qSexod /r7ZpSXX5b5xP1w0sY88jAAdGanyoxibs2GU3sWDFA7PZ9fIYuupwJwF8IbxFJXbb92B xDWcdW8HOR1W8+F0u4WYytz9NBPlMppZ9UdiZgpGi/E3BqNGj+ob030uXkZw+B3mn35u Z6/CSTuSSUWUcDkE7OQVHQI4VUcmaB1oxtQ/OkNY/mr5qffa7U1FEdti0olfZDFpRQfx HMerAeSYgbBCqPDu6p5KL0uXQRFWTeoJ03qa1H5kgFlqi5EnmPUPlRUbinnm024EcdEs fUCQ== MIME-Version: 1.0 X-Received: by 10.194.76.10 with SMTP id g10mr2495668wjw.67.1397498726923; Mon, 14 Apr 2014 11:05:26 -0700 (PDT) Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 11:05:26 -0700 (PDT) In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F493A020C@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <060.b2ab04d2716ada34d0a26f7de381d988@tools.ietf.org> <831693C2CDA2E849A7D7A712B24E257F493A020C@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Date: Mon, 14 Apr 2014 11:05:26 -0700 Message-ID: From: "Murray S. Kucherawy" To: "Hollenbeck, Scott" Content-Type: multipart/alternative; boundary=047d7bf0c0803170d304f70487d6 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/bnBjJ1Jne3pbd0AaCQiFW79AW2g Cc: "weirds@ietf.org" Subject: Re: [weirds] #25 (rdap-query): Clarify what is done with unsupported queries 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, 14 Apr 2014 18:05:35 -0000 --047d7bf0c0803170d304f70487d6 Content-Type: text/plain; charset=UTF-8 On Mon, Apr 14, 2014 at 3:57 AM, Hollenbeck, Scott wrote: > Would it be sufficient to provide a reference to this text from the > using-http document? > > "5.4. Malformed Queries > > If a server receives a query which it cannot interpret as an RDAP > query, it returns a 400 response code. Optionally, it MAY include > additional information regarding this negative answer in the HTTP > entity body." > Does that include the unknown types? I would think such a query is still recognizable as an RDAP query, just with a type that isn't locally supported. -MSK --047d7bf0c0803170d304f70487d6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Mon, Apr 14, 2014 at 3:57 AM, Hollenbeck, Scott <shollenbeck@verisign.com> wrote:
Would it be sufficient to provide a referenc= e to this text from the using-http document?

"5.4. =C2=A0Malformed Queries

=C2=A0 =C2=A0If a server receives a query which it cannot interpret as an R= DAP
=C2=A0 =C2=A0query, it returns a 400 response code. =C2=A0Optionally, it MA= Y include
=C2=A0 =C2=A0additional information regarding this negative answer in the H= TTP
=C2=A0 =C2=A0entity body."

Does th= at include the unknown types?=C2=A0 I would think such a query is still rec= ognizable as an RDAP query, just with a type that isn't locally support= ed.

-MSK
--047d7bf0c0803170d304f70487d6-- From nobody Mon Apr 14 12:01:10 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B299F1A0201 for ; Mon, 14 Apr 2014 12:01:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nz_BbHSHYiRG for ; Mon, 14 Apr 2014 12:01:04 -0700 (PDT) Received: from exprod6og113.obsmtp.com (exprod6og113.obsmtp.com [64.18.1.31]) by ietfa.amsl.com (Postfix) with ESMTP id B75FC1A0664 for ; Mon, 14 Apr 2014 12:00:53 -0700 (PDT) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob113.postini.com ([64.18.5.12]) with SMTP ID DSNKU0wwY5lnMjFYmujojeSEFvV6JPj5IuM9@postini.com; Mon, 14 Apr 2014 12:00:52 PDT Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id s3EJ0oIk021438 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 14 Apr 2014 15:00:50 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 14 Apr 2014 15:00:50 -0400 From: "Hollenbeck, Scott" To: "Murray S. Kucherawy" Thread-Topic: [weirds] #25 (rdap-query): Clarify what is done with unsupported queries Thread-Index: AQHPV7H5bGteZtfWgEGG0kPDsiHCipsQ8M3ggAC7FgD//8eiIA== Date: Mon, 14 Apr 2014 19:00:49 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F493A1137@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <060.b2ab04d2716ada34d0a26f7de381d988@tools.ietf.org> <831693C2CDA2E849A7D7A712B24E257F493A020C@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: multipart/alternative; boundary="_000_831693C2CDA2E849A7D7A712B24E257F493A1137BRN1WNEXMBX01vc_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/dguVpvbAfU0WjDb27PNW5B5Qq0U Cc: "weirds@ietf.org" Subject: Re: [weirds] #25 (rdap-query): Clarify what is done with unsupported queries 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, 14 Apr 2014 19:01:08 -0000 --_000_831693C2CDA2E849A7D7A712B24E257F493A1137BRN1WNEXMBX01vc_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 RnJvbTogTXVycmF5IFMuIEt1Y2hlcmF3eSBbbWFpbHRvOnN1cGVydXNlckBnbWFpbC5jb21dDQpT ZW50OiBNb25kYXksIEFwcmlsIDE0LCAyMDE0IDI6MDUgUE0NClRvOiBIb2xsZW5iZWNrLCBTY290 dA0KQ2M6IHdlaXJkc0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IFt3ZWlyZHNdICMyNSAocmRhcC1x dWVyeSk6IENsYXJpZnkgd2hhdCBpcyBkb25lIHdpdGggdW5zdXBwb3J0ZWQgcXVlcmllcw0KDQpP biBNb24sIEFwciAxNCwgMjAxNCBhdCAzOjU3IEFNLCBIb2xsZW5iZWNrLCBTY290dCA8c2hvbGxl bmJlY2tAdmVyaXNpZ24uY29tPG1haWx0bzpzaG9sbGVuYmVja0B2ZXJpc2lnbi5jb20+PiB3cm90 ZToNCldvdWxkIGl0IGJlIHN1ZmZpY2llbnQgdG8gcHJvdmlkZSBhIHJlZmVyZW5jZSB0byB0aGlz IHRleHQgZnJvbSB0aGUgdXNpbmctaHR0cCBkb2N1bWVudD8NCg0KIjUuNC4gIE1hbGZvcm1lZCBR dWVyaWVzDQoNCiAgIElmIGEgc2VydmVyIHJlY2VpdmVzIGEgcXVlcnkgd2hpY2ggaXQgY2Fubm90 IGludGVycHJldCBhcyBhbiBSREFQDQogICBxdWVyeSwgaXQgcmV0dXJucyBhIDQwMCByZXNwb25z ZSBjb2RlLiAgT3B0aW9uYWxseSwgaXQgTUFZIGluY2x1ZGUNCiAgIGFkZGl0aW9uYWwgaW5mb3Jt YXRpb24gcmVnYXJkaW5nIHRoaXMgbmVnYXRpdmUgYW5zd2VyIGluIHRoZSBIVFRQDQogICBlbnRp dHkgYm9keS4iDQoNCkRvZXMgdGhhdCBpbmNsdWRlIHRoZSB1bmtub3duIHR5cGVzPyAgSSB3b3Vs ZCB0aGluayBzdWNoIGEgcXVlcnkgaXMgc3RpbGwgcmVjb2duaXphYmxlIGFzIGFuIFJEQVAgcXVl cnksIGp1c3Qgd2l0aCBhIHR5cGUgdGhhdCBpc24ndCBsb2NhbGx5IHN1cHBvcnRlZC4NCltTQUhd IEl0IGNvdWxkIGluY2x1ZGUgYm90aCB1bmtub3duIHR5cGVzIGFuZCBtYWxmb3JtZWQgcXVlcnkg c3ludGF4LCBuZWl0aGVyIG9mIHdoaWNoIGFyZSB2YWxpZCBxdWVyaWVzIGJlY2F1c2UgdGhleSBj YW7igJl0IGJlIGludGVycHJldGVkLiBUaGUgdGV4dCBJIGFkZCB0byByZGFwLXF1ZXJ5IGNvdWxk IG1ha2UgaXQgY2xlYXIgdGhhdCB0aGlzIGlzIGhvdyB0byByZXNwb25kIHRvIGFsbCBxdWVyaWVz IHRoYXQgY2Fu4oCZdCBiZSByZWNvZ25pemVkIGFzIG9uZSBvZiB0aGUgZGVmaW5lZCB0eXBlcy4N Cg0KU2NvdHQNCg== --_000_831693C2CDA2E849A7D7A712B24E257F493A1137BRN1WNEXMBX01vc_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6 Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z b05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6 Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNv LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEOw0KCWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglmb250LXN0 eWxlOm5vcm1hbDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25s eTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO30NCkBwYWdlIFdvcmRTZWN0 aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4w aW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxl PjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIg c3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48 eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQi IGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+ DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNs YXNzPSJXb3JkU2VjdGlvbjEiPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6 c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2 IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGlu ZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHls ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7 c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6 MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1 b3Q7Ij4gTXVycmF5IFMuIEt1Y2hlcmF3eSBbbWFpbHRvOnN1cGVydXNlckBnbWFpbC5jb21dDQo8 YnI+DQo8Yj5TZW50OjwvYj4gTW9uZGF5LCBBcHJpbCAxNCwgMjAxNCAyOjA1IFBNPGJyPg0KPGI+ VG86PC9iPiBIb2xsZW5iZWNrLCBTY290dDxicj4NCjxiPkNjOjwvYj4gd2VpcmRzQGlldGYub3Jn PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbd2VpcmRzXSAjMjUgKHJkYXAtcXVlcnkpOiBDbGFy aWZ5IHdoYXQgaXMgZG9uZSB3aXRoIHVuc3VwcG9ydGVkIHF1ZXJpZXM8bzpwPjwvbzpwPjwvc3Bh bj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8 L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gTW9uLCBBcHIgMTQsIDIw MTQgYXQgMzo1NyBBTSwgSG9sbGVuYmVjaywgU2NvdHQgJmx0OzxhIGhyZWY9Im1haWx0bzpzaG9s bGVuYmVja0B2ZXJpc2lnbi5jb20iIHRhcmdldD0iX2JsYW5rIj5zaG9sbGVuYmVja0B2ZXJpc2ln bi5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGJsb2Nr cXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7 cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6 MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPldvdWxkIGl0IGJlIHN1ZmZpY2llbnQgdG8gcHJv dmlkZSBhIHJlZmVyZW5jZSB0byB0aGlzIHRleHQgZnJvbSB0aGUgdXNpbmctaHR0cCBkb2N1bWVu dD88YnI+DQo8YnI+DQomcXVvdDs1LjQuICZuYnNwO01hbGZvcm1lZCBRdWVyaWVzPGJyPg0KPGJy Pg0KJm5ic3A7ICZuYnNwO0lmIGEgc2VydmVyIHJlY2VpdmVzIGEgcXVlcnkgd2hpY2ggaXQgY2Fu bm90IGludGVycHJldCBhcyBhbiBSREFQPGJyPg0KJm5ic3A7ICZuYnNwO3F1ZXJ5LCBpdCByZXR1 cm5zIGEgNDAwIHJlc3BvbnNlIGNvZGUuICZuYnNwO09wdGlvbmFsbHksIGl0IE1BWSBpbmNsdWRl PGJyPg0KJm5ic3A7ICZuYnNwO2FkZGl0aW9uYWwgaW5mb3JtYXRpb24gcmVnYXJkaW5nIHRoaXMg bmVnYXRpdmUgYW5zd2VyIGluIHRoZSBIVFRQPGJyPg0KJm5ic3A7ICZuYnNwO2VudGl0eSBib2R5 LiZxdW90OzxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9 Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5Eb2VzIHRoYXQgaW5jbHVk ZSB0aGUgdW5rbm93biB0eXBlcz8mbmJzcDsgSSB3b3VsZCB0aGluayBzdWNoIGEgcXVlcnkgaXMg c3RpbGwgcmVjb2duaXphYmxlIGFzIGFuIFJEQVAgcXVlcnksIGp1c3Qgd2l0aCBhIHR5cGUgdGhh dCBpc24ndCBsb2NhbGx5IHN1cHBvcnRlZC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5bU0FIXSBJ dCBjb3VsZCBpbmNsdWRlIGJvdGggdW5rbm93biB0eXBlcyBhbmQgbWFsZm9ybWVkIHF1ZXJ5IHN5 bnRheCwgbmVpdGhlciBvZiB3aGljaCBhcmUgdmFsaWQgcXVlcmllcyBiZWNhdXNlIHRoZXkgY2Fu 4oCZdCBiZSBpbnRlcnByZXRlZC4gVGhlIHRleHQgSSBhZGQgdG8gcmRhcC1xdWVyeSBjb3VsZCBt YWtlIGl0IGNsZWFyIHRoYXQgdGhpcyBpcyBob3cgdG8NCiByZXNwb25kIHRvIGFsbCBxdWVyaWVz IHRoYXQgY2Fu4oCZdCBiZSByZWNvZ25pemVkIGFzIG9uZSBvZiB0aGUgZGVmaW5lZCB0eXBlcy48 bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z b05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPlNjb3R0PG86cD48L286cD48L3Nw YW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K PC9ib2R5Pg0KPC9odG1sPg0K --_000_831693C2CDA2E849A7D7A712B24E257F493A1137BRN1WNEXMBX01vc_-- From nobody Mon Apr 14 12:50: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 672111A0706 for ; Mon, 14 Apr 2014 12:50:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IExv3irlLPRA for ; Mon, 14 Apr 2014 12:50:16 -0700 (PDT) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 932FE1A0719 for ; Mon, 14 Apr 2014 12:50:16 -0700 (PDT) Received: by mail-wg0-f52.google.com with SMTP id k14so8502659wgh.11 for ; Mon, 14 Apr 2014 12:50:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9wLJ9kTQGanGVCr2xCqNngfusyTMv/FL9TghBVSR+gY=; b=BcuyQhmw8mK8DeguPhzYQIf2wMCjHdpvi/vV1V66aReLUS6y0Yh7epOAPmFanfVkOt X3wakSNC+/b9xXa5dOWgf6QusPKIm3jeKlLHiQNx5KiBXVt0pxd9YYveRSNg6bFkdPg2 VKhhmw2XCq+/cCaUtyXvFluuLkRN6/wL3IojybC7udHGvROQRSa2XOBB69dRwwSHWYsu uGJOiHYcFVoHDmdevlzCWCCRHzV+2rjdOCB8hqILUGU0QNqOkNZJUIGOAnoLxysK/uff vBOxtL3Bk1VEFym0TXIQzxX5CAfG64CrfbgtcEatzhK1vNkVptLlzvJRplWzEFK9oqVH iiUA== MIME-Version: 1.0 X-Received: by 10.194.89.168 with SMTP id bp8mr34082wjb.73.1397505013597; Mon, 14 Apr 2014 12:50:13 -0700 (PDT) Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 12:50:13 -0700 (PDT) In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F493A1137@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <060.b2ab04d2716ada34d0a26f7de381d988@tools.ietf.org> <831693C2CDA2E849A7D7A712B24E257F493A020C@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F493A1137@BRN1WNEXMBX01.vcorp.ad.vrsn.com> Date: Mon, 14 Apr 2014 12:50:13 -0700 Message-ID: From: "Murray S. Kucherawy" To: "Hollenbeck, Scott" Content-Type: multipart/alternative; boundary=047d7bf10a1ce84bc704f705fd9b Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/X74_C9mE28LwXA6WnJlJaB2gpPo Cc: "weirds@ietf.org" Subject: Re: [weirds] #25 (rdap-query): Clarify what is done with unsupported queries 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, 14 Apr 2014 19:50:21 -0000 --047d7bf10a1ce84bc704f705fd9b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Apr 14, 2014 at 12:00 PM, Hollenbeck, Scott < shollenbeck@verisign.com> wrote: > *From:* Murray S. Kucherawy [mailto:superuser@gmail.com] > *Sent:* Monday, April 14, 2014 2:05 PM > *To:* Hollenbeck, Scott > *Cc:* weirds@ietf.org > *Subject:* Re: [weirds] #25 (rdap-query): Clarify what is done with > unsupported queries > > > > On Mon, Apr 14, 2014 at 3:57 AM, Hollenbeck, Scott < > shollenbeck@verisign.com> wrote: > > Would it be sufficient to provide a reference to this text from the > using-http document? > > "5.4. Malformed Queries > > If a server receives a query which it cannot interpret as an RDAP > query, it returns a 400 response code. Optionally, it MAY include > additional information regarding this negative answer in the HTTP > entity body." > > > > Does that include the unknown types? I would think such a query is still > recognizable as an RDAP query, just with a type that isn't locally > supported. > > [SAH] It could include both unknown types and malformed query syntax, > neither of which are valid queries because they can=E2=80=99t be interpre= ted. The > text I add to rdap-query could make it clear that this is how to respond = to > all queries that can=E2=80=99t be recognized as one of the defined types. > > > That works if we're not interested in (i.e., there is no benefit to) distinguishing between syntactically invalid queries vs. unsupported query types. Is that the case here? I'm not trying to lead us in one direction or the other; I just want the reasoning to be explicit. -MSK --047d7bf10a1ce84bc704f705fd9b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Mon, Apr 14, 2014 at 12:00 PM, Hollenbeck, Scott <shollenbeck@verisign.com> wrote:

From: Murray S= . Kucherawy [mailto:superuser@gmail.com]
Sent: Monday, April 14, 2014 2:05 PM
To: Hollenbeck, Scott
Cc: weirds@ietf= .org
Subject: Re: [weirds] #25 (rdap-query): Clarify what is done with un= supported queries

=C2=A0

On Mon, Apr 14, 2014 at 3:57 AM, Hollenbeck, Scott &= lt;shollenbec= k@verisign.com> wrote:

Would it be sufficient to provide a reference to thi= s text from the using-http document?

"5.4. =C2=A0Malformed Queries

=C2=A0 =C2=A0If a server receives a query which it cannot interpret as an R= DAP
=C2=A0 =C2=A0query, it returns a 400 response code. =C2=A0Optionally, it MA= Y include
=C2=A0 =C2=A0additional information regarding this negative answer in the H= TTP
=C2=A0 =C2=A0entity body."

=C2=A0

Does that include the= unknown types?=C2=A0 I would think such a query is still recognizable as a= n RDAP query, just with a type that isn't locally supported.<= /u>

[SAH] It could include= both unknown types and malformed query syntax, neither of which are valid = queries because they can=E2=80=99t be interpreted. The text I add to rdap-q= uery could make it clear that this is how to respond to all queries that can=E2=80=99t be recognized as one of the defi= ned types.

<= font color=3D"#888888">

=C2=A0


That works if we're not interested in (i.e., there is no benef= it to) distinguishing between syntactically invalid queries vs. unsupported= query types.=C2=A0 Is that the case here?

I'm not trying to lead us in one direction or the other;= I just want the reasoning to be explicit.

-MSK
=
--047d7bf10a1ce84bc704f705fd9b-- From nobody Mon Apr 14 15:23: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 814961A0764 for ; Mon, 14 Apr 2014 15:23:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.542 X-Spam-Level: * X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z7EzRaS56yrm for ; Mon, 14 Apr 2014 15:23:07 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4B2541A0762 for ; Mon, 14 Apr 2014 15:23:07 -0700 (PDT) Received: (qmail 61939 invoked from network); 14 Apr 2014 22:23:04 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 14 Apr 2014 22:23:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=7dff.534c5fc8.k1404; i=johnl@user.iecc.com; bh=uP7cQ0tiav9uBLl0fs46tlvc64zDTfdKSfyx7HACNDY=; b=bENn3mGShNJ6eeRWt4bv+OQeWpvxavr3/cFmCS7NgETwqbMXdabENRSbRJzsN2IF3W/BG9eMOpAfHX6gV6IhN33/LK4L7s89G4ohVcKZz2ejdFg0OMpD+G+Bdyw4wHRWwxuDWA/X/FKjBGeZlHXlCZPNQjcNqR4BJD0V9Usc3d7RXE9JiE+Uvsl8x//2NCVIVLwYLVjqL5rQjM1A4TL4lyxnBEJYRH/Pz2oZKxQPr0d4BtGBMbdlFLvUA80cR+zr 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=7dff.534c5fc8.k1404; olt=johnl@user.iecc.com; bh=uP7cQ0tiav9uBLl0fs46tlvc64zDTfdKSfyx7HACNDY=; b=wuKhV/uWTN0/rhwJjM99gAbzeinnUNwNcGSBqNt3Bb0KIn9c/g1aOo08vzKTOq5SShaDAHpXgQz6zpU9GJyO6S864bfJ+3bya9BWxI6akmvO3yKDQkW8MStI1Y4l0aACo0eK/qlkxVN6SjGd1TJn6xxg8VJjV23VIW+0tTDgTa/8S1jEmxis3JsR6CdQYLll0IZeIdWc3YM3DUU2LV4i89a4q8kegc5jDUz084m/LON3OhAP8etcHpn4oUI/h+aS Date: 14 Apr 2014 22:22:42 -0000 Message-ID: <20140414222242.32254.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/1VhbAsADqhFbJwOgr2e_W_szCOo Subject: Re: [weirds] #25 (rdap-query): Clarify what is done with unsupported queries 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, 14 Apr 2014 22:23:11 -0000 >> "5.4. Malformed Queries >> >> If a server receives a query which it cannot interpret as an RDAP >> query, it returns a 400 response code. Optionally, it MAY include >> additional information regarding this negative answer in the HTTP >> entity body." >> > >Does that include the unknown types? I would think such a query is still >recognizable as an RDAP query, just with a type that isn't locally >supported. It seems unlikely that a server would know the difference between an type that exists but it doesn't support and a random string, particularly if new query types are added down the road. Code 400 seems adequate for either. If we're telling people what codes to use, from my reading of RFC 2616, a well formed query that the server can't answer, e.g., asking about an entity handle that doesn't exist or a pattern that matches nothing, gets a 404. A query for something that needs authentication, e.g., registrant's address and phone for registries that protect them, gets 401. There might be a few others, maybe 416 for unsupported media type if the query asks for XML and the server only does JSON and XML. R's, John From nobody Mon Apr 14 17:15:51 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A11BC1A044C for ; Mon, 14 Apr 2014 17:15:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1gUb-mcGNHod for ; Mon, 14 Apr 2014 17:15:47 -0700 (PDT) Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 807891A0440 for ; Mon, 14 Apr 2014 17:15:47 -0700 (PDT) Received: by mail-we0-f174.google.com with SMTP id t60so8751615wes.19 for ; Mon, 14 Apr 2014 17:15:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nvLDEILShln0mlNTNWcVIykJyrP7hDTAA30ULEMWjAs=; b=N4GJTYfAsg5WWjcAVwsJjMAOInZe2zU4r7FzhpfxPushI54L2Be2cmdp77xY81jJU7 Jfx8bN7JkWp3iT554qurJW1+xw/Or+wOO4wsEfGdYGU8cuMvpKXnx3HvrTHfpethwBNP N+3DESv6tYcttv7y6F+28MfieyOYZOQJbtSFfXyeMq6KE6hFn6xgtnexckQtGnAug/dU CkJ9mrF6pmD1DyVYXvQAoInOe+5Ubh14gbUMeui83TtKWV9TUZDilIfpa21oxESLNI5z LOAq3T0nGxO31n27GzHKJvb9tVXXMx+tgJIRn63gsU5DLA1Q6FXJFhTgQRsa8XWwLZNT gzrA== MIME-Version: 1.0 X-Received: by 10.180.84.129 with SMTP id z1mr11586770wiy.8.1397520944404; Mon, 14 Apr 2014 17:15:44 -0700 (PDT) Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 17:15:44 -0700 (PDT) In-Reply-To: <20140414222242.32254.qmail@joyce.lan> References: <20140414222242.32254.qmail@joyce.lan> Date: Mon, 14 Apr 2014 17:15:44 -0700 Message-ID: From: "Murray S. Kucherawy" To: John Levine Content-Type: multipart/alternative; boundary=f46d043bdec0751f1604f709b347 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/4vz7lW7MqGIBPzuf4uA3dH54W-I Cc: "weirds@ietf.org" Subject: Re: [weirds] #25 (rdap-query): Clarify what is done with unsupported queries 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, 15 Apr 2014 00:15:49 -0000 --f46d043bdec0751f1604f709b347 Content-Type: text/plain; charset=UTF-8 On Mon, Apr 14, 2014 at 3:22 PM, John Levine wrote: > >> "5.4. Malformed Queries > >> > >> If a server receives a query which it cannot interpret as an RDAP > >> query, it returns a 400 response code. Optionally, it MAY include > >> additional information regarding this negative answer in the HTTP > >> entity body." > >> > > > >Does that include the unknown types? I would think such a query is still > >recognizable as an RDAP query, just with a type that isn't locally > >supported. > > It seems unlikely that a server would know the difference between an > type that exists but it doesn't support and a random string, > particularly if new query types are added down the road. Code 400 > seems adequate for either. > I guess I'm envisioning a query that includes a string like "...?type=foobar..." where the server receiving the query parses the URI and doesn't understand what a "foobar" is, but the rest is valid. To my mind that's semantics, not syntax; "foobar" fits the ABNF, but isn't known. --f46d043bdec0751f1604f709b347 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Mon, Apr 14, 2014 at 3:22 PM, John Levine <johnl@taugh.c= om> wrote:
>> "5.4. =C2=A0Malformed Queries
>>
>> =C2=A0 =C2=A0If a server receives a query which it cannot interpre= t as an RDAP
>> =C2=A0 =C2=A0query, it returns a 400 response code. =C2=A0Optional= ly, it MAY include
>> =C2=A0 =C2=A0additional information regarding this negative answer= in the HTTP
>> =C2=A0 =C2=A0entity body."
>>
>
>Does that include the unknown types? =C2=A0I would think such a query i= s still
>recognizable as an RDAP query, just with a type that isn't locally<= br> >supported.

It seems unlikely that a server would know the difference between an<= br> type that exists but it doesn't support and a random string,
particularly if new query types are added down the road. =C2=A0Code 400
seems adequate for either.

I guess I= 9;m envisioning a query that includes a string like "...?type=3Dfoobar= ..." where the server receiving the query parses the URI and doesn'= ;t understand what a "foobar" is, but the rest is valid.=C2=A0 To= my mind that's semantics, not syntax; "foobar" fits the ABNF= , but isn't known.
--f46d043bdec0751f1604f709b347-- From nobody Mon Apr 14 19:03:49 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD581A02CA for ; Mon, 14 Apr 2014 19:03:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.542 X-Spam-Level: * X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_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 wiZhQvK7-EdG for ; Mon, 14 Apr 2014 19:03:45 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 57D5F1A0259 for ; Mon, 14 Apr 2014 19:03:45 -0700 (PDT) Received: (qmail 96573 invoked from network); 15 Apr 2014 02:03:42 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 15 Apr 2014 02:03:42 -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=8126.534c937e.k1404; i=johnl@user.iecc.com; bh=tGxpEjeemS3hQWZ04d4gBhDJ2D6KgejLAjzsoXWsPZ4=; b=SPVTaNqZ+7y5OsSOyRMU0VNS1JL9NejwB7JBXpPOPzi1AoJCwdZtO7PPmSbHRvTWUQfzSGZFnAR8LV9pbZWTkrKCOllv1pzFRq1wCebxFsw441zewKkqRoxXOBB7IK7Gk8O9JEa2x6Zqqmd90s/WkeX+e40if3bCOgqKInbAGsk3kH6zeV3ZVmCDWFxrIQXBdDebE8fx3WftUdIxDN0YAqhLhZZU/EJfgoOu4QGnf0PWaAqHh2MFVNLZjVVMlUnA 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=8126.534c937e.k1404; olt=johnl@user.iecc.com; bh=tGxpEjeemS3hQWZ04d4gBhDJ2D6KgejLAjzsoXWsPZ4=; b=MvXYesjhpy9DvCAY6kIlpEfL6gse+wo2rP7F8xAyUqZaAIYl+KugeDXAd7cLYwO6wpYxlPv6+MTbqJbwUgexGGCsotcnqcKKx+Po02ZGFX8Sk+bnfsRda9QqYKIXwPC7MciOLgw0VcWsUNepD+8nIfWvRhVBXKKqqkdlPuFHPMg6wyFXrhZUe00MVEUX/XFtPiYYeLUHjP7MX2q7igs0uXH/XYL4VYP9XDmk4TftbUrLFTbWmjUm/SL/B5fkPxAM Date: 15 Apr 2014 02:03:20 -0000 Message-ID: <20140415020320.33061.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/IKop6tgK5clOBD2pW5i8JwB_LJA Subject: Re: [weirds] #25 (rdap-query): Clarify what is done with unsupported queries 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, 15 Apr 2014 02:03:46 -0000 >> It seems unlikely that a server would know the difference between an >> type that exists but it doesn't support and a random string, >> particularly if new query types are added down the road. Code 400 >> seems adequate for either. > >I guess I'm envisioning a query that includes a string like >"...?type=foobar..." where the server receiving the query parses the URI >and doesn't understand what a "foobar" is, but the rest is valid. To my >mind that's semantics, not syntax; "foobar" fits the ABNF, but isn't known. For a query, it's the "type" the server has to understand, and "foobar" is a search query. But also remember that many (most?) web servers parse up the query string and the application typically ignores the fields it doesn't understand. So if you send: /search?pickle=dill and there's no "pickle" search, it'll in effect see this: /search and that's just ill formed. R's, John From nobody Wed Apr 16 22:00: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 2B8E11A046F for ; Wed, 16 Apr 2014 22:00:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.43 X-Spam-Level: *** X-Spam-Status: No, score=3.43 tagged_above=-999 required=5 tests=[BAYES_99=3.5, BAYES_999=0.2, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272] 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 4Dg7rxDlldqz for ; Wed, 16 Apr 2014 22:00:34 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 9E99A1A045E for ; Wed, 16 Apr 2014 22:00:33 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn Received: from unknown127.0.0.1 (HELO user-think) (127.0.0.1) by 127.0.0.1 with SMTP; Thu, 17 Apr 2014 13:00:27 +0800 Date: Thu, 17 Apr 2014 13:00:29 +0800 From: "Linlin Zhou" To: weirds X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7, 2, 5, 136[cn] Mime-Version: 1.0 Message-ID: <2014041713002928844263@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart430704656741_=----" Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/cfMAlyCzHRUfMK1DpTCpJRZZRoI Subject: [weirds] Empty search status code 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, 17 Apr 2014 05:00:35 -0000 This is a multi-part message in MIME format. ------=_001_NextPart430704656741_=---- Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: base64 RGVhciBhbGwsDQpJIGhhdmUgYSBxdWVzdGlvbiBhYm91dCB0aGUgZW1wdHkgc2VhcmNoIHN0YXR1 cyBjb2RlLiANCldoZW4gc2VhcmNoaW5nIGRvbWFpbiwgbmFtZXNlcnZlciBvciBlbnRpdHksIHNl cnZlciByZXR1cm5zIGVtcHR5IHJlc3VsdHMuIEN1cnJlbnRseSwgd2UgaGFuZGxlIHF1ZXJ5IGFu ZCBzZWFyY2ggaW4gdGhlIHNhbWUsIGJvdGggcmV0dXJuIDQwNCBpZiB0aGVyZSBpcyBubyBpbmZv cm1haXRvbiB0byByZXNwb25kLiBCdXQgbWF5YmUgdGhlIGVtcHR5IHNlYXJjaCBpbmZvcm1hdGlv biBpcyBzb21ldGhpbmcgdXNlZnVsIHRvIGNsaWVudCwgcmVzcG9uZGluZyAyMDAgYW5kIGVtcHR5 IHJlc3VsdCBzZXQgbWFrZXMgc2Vuc2UgYXMgd2VsbC4gV2hpY2ggaHR0cCBjb2RlIGlzIHByb3Bl ciwgMjAwIG9yIDQwND8NCg0KUmVnYXJkcywNCg0KDQpMaW5saW4gWmhvdQ0K ------=_001_NextPart430704656741_=---- Content-Type: text/html; charset="GB2312" Content-Transfer-Encoding: quoted-printable =0A
Dear all,
I have a question about the empty searc= h status code. 
When searching domain, nameserver or entity, server ret= urns empty results. Currently, we handle query and search= in the same, both return 404 if there is no informaiton to respond. But m= aybe the empty search information is something useful to client, respondin= g 200 and empty result set makes sense as well. Which htt= p code is proper, 200 or 404?

Regards,
=
=0A
Linlin Zhou
=0A ------=_001_NextPart430704656741_=------ From nobody Thu Apr 17 07:09: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 063FA1A0043 for ; Thu, 17 Apr 2014 07:09:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8KPV6CvEJW9b for ; Thu, 17 Apr 2014 07:09:29 -0700 (PDT) Received: from mail-qa0-f46.google.com (mail-qa0-f46.google.com [209.85.216.46]) by ietfa.amsl.com (Postfix) with ESMTP id ADDB81A019D for ; Thu, 17 Apr 2014 07:09:27 -0700 (PDT) Received: by mail-qa0-f46.google.com with SMTP id i13so426558qae.33 for ; Thu, 17 Apr 2014 07:09:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=R52sPFWt2dFcEsZjxwZNElHh8OV61A/Xcr/2TvY83+E=; b=ZhtOvgRB5wIJ+nvADCh6VgpYurGZgIOYcVgkZaPJ51T9vdz5cv3zSh6bJX8eOqC1/E YcVCPNcGcw49aeTpXQRVLuU8TXpVL057l7sqjp9csOeZuwycAL3ngLXJZfvu662adA0W Px7gQ2uWqf9N1IUxnAQFRe6/Bed5dqW6Kr39G3rfwEO7QBBNfeitI8JqzFQIJVi9OWen YfFZWOELxe+9gc27er0Xevh3o7e3VlExt2c1ooJtw/qEsLGOwAviJiXbe66gbfKHRZ+N VDvqLmDOU5zYQe8APHyg0t50f3NmxbBoehZzuqLsrQ/wyz+dpCBP4uUBofR86yE9clSf cLKw== X-Gm-Message-State: ALoCoQkCas+w9GtamZjGZR9Ig9uH0iFptuclVnHazgK2h1vlXkUgbfG+3ygUxUYFFtWKbTa5WGYd MIME-Version: 1.0 X-Received: by 10.224.29.4 with SMTP id o4mr11161219qac.55.1397743762374; Thu, 17 Apr 2014 07:09:22 -0700 (PDT) Received: by 10.140.36.45 with HTTP; Thu, 17 Apr 2014 07:09:22 -0700 (PDT) X-Originating-IP: [2001:500:4:34::130] In-Reply-To: <2014041713002928844263@cnnic.cn> References: <2014041713002928844263@cnnic.cn> Date: Thu, 17 Apr 2014 09:09:22 -0500 Message-ID: From: Andrew Newton To: Linlin Zhou Content-Type: text/plain; charset=ISO-8859-1 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/vFwiQnd9sizE9bW9lkG1NqEOvqI Cc: weirds Subject: Re: [weirds] Empty search status code 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, 17 Apr 2014 14:09:33 -0000 For simple clients, a 404 is a simple check. And just because you return a 404 doesn't mean you cannot also return a JSON response body with empty results. -andy On Thu, Apr 17, 2014 at 12:00 AM, Linlin Zhou wrote: > Dear all, > I have a question about the empty search status code. > When searching domain, nameserver or entity, server returns empty results. > Currently, we handle query and search in the same, both return 404 if there > is no informaiton to respond. But maybe the empty search information is > something useful to client, responding 200 and empty result set makes sense > as well. Which http code is proper, 200 or 404? > > Regards, > ________________________________ > Linlin Zhou > > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds > From nobody Thu Apr 17 07:53: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 543F61A01BA for ; Thu, 17 Apr 2014 07:53:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.173 X-Spam-Level: X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, 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 1osmKR8UpYJX for ; Thu, 17 Apr 2014 07:53:39 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 216681A0246 for ; Thu, 17 Apr 2014 07:53:34 -0700 (PDT) Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:2520:ef8a:477:622f]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 73038403D3 for ; Thu, 17 Apr 2014 10:53:30 -0400 (EDT) Message-ID: <534FEAEA.8080909@viagenie.ca> Date: Thu, 17 Apr 2014 10:53:30 -0400 From: Simon Perreault User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: weirds@ietf.org References: <2014041713002928844263@cnnic.cn> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/Rinx94cAIEvrG86JIMPrEZIxKVY Subject: Re: [weirds] Empty search status code 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, 17 Apr 2014 14:53:40 -0000 Le 2014-04-17 10:09, Andrew Newton a écrit : > For simple clients, a 404 is a simple check. And just because you > return a 404 doesn't mean you cannot also return a JSON response body > with empty results. Whatever the outcome is (I don't care), please state it explicitly in the next draft revision. 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 From nobody Thu Apr 17 18:33:04 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB3B1A021F for ; Thu, 17 Apr 2014 18:33:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.17 X-Spam-Level: X-Spam-Status: No, score=-2.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272] 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 ppJIBn_lexp0 for ; Thu, 17 Apr 2014 18:32:56 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id CBFFB1A003A for ; Thu, 17 Apr 2014 18:32:55 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn Received: from unknown127.0.0.1 (HELO user-think) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 18 Apr 2014 09:32:49 +0800 Date: Fri, 18 Apr 2014 09:32:53 +0800 From: "Linlin Zhou" To: "Andrew Newton" References: <2014041713002928844263@cnnic.cn>, X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7, 2, 5, 136[cn] Mime-Version: 1.0 Message-ID: <2014041809325264054412@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart658362631073_=----" Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/udGxee1j4UEw2iYFNUAi6H9FXtE Cc: weirds Subject: Re: [weirds] Empty search status code 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, 18 Apr 2014 01:33:02 -0000 This is a multi-part message in MIME format. ------=_001_NextPart658362631073_=---- Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 U28gbXkgdGFrZSBpcywNCiMxIEp1c3QgcmV0dXJuIDQwNA0KIzIgUmV0dXJuIDQwNCB3aXRoIGVt cHR5IHJlc3VsdHMNCiMzIFJldHVybiAyMDAgd2l0aCBlbXB0eSByZXN1bHRzDQoNCkJvdGggIzEg YW5kICMyIGFyZSBhbGxvd2VkIGluIGh0dHAgZHJhZnQuIFJpZ2h0Pw0KDQpSZWdhcmRzLA0KDQoN CkxpbmxpbiBaaG91DQogDQpGcm9tOiBBbmRyZXcgTmV3dG9uDQpEYXRlOiAyMDE0LTA0LTE3IDIy OjA5DQpUbzogTGlubGluIFpob3UNCkNDOiB3ZWlyZHMNClN1YmplY3Q6IFJlOiBbd2VpcmRzXSBF bXB0eSBzZWFyY2ggc3RhdHVzIGNvZGUNCkZvciBzaW1wbGUgY2xpZW50cywgYSA0MDQgaXMgYSBz aW1wbGUgY2hlY2suIEFuZCBqdXN0IGJlY2F1c2UgeW91DQpyZXR1cm4gYSA0MDQgZG9lc24ndCBt ZWFuIHlvdSBjYW5ub3QgYWxzbyByZXR1cm4gYSBKU09OIHJlc3BvbnNlIGJvZHkNCndpdGggZW1w dHkgcmVzdWx0cy4NCiANCi1hbmR5DQogDQpPbiBUaHUsIEFwciAxNywgMjAxNCBhdCAxMjowMCBB TSwgTGlubGluIFpob3UgPHpob3VsaW5saW5AY25uaWMuY24+IHdyb3RlOg0KPiBEZWFyIGFsbCwN Cj4gSSBoYXZlIGEgcXVlc3Rpb24gYWJvdXQgdGhlIGVtcHR5IHNlYXJjaCBzdGF0dXMgY29kZS4N Cj4gV2hlbiBzZWFyY2hpbmcgZG9tYWluLCBuYW1lc2VydmVyIG9yIGVudGl0eSwgc2VydmVyIHJl dHVybnMgZW1wdHkgcmVzdWx0cy4NCj4gQ3VycmVudGx5LCB3ZSBoYW5kbGUgcXVlcnkgYW5kIHNl YXJjaCBpbiB0aGUgc2FtZSwgYm90aCByZXR1cm4gNDA0IGlmIHRoZXJlDQo+IGlzIG5vIGluZm9y bWFpdG9uIHRvIHJlc3BvbmQuIEJ1dCBtYXliZSB0aGUgZW1wdHkgc2VhcmNoIGluZm9ybWF0aW9u IGlzDQo+IHNvbWV0aGluZyB1c2VmdWwgdG8gY2xpZW50LCByZXNwb25kaW5nIDIwMCBhbmQgZW1w dHkgcmVzdWx0IHNldCBtYWtlcyBzZW5zZQ0KPiBhcyB3ZWxsLiBXaGljaCBodHRwIGNvZGUgaXMg cHJvcGVyLCAyMDAgb3IgNDA0Pw0KPg0KPiBSZWdhcmRzLA0KPiBfX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXw0KPiBMaW5saW4gWmhvdQ0KPg0KPiBfX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fXw0KPiB3ZWlyZHMgbWFpbGluZyBsaXN0DQo+IHdlaXJk c0BpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3dlaXJk cw0KPg0K ------=_001_NextPart658362631073_=---- Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable =0A
So my take is,
#1 Just return 404
#2 Return 404 with empty results
#3 Return 200 with empty r= esults

Both #1 and #2 are allowed in http = draft. Right?
=0A

Regards,
=0A
=
Linlin Zhou
=0A
 
Date: 2014-04-17 22:09
To: Linlin Zhou
CC: weirds
Subject: Re: [weirds] Empty search status code
For simple clients, a 404 is a simple check. And just be= cause you
=0A
return a 404 doesn't mean you cannot also return a = JSON response body
=0A
with empty results.
=0A
 =0A
-andy
=0A
 
=0A
On Thu, Apr 17, 2014 at = 12:00 AM, Linlin Zhou <zhoulinlin@cnnic.cn> wrote:
=0A
>= Dear all,
=0A
> I have a question about the empty search stat= us code.
=0A
> When searching domain, nameserver or entity, se= rver returns empty results.
=0A
> Currently, we handle query a= nd search in the same, both return 404 if there
=0A
> is no in= formaiton to respond. But maybe the empty search information is
=0A> something useful to client, responding 200 and empty result set ma= kes sense
=0A
> as well. Which http code is proper, 200 or 404= ?
=0A
>
=0A
> Regards,
=0A
> _________= _______________________
=0A
> Linlin Zhou
=0A
>=0A
> _______________________________________________
=0A> weirds mailing list
=0A
> weirds@ietf.org
=0A> https://www.ietf.org/mailman/listinfo/weirds
=0A
>
= =0A
=0A ------=_001_NextPart658362631073_=------ From nobody Thu Apr 17 18:48:51 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9612B1A000F for ; Thu, 17 Apr 2014 18:48:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.19 X-Spam-Level: X-Spam-Status: No, score=-1.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272] 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 ly9DkrmXsMNz for ; Thu, 17 Apr 2014 18:48:43 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id C12191A0062 for ; Thu, 17 Apr 2014 18:48:38 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn Received: from unknown127.0.0.1 (HELO user-think) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 18 Apr 2014 09:48:33 +0800 Date: Fri, 18 Apr 2014 09:48:36 +0800 From: "Linlin Zhou" To: simon.perreault , weirds References: <2014041713002928844263@cnnic.cn>, , <534FEAEA.8080909@viagenie.ca> X-Priority: 3 X-Has-Attach: no X-Mailer: Foxmail 7, 2, 5, 136[cn] Mime-Version: 1.0 Message-ID: <2014041809483637587127@cnnic.cn> Content-Type: multipart/alternative; boundary="----=_001_NextPart622386732605_=----" Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/RPhTG7zSFKxFA4dJb_KjqISIr34 Subject: Re: [weirds] Empty search status code 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, 18 Apr 2014 01:48:48 -0000 This is a multi-part message in MIME format. ------=_001_NextPart622386732605_=---- Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 UmVyZWFkIHRoZSBodHRwIGRyYWZ0LCBpbiBkcmFmdC1pZXRmLXdlaXJkcy11c2luZy1odHRwLTA4 IHNlY3Rpb24gNS4zOg0KSWYgYSBzZXJ2ZXIgd2lzaGVzIHRvIHJlc3BvbmQgdGhhdCBpdCBoYXMg bm8gaW5mb3JtYXRpb24gcmVnYXJkaW5nIHRoZSBxdWVyeSwgaXQgcmV0dXJucyBhIDQwNCByZXNw b25zZSBjb2RlLiBPcHRpb25hbGx5LCBpdCBNQVkgaW5jbHVkZSBhZGRpdGlvbmFsIGluZm9ybWF0 aW9uIHJlZ2FyZGluZyB0aGUgbmVnYXRpdmUgYW5zd2VyIGluIHRoZSBIVFRQIGVudGl0eSBib2R5 LkkgdGhpbmsgdGhpcyBwYXJhZ3JhcGggZ2l2ZXMgdGhlIGV4cGxhbmF0aW9uIHRoYXQgNDA0IGNv ZGUgd2l0aCBhZGRpdGlvbmFsIGluZm9ybWF0aW9uIGlzIGFsbG93ZWQuDQpSZWdhcmRzDQoNCg0K TGlubGluIFpob3UNCiANCkZyb206IFNpbW9uIFBlcnJlYXVsdA0KRGF0ZTogMjAxNC0wNC0xNyAy Mjo1Mw0KVG86IHdlaXJkcw0KU3ViamVjdDogUmU6IFt3ZWlyZHNdIEVtcHR5IHNlYXJjaCBzdGF0 dXMgY29kZQ0KTGUgMjAxNC0wNC0xNyAxMDowOSwgQW5kcmV3IE5ld3RvbiBhIMOpY3JpdCA6DQo+ IEZvciBzaW1wbGUgY2xpZW50cywgYSA0MDQgaXMgYSBzaW1wbGUgY2hlY2suIEFuZCBqdXN0IGJl Y2F1c2UgeW91DQo+IHJldHVybiBhIDQwNCBkb2Vzbid0IG1lYW4geW91IGNhbm5vdCBhbHNvIHJl dHVybiBhIEpTT04gcmVzcG9uc2UgYm9keQ0KPiB3aXRoIGVtcHR5IHJlc3VsdHMuDQogDQpXaGF0 ZXZlciB0aGUgb3V0Y29tZSBpcyAoSSBkb24ndCBjYXJlKSwgcGxlYXNlIHN0YXRlIGl0IGV4cGxp Y2l0bHkgaW4NCnRoZSBuZXh0IGRyYWZ0IHJldmlzaW9uLg0KIA0KVGhhbmtzLA0KU2ltb24NCi0t IA0KRFROIG1hZGUgZWFzeSwgbGVhbiwgYW5kIHNtYXJ0IC0tPiBodHRwOi8vcG9zdGVsbGF0aW9u LnZpYWdlbmllLmNhDQpOQVQ2NC9ETlM2NCBvcGVuLXNvdXJjZSAgICAgICAgLS0+IGh0dHA6Ly9l Y2R5c2lzLnZpYWdlbmllLmNhDQpTVFVOL1RVUk4gc2VydmVyICAgICAgICAgICAgICAgLS0+IGh0 dHA6Ly9udW1iLnZpYWdlbmllLmNhDQogDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXw0Kd2VpcmRzIG1haWxpbmcgbGlzdA0Kd2VpcmRzQGlldGYub3JnDQpo dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3dlaXJkcw0K ------=_001_NextPart622386732605_=---- Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable =0A
Reread the http draft,= in draft-ietf-weirds-using-http-08 section 5.3:
If a server wishes to respond that it h=
as no information regarding the query, it returns a 404 response code. Opt=
ionally, it MAY include additional information regarding the negative answ=
er in the HTTP entity body.
I think this=
 paragraph gives the explanation that 404 code with additional information=
 is allowed.

<=
/pre>
Regards
=0A
=
<= div>Linlin Zhou
=0A
 
Date: 2014-04-17&nbs= p;22:53
Subject: Re: [weirds] Empty search status code=
Le 2014-04-17 10:09, Andrew Newton a =C3=A9cri= t :
=0A
> For simple clients, a 404 is a simple check. And jus= t because you
=0A
> return a 404 doesn't mean you cannot also = return a JSON response body
=0A
> with empty results.
=0A=
 
=0A
Whatever the outcome is (I don't care), please st= ate it explicitly in
=0A
the next draft revision.
=0A
&n= bsp;
=0A
Thanks,
=0A
Simon
=0A
--
=0ADTN made easy, lean, and smart --> http://postellation.viagenie.ca=0A
NAT64/DNS64 open-source       = ; --> http://ecdysis.viagenie.ca
=0A
STUN/TURN server &nb= sp;            = ; --> http://numb.viagenie.ca
=0A
 
=0A
________= _______________________________________
=0A
weirds mailing list=0A
weirds@ietf.org
=0A
https://www.ietf.org/mailman/list= info/weirds
=0A
=0A ------=_001_NextPart622386732605_=------ From nobody Fri Apr 18 05:45: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 915621A01D4 for ; Fri, 18 Apr 2014 05:45:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.173 X-Spam-Level: X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, 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 hU6mtBmmzW2T for ; Fri, 18 Apr 2014 05:45:09 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id ECD951A011B for ; Fri, 18 Apr 2014 05:45:08 -0700 (PDT) Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:349d:fe5f:bc57:89]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 701D44021E; Fri, 18 Apr 2014 08:45:04 -0400 (EDT) Message-ID: <53511E50.7070904@viagenie.ca> Date: Fri, 18 Apr 2014 08:45:04 -0400 From: Simon Perreault User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Linlin Zhou , weirds References: <2014041713002928844263@cnnic.cn>, , <534FEAEA.8080909@viagenie.ca> <2014041809483637587127@cnnic.cn> In-Reply-To: <2014041809483637587127@cnnic.cn> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/wzBTrFbIIGlkfAQptkmEEDsElrI Subject: Re: [weirds] Empty search status code 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, 18 Apr 2014 12:45:13 -0000 Le 2014-04-17 21:48, Linlin Zhou a Ă©crit : > Reread the http draft, in draft-ietf-weirds-using-http-08 section 5.3: > > If a server wishes to respond that it has no information regarding the query, it returns a 404 response code. Optionally, it MAY include additional information regarding the negative answer in the HTTP entity body. > > I think this paragraph gives the explanation that 404 code with additional information is allowed. In my understanding, this text means the server should return 200, since an empty result set *is* information. But I'm not arguing that point, I don't care. The fact that we have a different understanding of the current text means that the current text is not sufficiently explicit. That's why I said that the next draft revision should state the outcome of this discussion explicitly. And I don't care what the outcome is. I just want the text to be clear. 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 nobody Fri Apr 18 06:58: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 96A5D1A0260 for ; Fri, 18 Apr 2014 06:58:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.172 X-Spam-Level: X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 iTat1c4mWCIY for ; Fri, 18 Apr 2014 06:58:38 -0700 (PDT) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 154F51A0177 for ; Fri, 18 Apr 2014 06:58:38 -0700 (PDT) Received: by smtp2.arin.net (Postfix, from userid 323) id 0D1A42136AE; Fri, 18 Apr 2014 09:58:34 -0400 (EDT) Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id 6B26F213693; Fri, 18 Apr 2014 09:58:33 -0400 (EDT) Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.342.3; Fri, 18 Apr 2014 09:58:33 -0400 Received: from CHAXCH02.corp.arin.net ([169.254.2.48]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0328.009; Fri, 18 Apr 2014 09:58:32 -0400 From: Andy Newton To: Simon Perreault Thread-Topic: [weirds] Empty search status code Thread-Index: AQHPWfoNHfN2N9XjeUuFcPPCT+IN55sWHFwAgAAMVQCAAHQRKIAA+mIAgAAUjIA= Date: Fri, 18 Apr 2014 13:58:31 +0000 Message-ID: <2997BB1D-8BC5-4FC0-825B-B83DCCBCD7CF@arin.net> References: <2014041713002928844263@cnnic.cn>, , <534FEAEA.8080909@viagenie.ca> <2014041809483637587127@cnnic.cn> <53511E50.7070904@viagenie.ca> In-Reply-To: <53511E50.7070904@viagenie.ca> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.30.37] Content-Type: text/plain; charset="Windows-1252" Content-ID: <4C27A896E8E4234FA9F853EBA2DE9D4A@corp.arin.net> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/Pnx8LHHvfWrRxuH6NyZr-0UTj-k Cc: "weirds@ietf.org" Subject: Re: [weirds] Empty search status code 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, 18 Apr 2014 13:58:42 -0000 On Apr 18, 2014, at 8:45 AM, Simon Perreault = wrote: > Le 2014-04-17 21:48, Linlin Zhou a =E9crit : >> Reread the http draft, in draft-ietf-weirds-using-http-08 section 5.3: >>=20 >> If a server wishes to respond that it has no information regarding the q= uery, it returns a 404 response code. Optionally, it MAY include additional= information regarding the negative answer in the HTTP entity body. >>=20 >> I think this paragraph gives the explanation that 404 code with addition= al information is allowed. >=20 > In my understanding, this text means the server should return 200, since > an empty result set *is* information. But I'm not arguing that point, I > don't care. The fact that we have a different understanding of the > current text means that the current text is not sufficiently explicit. > That's why I said that the next draft revision should state the outcome > of this discussion explicitly. And I don't care what the outcome is. I > just want the text to be clear. Point taken. Perhaps it should be =93answer 404 if there is no information = that answers the query.=94 However, I=92d like it to stay 404 because that is an easy path for clients= . -andy= From nobody Fri Apr 18 07:03:03 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A60CF1A022E for ; Fri, 18 Apr 2014 07:03:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.173 X-Spam-Level: X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, 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 piJ8OE1C6X1c for ; Fri, 18 Apr 2014 07:02:57 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 06D321A0161 for ; Fri, 18 Apr 2014 07:02:57 -0700 (PDT) Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:349d:fe5f:bc57:89]) by jazz.viagenie.ca (Postfix) with ESMTPSA id CC45E4021E; Fri, 18 Apr 2014 10:02:52 -0400 (EDT) Message-ID: <5351308C.4060201@viagenie.ca> Date: Fri, 18 Apr 2014 10:02:52 -0400 From: Simon Perreault User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Andy Newton References: <2014041713002928844263@cnnic.cn>, , <534FEAEA.8080909@viagenie.ca> <2014041809483637587127@cnnic.cn> <53511E50.7070904@viagenie.ca> <2997BB1D-8BC5-4FC0-825B-B83DCCBCD7CF@arin.net> In-Reply-To: <2997BB1D-8BC5-4FC0-825B-B83DCCBCD7CF@arin.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/Fjg7fK-ds5ux9aP4-Qk5t-YBqF4 Cc: "weirds@ietf.org" Subject: Re: [weirds] Empty search status code 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, 18 Apr 2014 14:03:01 -0000 Le 2014-04-18 09:58, Andy Newton a écrit : > > On Apr 18, 2014, at 8:45 AM, Simon Perreault wrote: > >> Le 2014-04-17 21:48, Linlin Zhou a écrit : >>> Reread the http draft, in draft-ietf-weirds-using-http-08 section 5.3: >>> >>> If a server wishes to respond that it has no information regarding the query, it returns a 404 response code. Optionally, it MAY include additional information regarding the negative answer in the HTTP entity body. >>> >>> I think this paragraph gives the explanation that 404 code with additional information is allowed. >> >> In my understanding, this text means the server should return 200, since >> an empty result set *is* information. But I'm not arguing that point, I >> don't care. The fact that we have a different understanding of the >> current text means that the current text is not sufficiently explicit. >> That's why I said that the next draft revision should state the outcome >> of this discussion explicitly. And I don't care what the outcome is. I >> just want the text to be clear. > > Point taken. Perhaps it should be “answer 404 if there is no information that answers the query.” Not explicit enough. As I said, in my understanding an empty result set *is* information that answers the query. Suggestion: "If a search query yields an empty result set, the response's status code MUST be XXX." Pick XXX however you like. > However, I’d like it to stay 404 because that is an easy path for clients. Fine with me. 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 nobody Fri Apr 18 07:45: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 D34751A0372 for ; Fri, 18 Apr 2014 07:45:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.171 X-Spam-Level: X-Spam-Status: No, score=-2.171 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272] 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 sfjgh7T8NcxI for ; Fri, 18 Apr 2014 07:45:33 -0700 (PDT) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id EC9681A030E for ; Fri, 18 Apr 2014 07:45:32 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id 157A01655D3; Fri, 18 Apr 2014 10:45:29 -0400 (EDT) Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp1.arin.net (Postfix) with ESMTP id 9FD281655D1; Fri, 18 Apr 2014 10:45:28 -0400 (EDT) Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.342.3; Fri, 18 Apr 2014 10:45:28 -0400 Received: from CHAXCH02.corp.arin.net ([169.254.2.48]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0328.009; Fri, 18 Apr 2014 10:45:27 -0400 From: Andy Newton To: Simon Perreault Thread-Topic: [weirds] Empty search status code Thread-Index: AQHPWfoNHfN2N9XjeUuFcPPCT+IN55sWHFwAgAAMVQCAAHQRKIAA+mIAgAAUjICAAAEwAIAAC+wA Date: Fri, 18 Apr 2014 14:45:27 +0000 Message-ID: <6BFE8FE5-4300-4C68-B121-54ED84B10BBD@arin.net> References: <2014041713002928844263@cnnic.cn>, , <534FEAEA.8080909@viagenie.ca> <2014041809483637587127@cnnic.cn> <53511E50.7070904@viagenie.ca> <2997BB1D-8BC5-4FC0-825B-B83DCCBCD7CF@arin.net> <5351308C.4060201@viagenie.ca> In-Reply-To: <5351308C.4060201@viagenie.ca> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.30.37] Content-Type: multipart/alternative; boundary="_000_6BFE8FE543004C68B12154ED84B10BBDarinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/tFr7AbtfC_LpENEV7Ia79DLTWOs Cc: "weirds@ietf.org" Subject: Re: [weirds] Empty search status code 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, 18 Apr 2014 14:45:38 -0000 --_000_6BFE8FE543004C68B12154ED84B10BBDarinnet_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable On Apr 18, 2014, at 10:02 AM, Simon Perreault > wrote: Suggestion: "If a search query yields an empty result set, the response's status code MUST be XXX." Works for me. Thanks. -andy --_000_6BFE8FE543004C68B12154ED84B10BBDarinnet_ Content-Type: text/html; charset="Windows-1252" Content-ID: <4E78D1974436D64987EA58513564EC7D@corp.arin.net> Content-Transfer-Encoding: quoted-printable
On Apr 18, 2014, at 10:02 AM, Simon Perreault <simon.perreault@viagenie.ca> wrote:

Suggestion: "If a search query yields an empty result set, the
response'= s status code MUST be XXX."

Works for me. Thanks.

-andy
--_000_6BFE8FE543004C68B12154ED84B10BBDarinnet_-- From nobody Fri Apr 18 09: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 457C91A045B for ; Fri, 18 Apr 2014 09:54:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.172 X-Spam-Level: X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 snnPIc2RjL1K for ; Fri, 18 Apr 2014 09:54:47 -0700 (PDT) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id D1B7E1A0455 for ; Fri, 18 Apr 2014 09:54:47 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id E6ED11655FC; Fri, 18 Apr 2014 12:54:43 -0400 (EDT) Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp1.arin.net (Postfix) with ESMTP id 615391655F8 for ; Fri, 18 Apr 2014 12:54:43 -0400 (EDT) Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.342.3; Fri, 18 Apr 2014 12:54:43 -0400 Received: from CHAXCH02.corp.arin.net ([169.254.2.48]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0347.000; Fri, 18 Apr 2014 12:54:42 -0400 From: Andy Newton To: "weirds@ietf.org" Thread-Topic: a couple of enhancements to json-response Thread-Index: AQHPWybVyrlVuBrW5kaVSY6vQhbezQ== Date: Fri, 18 Apr 2014 16:54:17 +0000 Message-ID: <26E9CAB4-7AC3-4400-B297-DC39EAE88802@arin.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.30.37] Content-Type: text/plain; charset="Windows-1252" Content-ID: <821111440A6E05458A678A20FF824A57@corp.arin.net> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/Z9EjEAAlVBu2N1r7S7yu6aebOIc Subject: [weirds] a couple of enhancements to json-response 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, 18 Apr 2014 16:54:52 -0000 During IETF 89, there were some private discussions regarding an RIR-scoped= extension to json-response. Since we seem to be a little stalled, perhaps = we should go ahead and put this is the next rev. given that this proposal a= dds no new object classes. Here=92s what we are thinking: 1. Add =93network=94 to domain for the representation of the IP network for= which the domain exists in the reverse DNS. Both ARIN and RIPE do this tod= ay: { "handle" : "XXX", "ldhName" : =93123.in-addr.arpa", ... "nameServers" : [ ... ], ... "entities" : [ ... ], ... =93network=94 : { ... } =20 } 2. Add =93domains=94 to IP network to represent the domains of the revers D= NS upon which a network maps into. This is the converse of the above, and d= one by some RIRs today: { "handle" : "XXX", ... "entities" : [ ... ], =85 =93domains=94 : [ =85. ] } 3. Add =93networks=94 and =93autnums=94 to entity, as some of the RIRs do = this today. Of course, this brings up this question: Should there be a =93domains=94 fo= r DNRs? In both cases, it is quite possible to get an entity that exceeds a size po= licy limit. And for that, see #4 4. Change the =93searchResultsTruncated=94 in Section 9 to a more general = =93resultsTruncated=94 applicable to both searches and lookups. Comments, questions? -andy= From nobody Sun Apr 20 09:20: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 785951A0025 for ; Sun, 20 Apr 2014 09:20:22 -0700 (PDT) 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 lR03wbPe49Vd for ; Sun, 20 Apr 2014 09:20:18 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id C21151A0015 for ; Sun, 20 Apr 2014 09:20:17 -0700 (PDT) Received: (qmail 12434 invoked from network); 20 Apr 2014 16:20:12 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 20 Apr 2014 16:20:12 -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=12951.5353f3bc.k1404; i=johnl@user.iecc.com; bh=h2xB/cy5iUAAroJoKI9yXCPWb5RZgqi7ZqqU1Ku51Lc=; b=iOKYVcjX7VLO8Dxsg6FE/abAIzCjmB3p7llAADeYrvaWYiuzlwEwsZuO2HxfrbSJldyzfVR9dEqGlNoqXyOxs84ufCP0j37Z4Dtn/VsEhLYRlQWLjO4x0gCIZroyPPJK7+BnJ1FlNT2zgtuSm1MtPwB5y1g9XswHXk5z0wipTymmeeawmSF2KBCwOcEZa8JrW7dbBrQB+0xo93RBx48L2B3Uyu2FGGzPNywFX47cISUNOkNlE3whV9CW4HdZcS0B 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=12951.5353f3bc.k1404; olt=johnl@user.iecc.com; bh=h2xB/cy5iUAAroJoKI9yXCPWb5RZgqi7ZqqU1Ku51Lc=; b=xa2MGZvZuCkTN0cxlwtu8ZI9JhNWpAGq1SxlzDHet6oJucyh5FFkOmxJISiRs3iFOYrP1aSFugAwONLAFbZ9HaNrF7HNrykObpiqeHui0ygE0Yd/QeNqNokxHgg330OgP2BpJsE5wC2wQzz7kAEfmiwoUDPDENVyNGvvidZln7sPiAFIPdmwSuVBnPXyIs8nLdU8NyIWbj8jfraqSlMclkYjrp9OAl4PuXP9gt+l12n/gbQuuop30iCVfNdOPecp Date: 20 Apr 2014 16:19:50 -0000 Message-ID: <20140420161950.76112.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: <26E9CAB4-7AC3-4400-B297-DC39EAE88802@arin.net> Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/or-dKIYCGKJfhTH1rOD8IjVIeXk Subject: Re: [weirds] a couple of enhancements to json-response 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, 20 Apr 2014 16:20:22 -0000 In article <26E9CAB4-7AC3-4400-B297-DC39EAE88802@arin.net> you write: >During IETF 89, there were some private discussions regarding an RIR-scoped extension to json-response. Since we seem >to be a little stalled, perhaps we should go ahead and put this is the next rev. given that this proposal adds no new >object classes. Keeping in mind that I'm not an RIR nor an RIR member so perhaps my opinion is not of the greatest relevance, it looks at worst harmless, so sure, go ahead. >Of course, this brings up this question: Should there be a “domains” for DNRs? The usual answer, not unless we have someone who plans to implement it. R's, John From nobody Sun Apr 20 09:21:48 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 595C21A0025 for ; Sun, 20 Apr 2014 09:21:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.043 X-Spam-Level: * X-Spam-Status: No, score=1.043 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 KGqjLgHmLYhf for ; Sun, 20 Apr 2014 09:21:42 -0700 (PDT) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 12F641A0011 for ; Sun, 20 Apr 2014 09:21:41 -0700 (PDT) Received: (qmail 12592 invoked from network); 20 Apr 2014 16:21:37 -0000 Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 20 Apr 2014 16:21:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=12967.5353f411.k1404; i=johnl@user.iecc.com; bh=fN1yXBWyMia7d3///TtegM4XM3/ZBJzSgfZILwfTrSo=; b=CCmlneMp0R4DHHnoYpzJSnPC9DV7kmVdiMxxAh+C8xsr8g/+oI1Q+AKgETm5E/2pKOcYEtdwfnEhC+0pS0EXtXSwa/IvnU3VgVVo0QumC+AOr5zU4KCRH5inNnM43WJPdntHsSfaJMCikm2WHky9KpIUonILJ1pnwEH3U9GIcX4z+l7MrdPADJHgXYIH6ox2ugdm1E/NPXOuP2DfVh2nxeizH0EyvggaUblhuBFqMFskYfsz5sNrZV0NOiHBQLPh 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=12967.5353f411.k1404; olt=johnl@user.iecc.com; bh=fN1yXBWyMia7d3///TtegM4XM3/ZBJzSgfZILwfTrSo=; b=DIt2AfiCx/4V0c0+m3Yd/IDVTo+bZU+/90SDTwaX++5DwVpJwM8DfGQwSkx2dn0L/NCKqF5X65h8QH55cXNL2rYMJ8ROV6GPky/JekqPl07Vqe0cf8RN+q+FKCy3iq4iDc8MR8Nry8BEvmmONNbm0M1B/8OeiL7ol3ss4QcIH1k0rQxsvtw/3nuyq98P8L0ftcrf8HWk0agZGXonv5OqfWxd0xQJbSPE8D62AVuQxsND6NxpngntacANckAw3kOV Date: 20 Apr 2014 16:21:14 -0000 Message-ID: <20140420162114.76134.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/6NkLrYr5KgZMYMKDi7_AqnbElv8 Subject: Re: [weirds] #12 (bootstrap): Bootstrap templates 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, 20 Apr 2014 16:21:46 -0000 >This ticket is (I believe) for settling the format of the deserialized IANA >registry content. Both the format and the contents. Who's holding the pen on this? I'd have thought it was Marc. If not, I can do it but not right away. R's, John From nobody Sun Apr 20 13:07:55 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4268F1A000C for ; Sun, 20 Apr 2014 13:07:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.173 X-Spam-Level: X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, 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 lv_we5UbHKaX for ; Sun, 20 Apr 2014 13:07:47 -0700 (PDT) Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 114E71A0016 for ; Sun, 20 Apr 2014 13:07:47 -0700 (PDT) Received: from h226.viagenie.ca (h226.viagenie.ca [206.123.31.226]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 24601403F8; Sun, 20 Apr 2014 16:07:40 -0400 (EDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Marc Blanchet In-Reply-To: <20140420162114.76134.qmail@joyce.lan> Date: Sun, 20 Apr 2014 16:07:38 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140420162114.76134.qmail@joyce.lan> To: John Levine X-Mailer: Apple Mail (2.1874) Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/8Z_owIpeJcL7-Sc2-O-nUu_CyuQ Cc: weirds@ietf.org Subject: Re: [weirds] #12 (bootstrap): Bootstrap templates 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, 20 Apr 2014 20:07:52 -0000 Le 2014-04-20 =E0 12:21, John Levine a =E9crit : >> This ticket is (I believe) for settling the format of the = deserialized IANA >> registry content. >=20 > Both the format and the contents. >=20 > Who's holding the pen on this? I'd have thought it was Marc. yes. I have a local modified copy of the bootstrap that I shall publish = soon. I had some variation of what Murray was suggesting. Marc. > If not, > I can do it but not right away. >=20 > R's, > John >=20 > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds From nobody Sun Apr 20 21:02: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 05F5C1A0194 for ; Sun, 20 Apr 2014 21:02:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.036 X-Spam-Level: *** X-Spam-Status: No, score=3.036 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.272, 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 Vr8-R_nP_wsN for ; Sun, 20 Apr 2014 21:02:08 -0700 (PDT) Received: from off-send02.tyo.jprs.co.jp (off-send02.tyo.jprs.co.jp [IPv6:2001:df0:8:17::20]) by ietfa.amsl.com (Postfix) with ESMTP id 282171A0096 for ; Sun, 20 Apr 2014 21:02:08 -0700 (PDT) Received: from off-sendsmg02.tyo.jprs.co.jp (off-sendsmg02.tyo.jprs.co.jp [172.18.8.33]) by off-send02.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id s3L41tPd010865 for ; Mon, 21 Apr 2014 13:02:01 +0900 X-AuditID: ac120821-b7f946d000000d60-f7-53549838f6ba Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg02.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id 93.E9.03424.83894535; Mon, 21 Apr 2014 13:02:00 +0900 (JST) Date: Mon, 21 Apr 2014 13:02:00 +0900 (JST) Message-Id: <20140421.130200.183055613.kambe@jprs.co.jp> To: weirds@ietf.org From: Naoki Kambe In-Reply-To: <6BFE8FE5-4300-4C68-B121-54ED84B10BBD@arin.net> References: <2997BB1D-8BC5-4FC0-825B-B83DCCBCD7CF@arin.net> <5351308C.4060201@viagenie.ca> <6BFE8FE5-4300-4C68-B121-54ED84B10BBD@arin.net> Organization: Japan Registry Services Co., Ltd. X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJIsWRmVeSWpSXmKPExsWyRoiFT9diRkiwwaM7Fhbzu46zODB6LFny kymAMYrLJiU1J7MstUjfLoEro6v5HnvBQ9aKOQv3sjYwnmfpYuTgkBAwkdh/iL2LkRPIFJO4 cG89WxcjF4eQwElGie2L28ASLALaEkvuP2IEsXkFLCS2XT/KDGKLCAhLLH75jgXEFhbQk+g9 uYMVxGYTUJFYdm8zE4jNKWAj8b7nOSPE0D5GieZvU9lBFvML6EtMbUqBWGwn0fT3Hdg9vAKC En93CIOEmQW0JHpmPGaHsOUltr+dwzyBkX8WQtUsJFWzkFQtYGRexSiTn5amW5yal1Kcm25g pFdSma+XVVBUrJcMojcxgkOOQ3EH46OdBocYBTgYlXh4I0xDgoVYE8uKK3MPMUpyMCmJ8s6b DBTiS8pPqcxILM6ILyrNSS0+xCjBwawkwiveCJTjTUmsrEotyodJSXOwKInzrn1zJlBIID2x JDU7NbUgtQgmK8PBoSTBu2caUKNgUWp6akVaZk4JQpqJgxNkOA/QcLXpIMOLCxJzizPTIfKn GCWlxHnvgjQLgCQySvPgel8xigO9IMz7HyTLA0wfcF2vgAYyAQ38eyYAZGBJIkJKqoHxxInQ f7/Or09Zrnx5obOYH2/YX1kOfpXs17NdLXM4u3fueSNjOeG4IvdX8T0TT07+uzCB5e7Vp6zR mxQNJp5NtL7Panz+W+rsibnTQ141Ol4oEdc5fichRpKLyfqsnFlCwzuGupU93IE1j1PX9Xev FY5W5TEPy1sYvncLy4Pj1+dc/NDy/91VJZbijERDLeai4kQA+w49JdwCAAA= Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/NLMJf7n2JdQYK7OJEu1l_4QgDtQ Subject: Re: [weirds] Empty search status code 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, 21 Apr 2014 04:02:13 -0000 From: Andy Newton Date: Fri, 18 Apr 2014 14:45:27 +0000 > On Apr 18, 2014, at 10:02 AM, Simon Perreault > > > wrote: > Suggestion: "If a search query yields an empty result set, the > response's status code MUST be XXX." I'm not quite sure about my understanding of this context. In a case of no result found, does this mean that returning an XXX status code other than 404 is capable? I'm afraid that this might be confusion for clients. They might not know which status code the server returns before asking. They might check both a header and a body of the empty result depending on the server response. Regards, Naoki Kambe From nobody Tue Apr 22 22:05: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 3489F1A0063 for ; Tue, 22 Apr 2014 22:05:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l-LZ9EqpoVPK for ; Tue, 22 Apr 2014 22:05:48 -0700 (PDT) Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id E502A1A0062 for ; Tue, 22 Apr 2014 22:05:47 -0700 (PDT) Received: by mail-we0-f169.google.com with SMTP id w62so348816wes.28 for ; Tue, 22 Apr 2014 22:05:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=juZcVR2NudJUsnMI/QtpRGG37fOKWrDL3cF8k5jAdp4=; b=c57wV5zX49ns2sPCr93H5UexcQkkjRKq8jhR7rjY5BCC+s7G7LTJ5J1EWj3xGa3CIm 9FX36w/GxaOKKAF8mnGeUVyj59lIQ9/ctGq9ipRxXm0CJPYv8BGB9aCxns6/4objOKkH ZFQs4GxnhqMxcVe2sxVCOJDyOhes9hJNLevh/dcIQ5/9ayABVn/E3ADJXgflEAAFKFb2 BZ7LW0d7SOKUP9WpeHgh+WoEOFGICZ7sp7CJBHlGLuJWrCJ5eKwP4rTFSyR5TpVAOano sswSsIskRq2wI0mNyyo0CKTQVWD3kIYHdVkCHTSsaDFi3BMeBaQWnnuld2nXoTUQWtNg FPtA== MIME-Version: 1.0 X-Received: by 10.194.78.4 with SMTP id x4mr487859wjw.58.1398229541844; Tue, 22 Apr 2014 22:05:41 -0700 (PDT) Received: by 10.180.210.194 with HTTP; Tue, 22 Apr 2014 22:05:41 -0700 (PDT) In-Reply-To: <20140423043458.20109.87374.idtracker@ietfa.amsl.com> References: <20140423043458.20109.87374.idtracker@ietfa.amsl.com> Date: Tue, 22 Apr 2014 22:05:41 -0700 Message-ID: From: "Murray S. Kucherawy" To: "weirds@ietf.org" Content-Type: multipart/alternative; boundary=047d7bfcf91427fbaa04f7aeaf96 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/eOXvrh0EjaUad9kKQ-hSO6k3oOU Subject: [weirds] Fwd: ID Tracker State Update Notice: 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, 23 Apr 2014 05:05:50 -0000 --047d7bfcf91427fbaa04f7aeaf96 Content-Type: text/plain; charset=UTF-8 FYI, this will be up for IETF-wide Last Call shortly. -MSK ---------- Forwarded message ---------- From: IETF Secretariat Date: Tue, Apr 22, 2014 at 9:34 PM Subject: ID Tracker State Update Notice: To: appsawg-chairs@tools.ietf.org, draft-ietf-appsawg-uri-get-off-my-lawn@tools.ietf.org, mt@mozilla.com IESG state changed to Last Call Requested from AD Evaluation ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-appsawg-uri-get-off-my-lawn/ --047d7bfcf91427fbaa04f7aeaf96 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
FYI, this will be up for IETF-wide Last Call shortly.=

-MSK

---------- F= orwarded message ----------
From: IETF Sec= retariat <ietf-secretariat-reply@ietf.org>
Date: Tue, Apr 22, 2014 at 9:34 PM
Subject: ID Tracker State Update Noti= ce: <draft-ietf-appsawg-uri-get-off-my-lawn-04.txt>
To: appsawg-chairs@tools.ietf.org, <= a href=3D"mailto:draft-ietf-appsawg-uri-get-off-my-lawn@tools.ietf.org">dra= ft-ietf-appsawg-uri-get-off-my-lawn@tools.ietf.org, mt@mozilla.com


IESG state changed to Last Call Requested from AD Evaluation
ID Tracker URL: http://datatracker.ietf.org/doc/= draft-ietf-appsawg-uri-get-off-my-lawn/


--047d7bfcf91427fbaa04f7aeaf96-- From nobody Wed Apr 23 04:57:06 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 E74DA1A0341 for ; Wed, 23 Apr 2014 04:57:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.273 X-Spam-Level: X-Spam-Status: No, score=-0.273 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RP_MATCHES_RCVD=-0.272] 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 lQb-Z6UkMdZV for ; Wed, 23 Apr 2014 04:57:02 -0700 (PDT) Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id 9A8C11A0339 for ; Wed, 23 Apr 2014 04:57:02 -0700 (PDT) Received: by smtp1.arin.net (Postfix, from userid 323) id EED871650D3; Wed, 23 Apr 2014 07:56:56 -0400 (EDT) Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp1.arin.net (Postfix) with ESMTP id 01912164E5B; Wed, 23 Apr 2014 07:56:54 -0400 (EDT) Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.342.3; Wed, 23 Apr 2014 07:56:53 -0400 Received: from CHAXCH02.corp.arin.net ([169.254.2.48]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0328.009; Wed, 23 Apr 2014 07:56:48 -0400 From: Andy Newton To: Naoki Kambe Thread-Topic: [weirds] Empty search status code Thread-Index: AQHPWfoNHfN2N9XjeUuFcPPCT+IN55sWHFwAgAAMVQCAAHQRKIAA+mIAgAAUjICAAAEwAIAAC+wAgAQDMgCAA6lQgA== Date: Wed, 23 Apr 2014 11:56:47 +0000 Message-ID: <62627173-6548-4F0F-BAD5-00C952A77918@arin.net> References: <2997BB1D-8BC5-4FC0-825B-B83DCCBCD7CF@arin.net> <5351308C.4060201@viagenie.ca> <6BFE8FE5-4300-4C68-B121-54ED84B10BBD@arin.net> <20140421.130200.183055613.kambe@jprs.co.jp> In-Reply-To: <20140421.130200.183055613.kambe@jprs.co.jp> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.149.252.96] Content-Type: text/plain; charset="us-ascii" Content-ID: <2F2ADBD3E8288541BB626360E25D5085@corp.arin.net> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/dNjLobSzjSh3yBdRX90JU9SbXRU Cc: "weirds@ietf.org" Subject: Re: [weirds] Empty search status code 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, 23 Apr 2014 11:57:04 -0000 On Apr 21, 2014, at 12:02 AM, Naoki Kambe wrote: > From: Andy Newton > Date: Fri, 18 Apr 2014 14:45:27 +0000 >> On Apr 18, 2014, at 10:02 AM, Simon Perreault >> > >> wrote: >> Suggestion: "If a search query yields an empty result set, the >> response's status code MUST be XXX." >=20 > I'm not quite sure about my understanding of this context. =20 >=20 > In a case of no result found, does this mean that returning an XXX > status code other than 404 is capable?=20 >=20 > I'm afraid that this might be confusion for clients. They might not > know which status code the server returns before asking. They might > check both a header and a body of the empty result depending on the > server response. A client should check for 404. If the client wants more in-depth informatio= n, it can look at the response body. -andy= From nobody Wed Apr 23 19:38:23 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A3601A02FF for ; Wed, 23 Apr 2014 19:38:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.235 X-Spam-Level: ** X-Spam-Status: No, score=2.235 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RP_MATCHES_RCVD=-0.272, 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 q2d00pXryRqI for ; Wed, 23 Apr 2014 19:38:18 -0700 (PDT) Received: from off-send02.tyo.jprs.co.jp (off-send02.tyo.jprs.co.jp [IPv6:2001:df0:8:17::20]) by ietfa.amsl.com (Postfix) with ESMTP id 67BE71A00EC for ; Wed, 23 Apr 2014 19:38:18 -0700 (PDT) Received: from off-sendsmg02.tyo.jprs.co.jp (off-sendsmg02.tyo.jprs.co.jp [172.18.8.33]) by off-send02.tyo.jprs.co.jp (8.13.8/8.13.8) with ESMTP id s3O2cBHZ031725 for ; Thu, 24 Apr 2014 11:38:11 +0900 X-AuditID: ac120821-b7f946d000000d60-68-535879130093 Received: from localhost (off-cpu04.tyo.jprs.co.jp [172.18.4.14]) by off-sendsmg02.tyo.jprs.co.jp (Symantec Messaging Gateway) with SMTP id A0.5B.03424.31978535; Thu, 24 Apr 2014 11:38:11 +0900 (JST) Date: Thu, 24 Apr 2014 11:36:14 +0900 (JST) Message-Id: <20140424.113614.45132291.kambe@jprs.co.jp> To: weirds@ietf.org From: Naoki Kambe In-Reply-To: <62627173-6548-4F0F-BAD5-00C952A77918@arin.net> References: <6BFE8FE5-4300-4C68-B121-54ED84B10BBD@arin.net> <20140421.130200.183055613.kambe@jprs.co.jp> <62627173-6548-4F0F-BAD5-00C952A77918@arin.net> Organization: Japan Registry Services Co., Ltd. X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFIsWRmVeSWpSXmKPExsWyRoiFT1e4MiLYYOo2DYv5XcdZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVMXflccaCIxwVPbsvsDUw3mTrYuTkkBAwkfgy9xwzhC0mceHe eqA4F4eQwElGiZt3GthBEiwC2hJTV+4Da+AVMJeYMuMgK4gtIiAssfjlOxYQW1hAT6L35A6w OJuAisSye5uZQGxOARuJg3cOM0MMncMocWTSN6AiDg5+AX2JqU0pEIvtJJr+gszhAJovKPF3 hzBImFlAS6JnxmN2CFteYvvbOcwTGPlnIVTNQlI1C0nVAkbmVYwy+WlpusWpeSnFuekGRnol lfl6WQVFxXrJIHoTIzjoOBR3MD7aaXCIUYCDUYmHt+xqeLAQa2JZcWXuIUZJDiYlUd6Wkohg Ib6k/JTKjMTijPii0pzU4kOMEhzMSiK8eR5AOd6UxMqq1KJ8mJQ0B4uSOO/aN2cChQTSE0tS s1NTC1KLYLIyHBxKErx3yoEaBYtS01Mr0jJzShDSTBycIMN5gIZXgdTwFhck5hZnpkPkTzFK SonzLgNJCIAkMkrz4HpfMYoDvSDMa1YBlOUBJhC4rldAA5mABhZMCAcZWJKIkJJqYNx9Jine ZfXiO9Gfen7u3Z5T9O4189G35VuL5Rg/1q4z2NBvfcC+3th9osasaW0dXLdvyX3ec3amo0hC rv1Ufl2+6zyz0/sWxO34/yCyjD/G9azpowCp5Bnfqwy+MOzR5t2vJnJYQH1Z0fJnqnHfVobY uOt8qpfcUSFXYpWastNq569yjwkCjUosxRmJhlrMRcWJAJxwt7rdAgAA Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/gAqyyjSL4iD-iFitjveI1NKB020 Subject: Re: [weirds] Empty search status code 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, 24 Apr 2014 02:38:20 -0000 From: Andy Newton Date: Wed, 23 Apr 2014 11:56:47 +0000 > On Apr 21, 2014, at 12:02 AM, Naoki Kambe wrote: > > From: Andy Newton > > Date: Fri, 18 Apr 2014 14:45:27 +0000 > >> On Apr 18, 2014, at 10:02 AM, Simon Perreault > >> > > >> wrote: > >> Suggestion: "If a search query yields an empty result set, the > >> response's status code MUST be XXX." > > > > I'm not quite sure about my understanding of this context. > > > > In a case of no result found, does this mean that returning an XXX > > status code other than 404 is capable? > > > > I'm afraid that this might be confusion for clients. They might not > > know which status code the server returns before asking. They might > > check both a header and a body of the empty result depending on the > > server response. > > A client should check for 404. If the client wants more in-depth > information, it can look at the response body. That makes sense to me. Thanks, Naoki Kambe From nobody Fri Apr 25 14:19: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 A8D2C1A0673 for ; Fri, 25 Apr 2014 14:19:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5vQurtT2i1WX for ; Fri, 25 Apr 2014 14:19:07 -0700 (PDT) Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id CBC631A03CE for ; Fri, 25 Apr 2014 14:19:06 -0700 (PDT) Received: by mail-wg0-f46.google.com with SMTP id b13so4184468wgh.29 for ; Fri, 25 Apr 2014 14:18:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=LbLMjv2O4ZPC5pHgEijsFkejxyJxVClbYz6Ls8aEAPs=; b=J9ohvURLbR0NnuMASIHw5OdLJs7/p2GoQ8XopwrBHmj1wjuCpBt6PdNKipL4rWt4FX kwR7vnoM5fMZvX4WvFFsqnj6JZNhPwLjfjzdSt+YYKod/TxsHZIjfzwejpHl7X4xjbx6 MwfLPAFgf/pGEa0h7kXoFQ18sEvKBH6F+rUy1BVVCeeoFguiTu46HDPP6FMbAKbRI/wc oXfRAhdxYWlA59fVf2G9MHM83AGWWqj9E8AvKDYy9AUiwmhvOIORnWCrFOpwJsmf6sjl 8fdkDvvnzVVJeVvOYyfk9Ia3k9/yL154RcO62zGdzKp0yoJVu64qtC2wbIUbNGzoEGPC mJcg== MIME-Version: 1.0 X-Received: by 10.194.190.42 with SMTP id gn10mr8608574wjc.9.1398460739907; Fri, 25 Apr 2014 14:18:59 -0700 (PDT) Received: by 10.180.210.194 with HTTP; Fri, 25 Apr 2014 14:18:59 -0700 (PDT) In-Reply-To: References: Date: Fri, 25 Apr 2014 14:18:59 -0700 Message-ID: From: "Murray S. Kucherawy" To: "weirds@ietf.org" Content-Type: multipart/alternative; boundary=047d7bb70882a2754d04f7e483ab Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/6uDNCPoI2P4a5qfb3mwbJmPXICo Subject: Re: [weirds] Remaining issues from London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Apr 2014 21:19:08 -0000 --047d7bb70882a2754d04f7e483ab Content-Type: text/plain; charset=UTF-8 On Mon, Apr 14, 2014 at 12:37 AM, Murray S. Kucherawy wrote: > > I'm going to open tracker items and email threads on this list for each of >> the items identified during the London meeting. For each of them, we need >> to come to a rough (or better) consensus resolution before we can proceed, >> so I encourage everyone to participate in as many of them as is >> practicable. We can create design teams as needed, assuming we can get >> people to volunteer for the ones we decide we need. >> >> If you don't see a tracker item and email thread start for an issue you'd >> like to see resolved, please contact the co-chairs or post to the list to >> get it on the record for discussion. >> > > As you can see, these are now open. I just noticed that several others > were opened during the London meeting by other participants. If there are > any duplicates, please mark them as such so the work doesn't get confused. > If any have been mis-assigned, please let us know and we can get them > adjusted. > > The full set of open items is here: > > http://trac.tools.ietf.org/wg/weirds/trac/report/1 > > Let's get some discussions going! > Hello there, It's been 11 days since this was done. There's been only a bit of activity since then, on only two of the 24 open tasks. Not very encouraging toward our hope of not having to meet in Toronto... Can we get at least the document authors/editors to respond to each of them, say by May 9th (Friday)? -MSK --047d7bb70882a2754d04f7e483ab Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Mon, Apr 14, 2014 at 12:37 AM, Murray S. Kucherawy <= superuser@gmail.com> wrote:
=
I'm going to open tracker items and email threads on this list for ea= ch of the items identified during the London meeting.=C2=A0 For each of the= m, we need to come to a rough (or better) consensus resolution before we ca= n proceed, so I encourage everyone to participate in as many of them as is = practicable.=C2=A0 We can create design teams as needed, assuming we can ge= t people to volunteer for the ones we decide we need.

If you don't see a tracker item and email thread start f= or an issue you'd like to see resolved, please contact the co-chairs or= post to the list to get it on the record for discussion.

As you can see, these are now = open.=C2=A0 I just noticed that several others were opened during the Londo= n meeting by other participants.=C2=A0 If there are any duplicates, please = mark them as such so the work doesn't get confused.=C2=A0 If any have b= een mis-assigned, please let us know and we can get them adjusted.

The full set of open items is here:

http://trac.tools.ietf= .org/wg/weirds/trac/report/1

Let's get some discu= ssions going!

Hello there,

It&#= 39;s been 11 days since this was done.=C2=A0 There's been only a bit of= activity since then, on only two of the 24 open tasks.=C2=A0 Not very enco= uraging toward our hope of not having to meet in Toronto...

Can we get at least the document authors/editors to respond to each of = them, say by May 9th (Friday)?

-MSK
= --047d7bb70882a2754d04f7e483ab-- From nobody Sat Apr 26 14:54: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 A68E41A06C2 for ; Sat, 26 Apr 2014 14:54:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rAKsDGeoLz5p for ; Sat, 26 Apr 2014 14:54:24 -0700 (PDT) Received: from exprod6og107.obsmtp.com (exprod6og107.obsmtp.com [64.18.1.208]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8611A03CE for ; Sat, 26 Apr 2014 14:54:22 -0700 (PDT) Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob107.postini.com ([64.18.5.12]) with SMTP ID DSNKU1wrB44EhbuCFWYG5QJH2Jd/AxJiHfxm@postini.com; Sat, 26 Apr 2014 14:54:17 PDT Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id s3QLsER9019463 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 26 Apr 2014 17:54:14 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Sat, 26 Apr 2014 17:54:05 -0400 From: "Hollenbeck, Scott" To: "Murray S. Kucherawy" Thread-Topic: [weirds] Remaining issues from London Thread-Index: AQHPYMv9ZldYJ7M5jEG4oDpPziFpc5skcodn Date: Sat, 26 Apr 2014 21:54:13 +0000 Message-ID: <14E45024-BC40-4DA4-B3C9-059725775C71@verisign.com> References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: multipart/alternative; boundary="_000_14E45024BC404DA4B3C9059725775C71verisigncom_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/zJdpAdE02IFwWCfHP4Sp-CtBS2g Cc: "weirds@ietf.org" Subject: Re: [weirds] Remaining issues from London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Apr 2014 21:54:26 -0000 --_000_14E45024BC404DA4B3C9059725775C71verisigncom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'm waiting for a bootstrap update before I start work on the smaller query= tasks. Scott On Apr 25, 2014, at 5:19 PM, "Murray S. Kucherawy" > wrote: On Mon, Apr 14, 2014 at 12:37 AM, Murray S. Kucherawy > wrote: I'm going to open tracker items and email threads on this list for each of = the items identified during the London meeting. For each of them, we need = to come to a rough (or better) consensus resolution before we can proceed, = so I encourage everyone to participate in as many of them as is practicable= . We can create design teams as needed, assuming we can get people to volu= nteer for the ones we decide we need. If you don't see a tracker item and email thread start for an issue you'd l= ike to see resolved, please contact the co-chairs or post to the list to ge= t it on the record for discussion. As you can see, these are now open. I just noticed that several others wer= e opened during the London meeting by other participants. If there are any= duplicates, please mark them as such so the work doesn't get confused. If= any have been mis-assigned, please let us know and we can get them adjuste= d. The full set of open items is here: http://trac.tools.ietf.org/wg/weirds/trac/report/1 Let's get some discussions going! Hello there, It's been 11 days since this was done. There's been only a bit of activity= since then, on only two of the 24 open tasks. Not very encouraging toward= our hope of not having to meet in Toronto... Can we get at least the document authors/editors to respond to each of them= , say by May 9th (Friday)? -MSK _______________________________________________ weirds mailing list weirds@ietf.org https://www.ietf.org/mailman/listinfo/weirds --_000_14E45024BC404DA4B3C9059725775C71verisigncom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
I'm waiting for a bootstrap update before I start work on the smaller = query tasks.

Scott

On Apr 25, 2014, at 5:19 PM, "Murray S. Kucherawy" <superuser@gmail.com> wrote:

On Mon, Apr 14, 2014 at 12:37 AM, Murray S. Kucherawy <superuser@gmai= l.com> wrote:

I'm going to open tracker items and email threads on this list for eac= h of the items identified during the London meeting.  For each of them= , we need to come to a rough (or better) consensus resolution before we can= proceed, so I encourage everyone to participate in as many of them as is practicable.  We can create desi= gn teams as needed, assuming we can get people to volunteer for the ones we= decide we need.

If you don't see a tracker item and email thread start for an issue yo= u'd like to see resolved, please contact the co-chairs or post to the list = to get it on the record for discussion.

As you can see, these are now open.  I just noticed that several = others were opened during the London meeting by other participants.  I= f there are any duplicates, please mark them as such so the work doesn't ge= t confused.  If any have been mis-assigned, please let us know and we can get them adjusted.

The full set of open items is here:

http://trac.tools.ietf.org/wg/weirds/trac/report/1

Let's get some discussions going!=

Hello there,

It's been 11 days since this was done.  There's been only a bit of act= ivity since then, on only two of the 24 open tasks.  Not very encourag= ing toward our hope of not having to meet in Toronto...

Can we get at least the document authors/editors to respond to each of them= , say by May 9th (Friday)?

-MSK
_______________________________________________
weirds mailing list
weirds@ietf.org
https://www.= ietf.org/mailman/listinfo/weirds
--_000_14E45024BC404DA4B3C9059725775C71verisigncom_-- From nobody Mon Apr 28 12:21: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 0740C1A6FA9 for ; Mon, 28 Apr 2014 12:21:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.55 X-Spam-Level: X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgZp14VORTcz for ; Mon, 28 Apr 2014 12:21:12 -0700 (PDT) Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 9AF9A1A6FA8 for ; Mon, 28 Apr 2014 12:21:12 -0700 (PDT) Received: by smtp2.arin.net (Postfix, from userid 323) id CE4A2213680; Mon, 28 Apr 2014 15:21:11 -0400 (EDT) Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id 60BEE21366D; Mon, 28 Apr 2014 15:21:11 -0400 (EDT) Received: from CHAXCH04.corp.arin.net (10.1.30.19) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.342.3; Mon, 28 Apr 2014 15:21:11 -0400 Received: from CHAXCH02.corp.arin.net ([169.254.2.7]) by CHAXCH04.corp.arin.net ([10.1.30.19]) with mapi id 14.02.0347.000; Mon, 28 Apr 2014 15:21:10 -0400 From: Andy Newton To: "Murray S. Kucherawy" Thread-Topic: [weirds] Remaining issues from London Thread-Index: AQHPV62QsmSvzZOLsEej+JkWjPMd5psQ/FqAgBIvS4CABJYSgA== Date: Mon, 28 Apr 2014 19:21:09 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.30.37] Content-Type: multipart/alternative; boundary="_000_DEC3D2BA67AD4B4E8AFE99148D82D450arinnet_" MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/n_M5Xhn-2Z89nF0Lr6wKRaea7OE Cc: "weirds@ietf.org" Subject: Re: [weirds] Remaining issues from London X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2014 19:21:15 -0000 --_000_DEC3D2BA67AD4B4E8AFE99148D82D450arinnet_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Apr 25, 2014, at 5:18 PM, Murray S. Kucherawy > wrote: It's been 11 days since this was done. There's been only a bit of activity= since then, on only two of the 24 open tasks. Not very encouraging toward= our hope of not having to meet in Toronto... Can we get at least the document authors/editors to respond to each of them= , say by May 9th (Friday)? Murray, Some of the issues require the people who raised the issues to respond. How= long do we give them? -andy --_000_DEC3D2BA67AD4B4E8AFE99148D82D450arinnet_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
On Apr 25, 2014, at 5:18 PM, Murray S. Kucherawy <superuser@gmail.com> wrote:

It's been 11 days since this was done.  There's been only a bit of activit= y since then, on only two of the 24 open tasks.  Not very encouraging = toward our hope of not having to meet in Toronto...

Can we get at least the document authors/editors to respond to each of them, s= ay by May 9th (Friday)?

Murray,

Some of the issues require the people who raised the issues to respond= . How long do we give them?

-andy
--_000_DEC3D2BA67AD4B4E8AFE99148D82D450arinnet_-- From nobody Wed Apr 30 15:23:23 2014 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D61A51A0955; Wed, 30 Apr 2014 15:23:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S3NOimbsHm-D; Wed, 30 Apr 2014 15:23:10 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A4D31A09BC; Wed, 30 Apr 2014 15:23:06 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.4.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140430222306.17013.83001.idtracker@ietfa.amsl.com> Date: Wed, 30 Apr 2014 15:23:06 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/a9KAXC_eJq_FPFVxurXOnuCbdrk Cc: weirds@ietf.org Subject: [weirds] I-D Action: draft-ietf-weirds-json-response-07.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: Wed, 30 Apr 2014 22:23:15 -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 : JSON Responses for the Registration Data Access Protocol (RDAP) Authors : Andrew Lee Newton Scott Hollenbeck Filename : draft-ietf-weirds-json-response-07.txt Pages : 83 Date : 2014-04-30 Abstract: This document describes JSON data structures representing registration information maintained by Regional Internet Registries (RIRs) and Domain Name Registries (DNRs). These data structures are used to form Registration Data Access Protocol (RDAP) query responses. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-weirds-json-response/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-weirds-json-response-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-weirds-json-response-07 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/