Re: Comments on draft-fz-6man-ipv6-alt-mark-09

Tom Herbert <tom@herbertland.com> Tue, 19 May 2020 15:00 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0A263A07DE for <ipv6@ietfa.amsl.com>; Tue, 19 May 2020 08:00:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001] 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 mzMWN_WHKDbL for <ipv6@ietfa.amsl.com>; Tue, 19 May 2020 08:00:41 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 88D2F3A08CF for <6man@ietf.org>; Tue, 19 May 2020 08:00:41 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id d7so11624135eja.7 for <6man@ietf.org>; Tue, 19 May 2020 08:00:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+oYZAmOJKa8o3rL47Ncx85u7xQzQoRVq/AxLvR8DGmU=; b=L3QBZB+tYYm9U1C5UCxCUBwdrjebAFsx41C2Hc73J4xJ/AKnhR3b3Znv3Yl8+yuL1v mQoAeaQGHG+HBBS9I31CTEFbxZuexwRB86Sa9TsTM/G/OYkZVoKNv/Vu2vVzRSlnB19m uD7/1t63z9xIZuZ26U6hFltQTqp5ajcTxWjFP2LFBTMpH/W19hIN4ksSeaREi/xFjz0z Logag0VsECeoOm7BAI5CIWIi1L5gnpVuePdpTobWwRhTTQSY8TGB2aylXfU/qPIFsebg f7vc0apI2ticuzltCT85MJ256O87JMeq/bP2Xnb5BeTZ02OYJd3v55wxefpjPC4a4rNY r4tg==
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=+oYZAmOJKa8o3rL47Ncx85u7xQzQoRVq/AxLvR8DGmU=; b=a96ccqGO+gt17cvq3AJsBUBIi54zlS51S0hhtSMOjKYjTZwSztGRLWyhypKhxImqjC HQQubAcmOGsEL9xWIrydasuLvD3SD3YTf5Os6d/EdkGfiPMgwgl8rrTndCXprGFlQ06D 0x8tC12f8gs6hz6r7PoCFxERP1MkUXFYZsL+fPHW/HnHCAu98cAqTgxyf3UBdNhyMtrL CcQSByjo5E8OJ2JIkXpuDgHyTQjYeoPcXmu50BdhJsK0iGJCJ9NWcKuF83n/yMB5wVlG jOYiaoHhr1kxaYYHWtU2zIXjLVFNrpdEJWGEKxMZq95+DJTNb5dM67aZfzTbcXD08PuN 5J5w==
X-Gm-Message-State: AOAM530XsxGubJ4wVvd0QKazf83JCYS0W1x0Wy8/xCfwf8zoXvPwJPkW aGfRZ1WS8LJo0HvhhD+ND2Zf4xCpg1dDE/LltTnyRA==
X-Google-Smtp-Source: ABdhPJxJgVwZZErRZau3eIO26e4CQcMePfeWoqzmNOCKXqs+FUtkVm8W7QUzMnV33nIuKBuZgxPbBVWRrd/Y5aar7rQ=
X-Received: by 2002:a17:906:aecc:: with SMTP id me12mr1065827ejb.525.1589900439887; Tue, 19 May 2020 08:00:39 -0700 (PDT)
MIME-Version: 1.0
References: <CALx6S35bWVkTWcbdOt-HA-9XbH4WwRsTyaUdDA5q4rUNJvNNiw@mail.gmail.com> <da6e0d76-915b-a7da-8744-2f3761b43a98@gmail.com>
In-Reply-To: <da6e0d76-915b-a7da-8744-2f3761b43a98@gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Tue, 19 May 2020 08:00:28 -0700
Message-ID: <CALx6S37STTqFfFmOm9Rosmot5Dt2+YpQLoy4EPGzFn=6MTG_+A@mail.gmail.com>
Subject: Re: Comments on draft-fz-6man-ipv6-alt-mark-09
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: 6MAN <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/h2O5I7qBFQwTgMi_-ragwOx5qCw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 May 2020 15:00:45 -0000

On Mon, May 18, 2020 at 7:39 PM Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
>
> Tom,
>
> > It's unclear to me how the FlowMonID is set, how it's used, and why
> > the Flow Label isn't sufficient for this purpose.
>
> That was proposed by the authors and discarded a long time ago, because
> the usage was incompatible with RFC6437. I can't remember the details
> without looking up long-expired drafts and old email. But generally:
> you can't encode semantics in conformant flow labels, because they are
> pseudo-random.
>
Brian,

AFAICT the FlowMonID is just another type of flow identifier in the
packet. For the purposes of correlating flows in the network I believe
it is redundant to the flow label and would otherwise add a lot of
complexity to implement. I think what you might be referring to are
earlier proposals to put the loss signal bits in the flow label and
not use an EH-- that idea is indeed infeasible at this point. IMO, we
should be able to eliminate FlowMonID from the option, but still need
the two signaling bits in the option hence the alt marking option
would contain one byte of data.

Tom

> Regards
>    Brian