Re: [grobj] Referral definition and its purpose?

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 27 May 2010 15:59 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: grobj@core3.amsl.com
Delivered-To: grobj@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4EDD3A6AF6 for <grobj@core3.amsl.com>; Thu, 27 May 2010 08:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mQtpE+wkVgRj for <grobj@core3.amsl.com>; Thu, 27 May 2010 08:59:45 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 9B1FF3A696F for <grobj@ietf.org>; Thu, 27 May 2010 08:59:45 -0700 (PDT)
Received: by wye20 with SMTP id 20so85900wye.31 for <grobj@ietf.org>; Thu, 27 May 2010 08:59:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ao1fV88LExGTqrIlpDifrpbmSEVRpOr/vaIMxcqk+nk=; b=Wue3BQy6X+GOnjKZ7ecC9CvtrcZZnkfzP5n7O1OCSM1VhkiMaRPaTGWM1ZKojYRPqa kQDk/vlPBMS9bSqMikO2vQTsWM+4EKN880SdDz7dVBZPBuShs1J9EQM7wdJ9/IBd6LxQ zhNAKJrLThJ+BnuiXNyeVfJayHirq0blRON04=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=gSZCMWUzcb4SNJDV05glhuK0+6IlBddfLF/tqI0TaloCiJSVAL30jEMeFx6qhFlWVg NMMRHJxp+eZgvA54dRAVoSRTp3pt4yb5irLlC933MGe2Qf1NyD9sSDvapycRZfRxdyZo +HrZ3cyeeumY5oWMIfBhKjy6x8SA2DhM+N6ug=
Received: by 10.216.161.67 with SMTP id v45mr798276wek.26.1274975600557; Thu, 27 May 2010 08:53:20 -0700 (PDT)
Received: from [192.168.0.3] ([90.193.140.98]) by mx.google.com with ESMTPS id t70sm812571weq.2.2010.05.27.08.53.18 (version=SSLv3 cipher=RC4-MD5); Thu, 27 May 2010 08:53:19 -0700 (PDT)
Message-ID: <4BFE9568.5010605@gmail.com>
Date: Fri, 28 May 2010 03:53:12 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: bo zhou <zhouboyj@gmail.com>
References: <004d01caf668$b33272e0$730c6f0a@china.huawei.com> <115701cafd32$7cefc180$c4f0200a@cisco.com> <4BFDF394.6050102@network-heretics.com> <124e01cafd55$7f1aa2e0$c4f0200a@cisco.com> <4BFDF9EB.9000404@network-heretics.com> <AANLkTiklnzhDtTJ2xgciLh1PAoGGDvNcUoMkqLxmltSg@mail.gmail.com>
In-Reply-To: <AANLkTiklnzhDtTJ2xgciLh1PAoGGDvNcUoMkqLxmltSg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: grobj@ietf.org
Subject: Re: [grobj] Referral definition and its purpose?
X-BeenThere: grobj@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discuss Generic Referral Objects <grobj.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/grobj>, <mailto:grobj-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grobj>
List-Post: <mailto:grobj@ietf.org>
List-Help: <mailto:grobj-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grobj>, <mailto:grobj-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 May 2010 15:59:46 -0000

On 2010-05-27 19:29, bo zhou wrote:
...
> [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.
> And in the real world, could you give me an example why A will give B three
> path. For my knowledge, A always tells B only one path. Or you want to say
> the communication between A and B support MIF scenario?

The application entity may not know or care whether there is one or
multiple interfaces, so we certainly must not exclude MIF scenarios.
However, choice of interface, like choice of address, is something
that happens after the referral has been sent.

    Brian