IETF Logo Mail Archive

Re: exploring the process of self retiring one's name from an RFC

Tim Chown <Tim.Chown@jisc.ac.uk> Sat, 20 April 2019 07:24 UTC

Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F294120074 for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2019 00:24:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 8n8bjtpxPzg8 for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2019 00:24:57 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [207.82.80.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26CFA120033 for <ietf@ietf.org>; Sat, 20 Apr 2019 00:24:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1555745094; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iYEO/EkiZNcJcWWzwYLa7ukYiXtrhxOTuy1Cu2IuH/g=; b=BOQSjf/uRLLxoLJNrGkGfWBlWp+m0aXT2CiNwkwB0mPs6Yh4uEnhskH4cYC+NmU8ySMYsa0vmbJfdc9s8f9g33s2Mgd36FU7Yu0Fpf0x7Uz3IS9GHrrK9LCBAdlzigHYDptUnO/+9ygRh65kfDfgRvZo4MCuoDheDRYOvUq7hLY=
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01lp2057.outbound.protection.outlook.com [104.47.1.57]) (Using TLS) by relay.mimecast.com with ESMTP id uk-mta-152-sNPXcUWLM-SaacocDhiZSw-2; Sat, 20 Apr 2019 08:24:51 +0100
Received: from AM0PR07MB4177.eurprd07.prod.outlook.com (52.133.54.140) by AM0PR07MB4290.eurprd07.prod.outlook.com (52.133.54.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1813.9; Sat, 20 Apr 2019 07:24:49 +0000
Received: from AM0PR07MB4177.eurprd07.prod.outlook.com ([fe80::6cb9:32aa:c8aa:12e5]) by AM0PR07MB4177.eurprd07.prod.outlook.com ([fe80::6cb9:32aa:c8aa:12e5%7]) with mapi id 15.20.1813.011; Sat, 20 Apr 2019 07:24:49 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Paul Wouters <paul@nohats.ca>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
CC: Christian Huitema <huitema@huitema.net>, IETF Discussion <ietf@ietf.org>, Jared Mauch <jared@puck.nether.net>
Subject: Re: exploring the process of self retiring one's name from an RFC
Thread-Topic: exploring the process of self retiring one's name from an RFC
Thread-Index: AQHU9pbjxL3CB0G2mk+zvtaoG5nUoqZDWNCAgAAHnICAAAZOgIAAHxgAgAAQsACAAAqqAIABBesA
Date: Sat, 20 Apr 2019 07:24:49 +0000
Message-ID: <0BED049F-78EC-46D2-B79C-7D08F3FDD245@jisc.ac.uk>
References: <1a0ba1ad-9e32-4663-208c-f94f4f0306de@gmail.com> <00fde7c6-c8a4-508e-5735-056647cdfb52@gmail.com> <9E3D5C77-C1C8-4D22-97BF-B97324C7DFCC@puck.nether.net> <13a585d3-ff7c-757d-3f5d-d60be289e0d1@gmail.com> <FE3CDAA5-CF0E-4D19-8985-76BAEEEC9E36@huitema.net> <b94d0cd7-0ca2-4072-3f2a-ef387406c2b0@gmail.com> <1C743268-61FA-4D7C-A3F4-C2DA950300C1@nohats.ca>
In-Reply-To: <1C743268-61FA-4D7C-A3F4-C2DA950300C1@nohats.ca>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.104.8)
x-originating-ip: [2001:a88:d510:1101:685c:f28f:1597:264a]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ff0787b4-2435-47df-c1c3-08d6c561460c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:AM0PR07MB4290;
x-ms-traffictypediagnostic: AM0PR07MB4290:
x-microsoft-antispam-prvs: <AM0PR07MB4290F4A92F14EAD714D546E8D6200@AM0PR07MB4290.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:5516;
x-forefront-prvs: 0013079544
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39850400004)(346002)(376002)(396003)(136003)(366004)(189003)(199004)(6246003)(6436002)(4744005)(6486002)(4326008)(99286004)(486006)(476003)(478600001)(110136005)(54906003)(64756008)(66446008)(53936002)(66946007)(66476007)(76116006)(91956017)(66556008)(72206003)(8676002)(5660300002)(71200400001)(86362001)(71190400001)(2906002)(6116002)(73956011)(14454004)(68736007)(76176011)(25786009)(102836004)(93886005)(229853002)(82746002)(786003)(53546011)(316002)(6512007)(83716004)(50226002)(186003)(36756003)(6506007)(81156014)(81166006)(74482002)(8936002)(11346002)(2616005)(446003)(305945005)(33656002)(46003)(256004)(97736004)(7736002)(57306001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR07MB4290; H:AM0PR07MB4177.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 5VtK9WEZp4znSM1EVcj1BmZh6Nn6E3YzPgg2l1+BhwopJTpSkw8OE9tJfBoOHu5O/CohYgEqMBo6kpmJbJ74zJRtdPNfaboBZoLzgJlEBldBOTKWnNLjgVovyFx6/rhtnS7adIIIXUiiyLkPF6PtbOkqFypMjXhwj9t/clOva8kYj4+FY8SbA6VDNLAaHCVwmFJxn2dbsx2VZKunTuW8ItB9toglp5j2BFLtCoOmZOAsuMCk/gVlOwb7w6+amyq2osVVWuXwiU6DE1kp2OS3srAwC/+vn0uCULKQwYXUBjHSm6pEhsIJjnAv16n/HzMbTaM0g+L+9jed+E5X6NgpCj3cGsgSDWNAoPEN30++Yt2JznjPuwNUUX3RXvUWKrHF84OcEQom5ekRua3fj4sZxm1dpgZbf1RIqAh4ykAA38g=
Content-ID: <A22EACB038EDCA42996189DE30E8BA04@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: ff0787b4-2435-47df-c1c3-08d6c561460c
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2019 07:24:49.6035 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB4290
X-MC-Unique: sNPXcUWLM-SaacocDhiZSw-2
X-Mimecast-Spam-Score: 0
Content-Type: text/plain; charset="WINDOWS-1252"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0CdIFyAlFY7LRFbXRbqAHZiUkNA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Apr 2019 07:24:59 -0000

> On 19 Apr 2019, at 16:47, Paul Wouters <paul@nohats.ca> wrote:
> 
> You seem to think the RFC should not apply anymore. So convince your old authors and/or the appropriate WG to move the RFC to Historic status.

As another author of that RFC, I would object strongly to that.  The (purely informational) draft documents the pros and cons of the 64-bit boundary, why it exists, and impacts of changing it (assumptions made).  It does not preclude any such future change.  

Alex, I recall at the time you had the view you are expressing now, but chose to remain an author.  I think you now have to live with that choice!

But nothing precludes a new draft being written on the subject.

Tim

v2.23.0 | Report a Bug | By Email