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

"Christian Huitema" <huitema@windows.microsoft.com> Fri, 21 May 2004 06:39 UTC

Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09097 for <ipv6-archive@odin.ietf.org>; Fri, 21 May 2004 02:39:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR3WC-0004HH-2z for ipv6-archive@odin.ietf.org; Fri, 21 May 2004 02:28:32 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4L6SWP5016422 for ipv6-archive@odin.ietf.org; Fri, 21 May 2004 02:28:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR3Uy-0003mQ-Oq for ipv6-web-archive@optimus.ietf.org; Fri, 21 May 2004 02:27:16 -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 CAA08453 for <ipv6-web-archive@ietf.org>; Fri, 21 May 2004 02:27:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR3Uv-0004Jv-6X for ipv6-web-archive@ietf.org; Fri, 21 May 2004 02:27:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR3U0-0004Bh-00 for ipv6-web-archive@ietf.org; Fri, 21 May 2004 02:26:16 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BR3T9-00045C-00 for ipv6-web-archive@ietf.org; Fri, 21 May 2004 02:25:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR3L5-0007eY-34; Fri, 21 May 2004 02:17:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BR3Df-0003tq-2v for ipv6@optimus.ietf.org; Fri, 21 May 2004 02:09:23 -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 CAA03343 for <ipv6@ietf.org>; Fri, 21 May 2004 02:09:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BR3Db-0001xh-Hk for ipv6@ietf.org; Fri, 21 May 2004 02:09:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BR3CZ-0001qL-00 for ipv6@ietf.org; Fri, 21 May 2004 02:08:16 -0400
Received: from mail4.microsoft.com ([131.107.3.122]) by ietf-mx with esmtp (Exim 4.12) id 1BR3Bb-0001d6-00 for ipv6@ietf.org; Fri, 21 May 2004 02:07:15 -0400
Received: from inet-vrs-04.redmond.corp.microsoft.com ([157.54.8.149]) by mail4.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 20 May 2004 23:06:45 -0700
Received: from 157.54.5.25 by inet-vrs-04.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 20 May 2004 23:06:45 -0700
Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-hub-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 20 May 2004 23:06:51 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.84]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 20 May 2004 23:06:17 -0700
Received: from WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com ([157.54.12.81]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069); Thu, 20 May 2004 23:07:18 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Subject: RE: [rfc2462bis] relationship between M/O flags and related protocols
Date: Thu, 20 May 2004 23:06:40 -0700
Message-ID: <DAC3FCB50E31C54987CD10797DA511BA092190CD@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: [rfc2462bis] relationship between M/O flags and related protocols
thread-index: AcQ+9kCMAA72NaJjS8CcuSL3wJzVYQAA0Nfg
From: Christian Huitema <huitema@windows.microsoft.com>
To: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>, Erik Nordmark <Erik.Nordmark@sun.com>
Cc: Ralph Droms <rdroms@cisco.com>, ipv6@ietf.org
X-OriginalArrivalTime: 21 May 2004 06:07:18.0656 (UTC) FILETIME=[DF40C800:01C43EF9]
Content-Transfer-Encoding: 7bit
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: 7bit
Content-Transfer-Encoding: 7bit

> Assuming it's okay for Christian to mention other documents on
> details, can you live with the last proposal from Ralph?
> 
>        The details of how a host uses the M flag from a valid Router
>        Advertisement it receives will be described in a separate document.

I can certainly live with that, but I would rather say:

       The details of how a host may use the M flag from a valid Router
       Advertisement it receives will be described in a separate document.

-- Christian Huitema


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