summaryrefslogtreecommitdiff
path: root/doc/rvi_fragmentation.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/rvi_fragmentation.md')
-rw-r--r--doc/rvi_fragmentation.md22
1 files changed, 16 insertions, 6 deletions
diff --git a/doc/rvi_fragmentation.md b/doc/rvi_fragmentation.md
index 78362c9..0992005 100644
--- a/doc/rvi_fragmentation.md
+++ b/doc/rvi_fragmentation.md
@@ -1,13 +1,21 @@
+<style type="text/css" media="print">
+ div.pagebreak
+ {
+ page-break-before: always;
+ }
+</style>
# The RVI Core Fragmentation Protocol
## Abstract
-The Remote Vehicle Interaction (RVI) system is a framework for secure interaction between
-vehicles and other devices and/or cloud services. RVI is designed to be agnostic in regard
-to connectivity options and intermittent connectivity. One consequence of this is that
-large messages may have to be partially transmitted via one type of connection, and completed
-on another. The fragmentation protocol described below allows for varying Message Transfer
-Unit (MTU) and lets the remote client request fragments as needed.
+The Remote Vehicle Interaction (RVI) system is a framework for secure
+interaction between vehicles and other devices and/or cloud services.
+RVI is designed to be agnostic in regard to connectivity options and
+intermittent connectivity. One consequence of this is that large messages
+may have to be partially transmitted via one type of connection, and completed
+on another. The fragmentation protocol described below allows for varying
+Message Transfer Unit (MTU) and lets the remote client request fragments
+as needed.
## Status of This Memo
@@ -41,6 +49,8 @@ Term | Meaning
`Server` | Receiving side of the interaction
`MTU` | Message Transfer Unit
+<div class="pagebreak"></div>
+
## System Overview
The fragmentation support is intended to operate immediately on top of the transport