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

"Jozef Babiarz" <babiarz@nortel.com> Tue, 23 October 2007 16:22 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 1IkMWN-0005RS-I3; Tue, 23 Oct 2007 12:22:23 -0400
Received: from pcn by megatron.ietf.org with local (Exim 4.43) id 1IkMWL-0005RG-RO for pcn-confirm+ok@megatron.ietf.org; Tue, 23 Oct 2007 12:22:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IkMWK-0005Q3-Oi for pcn@ietf.org; Tue, 23 Oct 2007 12:22:20 -0400
Received: from zcars04e.nortel.com ([47.129.242.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IkMWC-000087-IX for pcn@ietf.org; Tue, 23 Oct 2007 12:22:18 -0400
Received: from zcarhxm1.corp.nortel.com (zcarhxm1.corp.nortel.com [47.129.230.97]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id l9NGJ1716385; Tue, 23 Oct 2007 16:19:02 GMT
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: Tue, 23 Oct 2007 12:21:43 -0400
Message-ID: <9671A92C3C8B5744BC97F855F7CB646512C6F7D0@zcarhxm1.corp.nortel.com>
In-Reply-To: <1B6169C658325341A3B8066E23919E1C0DE8FD@S4DE8PSAANK.mitte.t-com.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PCN] Architecture draft - probing section & general updates.
Thread-Index: AcgQFh3bpdXKC6/iTqGKgTMqojS39gFKBadgABQhwRA=
References: <75A199C5D243C741BF3D3F1EBCEF9BA5019DC5CD@E03MVZ1-UKDY.domain1.systemhost.net> <1B6169C658325341A3B8066E23919E1C0DE8FD@S4DE8PSAANK.mitte.t-com.de>
From: Jozef Babiarz <babiarz@nortel.com>
To: "Geib, Ruediger" <Ruediger.Geib@t-systems.com>, philip.eardley@bt.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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

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