Re: comments on draft-ietf-ipv6-scoping-arch-00.txt

Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de> Mon, 03 November 2003 13:02 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 IAA00343 for <ipv6-archive@odin.ietf.org>; Mon, 3 Nov 2003 08:02:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGeLu-0003b6-Au for ipv6-archive@odin.ietf.org; Mon, 03 Nov 2003 08:02:39 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hA3D2cGs013822 for ipv6-archive@odin.ietf.org; Mon, 3 Nov 2003 08:02:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGeLu-0003ar-5O for ipv6-web-archive@optimus.ietf.org; Mon, 03 Nov 2003 08:02:38 -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 IAA00308 for <ipv6-web-archive@ietf.org>; Mon, 3 Nov 2003 08:02:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGeLt-0005Ai-00 for ipv6-web-archive@ietf.org; Mon, 03 Nov 2003 08:02:37 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AGeLs-0005Af-00 for ipv6-web-archive@ietf.org; Mon, 03 Nov 2003 08:02:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGeLK-0003Q6-Sv; Mon, 03 Nov 2003 08:02:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AGeKP-0003PT-3h for ipv6@optimus.ietf.org; Mon, 03 Nov 2003 08:01:05 -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 IAA00239 for <ipv6@ietf.org>; Mon, 3 Nov 2003 08:00:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AGeKO-00058s-00 for ipv6@ietf.org; Mon, 03 Nov 2003 08:01:04 -0500
Received: from merkur.iu-bremen.de ([212.201.44.27]) by ietf-mx with esmtp (Exim 4.12) id 1AGeKN-00058f-00 for ipv6@ietf.org; Mon, 03 Nov 2003 08:01:03 -0500
Received: from localhost (localhost [127.0.0.1]) by merkur.iu-bremen.de (Postfix) with ESMTP id CCA1B7B5F2; Mon, 3 Nov 2003 14:00:31 +0100 (CET)
Received: from james (unknown [212.201.47.4]) by merkur.iu-bremen.de (Postfix) with ESMTP id 17D711AD17; Mon, 3 Nov 2003 14:00:30 +0100 (CET)
Received: by james (Postfix, from userid 1000) id 201408517; Mon, 3 Nov 2003 14:00:28 +0100 (CET)
Date: Mon, 03 Nov 2003 14:00:28 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: "JINMEI Tatuya / ?$B?@L@C#:H" <jinmei@isl.rdc.toshiba.co.jp>
Cc: ipv6@ietf.org
Subject: Re: comments on draft-ietf-ipv6-scoping-arch-00.txt
Message-ID: <20031103130028.GA2238@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: "JINMEI Tatuya / ?$B?@L@C#:H" <jinmei@isl.rdc.toshiba.co.jp>, ipv6@ietf.org
References: <20031028144912.GA2088@iu-bremen.de> <y7vvfq20xfo.wl@ocean.jinmei.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <y7vvfq20xfo.wl@ocean.jinmei.org>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned: by AMaViS 0.3.12pre8
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>

On Mon, Nov 03, 2003 at 03:37:47PM +0900, JINMEI Tatuya / ?$B?@L@C#:H wrote:
> 
> >    I am not sure why this is helpful. Is there a particular reason why
> >    we can not just say that the default zone is indicated by a zone
> >    index which MUST (or SHOULD if we have to compromise) be zero?
> 
> Hmm, from a quick re-read of the draft, I don't see a particular
> reason for not using a stronger word.  Perhaps the intention was the
> choice is purely local to the node.  Even so, if using a specific
> requirement helps the MIB work, I think it is reasonable to use a
> strong word.  So, could you tell me the MIB document that can be
> clearer if we use MUST or SHOULD to specify the default zone ID?

The document in question is <draft-ietf-ops-rfc3291bis-01.txt> and
it says in several places that 0 refers to the default zone. It would
be nice if the scoping architecture could actually back this up by at
least saying the default zone SHOULD be identified by the zone index 0.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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