NetBSD Problem Report #48307
From www@NetBSD.org Sun Oct 13 15:25:12 2013
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "mail.NetBSD.org", Issuer "Postmaster NetBSD.org" (verified OK))
by mollari.NetBSD.org (Postfix) with ESMTPS id A8BEE72535
for <gnats-bugs@gnats.NetBSD.org>; Sun, 13 Oct 2013 15:25:12 +0000 (UTC)
Message-Id: <20131013152510.E3FC27261B@mollari.NetBSD.org>
Date: Sun, 13 Oct 2013 15:25:10 +0000 (UTC)
From: sm+bsd@elandsys.com
Reply-To: sm+bsd@elandsys.com
To: gnats-bugs@NetBSD.org
Subject: Updating http://www.netbsd.org/docs/network/ipv6/
X-Send-Pr-Version: www-1.0
>Number: 48307
>Category: misc
>Synopsis: Updating http://www.netbsd.org/docs/network/ipv6/
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: misc-bug-people
>State: closed
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sun Oct 13 15:30:00 +0000 2013
>Closed-Date: Sun Oct 13 17:18:32 +0000 2013
>Last-Modified: Sun Oct 13 17:20:00 +0000 2013
>Originator: S. Moonesamy
>Release: not applicable
>Organization:
>Environment:
not applicable
>Description:
The page at http://www.netbsd.org/docs/network/ipv6/ could be updated as:
1. IPsec is now recommended instead of being mandatory (see RFC 6434)
2. Stateless host autoconfiguration is currently specified in RFC 4862.
3. DHCPv6 is specified in RFC3315
4. ip6.int has been deprecated (see RFC 4159).
5. 6bone prefixes are no longer valid since June 2006.
6. A6 now has a historic status.
7. The webring has been discontinued.
>How-To-Repeat:
>Fix:
--- docs/network/ipv6/index.xml.orig 2012-07-20 16:23:29.000000000 +0000
+++ docs/network/ipv6/index.xml 2013-10-13 08:00:04.000000000 +0000
@@ -34,7 +34,6 @@
<listitem><ulink url="http://orange.kame.net/dev/cvsweb.cgi/kame/IMPLEMENTATION">detailed information on the implementation</ulink></listitem>
<listitem><ulink url="http://www.onlamp.com/pub/a/onlamp/2001/05/24/ipv6_tutorial.html">Introduction to IPv6</ulink> by Hubert Feyrer</listitem>
<listitem><ulink url="http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html">Getting Connected with 6to4</ulink> by Hubert Feyrer</listitem>
- <listitem>Some <ulink url="http://www.ipv6tools.com/">IPv6 tools</ulink> accessible through a web page.</listitem>
</itemizedlist>
</sect2>
@@ -106,13 +105,13 @@
a DHCP server.
With IPv6, a "stateless host autoconfiguration" mechanism is mandatory.
This is much simpler to use and manage than IPv4 DHCP.
- <!-- RFC -->RFC2462 has the specification for it.</listitem>
+ <!-- RFC -->RFC4862 has the specification for it.</listitem>
<listitem><emphasis role="bold">Security</emphasis>.
With IPv4, IPsec is optional and you need to ask the peer if it
supports IPsec.
- With IPv6, IPsec support is mandatory.
- By mandating IPsec, we can assume that you can secure your IP
+ With IPv6, IPsec support is recommended.
+ By recommending IPsec, we can assume that you can secure your IP
communication whenever you talk to IPv6 devices.</listitem>
<listitem><emphasis role="bold">Friendly to traffic engineering technologies</emphasis>.
@@ -241,9 +240,9 @@
<para>There are two separate mechanisms defined for IPv6 host autoconfiguration.
One is called <emphasis>stateless address autoconfiguration</emphasis>,
and is specified in <!-- RFC -->RFC2462.
- The other is called <emphasis>DHCPv6</emphasis>, and is being discussed by the IETF dhc
- working group.
- NetBSD currently implements the former.</para>
+ The other is called <emphasis>DHCPv6</emphasis>, and is specified in
+ <!-- RFC --> RFC3315. DHCPv6 is discussed in the IETF dhc working group.
+ NetBSD currently implements the RFC2462.</para>
<para>Stateless address configuration basically works as follows.
We have two parties here: a host (which is to be autoconfigured) and a router
@@ -516,15 +515,14 @@
<para>Note: If you have heard about A6 records and bitstring
labels for DNS – A6 and bitstrings are now in
- experimental status, so you don't need to worry about them. AAAA
+ historic status, so you don't need to worry about them. AAAA
is to be used for production service and works
fine.</para>
- <para>Also note that the reverse DNS table is moving from
+ <para>Also note that the reverse DNS table has moved from
ip6.int to ip6.arpa; 6Bone (3ffe)
- addresses are at the time of this writing only known in ip6.int,
- production addresses should be announced under ip6.arpa, as
- ip6.int will go away.</para>
+ addresses are no longer used. Production addresses should be
+ announced under ip6.arpa.</para>
</listitem>
</orderedlist>
@@ -594,12 +592,6 @@
encapsulated into IPv4 packets). The section talks about the
latter case.</para>
- <para>You can hook your machine up to experimental IPv6 network,
- called <ulink url="http://www.6bone.net/">"6bone"</ulink>. You
- will need to talk with nearest 6bone site, to get your IPv6
- address prefix. Note that you'll need to have a fixed IPv4
- global address for this.</para>
-
<para>If you do not have a fixed IPv4 global address (if you are
using dialup ISP connection), don't panic. You can hook yourself
up to <ulink url="http://www.freenet6.net/">Freenet6</ulink>.
@@ -1172,11 +1164,9 @@
<title> Where to ask questions</title>
<para>If you have any questions, do not hesitate to ask on the
- tech-net mailing list, or <ulink
- url="http://www.ipv6.org/">users@ipv6.org</ulink>. When you ask
- about your configuration, be VERY sure to attach a network
- diagram for your site. Without a network diagram, nobody can
- guess your network configuration.</para>
+ tech-net mailing list. When you ask about your configuration, be
+ VERY sure to attach a network diagram for your site. Without a
+ network diagram, nobody can guess your network configuration.</para>
</sect3>
<sect3 id="maintenance">
@@ -1291,18 +1281,9 @@
</sect3>
-<para>This <ulink url="http://www.ipv6.euronet.be/webring/">IPv6
-Configuration Help</ulink> site is owned by <ulink url="/">The NetBSD
+<para>This IPv6 Configuration Help site is owned by <ulink url="/">The NetBSD
Project</ulink>.</para>
-<para>
-[
-<ulink url="http://go.webring.yahoo.com/go?ring=ipv6&id=3&prev">Previous</ulink> |
-<ulink url="http://go.webring.yahoo.com/go?ring=ipv6&id=3&next">Next</ulink> |
-<ulink url="http://go.webring.yahoo.com/go?ring=ipv6&id=3&random">Random Site</ulink> |
-<ulink url="http://nav.webring.yahoo.com/hub?ring=ipv6&list">List Sites</ulink>
-]
-</para>
</sect2>
</sect1>
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed
State-Changed-By: spz@NetBSD.org
State-Changed-When: Sun, 13 Oct 2013 17:18:32 +0000
State-Changed-Why:
thanks for the prodding, the page needed a scrub :)
.
From: "S.P.Zeidler" <spz@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc:
Subject: PR/48307 CVS commit: htdocs/docs/network/ipv6
Date: Sun, 13 Oct 2013 17:15:59 +0000
Module Name: htdocs
Committed By: spz
Date: Sun Oct 13 17:15:59 UTC 2013
Modified Files:
htdocs/docs/network/ipv6: index.xml
Log Message:
pick up improvement suggestions from PR48307
To generate a diff of this commit:
cvs rdiff -u -r1.10 -r1.11 htdocs/docs/network/ipv6/index.xml
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.