Re: [grobj] Referral definition and its purpose?

[Sheng Jiang <[e-mail]>]

于 2010/5/27 18:48, Keith Moore 写道:
> On 5/27/10 3:29 AM, bo zhou wrote:
>>
>>
>>     here's an example: over path P1, A sends to B a referral that
>>     specifies three paths by which A can be reached: P1, P2, and P3.
>>     when B tries to reconnect to A, its circumstances are such that P1
>>     appears to be the best of the three paths. I don't know why B
>>     shouldn't use P1.
>>
>> [bo] I am not sure why B will use P1 to connect to A, because it is
>> hard for B to understand which path is the best. A send B a referral
>> over P1 is bacause only P1 is known at the beginning of communication.
>> A can tell B there are three paths, but cannot tell B which one is the
>> best.
> It is indeed difficult for B to know which path is best. And in many
> cases "best" depends on the specific needs of the application. One
> application might need maximum bandwidth, another low delay, another
> might prefer a stable address.

I believe this is an information provisioning issue. If somehow, B has 
been provided enough information of A, it can make a right decision on 
its own behave.

There is no single standard what is best. One path may be fast, but 
expensive; while another is slow, but free. Which is the best depends on 
individual request.

There was discussion before how much information should be included in 
GROBJ. Some said minimum and necessary information with no clear 
definition what is necessary. Some other said put whatever may useful 
information (ALL) into GROBJ. Then it is a lot overhead and expensive, 
also maybe create many waste. This is still an open issue.

Cheers,

Sheng