[dhcwg] Order of occurence of DHCPv6 options

"Vijayabhaskar A K" <vijayak@india.hp.com> Sat, 15 June 2002 17:30 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 NAA12620 for <dhcwg-archive@odin.ietf.org>; Sat, 15 Jun 2002 13:30:53 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA27831 for dhcwg-archive@odin.ietf.org; Sat, 15 Jun 2002 13:31:29 -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 NAA27318; Sat, 15 Jun 2002 13:29:50 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA27293 for <dhcwg@optimus.ietf.org>; Sat, 15 Jun 2002 13:29:48 -0400 (EDT)
Received: from atlrel6.hp.com (atlrel6.hp.com [156.153.255.205]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12565 for <dhcwg@ietf.org>; Sat, 15 Jun 2002 13:29:12 -0400 (EDT)
Received: from dce.india.hp.com (dce.india.hp.com [15.10.45.122]) by atlrel6.hp.com (Postfix) with ESMTP id B70162EF for <dhcwg@ietf.org>; Sat, 15 Jun 2002 13:29:16 -0400 (EDT)
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 XAA22468 for <dhcwg@ietf.org>; Sat, 15 Jun 2002 23:04:37 +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 23:00:56 +0530
Message-ID: <000e01c21492$6882ab90$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] Order of occurence of DHCPv6 options
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

I think, we need to fix the order of options occuring in DHCPv6 messages
for better processing of the messages.

1. Elapsed Time option - Since based on this value only, the relay/server is
going to decide the policy of reply.

2. Status Code - In the case of Failure, this message can be directly
ignored

3. Authentication option - If authentication fails, nothing is needed to
be processed.

4. server-id - If the server id doesn't match, server can ignore it.

5. client-id - If the client id doesn't match, client can ignore it.

6. Rapid commit - Based on this, the server can determine whether it need
to send Advertise or Reply.


If any of these options are occuring, then they MUST occur in this order.

----------------------------------------------------------------------------
--

ConfNoMatch and AddrUnavail are nowhere used. It can be removed.

AuthFailed is also nowhere used. We need to add text saying if the
server/client is not able to authenticate the other, then they
should send reply with error code AuthFailed set.

----------------------------------------------------------------------------
--
R-forw.    *                        *     *      *      *
R-repl.    *                        *     *      *      *

Why Authentication, User class, Vendor class, Vendor specific options
are needed in Relay-fwd and Relay-reply message.

~Vijay


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