Re: [mpls] Today's MPLS Open DT meeting cancelled
Loa Andersson <loa@pi.nu> Wed, 27 October 2021 15:03 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 B15243A0D7C; Wed, 27 Oct 2021 08:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.227
X-Spam-Level:
X-Spam-Status: No, score=-5.227 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-3.33, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 O1wu-Vd_yq_m; Wed, 27 Oct 2021 08:03:40 -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 C9B4D3A0D8E; Wed, 27 Oct 2021 08:03:39 -0700 (PDT)
Received: from [192.168.1.94] (c-e605e353.020-236-73746f24.bbcust.telenor.se [83.227.5.230]) (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 2FA5234A3DB; Wed, 27 Oct 2021 17:03:36 +0200 (CEST)
To: Kireeti Kompella <kireeti.ietf@gmail.com>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "pals-chairs@ietf.org" <pals-chairs@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, DetNet Chairs <detnet-chairs@ietf.org>
References: <d3cf1ff1-031e-b1ba-e1a4-927e7a1da9aa@pi.nu> <31BCDA2B-4FA1-479A-A395-940C09337449@gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <a0c87a8c-fb56-54c3-fb17-884bfca754d1@pi.nu>
Date: Wed, 27 Oct 2021 17:03:36 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <31BCDA2B-4FA1-479A-A395-940C09337449@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/ada8e6owzg_5iK6bwG6bLrDi3AI>
Subject: Re: [mpls] Today's MPLS Open DT meeting cancelled
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: Wed, 27 Oct 2021 15:03:45 -0000
Kireeti, Sorry for late response. One reason why we setup the agenda as we did for last week (1) requrements and (2 )PSD Directive (if time allows), was that we wanted to the requirements first. Then the discussion on the requirements disappeared it was natural to cancel the meeting. There are also a few question that I wanted to think about before going ahead with the PSD directive. First, the design directive should be a guideline the keeps solutions within a sound architectural boundary. Your text seem to be describing one particulate solution. We should not confuse a design directive with the specification. For the design directive is enough if we say "you can't place PSD that belongs to more than one FA/NF afteer the label with the BoS bit set". The rest is specification and should go into ID/RFC. Second, we should not anticipate wg consensus or actually specifications. There are currently more than one proposal, on for example how the indicators should work. For example the FAI proposal works with one flag field, and let the implementation figure out what is in the PSD. The NFI proposal is different, and I not entirely clear how it works. I think it is one flag field for actions/function that generate ISD and NoD, and two flag fields (end-to-end and hop-by-hop) for actions/functions that generate PSD. Your design directive seems to anticipate that we will go with the FAI proposal, but we need to wait to take that decision. The design directive don't need that decision "don't place more than one set of PSD after the BoS" is independent of how the PSD is generated. /Loa On 21/10/2021 16:23, Kireeti Kompella wrote: > Agree we should wait for Matthew on the requirements discussion, but we can still have the meeting today and talk about the PSD Directive. I’m ready. > >> On Oct 21, 2021, at 06:52, Loa Andersson <loa@pi.nu> wrote: >> >> Folks, >> >> We have just learned that Matthew can't make today's meeting. In a short consultation with the other chairs we agree that we don't want to take the requirement discussion without Matthew. We therefore decided to postpone the meeting one week. >> >> /Loa >> -- >> >> 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 > -- Loa Andersson email: loa@pi.nu Senior MPLS Expert loa.pi.nu@gmail.com Bronze Dragon Consulting phone: +46 739 81 21 64
- [mpls] Today's MPLS Open DT meeting cancelled Loa Andersson
- Re: [mpls] Today's MPLS Open DT meeting cancelled Kireeti Kompella
- Re: [mpls] Today's MPLS Open DT meeting cancelled Loa Andersson
- Re: [mpls] Today's MPLS Open DT meeting cancelled John E Drake
- Re: [mpls] Today's MPLS Open DT meeting cancelled Kireeti Kompella