IETF Logo Mail Archive

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

"touch@strayalpha.com" <touch@strayalpha.com> Mon, 10 April 2023 04:18 UTC

Return-Path: <touch@strayalpha.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 D6647C151533 for <int-area@ietfa.amsl.com>; Sun, 9 Apr 2023 21:18:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.315
X-Spam-Level:
X-Spam-Status: No, score=-1.315 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 CZVaOQ3gxOUd for <int-area@ietfa.amsl.com>; Sun, 9 Apr 2023 21:18:07 -0700 (PDT)
Received: from server217-2.web-hosting.com (server217-2.web-hosting.com [198.54.115.98]) (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 F2C75C14CE4F for <int-area@ietf.org>; Sun, 9 Apr 2023 21:18:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=VJHmz+y28HY6HTiNlmWA4N72bGCWog/Xs5+Q/rjXAVg=; b=Hdni/HwOFVmlx4uav5eWpEvjeN lE5G1hap7TvNlTs6VPun3WvInZjHq+KUI/AxLehKRJgPFXGOC/BiAl4oRJFkhNfa2rDLLZ5uPu06c Ry7qQbKgXX5M3JFGs0ggFjsAW210nvt1wfi9TaI5+sy0m/R79aHVWsYMP00TE5Rz64qjFTqjFAheF 0MeZFn2HU9ClF5cZU/a2teS00UFKq0/+pSWIrfP4RFg/0/eAH/d7ICPElzWVbIK8d0ufY4D6q1BpO 3HgnP0VtlS/NetblVS1GPva4ReSg4/5kFeKkiz4cwaIbE/NIn+RvST2Wp58gQph55UkEnQw+8u2Ga JfvlAbMQ==;
Received: from [172.56.184.232] (port=48753 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from <touch@strayalpha.com>) id 1pliyb-000aCO-4T; Mon, 10 Apr 2023 00:18:01 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_578FABD9-6434-46A1-9DB8-8F2DA297D2DE"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <8a4b2a09-3abf-59fc-3eff-d99dcdc29e9c@htt-consult.com>
Date: Sun, 09 Apr 2023 21:17:44 -0700
Cc: int-area@ietf.org
Message-Id: <EA2B842D-768F-41AE-ACC7-28945CB8EC63@strayalpha.com>
References: <cfd8779b-1dbd-572d-8432-3b9769665712@htt-consult.com> <CF620D20-A653-4B34-9F11-6FFD6F29E96A@strayalpha.com> <8a4b2a09-3abf-59fc-3eff-d99dcdc29e9c@htt-consult.com>
To: Robert Moskowitz <rgm-ietf@htt-consult.com>
X-Mailer: Apple Mail (2.3731.500.231)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/ySVZ3QeVvxqEPK45hRZ-f7ABtPY>
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: Mon, 10 Apr 2023 04:18:10 -0000

Hi, Bob,

Having SCHC as an IP protocol number is more than sufficient to use it with numerous tunneling protocols and/or layering protocols, including GRE - which can be tunneled in UDP too.

Why is that - any of numerous other network-layer tunnel protocols (that demux on network protocol ID)  - not sufficient?

If not, IMO the doc would need to provide the details of the tunneling protocol at the transport layer to justify a transport port assignment.

Joe

—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com

> On Apr 9, 2023, at 2:30 PM, Robert Moskowitz <rgm-ietf@htt-consult.com> wrote:
> 
> 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 <mailto:touch@strayalpha.com> wrote:
>> Hi, Bob,
>> 
>>> On Apr 5, 2023, at 4:22 AM, Robert Moskowitz <rgm-ietf@htt-consult.com> <mailto: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 <http://www.strayalpha.com/>
>> 
>

v2.23.0 | Report a Bug | By Email