draft-ietf-tsvwg-sctp-prpolicies-03.txt   draft-ietf-tsvwg-sctp-prpolicies-04.txt 
Network Working Group M. Tuexen Network Working Group M. Tuexen
Internet-Draft Muenster Univ. of Appl. Sciences Internet-Draft Muenster Univ. of Appl. Sciences
Intended status: Standards Track R. Seggelmann Intended status: Standards Track R. Seggelmann
Expires: November 30, 2014 T-Systems International GmbH Expires: April 1, 2015 T-Systems International GmbH
R. Stewart R. Stewart
Adara Networks Netflix, Inc.
S. Loreto S. Loreto
Ericsson Ericsson
May 29, 2014 September 28, 2014
Additional Policies for the Partial Reliability Extension of the Stream Additional Policies for the Partial Reliability Extension of the Stream
Control Transmission Protocol Control Transmission Protocol
draft-ietf-tsvwg-sctp-prpolicies-03.txt draft-ietf-tsvwg-sctp-prpolicies-04.txt
Abstract Abstract
This document defines two additional policies for the Partial This document defines two additional policies for the Partial
Reliability Extension of the Stream Control Transmission Protocol Reliability Extension of the Stream Control Transmission Protocol
(PR-SCTP) allowing to limit the number of retransmissions or to (PR-SCTP) allowing to limit the number of retransmissions or to
prioritize user messages for more efficient send buffer usage. prioritize user messages for more efficient send buffer usage.
Status of This Memo Status of This Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 November 30, 2014. This Internet-Draft will expire on April 1, 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 2, line 20 skipping to change at page 2, line 20
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Additional PR-SCTP Policies . . . . . . . . . . . . . . . . . 3 3. Additional PR-SCTP Policies . . . . . . . . . . . . . . . . . 3
3.1. Limited Retransmissions Policy . . . . . . . . . . . . . 3 3.1. Limited Retransmissions Policy . . . . . . . . . . . . . 3
3.2. Priority Policy . . . . . . . . . . . . . . . . . . . . . 3 3.2. Priority Policy . . . . . . . . . . . . . . . . . . . . . 3
4. Socket API Considerations . . . . . . . . . . . . . . . . . . 4 4. Socket API Considerations . . . . . . . . . . . . . . . . . . 4
4.1. Data Types . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Data Types . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Support for Added PR-SCTP Policies . . . . . . . . . . . 4 4.2. Support for Added PR-SCTP Policies . . . . . . . . . . . 4
4.3. Socket Option for Getting the PR-SCTP Status 4.3. Socket Option for Getting the Stream Specific PR-SCTP
(SCTP_PR_STATUS) . . . . . . . . . . . . . . . . . . . . 5 Status (SCTP_PR_STREAM_STATUS) . . . . . 5
4.4. Socket Option for Getting and Setting the PR-SCTP Support 4.4. Socket Option for Getting the Association Specific PR-
(SCTP_PR_SUPPORTED) . . . . . . . . . . . . . . . . . . . 6 SCTP Status (SCTP_PR_ASSOC_STATUS) . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4.5. Socket Option for Getting and Setting the PR-SCTP Support
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 (SCTP_PR_SUPPORTED) . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 7 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
The SCTP Partial Reliability Extension (PR-SCTP) defined in [RFC3758] The SCTP Partial Reliability Extension (PR-SCTP) defined in [RFC3758]
provides a generic method for senders to abandon user messages. The provides a generic method for senders to abandon user messages. The
decision to abandon a user message is sender side only and the exact decision to abandon a user message is sender side only and the exact
condition is called a PR-SCTP policy. [RFC3758] also defines one condition is called a PR-SCTP policy. [RFC3758] also defines one
particular PR-SCTP policy, called Timed Reliability. This allows the particular PR-SCTP policy, called Timed Reliability. This allows the
sender to specify a timeout for a user message after which the SCTP sender to specify a timeout for a user message after which the SCTP
stack abandons the user message. stack abandons the user message.
skipping to change at page 5, line 14 skipping to change at page 5, line 14
+-------------------+---------------------------+---------------+ +-------------------+---------------------------+---------------+
| pr_policy | pr_value | Specification | | pr_policy | pr_value | Specification |
+-------------------+---------------------------+---------------+ +-------------------+---------------------------+---------------+
| SCTP_PR_SCTP_NONE | Ignored | [RFC6458] | | SCTP_PR_SCTP_NONE | Ignored | [RFC6458] |
| SCTP_PR_SCTP_TTL | Lifetime in ms | [RFC6458] | | SCTP_PR_SCTP_TTL | Lifetime in ms | [RFC6458] |
| SCTP_PR_SCTP_RTX | Number of retransmissions | Section 3.1 | | SCTP_PR_SCTP_RTX | Number of retransmissions | Section 3.1 |
| SCTP_PR_SCTP_PRIO | Priority | Section 3.2 | | SCTP_PR_SCTP_PRIO | Priority | Section 3.2 |
+-------------------+---------------------------+---------------+ +-------------------+---------------------------+---------------+
4.3. Socket Option for Getting the PR-SCTP Status (SCTP_PR_STATUS) 4.3. Socket Option for Getting the Stream Specific PR-SCTP Status
(SCTP_PR_STREAM_STATUS)
This socket option uses IPPROTO_SCTP as its level and SCTP_PR_STATUS This socket option uses IPPROTO_SCTP as its level and
as its name. It can only be used with getsockopt(), but not with SCTP_PR_STREAM_STATUS as its name. It can only be used with
setsockopt(). The socket option value uses the following structure: getsockopt(), but not with setsockopt(). The socket option value
uses the following structure:
struct sctp_prstatus { struct sctp_prstatus {
sctp_assoc_t sprstat_assoc_id; sctp_assoc_t sprstat_assoc_id;
uint16_t sprstat_sid;
uint16_t sprstat_policy;
uint64_t sprstat_abandoned_unsent; uint64_t sprstat_abandoned_unsent;
uint64_t sprstat_abandoned_sent; uint64_t sprstat_abandoned_sent;
}; };
sprstat_assoc_id: This parameter is ignored for one-to-one style sprstat_assoc_id: This parameter is ignored for one-to-one style
sockets. For one-to-many style sockets this parameter indicates sockets. For one-to-many style sockets this parameter indicates
for which association the user wants the information. It is an for which association the user wants the information. It is an
error to use SCTP_{CURRENT|ALL|FUTURE}_ASSOC in sprstat_assoc_id. error to use SCTP_{CURRENT|ALL|FUTURE}_ASSOC in sprstat_assoc_id.
sprstat_sid: This parameter indicates for which outgoing SCTP stream
the user wants the information.
sprstat_policy: This parameter indicates for which PR-SCTP policy
the user wants the information. It is an error to use
SCTP_PR_SCTP_NONE in sprstat_policy. If SCTP_PR_SCTP_ALL is used,
the counters provided are aggregated over all supported policies.
sprstat_abandoned_unsent: The number of user messages which have sprstat_abandoned_unsent: The number of user messages which have
been abandoned, before any part of the user message could be sent. been abandoned using the policy specified in sprstat_policy on the
stream specified in sprstat_sid for the association specified by
sprstat_assoc_id, before any part of the user message could be
sent.
sprstat_abandoned_sent: The number of user messages which have been sprstat_abandoned_sent: The number of user messages which have been
abandoned, after a part of the user message has been sent. abandoned using the policy specified in sprstat_policy on the
stream specified in sprstat_sid for the association specified by
sprstat_assoc_id, after a part of the user message has been sent.
There are separate counters for unsent and sent user messages because There are separate counters for unsent and sent user messages because
the SCTP_SEND_FAILED_EVENT supports a similar differentiation. the SCTP_SEND_FAILED_EVENT supports a similar differentiation.
Please note that an abandoned large user message requiring an SCTP Please note that an abandoned large user message requiring an SCTP
level fragmentation is reported in the sprstat_abandoned_sent counter level fragmentation is reported in the sprstat_abandoned_sent counter
as soon as at least one fragment of it has been sent. Therefore each as soon as at least one fragment of it has been sent. Therefore each
abandoned user message is either counted in sprstat_abandoned_unsent abandoned user message is either counted in sprstat_abandoned_unsent
or sprstat_abandoned_sent. or sprstat_abandoned_sent.
If more detailed information about abandoned user messages is If more detailed information about abandoned user messages is
required, the subscription to the SCTP_SEND_FAILED_EVENT is required, the subscription to the SCTP_SEND_FAILED_EVENT is
recommended. recommended. Please note that some implementations might not support
this option on purpose, since it increases the resources needed for
an outgoing SCTP stream. For the same reasons, some implementations
might only support using SCTP_PR_SCTP_ALL in sprstat_policy.
sctp_opt_info() needs to be extended to support SCTP_PR_STATUS. sctp_opt_info() needs to be extended to support
SCTP_PR_STREAM_STATUS.
4.4. Socket Option for Getting and Setting the PR-SCTP Support 4.4. Socket Option for Getting the Association Specific PR-SCTP Status
(SCTP_PR_ASSOC_STATUS)
This socket option uses IPPROTO_SCTP as its level and
SCTP_PR_ASSOC_STATUS as its name. It can only be used with
getsockopt(), but not with setsockopt(). The socket option value
uses the same structure as described in Section 4.3:
struct sctp_prstatus {
sctp_assoc_t sprstat_assoc_id;
uint16_t sprstat_sid;
uint16_t sprstat_policy;
uint64_t sprstat_abandoned_unsent;
uint64_t sprstat_abandoned_sent;
};
sprstat_assoc_id: This parameter is ignored for one-to-one style
sockets. For one-to-many style sockets this parameter indicates
for which association the user wants the information. It is an
error to use SCTP_{CURRENT|ALL|FUTURE}_ASSOC in sprstat_assoc_id.
sprstat_sid: This parameter is ignored.
sprstat_policy: This parameter indicates for which PR-SCTP policy
the user wants the information. It is an error to use
SCTP_PR_SCTP_NONE in sprstat_policy. If SCTP_PR_SCTP_ALL is used,
the counters provided are aggregated over all supported policies.
sprstat_abandoned_unsent: The number of user messages which have
been abandoned using the policy specified in sprstat_policy for
the association specified by sprstat_assoc_id, before any part of
the user message could be sent.
sprstat_abandoned_sent: The number of user messages which have been
abandoned using the policy specified in sprstat_policy for the
association specified by sprstat_assoc_id, after a part of the
user message has been sent.
There are separate counters for unsent and sent user messages because
the SCTP_SEND_FAILED_EVENT supports a similar differentiation.
Please note that an abandoned large user message requiring an SCTP
level fragmentation is reported in the sprstat_abandoned_sent counter
as soon as at least one fragment of it has been sent. Therefore each
abandoned user message is either counted in sprstat_abandoned_unsent
or sprstat_abandoned_sent.
If more detailed information about abandoned user messages is
required, the usage of the option described in Section 4.3 or the
subscription to the SCTP_SEND_FAILED_EVENT is recommended.
sctp_opt_info() needs to be extended to support SCTP_PR_ASSOC_STATUS.
4.5. Socket Option for Getting and Setting the PR-SCTP Support
(SCTP_PR_SUPPORTED) (SCTP_PR_SUPPORTED)
This socket option allows the enabling or disabling of the This socket option allows the enabling or disabling of the
negotiation of PR-SCTP support for future associations. For existing negotiation of PR-SCTP support for future associations. For existing
associations it allows to query whether PR-SCTP support was associations it allows to query whether PR-SCTP support was
negotiated or not on particular associations. negotiated or not on a particular association.
Whether PR-SCTP is enabled or not per default is implementation Whether PR-SCTP is enabled or not per default is implementation
specific. specific.
This socket option uses IPPROTO_SCTP as its level and This socket option uses IPPROTO_SCTP as its level and
SCTP_PR_SUPPORTED as its name. It can be used with getsockopt() and SCTP_PR_SUPPORTED as its name. It can be used with getsockopt() and
setsockopt(). The socket option value uses the following structure setsockopt(). The socket option value uses the following structure
defined in [RFC6458]: defined in [RFC6458]:
struct sctp_assoc_value { struct sctp_assoc_value {
skipping to change at page 7, line 46 skipping to change at page 9, line 20
Yasevich, "Sockets API Extensions for the Stream Control Yasevich, "Sockets API Extensions for the Stream Control
Transmission Protocol (SCTP)", RFC 6458, December 2011. Transmission Protocol (SCTP)", RFC 6458, December 2011.
[RFC7011] Claise, B., Trammell, B., and P. Aitken, "Specification of [RFC7011] Claise, B., Trammell, B., and P. Aitken, "Specification of
the IP Flow Information Export (IPFIX) Protocol for the the IP Flow Information Export (IPFIX) Protocol for the
Exchange of Flow Information", STD 77, RFC 7011, September Exchange of Flow Information", STD 77, RFC 7011, September
2013. 2013.
[I-D.ietf-rtcweb-data-channel] [I-D.ietf-rtcweb-data-channel]
Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data Jesup, R., Loreto, S., and M. Tuexen, "WebRTC Data
Channels", draft-ietf-rtcweb-data-channel-09 (work in Channels", draft-ietf-rtcweb-data-channel-11 (work in
progress), May 2014. progress), July 2014.
[IEEE.1003-1G.1997] [IEEE.1003-1G.1997]
Institute of Electrical and Electronics Engineers, Institute of Electrical and Electronics Engineers,
"Protocol Independent Interfaces", IEEE Standard 1003.1G, "Protocol Independent Interfaces", IEEE Standard 1003.1G,
March 1997. March 1997.
Authors' Addresses Authors' Addresses
Michael Tuexen Michael Tuexen
Muenster University of Applied Sciences Muenster University of Applied Sciences
skipping to change at page 8, line 22 skipping to change at page 10, line 4
Email: tuexen@fh-muenster.de Email: tuexen@fh-muenster.de
Robin Seggelmann Robin Seggelmann
T-Systems International GmbH T-Systems International GmbH
Fasanenweg 5 Fasanenweg 5
70771 Leinfelden-Echterdingen 70771 Leinfelden-Echterdingen
DE DE
Email: robin.seggelmann@t-systems.com Email: robin.seggelmann@t-systems.com
Randall R. Stewart Randall R. Stewart
Adara Networks Netflix, Inc.
Chapin, SC 29036 Chapin, SC 29036
US US
Email: randall@lakerest.net Email: randall@lakerest.net
Salvatore Loreto Salvatore Loreto
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
Jorvas 02420 Jorvas 02420
FI FI
 End of changes. 19 change blocks. 
30 lines changed or deleted 104 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/