Re: [weirds] feedback on draft-designteam-weirds-using-http

Arturo Servin <aservin@lacnic.net> Thu, 17 May 2012 17:16 UTC

Return-Path: <aservin@lacnic.net>
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 8A00021F86B8 for <weirds@ietfa.amsl.com>; Thu, 17 May 2012 10:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level:
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 dHc-D8KGZ9s2 for <weirds@ietfa.amsl.com>; Thu, 17 May 2012 10:16:13 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id A1B9421F853F for <weirds@ietf.org>; Thu, 17 May 2012 10:16:12 -0700 (PDT)
Received: from 85-7-200.lacnic.net.uy (unknown [200.7.85.172]) by mail.lacnic.net.uy (Postfix) with ESMTP id 924DC30843E; Thu, 17 May 2012 14:16:18 -0300 (UYT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_F9397E69-9846-494B-9DA0-D053BF040ED3"
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <4FB520B4.1070803@gmx.de>
Date: Thu, 17 May 2012 14:16:08 -0300
Message-Id: <18A3C630-38CD-471B-9877-C8D78228B585@lacnic.net>
References: <4FB26082.3070800@gmx.de> <9B94D739-E037-4539-82E8-0E79BBFEC543@hxr.us> <4FB520B4.1070803@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck:
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: weirds@ietf.org
Subject: Re: [weirds] feedback on draft-designteam-weirds-using-http
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: Thu, 17 May 2012 17:16:13 -0000

	I think it is important to mention it. Otherwise you will end up with different approaches to solve the problem for getting fresh information.

regards,
as

On 17 May 2012, at 13:00, Julian Reschke wrote:

>>> 4.2.  Parameters
>>> 
>>>   To overcome issues with misbehaving HTTP [RFC2616] cache
>>>   infrastructure, clients may use the '__weirds__cachebust' query
>>>   parameter with a random value of their choosing.  Servers MUST ignore
>>>   this query parameter.
>>> 
>>>   The following is an example use of this parameter to retreive the
>>>   abuse contacts associated with the most specific IP network with the
>>>   address 192.0.2.0:
>>> 
>>> 
>>>     /ip/192.0.2.0/operator/contacts/abuse?__weirds_cachebust=xyz123
>>> 
>>> 
>>>   For all others, servers SHOULD ignore unknown query parameters.
>>> 
>>> I think what you're saying is that all query parameters are ignored, right?
>>> 
>>> The whole concept of reserving a specific one is strange to say the least.
>> 
>> I don't know if it is strange, but I see your point. We simply need to state that all query unknown parameters should be ignored and the problem takes care of itself.
> 
> Yep.
> 
> I'd also move the discussion of cache busting into an appendix, or not mention it at all; it's not specific to this protocol.