Re: [Idr] draft-litkowski-idr-bgp-timestamp
"Susan Hares" <shares@ndzh.com> Thu, 24 July 2014 18:50 UTC
Return-Path: <shares@ndzh.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 6A71F1A0AF9 for <idr@ietfa.amsl.com>; Thu, 24 Jul 2014 11:50:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] 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 6DXy2j4M5pWB for <idr@ietfa.amsl.com>; Thu, 24 Jul 2014 11:50:16 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id DBF7E1A0194 for <idr@ietf.org>; Thu, 24 Jul 2014 11:50:15 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=31.133.162.238;
From: Susan Hares <shares@ndzh.com>
To: 'Jon Mitchell' <jrmitche@puck.nether.net>, stephane.litkowski@orange.com
References: <5637_1406056798_53CEB95E_5637_4963_1_9E32478DFA9976438E7A22F69B08FF92044435@OPEXCLILM34.corporate.adroot.infra.ftgroup> <20140722212735.GA11770@puck.nether.net> <25601_1406066454_53CEDF16_25601_752_1_9E32478DFA9976438E7A22F69B08FF9204461C@OPEXCLILM34.corporate.adroot.infra.ftgroup> <20140722222246.GB19654@puck.nether.net>
In-Reply-To: <20140722222246.GB19654@puck.nether.net>
Date: Thu, 24 Jul 2014 14:50:06 -0400
Message-ID: <006a01cfa770$165cccf0$431666d0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF7cNhsKZhrfXZn4jdnN6RtIb/8AQHzVLjSAbWg4sQCToKL9pwoQUrg
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: http://mailarchive.ietf.org/arch/msg/idr/dDLWE-eQj5_oLBuQqO_ig0utwl8
Cc: 'Jeffrey Haas' <jhaas@juniper.net>, 'idr wg' <idr@ietf.org>, 'Robert Raszuk' <robert@raszuk.net>
Subject: Re: [Idr] draft-litkowski-idr-bgp-timestamp
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: Thu, 24 Jul 2014 18:50:18 -0000
Jon and Stephan: Based on work with vendor boxes for the BMWG BGP work - I would recommend you timestamp the BGP trace NLRI as you leave the BGP Peer and as you receive it. Otherwise, you run into the data flow patterns the trace NLRI is included in causing variation in your flows. Sue -----Original Message----- From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Jon Mitchell Sent: Tuesday, July 22, 2014 6:23 PM To: stephane.litkowski@orange.com Cc: Jeffrey Haas; idr wg; Robert Raszuk Subject: Re: [Idr] draft-litkowski-idr-bgp-timestamp On 22/07/14 22:00 +0000, stephane.litkowski@orange.com wrote: > Hi Jon, > > Thanks for your comment. > Regarding packing, depending of the address family you are trying to monitor, current packing may be low or high. In case where existing packing is low, it does not change anything. In case packing is high, yes I agree that the processing of the update is a bit changed and my beacon would be sent may be faster. Packing is introducing slight delay but I don't think delay introduced by packing is a major component expect if an implementation get stucks in packing (it may happen but I never seen it). IMHO, I don't think this is a critical point but I'm open to other opinions. > > Now for BMP, we are not targeting to monitor our beacons on all PEs, just a subset of representative. > Moreover it's not only a question about number of sessions, it's a question of ordering the information retrieved. If you consider using BMP , the tool will peer with selected PEs, but also "transit BGP Speakers" (ASBRs, RRs ...). When the tool will receive the timestamp information (if implementation of BMP supports timestamp), it requires to sort and reorganize the received information based on the knowledge of the topology : you cannot just sort by timestamp, you have to find relationship between BGP Speakers (information from BMP and topology) and combine them to recreate our timestamp vector. BGP transport permits to create automatically this timestamp vector without having to implement a complex machinery in the tool. But BMP can be used at the selected PE to the tool to retrieve timestamp vectors. > Stephane - yes, I think this second point is the real object of the draft (correct me if I'm wrong). Offline correlation engines are complicated to implement and/or expensive, although commercially available. Getting the timestamp data seems not to be the real issue here at all (via BMP or other mechanisms a local implementation can provide). Maybe this point should be more clear in the intro and text. Jon _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr
- [Idr] draft-litkowski-idr-bgp-timestamp stephane.litkowski
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Robert Raszuk
- Re: [Idr] draft-litkowski-idr-bgp-timestamp stephane.litkowski
- Re: [Idr] draft-litkowski-idr-bgp-timestamp stephane.litkowski
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Robert Raszuk
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Robert Raszuk
- Re: [Idr] draft-litkowski-idr-bgp-timestamp stephane.litkowski
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Robert Raszuk
- Re: [Idr] draft-litkowski-idr-bgp-timestamp stephane.litkowski
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Jon Mitchell
- Re: [Idr] draft-litkowski-idr-bgp-timestamp stephane.litkowski
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Jon Mitchell
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Thomas Mangin
- Re: [Idr] draft-litkowski-idr-bgp-timestamp stephane.litkowski
- Re: [Idr] draft-litkowski-idr-bgp-timestamp stephane.litkowski
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Susan Hares
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Robert Raszuk
- Re: [Idr] draft-litkowski-idr-bgp-timestamp stephane.litkowski
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Susan Hares
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Jeffrey Haas
- Re: [Idr] draft-litkowski-idr-bgp-timestamp Jeffrey Haas