A new IETF non-working group email list has been created. List address: [email protected] Archive: https://mailarchive.ietf.org/arch/browse/ptth/ To subscribe: https://mailman3.ietf.org/mailman3/lists/ptth.ietf.org/
Purpose: The HTTP protocol family provides a rich request-response facility between HTTP clients (which emit requests) and HTTP servers (which return responses). Each version of HTTP relies on a transport protocol to provide the connection – typically TCP, TLS, or QUIC. The transport also identifies a client (which initiates the connection) and a server (which accepts the connection). In every standard version of HTTP, the transport client is also the HTTP client. This is sensible in ordinary HTTP use cases, in which the client knows how to reach the desired server, but the server does not know how or when to reach all potential clients. However, there are some specialized service architectures in which the situation is reversed: - The server is only intended to be accessed directly by a small number of clients. - The server knows how to reach these approved clients. - The server is not widely accessible by arbitrary clients due to security or routing constraints. This arrangement most commonly occurs for servers that are subject to a strict transport firewall or have no fixed location. This list will discuss use cases and concrete proposals for doing Reverse HTTP. This list belongs to IETF area: WIT For additional information, please contact the list administrators. _______________________________________________ IETF-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected]
