Solaris 8 (SPARC Platform Edition) Online Release Notes

Chapter 5. Documentation Issues

Documentation Errata

Document Affected: IPv6 Header Format in System Administration Guide, Volume 3

The 4-bit Priority field description reflects RFC 1883, which has been obsoleted by RFC 2460 (Solaris 8 implements RFC 2460). Consequently, the Priority field has been replaced by an 8-bit Traffic Class field. The IPv6 Header Format figure should identify the Traffic Class field in place of the Priority field. The Priority bullet on this page should also be replaced by the following Traffic Class description:

Traffic Class - 8 bit traffic class field.

This new value also reduces the number of bits allocated to the "Flow Label" field to 20 bits.

Document Affected: Priority Values in System Administration Guide, Volume 3

The 4-bit Priority field description reflects RFC 1883, which has been obsoleted by RFC 2460 (Solaris 8 implements RFC 2460). Consequently, the Priority field has been replaced by the 8-bit Traffic Class field. The Priority section should be replaced by the following Traffic Classes section:

Traffic Classes

Originating nodes and forwarding routers can use the 8-bit Traffic Class field in the IPv6 header to identify and distinguish between different classes or priorities of IPv6 packets.

The following general requirements apply to the Traffic Class field:

• The service interface to the IPv6 service within a node must provide a means for an upper-layer protocol to supply the value of the Traffic Class bits in packets originated by that upper-layer protocol. The default value must be zero for all 8 bits.

• Nodes that support a specific use of some or all of the Traffic Class bits can change the value of those bits in packets that they originate, forward, or receive, as required for that specific use. Nodes should ignore and leave unchanged any bits of the Traffic Class field for which they do not support a specific use.

Document Affected: Implementing IPsec in System Administration Guide, Volume 3

Step 10c in this procedure incorrectly omits the addition of the up parameter required in the line added to the /etc/hostname.ip.tun0 file. Consequently, the up parameter must be added at the end of the line entry in this step.

Document Affected: NFS Parameters for the nfs Module in System Administration Guide, Volume 3 (4299091)

Several corrections apply to this section:

• For the nfs_32_time_ok symbol:

  • Change the symbol name to: nfs_allow_preepoch_time.

  • Change the description to: This symbol controls whether the NFS client or server allows file time stamps that precedes 1970.

  • No change to the default description.

  • Delete the nfs_acl_cache symbol entry.

• Add a nfs_disable_rddir_cache symbol entry.

  • Description: Some servers do not properly update the attributes of the directory when changes are made. To allow interoperability with these broken servers, set this variable to disable the readdir cache.

  • Default:Sset to off(0).

• For the nfs_lookup_neg_cache and nfs3_lookup_neg_cache symbols:

  • Change the default to 1. Ignore the comment about the directory name caching.

• For the nrnode symbol: nrnode

  • Change the default description to: set to ncsize. By setting the variable to 1 you are effectively disabling the cache, not because there is an explicit check to see whether or not it is 1, but because you are creating a very small cache.

• For the nfs_write_error_interval symbol:

  • Change the description: This symbol controls how often NFS ENOSPC and EDQUOT write error messages are logged. Its units are in seconds.

  • No change to the default description.

Document Affected: NFS Parameters for the nfs Module in System Administration Guide, Volume 3 (4299091)

• Delete the nfsreadmap symbol entry.

Document Affected: NFS Parameters for rpcsec Parameters in System Administration Guide, Volume 3 (4299091)

For the authdes_cachesz symbol:

• Change the default description: Defaults to 1024.

• Delete the authkerb_cachesz symbol entry.

• Delete the authkerb_win symbol entry.

End-Of-Software Support Statements In Future Releases		CERT Advisories