Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT)

heasley <heas@shrubbery.net> Wed, 04 January 2017 15:21 UTC

Return-Path: <heas@shrubbery.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 36FF01294F0; Wed, 4 Jan 2017 07:21:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.302
X-Spam-Level:
X-Spam-Status: No, score=-7.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 DoVHLx9Zv5kM; Wed, 4 Jan 2017 07:21:57 -0800 (PST)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34D37129463; Wed, 4 Jan 2017 07:21:57 -0800 (PST)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id C1DB287538; Wed, 4 Jan 2017 15:21:56 +0000 (UTC)
Date: Wed, 4 Jan 2017 15:21:56 +0000
From: heasley <heas@shrubbery.net>
To: Benoit Claise <bclaise@cisco.com>
Message-ID: <20170104152156.GC21501@shrubbery.net>
References: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <148354156226.13001.17853336045471596840.idtracker@ietfa.amsl.com>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0OvirzRB0IHOMsJ90Ss5-4sB3XY>
Cc: idr@ietf.org, draft-ietf-idr-large-community@ietf.org, The IESG <iesg@ietf.org>, idr-chairs@ietf.org, rick.casarez@gmail.com
Subject: Re: [Idr] Benoit Claise's Discuss on draft-ietf-idr-large-community-11: (with DISCUSS and COMMENT)
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: Wed, 04 Jan 2017 15:21:58 -0000

Wed, Jan 04, 2017 at 06:52:42AM -0800, Benoit Claise:
> I see from the abstract: "The attribute is suitable for use with
> four-octet ASNs."
> I also see this text, which doesn't mention four-octet ASNs
> 
>    The Global Administrator field is intended to allow different
>    Autonomous Systems to define BGP Large Communities without
> collision.
>    This field SHOULD be an Autonomous System Number (ASN), in which
> case
>    the Local Data Parts are to be interpreted as defined by the owner
> of
>    the ASN.  The use of Reserved ASNs (0 [RFC7607], 65535 and
> 4294967295
>    [RFC7300]) is NOT RECOMMENDED.
> 
> What if the ASN is two bytes, we use padding? How?
> Even if we would say: "This field SHOULD be an four-octet Autonomous
> System Number (ASN)", it doesn't preclude inserting a two-octet ASN in
> the Global Administrator field.
> Isn't it better to specify how? 
> 
> >From RFC 6793:
> 
>    Currently assigned two-octet AS numbers are converted into
> four-octet
>    AS numbers by setting the two high-order octets of the four-octet
>    field to zero.  Such a four-octet AS number is said to be mappable
> to
>    a two-octet AS number.

The draft should just reference rfc 6793, which ISTR it once had, though
that version may not have been published.