Re: [bmwg] draft-litkowski-idr-bgp-timestamp-01.txt
<stephane.litkowski@orange.com> Tue, 17 March 2015 23:57 UTC
Return-Path: <stephane.litkowski@orange.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DDBD1A1B96 for <bmwg@ietfa.amsl.com>; Tue, 17 Mar 2015 16:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 n4HIo08uM7P2 for <bmwg@ietfa.amsl.com>; Tue, 17 Mar 2015 16:57:08 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB4421A1B1C for <bmwg@ietf.org>; Tue, 17 Mar 2015 16:57:07 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 3BAD918C172 for <bmwg@ietf.org>; Wed, 18 Mar 2015 00:57:06 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.16]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 2010C238061 for <bmwg@ietf.org>; Wed, 18 Mar 2015 00:57:06 +0100 (CET)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([10.114.31.16]) with mapi id 14.03.0224.002; Wed, 18 Mar 2015 00:57:06 +0100
From: stephane.litkowski@orange.com
To: "bmwg@ietf.org" <bmwg@ietf.org>
Thread-Topic: draft-litkowski-idr-bgp-timestamp-01.txt
Thread-Index: AdBXZaIjVJq4l2dLR1e0MeCs29yAsgJqDawg
Date: Tue, 17 Mar 2015 23:57:04 +0000
Message-ID: <16788_1426636626_5508BF52_16788_493_1_9E32478DFA9976438E7A22F69B08FF9216616066@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <21602_1425574821_54F88BA5_21602_1733_1_9E32478DFA9976438E7A22F69B08FF9215C3A1A3@OPEXCLILM34.corporate.adroot.infra.ftgroup>
In-Reply-To: <21602_1425574821_54F88BA5_21602_1733_1_9E32478DFA9976438E7A22F69B08FF9215C3A1A3@OPEXCLILM34.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.12.16.112421
Archived-At: <http://mailarchive.ietf.org/arch/msg/bmwg/4tUTp_IGf37bJILlpDg_JnKn3X0>
Subject: Re: [bmwg] draft-litkowski-idr-bgp-timestamp-01.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bmwg/>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2015 23:57:11 -0000
Hi Folks, I would really appreciate your feedback on this IDR draft proposal. http://www.ietf.org/internet-drafts/draft-litkowski-idr-bgp-timestamp-01.txt Thanks, Stephane -----Original Message----- From: bmwg [mailto:bmwg-bounces@ietf.org] On Behalf Of stephane.litkowski@orange.com Sent: Thursday, March 05, 2015 18:00 To: bmwg@ietf.org Subject: [bmwg] draft-litkowski-idr-bgp-timestamp-01.txt Hi BMWG Folks, I'm currently try to work on a solution to monitor propagation time within a BGP controlplane. You will find below a draft reference. I'm looking for your feedback on the proposed solution especially on it's accuracy. Thanks in advance, Stephane -----Original Message----- From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] Sent: Thursday, March 05, 2015 17:58 To: Jeffrey Haas; LITKOWSKI Stephane SCE/IBNF; Keyur Patel; Keyur Patel; Jeff Haas; LITKOWSKI Stephane SCE/IBNF Subject: New Version Notification for draft-litkowski-idr-bgp-timestamp-01.txt A new version of I-D, draft-litkowski-idr-bgp-timestamp-01.txt has been successfully submitted by Stephane Litkowski and posted to the IETF repository. Name: draft-litkowski-idr-bgp-timestamp Revision: 01 Title: Timestamp support for BGP paths Document date: 2015-03-05 Group: Individual Submission Pages: 26 URL: http://www.ietf.org/internet-drafts/draft-litkowski-idr-bgp-timestamp-01.txt Status: https://datatracker.ietf.org/doc/draft-litkowski-idr-bgp-timestamp/ Htmlized: http://tools.ietf.org/html/draft-litkowski-idr-bgp-timestamp-01 Diff: http://www.ietf.org/rfcdiff?url2=draft-litkowski-idr-bgp-timestamp-01 Abstract: BGP is more and more used to transport routing information for critical services. Some BGP updates may be critical to be received as fast as possible : for example, in a layer 3 VPN scenario where a dual-attached site is loosing primary connection, the BGP withdraw message should be propagated as fast as possible to restore the service. The same criticity exists for other address-families like multicast VPNs where "join" messages should also be propagated very fast. Experience of service providers shows that BGP path propagation time may vary depending on network conditions (especially load of BGP speaker on the path) and too long propagation time are affecting customer service. It is important for service providers to keep track of BGP updates propagation time to monitor quality of service for the customers. It is also important to be able to identify BGP Speakers that are slowing down the propagation. This document presents a solution to transport timestamps of a BGP path. The solution is targeted to be used using special identified beacon prefixes that are single-homed. 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 _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ bmwg mailing list bmwg@ietf.org https://www.ietf.org/mailman/listinfo/bmwg _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
- Re: [bmwg] draft-litkowski-idr-bgp-timestamp-01.t… stephane.litkowski
- [bmwg] draft-litkowski-idr-bgp-timestamp-01.txt stephane.litkowski