[GROW] Opsdir last call review of draft-ietf-grow-wkc-behavior-03
Carlos Pignataro via Datatracker <noreply@ietf.org> Fri, 10 May 2019 01:40 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: grow@ietf.org
Delivered-To: grow@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 68D11120047; Thu, 9 May 2019 18:40:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carlos Pignataro via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: grow@ietf.org, ietf@ietf.org, draft-ietf-grow-wkc-behavior.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Carlos Pignataro <cpignata@cisco.com>
Message-ID: <155745241938.24600.10242636748872467209@ietfa.amsl.com>
Date: Thu, 09 May 2019 18:40:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/uKDcRB6_U65ZteC0iv0R6Crq0vs>
Subject: [GROW] Opsdir last call review of draft-ietf-grow-wkc-behavior-03
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 10 May 2019 01:40:20 -0000
Reviewer: Carlos Pignataro Review result: Has Issues Reviewer: Carlos Pignataro I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. Easy-to-read straightforward document. I've some questions, comments, small issues, and pedantic nits for your consideration: Intended status: Standards Track This really "reads" like a BCP to me... has the intended status been discussed? 5. Note for Those Writing RFCs for New Community-Like Attributes Care should be taken when establishing new [RFC1997]-like attributes (large communities, wide communities, etc) to avoid repeating this s/etc/etc./ 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. 8. IANA Considerations This document has no IANA Considerations other than to be aware that any future Well-Known Communities will be subject to the policy treatment described here. 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] 10. Normative References [IANA-WKS] "IANA Well-Known Communities", <https://www.iana.org/assignments/bgp-well-known- communities/bgp-well-known-communities.xhtml>. 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"? Nit: Capitalization of "well-known" throughout. The document includes "well-known", "Well-Known", "Well-Known Communities", "Well-Known communities", and other variations that could use normalization. Best, Carlos Pignataro.
- [GROW] Opsdir last call review of draft-ietf-grow… Carlos Pignataro via Datatracker