IETF Logo Mail Archive

Re: [rohc] [multipathtcp] MPTCP and ROHC

"West, Mark" <mark.west@roke.co.uk> Thu, 12 September 2019 20:44 UTC

Return-Path: <mark.west@roke.co.uk>
X-Original-To: rohc@ietfa.amsl.com
Delivered-To: rohc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9537B120169 for <rohc@ietfa.amsl.com>; Thu, 12 Sep 2019 13:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.098
X-Spam-Level:
X-Spam-Status: No, score=-4.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OfSFY5qZQP2D for <rohc@ietfa.amsl.com>; Thu, 12 Sep 2019 13:44:04 -0700 (PDT)
Received: from eu-smtp-delivery-167.mimecast.com (eu-smtp-delivery-167.mimecast.com [146.101.78.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75BCB12006E for <rohc@ietf.org>; Thu, 12 Sep 2019 13:44:04 -0700 (PDT)
Received: from UM-EXCAS01.comm.ad.roke.co.uk (salt-ext.roke.co.uk [109.207.29.2]) (Using TLS) by relay.mimecast.com with ESMTP id uk-mta-103-qOxo_fFXM6O2Xy7tuK4jTg-1; Thu, 12 Sep 2019 21:43:59 +0100
Received: from UM-EXMBX02.comm.ad.roke.co.uk ([fe80::867:2e75:af6e:4b7f]) by UM-EXCAS01.comm.ad.roke.co.uk ([::1]) with mapi id 14.03.0319.002; Thu, 12 Sep 2019 21:43:58 +0100
From: "West, Mark" <mark.west@roke.co.uk>
To: "Border, John" <John.Border@hughes.com>, Yoshifumi Nishida <nsd.ietf@gmail.com>
CC: "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "rohc@ietf.org" <rohc@ietf.org>
Thread-Topic: [multipathtcp] MPTCP and ROHC
Thread-Index: AQHVaaZNJGhvXnKmOkqKQ6oVlhldd6cofzmA
Date: Thu, 12 Sep 2019 20:43:57 +0000
Message-ID: <73A52B51F0555740AC68A0F117F0C49202D377D4CC@UM-EXMBX02.comm.ad.roke.co.uk>
References: <BL0PR11MB33946D4261C2EE3A6CB8724E90B40@BL0PR11MB3394.namprd11.prod.outlook.com> <CAAK044TuJ+LHpQFBSzofx433RqzSM9Ma7UsBYNP4BZgaAM7wzg@mail.gmail.com> <BL0PR11MB3394E07141956303060D612A90B00@BL0PR11MB3394.namprd11.prod.outlook.com>
In-Reply-To: <BL0PR11MB3394E07141956303060D612A90B00@BL0PR11MB3394.namprd11.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.193.190]
MIME-Version: 1.0
X-MC-Unique: qOxo_fFXM6O2Xy7tuK4jTg-1
X-Mimecast-Spam-Score: 0
Content-Type: multipart/alternative; boundary="_000_73A52B51F0555740AC68A0F117F0C49202D377D4CCUMEXMBX02comm_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rohc/hEHCGGO4E_NLAppMa-IlXCq4a78>
Subject: Re: [rohc] [multipathtcp] MPTCP and ROHC
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rohc/>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Sep 2019 20:50:59 -0000

It’s been a long time, but… ROHC-TCP should work with MPTCP (although I’ve never tested it). ROHC can handle ‘generic’ TCP options (i.e. those for which there’s no optimised  compressor  behaviour; that would include all MPTCP options) and in other respects should be transparent: if a header field changes in an unexpected way, the compressor will end up sending a less efficient (or even uncompressed) representation. So I haven’t thought about the implications for the compression ratio – but it shouldn’t break.

Mark.


From: Rohc [mailto:rohc-bounces@ietf.org] On Behalf Of Border, John
Sent: 12 September 2019 21:11
To: Yoshifumi Nishida
Cc: multipathtcp@ietf.org; rohc@ietf.org
Subject: Re: [rohc] [multipathtcp] MPTCP and ROHC

The latter.

From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Sent: Thursday, September 12, 2019 3:46 AM
To: Border, John <John.Border@hughes.com>
Cc: multipathtcp@ietf.org; rohc@ietf.org
Subject: Re: [multipathtcp] MPTCP and ROHC

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi John,
Do you mean whether we can compress MPTCP options with ROHC or just MPTCP won't break ROHC?
--
Yoshi

On Sun, Sep 8, 2019 at 7:26 AM Border, John <John.Border@hughes.com<mailto:John.Border@hughes.com>> wrote:

    Does ROHC work with MPTCP?


John

_______________________________________________
multipathtcp mailing list
multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
https://www.ietf.org/mailman/listinfo/multipathtcp<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_multipathtcp&d=DwMFaQ&c=dIKa1mMv92xhhFzVXv5A3Q&r=9F44ji63_2hvW5HufmlpP-DFKXuFy4jDtL5PXwKlTqg&m=r8FoosS9r5k8j4FLwQ_iuAeeuWLM7tRjWDDnCADTVGM&s=YO-lkzCO6o1DwCPEXY54s5u8wQcJwhe2aWqzIdiU5PQ&e=>

v2.23.0 | Report a Bug | By Email