Re: [grobj] Referral definition and its purpose?

Dong Zhang <zhangdong_rh@huaweisymantec.com> Wed, 19 May 2010 06:18 UTC

Return-Path: <zhangdong_rh@huaweisymantec.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 D67753A67EC for <grobj@core3.amsl.com>; Tue, 18 May 2010 23:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.645
X-Spam-Level: **
X-Spam-Status: No, score=2.645 tagged_above=-999 required=5 tests=[AWL=0.645, BAYES_80=2]
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 jRFkZgqvfi2F for <grobj@core3.amsl.com>; Tue, 18 May 2010 23:18:37 -0700 (PDT)
Received: from mta1.huaweisymantec.com (mta1.huaweisymantec.com [218.17.155.14]) by core3.amsl.com (Postfix) with ESMTP id 0553D3A67AF for <grobj@ietf.org>; Tue, 18 May 2010 23:18:36 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="gb2312"
Received: from hstml01-in.huaweisymantec.com ([172.26.3.41]) by hstga01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTP id <0L2N00GRELIS3G90@hstga01-in.huaweisymantec.com> for grobj@ietf.org; Wed, 19 May 2010 14:18:28 +0800 (CST)
Received: from z90001956 ([10.27.154.76]) by hstml01-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-8.03 (built Apr 24 2009; 32bit)) with ESMTPA id <0L2N001UILIPG010@hstml01-in.huaweisymantec.com> for grobj@ietf.org; Wed, 19 May 2010 14:18:25 +0800 (CST)
Date: Wed, 19 May 2010 14:18:24 +0800
From: Dong Zhang <zhangdong_rh@huaweisymantec.com>
To: Sheng Jiang <shengjiang@huawei.com>, 'Keith Moore' <moore@network-heretics.com>
References: <004f01caf712$a0defa00$730c6f0a@china.huawei.com>
Message-id: <201005191418237821049@huaweisymantec.com>
X-Mailer: Foxmail 6, 10, 201, 20 [cn]
Cc: "grobj@ietf.org" <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: Wed, 19 May 2010 06:18:39 -0000

Hi,

Sheng Jiang 2010-05-19 Wrote:
>> -----Original Message-----
>> From: Keith Moore [mailto:moore@network-heretics.com] 
>> Sent: Tuesday, May 18, 2010 8:27 PM
>> To: Sheng Jiang
>> Cc: grobj@ietf.org
>> Subject: Re: [grobj] Referral definition and its purpose?
>> 
>> On 5/18/10 5:01 AM, Sheng Jiang wrote: 
>> 
>> 	Hi, all,
>> 	
>> 	We are now working on an referral PS draft, targeting 
>> to submit end of May
>> 	or the beginning of June. We'd like to discuss the 
>> relevant contents/topic
>> 	publicly in the mail list during our writing. Comments 
>> or contributions are
>> 	more than welcome.
>> 	
>> 	The first target is to understand what is referral and 
>> its purpose. There
>> 	may be different understanding, our goal here is to 
>> find a common definition
>> 	for our PS draft. The following is my understanding and 
>> what's in the draft
>> 	now.
>> 	
>> 	In abstract: The purpose of a referral is to enable a 
>> given entity in a
>> 	multiparty Internet application to pass information to 
>> another party. It
>> 	enables a communication initiator to aware relevant 
>> information of its
>> 	destination entity before launching the communication.
>> 	
>> 	In the introduction: A frequently occurring situation 
>> is that one entity A
>> 	connected to the Internet (or to some private network 
>> using the Internet
>> 	protocol suite) needs to inform another entity B how to 
>> reach either A
>> 	itself or some third-party entity C. This is known as a 
>> referral.
>> 	
>> 	Does everyone can agree on this Referral definition and 
>> its purpose? Only if
>> 	consensus can reach here, our next discussion for 
>> referral scenarios can
>> 	make sense.
>> 	
>> 
>> I would define the scope as somewhat broader than that.  I 
>> think it's quite reasonable to want to make referrals across 
>> application boundaries.  If one application provides a 
>> service that's useful to another application, I think it's 
>> reasonable to pass a referral object from one application to 
>> another.    To say this another way, I think that these days 
>> the boundary between one application and another is rather arbitrary.
>
>Hi, Keith,
>
>Fully agree. The approach we are discussing is application independent. So, natually, the solution
>we may produce will have the ability to traverse application boundaries. My ideal model is the
>referral will happen in transport layer to serve all applications. 
Why not in IP layer? I mean using the extension header, such as destination options header.

Thanks.
------------------				 
Dong Zhang
2010-05-19