Re: [GROW] Value of timestamps in BMP header for rib-out monitoring
Randy Bush <randy@psg.com> Thu, 13 June 2019 17:18 UTC
Return-Path: <randy@psg.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8781812011C; Thu, 13 Jun 2019 10:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=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 pmAOIgyc1cJl; Thu, 13 Jun 2019 10:18:36 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84707120123; Thu, 13 Jun 2019 10:18:36 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1hbTMu-0002Qf-FU; Thu, 13 Jun 2019 17:18:32 +0000
Date: Thu, 13 Jun 2019 10:18:31 -0700
Message-ID: <m2wohpjteg.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Mukul Srivastava <msri=40juniper.net@dmarc.ietf.org>
Cc: "draft-ietf-grow-bmp-adj-rib-out@ietf.org" <draft-ietf-grow-bmp-adj-rib-out@ietf.org>, Jeff Haas <jhaas@juniper.net>, "grow@ietf.org" <grow@ietf.org>
In-Reply-To: <66F6B0D4-1423-467B-AC3F-1723CAA3425A@juniper.net>
References: <66F6B0D4-1423-467B-AC3F-1723CAA3425A@juniper.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.2 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="ISO-2022-JP"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/_7kWvkE4WHcq3N7cQ1AxmTNrFqw>
Subject: Re: [GROW] Value of timestamps in BMP header for rib-out monitoring
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jun 2019 17:18:38 -0000
> Otherwise the definition of “timestamp” would be the same as in RFC > 7854. So, something like this should be added in the for BMP > ADJ-RIB-OUT draft: > > o Timestamp: The time when the encapsulated routes were advertised > (one may also think of this as the time when they were installed > in the Adj-RIB-Out), expressed in seconds and microseconds since > midnight (zero hour), January 1, 1970 (UTC). If zero, the time is > unavailable. Precision of the timestamp is implementation- > dependent. just ref 7854 sec 4.2 Timestamp randy
- [GROW] Value of timestamps in BMP header for rib-… Mukul Srivastava
- Re: [GROW] Value of timestamps in BMP header for … John Scudder
- Re: [GROW] Value of timestamps in BMP header for … Tim Evens (tievens)
- Re: [GROW] Value of timestamps in BMP header for … Mukul Srivastava
- Re: [GROW] Value of timestamps in BMP header for … Randy Bush
- Re: [GROW] Value of timestamps in BMP header for … John Scudder
- Re: [GROW] Value of timestamps in BMP header for … Paolo Lucente