Flexible Session Protocol
draft-gao-flexible-session-protocol-05
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
高军安
|
|
Last updated |
|
2020-10-19
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group J. Gao
Internet-Draft Individual
Intended status: Experimental October 17, 2020
Expires: April 20, 2021
Flexible Session Protocol
draft-gao-flexible-session-protocol-05
Abstract
FSP is a connection-oriented transport layer protocol that provides
mobility and multihoming support by introducing the concept of 'upper
layer thread ID', which is associated with some shared secret that is
applied with some secure hash or authenticated encryption algorithm
to protect authenticity of the origin of the FSP packets. It is able
to provide following services to the upper layer application:
o Stream-oriented send-receive with native message boundary
o Ubiquitous authenticated encryption
o 0-RTT multiplication of connections
o On-the-wire compression
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 20, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
Gao Expires April 20, 2021 [Page 1]
Internet-Draft Flexible Session Protocol October 2020
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
1. Introduction
Flexible Session Protocol is a connection-oriented transport layer
provides mobility, multi-homing and multi-path support by introducing
the concept of 'upper layer thread ID' (ULTID), which was firstly
suggested in [Gao2002].
An integrity check code (ICC) field associated with the ULTID is
designed in the FSP header to protect authenticity and optionally
privacy of the FSP packet. An FSP packet is assumed to originate
from the same source if the ICC value associated with certain
destination ULTID passes validation, regardless of the source or
destination address of the packet in the underlying layer.
ICC is either calculated by [CRC64] which protects FSP against
unintended modification, or a cryptographic hash function, or
cryptographically calculated with some Authenticated Encryption with
Additional Data [R01] algorithm, each of which requires a shared
secret key.
In the former case a weak key meant to obfuscate the CRC64 checksum
is agreed by the FSP participants. In the latter two cases, the
shared secret key is assumed to be installed by the upper layer
application (ULA).
The ULTID is assigned roughly the same semantics as the Security
Parameter Index (SPI) in MOBIKE [RFC4555]. Either the weak key or
the shared secret key is indexed by the source or destination ULTID
in the local context of the sender or the receiver, respectively.
FSP facilitates secret key installation by introducing the concept of
transmit transaction. Mechanism of transmit transaction also
provides the session-connection synchronization service to the upper
layer.
FSP is a transport layer protocol as specified in [RFC1122], provides
services alike TCP [STD5] to ULA, with session layer features as
suggested in [OSI_RM], most noticeably session-connection
synchronization.
Gao Expires April 20, 2021 [Page 2]
Internet-Draft Flexible Session Protocol October 2020
1.1. Features
1.1.1. Transport Layer Mobility Support
FSP is meant to be transport layer protocol that keeps the IP address
as the routing locater but keeps it from being the key constituent of
the FSP identifier or any upper layer protocol built upon FSP. It is
a solution to avoid the routing scalability problem.
The dominating transport layer protocols, TCP and UDP that take use
of the IP address to identifying the end node, introduce the
Show full document text