works for me
---
>From [EMAIL PROTECTED] Thu Dec 27 10:45:19 2001
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to
[EMAIL PROTECTED] using -f
Date: Thu, 27 Dec 2001 16:43:48 +0100
From: Brian E Carpenter <[EMAIL PROTECTED]>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr
Mime-Version: 1.0
To: [EMAIL PROTECTED]
Subject: Re: Proposed update to RFC 2460 [was Re: Flow Label]
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: [EMAIL PROTECTED]
Precedence: bulk
Taking Scott's suggestion, here's another try:
I'd like to propose the following as the
complete and total replacement of Section 6 of RFC 2460.
The 20-bit Flow Label field in the IPv6 header MAY be set by a
source to uniquely label sets of packets. Nodes that do not support
the Flow Label field MUST set the field to zero when originating a
packet, and MUST ignore the field when receiving a packet. All routers
MUST pass the field on unchanged when forwarding a packet.
This specification does not further define the meaning of the
Flow Label.
[and delete Appendix A, which is unhelpful.]
Brian
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
