Re: [rohc] [multipathtcp] MPTCP and ROHC

Yoshifumi Nishida <nsd.ietf@gmail.com> Fri, 13 September 2019 07:36 UTC

Return-Path: <nsd.ietf@gmail.com>
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 1BFDA1200E5; Fri, 13 Sep 2019 00:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LY2k0gVJxd02; Fri, 13 Sep 2019 00:36:06 -0700 (PDT)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 367541200C1; Fri, 13 Sep 2019 00:36:06 -0700 (PDT)
Received: by mail-wr1-x42d.google.com with SMTP id y19so31012182wrd.3; Fri, 13 Sep 2019 00:36:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ohNmx6A6ZsycIPBuewimjXC/ajxTGWA5UC7nfOwkXl8=; b=qsDHdioBxr85iO8NPFBQJIGowD95RNf85EeXgqlLpO2BDGrObpD8xHMtaEzsWtY8UA i9BS0Gj9ziSjsWtiAoEaHzAY8MZL95KXtf/4kN1Qrnkz9MmLMV3PuwTH7UuJncbE4Un8 n0RF9ntygINUjqURZDSdIUhyGRGBVk6TU/CslESL/nsCtW/bX+5zbHAoQQgRXyfpPkj+ mA8DTt1MrZ/G0ksZ7snFTqL+4CrLPS6jBhvOTEF7Vqd3m/jd6rkyvlFiIpgkUlvNZS36 95F+1fu1kNJZzyg2Q/uo1H3S3hfAl8jvyR7OeBxvwRtN4Uxkzm9I1yU8Z7AMthqS6Tp1 541A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ohNmx6A6ZsycIPBuewimjXC/ajxTGWA5UC7nfOwkXl8=; b=HkqY75Y1+ZFPVwQMTfwjwyQJp+npkcpCvr9PcxWesXKDHm2q8GOAQRNIa4mg/zmzTS i724uP/q9VJFI0SXYRLI5SLch+/n4JEHWHXOoC1WLcR7Tp2bKOfQRyZU9iWqjZdQpKBE tvANhk51pAKlbeIM6nCT3Y4AfrBgH5QFxYD3a50TBl46HDOCiEiqf3WlGdrLrH+xMC0E L7VEfRu3HIgl4RJfYHJPTzmnD8Fxq+LdCnAmi9Eeetn89IFaXPejtZNHClP70MLiQboZ qtfyoiC1mfWKWi2Z2jjTJ9bi/TklQGw7KcGZCDT0UFTeiQICXBNnYC8gkkir/lzyZhQ/ UimA==
X-Gm-Message-State: APjAAAWGxnp7Cr06zYO4uOQEm3U4jGCdOj7vX/ayhmEYxhOXsjSaiBvr hKi61e8WmgPHI3/UAVFhfAAZ/X2YeMPA9rkX1sY=
X-Google-Smtp-Source: APXvYqyutfLbNdGWNXwhOi94yNlYZ8CPNG3y6XYB7vcTIU05zXv8JVpOmGgo4qyHH+mTLvlpi+6PQzw+JwMYANUKK6s=
X-Received: by 2002:a5d:63ca:: with SMTP id c10mr3495422wrw.314.1568360164668; Fri, 13 Sep 2019 00:36:04 -0700 (PDT)
MIME-Version: 1.0
References: <BL0PR11MB33946D4261C2EE3A6CB8724E90B40@BL0PR11MB3394.namprd11.prod.outlook.com> <CAAK044TuJ+LHpQFBSzofx433RqzSM9Ma7UsBYNP4BZgaAM7wzg@mail.gmail.com> <BL0PR11MB3394E07141956303060D612A90B00@BL0PR11MB3394.namprd11.prod.outlook.com> <73A52B51F0555740AC68A0F117F0C49202D377D4CC@UM-EXMBX02.comm.ad.roke.co.uk>
In-Reply-To: <73A52B51F0555740AC68A0F117F0C49202D377D4CC@UM-EXMBX02.comm.ad.roke.co.uk>
From: Yoshifumi Nishida <nsd.ietf@gmail.com>
Date: Fri, 13 Sep 2019 00:35:52 -0700
Message-ID: <CAAK044Tt+k-2Cq1e0Rt=nTi7ZNYcrr=U_04PiU4i62MKmQjekA@mail.gmail.com>
To: "West, Mark" <mark.west@roke.co.uk>
Cc: "Border, John" <John.Border@hughes.com>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>, "rohc@ietf.org" <rohc@ietf.org>
Content-Type: multipart/related; boundary="0000000000007ef1b105926a4e6f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rohc/ilBgBMbCvnXWRawAhpuzuJSZuVA>
X-Mailman-Approved-At: Fri, 13 Sep 2019 05:00:30 -0700
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: Fri, 13 Sep 2019 07:36:09 -0000

+1.
I think the only difference between MPTCP packets and non-MPTCP TCP packets
is MPTCP option.
Also, MPTCP option should be no less than another kind of TCP option.
if there's any concerns on this, it'll be an interesting point for
discussions.
--
Yoshi

On Thu, Sep 12, 2019 at 1:44 PM West, Mark <mark.west@roke.co.uk> wrote:

>
>
> 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.
>
>
>
>
>
> [image: DSEi - Exhibiting at stand S1-310]
> <https://www.dsei.co.uk/welcome>
>
> Follow Us: LinkedIn <http://www.linkedin.com/company/roke-manor-research>
> | Twitter <https://twitter.com/rokemanor> | Facebook
> <https://www.facebook.com/rokemanor>
>
> Roke Manor Research Limited, Romsey, Hampshire, SO51 0ZN, United Kingdom.
> Part of the Chemring Group. Registered in England & Wales. Registered No:
> 00267550. The information contained in this e-mail and any attachments is
> proprietary to Roke Manor Research Limited and must not be passed to any
> third party without permission. This communication is for information only
> and shall not create or change any contractual relationship.
> www.roke.co.uk
> <http://www.roke.co.uk/?utm_source=Roke&utm_medium=Email&utm_content=Company%20Signature&utm_campaign=Roke>
> ------------------------------
>
> *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>
> wrote:
>
>
>
>     Does ROHC work with MPTCP?
>
>
>
>
>
> John
>
>
>
> _______________________________________________
> multipathtcp mailing list
> 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=>
>
>