IETF Logo Mail Archive

Re: [mpls] Update to the bullets on the first page of my review of draft-song-mpls-extension-header-09

Loa Andersson <loa@pi.nu> Thu, 08 September 2022 09:20 UTC

Return-Path: <loa@pi.nu>
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 3663EC1524D7; Thu, 8 Sep 2022 02:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 VwOWRABl12P6; Thu, 8 Sep 2022 02:20:28 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 390C0C1524B0; Thu, 8 Sep 2022 02:20:25 -0700 (PDT)
Received: from [192.168.1.241] (c-8f02e353.020-236-73746f24.bbcust.telenor.se [83.227.2.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 43F2136869F; Thu, 8 Sep 2022 11:20:23 +0200 (CEST)
Message-ID: <67e02989-b305-7a5d-3d2e-ac569c6a4a84@pi.nu>
Date: Thu, 08 Sep 2022 11:20:22 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.1
Content-Language: en-CA
To: Tony Li <tony.li@tony.li>, John Drake <jdrake@juniper.net>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "draft-song-mpls-extension-header@ietf.org" <draft-song-mpls-extension-header@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>, DetNet Chairs <detnet-chairs@ietf.org>
References: <98356ad3-ec52-3a5c-ee31-1ee604d4b5db@pi.nu> <dc03203bf7ee49caafccdb70221edc1a@huawei.com> <b718cd04-c822-b744-0ca2-9c3e47ea2f62@pi.nu> <BY3PR13MB47879BAD2537E77C1D6193F89A799@BY3PR13MB4787.namprd13.prod.outlook.com> <33185189-08e3-71da-123c-2f17fe5ad0bb@pi.nu> <BY3PR13MB47878BDBE64EE739BA4F5DF99A799@BY3PR13MB4787.namprd13.prod.outlook.com> <5A840AB5-7B0F-4C21-B0B0-700194B03A32@tony.li> <BY3PR13MB478797DB5335413F94621C219A799@BY3PR13MB4787.namprd13.prod.outlook.com> <06759C2A-CA9D-4957-8203-D71BAFA1AB67@tony.li> <c5820e62-b4ed-d88a-d738-16ee52088342@pi.nu> <200451CE-9554-4298-BB9C-2EB4B63D843F@tony.li> <4F01E812-4BF5-4808-B21E-063577A47E4F@juniper.net> <E46FD1E3-04C9-44D1-AEEF-8588BA647841@tony.li>
From: Loa Andersson <loa@pi.nu>
In-Reply-To: <E46FD1E3-04C9-44D1-AEEF-8588BA647841@tony.li>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/ivkANwI_52z_G8BUATprGeJoUi0>
Subject: Re: [mpls] Update to the bullets on the first page of my review of draft-song-mpls-extension-header-09
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 08 Sep 2022 09:20:33 -0000

Tony,

I'm fine with your proposed text for the framework.

What I don't understand is why we should not add something to the 
requirements also.

/Loa

On 2022-09-05 19:13, Tony Li wrote:
> 
> John,
> 
>>  Should we also add that the definition of a network action MUST 
>> specify its interaction with all other currently defined network actions?
> 
> 
> You want deterministic semantics too? :-)
> 
> I can live with that.  Revised text:
> 
>     For MNA to be consistent across implementations and predictable
>     in operational environments, its semantics need to be entirely
>     predictable. A solution MUST specify a deterministic order for
>     processing each of the Network Actions in a packet. Each Network
>     Action must specify how it interacts with all other previously
>     defined Network Actions.
> 
> 
> Tony
> 

-- 
Loa Andersson                        email: loa@pi.nu
Senior MPLS Expert                          loa.pi.nu@gmail.com
Bronze Dragon Consulting             phone: +46 739 81 21 64

v2.23.0 | Report a Bug | By Email