[savi] review: draft-bi-savi-csa-00.txt
ZhangDong <zhangdong_rh@huaweisymantec.com> Wed, 20 August 2008 09:52 UTC
Return-Path: <zhangdong_rh@huaweisymantec.com>
X-Original-To: savi@core3.amsl.com
Delivered-To: savi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BBD93A6BB4 for <savi@core3.amsl.com>; Wed, 20 Aug 2008 02:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.042
X-Spam-Level:
X-Spam-Status: No, score=-0.042 tagged_above=-999 required=5 tests=[AWL=2.557, BAYES_00=-2.599]
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 POrAm6g1YgsM for <savi@core3.amsl.com>; Wed, 20 Aug 2008 02:52:47 -0700 (PDT)
Received: from mta2.huaweisymantec.com (mta2.huaweisymantec.com [121.15.168.143]) by core3.amsl.com (Postfix) with ESMTP id 3A2973A69ED for <savi@ietf.org>; Wed, 20 Aug 2008 02:52:47 -0700 (PDT)
MIME-version: 1.0
Content-disposition: inline
Content-type: text/plain; charset="utf-8"
Received: from hstml02-in.huaweisymantec.com ([172.26.3.42]) by hstga02-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-5.02 (built Oct 12 2007; 32bit)) with ESMTP id <0K5W00IGE8S5W430@hstga02-in.huaweisymantec.com> for savi@ietf.org; Wed, 20 Aug 2008 17:52:54 +0800 (CST)
Received: from huaweisymantec.com ([127.0.0.1]) by hstml02-in.huaweisymantec.com (Sun Java(tm) System Messaging Server 6.3-5.02 (built Oct 12 2007; 32bit)) with ESMTP id <0K5W00FPD8S3MR00@hstml02-in.huaweisymantec.com> for savi@ietf.org; Wed, 20 Aug 2008 17:52:52 +0800 (CST)
Received: from [10.27.140.206] by hstml02-in.huaweisymantec.com (mshttpd); Wed, 20 Aug 2008 17:52:51 +0800
From: ZhangDong <zhangdong_rh@huaweisymantec.com>
To: savi@ietf.org
Message-id: <fc69cc483c10.48ac59f3@huaweisymantec.com>
Date: Wed, 20 Aug 2008 17:52:51 +0800
X-Mailer: Sun Java(tm) System Messenger Express 6.3-5.02 (built Oct 12 2007; 32bit)
Content-language: zh-CN
X-Accept-Language: zh-CN
Priority: normal
Content-transfer-encoding: quoted-printable
Subject: [savi] review: draft-bi-savi-csa-00.txt
X-BeenThere: savi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the SAVI WG <savi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/savi>, <mailto:savi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/savi>
List-Post: <mailto:savi@ietf.org>
List-Help: <mailto:savi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/savi>, <mailto:savi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Aug 2008 09:52:48 -0000
Processor Bi, Wu and Yao,
< If the node is an IPv4 node, the only different case is DHCP. The
< node cannot use a CGA address to send a DHCP solicitation. This can
< be solved by using the address as an identifier, but not as a
< locator. The CGA address in contained in the packet as an option,
< and the host id of the IPv4 address is the hash of the CGA address.
< The signature is computed on the whole packet.
Here, I wonder whether the host id of the IPv4 address created by the hash of the CGA address will bring a collision. In other words, the host id of the IPv4 address may already be used. Perhaps, it should has a duplicate detection.
Best regards.
-----------
Dong Zhang
Huawei Symantec Technologies Co., Ltd
TEL：010-82829263
ADDRESS：Harbour Networks P&D Center. Building 17, ZhongGuanCun Software Park, No.8,
Dongbeiwang West Road, HaiDian District, Beijing, China.
- [savi] review: draft-bi-savi-csa-00.txt ZhangDong
- [savi] review: draft-bi-savi-csa-00.txt ZhangDong