[manet] Re: draft-ietf-manet-inet-gap-analysis-06.txt
"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Fri, 14 August 2026 15:31 UTC
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: manet@mail2.ietf.org
Delivered-To: manet@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id BCA81129DA30F; Fri, 14 Aug 2026 08:31:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1786721481; bh=jSwVE1R8mHmwwKVw3qcy4ZQU1lej7ESifPFfd67YJjU=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=wdfc+FbKsPl1FWnJIkLtjwp77zz3xmPeIizq2SZYZStsf2q5oZ20UloSQ6uQq0YXs /J060eySJdVYC/5y4UpuDFkXp3fCpRgN71dgDEye0nJ1qzzk0qdf66s9LFf0qDj090 Fojsn5E3s0bc/87gFGXMJs1wIxLBxyRY6BU9yMWM=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.com header.b="ny4yZukS"; dkim=pass (1024-bit key) header.d=boeing.onmicrosoft.com header.b="Q1KZ8c7Y"
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8R8Csaaj5crt; Fri, 14 Aug 2026 08:31:21 -0700 (PDT)
Received: from ewa-mbsout-01.mbs.boeing.net (ewa-mbsout-01.mbs.boeing.net [130.76.20.194]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D689A129DA30A; Fri, 14 Aug 2026 08:31:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ewa-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 67EFVDYS048578; Fri, 14 Aug 2026 08:31:13 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1786721473; bh=jSwVE1R8mHmwwKVw3qcy4ZQU1lej7ESifPFfd67YJjU=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=ny4yZukSHTIETk1MewI4ZDaV0lEqn9vXiISSFmyDf4uSfirBxpbLRtgfO5e5n3Tqr bx3avGdrH+vZd2kKRoGqPULKPYKivbalzyQI9siZjkA+ZAKB2CpEh2w6esrjRhzFQf UXJHIqYPCLrHsKVytg2YUcl7cR0XFk7HeIqMdYqGuqOecHMy12pxidq3PtT4eFKoV3 0fj72+FU/nAyBWuUaIggppy86p+TZCs8BBLyw211yslBHKLYc6BnKhKZrrvf6XORY8 +amKOQbjXPV+K1bRgbjgcDnV+qKxBtJz6U9umVVEc551rbG0/yVe4f/MGLakE0bkeY wkzEenaXRtiOA==
Received: from XCH16-07-04.nos.boeing.com (xch16-07-04.nos.boeing.com [137.137.111.37]) by ewa-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 67EFV5Wc048476 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 14 Aug 2026 08:31:06 -0700
Received: from XCH19-01-01.nos.boeing.com (137.137.109.166) by XCH16-07-04.nos.boeing.com (137.137.111.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.71; Fri, 14 Aug 2026 08:31:05 -0700
Received: from XCH19-EDGE-Q02.nos.boeing.com (130.76.23.14) by XCH19-01-01.nos.boeing.com (137.137.109.166) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.45 via Frontend Transport; Fri, 14 Aug 2026 08:31:05 -0700
Received: from USG02-CY1-obe.outbound.protection.office365.us (23.103.199.176) by boeing.com (130.76.23.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.43; Fri, 14 Aug 2026 08:30:49 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector5401; d=microsoft.com; cv=none; b=Kilr7U6leLap4EdgCi3xLXLqJHwUBoLepSBVciM9CgTSXK46V0z9VSz9pwnFmGrfDzmgpjGSmgaOb6HPIRtb4ypLVds5ITXThrNsp/ZdRDT3CEc/fbl9lw3+89aCntKpiSGy7KBdOiK8QjGelh2W8pE+uR2FVZTnxtX0pPsw05K3UbfsoCIR/s0cBJE5fxyQKEE/LcDfo7FphBVFz4V2lrJ5HMj6Fj/duUUjAbf3jX+DW3/rRXJ2Kh2Smi0aN5Ugd61DofDKqtr3nZ6U198e4RmwnlA1Iw3ntTo7chi2bC7vRyRLCvjyLdHJW/ezs2ns7cvKm8A/kaw6la60Os60fA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector5401; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=jSwVE1R8mHmwwKVw3qcy4ZQU1lej7ESifPFfd67YJjU=; b=CKaPJNiASHhasJQCyCbs1s6zJhqKuVYGf6tgplHoi8QfqFKS2f04qIGFU3Ev/kqNkzAHG14F0oBxM0JfCAkf1idEzPkk9ghuCIrAorD13Kyf3l2K5q1oRw85e1hm6SLBez9hYmJ0OyxDpb8PqxpUWqoMKANMptOwjJkS0KUBny8+dlv6w61CQ4GehTH2Ec/yLtdoVxlIjaWbmlKLdUcDhzxe9rmOki99RvHU3gvuY+33YR6PRam4kFr3+l1dRNWgCs6+Eotjv8qXii0XV6bE3JQAzpwKHSaJXZAAiR9hU8QXOTqmEXfYxa98VkWqp6UfNzZWcqVAO7UhJ2eIElH4UA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=boeing.com; dmarc=pass action=none header.from=boeing.com; dkim=pass header.d=boeing.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.onmicrosoft.com; s=selector1-boeing-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jSwVE1R8mHmwwKVw3qcy4ZQU1lej7ESifPFfd67YJjU=; b=Q1KZ8c7Yt6t70MqIC7K6uLkpnr3nZ825xGgJRB3ii7AcH1RfjE74WID7sqo/xNBSvF1S4p4P+C9Bgno5AKq/wcMtp5cVdGJ/8fddrG/+UQZlDO+0EI3irZbQUwLZeF6xQRBIjLRmanbnU1B/gH2eHzYSGM+h+izl49H1Qok3EAc=
Received: from BNZP110MB2447.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:4a8::19) by BN0P110MB1109.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:16d::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.21.315.13; Fri, 14 Aug 2026 15:30:47 +0000
Received: from BNZP110MB2447.NAMP110.PROD.OUTLOOK.COM ([fe80::e78d:58b7:4631:fce1]) by BNZP110MB2447.NAMP110.PROD.OUTLOOK.COM ([fe80::e78d:58b7:4631:fce1%6]) with mapi id 15.21.0315.008; Fri, 14 Aug 2026 15:30:47 +0000
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "Templin (US), Fred L" <Fred.L.Templin=40boeing.com@dmarc.ietf.org>, Christopher Dearlove <christopher.dearlove@gmail.com>
Thread-Topic: draft-ietf-manet-inet-gap-analysis-06.txt
Thread-Index: AQHdK/g6EIL/aDriIUCb0YX89svfNradq8/w
Date: Fri, 14 Aug 2026 15:30:46 +0000
Message-ID: <BNZP110MB24473724566B88E9856B413EA3DAA@BNZP110MB2447.NAMP110.PROD.OUTLOOK.COM>
References: <178542889953.1430372.11902630643836405253@dt-datatracker-d4d6ff9d9-fsx7d> <BN0P110MB14208C4A410B26DE75C319C1A3C9A@BN0P110MB1420.NAMP110.PROD.OUTLOOK.COM> <BN0P110MB142013E42BCC29AB2B925E24A3D5A@BN0P110MB1420.NAMP110.PROD.OUTLOOK.COM> <26F91315-EBAA-45A6-9700-A9283D620A2E@gmail.com> <BNZP110MB2447077A740DE1A0391E7CF7A3DBA@BNZP110MB2447.NAMP110.PROD.OUTLOOK.COM> <E3EFFAC0-F30D-47DC-AAD6-0D9B33612533@gmail.com> <BNZP110MB2447ECAAA00E428038F130DAA3DAA@BNZP110MB2447.NAMP110.PROD.OUTLOOK.COM>
In-Reply-To: <BNZP110MB2447ECAAA00E428038F130DAA3DAA@BNZP110MB2447.NAMP110.PROD.OUTLOOK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=boeing.com;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: BNZP110MB2447:EE_|BN0P110MB1109:EE_
x-ms-office365-filtering-correlation-id: 33467262-7e71-40e3-9ede-08defa19035a
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;ARA:13230040|1800799024|23010399003|4022899009|366016|38070700021|4143699003|10067099003|18002099003|5023799004|56012099006|3023799007|22082099003;
x-microsoft-antispam-message-info: o5MlEUlXd2GuCVnP2sETwIPv96h7sKNNG/0EjGhDtnYsmJJBAT5S3U24kuVLm6t4f5DyE2sQQ5qMWFSGmaDVsIdRqDoS77aBn9T0yO8IDiq7/pVs6i3N8BYp9BcYXHcUijIy1W+dRKELv64CiIJ/sH4KSG5nTXVaeovloppZ7n7D8YeyQIz4vq1/XaCTE808mpqpskqEB5HZcKrG2bBYT+SPWDgn08b1282cdbAp71LqYltabbxtIRNr0fZYOTcWxGzmYcwkYSwblG3qrJfuTOv2IxYpoXhtPRJZT9fKh8HYGicYohj8ew8zz9ULhj+URt2oaz+Yr0TO6MkpYJBBGy2w0blXeTYSzl69VZ1q8/VziM1vm16fgng4HR5gWeSX4DXnCmDnMG4S+gpkl6mue39GcQUWyhN/kTyYumKB7sZOGhQjNBFDxROWYJwbA/5DROEq9iA50F2RqWBYyun9jrheQUUbHbPX3Nu3JMiFuvLTLqBK5tJDKoAldqyuIYYaHPZNYT5UinY7KbDIRAAZPrMwgaOPlBs/W72HOufnZ1fcmSIqX86ovmez3hYUecZuDL9SK3TXokc4IK3RPie7FEfZBUWgIocIOdjtidFhztZdi/gVTQfPhjfFaFQpecbQWtGZrkpeO6eXDpOj3LaU+Rsod5P6FYEw4QQ0IP/m4JaSxumgm1sS9DuKRMpb+OnNU+xEcXa2OZoUE40xGmyq+JBIYO6I9otcZKVSTM5mR0M=
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:BNZP110MB2447.NAMP110.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230040)(1800799024)(23010399003)(4022899009)(366016)(38070700021)(4143699003)(10067099003)(18002099003)(5023799004)(56012099006)(3023799007)(22082099003);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: e01xaBVBBCjEpya2haMW35cDIit2GEBIzdO6FdyBCIgwZXWewaSLuGgcGXYiwwf+zmqvLTyXPLrkeXDsU/aIZ9L+G1MB4L7f7esNu+wiTfydkTRJfvt3XsE8VsO3bj+RQN5Uz1pFziNUCxtfMw51rUp06gDT47DVjTiZONbKFu5F4JXntlDo3Va1OcFT5KQtfFy3C7+jQRWqJPdeL2Zz2yRNSZe/QuUhFGk71FBSoUrLHBJyqCnERf0x1IRqsvCK6ruRgMuujo7/vI/7bEJubvXP8glD0qUeK2AK+p+Afn86sjS+FUlftXSMRs3OMVWigKzznAguV5NxRWWpveMEXxmYjJW9aa5F98JZ1MDEGEns0x9HHkGNN1jMXfReFLNOQ03nJKej4ecXREr0/Eu5matBu3cTzqivwLr9ZyCZ+zheqxRB5Hx/OQbrMX66/oCWCsiJGY2dwqdmKRj405hVVAKYiTir97SQkoRITGI94CluxJDS0Ur8O0JTJSQh4fkrXqBRIn1dGIjX9dmSJ804BVh4HjKhe8d4HMuRsWFVuxkTbKcO3Zu/tIgKU3zYphtZXA3SfgAj8oQwBnyvDvza/gy43yktCd4KqpmvLkNZEcUV37TANpJqiunMEj+qjjROoyb3ycw/5BYnqEXXe9UHEQi31+adEm0DL2JrtnZg9Hc2mWyC4nnl/ujEioktUoaT9kCPXZAv5shVWk3tbmyHcZh1g3SlZ2SGSuhG+oRRAro098oc7hhHlaaTRVLUAlbMpG9zFijZy6TvRY5NgS1hHMpPxo9Zp3iloP5bX6pu76reCXCCVqyYqgV2Abc+TvbqXV5YdaNZab+5GQe0NPOT88eZqs9L6MB0e0cYRJbMZHC6CRemkYMptd/eN2LeAtFNDiAijfiL2rb/4phomggqqYLw8JuY2W2QzGB2D5hKf4Jq05Y4o8Gwgb83SUvfRJy2WES/Jb150T6hFux67JlWMoJvTuTEuOgvM96tWyW+Vwm5SghHhk/fver0fHsHLnZ3wLlUaQSYxp5nJOlgQre1sxiRkkNxWUvaD2jwE+MvWHepXpj/17PX59jn2svui8/gyL7arE4F381pCBzswUmVQfjOPO+wnvKOJM3lRleOGemsG6M2vk5B6oAOnlGxJJ4jn+yfh1CO1ZEVPDZPPVN/me2B9YKe3gDusewjKa3DLTO9BwYfroFVhmq4paftJVWd6V2Z0+RTsp9bjjZSIpznrBd8fazhZXvcOeOVelWmiaMZ+jt6pAJYpn2FZM1okH1CycQiK13R2BpxVXO0VCaEPRWGFrYXc3SmDgw/W5DBf8nHbqo3TQD7HW8qjRas1in6GF6i/LfhHX8qJoJRVqBWt+pqrg8Twq3I/EkTX9CHYFG7J1IilviivNO8btztuAMI+froIh6xKC/KAhD1ytXW/j8/yq5GR+9fj0NOmhkwRZJLOR7OHEjQr2PJed7La3w9r7rhvvu9mtKVh26e0sU5uYZKJAKc6XBBOeyaqAqTPgcXxjhzSiJ3QL3staFeOgMLCZsLkZLwYzQjC5O45ecVbJ8hVAF0pNpCQhBKmAs/UhbaRMbgNuH9Zc2dqr7rfz/79nHhf7kS5YahS9PKjDHEFo+NVSQLe5xU76wJk1TMufxEYslR8lYbJ/eWphBuJVZjcRxHddAo6v9HgCB7UeuGoA==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BNZP110MB2447.NAMP110.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 33467262-7e71-40e3-9ede-08defa19035a
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Aug 2026 15:30:47.0101 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bcf48bba-4d6f-4dee-a0d2-7df59cc36629
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN0P110MB1109
X-OriginatorOrg: boeing.com
X-TM-AS-GCONF: 00
Message-ID-Hash: AAIG4QEGTR6N7FPKD2VO3K22EIVDVHZE
X-Message-ID-Hash: AAIG4QEGTR6N7FPKD2VO3K22EIVDVHZE
X-MailFrom: Fred.L.Templin@boeing.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-manet.ietf.org-0; header-match-manet.ietf.org-1; header-match-manet.ietf.org-2; header-match-manet.ietf.org-3; header-match-manet.ietf.org-4; header-match-manet.ietf.org-5; header-match-manet.ietf.org-6; header-match-manet.ietf.org-7; header-match-manet.ietf.org-8; header-match-manet.ietf.org-9; header-match-manet.ietf.org-10; header-match-manet.ietf.org-11; header-match-manet.ietf.org-12; header-match-manet.ietf.org-13; header-match-manet.ietf.org-14; header-match-manet.ietf.org-15; header-match-manet.ietf.org-16; header-match-manet.ietf.org-17; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "internet-drafts@ietf.org" <internet-drafts@ietf.org>, "manet@ietf.org" <manet@ietf.org>, "i-d-announce@ietf.org" <i-d-announce@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [manet] Re: draft-ietf-manet-inet-gap-analysis-06.txt
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/iQLDyPyIuk6fi4JDvzueRGq7oYk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Owner: <mailto:manet-owner@ietf.org>
List-Post: <mailto:manet@ietf.org>
List-Subscribe: <mailto:manet-join@ietf.org>
List-Unsubscribe: <mailto:manet-leave@ietf.org>
Christopher, I am going to abandon this line of discussion: >> Authorization and key management are a red herring in this discussion. A MANET is not the same thing as a WiFi SSID as the integrity of the MANET routing information base needs to be assured. So, lower-layer security for (multi-hop) MANETs is more critical than for (single-hop) WiFi SSIDs. Just the same, people can and do operate MANETs with no lower-layer security but that may be risky out in open networks outside of controlled environments. Thank you - Fred > -----Original Message----- > From: Templin (US), Fred L <Fred.L.Templin=40boeing.com@dmarc.ietf.org> > Sent: Friday, August 14, 2026 7:22 AM > To: Christopher Dearlove <christopher.dearlove@gmail.com> > Cc: internet-drafts@ietf.org; manet@ietf.org; i-d-announce@ietf.org > Subject: [manet] Re: draft-ietf-manet-inet-gap-analysis-06.txt > > Hi Christopher, > > > -----Original Message----- > > From: Christopher Dearlove <christopher.dearlove@gmail.com> > > Sent: Thursday, August 13, 2026 4:19 PM > > To: Templin (US), Fred L <Fred.L.Templin@boeing.com> > > Cc: internet-drafts@ietf.org; manet@ietf.org; i-d-announce@ietf.org > > Subject: Re: draft-ietf-manet-inet-gap-analysis-06.txt > > > > > On 13 Aug 2026, at 22:55, Templin (US), Fred L <Fred.L.Templin@boeing.com> wrote: > > > > > > Hi Christoper, > > > > > > I appreciate these comments and take it as input that the draft should strive for better balance when talking about numbers. The intention > > is not to predict a doomsday scenario where one day all worldwide wireless infrastructure collapses leaving people's cellphones to fend for > > themselves. Yet, anyone's cellphone can at any time find itself operating outside of cellular coverage and if there are others nearby it should > > be capable of forming a MANET. > > > > Something I meant to note but didn’t i that LTE was developing a mobile to mobile interface. The interest was from emergency services. I > > don’t know if it was standardised, or even if it was if implemented. If that went more than one hop you have a MANET. But that would most > > obviously grow from a point attached the main network (which might not be the internet). Whether a pure peer to peer network with no > > attachment was considered I don’t know. And in any case, this come under the heading of pre-authorised devices. > > LTE called it "proximity services" (ProSe) which was the pre-cursor to 5G "SideLink" which 3GPP is currently writing into the standards. > > > > Yes, this might require asking someone for the shared secret key, but the technology to support the operating mode should be attainable. > > > > As soon as you say hared secret key, you’ve limited the size of your group of potential members drastically. And have to think about how to > > hare it. It’s been said encryption I say, key management is hard. (OK, here we’re talking authentication not encryption - though that is a next > > step - but same principle.) > > Authorization and key management are a red herring in this discussion. Not all MANETs will have a centralized administrative authority > responsible for handing out keys; many will be truly open access just as many WiFi SSIDs do not require a password. My Android phone lets > me turn off security on my WiFi hotspot. > > > > For this reason, I think the draft could be improved by regarding all cellphones as *potential* MANET routers. Whether many or even any > > ever become *functional* MANET routers is besides the point and not relevant to the fact that they could support the operating mode if > > programmed to do so. > > > > I’m not sure that’ the point. Erything is a potential MANET node if Android and Apple implement it. > > Cellphones have both 5G (soon to support SideLink) and WiFi (already supports mesh/IBSS) which are both excellent candidate MANET > Interface types. The hardware underpinnings for a potential MANET router are already in place in modern cellphones, and should therefore > be noted as such. > > > > Not all that long ago, not too many people imagined that one day a cellphone could act as a WiFi hotspot but in modern times that function > > is widely deployed and used all the time. I am not saying with certainty that there will come a day that all cellphones become MANET > routers, > > but the *potential* is already present in devices anyone can buy off the shelf at least from the hardware perspective. > > > > But while I use the tethering feature of ny phone a lot (right now in fact) only devices I have specifically authoried to ue that hotpot can do > so. > > And right now that is two devices (except one is failing to connect). > > The password could be removed if you wanted to allow open access to your cellphone's SSID just as many more traditional WiFi hotspots > support open access SSIDs. Access authentication is a red herring in this discussion. > > I will make a deal with you - as soon as everyone stops using their phones as WiFi hotspots I will stop saying cellphones are potential MANET > routers. > > Thank you - Fred > > > > Thank you - Fred > > > > > >> -----Original Message----- > > >> From: Christopher Dearlove <christopher.dearlove@gmail.com> > > >> Sent: Thursday, August 13, 2026 12:39 PM > > >> To: Templin (US), Fred L <Fred.L.Templin@boeing.com> > > >> Cc: internet-drafts@ietf.org; manet@ietf.org; i-d-announce@ietf.org > > >> Subject: draft-ietf-manet-inet-gap-analysis-06.txt > > >> > > >> I haven’t made this comment before, but have been thinking about it. > > >> > > >> I am not convinced that the suggestion that there are billions of devices that might connect to a MANET is helpful. > > >> > > >> There are billions of phones out there. But for various reasons the architecture used is not a MANET. An important reason why is access > > >> control. When you attempt to use your mobile phone, the base station you are trying to connect to verifies you are authored to do so. To > > that > > >> end it (or other parts of the network on its behalf) consults database(s) to determine both that and other information. Of course that is > > highly > > >> optimised in various ways, but that’s not important here, the key thing is that your phone is verified (and cryptographic stuff to confirm > that > > >> and more is done, again details not important here). > > >> > > >> Why? Well, most importantly from the point of view of the operators is so they get paid. Also for various security related reasons. > > >> > > >> Now let’s consider a MANET. There are two obvious scenarios here. A small private network and a larger public network. > > >> > > >> Let’s start with the small private network. Yes, there might be quite a lot more potential members than actual members at any time, but > > it’s > > >> still not in the billions range. Typical use case is an emergency services network (or a military network, though we tend not to mention > that > > in > > >> RFCs). We have RFC 7183 whose purpose is to manage access to an OLSRv2 network. The specific methods in there assume a shared > > secret > > >> key, although there is an alternative in RFC 7859, but both involve some sort of key distribution to all potential participants. That is hard > > >> enough at the hundreds or thousands level. > > >> > > >> Or there’s a network with public access. The likely equivalent to that is the Wi-Fi networks we find everywhere. Where typically we learn > a > > >> key from a written instruction in our coffee shop or hotel. Or - popular on trains - there’ an authentication process that involves email > > >> addresses and network access. That’s not going help us, we will usually need security at a lower level and sooner. And doe this have to be > > >> free? > > >> > > >> (I would be interested to know how the Freifunk network works here. Its it a third case? Or a variant of one of these?) > > >> > > >> Of course in the latter case billions is not irrelevant, but mostly because what it says is pre-existing addresses are unplanned and non- > > >> aggregatable. That happens well before billions. Unless new addresses are issued. But we still have the problem of how (assuming > > completely > > >> unsecured networks are not allowed in most cases and/or that someone wants to be paid) of how some sort of identity or key > information > > is > > >> to be distributed. For the small private network where billions of users is not relevant, OK. For a network with internet access, maybe OK. > > For > > >> an isolated MANET as often assumed, not so OK. > > >> > > >> My point is that rising the billions of users without addressing these issues - at least making them problems - is likely to lead to > discussions > > of > > >> the form above (or better ones) and hinder any progress of the draft. > > > > > _______________________________________________ > manet mailing list -- manet@ietf.org > To unsubscribe send an email to manet-leave@ietf.org
- [manet] Re: draft-ietf-manet-inet-gap-analysis-06… Christopher Dearlove
- [manet] I-D Action: draft-ietf-manet-inet-gap-ana… internet-drafts
- [manet] Re: draft-ietf-manet-inet-gap-analysis-06… Templin (US), Fred L
- [manet] Re: I-D Action: draft-ietf-manet-inet-gap… Templin (US), Fred L
- [manet] Issue tracker (RE: I-D Action: draft-ietf… Templin (US), Fred L
- [manet] Re: draft-ietf-manet-inet-gap-analysis-06… Christopher Dearlove
- [manet] Re: draft-ietf-manet-inet-gap-analysis-06… Templin (US), Fred L
- [manet] draft-ietf-manet-inet-gap-analysis-06.txt Christopher Dearlove
- [manet] Re: draft-ietf-manet-inet-gap-analysis-06… Templin (US), Fred L
- [manet] Re: draft-ietf-manet-inet-gap-analysis-06… Christopher Dearlove
- [manet] Re: draft-ietf-manet-inet-gap-analysis-06… Templin (US), Fred L
- [manet] Re: draft-ietf-manet-inet-gap-analysis-06… Templin (US), Fred L
- [manet] Re: draft-ietf-manet-inet-gap-analysis-06… Christopher Dearlove
- [manet] Re: draft-ietf-manet-inet-gap-analysis-06… Templin (US), Fred L
- [manet] Re: draft-ietf-manet-inet-gap-analysis-06… Abdussalam Baryun
- [manet] Re: I-D Action: draft-ietf-manet-inet-gap… Abdussalam Baryun
- [manet] L2/L3 MANETs (Re: Re: I-D Action: draft-i… Templin (US), Fred L
- [manet] Re: L2/L3 MANETs (Re: Re: I-D Action: dra… Abdussalam Baryun
- [manet] Re: L2/L3 MANETs (Re: Re: I-D Action: dra… Templin (US), Fred L