Talk:Stream Control Transmission Protocol

message: What is a "Message" in this given context? --194.113.59.80 (talk) 09:47, 5 August 2008 (UTC)
thread_title: Definition of "Message"

message: "All bytes sent in a TCP connection must be delivered in that order, which requires that a byte transmitted first must safely arrive at the destination before a second byte can be processed even if the second byte manages to arrive first. If an arbitrary number of bytes are sent in one step and later some more bytes are sent, these bytes will be received in order, but the receiver can not distinguish which bytes were sent in which step. SCTP in contrast, conserves message boundaries by operating on whole messages instead of single bytes. That means if one message of several related bytes of information is sent in one step, exactly that message is received in one step."
:This paragraph is vague and confusing, and I do know something about network protocols. I think the first sentence is saying that TCP cannot gracefully handle byte reordering of its packet payloads. The second sentence seems to be more confusing explanation of this point. I don't understand the meaning of the third sentence at all ("operating on" whole messages vs. single bytes? How is it "operating"? What is a "message" in this context?)  In the fourth sentence, what does "related bytes" mean?  If the checksum on a TCP packet checks out, its payload is received in "one step" as well.  I'm guessing that the SCTP bytestream is further semantically divided into messages, but I can't tell for sure from what is written in this paragraph. - 74.112.174.192 15:16, 5 February 2007 (UTC)
thread_title: Please reword

message: Is the comparison table in Transport_layer#Transport_protocol_comparison_table really correct? Now SCTP seemes to be equivalent to TCP. Please add rows to the table that pinpoints the major differences. Mange01 07:54, 27 June 2007 (UTC)
replies: text: As things turned out, it was Mange01 who fixed this problem in July 2007. Nice work. CWC 08:43, 10 March 2008 (UTC)
thread_title:  Comparison table with TCP and UDP 

message: Stream Control Transmission Protocol is not a proper noun as far as I believe and from the guidelines in WP:MOS. 87.254.89.197 (talk) 01:51, 1 March 2009 (UTC)
replies: text: It is a proper noun.  It refers to a unique transport protocol.  Transport protocol is not a proper noun because it refers to a class of protocols and can be preceded by any or some.  Stream Control Transmission Protocol cannot be preceded by any or some.  If you are the editor walking through all of the computing and telcom pages removing the caps from all of the proper nouns such as this, please stop.  — Dgtsyb (talk) 16:54, 1 March 2009 (UTC)
thread_title:  Proper nouns 

message: DCCP appears exactly once in the article as a column heading in the transport control protocol. DCCP appears to accomplish some of the same things as SCTP. Some discussion of DCCP comparing and contrasting the two in the article would be helpful --Kvng (talk) 03:46, 16 May 2009 (UTC)
thread_title:  DCCP 

message: There are two identical criterias:
Reliable transport 	
Unreliable transport  —Preceding unsigned comment added by 212.154.22.58 (talk) 08:36, 18 May 2009 (UTC)
replies: text: No, they are not identical: and SCTP is the only one listed that can provide both (either). — Dgtsyb (talk) 13:20, 18 May 2009 (UTC)
thread_title:  Comparison between transport layers 

message: The term "transaction" is common in the realm of databases and possibly memory systems where a set of changes must be made "atomically"--that is, all or nothing--to maintain consistency. I do not believe this term is appropriate in networking. In networking a more essential distinction is that between "streams" and "messages". In this article I prefer the term "message-oriented" over "transaction-oriented".
IOLJeff (talk) 21:15, 3 July 2009 (UTC)
thread_title:  "message-oriented" versus "transaction-oriented" 

message: The Packet Structure section states "SCTP packets have a simpler basic structure than TCP or UDP packets." OK, TCP arguably, but UDP? UDP has 5 fields including the data payload. Even a single chunk SCTP packet has 8. I'm removing the reference to UDP, though if anybody thinks this is a goof feel free to reinstate it. Jonathan.  —Preceding unsigned comment added by 86.216.134.185 (talk) 14:34, 21 February 2010 (UTC)
replies: text: Good catch. (I'm embarrassed I didn't notice that.) Thanks, CWC 18:24, 21 February 2010 (UTC)
thread_title:  Simpler than UDP? 

message: You say as the first paragraph:
"In computer networking, the Stream Control Transmission Protocol (SCTP) is a Transport Layer protocol, serving in a similar role as the popular protocols Transmission Control Protocol (TCP) and User Datagram Protocol (UDP). It provides some of the same service features of both, ensuring reliable, in-sequence transport of messages with congestion control.
It seems that you're stating that UDP allows in-sequence transport because you say "serving in a similar role as ...TCP and UDP. It provides some of the same service features of both:....reliable, in-sequence transport".
UDP is not reliable nor guarantees in-sequence transport.—Preceding unsigned comment added by Dwilches (talk • contribs) 21:29, 27 April 2010
:Good point. AFAIK the only feature SCTP has in common with UDP is preserving message boundaries. I've changed the lede accordingly. Thanks, Dwilches. CWC 03:16, 28 April 2010 (UTC)
thread_title:  UDP doesnt guarantee reliability or in-sequence arrival 

message: The external links section was full of reference type items. This would be a good resource for someone who wants to improve the article or add citations. I don't think these comply with WP:EL and I don't think these are of direct use to most readers. --Kvng (talk) 15:26, 29 November 2010 (UTC)
replies: text: I don't see any problem with any of these links.  They are certainly not spam.  Also, the transport comparison was meant to highlight SCTP's differences from other transport protocols and I believe should be retained here.  I have reverted those changes.  Can we please discuss more. — Dgtsyb (talk) 02:23, 30 November 2010 (UTC)
replies: text: The primary purpose of the External links section is described in WP:ELYES. The external links section is long and, in my opinion has a WP:NOTLINK problem. But indeed none of the links appear to violate WP:ELNO. We do need to improve the EL section. Ideally many of the links would be repurposed as references. Apparently we have to do this incrementally not boldly. --Kvng (talk) 14:32, 30 November 2010 (UTC)
replies: text: The article is not a mere list of links.  Also, if it were to become a featured article, it would probably contain them all.  Yes, they could be used in citations where possible, but this would require additional copy that is not yet in the article.  One unfortunate reality of SCTP is that most of the textbooks that cover it simply regurgitate the RFCs, leaving web links as the only notable sources beyond the RFC itself. — Dgtsyb (talk) 02:27, 1 December 2010 (UTC)
thread_title:  References 

message: Hello fellow Wikipedians,
I have just modified one external link on Stream Control Transmission Protocol. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20131126184525/http://www.iem.uni-due.de/~dreibh/sctp/ to http://www.iem.uni-due.de/~dreibh/sctp/
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 23:50, 25 April 2017 (UTC)
thread_title:  External links modified 

message: The text states that ordering is optional, and that the receiver may choose to process ordered packets in an unordered fashion. The RFC states (https://tools.ietf.org/html/rfc4960#section-6.6) that ordered packets must be delivered to the upper layer in the correct order, which apparently contradicts this statement. Could somebody with better knowledge of SCTP verify this, and add a reference or remove the statement. RogierA7 (talk) 13:33, 9 December 2017 (UTC)
thread_title:  Processing ordered messages out-of-order ? 

message: The referenced (and unreadable due to paywall) IEEE source doesn't seem to be related to the statement that ssh implements SCTP; I have found no references that it would nor found any instance of the string "sctp" in openssh source. I would like to see a direct reference to ssh changelog or source please. I doubt its correctness, to put it nicely. --grin ✎ 18:44, 13 August 2020 (UTC)
thread_title:  ssh