Re: [netlmm] Consensus call: RFC5107 based DHCP message intercept at MAG

Frank Xia <xiayangsong@huawei.com> Mon, 13 April 2009 14:51 UTC

Return-Path: <xiayangsong@huawei.com>
X-Original-To: netlmm@core3.amsl.com
Delivered-To: netlmm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DBCC03A686C for <netlmm@core3.amsl.com>; Mon, 13 Apr 2009 07:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[AWL=0.588, BAYES_00=-2.599, STOX_REPLY_TYPE=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 enF3yXima31V for <netlmm@core3.amsl.com>; Mon, 13 Apr 2009 07:51:04 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 270F73A6DD2 for <netlmm@ietf.org>; Mon, 13 Apr 2009 07:50:40 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KI1007T0NYDL5@szxga04-in.huawei.com> for netlmm@ietf.org; Mon, 13 Apr 2009 22:51:49 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KI1005PTNYDGJ@szxga04-in.huawei.com> for netlmm@ietf.org; Mon, 13 Apr 2009 22:51:49 +0800 (CST)
Received: from X24512z ([10.124.12.62]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KI100FAHNYB1E@szxml04-in.huawei.com> for netlmm@ietf.org; Mon, 13 Apr 2009 22:51:49 +0800 (CST)
Date: Mon, 13 Apr 2009 09:51:20 -0500
From: Frank Xia <xiayangsong@huawei.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>, netlmm@ietf.org
Message-id: <016401c9bc47$5f751ba0$3e0c7c0a@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; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <BE82361A0E26874DBC2ED1BA244866B9382A1F89@NALASEXMB08.na.qualcomm.com>
Subject: Re: [netlmm] Consensus call: RFC5107 based DHCP message intercept at MAG
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2009 14:51:04 -0000

Hi all

Technically:

I am okay with keeping this optional mechanism.

BR
Frank

----- Original Message ----- 
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: <netlmm@ietf.org>
Sent: Thursday, April 09, 2009 11:48 PM
Subject: [netlmm] Consensus call: RFC5107 based DHCP message intercept at 
MAG


> An issue has been raised on the inclusion of the DHCP Server Identifier 
> Override sub-option (specified in RFC5107) as a means for the MAG to 
> intercept the MN's DHCP messages sent to the DHCP server.  This option 
> allows the relay (MAG) to act like the DHCP server and more directly get 
> the MN to even address the RENEW DHCP requests to itself, so that the MAG 
> can include the Relay Agent option in those messages as well.  Without 
> this option, the relay in the MAG would need to intercept all DHCP 
> messages.
>
> In PMIPv6, all packets from the MN will go through the MAG - from an 
> implementation perspective, my interpretation is that the use of RFC5107 
> is likely to make a difference in the extent of hardware based forwarding 
> that is made feasible in the MAG.  Otherwise, functionally, the MAG should 
> be able to intercept all DHCP messages even without this option.
>
> The issue raised is primarily from an IPR perspective - please see the 
> following link for the IPR terms associated with RFC5107:
>
> https://datatracker.ietf.org/ipr/124/
>
> I would like to hear WG input on whether you prefer to keep the option in 
> the document or take it out.  If you can provide an explanation for the 
> choice you make (IPR and/or technical), it will be useful.
>
> Please respond to the list by April 15th, 2009.
>
> Thanks,
> Vidya <as co-chair>
> _______________________________________________
> netlmm mailing list
> netlmm@ietf.org
> https://www.ietf.org/mailman/listinfo/netlmm