[hiprg] About introducing HIP into Telecom Core Network and Clouding Computing //Open talk and investigation
gao.yang2@zte.com.cn Mon, 26 April 2010 10:34 UTC
Return-Path: <gao.yang2@zte.com.cn>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 062F63A694C for <hiprg@core3.amsl.com>; Mon, 26 Apr 2010 03:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.238
X-Spam-Level:
X-Spam-Status: No, score=-99.238 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nkiEWlJpZ8Pc for <hiprg@core3.amsl.com>; Mon, 26 Apr 2010 03:34:52 -0700 (PDT)
Received: from mx7.zte.com.cn (out1.zte.com.cn [202.103.147.172]) by core3.amsl.com (Postfix) with ESMTP id 95B3B3A6808 for <hiprg@irtf.org>; Mon, 26 Apr 2010 03:34:48 -0700 (PDT)
Received: from [192.168.168.1] by [192.168.168.16] with StormMail ESMTP id 57638.1852329331; Mon, 26 Apr 2010 18:30:35 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id o3QAYaGD006479 for <hiprg@irtf.org>; Mon, 26 Apr 2010 18:34:36 +0800 (CST) (envelope-from gao.yang2@zte.com.cn)
To: hiprg@irtf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006
Message-ID: <OF250B8CB7.24033016-ON48257711.0033146B-48257711.003A0E14@zte.com.cn>
From: gao.yang2@zte.com.cn
Date: Mon, 26 Apr 2010 18:32:24 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2010-04-26 18:34:21, Serialize complete at 2010-04-26 18:34:21
Content-Type: multipart/alternative; boundary="=_alternative 003A0E0448257711_="
X-MAIL: mse2.zte.com.cn o3QAYaGD006479
Subject: [hiprg] About introducing HIP into Telecom Core Network and Clouding Computing //Open talk and investigation
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2010 10:34:53 -0000
1.Telecom Core Network IMS(IP Multimedia Subsystem) is aimed for unified user management, unified authentication, unified policy/charging and unified service control, but it is tightly coupled with SIP. While the telecom core network operators want to deploy any non-sip application, they find that the unified platform(IMS) would not be suitable. We may conclude from the situation that, if telecom (core network) operators want to make one infrastructure(unified user management, unified authentication, unified policy/charging and unified service control) suitable for any application(sip and non-sip), they need make an sip decoupling AAA infrastructure at first. Making IMS's AAA based on HIP and IMS's multimedia level still on sip, would make IMS's infrastructure open for any other protocol and application. And if the telecom (core network) operators want to embrace more and more non-sip application, HIP may be the only way. 2.Clouding Computing Some standard cloud/grid computing technology is based on Web. On the web platform, it is easy to bulid one AAA infrastructure and open for appliaction such as SOA. But if we want to build web and non-web(such as RAI) application on the same platform, there's the same problem IMS has. So, if IT industry's could computing want to embrace non-web application, HIP may be the same way again. =================================== Zip : 210012 Tel : 87211 Tel2 :(+86)-025-52877211 e_mail : gao.yang2@zte.com.cn =================================== -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system.