[Hipsec] A question about HIP
Suping ZHAI <zhaisuping@huawei.com> Thu, 23 October 2008 08:25 UTC
Return-Path: <hipsec-bounces@ietf.org>
X-Original-To: hip-archive@lists.ietf.org
Delivered-To: ietfarch-hip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 253713A6AA5; Thu, 23 Oct 2008 01:25:27 -0700 (PDT)
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E2BF23A69AF for <hipsec@core3.amsl.com>; Thu, 23 Oct 2008 01:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.805
X-Spam-Level:
X-Spam-Status: No, score=0.805 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 cdOYe1HB7JIL for <hipsec@core3.amsl.com>; Thu, 23 Oct 2008 01:25:25 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id F1C0B3A68DA for <hipsec@ietf.org>; Thu, 23 Oct 2008 01:25:24 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K960005YNECCK@szxga02-in.huawei.com> for hipsec@ietf.org; Thu, 23 Oct 2008 16:25:24 +0800 (CST)
Received: from huawei.com ([172.24.1.12]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K9600K80NECQU@szxga02-in.huawei.com> for hipsec@ietf.org; Thu, 23 Oct 2008 16:25:24 +0800 (CST)
Received: from zhaisp ([10.111.12.102]) by szxml05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0K9600JA4NEBTA@szxml05-in.huawei.com> for hipsec@ietf.org; Thu, 23 Oct 2008 16:25:24 +0800 (CST)
Date: Thu, 23 Oct 2008 16:25:24 +0800
From: Suping ZHAI <zhaisuping@huawei.com>
To: "hipsec@ietf.org" <hipsec@ietf.org>
Message-id: <0K9600JA5NEBTA@szxml05-in.huawei.com>
MIME-version: 1.0
X-Mailer: Foxmail 4.2 [cn]
Subject: [Hipsec] A question about HIP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: hipsec-bounces@ietf.org
Errors-To: hipsec-bounces@ietf.org
Hi all, After studying HIP for a while, I find that HIP can perfectly solve the mobility/multihoming/security problems which the now existing internet faces. But as to the multicast, which is an important feature which make so many applications such as IPTV, VOD, etc, how to accormmodate it in HIP? In another word, how to support the multicast services with HIP? Can somebody give me a guidance? TIA. Best Regards, Suping ZHAI zhaisuping@huawei.com Tel:0086-10-82836044 Fax:0086-10-82836284 _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec
- Re: [Hipsec] A question about HIP Andrei Gurtov
- [Hipsec] A question about HIP Suping ZHAI
- Re: [Hipsec] A question about HIP Varjonen Samu