Subject: [Spud] "framing for UDP"

From: Lars Westberg <[email-masked]>
Date: Tue, 14 Apr 2015 11:03:17 +0000

Hi all,

We have prepared a draft on a UDP-based container architecture to transfer transport protocol components in an end2end  UDP-stream. The concept proposes a standard “encapsulation”  to identify/select the used protocol components rather than having separate specification for different protocols. The idea is to allow for a more open protocol design where each  smaller protocol component can be modified and replaced separately.

This end2end component identification/selection has the same semantics as SPUD (meant to bring information about higher protocol layers in an end2end header), so in principle SPUD could be used as a protocol for both end2end transport protocol (component) negotiation and middlebox interception of the information about the used components.

Is this relevant for the SPUD-work?

http://www.ietf.org/internet-drafts/draft-mihaly-tp-flexibility-00.txt
http://www.ietf.org/internet-drafts/draft-westberg-tp-compositioning-framework-00.txt

-Lars Westberg, Ericsson