Re: [Seamoby] DoCoMo Implementation Issues with CTP
Rajeev Koodli <rajeev@iprg.nokia.com> Thu, 19 February 2004 01:51 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06811 for <seamoby-archive@odin.ietf.org>; Wed, 18 Feb 2004 20:51:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtdKv-0003y4-Eo for seamoby-archive@odin.ietf.org; Wed, 18 Feb 2004 20:50:45 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J1oj4C015248 for seamoby-archive@odin.ietf.org; Wed, 18 Feb 2004 20:50:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtdKv-0003xr-AC for seamoby-web-archive@optimus.ietf.org; Wed, 18 Feb 2004 20:50:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06780 for <seamoby-web-archive@ietf.org>; Wed, 18 Feb 2004 20:50:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtdKs-0000ft-00 for seamoby-web-archive@ietf.org; Wed, 18 Feb 2004 20:50:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtdJv-0000eW-00 for seamoby-web-archive@ietf.org; Wed, 18 Feb 2004 20:49:44 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AtdJF-0000dQ-00 for seamoby-web-archive@ietf.org; Wed, 18 Feb 2004 20:49:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtdJF-0003qC-R9; Wed, 18 Feb 2004 20:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtdIz-0003pd-Q9 for seamoby@optimus.ietf.org; Wed, 18 Feb 2004 20:48:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06761 for <seamoby@ietf.org>; Wed, 18 Feb 2004 20:48:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtdIx-0000ct-00 for seamoby@ietf.org; Wed, 18 Feb 2004 20:48:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AtdI4-0000bx-00 for seamoby@ietf.org; Wed, 18 Feb 2004 20:47:49 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx with esmtp (Exim 4.12) id 1AtdHr-0000aI-00 for seamoby@ietf.org; Wed, 18 Feb 2004 20:47:36 -0500
Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id i1J1kwN32565; Wed, 18 Feb 2004 17:46:58 -0800
X-mProtect: <200402190146> Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdkmeFLo; Wed, 18 Feb 2004 17:46:56 PST
Message-ID: <40341585.127EE1A7@iprg.nokia.com>
Date: Wed, 18 Feb 2004 17:46:46 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
CC: seamoby@ietf.org, Raghu Dendukuri <dendukuri@docomolabs-usa.com>
Subject: Re: [Seamoby] DoCoMo Implementation Issues with CTP
References: <059c01c3f5a4$63e9e360$936015ac@dclkempt40>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-BeenThere: seamoby@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=unsubscribe>
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
List-Post: <mailto:seamoby@ietf.org>
List-Help: <mailto:seamoby-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/seamoby>, <mailto:seamoby-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Jim, the suggested changes are okay. I am curious about couple of suggestions however.. - When both IPv4 and IPv6 addresses are used in CTD, "Processing the address of the opposite version in the stack is complicated. " Could you elaborate on this ? I can see that once IP (v4 or v6) stack demultiplexes the packet to belong to a CTP client, it would just forward the block to a CTP module (a daemon for instance), which could then process contexts associated with both the addresses. - Isn't MTU a consideration in increasing the size of the Length field to 16 bits ? Thanks, -Rajeev James Kempf wrote: > DoCoMo is in the process of implementing CTP, and we came up with the > following list of issues in the spec. Since none of them seem particularly > large, Allison suggested that we simply update the current version of the > document (which is now under review by the ROHC WG) in place, without reving > the document to a new version. She will make the changes. > Below, a list of the issues and suggested changes to the document to address > them. > > Any comments? Please let me know by March 6. > > jak > > ------------------------------------------- > > 1) Section 2.5.1, pg. 10; Section 2.5.2, pg. 11; Section 2.5.3, pg. 12; > Section 2.5.4, pg. 13; Section 2.5.6, pg. 15 - 'V' flag > > The spec allows CTP messages to carry both IPv4 and IPv6 addresses, but as a > practical matter in the implementation, a CTP message will be sent to the > IPv4 or IPv6 address of a router. Processing the address of the opposite > version in the stack is complicated. Suggestion is to only allow IPv4 or > IPv6 addresses, but keep the flag field size at 2 bits in case further > experience shows that there are reasons why both might be sent. The router > can issue separate messages if both addresses must be changed, Suggested > change in text: > > Replace: "When set to '10', indicate presence of both IPv6 and IPv4 Previous > (New) addresses." > With: "Values of '10' and '11' are reserved". > > 2) Section 2.5.3, pg. 12 - Length of Algorithm field in CTD message block. > > The length of the algorithm field in the CTD message block is shown as 17 > bits. It should be 16. > > 3) Section 2.5.1, pg. 10; Section 2.5.2, pg. 11; Section 2.5.3, pg. 12; > Section 2.5.4, pg. 13; Section 2.5.6, pg. 15 - Length field. > > The size of the message length field is currently 8 bits, and the units for > the length are in 8 octet words. This allows a maximum of 2048 octets, which > might not be enough for bundling large amounts of context if padding is > required. Suggestion is to increase the size of the field and make it be > units of octets, for a total of 65535 octets. This would only involve moving > the flags into the Reserved field, and would not otherwise modify the > message. > > Replace: In message diagram blocks, move Length to be 16 bits rather than 8. > > Replace: "Length message length in units of 8 octet words" > With: "Length message length in units of octets" > > 4) Section 2.5.1. pg. 9; Section 2.5.2, pg. 11; Section 2.5.3, pg. 12; > Section 2.5.4, pg. 13; Section 2.5.5, pg. 14; Section 2.4.6, pg. 15 - IP > address field size. > > The message block diagrams show the size of the IP address fields as 4 > octets, but if the IP address is for IPv6, it will be 16. > > Replace: In the message block diagrams, replace the final "|" with a "~" to > indicate a variable length field. Indicate variable length field by putting > "(4 or 16 octets)" after the text in the field. > > 5) Section 2.5.3, pg. 12 - Key field in message diagram > > Only 4 bytes are shown for the key field, but the key size field allows > 65535. The message diagram needs to be changed. > > Replace: In the message diagram, replace the final "|" with a "~" to > indicate a variable length field. Indicate the variable length field by > putting "(variable)" after the text in the field. > > _______________________________________________ > Seamoby mailing list > Seamoby@ietf.org > https://www1.ietf.org/mailman/listinfo/seamoby _______________________________________________ Seamoby mailing list Seamoby@ietf.org https://www1.ietf.org/mailman/listinfo/seamoby
- [Seamoby] DoCoMo Implementation Issues with CTP James Kempf
- RE: [Seamoby] DoCoMo Implementation Issues with C… john.loughney
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- RE: [Seamoby] DoCoMo Implementation Issues with C… Soliman Hesham
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- RE: [Seamoby] DoCoMo Implementation Issues with C… Soliman Hesham
- Re: [Seamoby] DoCoMo Implementation Issues with C… James Kempf
- Re: [Seamoby] DoCoMo Implementation Issues with C… James Kempf
- Re: [Seamoby] DoCoMo Implementation Issues with C… James Kempf
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… Raghu
- Re: [Seamoby] DoCoMo Implementation Issues with C… James Kempf
- Re: [Seamoby] DoCoMo Implementation Issues with C… Rajeev Koodli
- Re: [Seamoby] DoCoMo Implementation Issues with C… James Kempf