Re: [Idr] WG adoption of draft-heitz-idr-large-community; one week to comment on early code point allocation

Job Snijders <job@ntt.net> Tue, 27 September 2016 14:58 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 2B47112B0D8 for <idr@ietfa.amsl.com>; Tue, 27 Sep 2016 07:58:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.251
X-Spam-Level:
X-Spam-Status: No, score=-4.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, 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 3_3CDIRq5vCZ for <idr@ietfa.amsl.com>; Tue, 27 Sep 2016 07:58:46 -0700 (PDT)
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 A9D2C12B05F for <idr@ietf.org>; Tue, 27 Sep 2016 07:58:46 -0700 (PDT)
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 1botqG-000E3N-Rx (job@us.ntt.net); Tue, 27 Sep 2016 14:58:45 +0000
Date: Tue, 27 Sep 2016 16:58:41 +0200
From: Job Snijders <job@ntt.net>
To: Jeffrey Haas <jhaas@pfrc.org>
Message-ID: <20160927145841.GF64449@Vurt.local>
References: <43B423F6-E214-402D-BB29-99C062C46363@juniper.net> <20160924092657.GE1603@Vurt.local> <CAH1iCiobhRP=LqexAoi8LOVMN-O474EFHJTUTaRgxghxEi4aRw@mail.gmail.com> <20160926211852.GL3036@Hanna.local> <CAH1iCip0=uYNieQmu=EMRNkGJTSLkhT_WjMj_4m0g+XApBEfkw@mail.gmail.com> <C8FC1795-5A6B-4994-AB35-8C8F82127F7D@pfrc.org> <20160927082443.GI1558@Vurt.local> <E84D9BB0-CCAD-4E21-984F-E3B1949E225C@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E84D9BB0-CCAD-4E21-984F-E3B1949E225C@pfrc.org>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.0 (2016-08-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ipnqjpzhNnIleJ8suPgBjlUVwII>
Cc: In-Depth Review <idr@ietf.org>
Subject: Re: [Idr] WG adoption of draft-heitz-idr-large-community; one week to comment on early code point allocation
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: Tue, 27 Sep 2016 14:58:48 -0000

On Tue, Sep 27, 2016 at 10:31:45AM -0400, Jeffrey Haas wrote:
> > On Sep 27, 2016, at 4:24 AM, Job Snijders <job@ntt.net> wrote:
> > 
> > On Mon, Sep 26, 2016 at 07:31:57PM -0400, Jeffrey Haas wrote:
> >> FWIW, I think things with "well known" semantics should stick to the
> >> reserved code point space in 1997 communities unless there's some
> >> motivation to have a common parameter/argument in it.  In that case,
> >> it fits the case for large comms anyway.
> > 
> > I agree with you Jeff. 
> > 
> > How about the following:
> > 
> > """
> >    The Large Community attribute values in the following ranges are
> >    reserved:
> > 
> >             0:0:0 -          0:4294967295:4294967295
> >    4294967295:0:0 - 4294967295:4294967295:4294967295
> > 
> > """
> > 
> > This way the lowest and highest possible value are reserved, and at some
> > later point (part of) these reserved ranges could be converted to
> > Well-known or something else if that need arises.
> 
> I'm fine with such a reservation. However, it'd be good to get the
> reasoning in the doc rather than letting it be inferred after the
> fact.

Thank you for your feedback.

Would you be willing to (unicast) a couple of sentences to describe why
0 and 2^32-1 are special?

Kind regards,

Job