Re: [PCN] affected marking (or router marking) discussion in pcn architecture draft

<philip.eardley@bt.com> Mon, 04 February 2008 13:01 UTC

Return-Path: <pcn-bounces@ietf.org>
X-Original-To: ietfarch-pcn-archive@core3.amsl.com
Delivered-To: ietfarch-pcn-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 529153A6EF7; Mon, 4 Feb 2008 05:01:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S-IvgGy-JSHB; Mon, 4 Feb 2008 05:01:34 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 768703A6E88; Mon, 4 Feb 2008 05:01:34 -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 DB3FC3A6E86 for <pcn@core3.amsl.com>; Mon, 4 Feb 2008 05:01:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d96nXoV3ps6t for <pcn@core3.amsl.com>; Mon, 4 Feb 2008 05:01:31 -0800 (PST)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by core3.amsl.com (Postfix) with ESMTP id 1F4113A6E75 for <pcn@ietf.org>; Mon, 4 Feb 2008 05:01:30 -0800 (PST)
Received: from E03MVZ1-UKDY.domain1.systemhost.net ([193.113.30.62]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 4 Feb 2008 13:03:03 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 04 Feb 2008 13:03:02 -0000
Message-ID: <75A199C5D243C741BF3D3F1EBCEF9BA503B3452A@E03MVZ1-UKDY.domain1.systemhost.net>
In-Reply-To: <000d01c864bb$2ad17090$810c5982@dynamic.ewi.utwente.nl>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: affected marking (or router marking) discussion in pcn architecture draft
Thread-Index: AchkuyfW/SRYnB5hTKGGPg1stQU2DwCcmSVg
From: philip.eardley@bt.com
To: karagian@cs.utwente.nl
X-OriginalArrivalTime: 04 Feb 2008 13:03:03.0582 (UTC) FILETIME=[46E7EBE0:01C8672E]
Cc: pcn@ietf.org
Subject: Re: [PCN] affected marking (or router marking) discussion in pcn architecture draft
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <http://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: <http://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 Georgios

Please note the following text in S6

<
The following are open issues.  They are mainly taken from
   [I-D.briscoe-tsvwg-cl-architecture] which also describes some
   possible solutions.  Note that some may be considered unimportant in
   general or in specific deployment scenarios or by some operators.

   NOTE: Potential solutions are out of scope for this document.
>

So I don't think it's right to include your statement below, as it's in
solution space.

As a side note, I think I remember that affected marking is done when an
interface is 'admission marking' pkts (rather than when an interface is
'termination marking pkts). In that case, affected marking tackles the
ecmp issue for flow admission (rather than for flow termination). 

phil

> -----Original Message-----
> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]
> Sent: 01 February 2008 10:14
> To: Eardley,PL,Philip,CXR9 R
> Cc: pcn@ietf.org
> Subject: affected marking (or router marking) discussion in pcn
> architecture draft
> 
> Hi Phil
> 
> As mentioned in
>
http://www.watersprings.org/pub/id/draft-briscoe-tsvwg-cl-architecture-
> 04.tx
> t
> Page 33, second bullet, the use of "'Router Marking' or "Affected
Marking"
> can be used
> to solve the ECMP issue during flow termination.
> 
> Can you please include this information in the PCN architecture draft,
> i.e.,
> in the section that
> discusses the ECMP issue?
> 
> 
> Best regards,
> Georgios
> 

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