IETF Logo Mail Archive

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

Stewart Bryant <stewart.bryant@gmail.com> Mon, 18 January 2021 15:38 UTC

Return-Path: <stewart.bryant@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 E60303A0839; Mon, 18 Jan 2021 07:38:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 00AmJ-gCHZbq; Mon, 18 Jan 2021 07:38:56 -0800 (PST)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 890773A0812; Mon, 18 Jan 2021 07:38:56 -0800 (PST)
Received: by mail-wr1-x435.google.com with SMTP id v15so13232347wrx.4; Mon, 18 Jan 2021 07:38:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9czXUsYc3mDfx3SKIZTmGMfC327a+kCIxMHIYXe0RF0=; b=l053GHEUxH4p6jOJ39CtmWUVgJtcm6YITZ+rYUvuyxpwjHc+3ZW2Zq054stWhHWL9F ESRkcrOtIdcoTA0+oW2ywgodgc2KO9JIbstSvzP14yuR7F7aTGBKgAE+C6FwwekKluxY wxBQiK7C8RLcCtvoGjFxzs3LaZzjTg9x0AuvkQ8W9VuiEpGHUNC/gOKFfnqnD28IsCO8 +TerYyuVNbTNTdFa7myThZDkihQIlHIXSM+ezXSwO2JdimHbVhqNbgiZTgyD0oD0FJB0 D+1LsCSYPkcoDIw0LgOVQF0Ucvo8MFColVA9WgGj/ffmYh4GmrB6cK6OZZPEO551RUUe OAtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9czXUsYc3mDfx3SKIZTmGMfC327a+kCIxMHIYXe0RF0=; b=I6TVEp9TgTJiUXV+sENgFeeTyUYs2WTwPfzpDd6YfPV+UfjXcSJB6fero1nFKUWWWh J1ujDZP7sTuFfWGwciEzol3dFuUmCbMsU1y+J3SclXzN/R/ypoMKLsCrdJXQnew8wtZc orEJgb3Fu4cR73Vi2AunFVv2NiwjBM4GaomHzHKsMqEZMHwsEx4bQ0mfsDKf4ll+Sr8G Qpn17izaX638uJIRZzKPyrGE0QVFAP7mGfAENTs+ecNl9U4cFPBH7fRCrfsXGlIXwvip rQ2scUj5vOJn528A7my5P2u3v5ZPIDpJoVxvPKPIk3l8UGKHz49Fzx1Gkt5mcsJ/Sj01 RwzA==
X-Gm-Message-State: AOAM532mFMhm6MsnBNmJ+gAus+BK0kbjhR/BSFYWFQuLlZDDDFYTXgnO 4nrBUyuZL5v1qYsyg0sjuMVDnbfSFGK4fA==
X-Google-Smtp-Source: ABdhPJzYcGQf4NZF8ib4Jpe2yaGDfwOvAtdINZuF5crpLRW1Yywg0ilmO6g5aT+fDDonybwxcefksg==
X-Received: by 2002:a5d:6884:: with SMTP id h4mr86929wru.174.1610984334988; Mon, 18 Jan 2021 07:38:54 -0800 (PST)
Received: from broadband.bt.com ([2a00:23c5:3395:c901:e820:e4ca:2b49:5533]) by smtp.gmail.com with ESMTPSA id g132sm13669390wmg.2.2021.01.18.07.38.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Jan 2021 07:38:54 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE2980F43C6@dggeml530-mbs.china.huawei.com>
Date: Mon, 18 Jan 2021 15:38:53 +0000
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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1111CEC7-B11D-4A22-AFEA-DB9F90FA0B82@gmail.com>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE2980E847D@dggeml530-mbs.china.huawei.com> <31E0C5A4-1EA3-486F-8BC4-E4E9AA107D95@gmail.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE2980F43C6@dggeml530-mbs.china.huawei.com>
To: Mach Chen <mach.chen@huawei.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/ZZ_gb7bzydWJD8_s7Cuos0dqsbA>
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: Mon, 18 Jan 2021 15:38:58 -0000

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

v2.23.0 | Report a Bug | By Email