Edit - Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Rev

1

Brought me all the way back to 1996 and the OSI Model en.wikipedia.org/wiki/OSI_model
– Rudi
Commented Jul 17, 2012 at 15:06
There are more than 2 transport layer protocols: en.wikipedia.org/wiki/Transport_layer#Protocols
– Stuart Blackler
Commented Jul 19, 2012 at 11:53
@StuartBlackler: Interesting point, thanks. Are there any (other than TCP & UDP) that don't fall into what I called the "vanishingly small specialist use" category and which are used over IP? If I measured IP traffic at an Internet Exchange Point, what proportion of the transport layer protocols would be anything other than TCP or UDP?
– RedGrittyBrick
Commented Jul 19, 2012 at 15:23
Take DCCP for example, it's still a new protocol but I imagine over the next few years you will see more applications use the protocol. Reason I don't think it's mainstream yet is because I don't believe there is support for it in Windows. Think of it as UDP with congestion control. Can be very handy for a lot of applications such as Skype and gaming :) Have a look at it. To answer your question, it's probably a very small amount at the moment
– Stuart Blackler
Commented Jul 20, 2012 at 15:37
@Rudi err, you should realize that is not the OSI reference model, and if you do realize that, then don't mislead people into thinking that it is. It's the TCP/IP model / architecture... Sometimes the TCP/IP architecture is described with the terminology of OSI, the OSI reference model. But the 4 layers shown and with those names, is very much TCP/IP not OSI. No issue with red's post but your comment is misleading at best.
– barlop
Commented Aug 3, 2015 at 1:22

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »