Re: [PCN] FW: New Version Notification fordraft-ietf-pcn-baseline-encoding-05

[<Ruediger.Geib at telekom.de>]

I've read A1 only and think this text is allright from what it intends to say. 

Phil had some comments, one of which was related to CS5. While I'm aware of EF 
and some AF codepoints to be commercially deployed, I'd have to study my 
archived material to see, whether any of the class/codepoint schemes I've seen 
uses CS5 on IP level. 

But I don't fundamentally object to adding CS5 to the A1 list of recommended 
DSCP's (as I only know a few class/codepoint concepts).

Regards,

Ruediger

-----Original Message-----
From: pcn-bounces at ietf.org [mailto:pcn-bounces at ietf.org] On Behalf Of toby.moncaster at bt.com
Sent: Thursday, August 20, 2009 5:19 PM
To: pcn at ietf.org; lars.eggert at nokia.com
Subject: [PCN] FW: New Version Notification fordraft-ietf-pcn-baseline-encoding-05

I hope this accurately reflects the ML discussions over the past few days? I have also corrected all the nits and hopefully haven't left any spelling mistakes or typos...

Toby

____________________________________________________________________ 
Toby Moncaster, <toby.moncaster at bt.com> Networks Research Centre, BT 
B54/70 Adastral Park, Ipswich, IP53RE, UK.  +44 7918 901170 



-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission at ietf.org] 
Sent: 20 August 2009 16:17
To: Moncaster,T,Toby,DER3 R
Cc: Briscoe,RJ,Bob,DER3 R; menth at informatik.uni-wuerzburg.de
Subject: New Version Notification for draft-ietf-pcn-baseline-encoding-05 


A new version of I-D, draft-ietf-pcn-baseline-encoding-05.txt has been successfuly submitted by T Moncaster and posted to the IETF repository.

Filename:	 draft-ietf-pcn-baseline-encoding
Revision:	 05
Title:		 Baseline Encoding and Transport of Pre-Congestion Information
Creation_date:	 2009-08-20
WG ID:		 pcn
Number_of_pages: 14

Abstract:
The objective of Pre-Congestion Notification (PCN) is to protect the
quality of service (QoS) of inelastic flows within a Diffserv domain.
The overall rate of the PCN-traffic is metered on every link in the
PCN-domain, and PCN-packets are appropriately marked when certain
configured rates are exceeded.  The level of marking allows the
boundary nodes to make decisions about whether to admit or block a
new flow request, and (in abnormal circumstances) whether to
terminate some of the existing flows, thereby protecting the QoS of
previously admitted flows.  This document specifies how such marks
are to be encoded into the IP header by re-using the Explicit
Congestion Notification (ECN) codepoints within this controlled
domain.  The baseline encoding described here provides for only two
PCN encoding states, Not-marked and PCN-marked.
                                                                                  


The IETF Secretariat.


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