RE: [nemo] RE: draft-ietf-nemo-home-network-models-05

["Pascal Thubert \(pthubert\)" <[e-mail]>]

Hi Mattias;

Yes, the idea is that the prefix is generally shorter than /64. 

We had long discussions in this ML about autoconfigs with shorter
prefixes (Alex?). But yes, NEMO should work in theory with a shorter
prefix assigned to the Home Link. Note that NEMO does not require
autoconf operations; and last that I know, a Cisco router will not
auto-configure an address on a prefix that is shorter than 64. 

So there might be some implementation specific issues to do at least
autoconf. DAD should work, though, which is what we need. Would I,
personally, recommend the aggregated mode? I don't think so. But if a
good half of the population starts with that mode in mind, it's good to
document the pro/cons, and hopefully, at the end the day, they will make
the right deployment decision for their needs...

Pascal

>-----Original Message-----
>From: Mattias Pettersson L (LD/EAB)
[mailto:[e-mail]]
>Sent: Tuesday, February 14, 2006 11:32 AM
>To: Pascal Thubert (pthubert); Alexandru Petrescu
>Cc: [e-mail]; [e-mail]; Margaret Wasserman;
[e-mail];
>[e-mail]; [e-mail]
>Subject: RE: [nemo] RE: draft-ietf-nemo-home-network-models-05
>
>
>> [Pascal] Aggregated mode is when you want to configure the
>> whole Home Network on the Home Link, though it is an
>> aggregation. Some people in the group found that model more
>> natural as an evolution from MIP6.
>
>Pascal, does this mean that you configure something else than /64
>prefixes on the home link? Is Neighbor Discovery/Address conf
compatible
>with that?
>
>/Mattias