Re: [Iotops] Automatically connecting to stub networks...
"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Mon, 07 December 2020 19:38 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 3FAE53A07AE; Mon, 7 Dec 2020 11:38:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_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 Zx27MwcUYdfL; Mon, 7 Dec 2020 11:38:19 -0800 (PST)
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 893D93A0766; Mon, 7 Dec 2020 11:38:19 -0800 (PST)
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 0B7JcGpm001259; Mon, 7 Dec 2020 14:38:18 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1607369898; bh=FNKtuR0CeMAL2pkOcKQp32jl6Eh+QKwMcul3jN9+IM8=; h=From:To:CC:Subject:Date:From; b=t0rJ8+77vsHKsublBH65IFTSgPupuHt3bZJJp89+TSVNmELbhG3FK8bUhmF4qYMVA s9Qa2uoaN8Hblq1YxoPFZI66U5DXetvByjAX0S1xVEne5wGSC53iJZwqqn5gegxJSV wvTc/Y9OqiCq/brRJpnuJY4iiJC/OtsK4OB6tUKvsF+FRFTEoOJtZwFfd1DXJECjvl znXkCDtuZA58at44wpicY/jnm7RrXajkeYIOwJNpY1xOpwlrilGkxFEnXRgpZTo1vy SwNd1+Gd18UvPhmUSU8nAubECYfowKiqRlV8l6qprtRzNSZ0frdxlor4E8Wyz+pSZX pleL6aXmIhGhA==
Received: from XCH16-07-10.nos.boeing.com (xch16-07-10.nos.boeing.com [144.115.66.112]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 0B7JcEvK001238 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 7 Dec 2020 14:38:14 -0500
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_CBC_SHA384) id 15.1.2044.4; Mon, 7 Dec 2020 11:38:13 -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; Mon, 7 Dec 2020 11:38:13 -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: AdbMz9OConAqMYjZtUCg6orRClX9ig==
Date: Mon, 07 Dec 2020 19:38:13 +0000
Message-ID: <2f1c1e67b96844ce934add51ef2c5f4d@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: C903505243D0C0D45BE205C7E0A8500541F541E74DA9712BB3812426EF6FEF262000:8
Content-Type: multipart/alternative; boundary="_000_2f1c1e67b96844ce934add51ef2c5f4dboeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/JJYSax7izYg5r-KBhZRNxuoJcYM>
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: Mon, 07 Dec 2020 19:38:22 -0000
Ted, please have another look: https://datatracker.ietf.org/doc/draft-templin-6man-omni-interface/ It now places a fully-formed DHCPv6 message inside of an OMNI option in RS/RA messages so the stub network node can do DHCPv6-PD at the same time it does RS/RA (this is something I have talked about before). However, right now it only allows for a small-message DHCPv6 exchange from within each RS/RA, which should provide ample space for most stub network DHCPv6-PD users. Does it look like enough, or should we support bigger? Thanks - Fred From: Ted Lemon [mailto:mellon@fugue.com] Sent: Friday, December 04, 2020 5:27 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... This message was sent from outside of Boeing. Please do not click links or open attachments unless you recognize the sender and know that the content is safe. I can’t see that being useful for stub networks. The whole point of “stub” is to avoid complicated routing, since it’s not useful for a typical stub network. On Dec 4, 2020, at 19:46, Templin (US), Fred L <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>> wrote: 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<mailto:Fred.L.Templin@boeing.com>> Cc: STARK, BARBARA H <bs7652@att.com<mailto:bs7652@att.com>>; Michael Richardson <mcr+ietf@sandelman.ca<mailto:mcr+ietf@sandelman.ca>>; Ole Trøan <otroan@employees.org<mailto:otroan@employees.org>>; 6MAN <6man@ietf.org<mailto:6man@ietf.org>>; iotops@ietf.org<mailto: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.
- Re: [Iotops] Automatically connecting to stub net… Michael Richardson
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… Michael Richardson
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… Behcet Sarikaya
- Re: [Iotops] Automatically connecting to stub net… Qin Wu
- Re: [Iotops] Automatically connecting to stub net… Michael Richardson
- Re: [Iotops] Automatically connecting to stub net… Toerless Eckert
- Re: [Iotops] Automatically connecting to stub net… Michael Richardson
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… Michael Richardson
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… Michael Richardson
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… Toerless Eckert
- Re: [Iotops] Automatically connecting to stub net… otroan
- Re: [Iotops] Automatically connecting to stub net… Toerless Eckert
- Re: [Iotops] Automatically connecting to stub net… otroan
- Re: [Iotops] Automatically connecting to stub net… Michael Richardson
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… STARK, BARBARA H
- Re: [Iotops] Automatically connecting to stub net… Templin (US), Fred L
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… Templin (US), Fred L
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] Automatically connecting to stub net… Philip Homburg
- Re: [Iotops] Automatically connecting to stub net… Philip Homburg
- Re: [Iotops] Automatically connecting to stub net… Templin (US), Fred L
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon
- Re: [Iotops] [EXTERNAL] Re: Automatically connect… Templin (US), Fred L
- Re: [Iotops] [EXTERNAL] Automatically connecting … Ted Lemon
- Re: [Iotops] [EXTERNAL] Re: Automatically connect… Mark Smith
- Re: [Iotops] Automatically connecting to stub net… Templin (US), Fred L
- Re: [Iotops] Automatically connecting to stub net… Ted Lemon