Re: [16NG] Re: traffic classification
Alexandru Petrescu <alexandru.petrescu@motorola.com> Mon, 05 February 2007 09:33 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1HE0EN-0005pG-3V; Mon, 05 Feb 2007 04:33:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1HE0EL-0005pB-Le
for 16ng@ietf.org; Mon, 05 Feb 2007 04:33:45 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HE0EK-00088g-BN
for 16ng@ietf.org; Mon, 05 Feb 2007 04:33:45 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-2.tower-128.messagelabs.com!1170668022!1017575!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 9615 invoked from network); 5 Feb 2007 09:33:42 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
by server-2.tower-128.messagelabs.com with SMTP;
5 Feb 2007 09:33:42 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l159Xctt023898;
Mon, 5 Feb 2007 02:33:38 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id l159XXdJ018235;
Mon, 5 Feb 2007 03:33:35 -0600 (CST)
Message-ID: <45C6F9EB.6010007@motorola.com>
Date: Mon, 05 Feb 2007 10:33:31 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: "Riegel, Maximilian" <maximilian.riegel@siemens.com>
Subject: Re: [16NG] Re: traffic classification
References: <4BB931F00625F54DA8B8563E5A5CA25A01347220@MCHP7I6A.ww002.siemens.net>
In-Reply-To: <4BB931F00625F54DA8B8563E5A5CA25A01347220@MCHP7I6A.ww002.siemens.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
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
Riegel, Maximilian wrote: > The host is not aware of the CIDs. CIDs belong to the MAC layer, and > it is the task of the convergence sublayer as upper part of the MAC > layer to feed packets into CIDs according to filter rules. IEEE802.16 > provides its own syntax for setting up filter rules. This syntax > treats all header field the same way. Ok, I understand the principle. There are MAC filtering rules that match an IP packet to a CID. My question was about a specific value in Traffic Class field. > IEEE802.16 is done, Ah? This is something I'm not sure of. For example, a new corrigendum IEEE Std 802.16, Corrigendum 2 [Draft 2]) has been circulated among 802.16 members just a few days ago. (In my reading, there are some modifications that are relevant to the discussion around entry procedure, for example it now says that only for managed SSs the IP connectivity shall be performed over Secondary Management Connection; previously (802.16e-2005) it said that for any SS, not necessarily managed.) > but it may be worth to consider in the IETF the definition of a > generic way to specify filter rules for IP packets. The WiMAX Forum > NWG has adopted the filter rule syntax of DIAMETER. So far it looks > pretty sufficient. I think some monami6 WG drafts look at filtering rules, although not specific to particular link-layer (they're for filtering at HA and mobility). Alex _______________________________________________ 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