IETF Logo Mail Archive

Re: [Int-area] Next steps for draft-ietf-intarea-schc-ip-protocol-number-00

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Wed, 09 November 2022 16:10 UTC

Return-Path: <Fred.L.Templin@boeing.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 119BCC14CE27; Wed, 9 Nov 2022 08:10:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.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 8yT5rAPNXdy0; Wed, 9 Nov 2022 08:10:33 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 90B28C14F73E; Wed, 9 Nov 2022 08:10:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 2A9GASnT020293; Wed, 9 Nov 2022 11:10:32 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1668010232; bh=WelzcogddyHFtAMXLQP09mp0aE9pCdplytDIGHahOTU=; h=From:To:Subject:Date:References:In-Reply-To:From; b=uIhdm291h9/Y/Emt3r5QL0x7Fahgk+cwdLBCrppDYhjXEKx5eIjyXHY7gnmLgpqNA msUVQcgzVbNT/eugqSNJFYTQw4q5+xf3QsJaZFLE8vcq9OfVyAYLNR6MUBKhl+ys3P XYTcRGie4w1HLTT4xZuDh67sn8jZVA9+4vbmiJg5YtqB4wqrp04PEYj7taO5mnAfSK LtUMt9LcPwy6KjM4deid5mCWLM4uEWNCD344goLF+0eXX7grme3uLLbXc9FSzApFxt YLSyqK6IwP8Di0ViJ7gqdO0DLZutrg8pJZU/nQRbHwZXf+Hn/a8cy2Iv3N5LYU3Ldf Kz0KN2M5Jl//Q==
Received: from XCH16-07-09.nos.boeing.com (xch16-07-09.nos.boeing.com [144.115.66.111]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 2A9GAMRs020204 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 9 Nov 2022 11:10:22 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-09.nos.boeing.com (144.115.66.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.12; Wed, 9 Nov 2022 08:10:21 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.2507.012; Wed, 9 Nov 2022 08:10:21 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "Juan Carlos Zuniga (juzuniga)" <juzuniga=40cisco.com@dmarc.ietf.org>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: Next steps for draft-ietf-intarea-schc-ip-protocol-number-00
Thread-Index: AQHY9FRh3AYwrBGwaEq3gZGl2Y9g4K42wiFQ
Date: Wed, 09 Nov 2022 16:10:21 +0000
Message-ID: <d7417d1e43ea47cd9fbff155b85fc736@boeing.com>
References: <MW5PR11MB5761CB30C40814FA4B86658AD13E9@MW5PR11MB5761.namprd11.prod.outlook.com>
In-Reply-To: <MW5PR11MB5761CB30C40814FA4B86658AD13E9@MW5PR11MB5761.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 7BDD1C82CF5288082FD4033CA83D8FAC91AD54F45EB752F09250F8C4D1755F2A2000:8
Content-Type: multipart/alternative; boundary="_000_d7417d1e43ea47cd9fbff155b85fc736boeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/wX2j4xoWjJEfBc-UsAEjEVQ6wiM>
Subject: Re: [Int-area] Next steps for draft-ietf-intarea-schc-ip-protocol-number-00
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: Wed, 09 Nov 2022 16:10:39 -0000

I want to understand whether granting these allocations for SCHC would prevent
OMNI from receiving exactly the same three allocation types. If so, then we need
to ask the question of whether the codepoints should go to SCHC or OMNI. In my
view, OMNI should get the codepoints.

Fred

From: Int-area <int-area-bounces@ietf.org> On Behalf Of Juan Carlos Zuniga (juzuniga)
Sent: Wednesday, November 09, 2022 8:07 AM
To: int-area@ietf.org
Subject: [EXTERNAL] [Int-area] Next steps for draft-ietf-intarea-schc-ip-protocol-number-00


EXT email: be mindful of links/attachments.




Hi IntArea WG,

Today we had an interesting discussion about the future of draft-ietf-intarea-schc-ip-protocol-number-00.
We would like to ask Bob Moskowitz et al. to upload a revised I-D with the text about the EtherType and UDP port numbers.

Once we have that draft published, we will re-confirm our call for adoption, and then we will proceed to coordinate with tsvwg as discussed.

Best,

Juan-Carlos & Wassim
(IntArea chairs)

v2.23.0 | Report a Bug | By Email