From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 3 18:11:33 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59DFA10656B7 for ; Tue, 3 Jan 2012 18:11:33 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 1F8988FC1B for ; Tue, 3 Jan 2012 18:11:32 +0000 (UTC) Received: from pps.filterd (ltcfislmsgpa02 [127.0.0.1]) by ltcfislmsgpa02.fnfis.com (8.14.4/8.14.4) with SMTP id q03HQ5KU032231; Tue, 3 Jan 2012 12:11:32 -0600 Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa02.fnfis.com with ESMTP id 1245hc8c0v-28 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 03 Jan 2012 12:11:32 -0600 Received: from dtwin (10.14.152.15) by smtp.fisglobal.com (10.132.206.31) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 3 Jan 2012 12:11:24 -0600 From: Devin Teske To: "'Matthew Seaman'" , References: <2092634439.782373.1325609539518.JavaMail.root@erie.cs.uoguelph.ca> <4F03425C.6040104@infracaninophile.co.uk> In-Reply-To: <4F03425C.6040104@infracaninophile.co.uk> Date: Tue, 3 Jan 2012 10:11:29 -0800 Message-ID: <04db01ccca43$1e93bd00$5bbb3700$@fisglobal.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQIVGeTRooOjsrMpyRvNlvFBKfeIZwHmTtfYlVsev6A= Content-Language: en-us X-Originating-IP: [10.14.152.15] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110, 1.0.211, 0.0.0000 definitions=2012-01-03_03:2012-01-03, 2012-01-03, 1970-01-01 signatures=0 Content-Type: text/plain; charset="utf-8" Cc: Subject: RE: [ANN] host-setup 4.0 released X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2012 18:11:33 -0000 > -----Original Message----- > From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd- > hackers@freebsd.org] On Behalf Of Matthew Seaman > Sent: Tuesday, January 03, 2012 10:01 AM > To: freebsd-hackers@freebsd.org > Subject: Re: [ANN] host-setup 4.0 released >=20 > On 03/01/2012 16:52, Rick Macklem wrote: > > The basics are in RFC4291, but I think that inet_pton(3) knows how to > > deal with it. (I think "::" can be used once to specify the longest # > > of 16bit fields that are all zeros.) >=20 > RFC 4291 has a basic description of the textual representation of IPv6 ad= dresses, > but it is ambiguous: there are several different ways to present the same= address > according to the RFC 4291 rules. >=20 > inet_pton(3) follows RFC 5952 which is a superset of the 4291 rules, only= allowing > a single, unambiguous representation for each IPv6 number. >=20 > > After inet_pton() has translated it to a binary address, then the > > macros in sys/netinet6/in6.h can be used to determine if the address is= a > loopback, etc. >=20 > While 5952 describes how to correctly present an IPv6 address, there's st= ill lots of > important other stuff in 4291. For instance bit 70 in an > IPv6 address flags that the address is derived from a number hardwired in= to the > interface -- typically the ethernet MAC address, as is commonly done for = SLAAC > (StateLess Address Autoconfiguration: RFC 4862, rtsold(8), rtadvd(8)). So= an > arbitrarily invented address should have that bit set to zero. Bit 71 is= also special, > indicating manycast vs unicast, and should also be zero for the vast majo= rity of > uses. > See > http://www.infracaninophile.co.uk/articles/hotchpotch.html#rand-aaaa.pl > for some perl code that operates in this area. >=20 > Also of interest: RFC 5156 which lists IPv6 address ranges dedicated to s= pecial > purpose usages, and RFC 4193 which roughly is the IPv6 equivalent to RFC = 1918, > but somewhat more complicated. You might find > https://www.sixxs.net/tools/grh/ula/ relevant too, although actually usin= g that > as a registry is pretty pointless. >=20 Thank you ALL for such great feedback. We'll have to digest this information in entirety and also start playing wi= th rtsold and rtadvd in the lab. When we do add IPv6 support, it will be robust and solid (we don't like to = do things half-arsed). It might be awhile before host-setup supports IPv6 (only because we're not = using it ourselves, just yet), but it does sound like something that is rat= her desired. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.