IETF Logo Mail Archive

Re: [GROW] Value of timestamps in BMP header for local-rib monitoring

"Tim Evens (tievens)" <tievens@cisco.com> Thu, 13 June 2019 16:17 UTC

Return-Path: <tievens@cisco.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 9ECF81201C3; Thu, 13 Jun 2019 09:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Wuzcfx0s; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Zz1mkJxd
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 sDWNcKqreZp6; Thu, 13 Jun 2019 09:17:17 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD48C1201DC; Thu, 13 Jun 2019 09:17:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16139; q=dns/txt; s=iport; t=1560442636; x=1561652236; h=from:to:cc:subject:date:message-id:mime-version; bh=CYhfr3u2c0HStME67F1b2x6EhM7HLlXp+1Omu4WyNO8=; b=Wuzcfx0s/gxm2gtsa5w9cbZOd8HTG7PKJifaQ1463VODP6Ujzq4jLaHr PWxzKfa2jJT3bE7j4K7h1uawBScyGgOZkx83nH7/DVnM5+hs6oqnVolmb IOBtNULntkHzkw9YovL3qIvJomqWsduF49aDisRZZdukLtPZiNUf+T79j w=;
IronPort-PHdr: 9a23:cAphhBOmgCb2ocV85akl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu60/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBjnLfP0YiohNM9DT1RiuXq8NBsdFQ==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BNAQCgdQJd/5hdJa1lHAEBAQQBAQcEAQGBVAQBAQsBgQ4vUANqVSAECygKhAyDRwOOYpU3hFOCUgNUCQEBAQwBAS0CAQGEQAIXgjIjNwYOAQMBAQQBAQIBBG0cDIVLAgEDEhEKEwEBNwERAQg/AwIEMBQTBAENBSKDAAGBHU0DHQGfcgKBOIhfcYExgnkBAQWFARiCDwmBNAGLXBeBQD+BEScfgh4uPoJhBIIVglQygiaONYRziEeNYQkCghCTTBuCJpUGjRuBK5UnAgQCBAUCDgEBBYFlIoFYcBVlAYJBgg+DcIpTcgGBKI5rAYEgAQE
X-IronPort-AV: E=Sophos;i="5.63,369,1557187200"; d="scan'208,217";a="354290351"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Jun 2019 16:17:15 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x5DGHDd6010487 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 13 Jun 2019 16:17:15 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 13 Jun 2019 11:17:13 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 13 Jun 2019 12:02:07 -0400
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 13 Jun 2019 12:02:07 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CYhfr3u2c0HStME67F1b2x6EhM7HLlXp+1Omu4WyNO8=; b=Zz1mkJxdO0XbfDP0yjIPJ27sjFrS1q3D34lAkqLxi7op7XvCIhvZ9TCgWAhg7GUax5FrkmjYZRkHsX5HMWq4pE7HMkvPk5XBfuQQdcidOalkqkUnBhEgUo2XoGRdb1JmLH7vfEOd6qNxYmqh7c2IgyhtyvdXEtM0lJLgUS1djdM=
Received: from MWHPR1101MB2319.namprd11.prod.outlook.com (10.174.97.9) by MWHPR1101MB2320.namprd11.prod.outlook.com (10.174.97.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1987.12; Thu, 13 Jun 2019 16:02:05 +0000
Received: from MWHPR1101MB2319.namprd11.prod.outlook.com ([fe80::e925:911c:84b9:3fe5]) by MWHPR1101MB2319.namprd11.prod.outlook.com ([fe80::e925:911c:84b9:3fe5%7]) with mapi id 15.20.1987.013; Thu, 13 Jun 2019 16:02:05 +0000
From: "Tim Evens (tievens)" <tievens@cisco.com>
To: Mukul Srivastava <msri=40juniper.net@dmarc.ietf.org>, "draft-ietf-grow-bmp-local-rib@ietf.org" <draft-ietf-grow-bmp-local-rib@ietf.org>
CC: Jeff Haas <jhaas@juniper.net>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] Value of timestamps in BMP header for local-rib monitoring
Thread-Index: AQHVIgFYAutrV0MtrkOyHH+Z1+NzVA==
Date: Thu, 13 Jun 2019 16:02:05 +0000
Message-ID: <ACCCEC80-09BF-4E68-BB1F-0F39EC5C5AF3@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=tievens@cisco.com;
x-originating-ip: [128.107.241.178]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d97c46d3-1efe-4cd5-18e7-08d6f0187b65
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MWHPR1101MB2320;
x-ms-traffictypediagnostic: MWHPR1101MB2320:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MWHPR1101MB23207BBF81760250133E4929B6EF0@MWHPR1101MB2320.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0067A8BA2A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39860400002)(366004)(136003)(376002)(346002)(189003)(199004)(53754006)(86362001)(66066001)(36756003)(71190400001)(71200400001)(14444005)(256004)(4326008)(25786009)(5660300002)(26005)(102836004)(186003)(99286004)(110136005)(54906003)(6506007)(316002)(66446008)(53936002)(7736002)(68736007)(2906002)(2501003)(6436002)(6306002)(236005)(6512007)(54896002)(66556008)(66946007)(73956011)(6486002)(14454004)(76116006)(91956017)(66476007)(64756008)(8936002)(81166006)(81156014)(8676002)(478600001)(3846002)(6116002)(229853002)(6246003)(561944003)(33656002)(486006)(2616005)(476003); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR1101MB2320; H:MWHPR1101MB2319.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: EQz6WrYtsSNlVeOWDjBMEamHPJmA20v1hAH4TDZ0sHaM99B10dtDQRKSITbknsbAWk4IzGx4Na/j1MzV/umM0yfW44N06Fv3kFkvFUGCkOkVvTFtgCkka+ZxkYVrYMdIlhgyEDeA3Ul+u617bw/+4YbqxC86GrS3py2rYZT4RJnv+mpaztU2BemO2c09aId9VKk1urwQ2IS7o8DJ33dTSxxcs0hJIepGgohkKqPr0SiYkaWSrIQdYqfztov4PYJe6oTNfk4UMvUJfcaPA7k7Wy5Z/T2+c7ORNUDrzlvME9nuSi74nfGqCM8R6gVu/dQM9wS/pwxUjnbS5pPR7claSUj6rJJ3EsjNjC6AOdp/vjKSDWW8unZszCSSrO2aOI43IEO0+udWT/aothrKFeLQ67j+oNOd0z6wUF6bqXdVo3s=
Content-Type: multipart/alternative; boundary="_000_ACCCEC8009BF4E68BB1F0F39EC5C5AF3ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d97c46d3-1efe-4cd5-18e7-08d6f0187b65
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jun 2019 16:02:05.9037 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: tievens@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR1101MB2320
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/TEitf5ooE4oqCPJwz4G6BbQJxmU>
Subject: Re: [GROW] Value of timestamps in BMP header for local-rib 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 16:17:20 -0000

Thanks Mukul. I'll also update this one as noted.

On 6/13/19, 8:16 AM, "GROW on behalf of Mukul Srivastava" <grow-bounces@ietf.org<mailto:grow-bounces@ietf.org> on behalf of msri=40juniper.net@dmarc.ietf.org<mailto:msri=40juniper.net@dmarc.ietf.org>> wrote:

Hi All

The current BMP Local-RIb draft doesn’t define what timestamp should be used in Per-Peer header for BMP local RIB monitoring.

BMP RFC 7854 defines “Timestamp” in Per-Peer header as below:

Timestamp: The time when the encapsulated routes were received(one may also think of this as the time when they were installed in the Adj-RIB-In), 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.

The above timestamp use doesn’t make much sense for local RIB monitoring case.

Proposal:
1.      Since local RIB is not specific to a peer, the time stamp could be the time when BMP RM message was created or sent to BMP collector.
2.      Another option would be that the timestamp value be the time when this prefix was installed in local RIB.

Otherwise the definition of “timestamp” would be the same as in RFC 7854. So, something like this:

   o  Timestamp: The time when the encapsulated routes were installed in
      The Loc-RIB, 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.
Thanks
Mukul

v2.23.0 | Report a Bug | By Email