Re: [DMM] Mobility Exposure and Selection WT call
Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 24 April 2015 16:36 UTC
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E3B01ACC83 for <dmm@ietfa.amsl.com>; Fri, 24 Apr 2015 09:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 XDaAOx3fYU_N for <dmm@ietfa.amsl.com>; Fri, 24 Apr 2015 09:36:15 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5DB21A1BD2 for <dmm@ietf.org>; Fri, 24 Apr 2015 09:36:14 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t3OGa7mx013908; Fri, 24 Apr 2015 18:36:07 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C23EA2034C7; Fri, 24 Apr 2015 18:37:35 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B298A202091; Fri, 24 Apr 2015 18:37:35 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t3OGZqkk025846; Fri, 24 Apr 2015 18:36:07 +0200
Message-ID: <553A70E8.2010304@gmail.com>
Date: Fri, 24 Apr 2015 18:35:52 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Jouni Korhonen <jouni.nospam@gmail.com>, "dmm@ietf.org" <dmm@ietf.org>
References: <A730EA79-F6CF-49CD-9933-9FDA4AA75541@yegin.org> <556A06B1-A71C-45DC-A5FB-66CC8ECF47B8@yegin.org> <223129BA-541E-4C56-9364-6C2B8A5A1D3B@yegin.org> <29DDE580-C9A3-4825-8C0B-CF6844438BEC@yegin.org> <54DB49BF.9090702@gmail.com> <4238F47D-1284-46D3-AF61-F173E4A3BDBE@yegin.org> <54E5A34C.2030106@gmail.com> <75DD1093-4761-4E0C-A5B9-1A1A96D850CE@yegin.org> <54E60579.5090401@gmail.com> <55144953.8070104@gmail.com> <55144D3F.2030002@gmail.com> <551481F8.9090507@gmail.com> <2134F8430051B64F815C691A62D9831832E2E10A@XCH-BLV-504.nw.nos.boeing.com> <5536A823.9070803@gmail.com> <2134F8430051B64F815C691A62D9831832E4FA76@XCH-BLV-504.nw.nos.boeing.com> <5537D364.1010906@gmail.com> <2134F8430051B64F815C691A62D9831832E4FB26@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832E4FB26@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmm/Lu6OolX9UrV-48OgpgjvSMFHOB8>
Subject: Re: [DMM] Mobility Exposure and Selection WT call
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2015 16:36:19 -0000
Hi Fred, Le 22/04/2015 19:22, Templin, Fred L a écrit : > Hi Alex, > >> -----Original Message----- >> From: Alexandru Petrescu [mailto:alexandru.petrescu@gmail.com] >> Sent: Wednesday, April 22, 2015 9:59 AM >> To: Templin, Fred L; Jouni Korhonen; dmm@ietf.org >> Subject: Re: [DMM] Mobility Exposure and Selection WT call >> >> Le 22/04/2015 18:51, Templin, Fred L a écrit : >>> Hi Alex, >>> >>>> -----Original Message----- >>>> From: Alexandru Petrescu [mailto:alexandru.petrescu@gmail.com] >>>> Sent: Tuesday, April 21, 2015 12:42 PM >>>> To: Templin, Fred L; Jouni Korhonen; dmm@ietf.org >>>> Subject: Re: [DMM] Mobility Exposure and Selection WT call >>>> >>>> Le 31/03/2015 00:42, Templin, Fred L a écrit : >>>>> Hi Alex, >>>>> >>>>>> -----Original Message----- From: dmm [mailto:dmm-bounces@ietf.org] >>>>>> On Behalf Of Alexandru Petrescu Sent: Thursday, March 26, 2015 3:03 >>>>>> PM To: Jouni Korhonen; dmm@ietf.org Subject: Re: [DMM] Mobility >>>>>> Exposure and Selection WT call >>>>>> >>>>>> Le 26/03/2015 13:17, Jouni Korhonen a écrit : >>>>>>> Alex, >>>>>>> >>>>>>> 3/26/2015, 11:00 AM, Alexandru Petrescu kirjoitti: >>>>>>> >>>>>>> [snip] >>>>>>> >>>>>>>>> I thought by "fixed" you meant it stays the same wherever the >>>>>>>>> Host goes (something like the Home Address). >>>>>>>> >>>>>>>> Alper - I think a LL address can also be qualified as 'fixed' - >>>>>>>> it never changes. >>>>>>> >>>>>>> Does LL here mean link-local or link-layer? If it is the former >>>>>>> one, then the above assertion is not correct. >>>>>> >>>>>> Link-local. >>>>>> >>>>>> And you seem to say a link-local address is not fixed? I think >>>>>> link-local addresses _are_ fixed set in stone. They are formed >>>>>> locally without need of help from router. >>>>> >>>>> AERO provides a fixed link-local address that is formed from a >>>>> prefix received by DHCPv6 Prefix Delegation (PD). >>>> >>>> Fred - but why should this ll prefix be provided by DHCP? Is it of >>>> variable value? Or is the link-local constant all the time? (in which >>>> case it could be hardcoded everywhere). >>> >>> DHCPv6 Prefix Delegation delegates an IPv6 prefix to the AERO >>> Client (e.g., 2001:db8:1:2::/64). The Client then constructs an >>> AERO link-local address from the prefix as fe80::2001:db8:1:2 >>> (i.e., it embeds the 64-bit prefix from the prefix delegation in >>> the 64-bit interface identifier of an IPv6 link-local address). >> >> Fred, that looks weird. Never saw a prefix to be used as an Interface >> Identifier. > > It is specified in the AERO document and also cited in RFC7421. There are > lots of weird "address within address" encapsulations in common use > within the IPv6 interface identifier (e.g., ISATAP address, etc.) and > this I think is in some ways less weird than some of the others. Ok. >> I guess this breaks the DHCP prefix delegation specification. > > Not at all; I have running code that uses unmodified public domain > DHCPv6 clients and servers. On the server side, I was using ISC > DHCP but have recently moved over to a great new server package > called Kea (also from ISC). > >> Why does not the DHCPv6 server assign a link-local address altogether >> (rather than assigning a prefix, to be used as an IID). > > Because the prefix length may be different than /64; hence, the > Client needs to receive the prefix in a DHCPv6 IA_PD option. What if DHCP had an option to provide an Interface ID (instead of Prefix Delegation)? Wouldnt that be more appropriate to form a link-local address with that Interface ID? Alex > > Thanks - Fred > fred.l.templin@boeing.com > >> Alex >> >>> Once the prefix delegation and AERO address configuration >>> are done, they stay fixes as long as the Client remains >>> associated with the same AERO link. >>> >>>>> Once the AERO Client is given a PD (either IPv6 or IPv4) it can form >>>>> an AERO link-local address that stays the same wherever the Client >>>>> moves and with no need to perform Duplicate Address Detection (DAD). >>>>> It makes IPv6 ND simple and seamless. >>>> >>>> Is that prefix fe80::/10? >>> >>> No, it would be a global IPv6 prefix like 2001:db8:1:2::/64. The AERO link >>> has an associated AERO Service Prefix (e.g., 2001:db8::/32) from which >>> longer global IPv6 prefixes are delegated to each Client. The Client then >>> gets to keep and continually use its prefix delegation as long as it stays >>> associated with the same AERO link. >>> >>> Thanks - Fred >>> fred.l.templin@boeing.com >>> >>>> Alex >>>> >>>>> >>>>> Thanks - Fred fred.l.templin@boeing.com >>>>> >>>>>> Alex >>>>>> >>>>>>> >>>>>>> - Jouni >>>>>>> >>>>>>>> >>>>>>>> I think it's hard to disagree with that, no? >>>>>>>> >>>>>>>> Alex >>>>>>>> >>>>>>>>> >>>>>>>>> So, I guess, I should have referred to the "nomadic" address >>>>>>>>> to mean the one that is constant, wherever the Host goes. >>>>>>>>> >>>>>>>>> As such, my suggestion is that a "nomadic" address can never >>>>>>>>> be an RFC7217 address. >>>>>>>>> >>>>>>>>> In practice that would mean that if you configure an address >>>>>>>>> to be "nomadic" you must also tell the kernel to not run >>>>>>>>> RFC7217 on it. >>>>>>>>> >>>>>>>>> But ok, one might think that these two aspects ("nomadic" and >>>>>>>>> RFC7217) are orthogonal at this point in time. >>>>>>>>> >>>>>>>>> Alex >>>>>>>>> >>>>>>>>>> >>>>>>>>>> I don't know if it makes sense to request a fixed and >>>>>>>>>> random-based IP address. But if someone does it, it works. >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Alper >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>>>> - configured by SLAAC, by DHCPv6, by PPP, or >>>>>>>>>>>>> registered (RFC 6775). >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Orthogonal. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> E.g. a nomadic address could never be a link-local >>>>>>>>>>>>> address. >>>>>>>>>>>>> >>>>>>>>>>>>>> #2. Describe how IP address type information is >>>>>>>>>>>>>> conveyed from network to MN. >>>>>>>>>>>>> >>>>>>>>>>>>> If one designs a protocol to convey address type >>>>>>>>>>>>> information from the network to the end node, then >>>>>>>>>>>>> one could also add the other types mentioned above. >>>>>>>>>>>>> >>>>>>>>>>>>> SLAAC could never 'convey' the address type to the >>>>>>>>>>>>> end-node, because SLAAC is an operation happening >>>>>>>>>>>>> with as heavy weight from the Server (router) as from >>>>>>>>>>>>> the Client (Host): the Router decides the prefix but >>>>>>>>>>>>> the Client decides the Interface ID. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Still, the network can convey the type of IP address to >>>>>>>>>>>> the host. Also, one can imagine augmenting Router >>>>>>>>>>>> Solicitation to let the host convey its requested >>>>>>>>>>>> type. >>>>>>>>>>> >>>>>>>>>>> I agree. >>>>>>>>>>> >>>>>>>>>>> Alex >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>> Address Registration Option of 6lo and BTLE would >>>>>>>>>>>>> have the Host conveying this information to the >>>>>>>>>>>>> Router (and not vice-versa). >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> OK. >>>>>>>>>>>> >>>>>>>>>>>> Alper >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> Yours, >>>>>>>>>>>>> >>>>>>>>>>>>> Alex >>>>>>>>>>>>> >>>>>>>>>>>>>> WT agreed to use draft-yegin-dmm-ondemand-mobility >>>>>>>>>>>>>> as the baseline for item#1 (the API). A revision of >>>>>>>>>>>>>> the draft will also include a new section to cover >>>>>>>>>>>>>> backward compatibility (Danny will provide the >>>>>>>>>>>>>> draft text). Comments on the draft are welcome. >>>>>>>>>>>>>> >>>>>>>>>>>>>> The next call will be about items #2/#3 (IP >>>>>>>>>>>>>> address configuration enhancements associated with >>>>>>>>>>>>>> the API). We intend to schedule that one in about 2 >>>>>>>>>>>>>> weeks. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Alper >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Feb 9, 2015, at 9:59 AM, Alper Yegin wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Folks, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> See below for the Webex details. Remember, the >>>>>>>>>>>>>>> call is on Tue, Feb 10, at 4pm CET. And don't >>>>>>>>>>>>>>> forget to read the documents in the reading list >>>>>>>>>>>>>>> prior to the call. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Attendees _shall read _the following material >>>>>>>>>>>>>>>> before the call so that we can directly jump to >>>>>>>>>>>>>>>> the discussions: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 1. >>>>>>>>>>>>>>>> http://www.ietf.org/proceedings/91/slides/slides-91-dmm-4.pdf >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> 2. http://www.ietf.org/proceedings/90/slides/slides-90-dmm-6.pdf >>>>>>>>>>>>>>>> 3. >>>>>>>>>>>>>>>> https://datatracker.ietf.org/doc/draft-yegin-dmm-ondemand-mobility/ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> 4. http://www.ietf.org/proceedings/88/slides/slides-88-dmm-8.pdf >>>>>>>>>>>>>>>> 5. >>>>>>>>>>>>>>>> http://tools.ietf.org/html/draft-liu-dmm-mobility-api-02 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> Alper >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *DMM - Mobility Exposure and Selection WT* >>>>>>>>>>>>>>> Tuesday 10 February 2015 16:00 | Europe Time >>>>>>>>>>>>>>> (Paris, GMT+01:00) | 1 hr 30 min >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *Join WebEx meeting* >>>>>>>>>>>>>>>> <https://ietf.webex.com/ietf/j.php?MTID=m1dad9871a277ff2ab142ae8ff4b77ad3> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> Meeting number:641 085 326 >>>>>>>>>>>>>>>> Meeting password:dmm1911 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *Join by phone* *1-877-668-4493* Call-in toll >>>>>>>>>>>>>>>> free number (US/Canada) *1-650-479-3208* >>>>>>>>>>>>>>>> Call-in toll number (US/Canada) Access code: >>>>>>>>>>>>>>>> 641 085 326 Toll-free calling restrictions >>>>>>>>>>>>>>>> <http://www.webex.com/pdf/tollfree_restrictions.pdf> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> Add this meeting >>>>>>>>>>>>>>>> <https://ietf.webex.com/ietf/j.php?MTID=m0855d524ccb7239248d0ce34e19f38c8> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> to your calendar. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Can't join the meeting? Contact support. >>>>>>>>>>>>>>>> <https://ietf.webex.com/ietf/mc> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> IMPORTANT NOTICE: Please note that this WebEx >>>>>>>>>>>>>>>> service allows audio and other information sent >>>>>>>>>>>>>>>> during the session to be recorded, which may be >>>>>>>>>>>>>>>> discoverable in a legal matter. By joining this >>>>>>>>>>>>>>>> session, you automatically consent to such >>>>>>>>>>>>>>>> recordings. If you do not consent to being >>>>>>>>>>>>>>>> recorded, discuss your concerns with the host >>>>>>>>>>>>>>>> or do not join the session. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> <WebEx_Meeting.ics> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Jan 27, 2015, at 11:12 AM, Alper Yegin wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Poll is closed, and majority selected the >>>>>>>>>>>>>>>> following date for the call: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Feb 10, 4pm CET. 1,5hr call. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Please mark your calendars. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> In this call, we'll aim making progress on the >>>>>>>>>>>>>>>> I-D for item#1 (an API for source address >>>>>>>>>>>>>>>> selection). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Attendees _shall read _the following material >>>>>>>>>>>>>>>> before the call so that we can directly jump to >>>>>>>>>>>>>>>> the discussions: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 1. >>>>>>>>>>>>>>>> http://www.ietf.org/proceedings/91/slides/slides-91-dmm-4.pdf >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> 2. http://www.ietf.org/proceedings/90/slides/slides-90-dmm-6.pdf >>>>>>>>>>>>>>>> 3. >>>>>>>>>>>>>>>> https://datatracker.ietf.org/doc/draft-yegin-dmm-ondemand-mobility/ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> 4. http://www.ietf.org/proceedings/88/slides/slides-88-dmm-8.pdf >>>>>>>>>>>>>>>> 5. >>>>>>>>>>>>>>>> http://tools.ietf.org/html/draft-liu-dmm-mobility-api-02 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> Alper >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Jan 23, 2015, at 3:28 PM, Alper Yegin >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Folks, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Please mark your availability on the >>>>>>>>>>>>>>>>> following doodle for our next DMM WG Mobility >>>>>>>>>>>>>>>>> Exposure and Selection WT call: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> http://doodle.com/7xgcr8x6cgxnbzur >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Register your availability no later than the >>>>>>>>>>>>>>>>> end of Monday (Jan 26). >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Alper >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ dmm >>>>>>>>>>>>>> mailing list dmm@ietf.org <mailto:dmm@ietf.org> >>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dmm >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ dmm >>>>>>>>>>>>> mailing list dmm@ietf.org <mailto:dmm@ietf.org> >>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dmm >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ dmm mailing >>>>>>>>> list dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ dmm mailing >>>>>>>> list dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ dmm mailing list >>>>>> dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm >>>>> >>>>> >>>> >>> >>> >>> >> > > >
- Re: [DMM] Mobility Exposure and Selection WT call Alexandru Petrescu
- Re: [DMM] Mobility Exposure and Selection WT call Alexandru Petrescu
- Re: [DMM] Mobility Exposure and Selection WT call Jouni Korhonen
- Re: [DMM] Mobility Exposure and Selection WT call Alexandru Petrescu
- Re: [DMM] Mobility Exposure and Selection WT call Templin, Fred L
- [DMM] Mobility Exposure and Selection WT call Alper Yegin
- Re: [DMM] Mobility Exposure and Selection WT call Alper Yegin
- Re: [DMM] Mobility Exposure and Selection WT call Alper Yegin
- Re: [DMM] Mobility Exposure and Selection WT call Alper Yegin
- [DMM] Mobility Exposure and Selection WT call#5 Alper Yegin
- Re: [DMM] Mobility Exposure and Selection WT call Alexandru Petrescu
- Re: [DMM] Mobility Exposure and Selection WT call Marco Liebsch
- Re: [DMM] Mobility Exposure and Selection WT call Alper Yegin
- Re: [DMM] Mobility Exposure and Selection WT call Alper Yegin
- Re: [DMM] Mobility Exposure and Selection WT call… Alper Yegin
- Re: [DMM] Mobility Exposure and Selection WT call… Alper Yegin
- Re: [DMM] Mobility Exposure and Selection WT call Alexandru Petrescu
- Re: [DMM] Mobility Exposure and Selection WT call Alper Yegin
- Re: [DMM] Mobility Exposure and Selection WT call Alexandru Petrescu
- Re: [DMM] Mobility Exposure and Selection WT call… Alper Yegin
- Re: [DMM] Mobility Exposure and Selection WT call Alper Yegin
- Re: [DMM] Mobility Exposure and Selection WT call Alexandru Petrescu
- Re: [DMM] Mobility Exposure and Selection WT call Templin, Fred L
- Re: [DMM] Mobility Exposure and Selection WT call Alexandru Petrescu
- Re: [DMM] Mobility Exposure and Selection WT call Templin, Fred L
- Re: [DMM] Mobility Exposure and Selection WT call Alexandru Petrescu
- Re: [DMM] Mobility Exposure and Selection WT call Templin, Fred L
- Re: [DMM] Mobility Exposure and Selection WT call Brian Haberman
- Re: [DMM] Mobility Exposure and Selection WT call Templin, Fred L
- Re: [DMM] Mobility Exposure and Selection WT call Brian Haberman
- Re: [DMM] Mobility Exposure and Selection WT call Templin, Fred L
- Re: [DMM] Mobility Exposure and Selection WT call Brian Haberman
- Re: [DMM] Mobility Exposure and Selection WT call Templin, Fred L