Re: [DMM] Mobility Exposure and Selection WT call

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 26 March 2015 18:01 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 2CF1B1B29CA for <dmm@ietfa.amsl.com>; Thu, 26 Mar 2015 11:01:31 -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 0Cj3HytvO1Uw for <dmm@ietfa.amsl.com>; Thu, 26 Mar 2015 11:01:27 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D7EA1AD36E for <dmm@ietf.org>; Thu, 26 Mar 2015 11:01:25 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t2QI1OWt016327; Thu, 26 Mar 2015 19:01:24 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 32D3D204E70; Thu, 26 Mar 2015 19:02:09 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 26492200CD8; Thu, 26 Mar 2015 19:02:09 +0100 (CET)
Received: from [127.0.0.1] ([132.166.84.136]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t2QI1MY5025560; Thu, 26 Mar 2015 19:01:23 +0100
Message-ID: <55144971.5080208@gmail.com>
Date: Thu, 26 Mar 2015 13:01:21 -0500
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: Alper Yegin <alper.yegin@yegin.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>
In-Reply-To: <4238F47D-1284-46D3-AF61-F173E4A3BDBE@yegin.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmm/MQltlxAjcJ_KBqFKkju-h0DKMhE>
Cc: dmm@ietf.org
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: Thu, 26 Mar 2015 18:01:31 -0000

Le 13/02/2015 03:09, Alper Yegin a écrit :
> Hello Alex,
>
>> I looked at the slides.  I think I understand the concept of type
>> of IP address from a mobility perspective: fixed, sustained,
>> nomadic.
>>
>> I have remarks: - could an aquired prefix (DHCPv6 PD) also be
>> qualified as fixed, sustained, nomadic?
>
> Yes.
>
>> - how would a mobility address type relate to other address
>> 'types'? - link-local, ULA, global.
>
> Link-local can only be nomadic.

I disagree.  A LL can also be 'fixed', because it's fixed.

> Global can be any type.

Ok.

> We cannot assure a ULA address stays the same
> (considering border crossings), hence it can only be nomadic.

But it can also be sustained.

>> - unicast, anycast, multicast.
>
> This is source address selection, hence multicast address is out-of
> picture. Unicast vs anycast distinction is orthogonal to mobility
> type of the address.

So all SUSTAINED, NOMADIC, FIXED addresses can only be unicast, right?

>> - MAC-based, random-based (RFC7217).
>
> Orthogonal.

What does that mean?  orthogonal?

Alex


>
>> - 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.
>
>
>> 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 https://www.ietf.org/mailman/listinfo/dmm
>>>
>>
>>
>> _______________________________________________ dmm mailing list
>> dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
>
>
>