Re: [Isis-wg] =?UTF-8?B?562U5aSN?=: WG Last Call for draft-ietf-isis-segment-routing-msd-07

Jeff Tantsura <jefftant.ietf@gmail.com> Thu, 21 December 2017 21:21 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6ECB12D7E2; Thu, 21 Dec 2017 13:21:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 Nloe1Y62DdhA; Thu, 21 Dec 2017 13:21:38 -0800 (PST)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 D55BD1275FD; Thu, 21 Dec 2017 13:21:37 -0800 (PST)
Received: by mail-oi0-x22e.google.com with SMTP id f69so17722584oig.10; Thu, 21 Dec 2017 13:21:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :mime-version:content-transfer-encoding; bh=B0TVfA2TrjOe5Ab6XvGEkv93QBdTu0FPUcSo7AYUUzk=; b=uez/j2gKsBp7lpcBn9u+KHBG+b8seauk3H8rlXBoo/aHa3oBu4ds+cQppXoLEz8s0O UqQNxhuF1pFJvIw+BlShK/1N9xYZTyM6whQRV+EarexyCEig9zae4AKjtwYeSDYU8G4v L0b3u/RsIwN8jeDE2rvV6h5oaLf028pPs7tT+g0H6LsezLtIY/XZW70HGUbcM+AL5Kra 16gxFVLf8uc45Rjdy6vgaQ8edU/OM0zPGcfQ718Kd+dUN50wCv7j4+CTH3QQvThLT4gp mGNSs7ifMksrMQRcDwKqqwuBm8Zg5N10oWg2MkfEvcUNh676B1hrCGZubyjbeg4YfAFs 3Cbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:mime-version:content-transfer-encoding; bh=B0TVfA2TrjOe5Ab6XvGEkv93QBdTu0FPUcSo7AYUUzk=; b=qe9u+p2AmiD4Dvbku2iojSCbH+VbJ62cmQjOxAQuP31D/KGQBv+RWY6nC1RnkmNCD1 ZBBNAxXmePq8GQg+S4mddgDP3tHDRWOyYokysaopRyqNLHV+F4YPaVnUdWr+Oe4CVLme O1ewS0mRbNq7JQOxYxYzthTv9f40vAnR3Q9wikfU6Q6na7//ZwwtUqT9okc5NI5fLv2m bGjTlnocVAUuSblf1Ehh8fRRJeOKS8ZhcC9f9WhKF7hDE/6u/XSYoPcSaQuJ8oduHNq1 rStV1kxFiunSZ6o8y09YzzjF++3khRdep04UQ+3l3Yuj4Ki3J9NJsw/HrnXF8v8F9a2B vJ9w==
X-Gm-Message-State: AKGB3mKTY3CshEtHliI68L0r7HBD6VcZFdehztf/RLuWvj+xhkyLlCKx mw6Kj7pe+d6/AJGX4LAqkeM=
X-Google-Smtp-Source: ACJfBotWgXFrv+6Yx256R1+cjkOnIqOnMZQ4AtBel70FPhgDUZpQte8MMy5QLcR00i7mhKa1O+orZg==
X-Received: by 10.202.182.196 with SMTP id g187mr9097118oif.216.1513891297023; Thu, 21 Dec 2017 13:21:37 -0800 (PST)
Received: from [100.65.101.83] ([206.16.17.196]) by smtp.gmail.com with ESMTPSA id q13sm5558755ota.42.2017.12.21.13.21.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Dec 2017 13:21:36 -0800 (PST)
User-Agent: Microsoft-MacOutlook/f.29.0.171205
Date: Thu, 21 Dec 2017 13:21:31 -0800
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Ketan Talaulikar (ketant)" <ketant@cisco.com>, Christian Hopps <chopps@chopps.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
CC: "isis-ads@ietf.org" <isis-ads@ietf.org>, "draft-ietf-isis-segment-routing-msd@ietf.org" <draft-ietf-isis-segment-routing-msd@ietf.org>
Message-ID: <41DCA7FB-82D8-479E-B567-56BB8516BA5E@gmail.com>
Thread-Topic: =?UTF-8?B?562U5aSN?=: [Isis-wg] WG Last Call for draft-ietf-isis-segment-routing-msd-07
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/K2WjlcN6U82R_Cf99bVKl28xCVw>
Subject: Re: [Isis-wg] =?UTF-8?B?562U5aSN?=: WG Last Call for draft-ietf-isis-segment-routing-msd-07
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Dec 2017 21:21:40 -0000

Xuxiaohu,

To clarify:
The concept had been developed in both, in parallel, however PCEP implementation is limited (node only, PCC in question has to have PCEP sessions with the PCE), and this is clearly stated in the draft – if MSD is known from both sources (PCEP and IGP/BGP-LS) the later takes precedence. IGP drafts are the source of truth when it comes to semantics definitions.

Personally, I don’t see any confusion wrt name, all drafts have been around for quite some time, reviewed by many people, presented in academia and networking events, noone was ever confused…

I’m not sure about value of your proposal either, and I’d leave the decision what to use to people who are the consumers of the technology, those who are going to implement it (at least 3 MSD implementations are on their ways).

As the last point – we are not “considering” expanding, the draft is clear about the future extensions to come and encoding is done in a way to facilitate such extensions.  
This is the working group last call for the draft, not a discussion whether we should proceed with the technology:
If you see any technical problems with the solution proposed – I’d be the first to listen to you and address them!

Happy holidays!

Cheers,
Jeff

-----Original Message-----
From: Xuxiaohu <xuxiaohu@huawei.com>
Date: Wednesday, December 20, 2017 at 18:40
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>om>, "Ketan Talaulikar (ketant)" <ketant@cisco.com>om>, Christian Hopps <chopps@chopps.org>rg>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Cc: "isis-ads@ietf.org" <isis-ads@ietf.org>rg>, "draft-ietf-isis-segment-routing-msd@ietf.org" <draft-ietf-isis-segment-routing-msd@ietf.org>
Subject: 答复: [Isis-wg] WG Last Call for draft-ietf-isis-segment-routing-msd-07
Resent-From: <alias-bounces@ietf.org>
Resent-To: <jefftant.ietf@gmail.com>om>, <uma.chunduri@huawei.com>om>, <aldrin.ietf@gmail.com>om>, <ginsberg@cisco.com>
Resent-Date: Wed, 20 Dec 2017 18:40:16 -0800 (PST)

    Hi Les,
    
    If I understand it correctly, the MSD concept was originated from (https://tools.ietf.org/html/draft-ietf-pce-segment-routing-11#page-7) as described below:
    
    "The "Maximum SID Depth" (1
       octet) field (MSD) specifies the maximum number of SIDs (MPLS label
       stack depth in the context of this document) that a PCC is capable of
       imposing on a packet."
    
    Before considering expanding the semantics of the MSD concept as defined in the above PCE-SR draft, how about first considering renaming the capability of imposing the maximum number of labels so as to eliminate possible confusions, e.g., Writable Label-stack Depth (WLD) as opposed to the Readable Label-stack Depth (RLD) as defined in (https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc) and (https://tools.ietf.org/html/draft-ietf-isis-mpls-elc) ?
    
    Best regards,
    Xiaohu
    
    > -----邮件原件-----
    > 发件人: Isis-wg [mailto:isis-wg-bounces@ietf.org] 代表 Les Ginsberg (ginsberg)
    > 发送时间: 2017年12月21日 4:02
    > 收件人: Ketan Talaulikar (ketant); Christian Hopps; isis-wg@ietf.org
    > 抄送: isis-ads@ietf.org; draft-ietf-isis-segment-routing-msd@ietf.org
    > 主题: Re: [Isis-wg] WG Last Call for draft-ietf-isis-segment-routing-msd-07
    > 
    > Ketan -
    > 
    > Thanx for the comments.
    > I think we do want to allow MSD support for values other than imposition
    > values. We will revise the text so we are not restricted to only imposition cases.
    > 
    >   Les
    > 
    > 
    > > -----Original Message-----
    > > From: Ketan Talaulikar (ketant)
    > > Sent: Wednesday, December 20, 2017 1:51 AM
    > > To: Christian Hopps <chopps@chopps.org>rg>; isis-wg@ietf.org
    > > Cc: isis-ads@ietf.org; draft-ietf-isis-segment-routing-msd@ietf.org
    > > Subject: RE: [Isis-wg] WG Last Call for
    > > draft-ietf-isis-segment-routing-msd-07
    > >
    > > Hello,
    > >
    > > I support this document and would like to ask the authors and WG to
    > > consider if we can expand the scope of this draft to not just
    > > "imposition" of the SID stack but also other similar limits related to other
    > actions (e.g.
    > > reading, processing, etc.). With Segment Routing, we are coming across
    > > various actions that nodes need to do with the SID stack for different
    > > purposes and IMHO it would be useful to extend the MSD ability to
    > > cover those as they arise.
    > >
    > > Thanks,
    > > Ketan
    > >
    > > -----Original Message-----
    > > From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Christian
    > > Hopps
    > > Sent: 20 December 2017 14:03
    > > To: isis-wg@ietf.org
    > > Cc: isis-ads@ietf.org; draft-ietf-isis-segment-routing-msd@ietf.org
    > > Subject: [Isis-wg] WG Last Call for
    > > draft-ietf-isis-segment-routing-msd-07
    > >
    > >
    > > The authors have asked for and we are starting a WG Last Call on
    > >
    > >  https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-msd/
    > >
    > > which will last an extended 4 weeks to allow for year-end PTO patterns.
    > >
    > > An IPR statement exists:
    > >
    > >
    > > https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-is
    > > is-
    > > segment-routing-msd
    > >
    > > Authors please reply to the list indicating whether you are aware of
    > > any
    > > *new* IPR.
    > >
    > > Thanks,
    > > Chris.
    > >
    > > _______________________________________________
    > > Isis-wg mailing list
    > > Isis-wg@ietf.org
    > > https://www.ietf.org/mailman/listinfo/isis-wg
    > 
    > _______________________________________________
    > Isis-wg mailing list
    > Isis-wg@ietf.org
    > https://www.ietf.org/mailman/listinfo/isis-wg