Mike,

You forgot a third:

3) Readable when the packet is encrypted

Thus, QoS can be accomplished even if the
rest of the packet is encrypted.

            jak

----- Original Message -----
From: "Michael Thomas" <[EMAIL PROTECTED]>
To: "Margaret Wasserman" <[EMAIL PROTECTED]>
Cc: "Brian E Carpenter" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, December 17, 2001 8:21 AM
Subject: Re: draft-rajahalme-ipv6-flow-label-00.txt


> Margaret Wasserman writes:
>  > If I seem to be missing an important point or concept, please send
>  > some hints or pointers.
>
> Margaret,
>
> I don't think you're alone wondering what all the
> fuss is about with the flow label since it's
> fairly obvious that normal Intserv classifiers
> function equivalently. However, there's two fairly
> important things that the flow label brings to the
> party:
>
> 1) Speed
>
> Speed is primarily due to the fact that the flow's
> tag is in the IP header itself at a fixed
> location. This simplifies the processing --
> helpful for ASIC's -- as well allowing
> classification of problematic flows, such
> as IPsec and flows which contain destination
> options or other things which require that
> the header list be traversed.
>
> 2) Protocol independence
>
> RSVP normally uses a 5 tuple which implicitly
> expect a source and destination port. Other
> protocols either disagree (IPsec which requires
> classification based on SPI) or are undefined
> (SCTP...). Use of the flow label will allow us to
> deploy new protocols without having to come up
> with new RFC's to describe how to create its own
> flow classifier. Better, it will not require
> software/hardware upgrades in routers to be able
> to give QoS treatment to new IP protocols.
>
>      Mike
> --------------------------------------------------------------------
> 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]
--------------------------------------------------------------------

Reply via email to