Unfortunately I found another few of points... I can't remember whether we discussed them before.
Somewhere in section 4 I think we should add something along these lines:
4.x Special header fields
If a node supports the Traffic Class field, it MUST do so in accordance with [RFC2474], [RFC 3168], or both. Hosts that do not support this field MUST set it to zero when sending packets. Routers that do not support this field MUST NOT change its value when forwarding packets.
If a node supports the Flow Label field, it MUST do so in accordance with [RFC 3697]. Hosts that do not support this field MUST set it to zero when sending packets. Routers that do not support this field MUST NOT change its value when forwarding packets.
Then I think section 4.5.1 needs to be changed:
The IPv6 Addressing Architecture [RFC-3513] MUST be supported, as updated by [RFC XXXX].
(where that is the future RFC version of draft-ietf-ipv6-deprecate-site-local-03.txt)
Brian
[EMAIL PROTECTED] wrote:
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Version 6 Working Group Working Group of the IETF.
Title : IPv6 Node Requirements Author(s) : J. Loughney Filename : draft-ietf-ipv6-node-requirements-09.txt Pages : 19 Date : 2004-5-24 This document defines requirements for IPv6 nodes. It is expected that IPv6 will be deployed in a wide range of devices and situations. Specifying the requirements for IPv6 nodes allows IPv6 to function well and interoperate in a large number of situations and deployments.
A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipv6-node-requirements-09.txt
-------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
