Hi Brian, > -----Original Message----- > From: dmm [mailto:dmm-boun...@ietf.org] On Behalf Of Brian Haberman > Sent: Monday, April 27, 2015 6:45 AM > To: dmm@ietf.org > Subject: Re: [DMM] Mobility Exposure and Selection WT call > > > > On 4/22/15 12:51 PM, Templin, Fred L wrote: > > Hi Alex, > > > >> -----Original Message----- > >> From: Alexandru Petrescu [mailto:alexandru.petre...@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-boun...@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). > > So, it is not actually a link-local address per the IPv6 Addressing > Architecture (https://tools.ietf.org/html/rfc4291#section-2.5.6).
Just because the AERO address Interface ID is not formed via EUI-64 does not mean that it is not a link-local address (see RFC7136, which updates RFC4291). RFC7421 gives further commentary. Thanks - Fred fred.l.temp...@boeing.com > Regards, > Brian _______________________________________________ dmm mailing list dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
