Re: Mobility Exposure and Selection WT call

Hi Brian,

> -----Original Message-----
> From: dmm [mailto:[email protected]] On Behalf Of Brian Haberman
> Sent: Monday, April 27, 2015 9:36 AM
> To: [email protected]
> Subject: Re: [DMM] Mobility Exposure and Selection WT call
> 
> 
> 
> On 4/27/15 12:30 PM, Templin, Fred L wrote:
> > Hi Brian,
> >
> >> -----Original Message-----
> >> From: dmm [mailto:[email protected]] On Behalf Of Brian Haberman
> >> Sent: Monday, April 27, 2015 9:22 AM
> >> To: [email protected]
> >> Subject: Re: [DMM] Mobility Exposure and Selection WT call
> >>
> >>
> >>
> >> On 4/27/15 11:53 AM, Templin, Fred L wrote:
> >>
> >>>> 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.
> >>
> >> I am not referring to the IID of the link-local address.  I am talking
> >> about the 54 bits of zero which immediately follow the FE80::/10 prefix.
> >
> > AERO leaves those 54 bits as zero - are you seeing some place in the
> > spec where it does not appear that way?
> 
> Apologies.  I read your example incorrectly.  As long as the prefix
> delegated is 64 bits...

Yes, that is correct. The longest prefix AERO can delegate is /64. It
can however delegate shorter prefixes like /56, /48, etc.

Thanks - Fred
[email protected]

> Brian