svn commit: r41721 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking

[Hiroki Sato]

Hi Tom,

Tom Rhodes <trhodes at FreeBSD.org> wrote
  in <201305231151.r4NBpYaA081350 at svn.freebsd.org>:

tr> Author: trhodes
tr> Date: Thu May 23 11:51:34 2013
tr> New Revision: 41721
tr> URL: http://svnweb.freebsd.org/changeset/doc/41721
tr>
tr> Log:
tr>   Discuss (in brief) RFC 3943 sections 3.6 and 3.7.
tr>
tr>   PR:		99506
tr>   Reviewed by:	bjk
tr>
tr> Modified:
tr>   projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml

(snip)

tr> +      <para>This option may not be required in most cases and is
tr> +	available only for compatibility while services are updated
tr> +	to support <acronym>IPv6</acronym>.  To enable the feature,
tr> +	add the following to <filename>/etc/rc.conf</filename>:</para>

 This part "while services are updated to support IPv6" looks strange
 to me.  IPv4-mapped IPv6 address is required for programs which
 supports only IPv6 to also support IPv4 on a dual stack node.  If
 this is disabled, IPv6-only programs can work only with IPv6 address.
 This is not for IPv4-only programs.

 Although all of IPv6-ready programs in the base system do not use
 IPv4-mapped IPv6 address for IPv4 sockets regardless of this option,
 the necessity of this option depends on application (Java, for
 example).  People should also refer Section 4.2 in RFC 4038.

-- Hiroki
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-doc-projects/attachments/20130524/4272ea1d/attachment.sig>