<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=US-ASCII">
<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> </DIV>
<DIV>I think rerouting inside the path between multi-homed source user A
and multi-homed destination user B ought to be possible at which ever
point prior getting to B. It may be at A and at any router in the
path. It should not involve B nor the application being run at B. And it should
not involve the application at A either.</DIV>
<DIV> </DIV>
<DIV>Rerouting may either be done such that the packets are
still forwarded towards the same destination location, or, if
this becomes necessary/advantageous (e.g. for reasons of traffic balancing),
that</DIV>
<DIV>the destination location is changed- e.g somewhere in the middle of
the path or at/by the egress router in the first place.</DIV>
<DIV> </DIV>
<DIV>Is this a wanted objective ? If so, any architecture, including TARA, needs
to do something about it.</DIV>
<DIV>E.g. a natural approach is to convey an armed destination location as well
the potential alternatives while a packet is transmitted. Right ?</DIV>
<DIV> </DIV>
<DIV>Heiner</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV></FONT></BODY></HTML>