LOOPS Generic Information Set
draft-welzl-loops-gen-info-04
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Michael Welzl , Carsten Bormann | ||
| Last updated | 2021-01-14 (latest revision 2020-07-13) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-welzl-loops-gen-info-04.txt
Abstract
LOOPS (Local Optimizations on Path Segments) aims to provide local (not end-to-end but in-network) recovery of lost packets to achieve better data delivery in the presence of losses. [I-D.li-tsvwg-loops-problem-opportunities] provides an overview over the problems and optimization opportunities that LOOPS could address. The present document is a strawman for the set of information that would be interchanged in a LOOPS protocol, without already defining a specific data packet format. The generic information set needs to be mapped to a specific encapsulation protocol to actually run the LOOPS optimizations. A companion document contains a sketch of a binding to the tunnel encapsulation protocol Geneve [I-D.ietf-nvo3-geneve].
Authors
Michael Welzl
(michawe@ifi.uio.no)
Carsten Bormann
(cabo@tzi.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)