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> Thu, 06 April 2023 04:13 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 DA72BC15952A for <int-area@ietfa.amsl.com>; Wed, 5 Apr 2023 21:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.316
X-Spam-Level:
X-Spam-Status: No, score=-1.316 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_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 M4_lgA0KvHUI for <int-area@ietfa.amsl.com>; Wed, 5 Apr 2023 21:13:47 -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 4587DC1595E5 for <int-area@ietf.org>; Wed, 5 Apr 2023 21:13:47 -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=UY/MPQ5O8I/D6Y5T2W1/XghreJHqcT7tIveAZ72JIVQ=; b=woV0MfIfXvan9pTjegi5IJvLXI J3SPUN3m9uoCGzsmO3OmUyKO2FY42dGUIYeqD2BYtLLdT5HKoKJO4PxorIJtfi57sPfN3MqVEwKAk H3gFM/rK4jBvVWUKPGkP+OqwkADOlFC+UHcAD1AO0GpxmmMZ236ue1bJi7iiAXwv0h24WcgavVZnG Q5aVNQd3+snBvWx6HF6ppl4BFMo2mus8vBX4TwdQ3Y96xxv6iUeyIuRG1UL1DRriAwff0/YTPQrAE C+cHlGZUvybftTP++Mule73MDpJ5wNpiF2Ac9tBuTouoLD05H+Z3TRp854P2e8vO+nrP0g9v1ubrs ASzmDPQA==;
Received: from [172.58.208.166] (port=7819 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 1pkH0B-00ArM9-Oh; Thu, 06 Apr 2023 00:13:40 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_D708C850-2B01-428D-BB65-769567B4F0E5"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <cfd8779b-1dbd-572d-8432-3b9769665712@htt-consult.com>
Date: Wed, 05 Apr 2023 21:13:22 -0700
Cc: int-area@ietf.org
Message-Id: <CF620D20-A653-4B34-9F11-6FFD6F29E96A@strayalpha.com>
References: <cfd8779b-1dbd-572d-8432-3b9769665712@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/POUHalbGdqwNFR1ajcV-aETw50I>
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: Thu, 06 Apr 2023 04:13:51 -0000

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