IETF Logo Mail Archive

Re: [MEXT] AD review of draft-ietf-mext-aaa-ha-goals-01

"Giaretta, Gerardo" <gerardog@qualcomm.com> Thu, 19 June 2008 16:11 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: mip6-archive@megatron.ietf.org
Delivered-To: ietfarch-mip6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E3BC3A67CF; Thu, 19 Jun 2008 09:11:30 -0700 (PDT)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 72A9D3A67CF for <mext@core3.amsl.com>; Thu, 19 Jun 2008 09:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 R4WwwBH7QyEX for <mext@core3.amsl.com>; Thu, 19 Jun 2008 09:11:28 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 43AB03A66B4 for <mext@ietf.org>; Thu, 19 Jun 2008 09:11:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=gerardog@qualcomm.com; q=dns/txt; s=qcdkim; t=1213891939; x=1245427939; h=x-mimeole:content-class:mime-version:content-type: content-transfer-encoding:subject:date:message-id: in-reply-to:x-ms-has-attach:x-ms-tnef-correlator: thread-topic:thread-index:references:from:to:cc: x-originalarrivaltime:x-ironport-av; z=X-MimeOLE:=20Produced=20By=20Microsoft=20Exchange=20V6.5 |Content-class:=20urn:content-classes:message |MIME-Version:=201.0|Content-Type:=20text/plain=3B=0D=0A =09charset=3D"us-ascii"|Content-Transfer-Encoding:=20quot ed-printable|Subject:=20RE:=20[MEXT]=20AD=20review=20of =20draft-ietf-mext-aaa-ha-goals-01|Date:=20Thu,=2019=20Ju n=202008=2009:12:11=20-0700|Message-ID:=20<CBDFC23ECA34FA 4CBC21675A25C28D6101A38284@NAEX12.na.qualcomm.com> |In-Reply-To:=20<485A83CF.9010000@piuha.net> |X-MS-Has-Attach:=20|X-MS-TNEF-Correlator:=20 |Thread-Topic:=20[MEXT]=20AD=20review=20of=20draft-ietf-m ext-aaa-ha-goals-01|Thread-Index:=20AcjSJkQLVkHOjQ4eRhCLT 2XLNSZx1gAAD/Zg|References:=20<48450C23.2080004@it.uc3m.e s>=20<485A83CF.9010000@piuha.net>|From:=20"Giaretta,=20Ge rardo"=20<gerardog@qualcomm.com>|To:=20"Jari=20Arkko"=20< jari.arkko@piuha.net>,=0D=0A=20=20=20=20=20=20=20=20<draf t-ietf-mext-aaa-ha-goals@tools.ietf.org>|Cc:=20"Pasi=20Er onen"=20<Pasi.Eronen@nokia.com>,=20<dime-chairs@tools.iet f.org>,=0D=0A=20=20=20=20=20=20=20=20<mext@ietf.org> |X-OriginalArrivalTime:=2019=20Jun=202008=2016:12:14.0405 =20(UTC)=20FILETIME=3D[3CB40F50:01C8D227]|X-IronPort-AV: =20E=3DMcAfee=3Bi=3D"5200,2160,5320"=3B=20a=3D"4063011"; bh=Ievz5w+Hi0MI6qXE5iUPBRUDEjVaiz8udEXm677l+CQ=; b=VaRzO4IBFHv5/PV40xkArrsnFmHNZsi8czPttYhxr3VzCdV7aUd2sOFj whvdzhPEizWrwA2+NC0hVHnISfTj+CA8tugrAPcIDmPhOrszqJsAopYM9 ADEDKpb2Ed3CFpr5G+UmiOJKZSOgEiQ1x1Z9HnFaLhQmhrf6gees+dlcY 8=;
X-IronPort-AV: E=McAfee;i="5200,2160,5320"; a="4063011"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Jun 2008 09:12:15 -0700
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m5JGCFk0016916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 19 Jun 2008 09:12:15 -0700
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com [172.30.32.65]) by hamtaro.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id m5JGCE94027466; Thu, 19 Jun 2008 09:12:14 -0700 (PDT)
Received: from NAEX12.na.qualcomm.com ([129.46.51.247]) by SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 19 Jun 2008 09:12:14 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 19 Jun 2008 09:12:11 -0700
Message-ID: <CBDFC23ECA34FA4CBC21675A25C28D6101A38284@NAEX12.na.qualcomm.com>
In-Reply-To: <485A83CF.9010000@piuha.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MEXT] AD review of draft-ietf-mext-aaa-ha-goals-01
Thread-Index: AcjSJkQLVkHOjQ4eRhCLT2XLNSZx1gAAD/Zg
References: <48450C23.2080004@it.uc3m.es> <485A83CF.9010000@piuha.net>
From: "Giaretta, Gerardo" <gerardog@qualcomm.com>
To: Jari Arkko <jari.arkko@piuha.net>, draft-ietf-mext-aaa-ha-goals@tools.ietf.org
X-OriginalArrivalTime: 19 Jun 2008 16:12:14.0405 (UTC) FILETIME=[3CB40F50:01C8D227]
Cc: Pasi Eronen <Pasi.Eronen@nokia.com>, dime-chairs@tools.ietf.org, mext@ietf.org
Subject: Re: [MEXT] AD review of draft-ietf-mext-aaa-ha-goals-01
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

Hi Jari,

Thanks for the review. 

Concerning the solution, it is specified in
http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-09.txt 

Gerardo

> -----Original Message-----
> From: mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] On Behalf
Of
> Jari Arkko
> Sent: Thursday, June 19, 2008 9:06 AM
> To: draft-ietf-mext-aaa-ha-goals@tools.ietf.org
> Cc: Pasi Eronen; dime-chairs@tools.ietf.org; mext@ietf.org
> Subject: [MEXT] AD review of draft-ietf-mext-aaa-ha-goals-01
> 
> I have done my AD review on this document.
> 
> The document is ready to move forward, but I wanted to note something
> regarding requirement G2.12.
> 
> This requirement says that it must be possible to support IKEv2 shared
> secret authentication. I can see some good and bad ways of
implementing
> this in terms of the solutions. Is the solution already in some
document?
> 
> I think we want to pay close attention to how this requirement is
> fulfilled and make sure the architecture is right. (Sending keys vs.
> specific keys for this HA vs. asking the server to calculate an
> authentication value, binding of access keys to things that go across
> accesses, mandatory vs. optional confidentiality of transported keys,
> etc.) I will ask for early security review on the solutions.
> 
> Jari
> 
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext
_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www.ietf.org/mailman/listinfo/mext

v2.23.0 | Report a Bug | By Email