IETF Logo Mail Archive

Re: [Idr] Can we eliminate the "IETF Review" Capablities range? [was: Re: I-D Action: draft-ietf-idr-capabilities-registry-change-04.txt]

John Scudder <jgs@juniper.net> Thu, 23 May 2019 18:15 UTC

Return-Path: <jgs@juniper.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B87B112006A for <idr@ietfa.amsl.com>; Thu, 23 May 2019 11:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 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_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 VIiZ-dQPPLtl for <idr@ietfa.amsl.com>; Thu, 23 May 2019 11:15:30 -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 3510B120043 for <idr@ietf.org>; Thu, 23 May 2019 11:15:29 -0700 (PDT)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x4NICdjp027727; Thu, 23 May 2019 11:15:25 -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=MnKad3bRksYCvQ/PItFvx/obxz/MPlAhppTNI/+zfb4=; b=aqnaoZEFiXOPpscmFOqbdSndGm+KjwdiDjld0R4DLo5/XFM/N9cAzUwysopMtGFMmLan 4m3b80EOqAQQDzmAf2ugo6xyiW7nCKlMPVTlceJKTPb84Qyck+PmjSEEtWr18FBFje/K fRnqr/kPP6IRIkc/NZChDIgkKMspz8cUhDdBtzBX7rTFOjbyMR07W/l5vvPxvKiOuVou CBMlswXN3/dk09BnMS0ME2w8j2K8vPeFUGAJS+kJK26rSpd9Pta1GC2VGsrc43I7woFa tLvfXsx3l1R9iDXKtKKkBMhvvwOEKw0Nauz8MHdK2+Ck06MLajND8XuJpNPbZ19H49V9 uQ==
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp2057.outbound.protection.outlook.com [104.47.42.57]) by mx0b-00273201.pphosted.com with ESMTP id 2snwmm0bnx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 23 May 2019 11:15:25 -0700
Received: from DM6PR05MB4714.namprd05.prod.outlook.com (20.176.109.215) by DM6PR05MB4795.namprd05.prod.outlook.com (20.176.111.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.10; Thu, 23 May 2019 18:15:23 +0000
Received: from DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::2835:a395:3945:523a]) by DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::2835:a395:3945:523a%3]) with mapi id 15.20.1922.013; Thu, 23 May 2019 18:15:23 +0000
From: John Scudder <jgs@juniper.net>
To: tom petch <ietfc@btconnect.com>
CC: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Can we eliminate the "IETF Review" Capablities range? [was: Re: I-D Action: draft-ietf-idr-capabilities-registry-change-04.txt]
Thread-Index: AQHVEYU6VT7LjhSaLUml0Fggyq2AHqZ5A+4A
Date: Thu, 23 May 2019 18:15:23 +0000
Message-ID: <2809E7BB-0233-45C4-8597-05FAC6EAA68A@juniper.net>
References: <155860518236.3859.4116481267193969204@ietfa.amsl.com> <F34580D3-0033-45CA-B90A-78A37DE22F9B@juniper.net> <015701d51184$a55712c0$4001a8c0@gateway.2wire.net>
In-Reply-To: <015701d51184$a55712c0$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [116.197.184.14]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 34e3ebf6-3601-459b-5d8a-08d6dfaa9f8c
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(4618075)(2017052603328)(7193020); SRVR:DM6PR05MB4795;
x-ms-traffictypediagnostic: DM6PR05MB4795:
x-microsoft-antispam-prvs: <DM6PR05MB47950CBEEC29037008A44AB8AA010@DM6PR05MB4795.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 00462943DE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(396003)(136003)(39860400002)(346002)(376002)(189003)(199004)(51444003)(6436002)(6486002)(7736002)(91956017)(76116006)(81166006)(81156014)(229853002)(99286004)(4744005)(8676002)(8936002)(66476007)(14444005)(446003)(86362001)(6116002)(2906002)(82746002)(66946007)(2616005)(256004)(73956011)(5660300002)(36756003)(64756008)(66556008)(53546011)(6506007)(102836004)(66446008)(486006)(66066001)(476003)(11346002)(3846002)(6246003)(68736007)(186003)(26005)(6916009)(478600001)(14454004)(4326008)(33656002)(53936002)(76176011)(25786009)(6512007)(54896002)(296002)(316002)(236005)(83716004)(71190400001)(71200400001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB4795; 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: EXfpTRchvhDh5hZ7FeU5B/6Ny+DJYZSXGGf+55R14NEP7VmgqZiSRyDqL2xCeIL9vkp9JpMLpA0Wl5ijkTX7FLvuFUjuO2zdthEXbcPkyxbnXHAx6FDMxbI9VZfkekhkw58GQ7Gk4QYAFjP6GW13PSsQOQ6HkN4M/2kxmJmLsiMsYLLp+EOLcMmdw9MYooddCW02eovAziRKzTq1TXDuTtEZPb5hqewNE6Db8bKZHYZfC7iInBaDrE1aVyNhaHq2VnGk681s5PNFx/WsvB3bFqVdDTV3e5FlOM7tulZOxT5PfLabdFR8KPxCuCS7Jyt5sOSbiOJ6akabvbpe9Hfuhzc7p4dBYsJ4/ztnxG5BHluhuDI16w8TY1viUJWFC8GvBDYkz5ASwLFLmqbNDn5y7CYJ63JNMJaHJtUTTeuJvLQ=
Content-Type: multipart/alternative; boundary="_000_2809E7BB023345C4859705FAC6EAA68Ajunipernet_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 34e3ebf6-3601-459b-5d8a-08d6dfaa9f8c
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2019 18:15:23.2535 (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: DM6PR05MB4795
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-23_15:, , 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=844 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905230121
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/mM6VEUUzl2qRrYFuK5nNiClOOhc>
Subject: Re: [Idr] Can we eliminate the "IETF Review" Capablities range? [was: Re: I-D Action: draft-ietf-idr-capabilities-registry-change-04.txt]
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2019 18:15:32 -0000

On May 23, 2019, at 7:33 PM, tom petch <ietfc@btconnect.com<mailto:ietfc@btconnect.com>> wrote:

We should reserve enough entries, i.e. IETF Review, to accommodate our
needs for, say, the next decade.

I think that’s more of an e.g. than it is an i.e., the other option being “Reserved”. Between those two, my own preference is for “Reserved” since doesn’t burden anyone with the (admittedly minor in the grand scheme) work of deciding which range to request a number from.

—John

v2.23.0 | Report a Bug | By Email