Re: [grobj] Referral definition and its purpose?

Sheng Jiang <shengjiang@huawei.com> Wed, 19 May 2010 10:20 UTC

Return-Path: <shengjiang@huawei.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 720F13A6BCC for <grobj@core3.amsl.com>; Wed, 19 May 2010 03:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.164
X-Spam-Level: *
X-Spam-Status: No, score=1.164 tagged_above=-999 required=5 tests=[AWL=-0.755, BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 CcbRaUkv7R9l for <grobj@core3.amsl.com>; Wed, 19 May 2010 03:20:36 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 4A37B3A6BBF for <grobj@ietf.org>; Wed, 19 May 2010 03:18:00 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L2N001YWWLGP4@szxga05-in.huawei.com> for grobj@ietf.org; Wed, 19 May 2010 18:17:40 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L2N00F75WLGDG@szxga05-in.huawei.com> for grobj@ietf.org; Wed, 19 May 2010 18:17:40 +0800 (CST)
Received: from j66104a ([10.111.12.115]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L2N00EGAWLF4Q@szxml06-in.huawei.com> for grobj@ietf.org; Wed, 19 May 2010 18:17:40 +0800 (CST)
Date: Wed, 19 May 2010 18:17:39 +0800
From: Sheng Jiang <shengjiang@huawei.com>
In-reply-to: <201005191418237821049@huaweisymantec.com>
To: 'Dong Zhang' <zhangdong_rh@huaweisymantec.com>, 'Keith Moore' <moore@network-heretics.com>
Message-id: <006501caf73c$82e49f80$730c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: Acr3GyA0pH3Y4jJpSsqCczyTN+eV8AAISVcQ
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: Wed, 19 May 2010 10:20:43 -0000

> >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.

As the same answer in another thread, many referral information is from IP layer, such as IP
addresses, hostnames, etc. The referral information may carried as IP payload. So, it is beyond the
IP layer. 

Cheers,

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