RE: [RRG] EXPLISP BOF at the Dublin IETF

["Templin, Fred L" <Fred.L.Templin@boeing.com>]

Dino, 

>-----Original Message-----
>From: Dino Farinacci [mailto:dino@cisco.com] 
>Sent: Monday, June 30, 2008 7:39 AM
>To: Templin, Fred L
>Cc: Robin Whittle; RRG; Jari Arkko
>Subject: Re: [RRG] EXPLISP BOF at the Dublin IETF
>
>> Your slide indicates a re-classification of the 240/4 space
>> as public IPv4 addresses, but I don't necessarily agree that
>> that is the best use of the space. At most, that would give
>> a short-term scaling for IPv4 but it has already been said
>> here that scalable deployment of IPv6 is the goal.
>
>The slide is an example how LISP+ALT works. It does not decree any  
>request or mandate for  address allocation.

Could you perhaps use a different example IPv4 prefix then?

Thanks - Fred
fred.l.templin@boeing.com

>> Instead, the 240/4 addresses could make life much better for
>> private addressing within end sites and enterprises, while
>> EIDs go to public IPv6 addresses. The question is whether
>> 2^32 (or thereabouts) end sites/enterprises is enough
>> (seems like it should be)?
>
>Dino
>
>>
>>
>> Fred
>> fred.l.templin@boeing.com
>>
>>> -----Original Message-----
>>> From: Dino Farinacci [mailto:dino@cisco.com]
>>> Sent: Saturday, June 28, 2008 12:08 PM
>>> To: Robin Whittle
>>> Cc: RRG; Jari Arkko
>>> Subject: Re: [RRG] EXPLISP BOF at the Dublin IETF
>>>
>>>> 2 - Better explain how LISP-ALT system works, by way of
>>>>   practical examples, presentation material with graphics
>>>>   etc.  I am not the only one who finds it hard to understand
>>>>   the LISP IDs clearly, and frequently finds that when a
>>>>   question about LISP is answered on the list, that the
>>>>   explanation involves things which seem to contradict what
>>>>   we thought we learnt from the LISP IDs.
>>>
>>> Here is a slide that has been used in many presentations.
>>>
>>> The top side is the initial Data Probe or Map-Request flow sent from
>>> the 11.0.0.1 ITR soliciting a Map-Reply from the destination
>>> site that
>>> owns EID 240.1.1.1. Then the bottom side is shows that ITR 11.0.0.1
>>> uses ETR 1.1.1.1 for subsequent packet encapsulation.
>>>
>>> The solid purple lines indicate where BGP over GRE operates. And the
>>> dotted purple lines are GRE tunnels where BGP is not used so we can
>>> realize a low OpEx ITR/ETR.
>>>
>>> We have the pilot network up running LISP+ALT for both IPv4 and IPv6
>>> EID-prefixes. We use 240.0.0.0/4 and 2610:00d0::/32 as EID-prefixes
>>> for IPv4 and IPv6 respectively.
>>>
>>> Dino
>>>
>>> P.S. RRG, if this is an inappropriate post, I'm sorry, I won't do it
>>> again.
>>>
>>>
>
>

--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg