[Seamoby] issue-#49: Length indicator for Router Certificate sub-option

"James Kempf" <kempf@docomolabs-usa.com> Wed, 05 May 2004 22:53 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 SAA17474 for <seamoby-archive@odin.ietf.org>; Wed, 5 May 2004 18:53:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLVDB-0004gQ-V4 for seamoby-archive@odin.ietf.org; Wed, 05 May 2004 18:49:57 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i45Mnv3U017998 for seamoby-archive@odin.ietf.org; Wed, 5 May 2004 18:49:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLVCJ-0004GN-LV for seamoby-web-archive@optimus.ietf.org; Wed, 05 May 2004 18:49:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17231 for <seamoby-web-archive@ietf.org>; Wed, 5 May 2004 18:48:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLVCG-00019J-CA for seamoby-web-archive@ietf.org; Wed, 05 May 2004 18:49:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLVBO-0000qj-00 for seamoby-web-archive@ietf.org; Wed, 05 May 2004 18:48:07 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BLVAY-0000ZB-00 for seamoby-web-archive@ietf.org; Wed, 05 May 2004 18:47:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLV6T-00014l-Js; Wed, 05 May 2004 18:43:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLUww-0005nx-E0 for seamoby@optimus.ietf.org; Wed, 05 May 2004 18:33:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16519 for <seamoby@ietf.org>; Wed, 5 May 2004 18:33:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLUwt-0004Hh-9y for seamoby@ietf.org; Wed, 05 May 2004 18:33:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLUvu-0003zX-00 for seamoby@ietf.org; Wed, 05 May 2004 18:32:06 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx with esmtp (Exim 4.12) id 1BLUvN-0003hd-00 for seamoby@ietf.org; Wed, 05 May 2004 18:31:33 -0400
Message-ID: <01e101c432f0$ceaf6ec0$366115ac@dcml.docomolabsusa.com>
From: James Kempf <kempf@docomolabs-usa.com>
To: seamoby@ietf.org
Date: Wed, 05 May 2004 15:32:09 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Seamoby] issue-#49: Length indicator for Router Certificate sub-option
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

All the length fields in CARD are 8 bits, which means restricts the size of
messages to 254 bytes. This length is insufficient for certificates.

An additional concern is that if the length field of the entire
Request/Reply mesage is the same as the sub-option length field, the
sub-option generator may want generate an option longer than would fit into
the message, since this would be allowed by the field length. The solution
for this in any case is for the sub-option generator code to respect the
overall limits on the message length, in addition to the sub-option length.

Proposal 1: Keep the length field size at 8 bits and make the units of
length be 8 octets, for a maximum 1634 bits  or 2048 bytes.

Proposal 2: Change the length field size to 16 bits, for a total of 65535
bits or 8192 bytes.

Suggested resolution: Proposal 2

Reason: Proposal 1 could result in a maximum of up to 7 padding bytes of
null data in an option or sub-option which is an extra overhead that is
unnecessary and unwanted over the air.


            jak



_______________________________________________
Seamoby mailing list
Seamoby@ietf.org
https://www1.ietf.org/mailman/listinfo/seamoby