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

"Vijay Devarapalli" <vijay@wichorus.com> Fri, 10 April 2009 05:33 UTC

Return-Path: <vijay@wichorus.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 D5B443A6885 for <netlmm@core3.amsl.com>; Thu, 9 Apr 2009 22:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level:
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599]
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 uHPGZ0ejF9Wb for <netlmm@core3.amsl.com>; Thu, 9 Apr 2009 22:33:20 -0700 (PDT)
Received: from outbound.mse15.exchange.ms (outbound.mse15.exchange.ms [216.52.164.185]) by core3.amsl.com (Postfix) with ESMTP id 9A3C83A687E for <netlmm@ietf.org>; Thu, 9 Apr 2009 22:33:19 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 10 Apr 2009 01:34:09 -0400
Message-ID: <DE33046582DF324092F2A982824D6B0305F9D1E6@mse15be2.mse15.exchange.ms>
In-Reply-To: <BE82361A0E26874DBC2ED1BA244866B9382A1F89@NALASEXMB08.na.qualcomm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [netlmm] Consensus call: RFC5107 based DHCP message intercept at MAG
Thread-Index: Acm5l5bZe/rw7pCLTNK7WcN/v0lm3AABge+A
From: Vijay Devarapalli <vijay@wichorus.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>, netlmm@ietf.org
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: Fri, 10 Apr 2009 05:33:20 -0000

Hi Vidya,

One clarification. There is no need for the MAG to intercept the unciast
DHCP requests from the MN to the DHCP server co-located with the LMA. It
can treat the DHCP messages as regular traffic from the MN. The LMA
checks if the MN is requesting the same address it has been allocated.

On the consensus call, my preference is to remove this entire optional
mechanism.

Vijay

> -----Original Message-----
> From: netlmm-bounces@ietf.org 
> [mailto:netlmm-bounces@ietf.org] On Behalf Of Narayanan, Vidya
> Sent: Thursday, April 09, 2009 9:48 PM
> To: netlmm@ietf.org
> 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
>