Re: [v6ops] Enterprises won't deploy IPv6 for IPv6's sake (as they didn't IPv4, IPX, XNS, or DECNet)

[Alexandru Petrescu <[e-mail]>]

Le 10/01/2014 17:00, Templin, Fred L a écrit :
> Hi Alex,
>
>> -----Original Message----- From: v6ops
>> [mailto:[e-mail]] On Behalf Of Alexandru Petrescu
>> Sent: Friday, January 10, 2014 1:18 AM To: [e-mail] Subject:
>> Re: [v6ops] Enterprises won't deploy IPv6 for IPv6's sake (as they
>> didn't IPv4, IPX, XNS, or DECNet)
>>
>> Le 09/01/2014 18:28, Templin, Fred L a écrit :
>>> Hi Tim,
>>>
>>>> -----Original Message----- From: Tim Chown
>>>> [mailto:[e-mail]] Sent: Thursday, January 09, 2014
>>>> 9:24 AM To: Templin, Fred L Cc: Mark ZZZ Smith; Randy Bush; Ted
>>>> Lemon; [e-mail] Subject: Re: [v6ops] Enterprises won't
>>>> deploy IPv6 for IPv6's sake (as they didn't IPv4, IPX, XNS, or
>>>> DECNet)
>>>>
>>>>
>>>> On 9 Jan 2014, at 17:21, "Templin, Fred L"
>>>> <[e-mail]> wrote:
>>>>
>>>>> Hi Tim,
>>>>>
>>>>>> The campus wireless solutions I've seen from vendors to
>>>>>> date that support IPv6 do some "interesting" things to
>>>>>> support devices roaming between IPv6 wireless subnets.
>>>>>> They certainly don't seem to use MIPv6, rather it seems
>>>>>> common to use either unicast RAs and/or L2 tunnelling
>>>>>> between controllers. e.g. see
>>>>>
>>>>> http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bae506.shtml#mobility.
>>>>>
>>>>>
>>>>>
>>
>>>>>
I am thinking of mobiles that have WiFi plus 3G/4G. When the mobile is
>>>>> in proximity of my enterprise infrastructure then it can
>>>>> certainly be managed as it hops between WLCs as you suggest.
>>>>> But, when the mobile leaves the campus and goes in via a
>>>>> Starbucks WiFi (or maybe my home WiFi) it is beyond the
>>>>> management realm of the enterprise and has to do something if
>>>>> it wants to maintain a stable IP address/subnet. Or, if the
>>>>> mobile goes off the "WiFi grid" it has to fire up its 3G/4G
>>>>> link and then still somehow maintain stability.
>>>>
>>>> MPTCP?  A la Siri on iOS7 etc :)
>>>
>>> That won't get me to a mobile router - it only addresses the apps
>>> on the mobile itself.
>>
>> YEs, and only apps using a particular transport protocols, not
>> all.
>>
>> (and yes the news of MPTCP at Apple is encouraging about that
>> particular protocol).
>>
>>>
>>>>> This is not about MIPv6 - it is about AERO:
>>>>
>>>> Well, the thread is about something else, so back to that....
>>>
>>> The thread is about IPv6 deployment in enterprise networks. AERO
>>> is about IPv6 deployment in enterprise networks (which should
>>> also be taken as input to your IPv6 enterprise deployment doc).
>>
>> Right.  But since this thread relates to the DHCP discussion, would
>> AERO have an aspect related to DHCP?  Or to RA?  How would an AERO
>> Router self-configure its address, its mobile network prefix and
>> its default route?  Would it accept many combinations or just one?
>
> AERO certainly has aspects related to both DHCP and RA. AERO nodes
> are all routers (not hosts) and so they would use DHCP as requesting
> routers for Prefix Delegation but not for address configuration. And,
> they would use unicast RS/RA for neighbor cache and default route
> maintenance to their default router.

All while I understand what is said above, I wonder whether running two
protocols simultaneously on slow AERO links is maybe little optimal, or not.

Alex

>
> AERO nodes self-configure link-local addresses through the AERO
> address format specified in the document. AERO nodes only assign
> link-local addresses to their AERO interfaces; they do not assign
> addresses of other scopes. AERO nodes connect IPv6 end user networks
> to the AERO link, and use the AERO link only as transit to get to
> other IPv6 networks. AERO nodes use unicast IPv6 ND for neighbor
> cache maintenance and route optimization.
>
> That is it in a nutshell. Reading and understanding this is enough
> basis for understanding the document as a whole.
>
> Thanks - Fred [e-mail]
>
>> Alex
>>
>>>
>>> Thanks - Fred [e-mail]
>>>
>>>> Tim
>>>>
>>>>>
>>>>> http://tools.ietf.org/html/draft-templin-aerolink
>>>>>
>>>>> Thanks - Fred [e-mail]
>>>>>
>>>>> PS I shouldn't have to ask, but please keep this as
>>>>> plaintext instead of converting to something else.
>>>
>>> _______________________________________________ v6ops mailing
>>> list [e-mail] https://www.ietf.org/mailman/listinfo/v6ops
>>>
>>>
>>
>>
>> _______________________________________________ v6ops mailing list
>> [e-mail] https://www.ietf.org/mailman/listinfo/v6ops
>
>