Re: [16NG] Re: traffic classification
Tim Enos <timbeck04@verizon.net> Mon, 05 February 2007 21:05 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1HEB1u-0007ye-9S; Mon, 05 Feb 2007 16:05:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1HEB1t-0007yY-Lw
for 16ng@ietf.org; Mon, 05 Feb 2007 16:05:37 -0500
Received: from vms046pub.verizon.net ([206.46.252.46])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HEB1r-0000vH-Vf
for 16ng@ietf.org; Mon, 05 Feb 2007 16:05:37 -0500
Received: from vms073.mailsrvcs.net ([192.168.1.2])
by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
(built Apr
3 2006)) with ESMTPA id <0JD0009A2D9BHS31@vms046.mailsrvcs.net> for
16ng@ietf.org; Mon, 05 Feb 2007 15:05:35 -0600 (CST)
Received: from 129.55.200.20 ([129.55.200.20])
by vms073.mailsrvcs.net (Verizon Webmail) with HTTP; Mon,
05 Feb 2007 15:05:35 -0600 (CST)
Date: Mon, 05 Feb 2007 15:05:35 -0600 (CST)
From: Tim Enos <timbeck04@verizon.net>
Subject: Re: [16NG] Re: traffic classification
X-Originating-IP: [129.55.200.20]
To: Jari Arkko <jari.arkko@piuha.net>,
Alexandru Petrescu <alexandru.petrescu@motorola.com>
Message-id: <19174063.3261241170709535305.JavaMail.root@vms073.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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
Hi all, >From: Jari Arkko <jari.arkko@piuha.net> >Date: 2007/02/05 Mon AM 10:42:22 CST >To: Alexandru Petrescu <alexandru.petrescu@motorola.com> >Cc: 16ng@ietf.org >Subject: Re: [16NG] Re: traffic classification >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. It seems that how to perform an automatic mapping (of an IPv6 Traffic Class value to a particular scheduling service) would be beyond the scope of the IEEE 802.16 standard. The text from which I derive that impression is in 6.3.14.7 which states in part: "The provisioning of service flows is done via means outside the scope of this standard, such as the network managment system." Not sure, but I'd figure we'd not try to define such an automatic mapping (in this draft at least). As an aside, it seems to me that traffic which would at the network layer be marked with Traffic Class EF (RFC 2598) (e.g. VoIP) could likely be traffic that would also be provisioned with a UGS service flow (6.3.5.2.1). In terms of priority, it seems the only scheduling service that requires the Traffic Priority QoS parameter (11.13.5) is nrtPS (6.3.5). Respectfully, Tim Enos Rom 8:28 > >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