IETF Logo Mail Archive

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

Robert Moskowitz <rgm-ietf@htt-consult.com> Sun, 09 April 2023 21:30 UTC

Return-Path: <rgm-ietf@htt-consult.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 422DBC17B321 for <int-area@ietfa.amsl.com>; Sun, 9 Apr 2023 14:30:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, 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
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 hpMH-z-lls2T for <int-area@ietfa.amsl.com>; Sun, 9 Apr 2023 14:30:19 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 3EB94C1782D0 for <int-area@ietf.org>; Sun, 9 Apr 2023 14:30:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id F1798624D4; Sun, 9 Apr 2023 17:29:52 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HysBWFigmk4O; Sun, 9 Apr 2023 17:29:44 -0400 (EDT)
Received: from [192.168.156.67] (253.sub-174-216-182.myvzw.com [174.216.182.253]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 3E3B960944; Sun, 9 Apr 2023 17:29:43 -0400 (EDT)
Content-Type: multipart/alternative; boundary="------------NYRI0N0b67RDzfZWbesFRwFR"
Message-ID: <8a4b2a09-3abf-59fc-3eff-d99dcdc29e9c@htt-consult.com>
Date: Sun, 09 Apr 2023 17:30:04 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0
Content-Language: en-US
To: "touch@strayalpha.com" <touch@strayalpha.com>
Cc: int-area@ietf.org
References: <cfd8779b-1dbd-572d-8432-3b9769665712@htt-consult.com> <CF620D20-A653-4B34-9F11-6FFD6F29E96A@strayalpha.com>
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
In-Reply-To: <CF620D20-A653-4B34-9F11-6FFD6F29E96A@strayalpha.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/Iw0BARvjj1yN8KvIlkSsd2rPyc0>
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: Sun, 09 Apr 2023 21:30:23 -0000

Joe,

My original use case was for SCHC as an IP Protocol Number with diet-esp 
being the sample.  WIthout this we have to do a hack on the SPI management.

My more recent work definitely benefits from SCHC as an Ethertype.

My text does/will cover these use cases for why.

SCHC as a port number was added by others, primarily Pacal Thubert for 
UDP firewall traversal.  He will be providing the text for that use case.

Back to writing on this bumpy train ride...

Bob

On 4/6/23 00:13, touch@strayalpha.com wrote:
> Hi, Bob,
>
>> On Apr 5, 2023, at 4:22 AM, Robert Moskowitz 
>> <rgm-ietf@htt-consult.com> wrote:
>>
>> 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.
>
> I understand maybe Ethertype (though I think this is the mistake that 
> IPv6 made all over again), but for this to get a port number it would 
> need to be associated with a transport service, not just a packet type.
>
> Why would that be needed, e.g., vs. running this inside one of any of 
> the numerous transport tunneling protocols (esp GRE)?
>
> Joe
>
> —
> Dr. Joe Touch, temporal epistemologist
> www.strayalpha.com
>

v2.23.0 | Report a Bug | By Email