The IPv6 basic and advanced APIs include placeholders/hooks for
specifying the Flow Label on outgoing IPv6 packets. But the way the
API is specified, the entire first 32 bits of the IP header can be
specified, which includes the Traffic Class field. Many of the details
are unspecified, however.
Questions:
1) What work has been done with regards to specifying an API for
setting the Traffic Class fields? Anything other than the IPv6
APIs?
2) Is it adequiate for the existing IPv6 APIs (basic and advanced)
to simply allow the traffic class to be set via the flow label
mechanism (without specifying the details much)?
3) What about APIs for IPv4? Aren't they needed too?
4) Or is there an assumption here that endpoint applications setting
the traffic class themselves via an API is not particularly
interesting or necessary?
Have a look at
draft-ietf-ipngwg-rfc2553bis-07.txt and
draft-ietf-ipngwg-rfc2292bis-07.txt
for the details of what has been specified so far.
Thoughts of what (if anything more) should be done with APIs for
diffserv would be appreciated.
Thomas
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
