Re: [16NG] Re: traffic classification

Jari Arkko <jari.arkko@piuha.net> Mon, 05 February 2007 16:42 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HE6vH-0006we-HD; Mon, 05 Feb 2007 11:42:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HE6vF-0006wQ-Kz for 16ng@ietf.org; Mon, 05 Feb 2007 11:42:29 -0500
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HE6vC-0006V1-Ui for 16ng@ietf.org; Mon, 05 Feb 2007 11:42:29 -0500
Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id ACDD5198775; Mon, 5 Feb 2007 18:42:23 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id A32E9198774; Mon, 5 Feb 2007 18:42:22 +0200 (EET)
Message-ID: <45C75E6E.3040507@piuha.net>
Date: Mon, 05 Feb 2007 11:42:22 -0500
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.9 (X11/20070104)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [16NG] Re: traffic classification
References: <45BDFD58.8060202@piuha.net> <45C099CD.8010506@piuha.net> <45C0A227.1040303@motorola.com> <45C0A4D1.9010602@piuha.net> <92e919fb0701310737m45cbb6f8ud1dab68aa75f380d@mail.gmail.com> <45C0C057.5040402@motorola.com> <92e919fb0702011851v42ff4d03m76be205179a6cc43@mail.gmail.com> <45C30A7D.2050605@motorola.com> <92e919fb0702022132hc20a415k39ed496a111017f5@mail.gmail.com> <45C48A0A.1010301@motorola.com> <45C6370C.9090603@piuha.net> <45C6FD49.1020501@motorola.com>
In-Reply-To: <45C6FD49.1020501@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

Alexandru,
>
> For QoS, there exist no resolution function like ND or DNS that would
> resolve a DSCP into a 802.16 Traffic Priority.
>
> Remark I'm not talking about mapping an IPv6 Traffic Class DSCP into a
> CID but into a 802.16 Traffic Priority or a 802.16 Service Name.
>
I browsed the relevant parts of 802.16 standards today.

The standard clearly says that it has a capability to filter
based on multiple fields in an IP packet, including the DSCP
field. The standard also clearly says that the classification
ensures the packet is delivered using the right QoS
characteristics.

I understand the desire to have an automatic mapping
that operates without any configured policy. But in
this case we clearly have functionality in the lower
layer that is designed for the QoS purpose. We may
disagree with that design. But it would be odd if the
IETF added its own competing QoS mapping mechanisms
on top of it.

Jari


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng