RE: [RRG] 2 billion IP cellphones in 2103 & mass adoption of IPv6 by currentIPv4 users

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

Noel, 

>-----Original Message-----
>From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu] 
>Sent: Tuesday, September 16, 2008 3:02 PM
>To: rrg@psg.com
>Cc: jnc@mercury.lcs.mit.edu
>Subject: RE: [RRG] 2 billion IP cellphones in 2103 & mass 
>adoption of IPv6 by currentIPv4 users
>
>
>    > From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
>
>    > Call that box a LISP ITR, e.g., and the decision of 
>where the packet
>    > goes is based on resolving an IPv6 EID to an IPv4 RLOC. That is a
>    > mapping function; not routing function.
>
>Ah, no - if there is a substantial amount of deployed 
>connectivity mesh (i.e.
>network) in which there is native IPv6 routing.
>
>_In that part of the network_, you will have to inject routes 
>to all those
>'mapped' IPv6 destinations, in order for IPv6 packets to those 
>destinations to
>be correctly forwarded through that deployed connectivity mesh.
>
>Map+Encap is only a 'pure' mapping solution when it's deployed 
>all the way at
>the edges _everywhere_ (i.e. no IPv6 router has anything 
>except a 'default'
>route, and maybe a few local routes). If you have some parts 
>of the network
>where M+E is not deployed, then it has a routing component 
>(see above) in
>those parts of the network.

It seems like we are still early enough along in IPv6 deployment
such that the address space has not become sufficiently fragmented
to preclude rules such as:

  Prefix:    Action:
  *******    *******
  ABCD::/3   route
  XYZW::/3   map+encaps
  (etc)

So, if we have one or a few coarse-grained prefixes that a
router can use to tell whether something should be routed
or map/encaps'd, that should be sufficient to keep the
routing tables small - right?

Fred
fred.l.templin@boeing.com
   
>
>	Noel
>

--
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