Re: [GROW] Alissa Cooper's No Objection on draft-ietf-grow-wkc-behavior-06: (with COMMENT)

Randy Bush <randy@psg.com> Mon, 10 June 2019 20:18 UTC

Return-Path: <randy@psg.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF1F12006B; Mon, 10 Jun 2019 13:18:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 EWBC4s7bIr1H; Mon, 10 Jun 2019 13:18:44 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 83A2312003E; Mon, 10 Jun 2019 13:18:44 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1haQkc-0003M9-T7; Mon, 10 Jun 2019 20:18:43 +0000
Date: Mon, 10 Jun 2019 13:18:42 -0700
Message-ID: <m2pnnlp525.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Alissa Cooper via Datatracker <noreply@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-grow-wkc-behavior@ietf.org, grow@ietf.org
In-Reply-To: <156019490227.14511.5752126140840043791.idtracker@ietfa.amsl.com>
References: <156019490227.14511.5752126140840043791.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.2 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/0z7OCY9nQzP6ZE-I5-wleYWfSPM>
Subject: Re: [GROW] Alissa Cooper's No Objection on draft-ietf-grow-wkc-behavior-06: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2019 20:18:46 -0000

> Section 4.1:
> 
> s/is not really on IANA's list/is not individually named on IANA's
> list/

more correctly, i think

   not receive special treatment in Cisco IOS XR, and at least one
   specific community on Cisco IOS XR's special treatment list (internet
   == 0:0) is not formally a Well-Known Community as it is not in
   [IANA-WKC]; but taken from the "Reserved" range
   [0x00000000-0x0000FFFF].

> Section 5:
> 
> I'm not sure what the '>' character indicates.

a klutz at the keyboard

> Section 6:
> 
> "Vendors SHOULD clearly document the behavior of "set" directive in
> their implementations." I'm not sure normative language makes sense
> here (otherwise, what is the rationale for not using MUST?).

in a vain hope of reciprocity, ops folk are hesitant to tell vendors
MUST unless something will actually break.  will consult with
co-authors.  my guess of outcome is MUST; but i am not a great guesser.

thanks for review!

randy