IETF Logo Mail Archive

[Idr] Fwd: New Version Notification for draft-raszuk-wide-bgp-communities-05.txt

Robert Raszuk <robert@raszuk.net> Sat, 07 March 2015 23:08 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CF3B1A1A07 for <idr@ietfa.amsl.com>; Sat, 7 Mar 2015 15:08:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 x5G3E6lvGM8b for <idr@ietfa.amsl.com>; Sat, 7 Mar 2015 15:08:46 -0800 (PST)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D27091A1A0B for <idr@ietf.org>; Sat, 7 Mar 2015 15:08:45 -0800 (PST)
Received: by iecvy18 with SMTP id vy18so30308972iec.1 for <idr@ietf.org>; Sat, 07 Mar 2015 15:08:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=/Foq3VPd3c2tEuiL4Lb28X2PriCYhJpT1OFn8rjunZI=; b=h71ZW+6/xLJEi6kZIhYig5EMesuK4waeF0i5eQVTiyBDsPf2lwjFwQ5L5+30A2wI8v Y3iGWz6zj7TNN8CDFPlQLNSs89eZql2swP2MUXzC83ZVXlbslZAO6wSu44mhhk3C2Vbm /flhABgI/+/ifi/FfG6buSa2OkOfhd7TMqGngy5Grnq2WPPHW9aZR0R/uJAW48LlGjW3 lW0RfHd28ls2QYxRRlLskKdH9M3Qgbvj2/MScdkUJvLKj/yUgow4oxtduMGnwvj4Eysd Xo/A7Vray0htz304L5iz9m+wfsU02Ifl6BG6zo177/PyPXd8aqpp2XzPzGPic70vKeUx 1ROg==
MIME-Version: 1.0
X-Received: by 10.42.123.135 with SMTP id s7mr18158556icr.55.1425769725251; Sat, 07 Mar 2015 15:08:45 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.107.136.156 with HTTP; Sat, 7 Mar 2015 15:08:45 -0800 (PST)
In-Reply-To: <20150307225549.18830.9906.idtracker@ietfa.amsl.com>
References: <20150307225549.18830.9906.idtracker@ietfa.amsl.com>
Date: Sun, 08 Mar 2015 00:08:45 +0100
X-Google-Sender-Auth: iYHx9GX-CPrnHZgJpjykeBHKX6w
Message-ID: <CA+b+ERkS_Df-VrUd9w--N3+368TiXrKPK06paUr_oEiDDd4T2Q@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: idr wg <idr@ietf.org>
Content-Type: multipart/alternative; boundary="20cf3010e7a90176d60510bae25c"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/dT-4WOVUL8CLY6gRDTYRwcV7D-c>
Subject: [Idr] Fwd: New Version Notification for draft-raszuk-wide-bgp-communities-05.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 07 Mar 2015 23:08:47 -0000

A new version of I-D, draft-raszuk-wide-bgp-communities-05.txt
has been successfully submitted by Robert Raszuk and posted to the
IETF repository.

Name:           draft-raszuk-wide-bgp-communities
Revision:       05
Title:          Wide BGP Communities Attribute
Document date:  2015-03-06
Group:          Individual Submission
Pages:          23
URL:
http://www.ietf.org/internet-drafts/draft-raszuk-wide-bgp-communities-05.txt
Status:
https://datatracker.ietf.org/doc/draft-raszuk-wide-bgp-communities/
Htmlized:
http://tools.ietf.org/html/draft-raszuk-wide-bgp-communities-05
Diff:
http://www.ietf.org/rfcdiff?url2=draft-raszuk-wide-bgp-communities-05

Abstract:
   Route tagging plays an important role in external BGP [RFC4271]
   relations, in communicating various routing policies between peers.
   It is also a very common best practice among operators to propagate
   various additional information about routes intra-domain.  The most
   common tool used today to attach various information about routes is
   through the use of BGP communities [RFC1997].

   Such information is important to allow BGP speakers to perform some
   mutually agreed actions without the need to maintain a separate
   offline database for each tuple of prefix and associated set of
   action entries.

   This document defines a new encoding which will enhance and simplify
   what can be accomplished today with the use of BGP communities.  The
   most important addition this specification makes over currently
   defined BGP communities is the ability to specify, carry as well as
   use for execution an operator's defined set of parameters.  It also
   provides an extensible platform for any new community encoding needs
   in the future.

The IETF Secretariat

v2.23.0 | Report a Bug | By Email