Re: [16NG] Re: traffic classification
Basavaraj Patil <basavaraj.patil@nokia.com> Mon, 05 February 2007 18:42 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1HE8mx-0005CB-Ut; Mon, 05 Feb 2007 13:42:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1HE8mx-0005C6-5b
for 16ng@ietf.org; Mon, 05 Feb 2007 13:42:03 -0500
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HE8mu-0004u9-N3
for 16ng@ietf.org; Mon, 05 Feb 2007 13:42:03 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
l15IdS0g005693; Mon, 5 Feb 2007 20:39:50 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 5 Feb 2007 20:40:57 +0200
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 5 Feb 2007 12:40:54 -0600
Received: from 172.19.244.84 ([172.19.244.84]) by daebe101.NOE.Nokia.com
([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ;
Mon, 5 Feb 2007 18:40:54 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Mon, 05 Feb 2007 12:43:30 -0600
Subject: Re: [16NG] Re: traffic classification
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Jari Arkko <jari.arkko@piuha.net>,
Alexandru Petrescu <alexandru.petrescu@motorola.com>
Message-ID: <C1ECD6F2.2DB5D%basavaraj.patil@nokia.com>
Thread-Topic: [16NG] Re: traffic classification
Thread-Index: AcdJVYeixil1m7VIEdugIwARJNUNiA==
In-Reply-To: <45C75E6E.3040507@piuha.net>
Mime-version: 1.0
Content-type: text/plain;
charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 05 Feb 2007 18:40:54.0944 (UTC)
FILETIME=[2B374A00:01C74955]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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
On 2/5/07 10:42 AM, "ext Jari Arkko" <jari.arkko@piuha.net> wrote: > 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. FWIW, I completely agree. -Raj > > Jari > > > _______________________________________________ > 16NG mailing list > 16NG@ietf.org > https://www1.ietf.org/mailman/listinfo/16ng _______________________________________________ 16NG mailing list 16NG@ietf.org https://www1.ietf.org/mailman/listinfo/16ng
- [16NG] FW: Review of the ipv6-over-ipv6cs draft Jari Arkko
- Re: [16NG] FW: Review of the ipv6-over-ipv6cs dra… Jari Arkko
- Re: traffic classification (was: [16NG] FW: Revie… Alexandru Petrescu
- [16NG] Re: traffic classification Jari Arkko
- Re: [16NG] Re: traffic classification JinHyeock Choi
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification yw_chen
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- [16NG] Re: Review of the ipv6-over-ipv6cs draft Basavaraj Patil
- [16NG] Re: Review of the ipv6-over-ipv6cs draft Pekka Savola
- Re: [16NG] Re: traffic classification JinHyeock Choi
- [16NG] Re: Review of the ipv6-over-ipv6cs draft Basavaraj Patil
- [16NG] Re: Review of the ipv6-over-ipv6cs draft Pekka Savola
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: Review of the ipv6-over-ipv6cs dra… JinHyeock Choi
- DNA and using 3*MaxRtrAdvInterval [Re: [16NG] Re:… Pekka Savola
- [16NG] Re: Review of the ipv6-over-ipv6cs draft Basavaraj Patil
- Re: [16NG] Re: traffic classification JinHyeock Choi
- Re: DNA and using 3*MaxRtrAdvInterval [Re: [16NG]… JinHyeock Choi
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification Jari Arkko
- RE: [16NG] Re: traffic classification Riegel, Maximilian
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification Basavaraj Patil
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification Jari Arkko
- Re: [16NG] Re: traffic classification Alexandru Petrescu
- Re: [16NG] Re: traffic classification Basavaraj Patil
- Re: [16NG] Re: traffic classification Basavaraj Patil