Re: [Idr] AD Review of draft-ietf-idr-large-community-09

Job Snijders <job@ntt.net> Fri, 02 December 2016 15:45 UTC

Return-Path: <job@ntt.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 955CB1297F1; Fri, 2 Dec 2016 07:45:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.831
X-Spam-Level:
X-Spam-Status: No, score=-4.831 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.896, SPF_SOFTFAIL=0.665] 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 GNQjtiDKWDJS; Fri, 2 Dec 2016 07:45:17 -0800 (PST)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 696BC129468; Fri, 2 Dec 2016 07:45:02 -0800 (PST)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <job@ntt.net>) id 1cCq1C-0003ud-8R (job@us.ntt.net); Fri, 02 Dec 2016 15:44:59 +0000
Date: Fri, 2 Dec 2016 16:44:54 +0100
From: Job Snijders <job@ntt.net>
To: Michael H Lambert <lambert@psc.edu>
Message-ID: <20161202154454.GH47164@Vurt.local>
References: <CE1331E4-3ECA-41D7-801F-05519778E8DA@cisco.com> <94f48779-14c8-0ec0-93ef-69eeba49e5be@gmail.com> <8B6BA07A-D636-4D8C-8B02-A5CB05538AAF@cisco.com> <AAC9E38F-BF0D-41D7-8871-9B89D31BC37B@juniper.net> <8A889AAA-05C6-4036-B05A-316FEB2C84E2@psc.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <8A889AAA-05C6-4036-B05A-316FEB2C84E2@psc.edu>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.1 (2016-10-04)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/VXeMGhCvKq7HBQGWSUi3DmqZNro>
Cc: "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-large-community@ietf.org" <draft-ietf-idr-large-community@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Subject: Re: [Idr] AD Review of draft-ietf-idr-large-community-09
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2016 15:45:28 -0000

On Fri, Dec 02, 2016 at 10:40:25AM -0500, Michael H Lambert wrote:
> > On 2 Dec 2016, at 08:57, John G. Scudder <jgs@juniper.net>; wrote:
> > 
> > On Dec 2, 2016, at 8:46 AM, Alvaro Retana (aretana) <aretana@cisco.com>; wrote:
> >> Removing and ignoring are obviously different thingsā€¦  The text
> >> above is fine with me, but I would ask: what do the current
> >> implementations do?  If they remove (as originally specified), then
> >> I would suggest you keep that.
> > 
> > What do you think would be a good minimal change to clarify? How
> > about changing the word "duplicate" to "redundant"?
> > 
> > OLD:
> >   Duplicate BGP Large Community values MUST NOT be transmitted.  A
> >   receiving speaker MUST silently remove duplicate BGP Large Community
> >   values from a BGP Large Community attribute.
> > 
> > NEW:
> >   Duplicate BGP Large Community values MUST NOT be transmitted.  A
> >   receiving speaker MUST silently remove redundant BGP Large Community
> >   values from a BGP Large Community attribute.
> 
> Just for clarification:  Does "speaker" in this context refer to a BGP
> speaker implementing large communities, and, by inference, excludes
> BGP speakers not supporting large communities?

This only applies to BGP speakers who understand the Large Community. To
speakers without Large Community support, it will just be an optional
transitive attribute which is passed on in verbatim.

Kind regards,

Job