IETF Logo Mail Archive

Re: [Idr] I-D Action: draft-ietf-idr-large-community-01.txt

Job Snijders <job@ntt.net> Mon, 03 October 2016 16:57 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 6B106129420 for <idr@ietfa.amsl.com>; Mon, 3 Oct 2016 09:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.931
X-Spam-Level:
X-Spam-Status: No, score=-4.931 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, 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 Omn6HHcEh4Ix for <idr@ietfa.amsl.com>; Mon, 3 Oct 2016 09:57:11 -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 4329A129405 for <idr@ietf.org>; Mon, 3 Oct 2016 09:57:11 -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 1br6Y9-000Dgk-7K (job@us.ntt.net); Mon, 03 Oct 2016 16:57:09 +0000
Date: Mon, 03 Oct 2016 18:57:06 +0200
From: Job Snijders <job@ntt.net>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
Message-ID: <20161003165706.GM20697@Vurt.local>
References: <147531113077.4216.12599976309263776317.idtracker@ietfa.amsl.com> <20161001085434.GW20697@Vurt.local> <005b01d21d58$aaf869e0$4001a8c0@gateway.2wire.net> <20161003095936.GC20697@Vurt.local> <04cf01d21d68$52c656a0$4001a8c0@gateway.2wire.net> <20161003115723.GD20697@Vurt.local> <57F27D3F.7090404@foobar.org> <74D0D4D0-0885-4E11-BDAB-85F9356B4AA1@cisco.com> <20161003161608.GG3127@Vurt.local> <D5115E3C-371A-4397-B8EB-090CE6B5A4F1@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <D5115E3C-371A-4397-B8EB-090CE6B5A4F1@cisco.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.0 (2016-08-17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/1AhI-Pef_pH-3H87sqMQ5oCxUxg>
Cc: "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-large-community-01.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: Mon, 03 Oct 2016 16:57:15 -0000

On Mon, Oct 03, 2016 at 04:53:14PM +0000, Jakob Heitz (jheitz) wrote:
> I write code. I watch people write code and test code. It adds to
> development time. 3 ranges is not necessary. It's messy.

As an implementor, you are not supposed to do anything with these
ranges0. They are just reserved in the sense that they belong to IANA,
not to a single operator. For the moment, operators should avoid using
values from these ranges, but implementations shouldn't prohibit them
from doing so.

This is no different than RFC1997 which reserves the following two:

    0x00000000 - 0x0000FFFF
    0xFFFF0000 - 0xFFFFFFFF

Can you elaborate on whether IOS XR treats RFC1997 values from those
ranges in a special way? (aside from the well known communities
ofcourse)

Kind regards,

Job

v2.23.0 | Report a Bug | By Email