Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)

Job Snijders <job@ntt.net> Thu, 20 October 2016 15:42 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 EDDF6129997 for <idr@ietfa.amsl.com>; Thu, 20 Oct 2016 08:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level:
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, 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 MRt9O_5ni-Sd for <idr@ietfa.amsl.com>; Thu, 20 Oct 2016 08:42:07 -0700 (PDT)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 609D7129996 for <idr@ietf.org>; Thu, 20 Oct 2016 08:42:07 -0700 (PDT)
Received: by mail3.mlpsca01.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 1bxFTl-000AzX-Aw (job@us.ntt.net); Thu, 20 Oct 2016 15:42:03 +0000
Date: Thu, 20 Oct 2016 10:41:53 -0500
From: Job Snijders <job@ntt.net>
To: "t.petch" <ietfc@btconnect.com>
Message-ID: <20161020154153.GT1033@Vurt.local>
References: <01f301d228b4$e3319ef0$a994dcd0$@ndzh.com> <20161017215134.GA464@pfrc.org> <20161018190851.GC15392@shrubbery.net> <20161018191521.GT95811@Vurt.local> <9EFC9BAA-F917-4C70-A139-1F69CAECF9C0@pfrc.org> <007201d229f6$b4ae9680$4001a8c0@gateway.2wire.net> <20161019185405.GA12214@puck.nether.net> <01ab01d22ab2$2b54f8e0$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01ab01d22ab2$2b54f8e0$4001a8c0@gateway.2wire.net>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.0 (2016-08-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/qsEG2-YcsOyG4C7MaV4-YP1uOA8>
Cc: IETF IDR WG <idr@ietf.org>, Sue Hares <shares@ndzh.com>
Subject: Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)
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: Thu, 20 Oct 2016 15:42:09 -0000

Hi Tom,

I've removed the word 'usually'. Thank you for the suggestion. 

Kind regards,

Job

On Thu, Oct 20, 2016 at 09:37:59AM +0100, t.petch wrote:
> Jared
> 
> As Brian has pointed out, it was the use of 'usually' that I was
> concerned with, as watering down the recommended use of an ASN by
> RFC1997.  Excise 'usually' and that part of my concern goes away.
> 
> Tom Petch
> 
> 
> ----- Original Message -----
> From: "Jared Mauch" <jared@puck.Nether.net>;
> Sent: Wednesday, October 19, 2016 7:54 PM
> 
> 
> > On Wed, Oct 19, 2016 at 11:47:05AM +0100, t.petch wrote:
> > > I remain unhappy with this I-D.
> > >
> > > I find it ironic that the messages for this Last Call should be
> > > interspersed with those relating to what goes wrong when someone
> > > somewhere else in the world uses a field in an unexpected way.  This
> > > reinforces my belief that this I-D should be more forceful in
> calling
> > > out the dangers (eg MUST instead of SHOULD).
> > >
> > > I think that this I-D is factually incorrect, or at least open to
> > > misinterpretation,  when it says
> > > '[RFC1997] BGP Communities attributes are four-octet values split
> into
> > >    two two-octet words.  The most significant word is usually
> > >    interpreted as an Autonomous System Number (ASN) '
> >
> > rfc1998: section 4 gives you the slice + dice bits:
> >
> > -- snip -- rfc 1998 --
> >    To make use of the BGP community attribute, several community
> values
> >    (MCI's AS number: 3561 = 0x0DE9) have been defined that can be used
> >    by customers to tag routes so that the appropriate "LOCAL_PREF"
> >    values are configured. Table 2 lists the appropriate community
> >    attribute values (and the mappings of community to LOCAL_PREF):
> > -- snip -- rfc 1998 --
> >
> > This is the segmenting, and most customers have
> > "ip bgp community new-format" configured.
> >
> > If your issue is about printf %ull vs %d:%d:%d we operators
> > can solve this by ensuring our vendors do the right thing, which
> > we have already done 20 years ago via rfc1998.
> >
> > This nit is imo not worth picking.
> >
> > - Jared
> >
> > --
> > Jared Mauch  | pgp key available via finger from jared@puck.nether.net
> > clue++;      | http://puck.nether.net/~jared/  My statements are only
> mine.
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr