Re: [Sidrops] Opsdir last call review of draft-ietf-sidrops-rtr-keying-02

Randy Bush <> Wed, 26 December 2018 14:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B461E130FED; Wed, 26 Dec 2018 06:25:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id v-iQLeJfRHL9; Wed, 26 Dec 2018 06:25:30 -0800 (PST)
Received: from ( [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DC2E1130FEC; Wed, 26 Dec 2018 06:25:29 -0800 (PST)
Received: from localhost ([] by with esmtp (Exim 4.90_1) (envelope-from <>) id 1gcA7i-0005x1-13; Wed, 26 Dec 2018 14:25:26 +0000
Date: Wed, 26 Dec 2018 09:25:25 -0500
Message-ID: <>
From: Randy Bush <>
To: Scott Bradner <>
Cc:,,, IETF Rinse Repeat <>
In-Reply-To: <>
References: <>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="ISO-8859-7"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [Sidrops] Opsdir last call review of draft-ietf-sidrops-rtr-keying-02
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 26 Dec 2018 14:25:32 -0000

mornin’ scott,

> it is hard to see why it should be standards track or why it should 
> be using RFC 2119 type terminology.

these are two separate issues.  

alvaro and the chairs can adjudicate what flavor of ice cream it should
be.  it my memory says it was a wg decision.  i really do not care.

as to 2119 language, i kinda feel it should remain.  it is used
sparingly. but is crucial when used.  e.g.

      all private keys MUST be protected when at rest in a secure

i suspect we would want to keep that strongly prescriptive; but it is
not a hill on which i am interested in dying.