6663
INFORMATIONAL
Requirements for Signaling of Pre-Congestion Information in a Diffserv Domain
Authors: G. Karagiannis, T. Taylor, K. Chan, M. Menth, P. Eardley
Date: July 2012
Area: tsv
Working Group: pcn
Stream: IETF
Abstract
Pre-Congestion Notification (PCN) is a means for protecting quality of service for inelastic traffic admitted to a Diffserv domain. The overall PCN architecture is described in RFC 5559. This memo describes the requirements for the signaling applied within the PCN-domain: (1) PCN-feedback-information is carried from the PCN-egress-node to the Decision Point; (2) the Decision Point may ask the PCN-ingress-node to measure, and report back, the rate of sent PCN-traffic between that PCN-ingress-node and PCN-egress-node. The Decision Point may be either collocated with the PCN-ingress-node or a centralized node (in the first case, (2) is not required). The signaling requirements pertain in particular to two edge behaviors, Controlled Load (CL) and Single Marking (SM). This document is not an Internet Standards Track specification; it is published for informational purposes.
RFC 6663
INFORMATIONAL
Internet Engineering Task Force (IETF) G. Karagiannis
Request for Comments: 6663 University of Twente
Category: Informational T. Taylor
ISSN: 2070-1721 Huawei
K. Chan
Consultant
M. Menth
University of Tuebingen
P. Eardley
BT
July 2012
<span class="h1">Requirements for Signaling of Pre-Congestion Information</span>
<span class="h1">in a Diffserv Domain</span>
Abstract
Pre-Congestion Notification (PCN) is a means for protecting quality
of service for inelastic traffic admitted to a Diffserv domain. The
overall PCN architecture is described in <a href="./rfc5559">RFC 5559</a>. This memo
describes the requirements for the signaling applied within the PCN-
domain: (1) PCN-feedback-information is carried from the PCN-egress-
node to the Decision Point; (2) the Decision Point may ask the PCN-
ingress-node to measure, and report back, the rate of sent PCN-
traffic between that PCN-ingress-node and PCN-egress-node. The
Decision Point may be either collocated with the PCN-ingress-node or
a centralized node (in the first case, (2) is not required). The
signaling requirements pertain in particular to two edge behaviors,
Controlled Load (CL) and Single Marking (SM).
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc6663">http://www.rfc-editor.org/info/rfc6663</a>.
<span class="grey">Karagiannis, et al. Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc6663">RFC 6663</a> PCN Signaling Requirements July 2012</span>
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Requirements Language ......................................<a href="#page-3">3</a>
2. Signaling Requirements for Messages from the PCN-Egress-Nodes
to Decision Point(s) ............................................<a href="#page-3">3</a>
3. Signaling Requirements for Messages between Decision Point(s)
and PCN-Ingress-Nodes ...........................................<a href="#page-5">5</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-5">5</a>
<a href="#section-5">5</a>. Acknowledgments .................................................<a href="#page-6">6</a>
<a href="#section-6">6</a>. References ......................................................<a href="#page-6">6</a>
<a href="#section-6.1">6.1</a>. Normative References .......................................<a href="#page-6">6</a>
<a href="#section-6.2">6.2</a>. Informative References .....................................<a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The main objective of Pre-Congestion Notification (PCN) is to support
the quality of service (QoS) of inelastic flows within a Diffserv
domain in a simple, scalable, and robust fashion. Two mechanisms are
used: admission control and flow termination. Admission control is
used to decide whether to admit or block a new flow request, while
flow termination is used in abnormal circumstances to decide whether
to terminate some of the existing flows. To support these two
features, the overall rate of PCN-traffic is metered on every link in
the domain, and PCN-packets are appropriately marked when certain
configured rates are exceeded. These configured rates are below the
rate of the link, thus providing notification to boundary nodes about
overloads before any congestion occurs (hence "pre-congestion"
notification). The PCN-egress-nodes measure the rates of differently
marked PCN traffic in periodic intervals and report these rates to
the Decision Points for admission control and flow termination; the
Decision Points use these rates to make decisions. The Decision
Points may be collocated with the PCN-ingress-nodes, or their
<span class="grey">Karagiannis, et al. Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc6663">RFC 6663</a> PCN Signaling Requirements July 2012</span>
function may be implemented in a centralized node. For more details
see [<a href="./rfc5559" title=""Pre-Congestion Notification (PCN) Architecture"">RFC5559</a>], [<a href="./rfc6661" title=""Pre-Congestion Notification (PCN) Boundary-Node Behaviour for the Controlled Load (CL) Mode of Operation"">RFC6661</a>], and [<a href="./rfc6662" title=""Pre-Congestion Notification (PCN) Boundary-Node Behaviour for the Single Marking (SM) Mode of Operation"">RFC6662</a>].
This memo specifies the requirements on signaling protocols:
o to carry reports from a PCN-egress-node to the Decision Point,
o to carry requests, from the Decision Point to a PCN-ingress-node,
that trigger the PCN-ingress-node to measure the PCN-sent-rate,
o to carry reports, from a PCN-ingress-node to the Decision Point.
The latter two messages are only needed if the Decision Point and
PCN-ingress-node are not collocated.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Signaling Requirements for Messages from the PCN-Egress-Nodes to</span>
<span class="h2"> Decision Point(s)</span>
The PCN-egress-node measures per ingress-egress-aggregate the rates
of differently marked PCN-traffic in regular intervals. The
measurement intervals are recommended to take a fixed value between
100 ms and 500 ms; see [<a href="./rfc6661" title=""Pre-Congestion Notification (PCN) Boundary-Node Behaviour for the Controlled Load (CL) Mode of Operation"">RFC6661</a>] and [<a href="./rfc6662" title=""Pre-Congestion Notification (PCN) Boundary-Node Behaviour for the Single Marking (SM) Mode of Operation"">RFC6662</a>]. At the end of each
measurement interval, the PCN-egress-node calculates the congestion-
level-estimate (CLE) based on these quantities.
The PCN-egress-node MAY be configured to record a set of identifiers
of PCN-flows for which it received excess-traffic-marked packets
during the last measurement interval. The latter may be useful to
perform flow termination in networks with multipath routing.
At the end of each measurement interval, or less frequently if
"optional report suppression" is activated (see [<a href="./rfc6661" title=""Pre-Congestion Notification (PCN) Boundary-Node Behaviour for the Controlled Load (CL) Mode of Operation"">RFC6661</a>] and
[<a href="./rfc6662" title=""Pre-Congestion Notification (PCN) Boundary-Node Behaviour for the Single Marking (SM) Mode of Operation"">RFC6662</a>]), the PCN-egress-node sends a report to the Decision Point.
For the SM edge behavior, the report MUST contain:
o the identifier of the PCN-ingress-node and the identifier of the
PCN-egress-node (typically their IP addresses); together they
specify the ingress-egress-aggregate to which the report refers,
o the rate of not-marked PCN-traffic (NM-rate) in octets/second, and
o the rate of PCN-marked traffic (PM-rate) in octets/second.
For the CL edge behavior, the report MUST contain:
o the identifier of the PCN-ingress-node and the identifier of the
PCN-egress-node (typically their IP addresses); together they
specify the ingress-egress-aggregate to which the report refers,
<span class="grey">Karagiannis, et al. Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc6663">RFC 6663</a> PCN Signaling Requirements July 2012</span>
o the rate of not-marked PCN-traffic (NM-rate) in octets/second,
o the rate of threshold-marked PCN traffic (ThM-rate) in
octets/second, and
o the rate of excess-traffic-marked traffic (ETM-rate) in
octets/second.
The number format and the rate units used by the signaling protocol
will limit the maximum rate that PCN can use. If signaling space is
tight, it might be reasonable to impose a limit, but any such limit
may impose unnecessary constraints in the future.
The signaling report can either be sent directly to the Decision
Point or it can "piggy-back", i.e., be included within some other
message that passes through the PCN-egress-node and then reaches the
Decision Point.
As described in [<a href="./rfc6661" title=""Pre-Congestion Notification (PCN) Boundary-Node Behaviour for the Controlled Load (CL) Mode of Operation"">RFC6661</a>], PCN reports from the PCN-egress-node to
the Decision Point may contain flow identifiers for individual flows
within an ingress-egress-aggregate that have recently experienced
excess-marking. Hence, the PCN report messages used by the PCN CL
edge behavior MUST be capable of carrying sequences of octet strings
constituting such identifiers.
Signaling messages SHOULD have a higher priority and a lower drop
precedence than PCN-packets (see [<a href="./rfc5559" title=""Pre-Congestion Notification (PCN) Architecture"">RFC5559</a>]) in order to deliver them
quickly and to prevent them from being dropped in case of overload.
The load generated by the signaling protocol SHOULD be minimized. We
give three methods that may help to achieve that goal:
1. piggy-backing the reports by the PCN-egress-nodes to the Decision
Point(s) onto other signaling messages that are already in place,
2. reducing the amount of reports to be sent by optional report
suppression, or
3. combining reports for different ingress-egress-aggregates in a
single message (if they are for the same Decision Point).
As PCN reports are sent regularly, additional reliability mechanisms
are not needed. This also holds in the presence of optional report
suppression, as reports are sent periodically if actions by the
Decision Point(s) are needed; see [<a href="./rfc6661" title=""Pre-Congestion Notification (PCN) Boundary-Node Behaviour for the Controlled Load (CL) Mode of Operation"">RFC6661</a>] and [<a href="./rfc6662" title=""Pre-Congestion Notification (PCN) Boundary-Node Behaviour for the Single Marking (SM) Mode of Operation"">RFC6662</a>].
<span class="grey">Karagiannis, et al. Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc6663">RFC 6663</a> PCN Signaling Requirements July 2012</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Signaling Requirements for Messages between Decision Point(s) and</span>
<span class="h2"> PCN-Ingress-Nodes</span>
Through request-response signaling between the Decision Point and
PCN-ingress-node, the Decision Point requests and in response the
PCN-ingress-node measures and reports the PCN-sent-rate for a
specific ingress-egress-aggregate. Signaling is needed only if the
Decision Point and PCN-ingress-node are not collocated.
The request MUST contain:
o the identifier of the PCN-ingress-node and the identifier of the
PCN-egress-node; together they determine the ingress-egress-
aggregate for which the PCN-sent-rate is requested, and
o the identifier of the Decision Point that requests the PCN-sent-
rate.
The report MUST contain:
o the PCN-sent-rate in octets/second, and
o the identifier of the PCN-ingress-node and the identifier of the
PCN-egress-node.
The request MUST be addressed to the PCN-ingress-node, and the report
MUST be addressed to the Decision Point that requested it.
Because they are sent only when flow termination is needed (which is
an urgent action), the request and the report SHOULD be sent with
high priority, with a lower drop precedence than PCN-packets, and in
a reliable manner.
Note that a complete system description for a PCN-domain with
centralized Decision Point includes the signaling from Decision Point
to the PCN-ingress-nodes to control flow admission and termination.
However, this is a known problem (with solutions provided in
[<a href="./rfc3084" title=""COPS Usage for Policy Provisioning (COPS-PR)"">RFC3084</a>] and [<a href="./rfc5431" title=""Diameter ITU-T Rw Policy Enforcement Interface Application"">RFC5431</a>], for example), and it lies outside the scope
of the present document.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
[<a id="ref-RFC5559">RFC5559</a>] provides a general description of the security
considerations for PCN. This memo relies on the security-related
requirements of the PCN signaling, provided in [<a href="./rfc5559" title=""Pre-Congestion Notification (PCN) Architecture"">RFC5559</a>]. In
particular, the signaling between the PCN-boundary-nodes must be
protected from attacks. For example, the recipient needs to validate
that the message is indeed from the node that claims to have sent it.
Possible measures include digest authentication and protection
against replay and man-in-the-middle attacks.
<span class="grey">Karagiannis, et al. Informational [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc6663">RFC 6663</a> PCN Signaling Requirements July 2012</span>
Specifically for the generic aggregate RSVP protocol, additional
protection methods against security attacks are described in
[<a href="./rfc4860" title=""Generic Aggregate Resource ReSerVation Protocol (RSVP) Reservations"">RFC4860</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span>
We would like to acknowledge the members of the PCN working group for
the discussions that produced the contents of this memo.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC5559">RFC5559</a>] Eardley, P., Ed., "Pre-Congestion Notification (PCN)
Architecture", <a href="./rfc5559">RFC 5559</a>, June 2009.
[<a id="ref-RFC6661">RFC6661</a>] Charny, A., Huang, F., Karagiannis, G., Twente, U., Menth,
M., and T. Taylor, Ed., "Pre-Congestion Notification (PCN)
Boundary-Node Behaviour for the Controlled Load (CL) Mode
of Operation", <a href="./rfc6661">RFC 6661</a>, July 2012.
[<a id="ref-RFC6662">RFC6662</a>] Charny, A., Zhang, J., Karagiannis, G., Twente, U., Menth,
M., and T. Taylor, Ed., "Pre-Congestion Notification (PCN)
Boundary-Node Behaviour for the Single Marking (SM) Mode
of Operation", <a href="./rfc6662">RFC 6662</a>, July 2012.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-RFC3084">RFC3084</a>] Chan, K., Seligson, J., Durham, D., Gai, S., McCloghrie,
K., Herzog, S., Reichmeyer, F., Yavatkar, R., and A.
Smith, "COPS Usage for Policy Provisioning (COPS-PR)", <a href="./rfc3084">RFC</a>
<a href="./rfc3084">3084</a>, March 2001.
[<a id="ref-RFC4860">RFC4860</a>] Le Faucheur, F., Davie, B., Bose, P., Christou, C., and M.
Davenport, "Generic Aggregate Resource ReSerVation
Protocol (RSVP) Reservations", <a href="./rfc4860">RFC 4860</a>, May 2007.
[<a id="ref-RFC5431">RFC5431</a>] Sun, D., "Diameter ITU-T Rw Policy Enforcement Interface
Application", <a href="./rfc5431">RFC 5431</a>, March 2009.
<span class="grey">Karagiannis, et al. Informational [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc6663">RFC 6663</a> PCN Signaling Requirements July 2012</span>
Authors' Addresses
Georgios Karagiannis
University of Twente
P.O. Box 217
7500 AE Enschede,
The Netherlands
EMail: [email protected]
Tom Taylor
Huawei Technologies
Ottawa
Canada
EMail: [email protected]
Kwok Ho Chan
Consultant
EMail: [email protected]
Michael Menth
University of Tuebingen
Sand 13
72076 Tuebingen
Germany
Phone: +49-7071-2970505
EMail: [email protected]
Philip Eardley
BT
B54/77, Sirius House Adastral Park Martlesham Heath
Ipswich, Suffolk IP5 3RE
United Kingdom
EMail: [email protected]
Karagiannis, et al. Informational [Page 7]
Annotations
Select text to annotate