Re: [mpls] [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths
Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Thu, 16 November 2017 09:46 UTC
Return-Path: <Alexander.Vainshtein@ecitele.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 3C38E1292AE; Thu, 16 Nov 2017 01:46:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.58
X-Spam-Level:
X-Spam-Status: No, score=-4.58 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=eci365.onmicrosoft.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 tLdBATgPgvGt; Thu, 16 Nov 2017 01:46:44 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.177]) (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 BA914129461; Thu, 16 Nov 2017 01:46:36 -0800 (PST)
Received: from [195.245.230.51] by server-17.bemta-3.messagelabs.com id 38/7E-07572-A7E5D0A5; Thu, 16 Nov 2017 09:46:34 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDJsWRWlGSWpSXmKPExsViovlDRbcyjjf K4N4eFYvtx9ewW2xbfIbV4tu0p6wWt5auZLU4fuE3o8XW86sYLV7v+MruwO4x5fdGVo+ds+6y e7QcecvqsWTJT6YAlijWzLyk/IoE1ozvv+cwFZxqZK7Ys+o/awPjnj9MXYxcHCwCbcwSW6e2s 4M4QgJTmCSurN/EDOHcY5T4vHI3kMPJwSZgK7Fp9V02EFtEQF2ic9txsA5mgR9MEm/mHAdLCA tkSVz7fRSogQOoKFui4Y8hRL2fRMPjE2BhFgFViVlnZEDCvAIxEmuvXmCC2LWaWWJ/+35GkAS nQKBE67wOMJtRQEzi+6k1TCA2s4C4xK0n88FsCQEBiSV7zjND2KISLx//Y4WwFSVm3JvDDmHL Slya380IskBC4Ai7xNX301kgEsYSXRP2QDX4ShzePxHsOAkBZYktL2Ih6lcwSnRv74NaoCPRc f03G8RBSRL3ny5khIjnS3x7sYQJomEeUMObBewQzkNWieP9rSwQU2UkfndbQsQnsEtcn3IVbK qQQLLEiTmfWSYwas9C8h2EnScx/dIi5lngYBKUODnzCcssoFHMApoS63fpQ5QoSkzpfsgOYWt ItM6Zy44svoCRfRWjenFqUVlqka6FXlJRZnpGSW5iZo6uoYGxXm5qcXFiempOYlKxXnJ+7iZG YIpjAIIdjBfanQ8xSnIwKYnyOv/mjhLiS8pPqcxILM6ILyrNSS0+xCjDwaEkwXs5hjdKSLAoN T21Ii0zB5hsYdISHDxKIrz1sUBp3uKCxNzizHSI1ClGV44NN+/+YeLYASb3gckn1+b9ZeJ4Nv N1A7MQS15+XqqUOC8nSLMASHNGaR7caFimuMQoKyXMywh0rBBPQWpRbmYJqvwrRnEORiVh3hc gF/Jk5pXAXfAK6DgmoONsbnCDHFeSiJCSamAMkjz1Zs5kJoZZa28kVM/K8Exdab8l7qtBy0yJ vQvfrvGxk67Z8HPqfS4l6ci5r5wULxuu+71uErvCqpMcvZFNQqfP/As+FV7PbfH3f2LnqiNOl pvb/6peLZXc8JjnmsPqZ9bVNWueyygK8avd+DvXpuP1F8m7W+eZZ2xdJNfc68231eXNMubHSi zFGYmGWsxFxYkA0WrZfA8EAAA=
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-14.tower-33.messagelabs.com!1510825589!119084394!1
X-Originating-IP: [52.41.248.36]
X-StarScan-Received:
X-StarScan-Version: 9.4.45; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 6899 invoked from network); 16 Nov 2017 09:46:32 -0000
Received: from ec2-52-41-248-36.us-west-2.compute.amazonaws.com (HELO EUR01-HE1-obe.outbound.protection.outlook.com) (52.41.248.36) by server-14.tower-33.messagelabs.com with AES256-SHA256 encrypted SMTP; 16 Nov 2017 09:46:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector1-ecitele-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=7l4SA0LCBOFBdhT5PlmP3SHMyyf7gJBjvb7ZuMd6CWQ=; b=WNAuhsoABSh3GBiLDH9SrudbetCzvFrQLgKyC79yXrpACAnAEF/nS+jilY/fba5KbygGvjJL4D9duFwA7DmGF8Ma/9gVC3ir4hZic/XcZFb/aEortjvngYR3VQ4M3oxhvo9ty0psCAh5RlagNyxQR/Z8qDXUzWSmWJgdfCcNZEs=
Received: from AM4PR03MB1713.eurprd03.prod.outlook.com (10.167.88.15) by DB6PR0301MB2567.eurprd03.prod.outlook.com (10.168.72.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.239.5; Thu, 16 Nov 2017 09:46:27 +0000
Received: from AM4PR03MB1713.eurprd03.prod.outlook.com ([fe80::51e:9df0:75fb:d611]) by AM4PR03MB1713.eurprd03.prod.outlook.com ([fe80::51e:9df0:75fb:d611%14]) with mapi id 15.20.0239.005; Thu, 16 Nov 2017 09:46:27 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Greg Mirsky <gregimirsky@gmail.com>
CC: draft-hegde-spring-traffic-accounting-for-sr-paths <draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org>, spring <spring@ietf.org>, "Zafar Ali (zali)" <zali@cisco.com>, mpls <mpls@ietf.org>, Xuxiaohu <xuxiaohu@huawei.com>, Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>, "draft-ietf-spring-oam-usecase@ietf.org" <draft-ietf-spring-oam-usecase@ietf.org>
Thread-Topic: [mpls] [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths
Thread-Index: AQHTXj7p2nUnIXsOmkCuZ5PMoKj+8KMWQkuAgAAGK4CAAFlbgIAAGHuAgAAGWsA=
Date: Thu, 16 Nov 2017 09:46:27 +0000
Message-ID: <AM4PR03MB1713EF1C33E1D8902476D1A39D2E0@AM4PR03MB1713.eurprd03.prod.outlook.com>
References: <CA+RyBmUHAkuA3o-LpHhMwCbkh0k+emt9OZ3B8Njj2h=jaasTZw@mail.gmail.com> <3B1EE673-044F-4E47-9C56-6FF360905C58@cisco.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE3047CEC9@NKGEML515-MBS.china.huawei.com> <CA+RyBmVC2OjEs-=1WsL13eBmycZtnYnM8ybSdmWhGPByLKNQfA@mail.gmail.com> <AM4PR03MB171328C37B726DE4AFF862D39D2E0@AM4PR03MB1713.eurprd03.prod.outlook.com> <CA+RyBmUE1vZd-T8mrNmrf8FbP_fGhzLvn9kEQQ3A=FUJazJQMg@mail.gmail.com>
In-Reply-To: <CA+RyBmUE1vZd-T8mrNmrf8FbP_fGhzLvn9kEQQ3A=FUJazJQMg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.241.1]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB6PR0301MB2567; 6:F/Dzpci5zrff8mSt7giJrOCSA+eqhqlhRD3JWl+Ckb6KilgXhJfv6zTH0F0GTsInBxxP7rUokqCpE9Xtsn8gJHGd2RjNdltgJW29Abjs0xo5jom30F+Q0a4HsEXumx+WPVFETK6jnFXr9BvcAKQO74MM5KEirScsov11PzAfohVEhsi+UjPLnzjZe2WDivT1u5esg66Is/LuiBkfVoYp2/Kv0sc3SiPwl3folV/vwGx6LEJrRG+jNJ80WHdBkmq8Zj7c3zZSSdmyuSLuDQCpQUoOTLrtpEWzKhLeojpwXRhpO41OL8NcFhJNQ7LR4T+LbD0st7IUKWUQJoQwsVuUofejEUe5dzgGXwLjIIzsmXQ=; 5:IS7UiwSiOaNvX7JhctqYomp9MB9nMxWFefQRdqEmgWMu9iVnCQ2+S6K4vgK7TRQ4mpCSWXoS3VqBQBC8OmK/myI5MnX+Yhg+Y0wMltDXTqEIsdx5ZEF9guDJxFNKrHhlyB19fpcw4biGapVGhEbgMXiIl6H+zV+hhxoOl1SeXvU=; 24:03hYj+hc5PCjtgBb+7TAHbNh9uR8Byhh2HEo9rqnduuzTe6BOYfehF8ORxfwsZ3lIREoqM+qvvSedvcj7nXjOdczMOO5BmW0rbZv8EQI4h0=; 7:oR7qh5Cq4ag4y9cORL4zYeV2pwdqFspbz2b52STjspnGCPsc9zR7TbYTghxTk6co6wRyaEtI+wP34rPhXPRFgjEr0KaO/4vA7VlLqb+u+VsHUy4fJtxcvaSkp1YWAxZtJe3zQ6tSSAHnMRIza+siHMs6X8aBLqaUMF3GHBG//FV9CnQYhv2AUsjwzzU+mb1vKavTUYSyi6uLuGghA3QX1ZBM8Zk2OP8f0J64uc5hpQgP3vs60vchHeZzoi7DLOWC
x-ms-exchange-antispam-srfa-diagnostics: SSOS;SSOR;
x-ms-office365-filtering-correlation-id: 5897cab4-382c-47b7-ceec-08d52cd6e817
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603258); SRVR:DB6PR0301MB2567;
x-ms-traffictypediagnostic: DB6PR0301MB2567:
x-microsoft-antispam-prvs: <DB6PR0301MB256773A9DF30850306C290A99D2E0@DB6PR0301MB2567.eurprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(50582790962513)(259379197776797)(95692535739014)(227612066756510)(21748063052155)(279101305709854);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231022)(100000703101)(100105400095)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123558100)(20161123555025)(20161123560025)(20161123564025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB6PR0301MB2567; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB6PR0301MB2567;
x-forefront-prvs: 0493852DA9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(189002)(377424004)(252514010)(199003)(51444003)(24454002)(54906003)(66066001)(39060400002)(966005)(72206003)(4326008)(93886005)(7696004)(5250100002)(316002)(4001150100001)(53936002)(1411001)(6246003)(236005)(55016002)(6306002)(6506006)(54896002)(229853002)(6436002)(99286004)(9686003)(97736004)(790700001)(3846002)(5660300001)(19609705001)(606006)(2950100002)(6916009)(25786009)(53546010)(6116002)(86362001)(102836003)(478600001)(81166006)(105586002)(8936002)(81156014)(68736007)(101416001)(7736002)(74316002)(54356999)(50986999)(189998001)(14454004)(7110500001)(33656002)(106356001)(8676002)(230783001)(76176999)(15650500001)(10710500007)(3660700001)(2420400007)(2900100001)(2906002)(3280700002)(345774005); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0301MB2567; H:AM4PR03MB1713.eurprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: ecitele.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR03MB1713EF1C33E1D8902476D1A39D2E0AM4PR03MB1713eurp_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5897cab4-382c-47b7-ceec-08d52cd6e817
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Nov 2017 09:46:27.0666 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0301MB2567
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/usgsxnT4454ziksSN61RLj6w4Cg>
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 09:46:54 -0000
Greg, I do not think that the quoted requirement from the SR OAM Requirements draft is relevant for this discussion, because, from my POV, it does not refer to ability to measure actual traffic carried in a specific SR-TE LSP across a specific link in the transit node. And this is actually what draft-hegde is all about. I also do not see how SPME (an ill-begotten MPLS-TP construct) is relevant for this discussion. As for the added state in transit node: From mu POV ability to recognize specific SR-TE Path ID in the label stack of a packet and to update the counters allocated to this SR-TE Path is a forwarding plane state. My 2c, Sasha Office: +972-39266302 Cell: +972-549266302 Email: Alexander.Vainshtein@ecitele.com From: Greg Mirsky [mailto:gregimirsky@gmail.com] Sent: Thursday, November 16, 2017 11:15 AM To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Cc: draft-hegde-spring-traffic-accounting-for-sr-paths <draft-hegde-spring-traffic-accounting-for-sr-paths@ietf.org>; spring <spring@ietf.org>; Zafar Ali (zali) <zali@cisco.com>; mpls <mpls@ietf.org>; Xuxiaohu <xuxiaohu@huawei.com>; Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>; draft-ietf-spring-oam-usecase@ietf.org Subject: Re: [mpls] [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths Hi Sasha, many thanks. I'd point to SR OAM Requirements<https://tools.ietf.org/html/draft-ietf-spring-sr-oam-requirement-03> (regrettably expired): REQ#13: SR OAM MUST have the ability to measure Packet loss, Packet Delay or Delay variation using Active (using synthetic probe) and Passive (using data stream) mode. I think that our discussion indicates that OAM requirements document is useful at least for as long as we're developing OAM toolset. And the document will benefit from clarification to reflect our discussion that PM may be performed both e2e and over SPME. Regards, Greg On Thu, Nov 16, 2017 at 4:11 PM, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote: Greg, I concur with your position: let’s first of all agree that ability to measure traffic carried by an SR-TE LSP in a specific transit node is a require OAM function for SR. I have looked up the SR OAM Use Cases<https://datatracker.ietf.org/doc/draft-ietf-spring-oam-usecase/?include_text=1> draft, and I did not find any relevant use cases there. The only time measurements are mentioned is a reference to an expired implementation report<https://tools.ietf.org/html/draft-leipnitz-spring-pms-implementation-report-00> draft discussing delay measurements. Since delay measurements are in any case based on synthetic traffic, and are always end-to-end (one-way or two-way), this reference is not relevant, IMHO, for this discussion. I have added the authors of the SR OAM Use Cases draft to tis thread. Regards, Sasha Office: +972-39266302<tel:+972%203-926-6302> Cell: +972-549266302<tel:+972%2054-926-6302> Email: Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com> From: mpls [mailto:mpls-bounces@ietf.org<mailto:mpls-bounces@ietf.org>] On Behalf Of Greg Mirsky Sent: Thursday, November 16, 2017 4:28 AM To: Xuxiaohu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>> Cc: 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>>; spring <spring@ietf.org<mailto:spring@ietf.org>>; Zafar Ali (zali) <zali@cisco.com<mailto:zali@cisco.com>>; mpls <mpls@ietf.org<mailto:mpls@ietf.org>> Subject: Re: [mpls] [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths Dear All, I cannot imagine that operators will agree to deploy network that lacks critical OAM tools to monitor performance and troubleshoot the network. True, some will brave the challenge and be the early adopters but even they will likely request that the OAM toolbox be sufficient to support their operational needs. I see that this work clearly describes the problem and why ability to quantify the flow behavior at internal nodes is important for efficient network operation. First let's discuss whether the case and requirement towards OAM is real and valid. Then we can continue to discussion of what measurement method to use. Regards, Greg On Thu, Nov 16, 2017 at 10:05 AM, Xuxiaohu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>> wrote: Concur. Although it has some values, it's not cost-efficient from my point of view. Network simplicity should be the first priority object. Hence we would have to make some compromise. 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 发件人: Zafar Ali (zali) 收件人: 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: [mpls] [spring] Special purpose labels in draft-hegde-spring-traffic-accounting-for-sr-paths 时间: 2017-11-16 02:24:10 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 ___________________________________________________________________________ This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof. ___________________________________________________________________________ ___________________________________________________________________________ This e-mail message is intended for the recipient only and contains information which is CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this transmission in error, please inform us by e-mail, phone or fax, and then delete the original and all copies thereof. ___________________________________________________________________________
- [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)