Re: [rfc2462bis] M/O flags and DHCPv6

Ralph Droms <rdroms@cisco.com> Tue, 30 March 2004 23:13 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 SAA26499 for <ipv6-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:13:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B8RjU-0006Zv-OS for ipv6-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:20 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i247nm9V017027 for ipv6-archive@odin.ietf.org; Thu, 4 Mar 2004 02:49:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aync4-0004PI-Bv for ipv6-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 02:49:48 -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 CAA24526 for <ipv6-web-archive@ietf.org>; Thu, 4 Mar 2004 02:49:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aynbl-0005zK-00 for ipv6-web-archive@ietf.org; Thu, 04 Mar 2004 02:49:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aynal-0005mJ-00 for ipv6-web-archive@ietf.org; Thu, 04 Mar 2004 02:48:27 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AynZx-0005av-00 for ipv6-web-archive@ietf.org; Thu, 04 Mar 2004 02:47:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AynZS-0003mI-Hp; Thu, 04 Mar 2004 02:47:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AynYP-0003aV-3a for ipv6@optimus.ietf.org; Thu, 04 Mar 2004 02:46:01 -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 CAA24100 for <ipv6@ietf.org>; Thu, 4 Mar 2004 02:45:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AynYL-0005Av-00 for ipv6@ietf.org; Thu, 04 Mar 2004 02:45:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AynXH-0004tf-00 for ipv6@ietf.org; Thu, 04 Mar 2004 02:44:52 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx with esmtp (Exim 4.12) id 1AynWI-0004af-00 for ipv6@ietf.org; Thu, 04 Mar 2004 02:43:50 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 03 Mar 2004 23:47:27 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i247hJh0011655 for <ipv6@ietf.org>; Thu, 4 Mar 2004 02:43:19 -0500 (EST)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-2-91.cisco.com [10.86.242.91]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AGM98062; Thu, 4 Mar 2004 02:43:16 -0500 (EST)
Message-Id: <4.3.2.7.2.20040304023041.029dc170@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 04 Mar 2004 02:33:23 -0500
To: ipv6@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [rfc2462bis] M/O flags and DHCPv6
In-Reply-To: <y7vznaxonll.wl@ocean.jinmei.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: ipv6-admin@ietf.org
Errors-To: ipv6-admin@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Id: IP Version 6 Working Group (ipv6) <ipv6.ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-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.0 required=5.0 tests=AWL autolearn=no version=2.60

At 02:19 AM 3/4/2004 +0900, JINMEI Tatuya / 
=?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= wrote:
>In the wg meeting on Tuesday, several concerns were raised regarding
>this issue (and the proposed resolution).  To summarize (some of)
>them,
>
>1. the resolution proposes to say "the stateful protocol is DHCPv6"
>    clearly, without leaving other possibilities.  This would require
>    RFC3315 (DHCPv6) to be listed as a normative reference.  However,
>    we'll then face a reference dependency issue, since rfc2462bis is
>    soon expected to be recycled as a DS while RFC3315 is still a PS.
>    (BTW: I could not find a direct source of this dependency issue.
>    Could someone give me a pointer?)

Do you mean that a DS spec cannot have an informative reference to a PS spec?

- Ralph


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------