Re: [16NG] traffic flow mapping

Alexandru Petrescu <alexandru.petrescu@gmail.com> Fri, 09 March 2007 10:00 UTC

Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPbu5-00060d-3d; Fri, 09 Mar 2007 05:00:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPbu3-00060P-7m for 16ng@ietf.org; Fri, 09 Mar 2007 05:00:47 -0500
Received: from mail128.messagelabs.com ([216.82.250.131]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HPbu1-0002a8-U9 for 16ng@ietf.org; Fri, 09 Mar 2007 05:00:47 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-15.tower-128.messagelabs.com!1173434444!3963509!1
X-StarScan-Version: 5.5.10.7.1; banners=.,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 16071 invoked from network); 9 Mar 2007 10:00:44 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103) by server-15.tower-128.messagelabs.com with SMTP; 9 Mar 2007 10:00:44 -0000
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231]) by motgate3.mot.com (8.12.11/Motorola) with ESMTP id l29A0ipR008360; Fri, 9 Mar 2007 03:00:44 -0700 (MST)
Received: from az10vts03 (az10vts03.mot.com [10.64.251.244]) by az33exr01.mot.com (8.13.1/Vontu) with SMTP id l29A0hn0012776; Fri, 9 Mar 2007 04:00:44 -0600 (CST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117]) by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id l29A0g8O012682; Fri, 9 Mar 2007 04:00:42 -0600 (CST)
Message-ID: <45F13043.8090303@gmail.com>
Date: Fri, 09 Mar 2007 11:00:35 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: vasanth varathan varathan <vasanth.varathan@gmail.com>
Subject: Re: [16NG] traffic flow mapping
References: <595262710703080040j4319c7dbl35592c142641213d@mail.gmail.com>
In-Reply-To: <595262710703080040j4319c7dbl35592c142641213d@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Vontu: Pass
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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

vasanth varathan varathan wrote:
> Hi all,
> 
> I have a doubts in mapping Qos paramater to DSA-REQ frame While the 
> MSS sends DSA-REQ message to obtain a new connection, how the Service
>  flow encoding (like Traffic priority, Max sustained rate, Min 
> reserved rate, Max Latency, etc..) are mapped from the above layers 
> into the MAC CS layer??? if I get some feedback it will be gud.

HEre's good feedback.

It has been proposed in the past, as mailing list discussion, not draft,
to have a meaningful means to map the values of the IPv6 Traffic Class
field (the 6bit DSCP) into the 5(?) services of 802.16.

The proposal was rejected.  There were public reasons for that and also
SDO dependencies which are less clear at least to myself.

I still think it is a good idea and very necessary, but am waiting that
new opportunities arise for this idea.  Hence this mail :-)

In what context do you need this mapping?  Is it for an exploratory
project?  Is it for an innovative differentiator in a new product?  For
a small prototype?  For liaising to another Standards Body?

Alex


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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