Re: [Diffserv] APIs for diffserv

Brian E Carpenter <brian@hursley.ibm.com> Wed, 16 October 2002 14:59 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 KAA02191 for <diffserv-archive@odin.ietf.org>; Wed, 16 Oct 2002 10:59:55 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9GF1dI07914 for diffserv-archive@odin.ietf.org; Wed, 16 Oct 2002 11:01:39 -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 g9GElDv06851; Wed, 16 Oct 2002 10:47:13 -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 g9GEONv04735 for <diffserv@optimus.ietf.org>; Wed, 16 Oct 2002 10:24:23 -0400
Received: from d12lmsgate-2.de.ibm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00325 for <diffserv@ietf.org>; Wed, 16 Oct 2002 10:22:09 -0400 (EDT)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23]) by d12lmsgate-2.de.ibm.com (8.12.3/8.12.3) with ESMTP id g9GEOHSZ043796; Wed, 16 Oct 2002 16:24:18 +0200
Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140]) by d12relay02.de.ibm.com (8.12.3/NCO/VER6.4) with SMTP id g9GEOEmd032450; Wed, 16 Oct 2002 16:24:15 +0200
Received: from gsine01.us.sine.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03) id AA57944 from <brian@hursley.ibm.com>; Wed, 16 Oct 2002 16:24:09 +0200
Message-Id: <3DAD7682.E201EE57@hursley.ibm.com>
Date: Wed, 16 Oct 2002 16:24:02 +0200
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr,de
Mime-Version: 1.0
To: itojun@iijlab.net
Cc: Thomas Narten <narten@us.ibm.com>, diffserv@ietf.org, ipng@sunroof.eng.sun.com
Subject: Re: [Diffserv] APIs for diffserv
References: <20021016012803.96DC14B22@coconut.itojun.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit

itojun@iijlab.net wrote:
> 
> >> 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.
> 
>         the API for traffic class field is merged into 2292bis.  see 2292bis
>         for exact wording i've put in.  basically ECN bits specified by user
>         can be overridden by the kernel, if the kernel implements ECN
>         mechanism (like for TCP).
> 
>         i stopped updating draft-itojun-ipv6-flowlabel-api-01.txt as there were
>         a lot of discussions on flowlabel semantics, like
>         draft-ietf-ipv6-flow-label-03.txt.
>         my plan was to re-start on the API side once the flowlabel semantics
>         discussion gets completed.  btw, i don't think flowlabel relates to
>         diffserv, am i right?

That is slightly contentious. The flow-label draft does not
define use cases, but if that draft is approved in its present
form I know how to define a diffserv use case for the
flow label (and there are several other use cases). However, it
shouldn't affect the socket API discussion.

   Brian
_______________________________________________
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