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

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Mon, 24 October 2016 19:11 UTC

Return-Path: <jheitz@cisco.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 ACE151299BB for <idr@ietfa.amsl.com>; Mon, 24 Oct 2016 12:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.952
X-Spam-Level:
X-Spam-Status: No, score=-14.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 qPM9Ay-Yxqq9 for <idr@ietfa.amsl.com>; Mon, 24 Oct 2016 12:11:33 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 234831299B4 for <idr@ietf.org>; Mon, 24 Oct 2016 12:11:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2851; q=dns/txt; s=iport; t=1477336293; x=1478545893; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=+cWLABf8VpAINaQ+J5OdHs/EnCeOB+a0Yz2cXjwF2xE=; b=SNXSYLg52fC5i9x0T1psoOa8Pui60m+V9JwQFr5MPNIkxwnkZE/sEz41 GALTLN4KZSEHuFF0IiUrIz61Zt4aW6QTl6t2UoNzN2nF4TbJzJ81wZ5gm +wI/wB9THtyymAEkQigXyEFdKiICZBwUITaCs11qPoY9qdJiGBL9cLrgs g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BYAQCkXA5Y/4UNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgyoBAQEBAR1YfQcBjSyWfJQ/ggccC4V6AoFoPxQBAgEBAQEBAQF?= =?us-ascii?q?iKIRiAQEBBAEBATc0CwwEAgEIEQQBAQEeCQcnCxQJCAIEAQ0FCAyIPg7BPwEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBARcFhj2DUIEFiiYFmhQBkAuBdYRtiACBJ4p2ghC?= =?us-ascii?q?EAAEeNl6DER8YgTpyh0EBfwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.31,543,1473120000"; d="scan'208";a="338988838"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Oct 2016 19:11:29 +0000
Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u9OJBS5q001820 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 24 Oct 2016 19:11:28 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 24 Oct 2016 14:11:28 -0500
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1210.000; Mon, 24 Oct 2016 14:11:28 -0500
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: heasley <heas@shrubbery.net>, Robert Raszuk <robert@raszuk.net>
Thread-Topic: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)
Thread-Index: AdIotF10Qx6LizvwQ9uItB9ryESdDgANiv0AACybzYAAADoegAAC4vMAAGdvEAAAChhMkAAaOlQAAADNMIAAK3rfgAAC/G6AAG1/BQAAAFTwAAAADk4AAAnd70A=
Date: Mon, 24 Oct 2016 19:11:28 +0000
Message-ID: <ba9ac147753340ecbc7f4a78bd6a2b6b@XCH-ALN-014.cisco.com>
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> <20161024181924.GN86859@shrubbery.net>
In-Reply-To: <20161024181924.GN86859@shrubbery.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [128.107.147.26]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/GPCaJjn9dBv32mgvYS38SWMF63M>
Cc: 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 19:11:35 -0000

This draft provides a 12 byte community.
The meaning of the 12 bytes is to be defined by mutual agreement between the sender and the receiver.
In many cases, a community is confined to within a single AS or between two ASes.
In that case, no further specification from the IETF is necessary.
In the case that a community stays attached to a route while it is propagated to multiple ASes,
we need to specify a little more.
For this case, we recommend that the first 4 bytes contain the ASN that is assigned to the entity that defines the meaning of the other 8 bytes.
In this way, multiple entities can attach communities to the same route without conflict.

There is no source ASN and no target ASN, just the namespace ASN.
I say "entity" and not AS, because an entity that is assigned an ASN does not necessarily use the ASN to construct an AS.


Thanks,
Jakob.


> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of heasley
> Sent: Monday, October 24, 2016 11:19 AM
> To: Robert Raszuk <robert@raszuk.net>;
> 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)
> 
> 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.
> > >
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr