draft-ietf-tsvwg-rsvp-pcn-02.txt   draft-ietf-tsvwg-rsvp-pcn-03.txt 
Internet Engineering Task Force Georgios Karagiannis Internet Engineering Task Force Georgios Karagiannis
Internet-Draft University of Twente Internet-Draft University of Twente
Intended status: Standards Track Anurag Bhargava Intended status: Experimental Anurag Bhargava
Expires: January 07, 2013 Cisco Systems, Inc. Expires: April 12, 2013 Cisco Systems, Inc.
July 07, 2012 October 12, 2012
Generic Aggregation of Resource ReSerVation Protocol (RSVP) Generic Aggregation of Resource ReSerVation Protocol (RSVP)
for IPv4 And IPv6 Reservations over PCN domains for IPv4 And IPv6 Reservations over PCN domains
draft-ietf-tsvwg-rsvp-pcn-02 draft-ietf-tsvwg-rsvp-pcn-03
Abstract Abstract
This document specifies the extensions to the Generic Aggregated RSVP This document specifies the extensions to the Generic Aggregated RSVP
[RFC4860] for support of the PCN Controlled Load (CL) and Single [RFC4860] for support of the PCN Controlled Load (CL) and Single
Marking (SM) edge behaviors over a Diffserv cloud using Pre- Marking (SM) edge behaviors over a Diffserv cloud using Pre-
Congestion Notification. Congestion Notification.
Status of this Memo Status of this Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 07, 2013. This Internet-Draft will expire on April 12, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 52 skipping to change at page 5, line 52
"pre" part of "pre-congestion notification"). The level of marking "pre" part of "pre-congestion notification"). The level of marking
allows decisions to be made about whether to admit or terminate PCN- allows decisions to be made about whether to admit or terminate PCN-
flows. flows.
The PCN-egress-nodes measure the rates of differently marked The PCN-egress-nodes measure the rates of differently marked
PCN-traffic in periodic intervals and report these rates to the PCN-traffic in periodic intervals and report these rates to the
decision points for admission control and flow termination, based on decision points for admission control and flow termination, based on
which they take their decisions. The decision points may be which they take their decisions. The decision points may be
collocated with the PCN-ingress-nodes or their function may be collocated with the PCN-ingress-nodes or their function may be
implemented in a centralized node. For more details see [RFC5559], implemented in a centralized node. For more details see [RFC5559],
[draft-ietf-pcn-cl-edge-behaviour-15], [draft-ietf-pcn-sm-edge- [RFC6661], [RFC6662]. In this document it is considered that the
behaviour-12]. In this document it is considered that the decision decision point is collocated with the PCN-ingress-node.
point is collocated with the PCN-ingress-node.
This document follows the PCN signaling requirements defined in This document follows the PCN signaling requirements defined in
[draft-ietf-pcn-signaling-requirements-08.txt] and specifies the [RFC6663] and specifies the
extensions to the Generic Aggregated RSVP [RFC4860] for the support extensions to the Generic Aggregated RSVP [RFC4860] for the support
of PCN edge behaviors as specified in [draft-ietf-pcn-cl-edge- of PCN edge behaviors as specified in [RFC6661] and [RFC6662].
behaviour-15] and [draft-ietf-pcn-sm-edge-behaviour-12]. Moreover, Moreover, this document specifies how RSVP aggregation can be used to
this document specifies how RSVP aggregation can be used to setup and setup and maintain: (1) Ingress Egress Aggregate (IEA) states at
maintain: (1) Ingress Egress Aggregate (IEA) states at Ingress and Ingress and Egress nodes and (2) generic aggregation of RSVP end-to-
Egress nodes and (2) generic aggregation of RSVP end-to-end RSVP end RSVP reservations over PCN (Congestion and Pre-Congestion
reservations over PCN (Congestion and Pre-Congestion Notification) Notification) domains.
domains.
This document, and according to [RFC4860] MAY also be used end-to-end This document, and according to [RFC4860] MAY also be used end-to-end
directly by end-systems attached to a Diffserv network. directly by end-systems attached to a Diffserv network.
Furthermore, this document and according to [RFC4860], in absence of Furthermore, this document and according to [RFC4860], in absence of
e2e RSVP flows, a variety of policies (not defined in this document) e2e RSVP flows, a variety of policies (not defined in this document)
can be used at the Aggregator to set the DSCP of packets passing into can be used at the Aggregator to set the DSCP of packets passing into
the aggregation region and how they are mapped onto generic aggregate the aggregation region and how they are mapped onto generic aggregate
reservations. These policies are not described in this document but reservations. These policies are not described in this document but
are a matter of local configuration. are a matter of local configuration.
In this document it is considered that the PCN-nodes MUST be able to In this document it is considered that the PCN-nodes MUST be able to
support the functionality specified in [RFC5670], [RFC5559], support the functionality specified in [RFC5670], [RFC5559],
[RFC5696],[draft-ietf-pcn-cl-edge-behaviour-15], [draft-ietf-pcn-sm- [RFC6660], [RFC6661], [RFC6662]. Furthermore, the PCN-boundary-nodes
edge-behaviour-12]. Furthermore, the PCN-boundary-nodes MUST support MUST support the RSVP generic aggregated reservation procedures
the RSVP generic aggregated reservation procedures specified in specified in [RFC4860] which are augmented with procedures specified
[RFC4860] which are augmented with procedures specified in this in this document.
document.
1.1. Terminology 1.1. Terminology
This document uses terms defined in [RFC4860], [RFC3175], [RFC5559], This document uses terms defined in [RFC4860], [RFC3175], [RFC5559],
[RFC5670], [draft-ietf-pcn-cl-edge-behaviour-15], [draft-ietf-pcn-sm- [RFC5670], [RFC6661], [RFC6662].
edge-behaviour-12].
For readability, a number of definitions from [RFC3175] as well as For readability, a number of definitions from [RFC3175] as well as
definitions for terms used in [RFC5559], [draft-ietf-pcn-cl-edge- definitions for terms used in [RFC5559], [RFC6661], and [RFC6662] are
behaviour-15], and [draft-ietf-pcn-sm-edge-behaviour-12] are provided provided here, where some of them are augmented with new meanings:
here, where some of them are augmented with new meanings:
Aggregator This is the process in (or associated with) the Aggregator This is the process in (or associated with) the
router at the ingress edge of the aggregation region router at the ingress edge of the aggregation region
(with respect to the end-to-end RSVP reservation) (with respect to the end-to-end RSVP reservation)
and behaving in accordance with [RFC4860]. In this and behaving in accordance with [RFC4860]. In this
document, it is also the PCN-ingress-node and the document, it is also the PCN-ingress-node and the
decision point. decision point.
Deaggregator This is the process in (or associated with) the Deaggregator This is the process in (or associated with) the
router at the egress edge of the aggregation region router at the egress edge of the aggregation region
skipping to change at page 7, line 45 skipping to change at page 7, line 42
specified in Section 2 of [RFC3140]. specified in Section 2 of [RFC3140].
VDstPort (Virtual Destination Port) VDstPort (Virtual Destination Port)
A 16-bit identifier used in the SESSION that A 16-bit identifier used in the SESSION that
remains constant over the life of the generic remains constant over the life of the generic
aggregate reservation. aggregate reservation.
Extended vDstPort (Extended Virtual Destination Port) Extended vDstPort (Extended Virtual Destination Port)
A 32-bit identifier used in the SESSION that An identifier used in the SESSION that remains
remains constant over the life of the generic constant over the life of the generic aggregate
aggregate reservation. A sender (or Aggregator) reservation. The length of this idenitifier is 32-
bits when IPv4 addresses are used and 128 bits when
IPv6 addresses are used. A sender(or Aggregator)
that wishes to narrow the scope of a SESSION to the that wishes to narrow the scope of a SESSION to the
sender-receiver pair (or Aggregator-Deaggregator sender-receiver pair (or Aggregator-Deaggregator
pair) SHOULD place its IPv4 or IPv6 address here as pair) SHOULD place its IPv4 or IPv6 address here as
a network unique identifier. A sender (or a network unique identifier. A sender (or
Aggregator) that wishes to use a common session Aggregator) that wishes to use a common session
with other senders (or Aggregators) in order to use with other senders (or Aggregators) in order to use
a shared reservation across senders (or a shared reservation across senders (or
Aggregators) MUST set this field to all zeros. Aggregators) MUST set this field to all zeros. In
In this document, the Extended vDstPort SHOULD this document, the Extended vDstPort SHOULD contain
contain the IPv4 or IPv6 address of the Aggregator. the IPv4 or IPv6 address of the Aggregator.
PCN-domain: a PCN-capable domain; a contiguous set of PCN-domain: a PCN-capable domain; a contiguous set of
PCN-enabled nodes that perform Diffserv scheduling PCN-enabled nodes that perform Diffserv scheduling
[RFC2474]; the complete set of PCN-nodes that in [RFC2474]; the complete set of PCN-nodes that in
principle can, through PCN-marking packets, principle can, through PCN-marking packets,
influence decisions about flow admission and influence decisions about flow admission and
termination for the PCN-domain; includes termination for the PCN-domain; includes
the PCN-egress-nodes, which measure these the PCN-egress-nodes, which measure these
PCN-marks, and the PCN-ingress-nodes. PCN-marks, and the PCN-ingress-nodes.
skipping to change at page 12, line 13 skipping to change at page 12, line 13
to PCN-compatible Diffserv codepoint(s). to PCN-compatible Diffserv codepoint(s).
o) Extended vDstPort SHOULD be set to the IPv4 or IPv6 destination o) Extended vDstPort SHOULD be set to the IPv4 or IPv6 destination
addresses, of the Aggregator (PCN-ingress-node) addresses, of the Aggregator (PCN-ingress-node)
2.1.1 PCN Marking and encoding and transport of pre-congestion 2.1.1 PCN Marking and encoding and transport of pre-congestion
information information
The method of PCN marking within the PCN domain is based on The method of PCN marking within the PCN domain is based on
[RFC5670]. In addition, the method of encoding and transport of pre- [RFC5670]. In addition, the method of encoding and transport of pre-
congestion information is based [RFC5696]. The PHB-ID (Per Hop congestion information is based [RFC6660]. The PHB-ID (Per Hop
Behavior Identification Code) used, SHOULD be set equal Behavior Identification Code) used, SHOULD be set equal
to PCN-compatible Diffserv codepoint(s). to PCN-compatible Diffserv codepoint(s).
2.1.2. Traffic Classification Within The Aggregation Region 2.1.2. Traffic Classification Within The Aggregation Region
The PCN-traffic is marked using PCN-marking and is classified using The PCN-traffic is marked using PCN-marking and is classified using
The PCN-BA (i.e., combination of the DSCP and ECN fields). The PCN-BA (i.e., combination of the DSCP and ECN fields).
The PCN-traffic (e.g., e2e microflows) belonging to an ingress- The PCN-traffic (e.g., e2e microflows) belonging to an ingress-
egress-aggregate can be classified only at the PCN-boundary-nodes egress-aggregate can be classified only at the PCN-boundary-nodes
using the combination of (1) PCN-BA (i.e., combination of the DSCP using the combination of (1) PCN-BA (i.e., combination of the DSCP
and ECN fields), (2) IP addresses of the specific pair of PCN- and ECN fields), (2) IP addresses of the specific pair of PCN-
boundary-nodes used by a ingress-egress-aggregate. boundary-nodes used by a ingress-egress-aggregate.
The method of classification and traffic conditioning of PCN-traffic The method of classification and traffic conditioning of PCN-traffic
and non-PCN traffic and PHB configuration is described in draft-ietf- and non-PCN traffic and PHB configuration is described in [RFC6661]
pcn-cl-edge-behaviour-15] and [draft-ietf-pcn-sm-edge-behaviour-12]. and [RFC6662]. Moreover, the PCN-traffic (e.g., e2e microflows)
Moreover, the PCN-traffic (e.g., e2e microflows) belonging to a belonging to a RSVP generic aggregated reservation can be classified
RSVP generic aggregated reservation can be classified only at the only at the PCN-boundary-nodes (i.e., Aggregator and Deaggregator) by
PCN-boundary-nodes (i.e., Aggregator and Deaggregator) by using the using the RSVP SESSION object for RSVP generic aggregated
RSVP SESSION object for RSVP generic aggregated reservations, see reservations, see [RFC4860].
[RFC4860].
2.1.3. Deaggregator (PCN-egress-node) Determination 2.1.3. Deaggregator (PCN-egress-node) Determination
In this document it is considered that for the determination of the In this document it is considered that for the determination of the
Deaggregator, the same methods can be used as the ones described in Deaggregator, the same methods can be used as the ones described in
[RFC4860]. [RFC4860].
2.1.4. Mapping E2E Reservations Onto Aggregate Reservations 2.1.4. Mapping E2E Reservations Onto Aggregate Reservations
In this document it is considered that for the mapping of e2e In this document it is considered that for the mapping of e2e
skipping to change at page 14, line 16 skipping to change at page 14, line 16
message that arrives at the external interface of the PCN- message that arrives at the external interface of the PCN-
ingress-node is mapped/matched onto an existing RSVP generic ingress-node is mapped/matched onto an existing RSVP generic
aggregation reservation state. aggregation reservation state.
o) If the timer t-recvFail expires for a given PCN-egress-node, the o) If the timer t-recvFail expires for a given PCN-egress-node, the
Decision Point (i.e., PCN-ingress-node) SHOULD NOT Decision Point (i.e., PCN-ingress-node) SHOULD NOT
allow the e2e microflow (i.e., PCN-flow) to be admitted to that allow the e2e microflow (i.e., PCN-flow) to be admitted to that
RSVP generic aggregated reservation (which is matched to one RSVP generic aggregated reservation (which is matched to one
ingress-egress-aggregate). The admission or rejection procedure ingress-egress-aggregate). The admission or rejection procedure
of a PCN-flow into the PCN-domain is defined in detail in: of a PCN-flow into the PCN-domain is defined in detail in:
[draft-ietf-pcn-cl-edge-behaviour-15] and [draft-ietf-pcn-sm- [RFC6661] and [RFC6662].
edge-behaviour-12].
If the Aggregator is not able to admit the e2e microflow it If the Aggregator is not able to admit the e2e microflow it
SHOULD then generate an e2e PathErr message using standard e2e SHOULD then generate an e2e PathErr message using standard e2e
RSVP procedures [RFC4495]. This e2e PathErr message is sent to RSVP procedures [RFC4495]. This e2e PathErr message is sent to
the originating sender of the e2e Path message. A new error code the originating sender of the e2e Path message. A new error code
"PCN-domain rejects e2e reservation" MUST be augmented to the "PCN-domain rejects e2e reservation" MUST be augmented to the
RSVP error codes to inform the sender that a PCN domains rejects RSVP error codes to inform the sender that a PCN domains rejects
the e2e reservation request. the e2e reservation request.
o) If the timer t-recvFail does NOT expire for a given PCN-egress- o) If the timer t-recvFail does NOT expire for a given PCN-egress-
node, then: node, then:
skipping to change at page 14, line 51 skipping to change at page 14, line 50
admitted by the Aggregator and an e2e PathErr message SHOULD admitted by the Aggregator and an e2e PathErr message SHOULD
be generated, using standard e2e RSVP procedures be generated, using standard e2e RSVP procedures
[RFC4495]. This e2e PathErr message is sent to the [RFC4495]. This e2e PathErr message is sent to the
originating sender of the e2e Path message, using standard originating sender of the e2e Path message, using standard
e2e RSVP procedures [RFC2205], [RFC4495]. A new error code e2e RSVP procedures [RFC2205], [RFC4495]. A new error code
"PCN-domain rejects e2e reservation" MUST be augmented to "PCN-domain rejects e2e reservation" MUST be augmented to
the RSVP error codes to inform the sender that a PCN domains the RSVP error codes to inform the sender that a PCN domains
rejects the e2e reservation request. rejects the e2e reservation request.
The way of how the PCN-admission-state is maintained is specified in The way of how the PCN-admission-state is maintained is specified in
[draft-ietf-pcn-cl-edge-behaviour-15] and [draft-ietf-pcn-sm-edge- [RFC6661] and [RFC6662]. The way of how the RSVP generic aggregated
behaviour-12]. The way of how the RSVP generic aggregated reservation reservation state is maintained is specified in [RFC4860].
state is maintained is specified in [RFC4860].
3.2. Handling Of E2E Path Message By Interior Routers 3.2. Handling Of E2E Path Message By Interior Routers
The e2e Path messages traverse zero or more PCN-interior-nodes. The e2e Path messages traverse zero or more PCN-interior-nodes.
The PCN-interior-nodes receive the e2e Path message on an interior The PCN-interior-nodes receive the e2e Path message on an interior
interface and forward it on another interior interface. The e2e Path interface and forward it on another interior interface. The e2e Path
messages are simply forwarded as normal IP datagrams. messages are simply forwarded as normal IP datagrams.
3.3. Receipt of E2E Path Message By PCN-egress-node (deaggregating 3.3. Receipt of E2E Path Message By PCN-egress-node (deaggregating
skipping to change at page 16, line 7 skipping to change at page 16, line 7
3.8. Initiation of New Aggregate Resv Message By Deaggregating Router 3.8. Initiation of New Aggregate Resv Message By Deaggregating Router
In this document it is considered that for the initiation of the new In this document it is considered that for the initiation of the new
RSVP aggregated Resv message by the PCN-ingress-node (Aggregator), RSVP aggregated Resv message by the PCN-ingress-node (Aggregator),
the same methods can be used as the ones described in [RFC4860] the same methods can be used as the ones described in [RFC4860]
augmented with the following rules: augmented with the following rules:
o) At the end of each t-meas measurement interval, or less o) At the end of each t-meas measurement interval, or less
frequently if "optional report suppression" is activated, see frequently if "optional report suppression" is activated, see
[draft-ietf-pcn-cl-edge-behaviour-15], and [RFC6661], and [RFC6662], the PCN-egress-node MUST include the
[draft-ietf-pcn-sm-edge-behaviour-12], the PCN-egress-node MUST new PCN object that will be sent to the associated Decision
include the new PCN object that will be sent to the associated Point (i.e., PCN-ingress-node). The PCN object is specified in
Decision Point (i.e., PCN-ingress-node). this document and is used for the report of the data measured by
The PCN object is specified in this document and is used for the the PCN-egress-node, for a particular ingress-egress-aggregate,
report of the data measured by the PCN-egress-node, for a see [RFC6661], and [RFC6662]. The address of the PCN-ingress-
particular ingress-egress-aggregate, see [draft-ietf-pcn-cl- node is the one specified in the same ingress-egress-aggregate.
edge-behaviour-15], and [draft-ietf-pcn-sm-edge-behaviour-12].
The address of the PCN-ingress-node is the one specified in the
same ingress-egress-aggregate.
3.9. Handling of Aggregate Resv Message by Interior Routers 3.9. Handling of Aggregate Resv Message by Interior Routers
The Aggregated Resv messages traverse zero or more PCN-interior- The Aggregated Resv messages traverse zero or more PCN-interior-
nodes. The PCN-interior-nodes receive the Aggregated Resv message on nodes. The PCN-interior-nodes receive the Aggregated Resv message on
an interior interface and forward it on another interior interface. an interior interface and forward it on another interior interface.
The Aggregated Resv messages are simply forwarded as normal IP The Aggregated Resv messages are simply forwarded as normal IP
datagrams. datagrams.
3.10. Handling of E2E Resv Message by Aggregating Router 3.10. Handling of E2E Resv Message by Aggregating Router
skipping to change at page 16, line 41 skipping to change at page 16, line 38
3.11. Handling of Aggregated Resv Message by Aggregating Router 3.11. Handling of Aggregated Resv Message by Aggregating Router
When the Aggregated Resv message arrives at the interior interface of When the Aggregated Resv message arrives at the interior interface of
the Aggregating router, i.e., PCN-ingress-node, then standard RSVP the Aggregating router, i.e., PCN-ingress-node, then standard RSVP
aggregation [RFC4860] procedures are used, augmented with the aggregation [RFC4860] procedures are used, augmented with the
following rules: following rules:
o) the Decision Point (i.e., the PCN-ingress-node) SHOULD use the o) the Decision Point (i.e., the PCN-ingress-node) SHOULD use the
information carried by the PCN objects as specified in information carried by the PCN objects as specified in
[draft-ietf-pcn-cl-edge-behaviour-15], [draft-ietf-pcn-sm-edge- [RFC6661], [RFC6662]. When the Aggregator (i.e.,
behaviour-12]. When the Aggregator (i.e., PCN-ingress-node) PCN-ingress-node) needs to terminate an amount of traffic
needs to terminate an amount of traffic associated to one associated to one ingress-egress-aggregate (see bullet 2 in
ingress-egress-aggregate (see bullet 2 in Section 3.3.2 of Section 3.3.2 of [RFC6661] and [RFC6662]), then several
[draft-ietf-pcn-cl-edge-behaviour-15] and [draft-ietf-pcn-sm- procedures of terminating e2e microflows can be deployed. The
edge-behaviour-12]), then several procedures of terminating default procedure of terminating e2e microflows (i.e.,
e2e microflows can be deployed. The default procedure of PCN-flows) is as follows, see e.g., [RFC6661]. For the same
terminating e2e microflows (i.e., PCN-flows) is as follows, see
e.g., [draft-ietf-pcn-cl-edge-behaviour-15]. For the same
ingress-egress-aggregate, select a number of e2e microflows ingress-egress-aggregate, select a number of e2e microflows
to be terminated in order to decrease the total incoming amount to be terminated in order to decrease the total incoming amount
of bandwidth associated with one ingress-egress-aggregate by the of bandwidth associated with one ingress-egress-aggregate by the
amount of traffic to be terminated, see above. amount of traffic to be terminated, see above.
In this situation the same mechanisms for terminating an e2e In this situation the same mechanisms for terminating an e2e
microflow can be followed as specified in [RFC2205]. microflow can be followed as specified in [RFC2205].
However, based on a local policy, the Aggregator could use However, based on a local policy, the Aggregator could use
other procedures of terminating microflows. other procedures of terminating microflows.
For example, for the same ingress-egress-aggregate, select a For example, for the same ingress-egress-aggregate, select a
skipping to change at page 18, line 5 skipping to change at page 18, line 5
(refresh) aggregated RSVP message to the PCN-ingress-node (i.e. (refresh) aggregated RSVP message to the PCN-ingress-node (i.e.
aggregator). aggregator).
o) the DSCP value included in the SESSION object, SHOULD be set equal o) the DSCP value included in the SESSION object, SHOULD be set equal
to a PCN-compatible Diffserv codepoint. to a PCN-compatible Diffserv codepoint.
o) An aggregated Resv message MUST carry one or more C-type PCN o) An aggregated Resv message MUST carry one or more C-type PCN
objects, see Section 4.1, to report the data measured by an objects, see Section 4.1, to report the data measured by an
PCN-egress-node (i.e., Deaggregator). PCN-egress-node (i.e., Deaggregator).
o) As described in [draft-ietf-pcn-cl-edge-behaviour-15], o) As described in [RFC6661], [RFC6663], PCN reports
[draft-ietf-pcn-signaling-requirements-08], PCN reports
from the PCN-egress-node (Deaggregator) to the decision point may from the PCN-egress-node (Deaggregator) to the decision point may
contain flow identifiers for individual flows within an contain flow identifiers for individual flows within an
ingress-egress-aggregate that have recently experienced ingress-egress-aggregate that have recently experienced
excess-marking. Hence, the PCN report messages used by the PCN CL excess-marking. Hence, the PCN report messages used by the PCN CL
edge behavior MUST be capable of carrying sequences of octet edge behavior MUST be capable of carrying sequences of octet
strings constituting such identifiers. When the PCN CL edge strings constituting such identifiers. When the PCN CL edge
behavior is used, the individual flow identifiers need to be behavior is used, the individual flow identifiers need to be
included in specific PCN objects, see Section 4.1 included in specific PCN objects, see Section 4.1
(C-Type = RSVP-AGGREGATE-IPv4-PCN-CL-FLIDs, (C-Type = RSVP-AGGREGATE-IPv4-PCN-CL-FLIDs,
= RSVP-AGGREGATE-IPv6-PCN-CL-FLIDs) = RSVP-AGGREGATE-IPv6-PCN-CL-FLIDs)
skipping to change at page 20, line 34 skipping to change at page 20, line 34
| | | |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| rate of not marked PCN-traffic (NM-rate) | | rate of not marked PCN-traffic (NM-rate) |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| rate of threshold-marked PCN-traffic (ThM-rate) | | rate of threshold-marked PCN-traffic (ThM-rate) |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| rate of excess-traffic-marked PCN-traffic (ETM-rate) | | rate of excess-traffic-marked PCN-traffic (ETM-rate) |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
The fields carried by the PCN object are specified in The fields carried by the PCN object are specified in
[draft-ietf-pcn-signaling-requirements-08.txt], [draft-ietf-pcn-cl- [RFC6663], [RFC6661] and [RFC6662]:
edge-behaviour-15] and [draft-ietf-pcn-sm-edge-behaviour-12]:
o the IPv4 or IPv6 address of the PCN-ingress-node and the IPv4 o the IPv4 or IPv6 address of the PCN-ingress-node and the IPv4
or IPv6 address of the PCN-egress-node; together they specify the or IPv6 address of the PCN-egress-node; together they specify the
ingress-egress-aggregate to which the report refers; ingress-egress-aggregate to which the report refers;
o rate of not-marked PCN-traffic (NM-rate) in octets/second; its o rate of not-marked PCN-traffic (NM-rate) in octets/second; its
format is a 32-bit IEEE floating point number; format is a 32-bit IEEE floating point number;
o rate of PCN-marked traffic (PM-rate) in octets/second; its format o rate of PCN-marked traffic (PM-rate) in octets/second; its format
is a 32-bit IEEE floating point number; is a 32-bit IEEE floating point number;
skipping to change at page 23, line 37 skipping to change at page 23, line 37
We would like to thank the authors of [draft-lefaucheur-rsvp-ecn- We would like to thank the authors of [draft-lefaucheur-rsvp-ecn-
01.txt], since some ideas used in this document are based on the work 01.txt], since some ideas used in this document are based on the work
initiated in [draft-lefaucheur-rsvp-ecn-01.txt]. Moreover, we would initiated in [draft-lefaucheur-rsvp-ecn-01.txt]. Moreover, we would
like to thank Tom Taylor, Philip Eardley, Michael Menth, like to thank Tom Taylor, Philip Eardley, Michael Menth,
Toby Moncaster, Francois Le Faucheur and James Polk for the provided Toby Moncaster, Francois Le Faucheur and James Polk for the provided
comments. comments.
8. Normative References 8. Normative References
[draft-ietf-pcn-cl-edge-behaviour-15] T. Taylor, A, Charny, F. Huang, [RFC6661] T. Taylor, A, Charny, F. Huang,
G. Karagiannis, M. Menth, "PCN Boundary Node Behaviour for the G. Karagiannis, M. Menth, "PCN Boundary Node Behaviour for the
Controlled Load (CL) Mode of Operation (Work in progress)", May Controlled Load (CL) Mode of Operation", July
2012. 2012.
[draft-ietf-pcn-sm-edge-behaviour-12] A. Charny, J. Zhang, [RFC6662] A. Charny, J. Zhang,
G. Karagiannis, M. Menth, T. Taylor, "PCN Boundary Node Behaviour G. Karagiannis, M. Menth, T. Taylor, "PCN Boundary Node Behaviour
for the Single Marking (SM) Mode of Operation (Work in progress)", for the Single Marking (SM) Mode of Operation",
April 2012. July 2012.
[draft-ietf-pcn-signaling-requirements-08] G. Karagiannis, T. Taylor, [RFC6663] G. Karagiannis, T. Taylor,
K. Chan, M. Menth, P. Eardley, " Requirements for Signaling of (Pre-) K. Chan, M. Menth, P. Eardley, " Requirements for Signaling of (Pre-)
Congestion Information in a DiffServ Domain(Work in progress)", Congestion Information in a DiffServ Domain",
February 2012. July 2012.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2205] Braden, R., ed., et al., "Resource ReSerVation Protocol [RFC2205] Braden, R., ed., et al., "Resource ReSerVation Protocol
(RSVP)- Functional Specification", RFC 2205, September 1997. (RSVP)- Functional Specification", RFC 2205, September 1997.
[RFC3140] Black, D., Brim, S., Carpenter, B., and F. Le [RFC3140] Black, D., Brim, S., Carpenter, B., and F. Le
Faucheur, "Per Hop Behavior Identification Codes", Faucheur, "Per Hop Behavior Identification Codes",
RFC 3140, June 2001. RFC 3140, June 2001.
skipping to change at page 24, line 24 skipping to change at page 24, line 24
Protocol (RSVP) Extension for the Reduction of Protocol (RSVP) Extension for the Reduction of
Bandwidth of a Reservation Flow", RFC 4495, May 2006. Bandwidth of a Reservation Flow", RFC 4495, May 2006.
[RFC4860] F. Le Faucheur, B. Davie, P. Bose, C. Christou, M. [RFC4860] F. Le Faucheur, B. Davie, P. Bose, C. Christou, M.
Davenport, "Generic Aggregate Resource ReSerVation Protocol (RSVP) Davenport, "Generic Aggregate Resource ReSerVation Protocol (RSVP)
Reservations", RFC4860, May 2007. Reservations", RFC4860, May 2007.
[RFC5670] Eardley, P., "Metering and Marking Behaviour of PCN-Nodes", [RFC5670] Eardley, P., "Metering and Marking Behaviour of PCN-Nodes",
RFC 5670, November 2009. RFC 5670, November 2009.
[RFC5696] Moncaster, T., Briscoe, B., and M. Menth, "Baseline [RFC6660] Moncaster, T., Briscoe, B., and M. Menth, "Baseline
Encoding and Transport of Pre-Congestion Information", RFC 5696, Encoding and Transport of Pre-Congestion Information", RFC 6660,
November 2009. July 2012.
9. Informative References 9. Informative References
[draft-lefaucheur-rsvp-ecn-01.txt] Le Faucheur, F., Charny, A., [draft-lefaucheur-rsvp-ecn-01.txt] Le Faucheur, F., Charny, A.,
Briscoe, B., Eardley, P., Chan, K., and J. Babiarz, "RSVP Extensions Briscoe, B., Eardley, P., Chan, K., and J. Babiarz, "RSVP Extensions
for Admission Control over Diffserv using Pre-congestion for Admission Control over Diffserv using Pre-congestion
Notification (PCN) (Work in progress)", June 2006. Notification (PCN) (Work in progress)", June 2006.
[RFC1633] Braden, R., Clark, D., and S. Shenker, "Integrated [RFC1633] Braden, R., Clark, D., and S. Shenker, "Integrated
Services in the Internet Architecture: an Overview", RFC 1633, June Services in the Internet Architecture: an Overview", RFC 1633, June
 End of changes. 27 change blocks. 
80 lines changed or deleted 67 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/