From owner-freebsd-current  Sat Feb 19  1:21:27 2000
Delivered-To: freebsd-current@freebsd.org
Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36])
	by hub.freebsd.org (Postfix) with ESMTP id CDBC337BB89
	for <freebsd-current@freebsd.org>; Sat, 19 Feb 2000 01:21:20 -0800 (PST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from m1.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway)
	id SAA15110 for <freebsd-current@freebsd.org>; Sat, 19 Feb 2000 18:20:43 +0900 (JST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master)
	id SAA13660; Sat, 19 Feb 2000 18:20:42 +0900 (JST)
Received: from localhost ([192.168.245.162]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002)
	id SAA25753; Sat, 19 Feb 2000 18:20:41 +0900 (JST)
To: freebsd-current@freebsd.org
Subject: IPv6 scoped addr format change
X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN)
X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000219182126A.shin@nd.net.fujitsu.co.jp>
Date: Sat, 19 Feb 2000 18:21:26 +0900
From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 50
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello,

Unfortunately, I have a notice that IPv6 scoped addr format
will change again.

It is once changed as the recent discussion between people who
are preparing IPv6 scoped addr draft for next IETF meeting in
March, like below.

  From    addr@scope
  To	  scope%addr

And I committed the change.
But, in more recent discussion, it further changed like below.

  From    scope%addr
  To	  addr%scope

Because some MIB expert commented that optional data before
addr is not suitable for MIB definition.

About that change I didn't committed yet, because I'm afraid of
another change. But this time the proposal seems to be stable.

But anyway, there is no guarantee that it can get concensus at
March IETF meeting, and same format could be adopted in the
RFC to be published after the meeting, maybe around April or
later.

But some scope addr format is need to be supported in 4.0.

So now I think of following things.

  -Adopt the format below now, and never change it again
   before 4.0 release.

     addr%scope

  -If future RFC will adopt another format, then support it
   also.
   E.g,

     Print out in new format.
     Support each format as input.

Sorry for flapping, but it is the best approach I can think
of now.

Thanks,
Yoshinobu Inoue


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message