Re: [Iotops] Automatically connecting to stub networks...

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Sat, 05 December 2020 00:46 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38F3E3A1115; Fri, 4 Dec 2020 16:46:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level:
X-Spam-Status: No, score=-2.118 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_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 OftPQzpDHjbj; Fri, 4 Dec 2020 16:46:47 -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 957593A110F; Fri, 4 Dec 2020 16:46:45 -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 0B50kYnl007301; Fri, 4 Dec 2020 19:46:44 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1607129204; bh=UDDqe1UP3HAuB+tBIFPtUu51xRqhr6SyjRW0dlq53NM=; h=From:To:CC:Subject:Date:From; b=dA3RUoUbNXSmCqHMEoxUAYxoEF9O1FHwihS8PXDLVhJzifV0DY2jRW8XjBOFFD9sd DhEyq/Fx78wbtQC4nTsRDzkZPHbE2/88aA3MDZHE7wxNBY3EfBDzaVWiCK7kcli07B zdLoWi7EsnYHTieaQ5nUaLdQxlIeqnBpqm5VsLyIvKLWBSBoIrHo0e2WuTRzRJi2kx sgkt8VD/S99FHeQofhKsJCB/Ss6p1R0iVf130RV9Epq5zwGHQc1UiGrPU+IR0aSIqF vdX+ZbWK5RlDMP/aYXr13Y7bE0O9U4Jj7yLVWB/Pj1379UpbaOxg+q0bQp4di8pjEg JmbeDIotJK9Ng==
Received: from XCH16-07-12.nos.boeing.com (xch16-07-12.nos.boeing.com [144.115.66.114]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 0B50kUPo007282 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 4 Dec 2020 19:46:30 -0500
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_CBC_SHA384) id 15.1.2044.4; Fri, 4 Dec 2020 16:46:29 -0800
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.2044.004; Fri, 4 Dec 2020 16:46:29 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Ted Lemon <mellon@fugue.com>
CC: "STARK, BARBARA H" <bs7652@att.com>, Michael Richardson <mcr+ietf@sandelman.ca>, Ole Trøan <otroan@employees.org>, 6MAN <6man@ietf.org>, "iotops@ietf.org" <iotops@ietf.org>
Thread-Topic: [Iotops] Automatically connecting to stub networks...
Thread-Index: AdbKno8gonAqMYjZtUCg6orRClX9ig==
Date: Sat, 05 Dec 2020 00:46:29 +0000
Message-ID: <fd7723f643064600b8037105529017e1@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: D8FC507F378D27BB6F041465F1D72DFBDB72B0FEFE782B0E84BC8BE2985F3B372000:8
Content-Type: multipart/alternative; boundary="_000_fd7723f643064600b8037105529017e1boeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/R6sH1xAHx0gPPtZciqB7heugVX8>
Subject: Re: [Iotops] Automatically connecting to stub networks...
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Dec 2020 00:46:49 -0000

Ted, the only aspects of OMNI you would need to see to grasp the concepts
are a quick scan of Sections 9.1.9 and 12.3 (approx. 1.25 total pages of text).

Basically, it imports DHCPv6 options into RS messages and asks the router
to send a “proxy DHCPv6-PD Solicit” to the DHCPv6 server on behalf of the
mobile node. After the router gets back the DHCPv6-PD Reply, it sends an
RA to the mobile node with the delegated prefix information.

This is something I suggested a long time ago, but that was before we had
the OMNI option concept. Now with the OMNI option, it can carry other
protocol information like DHCPv6 options just fine.

Fred

From: Ted Lemon [mailto:mellon@fugue.com]
Sent: Friday, December 04, 2020 3:15 PM
To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
Cc: STARK, BARBARA H <bs7652@att.com>; Michael Richardson <mcr+ietf@sandelman.ca>; Ole Trøan <otroan@employees.org>; 6MAN <6man@ietf.org>; iotops@ietf.org
Subject: [EXTERNAL] Re: [Iotops] Automatically connecting to stub networks...

On Dec 4, 2020, at 6:12 PM, Templin (US), Fred L <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>> wrote:
DHCPv6-PD fans, please have a look at the latest OMNI draft and see if it provides
the kind of prefix delegation services you would like to see for stub networks:

If you are extending DHCPv6-PD for OMNI, you should really do it as a separate document. OMNI is rather large, so making references to it isn’t ideal.

The only thing we need that isn’t specified anywhere is for the infrastructure router to add the prefix and destination to the routing infrastructure.