[GROW] reviews of draft-ietf-grow-wkc-behavior-04
draft-ietf-grow-wkc-behavior@ietf.org Wed, 29 May 2019 12:41 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 F1B3E120106; Wed, 29 May 2019 05:41:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.887
X-Spam-Level:
X-Spam-Status: No, score=-6.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01] 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 07VllpdpJEW8; Wed, 29 May 2019 05:41:05 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [198.180.150.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 2C92412006D; Wed, 29 May 2019 05:41:05 -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 1hVxt9-0000BP-DC; Wed, 29 May 2019 12:41:03 +0000
Date: Wed, 29 May 2019 05:41:02 -0700
Message-ID: <m28supa0wx.wl-draft-ietf-grow-wkc-behavior@ietf.org>
From: draft-ietf-grow-wkc-behavior@ietf.org
To: IESG <iesg@ietf.org>
Cc: GMO Crops <grow@ietf.org>
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: multipart/mixed; boundary="Multipart_Wed_May_29_05:41:02_2019-1"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/yM5w-1qqUEUdr1_YWYoyiIhDW8g>
X-Mailman-Approved-At: Wed, 29 May 2019 13:04:51 -0700
Subject: [GROW] reviews of draft-ietf-grow-wkc-behavior-04
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: Wed, 29 May 2019 12:41:09 -0000
thanks for reviews. -05 is circulating among authors and should be out today ot tomorrow. here is what we have so far. comments solicited. --- "Mirja Kühlewind via Datatracker" <noreply@ietf.org> wrote: > I think this document should update RFC1997. ok --- Adrian Farrel via Datatracker wrote: we have most of your comments in; but did not muck with the 2119bis etc.; preferring to support full employment for the rfc editor. :) and we leave it to the iseg to have fun deciding bcp, standard, info, whatever. above our pay grade. --- Carlos Pignataro via Datatracker wrote: > > 7. Security Considerations > > Surprising defaults and/or undocumented behaviors are not good for > security. This document attempts to remedy that. > > Indeed, but this is not an exclusivity of a security consideration. In fact, > default values and behaviors are covered in > https://tools.ietf.org/html/rfc5706#appendix-A. do not understand what change you are suggesting > Should then the IANA registry be updated to point to this RFC? > Otherwise someone looking at > https://www.iana.org/assignments/bgp-well-known-communities/ > > Will only see: > BGP Well-known Communities > Reference > [RFC1997] hmmm. ok, worth a note in the iana considerations and we'll see what they say. > In this Reference, there's a few improvements needed: > 1. The Author should have "IANA" org > 2. The Title should be "Border Gateway Protocol (BGP) Well-known Communities" > 3. The URI should be > "<https://www.iana.org/assignments/bgp-well-known-communities/>" 4. Should a > descriptive anchor be "IANA-WKC" instead of "IANA-WKS"? thanks. url refs are a pain. ---
- [GROW] reviews of draft-ietf-grow-wkc-behavior-04 draft-ietf-grow-wkc-behavior