Flow Classification in Information Centric Networking
draft-moiseenko-icnrg-flowclass-07
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Ilya Moiseenko , David Oran | ||
| Last updated | 2021-07-26 (latest revision 2021-01-13) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
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-moiseenko-icnrg-flowclass-07.txt
Abstract
For the ubiquitous and highly important Internet protocols (TCP, UDP, IP), flows are conventionally identified by the "5-tuple" of source and destination IP addresses, source and destination port, and protocol type in an IP packet. Information Centric Networking (ICN) is a new paradigm where network communications are accomplished by requesting named content, instead of sending packets to destination addresses. This document describes mechanisms allowing ICN forwarders, consumers, producers and other ICN nodes to encode, decode, and process equivalence class identifiers (flows) at any desired granularity of a routable name prefix and beyond the routable name prefix. This document is a product of the IRTF Information- Centric Networking Research Group (ICNRG).
Authors
Ilya Moiseenko
(imoiseenko@apple.com)
David Oran
(daveoran@orandom.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)