Re: [Idr] RFC 8092 on BGP Large Communities Attribute

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Thu, 16 February 2017 22:56 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 CC37912955E for <idr@ietfa.amsl.com>; Thu, 16 Feb 2017 14:56:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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.001, SPF_HELO_PASS=-0.001, 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 sh5yVx4BhoP9 for <idr@ietfa.amsl.com>; Thu, 16 Feb 2017 14:56:17 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36C5F129526 for <idr@ietf.org>; Thu, 16 Feb 2017 14:56:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3060; q=dns/txt; s=iport; t=1487285777; x=1488495377; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=g7s6lgj45rjNe6RGme/pzJf4h+WkeNKo68XdICq2spY=; b=Dh3cqpCf4jzHVUd9Y0ylLowkp9Yq8eSIDgER2SaNxmewf3tvbAHnjLXI h+MK9zt4fhDSkCPRmZWprAn4dGcKPYdMMuzQ/03xOeyluONDZiNDdQkw8 8bQey0ZofUpfw5wA6pAyVubSb4Y2AwD60VtOvpePX0Xh3rZ+uY/UHwHxG g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AVAQBlLaZY/5FdJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1FhgQkHjVqSD4gLjSiCDB8LhXgCghA/GAECAQEBAQEBAWIdC4R?= =?us-ascii?q?wAQEBBAEBOBQgFwQCAQgRAwEBAQ0SCQchBgoBFAkIAgQTCAwHAgSJMwMVDrJ+h?= =?us-ascii?q?zUNhBMBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYZMhG+BPIEVgWSGBAWVXIVpOgG?= =?us-ascii?q?Gb4cNhBGCBIUXiXSILYIKiGABHziBAFEVGCWERh2BYXWICYEhAYEMAQEB?=
X-IronPort-AV: E=Sophos;i="5.35,169,1484006400"; d="scan'208";a="386529745"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Feb 2017 22:56:16 +0000
Received: from XCH-ALN-013.cisco.com (xch-aln-013.cisco.com [173.36.7.23]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v1GMuG1e016566 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <idr@ietf.org>; Thu, 16 Feb 2017 22:56:16 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-013.cisco.com (173.36.7.23) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 16:56:15 -0600
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, 16 Feb 2017 16:56:15 -0600
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] RFC 8092 on BGP Large Communities Attribute
Thread-Index: AQHSiII65xve03/AI0WS9de5gqZeQqFsPngQ
Date: Thu, 16 Feb 2017 22:56:15 +0000
Message-ID: <23f1de27c8b24920acc4fbd1e2114ce6@XCH-ALN-014.cisco.com>
References: <20170216182349.DE675B8151F@rfc-editor.org>
In-Reply-To: <20170216182349.DE675B8151F@rfc-editor.org>
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.33]
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/-0G4GZHzZs8LzB1ZP7Ma1UYtIx4>
Subject: Re: [Idr] RFC 8092 on BGP Large Communities Attribute
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, 16 Feb 2017 22:56:19 -0000

Thanks to all supporters,

Jakob.

> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of rfc-editor@rfc-editor.org
> Sent: Thursday, February 16, 2017 10:24 AM
> To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
> Cc: drafts-update-ref@iana.org; idr@ietf.org; rfc-editor@rfc-editor.org
> Subject: [Idr] RFC 8092 on BGP Large Communities Attribute
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 8092
> 
>         Title:      BGP Large Communities Attribute
>         Author:     J. Heitz, Ed.,
>                     J. Snijders, Ed.,
>                     K. Patel,
>                     I. Bagdonas,
>                     N. Hilliard
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       February 2017
>         Mailbox:    jheitz@cisco.com,
>                     job@ntt.net,
>                     keyur@arrcus.com,
>                     ibagdona.ietf@gmail.com,
>                     nick@inex.ie
>         Pages:      8
>         Characters: 15979
>         Updates/Obsoletes/SeeAlso:   None
> 
>         I-D Tag:    draft-ietf-idr-large-community-12.txt
> 
>         URL:        https://www.rfc-editor.org/info/rfc8092
> 
>         DOI:        10.17487/RFC8092
> 
> This document describes the BGP Large Communities attribute, an
> extension to BGP-4.  This attribute provides a mechanism to signal
> opaque information within separate namespaces to aid in routing
> management.  The attribute is suitable for use with all Autonomous
> System Numbers (ASNs) including four-octet ASNs.
> 
> This document is a product of the Inter-Domain Routing Working Group of the IETF.
> 
> This is now a Proposed Standard.
> 
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
> standardization state and status of this protocol.  Distribution of this
> memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://www.ietf.org/mailman/listinfo/ietf-announce
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
> 
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr