Re: [RTG-DIR] [GROW] Routing Directorate Last Call Review for draft-ietf-grow-bmp-adj-rib-out-05.txt

"Tim Evens (tievens)" <tievens@cisco.com> Thu, 20 June 2019 19:11 UTC

Return-Path: <tievens@cisco.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE5A61200F9; Thu, 20 Jun 2019 12:11:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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=OQKWPErs; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=HthBZkh7
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 dlL8D6Zy21Uw; Thu, 20 Jun 2019 12:11:07 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 474681200B6; Thu, 20 Jun 2019 12:11:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15501; q=dns/txt; s=iport; t=1561057867; x=1562267467; h=from:to:cc:subject:date:message-id:mime-version; bh=oKAXnSrZJBwnKJR2M88yWGUdyOEvm3J+5H/09H/sfv8=; b=OQKWPErsH5Vw90E7rNuqqH1WKxoTM5q1FNxjsEwd3IcE6Sj+CQyrbKwa 40FaNXegy57f8dQc6CG2Oalt4Z+10U5csP+vFfbecKLBNgw2tAZCxNG5k mCRKFeR0J5Xz7V/jSoc8LxdTLO6v//JCuGav1QXZ0OsoET0YrSM4rtubX w=;
IronPort-PHdr: =?us-ascii?q?9a23=3AE522XheKO7suOuehvJA6/RgJlGMj4e+mNxMJ6p?= =?us-ascii?q?chl7NFe7ii+JKnJkHE+PFxlwGRD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFn?= =?us-ascii?q?pnwd4TgxRmBceEDUPhK/u/cy03AslET3du/mqwNg5eH8OtL1A=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DuAACn2Qtd/4QNJK1lHQEBBQEHBQG?= =?us-ascii?q?BVQYBCwGBFC9QA2pVIAQLKIQWg0cDjmKCWZJkhFOBLoEkA1QJAQEBDAEBJQg?= =?us-ascii?q?CAQGEQBmCRyM2Bw4BAwEBBAEBAgEFbYo3DIVLAgQSER0BATcBEQEIFCsDAgQ?= =?us-ascii?q?wFBMEAQ0FIoMAAYEdTQMdAQ6cTQKBOIhfcYExgnkBAQWBR0CCfhiCEQmBNAG?= =?us-ascii?q?EcIZtF4FAP4ERJx+CHi4+gVSBAgsCggENgl0ygiaLfyCCJIR4iE6NagkCghG?= =?us-ascii?q?FblyNEBuCKGqGIYlrhB+NIYEshXuPSgIEAgQFAg4BAQWBPRoJKIFYcBVlAYJ?= =?us-ascii?q?BCYI4N4M5hRSFP3IBgSiOTAEB?=
X-IronPort-AV: E=Sophos;i="5.63,397,1557187200"; d="scan'208,217";a="576796796"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 20 Jun 2019 19:11:05 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by alln-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x5KJB5Qg002555 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 20 Jun 2019 19:11:05 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 20 Jun 2019 14:11:04 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 20 Jun 2019 14:11:04 -0500
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 20 Jun 2019 15:11:04 -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=oKAXnSrZJBwnKJR2M88yWGUdyOEvm3J+5H/09H/sfv8=; b=HthBZkh7FWO1WEQXdOzbbVTp+GScW2ihpf0ikawU5PmfEOAAnILTF4mFVY1K/XIAJK+C592HsFmEom/vaocpJPFbT9sd9IN/B4BiHyRJgcNZ112P8fNFdbWEqKBacUjboSjhmmfF2AcBRo54n7FIMS80wJyqPqhgtO9WK2UL5Fk=
Received: from MWHPR1101MB2319.namprd11.prod.outlook.com (10.174.97.9) by MWHPR1101MB2336.namprd11.prod.outlook.com (10.173.50.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1987.11; Thu, 20 Jun 2019 19:10:54 +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.014; Thu, 20 Jun 2019 19:10:54 +0000
From: "Tim Evens (tievens)" <tievens@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "draft-ietf-grow-bmp-adj-rib-out@ietf.org" <draft-ietf-grow-bmp-adj-rib-out@ietf.org>, "<rtg-ads@ietf.org> (rtg-ads@ietf.org)" <rtg-ads@ietf.org>
CC: Routing Directorate <rtg-dir@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [GROW] Routing Directorate Last Call Review for draft-ietf-grow-bmp-adj-rib-out-05.txt
Thread-Index: AQHVJ5viRpSFZBUJQU+Q6PWS3KtM4g==
Date: Thu, 20 Jun 2019 19:10:54 +0000
Message-ID: <0FCCDEFA-FF65-4B64-B2C5-E639D50CC8F5@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: [2001:420:c0c8:1002::10b]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a4c87390-3587-4451-85a6-08d6f5b304b9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MWHPR1101MB2336;
x-ms-traffictypediagnostic: MWHPR1101MB2336:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <MWHPR1101MB233631479D1DB00B54D57B19B6E40@MWHPR1101MB2336.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0074BBE012
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(346002)(396003)(376002)(366004)(136003)(199004)(189003)(76116006)(66446008)(64756008)(66556008)(91956017)(86362001)(316002)(236005)(7736002)(25786009)(476003)(486006)(8676002)(73956011)(8936002)(66476007)(81156014)(6512007)(33656002)(9326002)(6116002)(66946007)(81166006)(2906002)(36756003)(6306002)(6436002)(5024004)(2616005)(68736007)(6246003)(46003)(6486002)(4326008)(186003)(54896002)(53936002)(2501003)(14444005)(229853002)(5660300002)(6506007)(71190400001)(99286004)(508600001)(256004)(66574012)(110136005)(102836004)(54906003)(53546011)(14454004)(606006)(966005)(71200400001)(450100002); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR1101MB2336; H:MWHPR1101MB2319.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: divAhVN2rc8dNcDGFJs1FNgOILfyfIkZhwjgFQzpMIMp0FnKWvuMYGOpjRG3vLu3ZcVm6i08yv8o7+H6jjHNhQBmGutg1GCkGZvj6/BOmGNg2vlAWgZj+Hj2ALK59bIDAPuFTtbnBuE8yJWb75k+xM6Sj1fY+RTXYpuUStjTo7rGcUf5qaRquHjjjC4oUzsCGhbaluWEyH+q86gK8hgOSwB4mHQ7S6wy5rNFj3oygagHo5MqvRzmreqn2Ph+d1Fz6ep+Vrg2DTs4J3UuJs3FrrF5eMmFPxcg2f0bzzL8LRgMmAW633d3JMExESg5Z5y9k1/YXhX3pYMZUt7Lu/VYQRTxygv56+IFQNrCLYL2T3JwXpEOrWi2JyDIZ2CVu2pf+Ionc0+OcypL6bG9SEbIsZrjqgsxnPq/AdoB0Pdbslk=
Content-Type: multipart/alternative; boundary="_000_0FCCDEFAFF654B64B2C5E639D50CC8F5ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: a4c87390-3587-4451-85a6-08d6f5b304b9
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Jun 2019 19:10:54.5591 (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: MWHPR1101MB2336
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.25, xch-rcd-015.cisco.com
X-Outbound-Node: alln-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/bLsd4fDQLOKCWnnb-mSvrb5G_40>
Subject: Re: [RTG-DIR] [GROW] Routing Directorate Last Call Review for draft-ietf-grow-bmp-adj-rib-out-05.txt
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2019 19:11:11 -0000

Hi Acee,

Thank you so much for the review and diff of changes.  I've made all the requested changes.  We already had the terminology change from the art view.    We'll update the security section based on their review considering they may have some other suggestions.

You can see the changes at https://github.com/TimEvens/draft-ietf-grow-bmp-adj-rib-out/pull/12/files .  After the security review, we should be set to publish the final as revision 6.

Thanks!
Tim


On 6/20/19, 10:11 AM, "GROW on behalf of Acee Lindem (acee)" <grow-bounces@ietf.org<mailto:grow-bounces@ietf.org> on behalf of acee@cisco.com<mailto:acee@cisco.com>> wrote:

Hello,

I have been selected as the Routing Directorate reviewer for this draft. The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review, and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs. For more information about the Routing Directorate, please see ​http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments that you receive, and strive to resolve them through discussion or by updating the draft.

Document: draft-ietf-grow-bmp-adj-rib-out-05.txt
Reviewer: Acee Lindem
Review Date: June 20, 2018
IETF LC End Date: Not started yet.
Intended Status: Standards Track

Summary: The document extends BGP Monitoring Protocol to support per-peer Pre-Policy and Post-Policy Adj-RIB-Out monitoring similar to RFC 7854 support of Adj-RIB-In. The document is ready for publication.

Comments: A well-written clear and concise document.

Major Issues: N/A

Minor Issues:
    Use updated boilerplate text for “Reserved Words”.

    You will be undoubtedly asked to explain why the Adj-RIB-Out support doesn’t add any additional security considerations. However, I’ll leave that the security reviewers so that they can fulfill their divine mandate of securing the Internet.

Nits: See attached diff including Peer Up and Peer Down capitalization consistent with RFC 7854.

Thanks,
Acee