Re: [PCN] comment at mike on draft-ietf-tsvwg-rsvp-pcn-01

<karagian@cs.utwente.nl> Tue, 27 March 2012 15:27 UTC

Return-Path: <karagian@cs.utwente.nl>
X-Original-To: pcn@ietfa.amsl.com
Delivered-To: pcn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0837021E80A6; Tue, 27 Mar 2012 08:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.252
X-Spam-Level:
X-Spam-Status: No, score=-0.252 tagged_above=-999 required=5 tests=[AWL=0.252, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fu-U19J4i8uT; Tue, 27 Mar 2012 08:27:56 -0700 (PDT)
Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by ietfa.amsl.com (Postfix) with ESMTP id DA23621E8083; Tue, 27 Mar 2012 08:27:55 -0700 (PDT)
Received: from EXHUB01.ad.utwente.nl (130.89.4.228) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 27 Mar 2012 17:28:01 +0200
Received: from EXMBX04.ad.utwente.nl ([169.254.4.113]) by EXHUB01.ad.utwente.nl ([130.89.4.228]) with mapi id 14.01.0339.001; Tue, 27 Mar 2012 17:27:54 +0200
From: karagian@cs.utwente.nl
To: philip.eardley@bt.com, pcn@ietf.org, tsvwg@ietf.org
Thread-Topic: comment at mike on draft-ietf-tsvwg-rsvp-pcn-01
Thread-Index: AQHNC+6d9MhH5pYYBkKeQn1PQISJ4pZ+QMi0
Date: Tue, 27 Mar 2012 15:27:53 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F26C26AF8@EXMBX04.ad.utwente.nl>
References: <9510D26531EF184D9017DF24659BB87F331DE0C41E@EMV65-UKRD.domain1.systemhost.net>
In-Reply-To: <9510D26531EF184D9017DF24659BB87F331DE0C41E@EMV65-UKRD.domain1.systemhost.net>
Accept-Language: nl-NL, en-US
Content-Language: nl-NL
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [83.202.83.1]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [PCN] comment at mike on draft-ietf-tsvwg-rsvp-pcn-01
X-BeenThere: pcn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCN WG list <pcn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcn>, <mailto:pcn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 27 Mar 2012 15:27:58 -0000

Hi Phil,

This is a good question!

The answer is the following:
By using RFC4860 you could actually deploy both scenarios:

1) Use RFC4860 and configure it to only support only one to one mapping between one RSVP generic aggregated state to one PCN IEA (so only one RSVP aggregated state is using one PHB). In this case exactly the same functionality is achieved as when using the Aggregated RSVP (RFC3175). This is the basic functionality that RFC4860 can provide which is the functionality supported by RFC3175.

2) Use RFC4860 and configure it to support more than one to one mapping between more than one RSVP generic aggregated state to one PCN IEA (so more than one RSVP aggregated states are using one PHB). . In this way the additional features of RFC4860, including bandwidth reduction of the individual flows, can be supported.


Best regards,
Georgios
_______

_________________________________
Van: philip.eardley@bt.com [philip.eardley@bt.com]
Verzonden: dinsdag 27 maart 2012 9:52
Aan: Karagiannis, G. (EWI); pcn@ietf.org; tsvwg@ietf.org
Onderwerp: comment at mike on draft-ietf-tsvwg-rsvp-pcn-01

the question I was trying to raise at the mike earlier is this:-

at the moment the draft is written as an extension to generic aggregated rsvp. Is it possible to write an extension that works as a PCN extension for either /both aggregated rsvp or generic aggregated rsvp? that would widen its applicability.
(Unless in practice only generic aggregated is used and aggregated rsvp isn't used??)

may well be that this is a stupid suggestion!

thanks
phil