IETF Logo Mail Archive

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

Brian Dickson <brian.peter.dickson@gmail.com> Mon, 26 September 2016 19:49 UTC

Return-Path: <brian.peter.dickson@gmail.com>
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 B782412B00E for <idr@ietfa.amsl.com>; Mon, 26 Sep 2016 12:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ZeBqZKiCDDyA for <idr@ietfa.amsl.com>; Mon, 26 Sep 2016 12:49:43 -0700 (PDT)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (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 BA0E112B2C9 for <idr@ietf.org>; Mon, 26 Sep 2016 12:49:43 -0700 (PDT)
Received: by mail-qk0-x230.google.com with SMTP id t7so178963260qkh.2 for <idr@ietf.org>; Mon, 26 Sep 2016 12:49:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RAJkjw1TmpqT1AZZKE/FVwrHzRiedjAkHUGVzdAxx5g=; b=zgLucEJN03KMIecFs+NKh4sfyjQjCluUDc1ozuW+/C9fF32KVN0HHETCglqgiXY0xc nYyO0ogx+MMXwrq2l4TnRYDi4E9Ir3aZrGJwNGlrP+ZLJo3wbGjGNFnwlQKZ9Bw1eOzZ 5CnTMVFE2IrhSDh9Vzg6X9tmwy0rQtW2bLqEsjekUHSiA0oqXTASOBs7lVXZVACOeKRm +hjJ6Q/Genqmzmyyq8Kd1C3Heot+WA59GWcwY4TBnHNCf6JcWlVaDho0tTv5MSCNz2t8 fFIQRKRuMix4KiqjcolguM9z52pyvNtXOeFleAPZ7vl2Rgkvh99x5C+sGx7Ik70irqXJ bCTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RAJkjw1TmpqT1AZZKE/FVwrHzRiedjAkHUGVzdAxx5g=; b=Hy/ZHIIlbS+Ej/bGmghQ5iGdxSsXcHQqM7iGM3uo36hU40JDydBMk2AJCkMlsISGg5 uyl+BlXT0ZmXhJ/kud/HctfvT6OcRKIVxqlV/YJGYxbqs7mWdcN9c9UCOzt7unN+4nz9 HApgq5LCSG/W+jfsuOr2OapTf8OcRFtJFx4sFzLFB9torG5R4yqoI481XBFVIF6nXCTG JXUpY1Qlq8YpbOSScj33rXfcsPxbX9+3CTlp6bMdU4qtjiU13oA+ieaRIv+lm51a2rxa FOVWVrfyT2TyWCOkNm7BwWzvOymjdkHmFgcgViGmid4RX9Q6ZwuWs0Xj09cftdyn6FxX hn0w==
X-Gm-Message-State: AE9vXwPs3ywU1skDgjDqx9eUfMhAnbYvz/npEbsvymTCRKCbp30ldsahaKONm/7zfJFI1qQlW+t05TQRAzZ0nA==
X-Received: by 10.194.176.229 with SMTP id cl5mr19012234wjc.107.1474919382782; Mon, 26 Sep 2016 12:49:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.203.4 with HTTP; Mon, 26 Sep 2016 12:49:41 -0700 (PDT)
In-Reply-To: <20160924092657.GE1603@Vurt.local>
References: <43B423F6-E214-402D-BB29-99C062C46363@juniper.net> <20160924092657.GE1603@Vurt.local>
From: Brian Dickson <brian.peter.dickson@gmail.com>
Date: Mon, 26 Sep 2016 12:49:41 -0700
Message-ID: <CAH1iCiobhRP=LqexAoi8LOVMN-O474EFHJTUTaRgxghxEi4aRw@mail.gmail.com>
To: Job Snijders <job@ntt.net>
Content-Type: multipart/alternative; boundary="089e0103e520e219ce053d6e6ded"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/AfitwhB6uOSqYv43iMvqhZH6oQo>
Cc: I Don't Remember <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: Mon, 26 Sep 2016 19:49:46 -0000

On Sat, Sep 24, 2016 at 2:26 AM, Job Snijders <job@ntt.net> wrote:

>
> 3) Should values in the range "65535:0:0 - 65535:4294967295:4294967295" be
>    reserved to accomodate any future well known communities? 65535 is
>    used in RFC1997 so i see merit in continuing to use that number.
>

IMHO, the first of the 3 32-bit values, should be treated as per the IANA
registry for Autonomous System Numbers.

There are several values in both 16-bit and 32-bit ranges with special
purposes.

Those include documentation purposes, private use, and "reserved".
Currently, I see the relevant values in the table as follows:

0 (Reserved, RFC7607)
23456 (AS_TRANS, RFC6794)
64496-64511 (Documentation and sample code, RFC5398)
64512-65534 (Private use, RFC6996)
65535 (Reserved, RFC7300)
65536-65551 (Doc'n & sample code, RFC5398)
65552-131071 (Reserved)
4200000000-4294967294 (Private use, RFC6996)
4294967295 (Reserved, RFC7300)

I'm not sure what the preferred method is these days, either refer to the
ARIN table, or to the RFCs directly.
However, the corresponding communities should inherit the properties
(Reserved, Documentation and Sample Code, Private Use, and AS_TRANS).

Brian

v2.23.0 | Report a Bug | By Email