
From vfajardo@tari.toshiba.com  Thu Apr  2 08:59:46 2009
Return-Path: <vfajardo@tari.toshiba.com>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D6A73A6A70 for <pana@core3.amsl.com>; Thu,  2 Apr 2009 08:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 enHYOlN4e5fj for <pana@core3.amsl.com>; Thu,  2 Apr 2009 08:59:45 -0700 (PDT)
Received: from toshi17.tari.toshiba.com (unknown [IPv6:2001:418:1403:0:212:17ff:fe52:7811]) by core3.amsl.com (Postfix) with ESMTP id B111D3A6C67 for <pana@ietf.org>; Thu,  2 Apr 2009 08:58:16 -0700 (PDT)
Received: from [127.0.0.1] (smtp.tari.toshiba.com [172.30.24.10]) by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id n32G3SWZ029128; Thu, 2 Apr 2009 11:03:29 -0500 (EST) (envelope-from vfajardo@tari.toshiba.com)
Message-ID: <49D4E0D4.2020201@tari.toshiba.com>
Date: Thu, 02 Apr 2009 11:59:16 -0400
From: Victor Fajardo <vfajardo@tari.toshiba.com>
User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <49C423FC.6010202@piuha.net> <49C7DB3F.1040704@tari.toshiba.com>
In-Reply-To: <49C7DB3F.1040704@tari.toshiba.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-pana-statemachine@tools.ietf.org, pana@ietf.org
Subject: Re: [Pana] AD review of draft-ietf-pana-statemachine
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2009 15:59:46 -0000

Hi Jari,

I've uploaded a new rev of the pana statemachine draft that addresses 
your comments.

regards,
victor

> Hi Jari,
>
>> Apologies for taking some time to do this. I have reviewed the draft 
>> and I think it is in very good shape. There are one or two technical 
>> problems that require the draft to be revised, unless I missed 
>> something. Please discuss this with me and, if needed, revise the 
>> draft accordingly.
>>
>> Here are my comments:
>>
>>> 7.2. Constants
>>>
>>> FAILED_SESS_TIMEOUT
>>>
>>> Configurable value ...
>>
>> Small editorial problem: Something is inconsistent here.... maybe 
>> call the section "7.2. Configurable Values"?
>
> Ok. This seems reasonable.
>
>>
>>> State: WAIT_PNA
>>
>> Three technical problems:
>>
>> 1. You enter this state in two ways, either because you sent a PING, 
>> or because you wanted to re-authenticate. However, coming back from 
>> the state you go to re-authentication or ping processing depending on 
>> the flag in the answer message. So, if the peer responds with the 
>> wrong flag value, you might accidentally go into, say, OPEN state 
>> even if you really were going to do re-authentication...
>>
>> The fix is is to either note the limitation or split WAIT_PNA into 
>> two different states.
>
> Good catch. It would be best to split the states to avoid this case.
>
>>
>> 2. What happens if you want to initiate re-auth while waiting for 
>> ping response? Perhaps you could state that the relevant variables 
>> are not supposed to be set until you are in OPEN... or you could do 
>> some more radical change.
>
> yes additional text is needed to restrict the firing of these event 
> variables. I'll add them accordingly.
>
>>
>> 3. More seriously, I think you need to support the case that you are 
>> doing ping on one side while the other guy initiates 
>> re-authentication. WAIT_PNA does not support reception of the 
>> relevant messages. This needs to be fixed somehow.
>>
>> Generalizing the last point a little bit, what do you do when there's 
>> termination / ping / re-authentication / initialization in parallel 
>> with something else that the other peer is doing? At the very least, 
>> you need to explicitly decide to discard undesired events in states 
>> (and show that its still according to the RFC). Or, some other type 
>> of a change is needed in the draft.
>
> I agree. race conditions of such kind are not really handled in the 
> fsm (and should be handled). The options of a) discarding un-expected 
> events or b) making assumptions of which events takes precedence in a 
> given state .. are not explicitly/implicitly stated in the rfc. Option 
> a) is not so good from basic the operations and vulnerability 
> point-of-view. Option b) needs some event precedence assumptions which 
> can be:
>
> * Waiting for re-auth reply (pac only)
> - on ping, reply to ping and continue waiting
> - on terminate, give up on re-auth and continue with terminate
>
> * Waiting for re-auth reply (paa only)
> - on ping, ignore ping and continue waiting
> - on terminate, give up on re-auth and continue with terminate
>
> * Waiting for ping reply (pac and paa)
> - on re-auth, give up on ping and continue with re-auth
> - on terminate, give up on ping and continue with terminate
>
> * Waiting for terminate (pac and paa)
> - ingore everything and continue waiting
>
> re-auth for paa and pac is separated so as to conform to the rfc; ping 
> sent only in the access phase. if these assumptions are reasonable 
> (??) then I can introduce event handlers for them.
>
>>
>>> ------------------------------
>>> State: INITIAL (Initial State)
>>> ------------------------------
>>>
>>> Initialization Action:
>>>
>>> OPTIMIZED_INIT=Set|Unset;
>>> NONCE_SENT=Unset;
>>> RTX_COUNTER=0;
>>> RtxTimerStop();
>>>
>>> ...
>>>
>>> - - - - - - - - - - - - - - (PAN Handling) - - - - - - - - - -
>>> Rx:PAN[S] && if (PAN.exist_avp WAIT_EAP_MSG
>>> ((OPTIMIZED_INIT == ("EAP-Payload"))
>>> Unset) || TxEAP();
>>> PAN.exist_avp else {
>>> ("EAP-Payload")) EAP_Restart();
>>> SessionTimerReStart
>>> (FAILED_SESS_TIMEOUT);
>>> }
>>>
>>> Rx:PAN[S] && None(); WAIT_PAN_OR_PAR
>>> (OPTIMIZED_INIT ==
>>> Set) &&
>>> ! PAN.exist_avp
>>> ("EAP-Payload")
>>
>> Observation: the two actions do not cover all possible combinations, 
>> e.g., not Rx:PAN[S] && OPTIMIZED_INIT == Unset && 
>> !PAN.exist_avp("EAP-Payload").
>
> The 1st and 2nd event condition (PAN handling shown above) is suppose 
> to handle all relevant combinations. In the example you mentioned, the 
> 1st event condition will be triggered (by OPTIMIZED_INIT == Unset) and 
> the action takes care of checking "EAP-Payload".
>
>>
>> You are setting OPTIMIZED_INIT to a value at the time that the state 
>> machine is created. What if it disagrees with the contents of the PAN 
>> that you receive from the network?
>
> The current PAA event conditions was intended to handle both cases 
> where the PAN agrees (w/ EAP-Payload) or disagress (w/o EAP-Payload) 
> with OPTIMIZED_INIT. This is why the 1st event condition for PAN 
> handling is an OR (||); to handle most of the combinations. The 2nd 
> condition for PAN handling covers the case where there is disagreement 
> and optimized inits will not take place. In all cases, it proceeds 
> accordingly.
>
> regards,
> victor
>
>>
>> Jari
>>
>> _______________________________________________
>> Pana mailing list
>> Pana@ietf.org
>> https://www.ietf.org/mailman/listinfo/pana
>>
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
>
>


From root@core3.amsl.com  Thu Apr  2 09:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: pana@ietf.org
Delivered-To: pana@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id CCE1F3A68B2; Thu,  2 Apr 2009 09:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090402160001.CCE1F3A68B2@core3.amsl.com>
Date: Thu,  2 Apr 2009 09:00:01 -0700 (PDT)
Cc: pana@ietf.org
Subject: [Pana] I-D Action:draft-ietf-pana-statemachine-10.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2009 16:00:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol for carrying Authentication for Network Access Working Group of the IETF.


	Title           : State Machines for Protocol for Carrying Authentication for Network Access (PANA)
	Author(s)       : V. Fajardo, et al.
	Filename        : draft-ietf-pana-statemachine-10.txt
	Pages           : 39
	Date            : 2009-04-02

This document defines the conceptual state machines for the Protocol
for Carrying Authentication for Network Access (PANA).  The state
machines consist of the PANA Client (PaC) state machine and the PANA
Authentication Agent (PAA) state machine.  The two state machines
show how PANA can interface with the EAP state machines.  The state
machines and associated model are informative only.  Implementations
may achieve the same results using different methods.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pana-statemachine-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pana-statemachine-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-04-02084926.I-D@ietf.org>


--NextPart--

From yohba@tari.toshiba.com  Thu Apr  2 12:40:05 2009
Return-Path: <yohba@tari.toshiba.com>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0CA93A6DF4 for <pana@core3.amsl.com>; Thu,  2 Apr 2009 12:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.015
X-Spam-Level: 
X-Spam-Status: No, score=-1.015 tagged_above=-999 required=5 tests=[AWL=-1.028, BAYES_00=-2.599, FAKE_REPLY_C=2.012, J_CHICKENPOX_82=0.6]
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 P6pHFdeFKkrt for <pana@core3.amsl.com>; Thu,  2 Apr 2009 12:40:04 -0700 (PDT)
Received: from toshi17.tari.toshiba.com (unknown [IPv6:2001:418:1403:0:212:17ff:fe52:7811]) by core3.amsl.com (Postfix) with ESMTP id 9CD9A3A6AC9 for <pana@ietf.org>; Thu,  2 Apr 2009 12:40:04 -0700 (PDT)
Received: from steelhead.localdomain (ns.tari.toshiba.com [172.30.24.10]) by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id n32JjCGP030896; Thu, 2 Apr 2009 14:45:13 -0500 (EST) (envelope-from yohba@tari.toshiba.com)
Received: from ohba by steelhead.localdomain with local (Exim 4.69) (envelope-from <yohba@tari.toshiba.com>) id 1LpSgU-0006Ig-Oj; Thu, 02 Apr 2009 15:34:42 -0400
Date: Thu, 2 Apr 2009 15:34:42 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: Alper Yegin <alper.yegin@yegin.org>
Message-ID: <20090402193442.GE19662@steelhead.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: pana@ietf.org, 'Glen Zorn' <glenzorn@comcast.net>, Basavaraj.Patil@nokia.com
Subject: Re: [Pana] WGLC comments on draft-ietf-pana-preauth-04
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2009 19:40:05 -0000

I thought more about this, and the new attribute corresponds 
to the 'E' bit setting.  

Attached=Yes <-> 'E' bit cleared
Attached=No  <-> 'E' bit set

So I think what we need to define as a new PANA session attribute is
the 'E' bit value.

Yoshihiro Ohba


On Fri, Mar 13, 2009 at 11:19:26AM +0200, Alper Yegin wrote:
> Hi Yoshi,
> 
> What I'm thinking is, there'd be a new attribute associated with the PANA
> session: 
> 
> 	Attached: Yes/No. Indicates whether the PaC is attached to the
> access network or not.
> 
> At the time of pre-auth and up until the PaC moves to the target network,
> this attribute is set to No. If the network detects that PaC has detached
> (via some lower-layer indications), it can set this to No again. If the PaC
> moves and performs pre-auth to maintain its session, it shall be set to No
> again.
> 
> So, at any time a PaC is:
> 
> - authenticated/authorized and attached, or
> - authenticated/authorized and not attached, or
> 
> Does this make sense?
> 
> Alper
> 
> 
> 
> 
> 
> 
> 
> 
> 
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Wednesday, March 11, 2009 11:12 PM
> > To: Alper Yegin
> > Cc: 'Glen Zorn'; 'Glen Zorn'; pana@ietf.org; Basavaraj.Patil@nokia.com
> > Subject: Re: WGLC comments on draft-ietf-pana-preauth-04
> > 
> > On Fri, Feb 13, 2009 at 11:36:38AM +0200, Alper Yegin wrote:
> > > > > > In the same section, it appears that "pre-authorization" is
> > simply
> > > > a
> > > > > > pre-provisioned filter applied to all traffic but that is not
> > > > > actually
> > > > > > clear
> > > > > > from the document.
> > > > >
> > > > > Document says:
> > > > >
> > > > > 	Pre-authorization:  An authorization for a PaC, made by a
> > CPAA
> > > > > for
> > > > >       the PaC at the time of pre-authentication.
> > > > >
> > > > > Not sure where a "pre-provisioned" filter comes into play.
> > Basically
> > > > > pre-authorization is the state a PaC reaches when it completes a
> > > > > successful
> > > > > pre-authentication. And post-authorization is the state a PaC
> > reaches
> > > > > when
> > > > > it attaches to one of the candidate networks with whom it has
> > reached
> > > > > pre-authorization state.
> > > >
> > > > OK, so what relation do these states have to the arrival of AAA
> > > > authorization?  My comment about pre-provisioned filters pertained
> > to
> > > > the
> > > > authorization state before the arrival of a RADIUS Access-Accept
> > > > message,
> > > > for example.  As I noted later, the transition between the
> > > > "pre-authorization" & "post-authorization" states doesn't appear to
> > > > actually
> > > > have anything to do with authorization.  In any case, this whole
> > thing
> > > > is
> > > > pretty confusing & I think that it would be a good idea to clarify
> > it.
> > >
> > > I agree.
> > >
> > > There are no two separate AAA authorizations taking place. There is
> > only one
> > > RADIUS Access-Accept.
> > >
> > > I wonder if we lose anything if we were to drop these new terms: pre-
> > authz,
> > > post-authz.
> > >
> > > What we really mean to convey is: A PaC is authorized on the
> > candidate PAA
> > > by means of pre-authentication procedure prior to the PaC's
> > attachment to
> > > the PAA's network (candidate network).
> > 
> > Commenting as editor, I need more specific guidances on text changes
> > with regard to which terms should be used instead of
> > pre-authz/post-authz.  Can you help?
> > 
> > Regards,
> > Yoshihiro Ohba
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana
> 

From jari.arkko@piuha.net  Mon Apr  6 06:10:04 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 704723A6C20 for <pana@core3.amsl.com>; Mon,  6 Apr 2009 06:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  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 doYIf7xhd+Ts for <pana@core3.amsl.com>; Mon,  6 Apr 2009 06:10:03 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id EA7CA3A6C0A for <pana@ietf.org>; Mon,  6 Apr 2009 06:10:02 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id E88711986D8; Mon,  6 Apr 2009 16:11:07 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 8043B198674; Mon,  6 Apr 2009 16:11:07 +0300 (EEST)
Message-ID: <49D9FF64.1030803@piuha.net>
Date: Mon, 06 Apr 2009 16:11:00 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Victor Fajardo <vfajardo@tari.toshiba.com>
References: <49C423FC.6010202@piuha.net> <49C7DB3F.1040704@tari.toshiba.com> <49D4E0D4.2020201@tari.toshiba.com>
In-Reply-To: <49D4E0D4.2020201@tari.toshiba.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: draft-ietf-pana-statemachine@tools.ietf.org, pana@ietf.org
Subject: Re: [Pana] AD review of draft-ietf-pana-statemachine
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 13:10:04 -0000

I'm happy with the new version. I'm moving the draft forward. Thanks for 
the quick update!

Jari

Victor Fajardo wrote:
> Hi Jari,
>
> I've uploaded a new rev of the pana statemachine draft that addresses 
> your comments.
>
> regards,
> victor
>
>> Hi Jari,
>>
>>> Apologies for taking some time to do this. I have reviewed the draft 
>>> and I think it is in very good shape. There are one or two technical 
>>> problems that require the draft to be revised, unless I missed 
>>> something. Please discuss this with me and, if needed, revise the 
>>> draft accordingly.
>>>
>>> Here are my comments:
>>>
>>>> 7.2. Constants
>>>>
>>>> FAILED_SESS_TIMEOUT
>>>>
>>>> Configurable value ...
>>>
>>> Small editorial problem: Something is inconsistent here.... maybe 
>>> call the section "7.2. Configurable Values"?
>>
>> Ok. This seems reasonable.
>>
>>>
>>>> State: WAIT_PNA
>>>
>>> Three technical problems:
>>>
>>> 1. You enter this state in two ways, either because you sent a PING, 
>>> or because you wanted to re-authenticate. However, coming back from 
>>> the state you go to re-authentication or ping processing depending 
>>> on the flag in the answer message. So, if the peer responds with the 
>>> wrong flag value, you might accidentally go into, say, OPEN state 
>>> even if you really were going to do re-authentication...
>>>
>>> The fix is is to either note the limitation or split WAIT_PNA into 
>>> two different states.
>>
>> Good catch. It would be best to split the states to avoid this case.
>>
>>>
>>> 2. What happens if you want to initiate re-auth while waiting for 
>>> ping response? Perhaps you could state that the relevant variables 
>>> are not supposed to be set until you are in OPEN... or you could do 
>>> some more radical change.
>>
>> yes additional text is needed to restrict the firing of these event 
>> variables. I'll add them accordingly.
>>
>>>
>>> 3. More seriously, I think you need to support the case that you are 
>>> doing ping on one side while the other guy initiates 
>>> re-authentication. WAIT_PNA does not support reception of the 
>>> relevant messages. This needs to be fixed somehow.
>>>
>>> Generalizing the last point a little bit, what do you do when 
>>> there's termination / ping / re-authentication / initialization in 
>>> parallel with something else that the other peer is doing? At the 
>>> very least, you need to explicitly decide to discard undesired 
>>> events in states (and show that its still according to the RFC). Or, 
>>> some other type of a change is needed in the draft.
>>
>> I agree. race conditions of such kind are not really handled in the 
>> fsm (and should be handled). The options of a) discarding un-expected 
>> events or b) making assumptions of which events takes precedence in a 
>> given state .. are not explicitly/implicitly stated in the rfc. 
>> Option a) is not so good from basic the operations and vulnerability 
>> point-of-view. Option b) needs some event precedence assumptions 
>> which can be:
>>
>> * Waiting for re-auth reply (pac only)
>> - on ping, reply to ping and continue waiting
>> - on terminate, give up on re-auth and continue with terminate
>>
>> * Waiting for re-auth reply (paa only)
>> - on ping, ignore ping and continue waiting
>> - on terminate, give up on re-auth and continue with terminate
>>
>> * Waiting for ping reply (pac and paa)
>> - on re-auth, give up on ping and continue with re-auth
>> - on terminate, give up on ping and continue with terminate
>>
>> * Waiting for terminate (pac and paa)
>> - ingore everything and continue waiting
>>
>> re-auth for paa and pac is separated so as to conform to the rfc; 
>> ping sent only in the access phase. if these assumptions are 
>> reasonable (??) then I can introduce event handlers for them.
>>
>>>
>>>> ------------------------------
>>>> State: INITIAL (Initial State)
>>>> ------------------------------
>>>>
>>>> Initialization Action:
>>>>
>>>> OPTIMIZED_INIT=Set|Unset;
>>>> NONCE_SENT=Unset;
>>>> RTX_COUNTER=0;
>>>> RtxTimerStop();
>>>>
>>>> ...
>>>>
>>>> - - - - - - - - - - - - - - (PAN Handling) - - - - - - - - - -
>>>> Rx:PAN[S] && if (PAN.exist_avp WAIT_EAP_MSG
>>>> ((OPTIMIZED_INIT == ("EAP-Payload"))
>>>> Unset) || TxEAP();
>>>> PAN.exist_avp else {
>>>> ("EAP-Payload")) EAP_Restart();
>>>> SessionTimerReStart
>>>> (FAILED_SESS_TIMEOUT);
>>>> }
>>>>
>>>> Rx:PAN[S] && None(); WAIT_PAN_OR_PAR
>>>> (OPTIMIZED_INIT ==
>>>> Set) &&
>>>> ! PAN.exist_avp
>>>> ("EAP-Payload")
>>>
>>> Observation: the two actions do not cover all possible combinations, 
>>> e.g., not Rx:PAN[S] && OPTIMIZED_INIT == Unset && 
>>> !PAN.exist_avp("EAP-Payload").
>>
>> The 1st and 2nd event condition (PAN handling shown above) is suppose 
>> to handle all relevant combinations. In the example you mentioned, 
>> the 1st event condition will be triggered (by OPTIMIZED_INIT == 
>> Unset) and the action takes care of checking "EAP-Payload".
>>
>>>
>>> You are setting OPTIMIZED_INIT to a value at the time that the state 
>>> machine is created. What if it disagrees with the contents of the 
>>> PAN that you receive from the network?
>>
>> The current PAA event conditions was intended to handle both cases 
>> where the PAN agrees (w/ EAP-Payload) or disagress (w/o EAP-Payload) 
>> with OPTIMIZED_INIT. This is why the 1st event condition for PAN 
>> handling is an OR (||); to handle most of the combinations. The 2nd 
>> condition for PAN handling covers the case where there is 
>> disagreement and optimized inits will not take place. In all cases, 
>> it proceeds accordingly.
>>
>> regards,
>> victor
>>
>>>
>>> Jari
>>>
>>> _______________________________________________
>>> Pana mailing list
>>> Pana@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pana
>>>
>>
>>
>> ______________________________________________________________________
>> This email has been scanned by the MessageLabs Email Security System.
>> For more information please visit http://www.messagelabs.com/email 
>> ______________________________________________________________________
>>
>>
>
>
>


From jari.arkko@piuha.net  Mon Apr  6 06:15:14 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 082BB3A6C6B for <pana@core3.amsl.com>; Mon,  6 Apr 2009 06:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  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 tRBah0TdD4Az for <pana@core3.amsl.com>; Mon,  6 Apr 2009 06:15:13 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 2FEB73A6782 for <pana@ietf.org>; Mon,  6 Apr 2009 06:15:13 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 3D625198723 for <pana@ietf.org>; Mon,  6 Apr 2009 16:16:18 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id EDF8819867A for <pana@ietf.org>; Mon,  6 Apr 2009 16:16:17 +0300 (EEST)
Message-ID: <49DA009B.30507@piuha.net>
Date: Mon, 06 Apr 2009 16:16:11 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: pana@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [Pana] pana-ipsec status?
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 13:15:14 -0000

What needs to be done to draft-ietf-pana-ipsec to move it forward? Or 
are the serious technical issues based on earlier reviews or lack of 
energy? I would like to move forward with the remaining work items...

Jari


From wwwrun@core3.amsl.com  Mon Apr  6 08:09:09 2009
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: pana@ietf.org
Delivered-To: pana@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id C5BB83A6808; Mon,  6 Apr 2009 08:09:09 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20090406150909.C5BB83A6808@core3.amsl.com>
Date: Mon,  6 Apr 2009 08:09:09 -0700 (PDT)
Cc: pana@ietf.org
Subject: [Pana] Last Call: draft-ietf-pana-statemachine (State Machines for Protocol for Carrying Authentication for Network Access (PANA)) to Informational RFC
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 15:09:09 -0000

The IESG has received a request from the Protocol for carrying 
Authentication for Network Access WG (pana) to consider the following
document:

- 'State Machines for Protocol for Carrying Authentication for Network 
   Access (PANA) '
   <draft-ietf-pana-statemachine-10.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-04-20. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-pana-statemachine-10.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13226&rfc_flag=0

The following IPR Declarations may be related to this I-D:




From Basavaraj.Patil@nokia.com  Mon Apr  6 08:23:32 2009
Return-Path: <Basavaraj.Patil@nokia.com>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E2BC3A6C8F for <pana@core3.amsl.com>; Mon,  6 Apr 2009 08:23:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.291
X-Spam-Level: 
X-Spam-Status: No, score=-6.291 tagged_above=-999 required=5 tests=[AWL=0.308,  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 7R8nx5q5DyXr for <pana@core3.amsl.com>; Mon,  6 Apr 2009 08:23:25 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 51DEB28C1F1 for <pana@ietf.org>; Mon,  6 Apr 2009 08:23:25 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n36FO0OV011008; Mon, 6 Apr 2009 10:24:31 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 6 Apr 2009 18:24:17 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 6 Apr 2009 18:24:17 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 6 Apr 2009 18:24:12 +0300
Received: from NOK-EUMSG-03.mgdnok.nokia.com ([65.54.30.108]) by nok-am1mhub-01.mgdnok.nokia.com ([65.54.30.5]) with mapi; Mon, 6 Apr 2009 17:24:12 +0200
From: <Basavaraj.Patil@nokia.com>
To: <jari.arkko@piuha.net>, <pana@ietf.org>
Date: Mon, 6 Apr 2009 17:24:21 +0200
Thread-Topic: [Pana] pana-ipsec status?
Thread-Index: Acm2ueYDslYhPVWNSImTQdqEI2gbZQAEdw3/
Message-ID: <C5FF88D5.26364%basavaraj.patil@nokia.com>
In-Reply-To: <49DA009B.30507@piuha.net>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 06 Apr 2009 15:24:12.0503 (UTC) FILETIME=[BD29F670:01C9B6CB]
X-Nokia-AV: Clean
Cc: lionel.morand@orange-ftgroup.com
Subject: Re: [Pana] pana-ipsec status?
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 15:23:32 -0000

Hi Jari,

There is a lack of energy from the original editor of this I-D. We did
however get a volunteer (Lionel Morand) to take over the editorship and
complete this I-D.=20
If we do not see traction on this I-D in the next few weeks, we can drop it
from the WG I-D list and move on.

-Raj


On 4/6/09 8:16 AM, "ext Jari Arkko" <jari.arkko@piuha.net> wrote:

> What needs to be done to draft-ietf-pana-ipsec to move it forward? Or
> are the serious technical issues based on earlier reviews or lack of
> energy? I would like to move forward with the remaining work items...
>=20
> Jari
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana


From Basavaraj.Patil@nokia.com  Thu Apr  9 12:05:23 2009
Return-Path: <Basavaraj.Patil@nokia.com>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A9DA3A6AA6 for <pana@core3.amsl.com>; Thu,  9 Apr 2009 12:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.314
X-Spam-Level: 
X-Spam-Status: No, score=-6.314 tagged_above=-999 required=5 tests=[AWL=0.285,  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 7ZcYAVBMYgTO for <pana@core3.amsl.com>; Thu,  9 Apr 2009 12:04:45 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id EAEB03A67E2 for <pana@ietf.org>; Thu,  9 Apr 2009 12:04:44 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n39J5mtL027539 for <pana@ietf.org>; Thu, 9 Apr 2009 22:05:49 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 9 Apr 2009 22:05:49 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 9 Apr 2009 22:05:44 +0300
Received: from nok-am1mhub-06.mgdnok.nokia.com (65.54.30.10) by NOK-AM1MHUB-03.mgdnok.nokia.com (65.54.30.7) with Microsoft SMTP Server (TLS) id 8.1.340.0; Thu, 9 Apr 2009 21:05:44 +0200
Received: from NOK-EUMSG-03.mgdnok.nokia.com ([65.54.30.108]) by nok-am1mhub-06.mgdnok.nokia.com ([65.54.30.10]) with mapi; Thu, 9 Apr 2009 21:05:44 +0200
From: <Basavaraj.Patil@nokia.com>
To: <pana@ietf.org>
Date: Thu, 9 Apr 2009 21:05:53 +0200
Thread-Topic: What to do with I-D: draft-ietf-pana-ipsec
Thread-Index: Acm5RjQd3k8ky4ZpMkCBtsGH7Jf/tQ==
Message-ID: <C603B141.26687%basavaraj.patil@nokia.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 09 Apr 2009 19:05:44.0879 (UTC) FILETIME=[2F46D3F0:01C9B946]
X-Nokia-AV: Clean
Subject: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2009 19:05:23 -0000

Hello,

The PANA WG developed the concept of securing the link between the host and
the access router (PaC and EP) using IPsec. The I-D: draft-ietf-pana-ipsec
has not been revised since 2005 and I do not see any interest in doing so
either.=20
Additionally I believe that the need to use PANA for securing the access
link does not have much traction.

Two questions:
1. Should we drop this I-D from the PANA WG scope
2. If the answer to (1) is no, are there any volunteers who would be willin=
g
to revise the I-D and complete the work.

-Raj=20


From gwz@net-zen.net  Thu Apr  9 18:24:09 2009
Return-Path: <gwz@net-zen.net>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC19E28C11A for <pana@core3.amsl.com>; Thu,  9 Apr 2009 18:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 lcXa1fWeLhlX for <pana@core3.amsl.com>; Thu,  9 Apr 2009 18:24:09 -0700 (PDT)
Received: from smtpauth21.prod.mesa1.secureserver.net (smtpauth21.prod.mesa1.secureserver.net [64.202.165.38]) by core3.amsl.com (Postfix) with SMTP id EDA7F28C119 for <pana@ietf.org>; Thu,  9 Apr 2009 18:24:08 -0700 (PDT)
Received: (qmail 27034 invoked from network); 10 Apr 2009 01:25:17 -0000
Received: from unknown (124.120.223.210) by smtpauth21.prod.mesa1.secureserver.net (64.202.165.38) with ESMTP; 10 Apr 2009 01:25:16 -0000
From: "Glen Zorn" <gwz@net-zen.net>
To: <Basavaraj.Patil@nokia.com>
References: <C603B141.26687%basavaraj.patil@nokia.com>
In-Reply-To: <C603B141.26687%basavaraj.patil@nokia.com>
Date: Fri, 10 Apr 2009 08:25:07 +0700
Organization: Network Zen
Message-ID: <007201c9b97b$30c606d0$92521470$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acm5RjQd3k8ky4ZpMkCBtsGH7Jf/tQANNbYQ
Content-Language: en-us
Cc: pana@ietf.org
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2009 01:24:09 -0000

> Hello,
> 
> The PANA WG developed the concept of securing the link between the host
> and
> the access router (PaC and EP) using IPsec. The I-D: draft-ietf-pana-
> ipsec
> has not been revised since 2005 and I do not see any interest in doing
> so
> either.
> Additionally I believe that the need to use PANA for securing the
> access
> link does not have much traction.
> 
> Two questions:
> 1. Should we drop this I-D from the PANA WG scope

No.

> 2. If the answer to (1) is no, are there any volunteers who would be
> willing
> to revise the I-D and complete the work.

I'll do it.

> 
> -Raj
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana



From julien.bournelle@gmail.com  Thu Apr  9 23:59:30 2009
Return-Path: <julien.bournelle@gmail.com>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 213353A6D41 for <pana@core3.amsl.com>; Thu,  9 Apr 2009 23:59:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.86
X-Spam-Level: 
X-Spam-Status: No, score=-1.86 tagged_above=-999 required=5 tests=[AWL=0.739,  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 tqoINShlvx7N for <pana@core3.amsl.com>; Thu,  9 Apr 2009 23:59:29 -0700 (PDT)
Received: from mail-bw0-f169.google.com (mail-bw0-f169.google.com [209.85.218.169]) by core3.amsl.com (Postfix) with ESMTP id 1EDB63A6845 for <pana@ietf.org>; Thu,  9 Apr 2009 23:59:28 -0700 (PDT)
Received: by bwz17 with SMTP id 17so918094bwz.37 for <pana@ietf.org>; Fri, 10 Apr 2009 00:00:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=w2io6aST0myq1sSaarS3ipVyy0kpM809XHm84nXZkBA=; b=Q+Enjt0OW/SnvPFx5HEby2oPBcgXZHRXG88YLR3GfPOT7bJ8gdb/weGM0LLQk/o3n9 IpgZXm3oF+VFywqhZvpQoSQqC13SE/yaaTZ8PAzpwmVVO9pG6kytjkDNN8Iz87flI5RN Knkc+Pbg1tR7DJj0Kv1wWgjgyy0SP6ytnK0uE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=eV+LNM0KfIiPXQExFq8jbTTSwnJ1tsWFUDF01inL/mFTAao1u7KSmIoX3lEQa9UDQj FwYpN/yFEQF3oY0MRKRDPwHBQ5fe2Vo6HTqG/H8CgNdF6LcnACpwiSHayCVVet/Wf6v4 K4X9frRH9Q9gm3w8hOiwWS7bB8Hqxs8cey4Sg=
MIME-Version: 1.0
Received: by 10.239.163.69 with SMTP id o5mr98235hbd.40.1239346836398; Fri, 10  Apr 2009 00:00:36 -0700 (PDT)
In-Reply-To: <007201c9b97b$30c606d0$92521470$@net>
References: <C603B141.26687%basavaraj.patil@nokia.com> <007201c9b97b$30c606d0$92521470$@net>
Date: Fri, 10 Apr 2009 09:00:36 +0200
Message-ID: <5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com>
From: Julien Bournelle <julien.bournelle@gmail.com>
To: Glen Zorn <gwz@net-zen.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: pana@ietf.org, Basavaraj.Patil@nokia.com
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2009 06:59:30 -0000

Hello,

On Fri, Apr 10, 2009 at 3:25 AM, Glen Zorn <gwz@net-zen.net> wrote:
>> Hello,
>>
>> The PANA WG developed the concept of securing the link between the host
>> and
>> the access router (PaC and EP) using IPsec. The I-D: draft-ietf-pana-
>> ipsec
>> has not been revised since 2005 and I do not see any interest in doing
>> so
>> either.
>> Additionally I believe that the need to use PANA for securing the
>> access
>> link does not have much traction.
>>
>> Two questions:
>> 1. Should we drop this I-D from the PANA WG scope
>
> No.

No. If one day PANA is used. This would be a missing piece. Thus I
would prefer to keep it.

>
>> 2. If the answer to (1) is no, are there any volunteers who would be
>> willing
>> to revise the I-D and complete the work.
>
> I'll do it.

If needed, I can help.

 Regards,

 Julien

>
>>
>> -Raj
>>
>> _______________________________________________
>> Pana mailing list
>> Pana@ietf.org
>> https://www.ietf.org/mailman/listinfo/pana
>
>
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana
>

From jari.arkko@piuha.net  Mon Apr 13 02:11:09 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE3AB3A6C21 for <pana@core3.amsl.com>; Mon, 13 Apr 2009 02:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 RcKb3y8nCYWT for <pana@core3.amsl.com>; Mon, 13 Apr 2009 02:11:09 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id D9ECE3A6B6E for <pana@ietf.org>; Mon, 13 Apr 2009 02:11:08 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 7B4F119871D; Mon, 13 Apr 2009 12:12:18 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 1CFA9198665; Mon, 13 Apr 2009 12:12:18 +0300 (EEST)
Message-ID: <49E301EA.10605@piuha.net>
Date: Mon, 13 Apr 2009 12:12:10 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Julien Bournelle <julien.bournelle@gmail.com>, Glen Zorn <gwz@net-zen.net>
References: <C603B141.26687%basavaraj.patil@nokia.com>	<007201c9b97b$30c606d0$92521470$@net> <5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com>
In-Reply-To: <5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: Basavaraj.Patil@nokia.com, pana@ietf.org
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2009 09:11:09 -0000

My primary issue with this document was the lack of cycles, if there had 
been no one interested in taking it to completion we should have dropped 
it. Since you two are volunteering, can you work with the chairs to take 
over the work, and do whatever is needed to bring the document to a 
reasonable state?

Jari


From root@core3.amsl.com  Mon Apr 13 08:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: pana@ietf.org
Delivered-To: pana@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 3AEFE3A6DC6; Mon, 13 Apr 2009 08:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090413154501.3AEFE3A6DC6@core3.amsl.com>
Date: Mon, 13 Apr 2009 08:45:01 -0700 (PDT)
Cc: pana@ietf.org
Subject: [Pana] I-D Action:draft-ietf-pana-preauth-05.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2009 15:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol for carrying Authentication for Network Access Working Group of the IETF.


	Title           : Pre-authentication Support for PANA
	Author(s)       : Y. Ohba
	Filename        : draft-ietf-pana-preauth-05.txt
	Pages           : 9
	Date            : 2009-04-13

This document defines an extension to the Protocol for carrying
Authentication for Network Access (PANA) for proactively establishing
a PANA security association between a PANA client in one access
network and a PANA authentication agent in another access network to
which the PANA client may move.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pana-preauth-05.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pana-preauth-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-04-13083034.I-D@ietf.org>


--NextPart--

From yohba@tari.toshiba.com  Mon Apr 13 08:54:49 2009
Return-Path: <yohba@tari.toshiba.com>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9A9A3A6DB0 for <pana@core3.amsl.com>; Mon, 13 Apr 2009 08:54:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.028
X-Spam-Level: 
X-Spam-Status: No, score=-3.028 tagged_above=-999 required=5 tests=[AWL=1.061,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 gft6bZR0S9ek for <pana@core3.amsl.com>; Mon, 13 Apr 2009 08:54:36 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by core3.amsl.com (Postfix) with ESMTP id BAF033A6DD6 for <pana@ietf.org>; Mon, 13 Apr 2009 08:54:35 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id n3DFtjS0009096 for <pana@ietf.org>; Tue, 14 Apr 2009 00:55:45 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id n3DFtjOt024802 for pana@ietf.org; Tue, 14 Apr 2009 00:55:45 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id AAA24801; Tue, 14 Apr 2009 00:55:45 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id n3DFti0h024761 for <pana@ietf.org>; Tue, 14 Apr 2009 00:55:44 +0900 (JST)
Received: from ivp1.toshiba.co.jp by toshiba.co.jp id n3DFtixw013614; Tue, 14 Apr 2009 00:55:44 +0900 (JST)
Received: from ext-gw.toshiba.co.jp by ivp1.toshiba.co.jp  with ESMTP id n3DFthwg012916 for <pana@ietf.org>; Tue, 14 Apr 2009 00:55:43 +0900 (JST)
Received: from toshi17.tari.toshiba.com (tari-gw [172.30.24.10]) by ext-gw.toshiba.co.jp  with ESMTP id n3DFtfnv018953 for <pana@ietf.org>; Tue, 14 Apr 2009 00:55:42 +0900 (JST)
Received: from steelhead.localdomain (tarij-62.tari.toshiba.com [172.30.24.110]) by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id n3DFxMPS017609; Mon, 13 Apr 2009 11:59:22 -0400 (EDT) (envelope-from yohba@tari.toshiba.com)
Received: from ohba by steelhead.localdomain with local (Exim 4.69) (envelope-from <yohba@tari.toshiba.com>) id 1LtOVZ-00080U-JU; Mon, 13 Apr 2009 11:55:41 -0400
Date: Mon, 13 Apr 2009 11:55:41 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-ID: <20090413155541.GD29716@steelhead.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: [Pana] pana-preauth-05 available
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2009 15:54:49 -0000

This new revision reflects the WGLC comments.  Basically the document
has been much simplified.

Changes:

- Removed pre/post-authorization stuff

- Removed description on IP address update

- Removed authorization and accounting considerations section.

- Removed context binding description.

- Added clarification that EAP authentication is performed over PAR
and PAN exchanges.

- Added backward compatibility section

- Editorial fixes.

Regards,
Yoshihiro Ohba

From lionel.morand@orange-ftgroup.com  Tue Apr 14 01:11:17 2009
Return-Path: <lionel.morand@orange-ftgroup.com>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1960C3A67A1 for <pana@core3.amsl.com>; Tue, 14 Apr 2009 01:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.392
X-Spam-Level: 
X-Spam-Status: No, score=-3.392 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-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 He8XQnh+K-4t for <pana@core3.amsl.com>; Tue, 14 Apr 2009 01:11:16 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id E69223A6767 for <pana@ietf.org>; Tue, 14 Apr 2009 01:11:15 -0700 (PDT)
Received: from FTRDMEL2.rd.francetelecom.fr ([10.192.128.41]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 14 Apr 2009 10:12:27 +0200
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 14 Apr 2009 10:12:23 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026065E770D@ftrdmel2>
In-Reply-To: <49E301EA.10605@piuha.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] What to do with I-D: draft-ietf-pana-ipsec
Thread-Index: Acm8F/p+H6U0q3BsR1G7BHnUq8+sUwAwKgRQ
References: <C603B141.26687%basavaraj.patil@nokia.com>	<007201c9b97b$30c606d0$92521470$@net><5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com> <49E301EA.10605@piuha.net>
From: <lionel.morand@orange-ftgroup.com>
To: <jari.arkko@piuha.net>, <julien.bournelle@gmail.com>, <gwz@net-zen.net>
X-OriginalArrivalTime: 14 Apr 2009 08:12:27.0189 (UTC) FILETIME=[BFB2BE50:01C9BCD8]
Cc: pana@ietf.org, Basavaraj.Patil@nokia.com
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2009 08:11:17 -0000

I'm also volunteering for helping in this work.

Lionel=20

> -----Message d'origine-----
> De : pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] De=20
> la part de Jari Arkko
> Envoy=E9 : lundi 13 avril 2009 11:12
> =C0 : Julien Bournelle; Glen Zorn
> Cc : Basavaraj.Patil@nokia.com; pana@ietf.org
> Objet : Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
>=20
> My primary issue with this document was the lack of cycles,=20
> if there had been no one interested in taking it to=20
> completion we should have dropped it. Since you two are=20
> volunteering, can you work with the chairs to take over the=20
> work, and do whatever is needed to bring the document to a=20
> reasonable state?
>=20
> Jari
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana
>=20

From gwz@net-zen.net  Tue Apr 14 02:08:05 2009
Return-Path: <gwz@net-zen.net>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E554D3A6A9B for <pana@core3.amsl.com>; Tue, 14 Apr 2009 02:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 BCYykSPqsIuw for <pana@core3.amsl.com>; Tue, 14 Apr 2009 02:08:05 -0700 (PDT)
Received: from smtpout07.prod.mesa1.secureserver.net (smtpout07-01.prod.mesa1.secureserver.net [64.202.165.230]) by core3.amsl.com (Postfix) with SMTP id 300033A69D6 for <pana@ietf.org>; Tue, 14 Apr 2009 02:08:05 -0700 (PDT)
Received: (qmail 22353 invoked from network); 14 Apr 2009 09:09:14 -0000
Received: from unknown (124.121.211.208) by smtpout07.prod.mesa1.secureserver.net (64.202.165.230) with ESMTP; 14 Apr 2009 09:09:13 -0000
From: "Glen Zorn" <gwz@net-zen.net>
To: "'Jari Arkko'" <jari.arkko@piuha.net>, <pana@ietf.org>
References: <49DA009B.30507@piuha.net>
In-Reply-To: <49DA009B.30507@piuha.net>
Date: Tue, 14 Apr 2009 16:09:08 +0700
Organization: Network Zen
Message-ID: <00b301c9bce0$ad625a50$08270ef0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acm2ueHIk8v5Nb59Sfuoc0eQ5ligKQGJi2Mg
Content-Language: en-us
Subject: Re: [Pana] pana-ipsec status?
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2009 09:08:06 -0000

> What needs to be done to draft-ietf-pana-ipsec to move it forward? Or
> are the serious technical issues based on earlier reviews or lack of
> energy? 

Looking at it, there didn't appear to me to be any serious technical issues.

> I would like to move forward with the remaining work items...
> 
> Jari
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana



From yohba@tari.toshiba.com  Tue Apr 14 16:49:08 2009
Return-Path: <yohba@tari.toshiba.com>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6785D3A6EB8 for <pana@core3.amsl.com>; Tue, 14 Apr 2009 16:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.066
X-Spam-Level: 
X-Spam-Status: No, score=-3.066 tagged_above=-999 required=5 tests=[AWL=1.023,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 nr4+fqb-edxg for <pana@core3.amsl.com>; Tue, 14 Apr 2009 16:49:07 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by core3.amsl.com (Postfix) with ESMTP id 6ED5F3A6EAC for <pana@ietf.org>; Tue, 14 Apr 2009 16:49:07 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id n3ENoF50008251; Wed, 15 Apr 2009 08:50:15 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id n3ENoFMU003734; Wed, 15 Apr 2009 08:50:15 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id JAA03733; Wed, 15 Apr 2009 08:50:15 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id n3ENoFGn013707; Wed, 15 Apr 2009 08:50:15 +0900 (JST)
Received: from ivp1.toshiba.co.jp by toshiba.co.jp id n3ENoEtX012476; Wed, 15 Apr 2009 08:50:14 +0900 (JST)
Received: from ext-gw.toshiba.co.jp by ivp1.toshiba.co.jp  with ESMTP id n3ENoD68021762; Wed, 15 Apr 2009 08:50:14 +0900 (JST)
Received: from toshi17.tari.toshiba.com (tari-gw [172.30.24.10]) by ext-gw.toshiba.co.jp  with ESMTP id n3ENoCHf025592; Wed, 15 Apr 2009 08:50:13 +0900 (JST)
Received: from steelhead.localdomain (tarij-62.tari.toshiba.com [172.30.24.110]) by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id n3ENrm42036073; Tue, 14 Apr 2009 19:53:48 -0400 (EDT) (envelope-from yohba@tari.toshiba.com)
Received: from ohba by steelhead.localdomain with local (Exim 4.69) (envelope-from <yohba@tari.toshiba.com>) id 1LtsOJ-0002WT-J3; Tue, 14 Apr 2009 19:50:11 -0400
Date: Tue, 14 Apr 2009 19:50:11 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: Jari Arkko <jari.arkko@piuha.net>
Message-ID: <20090414235011.GQ29716@steelhead.localdomain>
References: <C603B141.26687%basavaraj.patil@nokia.com> <007201c9b97b$30c606d0$92521470$@net> <5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com> <49E301EA.10605@piuha.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
In-Reply-To: <49E301EA.10605@piuha.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: pana@ietf.org, Basavaraj.Patil@nokia.com
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2009 23:49:08 -0000

There is a related document (i.e., draft-ohba-pana-pemk-02) that
defines PaC-EP Master Key (PEMK).  PEMK is derived to be
cryptographically independent across multiple different types of lower
layers including IPsec.  What should we do with pana-pemk draft?

Yoshihiro Ohba


On Mon, Apr 13, 2009 at 12:12:10PM +0300, Jari Arkko wrote:
> My primary issue with this document was the lack of cycles, if there had  
> been no one interested in taking it to completion we should have dropped  
> it. Since you two are volunteering, can you work with the chairs to take  
> over the work, and do whatever is needed to bring the document to a  
> reasonable state?
>
> Jari
>
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana
>

From Basavaraj.Patil@nokia.com  Tue Apr 14 19:04:29 2009
Return-Path: <Basavaraj.Patil@nokia.com>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0CCC3A6B9E for <pana@core3.amsl.com>; Tue, 14 Apr 2009 19:04:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.352
X-Spam-Level: 
X-Spam-Status: No, score=-6.352 tagged_above=-999 required=5 tests=[AWL=0.247,  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 LhPRl3KnPkDf for <pana@core3.amsl.com>; Tue, 14 Apr 2009 19:04:28 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 6496B3A6EEA for <pana@ietf.org>; Tue, 14 Apr 2009 19:04:27 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n3F25RXg025030; Wed, 15 Apr 2009 05:05:34 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 15 Apr 2009 05:05:35 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 15 Apr 2009 05:05:34 +0300
Received: from nok-am1mhub-06.mgdnok.nokia.com (65.54.30.10) by NOK-AM1MHUB-03.mgdnok.nokia.com (65.54.30.7) with Microsoft SMTP Server (TLS) id 8.1.340.0; Wed, 15 Apr 2009 04:05:34 +0200
Received: from NOK-EUMSG-03.mgdnok.nokia.com ([65.54.30.108]) by nok-am1mhub-06.mgdnok.nokia.com ([65.54.30.10]) with mapi; Wed, 15 Apr 2009 04:05:34 +0200
From: <Basavaraj.Patil@nokia.com>
To: <yohba@tari.toshiba.com>, <jari.arkko@piuha.net>
Date: Wed, 15 Apr 2009 04:05:33 +0200
Thread-Topic: [Pana] What to do with I-D: draft-ietf-pana-ipsec
Thread-Index: Acm9W8lg9mU2qcI4RUut72XhHQz2WwAD+F4Q
Message-ID: <FAAB54171A6C764E969E6B4CB3C2ADD20A44A0AFFD@NOK-EUMSG-03.mgdnok.nokia.com>
References: <C603B141.26687%basavaraj.patil@nokia.com> <007201c9b97b$30c606d0$92521470$@net> <5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com> <49E301EA.10605@piuha.net> <20090414235011.GQ29716@steelhead.localdomain>
In-Reply-To: <20090414235011.GQ29716@steelhead.localdomain>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 15 Apr 2009 02:05:34.0642 (UTC) FILETIME=[A99C6120:01C9BD6E]
X-Nokia-AV: Clean
Cc: pana@ietf.org
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2009 02:04:29 -0000

Hi Yoshi,

Current intent is to complete the WG I-Ds. Given that the PEMK I-D is not a=
 WG document at this time, I would be reluctant to consider any further act=
ion from the PANA WG perspective.=20

-Raj=20

-----Original Message-----
From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf Of ext=
 Yoshihiro Ohba
Sent: Tuesday, April 14, 2009 6:50 PM
To: Jari Arkko
Cc: pana@ietf.org; Patil Basavaraj (Nokia-D/Dallas)
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec

There is a related document (i.e., draft-ohba-pana-pemk-02) that defines Pa=
C-EP Master Key (PEMK).  PEMK is derived to be cryptographically independen=
t across multiple different types of lower layers including IPsec.  What sh=
ould we do with pana-pemk draft?

Yoshihiro Ohba


On Mon, Apr 13, 2009 at 12:12:10PM +0300, Jari Arkko wrote:
> My primary issue with this document was the lack of cycles, if there=20
> had been no one interested in taking it to completion we should have=20
> dropped it. Since you two are volunteering, can you work with the=20
> chairs to take over the work, and do whatever is needed to bring the=20
> document to a reasonable state?
>
> Jari
>
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana
>
_______________________________________________
Pana mailing list
Pana@ietf.org
https://www.ietf.org/mailman/listinfo/pana

From jari.arkko@piuha.net  Wed Apr 15 02:21:55 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C9123A67FA for <pana@core3.amsl.com>; Wed, 15 Apr 2009 02:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.081,  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 8OmxU8zCdEZ7 for <pana@core3.amsl.com>; Wed, 15 Apr 2009 02:21:54 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 271A03A687D for <pana@ietf.org>; Wed, 15 Apr 2009 02:21:54 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id AE43D19872A; Wed, 15 Apr 2009 12:23:05 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 66F22198641; Wed, 15 Apr 2009 12:23:05 +0300 (EEST)
Message-ID: <49E57D21.8030402@piuha.net>
Date: Wed, 15 Apr 2009 09:22:25 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Basavaraj.Patil@nokia.com
References: <C603B141.26687%basavaraj.patil@nokia.com>	<007201c9b97b$30c606d0$92521470$@net>	<5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com>	<49E301EA.10605@piuha.net> <20090414235011.GQ29716@steelhead.localdomain> <FAAB54171A6C764E969E6B4CB3C2ADD20A44A0AFFD@NOK-EUMSG-03.mgdnok.nokia.com>
In-Reply-To: <FAAB54171A6C764E969E6B4CB3C2ADD20A44A0AFFD@NOK-EUMSG-03.mgdnok.nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: yohba@tari.toshiba.com, pana@ietf.org
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2009 09:21:55 -0000

Can we technically specify the IPsec parts without PEMK? If yes, we 
should do it. If not, we have an issue.

Quickly scanning through the documents, PaC-EP-Master-Key does not seem 
to be defined in RFC 5191 but it is used by draft-ietf-pana-ipsec. At 
the very least we need a definition of Pac-EP-Master-Key in 
draft-ietf-pana-ipsec, not sure if a separate document is needed.

Jari

Basavaraj.Patil@nokia.com wrote:
> Hi Yoshi,
>
> Current intent is to complete the WG I-Ds. Given that the PEMK I-D is not a WG document at this time, I would be reluctant to consider any further action from the PANA WG perspective. 
>
> -Raj 
>
> -----Original Message-----
> From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf Of ext Yoshihiro Ohba
> Sent: Tuesday, April 14, 2009 6:50 PM
> To: Jari Arkko
> Cc: pana@ietf.org; Patil Basavaraj (Nokia-D/Dallas)
> Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
>
> There is a related document (i.e., draft-ohba-pana-pemk-02) that defines PaC-EP Master Key (PEMK).  PEMK is derived to be cryptographically independent across multiple different types of lower layers including IPsec.  What should we do with pana-pemk draft?
>
> Yoshihiro Ohba
>
>
> On Mon, Apr 13, 2009 at 12:12:10PM +0300, Jari Arkko wrote:
>   
>> My primary issue with this document was the lack of cycles, if there 
>> had been no one interested in taking it to completion we should have 
>> dropped it. Since you two are volunteering, can you work with the 
>> chairs to take over the work, and do whatever is needed to bring the 
>> document to a reasonable state?
>>
>> Jari
>>
>> _______________________________________________
>> Pana mailing list
>> Pana@ietf.org
>> https://www.ietf.org/mailman/listinfo/pana
>>
>>     
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana
>
>
>   



From gwz@net-zen.net  Wed Apr 15 03:09:33 2009
Return-Path: <gwz@net-zen.net>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F13103A6DA0 for <pana@core3.amsl.com>; Wed, 15 Apr 2009 03:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114,  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 X2QhBNHTjRj5 for <pana@core3.amsl.com>; Wed, 15 Apr 2009 03:09:33 -0700 (PDT)
Received: from smtpauth03.prod.mesa1.secureserver.net (smtpauth03.prod.mesa1.secureserver.net [64.202.165.183]) by core3.amsl.com (Postfix) with SMTP id 2F3B93A6B9E for <pana@ietf.org>; Wed, 15 Apr 2009 03:09:33 -0700 (PDT)
Received: (qmail 12675 invoked from network); 15 Apr 2009 10:10:44 -0000
Received: from unknown (124.120.222.25) by smtpauth03.prod.mesa1.secureserver.net (64.202.165.183) with ESMTP; 15 Apr 2009 10:10:43 -0000
From: "Glen Zorn" <gwz@net-zen.net>
To: "'Jari Arkko'" <jari.arkko@piuha.net>
References: <C603B141.26687%basavaraj.patil@nokia.com>	<007201c9b97b$30c606d0$92521470$@net>	<5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com>	<49E301EA.10605@piuha.net>	<20090414235011.GQ29716@steelhead.localdomain>	<FAAB54171A6C764E969E6B4CB3C2ADD20A44A0AFFD@NOK-EUMSG-03.mgdnok.nokia.com> <49E57D21.8030402@piuha.net>
In-Reply-To: <49E57D21.8030402@piuha.net>
Date: Wed, 15 Apr 2009 17:10:38 +0700
Organization: Network Zen
Message-ID: <002d01c9bdb2$6fa9d800$4efd8800$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acm9q8ptZE9+enEhRrqP4wf8GQKQtQAA7aJw
Content-Language: en-us
Cc: yohba@tari.toshiba.com, Basavaraj.Patil@nokia.com, pana@ietf.org
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2009 10:09:34 -0000

Jari Arkko [mailto:jari.arkko@piuha.net] writes:

> Can we technically specify the IPsec parts without PEMK? If yes, we
> should do it. If not, we have an issue.
> 
> Quickly scanning through the documents, PaC-EP-Master-Key does not seem
> to be defined in RFC 5191 but it is used by draft-ietf-pana-ipsec. 

One of the problems w/draft-ietf-pana-ipsec is that the precise nature of
the protection between the PaC & EP doesn't seem to be specified _anywhere_
(please correct me if I'm wrong).  For the purposes of
draft-ietf-pana-ipsec, the connection should probably be protected using
IPsec (to avoid a weakest-link attack), but that needs to be specified.  As
for draft-ohba-pana-pemk-02, it specifies (as does 5191) the use of the MSK
which is a _really_ bad idea IMHO -- the EMSK should really be used instead.

> At the very least we need a definition of Pac-EP-Master-Key in
> draft-ietf-pana-ipsec, not sure if a separate document is needed.
> 

...

~ gwz

Nuclear power: more toxic than Britney Spears.




From alper.yegin@yegin.org  Wed Apr 15 06:51:05 2009
Return-Path: <alper.yegin@yegin.org>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF7C93A6C35 for <pana@core3.amsl.com>; Wed, 15 Apr 2009 06:51:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.732
X-Spam-Level: 
X-Spam-Status: No, score=-0.732 tagged_above=-999 required=5 tests=[AWL=0.418,  BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
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 k-f51K9WfiR4 for <pana@core3.amsl.com>; Wed, 15 Apr 2009 06:51:05 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 34B483A69CF for <pana@ietf.org>; Wed, 15 Apr 2009 06:50:37 -0700 (PDT)
Received: from LENOVO (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1Lu5WU1kuV-000g32; Wed, 15 Apr 2009 09:51:36 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Jari Arkko'" <jari.arkko@piuha.net>, <Basavaraj.Patil@nokia.com>
References: <C603B141.26687%basavaraj.patil@nokia.com>	<007201c9b97b$30c606d0$92521470$@net>	<5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com>	<49E301EA.10605@piuha.net>	<20090414235011.GQ29716@steelhead.localdomain>	<FAAB54171A6C764E969E6B4CB3C2ADD20A44A0AFFD@NOK-EUMSG-03.mgdnok.nokia.com> <49E57D21.8030402@piuha.net>
In-Reply-To: <49E57D21.8030402@piuha.net>
Date: Wed, 15 Apr 2009 16:51:19 +0300
Message-ID: <02cb01c9bdd1$45b90e20$d12b2a60$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: Acm9q8sGwb8UshmxR4CY/x2S5YWv6AAJOWGw
Content-Language: en-us
X-Provags-ID: V01U2FsdGVkX19NILf5TO8KXAq4bU5pgMSeog/TjNeX8YwuwGM 1SVMJ+cbjzDK+slZ9ta4If3xIq3aU0YD02YKmGdF3yv8rVzSh3 DtrKoiC2TQVsEYe3JuZzQ==
Cc: yohba@tari.toshiba.com, pana@ietf.org
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2009 13:51:06 -0000

Jari,

PaC-EP-Master-Key used to be defined in PANA base specification.
Sam Hartman had asked it be split into a separate document, so we did.

PaC-EP-Master-Key is the glue between PANA and the PaC-EP secure association
protocols.
PaC-EP-Master-Key definition is agnostic to the PaC-EP secure association
protocol, therefore I don't think it makes sense to embed that into
individual protocol document(s).

Alper







> -----Original Message-----
> From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf Of
> Jari Arkko
> Sent: Wednesday, April 15, 2009 9:22 AM
> To: Basavaraj.Patil@nokia.com
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
> 
> Can we technically specify the IPsec parts without PEMK? If yes, we
> should do it. If not, we have an issue.
> 
> Quickly scanning through the documents, PaC-EP-Master-Key does not seem
> to be defined in RFC 5191 but it is used by draft-ietf-pana-ipsec. At
> the very least we need a definition of Pac-EP-Master-Key in
> draft-ietf-pana-ipsec, not sure if a separate document is needed.
> 
> Jari
> 
> Basavaraj.Patil@nokia.com wrote:
> > Hi Yoshi,
> >
> > Current intent is to complete the WG I-Ds. Given that the PEMK I-D is
> not a WG document at this time, I would be reluctant to consider any
> further action from the PANA WG perspective.
> >
> > -Raj
> >
> > -----Original Message-----
> > From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf
> Of ext Yoshihiro Ohba
> > Sent: Tuesday, April 14, 2009 6:50 PM
> > To: Jari Arkko
> > Cc: pana@ietf.org; Patil Basavaraj (Nokia-D/Dallas)
> > Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
> >
> > There is a related document (i.e., draft-ohba-pana-pemk-02) that
> defines PaC-EP Master Key (PEMK).  PEMK is derived to be
> cryptographically independent across multiple different types of lower
> layers including IPsec.  What should we do with pana-pemk draft?
> >
> > Yoshihiro Ohba
> >
> >
> > On Mon, Apr 13, 2009 at 12:12:10PM +0300, Jari Arkko wrote:
> >
> >> My primary issue with this document was the lack of cycles, if there
> >> had been no one interested in taking it to completion we should have
> >> dropped it. Since you two are volunteering, can you work with the
> >> chairs to take over the work, and do whatever is needed to bring the
> >> document to a reasonable state?
> >>
> >> Jari
> >>
> >> _______________________________________________
> >> Pana mailing list
> >> Pana@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pana
> >>
> >>
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www.ietf.org/mailman/listinfo/pana
> >
> >
> >
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana



From alper.yegin@yegin.org  Wed Apr 15 06:54:38 2009
Return-Path: <alper.yegin@yegin.org>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D148F3A6C0B for <pana@core3.amsl.com>; Wed, 15 Apr 2009 06:54:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.753
X-Spam-Level: 
X-Spam-Status: No, score=-0.753 tagged_above=-999 required=5 tests=[AWL=0.397,  BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
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 hpeabFxPrf-i for <pana@core3.amsl.com>; Wed, 15 Apr 2009 06:54:38 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 2267A3A6E31 for <pana@ietf.org>; Wed, 15 Apr 2009 06:54:38 -0700 (PDT)
Received: from LENOVO (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1Lu5aW2Mfo-000cm1; Wed, 15 Apr 2009 09:55:50 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Glen Zorn'" <gwz@net-zen.net>, "'Jari Arkko'" <jari.arkko@piuha.net>
References: <C603B141.26687%basavaraj.patil@nokia.com>	<007201c9b97b$30c606d0$92521470$@net>	<5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com>	<49E301EA.10605@piuha.net>	<20090414235011.GQ29716@steelhead.localdomain>	<FAAB54171A6C764E969E6B4CB3C2ADD20A44A0AFFD@NOK-EUMSG-03.mgdnok.nokia.com>	<49E57D21.8030402@piuha.net> <002d01c9bdb2$6fa9d800$4efd8800$@net>
In-Reply-To: <002d01c9bdb2$6fa9d800$4efd8800$@net>
Date: Wed, 15 Apr 2009 16:55:18 +0300
Message-ID: <02cc01c9bdd1$dac57d00$90507700$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: Acm9q8ptZE9+enEhRrqP4wf8GQKQtQAA7aJwAAh4POA=
Content-Language: en-us
X-Provags-ID: V01U2FsdGVkX19AzqmTCkETniATd5mbQ3+F3OI8RaJrXi4AtAZ 4jS60Ds49wsk431AipPfv6pK3LOSgtkQUFQe7raTor9HFnhel5 s6x/kzPyDkxA3NoUPiSEg==
Cc: yohba@tari.toshiba.com, pana@ietf.org, Basavaraj.Patil@nokia.com
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2009 13:54:38 -0000

> As
> for draft-ohba-pana-pemk-02, it specifies (as does 5191) the use of the
> MSK
> which is a _really_ bad idea IMHO -- the EMSK should really be used
> instead.

Why so?

Secure association protocols have been using MSK-driven keys.
And it makes sense, as MSK is what NAS knows (not EMSK).
I have no idea what value using EMSK has, but the obvious cost is to impact
the AAA deployment between the NAS and AAA servers. Today AAA protocols
deliver MSK, not EMSK or any of its children.

Alper





From jari.arkko@piuha.net  Wed Apr 15 07:04:44 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A1AF03A6C1E for <pana@core3.amsl.com>; Wed, 15 Apr 2009 07:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065,  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 1l1reNNavsAI for <pana@core3.amsl.com>; Wed, 15 Apr 2009 07:04:44 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id C7F1C28C1CF for <pana@ietf.org>; Wed, 15 Apr 2009 07:04:43 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 83FF619872A; Wed, 15 Apr 2009 17:05:54 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 1FB8A198665; Wed, 15 Apr 2009 17:05:54 +0300 (EEST)
Message-ID: <49E5E9B7.6070509@piuha.net>
Date: Wed, 15 Apr 2009 17:05:43 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
References: <C603B141.26687%basavaraj.patil@nokia.com>	<007201c9b97b$30c606d0$92521470$@net>	<5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com>	<49E301EA.10605@piuha.net>	<20090414235011.GQ29716@steelhead.localdomain>	<FAAB54171A6C764E969E6B4CB3C2ADD20A44A0AFFD@NOK-EUMSG-03.mgdnok.nokia.com>	<49E57D21.8030402@piuha.net> <002d01c9bdb2$6fa9d800$4efd8800$@net> <02cc01c9bdd1$dac57d00$90507700$@yegin@yegin.org>
In-Reply-To: <02cc01c9bdd1$dac57d00$90507700$@yegin@yegin.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: yohba@tari.toshiba.com, pana@ietf.org, Basavaraj.Patil@nokia.com
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2009 14:04:44 -0000

I think I agree with what Alper is saying below. It is obviously 
important to have separated keys for PANA itself and the per-packet 
protection (such as for IPsec). But given the definition of the keys 
used for PANA in the RFC, I think it is possible to have other 
MSK-derived keys for IPsec.

Jari

Alper Yegin wrote:
>> As
>> for draft-ohba-pana-pemk-02, it specifies (as does 5191) the use of the
>> MSK
>> which is a _really_ bad idea IMHO -- the EMSK should really be used
>> instead.
>>     
>
> Why so?
>
> Secure association protocols have been using MSK-driven keys.
> And it makes sense, as MSK is what NAS knows (not EMSK).
> I have no idea what value using EMSK has, but the obvious cost is to impact
> the AAA deployment between the NAS and AAA servers. Today AAA protocols
> deliver MSK, not EMSK or any of its children.
>
> Alper
>
>
>
>
>
>
>   


From jsalowey@cisco.com  Fri Apr 17 09:39:12 2009
Return-Path: <jsalowey@cisco.com>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF21A3A69DF for <pana@core3.amsl.com>; Fri, 17 Apr 2009 09:39:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.276
X-Spam-Level: 
X-Spam-Status: No, score=-6.276 tagged_above=-999 required=5 tests=[AWL=0.323,  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 OA8LFMSSGdMF for <pana@core3.amsl.com>; Fri, 17 Apr 2009 09:39:11 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 3AF733A6E24 for <pana@ietf.org>; Fri, 17 Apr 2009 09:39:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,205,1238976000"; d="scan'208";a="155993236"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-2.cisco.com with ESMTP; 17 Apr 2009 16:40:25 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n3HGePOF009643;  Fri, 17 Apr 2009 09:40:25 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id n3HGePra027657; Fri, 17 Apr 2009 16:40:25 GMT
Received: from xmb-sjc-225.amer.cisco.com ([128.107.191.38]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 17 Apr 2009 09:40:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Apr 2009 09:40:22 -0700
Message-ID: <AC1CFD94F59A264488DC2BEC3E890DE507D92D4D@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <49E5E9B7.6070509@piuha.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] What to do with I-D: draft-ietf-pana-ipsec
Thread-Index: Acm901IlkuK4V4nMTwmTJ/q9OfOkHABn4kzw
References: <C603B141.26687%basavaraj.patil@nokia.com>	<007201c9b97b$30c606d0$92521470$@net>	<5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com>	<49E301EA.10605@piuha.net>	<20090414235011.GQ29716@steelhead.localdomain>	<FAAB54171A6C764E969E6B4CB3C2ADD20A44A0AFFD@NOK-EUMSG-03.mgdnok.nokia.com>	<49E57D21.8030402@piuha.net><002d01c9bdb2$6fa9d800$4efd8800$@net><02cc01c9bdd1$dac57d00$90507700$@yegin@yegin.org> <49E5E9B7.6070509@piuha.net>
From: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
To: "Jari Arkko" <jari.arkko@piuha.net>, "Alper Yegin" <alper.yegin@yegin.org>
X-OriginalArrivalTime: 17 Apr 2009 16:40:23.0088 (UTC) FILETIME=[33FD2300:01C9BF7B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1783; t=1239986425; x=1240850425; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jsalowey@cisco.com; z=From:=20=22Joseph=20Salowey=20(jsalowey)=22=20<jsalowey@ci sco.com> |Subject:=20RE=3A=20[Pana]=20What=20to=20do=20with=20I-D=3A =20draft-ietf-pana-ipsec |Sender:=20; bh=QhT0k7i7jvxI0MR2bzQlj0Ciqwg273ddndD6auLUMGk=; b=JwInVcATEbbLf2vPnIsO92aQZdF7hFh9gr/PjM/d4Q/PjYwXEwfRP7WHsg CtzNvkPgT+5r6EOcOdzJLK+05KPzIGQ1jV8HsAoFeMrbpun2W0SFCKvLzBG7 J+SBUsrWkS;
Authentication-Results: sj-dkim-2; header.From=jsalowey@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: yohba@tari.toshiba.com, Basavaraj.Patil@nokia.com, pana@ietf.org
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2009 16:39:13 -0000

If the use of the key is entirely within the PANA authenticator and PANA
specifications then using the MSK is OK.  If the same key is going to be
used in specifications independent of PANA (802.11, etc) or used
somewhere other than the authenticator then the MSK may not be a good
choice. =20

> -----Original Message-----
> From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On=20
> Behalf Of Jari Arkko
> Sent: Wednesday, April 15, 2009 7:06 AM
> To: Alper Yegin
> Cc: yohba@tari.toshiba.com; pana@ietf.org; Basavaraj.Patil@nokia.com
> Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
>=20
> I think I agree with what Alper is saying below. It is=20
> obviously important to have separated keys for PANA itself=20
> and the per-packet protection (such as for IPsec). But given=20
> the definition of the keys used for PANA in the RFC, I think=20
> it is possible to have other MSK-derived keys for IPsec.
>=20
> Jari
>=20
> Alper Yegin wrote:
> >> As
> >> for draft-ohba-pana-pemk-02, it specifies (as does 5191)=20
> the use of=20
> >> the MSK which is a _really_ bad idea IMHO -- the EMSK=20
> should really=20
> >> be used instead.
> >>    =20
> >
> > Why so?
> >
> > Secure association protocols have been using MSK-driven keys.
> > And it makes sense, as MSK is what NAS knows (not EMSK).
> > I have no idea what value using EMSK has, but the obvious=20
> cost is to=20
> > impact the AAA deployment between the NAS and AAA servers.=20
> Today AAA=20
> > protocols deliver MSK, not EMSK or any of its children.
> >
> > Alper
> >
> >
> >
> >
> >
> >
> >  =20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www.ietf.org/mailman/listinfo/pana
>=20

From jari.arkko@piuha.net  Fri Apr 17 10:35:15 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D96363A6E20 for <pana@core3.amsl.com>; Fri, 17 Apr 2009 10:35:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083,  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 SbH9nDEGPj-E for <pana@core3.amsl.com>; Fri, 17 Apr 2009 10:35:15 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id CA21A3A6813 for <pana@ietf.org>; Fri, 17 Apr 2009 10:35:14 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id E2ABD198723; Fri, 17 Apr 2009 20:36:26 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 8117A198665; Fri, 17 Apr 2009 20:36:26 +0300 (EEST)
Message-ID: <49E8BE0F.7000709@piuha.net>
Date: Fri, 17 Apr 2009 20:36:15 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>
References: <C603B141.26687%basavaraj.patil@nokia.com>	<007201c9b97b$30c606d0$92521470$@net>	<5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com>	<49E301EA.10605@piuha.net>	<20090414235011.GQ29716@steelhead.localdomain>	<FAAB54171A6C764E969E6B4CB3C2ADD20A44A0AFFD@NOK-EUMSG-03.mgdnok.nokia.com>	<49E57D21.8030402@piuha.net><002d01c9bdb2$6fa9d800$4efd8800$@net><02cc01c9bdd1$dac57d00$90507700$@yegin@yegin.org> <49E5E9B7.6070509@piuha.net> <AC1CFD94F59A264488DC2BEC3E890DE507D92D4D@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE507D92D4D@xmb-sjc-225.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: Basavaraj.Patil@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2009 17:35:15 -0000

Right.

Jari

Joseph Salowey (jsalowey) wrote:
> If the use of the key is entirely within the PANA authenticator and PANA
> specifications then using the MSK is OK.  If the same key is going to be
> used in specifications independent of PANA (802.11, etc) or used
> somewhere other than the authenticator then the MSK may not be a good
> choice.  
>
>   
>> -----Original Message-----
>> From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On 
>> Behalf Of Jari Arkko
>> Sent: Wednesday, April 15, 2009 7:06 AM
>> To: Alper Yegin
>> Cc: yohba@tari.toshiba.com; pana@ietf.org; Basavaraj.Patil@nokia.com
>> Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
>>
>> I think I agree with what Alper is saying below. It is 
>> obviously important to have separated keys for PANA itself 
>> and the per-packet protection (such as for IPsec). But given 
>> the definition of the keys used for PANA in the RFC, I think 
>> it is possible to have other MSK-derived keys for IPsec.
>>
>> Jari
>>
>> Alper Yegin wrote:
>>     
>>>> As
>>>> for draft-ohba-pana-pemk-02, it specifies (as does 5191) 
>>>>         
>> the use of 
>>     
>>>> the MSK which is a _really_ bad idea IMHO -- the EMSK 
>>>>         
>> should really 
>>     
>>>> be used instead.
>>>>     
>>>>         
>>> Why so?
>>>
>>> Secure association protocols have been using MSK-driven keys.
>>> And it makes sense, as MSK is what NAS knows (not EMSK).
>>> I have no idea what value using EMSK has, but the obvious 
>>>       
>> cost is to 
>>     
>>> impact the AAA deployment between the NAS and AAA servers. 
>>>       
>> Today AAA 
>>     
>>> protocols deliver MSK, not EMSK or any of its children.
>>>
>>> Alper
>>>
>>>
>>>
>>>
>>>
>>>
>>>   
>>>       
>> _______________________________________________
>> Pana mailing list
>> Pana@ietf.org
>> https://www.ietf.org/mailman/listinfo/pana
>>
>>     
>
>
>   


From alper.yegin@yegin.org  Fri Apr 17 10:49:02 2009
Return-Path: <alper.yegin@yegin.org>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5975A3A6DF5 for <pana@core3.amsl.com>; Fri, 17 Apr 2009 10:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level: 
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
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 R3U2frL4nCbU for <pana@core3.amsl.com>; Fri, 17 Apr 2009 10:49:01 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 904263A6BAC for <pana@ietf.org>; Fri, 17 Apr 2009 10:49:01 -0700 (PDT)
Received: from LENOVO (dsl88-248-27784.ttnet.net.tr [88.248.108.136]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1LusCQ2T4g-000d0n; Fri, 17 Apr 2009 13:50:09 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Joseph Salowey \(jsalowey\)'" <jsalowey@cisco.com>, "'Jari Arkko'" <jari.arkko@piuha.net>
References: <C603B141.26687%basavaraj.patil@nokia.com>	<007201c9b97b$30c606d0$92521470$@net>	<5e2406980904100000t57c951duab69d7c0b7b7277@mail.gmail.com>	<49E301EA.10605@piuha.net>	<20090414235011.GQ29716@steelhead.localdomain>	<FAAB54171A6C764E969E6B4CB3C2ADD20A44A0AFFD@NOK-EUMSG-03.mgdnok.nokia.com>	<49E57D21.8030402@piuha.net><002d01c9bdb2$6fa9d800$4efd8800$@net><02cc01c9bdd1$dac57d00$90507700$@yegin@yegin.org> <49E5E9B7.6070509@piuha.net> <AC1CFD94F59A264488DC2BEC3E890DE507D92D4D@xmb-sjc-225.amer.cisco.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE507D92D4D@xmb-sjc-225.amer.cisco.com>
Date: Fri, 17 Apr 2009 20:49:51 +0300
Message-ID: <011801c9bf84$eedc67e0$cc9537a0$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acm901IlkuK4V4nMTwmTJ/q9OfOkHABn4kzwAARrXVA=
Content-Language: en-us
X-Provags-ID: V01U2FsdGVkX1+Wg7//pmLR7KQtpDgt8ignTig+0k3gGC45mto opWHrsKLQEpVEBxX5yw4udUk+O4jrBqZ/bR5Q/qo4qsUyEZm9v STceikxYypoN/VyybB9sw==
Cc: yohba@tari.toshiba.com, Basavaraj.Patil@nokia.com, pana@ietf.org
Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2009 17:49:02 -0000

Joe,

PaC-EP key is used by the PaC and the EP.
EP may be physically separate from the PAA (e.g., a base station separated
from NAS).
PaC-EP key is used by the secure association protocol between the PaC and
the EP.

I'm not sure if these satisfy your conditions. Please let us know.

Alper





> -----Original Message-----
> From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com]
> Sent: Friday, April 17, 2009 7:40 PM
> To: Jari Arkko; Alper Yegin
> Cc: yohba@tari.toshiba.com; pana@ietf.org; Basavaraj.Patil@nokia.com
> Subject: RE: [Pana] What to do with I-D: draft-ietf-pana-ipsec
> 
> If the use of the key is entirely within the PANA authenticator and
> PANA
> specifications then using the MSK is OK.  If the same key is going to
> be
> used in specifications independent of PANA (802.11, etc) or used
> somewhere other than the authenticator then the MSK may not be a good
> choice.
> 
> > -----Original Message-----
> > From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On
> > Behalf Of Jari Arkko
> > Sent: Wednesday, April 15, 2009 7:06 AM
> > To: Alper Yegin
> > Cc: yohba@tari.toshiba.com; pana@ietf.org; Basavaraj.Patil@nokia.com
> > Subject: Re: [Pana] What to do with I-D: draft-ietf-pana-ipsec
> >
> > I think I agree with what Alper is saying below. It is
> > obviously important to have separated keys for PANA itself
> > and the per-packet protection (such as for IPsec). But given
> > the definition of the keys used for PANA in the RFC, I think
> > it is possible to have other MSK-derived keys for IPsec.
> >
> > Jari
> >
> > Alper Yegin wrote:
> > >> As
> > >> for draft-ohba-pana-pemk-02, it specifies (as does 5191)
> > the use of
> > >> the MSK which is a _really_ bad idea IMHO -- the EMSK
> > should really
> > >> be used instead.
> > >>
> > >
> > > Why so?
> > >
> > > Secure association protocols have been using MSK-driven keys.
> > > And it makes sense, as MSK is what NAS knows (not EMSK).
> > > I have no idea what value using EMSK has, but the obvious
> > cost is to
> > > impact the AAA deployment between the NAS and AAA servers.
> > Today AAA
> > > protocols deliver MSK, not EMSK or any of its children.
> > >
> > > Alper
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www.ietf.org/mailman/listinfo/pana
> >



From root@core3.amsl.com  Mon Apr 20 14:15:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: pana@ietf.org
Delivered-To: pana@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id B5B663A6B03; Mon, 20 Apr 2009 14:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090420211501.B5B663A6B03@core3.amsl.com>
Date: Mon, 20 Apr 2009 14:15:01 -0700 (PDT)
Cc: pana@ietf.org
Subject: [Pana] I-D Action:draft-ietf-pana-statemachine-11.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Apr 2009 21:15:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol for carrying Authentication for Network Access Working Group of the IETF.


	Title           : State Machines for Protocol for Carrying Authentication for Network Access (PANA)
	Author(s)       : V. Fajardo, et al.
	Filename        : draft-ietf-pana-statemachine-11.txt
	Pages           : 39
	Date            : 2009-04-20

This document defines the conceptual state machines for the Protocol
for Carrying Authentication for Network Access (PANA).  The state
machines consist of the PANA Client (PaC) state machine and the PANA
Authentication Agent (PAA) state machine.  The two state machines
show how PANA can interface with the EAP state machines.  The state
machines and associated model are informative only.  Implementations
may achieve the same results using different methods.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pana-statemachine-11.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pana-statemachine-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-04-20140154.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Thu Apr 23 07:15:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: pana@ietf.org
Delivered-To: pana@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 7749D3A6D2E; Thu, 23 Apr 2009 07:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090423141501.7749D3A6D2E@core3.amsl.com>
Date: Thu, 23 Apr 2009 07:15:01 -0700 (PDT)
Cc: pana@ietf.org
Subject: [Pana] I-D Action:draft-ietf-pana-statemachine-12.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2009 14:15:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Protocol for carrying Authentication for Network Access Working Group of the IETF.


	Title           : State Machines for Protocol for Carrying Authentication for Network Access (PANA)
	Author(s)       : V. Fajardo, et al.
	Filename        : draft-ietf-pana-statemachine-12.txt
	Pages           : 40
	Date            : 2009-04-23

This document defines the conceptual state machines for the Protocol
for Carrying Authentication for Network Access (PANA).  The state
machines consist of the PANA Client (PaC) state machine and the PANA
Authentication Agent (PAA) state machine.  The two state machines
show how PANA can interface with the EAP state machines.  The state
machines and associated model are informative only.  Implementations
may achieve the same results using different methods.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pana-statemachine-12.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-pana-statemachine-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-04-23071412.I-D@ietf.org>


--NextPart--
