Document Action: 'PCN Boundary Node Behaviour for the Single Marking (SM) Mode of Operation' to Experimental RFC (draft-ietf-pcn-sm-edge-behaviour-12.txt)

The IESG <iesg-secretary@ietf.org> Mon, 23 April 2012 19:28 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'PCN Boundary Node Behaviour for the Single Marking (SM) Mode of Operation' to Experimental RFC (draft-ietf-pcn-sm-edge-behaviour-12.txt)
Message-ID: <20120423192850.16522.36356.idtracker@ietfa.amsl.com>
Date: Mon, 23 Apr 2012 12:28:50 -0700
Cc: pcn mailing list <pcn@ietf.org>, pcn chair <pcn-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Precedence: list

The IESG has approved the following document:
- 'PCN Boundary Node Behaviour for the Single Marking (SM) Mode of
   Operation'
  (draft-ietf-pcn-sm-edge-behaviour-12.txt) as an Experimental RFC

This document is the product of the Congestion and Pre-Congestion
Notification Working Group.

The IESG contact persons are Martin Stiemerling and Wesley Eddy.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-pcn-sm-edge-behaviour/




Technical Summary

This document describes a possible boundary node behaviour
 for a PCN-domain (as defined in RFC 5559), known informally as
 the Single Marking (SM) PCN-boundary-node behaviour.
The behaviour described here is a form of measurement-based
load control using two PCN marking states: not-marked, and 
excess-traffic-marked.

Working Group Summary

The document was subject to thorough review by the PCN working
group, and strong consensus for publication was reached.

The area director required substantial re-write of the document to address
a lack of operations and management considerations. 

IETF Last Call raised an issue about the lack of any standardized 
signaling protocol between the egress and ingress nodes. 
Subsequent work by the WG on one possible signaling protocol (RSVP)
was developed, but this protocol required an extension to RSVP.
This protocol work item was transferred from the PCN WG charter to the
TSVWG WG charter where most RSVP experts are active. The
document required a re-write to discuss operational considerations
for signaling protocols, and a suggestion that the RSVP extension
would be suitable in RSVP environments.

The logging description used enterprise-specific structured data rather
than standardized structured data, and the area director recommended this be changed,
which it was.

A second WGLC and a second IETF Last Call were performed, given
the extensive modifications to the document.

Document Quality

There are existing implementations of the protocol, and the
document cites research that has been done measuring the performance of 
this approach.

The document has been reviewed by the OPSDIR
The document has been reviewed by the SECDIR. No problems were identified.

Personnel

   Document Shepherd: Steven Blake, PCN co-chair <slblake@petri-meat.com>
   Responsible Area Director: Martin Stiemerling

Document Action: 'PCN Boundary Node Behaviour for… The IESG