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> Thu, 20 October 2016 23:46 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 4107F129630 for <idr@ietfa.amsl.com>; Thu, 20 Oct 2016 16:46:08 -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 fnKS0KnsGkhU for <idr@ietfa.amsl.com>; Thu, 20 Oct 2016 16:46:06 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0466129549 for <idr@ietf.org>; Thu, 20 Oct 2016 16:46:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2824; q=dns/txt; s=iport; t=1477007166; x=1478216766; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Tn63L9j57FLABs2xBB8n+MliumEn5XRfzdXTQmx4TpQ=; b=fXhazUJYLRiViXnQoISbiNWZ7VqPnO0cY+nMoxm2wk52t5de84Bk70G4 2xwTcKrryi1bYiAklED+/YHta0QvaHXKPRfedgn3jISNynBQ90HMIf61e JnkiivPy6dRnlcaPtrvqt7CS/DWTZ508jHl8hDESNpGHg+KJPS0YY/LS5 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AtAQDsVglY/4wNJK1cGQEBAQEBAQEBAQEBBwEBAQEBgz4BAQEBAR1XfQcBjSyWfJQ9gggcC4V6AoF9PxQBAgEBAQEBAQFiKIRiAQEBBAEBATc0CwwEAgEIEQQBAQEeCQcnCxQJCAIEDgUIDIg+DsNiAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWGPYRViiYFmg4BhimJXJACjH+DfwEeNliDBDqBOnKIGQF/AQEB
X-IronPort-AV: E=Sophos;i="5.31,521,1473120000"; d="scan'208";a="159918751"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Oct 2016 23:46:05 +0000
Received: from XCH-ALN-014.cisco.com (xch-aln-014.cisco.com [173.36.7.24]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u9KNk5fu031636 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 20 Oct 2016 23:46:05 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-014.cisco.com (173.36.7.24) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Oct 2016 18:46:04 -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; Thu, 20 Oct 2016 18:46:04 -0500
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: Job Snijders <job@ntt.net>
Thread-Topic: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)
Thread-Index: AdIotF10Qx6LizvwQ9uItB9ryESdDgANiv0AACybzYAAADoegAAC4vMAAGdvEAAAChhMkP//vVQAgABPXBCAAJVk4A==
Date: Thu, 20 Oct 2016 23:46:04 +0000
Message-ID: <2894c1eb263143cc8129ec8e381957dc@XCH-ALN-014.cisco.com>
References: <01f301d228b4$e3319ef0$a994dcd0$@ndzh.com> <20161017215134.GA464@pfrc.org> <20161018190851.GC15392@shrubbery.net> <20161018191521.GT95811@Vurt.local> <9EFC9BAA-F917-4C70-A139-1F69CAECF9C0@pfrc.org> <20161020215938.GE1074@Vurt.local> <adb00bcd7b8e45db857eae7019c646fc@XCH-ALN-014.cisco.com> <20161020225004.GG1074@Vurt.local> <a141faafa05845a1af6417a73aa2f361@XCH-ALN-014.cisco.com>
In-Reply-To: <a141faafa05845a1af6417a73aa2f361@XCH-ALN-014.cisco.com>
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.151.84]
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/UHvuYzkJVOYMyU8GqqsoXpVLzPo>
Cc: heasley <heas@shrubbery.net>, IETF IDR WG <idr@ietf.org>, Sue 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: Thu, 20 Oct 2016 23:46:08 -0000

Perhaps, we should add in an operations section that we should not and will not go any further.
In particular, within an AS and between adjacent BGP neighbors, ANY values will be allowed.
The only requirement is that sender and receiver have the same understanding of the contents,
but no RFC is required to say this.

Thanks,
Jakob.


> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Jakob Heitz (jheitz)
> Sent: Thursday, October 20, 2016 4:06 PM
> To: Job Snijders <job@ntt.net>
> Cc: heasley <heas@shrubbery.net>; Sue Hares <shares@ndzh.com>; IETF IDR WG <idr@ietf.org>
> Subject: Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)
> 
> Evidently, it wasn't clear. Now it is.
> 
> Thanks,
> Jakob.
> 
> 
> > -----Original Message-----
> > From: Job Snijders [mailto:job@ntt.net]
> > Sent: Thursday, October 20, 2016 3:50 PM
> > To: Jakob Heitz (jheitz) <jheitz@cisco.com>
> > Cc: Jeffrey Haas <jhaas@pfrc.org>; heasley <heas@shrubbery.net>; IETF IDR WG <idr@ietf.org>; Sue Hares
> > <shares@ndzh.com>
> > Subject: Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)
> >
> > Hi Jakob,
> >
> > I am not sure what issue this replacement resolves. With the replacement
> > text in the document I feel I have more questions than answers.
> >
> > Usually a community is intended to be sent to one AS to trigger an
> > action, and to multiple ASes if the community is of informative nature.
> > We know we can attach multiple Large BGP Communities to a route, because
> > of the variable length of the attribute.
> >
> > In an earlier response I pointed at text that addresses this specific
> > feature already in the current text: https://mailarchive.ietf.org/arch/msg/idr/_QULjIUDaBB4JqDR8IXuIYkAVJw
> >
> > Kind regards,
> >
> > Job
> >
> >
> > On Thu, Oct 20, 2016 at 10:13:41PM +0000, Jakob Heitz (jheitz) wrote:
> > > In addition, to deal with the values for the GA field, we will replace
> > >
> > >    The Global Administrator field is intended to allow different
> > >    Autonomous Systems to define Large BGP Communities without collision.
> > >
> > > with
> > >
> > >   A Large Community that is intended to be sent to multiple ASes
> > >   SHOULD contain an ASN in the Global Administrator field. The ASN
> > >   SHOULD be one that is assigned to the entity that defines the
> > >   meaning of the rest of the Large Community.  This allows a route to
> > >   carry multiple Large Communities, the meaning of each being defined
> > >   by different independent entities.
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr