Re: Genart last call review of draft-ietf-grow-large-communities-usage-06

Job Snijders <job@instituut.net> Tue, 18 April 2017 23:59 UTC

Return-Path: <job@instituut.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4205A129471 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=instituut-net.20150623.gappssmtp.com
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 su75tacGFwrD for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 16:59:05 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 625FC129454 for <ietf@ietf.org>; Tue, 18 Apr 2017 16:59:02 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id r190so9352876wme.1 for <ietf@ietf.org>; Tue, 18 Apr 2017 16:59:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=DF3uJat12kvgKRtdU59rkzOHPq8lXIuqdOvP0M2DTjw=; b=Kh0xYTjmgskNnBOGVDhZn9LtH50yrnyxJ439ZHvMvFTWqUlSZL/m1CA0bl237YHyEL x95F0wCozvcHjVhdjm8sXJGfe8jZuzd6vMfZ/HaKKZX4POnP5AkOvfPybKbgA7wsz0k4 XFJTDeJZSd7LlHbprNN0uoMozZWHcNup8vIS5ZCTL1ZN1AwVTHUMicrqWjQOLUFm/Ma+ G/sOa4Frjm8g8Hqqm2FiPrAixFZ3MPS7EQuzI8As0Vx/n8uSWpaAEpAgCJQPCtxmw+aR PMh7rxRdt/LKtShZ0V/u0arHAJTMcJCSMMgfNOpXjiOXU4SSMIt0H2MLaAy4rjBce/89 59pA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=DF3uJat12kvgKRtdU59rkzOHPq8lXIuqdOvP0M2DTjw=; b=LDm+kETlACpYv2lhptkRLVc9stm5sqfcZK2CpbB10ajtJsr84hF4skocdhXlsMicSd y8KjCHOX54E+SbOvBg3Q1vHHshrACjjVNRknWIsTYL4il0l9IxF0nDvkDKaYRggi/BkZ sW4Lh6BkXYKoj9LRHrixcW9eYoX0h2gZLMFQOMUez6XM8vk2Pb5ieaWhT8pNC3pvgwUQ rlQ/S7dGB4PGziyD2cq3wlk3CHryqUC1VB51CLTIUoMYqmU+Ci3D+tuG49yOav4e7AKJ ialZpO+nKdgEcIAY0om4zAu2ibwc+mI6C+DSgrCcmXHlOVU//6+iyNRSwqe00lpc0J6g cAyA==
X-Gm-Message-State: AN3rC/7UBxzELtDPGdZRqvhJjPrarysuK4SD5NUyLQczE/dNvL+67oCQ dVUsdBrg7sL26A==
X-Received: by 10.28.100.195 with SMTP id y186mr15705406wmb.68.1492559940550; Tue, 18 Apr 2017 16:59:00 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:b007:e025:f7a1:2601]) by smtp.gmail.com with ESMTPSA id 31sm862871wrt.35.2017.04.18.16.58.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Apr 2017 16:58:59 -0700 (PDT)
Date: Wed, 19 Apr 2017 01:58:58 +0200
From: Job Snijders <job@instituut.net>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Subject: Re: Genart last call review of draft-ietf-grow-large-communities-usage-06
Message-ID: <20170418235858.sgsa64r7b5th7zam@Vurt.local>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FfX9kpdNJLNZ4gy4gZNYM-IXFxg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 23:59:06 -0000

Hi Bryant,

Thank you for taking the time to go through the document.

On Tue, Apr 18, 2017 at 06:41:15AM -0700, Stewart Bryant wrote:
> Please treat these comments just like any other last call comments.
> 
> SB> Even if you just copy the Introduction, the Abstract should
> SB> really be expanded to help the reader understand whether or not
> SB> they want read the RFC or if they had read it what it was about.

OK, we'll copy some text from the introduction section to the abstract
section to provide a better pitch why one would want to read this
document.

> ============
> 
> 5.  Security Considerations
> 
>    Operators should note the recommendations in Section 11 of BGP
>    Operations and Security [RFC7454].
> 
> SB> You do not address the question of whether there are new
> SB> considerations, or considerations that are of increased importance?

It is my understanding that RFC 8092 "BGP Large Communities" are just
like RFC 1997 "BGP Communities", but ...  larger (for lack of better
words). Referencing RFC 7454 seems plenteous.

So, what if there are not any additional considerations, If there were,
they would've been (or are) covered in RFC 8092's security section,
right?

This is an Internet-Draft targetted for Informational status, I'm not
sure what you expect here.

> SB> Is there is text somewhere that discusses the integrity and
> SB> synchronization of the parameters and any consequences that arise?

the what now? Can you elaborate on the above?

> ===========
> 
> Minor issues:
> 
> 2.2.  Action Communities
> 
>    Action Communities are added as a label to request that a route be
>    treated in a particular way within an AS.  The operator of the AS
>    defines a routing policy that adjusts path attributes based on the
>    community.  For example, the route's propagation characteristics,
>    the LOCAL_PREF (local preference), the next-hop, or the number of
>    AS_PATH prepends to be added when it is received or propagated can
>    be changed.
> 
> SB> Although these are well known to the target audience, I think you
> SB> need some references in the above para.

What reference would you suggest? You feel the section 2.2 text cannot
stand on its own?

Kind regards,

Job