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

Robert Moskowitz <rgm-ietf@htt-consult.com> Tue, 11 April 2023 01:48 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 8C8E9C152A14 for <int-area@ietfa.amsl.com>; Mon, 10 Apr 2023 18:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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
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 tqRM5XT5VODC for <int-area@ietfa.amsl.com>; Mon, 10 Apr 2023 18:48:29 -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 B5CBEC151B16 for <int-area@ietf.org>; Mon, 10 Apr 2023 18:48:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 3BA12624D4 for <int-area@ietf.org>; Mon, 10 Apr 2023 21:48:03 -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 J978EhasMaap for <int-area@ietf.org>; Mon, 10 Apr 2023 21:47:55 -0400 (EDT)
Received: from [192.168.156.67] (186.sub-174-239-122.myvzw.com [174.239.122.186]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id F18E26221A for <int-area@ietf.org>; Mon, 10 Apr 2023 21:47:51 -0400 (EDT)
Content-Type: multipart/alternative; boundary="------------0LYc8wYUPwpz34z0OJunEq01"
Message-ID: <eb940ae7-5bb1-1626-7a83-bbeb69c58201@htt-consult.com>
Date: Mon, 10 Apr 2023 21:48:11 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0
To: "int-area@ietf.org" <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/3RsTgdtLEY7Oi2s7iCRvotftVNw>
Subject: [Int-area] Fwd: New Version Notification for draft-ietf-intarea-schc-protocol-numbers-00.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: Tue, 11 Apr 2023 01:48:33 -0000

Here is the new version adding the Ethertype request.

I request people review and comment.

Still not included is the UDP port for firewall traversal.  I decided 
not to wait on that to get a draft out for review.

Bob


-------- Forwarded Message --------
Subject: 	New Version Notification for 
draft-ietf-intarea-schc-protocol-numbers-00.txt
Date: 	Mon, 10 Apr 2023 16:37:35 -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 I-D, draft-ietf-intarea-schc-protocol-numbers-00.txt
has been successfully submitted by Robert Moskowitz and posted to the
IETF repository.

Name: draft-ietf-intarea-schc-protocol-numbers
Revision: 00
Title: Protocol Numbers for SCHC
Document date: 2023-04-10
Group: intarea
Pages: 9
URL: 
https://www.ietf.org/archive/id/draft-ietf-intarea-schc-protocol-numbers-00.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-00.html
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-ietf-intarea-schc-protocol-numbers


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