< draft-oran-icnrg-flowbalance-06.txt   draft-oran-icnrg-flowbalance-07.txt >
ICNRG D. Oran ICNRG D. Oran
Internet-Draft Network Systems Research and Design Internet-Draft Network Systems Research and Design
Intended status: Experimental 25 October 2021 Intended status: Experimental 5 May 2022
Expires: 28 April 2022 Expires: 6 November 2022
Maintaining CCNx or NDN flow balance with highly variable data object Maintaining CCNx or NDN flow balance with highly variable data object
sizes sizes
draft-oran-icnrg-flowbalance-06 draft-oran-icnrg-flowbalance-07
Abstract Abstract
Deeply embedded in some ICN architectures, especially Named Data Deeply embedded in some ICN architectures, especially Named Data
Networking (NDN) and Content-Centric Networking (CCNx) is the notion Networking (NDN) and Content-Centric Networking (CCNx) is the notion
of flow balance. This captures the idea that there is a one-to-one of flow balance. This captures the idea that there is a one-to-one
correspondence between requests for data, carried in Interest correspondence between requests for data, carried in Interest
messages, and the responses with the requested data object, carried messages, and the responses with the requested data object, carried
in Data messages. This has a number of highly beneficial properties in Data messages. This has a number of highly beneficial properties
for flow and congestion control in networks, as well as some for flow and congestion control in networks, as well as some
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 28 April 2022. This Internet-Draft will expire on 6 November 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. Method to enhance congestion control with signaled size 3. Method to enhance congestion control with signaled size
information in Interest Messages . . . . . . . . . . . . 5 information in Interest Messages . . . . . . . . . . . . 4
3.1. How to predict the size of returning Data messages . . . 6 3.1. How to predict the size of returning Data messages . . . 5
3.2. Handling 'too big' cases . . . . . . . . . . . . . . . . 7 3.2. Handling 'too big' cases . . . . . . . . . . . . . . . . 6
3.3. Handling 'too small' cases . . . . . . . . . . . . . . . 8 3.3. Handling 'too small' cases . . . . . . . . . . . . . . . 7
3.4. Interactions with Interest Aggregation . . . . . . . . . 9 3.4. Interactions with Interest Aggregation . . . . . . . . . 8
3.5. Operation when some Interests lack the expected data size 3.5. Operation when some Interests lack the expected data size
option and some have it . . . . . . . . . . . . . . . . . 10 option and some have it . . . . . . . . . . . . . . . . . 10
4. Dealing with malicious actors . . . . . . . . . . . . . . . . 12 4. Dealing with malicious actors . . . . . . . . . . . . . . . . 11
5. Mapping to CCNx and NDN packet encodings . . . . . . . . . . 13 5. Mapping to CCNx and NDN packet encodings . . . . . . . . . . 12
5.1. Packet encoding for CCNx . . . . . . . . . . . . . . . . 13 5.1. Packet encoding for CCNx . . . . . . . . . . . . . . . . 12
5.2. Packet encoding for NDN . . . . . . . . . . . . . . . . . 13 5.2. Packet encoding for NDN . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . 14 9.1. Normative References . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . 14 9.2. Informative References . . . . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 16 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
Deeply embedded in some ICN architectures, especially Named Data Deeply embedded in some ICN architectures, especially Named Data
Networking ([NDN]) and Content-Centric Networking (CCNx Networking ([NDN]) and Content-Centric Networking (CCNx
[RFC8569],[RFC8609]) is the notion of _flow balance_. This captures [RFC8569],[RFC8609]) is the notion of _flow balance_. This captures
the idea that there is a one-to-one correspondence between requests the idea that there is a one-to-one correspondence between requests
for data, carried in Interest messages, and the responses with the for data, carried in Interest messages, and the responses with the
requested data object, carried in Data messages. This has a number requested data object, carried in Data messages. This has a number
of highly beneficial properties for flow and congestion control in of highly beneficial properties for flow and congestion control in
 End of changes. 8 change blocks. 
21 lines changed or deleted 21 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/