12:5312:53, 5 August 2021diffhist+37
m
HTTP
If you're going to specify what layer the protocol is in, you need to specify the model you're using too.
12:0412:04, 5 August 2021diffhist−18
OSI model
Undid revision 1037190813 by
Johnuniq (
talk) The RFC, especially one line in the introduction, does control what layer the protocol is in - the function of the protocol does. HTTP does control and manage the connections between computers. it redirects, closes, opens with GETs - it is the first layer that transfers data. It is a session layer protocol.Tags: UndoReverted
15:3215:32, 4 August 2021diffhist−18
OSI model
https://datatracker.ietf.org/doc/html/rfc7230 "HTTP is a stateless request/response protocol that operates by exchanging messages (Section 3) across a reliable transport- or session-layer "connection" (Section 6). An HTTP "client" is a program that establishes a connection to a server for the purpose of sending one or more HTTP requests. An HTTP "server" is a program that accepts connections in order to service HTTP requests by sending HTTP responses."Tags: UndoReverted
14:5214:52, 4 August 2021diffhist−18
m
OSI model
The RFC "Overall Operational" states "The HTTP protocol is a request/response protocol." IT MUST CREATE AND MANAGE A SESSION with the server, therefore Session Layer. It transfers HTML! HTTP CAN NOT POSSIBLY BE IN APPLICATION because HTML would be WHERE? Level 8?Tags: Manual revertReverted
12:5412:54, 4 August 2021diffhist−5
m
HTTP
HTTP is *not* in the application layer, it's session layer 5. HTML is above HTTP. I cite THIS ARTICLE where it talks about creating a SESSION!Tag: Reverted
11:5711:57, 7 August 2017diffhist−622
OSI model
The protocols examples are not application layer. never have been. They have ports, therefore Session layer.
14:2414:24, 13 June 2016diffhist+545
OSI model
Guy Harris confuses "Protocol" as ONLY being a network dialog. An API calling standard in the Level 7 IS also a protocol.
13:4713:47, 27 April 2016diffhist+693
OSI model
“The OSI reference model” published in IEEE vol.71,issue 12, Page 430. Sec:C Par:1 "Management of OSI comprises those FUNCTIONS required..."
12:4512:45, 27 April 2016diffhist+693
OSI model
No, this is correct. I've been writing network software for over 20 years, this is the way it is. Level 5 is APIs. Period.
16:4116:41, 19 January 2016diffhist−6
OSI model
FTP, HTTP, SMTP, SSH and Telnet are all Session Layer protocols Managing communications between client and server. You can't have HTTP be in the application layer while HTML is in the Presentation Layer. Read the RFCs! These are managing the sessions!
12:5312:53, 5 August 2021diffhist+37
m
HTTP
If you're going to specify what layer the protocol is in, you need to specify the model you're using too.
12:0412:04, 5 August 2021diffhist−18
OSI model
Undid revision 1037190813 by
Johnuniq (
talk) The RFC, especially one line in the introduction, does control what layer the protocol is in - the function of the protocol does. HTTP does control and manage the connections between computers. it redirects, closes, opens with GETs - it is the first layer that transfers data. It is a session layer protocol.Tags: UndoReverted
15:3215:32, 4 August 2021diffhist−18
OSI model
https://datatracker.ietf.org/doc/html/rfc7230 "HTTP is a stateless request/response protocol that operates by exchanging messages (Section 3) across a reliable transport- or session-layer "connection" (Section 6). An HTTP "client" is a program that establishes a connection to a server for the purpose of sending one or more HTTP requests. An HTTP "server" is a program that accepts connections in order to service HTTP requests by sending HTTP responses."Tags: UndoReverted
14:5214:52, 4 August 2021diffhist−18
m
OSI model
The RFC "Overall Operational" states "The HTTP protocol is a request/response protocol." IT MUST CREATE AND MANAGE A SESSION with the server, therefore Session Layer. It transfers HTML! HTTP CAN NOT POSSIBLY BE IN APPLICATION because HTML would be WHERE? Level 8?Tags: Manual revertReverted
12:5412:54, 4 August 2021diffhist−5
m
HTTP
HTTP is *not* in the application layer, it's session layer 5. HTML is above HTTP. I cite THIS ARTICLE where it talks about creating a SESSION!Tag: Reverted
11:5711:57, 7 August 2017diffhist−622
OSI model
The protocols examples are not application layer. never have been. They have ports, therefore Session layer.
14:2414:24, 13 June 2016diffhist+545
OSI model
Guy Harris confuses "Protocol" as ONLY being a network dialog. An API calling standard in the Level 7 IS also a protocol.
13:4713:47, 27 April 2016diffhist+693
OSI model
“The OSI reference model” published in IEEE vol.71,issue 12, Page 430. Sec:C Par:1 "Management of OSI comprises those FUNCTIONS required..."
12:4512:45, 27 April 2016diffhist+693
OSI model
No, this is correct. I've been writing network software for over 20 years, this is the way it is. Level 5 is APIs. Period.
16:4116:41, 19 January 2016diffhist−6
OSI model
FTP, HTTP, SMTP, SSH and Telnet are all Session Layer protocols Managing communications between client and server. You can't have HTTP be in the application layer while HTML is in the Presentation Layer. Read the RFCs! These are managing the sessions!