IETF Logo Mail Archive

Re: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 01 May 2012 18:44 UTC

Return-Path: <shollenbeck@verisign.com>
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 49F3C21E814D for <weirds@ietfa.amsl.com>; Tue, 1 May 2012 11:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 pZV9JEB+K--B for <weirds@ietfa.amsl.com>; Tue, 1 May 2012 11:44:13 -0700 (PDT)
Received: from exprod6og101.obsmtp.com (exprod6og101.obsmtp.com [64.18.1.181]) by ietfa.amsl.com (Postfix) with ESMTP id C821B21E8088 for <weirds@ietf.org>; Tue, 1 May 2012 11:44:09 -0700 (PDT)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob101.postini.com ([64.18.5.12]) with SMTP ID DSNKT6Au+Zhg6NwmziduIVaGWESDLMLN+Vym@postini.com; Tue, 01 May 2012 11:44:13 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 q41Ii5nS003639 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 1 May 2012 14:44:05 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0247.003; Tue, 1 May 2012 14:44:05 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Arturo Servin <aservin@lacnic.net>
Thread-Topic: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt
Thread-Index: AQHNJ8XG31Qsu8PqsUqysAXCEDRgwJa1P26w
Date: Tue, 01 May 2012 18:44:04 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F0D5F7018@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <20120501024631.97808.qmail@joyce.lan> <6DAAECD8-30D3-4195-BE44-C95D0EE3ECE3@icann.org> <0145b859-fce2-488d-a9a9-b629525e2b6b@email.android.com> <25F98C9D-3F87-49C8-86F7-3E3797779F14@lacnic.net> <831693C2CDA2E849A7D7A712B24E257F0D5F6DB6@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <EC3C5A07-13B2-431F-BC33-3E040269980B@lacnic.net>
In-Reply-To: <EC3C5A07-13B2-431F-BC33-3E040269980B@lacnic.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/alternative; boundary="_000_831693C2CDA2E849A7D7A712B24E257F0D5F7018BRN1WNEXMBX01vc_"
MIME-Version: 1.0
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 18:44:17 -0000

I'm talking about a query like this, not authentication by IP address:

whois -h whois.verisign-grs.com 198.41.1.1

Are we talking about the same thing?

Scott

From: Arturo Servin [mailto:aservin@lacnic.net]
Sent: Tuesday, May 01, 2012 2:11 PM
To: Hollenbeck, Scott
Cc: weirds@ietf.org
Subject: Re: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt


          This seems that is because access restrictions, which I think it could be done with several methods: IP address, certificates, API keys, etc.

          Anyhow, if you are going to authenticate by IP address you are going to see the source address of the connection, not the IP address of the query. Isn't it?

Regards,
as


On 1 May 2012, at 13:49, Hollenbeck, Scott wrote:


>  Where is that info in the current whois and more important, why?

One example: Verisign currently supports whois host lookup by IP address for .com and .net. I don't know why that capability was added originally, but I believe it's been there for as long as com/net whois service has been available.

Scott

From: weirds-bounces@ietf.org<mailto:weirds-bounces@ietf.org> [mailto:weirds-bounces@ietf.org] On Behalf Of Arturo Servin
Sent: Tuesday, May 01, 2012 11:21 AM
To: Patrick Vande Walle
Cc: John Levine; weirds@ietf.org<mailto:weirds@ietf.org>
Subject: Re: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt


          Agree with Patrick.

          I do not really see the relevance to include that field.

          And as Andy mentioned in another e-mail, where is that info in the current whois and more important, why?

v2.38.3 | Report a Bug | By Email | System Status