Jun-ichiro itojun Hagino wrote:
>
> then why you pushed those non-IANA values in the presentation?
> this is the source of confusion.
You refer to the last 2 slides of the 14 slide presentation, each WITH
BIG TITLES:
OTHER POSSIBLE IPv6 FLOW LABEL FORMATS, presenting Appendix A of the
draft.
Your message title confused me: I thought you've read the draft, and
based your comments on the draft.
I agree. Certainly less confusion, less nit picking, non-bias, always
helps.
<...>
> ... have you ever used alignment-picky CPUs like alpha?
>
at the top of page 27 in the draft, in Appendix A:
"...IPv6 headers are 8byte aligned, therefore the length could be
represented as the number of 8byte
chunks occupied by the headers, in which case the maximum length would
be 32Kbytes."
With this representation, the receiver would simply shift the value of
the field with 3 bits, thus ensuring a 8 byte alignment on accessing the
TCP/UDP headers.
>...
> how can you trust IPv6 stack that is in the possession of end user?
> they can be hacked up. the only devices you can trust is those you
> administer in your diffserv cloud. you can never trust customers
> devices.
>
It seems to me that you are still missing the points made earlier.
The Diffserv QoS engines in the access routers do a policing
(classification&metering&dropping) that trims the high level QoS traffic
-- hacked by a user, or not -- to the level specified in SLAs, TCAs. So,
a user, at the most, uses up all that was contracted with the ISP, and
paid for, anyway. This is in fact THE BEAUTY of THE MODEL.
> itojun
S/MIME Cryptographic Signature
