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

<philip.eardley@bt.com> Thu, 25 October 2007 10:56 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 1Il0OI-0007yu-5R; Thu, 25 Oct 2007 06:56:42 -0400
Received: from pcn by megatron.ietf.org with local (Exim 4.43) id 1Il0OH-0007yp-94 for pcn-confirm+ok@megatron.ietf.org; Thu, 25 Oct 2007 06:56:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Il0OG-0007yg-Ua for pcn@ietf.org; Thu, 25 Oct 2007 06:56:40 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Il0OG-000312-HC for pcn@ietf.org; Thu, 25 Oct 2007 06:56:40 -0400
Received: from E03MVZ1-UKDY.domain1.systemhost.net ([193.113.30.63]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 25 Oct 2007 11:56:39 +0100
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: Thu, 25 Oct 2007 11:56:38 +0100
Message-ID: <75A199C5D243C741BF3D3F1EBCEF9BA5019DC5FC@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <9EE2BE22-5E19-4625-B368-3A603728ED52@nokia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PCN] Architecture draft - probing section & general updates.
Thread-Index: AcgW7Vwus3tUSdCIRHq1ll0tgHrrfwAB8PQw
From: philip.eardley@bt.com
To: lars.eggert@nokia.com, babiarz@nortel.com
X-OriginalArrivalTime: 25 Oct 2007 10:56:39.0619 (UTC) FILETIME=[B8608130:01C816F5]
X-Spam-Score: -1.0 (-)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: pcn@ietf.org, Ruediger.Geib@t-systems.com
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

Lars, I believe the guess is that there'll be many ingress-egress pairs
with none or very few flows at a particular moment. Not a random
distribution of calls onto all possible pairs. Basically there are many
calls between London & Manchester and very few between truro and
Shetland. I & Ben will try and extract some numbers from the [bt]
predicted future traffic matrix.

-----Original Message-----
From: Lars Eggert [mailto:lars.eggert@nokia.com] 
Sent: 25 October 2007 10:54
To: ext Jozef Babiarz
Cc: pcn@ietf.org; Geib, Ruediger
Subject: Re: [PCN] Architecture draft - probing section & general
updates.

On 2007-10-24, at 19:14, ext Jozef Babiarz wrote:
> I'm thinking of a scenario that many enterprises face today. Large  
> multi
> location enterprises use multiple WAN links or VPS to interconnect  
> their
> locations. PCN is run inside the enterprise network including WAN  
> links
> which maybe tunneled across the carrier network. Network Access  
> Control
> with PCN admission control is done at the enterprise access edge  
> nodes.
> New flows can be routed to any egress access edge node and some flows
> will (between different locations) be routed over one of the WAN links
> which are normally bandwidth constrained.

I understand your scenario so far.

> There is a high probability
> that many access nodes will only have one flow between each other as
> there are a large number of them.

I don't see how this follows, however. It seems that if the sites  
that are being interconnected aren't tiny, there should very likely  
be multiple flows per ingress/egress pair, no?

Lars


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