This document describes a possible boundary node behaviour
for a PCN-domain (as defined in RFC 5559), known informally as
the Controlled Load (CL) PCN-boundary-node behaviour.
The behaviour described here is a form of measurement-based
load control using three PCN marking states: not-marked,
threshold-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. Joel Halpern raised an issue about
being able to determine ingress-egress-aggregate relationships.
There are existing implementations of the protocol, and the
document cites research that has been done measuring the performance of
The document has been reviewed by the SECDIR. No problems were identified.
David Harrington, co-chair of syslog WG, checked the IANA registration for syslog.
Document Shepherd: Steven Blake, PCN co-chair <firstname.lastname@example.org>
Responsible Area Director: Martin Stiemerling