Re: [weirds] Applications Area Directorate Review of draft-ietf-weirds-rdap-sec-09

Andy Newton <andy@arin.net> Wed, 22 October 2014 13:55 UTC

Return-Path: <andy@arin.net>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57D0A1AC3A8; Wed, 22 Oct 2014 06:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0fa_JKsXSjWe; Wed, 22 Oct 2014 06:55:43 -0700 (PDT)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id 3385D1AC3AE; Wed, 22 Oct 2014 06:55:42 -0700 (PDT)
Received: by smtp2.arin.net (Postfix, from userid 323) id E323F21378A; Wed, 22 Oct 2014 09:55:41 -0400 (EDT)
Received: from chaedge02.corp.arin.net (chaedge02.corp.arin.net [192.149.252.119]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp2.arin.net (Postfix) with ESMTP id 361B521378F; Wed, 22 Oct 2014 09:55:41 -0400 (EDT)
Received: from CHACAS02.corp.arin.net (10.1.30.108) by chaedge02.corp.arin.net (192.149.252.119) with Microsoft SMTP Server (TLS) id 14.3.181.6; Wed, 22 Oct 2014 09:57:34 -0400
Received: from CHAMBX02.corp.arin.net ([fe80::905e:9b4d:2909:f55a]) by CHACAS02.corp.arin.net ([fe80::54ae:f9de:2f8b:1072%12]) with mapi id 14.03.0181.006; Wed, 22 Oct 2014 09:55:40 -0400
From: Andy Newton <andy@arin.net>
To: Scott Hollenbeck <shollenbeck@verisign.com>
Thread-Topic: [weirds] Applications Area Directorate Review of draft-ietf-weirds-rdap-sec-09
Thread-Index: AQHP7dOraLlEMb/T9k2LS8+NEgKgD5w8HmfwgABIuIA=
Date: Wed, 22 Oct 2014 13:55:39 +0000
Message-ID: <2FC7374A-6DF3-49F8-9FDD-8E8ADDCAA15A@arin.net>
References: <46A1DF3F04371240B504290A071B4DB63E779CE3@SZXEMA510-MBX.china.huawei.com> <831693C2CDA2E849A7D7A712B24E257F494F1417@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F494F1417@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.0.87]
Content-Type: multipart/alternative; boundary="_000_2FC7374A6DF349F89FDD8E8ADDCAA15Aarinnet_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/M2sWLnlokqj0T0i0uwdxRld6FfE
Cc: "draft-ietf-weirds-rdap-sec.all@tools.ietf.org" <draft-ietf-weirds-rdap-sec.all@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] Applications Area Directorate Review of draft-ietf-weirds-rdap-sec-09
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 22 Oct 2014 13:55:47 -0000

On Oct 22, 2014, at 9:46 AM, Hollenbeck, Scott <shollenbeck@verisign.com<mailto:shollenbeck@verisign.com>> wrote:

n1) 3.3, it would be nice to replace "a 429 response code" by "a 429
(Too many Requests) response code".

Thanks for the feedback, Bert. You're probably right, but since this is a nit I'd prefer to leave the text as-is to maintain consistency with other RDAP documents that describe HTTP response codes without using parenthetical text to describe the meaning of the code. We have normative references in the appropriate places to do that.

Scott,

Bert has made the same comment on using-http, so the parentheticals will appear in our other documents. I view it as a readability thing, not necessarily a normative reference issue.

-andy