[Int-area] AERO/OMNI transition to the IETF (abridged)
"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Wed, 04 August 2021 22:01 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 2B3503A0D89; Wed, 4 Aug 2021 15:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K4fZsWmRX63p; Wed, 4 Aug 2021 15:01:26 -0700 (PDT)
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 7E7FA3A0D94; Wed, 4 Aug 2021 15:01:25 -0700 (PDT)
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 174M1Kke004065; Wed, 4 Aug 2021 18:01:24 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1628114484; bh=Tw+Y1bU2s3yQeqsFt0/332w8Dy4e9L5R79O4NKNWR34=; h=From:To:CC:Subject:Date:From; b=FbM4rfbf5LXn0I9M5Ko2XLzvDDIwiEB/KxdO262NTLf3OmNsQj6NuLom5awzjN2ht wPPDyZQyH7jVjDd3nqzOUpqUfCnWbVe2cA7kZdGsL+ow2gZBq2AtGd1spV2dnysKnH lDfJiLdKnP6PtRtOrC7aElBYtAVZtWtNL8/Q3FSitFeymYU9Tmgre81ARaCEJwyxyy hFGEHE/qwiro4hRPkbjUN2Ithpfb1a4DW4D9E9guuavl6gNJ01jvyKf2MPoPA64sDz A+k/e9zrChAA1+rSeYc8jhCRLtHG9DkTl+rk05EQOMVV6chCCRw+Y79uurXid3HMIy RmiuuFuNeHPHg==
Received: from XCH16-07-10.nos.boeing.com (xch16-07-10.nos.boeing.com [144.115.66.112]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 174M1J4S004055 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 4 Aug 2021 18:01:19 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-10.nos.boeing.com (144.115.66.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2242.4; Wed, 4 Aug 2021 15:01:18 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2242.008; Wed, 4 Aug 2021 15:01:18 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Fred Baker <fredbaker.ietf@gmail.com>, Vasilenko Eduard <vasilenko.eduard@huawei.com>
CC: "atn@ietf.org" <atn@ietf.org>, "6man@ietf.org" <6man@ietf.org>, int-area <int-area@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>, routing WG <rtgwg@ietf.org>
Thread-Topic: AERO/OMNI transition to the IETF (abridged)
Thread-Index: AdeJfBC43FEqc6NkRIqGjG6k4rXdTg==
Date: Wed, 04 Aug 2021 22:01:18 +0000
Message-ID: <8ad87c53788d4bc5a544caefad7c5412@boeing.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: 85D4763096A6E23DC1150690767BDF9479B91FA9442473CA7341A0D76540ACBF2000:8
Content-Type: multipart/alternative; boundary="_000_8ad87c53788d4bc5a544caefad7c5412boeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/x8Gp9i2zsNrajO-PNMM3BsVeiPI>
Subject: [Int-area] AERO/OMNI transition to the IETF (abridged)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area 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, 04 Aug 2021 22:01:34 -0000
(Trying again – previous attempt exceeded the intarea list MTU and I got back a “Message Too Big” error) Fred, thanks for posting again with Cc:’s trimmed to make it more palatable to lists. Your point about working group charters are noted; I looked at the charters and have the following impressions: 1) Scope of both AERO and OMNI are too broad for the current 6man charter. If anyone disagrees I am happy to discuss AERO/OMNI as 6man wg items but past overtures to that particular wg have been met with contempt and disdain. 2) AERO fits well with the rtgwg charter. I have contacted the rtgwg chairs and AD in a private email to express the same. A number of technical discussion points were raised during the rtgwg presentation at IETF111, and addressed in this post: https://mailarchive.ietf.org/arch/msg/rtgwg/oNPr8BA_4esFDXTmY-CbBRhkJ2I/ 3) OMNI fits well with the intarea charter. I have contacted the intarea wg chairs and AD in a private email to express the same. No technical discussion points were raised during the intarea presentation at IETF111. About IPv6 networks, whatever our past communications may have been I am happy to talk about IPv6 networks all day long within the context of the current AERO and OMNI specs. AERO/OMNI can be applied to all IP networks regardless of the IP protocol version. About turning ATN into an IETF working group, sure why not. I already have that experience (as well as battle scars) from taking the lead on turning DTN into an IETF working group. But, forming a working group requires significant time and energy that I am not sure the aviation community can muster. And, AERO/OMNI may have benefitted from aviation community input but as it turns out are in no way limited to that one specific use case. The aviation use case is very significant to be sure, but the AERO/OMNI domains of applicability are far more broad than just one use case. Fred T. fred.l.templin@boeing.com<mailto:fred.l.templin@boeing.com> fltemplin@acm.org<mailto:fltemplin@acm.org>
- [Int-area] AERO/OMNI transition to the IETF (abri… Templin (US), Fred L
- Re: [Int-area] AERO/OMNI transition to the IETF (… Templin (US), Fred L