<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
<META content="MSHTML 6.00.6000.16735" name=GENERATOR></HEAD>
<BODY id=role_body style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Arial"
bottomMargin=7 leftMargin=7 topMargin=7 rightMargin=7><FONT id=role_document
face=Arial color=#000000 size=2>
<DIV>In einer eMail vom 18.11.2008 06:04:38 Westeuropäische Normalzeit schreibt
tony.li@tony.li:</DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><FONT
style="BACKGROUND-COLOR: transparent" face=Arial color=#000000
size=2><BR>|
Since it is not practical to solve the<BR>|
routing
scaling problem with host upgrades,<BR>|
adding a core-edge separation
scheme (ITRs,<BR>|
ETRs and a mapping system) is a way of<BR>|
providing portability and multihoming to<BR>|
all end-user networks
which want it, while<BR>|
reducing the burden on routers, and
while<BR>|
maintaining the full Internet service at all<BR>|
times.<BR>|<BR>|
It is adding "stuff" - hardware, software<BR>|
and a global mapping system - to the Net,<BR>|
in order to avoid
adding something uglier<BR>|
and more expensive, ever-bigger
routers<BR>|
and a less stable DFZ (while still not<BR>|
meeting
the portability and multihoming<BR>|
needs of many smaller end-user
networks).<BR><BR><BR>Well, that's certainly one opinion.<BR><BR>If we want to
change the architecture to something that we can live with in<BR>perpetuity,
we might want to step back and take a larger view of the world.<BR>IPv6 is
coming, like it or not. </FONT></BLOCKQUOTE>
<DIV>Well, that's certainly one opinion, too.</DIV>
<DIV>Quote from the RAWS report:</DIV>
<DIV> </DIV>
<DIV>3.2. IPv6 and Its Potential Impact on Routing Table Size</DIV>
<DIV> </DIV>
<DIV> Due to the increased IPv6 address size over IPv4, a full
immediate<BR> transition to IPv6 is estimated to lead to the RIB and
FIB sizes<BR> increasing by a factor of about four. The size
of the routing table<BR> based on a more realistic assumption, that
of parallel IPv4 and IPv6<BR> routing for many years, is less
clear. An increasing amount of<BR> allocated IPv6 address
prefixes is in PI space. ARIN [ARIN] has<BR> relaxed its
policy for allocation of such space and has been<BR> allocating /48
prefixes when customers request PI prefixes. Thus,<BR> the
same pressures affecting IPv4 address allocations also affect<BR>
IPv6 allocations.</DIV>
<DIV> </DIV>
<DIV>Heiner</DIV></FONT></BODY></HTML>