draft-ietf-tsvwg-sctp-prpolicies-05.txt   draft-ietf-tsvwg-sctp-prpolicies-06.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: May 13, 2015 T-Systems International GmbH Expires: June 13, 2015 T-Systems International GmbH
R. Stewart R. Stewart
Netflix, Inc. Netflix, Inc.
S. Loreto S. Loreto
Ericsson Ericsson
November 9, 2014 December 10, 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-05.txt draft-ietf-tsvwg-sctp-prpolicies-06.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 May 13, 2015. This Internet-Draft will expire on June 13, 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 39 skipping to change at page 2, line 39
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 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] refers to them as
particular PR-SCTP policy, called Timed Reliability. This allows the 'PR-SCTP Services'). [RFC3758] also defines one particular PR-SCTP
sender to specify a timeout for a user message after which the SCTP policy, called Timed Reliability. This allows the sender to specify
stack abandons the user message. a timeout for a user message after which the SCTP stack abandons the
user message.
This document specifies the following two additional PR-SCTP This document specifies the following two additional PR-SCTP
policies: policies:
Limited Retransmission Policy: Allows to limit the number of Limited Retransmission Policy: Allows to limit the number of
retransmissions. retransmissions.
Priority Policy: Allows to discard lower priority messages if space Priority Policy: Allows to discard lower priority messages if space
for higher priority messages is needed in the send buffer. for higher priority messages is needed in the send buffer.
skipping to change at page 8, line 21 skipping to change at page 8, line 21
This document requires no actions from IANA. This document requires no actions from IANA.
6. Security Considerations 6. Security Considerations
This document does not add any additional security considerations in This document does not add any additional security considerations in
addition to the ones given in [RFC4960], [RFC3758], and [RFC6458]. addition to the ones given in [RFC4960], [RFC3758], and [RFC6458].
As indicated in the Security Section of [RFC3758], transport layer As indicated in the Security Section of [RFC3758], transport layer
security in the form of TLS over SCTP (see [RFC3436]) can't be used security in the form of TLS over SCTP (see [RFC3436]) can't be used
for PR-SCTP. However, DTLS over SCTP (see [RFC6083]) could be used for PR-SCTP. However, DTLS over SCTP (see [RFC6083]) could be used
instead. It should also be noted that using PR-SCTP for an SCTP instead. If DTLS over SCTP as specified in [RFC6083] is used, the
association doesn't allow that association to behave more security considerations of [RFC6083] do apply. It should also be
aggressively than an SCTP association not using PR-SCTP. noted that using PR-SCTP for an SCTP association doesn't allow that
association to behave more aggressively than an SCTP association not
using PR-SCTP.
7. Acknowledgments 7. Acknowledgments
The authors wish to thank Spencer Dawkins, Gorry Fairhurst, Karen The authors wish to thank Spencer Dawkins, Gorry Fairhurst, Karen
Egede Nielsen, Ka-Cheong Poon, Irene Ruengeler, Jamal Hadi Salim, and Egede Nielsen, Ka-Cheong Poon, Dan Romascanu, Irene Ruengeler, Jamal
Vlad Yasevich for their invaluable comments. Hadi Salim, Joseph Salowey, and Vlad Yasevich for their invaluable
comments.
8. References 8. References
8.1. Normative References 8.1. Normative References
[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.
[RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. [RFC3758] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P.
Conrad, "Stream Control Transmission Protocol (SCTP) Conrad, "Stream Control Transmission Protocol (SCTP)
 End of changes. 7 change blocks. 
13 lines changed or deleted 17 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/