Re: [conex] Draft "Pre-congestion notification in mobile networks"
STUART VENTERS <stuart.venters@adtran.com> Mon, 12 March 2012 15:59 UTC
Return-Path: <stuart.venters@adtran.com>
X-Original-To: conex@ietfa.amsl.com
Delivered-To: conex@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D85EF21E801E for <conex@ietfa.amsl.com>; Mon, 12 Mar 2012 08:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7rnsELDBA2eH for <conex@ietfa.amsl.com>; Mon, 12 Mar 2012 08:59:27 -0700 (PDT)
Received: from p02c12o147.mxlogic.net (p02c12o147.mxlogic.net [208.65.145.80]) by ietfa.amsl.com (Postfix) with ESMTP id 25DDB11E8075 for <conex@ietf.org>; Mon, 12 Mar 2012 08:59:25 -0700 (PDT)
Received: from unknown [76.164.174.83] (EHLO p02c12o147.mxlogic.net) by p02c12o147.mxlogic.net(mxl_mta-6.13.0-2) with ESMTP id e5d1e5f4.656e3940.86651.00-548.211849.p02c12o147.mxlogic.net (envelope-from <stuart.venters@adtran.com>); Mon, 12 Mar 2012 09:59:26 -0600 (MDT)
X-MXL-Hash: 4f5e1d5e5a616668-def9e2790c277100e49d98064afcd0182a9b4a18
Received: from unknown [76.164.174.83] by p02c12o147.mxlogic.net(mxl_mta-6.13.0-2) with SMTP id 55d1e5f4.0.86604.00-330.211674.p02c12o147.mxlogic.net (envelope-from <stuart.venters@adtran.com>); Mon, 12 Mar 2012 09:59:19 -0600 (MDT)
X-MXL-Hash: 4f5e1d57043402d1-d3852fdf4080375c001a214bdbbb75ec0efc1164
Received: from ex-mb1.corp.adtran.com ([fe80::51a3:972d:5f16:9952]) by ex-hc2.corp.adtran.com ([fe80::d50f:ceda:4e38:ebf0%15]) with mapi id 14.01.0339.001; Mon, 12 Mar 2012 10:59:40 -0500
From: STUART VENTERS <stuart.venters@adtran.com>
To: "sebastien.jobert@orange.com" <sebastien.jobert@orange.com>
Thread-Topic: Draft "Pre-congestion notification in mobile networks"
Thread-Index: Acz9jrbRNPBod6S3QWSO/G4dZZpM1QC2Qa8Q
Date: Mon, 12 Mar 2012 15:59:40 +0000
Message-ID: <1220E2C537595D439C5D026E83751866220398FC@ex-mb1.corp.adtran.com>
References: <AFC377AFCC0FBD4DABE49F4B81EC4F1A03520051@ftrdmel1>
In-Reply-To: <AFC377AFCC0FBD4DABE49F4B81EC4F1A03520051@ftrdmel1>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.22.113.98]
Content-Type: multipart/alternative; boundary="_000_1220E2C537595D439C5D026E83751866220398FCexmb1corpadtran_"
MIME-Version: 1.0
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <stuart.venters@adtran.com>
X-SOURCE-IP: [76.164.174.83]
X-AnalysisOut: [v=1.0 c=1 a=ruWq0YzyRmIA:10 a=qZE7q64NgjsA:10 a=qZHQZMT3ap]
X-AnalysisOut: [YA:10 a=BLceEmwcHowA:10 a=xqWC_Br6kY4A:10 a=5zDNsY1we+1mvV]
X-AnalysisOut: [cp/5+1jQ==:17 a=48vgC7mUAAAA:8 a=z9tbli-vAAAA:8 a=jO2692MM]
X-AnalysisOut: [AAAA:8 a=_r_i8vQ192Ogds36LjUA:9 a=eCQlZ5lrrOeqQI8_LMUA:7 a]
X-AnalysisOut: [=wPNLvfGTeEIA:10 a=lZB815dzVvQA:10 a=oAXR_kdF8uMA:10 a=cPi]
X-AnalysisOut: [Qg-nXjNYA:10 a=qO5-93tIaei6J40F:21 a=Ny3ohJtp7xYIOw76:21 a]
X-AnalysisOut: [=SSmOFEACAAAA:8 a=yMhMjlubAAAA:8 a=8AYmYBJub6LVdLqT1JIA:9 ]
X-AnalysisOut: [a=VcQpiWaILO6tJEF1yMQA:7 a=gKO2Hq4RSVkA:10 a=_W_S_7VecoQA:]
X-AnalysisOut: [10 a=gMsgoVrhTLqk6YWP:21 a=9nthCi0HMFfofmHi:21]
Cc: "conex@ietf.org" <conex@ietf.org>
Subject: Re: [conex] Draft "Pre-congestion notification in mobile networks"
X-BeenThere: conex@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Congestion Exposure working group discussion list <conex.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/conex>, <mailto:conex-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/conex>
List-Post: <mailto:conex@ietf.org>
List-Help: <mailto:conex-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/conex>, <mailto:conex-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2012 15:59:30 -0000
Sebastien, You bring up an interesting point about fairness in a wireless network. Since the radio path quality may be different from handset to handset, the amount of radio resources required to transport a given number of bits may also be different. To be fair, should each handset get the same number of bits or the same number of radio resources? (Or, more likely, as you suggest in section 6, a combination of the two.) This seems as much a marketing issue as a technical one, so I would expect each carrier to want to be able to choose the cost function combining these two factors. I agree with you that just counting the bytes is not enough. Cheers, Stuart ________________________________ From: conex-bounces@ietf.org [mailto:conex-bounces@ietf.org] On Behalf Of sebastien.jobert@orange.com Sent: Thursday, March 08, 2012 6:51 PM To: conex@ietf.org Cc: isabelle.hamchaoui@orange.com Subject: [conex] Draft "Pre-congestion notification in mobile networks" Hi all, We have uploaded an Internet-Draft called "Pre-congestion notification in mobile networks" - http://www.ietf.org/id/draft-jobert-tsvwg-pre-congest-notif-mobile-00.pdf Abstract Mobile networks may be divided into two main segments: the radio segment, and the wireline segment. This document highlights that the algorithms leading to pre-congestion notification (e.g. ECN marking) are usually significantly different for these two segments, and not defined or documented in general over the radio segment. It also explains that using ECN bits leads to having a unique signal for notifying a pre-congestion related to two separate segments with very different notification algorithms. Some consequences are questioned, as well as the potential benefits of being able to identify where the congestion comes from. This document finally discusses the possibility to take into account the radio conditions of the terminals when counting the volume of congestion over the radio segment. It has been posted in TSVWG, but some aspects discussed in this draft are related to discussions in CONEX, and might be of interest to the WG. We are interested by review and comments. Thanks. Best Regards, Sébastien JOBERT Orange Expert, network synchronization and QoS in mobile networks Orange Labs, Networks & Carriers - France Telecom Orange sebastien.jobert@orange.com<mailto:sebastien.jobert@orange-ftgroup.com>
- [conex] Draft "Pre-congestion notification in mob… sebastien.jobert
- Re: [conex] Draft "Pre-congestion notification in… STUART VENTERS
- Re: [conex] Draft "Pre-congestion notification in… sebastien.jobert