Additional Considerations for UDP Encapsulation of Stream Control Transmission Protocol (SCTP) Packets
draft-tuexen-tsvwg-sctp-udp-encaps-cons-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-07-03
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group M. Tuexen
Internet-Draft Muenster Univ. of Appl. Sciences
Updates: 6951 (if approved) R. Stewart
Intended status: Standards Track Netflix, Inc.
Expires: January 4, 2018 July 3, 2017
Additional Considerations for UDP Encapsulation of Stream Control
Transmission Protocol (SCTP) Packets
draft-tuexen-tsvwg-sctp-udp-encaps-cons-02.txt
Abstract
RFC 6951 specifies the UDP encapsulation of SCTP packets. The
described handling of received packets requires the check of the
verification tag. However, RFC 6951 misses a specification for the
handling of received packets for which this check is not possible.
This document updates RFC 6951 by specifying the handling of received
packets where the verification tag can not be checked.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 4, 2018.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Tuexen & Stewart Expires January 4, 2018 [Page 1]
Internet-Draft Additional Considerations for SCTP over UDP July 2017
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Handling of Out of the Blue Packets . . . . . . . . . . . . . 3
4. Handling of SCTP Packets Containing an INIT Chunk Matching an
Existing Association . . . . . . . . . . . . . . . . . . . . 3
5. Middlebox Considerations . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
9. Normative References . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction
[RFC6951] specifies the UDP encapsulation of SCTP packets. To be
able to adopt automatically to changes of the remote UDP
encapsulation port number, it is updated automatically when
processing received packets. This includes automatic enabling and
disabling of UDP encapsulation.
Section 5.4 of [RFC6951] describes the processing of received packets
and requires the check of the verification tag before updating the
remote UDP encapsulation port and the possible enabling or disabling
of UDP encapsulation.
[RFC6951] basically misses a description for the handling of received
packets where this verification tag check is not possible. This
includes packets for which no association can be found and packets
containing an INIT chunk, since the verification tag for these
packets must be 0.
2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Tuexen & Stewart Expires January 4, 2018 [Page 2]
Internet-Draft Additional Considerations for SCTP over UDP July 2017
3. Handling of Out of the Blue Packets
Show full document text