draft-ietf-tsvwg-rsvp-pcn-08.txt   draft-ietf-tsvwg-rsvp-pcn-09.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: August 14, 2014 Cisco Systems, Inc. Expires: February 11, 2015 Cisco Systems, Inc.
February 14, 2014 August 11, 2014
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-08 draft-ietf-tsvwg-rsvp-pcn-09
Abstract Abstract
This document specifies extensions to Generic Aggregated RSVP This document specifies extensions to Generic Aggregated RSVP
RFC 4860 for support of the PCN Controlled Load (CL) and Single RFC 4860 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 August 14, 2014. This Internet-Draft will expire on February 11, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 16, line 40 skipping to change at page 16, line 40
3.4. Initiation of new Aggregate Path Message by Aggregating Router 3.4. Initiation of new Aggregate Path Message by Aggregating Router
To comply with this specification, for the initiation of the new RSVP To comply with this specification, for the initiation of the new RSVP
generic aggregated Path message by the Aggregator (also PCN-ingress- generic aggregated Path message by the Aggregator (also PCN-ingress-
node in this document), the same methods MUST be used as the ones node in this document), the same methods MUST be used as the ones
described in [RFC4860]. described in [RFC4860].
3.5. Handling Of Aggregate Path Message By Interior Routers 3.5. Handling Of Aggregate Path Message By Interior Routers
The Aggregate Path messages traverse zero or more PCN-interior-nodes. The Aggregate 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 Aggregated Path message on an
interface and forward it on another interior interface. interior interface and forward it on another interior interface.
It is considered that, by configuration, the PCN-interior-nodes It is considered that, by configuration, the PCN-interior-nodes
ignore the E2E RSVP signaling messages [RFC2205]. Therefore, the ignore the Aggregated Path signaling messages. Therefore, the
Aggregated Path messages are simply forwarded as normal IP datagrams. Aggregated Path messages are simply forwarded as normal IP datagrams.
3.6. Handling Of Aggregate Path Message By Deaggregating Router 3.6. Handling Of Aggregate Path Message By Deaggregating Router
When receiving the Aggregated Path message, the Deaggregator (also When receiving the Aggregated Path message, the Deaggregator (also
PCN-egress-node and Decision Point in this document) performs the PCN-egress-node and Decision Point in this document) performs the
regular [RFC4860] procedures, augmented with the following rules: regular [RFC4860] procedures, augmented with the following rules:
o) When the received Aggregated Path message by the Deaggregator o) When the received Aggregated Path message by the Deaggregator
contains the RSVP-AGGREGATE-IPv4-PCN-response or contains the RSVP-AGGREGATE-IPv4-PCN-response or
skipping to change at page 21, line 6 skipping to change at page 21, line 6
o) RSVP-AGGREGATE-IPv4-PCN-response, o) RSVP-AGGREGATE-IPv4-PCN-response,
o) RSVP-AGGREGATE-IPv6-PCN-response. o) RSVP-AGGREGATE-IPv6-PCN-response.
4.1 PCN objects 4.1 PCN objects
This section describes four types of PCN objects that can be carried This section describes four types of PCN objects that can be carried
by the (refresh) Aggregate Path or the (refresh) Aggregate Resv by the (refresh) Aggregate Path or the (refresh) Aggregate Resv
messages specified in [RFC4860]. messages specified in [RFC4860].
These objects are: These objects are:
o RSVP-AGGREGATE-IPv4-PCN-request, o RSVP-AGGREGATE-IPv4-PCN-request,
o RSVP-AGGREGATE-IPv6-PCN-request, o RSVP-AGGREGATE-IPv6-PCN-request,
o RSVP-AGGREGATE-IPv4-PCN-response, o RSVP-AGGREGATE-IPv4-PCN-response,
o RSVP-AGGREGATE-IPv6-PCN-response. o RSVP-AGGREGATE-IPv6-PCN-response.
o) RSVP-AGGREGATE-IPv4-PCN-request: PCN request object, when o) RSVP-AGGREGATE-IPv4-PCN-request: PCN request object, when
IPv4 addresses are used: IPv4 addresses are used:
Class = (to be replaced by IANA) (PCN) Class = 248 (PCN)
C-Type = RSVP-AGGREGATE-IPv4-PCN-request (to be replaced by IANA) C-Type = 1 (RSVP-AGGREGATE-IPv4-PCN-request
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| IPv4 PCN-ingress-node Address (4 bytes) | | IPv4 PCN-ingress-node Address (4 bytes) |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| IPv4 PCN-egress-node Address (4 bytes) | | IPv4 PCN-egress-node Address (4 bytes) |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| IPv4 Decision Point Address (4 bytes) | | IPv4 Decision Point Address (4 bytes) |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
|R| Reserved | |R| Reserved |
+-------------+-------------+-------------+-------------| +-------------+-------------+-------------+-------------|
o) RSVP-AGGREGATE-IPv6-PCN-request: PCN object, when o) RSVP-AGGREGATE-IPv6-PCN-request: PCN object, when
IPv6 addresses are used: IPv6 addresses are used:
Class = (to be replaced by IANA) (PCN) Class = 248 (PCN)
C-Type = RSVP-AGGREGATE-IPv6-PCN-request (to be replaced by IANA) C-Type = 2 (RSVP-AGGREGATE-IPv6-PCN-request
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| | | |
+ + + +
| | | |
+ IPv6 PCN-ingress-node Address (16 bytes) + + IPv6 PCN-ingress-node Address (16 bytes) +
| | | |
+ + + +
| | | |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
skipping to change at page 22, line 7 skipping to change at page 22, line 7
+ Decision Point Address (16 bytes) + + Decision Point Address (16 bytes) +
| | | |
+ + + +
| | | |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
|R| Reserved | |R| Reserved |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
o) RSVP-AGGREGATE-IPv4-PCN-response: PCN object, IPv4 o) RSVP-AGGREGATE-IPv4-PCN-response: PCN object, IPv4
addresses are used: addresses are used:
Class = (to be replaced by IANA) (PCN) Class = 248 (PCN)
C-Type = RSVP-AGGREGATE-IPv4-PCN-response (To be replaced by IANA) C-Type = 3 (RSVP-AGGREGATE-IPv4-PCN-response)
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| IPv4 PCN-ingress-node Address (4 bytes) | | IPv4 PCN-ingress-node Address (4 bytes) |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| IPv4 PCN-egress-node Address (4 bytes) | | IPv4 PCN-egress-node Address (4 bytes) |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| IPv4 Decision Point Address (4 bytes) | | IPv4 Decision Point Address (4 bytes) |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| PCN-sent-rate | | PCN-sent-rate |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
o) RSVP-AGGREGATE-IPv6-PCN-response: PCN object, IPv6 o) RSVP-AGGREGATE-IPv6-PCN-response: PCN object, IPv6
addresses are used: addresses are used:
Class = (to be replaced by IANA) (PCN) Class = 248 (PCN)
C-Type = RSVP-AGGREGATE-IPv6-PCN-response (to be replaced by IANA) C-Type = 4 (RSVP-AGGREGATE-IPv6-PCN-response)
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| | | |
+ + + +
| | | |
+ IPv6 PCN-ingress-node Address (16 bytes) + + IPv6 PCN-ingress-node Address (16 bytes) +
| | | |
+ + + +
| | | |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
skipping to change at page 23, line 42 skipping to change at page 23, line 42
is receiving PCN-traffic that is destined for the given is receiving PCN-traffic that is destined for the given
ingress-egress-aggregate. ingress-egress-aggregate.
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. IANA has modified the RSVP parameters registry, 'Class Names,
IANA needs to modify the RSVP parameters registry, 'Class Names, Class Numbers, and Class Types' subregistry, to add a new
Class Numbers, and Class Types' subregistry, and add a new Class Number and assign 4 new C-Types under this new Class
Class Number as well as assign 4 new C-Types under this new Class
Number, as described below, see Section 4.1: Number, as described below, see Section 4.1:
Class Class
Number Class Name Reference Number Class Name Reference
------ ----------------------- --------- ------ ---------------------- ---------
(defined 248 PCN this document
by IANA) PCN this document
Class Types or C-Types: Class Types or C-Types:
(defined by IANA) RSVP-AGGREGATE-IPv4-PCN-request this document 1 RSVP-AGGREGATE-IPv4-PCN-request this document
(defined by IANA) RSVP-AGGREGATE-IPv6-PCN-request this document 2 RSVP-AGGREGATE-IPv6-PCN-request this document
(defined by IANA) RSVP-AGGREGATE-IPv4-PCN-response this document 3 RSVP-AGGREGATE-IPv4-PCN-response this document
(defined by IANA) RSVP-AGGREGATE-IPv6-PCN-response this document 4 RSVP-AGGREGATE-IPv6-PCN-response this document
When this draft is published as an RFC, IANA should update the
reference for the above 5 items to that published RFC (and the RFC
Editor should remove this sentence).
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, James Polk and Philip Eardley, Michael Menth, Toby Moncaster, James Polk, Scott
Lixia Zhang for the provided comments. In particular, we would like Bradner and Lixia Zhang for the provided comments. In particular, we
to thank Francois Le Faucheur for contributing in addition to would like to thank Francois Le Faucheur for contributing in addition
comments also a significant amount of text. to comments also to a significant amount of text.
8. Normative References 8. Normative References
[RFC6661] 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", July Controlled Load (CL) Mode of Operation", July
2012. 2012.
[RFC6662] 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
skipping to change at page 26, line 48 skipping to change at page 26, line 48
E2E Resv E2E Resv
<--------- <---------
(8) (8)
E2E Resv (SOI=GApcn) E2E Resv (SOI=GApcn)
<----------------------------- <-----------------------------
(9) (9)
E2E Resv E2E Resv
<----------- <-----------
(1) The Aggregator forwards E2E Path into the aggregation region (1) The Aggregator forwards E2E Path into the aggregation region
after modifying its IP protocol number to RSVP-E2E-IGNORE after modifying its IP protocol number to RSVP-E2E-IGNORE
(2) Let's assume no Aggregate Path exists. To be able to accurately (2) Let's assume no Aggregate Path exists. To be able to accurately
update the ADSPEC of the E2E Path, the Deaggregator needs the update the ADSPEC of the E2E Path, the Deaggregator needs the
ADSPEC of Aggregate Path. In this example, the Deaggregator ADSPEC of Aggregate Path. In this example, the Deaggregator
elects to instruct the Aggregator to set up an Aggregate Path elects to instruct the Aggregator to set up an Aggregate Path
state for the PCN PHB-ID. To do that, the Deaggregator state for the PCN PHB-ID. To do that, the Deaggregator
sends an E2E PathErr message with a New-Agg-Needed PathErr sends an E2E PathErr message with a New-Agg-Needed PathErr
code. code.
The PathErr message also contains a SESSION-OF-INTEREST The PathErr message also contains a SESSION-OF-INTEREST
 End of changes. 15 change blocks. 
32 lines changed or deleted 35 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/