[Int-area] Fwd: New Version Notification for draft-ietf-intarea-schc-protocol-numbers-02.txt

Robert Moskowitz <rgm-ietf@htt-consult.com> Mon, 08 April 2024 20:01 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 7CBD9C15107F for <int-area@ietfa.amsl.com>; Mon, 8 Apr 2024 13:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.195
X-Spam-Level:
X-Spam-Status: No, score=-4.195 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 GMKAPEvDqcDb for <int-area@ietfa.amsl.com>; Mon, 8 Apr 2024 13:01:08 -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 D9AFAC151072 for <int-area@ietf.org>; Mon, 8 Apr 2024 13:01:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 32D316256E for <int-area@ietf.org>; Mon, 8 Apr 2024 16:00:35 -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 XcyO3ABFo-op for <int-area@ietf.org>; Mon, 8 Apr 2024 16:00:26 -0400 (EDT)
Received: from [192.168.160.29] (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 7BD366250B for <int-area@ietf.org>; Mon, 8 Apr 2024 16:00:26 -0400 (EDT)
Content-Type: multipart/alternative; boundary="------------SVpkU9Y8oZvyCD3g7vBB72dT"
Message-ID: <4ad0c3c5-bea8-4851-b1ca-0d6f9f0a713d@htt-consult.com>
Date: Mon, 08 Apr 2024 16:00:42 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: int-area <int-area@ietf.org>
Content-Language: en-US
From: Robert Moskowitz <rgm-ietf@htt-consult.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/3IeMEbtreAy6exJ_qY89gEyOZM0>
Subject: [Int-area] Fwd: New Version Notification for draft-ietf-intarea-schc-protocol-numbers-02.txt
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, 08 Apr 2024 20:01:12 -0000

Changed references for diet-esp to ipsecme workgroup.

Ahem, after I get through some working with students to get some 
ArduPilot coding going, I really need to get serious on this draft.

Sigh.

Bob


-------- Forwarded Message --------
Subject: 	New Version Notification for 
draft-ietf-intarea-schc-protocol-numbers-02.txt
Date: 	Mon, 08 Apr 2024 12:57:09 -0700
From: 	internet-drafts@ietf.org
To: 	Stuart W. Card <stu.card@axenterprize.com>, Adam Wiethuechter 
<adam.wiethuechter@axenterprize.com>, Pascal Thubert 
<pthubert@cisco.com>, Robert Moskowitz <rgm@labs.htt-consult.com>, 
Stuart Card <stu.card@axenterprize.com>



A new version of Internet-Draft
draft-ietf-intarea-schc-protocol-numbers-02.txt has been successfully
submitted by Robert Moskowitz and posted to the
IETF repository.

Name: draft-ietf-intarea-schc-protocol-numbers
Revision: 02
Title: Protocol Numbers for SCHC
Date: 2024-04-08
Group: intarea
Pages: 9
URL: 
https://www.ietf.org/archive/id/draft-ietf-intarea-schc-protocol-numbers-02.txt
Status: 
https://datatracker.ietf.org/doc/draft-ietf-intarea-schc-protocol-numbers/
HTML: 
https://www.ietf.org/archive/id/draft-ietf-intarea-schc-protocol-numbers-02.html
HTMLized: 
https://datatracker.ietf.org/doc/html/draft-ietf-intarea-schc-protocol-numbers
Diff: 
https://author-tools.ietf.org/iddiff?url2=draft-ietf-intarea-schc-protocol-numbers-02

Abstract:

This document requests an Internet Protocol Number, an Ethertype, and
UDP port assignment for SCHC. The Internet Protocol Number request
is so that SCHC can be used for IP independent SCHC of other
transports such as UDP and ESP. The Ethertype is to support generic
use of native SCHC over any IEEE 802 technology for IP and non-IP
protocols. The UDP port request is to support End-to-End SCHC
through potentially blocking firewalls.



The IETF Secretariat