IETF Logo Mail Archive

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

Mukul Srivastava <msri@juniper.net> Thu, 13 June 2019 15:16 UTC

Return-Path: <msri@juniper.net>
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 73F88120410; Thu, 13 Jun 2019 08:16:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level:
X-Spam-Status: No, score=-2.709 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_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 R3Dw6HZaDxdK; Thu, 13 Jun 2019 08:16:34 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 D5FFB1203FA; Thu, 13 Jun 2019 08:16:22 -0700 (PDT)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x5DF3f10008707; Thu, 13 Jun 2019 08:16:21 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : content-type : mime-version; s=PPS1017; bh=9xCZUnvJZIRH0L4LSHiRjGP3fwVFzHXmblrcTxPaRd0=; b=cGS2QNohaJjs9p2HeTjDRh4GoDzd1jbYnztdtse7aavMhsbGjPecL2OfHu4YqTs/j599 E8x5z31uucAk2OH50h6ewmOPSn0X1X7mq+0CCUY7yJs+/xU+JRIW+U7GYPn8YT7j4bPa UCdeUrQmH8MJejivcIz9RT202yQqSwkghtzpau0j7G3E6EH8zZo0eNq7FBSkmZWsVHji fUAofolP7e00ivTxi98H9scAZWQh0w6WCRoJ0G2utKdtagjDDg1z2KIEOLoTMN/6yJts C4wY1BuWHQk9DWNcDsMwA+IgLV40m8qZeW8iGCxGvw3yt5EXPBlEnqgt8b0GYz8oZskr AQ==
Received: from nam05-by2-obe.outbound.protection.outlook.com (mail-by2nam05lp2054.outbound.protection.outlook.com [104.47.50.54]) by mx0b-00273201.pphosted.com with ESMTP id 2t3k0pgm8h-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 13 Jun 2019 08:16:21 -0700
Received: from BYAPR05MB5350.namprd05.prod.outlook.com (20.177.127.159) by BYAPR05MB4119.namprd05.prod.outlook.com (52.135.199.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1987.10; Thu, 13 Jun 2019 15:16:19 +0000
Received: from BYAPR05MB5350.namprd05.prod.outlook.com ([fe80::892c:289b:c190:762]) by BYAPR05MB5350.namprd05.prod.outlook.com ([fe80::892c:289b:c190:762%6]) with mapi id 15.20.1987.010; Thu, 13 Jun 2019 15:16:19 +0000
From: Mukul Srivastava <msri@juniper.net>
To: "draft-ietf-grow-bmp-local-rib@ietf.org" <draft-ietf-grow-bmp-local-rib@ietf.org>
CC: "grow@ietf.org" <grow@ietf.org>, Jeff Haas <jhaas@juniper.net>, John Scudder <jgs@juniper.net>
Thread-Topic: Value of timestamps in BMP header for local-rib monitoring
Thread-Index: AQHVIfrzOZrvPVFqH0mtWoJKAyXKMA==
Date: Thu, 13 Jun 2019 15:16:19 +0000
Message-ID: <8924AA48-2336-44A5-BEA6-7D77F7440A83@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.17.1.190326
x-originating-ip: [66.129.241.13]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bf1bd4dd-ee26-4be3-64db-08d6f0121643
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:BYAPR05MB4119;
x-ms-traffictypediagnostic: BYAPR05MB4119:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BYAPR05MB4119F294D76F1526D54D4BD5D1EF0@BYAPR05MB4119.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0067A8BA2A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(136003)(346002)(39860400002)(376002)(396003)(53754006)(189003)(199004)(86362001)(3846002)(26005)(73956011)(102836004)(476003)(6436002)(66946007)(486006)(561944003)(36756003)(33656002)(2906002)(6506007)(2616005)(25786009)(66556008)(2351001)(186003)(6116002)(66476007)(5660300002)(5640700003)(4326008)(66446008)(450100002)(99286004)(64756008)(58126008)(6486002)(54906003)(81156014)(81166006)(256004)(68736007)(107886003)(66066001)(2501003)(71200400001)(6512007)(8676002)(53936002)(7736002)(6916009)(478600001)(6306002)(316002)(76116006)(54896002)(8936002)(71190400001)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB4119; H:BYAPR05MB5350.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 8fJnVFeS7vYOl0cpV4KbBjnuAnsHOawJbh26tK7oqUyvQhJrfdeMLp4AwGe2uB4Z8E0dCMcTU6tuYMfqQEyEezcAIZi+iJgziWHSbVWlBy9+v0kf8fuugLY1dcWPtdwNuLFX4tcZMkdsnVNESacllhOGyKR1mGELYLkW66FfcwbTWk2PH3LZ/9YMmGLKWvCnWDwNCQukhFF5xOGfxVaYcakFSGEEILvqrM1X5R71BFD8XuWAon/jXBhpq+nnnVDhik7kjMv8XAYSx29wOGa05XaeuWIbXEtmVv0ZtRkC3Cy7Pq/mWj57jf3L1hkVGJTqLFqXV7RGl8FCNqks0aI20MyRmY8/IwiBApBgQr7wTGzZ/PdEKMXoK8BDOkJggjqf9g1/wVfo4F4HaOHB+33O/FPG3wxy4nVeX3r5GpJhrDQ=
Content-Type: multipart/alternative; boundary="_000_8924AA48233644A5BEA67D77F7440A83junipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: bf1bd4dd-ee26-4be3-64db-08d6f0121643
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jun 2019 15:16:19.1727 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: msri@juniper.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB4119
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-13_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=753 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906130113
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/Zex1QaaO5D63xe94HoivM7cnGWU>
Subject: [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 15:16:39 -0000

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.

  1.  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