Edit - Network Engineering Stack Exchange

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.

1

You can certainly label things as you see fit, but HTTP was developed without regard to the OSI model, and it doesn't conform to the specifications. The same is true about VPNs -- the OSI standards never anticipated them. So any resemblance is, as they say, completely coincidental.

Ron Trunk
– Ron Trunk

2017-02-19 15:25:48 +00:00
Commented Feb 19, 2017 at 15:25
@RonTrunk - IP wasn't designed to the OSI model, but it fits pretty neatly in layer 3. OSI has a model, and it has detailed specifications of lots of services. HTTP doesn't match any of the OSI service specifications, not even close. But I would assert that it does handle issues that are addressed in the OSI application and presentation model layers. Now, I don't know whether that assertion is very helpful, but it's valid.

Jeff Learman
– Jeff Learman

2020-12-18 03:03:07 +00:00
Commented Dec 18, 2020 at 3:03

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**
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 »