Re: [Idr] Review of draft-ietf-large-community-06.txt

Job Snijders <job@ntt.net> Fri, 04 November 2016 18:13 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 128B11295ED; Fri, 4 Nov 2016 11:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.432
X-Spam-Level:
X-Spam-Status: No, score=-3.432 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.497, 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 qkwndW1H_5sf; Fri, 4 Nov 2016 11:13:57 -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 AD9B312961E; Fri, 4 Nov 2016 11:13:06 -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 1c2iz7-0006a9-Hy (job@us.ntt.net); Fri, 04 Nov 2016 18:13:02 +0000
Date: Fri, 4 Nov 2016 19:12:59 +0100
From: Job Snijders <job@ntt.net>
To: Geoff Huston <gih@apnic.net>
Message-ID: <20161104181259.GH961@Vurt.local>
References: <112dc01d235fd$57f9c370$07ed4a50$@ndzh.com> <C2DABF02-D3CB-4646-B869-FBCE5F05FDA1@apnic.net> <117ea01d23611$a28513e0$e78f3ba0$@ndzh.com> <CED07D95-A426-469C-85B4-DB2FBE52D14A@apnic.net> <288c77155de540adbdb60d8587b9f39b@XCH-ALN-014.cisco.com> <E3FB42F7-507F-4F8D-9F52-70D39CDCDAC9@apnic.net> <20161104171834.GE961@Vurt.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20161104171834.GE961@Vurt.local>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.1 (2016-10-04)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_FBsS0L0pRvproo1SPkXyJJdFy0>
Cc: IETF IDR WG <idr@ietf.org>, Susan Hares <shares@ndzh.com>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
Subject: Re: [Idr] Review of draft-ietf-large-community-06.txt
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, 04 Nov 2016 18:13:58 -0000

If we consider this as Option B:

On Fri, Nov 04, 2016 at 06:18:34PM +0100, Job Snijders wrote:
> Does removing the word "canonical" address the raised remark?
> 
> """
> 4.  Representation
> 
>    Large BGP Communities MUST be represented as three separate unsigned
>    integers in decimal notation in the following order: Global
>    Administrator, Local Data 1, Local Data 2.  Numbers MUST NOT contain
>    leading zeros; a zero value MUST be represented with a single zero.
>    For example: 64496:4294967295:2, 64496:0:0, or (64496, 111, 222).
> """

Option C:

4.  Canonical Representation

   Large BGP Communities SHOULD be represented as three separate
   unsigned integers in decimal notation, separated by a colon, in the
   following order: Global Administrator, Local Data 1, Local Data 2.
   Numbers MUST NOT contain leading zeros; a zero value MUST be
   represented with a single zero. For example: 64496:4294967295:2
   or 64496:0:0.


Option D:

    remove the section and let the market figure it out.

Some might argue "this is a minute detail" - however I do think that the
proliferation of ways to notate extended communities have not really
helped the extended communities effort. this is a good chance and a good
place to shortcut some of that proces and provide guidance.

Option C is basically as watered down as possible. Settle on that and
move on?

Kind regards,

Job