Transport Considerations for IP and UDP Proxying in MASQUE
draft-westerlund-masque-transport-issues-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Magnus Westerlund , Marcus Ihlar , Zaheduzzaman Sarker , Mirja Kühlewind | ||
| Last updated | 2021-01-11 (Latest revision 2020-07-10) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The HTTP Connect method uses back-to-back TCP connections to and from a proxy. Such a solution takes care of many transport aspects as well as IP Flow related concerns. With UDP and IP proxying on the other hand, there are several per-packet and per-flow aspects that need consideration to preserve the properties of end- to-end IP/UDP flows. The aim of this document is to highlight and provide solutions for these issues related to UDP and IP proxying.
Authors
Magnus Westerlund
Marcus Ihlar
Zaheduzzaman Sarker
Mirja Kühlewind
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)