1 / 6

Legacy Client-Server Communication & MPTCP Subflow Management

This document outlines the communication process between legacy clients and IPv4 servers, detailing request and response patterns, including address mapping and A-record retrieval for domains. It addresses issues of subflow management in Multipath TCP (MPTCP), demonstrating how addresses are swapped and how requests for A-records are resolved. The interactions are exemplified by numerous IP addresses and methodologies employed to enhance server-client transactions while maintaining connectivity within a complex network structure.

clint
Télécharger la présentation

Legacy Client-Server Communication & MPTCP Subflow Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Legacy client -> hIPv4 server S:10.1.1.1.1 D:10.2.2.2 S:10.1.1.1 D:172.16.0.5 A:192.168.0.1 E:10.2.2.2 S:192.168.0.1 D:10.2.2.2 A:172.16.0.5 E:10.1.1.1 ReplyALOC 172.16.0.5ALOC 172.16.0.4 SWAP S:192.168.0.1 D:10.2.2.2 Mapping RequestWhere is 10.2.2.2? A:172.16.0.5 E:10.1.1.1 www.foo.com? A-record: 10.2.2.2

  2. Legacy client -> hIPv4 server, return path S:10.2.2.2 D:192.168.0.1 S:10.2.2.2 D:10.1.1.1 S:10.2.2.2 D:192.168.0.1 A:172.16.0.5 E:10.1.1.1 A:172.16.0.5 E:10.1.1.1 S:10.1.1.1.1 D:10.2.2.2 S:10.1.1.1 D:172.16.0.5 A:192.168.0.1 E:10.2.2.2 S:10.2.2.2 D:192.168.0.1 A:172.16.0.5 E:10.1.1.1 S:192.168.0.1 D:10.2.2.2 A:172.16.0.5 E:10.1.1.1 ReplyALOC 172.16.0.5ALOC 172.16.0.4 SWAP S:192.168.0.1 D:10.2.2.2 Mapping RequestWhere is 10.2.2.2? A:172.16.0.5 E:10.1.1.1 www.foo.com? A-record: 10.2.2.2

  3. Legacy client -> hIPv4 server, adding MPTCP subflow S:192.168.0.2 D:10.2.2.2 SWAP A:172.16.0.4 E:10.1.1.1 S:10.1.1.1 D:172.16.0.4 A:192.168.0.2 E:10.2.2.2 S:10.1.1.1.1 D:10.2.2.2 S:10.1.1.1 D:172.16.0.5 A:192.168.0.1 E:10.2.2.2 S:192.168.0.2 D:10.2.2.2 S:192.168.0.1 D:10.2.2.2 A:172.16.0.4 E:10.1.1.1 A:172.16.0.5 E:10.1.1.1 ReplyALOC 172.16.0.5ALOC 172.16.0.4 SWAP S:192.168.0.1 D:10.2.2.2 Mapping RequestWhere is 10.2.2.2? A:172.16.0.5 E:10.1.1.1 www.foo.com? A-record: 10.2.2.2

  4. hIPv4 client -> legacy server S:10.2.2.2 D:10.1.1.1 www.foo.com? A-record: 10.1.1.1RLOC:192.168.0.1RLOC:192.168.0.2 S:10.2.2.2 D:192.168.0.1 A:172.16.0.5 E:10.1.1.1 S:10.2.2.2 D:192.168.0.1 A:172.16.0.5 E:10.1.1.1

  5. hIPv4 client -> legacy server, return path SWAP S:10.1.1.1 D:172.16.0.5 S:10.1.1.1 D:10.2.2.2 A:192.168.0.1 E:10.2.2.2 S:192.168.0.1 D:10.2.2.2 S:10.2.2.2 D:10.1.1.1 www.foo.com? A:172.16.0.5 E:10.1.1.1 A-record: 10.1.1.1RLOC:192.168.0.1RLOC:192.168.0.2 S:10.2.2.2 D:192.168.0.1 A:172.16.0.5 E:10.1.1.1 S:10.2.2.2 D:192.168.0.1 A:172.16.0.5 E:10.1.1.1

  6. hIPv4 client -> legacy server, adding MPTCP subflow S:10.2.2.2 D:192.168.0.2 A:172.16.0.4 E:10.1.1.1 S:10.2.2.2 D:192.168.0.2 A:172.16.0.4 E:10.1.1.1 S:10.2.2.2 D:10.1.1.1 www.foo.com? A-record: 10.1.1.1RLOC:192.168.0.1RLOC:192.168.0.2 S:10.2.2.2 D:192.168.0.1 A:172.16.0.5 E:10.1.1.1 S:10.2.2.2 D:192.168.0.1 A:172.16.0.5 E:10.1.1.1

More Related