> I would like to suggest another choice:
>
> e) a set of bits we hold in reserve for the future
>
> I don't think that we have enough experience to pick between a), b), or c)
> now, and think that something might come up in the future where 28 bits in
> the IPv6 header might be very useful. This might not have anything to do
> with QOS.
Currently the field is defined as "must be random"; if we want to
preserve the ability to recycle it for something else in the future,
we need to redefine it *NOW* as a "must be zero".
- Bill
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
- Higher level question about flow label Brian E Carpenter
- Re: Higher level question about flow label Jim Bound
- Re: Higher level question about flow label Bob Hinden
- Re: Higher level question about flow label Brian Haberman
- RE: Higher level question about flow label john . loughney
- Re: Higher level question about flow label Tim Chown
- Re: Higher level question about flow label Francis Dupont
- Re: Higher level question about flow label Bob Hinden
- Re: Higher level question about flow label Bill Sommerfeld
- Re: Higher level question about flow label Francis Dupont
- Re: Higher level question about flow label Brian E Carpenter
- RE: Higher level question about flow label Thomas Eklund
- Re: Higher level question about flow label Brian E Carpenter
- RE: Higher level question about flow label Thomas Eklund
- Re: Higher level question about flow label Jim Bound
