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

Loa Andersson <loa.pi.nu@gmail.com> Tue, 19 January 2021 02:58 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 C07283A1082; Mon, 18 Jan 2021 18:58:14 -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 6oj6c_SFrxcS; Mon, 18 Jan 2021 18:58:13 -0800 (PST)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 ED7BB3A107C; Mon, 18 Jan 2021 18:58:12 -0800 (PST)
Received: by mail-pl1-x62a.google.com with SMTP id y8so9687741plp.8; Mon, 18 Jan 2021 18:58:12 -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=qn3bZv00rC7r4e6kj+3zr4Pn1itaLJQZwJ0vvrKAeSs=; b=gRu0oM30oxklI0JTpNvp87DjiJNEHNrfTqqt1ZXboRegXJtH5ry5LArfhKFgcfM0Qq vQX8bbJFwY2Orwlx7wk2VV0dMdrwCQf2WDOedVcIeC3SNmUikcOzJQZutIrKCGxgUBEk ZBwE9Fb7puEVjeQKGaTIARWpOO+iLBYaUslS1RDLuc5yPMuW6JMV9KTbDEbfSwkrO9PC /uE0jB6KDvp2yd5Q4evNKYbl0vH9lv32QQ/if/7f29K9mQ0/6r6KI+dk5ag1JCPBZbHa rTz0AthIBCrCKtOkOgcm2Zv1h1X5P7tj76QsO0Os07zFZswcohPuzmqFD1C5dVd+y/UA 9/Ag==
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=qn3bZv00rC7r4e6kj+3zr4Pn1itaLJQZwJ0vvrKAeSs=; b=MjFSNHVpdMDjEwMULU5vfJWCKjhbcTZCnO9CS3zjhHqgjxvbkxUrXXCOeF0KCXldn2 eC1PW1wAoAhZs7dMEZmClKAVn6dDAFAzECmMOYIKCBOZCVuH4lUjA2Kf904zYdytcBxv 62mN9EZrNxL8T9pSsgL8uAUyUUk8Yez1IuWdEL7KkqGJ5YLsQiXvooDkfXEyBXSKuCuS /SE37mb8XDSXsXT4DZtxJCDWlM16jkwxUZqSkEHUGIv6804sB5bR+MzRS1oP0bC1WRzw fkbdS27Bdk9/nDSsL3WodKbfHvIjA4S2hWwJ8C5nB51rDsZHc1vzDKSSCYcHDGF6zk17 lThw==
X-Gm-Message-State: AOAM531rqQNxBbdQS2jXMeNOn5/yHl/Kzt4KEBij1uKonsW6pkCj9jb4 4IGKnliUXAJyCNXhlP7C4eY=
X-Google-Smtp-Source: ABdhPJzTgWkg77GN5IEdF28Ph+V5FkDliuuvYN6z+vsCFKAy8fcIb97iTECUjkQos0Y5YCt3bTP1AA==
X-Received: by 2002:a17:90a:8508:: with SMTP id l8mr2525357pjn.131.1611025092396; Mon, 18 Jan 2021 18:58:12 -0800 (PST)
Received: from [192.168.1.31] ([124.104.17.232]) by smtp.gmail.com with ESMTPSA id l4sm709023pju.26.2021.01.18.18.58.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Jan 2021 18:58:11 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-2296A0B6-F89B-4646-B547-5DF23BF7C112"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Loa Andersson <loa.pi.nu@gmail.com>
In-Reply-To: <DM6PR11MB3115D423D85F84A3A1AD0547BFA40@DM6PR11MB3115.namprd11.prod.outlook.com>
Date: Tue, 19 Jan 2021 10:58:07 +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: <9A29135C-0660-4016-903A-835004B5FF9D@gmail.com>
References: <DM6PR11MB3115D423D85F84A3A1AD0547BFA40@DM6PR11MB3115.namprd11.prod.outlook.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/EYaQsIyi7E_AaE2lv_669c7GMTc>
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 02:58:15 -0000

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