Re: [mpls] MPLS-RT Review of draft-gandhi-mpls-ioam-sr-04

Loa Andersson <loa.pi.nu@gmail.com> Tue, 19 January 2021 03:00 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 AF39D3A1080; Mon, 18 Jan 2021 19:00:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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 T19_UY7m8ZKs; Mon, 18 Jan 2021 19:00:40 -0800 (PST)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (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 CB45A3A1082; Mon, 18 Jan 2021 19:00:40 -0800 (PST)
Received: by mail-pf1-x434.google.com with SMTP id 11so11361516pfu.4; Mon, 18 Jan 2021 19:00:40 -0800 (PST)
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=mKdacPoYSUw/iLriFP39unqCLmmVdSGfiyVljRnojts=; b=cA8Kpec9zwUdKv9AZm6uaMtVif0A30pTfqOkb3/raS6ymXPXOF7xAUCVUlqyheCYy7 Yr2NDp3jDP6y3jWIC3hD2ORu0s4uJ66WHCY99AkUwz2Z63FZ+r5mMHARjnUGqt43oFdX j9gFOtT3enEl7el/xR188Rdy2EAROBL+wci92Fqv8DKe+zlqBtpTxe3UiPm5EVgQUJ/h KTVuVahnDGMNWXwywN/uGRmIL8nnfm7rkKQVGkiVhehjoPpmYQfxNcPPOkxYX7JRoOAA sO+8KAb4CUajXW1aJ87dePrwPGxUhmJkxR02tGUcZmymz5nPoEOAVXWmHooqKR1jvvha 2vnw==
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=mKdacPoYSUw/iLriFP39unqCLmmVdSGfiyVljRnojts=; b=iK1bIty8BHKpf48I5vyy161WjVg0Po2H5s0Rp01Kskk9qNtiywzfKriWovRvHwRXKj DpUlL+FFLTV/2x4nKanAMQZMDNPWmyYR55A5lewBkNT44/WwO9hpl6L0KuajitTqTWKv 8gm6rS9HwaB0MklgcM9JGbix3krpxGV30XcaO7JqVPr5ZjRi0nr6Vb6/1lKRtWKgCLuV o5VX55Tfd41+TUYtvSfnkxZ959X8Gs7w4roONOv+tbrzOp0Koa9XDh8ljG9kedMA56gG SJ7LqecX7DlUGpg+xVqX13zIK5cJUnxU+wY4nT/UyS3o7jZ2uuUFJKR8ac4mqCbOhpel PMZA==
X-Gm-Message-State: AOAM531dzL4cBYzKaxyR4JULmH5aB2U5yE5ZuR22Q4mD0fqOHhiLZrx+ h5Qr/F91XdeAQ+w1wogQ9eE=
X-Google-Smtp-Source: ABdhPJxi3d9ZkBESaOqnHgmP9kcfYiMLEu69dVir1IBT2sqzxFZDou3wkNIf2l2CidOEpY87k+WNBw==
X-Received: by 2002:a63:1519:: with SMTP id v25mr2478491pgl.217.1611025240152; Mon, 18 Jan 2021 19:00:40 -0800 (PST)
Received: from [192.168.1.31] ([124.104.17.232]) by smtp.gmail.com with ESMTPSA id e21sm16972389pgv.74.2021.01.18.19.00.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Jan 2021 19:00:39 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-D257B6C3-9F64-4333-90B8-2C00654255BB"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Loa Andersson <loa.pi.nu@gmail.com>
In-Reply-To: <9A29135C-0660-4016-903A-835004B5FF9D@gmail.com>
Date: Tue, 19 Jan 2021 11:00:37 +0800
Cc: Stewart Bryant <stewart.bryant@gmail.com>, Mach Chen <mach.chen@huawei.com>, mpls <mpls@ietf.org>, mpls-chairs <mpls-chairs@ietf.org>, draft-gandhi-mpls-ioam-sr@ietf.org
Message-Id: <62C862C5-2429-48E6-B6F3-BCD8F392B221@gmail.com>
References: <9A29135C-0660-4016-903A-835004B5FF9D@gmail.com>
To: "Rakesh Gandhi (rgandhi)" <rgandhi=40cisco.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (18C66)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/_Kd6q8jIEBbyCOqSGS4vJc15THA>
Subject: Re: [mpls] MPLS-RT Review of draft-gandhi-mpls-ioam-sr-04
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: Tue, 19 Jan 2021 03:00:43 -0000

Oooopps!

the list was already copied, well fine. Please comment!

/Loa

Sent from my iPhone

> On 19 Jan 2021, at 10:58, Loa Andersson <loa.pi.nu@gmail.com> wrote:
> 
> Rskesh,
> 
> I agree making it mpls generic. Actually looking at it is pretty close to that, with minor edits it is possible to read the references to SR as examples. 
> 
> We should move this discussion to the working group mailing list. 
> 
> Rakesh, 
> Can send a mail to the list, outlining what we agreed to and ask for comments?
> 
> /Loa
> 
> Sent from my iPhone
> 
>>> On 19 Jan 2021, at 05:52, Rakesh Gandhi (rgandhi) <rgandhi=40cisco.com@dmarc.ietf.org> wrote:
>>> 
>> 
>> Hi Stewart,
>>  
>> Thanks for the suggestion. Agree with making this generic to MPLS and not specific to SR-MPLS.
>>  
>> Thanks,
>> Rakesh
>>  
>>  
>> From: Stewart Bryant <stewart.bryant@gmail.com>
>> Date: Monday, January 18, 2021 at 10:39 AM
>> To: Mach Chen <mach.chen@huawei.com>
>> Cc: Stewart Bryant <stewart.bryant@gmail.com>, Eric Gray <eric.gray@ericsson.com>, loa Andersson <loa@pi.nu>, Greg Mirsky <gregimirsky@gmail.com>, mpls <mpls@ietf.org>, Rakesh Gandhi (rgandhi) <rgandhi=40cisco.com@dmarc.ietf.org>, mpls-chairs <mpls-chairs@ietf.org>, draft-gandhi-mpls-ioam-sr@ietf.org <draft-gandhi-mpls-ioam-sr@ietf.org>
>> Subject: Re: [mpls] MPLS-RT Review of draft-gandhi-mpls-ioam-sr-04
>> 
>> Hi Mach
>> 
>> It is as much a question for the WG given that this is up for adoption.
>> 
>> In all other aspects MPLS-SR inherits everything from MPLS so why would it not do so here?
>> 
>> Also given that we want iOAM for SR why would we not want it for MPLS and associated technologies such as PW and VPN as well?
>> 
>> So my view is not to make a special case for SR and then have the complexity of introducing it to base MPLS, but instead solve this for MPLS and use it everywhere.
>> 
>> Is there something special about the SR case that I am missing here?
>> 
>> - Stewart
>> 
>> 
>> 
>> > On 12 Jan 2021, at 03:18, Mach Chen <mach.chen@huawei.com> wrote:
>> > 
>> > Hi Stewart,
>> > 
>> > I guess your questions are for the authors of the draft, I will let the authors to answer the questions :-)
>> > 
>> > Best regards,
>> > Mach
>> > 
>> >> -----Original Message-----
>> >> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
>> >> Sent: Tuesday, January 12, 2021 3:29 AM
>> >> To: Mach Chen <mach.chen@huawei.com>
>> >> Cc: Eric Gray <eric.gray@ericsson.com>; Loa Andersson <loa@pi.nu>; Greg
>> >> Mirsky <gregimirsky@gmail.com>; mpls <mpls@ietf.org>; Rakesh Gandhi
>> >> (rgandhi) <rgandhi=40cisco.com@dmarc.ietf.org>; mpls-chairs
>> >> <mpls-chairs@ietf.org>; draft-gandhi-mpls-ioam-sr@ietf.org
>> >> Subject: Re: [mpls] MPLS-RT Review of draft-gandhi-mpls-ioam-sr-04
>> >> 
>> >> I have a slightly more fundamental question.
>> >> 
>> >> Why are we specifying this for sr?
>> >> 
>> >> Surely we should specify it for MPLS  and have SR inherit that?
>> >> 
>> >> Also what happens if the MPLS payload is a PW or Detnet or something else
>> >> defined to be immediately below the bottom label?
>> >> 
>> >> Stewart
>> 
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls