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 12:32 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 4D34C129449; Thu, 16 Nov 2017 04:32:47 -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 lHRqvrTc2RLi; Thu, 16 Nov 2017 04:32:44 -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 803AC1293E8; Thu, 16 Nov 2017 04:32:44 -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 vAGCSvd5030572; Thu, 16 Nov 2017 04:32:19 -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=Mgr4hs86C5mW6UaP4FVsNXS9yLMvt5pLEmFOxwzuSN4=; b=vZbGhSZ1WXXvDiDa/CggLvS26hA0c/1Ne6rWPofOb5EBjZQWXzx5AEBRxOxw4zWWws6i 0gLBQ6S/Nkd55pPsdNqFfVpbb+aiXGUQyLq62iFMGf2U1rcnpSnfpCAA+pMKzLwIaRSv M4t8giHH5agz6j2S1Dzt3sUkBpdCzk0PaHSIofIO2M3Rg2NVjW8ECcyAxU9zeC6/FP3s Thsw1YdhqYBQb0ptMy0YF36Xml4X5hJ8es4Wd7ywJq1PVsXcvZSeAmUiow6eA+XS83sr Li4dyWG8V7v5zoiUA/PAejpt6lqKLcUqSiZfv4uQomRekJCh4VOAfj9mMIxLGhlhSv+e gg==
Received: from nam03-dm3-obe.outbound.protection.outlook.com (mail-dm3nam03lp0024.outbound.protection.outlook.com [207.46.163.24]) by mx0b-00273201.pphosted.com with ESMTP id 2e99uv03ew-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 16 Nov 2017 04:32:18 -0800
Received: from DM5PR05MB3545.namprd05.prod.outlook.com (10.174.242.150) by DM5PR05MB3548.namprd05.prod.outlook.com (10.174.242.153) 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:32:17 +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:32:17 +0000
From: John E Drake <jdrake@juniper.net>
To: Xuxiaohu <xuxiaohu@huawei.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 <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: AQHTXj7n5TRYZZG6f0OmPllyjgaJFKMWWYGAgAAGowCAAJBHQA==
Date: Thu, 16 Nov 2017 12:32:17 +0000
Message-ID: <DM5PR05MB35454B39214871304E1FF230C72E0@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> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE3047D266@NKGEML515-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE3047D266@NKGEML515-MBS.china.huawei.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; DM5PR05MB3548; 6:g8OHNa/3iUkDxZqM69QwRI4EUs+eoX7UFrt0wOmnQDE0RseVRT2Qe6uJsZhvrDhpMBVL7PhF61y/16SR7TCPFPpluQnLjHQNCUE+R5vZbkxQdiZSRjQMMCpJ5KLpy17sNgERx8yWVs+Y6ownZRvUmxKRaIAn+4Uqx4gI+6pdTDGgsdDkfI87tddY1M2DDEiXwbFk4MkME6807k9SjeXmaCfrJ0rzf2e5gapMYSbNCKV8cnTopXnT6cFhWPYkosc97RjtQHOnBs0uR5JeiQEmKl+lP9Fz07QcvkS70Y8mY4sE3DWl/hHr/blX+GcrGeV2W4uiu589IZBepJB1hIitWchNgCXZ7F4qwNNcv1yG3rs=; 5:uZHwGhUPD5FobIApWR1MUYH0hucYQwhLzU78/EgxtLtkgnuUPh3+UbNFXGV2RT+coZL6PWbxACA+KqkY4lSrO4vYX+aLQLSfVz1t7Q/DnOXEknktIautKpgBpD7wek+xG8rJPssL6HXxkg2rvXRTlUyCMn14UwZsy5NK+nCRnvg=; 24:9fXJZhku0l/6ui0M7FrK9nmqimC2PHS+ctGn413mNOiwlr7R5TsMGmyRM3VvUtBKtrGb425bvxdvseLE/V6dJp9656Awv/R1qHwPgFznNjA=; 7:OdGur9NuA7Z6Ogxweh8qVnGb/VHLftR/5W2kg8aRIl/WrRi8o43e5PMT8P9zPBHZla8xXFILcPpt1iRYlR4zQ4GFNuyoOC54gOLc8vmOLKud1OqSHkcv6JaCY5+RXRyOU7A4MPWiovPU43nUHGPq7D7ly6+Na0lNdPRPoncamNv7hDjfsB99D8rwtuWiFOKIX3dYuIxRDfNtUx/FOdIDJKaixhXiFAtAy/3oRgoSUAo4Q6lknPjwrokYT1mJTMa6
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 11889840-159e-4962-e03e-08d52cee12dc
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(48565401081)(2017052603199); SRVR:DM5PR05MB3548;
x-ms-traffictypediagnostic: DM5PR05MB3548:
x-microsoft-antispam-prvs: <DM5PR05MB3548B60F912D2C5708E891E2C72E0@DM5PR05MB3548.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)(5005006)(8121501046)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(3231022)(3002001)(6055026)(6041248)(20161123558100)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123564025)(20161123562025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DM5PR05MB3548; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DM5PR05MB3548;
x-forefront-prvs: 0493852DA9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(39860400002)(189002)(377424004)(37854004)(51444003)(199003)(966005)(15650500001)(77096006)(7110500001)(97736004)(74316002)(2906002)(16234385003)(3660700001)(7736002)(3280700002)(86362001)(4001150100001)(105586002)(3846002)(110136005)(316002)(6116002)(102836003)(606006)(345774005)(5660300001)(106356001)(25786009)(7696004)(2420400007)(790700001)(189998001)(229853002)(99286004)(101416001)(53546010)(8676002)(66066001)(478600001)(93886005)(2900100001)(6506006)(39060400002)(8936002)(81166006)(76176999)(230783001)(68736007)(55016002)(6436002)(236005)(14454004)(53936002)(33656002)(6306002)(54356999)(81156014)(2950100002)(6246003)(50986999)(54896002)(9326002)(9686003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3548; H:DM5PR05MB3545.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A: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_DM5PR05MB35454B39214871304E1FF230C72E0DM5PR05MB3545namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 11889840-159e-4962-e03e-08d52cee12dc
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Nov 2017 12:32:17.2003 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3548
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=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1711160171
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/FrA4xVLQ_mNAStrnisvRIJgvN-U>
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 12:32:47 -0000
Hi, This I completely agree with, however, given that we have had similar counters in LSRs since the advent of MPLS/RSVP-TE I am not sure this is a “complicated function”. Yours Irrespectively, John From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Xuxiaohu Sent: Wednesday, November 15, 2017 10:52 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 <draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org>; mpls <mpls@ietf.org>; spring <spring@ietf.org> Subject: Re: [mpls] [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<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dspring-2Dsegment-2Drouting-2D13&d=DwMFbw&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=H0f4eGIEJx8dGGNmVC6odbGYPjUtSzVjG1nidDV81W4&s=_uDfZ91-H1J1EfZbUnB1bCKToDMryuq30oQd8aOBquQ&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)