IETF Logo Mail Archive

Re: [Int-area] What is in a name - draft-ietf-intarea-schc-ip-protocol-number

Bob Hinden <bob.hinden@gmail.com> Wed, 05 April 2023 18:10 UTC

Return-Path: <bob.hinden@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF74C1526FF for <int-area@ietfa.amsl.com>; Wed, 5 Apr 2023 11:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tkUl-J3tDDUN for <int-area@ietfa.amsl.com>; Wed, 5 Apr 2023 11:10:30 -0700 (PDT)
Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72DEFC1524AC for <int-area@ietf.org>; Wed, 5 Apr 2023 11:10:30 -0700 (PDT)
Received: by mail-oi1-x229.google.com with SMTP id l18so27260099oic.13 for <int-area@ietf.org>; Wed, 05 Apr 2023 11:10:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680718229; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=nDrwa9eS4nzQxeXdrU4VC+u1l2lgpUe20uHpQAbhu3Q=; b=lYdcp9b9QGqO2fgrDsNVN5WVOkUs9Q5bRmP75Qkbvmg8pZz3eD66x3RJHheAFuyRw7 vUeAvIDP/hJoRVWIyYX5MNWf0NKArCJY/fdsWqYCmeCLVcdrT5QmhvIfxaYTktW7zRT6 5ZJ2qpdHmP10C8UhVBI852GIkMUjv2tQsOwjzznYtMwYrH8psDpAkXnmXh5tMdWxptMJ fcXwegvjp4sWt2WnU0FN2fMetCu+qEVXAJT/qLCr2eIZHJ1weIefggeN4qS9TCBFH037 L986CRQbNHnOtLBh8AQU7/WQpKNEeNaCJFfMO94SYgHGLpYj+gyCHH1e5HUXeZZd0keH 9HXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680718229; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=nDrwa9eS4nzQxeXdrU4VC+u1l2lgpUe20uHpQAbhu3Q=; b=UrX+Nvex/fYyBqBX8QZCgdAx96wVgc/Iqm0qnlX7fXOM2KSB6bqWAtWxBcMfZpEgIR mr/cNoAELQi50mAXGK7vevA4I7lvgHDdODdcfRv9bvWzcUS8yfOZUNY0NSVSHViT18bD KZZRoH1iEaBOJAU/041rjh3FCna0LACVul0oPy+3Uf1GGEJhLA17bFayv9TV8Sybt454 P6ghDZDaIsT37wWjUWNi7R7CjVEGDlQv7Kfq1FCuGXhvqCCmrjWchuiadtoAgL0P33G0 8q8uEz6gGFCXpGI23VGNvRlBi5DgXHWePjIxw1wUa8a8IZtglYZ8ev1hkg5Rff2rslZr /m5g==
X-Gm-Message-State: AAQBX9dlDOauKMSSz/tRTnIJoN5RN0dAz/zyarWYXQfPHxtqBo5fd77L 9/cKpNQ46HE0sjxvkq6LlDI=
X-Google-Smtp-Source: AKy350bFXeOWR/fG/0BsRIu7w/U8TaBrEJ3oSDrQIdDVinb2xLc1Dlj8f9z+DaRVMHEGNc7d36Bhzg==
X-Received: by 2002:a05:6808:2a05:b0:387:53ce:4eb3 with SMTP id ez5-20020a0568082a0500b0038753ce4eb3mr3437091oib.48.1680718229356; Wed, 05 Apr 2023 11:10:29 -0700 (PDT)
Received: from smtpclient.apple ([204.239.251.4]) by smtp.gmail.com with ESMTPSA id n6-20020a4a4006000000b0052a77e38722sm7032402ooa.26.2023.04.05.11.10.28 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Apr 2023 11:10:28 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_8EE74BE3-0F43-4DD7-B3D0-B8910A108434"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.2\))
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <8c6e4cc0-3dc8-de67-f921-a8b6d7374381@htt-consult.com>
Date: Wed, 05 Apr 2023 11:10:27 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, tom petch <ietfc@btconnect.com>, "int-area@ietf.org" <int-area@ietf.org>
Message-Id: <B40001F0-229B-4010-B5AD-C5941A55A70B@gmail.com>
References: <cfd8779b-1dbd-572d-8432-3b9769665712@htt-consult.com> <AM7PR07MB6248DAFD838C2C00ACB15A2EA0909@AM7PR07MB6248.eurprd07.prod.outlook.com> <8c6e4cc0-3dc8-de67-f921-a8b6d7374381@htt-consult.com>
To: Robert Moskowitz <rgm-ietf@htt-consult.com>
X-Mailer: Apple Mail (2.3696.120.41.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/aEaLLyVNTFBaj6VjeE1tWFNnO0I>
Subject: Re: [Int-area] What is in a name - draft-ietf-intarea-schc-ip-protocol-number
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Internet Area WG Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2023 18:10:34 -0000

Bob,

It’s only the draft file name, you can change the title of the document and keep the same file number.   That would make it easier to see the evolution of the work.

Chag Sameach!

Bob




> On Apr 5, 2023, at 10:58 AM, Robert Moskowitz <rgm-ietf@htt-consult.com> wrote:
> 
> The origin draft only was discussing SCHC as an IP Protocol Number.
> 
> At IETF115, the attendees agreed that the draft needs to be expanded to also SCHC as an Ethertype and as a UDP Port Number.
> 
> Thus the old draft name no longer reflects the new content.  There is a mechanism when you submit a draft to link it to a prior draft so the draft history is properly maintained (it does not support linking to multiple prior drafts or splitting an old draft into multiple, for that you have to ask for human help).
> 
> So the new draft name will reflect the new draft content.
> 
> I just don't have enough time to get content into the new draft prior to Passover Holiday start.  I hope to get it done during the middle days, say Sunday.  Stay tuned.  Pascal Thubert is helping me with the new content.  Particularly the specific content needed to liason with IEEE 802 on the Ethertype.
> 
> Bob
> 
> On 4/5/23 11:49, tom petch wrote:
>> From: Int-area <int-area-bounces@ietf.org> on behalf of Robert Moskowitz <rgm-ietf@htt-consult.com>
>> Sent: 05 April 2023 12:22
>> 
>> I am in the process of reving draft
>> 
>> draft-ietf-intarea-schc-ip-protocol-number
>> 
>> and adding support for schc as an ethertype and tcp/udp port number as I
>> said I would do back in Nov.  Sigh.
>> 
>> So what to name the new draft?
>> 
>> <tp>
>> If you are producing a new version of draft-ietf-intarea-schc-ip-protocol-number-00 then I would call it draft-ietf-intarea-schc-ip-protocol-number-01.  I do not see any other logical choice.
>> 
>> Tom Petch
>> 
>> 
>> 
>> draft-ietf-intarea-schc-protocol-numbers
>> 
>> ??
>> 
>> Alternatives?
>> 
>> Thanks and now back to my writing as I really want to get an update out
>> today before Holidays...
>> 
>> Bob
>> 
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

v2.23.0 | Report a Bug | By Email