Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH
Ron Bonica <rbonica@juniper.net> Mon, 25 May 2020 15:43 UTC
Return-Path: <rbonica@juniper.net>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D503A0D74; Mon, 25 May 2020 08:43:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, 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=juniper.net header.b=alSvbl+d; dkim=pass (1024-bit key) header.d=juniper.net header.b=WO9m8o4D
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 xGDKBCdpZgCM; Mon, 25 May 2020 08:43:40 -0700 (PDT)
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 74C833A0D8E; Mon, 25 May 2020 08:43:39 -0700 (PDT)
Received: from pps.filterd (m0108162.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 04PFglTM027286; Mon, 25 May 2020 08:43:38 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=PPS1017; bh=xRSh0ib7WLVfbiR2p6BXbFBTcmmq0bYoW8ygUklb2Sg=; b=alSvbl+dBb7/0QhqhXkvhQ4cKFQ+uZ7sh6IUHqBPZIeFz933qTs9A1TJmg2nqWyukQdw 3AWubLpxPwdYqJuzHZXAeYV05SEvI/bMRV9ev9roUAyfk7ujpXSNVY0CSpKYo8GTBUQA 9WiaJ+rYxx5qxd1EDqOkC66fJyJfIzHH4b/yQRPEy27LtawOADmN++CVhQV97G3dSl3Y he4lRAFIXtnpxi3e6UE+u3PRNuwmGYmvZVcy/ENxUtDR/ubCc8ulxUqcJ88buhN7shHN Tb8Lg5FEpzDJnrLbYZWZ4iiRY6W2z3Qrh0grJGEUc39SKz5GEZ4gPvlFiRqmbjHxjZGE rw==
Received: from nam12-mw2-obe.outbound.protection.outlook.com (mail-mw2nam12lp2049.outbound.protection.outlook.com [104.47.66.49]) by mx0b-00273201.pphosted.com with ESMTP id 3172392t51-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 25 May 2020 08:43:38 -0700
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UAU+12tkEAsHjFDRBGwKItEdJ0A2SWfGXIVlq4sL+Ea1rVa3uXKccDd8BPwRM+22qD7y2XRP7x2BgGgT0PTZX6UeAoovWM8dfEmIL+nvpuq5qbYBU4wYahx39+hU8xS0VQvd+XJ4KjjTW4UPFoHc6XAgQ2wM6D+jOtSDxMu9D8lAMi7HneVku1qLsuDy73lfZPYwcXmexh9a5cJ8a2pxcOc4O/q8fHlSrfKlHt+ZhMxwKAvFHMQlGwp+U2ArOq1tbU+K3oX656Ip/h9PkTZX82n7vq1HmsKr1XYCl5qvbGXMHkpxkGtlFfLyDjzF/Vd9KokjT3I8MwFS7biScz0zLA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xRSh0ib7WLVfbiR2p6BXbFBTcmmq0bYoW8ygUklb2Sg=; b=m4LkzQJ6l16jMemjC3zbRMGpZQXN920Ji4kuPae5bxGqiJDXu4DZhcccwhfzvnwnRNqzX1RooMP4RkAK8gdlr1yIS2CgAkOpu7GDpWBK6yN4hfsQ1stVqqoexl5IpKvNKRGuZ5abAOJmc3aqrqxX/S9qiqd7XACt4ik3K5IpJrYFf2QHKabA5E8WJWyg4IPPgKc5koYXPyinxcVOaKVneTbDQs/YSdrAo2WeIAqqm/C9I8hNPb7w7+B1jQ186g6oOY43/uzrVqLIqOlxISXwLMJjoEyVSj5NB6tCs5+8rkO18MNFDs68SVvTbhyfU9fL0bjZbyRcOtNLfu/iXcno+g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xRSh0ib7WLVfbiR2p6BXbFBTcmmq0bYoW8ygUklb2Sg=; b=WO9m8o4DItckMCC6P2b8jE3Wl97lJejnLbit9FJ7xlgHUwcfPRr0b5/SvQ65Og4ZGooR2iK2zMN/lfPLm8Jft31agIEbV3JACwy+y8FmT6P2GW2p92yX/cIu0AEW5P3pfsD13UikBq2V/bnN+3MgWk+dWFtkxzY49YKEEeLbNPU=
Received: from DM6PR05MB6348.namprd05.prod.outlook.com (2603:10b6:5:122::15) by DM6PR05MB4348.namprd05.prod.outlook.com (2603:10b6:5:95::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.10; Mon, 25 May 2020 15:43:35 +0000
Received: from DM6PR05MB6348.namprd05.prod.outlook.com ([fe80::c020:3bf5:7230:75e3]) by DM6PR05MB6348.namprd05.prod.outlook.com ([fe80::c020:3bf5:7230:75e3%4]) with mapi id 15.20.3045.014; Mon, 25 May 2020 15:43:35 +0000
From: Ron Bonica <rbonica@juniper.net>
To: "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>
CC: "rtg-ads@ietf.org" <rtg-ads@ietf.org>, "spring@ietf.org" <spring@ietf.org>, 6man <6man@ietf.org>
Thread-Topic: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH
Thread-Index: AQHWL4VxmYvkCvDoNEmQ3Xkat3whdqiytyCggAALHOCAAAWDcIAAXREAgABKZfCAAAVCgIAAAypAgAANNoCAAAvxgIAAnLwAgAKNblCAAWx9AIAAV42QgAB2TjA=
Date: Mon, 25 May 2020 15:43:35 +0000
Message-ID: <DM6PR05MB634848BE997686F212FF9E49AEB30@DM6PR05MB6348.namprd05.prod.outlook.com>
References: <9CF68CCE-B584-4648-84DA-F2DBEA94622D@cisco.com> <C7C2E1C43D652C4E9E49FE7517C236CB02A2C1AE@dggeml529-mbx.china.huawei.com> <DM6PR05MB6348A22A123AFA7E7345087BAEB70@DM6PR05MB6348.namprd05.prod.outlook.com> <MW3PR11MB457041A967A6BBDA1C7EF0FDC1B70@MW3PR11MB4570.namprd11.prod.outlook.com> <93a31c7f-a102-da59-d9a8-2585cd8e3c65@gmail.com> <MW3PR11MB4570B197EE00C5385DAEE138C1B40@MW3PR11MB4570.namprd11.prod.outlook.com> <5F062FA6-9E2D-46BB-A3D6-257D374D8F92@gmail.com> <MW3PR11MB4570485EEDBADEF3B193BB82C1B40@MW3PR11MB4570.namprd11.prod.outlook.com> <ec63e90e-19fa-cd6c-eacb-4dee44815c99@joelhalpern.com> <MW3PR11MB4570FB2397D4B28A42626802C1B40@MW3PR11MB4570.namprd11.prod.outlook.com> <3bbb28c8-0106-ad63-abf9-c9dc4e428e0c@joelhalpern.com> <MW3PR11MB4570FD37ED32519C677F5E59C1B20@MW3PR11MB4570.namprd11.prod.outlook.com> <DM6PR05MB63486B842CD9DF5BE57FC1A5AEB30@DM6PR05MB6348.namprd05.prod.outlook.com> <MW3PR11MB45706D51FBE6CD63B58CDF15C1B30@MW3PR11MB4570.namprd11.prod.outlook.com>
In-Reply-To: <MW3PR11MB45706D51FBE6CD63B58CDF15C1B30@MW3PR11MB4570.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=true; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2020-05-25T03:32:27Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Standard; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=0633b888-ae0d-4341-a75f-06e04137d755; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ActionId=fce2e8ee-c77f-4352-852c-4509f560098b; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=2
dlp-product: dlpe-windows
dlp-version: 11.4.0.45
dlp-reaction: no-action
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none; dmarc.ietf.org; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [108.28.233.91]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: a939ba19-5028-4f69-ab3c-08d800c262d3
x-ms-traffictypediagnostic: DM6PR05MB4348:
x-microsoft-antispam-prvs: <DM6PR05MB43484C29294A461D805683E6AEB30@DM6PR05MB4348.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 0414DF926F
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: rr3GAHPKVYgAmTJaRFRRrfYzcrIK5s0uk+BcJMDiBo9QyK6tjWcZI3EDTCwkJMgRCB354zbuzkGBO0MuCXmk90fFg0xflY++1N4mLy0Y43BWN9OMX4tULZL0I4SWjTnUvD+WNnao1kIg9iorEMA7Wtt9E9XF5wtabhptltzYb8r+Y2XhoA4XZDHtjrjZxuXnAMr+DDV37yG56OeiMPB4ZyO132vU5Dhz8C08DwKYJTKL7kzLhKieSLaJ2pdHZq73w2QAUMCF79K6TjeKvLV8Ymra090SvgAkss3aUBKRG0SKyWi9R7BYJQHDPP2/6IRQlLJrlrTwmfqCDXL0uNlRtOAYsLokiBPm1qs8PW6uqQ7G2gwVhIVe5DsD7Ld+nR3vkM5+Gc5KkdXZ7a4kjVg2ZQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR05MB6348.namprd05.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(346002)(396003)(39860400002)(366004)(136003)(376002)(110136005)(8936002)(316002)(8676002)(4326008)(54906003)(64756008)(66556008)(66946007)(66476007)(66446008)(76116006)(86362001)(52536014)(966005)(478600001)(2906002)(33656002)(5660300002)(7696005)(53546011)(6506007)(26005)(71200400001)(55016002)(186003)(9686003); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: cQNsKZ/1yECKkv3JnteS4S4EOR/10jj929kbuj5vOmBBpLThLZiEXfcsHSlJU+GXifRRKtZ2/OLgHfmBIgSZqgOb1UWCT+7ytaGIgkGOTNFfhogWMjZSqaj77Pygr13OdplIqi5KO74VyyAZGUilQR/WWz1csBLM3SeYbPuRJbwDQcOrppXtxfbHlS1tfLgm29iJz4Oldxw79X4OLlRGs8UB6f/GZezoAvCrtF0rCmi+7zZybKAigB7M8Y+tO48okY7belE7pifc3YbzAYLm1SGD+4NjtyBdMQnZZ5wkWGQFRHWBM8kQcNIPLPKrFHflcpyjLqgi+fllZy6WL8LUy/a8qHPUhG6KcQ2LC5CJkj9JejmL+zJ0C5V7sp6DqzN8coZ+pZuLx5MB4ZNs2Bgq/ZLer+ZIbwiGZX94WhdjZmgliaHQPOz2FRVur0mTSvzp1gVWPxBJ3y2ipsqTI/Q9sdSHW8BIHGHnRwuVA5ZBpOsE03wDkWy7rvKT3OhEj6Rn
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: a939ba19-5028-4f69-ab3c-08d800c262d3
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 May 2020 15:43:35.2990 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: om9/UYo/0a0CWH8Lf38EXxjd+AmiThHbh1olUFYHGxpvqsuUGGmPa7uR1Xr7pGJW2YQ3uj1RvdhGXiaS9YRXog==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB4348
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.687 definitions=2020-05-25_09:2020-05-25, 2020-05-25 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 phishscore=0 clxscore=1015 suspectscore=0 priorityscore=1501 malwarescore=0 adultscore=0 cotscore=-2147483648 spamscore=0 mlxscore=0 lowpriorityscore=0 impostorscore=0 mlxlogscore=999 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2004280000 definitions=main-2005250122
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/IFdATJ7la-RdT4Ox1RNikejtUOw>
Subject: Re: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 May 2020 15:43:50 -0000
Ketan, It would not be fair to say that these operators "wish to deploy a Traffic Engineering solution using a subset of Segment Routing". It would be fair to say that these operators "wish to deploy IPv6 Traffic Engineering". Some of these operators don't care about SR. Some are actively averse to SRv6. All they want is a Routing header. Ron Juniper Business Use Only -----Original Message----- From: Ketan Talaulikar (ketant) <ketant=40cisco.com@dmarc.ietf.org> Sent: Monday, May 25, 2020 5:21 AM To: Ron Bonica <rbonica@juniper.net>; Joel M. Halpern <jmh@joelhalpern.com> Cc: rtg-ads@ietf.org; spring@ietf.org; 6man <6man@ietf.org> Subject: RE: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH [External Email. Be cautious of content] Hi Ron, Thanks for that clarification. I note that you are not anymore saying "Are not interested in SR" like you had mentioned before the WG adoption call : https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/ipv6/LheyFD_uwuHp7tiG8Y1CwKngDYI/__;!!NEt6yMaO-gk!X2qW2zTZEbZRfBSE6c_KM-k7aIvZTIT9bycp3jyFJ3sTbf8MtGo4E_uGX7zYZ7lk$ So, would it be fair to say that the operator that you are referring to below, wishes to deploy a Traffic Engineering solution using a subset of Segment Routing (i.e. a reduced portion of Spring Architecture) that only supports prefix and adjacency SIDs as indicated by the two "forwarding methods" that are referred to in draft-bonica-6man-comp-rtg-hdr? Thanks, Ketan -----Original Message----- From: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org> Sent: 25 May 2020 09:03 To: Ketan Talaulikar (ketant) <ketant@cisco.com>; Joel M. Halpern <jmh@joelhalpern.com> Cc: rtg-ads@ietf.org; spring@ietf.org; 6man <6man@ietf.org> Subject: RE: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH Ketan, Please consider an operator who: - Wants a way to steer IPv6 packets through a specified path that includes many nodes (>8) - Does not want any of the following: - A new VPN encapsulation technique - A new service function chaining technique - Network programming - MPLS and uSID - To encoding instructions in IPv6 addresses. These operators want a compact routing header, nothing more. Ron Juniper Business Use Only -----Original Message----- From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Ketan Talaulikar (ketant) Sent: Sunday, May 24, 2020 1:42 AM To: Joel M. Halpern <jmh@joelhalpern.com> Cc: rtg-ads@ietf.org; spring@ietf.org; 6man <6man@ietf.org> Subject: RE: [spring] CRH is back to the SPRING Use-Case - Re: Size of CR in CRH [SNIP] I am looking for explanation of the "other ways" that CRH can be used (i.e. those outside the Spring architecture). I am trying to understand from the authors what would be the applicability of that solution, it's use-cases and it's requirements. That is what, I believe, will help us evaluate the CRH proposal in the context of this working call. That will help us answer these questions like the scope of the SID, 32-bit or 16-bit or something else and what the CRH-FIB is going to turn out like. [SNIP] ------------------------------------------------------
- Re: [spring] CRH is back to the SPRING Use-Case -… Ketan Talaulikar (ketant)
- Re: [spring] CRH is back to the SPRING Use-Case -… Ketan Talaulikar (ketant)
- Re: [spring] CRH is back to the SPRING Use-Case -… Joel M. Halpern
- Re: [spring] CRH is back to the SPRING Use-Case -… Ketan Talaulikar (ketant)
- Re: [spring] CRH is back to the SPRING Use-Case -… Bob Hinden
- Re: [spring] CRH is back to the SPRING Use-Case -… Ketan Talaulikar (ketant)
- [spring] CRH is back to the SPRING Use-Case - Re:… Zafar Ali (zali)
- Re: [spring] CRH is back to the SPRING Use-Case -… Chengli (Cheng Li)
- Re: [spring] CRH is back to the SPRING Use-Case -… Ron Bonica
- Re: [spring] CRH is back to the SPRING Use-Case -… Ketan Talaulikar (ketant)
- Re: [spring] CRH is back to the SPRING Use-Case -… Brian E Carpenter
- Re: [spring] CRH is back to the SPRING Use-Case -… Brian E Carpenter
- Re: [spring] CRH is back to the SPRING Use-Case -… Andrew Alston
- Re: [spring] CRH is back to the SPRING Use-Case -… Andrew Alston
- Re: [spring] CRH is back to the SPRING Use-Case -… Fernando Gont
- Re: [spring] CRH is back to the SPRING Use-Case -… Joel M. Halpern
- Re: [spring] CRH is back to the SPRING Use-Case -… Pengshuping (Peng Shuping)
- Re: [spring] CRH is back to the SPRING Use-Case -… Pengshuping (Peng Shuping)
- Re: [spring] CRH is back to the SPRING Use-Case -… Tom Herbert
- [spring] 答复: CRH is back to the SPRING Use-Case -… Aijun Wang
- Re: [spring] 答复: CRH is back to the SPRING Use-Ca… Andrew Alston
- Re: [spring] 答复: CRH is back to the SPRING Use-Ca… Pengshuping (Peng Shuping)
- Re: [spring] CRH is back to the SPRING Use-Case -… Ketan Talaulikar (ketant)
- Re: [spring] CRH is back to the SPRING Use-Case -… Ketan Talaulikar (ketant)
- Re: [spring] 答复: CRH is back to the SPRING Use-Ca… Aijun Wang
- Re: [spring] 答复: CRH is back to the SPRING Use-Ca… Joel Halpern Direct
- Re: [spring] 答复: CRH is back to the SPRING Use-Ca… Aijun Wang
- Re: [spring] CRH is back to the SPRING Use-Case -… Ron Bonica
- Re: [spring] CRH is back to the SPRING Use-Case -… Robert Raszuk
- Re: [spring] CRH is back to the SPRING Use-Case -… Ketan Talaulikar (ketant)
- Re: [spring] CRH is back to the SPRING Use-Case -… Sander Steffann
- Re: [spring] CRH is back to the SPRING Use-Case -… otroan
- Re: [spring] CRH is back to the SPRING Use-Case -… Sander Steffann
- Re: [spring] CRH is back to the SPRING Use-Case -… Ron Bonica
- Re: [spring] CRH is back to the SPRING Use-Case -… Ron Bonica
- Re: [spring] CRH is back to the SPRING Use-Case -… Robert Raszuk
- Re: [spring] CRH is back to the SPRING Use-Case -… Ole Troan
- Re: [spring] CRH is back to the SPRING Use-Case -… Ron Bonica
- [spring] What's the colour of the hat (was: Re: C… otroan
- Re: [spring] CRH is back to the SPRING Use-Case -… Andrew Alston
- Re: [spring] What's the colour of the hat (was: R… Ron Bonica
- Re: [spring] What's the colour of the hat (was: R… Sander Steffann
- Re: [spring] What's the colour of the hat (was: R… Ron Bonica
- Re: [spring] What's the colour of the hat (was: R… Robert Raszuk
- Re: [spring] CRH is back to the SPRING Use-Case -… Srihari Sangli
- Re: [spring] CRH is back to the SPRING Use-Case -… Ketan Talaulikar (ketant)
- Re: [spring] CRH is back to the SPRING Use-Case -… Fernando Gont
- Re: [spring] CRH is back to the SPRING Use-Case -… Wang, Weibin (NSB - CN/Shanghai)
- Re: [spring] CRH is back to the SPRING Use-Case -… Gyan Mishra
- Re: [spring] CRH is back to the SPRING Use-Case -… Ron Bonica
- Re: [spring] CRH is back to the SPRING Use-Case -… Ron Bonica
- Re: [spring] CRH is back to the SPRING Use-Case -… Peter Psenak
- Re: [spring] CRH is back to the SPRING Use-Case -… Gyan Mishra
- Re: [spring] CRH is back to the SPRING Use-Case -… Peter Psenak
- Re: [spring] CRH is back to the SPRING Use-Case -… Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [spring] CRH is back to the SPRING Use-Case -… John Scudder
- Re: [spring] CRH is back to the SPRING Use-Case -… Peter Psenak
- Re: [spring] CRH is back to the SPRING Use-Case -… John Scudder
- Re: [spring] CRH is back to the SPRING Use-Case -… Peter Psenak
- Re: [spring] CRH is back to the SPRING Use-Case -… John Scudder
- Re: [spring] CRH is back to the SPRING Use-Case -… Peter Psenak
- Re: [spring] CRH is back to the SPRING Use-Case -… Tony Przygienda
- Re: [spring] CRH is back to the SPRING Use-Case -… Ketan Talaulikar (ketant)
- Re: [spring] CRH is back to the SPRING Use-Case -… Ketan Talaulikar (ketant)
- Re: [spring] CRH is back to the SPRING Use-Case -… Robert Raszuk