IETF Logo Mail Archive

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

John Scudder <jgs@juniper.net> Thu, 13 June 2019 13:32 UTC

Return-Path: <jgs@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 A68011202D2; Thu, 13 Jun 2019 06:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.708
X-Spam-Level:
X-Spam-Status: No, score=-2.708 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, URIBL_BLOCKED=0.001] 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 wCSq2dXyqfmz; Thu, 13 Jun 2019 06:32:49 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 6E2FB120298; Thu, 13 Jun 2019 06:32:49 -0700 (PDT)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x5DDTcKO005324; Thu, 13 Jun 2019 06:32:48 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=zv70bNy5k4FVRUvMJreeDycUwDjgARDZBneTjOU9TUg=; b=1v3Sjh4CTmtVoaI8sZWxiGtYnSpJpAQVJ06bu8dvBsTxaWcM5MlzsOxvxYtrqXKsZVVr xbFDYMkoDaQZ6zQekCKjZpp7s+Kr8dapKPJ0KbF/H1GJ4jz4W7FCqT30aj2178QzE6hz 9IyIDdjJKTqo0/WV7FafvGap9yNUUu43F43z3nC1Iu2ktWyPYHjbqtTKZbzulqYzw3lY 71bFTYtKuFoDEPtbFw40iTlGMoggy6ut9wEOl9cLNfgGCA4uvpXEpyGbq69WAiwRwaG4 i6F/+w2J7YuyhB2zsX+ZGP96ETRUi9Hf+JxPSPZznRpQ7Ork0F3zGdOi7/42BZfsVXzW Vg==
Received: from nam01-sn1-obe.outbound.protection.outlook.com (mail-sn1nam01lp2059.outbound.protection.outlook.com [104.47.32.59]) by mx0a-00273201.pphosted.com with ESMTP id 2t3p6vr4a3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 13 Jun 2019 06:32:48 -0700
Received: from DM6PR05MB4714.namprd05.prod.outlook.com (20.176.109.215) by DM6PR05MB4460.namprd05.prod.outlook.com (20.176.79.17) 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 13:32:47 +0000
Received: from DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::1549:ffd0:8373:4593]) by DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::1549:ffd0:8373:4593%3]) with mapi id 15.20.2008.006; Thu, 13 Jun 2019 13:32:47 +0000
From: John Scudder <jgs@juniper.net>
To: Mukul Srivastava <msri@juniper.net>
CC: "draft-ietf-grow-bmp-adj-rib-out@ietf.org" <draft-ietf-grow-bmp-adj-rib-out@ietf.org>, "grow@ietf.org" <grow@ietf.org>, Jeff Haas <jhaas@juniper.net>
Thread-Topic: Value of timestamps in BMP header for rib-out monitoring
Thread-Index: AQHVHIIxgmwsDA0sP0OTPXcJeohMKaaZn/QA
Date: Thu, 13 Jun 2019 13:32:47 +0000
Message-ID: <5E10B050-82A9-4DB2-A7C4-270F31E07F5F@juniper.net>
References: <66F6B0D4-1423-467B-AC3F-1723CAA3425A@juniper.net>
In-Reply-To: <66F6B0D4-1423-467B-AC3F-1723CAA3425A@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [162.225.191.79]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6376ac5e-cb79-4b2c-3340-08d6f0039f88
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:DM6PR05MB4460;
x-ms-traffictypediagnostic: DM6PR05MB4460:
x-microsoft-antispam-prvs: <DM6PR05MB44603FC3DD2BDE2B67FC5D68AAEF0@DM6PR05MB4460.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 0067A8BA2A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(366004)(396003)(39860400002)(346002)(136003)(189003)(199004)(53754006)(14454004)(66446008)(53546011)(6512007)(33656002)(54896002)(6246003)(450100002)(6486002)(37006003)(4326008)(66556008)(8936002)(81156014)(107886003)(66476007)(478600001)(8676002)(2906002)(316002)(476003)(6436002)(11346002)(81166006)(2616005)(66066001)(6636002)(54906003)(6862004)(6116002)(5660300002)(486006)(76116006)(66946007)(446003)(53936002)(64756008)(236005)(229853002)(99286004)(7736002)(1941001)(3846002)(256004)(71200400001)(86362001)(25786009)(36756003)(186003)(26005)(68736007)(73956011)(6506007)(71190400001)(76176011)(102836004); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB4460; H:DM6PR05MB4714.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: LRZVEeGRYCjeozVz7QBo5apFjU9yY/QF1Oxttls5LaF54C5RW35Ixu5Sj+9iwBQ5DgNNlgNbDTkl3mT0G8j2pwR9NtV9QzTol9aToXTR7fuTFxW51MDZewNV6Vxmiu2W/6untK4K90f8dWvHvx0onE6dkeYsnUqhXmuXLSWMU90Gg5+4oLhg9UBxKYtshaV0nPkTOTMsWe7QPj7eYUbdnZiP6P3aoq6v5YhYXm7zfVV7eDgUL+bMx6Gh7TOnsi1jZajRPZajl4PnV+NkGYhAS9gBZ1MCY73umfDFJdwtsxX/oWqawxqkfHlgUZkoeyvJVxXS4BBkX38gYlWtK4sGdwvt6fjwyNET+TDgZvvcpHMtpNbebOxAfXDcbMmLuchyrljAFL22wmpiSbF+iv74abzGtNvwTCEoE3KQVf1G5W8=
Content-Type: multipart/alternative; boundary="_000_5E10B05082A94DB2A7C4270F31E07F5Fjunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 6376ac5e-cb79-4b2c-3340-08d6f0039f88
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jun 2019 13:32:47.0765 (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: jgs@juniper.net
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB4460
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-13_08:, , 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=990 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906130103
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/QWxoVWPCNv_sxdlnGKHkBp77eQ4>
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 13:32:52 -0000

This makes sense to me, thanks.

—John

On Jun 13, 2019, at 9:17 AM, Mukul Srivastava <msri@juniper.net<mailto:msri@juniper.net>> wrote:

Hi All

The current BMP Adj-RIB-Out draft doesn’t define what timestamp should be used in Per-Peer header for BMP ADJ-RIB-OUT 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 Adj-RIB-Out case. A better value for timestamp, would be the time when a prefix was advertised to a peer. Collector can use this time stamp to get some sense of “when a given prefix was advertised to a peer”.

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.

Thanks
Mukul

v2.23.0 | Report a Bug | By Email