I've done some testing against a Unicode database tabl= e containing

=C2=A0 semain= e

=C2=A0 s=C3=A9maph= ore

=C2=A0 semblant<= /div>

=C2=A0 s=C3=A9minaire

And confirmed that:
Search se* =C2=A0\u73\u65\*
=C2=A0 =C2=A0semaine
=C2=A0 =C2=A0semblan= t
Search s=C3=A9* =C2=A0\u73\uE9\*
=C2=A0 =C2=A0s=C3=A9maphore
=C2= =A0 =C2=A0s=C3=A9minaire

However, this pattern is not the same for all languages. If a diacritical m= ark =C2=A0is not combined with the character into a single Unicode point (i= n NFC) as for =C3=A9 above, then the character combined with all diacritica= ls are matched. Here is an example from Hebrew.

Search *=D7=90 =C2=A0\u05d0\*

=D7=90=D7= =91 =C2=A0u'\u05d0\u05d1'

=D7=90=D6=B7=D7=91 =C2=A0u'= \u05d0\u05b7\u05d1'

=D7=90=D6=B8=D7=91 =C2=A0u'\u05d0\u05= b8\u05d1'

But a search that includes the diacr= itical only matches that one.

Search *=D7=90=D6=B7 =C2=A0\u05d0\u05b7\*

=D7=90=D6=B7=D7=91 =C2=A0u'\u05d0\u05b7\u05d1'

<= /div>

It might be worth noting these differences and dependencies on la= nguages in the=C2=A0json-response document.

Anothe= r confusing issue to be aware of is that for right-to-left languages, when = the user enters the search string "abc" followed by *, it may be = displayed as either cba* or *cba. While there is a Unicode Bidirectional (b= idi) algorithm, the real world fact is that there are plenty of differences= between environments. For example, in FireFox, entering abc* in the url ad= dress line appears as cba* but when the Google search page comes up, it app= ears as *cba in the Search box. Generally this is a local display only and = the Unicode is transmitted with the * at the end of the string, as shown in= the examples above. If it is not, then an RDAP search as currently defined= should fail.

-Ernie

On Wed, Aug 28, 2013 at 5:13 AM, Linlin Zhou <z= houlinlin@cnnic.cn> wrote:

Store the data in databases with the NFC normalization for= m and search for "abc*" or "ab=C3=A7*" also in NFC, I f= eel this is the most straightforward way for this issue.

Regards,
Linlin

> -----Original Message-----
> From: wei= rds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On Behalf Of
> John Levine

> Sent: Tuesday, August 27, 2013 5:34 AM
> To: weirds@ietf.o= rg
> Subject: Re: [weirds] Comments on draft-ietf-weirds-json-response-05 >

> >I believe most people doing an RDAP search for "se= *" would expect to
> >get the whole list. With NFC normalization, they will only get
> > =C2=A0 =C2=A0 semaine
> > =C2=A0 =C2=A0 semblant
>

> Unfortunately, this is a tarpit. =C2=A0While the French consider= e and =C2=A0to be
> approximately the same, the Swedes consider a, , and =C2=A0to be as di= fferent as a,

> b, and c.
>
> I think the least bad we can do is to say that searches are against NF= C strings,
> and if you want to find accented characters, you have to search for th= em.
>
> R's,
> John

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

--001a11c238e8813c8204e60b2427-- From edainow@afilias.info Tue Sep 10 11:33:24 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7591D11E811B for ; Tue, 10 Sep 2013 11:33:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.676 X-Spam-Level: X-Spam-Status: No, score=-1.676 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_35=0.6] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gqXxV3cKHhzl for ; Tue, 10 Sep 2013 11:33:18 -0700 (PDT) Received: from outbound.afilias.info (outbound.afilias.info [66.199.183.4]) by ietfa.amsl.com (Postfix) with ESMTP id 33DD221F9B58 for ; Tue, 10 Sep 2013 11:33:11 -0700 (PDT) Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.72) (envelope-from ) id 1VJSkQ-0001oI-3S for weirds@ietf.org; Tue, 10 Sep 2013 18:33:10 +0000 Received: from mail-la0-f52.google.com ([209.85.215.52]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1VJSkP-00005V-5i for weirds@ietf.org; Tue, 10 Sep 2013 18:33:10 +0000 Received: by mail-la0-f52.google.com with SMTP id ev20so6370716lab.25 for ; Tue, 10 Sep 2013 11:33:03 -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=Nu3kwSOlfkwW/0pedqHp7YpsRFYvEHLEzJ4EVKBffuQ=; b=OzJ/jotbTJQ0nuwJA8iLe1Y695G7STmHopJY3LYNQGr7JJV0pDk9R9hkDnzq/e11hX EK5BoTY8IUgAGl8myosDujT5xZ9hM7ihz4/BFnjGRXT2R4BAdM/gm+T3Kx4aNkvqj8N/ oqgGHLum5NQ8BIbaN8HF3KlHSzxETvQCHcRHfBlkAtMxoKwLoYrBxzCiHY9uYorm350j novneGm3fkL7+u6Uv0qhgyJUF+LyfX32PdGOoZbm/GROSDXw8FxB6Xs2kZYQCHk+ttOk YqsDxRzI1FFwhohwAdk5AJ0sZC5NvvxhBdiG3GD7a2Y7NI/US7CmOYYupOyYcneUSV67 w7og== X-Gm-Message-State: ALoCoQk4UrbYBA2ht4kS6id4Bk1qH7NAGjX81gykr1Xe6Zdz8bE11kRfQ3Z5vI4+MGZFEThRgufaCbULv0VpvDU3OfNSQ+mUG0oVsq5ONuY+/LgTHK/isVQAF33keE792Y20maMxdpet X-Received: by 10.112.51.166 with SMTP id l6mr22126716lbo.5.1378837983450; Tue, 10 Sep 2013 11:33:03 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.51.166 with SMTP id l6mr22126710lbo.5.1378837983358; Tue, 10 Sep 2013 11:33:03 -0700 (PDT) Received: by 10.112.3.7 with HTTP; Tue, 10 Sep 2013 11:33:03 -0700 (PDT) In-Reply-To: References: <521394CE.7060400@afilias.info> Date: Tue, 10 Sep 2013 14:33:03 -0400 Message-ID: From: Ernie Dainow To: Andy Newton Content-Type: multipart/alternative; boundary=001a113366bc337fc504e60bbc3d Cc: "weirds@ietf.org" Subject: Re: [weirds] Comments on draft-ietf-weirds-json-response-05 X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Sep 2013 18:33:24 -0000 --001a113366bc337fc504e60bbc3d Content-Type: text/plain; charset=ISO-8859-1 Generally when someone submits a search, they are trying to discover what names exist. After they get a list of results, they may then do an exact lookup on particular names to get more details. I don't think we can anticipate what details they may be interested in, so I don't think we need to return anything other than a simple list of names, as in "names" : [ "1.example.com", "2.example.com", ... ] This can be used for all search results, domains, nameservers and entities. In particular, since domain handles cannot be used for any kind of lookup, there does not seem to be much value in returning them. An argument can be made for removing handles from all RDAP objects, unless they can be used for lookups. The only handles in this category are entities. Domain, nameserver and ip handles seem superfluous. Or am I missing something useful that a client or end user might do with a handle? -Ernie On Tue, Aug 20, 2013 at 2:00 PM, Andy Newton wrote: > On 8/20/13 12:09 PM, "Ernie Dainow" wrote: > > >9. Responding To Searches > > > >The domains array returned from a search > > > >"domains" : > > [ > > { > > "handle" : "1-XXXX", > > "name" : "1.example.com", > > ... > > }, > > > >seems inconsistent with the request in draft-ietf-weirds-rdap-query-06 > >and with domain responses already defined. It should have "ldhName" or > >"unicodeName" (or both) instead of "name". > > This was a cut&paste error. Thanks. > > >Domains is a new array, not used elsewhere. But "nameservers" and > >"entities" arrays returned from search are already defined, as quite > >large structures. Does this mean the server can return any subset of > >information from these structures in a search response? This will result > >in a rather lengthy response for an entities search by name, since the > >name ("fn") is embedded inside the vcardArray. Some examples here would > >help. I think simple new arrays specific for "nameservers" and > >"entities" search results might be preferable. > > Would 'entitySearchResults', 'nameserverSearchResults', and > 'domainSearchResults' work better? > > -andy > > --001a113366bc337fc504e60bbc3d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Generally when someone submits a search, they are trying t= o discover what names exist. After they get a list of results, they may the= n do an exact lookup on particular names to get more details. I don't t= hink we can anticipate what details they may be interested in, so I don'= ;t think we need to return anything other than a simple list of names, as i= n

=A0 =A0 =A0"names" : [ "1.example.com", "2.example.com", ... ]<= /div>

This can be used for all search results, domains,=A0nam= eservers and entities.

In particular, since domain handles cannot be used for = any kind of lookup, there does not seem to be much value in returning them.= =A0

An argument can be made for removing handles f= rom all RDAP objects, unless they can be used for lookups. The only handles= in this category are entities. Domain, nameserver and ip=A0handles=A0seem = superfluous. Or am I missing something useful that a client or end user mig= ht do with a handle?

-Ernie

<= br>

On Tue, Aug 20, 2013 at 2:00 PM, Andy New= ton <andy@arin.net> wrote:

On 8/20/13 12:09 PM, "Ernie Dainow= " <edaino= w@afilias.info> wrote:

>9. =A0Responding To Searches
>
>The domains array returned from a search
>
>"domains" :
> =A0 =A0 =A0[
> =A0 =A0 =A0 =A0{
> =A0 =A0 =A0 =A0 =A0"handle" : "1-XXXX",
> =A0 =A0 =A0 =A0 =A0"name" : "1.example.com",
> =A0 =A0 =A0 =A0 =A0...
> =A0 =A0 =A0 =A0},
>
>seems inconsistent with the request in draft-ietf-weirds-rdap-query-06<= br> >and with domain responses already defined. It should have "ldhName= " or
>"unicodeName" (or both) instead of "name".

This was a cut&paste error. Thanks.

>Domains is a new array, not used elsewhere. But "nameservers"= and
>"entities" arrays returned from search are already defined, a= s quite
>large structures. Does this mean the server can return any subset of >information from these structures in a search response? This will resul= t
>in a rather lengthy response for an entities search by name, since the<= br> >name ("fn") is embedded inside the vcardArray. Some examples = here would
>help. I think simple new arrays specific for "nameservers" an= d
>"entities" search results might be preferable.

Would 'entitySearchResults', 'nameserverSearchResults'= ;, and
'domainSearchResults' work better?

-andy

--001a113366bc337fc504e60bbc3d-- From shollenbeck@verisign.com Fri Sep 13 04:36:03 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8CC911E80EF for ; Fri, 13 Sep 2013 04:36:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rRkQP-GB3qbh for ; Fri, 13 Sep 2013 04:35:57 -0700 (PDT) Received: from exprod6og124.obsmtp.com (exprod6og124.obsmtp.com [64.18.1.242]) by ietfa.amsl.com (Postfix) with ESMTP id 2576411E80F7 for ; Fri, 13 Sep 2013 04:35:56 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob124.postini.com ([64.18.5.12]) with SMTP ID DSNKUjL4m/OheeQpMzhCj7CcocCfl++Uwj7Y@postini.com; Fri, 13 Sep 2013 04:35:57 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 r8DBZtU0000979 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Sep 2013 07:35:55 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Fri, 13 Sep 2013 07:35:54 -0400 From: "Hollenbeck, Scott" To: "Murray S. Kucherawy" , "weirds@ietf.org" Thread-Topic: [weirds] Call for WEIRDS Agenda items for November Thread-Index: AQHOrY9Jod/i8uMSvkKEBzA9c2wnPZnDj4Ug Date: Fri, 13 Sep 2013 11:35:54 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F49261CC3@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.173.152.4] Content-Type: multipart/alternative; boundary="_000_831693C2CDA2E849A7D7A712B24E257F49261CC3BRN1WNEXMBX01vc_" MIME-Version: 1.0 Subject: Re: [weirds] Call for WEIRDS Agenda items for November X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Sep 2013 11:36:03 -0000 --_000_831693C2CDA2E849A7D7A712B24E257F49261CC3BRN1WNEXMBX01vc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Andy and I would like to have a few minutes to talk about Unicode, normaliz= ation, and searching. Scott From: weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On Behalf Of= Murray S. Kucherawy Sent: Monday, September 09, 2013 3:02 PM To: weirds@ietf.org Subject: [weirds] Call for WEIRDS Agenda items for November Colleagues, It's that time again. If you would like to make a presentation to WEIRDS w= hen we convene in November, or if you would like to request that someone co= ver a specific topic, please email weirds-chairs@tools.ietf.org with your topic and requested time. We need some= idea of how long the meeting will be so we can request an appropriate time= slot. As I said in Berlin, we will be more liberal with the amount of tim= e we request since we seem to consistently run out of time, but we still ne= ed some idea in advance of what the agenda will look like so we can be sure= major subject areas are covered. The deadline for us to request a time slot is only a few weeks away, so ple= ase don't leave your requests until the last minute. Thanks! -MSK, WEIRDS co-chair --_000_831693C2CDA2E849A7D7A712B24E257F49261CC3BRN1WNEXMBX01vc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Andy and I would like to have a few minute= s to talk about Unicode, normalization, and searching.

Scott

From: weirds-b= ounces@ietf.org [mailto:weirds-bounces@ietf.org] On Behalf Of Murray S. Kucherawy
Sent: Monday, September 09, 2013 3:02 PM
To: weirds@ietf.org
Subject: [weirds] Call for WEIRDS Agenda items for November

Colleagues,

It's that time again. If you would like to make a presentation to WEI= RDS when we convene in November, or if you would like to request that someo= ne cover a specific topic, please email weirds-chairs@tools.ietf.or= g with your topic and requested time. We need some idea of how lo= ng the meeting will be so we can request an appropriate time slot. As= I said in Berlin, we will be more liberal with the amount of time we request since we seem to consistently run out of tim= e, but we still need some idea in advance of what the agenda will look like= so we can be sure major subject areas are covered.

The deadline for us to request a time slot is only a few weeks away, so ple= ase don't leave your requests until the last minute.

Thanks!

-MSK, WEIRDS co-chair

--_000_831693C2CDA2E849A7D7A712B24E257F49261CC3BRN1WNEXMBX01vc_-- From edainow@afilias.info Fri Sep 13 11:31:08 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EAE721F9EB5 for ; Fri, 13 Sep 2013 11:31:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TmJfCgoq1n5C for ; Fri, 13 Sep 2013 11:30:57 -0700 (PDT) Received: from outbound.afilias.info (outbound.afilias.info [66.199.183.4]) by ietfa.amsl.com (Postfix) with ESMTP id E45A321F9D68 for ; Fri, 13 Sep 2013 11:30:56 -0700 (PDT) Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.72) (envelope-from ) id 1VKY8u-0005qS-3p for weirds@ietf.org; Fri, 13 Sep 2013 18:30:56 +0000 Received: from mail-ie0-f182.google.com ([209.85.223.182]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1VKY8u-0002ww-3a for weirds@ietf.org; Fri, 13 Sep 2013 18:30:56 +0000 Received: by mail-ie0-f182.google.com with SMTP id aq17so3402575iec.13 for ; Fri, 13 Sep 2013 11:30:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=UN4oYr33bWUKeeAAumS63oJiu5ItGIFoRx2TuiPzvZo=; b=RTqa/tGAUihVVYcGnSH+Gue81KawII/g60O5JHYFmdLVOYNstcqypyHPzk6dqDHOOy eH2v7UK/AsgkXHT4c+ljxs9cZfDz2NEdraWZcbFU84TJMxxTz3tLYeIPOIzm+sqopcZf se5vnJ6xMaD2rFyTXvBDNk7GZ8M381a4EIjtO3O+UVGcld27LK9054gU0M8NuDqacQ9V y22uhwW1sUtfQNIX+t6nuuHUqdi45LTFY1H5GxWCpZ/8DD254WoYEnixDGClRIAkt2Qg AuvKmDj1w4kS151icbM4gNrAWp9CjqWGIIgNMqF1JJ0YnStt2s6ADSrV+R2g8Zcajngf doRA== X-Gm-Message-State: ALoCoQnvregYydBsunigbu6Ja9TeMjoiQH12S8KSF47KMH4lOb795XNhhjtLAuvPEn7NifgUPKyUvSVLE2XCw6yHkYorQ8yHubu7VtKhLnWQdDJDSsXZA4bGmO1gnMJ8R6qlvPiq7bIu X-Received: by 10.50.45.34 with SMTP id j2mr1841719igm.13.1379097050713; Fri, 13 Sep 2013 11:30:50 -0700 (PDT) X-Received: by 10.50.45.34 with SMTP id j2mr1841715igm.13.1379097050644; Fri, 13 Sep 2013 11:30:50 -0700 (PDT) Received: from [10.10.68.31] (tor-gateway.afilias.info. [199.15.87.4]) by mx.google.com with ESMTPSA id oq3sm1058281igb.1.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Sep 2013 11:30:49 -0700 (PDT) Message-ID: <523359D4.1050901@afilias.info> Date: Fri, 13 Sep 2013 14:30:44 -0400 From: Ernie Dainow User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: "weirds@ietf.org" Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [weirds] search url query parameters X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Sep 2013 18:31:08 -0000 I don't think the following specification is correct domains/?ldhName= It should be domains?ldhName= See http://tools.ietf.org/html/rfc3986#section-3 -Ernie From shollenbeck@verisign.com Fri Sep 13 12:00:40 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E5D311E81B6 for ; Fri, 13 Sep 2013 12:00:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XjtPefyzwm9u for ; Fri, 13 Sep 2013 12:00:34 -0700 (PDT) Received: from exprod6og106.obsmtp.com (exprod6og106.obsmtp.com [64.18.1.191]) by ietfa.amsl.com (Postfix) with ESMTP id D471711E81A9 for ; Fri, 13 Sep 2013 11:59:49 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob106.postini.com ([64.18.5.12]) with SMTP ID DSNKUjNgpcbhoctQWaNBp1y5+UBZx2cFDr0e@postini.com; Fri, 13 Sep 2013 12:00:10 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 r8DIxjnt013453 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Sep 2013 14:59:45 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Fri, 13 Sep 2013 14:59:45 -0400 From: "Hollenbeck, Scott" To: Ernie Dainow , "weirds@ietf.org" Thread-Topic: [weirds] search url query parameters Thread-Index: AQHOsK9tIwjymIzE4EmGJ52z31VTJJnEBVqA Date: Fri, 13 Sep 2013 18:59:45 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F4926381A@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <523359D4.1050901@afilias.info> In-Reply-To: <523359D4.1050901@afilias.info> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.173.152.4] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] search url query parameters X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Sep 2013 19:00:41 -0000 > -----Original Message----- > From: weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On > Behalf Of Ernie Dainow > Sent: Friday, September 13, 2013 2:31 PM > To: weirds@ietf.org > Subject: [weirds] search url query parameters >=20 > I don't think the following specification is correct > domains/?ldhName=3D >=20 > It should be > domains?ldhName=3D True. Will fix. Scott From superuser@gmail.com Wed Sep 18 13:26:59 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05C6911E82CD for ; Wed, 18 Sep 2013 13:26:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.77 X-Spam-Level: X-Spam-Status: No, score=-1.77 tagged_above=-999 required=5 tests=[AWL=-0.660, BAYES_05=-1.11, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iz3+FcGIGmWZ for ; Wed, 18 Sep 2013 13:26:58 -0700 (PDT) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE8D11E8111 for ; Wed, 18 Sep 2013 13:26:57 -0700 (PDT) Received: by mail-wg0-f42.google.com with SMTP id m15so6208689wgh.5 for ; Wed, 18 Sep 2013 13:26:57 -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=zErHJ+96lW/13TyM5S0AyJ4alozZDFNpWd1U75SAHGw=; b=EHtvq0tJNccP5EF39xiBE+mBMbJE9o0RxvmaGk3XWzhqfTssHhUmsLc8tpxewhnOK7 1xNcydHuK6B7iAKFrNXbDjkQHbVzzqHTlbbzB2eIqy4m4vmZIRmooOS1Rq76DXaPGC+T 8FQ+suRdBKgvlQ2QQqhmJP0SFCHVY54T2mbrXMa2NMrxD0gxYJfTjlWKPsmC7GB9yxSr aCvRmeF5hl3AJiOllniVEVUXYiK26tKXxAG8NG9Ch/SHk4kImHr2uo7wdE0rTx5zgXaq Rdr9lErf6DRLFqmCZYhywKKnBNDPeLFdKaXt1zl+YM6vdnoV1H7hBWDp5rG5+5Y/Au0c cjOg== MIME-Version: 1.0 X-Received: by 10.194.93.72 with SMTP id cs8mr3171068wjb.49.1379536017296; Wed, 18 Sep 2013 13:26:57 -0700 (PDT) Received: by 10.180.106.169 with HTTP; Wed, 18 Sep 2013 13:26:57 -0700 (PDT) Date: Wed, 18 Sep 2013 13:26:57 -0700 Message-ID: From: "Murray S. Kucherawy" To: "weirds@ietf.org" Content-Type: multipart/alternative; boundary=047d7bb04d864412ef04e6ae42c6 Subject: [weirds] Upcoming milestones X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 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, 18 Sep 2013 20:26:59 -0000 --047d7bb04d864412ef04e6ae42c6 Content-Type: text/plain; charset=ISO-8859-1 Colleagues, Just a reminder that we have a group of milestones approaching. Specifically: The "object inventory" draft is due next month, and there's been no review or other activity on it since we accepted it into the WG. The "redirects", "rdap-query", and "json-response" documents are due in November (though not necessarily before the Vancouver meeting). If authors are stuck waiting for direction on a particular topic (search, for example), I suggest they come up with some kind of proposal based on the feedback so far, and post a new version or at least a diff for the WG to consider, which would then be fodder for discussion. Just trying to keep us moving! -MSK --047d7bb04d864412ef04e6ae42c6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Colleagues,

Just a reminder tha= t we have a group of milestones approaching.=A0 Specifically:

= The "object inventory" draft is due next month, and there's b= een no review or other activity on it since we accepted it into the WG.

The "redirects", "rdap-query", and "json= -response" documents are due in November (though not necessarily befor= e the Vancouver meeting).

If authors are stuck waiting for dir= ection on a particular topic (search, for example), I suggest they come up = with some kind of proposal based on the feedback so far, and post a new ver= sion or at least a diff for the WG to consider, which would then be fodder = for discussion.

Just trying to keep us moving!

-MSK

--047d7bb04d864412ef04e6ae42c6-- From carlosm3011@gmail.com Thu Sep 19 06:48:26 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45BCB21F92B9 for ; Thu, 19 Sep 2013 06:48:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mFNiTz3+PkQ9 for ; Thu, 19 Sep 2013 06:48:25 -0700 (PDT) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 248BD21F9248 for ; Thu, 19 Sep 2013 06:48:17 -0700 (PDT) Received: by mail-la0-f52.google.com with SMTP id ev20so6998792lab.11 for ; Thu, 19 Sep 2013 06:48:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=M2bvJJQXD1pLFDkBvlNtACQ5iLoIHPS1tZ5kQM5JX84=; b=Ez/aFGFA2lvkIGGf3TjGOKH954/Ot2B4SWQ8cWw/2dxVkXbdG3p2+XzNogwgybKgx3 qj2Ji8vzSHMsHXhjind2rVkutZ/3GRfe5R+QlxSIkSHPR8Rv9Nzvg7BFzUB9V2HnI3A5 YH2guIFXPbEAHhbdc+yOek9O8nlKHLC/xLu6c9BeV6XsKMGmt0EejihhgRiofwi4jTHX W0Ef+wckc/V/okKclG390O9rr9QvxD22UtVAPZqRGg5m9Rk/eUGzu7Mlm0GHrOqwhEcx 65s8PHo7v8IGPrNptIJ/KG3G3Pt8BHvQHluZwcvW1TuhX/3zFhtCuQS3pV/xaZ72LWJR 1h3w== MIME-Version: 1.0 X-Received: by 10.112.128.166 with SMTP id np6mr1885029lbb.7.1379598496940; Thu, 19 Sep 2013 06:48:16 -0700 (PDT) Received: by 10.112.210.136 with HTTP; Thu, 19 Sep 2013 06:48:16 -0700 (PDT) In-Reply-To: References: Date: Thu, 19 Sep 2013 10:48:16 -0300 Message-ID: From: Carlos Martinez-Cagnazzo To: "Murray S. Kucherawy" Content-Type: multipart/alternative; boundary=047d7b343ef257c72904e6bcce7c Cc: "weirds@ietf.org" Subject: Re: [weirds] Call for WEIRDS Agenda items for November X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: carlos@lacnic.net List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Sep 2013 13:48:26 -0000 --047d7b343ef257c72904e6bcce7c Content-Type: text/plain; charset=ISO-8859-1 Dear Chairs, I'd like to ask you to consider requesting webex/ meetecho for the weirds session, if that would be possible at all. cheers! ~Carlos On Mon, Sep 9, 2013 at 4:02 PM, Murray S. Kucherawy wrote: > Colleagues, > > It's that time again. If you would like to make a presentation to WEIRDS > when we convene in November, or if you would like to request that someone > cover a specific topic, please email weirds-chairs@tools.ietf.org with > your topic and requested time. We need some idea of how long the meeting > will be so we can request an appropriate time slot. As I said in Berlin, > we will be more liberal with the amount of time we request since we seem to > consistently run out of time, but we still need some idea in advance of > what the agenda will look like so we can be sure major subject areas are > covered. > > The deadline for us to request a time slot is only a few weeks away, so > please don't leave your requests until the last minute. > > Thanks! > > -MSK, WEIRDS co-chair > > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds > > -- -- ========================= Carlos M. Martinez-Cagnazzo h ttp://cagnazzo.me ========================= --047d7b343ef257c72904e6bcce7c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Dear Chairs,

I'd like to ask you to= consider requesting webex/ meetecho for the weirds session, if that would = be possible at all.

cheers!

~Carlos

On Mon, Sep 9, 2013 at 4:02 PM, Murray S. Kucherawy <superuser@gma= il.com> wrote:

Colleagues,

It&= #39;s that time again.=A0 If you would like to make a presentation to WEIRDS when we=20 convene in November, or if you would like to request that someone cover a specific topic, please email weirds-chairs@tools.ietf.org with your=20 topic and requested time.=A0 We need some idea of how long the meeting=20 will be so we can request an appropriate time slot.=A0 As I said in Berlin,= we will be more liberal with the amount of time we request since we seem t= o consistently run out of time, but we still need some idea in advance of w= hat the agenda will look like so we can be sure major subject areas are cov= ered.

The deadline for us to request a time slot is only a few weeks away, so= please don't leave your requests until the last minute.

Thanks!=

-MSK, WEIRDS co-chair

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

--
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D
Carlos M. Martinez-Cagnazzo
http://cagnazzo.me
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

--047d7b343ef257c72904e6bcce7c-- From zhoulinlin@cnnic.cn Mon Sep 23 03:12:23 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13C6121F9EA2 for ; Mon, 23 Sep 2013 03:12:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.788 X-Spam-Level: X-Spam-Status: No, score=-0.788 tagged_above=-999 required=5 tests=[AWL=-0.603, BAYES_40=-0.185] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UyiGc98Q1y5q for ; Mon, 23 Sep 2013 03:12:17 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 1692811E8195 for ; Mon, 23 Sep 2013 03:08:07 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn Received: from unknown127.0.0.1 (HELO lenovo95e6383c) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 23 Sep 2013 18:07:53 +0800 From: "Linlin Zhou" To: Date: Mon, 23 Sep 2013 18:07:54 +0800 Message-ID: <013701ceb844$c573ca70$505b5f50$@cn> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac64RMOUtqDO61zwRIGcIUQsdX5oXA== Content-Language: zh-cn Cc: =?gb2312?B?J1NlYW4gyfLLuCBTaGVuJw==?= Subject: [weirds] Object inventory update X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 10:12:24 -0000 All, The authors of object inventory draft are planning to review and update this document. When we discussed about the updates, we have two questions for the WG. #1 As we all know that this draft only talks about the DNR object inventory, does the WG feel necessary to include RIR part? #2 If we decide to include RIR object inventory, would any volunteer from RIR like to contribute text? Many thanks. Regards, Linlin From nkong@cnnic.cn Mon Sep 23 09:41:55 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B444321F8F24 for ; Mon, 23 Sep 2013 09:41:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-kblm66zBDF for ; Mon, 23 Sep 2013 09:41:51 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 37DAD21F8EB2 for ; Mon, 23 Sep 2013 09:41:51 -0700 (PDT) Received: from unknown127.0.0.1 (HELO [192.168.1.220]) (127.0.0.1) by 127.0.0.1 with SMTP; Tue, 24 Sep 2013 00:41:35 +0800 Content-Type: multipart/alternative; boundary="Apple-Mail=_AD04CF93-066A-45B5-8CAA-90A8E5ED9553" Mime-Version: 1.0 (Mac OS X Mail 6.6 $1510$) From: Ning Kong In-Reply-To: Date: Tue, 24 Sep 2013 00:41:35 +0800 Message-Id: <48DED10C-FF7C-429C-ACBC-1B8C2BF7DDB8@cnnic.cn> References: To: Murray S. Kucherawy X-Mailer: Apple Mail (2.1510) Cc: "weirds-chairs@tools.ietf.org Chairs" , weirds@ietf.org Subject: Re: [weirds] Call for WEIRDS Agenda items for November X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 16:41:55 -0000 --Apple-Mail=_AD04CF93-066A-45B5-8CAA-90A8E5ED9553 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Murray and all, If possible, I'd like to request 10 or 15 minutes to talk about the = backward compatibility of RDAP for Port 43 Whois. The reason why I want to raise this issue is, #1 There is a requirement from ICANN's RFP (Request for Proposal) for = an Open-Source Reference Implementation of a RESTful-based Domain Name = Registration Data Access Protocol. 2.4.4. The reference implementation should also include a PORT 43 WHOIS = server proxy. The proxy server should be able accept client queries that = conforms to RFC 3912, with the parameters as dictated by the gTLD = registry / registrar policies. The proxy will translate port 43 WHOIS = queries into RESTful queries, query the RESTful RDAP Service, and return = the plain text results via PORT 43 back to clients. #2 There are many users, especially the registrars, who are accustomed = to the Port 43 Whois. It seems that there may be a not-short transition = period from Port 43 Whois to RDAP in the near future. How to attract = more users to RDAP and make this transition period transparent and = steady? I think this is a question worthy of consideration by the WG. = IMHO, It maybe makes sense that RDAP can be compatible with the existing = Port 43 Whois, and Port 43 Whois can be updated as a RDAP client. If the WG is interested in this question, I think the following detailed = issues need to be discussed. #1 Query format of Port 43 Whois The common Port 43 Whois query commands are as follows, whois -h rdap.restfulwhois.org ip whois -h rdap.restfulwhois.org domain Do we need to define new query parameters for Port 43 Whois based on = RDAP query document? For example: whois -h rdap.restfulwhois.org -as 1223 whois -h rdap.restfulwhois.org -ns ns1.google.com whois -h rdap.restfulwhois.org -entity apnic #2 Response format of Port 43 Whois How to return RDAP responses in JSON format via Port 43 back to Whois = clients? Do we need to standardize the way to translate the JSON into = plain text format or define another new response format for Port 43 = Whois clients? #3 Authentication Http basic/digest authentication mechanism is not suitable for Port 43 = Whois. Should we consider to provide authentication functions to Port 43 = Whois clients? #4 Redirect Should we consider to provide Redirect functions to Port 43 Whois = clients? If so, how? #5 Search Should we consider to provide Search functions to Port 43 Whois clients? = If so, how? I'm not sure whether I go astray. If so, save me please ;-) Cheers, Ning > Colleagues, >=20 > It's that time again. If you would like to make a presentation to = WEIRDS when we convene in November, or if you would like to request that = someone cover a specific topic, please email = weirds-chairs@tools.ietf.org with your topic and requested time. We = need some idea of how long the meeting will be so we can request an = appropriate time slot. As I said in Berlin, we will be more liberal = with the amount of time we request since we seem to consistently run out = of time, but we still need some idea in advance of what the agenda will = look like so we can be sure major subject areas are covered. >=20 > The deadline for us to request a time slot is only a few weeks away, = so please don't leave your requests until the last minute. >=20 > Thanks! >=20 > -MSK, WEIRDS co-chair > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds --Apple-Mail=_AD04CF93-066A-45B5-8CAA-90A8E5ED9553 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

2.4.4. The reference implementation should also = include a PORT 43 WHOIS server proxy. The proxy server should be able = accept client queries that conforms to RFC 3912, with the parameters as = dictated by the gTLD registry / registrar policies. The proxy will = translate port 43 WHOIS queries into RESTful queries, query the RESTful = RDAP Service, and return the plain text results via PORT 43 back to = clients.

#2 There are many = users, especially the registrars, who are accustomed to the = Port 43 Whois. It seems that there may be a not-short transition = period from Port 43 Whois to RDAP in the near future. How to = attract more users to RDAP and make this transition period transparent = and steady? I think = this is a question worthy of consideration = by the WG. IMHO, It maybe makes sense that RDAP can be = compatible with the existing Port 43 Whois, and Port 43 Whois can be = updated as a RDAP client.

If the WG is = interested in this question, I think the following detailed issues need = to be discussed.

#1 Query format of = Port 43 Whois

The common Port 43 Whois query = commands are as follows,

whois -h rdap.restfulwhois.org = ip
whois -h rdap.restfulwhois.org = domain

Do we need to = define new query parameters for Port 43 Whois based on RDAP query = document?

For example:

whois -h rdap.restfulwhois.org -as = 1223
whois -h rdap.restfulwhois.org -ns ns1.google.com
who= is -h rdap.restfulwhois.org = -entity apnic

#2 = Response format of Port 43 Whois

How to return RDAP = responses in JSON format via Port 43 back to Whois clients? Do we = need to standardize the way to translate the JSON into plain text format = or define another new response format for Port 43 Whois = clients?

#3 Authentication

Http = basic/digest authentication mechanism is not suitable for Port 43 Whois. = Should we consider to provide authentication functions to Port 43 Whois = clients?

#4 Redirect

Should = we consider to provide Redirect functions to Port 43 Whois = clients? If so, how?

#5 Search

Should = we consider to provide Search functions to Port 43 Whois = clients? If so, how?

I'm not sure whether = I go astray. If so, save me please = ;-)

Cheers,

Ning

Colleagues,

It's that time again. If you = would like to make a presentation to WEIRDS when we=20 convene in November, or if you would like to request that someone cover = a specific topic, please email weirds-chairs@tools.ietf.org<= /a> with your=20 topic and requested time. We need some idea of how long the = meeting=20 will be so we can request an appropriate time slot. As I said in = Berlin, we will be more liberal with the amount of time we request since = we seem to consistently run out of time, but we still need some idea in = advance of what the agenda will look like so we can be sure major = subject areas are covered.

The deadline for us to request a time slot is only a few weeks away, = so please don't leave your requests until the last = minute.

Thanks!

-MSK, WEIRDS co-chair
_______________________________________________
weirds mailing = list
weirds@ietf.org
https://www.ietf.or= g/mailman/listinfo/weirds

= --Apple-Mail=_AD04CF93-066A-45B5-8CAA-90A8E5ED9553-- From superuser@gmail.com Mon Sep 23 12:08:45 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1843E21F9FD7 for ; Mon, 23 Sep 2013 12:08:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.493 X-Spam-Level: X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QzC-H5gbtOi6 for ; Mon, 23 Sep 2013 12:08:42 -0700 (PDT) Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id AA05D11E80F4 for ; Mon, 23 Sep 2013 12:08:33 -0700 (PDT) Received: by mail-we0-f175.google.com with SMTP id q59so3545008wes.34 for ; Mon, 23 Sep 2013 12:08:29 -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=er5bClBvwJNnpeokKzsDvTIQ4deJw9rNosLtj331Rvg=; b=T/jIU438tEmEmUb1oOMI++tJhLBR+5veS4O0OfNasVNwu0Ho2KFwghISan9Dtltha6 liWkOj4IHjvnZlzO8zqjNWKdrUSsqVFb9jQ0hZpftGPH5gvfkJjruiy4DTmpr58ecGdY nZvkv9rZh7SKijwtdi5fas8ufOoKg5Xny8XjfZNNaGnGARy1/dlEjo24i++HzYm3h2GZ Hs7zw7DxFXu1SYcVUsUTSoK1UJqHy4KBfGUC19qVptskcycubaI5MjumNHEUNtZNUuBK QG74BVGQPNZdhCnUt0GCLoc3Df6h9iLVBJ94OA5zP6iUJVIYnBF06n1PaU/Nw4UaFTGK kp7Q== MIME-Version: 1.0 X-Received: by 10.180.184.107 with SMTP id et11mr14843625wic.60.1379963309927; Mon, 23 Sep 2013 12:08:29 -0700 (PDT) Received: by 10.180.18.202 with HTTP; Mon, 23 Sep 2013 12:08:29 -0700 (PDT) Date: Mon, 23 Sep 2013 12:08:29 -0700 Message-ID: From: "Murray S. Kucherawy" To: "weirds@ietf.org" Content-Type: multipart/alternative; boundary=001a11c227eee4362004e711bed0 Subject: [weirds] IETF 88 session request submitted X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 19:08:45 -0000 --001a11c227eee4362004e711bed0 Content-Type: text/plain; charset=ISO-8859-1 Colleagues, I've submitted a request for a two-hour session; even with a relatively simple agenda, we do tend to need a lot more time than we usually request. I'll advise when it's been formally scheduled. We are still accepting agenda items. We're a month away from having to settle on that, so there's still time, but please don't wait until the last minute as we may not be able to accommodate your request if you do. -MSK, WEIRDS co-chair --001a11c227eee4362004e711bed0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Colleagues,

I've submitted a request = for a two-hour session; even with a relatively simple agenda, we do tend to= need a lot more time than we usually request.=A0 I'll advise when it&#= 39;s been formally scheduled.

We are still accepting agenda items.=A0 We're a month away from having to= =20 settle on that, so there's still time, but please don't wait until = the=20 last minute as we may not be able to accommodate your request if you do.

-MSK, WEIRDS co-chair

--001a11c227eee4362004e711bed0-- From superuser@gmail.com Mon Sep 23 13:27:16 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAF3921F9D30 for ; Mon, 23 Sep 2013 13:27:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.497 X-Spam-Level: X-Spam-Status: No, score=-2.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eotu5czCs8qr for ; Mon, 23 Sep 2013 13:27:16 -0700 (PDT) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id D259021F9D2E for ; Mon, 23 Sep 2013 13:27:15 -0700 (PDT) Received: by mail-wg0-f51.google.com with SMTP id c11so3542739wgh.18 for ; Mon, 23 Sep 2013 13:27:15 -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=KSdVmgjQSXXXt4WUK9aBXM5RbQUkLbe+M/RaRUWN3aQ=; b=XOTpJ3umsON0Z51im/19xxnfAW2Tyy+IJc8zKEqEkoFck8tpeBcbzOTVUdzh8M1Yek MPcP//HtRyS+V5pbKH+9lwMNLlDzV2LSVB84KJ00FKW8+tYvq1No6O6y64TBQwIc3Ot1 HcoMX4TUraxIf4uSk/3i62ckLpQT9or4vyCucxvR/dCBLyQddW+nfeI8to0eNOrkztQE qyIu14Z+JtkTGIkZ4PQiO3wHnfF1n/1ryv1ezqpYKGhHtyOP5Nn1vFGt2BZwvO8+hkU6 a8lHjkMKx3lQNQIfkBKgOs4sqkKioFFd6yzvi45r3sbeGwPcayv8xSl5L9Qmq+R3pYTu LiEw== MIME-Version: 1.0 X-Received: by 10.194.71.72 with SMTP id s8mr2942725wju.52.1379968035026; Mon, 23 Sep 2013 13:27:15 -0700 (PDT) Received: by 10.180.18.202 with HTTP; Mon, 23 Sep 2013 13:27:14 -0700 (PDT) In-Reply-To: <013701ceb844$c573ca70$505b5f50$@cn> References: <013701ceb844$c573ca70$505b5f50$@cn> Date: Mon, 23 Sep 2013 13:27:14 -0700 Message-ID: From: "Murray S. Kucherawy" To: Linlin Zhou Content-Type: multipart/alternative; boundary=047d7bd91a0487893504e712d8d3 Cc: "weirds@ietf.org" , =?GB2312?B?U2VhbiDJ8su4IFNoZW4=?= Subject: Re: [weirds] Object inventory update X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 20:27:16 -0000 --047d7bd91a0487893504e712d8d3 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Sep 23, 2013 at 3:07 AM, Linlin Zhou wrote: > #1 As we all know that this draft only talks about the DNR object > inventory, > does the WG feel necessary to include RIR part? > #2 If we decide to include RIR object inventory, would any volunteer from > RIR like to contribute text? > > > It's my understanding that at least the "person" object has to accommodate the needs of both sides of the equation, so it seems like the RIR input should be included. Unfortunately, I'm not an RIR so I don't have a specific contribution here. -MSK, participatin' --047d7bd91a0487893504e712d8d3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, Sep 23, 2013 at 3:07 AM, Linlin Zhou <zhoulinli= n@cnnic.cn> wrote:

#1 As we all know that this draft only talks= about the DNR object inventory,
does the WG feel necessary to include RIR part?
#2 If we decide to include RIR object inventory, would any volunteer from RIR like to contribute text?

It's my understanding that at = least the "person" object has to accommodate the needs of both si= des of the equation, so it seems like the RIR input should be included.=A0 = Unfortunately, I'm not an RIR so I don't have a specific contributi= on here.

-MSK, participatin'

--047d7bd91a0487893504e712d8d3-- From johnl@iecc.com Mon Sep 23 17:45:17 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97E5A21F9CF3 for ; Mon, 23 Sep 2013 17:45:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.607 X-Spam-Level: X-Spam-Status: No, score=-102.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z6cLzodC34Mw for ; Mon, 23 Sep 2013 17:45:12 -0700 (PDT) Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 3F0B521F9CE9 for ; Mon, 23 Sep 2013 17:45:11 -0700 (PDT) Received: (qmail 21803 invoked from network); 24 Sep 2013 00:45:09 -0000 Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 24 Sep 2013 00:45:09 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5240e094.xn--30v786c.k1309; i=johnl@user.iecc.com; bh=lPLoOvRmzRhAt5pa8WqoHOr/Wme/wQ1LLuiTWUCcESc=; b=aEKe6TPwNH2rrKkSgcXSO+em7SAPP4ss9TUcY0cWLP1Xw/SAkaBUsnzAK6uJ0RZwLErlaELtb75yQ4Xw4+ZTZ75DYZhGTlrlUNMYjWKKDGHTAIdvV5Z0YrhaXhiepgKMMnYHsUdyGleL/EbsZWHmegNfUuVcK6Y+KWTBCLJNQOdsIwm0B6rgxaGJeC9Ntm34Z9OUSKULgKQIP8q6JZDLVBJbvBNa+YdV7BzAMd7C5PywhTeIIMKbZpY31jCpgERM 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=5240e094.xn--30v786c.k1309; olt=johnl@user.iecc.com; bh=lPLoOvRmzRhAt5pa8WqoHOr/Wme/wQ1LLuiTWUCcESc=; b=J47nd+sEeRvEufVX8OSZ5c9wvumTpztMF2BTpnsuLewE0y3izkL51nGWnfRfuQLOVpODDyjH6gVaBpuIAyxtSpRd4pLe4ixY9k+bPlDJb8Cbq5WW6E2E5Vb/xrdzyvP9TrJWHulPxet7SYvx0j0gh9N/eY05XSf+X15uxZA6NE7uDe3WpFJQkKtU8TwOv2EPLByE3cEWpJ+8usUYg7Lhu7XsvwFUrrvGnGIllksr8bVeYTWCp3FA3wPlPMBqt2Bc Date: 24 Sep 2013 00:44:46 -0000 Message-ID: <20130924004446.2059.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: <48DED10C-FF7C-429C-ACBC-1B8C2BF7DDB8@cnnic.cn> Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Subject: Re: [weirds] Call for WEIRDS Agenda items for November X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Sep 2013 00:45:18 -0000 >If the WG is interested in this question, I think the following detailed issues need to be discussed. It's worth talking about, if only to be sure we understand the differences between what a WEIRDS port 43 proxy will provide, and what the various ICANN gTLD contrcats say, and to decide whether we care. The details of WHOIS in the different contracts are somewhat incompatible, so either ICANN should agree that the differences don't matter, or else you're going to have to add a whole bunch of nitpicky backward compatibility options, for which (if I were you) I'd ask for an amended contract to cover the extra development effort. R's, John From zhoulinlin@cnnic.cn Mon Sep 23 18:21:55 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D282821F9C72 for ; Mon, 23 Sep 2013 18:21:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.569 X-Spam-Level: X-Spam-Status: No, score=-0.569 tagged_above=-999 required=5 tests=[AWL=-0.421, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21gG6r1EzaE1 for ; Mon, 23 Sep 2013 18:21:48 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 6BF1821F9634 for ; Mon, 23 Sep 2013 18:21:43 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn Received: from unknown127.0.0.1 (HELO lenovo95e6383c) (127.0.0.1) by 127.0.0.1 with SMTP; Tue, 24 Sep 2013 09:21:36 +0800 From: "Linlin Zhou" To: "'Murray S. Kucherawy'" References: <013701ceb844$c573ca70$505b5f50$@cn> In-Reply-To: Date: Tue, 24 Sep 2013 09:21:35 +0800 Message-ID: <016f01ceb8c4$6ad9ea10$408dbe30$@cn> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0170_01CEB907.78FD2A10" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac64m1cJj1ImPCd9SXmCA5TDGB2cgwAJciSQ Content-Language: zh-cn Cc: weirds@ietf.org, =?gb2312?B?J1NlYW4gyfLLuCBTaGVuJw==?= Subject: Re: [weirds] Object inventory update X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Sep 2013 01:21:55 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0170_01CEB907.78FD2A10 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Thanks Murray. =20 If any RIR person could contribute or provide the existing RIR entity objects, that would be appreciated. =20 Regards, Linlin =20 From: Murray S. Kucherawy [mailto:superuser@gmail.com]=20 Sent: Tuesday, September 24, 2013 4:27 AM To: Linlin Zhou Cc: weirds@ietf.org; Sean =C9=F2=CB=B8 Shen Subject: Re: [weirds] Object inventory update =20 On Mon, Sep 23, 2013 at 3:07 AM, Linlin Zhou = wrote: #1 As we all know that this draft only talks about the DNR object = inventory, does the WG feel necessary to include RIR part? #2 If we decide to include RIR object inventory, would any volunteer = from RIR like to contribute text? =20 It's my understanding that at least the "person" object has to = accommodate the needs of both sides of the equation, so it seems like the RIR input should be included. Unfortunately, I'm not an RIR so I don't have a specific contribution here. -MSK, participatin' =20 ------=_NextPart_000_0170_01CEB907.78FD2A10 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Thanks = Murray.

If any RIR = person could contribute or provide the existing RIR entity objects, that = would be appreciated.

Regards,

Linlin=

From:= Murray S. = Kucherawy [mailto:superuser@gmail.com]
Sent: Tuesday, = September 24, 2013 4:27 AM
To: Linlin Zhou
Cc: = weirds@ietf.org; Sean =C9=F2=CB=B8 = Shen
Subject: Re: [weirds] Object inventory = update

On Mon, Sep 23, 2013 at 3:07 AM, Linlin Zhou <zhoulinlin@cnnic.cn> = wrote:

#1 As we all know that = this draft only talks about the DNR object inventory,
does the WG = feel necessary to include RIR part?
#2 If we decide to include RIR = object inventory, would any volunteer from
RIR like to contribute = text?

It's my understanding = that at least the "person" object has to accommodate the needs = of both sides of the equation, so it seems like the RIR input should be = included. Unfortunately, I'm not an RIR so I don't have a specific = contribution here.

-MSK, = participatin'

<= /html> ------=_NextPart_000_0170_01CEB907.78FD2A10-- From nkong@cnnic.cn Mon Sep 23 19:45:50 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8509321F9C00 for ; Mon, 23 Sep 2013 19:45:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qh3hibEKUc1d for ; Mon, 23 Sep 2013 19:45:45 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 8B3E521F9B21 for ; Mon, 23 Sep 2013 19:45:40 -0700 (PDT) Received: from unknown127.0.0.1 (HELO [192.168.1.102]) (127.0.0.1) by 127.0.0.1 with SMTP; Tue, 24 Sep 2013 10:45:17 +0800 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 6.6 $1510$) From: Ning Kong In-Reply-To: <20130924004446.2059.qmail@joyce.lan> Date: Tue, 24 Sep 2013 10:45:13 +0800 Content-Transfer-Encoding: quoted-printable Message-Id: <59D5E798-5BE6-4E65-933E-BD91F18FC3C4@cnnic.cn> References: <20130924004446.2059.qmail@joyce.lan> To: "John Levine" X-Mailer: Apple Mail (2.1510) Cc: weirds@ietf.org Subject: Re: [weirds] Call for WEIRDS Agenda items for November X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "WHOIS-based Extensible Internet Registration Data Service $WEIRDS$" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Sep 2013 02:45:50 -0000 Hi John, Thanks for your feedback. >> If the WG is interested in this question, I think the following = detailed issues need to be discussed. >=20 > It's worth talking about, if only to be sure we understand the > differences between what a WEIRDS port 43 proxy will provide, and what > the various ICANN gTLD contrcats say, and to decide whether we care. >=20 > The details of WHOIS in the different contracts are somewhat > incompatible, so either ICANN should agree that the differences don't > matter, Even if ICANN don't care about the differences among current WHOIS = implementations, if either ICANN or the WG think it's necessary to = standardize a PORT 43 WHOIS server proxy in RDAP, I suggest we should = have a slot to discuss this issue. > or else you're going to have to add a whole bunch of nitpicky > backward compatibility options, for which (if I were you) I'd ask for > an amended contract to cover the extra development effort. You should tell us earlier ;-) Cheers, Ning= From eshryane@ripe.net Fri Sep 27 06:50:12 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E71321F9F7F for ; Fri, 27 Sep 2013 06:50:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.185 X-Spam-Level: X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oKnqrixH0+PM for ; Fri, 27 Sep 2013 06:50:06 -0700 (PDT) Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 20BED11E8130 for ; Fri, 27 Sep 2013 06:50:04 -0700 (PDT) Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VPYQi-00075A-TG for weirds@ietf.org; Fri, 27 Sep 2013 15:50:03 +0200 Received: from s258-sslvpn-1.ripe.net ([193.0.20.231] helo=vpn-141.ripe.net) by dodo.ripe.net with esmtps (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from ) id 1VPYQi-0000pL-QI for weirds@ietf.org; Fri, 27 Sep 2013 15:50:00 +0200 From: Edward Shryane Content-Type: multipart/signed; boundary="Apple-Mail=_3D627611-91BA-4C7B-B4CC-8966C469604A"; protocol="application/pgp-signature"; micalg=pgp-sha256 Date: Fri, 27 Sep 2013 15:49:59 +0200 Message-Id: To: weirds@ietf.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20130927 clean X-RIPE-Spam-Level: ----- X-RIPE-Spam-Report: Spam Total Points: -5.3 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-RIPE-Signature: 3845d4b495fe518e26952f144fb12e409aff97038f8aa628f9dee70a41c072bc Subject: Re: [weirds] Object inventory update X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 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, 27 Sep 2013 13:50:12 -0000 --Apple-Mail=_3D627611-91BA-4C7B-B4CC-8966C469604A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi all, I'm a Software Developer in the Database Department in the RIPE NCC, we = are interested in contributing to the object inventory update. There are many RPSL object types, for both the Internet Number Registry = and the Routing Registry operated by the RIPE NCC, that are not = currently available via RDAP. Should a new path segment be added to allow for querying for all of = these objects, or will any additions be classified as entities? Should a new path segment be added to query routing objects = specifically? How would differences in these object types between RIRs be addressed? Regards, Ed --Apple-Mail=_3D627611-91BA-4C7B-B4CC-8966C469604A Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iF4EAREIAAYFAlJFjQcACgkQVt3x5YAnQzBicgD/We3/XTG67+rNMN93HuIActQ7 CXf8AXE1b2p1NlOdbQ0A/AzYMwmhUySO9JGxAcbx0CgyhdPPwI22yFv3zeVlyVKg =F1qG -----END PGP SIGNATURE----- --Apple-Mail=_3D627611-91BA-4C7B-B4CC-8966C469604A-- From zhoulinlin@cnnic.cn Sun Sep 29 00:41:19 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B667A21F9ECA for ; Sun, 29 Sep 2013 00:41:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.389 X-Spam-Level: X-Spam-Status: No, score=-0.389 tagged_above=-999 required=5 tests=[AWL=-0.390, BAYES_50=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WudKaeVen4a5 for ; Sun, 29 Sep 2013 00:41:04 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id B928E21F9EC4 for ; Sun, 29 Sep 2013 00:40:49 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn Received: from unknown127.0.0.1 (HELO lenovo95e6383c) (127.0.0.1) by 127.0.0.1 with SMTP; Sun, 29 Sep 2013 15:40:39 +0800 From: "Linlin Zhou" To: "'Edward Shryane'" , References: In-Reply-To: Date: Sun, 29 Sep 2013 15:40:40 +0800 Message-ID: <006e01cebce7$3228b940$967a2bc0$@cn> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac67iH7xtrWo1ey/SpaTtDhMFiy4JwBXGMjQ Content-Language: zh-cn Subject: Re: [weirds] Object inventory update X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 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, 29 Sep 2013 07:41:20 -0000 Hi Edward, > Hi all, > > I'm a Software Developer in the Database Department in the RIPE NCC, we are > interested in contributing to the object inventory update. > Thank you for your interest in this object inventory draft. We really need the help from RIRs. > There are many RPSL object types, for both the Internet Number Registry and > the Routing Registry operated by the RIPE NCC, that are not currently available > via RDAP. > > Should a new path segment be added to allow for querying for all of these > objects, or will any additions be classified as entities? > > Should a new path segment be added to query routing objects specifically? > > How would differences in these object types between RIRs be addressed? The object inventory draft mainly reflects the existing objects used in the Whois response. I think maybe we could talk about the RPSL objects in a new section or in Appendix. For your questions whether we need a new path segment, I think we need more opinions from WG. Regards, Linlin From denis@ripe.net Sun Sep 29 08:35:00 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 808C621F8E2D for ; Sun, 29 Sep 2013 08:35:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.185 X-Spam-Level: X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ithoDm-O85H8 for ; Sun, 29 Sep 2013 08:34:55 -0700 (PDT) Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 28AA721F866E for ; Sun, 29 Sep 2013 08:34:55 -0700 (PDT) Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VQJ1H-0007OU-GP; Sun, 29 Sep 2013 17:34:54 +0200 Received: from s258-sslvpn-1.ripe.net ([193.0.20.231] helo=Deniss-MacBook-Pro.local) by ayeaye.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1VQJ1H-0006sq-Ck; Sun, 29 Sep 2013 17:34:51 +0200 Message-ID: <52484899.6070706@ripe.net> Date: Sun, 29 Sep 2013 17:34:49 +0200 From: Denis Walker Organization: RIPE NCC User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Linlin Zhou References: <006e01cebce7$3228b940$967a2bc0$@cn> In-Reply-To: <006e01cebce7$3228b940$967a2bc0$@cn> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20130929 clean X-RIPE-Spam-Level: ----- X-RIPE-Spam-Report: Spam Total Points: -5.3 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-RIPE-Signature: 58f9516073e303fae3c21805d1b2e01c9144f782f932bbd92ab516f354aa925f Cc: weirds@ietf.org Subject: Re: [weirds] Object inventory update X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 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, 29 Sep 2013 15:35:00 -0000 Hi Linlin Ed is on vacation this week but I would like to clarify some of what you said below. On 29/09/2013 09:40, Linlin Zhou wrote: > Hi Edward, > >> Hi all, >> >> I'm a Software Developer in the Database Department in the RIPE NCC, we > are >> interested in contributing to the object inventory update. >> > > Thank you for your interest in this object inventory draft. We really need > the help from RIRs. > >> There are many RPSL object types, for both the Internet Number Registry > and >> the Routing Registry operated by the RIPE NCC, that are not currently > available >> via RDAP. >> >> Should a new path segment be added to allow for querying for all of these >> objects, or will any additions be classified as entities? >> >> Should a new path segment be added to query routing objects specifically? >> >> How would differences in these object types between RIRs be addressed? > > The object inventory draft mainly reflects the existing objects used in the > Whois response. I think maybe we could talk about the RPSL objects in a new > section or in Appendix. Perhaps we need to be clearer with use of terms here. The RIPE Database operates as an Internet Number Registry and a Routing Registry. They are physically and logically contained within the one database. All the existing objects in the RIPE Database are in RPSL format for both these registries. So when 'we' think of a 'whois response' it includes objects from both registries. That is address space, ASNs, routes, all the various set object types and all the secondary objects like organisation, person, role and maintainers. These are all in RPSL format. As APNIC and AFRINIC use the same RPSL structure as RIPE these objects are more or less the same. But they are quite different to ARIN and LACNIC in format, even though the content may be the same. Also not all RIRs operate a Routing Registry and many other organisations that are not RIRs and not Domain Name Registries do operate Routing Registries. Is it the goal of RDAP to be able to query all of these registries for all this information? Regards Denis Walker Business Analyst RIPE NCC Database Team > For your questions whether we need a new path segment, I think we need more > opinions from WG. > > Regards, > Linlin > > > _______________________________________________ > weirds mailing list > weirds@ietf.org > https://www.ietf.org/mailman/listinfo/weirds > From johnl@iecc.com Sun Sep 29 09:49:50 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A983511E811A for ; Sun, 29 Sep 2013 09:49:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.606 X-Spam-Level: X-Spam-Status: No, score=-102.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PZkeiznBbh7o for ; Sun, 29 Sep 2013 09:49:46 -0700 (PDT) Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 4192311E80E7 for ; Sun, 29 Sep 2013 09:49:45 -0700 (PDT) Received: (qmail 44628 invoked from network); 29 Sep 2013 16:49:44 -0000 Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 29 Sep 2013 16:49:44 -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=52485a28.xn--3zv.k1309; i=johnl@user.iecc.com; bh=vVhTz76qKiZ5/RSC6JJrF6Lq5jWdrDvYRlRnsIhXk5c=; b=zOHk2TGhHLNPeZ7JKDSAnwsDNdQJ03J0hZGwtLjrG2hm/Ts5rnmtk3njHAnIkHO5o8aC7LIVdWNhqkB0R6qte/pD7OFwJpEICDut1qFp9szSHTzLt8I5///0lww4Mep/tbozwH+AA2gZ2YbceOiUA/4dXX2ZJgEnCU7nlFL0wQw5VHiaV1RrYGl4BfgdHdIqqtgfDjaM5+ewTCPaUdcxfIC8eImhjsp+e5eK6ipynT9uKy8TH2cY3BJcUDoyFZ6K 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=52485a28.xn--3zv.k1309; olt=johnl@user.iecc.com; bh=vVhTz76qKiZ5/RSC6JJrF6Lq5jWdrDvYRlRnsIhXk5c=; b=X4KW/7MhkJ0H8RE73CLlYyiG+YgcNx8+EdjQ8tmFSUHcfQfg6GAEm7JDo/PPxO1Zlt5div5cDBYVHYJffWT6IU50sQhunNwiY2JLyhptbnmG2Mh6I4JMyRXpwIce9KXhep4GEfSTAGvhtr/kqlMkWmWvFn8WEpeN0s79CaHiyfQlBblzwrNDTDJKB9KfSwELK4L2nKAcbhd913xxgUyN/Kcl26zywS4dJTmHS12sRoUkuOvNp9FORTIeLNdi4J/+ Date: 29 Sep 2013 16:49:21 -0000 Message-ID: <20130929164921.45188.qmail@joyce.lan> From: "John Levine" To: weirds@ietf.org In-Reply-To: <52484899.6070706@ripe.net> Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit Subject: Re: [weirds] Object inventory update X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 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, 29 Sep 2013 16:49:50 -0000 >Is it the goal of RDAP to be able to query all of these registries for >all this information? To the extent possible, yes definitely. Keep in mind that doesn't mean that all the RIRs have to provide the same data or answer the same set of queries. It does mean that for the data they do provide, the query and response formats are the same. If some RIRs respond to queries with the JSON equivalent of "I don't know" for the stuff they don't handle, that's OK. R's, John From zhoulinlin@cnnic.cn Sun Sep 29 23:44:19 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4846A21F97C7 for ; Sun, 29 Sep 2013 23:44:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.404 X-Spam-Level: X-Spam-Status: No, score=-0.404 tagged_above=-999 required=5 tests=[AWL=-0.220, BAYES_40=-0.185, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TRo4wWPrxwnK for ; Sun, 29 Sep 2013 23:44:14 -0700 (PDT) Received: from cnnic.cn (smtp.cnnic.cn [218.241.118.7]) by ietfa.amsl.com (Postfix) with SMTP id 49BA721F8948 for ; Sun, 29 Sep 2013 23:44:12 -0700 (PDT) X-EYOUMAIL-SMTPAUTH: zhoulinlin@cnnic.cn Received: from unknown127.0.0.1 (HELO lenovo95e6383c) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 30 Sep 2013 14:44:01 +0800 From: "Linlin Zhou" To: "'Murray S. Kucherawy'" , References: In-Reply-To: Date: Mon, 30 Sep 2013 14:51:53 +0800 Message-ID: <00b701cebda9$8c4025e0$a4c071a0$@cn> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B8_01CEBDEC.9A6365E0" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac6tj0iV9q+7WbQdTBWYbKRDef8MMwQAFe6Q Content-Language: zh-cn Subject: Re: [weirds] Call for WEIRDS Agenda items for November X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 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, 30 Sep 2013 06:44:19 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_00B8_01CEBDEC.9A6365E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear all, I'd like to ask for a 10 minutes slot to talk about object inventory. First, show some updates about RIR object inventory. Second, discuss about the extension possibility of Whois query and response. Maybe I'll send a detailed agenda later. Regards, Linlin From: weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On Behalf Of Murray S. Kucherawy Sent: Tuesday, September 10, 2013 3:02 AM To: weirds@ietf.org Subject: [weirds] Call for WEIRDS Agenda items for November Colleagues, It's that time again. If you would like to make a presentation to WEIRDS when we convene in November, or if you would like to request that someone cover a specific topic, please email weirds-chairs@tools.ietf.org with your topic and requested time. We need some idea of how long the meeting will be so we can request an appropriate time slot. As I said in Berlin, we will be more liberal with the amount of time we request since we seem to consistently run out of time, but we still need some idea in advance of what the agenda will look like so we can be sure major subject areas are covered. The deadline for us to request a time slot is only a few weeks away, so please don't leave your requests until the last minute. Thanks! -MSK, WEIRDS co-chair ------=_NextPart_000_00B8_01CEBDEC.9A6365E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear = all,

I’d = like to ask for a 10 minutes slot to talk about object inventory. = First, show some updates about RIR object inventory. Second, = discuss about the extension possibility of Whois query and response. = Maybe I’ll send a detailed agenda later.

Regards,

Linlin=

From:= = weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On Behalf Of = Murray S. Kucherawy
Sent: Tuesday, September 10, 2013 3:02 = AM
To: weirds@ietf.org
Subject: [weirds] Call for = WEIRDS Agenda items for November

Colleagues,

It's that time again. If you would = like to make a presentation to WEIRDS when we convene in November, or if = you would like to request that someone cover a specific topic, please = email weirds-chairs@tools.ietf.org= with your topic and requested time. We need some idea of how = long the meeting will be so we can request an appropriate time = slot. As I said in Berlin, we will be more liberal with the amount = of time we request since we seem to consistently run out of time, but we = still need some idea in advance of what the agenda will look like so we = can be sure major subject areas are covered.

The deadline for us = to request a time slot is only a few weeks away, so please don't leave = your requests until the last = minute.

Thanks!

-MSK, WEIRDS = co-chair

------=_NextPart_000_00B8_01CEBDEC.9A6365E0-- From shollenbeck@verisign.com Mon Sep 30 06:58:12 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 844FD21F9C0D for ; Mon, 30 Sep 2013 06:58:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUQQ1SscopYO for ; Mon, 30 Sep 2013 06:58:06 -0700 (PDT) Received: from exprod6og120.obsmtp.com (exprod6og120.obsmtp.com [64.18.1.236]) by ietfa.amsl.com (Postfix) with ESMTP id 3F59F21F9C6C for ; Mon, 30 Sep 2013 06:57:42 -0700 (PDT) Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob120.postini.com ([64.18.5.12]) with SMTP ID DSNKUkmDVeWtLg0Pz79lxAQ4PbHOEAgg4qH9@postini.com; Mon, 30 Sep 2013 06:58:03 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 r8UDvcIp004021 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 30 Sep 2013 09:57:38 -0400 Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Mon, 30 Sep 2013 09:57:38 -0400 From: "Hollenbeck, Scott" To: Ernie Dainow , "weirds@ietf.org" Thread-Topic: [weirds] Comments on draft-ietf-weirds-rdap-query-06 Thread-Index: AQHOnb18Dd4hjmUJ/ESsix6yDNVWqpnejk2w Date: Mon, 30 Sep 2013 13:57:37 +0000 Message-ID: <831693C2CDA2E849A7D7A712B24E257F49287943@BRN1WNEXMBX01.vcorp.ad.vrsn.com> References: <52139101.6090408@afilias.info> In-Reply-To: <52139101.6090408@afilias.info> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.173.152.4] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [weirds] Comments on draft-ietf-weirds-rdap-query-06 X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 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, 30 Sep 2013 13:58:12 -0000 > -----Original Message----- > From: weirds-bounces@ietf.org [mailto:weirds-bounces@ietf.org] On > Behalf Of Ernie Dainow > Sent: Tuesday, August 20, 2013 11:54 AM > To: weirds@ietf.org > Subject: [weirds] Comments on draft-ietf-weirds-rdap-query-06 >=20 > 3.1.2. where XXX is an asplain autonomous system number [RFC5396]. > There were several suggestions on the previous draft about improved > wording for "asplain". The most consistent change would be to use the > wording in 3.1, "an AS Plain autonomous system number". >=20 > 3.2.1. Domain Search > Domain search requires a qualifier, ldhName or unicodeName. So the > client has to figure out what type of name is being searched. This is > inconsistent with domain lookup, where the server is expected to > distinguish between ldh and unicode names, and there is no work for the > client. >=20 > 3.2.3. Entity Search > Entity lookup is by handle, but search is by name. This seems somewhat > inconsistent, but practical, since search by name is generally more > useful. For more completeness, perhaps there should also be a search by > handle. It is supported by some existing whois servers. See for > example, > whois -h whois.pir.org contact 35975136-% I'm making changes to rdap-query to address each of these issues. Scott From superuser@gmail.com Mon Sep 30 10:17:35 2013 Return-Path: X-Original-To: weirds@ietfa.amsl.com Delivered-To: weirds@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA7421F91F2 for ; Mon, 30 Sep 2013 10:17:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.51 X-Spam-Level: X-Spam-Status: No, score=-2.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6YQW6MD7cRO for ; Mon, 30 Sep 2013 10:17:34 -0700 (PDT) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) by ietfa.amsl.com (Postfix) with ESMTP id DB56321F9CED for ; Mon, 30 Sep 2013 10:17:27 -0700 (PDT) Received: by mail-wi0-f180.google.com with SMTP id hj3so4256373wib.1 for ; Mon, 30 Sep 2013 10:17:25 -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=cQhd+jPGNcEjR3PBluRjbA6ZuduEpeEGQbnvExlO4NM=; b=IOv8f4dJC+N1vUrOfKkjFwYVfygHMW7TYBArcjMwNH7NFk0Obp+86VbG/ObkJFTqbK kBda7nca+ILsPmHctoLj1f2WgJQQps9vwERdgghQ60NZdFT7ph6UuLW7zSfo2D0cR6dx O3ibGonICRu0RsywSagF08st0/pX0rOk7jtCOcZXvcKoMVNBIswMqCGKDCSBugvocoGu SkbxJB6yKsclXFqjWbAOtuYYpGYFXU+8G0wzWSJhQS2Wt8oIb1uO/Pyaw1ZREvexvr1m A6n17QcqOYrHVKYwtsHl+q/45sq/Wmh4gtKTCl8RGivAmVkdIizTwlY89bJH7Vak8kZs Z/Xw== MIME-Version: 1.0 X-Received: by 10.180.189.9 with SMTP id ge9mr14754730wic.52.1380561445690; Mon, 30 Sep 2013 10:17:25 -0700 (PDT) Received: by 10.180.18.202 with HTTP; Mon, 30 Sep 2013 10:17:25 -0700 (PDT) Date: Mon, 30 Sep 2013 10:17:25 -0700 Message-ID: From: "Murray S. Kucherawy" To: "weirds@ietf.org" Content-Type: multipart/alternative; boundary=001a11c343028fa03b04e79d0271 Subject: [weirds] Reminder: Document cutoff three weeks away X-BeenThere: weirds@ietf.org X-Mailman-Version: 2.1.12 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, 30 Sep 2013 17:17:35 -0000 --001a11c343028fa03b04e79d0271 Content-Type: text/plain; charset=ISO-8859-1 Just a reminder to authors that the final date to submit new or updated drafts to the tracker before the pre-meeting cutoff is October 21, which is three weeks from now. Any document that is to be on the Vancouver agenda needs to be submitted prior to then. -MSK --001a11c343028fa03b04e79d0271 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Just a reminder to authors that the final date to sub= mit new or updated drafts to the tracker before the pre-meeting cutoff is O= ctober 21, which is three weeks from now.=A0 Any document that is to be on = the Vancouver agenda needs to be submitted prior to then.

-MSK

--001a11c343028fa03b04e79d0271--