From mailman-bounces@ietf.org  Fri Oct  1 07:04:45 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17768
	for <pana-archive@lists.ietf.org>; Fri, 1 Oct 2004 07:04:45 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CDJnU-0006rQ-4n
	for pana-archive@lists.ietf.org; Fri, 01 Oct 2004 05:33:52 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: pana-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.11672.1096622068.3166.mailman@lists.ietf.org>
Date: Fri, 01 Oct 2004 05:14:28 -0400
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

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

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

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

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

NOTE WELL:

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

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

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

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

Please consult RFC 3667 for details.

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


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

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

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


From pana-bounces@ietf.org  Tue Oct 12 22:02:12 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08722
	for <pana-archive@lists.ietf.org>; Tue, 12 Oct 2004 22:02:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHYOv-00054z-KQ; Tue, 12 Oct 2004 21:58:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHYMu-0004R1-1H
	for pana@megatron.ietf.org; Tue, 12 Oct 2004 21:55:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08071
	for <pana@ietf.org>; Tue, 12 Oct 2004 21:55:53 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHYXZ-0000hH-ON
	for pana@ietf.org; Tue, 12 Oct 2004 22:07:08 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i9D1tUbv009318;
	Wed, 13 Oct 2004 10:55:30 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i9D1tU1L027412;
	Wed, 13 Oct 2004 10:55:30 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	LAA27408 ; Wed, 13 Oct 2004 10:55:30 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id KAA19178; Wed, 13 Oct 2004 10:55:29 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i9D1tSFC005483;
	Wed, 13 Oct 2004 10:55:28 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i9D1tRXU007162;
	Wed, 13 Oct 2004 10:55:27 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I5I0065A2OCVY@tsbpo1.po.toshiba.co.jp>; Wed,
	13 Oct 2004 10:55:27 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1CHHwL-0005uO-00; Tue, 12 Oct 2004 01:23:25 -0700
Date: Tue, 12 Oct 2004 04:23:25 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20041012082325.GE1488@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Subject: [Pana] PANA state machine review
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Here is review of draft-ohba-pana-statemachine-00.txt by Julien Bournelle.
Thanks Julien for reviewing the draft!

Yoshihiro Ohba

--------------------------------------------------------------------------
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
Subject: Re: PANA state machine I-D: request for review
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
                                                                                
Hi yoshi,

 I have read the pana state machine draft and I didn't find any "fatal" error. I
must admit that it is not easy to review state machine :-)..however I
have some minor editorial comments..

* there are no references to PANA-Ping ?

* p. 11

"If the state machine already have a ..."

s/have/has

* p. 14   6.1.1 Delvering EAP Messages from PaC to EAP Peer

TxEAP() is only used to deliver EAP Request to EAP module ?

you do not deliver EAP-Success or Failure ?

* p. 15   6.1.4

How can PaC can set EAP_SUCCESS/EAP_FAILURE before receiving PBR/PFER ?



* p. 19

I don't understand why there are sometimes a RtxTimerStop() in the Exit
Action. Do we assume that a Timer is always triggered when we receive a
message ?

* p. 27  7.1.2

same comments as for p. 14, TxEAP() is lny used for EAP-Response ?

* p. 27 7.1.3

s/PaC/PAA

* p. 32
(PSA processing without mobility support)

s/exit_avp/exist_avp

(PSA processing with mobility support)

is is normal to have PBR.insert_avp("MAC") 2 times ?

* p. 35

s/FAIT_FAIL_PBA/WAIT_FAIL_PBA

* p.40

s/Resposne/Response


and that's all. 

Hope it helps,

---------
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
Subject: Re: PANA state machine I-D: request for review
To: Yoshihiro Ohba <yohba@tari.toshiba.com>

hi yoshi,

 one of my colleague (the guy who is working on pana implementation)
just mention me another error:

p.26

State: WAIT_PRAA

s/initiated by PAA/initiated by PaC

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


From pana-bounces@ietf.org  Tue Oct 12 22:34:39 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10859
	for <pana-archive@lists.ietf.org>; Tue, 12 Oct 2004 22:34:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CHYws-0006EO-Bu; Tue, 12 Oct 2004 22:33:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CHYu8-0005DG-N2
	for pana@megatron.ietf.org; Tue, 12 Oct 2004 22:30:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10511
	for <pana@ietf.org>; Tue, 12 Oct 2004 22:30:13 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CHZ4y-0001ND-Lx
	for pana@ietf.org; Tue, 12 Oct 2004 22:41:29 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i9D2UCbv008394;
	Wed, 13 Oct 2004 11:30:12 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i9D2UC1B021981;
	Wed, 13 Oct 2004 11:30:12 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	MAA21977 ; Wed, 13 Oct 2004 11:30:11 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id LAA24919; Wed, 13 Oct 2004 11:30:10 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id i9D2U9u3002529;
	Wed, 13 Oct 2004 11:30:09 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw.toshiba.co.jp  with ESMTP id i9D2U8XU006529;
	Wed, 13 Oct 2004 11:30:08 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I5I00CPF4A5VG@tsbpo1.po.toshiba.co.jp>; Wed,
	13 Oct 2004 11:30:07 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1CHIGQ-0005xR-00; Tue, 12 Oct 2004 01:44:10 -0700
Date: Tue, 12 Oct 2004 04:44:10 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] PANA state machine review
In-reply-to: <20041012082325.GE1488@steelhead>
To: pana@ietf.org
Message-id: <20041012084410.GG1488@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org, Julien.Bournelle@int-evry.fr
User-Agent: Mutt/1.5.5.1+cvs20040105i
References: <20041012082325.GE1488@steelhead>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Cc: Julien.Bournelle@int-evry.fr
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Julien and all,

Please see my comments in line.

On Tue, Oct 12, 2004 at 04:23:25AM -0400, Yoshihiro Ohba wrote:
> Here is review of draft-ohba-pana-statemachine-00.txt by Julien Bournelle.
> Thanks Julien for reviewing the draft!
> 
> Yoshihiro Ohba
> 
> --------------------------------------------------------------------------
> From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
> Subject: Re: PANA state machine I-D: request for review
> To: Yoshihiro Ohba <yohba@tari.toshiba.com>
>                                                                                 
> Hi yoshi,
> 
>  I have read the pana state machine draft and I didn't find any "fatal" error. I
> must admit that it is not easy to review state machine :-)..however I
> have some minor editorial comments..
> 
> * there are no references to PANA-Ping ?

Since draft-ohba-pana-statemachine-00.txt is written based on the pana-pana-04
and PANA-Ping was defined in pana-pana-05, there is no reference to PANA-Ping.
The next revision of the PANA state machine will have PANA-Ping handling.

> 
> * p. 11
> 
> "If the state machine already have a ..."
> 
> s/have/has

OK.

> 
> * p. 14   6.1.1 Delvering EAP Messages from PaC to EAP Peer
> 
> TxEAP() is only used to deliver EAP Request to EAP module ?
> 
> you do not deliver EAP-Success or Failure ?


You are right.  TxEAP() at PaC is also used for delivering EAP-Success
and EAP-Failure messages.  Thanks for pointing this out.

> 
> * p. 15   6.1.4
> 
> How can PaC can set EAP_SUCCESS/EAP_FAILURE before receiving PBR/PFER ?

The EAP_SUCCESS and EAP_FAILURE event variables refer to eapSuccess
and eapFail variables of the EAP peer state machine, respectively.
The EAP peer state machine defines several situations where eapSuccess
and eapFail variables are set even before receiving an EAP-Success or
an EAP-Failure message.  One example is that if an EAP method supports
method-specific result indications, the EAP peer can determine whether
the EAP method has completed with success or failure before receiving
an EAP-Success or an EAP-Failure (that is carried in PBR/PFER).

> 
> 
> 
> * p. 19
> 
> I don't understand why there are sometimes a RtxTimerStop() in the Exit
> Action. Do we assume that a Timer is always triggered when we receive a
> message ?

The RtxTimerStop() procecure is called in Exit Action when there is an
outstanding request in the current state.  On the other hand, the
RtxTimerStop() procecure is not called in a state that does not have
an outstanding request.

> 
> * p. 27  7.1.2
> 
> same comments as for p. 14, TxEAP() is lny used for EAP-Response ?

TxEAP() at PAA sidde only used for EAP-Response.

> 
> * p. 27 7.1.3
> 
> s/PaC/PAA

OK.

> 
> * p. 32
> (PSA processing without mobility support)
> 
> s/exit_avp/exist_avp

OK.

> 
> (PSA processing with mobility support)
> 
> is is normal to have PBR.insert_avp("MAC") 2 times ?

That is a dup.  I will remove one.

> 
> * p. 35
> 
> s/FAIT_FAIL_PBA/WAIT_FAIL_PBA

OK.

> 
> * p.40
> 
> s/Resposne/Response

OK.

> 
> 
> and that's all. 
> 
> Hope it helps,
> 
> ---------
> From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
> Subject: Re: PANA state machine I-D: request for review
> To: Yoshihiro Ohba <yohba@tari.toshiba.com>
> 
> hi yoshi,
> 
>  one of my colleague (the guy who is working on pana implementation)
> just mention me another error:
> 
> p.26
> 
> State: WAIT_PRAA
> 
> s/initiated by PAA/initiated by PaC

OK.

Best regards,

Yoshihiro Ohba


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


From pana-bounces@ietf.org  Wed Oct 20 05:39:50 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15162
	for <pana-archive@lists.ietf.org>; Wed, 20 Oct 2004 05:39:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKBYe-0004on-Ut; Wed, 20 Oct 2004 04:10:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKAB0-0004Rw-PG
	for pana@megatron.ietf.org; Wed, 20 Oct 2004 02:42:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04377
	for <pana@ietf.org>; Wed, 20 Oct 2004 02:42:19 -0400 (EDT)
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKANG-0000kO-GS
	for pana@ietf.org; Wed, 20 Oct 2004 02:55:07 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by thoth.sbs.de (8.12.6/8.12.6) with ESMTP id i9K6gIfO026727
	for <pana@ietf.org>; Wed, 20 Oct 2004 08:42:18 +0200
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id i9K6gHBO003663
	for <pana@ietf.org>; Wed, 20 Oct 2004 08:42:17 +0200
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <4BVRYNSG>; Wed, 20 Oct 2004 08:42:17 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F046868FA@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'pana@ietf.org'" <pana@ietf.org>
Date: Wed, 20 Oct 2004 08:42:14 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Subject: [Pana] FW: I-D ACTION:draft-thomson-nacp-00.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

hi all, 

this draft might be of interest for the pana working group. 

ciao
hannes
 

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] 
Sent: Tuesday, October 19, 2004 1:48 PM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-thomson-nacp-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Network Access Control Protocol (NACP)
	Author(s)	: S. Thomson, et al.
	Filename	: draft-thomson-nacp-00.txt
	Pages		: 17
	Date		: 2004-10-18
	
The Network Access Control Protocol (NACP) is a protocol used to 
   encapsulate EAP (Extensible Authentication Protocol) messages in a 
   UDP (User Datagram Protocol) transport between an authenticator and 
   peer.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-thomson-nacp-00.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of the
message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in, type
"cd internet-drafts" and then
	"get draft-thomson-nacp-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-thomson-nacp-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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


From pana-bounces@ietf.org  Thu Oct 21 08:10:04 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12515
	for <pana-archive@lists.ietf.org>; Thu, 21 Oct 2004 08:10:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKasx-0007hE-SQ; Thu, 21 Oct 2004 07:13:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKMxr-0008KU-R8
	for pana@megatron.ietf.org; Wed, 20 Oct 2004 16:21:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21920
	for <pana@ietf.org>; Wed, 20 Oct 2004 16:21:35 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKNAE-0004SH-2O
	for pana@ietf.org; Wed, 20 Oct 2004 16:34:31 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I5W00F01GJ3WY@mailout3.samsung.com> for pana@ietf.org; Thu,
	21 Oct 2004 05:21:03 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I5W00JPQGJ2RH@mailout3.samsung.com> for pana@ietf.org;
	Thu, 21 Oct 2004 05:21:03 +0900 (KST)
Received: from Alperyegin ([105.253.155.49])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0I5W00DR3GJ0UF@mmp1.samsung.com> for pana@ietf.org; Thu,
	21 Oct 2004 05:21:02 +0900 (KST)
Date: Wed, 20 Oct 2004 13:21:00 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <010e01c4b6e2$52571780$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7BIT
Subject: [Pana] PANA WG last call: draft-ietf-pana-framework-02
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


This message announces the PANA WG last call on PANA Framework document
(draft-ietf-pana-framework-02). The last call will conclude on Nov 3rd,
2004.

Please read and review the document, and register your feedback on the
PANA mailing list (even if it is a simple "I read the document and it is
ready to proceed.").

http://www.ietf.org/internet-drafts/draft-ietf-pana-framework-02.txt

- PANA WG chairs




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


From pana-bounces@ietf.org  Thu Oct 21 08:24:40 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14395
	for <pana-archive@lists.ietf.org>; Thu, 21 Oct 2004 08:24:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKazs-0004RY-CI; Thu, 21 Oct 2004 07:20:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKQDy-0003Se-N8
	for pana@megatron.ietf.org; Wed, 20 Oct 2004 19:50:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19828
	for <pana@ietf.org>; Wed, 20 Oct 2004 19:50:26 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKQQO-0003Wq-31
	for pana@ietf.org; Wed, 20 Oct 2004 20:03:25 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I5W004OCQ78YK@mailout2.samsung.com> for pana@ietf.org; Thu,
	21 Oct 2004 08:49:56 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I5W00JWAQ5NL9@mailout2.samsung.com> for pana@ietf.org;
	Thu, 21 Oct 2004 08:48:59 +0900 (KST)
Received: from Alperyegin ([105.253.155.49])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0I5W00CYSQ5KCA@mmp1.samsung.com> for pana@ietf.org; Thu,
	21 Oct 2004 08:48:59 +0900 (KST)
Date: Wed, 20 Oct 2004 16:48:55 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <021201c4b6ff$5e0f6740$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7BIT
Subject: [Pana] PANA WG last call: draft-ietf-pana-framework-02
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


This message announces the PANA WG last call on PANA Framework document
(draft-ietf-pana-framework-02). The last call will conclude on Nov 3rd,
2004.

Please read and review the document, and register your feedback on the
PANA mailing list (even if it is a simple "I read the document and it is
ready to proceed.").

http://www.ietf.org/internet-drafts/draft-ietf-pana-framework-02.txt

- PANA WG chairs




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


From pana-bounces@ietf.org  Thu Oct 21 08:25:02 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14445
	for <pana-archive@lists.ietf.org>; Thu, 21 Oct 2004 08:25:01 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKazu-0004Wm-05; Thu, 21 Oct 2004 07:20:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKQEh-0003Xr-Ej
	for pana@megatron.ietf.org; Wed, 20 Oct 2004 19:51:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19908
	for <pana@ietf.org>; Wed, 20 Oct 2004 19:51:10 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKQR6-0003Zg-DR
	for pana@ietf.org; Wed, 20 Oct 2004 20:04:09 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	id <0I5W00I44Q8GF9@mailout1.samsung.com> for pana@ietf.org; Thu,
	21 Oct 2004 08:50:40 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0I5W00HAPQ632P@mailout1.samsung.com> for pana@ietf.org;
	Thu, 21 Oct 2004 08:49:15 +0900 (KST)
Received: from Alperyegin ([105.253.155.49])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0I5W008JJQ60TT@mmp1.samsung.com> for pana@ietf.org; Thu,
	21 Oct 2004 08:49:15 +0900 (KST)
Date: Wed, 20 Oct 2004 16:49:11 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <021301c4b6ff$67d05a00$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7BIT
Subject: [Pana] PANA WG last call: draft-ietf-pana-ipsec-04.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


This message announces the PANA WG last call on "PANA Enabling
IPsec-based Access Control" document (draft-ietf-pana-ipsec-04.txt). The
last call will conclude on Nov 3rd, 2004.

Please read and review the document, and register your feedback on the
PANA mailing list (even if it is a simple "I read the document and it is
ready to proceed.").

http://www.ietf.org/internet-drafts/draft-ietf-pana-ipsec-04.txt

Previously discussed and closed issues on this document can be found at:
http://danforsberg.info:8080/pana-issues/

- PANA WG Chairs



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


From pana-bounces@ietf.org  Thu Oct 21 13:55:25 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29115
	for <pana-archive@lists.ietf.org>; Thu, 21 Oct 2004 13:55:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKgzn-0005ix-W4; Thu, 21 Oct 2004 13:45:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CKgkK-0004we-0w
	for pana@megatron.ietf.org; Thu, 21 Oct 2004 13:29:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25921
	for <pana@ietf.org>; Thu, 21 Oct 2004 13:29:00 -0400 (EDT)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKgwu-0000YU-G0
	for pana@ietf.org; Thu, 21 Oct 2004 13:42:09 -0400
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	id <0I5Y00F01306SL@mailout1.samsung.com> for pana@ietf.org; Fri,
	22 Oct 2004 02:24:06 +0900 (KST)
Received: from ep_mmp1 (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0I5Y007V9305J7@mailout1.samsung.com> for pana@ietf.org;
	Fri, 22 Oct 2004 02:24:06 +0900 (KST)
Received: from Alperyegin ([105.253.155.49])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0I5Y00H4L30384@mmp1.samsung.com> for pana@ietf.org; Fri,
	22 Oct 2004 02:24:05 +0900 (KST)
Date: Thu, 21 Oct 2004 10:23:56 -0700
From: Alper Yegin <alper.yegin@samsung.com>
In-reply-to: <021301c4b6ff$67d05a00$6401a8c0@sisa.samsung.com>
To: pana@ietf.org
Message-id: <03d001c4b792$c03fa040$6401a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7BIT
Subject: [Pana] PANA WG last call: draft-ietf-pana-pana-06.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

This message announces the PANA WG last call on "Protocol for Carrying
Authentication for Network Access (PANA)" document
(draft-ietf-pana-pana-06.txt). The last call will conclude on Nov 4th,
2004.

Please read and review the document, and register your feedback on the
PANA mailing list (even if it is a simple "I read the document and it is
ready to proceed.").

Version 06 of the document is submitted to IETF and it is in the process
of publication. Until it is posted on the IETF repository, you can
access this latest revision at the following URL. Make sure to review
**-06**.

http://www.toshiba.com/tari/pana/draft-ietf-pana-pana-06.txt

 
Previously discussed and closed issues on this document can be found at:

http://danforsberg.info:8080/pana-issues/


- PANA WG Chairs



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


From pana-bounces@ietf.org  Thu Oct 21 20:16:35 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09582
	for <pana-archive@lists.ietf.org>; Thu, 21 Oct 2004 20:16:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKl6c-0005GR-6Q; Thu, 21 Oct 2004 18:08:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CKj6w-0002bF-Lu; Thu, 21 Oct 2004 16:00:34 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14093;
	Thu, 21 Oct 2004 16:00:32 -0400 (EDT)
Message-Id: <200410212000.QAA14093@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 21 Oct 2004 16:00:32 -0400
Cc: pana@ietf.org
Subject: [Pana] I-D ACTION:draft-ietf-pana-pana-06.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

--NextPart

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

	Title		: Protocol for Carrying Authentication for Network 
			  Access (PANA)
	Author(s)	: D. Forsberg, et al.
	Filename	: draft-ietf-pana-pana-06.txt
	Pages		: 75
	Date		: 2004-10-21
	
Extensible Authentication Protocol (EAP) defines a number of
   authentication schemes.  Network access authentication requires a
   host to authenticate itself before being authorized for sending and
   receiving packets.  The Protocol for Carrying Authentication for
   Network Access (PANA) is defined in this document.  PANA is a
   link-layer agnostic carrier for EAP.  PANA specifies the
   client-to-network access authentication within the scope of an
   overall secure network access framework.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pana-pana-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pana-pana-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-10-21154742.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2004-10-21154742.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From pana-bounces@ietf.org  Fri Oct 22 17:49:24 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25600
	for <pana-archive@lists.ietf.org>; Fri, 22 Oct 2004 17:49:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL6gR-0007E2-E3; Fri, 22 Oct 2004 17:10:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CL5m6-0001DI-Jx; Fri, 22 Oct 2004 16:12:34 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06504;
	Fri, 22 Oct 2004 16:12:30 -0400 (EDT)
Message-Id: <200410222012.QAA06504@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 22 Oct 2004 16:12:30 -0400
Cc: pana@ietf.org
Subject: [Pana] I-D ACTION:draft-ietf-pana-snmp-02.txt
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

--NextPart

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

	Title		: SNMP usage for PAA-2-EP interface
	Author(s)	: Y. Mghazli, et al.
	Filename	: draft-ietf-pana-snmp-02.txt
	Pages		: 37
	Date		: 2004-10-22
	
The PANA Authentication Agent (PAA) does not necessarily act as an
   Enforcement Point (EP) to prevent unauthorized access or usage of the
   network. When a PANA Client (PaC) successfully authenticates itself
   to the PAA, EP(s) (e.g., access routers) will need to be suitably
   notified. The PANA working group mandates the use of Simple Network
   Management Protocol (SNMP) to deliver the authorization information
   to one or more EPs when the PAA is separated from EPs.

   The present document provides the necessary information and
   extensions needed to use SNMP as the PAA-2-EP protocol.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-pana-snmp-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pana-snmp-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2004-10-22162040.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pana-snmp-02.txt

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

Content-Type: text/plain
Content-ID: <2004-10-22162040.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From pana-bounces@ietf.org  Tue Oct 26 09:15:20 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04065
	for <pana-archive@lists.ietf.org>; Tue, 26 Oct 2004 09:15:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMR91-0001h8-IK; Tue, 26 Oct 2004 09:13:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMR6H-00011v-Pz
	for pana@megatron.ietf.org; Tue, 26 Oct 2004 09:11:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03616
	for <pana@ietf.org>; Tue, 26 Oct 2004 09:10:55 -0400 (EDT)
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMRJw-0002pa-Gy
	for pana@ietf.org; Tue, 26 Oct 2004 09:25:05 -0400
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by smtp2.int-evry.fr (Postfix) with ESMTP id 539FF2FD65;
	Tue, 26 Oct 2004 15:11:12 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1CMR4E-0002fG-62;
	Tue, 26 Oct 2004 15:08:50 +0200
Date: Tue, 26 Oct 2004 15:08:50 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: pana@ietf.org
Message-ID: <20041026130850.GB10232@ipv6-5.int-evry.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (score=-5.802, requis 4.5, autolearn=spam,
	ALL_TRUSTED -3.30, AWL 0.10, BAYES_00 -2.60)
X-MailScanner-From: jb@ipv6-5.int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: Gerardo Giaretta <gerardo.giaretta@tilab.com>,
        Maryline MAKNAVICIUS-LAURENT <maryline.maknavicius@int-evry.fr>,
        yacine <yacine.el_mghazli@alcatel.fr>,
        Hannes Tschofening <hannes.tschofenig@siemens.com>
Subject: [Pana] Use of CTP for PANA
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi all,

 we've recently submitted a new version of our I-D concerning use of CTP
for PANA. In this revision, we detail the interaction with the AAA
infrastructure and we give 3 approaches to perform the transfer. 

This I-D is available at:
http://www.ietf.org/internet-drafts/draft-bournelle-pana-ctp-01.txt

Comments would be appreciated.

-- 
julien.bournelle@int-evry.fr

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


From pana-bounces@ietf.org  Tue Oct 26 20:59:12 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16783
	for <pana-archive@lists.ietf.org>; Tue, 26 Oct 2004 20:59:12 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMc7i-0005NV-7E; Tue, 26 Oct 2004 20:57:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMc4k-00049p-32
	for pana@megatron.ietf.org; Tue, 26 Oct 2004 20:54:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16503
	for <pana@ietf.org>; Tue, 26 Oct 2004 20:54:04 -0400 (EDT)
Received: from smtp805.mail.sc5.yahoo.com ([66.163.168.184])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CMcIV-0008Hc-23
	for pana@ietf.org; Tue, 26 Oct 2004 21:08:19 -0400
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.17.134
	with login)
	by smtp805.mail.sc5.yahoo.com with SMTP; 27 Oct 2004 00:54:03 -0000
Message-ID: <006a01c4a42c$7d0b5ef0$861167c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Alper Yegin" <alper.yegin@samsung.com>, <pana@ietf.org>
References: <03d001c4b792$c03fa040$6401a8c0@sisa.samsung.com>
Subject: Re: [Pana] PANA WG last call: draft-ietf-pana-pana-06.txt
Date: Sun, 26 Sep 2004 17:54:00 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: 7bit
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit

The document seems to be in a good shape and here are a few comments that i had.

1) In section 2.0,
      PANA Session:

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

     Can we explain the reason why the session cannot be shared across multiple network interfaces ?
      I could not find any other place in the document where this is explained (perhaps missed it).

2) In section 4.1,

      In any case, PANA MUST NOT generate an EAP message on behalf of EAP
      peer or EAP (pass-through) authenticator.

   This looked like a general statement and not specific section to 4.1. It might have been
   good to have a general section on how EAP maps to PANA or at least how PANA uses
   EAP.

3) In section 4.1,

      A Nonce AVP MUST be included in PANA-Start-Request and
      PANA-Start-Answer messages.  The nonces are used to establish a PANA
      SA.

    This is the first place Nonce is used but not defined/explained at to why nonce
     is needed ? I understand that it adds freshness to the key material used for PANA
     SA. But isn't that already taken care when AAA-key is derived.
     It might be good to point out the security property of using the
     Nonce in the PANA_MAC_KEY.

4) Section 4.3 Authorization phase :
        I am confused by the usage of word "Authorization". In the "Authentication phase",
        the PaC is in the process of getting authenticated. Similarly does it mean that the PaC
        is in the process of getting authorized ? So, if i send a PANA_SUCCESS at the end
        of authentication phase, by definition the node is both authenticated and authorized. So,
        i don't know what authorization phase means.

5) section 4.3 : It is not explained as to how the replay attack is prevented. The attacker can
    collect the ping answers and can bombard them. But the use of sequence numbers prevent
    the replay attack. Also, if there was a recent request/response exchange, that implies that
    the other side is alive because of the sequence number being acked. This can be used 
    as an optimization to not send the ping request.

6) In section 5.3, 

    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 PANA-PAA-Discover, and
    the very first request messages.

   Expand "the very first request messages". 

7) In section 7.3,

     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.

I don't know why the privately managed AVP address space cannot overlap with
some other vendor specific AVPs ? Section 10.4.1 does not say anything.

8)  In section 11.1, you can note that the sequence number also can be used as liveness
     check.

Editorial
--------
1) In section 4.1,
    A PANA-Start-Request message MAY carry a Cookie AVP that contains a
   cookie.  The sequence number is set to a randomly picked initial
   sequence number.  The cookie is used for preventing the PAA from
   resource consumption DoS attacks by blind attackers.  

    s/blind attackers/attackers.

2) Section 11.8,

       11.8  Livenes Test

    s/Livenes Test/ Liveness Test

-mohan






----- Original Message ----- 
From: "Alper Yegin" <alper.yegin@samsung.com>
To: <pana@ietf.org>
Sent: Thursday, October 21, 2004 10:23 AM
Subject: [Pana] PANA WG last call: draft-ietf-pana-pana-06.txt


> This message announces the PANA WG last call on "Protocol for Carrying
> Authentication for Network Access (PANA)" document
> (draft-ietf-pana-pana-06.txt). The last call will conclude on Nov 4th,
> 2004.
> 
> Please read and review the document, and register your feedback on the
> PANA mailing list (even if it is a simple "I read the document and it is
> ready to proceed.").
> 
> Version 06 of the document is submitted to IETF and it is in the process
> of publication. Until it is posted on the IETF repository, you can
> access this latest revision at the following URL. Make sure to review
> **-06**.
> 
> http://www.toshiba.com/tari/pana/draft-ietf-pana-pana-06.txt
> 
>  
> Previously discussed and closed issues on this document can be found at:
> 
> http://danforsberg.info:8080/pana-issues/
> 
> 
> - PANA WG Chairs
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

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


From pana-bounces@ietf.org  Wed Oct 27 03:20:26 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12078
	for <pana-archive@lists.ietf.org>; Wed, 27 Oct 2004 03:20:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMi5Z-0004em-H8; Wed, 27 Oct 2004 03:19:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CMi4F-0004SH-TW
	for pana@megatron.ietf.org; Wed, 27 Oct 2004 03:18:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11963
	for <pana@ietf.org>; Wed, 27 Oct 2004 03:17:57 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CMiI4-0007Cl-5p
	for pana@ietf.org; Wed, 27 Oct 2004 03:32:16 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 27 Oct 2004 09:17:45 +0200
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] PANA WG last call: draft-ietf-pana-framework-02
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Wed, 27 Oct 2004 09:17:44 +0200
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB02601813D5A@FTRDMEL2.rd.francetelecom.fr>
Thread-Topic: [Pana] PANA WG last call: draft-ietf-pana-framework-02
Thread-Index: AcS3ZuBAByGY+cfSRZmEoCfVK0uAawEjREWA
From: "MORAND Lionel RD-CORE-ISS" <lionel.morand@francetelecom.com>
To: "Alper Yegin" <alper.yegin@samsung.com>, <pana@ietf.org>
X-OriginalArrivalTime: 27 Oct 2004 07:17:45.0857 (UTC)
	FILETIME=[0E8AB710:01C4BBF5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: quoted-printable
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Alper, all

The current document is pretty good from my point of view. The PANA =
applicability in WLAN/Lan and DSL environment is clearly described. =
However, I would have a comment/proposal on the DSL part.

I think that we could develop/clarify the DSL part in the PANA framework =
in order to highlight the possible added-value of the use of PANA in =
such environment.

Actually, the whole description is based on a traditional DSL network =
configuartion i.e. a DSL link between the CPE and the DSLAM, an =
ATM-based or Ethernet-based link between the DSLAM and the BRAS. In such =
a configuration, the DSLAM can be considered as an L2 =
collector/concentrator and we can consider that there is no need to =
highlight it in the descriptive figures.

However, existing scenarios/deployments propose to connect the DSLAM =
directly to an "standard" IP router (i.e. no BRAS after the DSLAM). =
VLANs are used between the DSLAM and the router, the DSLAM acts as a =
DHCP relay while the DHCP client is located in the host/residential =
gateway (RG). In this configuration, it is complex to rely on an AAA =
architecture to authenticate/authorize the network access to the user. =
Typically, there is no authentication phase and =
authentication/authorization is uselly based on the static binding of =
the host/RG's MAC address and the port-ID allocated by the DSLAM =
(inserted in the DHCP request by the DSLAM). Security is then mainly =
(only) based on anti-spoofing mechanisms.

It is sure that it could be useful to have a PANA agent in the DSLAM in =
order to use a backend AAA architecture and set-up security associations =
if needed.

In order to highlight this scenario in the framework document, I propose =
to:
* keep the current network configuration using the BRAS as a NAS but to =
add the DSLAM in the descriptive text as well as in the figures (even if =
the DSLAM is transparent)
* add the above scenario in which the DSLAM is connected via VLANs to an =
IP router

The first case could be seen as a smooth evolution of existing network =
configurations (moving from PPP to DHCP).
In the second case, PANA appears to be intrinsicaly part of the =
solution.

Best regards,

Lionel

> -----Message d'origine-----
> De : pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] De=20
> la part de Alper Yegin
> Envoy=E9 : mercredi 20 octobre 2004 22:21
> =C0 : pana@ietf.org
> Objet : [Pana] PANA WG last call: draft-ietf-pana-framework-02
>=20
>=20
>=20
> This message announces the PANA WG last call on PANA=20
> Framework document (draft-ietf-pana-framework-02). The last=20
> call will conclude on Nov 3rd, 2004.
>=20
> Please read and review the document, and register your=20
> feedback on the PANA mailing list (even if it is a simple "I=20
> read the document and it is ready to proceed.").
>=20
http://www.ietf.org/internet-drafts/draft-ietf-pana-framework-02.txt

- PANA WG chairs




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

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


From pana-bounces@ietf.org  Wed Oct 27 11:16:54 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13692
	for <pana-archive@lists.ietf.org>; Wed, 27 Oct 2004 11:16:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMpWF-0002fP-GX; Wed, 27 Oct 2004 11:15:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CMpLz-0005um-0d; Wed, 27 Oct 2004 11:04:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12018;
	Wed, 27 Oct 2004 11:04:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CMpZs-0007ON-4p; Wed, 27 Oct 2004 11:19:08 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CMpGn-00048n-PU; Wed, 27 Oct 2004 10:59:25 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CMpGn-00048n-PU@megatron.ietf.org>
Date: Wed, 27 Oct 2004 10:59:25 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: pana chair <alper.yegin@samsung.com>, pana mailing list <pana@ietf.org>,
        Internet Architecture Board <iab@iab.org>,
        pana chair <basavaraj.patil@nokia.com>,
        RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Pana] Document Action: 'Protocol for Carrying Authentication for 
 Network Access (PANA)Requirements' to Informational RFC 
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

The IESG has approved the following document:

- 'Protocol for Carrying Authentication for Network Access (PANA)
   Requirements '
   <draft-ietf-pana-requirements-09.txt> as an Informational RFC

This document is the product of the Protocol for carrying Authentication for 
Network Access Working Group. 

The IESG contact persons are Thomas Narten and Margaret Wasserman.

Technical Summary
 
This document provides the problem statement/requirements for PANA. It also 
includes some usage scenarios

Working Group Summary
 
There is concensus on this document in the WG
 
Protocol Quality
 
This document has been reviewed for the IESG by Thomas Narten.


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


From pana-bounces@ietf.org  Thu Oct 28 18:59:48 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05073
	for <pana-archive@lists.ietf.org>; Thu, 28 Oct 2004 18:59:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNGQr-00079F-SS; Thu, 28 Oct 2004 15:59:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNDfP-0007yh-6C
	for pana@megatron.ietf.org; Thu, 28 Oct 2004 13:02:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20048
	for <pana@ietf.org>; Thu, 28 Oct 2004 13:02:24 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNDtJ-00043W-Vx
	for pana@ietf.org; Thu, 28 Oct 2004 13:17:01 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I6B00H6W07WGZ@dns2.cselt.it> for pana@ietf.org; Thu,
	28 Oct 2004 18:52:44 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 28 Oct 2004 18:58:37 +0200
Date: Thu, 28 Oct 2004 19:00:43 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>,
        Alper Yegin <alper.yegin@samsung.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C573B64D6@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: Review of draft-ietf-pana-pana-06
thread-index: AcS9D8i1JfvwCMxWQ6mxfmdd8zxQcA==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 28 Oct 2004 16:58:37.0578 (UTC)
	FILETIME=[5E330EA0:01C4BD0F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Content-Transfer-Encoding: quoted-printable
Cc: pana@ietf.org
Subject: [Pana] Review of draft-ietf-pana-pana-06
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Alper and Yoshi,

I have some comments about PANA protocol draft.

Two general comments:=20

1. the draft specifies that there must be one hop between PaC and PAA.
This is not mentioned in section 3 (Introduction) and only in section
4.1 this is mentioned and partially motivated for the first time. I'd
suggest to write this requirement also in section 3. Moreover I have not
found in any PANA document a complete explanation of the reasons of this
choice (nor in draft-ietf-pana-requirements-09 where this requirement is
introduced). I think these reasons should be better explained in a PANA
WG document (which one? PANA framework?): in particular, this is
important since draft-tschofenig-mip6-bootstrapping-pana-00 proposes to
relax this assumption (even though in a complete different scenario).

2. I think the draft lacks of enough considerations about lifetimes of
PANA session, of PANA SA and of the keys defined in the draft (i.e.
PANA_MAC_KEY, AAA-key-int, AAA-key-new). For example, it's not clear to
me which are the relationships between the AAA-key lifetime and the PANA
session lifetime and the PANA SA lifetime. In the draft it is stated
that "The lifetime of the PANA SA is the same as the lifetime of the
PANA session for simplicity" (section 5.6) and "The PANA SA lifetime is
bounded by the AAA-Key lifetime.  Another execution of EAP method yields
in a new AAA-Key, and updates the PANA SA, PANA_MAC_KEY and key ID"
(sec. considerations section). Does it mean that (PANA session
lifetime)=3D(PANA SA lifetime)=3D(AAA-key lifetime)?=20
Moreover, which are the lifetimes of PANA_MAC_KEY, AAA-key-int and
AAA-key-new? Is it equal to the AAA-key lifetime? I think something
about this should be mentioned.


Some other (more detailed) comments:

- there are some terms used in the draft that are not defined in the
terminology section (Pre PANA Address, Post PANA Address, IPsec Tunnel
Inner Address, etc.). Since most of them are defined in PANA framework
terminology section, maybe it could be useful to have a reference to it
in the terminology section of PANA draft.

- section 3, bullet 2: the term ISP is not introduced, nor the
difference between NAP and ISP authentication. Maybe a possibility could
be to introduce ISP in the terminology section or include here a refence
to PANA framework.

- section 3, figure 1: I'd suggest to specify that this is an example in
case of a 1 RTT EAP method.

- section 4.1, first paragraph: it would seem that the only reason to
have PaC and PAA one hop away is the discovery process. I would suggest
to add a paragraph in introduction in order to state the motivations of
this choice or as, I stated before, introduce some text in PANA
framework and reference to it.

- section 4.1, figure 3: the figure shows that a L2 trigger at the EP
could trigger PANA protocol. This is certainly true, but there is not
any reference to this in the text. I'd suggest to add some text at the
end of paragraph 3, page 10.

- section 4.2, paragraph 2: "When an EAP Success/Failure message is sent
from a PAA, the message is carried in a PANA-Bind-Request (PBR)
message". This is not completly true because in case of separate NAP/ISP
authentication EAP Success/Failure message can be carried also in a
PFER. I'd suggest to add this comment in text. This is useful also
because, in paragraph 3, PFER and PFEA are mentioned together with PBR
and PBA.

- section 5.1 Provider-ID-AVP and Provider-Name-AVP are lacking. Is it
your choice?=20

- section 5.1, bullet 8: this bullet partially repeats what is specified
in bullet 3. Remove bullet 3?

- section 5.6: which is the reason to repeat the Key-Id AVP also in PBA?


- section 5.10, paragraph 2: "PAA should initiate EAP authentication
before the current session lifetime expires". Maybe
s/authentication/reauthentication?

- I don't understand the reason of section 6.1. It does not specify any
protocol details and it repeats a lot of details previously described.
Moreover it sounds like a "second" security consideration sectio.n

- section 6.2: CTP requires the usage of CTAR in order to trigger and
authorize the transfer. This means that the MN (PaC) has an active role
and CTP operations cannot be performed only by PAAs as suggested in this
section. This issue is tackled deeply in draft-bournelle-pana-ctp-01.
Maybe it is a CTP issue and not a PANA one but I think this should be
mentioned in the draft when the reference to CTP is made.=20
Another issue about the mobility handling is the need to communicate to
the AAA infrastructure the new NAS (PAA) to which the PaC is attached.
Again, maybe this is not directly a PANA issue but i think it should be
mentioned.

- section 8.2.1: there is still a reference to two sequence numbers.

- section 8.2.4: if EAP messages are not piggybacked, PARs can be sent
also by PaC. Same for section 8.2.5 and PAAs.  =20


Editorial nits:

- caption of figure 2: double space between Phase and when

- caption of figure 8: I'd suggest to add "triggered by PaC"

- section 5.5, bullet 3: double "in MAC or or IP header": s/or or/or
                                       =20
- section 8.2.9: s/PANA-Result-Request/PANA-Bind-Request

- section 8.3.18: "The IP-Address (AVP Code 18) contains an IP address
of n a PaC or PAA": s/of n a PaC/of a PaC
=20

- section 10.1: ")" is lacking


Regards,

--Gerardo


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

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

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


From pana-bounces@ietf.org  Thu Oct 28 19:00:04 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05125
	for <pana-archive@lists.ietf.org>; Thu, 28 Oct 2004 19:00:04 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNGRT-0008MD-0z; Thu, 28 Oct 2004 16:00:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNDkX-0001XN-AB
	for pana@megatron.ietf.org; Thu, 28 Oct 2004 13:07:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21306
	for <pana@ietf.org>; Thu, 28 Oct 2004 13:07:42 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNDyc-0004Xs-Q3
	for pana@ietf.org; Thu, 28 Oct 2004 13:22:20 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0I6B00I0N0H74Y@dns2.cselt.it> for pana@ietf.org; Thu,
	28 Oct 2004 18:58:19 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 28 Oct 2004 19:04:12 +0200
Date: Thu, 28 Oct 2004 19:06:18 +0200
From: Giaretta Gerardo <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Pana] PANA WG last call: draft-ietf-pana-pana-06.txt
To: Mohan Parthasarathy <mohanp@sbcglobal.net>,
        Alper Yegin <alper.yegin@samsung.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C573B64D7@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Pana] PANA WG last call: draft-ietf-pana-pana-06.txt
thread-index: AcS7wJpu6EyGfOSoR6WSWC4YtxdsDABT3lKg
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 28 Oct 2004 17:04:12.0703 (UTC)
	FILETIME=[25F312F0:01C4BD10]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: quoted-printable
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Mohan, Alper, all,

>=20
> 4) Section 4.3 Authorization phase :
>         I am confused by the usage of word "Authorization".=20
> In the "Authentication phase",
>         the PaC is in the process of getting authenticated.=20
> Similarly does it mean that the PaC
>         is in the process of getting authorized ? So, if i=20
> send a PANA_SUCCESS at the end
>         of authentication phase, by definition the node is=20
> both authenticated and authorized. So,
>         i don't know what authorization phase means.
>


I'm confused about the word "Authorization", too. If the PaC is in this
phase, it has been already authorized. Or am I missing something?

--Gerardo


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

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

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


From pana-bounces@ietf.org  Thu Oct 28 20:04:11 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21157
	for <pana-archive@lists.ietf.org>; Thu, 28 Oct 2004 20:04:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNJ1X-0008D5-4P; Thu, 28 Oct 2004 18:45:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNG0x-0001WE-J9
	for pana@megatron.ietf.org; Thu, 28 Oct 2004 15:32:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23416
	for <pana@ietf.org>; Thu, 28 Oct 2004 15:32:50 -0400 (EDT)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNGF5-0006MZ-F1
	for pana@ietf.org; Thu, 28 Oct 2004 15:47:28 -0400
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I6B00E017LQVO@mailout3.samsung.com> for pana@ietf.org; Fri,
	29 Oct 2004 04:32:14 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I6B004DY7LP2C@mailout3.samsung.com> for pana@ietf.org;
	Fri, 29 Oct 2004 04:32:13 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0I6B008YT7LMOZ@mmp1.samsung.com> for pana@ietf.org; Fri,
	29 Oct 2004 04:32:13 +0900 (KST)
Date: Thu, 28 Oct 2004 12:32:09 -0700
From: Alper Yegin <alper.yegin@samsung.com>
To: pana@ietf.org
Message-id: <001401c4bd24$d2d938a0$291d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Content-Transfer-Encoding: 7BIT
Subject: [Pana] PANA meeting agenda
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


If you'd like to get on the PANA meeting agenda, please send a note to
the chairs ASAP.

- Chairs



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


From pana-bounces@ietf.org  Fri Oct 29 16:49:44 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10310
	for <pana-archive@lists.ietf.org>; Fri, 29 Oct 2004 16:49:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNcmA-0005f4-Up; Fri, 29 Oct 2004 15:51:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNciA-00026Y-9j
	for pana@megatron.ietf.org; Fri, 29 Oct 2004 15:46:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29759
	for <pana@ietf.org>; Fri, 29 Oct 2004 15:46:56 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNcwU-0007Bv-SH
	for pana@ietf.org; Fri, 29 Oct 2004 16:01:47 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I6D00K012XCVI@mailout2.samsung.com> for pana@ietf.org; Sat,
	30 Oct 2004 04:46:24 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I6D000O52XBXY@mailout2.samsung.com> for pana@ietf.org;
	Sat, 30 Oct 2004 04:46:24 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I6D006K32X96E@mmp2.samsung.com> for
	pana@ietf.org; Sat, 30 Oct 2004 04:46:23 +0900 (KST)
Date: Fri, 29 Oct 2004 12:46:20 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [Pana] PANA WG last call: draft-ietf-pana-pana-06.txt
In-reply-to: <006a01c4a42c$7d0b5ef0$861167c0@adithya>
To: pana@ietf.org
Message-id: <028701c4bdef$f8175a90$291d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7BIT
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT


I have a long list of editorial comments that I'll send to the
editor/authors. Otherwise, I found just one technical issue:

The M (mandatory) bit is underspecified. We need more explanations about
when it is set, what happens when it is set/unset and an AVP is not
recognized, etc. Is it set for all AVPs defined in the base
specification? If so, let's state that.

Alper



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


From pana-bounces@ietf.org  Fri Oct 29 20:05:08 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27723
	for <pana-archive@lists.ietf.org>; Fri, 29 Oct 2004 20:05:08 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CNgbX-0000Hv-MX; Fri, 29 Oct 2004 19:56:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CNgRw-0001eW-6W
	for pana@megatron.ietf.org; Fri, 29 Oct 2004 19:46:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26925
	for <pana@ietf.org>; Fri, 29 Oct 2004 19:46:24 -0400 (EDT)
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNggI-0005o5-V3
	for pana@ietf.org; Fri, 29 Oct 2004 20:01:19 -0400
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I6D00F05E0JSZ@mailout2.samsung.com> for pana@ietf.org; Sat,
	30 Oct 2004 08:45:55 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I6D000BEE0GXY@mailout2.samsung.com> for pana@ietf.org;
	Sat, 30 Oct 2004 08:45:53 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0I6D00IAKE0EG7@mmp2.samsung.com> for
	pana@ietf.org; Sat, 30 Oct 2004 08:45:52 +0900 (KST)
Date: Fri, 29 Oct 2004 16:45:49 -0700
From: Alper Yegin <alper.yegin@samsung.com>
In-reply-to: <7DBAFEC6A76F3E42817DF1EBE64CB02601813D5A@FTRDMEL2.rd.francetelecom.fr>
To: pana@ietf.org
Message-id: <02f701c4be11$6cf67870$291d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7BIT
Subject: [Pana] PANA WG last call: draft-ietf-pana-framework-02
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7BIT

I reviewed this I-D. It looks good, except some editorial issues. I'll
send them to the editor/authors. 

One technical question:

Why do we have separate DHCP servers in some of the diagrams ("PRPA
DHCPv4 Server" and "POPA DHCPv4 Server")? Can't we just have one "DHCPv4
server"?

Alper



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


From pana-bounces@ietf.org  Sun Oct 31 12:20:49 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14500
	for <pana-archive@lists.ietf.org>; Sun, 31 Oct 2004 12:20:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COJLp-0007lS-3u; Sun, 31 Oct 2004 12:18:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COJJX-0006iq-SN
	for pana@megatron.ietf.org; Sun, 31 Oct 2004 12:16:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13918
	for <pana@ietf.org>; Sun, 31 Oct 2004 12:16:20 -0500 (EST)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COJY6-0000OP-MK
	for pana@ietf.org; Sun, 31 Oct 2004 12:31:37 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id i9VHG9bv020341;
	Mon, 1 Nov 2004 02:16:09 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id i9VHG9dv019578;
	Mon, 1 Nov 2004 02:16:09 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	CAA19577 ; Mon, 1 Nov 2004 02:16:09 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA23498; Mon, 1 Nov 2004 02:16:09 +0900 (JST)
Received: from tsb-sgw2.toshiba.co.jp by toshiba.co.jp id i9VHG8Tq024381;
	Mon, 1 Nov 2004 02:16:08 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw2.toshiba.co.jp  with ESMTP id i9VHG8uY015862;
	Mon, 1 Nov 2004 02:16:08 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I6G00EXXLATWQ@tsbpo1.po.toshiba.co.jp>; Mon,
	1 Nov 2004 02:16:07 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1COILP-0000OU-00; Sun, 31 Oct 2004 08:14:15 -0800
Date: Sun, 31 Oct 2004 11:14:15 -0500
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] PANA WG last call: draft-ietf-pana-ipsec-04.txt
In-reply-to: <021301c4b6ff$67d05a00$6401a8c0@sisa.samsung.com>
To: pana@ietf.org
Message-id: <20041031161415.GP18989@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.6+20040907i
References: <021301c4b6ff$67d05a00$6401a8c0@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

My last call comments on draft-ietf-pana-ipsec-04.txt are available at
http://www.toshiba.com/tari/pana/draft-ietf-pana-ipsec-04_ohba-comments.txt.
Most are editorial comments.  There are three technical comments which
are shown below:

Technical comment 1 (on section 6):

"
           ID_KEY_ID data = (Session-Id | Key-Id)

   The Session-Id and Key-Id are the values contained in the data
   portion of the Session-Id and Key-Id AVP respectively [PANA-PROT].
   They are concatenated to form the content of ID_KEY_ID data. IP
   addresses cannot be used as identifier as the PaC may be re-
   authenticated multiple times and hence may not uniquely identify the
   pre-shared key.
"
$ohba(technical) I don't think the reason for why not using an IP
address of the PaC in ID_KEY_ID is because the PaC may be
*re-authenticated multiple times*.  The actual reason is that the same
PaC or a different PaC may use the same IP address *across a PANA
session*, e.g.,

PaC A acquires IP address X and establishes a PANA session.  After the
PANA session terminates for some reason, the same PaC A or another PaC
B acquires IP address X and establishes a new PANA session.  In this
case, if ID_KEY_ID data were defined as (PaC's IP address | Key-Id),
it would end up with having the same ID_KEY_ID for the two IKE
pre-shared keys derived from two different PANA sessions.

Technical comment 2 (on Appendix A):

"
        When [RFC3456] is used, DHCP is
        run over the IPsec tunnel and the address (IPsec-TIA) is
        assigned to the IPsec tunnel interface.
"

$ohba(technical) I am not sure RFC3456 assumes that IPsec tunnel mode
SA is always implemented as a logical IP interface.  Please check.
(If IPsec tunnel mode SA does not have to be implemented as a logical
IP interface, I think the same source address selection could exist.)

Technical comment 3 (on Appendix A):

"
        The link-local address
        (IPsec-TOA) is assigned to the physical interface. As there is
"

$ohba(technical) Why the IPsec-TOA needs to be a link-local address in
RFC3456?  It could be a non-link-local address, I think.

Best regards,

Yoshihiro Ohba


On Wed, Oct 20, 2004 at 04:49:11PM -0700, Alper Yegin wrote:
> 
> This message announces the PANA WG last call on "PANA Enabling
> IPsec-based Access Control" document (draft-ietf-pana-ipsec-04.txt). The
> last call will conclude on Nov 3rd, 2004.
> 
> Please read and review the document, and register your feedback on the
> PANA mailing list (even if it is a simple "I read the document and it is
> ready to proceed.").
> 
> http://www.ietf.org/internet-drafts/draft-ietf-pana-ipsec-04.txt
> 
> Previously discussed and closed issues on this document can be found at:
> http://danforsberg.info:8080/pana-issues/
> 
> - PANA WG Chairs
> 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

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


From pana-bounces@ietf.org  Sun Oct 31 15:35:34 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01717
	for <pana-archive@lists.ietf.org>; Sun, 31 Oct 2004 15:35:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COMOf-0003X5-Id; Sun, 31 Oct 2004 15:33:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COMKj-0001dS-1l
	for pana@megatron.ietf.org; Sun, 31 Oct 2004 15:29:49 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01015
	for <pana@ietf.org>; Sun, 31 Oct 2004 15:29:47 -0500 (EST)
Received: from mx01.net.com ([134.56.3.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COMZI-0004Rf-Vj
	for pana@ietf.org; Sun, 31 Oct 2004 15:45:04 -0500
Received: from mx02-int.net.com (mx02-int.net.com [134.56.112.14])
	by mx01.net.com (Switch-3.1.3/Switch-3.1.0) with ESMTP id
	i9VKWi7O000640; Sun, 31 Oct 2004 12:32:45 -0800 (PST)
Received: from fmt-ex01.net.com ([134.56.112.251])
	by mx02-int.net.com (Switch-3.1.3/Switch-3.1.0) with ESMTP id
	i9VKWfG5003867; Sun, 31 Oct 2004 12:32:42 -0800 (PST)
Received: from fmt-owa02.net.com ([134.56.112.254]) by fmt-ex01.net.com with
	Microsoft SMTPSVC(6.0.3790.0); Sun, 31 Oct 2004 12:26:38 -0800
Received: from [134.56.24.55] ([134.56.24.55]) by fmt-owa02.net.com with
	Microsoft SMTPSVC(6.0.3790.0); Sun, 31 Oct 2004 12:26:30 -0800
Message-ID: <41854B4D.4020200@net.com>
Date: Sun, 31 Oct 2004 12:30:05 -0800
From: Prakash Jayaraman <prakash_jayaraman@net.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20040618
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@samsung.com>
Subject: Re: [Pana] PANA WG last call: draft-ietf-pana-framework-02
References: <02f701c4be11$6cf67870$291d9069@sisa.samsung.com>
In-Reply-To: <02f701c4be11$6cf67870$291d9069@sisa.samsung.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Oct 2004 20:26:30.0516 (UTC)
	FILETIME=[E7E39B40:01C4BF87]
X-Spam-Status: No, hits=-1.2 required=8.0 tests=AWL autolearn=ham version=2.63
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on fmt-spam02
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org
Content-Transfer-Encoding: 7bit

PRPA address space (and DHCP server) and POPA address space (and DHCP 
server) could be under different administrative domains.  The draft 
could state that these DHCP servers could be same or different depending 
upon deployment.

- prakash


Alper Yegin wrote:

>I reviewed this I-D. It looks good, except some editorial issues. I'll
>send them to the editor/authors. 
>
>One technical question:
>
>Why do we have separate DHCP servers in some of the diagrams ("PRPA
>DHCPv4 Server" and "POPA DHCPv4 Server")? Can't we just have one "DHCPv4
>server"?
>
>Alper
>
>
>
>_______________________________________________
>Pana mailing list
>Pana@ietf.org
>https://www1.ietf.org/mailman/listinfo/pana
>  
>


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


From pana-bounces@ietf.org  Sun Oct 31 23:37:02 2004
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03806
	for <pana-archive@lists.ietf.org>; Sun, 31 Oct 2004 23:37:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1COTrc-00070O-JN; Sun, 31 Oct 2004 23:32:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1COTqI-0006pY-5C
	for pana@megatron.ietf.org; Sun, 31 Oct 2004 23:30:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA03366
	for <pana@ietf.org>; Sun, 31 Oct 2004 23:30:50 -0500 (EST)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COU4v-0004eD-CP
	for pana@ietf.org; Sun, 31 Oct 2004 23:46:13 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id iA14UYbv027712;
	Mon, 1 Nov 2004 13:30:34 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id iA14UY7v009020;
	Mon, 1 Nov 2004 13:30:34 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id
	PAA09019 ; Mon, 1 Nov 2004 13:30:33 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id NAA28279; Mon, 1 Nov 2004 13:30:32 +0900 (JST)
Received: from tsb-sgw2.toshiba.co.jp by toshiba.co.jp id iA14UVBV000065;
	Mon, 1 Nov 2004 13:30:32 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp 
	by tsb-sgw2.toshiba.co.jp  with ESMTP id iA14UVuY004639;
	Mon, 1 Nov 2004 13:30:31 +0900 (JST)
Received: from steelhead (iVPN11-040.mobile.toshiba.co.jp)
	by tsbpo1.po.toshiba.co.jp
	(Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
	with ESMTP id <0I6H005WGGITFK@tsbpo1.po.toshiba.co.jp>; Mon,
	1 Nov 2004 13:30:30 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
	id 1COTUk-00012A-00; Sun, 31 Oct 2004 20:08:38 -0800
Date: Sun, 31 Oct 2004 23:08:38 -0500
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] PANA WG last call: draft-ietf-pana-pana-06.txt
In-reply-to: <03d001c4b792$c03fa040$6401a8c0@sisa.samsung.com>
To: pana@ietf.org
Message-id: <20041101040838.GE2224@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: pana@ietf.org
User-Agent: Mutt/1.5.6+20040907i
References: <021301c4b6ff$67d05a00$6401a8c0@sisa.samsung.com>
	<03d001c4b792$c03fa040$6401a8c0@sisa.samsung.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access
	<pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

These are my last call comments on draft-ietf-pana-pana-06.txt.

o Technical comment 1 (section 4.2)

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

The two "SHOULD" in the above text are ambiguous.  I think when a
Protection-Capability AVP is included in the PBR, a Device-Id AVP MUST
be included in order to indicate the MAC or IP address of each EP.
Also, when a Protection-Capability AVP is included, I think it is
always true that the device identifier of each EP is either MAC or IP
address.  On the other hand, when the PBR includes a Device-Id AVP, I
think that the PaC MUST include a Device-Id AVP in the PBA.  In this
case, what the PAA should do if the PAA sent a PBR with a
Protection-Capability AVP and one or more Device-Id AVP but the PBA
from the PaC does not contain any Device-Id AVP?  I think the right
behavior for this case is that the PAA sends a PANA-Error-Request
message with a PANA_MISSING_AVP result code and wait for a
PANA-Error-Answer message to terminate the session.

Suggested change:

"
   The PANA-Bind-Request and the PANA-Bind-Answer message exchange is
   also used for binding device identifiers of the PaC and EP(s), and
   the IP address of the PAA to the PANA SA.  To achieve this, the
   PANA-Bind-Request message MUST contain the device identifier(s) of
   EP(s) in Device-Id AVP(s) when a Protection-Capability ASP is
   included in the message.  The PANA-Bind-Request message MUST also
   contain the IP address of the PAA in an IP-Address AVP.  The
   PANA-Bind-Answer message MUST contain the PaC's device identifier
   in a Device-Id AVP when it is already presented with that of EP(s)
   in the request with using the same type of device identifier as
   contained in the request.  If the PANA-Bind-Answer message sent
   from the PaC does not contain a Device-Id AVP with the same device
   identifier type contained in the request, the PAA sends a
   PANA-Error-Request message with a PANA_MISSING_AVP result code, and
   wait for a PANA-Error-Answer message to terminate the session.
"

o Technical comment 2 (section 4.2)

"
   The PANA-Bind-Request message MAY also contain a
   Protection-Capability AVP to indicate if link-layer or network-layer
   ciphering should be initiated after PANA.  
"

If the Result-Code AVP included in the PBR does not indicate
PANA_SUCCESS, I think a Protection-Capability AVP does not need to be
included (or SHOULD NOT be included, to avoid unnecessary information
disclosure to unauthorized clients) in the PBR and the corresponding
PBA.

Suggested change:

"
   The PANA-Bind-Request message with a PANA_SUCCESS result code MAY
   also contain a Protection-Capability AVP to indicate if link-layer
   or network-layer ciphering should be initiated after PANA.
"


o Technical comment 3 (section 4.2)

"
   Additionally, PANA-Bind-Request MUST include a
   Post-PANA-Address-Configuration AVP, which helps PAA to inform PaC
   about whether a new IP address MUST be configured and the available
   methods to do so.  PaC MUST include a PPAC AVP in order to indicate
   its choice of method when there is a match between the methods
   offered by the PAA and the methods available on the PaC.
"

If the Result-Code AVP included in the PBR does not indicate
PANA_SUCCESS, I think a PPAC AVP does not need to be included (or
SHOULD NOT be included, to avoid unnecessary information disclosure to
unauthorized clients) in the PBR and the corresponding PBA.  Also
there is some duplicated wording "PaC MUST include a PPAC AVP in order
to indicate" text in the text.

Suggested change:

"
   Additionally, the PANA-Bind-Request message with a PANA_SUCCESS
   result code MUST include a Post-PANA-Address-Configuration AVP,
   which helps the PAA to inform the PaC about whether a new IP
   address MUST be configured and the available methods to do so.  The
   PaC MUST include a PPAC AVP in the PANA-Bind-Answer message in
   order to indicate its choice of method when there is a match
   between the methods offered by the PAA and the methods available on
   the PaC.
"

o Technical comment 4 (section 6.2)

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

Since MAC for the PSR used for mobility handling is calculated by
using a different key other than the PANA_MAC_KEY that is to be
established between the PaC and the current PAA and used for
subsequent PANA messages, I would suggest using a separate AVP
(something like Mobility-Optimization-MAC AVP or Mobility-Token AVP )
for this special MAC carried in PSR rather than overloading the MAC
AVP to be used with different keys, in order to avoid possible
mis-implementation.


Best regards,
Yoshihiro Ohba

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


