From pana-bounces@ietf.org Thu Apr 05 04:06:26 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HZMyj-0005eI-Id; Thu, 05 Apr 2007 04:05:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HZMyh-0005eA-RJ
	for pana@ietf.org; Thu, 05 Apr 2007 04:05:56 -0400
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZMyd-0005MF-Jq
	for pana@ietf.org; Thu, 05 Apr 2007 04:05:55 -0400
Received: from [88.235.62.106] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1HZMya14iQ-0008Ve; Thu, 05 Apr 2007 04:05:50 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: <pana@ietf.org>
Date: Thu, 5 Apr 2007 11:05:36 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: Acd3WTDyizSUEhDfQsmuXavrnmLM4A==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Message-ID: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1+7vkeqWFyAjx+Z5LZA0VmX3a5bG2uzlZqr/ti
	8axZgzM9Jzaehwi/xHaTPm278NsT7EufAnwQHu70N4TjuqO0xZ
	lggGAi4cJpgakFQDdSBzQ==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [Pana] Review pana-pana-15a
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>
Errors-To: pana-bounces@ietf.org


PANA specification is reviewed based on the last round of AD comments
(thanks Yoshi!).

The spec is here: 

http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt

And it's diff with the version that predates last round of AD comments
(-13): 

http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-from-3.diff.htm
l

Please review the document and register your feedback by the end of April
12, Thursday.

Upon collecting and resolving any issues, the document will proceed to IETF
last call.

Thanks

Alper







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



From pana-bounces@ietf.org Sun Apr 08 10:14:59 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HaY9p-0003NC-EG; Sun, 08 Apr 2007 10:14:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HaY9o-0003N7-0e
	for pana@ietf.org; Sun, 08 Apr 2007 10:14:16 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HaY9j-0003Aj-Na
	for pana@ietf.org; Sun, 08 Apr 2007 10:14:15 -0400
Received: from [127.0.0.1] (mgw.toshibaamericaresearch.com [165.254.55.12])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l38EDiYh039072; Sun, 8 Apr 2007 10:13:50 -0400 (EDT)
	(envelope-from vfajardo@tari.toshiba.com)
Message-ID: <4617F77D.2020603@tari.toshiba.com>
Date: Sat, 07 Apr 2007 15:56:45 -0400
From: Victor Fajardo <vfajardo@tari.toshiba.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
Subject: Re: [Pana] Review pana-pana-15a
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
In-Reply-To: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.4 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
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>
Errors-To: pana-bounces@ietf.org

Hi Alper,

I just have some minor editorial comments:

1. In page 10, 2nd paragraph:

"..successfully derived, the last PANA-Auth-Request message MUST contain"

for clarity, maybe better as:

"..successfully derived, the last PANA-Auth-Request message with 'C' 
(Complete) bit set MUST contain ..."

also maybe the same can be applied in other text such as 5.3.

2. Session Lifetime terminlogy, maybe we can add one sentence to the end of the description to make
it clear that session timeout is also used in post access phase.

  ...session lifetime can be updated by a new round of EAP
  authentication before it expires. <add>For PANA session in the
  authentication and authorization phase, it should be set to
  a value that allows the PaC to detect a failed session in
  a reasonable amount of time</add>.

regards,
victor





> PANA specification is reviewed based on the last round of AD comments
> (thanks Yoshi!).
>
> The spec is here: 
>
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
>
> And it's diff with the version that predates last round of AD comments
> (-13): 
>
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-from-3.diff.htm
> l
>
> Please review the document and register your feedback by the end of April
> 12, Thursday.
>
> Upon collecting and resolving any issues, the document will proceed to IETF
> last call.
>
> Thanks
>
> 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 Apr 09 15:52:41 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hazui-0006Xc-MO; Mon, 09 Apr 2007 15:52:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hazuh-0006XC-3v
	for pana@ietf.org; Mon, 09 Apr 2007 15:52:31 -0400
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hazuf-00008D-Ip
	for pana@ietf.org; Mon, 09 Apr 2007 15:52:31 -0400
Received: from [85.102.195.35] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1Hazub2oC0-0008ST; Mon, 09 Apr 2007 15:52:29 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: <pana@ietf.org>
Date: Mon, 9 Apr 2007 22:52:08 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: Acd64I2q6mUqF5wRTkazs5VxLHtsKw==
Message-ID: <0MKp2t-1Hazub2oC0-0008ST@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX19gJvNesVYta2MJYG7wo6LPg6Y3cLTrY5JgGcn
	uziq3ZMXoNCpXJbYVEiOFrUEOi89tGB/brR+uZ8CgPUec1pQYN
	kOTz9Fg845tGRljdzMiCw==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Subject: [Pana] pana fwk
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>
Errors-To: pana-bounces@ietf.org

>From pana-fwk document:

   The PaC dynamically or statically configures an IP address prior to
   running PANA.  After the successful PANA authentication, depending on
   the deployment scenario the PaC may need to re-configure its IP
   address or configure additional IP address(es).  If this additional
   IP address configuration happens in the middle of an application
   protocol run, an appropriate procedure for changing an IP address
   will need to be taken so that the IP address change is transparent to
   the application protocol.


I find the last sentence less than clear. The point is, there are cases when
the IP address used during PANA needs to change after the successful
authentication. And until that happens, applications should not be using the
IP address. This is akin to availability of Mobile IP care-of address to the
Mobile IP protocol but not to general applications. The home address, when
bound to the care-of address, becomes available to the general applications.

I'd recommend this re-write:


   The PaC dynamically or statically configures an IP address prior to
   running PANA.  After the successful PANA authentication, depending on
   the deployment scenario the PaC may need to re-configure its IP
   address or configure additional IP address(es).  For example, a 
   link-local IPv6 address may be used for PANA and the PaC may be 
   allowed to configure additional global IPv6 address(es) upon
   successful authentication. Another example: A PaC may be limited to 
   use a IPv4 link-local address during PANA, and allowed to reconfigure 
   its interface with a non-link-local IPv4 address after the
authentication.
   General-purpose applications cannot use the interface until PANA 
   authentication succeeds and appropriate IP address configuration takes
   place.


Comments?

Alper




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



From necojp@citiz.net Tue Apr 10 08:23:18 2007
Return-path: <necojp@citiz.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbFNW-0008Cw-5k
	for PANA-ARCHIVE@LISTS.IETF.ORG; Tue, 10 Apr 2007 08:23:18 -0400
Received: from [222.168.183.125] (helo=a-net.ne.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HbFNU-0000iR-6e
	for PANA-ARCHIVE@LISTS.IETF.ORG; Tue, 10 Apr 2007 08:23:18 -0400
Received: from wfnfrtgza5 (unknown [38.156.175.250])
	by smtp6 (Coremail) with SMTP id NVvykO2XaBkG0hkt.1
	for <pana-archive@lists.ietf.org>; Tue, 10 Apr 2007 20:23:04 +0800 (CST)
X-Originating-IP: [38.156.175.250]
Subject: =?iso-2022-jp?B?GyRCSWI1JCVQJWwkXiQ3JD8bKEI=?=
From: =?shift-jis?B?aW5mb3JtYXRpb24=?= <necojp@citiz.net>
To: <pana-archive@lists.ietf.org>
X-Mailer: Microsoft Outlook Express 
MIME-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
X-Spam-Score: 2.0 (++)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

$B$C$F$$$&?4G[$O$b$&ITMW!*(B

$BF|K\:GBg$N%;%U%l7G<(HD(B
http://www.10wn.com/h/?jup2


$B40A4$K%;%C%/%9$N$_$N!"3d$j@Z$C$?%+%s%1%$!&!&!&$=$l$,%;%C%/%9%U%l%s%I$J$N$G$9!*(B
$BITNQ$dIb5$$@$H!"$"$H$"$HLLE]$J$3$H$K$J$C$?$j$b$7$^$9$h$M!&!&!&!)(B
$B$@$1$I!"%;%C%/%9%U%l%s%I$H$$$&7A$J$i$P!"$=$&$$$&?4G[$bL5$7!*(B

$B%K%C%/%M!<%`$H%a%"%I$N$_$G$$$^$9$0;H$($k!"%;%U%l7G<(HD$G$9(B
http://www.10wn.com/h/?jup2

$B(#(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(B
$B("(B     $BG[?.Dd;_$O%3%A%i$^$G!#(B
$B("(B     DeliveryStop
$B("(B     max@orange07.flnet.org
$B("(B
$B("!ZG[?.Dd;_<jB3$-$N:]$O![(B
$B("I,$:7oL>$K!VG[?.Dd;_!W$H$*=q$-2<$5$$!#(B
$B("7oL>$K!VG[?.Dd;_!W$H5-:\$5$l$F$$$J$$>l9g$O=hM}$,9T$($^$;$s!#(B
$B(">0!"Dd;_$K$O?tF|4V$[$I$*;~4V$r$$$?$@$/>l9g$,$4$6$$$^$9!#(B
$B("Dd;_$^$G?tF|!"?t2s%a!<%k$,Aw?.$5$l$k$3$H$,$4$6$$$^$9$,!"(B
$B("2?B4$4N;>5$/$@$5$$!#(B
$B(&(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(!(B




From pana-bounces@ietf.org Tue Apr 10 16:16:36 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbMlN-0000j0-La; Tue, 10 Apr 2007 16:16:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbMlM-0000iW-B5
	for pana@ietf.org; Tue, 10 Apr 2007 16:16:24 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbMlK-0008Fc-0T
	for pana@ietf.org; Tue, 10 Apr 2007 16:16:24 -0400
Received: from [85.102.195.35] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1HbMlG2r8A-0008Vx; Tue, 10 Apr 2007 16:16:21 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: <pana@ietf.org>
Date: Tue, 10 Apr 2007 23:16:00 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
In-Reply-To: 
Thread-Index: Acd3WTDyizSUEhDfQsmuXavrnmLM4AEU8f4A
Message-ID: <0MKp2t-1HbMlG2r8A-0008Vx@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX18NIYgYOCU2648ntXqkFRPtH/EM121UdbVmGx7
	ucTztpPGHESkQUzyBBoNt6SF5VhtJMyvEAmiJhkFGJa/+mrHYB
	QXEQx5iS7j1YA5aAIHFkQ==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: [Pana] RE: Review pana-pana-15a
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>
Errors-To: pana-bounces@ietf.org


I did my review and it looks good.

Alper

> -----Original Message-----
> From: Alper Yegin [mailto:alper.yegin@yegin.org]
> Sent: Thursday, April 05, 2007 11:06 AM
> To: 'pana@ietf.org'
> Subject: Review pana-pana-15a
> 
> 
> PANA specification is reviewed based on the last round of AD comments
> (thanks Yoshi!).
> 
> The spec is here:
> 
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
> 
> And it's diff with the version that predates last round of AD comments (-
> 13):
> 
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-from-
> 3.diff.html
> 
> Please review the document and register your feedback by the end of April
> 12, Thursday.
> 
> Upon collecting and resolving any issues, the document will proceed to
> IETF last call.
> 
> Thanks
> 
> Alper
> 
> 
> 
> 



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



From pana-bounces@ietf.org Thu Apr 12 04:30:54 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hbuhh-0006th-Ra; Thu, 12 Apr 2007 04:30:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hbuhf-0006t6-QB
	for pana@ietf.org; Thu, 12 Apr 2007 04:30:51 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hbuhe-0004R4-CH
	for pana@ietf.org; Thu, 12 Apr 2007 04:30:51 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 10:30:43 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] Use of Error Request message
Date: Thu, 12 Apr 2007 10:30:18 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB02604784626@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] Use of Error Request message
Thread-Index: Acd3WTDyizSUEhDfQsmuXavrnmLM4AFegk4g
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	<pana@ietf.org>
X-OriginalArrivalTime: 12 Apr 2007 08:30:43.0552 (UTC)
	FILETIME=[DC63B600:01C77CDC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: 
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>
Errors-To: pana-bounces@ietf.org

Hi,

In the current draft, error request messages i.e. =
PANA-Notification-Request message with 'E' (Error) bit set, are sent =
after any received message that may cause an error.

I propose to limit the use of this specific mechanism to the handling of =
errors due to PANA answer messages received by the peer. In that =
specific case, it is actually the only way for providing error =
notification to the originator of the answer message (if needed).

On the other hand, for the handling of PANA request messages, it is =
easier to always rely on PANA answer messages for providing error =
notification to the originator of the request, as done e.g. with =
Diameter.
The 'E' bit would be set in the answer message header in order to =
distinguish error notification from "normal" answer messages (some PANA =
answer messages being used just as ack messages).
When the 'E' bit is set in answer message, the Result-Code AVP would =
have to be present as well as the Failed-AVP AVP if needed.

Any comment?

Lionel


> -----Message d'origine-----
> De : Alper Yegin [mailto:alper.yegin@yegin.org]=20
> Envoy=E9 : jeudi 5 avril 2007 10:06
> =C0 : pana@ietf.org
> Objet : [Pana] Review pana-pana-15a
>=20
>=20
> PANA specification is reviewed based on the last round of AD=20
> comments (thanks Yoshi!).
>=20
> The spec is here:=20
>=20
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
>=20
> And it's diff with the version that predates last round of AD comments
> (-13):=20
>=20
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> rom-3.diff.htm
> l
>=20
> Please review the document and register your feedback by the=20
> end of April 12, Thursday.
>=20
> Upon collecting and resolving any issues, the document will=20
> proceed to IETF last call.
>=20
> Thanks
>=20
> Alper
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-bounces@ietf.org Thu Apr 12 05:42:58 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HbvpR-0003e8-At; Thu, 12 Apr 2007 05:42:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HbvpP-0003cw-JF
	for pana@ietf.org; Thu, 12 Apr 2007 05:42:55 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HbvpN-0006Od-SH
	for pana@ietf.org; Thu, 12 Apr 2007 05:42:55 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 11:42:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] PAA initiating Re-authentication 
Date: Thu, 12 Apr 2007 11:42:30 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026047846B9@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] PAA initiating Re-authentication 
Thread-Index: Acd3WTDyizSUEhDfQsmuXavrnmLM4AFh5rhQ
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	<pana@ietf.org>
X-OriginalArrivalTime: 12 Apr 2007 09:42:47.0534 (UTC)
	FILETIME=[EDAF00E0:01C77CE6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: 
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>
Errors-To: pana-bounces@ietf.org

Hi,

In section 5.7 Session Lifetime, it is stated:

"The PAA MUST initiate the re-authentication phase before the current =
session lifetime expires."

I can't figure out why there is a "MUST" in that case.

As documented in the draft,=20

- The session lifetime is not negociable between the PAA and the PaC.
- The session lifetime may be sent to the PaC. If not, the PaC considers =
the PANA session as unlimited.
- Both PaC and PAA may initiate a re-authentication procedure regardless =
of the session lifetime.

Could we just have the following principles:

- If the session lifetime is sent to the PaC:
The PaC should re-authenticate before the expiration of the session =
lifetime. Otherwise, the session is deleted by the PAA at the expiration =
of the session lifetime (and the PaC will purge related local state).
The PAA may initiate a re-authentication procedure before the expiration =
of the session lifetime. Otherwise, the session is deleted by the PAA at =
the expiration of the session lifetime (and the PaC will purge related =
local state).
Both PaC and PAA may initiate a re-authentication procedure regardless =
of the session lifetime.

- If the session lifetime is sent to the PaC:=20
The PAA may initiate a re-authentication procedure before the expiration =
of the session lifetime. Otherwise, the session is deleted at the =
expiration of the session lifetime.
Both PaC and PAA may initiate a re-authentication procedure regardless =
of the session lifetime.


With these principles, it is up to the PaC to maintain active its PANA =
session when infomed by the network (PAA) of the authorized session =
lifetime.
There is no strong requirement for the PAA/network point of view to . It =
is therefore up to the network operator to configure the PAA expected =
behaviour.

Comments?

Lionel
=20

> -----Message d'origine-----
> De : Alper Yegin [mailto:alper.yegin@yegin.org]=20
> Envoy=E9 : jeudi 5 avril 2007 10:06
> =C0 : pana@ietf.org
> Objet : [Pana] Review pana-pana-15a
>=20
>=20
> PANA specification is reviewed based on the last round of AD=20
> comments (thanks Yoshi!).
>=20
> The spec is here:=20
>=20
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
>=20
> And it's diff with the version that predates last round of AD comments
> (-13):=20
>=20
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> rom-3.diff.htm
> l
>=20
> Please review the document and register your feedback by the=20
> end of April 12, Thursday.
>=20
> Upon collecting and resolving any issues, the document will=20
> proceed to IETF last call.
>=20
> Thanks
>=20
> Alper
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-bounces@ietf.org Thu Apr 12 11:02:44 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc0os-0000a5-Li; Thu, 12 Apr 2007 11:02:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc0or-0000ZP-3Y
	for pana@ietf.org; Thu, 12 Apr 2007 11:02:41 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc0oL-0001q2-4E
	for pana@ietf.org; Thu, 12 Apr 2007 11:02:12 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 17:01:52 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] Use of the Nonce AVP
Date: Thu, 12 Apr 2007 17:02:11 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB0260478485D@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] Use of the Nonce AVP
Thread-Index: Acd3WTDyizSUEhDfQsmuXavrnmLM4AFpCclg
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	<pana@ietf.org>
X-OriginalArrivalTime: 12 Apr 2007 15:01:52.0461 (UTC)
	FILETIME=[80F307D0:01C77D13]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: 
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>
Errors-To: pana-bounces@ietf.org

Hi again,

In Section 4.1, it is stated:

   "A Nonce AVP MUST be included in the first non-initial
   PANA-Auth-Request and PANA-Auth-Answer messages, and MUST NOT be
   included in any other message."

This wording is quite ambiguous as one may understand that the nonce is =
used in only once within a PANA session while it will be actually used =
during each re-authentication procedures. Besides, "first non-initial =
PANA-Auth-Request and PANA-Auth-Answer messages" is unclear.
I propose the following text:

   "A Nonce AVP MUST be included in the first PANA-Auth-Request and
   PANA-Auth-Answer messages following the initial PANA-Auth-Request
   and PANA-Auth-Answer messages (i.e. with 'S' (Start) bit set), and =
MUST
   NOT be included in any other message, except during re-authentication =

   procedures (see section 4.3)"

Any comment?

Lionel

> -----Message d'origine-----
> De : Alper Yegin [mailto:alper.yegin@yegin.org]=20
> Envoy=E9 : jeudi 5 avril 2007 10:06
> =C0 : pana@ietf.org
> Objet : [Pana] Review pana-pana-15a
>=20
>=20
> PANA specification is reviewed based on the last round of AD=20
> comments (thanks Yoshi!).
>=20
> The spec is here:=20
>=20
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
>=20
> And it's diff with the version that predates last round of AD comments
> (-13):=20
>=20
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> rom-3.diff.htm
> l
>=20
> Please review the document and register your feedback by the=20
> end of April 12, Thursday.
>=20
> Upon collecting and resolving any issues, the document will=20
> proceed to IETF last call.
>=20
> Thanks
>=20
> Alper
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-bounces@ietf.org Thu Apr 12 11:35:59 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc1L2-0004Cb-KN; Thu, 12 Apr 2007 11:35:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc1L0-0004CV-WD
	for pana@ietf.org; Thu, 12 Apr 2007 11:35:55 -0400
Received: from mgw.toshibaamericaresearch.com ([165.254.55.12]
	helo=toshi17.tari.toshiba.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Hc1Kx-0007GL-Iz
	for pana@ietf.org; Thu, 12 Apr 2007 11:35:54 -0400
Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3CFZntD058644; Thu, 12 Apr 2007 11:35:49 -0400 (EDT)
	(envelope-from vfajardo@tari.toshiba.com)
Message-ID: <461E51F2.8030906@tari.toshiba.com>
Date: Thu, 12 Apr 2007 11:36:18 -0400
From: Victor Fajardo <vfajardo@tari.toshiba.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.com>
Subject: Re: [Pana] Use of Error Request message
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
	<7DBAFEC6A76F3E42817DF1EBE64CB02604784626@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <7DBAFEC6A76F3E42817DF1EBE64CB02604784626@FTRDMEL2.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by
	toshi17.tari.toshiba.com id l3CFZntD058644
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
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>
Errors-To: pana-bounces@ietf.org

Hi Lionel,
> I propose to limit the use of this specific mechanism to the handling o=
f errors due to PANA answer messages received by the peer. In that specif=
ic case, it is actually the only way for providing error notification to =
the originator of the answer message (if needed).
>
> On the other hand, for the handling of PANA request messages, it is eas=
ier to always rely on PANA answer messages for providing error notificati=
on to the originator of the request, as done e.g. with Diameter.
> The 'E' bit would be set in the answer message header in order to disti=
nguish error notification from "normal" answer messages (some PANA answer=
 messages being used just as ack messages).
> When the 'E' bit is set in answer message, the Result-Code AVP would ha=
ve to be present as well as the Failed-AVP AVP if needed.
>
> Any comment?
>  =20

The proposal should work though I'm not sure what the additional benefit=20
would be except maybe the savings of not having to send the notification=20
answer message in the latter case.  However, maybe such optimization is=20
not so relevant since error conditions are not the norm. I generally=20
like the current scheme (use error notification messages) because it=20
keeps things simple by centralizing error indications for all cases.

As a side note, one minor suggestion for 5.8 is to include small text=20
explicitly terminating the request retransmission procedure when error=20
notification is received for a pending request.

regards,
victor
> Lionel
>
>
>  =20
>> -----Message d'origine-----
>> De : Alper Yegin [mailto:alper.yegin@yegin.org]=20
>> Envoy=E9 : jeudi 5 avril 2007 10:06
>> =C0 : pana@ietf.org
>> Objet : [Pana] Review pana-pana-15a
>>
>>
>> PANA specification is reviewed based on the last round of AD=20
>> comments (thanks Yoshi!).
>>
>> The spec is here:=20
>>
>> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
>>
>> And it's diff with the version that predates last round of AD comments
>> (-13):=20
>>
>> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
>> rom-3.diff.htm
>> l
>>
>> Please review the document and register your feedback by the=20
>> end of April 12, Thursday.
>>
>> Upon collecting and resolving any issues, the document will=20
>> proceed to IETF last call.
>>
>> Thanks
>>
>> Alper
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Pana mailing list
>> Pana@ietf.org
>> https://www1.ietf.org/mailman/listinfo/pana
>>
>>    =20
>
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>
>
>
>  =20


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



From pana-bounces@ietf.org Thu Apr 12 11:47:29 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc1WC-0000th-Dw; Thu, 12 Apr 2007 11:47:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc1WB-0000tN-BW
	for pana@ietf.org; Thu, 12 Apr 2007 11:47:27 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Hc1W8-0007zV-PM
	for pana@ietf.org; Thu, 12 Apr 2007 11:47:27 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 17:47:16 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Pana] Use of Error Request message
Date: Thu, 12 Apr 2007 17:47:42 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026047848B1@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <461E51F2.8030906@tari.toshiba.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] Use of Error Request message
Thread-Index: Acd9GEZnILkBcDatQcarLrz0lYHr9gAAE4xQ
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net><7DBAFEC6A76F3E42817DF1EBE64CB02604784626@FTRDMEL2.rd.francetelecom.fr>
	<461E51F2.8030906@tari.toshiba.com>
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>
To: "Victor Fajardo" <vfajardo@tari.toshiba.com>
X-OriginalArrivalTime: 12 Apr 2007 15:47:16.0326 (UTC)
	FILETIME=[D87FD860:01C77D19]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
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>
Errors-To: pana-bounces@ietf.org

Hi Victor,

I can agree though it is quite strange to have a Request/Answer messages =
protocols and to see a PANA-Notification-Request message in response to =
PANA-Auth-Request ;)
The proposed modification doesn't change the principle of the error =
handling mechanism. But I think it could be seen more consistent. At =
least for me ;)



> -----Message d'origine-----
> De : Victor Fajardo [mailto:vfajardo@tari.toshiba.com]=20
> Envoy=E9 : jeudi 12 avril 2007 17:36
> =C0 : MORAND Lionel RD-CORE-ISS
> Cc : pana@ietf.org
> Objet : Re: [Pana] Use of Error Request message
>=20
> Hi Lionel,
> > I propose to limit the use of this specific mechanism to=20
> the handling of errors due to PANA answer messages received=20
> by the peer. In that specific case, it is actually the only=20
> way for providing error notification to the originator of the=20
> answer message (if needed).
> >
> > On the other hand, for the handling of PANA request=20
> messages, it is easier to always rely on PANA answer messages=20
> for providing error notification to the originator of the=20
> request, as done e.g. with Diameter.
> > The 'E' bit would be set in the answer message header in=20
> order to distinguish error notification from "normal" answer=20
> messages (some PANA answer messages being used just as ack messages).
> > When the 'E' bit is set in answer message, the Result-Code=20
> AVP would have to be present as well as the Failed-AVP AVP if needed.
> >
> > Any comment?
> >  =20
>=20
> The proposal should work though I'm not sure what the=20
> additional benefit would be except maybe the savings of not=20
> having to send the notification answer message in the latter=20
> case.  However, maybe such optimization is not so relevant=20
> since error conditions are not the norm. I generally like the=20
> current scheme (use error notification messages) because it=20
> keeps things simple by centralizing error indications for all cases.
>=20
> As a side note, one minor suggestion for 5.8 is to include=20
> small text explicitly terminating the request retransmission=20
> procedure when error notification is received for a pending request.
>=20
> regards,
> victor
> > Lionel
> >
> >
> >  =20
> >> -----Message d'origine-----
> >> De : Alper Yegin [mailto:alper.yegin@yegin.org] Envoy=E9 : jeudi 5=20
> >> avril 2007 10:06 =C0 : pana@ietf.org Objet : [Pana] Review=20
> >> pana-pana-15a
> >>
> >>
> >> PANA specification is reviewed based on the last round of=20
> AD comments=20
> >> (thanks Yoshi!).
> >>
> >> The spec is here:=20
> >>
> >> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
> >>
> >> And it's diff with the version that predates last round of AD=20
> >> comments
> >> (-13):=20
> >>
> >> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> >> rom-3.diff.htm
> >> l
> >>
> >> Please review the document and register your feedback by=20
> the end of=20
> >> April 12, Thursday.
> >>
> >> Upon collecting and resolving any issues, the document=20
> will proceed=20
> >> to IETF last call.
> >>
> >> Thanks
> >>
> >> Alper
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Pana mailing list
> >> Pana@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/pana
> >>
> >>    =20
> >
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >
> >
> >
> >  =20
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-bounces@ietf.org Thu Apr 12 11:55:34 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc1e0-0008KN-SP; Thu, 12 Apr 2007 11:55:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc1dz-0008KD-9e
	for pana@ietf.org; Thu, 12 Apr 2007 11:55:31 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc1dx-0000A8-Rc
	for pana@ietf.org; Thu, 12 Apr 2007 11:55:31 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Apr 2007 17:55:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] IP address of the PaC in the PANA session attribute
Date: Thu, 12 Apr 2007 17:55:45 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026047848B6@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] IP address of the PaC in the PANA session attribute
Thread-Index: Acd3WTDyizSUEhDfQsmuXavrnmLM4AFuxkjw
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	<pana@ietf.org>
X-OriginalArrivalTime: 12 Apr 2007 15:55:18.0492 (UTC)
	FILETIME=[F7E489C0:01C77D1A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: 
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>
Errors-To: pana-bounces@ietf.org

Hi,

There is a description of the PANA session attributes in the section =
5.3:

   "PANA SA attributes as well as PANA session attributes are listed
   below:

   PANA Session attributes:

      *  Session Identifier

      *  IP address and UDP port number of the PaC.

      *  IP address and UDP port number of the PAA

      *  Sequence number of the last transmitted request

      *  Sequence number of the last received request

      *  Last transmitted message payload

      *  Retransmission interval

      *  Session lifetime

      *  PANA SA attributes "

A NAT may exist between the PaC and the PAA (that is already covered in =
section 6.1). Therefore, the PaC IP address/UDP port number should not =
be part of the PANA session attributes. Instead, we should have the =
source IP address and the UDP source port number of the last =
PaC-initiated PANA messages (to take into account the fact that the PaC =
may change its IP address cf. section 5.6). I don't have any concrete =
proposal for improving the current text... But maybe it is not needed if =
my comment is not valid at all ;)

Lionel=20

> -----Message d'origine-----
> De : Alper Yegin [mailto:alper.yegin@yegin.org]=20
> Envoy=E9 : jeudi 5 avril 2007 10:06
> =C0 : pana@ietf.org
> Objet : [Pana] Review pana-pana-15a
>=20
>=20
> PANA specification is reviewed based on the last round of AD=20
> comments (thanks Yoshi!).
>=20
> The spec is here:=20
>=20
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
>=20
> And it's diff with the version that predates last round of AD comments
> (-13):=20
>=20
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> rom-3.diff.htm
> l
>=20
> Please review the document and register your feedback by the=20
> end of April 12, Thursday.
>=20
> Upon collecting and resolving any issues, the document will=20
> proceed to IETF last call.
>=20
> Thanks
>=20
> Alper
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-bounces@ietf.org Thu Apr 12 13:11:48 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc2po-00088J-6L; Thu, 12 Apr 2007 13:11:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc2pm-00086m-P7
	for pana@ietf.org; Thu, 12 Apr 2007 13:11:46 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc2pl-0000ul-1H
	for pana@ietf.org; Thu, 12 Apr 2007 13:11:46 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3CHBgfp017447;
	Fri, 13 Apr 2007 02:11:42 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3CHBgRv015365;
	Fri, 13 Apr 2007 02:11:42 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id CAA15364;
	Fri, 13 Apr 2007 02:11:42 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3CHBfN0012836;
	Fri, 13 Apr 2007 02:11:42 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3CHBflo012157;
	Fri, 13 Apr 2007 02:11:41 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGE00ABIAFEMP70@mail.po.toshiba.co.jp>; Fri,
	13 Apr 2007 02:11:41 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hc2pf-0008Eo-Ez; Thu,
	12 Apr 2007 10:11:39 -0700
Date: Thu, 12 Apr 2007 13:11:39 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] IP address of the PaC in the PANA session attribute
In-reply-to: <7DBAFEC6A76F3E42817DF1EBE64CB026047848B6@FTRDMEL2.rd.francetelecom.fr>
To: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.com>
Message-id: <20070412171139.GB31369@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=euc-jp
Content-disposition: inline
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
	<7DBAFEC6A76F3E42817DF1EBE64CB026047848B6@FTRDMEL2.rd.francetelecom.fr>
User-Agent: Mutt/1.5.13 (2006-08-11)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by inet-tsb5.toshiba.co.jp
	id l3CHBgfp017447
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
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>
Errors-To: pana-bounces@ietf.org

Hi Lionel,

When NAT exists between PaC and PAA, the IP address and port number of
the PaC will simply point to the ones used by NAT.  If the IP address
and/or port of PaC changes, the IP address and port number attributes
will be modified to the new ones based on the IP address update
procedure defined in Section 5.6.  Said that I don't see a problem
with containing IP address and port number in the PANA session
attributes.

Yoshihiro Ohba


On Thu, Apr 12, 2007 at 05:55:45PM +0200, MORAND Lionel RD-CORE-ISS wrote=
:
> Hi,
>=20
> There is a description of the PANA session attributes in the section 5.=
3:
>=20
>    "PANA SA attributes as well as PANA session attributes are listed
>    below:
>=20
>    PANA Session attributes:
>=20
>       *  Session Identifier
>=20
>       *  IP address and UDP port number of the PaC.
>=20
>       *  IP address and UDP port number of the PAA
>=20
>       *  Sequence number of the last transmitted request
>=20
>       *  Sequence number of the last received request
>=20
>       *  Last transmitted message payload
>=20
>       *  Retransmission interval
>=20
>       *  Session lifetime
>=20
>       *  PANA SA attributes "
>=20
> A NAT may exist between the PaC and the PAA (that is already covered in=
 section 6.1). Therefore, the PaC IP address/UDP port number should not b=
e part of the PANA session attributes. Instead, we should have the source=
 IP address and the UDP source port number of the last PaC-initiated PANA=
 messages (to take into account the fact that the PaC may change its IP a=
ddress cf. section 5.6). I don't have any concrete proposal for improving=
 the current text... But maybe it is not needed if my comment is not vali=
d at all ;)
>=20
> Lionel=20
>=20
> > -----Message d'origine-----
> > De : Alper Yegin [mailto:alper.yegin@yegin.org]=20
> > Envoy=8F=AB=B1 : jeudi 5 avril 2007 10:06
> > =8F=AA=A2 : pana@ietf.org
> > Objet : [Pana] Review pana-pana-15a
> >=20
> >=20
> > PANA specification is reviewed based on the last round of AD=20
> > comments (thanks Yoshi!).
> >=20
> > The spec is here:=20
> >=20
> > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
> >=20
> > And it's diff with the version that predates last round of AD comment=
s
> > (-13):=20
> >=20
> > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> > rom-3.diff.htm
> > l
> >=20
> > Please review the document and register your feedback by the=20
> > end of April 12, Thursday.
> >=20
> > Upon collecting and resolving any issues, the document will=20
> > proceed to IETF last call.
> >=20
> > Thanks
> >=20
> > Alper
> >=20
> >=20
> >=20
> >=20
> >=20
> >=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20
>=20

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



From pana-bounces@ietf.org Thu Apr 12 13:43:51 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc3Kl-0001lY-Up; Thu, 12 Apr 2007 13:43:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc3Kk-0001fW-4V
	for pana@ietf.org; Thu, 12 Apr 2007 13:43:46 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc3Kh-0006am-AC
	for pana@ietf.org; Thu, 12 Apr 2007 13:43:46 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3CHhfUA020606;
	Fri, 13 Apr 2007 02:43:41 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3CHhf3A020901;
	Fri, 13 Apr 2007 02:43:41 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id CAA20900;
	Fri, 13 Apr 2007 02:43:41 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3CHheHC029110;
	Fri, 13 Apr 2007 02:43:40 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3CHhefj010941;
	Fri, 13 Apr 2007 02:43:40 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGE00AN2BWPMP70@mail.po.toshiba.co.jp>; Fri,
	13 Apr 2007 02:43:40 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hc3Kc-0005y4-DH; Thu,
	12 Apr 2007 10:43:38 -0700
Date: Thu, 12 Apr 2007 13:43:38 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Use of Error Request message
In-reply-to: <7DBAFEC6A76F3E42817DF1EBE64CB026047848B1@FTRDMEL2.rd.francetelecom.fr>
To: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.com>
Message-id: <20070412174338.GC31369@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=euc-jp
Content-disposition: inline
References: <461E51F2.8030906@tari.toshiba.com>
	<7DBAFEC6A76F3E42817DF1EBE64CB026047848B1@FTRDMEL2.rd.francetelecom.fr>
User-Agent: Mutt/1.5.13 (2006-08-11)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by inet-tsb5.toshiba.co.jp
	id l3CHhfUA020606
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
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>
Errors-To: pana-bounces@ietf.org

Hi Lionel,

On Thu, Apr 12, 2007 at 05:47:42PM +0200, MORAND Lionel RD-CORE-ISS wrote=
:
> Hi Victor,
>=20
> I can agree though it is quite strange to have a Request/Answer message=
s protocols and to see a PANA-Notification-Request message in response to=
 PANA-Auth-Request ;)

To me error messages are sort of "interruptions", so I don't see it
strange to send an error request in response to a request or an
answer.

> The proposed modification doesn't change the principle of the error han=
dling mechanism. But I think it could be seen more consistent. At least f=
or me ;)

>From my Diameter parser implementation experience, defining two types
of ABNF for answer messages depending on 'E' bit settings is more
complex.  I believe the way currently PANA is defined is much simpler.

Yoshihiro Ohba



>=20
>=20
>=20
> > -----Message d'origine-----
> > De : Victor Fajardo [mailto:vfajardo@tari.toshiba.com]=20
> > Envoy=8F=AB=B1 : jeudi 12 avril 2007 17:36
> > =8F=AA=A2 : MORAND Lionel RD-CORE-ISS
> > Cc : pana@ietf.org
> > Objet : Re: [Pana] Use of Error Request message
> >=20
> > Hi Lionel,
> > > I propose to limit the use of this specific mechanism to=20
> > the handling of errors due to PANA answer messages received=20
> > by the peer. In that specific case, it is actually the only=20
> > way for providing error notification to the originator of the=20
> > answer message (if needed).
> > >
> > > On the other hand, for the handling of PANA request=20
> > messages, it is easier to always rely on PANA answer messages=20
> > for providing error notification to the originator of the=20
> > request, as done e.g. with Diameter.
> > > The 'E' bit would be set in the answer message header in=20
> > order to distinguish error notification from "normal" answer=20
> > messages (some PANA answer messages being used just as ack messages).
> > > When the 'E' bit is set in answer message, the Result-Code=20
> > AVP would have to be present as well as the Failed-AVP AVP if needed.
> > >
> > > Any comment?
> > >  =20
> >=20
> > The proposal should work though I'm not sure what the=20
> > additional benefit would be except maybe the savings of not=20
> > having to send the notification answer message in the latter=20
> > case.  However, maybe such optimization is not so relevant=20
> > since error conditions are not the norm. I generally like the=20
> > current scheme (use error notification messages) because it=20
> > keeps things simple by centralizing error indications for all cases.
> >=20
> > As a side note, one minor suggestion for 5.8 is to include=20
> > small text explicitly terminating the request retransmission=20
> > procedure when error notification is received for a pending request.
> >=20
> > regards,
> > victor
> > > Lionel
> > >
> > >
> > >  =20
> > >> -----Message d'origine-----
> > >> De : Alper Yegin [mailto:alper.yegin@yegin.org] Envoy=8F=AB=B1 : j=
eudi 5=20
> > >> avril 2007 10:06 =8F=AA=A2 : pana@ietf.org Objet : [Pana] Review=20
> > >> pana-pana-15a
> > >>
> > >>
> > >> PANA specification is reviewed based on the last round of=20
> > AD comments=20
> > >> (thanks Yoshi!).
> > >>
> > >> The spec is here:=20
> > >>
> > >> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
> > >>
> > >> And it's diff with the version that predates last round of AD=20
> > >> comments
> > >> (-13):=20
> > >>
> > >> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> > >> rom-3.diff.htm
> > >> l
> > >>
> > >> Please review the document and register your feedback by=20
> > the end of=20
> > >> April 12, Thursday.
> > >>
> > >> Upon collecting and resolving any issues, the document=20
> > will proceed=20
> > >> to IETF last call.
> > >>
> > >> Thanks
> > >>
> > >> Alper
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> _______________________________________________
> > >> Pana mailing list
> > >> Pana@ietf.org
> > >> https://www1.ietf.org/mailman/listinfo/pana
> > >>
> > >>    =20
> > >
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > >
> > >
> > >
> > >  =20
> >=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20
>=20

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



From pana-bounces@ietf.org Thu Apr 12 13:49:44 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc3QW-0006Ig-6K; Thu, 12 Apr 2007 13:49:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc3QV-0006Ee-3Z
	for pana@ietf.org; Thu, 12 Apr 2007 13:49:43 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc3QT-0007iU-EK
	for pana@ietf.org; Thu, 12 Apr 2007 13:49:43 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3CHndtu021396;
	Fri, 13 Apr 2007 02:49:39 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3CHndbV022245;
	Fri, 13 Apr 2007 02:49:39 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id CAA22244;
	Fri, 13 Apr 2007 02:49:39 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3CHndLB002085;
	Fri, 13 Apr 2007 02:49:39 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3CHnd6d029608;
	Fri, 13 Apr 2007 02:49:39 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGE00APIC6MMP70@mail.po.toshiba.co.jp>; Fri,
	13 Apr 2007 02:49:39 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hc3QN-0005zB-Oa; Thu,
	12 Apr 2007 10:49:35 -0700
Date: Thu, 12 Apr 2007 13:49:35 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Use of Error Request message
In-reply-to: <461E51F2.8030906@tari.toshiba.com>
To: Victor Fajardo <vfajardo@tari.toshiba.com>
Message-id: <20070412174935.GD31369@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
	<7DBAFEC6A76F3E42817DF1EBE64CB02604784626@FTRDMEL2.rd.francetelecom.fr>
	<461E51F2.8030906@tari.toshiba.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.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>
Errors-To: pana-bounces@ietf.org

On Thu, Apr 12, 2007 at 11:36:18AM -0400, Victor Fajardo wrote:
> 
> As a side note, one minor suggestion for 5.8 is to include small text 
> explicitly terminating the request retransmission procedure when error 
> notification is received for a pending request.
> 

Adding the explicit text is good, but it is only for protected error
messages.  For unprotected errors, there is a rule in Section 5.8
which prohibits terminating the request retransmission procedure:

"
   If an error request or answer message is sent unprotected (i.e.,
   without using an AUTH AVP) then the message MUST be processed such
   that the receiver does not change its PANA protocol state.
"

Yoshihiro Ohba

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



From pana-bounces@ietf.org Thu Apr 12 13:53:01 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hc3Th-0008Tg-1l; Thu, 12 Apr 2007 13:53:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hc3Tf-0008TN-EU
	for pana@ietf.org; Thu, 12 Apr 2007 13:52:59 -0400
Received: from imx12.toshiba.co.jp ([61.202.160.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hc3Td-0007ze-NF
	for pana@ietf.org; Thu, 12 Apr 2007 13:52:59 -0400
Received: from wall11.toshiba.co.jp (wall11 [133.199.90.149])
	by imx12.toshiba.co.jp  with ESMTP id l3CHqtBh027230;
	Fri, 13 Apr 2007 02:52:55 +0900 (JST)
Received: (from root@localhost) by wall11.toshiba.co.jp  id l3CHqtxe002038;
	Fri, 13 Apr 2007 02:52:55 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] 
	by wall11.toshiba.co.jp with ESMTP id CAA02037;
	Fri, 13 Apr 2007 02:52:55 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp11.toshiba.co.jp  with ESMTP id l3CHqs7j001847;
	Fri, 13 Apr 2007 02:52:54 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3CHqsoe001734;
	Fri, 13 Apr 2007 02:52:54 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGE00A15CC3MM80@mail.po.toshiba.co.jp>; Fri,
	13 Apr 2007 02:52:54 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hc3TY-0005zo-Is; Thu,
	12 Apr 2007 10:52:52 -0700
Date: Thu, 12 Apr 2007 13:52:52 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Use of the Nonce AVP
In-reply-to: <7DBAFEC6A76F3E42817DF1EBE64CB0260478485D@FTRDMEL2.rd.francetelecom.fr>
To: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.com>
Message-id: <20070412175252.GE31369@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=euc-jp
Content-disposition: inline
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
	<7DBAFEC6A76F3E42817DF1EBE64CB0260478485D@FTRDMEL2.rd.francetelecom.fr>
User-Agent: Mutt/1.5.13 (2006-08-11)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by imx12.toshiba.co.jp id
	l3CHqtBh027230
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
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>
Errors-To: pana-bounces@ietf.org

The proposed text works for me.

Yoshihiro Ohba

On Thu, Apr 12, 2007 at 05:02:11PM +0200, MORAND Lionel RD-CORE-ISS wrote=
:
> Hi again,
>=20
> In Section 4.1, it is stated:
>=20
>    "A Nonce AVP MUST be included in the first non-initial
>    PANA-Auth-Request and PANA-Auth-Answer messages, and MUST NOT be
>    included in any other message."
>=20
> This wording is quite ambiguous as one may understand that the nonce is=
 used in only once within a PANA session while it will be actually used d=
uring each re-authentication procedures. Besides, "first non-initial PANA=
-Auth-Request and PANA-Auth-Answer messages" is unclear.
> I propose the following text:
>=20
>    "A Nonce AVP MUST be included in the first PANA-Auth-Request and
>    PANA-Auth-Answer messages following the initial PANA-Auth-Request
>    and PANA-Auth-Answer messages (i.e. with 'S' (Start) bit set), and M=
UST
>    NOT be included in any other message, except during re-authenticatio=
n=20
>    procedures (see section 4.3)"
>=20
> Any comment?
>=20
> Lionel
>=20
> > -----Message d'origine-----
> > De : Alper Yegin [mailto:alper.yegin@yegin.org]=20
> > Envoy=8F=AB=B1 : jeudi 5 avril 2007 10:06
> > =8F=AA=A2 : pana@ietf.org
> > Objet : [Pana] Review pana-pana-15a
> >=20
> >=20
> > PANA specification is reviewed based on the last round of AD=20
> > comments (thanks Yoshi!).
> >=20
> > The spec is here:=20
> >=20
> > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
> >=20
> > And it's diff with the version that predates last round of AD comment=
s
> > (-13):=20
> >=20
> > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> > rom-3.diff.htm
> > l
> >=20
> > Please review the document and register your feedback by the=20
> > end of April 12, Thursday.
> >=20
> > Upon collecting and resolving any issues, the document will=20
> > proceed to IETF last call.
> >=20
> > Thanks
> >=20
> > Alper
> >=20
> >=20
> >=20
> >=20
> >=20
> >=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20
>=20

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



From pana-bounces@ietf.org Fri Apr 13 04:30:34 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcHAv-00027K-Gr; Fri, 13 Apr 2007 04:30:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcHAu-00027C-Kx
	for pana@ietf.org; Fri, 13 Apr 2007 04:30:32 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcHAt-0006g0-6H
	for pana@ietf.org; Fri, 13 Apr 2007 04:30:32 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Apr 2007 10:30:28 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Pana] IP address of the PaC in the PANA session attribute
Date: Fri, 13 Apr 2007 10:30:23 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026047849BE@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <20070412171139.GB31369@steelhead>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] IP address of the PaC in the PANA session attribute
Thread-Index: Acd9JauQPUnugKvyRgykQkGRNWndtwAf5O2Q
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net><7DBAFEC6A76F3E42817DF1EBE64CB026047848B6@FTRDMEL2.rd.francetelecom.fr>
	<20070412171139.GB31369@steelhead>
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
X-OriginalArrivalTime: 13 Apr 2007 08:30:28.0052 (UTC)
	FILETIME=[FD905940:01C77DA5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
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>
Content-Type: multipart/mixed; boundary="===============0655801011=="
Errors-To: pana-bounces@ietf.org

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

SGkgWW9zaGksDQoNCk1heWJlIEkgd2FzIGNvbmZ1c2luZyEgSSdtIG5vdCBzYXlpbmcgdGhhdCB0
aGUgSVAgYWRkcmVzcy9wb3J0IG51bWJlciBzaG91bGQgbm90IGJlIHBhcnQgb2YgdGhlIFBBTkEg
c2Vzc2lvbiBhdHRyaWJ1dGVzLg0KSSdtIGp1c3Qgc2F5aW5nIHRoYXQgdGhlIHdvcmRpbmc6DQoN
CiAgICAgICAqICBJUCBhZGRyZXNzIGFuZCBVRFAgcG9ydCBudW1iZXIgb2YgdGhlIFBhQy4NCg0K
TWlnaHQgbm90IGJlIGNvcnJlY3QgaWYgeW91IGFyZSBjb25zaWRlcmluZyBOQVQuIEJ1dCBpdCBp
cyBub3QgYSBzdHJvbmcgcG9pbnQgZm9yIG1lLiBKdXN0IGEgTmljZS10by1IYXZlIGlmIGNvbnNp
ZGVyZWQgdG8gYmUgdXNlZnVsLg0KDQpCUiwNCg0KTGlvbmVsDQoNCj4gLS0tLS1NZXNzYWdlIGQn
b3JpZ2luZS0tLS0tDQo+IERlIDogWW9zaGloaXJvIE9oYmEgW21haWx0bzp5b2hiYUB0YXJpLnRv
c2hpYmEuY29tXSANCj4gRW52b3nDqSA6IGpldWRpIDEyIGF2cmlsIDIwMDcgMTk6MTINCj4gw4Ag
OiBNT1JBTkQgTGlvbmVsIFJELUNPUkUtSVNTDQo+IENjIDogcGFuYUBpZXRmLm9yZw0KPiBPYmpl
dCA6IFJlOiBbUGFuYV0gSVAgYWRkcmVzcyBvZiB0aGUgUGFDIGluIHRoZSBQQU5BIHNlc3Npb24g
YXR0cmlidXRlDQo+IA0KPiBIaSBMaW9uZWwsDQo+IA0KPiBXaGVuIE5BVCBleGlzdHMgYmV0d2Vl
biBQYUMgYW5kIFBBQSwgdGhlIElQIGFkZHJlc3MgYW5kIHBvcnQgDQo+IG51bWJlciBvZiB0aGUg
UGFDIHdpbGwgc2ltcGx5IHBvaW50IHRvIHRoZSBvbmVzIHVzZWQgYnkgTkFULiAgDQo+IElmIHRo
ZSBJUCBhZGRyZXNzIGFuZC9vciBwb3J0IG9mIFBhQyBjaGFuZ2VzLCB0aGUgSVAgYWRkcmVzcyAN
Cj4gYW5kIHBvcnQgbnVtYmVyIGF0dHJpYnV0ZXMgd2lsbCBiZSBtb2RpZmllZCB0byB0aGUgbmV3
IG9uZXMgDQo+IGJhc2VkIG9uIHRoZSBJUCBhZGRyZXNzIHVwZGF0ZSBwcm9jZWR1cmUgZGVmaW5l
ZCBpbiBTZWN0aW9uIA0KPiA1LjYuICBTYWlkIHRoYXQgSSBkb24ndCBzZWUgYSBwcm9ibGVtIHdp
dGggY29udGFpbmluZyBJUCANCj4gYWRkcmVzcyBhbmQgcG9ydCBudW1iZXIgaW4gdGhlIFBBTkEg
c2Vzc2lvbiBhdHRyaWJ1dGVzLg0KPiANCj4gWW9zaGloaXJvIE9oYmENCj4gDQo+IA0KPiBPbiBU
aHUsIEFwciAxMiwgMjAwNyBhdCAwNTo1NTo0NVBNICswMjAwLCBNT1JBTkQgTGlvbmVsIA0KPiBS
RC1DT1JFLUlTUyB3cm90ZToNCj4gPiBIaSwNCj4gPiANCj4gPiBUaGVyZSBpcyBhIGRlc2NyaXB0
aW9uIG9mIHRoZSBQQU5BIHNlc3Npb24gYXR0cmlidXRlcyBpbiANCj4gdGhlIHNlY3Rpb24gNS4z
Og0KPiA+IA0KPiA+ICAgICJQQU5BIFNBIGF0dHJpYnV0ZXMgYXMgd2VsbCBhcyBQQU5BIHNlc3Np
b24gYXR0cmlidXRlcyBhcmUgbGlzdGVkDQo+ID4gICAgYmVsb3c6DQo+ID4gDQo+ID4gICAgUEFO
QSBTZXNzaW9uIGF0dHJpYnV0ZXM6DQo+ID4gDQo+ID4gICAgICAgKiAgU2Vzc2lvbiBJZGVudGlm
aWVyDQo+ID4gDQo+ID4gICAgICAgKiAgSVAgYWRkcmVzcyBhbmQgVURQIHBvcnQgbnVtYmVyIG9m
IHRoZSBQYUMuDQo+ID4gDQo+ID4gICAgICAgKiAgSVAgYWRkcmVzcyBhbmQgVURQIHBvcnQgbnVt
YmVyIG9mIHRoZSBQQUENCj4gPiANCj4gPiAgICAgICAqICBTZXF1ZW5jZSBudW1iZXIgb2YgdGhl
IGxhc3QgdHJhbnNtaXR0ZWQgcmVxdWVzdA0KPiA+IA0KPiA+ICAgICAgICogIFNlcXVlbmNlIG51
bWJlciBvZiB0aGUgbGFzdCByZWNlaXZlZCByZXF1ZXN0DQo+ID4gDQo+ID4gICAgICAgKiAgTGFz
dCB0cmFuc21pdHRlZCBtZXNzYWdlIHBheWxvYWQNCj4gPiANCj4gPiAgICAgICAqICBSZXRyYW5z
bWlzc2lvbiBpbnRlcnZhbA0KPiA+IA0KPiA+ICAgICAgICogIFNlc3Npb24gbGlmZXRpbWUNCj4g
PiANCj4gPiAgICAgICAqICBQQU5BIFNBIGF0dHJpYnV0ZXMgIg0KPiA+IA0KPiA+IEEgTkFUIG1h
eSBleGlzdCBiZXR3ZWVuIHRoZSBQYUMgYW5kIHRoZSBQQUEgKHRoYXQgaXMgDQo+IGFscmVhZHkg
Y292ZXJlZCANCj4gPiBpbiBzZWN0aW9uIDYuMSkuIFRoZXJlZm9yZSwgdGhlIFBhQyBJUCBhZGRy
ZXNzL1VEUCBwb3J0IA0KPiBudW1iZXIgc2hvdWxkIA0KPiA+IG5vdCBiZSBwYXJ0IG9mIHRoZSBQ
QU5BIHNlc3Npb24gYXR0cmlidXRlcy4gSW5zdGVhZCwgd2Ugc2hvdWxkIGhhdmUgDQo+ID4gdGhl
IHNvdXJjZSBJUCBhZGRyZXNzIGFuZCB0aGUgVURQIHNvdXJjZSBwb3J0IG51bWJlciBvZiB0aGUg
bGFzdCANCj4gPiBQYUMtaW5pdGlhdGVkIFBBTkEgbWVzc2FnZXMgKHRvIHRha2UgaW50byBhY2Nv
dW50IHRoZSBmYWN0IHRoYXQgdGhlIA0KPiA+IFBhQyBtYXkgY2hhbmdlIGl0cyBJUCBhZGRyZXNz
IGNmLiBzZWN0aW9uIDUuNikuIEkgZG9uJ3QgaGF2ZSBhbnkgDQo+ID4gY29uY3JldGUgcHJvcG9z
YWwgZm9yIGltcHJvdmluZyB0aGUgY3VycmVudCB0ZXh0Li4uIEJ1dCBtYXliZSBpdCBpcyANCj4g
PiBub3QgbmVlZGVkIGlmIG15IGNvbW1lbnQgaXMgbm90IHZhbGlkIGF0IGFsbCA7KQ0KPiA+IA0K
PiA+IExpb25lbA0KPiA+IA0KPiA+ID4gLS0tLS1NZXNzYWdlIGQnb3JpZ2luZS0tLS0tDQo+ID4g
PiBEZSA6IEFscGVyIFllZ2luIFttYWlsdG86YWxwZXIueWVnaW5AeWVnaW4ub3JnXQ0KPiA+ID4g
RW52b3nvvJ8gOiBqZXVkaSA1IGF2cmlsIDIwMDcgMTA6MDYNCj4gPiA+IO+8nyA6IHBhbmFAaWV0
Zi5vcmcNCj4gPiA+IE9iamV0IDogW1BhbmFdIFJldmlldyBwYW5hLXBhbmEtMTVhDQo+ID4gPiAN
Cj4gPiA+IA0KPiA+ID4gUEFOQSBzcGVjaWZpY2F0aW9uIGlzIHJldmlld2VkIGJhc2VkIG9uIHRo
ZSBsYXN0IHJvdW5kIG9mIEFEIA0KPiA+ID4gY29tbWVudHMgKHRoYW5rcyBZb3NoaSEpLg0KPiA+
ID4gDQo+ID4gPiBUaGUgc3BlYyBpcyBoZXJlOiANCj4gPiA+IA0KPiA+ID4gaHR0cDovL3d3dy5w
YW5hc2VjLm9yZy9kb2NzL2VkaXRpbmcvZHJhZnQtaWV0Zi1wYW5hLXBhbmEtMTVhLnR4dA0KPiA+
ID4gDQo+ID4gPiBBbmQgaXQncyBkaWZmIHdpdGggdGhlIHZlcnNpb24gdGhhdCBwcmVkYXRlcyBs
YXN0IHJvdW5kIG9mIEFEIA0KPiA+ID4gY29tbWVudHMNCj4gPiA+ICgtMTMpOiANCj4gPiA+IA0K
PiA+ID4gaHR0cDovL3d3dy5wYW5hc2VjLm9yZy9kb2NzL2VkaXRpbmcvZHJhZnQtaWV0Zi1wYW5h
LXBhbmEtMTVhLWYNCj4gPiA+IHJvbS0zLmRpZmYuaHRtDQo+ID4gPiBsDQo+ID4gPiANCj4gPiA+
IFBsZWFzZSByZXZpZXcgdGhlIGRvY3VtZW50IGFuZCByZWdpc3RlciB5b3VyIGZlZWRiYWNrIGJ5
IA0KPiB0aGUgZW5kIG9mIA0KPiA+ID4gQXByaWwgMTIsIFRodXJzZGF5Lg0KPiA+ID4gDQo+ID4g
PiBVcG9uIGNvbGxlY3RpbmcgYW5kIHJlc29sdmluZyBhbnkgaXNzdWVzLCB0aGUgZG9jdW1lbnQg
DQo+IHdpbGwgcHJvY2VlZCANCj4gPiA+IHRvIElFVEYgbGFzdCBjYWxsLg0KPiA+ID4gDQo+ID4g
PiBUaGFua3MNCj4gPiA+IA0KPiA+ID4gQWxwZXINCj4gPiA+IA0KPiA+ID4gDQo+ID4gPiANCj4g
PiA+IA0KPiA+ID4gDQo+ID4gPiANCj4gPiA+IA0KPiA+ID4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiA+IFBhbmEgbWFpbGluZyBsaXN0DQo+ID4g
PiBQYW5hQGlldGYub3JnDQo+ID4gPiBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9wYW5hDQo+ID4gPiANCj4gPiANCj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPiA+IFBhbmEgbWFpbGluZyBsaXN0DQo+ID4gUGFuYUBpZXRm
Lm9yZw0KPiA+IGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BhbmENCj4g
PiANCj4gPiANCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQo+IFBhbmEgbWFpbGluZyBsaXN0DQo+IFBhbmFAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93
d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcGFuYQ0KPiANCg==


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

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

--===============0655801011==--



From pana-bounces@ietf.org Fri Apr 13 05:35:50 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcIC2-0007v4-GC; Fri, 13 Apr 2007 05:35:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcIC0-0007uu-4D
	for pana@ietf.org; Fri, 13 Apr 2007 05:35:44 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcIBx-0005qC-Jp
	for pana@ietf.org; Fri, 13 Apr 2007 05:35:44 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Apr 2007 11:35:39 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Pana] Use of Error Request message
Date: Fri, 13 Apr 2007 11:35:36 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB02604784A1B@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <20070412174338.GC31369@steelhead>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] Use of Error Request message
Thread-Index: Acd9KiBcpwlAJuAmT2+Rx1dAe62slwAgS5TQ
References: <461E51F2.8030906@tari.toshiba.com><7DBAFEC6A76F3E42817DF1EBE64CB026047848B1@FTRDMEL2.rd.francetelecom.fr>
	<20070412174338.GC31369@steelhead>
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
X-OriginalArrivalTime: 13 Apr 2007 09:35:39.0058 (UTC)
	FILETIME=[18B48120:01C77DAF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
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>
Content-Type: multipart/mixed; boundary="===============0933463308=="
Errors-To: pana-bounces@ietf.org

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

SGkgWW9zaGksDQoNCg0KPiAtLS0tLU1lc3NhZ2UgZCdvcmlnaW5lLS0tLS0NCj4gRGUgOiBZb3No
aWhpcm8gT2hiYSBbbWFpbHRvOnlvaGJhQHRhcmkudG9zaGliYS5jb21dIA0KPiBFbnZvecOpIDog
amV1ZGkgMTIgYXZyaWwgMjAwNyAxOTo0NA0KPiDDgCA6IE1PUkFORCBMaW9uZWwgUkQtQ09SRS1J
U1MNCj4gQ2MgOiBWaWN0b3IgRmFqYXJkbzsgcGFuYUBpZXRmLm9yZw0KPiBPYmpldCA6IFJlOiBb
UGFuYV0gVXNlIG9mIEVycm9yIFJlcXVlc3QgbWVzc2FnZQ0KPiANCj4gSGkgTGlvbmVsLA0KPiAN
Cj4gT24gVGh1LCBBcHIgMTIsIDIwMDcgYXQgMDU6NDc6NDJQTSArMDIwMCwgTU9SQU5EIExpb25l
bCANCj4gUkQtQ09SRS1JU1Mgd3JvdGU6DQo+ID4gSGkgVmljdG9yLA0KPiA+IA0KPiA+IEkgY2Fu
IGFncmVlIHRob3VnaCBpdCBpcyBxdWl0ZSBzdHJhbmdlIHRvIGhhdmUgYSBSZXF1ZXN0L0Fuc3dl
ciANCj4gPiBtZXNzYWdlcyBwcm90b2NvbHMgYW5kIHRvIHNlZSBhIFBBTkEtTm90aWZpY2F0aW9u
LVJlcXVlc3QgDQo+IG1lc3NhZ2UgaW4gDQo+ID4gcmVzcG9uc2UgdG8gUEFOQS1BdXRoLVJlcXVl
c3QgOykNCj4gDQo+IFRvIG1lIGVycm9yIG1lc3NhZ2VzIGFyZSBzb3J0IG9mICJpbnRlcnJ1cHRp
b25zIiwgc28gSSBkb24ndCANCj4gc2VlIGl0IHN0cmFuZ2UgdG8gc2VuZCBhbiBlcnJvciByZXF1
ZXN0IGluIHJlc3BvbnNlIHRvIGEgDQo+IHJlcXVlc3Qgb3IgYW4gYW5zd2VyLg0KDQpJIHdhcyBq
dXN0IHNheWluZyB0aGF0IGluIHRoZSBwcmluY2lwbGUgb2YgRGlhbWV0ZXIgKHRoYXQgd2FzIGlu
IG15IHVuZGVyc3RhbmRpbmcgdGhlIHJlZmVyZW5jZSBwcm90b2NvbCBmb3IgdGhlIFBBTkEgcHJv
dG9jbyBkZXNpZ24pLCB0aGUgbG9naWMgd2FzOiBhIFJlcXVlc3QgbWVzc2FnZSBhc3NvY2lhdGVk
IHdpdGggYW4gQW5zd2VyIG1lc3NhZ2Ugd2l0aCBhIFJlc3VsdC1Db2RlIChTdWNjZXNzIG9yIEZh
aWx1cmUpLCBhbmQgdGhlIEZhaWx1cmUgaW5jbHVkaW5nIGVycm9yIGNhc2VzLiBUaGUgb25seSBj
YXNlIHdoZXJlIHRoaXMgbWVjaGFuaXNtIGlzIG5vdCB1c2VmdWwgaXMgd2hlbiBlcnJvcnMgb2Nj
dXIgaW4gdGhlIGFuc3dlciBtZXNzYWdlIGhhbmRsaW5nLg0KICANCj4gDQo+ID4gVGhlIHByb3Bv
c2VkIG1vZGlmaWNhdGlvbiBkb2Vzbid0IGNoYW5nZSB0aGUgcHJpbmNpcGxlIG9mIHRoZSBlcnJv
ciANCj4gPiBoYW5kbGluZyBtZWNoYW5pc20uIEJ1dCBJIHRoaW5rIGl0IGNvdWxkIGJlIHNlZW4g
bW9yZSANCj4gY29uc2lzdGVudC4gQXQgDQo+ID4gbGVhc3QgZm9yIG1lIDspDQo+IA0KPiBGcm9t
IG15IERpYW1ldGVyIHBhcnNlciBpbXBsZW1lbnRhdGlvbiBleHBlcmllbmNlLCBkZWZpbmluZyAN
Cj4gdHdvIHR5cGVzIG9mIEFCTkYgZm9yIGFuc3dlciBtZXNzYWdlcyBkZXBlbmRpbmcgb24gJ0Un
IGJpdCANCj4gc2V0dGluZ3MgaXMgbW9yZSBjb21wbGV4LiAgSSBiZWxpZXZlIHRoZSB3YXkgY3Vy
cmVudGx5IFBBTkEgDQo+IGlzIGRlZmluZWQgaXMgbXVjaCBzaW1wbGVyLg0KDQoNCkl0IGlzIG5v
dCB0byBkZWZpbmUgdHdvIHR5cGVzIG9mIEFCTkYuIEl0IGlzIHRvIGRlZmluZSB0aGUgUmVzdWx0
LUNvZGUgQVZQIGFuZCBGYWlsZWQtQVZQIEFWUCBhcyBvcHRpb25hbCBBVlBzIG9mIHRoZSBQQU5B
LUF1dGgtQW5zd2VyIGFuZCBQQU5BLVRlcm1pbmF0aW9uLUFuc3dlciBtZXNzYWdlcy4gSSB3YXMg
cHJvcG9zaW5nIHRvIHJldXNlIHRoZSAnRScgYml0IGp1c3QgdG8gY2hhcmFjdGVyaXplIGVycm9y
IGFuc3dlcnMgaWYgbmVlZGVkLCBhcyBhIGhpbnQuDQpBYm91dCBjb21wbGV4aXR5LCBkbyB5b3Ug
bWVhbiB0aGF0IGl0IGlzIGVhc2llciBmb3IgdGhlIGltcGxlbWVudGF0aW9uIHRvIHBhcnNlIGEg
Tm90aWZpY2F0aW9uIG1lc3NhZ2UgdG8gZmluZCB0aGUgb3B0aW9uYWwgRmFpbGVkLU1lc3NhZ2Ut
SGVhZGVyIEFWUCB0byBmaW5kIHRoZSBtZXNzYWdlIHRoYXQgY2F1c2VzIHRoZSBlcnJvcj8NCg0K
TGlvbmVsDQoNCg0KPiANCj4gWW9zaGloaXJvIE9oYmENCj4gDQo+IA0KPiANCj4gPiANCj4gPiAN
Cj4gPiANCj4gPiA+IC0tLS0tTWVzc2FnZSBkJ29yaWdpbmUtLS0tLQ0KPiA+ID4gRGUgOiBWaWN0
b3IgRmFqYXJkbyBbbWFpbHRvOnZmYWphcmRvQHRhcmkudG9zaGliYS5jb21dDQo+ID4gPiBFbnZv
ee+8nyA6IGpldWRpIDEyIGF2cmlsIDIwMDcgMTc6MzYNCj4gPiA+IO+8nyA6IE1PUkFORCBMaW9u
ZWwgUkQtQ09SRS1JU1MNCj4gPiA+IENjIDogcGFuYUBpZXRmLm9yZw0KPiA+ID4gT2JqZXQgOiBS
ZTogW1BhbmFdIFVzZSBvZiBFcnJvciBSZXF1ZXN0IG1lc3NhZ2UNCj4gPiA+IA0KPiA+ID4gSGkg
TGlvbmVsLA0KPiA+ID4gPiBJIHByb3Bvc2UgdG8gbGltaXQgdGhlIHVzZSBvZiB0aGlzIHNwZWNp
ZmljIG1lY2hhbmlzbSB0bw0KPiA+ID4gdGhlIGhhbmRsaW5nIG9mIGVycm9ycyBkdWUgdG8gUEFO
QSBhbnN3ZXIgbWVzc2FnZXMgDQo+IHJlY2VpdmVkIGJ5IHRoZSANCj4gPiA+IHBlZXIuIEluIHRo
YXQgc3BlY2lmaWMgY2FzZSwgaXQgaXMgYWN0dWFsbHkgdGhlIG9ubHkgd2F5IGZvciANCj4gPiA+
IHByb3ZpZGluZyBlcnJvciBub3RpZmljYXRpb24gdG8gdGhlIG9yaWdpbmF0b3Igb2YgdGhlIA0K
PiBhbnN3ZXIgbWVzc2FnZSANCj4gPiA+IChpZiBuZWVkZWQpLg0KPiA+ID4gPg0KPiA+ID4gPiBP
biB0aGUgb3RoZXIgaGFuZCwgZm9yIHRoZSBoYW5kbGluZyBvZiBQQU5BIHJlcXVlc3QNCj4gPiA+
IG1lc3NhZ2VzLCBpdCBpcyBlYXNpZXIgdG8gYWx3YXlzIHJlbHkgb24gUEFOQSBhbnN3ZXIgbWVz
c2FnZXMgZm9yIA0KPiA+ID4gcHJvdmlkaW5nIGVycm9yIG5vdGlmaWNhdGlvbiB0byB0aGUgb3Jp
Z2luYXRvciBvZiB0aGUgcmVxdWVzdCwgYXMgDQo+ID4gPiBkb25lIGUuZy4gd2l0aCBEaWFtZXRl
ci4NCj4gPiA+ID4gVGhlICdFJyBiaXQgd291bGQgYmUgc2V0IGluIHRoZSBhbnN3ZXIgbWVzc2Fn
ZSBoZWFkZXIgaW4NCj4gPiA+IG9yZGVyIHRvIGRpc3Rpbmd1aXNoIGVycm9yIG5vdGlmaWNhdGlv
biBmcm9tICJub3JtYWwiIGFuc3dlciANCj4gPiA+IG1lc3NhZ2VzIChzb21lIFBBTkEgYW5zd2Vy
IG1lc3NhZ2VzIGJlaW5nIHVzZWQganVzdCBhcyANCj4gYWNrIG1lc3NhZ2VzKS4NCj4gPiA+ID4g
V2hlbiB0aGUgJ0UnIGJpdCBpcyBzZXQgaW4gYW5zd2VyIG1lc3NhZ2UsIHRoZSBSZXN1bHQtQ29k
ZQ0KPiA+ID4gQVZQIHdvdWxkIGhhdmUgdG8gYmUgcHJlc2VudCBhcyB3ZWxsIGFzIHRoZSBGYWls
ZWQtQVZQIA0KPiBBVlAgaWYgbmVlZGVkLg0KPiA+ID4gPg0KPiA+ID4gPiBBbnkgY29tbWVudD8N
Cj4gPiA+ID4gICANCj4gPiA+IA0KPiA+ID4gVGhlIHByb3Bvc2FsIHNob3VsZCB3b3JrIHRob3Vn
aCBJJ20gbm90IHN1cmUgd2hhdCB0aGUgYWRkaXRpb25hbCANCj4gPiA+IGJlbmVmaXQgd291bGQg
YmUgZXhjZXB0IG1heWJlIHRoZSBzYXZpbmdzIG9mIG5vdCBoYXZpbmcgDQo+IHRvIHNlbmQgdGhl
IA0KPiA+ID4gbm90aWZpY2F0aW9uIGFuc3dlciBtZXNzYWdlIGluIHRoZSBsYXR0ZXIgY2FzZS4g
IEhvd2V2ZXIsIA0KPiBtYXliZSBzdWNoIA0KPiA+ID4gb3B0aW1pemF0aW9uIGlzIG5vdCBzbyBy
ZWxldmFudCBzaW5jZSBlcnJvciBjb25kaXRpb25zIA0KPiBhcmUgbm90IHRoZSANCj4gPiA+IG5v
cm0uIEkgZ2VuZXJhbGx5IGxpa2UgdGhlIGN1cnJlbnQgc2NoZW1lICh1c2UgZXJyb3Igbm90aWZp
Y2F0aW9uIA0KPiA+ID4gbWVzc2FnZXMpIGJlY2F1c2UgaXQga2VlcHMgdGhpbmdzIHNpbXBsZSBi
eSBjZW50cmFsaXppbmcgZXJyb3IgDQo+ID4gPiBpbmRpY2F0aW9ucyBmb3IgYWxsIGNhc2VzLg0K
PiA+ID4gDQo+ID4gPiBBcyBhIHNpZGUgbm90ZSwgb25lIG1pbm9yIHN1Z2dlc3Rpb24gZm9yIDUu
OCBpcyB0byBpbmNsdWRlIHNtYWxsIA0KPiA+ID4gdGV4dCBleHBsaWNpdGx5IHRlcm1pbmF0aW5n
IHRoZSByZXF1ZXN0IHJldHJhbnNtaXNzaW9uIHByb2NlZHVyZSANCj4gPiA+IHdoZW4gZXJyb3Ig
bm90aWZpY2F0aW9uIGlzIHJlY2VpdmVkIGZvciBhIHBlbmRpbmcgcmVxdWVzdC4NCj4gPiA+IA0K
PiA+ID4gcmVnYXJkcywNCj4gPiA+IHZpY3Rvcg0KPiA+ID4gPiBMaW9uZWwNCj4gPiA+ID4NCj4g
PiA+ID4NCj4gPiA+ID4gICANCj4gPiA+ID4+IC0tLS0tTWVzc2FnZSBkJ29yaWdpbmUtLS0tLQ0K
PiA+ID4gPj4gRGUgOiBBbHBlciBZZWdpbiBbbWFpbHRvOmFscGVyLnllZ2luQHllZ2luLm9yZ10g
RW52b3nvvJ8gDQo+IDogamV1ZGkgNSANCj4gPiA+ID4+IGF2cmlsIDIwMDcgMTA6MDYg77yfIDog
cGFuYUBpZXRmLm9yZyBPYmpldCA6IFtQYW5hXSBSZXZpZXcgDQo+ID4gPiA+PiBwYW5hLXBhbmEt
MTVhDQo+ID4gPiA+Pg0KPiA+ID4gPj4NCj4gPiA+ID4+IFBBTkEgc3BlY2lmaWNhdGlvbiBpcyBy
ZXZpZXdlZCBiYXNlZCBvbiB0aGUgbGFzdCByb3VuZCBvZg0KPiA+ID4gQUQgY29tbWVudHMNCj4g
PiA+ID4+ICh0aGFua3MgWW9zaGkhKS4NCj4gPiA+ID4+DQo+ID4gPiA+PiBUaGUgc3BlYyBpcyBo
ZXJlOiANCj4gPiA+ID4+DQo+ID4gPiA+PiANCj4gaHR0cDovL3d3dy5wYW5hc2VjLm9yZy9kb2Nz
L2VkaXRpbmcvZHJhZnQtaWV0Zi1wYW5hLXBhbmEtMTVhLnR4dA0KPiA+ID4gPj4NCj4gPiA+ID4+
IEFuZCBpdCdzIGRpZmYgd2l0aCB0aGUgdmVyc2lvbiB0aGF0IHByZWRhdGVzIGxhc3Qgcm91bmQg
b2YgQUQgDQo+ID4gPiA+PiBjb21tZW50cw0KPiA+ID4gPj4gKC0xMyk6IA0KPiA+ID4gPj4NCj4g
PiA+ID4+IGh0dHA6Ly93d3cucGFuYXNlYy5vcmcvZG9jcy9lZGl0aW5nL2RyYWZ0LWlldGYtcGFu
YS1wYW5hLTE1YS1mDQo+ID4gPiA+PiByb20tMy5kaWZmLmh0bQ0KPiA+ID4gPj4gbA0KPiA+ID4g
Pj4NCj4gPiA+ID4+IFBsZWFzZSByZXZpZXcgdGhlIGRvY3VtZW50IGFuZCByZWdpc3RlciB5b3Vy
IGZlZWRiYWNrIGJ5DQo+ID4gPiB0aGUgZW5kIG9mDQo+ID4gPiA+PiBBcHJpbCAxMiwgVGh1cnNk
YXkuDQo+ID4gPiA+Pg0KPiA+ID4gPj4gVXBvbiBjb2xsZWN0aW5nIGFuZCByZXNvbHZpbmcgYW55
IGlzc3VlcywgdGhlIGRvY3VtZW50DQo+ID4gPiB3aWxsIHByb2NlZWQNCj4gPiA+ID4+IHRvIElF
VEYgbGFzdCBjYWxsLg0KPiA+ID4gPj4NCj4gPiA+ID4+IFRoYW5rcw0KPiA+ID4gPj4NCj4gPiA+
ID4+IEFscGVyDQo+ID4gPiA+Pg0KPiA+ID4gPj4NCj4gPiA+ID4+DQo+ID4gPiA+Pg0KPiA+ID4g
Pj4NCj4gPiA+ID4+DQo+ID4gPiA+Pg0KPiA+ID4gPj4gX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj4gPiA+ID4+IFBhbmEgbWFpbGluZyBsaXN0DQo+ID4g
PiA+PiBQYW5hQGlldGYub3JnDQo+ID4gPiA+PiBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9wYW5hDQo+ID4gPiA+Pg0KPiA+ID4gPj4gICAgIA0KPiA+ID4gPg0KPiA+ID4g
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+ID4g
PiBQYW5hIG1haWxpbmcgbGlzdA0KPiA+ID4gPiBQYW5hQGlldGYub3JnDQo+ID4gPiA+IGh0dHBz
Oi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3BhbmENCj4gPiA+ID4NCj4gPiA+ID4N
Cj4gPiA+ID4NCj4gPiA+ID4gICANCj4gPiA+IA0KPiA+ID4gDQo+ID4gPiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+ID4gUGFuYSBtYWlsaW5nIGxp
c3QNCj4gPiA+IFBhbmFAaWV0Zi5vcmcNCj4gPiA+IGh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL3BhbmENCj4gPiA+IA0KPiA+IA0KPiA+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gUGFuYSBtYWlsaW5nIGxpc3QNCj4gPiBQ
YW5hQGlldGYub3JnDQo+ID4gaHR0cHM6Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
cGFuYQ0KPiA+IA0KPiA+IA0KPiANCg==


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

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

--===============0933463308==--



From pana-bounces@ietf.org Fri Apr 13 10:17:21 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcMaT-0001F8-Ut; Fri, 13 Apr 2007 10:17:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcMaS-0001Dk-Rp
	for pana@ietf.org; Fri, 13 Apr 2007 10:17:16 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcMaR-0005Wv-EE
	for pana@ietf.org; Fri, 13 Apr 2007 10:17:16 -0400
Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3DEGuWE063632; Fri, 13 Apr 2007 10:16:56 -0400 (EDT)
	(envelope-from vfajardo@tari.toshiba.com)
Message-ID: <461F9137.7050807@tari.toshiba.com>
Date: Fri, 13 Apr 2007 10:18:31 -0400
From: Victor Fajardo <vfajardo@tari.toshiba.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.com>
Subject: Re: [Pana] Use of Error Request message
References: <461E51F2.8030906@tari.toshiba.com><7DBAFEC6A76F3E42817DF1EBE64CB026047848B1@FTRDMEL2.rd.francetelecom.fr>
	<20070412174338.GC31369@steelhead>
	<7DBAFEC6A76F3E42817DF1EBE64CB02604784A1B@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <7DBAFEC6A76F3E42817DF1EBE64CB02604784A1B@FTRDMEL2.rd.francetelecom.fr>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.4 (--)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
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>
Errors-To: pana-bounces@ietf.org

Hi Lionel,

>
> It is not to define two types of ABNF. It is to define the Result-Code AVP and Failed-AVP AVP as optional AVPs of the PANA-Auth-Answer and PANA-Termination-Answer messages. I was proposing to reuse the 'E' bit just to characterize error answers if needed, as a hint.
> About complexity, do you mean that it is easier for the implementation to parse a Notification message to find the optional Failed-Message-Header AVP to find the message that causes the error?
>   

The use of error notification maybe a little more simple for 
implementation processing because that single message can be treated as 
a catch all event or interruption as oppose to having a few more 
additional conditions testing for errors in every other incoming answer 
messages. In that sense, unifying error notification to a single message 
has some advantages.

best regards,
victor


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



From pana-bounces@ietf.org Fri Apr 13 10:29:45 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcMmW-0001BL-Ns; Fri, 13 Apr 2007 10:29:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcMmV-0001B8-9d
	for pana@ietf.org; Fri, 13 Apr 2007 10:29:43 -0400
Received: from imx12.toshiba.co.jp ([61.202.160.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcMmT-0001zk-GU
	for pana@ietf.org; Fri, 13 Apr 2007 10:29:43 -0400
Received: from wall11.toshiba.co.jp (wall11 [133.199.90.149])
	by imx12.toshiba.co.jp  with ESMTP id l3DETe6G018934;
	Fri, 13 Apr 2007 23:29:40 +0900 (JST)
Received: (from root@localhost) by wall11.toshiba.co.jp  id l3DETdKK000044;
	Fri, 13 Apr 2007 23:29:39 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] 
	by wall11.toshiba.co.jp with ESMTP id ZAA00041;
	Fri, 13 Apr 2007 23:29:39 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp11.toshiba.co.jp  with ESMTP id l3DETc5j021603;
	Fri, 13 Apr 2007 23:29:39 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3DETc3O025789;
	Fri, 13 Apr 2007 23:29:38 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGF00F8IXKYNU40@mail.po.toshiba.co.jp>; Fri,
	13 Apr 2007 23:29:38 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1HcMmB-0005HS-EU; Fri,
	13 Apr 2007 07:29:23 -0700
Date: Fri, 13 Apr 2007 10:29:23 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] IP address of the PaC in the PANA session attribute
In-reply-to: <7DBAFEC6A76F3E42817DF1EBE64CB026047849BE@FTRDMEL2.rd.francetelecom.fr>
To: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.com>
Message-id: <20070413142922.GD19392@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=euc-jp
Content-disposition: inline
References: <20070412171139.GB31369@steelhead>
	<7DBAFEC6A76F3E42817DF1EBE64CB026047849BE@FTRDMEL2.rd.francetelecom.fr>
User-Agent: Mutt/1.5.13 (2006-08-11)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by imx12.toshiba.co.jp id
	l3DETe6G018934
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
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>
Errors-To: pana-bounces@ietf.org

On Fri, Apr 13, 2007 at 10:30:23AM +0200, MORAND Lionel RD-CORE-ISS wrote=
:
> Hi Yoshi,
>=20
> Maybe I was confusing! I'm not saying that the IP address/port number s=
hould not be part of the PANA session attributes.
> I'm just saying that the wording:
>=20
>        *  IP address and UDP port number of the PaC.
>=20
> Might not be correct if you are considering NAT. But it is not a strong=
 point for me. Just a Nice-to-Have if considered to be useful.

I think it is correct in that PAA considers NAT as PaC.

Yoshihiro Ohba


>=20
> BR,
>=20
> Lionel
>=20
> > -----Message d'origine-----
> > De : Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]=20
> > Envoy=8F=AB=B1 : jeudi 12 avril 2007 19:12
> > =8F=AA=A2 : MORAND Lionel RD-CORE-ISS
> > Cc : pana@ietf.org
> > Objet : Re: [Pana] IP address of the PaC in the PANA session attribut=
e
> >=20
> > Hi Lionel,
> >=20
> > When NAT exists between PaC and PAA, the IP address and port=20
> > number of the PaC will simply point to the ones used by NAT. =20
> > If the IP address and/or port of PaC changes, the IP address=20
> > and port number attributes will be modified to the new ones=20
> > based on the IP address update procedure defined in Section=20
> > 5.6.  Said that I don't see a problem with containing IP=20
> > address and port number in the PANA session attributes.
> >=20
> > Yoshihiro Ohba
> >=20
> >=20
> > On Thu, Apr 12, 2007 at 05:55:45PM +0200, MORAND Lionel=20
> > RD-CORE-ISS wrote:
> > > Hi,
> > >=20
> > > There is a description of the PANA session attributes in=20
> > the section 5.3:
> > >=20
> > >    "PANA SA attributes as well as PANA session attributes are liste=
d
> > >    below:
> > >=20
> > >    PANA Session attributes:
> > >=20
> > >       *  Session Identifier
> > >=20
> > >       *  IP address and UDP port number of the PaC.
> > >=20
> > >       *  IP address and UDP port number of the PAA
> > >=20
> > >       *  Sequence number of the last transmitted request
> > >=20
> > >       *  Sequence number of the last received request
> > >=20
> > >       *  Last transmitted message payload
> > >=20
> > >       *  Retransmission interval
> > >=20
> > >       *  Session lifetime
> > >=20
> > >       *  PANA SA attributes "
> > >=20
> > > A NAT may exist between the PaC and the PAA (that is=20
> > already covered=20
> > > in section 6.1). Therefore, the PaC IP address/UDP port=20
> > number should=20
> > > not be part of the PANA session attributes. Instead, we should have=
=20
> > > the source IP address and the UDP source port number of the last=20
> > > PaC-initiated PANA messages (to take into account the fact that the=
=20
> > > PaC may change its IP address cf. section 5.6). I don't have any=20
> > > concrete proposal for improving the current text... But maybe it is=
=20
> > > not needed if my comment is not valid at all ;)
> > >=20
> > > Lionel
> > >=20
> > > > -----Message d'origine-----
> > > > De : Alper Yegin [mailto:alper.yegin@yegin.org]
> > > > Envoy=A1=A9 : jeudi 5 avril 2007 10:06
> > > > =A1=A9 : pana@ietf.org
> > > > Objet : [Pana] Review pana-pana-15a
> > > >=20
> > > >=20
> > > > PANA specification is reviewed based on the last round of AD=20
> > > > comments (thanks Yoshi!).
> > > >=20
> > > > The spec is here:=20
> > > >=20
> > > > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
> > > >=20
> > > > And it's diff with the version that predates last round of AD=20
> > > > comments
> > > > (-13):=20
> > > >=20
> > > > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> > > > rom-3.diff.htm
> > > > l
> > > >=20
> > > > Please review the document and register your feedback by=20
> > the end of=20
> > > > April 12, Thursday.
> > > >=20
> > > > Upon collecting and resolving any issues, the document=20
> > will proceed=20
> > > > to IETF last call.
> > > >=20
> > > > Thanks
> > > >=20
> > > > Alper
> > > >=20
> > > >=20
> > > >=20
> > > >=20
> > > >=20
> > > >=20
> > > >=20
> > > > _______________________________________________
> > > > Pana mailing list
> > > > Pana@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pana
> > > >=20
> > >=20
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > >=20
> > >=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
>=20

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



From pana-bounces@ietf.org Fri Apr 13 12:37:18 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcOly-0002x4-0f; Fri, 13 Apr 2007 12:37:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcOlx-0002wy-0R
	for pana@ietf.org; Fri, 13 Apr 2007 12:37:17 -0400
Received: from mail.um.es ([155.54.212.109])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcOlv-0005lk-G7
	for pana@ietf.org; Fri, 13 Apr 2007 12:37:16 -0400
Received: from localhost (localhost [127.0.0.1])
	by mail.um.es (Postfix) with ESMTP id C306B23D1E9
	for <pana@ietf.org>; Fri, 13 Apr 2007 18:37:14 +0200 (CEST)
Received: from mail.um.es ([127.0.0.1])
	by localhost (xenon2 [127.0.0.1]) (amavisd-new, port 10024) with LMTP
	id 14701-01-75; Fri, 13 Apr 2007 18:37:12 +0200 (CEST)
Received: from [155.54.205.13] (inf-205-13.um.es [155.54.205.13])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.um.es (Postfix) with ESMTP id 5AC0023D1C0;
	Fri, 13 Apr 2007 18:37:10 +0200 (CEST)
Message-ID: <461FB1B9.9060405@dif.um.es>
Date: Fri, 13 Apr 2007 18:37:13 +0200
From: Rafa Marin Lopez <rafa@dif.um.es>
Organization: University of Murcia
User-Agent: Thunderbird 1.5.0.8 (X11/20061115)
MIME-Version: 1.0
To: pana@ietf.org
Subject: Re: [Pana] Review pana-pana-15a
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
In-Reply-To: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at telemat.um.es
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: Rafa Marin Lopez <rafa@dif.um.es>
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>
Errors-To: pana-bounces@ietf.org

Hi all, I did my review and the document is a good shape to me...

only some minor comments

1.Introduction

...

"By the virtue of enabling transport of EAP
above IP, any authentication method that can be carried as an EAP
method is made available to PANA and hence to any link-layer
technology"...

I don't understand the conclusion in this sentence "hence to any=20
link-layer ..."

Maybe it should be enough

"By the virtue of enabling transport of EAP
above IP, any authentication method that can be carried as an EAP
method is made available to PANA".

In section 4.1

In case of PAA is stateful... might it be possible that PAA sends nonces=20
in the initial PANA-Auth-Req/Resp

 >From the text

"A Nonce AVP MUST be included in the first non-initial PANA-Auth-Request =
and PANA-Auth-Answer messages,=20
and MUST NOT be included in any other message."

, it seems not

My question why it is not possible to include them in the initial=20
PANA-Auth-Request/Resp?


Just the line before section 5.4

Key-ID AVP. ---> Key-Id AVP.

My best regards.




Alper Yegin escribi=F3:
> PANA specification is reviewed based on the last round of AD comments
> (thanks Yoshi!).
>
> The spec is here:=20
>
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
>
> And it's diff with the version that predates last round of AD comments
> (-13):=20
>
> http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-from-3.dif=
f.htm
> l
>
> Please review the document and register your feedback by the end of Apr=
il
> 12, Thursday.
>
> Upon collecting and resolving any issues, the document will proceed to =
IETF
> last call.
>
> Thanks
>
> Alper
>
>
>
>
>
>
>
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>
>
>  =20


--=20
------------------------------------------------------
Rafael Marin Lopez
Depto. Ing. de la Info. y las Comunicaciones
Faculty of Computer Science-University of Murcia
30100 Murcia - Spain
Telf: +34968398501    e-mail: rafa@dif.um.es
------------------------------------------------------


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



From pana-bounces@ietf.org Fri Apr 13 13:23:22 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcPUX-0006vH-Iu; Fri, 13 Apr 2007 13:23:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcPUW-0006v9-GF
	for pana@ietf.org; Fri, 13 Apr 2007 13:23:20 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcPUU-0003H9-S2
	for pana@ietf.org; Fri, 13 Apr 2007 13:23:20 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3DHNGT8029589;
	Sat, 14 Apr 2007 02:23:16 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3DHNHCs027343;
	Sat, 14 Apr 2007 02:23:17 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id CAA27340;
	Sat, 14 Apr 2007 02:23:16 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3DHNG7i024445;
	Sat, 14 Apr 2007 02:23:16 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3DHNGvb018322;
	Sat, 14 Apr 2007 02:23:16 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGG00FNB5M6NT40@mail.po.toshiba.co.jp>; Sat,
	14 Apr 2007 02:23:16 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1HcPU4-0006XO-JF; Fri,
	13 Apr 2007 10:22:52 -0700
Date: Fri, 13 Apr 2007 13:22:52 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Use of Error Request message
In-reply-to: <461E51F2.8030906@tari.toshiba.com>
To: Victor Fajardo <vfajardo@tari.toshiba.com>
Message-id: <20070413172252.GH19392@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
	<7DBAFEC6A76F3E42817DF1EBE64CB02604784626@FTRDMEL2.rd.francetelecom.fr>
	<461E51F2.8030906@tari.toshiba.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.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>
Errors-To: pana-bounces@ietf.org

Victor,

On Thu, Apr 12, 2007 at 11:36:18AM -0400, Victor Fajardo wrote:
> 
> As a side note, one minor suggestion for 5.8 is to include small text 
> explicitly terminating the request retransmission procedure when error 
> notification is received for a pending request.
> 

I have check the spec and there is some text sepcifying that behavior 
on Section 9:

"
   PANA retransmission timers are based on the model used in DHCPv6
   [RFC3315].  Variables used here are also borrowed from this
   specification.  PANA is a request/response-based protocol.  The
   message exchange terminates when the requester successfully receives
   the answer, a protected error message for the request is received, or
   the message exchange is considered to have failed according to the
   retransmission mechanism described below.
"

Isn't this sufficient?

Yoshihiro Ohba

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



From pana-bounces@ietf.org Fri Apr 13 14:31:55 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcQYm-0008WF-I7; Fri, 13 Apr 2007 14:31:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcQYl-0008WA-9E
	for pana@ietf.org; Fri, 13 Apr 2007 14:31:47 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcQYj-0001CF-WE
	for pana@ietf.org; Fri, 13 Apr 2007 14:31:47 -0400
Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3DIVPS0065063; Fri, 13 Apr 2007 14:31:25 -0400 (EDT)
	(envelope-from vfajardo@tari.toshiba.com)
Message-ID: <461FCCEA.6090006@tari.toshiba.com>
Date: Fri, 13 Apr 2007 14:33:14 -0400
From: Victor Fajardo <vfajardo@tari.toshiba.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Use of Error Request message
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
	<7DBAFEC6A76F3E42817DF1EBE64CB02604784626@FTRDMEL2.rd.francetelecom.fr>
	<461E51F2.8030906@tari.toshiba.com>
	<20070413172252.GH19392@steelhead>
In-Reply-To: <20070413172252.GH19392@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.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>
Errors-To: pana-bounces@ietf.org

Hi,
>> As a side note, one minor suggestion for 5.8 is to include small text 
>> explicitly terminating the request retransmission procedure when error 
>> notification is received for a pending request.
>>
>>     
>
> I have check the spec and there is some text sepcifying that behavior 
> on Section 9:
>
> "
>    PANA retransmission timers are based on the model used in DHCPv6
>    [RFC3315].  Variables used here are also borrowed from this
>    specification.  PANA is a request/response-based protocol.  The
>    message exchange terminates when the requester successfully receives
>    the answer, a protected error message for the request is received, or
>    the message exchange is considered to have failed according to the
>    retransmission mechanism described below.
> "
>
> Isn't this sufficient?
>   

I think this is ok.

-- victor


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



From pana-bounces@ietf.org Sat Apr 14 00:12:45 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcZcr-0005CL-Iy; Sat, 14 Apr 2007 00:12:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcZcp-0005C0-Ik
	for pana@ietf.org; Sat, 14 Apr 2007 00:12:35 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcZco-0003CN-5D
	for pana@ietf.org; Sat, 14 Apr 2007 00:12:35 -0400
Received: from localhost (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3E4CBAE066753; Sat, 14 Apr 2007 00:12:11 -0400 (EDT)
	(envelope-from yohba@tari.toshiba.com)
Date: Sat, 14 Apr 2007 00:12:12 -0400
To: Rafa Marin Lopez <rafa@dif.um.es>
Subject: Re: [Pana] Review pana-pana-15a
Message-ID: <20070414041212.GC31340@steelhead>
References: <0MKp2t-1HZMya14iQ-0008Ve@mrelay.perfora.net>
	<461FB1B9.9060405@dif.um.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=euc-jp
Content-Disposition: inline
In-Reply-To: <461FB1B9.9060405@dif.um.es>
User-Agent: Mutt/1.5.13 (2006-08-11)
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20050308(IM148)
Lines: 118
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by
	toshi17.tari.toshiba.com id l3E4CBAE066753
X-Spam-Score: -2.4 (--)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
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>
Errors-To: pana-bounces@ietf.org

On Fri, Apr 13, 2007 at 06:37:13PM +0200, Rafa Marin Lopez wrote:
> Hi all, I did my review and the document is a good shape to me...
>=20
> only some minor comments
>=20
> 1.Introduction
>=20
> ...
>=20
> "By the virtue of enabling transport of EAP
> above IP, any authentication method that can be carried as an EAP
> method is made available to PANA and hence to any link-layer
> technology"...
>=20
> I don't understand the conclusion in this sentence "hence to any=20
> link-layer ..."
>=20
> Maybe it should be enough
>=20
> "By the virtue of enabling transport of EAP
> above IP, any authentication method that can be carried as an EAP
> method is made available to PANA".

I don't think it is enough.  Your text only captures the virtue of
carrying EAP, not the virtue of carrying EAP *above IP*.

>=20
> In section 4.1
>=20
> In case of PAA is stateful... might it be possible that PAA sends nonce=
s=20
> in the initial PANA-Auth-Req/Resp
>=20
> >From the text
>=20
> "A Nonce AVP MUST be included in the first non-initial PANA-Auth-Reques=
t=20
> and PANA-Auth-Answer messages, and MUST NOT be included in any other=20
> message."
>=20
> , it seems not
>=20
> My question why it is not possible to include them in the initial=20
> PANA-Auth-Request/Resp?

If the initial PAR/PAN carries nonces, it makes PAA difficult to be
stateless in the initial exchange.

>=20
>=20
> Just the line before section 5.4
>=20
> Key-ID AVP. ---> Key-Id AVP.

OK.

Thanks,
Yoshihiro Ohba

>=20
> My best regards.
>=20
>=20
>=20
>=20
> Alper Yegin escribi=8F=AB=D1:
> >PANA specification is reviewed based on the last round of AD comments
> >(thanks Yoshi!).
> >
> >The spec is here:=20
> >
> >http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
> >
> >And it's diff with the version that predates last round of AD comments
> >(-13):=20
> >
> >http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-from-3.di=
ff.htm
> >l
> >
> >Please review the document and register your feedback by the end of Ap=
ril
> >12, Thursday.
> >
> >Upon collecting and resolving any issues, the document will proceed to=
 IETF
> >last call.
> >
> >Thanks
> >
> >Alper
> >
> >
> >
> >
> >
> >
> >
> >_______________________________________________
> >Pana mailing list
> >Pana@ietf.org
> >https://www1.ietf.org/mailman/listinfo/pana
> >
> >
> > =20
>=20
>=20
> --=20
> ------------------------------------------------------
> Rafael Marin Lopez
> Depto. Ing. de la Info. y las Comunicaciones
> Faculty of Computer Science-University of Murcia
> 30100 Murcia - Spain
> Telf: +34968398501    e-mail: rafa@dif.um.es
> ------------------------------------------------------
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20
>=20

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



From pana-bounces@ietf.org Sat Apr 14 00:28:16 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HcZs0-00057M-62; Sat, 14 Apr 2007 00:28:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcZry-00057D-Pl
	for pana@ietf.org; Sat, 14 Apr 2007 00:28:14 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcZry-0007LJ-JM
	for pana@ietf.org; Sat, 14 Apr 2007 00:28:14 -0400
Received: from localhost (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3E4Rvtu066798
	for <pana@ietf.org>; Sat, 14 Apr 2007 00:27:57 -0400 (EDT)
	(envelope-from yohba@tari.toshiba.com)
Date: Sat, 14 Apr 2007 00:27:58 -0400
To: pana@ietf.org
Message-ID: <20070414042758.GD31340@steelhead>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
User-Agent: Mutt/1.5.13 (2006-08-11)
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20050308(IM148)
Lines: 23
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [Pana] Error message processing
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>
Errors-To: pana-bounces@ietf.org

I discussed with Rafa and found some issue on error message
processing.

The current specification specifies the rule on error message
processing, but it is not clear what is the right protocol behavior
after processing an error message.  The erroneous request/answer
transaction will be terminated after a protected error message
exchange.  But what is the next behavior?  Repeating the erroneous
request/answer transaction until session times out is obviously not a
good approach.  I think that a simple behavior is to silently
terminate the PANA session immediately after any protected error
message exchange.

Note that if an error message is non-protected, the following rule
described in Section 5.8 still applies:

   If an error request or answer message is sent unprotected (i.e.,
   without using an AUTH AVP) then the message MUST be processed such
   that the receiver does not change its PANA protocol state.

Regards,
Yoshihiro Ohba


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



From pana-bounces@ietf.org Sat Apr 14 09:37:40 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HciRf-00023r-SN; Sat, 14 Apr 2007 09:37:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HciRe-00023m-Vb
	for pana@ietf.org; Sat, 14 Apr 2007 09:37:38 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HciRd-0008BH-JA
	for pana@ietf.org; Sat, 14 Apr 2007 09:37:38 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 14 Apr 2007 15:37:28 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Pana] Error message processing
Date: Sat, 14 Apr 2007 15:36:50 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB02604784C6A@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <20070414042758.GD31340@steelhead>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] Error message processing
Thread-Index: Acd+TVU0ua7+Vu77T+K6UOcTF6x+aQASmMhg
References: <20070414042758.GD31340@steelhead>
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>,
	<pana@ietf.org>
X-OriginalArrivalTime: 14 Apr 2007 13:37:28.0091 (UTC)
	FILETIME=[0B2CFEB0:01C77E9A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: 
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>
Errors-To: pana-bounces@ietf.org

=20

> -----Message d'origine-----
> De : Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]=20
> Envoy=E9 : samedi 14 avril 2007 06:28
> =C0 : pana@ietf.org
> Objet : [Pana] Error message processing
>=20
> I discussed with Rafa and found some issue on error message=20
> processing.
>=20
> The current specification specifies the rule on error message=20
> processing, but it is not clear what is the right protocol=20
> behavior after processing an error message.  The erroneous=20
> request/answer transaction will be terminated after a=20
> protected error message exchange.  But what is the next=20
> behavior?  Repeating the erroneous request/answer transaction=20
> until session times out is obviously not a good approach.  I=20
> think that a simple behavior is to silently terminate the=20
> PANA session immediately after any protected error message exchange.

Agreed. I assume that the "silently" is only related to the PANA session =
termination, because the PANA peer will have to anyway take into account =
the error notification ;)

>=20
> Note that if an error message is non-protected, the following=20
> rule described in Section 5.8 still applies:
>=20
>    If an error request or answer message is sent unprotected (i.e.,
>    without using an AUTH AVP) then the message MUST be processed such
>    that the receiver does not change its PANA protocol state.
>=20
> Regards,
> Yoshihiro Ohba
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-bounces@ietf.org Sat Apr 14 14:17:42 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hcmoa-0007Dm-Kn; Sat, 14 Apr 2007 14:17:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HcmoZ-0007Dh-Jd
	for pana@ietf.org; Sat, 14 Apr 2007 14:17:35 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HcmoY-0005ug-71
	for pana@ietf.org; Sat, 14 Apr 2007 14:17:35 -0400
Received: from localhost (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3EIHHqb079639; Sat, 14 Apr 2007 14:17:18 -0400 (EDT)
	(envelope-from yohba@tari.toshiba.com)
Date: Sat, 14 Apr 2007 14:17:19 -0400
To: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.com>
Subject: Re: [Pana] Error message processing
Message-ID: <20070414181719.GA32150@steelhead>
References: <20070414042758.GD31340@steelhead>
	<7DBAFEC6A76F3E42817DF1EBE64CB02604784C6A@FTRDMEL2.rd.francetelecom.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=euc-jp
Content-Disposition: inline
In-Reply-To: <7DBAFEC6A76F3E42817DF1EBE64CB02604784C6A@FTRDMEL2.rd.francetelecom.fr>
User-Agent: Mutt/1.5.13 (2006-08-11)
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20050308(IM148)
Lines: 71
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by
	toshi17.tari.toshiba.com id l3EIHHqb079639
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
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>
Errors-To: pana-bounces@ietf.org

Yes, "silently" is only related to the PANA session termination.

Here is suggested change on Section 5.8.

Change:

"
   If an error request or answer message is sent unprotected (i.e.,
   without using an AUTH AVP) then the message MUST be processed such
   that the receiver does not change its PANA protocol state.
"

To:

"
   If an error request or answer message is sent protected (i.e., with
   using an AUTH AVP), then the PANA session MUST be silently
   terminated after completion of the error message exchange.

   If an error request or answer message is sent unprotected, then the
   message MUST be processed such that the receiver does not change
   its PANA protocol state.
"

Regards,
Yoshihiro Ohba


On Sat, Apr 14, 2007 at 03:36:50PM +0200, MORAND Lionel RD-CORE-ISS wrote=
:
> =20
>=20
> > -----Message d'origine-----
> > De : Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]=20
> > Envoy=8F=AB=B1 : samedi 14 avril 2007 06:28
> > =8F=AA=A2 : pana@ietf.org
> > Objet : [Pana] Error message processing
> >=20
> > I discussed with Rafa and found some issue on error message=20
> > processing.
> >=20
> > The current specification specifies the rule on error message=20
> > processing, but it is not clear what is the right protocol=20
> > behavior after processing an error message.  The erroneous=20
> > request/answer transaction will be terminated after a=20
> > protected error message exchange.  But what is the next=20
> > behavior?  Repeating the erroneous request/answer transaction=20
> > until session times out is obviously not a good approach.  I=20
> > think that a simple behavior is to silently terminate the=20
> > PANA session immediately after any protected error message exchange.
>=20
> Agreed. I assume that the "silently" is only related to the PANA sessio=
n termination, because the PANA peer will have to anyway take into accoun=
t the error notification ;)
>=20
> >=20
> > Note that if an error message is non-protected, the following=20
> > rule described in Section 5.8 still applies:
> >=20
> >    If an error request or answer message is sent unprotected (i.e.,
> >    without using an AUTH AVP) then the message MUST be processed such
> >    that the receiver does not change its PANA protocol state.
> >=20
> > Regards,
> > Yoshihiro Ohba
> >=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
>=20

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



From qtxynipxfj@bevcomm.net Sun Apr 15 07:54:32 2007
Return-path: <qtxynipxfj@bevcomm.net>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hd3JQ-0007d5-Gj
	for pana-archive@lists.ietf.org; Sun, 15 Apr 2007 07:54:32 -0400
Received: from ip81.ip242.bevcomm.net ([199.199.242.81])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Hd3JO-0003bT-PP
	for pana-archive@lists.ietf.org; Sun, 15 Apr 2007 07:54:32 -0400
From:	"reduced" <qtxynipxfj@bevcomm.net>
To: pana-archive@lists.ietf.org
Subject: Your life
Date:	Sun, 15 Apr 2007 06:53:58 +0500
MIME-Version: 1.0
Content-Type: multipart/related;
	boundary="----=_NextPart_000_0000_01C77F2A.D7B5FA50"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: Acd/Kte1VDcPQlS6TXyY8Gv/OPpOqA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Message-Id: <8EE5EEB3B9FE487.15475EBA0B@bevcomm.net>
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1

------=_NextPart_000_0000_01C77F2A.D7B5FA50
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0001_01C77F2A.D7B5FA50"


------=_NextPart_001_0001_01C77F2A.D7B5FA50
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit



computers indeed buried ROMs cards programs anymore higher now.Yes Behls quotVideo Terminal VGA font.

Best Index Arts Film Comics Letters Latest Picks Features Previews


------=_NextPart_001_0001_01C77F2A.D7B5FA50
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
    {margin:0cm;
    margin-bottom:.0001pt;
    font-size:12.0pt;
    font-family:"Times New Roman";}
a:link, span.MsoHyperlink
    {color:blue;
    text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
    {color:purple;
    text-decoration:underline;}
span.EmailStyle17
    {mso-style-type:personal-compose;
    font-family:Arial;
    color:windowtext;}
@page Section1
    {size:595.3pt 841.9pt;
    margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.Section1
    {page:Section1;}
-->      
</style>

</head>

<body lang=3DEN link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><img width=3D562 height=3D118 id=3D"_x0000_i1025"
src=3D"cid:pic01.gif@01C77F2A.D7B5FA50"></span></font><font size=3D2 =
face=3DArial><span
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>computers indeed buried =
ROMs cards programs anymore higher now.Yes Behls quotVideo Terminal VGA =
font.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>Best Index Arts Film Comics =
Letters Latest Picks Features Previews<o:p></o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_001_0001_01C77F2A.D7B5FA50--

------=_NextPart_000_0000_01C77F2A.D7B5FA50
Content-Type: image/gif;
	name="pic01.gif"
Content-Transfer-Encoding: base64
Content-ID: <pic01.gif@01C77F2A.D7B5FA50>

R0lGODdhMgJ2AIcAAAAAAIAAAACAAICAAAAAgIAAgACAgMDAwMDcwKbK8EAgAGAgAIAgAKAg
AMAgAOAgAABAACBAAEBAAGBAAIBAAKBAAMBAAOBAAABgACBgAEBgAGBgAIBgAKBgAMBgAOBg
AACAACCAAECAAGCAAICAAKCAAMCAAOCAAACgACCgAECgAGCgAICgAKCgAMCgAOCgAADAACDA
AEDAAGDAAIDAAKDAAMDAAODAAADgACDgAEDgAGDgAIDgAKDgAMDgAODgAAAAQCAAQEAAQGAA
QIAAQKAAQMAAQOAAQAAgQCAgQEAgQGAgQIAgQKAgQMAgQOAgQABAQCBAQEBAQGBAQIBAQKBA
QMBAQOBAQABgQCBgQEBgQGBgQIBgQKBgQMBgQOBgQACAQCCAQECAQGCAQICAQKCAQMCAQOCA
QACgQCCgQECgQGCgQICgQKCgQMCgQOCgQADAQCDAQEDAQGDAQIDAQKDAQMDAQODAQADgQCDg
QEDgQGDgQIDgQKDgQMDgQODgQAAAgCAAgEAAgGAAgIAAgKAAgMAAgOAAgAAggCAggEAggGAg
gIAggKAggMAggOAggABAgCBAgEBAgGBAgIBAgKBAgMBAgOBAgABggCBggEBggGBggIBggKBg
gMBggOBggACAgCCAgECAgGCAgICAgKCAgMCAgOCAgACggCCggECggGCggICggKCggMCggOCg
gADAgCDAgEDAgGDAgIDAgKDAgMDAgODAgADggCDggEDggGDggIDggKDggMDggODggAAAwCAA
wEAAwGAAwIAAwKAAwMAAwOAAwAAgwCAgwEAgwGAgwIAgwKAgwMAgwOAgwABAwCBAwEBAwGBA
wIBAwKBAwMBAwOBAwABgwCBgwEBgwGBgwIBgwKBgwMBgwOBgwACAwCCAwECAwGCAwICAwKCA
wMCAwOCAwACgwCCgwECgwGCgwICgwKCgwMCgwOCgwADAwCDAwEDAwGDAwIDAwKDAwP/78KCg
pICAgP8AAAD/AP//AAAA//8A/wD//////ywAAAAAMgJ2AAcI/gD/CRxIsKDBgwgTKlzIsKHD
hxAjSpxIsaLFixgzatzIsaPHjyBDihxJsqTJkyhTNlyksqXLlzBjypxJs6bNmyB/4dzJs6fP
n0CDCh1KtKjRo0iTKnyltKnTp1CjSp1KtarVq1izat3KtavXr2DDih1LtqzZs2h3KknLtq3b
t3Djyp1Lt2q6unjz6t3Lt6/fv4ADT60nuLBhsAgOK17MuLHjx5AjS55MubLly5gza97MubNn
g3A+ix5NurTp06hTq17NurXr1yD5wZ5dk59t2f9w4yZ4e/dA3xN7294I/LfA4gl7OxyOUHnL
27+ZG0SeG/pB3Q73UKf92bf36cY9/mLXSH18w93beSdXn1K2+9zh1Rf/Dh7+cu6ov5uP7344
eunWVSddeM5ZZyCB0Dl3nH8BBsjfgv/1V950DToo4HHsGTjge/XJ12F0zJmnIYCl2YKffRju
B6GIGKZoXHosovfijC622KKMMvJ2YI3wbafbgD02R+CNNBbkIJAoAvejkvbFOOSJpelnY3w2
qigchNdVmWSRHAY5ZYwKErkljushGCKQOY535YRM6mghfcqpyeWUUHbnIYpUbjlmmRnOyWOX
gPbJY31ODmrknXjimWN1ec4X5KJasvdnk1pCWidpBdKZ6KIVMogkpYNaZ0qBCVLpn5m4qRJp
p5G6GaGE//Nt6F2pFEZ4qKQrgsihrXqmd+mvMFka7E6+AmssWhbGVKxpKhzr7GMEPCvttNRW
a+212Gar7bbb1sLtt1ABIC4AApF7kLkEmYsuQuuyW9C47WoUL7j0foXuvAPh+4++5TLU7r0e
8VvvwFcBfC+84u6bsLrj9ltuwwofnHC6+T6sbsX9QgxxxfDmOzHBIIfLscMYA7zvyBmTTK7J
Hk9s8sUnG3zuySmTHPLNSMlsscMvoxyzxQtjLLTKKa8ccdAGGV2zUuHgfLPOFMNMM9RK/zs0
zUKzLLXNPiuNNVBLOO3QOtp2PLXGXjP8cccuo/0x1xFTrHLD86a9M9xi5613UP6P7O2RA34H
LvjgjGlB+OGIJ6744oKlItQBjEcu+eSUG7VxQ+RWkZDAAuXjeT4DfQ76P6OTHrrplWdlBcEs
+7sQ56ijXjros59eeuq442R1xgurLTHRCNUe++i0m0587sjrvvbUPGNtN+zCi2678Z0nb/1N
F8OcfddfJxS9QcUXH/v15KvUs/ZLP9/Q9+CfXn358Kd0ec8xb6zx1QRJ/35Bwo8f///yA6AA
2fI21TRhgAhMoAIXyMAGYkQbDjRNACI4kzlQMC23U4ocLpg4s8ntIp8LneeCxz8OmjAirdNI
+IYHvtuN8IQwdB3v0ra25R1EfCzMHwszeDhFxNAlZv6j38/wxr8X9k+H1ePhDyUnj5Hsjnnp
8qBCVrg/JB5viVj8IPCgxpAVHtF9olNiFk/4xN8BjYike2Eaj5hBMY7xjRxxIxzn+Ja70PGO
eMyjHo2VmD368Y+ADKQgTRhEuMEOI1ubmRY7sq5DYs4hTMiIIx3ZPHbZ735Ea2RFDknJAJbM
JPhCn0XehrAzxu1dNTQj/ibSyQK+C42vHFq8OkkRTm6kaQqhpUN0uUmS6EuIdlta9z7Cy5Jo
cphAlNfmbNY6qjlvkbVE4S6nibJZ8iyVpjwaKkUZN3ERQZtnS2Uj3SaxYxayZOJ02908uIgg
tq2MLotaNqW4Mldu8ZNG2/+aO8UZy5chbJzv9F3LMnlJVXqQbgXdpkHp1jWGMnSdl9tZRK8Z
T2Zyr5nklOg751ZAhP6rorasZtKgOMSSei2WQ6Sf+p6ZwovK8p4kPWlMn/k6mn5NaqLEqU1J
OlKKyqxqH7TaLzOJ0pE686guTZ/cnDkzpNZsd9wMJlEVydSpmjSor9SaSBVZ0qmG9KlJK2c9
HxrOos6UeTqr6hnVqlMolvKUOgVoWJF2NHN+0q3cuytXE/kzoGbNlBNtKyajSNeVXpWLdd1p
XKWozTKydKB4faxFhblKqUr2qn9tbNbYBtm/Opav7tqqPLvnWC2m9a4rZWtSbwo8ha0SrJSd
LGb+e6o1YCoWjULEqmwtS9rWUtaph12tTJtpVZQa1rBbjetLY2tTywL3mMH17TChO1zR+guT
1gynQPc5S5CiFpyCjShnfbrUzRJ2rAxbZ8u6S1dwcjSKehUoOrl20L0uV7vu3Wzv2qbQy6pt
vTQtqHwfFmDxqhOwDz1nYStKWgabFpsU7ayB+YlRpDEWrnOtJDKNSZOW7sXDQCkmWEQ8ExLP
xcQbmWhfVPwTe3YFGdJUCooHSS+m0PjGOM6xjlPTxB37mGA7AJdw2pQlhmxIU0Jqz64iIqwi
E5nJYsrIsnSV5OB0ikWh6hKfoozkhTz5PGAWcpeL7OVbTXnKHPkyRJb+pSKMtLkiaKbPrYLz
JC/tKU8KaROak/MfKBuZXktSU4PolCAAeYpXVO7ViIy06AuV6k2FDtGTjnToKh2JP3Ji9JKw
JCAJcZrMbrpQqDvdISy/Z8lY2nSnWZUpUudKR9HhtILitCM7c6tQadpUkaIcqAeRaVK+Djao
GjUnLPN62ISqkZX8pGtjm/lUhvq1rm806FN/6di4Gjaq7cwka0u710N6M7ZwjaBSTxtHYfr2
mNLNbFTHqhWVivWK4MQlJHkbVF9+VaCbFCZcwUrLd542sl20bXyPWs80UreHrD2pNB1I3Nci
N5GIDPBCmVvdEwK2lyAeqF8Xp2kWx3OuB66scGEXS0rZLvmqyAypTB8K4cpmtpg6XuxwE0zi
Bj84oxV9ZGqf6eezkjSIZh70fffq1Qu6c79XPnBRFz1XQNfUrAut6VYhHTmcEtSrkh5rj6PK
zD5f1Yiyfscm45k4hzP7R/Ycw2TNWTzcecdzPrV2tv/47niHTB7yrhBjKOQIfA+84AdP+MIb
/vCIT7ziF5+8vTP+8ZCPvN4+IfnKW/7yWiEG5jfP+c57fjQBAQA7

------=_NextPart_000_0000_01C77F2A.D7B5FA50--




From pana-bounces@ietf.org Sun Apr 15 20:47:57 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdFNo-0003yW-L6; Sun, 15 Apr 2007 20:47:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HdFNm-0003yO-Rc
	for pana@ietf.org; Sun, 15 Apr 2007 20:47:50 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HdFNl-0001gm-HW
	for pana@ietf.org; Sun, 15 Apr 2007 20:47:50 -0400
Received: from localhost (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3G0lUio083260
	for <pana@ietf.org>; Sun, 15 Apr 2007 20:47:30 -0400 (EDT)
	(envelope-from yohba@tari.toshiba.com)
Date: Sun, 15 Apr 2007 20:47:32 -0400
To: pana@ietf.org
Message-ID: <20070416004732.GC10901@steelhead>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Disposition: inline
User-Agent: Mutt/1.5.13 (2006-08-11)
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Dispatcher: imput version 20050308(IM148)
Lines: 37
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: [Pana] Another issue on error message
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>
Errors-To: pana-bounces@ietf.org

In Section 6.3:

"
      M (Mandatory)

         The 'M' Bit, known as the Mandatory bit, indicates whether
         support of the AVP is required.  If an AVP with the 'M' bit set
         is received by the PaC or PAA and either the AVP or its value
         is unrecognized, the message MUST be rejected and the receiver
         MUST send a PANA-Notification-Request message with 'E' bit set.
         If the AVP was unrecognized the result code of the PANA-
         Notification-Request message with 'E' bit set MUST be
         PANA_AVP_UNSUPPORTED.  If the AVP value was unrecognized the
         result code of the PANA-Notification-Request message with 'E'
         bit set MUST be PANA_INVALID_AVP_DATA.  In either case the
         PANA-Notification-Request message with 'E' bit set MUST carry a
         Failed-AVP AVP containing the offending mandatory AVP.  AVPs
         with the 'M' bit cleared are informational only and a receiver
         that receives a message with such an AVP that is not
         recognized, or whose value is not recognized, MAY simply ignore
         the AVP.
"

To be consistent with Section 7.6, the penultimate sentence should be
changed to:

"
In either case the PANA-Notification-Request message with 'E' bit set
MUST carry a Failed-Message-Header AVP and MAY carry one or more
Failed AVPs.
"

Regards,
Yoshihiro Ohba




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



From pana-bounces@ietf.org Mon Apr 16 10:23:17 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdS6u-0006KT-H7; Mon, 16 Apr 2007 10:23:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HdS6r-0006KL-Aa
	for pana@ietf.org; Mon, 16 Apr 2007 10:23:13 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HdS6q-0005Cz-1C
	for pana@ietf.org; Mon, 16 Apr 2007 10:23:13 -0400
Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3GEMqwh090154
	for <pana@ietf.org>; Mon, 16 Apr 2007 10:22:54 -0400 (EDT)
	(envelope-from vfajardo@tari.toshiba.com)
Message-ID: <462386ED.2070204@tari.toshiba.com>
Date: Mon, 16 Apr 2007 10:23:41 -0400
From: Victor Fajardo <vfajardo@tari.toshiba.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: "pana@ietf.org" <pana@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.0 (--)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: [Pana] Additional minor comments
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>
Errors-To: pana-bounces@ietf.org

Hi Yoshi,

I have one more minor comments. In Sec 8.2, I think we should add a 
sentence "The AVP data is of type OctetString." to the AUTH AVP description.

regards,
victor 

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



From pana-bounces@ietf.org Mon Apr 16 11:54:16 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdTWy-0007Ax-7F; Mon, 16 Apr 2007 11:54:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HdTWw-0007Ah-Up
	for pana@ietf.org; Mon, 16 Apr 2007 11:54:14 -0400
Received: from imx12.toshiba.co.jp ([61.202.160.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HdTWv-0002Ok-9c
	for pana@ietf.org; Mon, 16 Apr 2007 11:54:14 -0400
Received: from wall11.toshiba.co.jp (wall11 [133.199.90.149])
	by imx12.toshiba.co.jp  with ESMTP id l3GFsBj4017803
	for <pana@ietf.org>; Tue, 17 Apr 2007 00:54:11 +0900 (JST)
Received: (from root@localhost) by wall11.toshiba.co.jp  id l3GFsBQ4015100;
	Tue, 17 Apr 2007 00:54:11 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] 
	by wall11.toshiba.co.jp with ESMTP id AAA15098;
	Tue, 17 Apr 2007 00:54:10 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp11.toshiba.co.jp  with ESMTP id l3GFsAbk001261;
	Tue, 17 Apr 2007 00:54:10 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3GFsATu016656;
	Tue, 17 Apr 2007 00:54:10 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGL007AGLI2WUA0@mail.po.toshiba.co.jp>; Tue,
	17 Apr 2007 00:54:10 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1HdTWk-0003qm-T7; Mon,
	16 Apr 2007 08:54:02 -0700
Date: Mon, 16 Apr 2007 11:54:02 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Additional minor comments
In-reply-to: <462386ED.2070204@tari.toshiba.com>
To: Victor Fajardo <vfajardo@tari.toshiba.com>
Message-id: <20070416155402.GH12458@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <462386ED.2070204@tari.toshiba.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: "pana@ietf.org" <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>
Errors-To: pana-bounces@ietf.org

On Mon, Apr 16, 2007 at 10:23:41AM -0400, Victor Fajardo wrote:
> Hi Yoshi,
> 
> I have one more minor comments. In Sec 8.2, I think we should add a 
> sentence "The AVP data is of type OctetString." to the AUTH AVP description.

Agreed.

Let me also respond with your earlier comments:

>1. In page 10, 2nd paragraph:
>
>
>"..successfully derived, the last PANA-Auth-Request message MUST contain"
>
>
>for clarity, maybe better as:
>
>"..successfully derived, the last PANA-Auth-Request message with 'C' (Complete) bit set MUST contain ..."
>
>
>also maybe the same can be applied in other text such as 5.3.

Agreed.

>2. Session Lifetime terminlogy, maybe we can add one sentence to the end of the description to make
>it clear that session timeout is also used in post access phase.
>
>
> ...session lifetime can be updated by a new round of EAP
> authentication before it expires. <add>For PANA session in the
> authentication and authorization phase, it should be set to
> a value that allows the PaC to detect a failed session in
> a reasonable amount of time</add>.

How about this?

...session lifetime can be updated by a new round of EAP
authentication before it expires. <add> Until a PANA session is
established, the lifetime SHOULD be set to a value that allows the PaC
to detect a failed session in a reasonable amount of time. </add>


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



From pana-bounces@ietf.org Mon Apr 16 12:39:26 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdUEf-0007Rq-Q3; Mon, 16 Apr 2007 12:39:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HdUEf-0007Rl-6z
	for pana@ietf.org; Mon, 16 Apr 2007 12:39:25 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HdUEd-0000fM-R5
	for pana@ietf.org; Mon, 16 Apr 2007 12:39:25 -0400
Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3GGd65V090872; Mon, 16 Apr 2007 12:39:06 -0400 (EDT)
	(envelope-from vfajardo@tari.toshiba.com)
Message-ID: <4623A6E3.1080507@tari.toshiba.com>
Date: Mon, 16 Apr 2007 12:40:03 -0400
From: Victor Fajardo <vfajardo@tari.toshiba.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Additional minor comments
References: <462386ED.2070204@tari.toshiba.com>
	<20070416155402.GH12458@steelhead>
In-Reply-To: <20070416155402.GH12458@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: "pana@ietf.org" <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>
Errors-To: pana-bounces@ietf.org

Hi,



>> ...session lifetime can be updated by a new round of EAP
>> authentication before it expires. <add>For PANA session in the
>> authentication and authorization phase, it should be set to
>> a value that allows the PaC to detect a failed session in
>> a reasonable amount of time</add>.
>>     
>
> How about this?
>
> ...session lifetime can be updated by a new round of EAP
> authentication before it expires. <add> Until a PANA session is
> established, the lifetime SHOULD be set to a value that allows the PaC
> to detect a failed session in a reasonable amount of time. </add>
>   

Your suggestion is much better.

regards,
victor


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



From pana-bounces@ietf.org Mon Apr 16 19:01:09 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdaC4-0004vL-LP; Mon, 16 Apr 2007 19:01:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HdaC2-0004oo-TB
	for pana@ietf.org; Mon, 16 Apr 2007 19:01:06 -0400
Received: from imx12.toshiba.co.jp ([61.202.160.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HdaC1-0005R0-7D
	for pana@ietf.org; Mon, 16 Apr 2007 19:01:06 -0400
Received: from wall11.toshiba.co.jp (wall11 [133.199.90.149])
	by imx12.toshiba.co.jp  with ESMTP id l3GN13oi001564
	for <pana@ietf.org>; Tue, 17 Apr 2007 08:01:03 +0900 (JST)
Received: (from root@localhost) by wall11.toshiba.co.jp  id l3GN12lR017103;
	Tue, 17 Apr 2007 08:01:02 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] 
	by wall11.toshiba.co.jp with ESMTP id JAA17101;
	Tue, 17 Apr 2007 08:01:02 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp11.toshiba.co.jp  with ESMTP id l3GN11QW028409;
	Tue, 17 Apr 2007 08:01:02 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3GN109H016665;
	Tue, 17 Apr 2007 08:01:00 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGM007AQ59MWUC0@mail.po.toshiba.co.jp>; Tue,
	17 Apr 2007 08:01:00 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1HdaBv-0002m1-Ef; Mon,
	16 Apr 2007 16:00:59 -0700
Date: Mon, 16 Apr 2007 19:00:59 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20070416230059.GP12458@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [Pana] Piggybacking EAP in PAN
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>
Errors-To: pana-bounces@ietf.org

In Section 4.1:

"
   EAP messages are carried in PANA-Auth-Request messages.
   PANA-Auth-Answer messages are simply used to acknowledge receipt of
   the requests.  As an optimization, a PANA-Auth-Answer message MAY
   include the EAP message.  This optimization SHOULD NOT be used when
   it takes time to generate the EAP message (due to, e.g., intervention
   of human input), in which case returning an PANA-Auth-Answer message
   without piggybacking an EAP message can avoid unnecessary
   retransmission of the PANA-Auth-Request message.
"

I think this piggybacking is allowed for PAN generated by PaC only.
Piggybacking EAP for PAN generated by PAA should not allowed,
otherwise the protocol operation can be complex.

Yoshihiro Ohba


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



From ehfmokzeyrq@iss.net Tue Apr 17 00:40:40 2007
Return-path: <ehfmokzeyrq@iss.net>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdfUe-0002RP-Fm
	for pana-archive@lists.ietf.org; Tue, 17 Apr 2007 00:40:40 -0400
Received: from [190.42.95.119] (helo=[190.42.95.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HdfUb-0006eN-I3
	for pana-archive@lists.ietf.org; Tue, 17 Apr 2007 00:40:40 -0400
From:	"ormore luxury" <ehfmokzeyrq@iss.net>
To: pana-archive@lists.ietf.org
Subject: Your 221.43% - breaking results
Date:	Mon, 16 Apr 2007 23:41:12 +0500
MIME-Version: 1.0
Content-Type: multipart/related;
	boundary="----=_NextPart_000_0001_01C78080.B7308CD0"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AceAgLcwzSeeDdttSDuh08eYPcmarA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Message-Id: <BD32EA1E1710416.E7C54F466F@iss.net>
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

------=_NextPart_000_0001_01C78080.B7308CD0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912" name=3D"GENERATOR">
</HEAD>
<BODY>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>DarkLord: DWPI Hits The Street, Price Climbs 221.43%</B></FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2><I>Distributed Power Inc.</I></FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Symbol: <B>DPWI</B> </FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Price: <B>$0.40 (+0.31)</B></FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2>News hits the streets!!! DPWI acquires huge oil reserves, drills deeper on current wells increasing production, and now opens Asian division. </FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Investors go nuts today and price rockets 221.43%. </FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B><U>Act fast, read the news and get on DPWI first thing Tuesday!<U></B></FONT></DIV></BODY></HTML>

------=_NextPart_000_0001_01C78080.B7308CD0--




From ysncbsy@cpkelco.com Tue Apr 17 04:59:35 2007
Return-path: <ysncbsy@cpkelco.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HdjXD-0005Ze-JW
	for pana-archive@lists.ietf.org; Tue, 17 Apr 2007 04:59:35 -0400
Received: from [88.251.245.95] (helo=[88.251.245.95])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HdjXB-0001bk-1w
	for pana-archive@lists.ietf.org; Tue, 17 Apr 2007 04:59:35 -0400
From:	"" <ysncbsy@cpkelco.com>
To: pana-archive@lists.ietf.org
Subject: Stock Trader Alert
Date:	Tue, 17 Apr 2007 12:00:36 -0300
MIME-Version: 1.0
Content-Type: multipart/related;
	boundary="----=_NextPart_000_0002_01C780E8.02853200"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AceA6AKFWG5yhKL+SFa1U5Mdjs83cQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Message-Id: <4017A3B3BCA05B7.ADA9E96255@cpkelco.com>
X-Spam-Score: 4.2 (++++)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

------=_NextPart_000_0002_01C780E8.02853200
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912" name=3D"GENERATOR">
</HEAD>
<BODY>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B>DarkLord: DWPI Hits The Street, Price Climbs 221.43%</B></FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2><I>Distributed Power Inc.</I></FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Symbol: <B>DPWI</B> </FONT></DIV>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Price: <B>$0.40 (+0.31)</B></FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2>News hits the streets!!! DPWI acquires huge oil reserves, drills deeper on current wells increasing production, and now opens Asian division. </FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2>Investors go nuts today and price rockets 221.43%. </FONT></DIV><BR>
<DIV align=3Dleft><FONT face=3DArial size=3D2><B><U>Act fast, read the news and get on DPWI first thing Tuesday!<U></B></FONT></DIV></BODY></HTML>

------=_NextPart_000_0002_01C780E8.02853200--




From pana-bounces@ietf.org Wed Apr 18 12:08:08 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeChP-00035P-KS; Wed, 18 Apr 2007 12:08:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeChO-00035D-I8
	for pana@ietf.org; Wed, 18 Apr 2007 12:08:02 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeChM-0006Z5-V7
	for pana@ietf.org; Wed, 18 Apr 2007 12:08:02 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3IG7xnB024406
	for <pana@ietf.org>; Thu, 19 Apr 2007 01:07:59 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3IG7x7c009054;
	Thu, 19 Apr 2007 01:07:59 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id BAA09048;
	Thu, 19 Apr 2007 01:07:59 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3IG7xlZ015300;
	Thu, 19 Apr 2007 01:07:59 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3IG7wtK002966;
	Thu, 19 Apr 2007 01:07:58 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGP00JR9BH7QGB0@mail.po.toshiba.co.jp>; Thu,
	19 Apr 2007 01:07:58 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1HeChH-0001lw-Gy; Wed,
	18 Apr 2007 09:07:55 -0700
Date: Wed, 18 Apr 2007 12:07:55 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20070418160755.GB4531@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: [Pana] Validity check on Algorithm AVP
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>
Errors-To: pana-bounces@ietf.org

A rule is missing for the case where an Algorithm AVP is contained in
PAR sent from PAA but PaC does not support the algorithms indicated in
the AVP.

I think it should be treated as an invalid message.

Suggestion: Add the following item in Section 5.5:

"
   o  When an Alorithm AVP is included, the algorithms indicated in the AVP value 
      is supported.
"

Yoshihiro Ohba

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



From pana-bounces@ietf.org Wed Apr 18 20:25:09 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeKSS-0004NC-1Q; Wed, 18 Apr 2007 20:25:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeKSQ-0004N7-Jn
	for pana@ietf.org; Wed, 18 Apr 2007 20:25:06 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeKSP-0001mZ-98
	for pana@ietf.org; Wed, 18 Apr 2007 20:25:06 -0400
Received: from [202.20.192.114] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1HeKSK2MHn-0002wv; Wed, 18 Apr 2007 20:25:03 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
	<pana@ietf.org>
Subject: RE: [Pana] Piggybacking EAP in PAN
Date: Thu, 19 Apr 2007 09:25:04 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-index: AceAex7Vdoao0a/OQ9eoqcgaVBRJ8wB0ARKg
In-reply-to: <20070416230059.GP12458@steelhead>
Message-ID: <0MKoyl-1HeKSK2MHn-0002wv@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX18sqA04LXvpEyZuGrRLJSMOj2f0GIQEnkuEdY0
	l9JeV3PzoP1dsehqMBbMyoLoyzPeeCIRFizRm0VW6v1ln+BzBq
	vog0UtkqLKCwUd16rCb2g==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: 
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>
Errors-To: pana-bounces@ietf.org

I agree.

Most of the benefits are realized when the PaC's "answer" can carry "EAP
response". 

The case where PAA needs to send PAN and can hang on to it until it receives
the next EAP Request seems less likely and possibly not worth the
complication.

Alper



> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Tuesday, April 17, 2007 2:01 AM
> To: pana@ietf.org
> Subject: [Pana] Piggybacking EAP in PAN
> 
> In Section 4.1:
> 
> "
>    EAP messages are carried in PANA-Auth-Request messages.
>    PANA-Auth-Answer messages are simply used to acknowledge receipt of
>    the requests.  As an optimization, a PANA-Auth-Answer message MAY
>    include the EAP message.  This optimization SHOULD NOT be used when
>    it takes time to generate the EAP message (due to, e.g., intervention
>    of human input), in which case returning an PANA-Auth-Answer message
>    without piggybacking an EAP message can avoid unnecessary
>    retransmission of the PANA-Auth-Request message.
> "
> 
> I think this piggybacking is allowed for PAN generated by PaC only.
> Piggybacking EAP for PAN generated by PAA should not allowed,
> otherwise the protocol operation can be complex.
> 
> 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 Wed Apr 18 20:32:17 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeKZL-0003pO-Of; Wed, 18 Apr 2007 20:32:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeKZK-0003pH-83
	for pana@ietf.org; Wed, 18 Apr 2007 20:32:14 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeKZI-0002v6-Rb
	for pana@ietf.org; Wed, 18 Apr 2007 20:32:14 -0400
Received: from [202.20.192.114] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1HeKZD3XS9-00006F; Wed, 18 Apr 2007 20:32:11 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'MORAND Lionel RD-CORE-ISS'" <lionel.morand@orange-ftgroup.com>,
	<pana@ietf.org>
Subject: RE: [Pana] PAA initiating Re-authentication 
Date: Thu, 19 Apr 2007 09:32:11 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-index: Acd3WTDyizSUEhDfQsmuXavrnmLM4AFh5rhQAVrDBaA=
In-reply-to: <7DBAFEC6A76F3E42817DF1EBE64CB026047846B9@FTRDMEL2.rd.francetelecom.fr>
Message-ID: <0MKp2t-1HeKZD3XS9-00006F@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX18YIhXp8dme6JR+npvdO2AE8hqTvT7q0w7CY9n
	Yp3wlq1HGLU1kZCEEcBTnSA8dBV9PziZiWVu3lNYGJEpM49Un5
	I0gKLX7PJxv9H9CJyTOcQ==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: 
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>
Errors-To: pana-bounces@ietf.org


In order to reduce the optionality, can we say:

- PAA MUST send lifetime (when infinity, it can send maxint).
- PaC SHOULD initiate re-auth before lifetime expires. A "should" =
because
PaC may choose not to extend the authorization. Or we can make it a must
with a conditional "if PaC wants to extend....".
- PAA MAY initiate re-auth. Now, this one does not have to be related to
lifetime expiry, given that we put that burden on the PaC.=20

Does this make sense?

Alper




> -----Original Message-----
> From: MORAND Lionel RD-CORE-ISS =
[mailto:lionel.morand@orange-ftgroup.com]
> Sent: Thursday, April 12, 2007 12:43 PM
> To: Alper Yegin; pana@ietf.org
> Subject: [Pana] PAA initiating Re-authentication
>=20
> Hi,
>=20
> In section 5.7 Session Lifetime, it is stated:
>=20
> "The PAA MUST initiate the re-authentication phase before the current
> session lifetime expires."
>=20
> I can't figure out why there is a "MUST" in that case.
>=20
> As documented in the draft,
>=20
> - The session lifetime is not negociable between the PAA and the PaC.
> - The session lifetime may be sent to the PaC. If not, the PaC =
considers
> the PANA session as unlimited.
> - Both PaC and PAA may initiate a re-authentication procedure =
regardless
> of the session lifetime.
>=20
> Could we just have the following principles:
>=20
> - If the session lifetime is sent to the PaC:
> The PaC should re-authenticate before the expiration of the session
> lifetime. Otherwise, the session is deleted by the PAA at the =
expiration
> of the session lifetime (and the PaC will purge related local state).
> The PAA may initiate a re-authentication procedure before the =
expiration
> of the session lifetime. Otherwise, the session is deleted by the PAA =
at
> the expiration of the session lifetime (and the PaC will purge related
> local state).
> Both PaC and PAA may initiate a re-authentication procedure regardless =
of
> the session lifetime.
>=20
> - If the session lifetime is sent to the PaC:
> The PAA may initiate a re-authentication procedure before the =
expiration
> of the session lifetime. Otherwise, the session is deleted at the
> expiration of the session lifetime.
> Both PaC and PAA may initiate a re-authentication procedure regardless =
of
> the session lifetime.
>=20
>=20
> With these principles, it is up to the PaC to maintain active its PANA
> session when infomed by the network (PAA) of the authorized session
> lifetime.
> There is no strong requirement for the PAA/network point of view to . =
It
> is therefore up to the network operator to configure the PAA expected
> behaviour.
>=20
> Comments?
>=20
> Lionel
>=20
>=20
> > -----Message d'origine-----
> > De : Alper Yegin [mailto:alper.yegin@yegin.org]
> > Envoy=E9 : jeudi 5 avril 2007 10:06
> > =C0 : pana@ietf.org
> > Objet : [Pana] Review pana-pana-15a
> >
> >
> > PANA specification is reviewed based on the last round of AD
> > comments (thanks Yoshi!).
> >
> > The spec is here:
> >
> > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
> >
> > And it's diff with the version that predates last round of AD =
comments
> > (-13):
> >
> > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> > rom-3.diff.htm
> > l
> >
> > Please review the document and register your feedback by the
> > end of April 12, Thursday.
> >
> > Upon collecting and resolving any issues, the document will
> > proceed to IETF last call.
> >
> > Thanks
> >
> > 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 Apr 19 03:00:00 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeQcY-0004V5-2o; Thu, 19 Apr 2007 02:59:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeQcV-0004Uv-7a
	for pana@ietf.org; Thu, 19 Apr 2007 02:59:55 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeQcT-0008C1-OG
	for pana@ietf.org; Thu, 19 Apr 2007 02:59:55 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Apr 2007 08:59:43 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Pana] PAA initiating Re-authentication 
Date: Thu, 19 Apr 2007 08:59:39 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026047BEDA0@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <0MKp2t-1HeKZD3XS9-00006F@mrelay.perfora.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] PAA initiating Re-authentication 
Thread-Index: Acd3WTDyizSUEhDfQsmuXavrnmLM4AFh5rhQAVrDBaAAAPTX4A==
References: <7DBAFEC6A76F3E42817DF1EBE64CB026047846B9@FTRDMEL2.rd.francetelecom.fr>
	<0MKp2t-1HeKZD3XS9-00006F@mrelay.perfora.net>
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	<pana@ietf.org>
X-OriginalArrivalTime: 19 Apr 2007 06:59:43.0588 (UTC)
	FILETIME=[4EE39240:01C78250]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Cc: 
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>
Errors-To: pana-bounces@ietf.org

It makes sense! ;)
For the PaC behavior, i think that a "If PaC wants... then PaC MUST" is =
acceptable.
Ok for the behavior of the PAA. It MAY initiate the re-auth when it =
wants.

BR,

Lionel

> -----Message d'origine-----
> De : Alper Yegin [mailto:alper.yegin@yegin.org]=20
> Envoy=E9 : jeudi 19 avril 2007 08:32
> =C0 : MORAND Lionel RD-CORE-ISS; pana@ietf.org
> Objet : RE: [Pana] PAA initiating Re-authentication=20
>=20
>=20
> In order to reduce the optionality, can we say:
>=20
> - PAA MUST send lifetime (when infinity, it can send maxint).
> - PaC SHOULD initiate re-auth before lifetime expires. A=20
> "should" because PaC may choose not to extend the=20
> authorization. Or we can make it a must with a conditional=20
> "if PaC wants to extend....".
> - PAA MAY initiate re-auth. Now, this one does not have to be=20
> related to lifetime expiry, given that we put that burden on the PaC.=20
>=20
> Does this make sense?
>=20
> Alper
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: MORAND Lionel RD-CORE-ISS=20
> > [mailto:lionel.morand@orange-ftgroup.com]
> > Sent: Thursday, April 12, 2007 12:43 PM
> > To: Alper Yegin; pana@ietf.org
> > Subject: [Pana] PAA initiating Re-authentication
> >=20
> > Hi,
> >=20
> > In section 5.7 Session Lifetime, it is stated:
> >=20
> > "The PAA MUST initiate the re-authentication phase before=20
> the current=20
> > session lifetime expires."
> >=20
> > I can't figure out why there is a "MUST" in that case.
> >=20
> > As documented in the draft,
> >=20
> > - The session lifetime is not negociable between the PAA=20
> and the PaC.
> > - The session lifetime may be sent to the PaC. If not, the PaC=20
> > considers the PANA session as unlimited.
> > - Both PaC and PAA may initiate a re-authentication procedure=20
> > regardless of the session lifetime.
> >=20
> > Could we just have the following principles:
> >=20
> > - If the session lifetime is sent to the PaC:
> > The PaC should re-authenticate before the expiration of the session=20
> > lifetime. Otherwise, the session is deleted by the PAA at the=20
> > expiration of the session lifetime (and the PaC will purge=20
> related local state).
> > The PAA may initiate a re-authentication procedure before the=20
> > expiration of the session lifetime. Otherwise, the session=20
> is deleted=20
> > by the PAA at the expiration of the session lifetime (and=20
> the PaC will=20
> > purge related local state).
> > Both PaC and PAA may initiate a re-authentication procedure=20
> regardless=20
> > of the session lifetime.
> >=20
> > - If the session lifetime is sent to the PaC:
> > The PAA may initiate a re-authentication procedure before the=20
> > expiration of the session lifetime. Otherwise, the session=20
> is deleted=20
> > at the expiration of the session lifetime.
> > Both PaC and PAA may initiate a re-authentication procedure=20
> regardless=20
> > of the session lifetime.
> >=20
> >=20
> > With these principles, it is up to the PaC to maintain=20
> active its PANA=20
> > session when infomed by the network (PAA) of the authorized session=20
> > lifetime.
> > There is no strong requirement for the PAA/network point of=20
> view to .=20
> > It is therefore up to the network operator to configure the PAA=20
> > expected behaviour.
> >=20
> > Comments?
> >=20
> > Lionel
> >=20
> >=20
> > > -----Message d'origine-----
> > > De : Alper Yegin [mailto:alper.yegin@yegin.org] Envoy=E9 : jeudi 5 =

> > > avril 2007 10:06 =C0 : pana@ietf.org Objet : [Pana] Review=20
> > > pana-pana-15a
> > >
> > >
> > > PANA specification is reviewed based on the last round of AD=20
> > > comments (thanks Yoshi!).
> > >
> > > The spec is here:
> > >
> > > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
> > >
> > > And it's diff with the version that predates last round of AD=20
> > > comments
> > > (-13):
> > >
> > > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> > > rom-3.diff.htm
> > > l
> > >
> > > Please review the document and register your feedback by=20
> the end of=20
> > > April 12, Thursday.
> > >
> > > Upon collecting and resolving any issues, the document=20
> will proceed=20
> > > to IETF last call.
> > >
> > > Thanks
> > >
> > > Alper
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > >
>=20
>=20

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



From pana-bounces@ietf.org Thu Apr 19 03:22:14 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeQy0-0007w6-7P; Thu, 19 Apr 2007 03:22:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeQxy-0007vo-Vz
	for pana@ietf.org; Thu, 19 Apr 2007 03:22:06 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeQxy-0007nF-JW
	for pana@ietf.org; Thu, 19 Apr 2007 03:22:06 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 19 Apr 2007 09:21:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Pana] Piggybacking EAP in PAN
Date: Thu, 19 Apr 2007 09:21:58 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026047BEDCB@FTRDMEL2.rd.francetelecom.fr>
In-Reply-To: <0MKoyl-1HeKSK2MHn-0002wv@mrelay.perfora.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pana] Piggybacking EAP in PAN
Thread-Index: AceAex7Vdoao0a/OQ9eoqcgaVBRJ8wB0ARKgAAIOWOA=
References: <20070416230059.GP12458@steelhead>
	<0MKoyl-1HeKSK2MHn-0002wv@mrelay.perfora.net>
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	"Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
X-OriginalArrivalTime: 19 Apr 2007 07:21:59.0792 (UTC)
	FILETIME=[6B541F00:01C78253]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: 
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>
Errors-To: pana-bounces@ietf.org

I agree too.

Lionel=20

> -----Message d'origine-----
> De : Alper Yegin [mailto:alper.yegin@yegin.org]=20
> Envoy=E9 : jeudi 19 avril 2007 08:25
> =C0 : 'Yoshihiro Ohba'; pana@ietf.org
> Objet : RE: [Pana] Piggybacking EAP in PAN
>=20
> I agree.
>=20
> Most of the benefits are realized when the PaC's "answer" can=20
> carry "EAP response".=20
>=20
> The case where PAA needs to send PAN and can hang on to it=20
> until it receives the next EAP Request seems less likely and=20
> possibly not worth the complication.
>=20
> Alper
>=20
>=20
>=20
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Tuesday, April 17, 2007 2:01 AM
> > To: pana@ietf.org
> > Subject: [Pana] Piggybacking EAP in PAN
> >=20
> > In Section 4.1:
> >=20
> > "
> >    EAP messages are carried in PANA-Auth-Request messages.
> >    PANA-Auth-Answer messages are simply used to acknowledge=20
> receipt of
> >    the requests.  As an optimization, a PANA-Auth-Answer message MAY
> >    include the EAP message.  This optimization SHOULD NOT=20
> be used when
> >    it takes time to generate the EAP message (due to, e.g.,=20
> intervention
> >    of human input), in which case returning an=20
> PANA-Auth-Answer message
> >    without piggybacking an EAP message can avoid unnecessary
> >    retransmission of the PANA-Auth-Request message.
> > "
> >=20
> > I think this piggybacking is allowed for PAN generated by PaC only.
> > Piggybacking EAP for PAN generated by PAA should not allowed,=20
> > otherwise the protocol operation can be complex.
> >=20
> > Yoshihiro Ohba
> >=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-bounces@ietf.org Thu Apr 19 07:46:02 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeV5M-0005Lp-Or; Thu, 19 Apr 2007 07:46:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeV5K-0005GQ-UP
	for pana@ietf.org; Thu, 19 Apr 2007 07:45:58 -0400
Received: from imx12.toshiba.co.jp ([61.202.160.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeV5K-00055e-4I
	for pana@ietf.org; Thu, 19 Apr 2007 07:45:58 -0400
Received: from wall11.toshiba.co.jp (wall11 [133.199.90.149])
	by imx12.toshiba.co.jp  with ESMTP id l3JBjth6012200;
	Thu, 19 Apr 2007 20:45:55 +0900 (JST)
Received: (from root@localhost) by wall11.toshiba.co.jp  id l3JBjtr1005202;
	Thu, 19 Apr 2007 20:45:55 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] 
	by wall11.toshiba.co.jp with ESMTP id WAA05192;
	Thu, 19 Apr 2007 20:45:54 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp11.toshiba.co.jp  with ESMTP id l3JBjrWP012034;
	Thu, 19 Apr 2007 20:45:54 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3JBjrw9015123;
	Thu, 19 Apr 2007 20:45:53 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGQ00136U0EJWH0@mail.po.toshiba.co.jp>; Thu,
	19 Apr 2007 20:45:53 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1HeV5C-0003kG-EL; Thu,
	19 Apr 2007 04:45:50 -0700
Date: Thu, 19 Apr 2007 07:45:50 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Piggybacking EAP in PAN
In-reply-to: <7DBAFEC6A76F3E42817DF1EBE64CB026047BEDCB@FTRDMEL2.rd.francetelecom.fr>
To: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.com>
Message-id: <20070419114549.GC13717@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=euc-jp
Content-disposition: inline
References: <20070416230059.GP12458@steelhead>
	<0MKoyl-1HeKSK2MHn-0002wv@mrelay.perfora.net>
	<7DBAFEC6A76F3E42817DF1EBE64CB026047BEDCB@FTRDMEL2.rd.francetelecom.fr>
User-Agent: Mutt/1.5.13 (2006-08-11)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by imx12.toshiba.co.jp id
	l3JBjth6012200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
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>
Errors-To: pana-bounces@ietf.org

OK.  Here is suggested text ("sent from the PaC" is added in the 2nd sent=
ence):

"
   EAP messages are carried in PANA-Auth-Request messages.
   PANA-Auth-Answer messages are simply used to acknowledge receipt of
   the requests.  As an optimization, a PANA-Auth-Answer message sent fro=
m the PaC MAY
   include the EAP message.  This optimization SHOULD NOT be used when
   it takes time to generate the EAP message (due to, e.g., intervention
   of human input), in which case returning an PANA-Auth-Answer message
   without piggybacking an EAP message can avoid unnecessary
   retransmission of the PANA-Auth-Request message. =20
"

Yoshihiro Ohba


On Thu, Apr 19, 2007 at 09:21:58AM +0200, MORAND Lionel RD-CORE-ISS wrote=
:
> I agree too.
>=20
> Lionel=20
>=20
> > -----Message d'origine-----
> > De : Alper Yegin [mailto:alper.yegin@yegin.org]=20
> > Envoy=8F=AB=B1 : jeudi 19 avril 2007 08:25
> > =8F=AA=A2 : 'Yoshihiro Ohba'; pana@ietf.org
> > Objet : RE: [Pana] Piggybacking EAP in PAN
> >=20
> > I agree.
> >=20
> > Most of the benefits are realized when the PaC's "answer" can=20
> > carry "EAP response".=20
> >=20
> > The case where PAA needs to send PAN and can hang on to it=20
> > until it receives the next EAP Request seems less likely and=20
> > possibly not worth the complication.
> >=20
> > Alper
> >=20
> >=20
> >=20
> > > -----Original Message-----
> > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: Tuesday, April 17, 2007 2:01 AM
> > > To: pana@ietf.org
> > > Subject: [Pana] Piggybacking EAP in PAN
> > >=20
> > > In Section 4.1:
> > >=20
> > > "
> > >    EAP messages are carried in PANA-Auth-Request messages.
> > >    PANA-Auth-Answer messages are simply used to acknowledge=20
> > receipt of
> > >    the requests.  As an optimization, a PANA-Auth-Answer message MA=
Y
> > >    include the EAP message.  This optimization SHOULD NOT=20
> > be used when
> > >    it takes time to generate the EAP message (due to, e.g.,=20
> > intervention
> > >    of human input), in which case returning an=20
> > PANA-Auth-Answer message
> > >    without piggybacking an EAP message can avoid unnecessary
> > >    retransmission of the PANA-Auth-Request message.
> > > "
> > >=20
> > > I think this piggybacking is allowed for PAN generated by PaC only.
> > > Piggybacking EAP for PAN generated by PAA should not allowed,=20
> > > otherwise the protocol operation can be complex.
> > >=20
> > > Yoshihiro Ohba
> > >=20
> > >=20
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> >=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
>=20

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



From pana-bounces@ietf.org Thu Apr 19 08:55:43 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeWAn-0004gk-SC; Thu, 19 Apr 2007 08:55:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeWAm-0004gf-8F
	for pana@ietf.org; Thu, 19 Apr 2007 08:55:40 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeWAk-0002mG-CG
	for pana@ietf.org; Thu, 19 Apr 2007 08:55:40 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3JCtZUJ025049;
	Thu, 19 Apr 2007 21:55:35 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3JCtah6009487;
	Thu, 19 Apr 2007 21:55:36 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id XAA09486;
	Thu, 19 Apr 2007 21:55:36 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3JCtZ5i000088;
	Thu, 19 Apr 2007 21:55:35 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3JCtZPB020653;
	Thu, 19 Apr 2007 21:55:35 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGQ001W6X86JWI0@mail.po.toshiba.co.jp>; Thu,
	19 Apr 2007 21:55:35 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1HeWAP-0003x7-5F; Thu,
	19 Apr 2007 05:55:17 -0700
Date: Thu, 19 Apr 2007 08:55:17 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] PAA initiating Re-authentication
In-reply-to: <7DBAFEC6A76F3E42817DF1EBE64CB026047BEDA0@FTRDMEL2.rd.francetelecom.fr>
To: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.com>
Message-id: <20070419125517.GD13717@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=euc-jp
Content-disposition: inline
References: <7DBAFEC6A76F3E42817DF1EBE64CB026047846B9@FTRDMEL2.rd.francetelecom.fr>
	<0MKp2t-1HeKZD3XS9-00006F@mrelay.perfora.net>
	<7DBAFEC6A76F3E42817DF1EBE64CB026047BEDA0@FTRDMEL2.rd.francetelecom.fr>
User-Agent: Mutt/1.5.13 (2006-08-11)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by inet-tsb5.toshiba.co.jp
	id l3JCtZUJ025049
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dd7e0c3fd18d19cffdd4de99a114001d
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>
Errors-To: pana-bounces@ietf.org

OK.  Let me propose text.

[1] In Section 3, change:

"
   o  Re-authentication phase: During the access phase, the PAA must
      initiate re-authentication before the PANA session lifetime
      expires.  EAP is carried by PANA to perform authentication.  This
      phase may be optionally triggered by both the PaC and the PAA
      without any respect to the session lifetime.  The session moves to
      this phase from the access phase, and returns back there upon
      successful re-authentication.
"

to:

"
      Re-authentication phase: During the access phase, the PAA may,
      and the PaC should, initiate re-authentication if they want to
      update the PANA session lifetime before the PANA
      session lifetime expires.  EAP is carried by PANA to perform
      authentication.  This phase may be optionally triggered by both
      the PaC and the PAA without any respect to the session lifetime.
      The session moves to this phase from the access phase, and
      returns back there upon successful re-authentication.
"

[2] In Section 4.3, 2nd paragraph, change:

"
   When the PaC wants to initiate re-authentication, it sends a
   PANA-Notification-Request message with 'A' bit set (a re-
   authentication request message) to the PAA. =20
"

to:

"
   When the PaC initiates re-authentication, it sends a
   PANA-Notification-Request message with 'A' bit set (a re-
   authentication request message) to the PAA. =20
"

[3] In Section 5.7, change:

"
   The authentication and authorization phase determines the PANA
   session lifetime when the network access authorization succeeds.  The
   Session-Lifetime AVP MAY be optionally included in the last
   PANA-Auth-Request message to inform the PaC about the valid lifetime
   of the PANA session.  It MUST be ignored when included in other PANA
   messages.

   When the Session-Lifetime AVP is not included in the last
   PANA-Auth-Request message then the PaC has no knowledge about a PANA
   session limitation and must therefore conclude that the session is
   not limited.

   The lifetime is a non-negotiable parameter that can be used by the
   PaC to manage PANA-related state.  The PaC does not have to perform
   any actions when the lifetime expires, other than purging local
   state.  The PAA MUST initiate the re-authentication phase before the
   current session lifetime expires.
"

to:

"
   The authentication and authorization phase determines the PANA
   session lifetime when the network access authorization succeeds.  The
   Session-Lifetime AVP MUST be included in the last PANA-Auth-Request
   message (i.e., with 'C' (Complete) bit set) in authentication and
   authorization phase or re-authentication phase to inform the PaC
   about the valid lifetime of the PANA session.  It MUST be ignored
   when included in other PANA messages.

   The lifetime is a non-negotiable parameter that can be used by the
   PaC to manage PANA-related state.  The PaC does not have to perform
   any actions when the lifetime expires, other than purging local
   state.  The PAA MAY, and the PaC SHOULD, initiate the
   re-authentication phase before the current session lifetime expires=20
   if they want to update the session lifetime.
"

(I don't think we should define a value for "infinity", because the
maximum value of session lifetime is 2^32-1 (4,294,967,295) sec =3D
49,710 days!)

Yoshihiro Ohba


On Thu, Apr 19, 2007 at 08:59:39AM +0200, MORAND Lionel RD-CORE-ISS wrote=
:
> It makes sense! ;)
> For the PaC behavior, i think that a "If PaC wants... then PaC MUST" is=
 acceptable.
> Ok for the behavior of the PAA. It MAY initiate the re-auth when it wan=
ts.
>=20
> BR,
>=20
> Lionel
>=20
> > -----Message d'origine-----
> > De : Alper Yegin [mailto:alper.yegin@yegin.org]=20
> > Envoy=8F=AB=B1 : jeudi 19 avril 2007 08:32
> > =8F=AA=A2 : MORAND Lionel RD-CORE-ISS; pana@ietf.org
> > Objet : RE: [Pana] PAA initiating Re-authentication=20
> >=20
> >=20
> > In order to reduce the optionality, can we say:
> >=20
> > - PAA MUST send lifetime (when infinity, it can send maxint).
> > - PaC SHOULD initiate re-auth before lifetime expires. A=20
> > "should" because PaC may choose not to extend the=20
> > authorization. Or we can make it a must with a conditional=20
> > "if PaC wants to extend....".
> > - PAA MAY initiate re-auth. Now, this one does not have to be=20
> > related to lifetime expiry, given that we put that burden on the PaC.=
=20
> >=20
> > Does this make sense?
> >=20
> > Alper
> >=20
> >=20
> >=20
> >=20
> > > -----Original Message-----
> > > From: MORAND Lionel RD-CORE-ISS=20
> > > [mailto:lionel.morand@orange-ftgroup.com]
> > > Sent: Thursday, April 12, 2007 12:43 PM
> > > To: Alper Yegin; pana@ietf.org
> > > Subject: [Pana] PAA initiating Re-authentication
> > >=20
> > > Hi,
> > >=20
> > > In section 5.7 Session Lifetime, it is stated:
> > >=20
> > > "The PAA MUST initiate the re-authentication phase before=20
> > the current=20
> > > session lifetime expires."
> > >=20
> > > I can't figure out why there is a "MUST" in that case.
> > >=20
> > > As documented in the draft,
> > >=20
> > > - The session lifetime is not negociable between the PAA=20
> > and the PaC.
> > > - The session lifetime may be sent to the PaC. If not, the PaC=20
> > > considers the PANA session as unlimited.
> > > - Both PaC and PAA may initiate a re-authentication procedure=20
> > > regardless of the session lifetime.
> > >=20
> > > Could we just have the following principles:
> > >=20
> > > - If the session lifetime is sent to the PaC:
> > > The PaC should re-authenticate before the expiration of the session=
=20
> > > lifetime. Otherwise, the session is deleted by the PAA at the=20
> > > expiration of the session lifetime (and the PaC will purge=20
> > related local state).
> > > The PAA may initiate a re-authentication procedure before the=20
> > > expiration of the session lifetime. Otherwise, the session=20
> > is deleted=20
> > > by the PAA at the expiration of the session lifetime (and=20
> > the PaC will=20
> > > purge related local state).
> > > Both PaC and PAA may initiate a re-authentication procedure=20
> > regardless=20
> > > of the session lifetime.
> > >=20
> > > - If the session lifetime is sent to the PaC:
> > > The PAA may initiate a re-authentication procedure before the=20
> > > expiration of the session lifetime. Otherwise, the session=20
> > is deleted=20
> > > at the expiration of the session lifetime.
> > > Both PaC and PAA may initiate a re-authentication procedure=20
> > regardless=20
> > > of the session lifetime.
> > >=20
> > >=20
> > > With these principles, it is up to the PaC to maintain=20
> > active its PANA=20
> > > session when infomed by the network (PAA) of the authorized session=
=20
> > > lifetime.
> > > There is no strong requirement for the PAA/network point of=20
> > view to .=20
> > > It is therefore up to the network operator to configure the PAA=20
> > > expected behaviour.
> > >=20
> > > Comments?
> > >=20
> > > Lionel
> > >=20
> > >=20
> > > > -----Message d'origine-----
> > > > De : Alper Yegin [mailto:alper.yegin@yegin.org] Envoy=8F=AB=B1 : =
jeudi 5=20
> > > > avril 2007 10:06 =8F=AA=A2 : pana@ietf.org Objet : [Pana] Review=20
> > > > pana-pana-15a
> > > >
> > > >
> > > > PANA specification is reviewed based on the last round of AD=20
> > > > comments (thanks Yoshi!).
> > > >
> > > > The spec is here:
> > > >
> > > > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a.txt
> > > >
> > > > And it's diff with the version that predates last round of AD=20
> > > > comments
> > > > (-13):
> > > >
> > > > http://www.panasec.org/docs/editing/draft-ietf-pana-pana-15a-f
> > > > rom-3.diff.htm
> > > > l
> > > >
> > > > Please review the document and register your feedback by=20
> > the end of=20
> > > > April 12, Thursday.
> > > >
> > > > Upon collecting and resolving any issues, the document=20
> > will proceed=20
> > > > to IETF last call.
> > > >
> > > > Thanks
> > > >
> > > > Alper
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Pana mailing list
> > > > Pana@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pana
> > > >
> >=20
> >=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20
>=20

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



From pana-bounces@ietf.org Thu Apr 19 11:46:37 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HeYqB-0004cm-UX; Thu, 19 Apr 2007 11:46:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HeYqA-0004ce-8n
	for pana@ietf.org; Thu, 19 Apr 2007 11:46:34 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HeYq8-0005QR-Uh
	for pana@ietf.org; Thu, 19 Apr 2007 11:46:34 -0400
Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3JFk6BQ007170
	for <pana@ietf.org>; Thu, 19 Apr 2007 11:46:06 -0400 (EDT)
	(envelope-from vfajardo@tari.toshiba.com)
Message-ID: <46278FB7.5090808@tari.toshiba.com>
Date: Thu, 19 Apr 2007 11:50:15 -0400
From: Victor Fajardo <vfajardo@tari.toshiba.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: "pana@ietf.org" <pana@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.0 (--)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Subject: [Pana] Ping and pending request
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>
Errors-To: pana-bounces@ietf.org

Hi,

A few more issues we can check:

a. In Sec 5.5, the following text:

"
+ The last PANA-Auth-Request as well as ping request before
  completion of the initial PANA-Auth-Request and
  PANA-Auth-Answer exchange.
"

should be replace with:

"
+ The last PANA-Auth-Request before completion of the initial
  PANA-Auth-Request and PANA-Auth-Answer exchange.

+ Ping request.
"

Reasons: We should not allow ping during authentication and 
authorization phase and re-authentication phase since it will allow for 
multiple outstanding requests to be sent (ping and auth request) which 
tends to complicate state transitions. Also, we don't need liveness test 
during these phases anyway since we already rely on session lifetime to 
detect failed sessions.

b. In Sec 5.5:

"
      *  In the access phase:

         +  PANA-Auth-Request.
"

Just for clarity, maybe it should be "+  PANA-Auth-Request with any of its bit flag set".

c. Optional text we want to consider for the same complexity reason as (a) above.

-- Sec 4.2.; First paragraph; Add a sentence: "The ping request MUST be sent only when there are no other pending un-answered request".
-- Same with sec 4.3 and 4.4 with regards to re-auth and termination request. Not sure how to phrase it though. Maybe "A PANA session MUST not enter the
   [re-auth|termination] phase while there are pending un-answered request" (??).

regards,
victor




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



From pana-bounces@ietf.org Thu Apr 19 23:11:18 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HejWo-0005rj-0Z; Thu, 19 Apr 2007 23:11:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HejWm-0005rW-Vi
	for pana@ietf.org; Thu, 19 Apr 2007 23:11:16 -0400
Received: from thumper.research.telcordia.com ([128.96.41.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HejWj-0003Zh-5d
	for pana@ietf.org; Thu, 19 Apr 2007 23:11:16 -0400
Received: from mailee.research.telcordia.com (mailee [192.4.16.29])
	by thumper.research.telcordia.com (8.13.6/8.13.5) with ESMTP id
	l3K3B1h3014005; Thu, 19 Apr 2007 23:11:01 -0400 (EDT)
Received: from [128.96.58.238] (vpntnlA238 [128.96.58.238])
	by mailee.research.telcordia.com (8.9.3/8.9.3) with ESMTP id XAA11702; 
	Thu, 19 Apr 2007 23:10:59 -0400 (EDT)
Message-ID: <46282F3B.5040102@research.telcordia.com>
Date: Thu, 19 Apr 2007 23:10:51 -0400
From: Subir Das <subir@research.telcordia.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: "pana@ietf.org" <pana@ietf.org>
References: <46278FB7.5090808@tari.toshiba.com>
In-Reply-To: <46278FB7.5090808@tari.toshiba.com>
Content-Type: multipart/mixed; boundary="------------050909040805000300050703"
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 23c749e40fca2767ff79edf93e31ce10
Cc: Subir Das <subir@research.telcordia.com>
Subject: [Pana] Comments on draft-pana-pana-15a
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>
Errors-To: pana-bounces@ietf.org

This is a multi-part message in MIME format.
--------------050909040805000300050703
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

The updated version looks good. Few comments and suggestions on draft -15a.

regards,
-Subir

--------------050909040805000300050703
Content-Type: text/plain; name="draft-ietf-pana-pana-15a_Subir(comments).txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
	filename="draft-ietf-pana-pana-15a_Subir(comments).txt"



PANA Working Group                                           D. Forsberg
Internet-Draft                                                     Nokia
Intended status: Standards Track                           Y. Ohba (Ed.)
Expires: October 6, 2007                                         Toshiba
                                                                B. Patil
                                                                   Nokia
                                                           H. Tschofenig
                                                                 Siemens
                                                                A. Yegin
                                                                 Samsung
                                                           April 4, 2007


     Protocol for Carrying Authentication for Network Access (PANA)
                        draft-ietf-pana-pana-15a

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on October 6, 2007.

Copyright Notice

   Copyright (C) The IETF Trust (2007).







Forsberg, et al.         Expires October 6, 2007                [Page 1]


Internet-Draft                    PANA                        April 2007


Abstract

   This document defines the Protocol for Carrying Authentication for
   Network Access (PANA), a network-layer transport for Extensible
   Authentication Protocol (EAP) to enable network access authentication
   between clients and access networks.  In EAP terms, PANA is a UDP-
   based EAP lower layer that runs between the EAP peer and the EAP
   authenticator.


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Specification of Requirements  . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  Protocol Overview  . . . . . . . . . . . . . . . . . . . . . .  7
   4.  Protocol Details . . . . . . . . . . . . . . . . . . . . . . .  9
     4.1.  Authentication and Authorization Phase . . . . . . . . . .  9
     4.2.  Access Phase . . . . . . . . . . . . . . . . . . . . . . . 12
     4.3.  Re-authentication Phase  . . . . . . . . . . . . . . . . . 12
     4.4.  Termination Phase  . . . . . . . . . . . . . . . . . . . . 14
   5.  Processing Rules . . . . . . . . . . . . . . . . . . . . . . . 15
     5.1.  Fragmentation  . . . . . . . . . . . . . . . . . . . . . . 15
     5.2.  Sequence Number and Retransmission . . . . . . . . . . . . 15
     5.3.  PANA Security Association  . . . . . . . . . . . . . . . . 16
     5.4.  Message Authentication . . . . . . . . . . . . . . . . . . 17
     5.5.  Message Validity Check . . . . . . . . . . . . . . . . . . 18
     5.6.  PaC Updating its IP Address  . . . . . . . . . . . . . . . 19
     5.7.  Session Lifetime . . . . . . . . . . . . . . . . . . . . . 19
     5.8.  Error Handling . . . . . . . . . . . . . . . . . . . . . . 20
   6.  Message Format . . . . . . . . . . . . . . . . . . . . . . . . 21
     6.1.  IP and UDP Headers . . . . . . . . . . . . . . . . . . . . 21
     6.2.  PANA Message Header  . . . . . . . . . . . . . . . . . . . 21
     6.3.  AVP Format . . . . . . . . . . . . . . . . . . . . . . . . 23
   7.  PANA Messages  . . . . . . . . . . . . . . . . . . . . . . . . 26
     7.1.  PANA-Client-Initiation (PCI) . . . . . . . . . . . . . . . 28
     7.2.  PANA-Auth-Request (PAR)  . . . . . . . . . . . . . . . . . 28
     7.3.  PANA-Auth-Answer (PAN) . . . . . . . . . . . . . . . . . . 29
     7.4.  PANA-Termination-Request (PTR) . . . . . . . . . . . . . . 29
     7.5.  PANA-Termination-Answer (PTA)  . . . . . . . . . . . . . . 29
     7.6.  PANA-Notification-Request (PNR)  . . . . . . . . . . . . . 29
     7.7.  PANA-Notification-Answer (PNA) . . . . . . . . . . . . . . 30
   8.  AVPs in PANA . . . . . . . . . . . . . . . . . . . . . . . . . 31
     8.1.  Algorithm AVP  . . . . . . . . . . . . . . . . . . . . . . 31
     8.2.  AUTH AVP . . . . . . . . . . . . . . . . . . . . . . . . . 32
     8.3.  EAP-Payload AVP  . . . . . . . . . . . . . . . . . . . . . 32
     8.4.  Failed-AVP AVP . . . . . . . . . . . . . . . . . . . . . . 32
     8.5.  Failed-Message-Header AVP  . . . . . . . . . . . . . . . . 32



Forsberg, et al.         Expires October 6, 2007                [Page 2]


Internet-Draft                    PANA                        April 2007


     8.6.  Key-Id AVP . . . . . . . . . . . . . . . . . . . . . . . . 33
     8.7.  Nonce AVP  . . . . . . . . . . . . . . . . . . . . . . . . 33
     8.8.  Result-Code AVP  . . . . . . . . . . . . . . . . . . . . . 33
       8.8.1.  Authentication Results Codes . . . . . . . . . . . . . 33
       8.8.2.  Protocol Error Result Codes  . . . . . . . . . . . . . 34
     8.9.  Session-Lifetime AVP . . . . . . . . . . . . . . . . . . . 36
     8.10. Termination-Cause AVP  . . . . . . . . . . . . . . . . . . 36
   9.  Retransmission Timers  . . . . . . . . . . . . . . . . . . . . 37
     9.1.  Transmission and Retransmission Parameters . . . . . . . . 38
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 39
     10.1. PANA UDP Port Number . . . . . . . . . . . . . . . . . . . 39
     10.2. PANA Message Header  . . . . . . . . . . . . . . . . . . . 39
       10.2.1. Version  . . . . . . . . . . . . . . . . . . . . . . . 39
       10.2.2. Message Type . . . . . . . . . . . . . . . . . . . . . 39
       10.2.3. Flags  . . . . . . . . . . . . . . . . . . . . . . . . 40
     10.3. AVP Header . . . . . . . . . . . . . . . . . . . . . . . . 40
       10.3.1. AVP Code . . . . . . . . . . . . . . . . . . . . . . . 40
       10.3.2. Flags  . . . . . . . . . . . . . . . . . . . . . . . . 41
     10.4. AVP Values . . . . . . . . . . . . . . . . . . . . . . . . 41
       10.4.1. Result-Code AVP Values . . . . . . . . . . . . . . . . 41
       10.4.2. Termination-Cause AVP Values . . . . . . . . . . . . . 41
   11. Security Considerations  . . . . . . . . . . . . . . . . . . . 42
     11.1. General Security Measures  . . . . . . . . . . . . . . . . 42
     11.2. Initial Exchange . . . . . . . . . . . . . . . . . . . . . 43
     11.3. EAP Methods  . . . . . . . . . . . . . . . . . . . . . . . 44
     11.4. Cryptographic Keys . . . . . . . . . . . . . . . . . . . . 44
     11.5. Per-packet Ciphering . . . . . . . . . . . . . . . . . . . 44
     11.6. PAA-to-EP Communication  . . . . . . . . . . . . . . . . . 45
     11.7. Liveness Test  . . . . . . . . . . . . . . . . . . . . . . 45
     11.8. Early Termination of a Session . . . . . . . . . . . . . . 45
   12. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 46
   13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 47
     13.1. Normative References . . . . . . . . . . . . . . . . . . . 47
     13.2. Informative References . . . . . . . . . . . . . . . . . . 47
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 49
   Intellectual Property and Copyright Statements . . . . . . . . . . 51















Forsberg, et al.         Expires October 6, 2007                [Page 3]


Internet-Draft                    PANA                        April 2007


1.  Introduction

   Providing secure network access service requires access control based
   on the authentication and authorization of the clients and the access
   networks.  Client-to-network authentication provides parameters that
   are needed to police the traffic flow through the enforcement points.
   A protocol is needed to carry authentication methods between the
   client and the access network.

   Scope of this work is identified as designing a network layer
   transport for network access authentication methods.  The Extensible
   Authentication Protocol (EAP) [RFC3748] provides such authentication
   methods.  In other words, PANA carries EAP which can carry various
   authentication methods.  By the virtue of enabling transport of EAP
   above IP, any authentication method that can be carried as an EAP
   method is made available to PANA and hence to any link-layer
   technology.  There is a clear division of labor between PANA (an EAP
   lower layer), EAP and EAP methods as described in [RFC3748].

   Various environments and usage models for PANA are identified in
   Appendix A of [RFC4058].  Potential security threats for
   network-layer access authentication protocol are discussed in
   [RFC4016].  These have been essential in defining the requirements
   [RFC4058] on the PANA protocol.  Note that some of these requirements
   are imposed by the chosen payload, EAP [RFC3748].

   There are components that are part of a complete secure network
   access solution but are outside of the PANA protocol specification,
   including authentication method choice, data traffic protection,
   PAA-EP protocol, and PAA discovery.  PANA authentication output is
   used for creating access control filters.  These components are
   described in separate documents (see [I-D.ietf-pana-framework],
   [I-D.ietf-pana-snmp] and [I-D.ietf-dhc-paa-option]).  The readers are
   recommended to read the PANA Framework document
   [I-D.ietf-pana-framework] prior to reading this protocol
   specification document.

1.1.  Specification of Requirements

   In this document, several words are used to signify the requirements
   of the specification.  These words are often capitalized.  The key
   words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
   "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document
   are to be interpreted as described in [RFC2119].







Forsberg, et al.         Expires October 6, 2007                [Page 4]


Internet-Draft                    PANA                        April 2007


2.  Terminology

   PANA Client (PaC):

      The client side of the protocol that resides in the access device
      (e.g., laptop, PDA, etc.).  It is responsible for providing the
      credentials in order to prove its identity (authentication) for
      network access authorization.  The PaC and the EAP peer are
      co-located in the same access device.

   PANA Authentication Agent (PAA):

      The protocol entity in the access network whose responsibility is
      to verify the credentials provided by a PANA client (PaC) and
      authorize network access to the access device.  The PAA and the
      EAP authenticator (and optionally the EAP server) are co-located
      in the same node.  Note the authentication and authorization
      procedure can, according to the EAP model, also be offloaded to
      the backend AAA infrastructure.

   PANA Session:

      A PANA session is established between the PANA Client (PaC) and
      the PANA Authentication Agent (PAA), and terminates as a result of
      an authentication or liveness test failure, a message delivery
      failure after retransmissions reach maximum values, session
      lifetime expiration, or an explicit termination message.  A fixed
      session identifier is maintained throughout a session.  A session
      cannot be shared across multiple network interfaces.

   Session Lifetime:

      A duration that is associated with a PANA session.  For an
      established PANA session, the session lifetime is bound to the
      lifetime of the current authorization given to the PaC.  The
      session lifetime can be updated[a1] by a new round of EAP
      authentication before it expires.

   Session Identifier:

      This identifier is used to uniquely identify a PANA session on the
      PaC and the PAA.  It is included in PANA messages to bind the
      message to a specific PANA session.  This bidirectional identifier
      is allocated by the PAA in the initial request message and freed
      when the session terminates.  The session identifier is assigned
      by the PAA and is unique within the PAA [a2]during the lifetime of the
      session.




Forsberg, et al.         Expires October 6, 2007                [Page 5]


Internet-Draft                    PANA                        April 2007


   PANA Security Association (PANA SA):

      A PANA security association is formed between the PaC and the PAA
      by sharing cryptographic keying material and associated context.
      The formed duplex security association is used to protect the
      bidirectional PANA signaling traffic between the PaC and PAA.

   Enforcement Point (EP):

      A node on the access network where per-packet enforcement policies
      (i.e., filters) are applied on the inbound and outbound traffic of
      access devices.  The EP and the PAA may be co-located.  EPs should
      prevent data traffic from and to any unauthorized client unless
      it's either PANA or one of the other allowed traffic types (e.g.,
      ARP, IPv6 neighbor discovery, DHCP, etc.).  Detailed enforcement
      policies may be specified in deployment-specific PANA
      applicability documents.
[a3]
   Master Session Key (MSK):

      A key derived by the EAP peer and the EAP server and transported
      to the EAP authenticator [RFC3748].

   For additional terminology definitions see the PANA framework
   document [I-D.ietf-pana-framework].


























Forsberg, et al.         Expires October 6, 2007                [Page 6]


Internet-Draft                    PANA                        April 2007


3.  Protocol Overview

   The PANA protocol is run between a client (PaC) and a server (PAA) in
   order to perform authentication and authorization for the network
   access service.

   The protocol messaging consists of a series of requests and answers,
   some of which may be initiated by either end.  Each message can carry
   zero or more AVPs within the payload.  The main payload of PANA is
   EAP which performs authentication.  PANA helps the PaC and PAA
   establish an EAP session.

   PANA is a UDP-based protocol.  It has its own retransmission
   mechanism to reliably deliver messages.

   PANA messages are sent between the PaC and PAA as part of a PANA
   session.  A PANA session consists of distinct phases:

   o  Authentication and authorization phase: This is the phase that
      initiates a new PANA session and executes EAP between the PAA and
      PaC.  The PANA session can be initiated by both the PaC and the
      PAA.  The EAP payload (which carry an EAP method inside) is what
      is used for authentication.  The PAA conveys the result of
      authentication and authorization to the PaC at the end of this
      phase.

   o  Access phase: After a successful authentication and authorization
      the host[a4] gains access to the network and can send and receive IP[a5]
      data traffic through the EP(s).  At any time during this phase,
      the PaC and PAA may optionally send PANA notification messages to
      test liveness of the PANA session on the peer.

   o  Re-authentication phase: During the access phase, the PAA must
      initiate re-authentication before the PANA session lifetime
      expires.  EAP is carried by PANA to perform authentication.[a6]  This
      phase may be optionally triggered by both the PaC and the PAA
      without any respect to the session lifetime. [a7] The session moves to
      this phase from the access phase, and returns back there upon
      successful re-authentication.

   o  Termination phase: The PaC or PAA may choose to discontinue the
      access service at any time.  An explicit disconnect message can be
      sent by either end.  If either the PaC or the PAA disconnects
      without engaging in termination messaging, it is expected that
      either the expiration of a finite session lifetime or failed
      liveness tests would clean up the session at the other end.

   Cryptographic protection of messages between the PaC and PAA is



Forsberg, et al.         Expires October 6, 2007                [Page 7]


Internet-Draft                    PANA                        April 2007


   possible as soon as EAP in conjunction with the EAP method exports a
   shared key.  That shared key is used to create a PANA SA.  The PANA
   SA helps generate per-message authentication codes that provide
   integrity protection and authentication.

   Throughout the lifetime of a session, various problems found with the
   incoming messages can generate an error request message (see
   Section 5.8) sent in response.[a8]











































Forsberg, et al.         Expires October 6, 2007                [Page 8]


Internet-Draft                    PANA                        April 2007


4.  Protocol Details

   The following sections explain in detail the various phases of a PANA
   session.

4.1.  Authentication and Authorization Phase

   The main task of the authentication and authorization phase is to
   establish a PANA session and carry EAP messages between the PaC and
   the PAA.  The PANA session can be initiated by either the PaC or the
   PAA.

   PaC-initiated Session:

      When the PaC initiates a PANA session, it sends a
      PANA-Client-Initiation message to the PAA.  When the PaC is not
      configured with an IP address of the PAA before initiating the
      PANA session, DHCP [I-D.ietf-dhc-paa-option] is used as the
      default method for dynamically configuring the IP address of the
      PAA.  Alternative methods for dynamically discovering the IP
      address of the PAA may be used for PaC-initiated session but they
      are outside the scope of this specification.  The PAA that
      receives the PANA-Client-Initiation message MUST respond to the
      PaC with a PANA-Auth-Request message.

   PAA-initiated Session:

      When the PAA knows the IP address of the PaC, it MAY send an
      unsolicited PANA-Auth-Request to the PaC.  The details of how PAA
      can learn the IP address of the PaC are outside the scope of this
      specification.

   A session identifier for the session is assigned by the PAA and
   carried in the initial PANA-Auth-Request message.  The same session
   identifier MUST be carried in the subsequent messages exchanged
   between the PAA and PaC throughout the session.

   When the PaC receives the initial PANA-Auth-Request message from a
   PAA, it responds with a PANA-Auth-Answer message, if it wishes to
   continue the PANA session.

   The initial PANA-Auth-Request and PANA-Auth-Answer messages MUST have
   'S' (Start) bit set, regardless of whether the session is initiated
   by the PaC or the PAA.  Non-initial PANA-Auth-Request and
   PANA-Auth-Answer messages as well as any other messages MUST NOT have
   'S' bit set.

   The PAA SHOULD limit the rate it processes incoming

[a9]

Forsberg, et al.         Expires October 6, 2007                [Page 9]


Internet-Draft                    PANA                        April 2007


   PANA-Client-Initiation messages in order not to subject itself to
   denial-of service (DoS) attacks.  Details of rate limiting are
   outside the scope of this specification.

   An Algorithm AVP MAY be included in the initial PANA-Auth-Request in
   order to indicate required and available capabilities for the network
   access.  This AVP MAY be used by the PaC for assessing the capability
   match even before the authentication takes place.  Since this AVP is
   provided in the insecure initial request, there are certain security
   risks involved in using the provided information.  See Section 11 for
   further discussion on this.

   If the PAA wants to stay stateless in response to a
   PANA-Client-Initiation message, it SHOULD NOT include an EAP-Payload
   AVP in the initial PANA-Auth-Request message, and it SHOULD NOT re-
   transmit the message on a timer.  For this reason, the PaC MUST
   retransmit the PANA-Client-Initiation message until it enters the
   authentication and authorization phase by receiving the second
   PANA-Auth-Request message (not a retransmission of the initial one)
   from the PAA.
[a10]
   It is possible that both the PAA and the PaC initiate the PANA
   session at the same time, i.e., the PAA unsolicitedly sends the
   initial PANA-Auth-Request message while the PaC sends a
   PANA-Client-Initiation message.  To resolve the race condition, the
   PAA SHOULD silently discard the PANA-Client-Initiation message
   received from the PaC after it has sent the initial PANA-Auth-Request
   message.  The PAA uses the source IP address and the source port
   number of the PANA-Client-Initiation message to identify the PaC
   among multiple PANA-Client-Initiation messages sent from different
   PaCs.

   EAP messages are carried in PANA-Auth-Request messages.
   PANA-Auth-Answer messages are simply used to acknowledge receipt of
   the requests.  As an optimization, a PANA-Auth-Answer message MAY
   include the EAP message.  This optimization SHOULD NOT be used when
   it takes time to generate the EAP message (due to, e.g., intervention
   of human input), in which case returning an PANA-Auth-Answer message
   without piggybacking an EAP message can avoid unnecessary
   retransmission of the PANA-Auth-Request message.

   A Nonce AVP MUST be included in the first non-initial
   PANA-Auth-Request and PANA-Auth-Answer messages, and MUST NOT be
   included in any other message.

   The result of PANA authentication is carried in the last
   PANA-Auth-Request message sent from the PAA to the PaC.  This message
   carries the EAP authentication result and the result of PANA



Forsberg, et al.         Expires October 6, 2007               [Page 10]


Internet-Draft                    PANA                        April 2007


   authentication.  The last PANA-Auth-Request message MUST be
   acknowledged with a PANA-Auth-Answer message.  The last
   PANA-Auth-Request and PANA-Auth-Answer messages MUST have 'C'
   (Complete) bit set, and any other message MUST NOT have 'C' bit set.
   Figure 1 shows an example sequence in the authentication and
   authorization phase for a PaC-initiated session.

   PaC      PAA  Message(sequence number)[AVPs]
   --------------------------------------------------------------------
      ----->     PANA-Client-Initiation(0)
      <-----     PANA-Auth-Request(x)         // 'S' bit set
      ----->     PANA-Auth-Answer(x)          // 'S' bit set
      <-----     PANA-Auth-Request(x+1)[Nonce, EAP]
      ----->     PANA-Auth-Answer(x+1)[Nonce] // No piggybacking EAP
      ----->     PANA-Auth-Request(y)[EAP]
      <-----     PANA-Auth-Answer(y)
      <-----     PANA-Auth-Request(x+2)[EAP]
      ----->     PANA-Auth-Answer(x+2)[EAP][a11]
      <-----     PANA-Auth-Request(x+3)[Result-Code, EAP, Key-Id,
                                            Algorithm, Lifetime, AUTH]
                                               // 'C' bit set
      ----->     PANA-Auth-Answer(x+3)[Key-Id, AUTH]
                                               // 'C' bit set

    Figure 1: Example sequence for the authentication and authorization
                     phase for a PaC-initiated session

   When an EAP method that is capable of deriving keys is used during
   the authentication and authorization phase and the keys are
   successfully derived, the last PANA-Auth-Request message MUST contain
   a Key-Id AVP and an AUTH AVP, and an Algorithm AVP for the first
   derivation of keys in the session, and any subsequent message MUST
   contain an AUTH AVP.  An Algorithm AVP MUST NOT be contained in any
   PANA-Auth-Request message after the first derivation of keys in the
   session.

   EAP authentication can fail at a pass-through authenticator without
   sending an EAP Failure message [RFC4137].  When this occurs, the PAA
   SHOULD silently terminate the session, expecting that a session
   timeout on the PaC will clean up the state on the PaC.

   There is a case where EAP authentication succeeds with producing an
   EAP Success message but network access authorization fails due to,
   e.g., authorization rejected by a AAA or authorization locally
   rejected by the PAA.  When this occurs, the PAA MUST send the last
   PANA-Auth-Request with a result code PANA_AUTHORIZATION_REJECTED.  If
   an MSK is available, the last PANA-Auth-Request and PANA-Auth-Answer
   messages MUST be protected with an AUTH AVP and carry a Key-Id AVP.



Forsberg, et al.         Expires October 6, 2007               [Page 11]


Internet-Draft                    PANA                        April 2007


   The last PANA-Auth-Request message MUST also carry an Algorithm AVP
   if it is for the first derivation of keys in the session.  The PANA
   session MUST be deleted immediately after the last PANA-Auth message
   exchange.
[a12]
4.2.  Access Phase

   Once the authentication and authorization phase or the
   re-authentication phase successfully completes,[a13] the PaC gains access
   to the network and can send and receive IP data traffic through the
   EP(s) and the PANA session enters the access phase.  In this phase,
   PANA-Notification-Request and PANA-Notification-Answer messages with
   'P' (Ping) bit set (ping request and ping answer messages,
   respectively) can be used for testing the liveness of the PANA
   session on the PANA peer.  Both the PaC and the PAA are allowed to
   send a ping request 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 ping answer message.  The ping request and answer
   messages MUST be protected with an AUTH 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.  Additionally, an implementation MAY
   rate-limit processing of  the incoming ping requests.  It should be noted
   that if a PAA or PaC which considers its connectivity lost after a
   relatively small number of unresponsive pings coupled with a peer
   that is aggressively rate-limiting the ping request and answer
   messages, false-positives could result. [a14] Care should be taken when
   rate-limiting ping request and answer messages to periodically
   respond, and a PAA or PaC should not rely on ping request and answer
   messages to quickly determine loss of connectivity.

4.3.  Re-authentication Phase

   The PANA session in the access phase can enter the re-authentication
   phase to extend the current session lifetime by re-executing EAP.
   Once the re-authentication phase successfully completes, the session
   re-enters the access phase.  Otherwise, the session is deleted.[a15]

   When the PaC wants to initiate re-authentication, it sends a
   PANA-Notification-Request message with 'A' bit set (a re-
   authentication request message) to the PAA.  This message MUST
   contain the session identifier assigned to the session being
   re-authenticated.  If the PAA already has an established PANA session
   for the PaC with the matching session identifier, it MUST first
   respond with a PANA-Notification-Answer message with 'A' bit set (a



Forsberg, et al.         Expires October 6, 2007               [Page 12]


Internet-Draft                    PANA                        April 2007


   re-authentication answer message), followed by a PANA-Auth-Request
   message that starts a new EAP authentication.  If the PAA cannot
   identify the session, it MUST silently discard the message.  The
   first PANA-Auth-Request and PANA-Auth-Answer messages in the
   re-authentication phase MUST have 'S' bit cleared [a16]and carry a Nonce
   AVP.

   The PaC may receive a PANA-Auth-Request before receiving the answer
   to its outstanding re-authentication request message.  This condition
   can arise due to packet re-ordering or a race condition between the
   PaC and PAA when they both attempt to engage in re-authentication.
   The PaC MUST keep discarding the received PANA-Auth-Requests until it
   receives the answer to its request.
[a17]
   When the PAA initiates re-authentication, it sends a
   PANA-Auth-Request message containing the session identifier for the
   PaC.  The PAA MUST initiate EAP re-authentication before the current
   session lifetime expires.

   Re-authentication of an on-going PANA session MUST NOT reset the
   sequence numbers.

   For any re-authentication, if there is an established PANA SA, re-
   authentication request and answer messages and subsequent
   PANA-Auth-Request and PANA-Auth-Answer messages MUST be protected
   with an AUTH AVP.  The final PANA-Auth-Request and PANA-Auth-Answer
   messages and any subsequent PANA message MUST be protected by using
   the key generated from the latest EAP authentication.

   PaC      PAA  Message(sequence number)[AVPs]
   ------------------------------------------------------
      ----->     PANA-Notification-Request(q)[AUTH] // 'A' bit set
      <-----     PANA-Notification-Answer(q)[AUTH]  // 'A' bit set
      <-----     PANA-Auth-Request(p)[EAP, Nonce, AUTH]
      ----->     PANA-Auth-Answer(p)[AUTH, Nonce]
      ----->     PANA-Auth-Request(q+1)[EAP, AUTH]
      <-----     PANA-Auth-Answer(q+1)[AUTH]
      <-----     PANA-Auth-Request(p+1)[EAP, AUTH]
      ----->     PANA-Auth-Answer(p+1)[EAP, AUTH]
      <-----     PANA-Auth-Request(p+2)[Result-Code, EAP, Key-Id,
                                             Algorithm, Lifetime, AUTH]
                                                     // 'C' bit set
      ----->     PANA-Auth-Answer(p+2)[Key-Id, AUTH]// 'C' bit set

   Figure 2: Example sequence for the re-authentication phase initiated
                                  by PaC





Forsberg, et al.         Expires October 6, 2007               [Page 13]


Internet-Draft                    PANA                        April 2007


4.4.  Termination Phase

   A procedure for explicitly terminating a PANA session can be
   initiated either from the PaC (i.e., disconnect indication) or from
   the PAA (i.e., session revocation).  The PANA-Termination-Request and
   PANA-Termination-Answer message exchanges are used for disconnect
   indication and session revocation procedures.

   The reason for termination is indicated in the Termination-Cause AVP.
   When there is an established PANA SA between the PaC and the PAA, all
   messages exchanged during the termination phase MUST be protected
   with an AUTH AVP.  When the sender of the PANA-Termination-Request
   message receives a valid acknowledgment, all states maintained for
   the PANA session MUST be deleted immediately.





































Forsberg, et al.         Expires October 6, 2007               [Page 14]


Internet-Draft                    PANA                        April 2007


5.  Processing Rules

5.1.  Fragmentation

   PANA does not provide fragmentation of PANA messages.  Instead, it
   relies on fragmentation provided by EAP methods and IP layer when
   needed.

5.2.  Sequence Number and Retransmission

   PANA uses sequence numbers to provide ordered and reliable delivery
   of messages.

   The PaC and PAA maintain two sequence numbers: 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. [a18] These sequence numbers are 32-bit
   unsigned numbers.  They are monotonically incremented by 1 as new
   requests are generated and received, and wrapped to zero on the next
   message after 2^32-1.  Answers always contain the same sequence
   number as the corresponding request.  Retransmissions reuse the
   sequence number contained in the original packet.

   The initial sequence numbers (ISN) are randomly picked by the PaC and
   PAA as they send their very first request messages except 
   PANA-Client-Initiation message that MUST be always 0. 
   When a request message is received, it is considered valid in terms
   of sequence numbers if and only if its sequence number matches the
   expected value.  This check does not apply to the
   PANA-Client-Initiation message and the initial PANA-Auth-Request
   message.

   When an answer message is received, it is considered valid in terms
   of sequence numbers if and only if its sequence number matches that
   of the currently outstanding request.  A peer can only have one
   outstanding request at a time.

   PANA request messages are retransmitted based on a timer until a
   response[a19] 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[a20] immediately).

   The retransmission timers SHOULD be calculated as described in
   Section 9 unless a given deployment chooses to use its own
   retransmission timers optimized for the underlying link-layer
   characteristics.

   Unless dropped due to rate limiting, the PaC and PAA MUST respond to



Forsberg, et al.         Expires October 6, 2007               [Page 15]


Internet-Draft                    PANA                        April 2007


   all duplicate request messages received.  The last transmitted answer
   MAY be cached in case it is not received by the peer and that
   generates a retransmission of the last request.  When available, the
   cached answer can be used instead of fully processing the
   retransmitted request and forming a new answer from scratch.

5.3.  PANA Security Association

   A PANA SA is created as an attribute of a PANA session when EAP
   authentication succeeds with a creation of an MSK.  A PANA SA is not
   created when the PANA authentication fails or no MSK is produced by
   the EAP authentication method.  When a new MSK is derived in the PANA
   re-authentication phase, any key derived from the old MSK MUST be
   updated to a new one that is derived from the new MSK.  In order to
   distinguish the new MSK from old ones, one Key-Id AVP MUST be carried
   in the last PANA-Auth-Request and PANA-Auth-Answer messages at the
   end of the EAP authentication which resulted in deriving a new MSK.
   The Key-Id AVP is of type Unsigned32 and MUST contain a value that
   uniquely identifies the MSK within the PANA session.  The last
   PANA-Auth-Answer message in response to the last PANA-Auth-Request
   message with a Key-Id AVP MUST contain a Key-Id AVP with the same MSK
   identifier carried in the request.  The last PANA-Auth-Request and
   PANA-Auth-Answer messages with a Key-Id AVP MUST also carry an AUTH
   AVP whose value is computed by using the new PANA_AUTH_KEY derived
   from the new MSK.  Although the specification does not mandate a
   particular method for calculation of the Key-Id AVP value, a simple
   method is to use monotonically increasing numbers.

   The PANA session lifetime is bounded by the authorization lifetime
   granted by the authentication server (same as the MSK lifetime).  The
   lifetime of the PANA SA (hence the PANA_AUTH_KEY) is the same as the
   lifetime of the PANA session.  The created PANA SA is deleted when
   the corresponding PANA session is deleted.

   PANA SA attributes as well as PANA session attributes are listed
   below:

   PANA Session attributes:

      *  Session Identifier

      *  IP address and UDP port number of the PaC.

      *  IP address and UDP port number of the PAA

      *  Sequence number of the last transmitted request





Forsberg, et al.         Expires October 6, 2007               [Page 16]


Internet-Draft                    PANA                        April 2007


      *  Sequence number of the last received request

      *  Last transmitted message payload

      *  Retransmission interval

      *  Session lifetime

      *  PANA SA attributes

   PANA SA attributes:

      *  Nonce generated by PaC (PaC_nonce)

      *  Nonce generated by PAA (PAA_nonce)

      *  MSK

      *  MSK Identifier

      *  PANA_AUTH_KEY

      *  Pseudo-random function

      *  Integrity algorithm

   The PANA_AUTH_KEY is derived from the available MSK and it is used to
   integrity protect PANA messages.  The PANA_AUTH_KEY is computed in
   the following way:

    PANA_AUTH_KEY = prf+(MSK, PaC_nonce|PAA_nonce|Session_ID|Key_ID)

   where the prf+ function is defined in IKEv2 [RFC4306].  The
   pseudo-random function to be used for the prf+ function is specified
   in the Algorithm AVP in the last PANA-Auth-Request message.  The
   length of PANA_AUTH_KEY depends on the integrity algorithm in use.
   See Section 5.4 for the detailed usage of the PANA_AUTH_KEY.
   PaC_nonce and PAA_nonce are values of the Nonce AVP carried in the
   first non-initial PANA-Auth-Answer and PANA-Auth-Request messages in
   the authentication and authorization phase or the first
   PANA-Auth-Answer and PANA-Auth-Request messages in the
   re-authentication phase, respectively.  Session_ID is the session
   identifier of the session.  Key_ID is the value of the Key-ID AVP.

5.4.  Message Authentication

   A PANA message can contain an AUTH AVP for cryptographically
   protecting the message.



Forsberg, et al.         Expires October 6, 2007               [Page 17]


Internet-Draft                    PANA                        April 2007


   When an AUTH AVP is included in a PANA message, the value field of
   the AUTH AVP is calculated by using the PANA_AUTH_KEY in the
   following way:

      AUTH AVP value = PANA_AUTH_HASH(PANA_AUTH_KEY, PANA_PDU)

   where PANA_PDU is the PANA message including the PANA header, with
   the AUTH AVP value field first initialized to 0.  PANA_AUTH_HASH
   represents the integrity algorithm specified in the Algorithm AVP in
   the last PANA-Auth-Request message.  The PaC and PAA MUST use the
   same integrity algorithm to calculate an AUTH AVP they originate and
   receive.  The algorithm is determined by the PAA.  When the PaC does
   not support the integrity algorithm specified in the last
   PANA-Auth-Request message, it MUST silently discard the message.

5.5.  Message Validity Check

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

   o  Each field in the message header contains a valid value including
      sequence number, message length, message type, version number,
      flags, session identifier, etc.

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

      *  In the authentication and authorization phase and the
         re-authentication phase:

         +  PANA-Client-Initiation after completion of the initial
            PANA-Auth-Request and PANA-Auth-Answer exchange.

         +  Re-authentication request.[a21]

         +  The last PANA-Auth-Request as well as ping request before
            completion of the initial PANA-Auth-Request and
            PANA-Auth-Answer exchange.

         +  The initial PANA-Auth-Request after a PaC receives a valid
            non-initial PANA-Auth-Request.

         +  PANA-Termination-Request.[a22]

      *  In the access phase:





Forsberg, et al.         Expires October 6, 2007               [Page 18]


Internet-Draft                    PANA                        April 2007


         +  PANA-Auth-Request.[a23]

         +  PANA-Client-Initiation.

      *  In the termination phase:

         +  PANA-Client-Initiation.

         +  All requests but PANA-Termination-Request.

   o  The message payload contains a valid set of AVPs allowed for the
      message type and there is no missing AVP that needs to be included
      in the payload and no AVP, which needs to be at a fixed position,
      is included in a position different from this fixed position.

   o  Each AVP is decoded correctly.

   o  When an AUTH AVP is included, the AVP value matches the hash value
      computed against the received message.

   Invalid messages MUST be discarded in order to provide robustness
   against DoS attacks.  In addition, an error request message MAY be
   returned to the sender.  See Section 5.8 for details.

5.6.  PaC Updating its IP Address

   A PaC's IP address used for PANA can change in certain situations,
   e.g., when the PaC moves from one IP link to another within the same
   PAA's realm.  In order to maintain the PANA session, the PAA needs to
   be notified about the change of PaC address.

   After the PaC has changed its IP address used for PANA, it MUST send
   any valid PANA message, except for an error request or answer, to the
   PAA.  If the message that carries the new PaC IP address in the
   Source Address field of the IP header is valid, the PAA MUST update
   the PANA session with the new PaC address.  If there is an
   established PANA SA, the message MUST be protected with an AUTH AVP.

5.7.  Session Lifetime

   The authentication and authorization phase determines the PANA
   session lifetime when the network access authorization succeeds.  The
   Session-Lifetime AVP MAY be optionally included in the last
   PANA-Auth-Request message to inform the PaC about the valid lifetime
   of the PANA session.  It MUST be ignored when included in other PANA
   messages.

   When the Session-Lifetime AVP is not included in the last



Forsberg, et al.         Expires October 6, 2007               [Page 19]


Internet-Draft                    PANA                        April 2007


   PANA-Auth-Request message then the PaC has no knowledge about a PANA
   session limitation and must therefore conclude that the session is
   not limited.

   The lifetime is a non-negotiable parameter that can be used by the
   PaC to manage PANA-related state.  The PaC does not have to perform
   any actions when the lifetime expires, other than purging local
   state.  The PAA MUST initiate the re-authentication phase before the
   current session lifetime expires.

   The PaC and the PAA MAY use information obtained outside PANA (e.g.,
   lower-layer indications) to expedite the detection of a disconnected
   peer.  Availability and reliability of such indications MAY depend on
   a specific link-layer or network topology and are therefore only
   hints.  A PANA peer SHOULD use the ping request and answer exchange
   to verify that a peer is, in fact, no longer alive, unless
   information obtained outside PANA is being used to expedite the
   detection of a disconnected peer.

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

5.8.  Error Handling

   A PANA-Notification-Request message with 'E' (Error) bit set (an
   error request message) MAY be sent by either the PaC or the PAA when
   a badly formed PANA message is received or in case of other errors.
   The receiver of this request MUST respond with a
   PANA-Notification-Answer message with 'E' bit set (an error answer
   message).

   An adversary might craft erroneous PANA messages to launch a DoS
   attack.  Unless the PaC or the PAA performs a rate-limitation of the
   generated error request messages it may be overburdened by responding
   to bogus messages.  Note that an error answer message that is sent in
   response to an error request message does not require either the PaC
   or the PAA to create a PANA protocol state.

   If an error request or answer message is sent unprotected (i.e.,
   without using an AUTH AVP) then the message MUST be processed such
   that the receiver does not change its PANA protocol state.







Forsberg, et al.         Expires October 6, 2007               [Page 20]


Internet-Draft                    PANA                        April 2007


6.  Message Format

   This section defines message formats for PANA protocol.

6.1.  IP and UDP Headers

   Any PANA message is unicast between the PaC and the PAA.

   For any PANA message sent from the peer that has initiated the PANA
   session, the UDP source port is set to any number and the destination
   port is set to the assigned PANA port number (to be assigned by
   IANA).  For any PANA message sent from the other peer, the source
   port is set to the assigned PANA port number (to be assigned by IANA)
   and the destination port is copied from the source port of the last
   received message.  [a24]In case both the PaC and PAA initiates the session
   (i.e., PANA-Client-Initiation and unsolicited PANA-Auth-Request
   messages cross each other), then the PaC is identified as the
   initiator.

6.2.  PANA Message Header

   A summary of the PANA message header format is shown below.  The
   fields are transmitted in network byte order.


    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    Version    |   Reserved    |        Message Length         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |             Flags             |         Message Type          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                      Session Identifier                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                        Sequence Number                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  AVPs ...
   +-+-+-+-+-+-+-+-+-+-+-+-+-

   Version

      This Version field MUST be set to 1 to indicate PANA Version 1.

   Reserved

      This 8-bit field is reserved for future use, and MUST be set to
      zero, and ignored by the receiver.




Forsberg, et al.         Expires October 6, 2007               [Page 21]


Internet-Draft                    PANA                        April 2007


   Message Length

      The Message Length field is two octets and indicates the length of
      the PANA message including the header fields.

   Flags

      The Flags field is two octets.  The following bits are assigned:

    0                   1
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |R S C A P E r r r r r r r r r r|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      R (Request)

         If set, the message is a request.  If cleared, the message is
         an answer.

      S (Start)

         If set, the message is the first PANA-Auth-Request or PANA-
         Auth-Answer in authentication and authorization phase.  For
         other messages, this bit MUST be cleared.

      C (Complete)

         If set, the message is the last PANA-Auth-Request or PANA-Auth-
         Answer in authentication and authorization phase.  For other
         messages this bit MUST be cleared.

      A (re-Authentication)

         If set, the message is a PANA-Notification-Request or PANA-
         Notification-Answer to initiate re-authentication.  For other
         messages this bit MUST be cleared.

      P (Ping)

         If set, the message is a PANA-Notification-Request or PANA-
         Notification-Answer for liveness test.  For other messages this
         bit MUST be cleared.

      E (Error)

         If set, the message is a PANA-Notification-Request or PANA-
         Notification-Answer for error indication.  For other messages



Forsberg, et al.         Expires October 6, 2007               [Page 22]


Internet-Draft                    PANA                        April 2007


         this bit MUST be cleared.

      r (reserved)

         These flag bits are reserved for future use, and MUST be set to
         zero, and ignored by the receiver.

   Message Type

      The Message Type field is two octets, and is used in order to
      communicate the message type with the message.  The 16-bit address
      space is managed by IANA [ianaweb].

   Session Identifier

      This field contains a 32 bit session identifier.

   Sequence Number

      This field contains contains a 32 bit sequence number.

   AVPs

      AVPs are a method of encapsulating information relevant to the
      PANA message.  See section Section 6.3 for more information on
      AVPs.

6.3.  AVP Format

   Each AVP of type OctetString MUST be padded to align on a 32-bit
   boundary, while other AVP types align naturally.  A number of
   zero-valued bytes are added to the end of the AVP Value field till a
   word boundary is reached.  The length of the padding is not reflected
   in the AVP Length field [RFC3588].

   The fields in the AVP are sent in network byte order.  The AVP format
   is:














Forsberg, et al.         Expires October 6, 2007               [Page 23]


Internet-Draft                    PANA                        April 2007


    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           AVP Code            |           AVP Flags           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          AVP Length           |            Reserved           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         Vendor-Id (opt)                       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    Value ...
   +-+-+-+-+-+-+-+-+

   AVP Code

      The AVP Code, together with the optional Vendor ID field,
      identifies attribute that follows.  If the V-bit is not set, the
      Vendor ID is not present and the AVP Code refers to an IETF
      attribute.

   AVP Flags

      The AVP Flags field is two octets.  The following bits are
      assigned:

    0                   1
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |V M r r r r r r r r r r r r r r|
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      V (Vendor)

         The 'V' bit, known as the Vendor-Specific bit, indicates
         whether the optional Vendor-Id field is present in the AVP
         header.  When set the AVP Code belongs to the specific vendor
         code address space.

      M (Mandatory)

         The 'M' Bit, known as the Mandatory bit, indicates whether
         support of the AVP is required.  If an AVP with the 'M' bit set
         is received by the PaC or PAA and either the AVP or its value
         is unrecognized, the message MUST be rejected and the receiver
         MUST send a PANA-Notification-Request message with 'E' bit set.
         If the AVP was unrecognized the result code of the PANA-
         Notification-Request message with 'E' bit set MUST be
         PANA_AVP_UNSUPPORTED.  If the AVP value was unrecognized the
         result code of the PANA-Notification-Request message with 'E'



Forsberg, et al.         Expires October 6, 2007               [Page 24]


Internet-Draft                    PANA                        April 2007


         bit set MUST be PANA_INVALID_AVP_DATA.  In either case the
         PANA-Notification-Request message with 'E' bit set MUST carry a
         Failed-AVP AVP containing the offending mandatory AVP.  AVPs
         with the 'M' bit cleared are informational only and a receiver
         that receives a message with such an AVP that is not
         recognized, or whose value is not recognized, MAY simply ignore
         the AVP.

      r (reserved)

         These flag bits are reserved for future use, and MUST be set to
         zero, and ignored by the receiver.

   AVP Length

      The AVP Length field is two octets, and indicates the number of
      octets in the Value field.  The length of the AVP Code, AVP
      Length, AVP Flags, Reserved and Vendor-Id fields are not counted
      in the AVP Length value.

   Reserved

      This two-octet field is reserved for future use, and MUST be set
      to zero, and ignored by the receiver.

   Vendor-Id

      The Vendor-Id field is present if the 'V' bit is set in the AVP
      Flags field.  The optional four-octet Vendor-Id field contains the
      IANA assigned "SMI Network Management Private Enterprise Codes"
      [ianaweb] value, encoded in network byte order.  Any vendor
      wishing to implement a vendor-specific PANA AVP MUST use their own
      Vendor-Id along with their privately managed AVP address space,
      guaranteeing that they will not collide with any other vendor's
      vendor-specific AVP(s), nor with future IETF applications.

   Value

      The Value field is zero or more octets and contains information
      specific to the Attribute.  The format of the Value field is
      determined by the AVP Code and Vendor-Id fields.  The length of
      the Value field is determined by the AVP Length field.

   Unless otherwise noted, AVPs defined in this document will have the
   following default AVP Flags field settings: The 'M' bit MUST be set.
   The 'V' bit MUST NOT be set.





Forsberg, et al.         Expires October 6, 2007               [Page 25]


Internet-Draft                    PANA                        April 2007


7.  PANA Messages

   Each Request/Answer message pair is assigned a Sequence Number, and
   the sub-type (i.e., request or answer) is identified via the 'R'
   (Request) bit in the Message Flags field of the PANA message header.

   Every PANA message MUST contain a message type in its header's
   Message Type field, which is used to determine the action that is to
   be taken for a particular message.  Figure 3 lists all PANA messages
   defined in this document:

   Message-Name              Abbrev. ID PaC<->PAA  Ref.
   ----------------------------------------------------------
   PANA-Client-Initiation     PCI    1  -------->  7.1
   PANA-Auth-Request          PAR    2  <------->  7.2
   PANA-Auth-Answer           PAN    2  <------->  7.3
   PANA-Termination-Request   PTR    3  <------->  7.4
   PANA-Termination-Answer    PTA    3  <------->  7.5
   PANA-Notification-Request  PNR    4  <------->  7.6
   PANA-Notification-Answer   PNA    4  <------->  7.7
   -----------------------------------------------------------

                     Figure 3: Table of PANA Messages

   Every PANA message defined MUST include a corresponding ABNF
   [RFC2234] specification, which is used to define the AVPs that MUST
   or MAY be present.  The following format is used in the definition:

  message-def      = Message-Name "::=" PANA-message

  message-name     = PANA-name

  PANA-name        = ALPHA *(ALPHA / DIGIT / "-")

  PANA-message     = header  [ *fixed] [ *required] [ *optional]
                     [ *fixed]

  header           = "< PANA-Header: " Message-Type
                     [r-bit] [s-bit] [c-bit] [a-bit] [p-bit] [e-bit] ">"

  Message-Type     = 1*DIGIT
                     ; The Message Type assigned to the message

  r-bit            = ", REQ"
                     ; If present, the 'R' bit in the Message
                     ; Flags is set, indicating that the message
                     ; is a request, as opposed to an answer.




Forsberg, et al.         Expires October 6, 2007               [Page 26]


Internet-Draft                    PANA                        April 2007


  s-bit            = ", STA"
                     ; If present, the 'S' bit in the Message
                     ; Flags is set, indicating that the message
                     ; is the initial PAR or PAN in authentication
                     ; and authorization phase.

  c-bit            = ", COM"
                     ; If present, the 'C' bit in the Message
                     ; Flags is set, indicating that the message
                     ; is the final PAR and PAN in authentication
                     ; and authorization phase or re-authentication
                     ; phase.

  a-bit            = ", REA"
                     ; If present, the 'A' bit in the Message
                     ; Flags is set, indicating that the message
                     ; is a re-authentication request or answer.

  p-bit            = ", PIN"
                     ; If present, the 'P' bit in the Message
                     ; Flags is set, indicating that the message
                     ; is a ping request or answer.

  e-bit            = ", ERR"
                     ; If present, the 'E' bit in the Message
                     ; Flags is set, indicating that the message
                     ; is an error request or answer.

  fixed            = [qual] "<" avp-spec ">"
                     ; Defines the fixed position of an AVP.

  required         = [qual] "{" avp-spec "}"
                     ; The AVP MUST be present and can appear
                     ; anywhere in the message.

  optional         = [qual] "[" avp-name "]"
                     ; The avp-name in the 'optional' rule cannot
                     ; evaluate to any AVP Name which is included
                     ; in a fixed or required rule.  The AVP can
                     ; appear anywhere in the message.

  qual             = [min] "*" [max]
                     ; See ABNF conventions, RFC 2234 Section 6.6.
                     ; The absence of any qualifiers depends on whether
                     ; it precedes a fixed, required, or optional
                     ; rule.  If a fixed or required rule has no
                     ; qualifier, then exactly one such AVP MUST
                     ; be present.  If an optional rule has no



Forsberg, et al.         Expires October 6, 2007               [Page 27]


Internet-Draft                    PANA                        April 2007


                     ; qualifier, then 0 or 1 such AVP may be
                     ; present.
                     ;
                     ; NOTE:  "[" and "]" have a different meaning
                     ; than in ABNF (see the optional rule, above).
                     ; These braces cannot be used to express
                     ; optional fixed rules (such as an optional
                     ; AUTH at the end).  To do this, the convention
                     ; is '0*1fixed'.

  min              = 1*DIGIT
                     ; The minimum number of times the element may
                     ; be present.  The default value is zero.

  max              = 1*DIGIT
                     ; The maximum number of times the element may
                     ; be present.  The default value is infinity.  A
                     ; value of zero implies the AVP MUST NOT be
                     ; present.

  avp-spec         = PANA-name
                     ; The avp-spec has to be an AVP Name, defined
                     ; in the base or extended PANA protocol
                     ; specifications.

  avp-name         = avp-spec / "AVP"
                     ; The string "AVP" stands for *any* arbitrary
                     ; AVP Name, which does not conflict with the
                     ; required or fixed position AVPs defined in
                     ; the message definition.

7.1.  PANA-Client-Initiation (PCI)

   The PANA-Client-Initiation (PCI) message is used for PaC-initiated
   session.  The Sequence Number and Session Identifier fields in this
   message MUST be set to zero (0).

   PANA-Client-Initiation ::= < PANA-Header: 1 >
                    *  [ AVP ]

7.2.  PANA-Auth-Request (PAR)

   The PANA-Auth-Request (PAR) message is either sent by the PAA or the
   PaC.

   The message MUST NOT have both 'S' and 'C' bits set.





Forsberg, et al.         Expires October 6, 2007               [Page 28]


Internet-Draft                    PANA                        April 2007


   PANA-Auth-Request ::= < PANA-Header: 2, REQ[,STA][,COM] >
                       [ EAP-Payload ]
                       [ Algorithm ]
                       [ Nonce ]
                       [ Result-Code ]
                       [ Session-Lifetime ]
                       [ Key-Id ]
                    *  [ AVP ]
                   0*1 < AUTH >

7.3.  PANA-Auth-Answer (PAN)

   The PANA-Auth-Answer (PAN) message is sent by either the PaC or the
   PAA in response to a PANA-Auth-Request message.

   The message MUST NOT have both 'S' and 'C' bits set.

   PANA-Auth-Answer ::= < PANA-Header: 2 [,STA][,COM] >
                       [ Nonce ]
                       [ EAP-Payload ]
                       [ Key-Id ]
                    *  [ AVP ]
                   0*1 < AUTH >

7.4.  PANA-Termination-Request (PTR)

   The PANA-Termination-Request (PTR) message is sent either by the PaC
   or the PAA to terminate a PANA session.

   PANA-Termination-Request ::= < PANA-Header: 3, REQ >
                       < Termination-Cause >
                    *  [ AVP ]
                   0*1 < AUTH >

7.5.  PANA-Termination-Answer (PTA)

   The PANA-Termination-Answer (PTA) message is sent either by the PaC
   or the PAA in response to PANA-Termination-Request.

   PANA-Termination-Answer ::= < PANA-Header: 3 >
                    *  [ AVP ]
                   0*1 < AUTH >

7.6.  PANA-Notification-Request (PNR)

   The PANA-Notification-Request (PNR) message is sent either by the PaC
   or the PAA for signaling re-authentication and errors, and performing
   liveness test.



Forsberg, et al.         Expires October 6, 2007               [Page 29]


Internet-Draft                    PANA                        April 2007


   If 'A' or 'P' bit is set, the message MUST NOT carry Result-Code,
   Failed-Message-Header and Failed-AVP AVPs.

   If 'E' bit is set, the message MUST carry one Result-Code AVP and one
   Failed-Message-Header AVP and MAY carry one or more Failed AVPs.

   The message MUST have one of 'A', 'P' and 'E' bits exclusively set.

 PANA-Notification-Request ::= < PANA-Header: 4, REQ[,REA][,PIN][,ERR] >
                     [ Result-Code ]
                     [ Failed-Message-Header ]
                  *  [ Failed-AVP ]
                  *  [ AVP ]
                 0*1 < AUTH >

7.7.  PANA-Notification-Answer (PNA)

   The PANA-Notification-Answer (PNA) message is sent by the PAA (PaC)
   to the PaC (PAA) in response to a PANA-Notification-Request from the
   PaC (PAA).

   The message MUST have one of 'A', 'P' and 'E' bits exclusively set.

  PANA-Notification-Answer ::= < PANA-Header: 4, REQ[,REA][,PIN][,ERR] >
                   *  [ AVP ]
                  0*1 < AUTH >

























Forsberg, et al.         Expires October 6, 2007               [Page 30]


Internet-Draft                    PANA                        April 2007


8.  AVPs in PANA

   This document uses AVP Value Format such as 'OctetString' and
   'Unsigned32' as defined in Section 4.2 of [RFC3588].  The definitions
   of these data formats are not repeated in this document.

   The following table lists the AVPs used in this document, and
   specifies in which PANA messages they MAY, or MAY NOT be present.

   The table uses the following symbols:

   0     The AVP MUST NOT be present in the message.

   0+    Zero or more instances of the AVP MAY be present in the
         message.

   0-1   Zero or one instance of the AVP MAY be present in the message.
         It is considered an error if there are more than one instance
         of the AVP.

   1     One instance of the AVP MUST be present in the message.


                         +---------------------------+
                         |        Message Type       |
                         +---+---+---+---+---+---+---+
   Attribute Name        |PCI|PAR|PAN|PTR|PTA|PNR|PNA|
   ----------------------+---+---+---+---+---+---+---+
   Algorithm             | 0 |0-1| 0 | 0 | 0 | 0 | 0 |
   AUTH                  | 0 |0-1|0-1|0-1|0-1|0-1|0-1|
   EAP-Payload           | 0 |0-1|0-1| 0 | 0 | 0 | 0 |
   Failed-AVP            | 0 | 0 | 0 | 0 | 0 | 0+| 0 |
   Failed-Message-Header | 0 | 0 | 0 | 0 | 0 |0-1| 0 |
   Key-Id                | 0 |0-1|0-1| 0 | 0 | 0 | 0 |
   Nonce                 | 0 |0-1|0-1| 0 | 0 | 0 | 0 |
   Result-Code           | 0 |0-1| 0 | 0 | 0 |0-1| 0 |
   Session-Lifetime      | 0 |0-1| 0 | 0 | 0 | 0 | 0 |
   Termination-Cause     | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
   ----------------------+---+---+---+---+---+---+---+

                      Figure 4: AVP Occurrence Table

8.1.  Algorithm AVP

   The Algorithm AVP (AVP Code 1) is used for conveying the
   pseudo-random function to derive PANA_AUTH_KEY as well as the
   integrity algorithm to compute an AUTH AVP.  The AVP data is of type
   Unsigned32.



Forsberg, et al.         Expires October 6, 2007               [Page 31]


Internet-Draft                    PANA                        April 2007


   The first 16-bit of the AVP data contains an IKEv2 Transform ID of
   Transform Type 2 [RFC4306] corresponding to the key derivation
   function.

   The last 16-bit of the AVP data contains an IKEv2 Transform ID of
   Transform Type 3 [RFC4306] for the integrity algorithm.

   All PANA implementations MUST support PRF_HMAC_SHA1 (2) [RFC2104] for
   the key derivation algorithm and AUTH_HMAC_SHA1_160 (7) [RFC4595]
   corresponding to the integrity algorithm.

8.2.  AUTH AVP

   The AUTH AVP (AVP Code 2) is used to integrity protect PANA messages.
   The AVP data payload contains the Message Authentication Code encoded
   in network byte order.  The AVP length varies depending on the
   integrity algorithm specified in an Algorithm AVP.

8.3.  EAP-Payload AVP

   The EAP-Payload AVP (AVP Code 3) is used for encapsulating the actual
   EAP message that is being exchanged between the EAP peer and the EAP
   authenticator.  The AVP data is of type OctetString.

[a25]8.4.  Failed-AVP AVP

   The Failed-AVP AVP (AVP Code 4) provides debugging information in
   cases where a message is rejected or not fully processed due to
   erroneous information in a specific AVP.  The AVP data is of type
   Grouped.  The format of the Failed-AVP AVP using the ABNF grammar
   defined in [RFC3588] for Grouped AVP is as follows.

           <Failed-AVP> ::= < AVP Header: 4 >
                         1* {AVP}

   In case of a failed grouped AVP, the Failed-AVP contains the whole
   grouped AVP.  In case of a failed AVP inside a grouped AVP, the
   Failed-AVP contains the single offending AVP.

8.5.  Failed-Message-Header AVP

   The Failed-Message-Header AVP (AVP Code 5) provides debugging
   information in cases where a message is rejected or not fully
   processed due to erroneous information in the message header or
   payload.  The AVP data is of type OctetString.  The AVP data contains
   the 16-octet header of the message that caused the error.





Forsberg, et al.         Expires October 6, 2007               [Page 32]


Internet-Draft                    PANA                        April 2007


8.6.  Key-Id AVP

   The Key-Id AVP (AVP Code 6) is of type Integer32, and contains an MSK
   identifier.  The MSK identifier is assigned by PAA and MUST be unique
   within the PANA session.

8.7.  Nonce AVP

   The Nonce AVP (AVP Code 7) carries a randomly chosen value that is
   used in cryptographic key computations.  The recommendations in
   [RFC4086] apply with regard to generation of random values.  The AVP
   data is of type OctetString and it contains a randomly generated
   value in opaque format.  The data length MUST be between 8 and 256
   octets inclusive.

   The length of the nonces are determined based on the available
   pseudo-random functions (PRFs) and the degree of trust placed into
   the two PaC and the PAA to compute random values.  The length of the
   random value for the nonce is determined whether

   1.  The PaC and the PAA each are likely to be able to compute a
       random nonce (according to [RFC4086]).  The length of the nonce
       has to be 1/2 the length of the PRF key [a26](e.g., 10 octets in the
       case of HMAC-SHA1).

   2.  The PaC and the PAA each are not trusted with regard to the
       computation of a random nonce (according to [RFC4086]).  The
       length of the nonce has to have the full length [a27]of the PRF key
       (e.g., 20 octets in the case of HMAC-SHA1).

   Furthermore, the strongest available PRF available for PANA has to be
   considered in this computation.  Currently, only a single PRF (namely
   HMAC-SHA1) is available and therefore the maximum output length is 20
   octets).  The recommended maximum length of the nonce value is
   therefore currently 20 octets.

8.8.  Result-Code AVP

   The Result-Code AVP (AVP Code 8) is of type Unsigned32 and indicates
   whether an EAP authentication was completed successfully or whether
   an error occurred.  Result-Code AVP values are described in the
   subsequent sections.

8.8.1.  Authentication Results Codes

   These result code values inform the PaC about the authentication and
   authorization result.  The authentication result and authorization
   result can be different as described below, but only one result is



Forsberg, et al.         Expires October 6, 2007               [Page 33]


Internet-Draft                    PANA                        April 2007


   returned to the PaC.  These codes are used with PANA-Auth-Request
   message with 'C' bit set.

   PANA_SUCCESS                               0

      Both authentication and authorization processes are successful.

   PANA_AUTHENTICATION_REJECTED               1

      Authentication has failed.  When this error is returned, it is
      assumed that authorization is automatically failed.

   PANA_AUTHORIZATION_REJECTED                [a28]2

      The authorization process has failed.  This error could occur when
      authorization is rejected by a AAA server or rejected locally by a
      PAA, even if the authentication procedure has succeeded.

8.8.2.  Protocol Error Result Codes

   These codes are used with error request messages.  Unless stated
   otherwise, they can be generated by both the PaC and the PAA.

   PANA_MESSAGE_UNSUPPORTED                1001

      Message type not recognized or supported.

   PANA_UNABLE_TO_DELIVER                  1002

      The PAA was unable to deliver the EAP payload to the
      authentication server.  Only the PAA can generate this code.

   PANA_INVALID_HDR_BITS                   1003

      A message was received whose bits in the PANA message header were
      either set to an invalid combination, or to a value that is
      inconsistent with the message type definition.

   PANA_INVALID_AVP_FLAGS                  1004

      A message was received that included an AVP whose flag bits are
      set to an unrecognized value, or that is inconsistent with the
      AVP's definition.

   PANA_AVP_UNSUPPORTED                    1005

      The received message contained an AVP that is not recognized or
      supported and was marked with the Mandatory bit.  A PANA message



Forsberg, et al.         Expires October 6, 2007               [Page 34]


Internet-Draft                    PANA                        April 2007


      with this error MUST contain one or more Failed-AVP AVP containing
      the AVPs that caused the failure.

   PANA_INVALID_AVP_DATA                   1006

      The message contained an AVP with an invalid value in its data
      portion.  A PANA message indicating this error MUST include the
      offending AVPs within a Failed-AVP AVP.

   PANA_MISSING_AVP                        1007

      The message did not contain an AVP that is required by the message
      type definition.  If this value is sent in the Result-Code AVP, a
      Failed-AVP AVP SHOULD be included in the message.  The Failed-AVP
      AVP MUST contain an example of the missing AVP complete with the
      Vendor-Id if applicable.  The value field of the missing AVP
      should be of correct minimum length and contain zeroes.

   PANA_RESOURCES_EXCEEDED                 1008

      A message was received that cannot be authorized because the
      client has already expended allowed resources.  An example of this
      error condition is a client that is restricted to one PANA session
      and attempts to establish a second session.  Only the PAA can
      generate this code.

   PANA_CONTRADICTING_AVPS                 1009

      The PAA has detected AVPs in the message that contradicted each
      other, and is not willing to provide service to the client.  One
      or more Failed-AVP AVPs MUST be present, containing the AVPs that
      contradicted each other.  Only the PAA can generate this code.

   PANA_AVP_NOT_ALLOWED                    1010

      A message was received with an AVP that MUST NOT be present.  The
      Failed-AVP AVP MUST be included and contain a copy of the
      offending AVP.

   PANA_AVP_OCCURS_TOO_MANY_TIMES          1011

      A message was received that included an AVP that appeared more
      often than permitted in the message definition.  The Failed-AVP
      AVP MUST be included and contain a copy of the first instance of
      the offending AVP that exceeded the maximum number of occurrences.






Forsberg, et al.         Expires October 6, 2007               [Page 35]


Internet-Draft                    PANA                        April 2007


   PANA_UNSUPPORTED_VERSION                1012

      This error is returned when a message was received, whose version
      number is unsupported.

   PANA_UNABLE_TO_COMPLY                   1013

      This error is returned when a request is rejected for unspecified
      reasons.

   PANA_INVALID_AVP_LENGTH 1014

      The message contained an AVP with an invalid length.  The error
      request message indicating this error MUST include the offending
      AVPs within a Failed-AVP AVP.

   PANA_INVALID_MESSAGE_LENGTH             1015

      This error is returned when a message is received with an invalid
      message length.

8.9.  Session-Lifetime AVP

   The Session-Lifetime AVP (AVP Code 9) contains the number of seconds
   remaining before the current session is considered expired.  The AVP
   data is of type Unsigned32.

8.10.  Termination-Cause AVP

   The Termination-Cause AVP (AVP Code 10) is used for indicating the
   reason why a session is terminated by the requester.  The AVP data is
   of type Enumerated.  The following Termination-Cause data values are
   used with PANA.

   LOGOUT                   1  (PaC -> PAA)

      The client initiated a disconnect

   ADMINISTRATIVE           4  (PAA -> PaC)

      The client was not granted access, or was disconnected, due to
      administrative reasons.

   SESSION_TIMEOUT          8  (PAA -> PaC)

      The session has timed out, and service has been terminated.





Forsberg, et al.         Expires October 6, 2007               [Page 36]


Internet-Draft                    PANA                        April 2007


9.  Retransmission Timers

   The PANA protocol provides retransmissions for the
   PANA-Client-Initiation message and all request messages.

   PANA retransmission timers are based on the model used in DHCPv6
   [RFC3315].  Variables used here are also borrowed from this
   specification.  PANA is a request/response-based protocol.  The
   message exchange terminates when the requester successfully receives
   the answer, a protected error message for the request is received, or
   the message exchange is considered to have failed according to the
   retransmission mechanism described below.

   The retransmission behavior is controlled and described by the
   following variables:

         RT     Retransmission timeout

         IRT    Initial retransmission time

         MRC    Maximum retransmission count

         MRT    Maximum retransmission time

         MRD    Maximum retransmission duration

         RAND   Randomization factor

   With each message transmission or retransmission, the sender sets RT
   according to the rules given below.  If RT expires before the message
   exchange terminates, the sender recomputes RT and retransmits the
   message.

   Each of the computations of a new RT include a randomization factor
   (RAND), which is a random number chosen with a uniform distribution
   between -0.1 and +0.1.  The randomization factor is included to
   minimize synchronization of messages.

   The algorithm for choosing a random number does not need to be
   cryptographically sound.  The algorithm SHOULD produce a different
   sequence of random numbers from each invocation.

   RT for the first message transmission is based on IRT:

         RT = IRT + RAND*IRT

   RT for each subsequent message transmission is based on the previous
   value of RT:



Forsberg, et al.         Expires October 6, 2007               [Page 37]


Internet-Draft                    PANA                        April 2007


         RT = 2*RTprev + RAND*RTprev

   MRT specifies an upper bound on the value of RT (disregarding the
   randomization added by the use of RAND).  If MRT has a value of 0,
   there is no upper limit on the value of RT.  Otherwise:

         if (RT > MRT)
            RT = MRT + RAND*MRT

   MRC specifies an upper bound on the number of times a sender may
   retransmit a message.  Unless MRC is zero, the message exchange fails
   once the sender has transmitted the message MRC times.

   MRD specifies an upper bound on the length of time a sender may
   retransmit a message.  Unless MRD is zero, the message exchange fails
   once MRD seconds have elapsed since the client first transmitted the
   message.

   If both MRC and MRD are non-zero, the message exchange fails whenever
   either of the conditions specified in the previous two paragraphs are
   met.

   If both MRC and MRD are zero, the client continues to transmit the
   message until it receives a response.

9.1.  Transmission and Retransmission Parameters

   This section presents a table of values used to describe the message
   retransmission behavior of PANA requests that are retransmitted
   (REQ_*) and PANA-Client-Initiation message (PCI_*).  The table shows
   default values.

          Parameter       Default   Description
          ------------------------------------------------
          PCI_IRT           1 sec   Initial PCI timeout.
          PCI_MRT         120 secs  Max PCI timeout value.
          PCI_MRC           0       Max PCI retransmission attempts.
          PCI_MRD           0       Max PCI retransmission duration.

          REQ_IRT           1 sec   Initial Request timeout.
          REQ_MRT          30 secs  Max Request timeout value.
          REQ_MRC          10       Max Request retransmission attempts.
          REQ_MRD           0       Max Request retransmission duration.

   So for example the first RT for the PBR message is calculated using
   REQ_IRT as the IRT:

           RT = REQ_IRT + RAND*REQ_IRT



Forsberg, et al.         Expires October 6, 2007               [Page 38]


Internet-Draft                    PANA                        April 2007


10.  IANA Considerations

   This section provides guidance to the Internet Assigned Numbers
   Authority (IANA) regarding registration of values related to the PANA
   protocol, in accordance with BCP 26 [IANA].  The following policies
   are used here with the meanings defined in BCP 26: "Private Use",
   "First Come First Served", "Expert Review", "Specification Required",
   "IETF Consensus", "Standards Action".

   This section explains the criteria to be used by the IANA for
   assignment of numbers within namespaces defined within this document.

   For registration requests where a Designated Expert should be
   consulted, the responsible IESG area director should appoint the
   Designated Expert.  For Designated Expert with Specification
   Required, the request is posted to the PANA WG mailing list (or, if
   it has been disbanded, a successor designated by the Area Director)
   for comment and review, and MUST include a pointer to a public
   specification.  Before a period of 30 days has passed, the Designated
   Expert will either approve or deny the registration request and
   publish a notice of the decision to the PANA WG mailing list or its
   successor.  A denial notice must be justified by an explanation and,
   in the cases where it is possible, concrete suggestions on how the
   request can be modified so as to become acceptable.

10.1.  PANA UDP Port Number

   PANA uses one well-known UDP port number Section 6.1), which needs to
   be assigned by the IANA.

10.2.  PANA Message Header

   As defined in Section 6.2, the PANA message header contains two
   fields that requires IANA namespace management; the Version, Message
   Type and Flags fields.

10.2.1.  Version

   The Version namespace is used to identify PANA versions.  The Version
   values are assigned by Standards Action [IANA].  This document
   defines the Version 1.

10.2.2.  Message Type

   The Message Type namespace is used to identify PANA messages.  Values
   0-65,519 are for permanent, standard message types, allocated by IETF
   Consensus [IANA].  This document defines the Message Types 1-4.  See
   Section 7.1 through Section 7.7 for the assignment of the namespace



Forsberg, et al.         Expires October 6, 2007               [Page 39]


Internet-Draft                    PANA                        April 2007


   in this specification.

   The values 65,520 and 65,535 (hexadecimal values 0xfff0 - 0xffff) are
   reserved for experimental messages.  As these codes are only for
   experimental and testing purposes, no guarantee is made for
   interoperability between the communicating PaC and PAA using
   experimental commands, as outlined in [IANA-EXP].

10.2.3.  Flags

   There are 16 bits in the Flags field of the PANA message header.
   This document assigns bit 0 ('R'), 1 ('S'), 2 ('C'), 3 ('A'), 4 ('P')
   and 5 ('E').  The remaining bits MUST only be assigned via a
   Standards Action [IANA].

10.3.  AVP Header

   As defined in Section 6.3, the AVP header contains three fields that
   requires IANA namespace management; the AVP Code, AVP Flags and
   Vendor-Id fields where only the AVP Code and AVP Flags create new
   namespaces.

10.3.1.  AVP Code

   The 16-bit AVP Code namespace is used to identify attributes.  There
   are multiple namespaces.  Vendors can have their own AVP Codes
   namespace which will be identified by their Vendor-ID (also known as
   Enterprise-Number) and they control the assignments of their
   vendor-specific AVP codes within their own namespace.  The absence of
   a Vendor-ID identifies the IETF IANA controlled AVP Codes namespace.
   The AVP Codes and sometimes also possible values in an AVP are
   controlled and maintained by IANA.

   AVP Code 0 is not used.  This document defines the AVP Codes 1-10.
   See Section 8.1 through Section 8.10 for the assignment of the
   namespace in this specification.

   AVPs may be allocated following Designated Expert with Specification
   Required [IANA] or Standards Action.  AVPs with 'M' bit set MUST be
   allocated by Standards Action.

   Note that PANA defines a mechanism for Vendor-Specific AVPs, where
   the Vendor-Id field in the AVP header is set to a non-zero value.
   Vendor-Specific AVPs codes are for Private Use and should be
   encouraged instead of allocation of global attribute types, for
   functions specific only to one vendor's implementation of PANA, where
   no interoperability is deemed useful.  Where a Vendor-Specific AVP is
   implemented by more than one vendor, allocation of global AVPs should



Forsberg, et al.         Expires October 6, 2007               [Page 40]


Internet-Draft                    PANA                        April 2007


   be encouraged instead.

10.3.2.  Flags

   There are 16 bits in the AVP Flags field of the AVP header, defined
   in Section 6.3.  This document assigns bit 0 ('V') and bit 1 ('M').
   The remaining bits should only be assigned via a Standards Action .

10.4.  AVP Values

   Certain AVPs in PANA define a list of values with various meanings.
   For attributes other than those specified in this section, adding
   additional values to the list can be done on a First Come, First
   Served basis by IANA [IANA].

10.4.1.  Result-Code AVP Values

   As defined in Section 8.8.1 and Section 8.8.2 the Result-Code AVP
   (AVP Code 8) defines the values 0-3 and 1001-1015.

   All remaining values are available for assignment via IETF Consensus
   [IANA].

10.4.2.  Termination-Cause AVP Values

   As defined in Section 8.10, the Termination-Cause AVP (AVP Code 10)
   defines the values 1, 4 and 8.

   All remaining values are available for assignment via IETF Consensus
   [IANA].





















Forsberg, et al.         Expires October 6, 2007               [Page 41]


Internet-Draft                    PANA                        April 2007


11.  Security Considerations

   The PANA protocol defines a UDP-based EAP encapsulation that runs
   between two IP-enabled nodes.  Various security threats that are
   relevant to a protocol of this nature are outlined in [RFC4016].
   Security considerations stemming from the use of EAP and EAP methods
   are discussed in [RFC3748] [I-D.ietf-eap-keying].  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 cryptographically-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).

11.1.  General Security Measures

   PANA provides multiple mechanisms to secure a PANA session.

   PANA messages carry sequence numbers, which are monotonically
   incremented by 1 with every new request message.  These numbers are
   randomly initialized at the beginning of the session, and verified
   against expected numbers upon receipt.  A message whose sequence
   number is different than the expected one is silently discarded.  In
   addition to accomplishing orderly delivery of EAP messages and
   duplicate elimination, this scheme also helps prevent an adversary
   spoofing messages to disturb ongoing PANA and EAP sessions unless it
   can also eavesdrop to synchronize on the expected sequence number.
   Furthermore, impact of replay attacks is reduced as any stale message
   (i.e., a request or answer with an unexpected sequence number and/or
   a session identifier for a non-existing session) and any duplicate
   answer are immediately discarded, and a duplicate request can trigger
   transmission of the cached answer (i.e., no need to process the
   request and generate a new answer).

   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 Internet/intranet.  A set of filters can be used to
   discard unauthorized packets, such as the initial PANA-Auth-Request
   message that is received from the segment of the access network where
   only the PaCs are supposed to be connected (i.e., preventing PAA



Forsberg, et al.         Expires October 6, 2007               [Page 42]


Internet-Draft                    PANA                        April 2007


   impersonation).

   The protocol also provides authentication and integrity protection to
   PANA messages when the used EAP method can generate cryptographic
   session keys.  A PANA SA is generated based on the MSK exported by
   the EAP method.  This SA is used for generating an AUTH AVP to
   protect the PANA message 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 AUTH verification is silently discarded.  The
   earliest this protection can be enabled is when the PANA-Auth-Request
   message that signals a successful authentication (EAP Success) is
   generated.  Starting with these messages, any subsequent PANA message
   until the session gets torn down can be cryptographically protected.

   The lifetime of the PANA SA is set to PANA session lifetime which is
   bounded by the authorization lifetime granted by the authentication
   server.  An implementation MAY add a grace period to that value.
   Unless the PANA session is extended by executing another EAP
   authentication, the 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.  Insecure lower-layers necessitate use of key-generating
   EAP methods.  In networks where lower-layers are already secured,
   cryptographic protection of PANA messages is not necessary.

11.2.  Initial Exchange

   The initial PANA-Auth-Request and PANA-Auth-Answer exchange is
   vulnerable to spoofing attacks as these messages are not
   authenticated and integrity protected.  In order to prevent very
   basic DoS attacks an adversary should not be able to cause state
   creation by sending PANA-Client-Initiation messages to the PAA.  This
   protection is achieved by allowing the responder (PAA) to create as
   little amount of state as possible in the initial message exchange.
   However, it is difficult to prevent all spoofing attacks in the
   initial message exchange entirely.

   In networks where lower-layers are not secured prior to running PANA,
   the capability discovery enabled through inclusion of an Algorithm
   AVP in the initial PANA-Auth-Request message is susceptible to
   spoofing leading to DoS attacks.  Therefore, usage of this AVP during
   the initial message exchange in such insecure networks is NOT



Forsberg, et al.         Expires October 6, 2007               [Page 43]


Internet-Draft                    PANA                        April 2007


   RECOMMENDED.  The same AVP is delivered with integrity protection via
   the last PANA-Auth-Request message upon successful authentication.

11.3.  EAP Methods

   Eavesdropping EAP messages 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 Response/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 method 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.

11.4.  Cryptographic Keys

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

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

   The PANA SA lifetime is bounded by the MSK lifetime.  Another
   execution of EAP method yields in a new MSK, and updates the PANA SA,
   PANA_AUTH_KEY and key ID.

11.5.  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 SA establishment.  The PANA framework allows
   generation of cryptographic keys from the PANA SA and use the keys
   with a secure association protocol to enable per-packet cryptographic
   protection such as link-layer or IPsec-based ciphering
   [I-D.ietf-pana-ipsec].  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.  How cryptographic keys are
   generated from the PANA SA and used with a secure association



Forsberg, et al.         Expires October 6, 2007               [Page 44]


Internet-Draft                    PANA                        April 2007


   protocol is outside the scope of this document.

11.6.  PAA-to-EP Communication

   The PANA framework allows separation of PAA from EP.  SNMPv3
   [I-D.ietf-pana-snmp] MAY be used between 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.

11.7.  Liveness 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 session 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,
   expecting the peer to 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 the discontinuation of data
   traffic for an extended period of time).  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 a PANA SA is
   available in order to prevent threats associated with the abuse of
   this functionality.

   Any valid PANA answer message received in response to a recently sent
   request message can be taken as an indication of peer's liveness.
   The PaC or PAA MAY forgo sending an explicit ping request message if
   a recent exchange has already confirmed that the peer is alive.

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







Forsberg, et al.         Expires October 6, 2007               [Page 45]


Internet-Draft                    PANA                        April 2007


12.  Acknowledgments

   We would like to thank Mark Townsley, Jari Arkko, Mohan
   Parthasarathy, Julien Bournelle, Rafael Marin Lopez, Pasi Eronen,
   Randy Turner, Erik Nordmark, Lionel Morand, Avi Lior, Susan Thomson,
   Giaretta Gerardo, Joseph Salowey, Sasikanth Bharadwaj, Spencer
   Dawkins, Tom Yu, Bernard Aboba and all members of the PANA working
   group for their valuable comments to this document.











































Forsberg, et al.         Expires October 6, 2007               [Page 46]


Internet-Draft                    PANA                        April 2007


13.  References

13.1.  Normative References

   [RFC2104]  Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed-
              Hashing for Message Authentication", RFC 2104,
              February 1997.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2234]  Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
              Specifications: ABNF", RFC 2234, November 1997.

   [RFC3588]  Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
              Arkko, "Diameter Base Protocol", RFC 3588, September 2003.

   [RFC3748]  Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H.
              Levkowetz, "Extensible Authentication Protocol (EAP)",
              RFC 3748, June 2004.

   [RFC4086]  Eastlake, D., Schiller, J., and S. Crocker, "Randomness
              Requirements for Security", BCP 106, RFC 4086, June 2005.

   [RFC4595]  Maino, F. and D. Black, "Use of IKEv2 in the Fibre Channel
              Security Association Management Protocol", RFC 4595,
              July 2006.

   [I-D.ietf-dhc-paa-option]
              Morand, L., "DHCP options for PANA Authentication Agents",
              draft-ietf-dhc-paa-option-05 (work in progress),
              December 2006.

   [IANA]     Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs",  BCP 26, RFC 2434,
              October 1998.

13.2.  Informative References

   [RFC3315]  Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
              and M. Carney, "Dynamic Host Configuration Protocol for
              IPv6 (DHCPv6)", RFC 3315, July 2003.

   [RFC4016]  Parthasarathy, M., "Protocol for Carrying Authentication
              and Network Access (PANA) Threat Analysis and Security
              Requirements", RFC 4016, March 2005.

   [RFC4058]  Yegin, A., Ohba, Y., Penno, R., Tsirtsis, G., and C. Wang,



Forsberg, et al.         Expires October 6, 2007               [Page 47]


Internet-Draft                    PANA                        April 2007


              "Protocol for Carrying Authentication for Network Access
              (PANA) Requirements", RFC 4058, May 2005.

   [RFC4137]  Vollbrecht, J., Eronen, P., Petroni, N., and Y. Ohba,
              "State Machines for Extensible Authentication Protocol
              (EAP) Peer and Authenticator", RFC 4137, August 2005.

   [RFC4306]  Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",
              RFC 4306, December 2005.

   [I-D.ietf-eap-keying]
              Aboba, B., "Extensible Authentication Protocol (EAP) Key
              Management Framework", draft-ietf-eap-keying-18 (work in
              progress), February 2007.

   [I-D.ietf-pana-ipsec]
              Parthasarathy, M., "PANA Enabling IPsec based Access
              Control", draft-ietf-pana-ipsec-07 (work in progress),
              July 2005.

   [I-D.ietf-pana-framework]
              Jayaraman, P., "Protocol for Carrying Authentication for
              Network Access (PANA) Framework",
              draft-ietf-pana-framework-07 (work in progress),
              August 2006.

   [I-D.ietf-pana-snmp]
              Mghazli, Y., "SNMP usage for PAA-EP interface",
              draft-ietf-pana-snmp-06 (work in progress), June 2006.

   [ianaweb]  IANA, "Number assignment",  http://www.iana.org.

   [IANA-EXP]
              Narten, T., "Assigning Experimental and Testing Numbers
              Considered Useful",  BCP 82, RFC 3692, January 2004.
















Forsberg, et al.         Expires October 6, 2007               [Page 48]


Internet-Draft                    PANA                        April 2007


Authors' Addresses

   Dan Forsberg
   Nokia Research Center
   P.O. Box 407
   FIN-00045 NOKIA GROUP
   Finland

   Phone: +358 50 4839470
   Email: dan.forsberg@nokia.com


   Yoshihiro Ohba
   Toshiba America Research, Inc.
   1 Telcordia Drive
   Piscataway, NJ  08854
   USA

   Phone: +1 732 699 5305
   Email: yohba@tari.toshiba.com


   Basavaraj Patil
   Nokia
   6000 Connection Dr.
   Irving, TX  75039
   USA

   Phone: +1 972-894-6709
   Email: Basavaraj.Patil@nokia.com


   Hannes Tschofenig
   Siemens Corporate Technology
   Otto-Hahn-Ring 6
   81739 Munich
   Germany

   Email: Hannes.Tschofenig@siemens.com












Forsberg, et al.         Expires October 6, 2007               [Page 49]


Internet-Draft                    PANA                        April 2007


   Alper E. Yegin
   Samsung Advanced Institute of Technology
   Istanbul,
   Turkey

   Phone: +90 538 719 0181
   Email: alper01.yegin@partner.samsung.com












































Forsberg, et al.         Expires October 6, 2007               [Page 50]


Internet-Draft                    PANA                        April 2007


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).





Forsberg, et al.         Expires October 6, 2007               [Page 51]


[a1]Extended may be a better term here.
[a2]May like to delete this part
[a3]Is it specified in a separate document. If so, pl. provide the reference, otherwise delete this sentence.
[a4]Other places ?access device? is used.  A consistent terminology  would be better. 
[a5]Is this correct?  Are DHCP, ND, ARP not IP data traffic? 
[a6]Is it authentication or re-authentication?
[a7]May consider revising this part. 
[a8]other places ?answer? is used .. terminology problem..
[a9]May consider revising the sentence.
[a10]Not  clear  in particular, the last part of the sentence.
[a11]Is this piggybacked EAP?  It is not clear why EAP is not inlcuded in PANA-Auth_Answer (y).  Some texts explaning the piggybaked EAP will be helpful 
Is it really a PANA Session?  This is happening during authentication and authorization phase which is a  part of a PANA session. Also the definition of PANA should include authorization as a cause to session termination.  [a12]
[a13]Is this true?  Accordig to eralier definition or re-authenticatrion, it happens during access phase. 
[a14]Not clear. May consider revising the senetence.
[a15]Is it deleted or "terminated"?
[a16]Some places it says   bit is not set and other places it is cleared. Consistency would be good.  
[a17]How will  PAA  know that PaC has not received it?  Will PaC  retransmit PANA-Notification-Request?
[a18]Not clear. May cosnider revising it. 
[a19]Should be 'answer'
[a20]Is it deleted or terminated ?
[a21]This seems incorrect since  it is expected that re-authentication request will apprear during re-authntication phase.
[a22]Same as before.
[a23]Same as before since PANA-Auth-Request may appear during re-authentication phase. 
[a24]What happens if PaC chooses a source port number  that is used by PAA?
[a25]This AVP describes the vaule format while few others do  not.  
[a26]Is it a MUST or SHOULD?  
[a27]Same a s before. 
[a28]How about Authentication-Success  but Authorization_Failed?  Is it useful? 

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

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

--------------050909040805000300050703--




From pana-bounces@ietf.org Fri Apr 20 19:37:46 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hf2fh-0003lT-VE; Fri, 20 Apr 2007 19:37:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hf2fg-0003lM-Gb
	for pana@ietf.org; Fri, 20 Apr 2007 19:37:44 -0400
Received: from imx12.toshiba.co.jp ([61.202.160.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hf2ff-000746-Lj
	for pana@ietf.org; Fri, 20 Apr 2007 19:37:44 -0400
Received: from wall11.toshiba.co.jp (wall11 [133.199.90.149])
	by imx12.toshiba.co.jp  with ESMTP id l3KNbe9g013995;
	Sat, 21 Apr 2007 08:37:40 +0900 (JST)
Received: (from root@localhost) by wall11.toshiba.co.jp  id l3KNbeCC007819;
	Sat, 21 Apr 2007 08:37:40 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] 
	by wall11.toshiba.co.jp with ESMTP id JAA07818;
	Sat, 21 Apr 2007 08:37:39 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp11.toshiba.co.jp  with ESMTP id l3KNbdKc029154;
	Sat, 21 Apr 2007 08:37:39 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3KNbdqt004134;
	Sat, 21 Apr 2007 08:37:39 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGT006F2LMODJH0@mail.po.toshiba.co.jp>; Sat,
	21 Apr 2007 08:37:38 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hf2fY-0007e5-NA; Fri,
	20 Apr 2007 16:37:36 -0700
Date: Fri, 20 Apr 2007 19:37:36 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Ping and pending request
In-reply-to: <46278FB7.5090808@tari.toshiba.com>
To: Victor Fajardo <vfajardo@tari.toshiba.com>
Message-id: <20070420233736.GE25611@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <46278FB7.5090808@tari.toshiba.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: townsley@cisco.com, "pana@ietf.org" <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>
Errors-To: pana-bounces@ietf.org

Victor,

You've raised an interesting issue (CC: Mark).  Please see my comment
below.

On Thu, Apr 19, 2007 at 11:50:15AM -0400, Victor Fajardo wrote:
> Hi,
> 
> A few more issues we can check:
> 
> a. In Sec 5.5, the following text:
> 
> "
> + The last PANA-Auth-Request as well as ping request before
>  completion of the initial PANA-Auth-Request and
>  PANA-Auth-Answer exchange.
> "
> 
> should be replace with:
> 
> "
> + The last PANA-Auth-Request before completion of the initial
>  PANA-Auth-Request and PANA-Auth-Answer exchange.
> 
> + Ping request.
> "
> 
> Reasons: We should not allow ping during authentication and 
> authorization phase and re-authentication phase since it will allow for 
> multiple outstanding requests to be sent (ping and auth request) which 
> tends to complicate state transitions. Also, we don't need liveness test 
> during these phases anyway since we already rely on session lifetime to 
> detect failed sessions.

There is one problem with allowing ping in access phase only.

Suppose both a PaC and a PAA are in access phase, and the PaC sends a
ping request while the PAA sends a PAR to start re-authentication at
the same time.  Then PAA will not accept the ping request because it
has entered re-authentication phase.  If ping is allowed in any
state, then PAA can answer to the ping request.

BTW, I've found another issue here.  In the above example, The PaC
will accept the PAR sent from the PAA and can return a PAN, but it
cannot send a new PAR (this can happen if the PAN does not carry EAP),
until the ping request is answered.  This is actually breaking
lock-step behavior of PANA (queuing requests should not be required
for a lock-step protocol).

If the ping message is handled independently of other messages, then
this kind of corner case will not exist.

I now remember Mark's suggestion to have a separate sequence number
space for pana ping and handle pana ping independently of other pana
messages.  I am now pretty motivated for it :)

> 
> b. In Sec 5.5:
> 
> "
>      *  In the access phase:
> 
>         +  PANA-Auth-Request.
> "
> 
> Just for clarity, maybe it should be "+  PANA-Auth-Request with any of its 
> bit flag set".

I think the current text is sufficient.

BTW, at least 'R' bit is set for PAR :)

> 
> c. Optional text we want to consider for the same complexity reason as (a) 
> above.
> 
> -- Sec 4.2.; First paragraph; Add a sentence: "The ping request MUST be 
> sent only when there are no other pending un-answered request".
> -- Same with sec 4.3 and 4.4 with regards to re-auth and termination 
> request. Not sure how to phrase it though. Maybe "A PANA session MUST not 
> enter the
>   [re-auth|termination] phase while there are pending un-answered request" 
>   (??).

I think this is already covered in the following sentence in Section 5.2:

"A peer can only have one outstanding request at a time."

I found another issue on Section 5.5:

PTR should be accepted in authentication and authorization phase and
the re-authentication phase as well, otherwise, it will create a race
condition similar to the problem of ping request and PAR for re-auth
crossing each other.

Regards,
Yoshihiro Ohba

> 
> regards,
> victor
> 
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________
> 

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



From pana-bounces@ietf.org Fri Apr 20 20:06:46 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hf37g-0005er-Q7; Fri, 20 Apr 2007 20:06:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hf37f-0005em-SG
	for pana@ietf.org; Fri, 20 Apr 2007 20:06:40 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hf37e-0007W7-8Q
	for pana@ietf.org; Fri, 20 Apr 2007 20:06:39 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3L06ZrX018720
	for <pana@ietf.org>; Sat, 21 Apr 2007 09:06:35 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3L06ZjO002997;
	Sat, 21 Apr 2007 09:06:35 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id KAA02996;
	Sat, 21 Apr 2007 09:06:35 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3L06Zxa022392;
	Sat, 21 Apr 2007 09:06:35 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3L06YUb023531;
	Sat, 21 Apr 2007 09:06:34 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGT006PMMYWDEG0@mail.po.toshiba.co.jp>; Sat,
	21 Apr 2007 09:06:34 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hf37Y-0007jp-Ik; Fri,
	20 Apr 2007 17:06:32 -0700
Date: Fri, 20 Apr 2007 20:06:32 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20070421000632.GA29582@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [Pana] Nits on processing invalid message
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>
Errors-To: pana-bounces@ietf.org

In Section 5.4:

"
   Invalid messages MUST be discarded in order to provide robustness
   against DoS attacks.  In addition, an error request message MAY be
   returned to the sender.  See Section 5.8 for details.
"

If an error request is returned in response to an erroneous message,
then this means that the sender of the error request message will
terminate the session after receiving the error answer.  This actually
does not provide robustness against DoS attacks because an attacker
can send an erroneous answer to terminate the session.  So the text
should say:

"
   Invalid messages MUST be discarded either silently in order to
   provide robustness against DoS attacks or with returning 
   an error request message to the sender.  See Section 5.8
   for details.
"

Yoshihiro Ohba

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



From pana-bounces@ietf.org Sun Apr 22 20:21:55 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HfmJU-0007d2-D8; Sun, 22 Apr 2007 20:21:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HfmJT-0007cw-Gc
	for pana@ietf.org; Sun, 22 Apr 2007 20:21:51 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HfmJR-0007Eu-4F
	for pana@ietf.org; Sun, 22 Apr 2007 20:21:51 -0400
Received: from [127.0.0.1] (mgw.toshibaamericaresearch.com [165.254.55.12])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3N0LHRI020782; Sun, 22 Apr 2007 20:21:17 -0400 (EDT)
	(envelope-from vfajardo@tari.toshiba.com)
Message-ID: <462BFBFD.7060600@tari.toshiba.com>
Date: Sun, 22 Apr 2007 20:21:17 -0400
From: Victor Fajardo <vfajardo@tari.toshiba.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Ping and pending request
References: <46278FB7.5090808@tari.toshiba.com>
	<20070420233736.GE25611@steelhead>
In-Reply-To: <20070420233736.GE25611@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.4 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: townsley@cisco.com, "pana@ietf.org" <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>
Errors-To: pana-bounces@ietf.org

Hi,

> There is one problem with allowing ping in access phase only.
>
> Suppose both a PaC and a PAA are in access phase, and the PaC sends a
> ping request while the PAA sends a PAR to start re-authentication at
> the same time.  Then PAA will not accept the ping request because it
> has entered re-authentication phase.  If ping is allowed in any
> state, then PAA can answer to the ping request.
>
> BTW, I've found another issue here.  In the above example, The PaC
> will accept the PAR sent from the PAA and can return a PAN, but it
> cannot send a new PAR (this can happen if the PAN does not carry EAP),
> until the ping request is answered.  This is actually breaking
> lock-step behavior of PANA (queuing requests should not be required
> for a lock-step protocol).
>
> If the ping message is handled independently of other messages, then
> this kind of corner case will not exist.
>
> I now remember Mark's suggestion to have a separate sequence number
> space for pana ping and handle pana ping independently of other pana
> messages.  I am now pretty motivated for it :)
>   

I agree. So I guess "independent" would mean that ping processing could
be exchange at anytime after the initial PAR/PAA and maybe in parallel
with other exchanges.


>   
>> b. In Sec 5.5:
>>
>> "
>>      *  In the access phase:
>>
>>         +  PANA-Auth-Request.
>> "
>>
>> Just for clarity, maybe it should be "+  PANA-Auth-Request with any of its 
>> bit flag set".
>>     
>
> I think the current text is sufficient.
>
> BTW, at least 'R' bit is set for PAR :)
>   

Yes your right :)

>   
>> c. Optional text we want to consider for the same complexity reason as (a) 
>> above.
>>
>> -- Sec 4.2.; First paragraph; Add a sentence: "The ping request MUST be 
>> sent only when there are no other pending un-answered request".
>> -- Same with sec 4.3 and 4.4 with regards to re-auth and termination 
>> request. Not sure how to phrase it though. Maybe "A PANA session MUST not 
>> enter the
>>   [re-auth|termination] phase while there are pending un-answered request" 
>>   (??).
>>     
>
> I think this is already covered in the following sentence in Section 5.2:
>
> "A peer can only have one outstanding request at a time."
>   

Ah ok.



regards,
victor


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



From pana-bounces@ietf.org Mon Apr 23 09:04:09 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HfyDA-0002L8-On; Mon, 23 Apr 2007 09:04:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HfyD9-0002Kx-JQ
	for pana@ietf.org; Mon, 23 Apr 2007 09:04:07 -0400
Received: from mout.perfora.net ([74.208.4.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HfyD8-00050n-19
	for pana@ietf.org; Mon, 23 Apr 2007 09:04:07 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1HfyD11y7X-0008TK; Mon, 23 Apr 2007 09:04:05 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
	"'Victor Fajardo'" <vfajardo@tari.toshiba.com>
Subject: RE: [Pana] Ping and pending request
Date: Mon, 23 Apr 2007 16:03:56 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceDpOYABwqhZ25OSguj2e/gmzw2ZQCAjiQA
In-Reply-To: <20070420233736.GE25611@steelhead>
Message-ID: <0MKp2t-1HfyD11y7X-0008TK@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX19VzOYmVgp3lBcYLDaG74ld9H6ozzIqBhT3GRD
	BNxCcwRdngj7zblhg/Q2tSI2CE0WDBDWQuFaQOHiyIGer8g4aE
	5Zx2//GGn3eU+U1XL3gyQ==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

> There is one problem with allowing ping in access phase only.
> 
> Suppose both a PaC and a PAA are in access phase, and the PaC sends a
> ping request while the PAA sends a PAR to start re-authentication at
> the same time.  Then PAA will not accept the ping request because it
> has entered re-authentication phase.  If ping is allowed in any
> state, then PAA can answer to the ping request.

I think the issue is about having two outstanding requests (one PANA-Ping
and one other) at the same time. The PAA (or PaC) having to respond to a
PANA-Ping-Request while it has an outstanding request shall not have a
problem. What do you think?


> BTW, I've found another issue here.  In the above example, The PaC
> will accept the PAR sent from the PAA and can return a PAN, but it
> cannot send a new PAR (this can happen if the PAN does not carry EAP),
> until the ping request is answered.  This is actually breaking
> lock-step behavior of PANA (queuing requests should not be required
> for a lock-step protocol).

What would be the issue of having request queuing?  


I'd like to see if we can avoid creating special case for PANA-Ping messages
(e.g., putting them under a separate treatment).

Alper



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



From pana-bounces@ietf.org Mon Apr 23 09:16:50 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HfyPP-0006lZ-OK; Mon, 23 Apr 2007 09:16:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HfyPO-0006lU-Jk
	for pana@ietf.org; Mon, 23 Apr 2007 09:16:46 -0400
Received: from mout.perfora.net ([74.208.4.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HfyPM-0000Nj-Ad
	for pana@ietf.org; Mon, 23 Apr 2007 09:16:46 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1HfyPF0sOO-0008S9; Mon, 23 Apr 2007 09:16:41 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
	"'MORAND Lionel RD-CORE-ISS'" <lionel.morand@orange-ftgroup.com>
Subject: RE: [Pana] PAA initiating Re-authentication
Date: Mon, 23 Apr 2007 16:16:34 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceCggvgjvleL6AHTKi2+aj9wOgMowDJlAIQ
In-Reply-To: <20070419125517.GD13717@steelhead>
Message-ID: <0MKp2t-1HfyPF0sOO-0008S9@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX18a/GN/++U77jTyIZbzTlKthv4pjg33DXjfbjC
	bDTQe7g8iVjlGUV2gUr1gi6/EWh98+yDEdEVBGAyz184/rTk3m
	GEPUCsyQm1BrB463At76Q==
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
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>
Errors-To: pana-bounces@ietf.org

>From proposed text for Section 5.7:

>    The lifetime is a non-negotiable parameter that can be used by the
>    PaC to manage PANA-related state.  The PaC does not have to perform
>    any actions when the lifetime expires, other than purging local
>    state.  The PAA MAY, and the PaC SHOULD, initiate the
>    re-authentication phase before the current session lifetime expires
>    if they want to update the session lifetime.

I think we want to say:


	The lifetime is a non-negotiable parameter that can be used by the
	PaC to manage PANA-related state. PaC MUST initiate the re-
	authentication phase before the current session lifetime expires if
it 
	wants to extend the session.

I think it is OK to be silent about the PAA actions as we don't specify what
it should or should not be doing.

Alper








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



From pana-bounces@ietf.org Mon Apr 23 09:20:35 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HfyT2-0007iH-KY; Mon, 23 Apr 2007 09:20:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HfyT1-0007i7-CE
	for pana@ietf.org; Mon, 23 Apr 2007 09:20:31 -0400
Received: from mout.perfora.net ([74.208.4.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HfySy-0001oq-1W
	for pana@ietf.org; Mon, 23 Apr 2007 09:20:31 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1HfySu3mLI-0008Rq; Mon, 23 Apr 2007 09:20:27 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
	<pana@ietf.org>
Subject: RE: [Pana] Nits on processing invalid message
Date: Mon, 23 Apr 2007 16:20:21 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceDqPMfLUKnI3HCTAi8ZhJkCz7cGgCAOmLw
In-Reply-To: <20070421000632.GA29582@steelhead>
Message-ID: <0MKp2t-1HfySu3mLI-0008Rq@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX19x2jNLYqYKHF0A4BB9QrLvMOnJjJiZN4c7pv/
	ikrf7EKnBJPCxO3NUnPx51Y8zKcQ6cnAIeqPd7ygsK2dS112nC
	mT4W7uP8NZQbxYI0+c5HQ==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 
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>
Errors-To: pana-bounces@ietf.org

 
> If an error request is returned in response to an erroneous message,
> then this means that the sender of the error request message will
> terminate the session after receiving the error answer.  This actually
> does not provide robustness against DoS attacks because an attacker
> can send an erroneous answer to terminate the session.  So the text
> should say:
> 
> "
>    Invalid messages MUST be discarded either silently in order to
>    provide robustness against DoS attacks or with returning
>    an error request message to the sender.  See Section 5.8
>    for details.
> "

I think this is effectively the same statement as the original one. If we
want to maintain the DoS resiliency, we shall just go with "Invalid messages
MUST be discarded in order to provide robustness against DoS attacks."

Alper



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



From pana-bounces@ietf.org Mon Apr 23 10:31:37 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HfzZp-00024h-2A; Mon, 23 Apr 2007 10:31:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HfzZl-00024R-7y
	for pana@ietf.org; Mon, 23 Apr 2007 10:31:33 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HfzZj-0000DR-Uk
	for pana@ietf.org; Mon, 23 Apr 2007 10:31:33 -0400
Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3NEUund023492; Mon, 23 Apr 2007 10:30:56 -0400 (EDT)
	(envelope-from vfajardo@tari.toshiba.com)
Message-ID: <462CC329.7050408@tari.toshiba.com>
Date: Mon, 23 Apr 2007 10:31:05 -0400
From: Victor Fajardo <vfajardo@tari.toshiba.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
Subject: Re: [Pana] Ping and pending request
References: <0MKp2t-1HfyD11y7X-0008TK@mrelay.perfora.net>
In-Reply-To: <0MKp2t-1HfyD11y7X-0008TK@mrelay.perfora.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

Hi Alper,

>> Suppose both a PaC and a PAA are in access phase, and the PaC sends a
>> ping request while the PAA sends a PAR to start re-authentication at
>> the same time.  Then PAA will not accept the ping request because it
>> has entered re-authentication phase.  If ping is allowed in any
>> state, then PAA can answer to the ping request.
>>     
>
> I think the issue is about having two outstanding requests (one PANA-Ping
> and one other) at the same time. The PAA (or PaC) having to respond to a
> PANA-Ping-Request while it has an outstanding request shall not have a
> problem. What do you think?
>   

I think in this scenario we may already be treating PANA-Ping in a 
special way already since we are not
strictly lock-stepping anymore; i.e., ping processing seems independent 
and in parallel of other exchanges.

regards,
victor


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



From pana-bounces@ietf.org Mon Apr 23 11:54:51 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg0sN-0006C7-5G; Mon, 23 Apr 2007 11:54:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg0sM-0006C2-7m
	for pana@ietf.org; Mon, 23 Apr 2007 11:54:50 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg0sL-0003tG-IK
	for pana@ietf.org; Mon, 23 Apr 2007 11:54:50 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3NFsjph015063;
	Tue, 24 Apr 2007 00:54:45 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3NFsjna028374;
	Tue, 24 Apr 2007 00:54:45 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id AAA28373;
	Tue, 24 Apr 2007 00:54:45 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3NFsjoN024954;
	Tue, 24 Apr 2007 00:54:45 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3NFsi8s010915;
	Tue, 24 Apr 2007 00:54:44 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGY00162K70OE00@mail.po.toshiba.co.jp>; Tue,
	24 Apr 2007 00:54:44 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hg0s8-0001CB-VV; Mon,
	23 Apr 2007 08:54:36 -0700
Date: Mon, 23 Apr 2007 11:54:36 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Ping and pending request
In-reply-to: <0MKp2t-1HfyD11y7X-0008TK@mrelay.perfora.net>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <20070423155436.GB3668@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <20070420233736.GE25611@steelhead>
	<0MKp2t-1HfyD11y7X-0008TK@mrelay.perfora.net>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

On Mon, Apr 23, 2007 at 04:03:56PM +0300, Alper Yegin wrote:
> > There is one problem with allowing ping in access phase only.
> > 
> > Suppose both a PaC and a PAA are in access phase, and the PaC sends a
> > ping request while the PAA sends a PAR to start re-authentication at
> > the same time.  Then PAA will not accept the ping request because it
> > has entered re-authentication phase.  If ping is allowed in any
> > state, then PAA can answer to the ping request.
> 
> I think the issue is about having two outstanding requests (one PANA-Ping
> and one other) at the same time. The PAA (or PaC) having to respond to a
> PANA-Ping-Request while it has an outstanding request shall not have a
> problem. What do you think?

I think having two outstanding requests sent in different directions
is acceptable.

> 
> 
> > BTW, I've found another issue here.  In the above example, The PaC
> > will accept the PAR sent from the PAA and can return a PAN, but it
> > cannot send a new PAR (this can happen if the PAN does not carry EAP),
> > until the ping request is answered.  This is actually breaking
> > lock-step behavior of PANA (queuing requests should not be required
> > for a lock-step protocol).
> 
> What would be the issue of having request queuing?  

Queueing itself may not be an issue.  But the actual issues is the
sender would need to distinguish two cases (i.e., if there is an
outstanding ping request or not) for each state.

For example, supposed that the PaC is in a state waiting for a ping
answer.  If another event that needs to send a PAR is generated, then
the PaC processes the event, generates and queues a PAR and transits
to a state that is waiting for a PAN, and it is still waiting for a
ping answer.  This would require N*2 states (N is number of states
except for ping, multiplied by 2 to consider whether there is a ping
request or not.

> 
> 
> I'd like to see if we can avoid creating special case for PANA-Ping messages
> (e.g., putting them under a separate treatment).

I think the only way to avoid it is:

- Allow sending ping request in access phase only.

- Allow receiving ping request in any phase.

- When there is an outstanding ping request, discard all incoming
messages except for ping answer or error request sent in resopnse to
the ping request.

This may be an acceptable operation.

Yoshihiro Ohba


> 
> Alper
> 
> 
> 

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



From pana-bounces@ietf.org Mon Apr 23 12:59:40 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg1t5-00049s-KI; Mon, 23 Apr 2007 12:59:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg1t4-00049h-0P
	for pana@ietf.org; Mon, 23 Apr 2007 12:59:38 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg1t2-0000ie-BM
	for pana@ietf.org; Mon, 23 Apr 2007 12:59:37 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3NGxXrM020946;
	Tue, 24 Apr 2007 01:59:33 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3NGxYwj009228;
	Tue, 24 Apr 2007 01:59:34 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id BAA09227;
	Tue, 24 Apr 2007 01:59:33 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3NGxX9g024267;
	Tue, 24 Apr 2007 01:59:33 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3NGxXZF014877;
	Tue, 24 Apr 2007 01:59:33 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGY001BXN6WOG00@mail.po.toshiba.co.jp>; Tue,
	24 Apr 2007 01:59:33 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hg1sm-0001Nj-17; Mon,
	23 Apr 2007 09:59:20 -0700
Date: Mon, 23 Apr 2007 12:59:19 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Nits on processing invalid message
In-reply-to: <0MKp2t-1HfySu3mLI-0008Rq@mrelay.perfora.net>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <20070423165919.GC3668@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <20070421000632.GA29582@steelhead>
	<0MKp2t-1HfySu3mLI-0008Rq@mrelay.perfora.net>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
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>
Errors-To: pana-bounces@ietf.org

On Mon, Apr 23, 2007 at 04:20:21PM +0300, Alper Yegin wrote:
>  
> > If an error request is returned in response to an erroneous message,
> > then this means that the sender of the error request message will
> > terminate the session after receiving the error answer.  This actually
> > does not provide robustness against DoS attacks because an attacker
> > can send an erroneous answer to terminate the session.  So the text
> > should say:
> > 
> > "
> >    Invalid messages MUST be discarded either silently in order to
> >    provide robustness against DoS attacks or with returning
> >    an error request message to the sender.  See Section 5.8
> >    for details.
> > "
> 
> I think this is effectively the same statement as the original one. If we
> want to maintain the DoS resiliency, we shall just go with "Invalid messages
> MUST be discarded in order to provide robustness against DoS attacks."

Does this mean that most protocol error result codes defined in
Section 8.8.2 are not needed, except for the folloiwng ones?

   PANA_UNABLE_TO_DELIVER                  1002
   PANA_RESOURCES_EXCEEDED                 1008
   PANA_UNABLE_TO_COMPLY                   1013

Yoshihiro Ohba


> 
> Alper
> 
> 
> 

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



From pana-bounces@ietf.org Mon Apr 23 15:22:30 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg47K-0005na-H9; Mon, 23 Apr 2007 15:22:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg47J-0005nA-91
	for pana@ietf.org; Mon, 23 Apr 2007 15:22:29 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg47H-00059O-UU
	for pana@ietf.org; Mon, 23 Apr 2007 15:22:29 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1Hg47A3yZA-0000Cb; Mon, 23 Apr 2007 15:22:26 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Victor Fajardo'" <vfajardo@tari.toshiba.com>
Subject: RE: [Pana] Ping and pending request
Date: Mon, 23 Apr 2007 22:22:17 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceFtBcCCXwa+g1GRiGIUQFUeEOi9AAKACTg
In-Reply-To: <462CC329.7050408@tari.toshiba.com>
Message-ID: <0MKoyl-1Hg47A3yZA-0000Cb@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX18q/3i44osdVn594RKQX8/2F89Aap/HBfOalut
	0QQ+CyTXY06H7JHwbYE1JbKOihwyvPQskRLLbmwYNfvH5cCxKU
	yIFoqk87XFijhydsaBPXw==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

Hi Victor,

> >> Suppose both a PaC and a PAA are in access phase, and the PaC sends a
> >> ping request while the PAA sends a PAR to start re-authentication at
> >> the same time.  Then PAA will not accept the ping request because it
> >> has entered re-authentication phase.  If ping is allowed in any
> >> state, then PAA can answer to the ping request.
> >>
> >
> > I think the issue is about having two outstanding requests (one PANA-
> Ping
> > and one other) at the same time. The PAA (or PaC) having to respond to a
> > PANA-Ping-Request while it has an outstanding request shall not have a
> > problem. What do you think?
> >
> 
> I think in this scenario we may already be treating PANA-Ping in a
> special way already since we are not
> strictly lock-stepping anymore; i.e., ping processing seems independent
> and in parallel of other exchanges.

I don't think it is special. I think it is true for some other messages that
the peer may have an outstanding request while it also has to respond to an
incoming request. 


PaC      PAA

1<-------- PAR
2--------> PAN
3---> PAR
4    <--- PAR
5    ---> PAR
6<---PAR
7-------> PAN
8<------- PAN

Consider messages 3 and 4 crossing each other on the wire.


Alper











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



From pana-bounces@ietf.org Mon Apr 23 15:30:09 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg4Eg-0003ZI-7H; Mon, 23 Apr 2007 15:30:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg4Ed-0003U0-9z
	for pana@ietf.org; Mon, 23 Apr 2007 15:30:04 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg4Ec-0008FQ-U4
	for pana@ietf.org; Mon, 23 Apr 2007 15:30:03 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1Hg4EV0HKE-0000An; Mon, 23 Apr 2007 15:30:01 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Subject: RE: [Pana] Ping and pending request
Date: Mon, 23 Apr 2007 22:29:51 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceFv7qlvDpTVTJuQLaKZdKajM4uzgAHT9iA
In-Reply-To: <20070423155436.GB3668@steelhead>
Message-ID: <0MKoyl-1Hg4EV0HKE-0000An@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1/WSp+Zqbih9MRax6v+XRh1ywtpm34nFIsv06f
	vr3THHPJbAWZluGqhacqEWuwsTQGP5l9Zk9S1/yOzvBiuFWc2c
	4CTXzp9rIFmmRRLR/xGQg==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

> > > There is one problem with allowing ping in access phase only.
> > >
> > > Suppose both a PaC and a PAA are in access phase, and the PaC sends a
> > > ping request while the PAA sends a PAR to start re-authentication at
> > > the same time.  Then PAA will not accept the ping request because it
> > > has entered re-authentication phase.  If ping is allowed in any
> > > state, then PAA can answer to the ping request.
> >
> > I think the issue is about having two outstanding requests (one PANA-
> Ping
> > and one other) at the same time. The PAA (or PaC) having to respond to a
> > PANA-Ping-Request while it has an outstanding request shall not have a
> > problem. What do you think?
> 
> I think having two outstanding requests sent in different directions
> is acceptable.
> 
> >
> >
> > > BTW, I've found another issue here.  In the above example, The PaC
> > > will accept the PAR sent from the PAA and can return a PAN, but it
> > > cannot send a new PAR (this can happen if the PAN does not carry EAP),
> > > until the ping request is answered.  This is actually breaking
> > > lock-step behavior of PANA (queuing requests should not be required
> > > for a lock-step protocol).
> >
> > What would be the issue of having request queuing?
> 
> Queueing itself may not be an issue.  But the actual issues is the
> sender would need to distinguish two cases (i.e., if there is an
> outstanding ping request or not) for each state.
> 
> For example, supposed that the PaC is in a state waiting for a ping
> answer.  If another event that needs to send a PAR is generated, then
> the PaC processes the event, generates and queues a PAR and transits
> to a state that is waiting for a PAN, and it is still waiting for a

It should not transit to such state until the PAR is actually transmitted.
I'd say PAR (or the event that leads to PAR generation) shall be queued
until the PANA-Ping is completed (ping answer is received).


> ping answer.  This would require N*2 states (N is number of states
> except for ping, multiplied by 2 to consider whether there is a ping
> request or not.
> 
> >
> >
> > I'd like to see if we can avoid creating special case for PANA-Ping
> messages
> > (e.g., putting them under a separate treatment).
> 
> I think the only way to avoid it is:
> 
> - Allow sending ping request in access phase only.
> 


Makes sense.

> - Allow receiving ping request in any phase.

Makes sense.

> 
> - When there is an outstanding ping request, discard all incoming
> messages except for ping answer or error request sent in resopnse to
> the ping request.

If the PaC receives a PAR while waiting for a PANA-Ping-Answer, why should
it discard the PAR?

Alper






> 
> This may be an acceptable operation.
> 
> Yoshihiro Ohba
> 
> 
> >
> > Alper
> >
> >
> >


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



From pana-bounces@ietf.org Mon Apr 23 15:38:42 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg4Mx-0000DB-4m; Mon, 23 Apr 2007 15:38:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg4Mv-0000D5-GM
	for pana@ietf.org; Mon, 23 Apr 2007 15:38:37 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg4Mu-0001VX-6Q
	for pana@ietf.org; Mon, 23 Apr 2007 15:38:37 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1Hg4Mo3wxE-0000BK; Mon, 23 Apr 2007 15:38:34 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Subject: RE: [Pana] Nits on processing invalid message
Date: Mon, 23 Apr 2007 22:38:27 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceFyMgTyO/ZMomAS/KiEaOgjCvA6QAFV8AA
In-Reply-To: <20070423165919.GC3668@steelhead>
Message-ID: <0MKoyl-1Hg4Mo3wxE-0000BK@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1+aFkxY8i/u8c+UeWLmESYwem0wFme4+763dMC
	CRE1IaqECNQ9MsPH9BP86EKavNFWF0c4bNyviqMMvY+BmLSimq
	PNySjTTyVzHLu38qFGtiQ==
X-Spam-Score: 0.0 (/)
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>
Errors-To: pana-bounces@ietf.org

> > > If an error request is returned in response to an erroneous message,
> > > then this means that the sender of the error request message will
> > > terminate the session after receiving the error answer.  This actually
> > > does not provide robustness against DoS attacks because an attacker
> > > can send an erroneous answer to terminate the session.  So the text
> > > should say:
> > >
> > > "
> > >    Invalid messages MUST be discarded either silently in order to
> > >    provide robustness against DoS attacks or with returning
> > >    an error request message to the sender.  See Section 5.8
> > >    for details.
> > > "
> >
> > I think this is effectively the same statement as the original one. If
> we
> > want to maintain the DoS resiliency, we shall just go with "Invalid
> messages
> > MUST be discarded in order to provide robustness against DoS attacks."
> 
> Does this mean that most protocol error result codes defined in
> Section 8.8.2 are not needed, except for the folloiwng ones?
> 
>    PANA_UNABLE_TO_DELIVER                  1002
>    PANA_RESOURCES_EXCEEDED                 1008
>    PANA_UNABLE_TO_COMPLY                   1013

Yes, this is what it boils down to. Is this a concern?

I personally don't mind reducing the error list down to that. If we wanted
to keep the same longer list, yet still have DoS resiliency, we could
mandate presence of AUTH AVP in the offending messages. If the offending
message does not have a valid AUTH AVP, the message must be silently
discarded. 

When we are talking about DoS in this case, we are concerned about attackers
who don't even have a PANA SA, right?

Alper



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



From pana-bounces@ietf.org Mon Apr 23 16:29:08 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg59n-0001bM-Jx; Mon, 23 Apr 2007 16:29:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg59m-0001bD-K6
	for pana@ietf.org; Mon, 23 Apr 2007 16:29:06 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg59l-0002Aa-Sm
	for pana@ietf.org; Mon, 23 Apr 2007 16:29:06 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3NKT2P2007621;
	Tue, 24 Apr 2007 05:29:02 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3NKT2Zb014003;
	Tue, 24 Apr 2007 05:29:02 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id FAA14002;
	Tue, 24 Apr 2007 05:29:02 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3NKT12J000862;
	Tue, 24 Apr 2007 05:29:01 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3NKT1Eo014804;
	Tue, 24 Apr 2007 05:29:01 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGY001Y7WW1OA00@mail.po.toshiba.co.jp>; Tue,
	24 Apr 2007 05:29:01 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hg59V-0001yy-1f; Mon,
	23 Apr 2007 13:28:49 -0700
Date: Mon, 23 Apr 2007 16:28:48 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Ping and pending request
In-reply-to: <0MKoyl-1Hg4EV0HKE-0000An@mrelay.perfora.net>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <20070423202848.GD3668@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <20070423155436.GB3668@steelhead>
	<0MKoyl-1Hg4EV0HKE-0000An@mrelay.perfora.net>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

On Mon, Apr 23, 2007 at 10:29:51PM +0300, Alper Yegin wrote:
> > >
> > > What would be the issue of having request queuing?
> > 
> > Queueing itself may not be an issue.  But the actual issues is the
> > sender would need to distinguish two cases (i.e., if there is an
> > outstanding ping request or not) for each state.
> > 
> > For example, supposed that the PaC is in a state waiting for a ping
> > answer.  If another event that needs to send a PAR is generated, then
> > the PaC processes the event, generates and queues a PAR and transits
> > to a state that is waiting for a PAN, and it is still waiting for a
> 
> It should not transit to such state until the PAR is actually transmitted.
> I'd say PAR (or the event that leads to PAR generation) shall be queued
> until the PANA-Ping is completed (ping answer is received).

Yes, this is certainly possible.

> 
> 
> > ping answer.  This would require N*2 states (N is number of states
> > except for ping, multiplied by 2 to consider whether there is a ping
> > request or not.
> > 
> > >
> > >
> > > I'd like to see if we can avoid creating special case for PANA-Ping
> > messages
> > > (e.g., putting them under a separate treatment).
> > 
> > I think the only way to avoid it is:
> > 
> > - Allow sending ping request in access phase only.
> > 
> 
> 
> Makes sense.
> 
> > - Allow receiving ping request in any phase.
> 
> Makes sense.
> 
> > 
> > - When there is an outstanding ping request, discard all incoming
> > messages except for ping answer or error request sent in resopnse to
> > the ping request.
> 
> If the PaC receives a PAR while waiting for a PANA-Ping-Answer, why should
> it discard the PAR?

Because if the receiver processes the PAR, it may transit to another
state after processing the message, which will end up with the 2*N
problem.  On the other hand, it may be possible for the PaC to queue
the incoming PAR until the ping request is answered.  

So how about relaxing the third item to:

"
- When there is an outstanding ping request, all incoming messages
  MUST NOT be processed except for ping answer or error request sent
  in response to the ping request.
"

Yoshihiro Ohba

> 
> Alper
> 
> 
> 
> 
> 
> 
> > 
> > This may be an acceptable operation.
> > 
> > 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 Mon Apr 23 16:39:55 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg5KD-00057v-PE; Mon, 23 Apr 2007 16:39:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg5KD-00057n-1x
	for pana@ietf.org; Mon, 23 Apr 2007 16:39:53 -0400
Received: from [2001:418:1403:0:212:17ff:fe52:7811]
	(helo=toshi17.tari.toshiba.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg5KB-0005Ls-PB
	for pana@ietf.org; Mon, 23 Apr 2007 16:39:53 -0400
Received: from [127.0.0.1] (toshi17.tari.toshiba.com [172.30.24.10])
	by toshi17.tari.toshiba.com (8.13.1/8.13.1) with ESMTP id
	l3NKdS73025514; Mon, 23 Apr 2007 16:39:28 -0400 (EDT)
	(envelope-from vfajardo@tari.toshiba.com)
Message-ID: <462D19A3.9030901@tari.toshiba.com>
Date: Mon, 23 Apr 2007 16:40:03 -0400
From: Victor Fajardo <vfajardo@tari.toshiba.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
Subject: Re: [Pana] Ping and pending request
References: <0MKoyl-1Hg47A3yZA-0000Cb@mrelay.perfora.net>
In-Reply-To: <0MKoyl-1Hg47A3yZA-0000Cb@mrelay.perfora.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.4 (--)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

Hi Alper,

>>>       
>> I think in this scenario we may already be treating PANA-Ping in a
>> special way already since we are not
>> strictly lock-stepping anymore; i.e., ping processing seems independent
>> and in parallel of other exchanges.
>>     
>
> I don't think it is special. I think it is true for some other messages that
> the peer may have an outstanding request while it also has to respond to an
> incoming request. 
>
>
> PaC      PAA
>
> 1<-------- PAR
> 2--------> PAN
> 3---> PAR
> 4    <--- PAR
> 5    ---> PAR
> 6<---PAR
> 7-------> PAN
> 8<------- PAN
>
> Consider messages 3 and 4 crossing each other on the wire.
>   

In general, I do agree that request crossovers are possible though my 
main difficultly is the complexity of the pana statemachine with regards 
to handling crossovers specifically with ping (problem of N*2 num of 
states mentioned by Yoshi in another thread). Anyway, we should continue 
that discussion on that thread to minimize email traffic.

best regards,
victor


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



From pana-bounces@ietf.org Mon Apr 23 16:49:31 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg5TX-0007G0-CU; Mon, 23 Apr 2007 16:49:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg5TV-00073Z-Do
	for pana@ietf.org; Mon, 23 Apr 2007 16:49:29 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg5TU-0002rT-MK
	for pana@ietf.org; Mon, 23 Apr 2007 16:49:29 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3NKnQ2E008753;
	Tue, 24 Apr 2007 05:49:26 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3NKnRFm016063;
	Tue, 24 Apr 2007 05:49:27 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id FAA16062;
	Tue, 24 Apr 2007 05:49:27 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3NKnQTe009316;
	Tue, 24 Apr 2007 05:49:26 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3NKnQaY018439;
	Tue, 24 Apr 2007 05:49:26 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGY001Z1XU4OE00@mail.po.toshiba.co.jp>; Tue,
	24 Apr 2007 05:49:26 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hg5TH-00022j-Or; Mon,
	23 Apr 2007 13:49:15 -0700
Date: Mon, 23 Apr 2007 16:49:15 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Nits on processing invalid message
In-reply-to: <0MKoyl-1Hg4Mo3wxE-0000BK@mrelay.perfora.net>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <20070423204915.GE3668@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <20070423165919.GC3668@steelhead>
	<0MKoyl-1Hg4Mo3wxE-0000BK@mrelay.perfora.net>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
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>
Errors-To: pana-bounces@ietf.org

On Mon, Apr 23, 2007 at 10:38:27PM +0300, Alper Yegin wrote:
> > > > If an error request is returned in response to an erroneous message,
> > > > then this means that the sender of the error request message will
> > > > terminate the session after receiving the error answer.  This actually
> > > > does not provide robustness against DoS attacks because an attacker
> > > > can send an erroneous answer to terminate the session.  So the text
> > > > should say:
> > > >
> > > > "
> > > >    Invalid messages MUST be discarded either silently in order to
> > > >    provide robustness against DoS attacks or with returning
> > > >    an error request message to the sender.  See Section 5.8
> > > >    for details.
> > > > "
> > >
> > > I think this is effectively the same statement as the original one. If
> > we
> > > want to maintain the DoS resiliency, we shall just go with "Invalid
> > messages
> > > MUST be discarded in order to provide robustness against DoS attacks."
> > 
> > Does this mean that most protocol error result codes defined in
> > Section 8.8.2 are not needed, except for the folloiwng ones?
> > 
> >    PANA_UNABLE_TO_DELIVER                  1002
> >    PANA_RESOURCES_EXCEEDED                 1008
> >    PANA_UNABLE_TO_COMPLY                   1013
> 
> Yes, this is what it boils down to. Is this a concern?

DoS attack is also possible with those errors.  The only difference is
whether the errors are supposed to be generated due to receipt of an
invalid message or some other reasons.

> 
> I personally don't mind reducing the error list down to that. If we wanted
> to keep the same longer list, yet still have DoS resiliency, we could
> mandate presence of AUTH AVP in the offending messages. If the offending
> message does not have a valid AUTH AVP, the message must be silently
> discarded. 

This does not seem to solve the problem either.  If the protected
message contains errors, then the receiver will create an protected
error request, but the session will be terminated after receiving an
error answer according to the discussion (i.e., in general, the sender
of the erronerous message has no idea on what to do next other than
terminating the session.)

I think error messages should be used only in debugging mode,
regardless whether there is PANA SA or not.

Yoshihiro Ohba

> 
> When we are talking about DoS in this case, we are concerned about attackers
> who don't even have a PANA SA, right?
> 
> Alper
> 
> 
> 

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



From pana-bounces@ietf.org Mon Apr 23 18:49:47 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg7Lt-0001vd-OA; Mon, 23 Apr 2007 18:49:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg7Ls-0001tZ-V5
	for pana@ietf.org; Mon, 23 Apr 2007 18:49:44 -0400
Received: from mout.perfora.net ([74.208.4.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg7Lr-0006QT-Ix
	for pana@ietf.org; Mon, 23 Apr 2007 18:49:44 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1Hg7Lm17SW-00006G; Mon, 23 Apr 2007 18:49:42 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Subject: RE: [Pana] Ping and pending request
Date: Tue, 24 Apr 2007 01:49:33 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-reply-to: <20070423202848.GD3668@steelhead>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
thread-index: AceF5gvIh2kzmutxQ/6eVcc9VZyoNAAEqYJw
Message-ID: <0MKoyl-1Hg7Lm17SW-00006G@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX18FFpQyokreFyiT6/ia/etH1OOz1CIReR3dtpS
	s6QSjKc12Gcxne+m2oNAlhaHBbHTXq652mrvqSKqhOUoJ/kl8O
	PaECc+1lIUtgIfmrXvQVQ==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

> > > - When there is an outstanding ping request, discard all incoming
> > > messages except for ping answer or error request sent in resopnse to
> > > the ping request.
> >
> > If the PaC receives a PAR while waiting for a PANA-Ping-Answer, why
> should
> > it discard the PAR?
> 
> Because if the receiver processes the PAR, it may transit to another
> state after processing the message, 

PANA-Ping-Request/Answer could have a separate state machine. That way, the
transitions in that state machine does not interfere with transitions in the
other state machine that deals with processing any other PANA message.

This scheme prevents any special case handling to be part of the protocol
specification. 

Your suggestion below works too I believe. Though I lean towards the above
suggestion, given that it does not special case one type of message in the
spec.

I remember once mentioning use of a separate state machine for pings. I
don't remember what the feedback was....

Alper


> which will end up with the 2*N
> problem.  On the other hand, it may be possible for the PaC to queue
> the incoming PAR until the ping request is answered.
> 
> So how about relaxing the third item to:
> 
> "
> - When there is an outstanding ping request, all incoming messages
>   MUST NOT be processed except for ping answer or error request sent
>   in response to the ping request.
> "
> 
> Yoshihiro Ohba
> 
> >
> > Alper
> >
> >
> >
> >
> >
> >
> > >
> > > This may be an acceptable operation.
> > >
> > > 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 Mon Apr 23 19:07:55 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg7dS-0000fo-SP; Mon, 23 Apr 2007 19:07:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg7dS-0000fR-LD
	for pana@ietf.org; Mon, 23 Apr 2007 19:07:54 -0400
Received: from imx12.toshiba.co.jp ([61.202.160.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg7dQ-0002J9-VT
	for pana@ietf.org; Mon, 23 Apr 2007 19:07:54 -0400
Received: from wall11.toshiba.co.jp (wall11 [133.199.90.149])
	by imx12.toshiba.co.jp  with ESMTP id l3NN7ne2011303;
	Tue, 24 Apr 2007 08:07:49 +0900 (JST)
Received: (from root@localhost) by wall11.toshiba.co.jp  id l3NN7n1V019707;
	Tue, 24 Apr 2007 08:07:49 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] 
	by wall11.toshiba.co.jp with ESMTP id JAA19703;
	Tue, 24 Apr 2007 08:07:48 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp11.toshiba.co.jp  with ESMTP id l3NN7mCm024720;
	Tue, 24 Apr 2007 08:07:48 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3NN7mAE018523;
	Tue, 24 Apr 2007 08:07:48 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGZ001FJ48XP010@mail.po.toshiba.co.jp>; Tue,
	24 Apr 2007 08:07:48 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hg7dJ-0002RH-2H; Mon,
	23 Apr 2007 16:07:45 -0700
Date: Mon, 23 Apr 2007 19:07:45 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Ping and pending request
In-reply-to: <0MKoyl-1Hg7Lm17SW-00006G@mrelay.perfora.net>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <20070423230745.GG3668@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <20070423202848.GD3668@steelhead>
	<0MKoyl-1Hg7Lm17SW-00006G@mrelay.perfora.net>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

On Tue, Apr 24, 2007 at 01:49:33AM +0300, Alper Yegin wrote:
> > > > - When there is an outstanding ping request, discard all incoming
> > > > messages except for ping answer or error request sent in resopnse to
> > > > the ping request.
> > >
> > > If the PaC receives a PAR while waiting for a PANA-Ping-Answer, why
> > should
> > > it discard the PAR?
> > 
> > Because if the receiver processes the PAR, it may transit to another
> > state after processing the message, 
> 
> PANA-Ping-Request/Answer could have a separate state machine. That way, the
> transitions in that state machine does not interfere with transitions in the
> other state machine that deals with processing any other PANA message.

I believe having a separate state machine for ping works only when
ping has a separate sequence number space, otherwise, there would be
no way to avoid interference between the two state machines (ping
state machine and state machine for other messages).  But I may be
missing something.

Yoshihiro Ohba


> 
> This scheme prevents any special case handling to be part of the protocol
> specification. 
> 
> Your suggestion below works too I believe. Though I lean towards the above
> suggestion, given that it does not special case one type of message in the
> spec.
> 
> I remember once mentioning use of a separate state machine for pings. I
> don't remember what the feedback was....
> 
> Alper
> 
> 
> > which will end up with the 2*N
> > problem.  On the other hand, it may be possible for the PaC to queue
> > the incoming PAR until the ping request is answered.
> > 
> > So how about relaxing the third item to:
> > 
> > "
> > - When there is an outstanding ping request, all incoming messages
> >   MUST NOT be processed except for ping answer or error request sent
> >   in response to the ping request.
> > "
> > 
> > Yoshihiro Ohba
> > 
> > >
> > > Alper
> > >
> > >
> > >
> > >
> > >
> > >
> > > >
> > > > This may be an acceptable operation.
> > > >
> > > > 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 Mon Apr 23 19:53:52 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg8Lv-00045R-HV; Mon, 23 Apr 2007 19:53:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg8Lu-00042D-K0
	for pana@ietf.org; Mon, 23 Apr 2007 19:53:50 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg8Lt-00032H-9T
	for pana@ietf.org; Mon, 23 Apr 2007 19:53:50 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1Hg8Lm2dlh-0008Sr; Mon, 23 Apr 2007 19:53:46 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Subject: RE: [Pana] Ping and pending request
Date: Tue, 24 Apr 2007 02:53:39 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-reply-to: <20070423230745.GG3668@steelhead>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
thread-index: AceF/DpROWWmmKERSaWhVN+jV5Zx6gABioNg
Message-ID: <0MKp2t-1Hg8Lm2dlh-0008Sr@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1+a7bWqmaANHDdWuhV+KBtGUGDfbXyI0edlpHj
	ibrHk/9LTSLYI4gL7qvXOWI6gmaI4xEOQWRwihlSzEsG04yBbj
	jC3kk8Ehdon9zfU/H/5AQ==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

> > PANA-Ping-Request/Answer could have a separate state machine. That way,
> the
> > transitions in that state machine does not interfere with transitions in
> the
> > other state machine that deals with processing any other PANA message.
> 
> I believe having a separate state machine for ping works only when
> ping has a separate sequence number space, otherwise, there would be
> no way to avoid interference between the two state machines (ping
> state machine and state machine for other messages).  But I may be
> missing something.

Do the sequence numbers play a role our state machines? I hadn't thought so.

Alper




> 
> Yoshihiro Ohba
> 
> 
> >
> > This scheme prevents any special case handling to be part of the
> protocol
> > specification.
> >
> > Your suggestion below works too I believe. Though I lean towards the
> above
> > suggestion, given that it does not special case one type of message in
> the
> > spec.
> >
> > I remember once mentioning use of a separate state machine for pings. I
> > don't remember what the feedback was....
> >
> > Alper
> >
> >
> > > which will end up with the 2*N
> > > problem.  On the other hand, it may be possible for the PaC to queue
> > > the incoming PAR until the ping request is answered.
> > >
> > > So how about relaxing the third item to:
> > >
> > > "
> > > - When there is an outstanding ping request, all incoming messages
> > >   MUST NOT be processed except for ping answer or error request sent
> > >   in response to the ping request.
> > > "
> > >
> > > Yoshihiro Ohba
> > >
> > > >
> > > > Alper
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > >
> > > > > This may be an acceptable operation.
> > > > >
> > > > > 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 Mon Apr 23 20:13:35 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hg8f0-0003cy-9u; Mon, 23 Apr 2007 20:13:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hg8ez-0003ct-47
	for pana@ietf.org; Mon, 23 Apr 2007 20:13:33 -0400
Received: from imx12.toshiba.co.jp ([61.202.160.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hg8ex-0002c8-7m
	for pana@ietf.org; Mon, 23 Apr 2007 20:13:33 -0400
Received: from wall11.toshiba.co.jp (wall11 [133.199.90.149])
	by imx12.toshiba.co.jp  with ESMTP id l3O0DRmi002273;
	Tue, 24 Apr 2007 09:13:27 +0900 (JST)
Received: (from root@localhost) by wall11.toshiba.co.jp  id l3O0DRGE007148;
	Tue, 24 Apr 2007 09:13:27 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] 
	by wall11.toshiba.co.jp with ESMTP id KAA07145;
	Tue, 24 Apr 2007 09:13:27 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp11.toshiba.co.jp  with ESMTP id l3O0DQuh010953;
	Tue, 24 Apr 2007 09:13:26 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3O0DQml015392;
	Tue, 24 Apr 2007 09:13:26 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JGZ0018W7ABOE20@mail.po.toshiba.co.jp>; Tue,
	24 Apr 2007 09:13:26 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hg8ep-0002d2-9C; Mon,
	23 Apr 2007 17:13:23 -0700
Date: Mon, 23 Apr 2007 20:13:23 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Ping and pending request
In-reply-to: <0MKp2t-1Hg8Lm2dlh-0008Sr@mrelay.perfora.net>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <20070424001323.GH3668@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <20070423230745.GG3668@steelhead>
	<0MKp2t-1Hg8Lm2dlh-0008Sr@mrelay.perfora.net>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

On Tue, Apr 24, 2007 at 02:53:39AM +0300, Alper Yegin wrote:
> > > PANA-Ping-Request/Answer could have a separate state machine. That way,
> > the
> > > transitions in that state machine does not interfere with transitions in
> > the
> > > other state machine that deals with processing any other PANA message.
> > 
> > I believe having a separate state machine for ping works only when
> > ping has a separate sequence number space, otherwise, there would be
> > no way to avoid interference between the two state machines (ping
> > state machine and state machine for other messages).  But I may be
> > missing something.
> 
> Do the sequence numbers play a role our state machines? I hadn't thought so.

The play is implicit based on the following lock-step constrations:

- Each peer maintains a single sequence number space for outgoing
requests.

- There is only one outstanding outgoing request allowed for each
peer.  A peer that receives a request accepts the sequence number
which is last received sequence number + 1 only.

This means sequence numbers play a role in our state machine.  Running
multiple state machines in pararell and independenly would break the
lock-step constraints.

Yoshihiro Ohba



> 
> Alper
> 
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > >
> > > This scheme prevents any special case handling to be part of the
> > protocol
> > > specification.
> > >
> > > Your suggestion below works too I believe. Though I lean towards the
> > above
> > > suggestion, given that it does not special case one type of message in
> > the
> > > spec.
> > >
> > > I remember once mentioning use of a separate state machine for pings. I
> > > don't remember what the feedback was....
> > >
> > > Alper
> > >
> > >
> > > > which will end up with the 2*N
> > > > problem.  On the other hand, it may be possible for the PaC to queue
> > > > the incoming PAR until the ping request is answered.
> > > >
> > > > So how about relaxing the third item to:
> > > >
> > > > "
> > > > - When there is an outstanding ping request, all incoming messages
> > > >   MUST NOT be processed except for ping answer or error request sent
> > > >   in response to the ping request.
> > > > "
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > > >
> > > > > Alper
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > This may be an acceptable operation.
> > > > > >
> > > > > > 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 sjniz@erac.com Tue Apr 24 03:56:29 2007
Return-path: <sjniz@erac.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgFsz-0004rA-3t
	for pana-archive@lists.ietf.org; Tue, 24 Apr 2007 03:56:29 -0400
Received: from cpc4-walt6-0-0-cust646.popl.cable.ntl.com ([82.29.114.135])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HgFsw-00031p-Mo
	for pana-archive@lists.ietf.org; Tue, 24 Apr 2007 03:56:29 -0400
Received: from dsdp ([118.96.118.187]) by cpc4-walt6-0-0-cust646.popl.cable.ntl.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Apr 2007 08:56:28 +0100
Message-ID: <462DB82C.2050108@erac.com>
Date: Tue, 24 Apr 2007 08:56:28 +0100
From: Stephen <sjniz@erac.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: pana-archive@lists.ietf.org
Subject: industrial park understatement
Content-Type: multipart/related;
 boundary="------------010100030206000508010104"
X-Spam-Score: 4.8 (++++)
X-Scan-Signature: fc231bf912a450f71747fa7a4e3e2f5a

--------------010100030206000508010104
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<img alt="surefire" src="cid:part1.06020705.05040808@erac.com"
 height="213" width="369"><br>
Helsinki is tevens de grootste stad en in alle opzichten het centrum van
het land. - Delivering the section within the schedule and budget.<br>
Your role will involve working with a team on the project management of
major retail projects in the Epping area.<br>
Ik ga opnieuw meedoen", beloofde hij al. A strong commercial awareness
as well as excellent leadership and staff management skills will be
highly thought of too. The Music Cocoon has an amplifier and features
hi-resolution pure tube sound via actual tubes. Dat maakte het EBU
(European Broadcasting Union) vandaag bekend.<br>
Portugal (22 punten)15. in zijn klas met een gouden award voor "Een
tocht door het donker". Zweden (116 punten)04.<br>
Rusland (154 punten)02. ze zijn mensen die hun moeders als hoer op
straat verkopen! You will be based off the site.<br>
What does Chicago have that NYC doesn't have?<br>
"De Finnen zijn de verdiende winnaars, zonder discussie", zei Sergio
vanmorgen in het Vlaamse TV programma De Zevende Dag. Daarbij is het
opmerkelijk dat meer dan 1 op 3 singles legaal werden gedownload via on
line muziekwinkels.<br>
- Ensuring a safe working environment. Groetjes van :Ines Celiker. Louis
Vuitton iPod Shuffle coverNow that the new and improved versions of the
iPod Nano and iPod Shuffle have come out, it's no wonder that some
people.<br>
000 euro in de deelname aan het festival en stuurden Kate Ryan op een
uitgebreide promotour. You will be indispensable to your employer giving
you the opportunity to showcase your leadership skills and build on your
career.<br>
En zelfs de Faroer Eilanden Veel Suc6 jullie 6 met voorbereiden!<br>
"Ze kunnen het Eurovisiesongfestival beter EurovisieSHOWfestival
noemen", vindt ze. -You will have a degree or equivalent and a
professional qualification is desirable although not vital for this
vacancy. If you really want to get revenge, create something of enormous
beauty.<br>
alS je het niet verstaat vrAag mAa aan je m0eder ;) Ja ik weet wat dat
betekent zelf ben iik ook Turks maar wat is dit voor onzin?<br>
Daar is niet iedereen blij mee. Lees ook:  Vlaanderen heeft ervoor
gekozen!<br>
Hij is meteen ook de jongste artiest ooit die deze eer te beurt viel.
Helsinki is de hoofdstad van de Republiek Finland. Pre-Pixel
Preservation How do you preserve those old photographs or videos? Dat ga
ik gebruiken als nachtlampje.<br>
Working on a book, painting, or song will help you channel your
frustration in a positive direction. Spending more time on the
activities and people you love will give you a sense of abiding
contentment.<br>
</body>
</html>

--------------010100030206000508010104
Content-Type: image/gif;
 name="snorkeling.gif"
Content-Transfer-Encoding: base64
Content-ID: <part1.06020705.05040808@erac.com>
Content-Disposition: inline;
 filename="snorkeling.gif"

R0lGODdhlQHpAPQTABsDETE0Cw4xI0YIJ5mpj9KovqW37IOpd256VdLsktmmnbF+omeS0FaWneTj
pZLaw55wo5TLaY5//fjZvvqhecrfT//5SvWJ14hWqKNV+U7A6tBP3sp6iNKkNlfdrKSYMiwAAAAA
lQHoAAAF/2AAiCMACGNACmg6DOzYpgHLkrUtxjJ9mj9gjGTSAYHEY1CgUqFEOGGqOFPBnrOUjYk0
8nqqYFH4VN6UpqS02CyHS7/3qWXl1ZA5o+w8Tz9Xa3NlZGppaGMnbW6GfW92dVh4eVx7Z3ZDO4GN
R3pHOFCGVWmfdYxQYUNaXlh0iGJBOFtqX4hMN05MoFOtU6MBMIwlqIO4XJeDWTO8lYW0LTe3t6aw
eL7A08NuecN7cGLKvNtotEs5xWFRdqO+v+HrqYrGrMia4bJmOrpqgJIDTafv/PyzhGKLJ01IKvEh
k0xHPmlEkvDD4+/fFFSjcpkTxDEhwov38HGSFU0jHIkTXf/8A+hI4Lk+NpQQyZJwkhwq+KBphBiM
EU0rFpvscolrR8GYHvvIVEiJYch9rqhQOgWQjsYa3AwmVednC7mObLA+DOkNjrOFLDMRzcUR6TpE
Er3SxCmkjblJfKC+enoRowxFWcnNTIr3K7lctnY+lRhVUBShfu9iNSr14JqIcufOudvrcpU7NZ0A
WvlrqKBB3v5kduuU012dkjuLAe1kqWi4/wb0epbKo+rVmlnDhs35Jiw6OQ6KHp1bt1+DEXEDn8s6
kc7ExW9axZPlE6U/uU1zjD6mWOZDc65R5dRV2qHbsMJz60Y+Dujz42gJZZNelPYu7qEB3yNW+DBE
bz6pIlX/dZV54ohRAqgn23G3FKIKPys5R1ke3qyg2oIMauULFUZJKJtV+aA3oCSlZUNfNfbx5hV6
EVJjkYMpqohVec2Z5VAw3OwnFWh7ycTYCbr5Z9yFFmZUgAEQQEDAAQhQYIWGQyJnQgENLFBABhLc
6FgyH8nhYZJpECDmKAaYBIAFRzRgF49NDHCAj4gBOZ4cJAUi2JE1aimkLwEKuGN8V6YGTU8barco
XTCZMkEBBSyAY08ysYABARUkQICadfoTQ59lbTOoQwxAKsADLAYzaiuDdoGpJwIQkIACCizwKQKh
4jJmQk9C4GUGKzFE5DfdvZHEqCZYuqYJbSbkwBEYXGjC/wWkHSDqUY8SQcG3ClzlFJENSbJVQaFZ
SBt6e3iY4bbcrguguMZ2twZyBEwwgQMTLIACA20AoCa0Bnz6wAPYCnDBAg1U8C3AvfIggAEUT9th
HqIumwur5j5gzI2DwWXgI8sIeIsDXDS37a9pKKBKhBkTktyI0ri57BgQUEUZAAYQGYDFJnPxgM4a
vJAcqSIggIAFFlRwQISHCnIAaAVYZImQISu5sxazAmiUzkbH9OPFNmQ8U5781QJAAw3c2US4tQ5U
tQgLLEAxARSPAIEtKliZW20AeEmxAQWYUswVfAqQQQEJpEozKlaH/MMLPjgWQAQE5IpONXkkcFWv
9+lkgv/L8US40L4W4Hrn45BDfgQE3xLQAOUjT+xrAKySwCs6LAzecxMJ4J7A0wvSlnMTFbCAOCcH
TI0C6UKxJW5TvAFAefT53LE558RlGDDL6BzeSTQk+la30dEXkM+0KrjsYOA6RTDZVBRbOke0NChC
wAAEHGz/CRvIgAII4KBUKQYwMELBCw7wqeYJYgEIiADmKLUPKLAgeIhRgQUSkAADhAkctYlABfBW
jARcQQANAIAC9lUBhxHQBAwwgAPgpgICTOxJ0qgbBCJAAQK+oCLDeFIAKDaxgZkghZARQN0MMLQb
DJABByMeIVpwvL6VjTUNrAEF2JGI5RRlK9YDIoTItyT/3mVwfpiZIoswJqKSoKUI5xPjCdR3shS4
rxr+Soz8MpiG+lEBf6Rhwf7694D/CSCAAyxgFyWDFkAssIF3sgEEJUgAChppDxhczgY7+EGZoUCE
JOzcCVO4Qge0sIdAiOEMb2FDwrWJLTrkoQ/RF8SeEbFgREAi75bYRCY8MYoNAU0VA0CBK9IiiwLY
Yv4WeZU3joGWY8xTGS14Rj76QY3sYKNb3Kif0bnvF0KB2w2iFYAMwIhnFxDWBdIpmi98ShnK+lkC
2CaC/jGwf/Zjgd++EIAUdvFTAMBAA/YmAAR4wnEA4BICPEUAg7IgV7wSQPPi6SAbzm9SHOQkuYTi
tE/t/0cBCTgBSAUmi2KaQAKqdADKAsCABuBtUjGBgCHghAQgzkF9FAtA4d4gp0wtYDI1WMDeoHUs
tqwtSlHiFUy+gIC4BSCkgYOgA5lALBoozl4ysalXamOmuECjnd2BZ0SKJbGyKuYLLcBVNomJq0lB
QE4oKABKGQAxgqUzSvNDigRxEhN94cpTU0OADYvgsSJ4ThwB0BYSPkUADAh0bzIVggSAUAANtI2x
RoFoU//wFiC8cjJ0jIEByHCaCuRPKIyLANwIuAXPMaEAb5WhxVCKlQls4QJjiICDrOavnJKznoPC
Hd+sKNqRcOSxSA1MDBpQKzVFQACp06xBBVYUAdCxTP/FOg1XKTqvvBqGW2uEUEfGghQbSBATubAA
uCaggN3VyoMonULhDHABh9TmBi2siyAoRQM1KYBDNmyBa0k0xNJsqQAuYwFzhwrHguTLAAxQ2tRE
4Nr2Romzsvkg3wY7h+Dpdw4TWKsKGGdYqbBKACtsbwPyxjNUiHNiVGAteoXiL5UG4Kd/COmgAmwO
z83BAcuCULWaMEyzjlaiBRVAAphGAQubgIH9ZC4COFBesanGahUCT2cvlKccJeI0Iq4yiJhFBQ4y
YAjqAwDH5vBfFRj0dgCwLTrrC9ZE0JU8LIjSKIKnppi80ASd8thRAtDmHEy0CBhAcRaYiwLm7sFt
AIj/gAPUC9ucdcVHuJ1fokdlATMJgV8PaN7QiLw4qII0AZSiKwqK2QR61goOAUaBBugLQX+NJxV4
qxuClRWuBDV01DUYsACADKhXt2wgNCkcAJ52J0lPmgKwzUEFAuBYAGwWWa+ij4fc9KLZZPBVWGvQ
aTmUnxmBw7p0VYADXqkBR9hWBf6kz3Uppr7lPIFtPT0pHP9H6ACAygZ3BLRrj1LoYOv4BIkuHBU3
K4CWPhjCbDnAkv2Gmd8oGwbtk9KnJtDprl5rAlGc8BB7psTCMUDdg7PBAzLHXqXBuwxnjsmsK5VH
nHDmlfUmQmgVNECNTPsOwMZzARqLAS+t5JgwxMDe/xiugp9qMaoAICi6GNKICg3JqwoyAcbnx0Wf
JOvowdkC5c6dgAecXAa/I0HO490DniHlAdewxSgQwABOSaBnJlApww5QKZ0OZLrvEBuxgQfVGjxN
pYgXqiAYsIAVToAzm8EaimLwgrRmIAMArZNlntHFwStRzTRjwQEYQCkKspQOMYcZtqcO+chXvD1h
lBhtNO+T5h1App/7grMCoAEJSNT2ky60BgjwrQAqD01Un7wjuN32ScSeDZ8xcGrG8LmZdTZFZTuh
J15ZgpgHgANHUsi9fqEbEwi2kkYFgAMY5lCwi7UyxTovEJ42bMQr0XSC6U32CEPuJTCBdtnQEuAW
D//KVjOYcCPnJj3KIyLd5nrn1H/lAIDD0BIwgWwxUC25oAEsQFcHEAHB8waOs0XYZ0xhpX/00iFt
xAY/FHh8UoEWWBfL9x0kWHFTVyH1QX7q8Qw4yILsMSqBJFZftCbndjb41xTdICPhVlM5WBcS6BhS
IHvI5hpBKCYJuG0n1BRHwxvBpYRVoIO0swvUcxSLVAwwiFhCglZ8IHad4CtamIQj8EPb0UVNuBA/
4INgV4bilh6IMwsKeIJVUHlQcwc38IWtMw5hoQhdMBCkEWR5iCR7qDHZwG3dcQUVoYXltxvGAYQ1
oGxr0W6k8WFg4Yh7OBLYw3x/eHz39X/vk37jFw//iVgUn/hh1QEzhRJ5ltOCo0CJqaiK7xArOhiF
XUGEGmMiowIqh4iLLqA8qQgyO+CLU5d1sAhUn3AuC7GAvrFIZTgTuPIkDaWMWQhvlRQ9mcgCoZYm
/JUGZ9YEoLIf9eGEUkGMY3iM7JEGJ1SJrjeNrMhXhIIczQQyluGOVGAidbgfn6MJ7RCI8UJRzLdU
GYEcZ0iHneIAhTN2MQAqSVKQiEA7ykN9N8CJIjBa7KgWJJMy4aMzCZF+ZJEL9kORcpgkH6gC1cIz
BoArBbNZl3gUGYABgjU3MPIGTFRYABCRuWBJNXRaoeAoYVgbLHkLF5ldQVB+ZcORbuhxnGdVJLlM
//7YRcYyE0oJlQVRINkjOV4JlQSWFL3gF/FxBlQIkQkgkWHEERZ5jyGjkTVShx2ZECCpkHQxhesh
Js1IhNTTdFp3kS15Ai9JbQRDk91Yl3aZkzvpcb3wky0glCNWNSlAQNn1lyORlHewlLnQlFSode8o
lZ7WWc+xj2lRklGglVcHgwrklXJ4i2IZkLWQfigRENJBkra5EAnggW6JPrJQGhgJLWHklYmBBACz
WNwxIeDRJn2pmmzYVdVIbZQHLxqhGz+nAuYEAKoWRgpXEicVBi80Vk9wedsZB3tEKbs3Ah72g9gY
jFL4mngBlk45OTcpOssEJNvFHsiWmjrDIbs5nf+dGTb5AJr/8ZZjQiBmuZ/8+UXpUXFhkDs/M5Fh
Q0MtEitnhgY2hGD6IRQcgCO+mAKftQ50JQE5Zx5QQytY6HTyGZy/sI4CQzBBUIAOgQJ5OWFkw1LJ
KQUq0JYrNQVtdoheYTRes1stGpwaYiHUgZ9cNFZANY8IFE9/WRj+0F2S8JrWWSCVY1yb2X9BAaKZ
aJVtQKTtkVg0cFhHQFP/NwAcwAEKUClAAAHrRldH0JuTsnMdFwaVojQ51TtJoHAqxERpNwIPMAEQ
ZqKtJQD7AjMicDB7OhWelzX/t1M9emAO8AAFMCnjckEyFI6ruQeXxwAYsAFS8ADyMxklkKcQYg7/
MFOl8MkOYaiCSToLh1CjrVIqCAIpqOqkCWoLZGot+YOSspqkIpETvpKfZpKrroCqqDgvEkpSRtVr
ifABLZQrFPChUeclEjBZlOVaj2cDlHotpRdDJIeZnjUHi8NERsAxKjBZNqBS+oIyLzAlB/AABtA8
KUNTG+EKTGBCLWMCUXIBDtCWOZEYFTB0f3ZpNbABAeRY21krEspjIrVMP5J9EMoSdOiF5bckNMKk
N8EhyaEx/CgPoddljKqiGFuNw9o1tWqrExKyyjqSzzQVNoAtl3kPVfMMDaA0pkVMQNBUZhAmloNi
6+CRAuCJtkYCMiYAvpcYood6VGBjcaZAAzQl/yPwXFzwge5ILgVwPS80VfyZJS3wOyhLaL2GmABw
AWl2MO90l5WjB5RHs0YQgLKih8xpBiVQo1rSXSHbGtcBODH4HdaDhXM7RrHwjs5RrOWhXY+QKYiB
YW1hm5vhJOiAe/9AbEfBNghQAT8FBHmkDP8mC5GVAgh1Ap5YX0eAW/cjFjYQUeEJBGgaCrjyYHdR
RdjIhhmgepHFQUrhen1iAYNHigFwYUe0JTbQPFKyBSiTQEb4NWVaFSHJLQDIpQRGEp/RpYBjrE7b
LdsWHWgBEV8TPtyieiLrSaTCnDvRssPlvSQZAL5XQwPDAzQalDZAABKAASSQYF/AXIBoAyOKtv+e
xQSjZT2nJARzIzZUwkD2amCrExHitEJ4xwQNrBbbBgC5WyOdC1C9e3xX2FLysw75xASfYjdQIoX+
9io5W1P/mLdXqZWR4SG02RNn0b+PCxDCK5pmgIhIc4l6Ar4ujCGqUpd8SAY0jB3o+wZfKKQKZD2F
OAIepLYXwMMo0LlFwDRMU3ZhIgIU0C81BwBNS4n+QEdhAAEMuwEFoGoCAAG09immVX5dcmTPQCWS
Ro8DEG+64Q8O8CnCMkCo8HM3KcMYkAFMdCvtc0dmhX/+MHomUU8ykwB2AwRQGT1lqcKQrHWFKI7S
Jwoceb2k9Y7eWBz5QQKXqJHPESDSJ5oVcbv/fynFrtIg4+jJ3sgT+CDKoxwWaJDKJkExEoAtp6xl
J2DFTLMOwDstZgWIAwAwObYADLs4QoAAhDOvg7k2hjTJKfA/kKxTQ1c3AHGqmZyfBbUBTDQinSx2
MGCPQsHDkDLKF1mVVkePh4DLJRmbuMEcjUt1glB5QMRZ6OwKPMySyGIm+8zE4bsLWkonNjd7xZp9
5byfSRwV6ty7UwDP2rPKyrF8XBNcxVw2BRIGDU0LtfxltUlRl8jR4shZTJku9Jyf3XAaumhgHJ0T
lYzDIN2GUTDSJN2MWvKZnNMSASN5Gc2oF2o9+RHTOCy4kywChIjUD2LSiWIIZ3jRH3vILY0l/0JN
vVVd1UZ1013E1Ke8Ho0w0Vh3zxod1B2dBR9NPUeN1NWgVRMdeSPtzVCdrDKCyFr60ptJ1DfJD+2s
1iMCzzld0PFsH2A9L7CMPliyz1/Qz2kDQjVt0wINfQRNfunCo4MNIAsy1b2Azh4d0yfIxAtiFk0t
DC4iILQyEsYs2TMgxTRxDWV4CcF1E2QaE1wpfSb5FUBCEwsINSvYAqpt1tRxrLEhztf82StQ0KK9
NUuREaat0WMn05AyuLhNhn/xsbBNhKAN2G+rGcm6mbrY3M5NDqxNYBV00MTt1MhIvccCIP7g3VcN
0YBoKDOGNdP01VS3mgRJI3XruOvt3Zqd2v9XAN/gwW3P4iIx2CFvi9/5PS/7/ZSqDcnvjSPxjRIV
1CjlfdwpMY9tp9+ozdtW/eCuQdqmIIbroJoQLW7pHYySfQRkaQdw+CdPSoXqEuIiHs/Y07IJ7jWh
jdViiIMMaBeQwSdl9BaC6JB9IV6Km+Hc8ZnovOJP8EPaxyKLrB0xfhLg1RcUG3Y3juINzeRN3r+3
St+iPSPxceVG4jNzAYtbvlRdfkISHhQ/7ignYZUSMyI1biRd+BOSkcTr3Agt3kif+OaJY+DmsZfr
UR3Zi+RimuKVnG04yObhReJrSQwvM+dFjtzKfU12ruSK/SprHpaQoBSk8Bozs4ihuNKIDtz/K6h5
nL6mg+akNmzh2tcbYMe64VXq1nfox/qGSQqbOlB55ZNNZ3la/40g/em0a5WHXvp1LD6rhFmgwECH
bj7idcLpJxEPtD5uRm7ZmJ7kdLzrStHrz14SAIrS0rgRpA4WwH3icDF2qg5CV6iWxVJB18F649ZM
bBGLWpHu6s7ii+TPgygX/7k9DWnsgqKI/Yntrkxuhw6lBkqYjvHuAa8LSU5usNKfUYrv/DTq1gel
wtnuljik1gteoW6D8F6fn2FWCA4UkDFeuX0Pf47EIb/j2WTv7RuiWVfqlyFHLAzLLv/yWrdVVmY4
XsSXQriPjZjz8f7tJJgX8U4EV+h8sm7w/0R/KiP72YZIj19aZUW4vcZuI0fXTiQ+1KXz3IEATpqp
9RCvZcoy749L74EEVoFtiKVTlVdv9rZYzE8PHilbGONu3j4uFnGPtxZI93ir64WIhlsfsuHDDEAv
Nn7v48Ml3II/6I2xrBJNFySoEINe8Yp4Rpcu93jxEbK5HPza8sf55nJnE2QYDp3v41xTq5NO6aH8
9mrB0rbq5qm/VQDK+fZG+rneoKH/CsL79bUv1tfhA/am+VD/+GD/4uoeI2IedtVnEuf238pvEF83
pkRxhCB+GsoAil9m7miZ+YpPFXJLXsJ/dCN972T2j3JR+lzJDOKhhqyAlYdiHtKd/Tmwsf/s3/4y
rBUgIAgAKQQkYJ6BuJ4jKgqDCATseLstibe3LIWy6YCDnmpVgw1PJVlNWHJObTydNCUaHJG1W6/U
LG6xYOuI2aNqg9EU28kCn4cwLqyoa719uZXYGNBMkY2X1thQW5qaCYrcj6FiFM2a3twb2p9kFtEg
Id3akqCd25vjGlKoolSlJZnPY5BZ4CvOAJYkTidRqWlMnKocq5rXpqSaXhkdZJpi3SIjcJNw7yQJ
nu3grvGmUzEZ6OpuJvQi4nQY2mopdt4lZvIsYK2nD+44OWmMKROq9Rx61wC4srcnljFPyAQNwjcM
DS9oUKRVeVSNU4xnBM/Q6gSkYS46ox7/SYTBqMs/XUEAvmCl6xOLMA5TfXumYstMkSZJskF0Mt3L
eal4cdpj4t1GOS7qBbxlplmWQvykbKmoLlYdMMWubotpCB/JhU1uiluqj6cvIVXhUGn2RalHi0Nr
IjMKNsxRprmo/vwRyUpHsV3EGO0T9uoTvIXvvvAada/ak0f4qJDFjsqIwVIKHy4qNw9bkA/zPt7L
qO/RvwEx1tQspDCTttTEarUbEo7J2JClVZWBg2MSz+hcKoKAAQKCHBAgaDGC68ABm1B4Yj41o03T
i22pdEmAKNxW4pxyQE9QoCEuVn50m/bX++jeOeoUEkzLWbx6wi/8cunZjeFU/EyWWkio/2TlhGtv
+YGfRq9pdVN//q1HXTtPDAgfcAZ2xiAABiSwwAbIjQBdGnZtsAE2styElh2lDCABAwwcAMEC50E1
HxtHGNCGPZlwiFkGEEBHgI1OpSgKafa0yM91fEjlWDBHnmMUhw3mwIht2Az2WzISTdLkTQXOxolm
8yBUJW0looegiklC1slaTnIEpVzEMWGBdygQIAKJvjmHTzaAAYFCegOVMEACEsBIAI1ztiTcfPNA
4BgxGSmyAHMyTLpHhIEKysRdlsbARXPB9QLaAgt4RsGUg9oZ4FQTcQpooAGpUSisKZDqW2Wn1rkd
kz3a6c+XpyUxQ6eu/OYYrqLquiuGlv9sdth2XlnAiwAIIADAAQ1AQFYBRQagrF8kNKBodPxgZsGu
HwVQAQAVyJsCc04cUMcD30Sx7UPC1tPhEn4GcKICRQ5QAAkXaLCilmdIkKoEdrQb0AQEEODAowGE
iyNzT8Q2lCeNfBnNIAaRWzI2dfg26oDuphKFbIethNgrxKYFxSf2KGsroe1hxsVkLr8835ifOKAr
GxYjQGS3qRmwYw8DVCCAAhecmBoABTSAAQMNMEkFBUCH/K688loQgKpWEKBOAuQIAN0B2j5ywQUT
TIBxFISgcPQXUIS7QQYbj5vB0wYUsCcLCBRM93kALCdBuBGjkMAASxvlwAQKENB2TDX/FpCAd239
4tJ2pzT7Fq/lZPPRzLjizLIlwZGBBNFuE1dt3s1+l3ofq7MOqso8WHjEQU955VUXB4qQZ38oRBBB
A+TxQXdsmztQ9QUFBDGB1hhIrokTClBAQQUHBIdAB2C0rX0PDFgUAUTZIgAdAl1oYADddeN9B1gI
7y6CAnzgvwBAIAMZGMEGcKA5BTjAARQ4T8RwYCMSbI4CFitCBCwWgXsBQQGp+pw6AuiGDhnAgCRR
QNYK9obmBcgHZ1rIJ95RKJiwjAbG89fxxuKMISQPd/zrSd8oY5jNIOQGLHShxGzIjCXmAScg04H5
ngUD0G3PN1djAgQmIIULaKEADdTa/wIy5IgIKEB87PLEpuhwNhh8Kw/wil+2tAQADWjgASiYQMmQ
RQMuYkUEC0gNikjAKsKkIE89uBYGkKAAHjTAfJWzQbgIELcDwG8P47NCGNZWsg1c4Gkm7MH16PY0
N9RqOi6cGQx5RJM2/YxUN5wdJq0RPx72cAxL8FQf/TLELwynI0iEnfFccLxxkYo40DnUIgEAul3c
SwYGXFkGPIZCG7ivB390RM6qqas1dKwXnAsABhqQizfGEgDbIgipGnA/A3yPKkBL1SCic4M9HWWR
JzCk8BighraJkwjJqUEit0nCM9zLE6mai9dod0BsSKCYDUSB+3JXiZyB73XqkgVJDP/0wrWERClz
+tVOtOSagSDrHTDD2cq+RrvY7cBH16FPL6QiUvEMyQHZowE8ceA1HBjQhYHUggNgECMvYm5ln9Cm
QAPAge18Dk/4cwe3ckhB/r0xXA9op764YDEvGkCfJDCAxRxggamZQIvBkkAsCBAAAjSAAceJngz8
t81wGUADlEQAM+hGKBhI4GPRhEHYSCVXAHBRHSUlgil5l5KZcWNZiHVpDz0qS4LEBjSJQedIZ1PS
P8wCpcILFkS80NJivPRJS6FlZklQ05sKIKci2KkIempFfgSVBENt4ASM6gOklnapJGlqAp5K2aha
FgB70lJVC3BVzSJrqw7oKgzAerH/sbbArB4DAFqDoFa2uhUCcBWBXK9DV7tGAK8u0CtUsetXKQT2
CIMtLDJ8l1ghLrYPJ60MRUclLYVAoyBSRYfYxPMNPHA2iEIE4n1VNNpJRBYu5sDstIjQyIvNQACC
YwHCgBAurMGLClrMQVuJOgUliCCgwwsABeKAtgRca7ACYICrcPC0dA2AAhawwPgKYACzIJYGGdQx
zCS5uV0Ulg0WhkDXGiA347YVA3442vAGMAGwHkCTK/hiNMWQL5j5bwQVANoAFmqDAIaCBTvbBUxm
gREFnUF20xHQTKTlH9SttBW7skiZK2zSAlPGEEA0yDd0MjOcyJQdtHSbN14gNtj4/8EJEciFWWF2
oP0IoI0eg8cLDQuRIjwAagSx8Y1Z9RaFICtknv2HTFNIgBiJU7JQOC524DEzB2S4BFv+QgGWg6m1
ofOAaUDhU57VI95NemT0KcREvnaJN9fpSn/wT3/yluhnES+GNHxFhUxL6ZUITBkuJRRiw72KUv+A
BrpERa+y3dFtu0ejVCoKXRYR72rHpN6nBZMRzZ0adKcbAL5mUS6YbdFwyOUMLgZvAwiQZWzYaAS1
jemhYq3vRo+YGO+o1jlUahCYgazdmAF3yeyNDHyP69SBNoekHRUNjQ/bsKBCbFdcPnECF2Y/b+qD
DwWeA+pwnD4e3w+4Yf6X+PoGaP/npnQdUMhYnut85y0PQ8BL8SAeCl01h8IZzSk+dFipeEJT8SjK
hBnvHwA9RQex+tVbQGCyOILsxsZRDK0D77C70IiPdex4Jl5yYjcH5cngybFG+Ix3L7EWfhKYK+OR
lbQnYeIp3boq526r0TEdNAF3j7Xt/rteDRhne9932/t9Wda4K9ngILifo/6Emmv+dxwZlZ/0vW+k
I7ho7lrQVlAPPmLy97Ogmrnetz7ppAG+9DtM/A0eMKQemPcEyVSXjAmgOAWEjsRG1hLWzd0VYNni
V2dH2R2GzXEsDJrtKkj83S1ldLVrP+YgU9ITWUel8Hvb8uT/eexr+ZsArZ2Y7Rf/frUsXuxgyEjU
B3ggyflVGwksgAHYjdLVwNqJFChU0rh0BsGpFeAlgVdAgRIRwAMoX5WplZPpwCLNQIyAVQSwmAB0
msUQAPVhhDVAoOxhHz48Wy3ZQnGNzR4wiRLFEKBZyHc0Gu9JSGKsH/+Iwx9EFs95X1O4igz0YM7A
gxZcyGMlIPFYiQyuhNHVIBEU0/D9Fyzs4CJA4UTMHu/ZgAPUiPWU4BOaG6H0By4kRxd2gWYQExjw
y4hZjAYGzBYIgOHEU3Q4mbnBiwh84P1I0r0kANk5wBVqBAfq2xuOS4xVYH00AQuNR/HkzBMiy33s
3YMkz9ENYX48ohs2TIQkoRw9/8Il1sXt5VEfcmIReeIUKlj+NaJFTASBHRoX6gAdWuIlnlwr8mGF
nWIZkp3YDFYA8M0jpgSgqNWz2Z0v4kKetMXzkJ29mRmiDAYU6NNRhBEujA/xyEAELGIxDd4Yal/P
SCKa8aJ6/KItaaC9lVSZBExTAIomeN4ZmiMu2lA6quMzlmPUNEvpWCNnbWGw8IoRQeN6aCBADsUy
5khCXiM0koQ7DuDszMpLlUqy2QDQTNMJseEMfGAakoAC7FgAfCABLAAb3sACRACtBeTB3GAYBiOi
cGIbHAADSICSJccNlFEF4gABREAFgA5Y5WMikOI/OEQsQF5AlpajwOOx4AHQ2P+cRjLkPa6EUYbF
Pialt/WdhBCYTGZiU+iRTQoPZRSBK5WhKo7U/eEEM6IeU3IkDdygDtLkXM6QWsrlAHjkGpQRB4pk
2pRk8j1ASq4k2rjkAAFNAYRlMJJBTTaPDOCkTmqLCvhkOApAUA5lcKlVQ75MG/JjynBGXBKTU3oU
VGLkVDZHVaLlVcJMZ57KQ/ajK76JXHIU2O3hrNwlVWokWl4ms2UlqbXhW77baEpl/DXhHkrlDK0H
SsxAAVwABDDQ0STj9cjAAziASCoN3QRAAnwgAnhObGUAJbHTGgyAPoHisBUCGSjAXLYZYS4AjPAk
ilHABVAA51hYUN5YnmSkPgr/DNaAxWxeH0euBSYZhR6EjHLWxrI0oT/iYsSRDrv9DjrphFdayueh
ZzioJ3qAQmj4xSXUIAfql3o8iIfuAoCagsqoIkddnDXGjlSaQRlq4wA8TcI5QPV5x2v5oQjEiB8N
QJEJAAdwQAokkhPAGkH8U/LgUEcJgKjpDQnkS0zAmAmMzwMBmwAEVVCOI0qklr6kjomORSAIKC4Q
qDBdHDPw4XJeI375ZogKW36QTJ9VYix9TCCAaJLCkoaaQprGIzOwqRMJ1JuaHASqSJjy3y1wxTA9
RcDsYoyKKAlAGbd4xwIkh5Ty6NsQ1iN8wAekQNqcwNpAwaRwFGVqiIaODxgg/4p3qBUQhE6lfUuB
PkAhPoCWPuiITkmy1eFlGVkZ/OluFt72yakYakKBLmRzZlabGVgQbMl1jQehcRR2QB0TVcaWiGER
OZuDAmp/WmuyykwOPuGhwuYw5Km0ksuiHoEdnQGkmlPWvNYNjBIAuM8CDMaNkQD7pMA5ycAGLIAi
YlMDeA1+jZgSjM8GJNzTcIsnUCBlBgKsWuesHgMW6lIrzMYGuke0XUFj3JtO5MK0rmPetMksjlqD
xFrASIlShNQUVuxSRMLJ3R2bAN5jWWg/TMZkfQbZjQSuzqmLjCk2KejIZayuXpdvwI0LFoB1xUuV
2asJ6OEKYmaqKI7dnMB3Wv+McYzFAjjjJbAFuAYsBXgLCrDPPOVANeYGIVrnZ9Fml5KFnRWczVgB
yiLbR+GX22XERXIDt9FjIpijyIaUsq5UZXEiPFYcz67Dz+4gRUlbbnDfw86flKgEU/jt1eLXyuKd
4fFhAMDNUBaDIf1R5TbT0TCAJGlLIUTtp45FxSqJu63GsqDoDoYL3TIJloyYj0gdyuDZmYoKNoZc
bRQfiaGtNcZjbhxkr2DNsNwHtJZsLTjHOuZuXQou5RIuQrTb6+JGeKzeuyFquPWS314cHNSMz6qY
xV0sE6SgIVUoOMhZTJQDucGffwBEzaoJ3XXJ93YofkRC7vGX7SCB2Dwb0VD/y+G5L+6eXrGA7/xW
ho+IXbih7509yYg2A/gRXLDOrGoyzLAQsDkqauRhIxH1y92m7t2iKEYBAGGahqGIgqL+5mYJTMhY
jNqyHdaqLKWQTWJ8lhUEUk+iwAJgQDhFlHqoQAI8lw/iL4EJJjM4o8RyyRLc3w7gLeV+MPxhi02I
KwLLnoZSikqAXgvv7AtXh2oewn4NB1FkR9zJwtq5XfVWcVJ2IY+kG7ftYFCdgkvIzvlKmp55XhhU
wPMklCEgwAc8WgO/wAfOSB0MQATcWAUesZFFWgCYpABgAALgMALoMDGIVQ9/YBwjCQ10S26BwYkc
Tg1ITpn28cVOVrUNSMVd/1bNRh5RaOAB68Yc+wlelK/xmUTgBvIc+kTwyPKgCNwblzA6GEEZvh4q
tVSMnR8JIEC4MPLZAqxxjV54wOPEioJDqBkA5CuV8lrWTCol8bE/3AAGPA1hbsoIzM/z2J0hf4NX
pYBJBoDk8Mm/PKkOLFMlh8z8YMVybID/TCp18Az19nJjEbMbHOs2B8+SyO7sYKWZ+eBoDJ7xAUPZ
XW892nIyh0aFEEVoFLRJRTMvjQdDSKKDmMA7cUABLICSRTTkra0dtNUDVIArqsqpBssJXMA3WHMm
b26/mcA5pQABpIcAiBOJ8F4521YUaI8J8CU+FQOsDuYOptwBNOcfaNJzNv/CsaDcsRYKZ/m0IS9r
3010My+bKrX0lLzyJGSiHQC0TsOcVWPtspa0szC0MvAzOl0XXGRC47XER3x0SI+0xxzun7VzCqC0
SrsNS5+ANvISTJeATKtATxtZANw0Zuo0T5vPWZsKN9JrCxB1roCwClByLl/cUsP1WkHSBUB18YR1
VtVEXVNh8FpHSaw1wCa1pFWiKYH1WN/ebHtMWbsLtKC1Kqk1XztzPJ8qU7+EFwcHKZ82F8GABtwy
dqSrEBRAlTG3tiAZA6i0G0wTgjQnKBWAAfXVHTEfXulOStiRe9lRv87BnWV1X9WAUF/pqkkABMAa
Kh2AIdKR4j7CBi1NL/n/24dBKEeHdUZg92kHQmovMUltNVzKxWBD3Q4pdKhYhRAU92+ctxoT+JLE
bkXnUZ1gd+otOLXohwosphYYQK94QABsTRuQ2SNgQPYMiTVrCwK0FYz9sDVouMaESwZ8jzWbqjqy
IgJAgCdDwOdYzFJ5NCmzRfUJQG6JgOEQbQTp7xDATYyAhxpQXwgOhwGoyvR6AoAGmhLDXP6qSezE
Gpg+WGt7XS8kuFjwd4TURaCOTW6bymabyrDaybIxllf3HEWHrCZwzwVMKpajgAZ4wAEsQERVGsqI
OBEcE71yQHSPoIyjBFXuWAksXLoAgI6r47E2UjcRAAZ8TgKIkEcbHgDA/w8RQI0A9BXdIsUtHpOU
owAETManqoAHnkC9qvmBbq+eRzhK6EUcC28QOuIzbmR9ELCGWPgrKKWD106EC/jgGUuqw5QhsNmC
yFHoxXWWO7gEcc9TK0IEuM9apYFQ74I17wVaaUEaPXqDcSc7SYDhgHvXIsz5SXnlTsNBrQOseGQA
THZ6c8Pd9gAiBvt0oMgRkFkAlNE0ESb7GLhS/hJQCC5riwJ2oNLMAl39vVz3RXsBsrVSunLD2ztf
r3Kcsohst3rQ3TrGY0v0rgHiOIs27YKnCbZ1vU1BGZfhTCq/FMG+3ootBFfBdvK7h7IKtLEI0FNz
LIeCLQn3kBGmyICkf/8FaS/gxmzvDYjTRFx5wWgRS4bRCaBkxkf7g9SctMVBSuU5mqlDmZhDY2xc
6+QzbHK4zV1so9mtDn0c6YCsYMsuNUCujFfirU/dreCyIizsQGsTIyAVQRBtxRxOTuuJ4fiWF5hP
6zAod7aNGNz44YBuCQwSJNlNAqSkKyStNYeWpSR9vb6YIqCfQKWkL3HjRAB5GPk2Zgo4naYEiRZE
v23UG3uxHA1YBXfDm9XgstE9neJ621dYKRPqw1MELeVdIogRs42prNGFP2jjEjmjyCxzRlRazwAQ
5kQa9QtTa3Kg5DuGCCiKXDnB2cxN3ZTg95vFt40MJRQRrcJx+Hsr7Af/yOx77xPW9ple/zXEPwgE
wggEACAM5ykEpluK4zwPg+jm4ooK6GpiBWO9kUoYhMl4JN5vdrpBh6lVK/miaVM4ncvH8oGNz6+L
UGrGAgymmHRblqwqLDE9kkHnqOGOdTJ08+OXRPZmFqh2Z0UC9wXGV1XIp9dCE2hlaAUUZeIDk4ln
U4YDpBbq1gMQJxeUUhf4cpqHKdqiyCQaR9ipWCWWg4sHlBpWxAopyxK7VjljCfbqFykNCXWVkytr
vAoV1wRjFEouW2v7OcxYzCoF6ve7l71ZPNS4Ch7ew7uMBY0exo6TOTZcJYmHTcepegMd+Sjoqgg/
JcXO7UmHxV4mG+7u/1DDNI/eGo1NHsmZMy5jJRnRMuUR6MRdQopp6pEc4+lkuok0IVkS0oOcxo0d
dQySOfNZJG1OHOW8uI9pT5/yxA3rRlTPmqPRgr0QyVRVpHwuU/bzd6lqUG4DTXBckoMXUkSzajJ0
I+bp0qiU0F4DCm1ZU6RhpIm6+8RpjD0oubCrFDSds2zO2rZDpYOLlmMreYRN/GMxVLOi7ORZpfBK
ZSduBzDOnK/kXj7cqHirqC+qL8inp4hT8nmX66Wwf3I+6DnVm7yi9Y3zXLqIZG0vVzMzDpU2W0DY
zKHSLfhgdRLUtQUnilnY3OOCt3Nnfs0wachEer/7/XUoweHEv8QeM/+bPQq9F1pztzh2mHi4+PYJ
cFgFYUN6/hm3Cn2ILRdafGUN4ouCC94XmXVR2ZKdRmGlwxxhjXHYT1nVOKPQefstEsU4m1UID2KN
hRbbhizStCMgMTo40Iw0DlcQiQEml4pkTci0zHNsKaiLeUINBUOEkayAJIW5mdjkMWCouJOAdaHI
iVREMpHkJZwQ8ZmaYnqCyQ5SRmeVQ+GtyaSWFTIj0x/WuHeik1FAaeedyOX5J5ED1sORYoC6Iyg7
hQpV4ZhafQGeR/VhM+iQYLrg55YotClHqJeypRhhifIDWSigTsknoCwB6NGq1onQ5mZkQEfIKzdS
IuJW/C0Cix6JMnL/KUxpvLWFRMCShyJAuXYTl5bIJlsLMlcy2Z4ivYJUxbSfDrvdednaQgely15Z
iEqnQBStEUfcMtmwAgXHbVq+1WaGUKA0ckS9Rb7S1I1F7raGEdG2SxWDAM+TCxWH3GgqbVtukbFl
3NSgsK0WUQtwF5soB4zBHm/88MIJCpNCy6cGWmdGwpw4cBikqMwaIHgx5jKnhyLBUn7JVbfYYbCo
wLO5P3fMmnLa3PsEl/deUd2jPpFjWLtFgORxgV/TeDAVCl0tNil9KGv0x6rZpfHOTftiasgLG0PZ
1cy1E1DRu/q9DRUcjf3GygkDfbfQrGgScNu00JbjzEwXLjbdh6sT/7TUWTLxx+KMU7brFAmyOTky
ld/BcmAut0fx1Z17vvZLjv9iYdyTU94xwj/rFzXnm2sylu+UPUpM5BbL/WfGwu6+ekVF0mslzGnU
xQOLYBdINu9Y825TYVkOl/TzjecH12kasYgMrj733NDNzTNFQ5bUkp1M4yNNgctQ1pe0fu4Lb/8+
lKmGP+EbCDiipwxTdAN93RGb8v4XsOYtRj/uIt8fiHUoezRQDVBL3NvYVxl2ZcgUBiyagy4YuXYI
EHs4keDReCcvhVmDhNXbGvlyox0VNkIx/HNhRWBYm8JUwxqY45IJR3JBYGUQL6GRhw+9ox8ztUBt
RjQZEhlmj4IwEf9ASPNhOcIGP4yZIwCDqyLFiJfCt+yQhR/0IvXYF0YSfYyMVIPeCY0Xk/3xUHZP
hNPdgji2N5mBik9RU5gYpsU1crGNEjRP2WhBRsFwSHMp/Eoy6vYePj4xhY9Rh8zwQKpdEAt0o/ve
63AFDay87zDsw5zdQHkEQQiEYqMjghSakkniNZKV0/KkCH8RSVGy7kTQydJJmvg1GWWOl23JQywh
BBNSCsiWr0Nm/FQZNIZ10mK/LFosPbFNY8DDlBsTkyY3ycxbaPCXsDzMJKdBzNK4pZo4SSU2/5hD
uvkSce0UJiOkWcx5IiuTpHThFy2DHBDhiI7k6U/8ECKZmlDnTcf/WGcR8+mzeQwMOcHiTAzA97r4
fORDCxGHLiqasCgWqRrCmMMX33GPj4aDOFowxGlwBFPsrXGdKl0p0chDH5ItlIwNrcdD8WAf2pl0
fajBC5ZahBIgEIAABkhAIDBAKh8QwAQGYMABppqACJBgAhO4wAIQgICkRkSngoRownDZB9llLUry
hFTXXDod75C0eEx9EeRUp4o3nWNr0bnrlVzToXPhNZWoAWr/YmrTi9JoDEVjLJU6MxLE0scqeFVW
Yx3rV59FtojXrB0BHjBVAzjgBAuISwAK4AIHGAADB/iqVX1A1glQYLcUSKoIbYPQmh4OABAQorII
MFdW6q4YrQBO/33G6JP0LUKDbckCYGMqxLTYsHaySk5zLdnd6V3DSTQCbs8s0Y1FKCB+clUNR/Hl
XVE9V7zRdch0sduJaNxEuHOAAAQQwAcDnMAChSnACdBgJRSstgsU6II3gGaxBHHsBBNYgAEeMAMA
I8FfG9AvFj0qnfxacinZUA2otqQc5X4SxCWuLH9N1FfVgdekFjDZSzCMISXOBqnsVMNtzdBeGQfB
qssd8E2NtlQTmhhABmaYYSfcEO1+BQMYEKQANPyFNgBAAfkZxoJzkIBILrVOQHCAmRNQgfhE66sF
6OoDMKxhIbxksAJo7ZnTvAIMnNYABtgBBSKAgAOwpgALgABWRf9rFNQVRjsBoMAFHBBmEdRWABGg
wHrpBzQ6SzlrJAncMb/yNgFEOlslaMMiIYdojvFzD4KOq79u5V4YoCFDkUgzihMQ6WHcJy4lQEM1
GJAzjTUHylHW7AsUoICTBoAAaD2AobU8gQIoYAMdNkUCzFyAC1xgAqHkLF9PcABkQzrNgtJCBFp9
Aj4L4ABXpupqwrwPBCygAG1Gswke0NXT4jsAGVhABSLwAHRvWQIFYAADELC8zOarBA4QNYFXUAEK
FADSLqD3ARAQgQpcWgAQ2MBU3Y04+KHI2Oug9TmP5mWA1WE6osvEAkaggAOU+5U0eAAACJCAGgtr
J11zQXFFW1r/Hph5gutLdJ+RAexgd1doxB5MhgBQAXKz5uOBJkAGTkBvaSfbDNhWAL1JLaxu8aG2
4VYAgvE2AuRS1AAXD7SgU8GAVwygtkDocwAAbgAJTPUBAZBABqq92hVYIAES4DOwbWMU/zZg8UVQ
rQMeoAENnCACEbj2gqfaZKiPoLYYpzy6v5qBKrdHWAOQdgEy8AKpn8Dmr6W3ASK/grITgNymmMCu
6Qhb7wWgthC4eiAo4F+vy5ybLRAwIK4+gmtP1QE1BgCf832qEZYAAgFYPJa/4ABjWJ7iJJwhGc89
1TCgngFf58EE8v5li3aOg/DBdXCGD4ZZZ54WaJiqF+i4BPYG/+LCH28zLcPQZ0PkfAZAAgCmEBJA
BQbWBAvQax9ncLPmdxvAZTyQcwmQdTe1Ni5wAA3gXxDQAAA2Av4HAG+2bP9WeQ23e8N3AgkwAg3Q
OWJ1cx+3ABIgAZVhDwkwVV6XezoXBK0mcdL2fAdGAG1GAA3GEjUYEmS0VQ6BVm5HABuwAvhGgAIA
WwIkAGrHAjV4AgpgVSsYABaYdQwgYJJiAhzogWjlGYE3BJV3bUR2U7LjAv/2VY5AADNIbwgIAPR2
AdKGc8TzDzrmM5inDTAYAS2VfQBwAQcjABNIAIxnFB0hHWBgfDFQADaiQdkXUtzWAyCoA1c3BAwI
CK0FAFiVDv81uFX8lgG5d2A8wGXj8RUy9xYbIAbI1Tld6AIsuG4yhwu+ZnckUAENOAEOQAELwICg
MwQHgIMoMAEMpxDsdnNCc3Q2twJaJgNVlj86cAAdcWVNWFtbdQIacA1SwE2UJwCmyHcukAGnsVXN
Fwha1kIlsHiythTOSBt0B0lroQMVACXCeAk1GADIlm0TEHOagTKK40mAYAPOZmF1OAK0JwJVKIqW
UokiMFUu6ALcBg47tAOyRVb8BzIfZHuKk4fiUIgZWFzD8HJWMAE2QAAKsACUFwHI5VUE0HuoJ2sE
AGkWQAFIZTLVRyo3kFbpdg4jmHMS0ADsJmoJMBzLxloGUIf/CzB74NYAqSiMDZaBfbACH9cAD7GM
a4BcAnCOMkBumoh1SiAALpiEu5eRUPdvGEcAb0dcMBMzrkRpTNkGOYB8ZyAAmPgJmYcrA9AAa4AB
8aOLcMJ4cDJYXqCPLVWJeZCIANCRBrCHjckfFsN06qA7c5dan9BbL+GJv9g7F3AOukhWV8F+G8ln
58d3H9kEBhCSIkB5ADB8JjCbebCEuOCPQbCMNqCTBBCbI2AABTCHzkCDBRBpPIk1aAkDCOcDSIg1
RJl3aIlrc6llNyeZF8AAs1aIMLBbN7M1j1kBG4hbEGEBvyhqshMBJTCJkGke7NYFL1GSNYFsQTFr
/5gZDoMs/1vVW1p4Bg2SfQgoDBOoNADQAK0AgjNwjjBFg5YyZwHjjYrge5vnA9qmA6KJn6eJXpbD
Cl9FVZyZSp9ZXYg4miJQmjbVCKjpmhemB8eSbq9Jaek5m7IJM8vGEgCQmxTWDr35mwIQnMOpDcV5
nMqSnA7GnDYaGT7wAAkQnSIwncNRnVSlbdk5edrQnY3zEuApnpBJnuaJizmQngGwntymBO6JNVcQ
nzswn7YZCFwmlwRkBfpZjrLgjS3wn5khoMJWoDlwoCOQoESwoP3QoF3woGkQoes2oRdQoaw5RGqm
REDQCmPDKU0iIIHaWpjBUjZDHcsBBg8QjA7gmzBKBC/XjP9a0agl0FzJhELhQhUuwIGL1wAaEJgi
EKGGFEamQ5g+EFYbmAH+NTyWoG0TUJ6iJ5AKkJPNxwA5VwFNiKsp+gCBtwIJUFs2tmwkpm0L0AAU
EJ5r6gUPVg3AVwEJII0H9gphRoN8FgE6iWI8UFxkFAAI13jP6QJ8JgFx5xn/YAYHcKxAEJgsUJLa
tm3nh6iZIhslxhjKs601tQOSWq+1oCFv9RoHy0UH5gAFFxihVBv+Uk5MkhqpJFTYwrABQGVUtq/3
gA73x62ySXaolQe5OrINEw2/6qwxqADcpnMEwABJan8i8K2uGZY8wABbaWNJNxDZtgC4WDLkVRK9
1ZlYcC//8cpnDyBWHMQDVZYDFpmFc7YGeSdO9ioD+MoDgkYCX3kCvyqmaCIPc6YkuGI/0hGpmEIL
l8Ap5/Qh/XGf6nO2icYqMqQn22VPCessoPScIQIUpnN/ytADbfZmzgiHVJQnaestXXBb9mSA8gJM
WNtFWHkRhTuwiwaHwYQ6GDMr48O2fussq5ooHzS33ieXnDFhQ7S3jjW63iEJ0JUWGZgj06UDSdcx
5OIFudFAnAsKLde3SnUc2zMD6RhPjXJ/9CNdy5sz1yNdwesDD3dNWOa7inAzjhAnIOa8/2NfvRts
v0suxRN2ePkLqpgAC0BlNwtkdHG7EvIXUeYrO1Q4R8S2/wsrGlyyPaR7SKaiA+DIT18TGatbLSgw
n9IlGrJyTnBBqq7ROFRbKEyluVADKt1bLWLQlQiKY6AUdh+0KXLgwAFzexpqE4a7Ahn8vfepcwKc
OqsgAZqUSsmmCAZ2d+FGjBjAvu8JSJKAYt0rv/bCRvABwwV1QbY3JprlJiPRhTzMHS4AoJ9WwEk4
U0CMa4oESTuHMwhxGUiwr7ymoV5xnxQIbzPRuwhBCl3ZA4wnDV20wFP8EFMoZ7XRtI8VEosgpra6
vDK8okyzRaPINn2zk0CghRaACQMAbHHMDXOcUbZrwv80HvYCYcJLxLHHLpTFuDvJxt4AsmJoAMPo
A6YWCv9Re0UsAGk4lwdkZ3VzKQDRlltLIGgXNwLzKnktWQiM8ZZthwA2AMGyiTSFA4eM4X4oQnlD
WIX9Aw3apm6uQW8oRgIW4Mw4KE0jBQDuKARqk6nh5QigN4VjVQBkVcDb6gEtqQCY/MgXegJUK8kB
0FpD0GTcVsnVbM0YYRvaW7eMU75CVJlv20RXQHfBGQSFGCnbMEWkEGjnioGgUWcYsHiV9nIQAMq1
FbXkk5WqZXZRS3YNkHSuUQEOMKwzKwMfh8s4rAEP4JICEiEA4AEXJ859ZsiyoLsgO2/JVhLgCwBn
hQA5u24ZF5NDaF40kG0SoAFGoG6Gxp+U5szPTIDbGwj/EfJzgkJH7HAaDmB2vrl5G8jJesDRyCYM
H/eW2jDSyAaKaWd4NDAALemUXZx/YVCFQZB7rlmeFTCEAv2TUeJKmkzTRLNojbBbW1kAP/emGEfI
eWB9VGV7AEBkNrBeA6AB5/fCA02gBb02DVGWOkDIxJUGOF244NahNzcD9jgzaaUNMlyO9Mp5LUCv
mOwZTio0KOjXYMoCF7cAzSrT9rwEff1fCNefuSs1O+SXAyCvFZaKsXeuR92leHMCgF1oEOGptBVJ
dOcC6xWv3TwBb5mLwxdmULBg2UCD2SmcXj24EQcB+OZfKKDSsgWKJ5oOYWkCsy0BurXXBJCR0NC0
DZJe/0RjwjXqPTxwrf82hGHtA055ABnXB/7lrmMIip5XZwygAcG5tFVbH/xiqEAQtRAAW+S31rS0
nAcQnGFgf41AjyWggCMZCrRokdKIYq4B35DwldU2tjCQ0gQw0l3YQMrwdV2Q1GBWS2EQnyjAZ5V4
Alq4jZQXdT/2GVT4gRl3ab5t4XrmArFZan2g4fRWxVdYW3cJCTsZMHfom/AGj74Q4DR5YdIIbIil
iqUQBOCoAxp24mIV35qEHzexUOHwKID1wgFQAT5QALdTeG95oGgVFgVw01VMXG3mmquVSqAYL1Fi
c03AnHXmfI4SFmBLVYG3iNBtBYU4JssYgldgA42J2//V+SRbWC4AwAEoUMy9BwMa4FWvF3e6Q0Sr
vIxKgIc5gGcogTcsOAR8xikGwDRgewW+FhJZGQUAENir3FUTO5h2/m8EqmVoRVWqVWO9dXMFIHnC
4K4wEG2np2+hoOYwgAFoxYHEeAKHJwIOoDb0rAJTmAM/F5TDfuflAiCHtCdsFV1zjoF1fud5qOcA
3ue4zc6B3oUUnpqG/hKIfhfisOhg0OgMaHcwEukoMOksgGyehOlRoOlUyOmlNwKfHlNHkNgrUOpU
CAOobgKqruGqjs3eQVZwMutxKB63rg66vgO8Tt6RAezbuoqLU+znxwDI3gJRl54Yfdw3zWfM12ha
Re3/DXPtJpDtGbDtQdDtJvDtCBDuoEjue3nuXpHussPuwfPuBdM3WGQaglSjEQRM6QbxJAoRCAAB
ew7f5B2jW1hhg3Nx3czRxPGYjOa3IxhwXzUB1CcCw7jWDq8DR1lbFih4FqDVUXhuvCcBUtCYObDo
uN2yP0AKC6AAEeABkefjXhd6410CXekC1W7cwmBmltT2TjlVtQnGWRlWuumivH4DL8l5+Mo0OM/L
7TBrddZmYkjDcSibc/B2X9BazoxsFyBg2OhsMWCTMDCb7QruV4DoHEd9AJCeVwBg0JJKA6AAfBZ5
DQCKaBUB8qpnkSjnlbT3VRJdnVI0TbbOq8URXxnL/5EUdcYAYIQGisCO8VsSnLknRZIPAo94EEBw
ClQAmOu5Cm8gSAVxDCsLVEq8jw4IwCC3ESBPhAFAcRruWILoQhEhEBjIZiETgJwAG4Omaoi9otMX
heKYtACQjKSOniGRRR2AkPgVFLQEwO0F2hCcMKVFPQBMATTsUCQJGERFBBy41NwcJBScWPQIQr4I
uRRsbAQuENwJcHAg6FEoQCAgNDTEWGVp8BLt5aENKCgYkEUhQAQaMOzk4UEOukShMEYPJqHs7Uxn
sEiI/gA8RDBDjBcFZh88TkwoACQcI7TnsQQYhOpfb/HR1ieBhTQ60hDDM8PbtyT6ZJR7JCVGkUFR
pP9cfCRtSzUdGZgl4hhQ4kMLDqxV0xijUpEcDWPkGlQgIkeKi7IFmbBghwUGzQpo2YGlwUEGBrBU
+GPiIkcTaEwEynChi8ppCwdUoPBgk0JfEBjMCIPxUYCWFtVQi8ZNJCOxTtdkpBYWhgCGbzGsONmE
mzl0CA7YZLKUhaQdgug5UPBqJdtreN4OVgugwCZpJBFu1Gj3rYuDDseSrRg5I9ONpkY+njaarcLL
mFeqtKuwM2c1UsoKdmtOyIHDLLI0e8yi38s1ANGedsi66gzNLl/StiowsD/ScU0/vJj6ONqHNYmU
m/YjTEJ9kPRUHJlWIl00jf+5h6t2SqXMcVSWmzL/4Onb8eQ/NzdRenHZpgN2Z5kXn3wqVWUfI5Zp
BJ5nlv0XUYDo3SeQNu2plmF/KCxIjEZWBShWeRLtx4d0FYZ3HobqpQVXQu9Blxof+fDlD4B4MIDB
ODDI0AJ9eQw4n1og2ufhiCc0gEEBycwXFjGwZfjZUhDOZtEdQtI3U5GSTfTCjN/oxg0K17knXoD3
WXlli3yR11ZzRObW3ZFqNlWmmetNtJJ4VJpoJV0qwjloGGcS8yWDYf65pm5LroncXCqOOIgGGvTo
BV3V1aRHdX2qVcSUrT2aBAMMNLCAM9GIuYWDgn0TK4VAHgQDp1vMVNenE4Uqqmm1osUIrLe12uA3
/0xIsOugbB5qK5suwrrCYU05lxCpMIo1LLGPjWmCtpQWShZtl/Eq4K4RCrjfjP6Vlq22sOhHRJw6
OHBJDBiEI9CN+GVnJ5HogXhoXBMcJpgggj3VqVu4RcFEDgY2K25Z+qqRQT5KdqqHHgELHKwOsCKM
EKPXDFAYESw8DAACza7QgSIa7ntxCzuVG9vGHI8WJso7iJZwnwtr6/C8tBVjW2TnPXBaaX2qWxfO
I1UqDM/EZpTyHQnEiQGsr1hQkIHe9QsmnTevsYK2ADhAjWjCJI3APCTl2McNCHDwNhESLKCqE0S/
AGvZYiVbQAI0B7BLAxCUgIQFIohQ134P/33y0v87o8zExS5mEwAUFz1MC8uUvDzWg2gLF0AJRsb2
uJhxnE2S5JWjS03cE1f9X8RFbxgoAJWFXS6dqjcXxtoavl4RtcLPWwJ5RAlGMEFesxCBX8Fk8xYD
WBDUtDGJJWL2sGmnBXICImCROAARVJCFDnnPXTeTEiRTgANYl71ktCnVkUEBCuwUwKm7QAAMD0gA
ARlXl5vlJgAKGAABFAMqyr0uP4w6CAJK5oo0WC1AfhhF6OLwoFCcKQChaMAzVIOFZ6hrDxMT3nWm
5kIJjmwpa0MexOpXjPtlo2yRe0mfDui0FX5schAMGbAyaLo4CIB5LHBe18QivVxQTzc8wp4FtKf/
AO4J73vUEh/5sCAR9KmPBewTgvsKBz9+zC94hsJhGvK3v/7973ACJOD4GpfC0J1ggQ08ncxAxqqx
mEkfFUxV98wWJ0hssAIdZJkUQBi8EZYwHydkQAofdpPXgQmTIQNNjrxHJnnVEImKYOO+QijFjPnQ
kvd5V/heGCSeGUgAMxmMBkZ5ATgE4CRhOMAB0LGL3e2OANITJAIkwIAHpE1UFKiCAioAGBcC4ALU
Ag8LGJCAR+RiBhrwQAQsoL7CFeYEHGBBL0+Vl3zcaJHVOAAGIHHN3R3gf8k65jvNoTGnmUUABHAA
MgsAAQZ9pDdT8A1ZjmCKQPqyAbx8B8oYSoxj/84Pd/5IgwIKcIE2GEYnJATLDESAAAKQQXsMmwIO
ZOHALSRgfhFAQr6k4ARJLiABigxI9RpgzFPlg3EPIMrE8HWBQkrhn8uYzKoi9S98Wg6a6OLZegLp
GBbQIg5/yANeJsqkBvzllwsVAgIi8BtqOEIfFqBAIChQAdcZbKnCQAI0HHOGFmAtAMMUpA56GQEG
jCNCbkFndU5wVonshAABjCeqWKABAwywnm/JgVkoUAImnO4RzswFAhZgiYwQBSDYeMI7TsBLTFQI
AAaI5YI6UzgCFCBvhikFANoagAE+gAALuMQ0GGu5CHDVbYnDqwFUGgHLRkGXSBjcAixAQCm6Bf9V
p5KABoabAA08wAAW28ICILCANgTpFcugrKpoy6fFjhQSw9qiuuICNR3ExASNgwRPPZgFn/zlHQqd
CBTox4JLTIICoCgABYIWiX9yZAItEUBQrrEyNJxVhMTpwwrsdgXXJghdjAwA1jSygT6oARq0RewD
LACfvg2AAjybxxYo4a0KXmCqjoitmIJ0AqE+4pc7GAKw8DKkh0SHSTKDg0ZM1tvxEQAKHKuIF0/m
g/NlAX4EvIIsAVC3QTjAAQs4QVwDEhEPHDO6yXqtUwDQTkgoJoAiloEPqIGOiVzAPKSZzfAkN6Q1
DDhPOaxfASpbAAtM6axKq/Ij5EumI/sFAwj/wEAUJqCQArSZCbuoQtdO0hJeRITBL8gEUR3AABKA
ULc3uMJBMoGk8+CYHuQRRAZ4KdgDeEAAWn4SYh1jpgG0FAA7yQMEAILoAeTqARTGsQxckIgW7IIP
R1bRysRTrmaF42IebsHmwIJIHHOjCAxFGS0E0EsC1CEZA1ipxcaJ4/ml1rTilgOqLxXd+wpJC0jA
wD5n4YVBzBoSf51ZQzIy5OFZ7s3e8tUd+uYqU0wGtRx76WkElwASLIAWJmNBmc+Xjs2J1qIcICtu
bjKxRQciCUUYQo6ii4vDicIkD7h03yq7gOvBJcoQ8ZOcVRCGpAlgsIJdjJaTkRYQfQMCN1kA/8Ik
kQcDsIMFlAhrR+KwCWAzDwkN5wMuwFCJDsmgqirxTQA4sIVdLDSsxfIWNGTwDgKrRNtpe8WUowBC
B4Q7OzJg4Jt1LdrxGWACZ7jXY8Agg7LnQcTf0K6aXW0Ks/QtdhrfD3PqQ59Y9brf1wrEDQggCUjP
uHQBmPdwLEo44wW+KRqf0ng8vjITVGDeARORKUab+JWz7EEXw/k2SMMRnpNltBXRBQTMirUB7Je/
Fe61wE53VcZwXO0V+MBmW2XaJmUgXzE3RZmngPVpM0UfjuCGzlt76SvUQYTzI0A7O0OwK4ICNQrh
JeJ+sRTYFmACpsoABlLVvxeYPqhyUX9yvv97GstlXmFNu6fhGVQrjgVMR4QBFLAXCjQQOnzAd7nG
wwjM5fDfrARJ3nzMuvzbYJxeq/jHK+mLcCwKgXjLK62A4y3ASukBAQmANGWgi03gjASDSPCa4jnE
CxiOlUGbiyggJPRX1C0FHfASMdACYADI9+mFW+xf4RxAABmANFlgAExZWPRI+5XdC9SSWPgcJJwE
KrnesbjYohyV4fUfufBemjyFBnbHCzSQFdSM0XwgrXDhA8KGQUxIo6gGwIUhNhQK1GAEBn5HFq7h
kgie44yJCnIG580h4kFEi43ho+TOp4FG9O3bvCxVFzKGRRyKaVji4dHDMSRAIYmhWFRPgTD/YiPC
jBH5Dv/1h4JgorjZ4WaBTRZ+muy4npm02NcwzbpQoh2eopiYmPP93yqy4pm44p+AWizy3ly4TqJg
hwq+4ajMIR0e4lwk4jTl4SuK4p1coOvYTP/BoXvkorFNgQbIw94gYvEJiQYEI+dVI3M8o7NkY4Ks
BY44BkTkxpY8hgPY23xo3h/90bWwYxdCBhyGhTtyw3T1WTx2Q0NUIiZeAz7uYdSQxYdM4TEe1T9u
Y61Yy+U0wfu1yjwmpELuypTUDE0kJNEgR3nh3Da+yZ64ikEepFMYBNjxyY2A5DFamQvEIHnMxwyh
00E0Yq95CRwmSNpoh5WJCAJkxW0spEuO/4vRiAqvGV+eiEgAhAMtkgmIMKALzAO33FwI4mPD6aMF
mkrOoAvhCaAd3txORkZvvc3K/RBK4NxWEuW/yY6KeEbHOCJZliVjyMVOogRcWmVb6EMLDiVyVCBS
xopSngs2uuN9UGVH/GTEvIVQPhVDqsxRPuRhGqMiihdZFmN9FMcaTKUortxVmkBWFmZ2RBYxeKVh
gmUMdF0LUVNZSslZalZaJsYL3oxbcks8EmYHWkhdosRdykUdyoxqGERPjiZgmoBgTmYP3RhrgqUn
emCspAwlImcM5AoDsgAYOAVrVaWdLMAGNEAE6F2kTYjSwBVBBMISWaCzVYI/DAAuUBZRLP9FgTVE
PHSBCq0AfQrHcOZSdySOrrBmrUBRe5nAQs3CDszDBdjjIEwABOBLdlRnxNhnJJBnxjmNoRGAoUWY
f1KYBRSABGwBQ9EBwqQWBTTRdgoAFC0MOyal8ZUIKH1SY5rAlKmKgMnAFehEtWFj9cCjp4gLZkYl
sNzcYcYBcUwBB0DMX+pAP8SAI9SDaqXEWBxZEuUbzohWCoTe590X/DhAG8zDtJjAOIiIP2ABL1HW
QQSoPyiAGxDMBVzAwwgBLlCJ65DhFAQFhswEHhTEDiScLgzG9mEBByyBrIHCBUgghaEd9xHawhgp
SBmFGG1A++1CdsYDFkzLhZCJl9pCUCD/QgOU6COgzzE0UwjmFpf2wVa9zhtY1Ck83KfQlD6gVgFI
Qhi4Aj8EQg4QkAVEQDNMmYtUJQ3+W74xhifS42FKI2nQlhQAlT51g66m1CaKQ2ztD//wmlokCwu0
E7FOymQYwHiiD5cmg5c6gIeh1mQIwAJoSoewQAdcBMTZTdnIj9fkag6gqVDJ1UolAH6ZgN3dSAP0
CARAGq5VQlz5aXgAAC6FQaHG1iPAqQkYF/jAmHXsAAkkgKe2R2YZA49F1ilGgemtgJ4dAgtYDBP0
UgVEmS6BVFjQmAIphh88FtqUK356QXzlQgBR7EW4QiDw1BfwwgncWpENxyl6qJ1oRoO0/wWAfFLO
mt0lwEEFeNWZgGwtoOj8aKuIokGDIkg1VatBcesdqNwW4BIAnNEZOYDJoqsgrFwU6N2MRcGv5aEs
latwOc07wAov4dY+7cCPBAStAqzA8oK9xEAhrcCvfgO/cuUA4FdUVq1iMa3KGEgoDAlPCUAEPIdO
1inIAsCydaxGXNrJVkATCtmK7oBX6cM74dq8vkGajSAQku7jytqtHob/iMtiYMHHhFOSfGKMCOjT
eaKjGCkfNpJooU2naIGYtIQiico/zcUsocxIPEO1PkLP+MkRpQHhENpg0NZZvYL6VUNaEJQ+YQT0
bUGtqVpKXWERqEBTLtTgQgLQ6cZbEf8GLxQqErxCGnQPSfCrCZhuW+HHBYiC1QrvFpjuI0ADMeAF
0KrQgJkHMF6YSzQoCVYMsf6s72kOJKDqtGGBCKSU92bFmVqH5uGCKxjF1UlDSIiAJZkYZ6zJc6jh
9BpP9YYawPULXUbKPCQLHOCIurFez+JeggCw2rhFmSmQFOQTNszuCQCXyqzCBYwrC8jUFeTKi/ZB
OApaakKcRmDAGCBW6D2G15SFAESZUuKpMIgFD1tfH1TEMU1KBWCVrYRoMkxAuTLcXp3gAjRA1WbI
6kQD5YFqtSqAiCrx3yjCQYFIExuABORLBUCIly2ABHhCZXCoCQQoZaUpC6yCWKTNYbT/wQ1EBkT4
aRSoWxIRw2gR2DFhwfxwJjTCkh3fyBEbY3bQsHaQycXYwiMv7hY0n3ikmbcI5QsYWlO4cK6kazQA
HgoY2kG8FFRtMZzywR94VbIuxawmMt+tKIzMAfwY3sQ5Gu5dk1ny63O4LjgF04ZSBsf40+o8Mvyo
LT30h0ZYFAQU8CdzoAAQ39tiADNJg/mSDOGZpQA0M3FMlZW0wamQnOngr5hYMo3JQTYj1h8EwsS5
wexWJUfM6iw41JbZ7zQcQBc1JSIKsUzShONsgwqWiHiFDZIw3ADQjFrQj+HVAfOSWAtQAls8B2ph
gdRVCzAHyd4clJHuZsP0DuupUBlS/6BMLYX06BASqK0irEBW4RUGZG8vna04mlbr9R2hrCQ0tWhT
LAFRuiO7DsZS27RFWonjpMiE8bHmVAcEbIA2P8KTEFAFJFBFQ4J1KUCC8opVlOlYe4dNP4d0GHNa
j9taY8gev2VTcomH8TUSSEAv0+KmqN0K9EauWFl6pB5Wlw4PCXNd1zJ9MPA740meeJGMVO6MYrQC
TNUrW9xV83GX0fNWS01Kz6FiG1tjFyl7dKBdCjYMW9wtMqEloydkhI9n/zUM7yVASAO7xpKbfOd5
XvZvm/T9tZkjAuI2HNQ7RhqWDOdNyowRh9pk/y5P9h1JmAXFngcDsx6S9LbOwLZ3dP9GX0/vtXoQ
CJJ3321mdYvNR0PdJRIlodSyWfNuAgELJf/pHtcbWun3dNh26VBgXHpGRcf3NAlo5owbzyw4pzQ4
Oj14b0LGh3BJUxH4jI4EZ86yeWf4WF+3Sn9IIz9Qf/uHfAvoWUAmU5X3vghDihsIf0elfyMHD7Fw
iDPFiN9iw+zlp3DEeVvHjpukcXb4j394bbC4MdN3jVdO6yDrhiu3JcZldoe1kKsBkdc35/z0alx5
zsYSj4sEl5dGdmf3hFPLjMuJkpi4keY3lmu4P9+2j6POh2fJlIM3jVs5XsZouSj5mhlxk3M4m0M5
B17Ld8/3lFr5mdOwwCxEd5P1JAb/5zTmUEcOuHbO6DlGGEksQb5Z1VJ0Q/39taZ/pABSzZ/0Cqh7
0DmW+Z2DoaUfUA2GuHGuBiEvqU1+N8C06Kbv9UkLRD4ZIqr70HF/WmrkjK8vKdH2igbaZcPkgFyO
OVpjtxfa8ORYeHs4oOJh4D2yh2bpRqk3Y33DQHoc2JNPac28QGohAJiaIBLksuJNIaT7tXEq4jDc
GFCSNFvq5bB7+3iDewEvd+JB+lNH1Qy07D4YQPuhTJDFF8Jl+zGrSW/f6WmMd4yVacIrfFNNjSmp
WmUzuf0IgAXwDx4nAaHNO+UNhAQImn2Du+wgAe0FgtcwtWhpHVWeyBSEg8UZh8q4/w0Bgfc14waj
xw28m468J4XN7XwP6cAUOnq/8C4M7UwIKc2OM0fTqAnVFHy358Gy/YxTumALfBYkuG4yJPICMJRH
bZV2dYynRNuTb4md0Lys9XUjr62Kj/xcQNdWpB96VRC22cSoKsAFmG8AWZdZ/ZXi+0HEP4RRVgAI
oSN9DVoAleoMgMLJiYAMHkB1/QxSpE/0eAcvFMDI4eo71UXFxxl7M0ebH6YjTcMS+98Lpt8EKP5Z
8O5/CPU/S+f0JoSvNLsfChFNUaNafNRWKLxVpRdJPQL/kIcnnwxXFOt9+5BNLLdlONUOCOxHKU9V
Np/mldbWsffLgAjWKsFSGM4B2P8UGhgA+mRFrvyFRqicHEQDfsUPAnSALRQf6YEAAYxjFJxRMi4L
EFAHQhQtIAjK0RDweQwDV+AQYAhOo0JgJOggDqbTQJBQLAy3pe2oJd0EpGVBeDpSBIxGY0sykB8H
AkFCOJCZYHwBgkBkAwUOMQELEHICBhgjAQgdFFYLfw4UfQFfEAEYUCcqJDYPYZ4nlgENXzcAB3EG
cKNleUsBHR1aAggjCVyWAgujAw+jR3+LXlN/xqZxWQASzRqgJHVqDXZLGwUGERW6pzaei8F5Ll9S
QaMSu0NMqhFABzcZEwWqFRSWCEgABUqM4AlLDx4YKNDIQrAyrwA4GAEEQINRucT/Lfm3RMAYEgW4
CDA1BIg5CwD8HPGUZ0CHUwEGqEqwB8uoMF1cxcwAroyFA4Z0MBnB4A2cd6liIflCop4DAjIICMC5
rw+CNGoSGJCQpKACK1ksVKFWhgCEDBgamNDaCRAmmDAtvQvHDsAAg66IugBgwYKTtqnIqeUyQISQ
cSPxMDR2xKM0ZUUeNMvwjAQDdhHsAGAgId68dBrBiDMXDtYuvpzdkIAmQI5bwlQ9CqhwQoQUFi5i
qGGAKYCB2wM5fCDzpwyAB6cGYBhlQe4JAy+BBwFwAcwJI6XLAXATASYENm+7hXwyIJNzKeDS+gZA
M20CAqMkb2EwZRSBgKrIvNwS/wToCTXRU6q8xXOEaCynDZARGAtQIBUwJxwlxRoB1EWCAsGEUhOE
caUCBQHtxYXKCXVZUMET7wwg0ndYcPGDOd/UggoQcgEhR3emTMYAbnQsocoOFeQIBnrRHBThFjdk
+ApKejU0mUAGyFERA9CxuBEDSD7WnQPfmeZWDDIsAMRtYXBgQ1xxPePAVQhsIAAQrGlXgDEBROQi
YO9Y5EsE6NWBAI1ACmABYSSocgAD44HnVopAaJFBF1y41BpRaJx5JnInwLcImxWd2VM6ligqIBEj
+KXEdF8A0ZwAEGAAwTMGFAqcEIoAkGMFACyAXqGiMHFCRjJllAqdxhT6GS4JsP8JwQ3q7RJJFiei
WOspZxrjCYYplcEkk0gGAY1+JgCgghaQIhROnlP4yixK5QRRwQMMVIfEbaG2N5AcDTiQ0gWWuABB
bct1mtJsR0WWVm+McABJquGK1s29BUqQ6igKICBwBB7ckMDEGEiggWgQLODAxkPdMEdESyy0X203
oOPLNy7QqsFcYSjFBT/OhThFugE5oJVmwvhyH2B9CGDmKBGANIJkRARA5SkPTMGfWyYPwEG9ATQ9
gBt+6dcFyy5woFebCVR8sWr5EnUIKRJ0p0FP42ygADlFGymKikG2RwIG3UWrjivsKaSVAfcq0F1Z
ALj2SoXBsBi2MMxO6jZMEwf/JzcJdSeklzYJSHCdfg0wMPFf8unyc+HhdgfkEhlTcIZMChiSwxcT
sxSABvm+DSQBBB9hgANMDrKLAlvkQ+gUF833NCm1kYJPs2ioQvsyWWwthzwFXNBcAaYSgAEB7YxA
lUIuaJ5AZAckPUADCEAwI6AnYIJKLqPctpDiQYYHQPG6TIyNJWCLngULzdvzXO49O0XV3Pa+lzgu
MIqIHCN0sIMEAMM/E7uNln6RAAvQ6SK8ARPomqWFzxjHIyjjRETiFhiGaGh0AaCc5VI2Pu9xToMB
+FwZDKe/ZZTudK5IHQFWJzH7vS52aPkC7VhkG9w9Bh+7693VwsCi4OVjeEeg/x8j8Dcz5ZWoUp9x
DwGgJz2LVO962WPGCBZShImBT3zkM58B0BcA9YGBfce5HRN7JT8pivB+zQodFvknDP8VAYAj8pji
SFDAjpFQCwl0xRPUQAAHciuCBpjgAyp4wX/BkIocBAezlhO/EBpSI7+qG2DwkJgKrA0cdBxH57iA
js4ZLh+Z8ZYr6jYuTgIxiFuz3RrRJwRUDMMLk8JBvupFMgEM5yUPwaSvvoQpUjAsAfIQoKmukzcA
8E4fI8icA74XgT+k8TaFoskuuqkLtMGCMMupl8maKZRdvLIitrlim/CWOw8KoDpMWA7t0pInb/nB
LUgYwo2U4juJAE8BFaCTZ//YWRPkRQ4wwSkGyjhHpMwMahHigAUwTdjJdtZLPprEmega2suXpASi
EbXBLYmRJ8Tt4qIY3QnWvAHQTs7lRzLpJc7O1EHf+ChlKA1VPm/JqZZipiRhyAMipuIXmtLyTMSo
EEiHRJ+e+tSZQjBHLW0ZuBDioXlghelLaYqokriTpTh1hU6rCrVaSnSihgwqGIbpBY1+lacdJWVU
TYopmPIGo0Rpq1tVOtG/dMOeflURS7/anbgRYxl/4WtvxDoeiKpySEKlzzdAAcsNjUusTIgg1tp1
1rmQY6/tHMYwcWoc54wLqoSFa6Vcm7jVCmamoSptxzo41b6yCLAiDcJ3UJb/LRQyiiFoUSVNgVSo
ZRgwoLYK6C/dFiGqkrUbGIDqcL3az5ciVUIfRQUemutceAoluoCZz2pfmpDl/ip+G1oiyyr4B19+
l2XjyWge02FYLrDMv4PTQuyqO9br2le7nEvRV791X/wqlSQcLK95/wvgX96WUZBN8NAozA3NIBe8
D05qc2Uy4d3GwsI7IfBYxXuKOMXEdxIily8HkwoHb3Qc5M2pfw0bUIddBW15EcIhfmOACyiAA2ZC
RWQQsIBRXQ3GQzuAAo7GhRg5VULKlUjcnDkfAE9YWyiGB4HlwuIyvxiuC5bch9EaYoyOWMcBrYV0
dyxTII1OH4iLxjcAJl7U/wqlzThu7HeGYlWsYgrDhGuvfkvTu+iignbRK88WFrCP5qQIPXHOKC7q
QoGn3qGEPtoHC64AHZfdSgmlEQgNroOKCpyHyceCZYFlVNcTZLfPN81HfmFiTEGDNDABQI8uTFBf
nNFrzCyuq33ljOs962LWVu3lbQM91ufWxNCTTS6EjaYRQgJgAlaarDjQmmk2iFi4IGUZ+XCj6974
8oTSdsw0Z6BXbhRAASlQwAU8oQPLSHqMLODHWolVAZvVpSG8S90GFiuKCUwAosgRwEK4cJVMxZsE
DyEBq5lXWQcE5DGkrJSC1eobXGeiIYPmbRJqUo1iRzchP5Lftpk5bpTpZf+54ZGsnd2M7jvMNLmH
lp2dBTABm/HuozNyQAHCfRvaAehtXLgFNVwmXtysSQDA6Q0RdDAtLnWw2Jl7T0U2cJ975aECOsAA
BhYwgWWL4pougBDGGyCBfRjBEwlwAAv4+hkgN8gjDFAABfhG9s71KKSWuPsRTMOLP3uiF1qI0Wlj
Op19rBGYS8tDT9ilViglIE5t8MoGCPNsIbB9AnAXwQHo60GCVuQh+yjA3XGhd0oPqNGA5ee0cY5R
yWon0Mziu8mB2wXOCBcVCig6rIDEJC4oJXByGAi7JnoE8qk9Pl+gNG7aTvWoB04ZBNorN7iupMCp
PSz3GkGn38AGOgPgDEz/iIIlMOAUBYxh3O/TxV+t3KYgfe8SMWFurpFBf3Q7ClB+0SdwJMACEBAB
FOAy6HVbtxEhN7AGwPQALMAKunCAUAIH4vUecUB6v5QYBfBwQyMHq8can1Ed/lV/9lceE7Mxo9Z+
BcViFCgXvPdyA+cZjhJ8vIWDuVZfvXdSbOA/X2UwRrMEUEE78pCDNkAAyRQA28AEAYcbArIxVLAR
FggHcgAN1/YHBpB2RSMHzzc/95BeefNu+VBBVvAErlADN3BN4vA+zCQTjZIH8mIJKngDbhCA3lA1
YDIVSccxRbADffhSGXMBDXh8mtFZYMB5vmNlTPAeuNA7hZBMbkAURcNT/x6EXz0hDuQDNJnBH1yQ
AZKIapx1BFdxfMx0VzpYVzdGEiRWL+I1Q52BX7EoE/pTUiBELDt2A23HBHkoAdMyAyZYcyOggifQ
C6gQSdrnBgPgcNbEaP0QbF0oi8GAJFhiO3WVcZdTBmXDivqnLRbQhuRAJxBAPpn3iNgoE8TYABhw
DUDDSQCia1vQCUpkCRPQBVgYNeNVC/SSMfoxdI7IJb8kAn3WVLJIASkADDtVDUvASYGlPea2Ml9C
BLpQA1/iF18gd1RRBhuDco1YVkrlfsuFjHVYIbUYkRLpHOGBa7qwiwjRi0vxi0SnVMNYjCVYZ56g
jITwUs6IDdAojWvjGv+3YI2U6AVxoY09YxvdSDq8EY40uIbluAAjkkJeoY6wKBov5wrvGI/8kEL0
uF2Vgo/uto+ERCX+WFVMEJC9IJIjeYSZuGMIKQ4KqZQM6UgP+Rct6ZJiJF4WeQQYOQoauXhf5ZG9
FJLiWIMlCWWaZnOziDPhYSQT2V/tOCjxVRgoh5C+szaa4RJcOQJyiIzdNAoPIURzmARjsDadcGQE
sDFW8jYJ0gW3wGheQDfzwwd90ABv2XO/1JEoEQdhQVNfcBsY9GzgqDD7tggqsBxPd1OaoQD4OAII
Inf+kYlcOVdM0IcQQC+UGYE3sDF3pi0bRSUTRREPgIVKxR8CBotzEQn/NGWCQyMFJ0ABJKEeNoAA
QbABCjMQHINyETh0GbZRzdaVarZYEil+OWiP3uAtDWE/O+Y/YGAKpXEbFsMAzwdlXRV1wYB2tENp
6WMI93ZK1sQBfQB3KRIpG6MASYILvqMIS1AITsERIhldCBABNmOf5JJUdyAQ7dgZ4/Yp9dFntSCa
9iN76NNpSKAG+pKiAKABzsFk+rGYHcQ/KAR39YIP5zlJDiQvLdZIfOmepUBpekYCSKQfBsEyPGKm
c3EBEqBquFKj41hy2XZZ8mWgnVgTF1WLsVhYT0YOy+EAmZiiOxV9TMIGUHZ/OxIXFUA727McD+GZ
KlegMJGeHDgRkFU1/ymSBZwETDGweuEVVuYGY7O1SrgmXFj0g3kwZbixCMBQN5XgECUUBn4XCQNJ
nLK5U4CgX8OjYK1DER60esjlX5A1pnlggSMAoxChVraqcQzHLoUhUzVHp6IaX0+GqBrSZyiHRS+J
krIoCpPnhNJWUSl6rdaKWZCTTmplmSjJF9k6q7OaXu5JqLpaoKRqZ++6GddmjzMGmXbTGUs0q33F
k1A3OkCoYaaVcnlKWfNRqsgYk9kKY7bAos/gkCXkrdSaZ7K5LAu1sBeVU4/lYRCGe4jXp0nll3MR
O+P4WB7lserKd+2nYMQKpN4Vr/xlspbFW0DkfnJmqtq6r+fVr6FArP8dprEDmkU4O0oqp7JQBk/y
sbDrFWdDx7GEhlnedaJcebPiyl46u23mGmfoCjn72q04NwUBmns4K5nf0BAqMmCxcLKJw1GugGqB
AWg9Kz+holTzgbYmW5Jryxn5tLFf91pyS2J1O213262OopR/CpPUZ26ewLaBKzuD+1kAxWUHQaBY
BmqztbitCK7j1q6Qm66j5bYvRLiFa4dFepJhE1BywAD7kAEXYDCPq62/giitGzJz9lp4NQpspF84
l7gGZFP6N2d7ZnNqK2h2BVt1GFm8GySYG3PJxlICO1tMe17tRbA7IV5P5ZfM24qZxrtvJlWCIRFK
iUvEq2snFroPu3P/ylu6jJtzz9u7hguLJYluGhEB+jsDNOBEAbtTl8ungdtTCEJ8cVsLyPpRZAU5
FYE17YZg9TW4Qqds2JG9taAskQVciCPAX0J57mVCDeqH7oS/CHGy2ma/c/Ut/yW5GWzAOHi3CrzA
l9ugWHZWI0kKfLu35bsi7QVLymJSLmwctsKjMgWkN4wE/yAROtx+PLwLU+E+0NtBgKNTiGVaRYWw
fOlrvlO5Ntiw47bETBzAfBrFaNFT5KAdKtJTaEZe8sPFarjFSixf9nUaPcxc6uvARyXExaqhLKnF
KhdUKfl14uFsguFpIStKd2DGGzzGO6ahNdUNxasu4tAM+UCKAmA6/wvAJHWjMOiSdEHCJPaXh5MR
PfSiNa3Xwbiixl7FxrMUkfYUlxKsp4RsVr+SsA/VwuFQy0SrygpGXoMmOsrLKFKrXD43sptRx7ml
xuoLVjaIe2Dcx1xrN4+MaG9LzMX8VU5lwWxVxoiny7PFy8WQp3JxLSRAyUiAkADAAaZDAZmMPgRw
qP7xhPtwFQL3zqRcAKYsBoITbMXryCxJpHERzH6LX08msTGrU4yMyLjYXyKnVl52p/8M0LYozuY7
U+vqDUJrXW3rh7jIPNYKvs88GBJti78nwEu0twDMg3rMU7XS0R79aQ+9Z8GMzb+xWOa8BOiszpjM
JK0Bz9MhzyNaz/+wKz347F9LRwau105r7Cz7ilfaYdIFfTWSqdIJvcXk1mjnCtIQfRovXDhhS6QM
d9FTzWsCDL01HLKl+lwexV1OIh74s7AmXa7AdFwIrVFmDV4hOxIfPQxLDL1PjQoPxDJet4yLYAEc
IDA0kBpGs0vVAGaic00NYs9KMCDs+B0tQHL+zNXI2CtVzMFRzbHZXMuVQis5N7SahtlKvcp8Erlb
9td4Pcgha27v218jlcixDUwwe82TydSs7dR9FtcbS70iO9O2XNAufdrqm9rFIGgKvKjtZCUnANkf
kCNWQAFeYoYC0Aw1YhHQe02UZgEUMCMBcAEDMiPm1gt6+szlMMf/y51FIZbcuseug3G7O1XbKhdX
AJ3IS+wLbR26HoEZdQa2sN0xMvW+dGrfvPVJo7rW+83fQjtUR1XEay3Lw5vNhyVSVp1r2LySSt3X
OVaSChiiD8Ia2eQ79sALsLYAxFgy9GGCl90f4+0fiXMWbczH6/17KqW8tLhdxbyupLpfn5VZwt1f
B1zjTVsuON7awoCv0aZ7TRthQf69/0XkaEzhNq4fOJ7jQRdf1+bkPy4uieNYMQbTaKzKHs7cp/Bw
uiZqF7Ci56wGCFABmUyF5QMBnlkadj4B5D1GfJAAFDAs+kDU44KfaPYvPZjkYN6JDXtJMUWSjEhm
3IVzqFtYi9UZ/yIo02h+WIUmS41eVo9O1wom6ZZL6Xj8CiLo3zqu6UC7slBTV3AJ6i1dc6NO6ZVF
meFAL8Uce3KiBWQ4B7j76gdgexhkAOSzQ96wD3flrcHdvCq7XG4TSxNOxe3GcM3SUg++WOyb5bLF
uEgQNmXLSUMi4A3VyBWd49YusqEu69ruSZd5OM4ukQF2zfFOeb/+6Wob6852sLKlwLnLZbrNXmc9
VOIIaKEAARtw8MoWr/vO7X615GtGc4veuH7J0eZ+YNoLSxAWrrSOKGrVuuOWu5O13xsS1sstoNo7
5Rmv8OzO8Eyrr4zbzz+OshztWOy9oLuHEqTOaxMlLnwHcyMhX/+1Dcl1Zq8JoJEvf6eyCTfd7iyV
tbay5FGe9fNOn/HE+ZihvmeZS+pddnNMP2sMzOnZOg7VHLkkKa04i/SglPMorVqBFcNk7+926Frn
RfZUD2jIiPbekvMltfPN9LR2pWGkveHTpuyyZZKV7oihq0l3ytw97xlYRsdlD7ziuvEqT9Bw89sN
BfQBBvV/v0SBL/TmRviFj/SF5oq3VcIow/gt+/czFfhTu3OiT69bzWu3+vUwn+EM5/p0vaN6D3SF
7nOWy4NT+vald9EOHLmfL7Q31/vcXOhb/9SZvzg8D7a47/lBv/t12vvQ5fzPj/m8CES0FPEUfzW6
36+8z/xAvPL/6aWuIJxgrF4r3e72D0YuSO+nj59cFxu3JysoAnZmzXvWIBAEwDAEApAC6IoKrziq
Mz3Lci0LePuyNmyQwpmGuhguaSSdaCwXLFabqm5U3U7le+WC1VQRINJKhzbxyMTVpqBRHtVmjYu9
aPANtxubv2O1U1vPHhyd2FfOkdbWz1CU0CFT1RFf3+EfIFtLT5nhWWROGw9j1w4kUZ5op9JdpqYb
kudnYR/Mok9pAGRkWCUhotnfSePTYKcsH+1lLRqWUQlXk9GwbZ3PyFqT1A8xymj1Z80Tknek3t3m
c3SjyFbSdXrdHfEiaFtWqDhZ++Wctx4LEQOy/WjnzlE1gui4/92yBy5coBUxopm7tzCgwHWTqOHj
iC1gNGyaLH7DN2uElYJLmukKGGwMRYO21rlcMdKmuYMz1rwaNnGPOZFBNw60hPJjUHgEy+EU5PTd
Q4uvdkSJ0kdokjwtER3t0e8a0mGgGEq9Ac9JI5xU94CtmG0lkqIV55X7mYUmU7JPEUZ1h9ISM6Kx
kmEl5HPTlnBpgzGCg+vWWrZAWQWeZGJwV4yEZnJ5DHjxGI/iul2r+mvOSna6kHTlA9IuUs+WFl/y
ixYtjDdWUVd+hjmzI3J33bCrRwNlY9w64ejAbUUKzOATYRJXXNMaKdw721GTCY6Hs1tKQgutM/2j
GzmawDOizf9TInfTy487vVetdXTzBql7VQyMo2xS7bOWXfeBV599z5GHk0/cIdXfZ0a15x6BXe3k
yCTFTScIa7rMYx9TY6ExYYCDbGeaT2+gU580/JzB3VNxLWSfPc15194UsuVGIIoWrqeZhie4xpIu
QuSXGCtAkjhaWjzu2GAzF8pjRHEj2siakeXhQtk/JL63kwByHTUKX0BNASODMvJnDSjnuDhhju91
Mpxc/UiJXSXHCVlWDFmGRREiXT6RnXZyKOKDmCs+BRYt+8XYJ13YtUmSNHAqZ+g9HyWqKEhtnbln
U2qix2ZWHFaKY45CuBSLHJ5+is8/fRoJYouTbHJMaTellaf/Dqr6kSeVZr7qpqwXUbXSISH5ktud
oCUZJoMs6anip6DGKtCsnNRqxpbLMlvfl7y24esdxzRj1RXWTlPkWN8eqCyYxwrY2VXAjgjYcQl1
WIJY7lyHJ67fxsMTqwClM+aZ/+ZrkmFFGsSJSnyxJh49AkbpkAsv2SuNPa3Cuq8axG2LnWGQcdzN
RsDQq3HC+AIBa8P84pJrjYyWxLGIaUaZjYvKWIMNediKBbFR1KjxjYvTtAB0GefstQ3PCr8M05hF
hkx0vYgevcjDSlv1i0NPQ00lMLlIRKTMItdk19YJchzLTKu88uuD93Y89dIspQ3LdTIdDVDSDAtS
gp/a8hOa/3opdihQ4O5Ogyi6S+O8DdWUj4RCCRczGmubyOW2OL+nrqXxFgMxvFnKv6hOpk2Z76zb
P517LiTob9JcNeQmSV4Q5UxTPRUJhfulzV+2ptgw47bLG3Tup9ueJBiXUQdW7Hr+XBWaQy+NkXBh
Jpbp5JU3eFhqwU/sF+eJl+agmSeztS5HpnODuteb/VRJc4TDvbmiUSreYEe60SLWNA9MSYPbeRw1
G/NBjXr9Kxf2aGcS972te/Kbn3egx8DpVeWBoXmSBM2CQe6x7Xu7w9RmUliq1kmPg4cD1gc/F0Kz
cG2ABZJfDSv4kQRGLn+hc+EL9TQ7yWRPgCT0m47ety740P9OgSL6IXo6uLHZzXCCI9wIEj0jHznl
QHqDeB/+2MOW+PCOG4Q5X3W0RTBKkCdAzGmhMQaIrBFRhYwFMeMZy9CZNaDPVqo4ignvthogEm+O
15sOwYiRx7FpsYN+PI1MIDIELzamkHPszhjlhEcsrukxm9NiIvbnwDC+rI4cGQ2EOpQOT+4oCwLB
YmQqxkkghsSQ/yOURb63OMTwsTSu9NBGYqmXWX4xiBdDSBMDmUueodFEEOsIMM8Vy5vADwtSJEwp
JViiPfJOlP2h3vdYaSXX6OZivFpfE6h1Ns8sTpzfNMwuGthIKNCxgeRABwxlOChfWLOaXevlHuMS
zyiyMj3/DoriRPB5zgpBIU/DOeJPaOSVN7wyNdlJTEhKxr+mgeeW2iKDM9vZSxDNDDK3ApThghUJ
zZCRic8ylF3iFFDh1GJlNMLLSimKkJxKJzJMVFk3aSpTydHUmhm7KU1ySq2hNUc/QurMMcJTzS81
xGZiAchRTZRUcoKNVCzKZEPxJ1EiUUOmGDUpTfQYOVJpbyDsI1KghBhTJoU1plFsykQFxdVVZHQN
bk2mtMo3S+1ph6IPI2hTxAmlOFahW361H/HkhleyUhWpDavlWavqDWq5iq08+asSWcXTwVaWEZmb
38rGBz728CV64yBhPKXigg7J6a7IW0qYVIXaUKFLpxgi/1nwxmHDXaxUELdVzaiQ16LSkUuryAQc
/nAb3NeuK7aJdSlh6SLce/LltPFikKfUOaVTQkMU3bSuWrBLWG9NDxqaBJR4ocKTcbiOLr5ADAHn
y1W4gqu3L8Dhy5QqWTqSJQinQM+QZhpJ8HlFlYltS/PYgVJ1Rvc99D3wDpsK1QLtw0QTwyuEC9hY
+JZMQqCUCOGWEDl6Xla/ewWR/OSrlhK3iXAgEUWK7XuhDQvVpbYQ7YNP572H9MttlBFDeaeE4gNz
gg18zO92HPXhIMNsyN/Z42rDUaQ74nigeVsmdrUIm8AOLCHNy8rKfFvjJFcKWyrWHYtpi8d+LsK9
wPqamqwL4t7LNLS+ldNHmO9Ijl2CFELjMl3ACHmTloTpeV6GT0R8LOEETlnIO7GxsIia0pEwOnR9
Vk+mnWIYdqrQwaIY66HXKjnDOQ0NpuMzJ7zcVVFDGZniAdOmePzH+6qj0ekssfhuU0YgURpZWD1d
nZrTVRqz49UPW+qfvwukDFEaNTe7Ra5duus7MdrXdU1FqBHzOJYWu0a3rvN1ZuuaStvA2b8GW7DB
dDCmiiAEADs=
--------------010100030206000508010104--




From pana-bounces@ietf.org Tue Apr 24 03:57:28 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgFtw-0005Ld-9U; Tue, 24 Apr 2007 03:57:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgFtu-0005Jr-D4
	for pana@ietf.org; Tue, 24 Apr 2007 03:57:26 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgFts-0003DP-1F
	for pana@ietf.org; Tue, 24 Apr 2007 03:57:26 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1HgFtl2ibp-0008Vy; Tue, 24 Apr 2007 03:57:21 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Subject: RE: [Pana] Ping and pending request
Date: Tue, 24 Apr 2007 10:57:13 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-reply-to: <20070424001323.GH3668@steelhead>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
thread-index: AceGBWWMrViC6NtORDa30D+Ep4H4BgAQAcQw
Message-ID: <0MKp2t-1HgFtl2ibp-0008Vy@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1+MRPpvebKrP4LfsBgKCEdibLRVQ/Sq4gTl19P
	A1wrWIgGIIury5wJohRX9hMMJFixsTy09JYffGmj/7tJqfQHb1
	VP5L++HuBtZBFXNaAI5Lw==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

> > Do the sequence numbers play a role our state machines? I hadn't thought
> so.
> 
> The play is implicit based on the following lock-step constrations:
> 
> - Each peer maintains a single sequence number space for outgoing
> requests.
> 
> - There is only one outstanding outgoing request allowed for each
> peer.  A peer that receives a request accepts the sequence number
> which is last received sequence number + 1 only.

Both of these rules are still maintained whether we have two state machines
or one. Do we change anything? As long as we stick to "one outstanding
request at a time" rule, these rules shall apply as they are.


> This means sequence numbers play a role in our state machine.  Running
> multiple state machines in pararell and independenly would break the
> lock-step constraints.

In my understanding, "lock-step" is about "not having two outstanding
requests issued by the same peer." Based on that, I'd say the lock-step
nature is preserved.

The sequence number processing on incoming messages are done for validation.
Invalid messages are tossed away, valid ones are processed by the state
machine. I don't think we'd have a statement in our state machine
specification that uses the "sequence number" as an input and change the way
state machine runs. 

What do you think?

Alper





> 
> Yoshihiro Ohba
> 
> 
> 
> >
> > Alper
> >
> >
> >
> >
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > > >
> > > > This scheme prevents any special case handling to be part of the
> > > protocol
> > > > specification.
> > > >
> > > > Your suggestion below works too I believe. Though I lean towards the
> > > above
> > > > suggestion, given that it does not special case one type of message
> in
> > > the
> > > > spec.
> > > >
> > > > I remember once mentioning use of a separate state machine for
> pings. I
> > > > don't remember what the feedback was....
> > > >
> > > > Alper
> > > >
> > > >
> > > > > which will end up with the 2*N
> > > > > problem.  On the other hand, it may be possible for the PaC to
> queue
> > > > > the incoming PAR until the ping request is answered.
> > > > >
> > > > > So how about relaxing the third item to:
> > > > >
> > > > > "
> > > > > - When there is an outstanding ping request, all incoming messages
> > > > >   MUST NOT be processed except for ping answer or error request
> sent
> > > > >   in response to the ping request.
> > > > > "
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > > >
> > > > > > Alper
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > This may be an acceptable operation.
> > > > > > >
> > > > > > > Yoshihiro Ohba
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > Alper
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Pana mailing list
> > > > > > Pana@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/pana
> > > > > >
> > > >
> > > >
> >
> >


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



From pana-bounces@ietf.org Tue Apr 24 08:55:46 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgKYb-0001Tq-Rh; Tue, 24 Apr 2007 08:55:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgKYa-0001Th-Pv
	for pana@ietf.org; Tue, 24 Apr 2007 08:55:44 -0400
Received: from imx12.toshiba.co.jp ([61.202.160.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgKYa-000826-1a
	for pana@ietf.org; Tue, 24 Apr 2007 08:55:44 -0400
Received: from wall11.toshiba.co.jp (wall11 [133.199.90.149])
	by imx12.toshiba.co.jp  with ESMTP id l3OCtWFW025966;
	Tue, 24 Apr 2007 21:55:32 +0900 (JST)
Received: (from root@localhost) by wall11.toshiba.co.jp  id l3OCtWgc015224;
	Tue, 24 Apr 2007 21:55:32 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] 
	by wall11.toshiba.co.jp with ESMTP id XAA15223;
	Tue, 24 Apr 2007 21:55:31 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp11.toshiba.co.jp  with ESMTP id l3OCtVRL003570;
	Tue, 24 Apr 2007 21:55:31 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3OCtV73022109;
	Tue, 24 Apr 2007 21:55:31 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JH00011K6KGOAF0@mail.po.toshiba.co.jp>; Tue,
	24 Apr 2007 21:55:31 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1HgKYJ-00034m-OH; Tue,
	24 Apr 2007 05:55:27 -0700
Date: Tue, 24 Apr 2007 08:55:27 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Ping and pending request
In-reply-to: <0MKp2t-1HgFtl2ibp-0008Vy@mrelay.perfora.net>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <20070424125527.GB11057@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <20070424001323.GH3668@steelhead>
	<0MKp2t-1HgFtl2ibp-0008Vy@mrelay.perfora.net>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Cc: townsley@cisco.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>
Errors-To: pana-bounces@ietf.org

On Tue, Apr 24, 2007 at 10:57:13AM +0300, Alper Yegin wrote:
> > > Do the sequence numbers play a role our state machines? I hadn't thought
> > so.
> > 
> > The play is implicit based on the following lock-step constrations:
> > 
> > - Each peer maintains a single sequence number space for outgoing
> > requests.
> > 
> > - There is only one outstanding outgoing request allowed for each
> > peer.  A peer that receives a request accepts the sequence number
> > which is last received sequence number + 1 only.
> 
> Both of these rules are still maintained whether we have two state machines
> or one. Do we change anything? As long as we stick to "one outstanding
> request at a time" rule, these rules shall apply as they are.

The issue I am trying to bring is complexity of maintaining two state
machines and still follow the "one outstanding request at a time"
rule.  I am actually faced with this issue while I am revising
pana-statemachine draft.

> 
> 
> > This means sequence numbers play a role in our state machine.  Running
> > multiple state machines in pararell and independenly would break the
> > lock-step constraints.
> 
> In my understanding, "lock-step" is about "not having two outstanding
> requests issued by the same peer." Based on that, I'd say the lock-step
> nature is preserved.

When we preserve "lock-step", then it means we can't run two state
machines independently, right?  This is very similar to multi-thread
programming using semaphore to access critical resource (i.s., one
outstanding request issued by the same peer) to which only one thread
can access at a time.  This constraint is basically coming from using
the same sequence number space for ping and other messages.  I am just
thinking that implementations can be much simpler if we have separate
sequence number space for ping in order to run ping state machine
independently of non-ping state machine.

Yoshihiro Ohba


> 
> The sequence number processing on incoming messages are done for validation.
> Invalid messages are tossed away, valid ones are processed by the state
> machine. I don't think we'd have a statement in our state machine
> specification that uses the "sequence number" as an input and change the way
> state machine runs. 
> 
> What do you think?
> 
> Alper
> 
> 
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > 
> > >
> > > Alper
> > >
> > >
> > >
> > >
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > >
> > > > > This scheme prevents any special case handling to be part of the
> > > > protocol
> > > > > specification.
> > > > >
> > > > > Your suggestion below works too I believe. Though I lean towards the
> > > > above
> > > > > suggestion, given that it does not special case one type of message
> > in
> > > > the
> > > > > spec.
> > > > >
> > > > > I remember once mentioning use of a separate state machine for
> > pings. I
> > > > > don't remember what the feedback was....
> > > > >
> > > > > Alper
> > > > >
> > > > >
> > > > > > which will end up with the 2*N
> > > > > > problem.  On the other hand, it may be possible for the PaC to
> > queue
> > > > > > the incoming PAR until the ping request is answered.
> > > > > >
> > > > > > So how about relaxing the third item to:
> > > > > >
> > > > > > "
> > > > > > - When there is an outstanding ping request, all incoming messages
> > > > > >   MUST NOT be processed except for ping answer or error request
> > sent
> > > > > >   in response to the ping request.
> > > > > > "
> > > > > >
> > > > > > Yoshihiro Ohba
> > > > > >
> > > > > > >
> > > > > > > Alper
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > This may be an acceptable operation.
> > > > > > > >
> > > > > > > > Yoshihiro Ohba
> > > > > > > >
> > > > > > > >
> > > > > > > > >
> > > > > > > > > Alper
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Pana mailing list
> > > > > > > Pana@ietf.org
> > > > > > > https://www1.ietf.org/mailman/listinfo/pana
> > > > > > >
> > > > >
> > > > >
> > >
> > >
> 
> 

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



From pana-bounces@ietf.org Tue Apr 24 19:42:52 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgUeS-00077w-Fc; Tue, 24 Apr 2007 19:42:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgUeR-00077l-08
	for pana@ietf.org; Tue, 24 Apr 2007 19:42:27 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgUeP-0000Fd-Br
	for pana@ietf.org; Tue, 24 Apr 2007 19:42:26 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3ONgM2Y010744
	for <pana@ietf.org>; Wed, 25 Apr 2007 08:42:22 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3ONgNgS029536;
	Wed, 25 Apr 2007 08:42:23 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id JAA29535;
	Wed, 25 Apr 2007 08:42:23 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3ONgM0J007655;
	Wed, 25 Apr 2007 08:42:22 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3ONgMU8010600;
	Wed, 25 Apr 2007 08:42:22 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JH1007NQ0IJ1290@mail.po.toshiba.co.jp>; Wed,
	25 Apr 2007 08:42:22 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1HgUeI-0004uA-Cg; Tue,
	24 Apr 2007 16:42:18 -0700
Date: Tue, 24 Apr 2007 19:42:18 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20070424234217.GG12528@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [Pana] Ping and pending request: proposed resolution
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>
Errors-To: pana-bounces@ietf.org

Here is proposed resolution:

- Allow sending ping request in access phase only.

- Allow receiving ping request in any phase.

Note 1: It is not necessary to have a separate sequence number space
for ping, given that PANA state machines draft will define a mechanism
to serialize events for transmitting requests so that lock-step
property is preserved.

Note 2: As long as lock-step property is preserved, it may be possible
to allow sending ping request in any phase, but allowing sending ping
request in access phase only is simpler and sufficient.

Regards,
Yoshihiro Ohba

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



From pana-bounces@ietf.org Wed Apr 25 04:49:03 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgdBO-00038e-A2; Wed, 25 Apr 2007 04:49:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgdBN-00038X-Ti
	for pana@ietf.org; Wed, 25 Apr 2007 04:49:01 -0400
Received: from mout.perfora.net ([74.208.4.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgdBM-0007xw-Hk
	for pana@ietf.org; Wed, 25 Apr 2007 04:49:01 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1HgdBG3yiP-0002i7; Wed, 25 Apr 2007 04:48:59 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
	<pana@ietf.org>
Subject: RE: [Pana] Ping and pending request: proposed resolution
Date: Wed, 25 Apr 2007 11:48:50 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-reply-to: <20070424234217.GG12528@steelhead>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
thread-index: AceGykYLQyXjwYldQy20xsILiWCu3AATEFzw
Message-ID: <0MKp2t-1HgdBG3yiP-0002i7@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1+vJ19xVQbWPbcpEqE4jstWPGrGjLW4rI2fesX
	46+IvvvHB/1jjyBF6Ch7omsFUoiORc8DayD37ubTJ2FptgaTym
	Uid2BsXIVVrCTqdHsM07A==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: 
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>
Errors-To: pana-bounces@ietf.org

I agree.

Alper


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Wednesday, April 25, 2007 2:42 AM
> To: pana@ietf.org
> Subject: [Pana] Ping and pending request: proposed resolution
> 
> Here is proposed resolution:
> 
> - Allow sending ping request in access phase only.
> 
> - Allow receiving ping request in any phase.
> 
> Note 1: It is not necessary to have a separate sequence number space
> for ping, given that PANA state machines draft will define a mechanism
> to serialize events for transmitting requests so that lock-step
> property is preserved.
> 
> Note 2: As long as lock-step property is preserved, it may be possible
> to allow sending ping request in any phase, but allowing sending ping
> request in access phase only is simpler and sufficient.
> 
> Regards,
> Yoshihiro Ohba
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana


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



From poste@sympatico.ca Wed Apr 25 05:06:29 2007
Return-path: <poste@sympatico.ca>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgdSH-0002ry-03
	for pana-archive@lists.ietf.org; Wed, 25 Apr 2007 05:06:29 -0400
Received: from tomts10.bellnexxia.net ([209.226.175.54] helo=tomts10-srv.bellnexxia.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HgdSF-0007tK-Ls
	for pana-archive@lists.ietf.org; Wed, 25 Apr 2007 05:06:28 -0400
Received: from User ([74.12.79.139]) by tomts10-srv.bellnexxia.net
          (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with SMTP
          id <20070425090626.YLNE1723.tomts10-srv.bellnexxia.net@User>;
          Wed, 25 Apr 2007 05:06:26 -0400
From: "Poste"<poste@sympatico.ca>
Subject: Una nuova gamma completa di servizi online  adesso disponibile !
Date: Wed, 25 Apr 2007 04:57:58 -0400
MIME-Version: 1.0
Content-Type: text/html;
	charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-Id: <20070425090626.YLNE1723.tomts10-srv.bellnexxia.net@User>
X-Spam-Score: 4.7 (++++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

<P>
<TABLE cellSpacing=0 cellPadding=0 width=500 align=center border=1>
<TBODY>
<TR>
<TD align=middle colSpan=3><FONT size=2>
<TABLE cellSpacing=0 cellPadding=0 width=600 bgColor=#e7efe2 border=0>
<TBODY>
<TR>
<TD>
<DIV><FONT size=2>
  <IMG src="http://www.posteitaliane.it/img/tb/logo_posteitaliane.gif" width="254" height="42"></FONT></DIV>
<DIV>
<TABLE cellSpacing=0 cellPadding=0 width=740 border=0>
<TBODY>
<TR bgColor=#000099>
<TD><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT></TD>
<TD align=right colSpan=2><FONT size=2>&nbsp;&nbsp;&nbsp; </FONT></TD></TR></TBODY></TABLE></DIV></TD></TR></TBODY></TABLE>
<DIV align=left><FONT face=Verdana size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  <IMG src="http://www.postecom.it/img/prodotto/posteit02h.jpg" width="220" height="129"></FONT></DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left><FONT face=Verdana>Caro cliente Poste.it,</FONT></DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left><FONT face=Verdana size=2>Una nuova gamma completa di servizi online  adesso disponibile !</FONT></DIV>
<DIV align=left><FONT face=Verdana size=2>Per poter usufruire dei nuovi servizi online di Poste.it occorre prima diventare UTENTE VERIFICATO.</FONT></DIV><FONT face=Verdana size=2><FONT size=3></FONT>
<DIV align=left><BR>&nbsp;&nbsp;&nbsp;<A title="Accedi a Poste.it " href="https://jsp.dti.unimi.it/scripts/ssl/postepay.it/online/personale/login-home.fcc/33554433&REALMOID/" target=""><IMG alt="Accedi a Poste.it " src="http://posteitaliane.it/img/ico/egramma_g.gif" border=0 width="12" height="12"></A><FONT size=3>&nbsp; <A title="Accedi a Poste.it " href="https://jsp.dti.unimi.it/scripts/ssl/postepay.it/online/personale/login-home.fcc/33554433&REALMOID/"><FONT color=#0000ff size=2>Accedi ai servizi online di Poste.it e diventa UTENTE VERIFICATO </FONT></A><STRONG>&nbsp;</STRONG></FONT></DIV>
<DIV align=left><STRONG><FONT size=3></FONT></STRONG>&nbsp;</DIV>
<DIV align=left>L'Assistenza Clienti, dopo aver ricevuto la documentazione e averne verificato la completezza e la veridicit, provveder immediatamente ad attivare&nbsp;il suo " <STRONG>Nome Utente Verificato</STRONG> ". Verrai informato telefonicamente di tale attivazione.</DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left><BR></DIV>
<DIV align=left>
  <IMG alt=TELEFONO src="http://www.poste.it/img/ico/telfono_b.gif" border=0 width="14" height="11">&nbsp;<B>TELEFONO</B><BR><STRONG>Numero gratuito 803.160</STRONG> (dal luned al sabato dalle ore 8 alle ore 20).&nbsp;&nbsp;&nbsp;</DIV>
<DIV align=left>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</DIV>
<DIV align=left>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left></FONT><FONT face="Times New Roman" size=2>|  Poste Italiane 2006 | </FONT><A href="http://www.poste.it/azienda/posterisponde/"><FONT face="Times New Roman" color=#0000ff size=2>contattaci</FONT></A><FONT face="Times New Roman" size=2> | </FONT><A href="http://www.poste.it/azienda/policy.shtml"><FONT face="Times New Roman" color=#0000ff size=2>privacy </FONT></A><FONT face="Times New Roman" size=2>| </FONT><A href="http://www.poste.it/online/mappa.shtml"><FONT face="Times New Roman" color=#0000ff size=2>mappa del sito</FONT></A><FONT face="Times New Roman" size=2> | </FONT><A href="http://www.poste.it/online/personalizza.shtml"><FONT face="Times New Roman" color=#0000ff size=2>personalizza visualizzazione</FONT></A><FONT face="Times New Roman"><FONT size=2> | Partita IVA 01114601006 |</FONT> </FONT></FONT></DIV></TD></TR></TBODY></TABLE>



From pana-bounces@ietf.org Wed Apr 25 09:12:50 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HghIg-0007kv-3X; Wed, 25 Apr 2007 09:12:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HghIf-0007ea-Bv
	for pana@ietf.org; Wed, 25 Apr 2007 09:12:49 -0400
Received: from mout.perfora.net ([74.208.4.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HghIc-0003Tm-VO
	for pana@ietf.org; Wed, 25 Apr 2007 09:12:49 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1HghIZ2vRn-0002md; Wed, 25 Apr 2007 09:12:46 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Subject: RE: [Pana] Nits on processing invalid message
Date: Wed, 25 Apr 2007 16:12:38 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-reply-to: <20070423204915.GE3668@steelhead>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
thread-index: AceF6OQmtzGAQHaYRD6gD79MtY2LFgBUhKhA
Message-ID: <0MKp2t-1HghIZ2vRn-0002md@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX18u/CLDBlFKPZLcpf0FDSCBkXbIBQmviifqFb2
	3dU1oLT2+m5r/guoUEipcikG/h4vJsb2Ttzocf4HRdp1VI3FTf
	StbPsG6XnPnRzAyM+pNpw==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
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>
Errors-To: pana-bounces@ietf.org

Maybe I misunderstood the problem.

PaC    PAA
 ----> req
 <---  error request
 --->  error answer


What kind of DoS attack are we looking at?

Is it about a rogue PaC spoofing an erroneous "req" and leading to PAA's
termination of the victim PaC's session? Or some other scenario....

Alper





> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Monday, April 23, 2007 11:49 PM
> To: Alper Yegin
> Cc: 'Yoshihiro Ohba'; pana@ietf.org
> Subject: Re: [Pana] Nits on processing invalid message
> 
> On Mon, Apr 23, 2007 at 10:38:27PM +0300, Alper Yegin wrote:
> > > > > If an error request is returned in response to an erroneous
> message,
> > > > > then this means that the sender of the error request message will
> > > > > terminate the session after receiving the error answer.  This
> actually
> > > > > does not provide robustness against DoS attacks because an
> attacker
> > > > > can send an erroneous answer to terminate the session.  So the
> text
> > > > > should say:
> > > > >
> > > > > "
> > > > >    Invalid messages MUST be discarded either silently in order to
> > > > >    provide robustness against DoS attacks or with returning
> > > > >    an error request message to the sender.  See Section 5.8
> > > > >    for details.
> > > > > "
> > > >
> > > > I think this is effectively the same statement as the original one.
> If
> > > we
> > > > want to maintain the DoS resiliency, we shall just go with "Invalid
> > > messages
> > > > MUST be discarded in order to provide robustness against DoS
> attacks."
> > >
> > > Does this mean that most protocol error result codes defined in
> > > Section 8.8.2 are not needed, except for the folloiwng ones?
> > >
> > >    PANA_UNABLE_TO_DELIVER                  1002
> > >    PANA_RESOURCES_EXCEEDED                 1008
> > >    PANA_UNABLE_TO_COMPLY                   1013
> >
> > Yes, this is what it boils down to. Is this a concern?
> 
> DoS attack is also possible with those errors.  The only difference is
> whether the errors are supposed to be generated due to receipt of an
> invalid message or some other reasons.
> 
> >
> > I personally don't mind reducing the error list down to that. If we
> wanted
> > to keep the same longer list, yet still have DoS resiliency, we could
> > mandate presence of AUTH AVP in the offending messages. If the offending
> > message does not have a valid AUTH AVP, the message must be silently
> > discarded.
> 
> This does not seem to solve the problem either.  If the protected
> message contains errors, then the receiver will create an protected
> error request, but the session will be terminated after receiving an
> error answer according to the discussion (i.e., in general, the sender
> of the erronerous message has no idea on what to do next other than
> terminating the session.)
> 
> I think error messages should be used only in debugging mode,
> regardless whether there is PANA SA or not.
> 
> Yoshihiro Ohba
> 
> >
> > When we are talking about DoS in this case, we are concerned about
> attackers
> > who don't even have a PANA SA, right?
> >
> > Alper
> >
> >
> >


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



From pana-bounces@ietf.org Wed Apr 25 09:26:10 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HghVa-00014a-2n; Wed, 25 Apr 2007 09:26:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HghVZ-00011U-GN
	for pana@ietf.org; Wed, 25 Apr 2007 09:26:09 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HghVW-0007vg-Rc
	for pana@ietf.org; Wed, 25 Apr 2007 09:26:09 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3PDQ383015940;
	Wed, 25 Apr 2007 22:26:03 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3PDQ4sw015554;
	Wed, 25 Apr 2007 22:26:04 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id YAA15553;
	Wed, 25 Apr 2007 22:26:04 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3PDQ33C021401;
	Wed, 25 Apr 2007 22:26:03 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3PDQ3he014082;
	Wed, 25 Apr 2007 22:26:03 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JH200BDJ2N9FQ40@mail.po.toshiba.co.jp>; Wed,
	25 Apr 2007 22:26:02 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1HghVK-00063G-M2; Wed,
	25 Apr 2007 06:25:54 -0700
Date: Wed, 25 Apr 2007 09:25:54 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Comments on draft-pana-pana-15a
In-reply-to: <46282F3B.5040102@research.telcordia.com>
To: Subir Das <subir@research.telcordia.com>
Message-id: <20070425132554.GC20849@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <46278FB7.5090808@tari.toshiba.com>
	<46282F3B.5040102@research.telcordia.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b83962958e2d910ed948e2f9e138d171
Cc: "pana@ietf.org" <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>
Errors-To: pana-bounces@ietf.org

Hi Subir and all,

Thank you very much for your review comments.  The comments are
definitely useful to improve the quality of the draft.

Please see my response below.

-------------------------------------
   Session Lifetime:

      A duration that is associated with a PANA session.  For an
      established PANA session, the session lifetime is bound to the
      lifetime of the current authorization given to the PaC.  The
      session lifetime can be updated[a1] by a new round of EAP
      authentication before it expires.

[a1]Extended may be a better term here.

[YO] OK, s/updated/extended/.

   Session Identifier:

      This identifier is used to uniquely identify a PANA session on the
      PaC and the PAA.  It is included in PANA messages to bind the
      message to a specific PANA session.  This bidirectional identifier
      is allocated by the PAA in the initial request message and freed
      when the session terminates.  The session identifier is assigned
      by the PAA and is unique within the PAA [a2]during the lifetime of the
      session.

[a2]May like to delete this part

[YO] We can delete "during the lifetime of the session"

   Enforcement Point (EP):

      A node on the access network where per-packet enforcement policies
      (i.e., filters) are applied on the inbound and outbound traffic of
      access devices.  The EP and the PAA may be co-located.  EPs should
      prevent data traffic from and to any unauthorized client unless
      it's either PANA or one of the other allowed traffic types (e.g.,
      ARP, IPv6 neighbor discovery, DHCP, etc.).  Detailed enforcement
      policies may be specified in deployment-specific PANA
      applicability documents.[a3]

[a3]Is it specified in a separate document. If so, pl. provide the
reference, otherwise delete this sentence.

[YO] There is an expired draft: draft-morand-pana-panaoverdsl-00.txt,
but we can simply remove the sentence to move forward.


   o  Access phase: After a successful authentication and authorization
      the host[a4] gains access to the network and can send and receive IP[a5]
      data traffic through the EP(s).  At any time during this phase,
      the PaC and PAA may optionally send PANA notification messages to
      test liveness of the PANA session on the peer.

[a4]Other places ?access device? is used.  A consistent terminology  would be better. 

[YO] I agree, s/host/access node/.

[a5]Is this correct?  Are DHCP, ND, ARP not IP data traffic? 

[YO] ARP is definitely not IP.  I am not sure if we can categorize
DHCP and ND as IP control or data traffic.  I think we can remove
"data" here.

   o  Re-authentication phase: During the access phase, the PAA must
      initiate re-authentication before the PANA session lifetime
      expires.  EAP is carried by PANA to perform authentication.[a6]  This
      phase may be optionally triggered by both the PaC and the PAA
      without any respect to the session lifetime. [a7] The session moves to
      this phase from the access phase, and returns back there upon
      successful re-authentication.

[a6]Is it authentication or re-authentication?

[YO] It should be s/authentication/re-authentication, because this
paragraph is talking about re-authentication phase.

[a7]May consider revising this part. 

[YO] I agree.  Since authorization state remains during
re-authentication, re-authentication phase should be described as a
sub-phase of access phase.  How about this?

  "Re-authentication phase is a sub-phase of access phase.  The
  session moves to this sub-phase from the access phase when
  re-authentication starts, and returns back there upon successful
  re-authentication."


   Cryptographic protection of messages between the PaC and PAA is
   possible as soon as EAP in conjunction with the EAP method exports a
   shared key.  That shared key is used to create a PANA SA.  The PANA
   SA helps generate per-message authentication codes that provide
   integrity protection and authentication.

   Throughout the lifetime of a session, various problems found with the
   incoming messages can generate an error request message (see
   Section 5.8) sent in response.[a8]

[a8]other places ?answer? is used .. terminology problem..

[YO] I think we can simply remove the paragraph.  I don't think we
need error handling overview in protocol overview section.


   The PAA SHOULD limit the rate it processes incoming[a9]
   PANA-Client-Initiation messages in order not to subject itself to
   denial-of service (DoS) attacks.  Details of rate limiting are
   outside the scope of this specification.

[a9]May consider revising the sentence.

[YO] How about this?

"
   The PAA SHOULD limit the rate it processes incoming
   PANA-Client-Initiation messages to provide robustness against
   denial-of service (DoS) attacks.
"

   If the PAA wants to stay stateless in response to a
   PANA-Client-Initiation message, it SHOULD NOT include an EAP-Payload
   AVP in the initial PANA-Auth-Request message, and it SHOULD NOT re-
   transmit the message on a timer.  For this reason, the PaC MUST
   retransmit the PANA-Client-Initiation message until it enters the
   authentication and authorization phase by receiving the second
   PANA-Auth-Request message (not a retransmission of the initial one)
   from the PAA.[a10]

[a10]Not  clear  in particular, the last part of the sentence.

[YO] There is some leftover from previous revison that had handshake
phase which we don't have now.  We can revise the sentence to:

"
   For this reason, the PaC MUST retransmit the PANA-Client-Initiation
   message until it receives the second PANA-Auth-Request message (not
   a retransmission of the initial one) from the PAA.
"

   PaC      PAA  Message(sequence number)[AVPs]
   --------------------------------------------------------------------
      ----->     PANA-Client-Initiation(0)
      <-----     PANA-Auth-Request(x)         // 'S' bit set
      ----->     PANA-Auth-Answer(x)          // 'S' bit set
      <-----     PANA-Auth-Request(x+1)[Nonce, EAP]
      ----->     PANA-Auth-Answer(x+1)[Nonce] // No piggybacking EAP
      ----->     PANA-Auth-Request(y)[EAP]
      <-----     PANA-Auth-Answer(y)
      <-----     PANA-Auth-Request(x+2)[EAP]
      ----->     PANA-Auth-Answer(x+2)[EAP][a11]
      <-----     PANA-Auth-Request(x+3)[Result-Code, EAP, Key-Id,
                                            Algorithm, Lifetime, AUTH]
                                               // 'C' bit set
      ----->     PANA-Auth-Answer(x+3)[Key-Id, AUTH]
                                               // 'C' bit set

    Figure 1: Example sequence for the authentication and authorization
                     phase for a PaC-initiated session

[a11]Is this piggybacked EAP?  It is not clear why EAP is not inlcuded
in PANA-Auth_Answer (y).  Some texts explaning the piggybaked EAP will
be helpful 

[YO] We can add "// Piggybacking EAP" here.  To explain piggybacked EAP, 
we can revise the Figure 1 caption as follows:

"
    Figure 1: Example sequence for the authentication and
    authorization phase for a PaC-initiated session ("Piggybacking
    EAP" is the case in which an EAP AVP is carried in PAN.)
"


   The last PANA-Auth-Request message MUST also carry an Algorithm AVP
   if it is for the first derivation of keys in the session.  The PANA
   session MUST be deleted immediately after the last PANA-Auth message
   exchange.[a12]

[a12]Is it really a PANA Session?  This is happening during
authentication and authorization phase which is a part of a PANA
session. Also the definition of PANA should include authorization as a
cause to session termination.

[YO] Yes, it's a PANA session that is terminated
(s/deleted/terminated/ per your other comment.).  With regard to
authorization as a cause to session termination, we can revise the
PANA Session definition in Section 2 to:

   PANA Session:

      A PANA session is established between the PANA Client (PaC) and
      the PANA Authentication Agent (PAA), and terminates as a result
      of an authentication or liveness test failure, a message
      delivery failure after retransmissions reach maximum values or
      session lifetime expiration, an explicit termination message or
      any event that causes discontinuation of the access service.  A
      fixed session identifier is maintained throughout a session.  A
      session cannot be shared across multiple network interfaces.

("any event that causes discontinuation of the access service" was added.)

4.2.  Access Phase

   Once the authentication and authorization phase or the
   re-authentication phase successfully completes,[a13] the PaC gains access

[a13]Is this true?  Accordig to eralier definition or re-authenticatrion, it happens during access phase. 

[YO] You are right.  We should remove "or the re-authentication phase".

   to the network and can send and receive IP data traffic through the
   EP(s) and the PANA session enters the access phase.  In this phase,
   PANA-Notification-Request and PANA-Notification-Answer messages with
   'P' (Ping) bit set (ping request and ping answer messages,
   respectively) can be used for testing the liveness of the PANA
   session on the PANA peer.  Both the PaC and the PAA are allowed to
   send a ping request 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 ping answer message.  The ping request and answer
   messages MUST be protected with an AUTH 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.  Additionally, an implementation MAY
   rate-limit processing of  the incoming ping requests.  It should be noted
   that if a PAA or PaC which considers its connectivity lost after a
   relatively small number of unresponsive pings coupled with a peer
   that is aggressively rate-limiting the ping request and answer
   messages, false-positives could result. [a14] Care should be taken when
   rate-limiting ping request and answer messages to periodically
   respond, and a PAA or PaC should not rely on ping request and answer
   messages to quickly determine loss of connectivity.

[a14]Not clear. May consider revising the senetence.

[YO] How about this?  

"
   Therefore, a PAA or PaC should not rely on highly frequent ping
   request and answer message exchanges to quickly determine loss of
   connectivity.
"


4.3.  Re-authentication Phase

   The PANA session in the access phase can enter the re-authentication
   phase to extend the current session lifetime by re-executing EAP.
   Once the re-authentication phase successfully completes, the session
   re-enters the access phase.  Otherwise, the session is deleted.[a15]

[a15]Is it deleted or "terminated"?

[YO] It should be "terminated".

   When the PaC wants to initiate re-authentication, it sends a
   PANA-Notification-Request message with 'A' bit set (a re-
   authentication request message) to the PAA.  This message MUST
   contain the session identifier assigned to the session being
   re-authenticated.  If the PAA already has an established PANA session
   for the PaC with the matching session identifier, it MUST first
   respond with a PANA-Notification-Answer message with 'A' bit set (a
   re-authentication answer message), followed by a PANA-Auth-Request
   message that starts a new EAP authentication.  If the PAA cannot
   identify the session, it MUST silently discard the message.  The
   first PANA-Auth-Request and PANA-Auth-Answer messages in the
   re-authentication phase MUST have 'S' bit cleared [a16]and carry a Nonce
   AVP.

[a16]Some places it says bit is not set and other places it is
cleared. Consistency would be good.

[YO] We shall use "cleared" throughout the document. 

   The PaC may receive a PANA-Auth-Request before receiving the answer
   to its outstanding re-authentication request message.  This condition
   can arise due to packet re-ordering or a race condition between the
   PaC and PAA when they both attempt to engage in re-authentication.
   The PaC MUST keep discarding the received PANA-Auth-Requests until it
   receives the answer to its request.[a17]

[a17]How will PAA know that PaC has not received it?  Will PaC
retransmit PANA-Notification-Request?

[YO] Yes.  The PAA will answer to the PNR.

5.2.  Sequence Number and Retransmission

   PANA uses sequence numbers to provide ordered and reliable delivery
   of messages.

   The PaC and PAA maintain two sequence numbers: 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. [a18] These sequence numbers are 32-bit

[a18]Not clear. May cosnider revising it. 

[YO] How about this?

"
   The PaC and PAA maintain two sequence numbers: the one to be used
   for the next outgoing request and the one it expects to see in the
   next incoming request.
"

   unsigned numbers.  They are monotonically incremented by 1 as new
   requests are generated and received, and wrapped to zero on the next
   message after 2^32-1.  Answers always contain the same sequence
   number as the corresponding request.  Retransmissions reuse the
   sequence number contained in the original packet.

   The initial sequence numbers (ISN) are randomly picked by the PaC and
   PAA as they send their very first request messages except 
   PANA-Client-Initiation message that MUST be always 0. 
   When a request message is received, it is considered valid in terms
   of sequence numbers if and only if its sequence number matches the
   expected value.  This check does not apply to the
   PANA-Client-Initiation message and the initial PANA-Auth-Request
   message.

   When an answer message is received, it is considered valid in terms
   of sequence numbers if and only if its sequence number matches that
   of the currently outstanding request.  A peer can only have one
   outstanding request at a time.

   PANA request messages are retransmitted based on a timer until a
   response[a19] is received (in which case the retransmission timer is

[a19]Should be 'answer'

[YO] Yes, s/response/answer/.


   stopped) or the number of retransmission reaches the maximum value
   (in which case the PANA session MUST be deleted[a20] immediately).

[a20]Is it deleted or terminated ?

[YO] s/deleted/terminated/.


5.5.  Message Validity Check

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

   o  Each field in the message header contains a valid value including
      sequence number, message length, message type, version number,
      flags, session identifier, etc.

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

      *  In the authentication and authorization phase and the
         re-authentication phase:

         +  PANA-Client-Initiation after completion of the initial
            PANA-Auth-Request and PANA-Auth-Answer exchange.

         +  Re-authentication request.[a21]

[a21]This seems incorrect since it is expected that re-authentication
request will apprear during re-authntication phase.

[YO] You are right.  Re-auth request should be accepted at least in
re-authentication phase to deal with re-auth race condition (i.e.,
re-auth request and PAR cross each other).


         +  The last PANA-Auth-Request as well as ping request before
            completion of the initial PANA-Auth-Request and
            PANA-Auth-Answer exchange.

         +  The initial PANA-Auth-Request after a PaC receives a valid
            non-initial PANA-Auth-Request.

         +  PANA-Termination-Request.[a22]

[a22]Same as before.

[YO] You are right.  Re-auth request should be accepted at least in
re-authentication phase to deal with another race condition (i.e., PTR
and re-auth request or PAR cross each other).  Now I think it is
better to separate items for authentication and authorization phase
and re-authentication phase.

      *  In the access phase:

         +  PANA-Auth-Request.[a23]

[a23]Same as before since PANA-Auth-Request may appear during re-authentication phase. 

[YO] Yes, PAR should be allowed for PAA-initiated re-auth.  We should remove this.

         +  PANA-Client-Initiation.

      *  In the termination phase:

         +  PANA-Client-Initiation.

         +  All requests but PANA-Termination-Request.


[YO] So here is the new deny rule-set (including the resolution of
recent ping issue):

"
      *  In the authentication and authorization phase:

         +  PANA-Client-Initiation after completion of the initial
            PANA-Auth-Request and PANA-Auth-Answer exchange.

         +  Re-authentication request.

         +  The last PANA-Auth-Request as well as ping request before
            completion of the initial PANA-Auth-Request and
            PANA-Auth-Answer exchange.

         +  The initial PANA-Auth-Request after a PaC receives a valid
            non-initial PANA-Auth-Request.

         +  PANA-Termination-Request.

      *  In the re-authentication phase:

         +  PANA-Client-Initiation.

         +  The initial PANA-Auth-Request.

      *  In the access phase:

         +  PANA-Client-Initiation.

      *  In the termination phase:

         +  PANA-Client-Initiation.

         +  All requests but PANA-Termination-Request and ping request.
"


6.1.  IP and UDP Headers

   Any PANA message is unicast between the PaC and the PAA.

   For any PANA message sent from the peer that has initiated the PANA
   session, the UDP source port is set to any number and the destination
   port is set to the assigned PANA port number (to be assigned by
   IANA).  For any PANA message sent from the other peer, the source
   port is set to the assigned PANA port number (to be assigned by IANA)
   and the destination port is copied from the source port of the last
   received message.  [a24]In case both the PaC and PAA initiates the session
   (i.e., PANA-Client-Initiation and unsolicited PANA-Auth-Request
   messages cross each other), then the PaC is identified as the
   initiator.

[a24]What happens if PaC chooses a source port number  that is used by PAA?

[YO] According to the rule, the PAA will change its source port number
to PANA port number once the initiator is determined to be the PaC.

[a25]8.4.  Failed-AVP AVP

[a25]This AVP describes the vaule format while few others do  not.  

[YO] Because it is of type Grouped.

   The Failed-AVP AVP (AVP Code 4) provides debugging information in
   cases where a message is rejected or not fully processed due to
   erroneous information in a specific AVP.  The AVP data is of type
   Grouped.  The format of the Failed-AVP AVP using the ABNF grammar
   defined in [RFC3588] for Grouped AVP is as follows.

           <Failed-AVP> ::= < AVP Header: 4 >
                         1* {AVP}

   In case of a failed grouped AVP, the Failed-AVP contains the whole
   grouped AVP.  In case of a failed AVP inside a grouped AVP, the
   Failed-AVP contains the single offending AVP.

8.7.  Nonce AVP

   The Nonce AVP (AVP Code 7) carries a randomly chosen value that is
   used in cryptographic key computations.  The recommendations in
   [RFC4086] apply with regard to generation of random values.  The AVP
   data is of type OctetString and it contains a randomly generated
   value in opaque format.  The data length MUST be between 8 and 256
   octets inclusive.

   The length of the nonces are determined based on the available
   pseudo-random functions (PRFs) and the degree of trust placed into
   the two PaC and the PAA to compute random values.  The length of the
   random value for the nonce is determined whether

   1.  The PaC and the PAA each are likely to be able to compute a
       random nonce (according to [RFC4086]).  The length of the nonce
       has to be 1/2 the length of the PRF key [a26](e.g., 10 octets in the
       case of HMAC-SHA1).

   2.  The PaC and the PAA each are not trusted with regard to the
       computation of a random nonce (according to [RFC4086]).  The
       length of the nonce has to have the full length [a27]of the PRF key
       (e.g., 20 octets in the case of HMAC-SHA1).

   Furthermore, the strongest available PRF available for PANA has to be
   considered in this computation.  Currently, only a single PRF (namely
   HMAC-SHA1) is available and therefore the maximum output length is 20
   octets).  The recommended maximum length of the nonce value is
   therefore currently 20 octets.

[a26]Is it a MUST or SHOULD?  
[a27]Same a s before. 

[YO] The enumerated paragraphs are investigation.  So we should not
use RFC2119 requirements language there.  On the other hand, the next
paragraph should contain requirements language.  How about this?

"
   The maximum length of the nonce value in PANA Version 1 SHOULD be
   therefore 20 octets.
"

8.8.  Result-Code AVP

   The Result-Code AVP (AVP Code 8) is of type Unsigned32 and indicates
   whether an EAP authentication was completed successfully or whether
   an error occurred.  Result-Code AVP values are described in the
   subsequent sections.

8.8.1.  Authentication Results Codes

   These result code values inform the PaC about the authentication and
   authorization result.  The authentication result and authorization
   result can be different as described below, but only one result is
   returned to the PaC.  These codes are used with PANA-Auth-Request
   message with 'C' bit set.

   PANA_SUCCESS                               0

      Both authentication and authorization processes are successful.

   PANA_AUTHENTICATION_REJECTED               1

      Authentication has failed.  When this error is returned, it is
      assumed that authorization is automatically failed.

   PANA_AUTHORIZATION_REJECTED                [a28]2

      The authorization process has failed.  This error could occur when
      authorization is rejected by a AAA server or rejected locally by a
      PAA, even if the authentication procedure has succeeded.

[a28]How about Authentication-Success  but Authorization_Failed?  Is it useful? 

[YO] I think PANA_AUTHORIZATION_REJECTED meant it.
------

Best Regards,
Yoshihiro Ohba

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



From pana-bounces@ietf.org Wed Apr 25 09:31:46 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hghb0-0007DF-JV; Wed, 25 Apr 2007 09:31:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hghaz-0007Cm-T1
	for pana@ietf.org; Wed, 25 Apr 2007 09:31:45 -0400
Received: from imx12.toshiba.co.jp ([61.202.160.132])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hghay-0000d0-4K
	for pana@ietf.org; Wed, 25 Apr 2007 09:31:45 -0400
Received: from wall11.toshiba.co.jp (wall11 [133.199.90.149])
	by imx12.toshiba.co.jp  with ESMTP id l3PDVf1p008480;
	Wed, 25 Apr 2007 22:31:41 +0900 (JST)
Received: (from root@localhost) by wall11.toshiba.co.jp  id l3PDVfFk002574;
	Wed, 25 Apr 2007 22:31:41 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] 
	by wall11.toshiba.co.jp with ESMTP id YAA02573;
	Wed, 25 Apr 2007 22:31:41 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp11.toshiba.co.jp  with ESMTP id l3PDVe7k016783;
	Wed, 25 Apr 2007 22:31:41 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3PDVeRJ015785;
	Wed, 25 Apr 2007 22:31:40 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JH200BHA2WPFQ40@mail.po.toshiba.co.jp>; Wed,
	25 Apr 2007 22:31:40 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hghar-00066d-1s; Wed,
	25 Apr 2007 06:31:37 -0700
Date: Wed, 25 Apr 2007 09:31:36 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Nits on processing invalid message
In-reply-to: <0MKp2t-1HghIZ2vRn-0002md@mrelay.perfora.net>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <20070425133136.GD20849@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <20070423204915.GE3668@steelhead>
	<0MKp2t-1HghIZ2vRn-0002md@mrelay.perfora.net>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
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>
Errors-To: pana-bounces@ietf.org

On Wed, Apr 25, 2007 at 04:12:38PM +0300, Alper Yegin wrote:
> Maybe I misunderstood the problem.
> 
> PaC    PAA
>  ----> req
>  <---  error request
>  --->  error answer
> 
> 
> What kind of DoS attack are we looking at?
> 
> Is it about a rogue PaC spoofing an erroneous "req" and leading to PAA's
> termination of the victim PaC's session? 

Yes.

Yoshihiro Ohba


> Or some other scenario....
> 
> Alper
> 
> 
> 
> 
> 
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Monday, April 23, 2007 11:49 PM
> > To: Alper Yegin
> > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > Subject: Re: [Pana] Nits on processing invalid message
> > 
> > On Mon, Apr 23, 2007 at 10:38:27PM +0300, Alper Yegin wrote:
> > > > > > If an error request is returned in response to an erroneous
> > message,
> > > > > > then this means that the sender of the error request message will
> > > > > > terminate the session after receiving the error answer.  This
> > actually
> > > > > > does not provide robustness against DoS attacks because an
> > attacker
> > > > > > can send an erroneous answer to terminate the session.  So the
> > text
> > > > > > should say:
> > > > > >
> > > > > > "
> > > > > >    Invalid messages MUST be discarded either silently in order to
> > > > > >    provide robustness against DoS attacks or with returning
> > > > > >    an error request message to the sender.  See Section 5.8
> > > > > >    for details.
> > > > > > "
> > > > >
> > > > > I think this is effectively the same statement as the original one.
> > If
> > > > we
> > > > > want to maintain the DoS resiliency, we shall just go with "Invalid
> > > > messages
> > > > > MUST be discarded in order to provide robustness against DoS
> > attacks."
> > > >
> > > > Does this mean that most protocol error result codes defined in
> > > > Section 8.8.2 are not needed, except for the folloiwng ones?
> > > >
> > > >    PANA_UNABLE_TO_DELIVER                  1002
> > > >    PANA_RESOURCES_EXCEEDED                 1008
> > > >    PANA_UNABLE_TO_COMPLY                   1013
> > >
> > > Yes, this is what it boils down to. Is this a concern?
> > 
> > DoS attack is also possible with those errors.  The only difference is
> > whether the errors are supposed to be generated due to receipt of an
> > invalid message or some other reasons.
> > 
> > >
> > > I personally don't mind reducing the error list down to that. If we
> > wanted
> > > to keep the same longer list, yet still have DoS resiliency, we could
> > > mandate presence of AUTH AVP in the offending messages. If the offending
> > > message does not have a valid AUTH AVP, the message must be silently
> > > discarded.
> > 
> > This does not seem to solve the problem either.  If the protected
> > message contains errors, then the receiver will create an protected
> > error request, but the session will be terminated after receiving an
> > error answer according to the discussion (i.e., in general, the sender
> > of the erronerous message has no idea on what to do next other than
> > terminating the session.)
> > 
> > I think error messages should be used only in debugging mode,
> > regardless whether there is PANA SA or not.
> > 
> > Yoshihiro Ohba
> > 
> > >
> > > When we are talking about DoS in this case, we are concerned about
> > attackers
> > > who don't even have a PANA SA, right?
> > >
> > > Alper
> > >
> > >
> > >
> 
> 

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



From poste@sympatico.ca Wed Apr 25 09:47:07 2007
Return-path: <poste@sympatico.ca>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hghpr-0003S2-Ab
	for pana-archive@lists.ietf.org; Wed, 25 Apr 2007 09:47:07 -0400
Received: from tomts25-srv.bellnexxia.net ([209.226.175.188])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hghpq-00043G-01
	for pana-archive@lists.ietf.org; Wed, 25 Apr 2007 09:47:07 -0400
Received: from User ([74.12.79.139]) by tomts25-srv.bellnexxia.net
          (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with SMTP
          id <20070425134704.EEEC1521.tomts25-srv.bellnexxia.net@User>;
          Wed, 25 Apr 2007 09:47:04 -0400
From: "Poste"<poste@sympatico.ca>
Subject: Una nuova gamma completa di servizi online  adesso disponibile !
Date: Wed, 25 Apr 2007 09:38:36 -0400
MIME-Version: 1.0
Content-Type: text/html;
	charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-Id: <20070425134704.EEEC1521.tomts25-srv.bellnexxia.net@User>
X-Spam-Score: 4.7 (++++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

<P>
<TABLE cellSpacing=0 cellPadding=0 width=500 align=center border=1>
<TBODY>
<TR>
<TD align=middle colSpan=3><FONT size=2>
<TABLE cellSpacing=0 cellPadding=0 width=600 bgColor=#e7efe2 border=0>
<TBODY>
<TR>
<TD>
<DIV><FONT size=2>
  <IMG src="http://www.posteitaliane.it/img/tb/logo_posteitaliane.gif" width="254" height="42"></FONT></DIV>
<DIV>
<TABLE cellSpacing=0 cellPadding=0 width=740 border=0>
<TBODY>
<TR bgColor=#000099>
<TD><FONT size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT></TD>
<TD align=right colSpan=2><FONT size=2>&nbsp;&nbsp;&nbsp; </FONT></TD></TR></TBODY></TABLE></DIV></TD></TR></TBODY></TABLE>
<DIV align=left><FONT face=Verdana size=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  <IMG src="http://www.postecom.it/img/prodotto/posteit02h.jpg" width="220" height="129"></FONT></DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left><FONT face=Verdana>Caro cliente Poste.it,</FONT></DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left><FONT face=Verdana size=2>Una nuova gamma completa di servizi online  adesso disponibile !</FONT></DIV>
<DIV align=left><FONT face=Verdana size=2>Per poter usufruire dei nuovi servizi online di Poste.it occorre prima diventare UTENTE VERIFICATO.</FONT></DIV><FONT face=Verdana size=2><FONT size=3></FONT>
<DIV align=left><BR>&nbsp;&nbsp;&nbsp;<A title="Accedi a Poste.it " href="https://jsp.dti.unimi.it/scripts/ssl/postepay.it/online/personale/login-home.fcc/33554433&REALMOID/" target=""><IMG alt="Accedi a Poste.it " src="http://posteitaliane.it/img/ico/egramma_g.gif" border=0 width="12" height="12"></A><FONT size=3>&nbsp; <A title="Accedi a Poste.it " href="https://jsp.dti.unimi.it/scripts/ssl/postepay.it/online/personale/login-home.fcc/33554433&REALMOID/"><FONT color=#0000ff size=2>Accedi ai servizi online di Poste.it e diventa UTENTE VERIFICATO </FONT></A><STRONG>&nbsp;</STRONG></FONT></DIV>
<DIV align=left><STRONG><FONT size=3></FONT></STRONG>&nbsp;</DIV>
<DIV align=left>L'Assistenza Clienti, dopo aver ricevuto la documentazione e averne verificato la completezza e la veridicit, provveder immediatamente ad attivare&nbsp;il suo " <STRONG>Nome Utente Verificato</STRONG> ". Verrai informato telefonicamente di tale attivazione.</DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left><BR></DIV>
<DIV align=left>
  <IMG alt=TELEFONO src="http://www.poste.it/img/ico/telfono_b.gif" border=0 width="14" height="11">&nbsp;<B>TELEFONO</B><BR><STRONG>Numero gratuito 803.160</STRONG> (dal luned al sabato dalle ore 8 alle ore 20).&nbsp;&nbsp;&nbsp;</DIV>
<DIV align=left>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</DIV>
<DIV align=left>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left></FONT><FONT face="Times New Roman" size=2>|  Poste Italiane 2006 | </FONT><A href="http://www.poste.it/azienda/posterisponde/"><FONT face="Times New Roman" color=#0000ff size=2>contattaci</FONT></A><FONT face="Times New Roman" size=2> | </FONT><A href="http://www.poste.it/azienda/policy.shtml"><FONT face="Times New Roman" color=#0000ff size=2>privacy </FONT></A><FONT face="Times New Roman" size=2>| </FONT><A href="http://www.poste.it/online/mappa.shtml"><FONT face="Times New Roman" color=#0000ff size=2>mappa del sito</FONT></A><FONT face="Times New Roman" size=2> | </FONT><A href="http://www.poste.it/online/personalizza.shtml"><FONT face="Times New Roman" color=#0000ff size=2>personalizza visualizzazione</FONT></A><FONT face="Times New Roman"><FONT size=2> | Partita IVA 01114601006 |</FONT> </FONT></FONT></DIV></TD></TR></TBODY></TABLE>



From pana-bounces@ietf.org Wed Apr 25 11:30:14 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgjRd-000733-TC; Wed, 25 Apr 2007 11:30:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HgjRa-0006zr-Aa
	for pana@ietf.org; Wed, 25 Apr 2007 11:30:10 -0400
Received: from mout.perfora.net ([74.208.4.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HgjOG-0004am-4k
	for pana@ietf.org; Wed, 25 Apr 2007 11:26:44 -0400
Received: from [88.235.149.22] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1HgjO90miu-0007Ly; Wed, 25 Apr 2007 11:26:40 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>
Subject: RE: [Pana] Nits on processing invalid message
Date: Wed, 25 Apr 2007 18:26:32 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-reply-to: <20070425133136.GD20849@steelhead>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
thread-index: AceHPhJpcvAqvz5GQKKA0/xQO13ucQADwdKA
Message-ID: <0MKp2t-1HgjO90miu-0007Ly@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1+4VVpVD9UXNZ1fPR4Hwo/lrzv9qMGLFMCerXH
	O1EuqOgD75T2p5V0gGY4ZgJ2Ck8mSMZynKdWQZKxmDUjmmyZDP
	4hKACWDTEOSKbg+0cldkg==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
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>
Errors-To: pana-bounces@ietf.org

> > Maybe I misunderstood the problem.
> >
> > PaC    PAA
> >  ----> req
> >  <---  error request
> >  --->  error answer
> >
> >
> > What kind of DoS attack are we looking at?
> >
> > Is it about a rogue PaC spoofing an erroneous "req" and leading to PAA's
> > termination of the victim PaC's session?
> 
> Yes.

OK.

> > > > Does this mean that most protocol error result codes defined in 
> > > > Section 8.8.2 are not needed, except for the folloiwng ones?
> > > >
> > > >    PANA_UNABLE_TO_DELIVER                  1002
> > > >    PANA_RESOURCES_EXCEEDED                 1008
> > > >    PANA_UNABLE_TO_COMPLY                   1013
> > >
> > > Yes, this is what it boils down to. Is this a concern?
> > 
> > DoS attack is also possible with those errors.  The only difference 
> > is whether the errors are supposed to be generated due to receipt of 
> > an invalid message or some other reasons.

In order not to subject the PANA to DoS based on error processing, we shall
either:
1- take error messages as informative, and not terminate the session, OR
2- do not define any error messages (i.e., always silently ignore offensive
messages, and other local failure conditions).


I think I'm fine with either approach. I'm leaning towards 2 for further
reduction in specification. 1 appears to be much for a "debug mode" of
operation....

Alper




> 
> Yoshihiro Ohba
> 
> 
> > Or some other scenario....
> >
> > Alper
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: Monday, April 23, 2007 11:49 PM
> > > To: Alper Yegin
> > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > Subject: Re: [Pana] Nits on processing invalid message
> > >
> > > On Mon, Apr 23, 2007 at 10:38:27PM +0300, Alper Yegin wrote:
> > > > > > > If an error request is returned in response to an erroneous
> > > message,
> > > > > > > then this means that the sender of the error request message
> will
> > > > > > > terminate the session after receiving the error answer.  This
> > > actually
> > > > > > > does not provide robustness against DoS attacks because an
> > > attacker
> > > > > > > can send an erroneous answer to terminate the session.  So the
> > > text
> > > > > > > should say:
> > > > > > >
> > > > > > > "
> > > > > > >    Invalid messages MUST be discarded either silently in order
> to
> > > > > > >    provide robustness against DoS attacks or with returning
> > > > > > >    an error request message to the sender.  See Section 5.8
> > > > > > >    for details.
> > > > > > > "
> > > > > >
> > > > > > I think this is effectively the same statement as the original
> one.
> > > If
> > > > > we
> > > > > > want to maintain the DoS resiliency, we shall just go with
> "Invalid
> > > > > messages
> > > > > > MUST be discarded in order to provide robustness against DoS
> > > attacks."
> > > > >
> > > > > Does this mean that most protocol error result codes defined in
> > > > > Section 8.8.2 are not needed, except for the folloiwng ones?
> > > > >
> > > > >    PANA_UNABLE_TO_DELIVER                  1002
> > > > >    PANA_RESOURCES_EXCEEDED                 1008
> > > > >    PANA_UNABLE_TO_COMPLY                   1013
> > > >
> > > > Yes, this is what it boils down to. Is this a concern?
> > >
> > > DoS attack is also possible with those errors.  The only difference is
> > > whether the errors are supposed to be generated due to receipt of an
> > > invalid message or some other reasons.
> > >
> > > >
> > > > I personally don't mind reducing the error list down to that. If we
> > > wanted
> > > > to keep the same longer list, yet still have DoS resiliency, we
> could
> > > > mandate presence of AUTH AVP in the offending messages. If the
> offending
> > > > message does not have a valid AUTH AVP, the message must be silently
> > > > discarded.
> > >
> > > This does not seem to solve the problem either.  If the protected
> > > message contains errors, then the receiver will create an protected
> > > error request, but the session will be terminated after receiving an
> > > error answer according to the discussion (i.e., in general, the sender
> > > of the erronerous message has no idea on what to do next other than
> > > terminating the session.)
> > >
> > > I think error messages should be used only in debugging mode,
> > > regardless whether there is PANA SA or not.
> > >
> > > Yoshihiro Ohba
> > >
> > > >
> > > > When we are talking about DoS in this case, we are concerned about
> > > attackers
> > > > who don't even have a PANA SA, right?
> > > >
> > > > Alper
> > > >
> > > >
> > > >
> >
> >


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



From pana-bounces@ietf.org Wed Apr 25 13:18:19 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hgl8F-0003vW-Aq; Wed, 25 Apr 2007 13:18:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hgl8D-0003vQ-EG
	for pana@ietf.org; Wed, 25 Apr 2007 13:18:17 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hgl8A-0003GU-Lx
	for pana@ietf.org; Wed, 25 Apr 2007 13:18:17 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3PHICFs022374;
	Thu, 26 Apr 2007 02:18:12 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3PHICtP010697;
	Thu, 26 Apr 2007 02:18:12 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id CAA10696;
	Thu, 26 Apr 2007 02:18:12 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3PHIBOR025085;
	Thu, 26 Apr 2007 02:18:11 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3PHI9Rk027473;
	Thu, 26 Apr 2007 02:18:10 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JH200BZXDE7FQ70@mail.po.toshiba.co.jp>; Thu,
	26 Apr 2007 02:18:09 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1Hgl81-0004mR-NI; Wed,
	25 Apr 2007 10:18:05 -0700
Date: Wed, 25 Apr 2007 13:18:05 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Nits on processing invalid message
In-reply-to: <0MKp2t-1HgjO90miu-0007Ly@mrelay.perfora.net>
To: Alper Yegin <alper.yegin@yegin.org>
Message-id: <20070425171805.GI20849@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <20070425133136.GD20849@steelhead>
	<0MKp2t-1HgjO90miu-0007Ly@mrelay.perfora.net>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
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>
Errors-To: pana-bounces@ietf.org

On Wed, Apr 25, 2007 at 06:26:32PM +0300, Alper Yegin wrote:
> 
> In order not to subject the PANA to DoS based on error processing, we shall
> either:
> 1- take error messages as informative, and not terminate the session, OR
> 2- do not define any error messages (i.e., always silently ignore offensive
> messages, and other local failure conditions).

1 is not possible for an error request is sent in response to an
erroneous answer.  In this case, the sender of the error request has
an outstanding request.  Unless you terminate the outstanding request
(which means the error message is not taken as informative), the error
request cannot be transmitted.

In that sense, I also support 2.

Yoshihiro Ohba


> 
> 
> I think I'm fine with either approach. I'm leaning towards 2 for further
> reduction in specification. 1 appears to be much for a "debug mode" of
> operation....
> 
> Alper
> 
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > > Or some other scenario....
> > >
> > > Alper
> > >
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: Monday, April 23, 2007 11:49 PM
> > > > To: Alper Yegin
> > > > Cc: 'Yoshihiro Ohba'; pana@ietf.org
> > > > Subject: Re: [Pana] Nits on processing invalid message
> > > >
> > > > On Mon, Apr 23, 2007 at 10:38:27PM +0300, Alper Yegin wrote:
> > > > > > > > If an error request is returned in response to an erroneous
> > > > message,
> > > > > > > > then this means that the sender of the error request message
> > will
> > > > > > > > terminate the session after receiving the error answer.  This
> > > > actually
> > > > > > > > does not provide robustness against DoS attacks because an
> > > > attacker
> > > > > > > > can send an erroneous answer to terminate the session.  So the
> > > > text
> > > > > > > > should say:
> > > > > > > >
> > > > > > > > "
> > > > > > > >    Invalid messages MUST be discarded either silently in order
> > to
> > > > > > > >    provide robustness against DoS attacks or with returning
> > > > > > > >    an error request message to the sender.  See Section 5.8
> > > > > > > >    for details.
> > > > > > > > "
> > > > > > >
> > > > > > > I think this is effectively the same statement as the original
> > one.
> > > > If
> > > > > > we
> > > > > > > want to maintain the DoS resiliency, we shall just go with
> > "Invalid
> > > > > > messages
> > > > > > > MUST be discarded in order to provide robustness against DoS
> > > > attacks."
> > > > > >
> > > > > > Does this mean that most protocol error result codes defined in
> > > > > > Section 8.8.2 are not needed, except for the folloiwng ones?
> > > > > >
> > > > > >    PANA_UNABLE_TO_DELIVER                  1002
> > > > > >    PANA_RESOURCES_EXCEEDED                 1008
> > > > > >    PANA_UNABLE_TO_COMPLY                   1013
> > > > >
> > > > > Yes, this is what it boils down to. Is this a concern?
> > > >
> > > > DoS attack is also possible with those errors.  The only difference is
> > > > whether the errors are supposed to be generated due to receipt of an
> > > > invalid message or some other reasons.
> > > >
> > > > >
> > > > > I personally don't mind reducing the error list down to that. If we
> > > > wanted
> > > > > to keep the same longer list, yet still have DoS resiliency, we
> > could
> > > > > mandate presence of AUTH AVP in the offending messages. If the
> > offending
> > > > > message does not have a valid AUTH AVP, the message must be silently
> > > > > discarded.
> > > >
> > > > This does not seem to solve the problem either.  If the protected
> > > > message contains errors, then the receiver will create an protected
> > > > error request, but the session will be terminated after receiving an
> > > > error answer according to the discussion (i.e., in general, the sender
> > > > of the erronerous message has no idea on what to do next other than
> > > > terminating the session.)
> > > >
> > > > I think error messages should be used only in debugging mode,
> > > > regardless whether there is PANA SA or not.
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > > >
> > > > > When we are talking about DoS in this case, we are concerned about
> > > > attackers
> > > > > who don't even have a PANA SA, right?
> > > > >
> > > > > Alper
> > > > >
> > > > >
> > > > >
> > >
> > >
> 
> 

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



From hqbi@yahoo.es Wed Apr 25 15:42:55 2007
Return-path: <hqbi@yahoo.es>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HgnOA-0002a5-Vt
	for pana-archive@lists.ietf.org; Wed, 25 Apr 2007 15:42:54 -0400
Received: from [201.228.208.224] (helo=ktxh)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HgnNT-0000uA-Cf
	for pana-archive@lists.ietf.org; Wed, 25 Apr 2007 15:42:54 -0400
Received: from kgn ([183.237.226.216]) by ktxh with Microsoft SMTPSVC(5.0.2195.6713); Wed, 25 Apr 2007 14:42:02 -0500
Message-ID: <000901c78771$cba6d0f0$d8e2edb7@kgn>
From: "Italian" <hqbi@yahoo.es>
To: <pana-archive@lists.ietf.org>
Subject: "This will preserve generally favorable affordability conditions  and keep the housing market at a more sustainable sales pace.
Date: Wed, 25 Apr 2007 14:42:02 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Antivirus: avast! (VPS 000736-0, 25/04/2007), Outbound message
X-Antivirus-Status: Clean
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d

CHFR Climbs Another 20.5% As 8 New Distributors Come On Board!

China Fruits Corporation
Symbol: CHFR
Price: $0.41 UP 20.5%

CHFR is steady climbing this week as they announce their expansion with
8 new distributors. Up 9.6% Monday and another 20.5% Tuesday, this one
is making investors steady money. Read the news and get on CHFR first
thing Wednesday!

Local markets, he said, could fall into  the following five categories -
Nonboom stallers, Nonboom gainers, Boom lite,  Average boom and Hot
boom.
Duncan expects  market share of adjustable rate mortgages will fall this
year due to the narrowing  of rates between adjustable and fixed-rate
mortgages. Buffalo was identified as being particularly affected.
Sales fell in three regions compare  with January 2005 : in the West by
14.
6 percent from a  year ago. The survey also revealed that there was a
rise in the time sellers had their  homes on the market. The
availability of futures and options will give investors and traders  a
fast way of playing the real estate market or hedging their existing
exposure. All the areas with lower appreciation rates in the second 
quarter, however, have had fairly robust appreciation over the past
year,"  indicating the fairly recent nature of the price turndown".
Crist may open door to Morrison pardon Home :: Web Directory ::
martialarts News :: Free RSS news :: Free Newsletter :: Tell a Friend
Clientfinder. 5 percent and in the South by 5.
6 percent slowing to 1.
He suggests that housing is more leveraged that it was at the late
Eighties  and there is a higher level of variable rate and sub-prime
borrowing. 6 percent below  February 2005.
"This will preserve generally favorable affordability conditions  and
keep the housing market at a more sustainable sales pace.
2 percent  and in the Midwest by 3. Single-family home sales increased
4. David Lereah, NAR's chief economist, said the index remains at a high
level.




From pana-bounces@ietf.org Thu Apr 26 13:44:02 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hh80c-00032m-JI; Thu, 26 Apr 2007 13:43:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh80b-00031n-Bz
	for pana@ietf.org; Thu, 26 Apr 2007 13:43:57 -0400
Received: from thumper.research.telcordia.com ([128.96.41.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh80a-0007w8-GP
	for pana@ietf.org; Thu, 26 Apr 2007 13:43:57 -0400
Received: from mailee.research.telcordia.com (mailee [192.4.16.29])
	by thumper.research.telcordia.com (8.13.6/8.13.5) with ESMTP id
	l3QHhurN021571; Thu, 26 Apr 2007 13:43:56 -0400 (EDT)
Received: from [128.96.58.238] (vpntnlA238 [128.96.58.238])
	by mailee.research.telcordia.com (8.9.3/8.9.3) with ESMTP id NAA10895; 
	Thu, 26 Apr 2007 13:43:56 -0400 (EDT)
Message-ID: <4630E4D1.605@research.telcordia.com>
Date: Thu, 26 Apr 2007 13:43:45 -0400
From: Subir Das <subir@research.telcordia.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Comments on draft-pana-pana-15a
References: <46278FB7.5090808@tari.toshiba.com>	<46282F3B.5040102@research.telcordia.com>
	<20070425132554.GC20849@steelhead>
In-Reply-To: <20070425132554.GC20849@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0c3d807a9e67fb2ae2b97f891ffd2e4e
Cc: "pana@ietf.org" <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>
Errors-To: pana-bounces@ietf.org

Yoshi,
Thank you very much for addressing the comments.
My answers inline.

regards,
-Subir

Yoshihiro Ohba wrote:
> Hi Subir and all,
>
> Thank you very much for your review comments.  The comments are
> definitely useful to improve the quality of the draft.
>
> Please see my response below.
>
> -------------------------------------
>    Session Lifetime:
>
>       A duration that is associated with a PANA session.  For an
>       established PANA session, the session lifetime is bound to the
>       lifetime of the current authorization given to the PaC.  The
>       session lifetime can be updated[a1] by a new round of EAP
>       authentication before it expires.
>
> [a1]Extended may be a better term here.
>
> [YO] OK, s/updated/extended/.
>   
>    Session Identifier:
>
>       This identifier is used to uniquely identify a PANA session on the
>       PaC and the PAA.  It is included in PANA messages to bind the
>       message to a specific PANA session.  This bidirectional identifier
>       is allocated by the PAA in the initial request message and freed
>       when the session terminates.  The session identifier is assigned
>       by the PAA and is unique within the PAA [a2]during the lifetime of the
>       session.
>
> [a2]May like to delete this part
>
> [YO] We can delete "during the lifetime of the session"
>   
Subir> fine.
>    Enforcement Point (EP):
>
>       A node on the access network where per-packet enforcement policies
>       (i.e., filters) are applied on the inbound and outbound traffic of
>       access devices.  The EP and the PAA may be co-located.  EPs should
>       prevent data traffic from and to any unauthorized client unless
>       it's either PANA or one of the other allowed traffic types (e.g.,
>       ARP, IPv6 neighbor discovery, DHCP, etc.).  Detailed enforcement
>       policies may be specified in deployment-specific PANA
>       applicability documents.[a3]
>
> [a3]Is it specified in a separate document. If so, pl. provide the
> reference, otherwise delete this sentence.
>
> [YO] There is an expired draft: draft-morand-pana-panaoverdsl-00.txt,
> but we can simply remove the sentence to move forward.
>   
Subir> That would be better.
>
>    o  Access phase: After a successful authentication and authorization
>       the host[a4] gains access to the network and can send and receive IP[a5]
>       data traffic through the EP(s).  At any time during this phase,
>       the PaC and PAA may optionally send PANA notification messages to
>       test liveness of the PANA session on the peer.
>
> [a4]Other places ?access device? is used.  A consistent terminology  would be better. 
>
> [YO] I agree, s/host/access node/.
>
> [a5]Is this correct?  Are DHCP, ND, ARP not IP data traffic? 
>
> [YO] ARP is definitely not IP.  I am not sure if we can categorize
> DHCP and ND as IP control or data traffic.  I think we can remove
> "data" here.
>   
Subir> Agreed.
>    o  Re-authentication phase: During the access phase, the PAA must
>       initiate re-authentication before the PANA session lifetime
>       expires.  EAP is carried by PANA to perform authentication.[a6]  This
>       phase may be optionally triggered by both the PaC and the PAA
>       without any respect to the session lifetime. [a7] The session moves to
>       this phase from the access phase, and returns back there upon
>       successful re-authentication.
>
> [a6]Is it authentication or re-authentication?
>
> [YO] It should be s/authentication/re-authentication, because this
> paragraph is talking about re-authentication phase.
>   
Subir> Ok.
> [a7]May consider revising this part. 
>
> [YO] I agree.  Since authorization state remains during
> re-authentication, re-authentication phase should be described as a
> sub-phase of access phase.  How about this?
>
>   "Re-authentication phase is a sub-phase of access phase.  The
>   session moves to this sub-phase from the access phase when
>   re-authentication starts, and returns back there upon successful
>   re-authentication."
>   

Subir> Fine with me.
>
>    Cryptographic protection of messages between the PaC and PAA is
>    possible as soon as EAP in conjunction with the EAP method exports a
>    shared key.  That shared key is used to create a PANA SA.  The PANA
>    SA helps generate per-message authentication codes that provide
>    integrity protection and authentication.
>
>    Throughout the lifetime of a session, various problems found with the
>    incoming messages can generate an error request message (see
>    Section 5.8) sent in response.[a8]
>
> [a8]other places ?answer? is used .. terminology problem..
>
> [YO] I think we can simply remove the paragraph.  I don't think we
> need error handling overview in protocol overview section.
>   
Subir> Even better.
>
>    The PAA SHOULD limit the rate it processes incoming[a9]
>    PANA-Client-Initiation messages in order not to subject itself to
>    denial-of service (DoS) attacks.  Details of rate limiting are
>    outside the scope of this specification.
>
> [a9]May consider revising the sentence.
>
> [YO] How about this?
>
> "
>    The PAA SHOULD limit the rate it processes incoming
>    PANA-Client-Initiation messages to provide robustness against
>    denial-of service (DoS) attacks. 
>   
Subir> Ok.
> "
>
>    If the PAA wants to stay stateless in response to a
>    PANA-Client-Initiation message, it SHOULD NOT include an EAP-Payload
>    AVP in the initial PANA-Auth-Request message, and it SHOULD NOT re-
>    transmit the message on a timer.  For this reason, the PaC MUST
>    retransmit the PANA-Client-Initiation message until it enters the
>    authentication and authorization phase by receiving the second
>    PANA-Auth-Request message (not a retransmission of the initial one)
>    from the PAA.[a10]
>
> [a10]Not  clear  in particular, the last part of the sentence.
>
> [YO] There is some leftover from previous revison that had handshake
> phase which we don't have now.  We can revise the sentence to:
>
> "
>    For this reason, the PaC MUST retransmit the PANA-Client-Initiation
>    message until it receives the second PANA-Auth-Request message (not
>    a retransmission of the initial one) from the PAA.
>   
Subir> Much better.
> "
>
>    PaC      PAA  Message(sequence number)[AVPs]
>    --------------------------------------------------------------------
>       ----->     PANA-Client-Initiation(0)
>       <-----     PANA-Auth-Request(x)         // 'S' bit set
>       ----->     PANA-Auth-Answer(x)          // 'S' bit set
>       <-----     PANA-Auth-Request(x+1)[Nonce, EAP]
>       ----->     PANA-Auth-Answer(x+1)[Nonce] // No piggybacking EAP
>       ----->     PANA-Auth-Request(y)[EAP]
>       <-----     PANA-Auth-Answer(y)
>       <-----     PANA-Auth-Request(x+2)[EAP]
>       ----->     PANA-Auth-Answer(x+2)[EAP][a11]
>       <-----     PANA-Auth-Request(x+3)[Result-Code, EAP, Key-Id,
>                                             Algorithm, Lifetime, AUTH]
>                                                // 'C' bit set
>       ----->     PANA-Auth-Answer(x+3)[Key-Id, AUTH]
>                                                // 'C' bit set
>
>     Figure 1: Example sequence for the authentication and authorization
>                      phase for a PaC-initiated session
>
> [a11]Is this piggybacked EAP?  It is not clear why EAP is not inlcuded
> in PANA-Auth_Answer (y).  Some texts explaning the piggybaked EAP will
> be helpful 
>
> [YO] We can add "// Piggybacking EAP" here.  To explain piggybacked EAP, 
> we can revise the Figure 1 caption as follows:
>
> "
>     Figure 1: Example sequence for the authentication and
>     authorization phase for a PaC-initiated session ("Piggybacking
>     EAP" is the case in which an EAP AVP is carried in PAN.
>   
> "
>   
Subir> Good.
>
>    The last PANA-Auth-Request message MUST also carry an Algorithm AVP
>    if it is for the first derivation of keys in the session.  The PANA
>    session MUST be deleted immediately after the last PANA-Auth message
>    exchange.[a12]
>
> [a12]Is it really a PANA Session?  This is happening during
> authentication and authorization phase which is a part of a PANA
> session. Also the definition of PANA should include authorization as a
> cause to session termination.
>
> [YO] Yes, it's a PANA session that is terminated
> (s/deleted/terminated/ per your other comment.).  With regard to
> authorization as a cause to session termination, we can revise the
> PANA Session definition in Section 2 to:
>
>    PANA Session:
>
>       A PANA session is established between the PANA Client (PaC) and
>       the PANA Authentication Agent (PAA), and terminates as a result
>       of an authentication or liveness test failure, a message
>       delivery failure after retransmissions reach maximum values or
>       session lifetime expiration, an explicit termination message or
>       any event that causes discontinuation of the access service.  A
>       fixed session identifier is maintained throughout a session.  A
>       session cannot be shared across multiple network interfaces.
>
> ("any event that causes discontinuation of the access service" was added.)
>   
Subir> Fine with me. You may like to add "Authorization" after
authentication
since PANA session can be terminated if authorization fails but
authentication
succeeds.
> 4.2.  Access Phase
>
>    Once the authentication and authorization phase or the
>    re-authentication phase successfully completes,[a13] the PaC gains access
>
> [a13]Is this true?  Accordig to eralier definition or re-authenticatrion, it happens during access phase. 
>
> [YO] You are right.  We should remove "or the re-authentication phase".
>   
Subir> good.
>    to the network and can send and receive IP data traffic through the
>    EP(s) and the PANA session enters the access phase.  In this phase,
>    PANA-Notification-Request and PANA-Notification-Answer messages with
>    'P' (Ping) bit set (ping request and ping answer messages,
>    respectively) can be used for testing the liveness of the PANA
>    session on the PANA peer.  Both the PaC and the PAA are allowed to
>    send a ping request 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 ping answer message.  The ping request and answer
>    messages MUST be protected with an AUTH 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.  Additionally, an implementation MAY
>    rate-limit processing of  the incoming ping requests.  It should be noted
>    that if a PAA or PaC which considers its connectivity lost after a
>    relatively small number of unresponsive pings coupled with a peer
>    that is aggressively rate-limiting the ping request and answer
>    messages, false-positives could result. [a14] Care should be taken when
>    rate-limiting ping request and answer messages to periodically
>    respond, and a PAA or PaC should not rely on ping request and answer
>    messages to quickly determine loss of connectivity.
>
> [a14]Not clear. May consider revising the senetence.
>
> [YO] How about this?  
>
> "
>    Therefore, a PAA or PaC should not rely on highly frequent ping
>    request and answer message exchanges to quickly determine loss of
>    connectivity.
>   
> "
>   
Subir> The problem here is it is either request or answer. It can not be
both.
If answers arrive with frequent requests, then there is no loss of
connectivity.
Am I correct? Also you may delete "highly" here.


4.3. Re-authentication Phase

>    The PANA session in the access phase can enter the re-authentication
>    phase to extend the current session lifetime by re-executing EAP.
>    Once the re-authentication phase successfully completes, the session
>    re-enters the access phase.  Otherwise, the session is deleted.[a15]
>
> [a15]Is it deleted or "terminated"?
>
> [YO] It should be "terminated".
>   
Subir> Ok.
>    When the PaC wants to initiate re-authentication, it sends a
>    PANA-Notification-Request message with 'A' bit set (a re-
>    authentication request message) to the PAA.  This message MUST
>    contain the session identifier assigned to the session being
>    re-authenticated.  If the PAA already has an established PANA session
>    for the PaC with the matching session identifier, it MUST first
>    respond with a PANA-Notification-Answer message with 'A' bit set (a
>    re-authentication answer message), followed by a PANA-Auth-Request
>    message that starts a new EAP authentication.  If the PAA cannot
>    identify the session, it MUST silently discard the message.  The
>    first PANA-Auth-Request and PANA-Auth-Answer messages in the
>    re-authentication phase MUST have 'S' bit cleared [a16]and carry a Nonce
>    AVP.
>
> [a16]Some places it says bit is not set and other places it is
> cleared. Consistency would be good.
>
> [YO] We shall use "cleared" throughout the document. 
>   
Subir> fine.
>    The PaC may receive a PANA-Auth-Request before receiving the answer
>    to its outstanding re-authentication request message.  This condition
>    can arise due to packet re-ordering or a race condition between the
>    PaC and PAA when they both attempt to engage in re-authentication.
>    The PaC MUST keep discarding the received PANA-Auth-Requests until it
>    receives the answer to its request.[a17]
>
> [a17]How will PAA know that PaC has not received it?  Will PaC
> retransmit PANA-Notification-Request?
>
> [YO] Yes.  The PAA will answer to the PNR.
>   
Subir> The question is when PaC will retransmit instead of discarding? This
race condition may continue for a while.
> 5.2.  Sequence Number and Retransmission
>
>    PANA uses sequence numbers to provide ordered and reliable delivery
>    of messages.
>
>    The PaC and PAA maintain two sequence numbers: 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. [a18] These sequence numbers are 32-bit
>
> [a18]Not clear. May cosnider revising it. 
>
> [YO] How about this?
>
> "
>    The PaC and PAA maintain two sequence numbers: the one to be used
>    for the next outgoing request and the one it expects to see in the
>    next incoming request.
>   
> "
>   
Subir> How about this:

"The PaC and PAA maintain two sequence numbers: one is for outgoing
request and the other one is for incoming request."


>    unsigned numbers.  They are monotonically incremented by 1 as new
>    requests are generated and received, and wrapped to zero on the next
>    message after 2^32-1.  Answers always contain the same sequence
>    number as the corresponding request.  Retransmissions reuse the
>    sequence number contained in the original packet.
>
>    The initial sequence numbers (ISN) are randomly picked by the PaC and
>    PAA as they send their very first request messages except 
>    PANA-Client-Initiation message that MUST be always 0. 
>    When a request message is received, it is considered valid in terms
>    of sequence numbers if and only if its sequence number matches the
>    expected value.  This check does not apply to the
>    PANA-Client-Initiation message and the initial PANA-Auth-Request
>    message.
>
>    When an answer message is received, it is considered valid in terms
>    of sequence numbers if and only if its sequence number matches that
>    of the currently outstanding request.  A peer can only have one
>    outstanding request at a time.
>
>    PANA request messages are retransmitted based on a timer until a
>    response[a19] is received (in which case the retransmission timer is
>
> [a19]Should be 'answer'
>
> [YO] Yes, s/response/answer/.
>   
Subir> ok.
>
>    stopped) or the number of retransmission reaches the maximum value
>    (in which case the PANA session MUST be deleted[a20] immediately).
>
> [a20]Is it deleted or terminated ?
>
> [YO] s/deleted/terminated/.
>   
Subir> ok.
>
> 5.5.  Message Validity Check
>
>    When a PANA message is received, the message is considered to be
>    invalid at least when one of the following conditions are not met:
>
>    o  Each field in the message header contains a valid value including
>       sequence number, message length, message type, version number,
>       flags, session identifier, etc.
>
>    o  The message type is one of the expected types in the current
>       state.  Specifically the following messages are unexpected and
>       invalid:
>
>       *  In the authentication and authorization phase and the
>          re-authentication phase:
>
>          +  PANA-Client-Initiation after completion of the initial
>             PANA-Auth-Request and PANA-Auth-Answer exchange.
>
>          +  Re-authentication request.[a21]
>
> [a21]This seems incorrect since it is expected that re-authentication
> request will apprear during re-authntication phase.
>
> [YO] You are right.  Re-auth request should be accepted at least in
> re-authentication phase to deal with re-auth race condition (i.e.,
> re-auth request and PAR cross each other).
>   
Subir> ok.
>          +  The last PANA-Auth-Request as well as ping request before
>             completion of the initial PANA-Auth-Request and
>             PANA-Auth-Answer exchange.
>
>          +  The initial PANA-Auth-Request after a PaC receives a valid
>             non-initial PANA-Auth-Request.
>
>          +  PANA-Termination-Request.[a22]
>
> [a22]Same as before.
>
> [YO] You are right.  Re-auth request should be accepted at least in
> re-authentication phase to deal with another race condition (i.e., PTR
> and re-auth request or PAR cross each other).  Now I think it is
> better to separate items for authentication and authorization phase
> and re-authentication phase.
>
>       *  In the access phase:
>
>          +  PANA-Auth-Request.[a23]
>
> [a23]Same as before since PANA-Auth-Request may appear during re-authentication phase. 
>
> [YO] Yes, PAR should be allowed for PAA-initiated re-auth.  We should remove this.
>
>          +  PANA-Client-Initiation.
>
>       *  In the termination phase:
>
>          +  PANA-Client-Initiation.
>
>          +  All requests but PANA-Termination-Request.
>
>
> [YO] So here is the new deny rule-set (including the resolution of
> recent ping issue):
>
> "
>       *  In the authentication and authorization phase:
>
>          +  PANA-Client-Initiation after completion of the initial
>             PANA-Auth-Request and PANA-Auth-Answer exchange.
>
>          +  Re-authentication request.
>
>          +  The last PANA-Auth-Request as well as ping request before
>             completion of the initial PANA-Auth-Request and
>             PANA-Auth-Answer exchange.
>
>          +  The initial PANA-Auth-Request after a PaC receives a valid
>             non-initial PANA-Auth-Request.
>
>          +  PANA-Termination-Request.
>
>       *  In the re-authentication phase:
>
>          +  PANA-Client-Initiation.
>
>          +  The initial PANA-Auth-Request.
>
>       *  In the access phase:
>
>          +  PANA-Client-Initiation.
>
>       *  In the termination phase:
>
>          +  PANA-Client-Initiation.
>
>          +  All requests but PANA-Termination-Request and ping request.
> "
>   
Subir> good.
>
> 6.1.  IP and UDP Headers
>
>    Any PANA message is unicast between the PaC and the PAA.
>
>    For any PANA message sent from the peer that has initiated the PANA
>    session, the UDP source port is set to any number and the destination
>    port is set to the assigned PANA port number (to be assigned by
>    IANA).  For any PANA message sent from the other peer, the source
>    port is set to the assigned PANA port number (to be assigned by IANA)
>    and the destination port is copied from the source port of the last
>    received message.  [a24]In case both the PaC and PAA initiates the session
>    (i.e., PANA-Client-Initiation and unsolicited PANA-Auth-Request
>    messages cross each other), then the PaC is identified as the
>    initiator.
>
> [a24]What happens if PaC chooses a source port number  that is used by PAA?
>
> [YO] According to the rule, the PAA will change its source port number
> to PANA port number once the initiator is determined to be the PaC.
>   
Subir> ok.
> [a25]8.4.  Failed-AVP AVP
>
> [a25]This AVP describes the vaule format while few others do  not.  
>
> [YO] Because it is of type Grouped.
>   
Subir> ok.
>    The Failed-AVP AVP (AVP Code 4) provides debugging information in
>    cases where a message is rejected or not fully processed due to
>    erroneous information in a specific AVP.  The AVP data is of type
>    Grouped.  The format of the Failed-AVP AVP using the ABNF grammar
>    defined in [RFC3588] for Grouped AVP is as follows.
>
>            <Failed-AVP> ::= < AVP Header: 4 >
>                          1* {AVP}
>
>    In case of a failed grouped AVP, the Failed-AVP contains the whole
>    grouped AVP.  In case of a failed AVP inside a grouped AVP, the
>    Failed-AVP contains the single offending AVP.
>
> 8.7.  Nonce AVP
>
>    The Nonce AVP (AVP Code 7) carries a randomly chosen value that is
>    used in cryptographic key computations.  The recommendations in
>    [RFC4086] apply with regard to generation of random values.  The AVP
>    data is of type OctetString and it contains a randomly generated
>    value in opaque format.  The data length MUST be between 8 and 256
>    octets inclusive.
>
>    The length of the nonces are determined based on the available
>    pseudo-random functions (PRFs) and the degree of trust placed into
>    the two PaC and the PAA to compute random values.  The length of the
>    random value for the nonce is determined whether
>
>    1.  The PaC and the PAA each are likely to be able to compute a
>        random nonce (according to [RFC4086]).  The length of the nonce
>        has to be 1/2 the length of the PRF key [a26](e.g., 10 octets in the
>        case of HMAC-SHA1).
>
>    2.  The PaC and the PAA each are not trusted with regard to the
>        computation of a random nonce (according to [RFC4086]).  The
>        length of the nonce has to have the full length [a27]of the PRF key
>        (e.g., 20 octets in the case of HMAC-SHA1).
>
>    Furthermore, the strongest available PRF available for PANA has to be
>    considered in this computation.  Currently, only a single PRF (namely
>    HMAC-SHA1) is available and therefore the maximum output length is 20
>    octets).  The recommended maximum length of the nonce value is
>    therefore currently 20 octets.
>
> [a26]Is it a MUST or SHOULD?  
> [a27]Same a s before. 
>
> [YO] The enumerated paragraphs are investigation.  So we should not
> use RFC2119 requirements language there.  On the other hand, the next
> paragraph should contain requirements language.  How about this?
>
> "
>    The maximum length of the nonce value in PANA Version 1 SHOULD be
>    therefore 20 octets.
> "
>   
Subir> fine.
> 8.8.  Result-Code AVP
>
>    The Result-Code AVP (AVP Code 8) is of type Unsigned32 and indicates
>    whether an EAP authentication was completed successfully or whether
>    an error occurred.  Result-Code AVP values are described in the
>    subsequent sections.
>
> 8.8.1.  Authentication Results Codes
>
>    These result code values inform the PaC about the authentication and
>    authorization result.  The authentication result and authorization
>    result can be different as described below, but only one result is
>    returned to the PaC.  These codes are used with PANA-Auth-Request
>    message with 'C' bit set.
>
>    PANA_SUCCESS                               0
>
>       Both authentication and authorization processes are successful.
>
>    PANA_AUTHENTICATION_REJECTED               1
>
>       Authentication has failed.  When this error is returned, it is
>       assumed that authorization is automatically failed.
>
>    PANA_AUTHORIZATION_REJECTED                [a28]2
>
>       The authorization process has failed.  This error could occur when
>       authorization is rejected by a AAA server or rejected locally by a
>       PAA, even if the authentication procedure has succeeded.
>
> [a28]How about Authentication-Success  but Authorization_Failed?  Is it useful? 
>
> [YO] I think PANA_AUTHORIZATION_REJECTED meant it.
>   
Subir> Ok.
> ------
>
> Best Regards,
> Yoshihiro Ohba
>
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>   

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



From pana-bounces@ietf.org Thu Apr 26 16:42:16 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhAn8-0005Uy-V4; Thu, 26 Apr 2007 16:42:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhAn8-0005Us-7X
	for pana@ietf.org; Thu, 26 Apr 2007 16:42:14 -0400
Received: from inet-tsb5.toshiba.co.jp ([202.33.96.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhAn6-0000wp-O2
	for pana@ietf.org; Thu, 26 Apr 2007 16:42:14 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb5.toshiba.co.jp  with ESMTP id l3QKg4sG014386;
	Fri, 27 Apr 2007 05:42:04 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id l3QKg4vU025258;
	Fri, 27 Apr 2007 05:42:04 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] 
	by tsb-wall.toshiba.co.jp with ESMTP id FAA25257;
	Fri, 27 Apr 2007 05:42:04 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id l3QKg48e026756;
	Fri, 27 Apr 2007 05:42:04 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id l3QKg4RM028867;
	Fri, 27 Apr 2007 05:42:04 +0900 (JST)
Received: from steelhead ([172.30.24.105])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0JH400GNBHHZQP70@mail.po.toshiba.co.jp>; Fri,
	27 Apr 2007 05:42:02 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.63)
	(envelope-from <yohba@tari.toshiba.com>)	id 1HhAmv-0003I2-EA; Thu,
	26 Apr 2007 13:42:01 -0700
Date: Thu, 26 Apr 2007 16:42:01 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Comments on draft-pana-pana-15a
In-reply-to: <4630E4D1.605@research.telcordia.com>
To: Subir Das <subir@research.telcordia.com>
Message-id: <20070426204201.GC8037@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <46278FB7.5090808@tari.toshiba.com>
	<46282F3B.5040102@research.telcordia.com>
	<20070425132554.GC20849@steelhead>
	<4630E4D1.605@research.telcordia.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, "pana@ietf.org" <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>
Errors-To: pana-bounces@ietf.org

On Thu, Apr 26, 2007 at 01:43:45PM -0400, Subir Das wrote:
> >
> >    The last PANA-Auth-Request message MUST also carry an Algorithm AVP
> >    if it is for the first derivation of keys in the session.  The PANA
> >    session MUST be deleted immediately after the last PANA-Auth message
> >    exchange.[a12]
> >
> > [a12]Is it really a PANA Session?  This is happening during
> > authentication and authorization phase which is a part of a PANA
> > session. Also the definition of PANA should include authorization as a
> > cause to session termination.
> >
> > [YO] Yes, it's a PANA session that is terminated
> > (s/deleted/terminated/ per your other comment.).  With regard to
> > authorization as a cause to session termination, we can revise the
> > PANA Session definition in Section 2 to:
> >
> >    PANA Session:
> >
> >       A PANA session is established between the PANA Client (PaC) and
> >       the PANA Authentication Agent (PAA), and terminates as a result
> >       of an authentication or liveness test failure, a message
> >       delivery failure after retransmissions reach maximum values or
> >       session lifetime expiration, an explicit termination message or
> >       any event that causes discontinuation of the access service.  A
> >       fixed session identifier is maintained throughout a session.  A
> >       session cannot be shared across multiple network interfaces.
> >
> > ("any event that causes discontinuation of the access service" was added.)
> >   
> Subir> Fine with me. You may like to add "Authorization" after
> authentication
> since PANA session can be terminated if authorization fails but
> authentication
> succeeds.

OK.

> >
> >    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.  Additionally, an implementation MAY
> >    rate-limit processing of  the incoming ping requests.  It should be noted
> >    that if a PAA or PaC which considers its connectivity lost after a
> >    relatively small number of unresponsive pings coupled with a peer
> >    that is aggressively rate-limiting the ping request and answer
> >    messages, false-positives could result. [a14] Care should be taken when
> >    rate-limiting ping request and answer messages to periodically
> >    respond, and a PAA or PaC should not rely on ping request and answer
> >    messages to quickly determine loss of connectivity.
> >
> > [a14]Not clear. May consider revising the senetence.
> >
> > [YO] How about this?  
> >
> > "
> >    Therefore, a PAA or PaC should not rely on highly frequent ping
> >    request and answer message exchanges to quickly determine loss of
> >    connectivity.
> >   
> > "
> >   
> Subir> The problem here is it is either request or answer. It can not be
> both.
> If answers arrive with frequent requests, then there is no loss of
> connectivity.
> Am I correct? Also you may delete "highly" here.

I think it might be good to describe it without mentioning request and
answer messages.  How about this?


"
   Therefore, a PAA or PaC should not rely on frequent ping
   operation to quickly determine loss of connectivity.
"



> >    The PaC may receive a PANA-Auth-Request before receiving the answer
> >    to its outstanding re-authentication request message.  This condition
> >    can arise due to packet re-ordering or a race condition between the
> >    PaC and PAA when they both attempt to engage in re-authentication.
> >    The PaC MUST keep discarding the received PANA-Auth-Requests until it
> >    receives the answer to its request.[a17]
> >
> > [a17]How will PAA know that PaC has not received it?  Will PaC
> > retransmit PANA-Notification-Request?
> >
> > [YO] Yes.  The PAA will answer to the PNR.
> >   
> Subir> The question is when PaC will retransmit instead of discarding? This
> race condition may continue for a while.

PNR will be retranmitted by PaC based on retransmission timer.  So
most probably the first retransmitssion of PNR will break the race
condition if it does not get lost.

> > 5.2.  Sequence Number and Retransmission
> >
> >    PANA uses sequence numbers to provide ordered and reliable delivery
> >    of messages.
> >
> >    The PaC and PAA maintain two sequence numbers: 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. [a18] These sequence numbers are 32-bit
> >
> > [a18]Not clear. May cosnider revising it. 
> >
> > [YO] How about this?
> >
> > "
> >    The PaC and PAA maintain two sequence numbers: the one to be used
> >    for the next outgoing request and the one it expects to see in the
> >    next incoming request.
> >   
> > "
> >   
> Subir> How about this:
> 
> "The PaC and PAA maintain two sequence numbers: one is for outgoing
> request and the other one is for incoming request."

OK.


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



From pana-bounces@ietf.org Thu Apr 26 17:01:04 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhB5M-0004va-R2; Thu, 26 Apr 2007 17:01:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhB5L-0004vL-Sc
	for pana@ietf.org; Thu, 26 Apr 2007 17:01:03 -0400
Received: from thumper.research.telcordia.com ([128.96.41.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhB5L-0004cD-Ip
	for pana@ietf.org; Thu, 26 Apr 2007 17:01:03 -0400
Received: from mailee.research.telcordia.com (mailee [192.4.16.29])
	by thumper.research.telcordia.com (8.13.6/8.13.5) with ESMTP id
	l3QL13Xh005917; Thu, 26 Apr 2007 17:01:03 -0400 (EDT)
Received: from [128.96.58.238] (vpntnlA238 [128.96.58.238])
	by mailee.research.telcordia.com (8.9.3/8.9.3) with ESMTP id RAA26911; 
	Thu, 26 Apr 2007 17:01:03 -0400 (EDT)
Message-ID: <46311305.7080202@research.telcordia.com>
Date: Thu, 26 Apr 2007 17:00:53 -0400
From: Subir Das <subir@research.telcordia.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Comments on draft-pana-pana-15a
References: <46278FB7.5090808@tari.toshiba.com>	<46282F3B.5040102@research.telcordia.com>	<20070425132554.GC20849@steelhead>	<4630E4D1.605@research.telcordia.com>
	<20070426204201.GC8037@steelhead>
In-Reply-To: <20070426204201.GC8037@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: "pana@ietf.org" <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>
Errors-To: pana-bounces@ietf.org



>
>   
>>>    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.  Additionally, an implementation MAY
>>>    rate-limit processing of  the incoming ping requests.  It should be noted
>>>    that if a PAA or PaC which considers its connectivity lost after a
>>>    relatively small number of unresponsive pings coupled with a peer
>>>    that is aggressively rate-limiting the ping request and answer
>>>    messages, false-positives could result. [a14] Care should be taken when
>>>    rate-limiting ping request and answer messages to periodically
>>>    respond, and a PAA or PaC should not rely on ping request and answer
>>>    messages to quickly determine loss of connectivity.
>>>
>>> [a14]Not clear. May consider revising the senetence.
>>>
>>> [YO] How about this?  
>>>
>>> "
>>>    Therefore, a PAA or PaC should not rely on highly frequent ping
>>>    request and answer message exchanges to quickly determine loss of
>>>    connectivity.
>>>   
>>> "
>>>   
>>>       
>> Subir> The problem here is it is either request or answer. It can not be
>> both.
>> If answers arrive with frequent requests, then there is no loss of
>> connectivity.
>> Am I correct? Also you may delete "highly" here.
>>     
>
> I think it might be good to describe it without mentioning request and
> answer messages.  How about this?
>   
>
> "
>    Therefore, a PAA or PaC should not rely on frequent ping
>    operation to quickly determine loss of connectivity.
>   
Subir> Fine.
> "
>
>
>
>   
>>>    The PaC may receive a PANA-Auth-Request before receiving the answer
>>>    to its outstanding re-authentication request message.  This condition
>>>    can arise due to packet re-ordering or a race condition between the
>>>    PaC and PAA when they both attempt to engage in re-authentication.
>>>    The PaC MUST keep discarding the received PANA-Auth-Requests until it
>>>    receives the answer to its request.[a17]
>>>
>>> [a17]How will PAA know that PaC has not received it?  Will PaC
>>> retransmit PANA-Notification-Request?
>>>
>>> [YO] Yes.  The PAA will answer to the PNR.
>>>   
>>>       
>> Subir> The question is when PaC will retransmit instead of discarding? This
>> race condition may continue for a while.
>>     
>
> PNR will be retranmitted by PaC based on retransmission timer.  So
> most probably the first retransmitssion of PNR will break the race
> condition if it does not get lost.
>
>   
Subir> Ok.
>>> 5.2.  Sequence Number and Retransmission
>>>
>>>    PANA uses sequence numbers to provide ordered and reliable delivery
>>>    of messages.
>>>
>>>    The PaC and PAA maintain two sequence numbers: 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. [a18] These sequence numbers are 32-bit
>>>
>>> [a18]Not clear. May cosnider revising it. 
>>>
>>> [YO] How about this?
>>>
>>> "
>>>    The PaC and PAA maintain two sequence numbers: the one to be used
>>>    for the next outgoing request and the one it expects to see in the
>>>    next incoming request.
>>>   
>>> "
>>>   
>>>       
>> Subir> How about this:
>>
>> "The PaC and PAA maintain two sequence numbers: one is for outgoing
>> request and the other one is for incoming request."
>>     
>
> OK.
>
>
> _______________________________________________
> 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 Apr 26 18:06:49 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HhC6w-0005sF-LS; Thu, 26 Apr 2007 18:06:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HhC6v-0005sA-Lw
	for pana@ietf.org; Thu, 26 Apr 2007 18:06:45 -0400
Received: from mout.perfora.net ([74.208.4.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhC6u-0000D0-D3
	for pana@ietf.org; Thu, 26 Apr 2007 18:06:45 -0400
Received: from [88.233.210.42] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1HhC6o0PrY-000615; Thu, 26 Apr 2007 18:06:42 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
	"'Subir Das'" <subir@research.telcordia.com>
Subject: RE: [Pana] Comments on draft-pana-pana-15a
Date: Fri, 27 Apr 2007 01:06:32 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-reply-to: <20070426204201.GC8037@steelhead>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
thread-index: AceIQ2AcjzthAxMHR/GDNU9/LxyZiAAC08hw
Message-ID: <0MKoyl-1HhC6o0PrY-000615@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX19cRSoJCtATUqkKteKLRXC6/8GvEw69cZaQBeJ
	6Da1Lj3vImCzFfaeAEvz0tBG064fzImwQa3f/G90lax8rfwCRb
	m9aPBmtOIqADHyb4t0wmQ==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
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>
Errors-To: pana-bounces@ietf.org

> > > [YO] How about this?
> > >
> > > "
> > >    The PaC and PAA maintain two sequence numbers: the one to be used
> > >    for the next outgoing request and the one it expects to see in the
> > >    next incoming request.
> > >
> > > "
> > >
> > Subir> How about this:
> >
> > "The PaC and PAA maintain two sequence numbers: one is for outgoing
> > request and the other one is for incoming request."
> 
> OK.

During that editing we lost some of the semantics. I'd recommend regaining
it like this:


	The PaC and PAA maintain two sequence numbers: One is for setting
the 
	sequence number of the next outgoing request, the other is for 
	matching the sequence number of the next incoming request.

Alper



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



From Poyamarkowycz@2msolutions.com.au Sat Apr 28 09:14:22 2007
Return-path: <Poyamarkowycz@2msolutions.com.au>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hhmko-0008KH-BE
	for pana-archive@lists.ietf.org; Sat, 28 Apr 2007 09:14:22 -0400
Received: from alille-256-1-131-154.w86-192.abo.wanadoo.fr ([86.192.162.154] helo=ALille-256-1-23-146.w90-18.abo.wanadoo.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hhmkl-0005fE-Ba
	for pana-archive@lists.ietf.org; Sat, 28 Apr 2007 09:14:22 -0400
Received: from acer-bbf60584a3 ([102.149.19.3] helo=acer-bbf60584a3)
	by ALille-256-1-23-146.w90-18.abo.wanadoo.fr ( sendmail 8.13.3/8.13.1) with esmtpa id 1mhhtT-000CMD-qb
	for pana-archive@lists.ietf.org; Sat, 28 Apr 2007 15:14:34 +0100
Message-ID: <000d01c7899f$82f44380$9266125a@acerbbf60584a3>
From: "Poya markowycz" <Poyamarkowycz@2msolutions.com.au>
To: <pana-archive@lists.ietf.org>
Subject: Market huge report.
Date: Sat, 28 Apr 2007 15:14:19 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0008_01C789A7.E4B8AB80"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 4.8 (++++)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

------=_NextPart_000_0008_01C789A7.E4B8AB80
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hot news
http://www.imagehosting.com/out.php/i533257_GW5CCk.png
In February 1993, I called the Institute by telephone and had an interesting chat with its public relations officer, Mr.
------=_NextPart_000_0008_01C789A7.E4B8AB80
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3059" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT Arial size=3D2>Hot news</FONT></DIV>
<DIV><A=20
HREF=3D"http://www.imagehosting.com/out.php/i533257_GW5CCk.png">http://ww=
w.imagehosting.com/out.php/i533257_GW5CCk.png</A></DIV>
<DIV><FONT Arial size=3D2>In February 1993, I called the Institute by =
telephone=20
and had an interesting chat with its public relations officer,=20
Mr.</FONT></DIV></BODY></HTML>

------=_NextPart_000_0008_01C789A7.E4B8AB80--




From wqg@marvell.com Sat Apr 28 10:19:43 2007
Return-path: <wqg@marvell.com>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hhnm3-0007su-R5
	for pana-archive@lists.ietf.org; Sat, 28 Apr 2007 10:19:43 -0400
Received: from 214.134.broadband5.iol.cz ([88.100.134.214])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1Hhnm2-0007y5-9W
	for pana-archive@lists.ietf.org; Sat, 28 Apr 2007 10:19:43 -0400
Received: from [159.69.222.153] (helo=vgo)
	by 214.134.broadband5.iol.cz with smtp (Exim 4.62 (FreeBSD))
	id 1I=oEg-0006R1-C2; Sat, 28 Apr 2007 16:21:24 +0200
Message-ID: <001201c789a0$42a17a40$99de459f@vgo>
From: "Andrew" <wqg@marvell.com>
To: <pana-archive@lists.ietf.org>
Subject: The problem lies in the build-up portions of the movie.
Date: Sat, 28 Apr 2007 16:19:40 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="windows-1250";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 3.5 (+++)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

CDPN Acquires GPS And Wireless Transportation Development Company!

China Datacom Corp.
Sym: CDPN
Close: $0.065

CDPN, through its subsidiary "Supremacy Intl", acquired all outstanding
shares in General Link Information Systems. General manages, serves and
operates the only GPS vehicle monitoring and management system in China,
and provides a wide range of mobile applications for the transport
industry. This is HOT! It's already taking off, volume jumped through
the roof Friday! Read the release and get in on CDPN first thing Monday.

So, Microsoft has made great strides, just not enough to reach the goal.
Spector defense will rely on science  -  Celebrity News - MSNBC.
GoToMyPC - Free Software Downloads and Software Reviews - Download.
" The interactions of the characters were unrealistically violent: never
would such beatings occur in a geisha house because even the servant
girls were considered investments not to be harmed.
The cards not only stay true to original design with its look and feel,
but are also in the original size of the 1955 and 1956 cards.
If you like campy, silly, goofy, but with a message sci-fi, you're gonna
like Lexx, especially this first one. 1 if your browser does not
automatically redirect you.




From CIPIERE-Ohta@adrexo-fo.org Mon Apr 30 10:24:55 2007
Return-path: <CIPIERE-Ohta@adrexo-fo.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HiWoB-0000Bc-DU
	for pana-archive@lists.ietf.org; Mon, 30 Apr 2007 10:24:55 -0400
Received: from [212.1.236.93] (helo=[213.141.131.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HiWo9-0006TK-T5
	for pana-archive@lists.ietf.org; Mon, 30 Apr 2007 10:24:55 -0400
Received: by 10.147.84.193 with SMTP id ZNgTCMONEMFAm;
	Mon, 30 Apr 2007 18:25:07 +0400 (GMT)
Received: by 192.168.216.68 with SMTP id XVzFsJwRGuLUDg.1093444312123;
	Mon, 30 Apr 2007 18:25:05 +0400 (GMT)
Message-ID: <000a01c78b33$570d4970$5d838dd5@clnuser>
From: "CIPIERE Ohta" <CIPIERE-Ohta@adrexo-fo.org>
To: <pana-archive@lists.ietf.org>
Subject: I'd gotten good at it, looking at the stars at night and marveling at the size of the universe.
Date: Mon, 30 Apr 2007 18:25:02 +0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0005_01C78B54.DE1EE970"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da

------=_NextPart_000_0005_01C78B54.DE1EE970
Content-Type: text/plain;
	charset="windows-1251"
Content-Transfer-Encoding: quoted-printable

This will list the formats supported by the primary buffer, and let you choose one.

WATCH OJU.F TRADE LIKE CRAZY!
THIS FRANKFURT STOCK IS
GOING THROUGH THE ROOF!

COMPANY: ORAMED PHARMA
SYMBOL: OJU.F
PRICE: 0.60
TARGET: 2.15
WKN : A0J3FG
ISIN : US68403P1049

WE ARE PREDICTING AMAZING
GAINS ON THIS ONE!
BE PART OF IT! ADD IT TO
YOUR PORTFOLIO!
WATCH OJU.F!!!

It's like our visit to the moon or to that other star I guess you go for nothing if you really want to go that far.
------=_NextPart_000_0005_01C78B54.DE1EE970
Content-Type: text/html;
	charset="windows-1251"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-1251">
<META content=3D"MSHTML 6.00.2900.3059" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT Arial size=3D2>This will list the formats supported by the =
primary=20
buffer, and let you choose one.</FONT></DIV>
<DIV><FONT Arial size=3D2></FONT></DIV>
<DIV><FONT Arial size=3D2>WATCH OJU.F TRADE LIKE CRAZY!</FONT></DIV>
<DIV><FONT Arial size=3D2>THIS FRANKFURT STOCK IS</FONT></DIV>
<DIV><FONT Arial size=3D2>GOING THROUGH THE ROOF!</FONT></DIV>
<DIV><FONT Arial size=3D2></FONT></DIV>
<DIV><FONT Arial size=3D2>COMPANY: ORAMED PHARMA</FONT></DIV>
<DIV><FONT Arial size=3D2>SYMBOL: OJU.F</FONT></DIV>
<DIV><FONT Arial size=3D2>PRICE: 0.60</FONT></DIV>
<DIV><FONT Arial size=3D2>TARGET: 2.15</FONT></DIV>
<DIV><FONT Arial size=3D2>WKN : A0J3FG</FONT></DIV>
<DIV><FONT Arial size=3D2>ISIN : US68403P1049</FONT></DIV>
<DIV><FONT Arial size=3D2></FONT></DIV>
<DIV><FONT Arial size=3D2>WE ARE PREDICTING AMAZING</FONT></DIV>
<DIV><FONT Arial size=3D2>GAINS ON THIS ONE!</FONT></DIV>
<DIV><FONT Arial size=3D2>BE PART OF IT! ADD IT TO</FONT></DIV>
<DIV><FONT Arial size=3D2>YOUR PORTFOLIO!</FONT></DIV>
<DIV><FONT Arial size=3D2>WATCH OJU.F!!!</FONT></DIV>
<DIV><FONT Arial size=3D2></FONT></DIV>
<DIV><FONT Arial size=3D2>It's like our visit to the moon or to that =
other star I=20
guess you go for nothing if you really want to go that=20
far.</FONT></DIV></BODY></HTML>

------=_NextPart_000_0005_01C78B54.DE1EE970--




From pana-bounces@ietf.org Mon Apr 30 10:34:56 2007
Return-path: <pana-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HiWxs-0004V3-42; Mon, 30 Apr 2007 10:34:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HiWxr-0004Uy-3y
	for pana@ietf.org; Mon, 30 Apr 2007 10:34:55 -0400
Received: from thumper.research.telcordia.com ([128.96.41.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HiWxp-0000BP-Rr
	for pana@ietf.org; Mon, 30 Apr 2007 10:34:55 -0400
Received: from mailee.research.telcordia.com (mailee [192.4.16.29])
	by thumper.research.telcordia.com (8.13.6/8.13.5) with ESMTP id
	l3UEEjc1002235; Mon, 30 Apr 2007 10:16:45 -0400 (EDT)
Received: from [128.96.58.238] (vpntnlA238 [128.96.58.238])
	by mailee.research.telcordia.com (8.9.3/8.9.3) with ESMTP id KAA08493; 
	Mon, 30 Apr 2007 10:14:45 -0400 (EDT)
Message-ID: <4635F9CA.2020207@research.telcordia.com>
Date: Mon, 30 Apr 2007 10:14:34 -0400
From: Subir Das <subir@research.telcordia.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
Subject: Re: [Pana] Comments on draft-pana-pana-15a
References: <0MKoyl-1HhC6o0PrY-000615@mrelay.perfora.net>
In-Reply-To: <0MKoyl-1HhC6o0PrY-000615@mrelay.perfora.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
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>
Errors-To: pana-bounces@ietf.org



Alper Yegin wrote:
>>>> [YO] How about this?
>>>>
>>>> "
>>>>    The PaC and PAA maintain two sequence numbers: the one to be used
>>>>    for the next outgoing request and the one it expects to see in the
>>>>    next incoming request.
>>>>
>>>> "
>>>>
>>>>         
>>> Subir> How about this:
>>>
>>> "The PaC and PAA maintain two sequence numbers: one is for outgoing
>>> request and the other one is for incoming request."
>>>       
>> OK.
>>     
>
> During that editing we lost some of the semantics. I'd recommend regaining
> it like this:
>
>
> 	The PaC and PAA maintain two sequence numbers: One is for setting
> the 
> 	sequence number of the next outgoing request, the other is for 
> 	matching the sequence number of the next incoming request.
>   

  Subir>  The term 'next' is not clear to me. Does it mean that one can 
not use the sequence number for
              previous outgoing/incoming  request?
> 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



