"Perry E. Metzger" wrote:
...
> Repeating my earlier request:
>
> I'm an old fashioned kind of engineer. I'd like to see some folks from
> router vendors give us precise information about the *exact* use
> they'll put the flow label information to,
Here are the precise definitions the IETF has documented:
1) IPv6 Flow-label FILTER_SPEC object: Class = 10, C-Type = 3
[RFC 2205, page 87]
2) diffServMultiFieldClfrFlowId OBJECT-TYPE
SYNTAX Unsigned32 (0..1048575)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The flow identifier in an IPv6 header."
::= { diffServMultiFieldClfrEntry 8 }
[draft-ietf-diffserv-mib-16.txt, approved as PS, page 52]
but these will be largely ignored by implementors until RFC 2460
is cleaned up.
> and quantitative
> information about how much better it will be for them to have the flow
> label than not to have it.
Nobody is going to publish that sort of competitive data. As noted earlier,
this is quite likely to be either qualitative (ability to classify ESP
traffic) or simply a matter of heat dissipation and the marginal cost of
a chip set.
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]
--------------------------------------------------------------------
