[dhcwg] NotOnlink status for confirm messages
"Vijayabhaskar A K" <vijayak@india.hp.com> Sat, 15 June 2002 17:07 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 NAA12230 for <dhcwg-archive@odin.ietf.org>; Sat, 15 Jun 2002 13:07:15 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id NAA26979 for dhcwg-archive@odin.ietf.org; Sat, 15 Jun 2002 13:07:50 -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 NAA26848; Sat, 15 Jun 2002 13:02:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA26823 for <dhcwg@optimus.ietf.org>; Sat, 15 Jun 2002 13:02:30 -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 NAA12020 for <dhcwg@ietf.org>; Sat, 15 Jun 2002 13:01:54 -0400 (EDT)
Received: from dce.india.hp.com (dce.india.hp.com [15.10.45.122]) by palrel11.hp.com (Postfix) with ESMTP id 85D47600827 for <dhcwg@ietf.org>; Sat, 15 Jun 2002 10:01:56 -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 WAA22321 for <dhcwg@ietf.org>; Sat, 15 Jun 2002 22:37:17 +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 22:33:36 +0530
Message-ID: <000d01c2148e$971d5a30$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] NotOnlink status for confirm messages
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
NoAddrsAvail NoBinding NotOnLink UnspecFail
Solicit Ignore NA NA NA
Advertise
Request Choose NA Solicit NA
next server
Confirm NA NA Solicit NA
Renew NA Request NA NA
Rebind NA Request NA NA
Release NA NA NA NA
Decline NA NA NA NA
Inform-req NA NA NA Choose
next server
The above is the state diagram for the client.
(Renew, NotOnlink) and (Rebind, NotOnlink) is NA here, because, the server
will make lifetimes as 0, in the case the addresses are not in the link.
But (Confirm, NotOnlink) is a applicable. If the server finds that one or
more prefixes are not appropriate, then it will send NotOnlink status.
I think, for the confirm also, server can do operation similar to
(Renew, NotOnlink) but with little bit change. If one or more addresses are
not appropriate to the link, it can return those addresses ONLY with status
NotOnLink, else it canreturn SUCCESS. Thus the client can continue using
the addressses which are appropriate to the link. This will avoid client
sending SOLICIT unnecessarily.
~ Vijay
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] NotOnlink status for confirm messages Vijayabhaskar A K