[Idr] New Version Notification for draft-raszuk-idr-bgp-pr-00.txt
Robert Raszuk <robert@raszuk.net> Wed, 23 July 2014 22:17 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 BFEDE1B281A for <idr@ietfa.amsl.com>; Wed, 23 Jul 2014 15:17:20 -0700 (PDT)
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 GgElrehFN4qA for <idr@ietfa.amsl.com>; Wed, 23 Jul 2014 15:17:19 -0700 (PDT)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AD1E1A0324 for <idr@ietf.org>; Wed, 23 Jul 2014 15:17:19 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id rl12so1581173iec.15 for <idr@ietf.org>; Wed, 23 Jul 2014 15:17:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=7S8sr5Qo803t0YvBqOwPfcy+l8RtWdgRLwPeTgDOxUI=; b=HJ3XQnr14E5w7SjSKX3Eipx8T3HOynmncMCLLKCQj0KnfHug3/K1br5tPjGkDx8I0P SItFRu9S7s8AxwK/8Y0K/S7sUqUjln3SdYypE6lxMMSjlSPtbggmwZ4IA6btc+k0FRoS HJS9ozRvwuvBA26wOGc55Z+2k05nNqL5tDG6ZK1/62l3QgcvwuS4olfYkYZvhF1WGoem tj7B5/TkLBffNb1wvcPnq0SBcUgGho/DDW655REiFssP13DUNMtjOsm0hbH5mg0QosyY +J8bQ90/hWCBlhUeDuuEYE2bYtJoAGGni7dvTQhcXIarat5MY0Wy5eEpceLQmQZWZXbV XJNw==
MIME-Version: 1.0
X-Received: by 10.50.88.37 with SMTP id bd5mr55128697igb.1.1406153838255; Wed, 23 Jul 2014 15:17:18 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.64.128.99 with HTTP; Wed, 23 Jul 2014 15:17:18 -0700 (PDT)
Date: Thu, 24 Jul 2014 00:17:18 +0200
X-Google-Sender-Auth: nh5MWwl0yV2sfuoAiOfEZBEAa0Y
Message-ID: <CA+b+ER=joKJM9E-hFGjZMOB==OigWajs3S9L2XXA0WUC_4TDGw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: idr wg <idr@ietf.org>
Content-Type: multipart/alternative; boundary="089e011777ff07676f04fee3b407"
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/BOXNNHa5cOrtVnfsOrdPlvSY0WQ
Subject: [Idr] New Version Notification for draft-raszuk-idr-bgp-pr-00.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: Wed, 23 Jul 2014 22:17:20 -0000
Hello, Based on the Monday's IDR WG meeting and in particular two presentations recommending collection of two different data sets from transit BGP speakers I took a moment today to write up a short proposal for more general encoding format to accommodate such collection and propagation. In fact as there is more useful operational information to be collected from BGP speakers instead of defining new BGP attribute for each such data type I propose a single structured attribute of BGP Path Record. Another benefit is to help any future proposals to focus on their specific application needs and definition of data to be carried without worry about the envelope it will be placed within. Suggested sub-TLVs in the document are optional and it is to the WG input if those proposed get WG consensus or that perhaps more sub-TLVs of BGP Hop TLV will be suggested for inclusion. Comments and feedback is very welcome ;) Best regards, Robert Raszuk. - - - A new version of I-D, draft-raszuk-idr-bgp-pr-00.txt has been successfully submitted by Robert Raszuk and posted to the IETF repository. Name: draft-raszuk-idr-bgp-pr Revision: 00 Title: BGP Path Record Attribute Document date: 2014-07-23 Group: Individual Submission Pages: 10 URL: http://www.ietf.org/internet-drafts/draft-raszuk-idr-bgp-pr-00.txt Status: https://datatracker.ietf.org/doc/draft-raszuk-idr-bgp-pr/ Htmlized: http://tools.ietf.org/html/draft-raszuk-idr-bgp-pr-00 Abstract: BGP protocol today contains number of build in mechanisms which record critical for its loop free operation data along the path of BGP message propagation. Those are encoded in AS_PATH, CLUSTER_LIST or ORIGINATOR_ID attributes. However in the same time there is no provisioning to record other useful information along the path which can be helpful to the operator in order to enhance end to end visibility of BGP control plane. In order to solve this problem this document proposes a new single BGP attribute designed as an generic and extensible container to carry number of new optional information corresponding to the BGP speakers given BGP advertisement (or withdraw) message traverses. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat
- [Idr] New Version Notification for draft-raszuk-i… Robert Raszuk