Re: [tsvwg] RFC Number for draft-ietf-tsvwg-rfc4960bis

Sandy Ginoza <sginoza@amsl.com> Tue, 12 April 2022 16:31 UTC

Return-Path: <sginoza@amsl.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C51573A0593 for <tsvwg@ietfa.amsl.com>; Tue, 12 Apr 2022 09:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Vx5IIg-QpEPo for <tsvwg@ietfa.amsl.com>; Tue, 12 Apr 2022 09:31:54 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F33633A0484 for <tsvwg@ietf.org>; Tue, 12 Apr 2022 09:31:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id E4EF6427C644; Tue, 12 Apr 2022 09:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30dXz-AB2epo; Tue, 12 Apr 2022 09:31:53 -0700 (PDT)
Received: from smtpclient.apple (2603-8000-9603-b513-28e1-2e61-2e6f-b4e8.res6.spectrum.com [IPv6:2603:8000:9603:b513:28e1:2e61:2e6f:b4e8]) by c8a.amsl.com (Postfix) with ESMTPSA id AFC7C427C643; Tue, 12 Apr 2022 09:31:53 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <5B1B5866-F68D-4B06-9AE6-67592128CF12@ericsson.com>
Date: Tue, 12 Apr 2022 09:31:53 -0700
Cc: Martin Duke <martin.h.duke@gmail.com>, Michael Tuexen <tuexen@fh-muenster.de>, John Levine <johnl@taugh.com>, tsvwg <tsvwg@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C7381E8F-7916-467E-A406-2416932765D7@amsl.com>
References: <CAM4esxQOzOWWS8Z_tfSimsDDYXdY2x=5ERp0Mq-2HPq5UL4dog@mail.gmail.com> <077790D6-F448-4DD9-AE4F-6B2F17B615F4@amsl.com> <CAM4esxTk9n1Z-n76JVF9YnP8rtkZfOc5cp3XTFkQ4G-2S71aHA@mail.gmail.com> <5B1B5866-F68D-4B06-9AE6-67592128CF12@ericsson.com>
To: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/R5opuSv_AbwnNl_LqzZr5DUkPvk>
Subject: Re: [tsvwg] RFC Number for draft-ietf-tsvwg-rfc4960bis
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Apr 2022 16:31:59 -0000

Hi all,

FYI - draft-ietf-tsvwg-rfc4960bis is AUTH48 as RFC-to-be 9260.

Thanks,
Sandy

> On Apr 12, 2022, at 3:48 AM, Mirja Kuehlewind <mirja.kuehlewind@ericsson.com> wrote:
> 
> I guess we could go for 9260 if not already taken…?
>  
>  
>  
>  
> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of Martin Duke <martin.h.duke@gmail.com>
> Date: Tuesday, 12. April 2022 at 02:57
> To: Sandy Ginoza <sginoza@amsl.com>
> Cc: Michael Tuexen <tuexen@fh-muenster.de>, John Levine <johnl@taugh.com>, tsvwg <tsvwg@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
> Subject: Re: [tsvwg] RFC Number for draft-ietf-tsvwg-rfc4960bis
>  
> Ok, thanks. 
>  
> On Mon, Apr 11, 2022, 16:16 Sandy Ginoza <sginoza@amsl.com> wrote:
>> Hi Martin,
>> 
>> We are unable to accommodate this request, as 9460 is a 200+ number jump from the range in which we are currently assigning.  It’s not ideal as it would take us 9 months to a year to close the gap. 
>> 
>> Thanks,
>> Sandy 
>> 
>> 
>> > On Apr 8, 2022, at 11:12 AM, Martin Duke <martin.h.duke@gmail.com> wrote:
>> > 
>> > Hello RFC Editor,
>> > 
>> > This document is the third in a series, succeeding RFCs 2960 and 4960.
>> > 
>> > Would it be possible to assign this document 9460?
>> > 
>> > Thanks
>> > Martin Duke
>> > TSV AD
>>