RE: [PCN] Architecture draft - probing section & general updates.
"Jozef Babiarz" <babiarz@nortel.com> Mon, 29 October 2007 21:05 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 1Imbo5-00077g-UX; Mon, 29 Oct 2007 17:05:57 -0400
Received: from pcn by megatron.ietf.org with local (Exim 4.43) id 1Imbo5-00076t-61 for pcn-confirm+ok@megatron.ietf.org; Mon, 29 Oct 2007 17:05:57 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Imbo4-00076j-Qd for pcn@ietf.org; Mon, 29 Oct 2007 17:05:56 -0400
Received: from zrtps0kp.nortel.com ([47.140.192.56]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Imbo4-0007q2-Cm for pcn@ietf.org; Mon, 29 Oct 2007 17:05:56 -0400
Received: from zcarhxm1.corp.nortel.com (zcarhxm1.corp.nortel.com [47.129.230.97]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l9TL5fI21333; Mon, 29 Oct 2007 21:05:41 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: Mon, 29 Oct 2007 17:05:36 -0400
Message-ID: <9671A92C3C8B5744BC97F855F7CB646512DFE32B@zcarhxm1.corp.nortel.com>
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: AcgW7SC2PEVcOi1+Qg+vZ1UxgSPGoQDfIixA
References: <9671A92C3C8B5744BC97F855F7CB646512C6F7D0@zcarhxm1.corp.nortel.com> <1B6169C658325341A3B8066E23919E1C0DE91D@S4DE8PSAANK.mitte.t-com.de> <9671A92C3C8B5744BC97F855F7CB646512CCCEE0@zcarhxm1.corp.nortel.com> <9EE2BE22-5E19-4625-B368-3A603728ED52@nokia.com>
From: Jozef Babiarz <babiarz@nortel.com>
To: Lars Eggert <lars.eggert@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: pcn@ietf.org, "Geib, Ruediger" <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
Hi Lars, I did not explain my scenario that clearly, I confused people the word "access node". So here goes a second try. 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 (branch offices). PCN is run inside the enterprise network including WAN links which may be tunneled across the carrier network. Carrier network is not required to support PCN as the enterprise traffic including PCN marking is tunneled, however it could. Network Access Control with PCN admission control is done at the *enterprise* LAN edge switch/router. New flows can be routed to any egress LAN edge switch/router and some flows will (between different locations) be routed over one of the WAN links which are normally bandwidth constrained. There is a high probability that many of the edge LAN switches/routers will have no flows setup between each other (no ingress-egress aggregate) as there are a large number of edge LAN switches/routers in the enterprise network and people calling patterns change. They normal expect that they should be able to call anyone. Regards, Joe email:babiarz@nortel.com Telephone:613-763-6098 -----Original Message----- From: Lars Eggert [mailto:lars.eggert@nokia.com] Sent: October 25, 2007 5:54 AM To: Babiarz, Jozef (CAR:0S03) Cc: Geib, Ruediger; pcn@ietf.org 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
- [PCN] Architecture draft - probing section & gene… philip.eardley
- RE: [PCN] Architecture draft - probing section & … Hancock, Robert
- Re: [PCN] Architecture draft - probing section & … Michael Menth
- RE: [PCN] Architecture draft - probing section & … Anna Charny (acharny)
- Re: [PCN] Architecture draft - probing section & … Lars Eggert
- RE: [PCN] Architecture draft - probing section & … Anna Charny (acharny)
- Re: [PCN] Architecture draft - probing section & … Lars Eggert
- RE: [PCN] Architecture draft - probing section & … Anna Charny (acharny)
- RE: [PCN] Architecture draft - probing section & … Geib, Ruediger
- RE: [PCN] Architecture draft - probing section & … Geib, Ruediger
- RE: [PCN] Architecture draft - probing section & … Anna Charny (acharny)
- RE: [PCN] Architecture draft - probing section & … Geib, Ruediger
- Re: [PCN] Architecture draft - probing section & … Lars Eggert
- RE: [PCN] Architecture draft - probing section & … Jozef Babiarz
- RE: [PCN] Architecture draft - probing section & … Geib, Ruediger
- RE: [PCN] Architecture draft - probing section & … Anna Charny (acharny)
- RE: [PCN] Architecture draft - probing section & … Geib, Ruediger
- RE: [PCN] Architecture draft - probing section & … Anna Charny (acharny)
- RE: [PCN] Architecture draft - probing section & … Jozef Babiarz
- RE: [PCN] Architecture draft - probing section & … Geib, Ruediger
- RE: [PCN] Architecture draft - probing section & … Geib, Ruediger
- RE: [PCN] Architecture draft - probing section & … Geib, Ruediger
- Re: [PCN] Architecture draft - probing section & … Lars Eggert
- RE: [PCN] Architecture draft - probing section & … philip.eardley
- Re: [PCN] Architecture draft - probing section & … Lars Eggert
- RE: [PCN] Architecture draft - probing section & … Jozef Babiarz
- RE: [PCN] Architecture draft - probing section & … Jozef Babiarz
- RE: [PCN] Architecture draft - probing section & … Geib, Ruediger
- RE: [PCN] Architecture draft - probing section & … philip.eardley
- RE: [PCN] Architecture draft - probing section & … Jozef Babiarz
- Re: [PCN] Architecture draft - probing section & … philip.eardley
- Re: [PCN] Architecture draft - probing section & … Jozef Babiarz