IETF Logo Mail Archive

Re: [Stackevo-discuss] Fwd: New Version Notification for draft-welzl-irtf-iccrg-tcp-in-udp-00.txt

Tom Herbert <tom@herbertland.com> Thu, 24 March 2016 00:51 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: stackevo-discuss@ietfa.amsl.com
Delivered-To: stackevo-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EEAA12DA20 for <stackevo-discuss@ietfa.amsl.com>; Wed, 23 Mar 2016 17:51:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 AHWZuoeN2kJQ for <stackevo-discuss@ietfa.amsl.com>; Wed, 23 Mar 2016 17:51:36 -0700 (PDT)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (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 7069C12DA21 for <stackevo-discuss@iab.org>; Wed, 23 Mar 2016 17:51:36 -0700 (PDT)
Received: by mail-ig0-x232.google.com with SMTP id ig19so3106117igb.1 for <stackevo-discuss@iab.org>; Wed, 23 Mar 2016 17:51:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Kjs6ITczTPGIhfmJ2BFyYJ5NA0YA/two4Rwj/O8Q6vY=; b=JvjjxwjHroGpsMoDaRR+FItUyeMzk1ar9wg7W7uxWBrb24SBHtOrlDNFe4gZbFSuue NmP+wW4y4gZrF5Sh1U5m3VH4DPMN3Yd8UBFcD4s3HED/8Gpm8krsbtmzgbbtZWIj14d8 SMdtN2Cpq65DcsMHImn1ccE1mmhyO4IOfShvL1LL0atLe0Yuz8pXJDWpgIR9lE2Z8dQ/ 5UT6hthIxlsu048U0CdDU0jadlWgo3HsZCZC/OEGSdcXsQOEbFM5tYu4hTZG8YqJMsZZ 8t0dpUDJlH9KoVjTri94jwfXOeWxaT9bFncj1HlqL95L6Rf0gCgzAbWoFqP2cFLFNf8j KMnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Kjs6ITczTPGIhfmJ2BFyYJ5NA0YA/two4Rwj/O8Q6vY=; b=nFGKY7OcEQYruVhMgG+D1llIdx4ELbB30gKpY/1+6rlAPGSSzPQkfNmIskNdmnSBCB z/slGHEhpp7w9i7FuldWHv94np8eo7D/dzgtZXX7Y1gHkFhQrXVTUTjd87yIAbIsgvFp vUo7UMXPnikoEJyHtP6uFxTgSesXlM1MGJvch6jtCuLbommvJfGMvQxVYkwT9Q4/Ogra 6sWrcWa1L3/FquIFvRfYHJqBx9rFgHt4HHafnhSROGE6sYLggmot2ftqnSvNrZfbL2r7 eqiEUFJr4KTNTvVa4PapFLmee2SVzKuvFwzJastUbThLYJ8i+Md8Zvzvp6p5yv0dCQWh i3AQ==
X-Gm-Message-State: AD7BkJKgA7AZt0bmwbyQmK3Hg7OGejlo8Lhr9vFs2SCAEZb0tBxX/ZqTY1S/3X3sGz7hg/vhH/BVBNviDwH3kw==
MIME-Version: 1.0
X-Received: by 10.50.28.105 with SMTP id a9mr12202872igh.94.1458780695768; Wed, 23 Mar 2016 17:51:35 -0700 (PDT)
Received: by 10.107.130.198 with HTTP; Wed, 23 Mar 2016 17:51:35 -0700 (PDT)
In-Reply-To: <56F32D4D.6040308@isi.edu>
References: <A741874C-0E2C-4905-9FD3-D29B4B94A9C0@ifi.uio.no> <56F3212B.5020408@isi.edu> <20F3E6FF-DED4-46BD-BFD5-C76F8A6A8D40@ifi.uio.no> <CALx6S35n8bD6UwGT823S8dhmzncm3=B_VYrKbm0sgzv35-weRQ@mail.gmail.com> <56F32D4D.6040308@isi.edu>
Date: Wed, 23 Mar 2016 17:51:35 -0700
Message-ID: <CALx6S35acubkAwo4VTz5aV=96mBToMCkxQWNPucN4=xY1gnFXg@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/stackevo-discuss/RNUKJHLpokzszuXmJ3FCITHTu4w>
Cc: stackevo-discuss@iab.org, Michael Welzl <michawe@ifi.uio.no>
Subject: Re: [Stackevo-discuss] Fwd: New Version Notification for draft-welzl-irtf-iccrg-tcp-in-udp-00.txt
X-BeenThere: stackevo-discuss@iab.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IP Stack Evolution Discussion List <stackevo-discuss.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/stackevo-discuss>, <mailto:stackevo-discuss-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stackevo-discuss/>
List-Post: <mailto:stackevo-discuss@iab.org>
List-Help: <mailto:stackevo-discuss-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/stackevo-discuss>, <mailto:stackevo-discuss-request@iab.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2016 00:51:39 -0000

On Wed, Mar 23, 2016 at 4:57 PM, Joe Touch <touch@isi.edu> wrote:
>
>
> On 3/23/2016 4:51 PM, Tom Herbert wrote:
> ...
>> You should be able to accomplish the "same path" behavior by setting
>> IPv6 flow label same value for different connections between same IP
>> pair. This avoids all the unpleasantness that accompanies
>> encapsulation.
>
> You would need to do IP encapsulation AND use a flow label on that
> encaps. Otherwise, you'd have different IP addresses with the same flow
> label - which aren't expected to do anything useful.
>
Oh, I guess I'm missing something. If the (destination) addresses are
different how does encapsulating in UDP allow packets for these
connections to take the same path?

Tom

> See RFC6437, Sec. 2.
>
> Joe

v2.23.0 | Report a Bug | By Email