Re: [mpls] Poll 1: ISD and PSD in the MNA Framework

Joel Halpern <jmh@joelhalpern.com> Mon, 30 May 2022 22:17 UTC

Return-Path: <jmh@joelhalpern.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 04940C1850C5 for <mpls@ietfa.amsl.com>; Mon, 30 May 2022 15:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.986
X-Spam-Level:
X-Spam-Status: No, score=-3.986 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, NICE_REPLY_A=-1.876, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbuuTBFh7ryB for <mpls@ietfa.amsl.com>; Mon, 30 May 2022 15:16:57 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B983AC17A756 for <mpls@ietf.org>; Mon, 30 May 2022 15:16:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4LBqWs2Xwsz6G9J8 for <mpls@ietf.org>; Mon, 30 May 2022 15:16:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1653949017; bh=WqaNjkcJrUr9lUn8GwYoM0Ix8WTsjBrqunT+npM6T2w=; h=Date:Subject:To:References:From:In-Reply-To:From; b=QDMTGAs+B63hJUnQBPF5laQDTOIboe1Ghf1l/vdUgr8vq+j5KbPgHCjkJ7BodFNt+ JQ6e4a1vqF71eFsB2h7yJ76iz6z3QaKM9nhnoeREnQtBacsQAM0gt0Rsjp9yOhyTuO uuiZ1z4jYw02NhnOLxo9p2H0WRTaipqeBlbaTy2M=
X-Quarantine-ID: <Rzy2Ye95Qvvn>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.23.181] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4LBqWr6pSPz6G99D for <mpls@ietf.org>; Mon, 30 May 2022 15:16:56 -0700 (PDT)
Message-ID: <024366c6-4e22-2153-81d7-9088383fe190@joelhalpern.com>
Date: Mon, 30 May 2022 18:16:55 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1
Content-Language: en-US
To: "mpls@ietf.org" <mpls@ietf.org>
References: <b660b14c-b9ee-16a6-b599-6d0789f363db@pi.nu>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <b660b14c-b9ee-16a6-b599-6d0789f363db@pi.nu>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/pzCIXDvc57ow7eFutLv51FOylZ8>
Subject: Re: [mpls] Poll 1: ISD and PSD in the MNA Framework
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.34
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: Mon, 30 May 2022 22:17:03 -0000

I agree that the framework should (and does) describe both in-stack data 
and post-stack data.

Thank you,

Joel

On 5/30/2022 5:20 PM, Loa Andersson wrote:
> MPLS working group and and the Open MPLS DT,
>
> The working group chairs believe the current situation is:
>
> The Framework document must be solution independent and say:
>
> a packet may carry Ancillary Data using one or both of the following 
> methods:
>
>    (1) in-stack, and
>
>    (2) post-stack.
>
> It is up to the document specifying the Network Action to specify which
> method is to be used for which Ancillary Data.
>
> Note, a Network Action may not require inclusion of Ancillary Data.
>
> Is this the consensus of the working group? Please respond to the MPLS 
> WG mail list.
>
>
> Loa Andersson
> for the Open DT wg chairs
>