draft-ietf-tsvwg-rsvp-pcn-05.txt   draft-ietf-tsvwg-rsvp-pcn-06.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: Experimental Anurag Bhargava Intended status: Experimental Anurag Bhargava
Expires: January 14, 2014 Cisco Systems, Inc. Expires: January 29, 2014 Cisco Systems, Inc.
July 14, 2013 July 29, 2013
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-05 draft-ietf-tsvwg-rsvp-pcn-06
Abstract Abstract
This document specifies extensions to Generic Aggregated RSVP This document specifies extensions to 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 14, 2014. This Internet-Draft will expire on January 29, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 10, line 31 skipping to change at page 10, line 31
o) Extended vDstPort SHOULD be set to the IPv4 or o) Extended vDstPort SHOULD be set to the IPv4 or
IPv6 destination addresses, of the Aggregator IPv6 destination addresses, of the Aggregator
(PCN-ingress-node) (PCN-ingress-node)
Ingress-egress-aggregate (IEA): Ingress-egress-aggregate (IEA):
The collection of PCN-packets from all PCN-flows The collection of PCN-packets from all PCN-flows
that travel in one direction between a specific pair that travel in one direction between a specific pair
of PCN-boundary-nodes. An ingress-egress-aggregate of PCN-boundary-nodes. An ingress-egress-aggregate
is identified by the combination of (1) PCN-BA is identified by the combination of (1) PCN-BA
(i.e., combination of the DSCP and ECN fields),(2) (i.e., combination of the DSCP and ECN fields),(2)
IP addresses of the specific pair of PCN-boundary- IP addresses of the specific pair of
-nodes used by the ingress-egress-aggregate. In PCN-boundary-nodes used by the
this document one RSVP generic aggregated ingress-egress-aggregate. In this document one RSVP
reservation is mapped to only one ingress-egress- generic aggregated reservation is mapped to only
-aggregate, while one ingress-egress-aggregate is one ingress-egress-aggregate, while one
mapped to either one or to more than one RSVP ingress-egress-aggregate is mapped to either
generic aggregated reservations. one or to more than one RSVP generic aggregated
reservations.
PCN-admission-state: PCN-admission-state:
The state ("admit" or "block") derived by the The state ("admit" or "block") derived by the
Decision Point for a given ingress-egress-aggregate Decision Point for a given ingress-egress-aggregate
based on statistics about PCN-packet marking. The based on statistics about PCN-packet marking. The
Decision Point decides to admit or block new flows Decision Point decides to admit or block new flows
offered to the aggregate based on the current value offered to the aggregate based on the current value
of the PCN-admission-state. of the PCN-admission-state.
Congestion level estimate (CLE): Congestion level estimate (CLE):
skipping to change at page 15, line 33 skipping to change at page 15, line 33
the ones described in Section 4 of [RFC4860] and [RFC5559]. the ones described in Section 4 of [RFC4860] and [RFC5559].
3. Elements of Procedure 3. Elements of Procedure
This section describes the procedures used to implement the This section describes the procedures used to implement the
aggregated RSVP procedure over PCN. It is considered that the aggregated RSVP procedure over PCN. It is considered that the
procedures for aggregation of e2e reservations over generic aggregate procedures for aggregation of e2e reservations over generic aggregate
RSVP reservations are same as the procedures specified in Section RSVP reservations are same as the procedures specified in Section
4 of [RFC4860]. Please refer to [RFC4860] for all the below error 4 of [RFC4860]. Please refer to [RFC4860] for all the below error
cases: cases:
o) Incomplete message *) Incomplete message
o) Unexpected objects *) Unexpected objects
3.1. Receipt of E2E Path Message By PCN-ingress-node (aggregating 3.1. Receipt of E2E Path Message By PCN-ingress-node (aggregating
router) router)
When the e2e RSVP message arrives at the exterior interface of the When the e2e RSVP message arrives at the exterior interface of the
Aggregator, i.e., PCN-ingress-node, then standard RSVP generic Aggregator, i.e., PCN-ingress-node, then standard RSVP generic
aggregation [RFC4860] procedures are used, augmented with the aggregation [RFC4860] procedures are used, augmented with the
following rules: following rules:
o) The e2e RSVP reservation session associated with an e2e Path o) The e2e RSVP reservation session associated with an e2e Path
skipping to change at page 16, line 13 skipping to change at page 16, line 13
destination. destination.
o) If for the same ingress-egress-aggregate and the same RSVP o) If for the same ingress-egress-aggregate and the same RSVP
generic aggregated reservation (1) the PCN-admission- generic aggregated reservation (1) the PCN-admission-
state and/or (2) the state for the RSVP generic aggregated state and/or (2) the state for the RSVP generic aggregated
reservation are/is "block", the flow SHOULD NOT be reservation are/is "block", the flow SHOULD NOT be
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]. This e2e PathErr
"PCN-domain rejects e2e reservation" MUST be augmented to message is sent to the originating sender of the e2e Path
the RSVP error codes to inform the sender that a PCN domains message. The e2e RSVP error code "01: Admission Control
rejects the e2e reservation request. failure" and the "Sub-code = 2: Requested bandwidth
unavailable " specified in Appendix B of [RFC2205] SHOULD be
used for this purpose.
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), see [RFC6661], [RFC6662]. The ingress-egress-aggregate), see [RFC6661], [RFC6662]. The
admission or rejection procedure of a PCN-flow into the PCN- admission or rejection procedure of a PCN-flow into the PCN-
domain is defined in detail in: [RFC6661] and [RFC6662]. domain is defined in detail in: [RFC6661] and [RFC6662].
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
skipping to change at page 17, line 53 skipping to change at page 17, line 53
interface and forward it on another interior interface. It is interface and forward it on another interior interface. It is
considered that by configuration the PCN-interior-nodes are not able considered that by configuration the PCN-interior-nodes are not able
to distinguish neither e2e RSVP sessions and their associated to distinguish neither e2e RSVP sessions and their associated
messages [RFC2205]. Therefore, the e2e Resv messages are simply messages [RFC2205]. Therefore, the e2e Resv messages are simply
forwarded as normal IP datagrams. forwarded as normal IP datagrams.
3.8. Initiation of New Aggregate Resv Message By Deaggregating Router 3.8. Initiation of New Aggregate Resv Message By Deaggregating Router
To comply with this specification it is considered that for the To comply with this specification it is considered that for the
initiation of the new RSVP aggregated Resv message by the PCN- initiation of the new RSVP aggregated Resv message by the PCN-
ingress-node (Aggregator), the same methods can be used as the ones egress-node (Deaggregator), the same methods can be used as the ones
described in Section 4 of [RFC4860] augmented with the following described in Section 4 of [RFC4860] augmented with the following
rules: 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
[RFC6661], and [RFC6662], the PCN-egress-node MUST include the [RFC6661], and [RFC6662], the PCN-egress-node MUST include the
new PCN object that will be sent to the associated Decision new PCN object that will be sent to the associated Decision
Point (i.e., PCN-ingress-node). The PCN-egress-node reports the Point (i.e., PCN-ingress-node). The PCN-egress-node reports the
data it measures for a particular ingress-egress-aggregate in a data it measures for a particular ingress-egress-aggregate in a
PCN object, as specified in Section 4 of this document (see PCN object, as specified in Section 4 of this document (see
skipping to change at page 25, line 23 skipping to change at page 25, line 23
5. Security Considerations 5. Security Considerations
The same security considerations specified in [RFC2205], [RFC4230], The same security considerations specified in [RFC2205], [RFC4230],
[RFC4860], [RFC5559] and [RFC6411]. [RFC4860], [RFC5559] and [RFC6411].
6. IANA Considerations 6. IANA Considerations
This document makes the following requests to the IANA: This document makes the following requests to the IANA:
o allocate a new Object Class (PCN Object), see Section 4.1. o allocate a new Object Class (PCN Object), see Section 4.1.
o allocate a "PCN-domain rejects e2e reservation" Error Code that
may appear only in e2e PathErr messages, see Section 3.1.
7. Acknowledgments 7. Acknowledgments
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 Bob Briscoe, David Black, Ken Carlberg, Tom Taylor, like to thank Bob Briscoe, David Black, Ken Carlberg, Tom Taylor,
Philip Eardley, Michael Menth, Toby Moncaster, Francois Le Faucheur, Philip Eardley, Michael Menth, Toby Moncaster, Francois Le Faucheur,
James Polk and Lixia Zhang for the provided comments. James Polk and Lixia Zhang for the provided comments.
8. Normative References 8. Normative References
 End of changes. 8 change blocks. 
21 lines changed or deleted 21 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/