Re: [netlmm] IPv4 Support
Alexandru Petrescu <alexandru.petrescu@gmail.com> Mon, 16 April 2007 19:39 UTC
Return-path: <netlmm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HdX2h-0003U4-RW; Mon, 16 Apr 2007 15:39:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HdX2g-0003Tk-V9 for netlmm@ietf.org; Mon, 16 Apr 2007 15:39:14 -0400
Received: from mail153.messagelabs.com ([216.82.253.51]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HdX2e-0003kR-DG for netlmm@ietf.org; Mon, 16 Apr 2007 15:39:14 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-2.tower-153.messagelabs.com!1176752350!3476029!1
X-StarScan-Version: 5.5.10.7.1; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 27988 invoked from network); 16 Apr 2007 19:39:11 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8) by server-2.tower-153.messagelabs.com with SMTP; 16 Apr 2007 19:39:11 -0000
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l3GJdAGx029921; Mon, 16 Apr 2007 12:39:10 -0700 (MST)
Received: from il06vts02.mot.com (il06vts02.mot.com [129.188.137.142]) by il06exr03.mot.com (8.13.1/Vontu) with SMTP id l3GJdAqF028863; Mon, 16 Apr 2007 14:39:10 -0500 (CDT)
Received: from [127.0.0.1] ([10.129.41.38]) by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id l3GJd83x028844; Mon, 16 Apr 2007 14:39:09 -0500 (CDT)
Message-ID: <4623D0DB.6050104@gmail.com>
Date: Mon, 16 Apr 2007 21:39:07 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
Subject: Re: [netlmm] IPv4 Support
References: <198227.99752.qm@web84105.mail.mud.yahoo.com> <45F6DEA1.5060008@piuha.net> <45F6E96E.4000402@gmail.com> <45F6F49F.4050405@azairenet.com> <45F6F650.9010709@gmail.com> <45F6F807.4050909@azairenet.com> <45F6FB38.8090509@gmail.com> <D4AE20519DDD544A98B3AE9235C8A4C2900A35@moe.corp.azairenet.com> <4623C73C.4030500@azairenet.com>
In-Reply-To: <4623C73C.4030500@azairenet.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 000734-0, 16/04/2007), Outbound message
X-Antivirus-Status: Clean
X-Vontu: Pass
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: netlmm@ietf.org
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
Errors-To: netlmm-bounces@ietf.org
Vijay Devarapalli wrote: > Hi Alex, I realized I never got back to you on this. Here is a call > flow for this. I haven't show the DHCP server in the call flow. :-) good I remember too now. It's a long discussion :-) > Lets check if we are all on the same page on this topic. One would make sure the 'Access Auth' phase doesn't deliver an IPv4 address to the mobile node. On a IPv4 point to point link with PPP and Radius one does both auth and address allocation. The DHCPv4 exchange seems to approach it right. The DHCP Offer and Request you picture between MN and MAG could extend to the DHCP Server, which I assume to be different than the MAG (a DHCP Relay), by a certain SDO. You seem to have already made a decision that PBack brings the IPv4 address to MN, whereas it could have been done with a real DHCP Offer and Ack, not simulated. I think we could ponder what is easier to implement: build a new DHCP Proxy entity plus ProxyMIPv6/IPv4, or maybe reuse a complete DHCPv4 implementation, no modification on it, and use its messages to trigger the ProxyBU. Then there's this question of differentiating the handover from initial attachment. The DISCOVER is sent only at initial attachment (usually). Upon handover, usually, only the REQUEST is sent, no DISCOVER. Remark, as you, I'm trying to have a complete reuse of the DHCP implementation on MN, no modification of DHCP. But yes, the picture makes sense to me. Let's see other oppinions. We'll surely need to talk this to the DHC WG as well. Alex > > Vijay > > Vijay Devarapalli wrote: >> Hi Alex, >> >> Instead of trying to answer your email point-by-point we will try >> to put out a call flow for this. >> >> Vijay >> >>> -----Original Message----- From: Alexandru Petrescu >>> [mailto:alexandru.petrescu@gmail.com] Sent: Tuesday, March 13, >>> 2007 12:28 PM To: Vijay Devarapalli Cc: Alexandru Petrescu; >>> Behcet Sarikaya; Jari Arkko; netlmm@ietf.org Subject: Re: >>> [netlmm] IPv4 Support >>> >>> Vijay Devarapalli wrote: >>>> Alexandru Petrescu wrote: >>>>> Vijay Devarapalli wrote: >>>>>> Hello Alex and Behcet, >>>>>> >>>>>> draft-sgundave-mip6-proxymip6-02 also provides support for >>>>>> an IPv4-only mobile node. The mobile node need not have a >>>>>> dual stack. See section 5.6. >>>>>> >>>>>> The IPv4 home address given to the mobile node is from a >>>>>> shared prefix from the LMA. There is no per-MN IPv4 prefix. >>>>>> >>>>>> >>>>>> Shared prefix is out of scope currently only for IPv6 >>>>>> addresses for the mobile node. >>>>> So can one say PMIPv6 does shared-prefix for IPv4 but >>> prefix-per-MN >>>>> for IPv6? >>>> Yes. That is what is assumed in >>> draft-sgundave-mip6-proxymip6-02 currently. >>>>>> The MAG gets the IPv4 address for the mobile node from the >>>>>> LMA using Proxy BU/Proxy BAck messages. After that the >>>>>> address is assigned to the mobile node using DHCP. >>>>> How does DHCP implementation on MAG know to _not_ do DHCP? >>>> I don't understand this question. >>> Well who does DHCP DISCOVER? MN. Who does DHCP ACK? MAG. >>> >>> How does MAG know to _not_ relay the DISCOVER to DHCP Server and >>> do P-BU/BAck instead? Is that a DHCP modification? Shouldn't >>> that be made clear that PMIPv6 requires DHCP modifications? >>> >>>>> This is what you imply: LMA gets DHCP request and then >>>>> obtains the IPv4 address with PBU/PBAck. >>>> The DHCP request does not go to the LMA. Only upto the MAG. >>>> Proxy BU/Proxy BAck is used between the MAG and the LMA. >>> How does MAG _know_ to _not_ send the DHCP Request received from >>> MN? A DHCP implementation _does_ forward the DHCP Request. >>> Provided it's a DHCP Relay, of course. I hope both you and me >>> assume the MAG is a DHCP Relay. >>> >>> Besides, it's not the DHCP Request that MAG receives first, it's >>> the DHCP DISCOVER. It's upon DHCP DISCOVER that MAG should act, >>> not upon DHCP Request. >>> >>> Alex >>> >>> >>> ______________________________________________________________________ >>> This email has been scanned by the MessageLabs Email Security >>> System. For more information please visit >>> http://www.messagelabs.com/email >>> ______________________________________________________________________ >>> >>> >> >> _______________________________________________ netlmm mailing list >> netlmm@ietf.org https://www1.ietf.org/mailman/listinfo/netlmm > ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ netlmm mailing list netlmm@ietf.org https://www1.ietf.org/mailman/listinfo/netlmm
- [netlmm] IPv4 Support Narayanan, Vidya
- Re: [netlmm] IPv4 Support Vijay Devarapalli
- RE: [netlmm] IPv4 Support Narayanan, Vidya
- Re: [netlmm] IPv4 Support Katsutoshi Nishida
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- Re: [netlmm] IPv4 Support Jari Arkko
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- Re: [netlmm] IPv4 Support Jari Arkko
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- Re: [netlmm] IPv4 Support Jari Arkko
- Re: [netlmm] IPv4 Support Behcet Sarikaya
- Re: [netlmm] IPv4 Support Jari Arkko
- Re: [netlmm] IPv4 Support Behcet Sarikaya
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- Re: [netlmm] IPv4 Support Vijay Devarapalli
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- Re: [netlmm] IPv4 Support Vijay Devarapalli
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- RE: [netlmm] IPv4 Support Vijay Devarapalli
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- Re: [netlmm] IPv4 Support Vijay Devarapalli
- Re: [netlmm] IPv4 Support Myung-Ki Shin
- Re: [netlmm] IPv4 Support Behcet Sarikaya
- Re: [netlmm] IPv4 Support Vijay Devarapalli
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- Re: [netlmm] IPv4 Support Behcet Sarikaya
- Re: [netlmm] IPv4 Support Vijay Devarapalli
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- Re: [netlmm] IPv4 Support Vijay Devarapalli
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- Re: [netlmm] IPv4 Support Vijay Devarapalli
- Re: [netlmm] IPv4 Support Alexandru Petrescu
- Re: [netlmm] IPv4 Support Jari Arkko
- RE: [netlmm] IPv4 Support Chowdhury, Kuntal
- Re: [netlmm] IPv4 Support Alexandru Petrescu