Re: [Idr] I-D Action: draft-ietf-idr-large-community-01.txt

Sander Steffann <sander@steffann.nl> Mon, 17 October 2016 22:03 UTC

Return-Path: <sander@steffann.nl>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DD8E129535 for <idr@ietfa.amsl.com>; Mon, 17 Oct 2016 15:03:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steffann.nl
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 laupT-CVlJiw for <idr@ietfa.amsl.com>; Mon, 17 Oct 2016 15:03:33 -0700 (PDT)
Received: from mail.sintact.nl (mail.sintact.nl [83.247.10.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0E7112943F for <idr@ietf.org>; Mon, 17 Oct 2016 15:03:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 776153A; Tue, 18 Oct 2016 00:03:29 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:message-id:date:date:in-reply-to:from:from :subject:subject:mime-version:content-type:content-type:received :received; s=mail; t=1476741807; bh=e9EdzyBYhCOhmkAO5dtxYD3Oq7NC o/ExbJOxWD4AhiQ=; b=b6po8XUEAFOVED3y88TxoJasFNOeCBou2DQKW2g5cXaS 3MJLmkGk+ucVPoNJSMnqjcmHsie+VFbEjhuhIwEWKEQFgsR3O10oM0cfCEra0t+o ya9iFyjR+11p0uTyqiO48ymUbH70Jia3EQk3F30nc3LdJuwzS9l/G0M2n/xPbcM=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id mr4Y_Sm9MKd2; Tue, 18 Oct 2016 00:03:27 +0200 (CEST)
Received: from [IPv6:2a02:a213:a300:9300:5d56:1f4d:74e2:2510] (unknown [IPv6:2a02:a213:a300:9300:5d56:1f4d:74e2:2510]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id 8E6D138; Tue, 18 Oct 2016 00:03:27 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_AF0BA535-95DC-4C29-BDD5-C2BF62E2F5E8"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <5803ECD9.3060405@foobar.org>
Date: Tue, 18 Oct 2016 00:03:25 +0200
Message-Id: <9E34B3BC-74A8-4EAA-877E-86BDCB31476D@steffann.nl>
References: <57F92043.20301@foobar.org> <A9BBA442-361F-444F-9AFC-33FAAF5F6061@gmail.com> <00ff01d22214$a9832440$4001a8c0@gateway.2wire.net> <57FAD3EA.6070800@foobar.org> <020b01d223a1$f0e34a20$4001a8c0@gateway.2wire.net> <20161011095417.GL19434@gir.theapt.org> <1476317462333.82977@dacor.de> <00fb01d2252f$700c2360$4001a8c0@gateway.2wire.net> <370dd06bff7c425db78dc82c5bce8907@XCH-ALN-014.cisco.com> <015001d226da$32df80c0$4001a8c0@gateway.2wire.net> <20161015124556.GW57491@Vurt.local> <8D4A7FDB-FBAC-4914-AE32-7D46EDC564C7@gmail.com> <5803ECD9.3060405@foobar.org>
To: Nick Hilliard <nick@foobar.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/7Tqj9xhVrmOvU8oqZ3GGb9C3oEc>
Cc: idr <idr@ietf.org>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-large-community-01.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2016 22:03:34 -0000

Hi,

> Until there is a protocol in place to make this viable, demanding MUST
> instead of SHOULD is creating a requirement for standards-track
> mandatory compliance with a poorly-defined specification which, as you
> note, cannot be enforced. This is not wise, and it has no place in a
> standards-track document.

I agree. The definition of SHOULD is strict enough as it is:

SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.

The "full implications must be understood and carefully weighed" is strong enough for this situation.

Cheers,
Sander