Re: [mpls] [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths
John E Drake <jdrake@juniper.net> Thu, 16 November 2017 13:18 UTC
Return-Path: <jdrake@juniper.net>
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 B3FCC129526; Thu, 16 Nov 2017 05:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 JBuFlQZ1YF6t; Thu, 16 Nov 2017 05:18:13 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB9F5120726; Thu, 16 Nov 2017 05:18:12 -0800 (PST)
Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id vAGCO9ZT026736; Thu, 16 Nov 2017 04:28:12 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=2NCUBmm4Tf4v5bFwCL6USgytVWqXkLB9gYHBILW9VjM=; b=KlCOxdM39k8iud7XoWv7x7ijdUiOXZwyJgW9On6OKLMLVTAogCq8WT6yLEBjYVtrpU9Z Snnr7k3tvct7Qh/MnaLklBcf6o98TJxaAmn5KdYsUZMNh2OaLz8kK+HX3bAtLXz9kDGF zJpuVI+sYAsb7BGyb9uZ4Ri/cWPcYwaOtz96bsI8Kdb9kTPzO6A/HRgTeG+NCjgv/BLL VMLao5itHc24t7tcEwgqVFhQWoSj5c6g2W7pYENAps4eWQ9hUZgQKPloD5jKQBXMJQRE x1UeY+6h0UogjtEY7AoeyfgAiKlKBfaxzMwmHynYG3oCC0uVAzsUuNhcUOI8VC6jfwEv Eg==
Received: from nam02-cy1-obe.outbound.protection.outlook.com (mail-cys01nam02lp0052.outbound.protection.outlook.com [207.46.163.52]) by mx0b-00273201.pphosted.com with ESMTP id 2e99uv039v-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 16 Nov 2017 04:28:12 -0800
Received: from DM5PR05MB3545.namprd05.prod.outlook.com (10.174.242.150) by DM5PR05MB3545.namprd05.prod.outlook.com (10.174.242.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.239.4; Thu, 16 Nov 2017 12:28:10 +0000
Received: from DM5PR05MB3545.namprd05.prod.outlook.com ([10.174.242.150]) by DM5PR05MB3545.namprd05.prod.outlook.com ([10.174.242.150]) with mapi id 15.20.0239.004; Thu, 16 Nov 2017 12:28:10 +0000
From: John E Drake <jdrake@juniper.net>
To: "Shah, Himanshu" <hshah@ciena.com>, Mach Chen <mach.chen@huawei.com>, "Zafar Ali (zali)" <zali@cisco.com>, Greg Mirsky <gregimirsky@gmail.com>, "draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org" <draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths
Thread-Index: AQHTXj7n5TRYZZG6f0OmPllyjgaJFKMWWYGAgAABzICAAJRx8A==
Date: Thu, 16 Nov 2017 12:28:10 +0000
Message-ID: <DM5PR05MB354571FD8B93FDBF15F23773C72E0@DM5PR05MB3545.namprd05.prod.outlook.com>
References: <CA+RyBmUHAkuA3o-LpHhMwCbkh0k+emt9OZ3B8Njj2h=jaasTZw@mail.gmail.com> <3B1EE673-044F-4E47-9C56-6FF360905C58@cisco.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE2922ADFD8@dggeml510-mbs.china.huawei.com> <32821369-051F-41CE-9CC3-FC34A6D4547E@ciena.com>
In-Reply-To: <32821369-051F-41CE-9CC3-FC34A6D4547E@ciena.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR05MB3545; 6:IkC9ORyAk76Oa9k37P3Sktoipq1Onf7jrAGwHDvn51OLoLhPX6DPmpAX3/hm6hBRKpi41yqaG8lvhUwfjtrVXRtooZQkQrElu3hER0e/ejpjJBY4kyFqoEZ4qAJb3RYfjbFDcdVYe3KllqlgkGPvy4e042T009lm08ToXD+IsbCYxel0si8LnvF46cxQJPmToXZBd0d1u37ARa3TtCbzcX24Ojg9U9465WGxxsToCd5GQ/KbY/WsZRFI+853iuuFG1l39IjPee0BSbieSN2gA+Wu8KNVHFqQkDH+KL8sjTz+0I10P3YbDJXANhwgPUJ6SD7mzzLdYDQsalBdhCciJ24inJXXQU2FgKb8AQ49EAE=; 5:OqK6Sd8Fa9v/cZcEv4o6N9Xa4hruFivBaTpEKt1B0MS0+2DbUH06FhJP0urbnMceRg61Cp0upQsDiF0ig58piPqnM3FpT9zBDbnIjwx5/mR0eXlYrRDQlNqLYfgbu+RR3f3lxQWzy/wnH9yTnCTFiUGZv3DyoPH7pzz5WSr1qr4=; 24:4ou1Cwa/jeBwNQRn3j8K3/6gxuwKH9+cn/kxi2dfbsbQ5D0mvdZykgb/lzdW0gpSFCs1aQG9UwatuiYeL/qZLgsVcA4Dcuv4/hwOPF2tOXQ=; 7:H0VGzgrrc92AJHlbwgatyEdmMtRxzHTOsyx0waVT9owuZmmRsbxjssKQ5euqgGkgXHLyQkzKgcKQ7inwphov1l+oic2HRYPv7B7Yj58iuFmcB3G/RU89mhFAzZyy5qJILMWcH69t0I+GBJfEoKIYqjUJemFohlkNrsIWRTCXa4b9BmpUrCmoMtyb+MHvwJiH5PK1nls7j/NziJ0QUpNJudDClCEoMTu1yhvrW553E4tD1UfkcXeZ1sBFLBDEsNoZ
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 20a6e999-dcb8-4766-1a47-08d52ced7fad
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(48565401081)(2017052603258); SRVR:DM5PR05MB3545;
x-ms-traffictypediagnostic: DM5PR05MB3545:
x-microsoft-antispam-prvs: <DM5PR05MB354597C972A4B12CD8076219C72E0@DM5PR05MB3545.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162)(50582790962513)(95692535739014)(227612066756510)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(100000703101)(100105400095)(3231022)(10201501046)(6055026)(6041248)(20161123558100)(20161123562025)(20161123555025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DM5PR05MB3545; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DM5PR05MB3545;
x-forefront-prvs: 0493852DA9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(51444003)(199003)(189002)(2501003)(14454004)(966005)(105586002)(106356001)(102836003)(110136005)(97736004)(478600001)(316002)(33656002)(5660300001)(236005)(229853002)(39060400002)(6246003)(6116002)(2950100002)(3280700002)(6436002)(53936002)(54896002)(15650500001)(2420400007)(25786009)(7696004)(3846002)(6306002)(790700001)(99286004)(3660700001)(8936002)(9686003)(54356999)(2906002)(68736007)(77096006)(6506006)(7110500001)(81166006)(81156014)(8676002)(230783001)(345774005)(2900100001)(189998001)(76176999)(2201001)(66066001)(93886005)(7736002)(101416001)(74316002)(606006)(86362001)(50986999)(53546010)(55016002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3545; H:DM5PR05MB3545.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR05MB354571FD8B93FDBF15F23773C72E0DM5PR05MB3545namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 20a6e999-dcb8-4766-1a47-08d52ced7fad
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Nov 2017 12:28:10.3402 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3545
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-11-16_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1711160169
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/n3QjWYxRwJBZStV-zouEsVUEw5o>
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 13:18:16 -0000
Himanshu, Good point. We also need to be able to turn on and off packet marking by the ingress routers. Yours Irrespectively, John From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Shah, Himanshu Sent: Wednesday, November 15, 2017 10:35 PM To: Mach Chen <mach.chen@huawei.com>; Zafar Ali (zali) <zali@cisco.com>; Greg Mirsky <gregimirsky@gmail.com>; draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org; mpls@ietf.org; spring@ietf.org Subject: Re: [mpls] [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths I agree with some of the opinions expressed here wrt transit LSR not completely immune of statelessness; lightweight (counters only) or otherwise. Another point that Greg made is important to underline. If such radioactive flows generate counters at LSRs, there needs to be a way to clear them, If intent of the scheme is to use it for spotlighting only. Thanks, Himanshu From: spring <spring-bounces@ietf.org<mailto:spring-bounces@ietf.org>> on behalf of Mach Chen <mach.chen@huawei.com<mailto:mach.chen@huawei.com>> Date: Thursday, November 16, 2017 at 11:29 AM To: 'Zafar ' <zali@cisco.com<mailto:zali@cisco.com>>, Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>, "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: Re: [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dspring-2Dsegment-2Drouting-2D13&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=4ShnRNbDzoyjKbbNOE-PVSsfnSVi8F_DypuBCQKeBg4&s=f7J_nBpiwUgdnKFZwyOikcSLxaC1P3Jl5Rt7977hqeo&e=>, 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
- [mpls] Special purpose labels in draft-hegde-spri… Greg Mirsky
- Re: [mpls] [spring] Special purpose labels in dra… Zafar Ali (zali)
- Re: [mpls] [spring] Special purpose labels in dra… Stewart Bryant
- Re: [mpls] [spring] Special purpose labels in dra… Xuxiaohu
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Greg Mirsky
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Greg Mirsky
- Re: [mpls] [spring] Special purpose labels in dra… Greg Mirsky
- Re: [mpls] [spring] Special purpose labels in dra… ShaoWen Ma
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Jeff Tantsura
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Xuxiaohu
- Re: [mpls] [spring] Special purpose labels in dra… Jeff Tantsura
- Re: [mpls] [spring] Special purpose labels in dra… Shraddha Hegde
- Re: [mpls] [spring] Special purpose labels in dra… David Allan I
- Re: [mpls] [spring] Special purpose labels in dra… Mach Chen
- Re: [mpls] [spring] Special purpose labels in dra… Xuxiaohu
- Re: [mpls] [spring] Special purpose labels in dra… Mach Chen
- Re: [mpls] [spring] Special purpose labels in dra… Shah, Himanshu
- Re: [mpls] [spring] Special purpose labels in dra… Xuxiaohu
- Re: [mpls] [spring] Special purpose labels in dra… Mach Chen
- Re: [mpls] [spring] Special purpose labels in dra… Mach Chen
- Re: [mpls] [spring] Special purpose labels in dra… Chengli (IP Technology Research)
- Re: [mpls] [spring] Special purpose labels in dra… Jeff Tantsura
- Re: [mpls] [spring] Special purpose labels in dra… Xuxiaohu
- Re: [mpls] [spring] Special purpose labels in dra… Xuxiaohu
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Alexander Vainshtein
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Zafar Ali (zali)
- Re: [mpls] [spring] Special purpose labels in dra… Greg Mirsky
- Re: [mpls] [spring] Special purpose labels in dra… Alexander Vainshtein
- Re: [mpls] [spring] Special purpose labels in dra… Ruediger.Geib
- Re: [mpls] [spring] Special purpose labels in dra… Greg Mirsky
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Alexander Vainshtein
- [mpls] Whether both E2E and SPME performance meas… Mach Chen
- Re: [mpls] [spring] Special purpose labels in dra… Alexander Vainshtein
- Re: [mpls] Whether both E2E and SPME performance … David Allan I
- Re: [mpls] Whether both E2E and SPME performance … Mach Chen
- Re: [mpls] [spring] Special purpose labels in dra… Greg Mirsky
- Re: [mpls] Whether both E2E and SPME performance … Ruediger.Geib
- Re: [mpls] [spring] Special purpose labels in dra… stephane.litkowski
- Re: [mpls] Whether both E2E and SPME performance … Robert Raszuk
- Re: [mpls] Whether both E2E and SPME performance … Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Alexander Vainshtein
- Re: [mpls] Whether both E2E and SPME performance … John E Drake
- Re: [mpls] [spring] Special purpose labels in dra… John E Drake
- Re: [mpls] [spring] Special purpose labels in dra… John E Drake
- Re: [mpls] Whether both E2E and SPME performance … Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Alexander Vainshtein
- Re: [mpls] [spring] Whether both E2E and SPME per… Alexander Vainshtein
- Re: [mpls] Whether both E2E and SPME performance … John E Drake
- Re: [mpls] [spring] Special purpose labels in dra… John E Drake
- Re: [mpls] [spring] Special purpose labels in dra… John E Drake
- Re: [mpls] Whether both E2E and SPME performance … John E Drake
- Re: [mpls] [spring] Whether both E2E and SPME per… John E Drake
- Re: [mpls] [spring] Special purpose labels in dra… John E Drake
- Re: [mpls] [spring] Special purpose labels in dra… John E Drake
- Re: [mpls] [spring] Whether both E2E and SPME per… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Mach Chen
- Re: [mpls] [spring] Special purpose labels in dra… Mach Chen
- Re: [mpls] [spring] Whether both E2E and SPME per… John E Drake
- Re: [mpls] [spring] Whether both E2E and SPME per… John E Drake
- Re: [mpls] [spring] Whether both E2E and SPME per… Robert Raszuk
- Re: [mpls] [spring] Whether both E2E and SPME per… Alexander Vainshtein
- Re: [mpls] [spring] Whether both E2E and SPME per… Greg Mirsky
- Re: [mpls] [spring] Whether both E2E and SPME per… Mach Chen
- Re: [mpls] [spring] Special purpose labels in dra… Stewart Bryant
- Re: [mpls] [spring] Whether both E2E and SPME per… Greg Mirsky
- [mpls] Fwd: Re: [spring] Special purpose labels i… Stewart Bryant
- Re: [mpls] [spring] Special purpose labels in dra… Jeff Tantsura
- Re: [mpls] Fwd: Re: [spring] Special purpose labe… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Mach Chen
- Re: [mpls] Fwd: Re: [spring] Special purpose labe… Stewart Bryant
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… John E Drake
- Re: [mpls] Fwd: Re: [spring] Special purpose labe… Uma Chunduri
- Re: [mpls] [spring] Special purpose labels in dra… Stewart Bryant
- Re: [mpls] [spring] Special purpose labels in dra… Stewart Bryant
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- [mpls] measurement requirements (was Re: [spring]… Martin Horneffer
- Re: [mpls] [spring] Special purpose labels in dra… Martin Horneffer
- Re: [mpls] [spring] Special purpose labels in dra… Zafar Ali (zali)
- Re: [mpls] [spring] measurement requirements (was… Zafar Ali (zali)
- Re: [mpls] [spring] Special purpose labels in dra… Adrian Farrel
- Re: [mpls] [spring] Special purpose labels in dra… John E Drake
- Re: [mpls] [spring] Special purpose labels in dra… Zafar Ali (zali)
- Re: [mpls] [spring] Special purpose labels in dra… Zafar Ali (zali)
- Re: [mpls] [spring] Special purpose labels in dra… Greg Mirsky
- Re: [mpls] [spring] Special purpose labels in dra… Zafar Ali (zali)
- Re: [mpls] [spring] Special purpose labels in dra… Greg Mirsky
- Re: [mpls] [spring] Special purpose labels in dra… Zafar Ali (zali)
- Re: [mpls] [spring] Special purpose labels in dra… Adrian Farrel
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Zafar Ali (zali)
- Re: [mpls] [spring] Special purpose labels in dra… Stewart Bryant
- Re: [mpls] [spring] Special purpose labels in dra… Martin Horneffer
- Re: [mpls] [spring] Special purpose labels in dra… Jeff Tantsura
- Re: [mpls] [spring] Special purpose labels in dra… Robert Raszuk
- Re: [mpls] [spring] Special purpose labels in dra… Carlos Pignataro (cpignata)
- Re: [mpls] [spring] Special purpose labels in dra… Carlos Pignataro (cpignata)
- Re: [mpls] [spring] Special purpose labels in dra… Carlos Pignataro (cpignata)
- Re: [mpls] [spring] Special purpose labels in dra… Greg Mirsky
- Re: [mpls] [spring] Special purpose labels in dra… Carlos Pignataro (cpignata)