Re: [Hipsec] A question about HIP
Andrei Gurtov <gurtov@cs.helsinki.fi> Thu, 23 October 2008 09:47 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 5F9953A6C45; Thu, 23 Oct 2008 02:47:53 -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 518973A6C45 for <hipsec@core3.amsl.com>; Thu, 23 Oct 2008 02:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 SjgM4ANvR3p1 for <hipsec@core3.amsl.com>; Thu, 23 Oct 2008 02:47:51 -0700 (PDT)
Received: from mail.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by core3.amsl.com (Postfix) with ESMTP id 33E663A6C37 for <hipsec@ietf.org>; Thu, 23 Oct 2008 02:47:51 -0700 (PDT)
Received: from [88.192.47.114] (dsl-hkibrasgw3-ff2fc000-114.dhcp.inet.fi [88.192.47.114]) (AUTH: PLAIN gurtov, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Thu, 23 Oct 2008 12:48:54 +0300 id 0005BF70.49004886.0000590A
Message-ID: <4900486D.4020501@cs.helsinki.fi>
Date: Thu, 23 Oct 2008 12:48:29 +0300
From: Andrei Gurtov <gurtov@cs.helsinki.fi>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: hipsec@ietf.org
References: <0K9600JA5NEBTA@szxml05-in.huawei.com>
In-Reply-To: <0K9600JA5NEBTA@szxml05-in.huawei.com>
Subject: Re: [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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: hipsec-bounces@ietf.org
Errors-To: hipsec-bounces@ietf.org
Check Chapter 6.6 from the HIP book :) http://eu.wiley.com/WileyCDA/WileyTitle/productCd-0470997907.html Andrei Suping ZHAI wrote: > 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 > _______________________________________________ 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