IETF Logo Mail Archive

RE: [rfc2462bis] relationship between M/O flags and related protocols

"Bound, Jim" <jim.bound@hp.com> Sat, 22 May 2004 03:38 UTC

Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23212 for <ipv6-archive@odin.ietf.org>; Fri, 21 May 2004 23:38:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRNJ3-0002t0-8O for ipv6-archive@odin.ietf.org; Fri, 21 May 2004 23:36:19 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4M3aH8L011094 for ipv6-archive@odin.ietf.org; Fri, 21 May 2004 23:36:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRNFg-00027r-SB for ipv6-web-archive@optimus.ietf.org; Fri, 21 May 2004 23:32:48 -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 XAA22873 for <ipv6-web-archive@ietf.org>; Fri, 21 May 2004 23:32:45 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRNFd-0004JH-FY for ipv6-web-archive@ietf.org; Fri, 21 May 2004 23:32:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRNEJ-0004C2-00 for ipv6-web-archive@ietf.org; Fri, 21 May 2004 23:31:25 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BRNDT-00045f-00 for ipv6-web-archive@ietf.org; Fri, 21 May 2004 23:30:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRN2M-0007ne-AX; Fri, 21 May 2004 23:19:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRMre-0005iP-5Q for ipv6@optimus.ietf.org; Fri, 21 May 2004 23:07:58 -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 XAA22063 for <ipv6@ietf.org>; Fri, 21 May 2004 23:07:52 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRMrY-0001pE-Ns for ipv6@ietf.org; Fri, 21 May 2004 23:07:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRMqY-0001jB-00 for ipv6@ietf.org; Fri, 21 May 2004 23:06:50 -0400
Received: from zmamail03.zma.compaq.com ([161.114.64.103]) by ietf-mx with esmtp (Exim 4.12) id 1BRMpZ-0001ap-00 for ipv6@ietf.org; Fri, 21 May 2004 23:05:49 -0400
Received: from tayexg12.americas.cpqcorp.net (tayexg12.americas.cpqcorp.net [16.103.130.103]) by zmamail03.zma.compaq.com (Postfix) with ESMTP id 7213920; Fri, 21 May 2004 23:05:49 -0400 (EDT)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26]) by tayexg12.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.0); Fri, 21 May 2004 23:05:49 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Subject: RE: [rfc2462bis] relationship between M/O flags and related protocols
Date: Fri, 21 May 2004 23:05:44 -0400
Message-ID: <9C422444DE99BC46B3AD3C6EAFC9711B0644C12F@tayexc13.americas.cpqcorp.net>
Thread-Topic: [rfc2462bis] relationship between M/O flags and related protocols
Thread-Index: AcQ/WKKvDaApsPJwSSOdcMCpmAmU1wAUPlWA
From: "Bound, Jim" <jim.bound@hp.com>
To: Ralph Droms <rdroms@cisco.com>, JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
Cc: Erik Nordmark <Erik.Nordmark@sun.com>, Christian Huitema <huitema@windows.microsoft.com>, ipv6@ietf.org
X-OriginalArrivalTime: 22 May 2004 03:05:49.0163 (UTC) FILETIME=[AF05C3B0:01C43FA9]
Content-Transfer-Encoding: base64
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
Content-Transfer-Encoding: base64
Content-Transfer-Encoding: base64

Me too and Christian H's use of "may" update.
/jim 

> -----Original Message-----
> From: ipv6-admin@ietf.org [mailto:ipv6-admin@ietf.org] On 
> Behalf Of Ralph Droms
> Sent: Friday, May 21, 2004 1:10 PM
> To: JINMEI Tatuya / 神明達哉
> Cc: Erik Nordmark; Christian Huitema; ipv6@ietf.org
> Subject: Re: [rfc2462bis] relationship between M/O flags and 
> related protocols
> 
> This text is fine with me, too.
> 
> - Ralph
> 
> At 09:43 AM 5/21/2004 -0700, Erik Nordmark wrote:
> > > Or, if you feel happier by mentioning changes of the M bit 
> > > explicitly, we could alternatively say
> > >
> > >      The details of how a host uses the M flag, including 
> any use of
> > >      the "on" and "off" transitions for this flag, to 
> control the use
> > >      of DHCPv6 for address assignment will be described 
> in a separate
> > >      document.
> > > (based on a previous text from Ralph)
> > >
> > > This way, we can avoid the use of the "possibly extraneous state 
> > > variable" which is internal information in the 
> implementation, while 
> > > keeping the essential idea about external behavior.
> >
> >The text above is fine with me.
> >
> >   Erik
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 
>

v2.23.0 | Report a Bug | By Email