Re: [grobj] Referral definition and its purpose?
bo zhou <zhouboyj@gmail.com> Thu, 27 May 2010 07:29 UTC
Return-Path: <zhouboyj@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 2E0D93A6951 for <grobj@core3.amsl.com>; Thu, 27 May 2010 00:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level:
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001]
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 C73IiBR8DWxE for <grobj@core3.amsl.com>; Thu, 27 May 2010 00:29:57 -0700 (PDT)
Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by core3.amsl.com (Postfix) with ESMTP id D30983A6843 for <grobj@ietf.org>; Thu, 27 May 2010 00:29:56 -0700 (PDT)
Received: by qyk11 with SMTP id 11so10980174qyk.13 for <grobj@ietf.org>; Thu, 27 May 2010 00:29:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=EVdxQ3OEA6XYc6Q4sUhsid04QWhuGYnUPk9hKjzvCFE=; b=K5eVT9Gyp7ShVGKVO78afryroE50HzQE40Gr8zWhIFXrneIbJSe7eivjuumbsLVNXE BKveatpQTc7Grvy0sqwqjtimiY/neudF6u8/LQBx7B7yMimCQ6TEKrR0hjeqsHzejwV9 OT1Ct7kahSlv9PJUyN+eWxF9ZnbmvL5D4b0g8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TfV+VY6zhpbOb25hzdX7Q4xmPkxpEwhemeV+jAxoqrLNSS6AaEtHso6LCHU1vdxCYk pYe8I/ZuVnpNQJkrvyIP0M+XfZde9djNs+726yJ1w85n/BiLA7H0vPikK1So92xjm8wq 62LlE61WNJNqYsPznSZAqFtHa4OIGcatBwTMc=
MIME-Version: 1.0
Received: by 10.229.249.145 with SMTP id mk17mr2137991qcb.163.1274945384342; Thu, 27 May 2010 00:29:44 -0700 (PDT)
Received: by 10.229.185.133 with HTTP; Thu, 27 May 2010 00:29:44 -0700 (PDT)
In-Reply-To: <4BFDF9EB.9000404@network-heretics.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>
Date: Thu, 27 May 2010 15:29:44 +0800
Message-ID: <AANLkTiklnzhDtTJ2xgciLh1PAoGGDvNcUoMkqLxmltSg@mail.gmail.com>
From: bo zhou <zhouboyj@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary="0016364ecc48bde4d404878e5a68"
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 07:29:58 -0000
Sorry to jump in discussion. On Thu, May 27, 2010 at 12:49 PM, Keith Moore <moore@network-heretics.com>wrote: > On 5/27/10 12:31 AM, Dan Wing wrote: > > The definition of referral should be tightened up slightly > that the parties are exchanging the information via one > channel (e.g., SIP signaling) but want to communicate (as) > directly (as possible) with each other *not* using that > channel. > > that's certainly one case. another case is when parties A > and B exchange information about how either A or B can > contact one or more other parties. > > > Two party case is easier to understand and conceptualize. > This covers a *huge* number of important cases. > > agree. > > Then, in a later section number of the same document, we > can explain 3 party case. > > I think I'd rather have the various examples together in the document, but > I won't try to nail down the document outline just yet. > > also, the referred-to path doesn't have to be more direct > than the path over which the referral is taking place. > > > Sure. > > But my point is that it is a *different* path than the > signaling path. I agree the path could be longer and > could go around the moon - twice. > > it's _probably_ a different path because if it were the same path, there'd > be little need for the referral. just reuse the same source address, > destination address, destination port as seen by the initiator of the > connection (though that might not work if the new connection needed to be > initiated by the receiver of the original connection). > > but to be general, it shouldn't _have_ to be a different path. it should > be possible to use a referral that specifies the same path used by the > connection used to send the referral. (or to put it another way, do you > really want the API to say "sorry, you can't use this referral because you > received it over the very path that it specifies?") > > 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. 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? > > Do you have a better way to represent that in ASCII that > gets the point across? Picture worth a thousand words > and all.. > > I thought your picture was okay for the case you were describing, but I > probably didn't look at it too closely as this is all familiar to me > already. > > Keith > > > _______________________________________________ > grobj mailing list > grobj@ietf.org > https://www.ietf.org/mailman/listinfo/grobj > > -- Regards, Bo Zhou China Mobile
- [grobj] Referral definition and its purpose? Sheng Jiang
- Re: [grobj] Referral definition and its purpose? Keith Moore
- Re: [grobj] Referral definition and its purpose? Sheng Jiang
- Re: [grobj] Referral definition and its purpose? Dong Zhang
- Re: [grobj] Referral definition and its purpose? Keith Moore
- Re: [grobj] Referral definition and its purpose? Sheng Jiang
- Re: [grobj] Referral definition and its purpose? Sheng Jiang
- Re: [grobj] Referral definition and its purpose? Brian E Carpenter
- Re: [grobj] Referral definition and its purpose? Sheng Jiang
- Re: [grobj] Referral definition and its purpose? Dan Wing
- Re: [grobj] Referral definition and its purpose? Keith Moore
- Re: [grobj] Referral definition and its purpose? Dan Wing
- Re: [grobj] Referral definition and its purpose? Keith Moore
- Re: [grobj] Referral definition and its purpose? bo zhou
- Re: [grobj] Referral definition and its purpose? bo zhou
- Re: [grobj] Referral definition and its purpose? Sheng Jiang
- Re: [grobj] Referral definition and its purpose? Keith Moore
- Re: [grobj] Referral definition and its purpose? Scott Brim
- Re: [grobj] Referral definition and its purpose? Scott Brim
- Re: [grobj] Referral definition and its purpose? Sheng Jiang
- Re: [grobj] Referral definition and its purpose? Sheng Jiang
- Re: [grobj] Referral definition and its purpose? Sheng Jiang
- Re: [grobj] Referral definition and its purpose? Brian E Carpenter