Return-Path: <sebastien.jobert@orange.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 CD9D821F85A7 for <conex@ietfa.amsl.com>;
 Thu,  8 Mar 2012 16:51:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.971
X-Spam-Level: 
X-Spam-Status: No, score=-5.971 tagged_above=-999 required=5 tests=[AWL=0.277,
 BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 YfUD3u3eF4UC for
 <conex@ietfa.amsl.com>; Thu,  8 Mar 2012 16:51:13 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com
 [217.108.152.42]) by ietfa.amsl.com (Postfix) with ESMTP id DCECD21F85A5 for
 <conex@ietf.org>; Thu,  8 Mar 2012 16:51:09 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain
 [127.0.0.1]) by localhost (Postfix) with SMTP id DC9BE5D893F for
 <conex@ietf.org>; Fri,  9 Mar 2012 01:51:08 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by
 r-mail2.rd.francetelecom.com (Postfix) with ESMTP id D09F05D8937 for
 <conex@ietf.org>; Fri,  9 Mar 2012 01:51:08 +0100 (CET)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by
 ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);
 Fri, 9 Mar 2012 01:51:08 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----_=_NextPart_001_01CCFD8E.B6FB6411"
Date: Fri, 9 Mar 2012 01:51:08 +0100
Message-ID: <AFC377AFCC0FBD4DABE49F4B81EC4F1A03520051@ftrdmel1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Draft "Pre-congestion notification in mobile networks"
Thread-Index: Acz9jrbRNPBod6S3QWSO/G4dZZpM1Q==
From: <sebastien.jobert@orange.com>
To: <conex@ietf.org>
X-OriginalArrivalTime: 09 Mar 2012 00:51:08.0736 (UTC)
 FILETIME=[B72E7400:01CCFD8E]
Cc: isabelle.hamchaoui@orange.com
Subject: [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: Fri, 09 Mar 2012 00:51:19 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCFD8E.B6FB6411
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

=20

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=


=20

Abstract

=20

   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.

=20

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.

=20

Thanks.

=20

Best Regards,

=20

S=E9bastien 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> =
=20

=20

=20


------_=_NextPart_001_01CCFD8E.B6FB6411
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DFR link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>Hi all,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>We have uploaded an Internet-Draft called =
&#8220;Pre-congestion notification in mobile networks&#8221; - <a =
href=3D"http://www.ietf.org/id/draft-jobert-tsvwg-pre-congest-notif-mobil=
e-00.pdf">http://www.ietf.org/id/draft-jobert-tsvwg-pre-congest-notif-mob=
ile-00.pdf</a><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Abstract<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; Mobile networks may be divided into two main =
segments: the radio<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; segment, and the wireline segment. This document =
highlights that the<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; algorithms leading to pre-congestion notification =
(e.g. ECN marking)<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; are usually significantly different for these two =
segments, and not<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; defined or documented in general over the radio =
segment. It also<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; explains that using ECN bits leads to having a unique =
signal for<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
notifying a pre-congestion related to two separate segments =
with<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; very =
different notification algorithms. Some consequences =
are<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
questioned, as well as the potential benefits of being able =
to<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
identify where the congestion comes from. This document =
finally<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
discusses the possibility to take into account the radio =
conditions<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; of the =
terminals when counting the volume of congestion over =
the<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; radio =
segment.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>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.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>We are interested by review and =
comments.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Thanks.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New"'>Best =
Regards,</span><span lang=3DEN-US><o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><b><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>S=E9bastien =
JOBERT</span></b><span lang=3DEN-US><br></span><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Orange =
Expert, network synchronization and QoS in mobile =
networks<br></span><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#F5801F'=
>Orange Labs, Networks &amp; Carriers - France Telecom =
Orange</span></b><span lang=3DEN-US><br><span style=3D'color:#E36C0A'><a =
href=3D"mailto:sebastien.jobert@orange-ftgroup.com"><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#E36C0A'=
>sebastien.jobert@orange.com</span></a></span> <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------_=_NextPart_001_01CCFD8E.B6FB6411--
