From owner-freebsd-net@FreeBSD.ORG Tue Jan 8 22:47:17 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 952EC16A421; Tue, 8 Jan 2008 22:47:17 +0000 (UTC) (envelope-from Jinmei_Tatuya@isc.org) Received: from mon.jinmei.org (unknown [IPv6:2001:4f8:3:36::162]) by mx1.freebsd.org (Postfix) with ESMTP id 98A1B13C43E; Tue, 8 Jan 2008 22:47:17 +0000 (UTC) (envelope-from Jinmei_Tatuya@isc.org) Received: from dhcp-wi-27.sql1.isc.org (dhcp-wi-27.sql1.isc.org [204.152.189.27]) by mon.jinmei.org (Postfix) with ESMTP id 73E9433C25; Wed, 9 Jan 2008 07:47:17 +0900 (JST) Date: Tue, 08 Jan 2008 14:47:17 -0800 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Michael Tuexen In-Reply-To: <0AA9B264-8935-41E9-AC26-102ED6EE253C@lurchi.franken.de> References: <20080104215626.GA88922@goku.pumpky.net> <0AA9B264-8935-41E9-AC26-102ED6EE253C@lurchi.franken.de> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Tue, 08 Jan 2008 22:54:24 +0000 Cc: "Crist J. Clark" , net@freebsd.org Subject: Re: Text for IPv6 Scope X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jan 2008 22:47:17 -0000 At Sat, 5 Jan 2008 12:52:53 +0100, Michael Tuexen wrote: > aren't site-local IPv6 addresses depreceated (RFC 3879)? So shouldn't > the site-local stuff be removed? RFC3879 only deprecates site-local *unicast* addresses; the notion of "site-local" is still valid for multicast addresses (this is a very common misunderstanding about the "deprecation of site-local"). So we should not remove IPV6_ADDR_SCOPE_SITELOCAL from in6.h. Going back to the original question of this thread, I don't have a strong opinion on whether it's a good idea to show scope types in alphabets. But I'd point out that it might break convention (further) that an output of ifconfig can often be used as an input, too. For example, if we have: ed0: flags=8843 mtu 1500 inet6 fe80::2c4:77ff:fea1:55ed%ed0 prefixlen 64 scopeid 0x1 inet 10.211.55.11 netmask 0xffffff00 broadcast 10.211.55.255 inet6 2001:db8::1234 prefixlen 64 ether 00:c4:77:a1:55:ed media: Ethernet autoselect (10baseT/UTP) then we could do # ifconfig ed0 `ifconfig ed0 | grep 'inet6 2001'` Adding the scope type text would break this convention (at least if implemented naively). I don't know whether people care about this much, though. Also, we've actually already broken this convention by showing 'scoped 0xXX' for link-locals, so it may not be a big deal any more. BTW, the patch in its current form is not correct in that "scopeid" is the scope index of a specific type of scope, not the "scope type" (link-local, site-local, etc). --- JINMEI, Tatuya Internet Systems Consortium, Inc.