From mailman-bounces@ietf.org  Thu Jul  1 06:27:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12119
	for <pana-archive@lists.ietf.org>; Thu, 1 Jul 2004 06:27:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BfxbD-0006xb-Bc
	for pana-archive@lists.ietf.org; Thu, 01 Jul 2004 05:11:19 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: pana-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.9286.1088672558.3306.mailman@lists.ietf.org>
Date: Thu, 01 Jul 2004 05:02:38 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for pana-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
pana@ietf.org                            onobde    
https://www1.ietf.org/mailman/options/pana/pana-archive%40lists.ietf.org


From pana-bounces@ietf.org  Thu Jul  1 12:17:30 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14680
	for <pana-archive@lists.ietf.org>; Thu, 1 Jul 2004 12:17:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bg3sC-0003Fh-PL; Thu, 01 Jul 2004 11:53:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bg3Sl-0005sK-09
	for pana@megatron.ietf.org; Thu, 01 Jul 2004 11:26:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10330
	for <pana@ietf.org>; Thu, 1 Jul 2004 11:26:57 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bg3Sk-0006fY-AP
	for pana@ietf.org; Thu, 01 Jul 2004 11:26:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bg3Qe-00060c-00
	for pana@ietf.org; Thu, 01 Jul 2004 11:24:49 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12) id 1Bg3Nc-0004s8-00
	for pana@ietf.org; Thu, 01 Jul 2004 11:21:40 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 694923109B; Thu,  1 Jul 2004 17:21:09 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id 38C453101B; Thu,  1 Jul 2004 17:21:09 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id 0641914426; Thu,  1 Jul 2004 17:19:28 +0200 (MET DST)
Message-ID: <40E42C1B.5080609@dif.um.es>
Date: Thu, 01 Jul 2004 17:22:03 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Lost answer problem (a new issue)
References: <20040629003737.GA25808@steelhead>
In-Reply-To: <20040629003737.GA25808@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi Yoshihiro

Yoshihiro Ohba wrote:

>There might be some cases in which a PaC or a PAA might need to send a
>duplicate answer to a retransmitted old request (as well as a fresh
>answer to a new request if any) considering that an answer message for
>an old request can be lost. 
>
> Without this, a PANA session may stall in
>a way that the requester keeps retransmitting the old request while
>the responder may keep discarding them with waiting for a new request.
>The cases are described below.
>
>- When a PaC sends a PANA-Start-Answer message in response to a valid
>PANA-Start-Request message without a Cookie AVP, the answer message
>can be lost.  The PANA-Start-Request would be retransmitted.  To deal
>with the case, it might be better for the PaC to return a duplicate
>PANA-Start-Answer message after the PaC has been sent the first
>PANA-Start-Answer message until the PaC receives a valid
>PANA-Auth-Request message.
>  
>
In this case, I guess PANA-Start-Request would be retransmitted by
updating transmission sequence number , and PANA-Start-Request by
udpating transmission and received sequence numbers). That is:

PaC PAA

PSR(x,0)
<---------------------
PSA(y,x)
---------X--------->
PSR(x+1,0)
<-------------------
PSA(y+1,x+1)
------------------->

Am I wrong?

>- When a PaC sends a PANA-FirstAuth-End-Answer message in response to a
>valid PANA-FirstAuth-End-Request message (remember that a
>PANA-FirstAuth-End exchange is used for delimiting the first and
>second EAP authentications), the answer message may be lost.  The
>PANA-FirstAuth-End-Request would be retransmitted (with updating
>transmission sequence number).  To deal with the case, it might be
>better for the PaC to return a duplicate PANA-FirstAuth-End-Answer
>message (with updating transmission and received sequence numbers)
>after the PaC has been sent the first PANA-FirstAuth-End-Answer
>message until the PaC receives a valid PANA-Auth-Request message for
>the second EAP authentication.
>
>- When a PaC sends a PANA-Bind-Answer message in response to a valid
>PANA-Bind-Request message, the answer message can be lost.  As as
>result, the PAA will retransmit the PANA-Bind-Request (but with using
>a different transmission sequence number).  To deal with the case, it
>might be better for the PaC to return a duplicate PANA-Bind-Answer
>message (but with using different transmission and received sequence
>numbers) for a while after the first PANA-Bind-Request was received.
>The same thing can also apply to a PANA-Address-Update-Answer message
>that is sent by a PaC.
>
>- When a PaC or a PAA sends a PANA-Termination-Answer message in
>response to a valid PANA-Termination-Request message, the answer
>message can be lost.  As as result, the requester will retransmit the
>request (but with using a different transmission sequence number).  To
>deal with the case, it might be better for the sender of the answer to
>return a duplicate answer (with using different transmission and
>received sequence numbers) for a while after the first
>PANA-Termination-Request was received.  The same thing can also apply
>to a PANA-Reauth-Answer message that is sent by a PaC or a PAA.
>
>Those could improve robustness of the PANA protocol against loss of
>answer message.
>
>Comments?
>
>Yoshihiro Ohba
>
>_______________________________________________
>Pana mailing list
>Pana@ietf.org
>https://www1.ietf.org/mailman/listinfo/pana
>
>
>  
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul  1 17:42:24 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03005
	for <pana-archive@lists.ietf.org>; Thu, 1 Jul 2004 17:42:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bg992-0000fx-NI; Thu, 01 Jul 2004 17:31:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bg8zx-0004zi-Ko
	for pana@megatron.ietf.org; Thu, 01 Jul 2004 17:21:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02272
	for <pana@ietf.org>; Thu, 1 Jul 2004 17:21:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bg8zw-0006y0-Ay
	for pana@ietf.org; Thu, 01 Jul 2004 17:21:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bg8z3-0006c2-00
	for pana@ietf.org; Thu, 01 Jul 2004 17:20:42 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bg8yY-0006FV-00
	for pana@ietf.org; Thu, 01 Jul 2004 17:20:10 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i61LK5pD021124;
	Fri, 2 Jul 2004 06:20:05 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i61LK5Ub005854;
	Fri, 2 Jul 2004 06:20:05 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	GAA05853 ; Fri, 2 Jul 2004 06:20:05 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA21444; Fri, 2 Jul 2004 06:20:05 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA00221;
	Fri, 2 Jul 2004 06:20:04 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i61LK4pl027033;
	Fri, 2 Jul 2004 06:20:04 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0600C9BZ9DWN@tsbpo1.po.toshiba.co.jp>; Fri,
	2 Jul 2004 06:20:03 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlwZN-0000YL-00; Sat, 17 Jul 2004 14:18:09 -0700
Date: Sat, 17 Jul 2004 17:18:04 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Lost answer problem (a new issue)
In-reply-to: <40E42C1B.5080609@dif.um.es>
To: Rafael Marin Lopez <rafa@dif.um.es>
Message-id: <20040717211804.GB1753@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Rafael Marin Lopez <rafa@dif.um.es>,
	Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040629003737.GA25808@steelhead> <40E42C1B.5080609@dif.um.es>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Rafa,

On Thu, Jul 01, 2004 at 05:22:03PM +0200, Rafael Marin Lopez wrote:
> Hi Yoshihiro
> 
> Yoshihiro Ohba wrote:
> 
> >There might be some cases in which a PaC or a PAA might need to send a
> >duplicate answer to a retransmitted old request (as well as a fresh
> >answer to a new request if any) considering that an answer message for
> >an old request can be lost. 
> >
> > Without this, a PANA session may stall in
> >a way that the requester keeps retransmitting the old request while
> >the responder may keep discarding them with waiting for a new request.
> >The cases are described below.
> >
> >- When a PaC sends a PANA-Start-Answer message in response to a valid
> >PANA-Start-Request message without a Cookie AVP, the answer message
> >can be lost.  The PANA-Start-Request would be retransmitted.  To deal
> >with the case, it might be better for the PaC to return a duplicate
> >PANA-Start-Answer message after the PaC has been sent the first
> >PANA-Start-Answer message until the PaC receives a valid
> >PANA-Auth-Request message.
> >  
> >
> In this case, I guess PANA-Start-Request would be retransmitted by
> updating transmission sequence number , and PANA-Start-Request by
> udpating transmission and received sequence numbers). That is:
> 
> PaC PAA
> 
> PSR(x,0)
> <---------------------
> PSA(y,x)
> ---------X--------->
> PSR(x+1,0)
> <-------------------
> PSA(y+1,x+1)
> ------------------->
> 
> Am I wrong?


With incrementing the transmission sequence numbers in PSR and PSA
before the two entities complete initial sequence number negotiation,
it is possible to fail to share the same pair of initial sequence
numbers between PaC and PAA.  So sequence numbers should not be
incremented in PSR and PSA.  I think section 4.1.4 should be more
specific on this.

Yoshihiro Ohba




> 
> >- When a PaC sends a PANA-FirstAuth-End-Answer message in response to a
> >valid PANA-FirstAuth-End-Request message (remember that a
> >PANA-FirstAuth-End exchange is used for delimiting the first and
> >second EAP authentications), the answer message may be lost.  The
> >PANA-FirstAuth-End-Request would be retransmitted (with updating
> >transmission sequence number).  To deal with the case, it might be
> >better for the PaC to return a duplicate PANA-FirstAuth-End-Answer
> >message (with updating transmission and received sequence numbers)
> >after the PaC has been sent the first PANA-FirstAuth-End-Answer
> >message until the PaC receives a valid PANA-Auth-Request message for
> >the second EAP authentication.
> >
> >- When a PaC sends a PANA-Bind-Answer message in response to a valid
> >PANA-Bind-Request message, the answer message can be lost.  As as
> >result, the PAA will retransmit the PANA-Bind-Request (but with using
> >a different transmission sequence number).  To deal with the case, it
> >might be better for the PaC to return a duplicate PANA-Bind-Answer
> >message (but with using different transmission and received sequence
> >numbers) for a while after the first PANA-Bind-Request was received.
> >The same thing can also apply to a PANA-Address-Update-Answer message
> >that is sent by a PaC.
> >
> >- When a PaC or a PAA sends a PANA-Termination-Answer message in
> >response to a valid PANA-Termination-Request message, the answer
> >message can be lost.  As as result, the requester will retransmit the
> >request (but with using a different transmission sequence number).  To
> >deal with the case, it might be better for the sender of the answer to
> >return a duplicate answer (with using different transmission and
> >received sequence numbers) for a while after the first
> >PANA-Termination-Request was received.  The same thing can also apply
> >to a PANA-Reauth-Answer message that is sent by a PaC or a PAA.
> >
> >Those could improve robustness of the PANA protocol against loss of
> >answer message.
> >
> >Comments?
> >
> >Yoshihiro Ohba
> >
> >_______________________________________________
> >Pana mailing list
> >Pana@ietf.org
> >https://www1.ietf.org/mailman/listinfo/pana
> >
> >
> >  
> >
> 
> 
> -- 
> ------------------------------------------------------
> Rafael Marin Lopez
> Faculty of Computer Science-University of Murcia
> 30071 Murcia - Spain
> Telf: +34968367645    e-mail: rafa@dif.um.es
> ------------------------------------------------------
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul  1 21:04:18 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12064
	for <pana-archive@lists.ietf.org>; Thu, 1 Jul 2004 21:04:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BgCDq-0003DB-13; Thu, 01 Jul 2004 20:48:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BgC5e-0008OS-E4
	for pana@megatron.ietf.org; Thu, 01 Jul 2004 20:39:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11477
	for <pana@ietf.org>; Thu, 1 Jul 2004 20:39:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BgC5c-0002EF-F9
	for pana@ietf.org; Thu, 01 Jul 2004 20:39:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BgC4d-0001rX-00
	for pana@ietf.org; Thu, 01 Jul 2004 20:38:40 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12) id 1BgC3c-0001BA-00
	for pana@ietf.org; Thu, 01 Jul 2004 20:37:36 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I070063W8DDNJ@mailout3.samsung.com> for pana@ietf.org; Fri,
	02 Jul 2004 09:36:49 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0700E878BMBG@mailout3.samsung.com> for pana@ietf.org;
	Fri, 02 Jul 2004 09:35:46 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I07009EF8BINT@mmp1.samsung.com> for
	pana@ietf.org; Fri, 02 Jul 2004 09:35:46 +0900 (KST)
Date: Thu, 01 Jul 2004 17:35:40 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <017d01c45fcc$8302c360$981d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: "'Randy Turner'" <rturner@amalfisystems.com>
Subject: [Pana] Randy Turner's comments #1
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Hello,

Here is some feedback from Randy Turner on the PANA documents. Stay
tuned for more....

Alper

----------------


Comments on draft-ietf-pana-framework-00

(This was the version available on the IETF website PANA WG links)




------
Section 3 of the PANA Framework Document...

The last three paragraphs of section 3 describe the high-level exchange
necessary for a PaC to gain access to the network, and you also describe
the fact that an SA exists between the PaC and the EP.  I would
emphasize the point here (again) that the SA can either be implicit (in
the case of DSL and a pre-secured link) or explicit (requiring protocol
support "on the wire").

And I would also emphasize (even though it might be obvious to some),
that since an explicit SA typically requires some type of secure
encapsulation, and additional overhead, that this protocol overhead will
get stripped off at the EP and not affect communications beyond the EP.

You've already stated earlier in the draft, as I commented in my
original comments to you in earlier drafts, that it's important to place
the EP as close to the edge of the network as possible . So given this
point,  the "cost" of erecting an SA is also reduced because it only
exists for the initial "hop" in the access network.

-------

With regards to the following text:

 PRPA and the IP address of PAA are assumed to be on the same IP
      subnet, hence the PaC and PAA can perform on-link communication as
      required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
      this assumption may not hold true. In order to maintain the same
      on-link communication, the PaC and PAA SHOULD create host routes
      to each other upon PaC's IP address change.  The PaC SHOULD create
      a host route to the PAA, and the PAA SHOULD create a host route to
      the PaC (POPA).

I didn't see anywhere in the document leading up to this section a
discussion on the entity that is responsible for configuring the POPA.
Does the PAA have to be co-resident with the host that is responsible
for allocating/communicating the POPA to the PaC ?  If not, then the PAA
must "snoop" the IP configuration process between the PaC and the
"allocation entity" in order to create the necessary host route to the
PaC.  Let me know if I missed something in the text.

-------

Regarding the following text...

 When an IPv4 PRPA is configured, the same address may be used as
      both IPsec-TOA and IPsec-TIA.  In this case, a POPA is not
      configured.  Alternatively, an IPsec-TIA can be obtained via the
      configuration method available within [RFC3456] for IPv4, and
      [I-D.ietf-ipsec-ikev2] for both IPv4 and IPv6. This newly
      configured address constitutes a POPA.  Please refer to
      [I-D.ietf-pana-ipsec] for more details.

The last time I looked at the internals of an IPSEC implementation, and
the associated routing that takes place, the inner tunnel typically
reflects a different network than the network that is reflected by
IPSEC-TOA.  This means that the IP stack has (at least) two entries in
the route table. One entry says how to send a packet to the network
indicated by the TOA, and another route entry that says how to send
packets that are destined for the network reflected by the TIA.  the
remote node would have two different route entries that map to the same
network. UNLESS one of the route entries (for the TIA as an example)
contains a longer prefix than the route entry reflecting the TOA
network. This is how I was able to "force" packets down a tunnel if I
had overlapping routes. Is this making sense? I guess what I'm
suggesting is that the NAP probably would not use this capability
because of it's special nature.  Other IPSEC implementations may make
this easier I don't know. Let me know if you think this is something
that should be clarified.

Also, If the PaC authenticates successfully and accesses the network,
but there is an IPSEC SA between the PaC and PAA (or is it the EP), THEN
the user subsequently creates an IPSEC tunnel between the PaC and say a
corporate firewall termination point, how would this look? (assuming
there's quite a bit of overhead on the PaC for maintaining these two
SAs).

------

I'm not clear on the functional distinction between sections 10.1.2 and
10.1.3 - The NAPT CPE is also a router (it's NAT'ing between address
spaces). Since I don't believe NAPT has any specific impact on PANA
(since the CPE is the Pac), I would have just combined these two
sections, indicating that the router might also use NAPT.

-------




_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul  2 02:16:02 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07914
	for <pana-archive@lists.ietf.org>; Fri, 2 Jul 2004 02:16:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BgHJ5-00077c-6f; Fri, 02 Jul 2004 02:13:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BgHHO-0005vl-ST
	for pana@megatron.ietf.org; Fri, 02 Jul 2004 02:12:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06349
	for <pana@ietf.org>; Fri, 2 Jul 2004 02:12:09 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BgHHM-0001Va-PN
	for pana@ietf.org; Fri, 02 Jul 2004 02:12:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BgHGJ-00017G-00
	for pana@ietf.org; Fri, 02 Jul 2004 02:11:04 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12) id 1BgHFN-0000kM-00
	for pana@ietf.org; Fri, 02 Jul 2004 02:10:05 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i626A3N17165
	for <pana@ietf.org>; Fri, 2 Jul 2004 09:10:04 +0300 (EET DST)
X-Scanned: Fri, 2 Jul 2004 09:09:48 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i6269mmB020644
	for <pana@ietf.org>; Fri, 2 Jul 2004 09:09:48 +0300
Received: from mgw-int2.ntc.nokia.com (172.21.143.97)
	by esdks004.ntc.nokia.com 009PPxBS; Fri, 02 Jul 2004 09:09:47 EEST
Received: from esebh003.NOE.Nokia.com (esebh003.ntc.nokia.com [172.21.138.82])
	by mgw-int2.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i6269lH07948
	for <pana@ietf.org>; Fri, 2 Jul 2004 09:09:47 +0300 (EET DST)
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by
	esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Fri, 2 Jul 2004 09:09:47 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 2 Jul 2004 09:09:47 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA02236289@esebe008.ntc.nokia.com>
Thread-Topic: [issue100] PSR and PSA sequence number clarification
Thread-Index: AcRf+vfYk4k0Y4WlTv+Ezxhw9ctfyQAABR+g
To: <pana@ietf.org>
X-OriginalArrivalTime: 02 Jul 2004 06:09:47.0698 (UTC)
	FILETIME=[2D704920:01C45FFB]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no 
	version=2.60
Subject: [Pana] NEW: [issue100] PSR and PSA sequence number clarification
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1415381235=="
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

--===============1415381235==
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

TmV3IHN1Ym1pc3Npb24gZnJvbSBEYW4gRm9yc2JlcmcgPGRhbi5mb3JzYmVyZ0Bub2tpYS5jb20+
Og0KDQo+ID4tIFdoZW4gYSBQYUMgc2VuZHMgYSBQQU5BLVN0YXJ0LUFuc3dlciBtZXNzYWdlIGlu
IHJlc3BvbnNlIHRvIGEgdmFsaWQNCj4gPlBBTkEtU3RhcnQtUmVxdWVzdCBtZXNzYWdlIHdpdGhv
dXQgYSBDb29raWUgQVZQLCB0aGUgYW5zd2VyIG1lc3NhZ2UNCj4gPmNhbiBiZSBsb3N0LiAgVGhl
IFBBTkEtU3RhcnQtUmVxdWVzdCB3b3VsZCBiZSByZXRyYW5zbWl0dGVkLiAgVG8gZGVhbA0KPiA+
d2l0aCB0aGUgY2FzZSwgaXQgbWlnaHQgYmUgYmV0dGVyIGZvciB0aGUgUGFDIHRvIHJldHVybiBh
IGR1cGxpY2F0ZQ0KPiA+UEFOQS1TdGFydC1BbnN3ZXIgbWVzc2FnZSBhZnRlciB0aGUgUGFDIGhh
cyBiZWVuIHNlbnQgdGhlIGZpcnN0DQo+ID5QQU5BLVN0YXJ0LUFuc3dlciBtZXNzYWdlIHVudGls
IHRoZSBQYUMgcmVjZWl2ZXMgYSB2YWxpZA0KPiA+UEFOQS1BdXRoLVJlcXVlc3QgbWVzc2FnZS4N
Cj4gPiAgDQo+ID4NCj4gSW4gdGhpcyBjYXNlLCBJIGd1ZXNzIFBBTkEtU3RhcnQtUmVxdWVzdCB3
b3VsZCBiZSByZXRyYW5zbWl0dGVkIGJ5DQo+IHVwZGF0aW5nIHRyYW5zbWlzc2lvbiBzZXF1ZW5j
ZSBudW1iZXIgLCBhbmQgUEFOQS1TdGFydC1SZXF1ZXN0IGJ5DQo+IHVkcGF0aW5nIHRyYW5zbWlz
c2lvbiBhbmQgcmVjZWl2ZWQgc2VxdWVuY2UgbnVtYmVycykuIFRoYXQgaXM6DQo+IA0KPiBQYUMg
UEFBDQo+IA0KPiBQU1IoeCwwKQ0KPiA8LS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IFBTQSh5LHgp
DQo+IC0tLS0tLS0tLVgtLS0tLS0tLS0+DQo+IFBTUih4KzEsMCkNCj4gPC0tLS0tLS0tLS0tLS0t
LS0tLS0NCj4gUFNBKHkrMSx4KzEpDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0+DQo+IA0KPiBBbSBJ
IHdyb25nPw0KDQpXaXRoIGluY3JlbWVudGluZyB0aGUgdHJhbnNtaXNzaW9uIHNlcXVlbmNlIG51
bWJlcnMgaW4gUFNSIGFuZCBQU0ENCmJlZm9yZSB0aGUgdHdvIGVudGl0aWVzIGNvbXBsZXRlIGlu
aXRpYWwgc2VxdWVuY2UgbnVtYmVyIG5lZ290aWF0aW9uLA0KaXQgaXMgcG9zc2libGUgdG8gZmFp
bCB0byBzaGFyZSB0aGUgc2FtZSBwYWlyIG9mIGluaXRpYWwgc2VxdWVuY2UNCm51bWJlcnMgYmV0
d2VlbiBQYUMgYW5kIFBBQS4gIFNvIHNlcXVlbmNlIG51bWJlcnMgc2hvdWxkIG5vdCBiZQ0KaW5j
cmVtZW50ZWQgaW4gUFNSIGFuZCBQU0EuICBJIHRoaW5rIHNlY3Rpb24gNC4xLjQgc2hvdWxkIGJl
IG1vcmUNCnNwZWNpZmljIG9uIHRoaXMuDQoNCllvc2hpaGlybyBPaGJhDQoNCi0tLS0tLS0tLS0N
CmNhdGVnb3J5OiBFZGl0b3JpYWwNCmRvY3VtZW50OiBkcmFmdC1pZXRmLXBhbmEtcGFuYS14eC50
eHQNCm1lc3NhZ2VzOiAzMzcNCm5vc3k6IGRmb3JzYmVyDQpwcmlvcml0eTogU2hvdWxkIEZpeA0K
c3RhdHVzOiBQZW5kaW5nDQp0aXRsZTogUFNSIGFuZCBQU0Egc2VxdWVuY2UgbnVtYmVyIGNsYXJp
ZmljYXRpb24NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KUEFOQSBJc3N1ZXMgPHBhbmFfaXNzdWVzQGRhbmZvcnNiZXJnLmluZm8+DQo8aHR0cDov
L2RhbmZvcnNiZXJnLmluZm86ODA4MC9wYW5hLWlzc3Vlcy9pc3N1ZTEwMD4NCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K


--===============1415381235==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana

--===============1415381235==--


From pana-bounces@ietf.org  Fri Jul  2 04:14:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14121
	for <pana-archive@lists.ietf.org>; Fri, 2 Jul 2004 04:14:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BgIzs-00072s-9n; Fri, 02 Jul 2004 04:02:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BgIvC-0004xW-7v
	for pana@megatron.ietf.org; Fri, 02 Jul 2004 03:57:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13530
	for <pana@ietf.org>; Fri, 2 Jul 2004 03:57:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BgIv9-0000Y1-Jd
	for pana@ietf.org; Fri, 02 Jul 2004 03:57:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BgIu8-0000Ao-00
	for pana@ietf.org; Fri, 02 Jul 2004 03:56:17 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12) id 1BgItK-0007W1-00
	for pana@ietf.org; Fri, 02 Jul 2004 03:55:26 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 30018308F1; Fri,  2 Jul 2004 09:54:54 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id 15DEA30871; Fri,  2 Jul 2004 09:54:54 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id 78BB414426; Fri,  2 Jul 2004 09:53:11 +0200 (MET DST)
Message-ID: <40E51503.9000809@dif.um.es>
Date: Fri, 02 Jul 2004 09:55:47 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Lost answer problem (a new issue)
References: <20040629003737.GA25808@steelhead> <40E42C1B.5080609@dif.um.es>
	<20040717211804.GB1753@steelhead>
In-Reply-To: <20040717211804.GB1753@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi Yoshihiro... see my comments below

Yoshihiro Ohba wrote:

>Hi Rafa,
>
>On Thu, Jul 01, 2004 at 05:22:03PM +0200, Rafael Marin Lopez wrote:
>  
>
>>Hi Yoshihiro
>>
>>Yoshihiro Ohba wrote:
>>
>>    
>>
>>>There might be some cases in which a PaC or a PAA might need to send a
>>>duplicate answer to a retransmitted old request (as well as a fresh
>>>answer to a new request if any) considering that an answer message for
>>>an old request can be lost. 
>>>
>>>Without this, a PANA session may stall in
>>>a way that the requester keeps retransmitting the old request while
>>>the responder may keep discarding them with waiting for a new request.
>>>The cases are described below.
>>>
>>>- When a PaC sends a PANA-Start-Answer message in response to a valid
>>>PANA-Start-Request message without a Cookie AVP, the answer message
>>>can be lost.  The PANA-Start-Request would be retransmitted.  To deal
>>>with the case, it might be better for the PaC to return a duplicate
>>>PANA-Start-Answer message after the PaC has been sent the first
>>>PANA-Start-Answer message until the PaC receives a valid
>>>PANA-Auth-Request message.
>>> 
>>>
>>>      
>>>
>>In this case, I guess PANA-Start-Request would be retransmitted by
>>updating transmission sequence number , and PANA-Start-Request by
>>udpating transmission and received sequence numbers). That is:
>>
>>PaC PAA
>>
>>PSR(x,0)
>><---------------------
>>PSA(y,x)
>>---------X--------->
>>PSR(x+1,0)
>><-------------------
>>PSA(y+1,x+1)
>>------------------->
>>
>>Am I wrong?
>>    
>>
>
>
>With incrementing the transmission sequence numbers in PSR and PSA
>before the two entities complete initial sequence number negotiation,
>it is possible to fail to share the same pair of initial sequence
>numbers between PaC and PAA.
>
I guess you mean : PANA session stores ISN_Pac and ISN_PAA values and if
transmission sequence numbers are incremented (as in example) ISN_Pac
and/or ISN_PAA has not good values.

Becuase I cannot see problem when ISN_PaC and ISN_PAA are equal. could
you clarify it?

>  So sequence numbers should not be
>incremented in PSR and PSA.  I think section 4.1.4 should be more
>specific on this.
>  
>
I think so as well

Regards.

>Yoshihiro Ohba
>
>
>
>
>  
>
>>>- When a PaC sends a PANA-FirstAuth-End-Answer message in response to a
>>>valid PANA-FirstAuth-End-Request message (remember that a
>>>PANA-FirstAuth-End exchange is used for delimiting the first and
>>>second EAP authentications), the answer message may be lost.  The
>>>PANA-FirstAuth-End-Request would be retransmitted (with updating
>>>transmission sequence number).  To deal with the case, it might be
>>>better for the PaC to return a duplicate PANA-FirstAuth-End-Answer
>>>message (with updating transmission and received sequence numbers)
>>>after the PaC has been sent the first PANA-FirstAuth-End-Answer
>>>message until the PaC receives a valid PANA-Auth-Request message for
>>>the second EAP authentication.
>>>
>>>- When a PaC sends a PANA-Bind-Answer message in response to a valid
>>>PANA-Bind-Request message, the answer message can be lost.  As as
>>>result, the PAA will retransmit the PANA-Bind-Request (but with using
>>>a different transmission sequence number).  To deal with the case, it
>>>might be better for the PaC to return a duplicate PANA-Bind-Answer
>>>message (but with using different transmission and received sequence
>>>numbers) for a while after the first PANA-Bind-Request was received.
>>>The same thing can also apply to a PANA-Address-Update-Answer message
>>>that is sent by a PaC.
>>>
>>>- When a PaC or a PAA sends a PANA-Termination-Answer message in
>>>response to a valid PANA-Termination-Request message, the answer
>>>message can be lost.  As as result, the requester will retransmit the
>>>request (but with using a different transmission sequence number).  To
>>>deal with the case, it might be better for the sender of the answer to
>>>return a duplicate answer (with using different transmission and
>>>received sequence numbers) for a while after the first
>>>PANA-Termination-Request was received.  The same thing can also apply
>>>to a PANA-Reauth-Answer message that is sent by a PaC or a PAA.
>>>
>>>Those could improve robustness of the PANA protocol against loss of
>>>answer message.
>>>
>>>Comments?
>>>
>>>Yoshihiro Ohba
>>>
>>>_______________________________________________
>>>Pana mailing list
>>>Pana@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/pana
>>>
>>>
>>> 
>>>
>>>      
>>>
>>-- 
>>------------------------------------------------------
>>Rafael Marin Lopez
>>Faculty of Computer Science-University of Murcia
>>30071 Murcia - Spain
>>Telf: +34968367645    e-mail: rafa@dif.um.es
>>------------------------------------------------------
>>
>>
>>_______________________________________________
>>Pana mailing list
>>Pana@ietf.org
>>https://www1.ietf.org/mailman/listinfo/pana
>>    
>>
>
>_______________________________________________
>Pana mailing list
>Pana@ietf.org
>https://www1.ietf.org/mailman/listinfo/pana
>
>
>  
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul  2 09:37:02 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05557
	for <pana-archive@lists.ietf.org>; Fri, 2 Jul 2004 09:37:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BgO5S-0007mT-Cq; Fri, 02 Jul 2004 09:28:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BgNwn-0003do-8b
	for pana@megatron.ietf.org; Fri, 02 Jul 2004 09:19:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04107
	for <pana@ietf.org>; Fri, 2 Jul 2004 09:19:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BgNwm-00056U-G1
	for pana@ietf.org; Fri, 02 Jul 2004 09:19:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BgNvj-0004kZ-00
	for pana@ietf.org; Fri, 02 Jul 2004 09:18:16 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BgNuq-0004Oi-00
	for pana@ietf.org; Fri, 02 Jul 2004 09:17:20 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i62DHFpD023043;
	Fri, 2 Jul 2004 22:17:15 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i62DHFen018491;
	Fri, 2 Jul 2004 22:17:15 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	YAA18490 ; Fri, 2 Jul 2004 22:17:15 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA05343; Fri, 2 Jul 2004 22:17:14 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA13548;
	Fri, 2 Jul 2004 22:17:14 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i62DHDpl016046;
	Fri, 2 Jul 2004 22:17:13 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0800J4H7KM6A@tsbpo1.po.toshiba.co.jp>; Fri,
	2 Jul 2004 22:17:13 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BmBXC-0001Tt-00; Sun, 18 Jul 2004 06:16:54 -0700
Date: Sun, 18 Jul 2004 09:16:54 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Lost answer problem (a new issue)
In-reply-to: <40E51503.9000809@dif.um.es>
To: Rafael Marin Lopez <rafa@dif.um.es>
Message-id: <20040718131654.GD1753@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Rafael Marin Lopez <rafa@dif.um.es>,
	Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040629003737.GA25808@steelhead> <40E42C1B.5080609@dif.um.es>
	<20040717211804.GB1753@steelhead> <40E51503.9000809@dif.um.es>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.3 required=5.0 tests=AWL,DATE_IN_FUTURE_96_XX 
	autolearn=no version=2.60
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Fri, Jul 02, 2004 at 09:55:47AM +0200, Rafael Marin Lopez wrote:
> Hi Yoshihiro... see my comments below
> 
> Yoshihiro Ohba wrote:
> 
> >Hi Rafa,
> >
> >On Thu, Jul 01, 2004 at 05:22:03PM +0200, Rafael Marin Lopez wrote:
> >  
> >
> >>Hi Yoshihiro
> >>
> >>Yoshihiro Ohba wrote:
> >>
> >>    
> >>
> >>>There might be some cases in which a PaC or a PAA might need to send a
> >>>duplicate answer to a retransmitted old request (as well as a fresh
> >>>answer to a new request if any) considering that an answer message for
> >>>an old request can be lost. 
> >>>
> >>>Without this, a PANA session may stall in
> >>>a way that the requester keeps retransmitting the old request while
> >>>the responder may keep discarding them with waiting for a new request.
> >>>The cases are described below.
> >>>
> >>>- When a PaC sends a PANA-Start-Answer message in response to a valid
> >>>PANA-Start-Request message without a Cookie AVP, the answer message
> >>>can be lost.  The PANA-Start-Request would be retransmitted.  To deal
> >>>with the case, it might be better for the PaC to return a duplicate
> >>>PANA-Start-Answer message after the PaC has been sent the first
> >>>PANA-Start-Answer message until the PaC receives a valid
> >>>PANA-Auth-Request message.
> >>> 
> >>>
> >>>      
> >>>
> >>In this case, I guess PANA-Start-Request would be retransmitted by
> >>updating transmission sequence number , and PANA-Start-Request by
> >>udpating transmission and received sequence numbers). That is:
> >>
> >>PaC PAA
> >>
> >>PSR(x,0)
> >><---------------------
> >>PSA(y,x)
> >>---------X--------->
> >>PSR(x+1,0)
> >><-------------------
> >>PSA(y+1,x+1)
> >>------------------->
> >>
> >>Am I wrong?
> >>    
> >>
> >
> >
> >With incrementing the transmission sequence numbers in PSR and PSA
> >before the two entities complete initial sequence number negotiation,
> >it is possible to fail to share the same pair of initial sequence
> >numbers between PaC and PAA.
> >
> I guess you mean : PANA session stores ISN_Pac and ISN_PAA values and if
> transmission sequence numbers are incremented (as in example) ISN_Pac
> and/or ISN_PAA has not good values.

Yes.

> 
> Becuase I cannot see problem when ISN_PaC and ISN_PAA are equal. could
> you clarify it?

I don't mean that ISN_PaC and ISN_PAA are equal.  

> 
> >  So sequence numbers should not be
> >incremented in PSR and PSA.  I think section 4.1.4 should be more
> >specific on this.
> >  
> >
> I think so as well

OK, I will propose some text.

Yoshihiro Ohba

> 
> Regards.
> 
> >Yoshihiro Ohba
> >
> >
> >
> >
> >  
> >
> >>>- When a PaC sends a PANA-FirstAuth-End-Answer message in response to a
> >>>valid PANA-FirstAuth-End-Request message (remember that a
> >>>PANA-FirstAuth-End exchange is used for delimiting the first and
> >>>second EAP authentications), the answer message may be lost.  The
> >>>PANA-FirstAuth-End-Request would be retransmitted (with updating
> >>>transmission sequence number).  To deal with the case, it might be
> >>>better for the PaC to return a duplicate PANA-FirstAuth-End-Answer
> >>>message (with updating transmission and received sequence numbers)
> >>>after the PaC has been sent the first PANA-FirstAuth-End-Answer
> >>>message until the PaC receives a valid PANA-Auth-Request message for
> >>>the second EAP authentication.
> >>>
> >>>- When a PaC sends a PANA-Bind-Answer message in response to a valid
> >>>PANA-Bind-Request message, the answer message can be lost.  As as
> >>>result, the PAA will retransmit the PANA-Bind-Request (but with using
> >>>a different transmission sequence number).  To deal with the case, it
> >>>might be better for the PaC to return a duplicate PANA-Bind-Answer
> >>>message (but with using different transmission and received sequence
> >>>numbers) for a while after the first PANA-Bind-Request was received.
> >>>The same thing can also apply to a PANA-Address-Update-Answer message
> >>>that is sent by a PaC.
> >>>
> >>>- When a PaC or a PAA sends a PANA-Termination-Answer message in
> >>>response to a valid PANA-Termination-Request message, the answer
> >>>message can be lost.  As as result, the requester will retransmit the
> >>>request (but with using a different transmission sequence number).  To
> >>>deal with the case, it might be better for the sender of the answer to
> >>>return a duplicate answer (with using different transmission and
> >>>received sequence numbers) for a while after the first
> >>>PANA-Termination-Request was received.  The same thing can also apply
> >>>to a PANA-Reauth-Answer message that is sent by a PaC or a PAA.
> >>>
> >>>Those could improve robustness of the PANA protocol against loss of
> >>>answer message.
> >>>
> >>>Comments?
> >>>
> >>>Yoshihiro Ohba
> >>>
> >>>_______________________________________________
> >>>Pana mailing list
> >>>Pana@ietf.org
> >>>https://www1.ietf.org/mailman/listinfo/pana
> >>>
> >>>
> >>> 
> >>>
> >>>      
> >>>
> >>-- 
> >>------------------------------------------------------
> >>Rafael Marin Lopez
> >>Faculty of Computer Science-University of Murcia
> >>30071 Murcia - Spain
> >>Telf: +34968367645    e-mail: rafa@dif.um.es
> >>------------------------------------------------------
> >>
> >>
> >>_______________________________________________
> >>Pana mailing list
> >>Pana@ietf.org
> >>https://www1.ietf.org/mailman/listinfo/pana
> >>    
> >>
> >
> >_______________________________________________
> >Pana mailing list
> >Pana@ietf.org
> >https://www1.ietf.org/mailman/listinfo/pana
> >
> >
> >  
> >
> 
> 
> -- 
> ------------------------------------------------------
> Rafael Marin Lopez
> Faculty of Computer Science-University of Murcia
> 30071 Murcia - Spain
> Telf: +34968367645    e-mail: rafa@dif.um.es
> ------------------------------------------------------
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul  5 01:08:32 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22135
	for <pana-archive@lists.ietf.org>; Mon, 5 Jul 2004 01:08:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhLe0-0003Je-QZ; Mon, 05 Jul 2004 01:03:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhLVS-0002YY-6R
	for pana@megatron.ietf.org; Mon, 05 Jul 2004 00:55:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21670
	for <pana@ietf.org>; Mon, 5 Jul 2004 00:54:57 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhLVL-0004jR-7Z
	for pana@ietf.org; Mon, 05 Jul 2004 00:54:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhLUW-0004Sj-00
	for pana@ietf.org; Mon, 05 Jul 2004 00:54:10 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BhLTm-0004Ce-00
	for pana@ietf.org; Mon, 05 Jul 2004 00:53:22 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i654rJpD006241;
	Mon, 5 Jul 2004 13:53:19 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i654rJr7021995;
	Mon, 5 Jul 2004 13:53:19 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	PAA21990 ; Mon, 5 Jul 2004 13:53:19 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id NAA00067; Mon, 5 Jul 2004 13:53:18 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id NAA14006;
	Mon, 5 Jul 2004 13:53:16 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i654rGpl027489;
	Mon, 5 Jul 2004 13:53:16 +0900 (JST)
Received: from steelhead (iVPN01-154.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0D00F9T48P62@tsbpo1.po.toshiba.co.jp>; Mon,
	5 Jul 2004 13:53:15 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BhLRc-0004LH-00; Sun, 04 Jul 2004 21:51:08 -0700
Date: Mon, 05 Jul 2004 00:51:08 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Randy Turner's comments #1
In-reply-to: <017d01c45fcc$8302c360$981d9069@sisa.samsung.com>
To: "'Randy Turner'" <rturner@amalfisystems.com>,
        Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040705045108.GE5655@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: 'Randy Turner' <rturner@amalfisystems.com>,
	Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <017d01c45fcc$8302c360$981d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hello Randy Turner,

Thank you very much for sending valuable comments.  Please see my
comments in line.

On Thu, Jul 01, 2004 at 05:35:40PM -0700, Alper Yegin wrote:
> Hello,
> 
> Here is some feedback from Randy Turner on the PANA documents. Stay
> tuned for more....
> 
> Alper
> 
> ----------------
> 
> 
> Comments on draft-ietf-pana-framework-00
> 
> (This was the version available on the IETF website PANA WG links)
> 
> 
> 
> 
> ------
> Section 3 of the PANA Framework Document...
> 
> The last three paragraphs of section 3 describe the high-level exchange
> necessary for a PaC to gain access to the network, and you also describe
> the fact that an SA exists between the PaC and the EP.  I would
> emphasize the point here (again) that the SA can either be implicit (in
> the case of DSL and a pre-secured link) or explicit (requiring protocol
> support "on the wire").

I agree that there can be a pre-established SA between PaC and EP when
PANA runs over pre-secured link.  One example is cdma2000 where a
link-layer SA needs to be established between a mobile and the radio
access network before establishing IP connectivity.  In this case, a
secure association protocol after PANA authentication is not
performed.  But I think it is probably not a good idea to use the word
"implicit SA" to represent the pre-established SA because the word
seems ambiguous.  Also, I am not sure what kind of security
association exists between PaC and EP in the case of physicaly secured
link because there is no cryptographic key shared betwen the two
entities.

> 
> And I would also emphasize (even though it might be obvious to some),
> that since an explicit SA typically requires some type of secure
> encapsulation, and additional overhead, that this protocol overhead will
> get stripped off at the EP and not affect communications beyond the EP.

OK.  How about revising the second last paragraph of section 3 from:

"
   In case a cryptographic access control needs to be enabled after the
   PANA authentication, a secure association protocol runs between the
   PaC and the EP.  The PaC should already have the input parameters to
   this process as a result of the successful PANA exchange. Similarly,
   the EP should have obtained them from the PAA via SNMP.  Secure
   association exchange produces the required security associations
   between the PaC and the EP to enable per-packet protection.
"

to:

"
   In case a cryptographic access control needs to be enabled after
   the PANA authentication, a secure association protocol runs between
   the PaC and the EP.  The PaC should already have the input parameters to
   this process as a result of the successful PANA exchange.  Similarly,
   the EP should have obtained them from the PAA via SNMP.  Secure
   association exchange produces the required security associations
   between the PaC and the EP to enable per-packet protection.
   Per-packet protection introduces additional per-packet overhead but
   the overhead exists only between the PaC and EP and will not
   affect communications beyond the EP.  In this sense it is important
   to place the EP as close to the edge of the network as possible.
"

> 
> You've already stated earlier in the draft, as I commented in my
> original comments to you in earlier drafts, that it's important to place
> the EP as close to the edge of the network as possible . So given this
> point,  the "cost" of erecting an SA is also reduced because it only
> exists for the initial "hop" in the access network.

I think the revised text above covers this point.

> 
> -------
> 
> With regards to the following text:
> 
>  PRPA and the IP address of PAA are assumed to be on the same IP
>       subnet, hence the PaC and PAA can perform on-link communication as
>       required by PANA.  When the PaC replaces its IPv4 PRPA with POPA,
>       this assumption may not hold true. In order to maintain the same
>       on-link communication, the PaC and PAA SHOULD create host routes
>       to each other upon PaC's IP address change.  The PaC SHOULD create
>       a host route to the PAA, and the PAA SHOULD create a host route to
>       the PaC (POPA).
> 
> I didn't see anywhere in the document leading up to this section a
> discussion on the entity that is responsible for configuring the POPA.
> Does the PAA have to be co-resident with the host that is responsible
> for allocating/communicating the POPA to the PaC ?  If not, then the PAA
> must "snoop" the IP configuration process between the PaC and the
> "allocation entity" in order to create the necessary host route to the
> PaC.  Let me know if I missed something in the text.

Right.  This was addressed in PANA specification Issue 85
(http://danforsberg.info:8080/pana-issues/issue85).  To deal with
this, PANA-Address-Update-Request/Answer messages the current PANA
specification snapshot
(http://www.toshiba.com/tari/pana/draft-ietf-pana-pana-05b.txt).

But I think we need some text in the framework draft.  How about
revising the above text to:

"
PRPA and the IP address of PAA are assumed to be on the same IP
subnet, hence the PaC and PAA can perform on-link communication as
required by PANA.  When the PaC replaces its IPv4 PRPA with POPA, this
assumption may not hold true. In order to maintain the same on-link
communication, the PaC and PAA SHOULD create host routes to each other
upon PaC's IP address change.  The PaC SHOULD create a host route to
the PAA, and the PAA SHOULD create a host route to the PaC (POPA).
PANA defines a mechanism for the PaC to report the POPA to the PAA.
"

> 
> -------
> 
> Regarding the following text...
> 
>  When an IPv4 PRPA is configured, the same address may be used as
>       both IPsec-TOA and IPsec-TIA.  In this case, a POPA is not
>       configured.  Alternatively, an IPsec-TIA can be obtained via the
>       configuration method available within [RFC3456] for IPv4, and
>       [I-D.ietf-ipsec-ikev2] for both IPv4 and IPv6. This newly
>       configured address constitutes a POPA.  Please refer to
>       [I-D.ietf-pana-ipsec] for more details.
> 
> The last time I looked at the internals of an IPSEC implementation, and
> the associated routing that takes place, the inner tunnel typically
> reflects a different network than the network that is reflected by
> IPSEC-TOA.  This means that the IP stack has (at least) two entries in
> the route table. One entry says how to send a packet to the network
> indicated by the TOA, and another route entry that says how to send
> packets that are destined for the network reflected by the TIA.  the
> remote node would have two different route entries that map to the same
> network. UNLESS one of the route entries (for the TIA as an example)
> contains a longer prefix than the route entry reflecting the TOA
> network. This is how I was able to "force" packets down a tunnel if I
> had overlapping routes. Is this making sense? I guess what I'm
> suggesting is that the NAP probably would not use this capability
> because of it's special nature.  Other IPSEC implementations may make
> this easier I don't know. Let me know if you think this is something
> that should be clarified.

I think this routing issue is common to most IPsec tunnel mode
implementations and not speficic to IPsec tunnel mode usage with PANA.
So I am not sure we need to clarify this is the PANA framework draft.

> 
> Also, If the PaC authenticates successfully and accesses the network,
> but there is an IPSEC SA between the PaC and PAA (or is it the EP), THEN
> the user subsequently creates an IPSEC tunnel between the PaC and say a
> corporate firewall termination point, how would this look? (assuming
> there's quite a bit of overhead on the PaC for maintaining these two
> SAs).

This aspect was once described in old pana-ipsec draft but removed
from the latest version, because there was some consensus that
consideration of remote IPsec gateway is out of scope of pana-ipsec
work.  I personally think that this issue is important but I am not
sure which document (existing one or a new one) would be the best
place to discuss this.

> 
> ------
> 
> I'm not clear on the functional distinction between sections 10.1.2 and
> 10.1.3 - The NAPT CPE is also a router (it's NAT'ing between address
> spaces). Since I don't believe NAPT has any specific impact on PANA
> (since the CPE is the Pac), I would have just combined these two
> sections, indicating that the router might also use NAPT.

I agree with you.  How above integrating section 10.1.2 and 10.2.3 
into a new section 10.1.2 as follows:

"
10.1.2 Router Mode

   In this case, the CPE acts as a router for the customer premises
   network.  The CPE itself may obtain the IP address using
   DHCP or be configured with static IP address.  Once the CPE is
   authenticated using PANA and is provided access to the service
   provider's network, the NAS should begin exchanging routing updates
   with the CPE. All devices at the customer premises will then have
   access to the service provider's network.

           Host--+
                 |
                 +----- CPE ---------------- NAS ------------- ISP
                 |   (Router, PaC)        (PAA,EP,AR)
           Host--+

                         Figure 9: Router Mode

   It is possible that both ends of the DSL link are configured with
   static IP addresses. PANA-based mutual authentication of CPE and
   NAS is desirable before data-traffic is exchanged between the
   customer premises network and the service provider network.  The
   CPE router may also use NAPT (Network Address Port Tranlation).
"

Regards,

Yoshihiro Ohba

> 
> -------

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul  5 13:18:42 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07567
	for <pana-archive@lists.ietf.org>; Mon, 5 Jul 2004 13:18:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhWrG-0007Qa-Lx; Mon, 05 Jul 2004 13:02:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhWik-0006lT-E3
	for pana@megatron.ietf.org; Mon, 05 Jul 2004 12:53:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06618
	for <pana@ietf.org>; Mon, 5 Jul 2004 12:53:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhWie-0004TW-G4
	for pana@ietf.org; Mon, 05 Jul 2004 12:53:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhWhe-0004B0-00
	for pana@ietf.org; Mon, 05 Jul 2004 12:52:27 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BhWga-0003fq-00
	for pana@ietf.org; Mon, 05 Jul 2004 12:51:21 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i65GpEpD026321;
	Tue, 6 Jul 2004 01:51:14 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i65GpEbY008092;
	Tue, 6 Jul 2004 01:51:14 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	BAA08091 ; Tue, 6 Jul 2004 01:51:14 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA13891; Tue, 6 Jul 2004 01:51:14 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA22060;
	Tue, 6 Jul 2004 01:51:13 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i65GpDpl009176;
	Tue, 6 Jul 2004 01:51:13 +0900 (JST)
Received: from steelhead (iVPN01-087.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0E00C0Z1HACF@tsbpo1.po.toshiba.co.jp>; Tue,
	6 Jul 2004 01:51:12 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BhWer-0004gZ-00; Mon, 05 Jul 2004 09:49:33 -0700
Date: Mon, 05 Jul 2004 12:49:28 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] PANA key derivation key
In-reply-to: <000001c45e2c$4d99bef0$981d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040705164928.GD17360@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040622153953.GA2625@steelhead>
	<000001c45e2c$4d99bef0$981d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

How about the following changes?

[1] In section 2,

change:

"
   AAA-Key:

      A key derived by the EAP peer and EAP server and transported to
      the authenticator [I-D.ietf-eap-keying].
"

to:

"
   AAA-Key:

      A key derived by the EAP peer and EAP server and transported to
      the authenticator [I-D.ietf-eap-keying].  In this document, when
      there are two such keys, namely AAA-Key1 and AAA-Key2, are
      generated as a result of running two EAP authentications in a
      single round of PANA authentication, the AAA-Key from
      which other keys are derived refers to the concatenation of
      AAA-Key1 and AAA-Key2.
"


[2] In section 4.1.5 of draft-ietf-pana-pana-04.txt change:


"
   The PANA_MAC_Key is used to integrity protect PANA messages.  When
   the PANA_MAC_Key is derived from a single AAA-Key, it is computed in
   the following way:


      PANA_MAC_KEY = The first N bits of
                     HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa | Session-ID)

   where the value of N depends on the integrity protection algorithm in
   use, i.e., N=160 for HMAC-SHY1.

   When the PANA_MAC_Key is derived from two AAA-Keys, it is computed in
   the following way:

      PANA_MAC_KEY = The first N bits of
                     HMAC_SHA1(AAA-Key1 | AAA-Key2, ISN_pac | ISN_paa |
                               Session-ID)

   where AAA-Key1 and AAA-Key2 are AAA-Keys for the first and second EAP
   authentication in a single PANA authentication phase, respectively.

   The length of AAA-Key, AAA-Key1 and AAA-Key2 MUST be N bits or
   longer.  See Section 4.1.6 for the detailed usage of the
   PANA_MAC_Key.
"

to:

"
   The PANA_MAC_Key is used to integrity protect PANA messages.  When
   the PANA_MAC_Key is derived from a single AAA-Key, it is computed in
   the following way:


      PANA_MAC_KEY = The first N bits of
                     HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa | Session-ID)

   where the value of N depends on the integrity protection algorithm
   in use, i.e., N=160 for HMAC-SHA1.  The length of AAA-Key MUST be N
   bits or longer.  See Section 4.1.6 for the detailed usage of the
   PANA_MAC_KEY.
"

[3] In section 4.3,

change:

"
   When separate NAP and ISP authentications are performed and the
   lower-layer is insecure, the two EAP methods MUST be capable of
   deriving keys.  In this case, if the first EAP authentication is
   successful, the PANA-FirstAuth-End-Request and
   PANA-FirstAuth-End-Answer messages as well as PANA-Auth-Request and
   PANA-Auth-Answer messages in the second EAP authentication MUST be
   protected with the key derived from the AAA-Key for the first EAP
   authentication. The PANA-Bind-Request and PANA-Bind-Answer messages
   and all subsequent PANA messages MUST be protected either with the
   AAA-Key for the first EAP authentication if the first EAP
   authentication succeeds and the second EAP authentication fails, or
   with the AAA-Key for the second EAP authentication if the first EAP
   authentication fails and the second EAP authentication succeeds, or
   with the compound key derived from the two AAA-Keys, one for the
   first EAP authentication and the other from the second EAP
   authentication, if both the first and second EAP authentications
   succeed (see Section 4.1.5 for how the compound key is derived).
"

to:

"
   When separate NAP and ISP authentications are performed and the
   lower-layer is insecure, the two EAP methods MUST be capable of
   deriving keys.  In this case, if the first EAP authentication is
   successful, the PANA-FirstAuth-End-Request and
   PANA-FirstAuth-End-Answer messages as well as PANA-Auth-Request and
   PANA-Auth-Answer messages in the second EAP authentication MUST be
   protected with the key derived from the AAA-Key for the first EAP
   authentication.  The PANA-Bind-Request and PANA-Bind-Answer
   messages and all subsequent PANA messages MUST be protected either
   with the AAA-Key for the first EAP authentication if the first EAP
   authentication succeeds and the second EAP authentication fails, or
   with the AAA-Key for the second EAP authentication if the first EAP
   authentication fails and the second EAP authentication succeeds, or
   with the compound AAA-Key derived from the two AAA-Keys, one for the
   first EAP authentication and the other from the second EAP
   authentication, if both the first and second EAP authentications
   succeed.
"

[4] In section 4.9,

change:

"
   As part of the context transfer, an intermediate AAA-Key material is
   provided by the previous PAA to the current PAA.

      AAA-Key-int = The first N bits of
                    HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)

   In case there are two AAA-Keys generated from a NAP-ISP
   authentication, the AAA-Key-int computation is:

      AAA-Key-int = The first N bits of
                    HMAC-SHA1(AAA-Key1 | AAA-Key2, DiameterIdentity |
                              Session-ID)
"

to:

"
   As part of the context transfer, an intermediate AAA-Key material is
   provided by the previous PAA to the current PAA.

      AAA-Key-int = The first N bits of
                    HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
"

Regards,

Yoshihiro Ohba


On Tue, Jun 29, 2004 at 03:56:22PM -0700, Alper Yegin wrote:
> Yoshi,
> 
> I understand these changes are proposed to have combine AAA keys when
> there are two of them. Couldn't we achieve the same by stating:
> 
> "AAA-key is set to (AAA-Key1 | AAA-Key2) when there are two EAP runs."
> 
> This could help collapse the two separate calculations into one in the
> pana-pana draft. Also what pana-ipsec refers to would still be valid.
> And we wouldn't need to compute a new key and use prf+ (simplification).
> 
> What do you think?
> 
> Alper
> 
>  
> 
> 
> > -----Original Message-----
> > From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf
> Of
> > Yoshihiro Ohba
> > Sent: Tuesday, June 22, 2004 8:40 AM
> > To: pana@ietf.org
> > Subject: [Pana] PANA key derivation key
> > 
> > To reflect Pasi's comment on how to deal with two AAA-Keys in
> > pana-ipsec draft and resulting discussions, here is a proposed text
> > for PANA specification draft to define PANA_KD_Key.
> > 
> > In section 4.1.5 of draft-ietf-pana-pana-04.txt,
> > 
> > change:
> > 
> > "
> >       *  PANA SA attributes:
> > 
> >          +  AAA-Key
> > 
> >          +  AAA-Key Identifier
> > 
> >          +  PANA_MAC_Key
> > 
> >    The PANA_MAC_Key is used to integrity protect PANA messages.  When
> >    the PANA_MAC_Key is derived from a single AAA-Key, it is computed
> in
> >    the following way:
> > 
> > 
> >       PANA_MAC_KEY = The first N bits of
> >                      HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa |
> Session-ID)
> > 
> >    where the value of N depends on the integrity protection algorithm
> in
> >    use, i.e., N=160 for HMAC-SHA1.
> > 
> >    When the PANA_MAC_Key is derived from two AAA-Keys, it is computed
> in
> >    the following way:
> > 
> >       PANA_MAC_KEY = The first N bits of
> >                      HMAC_SHA1(AAA-Key1 | AAA-Key2, ISN_pac | ISN_paa
> |
> >                                Session-ID)
> > 
> >    where AAA-Key1 and AAA-Key2 are AAA-Keys for the first and second
> EAP
> >    authentication in a single PANA authentication phase, respectively.
> > 
> >    The length of AAA-Key, AAA-Key1 and AAA-Key2 MUST be N bits or
> >    longer.  See Section 4.1.6 for the detailed usage of the
> >    PANA_MAC_Key.
> > "
> > 
> > to:
> > 
> >       *  PANA SA attributes:
> > 
> >          +  AAA-Key
> > 
> >          +  AAA-Key Identifier
> > 
> >          +  PANA_MAC_Key
> > 
> >          +  PANA_KD_Key
> > 
> >    The PANA_MAC_Key is used to integrity protect PANA messages.  The
> >    PANA_KD_Key is used to derive keys used for bootstrapping
> >    per-packet ciphering between PaC and EP.  The PANA_MAC_Key has a
> >    length of N bits, where the value of N depends on the integrity
> >    protection algorithm in use, which is HMAC-SHA1 in this document
> >    and N would be 160 bits for this case.  The PANA_KD_Key has a
> >    length of 512 bits, which is equal to the typical length of a
> >    AAA-Key or an EAP Master Session Key [I-D.ietf-eap-keying].
> > 
> >    When the PANA_MAC_Key and PANA_PD_Key are derived from a single
> >    AAA-Key, it is computed in the following way:
> > 
> >       {PANA_MAC_Key | PANA_KD_Key} =
> >             HMAC_SHA1+(AAA-Key, ISN_pac | ISN_paa | Session-ID)
> > 
> >    When PANA_MAC_Key and PANA_PD_Key are derived from two AAA-Keys, it
> >    is computed in the following way:
> > 
> >       {PANA_MAC_Key | PANA_KD_Key} =
> >             HMAC_SHA1+(AAA-Key1 | AAA-Key2, ISN_pac | ISN_paa |
> Session-
> > ID)
> > 
> >    In the above key derivation algorithms, HMAC_SHA1+ is the
> >    iteratively calculated version of HMAC_SHA1 algorithm by applying
> >    HMAC_SHA1 in the prf+ function defined in IKEv2
> >    [I-D:ietf-ipsec-ikev2].  AAA-Key1 and AAA-Key2 are AAA-Keys for the
> >    first and second EAP authentication in a single PANA authentication
> >    phase, respectively.  The length of AAA-Key, AAA-Key1 and AAA-Key2
> >    MUST be 160 bits or longer.  See Section 4.1.6 for the detailed
> >    usage of the PANA_MAC_Key.  See [I-D:ietf-pana-ipsec] for the usage
> >    of the PANA_KD_Key for bootstrapping IPsec between PaC and EP.
> > "
> > 
> > Regards,
> > 
> > Yoshihiro Ohba
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul  5 13:36:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08201
	for <pana-archive@lists.ietf.org>; Mon, 5 Jul 2004 13:36:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhXDl-0000qG-11; Mon, 05 Jul 2004 13:25:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhX47-0008Tx-8d
	for pana@megatron.ietf.org; Mon, 05 Jul 2004 13:15:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07414
	for <pana@ietf.org>; Mon, 5 Jul 2004 13:15:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhX41-0003LO-Dy
	for pana@ietf.org; Mon, 05 Jul 2004 13:15:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhX2x-00032v-00
	for pana@ietf.org; Mon, 05 Jul 2004 13:14:28 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BhX1z-0002kf-00
	for pana@ietf.org; Mon, 05 Jul 2004 13:13:27 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i65HDQpD002495;
	Tue, 6 Jul 2004 02:13:26 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i65HDQXh015056;
	Tue, 6 Jul 2004 02:13:26 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	CAA15055 ; Tue, 6 Jul 2004 02:13:26 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA19535; Tue, 6 Jul 2004 02:13:25 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA00680;
	Tue, 6 Jul 2004 02:13:25 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i65HDOpl018602;
	Tue, 6 Jul 2004 02:13:24 +0900 (JST)
Received: from steelhead (iVPN01-087.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0E00CE72IACF@tsbpo1.po.toshiba.co.jp>; Tue,
	6 Jul 2004 02:13:24 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BhWrQ-0004j2-00; Mon, 05 Jul 2004 10:02:32 -0700
Date: Mon, 05 Jul 2004 13:02:31 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] NEW: [issue100] PSR and PSA sequence number clarification
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA02236289@esebe008.ntc.nokia.com>
To: pana@ietf.org
Message-id: <20040705170231.GE17360@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org, Dan.Forsberg@nokia.com
User-Agent: Mutt/1.5.6+20040523i
References: <FC5FF66A769AB044AED651C705EAA8EA02236289@esebe008.ntc.nokia.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Dan.Forsberg@nokia.com
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Here is a proposed text.

In section 4.1.4,

change:

"
   The two sequence number fields have the same length of 32 bits and
   appear in PANA header.  tseq starts from initial sequence number
   (ISN) and is monotonically increased by 1. The serial number
   arithmetic defined in [RFC1982] is used for sequence number
   operation. The ISNs are exchanged between PaC and PAA during the
   discovery and initial handshake phase (see Section 4.2). The rules
   that govern the sequence numbers in other phases are described as
   follows.
"

to:

"
   The two sequence number fields have the same length of 32 bits and
   appear in PANA header.  The transmission sequence number starts
   from initial sequence number (ISN) and is monotonically increased
   by 1. The serial number arithmetic defined in [RFC1982] is used for
   sequence number operation. The ISNs are exchanged between PaC and
   PAA during the discovery and initial handshake phase (see Section
   4.2).  The transmission sequence number is never incremented in the
   messages exchanged during discovery and initial handshake phase.
   The rules that govern the sequence numbers in other phases are
   described as follows.
"

Regards,

Yoshihiro Ohba


On Fri, Jul 02, 2004 at 09:09:47AM +0300, Dan.Forsberg@nokia.com wrote:
> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> 
> > >- When a PaC sends a PANA-Start-Answer message in response to a valid
> > >PANA-Start-Request message without a Cookie AVP, the answer message
> > >can be lost.  The PANA-Start-Request would be retransmitted.  To deal
> > >with the case, it might be better for the PaC to return a duplicate
> > >PANA-Start-Answer message after the PaC has been sent the first
> > >PANA-Start-Answer message until the PaC receives a valid
> > >PANA-Auth-Request message.
> > >  
> > >
> > In this case, I guess PANA-Start-Request would be retransmitted by
> > updating transmission sequence number , and PANA-Start-Request by
> > udpating transmission and received sequence numbers). That is:
> > 
> > PaC PAA
> > 
> > PSR(x,0)
> > <---------------------
> > PSA(y,x)
> > ---------X--------->
> > PSR(x+1,0)
> > <-------------------
> > PSA(y+1,x+1)
> > ------------------->
> > 
> > Am I wrong?
> 
> With incrementing the transmission sequence numbers in PSR and PSA
> before the two entities complete initial sequence number negotiation,
> it is possible to fail to share the same pair of initial sequence
> numbers between PaC and PAA.  So sequence numbers should not be
> incremented in PSR and PSA.  I think section 4.1.4 should be more
> specific on this.
> 
> Yoshihiro Ohba
> 
> ----------
> category: Editorial
> document: draft-ietf-pana-pana-xx.txt
> messages: 337
> nosy: dforsber
> priority: Should Fix
> status: Pending
> title: PSR and PSA sequence number clarification
> ___________________________________________________
> PANA Issues <pana_issues@danforsberg.info>
> <http://danforsberg.info:8080/pana-issues/issue100>
> ___________________________________________________

> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul  6 00:34:29 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05167
	for <pana-archive@lists.ietf.org>; Tue, 6 Jul 2004 00:34:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BhhZj-00008e-SH; Tue, 06 Jul 2004 00:28:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BhhUE-0007st-Pa
	for pana@megatron.ietf.org; Tue, 06 Jul 2004 00:23:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04729
	for <pana@ietf.org>; Tue, 6 Jul 2004 00:23:10 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BhhU7-0004Z7-QN
	for pana@ietf.org; Tue, 06 Jul 2004 00:23:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BhhT2-0004Bw-00
	for pana@ietf.org; Tue, 06 Jul 2004 00:22:04 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BhhQr-0003QJ-00
	for pana@ietf.org; Tue, 06 Jul 2004 00:19:50 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i664JnpD008366;
	Tue, 6 Jul 2004 13:19:49 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i664JnZ5028868;
	Tue, 6 Jul 2004 13:19:49 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	PAA28866 ; Tue, 6 Jul 2004 13:19:49 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id NAA07452; Tue, 6 Jul 2004 13:19:48 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id NAA26559;
	Tue, 6 Jul 2004 13:19:47 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i664Jkpl027486;
	Tue, 6 Jul 2004 13:19:46 +0900 (JST)
Received: from steelhead (iVPN01-131.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0E00104XCWRP@tsbpo1.po.toshiba.co.jp>; Tue,
	6 Jul 2004 13:19:45 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BhhEJ-0006qE-00; Mon, 05 Jul 2004 21:06:51 -0700
Date: Tue, 06 Jul 2004 00:06:51 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New: [issue98] Lost answer problem
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA02236278@esebe008.ntc.nokia.com>
To: pana@ietf.org
Message-id: <20040706040651.GL17360@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org, Dan.Forsberg@nokia.com
User-Agent: Mutt/1.5.6+20040523i
References: <FC5FF66A769AB044AED651C705EAA8EA02236278@esebe008.ntc.nokia.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Dan.Forsberg@nokia.com
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Here is a proposed solution for the lost answer problem.

---------------------------------
Insert the following section.

"
Section 4.X  Retransmission of Duplicate Answers

Since PANA is designed over UDP, an answer as well as a request can be
lost.  In order to improve robustness against possible loss of
synchronization between a PaC and a PAA, the responder of a request
MAY send a duplicate answer to a duplicate request for which already
answered (as well as a fresh answer to a new request if any).  In
PANA, a duplicate PANA-Start-Request or PANA-Start-Answer message has
the same contents as the original request or answer, respectively.  A
duplicate request other than PANA-Start-Request has the same contents
as the original request except for the transmission sequence number
and a MAC AVP (if any).  Also, a duplicate answer other than
PANA-Start-Answer has the same contents as the original answer except
for the transmission and receiving sequence numbers and a MAC AVP (if
any).  Retransmission of a duplicate answer in response to a duplicate
request occurs in the following ways.

o When a PaC receives a duplicate PANA-Start-Request message for which
it has already answered, it MAY send a duplicate PANA-Start-Answer
message until it receives a valid PANA-Auth-Request message.

o When a PaC receives a duplicate PANA-FirstAuth-End-Request message
for which it has already answered, it MAY send a duplicate
PANA-FirstAuth-End-Answer message until it receives a valid
PANA-Auth-Request message for the second EAP authentication.

o When a PaC receives a duplicate PANA-Bind-Request message for which
it has already answered, it MAY send a duplicate PANA-Bind-Answer
message until it receives some hint provided outside the PANA protocol
(e.g., receipt of a secure association protocol message from an EP or
receipt of data traffic) indicating that the PAA has received a
PANA-Bind-Answer message.

o When a PaC or a PAA receives a duplicate PANA-Termination-Request
message for which it has already answered, it MAY send a duplicate
PANA-Termination-Answer message for a while before deleting the PANA
session.  The period to send duplicate PANA-Termination-Answer
messages may be a configurable parameter.
"

Regards,

Yoshihiro Ohba

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul  7 03:02:36 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26589
	for <pana-archive@lists.ietf.org>; Wed, 7 Jul 2004 03:02:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bi5zI-0002R4-L8; Wed, 07 Jul 2004 02:33:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bi5gA-0003kE-9o
	for pana@megatron.ietf.org; Wed, 07 Jul 2004 02:13:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09270
	for <pana@ietf.org>; Wed, 7 Jul 2004 02:13:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bi5g3-00051K-2D
	for pana@ietf.org; Wed, 07 Jul 2004 02:13:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bi5fK-0004i1-00
	for pana@ietf.org; Wed, 07 Jul 2004 02:12:23 -0400
Received: from omr3.netsolmail.com ([216.168.230.164])
	by ietf-mx with esmtp (Exim 4.12) id 1Bi5eg-0004Oc-00
	for pana@ietf.org; Wed, 07 Jul 2004 02:11:42 -0400
Received: from ms4.netsolmail.com (IDENT:mirapoint@[216.168.230.177])
	by omr3.netsolmail.com (8.12.10/8.12.10) with ESMTP id i676AbT6027185
	for <pana@ietf.org>; Wed, 7 Jul 2004 02:10:37 -0400 (EDT)
Received: from [4.26.220.234] (wbar21.lax1-4.26.220.234.lax1.dsl-verizon.net
	[4.26.220.234])
	by ms4.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id BRC31612; Wed, 7 Jul 2004 02:11:41 -0400 (EDT)
User-Agent: Microsoft-Entourage/11.0.0.040405
Date: Tue, 06 Jul 2004 23:11:41 -0700
From: Randy Turner <rturner@amalfisystems.com>
To: <pana@ietf.org>
Message-ID: <BD10E22D.1123%rturner@amalfisystems.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Pana] Comments on draft-ietf-pana-pana-04
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit


Hi Alper, and the list,

I'm working my through the drafts as I get a moment (mainly on flights ;).
Here are some other comments on draft-ietf-pana-pana-04...more to follow.

I will try and hit the list with some final comments by this weekend.

Regards,
Randy
(will this group be meeting in San Diego?)



draft-ietf-pana-pana-04 comments
=========================================


The document mentions that PANA assumes that the PAA is one hop away from
the PaC. Is this a requirement on the topology, or could the scope of the
multicast be wider than this?

-------

In Section 4.7, Device ID Choice, the text says that "the ID can be an IP
address, a MAC address, or an identifier that is not carried on data packets
but has local significance." Maybe it's my years of doing standards, but I
think maybe you should stipulate that the device ID MUST NOT have temporal
characteristics. You're requiring that the PaC have an IP address prior to
PANA, which means that this address (in IPv4) will probably be a temporary
address (auto-configured somehow), and this would probably be especially
true in an IPv6 environment. Likewise, MAC addresses might have local
persistence that is more persistent than an IP address, but it could still
change.  I think that the device ID should reference an agreed upon value
between NAP or ISP and the PaC. The namespace might vary between ISP or NAP
but I think (if I were you) I would emphasize the non-transient nature of
the device ID. It's really what the authentication is all about so it's
important that this be solid. In the framework document, I think you mention
the use of network access identifiers (NAIs), which would be ideal for the
NAP case, but also something similar could be used for service provider
authentication as well. Correct me if I'm wrong, but to the PANA-aware nodes
in the network, the device-ID is an opaque series of bytes of some length.
Is this correct?

By the way, I'm assuming that it's possible for multiple PANA sessions to be
in progress at the same time. Probably one session for the NAP, and possibly
<N> number of service provider sessions.  Which brings me to another point
about the protocol document, and I believe the framework document.
Throughout these documents you've isolated the dominant  model of network
connectivity today: someone wants to get access to the global internet.  But
looking ahead, the use of PANA could be expanded to ISP, ASP, whatever. I
think it's important for the audience of PANA to understand that this is not
just an "ISP connectivity" method, but could be reused, as could the
topological infrastructure, for a number of different business models.

--------

I may have missed it, but it wasn't clear to me that the PaC state machine
could receive an unsolicited PANA-Start-Request until Figure 3 (just prior
to 4.3).  It might have been inferred in the discussion about race
conditions when a PANA-PAA-Discover message and a PANA-Start-Request message
are sent at the same time, but I was thinking this condition would only
occur if the PaC retransmitted the "discover" message quicker than the PAA
could respond. 

Is it part of the core state machine of PANA that the PaC OR the PAA can
start the process? I like the idea about how the EP can notify the PAA that
a potential PaC is trying to use the network prior to authentication. Would
this be the only scenario where the PAA initiates a PANA session?

---------

Regarding the overall security (integrity, possible confidentiality)
discussed in the draft (as well as in the PANA-IPSEC doc), I know that
integrity and confidentiality is a nice feature to offer,  but it only
encompasses a subset of the links that the traffic has to traverse. At the
application level, the endpoints of the application have knowledge of the
potential security requirements for the traffic that the protocol will
generate. If the application mandates security and confidentiality, then the
application will establish an "end-to-end" SA, utilizing possibly both
confidentiality and encryption.  If the application/service endpoint is
co-resident with the PaC functionality, I'm concerned about the overhead
involved in having duplicate, layered SAs established.  I think this concern
is restricted primarily to the confidentiality aspects of data traffic, and
not necessarily integrity checking.

NAP or ISP authentication credentials should probably be protected during
the PANA establishment phase, but this only happens during the
initialization of the session.  If I'm deploying an application that
requires confidentiality, I would probably not want to rely on layer-2 or
layer-3 mechanisms to guarantee conifdentiality. It's difficult for me to
see a scenario where a NAP would mandate confidentiality on a link. Nor a
traditional ISP. However, in an earlier comment, I suggested emphasizing the
fact that PANA could be used in an ASP environment as well, where the
"service provider selection" mechanism would select and create a network
between the PaC and an ASP. In this case, it's an "Application" Service
Provider, and the path between the PaC and ASP might require
confidentiality.

I feel like I'm rambling a bit here, but I think there's a point regarding
the applicability of a heavyweight SA that implements both confidentiality
and integrity for the link between the PaC and the PAA.

Without the discussion of IPSEC and complex SA mechanisms in the PANA
document set, the protocol seems much easier to grasp and understand (and
potentially implement, depending upon your point of view). In my experience,
carriers and network folk are drawn to simplicity. If you're open to this
idea, I think a quick and straightforward way to approach this would be to
isolate anything regarding confidentiality and complex SA establishment to a
document or documents external to the base PANA protocol specification.
You've got the basic AVP extensibility mechanisms anyway, so it's a short
walk for someone to use this method. You've already got the specifics
regarding EAP mechanisms outside the docs which is a good way to approach
this.

Overall, I understand the perceived need to potentially offer
confidentiality over network links that are "shared" at the edge, but I
believe that in most cases, it will be redundantly applied to protect
application information. I may be over-reacting a bit here, and it's not a
big deal for me, I just have had to make this balance before in complexity
and layering. Splitting off confidentiality from anything that might
resemble the "core" of PANA is the right way to go (and you've already done
this with the separate IPSEC draft). Because of the need to secure the PANA
session itself with respect to filtering at the EP, you have already bought
the requirement for session-tagging with integrity, so again, this is mainly
a confidentiality thing I'm talking about.

I was curious if the IESG or anyone else has commented on these particular
security aspects of PANA work?

----------





_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul  8 22:23:38 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07112
	for <pana-archive@lists.ietf.org>; Thu, 8 Jul 2004 22:23:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bik1j-0005eN-13; Thu, 08 Jul 2004 21:18:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BiiZZ-0001uY-UN
	for pana@megatron.ietf.org; Thu, 08 Jul 2004 19:45:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14746
	for <pana@ietf.org>; Thu, 8 Jul 2004 19:44:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BiiZT-0002rD-1F
	for pana@ietf.org; Thu, 08 Jul 2004 19:44:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BiiYY-0002TU-00
	for pana@ietf.org; Thu, 08 Jul 2004 19:44:00 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BiiXf-00024S-00
	for pana@ietf.org; Thu, 08 Jul 2004 19:43:03 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i68NgwpD023156;
	Fri, 9 Jul 2004 08:42:58 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i68NgwVd013499;
	Fri, 9 Jul 2004 08:42:58 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	JAA13493 ; Fri, 9 Jul 2004 08:42:58 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA29690; Fri, 9 Jul 2004 08:42:56 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA07143;
	Fri, 9 Jul 2004 08:42:53 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i68Ngqpl029539;
	Fri, 9 Jul 2004 08:42:52 +0900 (JST)
Received: from steelhead (iVPN01-108.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0K0095A4JFYW@tsbpo1.po.toshiba.co.jp>; Fri,
	9 Jul 2004 08:42:51 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BiiWA-0003rj-00; Thu, 08 Jul 2004 16:41:30 -0700
Date: Thu, 08 Jul 2004 19:41:30 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Comments on draft-ietf-pana-pana-04
In-reply-to: <BD10E22D.1123%rturner@amalfisystems.com>
To: Randy Turner <rturner@amalfisystems.com>
Message-id: <20040708234130.GF12291@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Randy Turner <rturner@amalfisystems.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <BD10E22D.1123%rturner@amalfisystems.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hello Randy Turner,

Thank you (again) for sending detailed comments.

Please see my comments below.

On Tue, Jul 06, 2004 at 11:11:41PM -0700, Randy Turner wrote:
> 
> Hi Alper, and the list,
> 
> I'm working my through the drafts as I get a moment (mainly on flights ;).
> Here are some other comments on draft-ietf-pana-pana-04...more to follow.
> 
> I will try and hit the list with some final comments by this weekend.
> 
> Regards,
> Randy
> (will this group be meeting in San Diego?)
> 
> 
> 
> draft-ietf-pana-pana-04 comments
> =========================================
> 
> 
> The document mentions that PANA assumes that the PAA is one hop away from
> the PaC. Is this a requirement on the topology, or could the scope of the
> multicast be wider than this?

This is a requirement on the topology, as described in Section 4.5.3
of draft-ietf-pana-requirements-08.txt.

> 
> -------
> 
> In Section 4.7, Device ID Choice, the text says that "the ID can be an IP
> address, a MAC address, or an identifier that is not carried on data packets
> but has local significance." Maybe it's my years of doing standards, but I
> think maybe you should stipulate that the device ID MUST NOT have temporal
> characteristics. You're requiring that the PaC have an IP address prior to
> PANA, which means that this address (in IPv4) will probably be a temporary
> address (auto-configured somehow), and this would probably be especially
> true in an IPv6 environment. Likewise, MAC addresses might have local
> persistence that is more persistent than an IP address, but it could still
> change.  I think that the device ID should reference an agreed upon value
> between NAP or ISP and the PaC. The namespace might vary between ISP or NAP
> but I think (if I were you) I would emphasize the non-transient nature of
> the device ID. It's really what the authentication is all about so it's
> important that this be solid. In the framework document, I think you mention
> the use of network access identifiers (NAIs), which would be ideal for the
> NAP case, but also something similar could be used for service provider
> authentication as well. 

I am not sure whether you are talking about device identifier or
session identifier or both, but in PANA, device identifier is
changeable.  In the next revision, we will have
PANA-Address-Update-Request/Answer messsages to update device ID as
well as POPA (you can check the latest snapshot in
http://www.toshiba.com/tari/pana/pana-spec.html.)  Since device
identifier is defined as a changeable parameter, we defined session
identifier as a stable identifier (except for the case of mobility
handling described in section 4.9 where session identifier changes
after handoff.)

> Correct me if I'm wrong, but to the PANA-aware nodes
> in the network, the device-ID is an opaque series of bytes of some length.
> Is this correct?

In PANA, device identifier have a Diameter Address type which is
derived from Diameter OctetString type.  PANA session identifier has
the same structure as Diameter Session-Id AVP.

> 
> By the way, I'm assuming that it's possible for multiple PANA sessions to be
> in progress at the same time. Probably one session for the NAP, and possibly
> <N> number of service provider sessions.  Which brings me to another point
> about the protocol document, and I believe the framework document.
> Throughout these documents you've isolated the dominant  model of network
> connectivity today: someone wants to get access to the global internet.  But
> looking ahead, the use of PANA could be expanded to ISP, ASP, whatever. I
> think it's important for the audience of PANA to understand that this is not
> just an "ISP connectivity" method, but could be reused, as could the
> topological infrastructure, for a number of different business models.

This is an interesting scenario, but I think there is some significant
issues related to having <N> number of global IP addresses assigned by
<N> service providers, namely, source address selection issue and
multi-homing issue.  It is probably not a good idea to allow <N>
number of service provider sessions in PANA until those issues are
fully studied.


> 
> --------
> 
> I may have missed it, but it wasn't clear to me that the PaC state machine
> could receive an unsolicited PANA-Start-Request until Figure 3 (just prior
> to 4.3).  It might have been inferred in the discussion about race
> conditions when a PANA-PAA-Discover message and a PANA-Start-Request message
> are sent at the same time, but I was thinking this condition would only
> occur if the PaC retransmitted the "discover" message quicker than the PAA
> could respond. 

I think Figures 2 and 3 are not good example to show the race
condition because in the examples both either PaC or PAA is the
initiator of the discovery and initial handshake phase.

      PaC   EP      PAA    Message
      ------------------------------------------------------
       ---->o              (DHCP traffic triggers discovery at PAA
             ------>        via PAA-to-EP protocol)
       ------+
       <-----|------       PANA-Start-Request(x,0)[Cookie]
             +----->       PANA-PAA-Discover(0,0)
       ------------>       PANA-Start-Answer(y,x)[Cookie]
                           (continued to authentication phase)

In this example, both PaC and PAA tries to initiate discovery in which
case the race condition is likely to happen.


> 
> Is it part of the core state machine of PANA that the PaC OR the PAA can
> start the process? I like the idea about how the EP can notify the PAA that
> a potential PaC is trying to use the network prior to authentication. Would
> this be the only scenario where the PAA initiates a PANA session?

Yes.  And there is such a requirement in
draft-ietf-pana-requirements-08.txt.

BTW, I am writing up a new I-D on PANA state machines.  That document
could help you understand PANA protocol behavior in detail.

> 
> ---------
> 
> Regarding the overall security (integrity, possible confidentiality)
> discussed in the draft (as well as in the PANA-IPSEC doc), I know that
> integrity and confidentiality is a nice feature to offer,  but it only
> encompasses a subset of the links that the traffic has to traverse. At the
> application level, the endpoints of the application have knowledge of the
> potential security requirements for the traffic that the protocol will
> generate. If the application mandates security and confidentiality, then the
> application will establish an "end-to-end" SA, utilizing possibly both
> confidentiality and encryption.  If the application/service endpoint is
> co-resident with the PaC functionality, I'm concerned about the overhead
> involved in having duplicate, layered SAs established.  I think this concern
> is restricted primarily to the confidentiality aspects of data traffic, and
> not necessarily integrity checking.

I know your concern as you made the same comment on the PANA framework
draft.  

Since IPsec is flexible enough to allow establishing an IPsec SA with
null encryption, it is possible to avoid double encyption (i.e., one
at application level the other between PaC and EP) if you use L3
per-packet ciphers in the access network.  Anyway, I think PANA
specification is not the right place to address this.

> 
> NAP or ISP authentication credentials should probably be protected during
> the PANA establishment phase, but this only happens during the
> initialization of the session.  If I'm deploying an application that
> requires confidentiality, I would probably not want to rely on layer-2 or
> layer-3 mechanisms to guarantee conifdentiality. It's difficult for me to
> see a scenario where a NAP would mandate confidentiality on a link. Nor a
> traditional ISP. However, in an earlier comment, I suggested emphasizing the
> fact that PANA could be used in an ASP environment as well, where the
> "service provider selection" mechanism would select and create a network
> between the PaC and an ASP. In this case, it's an "Application" Service
> Provider, and the path between the PaC and ASP might require
> confidentiality.

The same comment as above.

> 
> I feel like I'm rambling a bit here, but I think there's a point regarding
> the applicability of a heavyweight SA that implements both confidentiality
> and integrity for the link between the PaC and the PAA.
> 
> Without the discussion of IPSEC and complex SA mechanisms in the PANA
> document set, the protocol seems much easier to grasp and understand (and
> potentially implement, depending upon your point of view). In my experience,
> carriers and network folk are drawn to simplicity. If you're open to this
> idea, I think a quick and straightforward way to approach this would be to
> isolate anything regarding confidentiality and complex SA establishment to a
> document or documents external to the base PANA protocol specification.
> You've got the basic AVP extensibility mechanisms anyway, so it's a short
> walk for someone to use this method. You've already got the specifics
> regarding EAP mechanisms outside the docs which is a good way to approach
> this.

I think specifics regarding not only EAP mechanisms but also IPsec are
already separated from the PANA specification draft.  I believe the
current draft has the structure that allows a quick and
straightforward way to approach this and I guess you are not proposing
some addtional text for the PANA specification draft on this.

> 
> Overall, I understand the perceived need to potentially offer
> confidentiality over network links that are "shared" at the edge, but I
> believe that in most cases, it will be redundantly applied to protect
> application information. I may be over-reacting a bit here, and it's not a
> big deal for me, I just have had to make this balance before in complexity
> and layering. Splitting off confidentiality from anything that might
> resemble the "core" of PANA is the right way to go (and you've already done
> this with the separate IPSEC draft). Because of the need to secure the PANA
> session itself with respect to filtering at the EP, you have already bought
> the requirement for session-tagging with integrity, so again, this is mainly
> a confidentiality thing I'm talking about.

The same comment as above.

> 
> I was curious if the IESG or anyone else has commented on these particular
> security aspects of PANA work?

This was once discussed in the context of pana-ipsec draft.

Best regards,

Yoshihiro Ohba


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

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul  8 22:51:48 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10258
	for <pana-archive@lists.ietf.org>; Thu, 8 Jul 2004 22:51:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bil3i-0005a4-Bi; Thu, 08 Jul 2004 22:24:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bik5e-0006Cn-PB
	for pana@megatron.ietf.org; Thu, 08 Jul 2004 21:22:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20358
	for <pana@ietf.org>; Thu, 8 Jul 2004 21:22:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bik5Y-00000m-3E
	for pana@ietf.org; Thu, 08 Jul 2004 21:22:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bik4R-0007Mb-00
	for pana@ietf.org; Thu, 08 Jul 2004 21:21:00 -0400
Received: from omr2.netsolmail.com ([216.168.230.163])
	by ietf-mx with esmtp (Exim 4.12) id 1Bik3W-0006z3-00
	for pana@ietf.org; Thu, 08 Jul 2004 21:20:02 -0400
Received: from ms4.netsolmail.com (IDENT:mirapoint@[216.168.230.177])
	by omr2.netsolmail.com (8.12.10/8.12.10) with ESMTP id i691JF6g029520; 
	Thu, 8 Jul 2004 21:19:15 -0400 (EDT)
Received: from [10.13.3.22] (fw-1.peerless.com [208.152.94.2])
	by ms4.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id BRI72092; Thu, 8 Jul 2004 21:20:02 -0400 (EDT)
User-Agent: Microsoft-Entourage/11.0.0.040405
Date: Thu, 08 Jul 2004 18:19:58 -0700
Subject: Re: [Pana] Comments on draft-ietf-pana-pana-04
From: Randy Turner <rturner@amalfisystems.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Message-ID: <BD1340CE.119A%rturner@amalfisystems.com>
In-Reply-To: <20040708234130.GF12291@steelhead>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit



Hi,

The DSL Forum is establishing a model for the access scenario that I
mentioned in my earlier email, which is the single NAP authentication, and
possibly multiple service provider PANA sessions. Also, this will definitely
happen in the FTTP broadband multi-service environment as well. An existence
proof already exists for multi-homing of IP services into broadband CPE
through multiple FTTP service trials that are currently being operated by
SBC, Verizon, etc.

I think we should put more thought into adapting PANA for this scenario, if
it is currently not supported.

If you guys are going to be at the IETF meeting in San Diego, maybe we can
get together and discuss this; I have some ideas on how this might operate.

Randy


> From: Yoshihiro Ohba <yohba@tari.toshiba.com>
> Date: Thu, 08 Jul 2004 19:41:30 -0400
> To: Randy Turner <rturner@amalfisystems.com>
> Cc: <pana@ietf.org>
> Subject: Re: [Pana] Comments on draft-ietf-pana-pana-04
> 
> Hello Randy Turner,
> 
> Thank you (again) for sending detailed comments.
> 
> Please see my comments below.
> 
> On Tue, Jul 06, 2004 at 11:11:41PM -0700, Randy Turner wrote:
>> 
>> Hi Alper, and the list,
>> 
>> I'm working my through the drafts as I get a moment (mainly on flights ;).
>> Here are some other comments on draft-ietf-pana-pana-04...more to follow.
>> 
>> I will try and hit the list with some final comments by this weekend.
>> 
>> Regards,
>> Randy
>> (will this group be meeting in San Diego?)
>> 
>> 
>> 
>> draft-ietf-pana-pana-04 comments
>> =========================================
>> 
>> 
>> The document mentions that PANA assumes that the PAA is one hop away from
>> the PaC. Is this a requirement on the topology, or could the scope of the
>> multicast be wider than this?
> 
> This is a requirement on the topology, as described in Section 4.5.3
> of draft-ietf-pana-requirements-08.txt.
> 
>> 
>> -------
>> 
>> In Section 4.7, Device ID Choice, the text says that "the ID can be an IP
>> address, a MAC address, or an identifier that is not carried on data packets
>> but has local significance." Maybe it's my years of doing standards, but I
>> think maybe you should stipulate that the device ID MUST NOT have temporal
>> characteristics. You're requiring that the PaC have an IP address prior to
>> PANA, which means that this address (in IPv4) will probably be a temporary
>> address (auto-configured somehow), and this would probably be especially
>> true in an IPv6 environment. Likewise, MAC addresses might have local
>> persistence that is more persistent than an IP address, but it could still
>> change.  I think that the device ID should reference an agreed upon value
>> between NAP or ISP and the PaC. The namespace might vary between ISP or NAP
>> but I think (if I were you) I would emphasize the non-transient nature of
>> the device ID. It's really what the authentication is all about so it's
>> important that this be solid. In the framework document, I think you mention
>> the use of network access identifiers (NAIs), which would be ideal for the
>> NAP case, but also something similar could be used for service provider
>> authentication as well.
> 
> I am not sure whether you are talking about device identifier or
> session identifier or both, but in PANA, device identifier is
> changeable.  In the next revision, we will have
> PANA-Address-Update-Request/Answer messsages to update device ID as
> well as POPA (you can check the latest snapshot in
> http://www.toshiba.com/tari/pana/pana-spec.html.)  Since device
> identifier is defined as a changeable parameter, we defined session
> identifier as a stable identifier (except for the case of mobility
> handling described in section 4.9 where session identifier changes
> after handoff.)
> 
>> Correct me if I'm wrong, but to the PANA-aware nodes
>> in the network, the device-ID is an opaque series of bytes of some length.
>> Is this correct?
> 
> In PANA, device identifier have a Diameter Address type which is
> derived from Diameter OctetString type.  PANA session identifier has
> the same structure as Diameter Session-Id AVP.
> 
>> 
>> By the way, I'm assuming that it's possible for multiple PANA sessions to be
>> in progress at the same time. Probably one session for the NAP, and possibly
>> <N> number of service provider sessions.  Which brings me to another point
>> about the protocol document, and I believe the framework document.
>> Throughout these documents you've isolated the dominant  model of network
>> connectivity today: someone wants to get access to the global internet.  But
>> looking ahead, the use of PANA could be expanded to ISP, ASP, whatever. I
>> think it's important for the audience of PANA to understand that this is not
>> just an "ISP connectivity" method, but could be reused, as could the
>> topological infrastructure, for a number of different business models.
> 
> This is an interesting scenario, but I think there is some significant
> issues related to having <N> number of global IP addresses assigned by
> <N> service providers, namely, source address selection issue and
> multi-homing issue.  It is probably not a good idea to allow <N>
> number of service provider sessions in PANA until those issues are
> fully studied.
> 
> 
>> 
>> --------
>> 
>> I may have missed it, but it wasn't clear to me that the PaC state machine
>> could receive an unsolicited PANA-Start-Request until Figure 3 (just prior
>> to 4.3).  It might have been inferred in the discussion about race
>> conditions when a PANA-PAA-Discover message and a PANA-Start-Request message
>> are sent at the same time, but I was thinking this condition would only
>> occur if the PaC retransmitted the "discover" message quicker than the PAA
>> could respond. 
> 
> I think Figures 2 and 3 are not good example to show the race
> condition because in the examples both either PaC or PAA is the
> initiator of the discovery and initial handshake phase.
> 
>       PaC   EP      PAA    Message
>       ------------------------------------------------------
>        ---->o              (DHCP traffic triggers discovery at PAA
>              ------>        via PAA-to-EP protocol)
>        ------+
>        <-----|------       PANA-Start-Request(x,0)[Cookie]
>              +----->       PANA-PAA-Discover(0,0)
>        ------------>       PANA-Start-Answer(y,x)[Cookie]
>                            (continued to authentication phase)
> 
> In this example, both PaC and PAA tries to initiate discovery in which
> case the race condition is likely to happen.
> 
> 
>> 
>> Is it part of the core state machine of PANA that the PaC OR the PAA can
>> start the process? I like the idea about how the EP can notify the PAA that
>> a potential PaC is trying to use the network prior to authentication. Would
>> this be the only scenario where the PAA initiates a PANA session?
> 
> Yes.  And there is such a requirement in
> draft-ietf-pana-requirements-08.txt.
> 
> BTW, I am writing up a new I-D on PANA state machines.  That document
> could help you understand PANA protocol behavior in detail.
> 
>> 
>> ---------
>> 
>> Regarding the overall security (integrity, possible confidentiality)
>> discussed in the draft (as well as in the PANA-IPSEC doc), I know that
>> integrity and confidentiality is a nice feature to offer,  but it only
>> encompasses a subset of the links that the traffic has to traverse. At the
>> application level, the endpoints of the application have knowledge of the
>> potential security requirements for the traffic that the protocol will
>> generate. If the application mandates security and confidentiality, then the
>> application will establish an "end-to-end" SA, utilizing possibly both
>> confidentiality and encryption.  If the application/service endpoint is
>> co-resident with the PaC functionality, I'm concerned about the overhead
>> involved in having duplicate, layered SAs established.  I think this concern
>> is restricted primarily to the confidentiality aspects of data traffic, and
>> not necessarily integrity checking.
> 
> I know your concern as you made the same comment on the PANA framework
> draft.  
> 
> Since IPsec is flexible enough to allow establishing an IPsec SA with
> null encryption, it is possible to avoid double encyption (i.e., one
> at application level the other between PaC and EP) if you use L3
> per-packet ciphers in the access network.  Anyway, I think PANA
> specification is not the right place to address this.
> 
>> 
>> NAP or ISP authentication credentials should probably be protected during
>> the PANA establishment phase, but this only happens during the
>> initialization of the session.  If I'm deploying an application that
>> requires confidentiality, I would probably not want to rely on layer-2 or
>> layer-3 mechanisms to guarantee conifdentiality. It's difficult for me to
>> see a scenario where a NAP would mandate confidentiality on a link. Nor a
>> traditional ISP. However, in an earlier comment, I suggested emphasizing the
>> fact that PANA could be used in an ASP environment as well, where the
>> "service provider selection" mechanism would select and create a network
>> between the PaC and an ASP. In this case, it's an "Application" Service
>> Provider, and the path between the PaC and ASP might require
>> confidentiality.
> 
> The same comment as above.
> 
>> 
>> I feel like I'm rambling a bit here, but I think there's a point regarding
>> the applicability of a heavyweight SA that implements both confidentiality
>> and integrity for the link between the PaC and the PAA.
>> 
>> Without the discussion of IPSEC and complex SA mechanisms in the PANA
>> document set, the protocol seems much easier to grasp and understand (and
>> potentially implement, depending upon your point of view). In my experience,
>> carriers and network folk are drawn to simplicity. If you're open to this
>> idea, I think a quick and straightforward way to approach this would be to
>> isolate anything regarding confidentiality and complex SA establishment to a
>> document or documents external to the base PANA protocol specification.
>> You've got the basic AVP extensibility mechanisms anyway, so it's a short
>> walk for someone to use this method. You've already got the specifics
>> regarding EAP mechanisms outside the docs which is a good way to approach
>> this.
> 
> I think specifics regarding not only EAP mechanisms but also IPsec are
> already separated from the PANA specification draft.  I believe the
> current draft has the structure that allows a quick and
> straightforward way to approach this and I guess you are not proposing
> some addtional text for the PANA specification draft on this.
> 
>> 
>> Overall, I understand the perceived need to potentially offer
>> confidentiality over network links that are "shared" at the edge, but I
>> believe that in most cases, it will be redundantly applied to protect
>> application information. I may be over-reacting a bit here, and it's not a
>> big deal for me, I just have had to make this balance before in complexity
>> and layering. Splitting off confidentiality from anything that might
>> resemble the "core" of PANA is the right way to go (and you've already done
>> this with the separate IPSEC draft). Because of the need to secure the PANA
>> session itself with respect to filtering at the EP, you have already bought
>> the requirement for session-tagging with integrity, so again, this is mainly
>> a confidentiality thing I'm talking about.
> 
> The same comment as above.
> 
>> 
>> I was curious if the IESG or anyone else has commented on these particular
>> security aspects of PANA work?
> 
> This was once discussed in the context of pana-ipsec draft.
> 
> Best regards,
> 
> Yoshihiro Ohba
> 
> 
>> ----------
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Pana mailing list
>> Pana@ietf.org
>> https://www1.ietf.org/mailman/listinfo/pana



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul  9 05:09:46 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12520
	for <pana-archive@lists.ietf.org>; Fri, 9 Jul 2004 05:09:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Biqxh-0000Nz-Up; Fri, 09 Jul 2004 04:42:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Biqj3-0005qi-Sc
	for pana@megatron.ietf.org; Fri, 09 Jul 2004 04:27:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA11090
	for <pana@ietf.org>; Fri, 9 Jul 2004 04:27:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Biqiw-0006Gd-JO
	for pana@ietf.org; Fri, 09 Jul 2004 04:27:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Biqi4-0005y8-00
	for pana@ietf.org; Fri, 09 Jul 2004 04:26:21 -0400
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx with esmtp (Exim 4.12) id 1BiqhV-0005My-00
	for pana@ietf.org; Fri, 09 Jul 2004 04:25:47 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I0K0007HSE3I0@dns2.cselt.it> for pana@ietf.org; Fri,
	09 Jul 2004 10:18:03 +0200 (MEST)
Received: from EXC01A.cselt.it ([163.162.4.198]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Fri, 09 Jul 2004 10:22:49 +0200
Received: from EXC2K01B.cselt.it ([163.162.4.97])
	by EXC01A.cselt.it with Microsoft SMTPSVC(6.0.3790.0); Fri,
	09 Jul 2004 10:24:55 +0200
Date: Fri, 09 Jul 2004 10:24:46 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
To: pana@ietf.org
Message-id: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Importance: normal
Priority: normal
Thread-Topic: Mobility Handling in PANA
thread-index: AcRljc1AlhQ8pUb+Qeq8nhmWk6oGtQ==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 09 Jul 2004 08:24:55.0024 (UTC)
	FILETIME=[36AC4F00:01C4658E]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_20_30,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60
Subject: [Pana] Mobility Handling in PANA
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0067496455=="
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0067496455==
Content-type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4658E.318209A5"
Content-Class: urn:content-classes:message

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4658E.318209A5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

I'd like to bring up a discussion regarding mobility handling in PANA.=20

Section 4.9 in PANA Protocol draft describes this procedure:

- PaC sends a PSA with the old session-id and a MAC AVP calculated using
the old PANA_MAC_key (shared between the PaC and the pPAA)
- nPAA retrieves the pPAA's address from the session-id=20
- nPAA provides in some way (TBD) this PSA to the pPAA.=20

A possibility stated by the dratf is the usage of CTP. The PANA draft
does not specify how CTP could be used. However, I think that in this
scenario the only way to trigger the context tansfer is that the nPAA
sends a CT-Req to the pPAA. There are two issues here: this CT-Req
message does not contain the previous IP address of the PaC and the
Authorization Token.=20

A different approach is provided in
http://www.ietf.org/internet-drafts/draft-bournelle-pana-ctp-00.txt.
This is the procedure we propose in this draft:=20

- PaC sends a PSA with a CTAR in a new PANA AVP. This PSA does not
contain any MAC AVP. The CTAR includes an authorization token calculated
with a new key (PANA-CTP-Key) and the pPAA's address.=20
- nPAA sends a CT-Req (including the authorization token and the
previous PaC's IP address carried by CTAR message)
- pPAA verifies the authorization token and (if it is correct) sends the
CTD with the PANA context
- nPAA sends a PBR with the new Session-id and a nonce to derive the new
AAA-key. This message includes a MAC AVP calculated using the new
PANA_MAC_Key
- PaC replies with a PBA

Comments?

--Gerardo




Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

------_=_NextPart_001_01C4658E.318209A5
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6487.1">
<TITLE>Mobility Handling in PANA</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Courier New">Hi all,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">I'd like to bring up a discussion =
regarding mobility handling in PANA. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Section 4.9 in PANA Protocol =
draft describes this procedure:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">- PaC sends a PSA with the old =
session-id and a MAC AVP calculated using the old PANA_MAC_key (shared =
between the PaC and the pPAA)</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">- nPAA retrieves the pPAA's =
address from the session-id </FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">- nPAA provides in some way =
(TBD) this PSA to the pPAA. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">A possibility stated by the dratf =
is the usage of CTP. The PANA draft does not specify how CTP could be =
used. However, I think that in this scenario the only way to trigger the =
context tansfer is that the nPAA sends a CT-Req to the pPAA. There are =
two issues here: this CT-Req message does not contain the previous IP =
address of the PaC and the Authorization Token. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">A different approach is provided =
in </FONT><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-bournelle-pana-ctp-00.t=
xt"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Courier =
New">http://www.ietf.org/internet-drafts/draft-bournelle-pana-ctp-00.txt<=
/FONT></U></A><FONT SIZE=3D2 FACE=3D"Courier New">. This is the =
procedure we propose in this draft: </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">- PaC sends a PSA with a CTAR in =
a new PANA AVP. This PSA does not contain any MAC AVP. The CTAR includes =
an authorization token calculated with a new key (PANA-CTP-Key) and the =
pPAA's address. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">- nPAA sends a CT-Req (including =
the authorization token and the previous PaC's IP address carried by =
CTAR message)</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">- pPAA verifies the =
authorization token and (if it is correct) sends the CTD with the PANA =
context</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">- nPAA sends a PBR with the new =
Session-id and a nonce to derive the new AAA-key. This message includes =
a MAC AVP calculated using the new PANA_MAC_Key</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">- PaC replies with a PBA</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Comments?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">--Gerardo</FONT>
</P>
<BR>

<p></p><p> Gruppo Telecom Italia - Direzione e coordinamento di Telecom =
Italia =
S.p.A.<br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>=
CONFIDENTIALITY NOTICE<br>This message and its attachments are addressed =
solely to the persons<br>above and may contain confidential information. =
If you have received<br>the message in error, be informed that any use =
of the content hereof<br>is prohibited. Please return it immediately to =
the sender and delete<br>the message. Should you have any questions, =
please send an e_mail to<br> MailAdmin@tilab.com. Thank =
you<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</BODY>
</HTML>
------_=_NextPart_001_01C4658E.318209A5--


--===============0067496455==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana

--===============0067496455==--



From pana-bounces@ietf.org  Sat Jul 10 01:25:17 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09062
	for <pana-archive@lists.ietf.org>; Sat, 10 Jul 2004 01:25:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BjAIr-0001ri-GH; Sat, 10 Jul 2004 01:21:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjA1N-0007kb-Qv
	for pana@megatron.ietf.org; Sat, 10 Jul 2004 01:03:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08242
	for <pana@ietf.org>; Sat, 10 Jul 2004 01:03:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjA1L-0002jj-N1
	for pana@ietf.org; Sat, 10 Jul 2004 01:03:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bj9yu-0002Ce-00
	for pana@ietf.org; Sat, 10 Jul 2004 01:01:01 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bj9xv-0001nX-00
	for pana@ietf.org; Sat, 10 Jul 2004 00:59:59 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6A4xwpD018013;
	Sat, 10 Jul 2004 13:59:58 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6A4xwYv019629;
	Sat, 10 Jul 2004 13:59:58 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	PAA19622 ; Sat, 10 Jul 2004 13:59:58 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id NAA16119; Sat, 10 Jul 2004 13:59:57 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id NAA01698;
	Sat, 10 Jul 2004 13:59:57 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6A4xupl016585;
	Sat, 10 Jul 2004 13:59:56 +0900 (JST)
Received: from steelhead (iVPN01-094.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0M00JZTDVV1A@tsbpo1.po.toshiba.co.jp>; Sat,
	10 Jul 2004 13:59:56 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bj9xR-0000li-00; Fri, 09 Jul 2004 21:59:29 -0700
Date: Sat, 10 Jul 2004 00:59:24 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040710045924.GA1305@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [Pana] PANA specification and framework snaps
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

The latest snapshots of PANA specification (05c) and PANA framework
(01c) are available at
http://www.toshiba.com/tari/pana/pana-spec.html.

1. PANA specication (draft-ietf-pana-pana-05c.txt)

Updates: Incoporated proposed text for Issues 98, 99, 100 as well as
editorial work by Hannes and AAA-Key revised definition by Alper.

Remaining issues : 94 and 95 (both on Section 9, waiting for revised
text from Alper and Hannes).

2. PANA framework (draft-ietf-pana-framework-01c.txt)

Updates: Reflected Randy Turner's comments.

Remaining issues : NONE (is it OK to submit?).

Best regards,

Yoshihiro Ohba

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Sat Jul 10 02:37:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25522
	for <pana-archive@lists.ietf.org>; Sat, 10 Jul 2004 02:37:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BjBPT-0003Wb-NX; Sat, 10 Jul 2004 02:32:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjBNB-00031m-L8
	for pana@megatron.ietf.org; Sat, 10 Jul 2004 02:30:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25251
	for <pana@ietf.org>; Sat, 10 Jul 2004 02:30:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjBN9-0000aC-3e
	for pana@ietf.org; Sat, 10 Jul 2004 02:30:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjBM8-0000C2-00
	for pana@ietf.org; Sat, 10 Jul 2004 02:29:05 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BjBLI-0007fz-00
	for pana@ietf.org; Sat, 10 Jul 2004 02:28:12 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6A6SApD014449;
	Sat, 10 Jul 2004 15:28:10 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6A6SAv8019081;
	Sat, 10 Jul 2004 15:28:10 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	RAA19080 ; Sat, 10 Jul 2004 15:28:10 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id PAA08910; Sat, 10 Jul 2004 15:28:09 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id PAA09814;
	Sat, 10 Jul 2004 15:28:09 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6A6S8pl017416;
	Sat, 10 Jul 2004 15:28:08 +0900 (JST)
Received: from steelhead (iVPN01-094.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0M000FTHYVXI@tsbpo1.po.toshiba.co.jp>; Sat,
	10 Jul 2004 15:28:08 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BjBKk-00017N-00; Fri, 09 Jul 2004 23:27:38 -0700
Date: Sat, 10 Jul 2004 02:27:38 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Mobility Handling in PANA
In-reply-to: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Message-id: <20040710062738.GD893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Gerardo,

I have a couple of comments on draft-bournelle-pana-ctp-00.txt.

[1] In predictive mode of the proposed scheme, is a CTAR message carried
in a PANA message sent from a PaC to pPAA?  If so, which PANA message
is used and how?  

[2] I think it is also possible to run the MN-AR context transfer
protocol to carry CTAR messages between MN and nPAA (or pPAA) instead
of piggybacking CTAR messages in PANA messages.  For example something
like this in the case of non-predictive mode:

   PaC           nPAA              pPAA
   ----------------------------------------
         CTAR 
   --------------->       CT-Request 
                        ------------>
                             CTD 
                        <------------

         PSR
   <---------------
    PSA[old Session-ID, Nonce]   // MAC AVP is not needed.
    --------------->
    PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
   <-------------
    PBA[new Session-ID, Key-Id, PPAC, MAC]
    ------------->

This has half round-trip redundancy compared to your proposal (due to
non-piggybacking CTAR), but provides better modularity between PANA
and Context Transfer Protocol.  Also this works with both
non-predictive and predictive modes.

[3] In CTD-PANA message, I think ISN-pac, ISN-paa, tseq and rseq do
not have to be defined in CTD-PANA, because sequence number contexts
are not inherited from the pPAA (i.e., new sequence number context is
established in the PSR-PBA exchange between PaC and nPAA).  Also, I
think retransmission interval does not need to be defined in CTD-PANA,
since retransmission interval can be locally determined parameter.

Regards,

Yoshihiro Ohba



On Fri, Jul 09, 2004 at 10:24:46AM +0200, Giaretta Gerardo wrote:
> Hi all,
> 
> I'd like to bring up a discussion regarding mobility handling in PANA. 
> 
> Section 4.9 in PANA Protocol draft describes this procedure:
> 
> - PaC sends a PSA with the old session-id and a MAC AVP calculated using
> the old PANA_MAC_key (shared between the PaC and the pPAA)
> - nPAA retrieves the pPAA's address from the session-id 
> - nPAA provides in some way (TBD) this PSA to the pPAA. 
> 
> A possibility stated by the dratf is the usage of CTP. The PANA draft
> does not specify how CTP could be used. However, I think that in this
> scenario the only way to trigger the context tansfer is that the nPAA
> sends a CT-Req to the pPAA. There are two issues here: this CT-Req
> message does not contain the previous IP address of the PaC and the
> Authorization Token. 
> 
> A different approach is provided in
> http://www.ietf.org/internet-drafts/draft-bournelle-pana-ctp-00.txt.
> This is the procedure we propose in this draft: 
> 
> - PaC sends a PSA with a CTAR in a new PANA AVP. This PSA does not
> contain any MAC AVP. The CTAR includes an authorization token calculated
> with a new key (PANA-CTP-Key) and the pPAA's address. 
> - nPAA sends a CT-Req (including the authorization token and the
> previous PaC's IP address carried by CTAR message)
> - pPAA verifies the authorization token and (if it is correct) sends the
> CTD with the PANA context
> - nPAA sends a PBR with the new Session-id and a nonce to derive the new
> AAA-key. This message includes a MAC AVP calculated using the new
> PANA_MAC_Key
> - PaC replies with a PBA
> 
> Comments?
> 
> --Gerardo
> 
> 
> 
> 
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
> 
> ====================================================================
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to
> MailAdmin@tilab.com. Thank you
> ====================================================================

> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Sat Jul 10 07:29:09 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07803
	for <pana-archive@lists.ietf.org>; Sat, 10 Jul 2004 07:29:09 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BjG0w-0005Oa-BJ; Sat, 10 Jul 2004 07:27:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjFzp-0005D5-S3
	for pana@megatron.ietf.org; Sat, 10 Jul 2004 07:26:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07660
	for <pana@ietf.org>; Sat, 10 Jul 2004 07:26:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjFzp-0002Au-B8
	for pana@ietf.org; Sat, 10 Jul 2004 07:26:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjFyn-0001qF-00
	for pana@ietf.org; Sat, 10 Jul 2004 07:25:17 -0400
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx with esmtp (Exim 4.12) id 1BjFxm-0001Ql-00
	for pana@ietf.org; Sat, 10 Jul 2004 07:24:14 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by goliath.siemens.de (8.12.6/8.12.6) with ESMTP id i6ABODNq016987;
	Sat, 10 Jul 2004 13:24:13 +0200
Received: from hannes (cert-mchp1-5.esn.sbs.de [139.25.62.5])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id i6ABOCn24135;
	Sat, 10 Jul 2004 13:24:12 +0200 (MEST)
Message-Id: <200407101124.i6ABOCn24135@mail1.siemens.de>
From: "Hannes Tschofenig" <Hannes.Tschofenig@siemens.com>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, <pana@ietf.org>
Subject: RE: [Pana] PANA specification and framework snaps
Date: Sat, 10 Jul 2004 13:24:12 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1409
Thread-Index: AcRmPkl6PccL5qBUTwKpXK5EtUfcygAMTbDg
In-Reply-To: <20040710045924.GA1305@steelhead>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit

hi yoshi, 

i have read the framework document and included some comments. most of them
are editorial. 
my feedback: this is a good and useful document. 

please find my comments at:
http://www.tschofenig.com/TEMP/draft-ietf-pana-framework-00-hannes.txt

ciao
hannes

ps: i haven't finished the entire document. hopefully i get the rest done
during the next week.

> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com] 
> Sent: Samstag, 10. Juli 2004 06:59
> To: pana@ietf.org
> Subject: [Pana] PANA specification and framework snaps
> 
> The latest snapshots of PANA specification (05c) and PANA framework
> (01c) are available at
> http://www.toshiba.com/tari/pana/pana-spec.html.
> 
> 1. PANA specication (draft-ietf-pana-pana-05c.txt)
> 
> Updates: Incoporated proposed text for Issues 98, 99, 100 as 
> well as editorial work by Hannes and AAA-Key revised 
> definition by Alper.
> 
> Remaining issues : 94 and 95 (both on Section 9, waiting for 
> revised text from Alper and Hannes).
> 
> 2. PANA framework (draft-ietf-pana-framework-01c.txt)
> 
> Updates: Reflected Randy Turner's comments.
> 
> Remaining issues : NONE (is it OK to submit?).
> 
> Best regards,
> 
> Yoshihiro Ohba
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Sun Jul 11 11:10:13 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25996
	for <pana-archive@lists.ietf.org>; Sun, 11 Jul 2004 11:10:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bjfos-0007qv-Sz; Sun, 11 Jul 2004 11:00:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bjfld-0007GX-St
	for pana@megatron.ietf.org; Sun, 11 Jul 2004 10:57:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25643
	for <pana@ietf.org>; Sun, 11 Jul 2004 10:57:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bjflc-0002SM-UH
	for pana@ietf.org; Sun, 11 Jul 2004 10:57:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bjfke-0002I4-00
	for pana@ietf.org; Sun, 11 Jul 2004 10:56:26 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BjfkQ-00028O-00
	for pana@ietf.org; Sun, 11 Jul 2004 10:56:10 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6BEu8pD015118;
	Sun, 11 Jul 2004 23:56:08 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6BEu8KF026536;
	Sun, 11 Jul 2004 23:56:08 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	ZAA26533 ; Sun, 11 Jul 2004 23:56:08 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id XAA12146; Sun, 11 Jul 2004 23:56:07 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id XAA03374;
	Sun, 11 Jul 2004 23:56:06 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6BEu6pl002529;
	Sun, 11 Jul 2004 23:56:06 +0900 (JST)
Received: from steelhead (iVPN01-182.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0P0059605GJE@tsbpo1.po.toshiba.co.jp>; Sun,
	11 Jul 2004 23:56:05 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BjfjS-0006va-00; Sun, 11 Jul 2004 07:55:10 -0700
Date: Sun, 11 Jul 2004 10:55:10 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] PANA specification and framework snaps
In-reply-to: <200407101124.i6ABOCn24135@mail1.siemens.de>
To: Hannes Tschofenig <Hannes.Tschofenig@siemens.com>
Message-id: <20040711145510.GM893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Hannes Tschofenig <Hannes.Tschofenig@siemens.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040710045924.GA1305@steelhead>
	<200407101124.i6ABOCn24135@mail1.siemens.de>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Hannes,

Thanks for your comments.  Your comments are reflected to a new
snapshot 00d at http://www.toshiba.com/tari/pana/pana-spec.html.  
I have some comments below (tagged with [ohba]).

-------------------------------------------------------------
In section 5,

(snip)

      If the PaC is a dual-stack host, it can configure both IPv4 and
      IPv6 type POPAs.



      PRPA and the IP address of PAA are assumed to be on the same IP
      subnet, hence the PaC and PAA can perform on-link communication as
      required by PANA.

[hannes] there is no such assumption in pana. 

[ohba] The entire paragraph is revised as:

"
      The PaC with a PRPA and the PAA with IP address X can perform
      on-link communication as required by PANA.  In IPv4, the PRPA and
      IP address X have the same on-link prefix.  In IPv6, the two
      addresses are link-local addresses.  When the PaC replaces its
      IPv4 PRPA with an IPv4 POPA, the PaC and PAA SHOULD create host
      routes to each other, as they do not share the same on-link prefix
      any more.  This is needed for the PaC with the IPv4 POPA and the
      PAA with IP address X to continue on-link communication.  In this
      case, the PaC SHOULD create a host route to IP address X, and the
      PAA SHOULD create a host route to the IPv4 POPA.  PANA defines a
      mechanism for the PaC to report the POPA to the PAA.
"

Does this work for you?

In Section 6,

   Network-layer ciphering, i.e., IPsec, can be used when data traffic
   protection is required but link-layer ciphering capability is not
   available.

[hannes] change to 
"
   Network-layer protection, i.e., IPsec, can be used when data traffic
   protection is required but link-layer protection is not
   available. Providing security at the network-layer allows to terminate security protection 
   deeper in the network.
"

[ohba] The last sentence in your suggested text seems to contradict
with "it is important to place the EP as close to the edge of the
network as possible."  So I would prefer not including the last sentence.

(snip)

  The details of such a mechanism is outside the
   scope of PANA protocol and is specified in [I-D.ietf-pana-ipsec].
   PANA provides bootstrapping functionality for such a mechanism by
   carrying EAP methods that can generate initial keying material.

   Using network-layer ciphers should be regarded as a substitute for
   link-layer ciphers when the latter is not available. Network-layer
   ciphering can also be used in addition to link-layer ciphering if the
   added benefits outweigh its cost to the user and the network.
  In
   this case, PANA bootstraps only the network-layer ciphering and
   link-layer is protected using any of the existing link-layer specific
   methods.


[hannes] the last paragraph is a repetition. 

[ohba]  Repetition of which text?  

In Section 7,

7. PAA-EP Protocol

   The PANA protocol provides client authentication and authorization
   functionality for securing network access.  The other component of a
   complete solution is the access control which ensures that only
   authenticated and authorized clients can gain access to the network.
   PANA enables access control by identifying legitimate clients and
   generating filtering information for access control mechanisms.

[hannes] "identifying legitimate clients" - what does that mean? 

[ohba] changed to "distinguishing authenticated and authorized clients
from others"

(snip)

7.1.1 Single PAA, Single EP, Co-located

   This model corresponds to the legacy NAS model.  Since the PAA and
   the EP are co-located, the PAA-EP communication can be implemented
   locally by using, e.g., IPC (Inter-Process Communication).  The only
   difference from the legacy NAS model is the case where there are
   multiple co-located PAA/EP devices on the same IP link and the PAA/EP
   devices are L2 switches or access points.

[hannes] the paa/ep cannot be a l2 switch in this model - only an access point. 

[ohba]  Why?

  In this case, for a PaC
   that attaches to a given PAA/EP device, other PAA/EP devices should
   not be visible to the PaC even if those devices are on the same IP
   link.

[hannes] what does it mean 'not be visible'?

[ohba] changed to "In this case, for a PaC that attaches to a given
PAA/EP device, other PAA/EP devices should not be discovered by the
PaC even if those devices are on the same IP link."

  Otherwise, the PaC may result in finding a PAA that is not the
   closest one to it during the PANA discovery and initial handshake
   phase and performing PANA with the wrong PAA.

[hannes] this issue might deserve a more detailed description.

[ohba] Changed to:

"
   Otherwise, the PaC may result in finding a PAA that is not the
   closest one to it during the PANA discovery and initial handshake
   phase and performing PANA with the PAA, which does not correspond
   to the legacy NAS model.
"

  To prevent this, each
   PAA/EP device on an L2 switch or access point should not forward
   multicast PANA discovery message sent by PaCs attached to it to other
   devices.

[hannes] is this really the solution? 

[ohba] I believe so, based on the legacy NAS model in which only one
authentication agent is discovered by a client.  If the client
discoveres a PAA a PAA that is not the closest one to it, then such a
case belongs to "Multiple PAAs" model instead of "Single PAA, Single
EP, Co-located".

7.1.2 Separate PAA and EP

   When PAA is separated from EP, two cases are possible with regard to
   whether PAA and EP are located in parallel or serial when viewed from
   PaC, for each of models described in this section.

   In the first case, PAA is located behind EP.  The EP should be
   configured to always pass through PANA messages and address
   configuration protocol messages used for configuring an IP address
   used for initial PANA messaging. This case can typically happen when
   the EP is an L2 switch or an access point (the EP also has an IP
   stack to communicate with PAA via a PAA-EP protocol).

[hannes] if the ep is an access point and the paa is "behind" the ep then it has to be an router. 
since pana has this one-hop away principle. 

[ohba] I think there is some misunderstanding here.  The access point
EP does not have to be a router under the one-hop away principle.
Specifically, there is an explicit text in the PANA requirement draft:

"
   The PAA and PaC MUST be exactly one IP hop away from each other.
   That is, there must be no IP routers between the two.  Note that this
   does not mean they are on the same physical link.  Bridging
   techniques can place two nodes just exactly one IP hop away from each
   other although they might be connected to separate physical links.  
"



             +---+        +---+        +---+
             |PaC|--------|EP |--------|PAA|
             +---+        +---+\       +---+
                                \
                                 +---- Internet


                     Figure 3: PAA and EP in Serial

(snip)

7.3 Filter Rule Installation

   Filtering rules to be installed on EP generally include a device
   identifier of PaC, and also cryptographic keying material (such as
   keys, key pairs, and initialization values) when needed.

[hannes] what is the difference between keys and key pairs? btw, ivs are most likely not installed since they are negotiated - at least in ike 

  The keying
   material is needed when attackers can eavesdrop and spoof on the
   device identifiers easily.  Each keying material is uniquely
   identified with a keying material name

[hannes] what is the 'keying material name'?  we had a long discussion on this issue in the pana wg. 

 and has a lifetime for key
   management purpose.

[hannes] not only for management purposes - it is for accounting, charging, access control & security reasons in general. 
the lifetime is an important issue here. 


  The keying material is used with link-layer or
   network-layer ciphering to provide additional protection. For issues
   regarding data-origin authentication see Section 6. 

[hannes] these issues should go into section 6 and not repeated here. 

[ohba] According to your comments on the first paragraph of section 7.1,
the paragraph is revised to:

" 

   Filtering rules to be installed on EP generally include a device
   identifier of PaC, and also cryptographic keying material (e.g., IKE
   pre-shared key [RFC2409]) when cryptographic data traffic protection
   is needed (See Section 6).  Each keying material is uniquely
   identified with a keying material name (e.g., ID_KEY_ID in IKE
   [RFC2409]) and has a lifetime for key management, accounting, access
   control and security reasons in general.  In addition to the device
   identifier and keying material, other filter rules, such as the IP
   filter rules specified in NAS-Filter-Rule AVPs carried in Diameter
   EAP application [I-D.ietf-aaa-eap] may be installed on EP.

"

Yoshihiro Ohba

On Sat, Jul 10, 2004 at 01:24:12PM +0200, Hannes Tschofenig wrote:
> hi yoshi, 
> 
> i have read the framework document and included some comments. most of them
> are editorial. 
> my feedback: this is a good and useful document. 
> 
> please find my comments at:
> http://www.tschofenig.com/TEMP/draft-ietf-pana-framework-00-hannes.txt
> 
> ciao
> hannes
> 
> ps: i haven't finished the entire document. hopefully i get the rest done
> during the next week.
> 
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com] 
> > Sent: Samstag, 10. Juli 2004 06:59
> > To: pana@ietf.org
> > Subject: [Pana] PANA specification and framework snaps
> > 
> > The latest snapshots of PANA specification (05c) and PANA framework
> > (01c) are available at
> > http://www.toshiba.com/tari/pana/pana-spec.html.
> > 
> > 1. PANA specication (draft-ietf-pana-pana-05c.txt)
> > 
> > Updates: Incoporated proposed text for Issues 98, 99, 100 as 
> > well as editorial work by Hannes and AAA-Key revised 
> > definition by Alper.
> > 
> > Remaining issues : 94 and 95 (both on Section 9, waiting for 
> > revised text from Alper and Hannes).
> > 
> > 2. PANA framework (draft-ietf-pana-framework-01c.txt)
> > 
> > Updates: Reflected Randy Turner's comments.
> > 
> > Remaining issues : NONE (is it OK to submit?).
> > 
> > Best regards,
> > 
> > Yoshihiro Ohba
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> > 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Sun Jul 11 20:19:47 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20849
	for <pana-archive@lists.ietf.org>; Sun, 11 Jul 2004 20:19:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BjoWH-0000ri-ST; Sun, 11 Jul 2004 20:18:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjoTB-0000ZL-Of
	for pana@megatron.ietf.org; Sun, 11 Jul 2004 20:14:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20712
	for <pana@ietf.org>; Sun, 11 Jul 2004 20:14:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjoTA-00014R-1r
	for pana@ietf.org; Sun, 11 Jul 2004 20:14:56 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjoSC-0000uk-00
	for pana@ietf.org; Sun, 11 Jul 2004 20:13:57 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BjoRd-0000ku-00
	for pana@ietf.org; Sun, 11 Jul 2004 20:13:21 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6C0D5pD022620;
	Mon, 12 Jul 2004 09:13:05 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6C0D5AR003219;
	Mon, 12 Jul 2004 09:13:05 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	KAA03215 ; Mon, 12 Jul 2004 09:13:05 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA09425; Mon, 12 Jul 2004 09:13:04 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA11408;
	Mon, 12 Jul 2004 09:13:03 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6C0D3pl021269;
	Mon, 12 Jul 2004 09:13:03 +0900 (JST)
Received: from steelhead (iVPN01-121.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0P00620PXP20@tsbpo1.po.toshiba.co.jp>; Mon,
	12 Jul 2004 09:13:02 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BjoQG-00082G-00; Sun, 11 Jul 2004 17:11:56 -0700
Date: Sun, 11 Jul 2004 20:11:56 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Mobility Handling in PANA
In-reply-to: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Message-id: <20040712001155.GQ893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Gerardo,

Another comment on draft-bournelle-pana-ctp-00.txt:

I am not sure how EAP-based re-authentication can work after the PaC
has successfully established a new PANA session with nPAA based on the
mobility optimization operation, especially with NAP and ISP separated
authentications.  Since PSR-PSA exchange is omitted in the case of
EAP-based re-authentication, there is no means to negotiate on NAP and
ISP separate authentications between the PaC and nPAA.  Do you have
any thoughts on this?

BTW, in my previous comment [2], A MAC AVP was needed in PSA in the
diagram.

Yoshihiro Ohba


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 06:30:41 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28209
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 06:30:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bjxyx-0003jv-De; Mon, 12 Jul 2004 06:24:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjxwF-0001BI-Kk
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 06:21:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27852
	for <pana@ietf.org>; Mon, 12 Jul 2004 06:21:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjxwC-0004y4-QT
	for pana@ietf.org; Mon, 12 Jul 2004 06:21:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjxvL-0004mn-00
	for pana@ietf.org; Mon, 12 Jul 2004 06:20:40 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx with esmtp (Exim 4.12) id 1Bjxuh-0004Ys-00
	for pana@ietf.org; Mon, 12 Jul 2004 06:19:59 -0400
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 451B32FD06;
	Mon, 12 Jul 2004 12:19:25 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1Bjxsq-000BjD-5I;
	Mon, 12 Jul 2004 12:18:04 +0200
Date: Mon, 12 Jul 2004 12:18:04 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: yohba@tari.toshiba.com, pana@ietf.org
Subject: Re: [Pana] Mobility Handling in PANA
Message-ID: <20040712101804.GF44906@ipv6-5.int-evry.fr>
References: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
	<20040710062738.GD893@steelhead>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040710062738.GD893@steelhead>
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (score=-4.9, requis 4.5, autolearn=not spam,
	BAYES_00 -4.90)
X-MailScanner-From: jb@ipv6-5.int-evry.fr
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Gerardo Giaretta <gerardo.giaretta@tilab.com>
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi yoshi,

 thanks for your comments.

 see my response inline

On Sat, Jul 10, 2004 at 02:27:38AM -0400, Yoshihiro Ohba wrote:
> 
> [1] In predictive mode of the proposed scheme, is a CTAR message carried
> in a PANA message sent from a PaC to pPAA?  If so, which PANA message
> is used and how?  

basically, we had in mind to use CTAR message as specified in CTP. In
other words, for predictive handover we do not use PANA message.

> 
> [2] I think it is also possible to run the MN-AR context transfer
> protocol to carry CTAR messages between MN and nPAA (or pPAA) instead
> of piggybacking CTAR messages in PANA messages.  For example something
> like this in the case of non-predictive mode:
> 
>    PaC           nPAA              pPAA
>    ----------------------------------------
>          CTAR 
>    --------------->       CT-Request 
>                         ------------>
>                              CTD 
>                         <------------
> 
>          PSR
>    <---------------
>     PSA[old Session-ID, Nonce]   // MAC AVP is not needed.
>     --------------->
>     PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
>    <-------------
>     PBA[new Session-ID, Key-Id, PPAC, MAC]
>     ------------->
> 
> This has half round-trip redundancy compared to your proposal (due to
> non-piggybacking CTAR), but provides better modularity between PANA
> and Context Transfer Protocol.  Also this works with both
> non-predictive and predictive modes.

The problem in this case is that the nEP will detect the CTAR message
and trigger a PANA authentication message. This means that in the same
time, we will have a PSR/PSA exchange and CT-Request/CTD. We can't
decorrelate PANA and CTP.

In my mind, when the pana module at pac receives a psr message it asks
the ctp module to provide the CTAR message. Thus we keep the
modularity.


> 
> [3] In CTD-PANA message, I think ISN-pac, ISN-paa, tseq and rseq do
> not have to be defined in CTD-PANA, because sequence number contexts
> are not inherited from the pPAA (i.e., new sequence number context is
> established in the PSR-PBA exchange between PaC and nPAA).  Also, I
> think retransmission interval does not need to be defined in CTD-PANA,
> since retransmission interval can be locally determined parameter.

I guess you are right. We'll delete those parameters in the next
revision.

-- 
julien.bournelle@int-evry.fr

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 07:40:19 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00769
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 07:40:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bjz1C-0002po-Ig; Mon, 12 Jul 2004 07:30:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bjyt7-0001t0-PY
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 07:22:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00087
	for <pana@ietf.org>; Mon, 12 Jul 2004 07:22:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bjyt2-0000zO-B3
	for pana@ietf.org; Mon, 12 Jul 2004 07:22:20 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bjys1-0000ms-00
	for pana@ietf.org; Mon, 12 Jul 2004 07:21:18 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bjyqy-0000QV-00
	for pana@ietf.org; Mon, 12 Jul 2004 07:20:13 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6CBK9pD014600;
	Mon, 12 Jul 2004 20:20:09 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6CBK9rr010019;
	Mon, 12 Jul 2004 20:20:09 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	WAA10016 ; Mon, 12 Jul 2004 20:20:08 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id UAA27791; Mon, 12 Jul 2004 20:20:08 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id UAA28313;
	Mon, 12 Jul 2004 20:20:07 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6CBK7pl012355;
	Mon, 12 Jul 2004 20:20:07 +0900 (JST)
Received: from steelhead (ncg-dhcp84.isl.rdc.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0Q00IWDKTI2I@tsbpo1.po.toshiba.co.jp>; Mon,
	12 Jul 2004 20:20:06 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bjypv-0001ts-00; Mon, 12 Jul 2004 04:19:07 -0700
Date: Mon, 12 Jul 2004 07:19:07 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Mobility Handling in PANA
In-reply-to: <20040712101804.GF44906@ipv6-5.int-evry.fr>
To: Julien Bournelle <Julien.Bournelle@int-evry.fr>
Message-id: <20040712111907.GT893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Julien Bournelle <Julien.Bournelle@int-evry.fr>,
	yohba@tari.toshiba.com, pana@ietf.org,
	Gerardo Giaretta <gerardo.giaretta@tilab.com>
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
	<20040710062738.GD893@steelhead>
	<20040712101804.GF44906@ipv6-5.int-evry.fr>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Gerardo Giaretta <gerardo.giaretta@tilab.com>, yohba@tari.toshiba.com,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Julien,

Thanks for your reply.  Please see my comment on [2].

On Mon, Jul 12, 2004 at 12:18:04PM +0200, Julien Bournelle wrote:
> 
> > 
> > [2] I think it is also possible to run the MN-AR context transfer
> > protocol to carry CTAR messages between MN and nPAA (or pPAA) instead
> > of piggybacking CTAR messages in PANA messages.  For example something
> > like this in the case of non-predictive mode:
> > 
> >    PaC           nPAA              pPAA
> >    ----------------------------------------
> >          CTAR 
> >    --------------->       CT-Request 
> >                         ------------>
> >                              CTD 
> >                         <------------
> > 
> >          PSR
> >    <---------------
> >     PSA[old Session-ID, Nonce]   // MAC AVP is not needed.
> >     --------------->
> >     PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> >    <-------------
> >     PBA[new Session-ID, Key-Id, PPAC, MAC]
> >     ------------->
> > 
> > This has half round-trip redundancy compared to your proposal (due to
> > non-piggybacking CTAR), but provides better modularity between PANA
> > and Context Transfer Protocol.  Also this works with both
> > non-predictive and predictive modes.
> 
> The problem in this case is that the nEP will detect the CTAR message
> and trigger a PANA authentication message. This means that in the same
> time, we will have a PSR/PSA exchange and CT-Request/CTD. We can't
> decorrelate PANA and CTP.
> 
> In my mind, when the pana module at pac receives a psr message it asks
> the ctp module to provide the CTAR message. Thus we keep the
> modularity.

Something like this?


    PaC           nPAA              pPAA
    ----------------------------------------
          PDI
     -------------->
          PSR
    <---------------
          CTAR
     --------------->

                          CT-Request 
                       -------------->
                              CTD 
                       <--------------

     PSA[old Session-ID, Nonce, MAC]
     --------------->
     PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
    <-------------
     PBA[new Session-ID, Key-Id, PPAC, MAC]
     ------------->
 

Yoshihiro Ohba

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 07:46:42 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01105
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 07:46:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BjzDf-0004YM-4b; Mon, 12 Jul 2004 07:43:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjzAU-0003y6-Oo
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 07:40:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00804
	for <pana@ietf.org>; Mon, 12 Jul 2004 07:40:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjzAU-0004Yq-6q
	for pana@ietf.org; Mon, 12 Jul 2004 07:40:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bjz9a-0004Ni-00
	for pana@ietf.org; Mon, 12 Jul 2004 07:39:27 -0400
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx with esmtp (Exim 4.12) id 1Bjz90-0004Bl-00
	for pana@ietf.org; Mon, 12 Jul 2004 07:38:50 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0I0Q00J1TLLLSS@dns1.cselt.it> for pana@ietf.org; Mon,
	12 Jul 2004 13:36:57 +0200 (MEST)
Received: from EXC2K01A.cselt.it ([163.162.4.34]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Mon, 12 Jul 2004 13:39:46 +0200
Received: from EXC2K01B.cselt.it ([163.162.4.97]) by EXC2K01A.cselt.it with
	Microsoft SMTPSVC(5.0.2195.5329); Mon, 12 Jul 2004 13:38:18 +0200
Date: Mon, 12 Jul 2004 13:38:18 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Pana] Mobility Handling in PANA
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Message-id: <625BE97BF4795E43970345790166B9BCD4DF2E@EXC2K01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Pana] Mobility Handling in PANA
Thread-Index: AcRnpSg2foJC6UdWTfe8NLXXkxcujAAXvLXQ
content-class: urn:content-classes:message
X-OriginalArrivalTime: 12 Jul 2004 11:38:18.0768 (UTC)
	FILETIME=[BA486100:01C46804]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Yoshi,

thanks for your comments.

> Hi Gerardo,
>=20
> Another comment on draft-bournelle-pana-ctp-00.txt:
>=20
> I am not sure how EAP-based re-authentication can work after=20
> the PaC has successfully established a new PANA session with=20
> nPAA based on the mobility optimization operation, especially=20
> with NAP and ISP separated authentications.  Since PSR-PSA=20
> exchange is omitted in the case of EAP-based=20
> re-authentication, there is no means to negotiate on NAP and=20
> ISP separate authentications between the PaC and nPAA.  Do=20
> you have any thoughts on this?
>=20

I'm not sure I understand your point: is this a general PANA issue or is
it related to the operations described in
draft-bournelle-pana-ctp-00.txt?

--Gerardo




Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 07:56:39 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01414
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 07:56:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BjzEb-0004aK-S6; Mon, 12 Jul 2004 07:44:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjzBT-00049C-3K
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 07:41:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00832
	for <pana@ietf.org>; Mon, 12 Jul 2004 07:41:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjzBS-0004kc-LC
	for pana@ietf.org; Mon, 12 Jul 2004 07:41:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjzAV-0004Z3-00
	for pana@ietf.org; Mon, 12 Jul 2004 07:40:23 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx with esmtp (Exim 4.12) id 1BjzA2-0004NU-00
	for pana@ietf.org; Mon, 12 Jul 2004 07:39:54 -0400
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 1B28E2FD5C;
	Mon, 12 Jul 2004 13:39:14 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1Bjz84-000BmN-Tg;
	Mon, 12 Jul 2004 13:37:52 +0200
Date: Mon, 12 Jul 2004 13:37:52 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: yohba@tari.toshiba.com, pana@ietf.org,
        Gerardo Giaretta <gerardo.giaretta@tilab.com>
Subject: Re: [Pana] Mobility Handling in PANA
Message-ID: <20040712113752.GJ44906@ipv6-5.int-evry.fr>
References: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
	<20040710062738.GD893@steelhead>
	<20040712101804.GF44906@ipv6-5.int-evry.fr>
	<20040712111907.GT893@steelhead>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040712111907.GT893@steelhead>
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (score=-4.9, requis 4.5, autolearn=not spam,
	BAYES_00 -4.90)
X-MailScanner-From: jb@ipv6-5.int-evry.fr
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

comments inline,

> On Mon, Jul 12, 2004 at 12:18:04PM +0200, Julien Bournelle wrote:
> > 
> > The problem in this case is that the nEP will detect the CTAR message
> > and trigger a PANA authentication message. This means that in the same
> > time, we will have a PSR/PSA exchange and CT-Request/CTD. We can't
> > decorrelate PANA and CTP.
> > 
> > In my mind, when the pana module at pac receives a psr message it asks
> > the ctp module to provide the CTAR message. Thus we keep the
> > modularity.
> 
> Something like this?
> 
> 
>     PaC           nPAA              pPAA
>     ----------------------------------------
>           PDI
>      -------------->
>           PSR
>     <---------------
>           CTAR
>      --------------->
> 
>                           CT-Request 
>                        -------------->
>                               CTD 
>                        <--------------
> 
>      PSA[old Session-ID, Nonce, MAC]
>      --------------->
>      PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
>     <-------------
>      PBA[new Session-ID, Key-Id, PPAC, MAC]
>      ------------->


if you do this, this means that the pac answers to a PANA message (PSR)
with a CTP message (CTAR). Moreover the nPAA waits for PSA message and
not for a CTP message. So at the nPAA, you receive a CTP message whereas
you are waiting for PANA message. 

This is why we propose to emebed the CTAR message in the PSR message.
Thus the pac answers with a PSA message. The PANA module at the pac aks
to the CTP module to get a valid CTAR message and embeds it in the PSA
message. The nPAA receives the PSA message that it is waiting for and
sees that it contains a CTAR message. It delivers it to its CTP module
and waits the CT-Request/CTD exchange. This why we introduce a new state
in the state machine (PANA-CTP-WAITING)


Thus we propose this:


     PaC           nPAA              pPAA
     ----------------------------------------
           PDI
      -------------->
           PSR
     <---------------
          PSA [old Session-ID, Nonce, CTAR] 
      --------------->
 
                           CT-Request 
                        -------------->
                               CTD 
                        <--------------

      PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
     <-------------
      PBA[new Session-ID, Key-Id, PPAC, MAC]
      ------------->




-- 
julien.bournelle@int-evry.fr

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 08:20:50 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02689
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 08:20:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bjze5-0007DO-8x; Mon, 12 Jul 2004 08:10:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjzSw-0006Dz-S9
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 07:59:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01521
	for <pana@ietf.org>; Mon, 12 Jul 2004 07:59:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjzSv-0000RM-UQ
	for pana@ietf.org; Mon, 12 Jul 2004 07:59:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjzS3-0000FO-00
	for pana@ietf.org; Mon, 12 Jul 2004 07:58:32 -0400
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx with esmtp (Exim 4.12) id 1BjzRP-00001O-00
	for pana@ietf.org; Mon, 12 Jul 2004 07:57:51 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I0Q00C3GKXWU8@dns2.cselt.it> for pana@ietf.org; Mon,
	12 Jul 2004 13:22:44 +0200 (MEST)
Received: from EXC2K04A.cselt.it ([163.162.161.230]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Mon, 12 Jul 2004 13:27:33 +0200
Received: from EXC2K01B.cselt.it ([163.162.4.97]) by EXC2K04A.cselt.it with
	Microsoft SMTPSVC(5.0.2195.5329); Mon, 12 Jul 2004 13:29:33 +0200
Date: Mon, 12 Jul 2004 13:29:32 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Pana] Mobility Handling in PANA
To: yohba@tari.toshiba.com, Julien Bournelle <Julien.Bournelle@int-evry.fr>
Message-id: <625BE97BF4795E43970345790166B9BCD4DF2C@EXC2K01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Pana] Mobility Handling in PANA
Thread-Index: AcRn+x/i/FyJ+IQ6Rvy4aedwlEWfiQABsVig
content-class: urn:content-classes:message
X-OriginalArrivalTime: 12 Jul 2004 11:29:33.0465 (UTC)
	FILETIME=[812D8090:01C46803]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Cc: Gerardo Giaretta <gerardo.giaretta@TILAB.COM>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Yoshi, Julien,

just one more comment. See inline..


> > [2] I think it is also possible to run the MN-AR context transfer=20
> > protocol to carry CTAR messages between MN and nPAA (or=20
> pPAA) instead=20
> > of piggybacking CTAR messages in PANA messages.  For=20
> example something=20
> > like this in the case of non-predictive mode:
> >=20
> >    PaC           nPAA              pPAA
> >    ----------------------------------------
> >          CTAR=20
> >    --------------->       CT-Request=20
> >                         ------------>
> >                              CTD=20
> >                         <------------
> >=20
> >          PSR
> >    <---------------
> >     PSA[old Session-ID, Nonce]   // MAC AVP is not needed.
> >     --------------->
> >     PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> >    <-------------
> >     PBA[new Session-ID, Key-Id, PPAC, MAC]
> >     ------------->
> >=20
> > This has half round-trip redundancy compared to your=20
> proposal (due to=20
> > non-piggybacking CTAR), but provides better modularity between PANA=20
> > and Context Transfer Protocol.  Also this works with both=20
> > non-predictive and predictive modes.
>=20
> The problem in this case is that the nEP will detect the CTAR=20
> message and trigger a PANA authentication message. This means=20
> that in the same time, we will have a PSR/PSA exchange and=20
> CT-Request/CTD. We can't decorrelate PANA and CTP.
>=20
> In my mind, when the pana module at pac receives a psr=20
> message it asks the ctp module to provide the CTAR message.=20
> Thus we keep the modularity.
>=20

Moreover, the nEP usually does not allow ICMP (i.e. CTAR) packets for
unauthorized PaC.=20
Therefore, in non-predictive case, I think that the message exchange
provided by Yoshi does not work. The nEP blocks the CTAR message and
triggers PANA authentication: in this way CTP and PANA, as Julien
pointed out, are decorrelated and no optimizations are possible.

--Gerardo =20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 08:21:07 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02719
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 08:21:07 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bjze5-0007DV-Ih; Mon, 12 Jul 2004 08:10:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjzSx-0006F7-NR
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 07:59:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01526
	for <pana@ietf.org>; Mon, 12 Jul 2004 07:59:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjzSx-0000RW-40
	for pana@ietf.org; Mon, 12 Jul 2004 07:59:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjzS4-0000FW-00
	for pana@ietf.org; Mon, 12 Jul 2004 07:58:33 -0400
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx with esmtp (Exim 4.12) id 1BjzRP-00001O-01
	for pana@ietf.org; Mon, 12 Jul 2004 07:57:51 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I0Q00C4BL5CUA@dns2.cselt.it> for pana@ietf.org; Mon,
	12 Jul 2004 13:27:12 +0200 (MEST)
Received: from EXC01C.cselt.it ([163.162.4.217]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Mon, 12 Jul 2004 13:32:00 +0200
Received: from EXC2K01B.cselt.it ([163.162.4.97])
	by EXC01C.cselt.it with Microsoft SMTPSVC(6.0.3790.0); Mon,
	12 Jul 2004 13:34:00 +0200
Date: Mon, 12 Jul 2004 13:34:00 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Pana] Mobility Handling in PANA
To: Yoshihiro Ohba <yohba@tari.toshiba.com>,
        Julien Bournelle <Julien.Bournelle@int-evry.fr>
Message-id: <625BE97BF4795E43970345790166B9BCD4DF2D@EXC2K01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Pana] Mobility Handling in PANA
Thread-Index: AcRoAz/jNLklF3olRPWfPWu623LvJQAABNTw
content-class: urn:content-classes:message
X-OriginalArrivalTime: 12 Jul 2004 11:34:00.0958 (UTC)
	FILETIME=[209DB1E0:01C46804]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Yoshi,

>=20
> Something like this?
>=20
>=20
>     PaC           nPAA              pPAA
>     ----------------------------------------
>           PDI
>      -------------->
>           PSR
>     <---------------
>           CTAR
>      --------------->
>=20
>                           CT-Request=20
>                        -------------->
>                               CTD=20
>                        <--------------
>=20
>      PSA[old Session-ID, Nonce, MAC]
>      --------------->
>      PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
>     <-------------
>      PBA[new Session-ID, Key-Id, PPAC, MAC]
>      ------------->
> =20
>=20
> Yoshihiro Ohba
>=20

Just a question (see also my previous email): CTAR is an ICMP packet. Do
you think it is feasible that the nEP allows this packet to be
transferred to the nPAA even though the PaC is not authenticated yet?

--Gerardo


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 08:28:20 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03259
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 08:28:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bjzmg-0008HG-Cn; Mon, 12 Jul 2004 08:19:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BjzUB-0006NK-1T
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 08:00:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01617
	for <pana@ietf.org>; Mon, 12 Jul 2004 08:00:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BjzUA-0000i4-GB
	for pana@ietf.org; Mon, 12 Jul 2004 08:00:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BjzTC-0000U4-00
	for pana@ietf.org; Mon, 12 Jul 2004 07:59:43 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BjzSb-0000GD-00
	for pana@ietf.org; Mon, 12 Jul 2004 07:59:05 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6CBx0pD003700;
	Mon, 12 Jul 2004 20:59:00 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6CBx0tY010034;
	Mon, 12 Jul 2004 20:59:00 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	WAA10033 ; Mon, 12 Jul 2004 20:59:00 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id UAA22228; Mon, 12 Jul 2004 20:58:59 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id UAA13807;
	Mon, 12 Jul 2004 20:58:59 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6CBwwpl004326;
	Mon, 12 Jul 2004 20:58:58 +0900 (JST)
Received: from steelhead (ncg-dhcp84.isl.rdc.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0Q000QDMMAAP@tsbpo1.po.toshiba.co.jp>; Mon,
	12 Jul 2004 20:58:58 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BjzRg-00024Y-00; Mon, 12 Jul 2004 04:58:08 -0700
Date: Mon, 12 Jul 2004 07:58:08 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Mobility Handling in PANA
In-reply-to: <625BE97BF4795E43970345790166B9BCD4DF2E@EXC2K01B.cselt.it>
To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Message-id: <20040712115808.GV893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>,
	Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BCD4DF2E@EXC2K01B.cselt.it>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Gerardo,

On Mon, Jul 12, 2004 at 01:38:18PM +0200, Giaretta Gerardo wrote:
> Hi Yoshi,
> 
> thanks for your comments.
> 
> > Hi Gerardo,
> > 
> > Another comment on draft-bournelle-pana-ctp-00.txt:
> > 
> > I am not sure how EAP-based re-authentication can work after 
> > the PaC has successfully established a new PANA session with 
> > nPAA based on the mobility optimization operation, especially 
> > with NAP and ISP separated authentications.  Since PSR-PSA 
> > exchange is omitted in the case of EAP-based 
> > re-authentication, there is no means to negotiate on NAP and 
> > ISP separate authentications between the PaC and nPAA.  Do 
> > you have any thoughts on this?
> > 
> 
> I'm not sure I understand your point: is this a general PANA issue or is
> it related to the operations described in
> draft-bournelle-pana-ctp-00.txt?

It might be related to both.  I think that if NAP and ISP separate
authentications were made in the initial authentication, then the same
NAP and ISP separate authentications should also be made in EAP-based
re-authentication (this is a PANA issue, i.e., this should be
described in the PANA specification.)  If the same thing needs to be
done in EAP-based re-authentication after handoff (though I am not
sure the same thing needs to be done in this case), information on
whether NAP and ISP separate authentications were made in the previous
network may need to be included in PANA-CTD (this is an issue of
draft-bournelle-pana-ctp-00.txt).

Yoshihiro Ohba


> 
> --Gerardo
> 
> 
> 
> 
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
> 
> ====================================================================
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to 
> MailAdmin@tilab.com. Thank you
> ====================================================================

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 08:37:04 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03790
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 08:37:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BjzoJ-00009a-DS; Mon, 12 Jul 2004 08:21:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bjzfs-0007PH-0y
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 08:12:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02100
	for <pana@ietf.org>; Mon, 12 Jul 2004 08:12:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bjzfp-0003AA-0G
	for pana@ietf.org; Mon, 12 Jul 2004 08:12:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bjzed-0002vK-00
	for pana@ietf.org; Mon, 12 Jul 2004 08:11:32 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BjzeG-0002jH-00
	for pana@ietf.org; Mon, 12 Jul 2004 08:11:09 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6CCB7pD009023;
	Mon, 12 Jul 2004 21:11:07 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6CCB76H018155;
	Mon, 12 Jul 2004 21:11:07 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	XAA18150 ; Mon, 12 Jul 2004 21:11:07 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id VAA29829; Mon, 12 Jul 2004 21:11:06 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id VAA24801;
	Mon, 12 Jul 2004 21:11:06 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6CCB5pl010746;
	Mon, 12 Jul 2004 21:11:05 +0900 (JST)
Received: from steelhead (ncg-dhcp84.isl.rdc.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0Q0024RN6H3F@tsbpo1.po.toshiba.co.jp>; Mon,
	12 Jul 2004 21:11:05 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bjzdo-00028Q-00; Mon, 12 Jul 2004 05:10:40 -0700
Date: Mon, 12 Jul 2004 08:10:40 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Mobility Handling in PANA
In-reply-to: <625BE97BF4795E43970345790166B9BCD4DF2D@EXC2K01B.cselt.it>
To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Message-id: <20040712121040.GW893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>,
	Yoshihiro Ohba <yohba@tari.toshiba.com>,
	Julien Bournelle <Julien.Bournelle@int-evry.fr>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BCD4DF2D@EXC2K01B.cselt.it>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Gerardo,

I think it is feasible to pass only limited type of packet like CTAR
to pass through EP.  I don't see any significant difference between
piggybacking CTAR and non-piggybacking in terms of security.

Yoshihiro Ohba


On Mon, Jul 12, 2004 at 01:34:00PM +0200, Giaretta Gerardo wrote:
> Yoshi,
> 
> > 
> > Something like this?
> > 
> > 
> >     PaC           nPAA              pPAA
> >     ----------------------------------------
> >           PDI
> >      -------------->
> >           PSR
> >     <---------------
> >           CTAR
> >      --------------->
> > 
> >                           CT-Request 
> >                        -------------->
> >                               CTD 
> >                        <--------------
> > 
> >      PSA[old Session-ID, Nonce, MAC]
> >      --------------->
> >      PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> >     <-------------
> >      PBA[new Session-ID, Key-Id, PPAC, MAC]
> >      ------------->
> >  
> > 
> > Yoshihiro Ohba
> > 
> 
> Just a question (see also my previous email): CTAR is an ICMP packet. Do
> you think it is feasible that the nEP allows this packet to be
> transferred to the nPAA even though the PaC is not authenticated yet?

> 
> --Gerardo
> 
> 
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
> 
> ====================================================================
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to
> MailAdmin@tilab.com. Thank you
> ====================================================================

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 08:58:37 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04729
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 08:58:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bk0CZ-0003T8-8Q; Mon, 12 Jul 2004 08:46:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk02j-0001jH-4H
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 08:36:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03777
	for <pana@ietf.org>; Mon, 12 Jul 2004 08:36:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bk02i-0000CL-G7
	for pana@ietf.org; Mon, 12 Jul 2004 08:36:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk01x-00000T-00
	for pana@ietf.org; Mon, 12 Jul 2004 08:35:37 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bk01I-0007bo-00
	for pana@ietf.org; Mon, 12 Jul 2004 08:34:57 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6CCYspD019686;
	Mon, 12 Jul 2004 21:34:54 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6CCYs6B004193;
	Mon, 12 Jul 2004 21:34:54 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	XAA04190 ; Mon, 12 Jul 2004 21:34:54 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id VAA14381; Mon, 12 Jul 2004 21:34:53 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id VAA23079;
	Mon, 12 Jul 2004 21:34:52 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6CCYqpl024214;
	Mon, 12 Jul 2004 21:34:52 +0900 (JST)
Received: from steelhead (ncg-dhcp84.isl.rdc.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0Q0042YOA31Y@tsbpo1.po.toshiba.co.jp>; Mon,
	12 Jul 2004 21:34:51 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bk00S-0002DP-00; Mon, 12 Jul 2004 05:34:04 -0700
Date: Mon, 12 Jul 2004 08:34:04 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Mobility Handling in PANA
In-reply-to: <20040712113752.GJ44906@ipv6-5.int-evry.fr>
To: Julien Bournelle <Julien.Bournelle@int-evry.fr>
Message-id: <20040712123404.GX893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Julien Bournelle <Julien.Bournelle@int-evry.fr>,
	yohba@tari.toshiba.com, pana@ietf.org,
	Gerardo Giaretta <gerardo.giaretta@tilab.com>
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
	<20040710062738.GD893@steelhead>
	<20040712101804.GF44906@ipv6-5.int-evry.fr>
	<20040712111907.GT893@steelhead>
	<20040712113752.GJ44906@ipv6-5.int-evry.fr>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Gerardo Giaretta <gerardo.giaretta@tilab.com>, yohba@tari.toshiba.com,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Julien,

On Mon, Jul 12, 2004 at 01:37:52PM +0200, Julien Bournelle wrote:
> comments inline,
> 
> > On Mon, Jul 12, 2004 at 12:18:04PM +0200, Julien Bournelle wrote:
> > > 
> > > The problem in this case is that the nEP will detect the CTAR message
> > > and trigger a PANA authentication message. This means that in the same
> > > time, we will have a PSR/PSA exchange and CT-Request/CTD. We can't
> > > decorrelate PANA and CTP.
> > > 
> > > In my mind, when the pana module at pac receives a psr message it asks
> > > the ctp module to provide the CTAR message. Thus we keep the
> > > modularity.
> > 
> > Something like this?
> > 
> > 
> >     PaC           nPAA              pPAA
> >     ----------------------------------------
> >           PDI
> >      -------------->
> >           PSR
> >     <---------------
> >           CTAR
> >      --------------->
> > 
> >                           CT-Request 
> >                        -------------->
> >                               CTD 
> >                        <--------------
> > 
> >      PSA[old Session-ID, Nonce, MAC]
> >      --------------->
> >      PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> >     <-------------
> >      PBA[new Session-ID, Key-Id, PPAC, MAC]
> >      ------------->
> 
> 
> if you do this, this means that the pac answers to a PANA message (PSR)
> with a CTP message (CTAR). Moreover the nPAA waits for PSA message and
> not for a CTP message. So at the nPAA, you receive a CTP message whereas
> you are waiting for PANA message. 

Since PANA and CTP are different protocols, I think nPAA can wait for
messages from both protocols at the same time without violating both
protocols.  But parhaps it is better in this case that CTAR is
acknowledged with CTAA and the PaC sends PSA after receiving CTAA to
provide synchronization bewteen context transfer operation and PANA
mobility optimization, something like:

PaC           nPAA              pPAA
----------------------------------------
      PDI
 -------------->
      PSR
 <---------------
      CTAR
 --------------->
                     CT-Request 
                  -------------->
                         CTD 
                  <--------------
      CTAA
 <--------------

  PSA[old Session-ID, Nonce, MAC]
  --------------->
  PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
  <-------------
  PBA[new Session-ID, Key-Id, PPAC, MAC]
  ------------->

Comparing this scheme with your scheme below, the discussion point
would be modularity (this sheme) vs optimization (your scheme).

Yoshihiro Ohba

> 
> This is why we propose to emebed the CTAR message in the PSR message.
> Thus the pac answers with a PSA message. The PANA module at the pac aks
> to the CTP module to get a valid CTAR message and embeds it in the PSA
> message. The nPAA receives the PSA message that it is waiting for and
> sees that it contains a CTAR message. It delivers it to its CTP module
> and waits the CT-Request/CTD exchange. This why we introduce a new state
> in the state machine (PANA-CTP-WAITING)
> 
> 
> Thus we propose this:
> 
> 
>      PaC           nPAA              pPAA
>      ----------------------------------------
>            PDI
>       -------------->
>            PSR
>      <---------------
>           PSA [old Session-ID, Nonce, CTAR] 
>       --------------->
>  
>                            CT-Request 
>                         -------------->
>                                CTD 
>                         <--------------
> 
>       PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
>      <-------------
>       PBA[new Session-ID, Key-Id, PPAC, MAC]
>       ------------->
> 
> 
> 
> 
> -- 
> julien.bournelle@int-evry.fr

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 11:18:39 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16628
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 11:18:38 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bk27i-0004fd-Kh; Mon, 12 Jul 2004 10:49:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk1yt-00025T-HJ
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 10:40:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12364
	for <pana@ietf.org>; Mon, 12 Jul 2004 10:40:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bk1ys-0004zF-DW
	for pana@ietf.org; Mon, 12 Jul 2004 10:40:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk1y3-0004m1-00
	for pana@ietf.org; Mon, 12 Jul 2004 10:39:43 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx with esmtp (Exim 4.12) id 1Bk1xL-0004Uj-00
	for pana@ietf.org; Mon, 12 Jul 2004 10:38:59 -0400
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by smtp2.int-evry.fr (Postfix) with ESMTP id BE2C72FD44;
	Mon, 12 Jul 2004 16:38:23 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1Bk1vS-000BuC-Db;
	Mon, 12 Jul 2004 16:37:02 +0200
Date: Mon, 12 Jul 2004 16:37:02 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: yohba@tari.toshiba.com, pana@ietf.org,
        Gerardo Giaretta <gerardo.giaretta@tilab.com>
Subject: Re: [Pana] Mobility Handling in PANA
Message-ID: <20040712143702.GA45745@ipv6-5.int-evry.fr>
References: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
	<20040710062738.GD893@steelhead>
	<20040712101804.GF44906@ipv6-5.int-evry.fr>
	<20040712111907.GT893@steelhead>
	<20040712113752.GJ44906@ipv6-5.int-evry.fr>
	<20040712123404.GX893@steelhead>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040712123404.GX893@steelhead>
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (score=-4.9, requis 4.5, autolearn=not spam,
	BAYES_00 -4.90)
X-MailScanner-From: jb@ipv6-5.int-evry.fr
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

> Since PANA and CTP are different protocols, I think nPAA can wait for
> messages from both protocols at the same time without violating both
> protocols.  But parhaps it is better in this case that CTAR is
> acknowledged with CTAA and the PaC sends PSA after receiving CTAA to
> provide synchronization bewteen context transfer operation and PANA
> mobility optimization, something like:
> 
> PaC           nPAA              pPAA
> ----------------------------------------
>       PDI
>  -------------->
>       PSR
>  <---------------
>       CTAR
>  --------------->
>                      CT-Request 
>                   -------------->
>                          CTD 
>                   <--------------
>       CTAA
>  <--------------
> 
>   PSA[old Session-ID, Nonce, MAC]
>   --------------->
>   PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
>   <-------------
>   PBA[new Session-ID, Key-Id, PPAC, MAC]
>   ------------->
> 
> Comparing this scheme with your scheme below, the discussion point
> would be modularity (this sheme) vs optimization (your scheme).

I think that with our solution we keep the modularity since the pana
module asks to the ctp module the CTAR message to be sent.

In your scenario, the PANA module at PaC receives the PSR message and
contacts the CTP module (saying that CTP module must sent a CTAR).
In our scenario, the PANA module asks to the CTP module the CTAR
message and embeds it. Thus I think that we keep the modularity.

Maybe I miss something, what do you mean by modularity ?

> 
> Yoshihiro Ohba
> 
> > 
> > This is why we propose to emebed the CTAR message in the PSR message.
> > Thus the pac answers with a PSA message. The PANA module at the pac aks
> > to the CTP module to get a valid CTAR message and embeds it in the PSA
> > message. The nPAA receives the PSA message that it is waiting for and
> > sees that it contains a CTAR message. It delivers it to its CTP module
> > and waits the CT-Request/CTD exchange. This why we introduce a new state
> > in the state machine (PANA-CTP-WAITING)
> > 
> > 
> > Thus we propose this:
> > 
> > 
> >      PaC           nPAA              pPAA
> >      ----------------------------------------
> >            PDI
> >       -------------->
> >            PSR
> >      <---------------
> >           PSA [old Session-ID, Nonce, CTAR] 
> >       --------------->
> >  
> >                            CT-Request 
> >                         -------------->
> >                                CTD 
> >                         <--------------
> > 
> >       PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> >      <-------------
> >       PBA[new Session-ID, Key-Id, PPAC, MAC]
> >       ------------->
> > 
> > 
> > 
> > 
> > -- 
> > julien.bournelle@int-evry.fr
> 

-- 
julien.bournelle@int-evry.fr

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 12:15:07 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20781
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 12:15:07 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bk3Co-0002BQ-Mj; Mon, 12 Jul 2004 11:59:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk2yr-0007NO-3A
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 11:44:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18586
	for <pana@ietf.org>; Mon, 12 Jul 2004 11:44:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bk2yq-00044W-3C
	for pana@ietf.org; Mon, 12 Jul 2004 11:44:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk2xu-0003pm-00
	for pana@ietf.org; Mon, 12 Jul 2004 11:43:39 -0400
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx with esmtp (Exim 4.12) id 1Bk2x1-0003ON-00
	for pana@ietf.org; Mon, 12 Jul 2004 11:42:43 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0I0Q00469WW2GK@dns1.cselt.it> for pana@ietf.org; Mon,
	12 Jul 2004 17:40:50 +0200 (MEST)
Received: from EXC2K04A.cselt.it ([163.162.161.230]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Mon, 12 Jul 2004 17:43:39 +0200
Received: from EXC2K01B.cselt.it ([163.162.4.97]) by EXC2K04A.cselt.it with
	Microsoft SMTPSVC(5.0.2195.5329); Mon, 12 Jul 2004 17:42:11 +0200
Date: Mon, 12 Jul 2004 17:42:11 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Pana] Mobility Handling in PANA
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Message-id: <625BE97BF4795E43970345790166B9BCE8D70A@EXC2K01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Pana] Mobility Handling in PANA
Thread-Index: AcRoB91OcpL5K3omTqKlc3kZBRC0pwADePGw
content-class: urn:content-classes:message
X-OriginalArrivalTime: 12 Jul 2004 15:42:11.0949 (UTC)
	FILETIME=[CC5699D0:01C46826]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Cc: Julien Bournelle <Julien.Bournelle@int-evry.fr>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Yoshi,

> > > I am not sure how EAP-based re-authentication can work after the=20
> > > PaC has successfully established a new PANA session with nPAA=20
> > > based on the mobility optimization operation, especially with NAP=20
> > > and ISP separated authentications.  Since PSR-PSA exchange is=20
> > > omitted in the case of EAP-based re-authentication, there is no=20
> > > means to negotiate on NAP and ISP separate authentications between

> > > the PaC and nPAA.  Do you have any thoughts on this?
> > >=20
> >=20
> > I'm not sure I understand your point: is this a general
> PANA issue or
> > is it related to the operations described in
> > draft-bournelle-pana-ctp-00.txt?
>=20
> It might be related to both.  I think that if NAP and ISP
> separate authentications were made in the initial=20
> authentication, then the same NAP and ISP separate=20
> authentications should also be made in EAP-based=20
> re-authentication (this is a PANA issue, i.e., this should be=20
> described in the PANA specification.)  If the same thing=20
> needs to be done in EAP-based re-authentication after handoff=20
> (though I am not sure the same thing needs to be done in this=20
> case), information on whether NAP and ISP separate=20
> authentications were made in the previous network may need to=20
> be included in PANA-CTD (this is an issue of=20
> draft-bournelle-pana-ctp-00.txt).
>

I agree with you. The result of the usage of CTP, as the result of any
fast authentication mechanism, must be the same as the one obtained
performing the whole authentication procedure. This implies that nPAA
should know if PaC performed double authentication and which ISP it
chose. Therefore this information must be transferred in CTD message.=20

However, I think that EAP re-authentication is not related to mobility
handling. The usage of CTP allows to transfer the PANA context to the
nPAA. After the PBR/PBA exchange the PaC is authenticated and the nPAA
knows the residual authorization lifetime. Therefore
EAP-reauthentication is not performed immediately after the handoff and
it is accomplished as specified in PANA specs.

Note that we have not defined yet how to inform both NAP and ISP AAA
system of the new PaC's location. I think this is also an important
issue.


--Gerardo


=20
> Yoshihiro Ohba
>=20




Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 21:28:28 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09429
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 21:28:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkAsN-0002oN-8y; Mon, 12 Jul 2004 20:10:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk8Qu-0001uX-BY
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 17:33:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17479
	for <pana@ietf.org>; Mon, 12 Jul 2004 17:33:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bk8Qs-0006Us-QH
	for pana@ietf.org; Mon, 12 Jul 2004 17:33:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk8Px-0006Dz-00
	for pana@ietf.org; Mon, 12 Jul 2004 17:32:59 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12) id 1Bk8PA-0005fw-00
	for pana@ietf.org; Mon, 12 Jul 2004 17:32:08 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0R00G01D4O5A@mailout3.samsung.com> for pana@ietf.org; Tue,
	13 Jul 2004 06:31:36 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0R00647D4NR4@mailout3.samsung.com> for pana@ietf.org;
	Tue, 13 Jul 2004 06:31:36 +0900 (KST)
Received: from Alperyegin ([105.253.155.20])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0R00EYSD4KGC@mmp1.samsung.com> for
	pana@ietf.org; Tue, 13 Jul 2004 06:31:35 +0900 (KST)
Date: Mon, 12 Jul 2004 14:31:37 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] PANA key derivation key
In-reply-to: <20040705164928.GD17360@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <009301c46857$9e412750$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Hi Yoshi,

> [1] In section 2,
> 
> change:
> 
> "
>    AAA-Key:
> 
>       A key derived by the EAP peer and EAP server and transported to
>       the authenticator [I-D.ietf-eap-keying].
> "
> 
> to:
> 
> "
>    AAA-Key:
> 
>       A key derived by the EAP peer and EAP server and transported to
>       the authenticator [I-D.ietf-eap-keying].  In this document, when
>       there are two such keys, namely AAA-Key1 and AAA-Key2, are
>       generated as a result of running two EAP authentications in a
>       single round of PANA authentication, the AAA-Key from
>       which other keys are derived refers to the concatenation of
>       AAA-Key1 and AAA-Key2.
> "


I think it is better if we didn't get into the specific AAA-keys and
computations in the terminology. I think we should keep the terminology
section as is, and later discuss how AAA-Key may be set to
AAA-Key1|AAA-Key2.


> 
> 
> [2] In section 4.1.5 of draft-ietf-pana-pana-04.txt change:
> 
> 
> "
>    The PANA_MAC_Key is used to integrity protect PANA messages.  When
>    the PANA_MAC_Key is derived from a single AAA-Key, it is computed
in
>    the following way:
> 
> 
>       PANA_MAC_KEY = The first N bits of
>                      HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa |
Session-ID)
> 
>    where the value of N depends on the integrity protection algorithm
in
>    use, i.e., N=160 for HMAC-SHY1.
> 
>    When the PANA_MAC_Key is derived from two AAA-Keys, it is computed
in
>    the following way:
> 
>       PANA_MAC_KEY = The first N bits of
>                      HMAC_SHA1(AAA-Key1 | AAA-Key2, ISN_pac | ISN_paa
|
>                                Session-ID)
> 
>    where AAA-Key1 and AAA-Key2 are AAA-Keys for the first and second
EAP
>    authentication in a single PANA authentication phase, respectively.
> 
>    The length of AAA-Key, AAA-Key1 and AAA-Key2 MUST be N bits or
>    longer.  See Section 4.1.6 for the detailed usage of the
>    PANA_MAC_Key.
> "
> 
> to:
> 
> "
>    The PANA_MAC_Key is used to integrity protect PANA messages.  When
>    the PANA_MAC_Key is derived from a single AAA-Key, it is computed
in
>    the following way:
> 
> 
>       PANA_MAC_KEY = The first N bits of
>                      HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa |
Session-ID)
> 
>    where the value of N depends on the integrity protection algorithm
>    in use, i.e., N=160 for HMAC-SHA1.  The length of AAA-Key MUST be N
>    bits or longer.  See Section 4.1.6 for the detailed usage of the
>    PANA_MAC_KEY.
> "


I think this is where we should discuss how two AAA-Keys are combined. 
For example:

	When two AAA-Keys (AAA-Key1 and AAA-Key2) are generated as a 
      result of double EAP authentication (see Section 4.3), the 
      compound AAA-Key can be computed as follows:

	AAA-Key = AAA-Key1 | AAA-Key2

      The PANA_MAC_Key is used to integrity protect PANA messages.
  
         PANA_MAC_KEY = The first N bits of
                        HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa |
Session-ID)
  
      where the value of N depends on the integrity protection algorithm
      in use, i.e., N=160 for HMAC-SHA1.  The length of AAA-Key MUST be
N
      bits or longer.  See Section 4.1.6 for the detailed usage of the
      PANA_MAC_KEY.

> 
> [3] In section 4.3,
> 
> change:
> 
> "
>    When separate NAP and ISP authentications are performed and the
>    lower-layer is insecure, the two EAP methods MUST be capable of
>    deriving keys.  In this case, if the first EAP authentication is
>    successful, the PANA-FirstAuth-End-Request and
>    PANA-FirstAuth-End-Answer messages as well as PANA-Auth-Request and
>    PANA-Auth-Answer messages in the second EAP authentication MUST be
>    protected with the key derived from the AAA-Key for the first EAP
>    authentication. The PANA-Bind-Request and PANA-Bind-Answer messages
>    and all subsequent PANA messages MUST be protected either with the
>    AAA-Key for the first EAP authentication if the first EAP
>    authentication succeeds and the second EAP authentication fails, or
>    with the AAA-Key for the second EAP authentication if the first EAP
>    authentication fails and the second EAP authentication succeeds, or
>    with the compound key derived from the two AAA-Keys, one for the
>    first EAP authentication and the other from the second EAP
>    authentication, if both the first and second EAP authentications
>    succeed (see Section 4.1.5 for how the compound key is derived).
> "
> 
> to:
> 
> "
>    When separate NAP and ISP authentications are performed and the
>    lower-layer is insecure, the two EAP methods MUST be capable of
>    deriving keys.  In this case, if the first EAP authentication is
>    successful, the PANA-FirstAuth-End-Request and
>    PANA-FirstAuth-End-Answer messages as well as PANA-Auth-Request and
>    PANA-Auth-Answer messages in the second EAP authentication MUST be
>    protected with the key derived from the AAA-Key for the first EAP
>    authentication.  The PANA-Bind-Request and PANA-Bind-Answer
>    messages and all subsequent PANA messages MUST be protected either
>    with the AAA-Key for the first EAP authentication if the first EAP
>    authentication succeeds and the second EAP authentication fails, or
>    with the AAA-Key for the second EAP authentication if the first EAP
>    authentication fails and the second EAP authentication succeeds, or
>    with the compound AAA-Key derived from the two AAA-Keys, one for
the
>    first EAP authentication and the other from the second EAP
>    authentication, if both the first and second EAP authentications
>    succeed.
> "
> 
> [4] In section 4.9,
> 
> change:
> 
> "
>    As part of the context transfer, an intermediate AAA-Key material
is
>    provided by the previous PAA to the current PAA.
> 
>       AAA-Key-int = The first N bits of
>                     HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
> 
>    In case there are two AAA-Keys generated from a NAP-ISP
>    authentication, the AAA-Key-int computation is:
> 
>       AAA-Key-int = The first N bits of
>                     HMAC-SHA1(AAA-Key1 | AAA-Key2, DiameterIdentity |
>                               Session-ID)
> "
> 
> to:
> 
> "
>    As part of the context transfer, an intermediate AAA-Key material
is
>    provided by the previous PAA to the current PAA.
> 
>       AAA-Key-int = The first N bits of
>                     HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
> "


Alper



> 
> Regards,
> 
> Yoshihiro Ohba
> 
> 
> On Tue, Jun 29, 2004 at 03:56:22PM -0700, Alper Yegin wrote:
> > Yoshi,
> >
> > I understand these changes are proposed to have combine AAA keys
when
> > there are two of them. Couldn't we achieve the same by stating:
> >
> > "AAA-key is set to (AAA-Key1 | AAA-Key2) when there are two EAP
runs."
> >
> > This could help collapse the two separate calculations into one in
the
> > pana-pana draft. Also what pana-ipsec refers to would still be
valid.
> > And we wouldn't need to compute a new key and use prf+
(simplification).
> >
> > What do you think?
> >
> > Alper
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On
Behalf
> > Of
> > > Yoshihiro Ohba
> > > Sent: Tuesday, June 22, 2004 8:40 AM
> > > To: pana@ietf.org
> > > Subject: [Pana] PANA key derivation key
> > >
> > > To reflect Pasi's comment on how to deal with two AAA-Keys in
> > > pana-ipsec draft and resulting discussions, here is a proposed
text
> > > for PANA specification draft to define PANA_KD_Key.
> > >
> > > In section 4.1.5 of draft-ietf-pana-pana-04.txt,
> > >
> > > change:
> > >
> > > "
> > >       *  PANA SA attributes:
> > >
> > >          +  AAA-Key
> > >
> > >          +  AAA-Key Identifier
> > >
> > >          +  PANA_MAC_Key
> > >
> > >    The PANA_MAC_Key is used to integrity protect PANA messages.
When
> > >    the PANA_MAC_Key is derived from a single AAA-Key, it is
computed
> > in
> > >    the following way:
> > >
> > >
> > >       PANA_MAC_KEY = The first N bits of
> > >                      HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa |
> > Session-ID)
> > >
> > >    where the value of N depends on the integrity protection
algorithm
> > in
> > >    use, i.e., N=160 for HMAC-SHA1.
> > >
> > >    When the PANA_MAC_Key is derived from two AAA-Keys, it is
computed
> > in
> > >    the following way:
> > >
> > >       PANA_MAC_KEY = The first N bits of
> > >                      HMAC_SHA1(AAA-Key1 | AAA-Key2, ISN_pac |
ISN_paa
> > |
> > >                                Session-ID)
> > >
> > >    where AAA-Key1 and AAA-Key2 are AAA-Keys for the first and
second
> > EAP
> > >    authentication in a single PANA authentication phase,
respectively.
> > >
> > >    The length of AAA-Key, AAA-Key1 and AAA-Key2 MUST be N bits or
> > >    longer.  See Section 4.1.6 for the detailed usage of the
> > >    PANA_MAC_Key.
> > > "
> > >
> > > to:
> > >
> > >       *  PANA SA attributes:
> > >
> > >          +  AAA-Key
> > >
> > >          +  AAA-Key Identifier
> > >
> > >          +  PANA_MAC_Key
> > >
> > >          +  PANA_KD_Key
> > >
> > >    The PANA_MAC_Key is used to integrity protect PANA messages.
The
> > >    PANA_KD_Key is used to derive keys used for bootstrapping
> > >    per-packet ciphering between PaC and EP.  The PANA_MAC_Key has
a
> > >    length of N bits, where the value of N depends on the integrity
> > >    protection algorithm in use, which is HMAC-SHA1 in this
document
> > >    and N would be 160 bits for this case.  The PANA_KD_Key has a
> > >    length of 512 bits, which is equal to the typical length of a
> > >    AAA-Key or an EAP Master Session Key [I-D.ietf-eap-keying].
> > >
> > >    When the PANA_MAC_Key and PANA_PD_Key are derived from a single
> > >    AAA-Key, it is computed in the following way:
> > >
> > >       {PANA_MAC_Key | PANA_KD_Key} =
> > >             HMAC_SHA1+(AAA-Key, ISN_pac | ISN_paa | Session-ID)
> > >
> > >    When PANA_MAC_Key and PANA_PD_Key are derived from two
AAA-Keys, it
> > >    is computed in the following way:
> > >
> > >       {PANA_MAC_Key | PANA_KD_Key} =
> > >             HMAC_SHA1+(AAA-Key1 | AAA-Key2, ISN_pac | ISN_paa |
> > Session-
> > > ID)
> > >
> > >    In the above key derivation algorithms, HMAC_SHA1+ is the
> > >    iteratively calculated version of HMAC_SHA1 algorithm by
applying
> > >    HMAC_SHA1 in the prf+ function defined in IKEv2
> > >    [I-D:ietf-ipsec-ikev2].  AAA-Key1 and AAA-Key2 are AAA-Keys for
the
> > >    first and second EAP authentication in a single PANA
authentication
> > >    phase, respectively.  The length of AAA-Key, AAA-Key1 and
AAA-Key2
> > >    MUST be 160 bits or longer.  See Section 4.1.6 for the detailed
> > >    usage of the PANA_MAC_Key.  See [I-D:ietf-pana-ipsec] for the
usage
> > >    of the PANA_KD_Key for bootstrapping IPsec between PaC and EP.
> > > "
> > >
> > > Regards,
> > >
> > > Yoshihiro Ohba
> > >
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> >
> >
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 21:36:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10655
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 21:36:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkAwJ-0005l4-7n; Mon, 12 Jul 2004 20:14:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk9GE-000347-TM
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 18:26:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24254
	for <pana@ietf.org>; Mon, 12 Jul 2004 18:26:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bk9GD-0006lo-Gm
	for pana@ietf.org; Mon, 12 Jul 2004 18:26:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk9FK-0006Sd-00
	for pana@ietf.org; Mon, 12 Jul 2004 18:26:03 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12) id 1Bk9EH-0005tV-00
	for pana@ietf.org; Mon, 12 Jul 2004 18:24:58 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0R00I08FKIN6@mailout3.samsung.com> for pana@ietf.org; Tue,
	13 Jul 2004 07:24:18 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0R00LV1FKI52@mailout3.samsung.com> for pana@ietf.org;
	Tue, 13 Jul 2004 07:24:18 +0900 (KST)
Received: from Alperyegin ([105.253.155.20])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0R001ZPFKFFH@mmp1.samsung.com> for
	pana@ietf.org; Tue, 13 Jul 2004 07:24:18 +0900 (KST)
Date: Mon, 12 Jul 2004 15:24:19 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] NEW: [issue100] PSR and PSA sequence number clarification
In-reply-to: <20040705170231.GE17360@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <00c301c4685e$fb5ce440$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: Dan.Forsberg@nokia.com
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


I'm trying to see if we can solve this problem without creating
exceptions to the sequencing scheme.....

As I understand, relying on the ISNs has an issue when PaC and PAA
retransmit the messages and any one of the last x sequences (n through
n-x+1) might have been accepted by the PAA as the ISN. Right?

Can we solve this problem by carrying Nonce values in PSR and PSA, and
using them with the PANA_MAC_KEY computation instead of ISNs?

Alper



> -----Original Message-----
> From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf
Of
> Yoshihiro Ohba
> Sent: Monday, July 05, 2004 10:03 AM
> To: pana@ietf.org
> Cc: Dan.Forsberg@nokia.com
> Subject: Re: [Pana] NEW: [issue100] PSR and PSA sequence number
> clarification
> 
> Here is a proposed text.
> 
> In section 4.1.4,
> 
> change:
> 
> "
>    The two sequence number fields have the same length of 32 bits and
>    appear in PANA header.  tseq starts from initial sequence number
>    (ISN) and is monotonically increased by 1. The serial number
>    arithmetic defined in [RFC1982] is used for sequence number
>    operation. The ISNs are exchanged between PaC and PAA during the
>    discovery and initial handshake phase (see Section 4.2). The rules
>    that govern the sequence numbers in other phases are described as
>    follows.
> "
> 
> to:
> 
> "
>    The two sequence number fields have the same length of 32 bits and
>    appear in PANA header.  The transmission sequence number starts
>    from initial sequence number (ISN) and is monotonically increased
>    by 1. The serial number arithmetic defined in [RFC1982] is used for
>    sequence number operation. The ISNs are exchanged between PaC and
>    PAA during the discovery and initial handshake phase (see Section
>    4.2).  The transmission sequence number is never incremented in the
>    messages exchanged during discovery and initial handshake phase.
>    The rules that govern the sequence numbers in other phases are
>    described as follows.
> "
> 
> Regards,
> 
> Yoshihiro Ohba
> 
> 
> On Fri, Jul 02, 2004 at 09:09:47AM +0300, Dan.Forsberg@nokia.com
wrote:
> > New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> >
> > > >- When a PaC sends a PANA-Start-Answer message in response to a
valid
> > > >PANA-Start-Request message without a Cookie AVP, the answer
message
> > > >can be lost.  The PANA-Start-Request would be retransmitted.  To
deal
> > > >with the case, it might be better for the PaC to return a
duplicate
> > > >PANA-Start-Answer message after the PaC has been sent the first
> > > >PANA-Start-Answer message until the PaC receives a valid
> > > >PANA-Auth-Request message.
> > > >
> > > >
> > > In this case, I guess PANA-Start-Request would be retransmitted by
> > > updating transmission sequence number , and PANA-Start-Request by
> > > udpating transmission and received sequence numbers). That is:
> > >
> > > PaC PAA
> > >
> > > PSR(x,0)
> > > <---------------------
> > > PSA(y,x)
> > > ---------X--------->
> > > PSR(x+1,0)
> > > <-------------------
> > > PSA(y+1,x+1)
> > > ------------------->
> > >
> > > Am I wrong?
> >
> > With incrementing the transmission sequence numbers in PSR and PSA
> > before the two entities complete initial sequence number
negotiation,
> > it is possible to fail to share the same pair of initial sequence
> > numbers between PaC and PAA.  So sequence numbers should not be
> > incremented in PSR and PSA.  I think section 4.1.4 should be more
> > specific on this.
> >
> > Yoshihiro Ohba
> >
> > ----------
> > category: Editorial
> > document: draft-ietf-pana-pana-xx.txt
> > messages: 337
> > nosy: dforsber
> > priority: Should Fix
> > status: Pending
> > title: PSR and PSA sequence number clarification
> > ___________________________________________________
> > PANA Issues <pana_issues@danforsberg.info>
> > <http://danforsberg.info:8080/pana-issues/issue100>
> > ___________________________________________________
> 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 21:36:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10816
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 21:36:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkAwU-00065e-0Z; Mon, 12 Jul 2004 20:14:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk9MJ-0003ta-S2
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 18:33:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24931
	for <pana@ietf.org>; Mon, 12 Jul 2004 18:33:12 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bk9MI-0000ax-8d
	for pana@ietf.org; Mon, 12 Jul 2004 18:33:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk9KH-0000Aq-00
	for pana@ietf.org; Mon, 12 Jul 2004 18:31:11 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bk9Hy-00078h-00
	for pana@ietf.org; Mon, 12 Jul 2004 18:28:47 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6CMSepD018847;
	Tue, 13 Jul 2004 07:28:40 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6CMSeAp011964;
	Tue, 13 Jul 2004 07:28:40 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	HAA11962 ; Tue, 13 Jul 2004 07:28:40 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA02665; Tue, 13 Jul 2004 07:28:39 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA15600;
	Tue, 13 Jul 2004 07:28:38 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6CMScpl014591;
	Tue, 13 Jul 2004 07:28:38 +0900 (JST)
Received: from steelhead (iVPN01-121.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0R00BSQFROS4@tsbpo1.po.toshiba.co.jp>; Tue,
	13 Jul 2004 07:28:37 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bk9Gz-0002X2-00; Mon, 12 Jul 2004 15:27:45 -0700
Date: Mon, 12 Jul 2004 18:27:45 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Mobility Handling in PANA
In-reply-to: <20040712143702.GA45745@ipv6-5.int-evry.fr>
To: Julien Bournelle <Julien.Bournelle@int-evry.fr>
Message-id: <20040712222745.GA893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Julien Bournelle <Julien.Bournelle@int-evry.fr>,
	yohba@tari.toshiba.com, pana@ietf.org,
	Gerardo Giaretta <gerardo.giaretta@tilab.com>
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
	<20040710062738.GD893@steelhead>
	<20040712101804.GF44906@ipv6-5.int-evry.fr>
	<20040712111907.GT893@steelhead>
	<20040712113752.GJ44906@ipv6-5.int-evry.fr>
	<20040712123404.GX893@steelhead>
	<20040712143702.GA45745@ipv6-5.int-evry.fr>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Gerardo Giaretta <gerardo.giaretta@tilab.com>, yohba@tari.toshiba.com,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Julien,

I just meant "not piggybacking other protocol messages" by modularity.
I think both non-piggybacking and piggybacking schemes should be
allowed in the design.  Non-piggybacking scheme allows other mobility
optimization schemes also to be used by PANA, while piggybacking
scheme provides optimization for a particular mobility optimization
scheme.

Yoshihiro Ohba


On Mon, Jul 12, 2004 at 04:37:02PM +0200, Julien Bournelle wrote:
> > Since PANA and CTP are different protocols, I think nPAA can wait for
> > messages from both protocols at the same time without violating both
> > protocols.  But parhaps it is better in this case that CTAR is
> > acknowledged with CTAA and the PaC sends PSA after receiving CTAA to
> > provide synchronization bewteen context transfer operation and PANA
> > mobility optimization, something like:
> > 
> > PaC           nPAA              pPAA
> > ----------------------------------------
> >       PDI
> >  -------------->
> >       PSR
> >  <---------------
> >       CTAR
> >  --------------->
> >                      CT-Request 
> >                   -------------->
> >                          CTD 
> >                   <--------------
> >       CTAA
> >  <--------------
> > 
> >   PSA[old Session-ID, Nonce, MAC]
> >   --------------->
> >   PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> >   <-------------
> >   PBA[new Session-ID, Key-Id, PPAC, MAC]
> >   ------------->
> > 
> > Comparing this scheme with your scheme below, the discussion point
> > would be modularity (this sheme) vs optimization (your scheme).
> 
> I think that with our solution we keep the modularity since the pana
> module asks to the ctp module the CTAR message to be sent.
> 
> In your scenario, the PANA module at PaC receives the PSR message and
> contacts the CTP module (saying that CTP module must sent a CTAR).
> In our scenario, the PANA module asks to the CTP module the CTAR
> message and embeds it. Thus I think that we keep the modularity.
> 
> Maybe I miss something, what do you mean by modularity ?
> 
> > 
> > Yoshihiro Ohba
> > 
> > > 
> > > This is why we propose to emebed the CTAR message in the PSR message.
> > > Thus the pac answers with a PSA message. The PANA module at the pac aks
> > > to the CTP module to get a valid CTAR message and embeds it in the PSA
> > > message. The nPAA receives the PSA message that it is waiting for and
> > > sees that it contains a CTAR message. It delivers it to its CTP module
> > > and waits the CT-Request/CTD exchange. This why we introduce a new state
> > > in the state machine (PANA-CTP-WAITING)
> > > 
> > > 
> > > Thus we propose this:
> > > 
> > > 
> > >      PaC           nPAA              pPAA
> > >      ----------------------------------------
> > >            PDI
> > >       -------------->
> > >            PSR
> > >      <---------------
> > >           PSA [old Session-ID, Nonce, CTAR] 
> > >       --------------->
> > >  
> > >                            CT-Request 
> > >                         -------------->
> > >                                CTD 
> > >                         <--------------
> > > 
> > >       PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> > >      <-------------
> > >       PBA[new Session-ID, Key-Id, PPAC, MAC]
> > >       ------------->
> > > 
> > > 
> > > 
> > > 
> > > -- 
> > > julien.bournelle@int-evry.fr
> > 
> 
> -- 
> julien.bournelle@int-evry.fr
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 21:40:31 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11229
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 21:40:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkAxp-00087K-Ia; Mon, 12 Jul 2004 20:16:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bk9yu-0003yk-S6
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 19:13:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29281
	for <pana@ietf.org>; Mon, 12 Jul 2004 19:13:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bk9yt-00062I-9a
	for pana@ietf.org; Mon, 12 Jul 2004 19:13:07 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bk9vG-0004wQ-00
	for pana@ietf.org; Mon, 12 Jul 2004 19:09:23 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bk9t4-0004FS-00
	for pana@ietf.org; Mon, 12 Jul 2004 19:07:06 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6CN72pD001393;
	Tue, 13 Jul 2004 08:07:02 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6CN72vW027879;
	Tue, 13 Jul 2004 08:07:02 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	JAA27878 ; Tue, 13 Jul 2004 08:07:01 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA14185; Tue, 13 Jul 2004 08:07:01 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA06087;
	Tue, 13 Jul 2004 08:07:01 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6CN70pl002028;
	Tue, 13 Jul 2004 08:07:00 +0900 (JST)
Received: from steelhead (iVPN01-121.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0R00EU4HJMJR@tsbpo1.po.toshiba.co.jp>; Tue,
	13 Jul 2004 08:07:00 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bk9rd-0002g9-00; Mon, 12 Jul 2004 16:05:37 -0700
Date: Mon, 12 Jul 2004 19:05:37 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] NEW: [issue100] PSR and PSA sequence number clarification
In-reply-to: <00c301c4685e$fb5ce440$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040712230537.GB893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org,
	Dan.Forsberg@nokia.com
User-Agent: Mutt/1.5.6+20040523i
References: <20040705170231.GE17360@steelhead>
	<00c301c4685e$fb5ce440$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Using Nonce values (which can be more than 32-bits) for PANA_MAC_KEY
computation instead of using ISNs (32-bit random values) provides
better randomness and probably a good thing.  This makes tseq in PSR
and PSA incrementable as other PANA messages (except for PDI).

This works for me.  Perhaps the minimum and the maximum lengthes for a
Nonce value might need to be defined.

Yoshihiro Ohba


On Mon, Jul 12, 2004 at 03:24:19PM -0700, Alper Yegin wrote:
> 
> I'm trying to see if we can solve this problem without creating
> exceptions to the sequencing scheme.....
> 
> As I understand, relying on the ISNs has an issue when PaC and PAA
> retransmit the messages and any one of the last x sequences (n through
> n-x+1) might have been accepted by the PAA as the ISN. Right?
> 
> Can we solve this problem by carrying Nonce values in PSR and PSA, and
> using them with the PANA_MAC_KEY computation instead of ISNs?
> 
> Alper
> 
> 
> 
> > -----Original Message-----
> > From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf
> Of
> > Yoshihiro Ohba
> > Sent: Monday, July 05, 2004 10:03 AM
> > To: pana@ietf.org
> > Cc: Dan.Forsberg@nokia.com
> > Subject: Re: [Pana] NEW: [issue100] PSR and PSA sequence number
> > clarification
> > 
> > Here is a proposed text.
> > 
> > In section 4.1.4,
> > 
> > change:
> > 
> > "
> >    The two sequence number fields have the same length of 32 bits and
> >    appear in PANA header.  tseq starts from initial sequence number
> >    (ISN) and is monotonically increased by 1. The serial number
> >    arithmetic defined in [RFC1982] is used for sequence number
> >    operation. The ISNs are exchanged between PaC and PAA during the
> >    discovery and initial handshake phase (see Section 4.2). The rules
> >    that govern the sequence numbers in other phases are described as
> >    follows.
> > "
> > 
> > to:
> > 
> > "
> >    The two sequence number fields have the same length of 32 bits and
> >    appear in PANA header.  The transmission sequence number starts
> >    from initial sequence number (ISN) and is monotonically increased
> >    by 1. The serial number arithmetic defined in [RFC1982] is used for
> >    sequence number operation. The ISNs are exchanged between PaC and
> >    PAA during the discovery and initial handshake phase (see Section
> >    4.2).  The transmission sequence number is never incremented in the
> >    messages exchanged during discovery and initial handshake phase.
> >    The rules that govern the sequence numbers in other phases are
> >    described as follows.
> > "
> > 
> > Regards,
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Fri, Jul 02, 2004 at 09:09:47AM +0300, Dan.Forsberg@nokia.com
> wrote:
> > > New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> > >
> > > > >- When a PaC sends a PANA-Start-Answer message in response to a
> valid
> > > > >PANA-Start-Request message without a Cookie AVP, the answer
> message
> > > > >can be lost.  The PANA-Start-Request would be retransmitted.  To
> deal
> > > > >with the case, it might be better for the PaC to return a
> duplicate
> > > > >PANA-Start-Answer message after the PaC has been sent the first
> > > > >PANA-Start-Answer message until the PaC receives a valid
> > > > >PANA-Auth-Request message.
> > > > >
> > > > >
> > > > In this case, I guess PANA-Start-Request would be retransmitted by
> > > > updating transmission sequence number , and PANA-Start-Request by
> > > > udpating transmission and received sequence numbers). That is:
> > > >
> > > > PaC PAA
> > > >
> > > > PSR(x,0)
> > > > <---------------------
> > > > PSA(y,x)
> > > > ---------X--------->
> > > > PSR(x+1,0)
> > > > <-------------------
> > > > PSA(y+1,x+1)
> > > > ------------------->
> > > >
> > > > Am I wrong?
> > >
> > > With incrementing the transmission sequence numbers in PSR and PSA
> > > before the two entities complete initial sequence number
> negotiation,
> > > it is possible to fail to share the same pair of initial sequence
> > > numbers between PaC and PAA.  So sequence numbers should not be
> > > incremented in PSR and PSA.  I think section 4.1.4 should be more
> > > specific on this.
> > >
> > > Yoshihiro Ohba
> > >
> > > ----------
> > > category: Editorial
> > > document: draft-ietf-pana-pana-xx.txt
> > > messages: 337
> > > nosy: dforsber
> > > priority: Should Fix
> > > status: Pending
> > > title: PSR and PSA sequence number clarification
> > > ___________________________________________________
> > > PANA Issues <pana_issues@danforsberg.info>
> > > <http://danforsberg.info:8080/pana-issues/issue100>
> > > ___________________________________________________
> > 
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > 
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 21:48:42 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12107
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 21:48:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkB8z-00034c-Kj; Mon, 12 Jul 2004 20:27:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkAJp-0000WB-Id
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 19:34:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02223
	for <pana@ietf.org>; Mon, 12 Jul 2004 19:34:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkAJo-0003pH-2x
	for pana@ietf.org; Mon, 12 Jul 2004 19:34:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkAHY-00036v-00
	for pana@ietf.org; Mon, 12 Jul 2004 19:32:25 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BkAEh-0002Uv-00
	for pana@ietf.org; Mon, 12 Jul 2004 19:29:27 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6CNTQpD011735;
	Tue, 13 Jul 2004 08:29:26 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6CNTQE6013993;
	Tue, 13 Jul 2004 08:29:26 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	JAA13990 ; Tue, 13 Jul 2004 08:29:26 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA25318; Tue, 13 Jul 2004 08:29:25 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA00274;
	Tue, 13 Jul 2004 08:29:24 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6CNTOpl012972;
	Tue, 13 Jul 2004 08:29:24 +0900 (JST)
Received: from steelhead (iVPN01-121.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0R00G0YIKYX6@tsbpo1.po.toshiba.co.jp>; Tue,
	13 Jul 2004 08:29:23 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BkAE6-0002m1-00; Mon, 12 Jul 2004 16:28:50 -0700
Date: Mon, 12 Jul 2004 19:28:50 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] PANA key derivation key
In-reply-to: <009301c46857$9e412750$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040712232850.GC893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040705164928.GD17360@steelhead>
	<009301c46857$9e412750$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

This looks good.

Yoshihiro Ohba

On Mon, Jul 12, 2004 at 02:31:37PM -0700, Alper Yegin wrote:
> Hi Yoshi,
> 
> > [1] In section 2,
> > 
> > change:
> > 
> > "
> >    AAA-Key:
> > 
> >       A key derived by the EAP peer and EAP server and transported to
> >       the authenticator [I-D.ietf-eap-keying].
> > "
> > 
> > to:
> > 
> > "
> >    AAA-Key:
> > 
> >       A key derived by the EAP peer and EAP server and transported to
> >       the authenticator [I-D.ietf-eap-keying].  In this document, when
> >       there are two such keys, namely AAA-Key1 and AAA-Key2, are
> >       generated as a result of running two EAP authentications in a
> >       single round of PANA authentication, the AAA-Key from
> >       which other keys are derived refers to the concatenation of
> >       AAA-Key1 and AAA-Key2.
> > "
> 
> 
> I think it is better if we didn't get into the specific AAA-keys and
> computations in the terminology. I think we should keep the terminology
> section as is, and later discuss how AAA-Key may be set to
> AAA-Key1|AAA-Key2.
> 
> 
> > 
> > 
> > [2] In section 4.1.5 of draft-ietf-pana-pana-04.txt change:
> > 
> > 
> > "
> >    The PANA_MAC_Key is used to integrity protect PANA messages.  When
> >    the PANA_MAC_Key is derived from a single AAA-Key, it is computed
> in
> >    the following way:
> > 
> > 
> >       PANA_MAC_KEY = The first N bits of
> >                      HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa |
> Session-ID)
> > 
> >    where the value of N depends on the integrity protection algorithm
> in
> >    use, i.e., N=160 for HMAC-SHY1.
> > 
> >    When the PANA_MAC_Key is derived from two AAA-Keys, it is computed
> in
> >    the following way:
> > 
> >       PANA_MAC_KEY = The first N bits of
> >                      HMAC_SHA1(AAA-Key1 | AAA-Key2, ISN_pac | ISN_paa
> |
> >                                Session-ID)
> > 
> >    where AAA-Key1 and AAA-Key2 are AAA-Keys for the first and second
> EAP
> >    authentication in a single PANA authentication phase, respectively.
> > 
> >    The length of AAA-Key, AAA-Key1 and AAA-Key2 MUST be N bits or
> >    longer.  See Section 4.1.6 for the detailed usage of the
> >    PANA_MAC_Key.
> > "
> > 
> > to:
> > 
> > "
> >    The PANA_MAC_Key is used to integrity protect PANA messages.  When
> >    the PANA_MAC_Key is derived from a single AAA-Key, it is computed
> in
> >    the following way:
> > 
> > 
> >       PANA_MAC_KEY = The first N bits of
> >                      HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa |
> Session-ID)
> > 
> >    where the value of N depends on the integrity protection algorithm
> >    in use, i.e., N=160 for HMAC-SHA1.  The length of AAA-Key MUST be N
> >    bits or longer.  See Section 4.1.6 for the detailed usage of the
> >    PANA_MAC_KEY.
> > "
> 
> 
> I think this is where we should discuss how two AAA-Keys are combined. 
> For example:
> 
> 	When two AAA-Keys (AAA-Key1 and AAA-Key2) are generated as a 
>       result of double EAP authentication (see Section 4.3), the 
>       compound AAA-Key can be computed as follows:
> 
> 	AAA-Key = AAA-Key1 | AAA-Key2
> 
>       The PANA_MAC_Key is used to integrity protect PANA messages.
>   
>          PANA_MAC_KEY = The first N bits of
>                         HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa |
> Session-ID)
>   
>       where the value of N depends on the integrity protection algorithm
>       in use, i.e., N=160 for HMAC-SHA1.  The length of AAA-Key MUST be
> N
>       bits or longer.  See Section 4.1.6 for the detailed usage of the
>       PANA_MAC_KEY.
> 
> > 
> > [3] In section 4.3,
> > 
> > change:
> > 
> > "
> >    When separate NAP and ISP authentications are performed and the
> >    lower-layer is insecure, the two EAP methods MUST be capable of
> >    deriving keys.  In this case, if the first EAP authentication is
> >    successful, the PANA-FirstAuth-End-Request and
> >    PANA-FirstAuth-End-Answer messages as well as PANA-Auth-Request and
> >    PANA-Auth-Answer messages in the second EAP authentication MUST be
> >    protected with the key derived from the AAA-Key for the first EAP
> >    authentication. The PANA-Bind-Request and PANA-Bind-Answer messages
> >    and all subsequent PANA messages MUST be protected either with the
> >    AAA-Key for the first EAP authentication if the first EAP
> >    authentication succeeds and the second EAP authentication fails, or
> >    with the AAA-Key for the second EAP authentication if the first EAP
> >    authentication fails and the second EAP authentication succeeds, or
> >    with the compound key derived from the two AAA-Keys, one for the
> >    first EAP authentication and the other from the second EAP
> >    authentication, if both the first and second EAP authentications
> >    succeed (see Section 4.1.5 for how the compound key is derived).
> > "
> > 
> > to:
> > 
> > "
> >    When separate NAP and ISP authentications are performed and the
> >    lower-layer is insecure, the two EAP methods MUST be capable of
> >    deriving keys.  In this case, if the first EAP authentication is
> >    successful, the PANA-FirstAuth-End-Request and
> >    PANA-FirstAuth-End-Answer messages as well as PANA-Auth-Request and
> >    PANA-Auth-Answer messages in the second EAP authentication MUST be
> >    protected with the key derived from the AAA-Key for the first EAP
> >    authentication.  The PANA-Bind-Request and PANA-Bind-Answer
> >    messages and all subsequent PANA messages MUST be protected either
> >    with the AAA-Key for the first EAP authentication if the first EAP
> >    authentication succeeds and the second EAP authentication fails, or
> >    with the AAA-Key for the second EAP authentication if the first EAP
> >    authentication fails and the second EAP authentication succeeds, or
> >    with the compound AAA-Key derived from the two AAA-Keys, one for
> the
> >    first EAP authentication and the other from the second EAP
> >    authentication, if both the first and second EAP authentications
> >    succeed.
> > "
> > 
> > [4] In section 4.9,
> > 
> > change:
> > 
> > "
> >    As part of the context transfer, an intermediate AAA-Key material
> is
> >    provided by the previous PAA to the current PAA.
> > 
> >       AAA-Key-int = The first N bits of
> >                     HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
> > 
> >    In case there are two AAA-Keys generated from a NAP-ISP
> >    authentication, the AAA-Key-int computation is:
> > 
> >       AAA-Key-int = The first N bits of
> >                     HMAC-SHA1(AAA-Key1 | AAA-Key2, DiameterIdentity |
> >                               Session-ID)
> > "
> > 
> > to:
> > 
> > "
> >    As part of the context transfer, an intermediate AAA-Key material
> is
> >    provided by the previous PAA to the current PAA.
> > 
> >       AAA-Key-int = The first N bits of
> >                     HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
> > "
> 
> 
> Alper
> 
> 
> 
> > 
> > Regards,
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Tue, Jun 29, 2004 at 03:56:22PM -0700, Alper Yegin wrote:
> > > Yoshi,
> > >
> > > I understand these changes are proposed to have combine AAA keys
> when
> > > there are two of them. Couldn't we achieve the same by stating:
> > >
> > > "AAA-key is set to (AAA-Key1 | AAA-Key2) when there are two EAP
> runs."
> > >
> > > This could help collapse the two separate calculations into one in
> the
> > > pana-pana draft. Also what pana-ipsec refers to would still be
> valid.
> > > And we wouldn't need to compute a new key and use prf+
> (simplification).
> > >
> > > What do you think?
> > >
> > > Alper
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On
> Behalf
> > > Of
> > > > Yoshihiro Ohba
> > > > Sent: Tuesday, June 22, 2004 8:40 AM
> > > > To: pana@ietf.org
> > > > Subject: [Pana] PANA key derivation key
> > > >
> > > > To reflect Pasi's comment on how to deal with two AAA-Keys in
> > > > pana-ipsec draft and resulting discussions, here is a proposed
> text
> > > > for PANA specification draft to define PANA_KD_Key.
> > > >
> > > > In section 4.1.5 of draft-ietf-pana-pana-04.txt,
> > > >
> > > > change:
> > > >
> > > > "
> > > >       *  PANA SA attributes:
> > > >
> > > >          +  AAA-Key
> > > >
> > > >          +  AAA-Key Identifier
> > > >
> > > >          +  PANA_MAC_Key
> > > >
> > > >    The PANA_MAC_Key is used to integrity protect PANA messages.
> When
> > > >    the PANA_MAC_Key is derived from a single AAA-Key, it is
> computed
> > > in
> > > >    the following way:
> > > >
> > > >
> > > >       PANA_MAC_KEY = The first N bits of
> > > >                      HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa |
> > > Session-ID)
> > > >
> > > >    where the value of N depends on the integrity protection
> algorithm
> > > in
> > > >    use, i.e., N=160 for HMAC-SHA1.
> > > >
> > > >    When the PANA_MAC_Key is derived from two AAA-Keys, it is
> computed
> > > in
> > > >    the following way:
> > > >
> > > >       PANA_MAC_KEY = The first N bits of
> > > >                      HMAC_SHA1(AAA-Key1 | AAA-Key2, ISN_pac |
> ISN_paa
> > > |
> > > >                                Session-ID)
> > > >
> > > >    where AAA-Key1 and AAA-Key2 are AAA-Keys for the first and
> second
> > > EAP
> > > >    authentication in a single PANA authentication phase,
> respectively.
> > > >
> > > >    The length of AAA-Key, AAA-Key1 and AAA-Key2 MUST be N bits or
> > > >    longer.  See Section 4.1.6 for the detailed usage of the
> > > >    PANA_MAC_Key.
> > > > "
> > > >
> > > > to:
> > > >
> > > >       *  PANA SA attributes:
> > > >
> > > >          +  AAA-Key
> > > >
> > > >          +  AAA-Key Identifier
> > > >
> > > >          +  PANA_MAC_Key
> > > >
> > > >          +  PANA_KD_Key
> > > >
> > > >    The PANA_MAC_Key is used to integrity protect PANA messages.
> The
> > > >    PANA_KD_Key is used to derive keys used for bootstrapping
> > > >    per-packet ciphering between PaC and EP.  The PANA_MAC_Key has
> a
> > > >    length of N bits, where the value of N depends on the integrity
> > > >    protection algorithm in use, which is HMAC-SHA1 in this
> document
> > > >    and N would be 160 bits for this case.  The PANA_KD_Key has a
> > > >    length of 512 bits, which is equal to the typical length of a
> > > >    AAA-Key or an EAP Master Session Key [I-D.ietf-eap-keying].
> > > >
> > > >    When the PANA_MAC_Key and PANA_PD_Key are derived from a single
> > > >    AAA-Key, it is computed in the following way:
> > > >
> > > >       {PANA_MAC_Key | PANA_KD_Key} =
> > > >             HMAC_SHA1+(AAA-Key, ISN_pac | ISN_paa | Session-ID)
> > > >
> > > >    When PANA_MAC_Key and PANA_PD_Key are derived from two
> AAA-Keys, it
> > > >    is computed in the following way:
> > > >
> > > >       {PANA_MAC_Key | PANA_KD_Key} =
> > > >             HMAC_SHA1+(AAA-Key1 | AAA-Key2, ISN_pac | ISN_paa |
> > > Session-
> > > > ID)
> > > >
> > > >    In the above key derivation algorithms, HMAC_SHA1+ is the
> > > >    iteratively calculated version of HMAC_SHA1 algorithm by
> applying
> > > >    HMAC_SHA1 in the prf+ function defined in IKEv2
> > > >    [I-D:ietf-ipsec-ikev2].  AAA-Key1 and AAA-Key2 are AAA-Keys for
> the
> > > >    first and second EAP authentication in a single PANA
> authentication
> > > >    phase, respectively.  The length of AAA-Key, AAA-Key1 and
> AAA-Key2
> > > >    MUST be 160 bits or longer.  See Section 4.1.6 for the detailed
> > > >    usage of the PANA_MAC_Key.  See [I-D:ietf-pana-ipsec] for the
> usage
> > > >    of the PANA_KD_Key for bootstrapping IPsec between PaC and EP.
> > > > "
> > > >
> > > > Regards,
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > > _______________________________________________
> > > > Pana mailing list
> > > > Pana@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pana
> > >
> > >
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 21:52:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12277
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 21:52:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkBhi-0006XK-V4; Mon, 12 Jul 2004 21:03:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkAbM-0003S2-TV
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 19:52:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03003
	for <pana@ietf.org>; Mon, 12 Jul 2004 19:52:50 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkAbK-0000VS-RS
	for pana@ietf.org; Mon, 12 Jul 2004 19:52:50 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkAaP-0000HF-00
	for pana@ietf.org; Mon, 12 Jul 2004 19:51:54 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12) id 1BkAa9-00002Z-00
	for pana@ietf.org; Mon, 12 Jul 2004 19:51:37 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0R00N91JL01T@mailout3.samsung.com> for pana@ietf.org; Tue,
	13 Jul 2004 08:51:00 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0R00HXBJI7FG@mailout3.samsung.com> for pana@ietf.org;
	Tue, 13 Jul 2004 08:49:19 +0900 (KST)
Received: from Alperyegin ([105.253.155.20])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0R00E6BJI3GC@mmp1.samsung.com> for
	pana@ietf.org; Tue, 13 Jul 2004 08:49:19 +0900 (KST)
Date: Mon, 12 Jul 2004 16:49:20 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] New: [issue98] Lost answer problem
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA02236278@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com, pana@ietf.org
Message-id: <01a401c4686a$db8f7310$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


I'm trying to understand the issue...

> From Yoshihiro Ohba:
> --------------------
> There might be some cases in which a PaC or a PAA might need to send a
> duplicate answer to a retransmitted old request (as well as a fresh
> answer to a new request if any) considering that an answer message for
> an old request can be lost.  Without this, a PANA session may stall in
> a way that the requester keeps retransmitting the old request while
> the responder may keep discarding them with waiting for a new request.

There would not be any discarding due to sequence numbers. I guess the
only problem could be that the PaC has jumped to the next state in the
state machine as soon as it responded to a message, and in that state it
does not expect the same request it had already responded earlier. Is
that the issue?

Alper


 



> The cases are described below.
> 
> - When a PaC sends a PANA-Start-Answer message in response to a valid
> PANA-Start-Request message without a Cookie AVP, the answer message
> can be lost.  The PANA-Start-Request would be retransmitted.  To deal
> with the case, it might be better for the PaC to return a duplicate
> PANA-Start-Answer message after the PaC has been sent the first
> PANA-Start-Answer message until the PaC receives a valid
> PANA-Auth-Request message.
> 
> - When a PaC sends a PANA-FirstAuth-End-Answer message in response to
a
> valid PANA-FirstAuth-End-Request message (remember that a
> PANA-FirstAuth-End exchange is used for delimiting the first and
> second EAP authentications), the answer message may be lost.  The
> PANA-FirstAuth-End-Request would be retransmitted (with updating
> transmission sequence number).  To deal with the case, it might be
> better for the PaC to return a duplicate PANA-FirstAuth-End-Answer
> message (with updating transmission and received sequence numbers)
> after the PaC has been sent the first PANA-FirstAuth-End-Answer
> message until the PaC receives a valid PANA-Auth-Request message for
> the second EAP authentication.
> 
> - When a PaC sends a PANA-Bind-Answer message in response to a valid
> PANA-Bind-Request message, the answer message can be lost.  As as
> result, the PAA will retransmit the PANA-Bind-Request (but with using
> a different transmission sequence number).  To deal with the case, it
> might be better for the PaC to return a duplicate PANA-Bind-Answer
> message (but with using different transmission and received sequence
> numbers) for a while after the first PANA-Bind-Request was received.
> The same thing can also apply to a PANA-Address-Update-Answer message
> that is sent by a PaC.
> 
> - When a PaC or a PAA sends a PANA-Termination-Answer message in
> response to a valid PANA-Termination-Request message, the answer
> message can be lost.  As as result, the requester will retransmit the
> request (but with using a different transmission sequence number).  To
> deal with the case, it might be better for the sender of the answer to
> return a duplicate answer (with using different transmission and
> received sequence numbers) for a while after the first
> PANA-Termination-Request was received.  The same thing can also apply
> to a PANA-Reauth-Answer message that is sent by a PaC or a PAA.
> 
> Those could improve robustness of the PANA protocol against loss of
> answer message.
> 
> Comments?
> 
> Yoshihiro Ohba
> 
> ----------
> category: Technical
> document: draft-ietf-pana-pana-xx.txt
> messages: 335
> nosy: dforsber
> priority: Must Fix
> status: Pending
> title: Lost answer problem
> __________________________________________________
> PANA Issues <pana_issues@danforsberg.info>
> <http://danforsberg.info:8080/pana-issues/issue98>
> __________________________________________________


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 22:33:31 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16520
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 22:33:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkCaJ-00059t-Dm; Mon, 12 Jul 2004 21:59:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkCCT-0006Tb-9F
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 21:35:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10514
	for <pana@ietf.org>; Mon, 12 Jul 2004 21:35:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkCCR-0004ud-Ii
	for pana@ietf.org; Mon, 12 Jul 2004 21:35:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkCBJ-0004Wt-00
	for pana@ietf.org; Mon, 12 Jul 2004 21:34:06 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BkCAI-0004E6-00
	for pana@ietf.org; Mon, 12 Jul 2004 21:33:03 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6D1X2pD019774;
	Tue, 13 Jul 2004 10:33:02 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6D1X1CW026093;
	Tue, 13 Jul 2004 10:33:01 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	LAA26091 ; Tue, 13 Jul 2004 10:33:01 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id KAA13061; Tue, 13 Jul 2004 10:33:01 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id KAA16396;
	Tue, 13 Jul 2004 10:32:56 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6D1Wtpl013855;
	Tue, 13 Jul 2004 10:32:56 +0900 (JST)
Received: from steelhead (iVPN01-080.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0R0090COAUCD@tsbpo1.po.toshiba.co.jp>; Tue,
	13 Jul 2004 10:32:55 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BkC9C-0003Hf-00; Mon, 12 Jul 2004 18:31:54 -0700
Date: Mon, 12 Jul 2004 21:31:54 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New: [issue98] Lost answer problem
In-reply-to: <01a401c4686a$db8f7310$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040713013154.GF893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	Dan.Forsberg@nokia.com, pana@ietf.org,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>
User-Agent: Mutt/1.5.6+20040523i
References: <FC5FF66A769AB044AED651C705EAA8EA02236278@esebe008.ntc.nokia.com>
	<01a401c4686a$db8f7310$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Mon, Jul 12, 2004 at 04:49:20PM -0700, Alper Yegin wrote:
> 
> I'm trying to understand the issue...
> 
> > From Yoshihiro Ohba:
> > --------------------
> > There might be some cases in which a PaC or a PAA might need to send a
> > duplicate answer to a retransmitted old request (as well as a fresh
> > answer to a new request if any) considering that an answer message for
> > an old request can be lost.  Without this, a PANA session may stall in
> > a way that the requester keeps retransmitting the old request while
> > the responder may keep discarding them with waiting for a new request.
> 
> There would not be any discarding due to sequence numbers. I guess the
> only problem could be that the PaC has jumped to the next state in the
> state machine as soon as it responded to a message, and in that state it
> does not expect the same request it had already responded earlier. Is
> that the issue?

Yes.

Yoshihiro Ohba


> 
> Alper
> 
> 
>  
> 
> 
> 
> > The cases are described below.
> > 
> > - When a PaC sends a PANA-Start-Answer message in response to a valid
> > PANA-Start-Request message without a Cookie AVP, the answer message
> > can be lost.  The PANA-Start-Request would be retransmitted.  To deal
> > with the case, it might be better for the PaC to return a duplicate
> > PANA-Start-Answer message after the PaC has been sent the first
> > PANA-Start-Answer message until the PaC receives a valid
> > PANA-Auth-Request message.
> > 
> > - When a PaC sends a PANA-FirstAuth-End-Answer message in response to
> a
> > valid PANA-FirstAuth-End-Request message (remember that a
> > PANA-FirstAuth-End exchange is used for delimiting the first and
> > second EAP authentications), the answer message may be lost.  The
> > PANA-FirstAuth-End-Request would be retransmitted (with updating
> > transmission sequence number).  To deal with the case, it might be
> > better for the PaC to return a duplicate PANA-FirstAuth-End-Answer
> > message (with updating transmission and received sequence numbers)
> > after the PaC has been sent the first PANA-FirstAuth-End-Answer
> > message until the PaC receives a valid PANA-Auth-Request message for
> > the second EAP authentication.
> > 
> > - When a PaC sends a PANA-Bind-Answer message in response to a valid
> > PANA-Bind-Request message, the answer message can be lost.  As as
> > result, the PAA will retransmit the PANA-Bind-Request (but with using
> > a different transmission sequence number).  To deal with the case, it
> > might be better for the PaC to return a duplicate PANA-Bind-Answer
> > message (but with using different transmission and received sequence
> > numbers) for a while after the first PANA-Bind-Request was received.
> > The same thing can also apply to a PANA-Address-Update-Answer message
> > that is sent by a PaC.
> > 
> > - When a PaC or a PAA sends a PANA-Termination-Answer message in
> > response to a valid PANA-Termination-Request message, the answer
> > message can be lost.  As as result, the requester will retransmit the
> > request (but with using a different transmission sequence number).  To
> > deal with the case, it might be better for the sender of the answer to
> > return a duplicate answer (with using different transmission and
> > received sequence numbers) for a while after the first
> > PANA-Termination-Request was received.  The same thing can also apply
> > to a PANA-Reauth-Answer message that is sent by a PaC or a PAA.
> > 
> > Those could improve robustness of the PANA protocol against loss of
> > answer message.
> > 
> > Comments?
> > 
> > Yoshihiro Ohba
> > 
> > ----------
> > category: Technical
> > document: draft-ietf-pana-pana-xx.txt
> > messages: 335
> > nosy: dforsber
> > priority: Must Fix
> > status: Pending
> > title: Lost answer problem
> > __________________________________________________
> > PANA Issues <pana_issues@danforsberg.info>
> > <http://danforsberg.info:8080/pana-issues/issue98>
> > __________________________________________________
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 22:42:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17142
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 22:42:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkD2d-0004ii-7c; Mon, 12 Jul 2004 22:29:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkCX9-0003fy-25
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 21:56:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12615
	for <pana@ietf.org>; Mon, 12 Jul 2004 21:56:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkCX7-0003hk-DF
	for pana@ietf.org; Mon, 12 Jul 2004 21:56:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkCRv-0002JM-00
	for pana@ietf.org; Mon, 12 Jul 2004 21:51:16 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BkCPs-0001jP-00
	for pana@ietf.org; Mon, 12 Jul 2004 21:49:08 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by mx2.foretec.com with esmtp (Exim 4.24) id 1BkCPs-0005NY-Kx
	for pana@ietf.org; Mon, 12 Jul 2004 21:49:08 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6D1n1pD003241;
	Tue, 13 Jul 2004 10:49:01 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6D1n11h020603;
	Tue, 13 Jul 2004 10:49:01 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	LAA20602 ; Tue, 13 Jul 2004 10:49:01 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id KAA28619; Tue, 13 Jul 2004 10:49:00 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id KAA19641;
	Tue, 13 Jul 2004 10:48:59 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6D1mxpl027087;
	Tue, 13 Jul 2004 10:48:59 +0900 (JST)
Received: from steelhead (iVPN01-080.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0R00ABJP1LWR@tsbpo1.po.toshiba.co.jp>; Tue,
	13 Jul 2004 10:48:58 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BkCOW-0003LD-00; Mon, 12 Jul 2004 18:47:44 -0700
Date: Mon, 12 Jul 2004 21:47:44 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
In-reply-to: <625BE97BF4795E43970345790166B9BCE8D70A@EXC2K01B.cselt.it>
To: pana@ietf.org, Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Message-id: <20040713014744.GG893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org, Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>,
	Julien Bournelle <Julien.Bournelle@int-evry.fr>
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BCE8D70A@EXC2K01B.cselt.it>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Julien Bournelle <Julien.Bournelle@int-evry.fr>
Subject: [Pana] EAP-based reauth clarification [Re: Mobility Handling in
	PANA]
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Based on the discussion below.  I would suggest adding the following
sentences to section 4.4 of PANA speficication:

" 
When NAP and ISP separate authetnications were performed in the first
occurence of PANA authentication phase, the same NAP and ISP separate
authentications MUST also be performed in subsequent EAP-based
re-authentication occurances.  Otherwise, NAP and ISP separate
authentications MUST NOT be performed in subsequent EAP-based
re-authentication occurances.
"

Yoshihiro Ohba


On Mon, Jul 12, 2004 at 05:42:11PM +0200, Giaretta Gerardo wrote:
> Hi Yoshi,
> 
> > > > I am not sure how EAP-based re-authentication can work after the 
> > > > PaC has successfully established a new PANA session with nPAA 
> > > > based on the mobility optimization operation, especially with NAP 
> > > > and ISP separated authentications.  Since PSR-PSA exchange is 
> > > > omitted in the case of EAP-based re-authentication, there is no 
> > > > means to negotiate on NAP and ISP separate authentications between
> 
> > > > the PaC and nPAA.  Do you have any thoughts on this?
> > > > 
> > > 
> > > I'm not sure I understand your point: is this a general
> > PANA issue or
> > > is it related to the operations described in
> > > draft-bournelle-pana-ctp-00.txt?
> > 
> > It might be related to both.  I think that if NAP and ISP
> > separate authentications were made in the initial 
> > authentication, then the same NAP and ISP separate 
> > authentications should also be made in EAP-based 
> > re-authentication (this is a PANA issue, i.e., this should be 
> > described in the PANA specification.)  If the same thing 
> > needs to be done in EAP-based re-authentication after handoff 
> > (though I am not sure the same thing needs to be done in this 
> > case), information on whether NAP and ISP separate 
> > authentications were made in the previous network may need to 
> > be included in PANA-CTD (this is an issue of 
> > draft-bournelle-pana-ctp-00.txt).
> >
> 
> I agree with you. The result of the usage of CTP, as the result of any
> fast authentication mechanism, must be the same as the one obtained
> performing the whole authentication procedure. This implies that nPAA
> should know if PaC performed double authentication and which ISP it
> chose. Therefore this information must be transferred in CTD message. 
> 
> However, I think that EAP re-authentication is not related to mobility
> handling. The usage of CTP allows to transfer the PANA context to the
> nPAA. After the PBR/PBA exchange the PaC is authenticated and the nPAA
> knows the residual authorization lifetime. Therefore
> EAP-reauthentication is not performed immediately after the handoff and
> it is accomplished as specified in PANA specs.
> 
> Note that we have not defined yet how to inform both NAP and ISP AAA
> system of the new PaC's location. I think this is also an important
> issue.
> 
> 
> --Gerardo
> 
> 
>  
> > Yoshihiro Ohba
> > 
> 
> 
> 
> 
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
> 
> ====================================================================
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to 
> MailAdmin@tilab.com. Thank you
> ====================================================================

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 12 22:54:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA17703
	for <pana-archive@lists.ietf.org>; Mon, 12 Jul 2004 22:54:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkD8z-0006iZ-KJ; Mon, 12 Jul 2004 22:35:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkCbJ-0006AI-Hf
	for pana@megatron.ietf.org; Mon, 12 Jul 2004 22:00:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13337
	for <pana@ietf.org>; Mon, 12 Jul 2004 22:00:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkCbH-0004SS-Ag
	for pana@ietf.org; Mon, 12 Jul 2004 22:00:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkCVe-0003C8-00
	for pana@ietf.org; Mon, 12 Jul 2004 21:55:07 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12) id 1BkCRB-00023C-00
	for pana@ietf.org; Mon, 12 Jul 2004 21:50:29 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0R00505P3AEF@mailout3.samsung.com> for pana@ietf.org; Tue,
	13 Jul 2004 10:49:58 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0R00L4YP3A52@mailout3.samsung.com> for pana@ietf.org;
	Tue, 13 Jul 2004 10:49:58 +0900 (KST)
Received: from Alperyegin ([105.253.155.19])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0R00BNGP37V9@mmp1.samsung.com> for
	pana@ietf.org; Tue, 13 Jul 2004 10:49:58 +0900 (KST)
Date: Mon, 12 Jul 2004 18:49:58 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] New: [issue98] Lost answer problem
In-reply-to: <20040713013154.GF893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <01d001c4687b$b60a9730$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: Dan.Forsberg@nokia.com, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> > > There might be some cases in which a PaC or a PAA might need to
send a
> > > duplicate answer to a retransmitted old request (as well as a
fresh
> > > answer to a new request if any) considering that an answer message
for
> > > an old request can be lost.  Without this, a PANA session may
stall in
> > > a way that the requester keeps retransmitting the old request
while
> > > the responder may keep discarding them with waiting for a new
request.
> >
> > There would not be any discarding due to sequence numbers. I guess
the
> > only problem could be that the PaC has jumped to the next state in
the
> > state machine as soon as it responded to a message, and in that
state it
> > does not expect the same request it had already responded earlier.
Is
> > that the issue?
> 
> Yes.

OK, then I think this is not a protocol issue and I'd propose discussing
this in the state machine I-D.  As long as the request is not rejected,
the PaC should be able to produce a response . [Last transmitted message
payload is already part of the session attributes. It can be partially
used for optimization if needed].

Alper






> 
> Yoshihiro Ohba
> 
> 
> >
> > Alper
> >
> >
> >
> >
> >
> >
> > > The cases are described below.
> > >
> > > - When a PaC sends a PANA-Start-Answer message in response to a
valid
> > > PANA-Start-Request message without a Cookie AVP, the answer
message
> > > can be lost.  The PANA-Start-Request would be retransmitted.  To
deal
> > > with the case, it might be better for the PaC to return a
duplicate
> > > PANA-Start-Answer message after the PaC has been sent the first
> > > PANA-Start-Answer message until the PaC receives a valid
> > > PANA-Auth-Request message.
> > >
> > > - When a PaC sends a PANA-FirstAuth-End-Answer message in response
to
> > a
> > > valid PANA-FirstAuth-End-Request message (remember that a
> > > PANA-FirstAuth-End exchange is used for delimiting the first and
> > > second EAP authentications), the answer message may be lost.  The
> > > PANA-FirstAuth-End-Request would be retransmitted (with updating
> > > transmission sequence number).  To deal with the case, it might be
> > > better for the PaC to return a duplicate PANA-FirstAuth-End-Answer
> > > message (with updating transmission and received sequence numbers)
> > > after the PaC has been sent the first PANA-FirstAuth-End-Answer
> > > message until the PaC receives a valid PANA-Auth-Request message
for
> > > the second EAP authentication.
> > >
> > > - When a PaC sends a PANA-Bind-Answer message in response to a
valid
> > > PANA-Bind-Request message, the answer message can be lost.  As as
> > > result, the PAA will retransmit the PANA-Bind-Request (but with
using
> > > a different transmission sequence number).  To deal with the case,
it
> > > might be better for the PaC to return a duplicate PANA-Bind-Answer
> > > message (but with using different transmission and received
sequence
> > > numbers) for a while after the first PANA-Bind-Request was
received.
> > > The same thing can also apply to a PANA-Address-Update-Answer
message
> > > that is sent by a PaC.
> > >
> > > - When a PaC or a PAA sends a PANA-Termination-Answer message in
> > > response to a valid PANA-Termination-Request message, the answer
> > > message can be lost.  As as result, the requester will retransmit
the
> > > request (but with using a different transmission sequence number).
To
> > > deal with the case, it might be better for the sender of the
answer to
> > > return a duplicate answer (with using different transmission and
> > > received sequence numbers) for a while after the first
> > > PANA-Termination-Request was received.  The same thing can also
apply
> > > to a PANA-Reauth-Answer message that is sent by a PaC or a PAA.
> > >
> > > Those could improve robustness of the PANA protocol against loss
of
> > > answer message.
> > >
> > > Comments?
> > >
> > > Yoshihiro Ohba
> > >
> > > ----------
> > > category: Technical
> > > document: draft-ietf-pana-pana-xx.txt
> > > messages: 335
> > > nosy: dforsber
> > > priority: Must Fix
> > > status: Pending
> > > title: Lost answer problem
> > > __________________________________________________
> > > PANA Issues <pana_issues@danforsberg.info>
> > > <http://danforsberg.info:8080/pana-issues/issue98>
> > > __________________________________________________
> >


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 13 06:27:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29380
	for <pana-archive@lists.ietf.org>; Tue, 13 Jul 2004 06:27:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkKSm-00012u-FK; Tue, 13 Jul 2004 06:24:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkKPc-0008S2-0T
	for pana@megatron.ietf.org; Tue, 13 Jul 2004 06:21:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28819
	for <pana@ietf.org>; Tue, 13 Jul 2004 06:21:21 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkKPZ-0003yi-Jy
	for pana@ietf.org; Tue, 13 Jul 2004 06:21:21 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkKOa-0003gO-00
	for pana@ietf.org; Tue, 13 Jul 2004 06:20:21 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BkKNX-00038h-00
	for pana@ietf.org; Tue, 13 Jul 2004 06:19:16 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6DAJ5pD010731;
	Tue, 13 Jul 2004 19:19:05 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6DAJ48F003220;
	Tue, 13 Jul 2004 19:19:04 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	VAA03217 ; Tue, 13 Jul 2004 19:19:04 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id TAA13416; Tue, 13 Jul 2004 19:19:03 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id TAA07694;
	Tue, 13 Jul 2004 19:19:02 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6DAJ1pl006552;
	Tue, 13 Jul 2004 19:19:01 +0900 (JST)
Received: from steelhead (iVPN01-117.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0S00HHMCNNY6@tsbpo1.po.toshiba.co.jp>; Tue,
	13 Jul 2004 19:19:00 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BkKMQ-0003ZZ-00; Tue, 13 Jul 2004 03:18:06 -0700
Date: Tue, 13 Jul 2004 06:18:06 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New: [issue98] Lost answer problem
In-reply-to: <01d001c4687b$b60a9730$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040713101806.GI893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
	pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040713013154.GF893@steelhead>
	<01d001c4687b$b60a9730$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Mon, Jul 12, 2004 at 06:49:58PM -0700, Alper Yegin wrote:
> > > > There might be some cases in which a PaC or a PAA might need to
> send a
> > > > duplicate answer to a retransmitted old request (as well as a
> fresh
> > > > answer to a new request if any) considering that an answer message
> for
> > > > an old request can be lost.  Without this, a PANA session may
> stall in
> > > > a way that the requester keeps retransmitting the old request
> while
> > > > the responder may keep discarding them with waiting for a new
> request.
> > >
> > > There would not be any discarding due to sequence numbers. I guess
> the
> > > only problem could be that the PaC has jumped to the next state in
> the
> > > state machine as soon as it responded to a message, and in that
> state it
> > > does not expect the same request it had already responded earlier.
> Is
> > > that the issue?
> > 
> > Yes.
> 
> OK, then I think this is not a protocol issue and I'd propose discussing
> this in the state machine I-D.  As long as the request is not rejected,
> the PaC should be able to produce a response . 

I think it is a protocol matter to specify in which condition a
request should be accepted or rejected.  For example, the PANA
specification should be clear on what to do when a PaC receives a
previously received PBR for which it has already sent a PBA.

Yoshihiro Ohba



> [Last transmitted message
> payload is already part of the session attributes. It can be partially
> used for optimization if needed].
> 
> Alper
> 
> 
> 
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > >
> > > Alper
> > >
> > >
> > >
> > >
> > >
> > >
> > > > The cases are described below.
> > > >
> > > > - When a PaC sends a PANA-Start-Answer message in response to a
> valid
> > > > PANA-Start-Request message without a Cookie AVP, the answer
> message
> > > > can be lost.  The PANA-Start-Request would be retransmitted.  To
> deal
> > > > with the case, it might be better for the PaC to return a
> duplicate
> > > > PANA-Start-Answer message after the PaC has been sent the first
> > > > PANA-Start-Answer message until the PaC receives a valid
> > > > PANA-Auth-Request message.
> > > >
> > > > - When a PaC sends a PANA-FirstAuth-End-Answer message in response
> to
> > > a
> > > > valid PANA-FirstAuth-End-Request message (remember that a
> > > > PANA-FirstAuth-End exchange is used for delimiting the first and
> > > > second EAP authentications), the answer message may be lost.  The
> > > > PANA-FirstAuth-End-Request would be retransmitted (with updating
> > > > transmission sequence number).  To deal with the case, it might be
> > > > better for the PaC to return a duplicate PANA-FirstAuth-End-Answer
> > > > message (with updating transmission and received sequence numbers)
> > > > after the PaC has been sent the first PANA-FirstAuth-End-Answer
> > > > message until the PaC receives a valid PANA-Auth-Request message
> for
> > > > the second EAP authentication.
> > > >
> > > > - When a PaC sends a PANA-Bind-Answer message in response to a
> valid
> > > > PANA-Bind-Request message, the answer message can be lost.  As as
> > > > result, the PAA will retransmit the PANA-Bind-Request (but with
> using
> > > > a different transmission sequence number).  To deal with the case,
> it
> > > > might be better for the PaC to return a duplicate PANA-Bind-Answer
> > > > message (but with using different transmission and received
> sequence
> > > > numbers) for a while after the first PANA-Bind-Request was
> received.
> > > > The same thing can also apply to a PANA-Address-Update-Answer
> message
> > > > that is sent by a PaC.
> > > >
> > > > - When a PaC or a PAA sends a PANA-Termination-Answer message in
> > > > response to a valid PANA-Termination-Request message, the answer
> > > > message can be lost.  As as result, the requester will retransmit
> the
> > > > request (but with using a different transmission sequence number).
> To
> > > > deal with the case, it might be better for the sender of the
> answer to
> > > > return a duplicate answer (with using different transmission and
> > > > received sequence numbers) for a while after the first
> > > > PANA-Termination-Request was received.  The same thing can also
> apply
> > > > to a PANA-Reauth-Answer message that is sent by a PaC or a PAA.
> > > >
> > > > Those could improve robustness of the PANA protocol against loss
> of
> > > > answer message.
> > > >
> > > > Comments?
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > > ----------
> > > > category: Technical
> > > > document: draft-ietf-pana-pana-xx.txt
> > > > messages: 335
> > > > nosy: dforsber
> > > > priority: Must Fix
> > > > status: Pending
> > > > title: Lost answer problem
> > > > __________________________________________________
> > > > PANA Issues <pana_issues@danforsberg.info>
> > > > <http://danforsberg.info:8080/pana-issues/issue98>
> > > > __________________________________________________
> > >
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 13 08:56:13 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07311
	for <pana-archive@lists.ietf.org>; Tue, 13 Jul 2004 08:56:13 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkMjL-00016M-LJ; Tue, 13 Jul 2004 08:49:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkMaD-000790-6F
	for pana@megatron.ietf.org; Tue, 13 Jul 2004 08:40:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06681
	for <pana@ietf.org>; Tue, 13 Jul 2004 08:40:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkMaC-0005sb-Jp
	for pana@ietf.org; Tue, 13 Jul 2004 08:40:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkMZE-0005Xm-00
	for pana@ietf.org; Tue, 13 Jul 2004 08:39:29 -0400
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx with esmtp (Exim 4.12) id 1BkMYG-0004v8-00
	for pana@ietf.org; Tue, 13 Jul 2004 08:38:28 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I0S0060LIRTEJ@dns2.cselt.it> for pana@ietf.org; Tue,
	13 Jul 2004 14:31:05 +0200 (MEST)
Received: from EXC05B.cselt.it ([163.162.36.250]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Tue, 13 Jul 2004 14:35:55 +0200
Received: from EXC2K01B.cselt.it ([163.162.4.97])
	by EXC05B.cselt.it with Microsoft SMTPSVC(5.0.2195.5329); Tue,
	13 Jul 2004 14:37:55 +0200
Date: Tue, 13 Jul 2004 14:37:55 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Message-id: <625BE97BF4795E43970345790166B9BCD4DF3C@EXC2K01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: EAP-based reauth clarification [Re: Mobility Handling in PANA]
Thread-Index: AcRoe644RMXOdWPXQd6dawT+Qq1YQQAWF/2Q
content-class: urn:content-classes:message
X-OriginalArrivalTime: 13 Jul 2004 12:37:55.0931 (UTC)
	FILETIME=[38D9E2B0:01C468D6]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Cc: Julien Bournelle <Julien.Bournelle@int-evry.fr>, pana@ietf.org
Subject: [Pana] RE: EAP-based reauth clarification [Re: Mobility Handling in
	PANA]
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Yoshihiro Ohba wrote: =20
>=20
> Based on the discussion below.  I would suggest adding the
> following sentences to section 4.4 of PANA speficication:
>=20
> "
> When NAP and ISP separate authetnications were performed in=20
> the first occurence of PANA authentication phase, the same=20
> NAP and ISP separate authentications MUST also be performed=20
> in subsequent EAP-based re-authentication occurances. =20
> Otherwise, NAP and ISP separate authentications MUST NOT be=20
> performed in subsequent EAP-based re-authentication occurances. "
>

Just two comments:

[1] A similar text is provided in section 4.9:=20

"
   When separate EAP authentications are performed for ISP and NAP in a
   single PANA session, it is possible that different authorization
   lifetime values are associated with the two authentications.  In this
   case, the smaller authorization lifetime value MUST be used for
   calculating the PANA Session-Lifetime value.  As a result, when
   EAP-based re-authentication occurs, both NAP and ISP authentications
   will be performed in the same re-authentication procedure.
"

Is this really needed? I mean, it could be unefficient to perform both
the authentications if only one is required. This is a consequence that
the PANA Session Lifetime is equal to the smaller authorization lifetime
value.=20
I'm thinking if it is possible to manage the lifetimes in order to
perform only the authentication that is required. Do you have any
thoughts on this?

A possible solution could be (however I'm not sure if this works):

PANA session lifetime =3D min (Residual NAP auth. Lifetime, Residual ISP
auth. Lifetime)=20

In this way, only the required re-authentication is performed and the
PANA session lifetime is re-calculated at the end of each
re-authentication. However there might be cases in which it is
convenient to perform both the authentications together (e.g. the
difference between the residual lifetimes is very small).=20

[2] What about a scenario in which a new ISP is available? Consider that
at the first occurence of PANA there were only two ISPs available (ISP1
and ISP2). If a new ISP (ISP3) becomes available (e.g. after a movement
of the PaC), I think this must be communicated to the PaC. How can we
handle this?


--Gerardo

=20
> Yoshihiro Ohba
>=20
>=20
> On Mon, Jul 12, 2004 at 05:42:11PM +0200, Giaretta Gerardo wrote:
> > Hi Yoshi,
> >=20
> > > > > I am not sure how EAP-based re-authentication can=20
> work after the
> > > > > PaC has successfully established a new PANA session with nPAA=20
> > > > > based on the mobility optimization operation,=20
> especially with NAP=20
> > > > > and ISP separated authentications.  Since PSR-PSA exchange is=20
> > > > > omitted in the case of EAP-based re-authentication,=20
> there is no=20
> > > > > means to negotiate on NAP and ISP separate=20
> authentications between
> >=20
> > > > > the PaC and nPAA.  Do you have any thoughts on this?
> > > > >=20
> > > >=20
> > > > I'm not sure I understand your point: is this a general
> > > PANA issue or
> > > > is it related to the operations described in=20
> > > > draft-bournelle-pana-ctp-00.txt?
> > >=20
> > > It might be related to both.  I think that if NAP and ISP=20
> separate=20
> > > authentications were made in the initial authentication, then the=20
> > > same NAP and ISP separate authentications should also be made in=20
> > > EAP-based re-authentication (this is a PANA issue, i.e.,=20
> this should=20
> > > be described in the PANA specification.)  If the same thing
> > > needs to be done in EAP-based re-authentication after handoff=20
> > > (though I am not sure the same thing needs to be done in this=20
> > > case), information on whether NAP and ISP separate=20
> > > authentications were made in the previous network may need to=20
> > > be included in PANA-CTD (this is an issue of=20
> > > draft-bournelle-pana-ctp-00.txt).
> > >
> >=20
> > I agree with you. The result of the usage of CTP, as the=20
> result of any=20
> > fast authentication mechanism, must be the same as the one obtained=20
> > performing the whole authentication procedure. This implies=20
> that nPAA=20
> > should know if PaC performed double authentication and which ISP it=20
> > chose. Therefore this information must be transferred in=20
> CTD message.
> >=20
> > However, I think that EAP re-authentication is not related=20
> to mobility=20
> > handling. The usage of CTP allows to transfer the PANA=20
> context to the=20
> > nPAA. After the PBR/PBA exchange the PaC is authenticated=20
> and the nPAA=20
> > knows the residual authorization lifetime. Therefore=20
> > EAP-reauthentication is not performed immediately after the handoff=20
> > and it is accomplished as specified in PANA specs.
> >=20
> > Note that we have not defined yet how to inform both NAP=20
> and ISP AAA=20
> > system of the new PaC's location. I think this is also an important=20
> > issue.
> >=20
> >=20
> > --Gerardo
> >=20
> >=20
> > =20
> > > Yoshihiro Ohba
> > >=20
> >=20
> >=20
> >=20
> >=20
> > Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia=20
> > S.p.A.
> >=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > CONFIDENTIALITY NOTICE
> > This message and its attachments are addressed solely to=20
> the persons=20
> > above and may contain confidential information. If you have=20
> received=20
> > the message in error, be informed that any use of the=20
> content hereof=20
> > is prohibited. Please return it immediately to the sender=20
> and delete=20
> > the message. Should you have any questions, please send an=20
> e_mail to=20
> > MailAdmin@tilab.com. Thank you=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 13 09:39:35 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10062
	for <pana-archive@lists.ietf.org>; Tue, 13 Jul 2004 09:39:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkNQ5-000387-Ak; Tue, 13 Jul 2004 09:34:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkNLi-0001yT-Dp
	for pana@megatron.ietf.org; Tue, 13 Jul 2004 09:29:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09587
	for <pana@ietf.org>; Tue, 13 Jul 2004 09:29:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkNLh-0005P9-JM
	for pana@ietf.org; Tue, 13 Jul 2004 09:29:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkNKm-00056L-00
	for pana@ietf.org; Tue, 13 Jul 2004 09:28:37 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx with esmtp (Exim 4.12) id 1BkNJy-0004Vx-00
	for pana@ietf.org; Tue, 13 Jul 2004 09:27:47 -0400
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 802922FE8F;
	Tue, 13 Jul 2004 15:27:05 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1BkNHy-000Cjc-UE;
	Tue, 13 Jul 2004 15:25:42 +0200
Date: Tue, 13 Jul 2004 15:25:42 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: yohba@tari.toshiba.com, pana@ietf.org,
        Gerardo Giaretta <gerardo.giaretta@tilab.com>
Subject: Re: [Pana] Mobility Handling in PANA
Message-ID: <20040713132542.GY45745@ipv6-5.int-evry.fr>
References: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
	<20040710062738.GD893@steelhead>
	<20040712101804.GF44906@ipv6-5.int-evry.fr>
	<20040712111907.GT893@steelhead>
	<20040712113752.GJ44906@ipv6-5.int-evry.fr>
	<20040712123404.GX893@steelhead>
	<20040712143702.GA45745@ipv6-5.int-evry.fr>
	<20040712222745.GA893@steelhead>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040712222745.GA893@steelhead>
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (score=-4.9, requis 4.5, autolearn=not spam,
	BAYES_00 -4.90)
X-MailScanner-From: jb@ipv6-5.int-evry.fr
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

hi yoshi,

On Mon, Jul 12, 2004 at 06:27:45PM -0400, Yoshihiro Ohba wrote:
> 
> I just meant "not piggybacking other protocol messages" by modularity.

I understand your point.
At the beginning, we thought about this approach but as the nPAA sends a
PANA message, we wanted to answer with a PSA message and not a CTAR
message.

> I think both non-piggybacking and piggybacking schemes should be
> allowed in the design.  Non-piggybacking scheme allows other mobility
> optimization schemes also to be used by PANA, while piggybacking
> scheme provides optimization for a particular mobility optimization
> scheme

do you think that we could live with the 2 options running in the same
time ? 

.
> 
> Yoshihiro Ohba
> 
> 
> On Mon, Jul 12, 2004 at 04:37:02PM +0200, Julien Bournelle wrote:
> > > Since PANA and CTP are different protocols, I think nPAA can wait for
> > > messages from both protocols at the same time without violating both
> > > protocols.  But parhaps it is better in this case that CTAR is
> > > acknowledged with CTAA and the PaC sends PSA after receiving CTAA to
> > > provide synchronization bewteen context transfer operation and PANA
> > > mobility optimization, something like:
> > > 
> > > PaC           nPAA              pPAA
> > > ----------------------------------------
> > >       PDI
> > >  -------------->
> > >       PSR
> > >  <---------------
> > >       CTAR
> > >  --------------->
> > >                      CT-Request 
> > >                   -------------->
> > >                          CTD 
> > >                   <--------------
> > >       CTAA
> > >  <--------------
> > > 
> > >   PSA[old Session-ID, Nonce, MAC]
> > >   --------------->
> > >   PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> > >   <-------------
> > >   PBA[new Session-ID, Key-Id, PPAC, MAC]
> > >   ------------->
> > > 
> > > Comparing this scheme with your scheme below, the discussion point
> > > would be modularity (this sheme) vs optimization (your scheme).
> > 
> > I think that with our solution we keep the modularity since the pana
> > module asks to the ctp module the CTAR message to be sent.
> > 
> > In your scenario, the PANA module at PaC receives the PSR message and
> > contacts the CTP module (saying that CTP module must sent a CTAR).
> > In our scenario, the PANA module asks to the CTP module the CTAR
> > message and embeds it. Thus I think that we keep the modularity.
> > 
> > Maybe I miss something, what do you mean by modularity ?
> > 
> > > 
> > > Yoshihiro Ohba
> > > 
> > > > 
> > > > This is why we propose to emebed the CTAR message in the PSR message.
> > > > Thus the pac answers with a PSA message. The PANA module at the pac aks
> > > > to the CTP module to get a valid CTAR message and embeds it in the PSA
> > > > message. The nPAA receives the PSA message that it is waiting for and
> > > > sees that it contains a CTAR message. It delivers it to its CTP module
> > > > and waits the CT-Request/CTD exchange. This why we introduce a new state
> > > > in the state machine (PANA-CTP-WAITING)
> > > > 
> > > > 
> > > > Thus we propose this:
> > > > 
> > > > 
> > > >      PaC           nPAA              pPAA
> > > >      ----------------------------------------
> > > >            PDI
> > > >       -------------->
> > > >            PSR
> > > >      <---------------
> > > >           PSA [old Session-ID, Nonce, CTAR] 
> > > >       --------------->
> > > >  
> > > >                            CT-Request 
> > > >                         -------------->
> > > >                                CTD 
> > > >                         <--------------
> > > > 
> > > >       PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> > > >      <-------------
> > > >       PBA[new Session-ID, Key-Id, PPAC, MAC]
> > > >       ------------->
> > > > 
> > > > 
> > > > 
> > > > 
> > > > -- 
> > > > julien.bournelle@int-evry.fr
> > > 
> > 
> > -- 
> > julien.bournelle@int-evry.fr
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 

-- 
julien.bournelle@int-evry.fr

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 13 14:07:27 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29862
	for <pana-archive@lists.ietf.org>; Tue, 13 Jul 2004 14:07:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkRcc-0000sN-GA; Tue, 13 Jul 2004 14:03:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkRQS-0006JY-6X
	for pana@megatron.ietf.org; Tue, 13 Jul 2004 13:50:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28629
	for <pana@ietf.org>; Tue, 13 Jul 2004 13:50:42 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkRQQ-0006Zl-FL
	for pana@ietf.org; Tue, 13 Jul 2004 13:50:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkRPV-0006FS-00
	for pana@ietf.org; Tue, 13 Jul 2004 13:49:45 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1BkROe-0005b2-00
	for pana@ietf.org; Tue, 13 Jul 2004 13:48:52 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0S00E01XGJO1@mailout2.samsung.com> for pana@ietf.org; Wed,
	14 Jul 2004 02:48:19 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0S00EI2XGJFN@mailout2.samsung.com> for pana@ietf.org;
	Wed, 14 Jul 2004 02:48:19 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0S00CW0XGGLM@mmp1.samsung.com> for
	pana@ietf.org; Wed, 14 Jul 2004 02:48:19 +0900 (KST)
Date: Tue, 13 Jul 2004 10:48:20 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] New: [issue98] Lost answer problem
In-reply-to: <20040713101806.GI893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <023501c46901$97596b00$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: Dan.Forsberg@nokia.com, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> > OK, then I think this is not a protocol issue and I'd propose
discussing
> > this in the state machine I-D.  As long as the request is not
rejected,
> > the PaC should be able to produce a response .
> 
> I think it is a protocol matter to specify in which condition a
> request should be accepted or rejected.  For example, the PANA
> specification should be clear on what to do when a PaC receives a
> previously received PBR for which it has already sent a PBA.

The default action would be to respond to the request (unless there is a
statement in the draft that makes an exception).

Alper



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 13 15:13:24 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05465
	for <pana-archive@lists.ietf.org>; Tue, 13 Jul 2004 15:13:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkSXQ-0001Cx-Lp; Tue, 13 Jul 2004 15:02:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkSPX-0004Nr-4F
	for pana@megatron.ietf.org; Tue, 13 Jul 2004 14:53:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03502
	for <pana@ietf.org>; Tue, 13 Jul 2004 14:53:48 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkSPV-0004cX-0C
	for pana@ietf.org; Tue, 13 Jul 2004 14:53:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkSOd-0004IW-00
	for pana@ietf.org; Tue, 13 Jul 2004 14:52:56 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1BkSNo-0003lt-00
	for pana@ietf.org; Tue, 13 Jul 2004 14:52:05 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0T00H010DYNT@mailout2.samsung.com> for pana@ietf.org; Wed,
	14 Jul 2004 03:51:34 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0T00C3O0DXZJ@mailout2.samsung.com> for pana@ietf.org;
	Wed, 14 Jul 2004 03:51:33 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0T0086P0DUKZ@mmp2.samsung.com> for
	pana@ietf.org; Wed, 14 Jul 2004 03:51:33 +0900 (KST)
Date: Tue, 13 Jul 2004 11:51:34 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] issue85 (initial text)
In-reply-to: <20040519015123.GC29343@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <023e01c4690a$6c6fc430$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Yoshi,

I'd suggest to have a more generic PANA message, such as "PANA-Update".
Initially we can use this just to update the IP address of PaC. We can
evaluate other types of updates as need arises. What do you think?

Also, I didn't understand where Device-ID comes into the picture. When
do we update the device-ID?

I have some editorial comments as well. I'll wait for your response to
these first.

Alper



> -----Original Message-----
> From: pana-admin@ietf.org [mailto:pana-admin@ietf.org] On Behalf Of
> Yoshihiro Ohba
> Sent: Tuesday, May 18, 2004 6:51 PM
> To: pana@ietf.org
> Subject: [Pana] issue85 (initial text)
> 
> This is the initial text for issue 85.
> 
> Comments are appreciated.
> 
> ----------
> 
> 
> [1] Add the following item in section 4.1.1
> 
> "
>    o  IP-Address AVP: Conveys an IP-Address of a PaC.
> "
> 
> 
> [2] Add the following items in section 4.1.5:
> 
> "
>       *  IP address of PaC (may be the same as the Device-Id of PaC)
> 
>       *  IP address of PAA (may be the same as the Device-Id of PAA)
> "
> 
> 
> [3] Add the following item in section section 4.1.7:
> 
> "
>       When an IP-Address AVP is included, the AVP is valid if (i) the
>       Address type contained in the AVP matches the expected one
>       (i.e., either IPv4 or IPv6) that is used for the current PANA
>       session and (ii) the AVP value matches the one extracted from
>       the IP header.
> "
> 
> [4] Update the following paragraph of section 4.4
> 
> "
>    The second type of re-authentication is based on a single protected
>    message exchange without entering the authentication phase.
>    PANA-Reauth-Request and PANA-Reauth-Answer messages are used for
this
>    purpose.  If there is an established PANA SA, both the PaC and the
>    PAA are allowed to send a PANA-Reauth-Request message to the
>    communicating peer whenever it needs to make sure the availability
of
>    the PANA SA on the peer and expect the peer to return a PANA-
>    Reauth-Answer message.  Both PANA-Reauth-Request/
PANA-Reauth-Answer
>    messages MUST be protected with a MAC AVP.
> "
> 
> to:
> 
> "
>    The second type of re-authentication is based on a single protected
>    message exchange without entering the authentication phase.
>    PANA-Reauth-Request and PANA-Reauth-Answer messages are used for
>    this purpose.  If there is an established PANA SA, both the PaC and
>    the PAA are allowed to send a PANA-Reauth-Request message to the
>    communicating peer whenever it needs to make sure the availability
>    of the PANA SA on the peer and expect the peer to return a
>    PANA-Reauth-Answer message.  In this case, both
>    PANA-Reauth-Request/PANA-Reauth-Answer messages MUST be protected
>    with a MAC AVP.  If there is an established PANA session but
>    without an established PANA SA, both the PaC and the PAA are
>    allowed to send a PANA-Reauth-Request message to the communicating
>    peer whenever it needs to make sure the availability of the PANA
>    session on the peer and expect the peer to return a
>    PANA-Reauth-Answer message.  In this case, both
>    PANA-Reauth-Request/PANA-Reauth-Answer messages are not protected
>    with a MAC AVP.
> "
> 
> [5] Insert the following section after section 4.7:
> 
> "
> 4.8. Updating PaC's Address
> 
> A PaC's address can change in certain situations.  For example, the
> PANA framework [I-D.ietf-pana-framework] describes a case in which a
> PaC replaces a pre-PANA address (PRPA) a post-PANA address (POPA), and
> the PaC and PAA create host routes to each other in order to maintain
> on-link communication based on the POPA where the link-layer address
> of the PaC is used as the device identifier.  Also, a PaC's device
> identifier may change regardless of whether a link-layer address or an
> IP address is used as the device identifier.  As a result, it is
> possible when a link-layer address is used as the device identifier
> that both the device identifier and an IP address change.  In any
> case, the PAA needs to be notified about the change of address(es).
> 
> After the PaC has changed its address(es), it MUST send a
> PANA-Address-Update-Request message to the PAA.  The message carries
> the new address(es) in a Device-Id AVP and/or an IP-Address AVP.  At
> least one of these AVPs MUST appear in the request.  If an IP address
> is used as the device identifier, a Device-Id AVP MUST be used and an
> IP-Address AVP MUST NOT be used.  If an address contained in the
> request is invalid, the PAA sends a PANA-Error message with a result
> code PANA_INVALID_DEVICE_ID or PANA_INVALID_IP_ADDRESS depending on
> whether the device identifier or the IP address is invalid (in case
> both a Device-Id AVP and an IP-Address AVP are included and both are
> invalid, whichever result code is returned).  Otherwise, the PAA
> updates the address(es) of the PaC of the session attributes and
> returns a PANA-Address-Update-Answer message.  If there is an
> established PANA SA, both PANA-Address-Update-Request and
> PANA-Address-Update-Answer messages MUST be protected with a MAC AVP.
> "
> 
> [6] Change Figure 10 to:
> 
> "
>                  Message                     Direction:
>                                              PaC---PAA
>                  ----------------------------------------
>                  PANA-PAA-Discover           -------->
> 
>                  PANA-Start-Request          <--------
>                  PANA-Start-Answer           -------->
> 
>                  PANA-Auth-Request           <--------
>                  PANA-Auth-Answer            -------->
> 
>                  PANA-FirstAuth-End-Request  <--------
>                  PANA-FirstAuth-End-Answer   -------->
> 
>                  PANA-Bind-Request           <--------
>                  PANA-Bind-Answer            -------->
> 
>                  PANA-Reauth-Request         <------->
>                  PANA-Reauth-Answer          <------->
> 
>                  PANA-Termination-Request    <------->
>                  PANA-Termination-Answer     <------->
> 
>                  PANA-Address-Update-Request -------->
>                  PANA-Address-Update-Answer  <--------
> 
>                  PANA-Error                  <------->
> "
> 
> [7] Change sections 6.4.9 and 6.4.10 from:
> 
> "
> 6.4.9 PANA-Reauth-Request (PRAR)
> 
>    PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
> 
>          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
>                        < Session-Id >
>                        [ Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> 
> 6.4.10 PANA-Reauth-Answer (PRAA)
> 
>    PANA-Reauth-Answer (PRAA) is sent in response to a
>    PANA-Reauth-Request.
> 
>          PANA-Reauth-Answer ::= < PANA-Header: 5 >
>                        < Session-Id >
>                        [ Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
> "
> 
> to:
> 
> "
> 6.4.9 PANA-Reauth-Request (PRAR)
> 
>    PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
> 
>          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
>                        < Session-Id >
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> 
> 6.4.10 PANA-Reauth-Answer (PRAA)
> 
>    PANA-Reauth-Answer (PRAA) is sent in response to a
>    PANA-Reauth-Request.
> 
>          PANA-Reauth-Answer ::= < PANA-Header: 5 >
>                        < Session-Id >
>                     *  [ AVP ]
>                    0*1 < MAC >
> "
> 
> [8] Add the following sections:
> 
> "
> 6.4.16 PANA-Address-Update-Request (PAUR)
> 
>    PANA-Address-Update-Request (PAUR) is sent by the PaC to the PAA.
> 
>          PANA-Address-Update-Request ::= < PANA-Header: 9, REQ >
>                        < Session-Id >
>                    0*1 { Device-Id }
>                    0*1 { IP-Address }
>                    0*1 < MAC >
> 
> 
> 6.4.17 PANA-Address-Update-Answer (PAUA)
> 
>    PANA-Address-Update-Answer (PAUA) is sent by the PAA to the PaC in
>    response to a PANA-Address-Update-Request.
> 
>          PANA-Address-Update-Answer ::= < PANA-Header: 9 >
>                        < Session-Id >
>                    0*1 < MAC >
> "
> 
> "
> 6.5.19 IP-Address AVP
> 
>    The IP-Address (AVP Code: 1041) contains an IP address of a PaC.
>    The payload format of the IP-Address AVP is the same as that of the
>    Device-Id AVP (see See section Section 6.5.2).  Address families
>    for IPv4 or IPv6 MUST be used for this AVP.
> "
> 
> 
> [9] Add the following result code in section 6.5.7.2:
> 
> "
>    PANA_INVALID_DEVICE_ID  5019
> 
>       Error code from PAA to PaC or from PaC to PAA.  This error is
>       returned in a PANA-Error message when the Device-Id AVP
>       contained in a received PANA-Bind-Request, PANA-Bind-Answer or
>       PANA-Address-Update-Request message is invalid.
> 
>    PANA_INVALID_IP_ADDRESS  5020
> 
>       Error code from PAA to PaC.  This error is returned in a
>       PANA-Error message when the IP-Address AVP in the received
>       PANA-Address-Update-Request message is invalid.
> 
> "
> 
> [10]  Modify the AVP occurrence table as:
> 
> "
>                           +-----------------------------------------+
>                           |        Message                          |
>                           |          Type                           |
>                           +-----+-----+-----+-----+-----+-----+-----+
>       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
>       Result-Code         |  0  |  0  |  0  |  0  |  1  |  1  |  0  |
>       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
>       Termination-Cause   |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
>       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
>       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
>       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |
>       Device-Id           |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
>       Cookie              | 0-1 | 0-1 |  0  |  0  |  0  |  0  |  0  |
>       Protection-Cap.     | 0-1 |  0  |  0  |  0  | 0-1 |  0  |  0  |
>       PPAC                | 0-1 |  0  |  0  |  0  |  1  | 0-1 |  0  |
>       Session-Lifetime    |  0  |  0  |  0  |  0  | 0-1 |  0  |  0  |
>       Failed-AVP          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
>       ISP-Information     |  0+ | 0-1 |  0  |  0  |  0  |  0  |  0  |
>       NAP-Information     | 0-1 |  0  |  0  |  0  |  0  |  0  |  0  |
>       EP-Device-Id        |  0  |  0  |  0  |  0  |  0+ |  0  |  0  |
>       Key-Id              |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
>       IP-Address          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
> 
>                  Figure 11: AVP Occurrence Table (1/3)
> 
>
+---------------------------------------------+
>                           |      Message
|
>                           |       Type
|
>
+------+------+-----+-----+-----+------+------+
>       Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER |
PFEA |
>
--------------------+------+------+-----+-----+-----+------+------+
>       Result-Code         |  0   |  0   |  0  |  0  |  1  |  1   |  0
|
>       Session-Id          |  1   |  1   |  1  |  1  |  1  |  1   |  1
|
>       Termination-Cause   |  0   |  0   |  1  |  0  |  0  |  0   |  0
|
>       EAP-Payload         |  0   |  0   |  0  |  0  |  0  |  1   |  0
|
>       MAC                 | 0-1  | 0-1  | 0-1 | 0-1 | 0-1 | 0-1  | 0-1
|
>       Nonce               |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Device-Id           |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Cookie              |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Protection-Cap.     |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       PPAC                |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Session-Lifetime    |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Failed-AVP          |  0   |  0   |  0  |  0  |  1  |  0   |  0
|
>       ISP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       NAP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       EP-Device-Id        |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Key-Id              |  0   |  0   |  0  |  0  |  0  | 0-1  | 0-1
|
>       IP-Address          |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>
--------------------+------+------+-----+-----+-----+------+------+
> 
>                  Figure 12: AVP Occurrence Table (2/3)
> 
> 
>                           +-------------+
>                           |   Message   |
>                           |     Type    |
>                           +------+------+
>       Attribute Name      | PAUR | PAUA |
>       --------------------+------+------+
>       Result-Code         |  0   |  0   |
>       Session-Id          |  1   |  1   |
>       Termination-Cause   |  0   |  0   |
>       EAP-Payload         |  0   |  0   |
>       MAC                 | 0-1  | 0-1  |
>       Nonce               |  0   |  0   |
>       Device-Id           | 0-1  |  0   |
>       Cookie              |  0   |  0   |
>       Protection-Cap.     |  0   |  0   |
>       PPAC                |  0   |  0   |
>       Session-Lifetime    |  0   |  0   |
>       Failed-AVP          |  0   |  0   |
>       ISP-Information     |  0   |  0   |
>       NAP-Information     |  0   |  0   |
>       EP-Device-Id        |  0   |  0   |
>       Key-Id              |  0   |  0   |
>       IP-Address          | 0-1  |  0   |
>       --------------------+------+------+
> 
>                  Figure 13: AVP Occurrence Table (3/3)
> "
> 
> [11]  Change the text in section 7 from:
> 
> "
>          PANA-PAA-Discover (PDI)
>          PANA-Start-Request (PSR)*
>          PANA-Start-Answer (PSA)**
>          PANA-Bind-Request (PBR)
>          PANA-FirstAuth-End-Request (PFER)
>          PANA-Reauth-Request (PRAR)
>          PANA-Termination-Request (PTR)
> 
>          *)  PSR that carries a Cookie AVP is not retransmitted.
>          **) PSA that does not carry a Cookie AVP is not
retransmitted.
> "
> 
> to:
> 
> "
>          PANA-PAA-Discover (PDI)
>          PANA-Start-Request (PSR)*
>          PANA-Start-Answer (PSA)**
>          PANA-Bind-Request (PBR)
>          PANA-FirstAuth-End-Request (PFER)
>          PANA-Reauth-Request (PRAR)
>          PANA-Termination-Request (PTR)
>          PANA-Address-Update-Request (PAUR)
> 
>          *)  PSR that carries a Cookie AVP is not retransmitted.
>          **) PSA that does not carry a Cookie AVP is not
retransmitted.
> "
> 
> [12]  Add the folliwng text in section 8:
> 
> "
>    j) Updating PaC's address
> 
>    An attacker can generate a PANA-Address-Update-Request with an
>    invalid Device-Id AVP or an IP-Address AVP.  There are several
>    threats:
> 
>    - An attacker spoofs an address and registers itself with the
>    address.  If the registered address is not assigned to any PaC,
>    subsequent PANA messages sent from the PAA to the attacker will not
>    reach any node and this is not a significant harm.  If the
>    registered address is assigned to some PaC, subsequent PANA
>    messages sent from the PAA to the attacker will reach the PaC, but
>    will be silently discarded because the Session-Id is different.
> 
>    - An attacker registers other PaC with any address.  As a result,
>    subsequent PANA messages sent from the PAA to the PaC will not
>    reach the PaC.
> 
>    To avoid all those attacks against an address update, an additional
>    mechanism may be defined outside the PANA protocol for the PAA to
>    validate ownership of the address.
> "
> 
> 
> Best regards,
> 
> Yoshihiro Ohba
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 13 22:57:34 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03439
	for <pana-archive@lists.ietf.org>; Tue, 13 Jul 2004 22:57:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkVT9-0004yO-9y; Tue, 13 Jul 2004 18:09:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkU4o-0004fu-Pz
	for pana@megatron.ietf.org; Tue, 13 Jul 2004 16:40:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14969
	for <pana@ietf.org>; Tue, 13 Jul 2004 16:40:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkU4n-0000QJ-KU
	for pana@ietf.org; Tue, 13 Jul 2004 16:40:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkU0s-0007JU-00
	for pana@ietf.org; Tue, 13 Jul 2004 16:36:32 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12) id 1BkTvk-0005qb-00
	for pana@ietf.org; Tue, 13 Jul 2004 16:31:12 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0T00F014Z42Q@mailout3.samsung.com> for pana@ietf.org; Wed,
	14 Jul 2004 05:30:40 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0T00FQK4Z30I@mailout3.samsung.com> for pana@ietf.org;
	Wed, 14 Jul 2004 05:30:40 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0T00AAZ4Z1F1@mmp1.samsung.com> for
	pana@ietf.org; Wed, 14 Jul 2004 05:30:39 +0900 (KST)
Date: Tue, 13 Jul 2004 13:30:41 -0700
From: Alper Yegin <alper.yegin@samsung.com>
In-reply-to: <20040713101806.GI893@steelhead>
To: pana@ietf.org
Message-id: <029301c46918$44f9f520$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: Erik.Nordmark@sun.com
Subject: [Pana] Erik Nordmark's review comments #1
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


(re-posting......)

-----Original Message-----
From: Alper Yegin - SAIT 
Sent: Monday, July 12, 2004 1:55 PM
To: 'pana@ietf.org'
Cc: 'Erik.Nordmark@sun.com'
Subject: Erik Nordmark's review comments #1

Hello,

Please see Erik's review comments on the base spec, framework, and IPsec
documents below. I've been holding on to these until we received the
more detailed ones, but they won't be coming in for another couple of
weeks. Until than, let's start processing these ones...	


Alper
 

-----Original Message-----
From: Erik Nordmark [mailto:Erik.Nordmark@sun.com] 
Sent: Wednesday, June 16, 2004 10:38 AM
To: Alper Yegin - SAIT
Cc: Erik Nordmark; Basavaraj.Patil@nokia.com
Subject: RE: PANA review request


So I did finish the read of the document set on Friday,
but I haven't typed up the comments and some of them are
extensive.

The quick summary is:
The framework seems to be in reasonable shape but the introduction
is lacking in that it doesn't give an overview of the solved problem
and it doesn't indicate which order the naive implementor or somebody
that is trying to understand PANA should read the different documents.

The ipsec doc is mostly ok. It should probably make the distinction
between
authentication (of a user) and per-packet authentication more clear.

The pana document has significant editorial problems; by the time I'd
read
up to and including the security considerations section I finally
understood
what the features are of the protocol; reading back to front instead of
front to back would have made it easier to understand.
So editorially it needs to be better at incremental disclosure.
For instance, talking about the features/functions up front without
mentioning the packet formats and bit fields (RFC 2461 tries to do this
and might be a reasonable approach). Then talk about the packets and
what
they are for (DHCPv6 has that type of info; basically a short paragraph
per
packet.)
The document also seems to have technical omissions. The top 4 are:
 - a session is not defined. Questions like who allocates the session
id,
   whether or not a session is bidirectional or unidirectional (with
different
   ids for both ends), and what happens to the session when
reauthenticating
   and when using the mobility optimization are unstated.
 - the usage of device ID seems confused because there are some device
IDs
   that are carried in packets (L2/L3 addresses) and others that are not
   (circuit ID) but most places in the document read as if circuit ids
are
   always carried in packets; there is even an EP device ID (which is
used
   to just carry the address of the EP). Furthermore, doesn't ipsec
per-packet 
   auth rely on identifying the packet based on something else (the
IPsec SA?).
   Would it be more clear if device ID had two subclasses: local device
ID
   (e.g., cirtcuit ID) and address device ID (which would be carried in
   packets)?
 - the reauth packets seem to have completely different functions
depending
   on the direction they are sent. In one direction it is a reauth
   and in the other direction it is a keepalive. (The document even uses
   the term "keepalive" somewhere I think.) Wouldn't it be clearer
   if these were different messages?
 - the retransmission text says that a retransmitted packet has a new
sequence
   number. This makes no sense to me.

I'll type up more complete comments later.

  Erik


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 13 23:03:03 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04207
	for <pana-archive@lists.ietf.org>; Tue, 13 Jul 2004 23:03:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkVcj-0003vg-Lk; Tue, 13 Jul 2004 18:19:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkUOG-0001vu-I9
	for pana@megatron.ietf.org; Tue, 13 Jul 2004 17:00:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17322
	for <pana@ietf.org>; Tue, 13 Jul 2004 17:00:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkUOF-0005pR-0A
	for pana@ietf.org; Tue, 13 Jul 2004 17:00:39 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkUI7-0004IP-00
	for pana@ietf.org; Tue, 13 Jul 2004 16:54:20 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1BkUBw-0002Py-00
	for pana@ietf.org; Tue, 13 Jul 2004 16:47:56 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0T00N015R13U@mailout2.samsung.com> for pana@ietf.org; Wed,
	14 Jul 2004 05:47:25 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0T00CKQ5R06A@mailout2.samsung.com> for pana@ietf.org;
	Wed, 14 Jul 2004 05:47:25 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0T003SD5QYSD@mmp2.samsung.com> for
	pana@ietf.org; Wed, 14 Jul 2004 05:47:24 +0900 (KST)
Date: Tue, 13 Jul 2004 13:47:26 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <02cc01c4691a$9bd0b8f0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Subject: [Pana] Couple of announcements...
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Hello,

- PANA WG will be meeting at San Diego IETF. We made a slot request, now
we are waiting for the agenda update to reflect our request.

- We had an update on the WG charter recently. Although technically this
is called "rechartering", updates are nothing more than the text
catching up with the earlier WG decisions.

- Both requirements and security threats documents went through the IESG
review. There are few editorials fixes needed before we can proceed to
IETF last call. Please use ID-tracker at
https://datatracker.ietf.org/public/pidtracker.cgi to see the details.

Chairs



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 13 23:17:23 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04942
	for <pana-archive@lists.ietf.org>; Tue, 13 Jul 2004 23:17:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkWeW-00083O-Hc; Tue, 13 Jul 2004 19:25:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkUtj-00026h-M9
	for pana@megatron.ietf.org; Tue, 13 Jul 2004 17:33:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21355
	for <pana@ietf.org>; Tue, 13 Jul 2004 17:33:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkUth-0005gw-To
	for pana@ietf.org; Tue, 13 Jul 2004 17:33:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkUmB-0003kM-00
	for pana@ietf.org; Tue, 13 Jul 2004 17:25:24 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12) id 1BkUfm-0001x2-00
	for pana@ietf.org; Tue, 13 Jul 2004 17:18:46 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0T00901769GR@mailout1.samsung.com> for pana@ietf.org; Wed,
	14 Jul 2004 06:18:09 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0T002NQ769N7@mailout1.samsung.com> for pana@ietf.org;
	Wed, 14 Jul 2004 06:18:09 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0T00ACC766F1@mmp1.samsung.com> for
	pana@ietf.org; Wed, 14 Jul 2004 06:18:09 +0900 (KST)
Date: Tue, 13 Jul 2004 14:18:10 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] EAP-based reauth clarification [Re: Mobility Handling in
	PANA]
In-reply-to: <20040713014744.GG893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org,
        "'Giaretta Gerardo'" <Gerardo.Giaretta@TILAB.COM>
Message-id: <030501c4691e$e73f7ed0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: "'Julien Bournelle'" <Julien.Bournelle@int-evry.fr>
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> Based on the discussion below.  I would suggest adding the following
> sentences to section 4.4 of PANA speficication:
> 
> "
> When NAP and ISP separate authetnications were performed in the first
> occurence of PANA authentication phase, the same NAP and ISP separate
> authentications MUST also be performed in subsequent EAP-based
> re-authentication occurances.  Otherwise, NAP and ISP separate
> authentications MUST NOT be performed in subsequent EAP-based
> re-authentication occurances.
> "

Can this be generalized to saying the NAP/ISP selection cannot change in
a PANA session? I'm trying to understand what happens (breaks?) if the
PaC changes its selection...

Alper

> 
> Yoshihiro Ohba
> 
> 
> On Mon, Jul 12, 2004 at 05:42:11PM +0200, Giaretta Gerardo wrote:
> > Hi Yoshi,
> >
> > > > > I am not sure how EAP-based re-authentication can work after
the
> > > > > PaC has successfully established a new PANA session with nPAA
> > > > > based on the mobility optimization operation, especially with
NAP
> > > > > and ISP separated authentications.  Since PSR-PSA exchange is
> > > > > omitted in the case of EAP-based re-authentication, there is
no
> > > > > means to negotiate on NAP and ISP separate authentications
between
> >
> > > > > the PaC and nPAA.  Do you have any thoughts on this?
> > > > >
> > > >
> > > > I'm not sure I understand your point: is this a general
> > > PANA issue or
> > > > is it related to the operations described in
> > > > draft-bournelle-pana-ctp-00.txt?
> > >
> > > It might be related to both.  I think that if NAP and ISP
> > > separate authentications were made in the initial
> > > authentication, then the same NAP and ISP separate
> > > authentications should also be made in EAP-based
> > > re-authentication (this is a PANA issue, i.e., this should be
> > > described in the PANA specification.)  If the same thing
> > > needs to be done in EAP-based re-authentication after handoff
> > > (though I am not sure the same thing needs to be done in this
> > > case), information on whether NAP and ISP separate
> > > authentications were made in the previous network may need to
> > > be included in PANA-CTD (this is an issue of
> > > draft-bournelle-pana-ctp-00.txt).
> > >
> >
> > I agree with you. The result of the usage of CTP, as the result of
any
> > fast authentication mechanism, must be the same as the one obtained
> > performing the whole authentication procedure. This implies that
nPAA
> > should know if PaC performed double authentication and which ISP it
> > chose. Therefore this information must be transferred in CTD
message.
> >
> > However, I think that EAP re-authentication is not related to
mobility
> > handling. The usage of CTP allows to transfer the PANA context to
the
> > nPAA. After the PBR/PBA exchange the PaC is authenticated and the
nPAA
> > knows the residual authorization lifetime. Therefore
> > EAP-reauthentication is not performed immediately after the handoff
and
> > it is accomplished as specified in PANA specs.
> >
> > Note that we have not defined yet how to inform both NAP and ISP AAA
> > system of the new PaC's location. I think this is also an important
> > issue.
> >
> >
> > --Gerardo
> >
> >
> >
> > > Yoshihiro Ohba
> > >
> >
> >
> >
> >
> > Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia
> S.p.A.
> >
> > ====================================================================
> > CONFIDENTIALITY NOTICE
> > This message and its attachments are addressed solely to the persons
> > above and may contain confidential information. If you have received
> > the message in error, be informed that any use of the content hereof
> > is prohibited. Please return it immediately to the sender and delete
> > the message. Should you have any questions, please send an e_mail to
> > MailAdmin@tilab.com. Thank you
> > ====================================================================
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 13 23:27:20 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06663
	for <pana-archive@lists.ietf.org>; Tue, 13 Jul 2004 23:27:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkYkW-00005i-Sr; Tue, 13 Jul 2004 21:39:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkV4e-0006OV-SK
	for pana@megatron.ietf.org; Tue, 13 Jul 2004 17:44:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22793
	for <pana@ietf.org>; Tue, 13 Jul 2004 17:44:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkV4c-0000Cy-G1
	for pana@ietf.org; Tue, 13 Jul 2004 17:44:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkUxE-0006KK-00
	for pana@ietf.org; Tue, 13 Jul 2004 17:36:48 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12) id 1BkUq0-0004Sy-00
	for pana@ietf.org; Tue, 13 Jul 2004 17:29:20 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0T00H017O2V7@mailout3.samsung.com> for pana@ietf.org; Wed,
	14 Jul 2004 06:28:50 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0T00HAD7O19P@mailout3.samsung.com> for pana@ietf.org;
	Wed, 14 Jul 2004 06:28:49 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0T008OA7NZKZ@mmp2.samsung.com> for
	pana@ietf.org; Wed, 14 Jul 2004 06:28:49 +0900 (KST)
Date: Tue, 13 Jul 2004 14:28:50 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Mobility Handling in PANA
In-reply-to: <20040712113752.GJ44906@ipv6-5.int-evry.fr>
To: "'Julien Bournelle'" <Julien.Bournelle@int-evry.fr>,
        yohba@tari.toshiba.com, pana@ietf.org,
        "'Gerardo Giaretta'" <gerardo.giaretta@tilab.com>
Message-id: <030601c46920$64d66a60$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> Thus we propose this:
> 
> 
>      PaC           nPAA              pPAA
>      ----------------------------------------
>            PDI
>       -------------->
>            PSR
>      <---------------
>           PSA [old Session-ID, Nonce, CTAR]
>       --------------->
> 
>                            CT-Request
>                         -------------->
>                                CTD
>                         <--------------
> 
>       PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
>      <-------------
>       PBA[new Session-ID, Key-Id, PPAC, MAC]
>       ------------->

This is the flow I had in my mind, but I don't see the need to have an
explicit CTAR AVP in the PSA.

Looking at the draft, CTAR carries:
- PaC's address. Why do we need this? The Pac is identified with its
session id.
- PAA's address. I don't think we need this either. Session id reveals
the ID of the pPAA. It's just a matter of mapping that to an IP address
(use DNS).
- Authorization token. MAC AVP already does the job.

Alper




_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 00:06:23 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10062
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 00:06:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkaLe-0005br-27; Tue, 13 Jul 2004 23:22:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkYDj-00082X-8o
	for pana@megatron.ietf.org; Tue, 13 Jul 2004 21:06:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19195
	for <pana@ietf.org>; Tue, 13 Jul 2004 21:06:01 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkYDh-0001Kh-J3
	for pana@ietf.org; Tue, 13 Jul 2004 21:06:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkXvb-0005JD-00
	for pana@ietf.org; Tue, 13 Jul 2004 20:47:20 -0400
Received: from bay12-f18.bay12.hotmail.com ([64.4.35.18] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12) id 1BkXcU-0001NZ-00
	for pana@ietf.org; Tue, 13 Jul 2004 20:27:34 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Tue, 13 Jul 2004 17:27:04 -0700
Received: from 67.161.73.174 by by12fd.bay12.hotmail.msn.com with HTTP;
	Wed, 14 Jul 2004 00:27:04 GMT
X-Originating-IP: [67.161.73.174]
X-Originating-Email: [aeyegin@hotmail.com]
X-Sender: aeyegin@hotmail.com
From: "Alper Yegin" <aeyegin@hotmail.com>
To: pana@ietf.org
Date: Tue, 13 Jul 2004 17:27:04 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY12-F18KV4a8aYnmn0002c459@hotmail.com>
X-OriginalArrivalTime: 14 Jul 2004 00:27:04.0449 (UTC)
	FILETIME=[49BE7F10:01C46939]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id VAA19195
Subject: [Pana] test...please ignore....
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

test...please ignore....

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar =96 get it now!=20
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 04:09:41 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00885
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 04:09:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bkebt-00069s-UB; Wed, 14 Jul 2004 03:55:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkeZZ-0004kq-B6
	for pana@megatron.ietf.org; Wed, 14 Jul 2004 03:53:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29889
	for <pana@ietf.org>; Wed, 14 Jul 2004 03:52:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkeZW-0004TD-M3
	for pana@ietf.org; Wed, 14 Jul 2004 03:52:58 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkeYZ-00049r-00
	for pana@ietf.org; Wed, 14 Jul 2004 03:52:00 -0400
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx with esmtp (Exim 4.12) id 1BkeXw-0003Wc-00
	for pana@ietf.org; Wed, 14 Jul 2004 03:51:21 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I0U00B2305C4C@dns2.cselt.it> for pana@ietf.org; Wed,
	14 Jul 2004 09:44:00 +0200 (MEST)
Received: from EXC2K01A.cselt.it ([163.162.4.34]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Wed, 14 Jul 2004 09:48:49 +0200
Received: from EXC2K01B.cselt.it ([163.162.4.97]) by EXC2K01A.cselt.it with
	Microsoft SMTPSVC(5.0.2195.5329); Wed, 14 Jul 2004 09:50:50 +0200
Date: Wed, 14 Jul 2004 09:50:50 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Pana] Mobility Handling in PANA
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <625BE97BF4795E43970345790166B9BCD4DF41@EXC2K01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Pana] Mobility Handling in PANA
thread-index: AcRpIHFHyLr7KW3bRgKt8dRCQ+fI5AAUq9Rg
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 14 Jul 2004 07:50:50.0598 (UTC)
	FILETIME=[482A6860:01C46977]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Cc: Julien Bournelle <Julien.Bournelle@int-evry.fr>, yohba@tari.toshiba.com,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Alper,

>=20
> > Thus we propose this:
> >=20
> >=20
> >      PaC           nPAA              pPAA
> >      ----------------------------------------
> >            PDI
> >       -------------->
> >            PSR
> >      <---------------
> >           PSA [old Session-ID, Nonce, CTAR]
> >       --------------->
> >=20
> >                            CT-Request
> >                         -------------->
> >                                CTD
> >                         <--------------
> >=20
> >       PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> >      <-------------
> >       PBA[new Session-ID, Key-Id, PPAC, MAC]
> >       ------------->
>=20
> This is the flow I had in my mind, but I don't see the need=20
> to have an explicit CTAR AVP in the PSA.
>=20
> Looking at the draft, CTAR carries:
> - PaC's address. Why do we need this? The Pac is identified=20
> with its session id.
> - PAA's address. I don't think we need this either. Session=20
> id reveals the ID of the pPAA. It's just a matter of mapping=20
> that to an IP address (use DNS).
> - Authorization token. MAC AVP already does the job.
>

CTAR (and thus a CTAR AVP in our draft) is always required by CTP as
specified in draft-ietf-seamoby-ctp-10.txt. It is not possible to use
CTP without sending a CTAR message both in predictive and reactive mode.
This is because in CTP the transfer is authorized trough the
authorization token that is shared between pAR and MN. However, I
completely agree with you that the information carried by CTAR can be
obtained by other means as you stated above.=20

I think here the issue is whether we want to apply the Seamoby CTP or to
define a context transfer mechanism only for PANA (which exploits PANA
features).

--Gerardo



> Alper
>=20
>=20
>=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 19:34:42 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09045
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 19:34:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkqZE-000309-9R; Wed, 14 Jul 2004 16:41:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkpeG-0008Ny-T5
	for pana@megatron.ietf.org; Wed, 14 Jul 2004 15:42:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11259
	for <pana@ietf.org>; Wed, 14 Jul 2004 15:42:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkpeF-00054S-MQ
	for pana@ietf.org; Wed, 14 Jul 2004 15:42:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkpdF-0004hy-00
	for pana@ietf.org; Wed, 14 Jul 2004 15:41:34 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BkpcG-0004M1-00
	for pana@ietf.org; Wed, 14 Jul 2004 15:40:32 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6EJeQpD020138;
	Thu, 15 Jul 2004 04:40:26 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6EJePLQ027437;
	Thu, 15 Jul 2004 04:40:25 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	EAA27436 ; Thu, 15 Jul 2004 04:40:25 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA13316; Thu, 15 Jul 2004 04:40:25 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA04441;
	Thu, 15 Jul 2004 04:40:25 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6EJeOpl010205;
	Thu, 15 Jul 2004 04:40:24 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0U00G97XB7ON@tsbpo1.po.toshiba.co.jp>; Thu,
	15 Jul 2004 04:40:23 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BkpbT-0006MQ-00; Wed, 14 Jul 2004 12:39:43 -0700
Date: Wed, 14 Jul 2004 15:39:43 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (initial text)
In-reply-to: <023e01c4690a$6c6fc430$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040714193943.GO893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040519015123.GC29343@steelhead>
	<023e01c4690a$6c6fc430$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Tue, Jul 13, 2004 at 11:51:34AM -0700, Alper Yegin wrote:
> Yoshi,
> 
> I'd suggest to have a more generic PANA message, such as "PANA-Update".
> Initially we can use this just to update the IP address of PaC. We can
> evaluate other types of updates as need arises. What do you think?

I think we can do that.

> 
> Also, I didn't understand where Device-ID comes into the picture. When
> do we update the device-ID?

- When an IP address is used as the device identifier, it can change
if the PaC configures its temporary link-local address based on RFC
3041 and the lifetime of the temporary address is expired.

- When a MAC address is used as the device identifer, it can change if
the PaC has multiple interfaces to the same link and switches from one
interface to another.

Yoshihiro Ohba


> 
> I have some editorial comments as well. I'll wait for your response to
> these first.
> 
> Alper
> 
> 
> 
> > -----Original Message-----
> > From: pana-admin@ietf.org [mailto:pana-admin@ietf.org] On Behalf Of
> > Yoshihiro Ohba
> > Sent: Tuesday, May 18, 2004 6:51 PM
> > To: pana@ietf.org
> > Subject: [Pana] issue85 (initial text)
> > 
> > This is the initial text for issue 85.
> > 
> > Comments are appreciated.
> > 
> > ----------
> > 
> > 
> > [1] Add the following item in section 4.1.1
> > 
> > "
> >    o  IP-Address AVP: Conveys an IP-Address of a PaC.
> > "
> > 
> > 
> > [2] Add the following items in section 4.1.5:
> > 
> > "
> >       *  IP address of PaC (may be the same as the Device-Id of PaC)
> > 
> >       *  IP address of PAA (may be the same as the Device-Id of PAA)
> > "
> > 
> > 
> > [3] Add the following item in section section 4.1.7:
> > 
> > "
> >       When an IP-Address AVP is included, the AVP is valid if (i) the
> >       Address type contained in the AVP matches the expected one
> >       (i.e., either IPv4 or IPv6) that is used for the current PANA
> >       session and (ii) the AVP value matches the one extracted from
> >       the IP header.
> > "
> > 
> > [4] Update the following paragraph of section 4.4
> > 
> > "
> >    The second type of re-authentication is based on a single protected
> >    message exchange without entering the authentication phase.
> >    PANA-Reauth-Request and PANA-Reauth-Answer messages are used for
> this
> >    purpose.  If there is an established PANA SA, both the PaC and the
> >    PAA are allowed to send a PANA-Reauth-Request message to the
> >    communicating peer whenever it needs to make sure the availability
> of
> >    the PANA SA on the peer and expect the peer to return a PANA-
> >    Reauth-Answer message.  Both PANA-Reauth-Request/
> PANA-Reauth-Answer
> >    messages MUST be protected with a MAC AVP.
> > "
> > 
> > to:
> > 
> > "
> >    The second type of re-authentication is based on a single protected
> >    message exchange without entering the authentication phase.
> >    PANA-Reauth-Request and PANA-Reauth-Answer messages are used for
> >    this purpose.  If there is an established PANA SA, both the PaC and
> >    the PAA are allowed to send a PANA-Reauth-Request message to the
> >    communicating peer whenever it needs to make sure the availability
> >    of the PANA SA on the peer and expect the peer to return a
> >    PANA-Reauth-Answer message.  In this case, both
> >    PANA-Reauth-Request/PANA-Reauth-Answer messages MUST be protected
> >    with a MAC AVP.  If there is an established PANA session but
> >    without an established PANA SA, both the PaC and the PAA are
> >    allowed to send a PANA-Reauth-Request message to the communicating
> >    peer whenever it needs to make sure the availability of the PANA
> >    session on the peer and expect the peer to return a
> >    PANA-Reauth-Answer message.  In this case, both
> >    PANA-Reauth-Request/PANA-Reauth-Answer messages are not protected
> >    with a MAC AVP.
> > "
> > 
> > [5] Insert the following section after section 4.7:
> > 
> > "
> > 4.8. Updating PaC's Address
> > 
> > A PaC's address can change in certain situations.  For example, the
> > PANA framework [I-D.ietf-pana-framework] describes a case in which a
> > PaC replaces a pre-PANA address (PRPA) a post-PANA address (POPA), and
> > the PaC and PAA create host routes to each other in order to maintain
> > on-link communication based on the POPA where the link-layer address
> > of the PaC is used as the device identifier.  Also, a PaC's device
> > identifier may change regardless of whether a link-layer address or an
> > IP address is used as the device identifier.  As a result, it is
> > possible when a link-layer address is used as the device identifier
> > that both the device identifier and an IP address change.  In any
> > case, the PAA needs to be notified about the change of address(es).
> > 
> > After the PaC has changed its address(es), it MUST send a
> > PANA-Address-Update-Request message to the PAA.  The message carries
> > the new address(es) in a Device-Id AVP and/or an IP-Address AVP.  At
> > least one of these AVPs MUST appear in the request.  If an IP address
> > is used as the device identifier, a Device-Id AVP MUST be used and an
> > IP-Address AVP MUST NOT be used.  If an address contained in the
> > request is invalid, the PAA sends a PANA-Error message with a result
> > code PANA_INVALID_DEVICE_ID or PANA_INVALID_IP_ADDRESS depending on
> > whether the device identifier or the IP address is invalid (in case
> > both a Device-Id AVP and an IP-Address AVP are included and both are
> > invalid, whichever result code is returned).  Otherwise, the PAA
> > updates the address(es) of the PaC of the session attributes and
> > returns a PANA-Address-Update-Answer message.  If there is an
> > established PANA SA, both PANA-Address-Update-Request and
> > PANA-Address-Update-Answer messages MUST be protected with a MAC AVP.
> > "
> > 
> > [6] Change Figure 10 to:
> > 
> > "
> >                  Message                     Direction:
> >                                              PaC---PAA
> >                  ----------------------------------------
> >                  PANA-PAA-Discover           -------->
> > 
> >                  PANA-Start-Request          <--------
> >                  PANA-Start-Answer           -------->
> > 
> >                  PANA-Auth-Request           <--------
> >                  PANA-Auth-Answer            -------->
> > 
> >                  PANA-FirstAuth-End-Request  <--------
> >                  PANA-FirstAuth-End-Answer   -------->
> > 
> >                  PANA-Bind-Request           <--------
> >                  PANA-Bind-Answer            -------->
> > 
> >                  PANA-Reauth-Request         <------->
> >                  PANA-Reauth-Answer          <------->
> > 
> >                  PANA-Termination-Request    <------->
> >                  PANA-Termination-Answer     <------->
> > 
> >                  PANA-Address-Update-Request -------->
> >                  PANA-Address-Update-Answer  <--------
> > 
> >                  PANA-Error                  <------->
> > "
> > 
> > [7] Change sections 6.4.9 and 6.4.10 from:
> > 
> > "
> > 6.4.9 PANA-Reauth-Request (PRAR)
> > 
> >    PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
> > 
> >          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
> >                        < Session-Id >
> >                        [ Device-Id ]
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> > 
> > 
> > 6.4.10 PANA-Reauth-Answer (PRAA)
> > 
> >    PANA-Reauth-Answer (PRAA) is sent in response to a
> >    PANA-Reauth-Request.
> > 
> >          PANA-Reauth-Answer ::= < PANA-Header: 5 >
> >                        < Session-Id >
> >                        [ Device-Id ]
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> > "
> > 
> > to:
> > 
> > "
> > 6.4.9 PANA-Reauth-Request (PRAR)
> > 
> >    PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
> > 
> >          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
> >                        < Session-Id >
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> > 
> > 
> > 6.4.10 PANA-Reauth-Answer (PRAA)
> > 
> >    PANA-Reauth-Answer (PRAA) is sent in response to a
> >    PANA-Reauth-Request.
> > 
> >          PANA-Reauth-Answer ::= < PANA-Header: 5 >
> >                        < Session-Id >
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> > "
> > 
> > [8] Add the following sections:
> > 
> > "
> > 6.4.16 PANA-Address-Update-Request (PAUR)
> > 
> >    PANA-Address-Update-Request (PAUR) is sent by the PaC to the PAA.
> > 
> >          PANA-Address-Update-Request ::= < PANA-Header: 9, REQ >
> >                        < Session-Id >
> >                    0*1 { Device-Id }
> >                    0*1 { IP-Address }
> >                    0*1 < MAC >
> > 
> > 
> > 6.4.17 PANA-Address-Update-Answer (PAUA)
> > 
> >    PANA-Address-Update-Answer (PAUA) is sent by the PAA to the PaC in
> >    response to a PANA-Address-Update-Request.
> > 
> >          PANA-Address-Update-Answer ::= < PANA-Header: 9 >
> >                        < Session-Id >
> >                    0*1 < MAC >
> > "
> > 
> > "
> > 6.5.19 IP-Address AVP
> > 
> >    The IP-Address (AVP Code: 1041) contains an IP address of a PaC.
> >    The payload format of the IP-Address AVP is the same as that of the
> >    Device-Id AVP (see See section Section 6.5.2).  Address families
> >    for IPv4 or IPv6 MUST be used for this AVP.
> > "
> > 
> > 
> > [9] Add the following result code in section 6.5.7.2:
> > 
> > "
> >    PANA_INVALID_DEVICE_ID  5019
> > 
> >       Error code from PAA to PaC or from PaC to PAA.  This error is
> >       returned in a PANA-Error message when the Device-Id AVP
> >       contained in a received PANA-Bind-Request, PANA-Bind-Answer or
> >       PANA-Address-Update-Request message is invalid.
> > 
> >    PANA_INVALID_IP_ADDRESS  5020
> > 
> >       Error code from PAA to PaC.  This error is returned in a
> >       PANA-Error message when the IP-Address AVP in the received
> >       PANA-Address-Update-Request message is invalid.
> > 
> > "
> > 
> > [10]  Modify the AVP occurrence table as:
> > 
> > "
> >                           +-----------------------------------------+
> >                           |        Message                          |
> >                           |          Type                           |
> >                           +-----+-----+-----+-----+-----+-----+-----+
> >       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
> >       --------------------+-----+-----+-----+-----+-----+-----+-----+
> >       Result-Code         |  0  |  0  |  0  |  0  |  1  |  1  |  0  |
> >       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
> >       Termination-Cause   |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
> >       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
> >       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
> >       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |
> >       Device-Id           |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
> >       Cookie              | 0-1 | 0-1 |  0  |  0  |  0  |  0  |  0  |
> >       Protection-Cap.     | 0-1 |  0  |  0  |  0  | 0-1 |  0  |  0  |
> >       PPAC                | 0-1 |  0  |  0  |  0  |  1  | 0-1 |  0  |
> >       Session-Lifetime    |  0  |  0  |  0  |  0  | 0-1 |  0  |  0  |
> >       Failed-AVP          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
> >       ISP-Information     |  0+ | 0-1 |  0  |  0  |  0  |  0  |  0  |
> >       NAP-Information     | 0-1 |  0  |  0  |  0  |  0  |  0  |  0  |
> >       EP-Device-Id        |  0  |  0  |  0  |  0  |  0+ |  0  |  0  |
> >       Key-Id              |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
> >       IP-Address          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
> >       --------------------+-----+-----+-----+-----+-----+-----+-----+
> > 
> >                  Figure 11: AVP Occurrence Table (1/3)
> > 
> >
> +---------------------------------------------+
> >                           |      Message
> |
> >                           |       Type
> |
> >
> +------+------+-----+-----+-----+------+------+
> >       Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER |
> PFEA |
> >
> --------------------+------+------+-----+-----+-----+------+------+
> >       Result-Code         |  0   |  0   |  0  |  0  |  1  |  1   |  0
> |
> >       Session-Id          |  1   |  1   |  1  |  1  |  1  |  1   |  1
> |
> >       Termination-Cause   |  0   |  0   |  1  |  0  |  0  |  0   |  0
> |
> >       EAP-Payload         |  0   |  0   |  0  |  0  |  0  |  1   |  0
> |
> >       MAC                 | 0-1  | 0-1  | 0-1 | 0-1 | 0-1 | 0-1  | 0-1
> |
> >       Nonce               |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Device-Id           |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Cookie              |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Protection-Cap.     |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       PPAC                |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Session-Lifetime    |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Failed-AVP          |  0   |  0   |  0  |  0  |  1  |  0   |  0
> |
> >       ISP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       NAP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       EP-Device-Id        |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Key-Id              |  0   |  0   |  0  |  0  |  0  | 0-1  | 0-1
> |
> >       IP-Address          |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >
> --------------------+------+------+-----+-----+-----+------+------+
> > 
> >                  Figure 12: AVP Occurrence Table (2/3)
> > 
> > 
> >                           +-------------+
> >                           |   Message   |
> >                           |     Type    |
> >                           +------+------+
> >       Attribute Name      | PAUR | PAUA |
> >       --------------------+------+------+
> >       Result-Code         |  0   |  0   |
> >       Session-Id          |  1   |  1   |
> >       Termination-Cause   |  0   |  0   |
> >       EAP-Payload         |  0   |  0   |
> >       MAC                 | 0-1  | 0-1  |
> >       Nonce               |  0   |  0   |
> >       Device-Id           | 0-1  |  0   |
> >       Cookie              |  0   |  0   |
> >       Protection-Cap.     |  0   |  0   |
> >       PPAC                |  0   |  0   |
> >       Session-Lifetime    |  0   |  0   |
> >       Failed-AVP          |  0   |  0   |
> >       ISP-Information     |  0   |  0   |
> >       NAP-Information     |  0   |  0   |
> >       EP-Device-Id        |  0   |  0   |
> >       Key-Id              |  0   |  0   |
> >       IP-Address          | 0-1  |  0   |
> >       --------------------+------+------+
> > 
> >                  Figure 13: AVP Occurrence Table (3/3)
> > "
> > 
> > [11]  Change the text in section 7 from:
> > 
> > "
> >          PANA-PAA-Discover (PDI)
> >          PANA-Start-Request (PSR)*
> >          PANA-Start-Answer (PSA)**
> >          PANA-Bind-Request (PBR)
> >          PANA-FirstAuth-End-Request (PFER)
> >          PANA-Reauth-Request (PRAR)
> >          PANA-Termination-Request (PTR)
> > 
> >          *)  PSR that carries a Cookie AVP is not retransmitted.
> >          **) PSA that does not carry a Cookie AVP is not
> retransmitted.
> > "
> > 
> > to:
> > 
> > "
> >          PANA-PAA-Discover (PDI)
> >          PANA-Start-Request (PSR)*
> >          PANA-Start-Answer (PSA)**
> >          PANA-Bind-Request (PBR)
> >          PANA-FirstAuth-End-Request (PFER)
> >          PANA-Reauth-Request (PRAR)
> >          PANA-Termination-Request (PTR)
> >          PANA-Address-Update-Request (PAUR)
> > 
> >          *)  PSR that carries a Cookie AVP is not retransmitted.
> >          **) PSA that does not carry a Cookie AVP is not
> retransmitted.
> > "
> > 
> > [12]  Add the folliwng text in section 8:
> > 
> > "
> >    j) Updating PaC's address
> > 
> >    An attacker can generate a PANA-Address-Update-Request with an
> >    invalid Device-Id AVP or an IP-Address AVP.  There are several
> >    threats:
> > 
> >    - An attacker spoofs an address and registers itself with the
> >    address.  If the registered address is not assigned to any PaC,
> >    subsequent PANA messages sent from the PAA to the attacker will not
> >    reach any node and this is not a significant harm.  If the
> >    registered address is assigned to some PaC, subsequent PANA
> >    messages sent from the PAA to the attacker will reach the PaC, but
> >    will be silently discarded because the Session-Id is different.
> > 
> >    - An attacker registers other PaC with any address.  As a result,
> >    subsequent PANA messages sent from the PAA to the PaC will not
> >    reach the PaC.
> > 
> >    To avoid all those attacks against an address update, an additional
> >    mechanism may be defined outside the PANA protocol for the PAA to
> >    validate ownership of the address.
> > "
> > 
> > 
> > Best regards,
> > 
> > Yoshihiro Ohba
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 19:44:22 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10567
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 19:44:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkrjC-0001GV-1P; Wed, 14 Jul 2004 17:55:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkpi7-0001AH-LG
	for pana@megatron.ietf.org; Wed, 14 Jul 2004 15:46:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11688
	for <pana@ietf.org>; Wed, 14 Jul 2004 15:46:33 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkpi5-0006WQ-SK
	for pana@ietf.org; Wed, 14 Jul 2004 15:46:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkph7-0006Ap-00
	for pana@ietf.org; Wed, 14 Jul 2004 15:45:34 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bkpg4-0005nV-00
	for pana@ietf.org; Wed, 14 Jul 2004 15:44:28 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6EJiOpD021192;
	Thu, 15 Jul 2004 04:44:24 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6EJiO84028476;
	Thu, 15 Jul 2004 04:44:24 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	EAA28475 ; Thu, 15 Jul 2004 04:44:24 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA14041; Thu, 15 Jul 2004 04:44:23 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA05655;
	Thu, 15 Jul 2004 04:44:23 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6EJiMpl011511;
	Thu, 15 Jul 2004 04:44:22 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0U00GAJXHOON@tsbpo1.po.toshiba.co.jp>; Thu,
	15 Jul 2004 04:44:22 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bkpey-0006NO-00; Wed, 14 Jul 2004 12:43:20 -0700
Date: Wed, 14 Jul 2004 15:43:20 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New: [issue98] Lost answer problem
In-reply-to: <023501c46901$97596b00$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040714194319.GP893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
	pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040713101806.GI893@steelhead>
	<023501c46901$97596b00$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Tue, Jul 13, 2004 at 10:48:20AM -0700, Alper Yegin wrote:
> > > OK, then I think this is not a protocol issue and I'd propose
> discussing
> > > this in the state machine I-D.  As long as the request is not
> rejected,
> > > the PaC should be able to produce a response .
> > 
> > I think it is a protocol matter to specify in which condition a
> > request should be accepted or rejected.  For example, the PANA
> > specification should be clear on what to do when a PaC receives a
> > previously received PBR for which it has already sent a PBA.
> 
> The default action would be to respond to the request (unless there is a
> statement in the draft that makes an exception).

There would be the following exceptions:

o In discovery and initial handshake phase,

  - PTR and PRAR is rejected.
  - PBR is rejected.
  - PAUR is rejected.

o In authentication phase, 

  - PTR and PRAR is rejected.
  - PAUR is rejected.
  - PSR is rejected after PaC receives the first vaild PAR.

o After successful PANA authentication,

 - PSR as well as a non-duplicate PBR is rejected.
 - PDI without a Session-Id AVP (i.e., initial authentication) is rejected.

o In termination phase,

 - All requests but PTR is rejected.

I think both the default action as well as these exceptions should be
described in the specification.

Yoshihiro Ohba


> 
> Alper
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 19:44:35 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10620
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 19:44:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BkrkC-0001Lr-Ga; Wed, 14 Jul 2004 17:56:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkpk5-0001kD-Ci
	for pana@megatron.ietf.org; Wed, 14 Jul 2004 15:48:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11785
	for <pana@ietf.org>; Wed, 14 Jul 2004 15:48:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkpk4-00079p-3O
	for pana@ietf.org; Wed, 14 Jul 2004 15:48:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkpiz-0006pk-00
	for pana@ietf.org; Wed, 14 Jul 2004 15:47:30 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bkpi0-0006Vo-00
	for pana@ietf.org; Wed, 14 Jul 2004 15:46:29 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6EJkRpD021708;
	Thu, 15 Jul 2004 04:46:27 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6EJkRXo029108;
	Thu, 15 Jul 2004 04:46:27 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	EAA29105 ; Thu, 15 Jul 2004 04:46:27 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA14578; Thu, 15 Jul 2004 04:46:26 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA25073;
	Thu, 15 Jul 2004 04:46:25 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6EJkPpl012239;
	Thu, 15 Jul 2004 04:46:25 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0U00GB4XL4ON@tsbpo1.po.toshiba.co.jp>; Thu,
	15 Jul 2004 04:46:24 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BkphJ-0006O6-00; Wed, 14 Jul 2004 12:45:45 -0700
Date: Wed, 14 Jul 2004 15:45:45 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Mobility Handling in PANA
In-reply-to: <20040713132542.GY45745@ipv6-5.int-evry.fr>
To: Julien Bournelle <Julien.Bournelle@int-evry.fr>
Message-id: <20040714194545.GQ893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Julien Bournelle <Julien.Bournelle@int-evry.fr>,
	yohba@tari.toshiba.com, pana@ietf.org,
	Gerardo Giaretta <gerardo.giaretta@tilab.com>
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BCE8D6B2@EXC2K01B.cselt.it>
	<20040710062738.GD893@steelhead>
	<20040712101804.GF44906@ipv6-5.int-evry.fr>
	<20040712111907.GT893@steelhead>
	<20040712113752.GJ44906@ipv6-5.int-evry.fr>
	<20040712123404.GX893@steelhead>
	<20040712143702.GA45745@ipv6-5.int-evry.fr>
	<20040712222745.GA893@steelhead>
	<20040713132542.GY45745@ipv6-5.int-evry.fr>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Gerardo Giaretta <gerardo.giaretta@tilab.com>, yohba@tari.toshiba.com,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Tue, Jul 13, 2004 at 03:25:42PM +0200, Julien Bournelle wrote:
> hi yoshi,
> 
> On Mon, Jul 12, 2004 at 06:27:45PM -0400, Yoshihiro Ohba wrote:
> > 
> > I just meant "not piggybacking other protocol messages" by modularity.
> 
> I understand your point.
> At the beginning, we thought about this approach but as the nPAA sends a
> PANA message, we wanted to answer with a PSA message and not a CTAR
> message.
> 
> > I think both non-piggybacking and piggybacking schemes should be
> > allowed in the design.  Non-piggybacking scheme allows other mobility
> > optimization schemes also to be used by PANA, while piggybacking
> > scheme provides optimization for a particular mobility optimization
> > scheme
> 
> do you think that we could live with the 2 options running in the same
> time ? 

If the PAA supports both methods, the 2 options should work at the
same time.  If a PaC supports non-piggybacking CTAR, then context
transfer completes before the a PAA receives a PSA.  When the PAA
receives the PSA, the PAA tries to retrieve a new AAA-Key locally from
its context transfer module to generate a PBR.  On the other hand, if
a PaC supports piggybacking CTAR, then the PAA passes the CTAR to the
context transfer module and waits for the context transfer operation
to complete.  Once the context transfer operation completes, the PAA
retrives a new AAA-Key from the context transfer module and generates
a PBR.

Yoshihiro Ohba

> 
> .
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Mon, Jul 12, 2004 at 04:37:02PM +0200, Julien Bournelle wrote:
> > > > Since PANA and CTP are different protocols, I think nPAA can wait for
> > > > messages from both protocols at the same time without violating both
> > > > protocols.  But parhaps it is better in this case that CTAR is
> > > > acknowledged with CTAA and the PaC sends PSA after receiving CTAA to
> > > > provide synchronization bewteen context transfer operation and PANA
> > > > mobility optimization, something like:
> > > > 
> > > > PaC           nPAA              pPAA
> > > > ----------------------------------------
> > > >       PDI
> > > >  -------------->
> > > >       PSR
> > > >  <---------------
> > > >       CTAR
> > > >  --------------->
> > > >                      CT-Request 
> > > >                   -------------->
> > > >                          CTD 
> > > >                   <--------------
> > > >       CTAA
> > > >  <--------------
> > > > 
> > > >   PSA[old Session-ID, Nonce, MAC]
> > > >   --------------->
> > > >   PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> > > >   <-------------
> > > >   PBA[new Session-ID, Key-Id, PPAC, MAC]
> > > >   ------------->
> > > > 
> > > > Comparing this scheme with your scheme below, the discussion point
> > > > would be modularity (this sheme) vs optimization (your scheme).
> > > 
> > > I think that with our solution we keep the modularity since the pana
> > > module asks to the ctp module the CTAR message to be sent.
> > > 
> > > In your scenario, the PANA module at PaC receives the PSR message and
> > > contacts the CTP module (saying that CTP module must sent a CTAR).
> > > In our scenario, the PANA module asks to the CTP module the CTAR
> > > message and embeds it. Thus I think that we keep the modularity.
> > > 
> > > Maybe I miss something, what do you mean by modularity ?
> > > 
> > > > 
> > > > Yoshihiro Ohba
> > > > 
> > > > > 
> > > > > This is why we propose to emebed the CTAR message in the PSR message.
> > > > > Thus the pac answers with a PSA message. The PANA module at the pac aks
> > > > > to the CTP module to get a valid CTAR message and embeds it in the PSA
> > > > > message. The nPAA receives the PSA message that it is waiting for and
> > > > > sees that it contains a CTAR message. It delivers it to its CTP module
> > > > > and waits the CT-Request/CTD exchange. This why we introduce a new state
> > > > > in the state machine (PANA-CTP-WAITING)
> > > > > 
> > > > > 
> > > > > Thus we propose this:
> > > > > 
> > > > > 
> > > > >      PaC           nPAA              pPAA
> > > > >      ----------------------------------------
> > > > >            PDI
> > > > >       -------------->
> > > > >            PSR
> > > > >      <---------------
> > > > >           PSA [old Session-ID, Nonce, CTAR] 
> > > > >       --------------->
> > > > >  
> > > > >                            CT-Request 
> > > > >                         -------------->
> > > > >                                CTD 
> > > > >                         <--------------
> > > > > 
> > > > >       PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> > > > >      <-------------
> > > > >       PBA[new Session-ID, Key-Id, PPAC, MAC]
> > > > >       ------------->
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > -- 
> > > > > julien.bournelle@int-evry.fr
> > > > 
> > > 
> > > -- 
> > > julien.bournelle@int-evry.fr
> > > 
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > 
> 
> -- 
> julien.bournelle@int-evry.fr
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 19:45:17 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10771
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 19:45:17 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bkrkc-0001iC-U1; Wed, 14 Jul 2004 17:57:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkppp-0002mU-BT
	for pana@megatron.ietf.org; Wed, 14 Jul 2004 15:54:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12290
	for <pana@ietf.org>; Wed, 14 Jul 2004 15:54:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkppo-0001XS-8L
	for pana@ietf.org; Wed, 14 Jul 2004 15:54:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkpon-0001DI-00
	for pana@ietf.org; Wed, 14 Jul 2004 15:53:30 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bkpnv-0000sR-00
	for pana@ietf.org; Wed, 14 Jul 2004 15:52:36 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6EJqZpD023151;
	Thu, 15 Jul 2004 04:52:35 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6EJqZ7D000572;
	Thu, 15 Jul 2004 04:52:35 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	EAA00571 ; Thu, 15 Jul 2004 04:52:35 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA15666; Thu, 15 Jul 2004 04:52:34 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA08515;
	Thu, 15 Jul 2004 04:52:33 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6EJqXpl014252;
	Thu, 15 Jul 2004 04:52:33 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0U00GDLXVHON@tsbpo1.po.toshiba.co.jp>; Thu,
	15 Jul 2004 04:52:32 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BkpnY-0006PI-00; Wed, 14 Jul 2004 12:52:12 -0700
Date: Wed, 14 Jul 2004 15:52:12 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
In-reply-to: <625BE97BF4795E43970345790166B9BCD4DF3C@EXC2K01B.cselt.it>
To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Message-id: <20040714195212.GR893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>,
	Yoshihiro Ohba <yohba@tari.toshiba.com>,
	Julien Bournelle <Julien.Bournelle@int-evry.fr>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BCD4DF3C@EXC2K01B.cselt.it>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Subject: [Pana] Re: EAP-based reauth clarification [Re: Mobility Handling in
	PANA]
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Tue, Jul 13, 2004 at 02:37:55PM +0200, Giaretta Gerardo wrote:
> Yoshihiro Ohba wrote:  
> > 
> > Based on the discussion below.  I would suggest adding the
> > following sentences to section 4.4 of PANA speficication:
> > 
> > "
> > When NAP and ISP separate authetnications were performed in 
> > the first occurence of PANA authentication phase, the same 
> > NAP and ISP separate authentications MUST also be performed 
> > in subsequent EAP-based re-authentication occurances.  
> > Otherwise, NAP and ISP separate authentications MUST NOT be 
> > performed in subsequent EAP-based re-authentication occurances. "
> >
> 
> Just two comments:
> 
> [1] A similar text is provided in section 4.9: 
> 
> "
>    When separate EAP authentications are performed for ISP and NAP in a
>    single PANA session, it is possible that different authorization
>    lifetime values are associated with the two authentications.  In this
>    case, the smaller authorization lifetime value MUST be used for
>    calculating the PANA Session-Lifetime value.  As a result, when
>    EAP-based re-authentication occurs, both NAP and ISP authentications
>    will be performed in the same re-authentication procedure.
> "
> 
> Is this really needed? I mean, it could be unefficient to perform both
> the authentications if only one is required. This is a consequence that
> the PANA Session Lifetime is equal to the smaller authorization lifetime
> value. 
> I'm thinking if it is possible to manage the lifetimes in order to
> perform only the authentication that is required. Do you have any
> thoughts on this?

I had a couple of thoughts on that before the current solution, but
there are many issues as described below.

> 
> A possible solution could be (however I'm not sure if this works):
> 
> PANA session lifetime = min (Residual NAP auth. Lifetime, Residual ISP
> auth. Lifetime) 
> 
> In this way, only the required re-authentication is performed and the
> PANA session lifetime is re-calculated at the end of each
> re-authentication. 

- Should the S-bit set if the EAP re-authentication with a single EAP
run is performed?

- Which exchange should be used for carrying authenticaiton result for
the EAP re-authentication with a single EAP run, PBR-PBA or PFER-PFEA?

- What happens if the EAP re-authentication with a single EAP run (for
NAP authentication for example) fails?  Should the PANA session be
deleted, or remain because authorization for ISP part still exists?
In the latter case, are the subsequent EAP-reauthentications always
performed with a single EAP run for ISP authentication?  And also in
the latter case is the PANA_MAC_KEY needs to be updated after the
single EAP run failure in the EAP re-authentication?  If so, how?

> However there might be cases in which it is
> convenient to perform both the authentications together (e.g. the
> difference between the residual lifetimes is very small). 

> 
> [2] What about a scenario in which a new ISP is available? Consider that
> at the first occurence of PANA there were only two ISPs available (ISP1
> and ISP2). If a new ISP (ISP3) becomes available (e.g. after a movement
> of the PaC), I think this must be communicated to the PaC. How can we
> handle this?

After a movement of a PaC, the new ISP information can be contained in
PSR sent from the new PAA.  However, if the PaC returns a PSA with
ISP3 information in a ISP-Information AVP, the PAA should not perform
mobility optimization.

In the case where a new ISP becomes available while the PaC is
connecting to the same PAA, I don't think the PaC has to know the new
ISP immediately.

Yoshihiro Ohba




> 
> 
> --Gerardo
> 
>  
> > Yoshihiro Ohba
> > 
> > 
> > On Mon, Jul 12, 2004 at 05:42:11PM +0200, Giaretta Gerardo wrote:
> > > Hi Yoshi,
> > > 
> > > > > > I am not sure how EAP-based re-authentication can 
> > work after the
> > > > > > PaC has successfully established a new PANA session with nPAA 
> > > > > > based on the mobility optimization operation, 
> > especially with NAP 
> > > > > > and ISP separated authentications.  Since PSR-PSA exchange is 
> > > > > > omitted in the case of EAP-based re-authentication, 
> > there is no 
> > > > > > means to negotiate on NAP and ISP separate 
> > authentications between
> > > 
> > > > > > the PaC and nPAA.  Do you have any thoughts on this?
> > > > > > 
> > > > > 
> > > > > I'm not sure I understand your point: is this a general
> > > > PANA issue or
> > > > > is it related to the operations described in 
> > > > > draft-bournelle-pana-ctp-00.txt?
> > > > 
> > > > It might be related to both.  I think that if NAP and ISP 
> > separate 
> > > > authentications were made in the initial authentication, then the 
> > > > same NAP and ISP separate authentications should also be made in 
> > > > EAP-based re-authentication (this is a PANA issue, i.e., 
> > this should 
> > > > be described in the PANA specification.)  If the same thing
> > > > needs to be done in EAP-based re-authentication after handoff 
> > > > (though I am not sure the same thing needs to be done in this 
> > > > case), information on whether NAP and ISP separate 
> > > > authentications were made in the previous network may need to 
> > > > be included in PANA-CTD (this is an issue of 
> > > > draft-bournelle-pana-ctp-00.txt).
> > > >
> > > 
> > > I agree with you. The result of the usage of CTP, as the 
> > result of any 
> > > fast authentication mechanism, must be the same as the one obtained 
> > > performing the whole authentication procedure. This implies 
> > that nPAA 
> > > should know if PaC performed double authentication and which ISP it 
> > > chose. Therefore this information must be transferred in 
> > CTD message.
> > > 
> > > However, I think that EAP re-authentication is not related 
> > to mobility 
> > > handling. The usage of CTP allows to transfer the PANA 
> > context to the 
> > > nPAA. After the PBR/PBA exchange the PaC is authenticated 
> > and the nPAA 
> > > knows the residual authorization lifetime. Therefore 
> > > EAP-reauthentication is not performed immediately after the handoff 
> > > and it is accomplished as specified in PANA specs.
> > > 
> > > Note that we have not defined yet how to inform both NAP 
> > and ISP AAA 
> > > system of the new PaC's location. I think this is also an important 
> > > issue.
> > > 
> > > 
> > > --Gerardo
> > > 
> > > 
> > >  
> > > > Yoshihiro Ohba
> > > > 
> > > 
> > > 
> > > 
> > > 
> > > Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia 
> > > S.p.A.
> > > 
> > > ====================================================================
> > > CONFIDENTIALITY NOTICE
> > > This message and its attachments are addressed solely to 
> > the persons 
> > > above and may contain confidential information. If you have 
> > received 
> > > the message in error, be informed that any use of the 
> > content hereof 
> > > is prohibited. Please return it immediately to the sender 
> > and delete 
> > > the message. Should you have any questions, please send an 
> > e_mail to 
> > > MailAdmin@tilab.com. Thank you 
> > > ====================================================================
> > 
> 
> 
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
> 
> ====================================================================
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to
> MailAdmin@tilab.com. Thank you
> ====================================================================

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 19:45:38 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10849
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 19:45:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bkrke-0001ij-Cw; Wed, 14 Jul 2004 17:57:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkpqr-00037T-MY
	for pana@megatron.ietf.org; Wed, 14 Jul 2004 15:55:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12370
	for <pana@ietf.org>; Wed, 14 Jul 2004 15:55:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkpqq-0001sf-Di
	for pana@ietf.org; Wed, 14 Jul 2004 15:55:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkpq3-0001ZT-00
	for pana@ietf.org; Wed, 14 Jul 2004 15:54:47 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BkppO-0001FW-00
	for pana@ietf.org; Wed, 14 Jul 2004 15:54:06 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6EJs6pD023544;
	Thu, 15 Jul 2004 04:54:06 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6EJs5Dv001042;
	Thu, 15 Jul 2004 04:54:05 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	EAA01041 ; Thu, 15 Jul 2004 04:54:05 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA15957; Thu, 15 Jul 2004 04:54:05 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA27768;
	Thu, 15 Jul 2004 04:54:04 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6EJs4pl014741;
	Thu, 15 Jul 2004 04:54:04 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0U00GE6XY0ON@tsbpo1.po.toshiba.co.jp>; Thu,
	15 Jul 2004 04:54:03 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BkpoW-0006QR-00; Wed, 14 Jul 2004 12:53:12 -0700
Date: Wed, 14 Jul 2004 15:53:12 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-based reauth clarification [Re: Mobility Handling in
	PANA]
In-reply-to: <030501c4691e$e73f7ed0$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040714195312.GS893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org,
	'Giaretta Gerardo' <Gerardo.Giaretta@TILAB.COM>,
	'Julien Bournelle' <Julien.Bournelle@int-evry.fr>
User-Agent: Mutt/1.5.6+20040523i
References: <20040713014744.GG893@steelhead>
	<030501c4691e$e73f7ed0$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Giaretta Gerardo'" <Gerardo.Giaretta@TILAB.COM>,
        "'Julien Bournelle'" <Julien.Bournelle@int-evry.fr>,
        "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Tue, Jul 13, 2004 at 02:18:10PM -0700, Alper Yegin wrote:
> > Based on the discussion below.  I would suggest adding the following
> > sentences to section 4.4 of PANA speficication:
> > 
> > "
> > When NAP and ISP separate authetnications were performed in the first
> > occurence of PANA authentication phase, the same NAP and ISP separate
> > authentications MUST also be performed in subsequent EAP-based
> > re-authentication occurances.  Otherwise, NAP and ISP separate
> > authentications MUST NOT be performed in subsequent EAP-based
> > re-authentication occurances.
> > "
> 
> Can this be generalized to saying the NAP/ISP selection cannot change in
> a PANA session? I'm trying to understand what happens (breaks?) if the
> PaC changes its selection...

In the current specification, the PaC is not allowed to change its
selection because PSR-PSA exchange is not performed in EAP-based
re-authentication.  So I think your question is what happens if we
modify the specification to allow PSR-PSA exchange to change the
selection in EAP-based re-authentication.  I think that works, but
probably the PSR-PSA exchange should be integrity protected with a MAC
AVP if a PANA SA exists in order to avoid false re-authentication
trigger DoS attack.  But adding a MAC AVP in PSA might conflict with
the current PANA mobility optimization solution.

Yoshihiro Ohba


> 
> Alper
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Mon, Jul 12, 2004 at 05:42:11PM +0200, Giaretta Gerardo wrote:
> > > Hi Yoshi,
> > >
> > > > > > I am not sure how EAP-based re-authentication can work after
> the
> > > > > > PaC has successfully established a new PANA session with nPAA
> > > > > > based on the mobility optimization operation, especially with
> NAP
> > > > > > and ISP separated authentications.  Since PSR-PSA exchange is
> > > > > > omitted in the case of EAP-based re-authentication, there is
> no
> > > > > > means to negotiate on NAP and ISP separate authentications
> between
> > >
> > > > > > the PaC and nPAA.  Do you have any thoughts on this?
> > > > > >
> > > > >
> > > > > I'm not sure I understand your point: is this a general
> > > > PANA issue or
> > > > > is it related to the operations described in
> > > > > draft-bournelle-pana-ctp-00.txt?
> > > >
> > > > It might be related to both.  I think that if NAP and ISP
> > > > separate authentications were made in the initial
> > > > authentication, then the same NAP and ISP separate
> > > > authentications should also be made in EAP-based
> > > > re-authentication (this is a PANA issue, i.e., this should be
> > > > described in the PANA specification.)  If the same thing
> > > > needs to be done in EAP-based re-authentication after handoff
> > > > (though I am not sure the same thing needs to be done in this
> > > > case), information on whether NAP and ISP separate
> > > > authentications were made in the previous network may need to
> > > > be included in PANA-CTD (this is an issue of
> > > > draft-bournelle-pana-ctp-00.txt).
> > > >
> > >
> > > I agree with you. The result of the usage of CTP, as the result of
> any
> > > fast authentication mechanism, must be the same as the one obtained
> > > performing the whole authentication procedure. This implies that
> nPAA
> > > should know if PaC performed double authentication and which ISP it
> > > chose. Therefore this information must be transferred in CTD
> message.
> > >
> > > However, I think that EAP re-authentication is not related to
> mobility
> > > handling. The usage of CTP allows to transfer the PANA context to
> the
> > > nPAA. After the PBR/PBA exchange the PaC is authenticated and the
> nPAA
> > > knows the residual authorization lifetime. Therefore
> > > EAP-reauthentication is not performed immediately after the handoff
> and
> > > it is accomplished as specified in PANA specs.
> > >
> > > Note that we have not defined yet how to inform both NAP and ISP AAA
> > > system of the new PaC's location. I think this is also an important
> > > issue.
> > >
> > >
> > > --Gerardo
> > >
> > >
> > >
> > > > Yoshihiro Ohba
> > > >
> > >
> > >
> > >
> > >
> > > Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia
> > S.p.A.
> > >
> > > ====================================================================
> > > CONFIDENTIALITY NOTICE
> > > This message and its attachments are addressed solely to the persons
> > > above and may contain confidential information. If you have received
> > > the message in error, be informed that any use of the content hereof
> > > is prohibited. Please return it immediately to the sender and delete
> > > the message. Should you have any questions, please send an e_mail to
> > > MailAdmin@tilab.com. Thank you
> > > ====================================================================
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 19:48:29 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11260
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 19:48:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bkrs0-0007wU-2p; Wed, 14 Jul 2004 18:04:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkq5k-000196-If
	for pana@megatron.ietf.org; Wed, 14 Jul 2004 16:11:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13989
	for <pana@ietf.org>; Wed, 14 Jul 2004 16:10:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkq5j-0006Tu-Be
	for pana@ietf.org; Wed, 14 Jul 2004 16:10:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkq2B-0005LQ-00
	for pana@ietf.org; Wed, 14 Jul 2004 16:07:20 -0400
Received: from bay12-f14.bay12.hotmail.com ([64.4.35.14] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12) id 1Bkpyj-00049N-00
	for pana@ietf.org; Wed, 14 Jul 2004 16:03:45 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Wed, 14 Jul 2004 13:01:45 -0700
Received: from 63.124.79.129 by by12fd.bay12.hotmail.msn.com with HTTP;
	Wed, 14 Jul 2004 20:01:45 GMT
X-Originating-IP: [63.124.79.129]
X-Originating-Email: [aeyegin@hotmail.com]
X-Sender: aeyegin@hotmail.com
From: "Alper Yegin" <aeyegin@hotmail.com>
To: pana@ietf.org
Subject: RE: [Pana] Erik Nordmark's review comments #1
Date: Wed, 14 Jul 2004 13:01:45 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY12-F14ebmspH2q6D00004d7e@hotmail.com>
X-OriginalArrivalTime: 14 Jul 2004 20:01:45.0238 (UTC)
	FILETIME=[63916B60:01C469DD]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

I went over the list and opened new entries in the issue tracker. Please 
start a new thread for discussing individual issues.

On pana-ipsec:
101 Clarify the distinction between initial auth. and per-packet auth.

On pana-pana:
102 Reorganize the document flow
103 "PANA session" needs more clarification
104 Device Id clarification and further consideration
105 Inconsistent and unclear usage of "reauth" messages
106 sequence number on rexmited messages must be incremented

I couldn't create an entry for the framework I-d because the category does 
not exist (and Dan is not available to create it).

Alper
P.S: I'm experiencing huge delays (5-6 hours) in getting my messages posted 
on the list. Is anyone else is having the same problem?


>-----Original Message-----
>From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf Of
>Alper Yegin
>Sent: Tuesday, July 13, 2004 1:31 PM
>To: pana@ietf.org
>Cc: Erik.Nordmark@sun.com
>Subject: [Pana] Erik Nordmark's review comments #1
>
>
>(re-posting......)
>
>-----Original Message-----
>From: Alper Yegin - SAIT
>Sent: Monday, July 12, 2004 1:55 PM
>To: 'pana@ietf.org'
>Cc: 'Erik.Nordmark@sun.com'
>Subject: Erik Nordmark's review comments #1
>
>Hello,
>
>Please see Erik's review comments on the base spec, framework, and IPsec
>documents below. I've been holding on to these until we received the
>more detailed ones, but they won't be coming in for another couple of
>weeks. Until than, let's start processing these ones...
>
>
>Alper
>
>
>-----Original Message-----
>From: Erik Nordmark [mailto:Erik.Nordmark@sun.com]
>Sent: Wednesday, June 16, 2004 10:38 AM
>To: Alper Yegin - SAIT
>Cc: Erik Nordmark; Basavaraj.Patil@nokia.com
>Subject: RE: PANA review request
>
>
>So I did finish the read of the document set on Friday,
>but I haven't typed up the comments and some of them are
>extensive.
>
>The quick summary is:
>The framework seems to be in reasonable shape but the introduction
>is lacking in that it doesn't give an overview of the solved problem
>and it doesn't indicate which order the naive implementor or somebody
>that is trying to understand PANA should read the different documents.
>
>The ipsec doc is mostly ok. It should probably make the distinction
>between
>authentication (of a user) and per-packet authentication more clear.
>
>The pana document has significant editorial problems; by the time I'd
>read
>up to and including the security considerations section I finally
>understood
>what the features are of the protocol; reading back to front instead of
>front to back would have made it easier to understand.
>So editorially it needs to be better at incremental disclosure.
>For instance, talking about the features/functions up front without
>mentioning the packet formats and bit fields (RFC 2461 tries to do this
>and might be a reasonable approach). Then talk about the packets and
>what
>they are for (DHCPv6 has that type of info; basically a short paragraph
>per
>packet.)
>The document also seems to have technical omissions. The top 4 are:
>  - a session is not defined. Questions like who allocates the session
>id,
>    whether or not a session is bidirectional or unidirectional (with
>different
>    ids for both ends), and what happens to the session when
>reauthenticating
>    and when using the mobility optimization are unstated.
>  - the usage of device ID seems confused because there are some device
>IDs
>    that are carried in packets (L2/L3 addresses) and others that are not
>    (circuit ID) but most places in the document read as if circuit ids
>are
>    always carried in packets; there is even an EP device ID (which is
>used
>    to just carry the address of the EP). Furthermore, doesn't ipsec
>per-packet
>    auth rely on identifying the packet based on something else (the
>IPsec SA?).
>    Would it be more clear if device ID had two subclasses: local device
>ID
>    (e.g., cirtcuit ID) and address device ID (which would be carried in
>    packets)?
>  - the reauth packets seem to have completely different functions
>depending
>    on the direction they are sent. In one direction it is a reauth
>    and in the other direction it is a keepalive. (The document even uses
>    the term "keepalive" somewhere I think.) Wouldn't it be clearer
>    if these were different messages?
>  - the retransmission text says that a retransmitted packet has a new
>sequence
>    number. This makes no sense to me.
>
>I'll type up more complete comments later.
>
>   Erik
>
>
>_______________________________________________
>Pana mailing list
>Pana@ietf.org
>https://www1.ietf.org/mailman/listinfo/pana

_________________________________________________________________
Get tips for maintaining your PC, notebook accessories and reviews in 
Technology 101. http://special.msn.com/tech/technology101.armx


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 19:54:55 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11734
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 19:54:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BksGk-0007Ej-Fr; Wed, 14 Jul 2004 18:30:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkqTV-0000bh-V6
	for pana@megatron.ietf.org; Wed, 14 Jul 2004 16:35:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17125
	for <pana@ietf.org>; Wed, 14 Jul 2004 16:35:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkqTU-0004kq-Ny
	for pana@ietf.org; Wed, 14 Jul 2004 16:35:32 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkqLw-0002wH-00
	for pana@ietf.org; Wed, 14 Jul 2004 16:27:48 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12) id 1BkqEc-00016E-00
	for pana@ietf.org; Wed, 14 Jul 2004 16:20:10 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0U00601Z4QGR@mailout1.samsung.com> for pana@ietf.org; Thu,
	15 Jul 2004 05:19:38 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0U00DPMZ4QH7@mailout1.samsung.com> for pana@ietf.org;
	Thu, 15 Jul 2004 05:19:38 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0U008VFZ4NZO@mmp1.samsung.com> for
	pana@ietf.org; Thu, 15 Jul 2004 05:19:38 +0900 (KST)
Date: Wed, 14 Jul 2004 13:19:38 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] issue85 (initial text)
In-reply-to: <20040714193943.GO893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <01fd01c469df$e47a4ba0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Yoshi,

> > Also, I didn't understand where Device-ID comes into the picture.
When
> > do we update the device-ID?
> 
> - When an IP address is used as the device identifier, it can change
> if the PaC configures its temporary link-local address based on RFC
> 3041 and the lifetime of the temporary address is expired.

RFC3041 only deals with global addresses. The link-local addresses stay
the same (and it does not jeopardize the privacy).
 
> - When a MAC address is used as the device identifer, it can change if
> the PaC has multiple interfaces to the same link and switches from one
> interface to another.

This is more like session migration from one network interface to
another. I think we can discuss that, but we need another issue in the
tracker. Issue 85 is concerned about change of PaC IP address from PRPA
to POPA.

Alper


> 
> Yoshihiro Ohba
> 
> 
> >
> > I have some editorial comments as well. I'll wait for your response
to
> > these first.
> >
> > Alper
> >
> >
> >
> > > -----Original Message-----
> > > From: pana-admin@ietf.org [mailto:pana-admin@ietf.org] On Behalf
Of
> > > Yoshihiro Ohba
> > > Sent: Tuesday, May 18, 2004 6:51 PM
> > > To: pana@ietf.org
> > > Subject: [Pana] issue85 (initial text)
> > >
> > > This is the initial text for issue 85.
> > >
> > > Comments are appreciated.
> > >
> > > ----------
> > >
> > >
> > > [1] Add the following item in section 4.1.1
> > >
> > > "
> > >    o  IP-Address AVP: Conveys an IP-Address of a PaC.
> > > "
> > >
> > >
> > > [2] Add the following items in section 4.1.5:
> > >
> > > "
> > >       *  IP address of PaC (may be the same as the Device-Id of
PaC)
> > >
> > >       *  IP address of PAA (may be the same as the Device-Id of
PAA)
> > > "
> > >
> > >
> > > [3] Add the following item in section section 4.1.7:
> > >
> > > "
> > >       When an IP-Address AVP is included, the AVP is valid if (i)
the
> > >       Address type contained in the AVP matches the expected one
> > >       (i.e., either IPv4 or IPv6) that is used for the current
PANA
> > >       session and (ii) the AVP value matches the one extracted
from
> > >       the IP header.
> > > "
> > >
> > > [4] Update the following paragraph of section 4.4
> > >
> > > "
> > >    The second type of re-authentication is based on a single
protected
> > >    message exchange without entering the authentication phase.
> > >    PANA-Reauth-Request and PANA-Reauth-Answer messages are used
for
> > this
> > >    purpose.  If there is an established PANA SA, both the PaC and
the
> > >    PAA are allowed to send a PANA-Reauth-Request message to the
> > >    communicating peer whenever it needs to make sure the
availability
> > of
> > >    the PANA SA on the peer and expect the peer to return a PANA-
> > >    Reauth-Answer message.  Both PANA-Reauth-Request/
> > PANA-Reauth-Answer
> > >    messages MUST be protected with a MAC AVP.
> > > "
> > >
> > > to:
> > >
> > > "
> > >    The second type of re-authentication is based on a single
protected
> > >    message exchange without entering the authentication phase.
> > >    PANA-Reauth-Request and PANA-Reauth-Answer messages are used
for
> > >    this purpose.  If there is an established PANA SA, both the PaC
and
> > >    the PAA are allowed to send a PANA-Reauth-Request message to
the
> > >    communicating peer whenever it needs to make sure the
availability
> > >    of the PANA SA on the peer and expect the peer to return a
> > >    PANA-Reauth-Answer message.  In this case, both
> > >    PANA-Reauth-Request/PANA-Reauth-Answer messages MUST be
protected
> > >    with a MAC AVP.  If there is an established PANA session but
> > >    without an established PANA SA, both the PaC and the PAA are
> > >    allowed to send a PANA-Reauth-Request message to the
communicating
> > >    peer whenever it needs to make sure the availability of the
PANA
> > >    session on the peer and expect the peer to return a
> > >    PANA-Reauth-Answer message.  In this case, both
> > >    PANA-Reauth-Request/PANA-Reauth-Answer messages are not
protected
> > >    with a MAC AVP.
> > > "
> > >
> > > [5] Insert the following section after section 4.7:
> > >
> > > "
> > > 4.8. Updating PaC's Address
> > >
> > > A PaC's address can change in certain situations.  For example,
the
> > > PANA framework [I-D.ietf-pana-framework] describes a case in which
a
> > > PaC replaces a pre-PANA address (PRPA) a post-PANA address (POPA),
and
> > > the PaC and PAA create host routes to each other in order to
maintain
> > > on-link communication based on the POPA where the link-layer
address
> > > of the PaC is used as the device identifier.  Also, a PaC's device
> > > identifier may change regardless of whether a link-layer address
or an
> > > IP address is used as the device identifier.  As a result, it is
> > > possible when a link-layer address is used as the device
identifier
> > > that both the device identifier and an IP address change.  In any
> > > case, the PAA needs to be notified about the change of
address(es).
> > >
> > > After the PaC has changed its address(es), it MUST send a
> > > PANA-Address-Update-Request message to the PAA.  The message
carries
> > > the new address(es) in a Device-Id AVP and/or an IP-Address AVP.
At
> > > least one of these AVPs MUST appear in the request.  If an IP
address
> > > is used as the device identifier, a Device-Id AVP MUST be used and
an
> > > IP-Address AVP MUST NOT be used.  If an address contained in the
> > > request is invalid, the PAA sends a PANA-Error message with a
result
> > > code PANA_INVALID_DEVICE_ID or PANA_INVALID_IP_ADDRESS depending
on
> > > whether the device identifier or the IP address is invalid (in
case
> > > both a Device-Id AVP and an IP-Address AVP are included and both
are
> > > invalid, whichever result code is returned).  Otherwise, the PAA
> > > updates the address(es) of the PaC of the session attributes and
> > > returns a PANA-Address-Update-Answer message.  If there is an
> > > established PANA SA, both PANA-Address-Update-Request and
> > > PANA-Address-Update-Answer messages MUST be protected with a MAC
AVP.
> > > "
> > >
> > > [6] Change Figure 10 to:
> > >
> > > "
> > >                  Message                     Direction:
> > >                                              PaC---PAA
> > >                  ----------------------------------------
> > >                  PANA-PAA-Discover           -------->
> > >
> > >                  PANA-Start-Request          <--------
> > >                  PANA-Start-Answer           -------->
> > >
> > >                  PANA-Auth-Request           <--------
> > >                  PANA-Auth-Answer            -------->
> > >
> > >                  PANA-FirstAuth-End-Request  <--------
> > >                  PANA-FirstAuth-End-Answer   -------->
> > >
> > >                  PANA-Bind-Request           <--------
> > >                  PANA-Bind-Answer            -------->
> > >
> > >                  PANA-Reauth-Request         <------->
> > >                  PANA-Reauth-Answer          <------->
> > >
> > >                  PANA-Termination-Request    <------->
> > >                  PANA-Termination-Answer     <------->
> > >
> > >                  PANA-Address-Update-Request -------->
> > >                  PANA-Address-Update-Answer  <--------
> > >
> > >                  PANA-Error                  <------->
> > > "
> > >
> > > [7] Change sections 6.4.9 and 6.4.10 from:
> > >
> > > "
> > > 6.4.9 PANA-Reauth-Request (PRAR)
> > >
> > >    PANA-Reauth-Request (PRAR) is either sent by the PaC or the
PAA.
> > >
> > >          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
> > >                        < Session-Id >
> > >                        [ Device-Id ]
> > >                     *  [ AVP ]
> > >                    0*1 < MAC >
> > >
> > >
> > > 6.4.10 PANA-Reauth-Answer (PRAA)
> > >
> > >    PANA-Reauth-Answer (PRAA) is sent in response to a
> > >    PANA-Reauth-Request.
> > >
> > >          PANA-Reauth-Answer ::= < PANA-Header: 5 >
> > >                        < Session-Id >
> > >                        [ Device-Id ]
> > >                     *  [ AVP ]
> > >                    0*1 < MAC >
> > > "
> > >
> > > to:
> > >
> > > "
> > > 6.4.9 PANA-Reauth-Request (PRAR)
> > >
> > >    PANA-Reauth-Request (PRAR) is either sent by the PaC or the
PAA.
> > >
> > >          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
> > >                        < Session-Id >
> > >                     *  [ AVP ]
> > >                    0*1 < MAC >
> > >
> > >
> > > 6.4.10 PANA-Reauth-Answer (PRAA)
> > >
> > >    PANA-Reauth-Answer (PRAA) is sent in response to a
> > >    PANA-Reauth-Request.
> > >
> > >          PANA-Reauth-Answer ::= < PANA-Header: 5 >
> > >                        < Session-Id >
> > >                     *  [ AVP ]
> > >                    0*1 < MAC >
> > > "
> > >
> > > [8] Add the following sections:
> > >
> > > "
> > > 6.4.16 PANA-Address-Update-Request (PAUR)
> > >
> > >    PANA-Address-Update-Request (PAUR) is sent by the PaC to the
PAA.
> > >
> > >          PANA-Address-Update-Request ::= < PANA-Header: 9, REQ >
> > >                        < Session-Id >
> > >                    0*1 { Device-Id }
> > >                    0*1 { IP-Address }
> > >                    0*1 < MAC >
> > >
> > >
> > > 6.4.17 PANA-Address-Update-Answer (PAUA)
> > >
> > >    PANA-Address-Update-Answer (PAUA) is sent by the PAA to the PaC
in
> > >    response to a PANA-Address-Update-Request.
> > >
> > >          PANA-Address-Update-Answer ::= < PANA-Header: 9 >
> > >                        < Session-Id >
> > >                    0*1 < MAC >
> > > "
> > >
> > > "
> > > 6.5.19 IP-Address AVP
> > >
> > >    The IP-Address (AVP Code: 1041) contains an IP address of a
PaC.
> > >    The payload format of the IP-Address AVP is the same as that of
the
> > >    Device-Id AVP (see See section Section 6.5.2).  Address
families
> > >    for IPv4 or IPv6 MUST be used for this AVP.
> > > "
> > >
> > >
> > > [9] Add the following result code in section 6.5.7.2:
> > >
> > > "
> > >    PANA_INVALID_DEVICE_ID  5019
> > >
> > >       Error code from PAA to PaC or from PaC to PAA.  This error
is
> > >       returned in a PANA-Error message when the Device-Id AVP
> > >       contained in a received PANA-Bind-Request, PANA-Bind-Answer
or
> > >       PANA-Address-Update-Request message is invalid.
> > >
> > >    PANA_INVALID_IP_ADDRESS  5020
> > >
> > >       Error code from PAA to PaC.  This error is returned in a
> > >       PANA-Error message when the IP-Address AVP in the received
> > >       PANA-Address-Update-Request message is invalid.
> > >
> > > "
> > >
> > > [10]  Modify the AVP occurrence table as:
> > >
> > > "
> > >
+-----------------------------------------+
> > >                           |        Message
|
> > >                           |          Type
|
> > >
+-----+-----+-----+-----+-----+-----+-----+
> > >       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA |
PDI |
> > >
--------------------+-----+-----+-----+-----+-----+-----+-----+
> > >       Result-Code         |  0  |  0  |  0  |  0  |  1  |  1  |  0
|
> > >       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  |
0-1 |
> > >       Termination-Cause   |  0  |  0  |  0  |  0  |  0  |  0  |  0
|
> > >       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0
|
> > >       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0
|
> > >       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0
|
> > >       Device-Id           |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0
|
> > >       Cookie              | 0-1 | 0-1 |  0  |  0  |  0  |  0  |  0
|
> > >       Protection-Cap.     | 0-1 |  0  |  0  |  0  | 0-1 |  0  |  0
|
> > >       PPAC                | 0-1 |  0  |  0  |  0  |  1  | 0-1 |  0
|
> > >       Session-Lifetime    |  0  |  0  |  0  |  0  | 0-1 |  0  |  0
|
> > >       Failed-AVP          |  0  |  0  |  0  |  0  |  0  |  0  |  0
|
> > >       ISP-Information     |  0+ | 0-1 |  0  |  0  |  0  |  0  |  0
|
> > >       NAP-Information     | 0-1 |  0  |  0  |  0  |  0  |  0  |  0
|
> > >       EP-Device-Id        |  0  |  0  |  0  |  0  |  0+ |  0  |  0
|
> > >       Key-Id              |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0
|
> > >       IP-Address          |  0  |  0  |  0  |  0  |  0  |  0  |  0
|
> > >
--------------------+-----+-----+-----+-----+-----+-----+-----+
> > >
> > >                  Figure 11: AVP Occurrence Table (1/3)
> > >
> > >
> > +---------------------------------------------+
> > >                           |      Message
> > |
> > >                           |       Type
> > |
> > >
> > +------+------+-----+-----+-----+------+------+
> > >       Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER |
> > PFEA |
> > >
> > --------------------+------+------+-----+-----+-----+------+------+
> > >       Result-Code         |  0   |  0   |  0  |  0  |  1  |  1   |
0
> > |
> > >       Session-Id          |  1   |  1   |  1  |  1  |  1  |  1   |
1
> > |
> > >       Termination-Cause   |  0   |  0   |  1  |  0  |  0  |  0   |
0
> > |
> > >       EAP-Payload         |  0   |  0   |  0  |  0  |  0  |  1   |
0
> > |
> > >       MAC                 | 0-1  | 0-1  | 0-1 | 0-1 | 0-1 | 0-1  |
0-1
> > |
> > >       Nonce               |  0   |  0   |  0  |  0  |  0  |  0   |
0
> > |
> > >       Device-Id           |  0   |  0   |  0  |  0  |  0  |  0   |
0
> > |
> > >       Cookie              |  0   |  0   |  0  |  0  |  0  |  0   |
0
> > |
> > >       Protection-Cap.     |  0   |  0   |  0  |  0  |  0  |  0   |
0
> > |
> > >       PPAC                |  0   |  0   |  0  |  0  |  0  |  0   |
0
> > |
> > >       Session-Lifetime    |  0   |  0   |  0  |  0  |  0  |  0   |
0
> > |
> > >       Failed-AVP          |  0   |  0   |  0  |  0  |  1  |  0   |
0
> > |
> > >       ISP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |
0
> > |
> > >       NAP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |
0
> > |
> > >       EP-Device-Id        |  0   |  0   |  0  |  0  |  0  |  0   |
0
> > |
> > >       Key-Id              |  0   |  0   |  0  |  0  |  0  | 0-1  |
0-1
> > |
> > >       IP-Address          |  0   |  0   |  0  |  0  |  0  |  0   |
0
> > |
> > >
> > --------------------+------+------+-----+-----+-----+------+------+
> > >
> > >                  Figure 12: AVP Occurrence Table (2/3)
> > >
> > >
> > >                           +-------------+
> > >                           |   Message   |
> > >                           |     Type    |
> > >                           +------+------+
> > >       Attribute Name      | PAUR | PAUA |
> > >       --------------------+------+------+
> > >       Result-Code         |  0   |  0   |
> > >       Session-Id          |  1   |  1   |
> > >       Termination-Cause   |  0   |  0   |
> > >       EAP-Payload         |  0   |  0   |
> > >       MAC                 | 0-1  | 0-1  |
> > >       Nonce               |  0   |  0   |
> > >       Device-Id           | 0-1  |  0   |
> > >       Cookie              |  0   |  0   |
> > >       Protection-Cap.     |  0   |  0   |
> > >       PPAC                |  0   |  0   |
> > >       Session-Lifetime    |  0   |  0   |
> > >       Failed-AVP          |  0   |  0   |
> > >       ISP-Information     |  0   |  0   |
> > >       NAP-Information     |  0   |  0   |
> > >       EP-Device-Id        |  0   |  0   |
> > >       Key-Id              |  0   |  0   |
> > >       IP-Address          | 0-1  |  0   |
> > >       --------------------+------+------+
> > >
> > >                  Figure 13: AVP Occurrence Table (3/3)
> > > "
> > >
> > > [11]  Change the text in section 7 from:
> > >
> > > "
> > >          PANA-PAA-Discover (PDI)
> > >          PANA-Start-Request (PSR)*
> > >          PANA-Start-Answer (PSA)**
> > >          PANA-Bind-Request (PBR)
> > >          PANA-FirstAuth-End-Request (PFER)
> > >          PANA-Reauth-Request (PRAR)
> > >          PANA-Termination-Request (PTR)
> > >
> > >          *)  PSR that carries a Cookie AVP is not retransmitted.
> > >          **) PSA that does not carry a Cookie AVP is not
> > retransmitted.
> > > "
> > >
> > > to:
> > >
> > > "
> > >          PANA-PAA-Discover (PDI)
> > >          PANA-Start-Request (PSR)*
> > >          PANA-Start-Answer (PSA)**
> > >          PANA-Bind-Request (PBR)
> > >          PANA-FirstAuth-End-Request (PFER)
> > >          PANA-Reauth-Request (PRAR)
> > >          PANA-Termination-Request (PTR)
> > >          PANA-Address-Update-Request (PAUR)
> > >
> > >          *)  PSR that carries a Cookie AVP is not retransmitted.
> > >          **) PSA that does not carry a Cookie AVP is not
> > retransmitted.
> > > "
> > >
> > > [12]  Add the folliwng text in section 8:
> > >
> > > "
> > >    j) Updating PaC's address
> > >
> > >    An attacker can generate a PANA-Address-Update-Request with an
> > >    invalid Device-Id AVP or an IP-Address AVP.  There are several
> > >    threats:
> > >
> > >    - An attacker spoofs an address and registers itself with the
> > >    address.  If the registered address is not assigned to any PaC,
> > >    subsequent PANA messages sent from the PAA to the attacker will
not
> > >    reach any node and this is not a significant harm.  If the
> > >    registered address is assigned to some PaC, subsequent PANA
> > >    messages sent from the PAA to the attacker will reach the PaC,
but
> > >    will be silently discarded because the Session-Id is different.
> > >
> > >    - An attacker registers other PaC with any address.  As a
result,
> > >    subsequent PANA messages sent from the PAA to the PaC will not
> > >    reach the PaC.
> > >
> > >    To avoid all those attacks against an address update, an
additional
> > >    mechanism may be defined outside the PANA protocol for the PAA
to
> > >    validate ownership of the address.
> > > "
> > >
> > >
> > > Best regards,
> > >
> > > Yoshihiro Ohba
> > >
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> >
> >
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 20:02:30 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13102
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 20:02:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BktMt-0000VZ-HK; Wed, 14 Jul 2004 19:40:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkr0I-0002il-PL
	for pana@megatron.ietf.org; Wed, 14 Jul 2004 17:09:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21466
	for <pana@ietf.org>; Wed, 14 Jul 2004 17:09:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bkr0H-00047k-3u
	for pana@ietf.org; Wed, 14 Jul 2004 17:09:25 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bkqqe-0001yq-00
	for pana@ietf.org; Wed, 14 Jul 2004 16:59:30 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1Bkqhy-0007ev-00
	for pana@ietf.org; Wed, 14 Jul 2004 16:50:30 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0V000010J7NJ@mailout2.samsung.com> for pana@ietf.org; Thu,
	15 Jul 2004 05:49:55 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0V00A830J77L@mailout2.samsung.com> for pana@ietf.org;
	Thu, 15 Jul 2004 05:49:55 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0V005VC0J451@mmp2.samsung.com> for
	pana@ietf.org; Thu, 15 Jul 2004 05:49:55 +0900 (KST)
Date: Wed, 14 Jul 2004 13:49:55 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] EAP-based reauth clarification [Re: Mobility Handling in
	PANA]
In-reply-to: <20040714195312.GS893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <028101c469e4$1fc3c480$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: "'Giaretta Gerardo'" <Gerardo.Giaretta@TILAB.COM>,
        "'Julien Bournelle'" <Julien.Bournelle@int-evry.fr>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

OK, I'm fine with locking a PANA session to fixed NAP/ISP. If the PaC
wants to hop around, it better terminate the current session and start a
new one.

Maybe we could briefly capture this by saying:

Any subsequent EAP-based authentication MUST be performed with the
same ISP and NAP that was selected during the initial authentication. 

Alper




> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Wednesday, July 14, 2004 12:53 PM
> To: Alper Yegin
> Cc: 'Yoshihiro Ohba'; pana@ietf.org; 'Giaretta Gerardo'; 'Julien
> Bournelle'
> Subject: Re: [Pana] EAP-based reauth clarification [Re: Mobility
Handling
> in PANA]
> 
> On Tue, Jul 13, 2004 at 02:18:10PM -0700, Alper Yegin wrote:
> > > Based on the discussion below.  I would suggest adding the
following
> > > sentences to section 4.4 of PANA speficication:
> > >
> > > "
> > > When NAP and ISP separate authetnications were performed in the
first
> > > occurence of PANA authentication phase, the same NAP and ISP
separate
> > > authentications MUST also be performed in subsequent EAP-based
> > > re-authentication occurances.  Otherwise, NAP and ISP separate
> > > authentications MUST NOT be performed in subsequent EAP-based
> > > re-authentication occurances.
> > > "
> >
> > Can this be generalized to saying the NAP/ISP selection cannot
change in
> > a PANA session? I'm trying to understand what happens (breaks?) if
the
> > PaC changes its selection...
> 
> In the current specification, the PaC is not allowed to change its
> selection because PSR-PSA exchange is not performed in EAP-based
> re-authentication.  So I think your question is what happens if we
> modify the specification to allow PSR-PSA exchange to change the
> selection in EAP-based re-authentication.  I think that works, but
> probably the PSR-PSA exchange should be integrity protected with a MAC
> AVP if a PANA SA exists in order to avoid false re-authentication
> trigger DoS attack.  But adding a MAC AVP in PSA might conflict with
> the current PANA mobility optimization solution.
> 
> Yoshihiro Ohba
> 
> 
> >
> > Alper
> >
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > > On Mon, Jul 12, 2004 at 05:42:11PM +0200, Giaretta Gerardo wrote:
> > > > Hi Yoshi,
> > > >
> > > > > > > I am not sure how EAP-based re-authentication can work
after
> > the
> > > > > > > PaC has successfully established a new PANA session with
nPAA
> > > > > > > based on the mobility optimization operation, especially
with
> > NAP
> > > > > > > and ISP separated authentications.  Since PSR-PSA exchange
is
> > > > > > > omitted in the case of EAP-based re-authentication, there
is
> > no
> > > > > > > means to negotiate on NAP and ISP separate authentications
> > between
> > > >
> > > > > > > the PaC and nPAA.  Do you have any thoughts on this?
> > > > > > >
> > > > > >
> > > > > > I'm not sure I understand your point: is this a general
> > > > > PANA issue or
> > > > > > is it related to the operations described in
> > > > > > draft-bournelle-pana-ctp-00.txt?
> > > > >
> > > > > It might be related to both.  I think that if NAP and ISP
> > > > > separate authentications were made in the initial
> > > > > authentication, then the same NAP and ISP separate
> > > > > authentications should also be made in EAP-based
> > > > > re-authentication (this is a PANA issue, i.e., this should be
> > > > > described in the PANA specification.)  If the same thing
> > > > > needs to be done in EAP-based re-authentication after handoff
> > > > > (though I am not sure the same thing needs to be done in this
> > > > > case), information on whether NAP and ISP separate
> > > > > authentications were made in the previous network may need to
> > > > > be included in PANA-CTD (this is an issue of
> > > > > draft-bournelle-pana-ctp-00.txt).
> > > > >
> > > >
> > > > I agree with you. The result of the usage of CTP, as the result
of
> > any
> > > > fast authentication mechanism, must be the same as the one
obtained
> > > > performing the whole authentication procedure. This implies that
> > nPAA
> > > > should know if PaC performed double authentication and which ISP
it
> > > > chose. Therefore this information must be transferred in CTD
> > message.
> > > >
> > > > However, I think that EAP re-authentication is not related to
> > mobility
> > > > handling. The usage of CTP allows to transfer the PANA context
to
> > the
> > > > nPAA. After the PBR/PBA exchange the PaC is authenticated and
the
> > nPAA
> > > > knows the residual authorization lifetime. Therefore
> > > > EAP-reauthentication is not performed immediately after the
handoff
> > and
> > > > it is accomplished as specified in PANA specs.
> > > >
> > > > Note that we have not defined yet how to inform both NAP and ISP
AAA
> > > > system of the new PaC's location. I think this is also an
important
> > > > issue.
> > > >
> > > >
> > > > --Gerardo
> > > >
> > > >
> > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > Gruppo Telecom Italia - Direzione e coordinamento di Telecom
Italia
> > > S.p.A.
> > > >
> > > >
====================================================================
> > > > CONFIDENTIALITY NOTICE
> > > > This message and its attachments are addressed solely to the
persons
> > > > above and may contain confidential information. If you have
received
> > > > the message in error, be informed that any use of the content
hereof
> > > > is prohibited. Please return it immediately to the sender and
delete
> > > > the message. Should you have any questions, please send an
e_mail to
> > > > MailAdmin@tilab.com. Thank you
> > > >
====================================================================
> > >
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> >


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 20:05:36 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13635
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 20:05:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BktOn-0001q8-9z; Wed, 14 Jul 2004 19:42:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BkrVX-0005Gp-Ko
	for pana@megatron.ietf.org; Wed, 14 Jul 2004 17:41:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25001
	for <pana@ietf.org>; Wed, 14 Jul 2004 17:41:40 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BkrVV-0003Ad-SL
	for pana@ietf.org; Wed, 14 Jul 2004 17:41:41 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BkrHM-0000I9-00
	for pana@ietf.org; Wed, 14 Jul 2004 17:27:06 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1Bkr8x-00063J-00
	for pana@ietf.org; Wed, 14 Jul 2004 17:18:23 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0V001011TTZA@mailout2.samsung.com> for pana@ietf.org; Thu,
	15 Jul 2004 06:17:53 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0V00CM51TSFC@mailout2.samsung.com> for pana@ietf.org;
	Thu, 15 Jul 2004 06:17:52 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0V00C0E1TQNW@mmp1.samsung.com> for
	pana@ietf.org; Thu, 15 Jul 2004 06:17:52 +0900 (KST)
Date: Wed, 14 Jul 2004 14:17:53 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] New: [issue98] Lost answer problem
In-reply-to: <20040714194319.GP893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <02c301c469e8$077761d0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: Dan.Forsberg@nokia.com, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Yoshi,

> > The default action would be to respond to the request (unless there
is a
> > statement in the draft that makes an exception).
> 
> There would be the following exceptions:
> 
> o In discovery and initial handshake phase,
> 
>   - PTR and PRAR is rejected.
>   - PBR is rejected.
>   - PAUR is rejected.
> 
> o In authentication phase,
> 
>   - PTR and PRAR is rejected.
>   - PAUR is rejected.
>   - PSR is rejected after PaC receives the first vaild PAR.
> 
> o After successful PANA authentication,
> 
>  - PSR as well as a non-duplicate PBR is rejected.
>  - PDI without a Session-Id AVP (i.e., initial authentication) is
rejected.
> 
> o In termination phase,
> 
>  - All requests but PTR is rejected.
> 
> I think both the default action as well as these exceptions should be
> described in the specification.

These are related to the "states". That's why I think the discussion
belongs to the state machine I-D. It can discuss definition of states,
how the session moves from one state to another, and how messages are
processed in each state (ignored, rejected, causes state change, etc.)
And all that pana specification can say is what it already says:

4.1.7 Message Validity Check

   When a PANA message is received, the message is considered to be
   invalid at least when one of the following conditions are not met:

   o  The message type is one of the expected types in the current
      state.

I think this is a more scalable and modular approach. 

Alper



> 
> Yoshihiro Ohba
> 
> 
> >
> > Alper
> >
> >
> >
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 14 20:11:55 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14268
	for <pana-archive@lists.ietf.org>; Wed, 14 Jul 2004 20:11:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bktbl-0002so-Gj; Wed, 14 Jul 2004 19:56:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BksVm-0005I9-Hk
	for pana@megatron.ietf.org; Wed, 14 Jul 2004 18:46:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03882
	for <pana@ietf.org>; Wed, 14 Jul 2004 18:45:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BksVk-0007RX-Rn
	for pana@ietf.org; Wed, 14 Jul 2004 18:46:00 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BksAk-0003N8-00
	for pana@ietf.org; Wed, 14 Jul 2004 18:24:19 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12) id 1Bkrue-0007lH-00
	for pana@ietf.org; Wed, 14 Jul 2004 18:07:41 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0V00B0143XHD@mailout1.samsung.com> for pana@ietf.org; Thu,
	15 Jul 2004 07:07:09 +0900 (KST)
Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0V00JRE43WIP@mailout1.samsung.com> for pana@ietf.org;
	Thu, 15 Jul 2004 07:07:08 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0V005ET43UH1@mmp2.samsung.com> for
	pana@ietf.org; Thu, 15 Jul 2004 07:07:08 +0900 (KST)
Date: Wed, 14 Jul 2004 15:07:09 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <036001c469ee$e945dfa0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Subject: [Pana] New Intro section for framework I-D
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

   
Hello,

Based on Erik's feedback, I have a new proposed text for the
introduction section of the PANA Framework document. Comments welcome.



   PANA is a link-layer agnostic network access authentication protocol
   that runs between a node that wants to gain access to the network and
   a server on the network side. PANA defines a new EAP [RFC3748] lower 
   layer that uses IP between the protocol end points. 

   The motivation to define such a protocol and the requirements are 
   described in [I-D.ietf-pana-requirements]. Protocol details are 
   documented in [I-D.ietf-pana-pana]. [I-D.ietf-pana-ipsec] describes
use 
   of IPsec for access control following PANA-based authentication.
IPsec 
   can be used for per-packet access control, but nevertheless it is not
the
   only way to achieve this functionality. Alternatives include reliance
on 
   physical security and link-layer ciphering. Separation of PANA server
   from the entity enforcing the access control is envisaged as an
optional
   deployment choice. SNMP [I-D.ietf-pana-snmp] is chosen as the
protocol to 
   carry associated information between the separate nodes.

   PANA design provides support for various types of deployments. Access
   networks can differ based on the availability of lower-layer
   security, placement of PANA entities, choice of client IP
   configuration and authentication methods, etc.

   PANA can be used in any access network regardless of the underlying
   security.  For example, the network might be physically secured, or
   secured by means of cryptographic mechanisms after the successful
   client-network authentication.

   The PANA client, PANA authentication agent, authentication server,
   and enforcement point are the relevant functional entities in this
   design.  PANA authentication agent and enforcement point(s) can be
   placed on various elements in the access network (e.g., access point,
   access router, dedicated host).

   IP address configuration mechanisms vary as well. Static
   configuration, DHCP, stateless address autoconfiguration are possible
   mechanisms to choose from. If the client configures an IPsec tunnel
   for enabling per-packet security, configuring IP addresses inside the
   tunnel becomes relevant, for which there are additional choices such
   as IKE.

   This I-D defines a general framework for describing how these various
   deployment choices are handled by PANA and the access network
   architectures.  Additionally, two possible deployments are described
   in detail: PANA over DSL networks and WLAN networks.	




_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 05:19:03 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05688
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 05:19:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl2Ex-0003ui-Rk; Thu, 15 Jul 2004 05:09:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl28n-0002JL-BN
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 05:03:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05050
	for <pana@ietf.org>; Thu, 15 Jul 2004 05:02:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl28k-0004PO-Ph
	for pana@ietf.org; Thu, 15 Jul 2004 05:02:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl27j-00044g-00
	for pana@ietf.org; Thu, 15 Jul 2004 05:01:52 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx with esmtp (Exim 4.12) id 1Bl26b-0003Px-00
	for pana@ietf.org; Thu, 15 Jul 2004 05:00:41 -0400
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by smtp2.int-evry.fr (Postfix) with ESMTP id CF31D2FD42;
	Thu, 15 Jul 2004 11:00:06 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1Bl24f-000ELJ-U8;
	Thu, 15 Jul 2004 10:58:41 +0200
Date: Thu, 15 Jul 2004 10:58:41 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Subject: Re: [Pana] Mobility Handling in PANA
Message-ID: <20040715085841.GQ45745@ipv6-5.int-evry.fr>
References: <625BE97BF4795E43970345790166B9BCD4DF41@EXC2K01B.cselt.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <625BE97BF4795E43970345790166B9BCD4DF41@EXC2K01B.cselt.it>
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (score=-4.9, requis 4.5, autolearn=not spam,
	BAYES_00 -4.90)
X-MailScanner-From: jb@ipv6-5.int-evry.fr
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Alper Yegin <alper.yegin@samsung.com>, yohba@tari.toshiba.com,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi,


see comments inline,

On Wed, Jul 14, 2004 at 09:50:50AM +0200, Giaretta Gerardo wrote:
> > 
> > > Thus we propose this:
> > > 
> > > 
> > >      PaC           nPAA              pPAA
> > >      ----------------------------------------
> > >            PDI
> > >       -------------->
> > >            PSR
> > >      <---------------
> > >           PSA [old Session-ID, Nonce, CTAR]
> > >       --------------->
> > > 
> > >                            CT-Request
> > >                         -------------->
> > >                                CTD
> > >                         <--------------
> > > 
> > >       PBR[new Session-ID, Key-Id, Nonce, PPAC, MAC]
> > >      <-------------
> > >       PBA[new Session-ID, Key-Id, PPAC, MAC]
> > >       ------------->
> > 
> > This is the flow I had in my mind, but I don't see the need 
> > to have an explicit CTAR AVP in the PSA.
> > 
> > Looking at the draft, CTAR carries:
> > - PaC's address. Why do we need this? The Pac is identified 
> > with its session id.
> > - PAA's address. I don't think we need this either. Session 
> > id reveals the ID of the pPAA. It's just a matter of mapping 
> > that to an IP address (use DNS).
> > - Authorization token. MAC AVP already does the job.
> >
> 
> CTAR (and thus a CTAR AVP in our draft) is always required by CTP as
> specified in draft-ietf-seamoby-ctp-10.txt. It is not possible to use
> CTP without sending a CTAR message both in predictive and reactive mode.
> This is because in CTP the transfer is authorized trough the
> authorization token that is shared between pAR and MN. However, I
> completely agree with you that the information carried by CTAR can be
> obtained by other means as you stated above. 
> 
> I think here the issue is whether we want to apply the Seamoby CTP or to
> define a context transfer mechanism only for PANA (which exploits PANA
> features).

I would like to add that we need CTAR message if we want to support
predictive handover. 


-- 
julien.bournelle@int-evry.fr

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 05:22:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05850
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 05:22:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl2Oc-0006ZO-8o; Thu, 15 Jul 2004 05:19:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl2FY-00048W-Ed
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 05:09:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05297
	for <pana@ietf.org>; Thu, 15 Jul 2004 05:09:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl2FV-0006dr-Qk
	for pana@ietf.org; Thu, 15 Jul 2004 05:09:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl2ET-0006JI-00
	for pana@ietf.org; Thu, 15 Jul 2004 05:08:51 -0400
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx with esmtp (Exim 4.12) id 1Bl2DW-0005gs-00
	for pana@ietf.org; Thu, 15 Jul 2004 05:07:50 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I0V0081TYCSGB@dns2.cselt.it> for pana@ietf.org; Thu,
	15 Jul 2004 11:00:28 +0200 (MEST)
Received: from EXC2K01A.cselt.it ([163.162.4.34]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Thu, 15 Jul 2004 11:05:18 +0200
Received: from EXC2K01B.cselt.it ([163.162.4.97]) by EXC2K01A.cselt.it with
	Microsoft SMTPSVC(5.0.2195.5329); Thu, 15 Jul 2004 11:07:20 +0200
Date: Thu, 15 Jul 2004 11:07:19 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Message-id: <625BE97BF4795E43970345790166B9BC01E2463A@EXC2K01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: EAP-based reauth clarification [Re: Mobility Handling in PANA]
thread-index: AcRp3GJLKngC85hhSriLrTjyGlFVwwAanTxw
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 15 Jul 2004 09:07:20.0483 (UTC)
	FILETIME=[225D0730:01C46A4B]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Cc: Alper Yegin <alper.yegin@samsung.com>,
        Julien Bournelle <Julien.Bournelle@int-evry.fr>, pana@ietf.org
Subject: [Pana] RE: EAP-based reauth clarification [Re: Mobility Handling in
	PANA]
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

> >=20
> > Just two comments:
> >=20
> > [1] A similar text is provided in section 4.9:
> >=20
> > "
> >    When separate EAP authentications are performed for ISP=20
> and NAP in a
> >    single PANA session, it is possible that different authorization
> >    lifetime values are associated with the two=20
> authentications.  In this
> >    case, the smaller authorization lifetime value MUST be used for
> >    calculating the PANA Session-Lifetime value.  As a result, when
> >    EAP-based re-authentication occurs, both NAP and ISP=20
> authentications
> >    will be performed in the same re-authentication procedure. "
> >=20
> > Is this really needed? I mean, it could be unefficient to=20
> perform both=20
> > the authentications if only one is required. This is a consequence=20
> > that the PANA Session Lifetime is equal to the smaller=20
> authorization=20
> > lifetime value. I'm thinking if it is possible to manage=20
> the lifetimes=20
> > in order to perform only the authentication that is=20
> required. Do you=20
> > have any thoughts on this?
>=20
> I had a couple of thoughts on that before the current=20
> solution, but there are many issues as described below.
>=20
> >=20
> > A possible solution could be (however I'm not sure if this works):
> >=20
> > PANA session lifetime =3D min (Residual NAP auth. Lifetime,=20
> Residual ISP=20
> > auth. Lifetime)
> >=20
> > In this way, only the required re-authentication is=20
> performed and the=20
> > PANA session lifetime is re-calculated at the end of each=20
> > re-authentication.
>

I try to reply to your issues, even if I'm still not sure if this
optimization is really needed.
=20
> - Should the S-bit set if the EAP re-authentication with a=20
> single EAP run is performed?
>

I think that S-bit should not be set if a single EAP run is performed
during the re-authentication.
The issue is how the PAA informs the PaC whether an ISP or a NAP
re-authentication must be performed. Can we use the N-flag for that?

=20
> - Which exchange should be used for carrying authenticaiton=20
> result for the EAP re-authentication with a single EAP run,=20
> PBR-PBA or PFER-PFEA?

I think PBR-PBA should be used.
Note that, for example after an ISP re-authentication, the PANA_MAC_Key
should be re-derived using the new ISP-AAA-key and the old NAP-AAA-Key.

>=20
> - What happens if the EAP re-authentication with a single EAP=20
> run (for NAP authentication for example) fails?  Should the=20
> PANA session be deleted, or remain because authorization for=20
> ISP part still exists? In the latter case, are the subsequent=20
> EAP-reauthentications always performed with a single EAP run=20
> for ISP authentication?  And also in the latter case is the=20
> PANA_MAC_KEY needs to be updated after the single EAP run=20
> failure in the EAP re-authentication?  If so, how?
>=20

I think this is the main issue. Maybe if one re-authentication fails,
the PANA session should be deleted. This case should be treated as the
bootstrap case when double authentication is performed and ISP or NAP
authentication fails.

> > However there might be cases in which it is
> > convenient to perform both the authentications together (e.g. the=20
> > difference between the residual lifetimes is very small).
>=20
> >=20
> > [2] What about a scenario in which a new ISP is available? Consider=20
> > that at the first occurence of PANA there were only two=20
> ISPs available=20
> > (ISP1 and ISP2). If a new ISP (ISP3) becomes available=20
> (e.g. after a=20
> > movement of the PaC), I think this must be communicated to the PaC.=20
> > How can we handle this?
>=20
> After a movement of a PaC, the new ISP information can be=20
> contained in PSR sent from the new PAA.  However, if the PaC=20
> returns a PSA with ISP3 information in a ISP-Information AVP,=20
> the PAA should not perform mobility optimization.
>=20

Agree.

> In the case where a new ISP becomes available while the PaC=20
> is connecting to the same PAA, I don't think the PaC has to=20
> know the new ISP immediately.
>=20

Agree.=20
Note that this implies that if the PaC performs only re-authentication
procedures, it will never know if a new ISP is available. Do you think
this is an issue?

-Gerardo
=20

> Yoshihiro Ohba
>=20
>=20
>=20
>=20
> >=20
> >=20
> > --Gerardo
> >=20
> > =20
> > > Yoshihiro Ohba
> > >=20
> > >=20
> > > On Mon, Jul 12, 2004 at 05:42:11PM +0200, Giaretta Gerardo wrote:
> > > > Hi Yoshi,
> > > >=20
> > > > > > > I am not sure how EAP-based re-authentication can
> > > work after the
> > > > > > > PaC has successfully established a new PANA session with=20
> > > > > > > nPAA
> > > > > > > based on the mobility optimization operation,=20
> > > especially with NAP
> > > > > > > and ISP separated authentications.  Since PSR-PSA=20
> exchange=20
> > > > > > > is
> > > > > > > omitted in the case of EAP-based re-authentication,=20
> > > there is no
> > > > > > > means to negotiate on NAP and ISP separate
> > > authentications between
> > > >=20
> > > > > > > the PaC and nPAA.  Do you have any thoughts on this?
> > > > > > >=20
> > > > > >=20
> > > > > > I'm not sure I understand your point: is this a general
> > > > > PANA issue or
> > > > > > is it related to the operations described in
> > > > > > draft-bournelle-pana-ctp-00.txt?
> > > > >=20
> > > > > It might be related to both.  I think that if NAP and ISP
> > > separate
> > > > > authentications were made in the initial authentication, then=20
> > > > > the
> > > > > same NAP and ISP separate authentications should also=20
> be made in=20
> > > > > EAP-based re-authentication (this is a PANA issue, i.e.,=20
> > > this should
> > > > > be described in the PANA specification.)  If the same thing=20
> > > > > needs to be done in EAP-based re-authentication after handoff=20
> > > > > (though I am not sure the same thing needs to be done in this=20
> > > > > case), information on whether NAP and ISP separate=20
> > > > > authentications were made in the previous network may=20
> need to be=20
> > > > > included in PANA-CTD (this is an issue of=20
> > > > > draft-bournelle-pana-ctp-00.txt).
> > > > >
> > > >=20
> > > > I agree with you. The result of the usage of CTP, as the
> > > result of any
> > > > fast authentication mechanism, must be the same as the one=20
> > > > obtained
> > > > performing the whole authentication procedure. This implies=20
> > > that nPAA
> > > > should know if PaC performed double authentication and=20
> which ISP=20
> > > > it
> > > > chose. Therefore this information must be transferred in=20
> > > CTD message.
> > > >=20
> > > > However, I think that EAP re-authentication is not related
> > > to mobility
> > > > handling. The usage of CTP allows to transfer the PANA
> > > context to the
> > > > nPAA. After the PBR/PBA exchange the PaC is authenticated
> > > and the nPAA
> > > > knows the residual authorization lifetime. Therefore
> > > > EAP-reauthentication is not performed immediately after=20
> the handoff=20
> > > > and it is accomplished as specified in PANA specs.
> > > >=20
> > > > Note that we have not defined yet how to inform both NAP
> > > and ISP AAA
> > > > system of the new PaC's location. I think this is also an=20
> > > > important
> > > > issue.
> > > >=20
> > > >=20
> > > > --Gerardo
> > > >=20
> > > >=20
> > > > =20
> > > > > Yoshihiro Ohba
> > > > >=20
> > > >=20
> > > >=20
> > > >=20
> > > >=20
> > > > Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> > > > Italia
> > > > S.p.A.
> > > >=20
> > > >=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > > =3D=3D
> > > > CONFIDENTIALITY NOTICE
> > > > This message and its attachments are addressed solely to=20
> > > the persons
> > > > above and may contain confidential information. If you have
> > > received
> > > > the message in error, be informed that any use of the
> > > content hereof
> > > > is prohibited. Please return it immediately to the sender
> > > and delete
> > > > the message. Should you have any questions, please send an
> > > e_mail to
> > > > MailAdmin@tilab.com. Thank you
> > > >=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > >=20
> >=20
> >=20
> > Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia=20
> > S.p.A.
> >=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > CONFIDENTIALITY NOTICE
> > This message and its attachments are addressed solely to=20
> the persons=20
> > above and may contain confidential information. If you have=20
> received=20
> > the message in error, be informed that any use of the=20
> content hereof=20
> > is prohibited. Please return it immediately to the sender=20
> and delete=20
> > the message. Should you have any questions, please send an=20
> e_mail to=20
> > MailAdmin@tilab.com. Thank you=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 07:03:14 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10851
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 07:03:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl3x5-0001Hb-NW; Thu, 15 Jul 2004 06:58:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl3tK-0000Eq-T8
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 06:55:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10481
	for <pana@ietf.org>; Thu, 15 Jul 2004 06:55:03 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl3tI-0001uB-CK
	for pana@ietf.org; Thu, 15 Jul 2004 06:55:04 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl3sI-0001Zb-00
	for pana@ietf.org; Thu, 15 Jul 2004 06:54:03 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12) id 1Bl3rL-0000vF-00
	for pana@ietf.org; Thu, 15 Jul 2004 06:53:03 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id EFC2917AD4; Thu, 15 Jul 2004 12:52:33 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id D204217A2B; Thu, 15 Jul 2004 12:52:33 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id 8952F14431; Thu, 15 Jul 2004 12:50:35 +0200 (MET DST)
Message-ID: <40F66223.3060706@dif.um.es>
Date: Thu, 15 Jul 2004 12:53:23 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@samsung.com>
Subject: Re: [Pana] New: [issue98] Lost answer problem
References: <02c301c469e8$077761d0$6401a8c0@sisa.samsung.com>
In-Reply-To: <02c301c469e8$077761d0$6401a8c0@sisa.samsung.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, rafa <rafa@dif.um.es>,
        Dan.Forsberg@nokia.com, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi Alper...

Sounds good for me.

NOTE: On the other hand,  will be [tseq of the last acknowledged 
message, tseq of the last transmitted message] included in draft instead 
of [tseq of the last acknowledged message + 1, tseq of the last 
transmitted message] finally or it is another issue?

Regards.

Alper Yegin wrote:

>Yoshi,
>
>  
>
>>>The default action would be to respond to the request (unless there
>>>      
>>>
>is a
>  
>
>>>statement in the draft that makes an exception).
>>>      
>>>
>>There would be the following exceptions:
>>
>>o In discovery and initial handshake phase,
>>
>>  - PTR and PRAR is rejected.
>>  - PBR is rejected.
>>  - PAUR is rejected.
>>
>>o In authentication phase,
>>
>>  - PTR and PRAR is rejected.
>>  - PAUR is rejected.
>>  - PSR is rejected after PaC receives the first vaild PAR.
>>
>>o After successful PANA authentication,
>>
>> - PSR as well as a non-duplicate PBR is rejected.
>> - PDI without a Session-Id AVP (i.e., initial authentication) is
>>    
>>
>rejected.
>  
>
>>o In termination phase,
>>
>> - All requests but PTR is rejected.
>>
>>I think both the default action as well as these exceptions should be
>>described in the specification.
>>    
>>
>
>These are related to the "states". That's why I think the discussion
>belongs to the state machine I-D. It can discuss definition of states,
>how the session moves from one state to another, and how messages are
>processed in each state (ignored, rejected, causes state change, etc.)
>And all that pana specification can say is what it already says:
>
>4.1.7 Message Validity Check
>
>   When a PANA message is received, the message is considered to be
>   invalid at least when one of the following conditions are not met:
>
>   o  The message type is one of the expected types in the current
>      state.
>
>I think this is a more scalable and modular approach. 
>
>Alper
>
>
>
>  
>
>>Yoshihiro Ohba
>>
>>
>>    
>>
>>>Alper
>>>
>>>
>>>
>>>_______________________________________________
>>>Pana mailing list
>>>Pana@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/pana
>>>      
>>>
>
>
>_______________________________________________
>Pana mailing list
>Pana@ietf.org
>https://www1.ietf.org/mailman/listinfo/pana
>
>
>  
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 09:20:36 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18328
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 09:20:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl66o-0007YO-Ck; Thu, 15 Jul 2004 09:17:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl605-0005cU-8e
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 09:10:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17524
	for <pana@ietf.org>; Thu, 15 Jul 2004 09:10:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl604-0005yG-AC
	for pana@ietf.org; Thu, 15 Jul 2004 09:10:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl5z2-0005fP-00
	for pana@ietf.org; Thu, 15 Jul 2004 09:09:08 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bl5ye-0005NK-00
	for pana@ietf.org; Thu, 15 Jul 2004 09:08:44 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6FD8epD019545;
	Thu, 15 Jul 2004 22:08:40 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6FD8e2p023156;
	Thu, 15 Jul 2004 22:08:40 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	YAA23154 ; Thu, 15 Jul 2004 22:08:40 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA23001; Thu, 15 Jul 2004 22:08:39 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA03087;
	Thu, 15 Jul 2004 22:08:38 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6FD8cpl019298;
	Thu, 15 Jul 2004 22:08:38 +0900 (JST)
Received: from steelhead (iVPN01-145.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0W00MK29UC5Z@tsbpo1.po.toshiba.co.jp>; Thu,
	15 Jul 2004 22:08:37 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bl5yO-0007Kj-00; Thu, 15 Jul 2004 06:08:28 -0700
Date: Thu, 15 Jul 2004 09:08:28 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New: [issue98] Lost answer problem
In-reply-to: <02c301c469e8$077761d0$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040715130828.GX893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040714194319.GP893@steelhead>
	<02c301c469e8$077761d0$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Alper,

On Wed, Jul 14, 2004 at 02:17:53PM -0700, Alper Yegin wrote:
> 
> These are related to the "states". That's why I think the discussion
> belongs to the state machine I-D. It can discuss definition of states,
> how the session moves from one state to another, and how messages are
> processed in each state (ignored, rejected, causes state change, etc.)
> And all that pana specification can say is what it already says:
> 
> 4.1.7 Message Validity Check
> 
>    When a PANA message is received, the message is considered to be
>    invalid at least when one of the following conditions are not met:
> 
>    o  The message type is one of the expected types in the current
>       state.
> 
> I think this is a more scalable and modular approach. 

I want to make sure the relationship between the PANA specification
I-D and the PANA state machine I-D.

The suggested approach seems to indicate that the PANA state machine
I-D is a part of the "complete" set of specification.  (Otherwise,
pana-pana draft needs to specify what messages types are expected in
the current state, doesn't it?)

Note that the suggested approach is different from the approach taken
by RFC 3748 (EAP) and EAP state machine I-D.  RFC 3748 specifies
everything including which message should be accepted or rejected in
certain conditions and EAP state machine I-D is just another
representation of RFC 3748.

Yoshihiro Ohba

> 
> Alper
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > >
> > > Alper
> > >
> > >
> > >
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 09:36:15 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19220
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 09:36:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl6LR-0002ek-Nz; Thu, 15 Jul 2004 09:32:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl6Ff-0001SX-Cd
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 09:26:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18623
	for <pana@ietf.org>; Thu, 15 Jul 2004 09:26:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl6Fe-0003ba-JA
	for pana@ietf.org; Thu, 15 Jul 2004 09:26:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl6Ek-0003IC-00
	for pana@ietf.org; Thu, 15 Jul 2004 09:25:23 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bl6Dy-0002yJ-00
	for pana@ietf.org; Thu, 15 Jul 2004 09:24:35 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6FDOTpD027760;
	Thu, 15 Jul 2004 22:24:29 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6FDOT92005636;
	Thu, 15 Jul 2004 22:24:29 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	YAA05635 ; Thu, 15 Jul 2004 22:24:29 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA02318; Thu, 15 Jul 2004 22:24:28 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA27887;
	Thu, 15 Jul 2004 22:24:27 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6FDOQpl027076;
	Thu, 15 Jul 2004 22:24:27 +0900 (JST)
Received: from steelhead (iVPN01-145.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0W0010XAKOBD@tsbpo1.po.toshiba.co.jp>; Thu,
	15 Jul 2004 22:24:26 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bl6Ch-0007PY-00; Thu, 15 Jul 2004 06:23:15 -0700
Date: Thu, 15 Jul 2004 09:23:15 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] RE: EAP-based reauth clarification [Re: Mobility Handling
	in PANA]
In-reply-to: <625BE97BF4795E43970345790166B9BC01E2463A@EXC2K01B.cselt.it>
To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Message-id: <20040715132315.GY893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>,
	Yoshihiro Ohba <yohba@tari.toshiba.com>,
	Alper Yegin <alper.yegin@samsung.com>,
	Julien Bournelle <Julien.Bournelle@int-evry.fr>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BC01E2463A@EXC2K01B.cselt.it>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Alper Yegin <alper.yegin@samsung.com>,
        Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Gerardo,

On Thu, Jul 15, 2004 at 11:07:19AM +0200, Giaretta Gerardo wrote:
> > 
> > - What happens if the EAP re-authentication with a single EAP 
> > run (for NAP authentication for example) fails?  Should the 
> > PANA session be deleted, or remain because authorization for 
> > ISP part still exists? In the latter case, are the subsequent 
> > EAP-reauthentications always performed with a single EAP run 
> > for ISP authentication?  And also in the latter case is the 
> > PANA_MAC_KEY needs to be updated after the single EAP run 
> > failure in the EAP re-authentication?  If so, how?
> > 
> 
> I think this is the main issue. Maybe if one re-authentication fails,
> the PANA session should be deleted. This case should be treated as the
> bootstrap case when double authentication is performed and ISP or NAP
> authentication fails.

If you delete the PANA session just because the re-authentication for
NAP fails, this would be a problem for the other (ISP) authorization
state.  


> 
> > > However there might be cases in which it is
> > > convenient to perform both the authentications together (e.g. the 
> > > difference between the residual lifetimes is very small).
> > 
> > > 
> > > [2] What about a scenario in which a new ISP is available? Consider 
> > > that at the first occurence of PANA there were only two 
> > ISPs available 
> > > (ISP1 and ISP2). If a new ISP (ISP3) becomes available 
> > (e.g. after a 
> > > movement of the PaC), I think this must be communicated to the PaC. 
> > > How can we handle this?
> > 
> > After a movement of a PaC, the new ISP information can be 
> > contained in PSR sent from the new PAA.  However, if the PaC 
> > returns a PSA with ISP3 information in a ISP-Information AVP, 
> > the PAA should not perform mobility optimization.
> > 
> 
> Agree.
> 
> > In the case where a new ISP becomes available while the PaC 
> > is connecting to the same PAA, I don't think the PaC has to 
> > know the new ISP immediately.
> > 
> 
> Agree. 
> Note that this implies that if the PaC performs only re-authentication
> procedures, it will never know if a new ISP is available. Do you think
> this is an issue?

I don't think that is an issue because it is a rare case.

Yoshihiro Ohba


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 09:48:05 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19885
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 09:48:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl6OC-0003um-GQ; Thu, 15 Jul 2004 09:35:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl6JU-0002Vm-Ne
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 09:30:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18855
	for <pana@ietf.org>; Thu, 15 Jul 2004 09:30:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl6JU-0004sP-0I
	for pana@ietf.org; Thu, 15 Jul 2004 09:30:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl6Ia-0004ZE-00
	for pana@ietf.org; Thu, 15 Jul 2004 09:29:21 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bl6Hx-0004Fc-00
	for pana@ietf.org; Thu, 15 Jul 2004 09:28:41 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6FDSepD029220;
	Thu, 15 Jul 2004 22:28:40 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6FDSeu7008046;
	Thu, 15 Jul 2004 22:28:40 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	YAA08045 ; Thu, 15 Jul 2004 22:28:40 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA03793; Thu, 15 Jul 2004 22:28:39 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA04001;
	Thu, 15 Jul 2004 22:28:39 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6FDScpl028941;
	Thu, 15 Jul 2004 22:28:38 +0900 (JST)
Received: from steelhead (iVPN01-145.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0W0014PARNBD@tsbpo1.po.toshiba.co.jp>; Thu,
	15 Jul 2004 22:28:37 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bl6Hh-0007Rv-00; Thu, 15 Jul 2004 06:28:25 -0700
Date: Thu, 15 Jul 2004 09:28:23 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (initial text)
In-reply-to: <01fd01c469df$e47a4ba0$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040715132823.GZ893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040714193943.GO893@steelhead>
	<01fd01c469df$e47a4ba0$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Alper,

On Wed, Jul 14, 2004 at 01:19:38PM -0700, Alper Yegin wrote:
> Yoshi,
> 
> > > Also, I didn't understand where Device-ID comes into the picture.
> When
> > > do we update the device-ID?
> > 
> > - When an IP address is used as the device identifier, it can change
> > if the PaC configures its temporary link-local address based on RFC
> > 3041 and the lifetime of the temporary address is expired.
> 
> RFC3041 only deals with global addresses. The link-local addresses stay
> the same (and it does not jeopardize the privacy).

Do you assume two interface identifiers on the same interface (e.g.,
one derived from an IEEE identifier for link-local address and
one randomly generated identifier for global addresses)?

In case where only one interface identifier is used per interface (I
believe this is the typical case), if the interface identifier
changes, doesn't it mean that the link-local address also changes?


>  
> > - When a MAC address is used as the device identifer, it can change if
> > the PaC has multiple interfaces to the same link and switches from one
> > interface to another.
> 
> This is more like session migration from one network interface to
> another. I think we can discuss that, but we need another issue in the
> tracker. Issue 85 is concerned about change of PaC IP address from PRPA
> to POPA.

There is another case in which device-id update is needed.  In
draft-ietf-pana-framework-00.txt, Case D of IPv4 in Appendix A.1 and
Case C of IPv6 in Appendix A.2 use the device id update mechanism.
I once mentioned this:
http://www1.ietf.org/mail-archive/web/pana/current/msg00679.html

Yoshihiro Ohba

> 
> Alper
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > >
> > > I have some editorial comments as well. I'll wait for your response
> to
> > > these first.
> > >
> > > Alper
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: pana-admin@ietf.org [mailto:pana-admin@ietf.org] On Behalf
> Of
> > > > Yoshihiro Ohba
> > > > Sent: Tuesday, May 18, 2004 6:51 PM
> > > > To: pana@ietf.org
> > > > Subject: [Pana] issue85 (initial text)
> > > >
> > > > This is the initial text for issue 85.
> > > >
> > > > Comments are appreciated.
> > > >
> > > > ----------
> > > >
> > > >
> > > > [1] Add the following item in section 4.1.1
> > > >
> > > > "
> > > >    o  IP-Address AVP: Conveys an IP-Address of a PaC.
> > > > "
> > > >
> > > >
> > > > [2] Add the following items in section 4.1.5:
> > > >
> > > > "
> > > >       *  IP address of PaC (may be the same as the Device-Id of
> PaC)
> > > >
> > > >       *  IP address of PAA (may be the same as the Device-Id of
> PAA)
> > > > "
> > > >
> > > >
> > > > [3] Add the following item in section section 4.1.7:
> > > >
> > > > "
> > > >       When an IP-Address AVP is included, the AVP is valid if (i)
> the
> > > >       Address type contained in the AVP matches the expected one
> > > >       (i.e., either IPv4 or IPv6) that is used for the current
> PANA
> > > >       session and (ii) the AVP value matches the one extracted
> from
> > > >       the IP header.
> > > > "
> > > >
> > > > [4] Update the following paragraph of section 4.4
> > > >
> > > > "
> > > >    The second type of re-authentication is based on a single
> protected
> > > >    message exchange without entering the authentication phase.
> > > >    PANA-Reauth-Request and PANA-Reauth-Answer messages are used
> for
> > > this
> > > >    purpose.  If there is an established PANA SA, both the PaC and
> the
> > > >    PAA are allowed to send a PANA-Reauth-Request message to the
> > > >    communicating peer whenever it needs to make sure the
> availability
> > > of
> > > >    the PANA SA on the peer and expect the peer to return a PANA-
> > > >    Reauth-Answer message.  Both PANA-Reauth-Request/
> > > PANA-Reauth-Answer
> > > >    messages MUST be protected with a MAC AVP.
> > > > "
> > > >
> > > > to:
> > > >
> > > > "
> > > >    The second type of re-authentication is based on a single
> protected
> > > >    message exchange without entering the authentication phase.
> > > >    PANA-Reauth-Request and PANA-Reauth-Answer messages are used
> for
> > > >    this purpose.  If there is an established PANA SA, both the PaC
> and
> > > >    the PAA are allowed to send a PANA-Reauth-Request message to
> the
> > > >    communicating peer whenever it needs to make sure the
> availability
> > > >    of the PANA SA on the peer and expect the peer to return a
> > > >    PANA-Reauth-Answer message.  In this case, both
> > > >    PANA-Reauth-Request/PANA-Reauth-Answer messages MUST be
> protected
> > > >    with a MAC AVP.  If there is an established PANA session but
> > > >    without an established PANA SA, both the PaC and the PAA are
> > > >    allowed to send a PANA-Reauth-Request message to the
> communicating
> > > >    peer whenever it needs to make sure the availability of the
> PANA
> > > >    session on the peer and expect the peer to return a
> > > >    PANA-Reauth-Answer message.  In this case, both
> > > >    PANA-Reauth-Request/PANA-Reauth-Answer messages are not
> protected
> > > >    with a MAC AVP.
> > > > "
> > > >
> > > > [5] Insert the following section after section 4.7:
> > > >
> > > > "
> > > > 4.8. Updating PaC's Address
> > > >
> > > > A PaC's address can change in certain situations.  For example,
> the
> > > > PANA framework [I-D.ietf-pana-framework] describes a case in which
> a
> > > > PaC replaces a pre-PANA address (PRPA) a post-PANA address (POPA),
> and
> > > > the PaC and PAA create host routes to each other in order to
> maintain
> > > > on-link communication based on the POPA where the link-layer
> address
> > > > of the PaC is used as the device identifier.  Also, a PaC's device
> > > > identifier may change regardless of whether a link-layer address
> or an
> > > > IP address is used as the device identifier.  As a result, it is
> > > > possible when a link-layer address is used as the device
> identifier
> > > > that both the device identifier and an IP address change.  In any
> > > > case, the PAA needs to be notified about the change of
> address(es).
> > > >
> > > > After the PaC has changed its address(es), it MUST send a
> > > > PANA-Address-Update-Request message to the PAA.  The message
> carries
> > > > the new address(es) in a Device-Id AVP and/or an IP-Address AVP.
> At
> > > > least one of these AVPs MUST appear in the request.  If an IP
> address
> > > > is used as the device identifier, a Device-Id AVP MUST be used and
> an
> > > > IP-Address AVP MUST NOT be used.  If an address contained in the
> > > > request is invalid, the PAA sends a PANA-Error message with a
> result
> > > > code PANA_INVALID_DEVICE_ID or PANA_INVALID_IP_ADDRESS depending
> on
> > > > whether the device identifier or the IP address is invalid (in
> case
> > > > both a Device-Id AVP and an IP-Address AVP are included and both
> are
> > > > invalid, whichever result code is returned).  Otherwise, the PAA
> > > > updates the address(es) of the PaC of the session attributes and
> > > > returns a PANA-Address-Update-Answer message.  If there is an
> > > > established PANA SA, both PANA-Address-Update-Request and
> > > > PANA-Address-Update-Answer messages MUST be protected with a MAC
> AVP.
> > > > "
> > > >
> > > > [6] Change Figure 10 to:
> > > >
> > > > "
> > > >                  Message                     Direction:
> > > >                                              PaC---PAA
> > > >                  ----------------------------------------
> > > >                  PANA-PAA-Discover           -------->
> > > >
> > > >                  PANA-Start-Request          <--------
> > > >                  PANA-Start-Answer           -------->
> > > >
> > > >                  PANA-Auth-Request           <--------
> > > >                  PANA-Auth-Answer            -------->
> > > >
> > > >                  PANA-FirstAuth-End-Request  <--------
> > > >                  PANA-FirstAuth-End-Answer   -------->
> > > >
> > > >                  PANA-Bind-Request           <--------
> > > >                  PANA-Bind-Answer            -------->
> > > >
> > > >                  PANA-Reauth-Request         <------->
> > > >                  PANA-Reauth-Answer          <------->
> > > >
> > > >                  PANA-Termination-Request    <------->
> > > >                  PANA-Termination-Answer     <------->
> > > >
> > > >                  PANA-Address-Update-Request -------->
> > > >                  PANA-Address-Update-Answer  <--------
> > > >
> > > >                  PANA-Error                  <------->
> > > > "
> > > >
> > > > [7] Change sections 6.4.9 and 6.4.10 from:
> > > >
> > > > "
> > > > 6.4.9 PANA-Reauth-Request (PRAR)
> > > >
> > > >    PANA-Reauth-Request (PRAR) is either sent by the PaC or the
> PAA.
> > > >
> > > >          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
> > > >                        < Session-Id >
> > > >                        [ Device-Id ]
> > > >                     *  [ AVP ]
> > > >                    0*1 < MAC >
> > > >
> > > >
> > > > 6.4.10 PANA-Reauth-Answer (PRAA)
> > > >
> > > >    PANA-Reauth-Answer (PRAA) is sent in response to a
> > > >    PANA-Reauth-Request.
> > > >
> > > >          PANA-Reauth-Answer ::= < PANA-Header: 5 >
> > > >                        < Session-Id >
> > > >                        [ Device-Id ]
> > > >                     *  [ AVP ]
> > > >                    0*1 < MAC >
> > > > "
> > > >
> > > > to:
> > > >
> > > > "
> > > > 6.4.9 PANA-Reauth-Request (PRAR)
> > > >
> > > >    PANA-Reauth-Request (PRAR) is either sent by the PaC or the
> PAA.
> > > >
> > > >          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
> > > >                        < Session-Id >
> > > >                     *  [ AVP ]
> > > >                    0*1 < MAC >
> > > >
> > > >
> > > > 6.4.10 PANA-Reauth-Answer (PRAA)
> > > >
> > > >    PANA-Reauth-Answer (PRAA) is sent in response to a
> > > >    PANA-Reauth-Request.
> > > >
> > > >          PANA-Reauth-Answer ::= < PANA-Header: 5 >
> > > >                        < Session-Id >
> > > >                     *  [ AVP ]
> > > >                    0*1 < MAC >
> > > > "
> > > >
> > > > [8] Add the following sections:
> > > >
> > > > "
> > > > 6.4.16 PANA-Address-Update-Request (PAUR)
> > > >
> > > >    PANA-Address-Update-Request (PAUR) is sent by the PaC to the
> PAA.
> > > >
> > > >          PANA-Address-Update-Request ::= < PANA-Header: 9, REQ >
> > > >                        < Session-Id >
> > > >                    0*1 { Device-Id }
> > > >                    0*1 { IP-Address }
> > > >                    0*1 < MAC >
> > > >
> > > >
> > > > 6.4.17 PANA-Address-Update-Answer (PAUA)
> > > >
> > > >    PANA-Address-Update-Answer (PAUA) is sent by the PAA to the PaC
> in
> > > >    response to a PANA-Address-Update-Request.
> > > >
> > > >          PANA-Address-Update-Answer ::= < PANA-Header: 9 >
> > > >                        < Session-Id >
> > > >                    0*1 < MAC >
> > > > "
> > > >
> > > > "
> > > > 6.5.19 IP-Address AVP
> > > >
> > > >    The IP-Address (AVP Code: 1041) contains an IP address of a
> PaC.
> > > >    The payload format of the IP-Address AVP is the same as that of
> the
> > > >    Device-Id AVP (see See section Section 6.5.2).  Address
> families
> > > >    for IPv4 or IPv6 MUST be used for this AVP.
> > > > "
> > > >
> > > >
> > > > [9] Add the following result code in section 6.5.7.2:
> > > >
> > > > "
> > > >    PANA_INVALID_DEVICE_ID  5019
> > > >
> > > >       Error code from PAA to PaC or from PaC to PAA.  This error
> is
> > > >       returned in a PANA-Error message when the Device-Id AVP
> > > >       contained in a received PANA-Bind-Request, PANA-Bind-Answer
> or
> > > >       PANA-Address-Update-Request message is invalid.
> > > >
> > > >    PANA_INVALID_IP_ADDRESS  5020
> > > >
> > > >       Error code from PAA to PaC.  This error is returned in a
> > > >       PANA-Error message when the IP-Address AVP in the received
> > > >       PANA-Address-Update-Request message is invalid.
> > > >
> > > > "
> > > >
> > > > [10]  Modify the AVP occurrence table as:
> > > >
> > > > "
> > > >
> +-----------------------------------------+
> > > >                           |        Message
> |
> > > >                           |          Type
> |
> > > >
> +-----+-----+-----+-----+-----+-----+-----+
> > > >       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA |
> PDI |
> > > >
> --------------------+-----+-----+-----+-----+-----+-----+-----+
> > > >       Result-Code         |  0  |  0  |  0  |  0  |  1  |  1  |  0
> |
> > > >       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  |
> 0-1 |
> > > >       Termination-Cause   |  0  |  0  |  0  |  0  |  0  |  0  |  0
> |
> > > >       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0
> |
> > > >       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0
> |
> > > >       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0
> |
> > > >       Device-Id           |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0
> |
> > > >       Cookie              | 0-1 | 0-1 |  0  |  0  |  0  |  0  |  0
> |
> > > >       Protection-Cap.     | 0-1 |  0  |  0  |  0  | 0-1 |  0  |  0
> |
> > > >       PPAC                | 0-1 |  0  |  0  |  0  |  1  | 0-1 |  0
> |
> > > >       Session-Lifetime    |  0  |  0  |  0  |  0  | 0-1 |  0  |  0
> |
> > > >       Failed-AVP          |  0  |  0  |  0  |  0  |  0  |  0  |  0
> |
> > > >       ISP-Information     |  0+ | 0-1 |  0  |  0  |  0  |  0  |  0
> |
> > > >       NAP-Information     | 0-1 |  0  |  0  |  0  |  0  |  0  |  0
> |
> > > >       EP-Device-Id        |  0  |  0  |  0  |  0  |  0+ |  0  |  0
> |
> > > >       Key-Id              |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0
> |
> > > >       IP-Address          |  0  |  0  |  0  |  0  |  0  |  0  |  0
> |
> > > >
> --------------------+-----+-----+-----+-----+-----+-----+-----+
> > > >
> > > >                  Figure 11: AVP Occurrence Table (1/3)
> > > >
> > > >
> > > +---------------------------------------------+
> > > >                           |      Message
> > > |
> > > >                           |       Type
> > > |
> > > >
> > > +------+------+-----+-----+-----+------+------+
> > > >       Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER |
> > > PFEA |
> > > >
> > > --------------------+------+------+-----+-----+-----+------+------+
> > > >       Result-Code         |  0   |  0   |  0  |  0  |  1  |  1   |
> 0
> > > |
> > > >       Session-Id          |  1   |  1   |  1  |  1  |  1  |  1   |
> 1
> > > |
> > > >       Termination-Cause   |  0   |  0   |  1  |  0  |  0  |  0   |
> 0
> > > |
> > > >       EAP-Payload         |  0   |  0   |  0  |  0  |  0  |  1   |
> 0
> > > |
> > > >       MAC                 | 0-1  | 0-1  | 0-1 | 0-1 | 0-1 | 0-1  |
> 0-1
> > > |
> > > >       Nonce               |  0   |  0   |  0  |  0  |  0  |  0   |
> 0
> > > |
> > > >       Device-Id           |  0   |  0   |  0  |  0  |  0  |  0   |
> 0
> > > |
> > > >       Cookie              |  0   |  0   |  0  |  0  |  0  |  0   |
> 0
> > > |
> > > >       Protection-Cap.     |  0   |  0   |  0  |  0  |  0  |  0   |
> 0
> > > |
> > > >       PPAC                |  0   |  0   |  0  |  0  |  0  |  0   |
> 0
> > > |
> > > >       Session-Lifetime    |  0   |  0   |  0  |  0  |  0  |  0   |
> 0
> > > |
> > > >       Failed-AVP          |  0   |  0   |  0  |  0  |  1  |  0   |
> 0
> > > |
> > > >       ISP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |
> 0
> > > |
> > > >       NAP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |
> 0
> > > |
> > > >       EP-Device-Id        |  0   |  0   |  0  |  0  |  0  |  0   |
> 0
> > > |
> > > >       Key-Id              |  0   |  0   |  0  |  0  |  0  | 0-1  |
> 0-1
> > > |
> > > >       IP-Address          |  0   |  0   |  0  |  0  |  0  |  0   |
> 0
> > > |
> > > >
> > > --------------------+------+------+-----+-----+-----+------+------+
> > > >
> > > >                  Figure 12: AVP Occurrence Table (2/3)
> > > >
> > > >
> > > >                           +-------------+
> > > >                           |   Message   |
> > > >                           |     Type    |
> > > >                           +------+------+
> > > >       Attribute Name      | PAUR | PAUA |
> > > >       --------------------+------+------+
> > > >       Result-Code         |  0   |  0   |
> > > >       Session-Id          |  1   |  1   |
> > > >       Termination-Cause   |  0   |  0   |
> > > >       EAP-Payload         |  0   |  0   |
> > > >       MAC                 | 0-1  | 0-1  |
> > > >       Nonce               |  0   |  0   |
> > > >       Device-Id           | 0-1  |  0   |
> > > >       Cookie              |  0   |  0   |
> > > >       Protection-Cap.     |  0   |  0   |
> > > >       PPAC                |  0   |  0   |
> > > >       Session-Lifetime    |  0   |  0   |
> > > >       Failed-AVP          |  0   |  0   |
> > > >       ISP-Information     |  0   |  0   |
> > > >       NAP-Information     |  0   |  0   |
> > > >       EP-Device-Id        |  0   |  0   |
> > > >       Key-Id              |  0   |  0   |
> > > >       IP-Address          | 0-1  |  0   |
> > > >       --------------------+------+------+
> > > >
> > > >                  Figure 13: AVP Occurrence Table (3/3)
> > > > "
> > > >
> > > > [11]  Change the text in section 7 from:
> > > >
> > > > "
> > > >          PANA-PAA-Discover (PDI)
> > > >          PANA-Start-Request (PSR)*
> > > >          PANA-Start-Answer (PSA)**
> > > >          PANA-Bind-Request (PBR)
> > > >          PANA-FirstAuth-End-Request (PFER)
> > > >          PANA-Reauth-Request (PRAR)
> > > >          PANA-Termination-Request (PTR)
> > > >
> > > >          *)  PSR that carries a Cookie AVP is not retransmitted.
> > > >          **) PSA that does not carry a Cookie AVP is not
> > > retransmitted.
> > > > "
> > > >
> > > > to:
> > > >
> > > > "
> > > >          PANA-PAA-Discover (PDI)
> > > >          PANA-Start-Request (PSR)*
> > > >          PANA-Start-Answer (PSA)**
> > > >          PANA-Bind-Request (PBR)
> > > >          PANA-FirstAuth-End-Request (PFER)
> > > >          PANA-Reauth-Request (PRAR)
> > > >          PANA-Termination-Request (PTR)
> > > >          PANA-Address-Update-Request (PAUR)
> > > >
> > > >          *)  PSR that carries a Cookie AVP is not retransmitted.
> > > >          **) PSA that does not carry a Cookie AVP is not
> > > retransmitted.
> > > > "
> > > >
> > > > [12]  Add the folliwng text in section 8:
> > > >
> > > > "
> > > >    j) Updating PaC's address
> > > >
> > > >    An attacker can generate a PANA-Address-Update-Request with an
> > > >    invalid Device-Id AVP or an IP-Address AVP.  There are several
> > > >    threats:
> > > >
> > > >    - An attacker spoofs an address and registers itself with the
> > > >    address.  If the registered address is not assigned to any PaC,
> > > >    subsequent PANA messages sent from the PAA to the attacker will
> not
> > > >    reach any node and this is not a significant harm.  If the
> > > >    registered address is assigned to some PaC, subsequent PANA
> > > >    messages sent from the PAA to the attacker will reach the PaC,
> but
> > > >    will be silently discarded because the Session-Id is different.
> > > >
> > > >    - An attacker registers other PaC with any address.  As a
> result,
> > > >    subsequent PANA messages sent from the PAA to the PaC will not
> > > >    reach the PaC.
> > > >
> > > >    To avoid all those attacks against an address update, an
> additional
> > > >    mechanism may be defined outside the PANA protocol for the PAA
> to
> > > >    validate ownership of the address.
> > > > "
> > > >
> > > >
> > > > Best regards,
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > > _______________________________________________
> > > > Pana mailing list
> > > > Pana@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pana
> > >
> > >
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 10:00:03 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20610
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 10:00:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl6eS-0000lb-ST; Thu, 15 Jul 2004 09:51:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl6Yx-00075m-Tn
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 09:46:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19768
	for <pana@ietf.org>; Thu, 15 Jul 2004 09:46:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl6Yx-0002LP-8O
	for pana@ietf.org; Thu, 15 Jul 2004 09:46:15 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl6Y0-00021Q-00
	for pana@ietf.org; Thu, 15 Jul 2004 09:45:17 -0400
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx with esmtp (Exim 4.12) id 1Bl6X7-0001Oa-00
	for pana@ietf.org; Thu, 15 Jul 2004 09:44:21 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP
	id 58EFD30CD5; Thu, 15 Jul 2004 15:43:48 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP
	id 3A90530B7E; Thu, 15 Jul 2004 15:43:48 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP
	id 76E0614431; Thu, 15 Jul 2004 15:41:49 +0200 (MET DST)
Message-ID: <40F68A46.1070906@dif.um.es>
Date: Thu, 15 Jul 2004 15:44:38 +0200
From: Rafael Marin Lopez <rafa@dif.um.es>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New: [issue98] Lost answer problem
References: <20040714194319.GP893@steelhead>	<02c301c469e8$077761d0$6401a8c0@sisa.samsung.com>
	<20040715130828.GX893@steelhead>
In-Reply-To: <20040715130828.GX893@steelhead>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Cc: Alper Yegin <alper.yegin@samsung.com>, rafa <rafa@dif.um.es>,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Hi Alper, Yoshihiro see my comments inline.

Yoshihiro Ohba wrote:

>Hi Alper,
>
>On Wed, Jul 14, 2004 at 02:17:53PM -0700, Alper Yegin wrote:
>  
>
>>These are related to the "states". That's why I think the discussion
>>belongs to the state machine I-D. It can discuss definition of states,
>>how the session moves from one state to another, and how messages are
>>processed in each state (ignored, rejected, causes state change, etc.)
>>And all that pana specification can say is what it already says:
>>
>>4.1.7 Message Validity Check
>>
>>   When a PANA message is received, the message is considered to be
>>   invalid at least when one of the following conditions are not met:
>>
>>   o  The message type is one of the expected types in the current
>>      state.
>>
>>I think this is a more scalable and modular approach. 
>>    
>>
>
>I want to make sure the relationship between the PANA specification
>I-D and the PANA state machine I-D.
>  
>
I get your point.

>The suggested approach seems to indicate that the PANA state machine
>I-D is a part of the "complete" set of specification.  (Otherwise,
>pana-pana draft needs to specify what messages types are expected in
>the current state, doesn't it?)
>
>Note that the suggested approach is different from the approach taken
>by RFC 3748 (EAP) and EAP state machine I-D.  RFC 3748 specifies
>everything including which message should be accepted or rejected in
>certain conditions and EAP state machine I-D is just another
>representation of RFC 3748.
>  
>
I would rather PANA draft specifies everything because in some sense
PANA state machine draft should be a reflection on PANA protocol draft
and not adding new additional information to clarify some aspects of
PANA protocol specification.

Regards.

>Yoshihiro Ohba
>
>  
>
>>Alper
>>
>>
>>
>>    
>>
>>>Yoshihiro Ohba
>>>
>>>
>>>      
>>>
>>>>Alper
>>>>
>>>>
>>>>
>>>>_______________________________________________
>>>>Pana mailing list
>>>>Pana@ietf.org
>>>>https://www1.ietf.org/mailman/listinfo/pana
>>>>        
>>>>
>
>_______________________________________________
>Pana mailing list
>Pana@ietf.org
>https://www1.ietf.org/mailman/listinfo/pana
>
>
>  
>


-- 
------------------------------------------------------
Rafael Marin Lopez
Faculty of Computer Science-University of Murcia
30071 Murcia - Spain
Telf: +34968367645    e-mail: rafa@dif.um.es
------------------------------------------------------


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 10:35:22 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24114
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 10:35:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl79N-0004tA-Ai; Thu, 15 Jul 2004 10:23:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl73S-0002JW-HW
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 10:17:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22480
	for <pana@ietf.org>; Thu, 15 Jul 2004 10:17:44 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl73R-0004Ki-Go
	for pana@ietf.org; Thu, 15 Jul 2004 10:17:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl70r-0003t8-00
	for pana@ietf.org; Thu, 15 Jul 2004 10:15:06 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bl6zs-0003XO-00
	for pana@ietf.org; Thu, 15 Jul 2004 10:14:05 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6FEE2pD019337;
	Thu, 15 Jul 2004 23:14:02 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6FEE2Ji004598;
	Thu, 15 Jul 2004 23:14:02 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	ZAA04595 ; Thu, 15 Jul 2004 23:14:02 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id XAA24196; Thu, 15 Jul 2004 23:14:01 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id XAA19617;
	Thu, 15 Jul 2004 23:14:01 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6FEE0pl020166;
	Thu, 15 Jul 2004 23:14:00 +0900 (JST)
Received: from steelhead (iVPN01-145.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0W005GUCVAHM@tsbpo1.po.toshiba.co.jp>; Thu,
	15 Jul 2004 23:13:59 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bl6zc-0007gW-00; Thu, 15 Jul 2004 07:13:48 -0700
Date: Thu, 15 Jul 2004 10:13:48 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New Intro section for framework I-D
In-reply-to: <036001c469ee$e945dfa0$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040715141348.GB893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <036001c469ee$e945dfa0$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Alper,

The suggested text looks fine.

Since the introduction section mentions that SNMP is chosen as the
protocol to carry associated information between the separate nodes, 
we might modify the following text in section 7 (PAA-EP Protocol):

"
   When a client is authenticated and authorized, PAA should notify
   EP(s) and ask for changing filtering rules to allow traffic for a
   recently authorized client.  There needs to be a protocol between PAA
   and EP(s) when these entities are not co-located.  PANA Working Group
   will not be defining a new protocol for this interaction.  Instead,
   it identifies one of the existing protocols that can fit the
   requirements.  An assessment was made in the PANA Working Group and
   SNMPv3 has been chosen as the mandatory PAA-EP protocol.
"

to: 

"
   When a PaC is authenticated and authorized, the PAA should notify
   EP(s) and ask for installing filtering rules to allow the PaC to sent
   and receive data traffic.  SNMP is used between PAA
   and EP(s) for this purpose when these entities are not co-located
   [I-D.ietf-pana-snmp].
"

Yoshihiro Ohba


On Wed, Jul 14, 2004 at 03:07:09PM -0700, Alper Yegin wrote:
>    
> Hello,
> 
> Based on Erik's feedback, I have a new proposed text for the
> introduction section of the PANA Framework document. Comments welcome.
> 
> 
> 
>    PANA is a link-layer agnostic network access authentication protocol
>    that runs between a node that wants to gain access to the network and
>    a server on the network side. PANA defines a new EAP [RFC3748] lower 
>    layer that uses IP between the protocol end points. 
> 
>    The motivation to define such a protocol and the requirements are 
>    described in [I-D.ietf-pana-requirements]. Protocol details are 
>    documented in [I-D.ietf-pana-pana]. [I-D.ietf-pana-ipsec] describes
> use 
>    of IPsec for access control following PANA-based authentication.
> IPsec 
>    can be used for per-packet access control, but nevertheless it is not
> the
>    only way to achieve this functionality. Alternatives include reliance
> on 
>    physical security and link-layer ciphering. Separation of PANA server
>    from the entity enforcing the access control is envisaged as an
> optional
>    deployment choice. SNMP [I-D.ietf-pana-snmp] is chosen as the
> protocol to 
>    carry associated information between the separate nodes.
> 
>    PANA design provides support for various types of deployments. Access
>    networks can differ based on the availability of lower-layer
>    security, placement of PANA entities, choice of client IP
>    configuration and authentication methods, etc.
> 
>    PANA can be used in any access network regardless of the underlying
>    security.  For example, the network might be physically secured, or
>    secured by means of cryptographic mechanisms after the successful
>    client-network authentication.
> 
>    The PANA client, PANA authentication agent, authentication server,
>    and enforcement point are the relevant functional entities in this
>    design.  PANA authentication agent and enforcement point(s) can be
>    placed on various elements in the access network (e.g., access point,
>    access router, dedicated host).
> 
>    IP address configuration mechanisms vary as well. Static
>    configuration, DHCP, stateless address autoconfiguration are possible
>    mechanisms to choose from. If the client configures an IPsec tunnel
>    for enabling per-packet security, configuring IP addresses inside the
>    tunnel becomes relevant, for which there are additional choices such
>    as IKE.
> 
>    This I-D defines a general framework for describing how these various
>    deployment choices are handled by PANA and the access network
>    architectures.  Additionally, two possible deployments are described
>    in detail: PANA over DSL networks and WLAN networks.	
> 
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 11:00:04 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25571
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 11:00:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl7WC-0004K9-0R; Thu, 15 Jul 2004 10:47:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl7OE-0001Wm-SQ
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 10:39:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24424
	for <pana@ietf.org>; Thu, 15 Jul 2004 10:39:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl7OD-0003S3-F4
	for pana@ietf.org; Thu, 15 Jul 2004 10:39:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl7NS-00039e-00
	for pana@ietf.org; Thu, 15 Jul 2004 10:38:27 -0400
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx with esmtp (Exim 4.12) id 1Bl7Me-0002mR-00
	for pana@ietf.org; Thu, 15 Jul 2004 10:37:36 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I0W00J3UDMBHW@dns2.cselt.it> for pana@ietf.org; Thu,
	15 Jul 2004 16:30:11 +0200 (MEST)
Received: from EXC05A.cselt.it ([163.162.36.249]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Thu, 15 Jul 2004 16:35:01 +0200
Received: from EXC2K01B.cselt.it ([163.162.4.97])
	by EXC05A.cselt.it with Microsoft SMTPSVC(5.0.2195.5329); Thu,
	15 Jul 2004 16:37:04 +0200
Date: Thu, 15 Jul 2004 16:37:03 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Pana] RE: EAP-based reauth clarification [Re: Mobility Handling
	in PANA]
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Message-id: <625BE97BF4795E43970345790166B9BC01E2463D@EXC2K01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Pana] RE: EAP-based reauth clarification [Re: Mobility Handling
	in PANA]
Thread-Index: AcRqbzWljxRRZ5p8Th6tBUxjTCqpWAACVh1Q
content-class: urn:content-classes:message
X-OriginalArrivalTime: 15 Jul 2004 14:37:04.0270 (UTC)
	FILETIME=[326B5AE0:01C46A79]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Cc: Alper Yegin <alper.yegin@samsung.com>,
        Julien Bournelle <Julien.Bournelle@int-evry.fr>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Yoshi,

thanks for your reply. See my comments below..

> Hi Gerardo,
>=20
> On Thu, Jul 15, 2004 at 11:07:19AM +0200, Giaretta Gerardo wrote:
> > >=20
> > > - What happens if the EAP re-authentication with a single EAP run=20
> > > (for NAP authentication for example) fails?  Should the PANA=20
> > > session be deleted, or remain because authorization for ISP part=20
> > > still exists? In the latter case, are the subsequent=20
> > > EAP-reauthentications always performed with a single EAP run for=20
> > > ISP authentication?  And also in the latter case is the=20
> > > PANA_MAC_KEY needs to be updated after the single EAP run failure=20
> > > in the EAP re-authentication?  If so, how?
> > >=20
> >=20
> > I think this is the main issue. Maybe if one
> re-authentication fails,
> > the PANA session should be deleted. This case should be
> treated as the
> > bootstrap case when double authentication is performed and
> ISP or NAP
> > authentication fails.
>=20
> If you delete the PANA session just because the
> re-authentication for NAP fails, this would be a problem for=20
> the other (ISP) authorization state. =20
>=20

Are you referring to the fact that the ISP state in the PAA would be
deleted?

Maybe I miss your point or the scenario you are referring to. Should the
PAA mantain the ISP authorization state even if the NAP
(re)authentication fails?
Can you please describe a scenario in which even if the NAP
authentication fails, the ISP authorization state in the PAA must be
kept?		=09

> >=20
> > Agree.
> > Note that this implies that if the PaC performs only=20
> re-authentication
> > procedures, it will never know if a new ISP is available.=20
> Do you think
> > this is an issue?
>=20
> I don't think that is an issue because it is a rare case.
>=20

ok.

--Gerardo

> Yoshihiro Ohba
>=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 11:10:51 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26359
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 11:10:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bl7ln-0000gn-Ft; Thu, 15 Jul 2004 11:03:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bl7id-0007t6-Du
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 11:00:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25615
	for <pana@ietf.org>; Thu, 15 Jul 2004 11:00:16 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Bl7ic-0002cP-H1
	for pana@ietf.org; Thu, 15 Jul 2004 11:00:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Bl7ha-0002I4-00
	for pana@ietf.org; Thu, 15 Jul 2004 10:59:15 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bl7gm-0001yg-00
	for pana@ietf.org; Thu, 15 Jul 2004 10:58:25 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6FEwKpD010976;
	Thu, 15 Jul 2004 23:58:20 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6FEwJ57008363;
	Thu, 15 Jul 2004 23:58:19 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	ZAA08362 ; Thu, 15 Jul 2004 23:58:19 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id XAA18745; Thu, 15 Jul 2004 23:58:17 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id XAA18567;
	Thu, 15 Jul 2004 23:58:17 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6FEwGpl011818;
	Thu, 15 Jul 2004 23:58:16 +0900 (JST)
Received: from steelhead (iVPN01-145.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0W008BZEX1DP@tsbpo1.po.toshiba.co.jp>; Thu,
	15 Jul 2004 23:58:16 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bl7g8-0007rv-00; Thu, 15 Jul 2004 07:57:44 -0700
Date: Thu, 15 Jul 2004 10:57:43 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] RE: EAP-based reauth clarification [Re: Mobility Handling
	in PANA]
In-reply-to: <625BE97BF4795E43970345790166B9BC01E2463D@EXC2K01B.cselt.it>
To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Message-id: <20040715145743.GD893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>,
	Yoshihiro Ohba <yohba@tari.toshiba.com>,
	Alper Yegin <alper.yegin@samsung.com>,
	Julien Bournelle <Julien.Bournelle@int-evry.fr>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <625BE97BF4795E43970345790166B9BC01E2463D@EXC2K01B.cselt.it>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: Alper Yegin <alper.yegin@samsung.com>,
        Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Thu, Jul 15, 2004 at 04:37:03PM +0200, Giaretta Gerardo wrote:
> Hi Yoshi,
> 
> thanks for your reply. See my comments below..
> 
> > Hi Gerardo,
> > 
> > On Thu, Jul 15, 2004 at 11:07:19AM +0200, Giaretta Gerardo wrote:
> > > > 
> > > > - What happens if the EAP re-authentication with a single EAP run 
> > > > (for NAP authentication for example) fails?  Should the PANA 
> > > > session be deleted, or remain because authorization for ISP part 
> > > > still exists? In the latter case, are the subsequent 
> > > > EAP-reauthentications always performed with a single EAP run for 
> > > > ISP authentication?  And also in the latter case is the 
> > > > PANA_MAC_KEY needs to be updated after the single EAP run failure 
> > > > in the EAP re-authentication?  If so, how?
> > > > 
> > > 
> > > I think this is the main issue. Maybe if one
> > re-authentication fails,
> > > the PANA session should be deleted. This case should be
> > treated as the
> > > bootstrap case when double authentication is performed and
> > ISP or NAP
> > > authentication fails.
> > 
> > If you delete the PANA session just because the
> > re-authentication for NAP fails, this would be a problem for 
> > the other (ISP) authorization state.  
> > 
> 
> Are you referring to the fact that the ISP state in the PAA would be
> deleted?

Yes.

> 
> Maybe I miss your point or the scenario you are referring to. Should the
> PAA mantain the ISP authorization state even if the NAP
> (re)authentication fails?
> Can you please describe a scenario in which even if the NAP
> authentication fails, the ISP authorization state in the PAA must be
> kept?			

If you fail NAP authentication, you may lose access to some
application servers within the NAP network for instance.  But if you
keep the ISP state, you can still access to the ISP network.

Yoshihiro Ohba


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 15:03:06 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13973
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 15:03:06 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlBKe-0003JI-Cn; Thu, 15 Jul 2004 14:51:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlBFo-0001pR-Vt
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 14:46:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12652
	for <pana@ietf.org>; Thu, 15 Jul 2004 14:46:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlBFn-0000te-Nt
	for pana@ietf.org; Thu, 15 Jul 2004 14:46:47 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlBEd-0000UO-00
	for pana@ietf.org; Thu, 15 Jul 2004 14:45:36 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12) id 1BlBDd-0007Zu-00
	for pana@ietf.org; Thu, 15 Jul 2004 14:44:34 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0W00C01PDEJC@mailout3.samsung.com> for pana@ietf.org; Fri,
	16 Jul 2004 03:44:02 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0W00B24PDD2J@mailout3.samsung.com> for pana@ietf.org;
	Fri, 16 Jul 2004 03:44:01 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0W002PWPDB0C@mmp1.samsung.com> for
	pana@ietf.org; Fri, 16 Jul 2004 03:44:01 +0900 (KST)
Date: Thu, 15 Jul 2004 11:44:05 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] New Intro section for framework I-D
In-reply-to: <20040715141348.GB893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <000001c46a9b$b6246490$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Makes sense. 

Alper


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Thursday, July 15, 2004 7:14 AM
> To: Alper Yegin
> Cc: pana@ietf.org
> Subject: Re: [Pana] New Intro section for framework I-D
> 
> Hi Alper,
> 
> The suggested text looks fine.
> 
> Since the introduction section mentions that SNMP is chosen as the
> protocol to carry associated information between the separate nodes,
> we might modify the following text in section 7 (PAA-EP Protocol):
> 
> "
>    When a client is authenticated and authorized, PAA should notify
>    EP(s) and ask for changing filtering rules to allow traffic for a
>    recently authorized client.  There needs to be a protocol between
PAA
>    and EP(s) when these entities are not co-located.  PANA Working
Group
>    will not be defining a new protocol for this interaction.  Instead,
>    it identifies one of the existing protocols that can fit the
>    requirements.  An assessment was made in the PANA Working Group and
>    SNMPv3 has been chosen as the mandatory PAA-EP protocol.
> "
> 
> to:
> 
> "
>    When a PaC is authenticated and authorized, the PAA should notify
>    EP(s) and ask for installing filtering rules to allow the PaC to
sent
>    and receive data traffic.  SNMP is used between PAA
>    and EP(s) for this purpose when these entities are not co-located
>    [I-D.ietf-pana-snmp].
> "
> 
> Yoshihiro Ohba
> 
> 
> On Wed, Jul 14, 2004 at 03:07:09PM -0700, Alper Yegin wrote:
> >
> > Hello,
> >
> > Based on Erik's feedback, I have a new proposed text for the
> > introduction section of the PANA Framework document. Comments
welcome.
> >
> >
> >
> >    PANA is a link-layer agnostic network access authentication
protocol
> >    that runs between a node that wants to gain access to the network
and
> >    a server on the network side. PANA defines a new EAP [RFC3748]
lower
> >    layer that uses IP between the protocol end points.
> >
> >    The motivation to define such a protocol and the requirements are
> >    described in [I-D.ietf-pana-requirements]. Protocol details are
> >    documented in [I-D.ietf-pana-pana]. [I-D.ietf-pana-ipsec]
describes
> > use
> >    of IPsec for access control following PANA-based authentication.
> > IPsec
> >    can be used for per-packet access control, but nevertheless it is
not
> > the
> >    only way to achieve this functionality. Alternatives include
reliance
> > on
> >    physical security and link-layer ciphering. Separation of PANA
server
> >    from the entity enforcing the access control is envisaged as an
> > optional
> >    deployment choice. SNMP [I-D.ietf-pana-snmp] is chosen as the
> > protocol to
> >    carry associated information between the separate nodes.
> >
> >    PANA design provides support for various types of deployments.
Access
> >    networks can differ based on the availability of lower-layer
> >    security, placement of PANA entities, choice of client IP
> >    configuration and authentication methods, etc.
> >
> >    PANA can be used in any access network regardless of the
underlying
> >    security.  For example, the network might be physically secured,
or
> >    secured by means of cryptographic mechanisms after the successful
> >    client-network authentication.
> >
> >    The PANA client, PANA authentication agent, authentication
server,
> >    and enforcement point are the relevant functional entities in
this
> >    design.  PANA authentication agent and enforcement point(s) can
be
> >    placed on various elements in the access network (e.g., access
point,
> >    access router, dedicated host).
> >
> >    IP address configuration mechanisms vary as well. Static
> >    configuration, DHCP, stateless address autoconfiguration are
possible
> >    mechanisms to choose from. If the client configures an IPsec
tunnel
> >    for enabling per-packet security, configuring IP addresses inside
the
> >    tunnel becomes relevant, for which there are additional choices
such
> >    as IKE.
> >
> >    This I-D defines a general framework for describing how these
various
> >    deployment choices are handled by PANA and the access network
> >    architectures.  Additionally, two possible deployments are
described
> >    in detail: PANA over DSL networks and WLAN networks.
> >
> >
> >
> >
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 15:34:28 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17402
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 15:34:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlBsL-0006YW-UW; Thu, 15 Jul 2004 15:26:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlBlY-0003xD-JP
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 15:19:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16002
	for <pana@ietf.org>; Thu, 15 Jul 2004 15:19:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlBlX-0004LX-2K
	for pana@ietf.org; Thu, 15 Jul 2004 15:19:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlBkj-00041o-00
	for pana@ietf.org; Thu, 15 Jul 2004 15:18:45 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1BlBjt-0003cD-00
	for pana@ietf.org; Thu, 15 Jul 2004 15:17:53 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0W00J01QWYMX@mailout2.samsung.com> for pana@ietf.org; Fri,
	16 Jul 2004 04:17:22 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0W008QPQWYX0@mailout2.samsung.com> for pana@ietf.org;
	Fri, 16 Jul 2004 04:17:22 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0W00275QWW0C@mmp1.samsung.com> for
	pana@ietf.org; Fri, 16 Jul 2004 04:17:22 +0900 (KST)
Date: Thu, 15 Jul 2004 12:17:26 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] New: [issue98] Lost answer problem
In-reply-to: <20040715130828.GX893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <000401c46aa0$5e896230$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> > These are related to the "states". That's why I think the discussion
> > belongs to the state machine I-D. It can discuss definition of
states,
> > how the session moves from one state to another, and how messages
are
> > processed in each state (ignored, rejected, causes state change,
etc.)
> > And all that pana specification can say is what it already says:
> >
> > 4.1.7 Message Validity Check
> >
> >    When a PANA message is received, the message is considered to be
> >    invalid at least when one of the following conditions are not
met:
> >
> >    o  The message type is one of the expected types in the current
> >       state.
> >
> > I think this is a more scalable and modular approach.
> 
> I want to make sure the relationship between the PANA specification
> I-D and the PANA state machine I-D.
> 
> The suggested approach seems to indicate that the PANA state machine
> I-D is a part of the "complete" set of specification.  (Otherwise,
> pana-pana draft needs to specify what messages types are expected in
> the current state, doesn't it?)

I went over your list of what is rejected (ignored?) in what state. They
looked intuitive to me, I mean things we don't need to spell out. Like
you cannot terminate a session before it starts, or you cannot
reauthenticate before the initial authentication is complete, etc. 

Maybe this is a subjective view. I'm trying to control the verbosity
level and document size without jeopardizing clarity. 

> 
> Note that the suggested approach is different from the approach taken
> by RFC 3748 (EAP) and EAP state machine I-D.  RFC 3748 specifies
> everything including which message should be accepted or rejected in
> certain conditions and EAP state machine I-D is just another
> representation of RFC 3748.

Can you give an example from the EAP spec on that? I'd like to better
understand how we are going to tackle this if we want to include text in
the PANA spec. An example text on PANA (for one message only) would be
useful too. I'd like to make sure we don't unintentionally end up
sliding state machine discussions into the base spec.

Alper



> 
> Yoshihiro Ohba
> 
> >
> > Alper
> >
> >
> >
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > > >
> > > > Alper
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Pana mailing list
> > > > Pana@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pana
> >


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 18:15:50 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09210
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 18:15:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlE3y-0001ni-Ra; Thu, 15 Jul 2004 17:46:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlCCI-0003m8-7F
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 15:47:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18498
	for <pana@ietf.org>; Thu, 15 Jul 2004 15:47:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlCCG-0005Tf-Kb
	for pana@ietf.org; Thu, 15 Jul 2004 15:47:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlC9V-0004pI-00
	for pana@ietf.org; Thu, 15 Jul 2004 15:44:23 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1BlC8G-0004F0-00
	for pana@ietf.org; Thu, 15 Jul 2004 15:43:04 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0W00K01S2XRU@mailout2.samsung.com> for pana@ietf.org; Fri,
	16 Jul 2004 04:42:33 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0W00A8XS2W4L@mailout2.samsung.com> for pana@ietf.org;
	Fri, 16 Jul 2004 04:42:33 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0W00HZVS2ULC@mmp1.samsung.com> for
	pana@ietf.org; Fri, 16 Jul 2004 04:42:32 +0900 (KST)
Date: Thu, 15 Jul 2004 12:42:36 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] issue85 (initial text)
In-reply-to: <20040715132823.GZ893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <000601c46aa3$e25a51c0$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> On Wed, Jul 14, 2004 at 01:19:38PM -0700, Alper Yegin wrote:
> > Yoshi,
> >
> > > > Also, I didn't understand where Device-ID comes into the
picture.
> > When
> > > > do we update the device-ID?
> > >
> > > - When an IP address is used as the device identifier, it can
change
> > > if the PaC configures its temporary link-local address based on
RFC
> > > 3041 and the lifetime of the temporary address is expired.
> >
> > RFC3041 only deals with global addresses. The link-local addresses
stay
> > the same (and it does not jeopardize the privacy).
> 
> Do you assume two interface identifiers on the same interface (e.g.,
> one derived from an IEEE identifier for link-local address and
> one randomly generated identifier for global addresses)?

I think this is possible.

> In case where only one interface identifier is used per interface (I
> believe this is the typical case), if the interface identifier
> changes, doesn't it mean that the link-local address also changes?

I'm not sure if there is any requirement to have the same interface
identifier across all IPv6 addresses on the same physical interface.

> > > - When a MAC address is used as the device identifer, it can
change if
> > > the PaC has multiple interfaces to the same link and switches from
one
> > > interface to another.
> >
> > This is more like session migration from one network interface to
> > another. I think we can discuss that, but we need another issue in
the
> > tracker. Issue 85 is concerned about change of PaC IP address from
PRPA
> > to POPA.
> 
> There is another case in which device-id update is needed.  In
> draft-ietf-pana-framework-00.txt, Case D of IPv4 in Appendix A.1 and
> Case C of IPv6 in Appendix A.2 use the device id update mechanism.
> I once mentioned this:
> http://www1.ietf.org/mail-archive/web/pana/current/msg00679.html

These are in the Appendix because they rely on a secure DHCP scheme that
is not a standard. That's why I don't think they are sufficient to add
new things to the base protocol.

By the way, case C says:

      "... and that there is no need for
      additional PRAR-PRAA exchange to update the PaC-DI."

Alper



> 
> Yoshihiro Ohba
> 
> >
> > Alper
> >
> >
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > > >
> > > > I have some editorial comments as well. I'll wait for your
response
> > to
> > > > these first.
> > > >
> > > > Alper
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: pana-admin@ietf.org [mailto:pana-admin@ietf.org] On
Behalf
> > Of
> > > > > Yoshihiro Ohba
> > > > > Sent: Tuesday, May 18, 2004 6:51 PM
> > > > > To: pana@ietf.org
> > > > > Subject: [Pana] issue85 (initial text)
> > > > >
> > > > > This is the initial text for issue 85.
> > > > >
> > > > > Comments are appreciated.
> > > > >
> > > > > ----------
> > > > >
> > > > >
> > > > > [1] Add the following item in section 4.1.1
> > > > >
> > > > > "
> > > > >    o  IP-Address AVP: Conveys an IP-Address of a PaC.
> > > > > "
> > > > >
> > > > >
> > > > > [2] Add the following items in section 4.1.5:
> > > > >
> > > > > "
> > > > >       *  IP address of PaC (may be the same as the Device-Id
of
> > PaC)
> > > > >
> > > > >       *  IP address of PAA (may be the same as the Device-Id
of
> > PAA)
> > > > > "
> > > > >
> > > > >
> > > > > [3] Add the following item in section section 4.1.7:
> > > > >
> > > > > "
> > > > >       When an IP-Address AVP is included, the AVP is valid if
(i)
> > the
> > > > >       Address type contained in the AVP matches the expected
one
> > > > >       (i.e., either IPv4 or IPv6) that is used for the current
> > PANA
> > > > >       session and (ii) the AVP value matches the one extracted
> > from
> > > > >       the IP header.
> > > > > "
> > > > >
> > > > > [4] Update the following paragraph of section 4.4
> > > > >
> > > > > "
> > > > >    The second type of re-authentication is based on a single
> > protected
> > > > >    message exchange without entering the authentication phase.
> > > > >    PANA-Reauth-Request and PANA-Reauth-Answer messages are
used
> > for
> > > > this
> > > > >    purpose.  If there is an established PANA SA, both the PaC
and
> > the
> > > > >    PAA are allowed to send a PANA-Reauth-Request message to
the
> > > > >    communicating peer whenever it needs to make sure the
> > availability
> > > > of
> > > > >    the PANA SA on the peer and expect the peer to return a
PANA-
> > > > >    Reauth-Answer message.  Both PANA-Reauth-Request/
> > > > PANA-Reauth-Answer
> > > > >    messages MUST be protected with a MAC AVP.
> > > > > "
> > > > >
> > > > > to:
> > > > >
> > > > > "
> > > > >    The second type of re-authentication is based on a single
> > protected
> > > > >    message exchange without entering the authentication phase.
> > > > >    PANA-Reauth-Request and PANA-Reauth-Answer messages are
used
> > for
> > > > >    this purpose.  If there is an established PANA SA, both the
PaC
> > and
> > > > >    the PAA are allowed to send a PANA-Reauth-Request message
to
> > the
> > > > >    communicating peer whenever it needs to make sure the
> > availability
> > > > >    of the PANA SA on the peer and expect the peer to return a
> > > > >    PANA-Reauth-Answer message.  In this case, both
> > > > >    PANA-Reauth-Request/PANA-Reauth-Answer messages MUST be
> > protected
> > > > >    with a MAC AVP.  If there is an established PANA session
but
> > > > >    without an established PANA SA, both the PaC and the PAA
are
> > > > >    allowed to send a PANA-Reauth-Request message to the
> > communicating
> > > > >    peer whenever it needs to make sure the availability of the
> > PANA
> > > > >    session on the peer and expect the peer to return a
> > > > >    PANA-Reauth-Answer message.  In this case, both
> > > > >    PANA-Reauth-Request/PANA-Reauth-Answer messages are not
> > protected
> > > > >    with a MAC AVP.
> > > > > "
> > > > >
> > > > > [5] Insert the following section after section 4.7:
> > > > >
> > > > > "
> > > > > 4.8. Updating PaC's Address
> > > > >
> > > > > A PaC's address can change in certain situations.  For
example,
> > the
> > > > > PANA framework [I-D.ietf-pana-framework] describes a case in
which
> > a
> > > > > PaC replaces a pre-PANA address (PRPA) a post-PANA address
(POPA),
> > and
> > > > > the PaC and PAA create host routes to each other in order to
> > maintain
> > > > > on-link communication based on the POPA where the link-layer
> > address
> > > > > of the PaC is used as the device identifier.  Also, a PaC's
device
> > > > > identifier may change regardless of whether a link-layer
address
> > or an
> > > > > IP address is used as the device identifier.  As a result, it
is
> > > > > possible when a link-layer address is used as the device
> > identifier
> > > > > that both the device identifier and an IP address change.  In
any
> > > > > case, the PAA needs to be notified about the change of
> > address(es).
> > > > >
> > > > > After the PaC has changed its address(es), it MUST send a
> > > > > PANA-Address-Update-Request message to the PAA.  The message
> > carries
> > > > > the new address(es) in a Device-Id AVP and/or an IP-Address
AVP.
> > At
> > > > > least one of these AVPs MUST appear in the request.  If an IP
> > address
> > > > > is used as the device identifier, a Device-Id AVP MUST be used
and
> > an
> > > > > IP-Address AVP MUST NOT be used.  If an address contained in
the
> > > > > request is invalid, the PAA sends a PANA-Error message with a
> > result
> > > > > code PANA_INVALID_DEVICE_ID or PANA_INVALID_IP_ADDRESS
depending
> > on
> > > > > whether the device identifier or the IP address is invalid (in
> > case
> > > > > both a Device-Id AVP and an IP-Address AVP are included and
both
> > are
> > > > > invalid, whichever result code is returned).  Otherwise, the
PAA
> > > > > updates the address(es) of the PaC of the session attributes
and
> > > > > returns a PANA-Address-Update-Answer message.  If there is an
> > > > > established PANA SA, both PANA-Address-Update-Request and
> > > > > PANA-Address-Update-Answer messages MUST be protected with a
MAC
> > AVP.
> > > > > "
> > > > >
> > > > > [6] Change Figure 10 to:
> > > > >
> > > > > "
> > > > >                  Message                     Direction:
> > > > >                                              PaC---PAA
> > > > >                  ----------------------------------------
> > > > >                  PANA-PAA-Discover           -------->
> > > > >
> > > > >                  PANA-Start-Request          <--------
> > > > >                  PANA-Start-Answer           -------->
> > > > >
> > > > >                  PANA-Auth-Request           <--------
> > > > >                  PANA-Auth-Answer            -------->
> > > > >
> > > > >                  PANA-FirstAuth-End-Request  <--------
> > > > >                  PANA-FirstAuth-End-Answer   -------->
> > > > >
> > > > >                  PANA-Bind-Request           <--------
> > > > >                  PANA-Bind-Answer            -------->
> > > > >
> > > > >                  PANA-Reauth-Request         <------->
> > > > >                  PANA-Reauth-Answer          <------->
> > > > >
> > > > >                  PANA-Termination-Request    <------->
> > > > >                  PANA-Termination-Answer     <------->
> > > > >
> > > > >                  PANA-Address-Update-Request -------->
> > > > >                  PANA-Address-Update-Answer  <--------
> > > > >
> > > > >                  PANA-Error                  <------->
> > > > > "
> > > > >
> > > > > [7] Change sections 6.4.9 and 6.4.10 from:
> > > > >
> > > > > "
> > > > > 6.4.9 PANA-Reauth-Request (PRAR)
> > > > >
> > > > >    PANA-Reauth-Request (PRAR) is either sent by the PaC or the
> > PAA.
> > > > >
> > > > >          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
> > > > >                        < Session-Id >
> > > > >                        [ Device-Id ]
> > > > >                     *  [ AVP ]
> > > > >                    0*1 < MAC >
> > > > >
> > > > >
> > > > > 6.4.10 PANA-Reauth-Answer (PRAA)
> > > > >
> > > > >    PANA-Reauth-Answer (PRAA) is sent in response to a
> > > > >    PANA-Reauth-Request.
> > > > >
> > > > >          PANA-Reauth-Answer ::= < PANA-Header: 5 >
> > > > >                        < Session-Id >
> > > > >                        [ Device-Id ]
> > > > >                     *  [ AVP ]
> > > > >                    0*1 < MAC >
> > > > > "
> > > > >
> > > > > to:
> > > > >
> > > > > "
> > > > > 6.4.9 PANA-Reauth-Request (PRAR)
> > > > >
> > > > >    PANA-Reauth-Request (PRAR) is either sent by the PaC or the
> > PAA.
> > > > >
> > > > >          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
> > > > >                        < Session-Id >
> > > > >                     *  [ AVP ]
> > > > >                    0*1 < MAC >
> > > > >
> > > > >
> > > > > 6.4.10 PANA-Reauth-Answer (PRAA)
> > > > >
> > > > >    PANA-Reauth-Answer (PRAA) is sent in response to a
> > > > >    PANA-Reauth-Request.
> > > > >
> > > > >          PANA-Reauth-Answer ::= < PANA-Header: 5 >
> > > > >                        < Session-Id >
> > > > >                     *  [ AVP ]
> > > > >                    0*1 < MAC >
> > > > > "
> > > > >
> > > > > [8] Add the following sections:
> > > > >
> > > > > "
> > > > > 6.4.16 PANA-Address-Update-Request (PAUR)
> > > > >
> > > > >    PANA-Address-Update-Request (PAUR) is sent by the PaC to
the
> > PAA.
> > > > >
> > > > >          PANA-Address-Update-Request ::= < PANA-Header: 9, REQ
>
> > > > >                        < Session-Id >
> > > > >                    0*1 { Device-Id }
> > > > >                    0*1 { IP-Address }
> > > > >                    0*1 < MAC >
> > > > >
> > > > >
> > > > > 6.4.17 PANA-Address-Update-Answer (PAUA)
> > > > >
> > > > >    PANA-Address-Update-Answer (PAUA) is sent by the PAA to the
PaC
> > in
> > > > >    response to a PANA-Address-Update-Request.
> > > > >
> > > > >          PANA-Address-Update-Answer ::= < PANA-Header: 9 >
> > > > >                        < Session-Id >
> > > > >                    0*1 < MAC >
> > > > > "
> > > > >
> > > > > "
> > > > > 6.5.19 IP-Address AVP
> > > > >
> > > > >    The IP-Address (AVP Code: 1041) contains an IP address of a
> > PaC.
> > > > >    The payload format of the IP-Address AVP is the same as
that of
> > the
> > > > >    Device-Id AVP (see See section Section 6.5.2).  Address
> > families
> > > > >    for IPv4 or IPv6 MUST be used for this AVP.
> > > > > "
> > > > >
> > > > >
> > > > > [9] Add the following result code in section 6.5.7.2:
> > > > >
> > > > > "
> > > > >    PANA_INVALID_DEVICE_ID  5019
> > > > >
> > > > >       Error code from PAA to PaC or from PaC to PAA.  This
error
> > is
> > > > >       returned in a PANA-Error message when the Device-Id AVP
> > > > >       contained in a received PANA-Bind-Request,
PANA-Bind-Answer
> > or
> > > > >       PANA-Address-Update-Request message is invalid.
> > > > >
> > > > >    PANA_INVALID_IP_ADDRESS  5020
> > > > >
> > > > >       Error code from PAA to PaC.  This error is returned in a
> > > > >       PANA-Error message when the IP-Address AVP in the
received
> > > > >       PANA-Address-Update-Request message is invalid.
> > > > >
> > > > > "
> > > > >
> > > > > [10]  Modify the AVP occurrence table as:
> > > > >
> > > > > "
> > > > >
> > +-----------------------------------------+
> > > > >                           |        Message
> > |
> > > > >                           |          Type
> > |
> > > > >
> > +-----+-----+-----+-----+-----+-----+-----+
> > > > >       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA
|
> > PDI |
> > > > >
> > --------------------+-----+-----+-----+-----+-----+-----+-----+
> > > > >       Result-Code         |  0  |  0  |  0  |  0  |  1  |  1
|  0
> > |
> > > > >       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1
|
> > 0-1 |
> > > > >       Termination-Cause   |  0  |  0  |  0  |  0  |  0  |  0
|  0
> > |
> > > > >       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0
|  0
> > |
> > > > >       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1
|  0
> > |
> > > > >       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0
|  0
> > |
> > > > >       Device-Id           |  0  |  0  |  0  |  0  | 0-1 | 0-1
|  0
> > |
> > > > >       Cookie              | 0-1 | 0-1 |  0  |  0  |  0  |  0
|  0
> > |
> > > > >       Protection-Cap.     | 0-1 |  0  |  0  |  0  | 0-1 |  0
|  0
> > |
> > > > >       PPAC                | 0-1 |  0  |  0  |  0  |  1  | 0-1
|  0
> > |
> > > > >       Session-Lifetime    |  0  |  0  |  0  |  0  | 0-1 |  0
|  0
> > |
> > > > >       Failed-AVP          |  0  |  0  |  0  |  0  |  0  |  0
|  0
> > |
> > > > >       ISP-Information     |  0+ | 0-1 |  0  |  0  |  0  |  0
|  0
> > |
> > > > >       NAP-Information     | 0-1 |  0  |  0  |  0  |  0  |  0
|  0
> > |
> > > > >       EP-Device-Id        |  0  |  0  |  0  |  0  |  0+ |  0
|  0
> > |
> > > > >       Key-Id              |  0  |  0  |  0  |  0  | 0-1 | 0-1
|  0
> > |
> > > > >       IP-Address          |  0  |  0  |  0  |  0  |  0  |  0
|  0
> > |
> > > > >
> > --------------------+-----+-----+-----+-----+-----+-----+-----+
> > > > >
> > > > >                  Figure 11: AVP Occurrence Table (1/3)
> > > > >
> > > > >
> > > > +---------------------------------------------+
> > > > >                           |      Message
> > > > |
> > > > >                           |       Type
> > > > |
> > > > >
> > > > +------+------+-----+-----+-----+------+------+
> > > > >       Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
PFER |
> > > > PFEA |
> > > > >
> > > >
--------------------+------+------+-----+-----+-----+------+------+
> > > > >       Result-Code         |  0   |  0   |  0  |  0  |  1  |  1
|
> > 0
> > > > |
> > > > >       Session-Id          |  1   |  1   |  1  |  1  |  1  |  1
|
> > 1
> > > > |
> > > > >       Termination-Cause   |  0   |  0   |  1  |  0  |  0  |  0
|
> > 0
> > > > |
> > > > >       EAP-Payload         |  0   |  0   |  0  |  0  |  0  |  1
|
> > 0
> > > > |
> > > > >       MAC                 | 0-1  | 0-1  | 0-1 | 0-1 | 0-1 |
0-1  |
> > 0-1
> > > > |
> > > > >       Nonce               |  0   |  0   |  0  |  0  |  0  |  0
|
> > 0
> > > > |
> > > > >       Device-Id           |  0   |  0   |  0  |  0  |  0  |  0
|
> > 0
> > > > |
> > > > >       Cookie              |  0   |  0   |  0  |  0  |  0  |  0
|
> > 0
> > > > |
> > > > >       Protection-Cap.     |  0   |  0   |  0  |  0  |  0  |  0
|
> > 0
> > > > |
> > > > >       PPAC                |  0   |  0   |  0  |  0  |  0  |  0
|
> > 0
> > > > |
> > > > >       Session-Lifetime    |  0   |  0   |  0  |  0  |  0  |  0
|
> > 0
> > > > |
> > > > >       Failed-AVP          |  0   |  0   |  0  |  0  |  1  |  0
|
> > 0
> > > > |
> > > > >       ISP-Information     |  0   |  0   |  0  |  0  |  0  |  0
|
> > 0
> > > > |
> > > > >       NAP-Information     |  0   |  0   |  0  |  0  |  0  |  0
|
> > 0
> > > > |
> > > > >       EP-Device-Id        |  0   |  0   |  0  |  0  |  0  |  0
|
> > 0
> > > > |
> > > > >       Key-Id              |  0   |  0   |  0  |  0  |  0  |
0-1  |
> > 0-1
> > > > |
> > > > >       IP-Address          |  0   |  0   |  0  |  0  |  0  |  0
|
> > 0
> > > > |
> > > > >
> > > >
--------------------+------+------+-----+-----+-----+------+------+
> > > > >
> > > > >                  Figure 12: AVP Occurrence Table (2/3)
> > > > >
> > > > >
> > > > >                           +-------------+
> > > > >                           |   Message   |
> > > > >                           |     Type    |
> > > > >                           +------+------+
> > > > >       Attribute Name      | PAUR | PAUA |
> > > > >       --------------------+------+------+
> > > > >       Result-Code         |  0   |  0   |
> > > > >       Session-Id          |  1   |  1   |
> > > > >       Termination-Cause   |  0   |  0   |
> > > > >       EAP-Payload         |  0   |  0   |
> > > > >       MAC                 | 0-1  | 0-1  |
> > > > >       Nonce               |  0   |  0   |
> > > > >       Device-Id           | 0-1  |  0   |
> > > > >       Cookie              |  0   |  0   |
> > > > >       Protection-Cap.     |  0   |  0   |
> > > > >       PPAC                |  0   |  0   |
> > > > >       Session-Lifetime    |  0   |  0   |
> > > > >       Failed-AVP          |  0   |  0   |
> > > > >       ISP-Information     |  0   |  0   |
> > > > >       NAP-Information     |  0   |  0   |
> > > > >       EP-Device-Id        |  0   |  0   |
> > > > >       Key-Id              |  0   |  0   |
> > > > >       IP-Address          | 0-1  |  0   |
> > > > >       --------------------+------+------+
> > > > >
> > > > >                  Figure 13: AVP Occurrence Table (3/3)
> > > > > "
> > > > >
> > > > > [11]  Change the text in section 7 from:
> > > > >
> > > > > "
> > > > >          PANA-PAA-Discover (PDI)
> > > > >          PANA-Start-Request (PSR)*
> > > > >          PANA-Start-Answer (PSA)**
> > > > >          PANA-Bind-Request (PBR)
> > > > >          PANA-FirstAuth-End-Request (PFER)
> > > > >          PANA-Reauth-Request (PRAR)
> > > > >          PANA-Termination-Request (PTR)
> > > > >
> > > > >          *)  PSR that carries a Cookie AVP is not
retransmitted.
> > > > >          **) PSA that does not carry a Cookie AVP is not
> > > > retransmitted.
> > > > > "
> > > > >
> > > > > to:
> > > > >
> > > > > "
> > > > >          PANA-PAA-Discover (PDI)
> > > > >          PANA-Start-Request (PSR)*
> > > > >          PANA-Start-Answer (PSA)**
> > > > >          PANA-Bind-Request (PBR)
> > > > >          PANA-FirstAuth-End-Request (PFER)
> > > > >          PANA-Reauth-Request (PRAR)
> > > > >          PANA-Termination-Request (PTR)
> > > > >          PANA-Address-Update-Request (PAUR)
> > > > >
> > > > >          *)  PSR that carries a Cookie AVP is not
retransmitted.
> > > > >          **) PSA that does not carry a Cookie AVP is not
> > > > retransmitted.
> > > > > "
> > > > >
> > > > > [12]  Add the folliwng text in section 8:
> > > > >
> > > > > "
> > > > >    j) Updating PaC's address
> > > > >
> > > > >    An attacker can generate a PANA-Address-Update-Request with
an
> > > > >    invalid Device-Id AVP or an IP-Address AVP.  There are
several
> > > > >    threats:
> > > > >
> > > > >    - An attacker spoofs an address and registers itself with
the
> > > > >    address.  If the registered address is not assigned to any
PaC,
> > > > >    subsequent PANA messages sent from the PAA to the attacker
will
> > not
> > > > >    reach any node and this is not a significant harm.  If the
> > > > >    registered address is assigned to some PaC, subsequent PANA
> > > > >    messages sent from the PAA to the attacker will reach the
PaC,
> > but
> > > > >    will be silently discarded because the Session-Id is
different.
> > > > >
> > > > >    - An attacker registers other PaC with any address.  As a
> > result,
> > > > >    subsequent PANA messages sent from the PAA to the PaC will
not
> > > > >    reach the PaC.
> > > > >
> > > > >    To avoid all those attacks against an address update, an
> > additional
> > > > >    mechanism may be defined outside the PANA protocol for the
PAA
> > to
> > > > >    validate ownership of the address.
> > > > > "
> > > > >
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > > _______________________________________________
> > > > > Pana mailing list
> > > > > Pana@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/pana
> > > >
> > > >
> > > > _______________________________________________
> > > > Pana mailing list
> > > > Pana@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pana
> >
> >
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 18:43:06 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13318
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 18:43:06 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlEr7-0000qx-1w; Thu, 15 Jul 2004 18:37:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlEeU-0002Nv-4E
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 18:24:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11248
	for <pana@ietf.org>; Thu, 15 Jul 2004 18:24:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlEeS-0000ou-K6
	for pana@ietf.org; Thu, 15 Jul 2004 18:24:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlEUv-0006YB-00
	for pana@ietf.org; Thu, 15 Jul 2004 18:14:39 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BlEEY-0003Df-00
	for pana@ietf.org; Thu, 15 Jul 2004 17:57:42 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6FLvepD007011;
	Fri, 16 Jul 2004 06:57:40 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6FLveXu019827;
	Fri, 16 Jul 2004 06:57:40 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	GAA19826 ; Fri, 16 Jul 2004 06:57:39 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA01783; Fri, 16 Jul 2004 06:57:39 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA08858;
	Fri, 16 Jul 2004 06:57:38 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6FLvcpl004745;
	Fri, 16 Jul 2004 06:57:38 +0900 (JST)
Received: from steelhead (iVPN01-047.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0W005FJYC067@tsbpo1.po.toshiba.co.jp>; Fri,
	16 Jul 2004 06:57:37 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlEEF-0000fY-00; Thu, 15 Jul 2004 14:57:23 -0700
Date: Thu, 15 Jul 2004 17:57:22 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New: [issue98] Lost answer problem
In-reply-to: <000401c46aa0$5e896230$9b1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040715215722.GK893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040715130828.GX893@steelhead>
	<000401c46aa0$5e896230$9b1d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Couple of examples in RFC 3748:

- On resending a Response in response to a duplicate Request

"
      If a peer receives a valid duplicate Request for which it has
      already sent a Response, it MUST resend its original Response
      without reprocessing the Request.  Requests MUST be processed in
      the order that they are received, and MUST be processed to their
      completion before inspecting the next Request.
"

- On Nak message rejection.

"
   A peer MUST NOT send a Nak (legacy or expanded) in reply to a Request
   after an initial non-Nak Response has been sent.  Since spoofed EAP
   Request packets may be sent by an attacker, an authenticator
   receiving an unexpected Nak SHOULD discard it and log the event.
"

- On EAP-Success/Failure message rejection:

"
   Success and Failure packets MUST NOT be sent by an EAP authenticator
   if the specification of the given method does not explicitly permit
   the method to finish at that point.  A peer EAP implementation
   receiving a Success or Failure packet where sending one is not
   explicitly permitted MUST silently discard it.  By default, an EAP
   peer MUST silently discard a "canned" Success packet (a Success
   packet sent immediately upon connection).  This ensures that a rogue
   authenticator will not be able to bypass mutual authentication by
   sending a Success packet prior to conclusion of the EAP method
   conversation.
"

- On prohibition of mixing Requests with different types.

"
   Once a peer has sent a Response of the same Type as the initial
   Request, an authenticator MUST NOT send a Request of a different Type
   prior to completion of the final round of a given method (with the
   exception of a Notification-Request) and MUST NOT send a Request for
   an additional method of any Type after completion of the initial
   authentication method; a peer receiving such Requests MUST treat them
   as invalid, and silently discard them.  As a result, Identity Requery
   is not supported.
"

Regards,

Yoshihiro Ohba




On Thu, Jul 15, 2004 at 12:17:26PM -0700, Alper Yegin wrote:
> > > These are related to the "states". That's why I think the discussion
> > > belongs to the state machine I-D. It can discuss definition of
> states,
> > > how the session moves from one state to another, and how messages
> are
> > > processed in each state (ignored, rejected, causes state change,
> etc.)
> > > And all that pana specification can say is what it already says:
> > >
> > > 4.1.7 Message Validity Check
> > >
> > >    When a PANA message is received, the message is considered to be
> > >    invalid at least when one of the following conditions are not
> met:
> > >
> > >    o  The message type is one of the expected types in the current
> > >       state.
> > >
> > > I think this is a more scalable and modular approach.
> > 
> > I want to make sure the relationship between the PANA specification
> > I-D and the PANA state machine I-D.
> > 
> > The suggested approach seems to indicate that the PANA state machine
> > I-D is a part of the "complete" set of specification.  (Otherwise,
> > pana-pana draft needs to specify what messages types are expected in
> > the current state, doesn't it?)
> 
> I went over your list of what is rejected (ignored?) in what state. They
> looked intuitive to me, I mean things we don't need to spell out. Like
> you cannot terminate a session before it starts, or you cannot
> reauthenticate before the initial authentication is complete, etc. 
> 
> Maybe this is a subjective view. I'm trying to control the verbosity
> level and document size without jeopardizing clarity. 
> 
> > 
> > Note that the suggested approach is different from the approach taken
> > by RFC 3748 (EAP) and EAP state machine I-D.  RFC 3748 specifies
> > everything including which message should be accepted or rejected in
> > certain conditions and EAP state machine I-D is just another
> > representation of RFC 3748.
> 
> Can you give an example from the EAP spec on that? I'd like to better
> understand how we are going to tackle this if we want to include text in
> the PANA spec. An example text on PANA (for one message only) would be
> useful too. I'd like to make sure we don't unintentionally end up
> sliding state machine discussions into the base spec.
> 
> Alper
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > >
> > > Alper
> > >
> > >
> > >
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > >
> > > > > Alper
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Pana mailing list
> > > > > Pana@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/pana
> > >
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 18:56:36 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15670
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 18:56:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlF6W-0006RY-I0; Thu, 15 Jul 2004 18:53:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlErk-0001CT-4r
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 18:38:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12874
	for <pana@ietf.org>; Thu, 15 Jul 2004 18:38:08 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlEri-0003YV-C3
	for pana@ietf.org; Thu, 15 Jul 2004 18:38:10 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlEhu-0001b0-00
	for pana@ietf.org; Thu, 15 Jul 2004 18:28:04 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BlEbO-00001U-00
	for pana@ietf.org; Thu, 15 Jul 2004 18:21:18 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6FMLCpD014177;
	Fri, 16 Jul 2004 07:21:12 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6FMLCnD028057;
	Fri, 16 Jul 2004 07:21:12 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	HAA28056 ; Fri, 16 Jul 2004 07:21:12 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA08061; Fri, 16 Jul 2004 07:21:12 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA29991;
	Fri, 16 Jul 2004 07:21:11 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6FMLApl015521;
	Fri, 16 Jul 2004 07:21:10 +0900 (JST)
Received: from steelhead (iVPN01-047.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0W005VSZF867@tsbpo1.po.toshiba.co.jp>; Fri,
	16 Jul 2004 07:21:10 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlEaw-0000kf-00; Thu, 15 Jul 2004 15:20:50 -0700
Date: Thu, 15 Jul 2004 18:20:50 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (initial text)
In-reply-to: <000601c46aa3$e25a51c0$9b1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040715222050.GL893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040715132823.GZ893@steelhead>
	<000601c46aa3$e25a51c0$9b1d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Thu, Jul 15, 2004 at 12:42:36PM -0700, Alper Yegin wrote:
> > On Wed, Jul 14, 2004 at 01:19:38PM -0700, Alper Yegin wrote:
> > > Yoshi,
> > >
> > > > > Also, I didn't understand where Device-ID comes into the
> picture.
> > > When
> > > > > do we update the device-ID?
> > > >
> > > > - When an IP address is used as the device identifier, it can
> change
> > > > if the PaC configures its temporary link-local address based on
> RFC
> > > > 3041 and the lifetime of the temporary address is expired.
> > >
> > > RFC3041 only deals with global addresses. The link-local addresses
> stay
> > > the same (and it does not jeopardize the privacy).
> > 
> > Do you assume two interface identifiers on the same interface (e.g.,
> > one derived from an IEEE identifier for link-local address and
> > one randomly generated identifier for global addresses)?
> 
> I think this is possible.

I think so.

> 
> > In case where only one interface identifier is used per interface (I
> > believe this is the typical case), if the interface identifier
> > changes, doesn't it mean that the link-local address also changes?
> 
> I'm not sure if there is any requirement to have the same interface
> identifier across all IPv6 addresses on the same physical interface.

I don't think there is such a requirement.  But should we mandate the
use of multiple interface identifiers to support RFC 3041 with PANA?
If so, I think we should explicitly mention this in the framework
document.

> 
> > > > - When a MAC address is used as the device identifer, it can
> change if
> > > > the PaC has multiple interfaces to the same link and switches from
> one
> > > > interface to another.
> > >
> > > This is more like session migration from one network interface to
> > > another. I think we can discuss that, but we need another issue in
> the
> > > tracker. Issue 85 is concerned about change of PaC IP address from
> PRPA
> > > to POPA.
> > 
> > There is another case in which device-id update is needed.  In
> > draft-ietf-pana-framework-00.txt, Case D of IPv4 in Appendix A.1 and
> > Case C of IPv6 in Appendix A.2 use the device id update mechanism.
> > I once mentioned this:
> > http://www1.ietf.org/mail-archive/web/pana/current/msg00679.html
> 
> These are in the Appendix because they rely on a secure DHCP scheme that
> is not a standard. That's why I don't think they are sufficient to add
> new things to the base protocol.
> 
> By the way, case C says:
> 
>       "... and that there is no need for
>       additional PRAR-PRAA exchange to update the PaC-DI."

The text is correct.  Figure 20 in the framework draft contains a bug.  I
will fix it.

Yoshihiro Ohba

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 19:03:29 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17089
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 19:03:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlF7S-0007LJ-50; Thu, 15 Jul 2004 18:54:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlF31-0004yf-Ag
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 18:49:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15031
	for <pana@ietf.org>; Thu, 15 Jul 2004 18:49:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlF2z-00068V-M5
	for pana@ietf.org; Thu, 15 Jul 2004 18:49:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlEvX-0004Mr-00
	for pana@ietf.org; Thu, 15 Jul 2004 18:42:08 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1BlEkP-00029p-00
	for pana@ietf.org; Thu, 15 Jul 2004 18:30:37 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0W00501ZU0GN@mailout2.samsung.com> for pana@ietf.org; Fri,
	16 Jul 2004 07:30:00 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0W0051TZTZDR@mailout2.samsung.com> for pana@ietf.org;
	Fri, 16 Jul 2004 07:29:59 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0W0040MZTXT7@mmp2.samsung.com> for
	pana@ietf.org; Fri, 16 Jul 2004 07:29:59 +0900 (KST)
Date: Thu, 15 Jul 2004 15:30:03 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <01aa01c46abb$46a98580$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Subject: [Pana] Issue 103: "PANA session" needs more clarification
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Here is the proposed text update:

Change:

PANA Session:

      PANA session is defined as the exchange of messages between the
      PANA Client (PaC) and the PANA Authentication Agent (PAA) to
      authenticate a user (PaC) for network access.  If the
      authentication is unsuccessful, the session is terminated.  The
      session is considered as active until there is a disconnect
      indication by the PaC or the PAA terminates it.  A distinct PANA
      session is associated with a pair of device identifiers of PaC and
      PAA.  For example, if the PaC has two interfaces connected to the
      same IP link with different IP addresses and IP address is used as
      a device identifier, a distinct PANA session will be created per
      interface if both interfaces addresses need to be authorized for
      network access.

   Session Identifier:

      This identifier is used to uniquely identify a PANA session on the
      PAA and PaC.  It is included in PANA messages to bind the message
      to a specific PANA session.

To:

   PANA Session:

      A PANA session begins with an initial handshake between the PANA
      Client (PaC) and the PANA Authentication Agent (PAA), and
      terminates due to an authentication failure, a timeout, or an
      explicit termination message. A fixed session identifier is 
      maintained throughout a session. A session cannot be shared
      across multiple physical network interfaces, but a physical
      network interface can have multiple sessions at a time. 


   Session Identifier:

      This identifier is used to uniquely identify a PANA session on the
      PAA and PaC. It includes an identifier of the PAA, therefore it 
      cannot be shared across multiple PAAs. It is included in PANA
messages 
      to bind the message to a specific PANA session. This bidirectional

      identifier is allocated by the PAA during the initial handshake 
      and freed when the session terminates. 




_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 19:16:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18005
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 19:16:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlFHp-0001uD-6p; Thu, 15 Jul 2004 19:05:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlFCj-0000Qu-3K
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 18:59:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16431
	for <pana@ietf.org>; Thu, 15 Jul 2004 18:59:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlFCh-0000j1-3e
	for pana@ietf.org; Thu, 15 Jul 2004 18:59:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlF7z-0007C2-00
	for pana@ietf.org; Thu, 15 Jul 2004 18:55:01 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BlF1G-0005a7-00
	for pana@ietf.org; Thu, 15 Jul 2004 18:48:02 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6FMm1pD022631;
	Fri, 16 Jul 2004 07:48:01 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6FMm1o3008297;
	Fri, 16 Jul 2004 07:48:01 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	HAA08291 ; Fri, 16 Jul 2004 07:48:01 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA15341; Fri, 16 Jul 2004 07:48:01 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA18371;
	Fri, 16 Jul 2004 07:48:00 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6FMlxpl026972;
	Fri, 16 Jul 2004 07:47:59 +0900 (JST)
Received: from steelhead (iVPN01-039.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0X007G10NXCE@tsbpo1.po.toshiba.co.jp>; Fri,
	16 Jul 2004 07:47:58 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlF0T-0000sV-00; Thu, 15 Jul 2004 15:47:13 -0700
Date: Thu, 15 Jul 2004 18:47:13 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040715224713.GN893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Subject: [Pana] Bug in sequence number management
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org


In section 4.1.4 of draft-ietf-pana-pana-04, change:

"
   o  When a message is received, it is considered valid in terms of
      sequence numbers if and only if (i) its tseq is greater than the
      tseq of the last accepted message and (ii) its rseq falls in the
      range between the tseq of the last acknowledged message + 1 and
      the tseq of the last transmitted message.
"

to:

"
   o  When a message is received, it is considered valid in terms of
      sequence numbers if and only if (i) its tseq is greater than the
      tseq of the last accepted message and (ii) its rseq falls in the
      range between the tseq of the last acknowledged message and
      the tseq of the last transmitted message.
"

Yoshihiro Ohba


----- Forwarded message from Alper Yegin <alper.yegin@samsung.com> -----

From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] New: [issue98] Lost answer problem
To: 'Yoshihiro Ohba' <yohba@tari.toshiba.com>,
	'Rafael Marin Lopez' <rafa@dif.um.es>
Importance: Normal
X-VirusChecked: Checked
X-Env-Sender: alper.yegin@samsung.com
X-Msg-Ref: server-13.tower-76.messagelabs.com!1089756330!2585408
X-StarScan-Version: 5.2.10; banners=-,-,-
X-Originating-IP: [203.254.224.33]
X-SpamReason: No, hits=0.0 required=7.0 tests=CYNIC_B,

Hmmm, looks like it.

Does increasing the range by 1 fix the problem (without breaking
anything else)? 

Like:

[tseq of the last acknowledged message, tseq of the last
transmitted message]

Alper


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Tuesday, July 13, 2004 2:49 PM
> To: Rafael Marin Lopez; Alper Yegin
> Cc: Yoshihiro Ohba
> Subject: Re: [Pana] New: [issue98] Lost answer problem
> 
> Hi Rafa,
> 
> I think your are right.  The discarding rule seems to be a bug.
> What do you think, Alper?
> 
> Yoshihiro Ohba
> 
> 
> On Tue, Jul 13, 2004 at 12:21:48PM +0200, Rafael Marin Lopez wrote:
> > Hi Yoshihiro...
> >
> > Maybe I am missing something but sentence "There would not be any
> > discarding due to sequence numbers" I am not sure if it completely
true.
> > For example:
> >
> >
> > PaC PAA
> > <------------PBR(x,y)-----------
> >
> > -------------PBA(y+1,x)--X--->
> >
> > <-----------PBR(x+1,y)--------
> > (silently discarded by PaC: "x+1" is correct but "y" does not belong
to
> > [ y (tseq of the last acknowledged message) + 1, y+1(tseq of the
last
> > transmitted message)]
> >
> > <---------- PBR(x+2,y)--------
> >
> > same situation
> >
> > Am I wrong?
> >
> >
> > Yoshihiro Ohba wrote:
> >
> > >On Mon, Jul 12, 2004 at 04:49:20PM -0700, Alper Yegin wrote:
> > >
> > >
> > >>I'm trying to understand the issue...
> > >>
> > >>
> > >>
> > >>>From Yoshihiro Ohba:
> > >>>--------------------
> > >>>There might be some cases in which a PaC or a PAA might need to
send
> a
> > >>>duplicate answer to a retransmitted old request (as well as a
fresh
> > >>>answer to a new request if any) considering that an answer
message
> for
> > >>>an old request can be lost.  Without this, a PANA session may
stall
> in
> > >>>a way that the requester keeps retransmitting the old request
while
> > >>>the responder may keep discarding them with waiting for a new
request.
> > >>>
> > >>>
> > >>There would not be any discarding due to sequence numbers. I guess
the
> > >>only problem could be that the PaC has jumped to the next state in
the
> > >>state machine as soon as it responded to a message, and in that
state
> it
> > >>does not expect the same request it had already responded earlier.
Is
> > >>that the issue?
> > >>
> > >>
> > >
> > >Yes.
> > >
> > >Yoshihiro Ohba
> > >
> > >
> > >
> > >
> > >>Alper
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>>The cases are described below.
> > >>>
> > >>>- When a PaC sends a PANA-Start-Answer message in response to a
valid
> > >>>PANA-Start-Request message without a Cookie AVP, the answer
message
> > >>>can be lost.  The PANA-Start-Request would be retransmitted.  To
deal
> > >>>with the case, it might be better for the PaC to return a
duplicate
> > >>>PANA-Start-Answer message after the PaC has been sent the first
> > >>>PANA-Start-Answer message until the PaC receives a valid
> > >>>PANA-Auth-Request message.
> > >>>
> > >>>- When a PaC sends a PANA-FirstAuth-End-Answer message in
response to
> > >>>
> > >>>
> > >>a
> > >>
> > >>
> > >>>valid PANA-FirstAuth-End-Request message (remember that a
> > >>>PANA-FirstAuth-End exchange is used for delimiting the first and
> > >>>second EAP authentications), the answer message may be lost.  The
> > >>>PANA-FirstAuth-End-Request would be retransmitted (with updating
> > >>>transmission sequence number).  To deal with the case, it might
be
> > >>>better for the PaC to return a duplicate
PANA-FirstAuth-End-Answer
> > >>>message (with updating transmission and received sequence
numbers)
> > >>>after the PaC has been sent the first PANA-FirstAuth-End-Answer
> > >>>message until the PaC receives a valid PANA-Auth-Request message
for
> > >>>the second EAP authentication.
> > >>>
> > >>>- When a PaC sends a PANA-Bind-Answer message in response to a
valid
> > >>>PANA-Bind-Request message, the answer message can be lost.  As as
> > >>>result, the PAA will retransmit the PANA-Bind-Request (but with
using
> > >>>a different transmission sequence number).  To deal with the
case, it
> > >>>might be better for the PaC to return a duplicate
PANA-Bind-Answer
> > >>>message (but with using different transmission and received
sequence
> > >>>numbers) for a while after the first PANA-Bind-Request was
received.
> > >>>The same thing can also apply to a PANA-Address-Update-Answer
message
> > >>>that is sent by a PaC.
> > >>>
> > >>>- When a PaC or a PAA sends a PANA-Termination-Answer message in
> > >>>response to a valid PANA-Termination-Request message, the answer
> > >>>message can be lost.  As as result, the requester will retransmit
the
> > >>>request (but with using a different transmission sequence
number).
> To
> > >>>deal with the case, it might be better for the sender of the
answer
> to
> > >>>return a duplicate answer (with using different transmission and
> > >>>received sequence numbers) for a while after the first
> > >>>PANA-Termination-Request was received.  The same thing can also
apply
> > >>>to a PANA-Reauth-Answer message that is sent by a PaC or a PAA.
> > >>>
> > >>>Those could improve robustness of the PANA protocol against loss
of
> > >>>answer message.
> > >>>
> > >>>Comments?
> > >>>
> > >>>Yoshihiro Ohba
> > >>>
> > >>>----------
> > >>>category: Technical
> > >>>document: draft-ietf-pana-pana-xx.txt
> > >>>messages: 335
> > >>>nosy: dforsber
> > >>>priority: Must Fix
> > >>>status: Pending
> > >>>title: Lost answer problem
> > >>>__________________________________________________
> > >>>PANA Issues <pana_issues@danforsberg.info>
> > >>><http://danforsberg.info:8080/pana-issues/issue98>
> > >>>__________________________________________________
> > >>>
> > >>>
> > >
> > >_______________________________________________
> > >Pana mailing list
> > >Pana@ietf.org
> > >https://www1.ietf.org/mailman/listinfo/pana
> > >
> > >
> > >
> > >
> >
> >
> > --
> > ------------------------------------------------------
> > Rafael Marin Lopez
> > Faculty of Computer Science-University of Murcia
> > 30071 Murcia - Spain
> > Telf: +34968367645    e-mail: rafa@dif.um.es
> > ------------------------------------------------------
> >


----- End forwarded message -----

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 19:18:43 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18149
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 19:18:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlFK1-0002Zo-MV; Thu, 15 Jul 2004 19:07:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlFFQ-00013L-9S
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 19:02:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16983
	for <pana@ietf.org>; Thu, 15 Jul 2004 19:02:36 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlFFO-0001br-Da
	for pana@ietf.org; Thu, 15 Jul 2004 19:02:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlFCn-0000kK-00
	for pana@ietf.org; Thu, 15 Jul 2004 18:59:59 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BlF8D-0007DZ-00
	for pana@ietf.org; Thu, 15 Jul 2004 18:55:13 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6FMtCpD025433;
	Fri, 16 Jul 2004 07:55:12 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6FMtCP3011603;
	Fri, 16 Jul 2004 07:55:12 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	HAA11602 ; Fri, 16 Jul 2004 07:55:12 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA17906; Fri, 16 Jul 2004 07:55:11 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA23163;
	Fri, 16 Jul 2004 07:55:11 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6FMtBpl000586;
	Fri, 16 Jul 2004 07:55:11 +0900 (JST)
Received: from steelhead (iVPN01-102.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0X007NW0ZWCE@tsbpo1.po.toshiba.co.jp>; Fri,
	16 Jul 2004 07:55:10 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlF7A-0000ud-00; Thu, 15 Jul 2004 15:54:08 -0700
Date: Thu, 15 Jul 2004 18:54:07 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-based reauth clarification [Re: Mobility Handling in
	PANA]
In-reply-to: <028101c469e4$1fc3c480$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040715225407.GO893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org,
	'Giaretta Gerardo' <Gerardo.Giaretta@TILAB.COM>,
	'Julien Bournelle' <Julien.Bournelle@int-evry.fr>
User-Agent: Mutt/1.5.6+20040523i
References: <20040714195312.GS893@steelhead>
	<028101c469e4$1fc3c480$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Giaretta Gerardo'" <Gerardo.Giaretta@TILAB.COM>,
        "'Julien Bournelle'" <Julien.Bournelle@int-evry.fr>,
        "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Wed, Jul 14, 2004 at 01:49:55PM -0700, Alper Yegin wrote:
> OK, I'm fine with locking a PANA session to fixed NAP/ISP. If the PaC
> wants to hop around, it better terminate the current session and start a
> new one.
> 
> Maybe we could briefly capture this by saying:
> 
> Any subsequent EAP-based authentication MUST be performed with the
> same ISP and NAP that was selected during the initial authentication. 

This works for me.

Yoshihiro Ohba

> 
> Alper
> 
> 
> 
> 
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Wednesday, July 14, 2004 12:53 PM
> > To: Alper Yegin
> > Cc: 'Yoshihiro Ohba'; pana@ietf.org; 'Giaretta Gerardo'; 'Julien
> > Bournelle'
> > Subject: Re: [Pana] EAP-based reauth clarification [Re: Mobility
> Handling
> > in PANA]
> > 
> > On Tue, Jul 13, 2004 at 02:18:10PM -0700, Alper Yegin wrote:
> > > > Based on the discussion below.  I would suggest adding the
> following
> > > > sentences to section 4.4 of PANA speficication:
> > > >
> > > > "
> > > > When NAP and ISP separate authetnications were performed in the
> first
> > > > occurence of PANA authentication phase, the same NAP and ISP
> separate
> > > > authentications MUST also be performed in subsequent EAP-based
> > > > re-authentication occurances.  Otherwise, NAP and ISP separate
> > > > authentications MUST NOT be performed in subsequent EAP-based
> > > > re-authentication occurances.
> > > > "
> > >
> > > Can this be generalized to saying the NAP/ISP selection cannot
> change in
> > > a PANA session? I'm trying to understand what happens (breaks?) if
> the
> > > PaC changes its selection...
> > 
> > In the current specification, the PaC is not allowed to change its
> > selection because PSR-PSA exchange is not performed in EAP-based
> > re-authentication.  So I think your question is what happens if we
> > modify the specification to allow PSR-PSA exchange to change the
> > selection in EAP-based re-authentication.  I think that works, but
> > probably the PSR-PSA exchange should be integrity protected with a MAC
> > AVP if a PANA SA exists in order to avoid false re-authentication
> > trigger DoS attack.  But adding a MAC AVP in PSA might conflict with
> > the current PANA mobility optimization solution.
> > 
> > Yoshihiro Ohba
> > 
> > 
> > >
> > > Alper
> > >
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > On Mon, Jul 12, 2004 at 05:42:11PM +0200, Giaretta Gerardo wrote:
> > > > > Hi Yoshi,
> > > > >
> > > > > > > > I am not sure how EAP-based re-authentication can work
> after
> > > the
> > > > > > > > PaC has successfully established a new PANA session with
> nPAA
> > > > > > > > based on the mobility optimization operation, especially
> with
> > > NAP
> > > > > > > > and ISP separated authentications.  Since PSR-PSA exchange
> is
> > > > > > > > omitted in the case of EAP-based re-authentication, there
> is
> > > no
> > > > > > > > means to negotiate on NAP and ISP separate authentications
> > > between
> > > > >
> > > > > > > > the PaC and nPAA.  Do you have any thoughts on this?
> > > > > > > >
> > > > > > >
> > > > > > > I'm not sure I understand your point: is this a general
> > > > > > PANA issue or
> > > > > > > is it related to the operations described in
> > > > > > > draft-bournelle-pana-ctp-00.txt?
> > > > > >
> > > > > > It might be related to both.  I think that if NAP and ISP
> > > > > > separate authentications were made in the initial
> > > > > > authentication, then the same NAP and ISP separate
> > > > > > authentications should also be made in EAP-based
> > > > > > re-authentication (this is a PANA issue, i.e., this should be
> > > > > > described in the PANA specification.)  If the same thing
> > > > > > needs to be done in EAP-based re-authentication after handoff
> > > > > > (though I am not sure the same thing needs to be done in this
> > > > > > case), information on whether NAP and ISP separate
> > > > > > authentications were made in the previous network may need to
> > > > > > be included in PANA-CTD (this is an issue of
> > > > > > draft-bournelle-pana-ctp-00.txt).
> > > > > >
> > > > >
> > > > > I agree with you. The result of the usage of CTP, as the result
> of
> > > any
> > > > > fast authentication mechanism, must be the same as the one
> obtained
> > > > > performing the whole authentication procedure. This implies that
> > > nPAA
> > > > > should know if PaC performed double authentication and which ISP
> it
> > > > > chose. Therefore this information must be transferred in CTD
> > > message.
> > > > >
> > > > > However, I think that EAP re-authentication is not related to
> > > mobility
> > > > > handling. The usage of CTP allows to transfer the PANA context
> to
> > > the
> > > > > nPAA. After the PBR/PBA exchange the PaC is authenticated and
> the
> > > nPAA
> > > > > knows the residual authorization lifetime. Therefore
> > > > > EAP-reauthentication is not performed immediately after the
> handoff
> > > and
> > > > > it is accomplished as specified in PANA specs.
> > > > >
> > > > > Note that we have not defined yet how to inform both NAP and ISP
> AAA
> > > > > system of the new PaC's location. I think this is also an
> important
> > > > > issue.
> > > > >
> > > > >
> > > > > --Gerardo
> > > > >
> > > > >
> > > > >
> > > > > > Yoshihiro Ohba
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Gruppo Telecom Italia - Direzione e coordinamento di Telecom
> Italia
> > > > S.p.A.
> > > > >
> > > > >
> ====================================================================
> > > > > CONFIDENTIALITY NOTICE
> > > > > This message and its attachments are addressed solely to the
> persons
> > > > > above and may contain confidential information. If you have
> received
> > > > > the message in error, be informed that any use of the content
> hereof
> > > > > is prohibited. Please return it immediately to the sender and
> delete
> > > > > the message. Should you have any questions, please send an
> e_mail to
> > > > > MailAdmin@tilab.com. Thank you
> > > > >
> ====================================================================
> > > >
> > > > _______________________________________________
> > > > Pana mailing list
> > > > Pana@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pana
> > >
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 19:30:00 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18841
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 19:30:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlFdC-0008C1-6d; Thu, 15 Jul 2004 19:27:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlFZZ-0007GN-WE
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 19:23:30 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18570
	for <pana@ietf.org>; Thu, 15 Jul 2004 19:23:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlFZY-00018x-59
	for pana@ietf.org; Thu, 15 Jul 2004 19:23:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlFYb-0000q1-00
	for pana@ietf.org; Thu, 15 Jul 2004 19:22:31 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12) id 1BlFXf-0000DZ-00
	for pana@ietf.org; Thu, 15 Jul 2004 19:21:32 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0X00D01270UY@mailout1.samsung.com> for pana@ietf.org; Fri,
	16 Jul 2004 08:21:00 +0900 (KST)
Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0X00I1026ZCA@mailout1.samsung.com> for pana@ietf.org;
	Fri, 16 Jul 2004 08:21:00 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0X005Q526XJF@mmp2.samsung.com> for
	pana@ietf.org; Fri, 16 Jul 2004 08:20:59 +0900 (KST)
Date: Thu, 15 Jul 2004 16:21:02 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] New: [issue98] Lost answer problem
In-reply-to: <20040715215722.GK893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <01c001c46ac2$666ee5c0$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

OK, I understand.

I went back to your original proposed text. It is free of state
machine-like discussions (which is good, imo). Do you want to stick with
it, or are there any updates needed based on our discussion? 

If we take it as the baseline, here are my comments:

> 
> Here is a proposed solution for the lost answer problem.
> 
> ---------------------------------
> Insert the following section.
> 
> "
> Section 4.X  Retransmission of Duplicate Answers

Maybe "Responding to Duplicate Requests" is more representative as the
origin of duplication is on the Request side. 

> 
> Since PANA is designed over UDP, an answer as well as a request can be
> lost.  In order to improve robustness against possible loss of
> synchronization between a PaC and a PAA, the responder of a request
> MAY send a duplicate answer to a duplicate request for which already
> answered (as well as a fresh answer to a new request if any).  In

", the responder MAY send a duplicate answer to a request that it had
just answered."


> PANA, a duplicate PANA-Start-Request or PANA-Start-Answer message has
> the same contents as the original request or answer, respectively.  A
> duplicate request other than PANA-Start-Request has the same contents
> as the original request except for the transmission sequence number
> and a MAC AVP (if any).  Also, a duplicate answer other than
> PANA-Start-Answer has the same contents as the original answer except
> for the transmission and receiving sequence numbers and a MAC AVP (if
> any).  

I'm not sure how these details relate to the discussion. If the
objective is to determine when the two requests are duplicate, maybe we
could say:

"The only difference between two consecutive duplicate requests
are the sequence numbers and the content of MAC AVP (when present)." 

> Retransmission of a duplicate answer in response to a duplicate
> request occurs in the following ways.
> 
> o When a PaC receives a duplicate PANA-Start-Request message for which
> it has already answered, it MAY send a duplicate PANA-Start-Answer
> message until it receives a valid PANA-Auth-Request message.

Shouldn't this be a "SHOULD"? I think this is safer towards more
robustness.

> 
> o When a PaC receives a duplicate PANA-FirstAuth-End-Request message
> for which it has already answered, it MAY send a duplicate
> PANA-FirstAuth-End-Answer message until it receives a valid
> PANA-Auth-Request message for the second EAP authentication.

I'd say "SHOULD" again.
 
> o When a PaC receives a duplicate PANA-Bind-Request message for which
> it has already answered, it MAY send a duplicate PANA-Bind-Answer
> message until it receives some hint provided outside the PANA protocol
> (e.g., receipt of a secure association protocol message from an EP or
> receipt of data traffic) indicating that the PAA has received a
> PANA-Bind-Answer message.

SHOULD again.

> 
> o When a PaC or a PAA receives a duplicate PANA-Termination-Request
> message for which it has already answered, it MAY send a duplicate
> PANA-Termination-Answer message for a while before deleting the PANA
> session.  The period to send duplicate PANA-Termination-Answer
> messages may be a configurable parameter.
> "

I think we can use the guidelines in Section 7.

So, we can say:

o When a PaC or a PAA receives a duplicate PANA-Termination-Request
  message for which it has already answered, it MAY send a duplicate
  PANA-Termination-Answer message in accordance with the timers
  Described in Section 7.

Even if we leave this as MAY, things would work as the requester would
eventually timeout.

Alper


> 
> Regards,
> 
> Yoshihiro Ohba
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

> -----Original Message-----
> From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf
Of
> Yoshihiro Ohba
> Sent: Thursday, July 15, 2004 2:57 PM
> To: Alper Yegin
> Cc: 'Yoshihiro Ohba'; pana@ietf.org
> Subject: Re: [Pana] New: [issue98] Lost answer problem
> 
> Couple of examples in RFC 3748:
> 
> - On resending a Response in response to a duplicate Request
> 
> "
>       If a peer receives a valid duplicate Request for which it has
>       already sent a Response, it MUST resend its original Response
>       without reprocessing the Request.  Requests MUST be processed in
>       the order that they are received, and MUST be processed to their
>       completion before inspecting the next Request.
> "
> 
> - On Nak message rejection.
> 
> "
>    A peer MUST NOT send a Nak (legacy or expanded) in reply to a
Request
>    after an initial non-Nak Response has been sent.  Since spoofed EAP
>    Request packets may be sent by an attacker, an authenticator
>    receiving an unexpected Nak SHOULD discard it and log the event.
> "
> 
> - On EAP-Success/Failure message rejection:
> 
> "
>    Success and Failure packets MUST NOT be sent by an EAP
authenticator
>    if the specification of the given method does not explicitly permit
>    the method to finish at that point.  A peer EAP implementation
>    receiving a Success or Failure packet where sending one is not
>    explicitly permitted MUST silently discard it.  By default, an EAP
>    peer MUST silently discard a "canned" Success packet (a Success
>    packet sent immediately upon connection).  This ensures that a
rogue
>    authenticator will not be able to bypass mutual authentication by
>    sending a Success packet prior to conclusion of the EAP method
>    conversation.
> "
> 
> - On prohibition of mixing Requests with different types.
> 
> "
>    Once a peer has sent a Response of the same Type as the initial
>    Request, an authenticator MUST NOT send a Request of a different
Type
>    prior to completion of the final round of a given method (with the
>    exception of a Notification-Request) and MUST NOT send a Request
for
>    an additional method of any Type after completion of the initial
>    authentication method; a peer receiving such Requests MUST treat
them
>    as invalid, and silently discard them.  As a result, Identity
Requery
>    is not supported.
> "
> 
> Regards,
> 
> Yoshihiro Ohba
> 
> 
> 
> 
> On Thu, Jul 15, 2004 at 12:17:26PM -0700, Alper Yegin wrote:
> > > > These are related to the "states". That's why I think the
discussion
> > > > belongs to the state machine I-D. It can discuss definition of
> > states,
> > > > how the session moves from one state to another, and how
messages
> > are
> > > > processed in each state (ignored, rejected, causes state change,
> > etc.)
> > > > And all that pana specification can say is what it already says:
> > > >
> > > > 4.1.7 Message Validity Check
> > > >
> > > >    When a PANA message is received, the message is considered to
be
> > > >    invalid at least when one of the following conditions are not
> > met:
> > > >
> > > >    o  The message type is one of the expected types in the
current
> > > >       state.
> > > >
> > > > I think this is a more scalable and modular approach.
> > >
> > > I want to make sure the relationship between the PANA
specification
> > > I-D and the PANA state machine I-D.
> > >
> > > The suggested approach seems to indicate that the PANA state
machine
> > > I-D is a part of the "complete" set of specification.  (Otherwise,
> > > pana-pana draft needs to specify what messages types are expected
in
> > > the current state, doesn't it?)
> >
> > I went over your list of what is rejected (ignored?) in what state.
They
> > looked intuitive to me, I mean things we don't need to spell out.
Like
> > you cannot terminate a session before it starts, or you cannot
> > reauthenticate before the initial authentication is complete, etc.
> >
> > Maybe this is a subjective view. I'm trying to control the verbosity
> > level and document size without jeopardizing clarity.
> >
> > >
> > > Note that the suggested approach is different from the approach
taken
> > > by RFC 3748 (EAP) and EAP state machine I-D.  RFC 3748 specifies
> > > everything including which message should be accepted or rejected
in
> > > certain conditions and EAP state machine I-D is just another
> > > representation of RFC 3748.
> >
> > Can you give an example from the EAP spec on that? I'd like to
better
> > understand how we are going to tackle this if we want to include
text in
> > the PANA spec. An example text on PANA (for one message only) would
be
> > useful too. I'd like to make sure we don't unintentionally end up
> > sliding state machine discussions into the base spec.
> >
> > Alper
> >
> >
> >
> > >
> > > Yoshihiro Ohba
> > >
> > > >
> > > > Alper
> > > >
> > > >
> > > >
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > >
> > > > > >
> > > > > > Alper
> > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Pana mailing list
> > > > > > Pana@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/pana
> > > >
> >
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 19:50:35 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19761
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 19:50:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlFxR-0005P0-U1; Thu, 15 Jul 2004 19:48:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlFut-0004b7-Gv
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 19:45:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19522
	for <pana@ietf.org>; Thu, 15 Jul 2004 19:45:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlFur-0000IJ-DD
	for pana@ietf.org; Thu, 15 Jul 2004 19:45:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlFtu-0007km-00
	for pana@ietf.org; Thu, 15 Jul 2004 19:44:31 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12) id 1BlFt5-00077o-00
	for pana@ietf.org; Thu, 15 Jul 2004 19:43:39 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0X003IC37WMG@mailout3.samsung.com> for pana@ietf.org; Fri,
	16 Jul 2004 08:43:08 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0X00K1233QNY@mailout3.samsung.com> for pana@ietf.org;
	Fri, 16 Jul 2004 08:40:39 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0X005LZ33OIZ@mmp2.samsung.com> for
	pana@ietf.org; Fri, 16 Jul 2004 08:40:38 +0900 (KST)
Date: Thu, 15 Jul 2004 16:40:42 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] issue85 (initial text)
In-reply-to: <20040715222050.GL893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <01c101c46ac5$254cfac0$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> > > In case where only one interface identifier is used per interface
(I
> > > believe this is the typical case), if the interface identifier
> > > changes, doesn't it mean that the link-local address also changes?
> >
> > I'm not sure if there is any requirement to have the same interface
> > identifier across all IPv6 addresses on the same physical interface.
> 
> I don't think there is such a requirement.  But should we mandate the
> use of multiple interface identifiers to support RFC 3041 with PANA?
> If so, I think we should explicitly mention this in the framework
> document.

This mandate is not arising from PANA, but this is an unstated
assumption in RFC3041. The RFC is specifically about changing
global-scope (and now-deprecated site-locals), nothing to do with the
link-locals. Hence the use of different interface identifiers is
inherent to RFC3041. I don't think we should do anything on that in PANA
documents.

Alper




_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 19:51:44 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19836
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 19:51:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlFxS-0005P5-5Y; Thu, 15 Jul 2004 19:48:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlFuu-0004bA-K5
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 19:45:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19527
	for <pana@ietf.org>; Thu, 15 Jul 2004 19:45:28 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlFus-0000IT-Ot
	for pana@ietf.org; Thu, 15 Jul 2004 19:45:30 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlFtv-0007kw-00
	for pana@ietf.org; Thu, 15 Jul 2004 19:44:32 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BlFt5-0007QX-00
	for pana@ietf.org; Thu, 15 Jul 2004 19:43:39 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6FNhUpD029646;
	Fri, 16 Jul 2004 08:43:30 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6FNhTwl011738;
	Fri, 16 Jul 2004 08:43:29 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	JAA11736 ; Fri, 16 Jul 2004 08:43:29 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA27921; Fri, 16 Jul 2004 08:43:29 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA16655;
	Fri, 16 Jul 2004 08:43:24 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6FNhNpl028828;
	Fri, 16 Jul 2004 08:43:23 +0900 (JST)
Received: from steelhead (iVPN01-124.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0X00COB38946@tsbpo1.po.toshiba.co.jp>; Fri,
	16 Jul 2004 08:43:23 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlFrl-00017D-00; Thu, 15 Jul 2004 16:42:17 -0700
Date: Thu, 15 Jul 2004 19:42:17 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 103: "PANA session" needs more clarification
In-reply-to: <01aa01c46abb$46a98580$9b1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040715234217.GQ893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <01aa01c46abb$46a98580$9b1d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Thu, Jul 15, 2004 at 03:30:03PM -0700, Alper Yegin wrote:
> Here is the proposed text update:
> 
> Change:
> 
> PANA Session:
> 
>       PANA session is defined as the exchange of messages between the
>       PANA Client (PaC) and the PANA Authentication Agent (PAA) to
>       authenticate a user (PaC) for network access.  If the
>       authentication is unsuccessful, the session is terminated.  The
>       session is considered as active until there is a disconnect
>       indication by the PaC or the PAA terminates it.  A distinct PANA
>       session is associated with a pair of device identifiers of PaC and
>       PAA.  For example, if the PaC has two interfaces connected to the
>       same IP link with different IP addresses and IP address is used as
>       a device identifier, a distinct PANA session will be created per
>       interface if both interfaces addresses need to be authorized for
>       network access.
> 
>    Session Identifier:
> 
>       This identifier is used to uniquely identify a PANA session on the
>       PAA and PaC.  It is included in PANA messages to bind the message
>       to a specific PANA session.
> 
> To:
> 
>    PANA Session:
> 
>       A PANA session begins with an initial handshake between the PANA
>       Client (PaC) and the PANA Authentication Agent (PAA), and
>       terminates due to an authentication failure, a timeout, or an
>       explicit termination message. A fixed session identifier is 
>       maintained throughout a session. A session cannot be shared
>       across multiple physical network interfaces, but a physical
>       network interface can have multiple sessions at a time. 

According to this definition, it is possible for a PaC with a single
physical interface to have multiple sessions (with different client
identities) to the same PAA.  I don't think we should allow it, because
the following text of the pana-requirement draft explicitly prohibits
it:

"
4.1.1  Authentication of Client

   PANA MUST enable authentication of PaCs for network access.  A PaC's
   identity can be authenticated by verifying the credentials (e.g.,
   identifier, authenticator) supplied by one of the users of the device
   or the device itself.  PANA MUST only grant network access service to
   the device identified by the DI, rather than granting separate access
   to multiple simultaneous users of the device.  ...
"

I think the following sentence of the original PANA session definition 
should be in the definition:

"
A distinct PANA
session is associated with a pair of device identifiers of PaC and
PAA.  
"

> 
> 
>    Session Identifier:
> 
>       This identifier is used to uniquely identify a PANA session on the
>       PAA and PaC. It includes an identifier of the PAA, therefore it 
>       cannot be shared across multiple PAAs. It is included in PANA
> messages 
>       to bind the message to a specific PANA session. This bidirectional
> 
>       identifier is allocated by the PAA during the initial handshake 
>       and freed when the session terminates. 

Session-Id AVP is not contained in PSR.  So, I think "during the
initial handshake" is not accurate.


Yoshihiro Ohba

> 
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 20:40:42 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22461
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 20:40:41 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlGfK-0008Bo-6Y; Thu, 15 Jul 2004 20:33:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlGdL-0007pv-VQ
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 20:31:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21999
	for <pana@ietf.org>; Thu, 15 Jul 2004 20:31:25 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlGdK-0007m7-4N
	for pana@ietf.org; Thu, 15 Jul 2004 20:31:26 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlGcK-0007RJ-00
	for pana@ietf.org; Thu, 15 Jul 2004 20:30:25 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12) id 1BlGbF-0006o0-00
	for pana@ietf.org; Thu, 15 Jul 2004 20:29:18 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0X00H395BZ1I@mailout1.samsung.com> for pana@ietf.org; Fri,
	16 Jul 2004 09:28:47 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0X007JU57IV2@mailout1.samsung.com> for pana@ietf.org;
	Fri, 16 Jul 2004 09:26:06 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0X0026I57F0C@mmp1.samsung.com> for
	pana@ietf.org; Fri, 16 Jul 2004 09:26:06 +0900 (KST)
Date: Thu, 15 Jul 2004 17:26:08 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 103: "PANA session" needs more clarification
In-reply-to: <20040715234217.GQ893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <01c301c46acb$7ecf32b0$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> According to this definition, it is possible for a PaC with a single
> physical interface to have multiple sessions (with different client
> identities) to the same PAA.  I don't think we should allow it,
because
> the following text of the pana-requirement draft explicitly prohibits
> it:
> 
> "
> 4.1.1  Authentication of Client
> 
>    PANA MUST enable authentication of PaCs for network access.  A
PaC's
>    identity can be authenticated by verifying the credentials (e.g.,
>    identifier, authenticator) supplied by one of the users of the
device
>    or the device itself.  PANA MUST only grant network access service
to
>    the device identified by the DI, rather than granting separate
access
>    to multiple simultaneous users of the device.  ...
> "
> 
> I think the following sentence of the original PANA session definition
> should be in the definition:
> 
> "
> A distinct PANA
> session is associated with a pair of device identifiers of PaC and
> PAA.
> "

OK.

   PANA Session:

      A PANA session begins with the initial handshake between the PANA
      Client (PaC) and the PANA Authentication Agent (PAA), and
      terminates by an authentication failure, a timeout, or an
      explicit termination message. A fixed session identifier is 
      maintained throughout a session. A session cannot be shared
      across multiple physical network interfaces. A distinct PANA
      session is associated with the device identifiers of PaC and
      PAA.

> 
> >
> >
> >    Session Identifier:
> >
> >       This identifier is used to uniquely identify a PANA session on
the
> >       PAA and PaC. It includes an identifier of the PAA, therefore
it
> >       cannot be shared across multiple PAAs. It is included in PANA
> > messages
> >       to bind the message to a specific PANA session. This
bidirectional
> >
> >       identifier is allocated by the PAA during the initial
handshake
> >       and freed when the session terminates.
> 
> Session-Id AVP is not contained in PSR.  So, I think "during the
> initial handshake" is not accurate.

Right.


   Session Identifier:

      This identifier is used to uniquely identify a PANA session on the
      PAA and PaC. It includes an identifier of the PAA, therefore it 
      cannot be shared across multiple PAAs. It is included in PANA
messages 
      to bind the message to a specific PANA session. This bidirectional

      identifier is allocated by the PAA following the initial handshake

      and freed when the session terminates.

Alper



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 15 21:13:44 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24578
	for <pana-archive@lists.ietf.org>; Thu, 15 Jul 2004 21:13:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlHAf-0001gj-RO; Thu, 15 Jul 2004 21:05:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlH5i-0000df-7J
	for pana@megatron.ietf.org; Thu, 15 Jul 2004 21:00:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23725
	for <pana@ietf.org>; Thu, 15 Jul 2004 21:00:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlH5g-0001pB-5G
	for pana@ietf.org; Thu, 15 Jul 2004 21:00:44 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlH4q-0001Tz-00
	for pana@ietf.org; Thu, 15 Jul 2004 20:59:53 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12) id 1BlH4E-000179-00
	for pana@ietf.org; Thu, 15 Jul 2004 20:59:14 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0X00I1L6PVAE@mailout1.samsung.com> for pana@ietf.org; Fri,
	16 Jul 2004 09:58:43 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0X009BC6ISAR@mailout1.samsung.com> for pana@ietf.org;
	Fri, 16 Jul 2004 09:54:29 +0900 (KST)
Received: from Alperyegin ([105.144.29.155])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0X007F66IQO7@mmp1.samsung.com> for
	pana@ietf.org; Fri, 16 Jul 2004 09:54:28 +0900 (KST)
Date: Thu, 15 Jul 2004 17:54:30 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: Issue 107 (RE: [Pana] Bug in sequence number management)
In-reply-to: <20040715224713.GN893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <01c501c46acf$7522b580$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

I created a record in the issue tracker: Issue 107.

This seems to solve the problem, and I couldn't think of any issues with
the proposed change.

Alper


> -----Original Message-----
> From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf
Of
> Yoshihiro Ohba
> Sent: Thursday, July 15, 2004 3:47 PM
> To: pana@ietf.org
> Subject: [Pana] Bug in sequence number management
> 
> 
> In section 4.1.4 of draft-ietf-pana-pana-04, change:
> 
> "
>    o  When a message is received, it is considered valid in terms of
>       sequence numbers if and only if (i) its tseq is greater than the
>       tseq of the last accepted message and (ii) its rseq falls in the
>       range between the tseq of the last acknowledged message + 1 and
>       the tseq of the last transmitted message.
> "
> 
> to:
> 
> "
>    o  When a message is received, it is considered valid in terms of
>       sequence numbers if and only if (i) its tseq is greater than the
>       tseq of the last accepted message and (ii) its rseq falls in the
>       range between the tseq of the last acknowledged message and
>       the tseq of the last transmitted message.
> "
> 
> Yoshihiro Ohba
> 
> 
> ----- Forwarded message from Alper Yegin <alper.yegin@samsung.com>
-----
> 
> From: Alper Yegin <alper.yegin@samsung.com>
> Subject: RE: [Pana] New: [issue98] Lost answer problem
> To: 'Yoshihiro Ohba' <yohba@tari.toshiba.com>,
> 	'Rafael Marin Lopez' <rafa@dif.um.es>
> Importance: Normal
> X-VirusChecked: Checked
> X-Env-Sender: alper.yegin@samsung.com
> X-Msg-Ref: server-13.tower-76.messagelabs.com!1089756330!2585408
> X-StarScan-Version: 5.2.10; banners=-,-,-
> X-Originating-IP: [203.254.224.33]
> X-SpamReason: No, hits=0.0 required=7.0 tests=CYNIC_B,
> 
> Hmmm, looks like it.
> 
> Does increasing the range by 1 fix the problem (without breaking
> anything else)?
> 
> Like:
> 
> [tseq of the last acknowledged message, tseq of the last
> transmitted message]
> 
> Alper
> 
> 
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Tuesday, July 13, 2004 2:49 PM
> > To: Rafael Marin Lopez; Alper Yegin
> > Cc: Yoshihiro Ohba
> > Subject: Re: [Pana] New: [issue98] Lost answer problem
> >
> > Hi Rafa,
> >
> > I think your are right.  The discarding rule seems to be a bug.
> > What do you think, Alper?
> >
> > Yoshihiro Ohba
> >
> >
> > On Tue, Jul 13, 2004 at 12:21:48PM +0200, Rafael Marin Lopez wrote:
> > > Hi Yoshihiro...
> > >
> > > Maybe I am missing something but sentence "There would not be any
> > > discarding due to sequence numbers" I am not sure if it completely
> true.
> > > For example:
> > >
> > >
> > > PaC PAA
> > > <------------PBR(x,y)-----------
> > >
> > > -------------PBA(y+1,x)--X--->
> > >
> > > <-----------PBR(x+1,y)--------
> > > (silently discarded by PaC: "x+1" is correct but "y" does not
belong
> to
> > > [ y (tseq of the last acknowledged message) + 1, y+1(tseq of the
> last
> > > transmitted message)]
> > >
> > > <---------- PBR(x+2,y)--------
> > >
> > > same situation
> > >
> > > Am I wrong?
> > >
> > >
> > > Yoshihiro Ohba wrote:
> > >
> > > >On Mon, Jul 12, 2004 at 04:49:20PM -0700, Alper Yegin wrote:
> > > >
> > > >
> > > >>I'm trying to understand the issue...
> > > >>
> > > >>
> > > >>
> > > >>>From Yoshihiro Ohba:
> > > >>>--------------------
> > > >>>There might be some cases in which a PaC or a PAA might need to
> send
> > a
> > > >>>duplicate answer to a retransmitted old request (as well as a
> fresh
> > > >>>answer to a new request if any) considering that an answer
> message
> > for
> > > >>>an old request can be lost.  Without this, a PANA session may
> stall
> > in
> > > >>>a way that the requester keeps retransmitting the old request
> while
> > > >>>the responder may keep discarding them with waiting for a new
> request.
> > > >>>
> > > >>>
> > > >>There would not be any discarding due to sequence numbers. I
guess
> the
> > > >>only problem could be that the PaC has jumped to the next state
in
> the
> > > >>state machine as soon as it responded to a message, and in that
> state
> > it
> > > >>does not expect the same request it had already responded
earlier.
> Is
> > > >>that the issue?
> > > >>
> > > >>
> > > >
> > > >Yes.
> > > >
> > > >Yoshihiro Ohba
> > > >
> > > >
> > > >
> > > >
> > > >>Alper
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>>The cases are described below.
> > > >>>
> > > >>>- When a PaC sends a PANA-Start-Answer message in response to a
> valid
> > > >>>PANA-Start-Request message without a Cookie AVP, the answer
> message
> > > >>>can be lost.  The PANA-Start-Request would be retransmitted.
To
> deal
> > > >>>with the case, it might be better for the PaC to return a
> duplicate
> > > >>>PANA-Start-Answer message after the PaC has been sent the first
> > > >>>PANA-Start-Answer message until the PaC receives a valid
> > > >>>PANA-Auth-Request message.
> > > >>>
> > > >>>- When a PaC sends a PANA-FirstAuth-End-Answer message in
> response to
> > > >>>
> > > >>>
> > > >>a
> > > >>
> > > >>
> > > >>>valid PANA-FirstAuth-End-Request message (remember that a
> > > >>>PANA-FirstAuth-End exchange is used for delimiting the first
and
> > > >>>second EAP authentications), the answer message may be lost.
The
> > > >>>PANA-FirstAuth-End-Request would be retransmitted (with
updating
> > > >>>transmission sequence number).  To deal with the case, it might
> be
> > > >>>better for the PaC to return a duplicate
> PANA-FirstAuth-End-Answer
> > > >>>message (with updating transmission and received sequence
> numbers)
> > > >>>after the PaC has been sent the first PANA-FirstAuth-End-Answer
> > > >>>message until the PaC receives a valid PANA-Auth-Request
message
> for
> > > >>>the second EAP authentication.
> > > >>>
> > > >>>- When a PaC sends a PANA-Bind-Answer message in response to a
> valid
> > > >>>PANA-Bind-Request message, the answer message can be lost.  As
as
> > > >>>result, the PAA will retransmit the PANA-Bind-Request (but with
> using
> > > >>>a different transmission sequence number).  To deal with the
> case, it
> > > >>>might be better for the PaC to return a duplicate
> PANA-Bind-Answer
> > > >>>message (but with using different transmission and received
> sequence
> > > >>>numbers) for a while after the first PANA-Bind-Request was
> received.
> > > >>>The same thing can also apply to a PANA-Address-Update-Answer
> message
> > > >>>that is sent by a PaC.
> > > >>>
> > > >>>- When a PaC or a PAA sends a PANA-Termination-Answer message
in
> > > >>>response to a valid PANA-Termination-Request message, the
answer
> > > >>>message can be lost.  As as result, the requester will
retransmit
> the
> > > >>>request (but with using a different transmission sequence
> number).
> > To
> > > >>>deal with the case, it might be better for the sender of the
> answer
> > to
> > > >>>return a duplicate answer (with using different transmission
and
> > > >>>received sequence numbers) for a while after the first
> > > >>>PANA-Termination-Request was received.  The same thing can also
> apply
> > > >>>to a PANA-Reauth-Answer message that is sent by a PaC or a PAA.
> > > >>>
> > > >>>Those could improve robustness of the PANA protocol against
loss
> of
> > > >>>answer message.
> > > >>>
> > > >>>Comments?
> > > >>>
> > > >>>Yoshihiro Ohba
> > > >>>
> > > >>>----------
> > > >>>category: Technical
> > > >>>document: draft-ietf-pana-pana-xx.txt
> > > >>>messages: 335
> > > >>>nosy: dforsber
> > > >>>priority: Must Fix
> > > >>>status: Pending
> > > >>>title: Lost answer problem
> > > >>>__________________________________________________
> > > >>>PANA Issues <pana_issues@danforsberg.info>
> > > >>><http://danforsberg.info:8080/pana-issues/issue98>
> > > >>>__________________________________________________
> > > >>>
> > > >>>
> > > >
> > > >_______________________________________________
> > > >Pana mailing list
> > > >Pana@ietf.org
> > > >https://www1.ietf.org/mailman/listinfo/pana
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > ------------------------------------------------------
> > > Rafael Marin Lopez
> > > Faculty of Computer Science-University of Murcia
> > > 30071 Murcia - Spain
> > > Telf: +34968367645    e-mail: rafa@dif.um.es
> > > ------------------------------------------------------
> > >
> 
> 
> ----- End forwarded message -----
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 06:49:29 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21708
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 06:49:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlQBG-00008A-QW; Fri, 16 Jul 2004 06:43:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlQ9D-0008Es-JK
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 06:41:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21190
	for <pana@ietf.org>; Fri, 16 Jul 2004 06:40:54 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlQ98-0000Yn-0R
	for pana@ietf.org; Fri, 16 Jul 2004 06:40:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlQ87-0000En-00
	for pana@ietf.org; Fri, 16 Jul 2004 06:39:52 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BlQ76-0007Vh-00
	for pana@ietf.org; Fri, 16 Jul 2004 06:38:48 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6G1WFpD027605;
	Fri, 16 Jul 2004 10:32:15 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6G1WFE3006889;
	Fri, 16 Jul 2004 10:32:15 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	LAA06887 ; Fri, 16 Jul 2004 10:32:15 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id KAA15210; Fri, 16 Jul 2004 10:32:14 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id KAA24052;
	Fri, 16 Jul 2004 10:32:13 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6G1WCpl020926;
	Fri, 16 Jul 2004 10:32:12 +0900 (JST)
Received: from steelhead (iVPN01-203.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0X005KX89L0K@tsbpo1.po.toshiba.co.jp>; Fri,
	16 Jul 2004 10:32:11 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlHZE-0001ZV-00; Thu, 15 Jul 2004 18:31:16 -0700
Date: Thu, 15 Jul 2004 21:31:16 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New: [issue98] Lost answer problem
In-reply-to: <01c001c46ac2$666ee5c0$9b1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040716013116.GV893@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040715215722.GK893@steelhead>
	<01c001c46ac2$666ee5c0$9b1d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

In addition to the original proposed text, I's suggest adding the list
of unexpected requests.  Here is the entire proposed text:

[1] Change section 4.1.7:

"
o  The message type is one of the expected types in the current
   state.
"

to:

o  The message type is one of the expected types in the current
   state.

   Specifically the following messages are unexpected and invalid:

   o In discovery and initial handshake phase:

     - PANA-Termination-Request and PANA-Reauth-Request.

     - PANA-Bind-Request.

     - PANA-Update-Request.

   o In authentication phase:

     - PANA-Termination-Request and PANA-Reauth-Request.

     - PANA-Update-Request.

     - PANA-Start-Request after a PaC receives the first valid
       PANA-Auth-Request.

   o After successful PANA authentication:

     - PANA-Start-Request as well as a non-duplicate PANA-Bind-Request
       (see section 4.X for definition of duplicate requests)

     - PANA-PAA-Discover without a Session-Id AVP.

   o In termination phase:

     - All requests but PANA-Termination-Request.
"

(I guess this section should move back, because it contains details.)


[2] Add the following section:

"   
Section 4.X  Responding to Duplicate Requests

Since PANA is designed over UDP, an answer as well as a request can be
lost.  In order to provide robustness against possible loss of
synchronization between a PaC and a PAA, the responder MAY send a
duplicate answer to a request that it had just answered.  The only
difference between two consecutive duplicate requests are the sequence
numbers and the content of MAC AVP (when present).

o When a PaC receives a duplicate PANA-Start-Request message for which
  it has already answered, it SHOULD send a duplicate
  PANA-Start-Answer message until it receives a valid
  PANA-Auth-Request message.

o When a PaC receives a duplicate PANA-FirstAuth-End-Request message
  for which it has already answered, it SHOULD send a duplicate
  PANA-FirstAuth-End-Answer message until it receives a valid
  PANA-Auth-Request message for the second EAP authentication.

o When a PaC receives a duplicate PANA-Bind-Request message for which
  it has already answered, it SHOULD send a duplicate PANA-Bind-Answer
  message until it receives some hint provided outside the PANA
  protocol (e.g., receipt of a secure association protocol message
  from an EP or receipt of data traffic) indicating that the PAA has
  received a PANA-Bind-Answer message.

o When a PaC or a PAA receives a duplicate PANA-Termination-Request
  message for which it has already answered, it MAY send a duplicate
  PANA-Termination-Answer message in accordance with the timers
  described in Section 7.
"

Yoshihiro Ohba


On Thu, Jul 15, 2004 at 04:21:02PM -0700, Alper Yegin wrote:
> OK, I understand.
> 
> I went back to your original proposed text. It is free of state
> machine-like discussions (which is good, imo). Do you want to stick with
> it, or are there any updates needed based on our discussion? 
> 
> If we take it as the baseline, here are my comments:
> 
> > 
> > Here is a proposed solution for the lost answer problem.
> > 
> > ---------------------------------
> > Insert the following section.
> > 
> > "
> > Section 4.X  Retransmission of Duplicate Answers
> 
> Maybe "Responding to Duplicate Requests" is more representative as the
> origin of duplication is on the Request side. 
> 
> > 
> > Since PANA is designed over UDP, an answer as well as a request can be
> > lost.  In order to improve robustness against possible loss of
> > synchronization between a PaC and a PAA, the responder of a request
> > MAY send a duplicate answer to a duplicate request for which already
> > answered (as well as a fresh answer to a new request if any).  In
> 
> ", the responder MAY send a duplicate answer to a request that it had
> just answered."
> 
> 
> > PANA, a duplicate PANA-Start-Request or PANA-Start-Answer message has
> > the same contents as the original request or answer, respectively.  A
> > duplicate request other than PANA-Start-Request has the same contents
> > as the original request except for the transmission sequence number
> > and a MAC AVP (if any).  Also, a duplicate answer other than
> > PANA-Start-Answer has the same contents as the original answer except
> > for the transmission and receiving sequence numbers and a MAC AVP (if
> > any).  
> 
> I'm not sure how these details relate to the discussion. If the
> objective is to determine when the two requests are duplicate, maybe we
> could say:
> 
> "The only difference between two consecutive duplicate requests
> are the sequence numbers and the content of MAC AVP (when present)." 
> 
> > Retransmission of a duplicate answer in response to a duplicate
> > request occurs in the following ways.
> > 
> > o When a PaC receives a duplicate PANA-Start-Request message for which
> > it has already answered, it MAY send a duplicate PANA-Start-Answer
> > message until it receives a valid PANA-Auth-Request message.
> 
> Shouldn't this be a "SHOULD"? I think this is safer towards more
> robustness.
> 
> > 
> > o When a PaC receives a duplicate PANA-FirstAuth-End-Request message
> > for which it has already answered, it MAY send a duplicate
> > PANA-FirstAuth-End-Answer message until it receives a valid
> > PANA-Auth-Request message for the second EAP authentication.
> 
> I'd say "SHOULD" again.
>  
> > o When a PaC receives a duplicate PANA-Bind-Request message for which
> > it has already answered, it MAY send a duplicate PANA-Bind-Answer
> > message until it receives some hint provided outside the PANA protocol
> > (e.g., receipt of a secure association protocol message from an EP or
> > receipt of data traffic) indicating that the PAA has received a
> > PANA-Bind-Answer message.
> 
> SHOULD again.
> 
> > 
> > o When a PaC or a PAA receives a duplicate PANA-Termination-Request
> > message for which it has already answered, it MAY send a duplicate
> > PANA-Termination-Answer message for a while before deleting the PANA
> > session.  The period to send duplicate PANA-Termination-Answer
> > messages may be a configurable parameter.
> > "
> 
> I think we can use the guidelines in Section 7.
> 
> So, we can say:
> 
> o When a PaC or a PAA receives a duplicate PANA-Termination-Request
>   message for which it has already answered, it MAY send a duplicate
>   PANA-Termination-Answer message in accordance with the timers
>   Described in Section 7.
> 
> Even if we leave this as MAY, things would work as the requester would
> eventually timeout.
> 
> Alper
> 
> 
> > 
> > Regards,
> > 
> > Yoshihiro Ohba
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 
> > -----Original Message-----
> > From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf
> Of
> > Yoshihiro Ohba
> > Sent: Thursday, July 15, 2004 2:57 PM
> > To: Alper Yegin
> > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > Subject: Re: [Pana] New: [issue98] Lost answer problem
> > 
> > Couple of examples in RFC 3748:
> > 
> > - On resending a Response in response to a duplicate Request
> > 
> > "
> >       If a peer receives a valid duplicate Request for which it has
> >       already sent a Response, it MUST resend its original Response
> >       without reprocessing the Request.  Requests MUST be processed in
> >       the order that they are received, and MUST be processed to their
> >       completion before inspecting the next Request.
> > "
> > 
> > - On Nak message rejection.
> > 
> > "
> >    A peer MUST NOT send a Nak (legacy or expanded) in reply to a
> Request
> >    after an initial non-Nak Response has been sent.  Since spoofed EAP
> >    Request packets may be sent by an attacker, an authenticator
> >    receiving an unexpected Nak SHOULD discard it and log the event.
> > "
> > 
> > - On EAP-Success/Failure message rejection:
> > 
> > "
> >    Success and Failure packets MUST NOT be sent by an EAP
> authenticator
> >    if the specification of the given method does not explicitly permit
> >    the method to finish at that point.  A peer EAP implementation
> >    receiving a Success or Failure packet where sending one is not
> >    explicitly permitted MUST silently discard it.  By default, an EAP
> >    peer MUST silently discard a "canned" Success packet (a Success
> >    packet sent immediately upon connection).  This ensures that a
> rogue
> >    authenticator will not be able to bypass mutual authentication by
> >    sending a Success packet prior to conclusion of the EAP method
> >    conversation.
> > "
> > 
> > - On prohibition of mixing Requests with different types.
> > 
> > "
> >    Once a peer has sent a Response of the same Type as the initial
> >    Request, an authenticator MUST NOT send a Request of a different
> Type
> >    prior to completion of the final round of a given method (with the
> >    exception of a Notification-Request) and MUST NOT send a Request
> for
> >    an additional method of any Type after completion of the initial
> >    authentication method; a peer receiving such Requests MUST treat
> them
> >    as invalid, and silently discard them.  As a result, Identity
> Requery
> >    is not supported.
> > "
> > 
> > Regards,
> > 
> > Yoshihiro Ohba
> > 
> > 
> > 
> > 
> > On Thu, Jul 15, 2004 at 12:17:26PM -0700, Alper Yegin wrote:
> > > > > These are related to the "states". That's why I think the
> discussion
> > > > > belongs to the state machine I-D. It can discuss definition of
> > > states,
> > > > > how the session moves from one state to another, and how
> messages
> > > are
> > > > > processed in each state (ignored, rejected, causes state change,
> > > etc.)
> > > > > And all that pana specification can say is what it already says:
> > > > >
> > > > > 4.1.7 Message Validity Check
> > > > >
> > > > >    When a PANA message is received, the message is considered to
> be
> > > > >    invalid at least when one of the following conditions are not
> > > met:
> > > > >
> > > > >    o  The message type is one of the expected types in the
> current
> > > > >       state.
> > > > >
> > > > > I think this is a more scalable and modular approach.
> > > >
> > > > I want to make sure the relationship between the PANA
> specification
> > > > I-D and the PANA state machine I-D.
> > > >
> > > > The suggested approach seems to indicate that the PANA state
> machine
> > > > I-D is a part of the "complete" set of specification.  (Otherwise,
> > > > pana-pana draft needs to specify what messages types are expected
> in
> > > > the current state, doesn't it?)
> > >
> > > I went over your list of what is rejected (ignored?) in what state.
> They
> > > looked intuitive to me, I mean things we don't need to spell out.
> Like
> > > you cannot terminate a session before it starts, or you cannot
> > > reauthenticate before the initial authentication is complete, etc.
> > >
> > > Maybe this is a subjective view. I'm trying to control the verbosity
> > > level and document size without jeopardizing clarity.
> > >
> > > >
> > > > Note that the suggested approach is different from the approach
> taken
> > > > by RFC 3748 (EAP) and EAP state machine I-D.  RFC 3748 specifies
> > > > everything including which message should be accepted or rejected
> in
> > > > certain conditions and EAP state machine I-D is just another
> > > > representation of RFC 3748.
> > >
> > > Can you give an example from the EAP spec on that? I'd like to
> better
> > > understand how we are going to tackle this if we want to include
> text in
> > > the PANA spec. An example text on PANA (for one message only) would
> be
> > > useful too. I'd like to make sure we don't unintentionally end up
> > > sliding state machine discussions into the base spec.
> > >
> > > Alper
> > >
> > >
> > >
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > > >
> > > > > Alper
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > Yoshihiro Ohba
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Alper
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Pana mailing list
> > > > > > > Pana@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/pana
> > > > >
> > >
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 11:53:51 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10933
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 11:53:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlUyK-0001In-9Q; Fri, 16 Jul 2004 11:50:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlUom-0008JU-Fs
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 11:40:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09970
	for <pana@ietf.org>; Fri, 16 Jul 2004 11:40:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlUoi-0004d8-RE
	for pana@ietf.org; Fri, 16 Jul 2004 11:40:08 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlUni-0004IF-00
	for pana@ietf.org; Fri, 16 Jul 2004 11:39:07 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BlUmp-0003y1-00
	for pana@ietf.org; Fri, 16 Jul 2004 11:38:11 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6GFcBlr008048;
	Sat, 17 Jul 2004 00:38:11 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6GFcAjH008872;
	Sat, 17 Jul 2004 00:38:10 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	AAA08871 ; Sat, 17 Jul 2004 00:38:10 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA10726; Sat, 17 Jul 2004 00:38:10 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA13948;
	Sat, 17 Jul 2004 00:38:09 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6GFc9pl009874;
	Sat, 17 Jul 2004 00:38:09 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0Y00HD8BFIL8@tsbpo1.po.toshiba.co.jp>; Sat,
	17 Jul 2004 00:38:08 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlUmT-0000Z0-00; Fri, 16 Jul 2004 08:37:49 -0700
Date: Fri, 16 Jul 2004 11:37:48 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (initial text)
In-reply-to: <01c101c46ac5$254cfac0$9b1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040716153748.GE1033@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040715222050.GL893@steelhead>
	<01c101c46ac5$254cfac0$9b1d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Alper,

I double checked this with KAME implementation and you are right.  I
agree that the device identifier update is probably not needed for
usual cases.

Yoshihiro Ohba


On Thu, Jul 15, 2004 at 04:40:42PM -0700, Alper Yegin wrote:
> > > > In case where only one interface identifier is used per interface
> (I
> > > > believe this is the typical case), if the interface identifier
> > > > changes, doesn't it mean that the link-local address also changes?
> > >
> > > I'm not sure if there is any requirement to have the same interface
> > > identifier across all IPv6 addresses on the same physical interface.
> > 
> > I don't think there is such a requirement.  But should we mandate the
> > use of multiple interface identifiers to support RFC 3041 with PANA?
> > If so, I think we should explicitly mention this in the framework
> > document.
> 
> This mandate is not arising from PANA, but this is an unstated
> assumption in RFC3041. The RFC is specifically about changing
> global-scope (and now-deprecated site-locals), nothing to do with the
> link-locals. Hence the use of different interface identifiers is
> inherent to RFC3041. I don't think we should do anything on that in PANA
> documents.
> 
> Alper
> 
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 13:49:31 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19018
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 13:49:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlWkK-0003ms-OL; Fri, 16 Jul 2004 13:43:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlWYI-0001Cx-CA
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 13:31:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17603
	for <pana@ietf.org>; Fri, 16 Jul 2004 13:31:15 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlWYE-000381-Qu
	for pana@ietf.org; Fri, 16 Jul 2004 13:31:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlWXH-0002ol-00
	for pana@ietf.org; Fri, 16 Jul 2004 13:30:16 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BlWWU-0002VY-00
	for pana@ietf.org; Fri, 16 Jul 2004 13:29:26 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6GHTQlr007840;
	Sat, 17 Jul 2004 02:29:26 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6GHTQo4013460;
	Sat, 17 Jul 2004 02:29:26 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	CAA13458 ; Sat, 17 Jul 2004 02:29:26 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA08363; Sat, 17 Jul 2004 02:29:25 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA12306;
	Sat, 17 Jul 2004 02:29:24 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6GHTOpl021307;
	Sat, 17 Jul 2004 02:29:24 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0Y00JSNGKXOU@tsbpo1.po.toshiba.co.jp>; Sat,
	17 Jul 2004 02:29:23 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlWVJ-00011J-00; Fri, 16 Jul 2004 10:28:13 -0700
Date: Fri, 16 Jul 2004 13:28:13 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] NEW: [issue100] PSR and PSA sequence number clarification
In-reply-to: <00c301c4685e$fb5ce440$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040716172813.GF1033@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040705170231.GE17360@steelhead>
	<00c301c4685e$fb5ce440$6401a8c0@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Mon, Jul 12, 2004 at 03:24:19PM -0700, Alper Yegin wrote:
> 
> I'm trying to see if we can solve this problem without creating
> exceptions to the sequencing scheme.....
> 
> As I understand, relying on the ISNs has an issue when PaC and PAA
> retransmit the messages and any one of the last x sequences (n through
> n-x+1) might have been accepted by the PAA as the ISN. Right?
> 
> Can we solve this problem by carrying Nonce values in PSR and PSA, and
> using them with the PANA_MAC_KEY computation instead of ISNs?
> 
> Alper
> 
> 

This is proposed text.

-----------------------------------------------
[1] Change the following text in section 4.1.4:

"
   The two sequence number fields have the same length of 32 bits and
   appear in PANA header.  tseq starts from initial sequence number
   (ISN) and is monotonically increased by 1. The serial number
   arithmetic defined in [RFC1982] is used for sequence number
   operation. The ISNs are exchanged between PaC and PAA during the
   discovery and initial handshake phase (see Section 4.2). The rules
   that govern the sequence numbers in other phases are described as
   follows.
"

"
   The two sequence number fields have the same length of 32 bits and
   appear in PANA header.  tseq starts from initial sequence number
   (ISN) and is monotonically increased by 1.  This rule applies to
   all PANA messages but PANA-PAA-Discover.  The serial number
   arithmetic defined in [RFC1982] is used for sequence number
   operation.  The ISNs are exchanged between PaC and PAA during the
   discovery and initial handshake phase (see Section 4.2).  The rules
   that govern the sequence numbers in other phases are described as
   follows.
"

[2]  In section 4.1.5, change:

"
      *  PANA SA attributes:

         +  AAA-Key

         +  AAA-Key Identifier

         +  PANA_MAC_Key
"

to:

"
      *  PANA SA attributes:

         +  Nonce generated by PaC (PaC_nonce)

         +  Nonce generated by PAA (PAA_nonce)

         +  AAA-Key

         +  AAA-Key Identifier

         +  PANA_MAC_KEY
"

[3] Change the following algorithm in section 4.1.5:

"
      PANA_MAC_KEY = The first N bits of
                     HMAC_SHA1(AAA-Key, ISN_pac | ISN_paa | Session-ID)
"

to:

"
      PANA_MAC_KEY = The first N bits of
                     HMAC_SHA1(AAA-Key, PaC_nonce | PAA_nonce | Session-ID)
"


[4]  Add the following text in section 4.2:

"
A Nonce AVP MUST be included in PANA-Start-Request and
PANA-Start-Answer messages.
"

(Note: Nonce AVP could be an optional AVP if a PANA SA is not
established, but I think it is simpler and securer to just make it
mandate.)


[5]  Change the following text in section 4.9:

"
   Upon changing its point of attachment, a PaC that wants to quickly
   resume its ongoing PANA session without running EAP MAY send its
   unexpired PANA session identifier in its PANA-Start-Answer message.
   Along with the Session-Id AVP, MAC and Nonce AVPs MUST be included in
   this message.  Nonce AVP carries a randomly chosen value (PaC_Nonce),
   and MAC AVP is computed by using the PANA_MAC_Key shared between the
   PaC and its previous PAA that has an unexpired PANA session with the
   PaC.  This action signals PaC's desire to perform the mobility
   optimization.  In the absence of Session-Id AVP in this message, PANA
   session takes its usual course (i.e., EAP-based authentication is
   performed).
"

"
   Upon changing its point of attachment, a PaC that wants to quickly
   resume its ongoing PANA session without running EAP MAY send its
   unexpired PANA session identifier in its PANA-Start-Answer message.
   Along with the Session-Id AVP, a MAC AVP MUST be included in this
   message.  The MAC AVP is computed by using the PANA_MAC_KEY shared
   between the PaC and its previous PAA that has an unexpired PANA
   session with the PaC.  This action signals PaC's desire to perform
   the mobility optimization.  In the absence of Session-Id AVP in
   this message, PANA session takes its usual course (i.e., EAP-based
   authentication is performed).
"

[6]  Change the following text in section 4.9:

"
   The current PAA and PaC compute the new AAA-Key by using the nonce
   values and the AAA-Key-int.  PAA_Nonce is the randomly chosen value
   that MUST be carried in a Nonce AVP in the PANA-Bind-Request message.

      AAA-Key-new = The first N bits of
                    HMAC-SHA1(AAA-Key-int, PaC_nonce | PAA_nonce)

"

to:

"
   The current PAA and PaC compute the new AAA-Key by using the nonce
   values and the AAA-Key-int.  

      AAA-Key-new = The first N bits of
                    HMAC-SHA1(AAA-Key-int, PaC_nonce | PAA_nonce)
"

[7] In section 6.4.3, add Nonce AVP to PANA-Start-Request
as a mandatory AVP.

[8] In sections 6.4.4, change Nonce AVP of PANA-Start-Answer from
optional AVP to mandatory AVP.

[9] In section 6.4.7, remove Nonce AVP from PANA-Bind-Request.

[10] In section 6.6., update AVP occurence table to be consistent with
changes [7], [8] and [9].



Yoshihiro Ohba

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 14:20:56 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21260
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 14:20:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlXEc-0000Yf-CA; Fri, 16 Jul 2004 14:15:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlX5E-00070r-Lt
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 14:05:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20134
	for <pana@ietf.org>; Fri, 16 Jul 2004 14:05:19 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlX5B-00073i-LS
	for pana@ietf.org; Fri, 16 Jul 2004 14:05:17 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlX4T-0006hm-00
	for pana@ietf.org; Fri, 16 Jul 2004 14:04:34 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1BlX3V-00063s-00
	for pana@ietf.org; Fri, 16 Jul 2004 14:03:33 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0Y00F01I4ZXE@mailout2.samsung.com> for pana@ietf.org; Sat,
	17 Jul 2004 03:03:00 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0Y00F5RI4Z58@mailout2.samsung.com> for pana@ietf.org;
	Sat, 17 Jul 2004 03:02:59 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0Y009FII4XUG@mmp1.samsung.com> for
	pana@ietf.org; Sat, 17 Jul 2004 03:02:59 +0900 (KST)
Date: Fri, 16 Jul 2004 11:03:03 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] New: [issue98] Lost answer problem
In-reply-to: <20040716013116.GV893@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <01ff01c46b5f$2480c320$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Looks good to me.

Alper


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Thursday, July 15, 2004 6:31 PM
> To: Alper Yegin
> Cc: 'Yoshihiro Ohba'; pana@ietf.org
> Subject: Re: [Pana] New: [issue98] Lost answer problem
> 
> In addition to the original proposed text, I's suggest adding the list
> of unexpected requests.  Here is the entire proposed text:
> 
> [1] Change section 4.1.7:
> 
> "
> o  The message type is one of the expected types in the current
>    state.
> "
> 
> to:
> 
> o  The message type is one of the expected types in the current
>    state.
> 
>    Specifically the following messages are unexpected and invalid:
> 
>    o In discovery and initial handshake phase:
> 
>      - PANA-Termination-Request and PANA-Reauth-Request.
> 
>      - PANA-Bind-Request.
> 
>      - PANA-Update-Request.
> 
>    o In authentication phase:
> 
>      - PANA-Termination-Request and PANA-Reauth-Request.
> 
>      - PANA-Update-Request.
> 
>      - PANA-Start-Request after a PaC receives the first valid
>        PANA-Auth-Request.
> 
>    o After successful PANA authentication:
> 
>      - PANA-Start-Request as well as a non-duplicate PANA-Bind-Request
>        (see section 4.X for definition of duplicate requests)
> 
>      - PANA-PAA-Discover without a Session-Id AVP.
> 
>    o In termination phase:
> 
>      - All requests but PANA-Termination-Request.
> "
> 
> (I guess this section should move back, because it contains details.)
> 
> 
> [2] Add the following section:
> 
> "
> Section 4.X  Responding to Duplicate Requests
> 
> Since PANA is designed over UDP, an answer as well as a request can be
> lost.  In order to provide robustness against possible loss of
> synchronization between a PaC and a PAA, the responder MAY send a
> duplicate answer to a request that it had just answered.  The only
> difference between two consecutive duplicate requests are the sequence
> numbers and the content of MAC AVP (when present).
> 
> o When a PaC receives a duplicate PANA-Start-Request message for which
>   it has already answered, it SHOULD send a duplicate
>   PANA-Start-Answer message until it receives a valid
>   PANA-Auth-Request message.
> 
> o When a PaC receives a duplicate PANA-FirstAuth-End-Request message
>   for which it has already answered, it SHOULD send a duplicate
>   PANA-FirstAuth-End-Answer message until it receives a valid
>   PANA-Auth-Request message for the second EAP authentication.
> 
> o When a PaC receives a duplicate PANA-Bind-Request message for which
>   it has already answered, it SHOULD send a duplicate PANA-Bind-Answer
>   message until it receives some hint provided outside the PANA
>   protocol (e.g., receipt of a secure association protocol message
>   from an EP or receipt of data traffic) indicating that the PAA has
>   received a PANA-Bind-Answer message.
> 
> o When a PaC or a PAA receives a duplicate PANA-Termination-Request
>   message for which it has already answered, it MAY send a duplicate
>   PANA-Termination-Answer message in accordance with the timers
>   described in Section 7.
> "
> 
> Yoshihiro Ohba
> 
> 
> On Thu, Jul 15, 2004 at 04:21:02PM -0700, Alper Yegin wrote:
> > OK, I understand.
> >
> > I went back to your original proposed text. It is free of state
> > machine-like discussions (which is good, imo). Do you want to stick
with
> > it, or are there any updates needed based on our discussion?
> >
> > If we take it as the baseline, here are my comments:
> >
> > >
> > > Here is a proposed solution for the lost answer problem.
> > >
> > > ---------------------------------
> > > Insert the following section.
> > >
> > > "
> > > Section 4.X  Retransmission of Duplicate Answers
> >
> > Maybe "Responding to Duplicate Requests" is more representative as
the
> > origin of duplication is on the Request side.
> >
> > >
> > > Since PANA is designed over UDP, an answer as well as a request
can be
> > > lost.  In order to improve robustness against possible loss of
> > > synchronization between a PaC and a PAA, the responder of a
request
> > > MAY send a duplicate answer to a duplicate request for which
already
> > > answered (as well as a fresh answer to a new request if any).  In
> >
> > ", the responder MAY send a duplicate answer to a request that it
had
> > just answered."
> >
> >
> > > PANA, a duplicate PANA-Start-Request or PANA-Start-Answer message
has
> > > the same contents as the original request or answer, respectively.
A
> > > duplicate request other than PANA-Start-Request has the same
contents
> > > as the original request except for the transmission sequence
number
> > > and a MAC AVP (if any).  Also, a duplicate answer other than
> > > PANA-Start-Answer has the same contents as the original answer
except
> > > for the transmission and receiving sequence numbers and a MAC AVP
(if
> > > any).
> >
> > I'm not sure how these details relate to the discussion. If the
> > objective is to determine when the two requests are duplicate, maybe
we
> > could say:
> >
> > "The only difference between two consecutive duplicate requests
> > are the sequence numbers and the content of MAC AVP (when present)."
> >
> > > Retransmission of a duplicate answer in response to a duplicate
> > > request occurs in the following ways.
> > >
> > > o When a PaC receives a duplicate PANA-Start-Request message for
which
> > > it has already answered, it MAY send a duplicate PANA-Start-Answer
> > > message until it receives a valid PANA-Auth-Request message.
> >
> > Shouldn't this be a "SHOULD"? I think this is safer towards more
> > robustness.
> >
> > >
> > > o When a PaC receives a duplicate PANA-FirstAuth-End-Request
message
> > > for which it has already answered, it MAY send a duplicate
> > > PANA-FirstAuth-End-Answer message until it receives a valid
> > > PANA-Auth-Request message for the second EAP authentication.
> >
> > I'd say "SHOULD" again.
> >
> > > o When a PaC receives a duplicate PANA-Bind-Request message for
which
> > > it has already answered, it MAY send a duplicate PANA-Bind-Answer
> > > message until it receives some hint provided outside the PANA
protocol
> > > (e.g., receipt of a secure association protocol message from an EP
or
> > > receipt of data traffic) indicating that the PAA has received a
> > > PANA-Bind-Answer message.
> >
> > SHOULD again.
> >
> > >
> > > o When a PaC or a PAA receives a duplicate
PANA-Termination-Request
> > > message for which it has already answered, it MAY send a duplicate
> > > PANA-Termination-Answer message for a while before deleting the
PANA
> > > session.  The period to send duplicate PANA-Termination-Answer
> > > messages may be a configurable parameter.
> > > "
> >
> > I think we can use the guidelines in Section 7.
> >
> > So, we can say:
> >
> > o When a PaC or a PAA receives a duplicate PANA-Termination-Request
> >   message for which it has already answered, it MAY send a duplicate
> >   PANA-Termination-Answer message in accordance with the timers
> >   Described in Section 7.
> >
> > Even if we leave this as MAY, things would work as the requester
would
> > eventually timeout.
> >
> > Alper
> >
> >
> > >
> > > Regards,
> > >
> > > Yoshihiro Ohba
> > >
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> >
> > > -----Original Message-----
> > > From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On
Behalf
> > Of
> > > Yoshihiro Ohba
> > > Sent: Thursday, July 15, 2004 2:57 PM
> > > To: Alper Yegin
> > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > Subject: Re: [Pana] New: [issue98] Lost answer problem
> > >
> > > Couple of examples in RFC 3748:
> > >
> > > - On resending a Response in response to a duplicate Request
> > >
> > > "
> > >       If a peer receives a valid duplicate Request for which it
has
> > >       already sent a Response, it MUST resend its original
Response
> > >       without reprocessing the Request.  Requests MUST be
processed in
> > >       the order that they are received, and MUST be processed to
their
> > >       completion before inspecting the next Request.
> > > "
> > >
> > > - On Nak message rejection.
> > >
> > > "
> > >    A peer MUST NOT send a Nak (legacy or expanded) in reply to a
> > Request
> > >    after an initial non-Nak Response has been sent.  Since spoofed
EAP
> > >    Request packets may be sent by an attacker, an authenticator
> > >    receiving an unexpected Nak SHOULD discard it and log the
event.
> > > "
> > >
> > > - On EAP-Success/Failure message rejection:
> > >
> > > "
> > >    Success and Failure packets MUST NOT be sent by an EAP
> > authenticator
> > >    if the specification of the given method does not explicitly
permit
> > >    the method to finish at that point.  A peer EAP implementation
> > >    receiving a Success or Failure packet where sending one is not
> > >    explicitly permitted MUST silently discard it.  By default, an
EAP
> > >    peer MUST silently discard a "canned" Success packet (a Success
> > >    packet sent immediately upon connection).  This ensures that a
> > rogue
> > >    authenticator will not be able to bypass mutual authentication
by
> > >    sending a Success packet prior to conclusion of the EAP method
> > >    conversation.
> > > "
> > >
> > > - On prohibition of mixing Requests with different types.
> > >
> > > "
> > >    Once a peer has sent a Response of the same Type as the initial
> > >    Request, an authenticator MUST NOT send a Request of a
different
> > Type
> > >    prior to completion of the final round of a given method (with
the
> > >    exception of a Notification-Request) and MUST NOT send a
Request
> > for
> > >    an additional method of any Type after completion of the
initial
> > >    authentication method; a peer receiving such Requests MUST
treat
> > them
> > >    as invalid, and silently discard them.  As a result, Identity
> > Requery
> > >    is not supported.
> > > "
> > >
> > > Regards,
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > >
> > >
> > > On Thu, Jul 15, 2004 at 12:17:26PM -0700, Alper Yegin wrote:
> > > > > > These are related to the "states". That's why I think the
> > discussion
> > > > > > belongs to the state machine I-D. It can discuss definition
of
> > > > states,
> > > > > > how the session moves from one state to another, and how
> > messages
> > > > are
> > > > > > processed in each state (ignored, rejected, causes state
change,
> > > > etc.)
> > > > > > And all that pana specification can say is what it already
says:
> > > > > >
> > > > > > 4.1.7 Message Validity Check
> > > > > >
> > > > > >    When a PANA message is received, the message is
considered to
> > be
> > > > > >    invalid at least when one of the following conditions are
not
> > > > met:
> > > > > >
> > > > > >    o  The message type is one of the expected types in the
> > current
> > > > > >       state.
> > > > > >
> > > > > > I think this is a more scalable and modular approach.
> > > > >
> > > > > I want to make sure the relationship between the PANA
> > specification
> > > > > I-D and the PANA state machine I-D.
> > > > >
> > > > > The suggested approach seems to indicate that the PANA state
> > machine
> > > > > I-D is a part of the "complete" set of specification.
(Otherwise,
> > > > > pana-pana draft needs to specify what messages types are
expected
> > in
> > > > > the current state, doesn't it?)
> > > >
> > > > I went over your list of what is rejected (ignored?) in what
state.
> > They
> > > > looked intuitive to me, I mean things we don't need to spell
out.
> > Like
> > > > you cannot terminate a session before it starts, or you cannot
> > > > reauthenticate before the initial authentication is complete,
etc.
> > > >
> > > > Maybe this is a subjective view. I'm trying to control the
verbosity
> > > > level and document size without jeopardizing clarity.
> > > >
> > > > >
> > > > > Note that the suggested approach is different from the
approach
> > taken
> > > > > by RFC 3748 (EAP) and EAP state machine I-D.  RFC 3748
specifies
> > > > > everything including which message should be accepted or
rejected
> > in
> > > > > certain conditions and EAP state machine I-D is just another
> > > > > representation of RFC 3748.
> > > >
> > > > Can you give an example from the EAP spec on that? I'd like to
> > better
> > > > understand how we are going to tackle this if we want to include
> > text in
> > > > the PANA spec. An example text on PANA (for one message only)
would
> > be
> > > > useful too. I'd like to make sure we don't unintentionally end
up
> > > > sliding state machine discussions into the base spec.
> > > >
> > > > Alper
> > > >
> > > >
> > > >
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > > >
> > > > > > Alper
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Yoshihiro Ohba
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > Alper
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > Pana mailing list
> > > > > > > > Pana@ietf.org
> > > > > > > > https://www1.ietf.org/mailman/listinfo/pana
> > > > > >
> > > >
> > >
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> >


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 14:34:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22431
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 14:34:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlXSA-0002jH-Uk; Fri, 16 Jul 2004 14:29:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlXG5-0000p2-0J
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 14:16:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20954
	for <pana@ietf.org>; Fri, 16 Jul 2004 14:16:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlXG0-0003DN-W2
	for pana@ietf.org; Fri, 16 Jul 2004 14:16:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlXEq-0002rm-00
	for pana@ietf.org; Fri, 16 Jul 2004 14:15:16 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12) id 1BlXEG-0002Ok-00
	for pana@ietf.org; Fri, 16 Jul 2004 14:14:40 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0Y00B08INNYO@mailout3.samsung.com> for pana@ietf.org; Sat,
	17 Jul 2004 03:14:11 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0Y00C1CINMB5@mailout3.samsung.com> for pana@ietf.org;
	Sat, 17 Jul 2004 03:14:10 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0Y00CYGINKB0@mmp1.samsung.com> for
	pana@ietf.org; Sat, 17 Jul 2004 03:14:10 +0900 (KST)
Date: Fri, 16 Jul 2004 11:14:14 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] NEW: [issue100] PSR and PSA sequence number clarification
In-reply-to: <20040716172813.GF1033@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <020001c46b60$b48ae350$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


Did you keep ISN_* in the PANA session attributes? We don't seem to need
them anymore, so we can remove them.


> [4]  Add the following text in section 4.2:
> 
> "
> A Nonce AVP MUST be included in PANA-Start-Request and
> PANA-Start-Answer messages.
> "

I agree.

Alper



> 
> (Note: Nonce AVP could be an optional AVP if a PANA SA is not
> established, but I think it is simpler and securer to just make it
> mandate.)
> 
> 
> [5]  Change the following text in section 4.9:
> 
> "
>    Upon changing its point of attachment, a PaC that wants to quickly
>    resume its ongoing PANA session without running EAP MAY send its
>    unexpired PANA session identifier in its PANA-Start-Answer message.
>    Along with the Session-Id AVP, MAC and Nonce AVPs MUST be included
in
>    this message.  Nonce AVP carries a randomly chosen value
(PaC_Nonce),
>    and MAC AVP is computed by using the PANA_MAC_Key shared between
the
>    PaC and its previous PAA that has an unexpired PANA session with
the
>    PaC.  This action signals PaC's desire to perform the mobility
>    optimization.  In the absence of Session-Id AVP in this message,
PANA
>    session takes its usual course (i.e., EAP-based authentication is
>    performed).
> "
> 
> "
>    Upon changing its point of attachment, a PaC that wants to quickly
>    resume its ongoing PANA session without running EAP MAY send its
>    unexpired PANA session identifier in its PANA-Start-Answer message.
>    Along with the Session-Id AVP, a MAC AVP MUST be included in this
>    message.  The MAC AVP is computed by using the PANA_MAC_KEY shared
>    between the PaC and its previous PAA that has an unexpired PANA
>    session with the PaC.  This action signals PaC's desire to perform
>    the mobility optimization.  In the absence of Session-Id AVP in
>    this message, PANA session takes its usual course (i.e., EAP-based
>    authentication is performed).
> "
> 
> [6]  Change the following text in section 4.9:
> 
> "
>    The current PAA and PaC compute the new AAA-Key by using the nonce
>    values and the AAA-Key-int.  PAA_Nonce is the randomly chosen value
>    that MUST be carried in a Nonce AVP in the PANA-Bind-Request
message.
> 
>       AAA-Key-new = The first N bits of
>                     HMAC-SHA1(AAA-Key-int, PaC_nonce | PAA_nonce)
> 
> "
> 
> to:
> 
> "
>    The current PAA and PaC compute the new AAA-Key by using the nonce
>    values and the AAA-Key-int.
> 
>       AAA-Key-new = The first N bits of
>                     HMAC-SHA1(AAA-Key-int, PaC_nonce | PAA_nonce)
> "
> 
> [7] In section 6.4.3, add Nonce AVP to PANA-Start-Request
> as a mandatory AVP.
> 
> [8] In sections 6.4.4, change Nonce AVP of PANA-Start-Answer from
> optional AVP to mandatory AVP.
> 
> [9] In section 6.4.7, remove Nonce AVP from PANA-Bind-Request.
> 
> [10] In section 6.6., update AVP occurence table to be consistent with
> changes [7], [8] and [9].
> 
> 
> 
> Yoshihiro Ohba


_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 15:04:20 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24589
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 15:04:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlXrm-0006ko-0M; Fri, 16 Jul 2004 14:55:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlXmh-0005xx-Ff
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 14:50:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23601
	for <pana@ietf.org>; Fri, 16 Jul 2004 14:50:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlXmd-0007Id-NX
	for pana@ietf.org; Fri, 16 Jul 2004 14:50:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlXlf-0006ys-00
	for pana@ietf.org; Fri, 16 Jul 2004 14:49:12 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BlXkb-0006Rr-00
	for pana@ietf.org; Fri, 16 Jul 2004 14:48:05 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6GIm5lr026110;
	Sat, 17 Jul 2004 03:48:05 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6GIm5Dj002306;
	Sat, 17 Jul 2004 03:48:05 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	DAA02305 ; Sat, 17 Jul 2004 03:48:05 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA00389; Sat, 17 Jul 2004 03:48:04 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA16251;
	Sat, 17 Jul 2004 03:48:04 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6GIm4pl015892;
	Sat, 17 Jul 2004 03:48:04 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0Y00MN8K81ZZ@tsbpo1.po.toshiba.co.jp>; Sat,
	17 Jul 2004 03:48:03 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlXjq-0001M3-00; Fri, 16 Jul 2004 11:47:18 -0700
Date: Fri, 16 Jul 2004 14:47:18 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] NEW: [issue100] PSR and PSA sequence number clarification
In-reply-to: <020001c46b60$b48ae350$9b1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040716184718.GH1033@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040716172813.GF1033@steelhead>
	<020001c46b60$b48ae350$9b1d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Fri, Jul 16, 2004 at 11:14:14AM -0700, Alper Yegin wrote:
> 
> Did you keep ISN_* in the PANA session attributes? We don't seem to need
> them anymore, so we can remove them.

OK, I will remove them.

Yoshihiro Ohba


> 
> 
> > [4]  Add the following text in section 4.2:
> > 
> > "
> > A Nonce AVP MUST be included in PANA-Start-Request and
> > PANA-Start-Answer messages.
> > "
> 
> I agree.
> 
> Alper
> 
> 
> 
> > 
> > (Note: Nonce AVP could be an optional AVP if a PANA SA is not
> > established, but I think it is simpler and securer to just make it
> > mandate.)
> > 
> > 
> > [5]  Change the following text in section 4.9:
> > 
> > "
> >    Upon changing its point of attachment, a PaC that wants to quickly
> >    resume its ongoing PANA session without running EAP MAY send its
> >    unexpired PANA session identifier in its PANA-Start-Answer message.
> >    Along with the Session-Id AVP, MAC and Nonce AVPs MUST be included
> in
> >    this message.  Nonce AVP carries a randomly chosen value
> (PaC_Nonce),
> >    and MAC AVP is computed by using the PANA_MAC_Key shared between
> the
> >    PaC and its previous PAA that has an unexpired PANA session with
> the
> >    PaC.  This action signals PaC's desire to perform the mobility
> >    optimization.  In the absence of Session-Id AVP in this message,
> PANA
> >    session takes its usual course (i.e., EAP-based authentication is
> >    performed).
> > "
> > 
> > "
> >    Upon changing its point of attachment, a PaC that wants to quickly
> >    resume its ongoing PANA session without running EAP MAY send its
> >    unexpired PANA session identifier in its PANA-Start-Answer message.
> >    Along with the Session-Id AVP, a MAC AVP MUST be included in this
> >    message.  The MAC AVP is computed by using the PANA_MAC_KEY shared
> >    between the PaC and its previous PAA that has an unexpired PANA
> >    session with the PaC.  This action signals PaC's desire to perform
> >    the mobility optimization.  In the absence of Session-Id AVP in
> >    this message, PANA session takes its usual course (i.e., EAP-based
> >    authentication is performed).
> > "
> > 
> > [6]  Change the following text in section 4.9:
> > 
> > "
> >    The current PAA and PaC compute the new AAA-Key by using the nonce
> >    values and the AAA-Key-int.  PAA_Nonce is the randomly chosen value
> >    that MUST be carried in a Nonce AVP in the PANA-Bind-Request
> message.
> > 
> >       AAA-Key-new = The first N bits of
> >                     HMAC-SHA1(AAA-Key-int, PaC_nonce | PAA_nonce)
> > 
> > "
> > 
> > to:
> > 
> > "
> >    The current PAA and PaC compute the new AAA-Key by using the nonce
> >    values and the AAA-Key-int.
> > 
> >       AAA-Key-new = The first N bits of
> >                     HMAC-SHA1(AAA-Key-int, PaC_nonce | PAA_nonce)
> > "
> > 
> > [7] In section 6.4.3, add Nonce AVP to PANA-Start-Request
> > as a mandatory AVP.
> > 
> > [8] In sections 6.4.4, change Nonce AVP of PANA-Start-Answer from
> > optional AVP to mandatory AVP.
> > 
> > [9] In section 6.4.7, remove Nonce AVP from PANA-Bind-Request.
> > 
> > [10] In section 6.6., update AVP occurence table to be consistent with
> > changes [7], [8] and [9].
> > 
> > 
> > 
> > Yoshihiro Ohba
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 15:32:12 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27297
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 15:32:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlYNc-00051r-FS; Fri, 16 Jul 2004 15:28:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlYEm-0002f4-A2
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 15:19:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26440
	for <pana@ietf.org>; Fri, 16 Jul 2004 15:19:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlYEj-0001PE-39
	for pana@ietf.org; Fri, 16 Jul 2004 15:19:13 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlYDl-00014v-00
	for pana@ietf.org; Fri, 16 Jul 2004 15:18:13 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BlYCn-0000f1-00
	for pana@ietf.org; Fri, 16 Jul 2004 15:17:13 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6GJHBlr002810;
	Sat, 17 Jul 2004 04:17:11 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6GJHB16008707;
	Sat, 17 Jul 2004 04:17:11 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	EAA08706 ; Sat, 17 Jul 2004 04:17:10 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA05445; Sat, 17 Jul 2004 04:17:10 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA27877;
	Sat, 17 Jul 2004 04:17:09 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6GJH9pl025024;
	Sat, 17 Jul 2004 04:17:09 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0Y00MWTLKIZZ@tsbpo1.po.toshiba.co.jp>; Sat,
	17 Jul 2004 04:17:08 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlYBn-0001V0-00; Fri, 16 Jul 2004 12:16:11 -0700
Date: Fri, 16 Jul 2004 15:16:10 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 103: "PANA session" needs more clarification
In-reply-to: <01c301c46acb$7ecf32b0$9b1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040716191610.GJ1033@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040715234217.GQ893@steelhead>
	<01c301c46acb$7ecf32b0$9b1d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

The proposed text looks fine.

Yoshihiro Ohba


On Thu, Jul 15, 2004 at 05:26:08PM -0700, Alper Yegin wrote:
> > According to this definition, it is possible for a PaC with a single
> > physical interface to have multiple sessions (with different client
> > identities) to the same PAA.  I don't think we should allow it,
> because
> > the following text of the pana-requirement draft explicitly prohibits
> > it:
> > 
> > "
> > 4.1.1  Authentication of Client
> > 
> >    PANA MUST enable authentication of PaCs for network access.  A
> PaC's
> >    identity can be authenticated by verifying the credentials (e.g.,
> >    identifier, authenticator) supplied by one of the users of the
> device
> >    or the device itself.  PANA MUST only grant network access service
> to
> >    the device identified by the DI, rather than granting separate
> access
> >    to multiple simultaneous users of the device.  ...
> > "
> > 
> > I think the following sentence of the original PANA session definition
> > should be in the definition:
> > 
> > "
> > A distinct PANA
> > session is associated with a pair of device identifiers of PaC and
> > PAA.
> > "
> 
> OK.
> 
>    PANA Session:
> 
>       A PANA session begins with the initial handshake between the PANA
>       Client (PaC) and the PANA Authentication Agent (PAA), and
>       terminates by an authentication failure, a timeout, or an
>       explicit termination message. A fixed session identifier is 
>       maintained throughout a session. A session cannot be shared
>       across multiple physical network interfaces. A distinct PANA
>       session is associated with the device identifiers of PaC and
>       PAA.
> 
> > 
> > >
> > >
> > >    Session Identifier:
> > >
> > >       This identifier is used to uniquely identify a PANA session on
> the
> > >       PAA and PaC. It includes an identifier of the PAA, therefore
> it
> > >       cannot be shared across multiple PAAs. It is included in PANA
> > > messages
> > >       to bind the message to a specific PANA session. This
> bidirectional
> > >
> > >       identifier is allocated by the PAA during the initial
> handshake
> > >       and freed when the session terminates.
> > 
> > Session-Id AVP is not contained in PSR.  So, I think "during the
> > initial handshake" is not accurate.
> 
> Right.
> 
> 
>    Session Identifier:
> 
>       This identifier is used to uniquely identify a PANA session on the
>       PAA and PaC. It includes an identifier of the PAA, therefore it 
>       cannot be shared across multiple PAAs. It is included in PANA
> messages 
>       to bind the message to a specific PANA session. This bidirectional
> 
>       identifier is allocated by the PAA following the initial handshake
> 
>       and freed when the session terminates.
> 
> Alper
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 18:21:02 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15116
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 18:21:02 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Blb1f-0008DV-B8; Fri, 16 Jul 2004 18:17:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Blarl-0003X5-3x
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 18:07:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13470
	for <pana@ietf.org>; Fri, 16 Jul 2004 18:07:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Blarg-0006E1-VL
	for pana@ietf.org; Fri, 16 Jul 2004 18:07:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Blaqi-0005ph-00
	for pana@ietf.org; Fri, 16 Jul 2004 18:06:37 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx with esmtp (Exim 4.12) id 1Blaoo-0004yH-00
	for pana@ietf.org; Fri, 16 Jul 2004 18:04:38 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0Y0080HTAXG5@mailout1.samsung.com> for pana@ietf.org; Sat,
	17 Jul 2004 07:04:09 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0Y0076ITAUO5@mailout1.samsung.com> for pana@ietf.org;
	Sat, 17 Jul 2004 07:04:06 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0Y00E2CTARQ5@mmp1.samsung.com> for
	pana@ietf.org; Sat, 17 Jul 2004 07:04:06 +0900 (KST)
Date: Fri, 16 Jul 2004 15:04:08 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: Issue 108 created (was Re: [Pana] issue85 (initial text))
To: pana@ietf.org
Message-id: <02c401c46b80$d2cc5950$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


> > - When a MAC address is used as the device identifer, it can change
if
> > the PaC has multiple interfaces to the same link and switches from
one
> > interface to another.
> 
> This is more like session migration from one network interface to
> another. I think we can discuss that, but we need another issue in the
> tracker. Issue 85 is concerned about change of PaC IP address from
PRPA
> to POPA.

There is a new record in the issue tracker for this feature:

108 Session migration from one interface to another

Discussions welcome.

Alper



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 19:14:08 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18079
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 19:14:08 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlbqL-0000kS-5l; Fri, 16 Jul 2004 19:10:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Blbp5-0000U5-Ow
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 19:09:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17666
	for <pana@ietf.org>; Fri, 16 Jul 2004 19:08:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Blbp1-000367-Si
	for pana@ietf.org; Fri, 16 Jul 2004 19:08:55 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Blbnu-0002hG-00
	for pana@ietf.org; Fri, 16 Jul 2004 19:07:48 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx with esmtp (Exim 4.12) id 1Blbms-0001xT-00
	for pana@ietf.org; Fri, 16 Jul 2004 19:06:43 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0Y00601W69WP@mailout2.samsung.com> for pana@ietf.org; Sat,
	17 Jul 2004 08:06:09 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0Y00F6VW6958@mailout2.samsung.com> for pana@ietf.org;
	Sat, 17 Jul 2004 08:06:09 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0Y001M4W66F1@mmp2.samsung.com> for
	pana@ietf.org; Sat, 17 Jul 2004 08:06:09 +0900 (KST)
Date: Fri, 16 Jul 2004 16:06:10 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] issue85 (initial text)
In-reply-to: <20040519015123.GC29343@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <02c801c46b89$7d34cb40$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

My comments on the proposed text are below....

> [1] Add the following item in section 4.1.1
> 
> "
>    o  IP-Address AVP: Conveys an IP-Address of a PaC.
> "
> 
> 
> [2] Add the following items in section 4.1.5:
> 
> "
>       *  IP address of PaC (may be the same as the Device-Id of PaC)
> 
>       *  IP address of PAA (may be the same as the Device-Id of PAA)
> "
> 
> 
> [3] Add the following item in section section 4.1.7:
> 
> "
>       When an IP-Address AVP is included, the AVP is valid if (i) the
>       Address type contained in the AVP matches the expected one
>       (i.e., either IPv4 or IPv6) that is used for the current PANA
>       session and (ii) the AVP value matches the one extracted from
>       the IP header.
> "

I think (i) and (ii) are over-constraining, and not sure about their
value. (ii) seems to achieve some kind of verification, but the PaC can
always spoof the IP source address anyways.  

> 
> [4] Update the following paragraph of section 4.4
> 
> "
>    The second type of re-authentication is based on a single protected
>    message exchange without entering the authentication phase.
>    PANA-Reauth-Request and PANA-Reauth-Answer messages are used for
this
>    purpose.  If there is an established PANA SA, both the PaC and the
>    PAA are allowed to send a PANA-Reauth-Request message to the
>    communicating peer whenever it needs to make sure the availability
of
>    the PANA SA on the peer and expect the peer to return a PANA-
>    Reauth-Answer message.  Both PANA-Reauth-Request/
PANA-Reauth-Answer
>    messages MUST be protected with a MAC AVP.
> "
> 
> to:
> 
> "
>    The second type of re-authentication is based on a single protected
>    message exchange without entering the authentication phase.
>    PANA-Reauth-Request and PANA-Reauth-Answer messages are used for
>    this purpose.  If there is an established PANA SA, both the PaC and
>    the PAA are allowed to send a PANA-Reauth-Request message to the
>    communicating peer whenever it needs to make sure the availability
>    of the PANA SA on the peer and expect the peer to return a
>    PANA-Reauth-Answer message.  In this case, both
>    PANA-Reauth-Request/PANA-Reauth-Answer messages MUST be protected
>    with a MAC AVP.  If there is an established PANA session but
>    without an established PANA SA, both the PaC and the PAA are
>    allowed to send a PANA-Reauth-Request message to the communicating
>    peer whenever it needs to make sure the availability of the PANA
>    session on the peer and expect the peer to return a
>    PANA-Reauth-Answer message.  In this case, both
>    PANA-Reauth-Request/PANA-Reauth-Answer messages are not protected
>    with a MAC AVP.
> "

I have a proposed text for this, which I think saves space:

"
   The second type of re-authentication is based on a single protected
   message exchange without entering the authentication phase.
   PANA-Reauth-Request and PANA-Reauth-Answer messages are used for this
   purpose.  If there is an established PANA session, both the PaC and
the
   PAA are allowed to send a PANA-Reauth-Request message to the
   communicating peer whenever they need to make sure the availability
of
   the session on the peer and expect the peer to return a PANA-
   Reauth-Answer message.  Both PANA-Reauth-Request/ PANA-Reauth-Answer
   messages MUST be protected with a MAC AVP when a PANA SA is
available.
"

So I think this is a test to see the availability of the matching
session on the peer. And it must be cryptographically protected when
possible. [Actually, I might even recommend we rename this type of usage
as PANA-ping or something. Though we can tackle this while resolving
issue 105.]


> 
> [5] Insert the following section after section 4.7:
> 
> "
> 4.8. Updating PaC's Address
> 
> A PaC's address can change in certain situations.  For example, the
> PANA framework [I-D.ietf-pana-framework] describes a case in which a
> PaC replaces a pre-PANA address (PRPA) a post-PANA address (POPA), and
> the PaC and PAA create host routes to each other in order to maintain
> on-link communication based on the POPA where the link-layer address
> of the PaC is used as the device identifier.  Also, a PaC's device
> identifier may change regardless of whether a link-layer address or an
> IP address is used as the device identifier.  As a result, it is
> possible when a link-layer address is used as the device identifier
> that both the device identifier and an IP address change.  In any
> case, the PAA needs to be notified about the change of address(es).
> 
> After the PaC has changed its address(es), it MUST send a
> PANA-Address-Update-Request message to the PAA.  The message carries
> the new address(es) in a Device-Id AVP and/or an IP-Address AVP.  At
> least one of these AVPs MUST appear in the request.  If an IP address
> is used as the device identifier, a Device-Id AVP MUST be used and an
> IP-Address AVP MUST NOT be used.  If an address contained in the
> request is invalid, the PAA sends a PANA-Error message with a result
> code PANA_INVALID_DEVICE_ID or PANA_INVALID_IP_ADDRESS depending on
> whether the device identifier or the IP address is invalid (in case
> both a Device-Id AVP and an IP-Address AVP are included and both are
> invalid, whichever result code is returned).  Otherwise, the PAA
> updates the address(es) of the PaC of the session attributes and
> returns a PANA-Address-Update-Answer message.  If there is an
> established PANA SA, both PANA-Address-Update-Request and
> PANA-Address-Update-Answer messages MUST be protected with a MAC AVP.
> "

Removing the "update of DI" from the above text and some other
editorials:

4.8. Updating PaC's Address
 
 A PaC's IP address can change in certain situations.  For example, the
 PANA framework [I-D.ietf-pana-framework] describes a case in which a
 PaC replaces a pre-PANA address (PRPA) with a post-PANA address (POPA),
and
 the PaC and PAA create host routes to each other in order to maintain
 on-link communication based on the POPA. The PAA needs to be notified 
 about the change of PaC address.
 
 After the PaC has changed its address, it MUST send a
 PANA-Update-Request message to the PAA.  The message MUST carry
 the new PaC address in an IP-Address AVP. If the address contained in
the
 request is invalid, the PAA MUST send a PANA-Error message with the
result
 code PANA_INVALID_IP_ADDRESS. Otherwise, the PAA MUST
 update the PANA session with the new PaC address and
 return a PANA-Update-Answer message.  If there is an
 established PANA SA, both PANA-Update-Request and
 PANA-Update-Answer messages MUST be protected with a MAC AVP.
 "



> 
> [6] Change Figure 10 to:
> 
> "
>                  Message                     Direction:
>                                              PaC---PAA
>                  ----------------------------------------
>                  PANA-PAA-Discover           -------->
> 
>                  PANA-Start-Request          <--------
>                  PANA-Start-Answer           -------->
> 
>                  PANA-Auth-Request           <--------
>                  PANA-Auth-Answer            -------->
> 
>                  PANA-FirstAuth-End-Request  <--------
>                  PANA-FirstAuth-End-Answer   -------->
> 
>                  PANA-Bind-Request           <--------
>                  PANA-Bind-Answer            -------->
> 
>                  PANA-Reauth-Request         <------->
>                  PANA-Reauth-Answer          <------->
> 
>                  PANA-Termination-Request    <------->
>                  PANA-Termination-Answer     <------->
> 
>                  PANA-Address-Update-Request -------->
>                  PANA-Address-Update-Answer  <--------

                 PANA-Update-Request -------->
                 PANA-Update-Answer  <--------

> 
>                  PANA-Error                  <------->
> "
> 
> [7] Change sections 6.4.9 and 6.4.10 from:
> 
> "
> 6.4.9 PANA-Reauth-Request (PRAR)
> 
>    PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
> 
>          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
>                        < Session-Id >
>                        [ Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> 
> 6.4.10 PANA-Reauth-Answer (PRAA)
> 
>    PANA-Reauth-Answer (PRAA) is sent in response to a
>    PANA-Reauth-Request.
> 
>          PANA-Reauth-Answer ::= < PANA-Header: 5 >
>                        < Session-Id >
>                        [ Device-Id ]
>                     *  [ AVP ]
>                    0*1 < MAC >
> "
> 
> to:
> 
> "
> 6.4.9 PANA-Reauth-Request (PRAR)
> 
>    PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
> 
>          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
>                        < Session-Id >
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> 
> 6.4.10 PANA-Reauth-Answer (PRAA)
> 
>    PANA-Reauth-Answer (PRAA) is sent in response to a
>    PANA-Reauth-Request.
> 
>          PANA-Reauth-Answer ::= < PANA-Header: 5 >
>                        < Session-Id >
>                     *  [ AVP ]
>                    0*1 < MAC >
> "
> 
> [8] Add the following sections:
> 
> "
> 6.4.16 PANA-Address-Update-Request (PAUR)

just renaming to PUR and removing DI part.

6.4.16 PANA-Update-Request (PUR)

 
    PANA-Update-Request (PUR) is sent by the PaC to the PAA.
 
          PANA-Update-Request ::= < PANA-Header: 9, REQ >
                        < Session-Id >
                        < IP-Address >
                    0*1 < MAC >
 
 
6.4.17 PANA-Update-Answer (PUA)
 
    PANA-Update-Answer (PAUA) is sent by the PAA to the PaC in
    response to a PANA-Update-Request.
 
          PANA-Update-Answer ::= < PANA-Header: 9 >
                        < Session-Id >
                    0*1 < MAC >
 "
> 
> "
> 6.5.19 IP-Address AVP
> 
>    The IP-Address (AVP Code: 1041) contains an IP address of a PaC.
>    The payload format of the IP-Address AVP is the same as that of the
>    Device-Id AVP (see See section Section 6.5.2).  Address families
>    for IPv4 or IPv6 MUST be used for this AVP.
> "
> 
> 
> [9] Add the following result code in section 6.5.7.2:

I think we can remove the DI part here.

> 
> "
>    PANA_INVALID_DEVICE_ID  5019
> 
>       Error code from PAA to PaC or from PaC to PAA.  This error is
>       returned in a PANA-Error message when the Device-Id AVP
>       contained in a received PANA-Bind-Request, PANA-Bind-Answer or
>       PANA-Address-Update-Request message is invalid.
> 
>    PANA_INVALID_IP_ADDRESS  5020

And this becomes 5019.

> 
>       Error code from PAA to PaC.  This error is returned in a
>       PANA-Error message when the IP-Address AVP in the received
>       PANA-Address-Update-Request message is invalid.


We can add "(e.g., a non-unicast address)."

> 
> "
> 
> [10]  Modify the AVP occurrence table as:
> 
> "
>                           +-----------------------------------------+
>                           |        Message                          |
>                           |          Type                           |
>                           +-----+-----+-----+-----+-----+-----+-----+
>       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
>       Result-Code         |  0  |  0  |  0  |  0  |  1  |  1  |  0  |
>       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
>       Termination-Cause   |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
>       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
>       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
>       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |
>       Device-Id           |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
>       Cookie              | 0-1 | 0-1 |  0  |  0  |  0  |  0  |  0  |
>       Protection-Cap.     | 0-1 |  0  |  0  |  0  | 0-1 |  0  |  0  |
>       PPAC                | 0-1 |  0  |  0  |  0  |  1  | 0-1 |  0  |
>       Session-Lifetime    |  0  |  0  |  0  |  0  | 0-1 |  0  |  0  |
>       Failed-AVP          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
>       ISP-Information     |  0+ | 0-1 |  0  |  0  |  0  |  0  |  0  |
>       NAP-Information     | 0-1 |  0  |  0  |  0  |  0  |  0  |  0  |
>       EP-Device-Id        |  0  |  0  |  0  |  0  |  0+ |  0  |  0  |
>       Key-Id              |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
>       IP-Address          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
>       --------------------+-----+-----+-----+-----+-----+-----+-----+
> 
>                  Figure 11: AVP Occurrence Table (1/3)
> 
>
+---------------------------------------------+
>                           |      Message
|
>                           |       Type
|
>
+------+------+-----+-----+-----+------+------+
>       Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER |
PFEA |
>
--------------------+------+------+-----+-----+-----+------+------+
>       Result-Code         |  0   |  0   |  0  |  0  |  1  |  1   |  0
|
>       Session-Id          |  1   |  1   |  1  |  1  |  1  |  1   |  1
|
>       Termination-Cause   |  0   |  0   |  1  |  0  |  0  |  0   |  0
|
>       EAP-Payload         |  0   |  0   |  0  |  0  |  0  |  1   |  0
|
>       MAC                 | 0-1  | 0-1  | 0-1 | 0-1 | 0-1 | 0-1  | 0-1
|
>       Nonce               |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Device-Id           |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Cookie              |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Protection-Cap.     |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       PPAC                |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Session-Lifetime    |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Failed-AVP          |  0   |  0   |  0  |  0  |  1  |  0   |  0
|
>       ISP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       NAP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       EP-Device-Id        |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>       Key-Id              |  0   |  0   |  0  |  0  |  0  | 0-1  | 0-1
|
>       IP-Address          |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
>
--------------------+------+------+-----+-----+-----+------+------+
> 
>                  Figure 12: AVP Occurrence Table (2/3)
> 
> 
>                           +-------------+
>                           |   Message   |
>                           |     Type    |
>                           +------+------+
>       Attribute Name      | PAUR | PAUA |

 PUR and PUA.


>       --------------------+------+------+
>       Result-Code         |  0   |  0   |
>       Session-Id          |  1   |  1   |
>       Termination-Cause   |  0   |  0   |
>       EAP-Payload         |  0   |  0   |
>       MAC                 | 0-1  | 0-1  |
>       Nonce               |  0   |  0   |
>       Device-Id           | 0-1  |  0   |

Device-Id 0 0

>       Cookie              |  0   |  0   |
>       Protection-Cap.     |  0   |  0   |
>       PPAC                |  0   |  0   |
>       Session-Lifetime    |  0   |  0   |
>       Failed-AVP          |  0   |  0   |
>       ISP-Information     |  0   |  0   |
>       NAP-Information     |  0   |  0   |
>       EP-Device-Id        |  0   |  0   |
>       Key-Id              |  0   |  0   |
>       IP-Address          | 0-1  |  0   |
>       --------------------+------+------+

IP-Address 1 0

> 
>                  Figure 13: AVP Occurrence Table (3/3)
> "
> 
> [11]  Change the text in section 7 from:
> 
> "
>          PANA-PAA-Discover (PDI)
>          PANA-Start-Request (PSR)*
>          PANA-Start-Answer (PSA)**
>          PANA-Bind-Request (PBR)
>          PANA-FirstAuth-End-Request (PFER)
>          PANA-Reauth-Request (PRAR)
>          PANA-Termination-Request (PTR)
> 
>          *)  PSR that carries a Cookie AVP is not retransmitted.
>          **) PSA that does not carry a Cookie AVP is not
retransmitted.
> "
> 
> to:
> 
> "
>          PANA-PAA-Discover (PDI)
>          PANA-Start-Request (PSR)*
>          PANA-Start-Answer (PSA)**
>          PANA-Bind-Request (PBR)
>          PANA-FirstAuth-End-Request (PFER)
>          PANA-Reauth-Request (PRAR)
>          PANA-Termination-Request (PTR)
>          PANA-Address-Update-Request (PAUR)

PUR

> 
>          *)  PSR that carries a Cookie AVP is not retransmitted.
>          **) PSA that does not carry a Cookie AVP is not
retransmitted.
> "
> 
> [12]  Add the folliwng text in section 8:
> 
> "
>    j) Updating PaC's address
> 
>    An attacker can generate a PANA-Address-Update-Request with an
>    invalid Device-Id AVP or an IP-Address AVP.  There are several

remove "invalid Device-Id AVP or".


>    threats:
> 
>    - An attacker spoofs an address and registers itself with the
>    address.  If the registered address is not assigned to any PaC,
>    subsequent PANA messages sent from the PAA to the attacker will not
>    reach any node and this is not a significant harm.  If the
>    registered address is assigned to some PaC, subsequent PANA
>    messages sent from the PAA to the attacker will reach the PaC, but
>    will be silently discarded because the Session-Id is different.
> 
>    - An attacker registers other PaC with any address.  As a result,
>    subsequent PANA messages sent from the PAA to the PaC will not
>    reach the PaC.
> 
>    To avoid all those attacks against an address update, an additional
>    mechanism may be defined outside the PANA protocol for the PAA to
>    validate ownership of the address.
> "


Alper



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 19:27:35 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19467
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 19:27:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Blc5e-0003G5-Na; Fri, 16 Jul 2004 19:26:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Blc4O-00038Z-TY
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 19:24:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19194
	for <pana@ietf.org>; Fri, 16 Jul 2004 19:24:46 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1Blc4L-0000m9-8x
	for pana@ietf.org; Fri, 16 Jul 2004 19:24:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Blc3d-0000Qn-00
	for pana@ietf.org; Fri, 16 Jul 2004 19:24:02 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Blc2X-0007jS-00
	for pana@ietf.org; Fri, 16 Jul 2004 19:22:53 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6GNMflr003207;
	Sat, 17 Jul 2004 08:22:41 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6GNMfpW011830;
	Sat, 17 Jul 2004 08:22:41 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	JAA11829 ; Sat, 17 Jul 2004 08:22:40 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA23735; Sat, 17 Jul 2004 08:22:40 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA03837;
	Sat, 17 Jul 2004 08:22:39 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6GNMdpl012141;
	Sat, 17 Jul 2004 08:22:39 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0Y00AMRWXO42@tsbpo1.po.toshiba.co.jp>; Sat,
	17 Jul 2004 08:22:38 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Blc1H-0002Xy-00; Fri, 16 Jul 2004 16:21:35 -0700
Date: Fri, 16 Jul 2004 19:21:35 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New: [issue98] Lost answer problem
In-reply-to: <01ff01c46b5f$2480c320$9b1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040716232135.GE6305@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040716013116.GV893@steelhead>
	<01ff01c46b5f$2480c320$9b1d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

I realized that PANA-PAA-Discover message should not be expected in
authentication phase and termination phase.  I'd further revise [1] to
reflect this.

Yoshihiro Ohba


On Fri, Jul 16, 2004 at 11:03:03AM -0700, Alper Yegin wrote:
> Looks good to me.
> 
> Alper
> 
> 
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Thursday, July 15, 2004 6:31 PM
> > To: Alper Yegin
> > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > Subject: Re: [Pana] New: [issue98] Lost answer problem
> > 
> > In addition to the original proposed text, I's suggest adding the list
> > of unexpected requests.  Here is the entire proposed text:
> > 
> > [1] Change section 4.1.7:
> > 
> > "
> > o  The message type is one of the expected types in the current
> >    state.
> > "
> > 
> > to:
> > 
> > o  The message type is one of the expected types in the current
> >    state.
> > 
> >    Specifically the following messages are unexpected and invalid:
> > 
> >    o In discovery and initial handshake phase:
> > 
> >      - PANA-Termination-Request and PANA-Reauth-Request.
> > 
> >      - PANA-Bind-Request.
> > 
> >      - PANA-Update-Request.
> > 
> >    o In authentication phase:
> > 
> >      - PANA-Termination-Request and PANA-Reauth-Request.
> > 
> >      - PANA-Update-Request.
> > 
> >      - PANA-Start-Request after a PaC receives the first valid
> >        PANA-Auth-Request.
> > 
> >    o After successful PANA authentication:
> > 
> >      - PANA-Start-Request as well as a non-duplicate PANA-Bind-Request
> >        (see section 4.X for definition of duplicate requests)
> > 
> >      - PANA-PAA-Discover without a Session-Id AVP.
> > 
> >    o In termination phase:
> > 
> >      - All requests but PANA-Termination-Request.
> > "
> > 
> > (I guess this section should move back, because it contains details.)
> > 
> > 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 20:04:06 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21182
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 20:04:06 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlcZo-0007Jn-94; Fri, 16 Jul 2004 19:57:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BlcTG-0006Zr-QB
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 19:50:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20497
	for <pana@ietf.org>; Fri, 16 Jul 2004 19:50:29 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlcTC-0001Si-UI
	for pana@ietf.org; Fri, 16 Jul 2004 19:50:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BlcSJ-00019R-00
	for pana@ietf.org; Fri, 16 Jul 2004 19:49:32 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1BlcRO-0000qi-00
	for pana@ietf.org; Fri, 16 Jul 2004 19:48:34 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6GNmWlr009937;
	Sat, 17 Jul 2004 08:48:32 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6GNmWRr019910;
	Sat, 17 Jul 2004 08:48:32 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	JAA19909 ; Sat, 17 Jul 2004 08:48:32 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA29553; Sat, 17 Jul 2004 08:48:31 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA12778;
	Sat, 17 Jul 2004 08:48:31 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6GNmUpl020751;
	Sat, 17 Jul 2004 08:48:30 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0Y00D2JY4QME@tsbpo1.po.toshiba.co.jp>; Sat,
	17 Jul 2004 08:48:29 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BlcQR-0002ex-00; Fri, 16 Jul 2004 16:47:35 -0700
Date: Fri, 16 Jul 2004 19:47:34 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (initial text)
In-reply-to: <02c801c46b89$7d34cb40$9b1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040716234734.GF6305@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040519015123.GC29343@steelhead>
	<02c801c46b89$7d34cb40$9b1d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Fri, Jul 16, 2004 at 04:06:10PM -0700, Alper Yegin wrote:
> My comments on the proposed text are below....
> 
> > [1] Add the following item in section 4.1.1
> > 
> > "
> >    o  IP-Address AVP: Conveys an IP-Address of a PaC.
> > "
> > 
> > 
> > [2] Add the following items in section 4.1.5:
> > 
> > "
> >       *  IP address of PaC (may be the same as the Device-Id of PaC)
> > 
> >       *  IP address of PAA (may be the same as the Device-Id of PAA)
> > "
> > 
> > 
> > [3] Add the following item in section section 4.1.7:
> > 
> > "
> >       When an IP-Address AVP is included, the AVP is valid if (i) the
> >       Address type contained in the AVP matches the expected one
> >       (i.e., either IPv4 or IPv6) that is used for the current PANA
> >       session and (ii) the AVP value matches the one extracted from
> >       the IP header.
> > "
> 
> I think (i) and (ii) are over-constraining, and not sure about their
> value. (ii) seems to achieve some kind of verification, but the PaC can
> always spoof the IP source address anyways.  

Yes, (ii) cannot prevent source address spoofing, thus I agree that 
(ii) might not be needed.

For (i), is there any valid case where IP-Address AVP with IPv4(v6) 
is contained while PANA runs over IPv6(v4)?

I agree on the rest of your suggestions.

Yoshihiro Ohba


> 
> > 
> > [4] Update the following paragraph of section 4.4
> > 
> > "
> >    The second type of re-authentication is based on a single protected
> >    message exchange without entering the authentication phase.
> >    PANA-Reauth-Request and PANA-Reauth-Answer messages are used for
> this
> >    purpose.  If there is an established PANA SA, both the PaC and the
> >    PAA are allowed to send a PANA-Reauth-Request message to the
> >    communicating peer whenever it needs to make sure the availability
> of
> >    the PANA SA on the peer and expect the peer to return a PANA-
> >    Reauth-Answer message.  Both PANA-Reauth-Request/
> PANA-Reauth-Answer
> >    messages MUST be protected with a MAC AVP.
> > "
> > 
> > to:
> > 
> > "
> >    The second type of re-authentication is based on a single protected
> >    message exchange without entering the authentication phase.
> >    PANA-Reauth-Request and PANA-Reauth-Answer messages are used for
> >    this purpose.  If there is an established PANA SA, both the PaC and
> >    the PAA are allowed to send a PANA-Reauth-Request message to the
> >    communicating peer whenever it needs to make sure the availability
> >    of the PANA SA on the peer and expect the peer to return a
> >    PANA-Reauth-Answer message.  In this case, both
> >    PANA-Reauth-Request/PANA-Reauth-Answer messages MUST be protected
> >    with a MAC AVP.  If there is an established PANA session but
> >    without an established PANA SA, both the PaC and the PAA are
> >    allowed to send a PANA-Reauth-Request message to the communicating
> >    peer whenever it needs to make sure the availability of the PANA
> >    session on the peer and expect the peer to return a
> >    PANA-Reauth-Answer message.  In this case, both
> >    PANA-Reauth-Request/PANA-Reauth-Answer messages are not protected
> >    with a MAC AVP.
> > "
> 
> I have a proposed text for this, which I think saves space:
> 
> "
>    The second type of re-authentication is based on a single protected
>    message exchange without entering the authentication phase.
>    PANA-Reauth-Request and PANA-Reauth-Answer messages are used for this
>    purpose.  If there is an established PANA session, both the PaC and
> the
>    PAA are allowed to send a PANA-Reauth-Request message to the
>    communicating peer whenever they need to make sure the availability
> of
>    the session on the peer and expect the peer to return a PANA-
>    Reauth-Answer message.  Both PANA-Reauth-Request/ PANA-Reauth-Answer
>    messages MUST be protected with a MAC AVP when a PANA SA is
> available.
> "
> 
> So I think this is a test to see the availability of the matching
> session on the peer. And it must be cryptographically protected when
> possible. [Actually, I might even recommend we rename this type of usage
> as PANA-ping or something. Though we can tackle this while resolving
> issue 105.]
> 
> 
> > 
> > [5] Insert the following section after section 4.7:
> > 
> > "
> > 4.8. Updating PaC's Address
> > 
> > A PaC's address can change in certain situations.  For example, the
> > PANA framework [I-D.ietf-pana-framework] describes a case in which a
> > PaC replaces a pre-PANA address (PRPA) a post-PANA address (POPA), and
> > the PaC and PAA create host routes to each other in order to maintain
> > on-link communication based on the POPA where the link-layer address
> > of the PaC is used as the device identifier.  Also, a PaC's device
> > identifier may change regardless of whether a link-layer address or an
> > IP address is used as the device identifier.  As a result, it is
> > possible when a link-layer address is used as the device identifier
> > that both the device identifier and an IP address change.  In any
> > case, the PAA needs to be notified about the change of address(es).
> > 
> > After the PaC has changed its address(es), it MUST send a
> > PANA-Address-Update-Request message to the PAA.  The message carries
> > the new address(es) in a Device-Id AVP and/or an IP-Address AVP.  At
> > least one of these AVPs MUST appear in the request.  If an IP address
> > is used as the device identifier, a Device-Id AVP MUST be used and an
> > IP-Address AVP MUST NOT be used.  If an address contained in the
> > request is invalid, the PAA sends a PANA-Error message with a result
> > code PANA_INVALID_DEVICE_ID or PANA_INVALID_IP_ADDRESS depending on
> > whether the device identifier or the IP address is invalid (in case
> > both a Device-Id AVP and an IP-Address AVP are included and both are
> > invalid, whichever result code is returned).  Otherwise, the PAA
> > updates the address(es) of the PaC of the session attributes and
> > returns a PANA-Address-Update-Answer message.  If there is an
> > established PANA SA, both PANA-Address-Update-Request and
> > PANA-Address-Update-Answer messages MUST be protected with a MAC AVP.
> > "
> 
> Removing the "update of DI" from the above text and some other
> editorials:
> 
> 4.8. Updating PaC's Address
>  
>  A PaC's IP address can change in certain situations.  For example, the
>  PANA framework [I-D.ietf-pana-framework] describes a case in which a
>  PaC replaces a pre-PANA address (PRPA) with a post-PANA address (POPA),
> and
>  the PaC and PAA create host routes to each other in order to maintain
>  on-link communication based on the POPA. The PAA needs to be notified 
>  about the change of PaC address.
>  
>  After the PaC has changed its address, it MUST send a
>  PANA-Update-Request message to the PAA.  The message MUST carry
>  the new PaC address in an IP-Address AVP. If the address contained in
> the
>  request is invalid, the PAA MUST send a PANA-Error message with the
> result
>  code PANA_INVALID_IP_ADDRESS. Otherwise, the PAA MUST
>  update the PANA session with the new PaC address and
>  return a PANA-Update-Answer message.  If there is an
>  established PANA SA, both PANA-Update-Request and
>  PANA-Update-Answer messages MUST be protected with a MAC AVP.
>  "
> 
> 
> 
> > 
> > [6] Change Figure 10 to:
> > 
> > "
> >                  Message                     Direction:
> >                                              PaC---PAA
> >                  ----------------------------------------
> >                  PANA-PAA-Discover           -------->
> > 
> >                  PANA-Start-Request          <--------
> >                  PANA-Start-Answer           -------->
> > 
> >                  PANA-Auth-Request           <--------
> >                  PANA-Auth-Answer            -------->
> > 
> >                  PANA-FirstAuth-End-Request  <--------
> >                  PANA-FirstAuth-End-Answer   -------->
> > 
> >                  PANA-Bind-Request           <--------
> >                  PANA-Bind-Answer            -------->
> > 
> >                  PANA-Reauth-Request         <------->
> >                  PANA-Reauth-Answer          <------->
> > 
> >                  PANA-Termination-Request    <------->
> >                  PANA-Termination-Answer     <------->
> > 
> >                  PANA-Address-Update-Request -------->
> >                  PANA-Address-Update-Answer  <--------
> 
>                  PANA-Update-Request -------->
>                  PANA-Update-Answer  <--------
> 
> > 
> >                  PANA-Error                  <------->
> > "
> > 
> > [7] Change sections 6.4.9 and 6.4.10 from:
> > 
> > "
> > 6.4.9 PANA-Reauth-Request (PRAR)
> > 
> >    PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
> > 
> >          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
> >                        < Session-Id >
> >                        [ Device-Id ]
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> > 
> > 
> > 6.4.10 PANA-Reauth-Answer (PRAA)
> > 
> >    PANA-Reauth-Answer (PRAA) is sent in response to a
> >    PANA-Reauth-Request.
> > 
> >          PANA-Reauth-Answer ::= < PANA-Header: 5 >
> >                        < Session-Id >
> >                        [ Device-Id ]
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> > "
> > 
> > to:
> > 
> > "
> > 6.4.9 PANA-Reauth-Request (PRAR)
> > 
> >    PANA-Reauth-Request (PRAR) is either sent by the PaC or the PAA.
> > 
> >          PANA-Reauth-Request ::= < PANA-Header: 5, REQ >
> >                        < Session-Id >
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> > 
> > 
> > 6.4.10 PANA-Reauth-Answer (PRAA)
> > 
> >    PANA-Reauth-Answer (PRAA) is sent in response to a
> >    PANA-Reauth-Request.
> > 
> >          PANA-Reauth-Answer ::= < PANA-Header: 5 >
> >                        < Session-Id >
> >                     *  [ AVP ]
> >                    0*1 < MAC >
> > "
> > 
> > [8] Add the following sections:
> > 
> > "
> > 6.4.16 PANA-Address-Update-Request (PAUR)
> 
> just renaming to PUR and removing DI part.
> 
> 6.4.16 PANA-Update-Request (PUR)
> 
>  
>     PANA-Update-Request (PUR) is sent by the PaC to the PAA.
>  
>           PANA-Update-Request ::= < PANA-Header: 9, REQ >
>                         < Session-Id >
>                         < IP-Address >
>                     0*1 < MAC >
>  
>  
> 6.4.17 PANA-Update-Answer (PUA)
>  
>     PANA-Update-Answer (PAUA) is sent by the PAA to the PaC in
>     response to a PANA-Update-Request.
>  
>           PANA-Update-Answer ::= < PANA-Header: 9 >
>                         < Session-Id >
>                     0*1 < MAC >
>  "
> > 
> > "
> > 6.5.19 IP-Address AVP
> > 
> >    The IP-Address (AVP Code: 1041) contains an IP address of a PaC.
> >    The payload format of the IP-Address AVP is the same as that of the
> >    Device-Id AVP (see See section Section 6.5.2).  Address families
> >    for IPv4 or IPv6 MUST be used for this AVP.
> > "
> > 
> > 
> > [9] Add the following result code in section 6.5.7.2:
> 
> I think we can remove the DI part here.
> 
> > 
> > "
> >    PANA_INVALID_DEVICE_ID  5019
> > 
> >       Error code from PAA to PaC or from PaC to PAA.  This error is
> >       returned in a PANA-Error message when the Device-Id AVP
> >       contained in a received PANA-Bind-Request, PANA-Bind-Answer or
> >       PANA-Address-Update-Request message is invalid.
> > 
> >    PANA_INVALID_IP_ADDRESS  5020
> 
> And this becomes 5019.
> 
> > 
> >       Error code from PAA to PaC.  This error is returned in a
> >       PANA-Error message when the IP-Address AVP in the received
> >       PANA-Address-Update-Request message is invalid.
> 
> 
> We can add "(e.g., a non-unicast address)."
> 
> > 
> > "
> > 
> > [10]  Modify the AVP occurrence table as:
> > 
> > "
> >                           +-----------------------------------------+
> >                           |        Message                          |
> >                           |          Type                           |
> >                           +-----+-----+-----+-----+-----+-----+-----+
> >       Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
> >       --------------------+-----+-----+-----+-----+-----+-----+-----+
> >       Result-Code         |  0  |  0  |  0  |  0  |  1  |  1  |  0  |
> >       Session-Id          |  0  | 0-1 |  1  |  1  |  1  |  1  | 0-1 |
> >       Termination-Cause   |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
> >       EAP-Payload         | 0-1 | 0-1 |  1  |  1  | 0-1 |  0  |  0  |
> >       MAC                 |  0  | 0-1 | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
> >       Nonce               |  0  | 0-1 |  0  |  0  | 0-1 |  0  |  0  |
> >       Device-Id           |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
> >       Cookie              | 0-1 | 0-1 |  0  |  0  |  0  |  0  |  0  |
> >       Protection-Cap.     | 0-1 |  0  |  0  |  0  | 0-1 |  0  |  0  |
> >       PPAC                | 0-1 |  0  |  0  |  0  |  1  | 0-1 |  0  |
> >       Session-Lifetime    |  0  |  0  |  0  |  0  | 0-1 |  0  |  0  |
> >       Failed-AVP          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
> >       ISP-Information     |  0+ | 0-1 |  0  |  0  |  0  |  0  |  0  |
> >       NAP-Information     | 0-1 |  0  |  0  |  0  |  0  |  0  |  0  |
> >       EP-Device-Id        |  0  |  0  |  0  |  0  |  0+ |  0  |  0  |
> >       Key-Id              |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
> >       IP-Address          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
> >       --------------------+-----+-----+-----+-----+-----+-----+-----+
> > 
> >                  Figure 11: AVP Occurrence Table (1/3)
> > 
> >
> +---------------------------------------------+
> >                           |      Message
> |
> >                           |       Type
> |
> >
> +------+------+-----+-----+-----+------+------+
> >       Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER |
> PFEA |
> >
> --------------------+------+------+-----+-----+-----+------+------+
> >       Result-Code         |  0   |  0   |  0  |  0  |  1  |  1   |  0
> |
> >       Session-Id          |  1   |  1   |  1  |  1  |  1  |  1   |  1
> |
> >       Termination-Cause   |  0   |  0   |  1  |  0  |  0  |  0   |  0
> |
> >       EAP-Payload         |  0   |  0   |  0  |  0  |  0  |  1   |  0
> |
> >       MAC                 | 0-1  | 0-1  | 0-1 | 0-1 | 0-1 | 0-1  | 0-1
> |
> >       Nonce               |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Device-Id           |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Cookie              |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Protection-Cap.     |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       PPAC                |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Session-Lifetime    |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Failed-AVP          |  0   |  0   |  0  |  0  |  1  |  0   |  0
> |
> >       ISP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       NAP-Information     |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       EP-Device-Id        |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >       Key-Id              |  0   |  0   |  0  |  0  |  0  | 0-1  | 0-1
> |
> >       IP-Address          |  0   |  0   |  0  |  0  |  0  |  0   |  0
> |
> >
> --------------------+------+------+-----+-----+-----+------+------+
> > 
> >                  Figure 12: AVP Occurrence Table (2/3)
> > 
> > 
> >                           +-------------+
> >                           |   Message   |
> >                           |     Type    |
> >                           +------+------+
> >       Attribute Name      | PAUR | PAUA |
> 
>  PUR and PUA.
> 
> 
> >       --------------------+------+------+
> >       Result-Code         |  0   |  0   |
> >       Session-Id          |  1   |  1   |
> >       Termination-Cause   |  0   |  0   |
> >       EAP-Payload         |  0   |  0   |
> >       MAC                 | 0-1  | 0-1  |
> >       Nonce               |  0   |  0   |
> >       Device-Id           | 0-1  |  0   |
> 
> Device-Id 0 0
> 
> >       Cookie              |  0   |  0   |
> >       Protection-Cap.     |  0   |  0   |
> >       PPAC                |  0   |  0   |
> >       Session-Lifetime    |  0   |  0   |
> >       Failed-AVP          |  0   |  0   |
> >       ISP-Information     |  0   |  0   |
> >       NAP-Information     |  0   |  0   |
> >       EP-Device-Id        |  0   |  0   |
> >       Key-Id              |  0   |  0   |
> >       IP-Address          | 0-1  |  0   |
> >       --------------------+------+------+
> 
> IP-Address 1 0
> 
> > 
> >                  Figure 13: AVP Occurrence Table (3/3)
> > "
> > 
> > [11]  Change the text in section 7 from:
> > 
> > "
> >          PANA-PAA-Discover (PDI)
> >          PANA-Start-Request (PSR)*
> >          PANA-Start-Answer (PSA)**
> >          PANA-Bind-Request (PBR)
> >          PANA-FirstAuth-End-Request (PFER)
> >          PANA-Reauth-Request (PRAR)
> >          PANA-Termination-Request (PTR)
> > 
> >          *)  PSR that carries a Cookie AVP is not retransmitted.
> >          **) PSA that does not carry a Cookie AVP is not
> retransmitted.
> > "
> > 
> > to:
> > 
> > "
> >          PANA-PAA-Discover (PDI)
> >          PANA-Start-Request (PSR)*
> >          PANA-Start-Answer (PSA)**
> >          PANA-Bind-Request (PBR)
> >          PANA-FirstAuth-End-Request (PFER)
> >          PANA-Reauth-Request (PRAR)
> >          PANA-Termination-Request (PTR)
> >          PANA-Address-Update-Request (PAUR)
> 
> PUR
> 
> > 
> >          *)  PSR that carries a Cookie AVP is not retransmitted.
> >          **) PSA that does not carry a Cookie AVP is not
> retransmitted.
> > "
> > 
> > [12]  Add the folliwng text in section 8:
> > 
> > "
> >    j) Updating PaC's address
> > 
> >    An attacker can generate a PANA-Address-Update-Request with an
> >    invalid Device-Id AVP or an IP-Address AVP.  There are several
> 
> remove "invalid Device-Id AVP or".
> 
> 
> >    threats:
> > 
> >    - An attacker spoofs an address and registers itself with the
> >    address.  If the registered address is not assigned to any PaC,
> >    subsequent PANA messages sent from the PAA to the attacker will not
> >    reach any node and this is not a significant harm.  If the
> >    registered address is assigned to some PaC, subsequent PANA
> >    messages sent from the PAA to the attacker will reach the PaC, but
> >    will be silently discarded because the Session-Id is different.
> > 
> >    - An attacker registers other PaC with any address.  As a result,
> >    subsequent PANA messages sent from the PAA to the PaC will not
> >    reach the PaC.
> > 
> >    To avoid all those attacks against an address update, an additional
> >    mechanism may be defined outside the PANA protocol for the PAA to
> >    validate ownership of the address.
> > "
> 
> 
> Alper
> 
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 20:21:47 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22300
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 20:21:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BlcuK-00025S-NN; Fri, 16 Jul 2004 20:18:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Blcpc-0001Ug-NL
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 20:13:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21745
	for <pana@ietf.org>; Fri, 16 Jul 2004 20:13:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BlcpY-0001Fb-UF
	for pana@ietf.org; Fri, 16 Jul 2004 20:13:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Blcob-0000wN-00
	for pana@ietf.org; Fri, 16 Jul 2004 20:12:33 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx with esmtp (Exim 4.12) id 1Blco1-0000cW-00
	for pana@ietf.org; Fri, 16 Jul 2004 20:11:57 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I0Y00508Z74W2@mailout3.samsung.com> for pana@ietf.org; Sat,
	17 Jul 2004 09:11:28 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I0Y00DYBZ70RH@mailout3.samsung.com> for pana@ietf.org;
	Sat, 17 Jul 2004 09:11:24 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I0Y003GHZ6YM2@mmp2.samsung.com> for
	pana@ietf.org; Sat, 17 Jul 2004 09:11:24 +0900 (KST)
Date: Fri, 16 Jul 2004 17:11:26 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] issue85 (initial text)
In-reply-to: <20040716234734.GF6305@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <02dc01c46b92$9b03c7d0$9b1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> For (i), is there any valid case where IP-Address AVP with IPv4(v6)
> is contained while PANA runs over IPv6(v4)?

I see it this way:
- Can PANA session start on IPv4(v6) and than switch to IPv6(v4) after
successful PANA authentication?

I couldn't find a solid scenario to back up the need for this. But on
the other hand I couldn't see the benefit of constraining this, or the
cost of relaxing either...

Alper
 




_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 16 20:40:51 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23556
	for <pana-archive@lists.ietf.org>; Fri, 16 Jul 2004 20:40:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BldDX-0004uF-E0; Fri, 16 Jul 2004 20:38:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BldBp-0004aQ-2u
	for pana@megatron.ietf.org; Fri, 16 Jul 2004 20:36:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23295
	for <pana@ietf.org>; Fri, 16 Jul 2004 20:36:31 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32) id 1BldBl-0001Hc-D5
	for pana@ietf.org; Fri, 16 Jul 2004 20:36:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BldAj-0000uw-00
	for pana@ietf.org; Fri, 16 Jul 2004 20:35:26 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12) id 1Bld9j-0000Y1-00
	for pana@ietf.org; Fri, 16 Jul 2004 20:34:23 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6H0YOlr023930;
	Sat, 17 Jul 2004 09:34:24 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6H0YOYC006447;
	Sat, 17 Jul 2004 09:34:24 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	KAA06444 ; Sat, 17 Jul 2004 09:34:24 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA11673; Sat, 17 Jul 2004 09:34:23 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA28649;
	Sat, 17 Jul 2004 09:34:22 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6H0YLpl007218;
	Sat, 17 Jul 2004 09:34:21 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I0Z00DR8096ME@tsbpo1.po.toshiba.co.jp>; Sat,
	17 Jul 2004 09:34:21 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bld8i-0002r6-00; Fri, 16 Jul 2004 17:33:20 -0700
Date: Fri, 16 Jul 2004 20:33:20 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue85 (initial text)
In-reply-to: <02dc01c46b92$9b03c7d0$9b1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040717003319.GG6305@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <20040716234734.GF6305@steelhead>
	<02dc01c46b92$9b03c7d0$9b1d9069@sisa.samsung.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Fri, Jul 16, 2004 at 05:11:26PM -0700, Alper Yegin wrote:
> > For (i), is there any valid case where IP-Address AVP with IPv4(v6)
> > is contained while PANA runs over IPv6(v4)?
> 
> I see it this way:
> - Can PANA session start on IPv4(v6) and than switch to IPv6(v4) after
> successful PANA authentication?
> 
> I couldn't find a solid scenario to back up the need for this. But on
> the other hand I couldn't see the benefit of constraining this, or the
> cost of relaxing either...

OK, I can live with also removing (i) until this case is determined to
be an error case without exception, given that this becomes a new PANA
issue.

Yoshihiro Ohba


> 
> Alper
>  
> 
> 
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 19 18:35:44 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24844
	for <pana-archive@lists.ietf.org>; Mon, 19 Jul 2004 18:35:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BmeSb-0005n8-GW; Mon, 19 Jul 2004 16:10:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BmeEy-0002A6-B1; Mon, 19 Jul 2004 15:56:00 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19476;
	Mon, 19 Jul 2004 15:55:57 -0400 (EDT)
Message-Id: <200407191955.PAA19476@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 19 Jul 2004 15:55:57 -0400
Cc: pana@ietf.org
Subject: [Pana] I-D ACTION:draft-ietf-pana-pana-05.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

--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		: Protocol for Carrying Authentication for Network Access (PANA)
	Author(s)	: D. Forsberg, et al.
	Filename	: draft-ietf-pana-pana-05.txt
	Pages		: 77
	Date		: 2004-7-19
	
Authentication Protocol (EAP) to enable network access authentication
   between clients and access networks.  PANA can carry any
   authentication method that can be specified as an EAP method, and can
   be used on any link that can carry IP.  PANA covers the
   client-to-network access authentication part of an overall secure
   network access framework, which additionally includes other protocols
   and mechanisms for service provisioning, access control as a result
   of initial authentication, and accounting.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pana-pana-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pana-pana-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-7-19152708.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pana-pana-05.txt

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

Content-Type: text/plain
Content-ID: <2004-7-19152708.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana

--NextPart--





From pana-bounces@ietf.org  Mon Jul 19 19:57:02 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11388
	for <pana-archive@lists.ietf.org>; Mon, 19 Jul 2004 19:57:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BmhTW-0000ud-6G; Mon, 19 Jul 2004 19:23:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BmfWQ-0005Wj-8P
	for pana@megatron.ietf.org; Mon, 19 Jul 2004 17:18:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08655
	for <pana@ietf.org>; Mon, 19 Jul 2004 17:18:03 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BmfWP-0005b7-GR
	for pana@ietf.org; Mon, 19 Jul 2004 17:18:06 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I1400F01B58HE@mailout2.samsung.com> for pana@ietf.org; Tue,
	20 Jul 2004 06:17:32 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I140023TB57F7@mailout2.samsung.com> for pana@ietf.org;
	Tue, 20 Jul 2004 06:17:31 +0900 (KST)
Received: from Alperyegin ([105.253.155.40])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I1400G70B5434@mmp2.samsung.com> for
	pana@ietf.org; Tue, 20 Jul 2004 06:17:31 +0900 (KST)
Date: Mon, 19 Jul 2004 14:17:34 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <02fb01c46dd5$d11bfaf0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7BIT
Cc: "'Thomas Narten'" <narten@us.ibm.com>
Subject: [Pana] Draft agenda for IETF 60
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Hello,

Here is the draft agenda for the upcoming PANA meeting.
Comments welcome.

- Chairs


Protocol for Carrying Authentication for Network Access WG (pana)

Monday, August 2 at 1530-1730
============================

CHAIRS: Basavaraj Patil <Basavaraj.Patil@nokia.com>
        Alper Yegin <alper@samsung.com>


AGENDA:

1. Preliminaries (bluesheets, minute takers, agenda bashing, document
   status) : 5 min, Chairs


2. PANA protocol update and open issues: 30 min, Alper Yegin

   Discussion of open and closed issues on draft-ietf-pana-pana-05.txt. 
   See "Change History" section of the draft for the list of issues 
   closed in this revision. Additional issues may be discussed on the 
   mailing list prior to the meeting. Detailed issue descriptions can 
   be found at http://danforsberg.info:8080/pana-issues/


3. PANA framework update and open issues: 5 min, Yoshihiro Ohba

   Discussion of open and closed issues on
draft-ietf-pana-framework-01.txt. 


4. SNMP usage for PAA-2-EP interface: 5 min, Yacine El Mghazli

   Discussion of open and closed issues on draft-ietf-pana-snmp-01.txt.



5. PANA-IPsec I-D update and open issues: 5 min, Mohan Parthasarathy

   Discussion of open and closed issues on
draft-ietf-pana-ipsec-04.txt(?).   


6. PANA state machine: 15 min, Victor Fajardo

   New I-D presentation for draft-ohba-pana-statemachine-00.txt.


7. Context transfer for PANA: 20 min, Julien Bournelle

   New I-D presentation for draft-bournelle-pana-ctp-00.txt.


8. Next steps: 5 min, Chairs



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 19 19:58:43 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11693
	for <pana-archive@lists.ietf.org>; Mon, 19 Jul 2004 19:58:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BmhZc-0004xD-8O; Mon, 19 Jul 2004 19:29:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bmfr7-0004dy-9X
	for pana@megatron.ietf.org; Mon, 19 Jul 2004 17:39:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12733
	for <pana@ietf.org>; Mon, 19 Jul 2004 17:39:25 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bmfr6-0006ne-E2
	for pana@ietf.org; Mon, 19 Jul 2004 17:39:29 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I1400G01C4VH0@mailout2.samsung.com> for pana@ietf.org; Tue,
	20 Jul 2004 06:38:55 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I1400AFWC4VD6@mailout2.samsung.com> for pana@ietf.org;
	Tue, 20 Jul 2004 06:38:55 +0900 (KST)
Received: from Alperyegin ([105.253.155.40])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I14001YKC4SJQ@mmp1.samsung.com> for
	pana@ietf.org; Tue, 20 Jul 2004 06:38:55 +0900 (KST)
Date: Mon, 19 Jul 2004 14:38:58 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <034f01c46dd8$ce18c5b0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7BIT
Subject: [Pana] same name space...
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

The PANA specification says:

6.5  AVPs in PANA

   Some of the used AVPs are defined in this document and some of them
   are defined in other documents like [RFC3588].  PANA proposes to use
   the same name space with [RFC3588].  For temporary allocation, PANA
   uses AVP type numbers starting from 1024.

I'm not sure what exactly using the same name space means here. Does it
mean what we should never use a DIAMETER AVP name as a PANA AVP name
unless the specifics are exactly same as defined in RFC 3588?

Alper



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 19 20:01:53 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12221
	for <pana-archive@lists.ietf.org>; Mon, 19 Jul 2004 20:01:53 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BmhdI-0000b3-9w; Mon, 19 Jul 2004 19:33:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bmg0t-0000Dn-Tq
	for pana@megatron.ietf.org; Mon, 19 Jul 2004 17:49:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14538
	for <pana@ietf.org>; Mon, 19 Jul 2004 17:49:32 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bmg0t-0007IF-EK
	for pana@ietf.org; Mon, 19 Jul 2004 17:49:36 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I1400J01CLKQG@mailout1.samsung.com> for pana@ietf.org; Tue,
	20 Jul 2004 06:48:56 +0900 (KST)
Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I1400EUSCLKIB@mailout1.samsung.com> for pana@ietf.org;
	Tue, 20 Jul 2004 06:48:56 +0900 (KST)
Received: from Alperyegin ([105.253.155.40])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I1400KE8CLHQ8@mmp2.samsung.com> for
	pana@ietf.org; Tue, 20 Jul 2004 06:48:55 +0900 (KST)
Date: Mon, 19 Jul 2004 14:48:59 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <035001c46dda$343d57b0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Content-Transfer-Encoding: 7BIT
Subject: [Pana] New Issue 109: Adjustment on the field sizes
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

http://danforsberg.info:8080/pana-issues/issue109

Alper



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 20 21:25:47 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20981
	for <pana-archive@lists.ietf.org>; Tue, 20 Jul 2004 21:25:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bn2GF-0002CY-UH; Tue, 20 Jul 2004 17:34:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bn15S-00089d-Eq; Tue, 20 Jul 2004 16:19:42 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25541;
	Tue, 20 Jul 2004 16:19:40 -0400 (EDT)
Message-Id: <200407202019.QAA25541@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 20 Jul 2004 16:19:39 -0400
Cc: pana@ietf.org
Subject: [Pana] I-D ACTION:draft-ietf-pana-framework-01.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

--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		: PANA Framework
	Author(s)	: P. Jayaraman, et al.
	Filename	: draft-ietf-pana-framework-01.txt
	Pages		: 46
	Date		: 2004-7-20
	
PANA design provides support for various types of deployments. Access
   networks can differ based on the availability of lower-layer
   security, placement of PANA entities, choice of client IP
   configuration and authentication methods, etc.  This I-D defines a
   general framework for describing how these various deployment choices
   are handled by PANA and the access network architectures.
   Additionally, two possible deployments are described in detail: using
   PANA over DSL networks and WLAN networks.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pana-framework-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pana-framework-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-7-20160250.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pana-framework-01.txt

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

Content-Type: text/plain
Content-ID: <2004-7-20160250.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana

--NextPart--





From pana-bounces@ietf.org  Wed Jul 21 10:27:57 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21872
	for <pana-archive@lists.ietf.org>; Wed, 21 Jul 2004 10:27:57 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnHvp-0002bA-6f; Wed, 21 Jul 2004 10:18:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnHk3-0004gG-T2
	for pana@megatron.ietf.org; Wed, 21 Jul 2004 10:06:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18886
	for <pana@ietf.org>; Wed, 21 Jul 2004 10:06:41 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnHkL-0003DD-Hk
	for pana@ietf.org; Wed, 21 Jul 2004 10:07:06 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6LE6Wlr014466;
	Wed, 21 Jul 2004 23:06:32 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6LE6W1v023522;
	Wed, 21 Jul 2004 23:06:32 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	ZAA23519 ; Wed, 21 Jul 2004 23:06:32 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id XAA06501; Wed, 21 Jul 2004 23:06:31 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id XAA18461;
	Wed, 21 Jul 2004 23:06:30 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6LE6UFi009699;
	Wed, 21 Jul 2004 23:06:30 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I17003ITGIR7L@tsbpo1.po.toshiba.co.jp>; Wed,
	21 Jul 2004 23:06:29 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BnHjK-0002vo-00; Wed, 21 Jul 2004 07:05:58 -0700
Date: Wed, 21 Jul 2004 10:05:58 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org, eap@frascone.com
Message-id: <20040721140558.GI1086@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org, eap@frascone.com
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Subject: [Pana] PANA IPv6 implementation available
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

http://www.opendiameter.org and
http://www.sourceforge.net/projects/diameter have more details.

Also, if you are implementing PANA and interested in PANA
interoperability testing, please send email to me.

Yoshihiro Ohba (Open Diameter Project)

----- Forwarded message from Victor Fajardo <vfajardo@mailsnare.net> -----

From: Victor Fajardo <vfajardo@mailsnare.net>
Subject: [Diameter-developers] Open Diameter Interim Release Version 1.0.7-a is
 now available
To: diameter-developers@lists.sourceforge.net
Reply-to: vfajardo@msbx.net
Importance: Normal
Sensitivity: Normal
X-VirusChecked: Checked
X-Env-Sender: diameter-developers-admin@lists.sourceforge.net
X-Msg-Ref: server-2.tower-75.messagelabs.com!1090252954!2771397
X-StarScan-Version: 5.2.10; banners=-,-,-
X-Originating-IP: [66.35.250.206]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-Virus-Scanned: by Clam AntiVirus
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net. See
 http://spamassassin.org/tag/ for more details. Report problems to
 http://sf.net/tracker/?func=add&group_id=1&atid=200001 0.0 SF_CHICKENPOX_SLASH
    BODY: Text interparsed with / 0.0 SF_CHICKENPOX_MINUS    BODY: Text
 interparsed with - 0.0 SF_CHICKENPOX_PERIOD   BODY: Text interparsed with .
 0.0 SF_CHICKENPOX_UNDERSCORE BODY: Text interparsed with _
X-BeenThere: diameter-developers@lists.sourceforge.net
X-Mailman-Version: 2.0.9-sf.net
List-Unsubscribe:
 <https://lists.sourceforge.net/lists/listinfo/diameter-developers>,
 <mailto:diameter-developers-request@lists.sourceforge.net?subject=unsubscribe>
List-Id: Diameter Developers Mailing List
 <diameter-developers.lists.sourceforge.net>
List-Post: <mailto:diameter-developers@lists.sourceforge.net>
List-Help:
 <mailto:diameter-developers-request@lists.sourceforge.net?subject=help>
List-Subscribe:
 <https://lists.sourceforge.net/lists/listinfo/diameter-developers>,
 <mailto:diameter-developers-request@lists.sourceforge.net?subject=subscribe>
List-Archive:
 <http://sourceforge.net/mailarchive/forum.php?forum=diameter-developers>
X-Original-Date: Mon, 19 Jul 2004 15:59:47 +0000

Release Version 1.0.7-a
Release Date : 07/19/2004

This release is an interim release for version 1.0.7. It is in support of incremental features that are ready for distribution and also covers critical fixes from the last major release.

1. PANA IPv6 Support

PANA now supports IPv6 for FreeBSD and Linux platforms only. PANA/IPv6 has been tested with FreeBSD 4.9 and above. For linux platforms, the kernel must support IPv6 (vanilla kernel or usagi) and must have a glibc version that supports IPv6 socket interface extensions (RFC 3493) and advanced socket API (RFC 2292) including BSD functions, i.e. getifaddrs(3). To compile libpana with IPv6, the ACE package must also be compiled with IPv6 support (enable ACE_HAS_IPV6 macro in config.h). The ACE-INSTALL document provides more details on enabling IPv6 support. The PANA library relies on this macro as well. There is also a sample IPv6 config file present in pana/config directory for both the Pac test code (pac6.xml) and Paa test code (paa6.xml).

2. Bug Fixes

The following are major fixes introduced in this iterim release:

a. Fixed a race condition in the PANA statmachine event function.
b. Added race condition protection in the diameter state machine protection.
c. Fixes to diameter header vendor specific flag checks in libdiamparser.
d. Fixes to diameter base protocol message initialization routines.

3. Distribution Fixes for Release 1.0.7

The 1.0.7 distribution file (opendiameter-1.0.7.tar.gz) should have included EAP-TLS library but it does not. This interim releases fixes this issue and includes sources for EAP-TLS library.








-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id040&op=click
_______________________________________________
Diameter-developers mailing list
Diameter-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/diameter-developers

----- End forwarded message -----

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 22 18:17:19 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17562
	for <pana-archive@lists.ietf.org>; Thu, 22 Jul 2004 18:17:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnjp1-0001hD-Ha; Thu, 22 Jul 2004 16:05:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnjY8-00029L-Jc; Thu, 22 Jul 2004 15:48:16 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20911;
	Thu, 22 Jul 2004 15:48:14 -0400 (EDT)
Message-Id: <200407221948.PAA20911@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 22 Jul 2004 15:48:14 -0400
Cc: pana@ietf.org
Subject: [Pana] I-D ACTION:draft-ietf-pana-snmp-01.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

--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		: SNMP usage for PAA-2-EP interface
	Author(s)	: Y. Mghazli, et al. 
	Filename	: draft-ietf-pana-snmp-01.txt
	Pages		: 36
	Date		: 2004-7-22
	
The PANA Authentication Agent (PAA) does not necessarily act as an
   Enforcement Point (EP) to prevent unauthorized access or usage of the
   network. When a PANA Client (PaC) successfully authenticates itself
   to the PAA, EP(s) (e.g., access routers) will need to be suitably
   notified. The PANA working group mandates the use of Simple Network
   Management Protocol (SNMP) to deliver the authorization information
   to one or more EPs when the PAA is separated from EPs.

   The present document provides the necessary information and
   extensions needed to use SNMP as the PAA-2-EP protocol.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pana-snmp-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pana-snmp-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-7-22145643.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pana-snmp-01.txt

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

Content-Type: text/plain
Content-ID: <2004-7-22145643.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana

--NextPart--





From pana-bounces@ietf.org  Thu Jul 22 19:20:23 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28215
	for <pana-archive@lists.ietf.org>; Thu, 22 Jul 2004 19:20:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnmYA-0006WN-Mr; Thu, 22 Jul 2004 19:00:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnkr2-0003qY-IU
	for pana@megatron.ietf.org; Thu, 22 Jul 2004 17:11:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04788
	for <pana@ietf.org>; Thu, 22 Jul 2004 17:11:50 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bnkrc-0003kE-IY
	for pana@ietf.org; Thu, 22 Jul 2004 17:12:32 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I1900M01UURJP@mailout3.samsung.com> for pana@ietf.org; Fri,
	23 Jul 2004 06:11:15 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I1900KBWUUQEC@mailout3.samsung.com> for pana@ietf.org;
	Fri, 23 Jul 2004 06:11:15 +0900 (KST)
Received: from Alperyegin ([105.144.29.156])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I1900MW8UUOBL@mmp1.samsung.com> for
	pana@ietf.org; Fri, 23 Jul 2004 06:11:14 +0900 (KST)
Date: Thu, 22 Jul 2004 14:11:12 -0700
From: Alper Yegin <alper.yegin@samsung.com>
In-reply-to: <02fb01c46dd5$d11bfaf0$6401a8c0@sisa.samsung.com>
To: pana@ietf.org
Message-id: <00e201c47030$6bae1b50$9c1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7BIT
Cc: "'Thomas Narten'" <narten@us.ibm.com>
Subject: [Pana] Final agenda for PANA meeting at IETF 60
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


Protocol for Carrying Authentication for Network Access WG (pana)

Monday, August 2 at 1530-1730
============================

CHAIRS: Basavaraj Patil <Basavaraj.Patil@nokia.com>
        Alper Yegin <alper@samsung.com>


AGENDA:

1. Preliminaries (bluesheets, minute takers, agenda bashing, document
   status) : 5 min, Chairs


2. PANA protocol update and open issues: 30 min, Alper Yegin

   Discussion of recently closed and currently open issues on 
   draft-ietf-pana-pana-05.txt. See "Change History" section of the 
   draft for the list of issues closed in this revision. Additional 
   issues may be discussed on the mailing list prior to the meeting. 
   Detailed issue descriptions can be found at 
   http://danforsberg.info:8080/pana-issues/


3. PANA framework update and open issues: 5 min, Yoshihiro Ohba

   Discussion of recently closed and currently open issues on 
   draft-ietf-pana-framework-01.txt. 


4. SNMP usage for PAA-2-EP interface: 5 min, Yacine El Mghazli

   Discussion of recently closed and currently open issues on 
   draft-ietf-pana-snmp-01.txt.


5. PANA-IPsec I-D update and open issues: 5 min, Mohan Parthasarathy

   Discussion of recently closed and currently open issues on 
   draft-ietf-pana-ipsec-03.txt.   


6. PANA state machine: 20 min, Victor Fajardo

   New I-D presentation for draft-ohba-pana-statemachine-00.txt.


7. Context transfer for PANA: 20 min, Julien Bournelle

   New I-D presentation for draft-bournelle-pana-ctp-00.txt.


8. Next steps: 5 min, Chairs




_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 22 21:09:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06046
	for <pana-archive@lists.ietf.org>; Thu, 22 Jul 2004 21:09:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BnoOX-0002Rt-ST; Thu, 22 Jul 2004 20:58:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnoG4-0005YG-G2
	for pana@megatron.ietf.org; Thu, 22 Jul 2004 20:49:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04719
	for <pana@ietf.org>; Thu, 22 Jul 2004 20:49:54 -0400 (EDT)
Received: from omr4.netsolmail.com ([216.168.230.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnoGi-0002ur-IS
	for pana@ietf.org; Thu, 22 Jul 2004 20:50:37 -0400
Received: from ms4.netsolmail.com (IDENT:mirapoint@[216.168.230.177])
	by omr4.netsolmail.com (8.12.10/8.12.10) with ESMTP id i6N0sPh8027850; 
	Thu, 22 Jul 2004 20:54:25 -0400 (EDT)
Received: from [10.13.3.22] (fw-1.peerless.com [208.152.94.2])
	by ms4.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA)
	with ESMTP id BSR92879; Thu, 22 Jul 2004 20:49:51 -0400 (EDT)
User-Agent: Microsoft-Entourage/11.0.0.040405
Date: Thu, 22 Jul 2004 17:49:29 -0700
Subject: Re: [Pana] Final agenda for PANA meeting at IETF 60
From: Randy Turner <rturner@amalfisystems.com>
To: Alper Yegin <alper.yegin@samsung.com>, <pana@ietf.org>
Message-ID: <BD25AEA9.1DCC%rturner@amalfisystems.com>
In-Reply-To: <00e201c47030$6bae1b50$9c1d9069@sisa.samsung.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: 7bit
Cc: "'Thomas Narten'" <narten@us.ibm.com>
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit



Hi Alper,

On the mailing list, I mentioned that we could discuss some deployment
issues for broadband services and business models that are evolving and see
if PANA can address these scenarios or would modifications be necessary.

Would there be time to discuss this during the formal session, or
alternatively, interested parties could discuss this in San Diego, outside
of a formal session?

Thanks,
Randy

> From: Alper Yegin <alper.yegin@samsung.com>
> Date: Thu, 22 Jul 2004 14:11:12 -0700
> To: <pana@ietf.org>
> Cc: 'Thomas Narten' <narten@us.ibm.com>
> Subject: [Pana] Final agenda for PANA meeting at IETF 60
> 
> 
> Protocol for Carrying Authentication for Network Access WG (pana)
> 
> Monday, August 2 at 1530-1730
> ============================
> 
> CHAIRS: Basavaraj Patil <Basavaraj.Patil@nokia.com>
>         Alper Yegin <alper@samsung.com>
> 
> 
> AGENDA:
> 
> 1. Preliminaries (bluesheets, minute takers, agenda bashing, document
>    status) : 5 min, Chairs
> 
> 
> 2. PANA protocol update and open issues: 30 min, Alper Yegin
> 
>    Discussion of recently closed and currently open issues on
>    draft-ietf-pana-pana-05.txt. See "Change History" section of the
>    draft for the list of issues closed in this revision. Additional
>    issues may be discussed on the mailing list prior to the meeting.
>    Detailed issue descriptions can be found at
>    http://danforsberg.info:8080/pana-issues/
> 
> 
> 3. PANA framework update and open issues: 5 min, Yoshihiro Ohba
> 
>    Discussion of recently closed and currently open issues on
>    draft-ietf-pana-framework-01.txt.
> 
> 
> 4. SNMP usage for PAA-2-EP interface: 5 min, Yacine El Mghazli
> 
>    Discussion of recently closed and currently open issues on
>    draft-ietf-pana-snmp-01.txt.
> 
> 
> 5. PANA-IPsec I-D update and open issues: 5 min, Mohan Parthasarathy
> 
>    Discussion of recently closed and currently open issues on
>    draft-ietf-pana-ipsec-03.txt.
> 
> 
> 6. PANA state machine: 20 min, Victor Fajardo
> 
>    New I-D presentation for draft-ohba-pana-statemachine-00.txt.
> 
> 
> 7. Context transfer for PANA: 20 min, Julien Bournelle
> 
>    New I-D presentation for draft-bournelle-pana-ctp-00.txt.
> 
> 
> 8. Next steps: 5 min, Chairs
> 
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 22 21:29:47 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07322
	for <pana-archive@lists.ietf.org>; Thu, 22 Jul 2004 21:29:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnonj-0006Zv-Qc; Thu, 22 Jul 2004 21:24:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnoYQ-00087a-2u
	for pana@megatron.ietf.org; Thu, 22 Jul 2004 21:08:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06038
	for <pana@ietf.org>; Thu, 22 Jul 2004 21:08:52 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnoZ2-00039U-6O
	for pana@ietf.org; Thu, 22 Jul 2004 21:09:35 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I1A00AOL5TTT3@mailout3.samsung.com> for pana@ietf.org; Fri,
	23 Jul 2004 10:08:17 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I1A0045O5RG9W@mailout3.samsung.com> for pana@ietf.org;
	Fri, 23 Jul 2004 10:06:52 +0900 (KST)
Received: from Alperyegin ([105.144.29.156])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I1A00BT85RDF7@mmp1.samsung.com> for
	pana@ietf.org; Fri, 23 Jul 2004 10:06:52 +0900 (KST)
Date: Thu, 22 Jul 2004 18:06:49 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Final agenda for PANA meeting at IETF 60
In-reply-to: <BD25AEA9.1DCC%rturner@amalfisystems.com>
To: "'Randy Turner'" <rturner@amalfisystems.com>, pana@ietf.org
Message-id: <023101c47051$56869920$9c1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Content-Transfer-Encoding: 7BIT
Cc: "'Thomas Narten'" <narten@us.ibm.com>
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Hi Randy,

I somehow thought you were referring to discussing it at a hallway
meeting or something. 

I think the best way is to initiate the discussion on the mailing list
first, and see what we can carry over to the meeting. Can you please
start a thread on that?

Alper




> -----Original Message-----
> From: Randy Turner [mailto:rturner@amalfisystems.com]
> Sent: Thursday, July 22, 2004 5:49 PM
> To: Alper Yegin; pana@ietf.org
> Cc: 'Thomas Narten'
> Subject: Re: [Pana] Final agenda for PANA meeting at IETF 60
> 
> 
> 
> Hi Alper,
> 
> On the mailing list, I mentioned that we could discuss some deployment
> issues for broadband services and business models that are evolving
and
> see
> if PANA can address these scenarios or would modifications be
necessary.
> 
> Would there be time to discuss this during the formal session, or
> alternatively, interested parties could discuss this in San Diego,
outside
> of a formal session?
> 
> Thanks,
> Randy
> 
> > From: Alper Yegin <alper.yegin@samsung.com>
> > Date: Thu, 22 Jul 2004 14:11:12 -0700
> > To: <pana@ietf.org>
> > Cc: 'Thomas Narten' <narten@us.ibm.com>
> > Subject: [Pana] Final agenda for PANA meeting at IETF 60
> >
> >
> > Protocol for Carrying Authentication for Network Access WG (pana)
> >
> > Monday, August 2 at 1530-1730
> > ============================
> >
> > CHAIRS: Basavaraj Patil <Basavaraj.Patil@nokia.com>
> >         Alper Yegin <alper@samsung.com>
> >
> >
> > AGENDA:
> >
> > 1. Preliminaries (bluesheets, minute takers, agenda bashing,
document
> >    status) : 5 min, Chairs
> >
> >
> > 2. PANA protocol update and open issues: 30 min, Alper Yegin
> >
> >    Discussion of recently closed and currently open issues on
> >    draft-ietf-pana-pana-05.txt. See "Change History" section of the
> >    draft for the list of issues closed in this revision. Additional
> >    issues may be discussed on the mailing list prior to the meeting.
> >    Detailed issue descriptions can be found at
> >    http://danforsberg.info:8080/pana-issues/
> >
> >
> > 3. PANA framework update and open issues: 5 min, Yoshihiro Ohba
> >
> >    Discussion of recently closed and currently open issues on
> >    draft-ietf-pana-framework-01.txt.
> >
> >
> > 4. SNMP usage for PAA-2-EP interface: 5 min, Yacine El Mghazli
> >
> >    Discussion of recently closed and currently open issues on
> >    draft-ietf-pana-snmp-01.txt.
> >
> >
> > 5. PANA-IPsec I-D update and open issues: 5 min, Mohan Parthasarathy
> >
> >    Discussion of recently closed and currently open issues on
> >    draft-ietf-pana-ipsec-03.txt.
> >
> >
> > 6. PANA state machine: 20 min, Victor Fajardo
> >
> >    New I-D presentation for draft-ohba-pana-statemachine-00.txt.
> >
> >
> > 7. Context transfer for PANA: 20 min, Julien Bournelle
> >
> >    New I-D presentation for draft-bournelle-pana-ctp-00.txt.
> >
> >
> > 8. Next steps: 5 min, Chairs
> >
> >
> >
> >
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 22 21:33:16 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07510
	for <pana-archive@lists.ietf.org>; Thu, 22 Jul 2004 21:33:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnorp-0000qz-Me; Thu, 22 Jul 2004 21:28:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BnohL-0002cm-81
	for pana@megatron.ietf.org; Thu, 22 Jul 2004 21:18:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06564
	for <pana@ietf.org>; Thu, 22 Jul 2004 21:18:04 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bnohz-0003Fu-5v
	for pana@ietf.org; Thu, 22 Jul 2004 21:18:48 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I1A007536995A@mailout2.samsung.com> for pana@ietf.org; Fri,
	23 Jul 2004 10:17:33 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I1A00ABB685G0@mailout2.samsung.com> for pana@ietf.org;
	Fri, 23 Jul 2004 10:16:53 +0900 (KST)
Received: from Alperyegin ([105.144.29.156])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I1A00B8R683F7@mmp1.samsung.com> for
	pana@ietf.org; Fri, 23 Jul 2004 10:16:53 +0900 (KST)
Date: Thu, 22 Jul 2004 18:16:51 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <023201c47052$bcaead90$9c1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7BIT
Subject: [Pana] comments draft-ohba-pana-statemachine-00
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

Hello,

I read draft-ohba-pana-statemachine-00, and it looks good. 

It'd be useful to have some state machine diagrams on the web, and
provide links to them in the I-D. That'd help readers follow what is
going on.

Some messages in the I-D are not matching the latest pana-pana spec.
Like PAUR and PAUA are PUR and PUA. Also device ID update does not
exist.

On page 21:

   Rx:PBR &&                alt_reject();              WAIT_EAP_RESULT
   1ST_EAP==Success &&
   PBR.RESULT_CODE==
   PANA_SUCCESS &&
   !PBR.exist_avp
   ("EAP-Payload"); 

I couldn't understand what scenario this is for...

Page 35:

   EAP_FAILURE &&           1ST_EAP=Failure            WAIT_PFEA
   1ST_EAP==Unset &&        PBR.insert_avp
                            ^^^^^^^^^^^^^^
 I think this should be PFER.insert_avp

   SEPARATE==Set &&         ("EAP-Payload");
   ABORT_ON_1ST_EAP_FAILURE if (key_available())
   ==Unset                    PFER.insert_avp("MAC");
                            PFER.S_flag=1;
                            if (NAP_AUTH)
                              PFER.N_flag=1;
                            Tx:PFER();
                            RtxTimerStart();


In 8.2:

	may come in the form of an SNMP conversations between PANA and
EP as

This should read "between PAA and EP".

Alper




_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 22 22:37:18 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22031
	for <pana-archive@lists.ietf.org>; Thu, 22 Jul 2004 22:37:18 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bnpsu-00070v-Hd; Thu, 22 Jul 2004 22:34:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bnpjh-0002Xv-AZ
	for pana@megatron.ietf.org; Thu, 22 Jul 2004 22:24:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21385
	for <pana@ietf.org>; Thu, 22 Jul 2004 22:24:34 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BnpkM-00042n-IR
	for pana@ietf.org; Thu, 22 Jul 2004 22:25:19 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6N2ORlr026988;
	Fri, 23 Jul 2004 11:24:27 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6N2OMJU003886;
	Fri, 23 Jul 2004 11:24:22 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	MAA03881 ; Fri, 23 Jul 2004 11:24:21 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id LAA29771; Fri, 23 Jul 2004 11:24:21 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id LAA06283;
	Fri, 23 Jul 2004 11:24:19 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6N2OIFi006514;
	Fri, 23 Jul 2004 11:24:18 +0900 (JST)
Received: from steelhead (iVPN01-098.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I1A0029Z9CFEE@tsbpo1.po.toshiba.co.jp>; Fri,
	23 Jul 2004 11:24:18 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bnpit-0005nM-00; Thu, 22 Jul 2004 19:23:47 -0700
Date: Thu, 22 Jul 2004 22:23:46 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] comments draft-ohba-pana-statemachine-00
In-reply-to: <023201c47052$bcaead90$9c1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040723022346.GI13267@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <023201c47052$bcaead90$9c1d9069@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Alper,

On Thu, Jul 22, 2004 at 06:16:51PM -0700, Alper Yegin wrote:
> Hello,
> 
> I read draft-ohba-pana-statemachine-00, and it looks good. 

Thank you very much for reading this draft.

> 
> It'd be useful to have some state machine diagrams on the web, and
> provide links to them in the I-D. That'd help readers follow what is
> going on.

I agree.  Rafa is now working on creating diagrams and hopefully they
will be available on the web soon.

> 
> Some messages in the I-D are not matching the latest pana-pana spec.
> Like PAUR and PAUA are PUR and PUA. Also device ID update does not
> exist.

Right.  We will fix them.

> 
> On page 21:
> 
>    Rx:PBR &&                alt_reject();              WAIT_EAP_RESULT
>    1ST_EAP==Success &&
>    PBR.RESULT_CODE==
>    PANA_SUCCESS &&
>    !PBR.exist_avp
>    ("EAP-Payload"); 
> 
> I couldn't understand what scenario this is for...

This case can happen in the following situation:

- NAP and ISP separate authentications are performed, and the first
EAP authentication succeeds.  (i.e., 1ST_EAP==Success)

- For the second EAP authentication, the PAA runs with EAP Full
Authenticator.  The second EAP authentication fails due to timeout
(i.e., the EAP Full Authenticator state machine enters TIMEOUT_FAILURE
or TIMEOUT_FAILURE2 sink state).  This does not generate an EAP
Failure message. (i.e., !PBR.exist_avp("EAP-Payload");).

- Assume that the PAA's policy is to allow network access for the PaC
unless both of two EAP authentications fail, the PAA returns a PBR
with a result code that indicates success (i.e.,
PBR.RESULT_CODE==PANA_SUCCESS).

> 
> Page 35:
> 
>    EAP_FAILURE &&           1ST_EAP=Failure            WAIT_PFEA
>    1ST_EAP==Unset &&        PBR.insert_avp
>                             ^^^^^^^^^^^^^^
>  I think this should be PFER.insert_avp

Right.  We will fix this.

> 
>    SEPARATE==Set &&         ("EAP-Payload");
>    ABORT_ON_1ST_EAP_FAILURE if (key_available())
>    ==Unset                    PFER.insert_avp("MAC");
>                             PFER.S_flag=1;
>                             if (NAP_AUTH)
>                               PFER.N_flag=1;
>                             Tx:PFER();
>                             RtxTimerStart();
> 
> 
> In 8.2:
> 
> 	may come in the form of an SNMP conversations between PANA and
> EP as
> 
> This should read "between PAA and EP".

We will fix this also.


Thanks again,

Yoshihiro Ohba


> 
> Alper
> 
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Fri Jul 23 17:32:52 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28628
	for <pana-archive@lists.ietf.org>; Fri, 23 Jul 2004 17:32:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bo7aV-0003VM-39; Fri, 23 Jul 2004 17:28:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bo7Nm-00017s-5Z
	for pana@megatron.ietf.org; Fri, 23 Jul 2004 17:15:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27719
	for <pana@ietf.org>; Fri, 23 Jul 2004 17:15:07 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bo7Oa-0006q0-HG
	for pana@ietf.org; Fri, 23 Jul 2004 17:16:02 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I1B00H04POBSY@mailout1.samsung.com> for pana@ietf.org; Sat,
	24 Jul 2004 06:14:35 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I1B005ZBPOAXI@mailout1.samsung.com> for pana@ietf.org;
	Sat, 24 Jul 2004 06:14:34 +0900 (KST)
Received: from Alperyegin ([105.144.29.156])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I1B008A0PO71N@mmp1.samsung.com> for
	pana@ietf.org; Sat, 24 Jul 2004 06:14:34 +0900 (KST)
Date: Fri, 23 Jul 2004 14:14:27 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <02ae01c470fa$0ac39020$9c1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92
Content-Transfer-Encoding: 7BIT
Cc: dbharrington@comcast.net, bwijnen@lucent.com
Subject: [Pana] FW: draft-ietf-pana-snmp-01.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


David Harrington's review feedback on the pana-snmp I-D...

Thank you David.

Alper

-----Original Message-----
From: David B Harrington [mailto:dbharrington@comcast.net] 
Sent: Thursday, July 22, 2004 7:46 PM
To: basavaraj.patil@nokia.com; alper.yegin@samsung.com
Cc: 'Wijnen, Bert (Bert)'
Subject: draft-ietf-pana-snmp-01.txt


Hi,

I have some comments on draft-ietf-pana-snmp-01.txt. Can you forward
to the pana mailing list?

I have not done a through review, but as SNMPv3 co-chair, I like to
check documents produced by WGs to see if they are planning to use
SNMPv3 as it was designed to be used. I have not looked closely at
whether the modules being reused are being used appropriately, whether
the design of mib tables and indices is appropriate, whether it meets
the mib review guidelines, and so on. 

It would be smart to ask Bert if he can get a MIB Doctor to act as
Technical Advisor for the WG, if the WG is going to use SNMPv3 for
secure configuration.

1) section 4.2.1, "SNMP enables the re-use of existing mibs, this is
detailed in Section 4." Since this statement is made in section 4, it
seems wrong.

"mibs" s/b "mib modules"

It is incorrect to say that SNMP enables the re-use of existing mibs. 

First, SNMP is a protocol used to transport mib module information;
the mib module is actually independent of the protocol, since the mib
can be used with any protocol that knows how to address and carry its
data. So it isn't SNMP that makes mib module re-use possible.

Second, while an existing mib module might be appropriately used to
manage a new technology, the management approach must fit the mib
module's design; It would be inappropriate to re-use an existing mib
module in a manner for which it was not designed. 

So, a better way to say this would be "PANA management can be modeled
in a way that is consistent with existing standard mib modules."

2) "With the use of SNMPv3 as the PAA-EP protocol, the polling and
notification models are supported by SNMP get and trap operations,
respectively." - "traps" should be "notifications".

3) "In general, the polling model is less scalable than the
notification model as the number of PaCs and/or EPs increases." 

I think this is debatable, depending to a degree on how you define
scalability. A product I worked on worked very well with large
networks using a polling model; when a telecomm customer tried to use
the product as an event-driven solution, sending all the information
from devices to the application using notifications, it hosed the
application; the application couldn't process all the data fast enough
because it was constantly being interrupted with new event reports,
and it never caught up. The event-driven approach wasn't scalable
because an SNMP receiver has no ability to control the flow, and the
agent has no way to know that the receiver can't process the events
fast enough; with the polling method, the application could control
the flow, and can see whether the agent has handled requests on a
timely basis. 

To help minimize the need to constantly poll devices looking to see if
anything has changed, the SNMP designers recommend using a
notification-directed polling approach. If an important change has
occurred, the device can notify the application that the change has
occurred, and the application can then poll the appropriate mib module
for the updated information. 

The notifications should be designed as part of a mib module to
identify which changes are important, and the mib module should also
have a "knob" to allow an operator to decide whether to enable the
notification, and whether to rate-limit it.

So I think it is inappropriate to say the polling model is less
scalable. That's merely an opinion and should not be part of a
standards specification.

4) The whole discussion of traps and unreliability is inappropriate
for an SNMPv3-based design. This is a problem from SNMPv1. SNMPv3
supports an Inform notification, for which there is a response
message.

5) "Thus, the notification model should be used for supporting this
type of authorization." Is this really required in the RFC2119
"SHOULD" sense? I don't think so, personally. It seems more like the
author's opinion of how to implement, not a standards requirement.

6) "This type of authorization" - should this be a new paragraph? It
seems to be a different topic than trap unreliability.

7) section 4.2.2 discusses various models of one-to-many relations. Is
section 4 supposed to be about the requirements for PANA, or a
discussion of how SNMP meets the requirement? If the requirement is
simply that the protocol used must support one-to-many relationships,
the whole first paragraph isn't needed here. SNMP supports
one-to-many, many-to-one, and many-to-many relationships.

If the requirements have not yet been identified in other PANA
documents, then it would be better to list the requirements in one
section, and then use a different section to show how SNMP meets the
requirement, referencing where the requirement is identified. If the
requirements are identified elsewhere, why not just reference the
requirement in the other document?

8) section 4.2.3 - would it be more succinct to say "SNMPv3 includes
the User-based Security Model (USM, [RFC3414]), which provides
authentication,
   confidentiality, and integrity."? I found the existing text
confusing since I couldn't tell what three standardized mechanisms
were being referenced.

"See Section 9" points to a section that should be listing sensitive
objects. It would probably be better to point the reader to RFC3410 or
the USM RFC if they want further details on the threats addressed.

9) 4.2.6 "shorter enough" s/b "short enough"

10) 5.3 - I'm concerned that this notification could be used to
overwhelm an SNMP application, thus creating a DoS attack on the
management of the network. A attacker could detect that such
traps/notifications are sent by multiple devices, and the attacker
could deliberately send lots of traffic through the devices.

11) pana802FilterVlanId - be aware that there are textual conventions
for vlanID and vlanindex that might be appropriate here. In addition,
the TCs may support cases that your syntax may not be able to support.
Bert Wijnen can advise you where to find the current TC.

12) I recommend using bullets to list the possible enumerations. As
written, it's a little bit harder to find the values one is looking
for, and then to parse the sentence it is contained in. This is obvous
not a big problem, but it does seem to improve ease-of-use.

13) did you consider using the SNMPConf work to provide policy based
mgmt? If not, why not?

14) pana802FiltRowStatus depends on the description in
pana802FilterType; wouldn't it be better to put the requirements in
one place? Would it be better to describe what process an application
should use to change the entry so applications know how to do it, and
agent implementers know how to implement support for the process
consistently? Failure to clearly specify this might result in
differnet vendors handling this in different ways, and applications
having to know how to do it multiple ways depending on which vendors'
equipment it is doing it to.

15) Once you've begun to identify the sensitive objects, it might be a
good idea to provide appropriate VACM view families for controlling
access. This will ensure that it will be possible to reasonably apply
access controls to the tables you design.

Hope this helps,

David Harrington
dbharrington@comcast.net
co-chair SNMPv3 WG, concluded



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 26 05:10:01 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10137
	for <pana-archive@lists.ietf.org>; Mon, 26 Jul 2004 05:10:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bp1TC-0003mT-Cx; Mon, 26 Jul 2004 05:08:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bp1QU-0003RM-VM
	for pana@megatron.ietf.org; Mon, 26 Jul 2004 05:05:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10027
	for <pana@ietf.org>; Mon, 26 Jul 2004 05:05:40 -0400 (EDT)
Received: from smail3.alcatel.fr ([64.208.49.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bp1Rr-0002VO-9n
	for pana@ietf.org; Mon, 26 Jul 2004 05:07:07 -0400
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr
	[155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id i6Q957VD024386;
	Mon, 26 Jul 2004 11:05:08 +0200
Received: from alcatel.fr ([172.25.72.141])
	by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
	with ESMTP id 2004072611050668:1654 ;
	Mon, 26 Jul 2004 11:05:06 +0200 
Message-ID: <4104C942.2080102@alcatel.fr>
Date: Mon, 26 Jul 2004 11:05:06 +0200
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.5) Gecko/20031007
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@samsung.com>
Subject: Re: [Pana] FW: draft-ietf-pana-snmp-01.txt
References: <02ae01c470fa$0ac39020$9c1d9069@sisa.samsung.com>
In-Reply-To: <02ae01c470fa$0ac39020$9c1d9069@sisa.samsung.com>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a
	|January 7, 2002) at 07/26/2004 11:05:06,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7,
	2002) at 07/26/2004 11:05:08,
	Serialize complete at 07/26/2004 11:05:08
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Alcanet-MTA-scanned-and-authorized: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 612a16ba5c5f570bfc42b3ac5606ac53
Content-Transfer-Encoding: 7bit
Cc: dbharrington@comcast.net, bwijnen@lucent.com, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit

thank you david for your review. indeed it does help. I think we agree 
on most of your comments.

* from a general point of view, a fair amount of your comments deal with 
text inherited from earlier discussion and docs we had on PANA framework 
issues (traps, pana reqs, etc.). thank you for pointing this out and I 
agree we need to clean this up in order to provide a coherent standards 
specification.

* a MIB doctor for PANA: good idea IMO. nethertheless, we should wait 
the MIB objects are in a more advanced stage to ask for this review. 
PANA decisions must be taken first (especially L2 support, see the open 
issues).

* concerning the non-choice of SNMPconf, I see 2 reasons for this (FYI):
- a "strategical" one: in order to promote its framework. PANA WG wants 
to stay as neutral as possible on this interface. smthg widely spread 
and readily re-usable is needed here. SNMPv3 is ok then.
- a technical one: PANA WG does not need a full policy suite, since 
PAA-EP cares about access control only.

* finally, for the remainning points, I think we agree on and I will 
personaly take care to integrate your proposals in the next iteration of 
the document and of course I'll keep you and the PANA WG informed.


thanks again,
yacine




Alper Yegin wrote:

> David Harrington's review feedback on the pana-snmp I-D...
> 
> Thank you David.
> 
> Alper
> 
> -----Original Message----- From: David B Harrington 
> [mailto:dbharrington@comcast.net] Sent: Thursday, July 22, 2004 7:46 
> PM To: basavaraj.patil@nokia.com; alper.yegin@samsung.com Cc: 
> 'Wijnen, Bert (Bert)' Subject: draft-ietf-pana-snmp-01.txt
> 
> 
> Hi,
> 
> I have some comments on draft-ietf-pana-snmp-01.txt. Can you forward
>  to the pana mailing list?
> 
> I have not done a through review, but as SNMPv3 co-chair, I like to 
> check documents produced by WGs to see if they are planning to use 
> SNMPv3 as it was designed to be used. I have not looked closely at 
> whether the modules being reused are being used appropriately, 
> whether the design of mib tables and indices is appropriate, whether 
> it meets the mib review guidelines, and so on.
> 
> It would be smart to ask Bert if he can get a MIB Doctor to act as 
> Technical Advisor for the WG, if the WG is going to use SNMPv3 for 
> secure configuration.
> 
> 1) section 4.2.1, "SNMP enables the re-use of existing mibs, this is
>  detailed in Section 4." Since this statement is made in section 4,
> it seems wrong.
> 
> "mibs" s/b "mib modules"
> 
> It is incorrect to say that SNMP enables the re-use of existing mibs.
> 
> 
> 
> First, SNMP is a protocol used to transport mib module information; 
> the mib module is actually independent of the protocol, since the mib
>  can be used with any protocol that knows how to address and carry 
> its data. So it isn't SNMP that makes mib module re-use possible.
> 
> Second, while an existing mib module might be appropriately used to 
> manage a new technology, the management approach must fit the mib 
> module's design; It would be inappropriate to re-use an existing mib
>  module in a manner for which it was not designed.
> 
> So, a better way to say this would be "PANA management can be modeled
>  in a way that is consistent with existing standard mib modules."
> 
> 2) "With the use of SNMPv3 as the PAA-EP protocol, the polling and 
> notification models are supported by SNMP get and trap operations, 
> respectively." - "traps" should be "notifications".
> 
> 3) "In general, the polling model is less scalable than the 
> notification model as the number of PaCs and/or EPs increases."
> 
> I think this is debatable, depending to a degree on how you define 
> scalability. A product I worked on worked very well with large 
> networks using a polling model; when a telecomm customer tried to use
>  the product as an event-driven solution, sending all the information
>  from devices to the application using notifications, it hosed the 
> application; the application couldn't process all the data fast 
> enough because it was constantly being interrupted with new event 
> reports, and it never caught up. The event-driven approach wasn't 
> scalable because an SNMP receiver has no ability to control the flow,
>  and the agent has no way to know that the receiver can't process the
>  events fast enough; with the polling method, the application could 
> control the flow, and can see whether the agent has handled requests 
> on a timely basis.
> 
> To help minimize the need to constantly poll devices looking to see 
> if anything has changed, the SNMP designers recommend using a 
> notification-directed polling approach. If an important change has 
> occurred, the device can notify the application that the change has 
> occurred, and the application can then poll the appropriate mib 
> module for the updated information.
> 
> The notifications should be designed as part of a mib module to 
> identify which changes are important, and the mib module should also
>  have a "knob" to allow an operator to decide whether to enable the 
> notification, and whether to rate-limit it.
> 
> So I think it is inappropriate to say the polling model is less 
> scalable. That's merely an opinion and should not be part of a 
> standards specification.
> 
> 4) The whole discussion of traps and unreliability is inappropriate 
> for an SNMPv3-based design. This is a problem from SNMPv1. SNMPv3 
> supports an Inform notification, for which there is a response 
> message.
> 
> 5) "Thus, the notification model should be used for supporting this 
> type of authorization." Is this really required in the RFC2119 
> "SHOULD" sense? I don't think so, personally. It seems more like the
>  author's opinion of how to implement, not a standards requirement.
> 
> 6) "This type of authorization" - should this be a new paragraph? It
>  seems to be a different topic than trap unreliability.
> 
> 7) section 4.2.2 discusses various models of one-to-many relations. 
> Is section 4 supposed to be about the requirements for PANA, or a 
> discussion of how SNMP meets the requirement? If the requirement is 
> simply that the protocol used must support one-to-many relationships,
>  the whole first paragraph isn't needed here. SNMP supports 
> one-to-many, many-to-one, and many-to-many relationships.
> 
> If the requirements have not yet been identified in other PANA 
> documents, then it would be better to list the requirements in one 
> section, and then use a different section to show how SNMP meets the
>  requirement, referencing where the requirement is identified. If the
>  requirements are identified elsewhere, why not just reference the 
> requirement in the other document?
> 
> 8) section 4.2.3 - would it be more succinct to say "SNMPv3 includes
>  the User-based Security Model (USM, [RFC3414]), which provides 
> authentication, confidentiality, and integrity."? I found the 
> existing text confusing since I couldn't tell what three standardized
>  mechanisms were being referenced.
> 
> "See Section 9" points to a section that should be listing sensitive
>  objects. It would probably be better to point the reader to RFC3410 
> or the USM RFC if they want further details on the threats addressed.
> 
> 
> 
> 9) 4.2.6 "shorter enough" s/b "short enough"
> 
> 10) 5.3 - I'm concerned that this notification could be used to 
> overwhelm an SNMP application, thus creating a DoS attack on the 
> management of the network. A attacker could detect that such 
> traps/notifications are sent by multiple devices, and the attacker 
> could deliberately send lots of traffic through the devices.
> 
> 11) pana802FilterVlanId - be aware that there are textual conventions
>  for vlanID and vlanindex that might be appropriate here. In 
> addition, the TCs may support cases that your syntax may not be able 
> to support. Bert Wijnen can advise you where to find the current TC.
> 
> 12) I recommend using bullets to list the possible enumerations. As 
> written, it's a little bit harder to find the values one is looking 
> for, and then to parse the sentence it is contained in. This is 
> obvous not a big problem, but it does seem to improve ease-of-use.
> 
> 13) did you consider using the SNMPConf work to provide policy based
>  mgmt? If not, why not?
> 
> 14) pana802FiltRowStatus depends on the description in 
> pana802FilterType; wouldn't it be better to put the requirements in 
> one place? Would it be better to describe what process an application
>  should use to change the entry so applications know how to do it, 
> and agent implementers know how to implement support for the process
>  consistently? Failure to clearly specify this might result in 
> differnet vendors handling this in different ways, and applications 
> having to know how to do it multiple ways depending on which vendors'
>  equipment it is doing it to.
> 
> 15) Once you've begun to identify the sensitive objects, it might be 
> a good idea to provide appropriate VACM view families for controlling
>  access. This will ensure that it will be possible to reasonably 
> apply access controls to the tables you design.
> 
> Hope this helps,
> 
> David Harrington dbharrington@comcast.net co-chair SNMPv3 WG, 
> concluded
> 
> 
> 
> _______________________________________________ Pana mailing list 
> Pana@ietf.org https://www1.ietf.org/mailman/listinfo/pana
> 



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Mon Jul 26 18:07:03 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14168
	for <pana-archive@lists.ietf.org>; Mon, 26 Jul 2004 18:07:03 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BpDVU-0004Sc-W0; Mon, 26 Jul 2004 17:59:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BpDQ1-0003Gs-TO
	for pana@megatron.ietf.org; Mon, 26 Jul 2004 17:54:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12789
	for <pana@ietf.org>; Mon, 26 Jul 2004 17:53:58 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpDRU-0000XX-0j
	for pana@ietf.org; Mon, 26 Jul 2004 17:55:33 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I1H00308BH3RS@mailout2.samsung.com> for pana@ietf.org; Tue,
	27 Jul 2004 06:53:27 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I1H00DVVBH09I@mailout2.samsung.com> for pana@ietf.org;
	Tue, 27 Jul 2004 06:53:24 +0900 (KST)
Received: from Alperyegin ([105.144.29.156])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I1H0006QBGYW5@mmp1.samsung.com> for
	pana@ietf.org; Tue, 27 Jul 2004 06:53:24 +0900 (KST)
Date: Mon, 26 Jul 2004 14:53:18 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <00fa01c4735a$f6d0dab0$0a4afea9@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7BIT
Subject: [Pana] Comments on draft-bournelle-pana-ctp-00
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


Thanks to the pana-ctp authors for this contribution.
Here are my comments on this I-D.

First of all, the pana spec already has the hooks to support so-called
reactive handover (as outlined in 4.12 Mobility Handling). Unless there
is a bug in that section, that mode should not require any changes
(state machine, AVPs, etc) to the base pana spec. 

Predictive mode was not considered in the base spec. Hence enabling that
too is likely to require updates to the base spec. If we are going to
keep the predictive in scope, we'll need to evaluate its impact on the
base spec.

Others....:

- The CTP details refer to CT between ARs. Well, the PAA does not have
to be on ARs, and this mechanism should work fine even than.

- There are updates to the base spec. For example, ISN_* are not kept as
part of session state anymore.

- "   o  The PaC previous Care-of address."
We don't really have a CoA in the context of PANA.

Alper


 






_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 27 17:15:39 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13996
	for <pana-archive@lists.ietf.org>; Tue, 27 Jul 2004 17:15:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BpZCX-00033c-TE; Tue, 27 Jul 2004 17:09:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BpZ9d-0002kh-8B
	for pana@megatron.ietf.org; Tue, 27 Jul 2004 17:06:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13668
	for <pana@ietf.org>; Tue, 27 Jul 2004 17:06:31 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpZBI-00004y-0I
	for pana@ietf.org; Tue, 27 Jul 2004 17:08:17 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6RL6Rlr029690;
	Wed, 28 Jul 2004 06:06:27 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6RL6R6o014481;
	Wed, 28 Jul 2004 06:06:27 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	GAA14478 ; Wed, 28 Jul 2004 06:06:27 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA25580; Wed, 28 Jul 2004 06:06:26 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA12891;
	Wed, 28 Jul 2004 06:06:26 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6RL6Qtq023479;
	Wed, 28 Jul 2004 06:06:26 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I1J00IDY3YN5D@tsbpo1.po.toshiba.co.jp>; Wed,
	28 Jul 2004 06:06:25 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BpZ8Q-0008V1-00; Tue, 27 Jul 2004 14:05:18 -0700
Date: Tue, 27 Jul 2004 17:05:17 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] same name space...
In-reply-to: <034f01c46dd8$ce18c5b0$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040727210517.GH22879@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
References: <034f01c46dd8$ce18c5b0$6401a8c0@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Mon, Jul 19, 2004 at 02:38:58PM -0700, Alper Yegin wrote:
> The PANA specification says:
> 
> 6.5  AVPs in PANA
> 
>    Some of the used AVPs are defined in this document and some of them
>    are defined in other documents like [RFC3588].  PANA proposes to use
>    the same name space with [RFC3588].  For temporary allocation, PANA
>    uses AVP type numbers starting from 1024.
> 
> I'm not sure what exactly using the same name space means here. Does it
> mean what we should never use a DIAMETER AVP name as a PANA AVP name
> unless the specifics are exactly same as defined in RFC 3588?

The paragraph is trying to indicate that PANA AVP code and Diameter
AVP code share the same code space.  For example, a Diameter AVP of
AVP code X and a PANA AVP of the same AVP code X point to the same AVP
definition (also implying that they use the same AVP name).  On the
other hand, I think PANA AVP Code can have its own code space as we
already do for PANA message types: If PANA AVP code X and Diameter
AVP code Y has the same the definition in the AVP payload, then the
PANA speficiation can just indicate so.

What do you think?

Yoshihiro Ohba


> 
> Alper
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Tue Jul 27 17:24:51 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14467
	for <pana-archive@lists.ietf.org>; Tue, 27 Jul 2004 17:24:51 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BpZJ8-0003q0-3l; Tue, 27 Jul 2004 17:16:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BpZEb-0003GQ-Cr
	for pana@megatron.ietf.org; Tue, 27 Jul 2004 17:11:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13868
	for <pana@ietf.org>; Tue, 27 Jul 2004 17:11:39 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpZGG-00009I-CW
	for pana@ietf.org; Tue, 27 Jul 2004 17:13:26 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6RLBclr001591;
	Wed, 28 Jul 2004 06:11:38 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6RLBbMS016185;
	Wed, 28 Jul 2004 06:11:37 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	GAA16180 ; Wed, 28 Jul 2004 06:11:37 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA26676; Wed, 28 Jul 2004 06:11:37 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA19536;
	Wed, 28 Jul 2004 06:11:36 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6RLBatq025916;
	Wed, 28 Jul 2004 06:11:36 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I1J00IH24795D@tsbpo1.po.toshiba.co.jp>; Wed,
	28 Jul 2004 06:11:35 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BpZDu-00005Z-00; Tue, 27 Jul 2004 14:10:58 -0700
Date: Tue, 27 Jul 2004 17:10:58 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040727211058.GI22879@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.6+20040523i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: [Pana] comments on issue 108
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

On Issue108: Session migration from one interface to another:

It is not a rare case that a device with multiple interfaces switches
from one interface to another.  This case actually frequently happens
to me.  I use a note PC that has a wired Ethernet interface and a
Wi-Fi interface.  While I am working in my office in a building, I
connect to a subnet from the wired Ethernet interface because wired
Ethernet is physically more stable than Wi-Fi.  When I have a meeting
in a nearby conference room in the same building, I remove the
Ethernet cable from the PC, bring the PC to the conference room and
connect to the same subnet through the Wi-Fi interface (there is no
wired Ethernet facility in the conference room).

For simplicity, let me assume MAC address is used as device-id.  There
are three ways for how to deal with this case in PANA (the same
discussion applies to the case where IP address is used as device id):

Method A: Start PANA from scratch when interface switching occurs.  Of
course PANA already supports this method.  However, this requires EAP
authentication when interface switching occurs.

Method B: Utilize PANA mobility optimization when interface switching
occurs.  The PaC performs PANA mobility optimization but with changing
the MAC address, i.e., PANA mobility optimization is performed by
using the MAC address assigned to the interface used after the
interface switching.  The current PANA specification does not prohibit
(and does not explicitly support) this method.

Method C: Use PANA-Update-Request/Answer exchange to update the device
identifier.  This is not supported in the current PANA specification.
This is more optimized but there might be some security issue since
this does not change the AAA-Key after the MAC address change.

The issues would be:

- Whether we should explicitly mention Method B in the current
specification or not.  My opinion is having some explicit text on
interface switching might be useful.

- Whether PANA should support Method C.  My opinion is PANA should not
support Method C unless we are sure there is no security issue in
Method C.


Regards,

Yoshihiro Ohba

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 28 22:06:23 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22668
	for <pana-archive@lists.ietf.org>; Wed, 28 Jul 2004 22:06:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bq0GH-0003HV-84; Wed, 28 Jul 2004 22:03:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bq0E8-0002ob-Mc
	for pana@megatron.ietf.org; Wed, 28 Jul 2004 22:01:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22514
	for <pana@ietf.org>; Wed, 28 Jul 2004 22:00:58 -0400 (EDT)
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bq0G4-0003Dg-7R
	for pana@ietf.org; Wed, 28 Jul 2004 22:03:00 -0400
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 82C2A2FDF1;
	Thu, 29 Jul 2004 04:00:23 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1Bq0CR-0001Qz-7K;
	Thu, 29 Jul 2004 03:59:15 +0200
Date: Thu, 29 Jul 2004 03:59:15 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Alper Yegin <alper.yegin@samsung.com>
Subject: Re: [Pana] Comments on draft-bournelle-pana-ctp-00
Message-ID: <20040729015915.GA5498@ipv6-5.int-evry.fr>
References: <00fa01c4735a$f6d0dab0$0a4afea9@sisa.samsung.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00fa01c4735a$f6d0dab0$0a4afea9@sisa.samsung.com>
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (score=-4.9, requis 4.5, autolearn=not spam,
	BAYES_00 -4.90)
X-MailScanner-From: jb@ipv6-5.int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi alper,

 thanks for your review, please see my comments inline.

On Mon, Jul 26, 2004 at 02:53:18PM -0700, Alper Yegin wrote:
> 
> First of all, the pana spec already has the hooks to support so-called
> reactive handover (as outlined in 4.12 Mobility Handling). Unless there
> is a bug in that section, that mode should not require any changes
> (state machine, AVPs, etc) to the base pana spec. 
> 
> Predictive mode was not considered in the base spec. Hence enabling that
> too is likely to require updates to the base spec. If we are going to
> keep the predictive in scope, we'll need to evaluate its impact on the
> base spec.

sure. I think that one of the main issue of our proposal is to know (as
outlined by gerardo) if we want to be totally compliant with CTP. Maybe
the best approach would be to keep PANA as it is (no modification of
state machine, AVPs etc. as you mentionned) and try to use CTP with
this.

> Others....:
> 
> - The CTP details refer to CT between ARs. Well, the PAA does not have
> to be on ARs, and this mechanism should work fine even than.

you're right

> 
> - There are updates to the base spec. For example, ISN_* are not kept as
> part of session state anymore.

ok, I'll correct this.

> - "   o  The PaC previous Care-of address."
> We don't really have a CoA in the context of PANA.

that's right, I'll also correct this.

> 
> Alper
> 
> 
>  
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 

-- 
julien.bournelle@int-evry.fr

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Wed Jul 28 23:05:13 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26479
	for <pana-archive@lists.ietf.org>; Wed, 28 Jul 2004 23:05:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bq1CG-0003wQ-02; Wed, 28 Jul 2004 23:03:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bq19I-0003UM-AV
	for pana@megatron.ietf.org; Wed, 28 Jul 2004 23:00:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26229
	for <pana@ietf.org>; Wed, 28 Jul 2004 23:00:01 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bq1BD-00044M-Gm
	for pana@ietf.org; Wed, 28 Jul 2004 23:02:04 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I1L00A08EZ6LO@mailout3.samsung.com> for pana@ietf.org; Thu,
	29 Jul 2004 11:59:30 +0900 (KST)
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I1L008B3EZ5GN@mailout3.samsung.com> for pana@ietf.org;
	Thu, 29 Jul 2004 11:59:29 +0900 (KST)
Received: from Alperyegin ([105.144.29.156])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I1L00CSTEZ36Y@mmp2.samsung.com> for
	pana@ietf.org; Thu, 29 Jul 2004 11:59:29 +0900 (KST)
Date: Wed, 28 Jul 2004 19:59:26 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] same name space...
In-reply-to: <20040727210517.GH22879@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <00a701c47518$106a18b0$9c1d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7BIT
Cc: Dan.Forsberg@nokia.com, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

> > 6.5  AVPs in PANA
> >
> >    Some of the used AVPs are defined in this document and some of
them
> >    are defined in other documents like [RFC3588].  PANA proposes to
use
> >    the same name space with [RFC3588].  For temporary allocation,
PANA
> >    uses AVP type numbers starting from 1024.
> >
> > I'm not sure what exactly using the same name space means here. Does
it
> > mean what we should never use a DIAMETER AVP name as a PANA AVP name
> > unless the specifics are exactly same as defined in RFC 3588?
> 
> The paragraph is trying to indicate that PANA AVP code and Diameter
> AVP code share the same code space.  For example, a Diameter AVP of
> AVP code X and a PANA AVP of the same AVP code X point to the same AVP
> definition (also implying that they use the same AVP name).  On the
> other hand, I think PANA AVP Code can have its own code space as we
> already do for PANA message types: If PANA AVP code X and Diameter
> AVP code Y has the same the definition in the AVP payload, then the
> PANA speficiation can just indicate so.
> 
> What do you think?

Actually we are not using the same code space anymore. (why the codes
are starting from 1024, I don't know...).

   AVP Code

      The AVP Code, combined with the Vendor-Id field, identifies the
      attribute uniquely.  AVP numbers are allocated by IANA [ianaweb].
      PANA uses its own address space for this field although some of
      the AVP formats are borrowed from Diameter protocol [RFC3588].

Alper



_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 29 00:09:42 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29154
	for <pana-archive@lists.ietf.org>; Thu, 29 Jul 2004 00:09:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bq28a-0002Mo-Ha; Thu, 29 Jul 2004 00:03:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bq24e-0001j9-Ky
	for pana@megatron.ietf.org; Wed, 28 Jul 2004 23:59:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28624
	for <pana@ietf.org>; Wed, 28 Jul 2004 23:59:17 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bq26a-0004xN-Ry
	for pana@ietf.org; Thu, 29 Jul 2004 00:01:21 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i6T3xClr002142;
	Thu, 29 Jul 2004 12:59:12 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i6T3xC2S003590;
	Thu, 29 Jul 2004 12:59:12 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	NAA03582 ; Thu, 29 Jul 2004 12:59:12 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id MAA07113; Thu, 29 Jul 2004 12:59:10 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id MAA29409;
	Thu, 29 Jul 2004 12:59:10 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i6T3x9tq000697;
	Thu, 29 Jul 2004 12:59:09 +0900 (JST)
Received: from steelhead (iVPN11-039.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I1L009LLHQJZ8@tsbpo1.po.toshiba.co.jp>; Thu,
	29 Jul 2004 12:59:08 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bq24F-0005jf-00; Wed, 28 Jul 2004 20:58:55 -0700
Date: Wed, 28 Jul 2004 23:58:55 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] same name space...
In-reply-to: <00a701c47518$106a18b0$9c1d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040729035855.GB20224@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper.yegin@samsung.com>,
	'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org,
	Dan.Forsberg@nokia.com
User-Agent: Mutt/1.5.6+20040523i
References: <20040727210517.GH22879@steelhead>
	<00a701c47518$106a18b0$9c1d9069@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hmm, then I think the specification can simply:

- remove the following sentense: "PANA proposes to use the same name
space with [RFC3588].  For temporary allocation, PANA uses AVP type
numbers starting from 1024." 

AND

- Renumber PANA AVP codes starting from 1.

Yoshihiro Ohba

On Wed, Jul 28, 2004 at 07:59:26PM -0700, Alper Yegin wrote:
> > > 6.5  AVPs in PANA
> > >
> > >    Some of the used AVPs are defined in this document and some of
> them
> > >    are defined in other documents like [RFC3588].  PANA proposes to
> use
> > >    the same name space with [RFC3588].  For temporary allocation,
> PANA
> > >    uses AVP type numbers starting from 1024.
> > >
> > > I'm not sure what exactly using the same name space means here. Does
> it
> > > mean what we should never use a DIAMETER AVP name as a PANA AVP name
> > > unless the specifics are exactly same as defined in RFC 3588?
> > 
> > The paragraph is trying to indicate that PANA AVP code and Diameter
> > AVP code share the same code space.  For example, a Diameter AVP of
> > AVP code X and a PANA AVP of the same AVP code X point to the same AVP
> > definition (also implying that they use the same AVP name).  On the
> > other hand, I think PANA AVP Code can have its own code space as we
> > already do for PANA message types: If PANA AVP code X and Diameter
> > AVP code Y has the same the definition in the AVP payload, then the
> > PANA speficiation can just indicate so.
> > 
> > What do you think?
> 
> Actually we are not using the same code space anymore. (why the codes
> are starting from 1024, I don't know...).
> 
>    AVP Code
> 
>       The AVP Code, combined with the Vendor-Id field, identifies the
>       attribute uniquely.  AVP numbers are allocated by IANA [ianaweb].
>       PANA uses its own address space for this field although some of
>       the AVP formats are borrowed from Diameter protocol [RFC3588].
> 
> Alper
> 
> 

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


From pana-bounces@ietf.org  Thu Jul 29 02:56:44 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20221
	for <pana-archive@lists.ietf.org>; Thu, 29 Jul 2004 02:56:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bq4m0-0001HE-Hd; Thu, 29 Jul 2004 02:52:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bq4hd-0000CA-He
	for pana@megatron.ietf.org; Thu, 29 Jul 2004 02:47:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19757
	for <pana@ietf.org>; Thu, 29 Jul 2004 02:47:43 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bq4ja-00079U-JI
	for pana@ietf.org; Thu, 29 Jul 2004 02:49:48 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I1L0075ZP6QYG@dns2.cselt.it> for pana@ietf.org; Thu,
	29 Jul 2004 08:40:02 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.0); Thu, 29 Jul 2004 08:45:00 +0200
Date: Thu, 29 Jul 2004 08:47:11 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Pana] Comments on draft-bournelle-pana-ctp-00
To: Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        Alper Yegin <alper.yegin@samsung.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C5708E7BE@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Pana] Comments on draft-bournelle-pana-ctp-00
Thread-Index: AcR1EPFyp16nk2siSkGcVMQjyEc/qwAJen/Q
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 29 Jul 2004 06:45:00.0078 (UTC)
	FILETIME=[91AB24E0:01C47537]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: quoted-printable
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Alper, Julien,

one more comment...


> > First of all, the pana spec already has the hooks to=20
> support so-called=20
> > reactive handover (as outlined in 4.12 Mobility Handling). Unless=20
> > there is a bug in that section, that mode should not require any=20
> > changes (state machine, AVPs, etc) to the base pana spec.
> >=20
> > Predictive mode was not considered in the base spec. Hence enabling=20
> > that too is likely to require updates to the base spec. If we are=20
> > going to keep the predictive in scope, we'll need to evaluate its=20
> > impact on the base spec.
>=20
> sure. I think that one of the main issue of our proposal is=20
> to know (as outlined by gerardo) if we want to be totally=20
> compliant with CTP. Maybe the best approach would be to keep=20
> PANA as it is (no modification of state machine, AVPs etc. as=20
> you mentionned) and try to use CTP with this.
>

I think the issue is that CTP was designed with MIPv6/FMIPv6 in mind.
This implies that some features are MIPv6-related (e.g. CoA, as Alper
noted). Thus, I think that the usage of CTP "as is" is not feasible in
our scenario (i.e. between two PAAs in order to transfer the PANA
context).

--Gerardo


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

_______________________________________________
Pana mailing list
Pana@ietf.org
https://www1.ietf.org/mailman/listinfo/pana


