Re: [v6ops] Focused discussion: draft-ietf-v6ops-unique-ipv6-prefix-per-host

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 07 January 2016 17:55 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE451A9132 for <v6ops@ietfa.amsl.com>; Thu, 7 Jan 2016 09:55:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 OlxfAVk-qerN for <v6ops@ietfa.amsl.com>; Thu, 7 Jan 2016 09:55:30 -0800 (PST)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (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 8F6E21A9131 for <v6ops@ietf.org>; Thu, 7 Jan 2016 09:55:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u07HtZpU019507; Thu, 7 Jan 2016 09:55:35 -0800
Received: from XCH-BLV-208.nw.nos.boeing.com (xch-blv-208.nw.nos.boeing.com [10.57.37.5]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u07HtVKw019321 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 7 Jan 2016 09:55:31 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.52]) by XCH-BLV-208.nw.nos.boeing.com ([169.254.8.46]) with mapi id 14.03.0235.001; Thu, 7 Jan 2016 09:55:25 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "draft-ietf-v6ops-unique-ipv6-prefix-per-host@tools.ietf.org" <draft-ietf-v6ops-unique-ipv6-prefix-per-host@tools.ietf.org>
Thread-Topic: [v6ops] Focused discussion: draft-ietf-v6ops-unique-ipv6-prefix-per-host
Thread-Index: AQHRRrIFI13RUsgT4kOKL/Th7Sw3uJ7vFi6A///VyTCAAW6RgP//3BOwgACOkQD//3qM8AARiNiAABB1ZDD//4agAIAAgaTQgAEA0zA=
Date: Thu, 07 Jan 2016 17:55:24 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832F9C052@XCH-BLV-504.nw.nos.boeing.com>
References: <201601031900.u03J0LMe009763@irp-lnx1.cisco.com> <CAKD1Yr3RY1oUtQnN675djc22f7B1Fhx0Ntsmr9rmZVEqmygRDg@mail.gmail.com> <D2B2F846.63BCC%evyncke@cisco.com> <2134F8430051B64F815C691A62D9831832F9ADDE@XCH-BLV-504.nw.nos.boeing.com> <E0AC9F63-5C23-4E79-8B5F-63E3168AE162@alcatel-lucent.com> <2134F8430051B64F815C691A62D9831832F9BC14@XCH-BLV-504.nw.nos.boeing.com> <7B3ACA5B-FB06-45B6-BE6E-B2D1FB26C0B9@alcatel-lucent.com> <2134F8430051B64F815C691A62D9831832F9BD05@XCH-BLV-504.nw.nos.boeing.com> <2D68058C-981F-4037-80C4-AFF88D8A2997@alcatel-lucent.com> <2134F8430051B64F815C691A62D9831832F9BF23@XCH-BLV-504.nw.nos.boeing.com> <33FC69DB-7389-4AA3-B1D0-DC1016C134DD@alcatel-lucent.com> <2134F8430051B64F815C691A62D9831832F9BFED@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832F9BFED@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/piCwRM-hA7NcM4S2Fubsvc8915s>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Focused discussion: draft-ietf-v6ops-unique-ipv6-prefix-per-host
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2016 17:55:32 -0000

People have asked about overlap between this work and AERO. The overlap
is in the way SoftGRE works in comparison with the AERO link model. SoftGRE
to my understanding is just another example of a Non-Broadcast, Multiple
Access (NBMA) tunnel virtual overlay in exactly the same fashion as for AERO.
The AP is analogous to the AERO Client, and the WLAN-GW is analogous to
the AERO Server. That the APs are bridging instead of providing a terminus
for prefix delegation is unique to this work, and not covered by AERO. But,
the tunnel virtual link model is one and the same.

That said, AERO can benefit this work through the manner in which multiple
WLAN-GWs can be networked to create a global routing system that can
sustain UE-to-prefix associations wherever the UEs happen to pop up in
the global community WiFi routing structure. It can be handled through
the addition of a new construct which I am calling the "WLAN-RELAY",
which is analogous to the AERO Relay, and through the introduction of
a private BGP instance that keeps track of all UE-to-WLAN-GW associations.
 I explained how this all works in my message to Gert several messages back,
and I would like to offer this as input to the authors of this draft:

https://mailarchive.ietf.org/arch/msg/v6ops/jN0vAnHPchobrHTp22tjQbFjGN4
https://datatracker.ietf.org/doc/draft-templin-aerolink/

Thanks - Fred
fred.l.templin@boeing.com