Re: [v6ops] I-D Action: draft-ietf-v6ops-ula-usage-recommendations-04.txt

Mark Andrews <marka@isc.org> Thu, 05 November 2015 07:17 UTC

Return-Path: <marka@isc.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 210931B3AAB for <v6ops@ietfa.amsl.com>; Wed, 4 Nov 2015 23:17:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 3d9WVUy6aVoB for <v6ops@ietfa.amsl.com>; Wed, 4 Nov 2015 23:17:45 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84E6D1B3A49 for <v6ops@ietf.org>; Wed, 4 Nov 2015 23:17:45 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.ams1.isc.org (Postfix) with ESMTPS id 3F5C11FCAB8; Thu, 5 Nov 2015 07:17:42 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 5CAD4160076; Thu, 5 Nov 2015 07:17:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 4887A160031; Thu, 5 Nov 2015 07:17:41 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id SCPEMwTqb6s6; Thu, 5 Nov 2015 07:17:41 +0000 (UTC)
Received: from rock.dv.isc.org (c122-106-161-187.carlnfd1.nsw.optusnet.com.au [122.106.161.187]) by zmx1.isc.org (Postfix) with ESMTPSA id 90B44160076; Thu, 5 Nov 2015 06:40:54 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 308F23BE9BE0; Thu, 5 Nov 2015 17:40:52 +1100 (EST)
To: David Farmer <farmer@umn.edu>
From: Mark Andrews <marka@isc.org>
References: <20141027073843.13643.64057.idtracker@ietfa.amsl.com> <8D8A25B4-2E47-4524-9F76-11A0C28DDD39@nestlabs.com> <8AACD6C0-7B3D-44B0-AEF4-1880A5A63FBD@nestlabs.com> <563ADB4B.4070409@umn.edu>
In-reply-to: Your message of "Wed, 04 Nov 2015 22:30:03 -0600." <563ADB4B.4070409@umn.edu>
Date: Thu, 05 Nov 2015 17:40:52 +1100
Message-Id: <20151105064052.308F23BE9BE0@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/tUAY9bSQOw9pPRAaVahZk47mEzw>
Cc: V6OPS Working Group <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ula-usage-recommendations-04.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Nov 2015 07:17:47 -0000

In message <563ADB4B.4070409@umn.edu>, David Farmer writes:
> On 11/4/15 19:41 , James Woodyatt wrote:
> > Everyone-
> >
> > This draft A) uses normative requirements language with RFC 2119
> > keywords and B) calls for publication in the Informational category. Is
> > the document really intended for the Best Current Practice (BCP)
> > category? If not, could we please either remove the citation of RFC 2119
> > and all the usage of upper case keywords, or insert an explanation for
> > why the document uses normative requirements language despite being an
> > Informational category document?
>
> The only use of use upper case RFC2119 keywords in the document are in
> quotes from other documents.  Such use seem appropriate, even if you
> think upper case RFC2119 keywords are not normally appropriate in an
> Informational category document.  Since quotes using upper case RFC2119
> keywords are included I think the citation of RFC 2119 is also
> appropriate and clarifies their use.

Then you have to think about all use of "must", "should" etc. in
terms of RFC2119.  For reference I've got drafts which quote
documents with RFC2119 semantics but have not cited RFC 2119.

There is also nothing preventing the use of RFC 2119 in BCP or INFO
documents.  The use of RFC 2119 does not imply standard.

Mark

> --
> ================================================
> David Farmer               Email: farmer@umn.edu
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE     Phone: 1-612-626-0815
> Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
> ================================================
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org