[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PCN] Second Last Call for draft-ietf-pcn-architecture
Daisuke,
I think it's very reasonable to add "(others might be possible)" to
S6.3, the same as in S6.1 & 6.2.
You're right that an operator might decide to do something we haven't
thought about.
Thanks
Phil/
{ -----Original Message-----
{ From: pcn-bounces at ietf.org [mailto:pcn-bounces at ietf.org] On Behalf Of
{ daisuke.satoh at ntt-at.co.jp
{ Sent: 01 October 2008 09:36
{ To: pcn at ietf.org
{ Subject: [PCN] Second Last Call for draft-ietf-pcn-architecture
{
{ Hi Phil,
{
{
{ Thank you for accepting my following comment. "Others might be
possible"
{ is added in both 6.1 and 6.2.
{ Does it mean that a new algorithm using the baseline encoding, which
{ realize both admission control and flow termination, is acceptable?
{ I would like to confirm it because there is no "Other might be
possible"
{ in 6.3.
{
{
{
{ A new algorithm may use excess-traffic-marking for PCN-threshold-rate
and
{ threshold-marking for PCN-excess-rate. Actually, Single Marking use
{ excess-traffic-marking for PCN-threshold-rate. It is unclear that the
{ architecture draft excludes such algorithms. In my opinion, they
should
{ not be excluded.
{
{
{
{ Best regards,
{ Daisuke
{
{
{
{ { -----Original Message-----
{ { From: pcn-bounces at ietf.org [mailto:pcn-bounces at ietf.org] On Behalf
Of
{ { daisuke.satoh at ntt-at.co.jp
{ { Sent: 14 August 2008 11:33
{ { To: pcn at ietf.org
{ { Subject: [PCN] PCN WG last call for
draft-ietf-pcn-architecture-05.txt
{ {
{ { Hi all,
{ {
{ {
{ From pcn-bounces at ietf.org Thu Oct 2 09:23:02 2008
Return-Path: <pcn-bounces at ietf.org>
X-Original-To: pcn-archive at optimus.ietf.org
Delivered-To: ietfarch-pcn-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 239FA28C1FC;
Thu, 2 Oct 2008 09:23:02 -0700 (PDT)
X-Original-To: pcn at core3.amsl.com
Delivered-To: pcn at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id BAB3B28C1F4
for <pcn at core3.amsl.com>; Thu, 2 Oct 2008 09:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.186
X-Spam-Level:
X-Spam-Status: No, score=-3.186 tagged_above=-999 required=5 tests=[AWL=0.413,
BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 iy16fn17d9h4 for <pcn at core3.amsl.com>;
Thu, 2 Oct 2008 09:22:59 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150])
by core3.amsl.com (Postfix) with ESMTP id 7C68A28C1D2
for <pcn at ietf.org>; Thu, 2 Oct 2008 09:22:59 -0700 (PDT)
Received: from E03MVB1-UKBR.domain1.systemhost.net ([193.113.197.107]) by
smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830);
Thu, 2 Oct 2008 17:22:46 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 2 Oct 2008 17:22:45 +0100
Message-ID: <4A916DBC72536E419A0BD955EDECEDEC03DAA32A at E03MVB1-UKBR.domain1.systemhost.net>
In-Reply-To: <20081001170320.E114.26AD349 at ntt-at.co.jp>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [PCN] Second Last Call for draft-ietf-pcn-architecture
Thread-Index: AckjoM0QNrLIHHaPRNOWy+qJV4z2gQBCXu9g
From: <philip.eardley at bt.com>
To: <daisuke.satoh at ntt-at.co.jp>,
<pcn at ietf.org>
X-OriginalArrivalTime: 02 Oct 2008 16:22:46.0426 (UTC)
FILETIME=[1ACA8FA0:01C924AB]
Subject: Re: [PCN] Second Last Call for draft-ietf-pcn-architecture
X-BeenThere: pcn at 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 at ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/pcn>
List-Post: <mailto:pcn at ietf.org>
List-Help: <mailto:pcn-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcn>,
<mailto:pcn-request at ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pcn-bounces at ietf.org
Errors-To: pcn-bounces at ietf.org
Daisuke,
I think it's very reasonable to add "(others might be possible)" to
S6.3, the same as in S6.1 & 6.2.
You're right that an operator might decide to do something we haven't
thought about.
Thanks
Phil/
{ -----Original Message-----
{ From: pcn-bounces at ietf.org [mailto:pcn-bounces at ietf.org] On Behalf Of
{ daisuke.satoh at ntt-at.co.jp
{ Sent: 01 October 2008 09:36
{ To: pcn at ietf.org
{ Subject: [PCN] Second Last Call for draft-ietf-pcn-architecture
{
{ Hi Phil,
{
{
{ Thank you for accepting my following comment. "Others might be
possible"
{ is added in both 6.1 and 6.2.
{ Does it mean that a new algorithm using the baseline encoding, which
{ realize both admission control and flow termination, is acceptable?
{ I would like to confirm it because there is no "Other might be
possible"
{ in 6.3.
{
{
{
{ A new algorithm may use excess-traffic-marking for PCN-threshold-rate
and
{ threshold-marking for PCN-excess-rate. Actually, Single Marking use
{ excess-traffic-marking for PCN-threshold-rate. It is unclear that the
{ architecture draft excludes such algorithms. In my opinion, they
should
{ not be excluded.
{
{
{
{ Best regards,
{ Daisuke
{
{
{
{ { -----Original Message-----
{ { From: pcn-bounces at ietf.org [mailto:pcn-bounces at ietf.org] On Behalf
Of
{ { daisuke.satoh at ntt-at.co.jp
{ { Sent: 14 August 2008 11:33
{ { To: pcn at ietf.org
{ { Subject: [PCN] PCN WG last call for
draft-ietf-pcn-architecture-05.txt
{ {
{ { Hi all,
{ {
{ {
{ { I have{ I have been interested in PCN WG and I have joined PCN WG since
{ { IETF69(Chicago).
{ {
{ { I have reviewed the architecture draft and have a comment on Sec
6.3.
{ { The third option (both admission control and flow termination)
almost
{ { describes the single marking algorithm itself. This description
seems
{ to
{ { exclude a future new algorithm and to limit a solution. In my
opinion,
{ a
{ { new algorithm should not be excluded. Actually, a new algorithm idea
{ was
{ { presented in Dublin by Roudiger Geib.
{ {
{ {
{ {
{ { I propose that the third option is modified as follows,
{ { o both admission cotrol and flow termination: Either excess-traffic-
{ { marking
{ { algorithm or threshold-marking algorithm writes PCN-marks. As an
{ example
{ { of excess-traffic-marking case (Figure 2), [I-D.
{ { charney-pcn-single-marking] describes how both admission control and
{ { flow termination can be triggered and also gives some of the pros
and
{ { cons of this approarch. The main downside is that admission control
is
{ { less accurate.
{ {
{ {
{ {
{ {
{ { Best regards,
{ { Daisuke SATOH
{ {
{ {
{
{
{
{
{
{ ---
{ Date: Mon, 29 Sep 2008 12:49:05 -0400
{ From: <slblake at petri-meat.com>
{ Subject: [PCN] Second Last Call for draft-ietf-pcn-architecture
{ To: pcn at ietf.org
{ Message-ID: <864b1db62edbb6688022b71b9421de85 at petri-meat.com>
{ Content-Type: text/plain; charset="UTF-8"
{
{ We will be running a brief (~1 week) last call on
{ draft-ietf-pcn-architecture-06. This last call will end on Tuesday
{ October
{ 7. Please send comments ASAP.
{
{ Diffs between -06 and -05 can be viewed at:
{
{ http://tools.ietf.org/rfcdiff
{
{ Use the following URLs to reference -05 and -06:
{
{ http://tools.ietf.org/id/draft-ietf-pcn-architecture-05.txt
{ http://tools.ietf.org/id/draft-ietf-pcn-architecture-06.txt
{
{ There are some known edits that have to be made before we can submit
to
{ the
{ IESG:
{
{ - Correct references to Internet Drafts to indicate "Work in Progress"
{ - Fix formatting errors detected by ID-nits
{
{
{ Regards,
{
{ // Steve
{
{
{
{ --
{ Daisuke Satoh
{ _______________________________________________
{ PCN mailing list
{ PCN at ietf.org
{ https://www.ietf.org/mailman/listinfo/pcn
_______________________________________________
PCN mailing list
PCN at ietf.org
https://www.ietf.org/mailman/listinfo/pcn
been interested in PCN WG and I have joined PCN WG since
{ { IETF69(Chicago).
{ {
{ { I have reviewed the architecture draft and have a comment on Sec
6.3.
{ { The third option (both admission control and flow termination)
almost
{ { describes the single marking algorithm itself. This description
seems
{ to
{ { exclude a future new algorithm and to limit a solution. In my
opinion,
{ a
{ { new algorithm should not be excluded. Actually, a new algorithm idea
{ was
{ { presented in Dublin by Roudiger Geib.
{ {
{ {
{ {
{ { I propose that the third option is modified as follows,
{ { o both admission cotrol and flow termination: Either excess-traffic-
{ { marking
{ { algorithm or threshold-marking algorithm writes PCN-marks. As an
{ example
{ { of excess-traffic-marking case (Figure 2), [I-D.
{ { charney-pcn-single-marking] describes how both admission control and
{ { flow termination can be triggered and also gives some of the pros
and
{ { cons of this approarch. The main downside is that admission control
is
{ { less accurate.
{ {
{ {
{ {
{ {
{ { Best regards,
{ { Daisuke SATOH
{ {
{ {
{
{
{
{
{
{ ---
{ Date: Mon, 29 Sep 2008 12:49:05 -0400
{ From: <slblake at petri-meat.com>
{ Subject: [PCN] Second Last Call for draft-ietf-pcn-architecture
{ To: pcn at ietf.org
{ Message-ID: <864b1db62edbb6688022b71b9421de85 at petri-meat.com>
{ Content-Type: text/plain; charset="UTF-8"
{
{ We will be running a brief (~1 week) last call on
{ draft-ietf-pcn-architecture-06. This last call will end on Tuesday
{ October
{ 7. Please send comments ASAP.
{
{ Diffs between -06 and -05 can be viewed at:
{
{ http://tools.ietf.org/rfcdiff
{
{ Use the following URLs to reference -05 and -06:
{
{ http://tools.ietf.org/id/draft-ietf-pcn-architecture-05.txt
{ http://tools.ietf.org/id/draft-ietf-pcn-architecture-06.txt
{
{ There are some known edits that have to be made before we can submit
to
{ the
{ IESG:
{
{ - Correct references to Internet Drafts to indicate "Work in Progress"
{ - Fix formatting errors detected by ID-nits
{
{
{ Regards,
{
{ // Steve
{
{
{
{ --
{ Daisuke Satoh
{ _______________________________________________
{ PCN mailing list
{ PCN at ietf.org
{ https://www.ietf.org/mailman/listinfo/pcn
_______________________________________________
PCN mailing list
PCN at ietf.org
https://www.ietf.org/mailman/listinfo/pcn