Re: [mpls] [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths

Mach Chen <mach.chen@huawei.com> Thu, 16 November 2017 04:02 UTC

Return-Path: <mach.chen@huawei.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 195C9127010; Wed, 15 Nov 2017 20:02:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 5IDH2VBH2Gli; Wed, 15 Nov 2017 20:02:02 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 40ECE124BE8; Wed, 15 Nov 2017 20:02:02 -0800 (PST)
Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id C1343567C29BA; Thu, 16 Nov 2017 04:01:59 +0000 (GMT)
Received: from DGGEML403-HUB.china.huawei.com (10.3.17.33) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 16 Nov 2017 04:02:00 +0000
Received: from DGGEML510-MBS.china.huawei.com ([169.254.3.195]) by DGGEML403-HUB.china.huawei.com ([fe80::74d9:c659:fbec:21fa%31]) with mapi id 14.03.0361.001; Thu, 16 Nov 2017 12:01:52 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, "Zafar Ali (zali)" <zali@cisco.com>, Greg Mirsky <gregimirsky@gmail.com>, draft-hegde-spring-traffic-accounting-for-sr-paths <draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org>, mpls <mpls@ietf.org>, spring <spring@ietf.org>
Thread-Topic: [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths
Thread-Index: AQHTXj70Q7+fGT1teEWvdiTu0xFRa6MWWYsQ//+AfACAAIg8wA==
Date: Thu, 16 Nov 2017 04:01:52 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE2922AE4DD@dggeml510-mbs.china.huawei.com>
References: <CA+RyBmUHAkuA3o-LpHhMwCbkh0k+emt9OZ3B8Njj2h=jaasTZw@mail.gmail.com> <3B1EE673-044F-4E47-9C56-6FF360905C58@cisco.com>, <F73A3CB31E8BE34FA1BBE3C8F0CB2AE2922ADFD8@dggeml510-mbs.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE3047D266@NKGEML515-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE3047D266@NKGEML515-MBS.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.52.35.212]
Content-Type: multipart/alternative; boundary="_000_F73A3CB31E8BE34FA1BBE3C8F0CB2AE2922AE4DDdggeml510mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/aRldmpsWvn9c_zUm_4qSVu-Z69Q>
Subject: Re: [mpls] [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 16 Nov 2017 04:02:05 -0000

IMHO, OAM is a fundamental function that is for an operator to running their SR network.

I hope we’d better not repeat the philosophy debate here. We should focus on the specific use case/requirement/technologies.

Best regards,
Mach

From: Xuxiaohu
Sent: Thursday, November 16, 2017 11:52 AM
To: Mach Chen; Zafar Ali (zali); Greg Mirsky; draft-hegde-spring-traffic-accounting-for-sr-paths; mpls; spring
Subject: RE: [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths


The beauty of MPLS-SR is less states are required. To keep it as beautiful as possible, it'd better for us to overcome the impulsion of adding more and more complicated functions.

Best regards,
Xiaohu


________________________________
徐小虎 Xuxiaohu
M:+86-13910161692<tel:+86-13910161692>
E:xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>
产品与解决方案-网络战略与业务发展部
Products & Solutions-Network Strategy & Business Development Dept
发件人: Mach Chen
收件人: Zafar Ali (zali)<zali@cisco.com<mailto:zali@cisco.com>>;Greg Mirsky<gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>;draft-hegde-spring-traffic-accounting-for-sr-paths<draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org<mailto:draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org>>;mpls<mpls@ietf.org<mailto:mpls@ietf.org>>;spring<spring@ietf.org<mailto:spring@ietf.org>>
主题: Re: [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths
时间: 2017-11-16 11:29:12

Hi Zafar,

Given that SR supports SID Binding, states only maintained at ingress is not very true.

Best regards,
Mach

From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Zafar Ali (zali)
Sent: Thursday, November 16, 2017 2:24 AM
To: Greg Mirsky; draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org<mailto:draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org>; mpls@ietf.org<mailto:mpls@ietf.org>; spring@ietf.org<mailto:spring@ietf.org>
Subject: Re: [mpls] [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths

Hi,

This draft breaks the SR architecture. I am quoting a snippet from abstract of SR Architecture document https://tools.ietf.org/html/draft-ietf-spring-segment-routing-13, which states:
“SR allows to enforce a flow through any topological path while maintaining per-flow state only at the ingress nodes to the SR domain.”

In addition to creating states at transit and egress nodes, the procedure also affects the data plane and makes it unscalable. It also makes controller job much harder and error prune. In summary, I find the procedure very complex and unscalable.

Thanks

Regards … Zafar


From: spring <spring-bounces@ietf.org<mailto:spring-bounces@ietf.org>> on behalf of Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>
Date: Wednesday, November 15, 2017 at 11:10 AM
To: "draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org<mailto:draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org>" <draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org<mailto:draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org>>, "mpls@ietf.org<mailto:mpls@ietf.org>" <mpls@ietf.org<mailto:mpls@ietf.org>>, "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>
Subject: [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths

Hi Shraddha,
thank you for very well written and thought through draft. I have these questions I'd like to discuss:

  *   Have you thought of using not one special purpose label for both SR Path Identifier and SR Path Identifier+Source SID cases but request two special purpose labels, one for each case. Then the SR Path Identifier would not have to lose the bit for C flag.
  *   And how you envision to collect the counters along the path? Of course, a Controller may query LSR for all counters or counters for the particular flow (SR Path Identifier+Source SID). But in addition I'd propose to use in-band mechanism, perhaps another special purpose label, to trigger the LSR to send counters of the same flow with the timestamp out-band to the predefined Collector.
  *   And the last, have you considered ability to flush counters per flow. In Scalability Considerations you've stated that counters are maintained as long as collection of statistics is enabled. If that is on the node scope, you may have to turn off/on the collection to flush off some old counters. I think that finer granularity, per flow granularity would be useful for operators. Again, perhaps the flow itself may be used to signal the end of the measurement and trigger release of counters.
Regards,
Greg