RE: [PCN] Architecture draft - probing section & general updates.

"Geib, Ruediger" <Ruediger.Geib@t-systems.com> Wed, 24 October 2007 07:03 UTC

Return-path: <pcn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkaHT-00053m-9g; Wed, 24 Oct 2007 03:03:55 -0400
Received: from pcn by megatron.ietf.org with local (Exim 4.43) id 1IkaHR-00053g-Qd for pcn-confirm+ok@megatron.ietf.org; Wed, 24 Oct 2007 03:03:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkaHN-0004tg-2k for pcn@ietf.org; Wed, 24 Oct 2007 03:03:49 -0400
Received: from tcmail31.telekom.de ([217.6.95.238]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkaHG-0000ni-MN for pcn@ietf.org; Wed, 24 Oct 2007 03:03:49 -0400
Received: from s4de8psaans.mitte.t-com.de by tcmail31.telekom.de with ESMTP; Wed, 24 Oct 2007 09:03:36 +0200
Received: from S4DE8PSAANK.mitte.t-com.de ([10.151.229.10]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Oct 2007 09:03:35 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PCN] Architecture draft - probing section & general updates.
Date: Wed, 24 Oct 2007 09:03:35 +0200
Message-Id: <1B6169C658325341A3B8066E23919E1C0DE91D@S4DE8PSAANK.mitte.t-com.de>
In-Reply-To: <9671A92C3C8B5744BC97F855F7CB646512C6F7D0@zcarhxm1.corp.nortel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PCN] Architecture draft - probing section & general updates.
thread-index: AcgQFh3bpdXKC6/iTqGKgTMqojS39gFKBadgABQhwRAAHsa+UA==
From: "Geib, Ruediger" <Ruediger.Geib@t-systems.com>
To: babiarz@nortel.com
X-OriginalArrivalTime: 24 Oct 2007 07:03:35.0897 (UTC) FILETIME=[FF041C90:01C8160B]
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: pcn@ietf.org
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
Errors-To: pcn-bounces@ietf.org

Joe,

my perception is, that probing may be useful, once there is 
pre-congestion. In a situation without a single admitted 
flow between an ingress and an egress, if neither ingress 
node nor egress node have any indication of pre-congestion 
on any of the links crossed by the PCN flows passing through 
them, there's with high probability no need to probe, 
I'd assume. I don't do simulations and would like to invite
those simulating to come up with cases where this assumption 
is wrong.

I'd further propose to collect information from providers 
on the probability of the event you describe. 

Regards, 

Rudiger

|-----Original Message-----
|From: Jozef Babiarz [mailto:babiarz@nortel.com]
|Sent: Tuesday, October 23, 2007 6:22 PM
|To: Geib, Rudiger; philip.eardley@bt.com
|Cc: pcn@ietf.org
|Subject: RE: [PCN] Architecture draft - probing section & general
|updates.
|
|
|Ruediger, the issue is not addition of one more flow into the link that
|is experiencing (pre-)congestion level for admission but potentially
|hundreds of new ingress-egress aggregates that have not been 
|established
|passing through the link. 
|
|Regards, Joe
|email:babiarz@nortel.com
|Telephone:613-763-6098
|
|-----Original Message-----
|From: Geib, Ruediger [mailto:Ruediger.Geib@t-systems.com] 
|Sent: October 23, 2007 4:19 AM
|To: philip.eardley@bt.com
|Cc: pcn@ietf.org
|Subject: RE: [PCN] Architecture draft - probing section & general
|updates.
|
|Phil,
|
|I appreciate that probing is optional. I understand that to mean that
|standardisation allows to operate PCN within a domain without having to
|support any probing functionality.
|
|There may be operational conditions, when probing makes sense. This may
|be the case, if the number of multiplexed flows is at the 
|lower bound of
|the range where statistical multiplexing can be applied on any link and
|the number of possible ingress to egress relations passing this link is
|big enough to lead to (pre-)congestion by admission of a single flow
|with a reasonable probability. I don't want to stop people from working
|on this issue, but I'd favour PCN to finish standards for an 
|operational
|environment where the probability of a single admitted flow causing
|congestion on a link is extremly low. 
|
|Regards,
|
|Rudiger
|
|
|_______________________________________________
|PCN mailing list
|PCN@ietf.org
|https://www1.ietf.org/mailman/listinfo/pcn
|


_______________________________________________
PCN mailing list
PCN@ietf.org
https://www1.ietf.org/mailman/listinfo/pcn