[dhcwg] Message fragmentation in DHCPv6

"Vijayabhaskar A K" <vijayak@india.hp.com> Sat, 15 June 2002 13:46 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07862 for <dhcwg-archive@odin.ietf.org>; Sat, 15 Jun 2002 09:46:54 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id JAA19026 for dhcwg-archive@odin.ietf.org; Sat, 15 Jun 2002 09:47:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA18899; Sat, 15 Jun 2002 09:44:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA18874 for <dhcwg@optimus.ietf.org>; Sat, 15 Jun 2002 09:44:32 -0400 (EDT)
Received: from palrel11.hp.com (palrel11.hp.com [156.153.255.246]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07805 for <dhcwg@ietf.org>; Sat, 15 Jun 2002 09:43:55 -0400 (EDT)
Received: from dce.india.hp.com (dce.india.hp.com [15.10.45.122]) by palrel11.hp.com (Postfix) with ESMTP id 70D67600836 for <dhcwg@ietf.org>; Sat, 15 Jun 2002 06:44:00 -0700 (PDT)
Received: from nt4147 (nt4147.india.hp.com [15.10.41.47]) by dce.india.hp.com with SMTP (8.8.6 (PHNE_17190)/8.8.6 SMKit7.02) id TAA22063 for <dhcwg@ietf.org>; Sat, 15 Jun 2002 19:19:21 +0530 (IST)
Reply-To: vijayak@india.hp.com
From: Vijayabhaskar A K <vijayak@india.hp.com>
To: dhcwg@ietf.org
Date: Sat, 15 Jun 2002 19:15:40 +0530
Message-ID: <000601c21472$f0e79010$2f290a0f@india.hp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Message fragmentation in DHCPv6
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit

"The server SHOULD limit the options returned to the client so that the DHCP
message header and options do not cause fragmentation."

Do we need to define some maximum DHCP message size here?

"The client has to include ALL the IAs in the reply to Reconfigure message."

Then, for this case, what should the client do, in the case if it finds that
there
will be fragmentation. The situation is worse, in the case, client is able
to send all the IAs, but the server is not able to reply with ALL IAs.
How will the server send the remaining options/IAs to the client?

~Vijay


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