IETF Logo Mail Archive

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:39 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 1BBA5129996 for <idr@ietfa.amsl.com>; Thu, 20 Oct 2016 08:39:10 -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 np2hLWbpi0H8 for <idr@ietfa.amsl.com>; Thu, 20 Oct 2016 08:39:09 -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 11B70129991 for <idr@ietf.org>; Thu, 20 Oct 2016 08:39:09 -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 1bxFQu-000Agk-Sx (job@us.ntt.net); Thu, 20 Oct 2016 15:39:06 +0000
Date: Thu, 20 Oct 2016 10:38:58 -0500
From: Job Snijders <job@ntt.net>
To: "t.petch" <ietfc@btconnect.com>
Message-ID: <20161020153858.GR1033@Vurt.local>
References: <007201d229f6$b4ae9680$4001a8c0@gateway.2wire.net> <20161019185405.GA12214@puck.nether.net> <CAH1iCirF_1ODLtLzeVhKmQPDeeGcczcQCSPXDcro=OQv2ipR3A@mail.gmail.com> <5807F3AF.9080200@foobar.org> <CA+b+ERn_7Bs8CeAgKrxSPiMPOCsE4pH9hoD+76tEDrWM-KYVRw@mail.gmail.com> <CAH1iCirF2C-83z3hYC4bBqMYW7zHs1eeofySVipyODo=8FNQxg@mail.gmail.com> <CA+b+ER=oyCTF24f1pAQQjA0ogMCtqw0rKWzT7+jcNpL4WjPjHQ@mail.gmail.com> <CAH1iCipd+wyFVwvunjVFxF1t52j3_sKm5efGXzNH8xwHLndaHQ@mail.gmail.com> <alpine.DEB.2.02.1610200756430.12036@uplift.swm.pp.se> <01ad01d22ab2$2c8c4060$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <01ad01d22ab2$2c8c4060$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/r8KhkQUOOlRGCkQG-oRkMloH4gs>
Cc: IETF IDR WG <idr@ietf.org>
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:39:10 -0000

On Thu, Oct 20, 2016 at 10:08:17AM +0100, t.petch wrote:
> In theory, I agree with you but in practice, I expect it will be at
> least a year or two before GROW produces such a document.  In the
> meantime, I would go with Jeff's suggestion to include an 'Operational
> Considerations' section in this I-D (and that then could refer to
> RFC7454 and clarify the meaning of 'high order bits').
> 
> But I think that we have yet to agree what such a section would say.

We are certainly not putting in sections for which we have no content.

I've mentioned this before: a small group of operators is working on
usage guidelines for large bgp communities in the spirit of rfc1998. The
document is not ready yet to be published. The target working group will
be GROW and its intended status Informational.

I think a 12 to 24 month timeframe for the document to mature is
reasonable and not a problem.

Kind regards,

Job

v2.23.0 | Report a Bug | By Email