[netlmm] FW: Editorial comments on draft-sgundave-mip6-proxymip6-02.txt
"Sri Gundavelli" <sgundave@cisco.com> Thu, 12 April 2007 19:11 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 1Hc4i6-0001ul-Nc; Thu, 12 Apr 2007 15:11:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc4i5-0001uV-JP for netlmm@ietf.org; Thu, 12 Apr 2007 15:11:57 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc4i3-0008Ll-IQ for netlmm@ietf.org; Thu, 12 Apr 2007 15:11:57 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 12 Apr 2007 12:11:55 -0700
X-IronPort-AV: i="4.14,403,1170662400"; d="scan'208,217"; a="135137565:sNHT168119235"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l3CJBt9b016894 for <netlmm@ietf.org>; Thu, 12 Apr 2007 12:11:55 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l3CJBnMf028209 for <netlmm@ietf.org>; Thu, 12 Apr 2007 19:11:54 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Apr 2007 12:11:22 -0700
Received: from sgundavewxp ([10.32.246.211]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 12 Apr 2007 12:11:20 -0700
From: Sri Gundavelli <sgundave@cisco.com>
To: netlmm@ietf.org
Date: Thu, 12 Apr 2007 12:11:20 -0700
Message-ID: <014f01c77d36$5afeea30$d3f6200a@amer.cisco.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acd9FpfmrpRcRreMQxSF6JXXBXiW0gAH4Wiw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-OriginalArrivalTime: 12 Apr 2007 19:11:21.0080 (UTC) FILETIME=[5AF10780:01C77D36]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=26546; t=1176405115; x=1177269115; c=relaxed/simple; s=sjdkim1004; 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:=20FW=3A=20Editorial=20comments=20on=20draft-sgundave-mip6-proxy mip6-02.txt |Sender:=20; bh=HJH9UH1Wp2uIg8sPZjRPXGY+3XfRc5m54fidh3nSvcg=; b=p7Lo/DGZGV5Yg6fk1dDbtyE2RIlrrYqQUopviPXM9SSFKY3y5YyJ5g1108kecAe1hdaiDYp0 qPOmKNWSxIENBKxoE1ZllX0IQC0MzdK+FrKFBYzGxOZqjTeE0kmB96Zlqvogui6a5lne380GqT 4M0EgGkSsup3RSrjNPw6BoMWc=;
Authentication-Results: sj-dkim-1; header.From=sgundave@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79668c4a0135b05f663aafe71bc273fd
Subject: [netlmm] FW: Editorial comments on draft-sgundave-mip6-proxymip6-02.txt
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>
Content-Type: multipart/mixed; boundary="===============0014636755=="
Errors-To: netlmm-bounces@ietf.org
FYI. Will be fixed in -01 version. Thanks Scott. Regards Sri _____ From: Droste Scott-QA3599 [mailto:Scott.Droste@motorola.com] Sent: Thursday, April 12, 2007 8:24 AM To: sgundave@cisco.com Subject: Editorial comments on draft-sgundave-mip6-proxymip6-02.txt Sri, I was reviewing your Internet-draft titled, "Proxy Mobile IPv6 draft-sgundave-mip6-proxymip6-02.txt" dated March 5, 2007 and had a couple of minor editorial comments. Since I'm not familiar with the official process/means for registering comments, I'm providing them to you for your consideration. As you will see, the comments are editorial in nature and you can handle them as you see fit - no need to contact me concerning the resolution. I would like to thank you and the other contributors for this important piece of work. The draft was well written and enjoyable to read. Best regards, Scott Droste Motorola scott.droste@motorola.com Comments on , "Proxy Mobile IPv6 draft-sgundave-mip6-proxymip6-02.txt" dated March 5, 2007 Section 3 (Proxy Mobile IPv6 Protocol Overview) Page 8. Current Text: "The mobile access gatway would have all the information for it to emulate the mobile node's home network on the access link." Suggested Change: correct spelling of "gateway" Page 9. Current Text: "Upon accepting the Proxy Binding Update request, the mobile access gateway sends a Proxy Binding Acknowledgment message to the mobile access gateway. It also sets up a route to the mobile node's home network prefix over the tunnel and sends Proxy Binding Acknowledgment message to the mobile access gateway." Suggested Change: These two sentences were a bit confusing to me, since I am not an expert in this area. If I have followed the logic presented in the draft, it may be more correct to modify the first sentence as follows: First sentence: "Upon accepting the Proxy Binding Update request, the local mobility anchor sends a Proxy Binding Acknowledgment message to the mobile access gateway." Again, since I'm not an expert in this area, I'm not sure how to correct the second sentence; but I'm sure that upon reading this, you will find the correct phrasing. Section 5.5 (Sequence Number and Time-Stamps for Message Ordering) Page 17. Current Text: "It creates certain ambiguity and the local mobility anchor will not be predictably order the messages." Suggested Change: Remove the word "be" or change to "will not be predictably ordering" Section 5.6. (IPv4 Home Address Mobility Support) Page 18. Current Text: "The mobile access on the access link where mobile node is attached, will register this address with the local mobility anchor using the IPv4 Home Address option, defined in Section 3.1.1, DSMIP6 draft [draft-ietf-mip6-nemo-v4traversal-03.txt]." Suggested Change: "The mobile access gateway on the access link where the mobile node is attached, ." (Added the word "gateway" after "mobile access" and the word "the" before "mobile node".) Section 6.5. (Link-Local and Global Address Uniqueness) Page 25. Current Text: "possibility of the link-local address collision on the connected access link, One of the work around for this issue to the set following flag ." Suggested Change: "possibility of the link-local address collision on the connected access link. One of the work arounds for this issue is to the set following flag." (changed the comma after "access link" to period, changed "work around" to "work arounds" and "this issue to" to "this issue is to".) End of comments ============================================================================
_______________________________________________ netlmm mailing list netlmm@ietf.org https://www1.ietf.org/mailman/listinfo/netlmm
- [netlmm] FW: Editorial comments on draft-sgundave… Sri Gundavelli