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:35 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 8E9EB1A9110 for <v6ops@ietfa.amsl.com>; Thu, 7 Jan 2016 09:35:05 -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 IXsV1Wv3ynsg for <v6ops@ietfa.amsl.com>; Thu, 7 Jan 2016 09:35:03 -0800 (PST)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (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 A9C5E1A910E for <v6ops@ietf.org>; Thu, 7 Jan 2016 09:35:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u07HZ2vQ026204; Thu, 7 Jan 2016 11:35:02 -0600
Received: from XCH-BLV-306.nw.nos.boeing.com (xch-blv-306.nw.nos.boeing.com [130.247.25.218]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u07HYwTX026083 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 7 Jan 2016 11:34:59 -0600
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.52]) by XCH-BLV-306.nw.nos.boeing.com ([169.254.6.160]) with mapi id 14.03.0235.001; Thu, 7 Jan 2016 09:34:58 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "VAN DE VELDE, Gunter (Nokia - BE)" <gunter.van_de_velde@alcatel-lucent.com>, "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//4agAIAAgaTQ
Date: Thu, 07 Jan 2016 17:34:57 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832F9BFED@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>
In-Reply-To: <33FC69DB-7389-4AA3-B1D0-DC1016C134DD@alcatel-lucent.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/dnMrCOMu9X7df0L_VYjDR5-W0B4>
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:35:05 -0000
Hi Gunter, > -----Original Message----- > From: VAN DE VELDE, Gunter (Nokia - BE) [mailto:gunter.van_de_velde@alcatel-lucent.com] > Sent: Thursday, January 07, 2016 9:14 AM > To: Templin, Fred L; draft-ietf-v6ops-unique-ipv6-prefix-per-host@tools.ietf.org > Cc: v6ops@ietf.org WG > Subject: Re: [v6ops] Focused discussion: draft-ietf-v6ops-unique-ipv6-prefix-per-host > > > > > > > On 07/01/16 17:56, "Templin, Fred L" <Fred.L.Templin@boeing.com> wrote: > > >Hi Gunter, > > > >Maybe I am not understanding you correctly. There may be many APs (100's, 1000's, etc.) > >associated with a single WLAN-GW - correct? > > GV> Yep, there can be indeed. I start to see where the confusion came from. MAC address spoofing is MAC address spoofing - whether there is 1 AP or 1000, and whether there is mobility or no mobility. I don't think there is any confusion. Where I am trying to understand is whether completely unmodified and COTS UEs can be used without there being a danger of MAC address spoofing DoS, or whether the UEs need to be enrolled in the service offered by the community WiFi provider. By "enrolled", I mean entered into the provider's PKI and given a cert, or something like that. Thanks - Fred fred.l.templin@boeing.com > >At each AP, a UE presents itself using its > >MAC address and initially sends out an RS using an IPv6 link-local address most likely > >derived from the MAC address. The AP (acting in bridge mode) then forwards the > >RS to the WLAN-GW which needs to have some way of knowing that the RS came > >from an authentic source. (You have said that the MAC address is the identifier for > >the UE - but, does the WLAN-GW see the MAC address, or does it only see the > >link-local address?) > > GV> AP is bridging from wifi to GRE tunnel, so the WLAN-GW sees MAC address indeed > > > > >Now, consider a UE 'A' associated with AP 'X' and a UE 'B' associated with AP 'Y'. > >A is the authentic owner of MAC address 'M'. When A associates with X, the > >WLAN-GW goes through the authentication procedures based on the MAC > >address M (or the IPv6 link-local address associated with MAC address M). > >But now, B associates with Y and also uses MAC address M. (Or, maybe B > >associates with Y before A associates with X.) What is to stop B from spoofing > >the MAC address in this way and DoS'ing A? > > GV> both AP’s use their own different SoftGRE tunnel to the WLAN-GW, and that is how WLAN-GW finds out they are different > because the tunnel can be part of the key. Ofcours UE mobility and other advanced features can be enabled on the WLAN-GW using > alternate authentication mechanisms, but that is beyond the scope of this particular draft as that drives pretty far into vendor > capability territory and i believe that is beyond v6ops scope. > > Be well, > G/ > > >
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- [v6ops] Focused discussion: draft-ietf-v6ops-uniq… fred
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Lorenzo Colitti
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Lorenzo Colitti
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Tore Anderson
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Brzozowski, John
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Brzozowski, John
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Tom Herbert
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Mark Smith
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… David Farmer
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Brzozowski, John
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Brzozowski, John
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Brzozowski, John
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Fred Baker (fred)
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… David Farmer
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… joel jaeggli
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… David Farmer
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Eric Vyncke (evyncke)
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… David Farmer
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… David Farmer
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… David Farmer
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Eric Vyncke (evyncke)
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… Templin, Fred L
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… VAN DE VELDE, Gunter (Gunter)
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… VAN DE VELDE, Gunter (Gunter)
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… VAN DE VELDE, Gunter (Nokia - BE)
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… VAN DE VELDE, Gunter (Nokia - BE)
- Re: [v6ops] Focused discussion: draft-ietf-v6ops-… VAN DE VELDE, Gunter (Nokia - BE)