IETF Logo Mail Archive

Re: [weirds] Scope and guiding principles (was Re: I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt)

"John Levine" <johnl@iecc.com> Fri, 04 May 2012 17:18 UTC

Return-Path: <johnl@iecc.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 2DBD821F8620 for <weirds@ietfa.amsl.com>; Fri, 4 May 2012 10:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.003
X-Spam-Level:
X-Spam-Status: No, score=-110.003 tagged_above=-999 required=5 tests=[AWL=1.196, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, 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 hk2pG2JXOS4n for <weirds@ietfa.amsl.com>; Fri, 4 May 2012 10:18:11 -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 4C97D21F861F for <weirds@ietf.org>; Fri, 4 May 2012 10:18:11 -0700 (PDT)
Received: (qmail 95559 invoked from network); 4 May 2012 17:18:09 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 4 May 2012 17:18: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:vbr-info; s=4fa40f51.xn--hew.k1205; i=johnl@user.iecc.com; bh=oK6JBodKF2MlilA0HG0nYTbOdHRhuacGeyW4roOiTJ4=; b=TxoX6Ut+9S7Hz0+PnGk/YIIwCuEPlFfWnAbjJrggka/p9vAwHht64WupTvC71YUzzbV/71HwU/sBgdhyM6bXKaCpBZluAGLCGmGDFFUbnKLhytRr/9d/wESfBc3NIJOqlf6TP2AMOzFkMH04RJwpKPzEWlA0SkX+Ts9bHMCJv28=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: Fri, 04 May 2012 17:17:47 -0000
Message-ID: <20120504171747.13750.qmail@joyce.lan>
From: John Levine <johnl@iecc.com>
To: weirds@ietf.org
In-Reply-To: <DA58E435-FB46-40C9-90B2-EAAF0BE7BF4B@arin.net>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 7bit
Subject: Re: [weirds] Scope and guiding principles (was Re: 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: Fri, 04 May 2012 17:18:12 -0000

>> 1. The protocol MUST enable policy options, not dictate them.

Yes.  It is in the nature of standards that they can't force anyone to
do anything, just tell people how to interoperate.

>> 2. We MUST only specify features that are already required/implemented by
>> registries/registrars. )Other features can be specified later by those
>> interested in extensions to the protocol.)

Yes.  It would be fine to keep a laundry list of features that someone would
like to add eventually but don't currently qualify.

R's,
John

v2.23.0 | Report a Bug | By Email