%% You should probably cite draft-kang-tcpm-subtype-capability-exchange-02 instead of this revision. @techreport{kang-tcpm-subtype-capability-exchange-01, number = {draft-kang-tcpm-subtype-capability-exchange-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-kang-tcpm-subtype-capability-exchange/01/}, author = {Jiao Kang and liangqiandeng and Shangling Deng}, title = {{Subtype Capability Exchange During MPTCP Handshake}}, pagetotal = 7, year = 2022, month = jun, day = 17, abstract = {Multipath TCP provides the ability to simultaneously use multiple paths between peers. MPTCP protocol defines seven subtypes in MPTCP v0 {[}RFC6824{]} and ten subtypes in MPTCP v1 {[}RFC8684{]} to differentiate message types and implement some additional functions during a session. This draft proposes an enhancement to support Subtype Capability Exchange during MPTCP connection establishment in order to improve elastic scalability of MPTCP protocol. It includes: 1) requirements for which this kind of capability exchange during handshake is important for a MPTCP session; 2) a typical flow for Subtype Capability Exchange between peers; 3) a feasible solution on protocol design is suggested.}, }