Re: [2461bis issue 250] Reception of prefix option with prefix length > 64

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Fri, 27 February 2004 07:24 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 CAA17696 for <ipv6-archive@odin.ietf.org>; Fri, 27 Feb 2004 02:24:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwcM9-0008ND-ME for ipv6-archive@odin.ietf.org; Fri, 27 Feb 2004 02:24:24 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1R7OLH6032148 for ipv6-archive@odin.ietf.org; Fri, 27 Feb 2004 02:24:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwcM7-0008MK-J1 for ipv6-web-archive@optimus.ietf.org; Fri, 27 Feb 2004 02:24:19 -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 CAA17648 for <ipv6-web-archive@ietf.org>; Fri, 27 Feb 2004 02:24:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AwcM4-0005eA-00 for ipv6-web-archive@ietf.org; Fri, 27 Feb 2004 02:24:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AwcLD-0005Y9-00 for ipv6-web-archive@ietf.org; Fri, 27 Feb 2004 02:23:23 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AwcKO-0005RL-00 for ipv6-web-archive@ietf.org; Fri, 27 Feb 2004 02:22:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwcJv-0007Fr-54; Fri, 27 Feb 2004 02:22:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AwcJN-00073H-78 for ipv6@optimus.ietf.org; Fri, 27 Feb 2004 02:21:29 -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 CAA17339 for <ipv6@ietf.org>; Fri, 27 Feb 2004 02:21:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AwcJ9-0005JH-00 for ipv6@ietf.org; Fri, 27 Feb 2004 02:21:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AwcIK-0005DV-00 for ipv6@ietf.org; Fri, 27 Feb 2004 02:20:25 -0500
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1AwcHl-00056U-00 for ipv6@ietf.org; Fri, 27 Feb 2004 02:19:49 -0500
Received: from ocean.jinmei.org (unknown [3ffe:501:100f:1048:200:39ff:fe5e:cfd7]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 0BB0715210; Fri, 27 Feb 2004 16:19:49 +0900 (JST)
Date: Fri, 27 Feb 2004 16:20:00 +0900
Message-ID: <y7vad35j8f3.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: Soliman Hesham <H.Soliman@flarion.com>
Cc: IETF Mailing List <ipv6@ietf.org>
Subject: Re: [2461bis issue 250] Reception of prefix option with prefix length > 64
In-Reply-To: <9E3BA3946476AD4EB94672712B12A85F042123@ftmail.lab.flarion.com>
References: <9E3BA3946476AD4EB94672712B12A85F042123@ftmail.lab.flarion.com>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset="US-ASCII"
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.5 required=5.0 tests=AWL,SUBJ_HAS_SPACES autolearn=no version=2.60

Catching up an old topic...

>>>>> On Tue, 10 Feb 2004 07:26:05 -0500, 
>>>>> Soliman Hesham <H.Soliman@flarion.com> said:

> What should a node do upon reception of a prefix option with the prefix
> length set to a value >64?

> The issue can be stated more accurately to say:
> What should a host do upon reception of a prefix option with the prefix
> length set to a value != 64?

You appear to focus on the address configuration side of this issue.
And RFC2461 is quite clear that the prefix handling in RFC2461 should
be separate from that in RFC2462, so I'd see this as a 2462bis issue
and not a 2461bis issue.

Regarding rfc2461bis, my impression is that the receiving node must
accept an prefix information in terms of the ND (2461 or bis) part
regardless of the prefix length.

For example, assuming a 64-bit interface identifier, if we receive an
RA containing an prefix information option with 80-bit prefix length
and with the L and A bits both being set, RFC2462 clearly says that
the prefix MUST be ignored in terms of address configuration:

       If the sum of the prefix length and interface identifier length
       does not equal 128 bits, the Prefix Information option MUST be
       ignored.
(RFC2462 Section 5.5.3, )

However, I think the receiving node should still consider the prefix
as valid in terms of ND (i.e., consider it as "on-link") and modify
the next-hop determination accordingly.

The questions are:

1. is this a correct understanding of the intention of RFC2461?
2. if yes, is this a reasonable behavior?
3. if yes (for both 1 and 2), should this explicitly be documented in
   rfc2461bis?

And my personal answers are:

yes for 1 (of course.  this is my understanding).
not sure for 2, but I don't oppose to the behavior (though I'll need
to change my own implementation).
probably yes for 3.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

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