IETF Logo Mail Archive

Re: [Int-area] AERO/OMNI transition to the IETF (abridged)

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Thu, 05 August 2021 16:36 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 2D4CC3A18CD; Thu, 5 Aug 2021 09:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 b0g_igqM7e5E; Thu, 5 Aug 2021 09:36:24 -0700 (PDT)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 98EE93A18B4; Thu, 5 Aug 2021 09:36:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 175GaL1U026483; Thu, 5 Aug 2021 12:36:21 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1628181382; bh=yP4AzfZ9OIBmuVum5+SkDiXqM3CuXd1o9zmdmk6qMlY=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=FgxeHLF/Zh6s7MZWrikuJAXuIxS/Ql3SnXkunBglP4t9XrFkZ+m4EoEnF+FN9JbQm tdBsJf1sbd9Uhb9fApbXY+FvgaYb0Dd479gqqxAW+Vk4H2Bo9wrWV/HPETFcPbYfp2 mW0dQ9h0LBi8/ifilMyjE7S7VqTe5qNqmZ6YVkooXKrnnwtWIdfFfC3sAE5cPNEF/k eMiKFDhpE5DEW9bNpVv1fGwkk1avAxLvtfut3fMRUjxGJHHdhAHFHdJlyhGO4OrdLW klLgAgbt4WdFi5or7r1iTdPpQCyR9+9EObUIYZngAxYmJcBqfzCYQL9iT1R+BIHZ93 ZCUrRrTF+Ly4w==
Received: from XCH16-07-12.nos.boeing.com (xch16-07-12.nos.boeing.com [144.115.66.114]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 175Ga770026333 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 5 Aug 2021 12:36:08 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-12.nos.boeing.com (144.115.66.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2242.4; Thu, 5 Aug 2021 09:36:06 -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; Thu, 5 Aug 2021 09:36:06 -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: "6man@ietf.org" <6man@ietf.org>, int-area <int-area@ietf.org>, "atn@ietf.org" <atn@ietf.org>, rtgwg-chairs <rtgwg-chairs@ietf.org>, routing WG <rtgwg@ietf.org>
Thread-Topic: AERO/OMNI transition to the IETF (abridged)
Thread-Index: AdeJfBC43FEqc6NkRIqGjG6k4rXdTgAmlKYg
Date: Thu, 05 Aug 2021 16:36:06 +0000
Message-ID: <660d202a46f3436a865d16846f08fd0f@boeing.com>
References: <8ad87c53788d4bc5a544caefad7c5412@boeing.com>
In-Reply-To: <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: 2D1BFA66D59E101BDE0F587D9910A5714F560620B17BA026343D442503057F022000:8
Content-Type: multipart/alternative; boundary="_000_660d202a46f3436a865d16846f08fd0fboeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/7vKpxXZ2Rqne7hCXUTGcKM_l7S0>
Subject: Re: [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: Thu, 05 Aug 2021 16:36:28 -0000

Fred, regarding turning ATN into an IETF working group if that is going to happen
then someone else besides me is going to have to head up the effort. I have been
there and done that for other working groups, and do not need to go through that
pain again.

So, unless someone on the ATN list wants to stand up and volunteer to do what it
takes to turn the list into an IETF working group, this leaves us with two alternatives:
1) have the work adopted by an existing IETF working group(s), or 2) re-submit the
documents to the RFC-ISE stream. Or, I suppose a third alternative is to just forget
the whole thing.

Fred

v2.23.0 | Report a Bug | By Email