Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)

heasley <heas@shrubbery.net> Mon, 24 October 2016 18:19 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 AF78E1298CE for <idr@ietfa.amsl.com>; Mon, 24 Oct 2016 11:19:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.633
X-Spam-Level:
X-Spam-Status: No, score=-4.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.431, 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 qEi7XIuwhVFc for <idr@ietfa.amsl.com>; Mon, 24 Oct 2016 11:19:24 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id B73CB129973 for <idr@ietf.org>; Mon, 24 Oct 2016 11:19:24 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 955EA58F12; Mon, 24 Oct 2016 18:19:24 +0000 (UTC)
Date: Mon, 24 Oct 2016 18:19:24 +0000
From: heasley <heas@shrubbery.net>
To: Robert Raszuk <robert@raszuk.net>
Message-ID: <20161024181924.GN86859@shrubbery.net>
References: <20161018191521.GT95811@Vurt.local> <9EFC9BAA-F917-4C70-A139-1F69CAECF9C0@pfrc.org> <20161020215938.GE1074@Vurt.local> <adb00bcd7b8e45db857eae7019c646fc@XCH-ALN-014.cisco.com> <ae5da282-201c-f745-9f26-67ce73826bd5@i3d.net> <CA+b+ERkV2PBtzzx=uoygDzvTyJzunROCNX=0Y4phvGdn=oK5Xw@mail.gmail.com> <20161022122735.GC79185@Space.Net> <CA+b+ERkEMuV7yNKMG-EBUruMEC2E1zSd-ouAaGYaeuMwzpv2SQ@mail.gmail.com> <20161024180818.GL86859@shrubbery.net> <CA+b+ERnhWrDGMi=d8Yi9fHzH=J6T-iQ+24MZE8DDvmXadt00Mw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+b+ERnhWrDGMi=d8Yi9fHzH=J6T-iQ+24MZE8DDvmXadt00Mw@mail.gmail.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/jT4o1DgKXFkOV94rhICUIFLqc1U>
Cc: heasley <heas@shrubbery.net>, IETF IDR WG <idr@ietf.org>, Susan Hares <shares@ndzh.com>
Subject: Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)
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, 24 Oct 2016 18:19:26 -0000

Mon, Oct 24, 2016 at 08:17:48PM +0200, Robert Raszuk:
> You still could do that.
> 
> You overload last octet with exact action you need just like you do today
> with 1997.

Please review the threads associated with -large- to re-discover why that
is not acceptable.

> Three sets of 4 octets with no semantics still requires curret way to
> advertise what action given community means at any target ASN.
> 
> Best,
> R
> 
> Ps. Besides adding 4 more octets to leave current LC as is just to be able
> to avoid anonymous injections seems to me like very little price as
> compared with befit. But I guess am alone with that point of view here.
> 
> On Oct 24, 2016 2:08 PM, "heasley" <heas@shrubbery.net>; wrote:
> 
> > Sat, Oct 22, 2016 at 03:53:05PM +0200, Robert Raszuk:
> > > You are mixing SRC_ASN with TARGET_ASN in the same field.
> >
> > I want to point-out that by forcing the first field to be "src_asn" as
> > you are suggesting, would make one intended use of -large- not possible,
> > for ASN1 to tell ASN2 to do something with a route as it applies to ASN3.
> > eg: ASN2:ASN3:action, ie: apply "action" (such as prepend) defined by ASN2
> > to ASN1's route when advertised to ASN3.
> >
> > > Yes RFC1997 works like that but here we have opportunity to improve it.
> >
> > We have improved it.
> >