Subrata Goswami wrote:
>
> Both of the following example actually only tells you
> how to set them, not how to use them and both are
> optional.
No, they tell you how to use them. A flow_spec is how intserv
identifies flows; a classifier is how diffserv classifies
packets. Yes they are both optional - like many enhancements.
>
> Given the fact that there are only 20 bits in the flow
> label, then globally only 4K flows can be defined - is that
> enough ?
It's the 2uple {source address, flow label} or possibly the
3uple {source addr, destination addr, flow label} that has to be
unique.
Brian
>
> Subrata
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Brian E Carpenter
> Sent: Thursday, December 27, 2001 5:07 AM
> To: Perry E. Metzger
> Cc: Michael Thomas; [EMAIL PROTECTED]
> Subject: Re: Flow Label
>
> "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]
> --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> 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]
> --------------------------------------------------------------------
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter
Distinguished Engineer, Internet Standards & Technology, IBM
On assignment at the IBM Zurich Laboratory, Switzerland
Board Chairman, Internet Society http://www.isoc.org
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
