Re: [PCN] new version LC-PCN draft + conclusions

"Georgios Karagiannis" <karagian@cs.utwente.nl> Wed, 19 November 2008 10:27 UTC

Return-Path: <pcn-bounces@ietf.org>
X-Original-To: pcn-archive@optimus.ietf.org
Delivered-To: ietfarch-pcn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 770CF3A684B; Wed, 19 Nov 2008 02:27:13 -0800 (PST)
X-Original-To: pcn@core3.amsl.com
Delivered-To: pcn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F64F3A684B for <pcn@core3.amsl.com>; Wed, 19 Nov 2008 02:27:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level:
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yKmvlfuzfTPn for <pcn@core3.amsl.com>; Wed, 19 Nov 2008 02:27:11 -0800 (PST)
Received: from rotterdam.ewi.utwente.nl (rotterdam.ewi.utwente.nl [130.89.10.5]) by core3.amsl.com (Postfix) with ESMTP id F25A23A67B2 for <pcn@ietf.org>; Wed, 19 Nov 2008 02:27:10 -0800 (PST)
Received: from ewi977 (ewi977.ewi.utwente.nl [130.89.12.129]) by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id mAJAR5MU009239; Wed, 19 Nov 2008 11:27:08 +0100 (MET)
From: Georgios Karagiannis <karagian@cs.utwente.nl>
To: philip.eardley@bt.com, pcn@ietf.org
References: <4A916DBC72536E419A0BD955EDECEDEC04440E9F@E03MVB1-UKBR.domain1.systemhost.net> <4A916DBC72536E419A0BD955EDECEDEC04440EA0@E03MVB1-UKBR.domain1.systemhost.net>
Date: Wed, 19 Nov 2008 11:27:00 +0100
Message-ID: <001801c94a31$5e857fb0$810c5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <4A916DBC72536E419A0BD955EDECEDEC04440EA0@E03MVB1-UKBR.domain1.systemhost.net>
Thread-Index: AclJ65CRaBa70dnERw+ExM7HzdY3iAAAAnd1ABE6r1A=
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (rotterdam.ewi.utwente.nl [130.89.10.5]); Wed, 19 Nov 2008 11:27:09 +0100 (MET)
Subject: Re: [PCN] new version LC-PCN draft + conclusions
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/pcn>
List-Post: <mailto:pcn@ietf.org>
List-Help: <mailto:pcn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>, <mailto:pcn-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pcn-bounces@ietf.org
Errors-To: pcn-bounces@ietf.org

Hi Phil

My argument was that doing the "1/N" at the PCN-boundary-node instead of the

PCN-interior-node is not good enough!

However, I would like to propose the following:

* Work-out the option of doing 1/N at the PCN-boundary-node. 
* If this option is not good enough to satisfy the requirements for a PCN
deployment scenario like LC-PCN, 
   then allow to work out an experimental specification that can use the 1/N
proportionality 
  at PCN_interior_nodes.

Best regards,
Georgios


> -----Original Message-----
> From: philip.eardley@bt.com [mailto:philip.eardley@bt.com] 
> Sent: woensdag 19 november 2008 3:16
> To: pcn@ietf.org; karagian@cs.utwente.nl
> Subject: RE: [PCN] new version LC-PCN draft + conclusions
> 
> HI Georgios
> response to your third point below.
>  
> this has already been discussed extensively on the mailing 
> list. there seems no benefit to this, because the same system 
> behaviour can be achieved by doing "1/N" behaviour at the 
> PCN-boundary-node instead of at the PCN-interior-node.
>  
> pointers to previous discussion:
> http://www.ietf.org/mail-archive/web/pcn/current/msg01642.html
> http://www.ietf.org/mail-archive/web/pcn/current/msg01091.html
> https://datatracker.ietf.org/drafts/draft-menth-pcn-emft/
>  
> so i am strongly opposed to including this option in the 
> markng draft. 
>  
> phil
>  
> ----------------------------
> *	Subject: [PCN] new version LC-PCN draft + conclusions 
> *	From: "Georgios Karagiannis" <karagian at cs.utwente.nl 
> <mailto:karagian@DOMAIN.HIDDEN> > 
> *	Date: Tue, 11 Nov 2008 17:16:05 +0000 
>  
> Dear all
> 
> Please note that a new version of the LC-PCN draft has been submitted,
> see:
> 
> http://www.ietf.org/internet-drafts/draft-westberg-pcn-load-co
ntrol-05.txt
> 
> This version contains among other results also the results 
> that were presented during the IETF in Dublin.
> 
> Section 5.8 contains the following experiment conclusions.
> 
>    Based on the results obtained from the experiments presented in
>    Sections 5.5, 5.6 and 5.7 this document recommends the following:
> 
>    o  Leave open the option to use PCN_Affected_Marking encoding since
>       it can solve the ECMP problem and it can provide an efficient
>       solution for the HOSE model.  In this document the term HOSE is
>       referring to the aggregation of incoming traffic from 
> all ingress
>       edges, which is associated with one traffic class, i.e., PHB,
>       towards one egress edge.  This type of HOSE model is 
> equivalent to
>       the Multiple to Point (MP2P) type of aggregation.
> 
>    o  Leave open the option of using random dropping in PCN-interior-
>       nodes for PCN_Marking, PCN_Affected_Marking and PCN_unmarked
>       encoded packets.
> 
>    o  Leave open the option of using the parameter N such that the
>       marked excess rate can represent also high level of measured
>       excess rate:
> 
>    **** Implemented by marking every N-th packet (or byte) instead of
>    marking each packet (or byte).
> 
> Best regards,
> Georgios
> 


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