draft-ietf-nsis-ntlp-sctp-02.txt   draft-ietf-nsis-ntlp-sctp-03.txt 
Network Working Group X. Fu Network Working Group X. Fu
Internet-Draft C. Dickmann Internet-Draft C. Dickmann
Expires: May 21, 2008 University of Goettingen Intended status: Standards Track University of Goettingen
J. Crowcroft Expires: August 17, 2008 J. Crowcroft
University of Cambridge University of Cambridge
November 18, 2007 February 14, 2008
General Internet Signaling Transport (GIST) over SCTP General Internet Signaling Transport (GIST) over SCTP
draft-ietf-nsis-ntlp-sctp-02.txt draft-ietf-nsis-ntlp-sctp-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 21, 2008. This Internet-Draft will expire on August 17, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
Abstract Abstract
The General Internet Signaling Transport (GIST) protocol currently The General Internet Signaling Transport (GIST) protocol currently
uses TCP or TLS over TCP for connection mode operation. This uses TCP or TLS over TCP for connection mode operation. This
document describes the usage of GIST over the Stream Control document describes the usage of GIST over the Stream Control
Transmission Protocol (SCTP). The use of SCTP can take advantage of Transmission Protocol (SCTP). The use of SCTP can take advantage of
features provided by SCTP, namely streaming-based transport, support features provided by SCTP, namely streaming-based transport, support
of multiple streams to avoid head of line blocking, and the support of multiple streams to avoid head of line blocking, and the support
of multi-homing to provide network level fault tolerance. of multi-homing to provide network level fault tolerance.
skipping to change at page 3, line 33 skipping to change at page 3, line 33
reliability, congestion control and fragmentation. Unlike TCP, SCTP reliability, congestion control and fragmentation. Unlike TCP, SCTP
provides a number of functions that are desirable for signaling provides a number of functions that are desirable for signaling
transport, such as multiple streams and multiple IP addresses for transport, such as multiple streams and multiple IP addresses for
path failure recovery. In addition, its Partial Reliability path failure recovery. In addition, its Partial Reliability
extension (PR-SCTP) [3] supports partial retransmission based on a extension (PR-SCTP) [3] supports partial retransmission based on a
programmable retransmission timer. programmable retransmission timer.
This document defines the use of SCTP as a transport protocol for This document defines the use of SCTP as a transport protocol for
GIST Messaging Associations and discusses the implications on GIST GIST Messaging Associations and discusses the implications on GIST
State Maintenance and API between GIST and NSLPs. Furturemore, this State Maintenance and API between GIST and NSLPs. Furturemore, this
document shows how GIST should be used to provide the additional document shows how GIST SHOULD be used to provide the additional
features offered by SCTP to deliver the GIST C-mode messages (which features offered by SCTP to deliver the GIST C-mode messages (which
can in turn carry NSIS Signaling Layer Protocol (NSLP) [6] messages can in turn carry NSIS Signaling Layer Protocol (NSLP) [6] messages
as payload). More specifically: as payload). More specifically:
o How to use the multiple streams feature of SCTP. o How to use the multiple streams feature of SCTP.
o How to use the PR-SCTP extention of SCTP. o How to use the PR-SCTP extention of SCTP.
o How to take advantage of the multi-homing support of SCTP. o How to take advantage of the multi-homing support of SCTP.
The method described in this document does not require any changes of The method described in this document does not require any changes of
GIST or SCTP. However, SCTP implementations MUST support the GIST or SCTP. However, SCTP implementations MUST support the
optional feature of fragmentation of SCTP user messages. optional feature of fragmentation of SCTP user messages.
2. Terminology and Abbreviations 2. Terminology and Abbreviations
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
"OPTIONAL", in this document are to be interpreted as described in document are to be interpreted as described in [4]. Other
BCP 14, RFC 2119 [4]. Other terminologies and abbreviations used in terminologies and abbreviations used in this document are taken from
this document are taken from related specifications (e.g., [1] and related specifications (e.g., [1] and [2]) as follows:
[2]) as follows:
o SCTP - Stream Control Transmission Protocol o SCTP - Stream Control Transmission Protocol
o PR-SCTP - SCTP Partial Reliability Extension o PR-SCTP - SCTP Partial Reliability Extension
o MRM - Message Routing Method o MRM - Message Routing Method
o MRI - Message Routing Information o MRI - Message Routing Information
o MRS - Message Routing State o MRS - Message Routing State
o MA - A GIST Messaging Association is a single connection between o MA - A GIST Messaging Association is a single connection between
two explicitly identified GIST adjacent peers on the data path. A two explicitly identified GIST adjacent peers on the data path. A
messaging association may use a specific transport protocol and messaging association may use a specific transport protocol and
known ports. If security protection is required, it may use a known ports. If security protection is required, it may use a
specific network layer security association, or use a transport specific network layer security association, or use a transport
skipping to change at page 7, line 4 skipping to change at page 7, line 4
error". When used with SCTP, this parameter is also used as the error". When used with SCTP, this parameter is also used as the
timeout for the "timed reliability" service of PR-SCTP. timeout for the "timed reliability" service of PR-SCTP.
3.4.2. NetworkNotification 3.4.2. NetworkNotification
The NetworkNotification primitive is passed from GIST to an NSLP. It The NetworkNotification primitive is passed from GIST to an NSLP. It
indicates that a network event of possible interest to the NSLP indicates that a network event of possible interest to the NSLP
occurred. occurred.
NetworkNotification ( MRI, Network-Notification-Type ) NetworkNotification ( MRI, Network-Notification-Type )
If SCTP detects a failure of the primary path, GIST should indicate If SCTP detects a failure of the primary path, GIST SHOULD indicate
this event to the NSLP by calling the NetworkNotification primitive this event to the NSLP by calling the NetworkNotification primitive
with Network-Notification-Type "Routing Status Change". This with Network-Notification-Type "Routing Status Change". This
notification should be done even if SCTP was able to remain an open notification should be done even if SCTP was able to remain an open
connection to the peer due to its multi-homing capabilities. connection to the peer due to its multi-homing capabilities.
4. Bit-Level Formats 4. Bit-Level Formats
4.1. MA-Protocol-Options 4.1. MA-Protocol-Options
This section provides the bit-level format for the MA-protocol- This section provides the bit-level format for the MA-protocol-
skipping to change at page 8, line 43 skipping to change at page 8, line 43
8. Acknowledgments 8. Acknowledgments
The authors would like to thank John Loughney, Robert Hancock, Andrew The authors would like to thank John Loughney, Robert Hancock, Andrew
McDonald, Fang-Chun Kuo and Jan Demter for their helpful suggestions. McDonald, Fang-Chun Kuo and Jan Demter for their helpful suggestions.
9. References 9. References
9.1. Normative References 9.1. Normative References
[1] Schulzrinne, H. and R. Hancock, "GIST: General Internet [1] Schulzrinne, H. and R. Hancock, "GIST: General Internet
Signalling Transport", draft-ietf-nsis-ntlp-14 (work in Signalling Transport", draft-ietf-nsis-ntlp-15 (work in
progress), July 2007. progress), February 2008.
[2] Stewart, R., "Stream Control Transmission Protocol", RFC 4960, [2] Stewart, R., "Stream Control Transmission Protocol", RFC 4960,
September 2007. September 2007.
[3] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. Conrad, [3] Stewart, R., Ramalho, M., Xie, Q., Tuexen, M., and P. Conrad,
"Stream Control Transmission Protocol (SCTP) Partial Reliability "Stream Control Transmission Protocol (SCTP) Partial Reliability
Extension", RFC 3758, May 2004. Extension", RFC 3758, May 2004.
[4] Bradner, S., "Key words for use in RFCs to Indicate Requirement [4] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 9, line 32 skipping to change at page 9, line 32
Security", RFC 4347, April 2006. Security", RFC 4347, April 2006.
[8] Tuexen, M. and E. Rescorla, "Datagram Transport Layer Security [8] Tuexen, M. and E. Rescorla, "Datagram Transport Layer Security
for Stream Control Transmission Protocol", for Stream Control Transmission Protocol",
draft-tuexen-dtls-for-sctp-02 (work in progress), November 2007. draft-tuexen-dtls-for-sctp-02 (work in progress), November 2007.
Authors' Addresses Authors' Addresses
Xiaoming Fu Xiaoming Fu
University of Goettingen University of Goettingen
Institute for Informatics Institute of Computer Science
Lotzestr. 16-18 Lotzestr. 16-18
Goettingen 37083 Goettingen 37083
Germany Germany
Email: fu@cs.uni-goettingen.de Email: fu@cs.uni-goettingen.de
Christian Dickmann Christian Dickmann
University of Goettingen University of Goettingen
Institute for Informatics Institute of Computer Science
Lotzestr. 16-18 Lotzestr. 16-18
Goettingen 37083 Goettingen 37083
Germany Germany
Email: mail@christian-dickmann.de Email: mail@christian-dickmann.de
Jon Crowcroft Jon Crowcroft
University of Cambridge University of Cambridge
Computer Laboratory Computer Laboratory
William Gates Building William Gates Building
15 JJ Thomson Avenue 15 JJ Thomson Avenue
Cambridge CB3 0FD Cambridge CB3 0FD
UK UK
Email: jon.crowcroft@cl.cam.ac.uk Email: jon.crowcroft@cl.cam.ac.uk
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 12 change blocks. 
18 lines changed or deleted 18 lines changed or added

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