Re: [RTG-DIR] Rtgdir early review of draft-ietf-idr-capabilities-registry-change-05

John Scudder <jgs@juniper.net> Mon, 14 October 2019 20:20 UTC

Return-Path: <jgs@juniper.net>
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 67AAA1200F7; Mon, 14 Oct 2019 13:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 tWIhKHqD9p_X; Mon, 14 Oct 2019 13:20:37 -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 2AAA8120013; Mon, 14 Oct 2019 13:20:34 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x9EKGCxH015167; Mon, 14 Oct 2019 13:20:31 -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 : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=Fca6zcyxfC8GOngqhF8yowvRuTQrdOX3s2EPipitBB0=; b=qlXRWxVtVXgVaek4fPBWljYtqksibxqJED2fnIiPbZD1yvirO0fhNms1t0tNRgmi5Qji AqZVM9M3KRhMfLxBRcCQiHcKq19rrmX4kQl+9gjszTatvzZ1D83IfawUkhs8eTucuvzg Fift0gbWMQqZ4x1T25O6anWduyruXbJ1pMMGkoK7rZacHUCtEs/0Sm5xSwJq91VlGnv3 aEdR5SHfAvAZNN+86yBc195dfMvEB9Z1m5VN+1dUr5bC+l9F+LHruktoJZpJdZNKIV6P lrU03joOD0UDaIMkmjg3JSkwBFYeh2ZHLDHQ1d2fxT5Hgn8E5ewg0s0oBD2lv0xG5YKt Gg==
Received: from nam01-sn1-obe.outbound.protection.outlook.com (mail-sn1nam01lp2050.outbound.protection.outlook.com [104.47.32.50]) by mx0a-00273201.pphosted.com with ESMTP id 2vmp3brxxv-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 14 Oct 2019 13:20:31 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XPe0sZpWlytTUX96AbejE+lVt5zWvjaSLL5ity2piVJ2CebNYZ2wAGGdAmN6ALL3x8zkV6LuYBR2EzRnPLty/Fry1E0bFxM2PrL21o2NV6sTLFLqGAwtiQzOhwMGrCxuVq6OK8/cMo5ezSGRvErik2iCKKCJF4SxvYLO66GRtV6wszxPjjByP6GhwF0AzQIN84Z/MKx6oJ8gaqFUatcw2vDGgorG5WE8BoCt170iedZ55dDIu4tVxZVip1JbdUpktrHXIYlHYwOiKVo0e4u9K41ui3Fn6asAJBURmKtERJjpgXsI+RPCJK+eR69vj7eYV45tEmWSi3JSr57Kq/9apQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Fca6zcyxfC8GOngqhF8yowvRuTQrdOX3s2EPipitBB0=; b=ogSdb+Ey0KUasCRmW5YstWj9p4GX52DQqaoNcMPFOHQDYqxYnpe8tAA/A1eLh4a2rwulmSB9r7+yE8cnIOyxM0feJZf6CBQMePviTKvlrrACMfFBA1qaO9Bj0xOpdoJHxgWkSVg4YGLcQMjk7HLyFYkdxqdJJOQ5zTyAdzi7MGeBBCsu2buSmgcIdffQXyuqzL3PXyQIeQcP5XompKsfNx0+dlQLMjdPPxbpq9GofztLDqvM1lmHPgcriW2Fcd7hcEuKMdJeTikdn+hVOAOonG58B2eT7q6pH8yJ85oP2JrDQtnuLDpshv+MhCxQudcIwhwuGA/QsZPSQPbxIHVSew==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
Received: from SN6PR05MB4127.namprd05.prod.outlook.com (52.135.66.161) by SN6PR05MB4734.namprd05.prod.outlook.com (52.135.114.220) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.13; Mon, 14 Oct 2019 20:20:29 +0000
Received: from SN6PR05MB4127.namprd05.prod.outlook.com ([fe80::dc00:b7dc:752b:d0cb]) by SN6PR05MB4127.namprd05.prod.outlook.com ([fe80::dc00:b7dc:752b:d0cb%3]) with mapi id 15.20.2347.023; Mon, 14 Oct 2019 20:20:29 +0000
From: John Scudder <jgs@juniper.net>
To: Christian Hopps <chopps@chopps.org>
CC: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-idr-capabilities-registry-change.all@ietf.org" <draft-ietf-idr-capabilities-registry-change.all@ietf.org>
Thread-Topic: Rtgdir early review of draft-ietf-idr-capabilities-registry-change-05
Thread-Index: AQHVIMZtSX/KX9cUa0KXglwfjCrDqqdbWBYA
Date: Mon, 14 Oct 2019 20:20:29 +0000
Message-ID: <6E7AE9E2-F41C-454D-8A6C-2FDA2828ED83@juniper.net>
References: <156030646312.23122.13759790091066171911@ietfa.amsl.com>
In-Reply-To: <156030646312.23122.13759790091066171911@ietfa.amsl.com>
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: 52ee9fd7-ffc5-41f9-18d5-08d750e3f4c9
x-ms-office365-filtering-ht: Tenant
x-ms-traffictypediagnostic: SN6PR05MB4734:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <SN6PR05MB473452077498E15AFA46F7B6AA900@SN6PR05MB4734.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:4941;
x-forefront-prvs: 01901B3451
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(376002)(366004)(136003)(396003)(346002)(199004)(189003)(76176011)(66066001)(6916009)(6116002)(186003)(3846002)(6486002)(86362001)(81156014)(91956017)(26005)(966005)(66446008)(64756008)(8676002)(102836004)(66556008)(66476007)(8936002)(81166006)(14454004)(66946007)(229853002)(6436002)(53546011)(6506007)(478600001)(76116006)(71190400001)(71200400001)(476003)(446003)(36756003)(99286004)(2616005)(6246003)(305945005)(486006)(7736002)(14444005)(256004)(2906002)(316002)(25786009)(11346002)(4326008)(54906003)(6512007)(6306002)(5660300002)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR05MB4734; H:SN6PR05MB4127.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 5CJNYh+0P6wthFJ8qSDr4bd5eB2562JrtAgKWxy7ItBAyvO4OgpovBB1h3fwJZ26XWTS7tGOtn7pR6OBjfYfRTXqWl9i0tfqLa8dDDMULay7p58WTjpvkUA0bi61qS5NvhajiQZ/WQHevFRq2OekgQ4GSzZEXbSnf5SKZ9rwnq5HgcglD/hZ2F7ZV3tXyV+x//BiYki4J9QroOg/8PjWagmuj14AhLj8aYrgDv2dlknv5mhxxY2g9ZJSxrpw3qwXAlz3O4b5oBjyQsps+Zul2EsmwFxA18M+rSMor0WqX2FWDQ1kni+syIGdSS96V4ZgXoWICSgYJfYctaNzNago/SXTM2VLEpvJMVpvKJ51u/zPi0TlVOLOEquqbKNSsnI+ez+B5ogzqR+iGVM90C+k8QD7w/K6uHSX2lWN3p/TXpECxMZoWum4aWbCY1sGKvv/eoBcWdQhm5jghpjugLu0kg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <55616D87ADAFE943AE0571A2F9E7453B@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 52ee9fd7-ffc5-41f9-18d5-08d750e3f4c9
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Oct 2019 20:20:29.0222 (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: DrNG1wercyF9sdeDIFMiKZblcUwNgZ608ImVNOZ3KvU5bj3bpAyyP/cwvRMbWkFN
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR05MB4734
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,1.0.8 definitions=2019-10-14_10:2019-10-11,2019-10-14 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 phishscore=0 mlxlogscore=999 clxscore=1011 malwarescore=0 adultscore=0 mlxscore=0 lowpriorityscore=0 suspectscore=0 spamscore=0 impostorscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1908290000 definitions=main-1910140168
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/3CcSpltqzDSEOPzLfE03kJtt3hE>
Subject: Re: [RTG-DIR] Rtgdir early review of draft-ietf-idr-capabilities-registry-change-05
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: Mon, 14 Oct 2019 20:20:40 -0000

Hi Chris,

Sorry I missed replying to this earlier. Regarding your question, I can’t think of any good reason to leave 255 in the registration procedures table, it’s been a while but that was probably just an oversight. Unless there’s an objection I’ll cut another version that removes it, before the RFCEd gets their hands on it.

—John

> On Jun 11, 2019, at 10:27 PM, Christian Hopps via Datatracker <noreply@ietf.org> wrote:
> 
> Reviewer: Christian Hopps
> Review result: Ready
> 
> Hello,
> 
> I have been selected to do a routing directorate “early” review of this draft.
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Didr-2Dcapabilities-2Dregistry-2Dchange_&d=DwIDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=hLt5iDJpw7ukqICc0hoT7A&m=emnUhRbCWwi-JEJUnNgHvn_CfCMgH_znQ785O_rURw0&s=K15OIZP7WxZ_9V-qk_nH0Lz7Pi5JcO0Y5dnQhl1gI5g&e= 
> 
> The routing directorate will, on request from the working group chair, perform
> an “early” review of a draft before it is submitted for publication to the
> IESG. The early review can be performed at any time during the draft’s lifetime
> as a working group document. The purpose of the early review depends on the
> stage that the document has reached.
> 
> As this document is in working group last call, my focus for the review was to
> determine whether the document is ready to be published. Please consider my
> comments along with the other working group last call comments.
> 
> For more information about the Routing Directorate, please see
> ​https://urldefense.proofpoint.com/v2/url?u=http-3A__trac.tools.ietf.org_area_rtg_trac_wiki_RtgDir&d=DwIDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=hLt5iDJpw7ukqICc0hoT7A&m=emnUhRbCWwi-JEJUnNgHvn_CfCMgH_znQ785O_rURw0&s=hYSD0PeieyP2Bgm2hMkUHV1t6o8WSP0eRXnbr1Op714&e= 
> 
> Document: draft-ietf-idr-capabilities-registry-change-05.txt
> Reviewer: Christian Hopps
> Review Date: June 11, 2019
> Intended Status: Standards Track
> 
> Summary:
> 
> No issues found. This documents is ready to proceed to the IESG.
> 
> Comments:
> 
> The draft is very readable, and ready for publication.
> 
> For my own curiosity: while perusing the per revision changes, I saw "0 -
> Reserved" was added then removed from the registration procedures table, but
> "255 - Reserved" was left in. I figure "0" was removed b/c it's not a range and
> it is reserved in the actual capability registry; however, why wouldn't this
> logic then also apply to "255"?
> 
> Thanks,
> Chris.
> 
>