RE: [PCN] comments on draft-ietf-pcn-architecture-02

<philip.eardley@bt.com> Thu, 22 November 2007 12:38 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 1IvBKP-0006BF-1x; Thu, 22 Nov 2007 07:38:45 -0500
Received: from pcn by megatron.ietf.org with local (Exim 4.43) id 1IvBKN-00060Y-DM for pcn-confirm+ok@megatron.ietf.org; Thu, 22 Nov 2007 07:38:43 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvBKM-0005xy-W0 for pcn@ietf.org; Thu, 22 Nov 2007 07:38:43 -0500
Received: from smtp1.smtp.bt.com ([217.32.164.137]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IvBKM-0004z6-Gt for pcn@ietf.org; Thu, 22 Nov 2007 07:38:42 -0500
Received: from E03MVZ1-UKDY.domain1.systemhost.net ([193.113.30.65]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Nov 2007 12:38:41 +0000
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] comments on draft-ietf-pcn-architecture-02
Date: Thu, 22 Nov 2007 12:38:40 -0000
Message-ID: <75A199C5D243C741BF3D3F1EBCEF9BA503B3439B@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <000001c82d03$5a4a4df0$4c0d5982@dynamic.ewi.utwente.nl>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PCN] comments on draft-ietf-pcn-architecture-02
Thread-Index: Acgs0ibapJhVEKTeSKaERK5iVAsa7AAHKj+AAAT0iCAAAEJfEA==
From: philip.eardley@bt.com
To: karagian@cs.utwente.nl, pcn@ietf.org
X-OriginalArrivalTime: 22 Nov 2007 12:38:41.0294 (UTC) FILETIME=[9CBEFAE0:01C82D04]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc:
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


> -----Original Message-----
> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> Sent: 22 November 2007 12:29
> To: Eardley,PL,Philip,CXR9 R; pcn@ietf.org
> Subject: RE: [PCN] comments on draft-ietf-pcn-architecture-02
> 
> Hi Phil
> 
> Thank you!
> Please see comments regarding comment_3:
> 
> > > Comment_3:
> > > In Section 3, page 29, you provide the below conclusion on the
> > viewpoint
> > > that admission control is always done by probing:
> > >
> > > "The first point breaks Assumption 3 (aggregation) and hence means
> > that
> > > this viewpoint is out of scope of initial Charter of the PCN WG."
> > >
> > > I do not agree with this conclusion, since I do not agree with the
> > > argumentation that the first point breaks Assumption 3
> >
> > the "first point" is this:
> > o  Simply admitting the new flow has a significant risk of leading
to
> >       overload, because the PCN-domain reaches out towards the end
> >       terminals where link capacity is low.
> > The link capacity is low means that adding a single flow to
> > the link can move it directly from no congestion to
> > overloaded [real queue grows significantly or overflows].
> > This breaks the aggregation assumption.
> 
> Georgios: yes, But if the link capacity is low and the admission
> threshold/rate in an PCN-interior node
> is high (by configuration), how then a single flow can move the state
in
> the
> PCN_interior_node from
> no congestion to congestion? This means that the admission
threshold/rate
> should be doen properly such
> that such a situation will not occur!
> 
after a bit of puzzling...
I was talking about the situation where the low capacity link is inside
the PCN-domain. I think your situation is different, where there's an
access network not running PCN, and the low capacity link is in the
access nw.
Is this right?

If yes, I'd say that how you do admission control in the access nw
(which isn't running PCN) is not a concern of PCN. if you want to always
do 'adm ctrl by probing' in the access nw, that's fine. presumably when
the PCN-boundary-nodes sees one of these probes then it's triggered to
do some PCN adm ctrl activity.


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