Re: [Diffserv] APIs for diffserv

Pekka Savola <pekkas@netcore.fi> Wed, 16 October 2002 03: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 XAA23188 for <diffserv-archive@odin.ietf.org>; Tue, 15 Oct 2002 23:57:30 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9G3xIa28042 for diffserv-archive@odin.ietf.org; Tue, 15 Oct 2002 23:59:18 -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 g9G3mwv27613; Tue, 15 Oct 2002 23:48:58 -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 g9FL4qv09059 for <diffserv@optimus.ietf.org>; Tue, 15 Oct 2002 17:04:52 -0400
Received: from netcore.fi (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15903 for <diffserv@ietf.org>; Tue, 15 Oct 2002 17:02:36 -0400 (EDT)
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id g9FL4ed05865; Wed, 16 Oct 2002 00:04:41 +0300
Date: Wed, 16 Oct 2002 00:04:40 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: Brian E Carpenter <brian@hursley.ibm.com>
cc: Thomas Narten <narten@us.ibm.com>, diffserv@ietf.org, ipng@sunroof.eng.sun.com, Jun-ichiro itojun Hagino <itojun@iijlab.net>
Subject: Re: [Diffserv] APIs for diffserv
In-Reply-To: <3DAC7C39.A17C7C3C@hursley.ibm.com>
Message-ID: <Pine.LNX.4.44.0210160001230.5853-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
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>

On Tue, 15 Oct 2002, Brian E Carpenter wrote:
> Thomas Narten wrote:
> > 
> > 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?
> 
> There was draft-itojun-ipv6-flowlabel-api-01.txt (April 2001).
> itojun may want to comment.
[...]

And also draft-itojun-ipv6-tclass-api-03.txt (July 2001):

ftp://ftp.itojun.org/pub/paper/draft-itojun-ipv6-tclass-api-03.txt

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords

_______________________________________________
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