Re: [bcause] [Bcause] interest and scope?
Gregory Dalle <gdalle@juniper.net> Mon, 25 March 2019 20:30 UTC
Return-Path: <gdalle@juniper.net>
X-Original-To: bcause@ietfa.amsl.com
Delivered-To: bcause@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59CEA1200A4 for <bcause@ietfa.amsl.com>; Mon, 25 Mar 2019 13:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.138
X-Spam-Level:
X-Spam-Status: No, score=0.138 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, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, KHOP_DYNAMIC=0.85, RCVD_IN_DNSWL_LOW=-0.7, 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 zWekPZjwc5VM for <bcause@ietfa.amsl.com>; Mon, 25 Mar 2019 13:30:32 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 DC600120020 for <bcause@ietf.org>; Mon, 25 Mar 2019 13:30:31 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x2PKT4Id032448; Mon, 25 Mar 2019 13:30:25 -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 : mime-version; s=PPS1017; bh=6uAoVwAr9mZPVj4yLlsBUmr7dID/pCRwD4jZE5VxYZU=; b=HyHpwy+OyFAUwwOoLZi+4PLMMmklGzhn4dqcJp2fFCLp8Z7CN9oxdw2j+Mhs3LaVnzYH u8yfKJt9zlibYTDYib2meaudqLQ5jli+m9X8jp+NFaV8KJa2oPzm3fZC1bpKDtHzZ3aJ kIeZ517QEh+OJcQVgbKzMYGRrdXYjZld4mRIU7gqUgufvg1366Xbbyr1ZuDnJD7xwdlT DMGn4uG2Sfb9HlWEIWdgixhEsUzGAdZU206RxAsc90IdvZ0f/YmpivpprrnCgRxdqN7J Tihr02EhF+S/fLu++3lAIHYIrkyP8dIuLOkkzA3tGCni933Ln0S+4ikX7LBzBhaO2x7F mw==
Received: from nam02-sn1-obe.outbound.protection.outlook.com (mail-sn1nam02lp2053.outbound.protection.outlook.com [104.47.36.53]) by mx0a-00273201.pphosted.com with ESMTP id 2rf2x5gaq2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 25 Mar 2019 13:30:25 -0700
Received: from MWHPR05MB3360.namprd05.prod.outlook.com (10.174.175.145) by MWHPR05MB3149.namprd05.prod.outlook.com (10.173.229.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.16; Mon, 25 Mar 2019 20:30:22 +0000
Received: from MWHPR05MB3360.namprd05.prod.outlook.com ([fe80::9895:5636:5403:b39d]) by MWHPR05MB3360.namprd05.prod.outlook.com ([fe80::9895:5636:5403:b39d%4]) with mapi id 15.20.1750.014; Mon, 25 Mar 2019 20:30:22 +0000
From: Gregory Dalle <gdalle@juniper.net>
To: "Aijun Wang@China Telecom" <wangaj.bri@chinatelecom.cn>
CC: Greg Mirsky <gregimirsky@gmail.com>, "Vigoureux, Martin (Nokia - FR/Paris-Saclay)" <martin.vigoureux@nokia.com>, "bcause@ietf.org" <bcause@ietf.org>
Thread-Topic: [bcause] [Bcause] interest and scope?
Thread-Index: AQHU4w1/W7NyntGkAkCpOzar0/O+t6YcndCAgAAlgICAAAbI8A==
Date: Mon, 25 Mar 2019 20:30:22 +0000
Message-ID: <MWHPR05MB3360B9C9529BB5E8B03392A1D35E0@MWHPR05MB3360.namprd05.prod.outlook.com>
References: <4c42b485-0798-50c4-b62e-501dff12c914@nokia.com> <CA+RyBmWp8HuDt31o_gtBELaE5=D06Yqe1zxpdigjORJDfwa8=Q@mail.gmail.com> <MWHPR05MB3360D79E90DD1E04E4EB418AD35E0@MWHPR05MB3360.namprd05.prod.outlook.com> <09BCFDCE-6A61-4897-935D-309CC507094C@chinatelecom.cn>
In-Reply-To: <09BCFDCE-6A61-4897-935D-309CC507094C@chinatelecom.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.1.100.23
dlp-reaction: no-action
x-originating-ip: [66.129.241.10]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7dd34cb4-2002-4840-ed53-08d6b160b4aa
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(4618075)(2017052603328)(7153060)(7193020); SRVR:MWHPR05MB3149;
x-ms-traffictypediagnostic: MWHPR05MB3149:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <MWHPR05MB314978C323DE3DA8579DB4FFD35E0@MWHPR05MB3149.namprd05.prod.outlook.com>
x-forefront-prvs: 0987ACA2E2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(136003)(376002)(396003)(39860400002)(366004)(189003)(199004)(68736007)(229853002)(478600001)(54896002)(14454004)(81166006)(71190400001)(256004)(5660300002)(105586002)(71200400001)(446003)(6246003)(74316002)(76176011)(6116002)(14444005)(6916009)(4326008)(316002)(2906002)(81156014)(966005)(66066001)(55016002)(6436002)(11346002)(9686003)(52536014)(9326002)(99286004)(6306002)(54906003)(53546011)(186003)(26005)(486006)(7696005)(7736002)(476003)(790700001)(606006)(3846002)(53936002)(106356001)(102836004)(93886005)(8936002)(97736004)(236005)(8676002)(33656002)(6506007)(25786009)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR05MB3149; H:MWHPR05MB3360.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: NFMS3NuxWcVHa9jEiri8hRdYc6PaysEOXoETGKH5yfetYserXzvxZ7/4Q7ak1U0ynd3LouTftReaipmyNrSFZcY57GewGyWwW6Gohk0f9jwJdcAH7KHO52dEQ1/pT8LhXZxSGb8IARFzlS0szKR23oE+kdZ9pvWqvA1ixA0hGetjwHotAtFNr5GzaeqoJqrtWiXg+twKuq7PxJalox2Hw0wffWy28tymSPed44n0ejAfrZCMon9GHW1S/hxv8S9bby1EKPQcnaaRRceCbpntRoAy9dv7oI4CpyJIqL4bcfWGXAjA9bmlUZuSkkVCupWyc/3slzjrjgqzrIa+930ykqFwpTjYxjue9IuT5pr3Ke1AjbY35xBquNM/8+zucTSJs9S5TlVZeSwg7VOUpudLTSFCPZAJeCM1z3gXZm8bas8=
Content-Type: multipart/alternative; boundary="_000_MWHPR05MB3360B9C9529BB5E8B03392A1D35E0MWHPR05MB3360namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 7dd34cb4-2002-4840-ed53-08d6b160b4aa
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Mar 2019 20:30:22.3810 (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-Transport-CrossTenantHeadersStamped: MWHPR05MB3149
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-03-25_11:, , 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 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1903250146
Archived-At: <https://mailarchive.ietf.org/arch/msg/bcause/LTejp9WALltOJ_OFR3pJC9cqGJg>
Subject: Re: [bcause] [Bcause] interest and scope?
X-BeenThere: bcause@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <bcause.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bcause>, <mailto:bcause-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bcause/>
List-Post: <mailto:bcause@ietf.org>
List-Help: <mailto:bcause-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bcause>, <mailto:bcause-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2019 20:30:35 -0000
Hi Aijun, I hear you have to join the BBF meetings to get the answers to these questions 😉 That being said, this mailing list is not about BNG versus AGF and 5G core. You could use PFCP between BNG-CP and BNG-UP, without any form of 5G convergence. Personally I don’t subscribe to a view that would split BNG domain into 2 clearly isolated segments: the “basic BNG” (TR178) and the “integrated BNG” (with wireless or convergence support). My view is that this is a continuum and we cannot just artificially build a wall in-between. For example, does Diameter Gx on a BNG make it “an integrated BNG”, since this is based on TR-300 (Policy Convergence)? I know “Fixed Network only” operators that use Gx/PCRF. Regards, Greg From: Aijun Wang@China Telecom <wangaj.bri@chinatelecom.cn> Sent: Monday, March 25, 2019 3:56 PM To: Gregory Dalle <gdalle@juniper.net> Cc: Greg Mirsky <gregimirsky@gmail.com>; Vigoureux, Martin (Nokia - FR/Paris-Saclay) <martin.vigoureux@nokia.com>; bcause@ietf.org Subject: Re: [bcause] [Bcause] interest and scope? Hi, Gregory: Can the FMC vision described now in BBF accomplish the following aims: 1. Converge in the control plan for mobile and broadband subscribers for sessions negotiations/management etc. functions? 2. Can the BNG existing in the network be upgraded to support the UPF function with minimum costs(for example, control software upgrades)? Control Plane in Mobile Network is more complex than the counterpart of broadband network, but BNG has more powerful forwarding capabilities than UPF. If the converge consider more how to utilize the advantages of each side, not just defining additional function entities(AGF etc.), I think the solutions will be easily rolled out in real network. Aijun Wang China Telecom On Mar 25, 2019, at 20:23, Gregory Dalle <gdalle=40juniper.net@dmarc.ietf.org<mailto:gdalle=40juniper.net@dmarc.ietf.org>> wrote: Hi Greg M, Commenting back on: “we have heard from several operators that they are interested only in FN (fixed network) DBNG CUPS (….) I don't think that requests by these operators should be ignored”. From what I can track on this mailing list: 1. 2 operators said they are interested only in fixed access BNG 2. 5 operators said they don’t want to restrict the protocol discussion to fixed access only The good news is that these 2 operators are not ignored, as the goal is provide a superset that includes support for basic TR178 BNG as they want. Thanks, Greg D From: bcause <bcause-bounces@ietf.org<mailto:bcause-bounces@ietf.org>> On Behalf Of Greg Mirsky Sent: Monday, March 25, 2019 9:20 AM To: Vigoureux, Martin (Nokia - FR/Paris-Saclay) <martin.vigoureux@nokia.com<mailto:martin.vigoureux@nokia.com>> Cc: bcause@ietf.org<mailto:bcause@ietf.org> Subject: Re: [bcause] [Bcause] interest and scope? Hi Martin, et al., I'd not discuss whether PFCP can be extended to suit yet undocumented DBNG CUPS requirements without changes to its architecture. Many stated that they believe that that is achievable and I'm not to argue with what people believe or don't believe in. I just want to point out that we have heard from several operators that they are interested only in FN (fixed network) DBNG CUPS. I interpret that these operators have and want to keep their fixed and mobile networks operated separately. And even though PFCP may be already is familiar to the operations team that manages their mobile network, introducing the new protocol into the operation of the fixed network will increase their operational cost. More so, operators that are not looking to introduce hybrid access or 5G FMC at any time soon may have a preference on which protocol selection as that is the reflection of their operational model. I don't think that requests by these operators should be ignored and the answer given by SDOs include only PFCP-based DBNG CUPS. I've participated in the discussion and contributed to the charter. The charter intended to work on FN-only DBNG CUPS first and deliver results quickly. Adding hybrid access and 5G FMC could be discussed later, including, based on findings by experts at BBF. Regards, Greg On Mon, Mar 4, 2019 at 2:22 PM Vigoureux, Martin (Nokia - FR/Paris-Saclay) <martin.vigoureux@nokia.com<mailto:martin.vigoureux@nokia.com>> wrote: Hello, as you might know, the RTGWG has hosted, for some time now, a set of documents that relate to the separation of the user plane and control plane of Broadband Network Gateways. These documents can be found at https://datatracker..ietf.org/group/rtgwg/documents/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_group_rtgwg_documents_&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=VhX0NAIO1d7yQxdURKFPY59GAxttnQcfkn45tfRnREs&m=S-4EDvyPmus0NS5LXfp-Ms9zGC_m8iVOllO5lcwmVo0&s=96SauSW0hDod15fcQ8L7ylDy5HchcDuklDH6996dPic&e=> and start with draft-cuspdt-* or draft-wadhwa-* Please read them if you haven't already. Recently, a group of persons has worked together and produced few paragraphs in support of their willingness to see a working group on this topic formed. Considering this, I am sharing this text with the IETF community in order to evaluate * the wider interest in, and willingness to work on, this topic, * the appropriateness of creating a focussed and short-lived working group (as opposed to continuing in rtgwg). To that effect, please read and comment on the text further down, it is here for being debated. As a matter of clarification: me sharing it, instead of the authors doing it, does not carry any special meaning. Important note: this topic has its roots in BroadBand Forum (BBF) with which IETF has exchanged few liaisons on the topic recently. These are important reads: https://datatracker.ietf.org/liaison/1619/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_liaison_1619_&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=VhX0NAIO1d7yQxdURKFPY59GAxttnQcfkn45tfRnREs&m=S-4EDvyPmus0NS5LXfp-Ms9zGC_m8iVOllO5lcwmVo0&s=WR5EeaTa7vVKvnvgUSwSif_tFMJATrrdUp85D9Wauww&e=> https://datatracker.ietf.org/liaison/1615/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_liaison_1615_&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=VhX0NAIO1d7yQxdURKFPY59GAxttnQcfkn45tfRnREs&m=S-4EDvyPmus0NS5LXfp-Ms9zGC_m8iVOllO5lcwmVo0&s=0siKbwwdh2W6FBBMHKJid3k-SaVYNP1bfqYkVAZMWWU&e=> https://datatracker.ietf.org/liaison/1600/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_liaison_1600_&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=VhX0NAIO1d7yQxdURKFPY59GAxttnQcfkn45tfRnREs&m=S-4EDvyPmus0NS5LXfp-Ms9zGC_m8iVOllO5lcwmVo0&s=ntY5jLiyuv6zQcLI7sHo0U-_oSajcmPcqdSQViQ7FAY&e=> https://datatracker.ietf.org/liaison/1566/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_liaison_1566_&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=VhX0NAIO1d7yQxdURKFPY59GAxttnQcfkn45tfRnREs&m=S-4EDvyPmus0NS5LXfp-Ms9zGC_m8iVOllO5lcwmVo0&s=8AnBB1mLQepiil0dgmBKNL1NDtxWktzl2IOEZ9XXNyI&e=> --- Current Broadband Network Gateways (BNGs) that terminate residential broadband subscribers at the edge of service provider networks run as an integrated system where both the subscriber management control plane and traffic forwarding user plane are combined in a single system. In a large network, where the subscriber density is high, it is better to distribute and locate BNG systems closer to the subscribers, especially when the content caches are distributed to reduce backhaul costs and latency. In this scenario, as the BNG footprint grows, the subscriber management control points also proliferate, increasing operational complexity. This trend motivates the broadband network access industry to adopt new architectures that take advantage of the increasing ability to disaggregate and virtualize appropriate network access functions. Additional benefits can be realized by separating subscriber management control plane (CP) and traffic forwarding user plane (UP) for BNGs (referred to as Control and User Plane Separation (CUPS)). That simplifies operations, provides independent location, and scaling for CP and UP functions. A single CP function, running as a centralized VNF, can control and manage multiple UP instances, which may be distributed and separated from the CP via a multi-hop L2 or L3 network. CUPS requires protocols for communication between CP and UP instances: from the CP to the UP to create and manage subscriber state instances and from the UP to the CP to handle relevant solicited or unsolicited events. The proposed Working Group is a narrowly scoped WG tasked to specify communication protocol(s) between the CP and UP of a BNG, a network element whose functions are defined by BBF. A BNG can deliver broadband services to subscriber over wireline access or over multiple access types to accommodate different deployments. The goal of the WG is to define protocol(s) for CUPS that may support multiple deployment scenarios for the BNG. The scope of the work covers protocol requirements, specification of the communications protocol, the information elements to be transferred with that protocol, and YANG data model(s) for Operations and Management as well as security, operational, and transport considerations. --- Thank you Martin -- Bcause mailing list Bcause@ietf.org<mailto:Bcause@ietf.org> https://www.ietf.org/mailman/listinfo/bcause<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bcause&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=VhX0NAIO1d7yQxdURKFPY59GAxttnQcfkn45tfRnREs&m=S-4EDvyPmus0NS5LXfp-Ms9zGC_m8iVOllO5lcwmVo0&s=H-G297qDrFOH-JKFv25D8NyN-fqntWahhcvLjzO-LWM&e=> -- bcause mailing list bcause@ietf.org<mailto:bcause@ietf.org> https://www.ietf.org/mailman/listinfo/bcause<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bcause&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=VhX0NAIO1d7yQxdURKFPY59GAxttnQcfkn45tfRnREs&m=GGbsRmcqJ3a17WOYMLVlwPyVDTIpdb9ItkZSHgdBDaw&s=2TkSZomez3l81DzY7ouAgpNcdTaahpMJNo8-eqzZAUI&e=>
- Re: [bcause] [Bcause] interest and scope? Joel M. Halpern
- [Bcause] interest and scope? Vigoureux, Martin (Nokia - FR/Paris-Saclay)
- [bcause] 答复: [Bcause] interest and scope? qinfengwei
- Re: [bcause] [Bcause] interest and scope? Dolganow, Andrew (Nokia - SG/Singapore)
- Re: [bcause] [Bcause] interest and scope? Dolganow, Andrew (Nokia - SG/Singapore)
- Re: [bcause] [Bcause] interest and scope? Greg Mirsky
- Re: [bcause] [Bcause] interest and scope? Donald Eastlake
- Re: [bcause] interest and scope? Mach Chen
- Re: [bcause] [Bcause] interest and scope? =?utf-8?B?5p2O6JCM6JCM?=
- Re: [bcause] [Bcause] interest and scope? huang.guangping
- Re: [bcause] interest and scope? Miziewicz, Krystof (Nokia - AU/Sydney)
- Re: [bcause] interest and scope? Wadhwa, Sanjay (Nokia - US/Mountain View)
- Re: [bcause] interest and scope? Georgios Karagiannis
- Re: [bcause] interest and scope? Adrian Farrel
- Re: [bcause] [Bcause] interest and scope? Gregory Dalle
- Re: [bcause] [Bcause] interest and scope? Greg Mirsky
- Re: [bcause] [Bcause] interest and scope? Yu Tianpeng
- Re: [bcause] [Bcause] interest and scope? Gregory Dalle
- Re: [bcause] [Bcause] interest and scope? Gregory Dalle
- Re: [bcause] [Bcause] interest and scope? Yu Tianpeng
- Re: [bcause] [Bcause] interest and scope? Donald Eastlake
- [bcause] 答复: [Bcause] interest and scope? qinfengwei
- Re: [bcause] [Bcause] interest and scope? Victor Lopez
- Re: [bcause] [Bcause] interest and scope? eduard.metz
- Re: [bcause] interest and scope? Wadhwa, Sanjay (Nokia - US/Mountain View)
- Re: [bcause] [Bcause] interest and scope? Chase, Chris
- Re: [bcause] [Bcause] interest and scope? Miaofuyou (Miao Fuyou)
- Re: [bcause] interest and scope? Ryan Hoffman
- Re: [bcause] interest and scope? David Allan I
- Re: [bcause] [Bcause] interest and scope? Diego R. Lopez
- [bcause] 答复: interest and scope? Aijun Wang
- Re: [bcause] interest and scope? Miaofuyou (Miao Fuyou)
- Re: [bcause] interest and scope? David Allan I
- Re: [bcause] interest and scope? David Allan I
- Re: [bcause] interest and scope? Miaofuyou (Miao Fuyou)
- Re: [bcause] [Bcause] interest and scope? Gregory Dalle
- Re: [bcause] interest and scope? Wadhwa, Sanjay (Nokia - US/Mountain View)
- [bcause] 答复: interest and scope? Miaofuyou (Miao Fuyou)
- Re: [bcause] 答复: interest and scope? huang.guangping
- Re: [bcause] interest and scope? Wadhwa, Sanjay (Nokia - US/Mountain View)
- Re: [bcause] 答复: interest and scope? Gregory Dalle
- Re: [bcause] 答复: interest and scope? Wadhwa, Sanjay (Nokia - US/Mountain View)
- Re: [bcause] interest and scope? Yu Tianpeng
- Re: [bcause] 答复: interest and scope? Miaofuyou (Miao Fuyou)
- Re: [bcause] interest and scope? Wadhwa, Sanjay (Nokia - US/Mountain View)
- Re: [bcause] interest and scope? Greg Mirsky
- Re: [bcause] interest and scope? Wadhwa, Sanjay (Nokia - US/Mountain View)
- Re: [bcause] 答复: interest and scope? Gregory Dalle
- Re: [bcause] 答复: interest and scope? Rajesh A Shinde
- Re: [bcause] 答复: interest and scope? Miaofuyou (Miao Fuyou)
- Re: [bcause] interest and scope? STARK, BARBARA H
- Re: [bcause] interest and scope? Miaofuyou (Miao Fuyou)
- Re: [bcause] 答复: interest and scope? Muley, Praveen (Nokia - US/Mountain View)
- Re: [bcause] 答复: interest and scope? KEN KO
- Re: [bcause] interest and scope? KEN KO
- Re: [bcause] [Bcause] interest and scope? Greg Mirsky
- Re: [bcause] interest and scope? Mach Chen
- Re: [bcause] interest and scope? David Allan I
- Re: [bcause] interest and scope? Mach Chen
- Re: [bcause] interest and scope? huang.guangping
- Re: [bcause] interest and scope? David Allan I
- [bcause] 答复: interest and scope? Zongning
- Re: [bcause] interest and scope? David Allan I
- Re: [bcause] [Bcause] interest and scope? Gregory Dalle
- Re: [bcause] [Bcause] interest and scope? Greg Mirsky
- Re: [bcause] [Bcause] interest and scope? Gregory Dalle
- Re: [bcause] [Bcause] interest and scope? Aijun Wang@China Telecom
- Re: [bcause] [Bcause] interest and scope? Greg Mirsky
- Re: [bcause] [Bcause] interest and scope? Gregory Dalle
- Re: [bcause] [Bcause] interest and scope? Gregory Dalle
- Re: [bcause] 答复: interest and scope? Adrian Farrel
- Re: [bcause] [Bcause] interest and scope? Dolganow, Andrew (Nokia - SG/Singapore)
- Re: [bcause] [Bcause] interest and scope? eduard.metz
- Re: [bcause] [Bcause] interest and scope? Greg Mirsky
- Re: [bcause] interest and scope? eduard.metz
- Re: [bcause] [Bcause] interest and scope? Dolganow, Andrew (Nokia - SG/Singapore)
- Re: [bcause] interest and scope? Dolganow, Andrew (Nokia - SG/Singapore)
- Re: [bcause] [Bcause] interest and scope? Miaofuyou (Miao Fuyou)
- Re: [bcause] [Bcause] interest and scope? David Allan I
- Re: [bcause] [Bcause] interest and scope? Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [bcause] [Bcause] interest and scope? Aijun Wang@China Telecom
- Re: [bcause] [Bcause] interest and scope? Greg Mirsky
- Re: [bcause] [Bcause] interest and scope? Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [bcause] [Bcause] interest and scope? Greg Mirsky
- Re: [bcause] [Bcause] interest and scope? Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [bcause] [Bcause] interest and scope? Miaofuyou (Miao Fuyou)
- Re: [bcause] [Bcause] interest and scope? David Sinicrope
- Re: [bcause] [Bcause] interest and scope? Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [bcause] [Bcause] interest and scope? Joel M. Halpern
- Re: [bcause] [Bcause] interest and scope? Greg Mirsky
- Re: [bcause] [Bcause] interest and scope? Mach Chen
- Re: [bcause] [Bcause] interest and scope? Wadhwa, Sanjay (Nokia - US/Mountain View)
- Re: [bcause] 答复: interest and scope? KEN KO