
From ietfdbh@comcast.net  Mon Dec  6 12:28:10 2010
Return-Path: <ietfdbh@comcast.net>
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 3167D3A6895 for <pcn@core3.amsl.com>; Mon,  6 Dec 2010 12:28:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.81
X-Spam-Level: 
X-Spam-Status: No, score=-101.81 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_05=-1.11, USER_IN_WHITELIST=-100]
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 qhUlFgBNMhmS for <pcn@core3.amsl.com>; Mon,  6 Dec 2010 12:28:09 -0800 (PST)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by core3.amsl.com (Postfix) with ESMTP id BB1AD3A687C for <pcn@ietf.org>; Mon,  6 Dec 2010 12:28:08 -0800 (PST)
Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta09.westchester.pa.mail.comcast.net with comcast id fokc1f00616LCl059wVZx6; Mon, 06 Dec 2010 20:29:33 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta06.westchester.pa.mail.comcast.net with comcast id fwVZ1f0052JQnJT3SwVZLg; Mon, 06 Dec 2010 20:29:33 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <pcn@ietf.org>
Date: Mon, 6 Dec 2010 15:29:14 -0500
Message-ID: <2B3B39A3F62E4B729B52BC86214FF24C@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Thread-Index: AcuVhD8KY0KMNNK1TYCLzDhstd8Q5Q==
Subject: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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: Mon, 06 Dec 2010 20:28:10 -0000

Hi,

I have performed an AD Review of draft-ietf-pcn-sm-edge-behaviour-04
and have some comments.

1) As I reviewed both the SM and CL edge behavior documents, I noted
with concern how similar the documents are. I wonder if you wouldn't
be better having one document, with common text in the early chapters,
and then a section for SM and a section for CL. Or even three
documents, to pave the way for addiitonal behavior documents.

The real concern is that when you have so much common text, you need
to work hard to keep them consistent. An additional concern is that
the IETF (in LC) IESG (in IESG Eval) will need to review these docs,
and check that you haven't overlooked anything; the IETF and IESG
basically perform sanity checks. This is made harder when the text is
almost the same in the two documents. If the editorial text is just
slightly different in multiple places, it becomes much harder to find
the important differences between the documents. 

My concrn has been realized. There are many unimportant differences
between these two documents, that make comparing the two documents
more difficult than it should be, such as:
   such that PCN keep-alive signalling is redundant.
   such that PCN keep-alive is redundant.

   o  NM-rate: octets per second of PCN-traffic in PCN-packets that
are
      not-marked;
   o  NM-rate: octets per second of PCN-traffic in PCN-packets that
are
      not PCN-Marked;

   egress-node, and the Decision Point (which may be collocated with
the
   egress-node and the Decision Point (which may be collocated with
the

   The PCN-egress-node collects the rates of not-marked, threshold-
   marked, and excess-traffic-marked PCN-traffic for each ingress-
   egress-aggregate and reports them to the Decision Point.  It may
also
   The PCN-egress-node collects and reports the rates of not-marked
and
   excess-traffic-marked PCN-traffic to the Decision Point. 
** the sentence structure is unnecssarily different, which makes it
just a little bit harder to read what the technical difference is.

   PCN was that recovery from overloads through the use of flow
   termination should happen within 1-3 seconds.  PCN probably
performs
   better than that.
   PCN was that recovery from overloads by flow termination should
   happen within 1-3 seconds.  PCN probably does better than this.

   o  The marking rules for re-marking PCN-traffic leaving the PCN
   o  The marking rules for re-marking PCN traffic leaving the PCN


   The PCN SM per-domain behaviour may interfere with the use of
end-to-
   end ECN due to reuse of ECN bits for PCN marking.  See Appendix B
of
   [RFC5696] for details.
   The PCN CL per-domain behaviour may interfere with the use of
end-to-
   end ECN due to reuse of ECN bits for PCN marking.  See the
applicable
   PCN marking specifications for details.
dbh: is [5696] the applicable specs? or are there others? How does a
reader determine which specs are applicable?

   quality of service of inelastic flows within a Diffserv domain, in
a
   quality of service (QoS) of inelastic flows within a Diffserv
domain,

   allows decisions to be made on whether to admit or terminate PCN-
   decisions to be made about whether to admit or terminate individual

This editorial inconsistency could hide small, potentially important
technical differences, such as:
   o  ETM-rate: octets per second of PCN-traffic in PCN-packets that
are
      excess-traffic-marked.
   o  ETM-rate: octets per second of PCN traffic in PCN-Marked
packets.

   2.  The amount of traffic that should be terminated is the
       difference:
   2.  The amount of traffic that must be terminated is the
difference:

   choose to complete its selection of PCN-flows to terminate in a
   single round of decisions.
   choose to complete its selection of flows to terminate in a single
   round of decisions.

   node SHOULD cease to admit PCN-flows to the
ingress-egress-aggregate
   node SHOULD cease to admit flows to the ingress-egress-aggregate

   T-maxsuppress if report suppression is enabled, and of the order of
3
   T-maxsuppress if report suppression is activated, and of the order
of

   about incipient overloads before any congestion occurs (hence the
   about overloads before any congestion occurs (hence the "pre" part
of

   o  on each link the reference rate for the excess-traffic-meter is
      configured with a PCN-excess-rate to be equal to the PCN-
      admissible-rate for the link;
   o  on each link the reference rate for the excess traffic meter is
      configured to be equal to the PCN-supportable-rate for the link;
   o  on each link the reference rate for the threshold-meter is
      configured to be equal to the PCN-admissible-rate for the link;

if you are going to have two documents with so much common text, I
will expect the editorial text to be consistent, so the technical
differences are clear.

2) Why are individual flow identifiers reported for
excess-traffic-marked PCN-traffic for CL but not for SM? Wouldn't this
be useful for both?

3) From Acknowledgements:    The authors thank Ruediger Geib for his
useful comments.  The acknowledgements in the CL boundary node
behaviour draft really apply here, too.
dbh: the CL draft is likely to be an RFC. If you want the
acknowledgement in both places, put it in both places.

4) I would be careful referencing other works-in-porgress, just in
case anything slows down the other document(s). No sense holding up
the publication of this document because another document runs into a
delay.

5) please check all lower-case RFC2119 keywords. The IESG prefers that
they be uppercased to make it clear they are normative. I recommend
using "might" rather than "may" for non-normative, and re-wording
musts, shoulds, and recommends to avoid using lowercased reserved
words.

6) section 3.2 and section 3.3.2 both present the formula for CLE, but
they present it differently. Just a style issue, but I recommend
presenting it consistently.

7) section 3.3 "The Decision Point MUST"; I recommend saying "A
compliant Decision Point MUST"

8) "PCN traffic" is used here, but where that term is defined is not
mentioned. Since this is used in formulae, that could be important to
understand correctly.

9) in 3.5, do we really need both t-meas and T-meas, etc.? The chart
would be easier to read if you eliminated one of the redundant
columns.

10) in Table 1, some word breaks are missing from the Action on Expiry
column. Put a space between conditionally and CLE, and between each
and IEA.

11) The acronym IEA is not defined before being used. 

12) t-maxsuppress has discussion of the value to use for an unreliable
transport; what is the recommended value for a reliable transport?

13) section 4 title has extra spaces.


David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)


From ietfdbh@comcast.net  Mon Dec  6 12:55:27 2010
Return-Path: <ietfdbh@comcast.net>
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 4BF153A6893 for <pcn@core3.amsl.com>; Mon,  6 Dec 2010 12:55:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 AjMq-UCaeZ7j for <pcn@core3.amsl.com>; Mon,  6 Dec 2010 12:55:26 -0800 (PST)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by core3.amsl.com (Postfix) with ESMTP id 4003A3A6806 for <pcn@ietf.org>; Mon,  6 Dec 2010 12:55:26 -0800 (PST)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta01.westchester.pa.mail.comcast.net with comcast id fvW51f0060Fqzac51wwryA; Mon, 06 Dec 2010 20:56:51 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta08.westchester.pa.mail.comcast.net with comcast id fwwP1f00Q2JQnJT3UwwSiM; Mon, 06 Dec 2010 20:56:27 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <pcn@ietf.org>
Date: Mon, 6 Dec 2010 15:56:03 -0500
Message-ID: <FEF2029CCC614C6A80884469A91E0015@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Thread-Index: AcuVh/5XpcX0yzhZTNuKSbR1FUGT5Q==
Subject: [PCN] AD Review: draft-ietf-pcn-cl-edge-behaviour-07
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/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: Mon, 06 Dec 2010 20:55:27 -0000

Hi,

Because this document has so much common text with the SM document,
almost all the AD Review comments for the SM document apply to CL as
well. Please incorporate those comments into this review.

A few comments came to mind after sending the SM review, that apply to
both; I added parenthesis to indictae it applies to both).

1) in section 2, reference is made to the "possible extension"
[ID.PCN3in1].
I recommend against referencing "possible extension" documents. 

2) "These allowable transitions are specified here" - usually
specified implies a normative specification. I suggest rewording with
less normative-like wording.

3) in 3.2.3, the calculation for CLE uses either the latest or the
previous interval in its caculations. Niether SM nor CL explains why
it is acceptable to use either interval. Is this explained somewhere?
How does this affect interoperability? (also applies to SM)

4) in 3.3.2, the DP MUST request an estimate of pcn-sent-rate; is
there a specific protocol that must/should be used to do this
(assuming they are not co-located)? If not, how is this
request/response done in a vendor-interoperable manner?

5) in 3.3.2, last paragraph, the list must be ETM-marked flows, right?
It doesn't say that.

6) in 3.3., an alarm should be raised to management. is there are
standardized approach to raising the alarm? If not, how does this
affect interoperability. Most notably, if two nodes form different
vendors raise an alarm using different protocols, how will the
management system correlate the alarms? If two implementations use
SNMP to raise the alarms, should they use consistent OIDs to identify
the problem? or consistent syslog SDEs? or consistent ipfix IEs?
Should the WG standardize the information models, and possibly data
models and protocols, for reporting such alarms?
 
7) in 5.2, it is asserted that [ID.PCN3in1] specifies the behavior;
but 2.2 mentions this as a "possible extension". If PCN3in1 is not
STDS track, then i think this text in 5.2 could be problematic. But I
suspect that 3086 expects a stable specification.

I have not worked with the 3086 template before. Is a reference to a
number of RFCs, without any discussion of their details really
sufficient? It doesn't sounce like that meets the description from
3086:

   This section specifies the rules or guidelines to create this PDB,
   each distinguished with "may", "must" and "should." The technical
   specification must list the classification and traffic conditioning
   required (if any) and the PHB (or PHBs) to be used with any
   additional requirements on their configuration beyond that
contained
   in RFCs.  Classification can reflect the results of an admission
   control process.  Traffic conditioning may include marking, traffic
   shaping, and policing.  A Service Provisioning Policy might be used
   to describe the technical specification of a particular PDB.

8) in 5.7, the reader is referred to "the applicable specifications";
can we identify the applicable specifications?

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)


From tom111.taylor@bell.net  Mon Dec  6 12:57:32 2010
Return-Path: <tom111.taylor@bell.net>
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 214343A689F for <pcn@core3.amsl.com>; Mon,  6 Dec 2010 12:57:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.739
X-Spam-Level: 
X-Spam-Status: No, score=-101.739 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 pOMKdc0h6zCq for <pcn@core3.amsl.com>; Mon,  6 Dec 2010 12:57:31 -0800 (PST)
Received: from blu0-omc3-s26.blu0.hotmail.com (blu0-omc3-s26.blu0.hotmail.com [65.55.116.101]) by core3.amsl.com (Postfix) with ESMTP id DF6CC3A6806 for <pcn@ietf.org>; Mon,  6 Dec 2010 12:57:30 -0800 (PST)
Received: from BLU0-SMTP71 ([65.55.116.74]) by blu0-omc3-s26.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 6 Dec 2010 12:58:42 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP71286F10F61E2EF2AF5284D82B0@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP71.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 6 Dec 2010 12:58:42 -0800
Date: Mon, 6 Dec 2010 15:58:43 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <2B3B39A3F62E4B729B52BC86214FF24C@23FX1C1>
In-Reply-To: <2B3B39A3F62E4B729B52BC86214FF24C@23FX1C1>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Dec 2010 20:58:42.0223 (UTC) FILETIME=[5D37F3F0:01CB9588]
Cc: pcn@ietf.org
Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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: Mon, 06 Dec 2010 20:57:32 -0000

Thanks for your comments.

With the permission of the list, I will look at the possibility of 
merging the two documents. I think any other edge node behaviours will 
be fairly different from these two.

I have responses to some points below. The earlier stuff is snipped.

On 06/12/2010 3:29 PM, David Harrington wrote:
> Hi,
>
> I have performed an AD Review of draft-ietf-pcn-sm-edge-behaviour-04
> and have some comments.
>
...
>
> 2) Why are individual flow identifiers reported for
> excess-traffic-marked PCN-traffic for CL but not for SM? Wouldn't this
> be useful for both?

[PTT] SM uses only excess-marking, and as a result, there won't 
necessarily be any flow termination when excess-traffic-marked flows are 
observed. Since flow termination is expected to be a relatively rare 
event, collecting and carrying flow identifiers would be a significant 
waste of resources.
>
> 3) From Acknowledgements:    The authors thank Ruediger Geib for his
> useful comments.  The acknowledgements in the CL boundary node
> behaviour draft really apply here, too.
> dbh: the CL draft is likely to be an RFC. If you want the
> acknowledgement in both places, put it in both places.

[PTT] Good point.
>
> 4) I would be careful referencing other works-in-porgress, just in
> case anything slows down the other document(s). No sense holding up
> the publication of this document because another document runs into a
> delay.
>
> 5) please check all lower-case RFC2119 keywords. The IESG prefers that
> they be uppercased to make it clear they are normative. I recommend
> using "might" rather than "may" for non-normative, and re-wording
> musts, shoulds, and recommends to avoid using lowercased reserved
> words.

[PTT] OK
>
> 6) section 3.2 and section 3.3.2 both present the formula for CLE, but
> they present it differently. Just a style issue, but I recommend
> presenting it consistently.

[PTT] OK
>
> 7) section 3.3 "The Decision Point MUST"; I recommend saying "A
> compliant Decision Point MUST"

[PTT] OK
>
> 8) "PCN traffic" is used here, but where that term is defined is not
> mentioned. Since this is used in formulae, that could be important to
> understand correctly.

[PTT] Will add a definition.
>
> 9) in 3.5, do we really need both t-meas and T-meas, etc.? The chart
> would be easier to read if you eliminated one of the redundant
> columns.

[PTT] Earlier versions didn't make the semantic distinction between 
timer variables and their limits and that led to confusion. I'll take 
another look at how this can be clarified.
>
> 10) in Table 1, some word breaks are missing from the Action on Expiry
> column. Put a space between conditionally and CLE, and between each
> and IEA.

[PTT] IIRC that was xml2rfc's doing, though of course I'll check. As an 
xml2rfc maintainer I might put a bug report in.
>
> 11) The acronym IEA is not defined before being used.
>
> 12) t-maxsuppress has discussion of the value to use for an unreliable
> transport; what is the recommended value for a reliable transport?

[PTT] Thought that was covered. I'll have to check.
>
> 13) section 4 title has extra spaces.
>
[PTT] OK
>
> David Harrington
> Director, IETF Transport Area
> ietfdbh@comcast.net (preferred for ietf)
> dbharrington@huaweisymantec.com
> +1 603 828 1401 (cell)
>
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>
>

From menth@informatik.uni-tuebingen.de  Mon Dec  6 14:05:16 2010
Return-Path: <menth@informatik.uni-tuebingen.de>
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 B718E3A68BE for <pcn@core3.amsl.com>; Mon,  6 Dec 2010 14:05:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.707
X-Spam-Level: 
X-Spam-Status: No, score=0.707 tagged_above=-999 required=5 tests=[AWL=-0.906,  BAYES_40=-0.185, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448]
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 DOkxCbQtT863 for <pcn@core3.amsl.com>; Mon,  6 Dec 2010 14:05:14 -0800 (PST)
Received: from mx5.informatik.uni-tuebingen.de (mx5.Informatik.Uni-Tuebingen.De [134.2.12.32]) by core3.amsl.com (Postfix) with SMTP id 360C63A68B1 for <pcn@ietf.org>; Mon,  6 Dec 2010 14:05:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.informatik.uni-tuebingen.de (Postfix) with ESMTP id C81885279; Mon,  6 Dec 2010 23:06:35 +0100 (MET)
X-Virus-Scanned: amavisd-new at informatik.uni-tuebingen.de
Received: from mx5.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx5.informatik.uni-tuebingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wm1nif68LlYP; Mon,  6 Dec 2010 23:06:31 +0100 (MET)
Received: from zcs-pu.informatik.uni-tuebingen.de (zcs-pu.Informatik.Uni-Tuebingen.De [134.2.12.61]) by mx5.informatik.uni-tuebingen.de (Postfix) with ESMTP id 4219B4B56; Mon,  6 Dec 2010 23:06:31 +0100 (MET)
Received: from [192.168.1.100] (HSI-KBW-095-208-114-108.hsi5.kabel-badenwuerttemberg.de [95.208.114.108]) by zcs-pu.informatik.uni-tuebingen.de (Postfix) with ESMTP id B0430BF37B6; Mon,  6 Dec 2010 23:06:30 +0100 (CET)
Message-ID: <4CFD5E67.4010404@informatik.uni-tuebingen.de>
Date: Mon, 06 Dec 2010 23:06:31 +0100
From: Michael Menth <menth@informatik.uni-tuebingen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: ietfdbh@comcast.net, Tom Taylor <tom111.taylor@bell.net>
References: <2B3B39A3F62E4B729B52BC86214FF24C@23FX1C1> <BLU0-SMTP71286F10F61E2EF2AF5284D82B0@phx.gbl>
In-Reply-To: <BLU0-SMTP71286F10F61E2EF2AF5284D82B0@phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: pcn@ietf.org
Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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: Mon, 06 Dec 2010 22:05:16 -0000

Hi David, hi Peter,

>> 2) Why are individual flow identifiers reported for
>> excess-traffic-marked PCN-traffic for CL but not for SM? Wouldn't this
>> be useful for both?
>
> [PTT] SM uses only excess-marking, and as a result, there won't=20
> necessarily be any flow termination when excess-traffic-marked flows=20
> are observed. Since flow termination is expected to be a relatively=20
> rare event, collecting and carrying flow identifiers would be a=20
> significant waste of resources.

One can put it in other words. The problem is that SM re-marks traffic=20
based on the admissible rate to indicate termination. Little re-marked=20
traffic does not indicate termination but lots of re-marked traffic=20
indicates termination.
1) When packets are re-marked, the supportable rate is not necessarily=20
exceeded by PCN traffic. Then, termination is not needed. Signalling=20
identifiers of re-marked flows in that case seems to be lots of overhead=20
(as stated above).
2) In networks with multipath routing (only there providing information=20
of re-marked flows is helpful), flows belonging to the same IEA may go=20
over different paths where the PCN traffic rate exceeds the supportable=20
rate of at least one link or where the PCN traffic rate exceeds the=20
admissible rate of at least one link but not the supportable rate. In=20
that scenario, the information that a flow was "re-marked" does not=20
necessarily indicate that the re-marked flow is a candidate for=20
termination. Providing identifiers of "re-marked" flows just increases=20
the probability to terminate the right flows.
3) SM is not a good option anyway for networks with multipath routing,=20
see 4.8.3 in
http://www3.informatik.uni-wuerzburg.de/staff/menth/Publications/papers/M=
enth08-Sub-9.pdf

Regards,

     Michael

--=20
Prof. Dr. habil. Michael Menth
University of Tuebingen
Wilhelm-Schickard-Institute
Lehrstuhl f=FCr Rechnernetze und Internet
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70505, fax: (+49)-7071/29-5220
mailto:menth@uni-tuebingen.de, http://www.net2.uni-tuebingen.de


From karagian@cs.utwente.nl  Mon Dec  6 23:36:49 2010
Return-Path: <karagian@cs.utwente.nl>
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 3D14E3A691C for <pcn@core3.amsl.com>; Mon,  6 Dec 2010 23:36:49 -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 c3JBrPcFM0+N for <pcn@core3.amsl.com>; Mon,  6 Dec 2010 23:36:46 -0800 (PST)
Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11]) by core3.amsl.com (Postfix) with ESMTP id 99A583A68C2 for <pcn@ietf.org>; Mon,  6 Dec 2010 23:36:45 -0800 (PST)
Received: from webmail.cs.utwente.nl (janus.ewi.utwente.nl [130.89.10.26]) by denhaag.ewi.utwente.nl (8.13.6/8.13.6) with SMTP id oB77buUj024075;  Tue, 7 Dec 2010 08:37:56 +0100 (MET)
Received: from 84.82.109.231 (auth. user karagian@imap1.ewi.utwente.nl) by webmail.cs.utwente.nl with HTTP; Tue, 07 Dec 2010 07:37:57 +0000
To: "David Harrington" <ietfdbh@comcast.net>, "pcn@ietf.org" <pcn@ietf.org>
Date: Tue, 07 Dec 2010 07:37:57 +0000
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <MTmJvkts.1291707477.0672830.karagian@ewi.utwente.nl>
In-Reply-To: <2B3B39A3F62E4B729B52BC86214FF24C@23FX1C1>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Errors-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (denhaag.ewi.utwente.nl [130.89.10.11]); Tue, 07 Dec 2010 08:38:07 +0100 (MET)
Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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, 07 Dec 2010 07:36:49 -0000

Dear David

Thank you very much for the provided comments!

Regarding the first comment, if it is to either merge the two documents,
or merge and then again split the documents in three documents, then I
am in favour of the latter one.

One document could describe the common text, that will be the same for
all edge behaviour drafts. Other two documents could then be related to
CL and the to SM. These CL and SM documents could refer then to the
common document.

All new edge behaviour drafts should also use as much as possible the
common document.

Best regards,
Georgios

On 12/6/2010, "David Harrington" <ietfdbh@comcast.net> wrote:

>Hi,
>
>I have performed an AD Review of draft-ietf-pcn-sm-edge-behaviour-04
>and have some comments.
>
>1) As I reviewed both the SM and CL edge behavior documents, I noted
>with concern how similar the documents are. I wonder if you wouldn't
>be better having one document, with common text in the early chapters,
>and then a section for SM and a section for CL. Or even three
>documents, to pave the way for addiitonal behavior documents.
>
>The real concern is that when you have so much common text, you need
>to work hard to keep them consistent. An additional concern is that
>the IETF (in LC) IESG (in IESG Eval) will need to review these docs,
>and check that you haven't overlooked anything; the IETF and IESG
>basically perform sanity checks. This is made harder when the text is
>almost the same in the two documents. If the editorial text is just
>slightly different in multiple places, it becomes much harder to find
>the important differences between the documents.
>
>My concrn has been realized. There are many unimportant differences
>between these two documents, that make comparing the two documents
>more difficult than it should be, such as:
>   such that PCN keep-alive signalling is redundant.
>   such that PCN keep-alive is redundant.
>
>   o  NM-rate: octets per second of PCN-traffic in PCN-packets that
>are
>      not-marked;
>   o  NM-rate: octets per second of PCN-traffic in PCN-packets that
>are
>      not PCN-Marked;
>
>   egress-node, and the Decision Point (which may be collocated with
>the
>   egress-node and the Decision Point (which may be collocated with
>the
>
>   The PCN-egress-node collects the rates of not-marked, threshold-
>   marked, and excess-traffic-marked PCN-traffic for each ingress-
>   egress-aggregate and reports them to the Decision Point.  It may
>also
>   The PCN-egress-node collects and reports the rates of not-marked
>and
>   excess-traffic-marked PCN-traffic to the Decision Point.
>** the sentence structure is unnecssarily different, which makes it
>just a little bit harder to read what the technical difference is.
>
>   PCN was that recovery from overloads through the use of flow
>   termination should happen within 1-3 seconds.  PCN probably
>performs
>   better than that.
>   PCN was that recovery from overloads by flow termination should
>   happen within 1-3 seconds.  PCN probably does better than this.
>
>   o  The marking rules for re-marking PCN-traffic leaving the PCN
>   o  The marking rules for re-marking PCN traffic leaving the PCN
>
>
>   The PCN SM per-domain behaviour may interfere with the use of
>end-to-
>   end ECN due to reuse of ECN bits for PCN marking.  See Appendix B
>of
>   [RFC5696] for details.
>   The PCN CL per-domain behaviour may interfere with the use of
>end-to-
>   end ECN due to reuse of ECN bits for PCN marking.  See the
>applicable
>   PCN marking specifications for details.
>dbh: is [5696] the applicable specs? or are there others? How does a
>reader determine which specs are applicable?
>
>   quality of service of inelastic flows within a Diffserv domain, in
>a
>   quality of service (QoS) of inelastic flows within a Diffserv
>domain,
>
>   allows decisions to be made on whether to admit or terminate PCN-
>   decisions to be made about whether to admit or terminate individual
>
>This editorial inconsistency could hide small, potentially important
>technical differences, such as:
>   o  ETM-rate: octets per second of PCN-traffic in PCN-packets that
>are
>      excess-traffic-marked.
>   o  ETM-rate: octets per second of PCN traffic in PCN-Marked
>packets.
>
>   2.  The amount of traffic that should be terminated is the
>       difference:
>   2.  The amount of traffic that must be terminated is the
>difference:
>
>   choose to complete its selection of PCN-flows to terminate in a
>   single round of decisions.
>   choose to complete its selection of flows to terminate in a single
>   round of decisions.
>
>   node SHOULD cease to admit PCN-flows to the
>ingress-egress-aggregate
>   node SHOULD cease to admit flows to the ingress-egress-aggregate
>
>   T-maxsuppress if report suppression is enabled, and of the order of
>3
>   T-maxsuppress if report suppression is activated, and of the order
>of
>
>   about incipient overloads before any congestion occurs (hence the
>   about overloads before any congestion occurs (hence the "pre" part
>of
>
>   o  on each link the reference rate for the excess-traffic-meter is
>      configured with a PCN-excess-rate to be equal to the PCN-
>      admissible-rate for the link;
>   o  on each link the reference rate for the excess traffic meter is
>      configured to be equal to the PCN-supportable-rate for the link;
>   o  on each link the reference rate for the threshold-meter is
>      configured to be equal to the PCN-admissible-rate for the link;
>
>if you are going to have two documents with so much common text, I
>will expect the editorial text to be consistent, so the technical
>differences are clear.
>
>2) Why are individual flow identifiers reported for
>excess-traffic-marked PCN-traffic for CL but not for SM? Wouldn't this
>be useful for both?
>
>3) From Acknowledgements:    The authors thank Ruediger Geib for his
>useful comments.  The acknowledgements in the CL boundary node
>behaviour draft really apply here, too.
>dbh: the CL draft is likely to be an RFC. If you want the
>acknowledgement in both places, put it in both places.
>
>4) I would be careful referencing other works-in-porgress, just in
>case anything slows down the other document(s). No sense holding up
>the publication of this document because another document runs into a
>delay.
>
>5) please check all lower-case RFC2119 keywords. The IESG prefers that
>they be uppercased to make it clear they are normative. I recommend
>using "might" rather than "may" for non-normative, and re-wording
>musts, shoulds, and recommends to avoid using lowercased reserved
>words.
>
>6) section 3.2 and section 3.3.2 both present the formula for CLE, but
>they present it differently. Just a style issue, but I recommend
>presenting it consistently.
>
>7) section 3.3 "The Decision Point MUST"; I recommend saying "A
>compliant Decision Point MUST"
>
>8) "PCN traffic" is used here, but where that term is defined is not
>mentioned. Since this is used in formulae, that could be important to
>understand correctly.
>
>9) in 3.5, do we really need both t-meas and T-meas, etc.? The chart
>would be easier to read if you eliminated one of the redundant
>columns.
>
>10) in Table 1, some word breaks are missing from the Action on Expiry
>column. Put a space between conditionally and CLE, and between each
>and IEA.
>
>11) The acronym IEA is not defined before being used.
>
>12) t-maxsuppress has discussion of the value to use for an unreliable
>transport; what is the recommended value for a reliable transport?
>
>13) section 4 title has extra spaces.
>
>
>David Harrington
>Director, IETF Transport Area
>ietfdbh@comcast.net (preferred for ietf)
>dbharrington@huaweisymantec.com
>+1 603 828 1401 (cell)
>
>_______________________________________________
>PCN mailing list
>PCN@ietf.org
>https://www.ietf.org/mailman/listinfo/pcn

From philip.eardley@bt.com  Tue Dec  7 01:24:00 2010
Return-Path: <philip.eardley@bt.com>
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 A72243A68B0 for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 01:24:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.964
X-Spam-Level: 
X-Spam-Status: No, score=-101.964 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
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 KucpiTyX1i-J for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 01:23:58 -0800 (PST)
Received: from smtpe1.intersmtp.com (smtp63.intersmtp.COM [62.239.224.236]) by core3.amsl.com (Postfix) with ESMTP id B00123A6892 for <pcn@ietf.org>; Tue,  7 Dec 2010 01:23:30 -0800 (PST)
Received: from EVMHT67-UKRD.domain1.systemhost.net (10.36.3.104) by RDW083A007ED63.smtp-e3.hygiene.service (10.187.98.12) with Microsoft SMTP Server (TLS) id 8.3.106.1; Tue, 7 Dec 2010 09:24:49 +0000
Received: from EMV65-UKRD.domain1.systemhost.net ([169.254.1.86]) by EVMHT67-UKRD.domain1.systemhost.net ([10.36.3.104]) with mapi; Tue, 7 Dec 2010 09:24:55 +0000
From: <philip.eardley@bt.com>
To: <karagian@cs.utwente.nl>, <ietfdbh@comcast.net>, <pcn@ietf.org>
Date: Tue, 7 Dec 2010 09:24:54 +0000
Thread-Topic: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
Thread-Index: AcuV4bjIyYS6kLnJQu24PNUQGyhB7gADljRg
Message-ID: <9510D26531EF184D9017DF24659BB87F32666F56AC@EMV65-UKRD.domain1.systemhost.net>
References: <2B3B39A3F62E4B729B52BC86214FF24C@23FX1C1> <MTmJvkts.1291707477.0672830.karagian@ewi.utwente.nl>
In-Reply-To: <MTmJvkts.1291707477.0672830.karagian@ewi.utwente.nl>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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, 07 Dec 2010 09:24:00 -0000

I'm happy to leave it to the editor to decide how to handle the first comme=
nt - Tom, whatever you think is the easiest way of handling (1, 2 or 3 docs=
).
=09
-----Original Message-----
From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of Georg=
ios Karagiannis
Sent: 07 December 2010 07:38
To: David Harrington; pcn@ietf.org
Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04

Dear David

Thank you very much for the provided comments!

Regarding the first comment, if it is to either merge the two documents,
or merge and then again split the documents in three documents, then I
am in favour of the latter one.

One document could describe the common text, that will be the same for
all edge behaviour drafts. Other two documents could then be related to
CL and the to SM. These CL and SM documents could refer then to the
common document.

All new edge behaviour drafts should also use as much as possible the
common document.

Best regards,
Georgios

On 12/6/2010, "David Harrington" <ietfdbh@comcast.net> wrote:

>Hi,
>
>I have performed an AD Review of draft-ietf-pcn-sm-edge-behaviour-04
>and have some comments.
>
>1) As I reviewed both the SM and CL edge behavior documents, I noted
>with concern how similar the documents are. I wonder if you wouldn't
>be better having one document, with common text in the early chapters,
>and then a section for SM and a section for CL. Or even three
>documents, to pave the way for addiitonal behavior documents.
>
>The real concern is that when you have so much common text, you need
>to work hard to keep them consistent. An additional concern is that
>the IETF (in LC) IESG (in IESG Eval) will need to review these docs,
>and check that you haven't overlooked anything; the IETF and IESG
>basically perform sanity checks. This is made harder when the text is
>almost the same in the two documents. If the editorial text is just
>slightly different in multiple places, it becomes much harder to find
>the important differences between the documents.
>
>My concrn has been realized. There are many unimportant differences
>between these two documents, that make comparing the two documents
>more difficult than it should be, such as:
>   such that PCN keep-alive signalling is redundant.
>   such that PCN keep-alive is redundant.
>
>   o  NM-rate: octets per second of PCN-traffic in PCN-packets that
>are
>      not-marked;
>   o  NM-rate: octets per second of PCN-traffic in PCN-packets that
>are
>      not PCN-Marked;
>
>   egress-node, and the Decision Point (which may be collocated with
>the
>   egress-node and the Decision Point (which may be collocated with
>the
>
>   The PCN-egress-node collects the rates of not-marked, threshold-
>   marked, and excess-traffic-marked PCN-traffic for each ingress-
>   egress-aggregate and reports them to the Decision Point.  It may
>also
>   The PCN-egress-node collects and reports the rates of not-marked
>and
>   excess-traffic-marked PCN-traffic to the Decision Point.
>** the sentence structure is unnecssarily different, which makes it
>just a little bit harder to read what the technical difference is.
>
>   PCN was that recovery from overloads through the use of flow
>   termination should happen within 1-3 seconds.  PCN probably
>performs
>   better than that.
>   PCN was that recovery from overloads by flow termination should
>   happen within 1-3 seconds.  PCN probably does better than this.
>
>   o  The marking rules for re-marking PCN-traffic leaving the PCN
>   o  The marking rules for re-marking PCN traffic leaving the PCN
>
>
>   The PCN SM per-domain behaviour may interfere with the use of
>end-to-
>   end ECN due to reuse of ECN bits for PCN marking.  See Appendix B
>of
>   [RFC5696] for details.
>   The PCN CL per-domain behaviour may interfere with the use of
>end-to-
>   end ECN due to reuse of ECN bits for PCN marking.  See the
>applicable
>   PCN marking specifications for details.
>dbh: is [5696] the applicable specs? or are there others? How does a
>reader determine which specs are applicable?
>
>   quality of service of inelastic flows within a Diffserv domain, in
>a
>   quality of service (QoS) of inelastic flows within a Diffserv
>domain,
>
>   allows decisions to be made on whether to admit or terminate PCN-
>   decisions to be made about whether to admit or terminate individual
>
>This editorial inconsistency could hide small, potentially important
>technical differences, such as:
>   o  ETM-rate: octets per second of PCN-traffic in PCN-packets that
>are
>      excess-traffic-marked.
>   o  ETM-rate: octets per second of PCN traffic in PCN-Marked
>packets.
>
>   2.  The amount of traffic that should be terminated is the
>       difference:
>   2.  The amount of traffic that must be terminated is the
>difference:
>
>   choose to complete its selection of PCN-flows to terminate in a
>   single round of decisions.
>   choose to complete its selection of flows to terminate in a single
>   round of decisions.
>
>   node SHOULD cease to admit PCN-flows to the
>ingress-egress-aggregate
>   node SHOULD cease to admit flows to the ingress-egress-aggregate
>
>   T-maxsuppress if report suppression is enabled, and of the order of
>3
>   T-maxsuppress if report suppression is activated, and of the order
>of
>
>   about incipient overloads before any congestion occurs (hence the
>   about overloads before any congestion occurs (hence the "pre" part
>of
>
>   o  on each link the reference rate for the excess-traffic-meter is
>      configured with a PCN-excess-rate to be equal to the PCN-
>      admissible-rate for the link;
>   o  on each link the reference rate for the excess traffic meter is
>      configured to be equal to the PCN-supportable-rate for the link;
>   o  on each link the reference rate for the threshold-meter is
>      configured to be equal to the PCN-admissible-rate for the link;
>
>if you are going to have two documents with so much common text, I
>will expect the editorial text to be consistent, so the technical
>differences are clear.
>
>2) Why are individual flow identifiers reported for
>excess-traffic-marked PCN-traffic for CL but not for SM? Wouldn't this
>be useful for both?
>
>3) From Acknowledgements:    The authors thank Ruediger Geib for his
>useful comments.  The acknowledgements in the CL boundary node
>behaviour draft really apply here, too.
>dbh: the CL draft is likely to be an RFC. If you want the
>acknowledgement in both places, put it in both places.
>
>4) I would be careful referencing other works-in-porgress, just in
>case anything slows down the other document(s). No sense holding up
>the publication of this document because another document runs into a
>delay.
>
>5) please check all lower-case RFC2119 keywords. The IESG prefers that
>they be uppercased to make it clear they are normative. I recommend
>using "might" rather than "may" for non-normative, and re-wording
>musts, shoulds, and recommends to avoid using lowercased reserved
>words.
>
>6) section 3.2 and section 3.3.2 both present the formula for CLE, but
>they present it differently. Just a style issue, but I recommend
>presenting it consistently.
>
>7) section 3.3 "The Decision Point MUST"; I recommend saying "A
>compliant Decision Point MUST"
>
>8) "PCN traffic" is used here, but where that term is defined is not
>mentioned. Since this is used in formulae, that could be important to
>understand correctly.
>
>9) in 3.5, do we really need both t-meas and T-meas, etc.? The chart
>would be easier to read if you eliminated one of the redundant
>columns.
>
>10) in Table 1, some word breaks are missing from the Action on Expiry
>column. Put a space between conditionally and CLE, and between each
>and IEA.
>
>11) The acronym IEA is not defined before being used.
>
>12) t-maxsuppress has discussion of the value to use for an unreliable
>transport; what is the recommended value for a reliable transport?
>
>13) section 4 title has extra spaces.
>
>
>David Harrington
>Director, IETF Transport Area
>ietfdbh@comcast.net (preferred for ietf)
>dbharrington@huaweisymantec.com
>+1 603 828 1401 (cell)
>
>_______________________________________________
>PCN mailing list
>PCN@ietf.org
>https://www.ietf.org/mailman/listinfo/pcn
_______________________________________________
PCN mailing list
PCN@ietf.org
https://www.ietf.org/mailman/listinfo/pcn

From toby@moncaster.com  Tue Dec  7 01:34:02 2010
Return-Path: <toby@moncaster.com>
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 EFF333A693E for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 01:34:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.407
X-Spam-Level: 
X-Spam-Status: No, score=-1.407 tagged_above=-999 required=5 tests=[AWL=0.842,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 RYdpRMWxMzPH for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 01:33:57 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by core3.amsl.com (Postfix) with ESMTP id C9CA43A693B for <pcn@ietf.org>; Tue,  7 Dec 2010 01:33:54 -0800 (PST)
Received: from TobysHP (host86-152-88-47.range86-152.btcentralplus.com [86.152.88.47]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0Lz0gC-1OLeBX2hge-014mQR; Tue, 07 Dec 2010 10:35:16 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: <philip.eardley@bt.com>, <karagian@cs.utwente.nl>, <ietfdbh@comcast.net>, <pcn@ietf.org>
References: <2B3B39A3F62E4B729B52BC86214FF24C@23FX1C1>	<MTmJvkts.1291707477.0672830.karagian@ewi.utwente.nl> <9510D26531EF184D9017DF24659BB87F32666F56AC@EMV65-UKRD.domain1.systemhost.net>
In-Reply-To: <9510D26531EF184D9017DF24659BB87F32666F56AC@EMV65-UKRD.domain1.systemhost.net>
Date: Tue, 7 Dec 2010 09:35:16 -0000
Message-ID: <000901cb95f2$0ebe06f0$2c3a14d0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcuV4bjIyYS6kLnJQu24PNUQGyhB7gADljRgAABiGxA=
Content-Language: en-gb
X-Provags-ID: V02:K0:IfoidtLOTyVA2huGQopMcopPO5FGbc+5p5p14bvjZG0 XZqfeV8Eom+k0KAjL+vvdRFI2kddlK/X3AozSx1hTxBq+Vbg56 tM6+awaK8TNYMKqjWiRbYZyasAOfW/w8xfC/xEW/Kfe+3WqAem wrJ1cFQ4Wv2k/mkCBcE4UxeDWp4AGDgS8NzeO3xYGQb9aqFa99 sTGEzyiOnc0QHCsow1hdJk28HSirzdTL7Nt4qNwpPw=
Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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, 07 Dec 2010 09:34:02 -0000

As I see things the aim of RFCs should be to make life easy for vendors and
developers. The more RFCs that relate to a single technology, the harder it
is for people to be certain they are fully compliant.

Speaking for myself, I would find a single document easiest. That document
could be structured into three parts as Georgios suggests below. The only
issue then is that somewhere there will need to be some text to explain how
developers choose which scheme to go for, and mandating certain behaviours
as a result... This could be an interesting challenge for Tom...

Toby

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> philip.eardley@bt.com
> Sent: 07 December 2010 09:25
> To: karagian@cs.utwente.nl; ietfdbh@comcast.net; pcn@ietf.org
> Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
> 
> I'm happy to leave it to the editor to decide how to handle the first
> comment - Tom, whatever you think is the easiest way of handling (1, 2
> or 3 docs).
> 
> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Georgios Karagiannis
> Sent: 07 December 2010 07:38
> To: David Harrington; pcn@ietf.org
> Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
> 
> Dear David
> 
> Thank you very much for the provided comments!
> 
> Regarding the first comment, if it is to either merge the two
> documents,
> or merge and then again split the documents in three documents, then I
> am in favour of the latter one.
> 
> One document could describe the common text, that will be the same for
> all edge behaviour drafts. Other two documents could then be related to
> CL and the to SM. These CL and SM documents could refer then to the
> common document.
> 
> All new edge behaviour drafts should also use as much as possible the
> common document.
> 
> Best regards,
> Georgios
> 
> On 12/6/2010, "David Harrington" <ietfdbh@comcast.net> wrote:
> 
> >Hi,
> >
> >I have performed an AD Review of draft-ietf-pcn-sm-edge-behaviour-04
> >and have some comments.
> >
> >1) As I reviewed both the SM and CL edge behavior documents, I noted
> >with concern how similar the documents are. I wonder if you wouldn't
> >be better having one document, with common text in the early chapters,
> >and then a section for SM and a section for CL. Or even three
> >documents, to pave the way for addiitonal behavior documents.
> >
> >The real concern is that when you have so much common text, you need
> >to work hard to keep them consistent. An additional concern is that
> >the IETF (in LC) IESG (in IESG Eval) will need to review these docs,
> >and check that you haven't overlooked anything; the IETF and IESG
> >basically perform sanity checks. This is made harder when the text is
> >almost the same in the two documents. If the editorial text is just
> >slightly different in multiple places, it becomes much harder to find
> >the important differences between the documents.
> >
> >My concrn has been realized. There are many unimportant differences
> >between these two documents, that make comparing the two documents
> >more difficult than it should be, such as:
> >   such that PCN keep-alive signalling is redundant.
> >   such that PCN keep-alive is redundant.
> >
> >   o  NM-rate: octets per second of PCN-traffic in PCN-packets that
> >are
> >      not-marked;
> >   o  NM-rate: octets per second of PCN-traffic in PCN-packets that
> >are
> >      not PCN-Marked;
> >
> >   egress-node, and the Decision Point (which may be collocated with
> >the
> >   egress-node and the Decision Point (which may be collocated with
> >the
> >
> >   The PCN-egress-node collects the rates of not-marked, threshold-
> >   marked, and excess-traffic-marked PCN-traffic for each ingress-
> >   egress-aggregate and reports them to the Decision Point.  It may
> >also
> >   The PCN-egress-node collects and reports the rates of not-marked
> >and
> >   excess-traffic-marked PCN-traffic to the Decision Point.
> >** the sentence structure is unnecssarily different, which makes it
> >just a little bit harder to read what the technical difference is.
> >
> >   PCN was that recovery from overloads through the use of flow
> >   termination should happen within 1-3 seconds.  PCN probably
> >performs
> >   better than that.
> >   PCN was that recovery from overloads by flow termination should
> >   happen within 1-3 seconds.  PCN probably does better than this.
> >
> >   o  The marking rules for re-marking PCN-traffic leaving the PCN
> >   o  The marking rules for re-marking PCN traffic leaving the PCN
> >
> >
> >   The PCN SM per-domain behaviour may interfere with the use of
> >end-to-
> >   end ECN due to reuse of ECN bits for PCN marking.  See Appendix B
> >of
> >   [RFC5696] for details.
> >   The PCN CL per-domain behaviour may interfere with the use of
> >end-to-
> >   end ECN due to reuse of ECN bits for PCN marking.  See the
> >applicable
> >   PCN marking specifications for details.
> >dbh: is [5696] the applicable specs? or are there others? How does a
> >reader determine which specs are applicable?
> >
> >   quality of service of inelastic flows within a Diffserv domain, in
> >a
> >   quality of service (QoS) of inelastic flows within a Diffserv
> >domain,
> >
> >   allows decisions to be made on whether to admit or terminate PCN-
> >   decisions to be made about whether to admit or terminate individual
> >
> >This editorial inconsistency could hide small, potentially important
> >technical differences, such as:
> >   o  ETM-rate: octets per second of PCN-traffic in PCN-packets that
> >are
> >      excess-traffic-marked.
> >   o  ETM-rate: octets per second of PCN traffic in PCN-Marked
> >packets.
> >
> >   2.  The amount of traffic that should be terminated is the
> >       difference:
> >   2.  The amount of traffic that must be terminated is the
> >difference:
> >
> >   choose to complete its selection of PCN-flows to terminate in a
> >   single round of decisions.
> >   choose to complete its selection of flows to terminate in a single
> >   round of decisions.
> >
> >   node SHOULD cease to admit PCN-flows to the
> >ingress-egress-aggregate
> >   node SHOULD cease to admit flows to the ingress-egress-aggregate
> >
> >   T-maxsuppress if report suppression is enabled, and of the order of
> >3
> >   T-maxsuppress if report suppression is activated, and of the order
> >of
> >
> >   about incipient overloads before any congestion occurs (hence the
> >   about overloads before any congestion occurs (hence the "pre" part
> >of
> >
> >   o  on each link the reference rate for the excess-traffic-meter is
> >      configured with a PCN-excess-rate to be equal to the PCN-
> >      admissible-rate for the link;
> >   o  on each link the reference rate for the excess traffic meter is
> >      configured to be equal to the PCN-supportable-rate for the link;
> >   o  on each link the reference rate for the threshold-meter is
> >      configured to be equal to the PCN-admissible-rate for the link;
> >
> >if you are going to have two documents with so much common text, I
> >will expect the editorial text to be consistent, so the technical
> >differences are clear.
> >
> >2) Why are individual flow identifiers reported for
> >excess-traffic-marked PCN-traffic for CL but not for SM? Wouldn't this
> >be useful for both?
> >
> >3) From Acknowledgements:    The authors thank Ruediger Geib for his
> >useful comments.  The acknowledgements in the CL boundary node
> >behaviour draft really apply here, too.
> >dbh: the CL draft is likely to be an RFC. If you want the
> >acknowledgement in both places, put it in both places.
> >
> >4) I would be careful referencing other works-in-porgress, just in
> >case anything slows down the other document(s). No sense holding up
> >the publication of this document because another document runs into a
> >delay.
> >
> >5) please check all lower-case RFC2119 keywords. The IESG prefers that
> >they be uppercased to make it clear they are normative. I recommend
> >using "might" rather than "may" for non-normative, and re-wording
> >musts, shoulds, and recommends to avoid using lowercased reserved
> >words.
> >
> >6) section 3.2 and section 3.3.2 both present the formula for CLE, but
> >they present it differently. Just a style issue, but I recommend
> >presenting it consistently.
> >
> >7) section 3.3 "The Decision Point MUST"; I recommend saying "A
> >compliant Decision Point MUST"
> >
> >8) "PCN traffic" is used here, but where that term is defined is not
> >mentioned. Since this is used in formulae, that could be important to
> >understand correctly.
> >
> >9) in 3.5, do we really need both t-meas and T-meas, etc.? The chart
> >would be easier to read if you eliminated one of the redundant
> >columns.
> >
> >10) in Table 1, some word breaks are missing from the Action on Expiry
> >column. Put a space between conditionally and CLE, and between each
> >and IEA.
> >
> >11) The acronym IEA is not defined before being used.
> >
> >12) t-maxsuppress has discussion of the value to use for an unreliable
> >transport; what is the recommended value for a reliable transport?
> >
> >13) section 4 title has extra spaces.
> >
> >
> >David Harrington
> >Director, IETF Transport Area
> >ietfdbh@comcast.net (preferred for ietf)
> >dbharrington@huaweisymantec.com
> >+1 603 828 1401 (cell)
> >
> >_______________________________________________
> >PCN mailing list
> >PCN@ietf.org
> >https://www.ietf.org/mailman/listinfo/pcn
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn


From tom111.taylor@bell.net  Tue Dec  7 05:44:39 2010
Return-Path: <tom111.taylor@bell.net>
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 481F83A6987 for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 05:44:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.742
X-Spam-Level: 
X-Spam-Status: No, score=-101.742 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 au98czbe8E+v for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 05:44:38 -0800 (PST)
Received: from blu0-omc2-s11.blu0.hotmail.com (blu0-omc2-s11.blu0.hotmail.com [65.55.111.86]) by core3.amsl.com (Postfix) with ESMTP id 5CEF83A677C for <pcn@ietf.org>; Tue,  7 Dec 2010 05:44:38 -0800 (PST)
Received: from BLU0-SMTP55 ([65.55.111.73]) by blu0-omc2-s11.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 7 Dec 2010 05:45:52 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP550A74017F5C045E23722FD82C0@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP55.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 7 Dec 2010 05:45:52 -0800
Date: Tue, 7 Dec 2010 08:45:53 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Georgios Karagiannis <karagian@cs.utwente.nl>
References: <MTmJvkts.1291707477.0672830.karagian@ewi.utwente.nl>
In-Reply-To: <MTmJvkts.1291707477.0672830.karagian@ewi.utwente.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Dec 2010 13:45:52.0465 (UTC) FILETIME=[10731C10:01CB9615]
Cc: "pcn@ietf.org" <pcn@ietf.org>
Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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, 07 Dec 2010 13:44:39 -0000

CL and SM edge behaviours have the following attributes in common:
  - decisions based on aggregate flow measurements
  - message transport independent of per-flow signalling (i.e., RSVP)

Your own proposal for the HOSE model shared those attributes, but was 
forestalled by the core behaviour the Working Group chose to adopt.

The piggybacked edge behaviour differs in the proposed transport, and 
Michael's proposal differs because it would use individual probes rather 
than aggregate measurements.

My sense of the matter is therefore that the text we provide for the SM 
and CL edge behaviours will not be greatly reusable for the most 
probable other edge behaviours that might be developed.

On 07/12/2010 2:37 AM, Georgios Karagiannis wrote:
> Dear David
>
> Thank you very much for the provided comments!
>
> Regarding the first comment, if it is to either merge the two documents,
> or merge and then again split the documents in three documents, then I
> am in favour of the latter one.
>
> One document could describe the common text, that will be the same for
> all edge behaviour drafts. Other two documents could then be related to
> CL and the to SM. These CL and SM documents could refer then to the
> common document.
>
> All new edge behaviour drafts should also use as much as possible the
> common document.
>
> Best regards,
> Georgios
>
...

From tom111.taylor@bell.net  Tue Dec  7 06:54:43 2010
Return-Path: <tom111.taylor@bell.net>
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 269493A6997 for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 06:54:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.745
X-Spam-Level: 
X-Spam-Status: No, score=-101.745 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 iSiAj85U7-q0 for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 06:54:41 -0800 (PST)
Received: from blu0-omc3-s38.blu0.hotmail.com (blu0-omc3-s38.blu0.hotmail.com [65.55.116.113]) by core3.amsl.com (Postfix) with ESMTP id AF8AB3A67A7 for <pcn@ietf.org>; Tue,  7 Dec 2010 06:54:41 -0800 (PST)
Received: from BLU0-SMTP65 ([65.55.116.72]) by blu0-omc3-s38.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 7 Dec 2010 06:56:06 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP65318F3CCA9217953772B6D82C0@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP65.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 7 Dec 2010 06:56:05 -0800
Date: Tue, 7 Dec 2010 09:56:07 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <FEF2029CCC614C6A80884469A91E0015@23FX1C1>
In-Reply-To: <FEF2029CCC614C6A80884469A91E0015@23FX1C1>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Dec 2010 14:56:06.0025 (UTC) FILETIME=[DFED5790:01CB961E]
Cc: pcn@ietf.org
Subject: Re: [PCN] AD Review: draft-ietf-pcn-cl-edge-behaviour-07
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/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, 07 Dec 2010 14:54:43 -0000

This one has some meatier issues. Responses below.

On 06/12/2010 3:56 PM, David Harrington wrote:
> Hi,
>
> Because this document has so much common text with the SM document,
> almost all the AD Review comments for the SM document apply to CL as
> well. Please incorporate those comments into this review.
>
> A few comments came to mind after sending the SM review, that apply to
> both; I added parenthesis to indictae it applies to both).
>
> 1) in section 2, reference is made to the "possible extension"
> [ID.PCN3in1].
> I recommend against referencing "possible extension" documents.

[PTT] Would it be OK to call it an example?
>
> 2) "These allowable transitions are specified here" - usually
> specified implies a normative specification. I suggest rewording with
> less normative-like wording.

[PTT] The point, of course, is not to specify the same thing in two 
places. However, it's probably legitimate to say that an extension 
suitable for the CL edge behaviour MUST conform to the following 
transitions ...
>
> 3) in 3.2.3, the calculation for CLE uses either the latest or the
> previous interval in its caculations. Niether SM nor CL explains why
> it is acceptable to use either interval. Is this explained somewhere?
> How does this affect interoperability? (also applies to SM)

[PTT] This is meant to be an inclusive OR, that is, the condition 2 MUST 
be satisfied for both intervals. I'll review wording.
>
> 4) in 3.3.2, the DP MUST request an estimate of pcn-sent-rate; is
> there a specific protocol that must/should be used to do this
> (assuming they are not co-located)? If not, how is this
> request/response done in a vendor-interoperable manner?

[PTT] Protocol development is outside the PCN charter. We do have a 
signalling requirements document in progress. I'll also mention that I 
was about to revive draft-fortune-dime-pcn-collection as one proposal 
for a PCN data collection protocol (using Diameter as an accounting 
application).
>
> 5) in 3.3.2, last paragraph, the list must be ETM-marked flows, right?
> It doesn't say that.
>
[PTT] I can mention it. 3.2.2 specifies that only ETM-marked flows are 
reported.

> 6) in 3.3., an alarm should be raised to management. is there are
> standardized approach to raising the alarm? If not, how does this
> affect interoperability. Most notably, if two nodes form different
> vendors raise an alarm using different protocols, how will the
> management system correlate the alarms? If two implementations use
> SNMP to raise the alarms, should they use consistent OIDs to identify
> the problem? or consistent syslog SDEs? or consistent ipfix IEs?
> Should the WG standardize the information models, and possibly data
> models and protocols, for reporting such alarms?

[PTT] To start with the last point, I can't see the WG specifying 
management protocols specifically to manage PCN -- this would be the 
tail wagging the dog. PCN is just one small part of managing a network, 
and I would think the operator would already have deployed their 
preferred tools. The best we could do is to ensure interoperability for 
each of the likely alternatives.
>
> 7) in 5.2, it is asserted that [ID.PCN3in1] specifies the behavior;
> but 2.2 mentions this as a "possible extension". If PCN3in1 is not
> STDS track, then i think this text in 5.2 could be problematic. But I
> suspect that 3086 expects a stable specification.
>
[PTT] [ID.PCN3in1] is currently Experimental. I can't remember if the 
plan is to reclassify it as Standards Track now that RFC 6040 has been 
published as Proposed Standard. Perhaps Toby or Bob could comment.

> I have not worked with the 3086 template before. Is a reference to a
> number of RFCs, without any discussion of their details really
> sufficient? It doesn't sounce like that meets the description from
> 3086:
>
>     This section specifies the rules or guidelines to create this PDB,
>     each distinguished with "may", "must" and "should." The technical
>     specification must list the classification and traffic conditioning
>     required (if any) and the PHB (or PHBs) to be used with any
>     additional requirements on their configuration beyond that
> contained
>     in RFCs.  Classification can reflect the results of an admission
>     control process.  Traffic conditioning may include marking, traffic
>     shaping, and policing.  A Service Provisioning Policy might be used
>     to describe the technical specification of a particular PDB.

[PTT] I'll look for an example to follow.
>
> 8) in 5.7, the reader is referred to "the applicable specifications";
> can we identify the applicable specifications?
>
> David Harrington
> Director, IETF Transport Area
> ietfdbh@comcast.net (preferred for ietf)
> dbharrington@huaweisymantec.com
> +1 603 828 1401 (cell)
>
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>
>

From karagian@cs.utwente.nl  Tue Dec  7 10:33:17 2010
Return-Path: <karagian@cs.utwente.nl>
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 59EEF3A6881 for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 10:33:17 -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 qSSAvKdc9WYE for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 10:33:15 -0800 (PST)
Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11]) by core3.amsl.com (Postfix) with ESMTP id 0B8783A6863 for <pcn@ietf.org>; Tue,  7 Dec 2010 10:33:14 -0800 (PST)
Received: from webmail.cs.utwente.nl (janus.ewi.utwente.nl [130.89.10.26]) by denhaag.ewi.utwente.nl (8.13.6/8.13.6) with SMTP id oB7IYO11010985;  Tue, 7 Dec 2010 19:34:24 +0100 (MET)
Received: from 84.82.109.231 (auth. user karagian@imap1.ewi.utwente.nl) by webmail.cs.utwente.nl with HTTP; Tue, 07 Dec 2010 18:34:25 +0000
To: "Tom Taylor" <tom111.taylor@bell.net>
Date: Tue, 07 Dec 2010 18:34:25 +0000
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <ABvzcw5Y.1291746865.1628450.karagian@ewi.utwente.nl>
In-Reply-To: <BLU0-SMTP550A74017F5C045E23722FD82C0@phx.gbl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Errors-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (denhaag.ewi.utwente.nl [130.89.10.11]); Tue, 07 Dec 2010 19:34:33 +0100 (MET)
Cc: "pcn@ietf.org" <pcn@ietf.org>
Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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, 07 Dec 2010 18:33:17 -0000

Hi Tom


Please do not include the HOSE model in the discussions, since this edge
behaviour draft is out of the scope of the PCN WG.

Regarding the other comments, if we use a common draft, then this draft
should describe the common terminology and the attributes associated
with the aggregated congestion and pre-congestion information from
within the domain, see also PCN charter:

"The Congestion and Pre-Congestion Notification (PCN) working group
develops mechanisms to protect the quality-of-service of established
inelastic flows within a DiffServ domain when congestion is imminent
or existing. These mechanisms operate at the domain boundary, based
on aggregated congestion and pre-congestion information from within
the domain."

Moreover, I do think that it is problematic to describe the SM and CL in
the same document. This is because the SM and CL edge behaviour drafts
differ severely on the assumed core network behaviour, see below (text
copied from the CL and SM drafts).
This will severely impact the clarity of the CL and SM specifications and
the clarity of their applicability.

Therefore, I think that these two specifications should be described in
two separate documents.

-----------------------------------------
2.  Assumed Core Network Behaviour for SM

   This section describes the assumed behaviour for nodes of the PCN-
   domain when acting in their role as PCN-interior-nodes.  The SM mode
   of operation assumes that:

   o  PCN-interior-nodes perform excess-traffic-marking of packets
      according to the rules specified in [RFC5670].

   o  excess-traffic-marking of packets uses the PCN-Marked (PM)
      codepoint defined in [RFC5696];

   o  on each link the reference rate for the excess-traffic-meter is
      configured with a PCN-excess-rate to be equal to the PCN-
      admissible-rate for the link;

-------------------------------------

2.  Assumed Core Network Behaviour for CL

   This section describes the assumed behaviour for nodes of the PCN-
   domain when acting in their role as PCN-interior-nodes.  The CL mode
   of operation assumes that:

   o  PCN-interior-nodes perform threshold-marking and excess-traffic-
      marking of packets according to the rules specified in [RFC5670],
      and any additional rules specified in the applicable encoding
      extension document;

   o  encoding of PCN status within individual packets is based on
      [RFC5696], extended to provide a third PCN encoding state.  A
      possible extension is documented in [ID.PCN3in1];

   o  the PCN-domain satisfies the conditions specified in the
      applicable encoding extension document;


   o  on each link the reference rate for the threshold-meter is
      configured to be equal to the PCN-admissible-rate for the link;

   o  on each link the reference rate for the excess traffic meter is
      configured to be equal to the PCN-supportable-rate for the link;

   According to [RFC5696], the encoding extension documents should
   specify the allowable transitions between marking states.  However,
   to be absolutely clear, these allowable transitions are specified
   here.  At any interior node, the only permitted transitions are
   these:

   o  a PCN-packet that is not-marked (NM) MAY be threshold-marked (ThM)
      or excess-traffic-marked (ETM);

   o  a PCN-packet that is threshold-marked (ThM) MAY be excess-traffic-
      marked (ETM).

   An interior node MUST NOT perform any of the following:

   o  re-mark a packet from PCN to non-PCN, or from non-PCN to PCN;

   o  re-mark a PCN-packet from threshold-marked (ThM) to not-marked
      (NM);

   o  re-mark a PCN-packet from excess-traffic-marked (ETM) to not-
      marked (NM) or threshold-marked (ThM).

---------------------

Best regards,
Georgios


On 12/7/2010, "Tom Taylor" <tom111.taylor@bell.net> wrote:

>CL and SM edge behaviours have the following attributes in common:
>  - decisions based on aggregate flow measurements
>  - message transport independent of per-flow signalling (i.e., RSVP)
>
>Your own proposal for the HOSE model shared those attributes, but was
>forestalled by the core behaviour the Working Group chose to adopt.
>
>The piggybacked edge behaviour differs in the proposed transport, and
>Michael's proposal differs because it would use individual probes rather
>than aggregate measurements.
>
>My sense of the matter is therefore that the text we provide for the SM
>and CL edge behaviours will not be greatly reusable for the most
>probable other edge behaviours that might be developed.
>
>On 07/12/2010 2:37 AM, Georgios Karagiannis wrote:
>> Dear David
>>
>> Thank you very much for the provided comments!
>>
>> Regarding the first comment, if it is to either merge the two documents,
>> or merge and then again split the documents in three documents, then I
>> am in favour of the latter one.
>>
>> One document could describe the common text, that will be the same for
>> all edge behaviour drafts. Other two documents could then be related to
>> CL and the to SM. These CL and SM documents could refer then to the
>> common document.
>>
>> All new edge behaviour drafts should also use as much as possible the
>> common document.
>>
>> Best regards,
>> Georgios
>>
>...

From tom111.taylor@bell.net  Tue Dec  7 12:01:49 2010
Return-Path: <tom111.taylor@bell.net>
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 1E4B73A6891 for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 12:01:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.747
X-Spam-Level: 
X-Spam-Status: No, score=-101.747 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 ncxdkfWeOHIT for <pcn@core3.amsl.com>; Tue,  7 Dec 2010 12:01:48 -0800 (PST)
Received: from blu0-omc2-s20.blu0.hotmail.com (blu0-omc2-s20.blu0.hotmail.com [65.55.111.95]) by core3.amsl.com (Postfix) with ESMTP id 4B8DF3A69B3 for <pcn@ietf.org>; Tue,  7 Dec 2010 12:01:46 -0800 (PST)
Received: from BLU0-SMTP65 ([65.55.111.72]) by blu0-omc2-s20.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 7 Dec 2010 12:01:49 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP65D7019C6CE1EAFAC49247D82C0@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP65.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 7 Dec 2010 12:01:48 -0800
Date: Tue, 7 Dec 2010 15:01:50 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Georgios Karagiannis <karagian@cs.utwente.nl>
References: <ABvzcw5Y.1291746865.1628450.karagian@ewi.utwente.nl>
In-Reply-To: <ABvzcw5Y.1291746865.1628450.karagian@ewi.utwente.nl>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Dec 2010 20:01:49.0197 (UTC) FILETIME=[954F43D0:01CB9649]
Cc: "pcn@ietf.org" <pcn@ietf.org>
Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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, 07 Dec 2010 20:01:49 -0000

I'm working up a combined document, which I will first submit as an 
individual draft to see if it meets WG approval. The intention is that 
there will be no change to technical content aside from responding to 
any technical comments David made. I have finished the core assumptions 
section, and I actually think this is pretty clear. I'm more worried 
about the other parts of the document.

The combined document has too many authors. I've left myself in to 
expedite the submission process, but my intention is to leave an note to 
the RFC Editor relegating me to the Contributors section at the point of 
publication if they want to cut back.

On 07/12/2010 1:34 PM, Georgios Karagiannis wrote:
> Hi Tom
>
>
> Please do not include the HOSE model in the discussions, since this edge
> behaviour draft is out of the scope of the PCN WG.
>
> Regarding the other comments, if we use a common draft, then this draft
> should describe the common terminology and the attributes associated
> with the aggregated congestion and pre-congestion information from
> within the domain, see also PCN charter:
>
> "The Congestion and Pre-Congestion Notification (PCN) working group
> develops mechanisms to protect the quality-of-service of established
> inelastic flows within a DiffServ domain when congestion is imminent
> or existing. These mechanisms operate at the domain boundary, based
> on aggregated congestion and pre-congestion information from within
> the domain."
>
> Moreover, I do think that it is problematic to describe the SM and CL in
> the same document. This is because the SM and CL edge behaviour drafts
> differ severely on the assumed core network behaviour, see below (text
> copied from the CL and SM drafts).
> This will severely impact the clarity of the CL and SM specifications and
> the clarity of their applicability.
>
> Therefore, I think that these two specifications should be described in
> two separate documents.
>
...

From toby@moncaster.com  Wed Dec  8 06:17:59 2010
Return-Path: <toby@moncaster.com>
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 AD98D3A68CB for <pcn@core3.amsl.com>; Wed,  8 Dec 2010 06:17:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 MEm-3YPdea38 for <pcn@core3.amsl.com>; Wed,  8 Dec 2010 06:17:58 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by core3.amsl.com (Postfix) with ESMTP id 45F543A6783 for <pcn@ietf.org>; Wed,  8 Dec 2010 06:17:53 -0800 (PST)
Received: from TobysHP (host86-133-99-139.range86-133.btcentralplus.com [86.133.99.139]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MHttJ-1PMlxb1Z6L-003YWt; Wed, 08 Dec 2010 15:19:18 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'Tom Taylor'" <tom111.taylor@bell.net>
References: <ABvzcw5Y.1291746865.1628450.karagian@ewi.utwente.nl> <BLU0-SMTP65D7019C6CE1EAFAC49247D82C0@phx.gbl>
In-Reply-To: <BLU0-SMTP65D7019C6CE1EAFAC49247D82C0@phx.gbl>
Date: Wed, 8 Dec 2010 14:19:20 -0000
Message-ID: <002901cb96e2$e7e79400$b7b6bc00$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcuWScmk54EhZR1pRbKZK6D8vivqhwAmJZ7A
Content-language: en-gb
X-Provags-ID: V02:K0:7Gs8Zeedvjqc3Mbf/Sj0Rii93L6YwHLxL/+KrPWuC6i euXDoEQGxF5LtGNd0fGACIeO2q7S5i0XR0RpX84m/jSCjlt9dY 45D7gQJ16E0qBCFFf/fhExLjX/hTyAcYoysF/cmMhXezP7OUzH xLiSjvFGuFwFBDRK23hBWg1NTeaRUKFT+nGqXoazkuwWuCPu4n 7g1U+TyG+5/6pGYXa+TnNJGYtNem+Ghglvy34mn6OY=
Cc: pcn@ietf.org
Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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: Wed, 08 Dec 2010 14:17:59 -0000

Hi Tom,

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Tom Taylor
> Sent: 07 December 2010 20:02
> To: Georgios Karagiannis
> Cc: pcn@ietf.org
> Subject: Re: [PCN] AD Review: draft-ietf-pcn-sm-edge-behaviour-04
> 
> I'm working up a combined document, which I will first submit as an
> individual draft to see if it meets WG approval. The intention is that
> there will be no change to technical content aside from responding to
> any technical comments David made. I have finished the core assumptions
> section, and I actually think this is pretty clear. I'm more worried
> about the other parts of the document.

As I said in an earlier response, the big issue is phrasing it so as to
clarify the MUSTs, SHOULDs, etc as they relate to each of the edge
behaviours...

If you want a review of stuff as you're writing it I hopefully will have
some time (and it shouldn't take me too long to reload context on PCN!). 

> 
> The combined document has too many authors. I've left myself in to
> expedite the submission process, but my intention is to leave an note
> to
> the RFC Editor relegating me to the Contributors section at the point
> of
> publication if they want to cut back.

My own view would be that you should be listed as the main editor (as you
will have done a heck of a lot of work on the combined document). The
Contributors section can then make it clear that the document is a merger of
2 drafts and list the authors of those two drafts.

Toby

> 
> On 07/12/2010 1:34 PM, Georgios Karagiannis wrote:
> > Hi Tom
> >
> >
> > Please do not include the HOSE model in the discussions, since this
> edge
> > behaviour draft is out of the scope of the PCN WG.
> >
> > Regarding the other comments, if we use a common draft, then this
> draft
> > should describe the common terminology and the attributes associated
> > with the aggregated congestion and pre-congestion information from
> > within the domain, see also PCN charter:
> >
> > "The Congestion and Pre-Congestion Notification (PCN) working group
> > develops mechanisms to protect the quality-of-service of established
> > inelastic flows within a DiffServ domain when congestion is imminent
> > or existing. These mechanisms operate at the domain boundary, based
> > on aggregated congestion and pre-congestion information from within
> > the domain."
> >
> > Moreover, I do think that it is problematic to describe the SM and CL
> in
> > the same document. This is because the SM and CL edge behaviour
> drafts
> > differ severely on the assumed core network behaviour, see below
> (text
> > copied from the CL and SM drafts).
> > This will severely impact the clarity of the CL and SM specifications
> and
> > the clarity of their applicability.
> >
> > Therefore, I think that these two specifications should be described
> in
> > two separate documents.
> >
> ...
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn


From tom111.taylor@bell.net  Thu Dec  9 09:44:47 2010
Return-Path: <tom111.taylor@bell.net>
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 A448528C13E for <pcn@core3.amsl.com>; Thu,  9 Dec 2010 09:44:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.753
X-Spam-Level: 
X-Spam-Status: No, score=-101.753 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 0FvPUhsjQ5-i for <pcn@core3.amsl.com>; Thu,  9 Dec 2010 09:44:47 -0800 (PST)
Received: from blu0-omc3-s16.blu0.hotmail.com (blu0-omc3-s16.blu0.hotmail.com [65.55.116.91]) by core3.amsl.com (Postfix) with ESMTP id C0D2E28C122 for <pcn@ietf.org>; Thu,  9 Dec 2010 09:44:46 -0800 (PST)
Received: from BLU0-SMTP70 ([65.55.116.72]) by blu0-omc3-s16.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 9 Dec 2010 09:46:16 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP70A674EAD36599A53B190AD82E0@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP70.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 9 Dec 2010 09:46:15 -0800
Date: Thu, 9 Dec 2010 12:46:17 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: pcn <pcn@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Dec 2010 17:46:15.0294 (UTC) FILETIME=[F9F3A9E0:01CB97C8]
Subject: [PCN] Showstopper for merger of PCN SM and CL drafts
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/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: Thu, 09 Dec 2010 17:44:48 -0000

I have just been reading a review that Toby Moncaster kindly provided 
for my proposed new merged SM + CL draft. It's that prickly issue of how 
to refer to [I-D.3in1]. The trouble is that [I-D.3in1] looks to be 
headed for Experimental track for the time being. This raises some sort 
of distinction between SM and CL, though I'm not quite sure what the 
significance is given that the edge behaviour drafts are Informational. 
Anyway, I suspect the difference means that SM and CL should be 
documented in separate drafts.

I'll look for some other way to fix the problem David identified. At the 
least, I'll clean up the unnecessary editorial differences. I wonder if 
it would work to put a marker in at each spot where the drafts must 
necessarily differ, for instance, by adding the phrase "For the SM 
boundary node behaviour", or "For the SM boundary node behaviour", as 
the case may be. I could also have an introductory note explaining that 
the two drafts are very similar and explaining the use of this marker.

Does this sound reasonable to you, David?

Tom Taylor

From toby@moncaster.com  Thu Dec  9 09:59:41 2010
Return-Path: <toby@moncaster.com>
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 7B2AB28C136 for <pcn@core3.amsl.com>; Thu,  9 Dec 2010 09:59:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 O5iU8vDb7CyV for <pcn@core3.amsl.com>; Thu,  9 Dec 2010 09:59:40 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by core3.amsl.com (Postfix) with ESMTP id 6777028C134 for <pcn@ietf.org>; Thu,  9 Dec 2010 09:59:40 -0800 (PST)
Received: from TobysHP (host86-141-37-244.range86-141.btcentralplus.com [86.141.37.244]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0LfnrC-1QG37X0ZD8-00ok50; Thu, 09 Dec 2010 19:01:09 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'Tom Taylor'" <tom111.taylor@bell.net>, "'pcn'" <pcn@ietf.org>
References: <BLU0-SMTP70A674EAD36599A53B190AD82E0@phx.gbl>
In-Reply-To: <BLU0-SMTP70A674EAD36599A53B190AD82E0@phx.gbl>
Date: Thu, 9 Dec 2010 18:01:09 -0000
Message-ID: <001f01cb97cb$0f63dff0$2e2b9fd0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcuXyP1aL3deIyMGQ8q/+uoUYT3UIwAANirg
Content-Language: en-gb
X-Provags-ID: V02:K0:fYs94fr7AyrVFtDTEUoRTF0pUAuHCfthCsdlyuEA/C1 70GoWe0iOUPBcv2XAj0rojku2o8Yf8LiyCnuQQ1TS4UYutiCyg FC1qN9wYHyNud5M5DiJ0Nb9bhlLiU46O1zZfx/57SdkOLyyC1b YP6R2/7V2mXBcnkXGF2jsS/1ov/itIvisF/yB3/JiCN1GbpeuM KHmt45T2cl5jYzKj1R7cesmaLf1+9ql9SUXUAXCkDs=
Subject: Re: [PCN] Showstopper for merger of PCN SM and CL drafts
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/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: Thu, 09 Dec 2010 17:59:41 -0000

One possible (though not entirely elegant) solution to the 3-in-1 problem
would be to summarise 3-in-1 within this document in a very brief manner.
This could be as simple as:

"CL edge behaviour requires an additional PCN-codepoint to carry the
ThM-marking. This could be provided by utilising the EXP codepoint defined
in RFC5696, following the rules set out in section 5 of that document."

Really it doesn't matter how the PCN-markings are encoded. All that matters
is that CL requires there to be an additional marking state... And if these
are INFO documents then it may be less of an issue still (as we won't be
standardising anything "through the back door").

As far as I can see we have 3 things here: stuff that is common to both edge
behaviours; stuff that is common, but where the details differ (calculating
CLE is an obvious example); stuff that only applies to CL. That suggests to
me that we could write the document in two halfs. The first part specifies
SM, but with markers for where CL differs. The second part then specifies
the differences.

Toby

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Tom Taylor
> Sent: 09 December 2010 17:46
> To: pcn
> Subject: [PCN] Showstopper for merger of PCN SM and CL drafts
> 
> I have just been reading a review that Toby Moncaster kindly provided
> for my proposed new merged SM + CL draft. It's that prickly issue of
> how
> to refer to [I-D.3in1]. The trouble is that [I-D.3in1] looks to be
> headed for Experimental track for the time being. This raises some sort
> of distinction between SM and CL, though I'm not quite sure what the
> significance is given that the edge behaviour drafts are Informational.
> Anyway, I suspect the difference means that SM and CL should be
> documented in separate drafts.
> 
> I'll look for some other way to fix the problem David identified. At
> the
> least, I'll clean up the unnecessary editorial differences. I wonder if
> it would work to put a marker in at each spot where the drafts must
> necessarily differ, for instance, by adding the phrase "For the SM
> boundary node behaviour", or "For the SM boundary node behaviour", as
> the case may be. I could also have an introductory note explaining that
> the two drafts are very similar and explaining the use of this marker.
> 
> Does this sound reasonable to you, David?
> 
> Tom Taylor
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn


From menth@informatik.uni-tuebingen.de  Thu Dec  9 12:37:45 2010
Return-Path: <menth@informatik.uni-tuebingen.de>
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 014773A6BB6 for <pcn@core3.amsl.com>; Thu,  9 Dec 2010 12:37:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.047
X-Spam-Level: 
X-Spam-Status: No, score=-0.047 tagged_above=-999 required=5 tests=[AWL=0.754,  BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448]
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 FbsxdoKN1NkZ for <pcn@core3.amsl.com>; Thu,  9 Dec 2010 12:37:43 -0800 (PST)
Received: from mx3.informatik.uni-tuebingen.de (mx3.Informatik.Uni-Tuebingen.De [134.2.12.26]) by core3.amsl.com (Postfix) with SMTP id 697CB3A69B3 for <pcn@ietf.org>; Thu,  9 Dec 2010 12:37:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx3.informatik.uni-tuebingen.de (Postfix) with ESMTP id EE2A952B3 for <pcn@ietf.org>; Thu,  9 Dec 2010 21:39:09 +0100 (MET)
X-Virus-Scanned: amavisd-new at informatik.uni-tuebingen.de
Received: from mx3.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx3.informatik.uni-tuebingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o3j6DnyxQqIc for <pcn@ietf.org>; Thu,  9 Dec 2010 21:39:04 +0100 (MET)
Received: from zcs-pu.informatik.uni-tuebingen.de (zcs-pu.Informatik.Uni-Tuebingen.De [134.2.12.61]) by mx3.informatik.uni-tuebingen.de (Postfix) with ESMTP id 940F952A3 for <pcn@ietf.org>; Thu,  9 Dec 2010 21:39:04 +0100 (MET)
Received: from [192.168.1.100] (HSI-KBW-095-208-114-108.hsi5.kabel-badenwuerttemberg.de [95.208.114.108]) by zcs-pu.informatik.uni-tuebingen.de (Postfix) with ESMTP id 0AFA0C05387 for <pcn@ietf.org>; Thu,  9 Dec 2010 21:39:03 +0100 (CET)
Message-ID: <4D013E6A.8040202@informatik.uni-tuebingen.de>
Date: Thu, 09 Dec 2010 21:39:06 +0100
From: Michael Menth <menth@informatik.uni-tuebingen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: pcn@ietf.org
References: <BLU0-SMTP70A674EAD36599A53B190AD82E0@phx.gbl> <001f01cb97cb$0f63dff0$2e2b9fd0$@com>
In-Reply-To: <001f01cb97cb$0f63dff0$2e2b9fd0$@com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PCN] Showstopper for merger of PCN SM and CL drafts
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/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: Thu, 09 Dec 2010 20:37:45 -0000

Hi Tom, hi David, hi Toby, and all,

Am 09.12.2010 19:01, schrieb Toby Moncaster:
> One possible (though not entirely elegant) solution to the 3-in-1 probl=
em
> would be to summarise 3-in-1 within this document in a very brief manne=
r.
> This could be as simple as:
>
> "CL edge behaviour requires an additional PCN-codepoint to carry the
> ThM-marking. This could be provided by utilising the EXP codepoint defi=
ned
> in RFC5696, following the rules set out in section 5 of that document."
>
> Really it doesn't matter how the PCN-markings are encoded. All that mat=
ters
> is that CL requires there to be an additional marking state... And if t=
hese
> are INFO documents then it may be less of an issue still (as we won't b=
e
> standardising anything "through the back door").
>
> As far as I can see we have 3 things here: stuff that is common to both=
 edge
> behaviours; stuff that is common, but where the details differ (calcula=
ting
> CLE is an obvious example); stuff that only applies to CL. That suggest=
s to
> me that we could write the document in two halfs. The first part specif=
ies
> SM, but with markers for where CL differs. The second part then specifi=
es
> the differences.

I fear that a description of CL based on differences to SM makes CL=20
unnecessarily difficult to understand. That's why I do not think that=20
this is a good approach, if I have understood it correctly. Apart from=20
that, I find CL is even easier to understand than SM and explaining=20
first the difficult method and then the simple one is not very efficient.

Apart from that, CL and SM are two incompatible approaches: it is not=20
possible to run both of them in a single network. That might be another=20
reason why they deserve to be described in two separate documents. It's=20
a bit like two- and three-rate color marking (RFC 2697 and RFC 2698).=20
They are different and it is much easier to express that by referring to=20
two different RFC numbers.

Regards,

     Michael

> Toby
>
>> -----Original Message-----
>> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
>> Tom Taylor
>> Sent: 09 December 2010 17:46
>> To: pcn
>> Subject: [PCN] Showstopper for merger of PCN SM and CL drafts
>>
>> I have just been reading a review that Toby Moncaster kindly provided
>> for my proposed new merged SM + CL draft. It's that prickly issue of
>> how
>> to refer to [I-D.3in1]. The trouble is that [I-D.3in1] looks to be
>> headed for Experimental track for the time being. This raises some sor=
t
>> of distinction between SM and CL, though I'm not quite sure what the
>> significance is given that the edge behaviour drafts are Informational=
.
>> Anyway, I suspect the difference means that SM and CL should be
>> documented in separate drafts.
>>
>> I'll look for some other way to fix the problem David identified. At
>> the
>> least, I'll clean up the unnecessary editorial differences. I wonder i=
f
>> it would work to put a marker in at each spot where the drafts must
>> necessarily differ, for instance, by adding the phrase "For the SM
>> boundary node behaviour", or "For the SM boundary node behaviour", as
>> the case may be. I could also have an introductory note explaining tha=
t
>> the two drafts are very similar and explaining the use of this marker.
>>
>> Does this sound reasonable to you, David?
>>
>> Tom Taylor
>> _______________________________________________
>> PCN mailing list
>> PCN@ietf.org
>> https://www.ietf.org/mailman/listinfo/pcn
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn

--=20
Prof. Dr. habil. Michael Menth
University of Tuebingen
Wilhelm-Schickard-Institute
Lehrstuhl f=FCr Rechnernetze und Internet
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70505, fax: (+49)-7071/29-5220
mailto:menth@uni-tuebingen.de, http://www.net2.uni-tuebingen.de


From karagian@cs.utwente.nl  Fri Dec 10 03:19:07 2010
Return-Path: <karagian@cs.utwente.nl>
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 E34063A6824 for <pcn@core3.amsl.com>; Fri, 10 Dec 2010 03:19:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.227
X-Spam-Level: 
X-Spam-Status: No, score=0.227 tagged_above=-999 required=5 tests=[AWL=0.732,  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 dlYpcCua3E+g for <pcn@core3.amsl.com>; Fri, 10 Dec 2010 03:19:04 -0800 (PST)
Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11]) by core3.amsl.com (Postfix) with ESMTP id AFCBC3A68AC for <pcn@ietf.org>; Fri, 10 Dec 2010 03:19:03 -0800 (PST)
Received: from ewi977 (ewi977.ewi.utwente.nl [130.89.12.129]) by denhaag.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id oBABKJ2M018148;  Fri, 10 Dec 2010 12:20:22 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Michael Menth'" <menth@informatik.uni-tuebingen.de>, <pcn@ietf.org>
References: <BLU0-SMTP70A674EAD36599A53B190AD82E0@phx.gbl><001f01cb97cb$0f63dff0$2e2b9fd0$@com> <4D013E6A.8040202@informatik.uni-tuebingen.de>
Date: Fri, 10 Dec 2010 12:20:15 +0100
Message-ID: <212004E222964213985AC2075A7BBE61@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4D013E6A.8040202@informatik.uni-tuebingen.de>
thread-index: AcuX4SjpvaW8cpVHQlWJpParOm4gqgAeitSw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (denhaag.ewi.utwente.nl [130.89.10.11]); Fri, 10 Dec 2010 12:20:32 +0100 (MET)
Subject: Re: [PCN] Showstopper for merger of PCN SM and CL drafts
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/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: Fri, 10 Dec 2010 11:19:08 -0000

Hi all=20

I also agree with Michael and Tom that the CL and SM drafts sould be
specified in different documents.

 In addition to the listed arguments, I think that the functionalities =
and
assumptions used by CL and SM=20
 PCN edge behaviour drafts are very different.

 In particular, they differ severely on the assumed core network=20
 behaviour, see below (text copied from the CL and SM drafts).
 If they are merged, then this will severely impact the clarity of the=20
 CL and SM specifications and the clarity of their applicability.
=20
=20
 Therefore, I think that these two specifications should be described=20
 in two separate documents.
=20
 -----------------------------------------
 2. Assumed Core Network Behaviour for SM
=20
    This section describes the assumed behaviour for nodes of the PCN-
    domain when acting in their role as PCN-interior-nodes. The SM mode
    of operation assumes that:
=20
    o PCN-interior-nodes perform excess-traffic-marking of packets
       according to the rules specified in [RFC5670].
=20
    o excess-traffic-marking of packets uses the PCN-Marked (PM)
       codepoint defined in [RFC5696];
=20
    o on each link the reference rate for the excess-traffic-meter is
       configured with a PCN-excess-rate to be equal to the PCN-
       admissible-rate for the link;

 -------------------------------------
=20
 2. Assumed Core Network Behaviour for CL
=20
    This section describes the assumed behaviour for nodes of the PCN-
    domain when acting in their role as PCN-interior-nodes. The CL mode
    of operation assumes that:
=20
    o PCN-interior-nodes perform threshold-marking and excess-traffic-
       marking of packets according to the rules specified in [RFC5670],
       and any additional rules specified in the applicable encoding
       extension document;
=20
    o encoding of PCN status within individual packets is based on
       [RFC5696], extended to provide a third PCN encoding state. A
       possible extension is documented in [ID.PCN3in1];
=20
    o the PCN-domain satisfies the conditions specified in the
       applicable encoding extension document;
=20
=20
    o on each link the reference rate for the threshold-meter is
       configured to be equal to the PCN-admissible-rate for the link;
=20
    o on each link the reference rate for the excess traffic meter is
       configured to be equal to the PCN-supportable-rate for the link;
=20
    According to [RFC5696], the encoding extension documents should
    specify the allowable transitions between marking states. However,
    to be absolutely clear, these allowable transitions are specified
    here. At any interior node, the only permitted transitions are
    these:
=20
    o a PCN-packet that is not-marked (NM) MAY be threshold-marked (ThM)
       or excess-traffic-marked (ETM);
=20
    o a PCN-packet that is threshold-marked (ThM) MAY be excess-traffic-
       marked (ETM).
=20
    An interior node MUST NOT perform any of the following:
    o re-mark a packet from PCN to non-PCN, or from non-PCN to PCN;
=20
    o re-mark a PCN-packet from threshold-marked (ThM) to not-marked
       (NM);
=20
    o re-mark a PCN-packet from excess-traffic-marked (ETM) to not-
      marked (NM) or threshold-marked (ThM).
=20
---------------------=20

Best regards,
Georgios


> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On=20
> Behalf Of Michael Menth
> Sent: donderdag 9 december 2010 21:39
> To: pcn@ietf.org
> Subject: Re: [PCN] Showstopper for merger of PCN SM and CL drafts
>=20
> Hi Tom, hi David, hi Toby, and all,
>=20
> Am 09.12.2010 19:01, schrieb Toby Moncaster:
> > One possible (though not entirely elegant) solution to the 3-in-1=20
> > problem would be to summarise 3-in-1 within this document=20
> in a very brief manner.
> > This could be as simple as:
> >
> > "CL edge behaviour requires an additional PCN-codepoint to=20
> carry the=20
> > ThM-marking. This could be provided by utilising the EXP codepoint=20
> > defined in RFC5696, following the rules set out in section=20
> 5 of that document."
> >
> > Really it doesn't matter how the PCN-markings are encoded. All that=20
> > matters is that CL requires there to be an additional=20
> marking state...=20
> > And if these are INFO documents then it may be less of an=20
> issue still=20
> > (as we won't be standardising anything "through the back door").
> >
> > As far as I can see we have 3 things here: stuff that is common to=20
> > both edge behaviours; stuff that is common, but where the details=20
> > differ (calculating CLE is an obvious example); stuff that only=20
> > applies to CL. That suggests to me that we could write the=20
> document in=20
> > two halfs. The first part specifies SM, but with markers=20
> for where CL=20
> > differs. The second part then specifies the differences.
>=20
> I fear that a description of CL based on differences to SM=20
> makes CL unnecessarily difficult to understand. That's why I=20
> do not think that this is a good approach, if I have=20
> understood it correctly. Apart from that, I find CL is even=20
> easier to understand than SM and explaining first the=20
> difficult method and then the simple one is not very efficient.
>=20
> Apart from that, CL and SM are two incompatible approaches:=20
> it is not possible to run both of them in a single network.=20
> That might be another reason why they deserve to be described=20
> in two separate documents. It's a bit like two- and=20
> three-rate color marking (RFC 2697 and RFC 2698).=20
> They are different and it is much easier to express that by=20
> referring to two different RFC numbers.
>=20
> Regards,
>=20
>      Michael
>=20
> > Toby
> >
> >> -----Original Message-----
> >> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org]=20
> On Behalf Of=20
> >> Tom Taylor
> >> Sent: 09 December 2010 17:46
> >> To: pcn
> >> Subject: [PCN] Showstopper for merger of PCN SM and CL drafts
> >>
> >> I have just been reading a review that Toby Moncaster=20
> kindly provided=20
> >> for my proposed new merged SM + CL draft. It's that=20
> prickly issue of=20
> >> how to refer to [I-D.3in1]. The trouble is that [I-D.3in1]=20
> looks to=20
> >> be headed for Experimental track for the time being. This=20
> raises some=20
> >> sort of distinction between SM and CL, though I'm not=20
> quite sure what=20
> >> the significance is given that the edge behaviour drafts are=20
> >> Informational.
> >> Anyway, I suspect the difference means that SM and CL should be=20
> >> documented in separate drafts.
> >>
> >> I'll look for some other way to fix the problem David=20
> identified. At=20
> >> the least, I'll clean up the unnecessary editorial differences. I=20
> >> wonder if it would work to put a marker in at each spot where the=20
> >> drafts must necessarily differ, for instance, by adding the phrase=20
> >> "For the SM boundary node behaviour", or "For the SM boundary node=20
> >> behaviour", as the case may be. I could also have an introductory=20
> >> note explaining that the two drafts are very similar and=20
> explaining=20
> >> the use of this marker.
> >>
> >> Does this sound reasonable to you, David?
> >>
> >> Tom Taylor
> >> _______________________________________________
> >> PCN mailing list
> >> PCN@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pcn
> > _______________________________________________
> > PCN mailing list
> > PCN@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcn
>=20
> --
> Prof. Dr. habil. Michael Menth
> University of Tuebingen
> Wilhelm-Schickard-Institute
> Lehrstuhl f=FCr Rechnernetze und Internet
> Sand 13, 72076 Tuebingen, Germany
> phone: (+49)-7071/29-70505, fax: (+49)-7071/29-5220=20
> mailto:menth@uni-tuebingen.de, http://www.net2.uni-tuebingen.de
>=20
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>=20



From toby@moncaster.com  Fri Dec 10 08:28:05 2010
Return-Path: <toby@moncaster.com>
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 2754928C0D6 for <pcn@core3.amsl.com>; Fri, 10 Dec 2010 08:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 mY6ve-geqJEt for <pcn@core3.amsl.com>; Fri, 10 Dec 2010 08:28:03 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by core3.amsl.com (Postfix) with ESMTP id 3A78628C0E0 for <pcn@ietf.org>; Fri, 10 Dec 2010 08:28:02 -0800 (PST)
Received: from TobysHP ([86.141.37.244]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0MIxJ3-1PTZkr1etV-00342X; Fri, 10 Dec 2010 17:29:33 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'Michael Menth'" <menth@informatik.uni-tuebingen.de>, <pcn@ietf.org>
References: <BLU0-SMTP70A674EAD36599A53B190AD82E0@phx.gbl>	<001f01cb97cb$0f63dff0$2e2b9fd0$@com> <4D013E6A.8040202@informatik.uni-tuebingen.de>
In-Reply-To: <4D013E6A.8040202@informatik.uni-tuebingen.de>
Date: Fri, 10 Dec 2010 16:29:24 -0000
Message-ID: <002901cb9887$68c0e4f0$3a42aed0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcuX4ScfB4Rv/0x+Qeiymus051ItcwApMm2g
Content-Language: en-gb
X-Provags-ID: V02:K0:VU/k2jC56aSgWswklAoXyn5AfktV/v3S32lAlFvAPa5 F2WMu7PmFQwwAsYYU474EguRQf32+TbSf1ZE1iUarZh76+j6wQ MMwU+DQhwYtUDGYMAn8pKDWXY1Josh7/b4yo/FM8i8i5v0TMtt zxq+veev5e1fYSM4jPb/U0xXV3jwqqGppJ+ZxfVJkbTlukcp9j /mLrVdczkhQSUI+GOqlZHonWmaB3U7wGIKtsJjuAKk=
Subject: Re: [PCN] Showstopper for merger of PCN SM and CL drafts
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/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: Fri, 10 Dec 2010 16:28:05 -0000

Hi All,

I agree with much of what Michael says, and on balance feel that 2 =
documents
will make life easier for developers and vendors...=20

See inline

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Michael Menth
> Sent: 09 December 2010 20:39
> To: pcn@ietf.org
> Subject: Re: [PCN] Showstopper for merger of PCN SM and CL drafts
>=20
> Hi Tom, hi David, hi Toby, and all,
>=20
> Am 09.12.2010 19:01, schrieb Toby Moncaster:
> > One possible (though not entirely elegant) solution to the 3-in-1
> problem
> > would be to summarise 3-in-1 within this document in a very brief
> manner.
> > This could be as simple as:
> >
> > "CL edge behaviour requires an additional PCN-codepoint to carry the
> > ThM-marking. This could be provided by utilising the EXP codepoint
> defined
> > in RFC5696, following the rules set out in section 5 of that
> document."
> >
> > Really it doesn't matter how the PCN-markings are encoded. All that
> matters
> > is that CL requires there to be an additional marking state... And =
if
> these
> > are INFO documents then it may be less of an issue still (as we =
won't
> be
> > standardising anything "through the back door").
> >
> > As far as I can see we have 3 things here: stuff that is common to
> both edge
> > behaviours; stuff that is common, but where the details differ
> (calculating
> > CLE is an obvious example); stuff that only applies to CL. That
> suggests to
> > me that we could write the document in two halfs. The first part
> specifies
> > SM, but with markers for where CL differs. The second part then
> specifies
> > the differences.
>=20
> I fear that a description of CL based on differences to SM makes CL
> unnecessarily difficult to understand. That's why I do not think that
> this is a good approach, if I have understood it correctly. Apart from
> that, I find CL is even easier to understand than SM and explaining
> first the difficult method and then the simple one is not very
> efficient.

TO be honest, these edge behaviour documents don't require an =
understanding
of the fine details of CL or SM, so it doesn't matter which one is =
easier to
understand... The only requirement is that the documents give clear =
guidance
to developers and operators regarding how to set variables and how to =
choose
whether to enable options or not.

>=20
> Apart from that, CL and SM are two incompatible approaches: it is not
> possible to run both of them in a single network. That might be =
another
> reason why they deserve to be described in two separate documents. =
It's
> a bit like two- and three-rate color marking (RFC 2697 and RFC 2698).
> They are different and it is much easier to express that by referring
> to
> two different RFC numbers.

I think I agree with this point. Take a hypothetical situation: Vendor X
decides to build SM edge behaviour nodes and Vendor Y builds CL =
behaviour
nodes. Operator Z then buys equipment from both these vendors. Because Z =
is
not paying close attention he simply specifies that he wants compliance =
with
RFCnnnn (which is the combined specification). In this sort of case Z =
ends
up with kit that doesn't work together because he didn't realise RFCnnnn
specifies two variants of edge behaviour.

So to summarise, I think I am now in favour of two documents but written
with significant care to ensure there are no unnecessary differences of
wording between them. That should be quite easy to achieve now that Tom =
has
spent so much effort combining them (he can simply clone and cut out =
those
bits that don't apply).=20

The 3-in-1 issue doesn't go away though, so it might be that CL would be
better left in limbo for a few months (perhaps left with RFC editor =
until
3-in-1 becomes an RFC). Alternatively the solution I suggest above might
work...

Toby


>=20
> Regards,
>=20
>      Michael
>=20
> > Toby
> >
> >> -----Original Message-----
> >> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf
> Of
> >> Tom Taylor
> >> Sent: 09 December 2010 17:46
> >> To: pcn
> >> Subject: [PCN] Showstopper for merger of PCN SM and CL drafts
> >>
> >> I have just been reading a review that Toby Moncaster kindly
> provided
> >> for my proposed new merged SM + CL draft. It's that prickly issue =
of
> >> how
> >> to refer to [I-D.3in1]. The trouble is that [I-D.3in1] looks to be
> >> headed for Experimental track for the time being. This raises some
> sort
> >> of distinction between SM and CL, though I'm not quite sure what =
the
> >> significance is given that the edge behaviour drafts are
> Informational.
> >> Anyway, I suspect the difference means that SM and CL should be
> >> documented in separate drafts.
> >>
> >> I'll look for some other way to fix the problem David identified. =
At
> >> the
> >> least, I'll clean up the unnecessary editorial differences. I =
wonder
> if
> >> it would work to put a marker in at each spot where the drafts must
> >> necessarily differ, for instance, by adding the phrase "For the SM
> >> boundary node behaviour", or "For the SM boundary node behaviour",
> as
> >> the case may be. I could also have an introductory note explaining
> that
> >> the two drafts are very similar and explaining the use of this
> marker.
> >>
> >> Does this sound reasonable to you, David?
> >>
> >> Tom Taylor
> >> _______________________________________________
> >> PCN mailing list
> >> PCN@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pcn
> > _______________________________________________
> > PCN mailing list
> > PCN@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcn
>=20
> --
> Prof. Dr. habil. Michael Menth
> University of Tuebingen
> Wilhelm-Schickard-Institute
> Lehrstuhl f=FCr Rechnernetze und Internet
> Sand 13, 72076 Tuebingen, Germany
> phone: (+49)-7071/29-70505, fax: (+49)-7071/29-5220
> mailto:menth@uni-tuebingen.de, http://www.net2.uni-tuebingen.de
>=20
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn


From tom111.taylor@bell.net  Fri Dec 10 13:28:39 2010
Return-Path: <tom111.taylor@bell.net>
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 9321D28C133 for <pcn@core3.amsl.com>; Fri, 10 Dec 2010 13:28:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.756
X-Spam-Level: 
X-Spam-Status: No, score=-101.756 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 4ywUfO0x2bls for <pcn@core3.amsl.com>; Fri, 10 Dec 2010 13:28:20 -0800 (PST)
Received: from blu0-omc1-s21.blu0.hotmail.com (blu0-omc1-s21.blu0.hotmail.com [65.55.116.32]) by core3.amsl.com (Postfix) with ESMTP id 82A4A28C164 for <pcn@ietf.org>; Fri, 10 Dec 2010 13:28:04 -0800 (PST)
Received: from BLU0-SMTP6 ([65.55.116.9]) by blu0-omc1-s21.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 10 Dec 2010 13:29:33 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP6659F588D54B67A8DDC8FD82F0@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP6.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 10 Dec 2010 13:29:32 -0800
Date: Fri, 10 Dec 2010 16:29:34 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: pcn <pcn@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Dec 2010 21:29:32.0946 (UTC) FILETIME=[55FCDF20:01CB98B1]
Subject: [PCN] A couple of proposed technical changes and one correction in the edge behaviour drafts
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/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: Fri, 10 Dec 2010 21:28:40 -0000

I'm currently in the process of ensuring that the CL and SM documents 
use identical text except where necessary, and I'm flagging all the 
variant parts with [CL-specific] or [SM-specific] in their respective 
documents. I have been thinking about David's comments as I worked, and 
have come up with the following changes I would like to propose:

1. In the core network assumptions section for CL, remove the reference 
to a coding extension document and [I-D.3in1]. Say simply that 
excess-traffic-marking uses the EXP codepoint defined in RFC 5696.

The reason for this proposal is that as I understand RFC 5696, the 
implementation of all the codepoints is clearly defined in terms of ECN 
bits. What is not defined is whether and how the PCN-domain supports 
end-to-end ECN. I'm not sure the edge behaviour drafts need to discuss 
that. If they do, the discussion probably belongs in the PDB template.

2. Thinking about the timer settings for reliable and unreliable 
transport, I realized that we are unlikely to offer the operator a 
choice between the two. Instead, we will write our signalling 
requirements document and another WG (according to the charter) will 
specify the actual transport.

The implication is that the SM and CL drafts should state that the 
transport protocol has not been specified, and make it a requirement 
that when it is specified, the specifications must include default 
values for T-maxsuppress and T-fail.

3. In addition, I noted an error in the current SM draft. The value of 
the factor U has to be greater than 1, not less than 1. I should 
probably also mention that it represents an average ratio of 
PCN-supportable-rate to PCN-admissible-rate over all the links of the 
PCN-domain.

Comments, please.
Tom Taylor

From toby@moncaster.com  Fri Dec 10 14:11:42 2010
Return-Path: <toby@moncaster.com>
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 7BB1F28C13A for <pcn@core3.amsl.com>; Fri, 10 Dec 2010 14:11:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 ar7JoCI3nlAS for <pcn@core3.amsl.com>; Fri, 10 Dec 2010 14:11:39 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by core3.amsl.com (Postfix) with ESMTP id 0F8803A6CC2 for <pcn@ietf.org>; Fri, 10 Dec 2010 14:11:35 -0800 (PST)
Received: from TobysHP (host86-141-37-244.range86-141.btcentralplus.com [86.141.37.244]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0LbPxa-1QAfIh1i8I-00ktjS; Fri, 10 Dec 2010 23:13:05 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'Tom Taylor'" <tom111.taylor@bell.net>
References: <BLU0-SMTP6659F588D54B67A8DDC8FD82F0@phx.gbl>
In-Reply-To: <BLU0-SMTP6659F588D54B67A8DDC8FD82F0@phx.gbl>
Date: Fri, 10 Dec 2010 22:13:05 -0000
Message-ID: <003e01cb98b7$6baf2a70$430d7f50$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcuYsXwqkQRz3ltNRQuwVATvSt0MkgABMzeQ
Content-Language: en-gb
X-Provags-ID: V02:K0:oTeg0W2yBu+iL796b19Ozb8hvZ7cqmcY/3jghAPE0Qn PIf1vngwhXkUrDdWCW9LzRaZumrMyQjcb2wZhMKBPif1v/u0i3 Xeq7ujoRMowiN2nsOw75zemka7SqSSd5IPIhluEVDkwQ+YjDzW ejjhXOJ1P7oimT7SQIzyLdQGY6gLUWZrqHy5RIDwtFAOA5ARfT LwAAdKnmR4SnVphco4XCtVPWUVK/BkaqfHG9Hwspic=
Cc: 'pcn' <pcn@ietf.org>
Subject: Re: [PCN] A couple of proposed technical changes and one correction in the edge behaviour drafts
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/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: Fri, 10 Dec 2010 22:11:42 -0000

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Tom Taylor
> Sent: 10 December 2010 21:30
> To: pcn
> Subject: [PCN] A couple of proposed technical changes and one
> correction in the edge behaviour drafts
> 
> I'm currently in the process of ensuring that the CL and SM documents
> use identical text except where necessary, and I'm flagging all the
> variant parts with [CL-specific] or [SM-specific] in their respective
> documents. I have been thinking about David's comments as I worked, and
> have come up with the following changes I would like to propose:
> 
> 1. In the core network assumptions section for CL, remove the reference
> to a coding extension document and [I-D.3in1]. Say simply that
> excess-traffic-marking uses the EXP codepoint defined in RFC 5696.

Seems sensible... Not sure if you need draw attention to the rules for using
that codepoint (section 5 of 5696)

> 
> The reason for this proposal is that as I understand RFC 5696, the
> implementation of all the codepoints is clearly defined in terms of ECN
> bits. What is not defined is whether and how the PCN-domain supports
> end-to-end ECN. I'm not sure the edge behaviour drafts need to discuss
> that. If they do, the discussion probably belongs in the PDB template.

I think it was generally agreed that, unless you use a really complex
encoding, PCN overrides e2e ECN. The only encoding that gives any ECN
support is the 3-state proposal, and that is only limited. Consequently I
don't feel you need make any mention of ECN in your documents.

> 
> 2. Thinking about the timer settings for reliable and unreliable
> transport, I realized that we are unlikely to offer the operator a
> choice between the two. Instead, we will write our signalling
> requirements document and another WG (according to the charter) will
> specify the actual transport.
> 
> The implication is that the SM and CL drafts should state that the
> transport protocol has not been specified, and make it a requirement
> that when it is specified, the specifications must include default
> values for T-maxsuppress and T-fail.

Probably OK. Although it does give people yet more cross references they
have to check. The other way to do it is "typically t-maxsuppress and t-fail
have the following values, but these depend on the transport. If a transport
has significantly different requirements that should be specified in the
appropriate document" 

> 
> 3. In addition, I noted an error in the current SM draft. The value of
> the factor U has to be greater than 1, not less than 1. I should
> probably also mention that it represents an average ratio of
> PCN-supportable-rate to PCN-admissible-rate over all the links of the
> PCN-domain.

That explanation would make it clearer, and it gives some idea of the likely
range for U...

Toby

PS Before we get too far down the road it would be sensible to check whether
Dave Harrington is satisfied or not. You have already spent a lot of effort
trying to merge the documents only to run into problems. I wouldn't like you
to have to go through another complete round of revisions only to be told to
start again!

> 
> Comments, please.
> Tom Taylor
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn


From menth@informatik.uni-tuebingen.de  Sat Dec 11 04:30:20 2010
Return-Path: <menth@informatik.uni-tuebingen.de>
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 88B543A68C0 for <pcn@core3.amsl.com>; Sat, 11 Dec 2010 04:30:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[AWL=0.503,  BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448]
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 ZhOyyeR-iDlC for <pcn@core3.amsl.com>; Sat, 11 Dec 2010 04:30:19 -0800 (PST)
Received: from mx3.informatik.uni-tuebingen.de (mx3.Informatik.Uni-Tuebingen.De [134.2.12.26]) by core3.amsl.com (Postfix) with SMTP id 22F7D3A68AC for <pcn@ietf.org>; Sat, 11 Dec 2010 04:30:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx3.informatik.uni-tuebingen.de (Postfix) with ESMTP id 8681852AF for <pcn@ietf.org>; Sat, 11 Dec 2010 13:31:46 +0100 (MET)
X-Virus-Scanned: amavisd-new at informatik.uni-tuebingen.de
Received: from mx3.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx3.informatik.uni-tuebingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dMhcOu5jsPnD for <pcn@ietf.org>; Sat, 11 Dec 2010 13:31:42 +0100 (MET)
Received: from zcs-pu.informatik.uni-tuebingen.de (zcs-pu.Informatik.Uni-Tuebingen.De [134.2.12.61]) by mx3.informatik.uni-tuebingen.de (Postfix) with ESMTP id E7D9252A2 for <pcn@ietf.org>; Sat, 11 Dec 2010 13:31:41 +0100 (MET)
Received: from [192.168.1.100] (HSI-KBW-095-208-114-108.hsi5.kabel-badenwuerttemberg.de [95.208.114.108]) by zcs-pu.informatik.uni-tuebingen.de (Postfix) with ESMTP id 93532C0F06F for <pcn@ietf.org>; Sat, 11 Dec 2010 13:31:40 +0100 (CET)
Message-ID: <4D036F2F.1030803@informatik.uni-tuebingen.de>
Date: Sat, 11 Dec 2010 13:31:43 +0100
From: Michael Menth <menth@informatik.uni-tuebingen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: pcn@ietf.org
References: <BLU0-SMTP6659F588D54B67A8DDC8FD82F0@phx.gbl>
In-Reply-To: <BLU0-SMTP6659F588D54B67A8DDC8FD82F0@phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PCN] A couple of proposed technical changes and one correction in the edge behaviour drafts
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/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: Sat, 11 Dec 2010 12:30:20 -0000

Hi Tom,

Am 10.12.2010 22:29, schrieb Tom Taylor:
> I'm currently in the process of ensuring that the CL and SM documents=20
> use identical text except where necessary, and I'm flagging all the=20
> variant parts with [CL-specific] or [SM-specific] in their respective=20
> documents. I have been thinking about David's comments as I worked,=20
> and have come up with the following changes I would like to propose:
>
> 1. In the core network assumptions section for CL, remove the=20
> reference to a coding extension document and [I-D.3in1]. Say simply=20
> that excess-traffic-marking uses the EXP codepoint defined in RFC 5696.
>
> The reason for this proposal is that as I understand RFC 5696, the=20
> implementation of all the codepoints is clearly defined in terms of=20
> ECN bits. What is not defined is whether and how the PCN-domain=20
> supports end-to-end ECN. I'm not sure the edge behaviour drafts need=20
> to discuss that. If they do, the discussion probably belongs in the=20
> PDB template.
>
> 2. Thinking about the timer settings for reliable and unreliable=20
> transport, I realized that we are unlikely to offer the operator a=20
> choice between the two. Instead, we will write our signalling=20
> requirements document and another WG (according to the charter) will=20
> specify the actual transport.
>
> The implication is that the SM and CL drafts should state that the=20
> transport protocol has not been specified, and make it a requirement=20
> that when it is specified, the specifications must include default=20
> values for T-maxsuppress and T-fail.
>
> 3. In addition, I noted an error in the current SM draft. The value of=20
> the factor U has to be greater than 1, not less than 1. I should=20
> probably also mention that it represents an average ratio of=20
> PCN-supportable-rate to PCN-admissible-rate over all the links of the=20
> PCN-domain.
The value U (>1) actually defines the ratio between PCN-supportable and=20
PCN-admissible rate. But this aspect is so far not really covered in the=20
draft, I believe. To let the user know the impact of the parameter U,=20
this relation would be indeed useful to know.

Best wishes,

     Michael


>
> Comments, please.
> Tom Taylor
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn

--=20
Prof. Dr. habil. Michael Menth
University of Tuebingen
Wilhelm-Schickard-Institute
Lehrstuhl f=FCr Rechnernetze und Internet
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70505, fax: (+49)-7071/29-5220
mailto:menth@uni-tuebingen.de, http://www.net2.uni-tuebingen.de


From karagian@cs.utwente.nl  Sun Dec 12 02:13:53 2010
Return-Path: <karagian@cs.utwente.nl>
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 82B853A6D0A for <pcn@core3.amsl.com>; Sun, 12 Dec 2010 02:13:53 -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 NR463ndFkeiy for <pcn@core3.amsl.com>; Sun, 12 Dec 2010 02:13:52 -0800 (PST)
Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11]) by core3.amsl.com (Postfix) with ESMTP id 136D13A6D01 for <pcn@ietf.org>; Sun, 12 Dec 2010 02:13:51 -0800 (PST)
Received: from webmail.cs.utwente.nl (janus.ewi.utwente.nl [130.89.10.26]) by denhaag.ewi.utwente.nl (8.13.6/8.13.6) with SMTP id oBCAFEhT020893;  Sun, 12 Dec 2010 11:15:15 +0100 (MET)
Received: from 84.82.109.231 (auth. user karagian@imap1.ewi.utwente.nl) by webmail.cs.utwente.nl with HTTP; Sun, 12 Dec 2010 10:15:14 +0000
To: "Tom Taylor" <tom111.taylor@bell.net>, "pcn" <pcn@ietf.org>
Date: Sun, 12 Dec 2010 10:15:14 +0000
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <SoQM7i1w.1292148914.7908500.karagian@ewi.utwente.nl>
In-Reply-To: <BLU0-SMTP6659F588D54B67A8DDC8FD82F0@phx.gbl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Errors-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (denhaag.ewi.utwente.nl [130.89.10.11]); Sun, 12 Dec 2010 11:15:23 +0100 (MET)
Subject: Re: [PCN] A couple of proposed technical changes and one correction in the edge behaviour drafts
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/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: Sun, 12 Dec 2010 10:13:53 -0000

Hi Tom

Please see in line!

On 12/10/2010, "Tom Taylor" <tom111.taylor@bell.net> wrote:

>I'm currently in the process of ensuring that the CL and SM documents
>use identical text except where necessary, and I'm flagging all the
>variant parts with [CL-specific] or [SM-specific] in their respective
>documents. I have been thinking about David's comments as I worked, and
>have come up with the following changes I would like to propose:
>
>1. In the core network assumptions section for CL, remove the reference
>to a coding extension document and [I-D.3in1]. Say simply that
>excess-traffic-marking uses the EXP codepoint defined in RFC 5696.
>

Georgios: Not sure if it is good to restrict the applicability only to
RFC 5696.

>The reason for this proposal is that as I understand RFC 5696, the
>implementation of all the codepoints is clearly defined in terms of ECN
>bits. What is not defined is whether and how the PCN-domain supports
>end-to-end ECN. I'm not sure the edge behaviour drafts need to discuss
>that. If they do, the discussion probably belongs in the PDB template.
>

Georgios: I think that PCN PCN overrides end to end ECN. I do not think
that it is needed to discuss this in the edge behaviour drafts.


>2. Thinking about the timer settings for reliable and unreliable
>transport, I realized that we are unlikely to offer the operator a
>choice between the two. Instead, we will write our signalling
>requirements document and another WG (according to the charter) will
>specify the actual transport.
>
>The implication is that the SM and CL drafts should state that the
>transport protocol has not been specified, and make it a requirement
>that when it is specified, the specifications must include default
>values for T-maxsuppress and T-fail.

Georgios: Okay, but use the approach proposed by Toby in a previous email.

>
>3. In addition, I noted an error in the current SM draft. The value of
>the factor U has to be greater than 1, not less than 1. I should
>probably also mention that it represents an average ratio of
>PCN-supportable-rate to PCN-admissible-rate over all the links of the
>PCN-domain.

Georgios: You are right, the value of U must be greater than or equal to
1.

Best regards,
Georgios

>
>Comments, please.
>Tom Taylor
>_______________________________________________
>PCN mailing list
>PCN@ietf.org
>https://www.ietf.org/mailman/listinfo/pcn

From toby@moncaster.com  Sun Dec 12 13:57:50 2010
Return-Path: <toby@moncaster.com>
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 A0FFE3A6E62 for <pcn@core3.amsl.com>; Sun, 12 Dec 2010 13:57:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 VjXqqAoFo657 for <pcn@core3.amsl.com>; Sun, 12 Dec 2010 13:57:49 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by core3.amsl.com (Postfix) with ESMTP id 7043F3A6E77 for <pcn@ietf.org>; Sun, 12 Dec 2010 13:57:49 -0800 (PST)
Received: from TobysHP (host86-141-37-244.range86-141.btcentralplus.com [86.141.37.244]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0M8dGh-1QNSXo3RAJ-00viSX; Sun, 12 Dec 2010 22:59:24 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'Georgios Karagiannis'" <karagian@cs.utwente.nl>, "'Tom Taylor'" <tom111.taylor@bell.net>, "'pcn'" <pcn@ietf.org>
References: <BLU0-SMTP6659F588D54B67A8DDC8FD82F0@phx.gbl> <SoQM7i1w.1292148914.7908500.karagian@ewi.utwente.nl>
In-Reply-To: <SoQM7i1w.1292148914.7908500.karagian@ewi.utwente.nl>
Date: Sun, 12 Dec 2010 21:59:23 -0000
Message-ID: <001001cb9a47$d671aa40$8354fec0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcuZ5YIhiZFu1ExOTYu6VIOeSscB9gAYgXAA
Content-Language: en-gb
X-Provags-ID: V02:K0:dMrNEQtS2qMifww68mZBmPS0hi7v2wZYJrFkRymbIXH jFl92r/hcZwgA9bxtTtKJvoSuQq6W5Epp7C/ubkyPZoqvMfdZ2 6sUyK3C8iujayWyEMwC6mCoENsks5sMCbwFjtqe2dVA6LxH8ng 4CKvezvpRtvpF4422D1qE2HposNnDdGPhdAjJdGL+a60REaApN /iq5z3P3G901IxUWZTkr7cOumJZXqhEJ+N0xPLMrtE=
Subject: Re: [PCN] A couple of proposed technical changes and one correction	in the edge behaviour drafts
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/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: Sun, 12 Dec 2010 21:57:50 -0000

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Georgios Karagiannis
> Sent: 12 December 2010 10:15
> To: Tom Taylor; pcn
> Subject: Re: [PCN] A couple of proposed technical changes and one
> correction in the edge behaviour drafts
> 
> Hi Tom
> 
> Please see in line!
> 
> On 12/10/2010, "Tom Taylor" <tom111.taylor@bell.net> wrote:
> 
> >I'm currently in the process of ensuring that the CL and SM documents
> >use identical text except where necessary, and I'm flagging all the
> >variant parts with [CL-specific] or [SM-specific] in their respective
> >documents. I have been thinking about David's comments as I worked,
> and
> >have come up with the following changes I would like to propose:
> >
> >1. In the core network assumptions section for CL, remove the
> reference
> >to a coding extension document and [I-D.3in1]. Say simply that
> >excess-traffic-marking uses the EXP codepoint defined in RFC 5696.
> >
> 
> Georgios: Not sure if it is good to restrict the applicability only to
> RFC 5696.

Perhaps it could be RFC5696 (or any encoding that succeeds it) to allow for
the possibility of 3-in-1 becoming a STDs track document eventually.

> 
> >The reason for this proposal is that as I understand RFC 5696, the
> >implementation of all the codepoints is clearly defined in terms of
> ECN
> >bits. What is not defined is whether and how the PCN-domain supports
> >end-to-end ECN. I'm not sure the edge behaviour drafts need to discuss
> >that. If they do, the discussion probably belongs in the PDB template.
> >
> 
> Georgios: I think that PCN PCN overrides end to end ECN. I do not think
> that it is needed to discuss this in the edge behaviour drafts.

Indeed. That is for encoding documents!

> 
> 
> >2. Thinking about the timer settings for reliable and unreliable
> >transport, I realized that we are unlikely to offer the operator a
> >choice between the two. Instead, we will write our signalling
> >requirements document and another WG (according to the charter) will
> >specify the actual transport.
> >
> >The implication is that the SM and CL drafts should state that the
> >transport protocol has not been specified, and make it a requirement
> >that when it is specified, the specifications must include default
> >values for T-maxsuppress and T-fail.
> 
> Georgios: Okay, but use the approach proposed by Toby in a previous
> email.
> 
> >
> >3. In addition, I noted an error in the current SM draft. The value of
> >the factor U has to be greater than 1, not less than 1. I should
> >probably also mention that it represents an average ratio of
> >PCN-supportable-rate to PCN-admissible-rate over all the links of the
> >PCN-domain.
> 
> Georgios: You are right, the value of U must be greater than or equal
> to
> 1.

And needs a brief explanation as suggested by Michael...

Toby

> 
> Best regards,
> Georgios
> 
> >
> >Comments, please.
> >Tom Taylor
> >_______________________________________________
> >PCN mailing list
> >PCN@ietf.org
> >https://www.ietf.org/mailman/listinfo/pcn
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn


From Ruediger.Geib@telekom.de  Mon Dec 13 03:00:06 2010
Return-Path: <Ruediger.Geib@telekom.de>
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 5BF173A6E89 for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 03:00:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 hIF5tnIYNtiO for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 03:00:05 -0800 (PST)
Received: from tcmail53.telekom.de (tcmail53.telekom.de [217.5.214.110]) by core3.amsl.com (Postfix) with ESMTP id 969983A6E88 for <pcn@ietf.org>; Mon, 13 Dec 2010 03:00:03 -0800 (PST)
Received: from he110890.emea1.cds.t-internal.com ([10.134.92.131]) by tcmail51.telekom.de with ESMTP/TLS/AES128-SHA; 13 Dec 2010 12:01:32 +0100
Received: from HE111648.emea1.cds.t-internal.com ([169.254.5.187]) by he110890 ([10.134.92.131]) with mapi; Mon, 13 Dec 2010 12:01:14 +0100
From: <Ruediger.Geib@telekom.de>
To: <menth@informatik.uni-tuebingen.de>
Date: Mon, 13 Dec 2010 12:01:13 +0100
Thread-Topic: [PCN] Showstopper for merger of PCN SM and CL drafts
Thread-Index: AcuX4UTw0eGMxOvaTnqNgDKAcsJj2gC035Gg
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D050E7426@HE111648.emea1.cds.t-internal.com>
References: <BLU0-SMTP70A674EAD36599A53B190AD82E0@phx.gbl> <001f01cb97cb$0f63dff0$2e2b9fd0$@com> <4D013E6A.8040202@informatik.uni-tuebingen.de>
In-Reply-To: <4D013E6A.8040202@informatik.uni-tuebingen.de>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: pcn@ietf.org
Subject: Re: [PCN] Showstopper for merger of PCN SM and CL drafts
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/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: Mon, 13 Dec 2010 11:00:06 -0000

Hi Michael,

the incompatibility of both approaches is indeed an argument to have two se=
parate
drafts, so I agree with you and the other PCN authors on the issue.

Regards,

Ruediger

-----Original Message-----
From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of Micha=
el Menth
Sent: Thursday, December 09, 2010 9:39 PM
To: pcn@ietf.org
Subject: Re: [PCN] Showstopper for merger of PCN SM and CL drafts

Hi Tom, hi David, hi Toby, and all,

Am 09.12.2010 19:01, schrieb Toby Moncaster:
> One possible (though not entirely elegant) solution to the 3-in-1 problem
> would be to summarise 3-in-1 within this document in a very brief manner.
> This could be as simple as:
>
> "CL edge behaviour requires an additional PCN-codepoint to carry the
> ThM-marking. This could be provided by utilising the EXP codepoint define=
d
> in RFC5696, following the rules set out in section 5 of that document."
>
> Really it doesn't matter how the PCN-markings are encoded. All that matte=
rs
> is that CL requires there to be an additional marking state... And if the=
se
> are INFO documents then it may be less of an issue still (as we won't be
> standardising anything "through the back door").
>
> As far as I can see we have 3 things here: stuff that is common to both e=
dge
> behaviours; stuff that is common, but where the details differ (calculati=
ng
> CLE is an obvious example); stuff that only applies to CL. That suggests =
to
> me that we could write the document in two halfs. The first part specifie=
s
> SM, but with markers for where CL differs. The second part then specifies
> the differences.

I fear that a description of CL based on differences to SM makes CL
unnecessarily difficult to understand. That's why I do not think that
this is a good approach, if I have understood it correctly. Apart from
that, I find CL is even easier to understand than SM and explaining
first the difficult method and then the simple one is not very efficient.

Apart from that, CL and SM are two incompatible approaches: it is not
possible to run both of them in a single network. That might be another
reason why they deserve to be described in two separate documents. It's
a bit like two- and three-rate color marking (RFC 2697 and RFC 2698).
They are different and it is much easier to express that by referring to
two different RFC numbers.

Regards,

     Michael

> Toby
>
>> -----Original Message-----
>> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
>> Tom Taylor
>> Sent: 09 December 2010 17:46
>> To: pcn
>> Subject: [PCN] Showstopper for merger of PCN SM and CL drafts
>>
>> I have just been reading a review that Toby Moncaster kindly provided
>> for my proposed new merged SM + CL draft. It's that prickly issue of
>> how
>> to refer to [I-D.3in1]. The trouble is that [I-D.3in1] looks to be
>> headed for Experimental track for the time being. This raises some sort
>> of distinction between SM and CL, though I'm not quite sure what the
>> significance is given that the edge behaviour drafts are Informational.
>> Anyway, I suspect the difference means that SM and CL should be
>> documented in separate drafts.
>>
>> I'll look for some other way to fix the problem David identified. At
>> the
>> least, I'll clean up the unnecessary editorial differences. I wonder if
>> it would work to put a marker in at each spot where the drafts must
>> necessarily differ, for instance, by adding the phrase "For the SM
>> boundary node behaviour", or "For the SM boundary node behaviour", as
>> the case may be. I could also have an introductory note explaining that
>> the two drafts are very similar and explaining the use of this marker.
>>
>> Does this sound reasonable to you, David?
>>
>> Tom Taylor
>> _______________________________________________
>> PCN mailing list
>> PCN@ietf.org
>> https://www.ietf.org/mailman/listinfo/pcn
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn

--
Prof. Dr. habil. Michael Menth
University of Tuebingen
Wilhelm-Schickard-Institute
Lehrstuhl f=FCr Rechnernetze und Internet
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70505, fax: (+49)-7071/29-5220
mailto:menth@uni-tuebingen.de, http://www.net2.uni-tuebingen.de

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

From tom111.taylor@bell.net  Mon Dec 13 08:05:45 2010
Return-Path: <tom111.taylor@bell.net>
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 E28EF28C0D0 for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 08:05:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.758
X-Spam-Level: 
X-Spam-Status: No, score=-101.758 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 4BFuYajO5qEI for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 08:05:44 -0800 (PST)
Received: from blu0-omc3-s34.blu0.hotmail.com (blu0-omc3-s34.blu0.hotmail.com [65.55.116.109]) by core3.amsl.com (Postfix) with ESMTP id B94C03A6CB5 for <pcn@ietf.org>; Mon, 13 Dec 2010 08:05:44 -0800 (PST)
Received: from BLU0-SMTP56 ([65.55.116.73]) by blu0-omc3-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Dec 2010 08:07:22 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP56D06AAA0407A85C78D0AFD8120@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP56.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Dec 2010 08:07:22 -0800
Date: Mon, 13 Dec 2010 11:07:21 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Dec 2010 16:07:22.0267 (UTC) FILETIME=[D33E96B0:01CB9ADF]
Cc: pcn <pcn@ietf.org>
Subject: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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: Mon, 13 Dec 2010 16:05:46 -0000

Here are my proposed responses to your first review note, based in part 
on list discussion. Do they meet your concerns?

PCN WG, is this OK for you?

======================

Hi,

I have performed an AD Review of draft-ietf-pcn-sm-edge-behaviour-04
and have some comments.

1) As I reviewed both the SM and CL edge behavior documents, I noted
with concern how similar the documents are. I wonder if you wouldn't
be better having one document, with common text in the early chapters,
and then a section for SM and a section for CL. Or even three
documents, to pave the way for addiitonal behavior documents.

The real concern is that when you have so much common text, you need
to work hard to keep them consistent. An additional concern is that
the IETF (in LC) IESG (in IESG Eval) will need to review these docs,
and check that you haven't overlooked anything; the IETF and IESG
basically perform sanity checks. This is made harder when the text is
almost the same in the two documents. If the editorial text is just
slightly different in multiple places, it becomes much harder to find
the important differences between the documents.

[snip]

if you are going to have two documents with so much common text, I
will expect the editorial text to be consistent, so the technical
differences are clear.

----------------

[PTT response] I propose that we:

  a) Add the following paragraph at the end of Section 1 (CL version shown):

"A companion document [I-D.SM-edge-behaviour] specifies the Single 
Marking (SM) PCN-boundary-node behaviour. This document and 
[I-D.SM-edge-behaviour] have a great deal of text in common. To simplify 
the task of the reader, the text in the present document that is 
specific to the CL PCN-boundary-node behaviour is preceded by the 
phrase: "[CL-specific]". A similar distinction for SM-specific text is 
made in [I-D.SM-edge-behaviour]."

b) Take a diff between CL-07 and SM-04, eliminate the purely editorial 
differences, and tag the technical differences as indicated by the above 
paragraph.


=====================


2) Why are individual flow identifiers reported for
excess-traffic-marked PCN-traffic for CL but not for SM? Wouldn't this
be useful for both?

[PTT response] Answered in a previous E-mail -- a matter of not having a 
sufficiently precise trigger with SM to know whether the flow 
identifiers should be collected or would be meaningful. I can't think of 
a text proposal, since it would logically belong in the SM draft but 
would be an explanation for text that isn't there.

=====================

3) From Acknowledgements:    The authors thank Ruediger Geib for his
useful comments.  The acknowledgements in the CL boundary node
behaviour draft really apply here, too.
dbh: the CL draft is likely to be an RFC. If you want the
acknowledgement in both places, put it in both places.

[PTT response] Will do as part of the editorial synchronization.

=====================

4) I would be careful referencing other works-in-porgress, just in
case anything slows down the other document(s). No sense holding up
the publication of this document because another document runs into a
delay.

[PTT response] Some of that is purely historic, and the documents have 
long expired. I see no harm in cross-referencing between the SM and CL 
drafts, though I should possibly use RFCyyyy notation. I-D.PCN3in1 will 
be dropped from the CL draft, per list discussion.

======================

5) please check all lower-case RFC2119 keywords. The IESG prefers that
they be uppercased to make it clear they are normative. I recommend
using "might" rather than "may" for non-normative, and re-wording
musts, shoulds, and recommends to avoid using lowercased reserved
words.

[PTT response] I think the usual situation where we run into this is 
talking about what an operator could do. Will check it out.

======================

6) section 3.2 and section 3.3.2 both present the formula for CLE, but
they present it differently. Just a style issue, but I recommend
presenting it consistently.

[PTT response] OK

=======================

7) section 3.3 "The Decision Point MUST"; I recommend saying "A
compliant Decision Point MUST"

[PTT response] OK

=======================

8) "PCN traffic" is used here, but where that term is defined is not
mentioned. Since this is used in formulae, that could be important to
understand correctly.

[PTT response] I propose to add the following definition:

PCN-traffic			
	An octet stream consisting of PCN-packets considered
         within a specific context.

=======================

9) in 3.5, do we really need both t-meas and T-meas, etc.? The chart
would be easier to read if you eliminated one of the redundant
columns.

[PTT response] OK

=======================

10) in Table 1, some word breaks are missing from the Action on Expiry
column. Put a space between conditionally and CLE, and between each
and IEA.

[PTT response] That was XML2RFC, fitting things into too little space. 
Eliminating one of the columns will fix that. I also propose to drop the 
word "conditionally" -- too much detail in a summary table.

=======================

11) The acronym IEA is not defined before being used.

[PTT response] Will add an expansion in the preamble to the table.

=======================

12) t-maxsuppress has discussion of the value to use for an unreliable
transport; what is the recommended value for a reliable transport?

[PTT response] The discussion is actually back up in section 3.2.3. The 
whole question of transport will be reframed in view of the realization 
that the choice of transport will be made in the IETF, not by the 
operator. The suggestion on the PCN list was to specify default values 
for all the timers, then say that any transport specification for PCN 
must (or is that MUST?) propose alternative values if the ones proposed 
in this document seem unreasonable for the chosen transport.

Default values are currently given in the body of the text (e.g., in 
section 3.2.1). I'm wresstling with the question of whether they should 
stay there or be replaced by forward references to section 3.5.

=======================

13) section 4 title has extra spaces.

[PTT response] OK, will fix.

=======================




From ietfdbh@comcast.net  Mon Dec 13 08:58:41 2010
Return-Path: <ietfdbh@comcast.net>
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 92C3928C0E2 for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 08:58:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.257
X-Spam-Level: 
X-Spam-Status: No, score=-102.257 tagged_above=-999 required=5 tests=[AWL=-0.258, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, USER_IN_WHITELIST=-100]
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 JSpPkDFp-IR9 for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 08:58:40 -0800 (PST)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by core3.amsl.com (Postfix) with ESMTP id 439D13A6EB8 for <pcn@ietf.org>; Mon, 13 Dec 2010 08:58:40 -0800 (PST)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta10.westchester.pa.mail.comcast.net with comcast id ifby1f0071HzFnQ5Ah0K1V; Mon, 13 Dec 2010 17:00:19 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta14.westchester.pa.mail.comcast.net with comcast id ih0F1f00j2JQnJT3ah0F49; Mon, 13 Dec 2010 17:00:16 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Tom Taylor'" <tom111.taylor@bell.net>
References: <BLU0-SMTP56D06AAA0407A85C78D0AFD8120@phx.gbl>
Date: Mon, 13 Dec 2010 12:00:35 -0500
Message-ID: <29080878471B483A8DF97203AA7EAAAB@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <BLU0-SMTP56D06AAA0407A85C78D0AFD8120@phx.gbl>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Thread-Index: Acua39V4eMo8p5E7TQatd20hA2HD4gABwOVg
Cc: 'pcn' <pcn@ietf.org>
Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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: Mon, 13 Dec 2010 16:58:41 -0000

Hi,

This looks good. a few comments inline.

dbh 

> -----Original Message-----
> From: Tom Taylor [mailto:tom111.taylor@bell.net] 
> Sent: Monday, December 13, 2010 11:07 AM
> To: David Harrington
> Cc: pcn
> Subject: Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-04
> 
> Here are my proposed responses to your first review note, 
> based in part 
> on list discussion. Do they meet your concerns?
> 
> PCN WG, is this OK for you?
> 
> ======================
> 
> Hi,
> 
> I have performed an AD Review of draft-ietf-pcn-sm-edge-behaviour-04
> and have some comments.
> 
> 1) As I reviewed both the SM and CL edge behavior documents, I noted
> with concern how similar the documents are. I wonder if you wouldn't
> be better having one document, with common text in the early
chapters,
> and then a section for SM and a section for CL. Or even three
> documents, to pave the way for addiitonal behavior documents.
> 
> The real concern is that when you have so much common text, you need
> to work hard to keep them consistent. An additional concern is that
> the IETF (in LC) IESG (in IESG Eval) will need to review these docs,
> and check that you haven't overlooked anything; the IETF and IESG
> basically perform sanity checks. This is made harder when the text
is
> almost the same in the two documents. If the editorial text is just
> slightly different in multiple places, it becomes much harder to
find
> the important differences between the documents.
> 
> [snip]
> 
> if you are going to have two documents with so much common text, I
> will expect the editorial text to be consistent, so the technical
> differences are clear.
> 
> ----------------
> 
> [PTT response] I propose that we:
> 
>   a) Add the following paragraph at the end of Section 1 (CL 
> version shown):
> 
> "A companion document [I-D.SM-edge-behaviour] specifies the Single 
> Marking (SM) PCN-boundary-node behaviour. This document and 
> [I-D.SM-edge-behaviour] have a great deal of text in common. 
> To simplify 
> the task of the reader, the text in the present document that is 
> specific to the CL PCN-boundary-node behaviour is preceded by the 
> phrase: "[CL-specific]". A similar distinction for 
> SM-specific text is 
> made in [I-D.SM-edge-behaviour]."

If you b), then a) is unnecessary, although it might be helpful for
people to see the distinction more easily. I would live with having
it,ot not having it, as long as b) is done.
> 
> b) Take a diff between CL-07 and SM-04, eliminate the purely 
> editorial 
> differences, and tag the technical differences as indicated 
> by the above 
> paragraph.
> 
> 
> =====================
> 
> 
> 2) Why are individual flow identifiers reported for
> excess-traffic-marked PCN-traffic for CL but not for SM? Wouldn't
this
> be useful for both?
> 
> [PTT response] Answered in a previous E-mail -- a matter of 
> not having a 
> sufficiently precise trigger with SM to know whether the flow 
> identifiers should be collected or would be meaningful. I 
> can't think of 
> a text proposal, since it would logically belong in the SM draft but

> would be an explanation for text that isn't there.
> 
> =====================
> 
> 3) From Acknowledgements:    The authors thank Ruediger Geib for his
> useful comments.  The acknowledgements in the CL boundary node
> behaviour draft really apply here, too.
> dbh: the CL draft is likely to be an RFC. If you want the
> acknowledgement in both places, put it in both places.
> 
> [PTT response] Will do as part of the editorial synchronization.
> 
> =====================
> 
> 4) I would be careful referencing other works-in-porgress, just in
> case anything slows down the other document(s). No sense holding up
> the publication of this document because another document runs into
a
> delay.
> 
> [PTT response] Some of that is purely historic, and the 
> documents have 
> long expired. I see no harm in cross-referencing between the 
> SM and CL 
> drafts, though I should possibly use RFCyyyy notation. 
> I-D.PCN3in1 will 
> be dropped from the CL draft, per list discussion.
> 
> ======================
> 
> 5) please check all lower-case RFC2119 keywords. The IESG prefers
that
> they be uppercased to make it clear they are normative. I recommend
> using "might" rather than "may" for non-normative, and re-wording
> musts, shoulds, and recommends to avoid using lowercased reserved
> words.
> 
> [PTT response] I think the usual situation where we run into this is

> talking about what an operator could do. Will check it out.
> 
> ======================
> 
> 6) section 3.2 and section 3.3.2 both present the formula for CLE,
but
> they present it differently. Just a style issue, but I recommend
> presenting it consistently.
> 
> [PTT response] OK
> 
> =======================
> 
> 7) section 3.3 "The Decision Point MUST"; I recommend saying "A
> compliant Decision Point MUST"
> 
> [PTT response] OK
> 
> =======================
> 
> 8) "PCN traffic" is used here, but where that term is defined is not
> mentioned. Since this is used in formulae, that could be important
to
> understand correctly.
> 
> [PTT response] I propose to add the following definition:
> 
> PCN-traffic			
> 	An octet stream consisting of PCN-packets considered
>          within a specific context.

Is PCN-packets defined?

> 
> =======================
> 
> 9) in 3.5, do we really need both t-meas and T-meas, etc.? The chart
> would be easier to read if you eliminated one of the redundant
> columns.
> 
> [PTT response] OK
> 
> =======================
> 
> 10) in Table 1, some word breaks are missing from the Action on
Expiry
> column. Put a space between conditionally and CLE, and between each
> and IEA.
> 
> [PTT response] That was XML2RFC, fitting things into too 
> little space. 
> Eliminating one of the columns will fix that. I also propose 
> to drop the 
> word "conditionally" -- too much detail in a summary table.
> 
> =======================
> 
> 11) The acronym IEA is not defined before being used.
> 
> [PTT response] Will add an expansion in the preamble to the table.
> 
> =======================
> 
> 12) t-maxsuppress has discussion of the value to use for an
unreliable
> transport; what is the recommended value for a reliable transport?
> 
> [PTT response] The discussion is actually back up in section 
> 3.2.3. The 
> whole question of transport will be reframed in view of the 
> realization 
> that the choice of transport will be made in the IETF, not by the 
> operator. The suggestion on the PCN list was to specify 
> default values 
> for all the timers, then say that any transport specification for
PCN 
> must (or is that MUST?) propose alternative values if the 
> ones proposed 
> in this document seem unreasonable for the chosen transport.
> 
> Default values are currently given in the body of the text (e.g., in

> section 3.2.1). I'm wresstling with the question of whether 
> they should 
> stay there or be replaced by forward references to section 3.5.
> 
> =======================
> 
> 13) section 4 title has extra spaces.
> 
> [PTT response] OK, will fix.
> 
> =======================
> 
> 
> 


From tom111.taylor@bell.net  Mon Dec 13 09:30:16 2010
Return-Path: <tom111.taylor@bell.net>
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 9B7AB28C114 for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 09:30:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.759
X-Spam-Level: 
X-Spam-Status: No, score=-101.759 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 uoyopjUSI+F0 for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 09:30:15 -0800 (PST)
Received: from blu0-omc3-s11.blu0.hotmail.com (blu0-omc3-s11.blu0.hotmail.com [65.55.116.86]) by core3.amsl.com (Postfix) with ESMTP id 6ADF828C0E4 for <pcn@ietf.org>; Mon, 13 Dec 2010 09:30:12 -0800 (PST)
Received: from BLU0-SMTP91 ([65.55.116.73]) by blu0-omc3-s11.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Dec 2010 09:31:50 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP9163E8F36D2E379B3091E6D8120@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP91.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Dec 2010 09:31:49 -0800
Date: Mon, 13 Dec 2010 12:31:49 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <FEF2029CCC614C6A80884469A91E0015@23FX1C1>
In-Reply-To: <FEF2029CCC614C6A80884469A91E0015@23FX1C1>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Dec 2010 17:31:50.0043 (UTC) FILETIME=[9FDFD6B0:01CB9AEB]
Cc: pcn@ietf.org
Subject: Re: [PCN] AD Review: draft-ietf-pcn-cl-edge-behaviour-07
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/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: Mon, 13 Dec 2010 17:30:16 -0000

Here is the proposed response to your second review E-mail. Again, 
everyone is invited to comment.

On 06/12/2010 3:56 PM, David Harrington wrote:
> Hi,
>
> Because this document has so much common text with the SM document,
> almost all the AD Review comments for the SM document apply to CL as
> well. Please incorporate those comments into this review.

[PTT response] OK

======================
>
> A few comments came to mind after sending the SM review, that apply to
> both; I added parenthesis to indictae it applies to both).
>
> 1) in section 2, reference is made to the "possible extension"
> [ID.PCN3in1].
> I recommend against referencing "possible extension" documents.

[PTT response] I propose to rewrite Section 2. The essence of the 
changes is to base the encoding entirely on RFC 5696, while leaving room 
for an unidentified successor document. Mention of I-D.PCN3in1 will also 
be dropped from the PDB template (see below).

Here is the proposed text for the CL document:

"2. [CL-Specific] Assumed Core Network Behaviour for CL	
				
This section describes the assumed behaviour for nodes of the PCN-domain 
when acting in their role as PCN-interior-nodes. The CL mode	
of operation assumes that:	
				
   o PCN-interior-nodes perform both threshold-marking and 
excess-traffic-marking of packets, according to the rules 
specified in		[RFC5670];	
				
   o excess-traffic-marking of packets uses the PCN-Marked (PM) 
codepoint defined in [RFC5696];			
				
   o threshold-marking of packets uses the EXP codepoint defined in 
[RFC5696];	
				
   o the PCN-domain satisfies the conditions specified in [RFC5696];	
				
   o on each link the reference rate for the threshold-meter is 
configured to be equal to the PCN-admissible-rate for the link;		
				
   o on each link the reference rate for the excess traffic meter is 
configured to be equal to the PCN-supportable-rate for the link;	
				
   o the set of valid codepoint transitions is as shown in Section 4.2 
of [RFC5696]."	

As a follow-up, it is proposed to add clauses indicating the packet 
marking in section 3.2.1 for the different rates. The text would become:

"The PCN-egress-node MUST meter received PCN-traffic in order to derive 
periodically the following rates for each ingress-egress-aggregate 
passing through it:	
				
   o NM-rate: octets per second of PCN-traffic in PCN-packets that are 
not-marked (i.e., marked with the NM codepoint);			
				
   o [CL-specific] ThM-rate: octets per second of PCN-traffic in 
PCN-packets that are threshold-marked (i.e., marked with the PM	 
codepoint);				
				
   o [CL-specific] ETM-rate: octets per second of PCN-traffic in 
PCN-packets that are excess-traffic-marked (i.e., marked with the EXP 
codepoint).

Similar changes would be made to the SM document.

======================
	
>
> 2) "These allowable transitions are specified here" - usually
> specified implies a normative specification. I suggest rewording with
> less normative-like wording.

[PTT response] Replaced by reference to the normative document. See above.

======================
>
> 3) in 3.2.3, the calculation for CLE uses either the latest or the
> previous interval in its caculations. Niether SM nor CL explains why
> it is acceptable to use either interval. Is this explained somewhere?
> How does this affect interoperability? (also applies to SM)
>
[PTT response] Will reword to make it clear that both conditions must be 
tested.

======================

> 4) in 3.3.2, the DP MUST request an estimate of pcn-sent-rate; is
> there a specific protocol that must/should be used to do this
> (assuming they are not co-located)? If not, how is this
> request/response done in a vendor-interoperable manner?

[PTT response] Answered in previous note. Protocol specification is 
still to be done but is explicitly outside the PCN WG charter.
>
> 5) in 3.3.2, last paragraph, the list must be ETM-marked flows, right?
> It doesn't say that.

[PTT response] Will add.

======================
>
> 6) in 3.3., an alarm should be raised to management. is there are
> standardized approach to raising the alarm? If not, how does this
> affect interoperability. Most notably, if two nodes form different
> vendors raise an alarm using different protocols, how will the
> management system correlate the alarms? If two implementations use
> SNMP to raise the alarms, should they use consistent OIDs to identify
> the problem? or consistent syslog SDEs? or consistent ipfix IEs?
> Should the WG standardize the information models, and possibly data
> models and protocols, for reporting such alarms?

[PTT response] This is a topic for another document. The work item seems 
to be missing from the WG charter.

======================
>
> 7) in 5.2, it is asserted that [ID.PCN3in1] specifies the behavior;
> but 2.2 mentions this as a "possible extension". If PCN3in1 is not
> STDS track, then i think this text in 5.2 could be problematic. But I
> suspect that 3086 expects a stable specification.

[PTT response] Reference to that I-D will be dropped.

======================

>
> I have not worked with the 3086 template before. Is a reference to a
> number of RFCs, without any discussion of their details really
> sufficient? It doesn't sounce like that meets the description from
> 3086:
>
>     This section specifies the rules or guidelines to create this PDB,
>     each distinguished with "may", "must" and "should." The technical
>     specification must list the classification and traffic conditioning
>     required (if any) and the PHB (or PHBs) to be used with any
>     additional requirements on their configuration beyond that
> contained
>     in RFCs.  Classification can reflect the results of an admission
>     control process.  Traffic conditioning may include marking, traffic
>     shaping, and policing.  A Service Provisioning Policy might be used
>     to describe the technical specification of a particular PDB.

[PTT response] The only use of the template I could readily find as a 
model was RFC 3662. Proposed to use the following text (common to both 
CL and SM):

"5.2 Technical Specification

5.2.1 Classification and Traffic Conditioning
		
This section paraphrases the applicable portions of Sections 3.6 and 4.2 
of [RFC5559].
		
Packets at the ingress to the domain are classified as either PCN
or non-PCN. Non-PCN packets may share the network with PCN packets
within the domain. Because the encoding specified in [RFC5696] and used 
in this document requires the use of the ECN fields, PCN-ingress-nodes 
MUST block ECN-capable traffic that uses the same DSCP as PCN from 
entering the PCN-domain directly.  "Blocking" means it is dropped or
downgraded to a lower-priority behaviour aggregate. Alternatively
such traffic MAY be tunnelled through the PCN-domain.
			
PCN packets are further classified as belonging or not belonging to
an admitted flow. PCN packets not belonging to an admitted flow are
dropped. (This assumes that requests for flow admission are signalled
in advance of the arrival of the flows themselves.) Packets belonging
to an admitted flow are policed to ensure that they adhere to the agreed
rate or flowspec.
		
5.2.2 PHB Configuration
		
The PCN SM and CL boundary node behaviours are metering and marking 
behaviours rather than scheduling behaviours. As a result, they are not 
tied to the selection of a specific DSCP value. The PCN working group 
suggests using admission control for the following service classes 
(defined in [RFC4594]):

    o  Telephony (EF)

    o  Real-time interactive (CS4)

    o  Broadcast Video (CS3)

    o  Multimedia Conferencing (AF4)

For a fuller discussion, see Section A.1 of Appendix A of [RFC5696]."

======================

>
> 8) in 5.7, the reader is referred to "the applicable specifications";
> can we identify the applicable specifications?

[PTT response] That will be RFCs 5559 as paraphrased above, plus RFC 
5696. Will fix, with section references.

>
> David Harrington
> Director, IETF Transport Area
> ietfdbh@comcast.net (preferred for ietf)
> dbharrington@huaweisymantec.com
> +1 603 828 1401 (cell)
>
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>
>

From toby@moncaster.com  Mon Dec 13 10:13:16 2010
Return-Path: <toby@moncaster.com>
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 A220E28C100 for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 10:13:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 D7gyoqbbTvbc for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 10:13:14 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by core3.amsl.com (Postfix) with ESMTP id 024B628C0E9 for <pcn@ietf.org>; Mon, 13 Dec 2010 10:13:13 -0800 (PST)
Received: from TobysHP (host86-141-37-244.range86-141.btcentralplus.com [86.141.37.244]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0LoMUn-1Q8RYY1qWH-00fvpV; Mon, 13 Dec 2010 19:14:46 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'David Harrington'" <ietfdbh@comcast.net>, "'Tom Taylor'" <tom111.taylor@bell.net>
References: <BLU0-SMTP56D06AAA0407A85C78D0AFD8120@phx.gbl> <29080878471B483A8DF97203AA7EAAAB@23FX1C1>
In-Reply-To: <29080878471B483A8DF97203AA7EAAAB@23FX1C1>
Date: Mon, 13 Dec 2010 18:14:43 -0000
Message-ID: <001a01cb9af1$9fc7d320$df577960$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acua39V4eMo8p5E7TQatd20hA2HD4gABwOVgAAKpI2A=
Content-Language: en-gb
X-Provags-ID: V02:K0:T5AdQfTICaSGkTKIgtnv4aBmdQ6nTCHbxqA/bokE/KA 35gSx0lMR6fpqZnUaGWvukMLWc03d+3A5+8o8e9SRiuTxUSLUK ljoVdLqXqYJJWeNspt8rMRrXjccyZt85y/FdGFW4nWfg9agkyj 532O2kwWf47xQARkZpQRKS13c6gZxVIOkOSIwlVkGRNJKZ49gY x4Cno4ow+E4sidt/o4AUl/s/UNJizUeE7z5mB+LmMk=
Cc: 'pcn' <pcn@ietf.org>
Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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: Mon, 13 Dec 2010 18:13:16 -0000

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> David Harrington
> Sent: 13 December 2010 17:01
> To: 'Tom Taylor'
> Cc: 'pcn'
> Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-
> behaviour-04
> 
> Hi,
> 
> This looks good. a few comments inline.
> 
> dbh
> 

<SNIP>

> >
> > 8) "PCN traffic" is used here, but where that term is defined is not
> > mentioned. Since this is used in formulae, that could be important
> to
> > understand correctly.
> >
> > [PTT response] I propose to add the following definition:
> >
> > PCN-traffic
> > 	An octet stream consisting of PCN-packets considered
> >          within a specific context.
> 
> Is PCN-packets defined?


Extract from RFC5559:

o  PCN-traffic, PCN-packets, PCN-BA: a PCN-domain carries traffic of
      different Diffserv behaviour aggregates (BAs) [RFC2474].  The
      PCN-BA uses the PCN mechanisms to carry PCN-traffic, and the
      corresponding packets are PCN-packets.  The same network will
      carry traffic of other Diffserv BAs.  The PCN-BA is distinguished
      by a combination of the Diffserv codepoint (DSCP) and ECN fields.




From ietfdbh@comcast.net  Mon Dec 13 11:01:35 2010
Return-Path: <ietfdbh@comcast.net>
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 3F6B928C0E9 for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 11:01:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 6lTOxYE1FgJ6 for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 11:01:34 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by core3.amsl.com (Postfix) with ESMTP id A5A443A6DEB for <pcn@ietf.org>; Mon, 13 Dec 2010 11:01:33 -0800 (PST)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta12.westchester.pa.mail.comcast.net with comcast id ihk71f0010SCNGk5Cj3CNX; Mon, 13 Dec 2010 19:03:12 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta09.westchester.pa.mail.comcast.net with comcast id ij361f00m2JQnJT3Vj38rL; Mon, 13 Dec 2010 19:03:10 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Toby Moncaster'" <toby@moncaster.com>, "'Tom Taylor'" <tom111.taylor@bell.net>
References: <BLU0-SMTP56D06AAA0407A85C78D0AFD8120@phx.gbl> <29080878471B483A8DF97203AA7EAAAB@23FX1C1> <001a01cb9af1$9fc7d320$df577960$@com>
Date: Mon, 13 Dec 2010 14:03:28 -0500
Message-ID: <1AED7DFB45A74CCBB9947A3B40F25962@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <001a01cb9af1$9fc7d320$df577960$@com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Thread-Index: Acua39V4eMo8p5E7TQatd20hA2HD4gABwOVgAAKpI2AAAZHZoA==
Cc: 'pcn' <pcn@ietf.org>
Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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: Mon, 13 Dec 2010 19:01:35 -0000

Hi,

There were a few places where a clear definition of PCN-packets or PCN
traffic would have made the spec less ambiguous. You might want to
include this definition text in the terminology section.

Normally, I do not encourage copying normative text from another
document, because keeping things in sync can be difficult, but here I
think it might be helpful. However, this document should be clear
where the normative definition is, so you might do something like:

o  PCN-traffic, PCN-packets, PCN-BA (from RFC 5559):
      a PCN-domain carries traffic of
      different Diffserv behaviour aggregates (BAs) [RFC2474].  The
      PCN-BA uses the PCN mechanisms to carry PCN-traffic, and the
      corresponding packets are PCN-packets.  The same network will
      carry traffic of other Diffserv BAs.  The PCN-BA is
distinguished
      by a combination of the Diffserv codepoint (DSCP) and ECN
fields. 

just a suggestion as a technical contributor.

dbh

> -----Original Message-----
> From: Toby Moncaster [mailto:toby@moncaster.com] 
> Sent: Monday, December 13, 2010 1:15 PM
> To: 'David Harrington'; 'Tom Taylor'
> Cc: 'pcn'
> Subject: RE: [PCN] Response to AD Review: 
> draft-ietf-pcn-sm-edge-behaviour-04
> 
> 
> 
> > -----Original Message-----
> > From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On 
> Behalf Of
> > David Harrington
> > Sent: 13 December 2010 17:01
> > To: 'Tom Taylor'
> > Cc: 'pcn'
> > Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-
> > behaviour-04
> > 
> > Hi,
> > 
> > This looks good. a few comments inline.
> > 
> > dbh
> > 
> 
> <SNIP>
> 
> > >
> > > 8) "PCN traffic" is used here, but where that term is 
> defined is not
> > > mentioned. Since this is used in formulae, that could be
important
> > to
> > > understand correctly.
> > >
> > > [PTT response] I propose to add the following definition:
> > >
> > > PCN-traffic
> > > 	An octet stream consisting of PCN-packets considered
> > >          within a specific context.
> > 
> > Is PCN-packets defined?
> 
> 
> Extract from RFC5559:
> 
> o  PCN-traffic, PCN-packets, PCN-BA: a PCN-domain carries traffic of
>       different Diffserv behaviour aggregates (BAs) [RFC2474].  The
>       PCN-BA uses the PCN mechanisms to carry PCN-traffic, and the
>       corresponding packets are PCN-packets.  The same network will
>       carry traffic of other Diffserv BAs.  The PCN-BA is 
> distinguished
>       by a combination of the Diffserv codepoint (DSCP) and 
> ECN fields.
> 
> 
> 


From toby@moncaster.com  Mon Dec 13 11:29:40 2010
Return-Path: <toby@moncaster.com>
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 21FE53A6DFB for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 11:29:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 IMHAVQApMnPb for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 11:29:39 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by core3.amsl.com (Postfix) with ESMTP id EA20D3A6D73 for <pcn@ietf.org>; Mon, 13 Dec 2010 11:29:38 -0800 (PST)
Received: from TobysHP (host86-141-37-244.range86-141.btcentralplus.com [86.141.37.244]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MLkJD-1PRxGT3RqN-000q2c; Mon, 13 Dec 2010 20:31:16 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'David Harrington'" <ietfdbh@comcast.net>, "'Tom Taylor'" <tom111.taylor@bell.net>
References: <BLU0-SMTP56D06AAA0407A85C78D0AFD8120@phx.gbl> <29080878471B483A8DF97203AA7EAAAB@23FX1C1> <001a01cb9af1$9fc7d320$df577960$@com> <1AED7DFB45A74CCBB9947A3B40F25962@23FX1C1>
In-Reply-To: <1AED7DFB45A74CCBB9947A3B40F25962@23FX1C1>
Date: Mon, 13 Dec 2010 19:31:15 -0000
Message-ID: <001e01cb9afc$4f982c00$eec88400$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acua39V4eMo8p5E7TQatd20hA2HD4gABwOVgAAKpI2AAAZHZoAAA+TIA
Content-Language: en-gb
X-Provags-ID: V02:K0:XDk5c+bO9IuB64XP7Pzo4tKezPj4UK2aWHovrtBG0w8 gQfUs88GM6cLeqgs5zxJzgrsmzV7cG6fQVx5WcnixoaM1k37/n fezPRVaBa71j9+iAGAaMaVRlkqwWI9zbmj1vm0HXHC6SsWs/WF aZf59iwkqydHfGpO7MSTSgWfIsI8D8cmBoued2funp2ayo+iQy nNosaLJQbfYHZ2Tl5S8fcxUe1Ketz1EQR7axJuNozY=
Cc: 'pcn' <pcn@ietf.org>
Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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: Mon, 13 Dec 2010 19:29:40 -0000

> -----Original Message-----
> From: David Harrington [mailto:ietfdbh@comcast.net]
> Sent: 13 December 2010 19:03
> To: 'Toby Moncaster'; 'Tom Taylor'
> Cc: 'pcn'
> Subject: RE: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-
> behaviour-04
> 
> Hi,
> 
> There were a few places where a clear definition of PCN-packets or PCN
> traffic would have made the spec less ambiguous. You might want to
> include this definition text in the terminology section.
> 
> Normally, I do not encourage copying normative text from another
> document, because keeping things in sync can be difficult, but here I
> think it might be helpful. However, this document should be clear
> where the normative definition is, so you might do something like:
> 
> o  PCN-traffic, PCN-packets, PCN-BA (from RFC 5559):
>       a PCN-domain carries traffic of
>       different Diffserv behaviour aggregates (BAs) [RFC2474].  The
>       PCN-BA uses the PCN mechanisms to carry PCN-traffic, and the
>       corresponding packets are PCN-packets.  The same network will
>       carry traffic of other Diffserv BAs.  The PCN-BA is
> distinguished
>       by a combination of the Diffserv codepoint (DSCP) and ECN
> fields.

How about:

* PCN-traffic, PCN-packets, PCN-BA. [RFC5559] defines these as:
	a PCN-domain carries traffic of
      different Diffserv behaviour aggregates (BAs) [RFC2474].  The
      PCN-BA uses the PCN mechanisms to carry PCN-traffic, and the
      corresponding packets are PCN-packets.  The same network will
      carry traffic of other Diffserv BAs.  The PCN-BA is distinguished
      by a combination of the Diffserv codepoint (DSCP) and ECN fields.

Which makes it clearer that the formal definition is in RFC5559...

It might also be helpful to include a list of defined terms that have been
used in the document and their normative source after the definitions
section. I know it takes some time, but it seemed to work well in RFC5696
(where a similar approach was used for the list of abbreviations).

Toby

> 
> just a suggestion as a technical contributor.
> 
> dbh
> 
> > -----Original Message-----
> > From: Toby Moncaster [mailto:toby@moncaster.com]
> > Sent: Monday, December 13, 2010 1:15 PM
> > To: 'David Harrington'; 'Tom Taylor'
> > Cc: 'pcn'
> > Subject: RE: [PCN] Response to AD Review:
> > draft-ietf-pcn-sm-edge-behaviour-04
> >
> >
> >
> > > -----Original Message-----
> > > From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On
> > Behalf Of
> > > David Harrington
> > > Sent: 13 December 2010 17:01
> > > To: 'Tom Taylor'
> > > Cc: 'pcn'
> > > Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-
> > > behaviour-04
> > >
> > > Hi,
> > >
> > > This looks good. a few comments inline.
> > >
> > > dbh
> > >
> >
> > <SNIP>
> >
> > > >
> > > > 8) "PCN traffic" is used here, but where that term is
> > defined is not
> > > > mentioned. Since this is used in formulae, that could be
> important
> > > to
> > > > understand correctly.
> > > >
> > > > [PTT response] I propose to add the following definition:
> > > >
> > > > PCN-traffic
> > > > 	An octet stream consisting of PCN-packets considered
> > > >          within a specific context.
> > >
> > > Is PCN-packets defined?
> >
> >
> > Extract from RFC5559:
> >
> > o  PCN-traffic, PCN-packets, PCN-BA: a PCN-domain carries traffic of
> >       different Diffserv behaviour aggregates (BAs) [RFC2474].  The
> >       PCN-BA uses the PCN mechanisms to carry PCN-traffic, and the
> >       corresponding packets are PCN-packets.  The same network will
> >       carry traffic of other Diffserv BAs.  The PCN-BA is
> > distinguished
> >       by a combination of the Diffserv codepoint (DSCP) and
> > ECN fields.
> >
> >
> >


From tom111.taylor@bell.net  Mon Dec 13 13:45:32 2010
Return-Path: <tom111.taylor@bell.net>
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 C0E7A3A6CC8 for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 13:45:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.76
X-Spam-Level: 
X-Spam-Status: No, score=-101.76 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 bCACi-PsWuPC for <pcn@core3.amsl.com>; Mon, 13 Dec 2010 13:45:32 -0800 (PST)
Received: from blu0-omc3-s5.blu0.hotmail.com (blu0-omc3-s5.blu0.hotmail.com [65.55.116.80]) by core3.amsl.com (Postfix) with ESMTP id 066D53A6EC1 for <pcn@ietf.org>; Mon, 13 Dec 2010 13:45:31 -0800 (PST)
Received: from BLU0-SMTP19 ([65.55.116.74]) by blu0-omc3-s5.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Dec 2010 13:47:10 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP19863534A0C7B30C0A2B01D8120@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP19.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Dec 2010 13:47:10 -0800
Date: Mon, 13 Dec 2010 16:47:09 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <BLU0-SMTP56D06AAA0407A85C78D0AFD8120@phx.gbl> <29080878471B483A8DF97203AA7EAAAB@23FX1C1>
In-Reply-To: <29080878471B483A8DF97203AA7EAAAB@23FX1C1>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Dec 2010 21:47:10.0192 (UTC) FILETIME=[4B650F00:01CB9B0F]
Cc: 'pcn' <pcn@ietf.org>
Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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: Mon, 13 Dec 2010 21:45:32 -0000

"PCN-packets" is defined in RFC 5559. So, I discover, is "PCN-traffic". 
What I will do is list the RFC 5559 terms used at the beginning of the 
terminology section.

On 13/12/2010 12:00 PM, David Harrington wrote:
> Hi,
>
> This looks good. a few comments inline.
>
> dbh
>
[snip]
>>
>> 8) "PCN traffic" is used here, but where that term is defined is not
>> mentioned. Since this is used in formulae, that could be important
> to
>> understand correctly.
>>
>> [PTT response] I propose to add the following definition:
>>
>> PCN-traffic			
>> 	An octet stream consisting of PCN-packets considered
>>           within a specific context.
>
> Is PCN-packets defined?
>


From toby@moncaster.com  Tue Dec 14 02:24:57 2010
Return-Path: <toby@moncaster.com>
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 3BA1B3A6F81 for <pcn@core3.amsl.com>; Tue, 14 Dec 2010 02:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 NAn37DRmdPS0 for <pcn@core3.amsl.com>; Tue, 14 Dec 2010 02:24:56 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by core3.amsl.com (Postfix) with ESMTP id 0F6163A6E3A for <pcn@ietf.org>; Tue, 14 Dec 2010 02:24:55 -0800 (PST)
Received: from TobysHP (host86-141-37-244.range86-141.btcentralplus.com [86.141.37.244]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0Lo3Ka-1Q8Pfx3iCO-00gFx1; Tue, 14 Dec 2010 11:26:30 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'Tom Taylor'" <tom111.taylor@bell.net>, "'David Harrington'" <ietfdbh@comcast.net>
References: <BLU0-SMTP56D06AAA0407A85C78D0AFD8120@phx.gbl>
In-Reply-To: <BLU0-SMTP56D06AAA0407A85C78D0AFD8120@phx.gbl>
Date: Tue, 14 Dec 2010 10:26:29 -0000
Message-ID: <001601cb9b79$5f1634b0$1d429e10$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: Acua39YQHtuYbWPiR4mXF1scYY7IDAAmQsiw
Content-Language: en-gb
X-Provags-ID: V02:K0:gTuZaQ1aN/HNiBDl+/6EYE7EIWwTg9Axbu9zenGHgwG xPV3rb1sUreOl/182gVMpW56rpc/p4rEX8xfOybOsggHT+TmJT b8z8Y0z0tTAJvqGFI194KEspVYeAadYxHr0SHlKfj55SJvnekB p5tJnvv7/IungmSnI+0EHspTJbwiJbjKM+f4Uc0C+9BLNkW6n4 z1e1Ypj0Q5K8mqZMAqiuoUMbmddUsu7y73auaMc05w=
Cc: 'pcn' <pcn@ietf.org>
Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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, 14 Dec 2010 10:24:57 -0000

One comment

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Tom Taylor
> Sent: 13 December 2010 16:07
> To: David Harrington
> Cc: pcn
> Subject: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-
> 04
> 

<SNIP>

> 
> ----------------
> 
> [PTT response] I propose that we:
> 
>   a) Add the following paragraph at the end of Section 1 (CL version
> shown):
> 
> "A companion document [I-D.SM-edge-behaviour] specifies the Single
> Marking (SM) PCN-boundary-node behaviour. This document and
> [I-D.SM-edge-behaviour] have a great deal of text in common. To
> simplify
> the task of the reader, the text in the present document that is
> specific to the CL PCN-boundary-node behaviour is preceded by the
> phrase: "[CL-specific]". A similar distinction for SM-specific text is
> made in [I-D.SM-edge-behaviour]."
> 
> b) Take a diff between CL-07 and SM-04, eliminate the purely editorial
> differences, and tag the technical differences as indicated by the
> above
> paragraph.


I personally feel we don't need to tag the differences. Certainly eliminate
any unnecessary textual differences, but if you start tagging things you may
end up confusing developers, many of whom don't speak English as a first
language... My suggestion is put in the paragraph explaining that the two
documents are similar but omit the tagging. Hopefully these can go through
rfc-editor as a pair and get consecutive numbers which will make it easier
for people to realise they are related docs...

Toby





From tom111.taylor@bell.net  Tue Dec 14 05:44:18 2010
Return-Path: <tom111.taylor@bell.net>
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 BFB113A6F5D for <pcn@core3.amsl.com>; Tue, 14 Dec 2010 05:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.761
X-Spam-Level: 
X-Spam-Status: No, score=-101.761 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 RjstxhEKj5SZ for <pcn@core3.amsl.com>; Tue, 14 Dec 2010 05:44:17 -0800 (PST)
Received: from blu0-omc3-s12.blu0.hotmail.com (blu0-omc3-s12.blu0.hotmail.com [65.55.116.87]) by core3.amsl.com (Postfix) with ESMTP id 4C2B03A6E8F for <pcn@ietf.org>; Tue, 14 Dec 2010 05:44:17 -0800 (PST)
Received: from BLU0-SMTP75 ([65.55.116.72]) by blu0-omc3-s12.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 14 Dec 2010 05:45:57 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP7521FE220827956F7464F8D8130@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP75.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 14 Dec 2010 05:45:56 -0800
Date: Tue, 14 Dec 2010 08:45:56 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <FEF2029CCC614C6A80884469A91E0015@23FX1C1>
In-Reply-To: <FEF2029CCC614C6A80884469A91E0015@23FX1C1>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Dec 2010 13:45:56.0751 (UTC) FILETIME=[3BE559F0:01CB9B95]
Cc: pcn@ietf.org
Subject: [PCN] Response to AD Review: draft-ietf-pcn-cl-edge-behaviour-07
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/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, 14 Dec 2010 13:44:18 -0000

This is a repeat of yesterday's mail with a new subject line, since no 
one seems to have noticed it.

On 06/12/2010 3:56 PM, David Harrington wrote:
> Hi,
>
> Because this document has so much common text with the SM document,
> almost all the AD Review comments for the SM document apply to CL as
> well. Please incorporate those comments into this review.

[PTT response] OK

======================
>
> A few comments came to mind after sending the SM review, that apply to
> both; I added parenthesis to indictae it applies to both).
>
> 1) in section 2, reference is made to the "possible extension"
> [ID.PCN3in1].
> I recommend against referencing "possible extension" documents.

[PTT response] I propose to rewrite Section 2. The essence of the 
changes is to base the encoding entirely on RFC 5696, while leaving room 
for an unidentified successor document. Mention of I-D.PCN3in1 will also 
be dropped from the PDB template (see below).

Here is the proposed text for the CL document:

"2. [CL-Specific] Assumed Core Network Behaviour for CL	
				
This section describes the assumed behaviour for nodes of the PCN-domain 
when acting in their role as PCN-interior-nodes. The CL mode	
of operation assumes that:	
				
   o PCN-interior-nodes perform both threshold-marking and 
excess-traffic-marking of packets, according to the rules 
specified in		[RFC5670];	
				
   o excess-traffic-marking of packets uses the PCN-Marked (PM) 
codepoint defined in [RFC5696];			
				
   o threshold-marking of packets uses the EXP codepoint defined in 
[RFC5696];	
				
   o the PCN-domain satisfies the conditions specified in [RFC5696];	
				
   o on each link the reference rate for the threshold-meter is 
configured to be equal to the PCN-admissible-rate for the link;		
				
   o on each link the reference rate for the excess traffic meter is 
configured to be equal to the PCN-supportable-rate for the link;	
				
   o the set of valid codepoint transitions is as shown in Section 4.2 
of [RFC5696]."	

As a follow-up, it is proposed to add clauses indicating the packet 
marking in section 3.2.1 for the different rates. The text would become:

"The PCN-egress-node MUST meter received PCN-traffic in order to derive 
periodically the following rates for each ingress-egress-aggregate 
passing through it:	
				
   o NM-rate: octets per second of PCN-traffic in PCN-packets that are 
not-marked (i.e., marked with the NM codepoint);			
				
   o [CL-specific] ThM-rate: octets per second of PCN-traffic in 
PCN-packets that are threshold-marked (i.e., marked with the PM	 
codepoint);				
				
   o [CL-specific] ETM-rate: octets per second of PCN-traffic in 
PCN-packets that are excess-traffic-marked (i.e., marked with the EXP 
codepoint).

Similar changes would be made to the SM document.

======================
	
>
> 2) "These allowable transitions are specified here" - usually
> specified implies a normative specification. I suggest rewording with
> less normative-like wording.

[PTT response] Replaced by reference to the normative document. See above.

======================
>
> 3) in 3.2.3, the calculation for CLE uses either the latest or the
> previous interval in its caculations. Niether SM nor CL explains why
> it is acceptable to use either interval. Is this explained somewhere?
> How does this affect interoperability? (also applies to SM)
>
[PTT response] Will reword to make it clear that both conditions must be 
tested.

======================

> 4) in 3.3.2, the DP MUST request an estimate of pcn-sent-rate; is
> there a specific protocol that must/should be used to do this
> (assuming they are not co-located)? If not, how is this
> request/response done in a vendor-interoperable manner?

[PTT response] Answered in previous note. Protocol specification is 
still to be done but is explicitly outside the PCN WG charter.
>
> 5) in 3.3.2, last paragraph, the list must be ETM-marked flows, right?
> It doesn't say that.

[PTT response] Will add.

======================
>
> 6) in 3.3., an alarm should be raised to management. is there are
> standardized approach to raising the alarm? If not, how does this
> affect interoperability. Most notably, if two nodes form different
> vendors raise an alarm using different protocols, how will the
> management system correlate the alarms? If two implementations use
> SNMP to raise the alarms, should they use consistent OIDs to identify
> the problem? or consistent syslog SDEs? or consistent ipfix IEs?
> Should the WG standardize the information models, and possibly data
> models and protocols, for reporting such alarms?

[PTT response] This is a topic for another document. The work item seems 
to be missing from the WG charter.

======================
>
> 7) in 5.2, it is asserted that [ID.PCN3in1] specifies the behavior;
> but 2.2 mentions this as a "possible extension". If PCN3in1 is not
> STDS track, then i think this text in 5.2 could be problematic. But I
> suspect that 3086 expects a stable specification.

[PTT response] Reference to that I-D will be dropped.

======================

>
> I have not worked with the 3086 template before. Is a reference to a
> number of RFCs, without any discussion of their details really
> sufficient? It doesn't sounce like that meets the description from
> 3086:
>
>     This section specifies the rules or guidelines to create this PDB,
>     each distinguished with "may", "must" and "should." The technical
>     specification must list the classification and traffic conditioning
>     required (if any) and the PHB (or PHBs) to be used with any
>     additional requirements on their configuration beyond that
> contained
>     in RFCs.  Classification can reflect the results of an admission
>     control process.  Traffic conditioning may include marking, traffic
>     shaping, and policing.  A Service Provisioning Policy might be used
>     to describe the technical specification of a particular PDB.

[PTT response] The only use of the template I could readily find as a 
model was RFC 3662. Proposed to use the following text (common to both 
CL and SM):

"5.2 Technical Specification

5.2.1 Classification and Traffic Conditioning
		
This section paraphrases the applicable portions of Sections 3.6 and 4.2 
of [RFC5559].
		
Packets at the ingress to the domain are classified as either PCN
or non-PCN. Non-PCN packets may share the network with PCN packets
within the domain. Because the encoding specified in [RFC5696] and used 
in this document requires the use of the ECN fields, PCN-ingress-nodes 
MUST block ECN-capable traffic that uses the same DSCP as PCN from 
entering the PCN-domain directly.  "Blocking" means it is dropped or
downgraded to a lower-priority behaviour aggregate. Alternatively
such traffic MAY be tunnelled through the PCN-domain.
			
PCN packets are further classified as belonging or not belonging to
an admitted flow. PCN packets not belonging to an admitted flow are
dropped. (This assumes that requests for flow admission are signalled
in advance of the arrival of the flows themselves.) Packets belonging
to an admitted flow are policed to ensure that they adhere to the agreed
rate or flowspec.
		
5.2.2 PHB Configuration
		
The PCN SM and CL boundary node behaviours are metering and marking 
behaviours rather than scheduling behaviours. As a result, they are not 
tied to the selection of a specific DSCP value. The PCN working group 
suggests using admission control for the following service classes 
(defined in [RFC4594]):

    o  Telephony (EF)

    o  Real-time interactive (CS4)

    o  Broadcast Video (CS3)

    o  Multimedia Conferencing (AF4)

For a fuller discussion, see Section A.1 of Appendix A of [RFC5696]."

======================

>
> 8) in 5.7, the reader is referred to "the applicable specifications";
> can we identify the applicable specifications?

[PTT response] That will be RFCs 5559 as paraphrased above, plus RFC 
5696. Will fix, with section references.

>
> David Harrington
> Director, IETF Transport Area
> ietfdbh@comcast.net (preferred for ietf)
> dbharrington@huaweisymantec.com
> +1 603 828 1401 (cell)
>
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>
>
_______________________________________________
PCN mailing list
PCN@ietf.org
https://www.ietf.org/mailman/listinfo/pcn



From tom111.taylor@bell.net  Tue Dec 14 06:13:35 2010
Return-Path: <tom111.taylor@bell.net>
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 03AA23A6E9B for <pcn@core3.amsl.com>; Tue, 14 Dec 2010 06:13:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.762
X-Spam-Level: 
X-Spam-Status: No, score=-101.762 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 dOgHJttysxUY for <pcn@core3.amsl.com>; Tue, 14 Dec 2010 06:13:34 -0800 (PST)
Received: from blu0-omc3-s38.blu0.hotmail.com (blu0-omc3-s38.blu0.hotmail.com [65.55.116.113]) by core3.amsl.com (Postfix) with ESMTP id 256533A6DA9 for <pcn@ietf.org>; Tue, 14 Dec 2010 06:13:33 -0800 (PST)
Received: from BLU0-SMTP23 ([65.55.116.74]) by blu0-omc3-s38.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 14 Dec 2010 06:15:14 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP237FF045ACB98F8FF658D9D8130@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP23.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 14 Dec 2010 06:15:13 -0800
Date: Tue, 14 Dec 2010 09:15:13 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Toby Moncaster <toby@moncaster.com>
References: <BLU0-SMTP56D06AAA0407A85C78D0AFD8120@phx.gbl> <001601cb9b79$5f1634b0$1d429e10$@com>
In-Reply-To: <001601cb9b79$5f1634b0$1d429e10$@com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Dec 2010 14:15:13.0960 (UTC) FILETIME=[53462A80:01CB9B99]
Cc: 'pcn' <pcn@ietf.org>
Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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, 14 Dec 2010 14:13:35 -0000

How about a compromise: leave the tags in for review, but have an RFC 
Editor's note calling for their removal (and removal of the explanatory 
paragraph) before publication.

On 14/12/2010 5:26 AM, Toby Moncaster wrote:
> One comment
>
>> -----Original Message-----
>> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
>> Tom Taylor
>> Sent: 13 December 2010 16:07
>> To: David Harrington
>> Cc: pcn
>> Subject: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-
>> 04
>>
>
> <SNIP>
>
>>
>> ----------------
>>
>> [PTT response] I propose that we:
>>
>>    a) Add the following paragraph at the end of Section 1 (CL version
>> shown):
>>
>> "A companion document [I-D.SM-edge-behaviour] specifies the Single
>> Marking (SM) PCN-boundary-node behaviour. This document and
>> [I-D.SM-edge-behaviour] have a great deal of text in common. To
>> simplify
>> the task of the reader, the text in the present document that is
>> specific to the CL PCN-boundary-node behaviour is preceded by the
>> phrase: "[CL-specific]". A similar distinction for SM-specific text is
>> made in [I-D.SM-edge-behaviour]."
>>
>> b) Take a diff between CL-07 and SM-04, eliminate the purely editorial
>> differences, and tag the technical differences as indicated by the
>> above
>> paragraph.
>
>
> I personally feel we don't need to tag the differences. Certainly eliminate
> any unnecessary textual differences, but if you start tagging things you may
> end up confusing developers, many of whom don't speak English as a first
> language... My suggestion is put in the paragraph explaining that the two
> documents are similar but omit the tagging. Hopefully these can go through
> rfc-editor as a pair and get consecutive numbers which will make it easier
> for people to realise they are related docs...
>
> Toby
>
>
>
>
>
>

From toby@moncaster.com  Tue Dec 14 06:16:37 2010
Return-Path: <toby@moncaster.com>
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 123603A6F5D for <pcn@core3.amsl.com>; Tue, 14 Dec 2010 06:16:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 Aobb9CIr+aeW for <pcn@core3.amsl.com>; Tue, 14 Dec 2010 06:16:36 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by core3.amsl.com (Postfix) with ESMTP id 0577A3A6E9E for <pcn@ietf.org>; Tue, 14 Dec 2010 06:16:36 -0800 (PST)
Received: from TobysHP (host86-170-51-241.range86-170.btcentralplus.com [86.170.51.241]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MR93L-1Pt4Sz1O0N-00UPor; Tue, 14 Dec 2010 15:18:10 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'Tom Taylor'" <tom111.taylor@bell.net>
References: <BLU0-SMTP56D06AAA0407A85C78D0AFD8120@phx.gbl> <001601cb9b79$5f1634b0$1d429e10$@com> <BLU0-SMTP237FF045ACB98F8FF658D9D8130@phx.gbl>
In-Reply-To: <BLU0-SMTP237FF045ACB98F8FF658D9D8130@phx.gbl>
Date: Tue, 14 Dec 2010 14:18:09 -0000
Message-ID: <000001cb9b99$bc931b10$35b95130$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcubmVPkKjohRbhxSOW0lGv6DHxgSgAAGFqw
Content-Language: en-gb
X-Provags-ID: V02:K0:/T+86vK44S9HYBvGwpWi+b/aUih8M5wNH1av//99rkc 9VzuFX9pYKJ/gwJRab8TeGsie7uieUSplh1NXexj6eNVEMHVZ5 dwrIKq4T9bfsEcrd0uzBTB/jURAUeRcoh4p3mlbOlf5g1bJkg6 kDcCjTe2qPBWzx2nsn4/6wfd6OWIVA047vS4Cu0jQr3rIeHeGP 8qU3uZ7j70aoviGUSECF7kWhYrBTf6Fg717otvS+BQ=
Cc: 'pcn' <pcn@ietf.org>
Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-behaviour-04
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/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, 14 Dec 2010 14:16:37 -0000

Sounds extremely sensible to me!

> -----Original Message-----
> From: Tom Taylor [mailto:tom111.taylor@bell.net]
> Sent: 14 December 2010 14:15
> To: Toby Moncaster
> Cc: 'David Harrington'; 'pcn'
> Subject: Re: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-
> behaviour-04
> 
> How about a compromise: leave the tags in for review, but have an RFC
> Editor's note calling for their removal (and removal of the explanatory
> paragraph) before publication.
> 
> On 14/12/2010 5:26 AM, Toby Moncaster wrote:
> > One comment
> >
> >> -----Original Message-----
> >> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf
> Of
> >> Tom Taylor
> >> Sent: 13 December 2010 16:07
> >> To: David Harrington
> >> Cc: pcn
> >> Subject: [PCN] Response to AD Review: draft-ietf-pcn-sm-edge-
> behaviour-
> >> 04
> >>
> >
> > <SNIP>
> >
> >>
> >> ----------------
> >>
> >> [PTT response] I propose that we:
> >>
> >>    a) Add the following paragraph at the end of Section 1 (CL
> version
> >> shown):
> >>
> >> "A companion document [I-D.SM-edge-behaviour] specifies the Single
> >> Marking (SM) PCN-boundary-node behaviour. This document and
> >> [I-D.SM-edge-behaviour] have a great deal of text in common. To
> >> simplify
> >> the task of the reader, the text in the present document that is
> >> specific to the CL PCN-boundary-node behaviour is preceded by the
> >> phrase: "[CL-specific]". A similar distinction for SM-specific text
> is
> >> made in [I-D.SM-edge-behaviour]."
> >>
> >> b) Take a diff between CL-07 and SM-04, eliminate the purely
> editorial
> >> differences, and tag the technical differences as indicated by the
> >> above
> >> paragraph.
> >
> >
> > I personally feel we don't need to tag the differences. Certainly
> eliminate
> > any unnecessary textual differences, but if you start tagging things
> you may
> > end up confusing developers, many of whom don't speak English as a
> first
> > language... My suggestion is put in the paragraph explaining that the
> two
> > documents are similar but omit the tagging. Hopefully these can go
> through
> > rfc-editor as a pair and get consecutive numbers which will make it
> easier
> > for people to realise they are related docs...
> >
> > Toby
> >
> >
> >
> >
> >
> >


From tom111.taylor@bell.net  Wed Dec 15 20:54:49 2010
Return-Path: <tom111.taylor@bell.net>
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 BF15728C13B for <pcn@core3.amsl.com>; Wed, 15 Dec 2010 20:54:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.763
X-Spam-Level: 
X-Spam-Status: No, score=-101.763 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 9ovE8dX2xh95 for <pcn@core3.amsl.com>; Wed, 15 Dec 2010 20:54:48 -0800 (PST)
Received: from blu0-omc3-s34.blu0.hotmail.com (blu0-omc3-s34.blu0.hotmail.com [65.55.116.109]) by core3.amsl.com (Postfix) with ESMTP id CB51E28C121 for <pcn@ietf.org>; Wed, 15 Dec 2010 20:54:48 -0800 (PST)
Received: from BLU0-SMTP69 ([65.55.116.74]) by blu0-omc3-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 15 Dec 2010 20:56:32 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP6925E6F0F2A375BD4A4E6CD8150@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP69.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 15 Dec 2010 20:56:31 -0800
Date: Wed, 15 Dec 2010 23:56:29 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: pcn <pcn@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Dec 2010 04:56:31.0413 (UTC) FILETIME=[9B1AEE50:01CB9CDD]
Subject: [PCN] draft-ietf-pcn-cl-edge-behaviour-08 posted
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/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: Thu, 16 Dec 2010 04:54:49 -0000

I have submitted draft-ietf-pcn-cl-edge-behaviour-08 with the changes 
indicated in my two responses to the AD review notes, modified by list 
discussion. Please have a look while I finish updating the SM draft.

Diff is available at

http://tools.ietf.org/rfcdiff?url2=draft-ietf-pcn-cl-edge-behaviour-08

Tom Taylor

From Internet-Drafts@ietf.org  Wed Dec 15 21:00:03 2010
Return-Path: <Internet-Drafts@ietf.org>
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 1407B28C13B; Wed, 15 Dec 2010 21:00:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 AT1OktzzYPiW; Wed, 15 Dec 2010 21:00:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EC2B28C121; Wed, 15 Dec 2010 21:00:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20101216050002.3841.51837.idtracker@localhost>
Date: Wed, 15 Dec 2010 21:00:02 -0800
Cc: pcn@ietf.org
Subject: [PCN] I-D Action:draft-ietf-pcn-cl-edge-behaviour-08.txt
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/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: Thu, 16 Dec 2010 05:00:03 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Congestion and Pre-Congestion Notification Working Group of the IETF.


	Title           : PCN Boundary Node Behaviour for the Controlled Load (CL) Mode of Operation
	Author(s)       : A. Charny, et al.
	Filename        : draft-ietf-pcn-cl-edge-behaviour-08.txt
	Pages           : 22
	Date            : 2010-12-15

Pre-congestion notification (PCN) is a means for protecting the
quality of service for inelastic traffic admitted to a Diffserv
domain.  The overall PCN architecture is described in RFC 5559.  This
memo is one of a series describing possible boundary node behaviours
for a PCN-domain.  The behaviour described here is that for a form of
measurement-based load control using three PCN marking states, not-
marked, threshold-marked, and excess-traffic-marked.  This behaviour
is known informally as the Controlled Load (CL) PCN-boundary-node
behaviour.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pcn-cl-edge-behaviour-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pcn-cl-edge-behaviour-08.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-12-15205113.I-D@ietf.org>


--NextPart--

From karagian@cs.utwente.nl  Thu Dec 16 01:09:06 2010
Return-Path: <karagian@cs.utwente.nl>
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 E57903A70A5 for <pcn@core3.amsl.com>; Thu, 16 Dec 2010 01:09:06 -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 EmrrwpBpedR1 for <pcn@core3.amsl.com>; Thu, 16 Dec 2010 01:09:06 -0800 (PST)
Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11]) by core3.amsl.com (Postfix) with ESMTP id B8ACA3A6FF2 for <pcn@ietf.org>; Thu, 16 Dec 2010 01:09:05 -0800 (PST)
Received: from webmail.cs.utwente.nl (janus.ewi.utwente.nl [130.89.10.26]) by denhaag.ewi.utwente.nl (8.13.6/8.13.6) with SMTP id oBG9AZBd022314;  Thu, 16 Dec 2010 10:10:35 +0100 (MET)
Received: from 84.82.109.231 (auth. user karagian@imap1.ewi.utwente.nl) by webmail.cs.utwente.nl with HTTP; Thu, 16 Dec 2010 09:10:36 +0000
To: "Tom Taylor" <tom111.taylor@bell.net>, "pcn" <pcn@ietf.org>
Date: Thu, 16 Dec 2010 09:10:36 +0000
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <CKFgVPYw.1292490636.6483400.karagian@ewi.utwente.nl>
In-Reply-To: <BLU0-SMTP6925E6F0F2A375BD4A4E6CD8150@phx.gbl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Errors-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (denhaag.ewi.utwente.nl [130.89.10.11]); Thu, 16 Dec 2010 10:10:44 +0100 (MET)
Subject: Re: [PCN] draft-ietf-pcn-cl-edge-behaviour-08 posted
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/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: Thu, 16 Dec 2010 09:09:07 -0000

Hi Tom

Thank you very much!

It looks good to me!

Best regards,
Georgios

On 12/16/2010, "Tom Taylor" <tom111.taylor@bell.net> wrote:

>I have submitted draft-ietf-pcn-cl-edge-behaviour-08 with the changes
>indicated in my two responses to the AD review notes, modified by list
>discussion. Please have a look while I finish updating the SM draft.
>
>Diff is available at
>
>http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcn-cl-edge-behaviour-08
>
>Tom Taylor
>_______________________________________________
>PCN mailing list
>PCN@ietf.org
>https://www.ietf.org/mailman/listinfo/pcn

From Internet-Drafts@ietf.org  Thu Dec 16 11:30:02 2010
Return-Path: <Internet-Drafts@ietf.org>
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 839553A69A7; Thu, 16 Dec 2010 11:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 HHNcukpcM23O; Thu, 16 Dec 2010 11:30:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D0683A6968; Thu, 16 Dec 2010 11:30:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20101216193001.3294.83589.idtracker@localhost>
Date: Thu, 16 Dec 2010 11:30:01 -0800
Cc: pcn@ietf.org
Subject: [PCN] I-D Action:draft-ietf-pcn-sm-edge-behaviour-05.txt
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/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: Thu, 16 Dec 2010 19:30:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Congestion and Pre-Congestion Notification Working Group of the IETF.


	Title           : PCN Boundary Node Behaviour for the Single Marking (SM) Mode of Operation
	Author(s)       : A. Charny, et al.
	Filename        : draft-ietf-pcn-sm-edge-behaviour-05.txt
	Pages           : 19
	Date            : 2010-12-16

Pre-congestion notification (PCN) is a means for protecting the
quality of service for inelastic traffic admitted to a Diffserv
domain.  The overall PCN architecture is described in RFC 5559.  This
memo is one of a series describing possible boundary node behaviours
for a PCN-domain.  The behaviour described here is that for a form of
measurement-based load control using two PCN marking states, not-
marked, and excess-traffic-marked.  This behaviour is known
informally as the Single Marking (SM) PCN edge behaviour.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pcn-sm-edge-behaviour-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pcn-sm-edge-behaviour-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-12-16111848.I-D@ietf.org>


--NextPart--

From tom111.taylor@bell.net  Thu Dec 16 11:36:50 2010
Return-Path: <tom111.taylor@bell.net>
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 71BEA3A69B7 for <pcn@core3.amsl.com>; Thu, 16 Dec 2010 11:36:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.764
X-Spam-Level: 
X-Spam-Status: No, score=-101.764 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 qVv0Zzf8OMQL for <pcn@core3.amsl.com>; Thu, 16 Dec 2010 11:36:49 -0800 (PST)
Received: from blu0-omc1-s8.blu0.hotmail.com (blu0-omc1-s8.blu0.hotmail.com [65.55.116.19]) by core3.amsl.com (Postfix) with ESMTP id 984023A697D for <pcn@ietf.org>; Thu, 16 Dec 2010 11:36:49 -0800 (PST)
Received: from BLU0-SMTP51 ([65.55.116.9]) by blu0-omc1-s8.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 16 Dec 2010 11:38:34 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP51B13FA4B2C6B09D9ABBEDD8150@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP51.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 16 Dec 2010 11:38:33 -0800
Date: Thu, 16 Dec 2010 14:38:32 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: pcn <pcn@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Dec 2010 19:38:33.0392 (UTC) FILETIME=[D3101300:01CB9D58]
Subject: [PCN] Fwd: New Version Notification - draft-ietf-pcn-sm-edge-behaviour-05.txt
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/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: Thu, 16 Dec 2010 19:36:50 -0000

I have updated and submitted the SM draft. Unfortunately, I did a final 
diff check between it and the CL draft *after* submission and found a 
few discrepancies. Earlier I found some changes that needed to be made 
in the CL draft. I stand ready to submit new versions of both to fix 
these primarily editorial glitches, but I'll wait until people have had 
a chance to check out the main sets of updates as provided in the 
current versions.

-------- Original Message --------
Subject: New Version Notification - draft-ietf-pcn-sm-edge-behaviour-05.txt
Date: Thu, 16 Dec 2010 11:30:01 -0800
From: Internet-Draft@ietf.org
To: pcn-chairs@tools.ietf.org, 
draft-ietf-pcn-sm-edge-behaviour@tools.ietf.org,	ietfdbh@comcast.net

New version (-05) has been submitted for 
draft-ietf-pcn-sm-edge-behaviour-05.txt.
http://www.ietf.org/internet-drafts/draft-ietf-pcn-sm-edge-behaviour-05.txt
Sub state has been changed to AD Follow up from New Id Needed

Diff from previous version:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-pcn-sm-edge-behaviour-05

IETF Secretariat.



From karagian@cs.utwente.nl  Thu Dec 16 12:04:20 2010
Return-Path: <karagian@cs.utwente.nl>
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 4B9163A6920 for <pcn@core3.amsl.com>; Thu, 16 Dec 2010 12:04:20 -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 Vjsf5Q55LSEe for <pcn@core3.amsl.com>; Thu, 16 Dec 2010 12:04:19 -0800 (PST)
Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11]) by core3.amsl.com (Postfix) with ESMTP id 3CE263A6919 for <pcn@ietf.org>; Thu, 16 Dec 2010 12:04:18 -0800 (PST)
Received: from webmail.cs.utwente.nl (janus.ewi.utwente.nl [130.89.10.26]) by denhaag.ewi.utwente.nl (8.13.6/8.13.6) with SMTP id oBGK5nhw006316;  Thu, 16 Dec 2010 21:05:49 +0100 (MET)
Received: from 84.82.109.231 (auth. user karagian@imap1.ewi.utwente.nl) by webmail.cs.utwente.nl with HTTP; Thu, 16 Dec 2010 20:05:51 +0000
To: "Tom Taylor" <tom111.taylor@bell.net>, "pcn" <pcn@ietf.org>
Date: Thu, 16 Dec 2010 20:05:50 +0000
X-Mailer: IlohaMail/0.8.13 (On: webmail.cs.utwente.nl)
Message-ID: <ifmCY4SY.1292529950.9334330.karagian@ewi.utwente.nl>
In-Reply-To: <BLU0-SMTP51B13FA4B2C6B09D9ABBEDD8150@phx.gbl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Bounce-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
Errors-To: "Georgios Karagiannis" <karagian@cs.utwente.nl>
MIME-Version: 1.0 
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (denhaag.ewi.utwente.nl [130.89.10.11]); Thu, 16 Dec 2010 21:05:58 +0100 (MET)
Subject: Re: [PCN] Fwd: New Version Notification - draft-ietf-pcn-sm-edge-behaviour-05.txt
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/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: Thu, 16 Dec 2010 20:04:20 -0000

Hi Tom

Thank you very much!
I think that the draft looks good, but regarding factor U, I think that
the following sentence should be changed from:

U is a configurable
       factor greater than one which is the same for all ingress-egress-
       aggregates.

INTO:

U is a configurable
       factor greater than or equal to one which is the same for all
       ingress-egress-aggregates.


Best regards,
Georgios


On 12/16/2010, "Tom Taylor" <tom111.taylor@bell.net> wrote:

>I have updated and submitted the SM draft. Unfortunately, I did a final
>diff check between it and the CL draft *after* submission and found a
>few discrepancies. Earlier I found some changes that needed to be made
>in the CL draft. I stand ready to submit new versions of both to fix
>these primarily editorial glitches, but I'll wait until people have had
>a chance to check out the main sets of updates as provided in the
>current versions.
>
>-------- Original Message --------
>Subject: New Version Notification - draft-ietf-pcn-sm-edge-behaviour-05.txt
>Date: Thu, 16 Dec 2010 11:30:01 -0800
>From: Internet-Draft@ietf.org
>To: pcn-chairs@tools.ietf.org,
>draft-ietf-pcn-sm-edge-behaviour@tools.ietf.org,=09ietfdbh@comcast.net
>
>New version (-05) has been submitted for
>draft-ietf-pcn-sm-edge-behaviour-05.txt.
>http://www.ietf.org/internet-drafts/draft-ietf-pcn-sm-edge-behaviour-05.txt
>Sub state has been changed to AD Follow up from New Id Needed
>
>Diff from previous version:
>http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcn-sm-edge-behaviour-05
>
>IETF Secretariat.
>
>
>_______________________________________________
>PCN mailing list
>PCN@ietf.org
>https://www.ietf.org/mailman/listinfo/pcn

From menth@informatik.uni-tuebingen.de  Thu Dec 16 14:19:27 2010
Return-Path: <menth@informatik.uni-tuebingen.de>
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 441E43A6934 for <pcn@core3.amsl.com>; Thu, 16 Dec 2010 14:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.148
X-Spam-Level: 
X-Spam-Status: No, score=-1.148 tagged_above=-999 required=5 tests=[AWL=1.101,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 SD6jZWRjmc4h for <pcn@core3.amsl.com>; Thu, 16 Dec 2010 14:19:26 -0800 (PST)
Received: from mx5.informatik.uni-tuebingen.de (mx5.informatik.uni-tuebingen.de [134.2.12.32]) by core3.amsl.com (Postfix) with SMTP id AEC6B3A6915 for <pcn@ietf.org>; Thu, 16 Dec 2010 14:19:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.informatik.uni-tuebingen.de (Postfix) with ESMTP id B436D5286 for <pcn@ietf.org>; Thu, 16 Dec 2010 23:21:06 +0100 (MET)
X-Virus-Scanned: amavisd-new at informatik.uni-tuebingen.de
Received: from mx5.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx5.informatik.uni-tuebingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fjNdgdfpwF0u for <pcn@ietf.org>; Thu, 16 Dec 2010 23:21:01 +0100 (MET)
Received: from zcs-bs.informatik.uni-tuebingen.de (zcs-bs.Informatik.Uni-Tuebingen.De [134.2.12.62]) by mx5.informatik.uni-tuebingen.de (Postfix) with ESMTP id D04E35274 for <pcn@ietf.org>; Thu, 16 Dec 2010 23:21:00 +0100 (MET)
Received: from [192.168.1.100] (HSI-KBW-095-208-114-108.hsi5.kabel-badenwuerttemberg.de [95.208.114.108]) by zcs-bs.informatik.uni-tuebingen.de (Postfix) with ESMTP id 43893F1F41A for <pcn@ietf.org>; Thu, 16 Dec 2010 23:20:59 +0100 (CET)
Message-ID: <4D0A90CA.4000604@informatik.uni-tuebingen.de>
Date: Thu, 16 Dec 2010 23:20:58 +0100
From: Michael Menth <menth@informatik.uni-tuebingen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: pcn@ietf.org
References: <ifmCY4SY.1292529950.9334330.karagian@ewi.utwente.nl>
In-Reply-To: <ifmCY4SY.1292529950.9334330.karagian@ewi.utwente.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PCN] Fwd: New Version Notification -	draft-ietf-pcn-sm-edge-behaviour-05.txt
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/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: Thu, 16 Dec 2010 22:19:27 -0000

Hi Tom, hi Georgios,

Am 16.12.2010 21:05, schrieb Georgios Karagiannis:
> Hi Tom
>
> Thank you very much!
> I think that the draft looks good, but regarding factor U, I think that
> the following sentence should be changed from:
>
> U is a configurable
>         factor greater than one which is the same for all ingress-egres=
s-
>         aggregates.
>
> INTO:
>
> U is a configurable
>         factor greater than or equal to one which is the same for all
>         ingress-egress-aggregates.

I don't think that "equal" makes sense. This implies that the admissible=20
rate equals the supportable rate. In such a system, flows are terminated=20
as soon as admission control blocks. This is unlikely to be a sensible=20
configuration.

Best wishes,

     Michael

>
> Best regards,
> Georgios
>
>
> On 12/16/2010, "Tom Taylor"<tom111.taylor@bell.net>  wrote:
>
>> I have updated and submitted the SM draft. Unfortunately, I did a fina=
l
>> diff check between it and the CL draft *after* submission and found a
>> few discrepancies. Earlier I found some changes that needed to be made
>> in the CL draft. I stand ready to submit new versions of both to fix
>> these primarily editorial glitches, but I'll wait until people have ha=
d
>> a chance to check out the main sets of updates as provided in the
>> current versions.
>>
>> -------- Original Message --------
>> Subject: New Version Notification - draft-ietf-pcn-sm-edge-behaviour-0=
5.txt
>> Date: Thu, 16 Dec 2010 11:30:01 -0800
>> From: Internet-Draft@ietf.org
>> To: pcn-chairs@tools.ietf.org,
>> draft-ietf-pcn-sm-edge-behaviour@tools.ietf.org,	ietfdbh@comcast.net
>>
>> New version (-05) has been submitted for
>> draft-ietf-pcn-sm-edge-behaviour-05.txt.
>> http://www.ietf.org/internet-drafts/draft-ietf-pcn-sm-edge-behaviour-0=
5.txt
>> Sub state has been changed to AD Follow up from New Id Needed
>>
>> Diff from previous version:
>> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcn-sm-edge-behaviour-=
05
>>
>> IETF Secretariat.
>>
>>
>> _______________________________________________
>> PCN mailing list
>> PCN@ietf.org
>> https://www.ietf.org/mailman/listinfo/pcn
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn

--=20
Prof. Dr. habil. Michael Menth
University of Tuebingen
Wilhelm-Schickard-Institute
Lehrstuhl f=FCr Rechnernetze und Internet
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70505, fax: (+49)-7071/29-5220
mailto:menth@uni-tuebingen.de, http://www.net2.uni-tuebingen.de


From toby@moncaster.com  Fri Dec 17 00:59:39 2010
Return-Path: <toby@moncaster.com>
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 8AA823A698C for <pcn@core3.amsl.com>; Fri, 17 Dec 2010 00:59:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 HxvN5vrHDVhk for <pcn@core3.amsl.com>; Fri, 17 Dec 2010 00:59:38 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by core3.amsl.com (Postfix) with ESMTP id 0ED233A68F0 for <pcn@ietf.org>; Fri, 17 Dec 2010 00:59:37 -0800 (PST)
Received: from TobysHP (host86-170-51-241.range86-170.btcentralplus.com [86.170.51.241]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0Lm8JB-1Q2ZxS19I9-00aDVi; Fri, 17 Dec 2010 10:01:23 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'Michael Menth'" <menth@informatik.uni-tuebingen.de>, <pcn@ietf.org>
References: <ifmCY4SY.1292529950.9334330.karagian@ewi.utwente.nl> <4D0A90CA.4000604@informatik.uni-tuebingen.de>
In-Reply-To: <4D0A90CA.4000604@informatik.uni-tuebingen.de>
Date: Fri, 17 Dec 2010 09:01:23 -0000
Message-ID: <000701cb9dc8$fae40a60$f0ac1f20$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acudb44HP9mrjtiLQaaMN7JONSGrmAAWL3FQ
Content-Language: en-gb
X-Provags-ID: V02:K0:qPppQDZDrh/Yqgu26sOsBWEK/GqEQiJu+zKAmeEL51g Fgwas8lIFyd19nMt5ITvZMPQtYscUPQwQqWUzEHIDuHj6GimKT MguVa6KNTif7AhcwZqVT/JZvJXJBWs2tS62ea5wsJjwOtGu6M+ NlpBsHZt3sIN4V96+dZTbmFe/KTta2KLfpDdn2+7YK2WZBk2Ce Bp4vI4E/0rZyjfA7u8SB6+pz2P5LPrDyAZAutOZ1WA=
Subject: Re: [PCN] Fwd: New Version Notification	-	draft-ietf-pcn-sm-edge-behaviour-05.txt
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/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: Fri, 17 Dec 2010 08:59:39 -0000

Hi all,

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Michael Menth
> Sent: 16 December 2010 22:21
> To: pcn@ietf.org
> Subject: Re: [PCN] Fwd: New Version Notification - draft-ietf-pcn-sm-
> edge-behaviour-05.txt
>=20
> Hi Tom, hi Georgios,
>=20
> Am 16.12.2010 21:05, schrieb Georgios Karagiannis:
> > Hi Tom
> >
> > Thank you very much!
> > I think that the draft looks good, but regarding factor U, I think
> that
> > the following sentence should be changed from:
> >
> > U is a configurable
> >         factor greater than one which is the same for all ingress-
> egress-
> >         aggregates.
> >
> > INTO:
> >
> > U is a configurable
> >         factor greater than or equal to one which is the same for =
all
> >         ingress-egress-aggregates.
>=20
> I don't think that "equal" makes sense. This implies that the
> admissible
> rate equals the supportable rate. In such a system, flows are
> terminated
> as soon as admission control blocks. This is unlikely to be a sensible
> configuration.

So the sentence needs to include some explanation:=20

U is a configurable factor that represents the ratio between supportable =
and
admissible rates. It MUST be greater than or equal to one. It is =
RECOMMENDED
to be greater than one as a value of one implies that the admissible =
rate
equals the supportable rate.

(although as an informational document I am never clear whether there is =
any
point in using RFC2119 language).

Certainly when I came back to this draft after a 12 month absence I had
completely forgotten what the significance of U was, and needed a bit of
explanation...

Toby

>=20
> Best wishes,
>=20
>      Michael
>=20
> >
> > Best regards,
> > Georgios
> >
> >
> > On 12/16/2010, "Tom Taylor"<tom111.taylor@bell.net>  wrote:
> >
> >> I have updated and submitted the SM draft. Unfortunately, I did a
> final
> >> diff check between it and the CL draft *after* submission and found
> a
> >> few discrepancies. Earlier I found some changes that needed to be
> made
> >> in the CL draft. I stand ready to submit new versions of both to =
fix
> >> these primarily editorial glitches, but I'll wait until people have
> had
> >> a chance to check out the main sets of updates as provided in the
> >> current versions.
> >>
> >> -------- Original Message --------
> >> Subject: New Version Notification - draft-ietf-pcn-sm-edge-
> behaviour-05.txt
> >> Date: Thu, 16 Dec 2010 11:30:01 -0800
> >> From: Internet-Draft@ietf.org
> >> To: pcn-chairs@tools.ietf.org,
> >> draft-ietf-pcn-sm-edge-behaviour@tools.ietf.org,
> 	ietfdbh@comcast.net
> >>
> >> New version (-05) has been submitted for
> >> draft-ietf-pcn-sm-edge-behaviour-05.txt.
> >> http://www.ietf.org/internet-drafts/draft-ietf-pcn-sm-edge-
> behaviour-05.txt
> >> Sub state has been changed to AD Follow up from New Id Needed
> >>
> >> Diff from previous version:
> >> =
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcn-sm-edge-behaviour-
> 05
> >>
> >> IETF Secretariat.
> >>
> >>
> >> _______________________________________________
> >> PCN mailing list
> >> PCN@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pcn
> > _______________________________________________
> > PCN mailing list
> > PCN@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcn
>=20
> --
> Prof. Dr. habil. Michael Menth
> University of Tuebingen
> Wilhelm-Schickard-Institute
> Lehrstuhl f=FCr Rechnernetze und Internet
> Sand 13, 72076 Tuebingen, Germany
> phone: (+49)-7071/29-70505, fax: (+49)-7071/29-5220
> mailto:menth@uni-tuebingen.de, http://www.net2.uni-tuebingen.de
>=20
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn


From toby@moncaster.com  Fri Dec 17 01:00:43 2010
Return-Path: <toby@moncaster.com>
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 4B3583A6AB4 for <pcn@core3.amsl.com>; Fri, 17 Dec 2010 01:00:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 EB0DYf-Rl+Py for <pcn@core3.amsl.com>; Fri, 17 Dec 2010 01:00:42 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by core3.amsl.com (Postfix) with ESMTP id 404543A69DD for <pcn@ietf.org>; Fri, 17 Dec 2010 01:00:42 -0800 (PST)
Received: from TobysHP (host86-170-51-241.range86-170.btcentralplus.com [86.170.51.241]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MDkte-1Pf3KG14DG-00HY6x; Fri, 17 Dec 2010 10:02:26 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'Tom Taylor'" <tom111.taylor@bell.net>, "'pcn'" <pcn@ietf.org>
References: <BLU0-SMTP51B13FA4B2C6B09D9ABBEDD8150@phx.gbl>
In-Reply-To: <BLU0-SMTP51B13FA4B2C6B09D9ABBEDD8150@phx.gbl>
Date: Fri, 17 Dec 2010 09:02:26 -0000
Message-ID: <000801cb9dc9$206b2070$61416150$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcudWNXPZf2Wi8sfTkakuRRK8S4e6AAcCpLQ
Content-Language: en-gb
X-Provags-ID: V02:K0:DOgrZMXOiqJWbhJxr44GbTzSIsoT0CwVK2k+lyYKyKO LnP8KOIJ/cCCAvT7uNDhSFjCmCHRrKxXNzt/Oq1IfunApwlW1s qIPNbrB7Ex5IOS41OFrkvdpeHcwrT+XwmLEJ3S44bwTHiE7WRE 3+U2hKcKI5IQHxVBs4PJoqsuJSOCpnol132iMWDbXpkNs5SGwu r+13feku+amFcrbid/D9OkAWpj8R86IR0cYbcv7yc8=
Subject: Re: [PCN] Fwd: New Version Notification -	draft-ietf-pcn-sm-edge-behaviour-05.txt
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/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: Fri, 17 Dec 2010 09:00:43 -0000

Hi Tom,

Thanks for all the work you have put in. Hopefully the rest of the process
will go smoothly now and you won't have to completely re-write the drafts
again!

Toby

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Tom Taylor
> Sent: 16 December 2010 19:39
> To: pcn
> Subject: [PCN] Fwd: New Version Notification - draft-ietf-pcn-sm-edge-
> behaviour-05.txt
> 
> I have updated and submitted the SM draft. Unfortunately, I did a final
> diff check between it and the CL draft *after* submission and found a
> few discrepancies. Earlier I found some changes that needed to be made
> in the CL draft. I stand ready to submit new versions of both to fix
> these primarily editorial glitches, but I'll wait until people have had
> a chance to check out the main sets of updates as provided in the
> current versions.
> 
> -------- Original Message --------
> Subject: New Version Notification - draft-ietf-pcn-sm-edge-behaviour-
> 05.txt
> Date: Thu, 16 Dec 2010 11:30:01 -0800
> From: Internet-Draft@ietf.org
> To: pcn-chairs@tools.ietf.org,
> draft-ietf-pcn-sm-edge-behaviour@tools.ietf.org,
> 	ietfdbh@comcast.net
> 
> New version (-05) has been submitted for
> draft-ietf-pcn-sm-edge-behaviour-05.txt.
> http://www.ietf.org/internet-drafts/draft-ietf-pcn-sm-edge-behaviour-
> 05.txt
> Sub state has been changed to AD Follow up from New Id Needed
> 
> Diff from previous version:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-pcn-sm-edge-behaviour-05
> 
> IETF Secretariat.
> 
> 
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn


From Ruediger.Geib@telekom.de  Fri Dec 17 01:09:24 2010
Return-Path: <Ruediger.Geib@telekom.de>
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 2E2173A6A26 for <pcn@core3.amsl.com>; Fri, 17 Dec 2010 01:09:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 irHX78hAnFrN for <pcn@core3.amsl.com>; Fri, 17 Dec 2010 01:09:23 -0800 (PST)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by core3.amsl.com (Postfix) with ESMTP id EBD853A69DD for <pcn@ietf.org>; Fri, 17 Dec 2010 01:09:22 -0800 (PST)
Received: from he110889.emea1.cds.t-internal.com ([10.134.92.130]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 17 Dec 2010 10:11:03 +0100
Received: from HE111648.emea1.cds.t-internal.com ([169.254.5.187]) by HE110889.emea1.cds.t-internal.com ([fe80::841f:f92c:15ca:8526%16]) with mapi; Fri, 17 Dec 2010 10:11:02 +0100
From: <Ruediger.Geib@telekom.de>
To: <toby@moncaster.com>, <tom111.taylor@bell.net>, <pcn@ietf.org>
Date: Fri, 17 Dec 2010 10:11:00 +0100
Thread-Topic: [PCN] Fwd: New Version Notification	- draft-ietf-pcn-sm-edge-behaviour-05.txt
Thread-Index: AcudWNXPZf2Wi8sfTkakuRRK8S4e6AAcCpLQAAA7b9A=
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D05E066FC@HE111648.emea1.cds.t-internal.com>
References: <BLU0-SMTP51B13FA4B2C6B09D9ABBEDD8150@phx.gbl> <000801cb9dc9$206b2070$61416150$@com>
In-Reply-To: <000801cb9dc9$206b2070$61416150$@com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [PCN] Fwd: New Version Notification	-	draft-ietf-pcn-sm-edge-behaviour-05.txt
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/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: Fri, 17 Dec 2010 09:09:24 -0000

Hi Tom, hi Toby

Toby's last proposal on an explanation of a reasonable setting of U seems s=
ound to me.

In addition I too thank you Tom for maintaining this draft that well.

Regards,

Ruediger

-----Original Message-----
From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of Toby =
Moncaster
Sent: Friday, December 17, 2010 10:02 AM
To: 'Tom Taylor'; 'pcn'
Subject: Re: [PCN] Fwd: New Version Notification - draft-ietf-pcn-sm-edge-b=
ehaviour-05.txt

Hi Tom,

Thanks for all the work you have put in. Hopefully the rest of the process
will go smoothly now and you won't have to completely re-write the drafts
again!

Toby

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Tom Taylor
> Sent: 16 December 2010 19:39
> To: pcn
> Subject: [PCN] Fwd: New Version Notification - draft-ietf-pcn-sm-edge-
> behaviour-05.txt
>
> I have updated and submitted the SM draft. Unfortunately, I did a final
> diff check between it and the CL draft *after* submission and found a
> few discrepancies. Earlier I found some changes that needed to be made
> in the CL draft. I stand ready to submit new versions of both to fix
> these primarily editorial glitches, but I'll wait until people have had
> a chance to check out the main sets of updates as provided in the
> current versions.
>
> -------- Original Message --------
> Subject: New Version Notification - draft-ietf-pcn-sm-edge-behaviour-
> 05.txt
> Date: Thu, 16 Dec 2010 11:30:01 -0800
> From: Internet-Draft@ietf.org
> To: pcn-chairs@tools.ietf.org,
> draft-ietf-pcn-sm-edge-behaviour@tools.ietf.org,
>       ietfdbh@comcast.net
>
> New version (-05) has been submitted for
> draft-ietf-pcn-sm-edge-behaviour-05.txt.
> http://www.ietf.org/internet-drafts/draft-ietf-pcn-sm-edge-behaviour-
> 05.txt
> Sub state has been changed to AD Follow up from New Id Needed
>
> Diff from previous version:
> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcn-sm-edge-behaviour-05
>
> IETF Secretariat.
>
>
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn

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

From karagian@cs.utwente.nl  Fri Dec 17 01:12:05 2010
Return-Path: <karagian@cs.utwente.nl>
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 C4EB13A69DD for <pcn@core3.amsl.com>; Fri, 17 Dec 2010 01:12:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.138
X-Spam-Level: 
X-Spam-Status: No, score=-0.138 tagged_above=-999 required=5 tests=[AWL=0.366,  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 osYNVWcCektN for <pcn@core3.amsl.com>; Fri, 17 Dec 2010 01:12:04 -0800 (PST)
Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11]) by core3.amsl.com (Postfix) with ESMTP id 759C13A695A for <pcn@ietf.org>; Fri, 17 Dec 2010 01:12:04 -0800 (PST)
Received: from ewi977 (ewi977.ewi.utwente.nl [130.89.12.129]) by denhaag.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id oBH9DZWq022667;  Fri, 17 Dec 2010 10:13:38 +0100 (MET)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "'Michael Menth'" <menth@informatik.uni-tuebingen.de>, <pcn@ietf.org>
References: <ifmCY4SY.1292529950.9334330.karagian@ewi.utwente.nl> <4D0A90CA.4000604@informatik.uni-tuebingen.de>
Date: Fri, 17 Dec 2010 10:13:33 +0100
Message-ID: <D0AB865915884224BD65308711627332@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4D0A90CA.4000604@informatik.uni-tuebingen.de>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
thread-index: Acudb5BqBmTXKHFESHuAB13z0wCprAAWvbUg
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.11
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3 (denhaag.ewi.utwente.nl [130.89.10.11]); Fri, 17 Dec 2010 10:13:48 +0100 (MET)
Subject: Re: [PCN] Fwd: New Version Notification-	draft-ietf-pcn-sm-edge-behaviour-05.txt
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/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: Fri, 17 Dec 2010 09:12:05 -0000

Hi Michael

The simulation that have been done on the SM approach used U as being
greater or equal to 1.
The text proposed by Toby is fine for me!

Best regards,
Georgios
=20

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On=20
> Behalf Of Michael Menth
> Sent: donderdag 16 december 2010 23:21
> To: pcn@ietf.org
> Subject: Re: [PCN] Fwd: New Version Notification-=20
> draft-ietf-pcn-sm-edge-behaviour-05.txt
>=20
> Hi Tom, hi Georgios,
>=20
> Am 16.12.2010 21:05, schrieb Georgios Karagiannis:
> > Hi Tom
> >
> > Thank you very much!
> > I think that the draft looks good, but regarding factor U, I think=20
> > that the following sentence should be changed from:
> >
> > U is a configurable
> >         factor greater than one which is the same for all=20
> ingress-egress-
> >         aggregates.
> >
> > INTO:
> >
> > U is a configurable
> >         factor greater than or equal to one which is the=20
> same for all
> >         ingress-egress-aggregates.
>=20
> I don't think that "equal" makes sense. This implies that the=20
> admissible rate equals the supportable rate. In such a=20
> system, flows are terminated as soon as admission control=20
> blocks. This is unlikely to be a sensible configuration.
>=20
> Best wishes,
>=20
>      Michael
>=20
> >
> > Best regards,
> > Georgios
> >
> >
> > On 12/16/2010, "Tom Taylor"<tom111.taylor@bell.net>  wrote:
> >
> >> I have updated and submitted the SM draft. Unfortunately, I did a=20
> >> final diff check between it and the CL draft *after*=20
> submission and=20
> >> found a few discrepancies. Earlier I found some changes=20
> that needed=20
> >> to be made in the CL draft. I stand ready to submit new=20
> versions of=20
> >> both to fix these primarily editorial glitches, but I'll=20
> wait until=20
> >> people have had a chance to check out the main sets of updates as=20
> >> provided in the current versions.
> >>
> >> -------- Original Message --------
> >> Subject: New Version Notification -=20
> >> draft-ietf-pcn-sm-edge-behaviour-05.txt
> >> Date: Thu, 16 Dec 2010 11:30:01 -0800
> >> From: Internet-Draft@ietf.org
> >> To: pcn-chairs@tools.ietf.org,
> >> draft-ietf-pcn-sm-edge-behaviour@tools.ietf.org,=09
> ietfdbh@comcast.net
> >>
> >> New version (-05) has been submitted for=20
> >> draft-ietf-pcn-sm-edge-behaviour-05.txt.
> >>=20
> http://www.ietf.org/internet-drafts/draft-ietf-pcn-sm-edge-behaviour-
> >> 05.txt Sub state has been changed to AD Follow up from New=20
> Id Needed
> >>
> >> Diff from previous version:
> >>=20
> =
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcn-sm-edge-behaviour-0
> >> 5
> >>
> >> IETF Secretariat.
> >>
> >>
> >> _______________________________________________
> >> PCN mailing list
> >> PCN@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pcn
> > _______________________________________________
> > PCN mailing list
> > PCN@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcn
>=20
> --
> Prof. Dr. habil. Michael Menth
> University of Tuebingen
> Wilhelm-Schickard-Institute
> Lehrstuhl f=FCr Rechnernetze und Internet
> Sand 13, 72076 Tuebingen, Germany
> phone: (+49)-7071/29-70505, fax: (+49)-7071/29-5220=20
> mailto:menth@uni-tuebingen.de, http://www.net2.uni-tuebingen.de
>=20
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>=20



From menth@informatik.uni-tuebingen.de  Sat Dec 18 14:39:36 2010
Return-Path: <menth@informatik.uni-tuebingen.de>
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 902253A6C0F for <pcn@core3.amsl.com>; Sat, 18 Dec 2010 14:39:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.644
X-Spam-Level: 
X-Spam-Status: No, score=-0.644 tagged_above=-999 required=5 tests=[AWL=0.157,  BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448]
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 gDomvCwSJIu8 for <pcn@core3.amsl.com>; Sat, 18 Dec 2010 14:39:35 -0800 (PST)
Received: from mx5.informatik.uni-tuebingen.de (mx5.Informatik.Uni-Tuebingen.De [134.2.12.32]) by core3.amsl.com (Postfix) with SMTP id A2A4A3A6BFE for <pcn@ietf.org>; Sat, 18 Dec 2010 14:39:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx5.informatik.uni-tuebingen.de (Postfix) with ESMTP id 011A45298; Sat, 18 Dec 2010 23:41:19 +0100 (MET)
X-Virus-Scanned: amavisd-new at informatik.uni-tuebingen.de
Received: from mx5.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx5.informatik.uni-tuebingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eOLKpb6WHlV7; Sat, 18 Dec 2010 23:41:11 +0100 (MET)
Received: from zcs-pu.informatik.uni-tuebingen.de (zcs-pu.Informatik.Uni-Tuebingen.De [134.2.12.61]) by mx5.informatik.uni-tuebingen.de (Postfix) with ESMTP id BDF685294; Sat, 18 Dec 2010 23:41:11 +0100 (MET)
Received: from [192.168.1.100] (HSI-KBW-095-208-114-108.hsi5.kabel-badenwuerttemberg.de [95.208.114.108]) by zcs-pu.informatik.uni-tuebingen.de (Postfix) with ESMTP id 92024C3C88F; Sat, 18 Dec 2010 23:41:11 +0100 (CET)
Message-ID: <4D0D3887.1060307@informatik.uni-tuebingen.de>
Date: Sat, 18 Dec 2010 23:41:11 +0100
From: Michael Menth <menth@informatik.uni-tuebingen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: pcn@ietf.org
References: <BLU0-SMTP6925E6F0F2A375BD4A4E6CD8150@phx.gbl>
In-Reply-To: <BLU0-SMTP6925E6F0F2A375BD4A4E6CD8150@phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PCN] draft-ietf-pcn-cl-edge-behaviour-08 posted
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/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: Sat, 18 Dec 2010 22:39:36 -0000

Hi Tom,

Hi Tom,

thank you for your hard work in editing the two drafts.
I reviewed the latest version of the CL document. Here are my comments.

p5: of the Disffserv codepoint and ECN fields -> and the ECN field.

p6: threshold-marked and excess-traffic-marked is not defined; the fact t=
hat
     it is only defined in 3.2.1 makes the doc harder to read. I suggest=20
defining
     it in the terminology section to help the reader.
     I still do not understand why the reference to the 3-in-1 marking=20
was left
     while its content is basically repeated in this doc.

p7: def. of SAR: The estimated maximum rate of PCN-traffic that can be=20
admitted to
     -> ... can be tolerated on ...
     At that stage, no more flows could be admitted!

p7/8: T-* (3x): An interval, the value of which is configurable, ...
     -> An interval whose duration is configurable ...

p9: ThM-rate: ... (i.e., marked with the PM codepoint);
     -> marked with the EXP codepoint).

     ETM-rate: ... (i.e., marked with the EXP codepoint).
     -> marked with the PM codepoint.

p10: T-maxsuppress functions as a keep-alive mechanism ...
     -> as a hello mechanism
     (these messages do not keep anything alive, they just show livelines=
s)

p11: This provides some protection against loss of egress reports and ...
     Hm, I don't think this provides protection, it just makes visible th=
at
     something does not work anymore. Either drop this sentence or clarif=
y
     what your exactly mean!

p12: an amount of flow -> flows

p13: If the difference ... single round of decision. Alternatively ...=20
[MeLe10]).

     -> If the difference calculated in the second round is positive, it
     is an estimate for the PCN traffic rate of the respective
     ingress-egress-aggregate that should be terminated to remove overloa=
d
     (excess of PCN-supportable-rate) on some link. The Decision Point=20
SHOULD
     terminate traffic until the PCN-sent-rate is no longer greater than=20
SAR.

     There are different strategies for the Decision Point to remove exce=
ss
     traffic. For instance, it may terminate an appropriate set of flows =
in
     one shot if it knows exact flow rates, e.g. from resource signalling=
,
     or it may terminate traffic incrementally over several measurement
     intervals. Special care has to be taken if the difference is less th=
an
     than the rate than the smallest rate of the flows in the correspondi=
ng
     ingress-egress-aggregate. Some termination options have been=20
proposed and
     investigated in Section 4.6 of [MeLe10].

     If the Decision Point has to terminate traffic more than once, it is
     RECOMMENDED that sufficient time has elapsed between successive=20
termination
     steps so that the effect of previous termination steps is reflected=20
in the
     measurements upon which the current termination decision is based.
     Otherwise, too much traffic may be terminated so that overterminatio=
n
     occurs [IEEE-Satoh and Sections 4.2 and 4.3 of [MeLe10]].

p13
    3.3.3 Decision Point Action For -> for
    Missing  PCN-Boundary -> Missing PCN-Boundary

p14 observation of at least thirty PCN-packets
     Where does this number come from?

     3.5 Summary of Timers
     Here some streamlining is needed. T-* was introduced as an interval
     in the terminology section, now T-* is the actual value and t-* is t=
he
     name of the timer. Is the latter one required at all in the doc?

     IEA is defined only over Table 1. I missed that while reading. Why n=
ot
     introduce "IEA" as an abbreviation in the terminology section?


p15 ... keep-alive procedure.
     -> hello-mechanism. ?
     keep-alive is actually needed when a softstate needs to be maintaine=
d,
     this is here not the case. Or is it? If so, make it explicit!

     ... as proposed by the transport protocol specification.
     What are you referring to? This is hard to understand. Sounds like t=
he
     signalling draft which is not cited ...

     The means by which this is done ...
     "this" refers to the last sentence which does not make sense. You me=
an
     another sentence before: rephrase! A new paragraph is not needed.

p16 (e.g. due to network failures): that is very general and maybe not=20
so clear
     -> (e.g. due to link or node failures with subsequent rerouting)

     The CL boundary node behaviour is less ...
     -> The performance results in [MeLe10] have shown that the CL ...

5.2.1 ... PCN-ingress-nodes MUST block ECN-capable traffic  that uses=20
the same DSCP as PCN ...

I don't agree. I think that the ECN field of such traffic should be set
to 00 (not-ECN), which means that ECN is basically disabled. That's bette=
r
than dropping or downgrading the traffic.

... Packets belonging to  ... flowspec.

... flowspec that were possibly signalled by a resource signalling protoc=
ol
for flow admission.

5.2.2

The meaning of this sentence is not clear to me:
"As a result, they are not tied to the selection of a specific DSCP value=
".
Does that mean that PCN will be available for mulitple DSCPs? That's what=
 we
always said no, but this sentence could be interpreted that way! This=20
section
is not yet very comprehensible.

p17

o Whether ... (2x)
-> o Indication whether ...

p18

... to map between ... PCN-egress-node
->
o The information needed to map an ingress-egress-aggregates to a
   corresponding PCN-ingress-nodes and a corresponding PCN-egress-node.

5.5 Assumptions

This section calls for bullets to simplify reading.

I'll review the SM-draft only in the next version when these and other=20
corrections have been applied.

Best wishes,

     Michael

Am 16.12.2010 05:56, schrieb Tom Taylor:
> I have submitted draft-ietf-pcn-cl-edge-behaviour-08 with the changes=20
> indicated in my two responses to the AD review notes, modified by list=20
> discussion. Please have a look while I finish updating the SM draft.
>
> Diff is available at
>
> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcn-cl-edge-behaviour-0=
8
>
> Tom Taylor
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn

--=20
Prof. Dr. habil. Michael Menth
University of Tuebingen
Wilhelm-Schickard-Institute
Lehrstuhl f=FCr Rechnernetze und Internet
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70505, fax: (+49)-7071/29-5220
mailto:menth@uni-tuebingen.de, http://www.net2.uni-tuebingen.de


From toby@moncaster.com  Tue Dec 21 07:44:25 2010
Return-Path: <toby@moncaster.com>
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 132973A6B0F for <pcn@core3.amsl.com>; Tue, 21 Dec 2010 07:44:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 MgqFDTFzRJUC for <pcn@core3.amsl.com>; Tue, 21 Dec 2010 07:44:23 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by core3.amsl.com (Postfix) with ESMTP id 3FC733A69F7 for <pcn@ietf.org>; Tue, 21 Dec 2010 07:44:23 -0800 (PST)
Received: from TobysHP (host86-170-51-241.range86-170.btcentralplus.com [86.170.51.241]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0Lx5jt-1QSZnd0041-016Pqj; Tue, 21 Dec 2010 16:46:16 +0100
From: "Toby Moncaster" <toby@moncaster.com>
To: "'Michael Menth'" <menth@informatik.uni-tuebingen.de>, <pcn@ietf.org>
References: <BLU0-SMTP6925E6F0F2A375BD4A4E6CD8150@phx.gbl> <4D0D3887.1060307@informatik.uni-tuebingen.de>
In-Reply-To: <4D0D3887.1060307@informatik.uni-tuebingen.de>
Date: Tue, 21 Dec 2010 15:46:16 -0000
Message-ID: <002201cba126$34b3f830$9e1be890$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcufBLcNo7Bo0nrTTGC1Zz4efybk6ACHY9gQ
Content-Language: en-gb
X-Provags-ID: V02:K0:DWSnl61/uVF4F3dvgTzltgpMVbTdwGPiMAlMt2oJ4ge a7uh0ssOvbF4Ta6RQFASXDV6wLJqIoIRlG9f6Zesd/rmGfcp7B k+ZZVQ5GW4vhtWCEZBhjug/BShAjARQxkYnNUJjTDBoBGN2Gmt DRUUHa+xSKa5FHvnl+JXERDbSzVogUjSPfVr0Be0s0JHN3lRAz /DX0JCrFNnvA3+GXMys2lmh5r0MrmgHnxwNw1YIKhg=
Subject: Re: [PCN] draft-ietf-pcn-cl-edge-behaviour-08 posted
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/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, 21 Dec 2010 15:44:25 -0000

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On Behalf Of
> Michael Menth
> Sent: 18 December 2010 22:41
> To: pcn@ietf.org
> Subject: Re: [PCN] draft-ietf-pcn-cl-edge-behaviour-08 posted
>=20
> Hi Tom,
>=20
> Hi Tom,
>=20
> thank you for your hard work in editing the two drafts.
> I reviewed the latest version of the CL document. Here are my =
comments.
>=20
> p5: of the Disffserv codepoint and ECN fields -> and the ECN field.

Agree

>=20
> p6: threshold-marked and excess-traffic-marked is not defined; the =
fact
> that
>      it is only defined in 3.2.1 makes the doc harder to read. I
> suggest
> defining
>      it in the terminology section to help the reader.
>      I still do not understand why the reference to the 3-in-1 marking
> was left
>      while its content is basically repeated in this doc.

Be careful not to repeat definitions that already exist in other
documents... We are already getting very near the stage of needing an
informational document listing all defined PCN terms along with their
normative reference!

3-in-1 is not worth referencing in case it delays publication. You can
(perhaps) reference Bob's new RFC6040 and explain that it relieves some =
of
the constraints that RFC5696 had to allow for... That way you hold the =
door
open for 3-in-1 without actually referencing it.

>=20
> p7: def. of SAR: The estimated maximum rate of PCN-traffic that can be
> admitted to
>      -> ... can be tolerated on ...
>      At that stage, no more flows could be admitted!

"can be tolerated" sounds wrong. I would suggest sticking with the =
original
wording or changing to "can be carried"


>=20
> p7/8: T-* (3x): An interval, the value of which is configurable, ...
>      -> An interval whose duration is configurable ...

I think I sent Tom some suggested alternative wording for all these =
phrases.
It went something like "A configurable time interval that defines the =
period
over which..."

>=20
> p9: ThM-rate: ... (i.e., marked with the PM codepoint);
>      -> marked with the EXP codepoint).

This possibly ties the document too firmly to RFC5696. But leave this to
others to decide

>=20
>      ETM-rate: ... (i.e., marked with the EXP codepoint).
>      -> marked with the PM codepoint.
>=20
> p10: T-maxsuppress functions as a keep-alive mechanism ...
>      -> as a hello mechanism
>      (these messages do not keep anything alive, they just show
> liveliness)

"as an indication the link is still live"

>=20
> p11: This provides some protection against loss of egress reports and
> ...
>      Hm, I don't think this provides protection, it just makes visible
> that
>      something does not work anymore. Either drop this sentence or
> clarify
>      what your exactly mean!

Agree with Michael. Going to be interesting to come up with elegant =
wording
though

>=20
> p12: an amount of flow -> flows
>=20
> p13: If the difference ... single round of decision. Alternatively ...
> [MeLe10]).
>=20
>      -> If the difference calculated in the second round is positive,
> it
>      is an estimate for the PCN traffic rate of the respective
>      ingress-egress-aggregate that should be terminated to remove
> overload
>      (excess of PCN-supportable-rate) on some link. The Decision Point
> SHOULD
>      terminate traffic until the PCN-sent-rate is no longer greater
> than
> SAR.
>=20
>      There are different strategies for the Decision Point to remove
> excess
>      traffic. For instance, it may terminate an appropriate set of
> flows in
>      one shot if it knows exact flow rates, e.g. from resource
> signalling,
>      or it may terminate traffic incrementally over several =
measurement
>      intervals. Special care has to be taken if the difference is less
> than
>      than the rate than the smallest rate of the flows in the
> corresponding
>      ingress-egress-aggregate. Some termination options have been
> proposed and
>      investigated in Section 4.6 of [MeLe10].
>=20
>      If the Decision Point has to terminate traffic more than once, it
> is
>      RECOMMENDED that sufficient time has elapsed between successive
> termination
>      steps so that the effect of previous termination steps is
> reflected
> in the
>      measurements upon which the current termination decision is =
based.
>      Otherwise, too much traffic may be terminated so that
> overtermination
>      occurs [IEEE-Satoh and Sections 4.2 and 4.3 of [MeLe10]].

I'm not convinced we need quite so much extra text in the main body of =
the
document. Quite a bit of what Michael is adding sounds like it really
belongs in an appendix.


>=20
> p13
>     3.3.3 Decision Point Action For -> for
>     Missing  PCN-Boundary -> Missing PCN-Boundary
>=20
> p14 observation of at least thirty PCN-packets
>      Where does this number come from?

Indeed. This comes across like something plucked from the air

>=20
>      3.5 Summary of Timers
>      Here some streamlining is needed. T-* was introduced as an
> interval
>      in the terminology section, now T-* is the actual value and t-* =
is
> the
>      name of the timer. Is the latter one required at all in the doc?
>=20
>      IEA is defined only over Table 1. I missed that while reading. =
Why
> not
>      introduce "IEA" as an abbreviation in the terminology section?


as the document currently stands I think the name of the timer is
unnecessary...

agree with putting IEA in terminology section, or use an asterisk and =
have
it as a footnote to the table

>=20
>=20
> p15 ... keep-alive procedure.
>      -> hello-mechanism. ?
>      keep-alive is actually needed when a softstate needs to be
> maintained,
>      this is here not the case. Or is it? If so, make it explicit!
>=20
>      ... as proposed by the transport protocol specification.
>      What are you referring to? This is hard to understand. Sounds =
like
> the
>      signalling draft which is not cited ...
>=20
>      The means by which this is done ...
>      "this" refers to the last sentence which does not make sense. You
> mean
>      another sentence before: rephrase! A new paragraph is not needed.
>=20
> p16 (e.g. due to network failures): that is very general and maybe not
> so clear
>      -> (e.g. due to link or node failures with subsequent rerouting)
>=20
>      The CL boundary node behaviour is less ...
>      -> The performance results in [MeLe10] have shown that the CL ...
>=20
> 5.2.1 ... PCN-ingress-nodes MUST block ECN-capable traffic  that uses
> the same DSCP as PCN ...
>=20
> I don't agree. I think that the ECN field of such traffic should be =
set
> to 00 (not-ECN), which means that ECN is basically disabled. That's
> better
> than dropping or downgrading the traffic.

The key is to ensure that whatever action is taken can be clearly =
understood
by the end hosts. Of the top of my head I can't recall the exact =
negotiation
rounds that ECN goes through, nor whether ECN in TCP can spot the ECN =
field
being reset... Personally I am really dubious about introducing a new
mechanism that resets an existing mechanism (and it might get people a =
bit
hot under the collar also)

>=20
> ... Packets belonging to  ... flowspec.
>=20
> ... flowspec that were possibly signalled by a resource signalling
> protocol
> for flow admission.

Change whole sentence to "Packets belonging to an admitted flow are =
policed
to ensure they adhere to the agreed rate or flowspec that was negotiated
during flow admission"

>=20
> 5.2.2
>=20
> The meaning of this sentence is not clear to me:
> "As a result, they are not tied to the selection of a specific DSCP
> value".
> Does that mean that PCN will be available for mulitple DSCPs? That's
> what we
> always said no, but this sentence could be interpreted that way! This
> section
> is not yet very comprehensible.

There are two competing things here. Within a PCN domain the choice of =
DSCPs
is limited, but between domains there aren't limits (as PCN is defined =
as a
single domain protocol). Indeed if you read appendix a of RFC5696 it
discusses choosing "suitable DSCPs"

>=20
> p17
>=20
> o Whether ... (2x)
> -> o Indication whether ...
>=20
> p18
>=20
> ... to map between ... PCN-egress-node
> ->
> o The information needed to map an ingress-egress-aggregates to a
>    corresponding PCN-ingress-nodes and a corresponding =
PCN-egress-node.

"The information needed to map an IEA to the corresponding =
PCN-ingress-node
and PCN-egress-node"

>=20
> 5.5 Assumptions
>=20
> This section calls for bullets to simplify reading.

Agree


Toby

PS I /may/ go through both documents again myself and see if I can spot =
any
other changes. But we are already at risk of changing so much that we =
will
have to go back to square one of the publication process (and the IESG =
are
going to start to wonder why we didn't do all this first time round!)

>=20
> I'll review the SM-draft only in the next version when these and other
> corrections have been applied.
>=20
> Best wishes,
>=20
>      Michael
>=20
> Am 16.12.2010 05:56, schrieb Tom Taylor:
> > I have submitted draft-ietf-pcn-cl-edge-behaviour-08 with the =
changes
> > indicated in my two responses to the AD review notes, modified by
> list
> > discussion. Please have a look while I finish updating the SM draft.
> >
> > Diff is available at
> >
> > =
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcn-cl-edge-behaviour-
> 08
> >
> > Tom Taylor
> > _______________________________________________
> > PCN mailing list
> > PCN@ietf.org
> > https://www.ietf.org/mailman/listinfo/pcn
>=20
> --
> Prof. Dr. habil. Michael Menth
> University of Tuebingen
> Wilhelm-Schickard-Institute
> Lehrstuhl f=FCr Rechnernetze und Internet
> Sand 13, 72076 Tuebingen, Germany
> phone: (+49)-7071/29-70505, fax: (+49)-7071/29-5220
> mailto:menth@uni-tuebingen.de, http://www.net2.uni-tuebingen.de
>=20
> _______________________________________________
> PCN mailing list
> PCN@ietf.org
> https://www.ietf.org/mailman/listinfo/pcn


From ietfdbh@comcast.net  Tue Dec 21 09:45:18 2010
Return-Path: <ietfdbh@comcast.net>
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 104BA3A6A7E for <pcn@core3.amsl.com>; Tue, 21 Dec 2010 09:45:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.515
X-Spam-Level: 
X-Spam-Status: No, score=-102.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 3cUabxu+Chwc for <pcn@core3.amsl.com>; Tue, 21 Dec 2010 09:45:17 -0800 (PST)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by core3.amsl.com (Postfix) with ESMTP id 0586D3A6A94 for <pcn@ietf.org>; Tue, 21 Dec 2010 09:45:16 -0800 (PST)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta03.westchester.pa.mail.comcast.net with comcast id lsC71f00F0EZKEL53tnE4M; Tue, 21 Dec 2010 17:47:14 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta01.westchester.pa.mail.comcast.net with comcast id ltn71f01E2JQnJT3Mtn8Rj; Tue, 21 Dec 2010 17:47:11 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Toby Moncaster'" <toby@moncaster.com>, "'Michael Menth'" <menth@informatik.uni-tuebingen.de>, <pcn@ietf.org>
References: <BLU0-SMTP6925E6F0F2A375BD4A4E6CD8150@phx.gbl><4D0D3887.1060307@informatik.uni-tuebingen.de> <002201cba126$34b3f830$9e1be890$@com>
Date: Tue, 21 Dec 2010 12:46:31 -0500
Message-ID: <60AEE4416541473CBA823CFBE0077ACA@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcufBLcNo7Bo0nrTTGC1Zz4efybk6ACHY9gQAAUEyEA=
In-Reply-To: <002201cba126$34b3f830$9e1be890$@com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Subject: Re: [PCN] draft-ietf-pcn-cl-edge-behaviour-08 posted
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/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, 21 Dec 2010 17:45:18 -0000

 

> -----Original Message-----
> From: pcn-bounces@ietf.org [mailto:pcn-bounces@ietf.org] On 
> Behalf Of Toby Moncaster
> Sent: Tuesday, December 21, 2010 10:46 AM
> To: 'Michael Menth'; pcn@ietf.org
> Subject: Re: [PCN] draft-ietf-pcn-cl-edge-behaviour-08 posted
> 
> PS I /may/ go through both documents again myself and see if 
> I can spot any
> other changes. But we are already at risk of changing so much 
> that we will
> have to go back to square one of the publication process (and 
> the IESG are
> going to start to wonder why we didn't do all this first time
round!)
> 

Hi,

You are only at square one of the publication process. The documents
are in AD Evaluation; they have not gone to the IESG yet. We ARE doing
all this the first time round. Hopefully, this all this work will
smooth the way through the IESG Evaluation. ;-) 

dbh


From ietfdbh@comcast.net  Tue Dec 21 12:18:12 2010
Return-Path: <ietfdbh@comcast.net>
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 E95683A68A6 for <pcn@core3.amsl.com>; Tue, 21 Dec 2010 12:18:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 lCaK9W9VlrvP for <pcn@core3.amsl.com>; Tue, 21 Dec 2010 12:18:11 -0800 (PST)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by core3.amsl.com (Postfix) with ESMTP id 709243A6AA1 for <pcn@ietf.org>; Tue, 21 Dec 2010 12:18:11 -0800 (PST)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta08.westchester.pa.mail.comcast.net with comcast id lucV1f00E0bG4ec58wL8ZR; Tue, 21 Dec 2010 20:20:08 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta03.westchester.pa.mail.comcast.net with comcast id lwL31f00K2JQnJT3PwL48N; Tue, 21 Dec 2010 20:20:06 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <pcn@ietf.org>
Date: Tue, 21 Dec 2010 15:19:26 -0500
Message-ID: <0DF92E3B84734E8A9C764B56EE60D628@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcuhTFzzsZKbV9OLQGmlTiJd9+gHTg==
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Subject: [PCN] comment on revised cl-edge
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/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, 21 Dec 2010 20:18:13 -0000

Hi,

So I started this email thinking i had a few minor comments. But as i
progressed, I realized that wasn't going to be true. As I said
earlier,
You are only at square one of the publication process. The documents
are in AD Evaluation; they have not gone to the IESG yet. We are doing
all this in the first round. Hopefully, this all this work will
smooth the way through the IESG Evaluation. ;-) 

Unfortunately, as I get into these document more, I am thinking there
are a few things that will not just be minor comments.

Don't get me wrong. I think these documents are well-written, fairly
easy to understand even for a novice, and important. We need a little
polish, and attention to some details that have not been addressed
yet.

1) in 3.5, you say 
      "At the time of writing,  
       that transport protocol has not yet been specified.  This  
       specification therefore requires that any transport protocol  
       specification for carrying PCN reports MUST specify an
appropriate  
       default value for T-maxsuppress."
Well, as an IESG member, that certainly makes me think that maybe we
should get that (one) protocol defined before advancing the spec. 
and since this specification THEREFORE requires ...
makes me wonder what happens when that transport IS defined; does that
mean this spec no longer requires ...?
I suggest:
      "Any transport protocol  
       specification for carrying PCN reports MUST specify an
appropriate  
       default value for T-maxsuppress."

however, how does one know what "appropriate" means? I think this
needs to be explained further.

The next paragraph talks about t-fail as a function of T-maxsuppress.
So if they use an inappropriate value for T-maxsuppress, that gets
cascaded into t-fail as well.

The text says t-maxsuppress is only active when report suppression is
enabled. If t-fail is a function of t-maxsuppress, does that mean
t-fail is also only active when report suppression is enabled? If
t-fail is active whether suppression is enabled or not, then maybe you
would do better to discuss t-fail first and then discuss
t-maxsuppression as a function of t-fail. 

Either way, I think we need to provide more concrete guidance than
these paragraphs offer.

2) in 4., I think I'd change "MUST send" to "sends"

3) in 5.1, is "too many flows" excessive terminations? It's awfully
vague.

4) in 5.2.1, "MUST block ... Alternatively ..." - it cannot be both
MUST and alternatively. How about "MUST be prevented from entering the
domain, such as by blocking or tunneling, ..." and then discuss those
approaches.

5) 5.2 flowspec is used before being defined.

6) 5.2.2 section title - expand PHB

7) It's been a while since I've dealt with diffserv. The "as a result"
conclusion in 5.2.2 is not obvious to me (and is unlikely to be
obvious to some members of IESG). The first sentence says "are
metering and marking rather then scheduling", which is also a little
non-obvious why that distinction is being made. I think the first two
sentences might be written with a little more explanation of the
nature of configuration needed for metering and marking behaviors. And
there is no justification for why the WG suggests admission control
for these particular classes. (and as a matter of style, I think it is
usually inappropriate to talk about the WG; just make the
recommendation - It is RECOMMENDED that admission control be used for
the following classes.)

8) in 5.3, the design requirement for PCN was that ... yeah, and what
is the design requirement now? Hmmm, if the requirement was 1..3
seconds, and we now do it in, say, 0.5 seconds, do we meet the
requirement? - our number is not in the range of 1..3. or is the
design requirement 3 seconds or less?

9) in 5.4, we say "see section 2"; but section 2 says "see RFC 5670";
why such an indirect route?
and under parameters at the interior node, we also point to section 2
for the same meters. maybe we don't need the references for these
meters since references are provided in section 2, where we say we
will use these terms throughout the document.

10) in 5.5,
	Assumed that a specific portion of link capacity has been
reserved  
 
	Assumed that the Decision Point receives requests  
       for admission of PCN-flows before the packets in the PCN-flows

       arrive.  This is not a critical assumption, but in its absence,

       packets will be dropped by the PCN-ingress-node until it
obtains the  
       admission decision from the Decision Point. 

how about Assumptions:
1) a specific portion of link capacity has been reserved for
PCN-traffic.
2) the Decision Point receives requests  
       for admission of PCN-flows before the packets in the PCN-flows

       arrive, and
       packets will not be dropped by the PCN-ingress-node until it
obtains the  
       admission decision from the Decision Point.

is this "will not" really a MUST NOT? or SHOULD NOT?

11) in 6, does ECN ever play into security considerations? does
reusing ecn bits then have a potential impact on security? 
- What about tunneling ECN-enabled traffic? Preventing entry into the
domain is a CL-edge requirement, right? Therefore, this document does
introduce new considerations for security, such as those mentioned in
RFC6040.
- what about blocking ecn-enabled traffic? ditto.

from RFC6040:
   Ensuring congestion
   markings are not lost is itself an aspect of security, because if
we
   allowed congestion notification to be lost, any attempt to enforce
a
   response to congestion would be much harder.

so I think this section needs a little more work.

12) I think this document might need an operational considerations
section that talks about the potential need to deploy ECN-tunneling
support in networks that use ECN and cl-edge metering/marking. plus a
discussion of the effect blocking of ECN might have for an operator.

There may be other operational considerations involved that will delay
IESG approval. 

The OPS area developed a set of guidelines for operational and
management considerations (RFC5706), and the OPS ADs are checking for
these considerations in documents coming before the IESG. Have we
checked to see if we would pass such a check? 

The OPS-dir has developed a checklist of things for reviewers to look
for when reviewing documents. Would we pass their checklist? (FYI, I
am pushing for similar guidelines and a checklist for transport issues
because not all authors bother to consider and document issues of
congestion control, ECN/PCN, timer values, etc.)

13) I think this document needs a management considerations section to
discuss how the operator can tell what is happening to the traffic in
their network. If you're dropping, tunneling, metering, etc. how is
that made visible to the operator? Does the Diffserv-MIB have that
information? 

MUST an implementer of CL-edge metering be sure that the CL metering
is reflected in the Diffserv-MIB's diffServMeterTable? where do you
say that?

How are the drops counted? are blocked ecn packets counted as drops?
in which statistic?

as an operator, where should I look to find the t-meas,
t-maxsuppresssion, and t-fail values in effect? 

the parameters required differ depending on where in the system you
are, as described in 5.4. How are these parameters made accessible to
the operator? Do each of these parameters have a default value? Are
there different compliance rules for a PCN-ingress-node implementation
than for a PCN-egress-node, than for an interior versus border node?
as an operator, how can I tell whether a decision point is using the
right mapping between IEA and corrseponding ingress and egress nodes?

How do you expect the confugraiton to be done? will you use an IETf
standard configuration protocol like netconf? proprietary CLIs? is
there a requirement that these be consistent across vendors? If there
are implied requirements about the responsibilities of border vs
interior nodes, and the border routers from vendor A use different
approaches to configuration than interior routers from vendor B, how
can you be sure they will work together properly? 

What are the ranges of acceptable values for parameters like t-fail
and t-meas? do these need to be consistent across implementations, or
are they only important within an implementation? What range does an
interior node need to support (conservative in what you send), and
what range of values does a decision point need to support (liberal in
what you receive)? What if two implementers support non-overlaping
ranges for these two ends of the communication?

I think this needs work.

(and don't tell me "it's not in the charter" - it is an IESG
expectation that protocols be operational and manageable and secure,
among other things. I can show you many IETF charters that never
mention congestion control, but specifications are still required to
talk about congestion control if use of the protocol could cause
congestion.)

David Harrington
Director, IETF Transport Area
ietfdbh@comcast.net (preferred for ietf)
dbharrington@huaweisymantec.com
+1 603 828 1401 (cell)


From tom111.taylor@bell.net  Tue Dec 21 12:18:14 2010
Return-Path: <tom111.taylor@bell.net>
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 602213A6B59 for <pcn@core3.amsl.com>; Tue, 21 Dec 2010 12:18:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.766
X-Spam-Level: 
X-Spam-Status: No, score=-101.766 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 rgmaIIpHvMCm for <pcn@core3.amsl.com>; Tue, 21 Dec 2010 12:18:13 -0800 (PST)
Received: from blu0-omc1-s36.blu0.hotmail.com (blu0-omc1-s36.blu0.hotmail.com [65.55.116.47]) by core3.amsl.com (Postfix) with ESMTP id 285F83A68A6 for <pcn@ietf.org>; Tue, 21 Dec 2010 12:18:13 -0800 (PST)
Received: from BLU0-SMTP60 ([65.55.116.7]) by blu0-omc1-s36.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 21 Dec 2010 12:20:09 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP60A35E428048635CE9011AD81A0@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP60.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 21 Dec 2010 12:20:08 -0800
Date: Tue, 21 Dec 2010 15:20:09 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Michael Menth <menth@informatik.uni-tuebingen.de>
References: <BLU0-SMTP6925E6F0F2A375BD4A4E6CD8150@phx.gbl> <4D0D3887.1060307@informatik.uni-tuebingen.de>
In-Reply-To: <4D0D3887.1060307@informatik.uni-tuebingen.de>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Dec 2010 20:20:09.0007 (UTC) FILETIME=[76A173F0:01CBA14C]
Cc: pcn@ietf.org
Subject: Re: [PCN] draft-ietf-pcn-cl-edge-behaviour-08 posted
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/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, 21 Dec 2010 20:18:14 -0000

Thank you for your review. In this awkward stage between the end of WGLC 
and the beginning of IETF Last Call, I'm not sure I can do anything to 
the document beyond satisfying AD comments. I'll take Steven Blake's 
advice on that, as PROTO Shepherd.

In any event, I have comments on some of your points. Please see below.

On 18/12/2010 5:41 PM, Michael Menth wrote:
> Hi Tom,
>
> Hi Tom,
>
> thank you for your hard work in editing the two drafts.
> I reviewed the latest version of the CL document. Here are my comments.
>
> p5: of the Disffserv codepoint and ECN fields -> and the ECN field.

[PTT] Can't change that -- it's a direct quotation. Anyway, I think it's 
correct. The sentence is talking about the behaviour aggregate.
>
> p6: threshold-marked and excess-traffic-marked is not defined; the fact
> that
> it is only defined in 3.2.1 makes the doc harder to read. I suggest
> defining
> it in the terminology section to help the reader.

[PTT] Face it, if you don't read the architecture document you can't 
really understand this one.

> I still do not understand why the reference to the 3-in-1 marking was left
> while its content is basically repeated in this doc.

[PTT] Process issues. It would introduce an undesirable dependency.
>
> p7: def. of SAR: The estimated maximum rate of PCN-traffic that can be
> admitted to
> -> ... can be tolerated on ...
> At that stage, no more flows could be admitted!
>
> p7/8: T-* (3x): An interval, the value of which is configurable, ...
> -> An interval whose duration is configurable ...

[PTT] Toby Moncaster didn't like that either. Guess it's a choice 
between grammatical correctness ("who" refers to persons) and 
naturalness of expression. As Churchill said: "That is a criticism up 
with which I will not put!"
>
> p9: ThM-rate: ... (i.e., marked with the PM codepoint);
> -> marked with the EXP codepoint).
>
> ETM-rate: ... (i.e., marked with the EXP codepoint).
> -> marked with the PM codepoint.

[PTT] Good catch! That has to be fixed right away, regardless of the 
stage of process.
>
> p10: T-maxsuppress functions as a keep-alive mechanism ...
> -> as a hello mechanism
> (these messages do not keep anything alive, they just show liveliness)
>
> p11: This provides some protection against loss of egress reports and ...
> Hm, I don't think this provides protection, it just makes visible that
> something does not work anymore. Either drop this sentence or clarify
> what your exactly mean!
>
> p12: an amount of flow -> flows

[PTT] First it detewrmines an amount, then it selects flows to achieve 
that amount.
>
> p13: If the difference ... single round of decision. Alternatively ...
> [MeLe10]).
>
> -> If the difference calculated in the second round is positive, it
> is an estimate for the PCN traffic rate of the respective
> ingress-egress-aggregate that should be terminated to remove overload
> (excess of PCN-supportable-rate) on some link. The Decision Point SHOULD
> terminate traffic until the PCN-sent-rate is no longer greater than SAR.
>
> There are different strategies for the Decision Point to remove excess
> traffic. For instance, it may terminate an appropriate set of flows in
> one shot if it knows exact flow rates, e.g. from resource signalling,
> or it may terminate traffic incrementally over several measurement
> intervals. Special care has to be taken if the difference is less than
> than the rate than the smallest rate of the flows in the corresponding
> ingress-egress-aggregate. Some termination options have been proposed and
> investigated in Section 4.6 of [MeLe10].
>
> If the Decision Point has to terminate traffic more than once, it is
> RECOMMENDED that sufficient time has elapsed between successive termination
> steps so that the effect of previous termination steps is reflected in the
> measurements upon which the current termination decision is based.
> Otherwise, too much traffic may be terminated so that overtermination
> occurs [IEEE-Satoh and Sections 4.2 and 4.3 of [MeLe10]].
>
> p13
> 3.3.3 Decision Point Action For -> for
> Missing PCN-Boundary -> Missing PCN-Boundary
>
> p14 observation of at least thirty PCN-packets
> Where does this number come from?

[PTT] It's the number you need to get the standard deviation of the 
average below a certain level if you are observing normally-distributed 
variates. Maybe a stretch to apply it to this statistical context, but 
better than nothing.
>
> 3.5 Summary of Timers
> Here some streamlining is needed. T-* was introduced as an interval
> in the terminology section, now T-* is the actual value and t-* is the
> name of the timer. Is the latter one required at all in the doc?

[PTT] Yes, otherwise how can I talk about action taken upon expiry?
>
> IEA is defined only over Table 1. I missed that while reading. Why not
> introduce "IEA" as an abbreviation in the terminology section?

[PTT] The table is the only point at which it is used in the document. I 
have to use it there for lack of space, otherwise I would avpoid it 
entirely.
>
>
> p15 ... keep-alive procedure.
> -> hello-mechanism. ?
> keep-alive is actually needed when a softstate needs to be maintained,
> this is here not the case. Or is it? If so, make it explicit!
>
> ... as proposed by the transport protocol specification.
> What are you referring to? This is hard to understand. Sounds like the
> signalling draft which is not cited ...

[PTT] What I am referring to is the document that specifies the actual 
transport protocol. The only concrete candidate at the moment is the 
proposal I've co-authored with others to use Diameter for the purpose. 
BTW none of this will apply for the piggybacking edge behaviour, if that 
ever gets written up.
>
> The means by which this is done ...
> "this" refers to the last sentence which does not make sense. You mean
> another sentence before: rephrase! A new paragraph is not needed.
>
> p16 (e.g. due to network failures): that is very general and maybe not
> so clear
> -> (e.g. due to link or node failures with subsequent rerouting)
>
> The CL boundary node behaviour is less ...
> -> The performance results in [MeLe10] have shown that the CL ...
>
> 5.2.1 ... PCN-ingress-nodes MUST block ECN-capable traffic that uses the
> same DSCP as PCN ...
>
> I don't agree. I think that the ECN field of such traffic should be set
> to 00 (not-ECN), which means that ECN is basically disabled. That's better
> than dropping or downgrading the traffic.

[PTT] File an erratum against RFC 5559, then.
>
> ... Packets belonging to ... flowspec.
>
> ... flowspec that were possibly signalled by a resource signalling protocol
> for flow admission.
>
> 5.2.2
>
> The meaning of this sentence is not clear to me:
> "As a result, they are not tied to the selection of a specific DSCP value".
> Does that mean that PCN will be available for mulitple DSCPs? That's
> what we
> always said no, but this sentence could be interpreted that way! This
> section
> is not yet very comprehensible.

[PTT] File an erratum against RFC 5696, which this quotes.
>
> p17
>
> o Whether ... (2x)
> -> o Indication whether ...
>
> p18
>
> ... to map between ... PCN-egress-node
> ->
> o The information needed to map an ingress-egress-aggregates to a
> corresponding PCN-ingress-nodes and a corresponding PCN-egress-node.
>
> 5.5 Assumptions
>
> This section calls for bullets to simplify reading.
>
> I'll review the SM-draft only in the next version when these and other
> corrections have been applied.
>
> Best wishes,
>
> Michael
>
...

From tom111.taylor@bell.net  Tue Dec 21 12:28:32 2010
Return-Path: <tom111.taylor@bell.net>
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 95DFA3A6AA2 for <pcn@core3.amsl.com>; Tue, 21 Dec 2010 12:28:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.767
X-Spam-Level: 
X-Spam-Status: No, score=-101.767 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, USER_IN_WHITELIST=-100]
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 k0ER5-tSQZ1k for <pcn@core3.amsl.com>; Tue, 21 Dec 2010 12:28:32 -0800 (PST)
Received: from blu0-omc1-s13.blu0.hotmail.com (blu0-omc1-s13.blu0.hotmail.com [65.55.116.24]) by core3.amsl.com (Postfix) with ESMTP id D4CF83A6A6B for <pcn@ietf.org>; Tue, 21 Dec 2010 12:28:31 -0800 (PST)
Received: from BLU0-SMTP87 ([65.55.116.7]) by blu0-omc1-s13.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 21 Dec 2010 12:30:28 -0800
X-Originating-IP: [70.26.23.173]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP8759E3C762F54F4FE21F93D81A0@phx.gbl>
Received: from [192.168.2.17] ([70.26.23.173]) by BLU0-SMTP87.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 21 Dec 2010 12:30:27 -0800
Date: Tue, 21 Dec 2010 15:30:28 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Michael Menth <menth@informatik.uni-tuebingen.de>
References: <BLU0-SMTP6925E6F0F2A375BD4A4E6CD8150@phx.gbl>	<4D0D3887.1060307@informatik.uni-tuebingen.de> <BLU0-SMTP60A35E428048635CE9011AD81A0@phx.gbl>
In-Reply-To: <BLU0-SMTP60A35E428048635CE9011AD81A0@phx.gbl>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Dec 2010 20:30:27.0920 (UTC) FILETIME=[E7881500:01CBA14D]
Cc: pcn@ietf.org
Subject: Re: [PCN] draft-ietf-pcn-cl-edge-behaviour-08 posted
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/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, 21 Dec 2010 20:28:32 -0000

Needless to say, I started writing this a few hours ago, before all the 
other notes arrived on the list, and didn't check the list until I sent 
it. I'll look them over.

On 21/12/2010 3:20 PM, Tom Taylor wrote:
> Thank you for your review. In this awkward stage between the end of WGLC
> and the beginning of IETF Last Call, I'm not sure I can do anything to
> the document beyond satisfying AD comments. I'll take Steven Blake's
> advice on that, as PROTO Shepherd.
...
