Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Xingang Liang (liangxgCATT.AC.CN)
Date: Sun May 27 2001 - 20:13:18 CDT
First,I should thank McPherson for his patient explanation,thank you!!!
Then,as you mentioned,"this is not the ideal forum for discussing such technology,"Of course,I know this is the forum for OSPF,but I believe all of you must be very interested in any new or never-heard routing technology,and want to discuss with some engineer for developing our routing knowledge.I am a novice for this forum and for the routing world,whenever I knowed of the new routing technology,I always want to talk with some engineer to exchange our viewpoints,Perhaps this is the occupational disease for an engineer,But I do think it is very useful,right?
For example,routing protocol can be divided by such categories:
routing protocols developed by IETF,such as OSPF,RIP,BGP;
routing protocols developed by ISO,such as IS-IS,ES-IS,IDRP;
routing protocols developed by certain company such as Cisco's IGRP,EIGRP,CDP,HSRP,CLNS,NAT;
routing protocols developed for mobile ad-hoc networks such as DSDV,GSR,HSR,ZHLS,FSR,CGSR,SSR,CBRP,ABR,AODV,DSRP,TORA,WRP;
routing protocols developed for certain technology such as MOSPF,PIM(SM,DM),CBT,DVMPR;
and there are still many.......
When I look at such abundant routing protocol,how can you have not an impulse to study,develop,and discuss these?I think no one can deny this.
So if this is not the ideal forum for discussing these technology,where is the ideal forum,Can anyone tell me about the ideal forum to discuss these ?If there is still no such a forum,Can we build or create such a forum?
I don't know what you think of this question,I welcome any comments about my ideas.
Hope we can talk heart to heart!!!
Ideas come into being when exchanged-----My opinion!
Thank all of you!!!Hoping not to disturb your jobs!
----- Original Message -----
From: "Danny McPherson" <dannyAMBERNETWORKS.COM>
Sent: Friday, May 25, 2001 10:20 PM
Subject: Re: Hot potato routing
The "hot potato routing" phrase is commonly used when referring to
the paradigm of inter-domain route selection in the Internet today.
That is, route policies, usually based on BGP attributes, typically
result in the closest egress router within the routing domain [that
contains a valid path to destination] being selected as the best
available egress point from the domain (aka. closest-exit routing).
The result is that the local network utilizes less resources than may
have otherwise been required -- had it attempted to carry the packet
as close to the destination host as possible.
The alternative, "best-exit" or "cold-potato *8^/" routing, involves
BGP MEDs or other path attributes being employed to convey the optimal
entry point into a routing domain. For example, when advertising
reachability to peer networks for destination host D.1 that resides in
Chicago, Chicago routers would set the MED value low, while LA routers
would set the MED to a [much less desirable] larger value. The result
is that the peer network now knows that carrying the data to Chicago
and then handing it to the peer network is more optimal than handing it
to the peer network in LA and expecting them to carry it to Chicago.
Of course, in the real world, with aggregation and the like, "cold-
potato" routing typically resembles something more akin to "mashed-
potato" routing, and is usally given thrust by service provider
BTW: You were correct this probably isn't the ideal forum for this
> Hot potato routing,just like the meaning of its name,
> resolve the routing problem by forwarding without storing,
> so every packet will be transmitted to the destination
> without being dropped.But I don't know how this technology
> has developped and in what environment can this technology
> be used?
> Can anyone explain for me?