[HOKEY] Change proposal for ERP-AAK - 3: Multiple CAP case support

Qin Wu <bill.wu@huawei.com> Thu, 29 September 2011 09:45 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: hokey@ietfa.amsl.com
Delivered-To: hokey@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D317721F8C8A for <hokey@ietfa.amsl.com>; Thu, 29 Sep 2011 02:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.428
X-Spam-Level:
X-Spam-Status: No, score=-4.428 tagged_above=-999 required=5 tests=[AWL=-0.183, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sp3z2EAS2KYG for <hokey@ietfa.amsl.com>; Thu, 29 Sep 2011 02:45:35 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 7701021F8C94 for <hokey@ietf.org>; Thu, 29 Sep 2011 02:45:34 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSA009F935MKF@szxga04-in.huawei.com> for hokey@ietf.org; Thu, 29 Sep 2011 17:46:34 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSA00LF135MA9@szxga04-in.huawei.com> for hokey@ietf.org; Thu, 29 Sep 2011 17:46:34 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEF30496; Thu, 29 Sep 2011 17:45:49 +0800
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 29 Sep 2011 17:45:43 +0800
Received: from w53375q (10.138.41.130) by szxeml402-hub.china.huawei.com (10.82.67.32) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 29 Sep 2011 17:45:40 +0800
Date: Thu, 29 Sep 2011 17:45:39 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: hokey@ietf.org
Message-id: <29A088215B784663B37041D5BCD3B130@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_icjpmyQdxs15YfpbCErUvw)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
Subject: [HOKEY] Change proposal for ERP-AAK - 3: Multiple CAP case support
X-BeenThere: hokey@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: HOKEY WG Mailing List <hokey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hokey>, <mailto:hokey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hokey>
List-Post: <mailto:hokey@ietf.org>
List-Help: <mailto:hokey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hokey>, <mailto:hokey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2011 09:45:35 -0000

Hi,
As we discussed on the list to the draft-ietf-hokey-erp-aak-04, it is not difficult to support multiple CAP(s) case.
However we should make sure each pMSK is calculated for each CAP using different Sequence number, therefore I propose to do the 
following change to allow two ways to avoid the same pMSK derived for multiple CAP,
one way is 
The multiple sequence numbers can be derived from SEQ field in the message header by following +1 rule.

e.g., we have 3 CAP, the SEQ field is set to the value 100

so the pMSK for CAP A will be derived using seqence number 100.

    the pMSK for CAP B will be derived using sequence number 100+1

   the pMSK for CAP C will be derived using sequence number 100+2



The second way is directly using Sequence number field carried in the TV of the message for each CAP,and mandate

each sequence number asscicated with each CAP must always follow that CAP. Also I think if multiple Sequenced number TLV are carried for each CAP,

the SEQ field in the ERP/AAK message header should be set to smallest  value contained in the  Sequenced number TLVs. This is more flexible way comparing 

with the first way. But I think it will be better to allow both.



Regards!

-Qin