RE: [netlmm] I-D Action:draft-ietf-netlmm-proxymip6-03.txt
"Sri Gundavelli" <sgundave@cisco.com> Mon, 10 September 2007 03:12 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 1IUZhp-0002pq-6F; Sun, 09 Sep 2007 23:12:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IUZhn-0002md-R9 for netlmm@ietf.org; Sun, 09 Sep 2007 23:12:55 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IUZhm-0006j6-DI for netlmm@ietf.org; Sun, 09 Sep 2007 23:12:55 -0400
X-IronPort-AV: E=Sophos;i="4.20,228,1186383600"; d="scan'208";a="214977465"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 09 Sep 2007 20:12:53 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l8A3CrPK008499; Sun, 9 Sep 2007 20:12:53 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l8A3CjF0010520; Mon, 10 Sep 2007 03:12:53 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 9 Sep 2007 20:12:49 -0700
Received: from sgundavewxp ([10.32.246.213]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 9 Sep 2007 20:12:48 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: 'Shyam H' <shyam.hemad@gmail.com>, netlmm@ietf.org
References: <E1ITAig-0002uA-1l@stiedprstage1.ietf.org><013f01c7f04f$ebbd1ab0$d4f6200a@amer.cisco.com> <4c174b660709071621s399377e5n9e4347c6f9191fd8@mail.gmail.com>
Subject: RE: [netlmm] I-D Action:draft-ietf-netlmm-proxymip6-03.txt
Date: Sun, 09 Sep 2007 20:12:48 -0700
Message-ID: <005e01c7f358$7767a020$d5f6200a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Thread-Index: AcfxpdIXFnAM2QyGQVC7fQT6cGgB0QBsgFAA
In-Reply-To: <4c174b660709071621s399377e5n9e4347c6f9191fd8@mail.gmail.com>
X-OriginalArrivalTime: 10 Sep 2007 03:12:49.0018 (UTC) FILETIME=[77750DA0:01C7F358]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5536; t=1189393973; x=1190257973; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sgundave@cisco.com; z=From:=20=22Sri=20Gundavelli=22=20<sgundave@cisco.com> |Subject:=20RE=3A=20[netlmm]=20I-D=20Action=3Adraft-ietf-netlmm-proxymip6 -03.txt |Sender:=20; bh=I3mTzyCgVWT8dYlavm1+xGa626GHwpA2C7koxbuoLHc=; b=GFDIBUVnQUy16/PLhLDFdL2VMAYKxna6qchK7VHdWosAbSj5wn7JsaOVJNiOyKjvhcr7mgMl OD2XhhfEhTLHOWjKt0rdQT3BH9W/JcE7WVIv1q2e/bWWm4D39uLs79Lp;
Authentication-Results: sj-dkim-4; header.From=sgundave@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Cc:
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
Hi Shyam, Please see inline ... > -----Original Message----- > From: Shyam H [mailto:shyam.hemad@gmail.com] > Sent: Friday, September 07, 2007 4:21 PM > To: netlmm@ietf.org > Subject: Re: [netlmm] I-D Action:draft-ietf-netlmm-proxymip6-03.txt > > Dear Sri > > > Thank you for updating the Proxy-MIP6 draft. We reviewed and discussed > the draft in detail and these are our comments. > > First, the draft is written nicely, organized very well; enjoyed > reading it; we thank the authors for the good work. > > > We did not like the timestamp format change; it was not needed, we > have to make changes to our code.; but fine. > > In MAG signaling, you should add the RS and RA flow related points; > You should add a small section with couple of lines on what the MAG > does when RA arrives; this is missing; it is there in the seq diagram. > Ok. > Lot of new error checking rules; but good; very detailed > > You should specify when the HA should consider the timestamp from MAG > as as outof sync. Suggest some time window like 1 second; define a > protocol variable. Or, make NTP use a must. Not an issue for us; we > have RO. > Ok. > On PBU and PBA retransmissions or timeouts, please say it is as per > rfc3775; or define new protocol constants > This is a good point. I've worked on the text for this and other points you raised, you will see it in the next rev. > PBA cannot have the type-II routing header, can it ? there is no home > address ; you should mention this; to avoid interop problems. > Format of the PBA is given. Its not there in it. But, if it needs to be explicitly mentioned, will do that. > > Hope this review helps. Thank you again for completing this > document; good job. > Thanks for the comments. Sri > > - Shyam > > > > -----Original Message----- > > > From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] > > > Sent: Wednesday, September 05, 2007 11:20 PM > > > To: i-d-announce@ietf.org > > > Cc: netlmm@ietf.org > > > Subject: [netlmm] I-D Action:draft-ietf-netlmm-proxymip6-03.txt > > > > > > A New Internet-Draft is available from the on-line > > > Internet-Drafts directories. > > > This draft is a work item of the Network-based Localized > > > Mobility Management Working Group of the IETF. > > > > > > > > > Title : Proxy Mobile IPv6 > > > Author(s) : S. Gundavelli, et al. > > > Filename : draft-ietf-netlmm-proxymip6-03.txt > > > Pages : 55 > > > Date : 2007-09-06 > > > > > > This specification describes a network-based mobility management > > > protocol. It is called Proxy Mobile IPv6 and is based on > Mobile IPv6 > > > [RFC-3775]. This protocol enables mobility support to a > host without > > > requiring its participation in any mobility related > signaling. The > > > design principle in the case of network-based mobility management > > > protocol relies on the network being in control of the mobility > > > management. The mobility entities in the network are > responsible for > > > tracking the movements of the host and initiating the required > > > mobility signaling on its behalf. > > > > > > A URL for this Internet-Draft is: > > > > http://www.ietf.org/internet-drafts/draft-ietf-netlmm-proxymip6-03.txt > > > > > > To remove yourself from the I-D Announcement list, send a > message to > > > i-d-announce-request@ietf.org with the word unsubscribe in > > > the body of > > > the message. > > > You can also visit > https://www1.ietf.org/mailman/listinfo/I-D-announce > > > to change your subscription settings. > > > > > > Internet-Drafts are also available by anonymous FTP. > Login with the > > > username "anonymous" and a password of your e-mail address. After > > > logging in, type "cd internet-drafts" and then > > > "get draft-ietf-netlmm-proxymip6-03.txt". > > > > > > A list of Internet-Drafts directories can be found in > > > http://www.ietf.org/shadow.html > > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > > > > Internet-Drafts can also be obtained by e-mail. > > > > > > Send a message to: > > > mailserv@ietf.org. > > > In the body type: > > > "FILE /internet-drafts/draft-ietf-netlmm-proxymip6-03.txt". > > > > > > NOTE: The mail server at ietf.org can return the document in > > > MIME-encoded form by using the "mpack" utility. To use this > > > feature, insert the command "ENCODING mime" before > the "FILE" > > > command. To decode the response(s), you will need > "munpack" or > > > a MIME-compliant mail reader. Different MIME-compliant > > > mail readers > > > exhibit different behavior, especially when dealing with > > > "multipart" MIME messages (i.e. documents which > have been split > > > up into multiple messages), so check your local > documentation on > > > how to manipulate these messages. > > > > > > Below is the data which will enable a MIME compliant mail reader > > > implementation to automatically retrieve the ASCII version of the > > > Internet-Draft. > > > > > > > _______________________________________________ > > netlmm mailing list > > netlmm@ietf.org > > https://www1.ietf.org/mailman/listinfo/netlmm > > > > _______________________________________________ > netlmm mailing list > netlmm@ietf.org > https://www1.ietf.org/mailman/listinfo/netlmm _______________________________________________ netlmm mailing list netlmm@ietf.org https://www1.ietf.org/mailman/listinfo/netlmm
- RE: [netlmm] Significance of MN-Identifier Alper Yegin
- [netlmm] I-D Action:draft-ietf-netlmm-proxymip6-0… Internet-Drafts
- RE: [netlmm] I-D Action:draft-ietf-netlmm-proxymi… Sri Gundavelli
- Re: [netlmm] I-D Action:draft-ietf-netlmm-proxymi… Shyam H
- RE: [netlmm] I-D Action:draft-ietf-netlmm-proxymi… Sri Gundavelli
- [netlmm] Significance of MN-Identifier Alper Yegin
- RE: [netlmm] Significance of MN-Identifier Sri Gundavelli
- RE: [netlmm] Significance of MN-Identifier Alper Yegin
- RE: [netlmm] Significance of MN-Identifier Sri Gundavelli
- RE: [netlmm] Significance of MN-Identifier Chowdhury, Kuntal