IETF Logo Mail Archive

[Diffserv] APIs for diffserv

Thomas Narten <narten@us.ibm.com> Tue, 15 October 2002 19:57 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13788 for <diffserv-archive@odin.ietf.org>; Tue, 15 Oct 2002 15:57:17 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9FJx3b04800 for diffserv-archive@odin.ietf.org; Tue, 15 Oct 2002 15:59:03 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FJeRv03850; Tue, 15 Oct 2002 15:40:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FDiVv16007 for <diffserv@optimus.ietf.org>; Tue, 15 Oct 2002 09:44:31 -0400
Received: from e2.ny.us.ibm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01362 for <diffserv@ietf.org>; Tue, 15 Oct 2002 09:42:17 -0400 (EDT)
Received: from northrelay03.pok.ibm.com (northrelay03.pok.ibm.com [9.56.224.151]) by e2.ny.us.ibm.com (8.12.2/8.12.2) with ESMTP id g9FDiQbo117944; Tue, 15 Oct 2002 09:44:26 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.12.14]) by northrelay03.pok.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id g9FDiOv5088518; Tue, 15 Oct 2002 09:44:24 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id g9FDgF122300; Tue, 15 Oct 2002 09:42:15 -0400
Message-Id: <200210151342.g9FDgF122300@rotala.raleigh.ibm.com>
To: diffserv@ietf.org
cc: ipng@sunroof.eng.sun.com
Date: Tue, 15 Oct 2002 09:42:15 -0400
From: Thomas Narten <narten@us.ibm.com>
Subject: [Diffserv] APIs for diffserv
Sender: diffserv-admin@ietf.org
Errors-To: diffserv-admin@ietf.org
X-BeenThere: diffserv@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/diffserv>, <mailto:diffserv-request@ietf.org?subject=unsubscribe>
List-Id: Diffserv Discussion List <diffserv.ietf.org>
List-Post: <mailto:diffserv@ietf.org>
List-Help: <mailto:diffserv-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/diffserv>, <mailto:diffserv-request@ietf.org?subject=subscribe>

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
_______________________________________________
diffserv mailing list
diffserv@ietf.org
https://www1.ietf.org/mailman/listinfo/diffserv
Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html

v2.23.0 | Report a Bug | By Email