Re: [Mip4] Recharter: Ethernet Service Support

Qin Wu <sunseawq@huawei.com> Wed, 06 May 2009 06:09 UTC

Return-Path: <sunseawq@huawei.com>
X-Original-To: mip4@core3.amsl.com
Delivered-To: mip4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 038173A6A48 for <mip4@core3.amsl.com>; Tue, 5 May 2009 23:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.471
X-Spam-Level:
X-Spam-Status: No, score=-0.471 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, 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 ailwvrW+lHqY for <mip4@core3.amsl.com>; Tue, 5 May 2009 23:09:10 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 156843A6824 for <mip4@ietf.org>; Tue, 5 May 2009 23:09:10 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ7009D0L5EL8@szxga03-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:10:26 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KJ700CVQL5EF3@szxga03-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:10:26 +0800 (CST)
Received: from w53375 ([10.164.12.38]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KJ7006PGL5DOW@szxml04-in.huawei.com> for mip4@ietf.org; Wed, 06 May 2009 14:10:26 +0800 (CST)
Date: Wed, 06 May 2009 14:10:25 +0800
From: Qin Wu <sunseawq@huawei.com>
To: Shahriar Rahman <rahman@redback.com>, McCann Peter-A001034 <pete.mccann@motorola.com>, mip4@ietf.org
Message-id: <02c601c9ce11$58c82f50$260ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <BE4B07D4197BF34EB3B753DD34EBCD13039BEE88@de01exm67.ds.mot.com> <B701736AA609BA4AB6555D5E7BC490FBC382B0CAC1@RBSJX.ad.redback.com>
Cc: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip4] Recharter: Ethernet Service Support
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mip4>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 May 2009 06:09:18 -0000

Thanks Shah, I am glad you join this work. As we discussed in the IETF74 meeting, 
I will consider to incorporate VSE mechanism as another candidate mechanism to transport ethernet service across MIP
to what we already have in the draft. And your further comments and suggestion are welcome in the maillist.

Regards!
-Qin
----- Original Message ----- 
From: "Shahriar Rahman" <rahman@redback.com>
To: "McCann Peter-A001034" <pete.mccann@motorola.com>; <mip4@ietf.org>
Cc: "Henrik Levkowetz" <henrik@levkowetz.com>
Sent: Wednesday, May 06, 2009 11:27 AM
Subject: Re: [Mip4] Recharter: Ethernet Service Support


> Hi,
> I support work on this topic and could be interested to assist in the works.
> 
> Thanks.
> Shah
> 
> -----Original Message-----
> From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On Behalf Of McCann Peter-A001034
> Sent: Tuesday, May 05, 2009 8:49 AM
> To: mip4@ietf.org
> Cc: Henrik Levkowetz
> Subject: [Mip4] Recharter: Ethernet Service Support
> 
> Hi, all,
> 
> During our meeting at IETF74, we discussed whether to take on
> a draft describing support for Ethernet service to a mobile node,
> as described in this draft:
> 
> draft-wu-mip4-ether-00.txt
> 
> The sense of the room seemed to be that we NOT take on this 
> as a work item at this time.
> 
> This message is a request to confirm/reject this approach.  Please
> respond to this e-mail with an indication of whether you agree
> or disagree, and state your reasons why.
> 
> -Pete
> --
> Mip4 mailing list: Mip4@ietf.org
>    Web interface: https://www.ietf.org/mailman/listinfo/mip4
>     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
> --
> Mip4 mailing list: Mip4@ietf.org
>    Web interface: https://www.ietf.org/mailman/listinfo/mip4
>     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>