draft-ietf-nsis-ntlp-sctp-13.txt   draft-ietf-nsis-ntlp-sctp-14.txt 
Network Working Group X. Fu Network Working Group X. Fu
Internet-Draft C. Dickmann Internet-Draft C. Dickmann
Intended status: Experimental University of Goettingen Intended status: Experimental University of Goettingen
Expires: December 26, 2010 J. Crowcroft Expires: December 27, 2010 J. Crowcroft
University of Cambridge University of Cambridge
June 24, 2010 June 25, 2010
General Internet Signaling Transport (GIST) over Stream Control General Internet Signaling Transport (GIST) over Stream Control
Transmission Protocol (SCTP) and Datagram Transport Layer Security Transmission Protocol (SCTP) and Datagram Transport Layer Security
(DTLS) (DTLS)
draft-ietf-nsis-ntlp-sctp-13.txt draft-ietf-nsis-ntlp-sctp-14.txt
Abstract Abstract
The General Internet Signaling Transport (GIST) protocol currently The General Internet Signaling Transport (GIST) protocol currently
uses TCP or Transport Layer Security (TLS) over TCP for connection uses TCP or Transport Layer Security (TLS) over TCP for connection
mode operation. This document describes the usage of GIST over the mode operation. This document describes the usage of GIST over the
Stream Control Transmission Protocol (SCTP) and Datagram Transport Stream Control Transmission Protocol (SCTP) and Datagram Transport
Layer Security (DTLS). It discusses how the use of SCTP can take Layer Security (DTLS). It discusses how the use of SCTP can take
advantage of features provided by SCTP, as well as how to establish advantage of features provided by SCTP, as well as how to establish
GIST security over datagram transport protocols with DTLS. GIST security over datagram transport protocols with DTLS.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 December 26, 2010. This Internet-Draft will expire on December 27, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 21 skipping to change at page 10, line 21
phase. phase.
The usage of DTLS [2] for securing GIST over datagram transport The usage of DTLS [2] for securing GIST over datagram transport
protocols MUST be implemented and SHOULD be used. protocols MUST be implemented and SHOULD be used.
GIST message associations using DTLS may carry messages with transfer GIST message associations using DTLS may carry messages with transfer
attributes requesting confidentiality or integrity protection. The attributes requesting confidentiality or integrity protection. The
specific DTLS version will be negotiated within the DTLS layer specific DTLS version will be negotiated within the DTLS layer
itself, but implementations MUST NOT negotiate to protocol versions itself, but implementations MUST NOT negotiate to protocol versions
prior to DTLS v1.0 and MUST use the highest protocol version prior to DTLS v1.0 and MUST use the highest protocol version
supported by both peers. GIST nodes supporting DTLS MUST be able to supported by both peers. NULL authentication and integrity ciphers
negotiate the DTLS NULL and block ciphers and SHOULD be able to MUST NOT be negotiated for GIST nodes supporting DTLS. For
negotiate the new cipher suites. They MAY negotiate any mutually confidentiality ciphers, nodes can negotiate the NULL ciphersuites.
acceptable ciphersuite that provides authentication, integrity, and The same rules for negotiating TLS cipher suites as specified in
confidentiality. The same rules for negotiating TLS cipher suites as Section 5.7.3 of [1] apply.
specified in Section 5.7.3 of [1] apply.
DTLS renegotiation [7] may cause problems for applications such that DTLS renegotiation [7] may cause problems for applications such that
connection security parameters can change without the application connection security parameters can change without the application
knowing it. Hence, it is RECOMMENDED that renegotiation be disabled knowing it. Hence, it is RECOMMENDED that renegotiation be disabled
for GIST over DTLS. for GIST over DTLS.
No MA-protocol-options field is required for DTLS. The configuration No MA-protocol-options field is required for DTLS. The configuration
information for the transport protocol over which DTLS is running information for the transport protocol over which DTLS is running
(e.g. SCTP port number) is provided by the MA-protocol-options for (e.g. SCTP port number) is provided by the MA-protocol-options for
that protocol. that protocol.
 End of changes. 5 change blocks. 
10 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/