Re: [mpls] mpls-open-dt: ancillary data commens

Loa Andersson <loa.pi.nu@gmail.com> Fri, 13 August 2021 12:24 UTC

Return-Path: <loa.pi.nu@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 721453A1685 for <mpls@ietfa.amsl.com>; Fri, 13 Aug 2021 05:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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 0m6YpX66mbuo for <mpls@ietfa.amsl.com>; Fri, 13 Aug 2021 05:24:28 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 55DC23A1684 for <mpls@ietf.org>; Fri, 13 Aug 2021 05:24:28 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id y34so19532312lfa.8 for <mpls@ietf.org>; Fri, 13 Aug 2021 05:24:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=ysD1ZqsocGo/zfI78LfsLL/27YJceu+XncMh0iB6VJk=; b=uH3KvLprlJSuyJ28jpp6bxCf8+FFBK8IKFhxjheCDZZPTSFdYWX4fWzJ5qIRxupHJB 4e/3c5K1Yl2LIwmuvk4htS0pRU+aOFK1woxTisRiZaEaRuTp0lAX8Rk0k5zAPOgTdFM6 ySpRo79FEGmxcPMx0D+TSnOvVEKsekfPaGO6eGHprCjS+bnTPHqvZZwKvlr6yztDjBZH SwSyIQ3O6lJQZpqbaMb8Bo+34P/ZTkusZysQuCFYVv9PAiiwvTixYbDoNjuXrkKBTmBe LdPKkXmTq4ntkzWau5WT9oqgRy1QQTHaLiRsW581gvHwpbgUvvxa8nAryX9qklcszDC4 IIyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:mime-version:subject :from:in-reply-to:date:cc:message-id:references:to; bh=ysD1ZqsocGo/zfI78LfsLL/27YJceu+XncMh0iB6VJk=; b=YMcU0k46X2kYILg6I0zBTv0A0JKv/DCGUb5bW3bNUAcwS7xA5B3pbfBSW+2Dkox8ab QCoQN6YJbPiiXeXYvLUtRQ63vpTbx+nsX6/PSaEm+RmR5djSd+Pa+3tl0ms0aXDFiDUK 9qj8ivzVk4MW0yYfAWaE2f4VL6ceiCHCEW1yBlau3pXv4T0g8uPRw+49WqSteZ7J6LGo VFLPvclIEC9HQt2zsNoQsFo/Fktl+/atlZxp+elmQJv9MOAINHx/HexxvuuSKaTLZgVL P2aKA8pWZwFvKwRcyVBWcSv16zGvUXm9iYGZsG4tyVQ8LRsnpdR1zH7sWEulGA5wUjnD H0uw==
X-Gm-Message-State: AOAM531kjwxegg3j8tftzxMPmYhDkAHeVjKjIUEP4DghJbi5XX8stK5d s8qBVMQIObz4npyegoLpUyk=
X-Google-Smtp-Source: ABdhPJxI84CwgfMWd3XD+Kn37au4rRstrTDPoTBnXI6vCBTwNPH26JMwc+CHEltqMcOpNEw4g3166Q==
X-Received: by 2002:a05:6512:942:: with SMTP id u2mr1454173lft.501.1628857464918; Fri, 13 Aug 2021 05:24:24 -0700 (PDT)
Received: from smtpclient.apple ([2a02:aa1:1601:8548:2c3d:26b4:42f4:cf83]) by smtp.gmail.com with ESMTPSA id s18sm142987lfe.198.2021.08.13.05.24.24 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 13 Aug 2021 05:24:24 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Loa Andersson <loa.pi.nu@gmail.com>
In-Reply-To: <e02e551c-634a-12ec-e1cb-24c1f33cc021@pi.nu>
Date: Fri, 13 Aug 2021 14:24:23 +0200
Cc: Toerless Eckert <tte@cs.fau.de>, mpls@ietf.org
Message-Id: <99E06554-AB70-4D59-B245-D09A9817E91E@gmail.com>
References: <e02e551c-634a-12ec-e1cb-24c1f33cc021@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: iPhone Mail (18G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/VQHx_-CAQkAebPrBgE_tDAEZ-zs>
Subject: Re: [mpls] mpls-open-dt: ancillary data commens
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Aug 2021 12:24:35 -0000

Toerless, DT,

I accidently omitted two words, uppdated below. 

Sent from my iPhone

> On 13 Aug 2021, at 12:20, Loa Andersson <loa@pi.nu> wrote:
> 
> ´╗┐Toerless,
> 
> I got your point, after thinking a bit, and not really convinced about the overload of "type". But I agree that "implicit", in-stack", and "after BoS"
does not
>  designates good "types", so I agree to change along thge lines you suggested, though I don't think changing the header only is enough.

/Loa
> 
> First:
> 
> What about:
> 
> OLD
> Types of ancillary data
> 
>   We have (tentatively) three different types of ancillary data
> 
>   - implicit, the indicator is sufficient, and a node knows what to do
>     just because the indicator is there
>   - "in-stack-data", the ancillary data is in the stack accompanying
>     the indicator
>   - "after the BoS", the ancillary data is found after the label stack
> 
>   Note: There might be a fourth possibility - the ancillary data is
>   carried as part of the packet pay-load, but for the time being I'd
>   like to excluded that method.
> NEW
> Positioning of ancillary data
> 
>   We have (tentatively) three different to include (position) ancillary
>   data in an MPLS packet.
> 
>   - implicit, the indicator is sufficient, and a node knows what to do
>     just because the indicator is there
>   - "in-stack-data", the ancillary data is in the stack accompanying
>     the indicator
>   - "after the BoS", the ancillary data is found after the label stack
> 
>   Note: There might be a fourth possibility - the ancillary data is
>   carried as part of the packet pay-load, but for the time being I'd
>   like to excluded that method.
> END
> 
> Does this work?
> 
> Second:
> 
> You had a comment about regardless how the ancillary data are positioned, it can be used to inform that there are data conveyed to the node by the control plane or that has been configured. I think that was intended to replace the "Note:" above.
> 
> Can you try to write a text.
> 
> /Loa
> 
>> On 12/08/2021 18:04, Toerless Eckert wrote:
>> a) Suggest to replace:
>>    Types of ancillary data
>>    with
>>    Positioning of ancillary data
>>    Types is an overloaded term and make me for example foremost think it means semantics.
>>    Positioning should hopefully be more precisely describin what this point describes.
> 
> -- 
> 
> Loa Andersson                        email: loa@pi.nu
> Senior MPLS Expert                          loa.pi.nu@gmail.com
> Bronze Dragon Consulting             phone: +46 739 81 21 64
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls