Re: [DMM] Mobility Exposure and Selection WT call

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 30 March 2015 22:42 UTC

Return-Path: <Fred.L.Templin@boeing.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 259731A6FED for <dmm@ietfa.amsl.com>; Mon, 30 Mar 2015 15:42:51 -0700 (PDT)
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 vDLfPUuRYcPv for <dmm@ietfa.amsl.com>; Mon, 30 Mar 2015 15:42:48 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FFE21A6F7B for <dmm@ietf.org>; Mon, 30 Mar 2015 15:42:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t2UMgmvJ009576; Mon, 30 Mar 2015 15:42:48 -0700
Received: from XCH-BLV-201.nw.nos.boeing.com (xch-blv-201.nw.nos.boeing.com [10.57.37.66]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t2UMgeo4009437 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 30 Mar 2015 15:42:40 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.229]) by XCH-BLV-201.nw.nos.boeing.com ([169.254.1.181]) with mapi id 14.03.0210.002; Mon, 30 Mar 2015 15:42:39 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, Jouni Korhonen <jouni.nospam@gmail.com>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] Mobility Exposure and Selection WT call
Thread-Index: AQHQaBCuHeg12xmiXkGwZvQpxTNtk501pKnA
Date: Mon, 30 Mar 2015 22:42:39 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832E2E10A@XCH-BLV-504.nw.nos.boeing.com>
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>
In-Reply-To: <551481F8.9090507@gmail.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmm/grq5QkWC1xWMtRj2sya6mvAbkrQ>
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: Mon, 30 Mar 2015 22:42:51 -0000

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). 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.

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