IETF Logo Mail Archive

Re: [16NG] Re: traffic classification

"JinHyeock Choi" <jinchoe@gmail.com> Sat, 03 February 2007 05:32 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HDDVz-0005dW-Rk; Sat, 03 Feb 2007 00:32:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HDDVx-0005dK-PO for 16ng@ietf.org; Sat, 03 Feb 2007 00:32:41 -0500
Received: from nf-out-0910.google.com ([64.233.182.187]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HDDVw-0000iF-Go for 16ng@ietf.org; Sat, 03 Feb 2007 00:32:41 -0500
Received: by nf-out-0910.google.com with SMTP id l36so1465796nfa for <16ng@ietf.org>; Fri, 02 Feb 2007 21:32:39 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=oL0WY40rjUV+SWQPeMLWMsYtgAvxwcGHxvh3ZbduNZ75CjUXjSDRgzeEksKI5MjBPOdSKPzvVF5tV9r8ohjc2A85ynK41JUixgGXUttS2j/syYHbJbNar7SRFBg8BcLmIT+dFDd6hX4Rm5tUFPKDcUUKKqJcxyc4LnGusGsHPfw=
Received: by 10.48.48.1 with SMTP id v1mr5874792nfv.1170480759683; Fri, 02 Feb 2007 21:32:39 -0800 (PST)
Received: by 10.48.217.6 with HTTP; Fri, 2 Feb 2007 21:32:39 -0800 (PST)
Message-ID: <92e919fb0702022132hc20a415k39ed496a111017f5@mail.gmail.com>
Date: Sat, 3 Feb 2007 14:32:39 +0900
From: "JinHyeock Choi" <jinchoe@gmail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Subject: Re: [16NG] Re: traffic classification
In-Reply-To: <45C30A7D.2050605@motorola.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 16ng@ietf.org, Pekka Savola <pekkas@netcore.fi>
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

Alex

> >> More specifically, what is the priority assigned to this service flow?
> >> ("traffic priority": sec 11.13.5 of 802.16-2004).  This encoding has
> >> values from 0 to 7 with higher numbers indicating higher priority.  If
> >> not the "traffic priority" value then what are the other service
> >> flow-specific constants that this IPv6 DSCP (diffserv codepoint)
> >> converts into.
> >
> > As of my knowledge, there is no rule to convert IPv6 DSCP (diffserv
> > codepoint) into 802.16 QoS parameter in a deterministic way. I
> > understand its up to the implementation & policy.
>
> Isn't this an interoperability issue? (between one's phone to one
> other's base station).

I can't think of any but which, I admit, doesn't guarantee there
exists none. :-)

Best Regards

JinHyeock

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

v2.8.7 | Report a Bug | By Email