From mailman-bounces@ietf.org  Sun Aug  1 06:16: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 GAA08547
	for <pana-archive@lists.ietf.org>; Sun, 1 Aug 2004 06:16: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 1BrCPf-0003Ai-Lw
	for pana-archive@lists.ietf.org; Sun, 01 Aug 2004 05:13:51 -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.11120.1091350991.10663.mailman@lists.ietf.org>
Date: Sun, 01 Aug 2004 05:03:11 -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  Sun Aug  1 11:03:45 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 LAA05218
	for <pana-archive@lists.ietf.org>; Sun, 1 Aug 2004 11:03:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BrHgg-0000dX-0S; Sun, 01 Aug 2004 10:51:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrHTb-00053M-VX
	for pana@megatron.ietf.org; Sun, 01 Aug 2004 10:38:16 -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 KAA03294
	for <pana@ietf.org>; Sun, 1 Aug 2004 10:38:14 -0400 (EDT)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrHWG-0003qW-GV
	for pana@ietf.org; Sun, 01 Aug 2004 10:41:01 -0400
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id i71Ebf0R020241; 
	Sun, 1 Aug 2004 07:37:42 -0700 (PDT)
Received: from localhost (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by bebop.France.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with SMTP id
	i71EbdJR004476; Sun, 1 Aug 2004 16:37:40 +0200 (MEST)
Date: Sun, 1 Aug 2004 07:38:05 -0700 (PDT)
From: Erik Nordmark <Erik.Nordmark@sun.com>
Subject: Re: [Pana] Issue 103: "PANA session" needs more clarification
To: Alper Yegin <alper.yegin@samsung.com>
In-Reply-To: "Your message with ID"
	<01aa01c46abb$46a98580$9b1d9069@sisa.samsung.com>
Message-ID: <Roam.SIMC.2.0.6.1091371085.14270.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Erik Nordmark <Erik.Nordmark@sun.com>
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

>    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. 

In the context of the mobility support, this presumably means that
the mobility support implies creating a new session (with a new session id)
by reusing information from an existing session.
Is that correct?

  Erik


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


From pana-bounces@ietf.org  Sun Aug  1 11:13: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 LAA05715
	for <pana-archive@lists.ietf.org>; Sun, 1 Aug 2004 11:13: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 1BrHmd-000326-6c; Sun, 01 Aug 2004 10:57:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrHan-0003LE-Tn
	for pana@megatron.ietf.org; Sun, 01 Aug 2004 10:45:42 -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 KAA03825
	for <pana@ietf.org>; Sun, 1 Aug 2004 10:45:40 -0400 (EDT)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrHdS-0003yV-LR
	for pana@ietf.org; Sun, 01 Aug 2004 10:48:28 -0400
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id i71Ej7J6010069; 
	Sun, 1 Aug 2004 07:45:08 -0700 (PDT)
Received: from localhost (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by bebop.France.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with SMTP id
	i71Ej5JR004604; Sun, 1 Aug 2004 16:45:06 +0200 (MEST)
Date: Sun, 1 Aug 2004 07:45:31 -0700 (PDT)
From: Erik Nordmark <Erik.Nordmark@sun.com>
Subject: Re: Issue 108 created (was Re: [Pana] issue85 (initial text))
To: Alper Yegin <alper.yegin@samsung.com>
In-Reply-To: "Your message with ID"
	<02c401c46b80$d2cc5950$9b1d9069@sisa.samsung.com>
Message-ID: <Roam.SIMC.2.0.6.1091371531.25254.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Erik Nordmark <Erik.Nordmark@sun.com>
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

> 108 Session migration from one interface to another

Isn't this just an aspect of the mobility support?

Question: does the mobility support assume that it is the same PAA
at the old and new attachment point?

If so, then all the mobility support needs to do is session migration
related to differences at the PaC end (different interfaces, different MAC
addresses?), and perhaps also deal with different EPs due to changing
the attachment point.

  Erik


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


From pana-bounces@ietf.org  Sun Aug  1 16:09: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 QAA21904
	for <pana-archive@lists.ietf.org>; Sun, 1 Aug 2004 16:09: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 1BrMbR-0000PS-4o; Sun, 01 Aug 2004 16:06:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrMZ7-0006vE-Tp
	for pana@megatron.ietf.org; Sun, 01 Aug 2004 16:04:17 -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 QAA21510
	for <pana@ietf.org>; Sun, 1 Aug 2004 16:04:15 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrMbp-00008g-Aw
	for pana@ietf.org; Sun, 01 Aug 2004 16:07:06 -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 <0I1S00A01AE2G4@mailout1.samsung.com> for pana@ietf.org; Mon,
	02 Aug 2004 05:03:38 +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 <0I1S001IUAE2OK@mailout1.samsung.com> for pana@ietf.org;
	Mon, 02 Aug 2004 05:03:38 +0900 (KST)
Received: from Alperyegin ([105.253.155.16])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I1S00LA4ADYOF@mmp2.samsung.com> for
	pana@ietf.org; Mon, 02 Aug 2004 05:03:37 +0900 (KST)
Date: Sun, 01 Aug 2004 13:03:33 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 103: "PANA session" needs more clarification
In-reply-to: <Roam.SIMC.2.0.6.1091371085.14270.nordmark@bebop.france>
To: "'Erik Nordmark'" <Erik.Nordmark@sun.com>
Message-id: <001201c47802$a15cfcb0$d4878182@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: 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

> >    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.
> 
> In the context of the mobility support, this presumably means that
> the mobility support implies creating a new session (with a new
session
> id)
> by reusing information from an existing session.
> Is that correct?

Yes.

Alper



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


From pana-bounces@ietf.org  Sun Aug  1 18:26: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 SAA28789
	for <pana-archive@lists.ietf.org>; Sun, 1 Aug 2004 18:26: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 1BrOfF-000202-3r; Sun, 01 Aug 2004 18:18:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BrOWm-0003nK-FL
	for pana@megatron.ietf.org; Sun, 01 Aug 2004 18:10: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 SAA27406
	for <pana@ietf.org>; Sun, 1 Aug 2004 18:09:57 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BrOZU-0001gu-Uj
	for pana@ietf.org; Sun, 01 Aug 2004 18:12:50 -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 <0I1S00L01G7P84@mailout2.samsung.com> for pana@ietf.org; Mon,
	02 Aug 2004 07:09: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 <0I1S007C4G7PGD@mailout2.samsung.com> for pana@ietf.org;
	Mon, 02 Aug 2004 07:09:25 +0900 (KST)
Received: from Alperyegin ([105.253.155.19])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I1S00MLJG7K8J@mmp2.samsung.com> for
	pana@ietf.org; Mon, 02 Aug 2004 07:09:25 +0900 (KST)
Date: Sun, 01 Aug 2004 15:09:19 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <000001c47814$340972d0$d4878182@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: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7BIT
Cc: "'Thomas Narten'" <narten@us.ibm.com>, margaret@thingmagic.com
Subject: [Pana] IMPORTANT: PANA meeting has moved
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


Due to AD schedule conflict, we had to move the PANA meeting to:

Wednesday, Aug 4, 13:00-15:00
Grand Ballroom C 

Sorry about this last minute change. Hopefully this won't impact
anyone's schedule.

- Chairs



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


From pana-bounces@ietf.org  Mon Aug  2 19:27: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 TAA14182
	for <pana-archive@lists.ietf.org>; Mon, 2 Aug 2004 19:27: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 1Brm4V-0000xo-0g; Mon, 02 Aug 2004 19:18:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Brls2-0003iK-U0
	for pana@megatron.ietf.org; Mon, 02 Aug 2004 19:05:30 -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 TAA13169
	for <pana@ietf.org>; Mon, 2 Aug 2004 19:05:28 -0400 (EDT)
From: Guy.Busschots@alcatel.be
Received: from smail.alcatel.fr ([62.23.212.165])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Brluz-0006S8-2a
	for pana@ietf.org; Mon, 02 Aug 2004 19:08:34 -0400
Received: from bemail01.netfr.alcatel.fr (bemail01.netfr.alcatel.fr
	[155.132.251.32])
	by smail.alcatel.fr (ALCANET/NETFR) with ESMTP id i72N09aI003451
	for <pana@ietf.org>; Tue, 3 Aug 2004 01:05:11 +0200
To: pana@ietf.org
Message-ID: <OFA4BDF06C.B1DA3C74-ONC1256EE4.007E706C-C1256EE4.007E706D@netfr.alcatel.fr>
Date: Tue, 3 Aug 2004 01:01:03 +0200
X-MIMETrack: Serialize by Router on BEMAIL01/BE/ALCATEL(Release 5.0.11 |July
	24, 2002) at 08/03/2004 01:05:11
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Alcanet-MTA-scanned-and-authorized: yes
X-Spam-Score: 0.3 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Subject: [Pana] Guy BUSSCHOTS/BE/ALCATEL is out of the office.
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 will be out of the office starting  02/08/2004 and will not return until
16/08/2004.


For Urgent matters Please Contact Peter Michiels

Gr,

Guy



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


From pana-bounces@ietf.org  Wed Aug  4 13:03: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 NAA19005
	for <pana-archive@lists.ietf.org>; Wed, 4 Aug 2004 13:03: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 1BsP3n-00064e-CP; Wed, 04 Aug 2004 12:56:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BsOt2-0002qX-42
	for pana@megatron.ietf.org; Wed, 04 Aug 2004 12:45:08 -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 MAA17548
	for <pana@ietf.org>; Wed, 4 Aug 2004 12:45:05 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BsOwK-0003DI-Q7
	for pana@ietf.org; Wed, 04 Aug 2004 12:48: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 <0I1X00B01L64OS@mailout3.samsung.com> for pana@ietf.org; Thu,
	05 Aug 2004 01:44:28 +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 <0I1X00K43L64Y4@mailout3.samsung.com> for pana@ietf.org;
	Thu, 05 Aug 2004 01:44:28 +0900 (KST)
Received: from Alperyegin ([105.253.155.26])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I1X00CDDL5ZAV@mmp1.samsung.com> for
	pana@ietf.org; Thu, 05 Aug 2004 01:44:27 +0900 (KST)
Date: Wed, 04 Aug 2004 09:44:23 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: Issue 108 created (was Re: [Pana] issue85 (initial text))
In-reply-to: <Roam.SIMC.2.0.6.1091371531.25254.nordmark@bebop.france>
To: "'Erik Nordmark'" <Erik.Nordmark@sun.com>
Message-id: <002101c47a42$4e7d4800$c3808182@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: 798b2e660f1819ae38035ac1d8d5e3ab
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

> > 108 Session migration from one interface to another
> 
> Isn't this just an aspect of the mobility support?

I think this can be implemented by using the existing mobility feature.

> Question: does the mobility support assume that it is the same PAA
> at the old and new attachment point?

No, it doesn't.

> If so, then all the mobility support needs to do is session migration
> related to differences at the PaC end (different interfaces, different
MAC
> addresses?), and perhaps also deal with different EPs due to changing
> the attachment point.

I think this should work.

Alper



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


From pana-bounces@ietf.org  Mon Aug  9 16:32: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 QAA12758
	for <pana-archive@lists.ietf.org>; Mon, 9 Aug 2004 16: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 1BuFt1-0004cB-GY; Mon, 09 Aug 2004 15:32:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuFn6-0002vd-Lc; Mon, 09 Aug 2004 15:26:40 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01720;
	Mon, 9 Aug 2004 15:26:38 -0400 (EDT)
Message-Id: <200408091926.PAA01720@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, 09 Aug 2004 15:26:38 -0400
Cc: pana@ietf.org
Subject: [Pana] I-D ACTION:draft-ietf-pana-threats-eval-07.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 and Network Access 
			  Threat Analysis and Security Requirements
	Author(s)	: M. Parthasarathy, et al.
	Filename	: draft-ietf-pana-threats-eval-07.txt
	Pages		: 17
	Date		: 2004-8-9
	
This document discusses the threats to protocols that are used to  
   carry authentication for network access. The security requirements  
   arising out of these threats will be used as additional input to the  
   PANA WG for designing the IP based network access authentication  
   protocol.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pana-threats-eval-07.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-threats-eval-07.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-threats-eval-07.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-8-9154847.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pana-threats-eval-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pana-threats-eval-07.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2004-8-9154847.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 Aug  9 21:01:25 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 VAA10919
	for <pana-archive@lists.ietf.org>; Mon, 9 Aug 2004 21:01:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BuKxR-0004UP-Vm; Mon, 09 Aug 2004 20:57:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BuKwY-0004IC-Kq
	for pana@megatron.ietf.org; Mon, 09 Aug 2004 20:56: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 UAA10528
	for <pana@ietf.org>; Mon, 9 Aug 2004 20:56:44 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BuL0y-00072m-9J
	for pana@ietf.org; Mon, 09 Aug 2004 21:01:21 -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 <0I2700H47H9I1O@mailout1.samsung.com> for pana@ietf.org; Tue,
	10 Aug 2004 09:56:07 +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 <0I2700E9UH9FDA@mailout1.samsung.com> for pana@ietf.org;
	Tue, 10 Aug 2004 09:56:04 +0900 (KST)
Received: from Alperyegin ([105.253.155.31])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I27004UIH9CXK@mmp2.samsung.com> for
	pana@ietf.org; Tue, 10 Aug 2004 09:56:03 +0900 (KST)
Date: Mon, 09 Aug 2004 17:56:02 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <01cd01c47e74$d0765aa0$60818182@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: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7BIT
Subject: [Pana] PANA over IP-in-IP tunnels
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


Can we run PANA over IP-in-IP tunnels as is, or do we need some
additional considerations for that? Consider the tunnel is established
prior to running PANA. PANA does not have anything to do with the
management of the tunnel, but simply takes it as a "link".

Alper
 





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


From pana-bounces@ietf.org  Fri Aug 13 19:34: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 TAA25555
	for <pana-archive@lists.ietf.org>; Fri, 13 Aug 2004 19:34: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 1BvlWh-0006Sv-Up; Fri, 13 Aug 2004 19:31:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvlWT-0006KL-CD
	for pana@megatron.ietf.org; Fri, 13 Aug 2004 19:31:45 -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 TAA25432
	for <pana@ietf.org>; Fri, 13 Aug 2004 19:31:42 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bvlbi-0001gq-BA
	for pana@ietf.org; Fri, 13 Aug 2004 19:37:11 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7DNValr024557;
	Sat, 14 Aug 2004 08:31:36 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7DNVaDp014436;
	Sat, 14 Aug 2004 08:31:36 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	JAA14435 ; Sat, 14 Aug 2004 08:31:36 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA24912; Sat, 14 Aug 2004 08:31:36 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA01828;
	Sat, 14 Aug 2004 08:31:34 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7DNVXtq029545;
	Sat, 14 Aug 2004 08:31: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 <0I2E002R5S0IZL@tsbpo1.po.toshiba.co.jp>; Sat,
	14 Aug 2004 08:31:33 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C1TY2-0003Ia-00; Sun, 29 Aug 2004 10:32:58 -0700
Date: Sun, 29 Aug 2004 13:32:58 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] PANA over IP-in-IP tunnels
In-reply-to: <01cd01c47e74$d0765aa0$60818182@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040829173258.GB12038@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+20040803i
References: <01cd01c47e74$d0765aa0$60818182@sisa.samsung.com>
X-Spam-Score: 2.4 (++)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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,

I think we can run PANA over an IP-in-IP tunnel as is, if the tunnel 
has been already established before running PANA over it.

I found in I-D tracker a comment from IESG with regard to
draft-ietf-pana-requirement-08.txt:

"
4.5.3 -- Please justify this requirement.  I can think of lots of
scenarios where it simply wouldn't hold, such as a large hotel or
conference center which permits free intranet access but demands
payment for most (but not all) external access.  Beyond that, what
about tunneled connections?  Are they permissible, given this
requirement?
"

I think we might clearly mention in the requirement draft that PANA
can run over IP-in-IP link.

Yoshihiro Ohba


On Mon, Aug 09, 2004 at 05:56:02PM -0700, Alper Yegin wrote:
> 
> Can we run PANA over IP-in-IP tunnels as is, or do we need some
> additional considerations for that? Consider the tunnel is established
> prior to running PANA. PANA does not have anything to do with the
> management of the tunnel, but simply takes it as a "link".
> 
> 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 Aug 13 20:41: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 UAA28376
	for <pana-archive@lists.ietf.org>; Fri, 13 Aug 2004 20:41: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 1BvmZW-0007uE-Nl; Fri, 13 Aug 2004 20:38:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BvmY1-0007lm-2C
	for pana@megatron.ietf.org; Fri, 13 Aug 2004 20:37:25 -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 UAA27927
	for <pana@ietf.org>; Fri, 13 Aug 2004 20:37:23 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BvmdG-0002UQ-Pd
	for pana@ietf.org; Fri, 13 Aug 2004 20:42:52 -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 <0I2E00J0LV1A35@mailout3.samsung.com> for pana@ietf.org; Sat,
	14 Aug 2004 09:36:46 +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 <0I2E00B72V0YFA@mailout3.samsung.com> for pana@ietf.org;
	Sat, 14 Aug 2004 09:36:34 +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 <0I2E001M4V0WDF@mmp2.samsung.com> for
	pana@ietf.org; Sat, 14 Aug 2004 09:36:34 +0900 (KST)
Date: Fri, 13 Aug 2004 17:36:31 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] PANA over IP-in-IP tunnels
In-reply-to: <20040829173258.GB12038@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <017f01c48196$bfdd5ed0$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-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
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,

> Hi Alper,
> 
> I think we can run PANA over an IP-in-IP tunnel as is, if the tunnel
> has been already established before running PANA over it.

What would be the DI? 

If there is a secure lower-layer channel (like physical security, or if
this is an IPsec tunnel), would we use the TOAs as the DIs? TOA is
equivalent to a link-layer address.

If there is no secure channel, one needs to be built based on IPsec. In
that case, the lower-layer addresses have no significance as DI in the
context of PANA.

> I found in I-D tracker a comment from IESG with regard to
> draft-ietf-pana-requirement-08.txt:
> 
> "
> 4.5.3 -- Please justify this requirement.  I can think of lots of
> scenarios where it simply wouldn't hold, such as a large hotel or
> conference center which permits free intranet access but demands
> payment for most (but not all) external access.  Beyond that, what
> about tunneled connections?  Are they permissible, given this
> requirement?
> "
> 
> I think we might clearly mention in the requirement draft that PANA
> can run over IP-in-IP link.

Yes, agreed.

Alper



> 
> Yoshihiro Ohba
> 
> 
> On Mon, Aug 09, 2004 at 05:56:02PM -0700, Alper Yegin wrote:
> >
> > Can we run PANA over IP-in-IP tunnels as is, or do we need some
> > additional considerations for that? Consider the tunnel is
established
> > prior to running PANA. PANA does not have anything to do with the
> > management of the tunnel, but simply takes it as a "link".
> >
> > 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  Sun Aug 15 20: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 UAA29705
	for <pana-archive@lists.ietf.org>; Sun, 15 Aug 2004 20: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 1BwVg9-0008Ed-DG; Sun, 15 Aug 2004 20:48:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BwVe7-0007xq-CE
	for pana@megatron.ietf.org; Sun, 15 Aug 2004 20:46: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 UAA29544
	for <pana@ietf.org>; Sun, 15 Aug 2004 20:46:41 -0400 (EDT)
Received: from smtp812.mail.sc5.yahoo.com ([66.163.170.82])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1BwVjm-0005Tp-Vn
	for pana@ietf.org; Sun, 15 Aug 2004 20:52:36 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.57.54 with
	login)
	by smtp812.mail.sc5.yahoo.com with SMTP; 16 Aug 2004 00:46:39 -0000
Message-ID: <011f01c4832a$7da6e050$6401a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Alper Yegin" <alper.yegin@samsung.com>, <pana@ietf.org>
References: <01cd01c47e74$d0765aa0$60818182@sisa.samsung.com>
Subject: Re: [Pana] PANA over IP-in-IP tunnels
Date: Sun, 15 Aug 2004 17:46:38 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
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

 
> 
> Can we run PANA over IP-in-IP tunnels as is, or do we need some
> additional considerations for that? Consider the tunnel is established
> prior to running PANA. PANA does not have anything to do with the
> management of the tunnel, but simply takes it as a "link".
> 
Though it is technically a single hop, it allows the PAA to be anywhere on
the internet. This means the attacker gets to consume all of the network resources (compared
to just a few devices if PAA is located on the edge) that is between the PaC and
the PAA. I don't remember all of the discussions on what prevented from PAA being
more than one hop away  i.e what are the dis-advantages of performing network access
authentication in the core ? Sure, hop count not being decremented in the tunnel still prevents
a few threats. 

-mohan

 
> 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  Mon Aug 16 02:40: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 CAA11716
	for <pana-archive@lists.ietf.org>; Mon, 16 Aug 2004 02:40: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 1Bwb8U-0001o3-5B; Mon, 16 Aug 2004 02:38:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwb4i-0001EV-0K
	for pana@megatron.ietf.org; Mon, 16 Aug 2004 02:34:32 -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 CAA11380
	for <pana@ietf.org>; Mon, 16 Aug 2004 02:34:30 -0400 (EDT)
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BwbAR-0002dL-T1
	for pana@ietf.org; Mon, 16 Aug 2004 02:40:28 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id i7G6YTso026673;
	Mon, 16 Aug 2004 08:34:29 +0200
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id i7G6XmNW010974;
	Mon, 16 Aug 2004 08:34:08 +0200
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <P8C2TV8B>; Mon, 16 Aug 2004 08:33:48 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F046864EB@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>,
        Alper Yegin
	<alper.yegin@samsung.com>, pana@ietf.org
Subject: RE: [Pana] PANA over IP-in-IP tunnels
Date: Mon, 16 Aug 2004 08:33:13 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
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 mohan, 

> > 
> > Can we run PANA over IP-in-IP tunnels as is, or do we need some 
> > additional considerations for that? Consider the tunnel is 
> established 
> > prior to running PANA. PANA does not have anything to do with the 
> > management of the tunnel, but simply takes it as a "link".
> > 
> Though it is technically a single hop, it allows the PAA to 
> be anywhere on the internet. This means the attacker gets to 
> consume all of the network resources (compared to just a few 
> devices if PAA is located on the edge) that is between the 
> PaC and the PAA.


i don't understand your last sentence. what is your concern? 


 I don't remember all of the discussions on 
> what prevented from PAA being more than one hop away  i.e 
> what are the dis-advantages of performing network access 
> authentication in the core ? Sure, hop count not being 
> decremented in the tunnel still prevents a few threats. 
the one hop away thing was mostly related to the packet filter installation,
routing asymmetry and topology knowledge. 


ciao
hannes

> 
> -mohan
> 
>  
> > 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  Mon Aug 16 14:33: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 OAA20729
	for <pana-archive@lists.ietf.org>; Mon, 16 Aug 2004 14:33: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 1Bwm79-0004lo-LW; Mon, 16 Aug 2004 14:21:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwm2H-0003mO-CQ
	for pana@megatron.ietf.org; Mon, 16 Aug 2004 14:16:45 -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 OAA19819
	for <pana@ietf.org>; Mon, 16 Aug 2004 14:16:44 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bwm86-00067C-Ss
	for pana@ietf.org; Mon, 16 Aug 2004 14:22: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 <0I2J00301XEZPJ@mailout2.samsung.com> for pana@ietf.org; Tue,
	17 Aug 2004 03:16:11 +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 <0I2J00H8QXEY9G@mailout2.samsung.com> for pana@ietf.org;
	Tue, 17 Aug 2004 03:16:11 +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 <0I2J00ITWXEW97@mmp1.samsung.com> for
	pana@ietf.org; Tue, 17 Aug 2004 03:16:10 +0900 (KST)
Date: Mon, 16 Aug 2004 11:16:04 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: "'Erik Nordmark'" <Erik.Nordmark@Sun.COM>
Message-id: <008601c483bd$1924db80$0041fea9@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: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
Subject: [Pana] Issue106: sequence number on rexmited messages must be
	incremented
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 Erik,

In your review feedback, you had said:

- the retransmission text says that a retransmitted packet has a new 
  sequence number. This makes no sense to me.

Can you please elaborate what kind of issues you are seeing with this.

Thank you.

Alper




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


From pana-bounces@ietf.org  Mon Aug 16 16:56: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 QAA09104
	for <pana-archive@lists.ietf.org>; Mon, 16 Aug 2004 16:56: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 1BwoHJ-0002R9-FP; Mon, 16 Aug 2004 16:40:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwnxh-0006Sx-8N
	for pana@megatron.ietf.org; Mon, 16 Aug 2004 16:20:09 -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 QAA04320
	for <pana@ietf.org>; Mon, 16 Aug 2004 16:20:07 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bwo3X-00020z-9g
	for pana@ietf.org; Mon, 16 Aug 2004 16:26:13 -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 <0I2K0090134NGZ@mailout2.samsung.com> for pana@ietf.org; Tue,
	17 Aug 2004 05:19:35 +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 <0I2K00F0B34MYB@mailout2.samsung.com> for pana@ietf.org;
	Tue, 17 Aug 2004 05:19:34 +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 <0I2K00IGP34KQ5@mmp2.samsung.com> for
	pana@ietf.org; Tue, 17 Aug 2004 05:19:34 +0900 (KST)
Date: Mon, 16 Aug 2004 13:19:27 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <00c001c483ce$5590c870$0041fea9@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: 7e267523e0685e5aa2dbbdde4b659686
Content-Transfer-Encoding: 7BIT
Subject: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
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 an attempt to resolve Issue 105.
The following text changes separate EAP-based reauthentication from
liveness test. The latter is accomplished by PANA-Ping-Request/Answer
now (renamed from PANA-Reauth-Request/Answer).

Comments welcome.



[1] In Section 3:


Change:

   In addition, PANA defines the following two types of
   re-authentication procedures that are performed while an established
   PANA session exists.

   1.  Re-authentication based on EAP

   2.  Re-authentication based on PANA-Reauth exchange

   The former type of re-authentication is used mainly for extending
   authorization lifetime or for updating the cryptographic keying
   material of a PANA SA.  The latter type of re-authentication is used
   mainly for maintaining the presence of the communicating peers each
   other so that the established PANA session can be terminated as soon
   as the presence of the peer is lost.

To:

   In addition, PANA allows re-authenticaiton of the PaC and PAA by
   allowing any one of them to initiate an EAP authentication during
   an on-going PANA session. Refreshing the session and cryptographic
   keys are possible reasons to engage in re-authentication.

   Finally, the protocol enables PAA and PaC ping each other to test 
   liveness of the session. 


[2] In Section 3.1:

Change:

  o  Re-authentication based on the PANA-Reauth-Request/ PANA-Reauth
      exchange is performed.

To:

  o  Liveness test based on the PANA-Ping-Request/PANA-Ping-Answer
      exchange is performed.


Change:

 // Re-authentication based on PANA-Reauth exchange
         <-----     PANA-Reauth-Request[Session-Id, MAC]
         ----->     PANA-Reauth-Answer[Session-Id, MAC]

To:

 // Liveness test based on PANA-Ping exchange
         <-----     PANA-Ping-Request[Session-Id, MAC]
         ----->     PANA-Ping-Answer[Session-Id, MAC]



[3] In Section 4.1.7:

Change:

 *  In discovery and initial handshake phase:

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

To:

 *  In discovery and initial handshake phase:

         +  PANA-Termination-Request.


Change:

   *  In authentication phase:

         +  PANA-PAA-Discover.

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

To:

   *  In authentication phase:

         +  PANA-PAA-Discover.

         +  PANA-Termination-Request.






[4] New text for Section 4.4:

4.4  Re-authentication

   An already authenitcation PANA session can enter an authentication 
   phase by re-executing EAP. In this case, some or all message
exchanges
   for discovery and initial handshake phase MAY be omitted in the
   following way.  When a PaC wants to initiate re-authentication, 
   it sends a unicast PANA-PAA-Discovery message to
   the PAA.  This message MUST contain a Session-Id AVP which is used
   for identifying the PANA session on the PAA.  If the PAA already has
   an established PANA session for the PaC with the matching identifier,
   it sends a PANA-Auth-Request message containing the same identifier
   to start an authentication phase.  If the PAA can not recognize the
   session identifier, it proceeds with regular authentication by
   sending back PANA-Start-Request. When the PAA initiates
   re-authentication, it sends a PANA-Auth-Request message containing
   the session identifier for the PaC to enter an authentication phase.
   PAA SHOULD initiate EAP authentication before the current session
   lifetime expires.  In both cases, the tseq and rseq values are
   inherited from the previous (re-)authentication.  For any
   re-authentication, if there is an established PANA SA,
   PANA-Auth-Request and PANA-Auth-Answer messages MUST be protected by
   adding a MAC AVP to each message.  Any subsequent EAP-based
   authentication MUST be performed with the same ISP and NAP that was
   selected during the initial authentication.  An example sequence for
   a re-authentication initiated by a PaC is shown in Figure
   6.

      PaC      PAA  Message
      ------------------------------------------------------
         ----->     PANA-PAA-Discover(0,0)[Session-Id]
         <-----     PANA-Auth-Request(p,q)[Session-Id, EAP, MAC]
         ----->     PANA-Auth-Answer(q+1,p)[Session-Id, EAP, MAC]
         <-----     PANA-Auth-Request(p+1,q+1)[Session-Id, EAP, MAC]
         ----->     PANA-Auth-Answer(q+2,p+1)[Session-Id, EAP, MAC]
         <-----     PANA-Bind-Request(p+2,q+2)
                       [Session-Id, EAP{Success}, Device-Id, Key-Id,
                        Lifetime, Protection-Cap., PPAC, MAC]
         ----->     PANA-Bind-Answer(q+3,p+2)
                       [Session-Id, Device-Id, Key-Id, PPAC, MAC]

  Figure 6: Example Sequence for EAP-based re-authentication initiated
                                 by PaC


[5] Create a new section after the current Section 4.4

4.5. Liveness Test
 
   PANA-Ping-Request and PANA-Ping-Answer messages are used for testing
   the liveness of the PANA session on the PANA peer. If there is an 
   established PANA session, both the PaC and
   the PAA are allowed to send a PANA-Ping-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-Ping-Answer message.  Both PANA-Ping-Request and
   PANA-Ping-Answer messages MUST be protected with a MAC AVP when a
   PANA SA is available.

   Implementations MUST limit the rate of performing this test.  
   The PaC and the PAA can handle
   rate limitation on their own, they do not have to perform any
   coordination with each other.  There is no negotiation of timers for
   this purpose.

   Figure 7 and Figure 8 illustrate liveness tests as they are initiated
   by the PaC and the PAA respectively.


      PaC      PAA     Message(tseq,rseq)[AVPs]
      ------------------------------------------------------
         ----->        PANA-Ping-Request(q,p)[Session-Id, MAC]
         <-----        PANA-Ping-Answer(p+1,q)[Session-Id, MAC]


        Figure 7: Example Sequence for PaC-initiated liveness test


      PaC      PAA     Message(tseq,rseq)[AVPs]
      ------------------------------------------------------
         <-----        PANA-Ping-Request(p,q)[Session-Id, MAC]
         ----->        PANA-Ping-Answer(q+1,p)[Session-Id, MAC]


        Figure 8: Example Sequence for PAA-initiated liveness test


[6] In section 4.6:

Remove:

  o  Re-authentication based on the PANA-Reauth exchange is performed.


[7] In Section 4.10:

Change:

   PANA peer can use PANA-Reauth-Request message to
   verify the disconnection before taking an action.

   The session lifetime parameter is not related to the transmission of
   PANA-Reauth-Request messages.  These messages can be used for
   asynchronously verifying the liveness of the peer and enabling
   mobility optimizations.  The decision to send PANA-Reauth-Request
   message is taken locally and does not require coordination between
   the peers.

To:

   PANA peer can use PANA-Ping-Request message to
   verify the disconnection before taking an action.

   The session lifetime parameter is not related to the transmission of
   PANA-Ping-Request messages.  These messages can be used for
   asynchronously verifying the liveness of the peer.  The decision 
   to send PANA-Ping-Request message is taken locally and does not 
   require coordination between the peers.


[8] In Section 6.4:

Change:

                 PANA-Reauth-Request         <------->
                 PANA-Reauth-Answer          <------->

To:

                 PANA-Ping-Request           <------->
                 PANA-Ping-Answer            <------->

[9] New text for Section 6.4.9 and 6.4.10:

6.4.9  PANA-Ping-Request (PPR)

   PANA-Ping-Request (PPR) is either sent by the PaC or the PAA.

         PANA-Ping-Request ::= < PANA-Header: 5, REQ >
                       < Session-Id >
                    *  [ AVP ]
                   0*1 < MAC >


6.4.10  PANA-Ping-Answer (PPA)

   PANA-Ping-Answer (PPA) is sent in response to a
   PANA-Ping-Request.

         PANA-Ping-Answer ::= < PANA-Header: 5 >
                       < Session-Id >
                    *  [ AVP ]
                   0*1 < MAC >

[10] In Section 6.6:

Change:

 Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER | PFEA |

To:

 Attribute Name      | PPR  | PPA  | PTR | PTA | PER | PFER | PFEA |



[11] In Section 7:

Change:

         PANA-Reauth-Request (PRAR)

To:

         PANA-Ping-Request (PPR)


Change:

   The last two messages, PRAR and PTR are sent either by PaC or
   PAA.

To:

   The last two messages, PPR and PTR are sent either by PaC or
   PAA.


[12] In Section 9.g:


Change:

   A disconnect may also be detected earlier by using PANA
   reauthentication messages.

To:

   A disconnect may also be detected earlier by using PANA
   ping messages.




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


From pana-bounces@ietf.org  Mon Aug 16 16:57: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 QAA09338
	for <pana-archive@lists.ietf.org>; Mon, 16 Aug 2004 16:57: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 1BwoLs-0004gz-GY; Mon, 16 Aug 2004 16:45:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BwoBd-0006TH-CE
	for pana@megatron.ietf.org; Mon, 16 Aug 2004 16:34: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 QAA06486
	for <pana@ietf.org>; Mon, 16 Aug 2004 16:34:30 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BwoHT-0002ks-Cb
	for pana@ietf.org; Mon, 16 Aug 2004 16:40:37 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7GKYSlr003301;
	Tue, 17 Aug 2004 05:34:28 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7GKYR2e000539;
	Tue, 17 Aug 2004 05:34:27 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	FAA00536 ; Tue, 17 Aug 2004 05:34:27 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id FAA07829; Tue, 17 Aug 2004 05:34:27 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id FAA27283;
	Tue, 17 Aug 2004 05:34:26 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7GKYQ6t010039;
	Tue, 17 Aug 2004 05:34: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 <0I2K00MS33TA1H@tsbpo1.po.toshiba.co.jp>; Tue,
	17 Aug 2004 05:34:25 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BwoB2-0003Qo-00; Mon, 16 Aug 2004 13:33:56 -0700
Date: Mon, 16 Aug 2004 16:33:55 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] PANA over IP-in-IP tunnels
In-reply-to: <017f01c48196$bfdd5ed0$981d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040816203355.GD9431@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+20040803i
References: <20040829173258.GB12038@steelhead>
	<017f01c48196$bfdd5ed0$981d9069@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
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, Aug 13, 2004 at 05:36:31PM -0700, Alper Yegin wrote:
> Yoshi,
> 
> > Hi Alper,
> > 
> > I think we can run PANA over an IP-in-IP tunnel as is, if the tunnel
> > has been already established before running PANA over it.
> 
> What would be the DI? 
> 
> If there is a secure lower-layer channel (like physical security, or if
> this is an IPsec tunnel), would we use the TOAs as the DIs? TOA is
> equivalent to a link-layer address.

For an IP-in-IP encapsulated tunnel, I think it is sufficient to use
the TOA (tunnel outer address) as DI.  But you also mention IPsec
tunnel.  For an IPsec tunnel, I am not sure whether using TOA-only as
DI is sufficient if we consider:

  - There can be multiple IPsec tunnels between the same IPsec
  endpoints.

  - An IPsec tunnel is UDP encapsulated when NAT-T is used
  and there may be multiple PaCs that are behind the same NAT box 
  and connecting to the same PAA.

> 
> If there is no secure channel, one needs to be built based on IPsec. In
> that case, the lower-layer addresses have no significance as DI in the
> context of PANA.

I agree.

Yoshihiro Ohba

> 
> > I found in I-D tracker a comment from IESG with regard to
> > draft-ietf-pana-requirement-08.txt:
> > 
> > "
> > 4.5.3 -- Please justify this requirement.  I can think of lots of
> > scenarios where it simply wouldn't hold, such as a large hotel or
> > conference center which permits free intranet access but demands
> > payment for most (but not all) external access.  Beyond that, what
> > about tunneled connections?  Are they permissible, given this
> > requirement?
> > "
> > 
> > I think we might clearly mention in the requirement draft that PANA
> > can run over IP-in-IP link.
> 
> Yes, agreed.
> 
> Alper
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Mon, Aug 09, 2004 at 05:56:02PM -0700, Alper Yegin wrote:
> > >
> > > Can we run PANA over IP-in-IP tunnels as is, or do we need some
> > > additional considerations for that? Consider the tunnel is
> established
> > > prior to running PANA. PANA does not have anything to do with the
> > > management of the tunnel, but simply takes it as a "link".
> > >
> > > 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  Tue Aug 17 08:38: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 IAA11727
	for <pana-archive@lists.ietf.org>; Tue, 17 Aug 2004 08:38: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 1Bx39i-0007Vq-FR; Tue, 17 Aug 2004 08:33:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bx35r-0006x5-Sv; Tue, 17 Aug 2004 08:29:36 -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 IAA11445;
	Tue, 17 Aug 2004 08:29:34 -0400 (EDT)
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bx3Br-0002sd-0J; Tue, 17 Aug 2004 08:35:48 -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 535652FE6B;
	Tue, 17 Aug 2004 14:28:56 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1Bx346-0000eu-C2;
	Tue, 17 Aug 2004 14:27:46 +0200
Date: Tue, 17 Aug 2004 14:27:46 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: seamoby@ietf.org
Message-ID: <20040817122746.GK1973@ipv6-5.int-evry.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Gerardo Giaretta <gerardo.giaretta@tilab.com>,
        Hannes Tschofening <hannes.tschofenig@siemens.com>,
        Maryline MAKNAVICIUS-LAURENT <maryline.maknavicius@int-evry.fr>,
        yacine <yacine.el_mghazli@alcatel.fr>, pana@ietf.org
Subject: [Pana] use of CTP for PANA: first issue
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 all,

 we try to use CTP to transfer PANA context between PANA Authentication
Agent (PAA). We think that this could enhance handover performance in
mobile environments where PANA could be used.
(cf. draft-bournelle-pana-ctp-00.txt).

 However, it appears that it is very difficult to use CTP "as is" for
PANA. As an example, in our proposal, the transfer occurs between PAAs.

>From draft-ietf-pana-pana-05.txt
"
PANA Authentication Agent (PAA):

    The protocol entity in the access network side whose responsibility
is to verify the credentials provided by a PANA client and grant network
access service to the device associated with the client and identified
by a DI. Note the authentication and authorization procedure can,
according to the EAP model, be also offloaded to the backend AAA
infrastructure.
"

 So the PAA is not necessarily an access router.

 In CTP, the transfer occurs between access routers.

 So we are facing a sort of conflict and we would like to get
feedback/comments from the seamoby wg for this issue.

 Thanks for your help,

ps: we have other issues concerning use of CTP for 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 Aug 17 13:56:11 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 NAA03555
	for <pana-archive@lists.ietf.org>; Tue, 17 Aug 2004 13:56:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bx86M-0000SI-6s; Tue, 17 Aug 2004 13:50:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bx7DA-0006h7-PU; Tue, 17 Aug 2004 12:53:24 -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 MAA29076;
	Tue, 17 Aug 2004 12:53:21 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Bx7JD-0007yz-8V; Tue, 17 Aug 2004 12:59:39 -0400
Message-ID: <00eb01c4847a$d210f620$536115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Julien Bournelle" <Julien.Bournelle@int-evry.fr>, <seamoby@ietf.org>
References: <20040817122746.GK1973@ipv6-5.int-evry.fr>
Date: Tue, 17 Aug 2004 09:54:09 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 17 Aug 2004 13:50:25 -0400
Cc: Gerardo Giaretta <gerardo.giaretta@tilab.com>, pana@ietf.org,
        Maryline MAKNAVICIUS-LAURENT <maryline.maknavicius@int-evry.fr>,
        yacine <yacine.el_mghazli@alcatel.fr>,
        Hannes Tschofening <hannes.tschofenig@siemens.com>
Subject: [Pana] Re: [Seamoby] use of CTP for PANA: first issue
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

CTP is an experimental draft. There's no reason why it can't  be modified
prior to resubmission for PS.

As soon as the IESG agrees to publication, I'd like to start discussion in
MOBOPTS about modifications to make it suitable for PS.

            jak

----- Original Message ----- 
From: "Julien Bournelle" <Julien.Bournelle@int-evry.fr>
To: <seamoby@ietf.org>
Cc: "Gerardo Giaretta" <gerardo.giaretta@tilab.com>; "Hannes Tschofening"
<hannes.tschofenig@siemens.com>; "Maryline MAKNAVICIUS-LAURENT"
<maryline.maknavicius@int-evry.fr>; "yacine" <yacine.el_mghazli@alcatel.fr>;
<pana@ietf.org>
Sent: Tuesday, August 17, 2004 5:27 AM
Subject: [Seamoby] use of CTP for PANA: first issue


> Hi all,
>
>  we try to use CTP to transfer PANA context between PANA Authentication
> Agent (PAA). We think that this could enhance handover performance in
> mobile environments where PANA could be used.
> (cf. draft-bournelle-pana-ctp-00.txt).
>
>  However, it appears that it is very difficult to use CTP "as is" for
> PANA. As an example, in our proposal, the transfer occurs between PAAs.
>
> >From draft-ietf-pana-pana-05.txt
> "
> PANA Authentication Agent (PAA):
>
>     The protocol entity in the access network side whose responsibility
> is to verify the credentials provided by a PANA client and grant network
> access service to the device associated with the client and identified
> by a DI. Note the authentication and authorization procedure can,
> according to the EAP model, be also offloaded to the backend AAA
> infrastructure.
> "
>
>  So the PAA is not necessarily an access router.
>
>  In CTP, the transfer occurs between access routers.
>
>  So we are facing a sort of conflict and we would like to get
> feedback/comments from the seamoby wg for this issue.
>
>  Thanks for your help,
>
> ps: we have other issues concerning use of CTP for PANA..
>
> -- 
> julien.bournelle@int-evry.fr
>
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
>



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


From pana-bounces@ietf.org  Wed Aug 18 05:07: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 FAA19596
	for <pana-archive@lists.ietf.org>; Wed, 18 Aug 2004 05:07: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 1BxMNn-0000Jp-OU; Wed, 18 Aug 2004 05:05:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxMJu-0008SF-UF
	for pana@megatron.ietf.org; Wed, 18 Aug 2004 05:01:23 -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 FAA19306
	for <pana@ietf.org>; Wed, 18 Aug 2004 05:01:20 -0400 (EDT)
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxMQ6-0008Eg-6h
	for pana@ietf.org; Wed, 18 Aug 2004 05:07:46 -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 6A93530006;
	Wed, 18 Aug 2004 11:00:45 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1BxMIA-0001MI-AQ;
	Wed, 18 Aug 2004 10:59:34 +0200
Date: Wed, 18 Aug 2004 10:59:34 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: James Kempf <kempf@docomolabs-usa.com>
Message-ID: <20040818085934.GC5191@ipv6-5.int-evry.fr>
References: <20040817122746.GK1973@ipv6-5.int-evry.fr>
	<00eb01c4847a$d210f620$536115ac@dcml.docomolabsusa.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00eb01c4847a$d210f620$536115ac@dcml.docomolabsusa.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: fb6060cb60c0cea16e3f7219e40a0a81
Cc: Gerardo Giaretta <gerardo.giaretta@tilab.com>, pana@ietf.org,
        Maryline MAKNAVICIUS-LAURENT <maryline.maknavicius@int-evry.fr>,
        yacine <yacine.el_mghazli@alcatel.fr>,
        Hannes Tschofening <hannes.tschofenig@siemens.com>
Subject: [Pana] Re: [Seamoby] use of CTP for PANA: first issue
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,

 thanks for your quick answer,

 do you think that we should post our issues concerning use of CTP for
PANA in the MOBOPTS ML ?

On Tue, Aug 17, 2004 at 09:54:09AM -0700, James Kempf wrote:
> CTP is an experimental draft. There's no reason why it can't  be modified
> prior to resubmission for PS.
> 
> As soon as the IESG agrees to publication, I'd like to start discussion in
> MOBOPTS about modifications to make it suitable for PS.
> 
>             jak
> 
> ----- Original Message ----- 
> From: "Julien Bournelle" <Julien.Bournelle@int-evry.fr>
> To: <seamoby@ietf.org>
> Cc: "Gerardo Giaretta" <gerardo.giaretta@tilab.com>; "Hannes Tschofening"
> <hannes.tschofenig@siemens.com>; "Maryline MAKNAVICIUS-LAURENT"
> <maryline.maknavicius@int-evry.fr>; "yacine" <yacine.el_mghazli@alcatel.fr>;
> <pana@ietf.org>
> Sent: Tuesday, August 17, 2004 5:27 AM
> Subject: [Seamoby] use of CTP for PANA: first issue
> 
> 
> > Hi all,
> >
> >  we try to use CTP to transfer PANA context between PANA Authentication
> > Agent (PAA). We think that this could enhance handover performance in
> > mobile environments where PANA could be used.
> > (cf. draft-bournelle-pana-ctp-00.txt).
> >
> >  However, it appears that it is very difficult to use CTP "as is" for
> > PANA. As an example, in our proposal, the transfer occurs between PAAs.
> >
> > >From draft-ietf-pana-pana-05.txt
> > "
> > PANA Authentication Agent (PAA):
> >
> >     The protocol entity in the access network side whose responsibility
> > is to verify the credentials provided by a PANA client and grant network
> > access service to the device associated with the client and identified
> > by a DI. Note the authentication and authorization procedure can,
> > according to the EAP model, be also offloaded to the backend AAA
> > infrastructure.
> > "
> >
> >  So the PAA is not necessarily an access router.
> >
> >  In CTP, the transfer occurs between access routers.
> >
> >  So we are facing a sort of conflict and we would like to get
> > feedback/comments from the seamoby wg for this issue.
> >
> >  Thanks for your help,
> >
> > ps: we have other issues concerning use of CTP for PANA..
> >
> > -- 
> > julien.bournelle@int-evry.fr
> >
> > _______________________________________________
> > Seamoby mailing list
> > Seamoby@ietf.org
> > https://www1.ietf.org/mailman/listinfo/seamoby
> >
> 
> 

-- 
julien.bournelle@int-evry.fr

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


From pana-bounces@ietf.org  Wed Aug 18 13:00: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 NAA21824
	for <pana-archive@lists.ietf.org>; Wed, 18 Aug 2004 13:00: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 1BxTWt-0004SY-41; Wed, 18 Aug 2004 12:43:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxTP7-0002kv-IG
	for pana@megatron.ietf.org; Wed, 18 Aug 2004 12:35:14 -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 MAA19793
	for <pana@ietf.org>; Wed, 18 Aug 2004 12:35:10 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxTVM-0000tq-TN
	for pana@ietf.org; Wed, 18 Aug 2004 12:41:41 -0400
Message-ID: <006b01c48541$7250e890$536115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Julien Bournelle" <Julien.Bournelle@int-evry.fr>
References: <20040817122746.GK1973@ipv6-5.int-evry.fr>
	<00eb01c4847a$d210f620$536115ac@dcml.docomolabsusa.com>
	<20040818085934.GC5191@ipv6-5.int-evry.fr>
Date: Wed, 18 Aug 2004 09:35:58 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <gerardo.giaretta@tilab.com>, pana@ietf.org,
        Maryline MAKNAVICIUS-LAURENT <maryline.maknavicius@int-evry.fr>,
        yacine <yacine.el_mghazli@alcatel.fr>,
        Hannes Tschofening <hannes.tschofenig@siemens.com>
Subject: [Pana] Re: [Seamoby] use of CTP for PANA: first issue
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

Yes.

            jak

----- Original Message ----- 
From: "Julien Bournelle" <Julien.Bournelle@int-evry.fr>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Gerardo Giaretta" <gerardo.giaretta@tilab.com>; "Hannes Tschofening"
<hannes.tschofenig@siemens.com>; "Maryline MAKNAVICIUS-LAURENT"
<maryline.maknavicius@int-evry.fr>; "yacine" <yacine.el_mghazli@alcatel.fr>;
<pana@ietf.org>
Sent: Wednesday, August 18, 2004 1:59 AM
Subject: Re: [Seamoby] use of CTP for PANA: first issue


> Hi,
>
>  thanks for your quick answer,
>
>  do you think that we should post our issues concerning use of CTP for
> PANA in the MOBOPTS ML ?
>
> On Tue, Aug 17, 2004 at 09:54:09AM -0700, James Kempf wrote:
> > CTP is an experimental draft. There's no reason why it can't  be
modified
> > prior to resubmission for PS.
> >
> > As soon as the IESG agrees to publication, I'd like to start discussion
in
> > MOBOPTS about modifications to make it suitable for PS.
> >
> >             jak
> >
> > ----- Original Message ----- 
> > From: "Julien Bournelle" <Julien.Bournelle@int-evry.fr>
> > To: <seamoby@ietf.org>
> > Cc: "Gerardo Giaretta" <gerardo.giaretta@tilab.com>; "Hannes
Tschofening"
> > <hannes.tschofenig@siemens.com>; "Maryline MAKNAVICIUS-LAURENT"
> > <maryline.maknavicius@int-evry.fr>; "yacine"
<yacine.el_mghazli@alcatel.fr>;
> > <pana@ietf.org>
> > Sent: Tuesday, August 17, 2004 5:27 AM
> > Subject: [Seamoby] use of CTP for PANA: first issue
> >
> >
> > > Hi all,
> > >
> > >  we try to use CTP to transfer PANA context between PANA
Authentication
> > > Agent (PAA). We think that this could enhance handover performance in
> > > mobile environments where PANA could be used.
> > > (cf. draft-bournelle-pana-ctp-00.txt).
> > >
> > >  However, it appears that it is very difficult to use CTP "as is" for
> > > PANA. As an example, in our proposal, the transfer occurs between
PAAs.
> > >
> > > >From draft-ietf-pana-pana-05.txt
> > > "
> > > PANA Authentication Agent (PAA):
> > >
> > >     The protocol entity in the access network side whose
responsibility
> > > is to verify the credentials provided by a PANA client and grant
network
> > > access service to the device associated with the client and identified
> > > by a DI. Note the authentication and authorization procedure can,
> > > according to the EAP model, be also offloaded to the backend AAA
> > > infrastructure.
> > > "
> > >
> > >  So the PAA is not necessarily an access router.
> > >
> > >  In CTP, the transfer occurs between access routers.
> > >
> > >  So we are facing a sort of conflict and we would like to get
> > > feedback/comments from the seamoby wg for this issue.
> > >
> > >  Thanks for your help,
> > >
> > > ps: we have other issues concerning use of CTP for PANA..
> > >
> > > -- 
> > > julien.bournelle@int-evry.fr
> > >
> > > _______________________________________________
> > > Seamoby mailing list
> > > Seamoby@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/seamoby
> > >
> >
> >
>
> -- 
> julien.bournelle@int-evry.fr
>



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


From pana-bounces@ietf.org  Wed Aug 18 14:57: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 OAA29294
	for <pana-archive@lists.ietf.org>; Wed, 18 Aug 2004 14:57: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 1BxVZc-00014N-JD; Wed, 18 Aug 2004 14:54:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxVSr-0008P7-Tl
	for pana@megatron.ietf.org; Wed, 18 Aug 2004 14:47:23 -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 OAA28581
	for <pana@ietf.org>; Wed, 18 Aug 2004 14:46:32 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxVYR-0003bK-C1
	for pana@ietf.org; Wed, 18 Aug 2004 14:53:02 -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 <0I2N00604O4GFN@mailout2.samsung.com> for pana@ietf.org; Thu,
	19 Aug 2004 03:45:53 +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 <0I2N0043GO4GAZ@mailout2.samsung.com> for pana@ietf.org;
	Thu, 19 Aug 2004 03:45:52 +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 <0I2N00989O4ETX@mmp2.samsung.com> for
	pana@ietf.org; Thu, 19 Aug 2004 03:45:52 +0900 (KST)
Date: Wed, 18 Aug 2004 11:45:49 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] PANA over IP-in-IP tunnels
In-reply-to: <20040816203355.GD9431@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <028b01c48553$959de7f0$0041fea9@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
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

> > What would be the DI?
> >
> > If there is a secure lower-layer channel (like physical security, or
if
> > this is an IPsec tunnel), would we use the TOAs as the DIs? TOA is
> > equivalent to a link-layer address.
> 
> For an IP-in-IP encapsulated tunnel, I think it is sufficient to use
> the TOA (tunnel outer address) as DI.  But you also mention IPsec
> tunnel.  For an IPsec tunnel, I am not sure whether using TOA-only as
> DI is sufficient if we consider:
> 
>   - There can be multiple IPsec tunnels between the same IPsec
>   endpoints.
> 
>   - An IPsec tunnel is UDP encapsulated when NAT-T is used
>   and there may be multiple PaCs that are behind the same NAT box
>   and connecting to the same PAA.

Good point. We could try to capture the DI as the collection of IP
address, IPsec SPI, UDP port number. But I think this is not only
getting complicated, but also it may not cover all sorts of other
tunneling mechanisms.

How about treating this case similar to addressless point-to-point
links? That is, not ever carrying the DI in PANA but relying on the
identifiers that are locally available (e.g., logical interface number).

I think this is a simpler and more scalable solution that is also
somewhat aligned with the current design.

Alper



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


From pana-bounces@ietf.org  Thu Aug 19 00:08: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 AAA14707
	for <pana-archive@lists.ietf.org>; Thu, 19 Aug 2004 00:08: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 1BxeB7-0003zb-Ko; Thu, 19 Aug 2004 00:05:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bxe7K-0003WJ-CO
	for pana@megatron.ietf.org; Thu, 19 Aug 2004 00:01:34 -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 AAA14512
	for <pana@ietf.org>; Thu, 19 Aug 2004 00:01:29 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxeDc-0001t6-VT
	for pana@ietf.org; Thu, 19 Aug 2004 00:08:06 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7J41Obv026910;
	Thu, 19 Aug 2004 13:01:24 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7J41Ow8016624;
	Thu, 19 Aug 2004 13:01:24 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	PAA16621 ; Thu, 19 Aug 2004 13:01:23 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id NAA14454; Thu, 19 Aug 2004 13:01:23 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id NAA28710;
	Thu, 19 Aug 2004 13:01:22 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7J41L6t019501;
	Thu, 19 Aug 2004 13:01:22 +0900 (JST)
Received: from steelhead (iVPN01-191.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 <0I2O002OKDU7L1@tsbpo1.po.toshiba.co.jp>; Thu,
	19 Aug 2004 13:01:21 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bxe72-00049P-00; Wed, 18 Aug 2004 21:01:16 -0700
Date: Thu, 19 Aug 2004 00:01:16 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] PANA over IP-in-IP tunnels
In-reply-to: <028b01c48553$959de7f0$0041fea9@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040819040116.GI27839@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+20040803i
References: <20040816203355.GD9431@steelhead>
	<028b01c48553$959de7f0$0041fea9@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
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 Wed, Aug 18, 2004 at 11:45:49AM -0700, Alper Yegin wrote:
> 
> Good point. We could try to capture the DI as the collection of IP
> address, IPsec SPI, UDP port number. But I think this is not only
> getting complicated, but also it may not cover all sorts of other
> tunneling mechanisms.
> 
> How about treating this case similar to addressless point-to-point
> links? That is, not ever carrying the DI in PANA but relying on the
> identifiers that are locally available (e.g., logical interface number).

I agree.  Note that an IPsec tunnel mode SA may not have a dedicated
logical interface, but it must have a dedicated SAD entry and some
local identifier corresonding to the SAD entry can work as DI in any
case.

> 
> I think this is a simpler and more scalable solution that is also
> somewhat aligned with the current design.

OK.

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 Aug 19 12:47: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 MAA15666
	for <pana-archive@lists.ietf.org>; Thu, 19 Aug 2004 12:47: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 1BxpuJ-0001KZ-Cr; Thu, 19 Aug 2004 12:36:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bxphb-0007vO-4F
	for pana@megatron.ietf.org; Thu, 19 Aug 2004 12:23:47 -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 MAA14209
	for <pana@ietf.org>; Thu, 19 Aug 2004 12:23:42 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bxpo0-0007tu-5w
	for pana@ietf.org; Thu, 19 Aug 2004 12:30:25 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7JGNPbv009074;
	Fri, 20 Aug 2004 01:23:25 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7JGNPZb009375;
	Fri, 20 Aug 2004 01:23:25 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	BAA09372 ; Fri, 20 Aug 2004 01:23:25 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA08081; Fri, 20 Aug 2004 01:23:24 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA28394;
	Fri, 20 Aug 2004 01:23:24 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7JGNN6t002239;
	Fri, 20 Aug 2004 01:23:23 +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 <0I2P00KKRC6V0O@tsbpo1.po.toshiba.co.jp>; Fri,
	20 Aug 2004 01:23:22 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BxphA-0005Pn-00; Thu, 19 Aug 2004 09:23:20 -0700
Date: Thu, 19 Aug 2004 12:23:20 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <00c001c483ce$5590c870$0041fea9@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040819162320.GJ27839@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+20040803i
References: <00c001c483ce$5590c870$0041fea9@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1dc446dc7ac353b90b60743d0e479e3
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 changes basically looks good.  Please see my minior
comments below.

On Mon, Aug 16, 2004 at 01:19:27PM -0700, Alper Yegin wrote:
> 
> Here is an attempt to resolve Issue 105.
> The following text changes separate EAP-based reauthentication from
> liveness test. The latter is accomplished by PANA-Ping-Request/Answer
> now (renamed from PANA-Reauth-Request/Answer).
> 
> Comments welcome.
> 
> 
> 
> [1] In Section 3:
> 
> 
> Change:
> 
>    In addition, PANA defines the following two types of
>    re-authentication procedures that are performed while an established
>    PANA session exists.
> 
>    1.  Re-authentication based on EAP
> 
>    2.  Re-authentication based on PANA-Reauth exchange
> 
>    The former type of re-authentication is used mainly for extending
>    authorization lifetime or for updating the cryptographic keying
>    material of a PANA SA.  The latter type of re-authentication is used
>    mainly for maintaining the presence of the communicating peers each
>    other so that the established PANA session can be terminated as soon
>    as the presence of the peer is lost.
> 
> To:
> 
>    In addition, PANA allows re-authenticaiton of the PaC and PAA by
>    allowing any one of them to initiate an EAP authentication during
>    an on-going PANA session. Refreshing the session and cryptographic
>    keys are possible reasons to engage in re-authentication.
> 
>    Finally, the protocol enables PAA and PaC ping each other to test 
>    liveness of the session. 
> 
> 
> [2] In Section 3.1:
> 
> Change:
> 
>   o  Re-authentication based on the PANA-Reauth-Request/ PANA-Reauth
>       exchange is performed.
> 
> To:
> 
>   o  Liveness test based on the PANA-Ping-Request/PANA-Ping-Answer
>       exchange is performed.
> 
> 
> Change:
> 
>  // Re-authentication based on PANA-Reauth exchange
>          <-----     PANA-Reauth-Request[Session-Id, MAC]
>          ----->     PANA-Reauth-Answer[Session-Id, MAC]
> 
> To:
> 
>  // Liveness test based on PANA-Ping exchange
>          <-----     PANA-Ping-Request[Session-Id, MAC]
>          ----->     PANA-Ping-Answer[Session-Id, MAC]
> 
> 
> 
> [3] In Section 4.1.7:
> 
> Change:
> 
>  *  In discovery and initial handshake phase:
> 
>          +  PANA-Termination-Request and PANA-Reauth-Request.
> 
> To:
> 
>  *  In discovery and initial handshake phase:
> 
>          +  PANA-Termination-Request.
> 

Should PANA-Ping-Request be allowed in discovery and initial handshake
phase?

> 
> Change:
> 
>    *  In authentication phase:
> 
>          +  PANA-PAA-Discover.
> 
>          +  PANA-Termination-Request and PANA-Reauth-Request.
> 
> To:
> 
>    *  In authentication phase:
> 
>          +  PANA-PAA-Discover.
> 
>          +  PANA-Termination-Request.
> 

Should PANA-Ping-Request be allowed in authentication phase?

Regards,

Yoshihiro Ohba

> 
> 
> 
> 
> 
> [4] New text for Section 4.4:
> 
> 4.4  Re-authentication
> 
>    An already authenitcation PANA session can enter an authentication 
>    phase by re-executing EAP. In this case, some or all message
> exchanges
>    for discovery and initial handshake phase MAY be omitted in the
>    following way.  When a PaC wants to initiate re-authentication, 
>    it sends a unicast PANA-PAA-Discovery message to
>    the PAA.  This message MUST contain a Session-Id AVP which is used
>    for identifying the PANA session on the PAA.  If the PAA already has
>    an established PANA session for the PaC with the matching identifier,
>    it sends a PANA-Auth-Request message containing the same identifier
>    to start an authentication phase.  If the PAA can not recognize the
>    session identifier, it proceeds with regular authentication by
>    sending back PANA-Start-Request. When the PAA initiates
>    re-authentication, it sends a PANA-Auth-Request message containing
>    the session identifier for the PaC to enter an authentication phase.
>    PAA SHOULD initiate EAP authentication before the current session
>    lifetime expires.  In both cases, the tseq and rseq values are
>    inherited from the previous (re-)authentication.  For any
>    re-authentication, if there is an established PANA SA,
>    PANA-Auth-Request and PANA-Auth-Answer messages MUST be protected by
>    adding a MAC AVP to each message.  Any subsequent EAP-based
>    authentication MUST be performed with the same ISP and NAP that was
>    selected during the initial authentication.  An example sequence for
>    a re-authentication initiated by a PaC is shown in Figure
>    6.
> 
>       PaC      PAA  Message
>       ------------------------------------------------------
>          ----->     PANA-PAA-Discover(0,0)[Session-Id]
>          <-----     PANA-Auth-Request(p,q)[Session-Id, EAP, MAC]
>          ----->     PANA-Auth-Answer(q+1,p)[Session-Id, EAP, MAC]
>          <-----     PANA-Auth-Request(p+1,q+1)[Session-Id, EAP, MAC]
>          ----->     PANA-Auth-Answer(q+2,p+1)[Session-Id, EAP, MAC]
>          <-----     PANA-Bind-Request(p+2,q+2)
>                        [Session-Id, EAP{Success}, Device-Id, Key-Id,
>                         Lifetime, Protection-Cap., PPAC, MAC]
>          ----->     PANA-Bind-Answer(q+3,p+2)
>                        [Session-Id, Device-Id, Key-Id, PPAC, MAC]
> 
>   Figure 6: Example Sequence for EAP-based re-authentication initiated
>                                  by PaC
> 
> 
> [5] Create a new section after the current Section 4.4
> 
> 4.5. Liveness Test
>  
>    PANA-Ping-Request and PANA-Ping-Answer messages are used for testing
>    the liveness of the PANA session on the PANA peer. If there is an 
>    established PANA session, both the PaC and
>    the PAA are allowed to send a PANA-Ping-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-Ping-Answer message.  Both PANA-Ping-Request and
>    PANA-Ping-Answer messages MUST be protected with a MAC AVP when a
>    PANA SA is available.
> 
>    Implementations MUST limit the rate of performing this test.  
>    The PaC and the PAA can handle
>    rate limitation on their own, they do not have to perform any
>    coordination with each other.  There is no negotiation of timers for
>    this purpose.
> 
>    Figure 7 and Figure 8 illustrate liveness tests as they are initiated
>    by the PaC and the PAA respectively.
> 
> 
>       PaC      PAA     Message(tseq,rseq)[AVPs]
>       ------------------------------------------------------
>          ----->        PANA-Ping-Request(q,p)[Session-Id, MAC]
>          <-----        PANA-Ping-Answer(p+1,q)[Session-Id, MAC]
> 
> 
>         Figure 7: Example Sequence for PaC-initiated liveness test
> 
> 
>       PaC      PAA     Message(tseq,rseq)[AVPs]
>       ------------------------------------------------------
>          <-----        PANA-Ping-Request(p,q)[Session-Id, MAC]
>          ----->        PANA-Ping-Answer(q+1,p)[Session-Id, MAC]
> 
> 
>         Figure 8: Example Sequence for PAA-initiated liveness test
> 
> 
> [6] In section 4.6:
> 
> Remove:
> 
>   o  Re-authentication based on the PANA-Reauth exchange is performed.
> 
> 
> [7] In Section 4.10:
> 
> Change:
> 
>    PANA peer can use PANA-Reauth-Request message to
>    verify the disconnection before taking an action.
> 
>    The session lifetime parameter is not related to the transmission of
>    PANA-Reauth-Request messages.  These messages can be used for
>    asynchronously verifying the liveness of the peer and enabling
>    mobility optimizations.  The decision to send PANA-Reauth-Request
>    message is taken locally and does not require coordination between
>    the peers.
> 
> To:
> 
>    PANA peer can use PANA-Ping-Request message to
>    verify the disconnection before taking an action.
> 
>    The session lifetime parameter is not related to the transmission of
>    PANA-Ping-Request messages.  These messages can be used for
>    asynchronously verifying the liveness of the peer.  The decision 
>    to send PANA-Ping-Request message is taken locally and does not 
>    require coordination between the peers.
> 
> 
> [8] In Section 6.4:
> 
> Change:
> 
>                  PANA-Reauth-Request         <------->
>                  PANA-Reauth-Answer          <------->
> 
> To:
> 
>                  PANA-Ping-Request           <------->
>                  PANA-Ping-Answer            <------->
> 
> [9] New text for Section 6.4.9 and 6.4.10:
> 
> 6.4.9  PANA-Ping-Request (PPR)
> 
>    PANA-Ping-Request (PPR) is either sent by the PaC or the PAA.
> 
>          PANA-Ping-Request ::= < PANA-Header: 5, REQ >
>                        < Session-Id >
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> 
> 6.4.10  PANA-Ping-Answer (PPA)
> 
>    PANA-Ping-Answer (PPA) is sent in response to a
>    PANA-Ping-Request.
> 
>          PANA-Ping-Answer ::= < PANA-Header: 5 >
>                        < Session-Id >
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> [10] In Section 6.6:
> 
> Change:
> 
>  Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER | PFEA |
> 
> To:
> 
>  Attribute Name      | PPR  | PPA  | PTR | PTA | PER | PFER | PFEA |
> 
> 
> 
> [11] In Section 7:
> 
> Change:
> 
>          PANA-Reauth-Request (PRAR)
> 
> To:
> 
>          PANA-Ping-Request (PPR)
> 
> 
> Change:
> 
>    The last two messages, PRAR and PTR are sent either by PaC or
>    PAA.
> 
> To:
> 
>    The last two messages, PPR and PTR are sent either by PaC or
>    PAA.
> 
> 
> [12] In Section 9.g:
> 
> 
> Change:
> 
>    A disconnect may also be detected earlier by using PANA
>    reauthentication messages.
> 
> To:
> 
>    A disconnect may also be detected earlier by using PANA
>    ping messages.
> 
> 
> 
> 
> _______________________________________________
> 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 Aug 19 17:11:40 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 RAA09774
	for <pana-archive@lists.ietf.org>; Thu, 19 Aug 2004 17:11:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bxtwp-0000vo-2N; Thu, 19 Aug 2004 16:55:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bxskn-0005CY-PS
	for pana@megatron.ietf.org; Thu, 19 Aug 2004 15:39:17 -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 PAA28253
	for <pana@ietf.org>; Thu, 19 Aug 2004 15:39:16 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxsrH-0003Bf-Aw
	for pana@ietf.org; Thu, 19 Aug 2004 15:46:00 -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 <0I2P00301L8FK4@mailout3.samsung.com> for pana@ietf.org; Fri,
	20 Aug 2004 04:38:39 +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 <0I2P002JNL8EBG@mailout3.samsung.com> for pana@ietf.org;
	Fri, 20 Aug 2004 04:38:38 +0900 (KST)
Received: from Alperyegin ([105.144.29.160])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I2P0030VL8CHY@mmp1.samsung.com> for
	pana@ietf.org; Fri, 20 Aug 2004 04:38:38 +0900 (KST)
Date: Thu, 19 Aug 2004 12:38:35 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <007a01c48624$1ef39100$291d9069@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: 4515df9441674711565101d9d5c4f63f
Content-Transfer-Encoding: 7BIT
Subject: [Pana] Issue 94 and 95 - proposed text
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 new proposed text for the security considerations section to
handle issues 94 and 95.

Comments welcome.

9.  Security Considerations

   The PANA protocol defines a UDP-based EAP encapsulation that runs 
   between two IP-enabled nodes on the same IP link. Various security
   threats that are relevant to a protocol of this nature are outlined
   in [I-D.ietf-pana-threats-eval]. Security considerations stemming
   from the use of EAP and EAP methods are discussed in [RFC3748].
   This section provides a discussion on the security-related issues
   that are related to PANA framework and protocol design.

   An important element in assessing security of PANA design and
   deployment in a network is the presence of lower-layer (physical and
   link-layer) security. In the context of this document, lower-layers 
   are said to be secure if they can prevent eavesdropping and spoofing
of
   packets. Examples of such networks are physically-secured DSL
networks 
   and 3GPP2 networks with crytographically-secured cdma2000 link-layer.

   In these examples, the lower-layer security is enabled even before 
   running the first PANA-based authentication. In the absence of such a

   pre-established secure channel, one needs to be created in
conjunction 
   with PANA using a link-layer or network-layer cryptographic 
   mechanism (e.g., IPsec). 
   
  
9.1. General security measures 

   PANA provides multiple mechanisms to secure a PANA session.

   Since PaC and PAA are on the same IP link, a simple TTL check on
   the received PANA messages prevents off-link attacks.

   PANA messages carry both a transmission sequence number and 
   an acknowledgement of the received sequence number. These numbers
   are randomly initialized at the beginning of the session, and
   verified against expected numbers upon receipt. A message whose
   sequence numbers fall outside of the expected range are silently
   discarded. In addition to accomplishing orderly delivery of EAP
messages 
   and duplicate elimination, this scheme also helps prevent an
adversary 
   spoof messages to disturb ongoing PANA and EAP sessions unless it can

   also eavesdrop to synchronize on the sequence numbers. 

   The PANA framework defines EP which is ideally located on a
   network device that can filter traffic from the PaCs
   before the traffic enters the intranet. A set of filters can be used
to
   discard unauthorized packets, such as a PANA-Start-Request message
   that is received from the segment of the access network where only
   PaCs are supposed to be connected.

   The protocol also provides authentication and integrity protection to
   PANA messages when the used EAP method can generate cryptographic 
   session keys. PANA SA is generated based on the AAA-Key exported by
the 
   EAP method. This SA is used for generating per-packet MAC to protect
the 
   PANA header and payload (including the complete EAP message).  The 
   cryptographic protection prevents an adversary from acting as a 
   man-in-the-middle, injecting messages, replaying messages and
modifying 
   the content of the exchanged messages. Any packet that fails to pass
the
   MAC verification is silently discarded. The earliest this protection
can
   be enabled is when the very first PANA-Bind-Request that signals a
   successful authentication is generated. Starting with the 
   PANA-Bind-Request and PANA-Bind-Answer, any subsequent PANA message 
   until the session gets torn down can be cryptographically protected. 

   PANA SA enables authenticated and integrity protected exchange of
   the device ID information between the PaC and PAA. This ensures there
   were no man-in-the-middle during the PANA authentication.

   The lifetime of the PANA SA is bounded by the AAA-authorized
   session lifetime with an additional tolerance period.  Unless PANA
   state is updated by executing another EAP authentication, PANA SA is
   removed when the current session expires.  

   The ability to use cryptographic protection within PANA is determined
   by the used EAP method, which is generally dictated by the deployment
   environment. Unsecure lower-layers necessitate use of key-generating
   EAP methods. In networks where lower-layers are already secured, 
   cryprographic protection of PANA messages is not necessary. 

        
9.2. Discovery

   The initial discovery phase is vulnerable to spoofing attacks as
   these messages are not authenticated and integrity protected. In
order
   to prevent very basic denial-of service attacks an adversary should
not 
   be able to cause state creation by sending discovery messages to the 
   PAA. This protection is achieved by using a cookie-based scheme
(similar 
   to [RFC2522]) which allows the responder (PAA) to be stateless in the

   first round of message exchange. A return-routability test does not
   provide additional protection as PANA traffic is not routed but
   simply forwarded on-link. It is difficult to prevent this
   threat entirely.  

   In networks where lower-layers are not secured prior to running PANA,
   the capability discovery enabled through inclusion of
   Protection-Capability and Post-PANA-Address-Configuration AVPs in
   PANA-Start-Request message is susceptible to spoofing leading to 
   denial-of service attacks.  Therefore, usage of these AVPs during the

   discovery phase in such insecure networks is NOT RECOMMENDED.  The
same 
   AVPs are delivered via an integrity-protected PANA-Bind-Request upon 
   successful authentication.


9.3. EAP methods

   Eavesdropping EAP packets might cause problems when the EAP
   method is weak and enables dictionary or replay attacks or even
   allows an adversary to learn the long-term password directly.
   Furthermore, if the optional EAP Identity payload is used then it
   allows the adversary to learn the identity of the PaC.  In such a
   case a privacy problem is prevalent.

   To prevent these threats, [I-D.ietf-pana-framework] suggests using
   proper EAP methods for particular environments.  Depending on the
   deployment environment an EAP authentication which supports user 
   identity confidentiality, protection against dictionary attacks and 
   session key establishment must be used. It is therefore
   the responsibility of the network operators and users to choose
   a proper EAP method.


9.4. Separate NAP-ISP authentication

   PANA design allows running two separate EAP methods for the same
   PaC: one with the NAP, and one with the ISP. The process of arriving
at 
   the resultant authorization, which is a combination of the individual
   authorizations obtained from respective service providers, is outside
   the scope of this protocol. In the absence of lower-layer security, 
   both authentications MUST be able to generate a AAA-Key, leading to 
   generation of PANA SA. The resultant PANA SA cryptographically binds
   the two AAA-Keys together, hence it prevents man-in-the-middle
attacks.


9.5. Cryptographic keys

   When the EAP method exports a AAA-Key, this key is used to produce a 
   PANA SA with PANA_MAC_KEY with a distinct key ID. PANA_MAC_KEY is
unique 
   to the PANA session, and takes PANA-based nonce values into
computation 
   to cryptographically separate itself from the AAA-Key.

   PANA_MAC_KEY is solely used for authentication and integrity
protection
   of the PANA messages within the designated session.

   Two AAA-keys may be generated as a result of separate NAP and ISP 
   authentication. In that case, the AAA-key used with the PANA SA is
the
   combination of both keys. 

   The PANA SA lifetime is bounded by the AAA-Key lifetime. Another 
   execution of EAP method yields in a new AAA-Key, and updates 
   the PANA SA, PANA_MAC_KEY and key ID.

   Upon PaC's movement to a another PAA (new PAA) and request to perform
   a context transfer based optimization, the current PAA computes a
   AAA-key-int based on the AAA-Key, ID of new PAA, and the session ID. 
   This AAA-key-int is delivered to the new PAA, and used in the
   computation of AAA-key-new, which further takes a pair of nonce
values 
   into account. After this point on, the AAA-key-new becomes the
AAA-key
   between the PaC and the new PAA.

   When link-layer or network-layer ciphering [I-D.ietf-pana-ipsec] is 
   enabled as a result of successful PANA authentication, a separate
master 
   key is generated based on the AAA-Key, session ID, key ID, and EP ID.

   The lifetime of this key is bounded by the lifetime of the PANA SA.
This 
   key may be used with a secure association protocol 
   [I-D.ietf-ipsec-ikev2] to produce further cipher-specific and
transient 
   keys. 
   

9.6. Per-packet ciphering

   Networks that are not secured at the lower-layers prior to running  
   PANA can rely on enabling per-packet data traffic ciphering upon
   successful PANA session establishment. The PANA framework allows 
   generation of a master key from AAA-key for using with a per-packet 
   protection mechanism, such as link-layer or IPsec-based
   ciphering [I-D.ietf-pana-ipsec]. In case the master key is not
readily 
   useful to the ciphering mechanism, an additional secure association 
   protocol [I-D.ietf-ipsec-ikev2] may be needed to produce the required

   keying material. These mechanisms ultimately establish a
cryptographic 
   binding between the data traffic generated by and for a client and
the 
   authenticated identity of the client. Data traffic must be minimally 
   data origin authenticated, replay and integrity protected, and 
   optionally encrypted.

   
9.7. PAA-to-EP communication

   The PANA framework allows separation of PAA from EP(s). SNMPv3 
   [I-D.ietf-pana-snmp] is used between the the PAA and EP for
   provisioning authorized PaC information on the EP. This exchange MUST
be
   always physically or cryptographically protected for authentication,
   integrity and replay protection. It MUST also be privacy-protected
   when per-PaC master key for per-packet ciphering is transmitted to
the
   EP.

   The per-packet ciphering master key MUST be unique to the PaC and EP 
   pair. The session ID and EP's device ID are taken into computation
for 
   achieving this effect [I-D.ietf-pana-ipsec]. Compromise of an EP does

   not automatically lead to compromise of another EP or the PAA.

 
9.8. Livenes test         

   A PANA session is associated with a session lifetime.  The session is
   terminated unless it is refreshed by a new round of EAP
   authentication before it expires.  Therefore, at the latest a
   disconnected client can be detected when its lifetime expires.  A
   disconnect may also be detected earlier by using PANA
   reauthentication messages.  A request message can be generated by
   either PaC or PAA at any time and the peer must respond with an
   answer message.  A successful round-trip of this exchange is a simple
   verification that the peer is alive.  This test can be engaged when
   there is a possibility that the peer might have disconnected (e.g.,
   after discontinuation of data traffic).  Periodic use of this
   exchange as a keep-alive requires additional care as it might result
   in congestion and hence false alarms.  This exchange is
   cryptographically protected when PANA SA is available in order to
   prevent threats associated with the abuse of this functionality.


9.9. Mobility optimization

   The mobility optimization described in Section 4.12 involves the
   previous PAA providing a AAA-Key to the current PAA of the PaC.
   There are security risks stemming from potential compromise of PAAs.
   Compromise of the current PAA does not yield compromise of the
   previous PAA, as AAA-Key cannot be computed from a compromised
   AAA-Key-new.  But a compromised previous PAA along with the
   intercepted nonce values on the current link leads to the 
   compromise of AAA-Key-new. Operators should be aware of the potential

   risk of using this optimization.  An operator can reduce the risk 
   exposure by forcing the PaC to perform an EAP-based authentication 
   immediately after the PaC gains access to new link via the optimized
PANA 
   execution.


9.10. Updating PaC's IP address

   Even though the IP-Address AVP in a PANA-update-Request can be
   cryptographically protected by the MAC AVP, there is not way to
   prove the ownership of the IP address presented by the PaC. Hence
   an authorized PaC can launch a redirect attack by spoofing a victim's
   IP address. 


9.11. Early termination of a session

   The PANA protocol supports the ability for both the PaC and the PAA
   to transmit a tear-down message before the session lifetime expires.

   This message causes state removal, a stop of the accounting procedure

   and removes the installed per-PaC state on the EP(s). This message is

   cryptographically protected when PANA SA is present.
   



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


From pana-bounces@ietf.org  Thu Aug 19 17:13: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 RAA09900
	for <pana-archive@lists.ietf.org>; Thu, 19 Aug 2004 17:13: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 1BxtxG-0001IN-0F; Thu, 19 Aug 2004 16:56:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxsrJ-0008N7-TM
	for pana@megatron.ietf.org; Thu, 19 Aug 2004 15:46:02 -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 PAA28973
	for <pana@ietf.org>; Thu, 19 Aug 2004 15:46:00 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bxsxm-0003ON-4m
	for pana@ietf.org; Thu, 19 Aug 2004 15:52: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 <0I2P00901LJMJM@mailout2.samsung.com> for pana@ietf.org; Fri,
	20 Aug 2004 04:45: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 <0I2P0008NLJLVF@mailout2.samsung.com> for pana@ietf.org;
	Fri, 20 Aug 2004 04:45:22 +0900 (KST)
Received: from Alperyegin ([105.144.29.160])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I2P00G7ULJJM5@mmp1.samsung.com> for
	pana@ietf.org; Fri, 20 Aug 2004 04:45:21 +0900 (KST)
Date: Thu, 19 Aug 2004 12:45:18 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040819162320.GJ27839@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <007f01c48625$0f60f1a0$291d9069@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
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

> Should PANA-Ping-Request be allowed in discovery and initial handshake
> phase?


> Should PANA-Ping-Request be allowed in authentication phase?

I thought about these. I decided to let the ping behavior handle this
automatically. If there is an established pana session on the peer, it
will respond. Otherwise, ping request will be silently discarded. This
behavior can be followed in any state. [Also, PDI and PAR/PAN can be
sent even when there is an established PANA session. Hence ping should
work in that case.]

Alper
 


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


From pana-bounces@ietf.org  Thu Aug 19 17:19: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 RAA10506
	for <pana-archive@lists.ietf.org>; Thu, 19 Aug 2004 17:19: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 1Bxu9B-0000rv-OP; Thu, 19 Aug 2004 17:08:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bxtlt-0004dA-Fh
	for pana@megatron.ietf.org; Thu, 19 Aug 2004 16:44: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 QAA07266
	for <pana@ietf.org>; Thu, 19 Aug 2004 16:44:27 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxtsK-0006Lj-7g
	for pana@ietf.org; Thu, 19 Aug 2004 16:51: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 <0I2P00601O94NB@mailout3.samsung.com> for pana@ietf.org; Fri,
	20 Aug 2004 05:43:52 +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 <0I2P0026RO94BG@mailout3.samsung.com> for pana@ietf.org;
	Fri, 20 Aug 2004 05:43:52 +0900 (KST)
Received: from Alperyegin ([105.144.29.160])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I2P00386O92HY@mmp1.samsung.com> for
	pana@ietf.org; Fri, 20 Aug 2004 05:43:52 +0900 (KST)
Date: Thu, 19 Aug 2004 13:43:48 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <00f801c4862d$3baf48d0$291d9069@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: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7BIT
Subject: [Pana] do we need DI for PAA?
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

While looking at issue 104, I started to think maybe we don't need to
deal with PAA DI in the specification.

We need DI for PaC for controlling authorized traffic.
We need DI for EP(s) conveyed to PaC for secure association process.

DI of PAA seems to be in the picture for two things:
- identifying the PAA. I think for that we can directly use IP address
of PAA. [note: DI may be IP address or MAC address]. IP address of PAA
and DI of PaC can be exchanged during the PBR/PBA to detect MitM. 
- implicitly signaling the type of DI to PaC. I think we can do that by
including the DI of EP(s).

How about:
- Including the IP address of PAA in an IP-Address AVP, and one or more
Device-ID AVPs for EP(s) in PBR
- Including Device-ID AVP for PaC in PBA
- Deprecating EP-Device-ID AVP, using Device-ID AVP instead.

So that we confine the usage of DIs for PaC and EP, and keep the PAA out
of this.

Comments?

Alper






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


From pana-bounces@ietf.org  Thu Aug 19 19:33: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 TAA19452
	for <pana-archive@lists.ietf.org>; Thu, 19 Aug 2004 19:33: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 1BxwGM-00058G-JX; Thu, 19 Aug 2004 19:24:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxwC5-0003yp-1O
	for pana@megatron.ietf.org; Thu, 19 Aug 2004 19:19: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 TAA18451
	for <pana@ietf.org>; Thu, 19 Aug 2004 19:19:38 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxwIX-0001OS-Nf
	for pana@ietf.org; Thu, 19 Aug 2004 19:26:25 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7JNJNbv010672;
	Fri, 20 Aug 2004 08:19:23 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7JNJNKX026754;
	Fri, 20 Aug 2004 08:19:23 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	JAA26752 ; Fri, 20 Aug 2004 08:19:23 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA28707; Fri, 20 Aug 2004 08:19:23 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA02166;
	Fri, 20 Aug 2004 08:19:22 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7JNJL6t027767;
	Fri, 20 Aug 2004 08:19: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 <0I2P00EXGVG6SB@tsbpo1.po.toshiba.co.jp>; Fri,
	20 Aug 2004 08:19:21 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C9Axb-0007YX-00; Sun, 19 Sep 2004 16:19:11 -0700
Date: Sun, 19 Sep 2004 19:19:11 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] do we need DI for PAA?
In-reply-to: <00f801c4862d$3baf48d0$291d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040919231911.GA22998@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+20040803i
References: <00f801c4862d$3baf48d0$291d9069@sisa.samsung.com>
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
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 proposal makes sense to me.

Yoshihiro Ohba


On Thu, Aug 19, 2004 at 01:43:48PM -0700, Alper Yegin wrote:
> While looking at issue 104, I started to think maybe we don't need to
> deal with PAA DI in the specification.
> 
> We need DI for PaC for controlling authorized traffic.
> We need DI for EP(s) conveyed to PaC for secure association process.
> 
> DI of PAA seems to be in the picture for two things:
> - identifying the PAA. I think for that we can directly use IP address
> of PAA. [note: DI may be IP address or MAC address]. IP address of PAA
> and DI of PaC can be exchanged during the PBR/PBA to detect MitM. 
> - implicitly signaling the type of DI to PaC. I think we can do that by
> including the DI of EP(s).
> 
> How about:
> - Including the IP address of PAA in an IP-Address AVP, and one or more
> Device-ID AVPs for EP(s) in PBR
> - Including Device-ID AVP for PaC in PBA
> - Deprecating EP-Device-ID AVP, using Device-ID AVP instead.
> 
> So that we confine the usage of DIs for PaC and EP, and keep the PAA out
> of this.
> 
> Comments?
> 
> 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 Aug 19 19:49:25 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 TAA20347
	for <pana-archive@lists.ietf.org>; Thu, 19 Aug 2004 19:49:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BxwZg-0001FE-SU; Thu, 19 Aug 2004 19:44:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxwU2-0007YV-CK
	for pana@megatron.ietf.org; Thu, 19 Aug 2004 19:38:14 -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 TAA19684
	for <pana@ietf.org>; Thu, 19 Aug 2004 19:38:13 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BxwaY-0001pN-I0
	for pana@ietf.org; Thu, 19 Aug 2004 19:44:59 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7JNcBbv020675;
	Fri, 20 Aug 2004 08:38:11 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7JNcBEl013011;
	Fri, 20 Aug 2004 08:38:11 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	JAA13005 ; Fri, 20 Aug 2004 08:38:11 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA09215; Fri, 20 Aug 2004 08:38:10 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA21894;
	Fri, 20 Aug 2004 08:38:09 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7JNc96t008905;
	Fri, 20 Aug 2004 08: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 <0I2P00G73WBIQW@tsbpo1.po.toshiba.co.jp>; Fri,
	20 Aug 2004 08:38:08 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C9BEv-0007el-00; Sun, 19 Sep 2004 16:37:05 -0700
Date: Sun, 19 Sep 2004 19:37:05 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <007f01c48625$0f60f1a0$291d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040919233705.GB22998@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+20040803i
References: <20040819162320.GJ27839@steelhead>
	<007f01c48625$0f60f1a0$291d9069@sisa.samsung.com>
X-Spam-Score: 2.4 (++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
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, Aug 19, 2004 at 12:45:18PM -0700, Alper Yegin wrote:
> > Should PANA-Ping-Request be allowed in discovery and initial handshake
> > phase?
> 
> 
> > Should PANA-Ping-Request be allowed in authentication phase?
> 
> I thought about these. I decided to let the ping behavior handle this
> automatically. If there is an established pana session on the peer, it
> will respond. Otherwise, ping request will be silently discarded. This
> behavior can be followed in any state. [Also, PDI and PAR/PAN can be
> sent even when there is an established PANA session. Hence ping should
> work in that case.]

It is probablly easier to do that at the receiving side of the ping
request, but what about transmitting side?  If we allow a PAA or a PaC
to send a PANA-Ping-Request and receiving a PANA-Ping-Answer between
two consecutive PANA-Auth-Request/Answer exchanges in authentication
phase, it would complicate the state machines (probably one additional
state is needed to support this case in the PaC and PAA state
machines).  I have a similar observation for PANA pinging in discovery
and initial handshake phase.

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 Aug 19 19:59:40 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 TAA20708
	for <pana-archive@lists.ietf.org>; Thu, 19 Aug 2004 19:59:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bxwkm-0003tl-Gf; Thu, 19 Aug 2004 19:55:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bxwe3-0002Lc-Mq
	for pana@megatron.ietf.org; Thu, 19 Aug 2004 19:48: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 TAA20316
	for <pana@ietf.org>; Thu, 19 Aug 2004 19:48:34 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bxwka-00022l-5v
	for pana@ietf.org; Thu, 19 Aug 2004 19:55:20 -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 <0I2P00L08WS37T@mailout2.samsung.com> for pana@ietf.org; Fri,
	20 Aug 2004 08:48:03 +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 <0I2P00JZNWS0VX@mailout2.samsung.com> for pana@ietf.org;
	Fri, 20 Aug 2004 08:48:00 +0900 (KST)
Received: from Alperyegin ([105.144.29.160])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I2P0067PWRYSU@mmp1.samsung.com> for
	pana@ietf.org; Fri, 20 Aug 2004 08:48:00 +0900 (KST)
Date: Thu, 19 Aug 2004 16:47:57 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040919233705.GB22998@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <000301c48646$f57e8a00$a01d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 244a2fd369eaf00ce6820a760a3de2e8
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,

I never thought we would need to deal with PANA-ping in the state
machine.
I perceive it as a tool that can be used asynchronous to the state
machine, and does not automatically impact the state machine. [Sure,
PANA implementation can use PANA ping to discover dead-peer, just like
it could use ICMP echos, or L2 indications]. If a state had explicitly
called for using PANA-ping, then we must have incorporated it in the
state machine.

Alper


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Sunday, September 19, 2004 4:37 PM
> To: Alper Yegin
> Cc: 'Yoshihiro Ohba'; pana@ietf.org
> Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
"reauth"
> messages
> 
> On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper Yegin wrote:
> > > Should PANA-Ping-Request be allowed in discovery and initial
handshake
> > > phase?
> >
> >
> > > Should PANA-Ping-Request be allowed in authentication phase?
> >
> > I thought about these. I decided to let the ping behavior handle
this
> > automatically. If there is an established pana session on the peer,
it
> > will respond. Otherwise, ping request will be silently discarded.
This
> > behavior can be followed in any state. [Also, PDI and PAR/PAN can be
> > sent even when there is an established PANA session. Hence ping
should
> > work in that case.]
> 
> It is probablly easier to do that at the receiving side of the ping
> request, but what about transmitting side?  If we allow a PAA or a PaC
> to send a PANA-Ping-Request and receiving a PANA-Ping-Answer between
> two consecutive PANA-Auth-Request/Answer exchanges in authentication
> phase, it would complicate the state machines (probably one additional
> state is needed to support this case in the PaC and PAA state
> machines).  I have a similar observation for PANA pinging in discovery
> and initial handshake phase.
> 
> 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 Aug 19 20:21: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 UAA21525
	for <pana-archive@lists.ietf.org>; Thu, 19 Aug 2004 20:21:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bxx6S-0007op-2M; Thu, 19 Aug 2004 20:17:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bxx1y-0007BL-2x
	for pana@megatron.ietf.org; Thu, 19 Aug 2004 20:13:18 -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 UAA21256
	for <pana@ietf.org>; Thu, 19 Aug 2004 20:13:16 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bxx8U-0002Q0-7K
	for pana@ietf.org; Thu, 19 Aug 2004 20:20:03 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7K0DBbv014753;
	Fri, 20 Aug 2004 09:13:11 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7K0DB1T024327;
	Fri, 20 Aug 2004 09:13:11 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	KAA24319 ; Fri, 20 Aug 2004 09:13:11 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA05931; Fri, 20 Aug 2004 09:13:10 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA18447;
	Fri, 20 Aug 2004 09:13:07 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7K0D76t001894;
	Fri, 20 Aug 2004 09:13:07 +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 <0I2P00JMAXXRS7@tsbpo1.po.toshiba.co.jp>; Fri,
	20 Aug 2004 09:13:06 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C9Bmf-0007qw-00; Sun, 19 Sep 2004 17:11:57 -0700
Date: Sun, 19 Sep 2004 20:11:57 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <000301c48646$f57e8a00$a01d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040920001157.GC22998@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+20040803i
References: <20040919233705.GB22998@steelhead>
	<000301c48646$f57e8a00$a01d9069@sisa.samsung.com>
X-Spam-Score: 2.4 (++)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
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 draft-ohba-pana-statemachine-00.txt, there is a state WAIT_PRAA
(which transits only from OPEN state) in both PaC and PAA state
machines to wait for PANA-Reauth-Answer after sending
PANA-Reauth-Request.  Since we are replacing PANA-Requth-* with
PANA-Ping-*, the WAIT_PRAA state would be replaced with WAIT_PPA.  I
am afraid if we need additional transitions to the WAIT_PPA state from
several states, it would complicate the state machines and I am
wondering what is the benefit of adding such complexity.

Yoshihiro Ohba

On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper Yegin wrote:
> Yoshi,
> 
> I never thought we would need to deal with PANA-ping in the state
> machine.
> I perceive it as a tool that can be used asynchronous to the state
> machine, and does not automatically impact the state machine. [Sure,
> PANA implementation can use PANA ping to discover dead-peer, just like
> it could use ICMP echos, or L2 indications]. If a state had explicitly
> called for using PANA-ping, then we must have incorporated it in the
> state machine.
> 
> Alper
> 
> 
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Sunday, September 19, 2004 4:37 PM
> > To: Alper Yegin
> > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
> "reauth"
> > messages
> > 
> > On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper Yegin wrote:
> > > > Should PANA-Ping-Request be allowed in discovery and initial
> handshake
> > > > phase?
> > >
> > >
> > > > Should PANA-Ping-Request be allowed in authentication phase?
> > >
> > > I thought about these. I decided to let the ping behavior handle
> this
> > > automatically. If there is an established pana session on the peer,
> it
> > > will respond. Otherwise, ping request will be silently discarded.
> This
> > > behavior can be followed in any state. [Also, PDI and PAR/PAN can be
> > > sent even when there is an established PANA session. Hence ping
> should
> > > work in that case.]
> > 
> > It is probablly easier to do that at the receiving side of the ping
> > request, but what about transmitting side?  If we allow a PAA or a PaC
> > to send a PANA-Ping-Request and receiving a PANA-Ping-Answer between
> > two consecutive PANA-Auth-Request/Answer exchanges in authentication
> > phase, it would complicate the state machines (probably one additional
> > state is needed to support this case in the PaC and PAA state
> > machines).  I have a similar observation for PANA pinging in discovery
> > and initial handshake phase.
> > 
> > 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 Aug 19 20:53: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 UAA22921
	for <pana-archive@lists.ietf.org>; Thu, 19 Aug 2004 20:53: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 1Bxxbc-00054s-Gl; Thu, 19 Aug 2004 20:50:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BxxUc-0003kq-Il
	for pana@megatron.ietf.org; Thu, 19 Aug 2004 20:42: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 UAA22475
	for <pana@ietf.org>; Thu, 19 Aug 2004 20:42:53 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bxxb9-0002qy-AZ
	for pana@ietf.org; Thu, 19 Aug 2004 20:49:39 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7K0gpbv009326;
	Fri, 20 Aug 2004 09:42:51 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7K0gpA6003742;
	Fri, 20 Aug 2004 09:42:51 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	KAA03737 ; Fri, 20 Aug 2004 09:42:50 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA01339; Fri, 20 Aug 2004 09:42:50 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA07537;
	Fri, 20 Aug 2004 09:42:49 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7K0gn6t022862;
	Fri, 20 Aug 2004 09:42:49 +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 <0I2P00MTNZB9Y8@tsbpo1.po.toshiba.co.jp>; Fri,
	20 Aug 2004 09:42:48 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C9CFf-00081K-00; Sun, 19 Sep 2004 17:41:55 -0700
Date: Sun, 19 Sep 2004 20:41:54 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040920004154.GF22998@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+20040803i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: [Pana] framework open issue
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

Section 11 of draft-ietf-pana-framework-01.txt says:

"
11.  Open Issue


   Certain combination of network environments and timing cases may
   require further considerations.


   If PaC changes access point right after a successful PANA
   authorization but before POPA configuration, it might be confused
   whether the new IP address configured via the new access point is the
   POPA of the ongoing session or a PRPA of a new session.  When the
   PRPA and POPA types or configuration mechanisms are different this is
   not a problem.  One possible combination where such clues are not
   available is when PaC moves from a Case A of Section 10.2.1.1
   (IPsec-TIA obtained by using DHCPv4) network to a Case D of Appendix
   A.1 (IPsec-TIA obtained by using RFC3118) network.


   In another example, when PaC switches from one wired Ethernet hub to
   another (without the use of bootstrapping IPsec) before configuring
   the POPA.  In this case, PaC may not able to know whether an obtained
   address is the POPA in the same subnet or a PRPA in a new subnet.
"

I think the above issue is related to DNA and not necessarily a PANA
framework issue (i.e., DNA can deal with this issue.)

Suggested change: Remove this section.

Yoshihiro Ohba


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


From pana-bounces@ietf.org  Fri Aug 20 10:10: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 KAA14818
	for <pana-archive@lists.ietf.org>; Fri, 20 Aug 2004 10:10: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 1By9eC-0007tB-Fb; Fri, 20 Aug 2004 09:41:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1By9RZ-0005MH-Ao
	for pana@megatron.ietf.org; Fri, 20 Aug 2004 09:28: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 JAA12151
	for <pana@ietf.org>; Fri, 20 Aug 2004 09:28:26 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1By9Y6-0007NP-Mx
	for pana@ietf.org; Fri, 20 Aug 2004 09:35:20 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7KDSNbv011161;
	Fri, 20 Aug 2004 22:28:23 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7KDSNai014106;
	Fri, 20 Aug 2004 22:28:23 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	YAA14105 ; Fri, 20 Aug 2004 22:28:23 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA11588; Fri, 20 Aug 2004 22:28:22 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA26565;
	Fri, 20 Aug 2004 22:28:21 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7KDSL6t023418;
	Fri, 20 Aug 2004 22:28: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 <0I2Q003ZVYR6ZO@tsbpo1.po.toshiba.co.jp>; Fri,
	20 Aug 2004 22:28:20 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C9OD9-0000TK-00; Mon, 20 Sep 2004 06:28:07 -0700
Date: Mon, 20 Sep 2004 09:28:05 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue106: sequence number on rexmited messages must be
	incremented
In-reply-to: <008601c483bd$1924db80$0041fea9@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040920132804.GG22998@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>,
	'Erik Nordmark' <Erik.Nordmark@Sun.COM>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040803i
References: <008601c483bd$1924db80$0041fea9@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: "'Erik Nordmark'" <Erik.Nordmark@Sun.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

If a retransmitted packet has a new sequence number, the sender would
need to re-generate a new MAC AVP for every retransmitted packet that
contains a MAC AVP, since the MAC computation covers PANA header.

This could be a performance issue at PAA which may have a large number
of retransmitted messages to different PaCs.  Also, if we don't change
the sequence number for retransmitted packets, implementation would be
much more simpler.

Yoshihiro Ohba


On Mon, Aug 16, 2004 at 11:16:04AM -0700, Alper Yegin wrote:
> Hi Erik,
> 
> In your review feedback, you had said:
> 
> - the retransmission text says that a retransmitted packet has a new 
>   sequence number. This makes no sense to me.
> 
> Can you please elaborate what kind of issues you are seeing with this.
> 
> Thank you.
> 
> 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 Aug 20 12:52:26 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 MAA26876
	for <pana-archive@lists.ietf.org>; Fri, 20 Aug 2004 12:52:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ByBhS-0001m1-55; Fri, 20 Aug 2004 11:53:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ByBB8-0001pe-L1
	for pana@megatron.ietf.org; Fri, 20 Aug 2004 11:19:42 -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 LAA20186
	for <pana@ietf.org>; Fri, 20 Aug 2004 11:19: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 1ByBHe-0001Bk-6C
	for pana@ietf.org; Fri, 20 Aug 2004 11:26:30 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7KFJVbv019589;
	Sat, 21 Aug 2004 00:19:31 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7KFJUpX011391;
	Sat, 21 Aug 2004 00:19:30 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	AAA11390 ; Sat, 21 Aug 2004 00:19:30 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA17004; Sat, 21 Aug 2004 00:19:30 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA07808;
	Sat, 21 Aug 2004 00:19:30 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7KFJT6t018702;
	Sat, 21 Aug 2004 00:19:29 +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 <0I2R00G7U3WE5U@tsbpo1.po.toshiba.co.jp>; Sat,
	21 Aug 2004 00:19:28 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C9Pvo-0001De-00; Mon, 20 Sep 2004 08:18:20 -0700
Date: Mon, 20 Sep 2004 11:18:20 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 94 and 95 - proposed text
In-reply-to: <007a01c48624$1ef39100$291d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040920151820.GD3131@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+20040803i
References: <007a01c48624$1ef39100$291d9069@sisa.samsung.com>
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
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 text looks very nice.  Maybe "PANA reauthentication messages" in
section 9.8 is replaced with "PANA ping messages".

Yoshihro Ohba

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


From pana-bounces@ietf.org  Fri Aug 20 15:18: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 PAA07928
	for <pana-archive@lists.ietf.org>; Fri, 20 Aug 2004 15:18: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 1ByE3v-0005QF-A0; Fri, 20 Aug 2004 14:24:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ByDIs-00076A-Mw
	for pana@megatron.ietf.org; Fri, 20 Aug 2004 13:35:50 -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 NAA00741
	for <pana@ietf.org>; Fri, 20 Aug 2004 13:35:43 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ByDPT-0004Ik-7l
	for pana@ietf.org; Fri, 20 Aug 2004 13:42:39 -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 <0I2R00501A6O6F@mailout1.samsung.com> for pana@ietf.org; Sat,
	21 Aug 2004 02:35:12 +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 <0I2R000PMA6N4G@mailout1.samsung.com> for pana@ietf.org;
	Sat, 21 Aug 2004 02:35:12 +0900 (KST)
Received: from Alperyegin ([105.253.155.54])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I2R00LAHA6KQ9@mmp2.samsung.com> for
	pana@ietf.org; Sat, 21 Aug 2004 02:35:11 +0900 (KST)
Date: Fri, 20 Aug 2004 10:35:07 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040920001157.GC22998@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <005201c486dc$0a8a0100$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 6d95a152022472c7d6cdf886a0424dc6
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

I'm trying not to limit use of PANA-ping to only OPEN state. I think we
don't have to incorporate PANA-ping to the state machine. It can have
its own state machine (if that makes sense), disjoint to the main one.

Alper


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Sunday, September 19, 2004 5:12 PM
> To: Alper Yegin
> Cc: 'Yoshihiro Ohba'; pana@ietf.org
> Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
"reauth"
> messages
> 
> In draft-ohba-pana-statemachine-00.txt, there is a state WAIT_PRAA
> (which transits only from OPEN state) in both PaC and PAA state
> machines to wait for PANA-Reauth-Answer after sending
> PANA-Reauth-Request.  Since we are replacing PANA-Requth-* with
> PANA-Ping-*, the WAIT_PRAA state would be replaced with WAIT_PPA.  I
> am afraid if we need additional transitions to the WAIT_PPA state from
> several states, it would complicate the state machines and I am
> wondering what is the benefit of adding such complexity.
> 
> Yoshihiro Ohba
> 
> On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper Yegin wrote:
> > Yoshi,
> >
> > I never thought we would need to deal with PANA-ping in the state
> > machine.
> > I perceive it as a tool that can be used asynchronous to the state
> > machine, and does not automatically impact the state machine. [Sure,
> > PANA implementation can use PANA ping to discover dead-peer, just
like
> > it could use ICMP echos, or L2 indications]. If a state had
explicitly
> > called for using PANA-ping, then we must have incorporated it in the
> > state machine.
> >
> > Alper
> >
> >
> > > -----Original Message-----
> > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: Sunday, September 19, 2004 4:37 PM
> > > To: Alper Yegin
> > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
> > "reauth"
> > > messages
> > >
> > > On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper Yegin wrote:
> > > > > Should PANA-Ping-Request be allowed in discovery and initial
> > handshake
> > > > > phase?
> > > >
> > > >
> > > > > Should PANA-Ping-Request be allowed in authentication phase?
> > > >
> > > > I thought about these. I decided to let the ping behavior handle
> > this
> > > > automatically. If there is an established pana session on the
peer,
> > it
> > > > will respond. Otherwise, ping request will be silently
discarded.
> > This
> > > > behavior can be followed in any state. [Also, PDI and PAR/PAN
can be
> > > > sent even when there is an established PANA session. Hence ping
> > should
> > > > work in that case.]
> > >
> > > It is probablly easier to do that at the receiving side of the
ping
> > > request, but what about transmitting side?  If we allow a PAA or a
PaC
> > > to send a PANA-Ping-Request and receiving a PANA-Ping-Answer
between
> > > two consecutive PANA-Auth-Request/Answer exchanges in
authentication
> > > phase, it would complicate the state machines (probably one
additional
> > > state is needed to support this case in the PaC and PAA state
> > > machines).  I have a similar observation for PANA pinging in
discovery
> > > and initial handshake phase.
> > >
> > > 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 Aug 20 15:58:26 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 PAA10096
	for <pana-archive@lists.ietf.org>; Fri, 20 Aug 2004 15:58:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ByEvs-0007pt-88; Fri, 20 Aug 2004 15:20:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ByENK-0001an-4o
	for pana@megatron.ietf.org; Fri, 20 Aug 2004 14:44:30 -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 OAA05001
	for <pana@ietf.org>; Fri, 20 Aug 2004 14:44:23 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ByETv-0005mt-Fk
	for pana@ietf.org; Fri, 20 Aug 2004 14:51:20 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7KIiLbv018830;
	Sat, 21 Aug 2004 03:44:21 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7KIiLip008353;
	Sat, 21 Aug 2004 03:44:21 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	DAA08351 ; Sat, 21 Aug 2004 03:44:21 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA14946; Sat, 21 Aug 2004 03:44:21 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA08164;
	Sat, 21 Aug 2004 03:44:20 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7KIiK6t008745;
	Sat, 21 Aug 2004 03:44:20 +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 <0I2R00LGJDDTSD@tsbpo1.po.toshiba.co.jp>; Sat,
	21 Aug 2004 03:44:19 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C9T8R-0002Ie-00; Mon, 20 Sep 2004 11:43:35 -0700
Date: Mon, 20 Sep 2004 14:43:34 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <005201c486dc$0a8a0100$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040920184334.GE3131@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+20040803i
References: <20040920001157.GC22998@steelhead>
	<005201c486dc$0a8a0100$6401a8c0@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
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, Aug 20, 2004 at 10:35:07AM -0700, Alper Yegin wrote:
> I'm trying not to limit use of PANA-ping to only OPEN state. I think we
> don't have to incorporate PANA-ping to the state machine. It can have
> its own state machine (if that makes sense), disjoint to the main one.

The disjointing approach does not make much sense to me if PANA is
designed as a lock-step protocol for which multiple outstanding
requests are not allowed.  For example, EAP is a lock-step protocol.
If PANA is designed to be a non-lock-step protocol, a ping request can
be sent even if there is an outstanding request, for which case
disjointing would make sense.

Question: Is PANA a lock-step protocol?

Yoshihiro Ohba


> 
> Alper
> 
> 
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Sunday, September 19, 2004 5:12 PM
> > To: Alper Yegin
> > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
> "reauth"
> > messages
> > 
> > In draft-ohba-pana-statemachine-00.txt, there is a state WAIT_PRAA
> > (which transits only from OPEN state) in both PaC and PAA state
> > machines to wait for PANA-Reauth-Answer after sending
> > PANA-Reauth-Request.  Since we are replacing PANA-Requth-* with
> > PANA-Ping-*, the WAIT_PRAA state would be replaced with WAIT_PPA.  I
> > am afraid if we need additional transitions to the WAIT_PPA state from
> > several states, it would complicate the state machines and I am
> > wondering what is the benefit of adding such complexity.
> > 
> > Yoshihiro Ohba
> > 
> > On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper Yegin wrote:
> > > Yoshi,
> > >
> > > I never thought we would need to deal with PANA-ping in the state
> > > machine.
> > > I perceive it as a tool that can be used asynchronous to the state
> > > machine, and does not automatically impact the state machine. [Sure,
> > > PANA implementation can use PANA ping to discover dead-peer, just
> like
> > > it could use ICMP echos, or L2 indications]. If a state had
> explicitly
> > > called for using PANA-ping, then we must have incorporated it in the
> > > state machine.
> > >
> > > Alper
> > >
> > >
> > > > -----Original Message-----
> > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: Sunday, September 19, 2004 4:37 PM
> > > > To: Alper Yegin
> > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
> > > "reauth"
> > > > messages
> > > >
> > > > On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper Yegin wrote:
> > > > > > Should PANA-Ping-Request be allowed in discovery and initial
> > > handshake
> > > > > > phase?
> > > > >
> > > > >
> > > > > > Should PANA-Ping-Request be allowed in authentication phase?
> > > > >
> > > > > I thought about these. I decided to let the ping behavior handle
> > > this
> > > > > automatically. If there is an established pana session on the
> peer,
> > > it
> > > > > will respond. Otherwise, ping request will be silently
> discarded.
> > > This
> > > > > behavior can be followed in any state. [Also, PDI and PAR/PAN
> can be
> > > > > sent even when there is an established PANA session. Hence ping
> > > should
> > > > > work in that case.]
> > > >
> > > > It is probablly easier to do that at the receiving side of the
> ping
> > > > request, but what about transmitting side?  If we allow a PAA or a
> PaC
> > > > to send a PANA-Ping-Request and receiving a PANA-Ping-Answer
> between
> > > > two consecutive PANA-Auth-Request/Answer exchanges in
> authentication
> > > > phase, it would complicate the state machines (probably one
> additional
> > > > state is needed to support this case in the PaC and PAA state
> > > > machines).  I have a similar observation for PANA pinging in
> discovery
> > > > and initial handshake phase.
> > > >
> > > > 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 Aug 20 16:47: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 QAA13125
	for <pana-archive@lists.ietf.org>; Fri, 20 Aug 2004 16:47: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 1ByFki-0007nm-54; Fri, 20 Aug 2004 16:12:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ByFKu-0006xF-DD
	for pana@megatron.ietf.org; Fri, 20 Aug 2004 15:46: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 PAA09447
	for <pana@ietf.org>; Fri, 20 Aug 2004 15:45:57 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ByFRT-00070y-9C
	for pana@ietf.org; Fri, 20 Aug 2004 15:52:55 -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 <0I2R00B08G7M3E@mailout1.samsung.com> for pana@ietf.org; Sat,
	21 Aug 2004 04:45:22 +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 <0I2R001UUG7M7G@mailout1.samsung.com> for pana@ietf.org;
	Sat, 21 Aug 2004 04:45:22 +0900 (KST)
Received: from Alperyegin ([105.253.155.54])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I2R001PMG7HW4@mmp1.samsung.com> for
	pana@ietf.org; Sat, 21 Aug 2004 04:45:22 +0900 (KST)
Date: Fri, 20 Aug 2004 12:45:14 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040920184334.GE3131@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <005701c486ee$391ff2b0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 2e8fc473f5174be667965460bd5288ba
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

> > I'm trying not to limit use of PANA-ping to only OPEN state. I think
we
> > don't have to incorporate PANA-ping to the state machine. It can
have
> > its own state machine (if that makes sense), disjoint to the main
one.
> 
> The disjointing approach does not make much sense to me if PANA is
> designed as a lock-step protocol for which multiple outstanding
> requests are not allowed.  For example, EAP is a lock-step protocol.
> If PANA is designed to be a non-lock-step protocol, a ping request can
> be sent even if there is an outstanding request, for which case
> disjointing would make sense.
> 
> Question: Is PANA a lock-step protocol?

I'm not sure if this is the right question. I think we should be trying
to answer if PANA-ping is ever needed when the sender is not in OPEN
state. 

I see at least two cases:
a- using PANA-ping for debugging. In that case you want to be able to
use it in any state (e.g., in the middle of a hung WAIT_* state).
b- to discover the state of the peer (e.g., after a crash and reboot.
Before the crash, the sender might have been in a state other than
OPEN).

Alper
 




> 
> Yoshihiro Ohba
> 
> 
> >
> > Alper
> >
> >
> > > -----Original Message-----
> > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: Sunday, September 19, 2004 5:12 PM
> > > To: Alper Yegin
> > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
> > "reauth"
> > > messages
> > >
> > > In draft-ohba-pana-statemachine-00.txt, there is a state WAIT_PRAA
> > > (which transits only from OPEN state) in both PaC and PAA state
> > > machines to wait for PANA-Reauth-Answer after sending
> > > PANA-Reauth-Request.  Since we are replacing PANA-Requth-* with
> > > PANA-Ping-*, the WAIT_PRAA state would be replaced with WAIT_PPA.
I
> > > am afraid if we need additional transitions to the WAIT_PPA state
from
> > > several states, it would complicate the state machines and I am
> > > wondering what is the benefit of adding such complexity.
> > >
> > > Yoshihiro Ohba
> > >
> > > On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper Yegin wrote:
> > > > Yoshi,
> > > >
> > > > I never thought we would need to deal with PANA-ping in the
state
> > > > machine.
> > > > I perceive it as a tool that can be used asynchronous to the
state
> > > > machine, and does not automatically impact the state machine.
[Sure,
> > > > PANA implementation can use PANA ping to discover dead-peer,
just
> > like
> > > > it could use ICMP echos, or L2 indications]. If a state had
> > explicitly
> > > > called for using PANA-ping, then we must have incorporated it in
the
> > > > state machine.
> > > >
> > > > Alper
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > Sent: Sunday, September 19, 2004 4:37 PM
> > > > > To: Alper Yegin
> > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage
of
> > > > "reauth"
> > > > > messages
> > > > >
> > > > > On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper Yegin wrote:
> > > > > > > Should PANA-Ping-Request be allowed in discovery and
initial
> > > > handshake
> > > > > > > phase?
> > > > > >
> > > > > >
> > > > > > > Should PANA-Ping-Request be allowed in authentication
phase?
> > > > > >
> > > > > > I thought about these. I decided to let the ping behavior
handle
> > > > this
> > > > > > automatically. If there is an established pana session on
the
> > peer,
> > > > it
> > > > > > will respond. Otherwise, ping request will be silently
> > discarded.
> > > > This
> > > > > > behavior can be followed in any state. [Also, PDI and
PAR/PAN
> > can be
> > > > > > sent even when there is an established PANA session. Hence
ping
> > > > should
> > > > > > work in that case.]
> > > > >
> > > > > It is probablly easier to do that at the receiving side of the
> > ping
> > > > > request, but what about transmitting side?  If we allow a PAA
or a
> > PaC
> > > > > to send a PANA-Ping-Request and receiving a PANA-Ping-Answer
> > between
> > > > > two consecutive PANA-Auth-Request/Answer exchanges in
> > authentication
> > > > > phase, it would complicate the state machines (probably one
> > additional
> > > > > state is needed to support this case in the PaC and PAA state
> > > > > machines).  I have a similar observation for PANA pinging in
> > discovery
> > > > > and initial handshake phase.
> > > > >
> > > > > 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 Aug 20 17:32: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 RAA15546
	for <pana-archive@lists.ietf.org>; Fri, 20 Aug 2004 17:32: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 1ByGUW-0003yb-DQ; Fri, 20 Aug 2004 17:00:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ByG28-0003oA-4F
	for pana@megatron.ietf.org; Fri, 20 Aug 2004 16:30:44 -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 QAA12094
	for <pana@ietf.org>; Fri, 20 Aug 2004 16:30:36 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ByG8k-00088H-4Z
	for pana@ietf.org; Fri, 20 Aug 2004 16:37:34 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7KKUabv018585;
	Sat, 21 Aug 2004 05:30:36 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7KKUZT7023601;
	Sat, 21 Aug 2004 05:30:35 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	FAA23600 ; Sat, 21 Aug 2004 05:30:35 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id FAA11865; Sat, 21 Aug 2004 05:30:35 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id FAA02633;
	Sat, 21 Aug 2004 05:30:34 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7KKUY6t017139;
	Sat, 21 Aug 2004 05:30:34 +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 <0I2R002H4IATTJ@tsbpo1.po.toshiba.co.jp>; Sat,
	21 Aug 2004 05:30:33 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1CKN5U-0002sg-00; Wed, 20 Oct 2004 13:29:36 -0700
Date: Wed, 20 Oct 2004 16:29:36 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <005701c486ee$391ff2b0$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20041020202936.GF3131@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+20040803i
References: <20040920184334.GE3131@steelhead>
	<005701c486ee$391ff2b0$6401a8c0@sisa.samsung.com>
X-Spam-Score: 2.4 (++)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
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, Aug 20, 2004 at 12:45:14PM -0700, Alper Yegin wrote:
> > > I'm trying not to limit use of PANA-ping to only OPEN state. I think
> we
> > > don't have to incorporate PANA-ping to the state machine. It can
> have
> > > its own state machine (if that makes sense), disjoint to the main
> one.
> > 
> > The disjointing approach does not make much sense to me if PANA is
> > designed as a lock-step protocol for which multiple outstanding
> > requests are not allowed.  For example, EAP is a lock-step protocol.
> > If PANA is designed to be a non-lock-step protocol, a ping request can
> > be sent even if there is an outstanding request, for which case
> > disjointing would make sense.
> > 
> > Question: Is PANA a lock-step protocol?
> 
> I'm not sure if this is the right question. I think we should be trying
> to answer if PANA-ping is ever needed when the sender is not in OPEN
> state. 
> 
> I see at least two cases:
> a- using PANA-ping for debugging. In that case you want to be able to
> use it in any state (e.g., in the middle of a hung WAIT_* state).

I think we can use other tools for debugging as we normally do for
other protocol implementations.

> b- to discover the state of the peer (e.g., after a crash and reboot.
> Before the crash, the sender might have been in a state other than
> OPEN).

Can't a simple method "wait for the current authentication session to
fail" be used here?  I do not have a serious demand on doing liveness
test for an incomplete session (but others may have...).

Yoshihiro Ohba


> 
> Alper
>  
> 
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > >
> > > Alper
> > >
> > >
> > > > -----Original Message-----
> > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: Sunday, September 19, 2004 5:12 PM
> > > > To: Alper Yegin
> > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
> > > "reauth"
> > > > messages
> > > >
> > > > In draft-ohba-pana-statemachine-00.txt, there is a state WAIT_PRAA
> > > > (which transits only from OPEN state) in both PaC and PAA state
> > > > machines to wait for PANA-Reauth-Answer after sending
> > > > PANA-Reauth-Request.  Since we are replacing PANA-Requth-* with
> > > > PANA-Ping-*, the WAIT_PRAA state would be replaced with WAIT_PPA.
> I
> > > > am afraid if we need additional transitions to the WAIT_PPA state
> from
> > > > several states, it would complicate the state machines and I am
> > > > wondering what is the benefit of adding such complexity.
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > > On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper Yegin wrote:
> > > > > Yoshi,
> > > > >
> > > > > I never thought we would need to deal with PANA-ping in the
> state
> > > > > machine.
> > > > > I perceive it as a tool that can be used asynchronous to the
> state
> > > > > machine, and does not automatically impact the state machine.
> [Sure,
> > > > > PANA implementation can use PANA ping to discover dead-peer,
> just
> > > like
> > > > > it could use ICMP echos, or L2 indications]. If a state had
> > > explicitly
> > > > > called for using PANA-ping, then we must have incorporated it in
> the
> > > > > state machine.
> > > > >
> > > > > Alper
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > > Sent: Sunday, September 19, 2004 4:37 PM
> > > > > > To: Alper Yegin
> > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage
> of
> > > > > "reauth"
> > > > > > messages
> > > > > >
> > > > > > On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper Yegin wrote:
> > > > > > > > Should PANA-Ping-Request be allowed in discovery and
> initial
> > > > > handshake
> > > > > > > > phase?
> > > > > > >
> > > > > > >
> > > > > > > > Should PANA-Ping-Request be allowed in authentication
> phase?
> > > > > > >
> > > > > > > I thought about these. I decided to let the ping behavior
> handle
> > > > > this
> > > > > > > automatically. If there is an established pana session on
> the
> > > peer,
> > > > > it
> > > > > > > will respond. Otherwise, ping request will be silently
> > > discarded.
> > > > > This
> > > > > > > behavior can be followed in any state. [Also, PDI and
> PAR/PAN
> > > can be
> > > > > > > sent even when there is an established PANA session. Hence
> ping
> > > > > should
> > > > > > > work in that case.]
> > > > > >
> > > > > > It is probablly easier to do that at the receiving side of the
> > > ping
> > > > > > request, but what about transmitting side?  If we allow a PAA
> or a
> > > PaC
> > > > > > to send a PANA-Ping-Request and receiving a PANA-Ping-Answer
> > > between
> > > > > > two consecutive PANA-Auth-Request/Answer exchanges in
> > > authentication
> > > > > > phase, it would complicate the state machines (probably one
> > > additional
> > > > > > state is needed to support this case in the PaC and PAA state
> > > > > > machines).  I have a similar observation for PANA pinging in
> > > discovery
> > > > > > and initial handshake phase.
> > > > > >
> > > > > > 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  Mon Aug 23 15:26:25 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 PAA04192
	for <pana-archive@lists.ietf.org>; Mon, 23 Aug 2004 15:26:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1BzK4v-0004wO-Q7; Mon, 23 Aug 2004 15:02:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzJk2-0007Ht-8i
	for pana@megatron.ietf.org; Mon, 23 Aug 2004 14:40:26 -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 OAA29938
	for <pana@ietf.org>; Mon, 23 Aug 2004 14:40:19 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzJkH-0002mD-Db
	for pana@ietf.org; Mon, 23 Aug 2004 14:40:44 -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 <0I2W00A01X6A94@mailout2.samsung.com> for pana@ietf.org; Tue,
	24 Aug 2004 03:39:46 +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 <0I2W00DH3X69J1@mailout2.samsung.com> for pana@ietf.org;
	Tue, 24 Aug 2004 03:39:46 +0900 (KST)
Received: from Alperyegin ([105.253.155.71])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I2W007PDX677V@mmp1.samsung.com> for
	pana@ietf.org; Tue, 24 Aug 2004 03:39:45 +0900 (KST)
Date: Mon, 23 Aug 2004 11:39:43 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20041020202936.GF3131@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <007701c48940$90051160$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 31b28e25e9d13a22020d8b7aedc9832c
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

> > I'm not sure if this is the right question. I think we should be
trying
> > to answer if PANA-ping is ever needed when the sender is not in OPEN
> > state.
> >
> > I see at least two cases:
> > a- using PANA-ping for debugging. In that case you want to be able
to
> > use it in any state (e.g., in the middle of a hung WAIT_* state).
> 
> I think we can use other tools for debugging as we normally do for
> other protocol implementations.

I'm thinking of this as similar to PPP echo-request/reply. 

> > b- to discover the state of the peer (e.g., after a crash and
reboot.
> > Before the crash, the sender might have been in a state other than
> > OPEN).
> 
> Can't a simple method "wait for the current authentication session to
> fail" be used here?  

The discovery can be much faster by using the ping if we didn't have to
wait for timeouts.

> I do not have a serious demand on doing liveness
> test for an incomplete session (but others may have...).

I think there are many ways this ability (to send PANA-ping at any time)
is useful. We might not be able to exhaust them right now. I just don't
want to limit its usage to certain states. Unless it complicates
anything I don't see why not have this flexibility.

Alper

> 
> Yoshihiro Ohba
> 
> 
> >
> > Alper
> >
> >
> >
> >
> >
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > > >
> > > > Alper
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > Sent: Sunday, September 19, 2004 5:12 PM
> > > > > To: Alper Yegin
> > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage
of
> > > > "reauth"
> > > > > messages
> > > > >
> > > > > In draft-ohba-pana-statemachine-00.txt, there is a state
WAIT_PRAA
> > > > > (which transits only from OPEN state) in both PaC and PAA
state
> > > > > machines to wait for PANA-Reauth-Answer after sending
> > > > > PANA-Reauth-Request.  Since we are replacing PANA-Requth-*
with
> > > > > PANA-Ping-*, the WAIT_PRAA state would be replaced with
WAIT_PPA.
> > I
> > > > > am afraid if we need additional transitions to the WAIT_PPA
state
> > from
> > > > > several states, it would complicate the state machines and I
am
> > > > > wondering what is the benefit of adding such complexity.
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > > On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper Yegin wrote:
> > > > > > Yoshi,
> > > > > >
> > > > > > I never thought we would need to deal with PANA-ping in the
> > state
> > > > > > machine.
> > > > > > I perceive it as a tool that can be used asynchronous to the
> > state
> > > > > > machine, and does not automatically impact the state
machine.
> > [Sure,
> > > > > > PANA implementation can use PANA ping to discover dead-peer,
> > just
> > > > like
> > > > > > it could use ICMP echos, or L2 indications]. If a state had
> > > > explicitly
> > > > > > called for using PANA-ping, then we must have incorporated
it in
> > the
> > > > > > state machine.
> > > > > >
> > > > > > Alper
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > > > Sent: Sunday, September 19, 2004 4:37 PM
> > > > > > > To: Alper Yegin
> > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear
usage
> > of
> > > > > > "reauth"
> > > > > > > messages
> > > > > > >
> > > > > > > On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper Yegin
wrote:
> > > > > > > > > Should PANA-Ping-Request be allowed in discovery and
> > initial
> > > > > > handshake
> > > > > > > > > phase?
> > > > > > > >
> > > > > > > >
> > > > > > > > > Should PANA-Ping-Request be allowed in authentication
> > phase?
> > > > > > > >
> > > > > > > > I thought about these. I decided to let the ping
behavior
> > handle
> > > > > > this
> > > > > > > > automatically. If there is an established pana session
on
> > the
> > > > peer,
> > > > > > it
> > > > > > > > will respond. Otherwise, ping request will be silently
> > > > discarded.
> > > > > > This
> > > > > > > > behavior can be followed in any state. [Also, PDI and
> > PAR/PAN
> > > > can be
> > > > > > > > sent even when there is an established PANA session.
Hence
> > ping
> > > > > > should
> > > > > > > > work in that case.]
> > > > > > >
> > > > > > > It is probablly easier to do that at the receiving side of
the
> > > > ping
> > > > > > > request, but what about transmitting side?  If we allow a
PAA
> > or a
> > > > PaC
> > > > > > > to send a PANA-Ping-Request and receiving a
PANA-Ping-Answer
> > > > between
> > > > > > > two consecutive PANA-Auth-Request/Answer exchanges in
> > > > authentication
> > > > > > > phase, it would complicate the state machines (probably
one
> > > > additional
> > > > > > > state is needed to support this case in the PaC and PAA
state
> > > > > > > machines).  I have a similar observation for PANA pinging
in
> > > > discovery
> > > > > > > and initial handshake phase.
> > > > > > >
> > > > > > > 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  Mon Aug 23 15:27: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 PAA04387
	for <pana-archive@lists.ietf.org>; Mon, 23 Aug 2004 15:27: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 1BzK4w-0004wX-0d; Mon, 23 Aug 2004 15:02:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzJk5-0007I6-JL
	for pana@megatron.ietf.org; Mon, 23 Aug 2004 14:40: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 OAA29946
	for <pana@ietf.org>; Mon, 23 Aug 2004 14:40:22 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzJkK-0002mD-Dj
	for pana@ietf.org; Mon, 23 Aug 2004 14:40:47 -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 <0I2W00A01X6D9B@mailout2.samsung.com> for pana@ietf.org; Tue,
	24 Aug 2004 03:39:49 +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 <0I2W0084IX6CNR@mailout2.samsung.com> for pana@ietf.org;
	Tue, 24 Aug 2004 03:39:48 +0900 (KST)
Received: from Alperyegin ([105.253.155.71])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I2W007PDX677V@mmp1.samsung.com> for
	pana@ietf.org; Tue, 24 Aug 2004 03:39:48 +0900 (KST)
Date: Mon, 23 Aug 2004 11:39:43 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 94 and 95 - proposed text
In-reply-to: <20040920151820.GD3131@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <007801c48940$914f1d90$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 4515df9441674711565101d9d5c4f63f
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

> The text looks very nice.  Maybe "PANA reauthentication messages" in
> section 9.8 is replaced with "PANA ping messages".

Thanks for catching this. I fixed it now.


9.  Security Considerations

   The PANA protocol defines a UDP-based EAP encapsulation that runs 
   between two IP-enabled nodes on the same IP link. Various security
   threats that are relevant to a protocol of this nature are outlined
   in [I-D.ietf-pana-threats-eval]. Security considerations stemming
   from the use of EAP and EAP methods are discussed in [RFC3748].
   This section provides a discussion on the security-related issues
   that are related to PANA framework and protocol design.

   An important element in assessing security of PANA design and
   deployment in a network is the presence of lower-layer (physical and
   link-layer) security. In the context of this document, lower-layers 
   are said to be secure if they can prevent eavesdropping and spoofing
of
   packets. Examples of such networks are physically-secured DSL
networks 
   and 3GPP2 networks with crytographically-secured cdma2000 link-layer.

   In these examples, the lower-layer security is enabled even before 
   running the first PANA-based authentication. In the absence of such a

   pre-established secure channel, one needs to be created in
conjunction 
   with PANA using a link-layer or network-layer cryptographic 
   mechanism (e.g., IPsec). 
   
  
9.1. General security measures 

   PANA provides multiple mechanisms to secure a PANA session.

   Since PaC and PAA are on the same IP link, a simple TTL check on
   the received PANA messages prevents off-link attacks.

   PANA messages carry both a transmission sequence number and 
   an acknowledgement of the received sequence number. These numbers
   are randomly initialized at the beginning of the session, and
   verified against expected numbers upon receipt. A message whose
   sequence numbers fall outside of the expected range are silently
   discarded. In addition to accomplishing orderly delivery of EAP
messages 
   and duplicate elimination, this scheme also helps prevent an
adversary 
   spoof messages to disturb ongoing PANA and EAP sessions unless it can

   also eavesdrop to synchronize on the sequence numbers. 

   The PANA framework defines EP which is ideally located on a
   network device that can filter traffic from the PaCs
   before the traffic enters the intranet. A set of filters can be used
to
   discard unauthorized packets, such as a PANA-Start-Request message
   that is received from the segment of the access network where only
   PaCs are supposed to be connected.

   The protocol also provides authentication and integrity protection to
   PANA messages when the used EAP method can generate cryptographic 
   session keys. PANA SA is generated based on the AAA-Key exported by
the 
   EAP method. This SA is used for generating per-packet MAC to protect
the 
   PANA header and payload (including the complete EAP message).  The 
   cryptographic protection prevents an adversary from acting as a 
   man-in-the-middle, injecting messages, replaying messages and
modifying 
   the content of the exchanged messages. Any packet that fails to pass
the
   MAC verification is silently discarded. The earliest this protection
can
   be enabled is when the very first PANA-Bind-Request that signals a
   successful authentication is generated. Starting with the 
   PANA-Bind-Request and PANA-Bind-Answer, any subsequent PANA message 
   until the session gets torn down can be cryptographically protected. 

   PANA SA enables authenticated and integrity protected exchange of
   the device ID information between the PaC and PAA. This ensures there
   were no man-in-the-middle during the PANA authentication.

   The lifetime of the PANA SA is bounded by the AAA-authorized
   session lifetime with an additional tolerance period.  Unless PANA
   state is updated by executing another EAP authentication, PANA SA is
   removed when the current session expires.  

   The ability to use cryptographic protection within PANA is determined
   by the used EAP method, which is generally dictated by the deployment
   environment. Unsecure lower-layers necessitate use of key-generating
   EAP methods. In networks where lower-layers are already secured, 
   cryprographic protection of PANA messages is not necessary. 

        
9.2. Discovery

   The initial discovery phase is vulnerable to spoofing attacks as
   these messages are not authenticated and integrity protected. In
order
   to prevent very basic denial-of service attacks an adversary should
not 
   be able to cause state creation by sending discovery messages to the 
   PAA. This protection is achieved by using a cookie-based scheme
(similar 
   to [RFC2522]) which allows the responder (PAA) to be stateless in the

   first round of message exchange. A return-routability test does not
   provide additional protection as PANA traffic is not routed but
   simply forwarded on-link. It is difficult to prevent this
   threat entirely.  

   In networks where lower-layers are not secured prior to running PANA,
   the capability discovery enabled through inclusion of
   Protection-Capability and Post-PANA-Address-Configuration AVPs in
   PANA-Start-Request message is susceptible to spoofing leading to 
   denial-of service attacks.  Therefore, usage of these AVPs during the

   discovery phase in such insecure networks is NOT RECOMMENDED.  The
same 
   AVPs are delivered via an integrity-protected PANA-Bind-Request upon 
   successful authentication.


9.3. EAP Methods

   Eavesdropping EAP packets might cause problems when the EAP
   method is weak and enables dictionary or replay attacks or even
   allows an adversary to learn the long-term password directly.
   Furthermore, if the optional EAP Identity payload is used then it
   allows the adversary to learn the identity of the PaC.  In such a
   case a privacy problem is prevalent.

   To prevent these threats, [I-D.ietf-pana-framework] suggests using
   proper EAP methods for particular environments.  Depending on the
   deployment environment an EAP authentication which supports user 
   identity confidentiality, protection against dictionary attacks and 
   session key establishment must be used. It is therefore
   the responsibility of the network operators and users to choose
   a proper EAP method.


9.4. Separate NAP-ISP authentication

   PANA design allows running two separate EAP methods for the same
   PaC: one with the NAP, and one with the ISP. The process of arriving
at 
   the resultant authorization, which is a combination of the individual
   authorizations obtained from respective service providers, is outside
   the scope of this protocol. In the absence of lower-layer security, 
   both authentications MUST be able to generate a AAA-Key, leading to 
   generation of PANA SA. The resultant PANA SA cryptographically binds
   the two AAA-Keys together, hence it prevents man-in-the-middle
attacks.


9.5. Cryptographic keys

   When the EAP method exports a AAA-Key, this key is used to produce a 
   PANA SA with PANA_MAC_KEY with a distinct key ID. PANA_MAC_KEY is
unique 
   to the PANA session, and takes PANA-based nonce values into
computation 
   to cryptographically separate itself from the AAA-Key.

   PANA_MAC_KEY is solely used for authentication and integrity
protection
   of the PANA messages within the designated session.

   Two AAA-keys may be generated as a result of separate NAP and ISP 
   authentication. In that case, the AAA-key used with the PANA SA is
the
   combination of both keys. 

   The PANA SA lifetime is bounded by the AAA-Key lifetime. Another 
   execution of EAP method yields in a new AAA-Key, and updates 
   the PANA SA, PANA_MAC_KEY and key ID.

   Upon PaC's movement to a another PAA (new PAA) and request to perform
   a context transfer based optimization, the current PAA computes a
   AAA-key-int based on the AAA-Key, ID of new PAA, and the session ID. 
   This AAA-key-int is delivered to the new PAA, and used in the
   computation of AAA-key-new, which further takes a pair of nonce
values 
   into account. After this point on, the AAA-key-new becomes the
AAA-key
   between the PaC and the new PAA.

   When link-layer or network-layer ciphering [I-D.ietf-pana-ipsec] is 
   enabled as a result of successful PANA authentication, a separate
master 
   key is generated based on the AAA-Key, session ID, key ID, and EP ID.

   The lifetime of this key is bounded by the lifetime of the PANA SA.
This 
   key may be used with a secure association protocol 
   [I-D.ietf-ipsec-ikev2] to produce further cipher-specific and
transient 
   keys. 
   

9.6. Per-packet ciphering

   Networks that are not secured at the lower-layers prior to running  
   PANA can rely on enabling per-packet data traffic ciphering upon
   successful PANA session establishment. The PANA framework allows 
   generation of a master key from AAA-key for using with a per-packet 
   protection mechanism, such as link-layer or IPsec-based
   ciphering [I-D.ietf-pana-ipsec]. In case the master key is not
readily 
   useful to the ciphering mechanism, an additional secure association 
   protocol [I-D.ietf-ipsec-ikev2] may be needed to produce the required

   keying material. These mechanisms ultimately establish a
cryptographic 
   binding between the data traffic generated by and for a client and
the 
   authenticated identity of the client. Data traffic must be minimally 
   data origin authenticated, replay and integrity protected, and 
   optionally encrypted.

   
9.7. PAA-to-EP communication

   The PANA framework allows separation of PAA from EP(s). SNMPv3 
   [I-D.ietf-pana-snmp] is used between the the PAA and EP for
   provisioning authorized PaC information on the EP. This exchange MUST
be
   always physically or cryptographically protected for authentication,
   integrity and replay protection. It MUST also be privacy-protected
   when per-PaC master key for per-packet ciphering is transmitted to
the
   EP.

   The per-packet ciphering master key MUST be unique to the PaC and EP 
   pair. The session ID and EP's device ID are taken into computation
for 
   achieving this effect [I-D.ietf-pana-ipsec]. Compromise of an EP does

   not automatically lead to compromise of another EP or the PAA.

 
9.8. Livenes test         

   A PANA session is associated with a session lifetime.  The session is
   terminated unless it is refreshed by a new round of EAP
   authentication before it expires.  Therefore, at the latest a
   disconnected client can be detected when its lifetime expires.  A
   disconnect may also be detected earlier by using PANA
   ping messages.  A request message can be generated by
   either PaC or PAA at any time and the peer must respond with an
   answer message.  A successful round-trip of this exchange is a simple
   verification that the peer is alive.  This test can be engaged when
   there is a possibility that the peer might have disconnected (e.g.,
   after discontinuation of data traffic).  Periodic use of this
   exchange as a keep-alive requires additional care as it might result
   in congestion and hence false alarms.  This exchange is
   cryptographically protected when PANA SA is available in order to
   prevent threats associated with the abuse of this functionality.


9.9. Mobility optimization

   The mobility optimization described in Section 4.12 involves the
   previous PAA providing a AAA-Key to the current PAA of the PaC.
   There are security risks stemming from potential compromise of PAAs.
   Compromise of the current PAA does not yield compromise of the
   previous PAA, as AAA-Key cannot be computed from a compromised
   AAA-Key-new.  But a compromised previous PAA along with the
   intercepted nonce values on the current link leads to the 
   compromise of AAA-Key-new. Operators should be aware of the potential

   risk of using this optimization.  An operator can reduce the risk 
   exposure by forcing the PaC to perform an EAP-based authentication 
   immediately after the PaC gains access to new link via the optimized
PANA 
   execution.


9.10. Updating PaC's IP address

   Even though the IP-Address AVP in a PANA-update-Request can be
   cryptographically protected by the MAC AVP, there is not way to
   prove the ownership of the IP address presented by the PaC. Hence
   an authorized PaC can launch a redirect attack by spoofing a victim's
   IP address. 


9.11. Early termination of a session

   The PANA protocol supports the ability for both the PaC and the PAA
   to transmit a tear-down message before the session lifetime expires.

   This message causes state removal, a stop of the accounting procedure
   and removes the installed per-PaC state on the EP(s). This message is

   cryptographically protected when PANA SA is present.
   



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


From pana-bounces@ietf.org  Mon Aug 23 18:30: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 SAA22850
	for <pana-archive@lists.ietf.org>; Mon, 23 Aug 2004 18:30: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 1BzMcX-0006rL-PE; Mon, 23 Aug 2004 17:44:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzLFJ-0003US-BP
	for pana@megatron.ietf.org; Mon, 23 Aug 2004 16:16:49 -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 QAA07685
	for <pana@ietf.org>; Mon, 23 Aug 2004 16:16:41 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzLFa-0004tV-PI
	for pana@ietf.org; Mon, 23 Aug 2004 16:17:07 -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 <0I2X001011MX7L@mailout1.samsung.com> for pana@ietf.org; Tue,
	24 Aug 2004 05:16: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 <0I2X008MM1MWUC@mailout1.samsung.com> for pana@ietf.org;
	Tue, 24 Aug 2004 05:16:09 +0900 (KST)
Received: from Alperyegin ([105.253.155.71])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I2X00IQ41MT91@mmp2.samsung.com> for
	pana@ietf.org; Tue, 24 Aug 2004 05:16:08 +0900 (KST)
Date: Mon, 23 Aug 2004 13:16:05 -0700
From: Alper Yegin <alper.yegin@samsung.com>
In-reply-to: <20040919231911.GA22998@steelhead>
To: pana@ietf.org
Message-id: <008401c4894e$06244070$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 8aa7cbc518894eb04182283f0682f662
Content-Transfer-Encoding: 7BIT
Subject: [Pana] Proposed text for issue 104
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


Comments welcome.


[1] Section 2:

Change:

 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.

To:

 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. 


Change:

   Device Identifier (DI):

      The identifier used by the network as a handle to control and
      police the network access of a client.  Depending on the access
      technology, this identifier might contain any of IP address,
      link-layer address, switch port number, etc.  of a connected
      device.

To:

   Device Identifier (DI):

      The identifier used by the network as a handle to control and
      police the network access of a client.  Depending on the access
      technology, this identifier may contain an address that is
      carried in protocol headers (e.g., IP or link-layer address),
      or a locally significant identifier that is made available
      by the local protocol stack (e.g., circuit id, PPP interface id) 
      of a connected device.

[2] Section 3.1:

Change:

         <-----     PANA-Bind-Request[Session-Id, EAP{Success},
                         Device-Id, Lifetime, Protection-Cap., Key-Id,
MAC]

To:

         <-----     PANA-Bind-Request[Session-Id, EAP{Success},
                         Device-Id, IP-Address, Lifetime,
Protection-Cap.,
                         Key-Id, MAC]


[3] Section 4.1.1:

Change:

   o  Device-Id AVP: contains a device identifier of the sender of the
      message.  A device identifier is represented as a pair of device
      identifier type and device identifier value.  Either a layer-2
      address or an IP address is used for the device identifier value.

To:

   o  Device-Id AVP: contains a device identifier of the PaC or an EP.
      A device identifier is represented as a pair of device
      identifier type and device identifier value.  Either a layer-2
      address or an IP address is used for the device identifier value
      when this AVP is present.

Remove:

   o  EP-Device-Id AVP: contains the device identifier of an EP.


[4] Section 4.1.5:

Change:

      *  Device-Id of PaC

      *  Device-Id of PAA

      *  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)

      *  List of device identifiers of EPs


To:

      *  Device-Id of PaC

      *  IP address of PaC (may be the same as the Device-Id of PaC)

      *  IP address of PAA

      *  List of device identifiers of EPs

[5] Section 4.1.7:

Change:

   o  When a device identifier of the communication peer is bound to the
      PANA session, it matches the device identifier carried in MAC and/
      or IP header(s), or other auxiliary indetifier provided by the
      lower-layers (e.g., circuit ID).


To:

   o  When a device identifier of the PaC is bound to the
      PANA session, it matches the device identifier carried in MAC or
      or IP header, or other locally-significant identifier provided by 
      the lower-layers (e.g., circuit ID) unless the message is 
      a PANA-Update-Request with IP-Address AVP.


Change:

   o  When a Device-Id AVP is included, the AVP is valid if the device
      identifier type contained in the AVP is supported (this check is
      for both PaC and PAA) and is the requested one (this check is for
      PAA only) and the device identifier value contained in the AVP
      matches the value extracted from the lower-layer encapsulation
      header corresponding to the device identifier type contained in
      the AVP.  Note that a Device-Id AVP carries the PaC's device
      identifier in messages from PaC to PAA and PAA's device identifier
      in messages from PAA to PaC.

To:


   o  When a Device-Id AVP is included, the AVP is valid if the device
      identifier type contained in the AVP is supported (this check is
      for both PaC and PAA) and is the requested one (this check is for
      PAA only) and the device identifier value contained in the AVP
      matches the value extracted from the lower-layer encapsulation
      header corresponding to the device identifier type contained in
      the AVP (this check is for PaC only).  Note that a Device-Id AVP
      carries the PaC's device identifier in messages from PaC to PAA  
      and EP(s)' device identifier in messages from PAA to PaC.

Add:

   o  When the IP-Address AVP is received in a message from the PAA,
      the AVP is valid if the IP address matches the source address
      in the IP header.


[6] Section 4.3:

Change:

        <-----     PANA-Bind-Request(x+3,y+2)
                       [Session-Id, EAP{Success}, Device-Id, Lifetime,
                        Protection-Cap., PPAC, MAC]

To:

        <-----     PANA-Bind-Request(x+3,y+2)
                       [Session-Id, EAP{Success}, Device-Id, IP-Address,
                        Lifetime, Protection-Cap., PPAC, MAC]


Change:

   The PANA-Bind-Request and the PANA-Bind-Answer message exchange is
   also used for binding device identifiers of the PaC and the PAA to
   the PANA SA when the identifiers are either IP or MAC addresses.  To
   achieve this, the PANA-Bind-Request and the PANA-Bind-Answer SHOULD
   contain a device identifier of the PAA and the PaC, respectively, in
   a Device-Id AVP.  Device identifier exchange that is protected by a
   MAC AVP prevents man-in-the-middle attacks.  The PaC MUST use the
   same type of device identifier as contained in the PANA-Bind-Request
   message.  

To:

   The PANA-Bind-Request and the PANA-Bind-Answer message exchange is
   also used for binding device identifiers of the PaC and EP(s), and 
   the IP address of the PAA to the PANA SA. To achieve this, 
   the PANA-Bind-Request SHOULD contain the device indentifier(s) of
   the EP(s) in Device-Id AVP(s) when they are either MAC or IP 
   address(es), and the IP address of the PAA in an IP-Address AVP. 
   PANA-Bind-Answer SHOULD contain PaC's device identifier in a 
   Device-Id AVP when it is already presented with that of EP(s). 
   The PaC MUST use the same type of device identifier as contained in 
   the PANA-Bind-Request message. This exchange when protected by a MAC 
   AVP prevents man-in-the-middle attacks. 


[7] Section 4.4:


Change:

         <-----     PANA-Bind-Request(p+2,q+2)
                       [Session-Id, EAP{Success}, Device-Id, Key-Id,
                        Lifetime, Protection-Cap., PPAC, MAC]

To:

         <-----     PANA-Bind-Request(p+2,q+2)
                       [Session-Id, EAP{Success}, Device-Id, IP-Address,
                        Key-Id, Lifetime, Protection-Cap., PPAC, MAC] 

[8] Section 4.6:

Change:

         <-----     PANA-Bind-Request(x+5,y+6)          // S-flag set
                      [EAP{Success}, Device-Id, Key-Id,
                       Lifetime, Protection-Cap., PPAC, MAC]

To:

         <-----     PANA-Bind-Request(x+5,y+6)          // S-flag set
                      [EAP{Success}, Device-Id, IP-Address, Key-Id,
                       Lifetime, Protection-Cap., PPAC, MAC]

[8] New text for Section 4.8:

4.8  Device ID Choice

   The device identifier used in the context of PANA can be an IP
   address, a MAC address, or an identifier that is not carried in data
   packets but has local significance in identifying a connected host
   (e.g., circuit id, PPP interface id).  The last type of identifiers 
   are commonly used in point-to-point links where MAC addresses are
   not available and lower-layers are already physically or
   cryptographically secured.

   It is assumed that the PAA knows the link type and the security
   mechanisms being provided or required on the access network (e.g.,
   based on physical security, link-layer ciphers enabled before or
   after PANA, or IPsec).  Based on that information, the PAA can decide
   what type of EP device id will be used when running PANA with the
   client.  When IPsec-based security [I-D.ietf-pana-ipsec] is the
   choice of access control, the PAA SHOULD provide IP address(es) 
   as EP(s)' device ID, and expect the PaC to provide its IP address 
   in return. In case IPsec is not used, MAC addresses are used as 
   device IDs when available.  If non-IPsec access control is enabled, 
   and a MAC address is not available, device ID exchange does not 
   occur within PANA. Instead, peers rely on lower-layers to provide
   locally-significant identifiers along with received PANA packets.

[9] Remove Section 4.13:

I think now the information in section 4.3 is already covered elsewhere,
so 
we can remove the section.




[10] Section 6.4.7:

Change:

6.4.7  PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

         PANA-Bind-Request ::= < PANA-Header: 4, REQ [SEP] [NAP] >
                       < Session-Id >
                       { Result-Code }
                       { PPAC }
                       [ EAP-Payload ]
                       [ Device-Id ]
                       [ Session-Lifetime ]
                       [ Protection-Capability ]
                       [ Key-Id ]
                    *  [ EP-Device-Id ]
                    *  [ AVP ]
                   0*1 < MAC >


To:

6.4.7  PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

         PANA-Bind-Request ::= < PANA-Header: 4, REQ [SEP] [NAP] >
                       < Session-Id >
                       { Result-Code }
                       { PPAC }
                       { IP-Address }
                       [ EAP-Payload ]
                       [ Device-Id ]
                       [ Session-Lifetime ]
                       [ Protection-Capability ]
                       [ Key-Id ]
                    *  [ Device-Id ]
                    *  [ AVP ]
                   0*1 < MAC >

[11] Remove "<Device-Id>" from PFER and PFEA in sections 6.4.14 and
6.4.15 

respectively.

[12] Remove Section "6.5.15  EP-Device-Id AVP".

[13] New text for Section 6.5.19:

6.5.19  IP-Address AVP

   The IP-Address (AVP Code: 1042) contains an IP address of a PaC or
PAA.
   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.

[14] Occurence tables in Section 6.6:


                          +-----------------------------------------+
                          |        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               |  1  |  1  |  0  |  0  |  0  |  0  |  0  |
      Device-Id           |  0  |  0  |  0  |  0  |  0+ | 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  |
      Key-Id              |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
      IP-Address          |  0  |  0  |  0  |  0  |  1  |  0  |  0  |
      --------------------+-----+-----+-----+-----+-----+-----+-----+

                 Figure 12: 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
|
      Key-Id              |  0   |  0   |  0  |  0  |  0  | 0-1  | 0-1
|
      IP-Address          |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
 
--------------------+------+------+-----+-----+-----+------+------+

                 Figure 13: AVP Occurrence Table (2/3)

                          +-----------+
                          |  Message  |
                          |   Type    |
                          +-----+-----+
      Attribute Name      | PUR | 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  |  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  |
      Key-Id              |  0  |  0  |
      IP-Address          |  1  |  0  |
      --------------------+-----+-----+

                 Figure 14: AVP Occurrence Table (3/3)




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


From pana-bounces@ietf.org  Mon Aug 23 19:46: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 TAA27975
	for <pana-archive@lists.ietf.org>; Mon, 23 Aug 2004 19:46: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 1BzO6z-0004Co-K5; Mon, 23 Aug 2004 19:20:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzN0A-000212-PQ
	for pana@megatron.ietf.org; Mon, 23 Aug 2004 18:09:19 -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 SAA20757
	for <pana@ietf.org>; Mon, 23 Aug 2004 18:09:10 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzN0S-0000Vi-ML
	for pana@ietf.org; Mon, 23 Aug 2004 18:09:38 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7NM99bv024165;
	Tue, 24 Aug 2004 07:09:09 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7NM99EK013452;
	Tue, 24 Aug 2004 07:09:09 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	HAA13451 ; Tue, 24 Aug 2004 07:09:08 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA08294; Tue, 24 Aug 2004 07:09:08 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7NM98Da029861;
	Tue, 24 Aug 2004 07:09:08 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7NM97wE027215;
	Tue, 24 Aug 2004 07:09:07 +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 <0I2X00G8A6V4Q2@tsbpo1.po.toshiba.co.jp>; Tue,
	24 Aug 2004 07:09:07 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1CLU3g-0006S8-00; Sat, 23 Oct 2004 15:08:20 -0700
Date: Sat, 23 Oct 2004 18:08:20 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <007701c48940$90051160$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20041023220820.GO3131@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+20040803i
References: <20041020202936.GF3131@steelhead>
	<007701c48940$90051160$6401a8c0@sisa.samsung.com>
X-Spam-Score: 2.4 (++)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1
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, Aug 23, 2004 at 11:39:43AM -0700, Alper Yegin wrote:
> > > I'm not sure if this is the right question. I think we should be
> trying
> > > to answer if PANA-ping is ever needed when the sender is not in OPEN
> > > state.
> > >
> > > I see at least two cases:
> > > a- using PANA-ping for debugging. In that case you want to be able
> to
> > > use it in any state (e.g., in the middle of a hung WAIT_* state).
> > 
> > I think we can use other tools for debugging as we normally do for
> > other protocol implementations.
> 
> I'm thinking of this as similar to PPP echo-request/reply. 

PPP echo is allowed only for its LCP Opened state, not for arbitrary
state.

> 
> > > b- to discover the state of the peer (e.g., after a crash and
> reboot.
> > > Before the crash, the sender might have been in a state other than
> > > OPEN).
> > 
> > Can't a simple method "wait for the current authentication session to
> > fail" be used here?  
> 
> The discovery can be much faster by using the ping if we didn't have to
> wait for timeouts.

If rebooting events are rare, I don't much care about timeouts for
rare events.

> 
> > I do not have a serious demand on doing liveness
> > test for an incomplete session (but others may have...).
> 
> I think there are many ways this ability (to send PANA-ping at any time)
> is useful. We might not be able to exhaust them right now. I just don't
> want to limit its usage to certain states. Unless it complicates
> anything I don't see why not have this flexibility.

I have a bit concern on the complexity needed to support this
flexibility from the state machine point of view, and my previous
question on lock-step operation relates to that.  I don't think just
having an independent state machine for pinging works for a protocol
that is designed under lock-step operations.

Yoshihiro Ohba


> 
> Alper
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > >
> > > Alper
> > >
> > >
> > >
> > >
> > >
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > >
> > > > > Alper
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > > Sent: Sunday, September 19, 2004 5:12 PM
> > > > > > To: Alper Yegin
> > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage
> of
> > > > > "reauth"
> > > > > > messages
> > > > > >
> > > > > > In draft-ohba-pana-statemachine-00.txt, there is a state
> WAIT_PRAA
> > > > > > (which transits only from OPEN state) in both PaC and PAA
> state
> > > > > > machines to wait for PANA-Reauth-Answer after sending
> > > > > > PANA-Reauth-Request.  Since we are replacing PANA-Requth-*
> with
> > > > > > PANA-Ping-*, the WAIT_PRAA state would be replaced with
> WAIT_PPA.
> > > I
> > > > > > am afraid if we need additional transitions to the WAIT_PPA
> state
> > > from
> > > > > > several states, it would complicate the state machines and I
> am
> > > > > > wondering what is the benefit of adding such complexity.
> > > > > >
> > > > > > Yoshihiro Ohba
> > > > > >
> > > > > > On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper Yegin wrote:
> > > > > > > Yoshi,
> > > > > > >
> > > > > > > I never thought we would need to deal with PANA-ping in the
> > > state
> > > > > > > machine.
> > > > > > > I perceive it as a tool that can be used asynchronous to the
> > > state
> > > > > > > machine, and does not automatically impact the state
> machine.
> > > [Sure,
> > > > > > > PANA implementation can use PANA ping to discover dead-peer,
> > > just
> > > > > like
> > > > > > > it could use ICMP echos, or L2 indications]. If a state had
> > > > > explicitly
> > > > > > > called for using PANA-ping, then we must have incorporated
> it in
> > > the
> > > > > > > state machine.
> > > > > > >
> > > > > > > Alper
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > > > > Sent: Sunday, September 19, 2004 4:37 PM
> > > > > > > > To: Alper Yegin
> > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear
> usage
> > > of
> > > > > > > "reauth"
> > > > > > > > messages
> > > > > > > >
> > > > > > > > On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper Yegin
> wrote:
> > > > > > > > > > Should PANA-Ping-Request be allowed in discovery and
> > > initial
> > > > > > > handshake
> > > > > > > > > > phase?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > Should PANA-Ping-Request be allowed in authentication
> > > phase?
> > > > > > > > >
> > > > > > > > > I thought about these. I decided to let the ping
> behavior
> > > handle
> > > > > > > this
> > > > > > > > > automatically. If there is an established pana session
> on
> > > the
> > > > > peer,
> > > > > > > it
> > > > > > > > > will respond. Otherwise, ping request will be silently
> > > > > discarded.
> > > > > > > This
> > > > > > > > > behavior can be followed in any state. [Also, PDI and
> > > PAR/PAN
> > > > > can be
> > > > > > > > > sent even when there is an established PANA session.
> Hence
> > > ping
> > > > > > > should
> > > > > > > > > work in that case.]
> > > > > > > >
> > > > > > > > It is probablly easier to do that at the receiving side of
> the
> > > > > ping
> > > > > > > > request, but what about transmitting side?  If we allow a
> PAA
> > > or a
> > > > > PaC
> > > > > > > > to send a PANA-Ping-Request and receiving a
> PANA-Ping-Answer
> > > > > between
> > > > > > > > two consecutive PANA-Auth-Request/Answer exchanges in
> > > > > authentication
> > > > > > > > phase, it would complicate the state machines (probably
> one
> > > > > additional
> > > > > > > > state is needed to support this case in the PaC and PAA
> state
> > > > > > > > machines).  I have a similar observation for PANA pinging
> in
> > > > > discovery
> > > > > > > > and initial handshake phase.
> > > > > > > >
> > > > > > > > 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

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


From pana-bounces@ietf.org  Mon Aug 23 19:49: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 TAA28132
	for <pana-archive@lists.ietf.org>; Mon, 23 Aug 2004 19:49: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 1BzODr-0005o6-0e; Mon, 23 Aug 2004 19:27:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzNNA-0001no-67
	for pana@megatron.ietf.org; Mon, 23 Aug 2004 18:33:14 -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 SAA23083
	for <pana@ietf.org>; Mon, 23 Aug 2004 18:32:56 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzNNT-0000z7-Cp
	for pana@ietf.org; Mon, 23 Aug 2004 18:33:24 -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 <0I2X004017XR8N@mailout2.samsung.com> for pana@ietf.org; Tue,
	24 Aug 2004 07:32:15 +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 <0I2X008MP7XQNR@mailout2.samsung.com> for pana@ietf.org;
	Tue, 24 Aug 2004 07:32:14 +0900 (KST)
Received: from Alperyegin ([105.253.155.71])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I2X00DXS7XNQ9@mmp2.samsung.com> for
	pana@ietf.org; Tue, 24 Aug 2004 07:32:14 +0900 (KST)
Date: Mon, 23 Aug 2004 15:32:10 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20041023220820.GO3131@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <012b01c48961$09447190$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 65bc4909d78e8b10349def623cf7a1d1
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

> > > I think we can use other tools for debugging as we normally do for
> > > other protocol implementations.
> >
> > I'm thinking of this as similar to PPP echo-request/reply.
> 
> PPP echo is allowed only for its LCP Opened state, not for arbitrary
> state.

I noticed that. But unless there is a technical reason, I don't think we
should inherit the same limitations.

> > > > b- to discover the state of the peer (e.g., after a crash and
> > reboot.
> > > > Before the crash, the sender might have been in a state other
than
> > > > OPEN).
> > >
> > > Can't a simple method "wait for the current authentication session
to
> > > fail" be used here?
> >
> > The discovery can be much faster by using the ping if we didn't have
to
> > wait for timeouts.
> 
> If rebooting events are rare, I don't much care about timeouts for
> rare events.
> 
> >
> > > I do not have a serious demand on doing liveness
> > > test for an incomplete session (but others may have...).
> >
> > I think there are many ways this ability (to send PANA-ping at any
time)
> > is useful. We might not be able to exhaust them right now. I just
don't
> > want to limit its usage to certain states. Unless it complicates
> > anything I don't see why not have this flexibility.
> 
> I have a bit concern on the complexity needed to support this
> flexibility from the state machine point of view, and my previous
> question on lock-step operation relates to that.  I don't think just
> having an independent state machine for pinging works for a protocol
> that is designed under lock-step operations.

I still don't understand the complexity on the state machine. My
recommendation is not to include PANA-ping in the (main) state machine.

And being lock-step was never a design goal or requirement. If this
addition is breaking the lock-step nature, I don't see a problem, unless
there was a benefit of being lock-stepped and now we are losing it. Are
we?

Alper



> 
> Yoshihiro Ohba
> 
> 
> >
> > Alper
> >
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > > >
> > > > Alper
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > >
> > > > > >
> > > > > > Alper
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > > > Sent: Sunday, September 19, 2004 5:12 PM
> > > > > > > To: Alper Yegin
> > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear
usage
> > of
> > > > > > "reauth"
> > > > > > > messages
> > > > > > >
> > > > > > > In draft-ohba-pana-statemachine-00.txt, there is a state
> > WAIT_PRAA
> > > > > > > (which transits only from OPEN state) in both PaC and PAA
> > state
> > > > > > > machines to wait for PANA-Reauth-Answer after sending
> > > > > > > PANA-Reauth-Request.  Since we are replacing PANA-Requth-*
> > with
> > > > > > > PANA-Ping-*, the WAIT_PRAA state would be replaced with
> > WAIT_PPA.
> > > > I
> > > > > > > am afraid if we need additional transitions to the
WAIT_PPA
> > state
> > > > from
> > > > > > > several states, it would complicate the state machines and
I
> > am
> > > > > > > wondering what is the benefit of adding such complexity.
> > > > > > >
> > > > > > > Yoshihiro Ohba
> > > > > > >
> > > > > > > On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper Yegin
wrote:
> > > > > > > > Yoshi,
> > > > > > > >
> > > > > > > > I never thought we would need to deal with PANA-ping in
the
> > > > state
> > > > > > > > machine.
> > > > > > > > I perceive it as a tool that can be used asynchronous to
the
> > > > state
> > > > > > > > machine, and does not automatically impact the state
> > machine.
> > > > [Sure,
> > > > > > > > PANA implementation can use PANA ping to discover
dead-peer,
> > > > just
> > > > > > like
> > > > > > > > it could use ICMP echos, or L2 indications]. If a state
had
> > > > > > explicitly
> > > > > > > > called for using PANA-ping, then we must have
incorporated
> > it in
> > > > the
> > > > > > > > state machine.
> > > > > > > >
> > > > > > > > Alper
> > > > > > > >
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > > > > > Sent: Sunday, September 19, 2004 4:37 PM
> > > > > > > > > To: Alper Yegin
> > > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and
unclear
> > usage
> > > > of
> > > > > > > > "reauth"
> > > > > > > > > messages
> > > > > > > > >
> > > > > > > > > On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper Yegin
> > wrote:
> > > > > > > > > > > Should PANA-Ping-Request be allowed in discovery
and
> > > > initial
> > > > > > > > handshake
> > > > > > > > > > > phase?
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > Should PANA-Ping-Request be allowed in
authentication
> > > > phase?
> > > > > > > > > >
> > > > > > > > > > I thought about these. I decided to let the ping
> > behavior
> > > > handle
> > > > > > > > this
> > > > > > > > > > automatically. If there is an established pana
session
> > on
> > > > the
> > > > > > peer,
> > > > > > > > it
> > > > > > > > > > will respond. Otherwise, ping request will be
silently
> > > > > > discarded.
> > > > > > > > This
> > > > > > > > > > behavior can be followed in any state. [Also, PDI
and
> > > > PAR/PAN
> > > > > > can be
> > > > > > > > > > sent even when there is an established PANA session.
> > Hence
> > > > ping
> > > > > > > > should
> > > > > > > > > > work in that case.]
> > > > > > > > >
> > > > > > > > > It is probablly easier to do that at the receiving
side of
> > the
> > > > > > ping
> > > > > > > > > request, but what about transmitting side?  If we
allow a
> > PAA
> > > > or a
> > > > > > PaC
> > > > > > > > > to send a PANA-Ping-Request and receiving a
> > PANA-Ping-Answer
> > > > > > between
> > > > > > > > > two consecutive PANA-Auth-Request/Answer exchanges in
> > > > > > authentication
> > > > > > > > > phase, it would complicate the state machines
(probably
> > one
> > > > > > additional
> > > > > > > > > state is needed to support this case in the PaC and
PAA
> > state
> > > > > > > > > machines).  I have a similar observation for PANA
pinging
> > in
> > > > > > discovery
> > > > > > > > > and initial handshake phase.
> > > > > > > > >
> > > > > > > > > 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


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


From pana-bounces@ietf.org  Mon Aug 23 20:50: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 UAA03558
	for <pana-archive@lists.ietf.org>; Mon, 23 Aug 2004 20:50: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 1BzP1q-00028u-Vp; Mon, 23 Aug 2004 20:19:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzOYe-00034z-Qi
	for pana@megatron.ietf.org; Mon, 23 Aug 2004 19:49:00 -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 TAA28104
	for <pana@ietf.org>; Mon, 23 Aug 2004 19:48:54 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzOYz-0002WP-2J
	for pana@ietf.org; Mon, 23 Aug 2004 19:49:21 -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 <0I2X00H01BGNPP@mailout2.samsung.com> for pana@ietf.org; Tue,
	24 Aug 2004 08:48:23 +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 <0I2X00D00BGMJ1@mailout2.samsung.com> for pana@ietf.org;
	Tue, 24 Aug 2004 08:48:23 +0900 (KST)
Received: from Alperyegin ([105.253.155.71])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I2X00DLFBGKQ9@mmp2.samsung.com> for
	pana@ietf.org; Tue, 24 Aug 2004 08:48:22 +0900 (KST)
Date: Mon, 23 Aug 2004 16:48:18 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] framework open issue
In-reply-to: <20040920004154.GF22998@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <013101c4896b$abf0d690$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 02ec665d00de228c50c93ed6b5e4fc1a
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


The first case shouldn't be marked as an issue on the I-D as the
associated mechanisms are only discussed in the Appendix as possible
other ways (but not officially supported otherwise).

Second issue can be handled either by use of link-layer event
notifications on the PaC, or the PAA initiating the PANA discovery
unsolicitedly.  

I got to the same point in a different way, but I agree with Yoshi that
we should remove this section.

Alper


> 
> Section 11 of draft-ietf-pana-framework-01.txt says:
> 
> "
> 11.  Open Issue
> 
> 
>    Certain combination of network environments and timing cases may
>    require further considerations.
> 
> 
>    If PaC changes access point right after a successful PANA
>    authorization but before POPA configuration, it might be confused
>    whether the new IP address configured via the new access point is
the
>    POPA of the ongoing session or a PRPA of a new session.  When the
>    PRPA and POPA types or configuration mechanisms are different this
is
>    not a problem.  One possible combination where such clues are not
>    available is when PaC moves from a Case A of Section 10.2.1.1
>    (IPsec-TIA obtained by using DHCPv4) network to a Case D of
Appendix
>    A.1 (IPsec-TIA obtained by using RFC3118) network.
> 
> 
>    In another example, when PaC switches from one wired Ethernet hub
to
>    another (without the use of bootstrapping IPsec) before configuring
>    the POPA.  In this case, PaC may not able to know whether an
obtained
>    address is the POPA in the same subnet or a PRPA in a new subnet.
> "
> 
> I think the above issue is related to DNA and not necessarily a PANA
> framework issue (i.e., DNA can deal with this issue.)
> 
> Suggested change: Remove this section.
> 
> 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 Aug 24 07:43: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 HAA27194
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 07:43: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 1BzZHJ-0003U1-BU; Tue, 24 Aug 2004 07:15:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzZ5g-0000Vf-Ap
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 07:03:48 -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 HAA24980
	for <pana@ietf.org>; Tue, 24 Aug 2004 07:03:45 -0400 (EDT)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzZ6A-0005sl-FH
	for pana@ietf.org; Tue, 24 Aug 2004 07:04:20 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id i7OB3i35028010
	for <pana@ietf.org>; Tue, 24 Aug 2004 04:03:45 -0700 (PDT)
Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,
	v2.2) with ESMTP id i7OB3i86002289
	for <pana@ietf.org>; Tue, 24 Aug 2004 07:03:44 -0400 (EDT)
Received: from phorcys.East.Sun.COM (localhost [127.0.0.1])
	by phorcys.East.Sun.COM (8.13.0+Sun/8.13.0) with ESMTP id
	i7OB3i4N024001; Tue, 24 Aug 2004 07:03:44 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.East.Sun.COM (8.13.0+Sun/8.13.0/Submit) id i7OB3iRH023998;
	Tue, 24 Aug 2004 07:03:44 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16683.8336.235742.618204@gargle.gargle.HOWL>
Date: Tue, 24 Aug 2004 07:03:44 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-Reply-To: Alper Yegin's message of 23 August 2004 15:32:10
References: <20041023220820.GO3131@steelhead>
	<012b01c48961$09447190$6401a8c0@sisa.samsung.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit

Alper Yegin writes:
> > PPP echo is allowed only for its LCP Opened state, not for arbitrary
> > state.
> 
> I noticed that. But unless there is a technical reason, I don't think we
> should inherit the same limitations.

Until LCP is Opened, you don't have a negotiated Magic-Number option,
so there's some ambiguity about what to put in each message and how to
verify the response.  Plus, while you're actively negotiating LCP,
there doesn't seem to be a reason to do an LCP Echo-Request -- you
know from LCP alone whether the peer is responding or not.

I think there may also have been a concern about using too many
different optional code numbers too early in the game.  Early
incarnations of PPP were a bit draconian about encountering bad codes
or LCP Code-Reject: they'd shut down the link.  Thus, unless it was
really absolutely necessary for operation of the link, it was left
until after LCP was done.

None of the above probably applies here.

-- 
James Carlson, IP Systems Group                <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.234W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.497N   Fax +1 781 442 1677

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


From pana-bounces@ietf.org  Tue Aug 24 10:59: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 KAA12419
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 10:59: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 1BzcMU-0006In-PI; Tue, 24 Aug 2004 10:33:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bzbz8-0007Yo-Ag
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 10:09:24 -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 KAA07610
	for <pana@ietf.org>; Tue, 24 Aug 2004 10:09:07 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzbzZ-00016z-J7
	for pana@ietf.org; Tue, 24 Aug 2004 10:09:42 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7OE95bv026815;
	Tue, 24 Aug 2004 23:09:05 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7OE95nP011077;
	Tue, 24 Aug 2004 23:09:05 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	ZAA11074 ; Tue, 24 Aug 2004 23:09:05 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id XAA19388; Tue, 24 Aug 2004 23:09:05 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7OE94Wh028593;
	Tue, 24 Aug 2004 23:09:04 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7OE94wE022891;
	Tue, 24 Aug 2004 23:09: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 <0I2Y00JGLFB0OS@tsbpo1.po.toshiba.co.jp>; Tue,
	24 Aug 2004 23:09:03 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1CLj3H-00089O-00; Sun, 24 Oct 2004 07:08:55 -0700
Date: Sun, 24 Oct 2004 10:08:55 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <012b01c48961$09447190$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20041024140855.GS3131@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+20040803i
References: <20041023220820.GO3131@steelhead>
	<012b01c48961$09447190$6401a8c0@sisa.samsung.com>
X-Spam-Score: 2.4 (++)
X-Scan-Signature: b360bd6cb019c35178e5cf9eeb747a5c
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,

Please see my analysis below.

By not including PANA-ping in the main state machine, I presume that
PANA-ping behavior is described in a separate state machine such as a
pana-ping state machine.  There are two design choices on how to
define the pana-ping state machine depending on whether PANA is
designed as a lock-step protocol or not.

1.  Lock-step PANA-ping

Since it is lock-step, it is prohibited to send a new request if there
is an outstanding request.  The pana-ping state machine and the main
state machine need to coordinate to guarantee this nature, probably by
defining a variable that is shared between the pana-ping state machine
and the main state machine to indicate whether there is an outstanding
request.  Also, exclusive write access to the variable from the two
state machines would be needed.  But how can such an exclusive write
access in the two state simply be described in the two state machines?
Or is there other way to describe the coordination in a simple manner?

2. Non-lock-step PANA-ping

In this case, it is allowed to send a new request regardless of
whether there is an outstanding request.  This means that there can be
multiple outstanding requests.  Since the answers for the outstanding
requests can arrive out of order, the requester needs to buffer
out-of-order answers and re-order them before passing them to the
state machines.  The re-ordering requirement also needs a
change to sequence number handling.  Especially the acceptable
sequence number range in condition (ii) of the following text in
section 4.1.4 would need to be changed to consider re-ordering.

"
   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.
"

The re-ordering requirement seems to be a significant change to the
PANA protocol.

Also consider the following case:

- A requester sends a request X.

- No answer for X is received for a while.

- The requester sends a PANA-Ping-Request for peer liveness test.

- A PANA-Ping-Answer is received from the peer before an answer for X,
but it is handled as an out-of-order packet and has to be buffered to
wait for an answer for X.

This would mean that non-lock-step PANA-ping and lock-step PANA-ping
are not much different in their high-level behaviors.  At least I can
say that non-lock-step PANA-ping does not pay for the incurring cost
to change the PANA protocol to support re-ordering and we should not
do that.

Regards,

Yoshihiro Ohba


On Mon, Aug 23, 2004 at 03:32:10PM -0700, Alper Yegin wrote:
> > > > I think we can use other tools for debugging as we normally do for
> > > > other protocol implementations.
> > >
> > > I'm thinking of this as similar to PPP echo-request/reply.
> > 
> > PPP echo is allowed only for its LCP Opened state, not for arbitrary
> > state.
> 
> I noticed that. But unless there is a technical reason, I don't think we
> should inherit the same limitations.
> 
> > > > > b- to discover the state of the peer (e.g., after a crash and
> > > reboot.
> > > > > Before the crash, the sender might have been in a state other
> than
> > > > > OPEN).
> > > >
> > > > Can't a simple method "wait for the current authentication session
> to
> > > > fail" be used here?
> > >
> > > The discovery can be much faster by using the ping if we didn't have
> to
> > > wait for timeouts.
> > 
> > If rebooting events are rare, I don't much care about timeouts for
> > rare events.
> > 
> > >
> > > > I do not have a serious demand on doing liveness
> > > > test for an incomplete session (but others may have...).
> > >
> > > I think there are many ways this ability (to send PANA-ping at any
> time)
> > > is useful. We might not be able to exhaust them right now. I just
> don't
> > > want to limit its usage to certain states. Unless it complicates
> > > anything I don't see why not have this flexibility.
> > 
> > I have a bit concern on the complexity needed to support this
> > flexibility from the state machine point of view, and my previous
> > question on lock-step operation relates to that.  I don't think just
> > having an independent state machine for pinging works for a protocol
> > that is designed under lock-step operations.
> 
> I still don't understand the complexity on the state machine. My
> recommendation is not to include PANA-ping in the (main) state machine.
> 
> And being lock-step was never a design goal or requirement. If this
> addition is breaking the lock-step nature, I don't see a problem, unless
> there was a benefit of being lock-stepped and now we are losing it. Are
> we?
> 
> Alper
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > >
> > > Alper
> > >
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > >
> > > > > Alper
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > Yoshihiro Ohba
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Alper
> > > > > > >
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > > > > Sent: Sunday, September 19, 2004 5:12 PM
> > > > > > > > To: Alper Yegin
> > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear
> usage
> > > of
> > > > > > > "reauth"
> > > > > > > > messages
> > > > > > > >
> > > > > > > > In draft-ohba-pana-statemachine-00.txt, there is a state
> > > WAIT_PRAA
> > > > > > > > (which transits only from OPEN state) in both PaC and PAA
> > > state
> > > > > > > > machines to wait for PANA-Reauth-Answer after sending
> > > > > > > > PANA-Reauth-Request.  Since we are replacing PANA-Requth-*
> > > with
> > > > > > > > PANA-Ping-*, the WAIT_PRAA state would be replaced with
> > > WAIT_PPA.
> > > > > I
> > > > > > > > am afraid if we need additional transitions to the
> WAIT_PPA
> > > state
> > > > > from
> > > > > > > > several states, it would complicate the state machines and
> I
> > > am
> > > > > > > > wondering what is the benefit of adding such complexity.
> > > > > > > >
> > > > > > > > Yoshihiro Ohba
> > > > > > > >
> > > > > > > > On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper Yegin
> wrote:
> > > > > > > > > Yoshi,
> > > > > > > > >
> > > > > > > > > I never thought we would need to deal with PANA-ping in
> the
> > > > > state
> > > > > > > > > machine.
> > > > > > > > > I perceive it as a tool that can be used asynchronous to
> the
> > > > > state
> > > > > > > > > machine, and does not automatically impact the state
> > > machine.
> > > > > [Sure,
> > > > > > > > > PANA implementation can use PANA ping to discover
> dead-peer,
> > > > > just
> > > > > > > like
> > > > > > > > > it could use ICMP echos, or L2 indications]. If a state
> had
> > > > > > > explicitly
> > > > > > > > > called for using PANA-ping, then we must have
> incorporated
> > > it in
> > > > > the
> > > > > > > > > state machine.
> > > > > > > > >
> > > > > > > > > Alper
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > > > > > > Sent: Sunday, September 19, 2004 4:37 PM
> > > > > > > > > > To: Alper Yegin
> > > > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and
> unclear
> > > usage
> > > > > of
> > > > > > > > > "reauth"
> > > > > > > > > > messages
> > > > > > > > > >
> > > > > > > > > > On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper Yegin
> > > wrote:
> > > > > > > > > > > > Should PANA-Ping-Request be allowed in discovery
> and
> > > > > initial
> > > > > > > > > handshake
> > > > > > > > > > > > phase?
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > Should PANA-Ping-Request be allowed in
> authentication
> > > > > phase?
> > > > > > > > > > >
> > > > > > > > > > > I thought about these. I decided to let the ping
> > > behavior
> > > > > handle
> > > > > > > > > this
> > > > > > > > > > > automatically. If there is an established pana
> session
> > > on
> > > > > the
> > > > > > > peer,
> > > > > > > > > it
> > > > > > > > > > > will respond. Otherwise, ping request will be
> silently
> > > > > > > discarded.
> > > > > > > > > This
> > > > > > > > > > > behavior can be followed in any state. [Also, PDI
> and
> > > > > PAR/PAN
> > > > > > > can be
> > > > > > > > > > > sent even when there is an established PANA session.
> > > Hence
> > > > > ping
> > > > > > > > > should
> > > > > > > > > > > work in that case.]
> > > > > > > > > >
> > > > > > > > > > It is probablly easier to do that at the receiving
> side of
> > > the
> > > > > > > ping
> > > > > > > > > > request, but what about transmitting side?  If we
> allow a
> > > PAA
> > > > > or a
> > > > > > > PaC
> > > > > > > > > > to send a PANA-Ping-Request and receiving a
> > > PANA-Ping-Answer
> > > > > > > between
> > > > > > > > > > two consecutive PANA-Auth-Request/Answer exchanges in
> > > > > > > authentication
> > > > > > > > > > phase, it would complicate the state machines
> (probably
> > > one
> > > > > > > additional
> > > > > > > > > > state is needed to support this case in the PaC and
> PAA
> > > state
> > > > > > > > > > machines).  I have a similar observation for PANA
> pinging
> > > in
> > > > > > > discovery
> > > > > > > > > > and initial handshake phase.
> > > > > > > > > >
> > > > > > > > > > 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
> 

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


From pana-bounces@ietf.org  Tue Aug 24 14:33:40 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 OAA01275
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 14:33:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Bzfmw-0003c9-TX; Tue, 24 Aug 2004 14:12:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzfXw-00075V-SE
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 13:57:24 -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 NAA28332
	for <pana@ietf.org>; Tue, 24 Aug 2004 13:57:18 -0400 (EDT)
Received: from brmea-mail-3.sun.com ([192.18.98.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzfYP-0005qi-S4
	for pana@ietf.org; Tue, 24 Aug 2004 13:57:55 -0400
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id i7OHvFil026614; 
	Tue, 24 Aug 2004 11:57:16 -0600 (MDT)
Received: from localhost (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by bebop.France.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with SMTP id
	i7OHvDJR026148; Tue, 24 Aug 2004 19:57:14 +0200 (MEST)
Date: Tue, 24 Aug 2004 10:57:39 -0700 (PDT)
From: Erik Nordmark <Erik.Nordmark@sun.com>
Subject: Re: [Pana] Issue106: sequence number on rexmited messages must be
	incremented
To: Alper Yegin <alper.yegin@samsung.com>
In-Reply-To: "Your message with ID"
	<008601c483bd$1924db80$0041fea9@sisa.samsung.com>
Message-ID: <Roam.SIMC.2.0.6.1093370259.26852.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: "'Erik Nordmark'" <Erik.Nordmark@sun.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Erik Nordmark <Erik.Nordmark@sun.com>
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 your review feedback, you had said:
> 
> - the retransmission text says that a retransmitted packet has a new 
>   sequence number. This makes no sense to me.
> 
> Can you please elaborate what kind of issues you are seeing with this.

Retransmissions are needed in two cases:
1. The message was lost
2. The acknowledgement of the message was lost

If a different sequence number is used for the retransmission
and #2 applies, then 2 copies of the message would be delivered
to the upper layers since PANA would have no mechanism to tell that
it has already received the message once.

  Erik


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


From pana-bounces@ietf.org  Tue Aug 24 15:00: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 PAA02940
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 15:00: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 1Bzg7f-0008PS-7t; Tue, 24 Aug 2004 14:34:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bzfw8-0004vn-9n
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 14:22:24 -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 OAA00417
	for <pana@ietf.org>; Tue, 24 Aug 2004 14:22:17 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bzfwb-0006Lw-Qp
	for pana@ietf.org; Tue, 24 Aug 2004 14:22:54 -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 <0I2Y00401QZYNJ@mailout2.samsung.com> for pana@ietf.org; Wed,
	25 Aug 2004 03:21: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 <0I2Y00HAZQZYJ7@mailout2.samsung.com> for pana@ietf.org;
	Wed, 25 Aug 2004 03:21:34 +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 <0I2Y00063QZWX0@mmp2.samsung.com> for
	pana@ietf.org; Wed, 25 Aug 2004 03:21:34 +0900 (KST)
Date: Tue, 24 Aug 2004 11:21:31 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20041024140855.GS3131@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <000001c48a07$2f655230$0041fea9@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: a5d64674af3d12893846a18a44c07b83
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,

Thank you for the analysis. I was thinking about something like 2 but I
totally missed the sequence numbering issue. While thinking about it,
some other issue came to my mind. I think these are related, let me
describe it.

  PaC       PAA   seq.nos.
1. <---------      x,y
2. --------->      y+1,x
3. ---+            y+2,x
4.    |  +---      x+1,y+1
   <--|--+
      +----->

Both message 3 and 4 would be dropped by the recipients. This situation
is possible even without PANA-ping, as we allow PaC to generate other
types of packets on its own (e.g., termination request, update request).

Alper






> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Sunday, October 24, 2004 7:09 AM
> To: Alper Yegin
> Cc: 'Yoshihiro Ohba'; pana@ietf.org
> Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
"reauth"
> messages
> 
> Hi Alper,
> 
> Please see my analysis below.
> 
> By not including PANA-ping in the main state machine, I presume that
> PANA-ping behavior is described in a separate state machine such as a
> pana-ping state machine.  There are two design choices on how to
> define the pana-ping state machine depending on whether PANA is
> designed as a lock-step protocol or not.
> 
> 1.  Lock-step PANA-ping
> 
> Since it is lock-step, it is prohibited to send a new request if there
> is an outstanding request.  The pana-ping state machine and the main
> state machine need to coordinate to guarantee this nature, probably by
> defining a variable that is shared between the pana-ping state machine
> and the main state machine to indicate whether there is an outstanding
> request.  Also, exclusive write access to the variable from the two
> state machines would be needed.  But how can such an exclusive write
> access in the two state simply be described in the two state machines?
> Or is there other way to describe the coordination in a simple manner?
> 
> 2. Non-lock-step PANA-ping
> 
> In this case, it is allowed to send a new request regardless of
> whether there is an outstanding request.  This means that there can be
> multiple outstanding requests.  Since the answers for the outstanding
> requests can arrive out of order, the requester needs to buffer
> out-of-order answers and re-order them before passing them to the
> state machines.  The re-ordering requirement also needs a
> change to sequence number handling.  Especially the acceptable
> sequence number range in condition (ii) of the following text in
> section 4.1.4 would need to be changed to consider re-ordering.
> 
> "
>    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.
> "
> 
> The re-ordering requirement seems to be a significant change to the
> PANA protocol.
> 
> Also consider the following case:
> 
> - A requester sends a request X.
> 
> - No answer for X is received for a while.
> 
> - The requester sends a PANA-Ping-Request for peer liveness test.
> 
> - A PANA-Ping-Answer is received from the peer before an answer for X,
> but it is handled as an out-of-order packet and has to be buffered to
> wait for an answer for X.
> 
> This would mean that non-lock-step PANA-ping and lock-step PANA-ping
> are not much different in their high-level behaviors.  At least I can
> say that non-lock-step PANA-ping does not pay for the incurring cost
> to change the PANA protocol to support re-ordering and we should not
> do that.
> 
> Regards,
> 
> Yoshihiro Ohba
> 
> 
> On Mon, Aug 23, 2004 at 03:32:10PM -0700, Alper Yegin wrote:
> > > > > I think we can use other tools for debugging as we normally do
for
> > > > > other protocol implementations.
> > > >
> > > > I'm thinking of this as similar to PPP echo-request/reply.
> > >
> > > PPP echo is allowed only for its LCP Opened state, not for
arbitrary
> > > state.
> >
> > I noticed that. But unless there is a technical reason, I don't
think we
> > should inherit the same limitations.
> >
> > > > > > b- to discover the state of the peer (e.g., after a crash
and
> > > > reboot.
> > > > > > Before the crash, the sender might have been in a state
other
> > than
> > > > > > OPEN).
> > > > >
> > > > > Can't a simple method "wait for the current authentication
session
> > to
> > > > > fail" be used here?
> > > >
> > > > The discovery can be much faster by using the ping if we didn't
have
> > to
> > > > wait for timeouts.
> > >
> > > If rebooting events are rare, I don't much care about timeouts for
> > > rare events.
> > >
> > > >
> > > > > I do not have a serious demand on doing liveness
> > > > > test for an incomplete session (but others may have...).
> > > >
> > > > I think there are many ways this ability (to send PANA-ping at
any
> > time)
> > > > is useful. We might not be able to exhaust them right now. I
just
> > don't
> > > > want to limit its usage to certain states. Unless it complicates
> > > > anything I don't see why not have this flexibility.
> > >
> > > I have a bit concern on the complexity needed to support this
> > > flexibility from the state machine point of view, and my previous
> > > question on lock-step operation relates to that.  I don't think
just
> > > having an independent state machine for pinging works for a
protocol
> > > that is designed under lock-step operations.
> >
> > I still don't understand the complexity on the state machine. My
> > recommendation is not to include PANA-ping in the (main) state
machine.
> >
> > And being lock-step was never a design goal or requirement. If this
> > addition is breaking the lock-step nature, I don't see a problem,
unless
> > there was a benefit of being lock-stepped and now we are losing it.
Are
> > we?
> >
> > Alper
> >
> >
> >
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > > >
> > > > Alper
> > > >
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > >
> > > > > >
> > > > > > Alper
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Yoshihiro Ohba
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > Alper
> > > > > > > >
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > > > > > Sent: Sunday, September 19, 2004 5:12 PM
> > > > > > > > > To: Alper Yegin
> > > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and
unclear
> > usage
> > > > of
> > > > > > > > "reauth"
> > > > > > > > > messages
> > > > > > > > >
> > > > > > > > > In draft-ohba-pana-statemachine-00.txt, there is a
state
> > > > WAIT_PRAA
> > > > > > > > > (which transits only from OPEN state) in both PaC and
PAA
> > > > state
> > > > > > > > > machines to wait for PANA-Reauth-Answer after sending
> > > > > > > > > PANA-Reauth-Request.  Since we are replacing
PANA-Requth-*
> > > > with
> > > > > > > > > PANA-Ping-*, the WAIT_PRAA state would be replaced
with
> > > > WAIT_PPA.
> > > > > > I
> > > > > > > > > am afraid if we need additional transitions to the
> > WAIT_PPA
> > > > state
> > > > > > from
> > > > > > > > > several states, it would complicate the state machines
and
> > I
> > > > am
> > > > > > > > > wondering what is the benefit of adding such
complexity.
> > > > > > > > >
> > > > > > > > > Yoshihiro Ohba
> > > > > > > > >
> > > > > > > > > On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper Yegin
> > wrote:
> > > > > > > > > > Yoshi,
> > > > > > > > > >
> > > > > > > > > > I never thought we would need to deal with PANA-ping
in
> > the
> > > > > > state
> > > > > > > > > > machine.
> > > > > > > > > > I perceive it as a tool that can be used
asynchronous to
> > the
> > > > > > state
> > > > > > > > > > machine, and does not automatically impact the state
> > > > machine.
> > > > > > [Sure,
> > > > > > > > > > PANA implementation can use PANA ping to discover
> > dead-peer,
> > > > > > just
> > > > > > > > like
> > > > > > > > > > it could use ICMP echos, or L2 indications]. If a
state
> > had
> > > > > > > > explicitly
> > > > > > > > > > called for using PANA-ping, then we must have
> > incorporated
> > > > it in
> > > > > > the
> > > > > > > > > > state machine.
> > > > > > > > > >
> > > > > > > > > > Alper
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: Yoshihiro Ohba
[mailto:yohba@tari.toshiba.com]
> > > > > > > > > > > Sent: Sunday, September 19, 2004 4:37 PM
> > > > > > > > > > > To: Alper Yegin
> > > > > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and
> > unclear
> > > > usage
> > > > > > of
> > > > > > > > > > "reauth"
> > > > > > > > > > > messages
> > > > > > > > > > >
> > > > > > > > > > > On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper
Yegin
> > > > wrote:
> > > > > > > > > > > > > Should PANA-Ping-Request be allowed in
discovery
> > and
> > > > > > initial
> > > > > > > > > > handshake
> > > > > > > > > > > > > phase?
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > > Should PANA-Ping-Request be allowed in
> > authentication
> > > > > > phase?
> > > > > > > > > > > >
> > > > > > > > > > > > I thought about these. I decided to let the ping
> > > > behavior
> > > > > > handle
> > > > > > > > > > this
> > > > > > > > > > > > automatically. If there is an established pana
> > session
> > > > on
> > > > > > the
> > > > > > > > peer,
> > > > > > > > > > it
> > > > > > > > > > > > will respond. Otherwise, ping request will be
> > silently
> > > > > > > > discarded.
> > > > > > > > > > This
> > > > > > > > > > > > behavior can be followed in any state. [Also,
PDI
> > and
> > > > > > PAR/PAN
> > > > > > > > can be
> > > > > > > > > > > > sent even when there is an established PANA
session.
> > > > Hence
> > > > > > ping
> > > > > > > > > > should
> > > > > > > > > > > > work in that case.]
> > > > > > > > > > >
> > > > > > > > > > > It is probablly easier to do that at the receiving
> > side of
> > > > the
> > > > > > > > ping
> > > > > > > > > > > request, but what about transmitting side?  If we
> > allow a
> > > > PAA
> > > > > > or a
> > > > > > > > PaC
> > > > > > > > > > > to send a PANA-Ping-Request and receiving a
> > > > PANA-Ping-Answer
> > > > > > > > between
> > > > > > > > > > > two consecutive PANA-Auth-Request/Answer exchanges
in
> > > > > > > > authentication
> > > > > > > > > > > phase, it would complicate the state machines
> > (probably
> > > > one
> > > > > > > > additional
> > > > > > > > > > > state is needed to support this case in the PaC
and
> > PAA
> > > > state
> > > > > > > > > > > machines).  I have a similar observation for PANA
> > pinging
> > > > in
> > > > > > > > discovery
> > > > > > > > > > > and initial handshake phase.
> > > > > > > > > > >
> > > > > > > > > > > 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
> >


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


From pana-bounces@ietf.org  Tue Aug 24 17:06: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 RAA11511
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 17:06: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 1Bzi4H-0004S0-Vj; Tue, 24 Aug 2004 16:38:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bzhvi-0000xW-Mz
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 16:30: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 QAA09302
	for <pana@ietf.org>; Tue, 24 Aug 2004 16:29:59 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzhwC-0000Dq-FG
	for pana@ietf.org; Tue, 24 Aug 2004 16:30:38 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7OKTubv022243;
	Wed, 25 Aug 2004 05:29:56 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7OKTupd020170;
	Wed, 25 Aug 2004 05:29:56 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	FAA20169 ; Wed, 25 Aug 2004 05:29:56 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id FAA08851; Wed, 25 Aug 2004 05:29:55 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7OKTtkk013967;
	Wed, 25 Aug 2004 05:29:55 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7OKTswE014684;
	Wed, 25 Aug 2004 05:29:55 +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 <0I2Y00HU0WXQOL@tsbpo1.po.toshiba.co.jp>; Wed,
	25 Aug 2004 05:29:54 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bzhuj-00028f-00; Tue, 24 Aug 2004 13:29:05 -0700
Date: Tue, 24 Aug 2004 16:29:04 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <000001c48a07$2f655230$0041fea9@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040824202904.GE1024@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+20040803i
References: <20041024140855.GS3131@steelhead>
	<000001c48a07$2f655230$0041fea9@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9178bae9f85419fdc08e9f2c86e345d0
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, Aug 24, 2004 at 11:21:31AM -0700, Alper Yegin wrote:
> Hi Yoshi,
> 
> Thank you for the analysis. I was thinking about something like 2 but I
> totally missed the sequence numbering issue. While thinking about it,
> some other issue came to my mind. I think these are related, let me
> describe it.
> 
>   PaC       PAA   seq.nos.
> 1. <---------      x,y
> 2. --------->      y+1,x
> 3. ---+            y+2,x
> 4.    |  +---      x+1,y+1
>    <--|--+
>       +----->
> 
> Both message 3 and 4 would be dropped by the recipients. This situation
> is possible even without PANA-ping, as we allow PaC to generate other
> types of packets on its own (e.g., termination request, update request).

Since the above example does not show the message type for each
message, so it would be difficult to discuss the issue on
non-lock-step vs. lock-step operations based on the above example.
But message 3 and 4 seem to be valid at least *in terms of sequence
numbers*.

Yoshihiro Ohba



> 
> Alper
> 
> 
> 
> 
> 
> 
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Sunday, October 24, 2004 7:09 AM
> > To: Alper Yegin
> > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
> "reauth"
> > messages
> > 
> > Hi Alper,
> > 
> > Please see my analysis below.
> > 
> > By not including PANA-ping in the main state machine, I presume that
> > PANA-ping behavior is described in a separate state machine such as a
> > pana-ping state machine.  There are two design choices on how to
> > define the pana-ping state machine depending on whether PANA is
> > designed as a lock-step protocol or not.
> > 
> > 1.  Lock-step PANA-ping
> > 
> > Since it is lock-step, it is prohibited to send a new request if there
> > is an outstanding request.  The pana-ping state machine and the main
> > state machine need to coordinate to guarantee this nature, probably by
> > defining a variable that is shared between the pana-ping state machine
> > and the main state machine to indicate whether there is an outstanding
> > request.  Also, exclusive write access to the variable from the two
> > state machines would be needed.  But how can such an exclusive write
> > access in the two state simply be described in the two state machines?
> > Or is there other way to describe the coordination in a simple manner?
> > 
> > 2. Non-lock-step PANA-ping
> > 
> > In this case, it is allowed to send a new request regardless of
> > whether there is an outstanding request.  This means that there can be
> > multiple outstanding requests.  Since the answers for the outstanding
> > requests can arrive out of order, the requester needs to buffer
> > out-of-order answers and re-order them before passing them to the
> > state machines.  The re-ordering requirement also needs a
> > change to sequence number handling.  Especially the acceptable
> > sequence number range in condition (ii) of the following text in
> > section 4.1.4 would need to be changed to consider re-ordering.
> > 
> > "
> >    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.
> > "
> > 
> > The re-ordering requirement seems to be a significant change to the
> > PANA protocol.
> > 
> > Also consider the following case:
> > 
> > - A requester sends a request X.
> > 
> > - No answer for X is received for a while.
> > 
> > - The requester sends a PANA-Ping-Request for peer liveness test.
> > 
> > - A PANA-Ping-Answer is received from the peer before an answer for X,
> > but it is handled as an out-of-order packet and has to be buffered to
> > wait for an answer for X.
> > 
> > This would mean that non-lock-step PANA-ping and lock-step PANA-ping
> > are not much different in their high-level behaviors.  At least I can
> > say that non-lock-step PANA-ping does not pay for the incurring cost
> > to change the PANA protocol to support re-ordering and we should not
> > do that.
> > 
> > Regards,
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Mon, Aug 23, 2004 at 03:32:10PM -0700, Alper Yegin wrote:
> > > > > > I think we can use other tools for debugging as we normally do
> for
> > > > > > other protocol implementations.
> > > > >
> > > > > I'm thinking of this as similar to PPP echo-request/reply.
> > > >
> > > > PPP echo is allowed only for its LCP Opened state, not for
> arbitrary
> > > > state.
> > >
> > > I noticed that. But unless there is a technical reason, I don't
> think we
> > > should inherit the same limitations.
> > >
> > > > > > > b- to discover the state of the peer (e.g., after a crash
> and
> > > > > reboot.
> > > > > > > Before the crash, the sender might have been in a state
> other
> > > than
> > > > > > > OPEN).
> > > > > >
> > > > > > Can't a simple method "wait for the current authentication
> session
> > > to
> > > > > > fail" be used here?
> > > > >
> > > > > The discovery can be much faster by using the ping if we didn't
> have
> > > to
> > > > > wait for timeouts.
> > > >
> > > > If rebooting events are rare, I don't much care about timeouts for
> > > > rare events.
> > > >
> > > > >
> > > > > > I do not have a serious demand on doing liveness
> > > > > > test for an incomplete session (but others may have...).
> > > > >
> > > > > I think there are many ways this ability (to send PANA-ping at
> any
> > > time)
> > > > > is useful. We might not be able to exhaust them right now. I
> just
> > > don't
> > > > > want to limit its usage to certain states. Unless it complicates
> > > > > anything I don't see why not have this flexibility.
> > > >
> > > > I have a bit concern on the complexity needed to support this
> > > > flexibility from the state machine point of view, and my previous
> > > > question on lock-step operation relates to that.  I don't think
> just
> > > > having an independent state machine for pinging works for a
> protocol
> > > > that is designed under lock-step operations.
> > >
> > > I still don't understand the complexity on the state machine. My
> > > recommendation is not to include PANA-ping in the (main) state
> machine.
> > >
> > > And being lock-step was never a design goal or requirement. If this
> > > addition is breaking the lock-step nature, I don't see a problem,
> unless
> > > there was a benefit of being lock-stepped and now we are losing it.
> Are
> > > we?
> > >
> > > Alper
> > >
> > >
> > >
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > >
> > > > > Alper
> > > > >
> > > > > >
> > > > > > Yoshihiro Ohba
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Alper
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > Yoshihiro Ohba
> > > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > Alper
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > -----Original Message-----
> > > > > > > > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > > > > > > Sent: Sunday, September 19, 2004 5:12 PM
> > > > > > > > > > To: Alper Yegin
> > > > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and
> unclear
> > > usage
> > > > > of
> > > > > > > > > "reauth"
> > > > > > > > > > messages
> > > > > > > > > >
> > > > > > > > > > In draft-ohba-pana-statemachine-00.txt, there is a
> state
> > > > > WAIT_PRAA
> > > > > > > > > > (which transits only from OPEN state) in both PaC and
> PAA
> > > > > state
> > > > > > > > > > machines to wait for PANA-Reauth-Answer after sending
> > > > > > > > > > PANA-Reauth-Request.  Since we are replacing
> PANA-Requth-*
> > > > > with
> > > > > > > > > > PANA-Ping-*, the WAIT_PRAA state would be replaced
> with
> > > > > WAIT_PPA.
> > > > > > > I
> > > > > > > > > > am afraid if we need additional transitions to the
> > > WAIT_PPA
> > > > > state
> > > > > > > from
> > > > > > > > > > several states, it would complicate the state machines
> and
> > > I
> > > > > am
> > > > > > > > > > wondering what is the benefit of adding such
> complexity.
> > > > > > > > > >
> > > > > > > > > > Yoshihiro Ohba
> > > > > > > > > >
> > > > > > > > > > On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper Yegin
> > > wrote:
> > > > > > > > > > > Yoshi,
> > > > > > > > > > >
> > > > > > > > > > > I never thought we would need to deal with PANA-ping
> in
> > > the
> > > > > > > state
> > > > > > > > > > > machine.
> > > > > > > > > > > I perceive it as a tool that can be used
> asynchronous to
> > > the
> > > > > > > state
> > > > > > > > > > > machine, and does not automatically impact the state
> > > > > machine.
> > > > > > > [Sure,
> > > > > > > > > > > PANA implementation can use PANA ping to discover
> > > dead-peer,
> > > > > > > just
> > > > > > > > > like
> > > > > > > > > > > it could use ICMP echos, or L2 indications]. If a
> state
> > > had
> > > > > > > > > explicitly
> > > > > > > > > > > called for using PANA-ping, then we must have
> > > incorporated
> > > > > it in
> > > > > > > the
> > > > > > > > > > > state machine.
> > > > > > > > > > >
> > > > > > > > > > > Alper
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: Yoshihiro Ohba
> [mailto:yohba@tari.toshiba.com]
> > > > > > > > > > > > Sent: Sunday, September 19, 2004 4:37 PM
> > > > > > > > > > > > To: Alper Yegin
> > > > > > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and
> > > unclear
> > > > > usage
> > > > > > > of
> > > > > > > > > > > "reauth"
> > > > > > > > > > > > messages
> > > > > > > > > > > >
> > > > > > > > > > > > On Thu, Aug 19, 2004 at 12:45:18PM -0700, Alper
> Yegin
> > > > > wrote:
> > > > > > > > > > > > > > Should PANA-Ping-Request be allowed in
> discovery
> > > and
> > > > > > > initial
> > > > > > > > > > > handshake
> > > > > > > > > > > > > > phase?
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Should PANA-Ping-Request be allowed in
> > > authentication
> > > > > > > phase?
> > > > > > > > > > > > >
> > > > > > > > > > > > > I thought about these. I decided to let the ping
> > > > > behavior
> > > > > > > handle
> > > > > > > > > > > this
> > > > > > > > > > > > > automatically. If there is an established pana
> > > session
> > > > > on
> > > > > > > the
> > > > > > > > > peer,
> > > > > > > > > > > it
> > > > > > > > > > > > > will respond. Otherwise, ping request will be
> > > silently
> > > > > > > > > discarded.
> > > > > > > > > > > This
> > > > > > > > > > > > > behavior can be followed in any state. [Also,
> PDI
> > > and
> > > > > > > PAR/PAN
> > > > > > > > > can be
> > > > > > > > > > > > > sent even when there is an established PANA
> session.
> > > > > Hence
> > > > > > > ping
> > > > > > > > > > > should
> > > > > > > > > > > > > work in that case.]
> > > > > > > > > > > >
> > > > > > > > > > > > It is probablly easier to do that at the receiving
> > > side of
> > > > > the
> > > > > > > > > ping
> > > > > > > > > > > > request, but what about transmitting side?  If we
> > > allow a
> > > > > PAA
> > > > > > > or a
> > > > > > > > > PaC
> > > > > > > > > > > > to send a PANA-Ping-Request and receiving a
> > > > > PANA-Ping-Answer
> > > > > > > > > between
> > > > > > > > > > > > two consecutive PANA-Auth-Request/Answer exchanges
> in
> > > > > > > > > authentication
> > > > > > > > > > > > phase, it would complicate the state machines
> > > (probably
> > > > > one
> > > > > > > > > additional
> > > > > > > > > > > > state is needed to support this case in the PaC
> and
> > > PAA
> > > > > state
> > > > > > > > > > > > machines).  I have a similar observation for PANA
> > > pinging
> > > > > in
> > > > > > > > > discovery
> > > > > > > > > > > > and initial handshake phase.
> > > > > > > > > > > >
> > > > > > > > > > > > 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
> > >
> 
> 
> _______________________________________________
> 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 Aug 24 18:31: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 SAA19306
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 18:31: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 1BzjVj-0007we-Ok; Tue, 24 Aug 2004 18:11:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bzj9f-0006tt-FO
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 17:48:36 -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 RAA14410
	for <pana@ietf.org>; Tue, 24 Aug 2004 17:48:27 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzjAA-0001h6-Pw
	for pana@ietf.org; Tue, 24 Aug 2004 17:49:07 -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 <0I2Z00H010JWCA@mailout2.samsung.com> for pana@ietf.org; Wed,
	25 Aug 2004 06:47:57 +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 <0I2Z00HMA0JWIC@mailout2.samsung.com> for pana@ietf.org;
	Wed, 25 Aug 2004 06:47:56 +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 <0I2Z00DMT0JUAE@mmp1.samsung.com> for
	pana@ietf.org; Wed, 25 Aug 2004 06:47:56 +0900 (KST)
Date: Tue, 24 Aug 2004 14:47:54 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040824202904.GE1024@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <001001c48a24$03b9f1f0$0041fea9@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 7cb76adb986247703cbb5582da68b5fc
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,

> >   PaC       PAA   seq.nos.
> > 1. <---------      x,y
> > 2. --------->      y+1,x
> > 3. ---+            y+2,x
> > 4.    |  +---      x+1,y+1
> >    <--|--+
> >       +----->

Imagine 3 is a termination request (PTR), and 4 is an authentication
request (PAR). I'm trying to point out a problem with the current design
(even without PANA-ping). 

Do you see the same problem? 

The solution to this may help answer what to do with PANA-ping question.

Alper






> >
> > Both message 3 and 4 would be dropped by the recipients. This
situation
> > is possible even without PANA-ping, as we allow PaC to generate
other
> > types of packets on its own (e.g., termination request, update
request).
> 
> Since the above example does not show the message type for each
> message, so it would be difficult to discuss the issue on
> non-lock-step vs. lock-step operations based on the above example.
> But message 3 and 4 seem to be valid at least *in terms of sequence
> numbers*.
> 
> Yoshihiro Ohba
> 
> 
> 
> >
> > Alper
> >
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: Sunday, October 24, 2004 7:09 AM
> > > To: Alper Yegin
> > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
> > "reauth"
> > > messages
> > >
> > > Hi Alper,
> > >
> > > Please see my analysis below.
> > >
> > > By not including PANA-ping in the main state machine, I presume
that
> > > PANA-ping behavior is described in a separate state machine such
as a
> > > pana-ping state machine.  There are two design choices on how to
> > > define the pana-ping state machine depending on whether PANA is
> > > designed as a lock-step protocol or not.
> > >
> > > 1.  Lock-step PANA-ping
> > >
> > > Since it is lock-step, it is prohibited to send a new request if
there
> > > is an outstanding request.  The pana-ping state machine and the
main
> > > state machine need to coordinate to guarantee this nature,
probably by
> > > defining a variable that is shared between the pana-ping state
machine
> > > and the main state machine to indicate whether there is an
outstanding
> > > request.  Also, exclusive write access to the variable from the
two
> > > state machines would be needed.  But how can such an exclusive
write
> > > access in the two state simply be described in the two state
machines?
> > > Or is there other way to describe the coordination in a simple
manner?
> > >
> > > 2. Non-lock-step PANA-ping
> > >
> > > In this case, it is allowed to send a new request regardless of
> > > whether there is an outstanding request.  This means that there
can be
> > > multiple outstanding requests.  Since the answers for the
outstanding
> > > requests can arrive out of order, the requester needs to buffer
> > > out-of-order answers and re-order them before passing them to the
> > > state machines.  The re-ordering requirement also needs a
> > > change to sequence number handling.  Especially the acceptable
> > > sequence number range in condition (ii) of the following text in
> > > section 4.1.4 would need to be changed to consider re-ordering.
> > >
> > > "
> > >    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.
> > > "
> > >
> > > The re-ordering requirement seems to be a significant change to
the
> > > PANA protocol.
> > >
> > > Also consider the following case:
> > >
> > > - A requester sends a request X.
> > >
> > > - No answer for X is received for a while.
> > >
> > > - The requester sends a PANA-Ping-Request for peer liveness test.
> > >
> > > - A PANA-Ping-Answer is received from the peer before an answer
for X,
> > > but it is handled as an out-of-order packet and has to be buffered
to
> > > wait for an answer for X.
> > >
> > > This would mean that non-lock-step PANA-ping and lock-step
PANA-ping
> > > are not much different in their high-level behaviors.  At least I
can
> > > say that non-lock-step PANA-ping does not pay for the incurring
cost
> > > to change the PANA protocol to support re-ordering and we should
not
> > > do that.
> > >
> > > Regards,
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > > On Mon, Aug 23, 2004 at 03:32:10PM -0700, Alper Yegin wrote:
> > > > > > > I think we can use other tools for debugging as we
normally do
> > for
> > > > > > > other protocol implementations.
> > > > > >
> > > > > > I'm thinking of this as similar to PPP echo-request/reply.
> > > > >
> > > > > PPP echo is allowed only for its LCP Opened state, not for
> > arbitrary
> > > > > state.
> > > >
> > > > I noticed that. But unless there is a technical reason, I don't
> > think we
> > > > should inherit the same limitations.
> > > >
> > > > > > > > b- to discover the state of the peer (e.g., after a
crash
> > and
> > > > > > reboot.
> > > > > > > > Before the crash, the sender might have been in a state
> > other
> > > > than
> > > > > > > > OPEN).
> > > > > > >
> > > > > > > Can't a simple method "wait for the current authentication
> > session
> > > > to
> > > > > > > fail" be used here?
> > > > > >
> > > > > > The discovery can be much faster by using the ping if we
didn't
> > have
> > > > to
> > > > > > wait for timeouts.
> > > > >
> > > > > If rebooting events are rare, I don't much care about timeouts
for
> > > > > rare events.
> > > > >
> > > > > >
> > > > > > > I do not have a serious demand on doing liveness
> > > > > > > test for an incomplete session (but others may have...).
> > > > > >
> > > > > > I think there are many ways this ability (to send PANA-ping
at
> > any
> > > > time)
> > > > > > is useful. We might not be able to exhaust them right now. I
> > just
> > > > don't
> > > > > > want to limit its usage to certain states. Unless it
complicates
> > > > > > anything I don't see why not have this flexibility.
> > > > >
> > > > > I have a bit concern on the complexity needed to support this
> > > > > flexibility from the state machine point of view, and my
previous
> > > > > question on lock-step operation relates to that.  I don't
think
> > just
> > > > > having an independent state machine for pinging works for a
> > protocol
> > > > > that is designed under lock-step operations.
> > > >
> > > > I still don't understand the complexity on the state machine. My
> > > > recommendation is not to include PANA-ping in the (main) state
> > machine.
> > > >
> > > > And being lock-step was never a design goal or requirement. If
this
> > > > addition is breaking the lock-step nature, I don't see a
problem,
> > unless
> > > > there was a benefit of being lock-stepped and now we are losing
it.
> > Are
> > > > we?
> > > >
> > > > Alper
> > > >
> > > >
> > > >
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > >
> > > > > >
> > > > > > Alper
> > > > > >
> > > > > > >
> > > > > > > Yoshihiro Ohba
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > Alper
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > Yoshihiro Ohba
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Alper
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: Yoshihiro Ohba
[mailto:yohba@tari.toshiba.com]
> > > > > > > > > > > Sent: Sunday, September 19, 2004 5:12 PM
> > > > > > > > > > > To: Alper Yegin
> > > > > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and
> > unclear
> > > > usage
> > > > > > of
> > > > > > > > > > "reauth"
> > > > > > > > > > > messages
> > > > > > > > > > >
> > > > > > > > > > > In draft-ohba-pana-statemachine-00.txt, there is a
> > state
> > > > > > WAIT_PRAA
> > > > > > > > > > > (which transits only from OPEN state) in both PaC
and
> > PAA
> > > > > > state
> > > > > > > > > > > machines to wait for PANA-Reauth-Answer after
sending
> > > > > > > > > > > PANA-Reauth-Request.  Since we are replacing
> > PANA-Requth-*
> > > > > > with
> > > > > > > > > > > PANA-Ping-*, the WAIT_PRAA state would be replaced
> > with
> > > > > > WAIT_PPA.
> > > > > > > > I
> > > > > > > > > > > am afraid if we need additional transitions to the
> > > > WAIT_PPA
> > > > > > state
> > > > > > > > from
> > > > > > > > > > > several states, it would complicate the state
machines
> > and
> > > > I
> > > > > > am
> > > > > > > > > > > wondering what is the benefit of adding such
> > complexity.
> > > > > > > > > > >
> > > > > > > > > > > Yoshihiro Ohba
> > > > > > > > > > >
> > > > > > > > > > > On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper
Yegin
> > > > wrote:
> > > > > > > > > > > > Yoshi,
> > > > > > > > > > > >
> > > > > > > > > > > > I never thought we would need to deal with
PANA-ping
> > in
> > > > the
> > > > > > > > state
> > > > > > > > > > > > machine.
> > > > > > > > > > > > I perceive it as a tool that can be used
> > asynchronous to
> > > > the
> > > > > > > > state
> > > > > > > > > > > > machine, and does not automatically impact the
state
> > > > > > machine.
> > > > > > > > [Sure,
> > > > > > > > > > > > PANA implementation can use PANA ping to
discover
> > > > dead-peer,
> > > > > > > > just
> > > > > > > > > > like
> > > > > > > > > > > > it could use ICMP echos, or L2 indications]. If
a
> > state
> > > > had
> > > > > > > > > > explicitly
> > > > > > > > > > > > called for using PANA-ping, then we must have
> > > > incorporated
> > > > > > it in
> > > > > > > > the
> > > > > > > > > > > > state machine.
> > > > > > > > > > > >
> > > > > > > > > > > > Alper
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > From: Yoshihiro Ohba
> > [mailto:yohba@tari.toshiba.com]
> > > > > > > > > > > > > Sent: Sunday, September 19, 2004 4:37 PM
> > > > > > > > > > > > > To: Alper Yegin
> > > > > > > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent
and
> > > > unclear
> > > > > > usage
> > > > > > > > of
> > > > > > > > > > > > "reauth"
> > > > > > > > > > > > > messages
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Thu, Aug 19, 2004 at 12:45:18PM -0700,
Alper
> > Yegin
> > > > > > wrote:
> > > > > > > > > > > > > > > Should PANA-Ping-Request be allowed in
> > discovery
> > > > and
> > > > > > > > initial
> > > > > > > > > > > > handshake
> > > > > > > > > > > > > > > phase?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Should PANA-Ping-Request be allowed in
> > > > authentication
> > > > > > > > phase?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I thought about these. I decided to let the
ping
> > > > > > behavior
> > > > > > > > handle
> > > > > > > > > > > > this
> > > > > > > > > > > > > > automatically. If there is an established
pana
> > > > session
> > > > > > on
> > > > > > > > the
> > > > > > > > > > peer,
> > > > > > > > > > > > it
> > > > > > > > > > > > > > will respond. Otherwise, ping request will
be
> > > > silently
> > > > > > > > > > discarded.
> > > > > > > > > > > > This
> > > > > > > > > > > > > > behavior can be followed in any state.
[Also,
> > PDI
> > > > and
> > > > > > > > PAR/PAN
> > > > > > > > > > can be
> > > > > > > > > > > > > > sent even when there is an established PANA
> > session.
> > > > > > Hence
> > > > > > > > ping
> > > > > > > > > > > > should
> > > > > > > > > > > > > > work in that case.]
> > > > > > > > > > > > >
> > > > > > > > > > > > > It is probablly easier to do that at the
receiving
> > > > side of
> > > > > > the
> > > > > > > > > > ping
> > > > > > > > > > > > > request, but what about transmitting side?  If
we
> > > > allow a
> > > > > > PAA
> > > > > > > > or a
> > > > > > > > > > PaC
> > > > > > > > > > > > > to send a PANA-Ping-Request and receiving a
> > > > > > PANA-Ping-Answer
> > > > > > > > > > between
> > > > > > > > > > > > > two consecutive PANA-Auth-Request/Answer
exchanges
> > in
> > > > > > > > > > authentication
> > > > > > > > > > > > > phase, it would complicate the state machines
> > > > (probably
> > > > > > one
> > > > > > > > > > additional
> > > > > > > > > > > > > state is needed to support this case in the
PaC
> > and
> > > > PAA
> > > > > > state
> > > > > > > > > > > > > machines).  I have a similar observation for
PANA
> > > > pinging
> > > > > > in
> > > > > > > > > > discovery
> > > > > > > > > > > > > and initial handshake phase.
> > > > > > > > > > > > >
> > > > > > > > > > > > > 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
> > > >
> >
> >
> > _______________________________________________
> > 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 Aug 24 18:35: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 SAA19647
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 18:35: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 1BzjXh-000163-6h; Tue, 24 Aug 2004 18:13:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzjEo-0000N2-O5
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 17:53: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 RAA14581
	for <pana@ietf.org>; Tue, 24 Aug 2004 17:53:47 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzjFJ-0001lq-TH
	for pana@ietf.org; Tue, 24 Aug 2004 17:54:27 -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 <0I2Z00I010SS96@mailout2.samsung.com> for pana@ietf.org; Wed,
	25 Aug 2004 06:53:16 +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 <0I2Z004GE0SRYN@mailout2.samsung.com> for pana@ietf.org;
	Wed, 25 Aug 2004 06:53:15 +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 <0I2Z00IVE0SP50@mmp2.samsung.com> for
	pana@ietf.org; Wed, 25 Aug 2004 06:53:15 +0900 (KST)
Date: Tue, 24 Aug 2004 14:53:13 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue106: sequence number on rexmited messages must be
	incremented
In-reply-to: <Roam.SIMC.2.0.6.1093370259.26852.nordmark@bebop.france>
To: "'Erik Nordmark'" <Erik.Nordmark@sun.com>
Message-id: <001101c48a24$c20a7ee0$0041fea9@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 9182cfff02fae4f1b6e9349e01d62f32
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

> Retransmissions are needed in two cases:
> 1. The message was lost
> 2. The acknowledgement of the message was lost
> 
> If a different sequence number is used for the retransmission
> and #2 applies, then 2 copies of the message would be delivered
> to the upper layers since PANA would have no mechanism to tell that
> it has already received the message once.

Upper layer to PANA is EAP. Retransmission of EAP carrying messages are
not handled by PANA. An EAP-carrying PANA message is retransmitted only
when EAP retransmits the same EAP message. And in that case PANA may not
even know it is a retransmission.

Since retransmission is not caused by PANA, duplicate prevention should
not be provided by PANA either. 

If message duplication due to lower layer (PANA) retransmissions is the
concern, I think that should be fine.

Alper





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


From pana-bounces@ietf.org  Tue Aug 24 18:50: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 SAA20413
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 18:50: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 1Bzjm2-0007G8-Nc; Tue, 24 Aug 2004 18:28:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzjQP-0005Ku-7w
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 18:05:53 -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 SAA15406
	for <pana@ietf.org>; Tue, 24 Aug 2004 18:05:44 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzjQt-0001xg-Oz
	for pana@ietf.org; Tue, 24 Aug 2004 18:06:25 -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 <0I2Z009IT1CPVV@mailout1.samsung.com> for pana@ietf.org; Wed,
	25 Aug 2004 07:05:13 +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 <0I2Z006FD0ZE88@mailout1.samsung.com> for pana@ietf.org;
	Wed, 25 Aug 2004 06:57:14 +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 <0I2Z006280ZCHX@mmp1.samsung.com> for
	pana@ietf.org; Wed, 25 Aug 2004 06:57:14 +0900 (KST)
Date: Tue, 24 Aug 2004 14:57:12 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue106: sequence number on rexmited messages must be
	incremented
In-reply-to: <20040920132804.GG22998@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <001201c48a25$5074c730$0041fea9@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7BIT
Cc: "'Erik Nordmark'" <Erik.Nordmark@Sun.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

> If a retransmitted packet has a new sequence number, the sender would
> need to re-generate a new MAC AVP for every retransmitted packet that
> contains a MAC AVP, since the MAC computation covers PANA header.
> 
> This could be a performance issue at PAA which may have a large number
> of retransmitted messages to different PaCs.  

I'm not sure if optimizing the spec for this is justified. Are there any
such protocol examples?

> Also, if we don't change
> the sequence number for retransmitted packets, implementation would be
> much more simpler.

I'm not sure about that either. The PANA layer has to detect EAP
retransmissions. Either we need to accommodate that in the PANA-EAP
interface, or PANA must inspect the EAP payload. 

Alper



> 
> Yoshihiro Ohba
> 
> 
> On Mon, Aug 16, 2004 at 11:16:04AM -0700, Alper Yegin wrote:
> > Hi Erik,
> >
> > In your review feedback, you had said:
> >
> > - the retransmission text says that a retransmitted packet has a new
> >   sequence number. This makes no sense to me.
> >
> > Can you please elaborate what kind of issues you are seeing with
this.
> >
> > Thank you.
> >
> > 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 Aug 24 19:06: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 TAA21244
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 19:06: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 1BzkDv-0007EP-F2; Tue, 24 Aug 2004 18:57:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bzjpa-0000OC-DH
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 18:31: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 SAA19356
	for <pana@ietf.org>; Tue, 24 Aug 2004 18:31:46 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bzjq5-0002Ti-GX
	for pana@ietf.org; Tue, 24 Aug 2004 18:32:27 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7OMVUbv027235;
	Wed, 25 Aug 2004 07:31:30 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7OMVUmt007084;
	Wed, 25 Aug 2004 07:31:30 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	HAA07078 ; Wed, 25 Aug 2004 07:31:30 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA10021; Wed, 25 Aug 2004 07:31:29 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7OMVT0M017218;
	Wed, 25 Aug 2004 07:31:29 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7OMVSwE009690;
	Wed, 25 Aug 2004 07:31:28 +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 <0I2Z00KZ22KD68@tsbpo1.po.toshiba.co.jp>; Wed,
	25 Aug 2004 07:31:27 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BzjoK-0002lx-00; Tue, 24 Aug 2004 15:30:36 -0700
Date: Tue, 24 Aug 2004 18:30:36 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue106: sequence number on rexmited messages must be
	incremented
In-reply-to: <001201c48a25$5074c730$0041fea9@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040824223036.GF1024@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>,
	'Erik Nordmark' <Erik.Nordmark@Sun.COM>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040803i
References: <20040920132804.GG22998@steelhead>
	<001201c48a25$5074c730$0041fea9@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
        "'Erik Nordmark'" <Erik.Nordmark@Sun.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, Aug 24, 2004 at 02:57:12PM -0700, Alper Yegin wrote:
> > If a retransmitted packet has a new sequence number, the sender would
> > need to re-generate a new MAC AVP for every retransmitted packet that
> > contains a MAC AVP, since the MAC computation covers PANA header.
> > 
> > This could be a performance issue at PAA which may have a large number
> > of retransmitted messages to different PaCs.  
> 
> I'm not sure if optimizing the spec for this is justified. Are there any
> such protocol examples?

IKEv2 has Message ID which does not change for retransmitted messages.
The exact copy of the original IKEv2 message is retransmitted.

> 
> > Also, if we don't change
> > the sequence number for retransmitted packets, implementation would be
> > much more simpler.
> 
> I'm not sure about that either. The PANA layer has to detect EAP
> retransmissions. Either we need to accommodate that in the PANA-EAP
> interface, or PANA must inspect the EAP payload. 

Since PANA relies on the EAP retransmission mechanism for EAP
messages, PANA-Auth-Request messages are not retransmitted by PANA.
Thus, the same transmission sequence number should not be used for
PANA-Auth-Requests messages, regardless of whether the messages are
generated as a result of EAP retransmission or not.  

Yoshihiro Ohba


> 
> Alper
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Mon, Aug 16, 2004 at 11:16:04AM -0700, Alper Yegin wrote:
> > > Hi Erik,
> > >
> > > In your review feedback, you had said:
> > >
> > > - the retransmission text says that a retransmitted packet has a new
> > >   sequence number. This makes no sense to me.
> > >
> > > Can you please elaborate what kind of issues you are seeing with
> this.
> > >
> > > Thank you.
> > >
> > > 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 Aug 24 20:05: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 UAA25526
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 20:05: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 1Bzkn6-0001Zx-LE; Tue, 24 Aug 2004 19:33:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzkSA-0003FC-AK
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 19:11:47 -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 TAA21610
	for <pana@ietf.org>; Tue, 24 Aug 2004 19:11:38 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzkSd-000395-9h
	for pana@ietf.org; Tue, 24 Aug 2004 19:12:19 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7ONBZbv012835;
	Wed, 25 Aug 2004 08:11:35 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7ONBZJP028773;
	Wed, 25 Aug 2004 08:11:35 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	JAA28770 ; Wed, 25 Aug 2004 08:11:34 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA24657; Wed, 25 Aug 2004 08:11:34 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7ONBYEJ006761;
	Wed, 25 Aug 2004 08:11:34 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7ONBXwE000803;
	Wed, 25 Aug 2004 08:11: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 <0I2Z004AI4F49F@tsbpo1.po.toshiba.co.jp>; Wed,
	25 Aug 2004 08:11:32 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1BzkRP-0002zN-00; Tue, 24 Aug 2004 16:10:59 -0700
Date: Tue, 24 Aug 2004 19:10:59 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <001001c48a24$03b9f1f0$0041fea9@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040824231059.GG1024@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+20040803i
References: <20040824202904.GE1024@steelhead>
	<001001c48a24$03b9f1f0$0041fea9@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f251f249fc9a04067ce354aa0943ab98
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, Aug 24, 2004 at 02:47:54PM -0700, Alper Yegin wrote:
> Yoshi,
> 
> > >   PaC       PAA   seq.nos.
> > > 1. <---------      x,y
> > > 2. --------->      y+1,x
> > > 3. ---+            y+2,x
> > > 4.    |  +---      x+1,y+1
> > >    <--|--+
> > >       +----->
> 
> Imagine 3 is a termination request (PTR), and 4 is an authentication
> request (PAR). I'm trying to point out a problem with the current design
> (even without PANA-ping). 

According to draft-ohba-pana-statemachine-00.txt:

- A PTR is allowed to be sent only in OPEN state.  So the PaC is
assumed to be in OPEN state before sending message 3 and in SESS_TERM
state after sending message 3.  Message 4 (PAR) will be dropped by the
PaC since PAR is not expected in SESS_TERM state.

- The PAA is assumed to be somehow in WAIT_PAN state after sending
message 4 (PAR).  Message 3 (PTR) will be dropped by the PAA since PTR
is not expected in WAIT_PAN state.

Yoshihiro Ohba

> 
> Do you see the same problem? 
> 
> The solution to this may help answer what to do with PANA-ping question.
> 
> Alper
> 
> 
> 
> 
> 
> 
> > >
> > > Both message 3 and 4 would be dropped by the recipients. This
> situation
> > > is possible even without PANA-ping, as we allow PaC to generate
> other
> > > types of packets on its own (e.g., termination request, update
> request).
> > 
> > Since the above example does not show the message type for each
> > message, so it would be difficult to discuss the issue on
> > non-lock-step vs. lock-step operations based on the above example.
> > But message 3 and 4 seem to be valid at least *in terms of sequence
> > numbers*.
> > 
> > Yoshihiro Ohba
> > 
> > 
> > 
> > >
> > > Alper
> > >
> > >
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: Sunday, October 24, 2004 7:09 AM
> > > > To: Alper Yegin
> > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
> > > "reauth"
> > > > messages
> > > >
> > > > Hi Alper,
> > > >
> > > > Please see my analysis below.
> > > >
> > > > By not including PANA-ping in the main state machine, I presume
> that
> > > > PANA-ping behavior is described in a separate state machine such
> as a
> > > > pana-ping state machine.  There are two design choices on how to
> > > > define the pana-ping state machine depending on whether PANA is
> > > > designed as a lock-step protocol or not.
> > > >
> > > > 1.  Lock-step PANA-ping
> > > >
> > > > Since it is lock-step, it is prohibited to send a new request if
> there
> > > > is an outstanding request.  The pana-ping state machine and the
> main
> > > > state machine need to coordinate to guarantee this nature,
> probably by
> > > > defining a variable that is shared between the pana-ping state
> machine
> > > > and the main state machine to indicate whether there is an
> outstanding
> > > > request.  Also, exclusive write access to the variable from the
> two
> > > > state machines would be needed.  But how can such an exclusive
> write
> > > > access in the two state simply be described in the two state
> machines?
> > > > Or is there other way to describe the coordination in a simple
> manner?
> > > >
> > > > 2. Non-lock-step PANA-ping
> > > >
> > > > In this case, it is allowed to send a new request regardless of
> > > > whether there is an outstanding request.  This means that there
> can be
> > > > multiple outstanding requests.  Since the answers for the
> outstanding
> > > > requests can arrive out of order, the requester needs to buffer
> > > > out-of-order answers and re-order them before passing them to the
> > > > state machines.  The re-ordering requirement also needs a
> > > > change to sequence number handling.  Especially the acceptable
> > > > sequence number range in condition (ii) of the following text in
> > > > section 4.1.4 would need to be changed to consider re-ordering.
> > > >
> > > > "
> > > >    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.
> > > > "
> > > >
> > > > The re-ordering requirement seems to be a significant change to
> the
> > > > PANA protocol.
> > > >
> > > > Also consider the following case:
> > > >
> > > > - A requester sends a request X.
> > > >
> > > > - No answer for X is received for a while.
> > > >
> > > > - The requester sends a PANA-Ping-Request for peer liveness test.
> > > >
> > > > - A PANA-Ping-Answer is received from the peer before an answer
> for X,
> > > > but it is handled as an out-of-order packet and has to be buffered
> to
> > > > wait for an answer for X.
> > > >
> > > > This would mean that non-lock-step PANA-ping and lock-step
> PANA-ping
> > > > are not much different in their high-level behaviors.  At least I
> can
> > > > say that non-lock-step PANA-ping does not pay for the incurring
> cost
> > > > to change the PANA protocol to support re-ordering and we should
> not
> > > > do that.
> > > >
> > > > Regards,
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > On Mon, Aug 23, 2004 at 03:32:10PM -0700, Alper Yegin wrote:
> > > > > > > > I think we can use other tools for debugging as we
> normally do
> > > for
> > > > > > > > other protocol implementations.
> > > > > > >
> > > > > > > I'm thinking of this as similar to PPP echo-request/reply.
> > > > > >
> > > > > > PPP echo is allowed only for its LCP Opened state, not for
> > > arbitrary
> > > > > > state.
> > > > >
> > > > > I noticed that. But unless there is a technical reason, I don't
> > > think we
> > > > > should inherit the same limitations.
> > > > >
> > > > > > > > > b- to discover the state of the peer (e.g., after a
> crash
> > > and
> > > > > > > reboot.
> > > > > > > > > Before the crash, the sender might have been in a state
> > > other
> > > > > than
> > > > > > > > > OPEN).
> > > > > > > >
> > > > > > > > Can't a simple method "wait for the current authentication
> > > session
> > > > > to
> > > > > > > > fail" be used here?
> > > > > > >
> > > > > > > The discovery can be much faster by using the ping if we
> didn't
> > > have
> > > > > to
> > > > > > > wait for timeouts.
> > > > > >
> > > > > > If rebooting events are rare, I don't much care about timeouts
> for
> > > > > > rare events.
> > > > > >
> > > > > > >
> > > > > > > > I do not have a serious demand on doing liveness
> > > > > > > > test for an incomplete session (but others may have...).
> > > > > > >
> > > > > > > I think there are many ways this ability (to send PANA-ping
> at
> > > any
> > > > > time)
> > > > > > > is useful. We might not be able to exhaust them right now. I
> > > just
> > > > > don't
> > > > > > > want to limit its usage to certain states. Unless it
> complicates
> > > > > > > anything I don't see why not have this flexibility.
> > > > > >
> > > > > > I have a bit concern on the complexity needed to support this
> > > > > > flexibility from the state machine point of view, and my
> previous
> > > > > > question on lock-step operation relates to that.  I don't
> think
> > > just
> > > > > > having an independent state machine for pinging works for a
> > > protocol
> > > > > > that is designed under lock-step operations.
> > > > >
> > > > > I still don't understand the complexity on the state machine. My
> > > > > recommendation is not to include PANA-ping in the (main) state
> > > machine.
> > > > >
> > > > > And being lock-step was never a design goal or requirement. If
> this
> > > > > addition is breaking the lock-step nature, I don't see a
> problem,
> > > unless
> > > > > there was a benefit of being lock-stepped and now we are losing
> it.
> > > Are
> > > > > we?
> > > > >
> > > > > Alper
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > Yoshihiro Ohba
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Alper
> > > > > > >
> > > > > > > >
> > > > > > > > Yoshihiro Ohba
> > > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > Alper
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Yoshihiro Ohba
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Alper
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: Yoshihiro Ohba
> [mailto:yohba@tari.toshiba.com]
> > > > > > > > > > > > Sent: Sunday, September 19, 2004 5:12 PM
> > > > > > > > > > > > To: Alper Yegin
> > > > > > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent and
> > > unclear
> > > > > usage
> > > > > > > of
> > > > > > > > > > > "reauth"
> > > > > > > > > > > > messages
> > > > > > > > > > > >
> > > > > > > > > > > > In draft-ohba-pana-statemachine-00.txt, there is a
> > > state
> > > > > > > WAIT_PRAA
> > > > > > > > > > > > (which transits only from OPEN state) in both PaC
> and
> > > PAA
> > > > > > > state
> > > > > > > > > > > > machines to wait for PANA-Reauth-Answer after
> sending
> > > > > > > > > > > > PANA-Reauth-Request.  Since we are replacing
> > > PANA-Requth-*
> > > > > > > with
> > > > > > > > > > > > PANA-Ping-*, the WAIT_PRAA state would be replaced
> > > with
> > > > > > > WAIT_PPA.
> > > > > > > > > I
> > > > > > > > > > > > am afraid if we need additional transitions to the
> > > > > WAIT_PPA
> > > > > > > state
> > > > > > > > > from
> > > > > > > > > > > > several states, it would complicate the state
> machines
> > > and
> > > > > I
> > > > > > > am
> > > > > > > > > > > > wondering what is the benefit of adding such
> > > complexity.
> > > > > > > > > > > >
> > > > > > > > > > > > Yoshihiro Ohba
> > > > > > > > > > > >
> > > > > > > > > > > > On Thu, Aug 19, 2004 at 04:47:57PM -0700, Alper
> Yegin
> > > > > wrote:
> > > > > > > > > > > > > Yoshi,
> > > > > > > > > > > > >
> > > > > > > > > > > > > I never thought we would need to deal with
> PANA-ping
> > > in
> > > > > the
> > > > > > > > > state
> > > > > > > > > > > > > machine.
> > > > > > > > > > > > > I perceive it as a tool that can be used
> > > asynchronous to
> > > > > the
> > > > > > > > > state
> > > > > > > > > > > > > machine, and does not automatically impact the
> state
> > > > > > > machine.
> > > > > > > > > [Sure,
> > > > > > > > > > > > > PANA implementation can use PANA ping to
> discover
> > > > > dead-peer,
> > > > > > > > > just
> > > > > > > > > > > like
> > > > > > > > > > > > > it could use ICMP echos, or L2 indications]. If
> a
> > > state
> > > > > had
> > > > > > > > > > > explicitly
> > > > > > > > > > > > > called for using PANA-ping, then we must have
> > > > > incorporated
> > > > > > > it in
> > > > > > > > > the
> > > > > > > > > > > > > state machine.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Alper
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > From: Yoshihiro Ohba
> > > [mailto:yohba@tari.toshiba.com]
> > > > > > > > > > > > > > Sent: Sunday, September 19, 2004 4:37 PM
> > > > > > > > > > > > > > To: Alper Yegin
> > > > > > > > > > > > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > > > > > > > > > > > Subject: Re: [Pana] Issue 105: Inconsistent
> and
> > > > > unclear
> > > > > > > usage
> > > > > > > > > of
> > > > > > > > > > > > > "reauth"
> > > > > > > > > > > > > > messages
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Thu, Aug 19, 2004 at 12:45:18PM -0700,
> Alper
> > > Yegin
> > > > > > > wrote:
> > > > > > > > > > > > > > > > Should PANA-Ping-Request be allowed in
> > > discovery
> > > > > and
> > > > > > > > > initial
> > > > > > > > > > > > > handshake
> > > > > > > > > > > > > > > > phase?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Should PANA-Ping-Request be allowed in
> > > > > authentication
> > > > > > > > > phase?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > I thought about these. I decided to let the
> ping
> > > > > > > behavior
> > > > > > > > > handle
> > > > > > > > > > > > > this
> > > > > > > > > > > > > > > automatically. If there is an established
> pana
> > > > > session
> > > > > > > on
> > > > > > > > > the
> > > > > > > > > > > peer,
> > > > > > > > > > > > > it
> > > > > > > > > > > > > > > will respond. Otherwise, ping request will
> be
> > > > > silently
> > > > > > > > > > > discarded.
> > > > > > > > > > > > > This
> > > > > > > > > > > > > > > behavior can be followed in any state.
> [Also,
> > > PDI
> > > > > and
> > > > > > > > > PAR/PAN
> > > > > > > > > > > can be
> > > > > > > > > > > > > > > sent even when there is an established PANA
> > > session.
> > > > > > > Hence
> > > > > > > > > ping
> > > > > > > > > > > > > should
> > > > > > > > > > > > > > > work in that case.]
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > It is probablly easier to do that at the
> receiving
> > > > > side of
> > > > > > > the
> > > > > > > > > > > ping
> > > > > > > > > > > > > > request, but what about transmitting side?  If
> we
> > > > > allow a
> > > > > > > PAA
> > > > > > > > > or a
> > > > > > > > > > > PaC
> > > > > > > > > > > > > > to send a PANA-Ping-Request and receiving a
> > > > > > > PANA-Ping-Answer
> > > > > > > > > > > between
> > > > > > > > > > > > > > two consecutive PANA-Auth-Request/Answer
> exchanges
> > > in
> > > > > > > > > > > authentication
> > > > > > > > > > > > > > phase, it would complicate the state machines
> > > > > (probably
> > > > > > > one
> > > > > > > > > > > additional
> > > > > > > > > > > > > > state is needed to support this case in the
> PaC
> > > and
> > > > > PAA
> > > > > > > state
> > > > > > > > > > > > > > machines).  I have a similar observation for
> PANA
> > > > > pinging
> > > > > > > in
> > > > > > > > > > > discovery
> > > > > > > > > > > > > > and initial handshake phase.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > 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
> > > > >
> > >
> > >
> > > _______________________________________________
> > > 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 Aug 24 20:30: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 UAA27158
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 20:30: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 1BzlJ2-0000Hz-8M; Tue, 24 Aug 2004 20:06:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzkoB-0001oD-Mn
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 19:34:31 -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 TAA23643
	for <pana@ietf.org>; Tue, 24 Aug 2004 19:34:23 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bzkof-0003WZ-M7
	for pana@ietf.org; Tue, 24 Aug 2004 19:35:05 -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 <0I2Z00G015GE83@mailout3.samsung.com> for pana@ietf.org; Wed,
	25 Aug 2004 08:33:51 +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 <0I2Z009Z65GEE5@mailout3.samsung.com> for pana@ietf.org;
	Wed, 25 Aug 2004 08:33:50 +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 <0I2Z009P65GBXK@mmp1.samsung.com> for
	pana@ietf.org; Wed, 25 Aug 2004 08:33:50 +0900 (KST)
Date: Tue, 24 Aug 2004 16:33:45 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040824231059.GG1024@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <002501c48a32$ce12e840$0041fea9@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: a7d6aff76b15f3f56fcb94490e1052e4
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

> >
> > > >   PaC       PAA   seq.nos.
> > > > 1. <---------      x,y
> > > > 2. --------->      y+1,x
> > > > 3. ---+            y+2,x
> > > > 4.    |  +---      x+1,y+1
> > > >    <--|--+
> > > >       +----->
> >
> > Imagine 3 is a termination request (PTR), and 4 is an authentication
> > request (PAR). I'm trying to point out a problem with the current
design
> > (even without PANA-ping).
> 
> According to draft-ohba-pana-statemachine-00.txt:
> 
> - A PTR is allowed to be sent only in OPEN state.  

Yes, that's fine. PaC and PAA can be in OPEN state before message 3.
(imagine 4 is for EAP authentication before the current PANA session
lifetime expires).

> So the PaC is
> assumed to be in OPEN state before sending message 3 and in SESS_TERM
> state after sending message 3.  Message 4 (PAR) will be dropped by the
> PaC since PAR is not expected in SESS_TERM state.
> 
> - The PAA is assumed to be somehow in WAIT_PAN state after sending
> message 4 (PAR).  Message 3 (PTR) will be dropped by the PAA since PTR
> is not expected in WAIT_PAN state.

Even before these packets are dropped due to state mismatch as you
described, they'd be dropped due to sequence number checks. Whatever the
reason is, they should not cancel each other. If they do, depending on
the retransmission timers, they can keep doing this and finally tear
down the session. This is a bug.

Alper





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


From pana-bounces@ietf.org  Tue Aug 24 20:32: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 UAA27271
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 20:32: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 1BzlLc-0000o7-9z; Tue, 24 Aug 2004 20:09:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bzkx4-00044r-Ct
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 19:43:42 -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 TAA24267
	for <pana@ietf.org>; Tue, 24 Aug 2004 19:43:35 -0400 (EDT)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzkxZ-0003gx-Ar
	for pana@ietf.org; Tue, 24 Aug 2004 19:44:15 -0400
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id i7ONhV35011716; 
	Tue, 24 Aug 2004 16:43:32 -0700 (PDT)
Received: from localhost (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by bebop.France.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with SMTP id
	i7ONhTJR019435; Wed, 25 Aug 2004 01:43:30 +0200 (MEST)
Date: Tue, 24 Aug 2004 16:43:55 -0700 (PDT)
From: Erik Nordmark <Erik.Nordmark@sun.com>
Subject: RE: [Pana] Issue106: sequence number on rexmited messages must be
	incremented
To: Alper Yegin <alper.yegin@samsung.com>
In-Reply-To: "Your message with ID"
	<001101c48a24$c20a7ee0$0041fea9@sisa.samsung.com>
Message-ID: <Roam.SIMC.2.0.6.1093391035.31910.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: "'Erik Nordmark'" <Erik.Nordmark@sun.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Erik Nordmark <Erik.Nordmark@sun.com>
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

> Upper layer to PANA is EAP. 

No, there is PANA itself.
Perhaps all the PANA message semantics are idempotent, but that is far
from clear to me.

> Retransmission of EAP carrying messages are
> not handled by PANA. An EAP-carrying PANA message is retransmitted only
> when EAP retransmits the same EAP message. And in that case PANA may not
> even know it is a retransmission.

Yes, but that isn't a PANA retransmission. That is an EAP method performing
a retransmission.

> Since retransmission is not caused by PANA, duplicate prevention should
> not be provided by PANA either. 

There seems to be PANA retransmissions of non-EAP messages.
Don't those PANA messages also have sequence numbers?  
   Other PANA layer messages that require a response
   from the communicating peer are retransmitted based on timer at
   PANA-layer until a response is received (in which case the
   retransmission timer is stopped) or the number of retransmission
   reaches the maximum value (in which case the PANA session MUST be
   deleted immediately). 

  Erik



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


From pana-bounces@ietf.org  Tue Aug 24 21:06: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 VAA29425
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 21:06: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 1BzlgX-0004uI-SU; Tue, 24 Aug 2004 20:30:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzlLX-0000lw-5k
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 20:08:59 -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 UAA25836
	for <pana@ietf.org>; Tue, 24 Aug 2004 20:08:52 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzlM3-0004CU-Cz
	for pana@ietf.org; Tue, 24 Aug 2004 20:09: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 <0I2Z004ZW71SY8@mailout1.samsung.com> for pana@ietf.org; Wed,
	25 Aug 2004 09:08:16 +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 <0I2Z00B3K70O1V@mailout1.samsung.com> for pana@ietf.org;
	Wed, 25 Aug 2004 09:07:36 +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 <0I2Z005SW70MMV@mmp2.samsung.com> for
	pana@ietf.org; Wed, 25 Aug 2004 09:07:36 +0900 (KST)
Date: Tue, 24 Aug 2004 17:07:33 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue106: sequence number on rexmited messages must be
	incremented
In-reply-to: <Roam.SIMC.2.0.6.1093391035.31910.nordmark@bebop.france>
To: "'Erik Nordmark'" <Erik.Nordmark@sun.com>
Message-id: <003201c48a37$868e65d0$0041fea9@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 02ec665d00de228c50c93ed6b5e4fc1a
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


Yes, there are retransmissions of non-EAP messages, and they also have
sequence numbers. 

If we go back to your earlier comment:

	Retransmissions are needed in two cases:
	1. The message was lost
	2. The acknowledgement of the message was lost

	If a different sequence number is used for the retransmission
and #2 
	applies, then 2 copies of the message would be delivered to the
upper 
	layers since PANA would have no mechanism to tell that it has
already 
	received the message once.
 
If PaC receives a duplicate request, it must respond to it as it does
not know whether the peer received the earlier response or not. So I
think duplicate request should not be discarded, but processed.

Alper

 


> > Upper layer to PANA is EAP.
> 
> No, there is PANA itself.
> Perhaps all the PANA message semantics are idempotent, but that is far
> from clear to me.
> 
> > Retransmission of EAP carrying messages are
> > not handled by PANA. An EAP-carrying PANA message is retransmitted
only
> > when EAP retransmits the same EAP message. And in that case PANA may
not
> > even know it is a retransmission.
> 
> Yes, but that isn't a PANA retransmission. That is an EAP method
> performing
> a retransmission.
> 
> > Since retransmission is not caused by PANA, duplicate prevention
should
> > not be provided by PANA either.
> 
> There seems to be PANA retransmissions of non-EAP messages.
> Don't those PANA messages also have sequence numbers?
>    Other PANA layer messages that require a response
>    from the communicating peer are retransmitted based on timer at
>    PANA-layer until a response is received (in which case the
>    retransmission timer is stopped) or the number of retransmission
>    reaches the maximum value (in which case the PANA session MUST be
>    deleted immediately).
> 
>   Erik
> 



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


From pana-bounces@ietf.org  Tue Aug 24 21:35: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 VAA01597
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 21:35: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 1BzmFw-0002zU-Gu; Tue, 24 Aug 2004 21:07:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bzls0-0006j7-2E
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 20:42:32 -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 UAA27808
	for <pana@ietf.org>; Tue, 24 Aug 2004 20:42:30 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bzlsc-0004l7-Gt
	for pana@ietf.org; Tue, 24 Aug 2004 20:43:11 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7P0gObv012591;
	Wed, 25 Aug 2004 09:42:24 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7P0gOxX007968;
	Wed, 25 Aug 2004 09:42:24 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	KAA07966 ; Wed, 25 Aug 2004 09:42:24 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA29580; Wed, 25 Aug 2004 09:42:22 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7P0gMhS024855;
	Wed, 25 Aug 2004 09:42:22 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7P0gLwE001326;
	Wed, 25 Aug 2004 09:42: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 <0I2Z00DF48MI25@tsbpo1.po.toshiba.co.jp>; Wed,
	25 Aug 2004 09:42:20 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bzlrc-0003SU-00; Tue, 24 Aug 2004 17:42:08 -0700
Date: Tue, 24 Aug 2004 20:42:08 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <002501c48a32$ce12e840$0041fea9@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040825004208.GH1024@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+20040803i
References: <20040824231059.GG1024@steelhead>
	<002501c48a32$ce12e840$0041fea9@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
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, Aug 24, 2004 at 04:33:45PM -0700, Alper Yegin wrote:
> > >
> > > > >   PaC       PAA   seq.nos.
> > > > > 1. <---------      x,y
> > > > > 2. --------->      y+1,x
> > > > > 3. ---+            y+2,x
> > > > > 4.    |  +---      x+1,y+1
> > > > >    <--|--+
> > > > >       +----->
> > >
> > > Imagine 3 is a termination request (PTR), and 4 is an authentication
> > > request (PAR). I'm trying to point out a problem with the current
> design
> > > (even without PANA-ping).
> > 
> > According to draft-ohba-pana-statemachine-00.txt:
> > 
> > - A PTR is allowed to be sent only in OPEN state.  
> 
> Yes, that's fine. PaC and PAA can be in OPEN state before message 3.
> (imagine 4 is for EAP authentication before the current PANA session
> lifetime expires).
> 
> > So the PaC is
> > assumed to be in OPEN state before sending message 3 and in SESS_TERM
> > state after sending message 3.  Message 4 (PAR) will be dropped by the
> > PaC since PAR is not expected in SESS_TERM state.
> > 
> > - The PAA is assumed to be somehow in WAIT_PAN state after sending
> > message 4 (PAR).  Message 3 (PTR) will be dropped by the PAA since PTR
> > is not expected in WAIT_PAN state.
> 
> Even before these packets are dropped due to state mismatch as you
> described, they'd be dropped due to sequence number checks. 

As I commented in a previous mail, they are valid at least in terms of
sequence numbers.  But your point indicated below is still valid.

> Whatever the
> reason is, they should not cancel each other. If they do, depending on
> the retransmission timers, they can keep doing this and finally tear
> down the session. This is a bug.

It seems that this is a race condition between EAP re-authentication
initiated by one entity and session termination initiated by the other
entity.  I agree with you that this is a bug and should be resolved.
I think the latter (session termination initiated by the other entity)
should supersede the former (EAP re-authentication initiated by one
entity).

Yoshihiro Ohba

> 
> Alper
> 
> 
> 
> 

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


From pana-bounces@ietf.org  Tue Aug 24 22:09: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 WAA04333
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 22:09: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 1BzmtQ-0000jg-DJ; Tue, 24 Aug 2004 21:48:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzmVn-0005Eh-Dm
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 21:24: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 VAA00724
	for <pana@ietf.org>; Tue, 24 Aug 2004 21:23:32 -0400 (EDT)
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BzmWJ-0005e7-Fd
	for pana@ietf.org; Tue, 24 Aug 2004 21:24:13 -0400
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id i7P1NT35014015; 
	Tue, 24 Aug 2004 18:23:30 -0700 (PDT)
Received: from localhost (d-mpk17-89-243.SFBay.Sun.COM [129.146.89.243])
	by bebop.France.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with SMTP id
	i7P1NRJR024463; Wed, 25 Aug 2004 03:23:28 +0200 (MEST)
Date: Tue, 24 Aug 2004 17:20:56 -0700 (PDT)
From: Erik Nordmark <Erik.Nordmark@sun.com>
Subject: RE: [Pana] Issue106: sequence number on rexmited messages must be
	incremented
To: Alper Yegin <alper.yegin@samsung.com>
In-Reply-To: "Your message with ID"
	<003201c48a37$868e65d0$0041fea9@sisa.samsung.com>
Message-ID: <Roam.SIMC.2.0.6.1093393256.16150.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: "'Erik Nordmark'" <Erik.Nordmark@sun.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Erik Nordmark <Erik.Nordmark@sun.com>
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

> If PaC receives a duplicate request, it must respond to it as it does
> not know whether the peer received the earlier response or not. So I
> think duplicate request should not be discarded, but processed.

Yes, but wouldn't it send the same response as it did the first time?

Using a new sequence number makes that quite hard, since it
can't easily tell whether the two requests were the same.

If there are PANA protocol operations that are not idempotent,
i.e. where processing the request twice results in something
different than processing it once, then it is requires that
the PANA reliability sub-layer retain the responses so that they can
be used when receiving a retransmitted request.

BTW: The use of "MAY" in section 4.11 implies that PANA isn't specified
to be robust to packet loss; for the protocol to be robust, duplicate
requests need to result in retransmitted responses.

   Erik


 


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


From pana-bounces@ietf.org  Tue Aug 24 22:32:45 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 WAA05550
	for <pana-archive@lists.ietf.org>; Tue, 24 Aug 2004 22:32: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 1BznA3-0003ni-Jc; Tue, 24 Aug 2004 22:05:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzmrR-0000Ti-9d
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 21:46: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 VAA02183
	for <pana@ietf.org>; Tue, 24 Aug 2004 21:45:53 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24] helo=mailout1)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bzmry-00065w-AN
	for pana@ietf.org; Tue, 24 Aug 2004 21:46:35 -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 <0I2Z00HI4AEFDK@mailout1.samsung.com> for pana@ietf.org; Wed,
	25 Aug 2004 10:20:39 +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 <0I2Z00BTDACIC5@mailout1.samsung.com> for pana@ietf.org;
	Wed, 25 Aug 2004 10:19:30 +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 <0I2Z00D36ACFAE@mmp1.samsung.com> for
	pana@ietf.org; Wed, 25 Aug 2004 10:19:30 +0900 (KST)
Date: Tue, 24 Aug 2004 18:19:27 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040825004208.GH1024@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <004101c48a41$91a7ff30$0041fea9@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 8abaac9e10c826e8252866cbe6766464
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

 
> It seems that this is a race condition between EAP re-authentication
> initiated by one entity and session termination initiated by the other
> entity.  I agree with you that this is a bug and should be resolved.
> I think the latter (session termination initiated by the other entity)
> should supersede the former (EAP re-authentication initiated by one
> entity).

I'm not sure what you mean by "supersede", or how it solves the problem.

This is the same non-lock-step issue with PANA-ping. If only one side
(PAA) generates the requests, there is no problem. If both sides can
asynchronously generate requests, the current sequence number checking
scheme fails (prevents asynchronous transmission, dropping valid
packets).

If we go back to the original intent of sequence numbering, it is for
orderly delivery of EAP messages. If all messages were EAP-driven, that
would be fine because all requests are generated by the PAA. But that's
not the case.

One solution could be to enforce orderly delivery only among
EAP-carrying messages, and let the other (PANA management) messages not
have to fit that scheme. What would be the impact on the design? [and of
course, are there any other solutions?]

Alper






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


From pana-bounces@ietf.org  Wed Aug 25 00:36:45 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 AAA13307
	for <pana-archive@lists.ietf.org>; Wed, 25 Aug 2004 00:36: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 1Bzp9z-0004D9-Hj; Wed, 25 Aug 2004 00:13:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1BzosQ-00016r-Gt
	for pana@megatron.ietf.org; Tue, 24 Aug 2004 23:55: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 XAA09963
	for <pana@ietf.org>; Tue, 24 Aug 2004 23:55:02 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bzosy-0008NK-GZ
	for pana@ietf.org; Tue, 24 Aug 2004 23:55:46 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7P3t0bv010988;
	Wed, 25 Aug 2004 12:55:00 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7P3t045006732;
	Wed, 25 Aug 2004 12:55:00 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	NAA06729 ; Wed, 25 Aug 2004 12:55:00 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id MAA21061; Wed, 25 Aug 2004 12:54:59 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7P3swH3005257;
	Wed, 25 Aug 2004 12:54:58 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7P3swwE008275;
	Wed, 25 Aug 2004 12:54:58 +0900 (JST)
Received: from steelhead (iVPN01-220.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 <0I2Z00K7AHJK5F@tsbpo1.po.toshiba.co.jp>; Wed,
	25 Aug 2004 12:54:57 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1Bzor9-0003go-00; Tue, 24 Aug 2004 20:53:51 -0700
Date: Tue, 24 Aug 2004 23:53:51 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <004101c48a41$91a7ff30$0041fea9@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040825035351.GJ1024@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+20040803i
References: <20040825004208.GH1024@steelhead>
	<004101c48a41$91a7ff30$0041fea9@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
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, Aug 24, 2004 at 06:19:27PM -0700, Alper Yegin wrote:
>  
> > It seems that this is a race condition between EAP re-authentication
> > initiated by one entity and session termination initiated by the other
> > entity.  I agree with you that this is a bug and should be resolved.
> > I think the latter (session termination initiated by the other entity)
> > should supersede the former (EAP re-authentication initiated by one
> > entity).
> 
> I'm not sure what you mean by "supersede", or how it solves the problem.

I mean that if an entity that has sent a message that initiates EAP
re-authentication (i.e., a PSA sent by a PAA in OPEN state or a PDI
sent by a PaC in OPEN state) receives a PTR, then it SHOULD respond
with a PTA and delete the session.

> 
> This is the same non-lock-step issue with PANA-ping. If only one side
> (PAA) generates the requests, there is no problem. If both sides can
> asynchronously generate requests, the current sequence number checking
> scheme fails (prevents asynchronous transmission, dropping valid
> packets).

By re-reading my analysis, I realized that the meaning of
"non-lock-step" was ambiguous.  "non-lock-step" meant that one side
can generate multiple outstanding requests.  For both lock-step and
non-lock-step models both sides can asynchronously generate requests.
So the above race condition is different from the non-lock-step issue
with PANA-ping.

> 
> If we go back to the original intent of sequence numbering, it is for
> orderly delivery of EAP messages. If all messages were EAP-driven, that
> would be fine because all requests are generated by the PAA. But that's
> not the case.
> 
> One solution could be to enforce orderly delivery only among
> EAP-carrying messages, and let the other (PANA management) messages not
> have to fit that scheme. What would be the impact on the design? [and of
> course, are there any other solutions?]

I am not sure what solution you mean by "let the other (PANA
management) messages not have to fit that scheme".

Yoshihiro Ohba


	
> 
> Alper
> 
> 
> 
> 
> 

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


From pana-bounces@ietf.org  Wed Aug 25 11:15: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 LAA22671
	for <pana-archive@lists.ietf.org>; Wed, 25 Aug 2004 11:15: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 1BzzFz-0007NB-Cf; Wed, 25 Aug 2004 11:00:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Bzz3D-0005Mw-TD
	for pana@megatron.ietf.org; Wed, 25 Aug 2004 10:46:59 -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 KAA20458
	for <pana@ietf.org>; Wed, 25 Aug 2004 10:46:52 -0400 (EDT)
Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bzz3r-0003HG-7u
	for pana@ietf.org; Wed, 25 Aug 2004 10:47:41 -0400
Received: from smtp.um.es (localhost [127.0.0.1])
	by localhost (Postfix) with ESMTP id 0C10517912
	for <pana@ietf.org>; Wed, 25 Aug 2004 16:46:17 +0200 (CEST)
Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253])
	by smtp.um.es (Postfix) with ESMTP id B3E79B05F
	for <pana@ietf.org>; Wed, 25 Aug 2004 16:46:01 +0200 (CEST)
Received: from dif.um.es (bravecard.dif.um.es [155.54.210.47])
	by aries.dif.um.es (Postfix) with ESMTP id 780CC14431
	for <pana@ietf.org>; Wed, 25 Aug 2004 16:43:17 +0200 (MET DST)
Message-ID: <412CA634.4030805@dif.um.es>
Date: Wed, 25 Aug 2004 16:46:12 +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: pana@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Subject: [Pana] PANA framework: Configure EPs after PUR-PUA exchange.
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 all.

In PANA framework I have seen this possible error. In figure 15 
(Appendix A.1) where IPSec-TIA is obtained by using RFC 3118:

Initially PAA configures EP(AR) by using PaC-DI value. However after 
authenticated RFC 3118 phase , PaC-DI changes : in fact, there is a 
PUR-PUA exchange using POPA as PaC-DI. This PaC-DI is not the same than 
PaC-DI configured in the EP(AR) previously. I think the EP(AR) 
configuration should be done after this exchange (PUR-PUA). PAA can know 
when, becuase it knows configuration method is RFC 3118.

comments?

Regards.

------------------------------------------------------
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  Wed Aug 25 13:05: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 NAA01022
	for <pana-archive@lists.ietf.org>; Wed, 25 Aug 2004 13:05: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 1C00lW-00054h-2X; Wed, 25 Aug 2004 12:36:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C00Sd-0001EW-3i
	for pana@megatron.ietf.org; Wed, 25 Aug 2004 12:17:19 -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 MAA27714
	for <pana@ietf.org>; Wed, 25 Aug 2004 12:17:11 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C00TH-00051C-Ud
	for pana@ietf.org; Wed, 25 Aug 2004 12:18:01 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7PGGfbv000698;
	Thu, 26 Aug 2004 01:16:41 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7PGGfsL023115;
	Thu, 26 Aug 2004 01:16:41 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	BAA23114 ; Thu, 26 Aug 2004 01:16:41 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA15347; Thu, 26 Aug 2004 01:16:41 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7PGGeSX012485;
	Thu, 26 Aug 2004 01:16:40 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7PGGewE008130;
	Thu, 26 Aug 2004 01:16:40 +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 <0I3000HEEFVPP9@tsbpo1.po.toshiba.co.jp>; Thu,
	26 Aug 2004 01:16:39 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C00Ql-0005Ea-00; Wed, 25 Aug 2004 09:15:23 -0700
Date: Wed, 25 Aug 2004 12:15:23 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] PANA framework: Configure EPs after PUR-PUA exchange.
In-reply-to: <412CA634.4030805@dif.um.es>
To: Rafael Marin Lopez <rafa@dif.um.es>
Message-id: <20040825161522.GK1024@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>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040803i
References: <412CA634.4030805@dif.um.es>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
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 Rafa,

Thank you for pointing this out.  You are right that EP(AR)
configuration should be done after updating the device identifier of
the PaC.

BTW, since PUR-PUA exchange is not be used for DI update any more
(instead mobility handling procedure can be used for updating DI), the
PUR-PUA exchange in Figure 15 should be replaced with "DI update
procedure by using PANA mobility handling".

Yoshihiro Ohba


On Wed, Aug 25, 2004 at 04:46:12PM +0200, Rafael Marin Lopez wrote:
> Hi all.
> 
> In PANA framework I have seen this possible error. In figure 15 
> (Appendix A.1) where IPSec-TIA is obtained by using RFC 3118:
> 
> Initially PAA configures EP(AR) by using PaC-DI value. However after 
> authenticated RFC 3118 phase , PaC-DI changes : in fact, there is a 
> PUR-PUA exchange using POPA as PaC-DI. This PaC-DI is not the same than 
> PaC-DI configured in the EP(AR) previously. I think the EP(AR) 
> configuration should be done after this exchange (PUR-PUA). PAA can know 
> when, becuase it knows configuration method is RFC 3118.
> 
> comments?
> 
> Regards.
> 
> ------------------------------------------------------
> 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  Wed Aug 25 19:19: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 TAA06360
	for <pana-archive@lists.ietf.org>; Wed, 25 Aug 2004 19:19: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 1C06jT-0007r6-FS; Wed, 25 Aug 2004 18:59:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C06Qo-0002GO-AL
	for pana@megatron.ietf.org; Wed, 25 Aug 2004 18:39: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 SAA03730
	for <pana@ietf.org>; Wed, 25 Aug 2004 18:39:42 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C06RX-0006N6-FA
	for pana@ietf.org; Wed, 25 Aug 2004 18:40: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 <0I3000401XL1SF@mailout3.samsung.com> for pana@ietf.org; Thu,
	26 Aug 2004 07:39:01 +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 <0I300092MXL0GB@mailout3.samsung.com> for pana@ietf.org;
	Thu, 26 Aug 2004 07:39:00 +0900 (KST)
Received: from Alperyegin ([105.253.155.33])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I30003X8XKXXU@mmp1.samsung.com> for
	pana@ietf.org; Thu, 26 Aug 2004 07:39:00 +0900 (KST)
Date: Wed, 25 Aug 2004 15:38:54 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040825035351.GJ1024@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <003e01c48af4$4e99c490$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 37af5f8fbf6f013c5b771388e24b09e7
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,

I think I'm understanding some of the issues.

1- I raised an issue with the sequencing, and gave an example how it
creates a problem when PaC and PAA can asynchronously send requests to
each other. I was wrong. There is no problem with the sequence numbers,
the packets are not really discarded due to them. [I think you've been
trying to tell me they were OK.]

2- You raised an issue with a peer having multiple outstanding requests
(for allowing PANA-ping-requests when there is already an outstanding
request). I agree that complicates the sequencing. 

Besides a peer might not need to send a PANA-ping if there is already an
outstanding request. Because a response to that is as good as pinging
the other peer. 

So I agree that we don't have to accommodate for transmission of a
PANA-ping-request when there is a pending request.

3- But, how about allowing the "reception" of a PANA-ping-request when
the peer has an outstanding request? I think that should be fine. The
receiver should simply respond to it, and that does not impact the state
machine imo (no state change for simply responding to a ping request).

4- PANA-termination-request (PTR) should be accepted in most (all?)
states,
even if the receiver has a pending request. We may have to limit its use
to only after the first successful PANA-Bind. Otherwise, it may be used
for DoS on the PaC that is trying to get authenticated for the first
time.

What do you think?

Alper 


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Tuesday, August 24, 2004 8:54 PM
> To: Alper Yegin
> Cc: 'Yoshihiro Ohba'; pana@ietf.org
> Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
"reauth"
> messages
> 
> On Tue, Aug 24, 2004 at 06:19:27PM -0700, Alper Yegin wrote:
> >
> > > It seems that this is a race condition between EAP
re-authentication
> > > initiated by one entity and session termination initiated by the
other
> > > entity.  I agree with you that this is a bug and should be
resolved.
> > > I think the latter (session termination initiated by the other
entity)
> > > should supersede the former (EAP re-authentication initiated by
one
> > > entity).
> >
> > I'm not sure what you mean by "supersede", or how it solves the
problem.
> 
> I mean that if an entity that has sent a message that initiates EAP
> re-authentication (i.e., a PSA sent by a PAA in OPEN state or a PDI
> sent by a PaC in OPEN state) receives a PTR, then it SHOULD respond
> with a PTA and delete the session.
> 
> >
> > This is the same non-lock-step issue with PANA-ping. If only one
side
> > (PAA) generates the requests, there is no problem. If both sides can
> > asynchronously generate requests, the current sequence number
checking
> > scheme fails (prevents asynchronous transmission, dropping valid
> > packets).
> 
> By re-reading my analysis, I realized that the meaning of
> "non-lock-step" was ambiguous.  "non-lock-step" meant that one side
> can generate multiple outstanding requests.  For both lock-step and
> non-lock-step models both sides can asynchronously generate requests.
> So the above race condition is different from the non-lock-step issue
> with PANA-ping.
> 
> >
> > If we go back to the original intent of sequence numbering, it is
for
> > orderly delivery of EAP messages. If all messages were EAP-driven,
that
> > would be fine because all requests are generated by the PAA. But
that's
> > not the case.
> >
> > One solution could be to enforce orderly delivery only among
> > EAP-carrying messages, and let the other (PANA management) messages
not
> > have to fit that scheme. What would be the impact on the design?
[and of
> > course, are there any other solutions?]
> 
> I am not sure what solution you mean by "let the other (PANA
> management) messages not have to fit that scheme".
> 
> Yoshihiro Ohba
> 
> 
> 
> >
> > Alper
> >
> >
> >
> >
> >


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


From pana-bounces@ietf.org  Wed Aug 25 19:41:45 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 TAA07597
	for <pana-archive@lists.ietf.org>; Wed, 25 Aug 2004 19:41:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C079L-0006rW-Qh; Wed, 25 Aug 2004 19:25:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C06t5-0002Gk-9h
	for pana@megatron.ietf.org; Wed, 25 Aug 2004 19:09:03 -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 TAA05766
	for <pana@ietf.org>; Wed, 25 Aug 2004 19:08:55 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C06tn-0006wt-Q8
	for pana@ietf.org; Wed, 25 Aug 2004 19:09:49 -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 <0I300050QYY071@mailout2.samsung.com> for pana@ietf.org; Thu,
	26 Aug 2004 08:08:24 +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 <0I300029VYXUY1@mailout2.samsung.com> for pana@ietf.org;
	Thu, 26 Aug 2004 08:08:19 +0900 (KST)
Received: from Alperyegin ([105.253.155.33])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I3000CB3YXRIR@mmp2.samsung.com> for
	pana@ietf.org; Thu, 26 Aug 2004 08:08:18 +0900 (KST)
Date: Wed, 25 Aug 2004 16:08:12 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue106: sequence number on rexmited messages must be
	incremented
In-reply-to: <Roam.SIMC.2.0.6.1093393256.16150.nordmark@bebop.france>
To: "'Erik Nordmark'" <Erik.Nordmark@sun.com>
Message-id: <00d801c48af8$6689dcd0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 769a46790fb42fbb0b0cc700c82f7081
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

> > If PaC receives a duplicate request, it must respond to it as it
does
> > not know whether the peer received the earlier response or not. So I
> > think duplicate request should not be discarded, but processed.
> 
> Yes, but wouldn't it send the same response as it did the first time?

Yes, it would.

> Using a new sequence number makes that quite hard, since it
> can't easily tell whether the two requests were the same.
> 
> If there are PANA protocol operations that are not idempotent,
> i.e. where processing the request twice results in something
> different than processing it once, then it is requires that
> the PANA reliability sub-layer retain the responses so that they can
> be used when receiving a retransmitted request.

So, if I'm understanding you right: This sub-layer is supposed to retain
a copy of the last transmitted message. If this is a request message, it
is retransmitted when retransmission timer goes off. If it is an answer
message, it is retransmitted when a duplicate request is received.
Preserving the same sequence number across retransmissions make the
latter easier (at least contain it in this sub-layer, other parts of
PANA process does not have to process the message). It makes sense to
me.


> 
> BTW: The use of "MAY" in section 4.11 implies that PANA isn't
specified
> to be robust to packet loss; for the protocol to be robust, duplicate
> requests need to result in retransmitted responses.

We shall fix that (btw, Section 4.7 and 4.11 are duplicates (an editing
bug), and 4.7 is more up-to-date... but nevertheless it needs that fix.)

Alper



> 
>    Erik
> 
> 
> 



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


From pana-bounces@ietf.org  Wed Aug 25 20: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 UAA08583
	for <pana-archive@lists.ietf.org>; Wed, 25 Aug 2004 20: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 1C07QB-0002wz-43; Wed, 25 Aug 2004 19:43:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C07An-0007H1-Ay
	for pana@megatron.ietf.org; Wed, 25 Aug 2004 19:27:21 -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 TAA06850
	for <pana@ietf.org>; Wed, 25 Aug 2004 19:27:13 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C07BU-0007Es-1L
	for pana@ietf.org; Wed, 25 Aug 2004 19:28:07 -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 <0I300085VZSG3G@mailout2.samsung.com> for pana@ietf.org; Thu,
	26 Aug 2004 08:26:40 +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 <0I30006ESZS91P@mailout2.samsung.com> for pana@ietf.org;
	Thu, 26 Aug 2004 08:26:33 +0900 (KST)
Received: from Alperyegin ([105.253.155.33])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I3000454ZS5RO@mmp2.samsung.com> for
	pana@ietf.org; Thu, 26 Aug 2004 08:26:33 +0900 (KST)
Date: Wed, 25 Aug 2004 16:26:26 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: issue 111 (was RE: [Pana] same name space...)
In-reply-to: <20040729035855.GB20224@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <00dd01c48afa$f2afc880$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 8de5f93cb2b4e3bee75302e9eacc33db
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


Issue 111 can be fixed by:


[1] Section 6.5:

> - 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."

[2] Section 6.5:

> - Renumber PANA AVP codes starting from 1.

[3] Section 6.4.1:

Remove

	Note that PANA messages have a different header format compared
to 
	Diameter.

That statement could be confusing, because nobody expects otherwise
anyways....

Alper












> 
> 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 Aug 26 10:40: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 KAA06052
	for <pana-archive@lists.ietf.org>; Thu, 26 Aug 2004 10:40: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 1C0L6S-0001i2-Tp; Thu, 26 Aug 2004 10:19:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0L27-0007o1-JQ
	for pana@megatron.ietf.org; Thu, 26 Aug 2004 10:15:19 -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 KAA02650
	for <pana@ietf.org>; Thu, 26 Aug 2004 10:15:14 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0L2q-0004nC-Tc
	for pana@ietf.org; Thu, 26 Aug 2004 10:16:15 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7QEExbv006848;
	Thu, 26 Aug 2004 23:14:59 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7QEExY8001410;
	Thu, 26 Aug 2004 23:14:59 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	ZAA01403 ; Thu, 26 Aug 2004 23:14:59 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id XAA18286; Thu, 26 Aug 2004 23:14:58 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7QEEw2W019771;
	Thu, 26 Aug 2004 23:14:58 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7QEEvwE000803;
	Thu, 26 Aug 2004 23:14:57 +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 <0I3200LYF4WUVM@tsbpo1.po.toshiba.co.jp>; Thu,
	26 Aug 2004 23:14:57 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C0L1b-0007i2-00; Thu, 26 Aug 2004 07:14:47 -0700
Date: Thu, 26 Aug 2004 10:14:46 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <003e01c48af4$4e99c490$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040826141446.GP1024@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+20040803i
References: <20040825035351.GJ1024@steelhead>
	<003e01c48af4$4e99c490$6401a8c0@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0
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

Alper,

On Wed, Aug 25, 2004 at 03:38:54PM -0700, Alper Yegin wrote:
> Yoshi,
> 
> I think I'm understanding some of the issues.
> 
> 1- I raised an issue with the sequencing, and gave an example how it
> creates a problem when PaC and PAA can asynchronously send requests to
> each other. I was wrong. There is no problem with the sequence numbers,
> the packets are not really discarded due to them. [I think you've been
> trying to tell me they were OK.]

OK.

> 
> 2- You raised an issue with a peer having multiple outstanding requests
> (for allowing PANA-ping-requests when there is already an outstanding
> request). I agree that complicates the sequencing. 

OK.

> 
> Besides a peer might not need to send a PANA-ping if there is already an
> outstanding request. Because a response to that is as good as pinging
> the other peer. 
> 
> So I agree that we don't have to accommodate for transmission of a
> PANA-ping-request when there is a pending request.
> 
> 3- But, how about allowing the "reception" of a PANA-ping-request when
> the peer has an outstanding request? I think that should be fine. The
> receiver should simply respond to it, and that does not impact the state
> machine imo (no state change for simply responding to a ping request).

Under the current sequence number scheme it is fine.  However, if we
consider using the same sequence number for retransmitted messages as
we are going to agree as a resolution for Issue 106, I think there is
a problem with allowing the reception of a PPR when the peer has an
outstanding request.  Please see the following example in which the
same sequence number for retransmitted messages:

Suppose that a PAA that has an outstanding PANA-Auth-Request with
tseq=x receives a PANA-Ping-Request from a PaC and returns a
PANA-Ping-Answer giving tseq=x+1 and the PaC receives the answer.
Then the retransmission timer expires and the PAA retransmit the
outstanding PAR with tseq=x.  The PaC will drop the retransmitted PAR
because the received tseq(=x) is less than the last accepted
tseq(=x+1).

This problem is due to sharing the same sequence number space among
requests and answers sent by one side.  It is probably better and
simpler to allocate one sequence number space to requests from PaC and
the other sequence number space to requests from PAA, and make answers
carry the sequence numbers of the corresponding requests, like the
sequence number scheme taken by IKEv2.  By doing this, we do not need
to carry two sequence numbers in each message any more, but there are
still two sequence number spaces as the current PANA sequcen number
scheme.

> 
> 4- PANA-termination-request (PTR) should be accepted in most (all?)
> states,
> even if the receiver has a pending request. We may have to limit its use
> to only after the first successful PANA-Bind. Otherwise, it may be used
> for DoS on the PaC that is trying to get authenticated for the first
> time.

For the receiving side of a PTR, it is OK.  But if the sender can send
PTR at any state, then we would still encounter issue 2 above.  The
same thing for sending PANA-Ping-Request at any state.  I still don't
know an easy way when we design state machines to allow sending a PTR
or a PPR at any state without conflicting with other requests sent by
the same node.  I still prefer allowing a PTR or a PPR to be sent in
OPEN state only.

Yoshihiro Ohba

> 
> What do you think?
> 
> Alper 
> 
> 
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Tuesday, August 24, 2004 8:54 PM
> > To: Alper Yegin
> > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
> "reauth"
> > messages
> > 
> > On Tue, Aug 24, 2004 at 06:19:27PM -0700, Alper Yegin wrote:
> > >
> > > > It seems that this is a race condition between EAP
> re-authentication
> > > > initiated by one entity and session termination initiated by the
> other
> > > > entity.  I agree with you that this is a bug and should be
> resolved.
> > > > I think the latter (session termination initiated by the other
> entity)
> > > > should supersede the former (EAP re-authentication initiated by
> one
> > > > entity).
> > >
> > > I'm not sure what you mean by "supersede", or how it solves the
> problem.
> > 
> > I mean that if an entity that has sent a message that initiates EAP
> > re-authentication (i.e., a PSA sent by a PAA in OPEN state or a PDI
> > sent by a PaC in OPEN state) receives a PTR, then it SHOULD respond
> > with a PTA and delete the session.
> > 
> > >
> > > This is the same non-lock-step issue with PANA-ping. If only one
> side
> > > (PAA) generates the requests, there is no problem. If both sides can
> > > asynchronously generate requests, the current sequence number
> checking
> > > scheme fails (prevents asynchronous transmission, dropping valid
> > > packets).
> > 
> > By re-reading my analysis, I realized that the meaning of
> > "non-lock-step" was ambiguous.  "non-lock-step" meant that one side
> > can generate multiple outstanding requests.  For both lock-step and
> > non-lock-step models both sides can asynchronously generate requests.
> > So the above race condition is different from the non-lock-step issue
> > with PANA-ping.
> > 
> > >
> > > If we go back to the original intent of sequence numbering, it is
> for
> > > orderly delivery of EAP messages. If all messages were EAP-driven,
> that
> > > would be fine because all requests are generated by the PAA. But
> that's
> > > not the case.
> > >
> > > One solution could be to enforce orderly delivery only among
> > > EAP-carrying messages, and let the other (PANA management) messages
> not
> > > have to fit that scheme. What would be the impact on the design?
> [and of
> > > course, are there any other solutions?]
> > 
> > I am not sure what solution you mean by "let the other (PANA
> > management) messages not have to fit that scheme".
> > 
> > Yoshihiro Ohba
> > 
> > 
> > 
> > >
> > > Alper
> > >
> > >
> > >
> > >
> > >
> 

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


From pana-bounces@ietf.org  Thu Aug 26 22:42: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 WAA04932
	for <pana-archive@lists.ietf.org>; Thu, 26 Aug 2004 22:42: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 1C0Wg1-0004Yz-8f; Thu, 26 Aug 2004 22:41:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0WeT-0004HJ-K9
	for pana@megatron.ietf.org; Thu, 26 Aug 2004 22:39: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 WAA04720
	for <pana@ietf.org>; Thu, 26 Aug 2004 22:39:39 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0WfV-0005md-9q
	for pana@ietf.org; Thu, 26 Aug 2004 22:40:47 -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 <0I3300G013D11M@mailout2.samsung.com> for pana@ietf.org; Fri,
	27 Aug 2004 11:39:01 +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 <0I3300AM13D0K1@mailout2.samsung.com> for pana@ietf.org;
	Fri, 27 Aug 2004 11:39:01 +0900 (KST)
Received: from Alperyegin ([105.253.155.49])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I330060N3CXNX@mmp1.samsung.com> for
	pana@ietf.org; Fri, 27 Aug 2004 11:39:00 +0900 (KST)
Date: Thu, 26 Aug 2004 19:38:54 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040826141446.GP1024@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <01da01c48bdf$00aca9a0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: e472ca43d56132790a46d9eefd95f0a5
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

> > 3- But, how about allowing the "reception" of a PANA-ping-request
when
> > the peer has an outstanding request? I think that should be fine.
The
> > receiver should simply respond to it, and that does not impact the
state
> > machine imo (no state change for simply responding to a ping
request).
> 
> Under the current sequence number scheme it is fine.  However, if we
> consider using the same sequence number for retransmitted messages as
> we are going to agree as a resolution for Issue 106, I think there is
> a problem with allowing the reception of a PPR when the peer has an
> outstanding request.  Please see the following example in which the
> same sequence number for retransmitted messages:
> 
> Suppose that a PAA that has an outstanding PANA-Auth-Request with
> tseq=x receives a PANA-Ping-Request from a PaC and returns a
> PANA-Ping-Answer giving tseq=x+1 and the PaC receives the answer.
> Then the retransmission timer expires and the PAA retransmit the
> outstanding PAR with tseq=x.  The PaC will drop the retransmitted PAR
> because the received tseq(=x) is less than the last accepted
> tseq(=x+1).

Good observation.

> This problem is due to sharing the same sequence number space among
> requests and answers sent by one side.  It is probably better and
> simpler to allocate one sequence number space to requests from PaC and
> the other sequence number space to requests from PAA, and make answers
> carry the sequence numbers of the corresponding requests, like the
> sequence number scheme taken by IKEv2.  By doing this, we do not need
> to carry two sequence numbers in each message any more, but there are
> still two sequence number spaces as the current PANA sequcen number
> scheme.

Susan Thomson has a proposal on that. I'll relay her proposal soon (I'm
waiting for her permission to forward her e-mail to the list).

> > 4- PANA-termination-request (PTR) should be accepted in most (all?)
> > states,
> > even if the receiver has a pending request. We may have to limit its
use
> > to only after the first successful PANA-Bind. Otherwise, it may be
used
> > for DoS on the PaC that is trying to get authenticated for the first
> > time.
> 
> For the receiving side of a PTR, it is OK.  But if the sender can send
> PTR at any state, then we would still encounter issue 2 above.  The
> same thing for sending PANA-Ping-Request at any state.  

I agree. My comment is about accepting a request on the receiving peer,
not transmitting the request. 

> I still don't
> know an easy way when we design state machines to allow sending a PTR
> or a PPR at any state without conflicting with other requests sent by
> the same node.  I still prefer allowing a PTR or a PPR to be sent in
> OPEN state only.

I think that's fine.

Alper



> 
> Yoshihiro Ohba
> 
> >
> > What do you think?
> >
> > Alper
> >
> >
> > > -----Original Message-----
> > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: Tuesday, August 24, 2004 8:54 PM
> > > To: Alper Yegin
> > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of
> > "reauth"
> > > messages
> > >
> > > On Tue, Aug 24, 2004 at 06:19:27PM -0700, Alper Yegin wrote:
> > > >
> > > > > It seems that this is a race condition between EAP
> > re-authentication
> > > > > initiated by one entity and session termination initiated by
the
> > other
> > > > > entity.  I agree with you that this is a bug and should be
> > resolved.
> > > > > I think the latter (session termination initiated by the other
> > entity)
> > > > > should supersede the former (EAP re-authentication initiated
by
> > one
> > > > > entity).
> > > >
> > > > I'm not sure what you mean by "supersede", or how it solves the
> > problem.
> > >
> > > I mean that if an entity that has sent a message that initiates
EAP
> > > re-authentication (i.e., a PSA sent by a PAA in OPEN state or a
PDI
> > > sent by a PaC in OPEN state) receives a PTR, then it SHOULD
respond
> > > with a PTA and delete the session.
> > >
> > > >
> > > > This is the same non-lock-step issue with PANA-ping. If only one
> > side
> > > > (PAA) generates the requests, there is no problem. If both sides
can
> > > > asynchronously generate requests, the current sequence number
> > checking
> > > > scheme fails (prevents asynchronous transmission, dropping valid
> > > > packets).
> > >
> > > By re-reading my analysis, I realized that the meaning of
> > > "non-lock-step" was ambiguous.  "non-lock-step" meant that one
side
> > > can generate multiple outstanding requests.  For both lock-step
and
> > > non-lock-step models both sides can asynchronously generate
requests.
> > > So the above race condition is different from the non-lock-step
issue
> > > with PANA-ping.
> > >
> > > >
> > > > If we go back to the original intent of sequence numbering, it
is
> > for
> > > > orderly delivery of EAP messages. If all messages were
EAP-driven,
> > that
> > > > would be fine because all requests are generated by the PAA. But
> > that's
> > > > not the case.
> > > >
> > > > One solution could be to enforce orderly delivery only among
> > > > EAP-carrying messages, and let the other (PANA management)
messages
> > not
> > > > have to fit that scheme. What would be the impact on the design?
> > [and of
> > > > course, are there any other solutions?]
> > >
> > > I am not sure what solution you mean by "let the other (PANA
> > > management) messages not have to fit that scheme".
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > >
> > > >
> > > > Alper
> > > >
> > > >
> > > >
> > > >
> > > >
> >


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


From pana-bounces@ietf.org  Fri Aug 27 10:18: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 KAA02160
	for <pana-archive@lists.ietf.org>; Fri, 27 Aug 2004 10:18: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 1C0hTm-000574-ME; Fri, 27 Aug 2004 10:13:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0hSc-0004Wi-Sv
	for pana@megatron.ietf.org; Fri, 27 Aug 2004 10:12:11 -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 KAA01336
	for <pana@ietf.org>; Fri, 27 Aug 2004 10:12:08 -0400 (EDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0hTl-00021U-GX
	for pana@ietf.org; Fri, 27 Aug 2004 10:13:22 -0400
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id i7REC753006768; 
	Fri, 27 Aug 2004 08:12:07 -0600 (MDT)
Received: from localhost (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by bebop.France.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with SMTP id
	i7REC4JR018542; Fri, 27 Aug 2004 16:12:05 +0200 (MEST)
Date: Thu, 26 Aug 2004 09:23:37 -0700 (PDT)
From: Erik Nordmark <Erik.Nordmark@sun.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
In-Reply-To: "Your message with ID" <20040826141446.GP1024@steelhead>
Message-ID: <Roam.SIMC.2.0.6.1093537417.28804.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
X-Spam-Score: 0.4 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Erik Nordmark <Erik.Nordmark@sun.com>
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 problem is due to sharing the same sequence number space among
> requests and answers sent by one side.  It is probably better and
> simpler to allocate one sequence number space to requests from PaC and
> the other sequence number space to requests from PAA, and make answers
> carry the sequence numbers of the corresponding requests, like the
> sequence number scheme taken by IKEv2.  By doing this, we do not need
> to carry two sequence numbers in each message any more, but there are
> still two sequence number spaces as the current PANA sequcen number
> scheme.

I think this makes sense.
I does assume that each request have a corresponding response. Is this the
case in the current PANA set of messages?

  Erik


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


From pana-bounces@ietf.org  Fri Aug 27 11:46: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 LAA10879
	for <pana-archive@lists.ietf.org>; Fri, 27 Aug 2004 11:46: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 1C0io8-0007VJ-TG; Fri, 27 Aug 2004 11:38:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0ifx-0005Te-81
	for pana@megatron.ietf.org; Fri, 27 Aug 2004 11:30: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 LAA09699
	for <pana@ietf.org>; Fri, 27 Aug 2004 11:29:57 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0ih6-0004GQ-DH
	for pana@ietf.org; Fri, 27 Aug 2004 11:31:13 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7RFTmbv022353;
	Sat, 28 Aug 2004 00:29:48 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7RFTmUC005653;
	Sat, 28 Aug 2004 00:29:48 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	AAA05652 ; Sat, 28 Aug 2004 00:29:48 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA06853; Sat, 28 Aug 2004 00:29:48 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7RFTlBq027708;
	Sat, 28 Aug 2004 00:29:47 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7RFTlwE023765;
	Sat, 28 Aug 2004 00:29:47 +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 <0I3400N8731J1I@tsbpo1.po.toshiba.co.jp>; Sat,
	28 Aug 2004 00:29:46 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C0ifN-0003sW-00; Fri, 27 Aug 2004 08:29:25 -0700
Date: Fri, 27 Aug 2004 11:29:25 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <Roam.SIMC.2.0.6.1093537417.28804.nordmark@bebop.france>
To: Erik Nordmark <Erik.Nordmark@sun.com>
Message-id: <20040827152925.GC1024@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Erik Nordmark <Erik.Nordmark@sun.com>,
	Yoshihiro Ohba <yohba@tari.toshiba.com>,
	Alper Yegin <alper.yegin@samsung.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040803i
References: <20040826141446.GP1024@steelhead>
	<Roam.SIMC.2.0.6.1093537417.28804.nordmark@bebop.france>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Alper Yegin <alper.yegin@samsung.com>,
        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, Aug 26, 2004 at 09:23:37AM -0700, Erik Nordmark wrote:
> > This problem is due to sharing the same sequence number space among
> > requests and answers sent by one side.  It is probably better and
> > simpler to allocate one sequence number space to requests from PaC and
> > the other sequence number space to requests from PAA, and make answers
> > carry the sequence numbers of the corresponding requests, like the
> > sequence number scheme taken by IKEv2.  By doing this, we do not need
> > to carry two sequence numbers in each message any more, but there are
> > still two sequence number spaces as the current PANA sequcen number
> > scheme.
> 
> I think this makes sense.
> I does assume that each request have a corresponding response. Is this the
> case in the current PANA set of messages?

PANA-PAA-Discover and PANA-Error do not have corresponding responses.  

- Since PANA-PAA-Discover is specially handled (the sequence number is
always zero), I think we don't need to define a corresponding response
for it.

- For PANA-Error, I think we needs to define a corresponding response.

Yoshihiro Ohba


> 
>   Erik
> 
> 
> _______________________________________________
> 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 Aug 27 14:19: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 OAA21200
	for <pana-archive@lists.ietf.org>; Fri, 27 Aug 2004 14:19: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 1C0lI1-0003Dv-1y; Fri, 27 Aug 2004 14:17:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0lF6-0002bM-7q
	for pana@megatron.ietf.org; Fri, 27 Aug 2004 14:14:30 -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 OAA20761
	for <pana@ietf.org>; Fri, 27 Aug 2004 14:14:26 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0lGG-0007RD-Rl
	for pana@ietf.org; Fri, 27 Aug 2004 14:15:42 -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 <0I340065SAN0O5@mailout1.samsung.com> for pana@ietf.org; Sat,
	28 Aug 2004 03:13:48 +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 <0I3400HQH9BH60@mailout1.samsung.com> for pana@ietf.org;
	Sat, 28 Aug 2004 02:45:17 +0900 (KST)
Received: from Alperyegin ([105.253.155.50])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I34008WX9B9UX@mmp1.samsung.com> for
	pana@ietf.org; Sat, 28 Aug 2004 02:45:17 +0900 (KST)
Date: Fri, 27 Aug 2004 10:45:07 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040827152925.GC1024@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
        "'Erik Nordmark'" <Erik.Nordmark@sun.com>
Message-id: <024c01c48c5d$9c530470$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 82c9bddb247d9ba4471160a9a865a5f3
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

Is it a requirement of this sequence numbering scheme that each message
that is not a response must generate a response from the receiving peer?

[the current spec says PANA-PAA-Discover uses sequence number 0. But I
suspect it is not taking into account that this message is also used by
PaC to initiate subsequent re-authentications. So maybe we shouldn't
really reset the sequence number like that in the middle of an ongoing
PANA session.]

Alper
  



> > > This problem is due to sharing the same sequence number space
among
> > > requests and answers sent by one side.  It is probably better and
> > > simpler to allocate one sequence number space to requests from PaC
and
> > > the other sequence number space to requests from PAA, and make
answers
> > > carry the sequence numbers of the corresponding requests, like the
> > > sequence number scheme taken by IKEv2.  By doing this, we do not
need
> > > to carry two sequence numbers in each message any more, but there
are
> > > still two sequence number spaces as the current PANA sequcen
number
> > > scheme.
> >
> > I think this makes sense.
> > I does assume that each request have a corresponding response. Is
this
> the
> > case in the current PANA set of messages?
> 
> PANA-PAA-Discover and PANA-Error do not have corresponding responses.
> 
> - Since PANA-PAA-Discover is specially handled (the sequence number is
> always zero), I think we don't need to define a corresponding response
> for it.
> 
> - For PANA-Error, I think we needs to define a corresponding response.
> 
> Yoshihiro Ohba
> 
> 
> >
> >   Erik
> >
> >
> > _______________________________________________
> > 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 Aug 27 14:21:45 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 OAA21319
	for <pana-archive@lists.ietf.org>; Fri, 27 Aug 2004 14:21:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C0lI1-0003E0-9l; Fri, 27 Aug 2004 14:17:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0lF8-0002bN-0B
	for pana@megatron.ietf.org; Fri, 27 Aug 2004 14:14:30 -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 OAA20764
	for <pana@ietf.org>; Fri, 27 Aug 2004 14:14:28 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0lGI-0007RD-Hu
	for pana@ietf.org; Fri, 27 Aug 2004 14:15:44 -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 <0I340069OAN7O5@mailout1.samsung.com> for pana@ietf.org; Sat,
	28 Aug 2004 03:13:55 +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 <0I3400AQH9M30H@mailout1.samsung.com> for pana@ietf.org;
	Sat, 28 Aug 2004 02:51:40 +0900 (KST)
Received: from Alperyegin ([105.253.155.50])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I34005VM9LVS7@mmp1.samsung.com> for
	pana@ietf.org; Sat, 28 Aug 2004 02:51:39 +0900 (KST)
Date: Fri, 27 Aug 2004 10:51:29 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <025201c48c5e$7ffd55e0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7f3fa64b9851a63d7f3174ef64114da7
Cc: "'Susan Thomson'" <sethomso@cisco.com>
Subject: [Pana] Alternative sequence numbering scheme
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="===============0703855717=="
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0703855717==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_ktzD2YdG54NF/Eb46H0CpA)"

This is a multi-part message in MIME format.

--Boundary_(ID_ktzD2YdG54NF/Eb46H0CpA)
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

Here is Susan Thomson's e-mail on the proposed scheme.
I think this is aligned with what Yoshi was describing as well.
 
Alper
 
-----Original Message-----
From: Susan Thomson [mailto:sethomso@cisco.com] 
Sent: Tuesday, August 24, 2004 6:55 PM
To: alper.yegin@samsung.com
Cc: jsalowey@cisco.com; hzhou@cisco.com; pgleicha@cisco.com
Subject: follow-up to PANA sequencing discussion
 
Hi Alper

A belated follow-up to sequencing discussion from IETF.

If the point of the second sequence number  is blind DOS protection
only, then an alternate proposal may be to rely on the session ID for
protection by making it a random number.

This frees up the sequencing scheme to use a single sequence number.

Assuming a request-response model where it is clear which messages are
requests and which responses, the sequence numbering works as follows:

[Note that a single component may play role of initiator or responder
for different message types depending on the protocol. In this case,
each endpoint of the protocol maintains two "current" Message IDs: the
next one to be used for a request it initiates and the next one it
expects to see in a request from the other end.]

The Initiator sets the Message ID in the header to any  value (e.g. 0)
in the first message of the session, and increases the Message ID by one
for each new request using serial number arithmetic. Retransmissions do
not increment the Message ID. Responses contain the same message ID as
the request. 

After the initial handshake, the Initiator keeps track of the current
Message ID to increment for new requests, to match up requests and
responses, and to identify retransmissions of messages. Likewise, the
Responder keeps track of the current Message ID to identify when a
request is new or when it is a retransmission. The Initiator is always
responsible for retransmissions. The Responder only retransmits a
response on seeing a retransmitted request; it does not otherwise
process the retransmitted request. 

If window is one (which I think it is for this protocol), the Initiator
must not send a new request until it receives a response to the previous
one. The Responder must remember a response until a request with a new
Message ID is received.

The above  is arguably simpler and can make use of a scheme that is
close to what many UDP-based protocols and thus is "tried-and-tested".
For example, the above is the same scheme that IKEv2 specifies.

Thanks
Susan



--Boundary_(ID_ktzD2YdG54NF/Eb46H0CpA)
Content-type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7BIT

<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<meta name=ProgId content=Word.Document>
<meta name=Generator content="Microsoft Word 10">
<meta name=Originator content="Microsoft Word 10">
<link rel=File-List href="cid:filelist.xml@01C48C23.CCED8A40">
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="time"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
 name="date"/>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:Compatibility>
   <w:UseFELayout/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;
	mso-font-alt:\BC14\D0D5;
	mso-font-charset:129;
	mso-generic-font-family:roman;
	mso-font-pitch:auto;
	mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:1627421319 -2147483648 8 0 66047 0;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;
	mso-font-charset:129;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:-1342176593 1775729915 48 0 524447 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:Batang;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */ 
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple style='tab-interval:.5in'>

<div class=Section1>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Here is Susan Thomson&#8217;s e-mail on
the proposed scheme.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I think this is aligned with what <span
class=SpellE>Yoshi</span> was describing as well.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Alper<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> Susan Thomson
[mailto:sethomso@cisco.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> </span></font><st1:date
Month="8" Day="24" Year="2004"><font size=2 face=Tahoma><span style='font-size:
 10.0pt;font-family:Tahoma'>Tuesday, August 24, 2004</span></font></st1:date><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> </span></font><st1:time
Hour="18" Minute="55"><font size=2 face=Tahoma><span style='font-size:10.0pt;
 font-family:Tahoma'>6:55 PM</span></font></st1:time><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'><br>
<b><span style='font-weight:bold'>To:</span></b> alper.yegin@samsung.com<br>
<b><span style='font-weight:bold'>Cc:</span></b> jsalowey@cisco.com;
hzhou@cisco.com; pgleicha@cisco.com<br>
<b><span style='font-weight:bold'>Subject:</span></b> follow-up to PANA
sequencing discussion</span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Hi Alper<br>
<br>
A belated follow-up to sequencing discussion from IETF.<br>
<br>
If the point of the second sequence number&nbsp; is blind DOS protection only,
then an alternate proposal may be to rely on the session ID for protection by
making it a random number.<br>
<br>
This frees up the sequencing scheme to use a single sequence number.<br>
<br>
Assuming a request-response model where it is clear which messages are requests
and which responses, the sequence numbering works as follows:<br>
<br>
[Note that a single component may play role of initiator or responder for
different message types depending on the protocol. In this case, e</span></font><font
face=Arial><span style='font-family:Arial'>ach endpoint of the protocol
maintains two &quot;current&quot; Message IDs: the next one to be used for a
request it initiates and the next one it expects to see in a request from the
other end.]<br>
<br>
</span></font>The Initiator sets the Message ID in the header to any&nbsp;
value<font face=Arial><span style='font-family:Arial'> (e.g. 0) in the first
message of the session, and increases the Message ID by one for each new
request using serial number arithmetic. Retransmissions do not increment the
Message ID. Responses contain the same message ID as the request. <br>
<br>
After the initial handshake, the Initiator keeps track of the current Message
ID to increment for new requests, to match up requests and responses, and to
identify retransmissions of messages. Likewise, the Responder keeps track of
the current Message ID to identify when a request is new or when it is a
retransmission. The Initiator is always responsible for retransmissions. The Responder
only retransmits a response on seeing a retransmitted request; it does not
otherwise process the retransmitted request. <br>
<br>
If window is one (which I think it is for this protocol), the Initiator must
not send a new request until it receives a response to the previous one. The
Responder must remember a response until a request with a new Message ID is
received.<br>
<br>
</span></font>The above&nbsp; is arguably simpler and can make use of a scheme
that is close to what many UDP-based protocols and thus is
&quot;tried-and-tested&quot;. For example, the above is the same scheme that
IKEv2 specifies.<br>
<br>
Thanks<br>
Susan<br style='mso-special-character:line-break'>
<![if !supportLineBreakNewLine]><br style='mso-special-character:line-break'>
<![endif]><o:p></o:p></p>

</div>

</body>

</html>

--Boundary_(ID_ktzD2YdG54NF/Eb46H0CpA)--


--===============0703855717==
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

--===============0703855717==--



From pana-bounces@ietf.org  Fri Aug 27 16:56: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 QAA10078
	for <pana-archive@lists.ietf.org>; Fri, 27 Aug 2004 16:56: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 1C0nSl-000775-TQ; Fri, 27 Aug 2004 16:36:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C0n85-0008Kc-BF
	for pana@megatron.ietf.org; Fri, 27 Aug 2004 16:15:21 -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 QAA03017
	for <pana@ietf.org>; Fri, 27 Aug 2004 16:15:18 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0n9H-0002Lv-RM
	for pana@ietf.org; Fri, 27 Aug 2004 16:16:36 -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 <0I3400E05G8IQ6@mailout2.samsung.com> for pana@ietf.org; Sat,
	28 Aug 2004 05:14:43 +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 <0I3400FCEG8HDP@mailout2.samsung.com> for pana@ietf.org;
	Sat, 28 Aug 2004 05:14:42 +0900 (KST)
Received: from Alperyegin ([105.253.155.50])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I34004YCG8E4A@mmp2.samsung.com> for
	pana@ietf.org; Sat, 28 Aug 2004 05:14:41 +0900 (KST)
Date: Fri, 27 Aug 2004 13:14:34 -0700
From: Alper Yegin <alper.yegin@samsung.com>
In-reply-to: <024c01c48c5d$9c530470$6401a8c0@sisa.samsung.com>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <027001c48c72$79dd1970$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: bd8a74b81c71f965ca7918b90d1c49c0
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
Subject: [Pana] Issue 105 - take 2
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

Let's get back to the resolution of Issue 105... Putting the sequence
numbering re-design aside (saving it for issue 106), here is what we
have for Issue 105. 

Note that only update #3 has changed since take 1.

  



[1] In Section 3:


Change:

   In addition, PANA defines the following two types of
   re-authentication procedures that are performed while an established
   PANA session exists.

   1.  Re-authentication based on EAP

   2.  Re-authentication based on PANA-Reauth exchange

   The former type of re-authentication is used mainly for extending
   authorization lifetime or for updating the cryptographic keying
   material of a PANA SA.  The latter type of re-authentication is used
   mainly for maintaining the presence of the communicating peers each
   other so that the established PANA session can be terminated as soon
   as the presence of the peer is lost.

To:

   In addition, PANA allows re-authentication of the PaC and PAA by
   allowing any one of them to initiate an EAP authentication during
   an on-going PANA session. Refreshing the session and cryptographic
   keys are possible reasons to engage in re-authentication.

   Finally, the protocol enables PAA and PaC ping each other to test 
   liveness of the session. 


[2] In Section 3.1:

Change:

  o  Re-authentication based on the PANA-Reauth-Request/ PANA-Reauth
      exchange is performed.

To:

  o  Liveness test based on the PANA-Ping-Request/PANA-Ping-Answer
      exchange is performed.


Change:

 // Re-authentication based on PANA-Reauth exchange
         <-----     PANA-Reauth-Request[Session-Id, MAC]
         ----->     PANA-Reauth-Answer[Session-Id, MAC]

To:

 // Liveness test based on PANA-Ping exchange
         <-----     PANA-Ping-Request[Session-Id, MAC]
         ----->     PANA-Ping-Answer[Session-Id, MAC]



[3] In Section 4.1.7:

Updated text: 

   o  The message type is one of the expected types in the current
      state.  Specifically the following messages are unexpected and
      invalid:

      *  In discovery and initial handshake phase:

         +  PANA-Termination-Request and PANA-Ping-Request.

         +  PANA-Bind-Request.

         +  PANA-Update-Request.

      *  In authentication phase:

         +  PANA-PAA-Discover.

         +  PANA-Update-Request.

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

         +  PANA-Termination-Request before the PaC receives the first
            successful PANA-Bind-Request.

      *  After successful PANA authentication:

         +  PANA-Start-Request as well as a non-duplicate
            PANA-Bind-Request (see section Section 4.7 for definition of
            duplicate requests).

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

      *  In termination phase:

         +  PANA-PAA-Discover.

         +  All requests but PANA-Termination-Request.


[4] New text for Section 4.4:

4.4  Re-authentication

   An already authenitcation PANA session can enter an authentication 
   phase by re-executing EAP. In this case, some or all message
exchanges
   for discovery and initial handshake phase MAY be omitted in the
   following way.  When a PaC wants to initiate re-authentication, 
   it sends a unicast PANA-PAA-Discovery message to
   the PAA.  This message MUST contain a Session-Id AVP which is used
   for identifying the PANA session on the PAA.  If the PAA already has
   an established PANA session for the PaC with the matching identifier,
   it sends a PANA-Auth-Request message containing the same identifier
   to start an authentication phase.  If the PAA can not recognize the
   session identifier, it proceeds with regular authentication by
   sending back PANA-Start-Request. When the PAA initiates
   re-authentication, it sends a PANA-Auth-Request message containing
   the session identifier for the PaC to enter an authentication phase.
   PAA SHOULD initiate EAP authentication before the current session
   lifetime expires.  In both cases, the tseq and rseq values are
   inherited from the previous (re-)authentication.  For any
   re-authentication, if there is an established PANA SA,
   PANA-Auth-Request and PANA-Auth-Answer messages MUST be protected by
   adding a MAC AVP to each message.  Any subsequent EAP-based
   authentication MUST be performed with the same ISP and NAP that was
   selected during the initial authentication.  An example sequence for
   a re-authentication initiated by a PaC is shown in Figure
   6.

      PaC      PAA  Message
      ------------------------------------------------------
         ----->     PANA-PAA-Discover(0,0)[Session-Id]
         <-----     PANA-Auth-Request(p,q)[Session-Id, EAP, MAC]
         ----->     PANA-Auth-Answer(q+1,p)[Session-Id, EAP, MAC]
         <-----     PANA-Auth-Request(p+1,q+1)[Session-Id, EAP, MAC]
         ----->     PANA-Auth-Answer(q+2,p+1)[Session-Id, EAP, MAC]
         <-----     PANA-Bind-Request(p+2,q+2)
                       [Session-Id, EAP{Success}, Device-Id, Key-Id,
                        Lifetime, Protection-Cap., PPAC, MAC]
         ----->     PANA-Bind-Answer(q+3,p+2)
                       [Session-Id, Device-Id, Key-Id, PPAC, MAC]

  Figure 6: Example Sequence for EAP-based re-authentication initiated
                                 by PaC


[5] Create a new section after the current Section 4.4

4.5. Liveness Test
 
   PANA-Ping-Request and PANA-Ping-Answer messages are used for testing
   the liveness of the PANA session on the PANA peer. If there is an 
   established PANA session, both the PaC and
   the PAA are allowed to send a PANA-Ping-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-Ping-Answer message.  Both PANA-Ping-Request and
   PANA-Ping-Answer messages MUST be protected with a MAC AVP when a
   PANA SA is available.

   Implementations MUST limit the rate of performing this test.  
   The PaC and the PAA can handle
   rate limitation on their own, they do not have to perform any
   coordination with each other.  There is no negotiation of timers for
   this purpose.

   Figure 7 and Figure 8 illustrate liveness tests as they are initiated
   by the PaC and the PAA respectively.


      PaC      PAA     Message(tseq,rseq)[AVPs]
      ------------------------------------------------------
         ----->        PANA-Ping-Request(q,p)[Session-Id, MAC]
         <-----        PANA-Ping-Answer(p+1,q)[Session-Id, MAC]


        Figure 7: Example Sequence for PaC-initiated liveness test


      PaC      PAA     Message(tseq,rseq)[AVPs]
      ------------------------------------------------------
         <-----        PANA-Ping-Request(p,q)[Session-Id, MAC]
         ----->        PANA-Ping-Answer(q+1,p)[Session-Id, MAC]


        Figure 8: Example Sequence for PAA-initiated liveness test


[6] In section 4.6:

Remove:

  o  Re-authentication based on the PANA-Reauth exchange is performed.


[7] In Section 4.10:

Change:

   PANA peer can use PANA-Reauth-Request message to
   verify the disconnection before taking an action.

   The session lifetime parameter is not related to the transmission of
   PANA-Reauth-Request messages.  These messages can be used for
   asynchronously verifying the liveness of the peer and enabling
   mobility optimizations.  The decision to send PANA-Reauth-Request
   message is taken locally and does not require coordination between
   the peers.

To:

   PANA peer can use PANA-Ping-Request message to
   verify the disconnection before taking an action.

   The session lifetime parameter is not related to the transmission of
   PANA-Ping-Request messages.  These messages can be used for
   asynchronously verifying the liveness of the peer.  The decision 
   to send PANA-Ping-Request message is taken locally and does not 
   require coordination between the peers.


[8] In Section 6.4:

Change:

                 PANA-Reauth-Request         <------->
                 PANA-Reauth-Answer          <------->

To:

                 PANA-Ping-Request           <------->
                 PANA-Ping-Answer            <------->

[9] New text for Section 6.4.9 and 6.4.10:

6.4.9  PANA-Ping-Request (PPR)

   PANA-Ping-Request (PPR) is either sent by the PaC or the PAA.

         PANA-Ping-Request ::= < PANA-Header: 5, REQ >
                       < Session-Id >
                    *  [ AVP ]
                   0*1 < MAC >


6.4.10  PANA-Ping-Answer (PPA)

   PANA-Ping-Answer (PPA) is sent in response to a
   PANA-Ping-Request.

         PANA-Ping-Answer ::= < PANA-Header: 5 >
                       < Session-Id >
                    *  [ AVP ]
                   0*1 < MAC >

[10] In Section 6.6:

Change:

 Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER | PFEA |

To:

 Attribute Name      | PPR  | PPA  | PTR | PTA | PER | PFER | PFEA |



[11] In Section 7:

Change:

         PANA-Reauth-Request (PRAR)

To:

         PANA-Ping-Request (PPR)


Change:

   The last two messages, PRAR and PTR are sent either by PaC or
   PAA.

To:

   The last two messages, PPR and PTR are sent either by PaC or
   PAA.


[12] In Section 9.g:


Change:

   A disconnect may also be detected earlier by using PANA
   reauthentication messages.

To:

   A disconnect may also be detected earlier by using PANA
   ping messages.






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


From pana-bounces@ietf.org  Sun Aug 29 22:54:25 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 WAA26453
	for <pana-archive@lists.ietf.org>; Sun, 29 Aug 2004 22:54:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1cHi-0002no-P6; Sun, 29 Aug 2004 22:52:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1cHQ-00028M-Hb
	for pana@megatron.ietf.org; Sun, 29 Aug 2004 22:52:25 -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 WAA26225
	for <pana@ietf.org>; Sun, 29 Aug 2004 22:52:21 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1cJ6-0006qO-F3
	for pana@ietf.org; Sun, 29 Aug 2004 22:54:09 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7U2qEbv020999;
	Mon, 30 Aug 2004 11:52:14 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7U2qEjS026519;
	Mon, 30 Aug 2004 11:52:14 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	MAA26513 ; Mon, 30 Aug 2004 11:52:14 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id LAA12343; Mon, 30 Aug 2004 11:52:13 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7U2qBuV024093;
	Mon, 30 Aug 2004 11:52:11 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7U2qBwE016478;
	Mon, 30 Aug 2004 11:52:11 +0900 (JST)
Received: from steelhead (iVPN01-135.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 <0I38003N6NYXZD@tsbpo1.po.toshiba.co.jp>; Mon,
	30 Aug 2004 11:52:10 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C1cGs-0004CN-00; Sun, 29 Aug 2004 19:51:50 -0700
Date: Sun, 29 Aug 2004 22:51:44 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
In-reply-to: <027001c48c72$79dd1970$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040830025144.GD1536@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+20040818i
References: <024c01c48c5d$9c530470$6401a8c0@sisa.samsung.com>
	<027001c48c72$79dd1970$6401a8c0@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Subject: [Pana] Re: Issue 105 - take 2
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 text looks good.  I found one typo.

On Fri, Aug 27, 2004 at 01:14:34PM -0700, Alper Yegin wrote:
> [4] New text for Section 4.4:
> 
> 4.4  Re-authentication
> 
>    An already authenitcation PANA session can enter an authentication 

I guess the above text should be "An already established PANA session..."

Yoshihiro Ohba


>    phase by re-executing EAP. In this case, some or all message
> exchanges
>    for discovery and initial handshake phase MAY be omitted in the
>    following way.  When a PaC wants to initiate re-authentication, 
>    it sends a unicast PANA-PAA-Discovery message to
>    the PAA.  This message MUST contain a Session-Id AVP which is used
>    for identifying the PANA session on the PAA.  If the PAA already has
>    an established PANA session for the PaC with the matching identifier,
>    it sends a PANA-Auth-Request message containing the same identifier
>    to start an authentication phase.  If the PAA can not recognize the
>    session identifier, it proceeds with regular authentication by
>    sending back PANA-Start-Request. When the PAA initiates
>    re-authentication, it sends a PANA-Auth-Request message containing
>    the session identifier for the PaC to enter an authentication phase.
>    PAA SHOULD initiate EAP authentication before the current session
>    lifetime expires.  In both cases, the tseq and rseq values are
>    inherited from the previous (re-)authentication.  For any
>    re-authentication, if there is an established PANA SA,
>    PANA-Auth-Request and PANA-Auth-Answer messages MUST be protected by
>    adding a MAC AVP to each message.  Any subsequent EAP-based
>    authentication MUST be performed with the same ISP and NAP that was
>    selected during the initial authentication.  An example sequence for
>    a re-authentication initiated by a PaC is shown in Figure
>    6.
> 
>       PaC      PAA  Message
>       ------------------------------------------------------
>          ----->     PANA-PAA-Discover(0,0)[Session-Id]
>          <-----     PANA-Auth-Request(p,q)[Session-Id, EAP, MAC]
>          ----->     PANA-Auth-Answer(q+1,p)[Session-Id, EAP, MAC]
>          <-----     PANA-Auth-Request(p+1,q+1)[Session-Id, EAP, MAC]
>          ----->     PANA-Auth-Answer(q+2,p+1)[Session-Id, EAP, MAC]
>          <-----     PANA-Bind-Request(p+2,q+2)
>                        [Session-Id, EAP{Success}, Device-Id, Key-Id,
>                         Lifetime, Protection-Cap., PPAC, MAC]
>          ----->     PANA-Bind-Answer(q+3,p+2)
>                        [Session-Id, Device-Id, Key-Id, PPAC, MAC]
> 
>   Figure 6: Example Sequence for EAP-based re-authentication initiated
>                                  by PaC
> 
> 

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


From pana-bounces@ietf.org  Sun Aug 29 23:37: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 XAA29157
	for <pana-archive@lists.ietf.org>; Sun, 29 Aug 2004 23:37: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 1C1cxb-0006IC-PA; Sun, 29 Aug 2004 23:35:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1cwg-0006DT-SC
	for pana@megatron.ietf.org; Sun, 29 Aug 2004 23:35:03 -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 XAA29050
	for <pana@ietf.org>; Sun, 29 Aug 2004 23:34:59 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1cyN-0007lm-A4
	for pana@ietf.org; Sun, 29 Aug 2004 23:36:47 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7U3Z0bv020844;
	Mon, 30 Aug 2004 12:35:00 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7U3Z01A020651;
	Mon, 30 Aug 2004 12:35:00 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	NAA20647 ; Mon, 30 Aug 2004 12:34:59 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id MAA16547; Mon, 30 Aug 2004 12:34:59 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7U3YwXK010138;
	Mon, 30 Aug 2004 12:34:58 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7U3YwwE022330;
	Mon, 30 Aug 2004 12:34:58 +0900 (JST)
Received: from steelhead (iVPN01-135.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 <0I3800BWZPY71M@tsbpo1.po.toshiba.co.jp>; Mon,
	30 Aug 2004 12:34:57 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C1cvN-0004Q3-00; Sun, 29 Aug 2004 20:33:41 -0700
Date: Sun, 29 Aug 2004 23:33:41 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <024c01c48c5d$9c530470$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040830033341.GE1536@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>,
	'Erik Nordmark' <Erik.Nordmark@sun.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040818i
References: <20040827152925.GC1024@steelhead>
	<024c01c48c5d$9c530470$6401a8c0@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
        "'Erik Nordmark'" <Erik.Nordmark@sun.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, Aug 27, 2004 at 10:45:07AM -0700, Alper Yegin wrote:
> Is it a requirement of this sequence numbering scheme that each message
> that is not a response must generate a response from the receiving peer?

I think so.  If there is some message for which a corresponding
response is not defined, then an endpoint cannot determine the next
sequence number to receive (due to a possible sequence number gap when
such a message is lost).  If we want to make some message
unacknowledged, then an endpoint would need to accept a range of
sequence numbers for the next message, but I think defining such a
range is difficult.

I think the "two sequence number spaces but one sequence number in
message header" scheme like IKEv2 works only if a protocol is defined
as a reliable protocol, again like IKEv2.

> 
> [the current spec says PANA-PAA-Discover uses sequence number 0. But I
> suspect it is not taking into account that this message is also used by
> PaC to initiate subsequent re-authentications. So maybe we shouldn't
> really reset the sequence number like that in the middle of an ongoing
> PANA session.]

When a PaC sends a PDI to initiate re-authentication, it carries the
sequence number 0, but in subsequent PANA message exchange the
previous sequence numbers are inherited according to section 4.4.

Yoshihiro Ohba

> 
> Alper
>   
> 
> 
> 
> > > > This problem is due to sharing the same sequence number space
> among
> > > > requests and answers sent by one side.  It is probably better and
> > > > simpler to allocate one sequence number space to requests from PaC
> and
> > > > the other sequence number space to requests from PAA, and make
> answers
> > > > carry the sequence numbers of the corresponding requests, like the
> > > > sequence number scheme taken by IKEv2.  By doing this, we do not
> need
> > > > to carry two sequence numbers in each message any more, but there
> are
> > > > still two sequence number spaces as the current PANA sequcen
> number
> > > > scheme.
> > >
> > > I think this makes sense.
> > > I does assume that each request have a corresponding response. Is
> this
> > the
> > > case in the current PANA set of messages?
> > 
> > PANA-PAA-Discover and PANA-Error do not have corresponding responses.
> > 
> > - Since PANA-PAA-Discover is specially handled (the sequence number is
> > always zero), I think we don't need to define a corresponding response
> > for it.
> > 
> > - For PANA-Error, I think we needs to define a corresponding response.
> > 
> > Yoshihiro Ohba
> > 
> > 
> > >
> > >   Erik
> > >
> > >
> > > _______________________________________________
> > > 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 Aug 30 14:04: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 OAA13614
	for <pana-archive@lists.ietf.org>; Mon, 30 Aug 2004 14:04: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 1C1qTm-0002K3-TJ; Mon, 30 Aug 2004 14:02:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1qPj-0001Hz-3X
	for pana@megatron.ietf.org; Mon, 30 Aug 2004 13:57:55 -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 NAA13183
	for <pana@ietf.org>; Mon, 30 Aug 2004 13:57:53 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1qRW-0001Up-Vf
	for pana@ietf.org; Mon, 30 Aug 2004 13:59:47 -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 <0I3900FJHTVLH6@mailout1.samsung.com> for pana@ietf.org; Tue,
	31 Aug 2004 02:57:21 +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 <0I39004PPTGO6V@mailout1.samsung.com> for pana@ietf.org;
	Tue, 31 Aug 2004 02:48:24 +0900 (KST)
Received: from Alperyegin ([105.253.155.52])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I3900CGSTGKA1@mmp2.samsung.com> for
	pana@ietf.org; Tue, 31 Aug 2004 02:48:24 +0900 (KST)
Date: Mon, 30 Aug 2004 10:48:20 -0700
From: Alper Yegin <alper.yegin@samsung.com>
In-reply-to: <027001c48c72$79dd1970$6401a8c0@sisa.samsung.com>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <003001c48eb9$8b636f20$291d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: dd887a8966a4c4c217a52303814d0b5f
Content-Transfer-Encoding: 7BIT
Cc: pana@ietf.org
Subject: [Pana] Issue 105 - take 3
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


Fixed the problem in [4]...

  

[1] In Section 3:


Change:

   In addition, PANA defines the following two types of
   re-authentication procedures that are performed while an established
   PANA session exists.

   1.  Re-authentication based on EAP

   2.  Re-authentication based on PANA-Reauth exchange

   The former type of re-authentication is used mainly for extending
   authorization lifetime or for updating the cryptographic keying
   material of a PANA SA.  The latter type of re-authentication is used
   mainly for maintaining the presence of the communicating peers each
   other so that the established PANA session can be terminated as soon
   as the presence of the peer is lost.

To:

   In addition, PANA allows re-authentication of the PaC and PAA by
   allowing any one of them to initiate an EAP authentication during
   an on-going PANA session. Refreshing the session and cryptographic
   keys are possible reasons to engage in re-authentication.

   Finally, the protocol enables PAA and PaC ping each other to test 
   liveness of the session. 


[2] In Section 3.1:

Change:

  o  Re-authentication based on the PANA-Reauth-Request/ PANA-Reauth
      exchange is performed.

To:

  o  Liveness test based on the PANA-Ping-Request/PANA-Ping-Answer
      exchange is performed.


Change:

 // Re-authentication based on PANA-Reauth exchange
         <-----     PANA-Reauth-Request[Session-Id, MAC]
         ----->     PANA-Reauth-Answer[Session-Id, MAC]

To:

 // Liveness test based on PANA-Ping exchange
         <-----     PANA-Ping-Request[Session-Id, MAC]
         ----->     PANA-Ping-Answer[Session-Id, MAC]



[3] In Section 4.1.7:

Updated text: 

   o  The message type is one of the expected types in the current
      state.  Specifically the following messages are unexpected and
      invalid:

      *  In discovery and initial handshake phase:

         +  PANA-Termination-Request and PANA-Ping-Request.

         +  PANA-Bind-Request.

         +  PANA-Update-Request.

      *  In authentication phase:

         +  PANA-PAA-Discover.

         +  PANA-Update-Request.

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

         +  PANA-Termination-Request before the PaC receives the first
            successful PANA-Bind-Request.

      *  After successful PANA authentication:

         +  PANA-Start-Request as well as a non-duplicate
            PANA-Bind-Request (see section Section 4.7 for definition of
            duplicate requests).

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

      *  In termination phase:

         +  PANA-PAA-Discover.

         +  All requests but PANA-Termination-Request.


[4] New text for Section 4.4:

4.4  Re-authentication

   An already established PANA session can enter an authentication 
   phase by re-executing EAP. In this case, some or all message
exchanges
   for discovery and initial handshake phase MAY be omitted in the
   following way.  When a PaC wants to initiate re-authentication, 
   it sends a unicast PANA-PAA-Discovery message to
   the PAA.  This message MUST contain a Session-Id AVP which is used
   for identifying the PANA session on the PAA.  If the PAA already has
   an established PANA session for the PaC with the matching identifier,
   it sends a PANA-Auth-Request message containing the same identifier
   to start an authentication phase.  If the PAA can not recognize the
   session identifier, it proceeds with regular authentication by
   sending back PANA-Start-Request. When the PAA initiates
   re-authentication, it sends a PANA-Auth-Request message containing
   the session identifier for the PaC to enter an authentication phase.
   PAA SHOULD initiate EAP authentication before the current session
   lifetime expires.  In both cases, the tseq and rseq values are
   inherited from the previous (re-)authentication.  For any
   re-authentication, if there is an established PANA SA,
   PANA-Auth-Request and PANA-Auth-Answer messages MUST be protected by
   adding a MAC AVP to each message.  Any subsequent EAP-based
   authentication MUST be performed with the same ISP and NAP that was
   selected during the initial authentication.  An example sequence for
   a re-authentication initiated by a PaC is shown in Figure
   6.

      PaC      PAA  Message
      ------------------------------------------------------
         ----->     PANA-PAA-Discover(0,0)[Session-Id]
         <-----     PANA-Auth-Request(p,q)[Session-Id, EAP, MAC]
         ----->     PANA-Auth-Answer(q+1,p)[Session-Id, EAP, MAC]
         <-----     PANA-Auth-Request(p+1,q+1)[Session-Id, EAP, MAC]
         ----->     PANA-Auth-Answer(q+2,p+1)[Session-Id, EAP, MAC]
         <-----     PANA-Bind-Request(p+2,q+2)
                       [Session-Id, EAP{Success}, Device-Id, Key-Id,
                        Lifetime, Protection-Cap., PPAC, MAC]
         ----->     PANA-Bind-Answer(q+3,p+2)
                       [Session-Id, Device-Id, Key-Id, PPAC, MAC]

  Figure 6: Example Sequence for EAP-based re-authentication initiated
                                 by PaC


[5] Create a new section after the current Section 4.4

4.5. Liveness Test
 
   PANA-Ping-Request and PANA-Ping-Answer messages are used for testing
   the liveness of the PANA session on the PANA peer. If there is an 
   established PANA session, both the PaC and
   the PAA are allowed to send a PANA-Ping-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-Ping-Answer message.  Both PANA-Ping-Request and
   PANA-Ping-Answer messages MUST be protected with a MAC AVP when a
   PANA SA is available.

   Implementations MUST limit the rate of performing this test.  
   The PaC and the PAA can handle
   rate limitation on their own, they do not have to perform any
   coordination with each other.  There is no negotiation of timers for
   this purpose.

   Figure 7 and Figure 8 illustrate liveness tests as they are initiated
   by the PaC and the PAA respectively.


      PaC      PAA     Message(tseq,rseq)[AVPs]
      ------------------------------------------------------
         ----->        PANA-Ping-Request(q,p)[Session-Id, MAC]
         <-----        PANA-Ping-Answer(p+1,q)[Session-Id, MAC]


        Figure 7: Example Sequence for PaC-initiated liveness test


      PaC      PAA     Message(tseq,rseq)[AVPs]
      ------------------------------------------------------
         <-----        PANA-Ping-Request(p,q)[Session-Id, MAC]
         ----->        PANA-Ping-Answer(q+1,p)[Session-Id, MAC]


        Figure 8: Example Sequence for PAA-initiated liveness test


[6] In section 4.6:

Remove:

  o  Re-authentication based on the PANA-Reauth exchange is performed.


[7] In Section 4.10:

Change:

   PANA peer can use PANA-Reauth-Request message to
   verify the disconnection before taking an action.

   The session lifetime parameter is not related to the transmission of
   PANA-Reauth-Request messages.  These messages can be used for
   asynchronously verifying the liveness of the peer and enabling
   mobility optimizations.  The decision to send PANA-Reauth-Request
   message is taken locally and does not require coordination between
   the peers.

To:

   PANA peer can use PANA-Ping-Request message to
   verify the disconnection before taking an action.

   The session lifetime parameter is not related to the transmission of
   PANA-Ping-Request messages.  These messages can be used for
   asynchronously verifying the liveness of the peer.  The decision 
   to send PANA-Ping-Request message is taken locally and does not 
   require coordination between the peers.


[8] In Section 6.4:

Change:

                 PANA-Reauth-Request         <------->
                 PANA-Reauth-Answer          <------->

To:

                 PANA-Ping-Request           <------->
                 PANA-Ping-Answer            <------->

[9] New text for Section 6.4.9 and 6.4.10:

6.4.9  PANA-Ping-Request (PPR)

   PANA-Ping-Request (PPR) is either sent by the PaC or the PAA.

         PANA-Ping-Request ::= < PANA-Header: 5, REQ >
                       < Session-Id >
                    *  [ AVP ]
                   0*1 < MAC >


6.4.10  PANA-Ping-Answer (PPA)

   PANA-Ping-Answer (PPA) is sent in response to a
   PANA-Ping-Request.

         PANA-Ping-Answer ::= < PANA-Header: 5 >
                       < Session-Id >
                    *  [ AVP ]
                   0*1 < MAC >

[10] In Section 6.6:

Change:

 Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER | PFEA |

To:

 Attribute Name      | PPR  | PPA  | PTR | PTA | PER | PFER | PFEA |



[11] In Section 7:

Change:

         PANA-Reauth-Request (PRAR)

To:

         PANA-Ping-Request (PPR)


Change:

   The last two messages, PRAR and PTR are sent either by PaC or
   PAA.

To:

   The last two messages, PPR and PTR are sent either by PaC or
   PAA.


[12] In Section 9.g:


Change:

   A disconnect may also be detected earlier by using PANA
   reauthentication messages.

To:

   A disconnect may also be detected earlier by using PANA
   ping messages.





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


From pana-bounces@ietf.org  Mon Aug 30 15:02:11 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 PAA17260
	for <pana-archive@lists.ietf.org>; Mon, 30 Aug 2004 15:02:11 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1rNe-00032E-LR; Mon, 30 Aug 2004 14:59:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1rDe-0000fP-Ld
	for pana@megatron.ietf.org; Mon, 30 Aug 2004 14:49:30 -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 OAA16312
	for <pana@ietf.org>; Mon, 30 Aug 2004 14:49:28 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1rFT-0002cg-Ey
	for pana@ietf.org; Mon, 30 Aug 2004 14:51:23 -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 <0I3900G01W9LUW@mailout3.samsung.com> for pana@ietf.org; Tue,
	31 Aug 2004 03:48:57 +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 <0I3900H6RW9L49@mailout3.samsung.com> for pana@ietf.org;
	Tue, 31 Aug 2004 03:48:57 +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 <0I39002EXW9IW4@mmp1.samsung.com> for
	pana@ietf.org; Tue, 31 Aug 2004 03:48:57 +0900 (KST)
Date: Mon, 30 Aug 2004 11:48:53 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040830033341.GE1536@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <003401c48ec2$01294ce0$291d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 2086112c730e13d5955355df27e3074b
Content-Transfer-Encoding: 7BIT
Cc: "'Erik Nordmark'" <Erik.Nordmark@sun.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

> > Is it a requirement of this sequence numbering scheme that each
message
> > that is not a response must generate a response from the receiving
peer?
> 
> I think so.  If there is some message for which a corresponding
> response is not defined, then an endpoint cannot determine the next
> sequence number to receive 

Why does it have to determine the next sequence number to receive?
All we care is orderly delivery. And for that, we can simply compare if
the new sequence number is greater than or equal to previous one. [This
has the potential blind DoS vulnerability, which should be taken care of
by having to match the randomly assigned Session ID]

Furthermore, in addition to PDI and PER, I think PAR also has issues.
PAR is not delivered reliably at the PANA layer. So, a single PAR can be
lost, and the EAP-generated retransmission would not have the same PANA
sequence number when transmitted. So, a legitimate gap in sequence
number is possible.

> (due to a possible sequence number gap when
> such a message is lost).  If we want to make some message
> unacknowledged, then an endpoint would need to accept a range of
> sequence numbers for the next message, but I think defining such a
> range is difficult.
> 
> I think the "two sequence number spaces but one sequence number in
> message header" scheme like IKEv2 works only if a protocol is defined
> as a reliable protocol, again like IKEv2.
> 
> >
> > [the current spec says PANA-PAA-Discover uses sequence number 0. But
I
> > suspect it is not taking into account that this message is also used
by
> > PaC to initiate subsequent re-authentications. So maybe we shouldn't
> > really reset the sequence number like that in the middle of an
ongoing
> > PANA session.]
> 
> When a PaC sends a PDI to initiate re-authentication, it carries the
> sequence number 0, but in subsequent PANA message exchange the
> previous sequence numbers are inherited according to section 4.4.

I didn't think so. I think this part is underspecified in the text. What
would be the logic behind PDI always using 0? I understand the very
first PDI, but the subsequent PDIs (which are unicasted btw) could
continue the ongoing sequence [given that we don't force
request-response with matching sequence numbers on all types of
messages].

Alper









> 
> Yoshihiro Ohba
> 
> >
> > Alper
> >
> >
> >
> >
> > > > > This problem is due to sharing the same sequence number space
> > among
> > > > > requests and answers sent by one side.  It is probably better
and
> > > > > simpler to allocate one sequence number space to requests from
PaC
> > and
> > > > > the other sequence number space to requests from PAA, and make
> > answers
> > > > > carry the sequence numbers of the corresponding requests, like
the
> > > > > sequence number scheme taken by IKEv2.  By doing this, we do
not
> > need
> > > > > to carry two sequence numbers in each message any more, but
there
> > are
> > > > > still two sequence number spaces as the current PANA sequcen
> > number
> > > > > scheme.
> > > >
> > > > I think this makes sense.
> > > > I does assume that each request have a corresponding response.
Is
> > this
> > > the
> > > > case in the current PANA set of messages?
> > >
> > > PANA-PAA-Discover and PANA-Error do not have corresponding
responses.
> > >
> > > - Since PANA-PAA-Discover is specially handled (the sequence
number is
> > > always zero), I think we don't need to define a corresponding
response
> > > for it.
> > >
> > > - For PANA-Error, I think we needs to define a corresponding
response.
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > > >
> > > >   Erik
> > > >
> > > >
> > > > _______________________________________________
> > > > 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 Aug 30 19:41:11 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 TAA14596
	for <pana-archive@lists.ietf.org>; Mon, 30 Aug 2004 19:41:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1vfV-0002B1-7i; Mon, 30 Aug 2004 19:34:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1vea-0001sC-14
	for pana@megatron.ietf.org; Mon, 30 Aug 2004 19:33:36 -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 TAA14282
	for <pana@ietf.org>; Mon, 30 Aug 2004 19:33:32 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1vgR-0003MJ-2O
	for pana@ietf.org; Mon, 30 Aug 2004 19:35:31 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7UNXRbv017627;
	Tue, 31 Aug 2004 08:33:27 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7UNXRiv012877;
	Tue, 31 Aug 2004 08:33:27 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	JAA12875 ; Tue, 31 Aug 2004 08:33:27 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA07000; Tue, 31 Aug 2004 08:33:22 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7UNXKA1027571;
	Tue, 31 Aug 2004 08:33:20 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7UNXJwE021898;
	Tue, 31 Aug 2004 08:33:19 +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 <0I3A00M6K9FGH3@tsbpo1.po.toshiba.co.jp>; Tue,
	31 Aug 2004 08:33:19 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C1vdf-00067Y-00; Mon, 30 Aug 2004 16:32:39 -0700
Date: Mon, 30 Aug 2004 19:32:39 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <003401c48ec2$01294ce0$291d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040830233238.GG1536@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>,
	'Erik Nordmark' <Erik.Nordmark@sun.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040818i
References: <20040830033341.GE1536@steelhead>
	<003401c48ec2$01294ce0$291d9069@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
        "'Erik Nordmark'" <Erik.Nordmark@sun.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, Aug 30, 2004 at 11:48:53AM -0700, Alper Yegin wrote:
> > > Is it a requirement of this sequence numbering scheme that each
> message
> > > that is not a response must generate a response from the receiving
> peer?
> > 
> > I think so.  If there is some message for which a corresponding
> > response is not defined, then an endpoint cannot determine the next
> > sequence number to receive 
> 
> Why does it have to determine the next sequence number to receive?
> All we care is orderly delivery. And for that, we can simply compare if
> the new sequence number is greater than or equal to previous one. [This
> has the potential blind DoS vulnerability, which should be taken care of
> by having to match the randomly assigned Session ID]

I think that the simple comparison scheme is too vulnerable to DoS
attack even having to match the Session ID.  The attacker can see one
packet to obtain the Session ID and sequence number and later on it
can blindly inject a bogus message with the expected Session ID and an
expected sequence number at about 50% probability.  This is the reason
for carrying rseq (receiving sequence number) in the current PANA
sequence number scheme.

> 
> Furthermore, in addition to PDI and PER, I think PAR also has issues.

Yes, I think so.

> PAR is not delivered reliably at the PANA layer. So, a single PAR can be
> lost, and the EAP-generated retransmission would not have the same PANA
> sequence number when transmitted. So, a legitimate gap in sequence
> number is possible.

Yes.  I am trying to analyze the effect of allowing the legitimate gap
in an IKEV2-like sequence number scheme, but I have yet come up with a
good solution to allow the gap.  A safer solution is to move the
responsibility of EAP message retransmission from EAP to PANA, but I
don't have a strong justification for it for now, either.

> 
> > (due to a possible sequence number gap when
> > such a message is lost).  If we want to make some message
> > unacknowledged, then an endpoint would need to accept a range of
> > sequence numbers for the next message, but I think defining such a
> > range is difficult.
> > 
> > I think the "two sequence number spaces but one sequence number in
> > message header" scheme like IKEv2 works only if a protocol is defined
> > as a reliable protocol, again like IKEv2.
> > 
> > >
> > > [the current spec says PANA-PAA-Discover uses sequence number 0. But
> I
> > > suspect it is not taking into account that this message is also used
> by
> > > PaC to initiate subsequent re-authentications. So maybe we shouldn't
> > > really reset the sequence number like that in the middle of an
> ongoing
> > > PANA session.]
> > 
> > When a PaC sends a PDI to initiate re-authentication, it carries the
> > sequence number 0, but in subsequent PANA message exchange the
> > previous sequence numbers are inherited according to section 4.4.
> 
> I didn't think so. I think this part is underspecified in the text. What
> would be the logic behind PDI always using 0? I understand the very
> first PDI, but the subsequent PDIs (which are unicasted btw) could
> continue the ongoing sequence [given that we don't force
> request-response with matching sequence numbers on all types of
> messages].

I understand it. I think we should not use the 0 sequence number for
PDI when it is sent for re-authentication (and such a PDI should 
be protected with a MAC AVP when a PANA SA is available.)

Yoshihiro Ohba


> 
> Alper
> 
> 
> 
> 
> 
> 
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > >
> > > Alper
> > >
> > >
> > >
> > >
> > > > > > This problem is due to sharing the same sequence number space
> > > among
> > > > > > requests and answers sent by one side.  It is probably better
> and
> > > > > > simpler to allocate one sequence number space to requests from
> PaC
> > > and
> > > > > > the other sequence number space to requests from PAA, and make
> > > answers
> > > > > > carry the sequence numbers of the corresponding requests, like
> the
> > > > > > sequence number scheme taken by IKEv2.  By doing this, we do
> not
> > > need
> > > > > > to carry two sequence numbers in each message any more, but
> there
> > > are
> > > > > > still two sequence number spaces as the current PANA sequcen
> > > number
> > > > > > scheme.
> > > > >
> > > > > I think this makes sense.
> > > > > I does assume that each request have a corresponding response.
> Is
> > > this
> > > > the
> > > > > case in the current PANA set of messages?
> > > >
> > > > PANA-PAA-Discover and PANA-Error do not have corresponding
> responses.
> > > >
> > > > - Since PANA-PAA-Discover is specially handled (the sequence
> number is
> > > > always zero), I think we don't need to define a corresponding
> response
> > > > for it.
> > > >
> > > > - For PANA-Error, I think we needs to define a corresponding
> response.
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > >
> > > > >   Erik
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > 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 Aug 30 20:31: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 UAA17732
	for <pana-archive@lists.ietf.org>; Mon, 30 Aug 2004 20:31: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 1C1wW0-0005Zh-Vh; Mon, 30 Aug 2004 20:28:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1wVo-0005P8-SZ
	for pana@megatron.ietf.org; Mon, 30 Aug 2004 20:28:36 -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 UAA17509
	for <pana@ietf.org>; Mon, 30 Aug 2004 20:28:35 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1wXf-0004bJ-TQ
	for pana@ietf.org; Mon, 30 Aug 2004 20:30:33 -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 <0I3A005JUBYMWN@mailout3.samsung.com> for pana@ietf.org; Tue,
	31 Aug 2004 09:27: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 <0I3A0057RBWCRE@mailout3.samsung.com> for pana@ietf.org;
	Tue, 31 Aug 2004 09:26:37 +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 <0I3A0025PBWAW4@mmp1.samsung.com> for
	pana@ietf.org; Tue, 31 Aug 2004 09:26:36 +0900 (KST)
Date: Mon, 30 Aug 2004 17:26:34 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040830233238.GG1536@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <00cc01c48ef1$2cd0a3f0$291d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7BIT
Cc: "'Erik Nordmark'" <Erik.Nordmark@sun.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

> > Why does it have to determine the next sequence number to receive?
> > All we care is orderly delivery. And for that, we can simply compare
if
> > the new sequence number is greater than or equal to previous one.
[This
> > has the potential blind DoS vulnerability, which should be taken
care of
> > by having to match the randomly assigned Session ID]
> 
> I think that the simple comparison scheme is too vulnerable to DoS
> attack even having to match the Session ID.  The attacker can see one
> packet to obtain the Session ID and sequence number and later on it
> can blindly inject a bogus message with the expected Session ID and an
> expected sequence number at about 50% probability.  

This is a possible threat when:
[a]- the adversary can snoop traffic long enough to catch one packet,
but not always (if it could always snoop, not even having rseq helps as
the adversary can synchronize on both rseq/tseq all the time).
[b]- The adversary does not want to immediately launch an attack. (but
it better be before the PANA SA is established).

I'm not sure how feasible condition [a] is, and why an adversary would
want to wait when there is a possibility of missing the chance ([b]).

> This is the reason
> for carrying rseq (receiving sequence number) in the current PANA
> sequence number scheme.
> 
> >
> > Furthermore, in addition to PDI and PER, I think PAR also has
issues.
> 
> Yes, I think so.
> 
> > PAR is not delivered reliably at the PANA layer. So, a single PAR
can be
> > lost, and the EAP-generated retransmission would not have the same
PANA
> > sequence number when transmitted. So, a legitimate gap in sequence
> > number is possible.
> 
> Yes.  I am trying to analyze the effect of allowing the legitimate gap
> in an IKEV2-like sequence number scheme, but I have yet come up with a
> good solution to allow the gap.  A safer solution is to move the
> responsibility of EAP message retransmission from EAP to PANA, but I
> don't have a strong justification for it for now, either.
> 
...

> > >
> > > When a PaC sends a PDI to initiate re-authentication, it carries
the
> > > sequence number 0, but in subsequent PANA message exchange the
> > > previous sequence numbers are inherited according to section 4.4.
> >
> > I didn't think so. I think this part is underspecified in the text.
What
> > would be the logic behind PDI always using 0? I understand the very
> > first PDI, but the subsequent PDIs (which are unicasted btw) could
> > continue the ongoing sequence [given that we don't force
> > request-response with matching sequence numbers on all types of
> > messages].
> 
> I understand it. I think we should not use the 0 sequence number for
> PDI when it is sent for re-authentication (and such a PDI should
> be protected with a MAC AVP when a PANA SA is available.)

Note that PDI is not a request-answer type. It does not have an answer
that can copy the sequence number from PDI either. (If the sequence
number of generated PAR is copied from the PDI, that'd disturb the
sequencing on the PAA). 

Alper




 


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


From pana-bounces@ietf.org  Mon Aug 30 21:09: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 VAA19889
	for <pana-archive@lists.ietf.org>; Mon, 30 Aug 2004 21:09: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 1C1x7P-0003Sd-Sv; Mon, 30 Aug 2004 21:07:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1x2L-0002qn-Uo
	for pana@megatron.ietf.org; Mon, 30 Aug 2004 21:02:14 -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 VAA19421
	for <pana@ietf.org>; Mon, 30 Aug 2004 21:02:11 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1x4D-0005IA-Qj
	for pana@ietf.org; Mon, 30 Aug 2004 21:04:10 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7V129bv025110;
	Tue, 31 Aug 2004 10:02:09 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7V129gh008158;
	Tue, 31 Aug 2004 10:02:09 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	LAA08153 ; Tue, 31 Aug 2004 10:02:09 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id KAA22110; Tue, 31 Aug 2004 10:02:09 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7V128lE025531;
	Tue, 31 Aug 2004 10:02:08 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7V127wE026422;
	Tue, 31 Aug 2004 10:02:07 +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 <0I3A00784DJGD4@tsbpo1.po.toshiba.co.jp>; Tue,
	31 Aug 2004 10:02:06 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C1x27-0006Wn-00; Mon, 30 Aug 2004 18:01:59 -0700
Date: Mon, 30 Aug 2004 21:01:59 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <00cc01c48ef1$2cd0a3f0$291d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040831010159.GH1536@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>,
	'Erik Nordmark' <Erik.Nordmark@sun.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040818i
References: <20040830233238.GG1536@steelhead>
	<00cc01c48ef1$2cd0a3f0$291d9069@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
        "'Erik Nordmark'" <Erik.Nordmark@sun.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, Aug 30, 2004 at 05:26:34PM -0700, Alper Yegin wrote:
> > > Why does it have to determine the next sequence number to receive?
> > > All we care is orderly delivery. And for that, we can simply compare
> if
> > > the new sequence number is greater than or equal to previous one.
> [This
> > > has the potential blind DoS vulnerability, which should be taken
> care of
> > > by having to match the randomly assigned Session ID]
> > 
> > I think that the simple comparison scheme is too vulnerable to DoS
> > attack even having to match the Session ID.  The attacker can see one
> > packet to obtain the Session ID and sequence number and later on it
> > can blindly inject a bogus message with the expected Session ID and an
> > expected sequence number at about 50% probability.  
> 
> This is a possible threat when:
> [a]- the adversary can snoop traffic long enough to catch one packet,
> but not always (if it could always snoop, not even having rseq helps as
> the adversary can synchronize on both rseq/tseq all the time).

The adversary could always snoop traffic long enough to catch one
packet.  The difficulty level of synchronization can be different
depending on the sequence number scheme in use.  With having rseq, the
adversary needs much more effort to synchronize on both rseq/tseq than
on tseq-only (50%).


> [b]- The adversary does not want to immediately launch an attack. (but
> it better be before the PANA SA is established).

In tseq-only solution, the adversary does not have to immediately
compose and transmit a bogus packet, which means that a device with
poor CPU power can easily launch the attack.

> 
> I'm not sure how feasible condition [a] is, and why an adversary would
> want to wait when there is a possibility of missing the chance ([b]).
> 
> > This is the reason
> > for carrying rseq (receiving sequence number) in the current PANA
> > sequence number scheme.
> > 
> > >
> > > Furthermore, in addition to PDI and PER, I think PAR also has
> issues.
> > 
> > Yes, I think so.
> > 
> > > PAR is not delivered reliably at the PANA layer. So, a single PAR
> can be
> > > lost, and the EAP-generated retransmission would not have the same
> PANA
> > > sequence number when transmitted. So, a legitimate gap in sequence
> > > number is possible.
> > 
> > Yes.  I am trying to analyze the effect of allowing the legitimate gap
> > in an IKEV2-like sequence number scheme, but I have yet come up with a
> > good solution to allow the gap.  A safer solution is to move the
> > responsibility of EAP message retransmission from EAP to PANA, but I
> > don't have a strong justification for it for now, either.
> > 
> ...
> 
> > > >
> > > > When a PaC sends a PDI to initiate re-authentication, it carries
> the
> > > > sequence number 0, but in subsequent PANA message exchange the
> > > > previous sequence numbers are inherited according to section 4.4.
> > >
> > > I didn't think so. I think this part is underspecified in the text.
> What
> > > would be the logic behind PDI always using 0? I understand the very
> > > first PDI, but the subsequent PDIs (which are unicasted btw) could
> > > continue the ongoing sequence [given that we don't force
> > > request-response with matching sequence numbers on all types of
> > > messages].
> > 
> > I understand it. I think we should not use the 0 sequence number for
> > PDI when it is sent for re-authentication (and such a PDI should
> > be protected with a MAC AVP when a PANA SA is available.)
> 
> Note that PDI is not a request-answer type. It does not have an answer
> that can copy the sequence number from PDI either. (If the sequence
> number of generated PAR is copied from the PDI, that'd disturb the
> sequencing on the PAA). 

You are right.  Then I think using 0 sequence number for PDI might be
a reasonable solution if we don't define PDI as a request-answer type
message.

Yoshihiro Ohba


> 
> Alper
> 
> 
> 
> 
>  
> 

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


From pana-bounces@ietf.org  Mon Aug 30 22:15: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 WAA23273
	for <pana-archive@lists.ietf.org>; Mon, 30 Aug 2004 22:15: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 1C1y8m-00072r-MI; Mon, 30 Aug 2004 22:12:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1y5E-0006TB-I6
	for pana@megatron.ietf.org; Mon, 30 Aug 2004 22:09:16 -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 WAA22937
	for <pana@ietf.org>; Mon, 30 Aug 2004 22:09:14 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1y77-0006Z6-1Z
	for pana@ietf.org; Mon, 30 Aug 2004 22:11:13 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7V294bv023530;
	Tue, 31 Aug 2004 11:09:04 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7V2942j023404;
	Tue, 31 Aug 2004 11:09:04 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	MAA23402 ; Tue, 31 Aug 2004 11:09:04 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id LAA29007; Tue, 31 Aug 2004 11:09:02 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7V28s3j008974;
	Tue, 31 Aug 2004 11:08:54 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7V28rwE027258;
	Tue, 31 Aug 2004 11:08:53 +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 <0I3A0009JGMQ0U@tsbpo1.po.toshiba.co.jp>; Tue,
	31 Aug 2004 11:08:52 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C1y4Q-0006ww-00; Mon, 30 Aug 2004 19:08:26 -0700
Date: Mon, 30 Aug 2004 22:08:25 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Proposed text for issue 104
In-reply-to: <008401c4894e$06244070$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040831020825.GI1536@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+20040818i
References: <20040919231911.GA22998@steelhead>
	<008401c4894e$06244070$6401a8c0@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
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

I have several comments.  Please see below.

On Mon, Aug 23, 2004 at 01:16:05PM -0700, Alper Yegin wrote:
> 
> Comments welcome.
> 
> 
> [1] Section 2:
> 
> Change:
> 
>  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.
> 
> To:
> 
>  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. 

I guess the last sentence applies to logical network interfaces as
well.

...

> 
> [5] Section 4.1.7:
> 
> Change:
> 
>    o  When a device identifier of the communication peer is bound to the
>       PANA session, it matches the device identifier carried in MAC and/
>       or IP header(s), or other auxiliary indetifier provided by the
>       lower-layers (e.g., circuit ID).
> 
> 
> To:
> 
>    o  When a device identifier of the PaC is bound to the
>       PANA session, it matches the device identifier carried in MAC or
>       or IP header, or other locally-significant identifier provided by 
>       the lower-layers (e.g., circuit ID) unless the message is 
>       a PANA-Update-Request with IP-Address AVP.
> 
> 
> Change:
> 
>    o  When a Device-Id AVP is included, the AVP is valid if the device
>       identifier type contained in the AVP is supported (this check is
>       for both PaC and PAA) and is the requested one (this check is for
>       PAA only) and the device identifier value contained in the AVP
>       matches the value extracted from the lower-layer encapsulation
>       header corresponding to the device identifier type contained in
>       the AVP.  Note that a Device-Id AVP carries the PaC's device
>       identifier in messages from PaC to PAA and PAA's device identifier
>       in messages from PAA to PaC.
> 
> To:
> 
> 
>    o  When a Device-Id AVP is included, the AVP is valid if the device
>       identifier type contained in the AVP is supported (this check is
>       for both PaC and PAA) and is the requested one (this check is for
>       PAA only) and the device identifier value contained in the AVP
>       matches the value extracted from the lower-layer encapsulation
>       header corresponding to the device identifier type contained in
>       the AVP (this check is for PaC only).  Note that a Device-Id AVP

Do you mean "(this check is for PAA only)"?  [I mean this check is for
PAA to validate PaC's device identifier.]

Yoshihiro Ohba


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


From pana-bounces@ietf.org  Mon Aug 30 22:16:58 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 WAA23352
	for <pana-archive@lists.ietf.org>; Mon, 30 Aug 2004 22:16:58 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1y8s-00077M-U0; Mon, 30 Aug 2004 22:13:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1y8U-0006la-7P
	for pana@megatron.ietf.org; Mon, 30 Aug 2004 22:12:38 -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 WAA23108
	for <pana@ietf.org>; Mon, 30 Aug 2004 22:12:35 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1yAM-0006dm-PN
	for pana@ietf.org; Mon, 30 Aug 2004 22:14:35 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7V2CZbv027386;
	Tue, 31 Aug 2004 11:12:35 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7V2CZo4029793;
	Tue, 31 Aug 2004 11:12:35 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	MAA29788 ; Tue, 31 Aug 2004 11:12:35 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id LAA03275; Tue, 31 Aug 2004 11:12:32 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7V2CUMx014227;
	Tue, 31 Aug 2004 11:12:30 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7V2CTwE000680;
	Tue, 31 Aug 2004 11:12:29 +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 <0I3A0001HGSQ9C@tsbpo1.po.toshiba.co.jp>; Tue,
	31 Aug 2004 11:12:28 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C1y7o-0006yb-00; Mon, 30 Aug 2004 19:11:56 -0700
Date: Mon, 30 Aug 2004 22:11:56 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
In-reply-to: <003001c48eb9$8b636f20$291d9069@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040831021156.GJ1536@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+20040818i
References: <027001c48c72$79dd1970$6401a8c0@sisa.samsung.com>
	<003001c48eb9$8b636f20$291d9069@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fcb459c204557d9509ce9c1b55d771f1
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, pana@ietf.org
Subject: [Pana] Re: Issue 105 - take 3
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 is now available in snapshot -06a.

Regards,

Yoshihiro Ohba

On Mon, Aug 30, 2004 at 10:48:20AM -0700, Alper Yegin wrote:
> 
> Fixed the problem in [4]...
> 
>   
> 
> [1] In Section 3:
> 
> 
> Change:
> 
>    In addition, PANA defines the following two types of
>    re-authentication procedures that are performed while an established
>    PANA session exists.
> 
>    1.  Re-authentication based on EAP
> 
>    2.  Re-authentication based on PANA-Reauth exchange
> 
>    The former type of re-authentication is used mainly for extending
>    authorization lifetime or for updating the cryptographic keying
>    material of a PANA SA.  The latter type of re-authentication is used
>    mainly for maintaining the presence of the communicating peers each
>    other so that the established PANA session can be terminated as soon
>    as the presence of the peer is lost.
> 
> To:
> 
>    In addition, PANA allows re-authentication of the PaC and PAA by
>    allowing any one of them to initiate an EAP authentication during
>    an on-going PANA session. Refreshing the session and cryptographic
>    keys are possible reasons to engage in re-authentication.
> 
>    Finally, the protocol enables PAA and PaC ping each other to test 
>    liveness of the session. 
> 
> 
> [2] In Section 3.1:
> 
> Change:
> 
>   o  Re-authentication based on the PANA-Reauth-Request/ PANA-Reauth
>       exchange is performed.
> 
> To:
> 
>   o  Liveness test based on the PANA-Ping-Request/PANA-Ping-Answer
>       exchange is performed.
> 
> 
> Change:
> 
>  // Re-authentication based on PANA-Reauth exchange
>          <-----     PANA-Reauth-Request[Session-Id, MAC]
>          ----->     PANA-Reauth-Answer[Session-Id, MAC]
> 
> To:
> 
>  // Liveness test based on PANA-Ping exchange
>          <-----     PANA-Ping-Request[Session-Id, MAC]
>          ----->     PANA-Ping-Answer[Session-Id, MAC]
> 
> 
> 
> [3] In Section 4.1.7:
> 
> Updated text: 
> 
>    o  The message type is one of the expected types in the current
>       state.  Specifically the following messages are unexpected and
>       invalid:
> 
>       *  In discovery and initial handshake phase:
> 
>          +  PANA-Termination-Request and PANA-Ping-Request.
> 
>          +  PANA-Bind-Request.
> 
>          +  PANA-Update-Request.
> 
>       *  In authentication phase:
> 
>          +  PANA-PAA-Discover.
> 
>          +  PANA-Update-Request.
> 
>          +  PANA-Start-Request after the PaC receives the first valid
>             PANA-Auth-Request.
> 
>          +  PANA-Termination-Request before the PaC receives the first
>             successful PANA-Bind-Request.
> 
>       *  After successful PANA authentication:
> 
>          +  PANA-Start-Request as well as a non-duplicate
>             PANA-Bind-Request (see section Section 4.7 for definition of
>             duplicate requests).
> 
>          +  PANA-PAA-Discover without a Session-Id AVP.
> 
>       *  In termination phase:
> 
>          +  PANA-PAA-Discover.
> 
>          +  All requests but PANA-Termination-Request.
> 
> 
> [4] New text for Section 4.4:
> 
> 4.4  Re-authentication
> 
>    An already established PANA session can enter an authentication 
>    phase by re-executing EAP. In this case, some or all message
> exchanges
>    for discovery and initial handshake phase MAY be omitted in the
>    following way.  When a PaC wants to initiate re-authentication, 
>    it sends a unicast PANA-PAA-Discovery message to
>    the PAA.  This message MUST contain a Session-Id AVP which is used
>    for identifying the PANA session on the PAA.  If the PAA already has
>    an established PANA session for the PaC with the matching identifier,
>    it sends a PANA-Auth-Request message containing the same identifier
>    to start an authentication phase.  If the PAA can not recognize the
>    session identifier, it proceeds with regular authentication by
>    sending back PANA-Start-Request. When the PAA initiates
>    re-authentication, it sends a PANA-Auth-Request message containing
>    the session identifier for the PaC to enter an authentication phase.
>    PAA SHOULD initiate EAP authentication before the current session
>    lifetime expires.  In both cases, the tseq and rseq values are
>    inherited from the previous (re-)authentication.  For any
>    re-authentication, if there is an established PANA SA,
>    PANA-Auth-Request and PANA-Auth-Answer messages MUST be protected by
>    adding a MAC AVP to each message.  Any subsequent EAP-based
>    authentication MUST be performed with the same ISP and NAP that was
>    selected during the initial authentication.  An example sequence for
>    a re-authentication initiated by a PaC is shown in Figure
>    6.
> 
>       PaC      PAA  Message
>       ------------------------------------------------------
>          ----->     PANA-PAA-Discover(0,0)[Session-Id]
>          <-----     PANA-Auth-Request(p,q)[Session-Id, EAP, MAC]
>          ----->     PANA-Auth-Answer(q+1,p)[Session-Id, EAP, MAC]
>          <-----     PANA-Auth-Request(p+1,q+1)[Session-Id, EAP, MAC]
>          ----->     PANA-Auth-Answer(q+2,p+1)[Session-Id, EAP, MAC]
>          <-----     PANA-Bind-Request(p+2,q+2)
>                        [Session-Id, EAP{Success}, Device-Id, Key-Id,
>                         Lifetime, Protection-Cap., PPAC, MAC]
>          ----->     PANA-Bind-Answer(q+3,p+2)
>                        [Session-Id, Device-Id, Key-Id, PPAC, MAC]
> 
>   Figure 6: Example Sequence for EAP-based re-authentication initiated
>                                  by PaC
> 
> 
> [5] Create a new section after the current Section 4.4
> 
> 4.5. Liveness Test
>  
>    PANA-Ping-Request and PANA-Ping-Answer messages are used for testing
>    the liveness of the PANA session on the PANA peer. If there is an 
>    established PANA session, both the PaC and
>    the PAA are allowed to send a PANA-Ping-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-Ping-Answer message.  Both PANA-Ping-Request and
>    PANA-Ping-Answer messages MUST be protected with a MAC AVP when a
>    PANA SA is available.
> 
>    Implementations MUST limit the rate of performing this test.  
>    The PaC and the PAA can handle
>    rate limitation on their own, they do not have to perform any
>    coordination with each other.  There is no negotiation of timers for
>    this purpose.
> 
>    Figure 7 and Figure 8 illustrate liveness tests as they are initiated
>    by the PaC and the PAA respectively.
> 
> 
>       PaC      PAA     Message(tseq,rseq)[AVPs]
>       ------------------------------------------------------
>          ----->        PANA-Ping-Request(q,p)[Session-Id, MAC]
>          <-----        PANA-Ping-Answer(p+1,q)[Session-Id, MAC]
> 
> 
>         Figure 7: Example Sequence for PaC-initiated liveness test
> 
> 
>       PaC      PAA     Message(tseq,rseq)[AVPs]
>       ------------------------------------------------------
>          <-----        PANA-Ping-Request(p,q)[Session-Id, MAC]
>          ----->        PANA-Ping-Answer(q+1,p)[Session-Id, MAC]
> 
> 
>         Figure 8: Example Sequence for PAA-initiated liveness test
> 
> 
> [6] In section 4.6:
> 
> Remove:
> 
>   o  Re-authentication based on the PANA-Reauth exchange is performed.
> 
> 
> [7] In Section 4.10:
> 
> Change:
> 
>    PANA peer can use PANA-Reauth-Request message to
>    verify the disconnection before taking an action.
> 
>    The session lifetime parameter is not related to the transmission of
>    PANA-Reauth-Request messages.  These messages can be used for
>    asynchronously verifying the liveness of the peer and enabling
>    mobility optimizations.  The decision to send PANA-Reauth-Request
>    message is taken locally and does not require coordination between
>    the peers.
> 
> To:
> 
>    PANA peer can use PANA-Ping-Request message to
>    verify the disconnection before taking an action.
> 
>    The session lifetime parameter is not related to the transmission of
>    PANA-Ping-Request messages.  These messages can be used for
>    asynchronously verifying the liveness of the peer.  The decision 
>    to send PANA-Ping-Request message is taken locally and does not 
>    require coordination between the peers.
> 
> 
> [8] In Section 6.4:
> 
> Change:
> 
>                  PANA-Reauth-Request         <------->
>                  PANA-Reauth-Answer          <------->
> 
> To:
> 
>                  PANA-Ping-Request           <------->
>                  PANA-Ping-Answer            <------->
> 
> [9] New text for Section 6.4.9 and 6.4.10:
> 
> 6.4.9  PANA-Ping-Request (PPR)
> 
>    PANA-Ping-Request (PPR) is either sent by the PaC or the PAA.
> 
>          PANA-Ping-Request ::= < PANA-Header: 5, REQ >
>                        < Session-Id >
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> 
> 6.4.10  PANA-Ping-Answer (PPA)
> 
>    PANA-Ping-Answer (PPA) is sent in response to a
>    PANA-Ping-Request.
> 
>          PANA-Ping-Answer ::= < PANA-Header: 5 >
>                        < Session-Id >
>                     *  [ AVP ]
>                    0*1 < MAC >
> 
> [10] In Section 6.6:
> 
> Change:
> 
>  Attribute Name      | PRAR | PRAA | PTR | PTA | PER | PFER | PFEA |
> 
> To:
> 
>  Attribute Name      | PPR  | PPA  | PTR | PTA | PER | PFER | PFEA |
> 
> 
> 
> [11] In Section 7:
> 
> Change:
> 
>          PANA-Reauth-Request (PRAR)
> 
> To:
> 
>          PANA-Ping-Request (PPR)
> 
> 
> Change:
> 
>    The last two messages, PRAR and PTR are sent either by PaC or
>    PAA.
> 
> To:
> 
>    The last two messages, PPR and PTR are sent either by PaC or
>    PAA.
> 
> 
> [12] In Section 9.g:
> 
> 
> Change:
> 
>    A disconnect may also be detected earlier by using PANA
>    reauthentication messages.
> 
> To:
> 
>    A disconnect may also be detected earlier by using PANA
>    ping messages.
> 
> 
> 
> 

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


From pana-bounces@ietf.org  Mon Aug 30 22:19:54 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 WAA23536
	for <pana-archive@lists.ietf.org>; Mon, 30 Aug 2004 22:19:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C1yDR-0008Ni-A3; Mon, 30 Aug 2004 22:17:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C1yAG-0007Py-DI
	for pana@megatron.ietf.org; Mon, 30 Aug 2004 22:14:28 -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 WAA23232
	for <pana@ietf.org>; Mon, 30 Aug 2004 22:14:26 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C1yC8-0006fw-9H
	for pana@ietf.org; Mon, 30 Aug 2004 22:16:25 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7V2EPbv028899
	for <pana@ietf.org>; Tue, 31 Aug 2004 11:14:25 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7V2EOGx002255
	for <pana@ietf.org>; Tue, 31 Aug 2004 11:14:24 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	MAA02250 ; Tue, 31 Aug 2004 11:14:24 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id LAA04800; Tue, 31 Aug 2004 11:14:10 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7V2E1jK016126;
	Tue, 31 Aug 2004 11:14:01 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7V2E1wE001955
	for <pana@ietf.org>; Tue, 31 Aug 2004 11:14:01 +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 <0I3A00041GVA9C@tsbpo1.po.toshiba.co.jp> for
	pana@ietf.org; Tue, 31 Aug 2004 11:14:00 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C1y8s-0006zb-00 for <pana@ietf.org>; Mon, 30 Aug 2004 19:13:02 -0700
Date: Mon, 30 Aug 2004 22:13:02 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20040831021302.GK1536@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+20040818i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574
Subject: [Pana] pana specification snapshot (06a)
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

is now available at http://www.toshiba.com/tari/pana/pana-spec.html.

Yoshihiro Ohba

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


From pana-bounces@ietf.org  Tue Aug 31 00:57:33 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 AAA04408
	for <pana-archive@lists.ietf.org>; Tue, 31 Aug 2004 00:57:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C20ds-0003Iu-I6; Tue, 31 Aug 2004 00:53:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C20Zi-0002Ij-K1
	for pana@megatron.ietf.org; Tue, 31 Aug 2004 00:48:55 -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 AAA04080
	for <pana@ietf.org>; Tue, 31 Aug 2004 00:48:50 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C20bZ-0001X9-HQ
	for pana@ietf.org; Tue, 31 Aug 2004 00:50:53 -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 <0I3A005JTO0DKE@mailout3.samsung.com> for pana@ietf.org; Tue,
	31 Aug 2004 13:48:13 +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 <0I3A005OWNZQRE@mailout3.samsung.com> for pana@ietf.org;
	Tue, 31 Aug 2004 13:47:51 +0900 (KST)
Received: from Alperyegin ([105.253.155.19])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I3A00FB2NZMT4@mmp2.samsung.com> for
	pana@ietf.org; Tue, 31 Aug 2004 13:47:50 +0900 (KST)
Date: Mon, 30 Aug 2004 21:47:43 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040831010159.GH1536@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <000001c48f15$aa044bf0$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7BIT
Cc: "'Erik Nordmark'" <Erik.Nordmark@sun.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

> > This is a possible threat when:
> > [a]- the adversary can snoop traffic long enough to catch one
packet,
> > but not always (if it could always snoop, not even having rseq helps
as
> > the adversary can synchronize on both rseq/tseq all the time).
> 
> The adversary could always snoop traffic long enough to catch one
> packet.  The difficulty level of synchronization can be different
> depending on the sequence number scheme in use.  With having rseq, the
> adversary needs much more effort to synchronize on both rseq/tseq than
> on tseq-only (50%).

If the adversary can snoop one packet and decides to launch the attack
immediately, I don't see any difference between having to deal with two
sequence numbers vs. one. If it captures (tseq, rseq), it will just
spoof (rseq+1, tseq) in the reverse direction with some appropriate
payload.


> > [b]- The adversary does not want to immediately launch an attack.
(but
> > it better be before the PANA SA is established).
> 
> In tseq-only solution, the adversary does not have to immediately
> compose and transmit a bogus packet, which means that a device with
> poor CPU power can easily launch the attack.

If the adversary is not fast enough to compose the immediate next packet
before the legitimate peer does, why not try to compose couple packets
later and cache it. And when the time comes (detected by snooping) just
transmit the canned packet. 

...

> >
> > Note that PDI is not a request-answer type. It does not have an
answer
> > that can copy the sequence number from PDI either. (If the sequence
> > number of generated PAR is copied from the PDI, that'd disturb the
> > sequencing on the PAA).
> 
> You are right.  Then I think using 0 sequence number for PDI might be
> a reasonable solution if we don't define PDI as a request-answer type
> message.

Or, if we don't require each non-response message to be treated as a
request and expect a response (with matching seq. no), then PDI can
continue the on-going sequence numbering. 

...

I'm still failing to see the seriousness of the DoS issue. But
nevertheless, if you have a low-cost solution, we should use it. 

[just to make sure we are on the same page, the current direction is:
- only one seq no is included in each message, but each peer has its own
seq no for the non-answer messages it generates.
- answers copy the seq no from the requests.

The issue is:
- There are messages that do not (or may not) generate "answers", such
as PDI, PER, and PAR. 
]

Alper



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


From pana-bounces@ietf.org  Tue Aug 31 00:59: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 AAA04506
	for <pana-archive@lists.ietf.org>; Tue, 31 Aug 2004 00:59: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 1C20gN-0003yY-1I; Tue, 31 Aug 2004 00:55:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C20cb-00032y-Sk
	for pana@megatron.ietf.org; Tue, 31 Aug 2004 00:51:53 -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 AAA04218
	for <pana@ietf.org>; Tue, 31 Aug 2004 00:51:50 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C20eW-0001aP-Bj
	for pana@ietf.org; Tue, 31 Aug 2004 00:53: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 <0I3A00FDIO5LOQ@mailout2.samsung.com> for pana@ietf.org; Tue,
	31 Aug 2004 13:51:21 +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 <0I3A00712O49I8@mailout2.samsung.com> for pana@ietf.org;
	Tue, 31 Aug 2004 13:50:34 +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 <0I3A009DGO449N@mmp1.samsung.com> for
	pana@ietf.org; Tue, 31 Aug 2004 13:50:33 +0900 (KST)
Date: Mon, 30 Aug 2004 21:50:26 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <20040831010159.GH1536@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <000001c48f16$0b26a130$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7BIT
Cc: "'Erik Nordmark'" <Erik.Nordmark@sun.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

> > This is a possible threat when:
> > [a]- the adversary can snoop traffic long enough to catch one
packet,
> > but not always (if it could always snoop, not even having rseq helps
as
> > the adversary can synchronize on both rseq/tseq all the time).
> 
> The adversary could always snoop traffic long enough to catch one
> packet.  The difficulty level of synchronization can be different
> depending on the sequence number scheme in use.  With having rseq, the
> adversary needs much more effort to synchronize on both rseq/tseq than
> on tseq-only (50%).

If the adversary can snoop one packet and decides to launch the attack
immediately, I don't see any difference between having to deal with two
sequence numbers vs. one. If it captures (tseq, rseq), it will just
spoof (rseq+1, tseq) in the reverse direction with some appropriate
payload.


> > [b]- The adversary does not want to immediately launch an attack.
(but
> > it better be before the PANA SA is established).
> 
> In tseq-only solution, the adversary does not have to immediately
> compose and transmit a bogus packet, which means that a device with
> poor CPU power can easily launch the attack.

If the adversary is not fast enough to compose the immediate next packet
before the legitimate peer does, why not try to compose couple packets
later and cache it. And when the time comes (detected by snooping) just
transmit the canned packet. 

...

> >
> > Note that PDI is not a request-answer type. It does not have an
answer
> > that can copy the sequence number from PDI either. (If the sequence
> > number of generated PAR is copied from the PDI, that'd disturb the
> > sequencing on the PAA).
> 
> You are right.  Then I think using 0 sequence number for PDI might be
> a reasonable solution if we don't define PDI as a request-answer type
> message.

Or, if we don't require each non-response message to be treated as a
request and expect a response (with matching seq. no), then PDI can
continue the on-going sequence numbering. 

...

I'm still failing to see the seriousness of the DoS issue. But
nevertheless, if you have a low-cost solution, we should use it. 

[just to make sure we are on the same page, the current direction is:
- only one seq no is included in each message, but each peer has its own
seq no for the non-answer messages it generates.
- answers copy the seq no from the requests.

The issue is:
- There are messages that do not (or may not) generate "answers", such
as PDI, PER, and PAR. 
]

Alper



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


From pana-bounces@ietf.org  Tue Aug 31 09:28: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 JAA16911
	for <pana-archive@lists.ietf.org>; Tue, 31 Aug 2004 09:28: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 1C28dU-0001tn-Ph; Tue, 31 Aug 2004 09:25:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C28WM-0006fX-SA
	for pana@megatron.ietf.org; Tue, 31 Aug 2004 09:17:59 -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 JAA16249
	for <pana@ietf.org>; Tue, 31 Aug 2004 09:17:55 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C28YH-0003Cc-4r
	for pana@ietf.org; Tue, 31 Aug 2004 09:19:59 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i7VDHnbv020843;
	Tue, 31 Aug 2004 22:17:49 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i7VDHnND020832;
	Tue, 31 Aug 2004 22:17:49 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	YAA20824 ; Tue, 31 Aug 2004 22:17:49 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA10239; Tue, 31 Aug 2004 22:17:48 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i7VDHmxT028048;
	Tue, 31 Aug 2004 22:17:48 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i7VDHlwE025645;
	Tue, 31 Aug 2004 22:17:47 +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 <0I3B006DYBLK31@tsbpo1.po.toshiba.co.jp>; Tue,
	31 Aug 2004 22:17:46 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1C28Vp-0007SN-00; Tue, 31 Aug 2004 06:17:25 -0700
Date: Tue, 31 Aug 2004 09:17:25 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 105: Inconsistent and unclear usage of "reauth"
	messages
In-reply-to: <000001c48f15$aa044bf0$6401a8c0@sisa.samsung.com>
To: Alper Yegin <alper.yegin@samsung.com>
Message-id: <20040831131725.GA27140@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>,
	'Erik Nordmark' <Erik.Nordmark@sun.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040818i
References: <20040831010159.GH1536@steelhead>
	<000001c48f15$aa044bf0$6401a8c0@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
        "'Erik Nordmark'" <Erik.Nordmark@sun.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, Aug 30, 2004 at 09:47:43PM -0700, Alper Yegin wrote:
> > > This is a possible threat when:
> > > [a]- the adversary can snoop traffic long enough to catch one
> packet,
> > > but not always (if it could always snoop, not even having rseq helps
> as
> > > the adversary can synchronize on both rseq/tseq all the time).
> > 
> > The adversary could always snoop traffic long enough to catch one
> > packet.  The difficulty level of synchronization can be different
> > depending on the sequence number scheme in use.  With having rseq, the
> > adversary needs much more effort to synchronize on both rseq/tseq than
> > on tseq-only (50%).
> 
> If the adversary can snoop one packet and decides to launch the attack
> immediately, I don't see any difference between having to deal with two
> sequence numbers vs. one. If it captures (tseq, rseq), it will just
> spoof (rseq+1, tseq) in the reverse direction with some appropriate
> payload.

Yes, that is true with the "snoop and immediate launch" condition.

> 
> 
> > > [b]- The adversary does not want to immediately launch an attack.
> (but
> > > it better be before the PANA SA is established).
> > 
> > In tseq-only solution, the adversary does not have to immediately
> > compose and transmit a bogus packet, which means that a device with
> > poor CPU power can easily launch the attack.
> 
> If the adversary is not fast enough to compose the immediate next packet
> before the legitimate peer does, why not try to compose couple packets
> later and cache it. And when the time comes (detected by snooping) just
> transmit the canned packet. 

To make that attack succeed in tseq-rseq scheme, the adversary still
need to immediately transmit the pre-composed packet with snooping the
latest conversation and do it before the legitimate peer can send
another packet.  I would say that not all cheap devices can be fast
enough to do that, and there is a difference in the difficulty levels
of synchronization between tseq-only scheme and tseq-rseq scheme.  To
me this is not a small difference and I have been consistent on this
point since the initial design phase.  I would feel more comfortable
with a reliable protocol that has notion of sequence number window
when an IKEv2-like sequence number scheme is used.

> 
> ...
> 
> > >
> > > Note that PDI is not a request-answer type. It does not have an
> answer
> > > that can copy the sequence number from PDI either. (If the sequence
> > > number of generated PAR is copied from the PDI, that'd disturb the
> > > sequencing on the PAA).
> > 
> > You are right.  Then I think using 0 sequence number for PDI might be
> > a reasonable solution if we don't define PDI as a request-answer type
> > message.
> 
> Or, if we don't require each non-response message to be treated as a
> request and expect a response (with matching seq. no), then PDI can
> continue the on-going sequence numbering. 
> 
> ...
> 
> I'm still failing to see the seriousness of the DoS issue. But
> nevertheless, if you have a low-cost solution, we should use it. 

Please see my comment above.

> 
> [just to make sure we are on the same page, the current direction is:
> - only one seq no is included in each message, but each peer has its own
> seq no for the non-answer messages it generates.
> - answers copy the seq no from the requests.
> 
> The issue is:
> - There are messages that do not (or may not) generate "answers", such
> as PDI, PER, and PAR. 
> ]

Yes, I am on that direction.

Yoshihiro Ohba


> 
> Alper
> 
> 

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


From pana-bounces@ietf.org  Tue Aug 31 13:18:10 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 NAA06571
	for <pana-archive@lists.ietf.org>; Tue, 31 Aug 2004 13:18:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C2C0y-0002Y1-8d; Tue, 31 Aug 2004 13:01:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C2BmU-0006w8-2R
	for pana@megatron.ietf.org; Tue, 31 Aug 2004 12:46:50 -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 MAA03828
	for <pana@ietf.org>; Tue, 31 Aug 2004 12:46:47 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from mgw-x3.nokia.com ([131.228.20.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2BoR-00009Y-Kp
	for pana@ietf.org; Tue, 31 Aug 2004 12:48:52 -0400
Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])
	by mgw-x3.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i7VGkiS18855
	for <pana@ietf.org>; Tue, 31 Aug 2004 19:46:44 +0300 (EET DST)
X-Scanned: Tue, 31 Aug 2004 19:46:31 +0300 Nokia Message Protector V1.3.31
	2004060815 - RELEASE
Received: (from root@localhost)
	by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i7VGkVP2017853
	for <pana@ietf.org>; Tue, 31 Aug 2004 19:46:31 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96)
	by esdks002.ntc.nokia.com 00oTDZDf; Tue, 31 Aug 2004 19:46:30 EEST
Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com
	[10.241.35.121])
	by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id
	i7VGkTY04846
	for <pana@ietf.org>; Tue, 31 Aug 2004 19:46:29 +0300 (EET DST)
Received: from daebe007.NOE.Nokia.com ([10.241.35.107]) by
	daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); 
	Tue, 31 Aug 2004 11:45:43 -0500
x-mimeole: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 31 Aug 2004 11:45:41 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF4403B1BCC9@daebe007.americas.nokia.com>
Thread-Topic: Draft minutes of PANA WG meeting at IETF60
Thread-Index: AcSPefLcqDCLTj+bT8eztqaRV/gtPA==
To: <pana@ietf.org>
X-OriginalArrivalTime: 31 Aug 2004 16:45:43.0995 (UTC)
	FILETIME=[F52628B0:01C48F79]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: f6ef73100908d67495ce675c3fe8f472
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] Draft minutes of PANA WG meeting at IETF60
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



Protocol for Carrying Authentication for Network Access WG (pana)

August 4th, 2004 Wednesday; 1300-1500
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Thanks to Subir Das and Mohan Parthasarathy for volunteering to take
the meeting minutes.

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

1. Preliminaries (bluesheets, minute takers, agenda bashing, document
   status) : 5 min, Chairs

- Chairs mentioned that charter has been updated
- Requirements and threats drafts are ready for last call
- The usage scenarios I-D has been deprectaed. The scenarios are now
  included as an appendix in the Requirements I-D
- Received Expert reviews for pana protocol, pana framework, pana
  Ipsec draft.=20
- pana snmp needs more reviews.

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

2. PANA protocol update and open issues: 30 min, Alper Yegin
   Discussion of recently closed and currently open issues on=20
   draft-ietf-pana-pana-05.txt. See "Change History" section of the=20
   draft for the list of issues closed in this revision. Additional=20
   issues may be discussed on the mailing list prior to the meeting.=20
   Detailed issue descriptions can be found at=20
   http://danforsberg.info:8080/pana-issues/=20

Alper presented the update and issues, Expert reviews have been
received. Several issues are resolved and some are still open=20
Issues resolved:=20
     -  Issue 71, Post-PANA address AVP=20
        Resolution: No config, DHCP, RFC2462 etc=20
     -  Issue 72: Capability discovery is not accomplished=20
        Resolution: PSR now includes PPAC and protection Capability AVP=20
     -  Issue 73: What type of DI will be used on DSL networks?=20
	Resolution: Locally significant identifiers are ok=20
	DI does not have to be carried in an AVP.=20

Mohan: Is DI carried by the packet
Alper: Yes, it can be carried by the packet=20

     - Issue 74: Using PRAR and PRAA for mobility feature. We can use
       PBR and PBA instead=20
       Resolution: Use PBR/PBA instead=20
Yoshihiro: May be it is related to other issue. For mobility, we can
	   change the DI =20
Alper: There is no text that conflicts your assertion=20
Mohan: Is it optional?
Alper: you can use as is. However the question is interface switching=20
     -  Issue 78: EAP pass-through =20

     - Issue 79: Should PANA  support the case where EAP
       authentication  succeeds?=20
       Resolution: PBR results codes: PANA_SUCCESS=20

     - Issue 85: If PRPA is replaced by POPA, PAA needs to be notified=20
       Resolution: PaC sends PANA-Update-Request with IP-address AVP=20

Sidefix: PANA-reauth MUST include MAC AVP only when PANA SA is available =


     - Issue 98: PANA answers may be lsot. PaC/PAA should b eready to
       respond to retransmitted requests=20
       Resolution: PANA-auth-req responses are driven by EAP
       May respond to duplicate PANA-termination-req
       Section 4.7 and 4.11 are duplicates=20

     - Issue 100: Due to retransmissions  and window of acceptable
     seq. numbers, ISN_* on PAA and PaC may differ. ISNs are used in
     PANA-MAC_key computation =20
     Resolution: Carry nonce values in PSR and PSA
     Use nonce values instead of nonce=20

     - Issue 107: Current seq no scheme does not accommodate rexmited =
rseq
     PaC drops msg 3 because "y" was already acknowledges

Issue 75, 76, 77, 80,83, 84,91,92,93,96,97,99,103 are mostly editorial
and clarification. Excpet 97 which are still open for further inputs. =20

Next steps: Fix the open issues, Publish.

Lionel: Is there any plan to have the distinction of different errors.=20

Alper: Currently we have some messages. But I don't know whether they
distinguish it or not =20

Raj: Do you want to change the state machine behaviour depending upon
the error message =20

Lionel: Something like that but not to change the state machine=20
Alper: It is hard to specifiy it=20
Raj: He has a valid point since client may take some other steps
depending upon partial information =20
Alper: If PaC receives failure, PaC is out of PANA and it is an
architectural decision =20
Ra: It seems that issue 79 does not resolve the complete scenario
and may be we should look it again.

Resolution: Relax the expected rseq window to allow rexmot of seq

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

3. PANA framework update and open issues: 5 min, Yoshihiro Ohba
   Discussion of recently closed and currently open issues on=20
   draft-ietf-pana-framework-01.txt.=20

- Issue: AP hopping was needed when PAA and AP(EP) are separated=20
  Resolution: Text for AP hopping was removed=20
  A single solution for both co-located and separated PAA-EP cases
  Misc fix: Added explicit text that IEEE802.11i 4-Way handshake by AP
- Issue: Simplifying DSL section:=20
  CPE acting as router (Router mode)
  CPE acting as a NATPT=20
  Resolution: Two modes can be combined=20
- Issue: Revising Introduction section=20
  Missing info on overview and other documents=20
  Resolution: Introduction section will be revised and other document
  references will be added  =20

Next step: WG last call?=20

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

4. SNMP usage for PAA-2-EP interface: 5 min, Yacine El Mghazli
   Discussion of recently closed and currently open issues on=20
   draft-ietf-pana-snmp-01.txt.

Yacine: PANA Wg mandates SNMP for PAA-EP=20
In last IETF this was accepted as WG item=20

IPSec config MIP splitted into 3 separate modules:
	Reuse of existing IPSEc configuration MIBs IP level access control
	Rule/Filter/action policy structure MIB module=20
ID-KEY_ID config=20
IpSEc IKE config

PANA-secific objects extends the SPD-MIB=20
	L2 filters=20
L2 protection=20

Changes in this draft:=20
Terminology section updated=20
PAA/EP separation context section=20
Feedback on SNMPv3:=20
-A MIB doctor to act as a technical advisor for the PANA WG?=20
- Careful use of SNMP terminology=20

Raj: Generally for new MIB, we use MIB doctor and that's the IETF =
practice=20
Yacine: Yes I agree=20

Security issue: New PaC notification could lead to DoS attacks on the =
PAA.

Alper: With SNMPv3, PAA=20

Attack not clear...

Alper: Attack pretty common...might be a general=20

Open issues:

- link layer filters: Do we support everything ? 802, DSL, What more ?
- L2 protection : Some additional objects needed ?

Alper: No need for enumerate all link layers. Define generic container.

Yacine: Use existing objects to configure EP. Some are lacking..

Security: Details the use of snmpv3 security.
	  Depends on MIB objects definition.

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

5. PANA-IPsec I-D update and open issues: 5 min, Mohan Parthasarathy
   Discussion of recently closed and currently open issues on=20
   draft-ietf-pana-ipsec-03.txt.=20

Mohan:  Version 03 updates
Clarification of Key-ID in IKE pre-shared key derivation for
reauthentication case =20
Address Config has been simplified=20
- Pre-PANA address can be link local
Double IPsc section has been removed=20
Dual stack operation section has been added=20
How is IKE pre-shared key derived ahen there are multriple
authentication schemes =20
Raj: Is the document ready for last call?
Mohan: Yes I think so. But is there are expert review pending?
=20
**********************************

6. PANA state machine: 20 min, Victor Fajardo
   New I-D presentation for draft-ohba-pana-statemachine-00.txt.

Victor: This is included in PANA base protocol documents=20
Important in implementation=20
- gives PANA internal details=20
- insights of  PANA=20
PaC State Diagram overview has been presented. The intention is to
show the difference with the previous presentation. The main
differences is the introduction of EAP Interaction states. More
details are available on the web site. In PAA state diagram the main
difference are EAP interaction and result indication states. Also
included issue 7 and 8. =20
Details retransmissions descriptions are also available.=20
Next Steps: Want to get the feedback from other implementers,
verification of state machine =20
Accommodate EP interface=20
Raj: This document is a result from the protocol document. Because of
the details, we decided to put it in a separate document and next
steps should be to proceed with this since the State machine is very
valuable.=20

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

7. Context transfer for PANA: 20 min, Julien Bournelle
   New I-D presentation for draft-bournelle-pana-ctp-00.txt.
Julien: Problem: Reauthentication from scratch ahen it moves to new
   PAA and that's hwy we need CTP (context transfer). The base PANA
   draft mentions that we need CTP for supporting mobility. =20
Two cases were discussed: Reactive and predictive:=20
Various uses were discussed: for example, CTP mentions use of CTAR
   message to trigger the transfer=20
- seems necessary in predictive case
Who enables the transfer?
	 In CTP: MN and pAR shares a key. The pAR validate an
   authentication token=20
-if PAA: can we still talk about CTP?

ALper: Answering the 2nd question: it is the inclusion of session
ID. Unless CTP does not mandate in CTAR format, it should be fine=20
Raj: Session ID is not enough for CTP transfer
Julien: Can we do that?=20
Gerado: in CTP, CTAR is always required?=20

Raj: We need to consider how do we do CTP? I agree that it may be
necessary=20

Gerado: CTP in Seamoby is not useful here.=20
=20
Vijay: Triggers should not be given by PANA

Hannes: Mobility protocols should give the trigger=20

Alper: If you know what to transfer, that's fine.=20

Raj: CTP is protocol=20

Raj: We should discuss in mailing list or offline.=20

Issue: Do we need to introduce new state in state machine=20

PAAs are not ARs (CTP mentions ARs)=20
=20
Should we handle inter-domain scenario?=20

Vijay: If PAA is AR then 2nd point does not apply

Alper: Regarding the state machine can we accommodate this?

Yoshi: In case of mobility optimization, pAA is alwys stateful=20
Hannes: Regarding the last bullet, for domain handover we need to
consider something more and not beeen discussed in seamoby since
multipartes are involved. =20

Alper: Is it a protocol issue or operational issue=20

Hannes: No it may be a protocol issue=20

Raj: I don't know how important is to consider CTP here in context of =
PANA protocol and tight schedule=20

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

8. Next steps: 5 min, Chairs=20

We need to do the WG last call with requirements and threats with next
few weeks =20

Proceed to WG last call on=20
Pana protocol, pana framework=20

SNMP draft is not ready for WG last call. Chairs will find MIB doctor
for this. =20



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


From pana-bounces@ietf.org  Tue Aug 31 16:08: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 QAA25051
	for <pana-archive@lists.ietf.org>; Tue, 31 Aug 2004 16:08: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 1C2ESh-0001iH-Vc; Tue, 31 Aug 2004 15:38:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1C2ELv-0006kZ-1e; Tue, 31 Aug 2004 15:31:35 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20084;
	Tue, 31 Aug 2004 15:31:33 -0400 (EDT)
Message-Id: <200408311931.PAA20084@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, 31 Aug 2004 15:31:33 -0400
Cc: pana@ietf.org
Subject: [Pana] I-D ACTION:draft-ietf-pana-requirements-09.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)Requirements
	Author(s)	: A. Yegin, et al.
	Filename	: draft-ietf-pana-requirements-09.txt
	Pages		: 24
	Date		: 2004-8-31
	
It is expected that future IP devices will have a variety of access 
technologies to gain network connectivity. Currently there are 
access-specific mechanisms for providing client information to the 
network for authentication and authorization purposes. In addition 
to being limited to specific access media (e.g., 802.1X for IEEE 802 
links), some of these protocols are limited to specific network 
topologies (e.g., PPP for point-to-point links). The goal of this 
document is to identify the requirements for a link-layer agnostic 
protocol that allows a host and a network to authenticate each other 
for network access. This protocol will run between a client's device 
and an agent in the network where the agent might be a client of the 
AAA infrastructure.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pana-requirements-09.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-requirements-09.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-requirements-09.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-8-31154118.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pana-requirements-09.txt

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

Content-Type: text/plain
Content-ID: <2004-8-31154118.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  Tue Aug 31 20:20: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 UAA16692
	for <pana-archive@lists.ietf.org>; Tue, 31 Aug 2004 20:20: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 1C2IeP-0004yP-BJ; Tue, 31 Aug 2004 20:06:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1C2IX5-0002JV-Ca
	for pana@megatron.ietf.org; Tue, 31 Aug 2004 19:59:26 -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 TAA14408
	for <pana@ietf.org>; Tue, 31 Aug 2004 19:59:20 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2IZ9-000348-K5
	for pana@ietf.org; Tue, 31 Aug 2004 20:01: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 <0I3C00HQR59WDG@mailout1.samsung.com> for pana@ietf.org; Wed,
	01 Sep 2004 08:58:44 +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 <0I3C00AQK58LWO@mailout1.samsung.com> for pana@ietf.org;
	Wed, 01 Sep 2004 08:57:58 +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 <0I3C00JWO58J7E@mmp1.samsung.com> for
	pana@ietf.org; Wed, 01 Sep 2004 08:57:57 +0900 (KST)
Date: Tue, 31 Aug 2004 16:57:54 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] Proposed text for issue 104
In-reply-to: <20040831020825.GI1536@steelhead>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Message-id: <00f701c48fb6$56084960$291d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
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: 8aa7cbc518894eb04182283f0682f662
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


Comments welcome.


[1] Section 2:

Change:

 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.

To:

 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
      network interfaces. 


Change:

   Device Identifier (DI):

      The identifier used by the network as a handle to control and
      police the network access of a client.  Depending on the access
      technology, this identifier might contain any of IP address,
      link-layer address, switch port number, etc.  of a connected
      device.

To:

   Device Identifier (DI):

      The identifier used by the network as a handle to control and
      police the network access of a client.  Depending on the access
      technology, this identifier may contain an address that is
      carried in protocol headers (e.g., IP or link-layer address),
      or a locally significant identifier that is made available
      by the local protocol stack (e.g., circuit id, PPP interface id) 
      of a connected device.

[2] Section 3.1:

Change:

         <-----     PANA-Bind-Request[Session-Id, EAP{Success},
                         Device-Id, Lifetime, Protection-Cap., Key-Id,
MAC]

To:

         <-----     PANA-Bind-Request[Session-Id, EAP{Success},
                         Device-Id, IP-Address, Lifetime,
Protection-Cap.,
                         Key-Id, MAC]


[3] Section 4.1.1:

Change:

   o  Device-Id AVP: contains a device identifier of the sender of the
      message.  A device identifier is represented as a pair of device
      identifier type and device identifier value.  Either a layer-2
      address or an IP address is used for the device identifier value.

To:

   o  Device-Id AVP: contains a device identifier of the PaC or an EP.
      A device identifier is represented as a pair of device
      identifier type and device identifier value.  Either a layer-2
      address or an IP address is used for the device identifier value
      when this AVP is present.

Remove:

   o  EP-Device-Id AVP: contains the device identifier of an EP.


[4] Section 4.1.5:

Change:

      *  Device-Id of PaC

      *  Device-Id of PAA

      *  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)

      *  List of device identifiers of EPs


To:

      *  Device-Id of PaC

      *  IP address of PaC (may be the same as the Device-Id of PaC)

      *  IP address of PAA

      *  List of device identifiers of EPs

[5] Section 4.1.7:

Change:

   o  When a device identifier of the communication peer is bound to the
      PANA session, it matches the device identifier carried in MAC and/
      or IP header(s), or other auxiliary indetifier provided by the
      lower-layers (e.g., circuit ID).


To:

   o  When a device identifier of the PaC is bound to the
      PANA session, it matches the device identifier carried in MAC or
      or IP header, or other locally-significant identifier provided by 
      the lower-layers (e.g., circuit ID) unless the message is 
      a PANA-Update-Request with IP-Address AVP.


Change:

   o  When a Device-Id AVP is included, the AVP is valid if the device
      identifier type contained in the AVP is supported (this check is
      for both PaC and PAA) and is the requested one (this check is for
      PAA only) and the device identifier value contained in the AVP
      matches the value extracted from the lower-layer encapsulation
      header corresponding to the device identifier type contained in
      the AVP.  Note that a Device-Id AVP carries the PaC's device
      identifier in messages from PaC to PAA and PAA's device identifier
      in messages from PAA to PaC.

To:


   o  When a Device-Id AVP is included, the AVP is valid if the device
      identifier type contained in the AVP is supported (check performed
      by both PaC and PAA) and is the requested one (check performed by
      PAA only) and the device identifier value contained in the AVP
      matches the value extracted from the lower-layer encapsulation
      header corresponding to the device identifier type contained in
      the AVP (check performed by PAA only).  Note that a Device-Id AVP
      carries the PaC's device identifier in messages from PaC to PAA  
      and EP(s)' device identifier in messages from PAA to PaC.

Add:

   o  When the IP-Address AVP is received in a message from the PAA,
      the AVP is valid if the IP address matches the source address
      in the IP header.


[6] Section 4.3:

Change:

        <-----     PANA-Bind-Request(x+3,y+2)
                       [Session-Id, EAP{Success}, Device-Id, Lifetime,
                        Protection-Cap., PPAC, MAC]

To:

        <-----     PANA-Bind-Request(x+3,y+2)
                       [Session-Id, EAP{Success}, Device-Id, IP-Address,
                        Lifetime, Protection-Cap., PPAC, MAC]


Change:

   The PANA-Bind-Request and the PANA-Bind-Answer message exchange is
   also used for binding device identifiers of the PaC and the PAA to
   the PANA SA when the identifiers are either IP or MAC addresses.  To
   achieve this, the PANA-Bind-Request and the PANA-Bind-Answer SHOULD
   contain a device identifier of the PAA and the PaC, respectively, in
   a Device-Id AVP.  Device identifier exchange that is protected by a
   MAC AVP prevents man-in-the-middle attacks.  The PaC MUST use the
   same type of device identifier as contained in the PANA-Bind-Request
   message.  

To:

   The PANA-Bind-Request and the PANA-Bind-Answer message exchange is
   also used for binding device identifiers of the PaC and EP(s), and 
   the IP address of the PAA to the PANA SA. To achieve this, 
   the PANA-Bind-Request SHOULD contain the device indentifier(s) of
   the EP(s) in Device-Id AVP(s) when they are either MAC or IP 
   address(es), and the IP address of the PAA in an IP-Address AVP. 
   PANA-Bind-Answer SHOULD contain PaC's device identifier in a 
   Device-Id AVP when it is already presented with that of EP(s). 
   The PaC MUST use the same type of device identifier as contained in 
   the PANA-Bind-Request message. This exchange when protected by a MAC 
   AVP prevents man-in-the-middle attacks. 


[7] Section 4.4:


Change:

         <-----     PANA-Bind-Request(p+2,q+2)
                       [Session-Id, EAP{Success}, Device-Id, Key-Id,
                        Lifetime, Protection-Cap., PPAC, MAC]

To:

         <-----     PANA-Bind-Request(p+2,q+2)
                       [Session-Id, EAP{Success}, Device-Id, IP-Address,
                        Key-Id, Lifetime, Protection-Cap., PPAC, MAC] 

[8] Section 4.6:

Change:

         <-----     PANA-Bind-Request(x+5,y+6)          // S-flag set
                      [EAP{Success}, Device-Id, Key-Id,
                       Lifetime, Protection-Cap., PPAC, MAC]

To:

         <-----     PANA-Bind-Request(x+5,y+6)          // S-flag set
                      [EAP{Success}, Device-Id, IP-Address, Key-Id,
                       Lifetime, Protection-Cap., PPAC, MAC]

[8] New text for Section 4.8:

4.8  Device ID Choice

   The device identifier used in the context of PANA can be an IP
   address, a MAC address, or an identifier that is not carried in data
   packets but has local significance in identifying a connected host
   (e.g., circuit id, PPP interface id).  The last type of identifiers 
   are commonly used in point-to-point links where MAC addresses are
   not available and lower-layers are already physically or
   cryptographically secured.

   It is assumed that the PAA knows the link type and the security
   mechanisms being provided or required on the access network (e.g.,
   based on physical security, link-layer ciphers enabled before or
   after PANA, or IPsec).  Based on that information, the PAA can decide
   what type of EP device id will be used when running PANA with the
   client.  When IPsec-based security [I-D.ietf-pana-ipsec] is the
   choice of access control, the PAA SHOULD provide IP address(es) 
   as EP(s)' device ID, and expect the PaC to provide its IP address 
   in return. In case IPsec is not used, MAC addresses are used as 
   device IDs when available.  If non-IPsec access control is enabled, 
   and a MAC address is not available, device ID exchange does not 
   occur within PANA. Instead, peers rely on lower-layers to provide
   locally-significant identifiers along with received PANA packets.

[9] Remove Section 4.13:

I think now the information in section 4.3 is already covered elsewhere,
so 
we can remove the section.




[10] Section 6.4.7:

Change:

6.4.7  PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

         PANA-Bind-Request ::= < PANA-Header: 4, REQ [SEP] [NAP] >
                       < Session-Id >
                       { Result-Code }
                       { PPAC }
                       [ EAP-Payload ]
                       [ Device-Id ]
                       [ Session-Lifetime ]
                       [ Protection-Capability ]
                       [ Key-Id ]
                    *  [ EP-Device-Id ]
                    *  [ AVP ]
                   0*1 < MAC >


To:

6.4.7  PANA-Bind-Request (PBR)

   PANA-Bind-Request (PBR) is sent by the PAA to the PaC.

         PANA-Bind-Request ::= < PANA-Header: 4, REQ [SEP] [NAP] >
                       < Session-Id >
                       { Result-Code }
                       { PPAC }
                       { IP-Address }
                       [ EAP-Payload ]
                       [ Device-Id ]
                       [ Session-Lifetime ]
                       [ Protection-Capability ]
                       [ Key-Id ]
                    *  [ Device-Id ]
                    *  [ AVP ]
                   0*1 < MAC >

[11] Remove "<Device-Id>" from PFER and PFEA in sections 6.4.14 and
6.4.15 

respectively.

[12] Remove Section "6.5.15  EP-Device-Id AVP".

[13] New text for Section 6.5.19:

6.5.19  IP-Address AVP

   The IP-Address (AVP Code: 1042) contains an IP address of a PaC or
PAA.
   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.

[14] Occurence tables in Section 6.6:


                          +-----------------------------------------+
                          |        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               |  1  |  1  |  0  |  0  |  0  |  0  |  0  |
      Device-Id           |  0  |  0  |  0  |  0  |  0+ | 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  |
      Key-Id              |  0  |  0  |  0  |  0  | 0-1 | 0-1 |  0  |
      IP-Address          |  0  |  0  |  0  |  0  |  1  |  0  |  0  |
      --------------------+-----+-----+-----+-----+-----+-----+-----+

                 Figure 12: 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
|
      Key-Id              |  0   |  0   |  0  |  0  |  0  | 0-1  | 0-1
|
      IP-Address          |  0   |  0   |  0  |  0  |  0  |  0   |  0
|
 
--------------------+------+------+-----+-----+-----+------+------+

                 Figure 13: AVP Occurrence Table (2/3)

                          +-----------+
                          |  Message  |
                          |   Type    |
                          +-----+-----+
      Attribute Name      | PUR | 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  |  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  |
      Key-Id              |  0  |  0  |
      IP-Address          |  1  |  0  |
      --------------------+-----+-----+

                 Figure 14: AVP Occurrence Table (3/3)




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


