From pana-admin@ietf.org  Wed Oct  1 04:21:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02585
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 04:21:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cEI-00005n-8d; Wed, 01 Oct 2003 04:21:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cDo-00004t-P4
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 04:20:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02562
	for <pana@ietf.org>; Wed, 1 Oct 2003 04:20:25 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cDl-0003pi-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:20:29 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cDl-0003pf-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:20:29 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h918KTt21876
	for <pana@ietf.org>; Wed, 1 Oct 2003 11:20:29 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6503c96d27ac158f24077@esvir04nok.ntc.nokia.com>;
 Wed, 1 Oct 2003 11:20:29 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:20:28 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:20:28 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] Issue 5
Date: Wed, 1 Oct 2003 11:20:27 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D10@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 5
Thread-Index: AcOHtLG2VMw4hagFQg2eQTF1KQzdQwAP+MXA
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 08:20:28.0403 (UTC) FILETIME=[DF43AC30:01C387F4]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Since the issue 5 was already closed I created a new issue about this.
http://danforsberg.info:8080/pana-issues/issue33

A comment about the Device-Id.
From section 4.1.7.

   o When a Device-Id AVP is included, the AVP is valid if the device=20
   identifier type contained in the AVP matches the expected one (this=20
   check is for PAA only) and the device identifier value contained in=20
   the AVP matches the value extracted from the lower-layer=20
   encapsulation header corresponding to the device identifier type=20
   contained in the AVP.=20

Section 4.7. seems to assume that Device-Id carries the PaC's device id =
in messages from PaC to PAA and PAA's device id in messages from PAA to =
PaC. I think this should be clarified in the draft. I.e. why "this check =
is for PAA only" is valid?

Br,
- Dan


> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 01 October, 2003 03:39
> To: pana@ietf.org
> Subject: [Pana] Issue 5
>=20
>=20
>=20
> New proposed text for section 4.7, for handling issue 5.=20
> Comments welcome...
> http://danforsberg.info:8080/pana-issues/issue5
>=20
> 4.7 Device ID Choice
>    =20
>    A PaC SHOULD configure an IP address before PANA if it=20
> can. It might
>    either have a pre-configured IP address, or have to obtain one via
>    dynamic methods such as DHCP or stateless address=20
> autoconfiguration.
>    Dynamic methods may or may not succeed depending on the local
>    security policy.  In networks where clients have to be authorized
>    before they are allowed to obtain an IP address, EPs will=20
> detect the
>    associated activity and PANA protocol will be engaged=20
> before the clients
>    can configure a valid IP address.
>   =20
>    Either an IP address or a link-layer address should be=20
> used as device
>    ID at any time. It is assumed that PAA knows the security=20
> mechanisms
>    being provided or required on the access network (e.g.,=20
> based on physical
>    security, link-layer ciphers enabled before or after PANA,=20
> or IPsec).
>    When IPsec-based mechanism [PANA-IPSEC] is the choice of=20
> access control,
>    PAA should provide its IP address as device ID, and expect=20
> the PaC to
>    provide its IP address in return.  In all other cases, link-layer
>    addresses can be provided from both sides.
>    =20
>    When IPsec-based access control is used but the PaC is using an
>    unspecified IP address in the authentication phase, the device ID
>    reported by the PaC MUST be either 0.0.0.0 or 0::0. This=20
> device ID MUST
>    be recorded as a temporary one by the PAA until the PaC=20
> obtains a valid
>    one and informs the PAA. Eventually PaC MUST obtain an IP address,
>    possibly by relying on the newly-created PANA session=20
> [PANA-DHCP], in
>    order to gain full access to the network. PaC MUST update=20
> the device
>    identifier registered on the PAA from unspecified to the=20
> valid IP address
>    by initiating a PANA-Reauth-Request/PANA-Reauth-Answer exchange in
>    which the IP address of the PaC is contained in the Device-Id AVP.
>=20
> References:
>=20
> [PANA-IPSEC] M. Parthasarathy: "Securing the first hop in=20
> PANA using IPsec,"
> Internet Draft, Internet Engineering Task Force, May 2003, Work in
> progress.=20
>=20
> [PANA-DHCP] H. Tschofenig, A. Yegin, D. Forsberg:=20
> "Bootstrapping RFC3118
> Delayed authentication using PANA," Internet Draft, Internet=20
> Engineering
> Task Force, June 2003, Work in progress.=20
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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


From exim@www1.ietf.org  Wed Oct  1 04:21:44 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02607
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 04:21:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cEb-000083-1C
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 04:21:21 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h918LKNk000484
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 04:21:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cEZ-00007j-HU
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 04:21:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02575
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 04:21:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cEK-0003qB-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 04:21:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cEK-0003q8-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 04:21:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cEI-00005n-8d; Wed, 01 Oct 2003 04:21:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cDo-00004t-P4
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 04:20:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02562
	for <pana@ietf.org>; Wed, 1 Oct 2003 04:20:25 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cDl-0003pi-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:20:29 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cDl-0003pf-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:20:29 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h918KTt21876
	for <pana@ietf.org>; Wed, 1 Oct 2003 11:20:29 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6503c96d27ac158f24077@esvir04nok.ntc.nokia.com>;
 Wed, 1 Oct 2003 11:20:29 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:20:28 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:20:28 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] Issue 5
Date: Wed, 1 Oct 2003 11:20:27 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D10@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 5
Thread-Index: AcOHtLG2VMw4hagFQg2eQTF1KQzdQwAP+MXA
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 08:20:28.0403 (UTC) FILETIME=[DF43AC30:01C387F4]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Since the issue 5 was already closed I created a new issue about this.
http://danforsberg.info:8080/pana-issues/issue33

A comment about the Device-Id.
From section 4.1.7.

   o When a Device-Id AVP is included, the AVP is valid if the device=20
   identifier type contained in the AVP matches the expected one (this=20
   check is for PAA only) and the device identifier value contained in=20
   the AVP matches the value extracted from the lower-layer=20
   encapsulation header corresponding to the device identifier type=20
   contained in the AVP.=20

Section 4.7. seems to assume that Device-Id carries the PaC's device id =
in messages from PaC to PAA and PAA's device id in messages from PAA to =
PaC. I think this should be clarified in the draft. I.e. why "this check =
is for PAA only" is valid?

Br,
- Dan


> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 01 October, 2003 03:39
> To: pana@ietf.org
> Subject: [Pana] Issue 5
>=20
>=20
>=20
> New proposed text for section 4.7, for handling issue 5.=20
> Comments welcome...
> http://danforsberg.info:8080/pana-issues/issue5
>=20
> 4.7 Device ID Choice
>    =20
>    A PaC SHOULD configure an IP address before PANA if it=20
> can. It might
>    either have a pre-configured IP address, or have to obtain one via
>    dynamic methods such as DHCP or stateless address=20
> autoconfiguration.
>    Dynamic methods may or may not succeed depending on the local
>    security policy.  In networks where clients have to be authorized
>    before they are allowed to obtain an IP address, EPs will=20
> detect the
>    associated activity and PANA protocol will be engaged=20
> before the clients
>    can configure a valid IP address.
>   =20
>    Either an IP address or a link-layer address should be=20
> used as device
>    ID at any time. It is assumed that PAA knows the security=20
> mechanisms
>    being provided or required on the access network (e.g.,=20
> based on physical
>    security, link-layer ciphers enabled before or after PANA,=20
> or IPsec).
>    When IPsec-based mechanism [PANA-IPSEC] is the choice of=20
> access control,
>    PAA should provide its IP address as device ID, and expect=20
> the PaC to
>    provide its IP address in return.  In all other cases, link-layer
>    addresses can be provided from both sides.
>    =20
>    When IPsec-based access control is used but the PaC is using an
>    unspecified IP address in the authentication phase, the device ID
>    reported by the PaC MUST be either 0.0.0.0 or 0::0. This=20
> device ID MUST
>    be recorded as a temporary one by the PAA until the PaC=20
> obtains a valid
>    one and informs the PAA. Eventually PaC MUST obtain an IP address,
>    possibly by relying on the newly-created PANA session=20
> [PANA-DHCP], in
>    order to gain full access to the network. PaC MUST update=20
> the device
>    identifier registered on the PAA from unspecified to the=20
> valid IP address
>    by initiating a PANA-Reauth-Request/PANA-Reauth-Answer exchange in
>    which the IP address of the PaC is contained in the Device-Id AVP.
>=20
> References:
>=20
> [PANA-IPSEC] M. Parthasarathy: "Securing the first hop in=20
> PANA using IPsec,"
> Internet Draft, Internet Engineering Task Force, May 2003, Work in
> progress.=20
>=20
> [PANA-DHCP] H. Tschofenig, A. Yegin, D. Forsberg:=20
> "Bootstrapping RFC3118
> Delayed authentication using PANA," Internet Draft, Internet=20
> Engineering
> Task Force, June 2003, Work in progress.=20
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-admin@ietf.org  Wed Oct  1 04:22:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02673
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 04:22:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFE-0000Al-Tz; Wed, 01 Oct 2003 04:22:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cEa-00007q-KE
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 04:21:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02578
	for <pana@ietf.org>; Wed, 1 Oct 2003 04:21:13 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cEX-0003qP-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:21:17 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cEX-0003qJ-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:21:17 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h918LHt22944
	for <pana@ietf.org>; Wed, 1 Oct 2003 11:21:17 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6503ca26dbac158f23077@esvir03nok.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 11:21:16 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:21:17 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:21:17 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 11:21:16 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D12@esebe008.ntc.nokia.com>
Thread-Topic: [issue21] Conformancy with RFC2284bis and draft-ietf-aaa-eap-02
Thread-Index: AcOH8gKFLrtijd/kSjeAPVkTDDglmQAAvLdg
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 08:21:17.0229 (UTC) FILETIME=[FC5DEDD0:01C387F4]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue21] Conformancy with RFC2284bis and draft-ietf-aaa-eap-02
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

PANA co-exists with NAS when necessary. Thus, NAS can provide =
EAP-Request
retransmissions. This should be clarified in the draft. I.e. update:

   "PANA relies on EAP-layer retransmission for retransmitting EAP=20
   Request based on timer."

to:

   "PANA relies on EAP-layer retransmissions, or for example NAS=20
   functionality [DIAMETER-EAP], for retransmitting EAP Requests=20
   based on timer."

________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue21
________________________________________________

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


From pana-admin@ietf.org  Wed Oct  1 04:22:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02688
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 04:22:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFF-0000BT-V5; Wed, 01 Oct 2003 04:22:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cEH-00005Z-7h
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 04:21:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02571
	for <pana@ietf.org>; Wed, 1 Oct 2003 04:20:54 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cEE-0003q5-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:20:58 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cED-0003q2-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:20:57 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h918Kwt22513
	for <pana@ietf.org>; Wed, 1 Oct 2003 11:20:58 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6503c9db2cac158f23077@esvir03nok.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 11:20:57 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:20:57 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 11:20:57 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D11@esebe008.ntc.nokia.com>
Thread-Topic: [issue9] Message format
Thread-Index: AcOH81SORJNLgrbATGiWC9mCVVkfhwAAZGuw
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 08:20:57.0881 (UTC) FILETIME=[F0D5A890:01C387F4]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue9] Message format
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

This issue (section 9) is not valid anymore and has been splitted into
several other issues (issue18, issue19, issue17, issue24, issue23, =
issue22).


----------
status: Text Proposed -> Closed
_______________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue9
_______________________________________________

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


From exim@www1.ietf.org  Wed Oct  1 04:22:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02707
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 04:22:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFH-0000HG-Vg
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 04:22:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h918M31h000905
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 04:22:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFF-0000BR-Tg
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 04:22:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02627
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 04:21:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cFD-0003qu-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 04:21:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cFC-0003qr-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 04:21:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFE-0000Al-Tz; Wed, 01 Oct 2003 04:22:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cEa-00007q-KE
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 04:21:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02578
	for <pana@ietf.org>; Wed, 1 Oct 2003 04:21:13 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cEX-0003qP-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:21:17 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cEX-0003qJ-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:21:17 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h918LHt22944
	for <pana@ietf.org>; Wed, 1 Oct 2003 11:21:17 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6503ca26dbac158f23077@esvir03nok.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 11:21:16 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:21:17 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:21:17 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 11:21:16 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D12@esebe008.ntc.nokia.com>
Thread-Topic: [issue21] Conformancy with RFC2284bis and draft-ietf-aaa-eap-02
Thread-Index: AcOH8gKFLrtijd/kSjeAPVkTDDglmQAAvLdg
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 08:21:17.0229 (UTC) FILETIME=[FC5DEDD0:01C387F4]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue21] Conformancy with RFC2284bis and draft-ietf-aaa-eap-02
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

PANA co-exists with NAS when necessary. Thus, NAS can provide =
EAP-Request
retransmissions. This should be clarified in the draft. I.e. update:

   "PANA relies on EAP-layer retransmission for retransmitting EAP=20
   Request based on timer."

to:

   "PANA relies on EAP-layer retransmissions, or for example NAS=20
   functionality [DIAMETER-EAP], for retransmitting EAP Requests=20
   based on timer."

________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue21
________________________________________________

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



From exim@www1.ietf.org  Wed Oct  1 04:22:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02714
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 04:22:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFI-0000In-NU
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 04:22:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h918M41R001130
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 04:22:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFH-0000H9-Q6
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 04:22:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02634
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 04:21:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cFE-0003r5-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 04:22:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cFE-0003r2-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 04:22:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFF-0000BT-V5; Wed, 01 Oct 2003 04:22:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cEH-00005Z-7h
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 04:21:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02571
	for <pana@ietf.org>; Wed, 1 Oct 2003 04:20:54 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cEE-0003q5-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:20:58 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cED-0003q2-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:20:57 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h918Kwt22513
	for <pana@ietf.org>; Wed, 1 Oct 2003 11:20:58 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6503c9db2cac158f23077@esvir03nok.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 11:20:57 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:20:57 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 11:20:57 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D11@esebe008.ntc.nokia.com>
Thread-Topic: [issue9] Message format
Thread-Index: AcOH81SORJNLgrbATGiWC9mCVVkfhwAAZGuw
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 08:20:57.0881 (UTC) FILETIME=[F0D5A890:01C387F4]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue9] Message format
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

This issue (section 9) is not valid anymore and has been splitted into
several other issues (issue18, issue19, issue17, issue24, issue23, =
issue22).


----------
status: Text Proposed -> Closed
_______________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue9
_______________________________________________

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



From pana-admin@ietf.org  Wed Oct  1 04:22:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02742
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 04:22:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFI-0000IY-Ew; Wed, 01 Oct 2003 04:22:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFA-0000AO-39
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 04:21:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02623
	for <pana@ietf.org>; Wed, 1 Oct 2003 04:21:49 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cF7-0003qo-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:21:53 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cF6-0003ql-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:21:52 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h918Lr614600
	for <pana@ietf.org>; Wed, 1 Oct 2003 11:21:53 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6503cab589ac158f21083@esvir01nok.ntc.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 11:21:53 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:21:53 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 11:21:52 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D13@esebe008.ntc.nokia.com>
Thread-Topic: [issue27] Non-acknowledgement error notification
Thread-Index: AcOH7dnX7SKn3ebWTzGOS0AVfBLErgABzDuQ
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 08:21:53.0283 (UTC) FILETIME=[11DB5530:01C387F5]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue27] Non-acknowledgement error notification
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

See issue17.


----------
status: No Discussion -> Closed
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue27
________________________________________________

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


From exim@www1.ietf.org  Wed Oct  1 04:22:34 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02757
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 04:22:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFP-0000Kn-96
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 04:22:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h918MBnY001279
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 04:22:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFP-0000KY-2H
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 04:22:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02651
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 04:22:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cFM-0003rV-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 04:22:08 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cFL-0003rS-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 04:22:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFI-0000IY-Ew; Wed, 01 Oct 2003 04:22:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cFA-0000AO-39
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 04:21:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02623
	for <pana@ietf.org>; Wed, 1 Oct 2003 04:21:49 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cF7-0003qo-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:21:53 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cF6-0003ql-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:21:52 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h918Lr614600
	for <pana@ietf.org>; Wed, 1 Oct 2003 11:21:53 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6503cab589ac158f21083@esvir01nok.ntc.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 11:21:53 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:21:53 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 11:21:52 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D13@esebe008.ntc.nokia.com>
Thread-Topic: [issue27] Non-acknowledgement error notification
Thread-Index: AcOH7dnX7SKn3ebWTzGOS0AVfBLErgABzDuQ
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 08:21:53.0283 (UTC) FILETIME=[11DB5530:01C387F5]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue27] Non-acknowledgement error notification
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

See issue17.


----------
status: No Discussion -> Closed
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue27
________________________________________________

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



From pana-admin@ietf.org  Wed Oct  1 04:33:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03014
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 04:33:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cPy-0000lz-Oc; Wed, 01 Oct 2003 04:33:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cPP-0000h2-8c
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 04:32:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02971
	for <pana@ietf.org>; Wed, 1 Oct 2003 04:32:23 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cPL-0003xX-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:32:27 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cPL-0003xU-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:32:27 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h918WRt07198
	for <pana@ietf.org>; Wed, 1 Oct 2003 11:32:27 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6503d461c7ac158f24077@esvir04nok.ntc.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 11:32:27 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:32:27 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 11:32:26 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D14@esebe008.ntc.nokia.com>
Thread-Topic: PANA issues
Thread-Index: AcOH9ouGKoQSL2WoTBC3uPJyAeojqQ==
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 08:32:27.0075 (UTC) FILETIME=[8BA05130:01C387F6]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] PANA issues
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi folks,

I have created new document types to the PANA issue tracker. These =
document types identify the version of the PANA protocol draft (01, 02, =
03 etc.).=20

PANA chair Alper Yegin had requested assignments of the issues. This is =
now also visible in the PANA issue tracker as well as the issues that =
are being resolved currently for the next version of the draft (document =
type draft-ietf-pana-pana-01.txt).

If issues that are listed with document type draft-ietf-pana-pana-01.txt =
are not resolved in the 02 draft, their document type will be changed =
either to draft-ietf-pana-pana-xx.txt of draft-ietf-pana-pana-02.txt.=20

Editorial issues are always specific to a certain version of the draft =
(i.e. document type draft-ietf-pana-pana-xx.txt is not possible) and =
must be resolved in the next version of the draft.

I have also taken an approach, where I don't always forward the PANA =
issue tracker notification to the pana mailing list because the text =
would be duplicated (especially in case of "text proposed" cases).

Any comments are welcome to these policy issues.

Br,
- Dan
"PANA issue tracker admin"

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


From exim@www1.ietf.org  Wed Oct  1 04:33:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03029
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 04:33:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cQ3-0000o9-QP
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 04:33:13 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h918XBnY003097
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 04:33:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cQ3-0000nm-E8
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 04:33:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02992
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 04:33:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cQ0-0003xz-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 04:33:08 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cPz-0003xw-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 04:33:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cPy-0000lz-Oc; Wed, 01 Oct 2003 04:33:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4cPP-0000h2-8c
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 04:32:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02971
	for <pana@ietf.org>; Wed, 1 Oct 2003 04:32:23 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cPL-0003xX-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:32:27 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4cPL-0003xU-00
	for pana@ietf.org; Wed, 01 Oct 2003 04:32:27 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h918WRt07198
	for <pana@ietf.org>; Wed, 1 Oct 2003 11:32:27 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6503d461c7ac158f24077@esvir04nok.ntc.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 11:32:27 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 11:32:27 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 11:32:26 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D14@esebe008.ntc.nokia.com>
Thread-Topic: PANA issues
Thread-Index: AcOH9ouGKoQSL2WoTBC3uPJyAeojqQ==
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 08:32:27.0075 (UTC) FILETIME=[8BA05130:01C387F6]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] PANA issues
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi folks,

I have created new document types to the PANA issue tracker. These =
document types identify the version of the PANA protocol draft (01, 02, =
03 etc.).=20

PANA chair Alper Yegin had requested assignments of the issues. This is =
now also visible in the PANA issue tracker as well as the issues that =
are being resolved currently for the next version of the draft (document =
type draft-ietf-pana-pana-01.txt).

If issues that are listed with document type draft-ietf-pana-pana-01.txt =
are not resolved in the 02 draft, their document type will be changed =
either to draft-ietf-pana-pana-xx.txt of draft-ietf-pana-pana-02.txt.=20

Editorial issues are always specific to a certain version of the draft =
(i.e. document type draft-ietf-pana-pana-xx.txt is not possible) and =
must be resolved in the next version of the draft.

I have also taken an approach, where I don't always forward the PANA =
issue tracker notification to the pana mailing list because the text =
would be duplicated (especially in case of "text proposed" cases).

Any comments are welcome to these policy issues.

Br,
- Dan
"PANA issue tracker admin"

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



From pana-admin@ietf.org  Wed Oct  1 06:19:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06817
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 06:19:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e4U-0006Vz-5A; Wed, 01 Oct 2003 06:19:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e4G-0006VM-7Q
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 06:18:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06789
	for <pana@ietf.org>; Wed, 1 Oct 2003 06:18:39 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e4C-0005IL-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:18:44 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e4B-0005II-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:18:43 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h91AIi603749
	for <pana@ietf.org>; Wed, 1 Oct 2003 13:18:44 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T650435ad02ac158f25446@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 13:18:43 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 13:18:43 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 13:18:42 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D17@esebe008.ntc.nokia.com>
Thread-Topic: [issue20] Retransmission timers and counts
Thread-Index: AcOIBAXhmq2KWPjCR8e9m9gaC8OZNQAAVXAw
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 10:18:43.0408 (UTC) FILETIME=[64378500:01C38805]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue20] Retransmission timers and counts
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

X. PANA protocol message retransmissions

   The PANA protocol provides retransmissions for messages that do not
   carry EAP payload AVP.  The messages that need retransmissions are
   listed below:

        PANA-PAA-Discover (PDI)
        PANA-Start-Answer (PSA)
        PANA-Bind-Request (PBR)
        PANA-Reauth-Request (PRAR)
        PANA-Termination-Request (PTR)

   The PDI and PSA messages are always sent by the PaC.  PBR is sent
   by PAA.  The last two messages, PRAR and PTR are sent either by PaC
   or PAA.

   The rule is that the sender of the request message retransmits the
   request if the corresponding answer is not received in time.
   Answer messages are sent as answers to the request messages, not
   based on a timer.  Exception to this rule is the PSA message.
   Because of the stateless nature of the PAA in the beginning PaC
   provides retransmission also for the PSA message.  PANA-Error
   messages MUST not be retransmitted.  See section <TBD> for more
   details of PANA error handling.

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

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

      RT     Retransmission timeout

      IRT    Initial retransmission time

      MRC    Maximum retransmission count

      MRT    Maximum retransmission time

      MRD    Maximum retransmission duration

      RAND   Randomization factor

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

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

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

   RT for the first message transmission is based on IRT:

      RT =3D IRT + RAND*IRT

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

      RT =3D 2*RTprev + RAND*RTprev

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

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

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

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

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

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


X.1. Transmission and Retransmission Parameters

   This section presents a table of values used to describe the
   message retransmission behavior of request and PANA-Start-Answer
   messages marked with REQ_*.  PANA-PAA-Discover message
   retransmission values are marked with PDI_*. The table shows
   default values.

   Parameter       Default   Description
   ------------------------------------------------
   PDI_IRT           1 sec   Initial PDI timeout.
   PDI_MRT         120 secs  Max PDI timeout value.
   PDI_MRC           0       Configurable.
   PDI_MRD           0       Configurable.

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


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

      RT =3D REQ_IRT + RAND*REQ_IRT


----------
status: Pending -> Text Proposed
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue20
________________________________________________

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


From exim@www1.ietf.org  Wed Oct  1 06:19:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06843
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 06:19:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e4X-0006Wr-8n
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 06:19:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h91AJ5u2025095
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 06:19:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e4X-0006Wg-1z
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 06:19:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06799
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 06:18:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e4T-0005IU-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 06:19:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e4S-0005IO-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 06:19:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e4T-0006Vf-MT; Wed, 01 Oct 2003 06:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e3w-0006V1-MA
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 06:18:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06776
	for <pana@ietf.org>; Wed, 1 Oct 2003 06:18:20 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e3s-0005I1-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:18:24 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e3s-0005Hx-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:18:24 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h91AIO603314
	for <pana@ietf.org>; Wed, 1 Oct 2003 13:18:24 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65043560f8ac158f21083@esvir01nok.ntc.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 13:18:23 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 13:18:24 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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 issues
Date: Wed, 1 Oct 2003 13:18:23 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C586@esebe008.ntc.nokia.com>
Thread-Topic: PANA issues
Thread-Index: AcOH9ouGKoQSL2WoTBC3uPJyAeojqQADHe/g
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 10:18:24.0546 (UTC) FILETIME=[58F96820:01C38805]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

One more comment about the statuses for the issues. There=20
are eight possible status values (all but Rejected and Closed=20
are borrowed from EAP issues=20
[http://www.drizzle.com/~aboba/EAP/eapissues.html]). An issue=20
can have only one of these in any time:

TEXT PROPOSED
   Text has been proposed on the list, and no consensus=20
   has been reached

ACCEPTED
   Text has been proposed, consensus has been reached,=20
   but the fix hasn't been included in a specification yet.

PENDING
   Discussion is on-going, no proposed text has been proposed

NO DISCUSSION
   No discussion has been initiated on this issue.

CLARIFYING TEXT REQUIRED
   The issue can be closed if additional clarifying text is=20
   added to the draft

POSSIBLE REJECT
   Issue will be rejected unless objections occur.

CLOSED
   The issue has been incorporated into the draft or some other
   reason with explanation in the issue body.

REJECTED
   The issue was rejected (no consensus on the list).


The query "Show Open" currently shows all issues that are not=20
CLOSED or REJECTED. The query "Show All" shows REJECTED and CLOSED
issues too. If the issue was CLOSED or REJECTED it should contain
an explanation about the reason for doing this. The default reason=20
for CLOSED issue is that it was incorporated into the draft.

Any comments are welcome.

Br,
- Dan


> -----Original Message-----
> From: ext Dan.Forsberg@nokia.com [mailto:Dan.Forsberg@nokia.com]
> Sent: 01 October, 2003 11:32
> To: pana@ietf.org
> Subject: [Pana] PANA issues
>=20
>=20
> Hi folks,
>=20
> I have created new document types to the PANA issue tracker.=20
> These document types identify the version of the PANA=20
> protocol draft (01, 02, 03 etc.).=20
>=20
> PANA chair Alper Yegin had requested assignments of the=20
> issues. This is now also visible in the PANA issue tracker as=20
> well as the issues that are being resolved currently for the=20
> next version of the draft (document type draft-ietf-pana-pana-01.txt).
>=20
> If issues that are listed with document type=20
> draft-ietf-pana-pana-01.txt are not resolved in the 02 draft,=20
> their document type will be changed either to=20
> draft-ietf-pana-pana-xx.txt of draft-ietf-pana-pana-02.txt.=20
>=20
> Editorial issues are always specific to a certain version of=20
> the draft (i.e. document type draft-ietf-pana-pana-xx.txt is=20
> not possible) and must be resolved in the next version of the draft.
>=20
> I have also taken an approach, where I don't always forward=20
> the PANA issue tracker notification to the pana mailing list=20
> because the text would be duplicated (especially in case of=20
> "text proposed" cases).
>=20
> Any comments are welcome to these policy issues.
>=20
> Br,
> - Dan
> "PANA issue tracker admin"
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From exim@www1.ietf.org  Wed Oct  1 06:19:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06845
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 06:19:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e4X-0006XD-G6
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 06:19:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h91AJ581025113
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 06:19:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e4X-0006Ww-BY
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 06:19:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06802
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 06:18:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e4T-0005IX-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 06:19:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e4S-0005IP-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 06:19:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e4U-0006Vz-5A; Wed, 01 Oct 2003 06:19:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e4G-0006VM-7Q
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 06:18:48 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06789
	for <pana@ietf.org>; Wed, 1 Oct 2003 06:18:39 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e4C-0005IL-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:18:44 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e4B-0005II-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:18:43 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h91AIi603749
	for <pana@ietf.org>; Wed, 1 Oct 2003 13:18:44 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T650435ad02ac158f25446@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 13:18:43 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 13:18:43 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 13:18:42 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D17@esebe008.ntc.nokia.com>
Thread-Topic: [issue20] Retransmission timers and counts
Thread-Index: AcOIBAXhmq2KWPjCR8e9m9gaC8OZNQAAVXAw
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 10:18:43.0408 (UTC) FILETIME=[64378500:01C38805]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue20] Retransmission timers and counts
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

X. PANA protocol message retransmissions

   The PANA protocol provides retransmissions for messages that do not
   carry EAP payload AVP.  The messages that need retransmissions are
   listed below:

        PANA-PAA-Discover (PDI)
        PANA-Start-Answer (PSA)
        PANA-Bind-Request (PBR)
        PANA-Reauth-Request (PRAR)
        PANA-Termination-Request (PTR)

   The PDI and PSA messages are always sent by the PaC.  PBR is sent
   by PAA.  The last two messages, PRAR and PTR are sent either by PaC
   or PAA.

   The rule is that the sender of the request message retransmits the
   request if the corresponding answer is not received in time.
   Answer messages are sent as answers to the request messages, not
   based on a timer.  Exception to this rule is the PSA message.
   Because of the stateless nature of the PAA in the beginning PaC
   provides retransmission also for the PSA message.  PANA-Error
   messages MUST not be retransmitted.  See section <TBD> for more
   details of PANA error handling.

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

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

      RT     Retransmission timeout

      IRT    Initial retransmission time

      MRC    Maximum retransmission count

      MRT    Maximum retransmission time

      MRD    Maximum retransmission duration

      RAND   Randomization factor

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

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

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

   RT for the first message transmission is based on IRT:

      RT =3D IRT + RAND*IRT

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

      RT =3D 2*RTprev + RAND*RTprev

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

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

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

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

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

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


X.1. Transmission and Retransmission Parameters

   This section presents a table of values used to describe the
   message retransmission behavior of request and PANA-Start-Answer
   messages marked with REQ_*.  PANA-PAA-Discover message
   retransmission values are marked with PDI_*. The table shows
   default values.

   Parameter       Default   Description
   ------------------------------------------------
   PDI_IRT           1 sec   Initial PDI timeout.
   PDI_MRT         120 secs  Max PDI timeout value.
   PDI_MRC           0       Configurable.
   PDI_MRD           0       Configurable.

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


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

      RT =3D REQ_IRT + RAND*REQ_IRT


----------
status: Pending -> Text Proposed
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue20
________________________________________________

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



From pana-admin@ietf.org  Wed Oct  1 06:54:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07664
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 06:54:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4ecK-00088H-UA; Wed, 01 Oct 2003 06:54:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4ebT-00087c-Po
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 06:53:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07632
	for <pana@ietf.org>; Wed, 1 Oct 2003 06:52:58 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ebP-0005aG-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:53:03 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ebO-0005aD-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:53:02 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h91Ar3613074
	for <pana@ietf.org>; Wed, 1 Oct 2003 13:53:03 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T650455153fac158f25446@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 13:53:01 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 13:53:01 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 13:53:00 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D18@esebe008.ntc.nokia.com>
Thread-Topic: [issue34] Behaviour with NAP and ISP (two EAP authentications).
Thread-Index: AcOICiF4+bE5+/0YR5mF6qHgHuOPswAAAfzw
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 10:53:01.0420 (UTC) FILETIME=[2EE33AC0:01C3880A]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue34] Behaviour with NAP and ISP (two EAP authentications).
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

New submission from Dan Forsberg <dan.forsberg@nokia.com>:

How does Session-Lifetime (or Session-Timeout) realate to NAP and ISP
authentications? When this lifetime expires PaC should probably
reauthenticate to NAP and ISP?=20

Clarification needed into the draft also for the case of session
terminateion. Does PaC or PAA terminate the part of the session that
relates to the ISP or NAP or both.

Would it be simpler to use PANA sessions with one EAP method only,
instead of two serial EAP methods in one session. Or should there be one
master session (NAP) and then subsessions (for ISPs). When the master
session is terminated, the subsessions are also terminated. PaC and PAA
can also terminate subsessions. Reauthentication should happen for all
the sessions because of independent EAP methods.

- Dan


----------
category: Technical
document: draft-ietf-pana-pana-xx.txt
messages: 105
nosy: dforsber
priority: Must Fix
status: No Discussion
title: Behaviour with NAP and ISP (two EAP authentications).
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue34
________________________________________________

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


From exim@www1.ietf.org  Wed Oct  1 06:54:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07679
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 06:54:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4ecN-00088v-M9
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 06:54:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h91As381031298
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 06:54:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4ecN-00088j-Ho
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 06:54:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07649
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 06:53:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ecJ-0005ah-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 06:53:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ecI-0005ae-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 06:53:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4ecK-00088H-UA; Wed, 01 Oct 2003 06:54:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4ebT-00087c-Po
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 06:53:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07632
	for <pana@ietf.org>; Wed, 1 Oct 2003 06:52:58 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ebP-0005aG-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:53:03 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ebO-0005aD-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:53:02 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h91Ar3613074
	for <pana@ietf.org>; Wed, 1 Oct 2003 13:53:03 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T650455153fac158f25446@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 13:53:01 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 13:53:01 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 1 Oct 2003 13:53:00 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D18@esebe008.ntc.nokia.com>
Thread-Topic: [issue34] Behaviour with NAP and ISP (two EAP authentications).
Thread-Index: AcOICiF4+bE5+/0YR5mF6qHgHuOPswAAAfzw
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 10:53:01.0420 (UTC) FILETIME=[2EE33AC0:01C3880A]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue34] Behaviour with NAP and ISP (two EAP authentications).
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

New submission from Dan Forsberg <dan.forsberg@nokia.com>:

How does Session-Lifetime (or Session-Timeout) realate to NAP and ISP
authentications? When this lifetime expires PaC should probably
reauthenticate to NAP and ISP?=20

Clarification needed into the draft also for the case of session
terminateion. Does PaC or PAA terminate the part of the session that
relates to the ISP or NAP or both.

Would it be simpler to use PANA sessions with one EAP method only,
instead of two serial EAP methods in one session. Or should there be one
master session (NAP) and then subsessions (for ISPs). When the master
session is terminated, the subsessions are also terminated. PaC and PAA
can also terminate subsessions. Reauthentication should happen for all
the sessions because of independent EAP methods.

- Dan


----------
category: Technical
document: draft-ietf-pana-pana-xx.txt
messages: 105
nosy: dforsber
priority: Must Fix
status: No Discussion
title: Behaviour with NAP and ISP (two EAP authentications).
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue34
________________________________________________

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



From pana-admin@ietf.org  Wed Oct  1 07:09:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06816
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 06:19:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e4T-0006Vf-MT; Wed, 01 Oct 2003 06:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4e3w-0006V1-MA
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 06:18:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06776
	for <pana@ietf.org>; Wed, 1 Oct 2003 06:18:20 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e3s-0005I1-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:18:24 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4e3s-0005Hx-00
	for pana@ietf.org; Wed, 01 Oct 2003 06:18:24 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h91AIO603314
	for <pana@ietf.org>; Wed, 1 Oct 2003 13:18:24 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65043560f8ac158f21083@esvir01nok.ntc.nokia.com> for <pana@ietf.org>;
 Wed, 1 Oct 2003 13:18:23 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 13:18:24 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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 issues
Date: Wed, 1 Oct 2003 13:18:23 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C586@esebe008.ntc.nokia.com>
Thread-Topic: PANA issues
Thread-Index: AcOH9ouGKoQSL2WoTBC3uPJyAeojqQADHe/g
To: <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 10:18:24.0546 (UTC) FILETIME=[58F96820:01C38805]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

One more comment about the statuses for the issues. There=20
are eight possible status values (all but Rejected and Closed=20
are borrowed from EAP issues=20
[http://www.drizzle.com/~aboba/EAP/eapissues.html]). An issue=20
can have only one of these in any time:

TEXT PROPOSED
   Text has been proposed on the list, and no consensus=20
   has been reached

ACCEPTED
   Text has been proposed, consensus has been reached,=20
   but the fix hasn't been included in a specification yet.

PENDING
   Discussion is on-going, no proposed text has been proposed

NO DISCUSSION
   No discussion has been initiated on this issue.

CLARIFYING TEXT REQUIRED
   The issue can be closed if additional clarifying text is=20
   added to the draft

POSSIBLE REJECT
   Issue will be rejected unless objections occur.

CLOSED
   The issue has been incorporated into the draft or some other
   reason with explanation in the issue body.

REJECTED
   The issue was rejected (no consensus on the list).


The query "Show Open" currently shows all issues that are not=20
CLOSED or REJECTED. The query "Show All" shows REJECTED and CLOSED
issues too. If the issue was CLOSED or REJECTED it should contain
an explanation about the reason for doing this. The default reason=20
for CLOSED issue is that it was incorporated into the draft.

Any comments are welcome.

Br,
- Dan


> -----Original Message-----
> From: ext Dan.Forsberg@nokia.com [mailto:Dan.Forsberg@nokia.com]
> Sent: 01 October, 2003 11:32
> To: pana@ietf.org
> Subject: [Pana] PANA issues
>=20
>=20
> Hi folks,
>=20
> I have created new document types to the PANA issue tracker.=20
> These document types identify the version of the PANA=20
> protocol draft (01, 02, 03 etc.).=20
>=20
> PANA chair Alper Yegin had requested assignments of the=20
> issues. This is now also visible in the PANA issue tracker as=20
> well as the issues that are being resolved currently for the=20
> next version of the draft (document type draft-ietf-pana-pana-01.txt).
>=20
> If issues that are listed with document type=20
> draft-ietf-pana-pana-01.txt are not resolved in the 02 draft,=20
> their document type will be changed either to=20
> draft-ietf-pana-pana-xx.txt of draft-ietf-pana-pana-02.txt.=20
>=20
> Editorial issues are always specific to a certain version of=20
> the draft (i.e. document type draft-ietf-pana-pana-xx.txt is=20
> not possible) and must be resolved in the next version of the draft.
>=20
> I have also taken an approach, where I don't always forward=20
> the PANA issue tracker notification to the pana mailing list=20
> because the text would be duplicated (especially in case of=20
> "text proposed" cases).
>=20
> Any comments are welcome to these policy issues.
>=20
> Br,
> - Dan
> "PANA issue tracker admin"
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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


From pana-admin@ietf.org  Wed Oct  1 08:41:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10198
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 08:41:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4gHu-0005Kf-9k; Wed, 01 Oct 2003 08:41:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4gHb-0005KA-MS
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 08:40:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10179
	for <pana@ietf.org>; Wed, 1 Oct 2003 08:40:35 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4gHa-0006Rf-00
	for pana@ietf.org; Wed, 01 Oct 2003 08:40:42 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4gHZ-0006Rc-00
	for pana@ietf.org; Wed, 01 Oct 2003 08:40:41 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h91Cee625260
	for <pana@ietf.org>; Wed, 1 Oct 2003 15:40:40 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6504b79f51ac158f21083@esvir01nok.ntc.nokia.com>;
 Wed, 1 Oct 2003 15:40:39 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 15:40:40 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] Issue 31
Date: Wed, 1 Oct 2003 15:40:39 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C588@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 31
Thread-Index: AcOHqS486OuM5gT1RBGvG1aJYc992gAbTI9Q
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 12:40:40.0157 (UTC) FILETIME=[389848D0:01C38819]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

This is a good change. AAA sessions are not EAP level. I=20
still think that clarified text is required.

- Dan

> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 01 October, 2003 02:16
> To: pana@ietf.org
> Subject: [Pana] Issue 31
>=20
>=20
> http://danforsberg.info:8080/pana-issues/issue31
>=20
> I think the current text is sufficient... EAP-level exchanges=20
> are always
> initiated by the authenticator/AS by EAP design.
>=20
> On the other hand, I propose we rely on session id instead of=20
> device id in
> order to identify a PaC requesting another round of EAP=20
> authentication.
>=20
> Change from:
>=20
>    When a PaC initiates EAP-based re-authentication, it
>    sends a PANA-PAA-Discovery message to the PAA.  If the PAA already
>    has an established PANA session for the PaC with a device=20
> identifier
>    that matches the one extracted from the MAC header and/or IP header
>    of the PANA-PAA-Discover message, it sends a PANA-Auth-Request
>    message with the session identifier for that PANA session to start
>    an authentication phase.  When the PAA initiates EAP-based re-
>    authentication, it sends a PANA-Auth-Request message with the
>    session identifier for the PaC to enter an authentication phase.
>=20
> To:
>=20
>    When a PaC wants to initiate EAP-based re-authentication, it
>    sends a unicast PANA-PAA-Discovery message to the PAA.=20
> This message MUST
>    contain a Session-Id AVP which is used for identifying the=20
> PANA session
>    on the PAA. If the PAA already has an established PANA=20
> session for the
>    PaC with the matching identifier, it sends a PANA-Auth-Request
>    message containing the same identifier to start an authentication
>    phase. If the PAA cannot recognize the session identifier,=20
> it proceeds
>    with regular authentication by sending back PANA-Start-Request.
>    When the PAA initiates EAP-based re-authentication, it sends a
>    PANA-Auth-Request message containing the session=20
> identifier for the PaC
>    to enter an authentication phase.
>=20
> Comments welcome.
>=20
> Alper
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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


From exim@www1.ietf.org  Wed Oct  1 08:41:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10220
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 08:41:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4gHy-0005M3-KU
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 08:41:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h91Cf6fD020542
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 08:41:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4gHy-0005LF-9w
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 08:41:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10187
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 08:40:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4gHv-0006Ru-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 08:41:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4gHv-0006Rr-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 08:41:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4gHu-0005Kf-9k; Wed, 01 Oct 2003 08:41:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4gHb-0005KA-MS
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 08:40:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10179
	for <pana@ietf.org>; Wed, 1 Oct 2003 08:40:35 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4gHa-0006Rf-00
	for pana@ietf.org; Wed, 01 Oct 2003 08:40:42 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4gHZ-0006Rc-00
	for pana@ietf.org; Wed, 01 Oct 2003 08:40:41 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h91Cee625260
	for <pana@ietf.org>; Wed, 1 Oct 2003 15:40:40 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6504b79f51ac158f21083@esvir01nok.ntc.nokia.com>;
 Wed, 1 Oct 2003 15:40:39 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 15:40:40 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] Issue 31
Date: Wed, 1 Oct 2003 15:40:39 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C588@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 31
Thread-Index: AcOHqS486OuM5gT1RBGvG1aJYc992gAbTI9Q
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 12:40:40.0157 (UTC) FILETIME=[389848D0:01C38819]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

This is a good change. AAA sessions are not EAP level. I=20
still think that clarified text is required.

- Dan

> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 01 October, 2003 02:16
> To: pana@ietf.org
> Subject: [Pana] Issue 31
>=20
>=20
> http://danforsberg.info:8080/pana-issues/issue31
>=20
> I think the current text is sufficient... EAP-level exchanges=20
> are always
> initiated by the authenticator/AS by EAP design.
>=20
> On the other hand, I propose we rely on session id instead of=20
> device id in
> order to identify a PaC requesting another round of EAP=20
> authentication.
>=20
> Change from:
>=20
>    When a PaC initiates EAP-based re-authentication, it
>    sends a PANA-PAA-Discovery message to the PAA.  If the PAA already
>    has an established PANA session for the PaC with a device=20
> identifier
>    that matches the one extracted from the MAC header and/or IP header
>    of the PANA-PAA-Discover message, it sends a PANA-Auth-Request
>    message with the session identifier for that PANA session to start
>    an authentication phase.  When the PAA initiates EAP-based re-
>    authentication, it sends a PANA-Auth-Request message with the
>    session identifier for the PaC to enter an authentication phase.
>=20
> To:
>=20
>    When a PaC wants to initiate EAP-based re-authentication, it
>    sends a unicast PANA-PAA-Discovery message to the PAA.=20
> This message MUST
>    contain a Session-Id AVP which is used for identifying the=20
> PANA session
>    on the PAA. If the PAA already has an established PANA=20
> session for the
>    PaC with the matching identifier, it sends a PANA-Auth-Request
>    message containing the same identifier to start an authentication
>    phase. If the PAA cannot recognize the session identifier,=20
> it proceeds
>    with regular authentication by sending back PANA-Start-Request.
>    When the PAA initiates EAP-based re-authentication, it sends a
>    PANA-Auth-Request message containing the session=20
> identifier for the PaC
>    to enter an authentication phase.
>=20
> Comments welcome.
>=20
> Alper
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-admin@ietf.org  Wed Oct  1 09:04:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10949
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 09:04:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4ge8-0006gd-D8; Wed, 01 Oct 2003 09:04:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4gdA-0006cN-JM
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 09:03:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10924
	for <pana@ietf.org>; Wed, 1 Oct 2003 09:02:51 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4gd9-0006h4-00
	for pana@ietf.org; Wed, 01 Oct 2003 09:02:59 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4gd8-0006h1-00
	for pana@ietf.org; Wed, 01 Oct 2003 09:02:58 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h91D2v621671
	for <pana@ietf.org>; Wed, 1 Oct 2003 16:02:57 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6504cc04c0ac158f21083@esvir01nok.ntc.nokia.com>;
 Wed, 1 Oct 2003 16:02:56 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 16:02:56 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] Issue 31
Date: Wed, 1 Oct 2003 16:02:56 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C589@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 31
Thread-Index: AcOHqS486OuM5gT1RBGvG1aJYc992gAbTI9QAADUM1A=
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 13:02:56.0855 (UTC) FILETIME=[55543670:01C3881C]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Text proposal for issue8 includes a statement: "PAA SHOULD initiate=20
EAP authentication before the current session lifetime expires.".

I suggest that we include this also to the section "4.4=20
Re-authentication".

Change to:

   When a PaC wants to initiate EAP-based re-authentication, it sends
   a unicast PANA-PAA-Discovery message to the PAA.  This message MUST
   contain a Session-Id AVP which is used for identifying the PANA
   session on the PAA. If the PAA already has an established PANA
   session for the PaC with the matching identifier, it sends a
   PANA-Auth-Request message containing the same identifier to start
   an authentication phase.  If the PAA can not recognize the session
   identifier, it proceeds with regular authentication by sending back
   PANA-Start-Request.  When the PAA initiates EAP-based
   re-authentication, it sends a PANA-Auth-Request message containing
   the session identifier for the PaC to enter an authentication
   phase. PAA SHOULD initiate EAP authentication before the current
   session lifetime expires.


- Dan

> -----Original Message-----
> From: ext Dan.Forsberg@nokia.com [mailto:Dan.Forsberg@nokia.com]
> Sent: 01 October, 2003 15:41
> To: alper@docomolabs-usa.com; pana@ietf.org
> Subject: RE: [Pana] Issue 31
>=20
>=20
> This is a good change. AAA sessions are not EAP level. I=20
> still think that clarified text is required.
>=20
> - Dan
>=20
> > -----Original Message-----
> > From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > Sent: 01 October, 2003 02:16
> > To: pana@ietf.org
> > Subject: [Pana] Issue 31
> >=20
> >=20
> > http://danforsberg.info:8080/pana-issues/issue31
> >=20
> > I think the current text is sufficient... EAP-level exchanges=20
> > are always
> > initiated by the authenticator/AS by EAP design.
> >=20
> > On the other hand, I propose we rely on session id instead of=20
> > device id in
> > order to identify a PaC requesting another round of EAP=20
> > authentication.
> >=20
> > Change from:
> >=20
> >    When a PaC initiates EAP-based re-authentication, it
> >    sends a PANA-PAA-Discovery message to the PAA.  If the=20
> PAA already
> >    has an established PANA session for the PaC with a device=20
> > identifier
> >    that matches the one extracted from the MAC header=20
> and/or IP header
> >    of the PANA-PAA-Discover message, it sends a PANA-Auth-Request
> >    message with the session identifier for that PANA=20
> session to start
> >    an authentication phase.  When the PAA initiates EAP-based re-
> >    authentication, it sends a PANA-Auth-Request message with the
> >    session identifier for the PaC to enter an authentication phase.
> >=20
> > To:
> >=20
> >    When a PaC wants to initiate EAP-based re-authentication, it
> >    sends a unicast PANA-PAA-Discovery message to the PAA.=20
> > This message MUST
> >    contain a Session-Id AVP which is used for identifying the=20
> > PANA session
> >    on the PAA. If the PAA already has an established PANA=20
> > session for the
> >    PaC with the matching identifier, it sends a PANA-Auth-Request
> >    message containing the same identifier to start an authentication
> >    phase. If the PAA cannot recognize the session identifier,=20
> > it proceeds
> >    with regular authentication by sending back PANA-Start-Request.
> >    When the PAA initiates EAP-based re-authentication, it sends a
> >    PANA-Auth-Request message containing the session=20
> > identifier for the PaC
> >    to enter an authentication phase.
> >=20
> > Comments welcome.
> >=20
> > Alper
> >=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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


From exim@www1.ietf.org  Wed Oct  1 09:04:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10964
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 09:04:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4geA-0006hD-V0
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 09:04:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h91D42rA025740
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 09:04:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4geA-0006h5-PK
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 09:04:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10937
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 09:03:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ge9-0006hi-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 09:04:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4ge8-0006hf-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 09:04:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4ge8-0006gd-D8; Wed, 01 Oct 2003 09:04:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4gdA-0006cN-JM
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 09:03:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10924
	for <pana@ietf.org>; Wed, 1 Oct 2003 09:02:51 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4gd9-0006h4-00
	for pana@ietf.org; Wed, 01 Oct 2003 09:02:59 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4gd8-0006h1-00
	for pana@ietf.org; Wed, 01 Oct 2003 09:02:58 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h91D2v621671
	for <pana@ietf.org>; Wed, 1 Oct 2003 16:02:57 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6504cc04c0ac158f21083@esvir01nok.ntc.nokia.com>;
 Wed, 1 Oct 2003 16:02:56 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 1 Oct 2003 16:02:56 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] Issue 31
Date: Wed, 1 Oct 2003 16:02:56 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C589@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 31
Thread-Index: AcOHqS486OuM5gT1RBGvG1aJYc992gAbTI9QAADUM1A=
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 01 Oct 2003 13:02:56.0855 (UTC) FILETIME=[55543670:01C3881C]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Text proposal for issue8 includes a statement: "PAA SHOULD initiate=20
EAP authentication before the current session lifetime expires.".

I suggest that we include this also to the section "4.4=20
Re-authentication".

Change to:

   When a PaC wants to initiate EAP-based re-authentication, it sends
   a unicast PANA-PAA-Discovery message to the PAA.  This message MUST
   contain a Session-Id AVP which is used for identifying the PANA
   session on the PAA. If the PAA already has an established PANA
   session for the PaC with the matching identifier, it sends a
   PANA-Auth-Request message containing the same identifier to start
   an authentication phase.  If the PAA can not recognize the session
   identifier, it proceeds with regular authentication by sending back
   PANA-Start-Request.  When the PAA initiates EAP-based
   re-authentication, it sends a PANA-Auth-Request message containing
   the session identifier for the PaC to enter an authentication
   phase. PAA SHOULD initiate EAP authentication before the current
   session lifetime expires.


- Dan

> -----Original Message-----
> From: ext Dan.Forsberg@nokia.com [mailto:Dan.Forsberg@nokia.com]
> Sent: 01 October, 2003 15:41
> To: alper@docomolabs-usa.com; pana@ietf.org
> Subject: RE: [Pana] Issue 31
>=20
>=20
> This is a good change. AAA sessions are not EAP level. I=20
> still think that clarified text is required.
>=20
> - Dan
>=20
> > -----Original Message-----
> > From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > Sent: 01 October, 2003 02:16
> > To: pana@ietf.org
> > Subject: [Pana] Issue 31
> >=20
> >=20
> > http://danforsberg.info:8080/pana-issues/issue31
> >=20
> > I think the current text is sufficient... EAP-level exchanges=20
> > are always
> > initiated by the authenticator/AS by EAP design.
> >=20
> > On the other hand, I propose we rely on session id instead of=20
> > device id in
> > order to identify a PaC requesting another round of EAP=20
> > authentication.
> >=20
> > Change from:
> >=20
> >    When a PaC initiates EAP-based re-authentication, it
> >    sends a PANA-PAA-Discovery message to the PAA.  If the=20
> PAA already
> >    has an established PANA session for the PaC with a device=20
> > identifier
> >    that matches the one extracted from the MAC header=20
> and/or IP header
> >    of the PANA-PAA-Discover message, it sends a PANA-Auth-Request
> >    message with the session identifier for that PANA=20
> session to start
> >    an authentication phase.  When the PAA initiates EAP-based re-
> >    authentication, it sends a PANA-Auth-Request message with the
> >    session identifier for the PaC to enter an authentication phase.
> >=20
> > To:
> >=20
> >    When a PaC wants to initiate EAP-based re-authentication, it
> >    sends a unicast PANA-PAA-Discovery message to the PAA.=20
> > This message MUST
> >    contain a Session-Id AVP which is used for identifying the=20
> > PANA session
> >    on the PAA. If the PAA already has an established PANA=20
> > session for the
> >    PaC with the matching identifier, it sends a PANA-Auth-Request
> >    message containing the same identifier to start an authentication
> >    phase. If the PAA cannot recognize the session identifier,=20
> > it proceeds
> >    with regular authentication by sending back PANA-Start-Request.
> >    When the PAA initiates EAP-based re-authentication, it sends a
> >    PANA-Auth-Request message containing the session=20
> > identifier for the PaC
> >    to enter an authentication phase.
> >=20
> > Comments welcome.
> >=20
> > Alper
> >=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-admin@ietf.org  Wed Oct  1 19:05:43 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09755
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 19:05:43 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4q1m-0002FF-6K; Wed, 01 Oct 2003 19:05:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4q0z-0002EZ-2M
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 19:04:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09681
	for <pana@ietf.org>; Wed, 1 Oct 2003 19:04:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4q0v-0006q4-00
	for pana@ietf.org; Wed, 01 Oct 2003 19:04:09 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4q0v-0006q1-00
	for pana@ietf.org; Wed, 01 Oct 2003 19:04:09 -0400
Date: Wed, 01 Oct 2003 16:03:50 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
Message-ID: <BBA0AB66.99F4%alper@docomolabs-usa.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Agenda items for IETF 58?
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello,

If you would like propose an agenda item for the PANA meeting, please let
the WG chairs know.

- Chairs


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


From exim@www1.ietf.org  Wed Oct  1 19:05:44 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09770
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 19:05:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4q27-0002Ib-67
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 19:05:23 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h91N5Nmp008831
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 19:05:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4q27-0002IM-2Q
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 19:05:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09742
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 19:05:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4q23-0006qz-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 19:05:19 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4q23-0006qw-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 19:05:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4q1m-0002FF-6K; Wed, 01 Oct 2003 19:05:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4q0z-0002EZ-2M
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 19:04:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09681
	for <pana@ietf.org>; Wed, 1 Oct 2003 19:04:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4q0v-0006q4-00
	for pana@ietf.org; Wed, 01 Oct 2003 19:04:09 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4q0v-0006q1-00
	for pana@ietf.org; Wed, 01 Oct 2003 19:04:09 -0400
Date: Wed, 01 Oct 2003 16:03:50 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
Message-ID: <BBA0AB66.99F4%alper@docomolabs-usa.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Agenda items for IETF 58?
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello,

If you would like propose an agenda item for the PANA meeting, please let
the WG chairs know.

- Chairs


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



From pana-admin@ietf.org  Wed Oct  1 20:12:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11508
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 20:12:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4r4b-00063r-U8; Wed, 01 Oct 2003 20:12:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4r43-00063K-TH
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 20:11:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11472
	for <pana@ietf.org>; Wed, 1 Oct 2003 20:11:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4r41-0007Or-00
	for pana@ietf.org; Wed, 01 Oct 2003 20:11:25 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4r41-0007Oo-00
	for pana@ietf.org; Wed, 01 Oct 2003 20:11:25 -0400
Date: Wed, 01 Oct 2003 17:11:08 -0700
Subject: Re: [Pana] [issue20] Retransmission timers and counts
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBA0BB2C.9A02%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6D17@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

This looks good.

Just one comment:

>  The PANA protocol provides retransmissions for messages that do not
>  carry EAP payload AVP.  The messages that need retransmissions are
>  listed below:
> 
>       PANA-PAA-Discover (PDI)
>       PANA-Start-Answer (PSA)
>       PANA-Bind-Request (PBR)
>       PANA-Reauth-Request (PRAR)
>       PANA-Termination-Request (PTR)

Since the PANA-Bind-Request carries EAP success/failure, the first statement
is not correct. Instead we could say:

    The PANA protocol provides retransmissions for all the message exchanges
    except PANA-Auth-Request/Answer. PANA-Auth-Request messages carry EAP
    requests which are retransmitted by the EAP protocol entities when
    needed. The messages that need PANA-level retransmissions are listed
    below:

Alper




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


From exim@www1.ietf.org  Wed Oct  1 20:12:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11523
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 20:12:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4r4h-00065b-66
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 20:12:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h920C7lx023401
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 20:12:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4r4g-00065M-VO
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 20:12:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11483
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 20:11:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4r4e-0007PJ-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 20:12:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4r4e-0007PG-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 20:12:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4r4b-00063r-U8; Wed, 01 Oct 2003 20:12:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4r43-00063K-TH
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 20:11:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11472
	for <pana@ietf.org>; Wed, 1 Oct 2003 20:11:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4r41-0007Or-00
	for pana@ietf.org; Wed, 01 Oct 2003 20:11:25 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4r41-0007Oo-00
	for pana@ietf.org; Wed, 01 Oct 2003 20:11:25 -0400
Date: Wed, 01 Oct 2003 17:11:08 -0700
Subject: Re: [Pana] [issue20] Retransmission timers and counts
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBA0BB2C.9A02%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6D17@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

This looks good.

Just one comment:

>  The PANA protocol provides retransmissions for messages that do not
>  carry EAP payload AVP.  The messages that need retransmissions are
>  listed below:
> 
>       PANA-PAA-Discover (PDI)
>       PANA-Start-Answer (PSA)
>       PANA-Bind-Request (PBR)
>       PANA-Reauth-Request (PRAR)
>       PANA-Termination-Request (PTR)

Since the PANA-Bind-Request carries EAP success/failure, the first statement
is not correct. Instead we could say:

    The PANA protocol provides retransmissions for all the message exchanges
    except PANA-Auth-Request/Answer. PANA-Auth-Request messages carry EAP
    requests which are retransmitted by the EAP protocol entities when
    needed. The messages that need PANA-level retransmissions are listed
    below:

Alper




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



From pana-admin@ietf.org  Wed Oct  1 20:36:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12230
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 20:36:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4rRp-0007UC-Rb; Wed, 01 Oct 2003 20:36:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4rRo-0007Tu-Jt
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 20:36:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12186
	for <pana@ietf.org>; Wed, 1 Oct 2003 20:35:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4rRm-0007cv-00
	for pana@ietf.org; Wed, 01 Oct 2003 20:35:58 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4rRl-0007cs-00
	for pana@ietf.org; Wed, 01 Oct 2003 20:35:57 -0400
Date: Wed, 01 Oct 2003 17:35:37 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBA0C0E9.9A0A%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6D0C@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

>        PANA_UNABLE_TO_DELIVER                  3002
>           Error code from PAA to PaC.  The network was unable to
>           deliver the message.

I presume this would be sent by the PAA when it cannot pass a response from
PaC to the AAA backend? We should clarify...
> 
>        PANA_REALM_NOT_SERVED                   3003
>           Error code from PAA to PaC.  The network doesn't recognize
>           the realm.

We don't have a place where PaC sends the realm information. So, I can't see
where such an error would be returned to the PaC.

> 
>        PANA_TOO_BUSY                           3004
>           Error code from PAA to PaC.  Not enough resources to serve
>           the client.  PaC SHOULD attempt to send this message to
>           alternate PAA.  This error SHOULD NOT be used as an answer
>           to the PANA-PAA-Discover message.

I think PAA should never have to send such a message. I'd say the PAA should
allocate sufficient resources before engaging in a PANA session. After all,
we don't have a session relocation facility, PaC cannot change its PAA in
the middle.

> 9.4.7.4.  Permanent failures
> 
>     Errors that fall within the permanent failures category are used
>     to inform the sender that the message processing failed, and
>     that the sender should not attempt to send the same message
>     again.

I'm not clear on the separation between these permanent failures and the
protocol errors (previous section).

> 
>        PANA_AVP_UNSUPPORTED                    5001
>           Error code from PAA to PaC or from PaC to PAA.  The
>           received message contained an AVP that is not recognized
>           or supported and was marked with the Mandatory bit.  A
>           PANA message with this error MUST contain one or more
>           Failed-AVP AVP containing the AVPs that caused the
>           failure.

I think we also need to define Failed-AVP AVP in the draft.

Alper


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


From exim@www1.ietf.org  Wed Oct  1 20:36:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12245
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 20:36:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4rRs-0007Uq-DW
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 20:36:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h920a45M028812
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 20:36:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4rRs-0007Ud-92
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 20:36:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12198
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 20:35:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4rRp-0007d6-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 20:36:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4rRp-0007d3-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 20:36:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4rRp-0007UC-Rb; Wed, 01 Oct 2003 20:36:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4rRo-0007Tu-Jt
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 20:36:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12186
	for <pana@ietf.org>; Wed, 1 Oct 2003 20:35:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4rRm-0007cv-00
	for pana@ietf.org; Wed, 01 Oct 2003 20:35:58 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4rRl-0007cs-00
	for pana@ietf.org; Wed, 01 Oct 2003 20:35:57 -0400
Date: Wed, 01 Oct 2003 17:35:37 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBA0C0E9.9A0A%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6D0C@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>        PANA_UNABLE_TO_DELIVER                  3002
>           Error code from PAA to PaC.  The network was unable to
>           deliver the message.

I presume this would be sent by the PAA when it cannot pass a response from
PaC to the AAA backend? We should clarify...
> 
>        PANA_REALM_NOT_SERVED                   3003
>           Error code from PAA to PaC.  The network doesn't recognize
>           the realm.

We don't have a place where PaC sends the realm information. So, I can't see
where such an error would be returned to the PaC.

> 
>        PANA_TOO_BUSY                           3004
>           Error code from PAA to PaC.  Not enough resources to serve
>           the client.  PaC SHOULD attempt to send this message to
>           alternate PAA.  This error SHOULD NOT be used as an answer
>           to the PANA-PAA-Discover message.

I think PAA should never have to send such a message. I'd say the PAA should
allocate sufficient resources before engaging in a PANA session. After all,
we don't have a session relocation facility, PaC cannot change its PAA in
the middle.

> 9.4.7.4.  Permanent failures
> 
>     Errors that fall within the permanent failures category are used
>     to inform the sender that the message processing failed, and
>     that the sender should not attempt to send the same message
>     again.

I'm not clear on the separation between these permanent failures and the
protocol errors (previous section).

> 
>        PANA_AVP_UNSUPPORTED                    5001
>           Error code from PAA to PaC or from PaC to PAA.  The
>           received message contained an AVP that is not recognized
>           or supported and was marked with the Mandatory bit.  A
>           PANA message with this error MUST contain one or more
>           Failed-AVP AVP containing the AVPs that caused the
>           failure.

I think we also need to define Failed-AVP AVP in the draft.

Alper


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



From pana-admin@ietf.org  Wed Oct  1 22:31:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15170
	for <pana-archive@lists.ietf.org>; Wed, 1 Oct 2003 22:31:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4tF7-0004J4-Gx; Wed, 01 Oct 2003 22:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4tF4-0004IP-1N
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 22:30:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15148
	for <pana@ietf.org>; Wed, 1 Oct 2003 22:30:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4tF0-0000xY-00
	for pana@ietf.org; Wed, 01 Oct 2003 22:30:54 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4tF0-0000xV-00
	for pana@ietf.org; Wed, 01 Oct 2003 22:30:54 -0400
Date: Wed, 01 Oct 2003 19:30:37 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
Message-ID: <BBA0DBDD.9A25%alper@docomolabs-usa.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Issue 30
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

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

See below for the proposed text for section 4.9. Comments welcome.


4.9 Mobility Handling
 
   If PaC wants to resume an ongoing PANA session after connecting to
   another link in the same access network, it MAY send the unexpired
   PANA session identifier in its PANA-Start-Answer message. In the
   absence of a Session-Id AVP in this message, PAA MUST assume this is a
   fresh session and assign a new session identifier in the first
   PANA-Auth-Request message.
    
   If PAA receives a session identifier in the PANA-Start-Answer message,
   and it is configured to enable fast re-authentication, it SHOULD
   retrieve the PANA SA from the previous PAA of the PaC. The mechanism
   required to determine the previous PAA of the PaC by relying on the PANA
   session identifier is outside the scope of PANA protocol. A possible
   solution is to embed the PAA identifier in the PANA session identifier.
   Furthermore, the mechanism required to retrieve the PANA SA from the
   previous PAA is outside the scope of this protocol. Seamoby Context
   Transfer Protocol [CTP] might be useful for this purpose.
    
   If the PAA is not configured to enable fast re-authentication, or
   can not retrieve the PANA SA, or the PANA SA has expired, the PAA
   MUST send the PANA-Auth-Request message with a new session identifier and
   let the PANA exchange take its usual course. Otherwise, PAA MUST
   continue the PANA session with a PANA-Reauth exchange (rather than
   PANA-Auth exchange which, in most of the times, means full EAP
   authentication). Device ID AVPs MUST be included in this exchange to
   bind the new DIs to the PANA SA.



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


From exim@www1.ietf.org  Wed Oct  1 22:31:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15187
	for <pana-archive@odin.ietf.org>; Wed, 1 Oct 2003 22:31:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4tFE-0004K7-SZ
	for pana-archive@odin.ietf.org; Wed, 01 Oct 2003 22:31:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h922V8vl016613
	for pana-archive@odin.ietf.org; Wed, 1 Oct 2003 22:31:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4tFE-0004Js-O9
	for pana-web-archive@optimus.ietf.org; Wed, 01 Oct 2003 22:31:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15153
	for <pana-web-archive@ietf.org>; Wed, 1 Oct 2003 22:31:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4tFB-0000xh-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 22:31:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4tFB-0000xe-00
	for pana-web-archive@ietf.org; Wed, 01 Oct 2003 22:31:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4tF7-0004J4-Gx; Wed, 01 Oct 2003 22:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4tF4-0004IP-1N
	for pana@optimus.ietf.org; Wed, 01 Oct 2003 22:30:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15148
	for <pana@ietf.org>; Wed, 1 Oct 2003 22:30:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4tF0-0000xY-00
	for pana@ietf.org; Wed, 01 Oct 2003 22:30:54 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4tF0-0000xV-00
	for pana@ietf.org; Wed, 01 Oct 2003 22:30:54 -0400
Date: Wed, 01 Oct 2003 19:30:37 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
Message-ID: <BBA0DBDD.9A25%alper@docomolabs-usa.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Issue 30
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

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

See below for the proposed text for section 4.9. Comments welcome.


4.9 Mobility Handling
 
   If PaC wants to resume an ongoing PANA session after connecting to
   another link in the same access network, it MAY send the unexpired
   PANA session identifier in its PANA-Start-Answer message. In the
   absence of a Session-Id AVP in this message, PAA MUST assume this is a
   fresh session and assign a new session identifier in the first
   PANA-Auth-Request message.
    
   If PAA receives a session identifier in the PANA-Start-Answer message,
   and it is configured to enable fast re-authentication, it SHOULD
   retrieve the PANA SA from the previous PAA of the PaC. The mechanism
   required to determine the previous PAA of the PaC by relying on the PANA
   session identifier is outside the scope of PANA protocol. A possible
   solution is to embed the PAA identifier in the PANA session identifier.
   Furthermore, the mechanism required to retrieve the PANA SA from the
   previous PAA is outside the scope of this protocol. Seamoby Context
   Transfer Protocol [CTP] might be useful for this purpose.
    
   If the PAA is not configured to enable fast re-authentication, or
   can not retrieve the PANA SA, or the PANA SA has expired, the PAA
   MUST send the PANA-Auth-Request message with a new session identifier and
   let the PANA exchange take its usual course. Otherwise, PAA MUST
   continue the PANA session with a PANA-Reauth exchange (rather than
   PANA-Auth exchange which, in most of the times, means full EAP
   authentication). Device ID AVPs MUST be included in this exchange to
   bind the new DIs to the PANA SA.



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



From pana-admin@ietf.org  Thu Oct  2 03:19:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05771
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 03:19:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xjp-0003Kj-UF; Thu, 02 Oct 2003 03:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xjY-0003Hq-9M
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 03:18:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05751
	for <pana@ietf.org>; Thu, 2 Oct 2003 03:18:35 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xjV-0003zJ-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:18:42 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xjG-0003z4-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:18:41 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h927Hot18816
	for <pana@ietf.org>; Thu, 2 Oct 2003 10:17:50 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6508b66dd4ac158f24077@esvir04nok.ntc.nokia.com>;
 Thu, 2 Oct 2003 10:17:50 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 10:17:49 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue19] Result-Code AVP values?
Date: Thu, 2 Oct 2003 10:17:48 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C58A@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOIfTGjAcKajXQbSQWiddEvhI//QwANJ5qA
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 07:17:49.0091 (UTC) FILETIME=[48F3EF30:01C388B5]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 02 October, 2003 03:36
> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>=20
> >        PANA_UNABLE_TO_DELIVER                  3002
> >           Error code from PAA to PaC.  The network was unable to
> >           deliver the message.
>=20
> I presume this would be sent by the PAA when it cannot pass a=20
> response from
> PaC to the AAA backend? We should clarify...

Yes. How about this:

   PANA_UNABLE_TO_DELIVER                  3002
      Error code from PAA to PaC.  PAA was unable to deliver
      the EAP payload to the authentication server.


> >=20
> >        PANA_REALM_NOT_SERVED                   3003
> >           Error code from PAA to PaC.  The network doesn't recognize
> >           the realm.
>=20
> We don't have a place where PaC sends the realm information.=20
> So, I can't see
> where such an error would be returned to the PaC.

The EAP-Response/Identity contains the realm if it is required. Or
should we create a NAI AVP, that contains only the realm? Realm is
needed to route the packet to the right AAA backend. If PAA
functionality doesn't check the realm, NAS or for example the local
AAA proxy will do it. But in the case of unknown realm the client
should be notified.

>=20
> >=20
> >        PANA_TOO_BUSY                           3004
> >           Error code from PAA to PaC.  Not enough resources to serve
> >           the client.  PaC SHOULD attempt to send this message to
> >           alternate PAA.  This error SHOULD NOT be used as an answer
> >           to the PANA-PAA-Discover message.
>=20
> I think PAA should never have to send such a message. I'd say=20
> the PAA should
> allocate sufficient resources before engaging in a PANA=20
> session. After all,
> we don't have a session relocation facility, PaC cannot=20
> change its PAA in
> the middle.

Ok. I'll remove this one.

>=20
> > 9.4.7.4.  Permanent failures
> >=20
> >     Errors that fall within the permanent failures category are used
> >     to inform the sender that the message processing failed, and
> >     that the sender should not attempt to send the same message
> >     again.
>=20
> I'm not clear on the separation between these permanent=20
> failures and the
> protocol errors (previous section).

Ok. I'll remove this separation.

>=20
> >=20
> >        PANA_AVP_UNSUPPORTED                    5001
> >           Error code from PAA to PaC or from PaC to PAA.  The
> >           received message contained an AVP that is not recognized
> >           or supported and was marked with the Mandatory bit.  A
> >           PANA message with this error MUST contain one or more
> >           Failed-AVP AVP containing the AVPs that caused the
> >           failure.
>=20
> I think we also need to define Failed-AVP AVP in the draft.

Yep. I'll attach this to the error handling issue17.

- Dan

>=20
> Alper
>=20


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


From exim@www1.ietf.org  Thu Oct  2 03:19:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05789
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 03:19:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xjw-0003LQ-2p
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 03:19:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h927J80O012853
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 03:19:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xjv-0003LE-32
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 03:19:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05757
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 03:18:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xjs-0003zW-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 03:19:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xjs-0003zT-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 03:19:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xjp-0003Kj-UF; Thu, 02 Oct 2003 03:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xjY-0003Hq-9M
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 03:18:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05751
	for <pana@ietf.org>; Thu, 2 Oct 2003 03:18:35 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xjV-0003zJ-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:18:42 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xjG-0003z4-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:18:41 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h927Hot18816
	for <pana@ietf.org>; Thu, 2 Oct 2003 10:17:50 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6508b66dd4ac158f24077@esvir04nok.ntc.nokia.com>;
 Thu, 2 Oct 2003 10:17:50 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 10:17:49 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue19] Result-Code AVP values?
Date: Thu, 2 Oct 2003 10:17:48 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C58A@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOIfTGjAcKajXQbSQWiddEvhI//QwANJ5qA
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 07:17:49.0091 (UTC) FILETIME=[48F3EF30:01C388B5]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 02 October, 2003 03:36
> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>=20
> >        PANA_UNABLE_TO_DELIVER                  3002
> >           Error code from PAA to PaC.  The network was unable to
> >           deliver the message.
>=20
> I presume this would be sent by the PAA when it cannot pass a=20
> response from
> PaC to the AAA backend? We should clarify...

Yes. How about this:

   PANA_UNABLE_TO_DELIVER                  3002
      Error code from PAA to PaC.  PAA was unable to deliver
      the EAP payload to the authentication server.


> >=20
> >        PANA_REALM_NOT_SERVED                   3003
> >           Error code from PAA to PaC.  The network doesn't recognize
> >           the realm.
>=20
> We don't have a place where PaC sends the realm information.=20
> So, I can't see
> where such an error would be returned to the PaC.

The EAP-Response/Identity contains the realm if it is required. Or
should we create a NAI AVP, that contains only the realm? Realm is
needed to route the packet to the right AAA backend. If PAA
functionality doesn't check the realm, NAS or for example the local
AAA proxy will do it. But in the case of unknown realm the client
should be notified.

>=20
> >=20
> >        PANA_TOO_BUSY                           3004
> >           Error code from PAA to PaC.  Not enough resources to serve
> >           the client.  PaC SHOULD attempt to send this message to
> >           alternate PAA.  This error SHOULD NOT be used as an answer
> >           to the PANA-PAA-Discover message.
>=20
> I think PAA should never have to send such a message. I'd say=20
> the PAA should
> allocate sufficient resources before engaging in a PANA=20
> session. After all,
> we don't have a session relocation facility, PaC cannot=20
> change its PAA in
> the middle.

Ok. I'll remove this one.

>=20
> > 9.4.7.4.  Permanent failures
> >=20
> >     Errors that fall within the permanent failures category are used
> >     to inform the sender that the message processing failed, and
> >     that the sender should not attempt to send the same message
> >     again.
>=20
> I'm not clear on the separation between these permanent=20
> failures and the
> protocol errors (previous section).

Ok. I'll remove this separation.

>=20
> >=20
> >        PANA_AVP_UNSUPPORTED                    5001
> >           Error code from PAA to PaC or from PaC to PAA.  The
> >           received message contained an AVP that is not recognized
> >           or supported and was marked with the Mandatory bit.  A
> >           PANA message with this error MUST contain one or more
> >           Failed-AVP AVP containing the AVPs that caused the
> >           failure.
>=20
> I think we also need to define Failed-AVP AVP in the draft.

Yep. I'll attach this to the error handling issue17.

- Dan

>=20
> Alper
>=20


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



From pana-admin@ietf.org  Thu Oct  2 03:20:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05837
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 03:20:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xkn-0003P7-3Z; Thu, 02 Oct 2003 03:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xjx-0003LW-Lf
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 03:19:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05761
	for <pana@ietf.org>; Thu, 2 Oct 2003 03:19:01 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xjv-0003zc-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:19:07 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xju-0003zZ-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:19:06 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h927Io607172
	for <pana@ietf.org>; Thu, 2 Oct 2003 10:19:03 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6508b744a3ac158f25621@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Thu, 2 Oct 2003 10:18:45 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 10:18:45 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 10:18:44 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D21@esebe008.ntc.nokia.com>
Thread-Topic: [issue17] Error handling
Thread-Index: AcOIs9rUTEmdPom4TfCEE2z+cbkSVgAAYgUw
To: <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 07:18:45.0182 (UTC) FILETIME=[6A62BDE0:01C388B5]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue17] Error handling
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

Add new section:

X. Error handling

   PANA-error message MAY be sent by either PaC or PAA when a
   badly formed PANA message is received or in case of other
   errors.  If the cause of this error message was a request
   message (e.g., PANA-PAA-Discover or *-Request), then the
   request MAY be retransmitted immediately without waiting for
   its retransmission timer to go off. If the cause of the
   error was a response message, the receiver of the PANA-error
   SHOULD NOT resend the same response until it receives the
   next request.

   To defend against DoS attacks a timer MAY be used. One (1)
   error notification is sent to each different sender each N
   seconds. N is a configurable parameter.
=20
   When an error message is sent unprotected with MAC AVP and
   the lower-layer is insecure, the error message is treated as
   an informational message.  The receiver of such an error
   message MUST NOT change its state unless the error persists
   and the PANA session is not making any progress.



Add new subsection:

9.3.Y    PANA-Error

   PANA-error is sent either by the PaC or the PAA.

   PANA-Error ::=3D < PANA-Header: 12 >
                   < Session-Id >=20
		   < Result-Code >
                   { Failed-AVP }
                 * [ AVP ]=20
               0*1 < MAC >


Add new subsection:

9.4.Z    Failed-AVP AVP

   The Failed-AVP AVP is defined in [DIAMETER].

________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue17
________________________________________________

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


From exim@www1.ietf.org  Thu Oct  2 03:20:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05852
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 03:20:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xkp-0003RG-IK
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 03:20:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h927K3nb013215
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 03:20:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xkp-0003R4-2P
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 03:20:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05807
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 03:19:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xkm-00040B-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 03:20:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xkm-000408-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 03:20:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xkn-0003P7-3Z; Thu, 02 Oct 2003 03:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xjx-0003LW-Lf
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 03:19:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05761
	for <pana@ietf.org>; Thu, 2 Oct 2003 03:19:01 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xjv-0003zc-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:19:07 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xju-0003zZ-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:19:06 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h927Io607172
	for <pana@ietf.org>; Thu, 2 Oct 2003 10:19:03 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6508b744a3ac158f25621@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Thu, 2 Oct 2003 10:18:45 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 10:18:45 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 10:18:44 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D21@esebe008.ntc.nokia.com>
Thread-Topic: [issue17] Error handling
Thread-Index: AcOIs9rUTEmdPom4TfCEE2z+cbkSVgAAYgUw
To: <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 07:18:45.0182 (UTC) FILETIME=[6A62BDE0:01C388B5]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue17] Error handling
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

Add new section:

X. Error handling

   PANA-error message MAY be sent by either PaC or PAA when a
   badly formed PANA message is received or in case of other
   errors.  If the cause of this error message was a request
   message (e.g., PANA-PAA-Discover or *-Request), then the
   request MAY be retransmitted immediately without waiting for
   its retransmission timer to go off. If the cause of the
   error was a response message, the receiver of the PANA-error
   SHOULD NOT resend the same response until it receives the
   next request.

   To defend against DoS attacks a timer MAY be used. One (1)
   error notification is sent to each different sender each N
   seconds. N is a configurable parameter.
=20
   When an error message is sent unprotected with MAC AVP and
   the lower-layer is insecure, the error message is treated as
   an informational message.  The receiver of such an error
   message MUST NOT change its state unless the error persists
   and the PANA session is not making any progress.



Add new subsection:

9.3.Y    PANA-Error

   PANA-error is sent either by the PaC or the PAA.

   PANA-Error ::=3D < PANA-Header: 12 >
                   < Session-Id >=20
		   < Result-Code >
                   { Failed-AVP }
                 * [ AVP ]=20
               0*1 < MAC >


Add new subsection:

9.4.Z    Failed-AVP AVP

   The Failed-AVP AVP is defined in [DIAMETER].

________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue17
________________________________________________

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



From pana-admin@ietf.org  Thu Oct  2 03:21:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05894
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 03:21:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xln-0003U4-6X; Thu, 02 Oct 2003 03:21:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xlX-0003TN-Gg
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 03:20:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05868
	for <pana@ietf.org>; Thu, 2 Oct 2003 03:20:39 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xlV-000418-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:20:45 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xlU-000415-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:20:44 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h927Kit22708
	for <pana@ietf.org>; Thu, 2 Oct 2003 10:20:45 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6508b91102ac158f23077@esvir03nok.nokia.com>;
 Thu, 2 Oct 2003 10:20:43 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 10:20:44 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 10:20:43 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D22@esebe008.ntc.nokia.com>
Thread-Topic: [issue24] AVP alignment
Thread-Index: AcOItFtTf9lbyjrBSCmRLW7EHVrxOgAARPNw
To: <pana@ietf.org>, <yohba@tari.toshiba.com>
X-OriginalArrivalTime: 02 Oct 2003 07:20:44.0545 (UTC) FILETIME=[B1881710:01C388B5]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue24] AVP alignment
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Yoshihiro,

I had this already in my "newest" message format section.

Br,
- Dan


Dan Forsberg <dan.forsberg@nokia.com> added the comment:

Change from:

9.2 AVP Header=20
=20
       0                   1                   2                   3=20
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1=20
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
      |                           AVP Code                            |=20
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
      |   AVP Flags   |                  AVP Length                   |=20
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
      |                         Vendor-Id (opt)                       |=20
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
      |    Data ...=20
      +-+-+-+-+-+-+-+-+=20

Change to:

9.2 AVP Header=20

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

   The fields in the AVP header MUST be sent in network byte order. The
   format of the header is:

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


----------
nosy:  -dforsber, yoshihiro
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue24
________________________________________________

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


From exim@www1.ietf.org  Thu Oct  2 03:21:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05909
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 03:21:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xlq-0003X5-Lb
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 03:21:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h927L6IX013573
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 03:21:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xlq-0003Wq-9H
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 03:21:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05878
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 03:20:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xln-00041X-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 03:21:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xln-00041U-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 03:21:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xln-0003U4-6X; Thu, 02 Oct 2003 03:21:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xlX-0003TN-Gg
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 03:20:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05868
	for <pana@ietf.org>; Thu, 2 Oct 2003 03:20:39 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xlV-000418-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:20:45 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xlU-000415-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:20:44 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h927Kit22708
	for <pana@ietf.org>; Thu, 2 Oct 2003 10:20:45 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6508b91102ac158f23077@esvir03nok.nokia.com>;
 Thu, 2 Oct 2003 10:20:43 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 10:20:44 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 10:20:43 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D22@esebe008.ntc.nokia.com>
Thread-Topic: [issue24] AVP alignment
Thread-Index: AcOItFtTf9lbyjrBSCmRLW7EHVrxOgAARPNw
To: <pana@ietf.org>, <yohba@tari.toshiba.com>
X-OriginalArrivalTime: 02 Oct 2003 07:20:44.0545 (UTC) FILETIME=[B1881710:01C388B5]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue24] AVP alignment
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Yoshihiro,

I had this already in my "newest" message format section.

Br,
- Dan


Dan Forsberg <dan.forsberg@nokia.com> added the comment:

Change from:

9.2 AVP Header=20
=20
       0                   1                   2                   3=20
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1=20
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
      |                           AVP Code                            |=20
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
      |   AVP Flags   |                  AVP Length                   |=20
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
      |                         Vendor-Id (opt)                       |=20
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
      |    Data ...=20
      +-+-+-+-+-+-+-+-+=20

Change to:

9.2 AVP Header=20

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

   The fields in the AVP header MUST be sent in network byte order. The
   format of the header is:

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


----------
nosy:  -dforsber, yoshihiro
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue24
________________________________________________

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



From pana-admin@ietf.org  Thu Oct  2 03:29:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06098
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 03:29:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xtV-0003yt-57; Thu, 02 Oct 2003 03:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xtN-0003yS-9F
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 03:28:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06078
	for <pana@ietf.org>; Thu, 2 Oct 2003 03:28:44 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xtK-00045S-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:28:50 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xtK-00045P-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:28:50 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h927Sot02239
	for <pana@ietf.org>; Thu, 2 Oct 2003 10:28:50 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6508c07ac6ac158f23077@esvir03nok.nokia.com> for <pana@ietf.org>;
 Thu, 2 Oct 2003 10:28:48 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 10:28:50 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 10:28:50 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D23@esebe008.ntc.nokia.com>
Thread-Topic: [issue19] Result-Code AVP values?
Thread-Index: AcOItrrXxGb4WTxXQ+Wccz3kDc6UmgAAAlVQ
To: <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 07:28:50.0415 (UTC) FILETIME=[D321F7F0:01C388B6]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue19] Result-Code AVP values?
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

- Removed error code section separation.
- Removed PANA_TOO_BUSY.
- Clarified PANA_UNABLE_TO_DELIVER.
-------------------------

9.4.7 Result-Code AVP=20
=20
   The Result-Code AVP is defined in [DIAMETER].  Here are Result-Code
   AVP values taken from [DIAMETER] and adapted for PANA.

9.4.7.1.  Authentication Results Codes

   These result code values inform the PaC about the EAP
   authentication method success or failure.

         PANA_SUCCESS                            2001
            The EAP method authentication was succesfull
            (EAP-Success).

         PANA_AUTHENTICATION_REJECTED            4001
            The authentication process for the client failed
            (EAP-Failure).

         PANA_AUTHORIZATION_REJECTED             5003
             A request was received for which the client could not be
             authorized.  This error could occur if the service
             requested is not permitted to the client.

9.4.7.2.  Protocol Error Result Codes
  =20
   Protocol error result code values.

         PANA_MESSAGE_UNSUPPORTED                3001
            Error code from PAA to PaC or from PaC to PAA.  Message
            type not recognized or supported.

         PANA_UNABLE_TO_DELIVER                  3002
            Error code from PAA to PaC.  PAA was unable to deliver the
            EAP payload to the authentication server.

         PANA_REALM_NOT_SERVED                   3003
            Error code from PAA to PaC.  The network doesn't recognize
            the realm.

         PANA_INVALID_HDR_BITS                   3008
            Error code from PAA to PaC or from PaC to PAA.  A message
            was received whose bits in the PANA header were either set
            to an invalid combination, or to a value that is
            inconsistent with the message type's definition.

         PANA_INVALID_AVP_BITS                   3009
            Error code from PAA to PaC or from PaC to PAA.  A message
            was received that included an AVP whose flag bits are set
            to an unrecognized value, or that is inconsistent with the
            AVP's definition.

         PANA_AVP_UNSUPPORTED                    5001
            Error code from PAA to PaC or from PaC to PAA.  The
            received message contained an AVP that is not recognized
            or supported and was marked with the Mandatory bit.  A
            PANA message with this error MUST contain one or more
            Failed-AVP AVP containing the AVPs that caused the
            failure.

         PANA_UNKNOWN_SESSION_ID                 5002
            Error code from PAA to PaC or from PaC to PAA.  The
            message contained an unknown Session-Id.  PAA MUST NOT
            send this error result code value to PaC if PaC sent an
            unknown Session-Id in the PANA-Start-Answer message
            (session resumption).

         PANA_INVALID_AVP_VALUE                  5004
            Error code from PAA to PaC or from PaC to PAA.  The
            message contained an AVP with an invalid value in its data
            portion.  A PANA message indicating this error MUST
            include the offending AVPs within a Failed-AVP AVP.

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

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

         PANA_CONTRADICTING_AVPS                 5007
            Error code from PAA to PaC.  The PAA has detected AVPs in
            the message that contradicted each other, and is not
            willing to provide service to the client.  One or more
            Failed-AVP AVPs MUST be present, containing the AVPs that
            contradicted each other.

         PANA_AVP_NOT_ALLOWED                    5008
            Error code from PAA to PaC or from PaC to PAA.  A message
            was received with an AVP that MUST NOT be present.  The
            Failed-AVP AVP MUST be included and contain a copy of the
            offending AVP.

         PANA_AVP_OCCURS_TOO_MANY_TIMES          5009
            Error code from PAA to PaC or from PaC to PAA.  A message
            was received that included an AVP that appeared more often
            than permitted in the message definition.  The Failed-AVP
            AVP MUST be included and contain a copy of the first
            instance of the offending AVP that exceeded the maximum
            number of occurrences.

         PANA_UNSUPPORTED_VERSION                5011
            Error code from PAA to PaC or from PaC to PAA.  This error
            is returned when a message was received, whose version
            number is unsupported.

         PANA_INVALID_AVP_LENGTH                 5014
            Error code from PAA to PaC or from PaC to PAA.  The
            message contained an AVP with an invalid length.  The
            PANA-Error message indicating this error MUST include the
            offending AVPs within a Failed-AVP AVP.

         PANA_INVALID_MESSAGE_LENGTH             5015
            Error code from PAA to PaC or from PaC to PAA.  This error
            is returned when a message is received with an invalid
            message length.


----------
status: Clarifying Text Required -> Text Proposed
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue19
________________________________________________

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


From exim@www1.ietf.org  Thu Oct  2 03:29:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06113
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 03:29:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xtY-00040e-SX
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 03:29:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h927T45G015406
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 03:29:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xtY-0003zz-HK
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 03:29:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06085
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 03:28:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xtW-00045e-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 03:29:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xtV-00045b-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 03:29:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xtV-0003yt-57; Thu, 02 Oct 2003 03:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4xtN-0003yS-9F
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 03:28:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06078
	for <pana@ietf.org>; Thu, 2 Oct 2003 03:28:44 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xtK-00045S-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:28:50 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4xtK-00045P-00
	for pana@ietf.org; Thu, 02 Oct 2003 03:28:50 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h927Sot02239
	for <pana@ietf.org>; Thu, 2 Oct 2003 10:28:50 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6508c07ac6ac158f23077@esvir03nok.nokia.com> for <pana@ietf.org>;
 Thu, 2 Oct 2003 10:28:48 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 10:28:50 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 10:28:50 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D23@esebe008.ntc.nokia.com>
Thread-Topic: [issue19] Result-Code AVP values?
Thread-Index: AcOItrrXxGb4WTxXQ+Wccz3kDc6UmgAAAlVQ
To: <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 07:28:50.0415 (UTC) FILETIME=[D321F7F0:01C388B6]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue19] Result-Code AVP values?
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

- Removed error code section separation.
- Removed PANA_TOO_BUSY.
- Clarified PANA_UNABLE_TO_DELIVER.
-------------------------

9.4.7 Result-Code AVP=20
=20
   The Result-Code AVP is defined in [DIAMETER].  Here are Result-Code
   AVP values taken from [DIAMETER] and adapted for PANA.

9.4.7.1.  Authentication Results Codes

   These result code values inform the PaC about the EAP
   authentication method success or failure.

         PANA_SUCCESS                            2001
            The EAP method authentication was succesfull
            (EAP-Success).

         PANA_AUTHENTICATION_REJECTED            4001
            The authentication process for the client failed
            (EAP-Failure).

         PANA_AUTHORIZATION_REJECTED             5003
             A request was received for which the client could not be
             authorized.  This error could occur if the service
             requested is not permitted to the client.

9.4.7.2.  Protocol Error Result Codes
  =20
   Protocol error result code values.

         PANA_MESSAGE_UNSUPPORTED                3001
            Error code from PAA to PaC or from PaC to PAA.  Message
            type not recognized or supported.

         PANA_UNABLE_TO_DELIVER                  3002
            Error code from PAA to PaC.  PAA was unable to deliver the
            EAP payload to the authentication server.

         PANA_REALM_NOT_SERVED                   3003
            Error code from PAA to PaC.  The network doesn't recognize
            the realm.

         PANA_INVALID_HDR_BITS                   3008
            Error code from PAA to PaC or from PaC to PAA.  A message
            was received whose bits in the PANA header were either set
            to an invalid combination, or to a value that is
            inconsistent with the message type's definition.

         PANA_INVALID_AVP_BITS                   3009
            Error code from PAA to PaC or from PaC to PAA.  A message
            was received that included an AVP whose flag bits are set
            to an unrecognized value, or that is inconsistent with the
            AVP's definition.

         PANA_AVP_UNSUPPORTED                    5001
            Error code from PAA to PaC or from PaC to PAA.  The
            received message contained an AVP that is not recognized
            or supported and was marked with the Mandatory bit.  A
            PANA message with this error MUST contain one or more
            Failed-AVP AVP containing the AVPs that caused the
            failure.

         PANA_UNKNOWN_SESSION_ID                 5002
            Error code from PAA to PaC or from PaC to PAA.  The
            message contained an unknown Session-Id.  PAA MUST NOT
            send this error result code value to PaC if PaC sent an
            unknown Session-Id in the PANA-Start-Answer message
            (session resumption).

         PANA_INVALID_AVP_VALUE                  5004
            Error code from PAA to PaC or from PaC to PAA.  The
            message contained an AVP with an invalid value in its data
            portion.  A PANA message indicating this error MUST
            include the offending AVPs within a Failed-AVP AVP.

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

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

         PANA_CONTRADICTING_AVPS                 5007
            Error code from PAA to PaC.  The PAA has detected AVPs in
            the message that contradicted each other, and is not
            willing to provide service to the client.  One or more
            Failed-AVP AVPs MUST be present, containing the AVPs that
            contradicted each other.

         PANA_AVP_NOT_ALLOWED                    5008
            Error code from PAA to PaC or from PaC to PAA.  A message
            was received with an AVP that MUST NOT be present.  The
            Failed-AVP AVP MUST be included and contain a copy of the
            offending AVP.

         PANA_AVP_OCCURS_TOO_MANY_TIMES          5009
            Error code from PAA to PaC or from PaC to PAA.  A message
            was received that included an AVP that appeared more often
            than permitted in the message definition.  The Failed-AVP
            AVP MUST be included and contain a copy of the first
            instance of the offending AVP that exceeded the maximum
            number of occurrences.

         PANA_UNSUPPORTED_VERSION                5011
            Error code from PAA to PaC or from PaC to PAA.  This error
            is returned when a message was received, whose version
            number is unsupported.

         PANA_INVALID_AVP_LENGTH                 5014
            Error code from PAA to PaC or from PaC to PAA.  The
            message contained an AVP with an invalid length.  The
            PANA-Error message indicating this error MUST include the
            offending AVPs within a Failed-AVP AVP.

         PANA_INVALID_MESSAGE_LENGTH             5015
            Error code from PAA to PaC or from PaC to PAA.  This error
            is returned when a message is received with an invalid
            message length.


----------
status: Clarifying Text Required -> Text Proposed
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue19
________________________________________________

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



From pana-admin@ietf.org  Thu Oct  2 04:28:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07557
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 04:28:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4yoa-0007Qe-SZ; Thu, 02 Oct 2003 04:28:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4yoX-0007QS-95
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 04:27:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07525
	for <pana@ietf.org>; Thu, 2 Oct 2003 04:27:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4yoU-0004fp-00
	for pana@ietf.org; Thu, 02 Oct 2003 04:27:54 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4yoT-0004fm-00
	for pana@ietf.org; Thu, 02 Oct 2003 04:27:53 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h928RPF1005609;
	Thu, 2 Oct 2003 17:27:47 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h928RPIo019673;
	Thu, 2 Oct 2003 17:27:25 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id TAA19672 ; Thu, 2 Oct 2003 17:27:25 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id RAA00987; Thu, 2 Oct 2003 17:27:14 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id RAA17273; Thu, 2 Oct 2003 17:27:05 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h928R5qT006248;
	Thu, 2 Oct 2003 17:27:05 +0900 (JST)
Received: from steelhead ([159.119.168.68]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HM400D9SFGXX7@tsbpo1.po.toshiba.co.jp>; Thu,
 2 Oct 2003 17:27:04 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A4ylW-0008P2-00; Thu, 02 Oct 2003 01:24:50 -0700
Date: Thu, 02 Oct 2003 01:24:50 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 5
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D10@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: alper@docomolabs-usa.com, pana@ietf.org
Message-id: <20031002082450.GA32046@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, alper@docomolabs-usa.com,
 pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D10@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Wed, Oct 01, 2003 at 11:20:27AM +0300, Dan.Forsberg@nokia.com wrote:
> Since the issue 5 was already closed I created a new issue about this.
> http://danforsberg.info:8080/pana-issues/issue33
> 
> A comment about the Device-Id.
> From section 4.1.7.
> 
>    o When a Device-Id AVP is included, the AVP is valid if the device 
>    identifier type contained in the AVP matches the expected one (this 
>    check is for PAA only) and the device identifier value contained in 
>    the AVP matches the value extracted from the lower-layer 
>    encapsulation header corresponding to the device identifier type 
>    contained in the AVP. 
> 
> Section 4.7. seems to assume that Device-Id carries the PaC's device id in messages from PaC to PAA and PAA's device id in messages from PAA to PaC. 

Yes.

> I think this should be clarified in the draft. I.e. why "this check is for PAA only" is valid?

"this check" means the device idententifier *type* check.  Since PaC
is expected to obey the device identifier type requested by the PAA, I
thought that the request type DI type is always considered as valid by
the PaC.  However, this is not always true since the PaC cannot obey a
device identifier type it does not support.  So both PaC and PAA would
need to check device idententifier type as well as device identifier
value.

So how about this?

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

Yoshihiro Ohba

> 
> Br,
> - Dan
> 
> 
> > -----Original Message-----
> > From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > Sent: 01 October, 2003 03:39
> > To: pana@ietf.org
> > Subject: [Pana] Issue 5
> > 
> > 
> > 
> > New proposed text for section 4.7, for handling issue 5. 
> > Comments welcome...
> > http://danforsberg.info:8080/pana-issues/issue5
> > 
> > 4.7 Device ID Choice
> >     
> >    A PaC SHOULD configure an IP address before PANA if it 
> > can. It might
> >    either have a pre-configured IP address, or have to obtain one via
> >    dynamic methods such as DHCP or stateless address 
> > autoconfiguration.
> >    Dynamic methods may or may not succeed depending on the local
> >    security policy.  In networks where clients have to be authorized
> >    before they are allowed to obtain an IP address, EPs will 
> > detect the
> >    associated activity and PANA protocol will be engaged 
> > before the clients
> >    can configure a valid IP address.
> >    
> >    Either an IP address or a link-layer address should be 
> > used as device
> >    ID at any time. It is assumed that PAA knows the security 
> > mechanisms
> >    being provided or required on the access network (e.g., 
> > based on physical
> >    security, link-layer ciphers enabled before or after PANA, 
> > or IPsec).
> >    When IPsec-based mechanism [PANA-IPSEC] is the choice of 
> > access control,
> >    PAA should provide its IP address as device ID, and expect 
> > the PaC to
> >    provide its IP address in return.  In all other cases, link-layer
> >    addresses can be provided from both sides.
> >     
> >    When IPsec-based access control is used but the PaC is using an
> >    unspecified IP address in the authentication phase, the device ID
> >    reported by the PaC MUST be either 0.0.0.0 or 0::0. This 
> > device ID MUST
> >    be recorded as a temporary one by the PAA until the PaC 
> > obtains a valid
> >    one and informs the PAA. Eventually PaC MUST obtain an IP address,
> >    possibly by relying on the newly-created PANA session 
> > [PANA-DHCP], in
> >    order to gain full access to the network. PaC MUST update 
> > the device
> >    identifier registered on the PAA from unspecified to the 
> > valid IP address
> >    by initiating a PANA-Reauth-Request/PANA-Reauth-Answer exchange in
> >    which the IP address of the PaC is contained in the Device-Id AVP.
> > 
> > References:
> > 
> > [PANA-IPSEC] M. Parthasarathy: "Securing the first hop in 
> > PANA using IPsec,"
> > Internet Draft, Internet Engineering Task Force, May 2003, Work in
> > progress. 
> > 
> > [PANA-DHCP] H. Tschofenig, A. Yegin, D. Forsberg: 
> > "Bootstrapping RFC3118
> > Delayed authentication using PANA," Internet Draft, Internet 
> > Engineering
> > Task Force, June 2003, Work in progress. 
> > 
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> > 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

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


From exim@www1.ietf.org  Thu Oct  2 04:28:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07579
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 04:28:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4yoh-0007RP-Cc
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 04:28:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h928S6TB028599
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 04:28:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4yoe-0007RC-Tb
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 04:28:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07536
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 04:27:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4yob-0004g4-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 04:28:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4yob-0004g1-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 04:28:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4yoa-0007Qe-SZ; Thu, 02 Oct 2003 04:28:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A4yoX-0007QS-95
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 04:27:57 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07525
	for <pana@ietf.org>; Thu, 2 Oct 2003 04:27:48 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4yoU-0004fp-00
	for pana@ietf.org; Thu, 02 Oct 2003 04:27:54 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A4yoT-0004fm-00
	for pana@ietf.org; Thu, 02 Oct 2003 04:27:53 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h928RPF1005609;
	Thu, 2 Oct 2003 17:27:47 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h928RPIo019673;
	Thu, 2 Oct 2003 17:27:25 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id TAA19672 ; Thu, 2 Oct 2003 17:27:25 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id RAA00987; Thu, 2 Oct 2003 17:27:14 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id RAA17273; Thu, 2 Oct 2003 17:27:05 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h928R5qT006248;
	Thu, 2 Oct 2003 17:27:05 +0900 (JST)
Received: from steelhead ([159.119.168.68]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HM400D9SFGXX7@tsbpo1.po.toshiba.co.jp>; Thu,
 2 Oct 2003 17:27:04 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A4ylW-0008P2-00; Thu, 02 Oct 2003 01:24:50 -0700
Date: Thu, 02 Oct 2003 01:24:50 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 5
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D10@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: alper@docomolabs-usa.com, pana@ietf.org
Message-id: <20031002082450.GA32046@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, alper@docomolabs-usa.com,
 pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D10@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Wed, Oct 01, 2003 at 11:20:27AM +0300, Dan.Forsberg@nokia.com wrote:
> Since the issue 5 was already closed I created a new issue about this.
> http://danforsberg.info:8080/pana-issues/issue33
> 
> A comment about the Device-Id.
> From section 4.1.7.
> 
>    o When a Device-Id AVP is included, the AVP is valid if the device 
>    identifier type contained in the AVP matches the expected one (this 
>    check is for PAA only) and the device identifier value contained in 
>    the AVP matches the value extracted from the lower-layer 
>    encapsulation header corresponding to the device identifier type 
>    contained in the AVP. 
> 
> Section 4.7. seems to assume that Device-Id carries the PaC's device id in messages from PaC to PAA and PAA's device id in messages from PAA to PaC. 

Yes.

> I think this should be clarified in the draft. I.e. why "this check is for PAA only" is valid?

"this check" means the device idententifier *type* check.  Since PaC
is expected to obey the device identifier type requested by the PAA, I
thought that the request type DI type is always considered as valid by
the PaC.  However, this is not always true since the PaC cannot obey a
device identifier type it does not support.  So both PaC and PAA would
need to check device idententifier type as well as device identifier
value.

So how about this?

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

Yoshihiro Ohba

> 
> Br,
> - Dan
> 
> 
> > -----Original Message-----
> > From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > Sent: 01 October, 2003 03:39
> > To: pana@ietf.org
> > Subject: [Pana] Issue 5
> > 
> > 
> > 
> > New proposed text for section 4.7, for handling issue 5. 
> > Comments welcome...
> > http://danforsberg.info:8080/pana-issues/issue5
> > 
> > 4.7 Device ID Choice
> >     
> >    A PaC SHOULD configure an IP address before PANA if it 
> > can. It might
> >    either have a pre-configured IP address, or have to obtain one via
> >    dynamic methods such as DHCP or stateless address 
> > autoconfiguration.
> >    Dynamic methods may or may not succeed depending on the local
> >    security policy.  In networks where clients have to be authorized
> >    before they are allowed to obtain an IP address, EPs will 
> > detect the
> >    associated activity and PANA protocol will be engaged 
> > before the clients
> >    can configure a valid IP address.
> >    
> >    Either an IP address or a link-layer address should be 
> > used as device
> >    ID at any time. It is assumed that PAA knows the security 
> > mechanisms
> >    being provided or required on the access network (e.g., 
> > based on physical
> >    security, link-layer ciphers enabled before or after PANA, 
> > or IPsec).
> >    When IPsec-based mechanism [PANA-IPSEC] is the choice of 
> > access control,
> >    PAA should provide its IP address as device ID, and expect 
> > the PaC to
> >    provide its IP address in return.  In all other cases, link-layer
> >    addresses can be provided from both sides.
> >     
> >    When IPsec-based access control is used but the PaC is using an
> >    unspecified IP address in the authentication phase, the device ID
> >    reported by the PaC MUST be either 0.0.0.0 or 0::0. This 
> > device ID MUST
> >    be recorded as a temporary one by the PAA until the PaC 
> > obtains a valid
> >    one and informs the PAA. Eventually PaC MUST obtain an IP address,
> >    possibly by relying on the newly-created PANA session 
> > [PANA-DHCP], in
> >    order to gain full access to the network. PaC MUST update 
> > the device
> >    identifier registered on the PAA from unspecified to the 
> > valid IP address
> >    by initiating a PANA-Reauth-Request/PANA-Reauth-Answer exchange in
> >    which the IP address of the PaC is contained in the Device-Id AVP.
> > 
> > References:
> > 
> > [PANA-IPSEC] M. Parthasarathy: "Securing the first hop in 
> > PANA using IPsec,"
> > Internet Draft, Internet Engineering Task Force, May 2003, Work in
> > progress. 
> > 
> > [PANA-DHCP] H. Tschofenig, A. Yegin, D. Forsberg: 
> > "Bootstrapping RFC3118
> > Delayed authentication using PANA," Internet Draft, Internet 
> > Engineering
> > Task Force, June 2003, Work in progress. 
> > 
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> > 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

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



From pana-admin@ietf.org  Thu Oct  2 06:03:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09944
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 06:03:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50IX-0003qL-9w; Thu, 02 Oct 2003 06:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50Hi-0003op-S2
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 06:02:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09844
	for <pana@ietf.org>; Thu, 2 Oct 2003 06:02:00 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50He-0005WI-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:02:06 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50He-0005WF-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:02:06 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h92A27t03720
	for <pana@ietf.org>; Thu, 2 Oct 2003 13:02:07 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65094cd4dcac158f24077@esvir04nok.ntc.nokia.com>;
 Thu, 2 Oct 2003 13:02:07 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 13:02:06 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] Issue 5
Date: Thu, 2 Oct 2003 13:02:05 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D26@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 5
Thread-Index: AcOIvytPqwe/pMCgTv66SSvqqfsiuQADQDXg
To: <yohba@tari.toshiba.com>
Cc: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 10:02:06.0933 (UTC) FILETIME=[3CAF4050:01C388CC]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Yoshihiro,

This is ok, thank you.

- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 02 October, 2003 11:25
> To: Forsberg Dan (NRC/Helsinki)
> Cc: alper@docomolabs-usa.com; pana@ietf.org
> Subject: Re: [Pana] Issue 5
> 
> 
> On Wed, Oct 01, 2003 at 11:20:27AM +0300, 
> Dan.Forsberg@nokia.com wrote:
> > Since the issue 5 was already closed I created a new issue 
> about this.
> > http://danforsberg.info:8080/pana-issues/issue33
> > 
> > A comment about the Device-Id.
> > From section 4.1.7.
> > 
> >    o When a Device-Id AVP is included, the AVP is valid if 
> the device 
> >    identifier type contained in the AVP matches the 
> expected one (this 
> >    check is for PAA only) and the device identifier value 
> contained in 
> >    the AVP matches the value extracted from the lower-layer 
> >    encapsulation header corresponding to the device identifier type 
> >    contained in the AVP. 
> > 
> > Section 4.7. seems to assume that Device-Id carries the 
> PaC's device id in messages from PaC to PAA and PAA's device 
> id in messages from PAA to PaC. 
> 
> Yes.
> 
> > I think this should be clarified in the draft. I.e. why 
> "this check is for PAA only" is valid?
> 
> "this check" means the device idententifier *type* check.  Since PaC
> is expected to obey the device identifier type requested by the PAA, I
> thought that the request type DI type is always considered as valid by
> the PaC.  However, this is not always true since the PaC cannot obey a
> device identifier type it does not support.  So both PaC and PAA would
> need to check device idententifier type as well as device identifier
> value.
> 
> So how about this?
> 
> "  o When a Device-Id AVP is included, the AVP is valid if the device
>      identifier type contained in the AVP is supported (this check is
>      for both PaC and PAA) and is the requested one (this check is
>      for PAA only) and the device identifier value contained in
>      the AVP matches the value extracted from the lower-layer 
>      encapsulation header corresponding to the device identifier type 
>      contained in the AVP.  Note that a Device-Id AVP carries the
>      PaC's device identifier in messages from PaC to PAA and PAA's
>      device identifier in messages from PAA to PaC."
> 
> Yoshihiro Ohba
> 
> > 
> > Br,
> > - Dan
> > 
> > 
> > > -----Original Message-----
> > > From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > > Sent: 01 October, 2003 03:39
> > > To: pana@ietf.org
> > > Subject: [Pana] Issue 5
> > > 
> > > 
> > > 
> > > New proposed text for section 4.7, for handling issue 5. 
> > > Comments welcome...
> > > http://danforsberg.info:8080/pana-issues/issue5
> > > 
> > > 4.7 Device ID Choice
> > >     
> > >    A PaC SHOULD configure an IP address before PANA if it 
> > > can. It might
> > >    either have a pre-configured IP address, or have to 
> obtain one via
> > >    dynamic methods such as DHCP or stateless address 
> > > autoconfiguration.
> > >    Dynamic methods may or may not succeed depending on the local
> > >    security policy.  In networks where clients have to be 
> authorized
> > >    before they are allowed to obtain an IP address, EPs will 
> > > detect the
> > >    associated activity and PANA protocol will be engaged 
> > > before the clients
> > >    can configure a valid IP address.
> > >    
> > >    Either an IP address or a link-layer address should be 
> > > used as device
> > >    ID at any time. It is assumed that PAA knows the security 
> > > mechanisms
> > >    being provided or required on the access network (e.g., 
> > > based on physical
> > >    security, link-layer ciphers enabled before or after PANA, 
> > > or IPsec).
> > >    When IPsec-based mechanism [PANA-IPSEC] is the choice of 
> > > access control,
> > >    PAA should provide its IP address as device ID, and expect 
> > > the PaC to
> > >    provide its IP address in return.  In all other cases, 
> link-layer
> > >    addresses can be provided from both sides.
> > >     
> > >    When IPsec-based access control is used but the PaC is using an
> > >    unspecified IP address in the authentication phase, 
> the device ID
> > >    reported by the PaC MUST be either 0.0.0.0 or 0::0. This 
> > > device ID MUST
> > >    be recorded as a temporary one by the PAA until the PaC 
> > > obtains a valid
> > >    one and informs the PAA. Eventually PaC MUST obtain an 
> IP address,
> > >    possibly by relying on the newly-created PANA session 
> > > [PANA-DHCP], in
> > >    order to gain full access to the network. PaC MUST update 
> > > the device
> > >    identifier registered on the PAA from unspecified to the 
> > > valid IP address
> > >    by initiating a PANA-Reauth-Request/PANA-Reauth-Answer 
> exchange in
> > >    which the IP address of the PaC is contained in the 
> Device-Id AVP.
> > > 
> > > References:
> > > 
> > > [PANA-IPSEC] M. Parthasarathy: "Securing the first hop in 
> > > PANA using IPsec,"
> > > Internet Draft, Internet Engineering Task Force, May 2003, Work in
> > > progress. 
> > > 
> > > [PANA-DHCP] H. Tschofenig, A. Yegin, D. Forsberg: 
> > > "Bootstrapping RFC3118
> > > Delayed authentication using PANA," Internet Draft, Internet 
> > > Engineering
> > > Task Force, June 2003, Work in progress. 
> > > 
> > > 
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > > 
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 

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


From exim@www1.ietf.org  Thu Oct  2 06:03:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09959
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 06:03:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50Ia-0003rd-FW
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 06:03:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h92A34SW014853
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 06:03:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50Ia-0003rU-B1
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 06:03:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09932
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 06:02:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50IW-0005XT-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 06:03:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50IW-0005XQ-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 06:03:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50IX-0003qL-9w; Thu, 02 Oct 2003 06:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50Hi-0003op-S2
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 06:02:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09844
	for <pana@ietf.org>; Thu, 2 Oct 2003 06:02:00 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50He-0005WI-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:02:06 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50He-0005WF-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:02:06 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h92A27t03720
	for <pana@ietf.org>; Thu, 2 Oct 2003 13:02:07 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65094cd4dcac158f24077@esvir04nok.ntc.nokia.com>;
 Thu, 2 Oct 2003 13:02:07 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 13:02:06 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] Issue 5
Date: Thu, 2 Oct 2003 13:02:05 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D26@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] Issue 5
Thread-Index: AcOIvytPqwe/pMCgTv66SSvqqfsiuQADQDXg
To: <yohba@tari.toshiba.com>
Cc: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 10:02:06.0933 (UTC) FILETIME=[3CAF4050:01C388CC]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yoshihiro,

This is ok, thank you.

- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 02 October, 2003 11:25
> To: Forsberg Dan (NRC/Helsinki)
> Cc: alper@docomolabs-usa.com; pana@ietf.org
> Subject: Re: [Pana] Issue 5
> 
> 
> On Wed, Oct 01, 2003 at 11:20:27AM +0300, 
> Dan.Forsberg@nokia.com wrote:
> > Since the issue 5 was already closed I created a new issue 
> about this.
> > http://danforsberg.info:8080/pana-issues/issue33
> > 
> > A comment about the Device-Id.
> > From section 4.1.7.
> > 
> >    o When a Device-Id AVP is included, the AVP is valid if 
> the device 
> >    identifier type contained in the AVP matches the 
> expected one (this 
> >    check is for PAA only) and the device identifier value 
> contained in 
> >    the AVP matches the value extracted from the lower-layer 
> >    encapsulation header corresponding to the device identifier type 
> >    contained in the AVP. 
> > 
> > Section 4.7. seems to assume that Device-Id carries the 
> PaC's device id in messages from PaC to PAA and PAA's device 
> id in messages from PAA to PaC. 
> 
> Yes.
> 
> > I think this should be clarified in the draft. I.e. why 
> "this check is for PAA only" is valid?
> 
> "this check" means the device idententifier *type* check.  Since PaC
> is expected to obey the device identifier type requested by the PAA, I
> thought that the request type DI type is always considered as valid by
> the PaC.  However, this is not always true since the PaC cannot obey a
> device identifier type it does not support.  So both PaC and PAA would
> need to check device idententifier type as well as device identifier
> value.
> 
> So how about this?
> 
> "  o When a Device-Id AVP is included, the AVP is valid if the device
>      identifier type contained in the AVP is supported (this check is
>      for both PaC and PAA) and is the requested one (this check is
>      for PAA only) and the device identifier value contained in
>      the AVP matches the value extracted from the lower-layer 
>      encapsulation header corresponding to the device identifier type 
>      contained in the AVP.  Note that a Device-Id AVP carries the
>      PaC's device identifier in messages from PaC to PAA and PAA's
>      device identifier in messages from PAA to PaC."
> 
> Yoshihiro Ohba
> 
> > 
> > Br,
> > - Dan
> > 
> > 
> > > -----Original Message-----
> > > From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > > Sent: 01 October, 2003 03:39
> > > To: pana@ietf.org
> > > Subject: [Pana] Issue 5
> > > 
> > > 
> > > 
> > > New proposed text for section 4.7, for handling issue 5. 
> > > Comments welcome...
> > > http://danforsberg.info:8080/pana-issues/issue5
> > > 
> > > 4.7 Device ID Choice
> > >     
> > >    A PaC SHOULD configure an IP address before PANA if it 
> > > can. It might
> > >    either have a pre-configured IP address, or have to 
> obtain one via
> > >    dynamic methods such as DHCP or stateless address 
> > > autoconfiguration.
> > >    Dynamic methods may or may not succeed depending on the local
> > >    security policy.  In networks where clients have to be 
> authorized
> > >    before they are allowed to obtain an IP address, EPs will 
> > > detect the
> > >    associated activity and PANA protocol will be engaged 
> > > before the clients
> > >    can configure a valid IP address.
> > >    
> > >    Either an IP address or a link-layer address should be 
> > > used as device
> > >    ID at any time. It is assumed that PAA knows the security 
> > > mechanisms
> > >    being provided or required on the access network (e.g., 
> > > based on physical
> > >    security, link-layer ciphers enabled before or after PANA, 
> > > or IPsec).
> > >    When IPsec-based mechanism [PANA-IPSEC] is the choice of 
> > > access control,
> > >    PAA should provide its IP address as device ID, and expect 
> > > the PaC to
> > >    provide its IP address in return.  In all other cases, 
> link-layer
> > >    addresses can be provided from both sides.
> > >     
> > >    When IPsec-based access control is used but the PaC is using an
> > >    unspecified IP address in the authentication phase, 
> the device ID
> > >    reported by the PaC MUST be either 0.0.0.0 or 0::0. This 
> > > device ID MUST
> > >    be recorded as a temporary one by the PAA until the PaC 
> > > obtains a valid
> > >    one and informs the PAA. Eventually PaC MUST obtain an 
> IP address,
> > >    possibly by relying on the newly-created PANA session 
> > > [PANA-DHCP], in
> > >    order to gain full access to the network. PaC MUST update 
> > > the device
> > >    identifier registered on the PAA from unspecified to the 
> > > valid IP address
> > >    by initiating a PANA-Reauth-Request/PANA-Reauth-Answer 
> exchange in
> > >    which the IP address of the PaC is contained in the 
> Device-Id AVP.
> > > 
> > > References:
> > > 
> > > [PANA-IPSEC] M. Parthasarathy: "Securing the first hop in 
> > > PANA using IPsec,"
> > > Internet Draft, Internet Engineering Task Force, May 2003, Work in
> > > progress. 
> > > 
> > > [PANA-DHCP] H. Tschofenig, A. Yegin, D. Forsberg: 
> > > "Bootstrapping RFC3118
> > > Delayed authentication using PANA," Internet Draft, Internet 
> > > Engineering
> > > Task Force, June 2003, Work in progress. 
> > > 
> > > 
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > > 
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 

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



From pana-admin@ietf.org  Thu Oct  2 06:42:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11441
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 06:42:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50uH-0006Tu-6p; Thu, 02 Oct 2003 06:42:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50ti-0006SM-UE
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 06:41:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11416
	for <pana@ietf.org>; Thu, 2 Oct 2003 06:41:15 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50te-0005yv-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:41:22 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50td-0005yr-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:41:22 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h92AfM610006
	for <pana@ietf.org>; Thu, 2 Oct 2003 13:41:22 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T650970bbaaac158f21083@esvir01nok.ntc.nokia.com> for <pana@ietf.org>;
 Thu, 2 Oct 2003 13:41:19 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 13:41:21 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 13:41:20 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D27@esebe008.ntc.nokia.com>
Thread-Topic: [issue26] Editorial comments for draft 01.
Thread-Index: AcOI0ZoXkLpY1cH5S5ex4c/4JFA/gwAABP+w
To: <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 10:41:21.0115 (UTC) FILETIME=[B7E2EAB0:01C388D1]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue26] Editorial comments for draft 01.
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

1) page 8, first phrase.
Change: "...it is considered as valid..."
To: "...it is considered valid..."

4) In page1, end of first paragraph is a typo.=20
Change "...PAA MUST be protected by using."
to: "... PAA MUST be protected by using, e.g., IPsec."

5) page 13 the first two phrases of the second paragraph.
Change:
   When an EAP method that is capable of deriving keys is used during=20
   the authentication phase and the keys are successfully derived all=20
   subsequent PANA messages MUST contain a MAC AVP.  The PANA-Bind-
   Request and the PANA-Bind-Answer message exchange is also used for=20
   binding device identifiers of the PaC and the PAA to the PANA SA. =20

To:
   When an EAP method that is capable of deriving keys is used during=20
   the authentication phase and the keys are successfully derived the=20
   PANA-Bind-Request and PANA-Bind-Answer messages and all subsequent=20
   PANA messages MUST contain a MAC AVP.  The PANA-Bind-Request and the=20
   PANA-Bind-Answer message exchange is also used for binding device=20
   identifiers of the PaC and the PAA to the PANA SA. =20

6) Handled elsewhere. See issue33 (clarifying 4.7).

________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue26
________________________________________________

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


From exim@www1.ietf.org  Thu Oct  2 06:42:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11456
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 06:42:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50uM-0006Uc-7Z
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 06:42:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h92Ag6xb024952
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 06:42:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50uM-0006UN-2s
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 06:42:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11425
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 06:41:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50uH-0005zC-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 06:42:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50uH-0005z5-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 06:42:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50uH-0006Tu-6p; Thu, 02 Oct 2003 06:42:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50ti-0006SM-UE
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 06:41:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11416
	for <pana@ietf.org>; Thu, 2 Oct 2003 06:41:15 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50te-0005yv-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:41:22 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50td-0005yr-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:41:22 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h92AfM610006
	for <pana@ietf.org>; Thu, 2 Oct 2003 13:41:22 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T650970bbaaac158f21083@esvir01nok.ntc.nokia.com> for <pana@ietf.org>;
 Thu, 2 Oct 2003 13:41:19 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 13:41:21 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 13:41:20 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D27@esebe008.ntc.nokia.com>
Thread-Topic: [issue26] Editorial comments for draft 01.
Thread-Index: AcOI0ZoXkLpY1cH5S5ex4c/4JFA/gwAABP+w
To: <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 10:41:21.0115 (UTC) FILETIME=[B7E2EAB0:01C388D1]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue26] Editorial comments for draft 01.
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

1) page 8, first phrase.
Change: "...it is considered as valid..."
To: "...it is considered valid..."

4) In page1, end of first paragraph is a typo.=20
Change "...PAA MUST be protected by using."
to: "... PAA MUST be protected by using, e.g., IPsec."

5) page 13 the first two phrases of the second paragraph.
Change:
   When an EAP method that is capable of deriving keys is used during=20
   the authentication phase and the keys are successfully derived all=20
   subsequent PANA messages MUST contain a MAC AVP.  The PANA-Bind-
   Request and the PANA-Bind-Answer message exchange is also used for=20
   binding device identifiers of the PaC and the PAA to the PANA SA. =20

To:
   When an EAP method that is capable of deriving keys is used during=20
   the authentication phase and the keys are successfully derived the=20
   PANA-Bind-Request and PANA-Bind-Answer messages and all subsequent=20
   PANA messages MUST contain a MAC AVP.  The PANA-Bind-Request and the=20
   PANA-Bind-Answer message exchange is also used for binding device=20
   identifiers of the PaC and the PAA to the PANA SA. =20

6) Handled elsewhere. See issue33 (clarifying 4.7).

________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue26
________________________________________________

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



From pana-admin@ietf.org  Thu Oct  2 06:43:20 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11528
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 06:43:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50vE-0006ZI-PX; Thu, 02 Oct 2003 06:43:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50uO-0006Vp-AU
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 06:42:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11432
	for <pana@ietf.org>; Thu, 2 Oct 2003 06:41:57 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50uK-0005zP-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:42:04 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50uJ-0005zM-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:42:03 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h92Ag4t21086
	for <pana@ietf.org>; Thu, 2 Oct 2003 13:42:04 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T650971604cac158f23077@esvir03nok.nokia.com> for <pana@ietf.org>;
 Thu, 2 Oct 2003 13:42:02 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 13:42:02 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 13:42:02 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D28@esebe008.ntc.nokia.com>
Thread-Topic: [issue33] Clarifying section 4.7
Thread-Index: AcOI0YmUQ1X/ihN9QwKPq6u1eQB99AAADcUA
To: <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 10:42:02.0487 (UTC) FILETIME=[D08BC870:01C388D1]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue33] Clarifying section 4.7
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

Change (from 4.1.7):

    o When a Device-Id AVP is included, the AVP is valid if the device=20
    identifier type contained in the AVP matches the expected one (this=20
    check is for PAA only) and the device identifier value contained in=20
    the AVP matches the value extracted from the lower-layer=20
    encapsulation header corresponding to the device identifier type=20
    contained in the AVP.=20

To (from Yoshihiro Ohba):

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

Updated section 4.7 (s/should/SHOULD/):

4.7 Device ID Choice
   =20
   A PaC SHOULD configure an IP address before PANA if it can. It might
   either have a pre-configured IP address, or have to obtain one via
   dynamic methods such as DHCP or stateless address autoconfiguration.
   Dynamic methods may or may not succeed depending on the local
   security policy.  In networks where clients have to be authorized
   before they are allowed to obtain an IP address, EPs will detect the
   associated activity and PANA protocol will be engaged before the=20
   clients can configure a valid IP address.
  =20
   Either an IP address or a link-layer address SHOULD be used as device
   ID at any time. It is assumed that PAA knows the security mechanisms
   being provided or required on the access network (e.g., based on=20
   physical security, link-layer ciphers enabled before or after PANA, =
or =20
   IPsec). When IPsec-based mechanism [PANA-IPSEC] is the choice of=20
   access control, PAA SHOULD provide its IP address as device ID, and =20
   expect the PaC to provide its IP address in return.  In all other=20
   cases, link-layer addresses can be provided from both sides.
   =20
   When IPsec-based access control is used but the PaC is using an
   unspecified IP address in the authentication phase, the device ID
   reported by the PaC MUST be either 0.0.0.0 or 0::0. This device ID=20
   MUST be recorded as a temporary one by the PAA until the PaC obtains =
a=20
   valid one and informs the PAA. Eventually PaC MUST obtain an IP=20
   address, possibly by relying on the newly-created PANA session=20
   [PANA-DHCP], in order to gain full access to the network. PaC MUST=20
   update the device identifier registered on the PAA from unspecified =
to=20
   the valid IP address by initiating a=20
   PANA-Reauth-Request/PANA-Reauth-Answer exchange in which the IP=20
   address of the PaC is contained in the Device-Id AVP.

________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue33
________________________________________________

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


From exim@www1.ietf.org  Thu Oct  2 06:43:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11543
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 06:43:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50vG-0006cL-15
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 06:43:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h92Ah1c9025431
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 06:43:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50vF-0006c6-Tc
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 06:43:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11489
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 06:42:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50vB-00060J-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 06:42:57 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50vB-00060G-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 06:42:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50vE-0006ZI-PX; Thu, 02 Oct 2003 06:43:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A50uO-0006Vp-AU
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 06:42:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11432
	for <pana@ietf.org>; Thu, 2 Oct 2003 06:41:57 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50uK-0005zP-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:42:04 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A50uJ-0005zM-00
	for pana@ietf.org; Thu, 02 Oct 2003 06:42:03 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h92Ag4t21086
	for <pana@ietf.org>; Thu, 2 Oct 2003 13:42:04 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T650971604cac158f23077@esvir03nok.nokia.com> for <pana@ietf.org>;
 Thu, 2 Oct 2003 13:42:02 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 2 Oct 2003 13:42:02 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Oct 2003 13:42:02 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D28@esebe008.ntc.nokia.com>
Thread-Topic: [issue33] Clarifying section 4.7
Thread-Index: AcOI0YmUQ1X/ihN9QwKPq6u1eQB99AAADcUA
To: <pana@ietf.org>
X-OriginalArrivalTime: 02 Oct 2003 10:42:02.0487 (UTC) FILETIME=[D08BC870:01C388D1]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue33] Clarifying section 4.7
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Dan Forsberg <dan.forsberg@nokia.com> added the comment:

Change (from 4.1.7):

    o When a Device-Id AVP is included, the AVP is valid if the device=20
    identifier type contained in the AVP matches the expected one (this=20
    check is for PAA only) and the device identifier value contained in=20
    the AVP matches the value extracted from the lower-layer=20
    encapsulation header corresponding to the device identifier type=20
    contained in the AVP.=20

To (from Yoshihiro Ohba):

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

Updated section 4.7 (s/should/SHOULD/):

4.7 Device ID Choice
   =20
   A PaC SHOULD configure an IP address before PANA if it can. It might
   either have a pre-configured IP address, or have to obtain one via
   dynamic methods such as DHCP or stateless address autoconfiguration.
   Dynamic methods may or may not succeed depending on the local
   security policy.  In networks where clients have to be authorized
   before they are allowed to obtain an IP address, EPs will detect the
   associated activity and PANA protocol will be engaged before the=20
   clients can configure a valid IP address.
  =20
   Either an IP address or a link-layer address SHOULD be used as device
   ID at any time. It is assumed that PAA knows the security mechanisms
   being provided or required on the access network (e.g., based on=20
   physical security, link-layer ciphers enabled before or after PANA, =
or =20
   IPsec). When IPsec-based mechanism [PANA-IPSEC] is the choice of=20
   access control, PAA SHOULD provide its IP address as device ID, and =20
   expect the PaC to provide its IP address in return.  In all other=20
   cases, link-layer addresses can be provided from both sides.
   =20
   When IPsec-based access control is used but the PaC is using an
   unspecified IP address in the authentication phase, the device ID
   reported by the PaC MUST be either 0.0.0.0 or 0::0. This device ID=20
   MUST be recorded as a temporary one by the PAA until the PaC obtains =
a=20
   valid one and informs the PAA. Eventually PaC MUST obtain an IP=20
   address, possibly by relying on the newly-created PANA session=20
   [PANA-DHCP], in order to gain full access to the network. PaC MUST=20
   update the device identifier registered on the PAA from unspecified =
to=20
   the valid IP address by initiating a=20
   PANA-Reauth-Request/PANA-Reauth-Answer exchange in which the IP=20
   address of the PaC is contained in the Device-Id AVP.

________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue33
________________________________________________

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



From pana-admin@ietf.org  Thu Oct  2 07:06:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12143
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 07:06:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A51HV-0007OC-Va; Thu, 02 Oct 2003 07:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A51HF-0007NV-9d
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 07:05:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12115
	for <pana@ietf.org>; Thu, 2 Oct 2003 07:05:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A51HA-0006GP-00
	for pana@ietf.org; Thu, 02 Oct 2003 07:05:40 -0400
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A51HA-0006GE-00
	for pana@ietf.org; Thu, 02 Oct 2003 07:05:40 -0400
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP
	id BB52B33A84; Thu,  2 Oct 2003 12:58:56 +0200 (CEST)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id E158C3F449; Thu,  2 Oct 2003 13:17:00 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003100212585612537
 ; Thu, 02 Oct 2003 12:58:56 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id 9CE083F449; Thu,  2 Oct 2003 13:17:00 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1A51AN-000Aaf-2R; Thu, 02 Oct 2003 12:58:39 +0200
Date: Thu, 2 Oct 2003 12:58:39 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: pana@ietf.org
Subject: Re: [Pana] Issue 30
Message-ID: <20031002105839.GC38817@ipv6-5.int-evry.fr>
References: <BBA0DBDD.9A25%alper@docomolabs-usa.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BBA0DBDD.9A25%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi all,

On Wed, Oct 01, 2003 at 07:30:37PM -0700, Alper Yegin wrote:
> http://danforsberg.info:8080/pana-issues/issue30
> 
> See below for the proposed text for section 4.9. Comments welcome.
> 
> 
> 4.9 Mobility Handling
>  
>    If PaC wants to resume an ongoing PANA session after connecting to
>    another link in the same access network, it MAY send the unexpired
>    PANA session identifier in its PANA-Start-Answer message. In the
>    absence of a Session-Id AVP in this message, PAA MUST assume this is a
>    fresh session and assign a new session identifier in the first
>    PANA-Auth-Request message.
>     
>    If PAA receives a session identifier in the PANA-Start-Answer message,
>    and it is configured to enable fast re-authentication, it SHOULD
>    retrieve the PANA SA from the previous PAA of the PaC. The mechanism
>    required to determine the previous PAA of the PaC by relying on the PANA
>    session identifier is outside the scope of PANA protocol. A possible
>    solution is to embed the PAA identifier in the PANA session identifier.

I just want to note that if we use this mechanism we need a way to
to change the session-id. Actually at the second handover the third PAA
won't be able to retrieve the second PAA's identity.

-- 
julien.bournelle@int-evry.fr

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


From exim@www1.ietf.org  Thu Oct  2 07:06:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12158
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 07:06:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A51HZ-0007Os-3L
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 07:06:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h92B65Hw028440
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 07:06:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A51HY-0007Od-V9
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 07:06:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12122
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 07:05:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A51HU-0006Gb-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 07:06:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A51HU-0006GY-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 07:06:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A51HV-0007OC-Va; Thu, 02 Oct 2003 07:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A51HF-0007NV-9d
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 07:05:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12115
	for <pana@ietf.org>; Thu, 2 Oct 2003 07:05:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A51HA-0006GP-00
	for pana@ietf.org; Thu, 02 Oct 2003 07:05:40 -0400
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A51HA-0006GE-00
	for pana@ietf.org; Thu, 02 Oct 2003 07:05:40 -0400
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP
	id BB52B33A84; Thu,  2 Oct 2003 12:58:56 +0200 (CEST)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id E158C3F449; Thu,  2 Oct 2003 13:17:00 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003100212585612537
 ; Thu, 02 Oct 2003 12:58:56 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id 9CE083F449; Thu,  2 Oct 2003 13:17:00 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1A51AN-000Aaf-2R; Thu, 02 Oct 2003 12:58:39 +0200
Date: Thu, 2 Oct 2003 12:58:39 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: pana@ietf.org
Subject: Re: [Pana] Issue 30
Message-ID: <20031002105839.GC38817@ipv6-5.int-evry.fr>
References: <BBA0DBDD.9A25%alper@docomolabs-usa.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BBA0DBDD.9A25%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi all,

On Wed, Oct 01, 2003 at 07:30:37PM -0700, Alper Yegin wrote:
> http://danforsberg.info:8080/pana-issues/issue30
> 
> See below for the proposed text for section 4.9. Comments welcome.
> 
> 
> 4.9 Mobility Handling
>  
>    If PaC wants to resume an ongoing PANA session after connecting to
>    another link in the same access network, it MAY send the unexpired
>    PANA session identifier in its PANA-Start-Answer message. In the
>    absence of a Session-Id AVP in this message, PAA MUST assume this is a
>    fresh session and assign a new session identifier in the first
>    PANA-Auth-Request message.
>     
>    If PAA receives a session identifier in the PANA-Start-Answer message,
>    and it is configured to enable fast re-authentication, it SHOULD
>    retrieve the PANA SA from the previous PAA of the PaC. The mechanism
>    required to determine the previous PAA of the PaC by relying on the PANA
>    session identifier is outside the scope of PANA protocol. A possible
>    solution is to embed the PAA identifier in the PANA session identifier.

I just want to note that if we use this mechanism we need a way to
to change the session-id. Actually at the second handover the third PAA
won't be able to retrieve the second PAA's identity.

-- 
julien.bournelle@int-evry.fr

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



From pana-admin@ietf.org  Thu Oct  2 12:05:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28413
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 12:05:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A55wt-0000X3-9a; Thu, 02 Oct 2003 12:05:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A55wV-0000W9-8v
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 12:04:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28367
	for <pana@ietf.org>; Thu, 2 Oct 2003 12:04:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A55wT-0002pw-00
	for pana@ietf.org; Thu, 02 Oct 2003 12:04:37 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A55wQ-0002ph-00
	for pana@ietf.org; Thu, 02 Oct 2003 12:04:36 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h92G4JF1001176;
	Fri, 3 Oct 2003 01:04:19 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h92G4Jvw005100;
	Fri, 3 Oct 2003 01:04:19 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA05099 ; Fri, 3 Oct 2003 01:04:19 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA05896; Fri, 3 Oct 2003 01:04:18 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA18111; Fri, 3 Oct 2003 01:04:17 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h92G4GqT011545;
	Fri, 3 Oct 2003 01:04:16 +0900 (JST)
Received: from steelhead ([159.119.168.171]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HM500I1Q0N2SD@tsbpo1.po.toshiba.co.jp>; Fri,
 3 Oct 2003 01:04:16 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A55vA-0000bE-00; Thu, 02 Oct 2003 09:03:16 -0700
Date: Thu, 02 Oct 2003 09:03:16 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue34] Behaviour with NAP and ISP (two EAP
 authentications).
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D18@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20031002160316.GB677@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D18@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

This is an interesting issue.

Basically there are pros and cons as to whether using a distinct PANA
session for each of two EAP authentication or using a single PANA
session for two EAP authentications.

As you mentioned, using a distinct PANA session for each of NAP and
ISP authentications will make it easier to handle different session
lifetimes for NAP and ISP.  However, there would be the
following cons in this approach:

o Which PANA SA should be used for bootstrapping IPsec and/or DHCP
  authentication?

o What happens if the PANA session from which IPsec and/or DHCP
  authentication are bootstrapped is terminated while the other PANA
  session still remains established.

Especially the latter issue would be more difficult to solve and I
don't recommend this approach.

Using a singel PANA session for both NAP and ISP authentications does
not have above the issues because there is only one PANA SA (and we
already decided to use the MSK of the first successul EAP
authentication with key derivation to derive the PANA SA).  This also
implies that when a PANA session is terminated, both NAP and ISP
authorizations will be removed.  On the other hand, consideration is
needed for this approach to handle different session lifetimes for NAP
and ISP, as you also mentioned below.  One solution to deal with this
is to perform both EAP-based re-authentications for both NAP and ISP
with using the minimum value of the NAP and ISP session lifetimes as
the PANA session lifetime (though this is not efficient when the
difference between the NAP and ISP session lifetimes are large.)

What do you think?

Yoshihiro Ohba



On Wed, Oct 01, 2003 at 01:53:00PM +0300, Dan.Forsberg@nokia.com wrote:
> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> 
> How does Session-Lifetime (or Session-Timeout) realate to NAP and ISP
> authentications? When this lifetime expires PaC should probably
> reauthenticate to NAP and ISP? 
> 
> Clarification needed into the draft also for the case of session
> terminateion. Does PaC or PAA terminate the part of the session that
> relates to the ISP or NAP or both.
> 
> Would it be simpler to use PANA sessions with one EAP method only,
> instead of two serial EAP methods in one session. Or should there be one
> master session (NAP) and then subsessions (for ISPs). When the master
> session is terminated, the subsessions are also terminated. PaC and PAA
> can also terminate subsessions. Reauthentication should happen for all
> the sessions because of independent EAP methods.
> 
> - Dan
> 
> 
> ----------
> category: Technical
> document: draft-ietf-pana-pana-xx.txt
> messages: 105
> nosy: dforsber
> priority: Must Fix
> status: No Discussion
> title: Behaviour with NAP and ISP (two EAP authentications).
> ________________________________________________
> PANA Issues <pana_issues@danforsberg.info>
> http://danforsberg.info:8080/pana-issues/issue34
> ________________________________________________
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Thu Oct  2 12:05:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28467
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 12:05:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A55wz-0000Yz-6R
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 12:05:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h92G59SY002159
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 12:05:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A55wy-0000Yk-TY
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 12:05:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28382
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 12:04:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A55wx-0002qc-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 12:05:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A55ww-0002qZ-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 12:05:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A55wt-0000X3-9a; Thu, 02 Oct 2003 12:05:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A55wV-0000W9-8v
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 12:04:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28367
	for <pana@ietf.org>; Thu, 2 Oct 2003 12:04:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A55wT-0002pw-00
	for pana@ietf.org; Thu, 02 Oct 2003 12:04:37 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A55wQ-0002ph-00
	for pana@ietf.org; Thu, 02 Oct 2003 12:04:36 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h92G4JF1001176;
	Fri, 3 Oct 2003 01:04:19 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h92G4Jvw005100;
	Fri, 3 Oct 2003 01:04:19 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA05099 ; Fri, 3 Oct 2003 01:04:19 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA05896; Fri, 3 Oct 2003 01:04:18 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA18111; Fri, 3 Oct 2003 01:04:17 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h92G4GqT011545;
	Fri, 3 Oct 2003 01:04:16 +0900 (JST)
Received: from steelhead ([159.119.168.171]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HM500I1Q0N2SD@tsbpo1.po.toshiba.co.jp>; Fri,
 3 Oct 2003 01:04:16 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A55vA-0000bE-00; Thu, 02 Oct 2003 09:03:16 -0700
Date: Thu, 02 Oct 2003 09:03:16 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue34] Behaviour with NAP and ISP (two EAP
 authentications).
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D18@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20031002160316.GB677@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D18@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

This is an interesting issue.

Basically there are pros and cons as to whether using a distinct PANA
session for each of two EAP authentication or using a single PANA
session for two EAP authentications.

As you mentioned, using a distinct PANA session for each of NAP and
ISP authentications will make it easier to handle different session
lifetimes for NAP and ISP.  However, there would be the
following cons in this approach:

o Which PANA SA should be used for bootstrapping IPsec and/or DHCP
  authentication?

o What happens if the PANA session from which IPsec and/or DHCP
  authentication are bootstrapped is terminated while the other PANA
  session still remains established.

Especially the latter issue would be more difficult to solve and I
don't recommend this approach.

Using a singel PANA session for both NAP and ISP authentications does
not have above the issues because there is only one PANA SA (and we
already decided to use the MSK of the first successul EAP
authentication with key derivation to derive the PANA SA).  This also
implies that when a PANA session is terminated, both NAP and ISP
authorizations will be removed.  On the other hand, consideration is
needed for this approach to handle different session lifetimes for NAP
and ISP, as you also mentioned below.  One solution to deal with this
is to perform both EAP-based re-authentications for both NAP and ISP
with using the minimum value of the NAP and ISP session lifetimes as
the PANA session lifetime (though this is not efficient when the
difference between the NAP and ISP session lifetimes are large.)

What do you think?

Yoshihiro Ohba



On Wed, Oct 01, 2003 at 01:53:00PM +0300, Dan.Forsberg@nokia.com wrote:
> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> 
> How does Session-Lifetime (or Session-Timeout) realate to NAP and ISP
> authentications? When this lifetime expires PaC should probably
> reauthenticate to NAP and ISP? 
> 
> Clarification needed into the draft also for the case of session
> terminateion. Does PaC or PAA terminate the part of the session that
> relates to the ISP or NAP or both.
> 
> Would it be simpler to use PANA sessions with one EAP method only,
> instead of two serial EAP methods in one session. Or should there be one
> master session (NAP) and then subsessions (for ISPs). When the master
> session is terminated, the subsessions are also terminated. PaC and PAA
> can also terminate subsessions. Reauthentication should happen for all
> the sessions because of independent EAP methods.
> 
> - Dan
> 
> 
> ----------
> category: Technical
> document: draft-ietf-pana-pana-xx.txt
> messages: 105
> nosy: dforsber
> priority: Must Fix
> status: No Discussion
> title: Behaviour with NAP and ISP (two EAP authentications).
> ________________________________________________
> PANA Issues <pana_issues@danforsberg.info>
> http://danforsberg.info:8080/pana-issues/issue34
> ________________________________________________
> 
> _______________________________________________
> 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-admin@ietf.org  Thu Oct  2 12:16:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28968
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 12:16:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A567V-0001Hx-Up; Thu, 02 Oct 2003 12:16:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A566b-0001FE-PH
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 12:15:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28906
	for <pana@ietf.org>; Thu, 2 Oct 2003 12:14:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A566a-00031h-00
	for pana@ietf.org; Thu, 02 Oct 2003 12:15:04 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A566Y-00031c-00
	for pana@ietf.org; Thu, 02 Oct 2003 12:15:03 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h92GF1F1003494
	for <pana@ietf.org>; Fri, 3 Oct 2003 01:15:01 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h92GF1Fi008243
	for <pana@ietf.org>; Fri, 3 Oct 2003 01:15:01 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA08242 ; Fri, 3 Oct 2003 01:15:01 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA08176; Fri, 3 Oct 2003 01:15:01 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA04608; Fri, 3 Oct 2003 01:15:00 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h92GF0qT013411
	for <pana@ietf.org>; Fri, 3 Oct 2003 01:15:00 +0900 (JST)
Received: from steelhead ([159.119.168.171]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HM500I8914YSD@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Fri,
 3 Oct 2003 01:14:59 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A565F-0000cX-00 for <pana@ietf.org>; Thu, 02 Oct 2003 09:13:41 -0700
Date: Thu, 02 Oct 2003 09:13:40 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031002161340.GC677@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.4i
Subject: [Pana] reference missing
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

In the following text in section 9.4.2, I can't find a reference to 
[IPv6-ETHER].  What document it points to?


   The first octet (8 bits) of the Device-Id (Code 1025) AVP data
   contains the device type. Rest of the AVP data payload contains
   the device data.  The content and format of data (including byte
   and bit ordering) is expected to be specified in specific
   documents.  For instance, [IPv6-ETHER].
                                                                                

Yoshihiro Ohba

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


From exim@www1.ietf.org  Thu Oct  2 12:16:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28983
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 12:16:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A567Z-0001Ie-8l
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 12:16:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h92GG5p6004990
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 12:16:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A567Z-0001IP-4A
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 12:16:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28946
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 12:15:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A567X-00032F-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 12:16:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A567X-00032C-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 12:16:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A567V-0001Hx-Up; Thu, 02 Oct 2003 12:16:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A566b-0001FE-PH
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 12:15:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28906
	for <pana@ietf.org>; Thu, 2 Oct 2003 12:14:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A566a-00031h-00
	for pana@ietf.org; Thu, 02 Oct 2003 12:15:04 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A566Y-00031c-00
	for pana@ietf.org; Thu, 02 Oct 2003 12:15:03 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h92GF1F1003494
	for <pana@ietf.org>; Fri, 3 Oct 2003 01:15:01 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h92GF1Fi008243
	for <pana@ietf.org>; Fri, 3 Oct 2003 01:15:01 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA08242 ; Fri, 3 Oct 2003 01:15:01 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA08176; Fri, 3 Oct 2003 01:15:01 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA04608; Fri, 3 Oct 2003 01:15:00 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h92GF0qT013411
	for <pana@ietf.org>; Fri, 3 Oct 2003 01:15:00 +0900 (JST)
Received: from steelhead ([159.119.168.171]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HM500I8914YSD@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Fri,
 3 Oct 2003 01:14:59 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A565F-0000cX-00 for <pana@ietf.org>; Thu, 02 Oct 2003 09:13:41 -0700
Date: Thu, 02 Oct 2003 09:13:40 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031002161340.GC677@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.4i
Subject: [Pana] reference missing
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

In the following text in section 9.4.2, I can't find a reference to 
[IPv6-ETHER].  What document it points to?


   The first octet (8 bits) of the Device-Id (Code 1025) AVP data
   contains the device type. Rest of the AVP data payload contains
   the device data.  The content and format of data (including byte
   and bit ordering) is expected to be specified in specific
   documents.  For instance, [IPv6-ETHER].
                                                                                

Yoshihiro Ohba

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



From pana-admin@ietf.org  Thu Oct  2 13:32:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15064
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 13:32:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A57J2-0005tM-JK; Thu, 02 Oct 2003 13:32:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A57IB-0005oU-FT
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 13:31:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14989
	for <pana@ietf.org>; Thu, 2 Oct 2003 13:30:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57I9-0003rd-00
	for pana@ietf.org; Thu, 02 Oct 2003 13:31:05 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57I8-0003rT-00
	for pana@ietf.org; Thu, 02 Oct 2003 13:31:04 -0400
Date: Thu, 02 Oct 2003 10:30:46 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBA1AED6.9AD1%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA0143C58A@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

>>>        PANA_REALM_NOT_SERVED                   3003
>>>           Error code from PAA to PaC.  The network doesn't recognize
>>>           the realm.
>> 
>> We don't have a place where PaC sends the realm information.
>> So, I can't see
>> where such an error would be returned to the PaC.
> 
> The EAP-Response/Identity contains the realm if it is required. Or
> should we create a NAI AVP, that contains only the realm? Realm is
> needed to route the packet to the right AAA backend. If PAA
> functionality doesn't check the realm, NAS or for example the local
> AAA proxy will do it. But in the case of unknown realm the client
> should be notified.

I should have said "We don't have a place where PaC sends the realm
information in PANA." You are right that EAP client ID can have this, but
than it is the responsibility of EAP or EAP method to deal with this. This
error case should not leak into PANA.

Alper


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


From exim@www1.ietf.org  Thu Oct  2 13:32:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15081
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 13:32:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A57J6-0005uE-Dn
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 13:32:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h92HW43x022696
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 13:32:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A57J6-0005tz-3b
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 13:32:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15035
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 13:31:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57J3-0003s5-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 13:32:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57J3-0003s2-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 13:32:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A57J2-0005tM-JK; Thu, 02 Oct 2003 13:32:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A57IB-0005oU-FT
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 13:31:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14989
	for <pana@ietf.org>; Thu, 2 Oct 2003 13:30:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57I9-0003rd-00
	for pana@ietf.org; Thu, 02 Oct 2003 13:31:05 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A57I8-0003rT-00
	for pana@ietf.org; Thu, 02 Oct 2003 13:31:04 -0400
Date: Thu, 02 Oct 2003 10:30:46 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBA1AED6.9AD1%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA0143C58A@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>>>        PANA_REALM_NOT_SERVED                   3003
>>>           Error code from PAA to PaC.  The network doesn't recognize
>>>           the realm.
>> 
>> We don't have a place where PaC sends the realm information.
>> So, I can't see
>> where such an error would be returned to the PaC.
> 
> The EAP-Response/Identity contains the realm if it is required. Or
> should we create a NAI AVP, that contains only the realm? Realm is
> needed to route the packet to the right AAA backend. If PAA
> functionality doesn't check the realm, NAS or for example the local
> AAA proxy will do it. But in the case of unknown realm the client
> should be notified.

I should have said "We don't have a place where PaC sends the realm
information in PANA." You are right that EAP client ID can have this, but
than it is the responsibility of EAP or EAP method to deal with this. This
error case should not leak into PANA.

Alper


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



From pana-admin@ietf.org  Thu Oct  2 14:29:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18651
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 14:29:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58CC-0001in-Od; Thu, 02 Oct 2003 14:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58Bg-0001iS-Ey
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 14:28:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18613
	for <pana@ietf.org>; Thu, 2 Oct 2003 14:28:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58Bd-0004ue-00
	for pana@ietf.org; Thu, 02 Oct 2003 14:28:25 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58Bd-0004ub-00
	for pana@ietf.org; Thu, 02 Oct 2003 14:28:25 -0400
Date: Thu, 02 Oct 2003 11:28:05 -0700
Subject: Re: [Pana] Issue 30
From: Alper Yegin <alper@docomolabs-usa.com>
To: Julien Bournelle <Julien.Bournelle@int-evry.fr>
CC: <pana@ietf.org>
Message-ID: <BBA1BC45.9ADB%alper@docomolabs-usa.com>
In-Reply-To: <20031002105839.GC38817@ipv6-5.int-evry.fr>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Julien,

> I just want to note that if we use this mechanism we need a way to
> to change the session-id. Actually at the second handover the third PAA
> won't be able to retrieve the second PAA's identity.

Good point. How about if we immediately assign a new session-id on the new
link. Please see below for another revision on the text:

4.9 Mobility Handling
 
   When a PaC wants to resume an ongoing PANA session after connecting to
   another link in the same access network, it MAY send the unexpired
   PANA session identifier in its PANA-Start-Answer message. In the
   absence of a Session-Id AVP in this message, PAA MUST assume this is a
   fresh session and continue its normal execution.
    
   If PAA receives a session identifier in the PANA-Start-Answer message,
   and it is configured to enable fast re-authentication, it SHOULD
   retrieve the PANA session attributes from the previous PAA of the PaC.
   The mechanism required to determine the previous PAA of the PaC by
   relying on the PANA session identifier is outside the scope of PANA
   protocol. A possible solution is to embed the PAA identifier in the PANA
   session identifier. Furthermore, the mechanism required to retrieve the
   session attributes from the previous PAA is outside the scope of this
   protocol. Seamoby Context Transfer Protocol [CTP] might be useful for
   this purpose.
    
   When the PAA is not configured to enable fast re-authentication, or
   can not retrieve the PANA session attributes, or the PANA session has
   already expired (i.e., session lifetime is zero), the PAA MUST send the
   PANA-Auth-Request message with the new session identifier and let the
   PANA exchange take its usual course. This action will engage EAP
   authentication and create a fresh PANA session from scratch.

   In case the new PAA retrieves the on-going PANA session attributes from
   the previous PAA, the PANA session continues with a PANA-Reauth exchange.
   The MAC AVP contained in the PANA-Reauth messages MUST be generated and
   verified by using the retrieved PANA SA attributes. This exchange MUST
   also include Session-Id AVP that contains the newly assigned session
   identifier, and Device-Id AVP. A new PANA session is created upon
   successful completion of this exchange. This session inherits only the
   session lifetime, protection capability, and MSK attributes from the
   previous session. Other attributes are generated based on the PANA
   exchanges on the new link. While MSK stays the same, a new PANA_MAC_Key
   is computed using the new parameters. Subsequent MAC-AVPs are processed
   using this new PANA SA.



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


From exim@www1.ietf.org  Thu Oct  2 14:29:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18666
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 14:29:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58CF-0001jf-Ar
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 14:29:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h92IT3FN006665
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 14:29:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58CF-0001jQ-5a
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 14:29:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18636
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 14:28:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58CC-0004v6-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 14:29:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58CC-0004v3-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 14:29:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58CC-0001in-Od; Thu, 02 Oct 2003 14:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58Bg-0001iS-Ey
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 14:28:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18613
	for <pana@ietf.org>; Thu, 2 Oct 2003 14:28:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58Bd-0004ue-00
	for pana@ietf.org; Thu, 02 Oct 2003 14:28:25 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58Bd-0004ub-00
	for pana@ietf.org; Thu, 02 Oct 2003 14:28:25 -0400
Date: Thu, 02 Oct 2003 11:28:05 -0700
Subject: Re: [Pana] Issue 30
From: Alper Yegin <alper@docomolabs-usa.com>
To: Julien Bournelle <Julien.Bournelle@int-evry.fr>
CC: <pana@ietf.org>
Message-ID: <BBA1BC45.9ADB%alper@docomolabs-usa.com>
In-Reply-To: <20031002105839.GC38817@ipv6-5.int-evry.fr>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Julien,

> I just want to note that if we use this mechanism we need a way to
> to change the session-id. Actually at the second handover the third PAA
> won't be able to retrieve the second PAA's identity.

Good point. How about if we immediately assign a new session-id on the new
link. Please see below for another revision on the text:

4.9 Mobility Handling
 
   When a PaC wants to resume an ongoing PANA session after connecting to
   another link in the same access network, it MAY send the unexpired
   PANA session identifier in its PANA-Start-Answer message. In the
   absence of a Session-Id AVP in this message, PAA MUST assume this is a
   fresh session and continue its normal execution.
    
   If PAA receives a session identifier in the PANA-Start-Answer message,
   and it is configured to enable fast re-authentication, it SHOULD
   retrieve the PANA session attributes from the previous PAA of the PaC.
   The mechanism required to determine the previous PAA of the PaC by
   relying on the PANA session identifier is outside the scope of PANA
   protocol. A possible solution is to embed the PAA identifier in the PANA
   session identifier. Furthermore, the mechanism required to retrieve the
   session attributes from the previous PAA is outside the scope of this
   protocol. Seamoby Context Transfer Protocol [CTP] might be useful for
   this purpose.
    
   When the PAA is not configured to enable fast re-authentication, or
   can not retrieve the PANA session attributes, or the PANA session has
   already expired (i.e., session lifetime is zero), the PAA MUST send the
   PANA-Auth-Request message with the new session identifier and let the
   PANA exchange take its usual course. This action will engage EAP
   authentication and create a fresh PANA session from scratch.

   In case the new PAA retrieves the on-going PANA session attributes from
   the previous PAA, the PANA session continues with a PANA-Reauth exchange.
   The MAC AVP contained in the PANA-Reauth messages MUST be generated and
   verified by using the retrieved PANA SA attributes. This exchange MUST
   also include Session-Id AVP that contains the newly assigned session
   identifier, and Device-Id AVP. A new PANA session is created upon
   successful completion of this exchange. This session inherits only the
   session lifetime, protection capability, and MSK attributes from the
   previous session. Other attributes are generated based on the PANA
   exchanges on the new link. While MSK stays the same, a new PANA_MAC_Key
   is computed using the new parameters. Subsequent MAC-AVPs are processed
   using this new PANA SA.



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



From pana-admin@ietf.org  Thu Oct  2 14:55:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19698
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 14:55:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58bO-0003TJ-07; Thu, 02 Oct 2003 14:55:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58af-0003SO-Hz
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 14:54:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19608
	for <pana@ietf.org>; Thu, 2 Oct 2003 14:54:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58ac-0005Db-00
	for pana@ietf.org; Thu, 02 Oct 2003 14:54:14 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58ab-0005DY-00
	for pana@ietf.org; Thu, 02 Oct 2003 14:54:14 -0400
Date: Thu, 02 Oct 2003 11:53:57 -0700
Subject: Re: [Pana] [issue34] Behaviour with NAP and ISP (two EAP
	authentications).
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <Dan.Forsberg@nokia.com>
CC: <pana@ietf.org>
Message-ID: <BBA1C255.9AE4%alper@docomolabs-usa.com>
In-Reply-To: <20031002160316.GB677@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


This is what we said in the requirements draft:

   Determining the authorization
   parameters as a result of two separate authentications is an
   operational issue and therefore it is outside the scope of PANA.

I think from PANA perspective, it is sufficient to enable two rounds of
authentication. But other than that, we should let the NAS mold NAP and ISP
authentication into a single "PANA session". How exactly this be done should
not be the concern of the base pana protocol. And once there is a session,
neither PAA nor PaC would see "ISP session" or "NAP session", it is just a
"combined session".

Cost (complexity) of separating NAP and ISP authentication beyond what we
already provide seems higher than the benefits, imo.

Alper





> This is an interesting issue.
> 
> Basically there are pros and cons as to whether using a distinct PANA
> session for each of two EAP authentication or using a single PANA
> session for two EAP authentications.
> 
> As you mentioned, using a distinct PANA session for each of NAP and
> ISP authentications will make it easier to handle different session
> lifetimes for NAP and ISP.  However, there would be the
> following cons in this approach:
> 
> o Which PANA SA should be used for bootstrapping IPsec and/or DHCP
> authentication?
> 
> o What happens if the PANA session from which IPsec and/or DHCP
> authentication are bootstrapped is terminated while the other PANA
> session still remains established.
> 
> Especially the latter issue would be more difficult to solve and I
> don't recommend this approach.
> 
> Using a singel PANA session for both NAP and ISP authentications does
> not have above the issues because there is only one PANA SA (and we
> already decided to use the MSK of the first successul EAP
> authentication with key derivation to derive the PANA SA).  This also
> implies that when a PANA session is terminated, both NAP and ISP
> authorizations will be removed.  On the other hand, consideration is
> needed for this approach to handle different session lifetimes for NAP
> and ISP, as you also mentioned below.  One solution to deal with this
> is to perform both EAP-based re-authentications for both NAP and ISP
> with using the minimum value of the NAP and ISP session lifetimes as
> the PANA session lifetime (though this is not efficient when the
> difference between the NAP and ISP session lifetimes are large.)
> 
> What do you think?
> 
> Yoshihiro Ohba
> 
> 
> 
> On Wed, Oct 01, 2003 at 01:53:00PM +0300, Dan.Forsberg@nokia.com wrote:
>> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
>> 
>> How does Session-Lifetime (or Session-Timeout) realate to NAP and ISP
>> authentications? When this lifetime expires PaC should probably
>> reauthenticate to NAP and ISP?
>> 
>> Clarification needed into the draft also for the case of session
>> terminateion. Does PaC or PAA terminate the part of the session that
>> relates to the ISP or NAP or both.
>> 
>> Would it be simpler to use PANA sessions with one EAP method only,
>> instead of two serial EAP methods in one session. Or should there be one
>> master session (NAP) and then subsessions (for ISPs). When the master
>> session is terminated, the subsessions are also terminated. PaC and PAA
>> can also terminate subsessions. Reauthentication should happen for all
>> the sessions because of independent EAP methods.
>> 
>> - Dan
>> 
>> 
>> ----------
>> category: Technical
>> document: draft-ietf-pana-pana-xx.txt
>> messages: 105
>> nosy: dforsber
>> priority: Must Fix
>> status: No Discussion
>> title: Behaviour with NAP and ISP (two EAP authentications).
>> ________________________________________________
>> PANA Issues <pana_issues@danforsberg.info>
>> http://danforsberg.info:8080/pana-issues/issue34
>> ________________________________________________
>> 
>> _______________________________________________
>> Pana mailing list
>> Pana@ietf.org
>> https://www1.ietf.org/mailman/listinfo/pana
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 


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


From exim@www1.ietf.org  Thu Oct  2 14:55:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19728
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 14:55:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58bR-0003a7-TL
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 14:55:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h92It5TD013766
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 14:55:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58bR-0003Zx-PD
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 14:55:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19654
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 14:54:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58bO-0005FC-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 14:55:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58bO-0005F9-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 14:55:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58bO-0003TJ-07; Thu, 02 Oct 2003 14:55:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A58af-0003SO-Hz
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 14:54:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19608
	for <pana@ietf.org>; Thu, 2 Oct 2003 14:54:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58ac-0005Db-00
	for pana@ietf.org; Thu, 02 Oct 2003 14:54:14 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A58ab-0005DY-00
	for pana@ietf.org; Thu, 02 Oct 2003 14:54:14 -0400
Date: Thu, 02 Oct 2003 11:53:57 -0700
Subject: Re: [Pana] [issue34] Behaviour with NAP and ISP (two EAP
	authentications).
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <Dan.Forsberg@nokia.com>
CC: <pana@ietf.org>
Message-ID: <BBA1C255.9AE4%alper@docomolabs-usa.com>
In-Reply-To: <20031002160316.GB677@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


This is what we said in the requirements draft:

   Determining the authorization
   parameters as a result of two separate authentications is an
   operational issue and therefore it is outside the scope of PANA.

I think from PANA perspective, it is sufficient to enable two rounds of
authentication. But other than that, we should let the NAS mold NAP and ISP
authentication into a single "PANA session". How exactly this be done should
not be the concern of the base pana protocol. And once there is a session,
neither PAA nor PaC would see "ISP session" or "NAP session", it is just a
"combined session".

Cost (complexity) of separating NAP and ISP authentication beyond what we
already provide seems higher than the benefits, imo.

Alper





> This is an interesting issue.
> 
> Basically there are pros and cons as to whether using a distinct PANA
> session for each of two EAP authentication or using a single PANA
> session for two EAP authentications.
> 
> As you mentioned, using a distinct PANA session for each of NAP and
> ISP authentications will make it easier to handle different session
> lifetimes for NAP and ISP.  However, there would be the
> following cons in this approach:
> 
> o Which PANA SA should be used for bootstrapping IPsec and/or DHCP
> authentication?
> 
> o What happens if the PANA session from which IPsec and/or DHCP
> authentication are bootstrapped is terminated while the other PANA
> session still remains established.
> 
> Especially the latter issue would be more difficult to solve and I
> don't recommend this approach.
> 
> Using a singel PANA session for both NAP and ISP authentications does
> not have above the issues because there is only one PANA SA (and we
> already decided to use the MSK of the first successul EAP
> authentication with key derivation to derive the PANA SA).  This also
> implies that when a PANA session is terminated, both NAP and ISP
> authorizations will be removed.  On the other hand, consideration is
> needed for this approach to handle different session lifetimes for NAP
> and ISP, as you also mentioned below.  One solution to deal with this
> is to perform both EAP-based re-authentications for both NAP and ISP
> with using the minimum value of the NAP and ISP session lifetimes as
> the PANA session lifetime (though this is not efficient when the
> difference between the NAP and ISP session lifetimes are large.)
> 
> What do you think?
> 
> Yoshihiro Ohba
> 
> 
> 
> On Wed, Oct 01, 2003 at 01:53:00PM +0300, Dan.Forsberg@nokia.com wrote:
>> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
>> 
>> How does Session-Lifetime (or Session-Timeout) realate to NAP and ISP
>> authentications? When this lifetime expires PaC should probably
>> reauthenticate to NAP and ISP?
>> 
>> Clarification needed into the draft also for the case of session
>> terminateion. Does PaC or PAA terminate the part of the session that
>> relates to the ISP or NAP or both.
>> 
>> Would it be simpler to use PANA sessions with one EAP method only,
>> instead of two serial EAP methods in one session. Or should there be one
>> master session (NAP) and then subsessions (for ISPs). When the master
>> session is terminated, the subsessions are also terminated. PaC and PAA
>> can also terminate subsessions. Reauthentication should happen for all
>> the sessions because of independent EAP methods.
>> 
>> - Dan
>> 
>> 
>> ----------
>> category: Technical
>> document: draft-ietf-pana-pana-xx.txt
>> messages: 105
>> nosy: dforsber
>> priority: Must Fix
>> status: No Discussion
>> title: Behaviour with NAP and ISP (two EAP authentications).
>> ________________________________________________
>> PANA Issues <pana_issues@danforsberg.info>
>> http://danforsberg.info:8080/pana-issues/issue34
>> ________________________________________________
>> 
>> _______________________________________________
>> Pana mailing list
>> Pana@ietf.org
>> https://www1.ietf.org/mailman/listinfo/pana
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 


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



From pana-admin@ietf.org  Thu Oct  2 21:28:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03911
	for <pana-archive@lists.ietf.org>; Thu, 2 Oct 2003 21:28:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5Ejh-0006zE-3E; Thu, 02 Oct 2003 21:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5Eiu-0006xb-OW
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 21:27:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03877
	for <pana@ietf.org>; Thu, 2 Oct 2003 21:27:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Eis-0001N7-00
	for pana@ietf.org; Thu, 02 Oct 2003 21:27:10 -0400
Received: from smtp005.mail.ukl.yahoo.com ([217.12.11.36])
	by ietf-mx with smtp (Exim 4.12)
	id 1A5Eir-0001Mf-00
	for pana@ietf.org; Thu, 02 Oct 2003 21:27:09 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp1.mail.vip.ukl.yahoo.com with SMTP; 3 Oct 2003 01:10:52 -0000
Message-ID: <00ba01c3894b$305f4b90$0b100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: <pana@ietf.org>
Date: Thu, 2 Oct 2003 18:10:48 -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.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Subject: [Pana] length of the session ID
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

In the latest PANA-IPSEC draft, i have included PANA session ID to be of 128
bits in length.
I don't see this described in the PANA protocol document. Am i missing it in
the document ?

-mohan


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


From exim@www1.ietf.org  Thu Oct  2 21:28:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03934
	for <pana-archive@odin.ietf.org>; Thu, 2 Oct 2003 21:28:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5Ejk-0006zt-Gk
	for pana-archive@odin.ietf.org; Thu, 02 Oct 2003 21:28:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h931S4Wm026893
	for pana-archive@odin.ietf.org; Thu, 2 Oct 2003 21:28:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5Ejk-0006zg-BW
	for pana-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 21:28:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03902
	for <pana-web-archive@ietf.org>; Thu, 2 Oct 2003 21:27:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Ejh-0001Nc-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 21:28:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Ejh-0001NZ-00
	for pana-web-archive@ietf.org; Thu, 02 Oct 2003 21:28:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5Ejh-0006zE-3E; Thu, 02 Oct 2003 21:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5Eiu-0006xb-OW
	for pana@optimus.ietf.org; Thu, 02 Oct 2003 21:27:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03877
	for <pana@ietf.org>; Thu, 2 Oct 2003 21:27:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Eis-0001N7-00
	for pana@ietf.org; Thu, 02 Oct 2003 21:27:10 -0400
Received: from smtp005.mail.ukl.yahoo.com ([217.12.11.36])
	by ietf-mx with smtp (Exim 4.12)
	id 1A5Eir-0001Mf-00
	for pana@ietf.org; Thu, 02 Oct 2003 21:27:09 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp1.mail.vip.ukl.yahoo.com with SMTP; 3 Oct 2003 01:10:52 -0000
Message-ID: <00ba01c3894b$305f4b90$0b100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: <pana@ietf.org>
Date: Thu, 2 Oct 2003 18:10:48 -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.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Subject: [Pana] length of the session ID
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

In the latest PANA-IPSEC draft, i have included PANA session ID to be of 128
bits in length.
I don't see this described in the PANA protocol document. Am i missing it in
the document ?

-mohan


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



From pana-admin@ietf.org  Fri Oct  3 04:13:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26796
	for <pana-archive@lists.ietf.org>; Fri, 3 Oct 2003 04:13:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5L3d-0002Pp-23; Fri, 03 Oct 2003 04:13:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5L2m-0002Lk-Sh
	for pana@optimus.ietf.org; Fri, 03 Oct 2003 04:12:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26773
	for <pana@ietf.org>; Fri, 3 Oct 2003 04:12:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5L2k-0005K7-00
	for pana@ietf.org; Fri, 03 Oct 2003 04:12:06 -0400
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5L2j-0005Ju-00
	for pana@ietf.org; Fri, 03 Oct 2003 04:12:05 -0400
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP
	id 72A6D34BF9; Fri,  3 Oct 2003 10:09:45 +0200 (CEST)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id ADB96403DC; Fri,  3 Oct 2003 10:28:03 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003100310093909599
 ; Fri, 03 Oct 2003 10:09:39 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id 5BC04403DB; Fri,  3 Oct 2003 10:27:55 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1A5Kzx-000BFT-9r; Fri, 03 Oct 2003 10:09:13 +0200
Date: Fri, 3 Oct 2003 10:09:13 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: pana@ietf.org
Subject: Re: [Pana] length of the session ID
Message-ID: <20031003080913.GT38817@ipv6-5.int-evry.fr>
References: <00ba01c3894b$305f4b90$0b100a0a@adithya>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00ba01c3894b$305f4b90$0b100a0a@adithya>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi,

On Thu, Oct 02, 2003 at 06:10:48PM -0700, Mohan Parthasarathy wrote:
> Hi,
> 
> In the latest PANA-IPSEC draft, i have included PANA session ID to be of 128
> bits in length.
> I don't see this described in the PANA protocol document. Am i missing it in
> the document ?

I guess that the Session-Id doesn't have specific length. Actually, the
PANA draft refers to Diameter (RFC 3588) for the Session-Id AVP
definition.


Hope it helps

-- 
julien.bournelle@int-evry.fr

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


From exim@www1.ietf.org  Fri Oct  3 04:13:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26811
	for <pana-archive@odin.ietf.org>; Fri, 3 Oct 2003 04:13:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5L3j-0002Ra-Td
	for pana-archive@odin.ietf.org; Fri, 03 Oct 2003 04:13:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h938D7eM009373
	for pana-archive@odin.ietf.org; Fri, 3 Oct 2003 04:13:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5L3i-0002Qp-UZ
	for pana-web-archive@optimus.ietf.org; Fri, 03 Oct 2003 04:13:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26786
	for <pana-web-archive@ietf.org>; Fri, 3 Oct 2003 04:12:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5L3g-0005KZ-00
	for pana-web-archive@ietf.org; Fri, 03 Oct 2003 04:13:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5L3f-0005KW-00
	for pana-web-archive@ietf.org; Fri, 03 Oct 2003 04:13:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5L3d-0002Pp-23; Fri, 03 Oct 2003 04:13:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5L2m-0002Lk-Sh
	for pana@optimus.ietf.org; Fri, 03 Oct 2003 04:12:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26773
	for <pana@ietf.org>; Fri, 3 Oct 2003 04:12:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5L2k-0005K7-00
	for pana@ietf.org; Fri, 03 Oct 2003 04:12:06 -0400
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5L2j-0005Ju-00
	for pana@ietf.org; Fri, 03 Oct 2003 04:12:05 -0400
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP
	id 72A6D34BF9; Fri,  3 Oct 2003 10:09:45 +0200 (CEST)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id ADB96403DC; Fri,  3 Oct 2003 10:28:03 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003100310093909599
 ; Fri, 03 Oct 2003 10:09:39 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id 5BC04403DB; Fri,  3 Oct 2003 10:27:55 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1A5Kzx-000BFT-9r; Fri, 03 Oct 2003 10:09:13 +0200
Date: Fri, 3 Oct 2003 10:09:13 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: pana@ietf.org
Subject: Re: [Pana] length of the session ID
Message-ID: <20031003080913.GT38817@ipv6-5.int-evry.fr>
References: <00ba01c3894b$305f4b90$0b100a0a@adithya>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00ba01c3894b$305f4b90$0b100a0a@adithya>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi,

On Thu, Oct 02, 2003 at 06:10:48PM -0700, Mohan Parthasarathy wrote:
> Hi,
> 
> In the latest PANA-IPSEC draft, i have included PANA session ID to be of 128
> bits in length.
> I don't see this described in the PANA protocol document. Am i missing it in
> the document ?

I guess that the Session-Id doesn't have specific length. Actually, the
PANA draft refers to Diameter (RFC 3588) for the Session-Id AVP
definition.


Hope it helps

-- 
julien.bournelle@int-evry.fr

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



From pana-admin@ietf.org  Fri Oct  3 07:31:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01434
	for <pana-archive@lists.ietf.org>; Fri, 3 Oct 2003 07:31:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5O9G-0000jx-C5; Fri, 03 Oct 2003 07:31:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5O8O-0000bD-8U
	for pana@optimus.ietf.org; Fri, 03 Oct 2003 07:30:08 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01280;
	Fri, 3 Oct 2003 07:30:00 -0400 (EDT)
Message-Id: <200310031130.HAA01280@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 03 Oct 2003 07:30:00 -0400
Subject: [Pana] I-D ACTION:draft-ietf-pana-ipsec-00.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: PANA enabling IPsec based Access Control
	Author(s)	: M. Parthasarathy
	Filename	: draft-ietf-pana-ipsec-00.txt
	Pages		: 11
	Date		: 2003-10-2
	
The PANA (Protocol for carrying Authentication for Network Access)  
working group is developing protocol for authenticating clients to  
the access network using IP based protocols.  The PANA protocol  
authenticates the client and also establishes a PANA security  
association between the PANA client and PANA authentication agent at  
the end of a successful authentication. This document discusses the  
details for establishing an IPsec security association using the PANA  
security association for enabling IPsec based access control.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ipsec-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-ietf-pana-ipsec-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.

--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:	<2003-10-2130858.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--



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


From exim@www1.ietf.org  Fri Oct  3 07:31:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01466
	for <pana-archive@odin.ietf.org>; Fri, 3 Oct 2003 07:31:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5O9J-0000lm-VF
	for pana-archive@odin.ietf.org; Fri, 03 Oct 2003 07:31:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h93BV5UE002952
	for pana-archive@odin.ietf.org; Fri, 3 Oct 2003 07:31:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5O9J-0000lW-Qr
	for pana-web-archive@optimus.ietf.org; Fri, 03 Oct 2003 07:31:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01406
	for <pana-web-archive@ietf.org>; Fri, 3 Oct 2003 07:30:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5O9I-00070s-00
	for pana-web-archive@ietf.org; Fri, 03 Oct 2003 07:31:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5O9I-00070l-00
	for pana-web-archive@ietf.org; Fri, 03 Oct 2003 07:31:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5O9G-0000jx-C5; Fri, 03 Oct 2003 07:31:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5O8O-0000bD-8U
	for pana@optimus.ietf.org; Fri, 03 Oct 2003 07:30:08 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01280;
	Fri, 3 Oct 2003 07:30:00 -0400 (EDT)
Message-Id: <200310031130.HAA01280@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Fri, 03 Oct 2003 07:30:00 -0400
Subject: [Pana] I-D ACTION:draft-ietf-pana-ipsec-00.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

--NextPart

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

	Title		: PANA enabling IPsec based Access Control
	Author(s)	: M. Parthasarathy
	Filename	: draft-ietf-pana-ipsec-00.txt
	Pages		: 11
	Date		: 2003-10-2
	
The PANA (Protocol for carrying Authentication for Network Access)  
working group is developing protocol for authenticating clients to  
the access network using IP based protocols.  The PANA protocol  
authenticates the client and also establishes a PANA security  
association between the PANA client and PANA authentication agent at  
the end of a successful authentication. This document discusses the  
details for establishing an IPsec security association using the PANA  
security association for enabling IPsec based access control.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ipsec-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-ietf-pana-ipsec-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.

--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:	<2003-10-2130858.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--



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



From pana-admin@ietf.org  Mon Oct  6 08:26:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27257
	for <pana-archive@lists.ietf.org>; Mon, 6 Oct 2003 08:26:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6UR6-0003CG-S4; Mon, 06 Oct 2003 08:26:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6UQn-0003Bh-CJ
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 08:25:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27193
	for <pana@ietf.org>; Mon, 6 Oct 2003 08:25:32 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6UQm-0004VD-00
	for pana@ietf.org; Mon, 06 Oct 2003 08:25:40 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6UQl-0004Uc-00
	for pana@ietf.org; Mon, 06 Oct 2003 08:25:39 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h96COwt00458
	for <pana@ietf.org>; Mon, 6 Oct 2003 15:25:00 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T651e68f74bac158f24077@esvir04nok.ntc.nokia.com>;
 Mon, 6 Oct 2003 15:24:52 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 6 Oct 2003 15:24:52 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue19] Result-Code AVP values?
Date: Mon, 6 Oct 2003 15:24:51 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D33@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOJCved1yCGadKCQLeQ8zA0HUHHFAC+XFYQ
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 06 Oct 2003 12:24:52.0231 (UTC) FILETIME=[D7A70170:01C38C04]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Ok. So do you want to say that realm based routing is outside=20
the scope of PANA and in error case NAS must inform PaC in some=20
other means than PANA protocol? I don't mind taking this error=20
case away. Anyway, I'm curious of how 802.1X does handle this=20
case?

- Dan

> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 02 October, 2003 20:31
> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>=20
>=20
> >>>        PANA_REALM_NOT_SERVED                   3003
> >>>           Error code from PAA to PaC.  The network=20
> doesn't recognize
> >>>           the realm.
> >>=20
> >> We don't have a place where PaC sends the realm information.
> >> So, I can't see
> >> where such an error would be returned to the PaC.
> >=20
> > The EAP-Response/Identity contains the realm if it is required. Or
> > should we create a NAI AVP, that contains only the realm? Realm is
> > needed to route the packet to the right AAA backend. If PAA
> > functionality doesn't check the realm, NAS or for example the local
> > AAA proxy will do it. But in the case of unknown realm the client
> > should be notified.
>=20
> I should have said "We don't have a place where PaC sends the realm
> information in PANA." You are right that EAP client ID can=20
> have this, but
> than it is the responsibility of EAP or EAP method to deal=20
> with this. This
> error case should not leak into PANA.
>=20
> Alper
>=20
>=20

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


From exim@www1.ietf.org  Mon Oct  6 08:26:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27276
	for <pana-archive@odin.ietf.org>; Mon, 6 Oct 2003 08:26:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6URC-0003DF-00
	for pana-archive@odin.ietf.org; Mon, 06 Oct 2003 08:26:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h96CQ5ak012349
	for pana-archive@odin.ietf.org; Mon, 6 Oct 2003 08:26:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6URA-0003D6-Ep
	for pana-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 08:26:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27233
	for <pana-web-archive@ietf.org>; Mon, 6 Oct 2003 08:25:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6UR9-0004W3-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 08:26:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6UR8-0004Vz-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 08:26:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6UR6-0003CG-S4; Mon, 06 Oct 2003 08:26:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6UQn-0003Bh-CJ
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 08:25:41 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27193
	for <pana@ietf.org>; Mon, 6 Oct 2003 08:25:32 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6UQm-0004VD-00
	for pana@ietf.org; Mon, 06 Oct 2003 08:25:40 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6UQl-0004Uc-00
	for pana@ietf.org; Mon, 06 Oct 2003 08:25:39 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h96COwt00458
	for <pana@ietf.org>; Mon, 6 Oct 2003 15:25:00 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T651e68f74bac158f24077@esvir04nok.ntc.nokia.com>;
 Mon, 6 Oct 2003 15:24:52 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 6 Oct 2003 15:24:52 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue19] Result-Code AVP values?
Date: Mon, 6 Oct 2003 15:24:51 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D33@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOJCved1yCGadKCQLeQ8zA0HUHHFAC+XFYQ
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 06 Oct 2003 12:24:52.0231 (UTC) FILETIME=[D7A70170:01C38C04]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Ok. So do you want to say that realm based routing is outside=20
the scope of PANA and in error case NAS must inform PaC in some=20
other means than PANA protocol? I don't mind taking this error=20
case away. Anyway, I'm curious of how 802.1X does handle this=20
case?

- Dan

> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 02 October, 2003 20:31
> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>=20
>=20
> >>>        PANA_REALM_NOT_SERVED                   3003
> >>>           Error code from PAA to PaC.  The network=20
> doesn't recognize
> >>>           the realm.
> >>=20
> >> We don't have a place where PaC sends the realm information.
> >> So, I can't see
> >> where such an error would be returned to the PaC.
> >=20
> > The EAP-Response/Identity contains the realm if it is required. Or
> > should we create a NAI AVP, that contains only the realm? Realm is
> > needed to route the packet to the right AAA backend. If PAA
> > functionality doesn't check the realm, NAS or for example the local
> > AAA proxy will do it. But in the case of unknown realm the client
> > should be notified.
>=20
> I should have said "We don't have a place where PaC sends the realm
> information in PANA." You are right that EAP client ID can=20
> have this, but
> than it is the responsibility of EAP or EAP method to deal=20
> with this. This
> error case should not leak into PANA.
>=20
> Alper
>=20
>=20

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



From pana-admin@ietf.org  Mon Oct  6 09:04:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28362
	for <pana-archive@lists.ietf.org>; Mon, 6 Oct 2003 09:04:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V1t-0004XR-7k; Mon, 06 Oct 2003 09:04:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V1g-0004X4-Vd
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 09:03:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28348
	for <pana@ietf.org>; Mon, 6 Oct 2003 09:03:39 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V1f-0004rf-00
	for pana@ietf.org; Mon, 06 Oct 2003 09:03:47 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V1e-0004rc-00
	for pana@ietf.org; Mon, 06 Oct 2003 09:03:46 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h96D3it17827
	for <pana@ietf.org>; Mon, 6 Oct 2003 16:03:44 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T651e8c8ca5ac158f23077@esvir03nok.nokia.com>;
 Mon, 6 Oct 2003 16:03:44 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 6 Oct 2003 16:03:43 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue34] Behaviour with NAP and ISP (two EAPauthentications).
Date: Mon, 6 Oct 2003 16:03:42 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C58D@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue34] Behaviour with NAP and ISP (two EAPauthentications).
Thread-Index: AcOJFpV/I1Tj6LtuTCS7+8UaoWCbgQC8VbJA
To: <alper@docomolabs-usa.com>, <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 06 Oct 2003 13:03:43.0253 (UTC) FILETIME=[450CBC50:01C38C0A]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

I'm just thinking of what is the benefit of binding two EAP =
authentications into one PANA session? This already makes the system =
complex and we encounter problems like this. Where did this idea come =
from anyways? The original NAP and ISP scenario (coffee shop) for my =
understanding was related to issue25, not with two EAP authentications.

If PaC sees only a "combined session", how does it know which EAP method =
to use for reauthentcation. EAP doesn't have sessions, so we can't say =
it's an EAP level issue. Looking from the network perspective the two =
separate EAP authentications may create separate sessions (different AAA =
backends) with different session lifetimes..

From Yoshihiro's email below:
"On the other hand, consideration is needed for this approach to handle =
different session lifetimes for NAP and ISP, as you also mentioned =
below. One solution to deal with this is to perform both EAP-based =
re-authentications for both NAP and ISP with using the minimum value of =
the NAP and ISP session lifetimes as the PANA session lifetime (though =
this is not efficient when the difference between the NAP and ISP =
session lifetimes are large.)"


- Dan


> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 02 October, 2003 21:54
> To: Yoshihiro Ohba; Forsberg Dan (NRC/Helsinki)
> Cc: pana@ietf.org
> Subject: Re: [Pana] [issue34] Behaviour with NAP and ISP (two
> EAPauthentications).
>=20
>=20
>=20
> This is what we said in the requirements draft:
>=20
>    Determining the authorization
>    parameters as a result of two separate authentications is an
>    operational issue and therefore it is outside the scope of PANA.
>=20
> I think from PANA perspective, it is sufficient to enable two=20
> rounds of
> authentication. But other than that, we should let the NAS=20
> mold NAP and ISP
> authentication into a single "PANA session". How exactly this=20
> be done should
> not be the concern of the base pana protocol. And once there=20
> is a session,
> neither PAA nor PaC would see "ISP session" or "NAP session",=20
> it is just a
> "combined session".
>=20
> Cost (complexity) of separating NAP and ISP authentication=20
> beyond what we
> already provide seems higher than the benefits, imo.
>=20
> Alper
>=20
>=20
>=20
>=20
>=20
> > This is an interesting issue.
> >=20
> > Basically there are pros and cons as to whether using a=20
> distinct PANA
> > session for each of two EAP authentication or using a single PANA
> > session for two EAP authentications.
> >=20
> > As you mentioned, using a distinct PANA session for each of NAP and
> > ISP authentications will make it easier to handle different session
> > lifetimes for NAP and ISP.  However, there would be the
> > following cons in this approach:
> >=20
> > o Which PANA SA should be used for bootstrapping IPsec and/or DHCP
> > authentication?
> >=20
> > o What happens if the PANA session from which IPsec and/or DHCP
> > authentication are bootstrapped is terminated while the other PANA
> > session still remains established.
> >=20
> > Especially the latter issue would be more difficult to solve and I
> > don't recommend this approach.
> >=20
> > Using a singel PANA session for both NAP and ISP=20
> authentications does
> > not have above the issues because there is only one PANA SA (and we
> > already decided to use the MSK of the first successul EAP
> > authentication with key derivation to derive the PANA SA). =20
> This also
> > implies that when a PANA session is terminated, both NAP and ISP
> > authorizations will be removed.  On the other hand, consideration is
> > needed for this approach to handle different session=20
> lifetimes for NAP
> > and ISP, as you also mentioned below.  One solution to deal=20
> with this
> > is to perform both EAP-based re-authentications for both NAP and ISP
> > with using the minimum value of the NAP and ISP session lifetimes as
> > the PANA session lifetime (though this is not efficient when the
> > difference between the NAP and ISP session lifetimes are large.)
> >=20
> > What do you think?
> >=20
> > Yoshihiro Ohba
> >=20
> >=20
> >=20
> > On Wed, Oct 01, 2003 at 01:53:00PM +0300,=20
> Dan.Forsberg@nokia.com wrote:
> >> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> >>=20
> >> How does Session-Lifetime (or Session-Timeout) realate to=20
> NAP and ISP
> >> authentications? When this lifetime expires PaC should probably
> >> reauthenticate to NAP and ISP?
> >>=20
> >> Clarification needed into the draft also for the case of session
> >> terminateion. Does PaC or PAA terminate the part of the=20
> session that
> >> relates to the ISP or NAP or both.
> >>=20
> >> Would it be simpler to use PANA sessions with one EAP method only,
> >> instead of two serial EAP methods in one session. Or=20
> should there be one
> >> master session (NAP) and then subsessions (for ISPs). When=20
> the master
> >> session is terminated, the subsessions are also=20
> terminated. PaC and PAA
> >> can also terminate subsessions. Reauthentication should=20
> happen for all
> >> the sessions because of independent EAP methods.
> >>=20
> >> - Dan
> >>=20
> >>=20
> >> ----------
> >> category: Technical
> >> document: draft-ietf-pana-pana-xx.txt
> >> messages: 105
> >> nosy: dforsber
> >> priority: Must Fix
> >> status: No Discussion
> >> title: Behaviour with NAP and ISP (two EAP authentications).
> >> ________________________________________________
> >> PANA Issues <pana_issues@danforsberg.info>
> >> http://danforsberg.info:8080/pana-issues/issue34
> >> ________________________________________________
> >>=20
> >> _______________________________________________
> >> Pana mailing list
> >> Pana@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/pana
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
>=20

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


From exim@www1.ietf.org  Mon Oct  6 09:04:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28377
	for <pana-archive@odin.ietf.org>; Mon, 6 Oct 2003 09:04:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V1x-0004Y3-5l
	for pana-archive@odin.ietf.org; Mon, 06 Oct 2003 09:04:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h96D451O017483
	for pana-archive@odin.ietf.org; Mon, 6 Oct 2003 09:04:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V1w-0004Xs-VV
	for pana-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 09:04:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28352
	for <pana-web-archive@ietf.org>; Mon, 6 Oct 2003 09:03:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V1v-0004rl-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 09:04:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V1v-0004ri-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 09:04:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V1t-0004XR-7k; Mon, 06 Oct 2003 09:04:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V1g-0004X4-Vd
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 09:03:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28348
	for <pana@ietf.org>; Mon, 6 Oct 2003 09:03:39 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V1f-0004rf-00
	for pana@ietf.org; Mon, 06 Oct 2003 09:03:47 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V1e-0004rc-00
	for pana@ietf.org; Mon, 06 Oct 2003 09:03:46 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h96D3it17827
	for <pana@ietf.org>; Mon, 6 Oct 2003 16:03:44 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T651e8c8ca5ac158f23077@esvir03nok.nokia.com>;
 Mon, 6 Oct 2003 16:03:44 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 6 Oct 2003 16:03:43 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue34] Behaviour with NAP and ISP (two EAPauthentications).
Date: Mon, 6 Oct 2003 16:03:42 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C58D@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue34] Behaviour with NAP and ISP (two EAPauthentications).
Thread-Index: AcOJFpV/I1Tj6LtuTCS7+8UaoWCbgQC8VbJA
To: <alper@docomolabs-usa.com>, <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 06 Oct 2003 13:03:43.0253 (UTC) FILETIME=[450CBC50:01C38C0A]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I'm just thinking of what is the benefit of binding two EAP =
authentications into one PANA session? This already makes the system =
complex and we encounter problems like this. Where did this idea come =
from anyways? The original NAP and ISP scenario (coffee shop) for my =
understanding was related to issue25, not with two EAP authentications.

If PaC sees only a "combined session", how does it know which EAP method =
to use for reauthentcation. EAP doesn't have sessions, so we can't say =
it's an EAP level issue. Looking from the network perspective the two =
separate EAP authentications may create separate sessions (different AAA =
backends) with different session lifetimes..

From Yoshihiro's email below:
"On the other hand, consideration is needed for this approach to handle =
different session lifetimes for NAP and ISP, as you also mentioned =
below. One solution to deal with this is to perform both EAP-based =
re-authentications for both NAP and ISP with using the minimum value of =
the NAP and ISP session lifetimes as the PANA session lifetime (though =
this is not efficient when the difference between the NAP and ISP =
session lifetimes are large.)"


- Dan


> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 02 October, 2003 21:54
> To: Yoshihiro Ohba; Forsberg Dan (NRC/Helsinki)
> Cc: pana@ietf.org
> Subject: Re: [Pana] [issue34] Behaviour with NAP and ISP (two
> EAPauthentications).
>=20
>=20
>=20
> This is what we said in the requirements draft:
>=20
>    Determining the authorization
>    parameters as a result of two separate authentications is an
>    operational issue and therefore it is outside the scope of PANA.
>=20
> I think from PANA perspective, it is sufficient to enable two=20
> rounds of
> authentication. But other than that, we should let the NAS=20
> mold NAP and ISP
> authentication into a single "PANA session". How exactly this=20
> be done should
> not be the concern of the base pana protocol. And once there=20
> is a session,
> neither PAA nor PaC would see "ISP session" or "NAP session",=20
> it is just a
> "combined session".
>=20
> Cost (complexity) of separating NAP and ISP authentication=20
> beyond what we
> already provide seems higher than the benefits, imo.
>=20
> Alper
>=20
>=20
>=20
>=20
>=20
> > This is an interesting issue.
> >=20
> > Basically there are pros and cons as to whether using a=20
> distinct PANA
> > session for each of two EAP authentication or using a single PANA
> > session for two EAP authentications.
> >=20
> > As you mentioned, using a distinct PANA session for each of NAP and
> > ISP authentications will make it easier to handle different session
> > lifetimes for NAP and ISP.  However, there would be the
> > following cons in this approach:
> >=20
> > o Which PANA SA should be used for bootstrapping IPsec and/or DHCP
> > authentication?
> >=20
> > o What happens if the PANA session from which IPsec and/or DHCP
> > authentication are bootstrapped is terminated while the other PANA
> > session still remains established.
> >=20
> > Especially the latter issue would be more difficult to solve and I
> > don't recommend this approach.
> >=20
> > Using a singel PANA session for both NAP and ISP=20
> authentications does
> > not have above the issues because there is only one PANA SA (and we
> > already decided to use the MSK of the first successul EAP
> > authentication with key derivation to derive the PANA SA). =20
> This also
> > implies that when a PANA session is terminated, both NAP and ISP
> > authorizations will be removed.  On the other hand, consideration is
> > needed for this approach to handle different session=20
> lifetimes for NAP
> > and ISP, as you also mentioned below.  One solution to deal=20
> with this
> > is to perform both EAP-based re-authentications for both NAP and ISP
> > with using the minimum value of the NAP and ISP session lifetimes as
> > the PANA session lifetime (though this is not efficient when the
> > difference between the NAP and ISP session lifetimes are large.)
> >=20
> > What do you think?
> >=20
> > Yoshihiro Ohba
> >=20
> >=20
> >=20
> > On Wed, Oct 01, 2003 at 01:53:00PM +0300,=20
> Dan.Forsberg@nokia.com wrote:
> >> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> >>=20
> >> How does Session-Lifetime (or Session-Timeout) realate to=20
> NAP and ISP
> >> authentications? When this lifetime expires PaC should probably
> >> reauthenticate to NAP and ISP?
> >>=20
> >> Clarification needed into the draft also for the case of session
> >> terminateion. Does PaC or PAA terminate the part of the=20
> session that
> >> relates to the ISP or NAP or both.
> >>=20
> >> Would it be simpler to use PANA sessions with one EAP method only,
> >> instead of two serial EAP methods in one session. Or=20
> should there be one
> >> master session (NAP) and then subsessions (for ISPs). When=20
> the master
> >> session is terminated, the subsessions are also=20
> terminated. PaC and PAA
> >> can also terminate subsessions. Reauthentication should=20
> happen for all
> >> the sessions because of independent EAP methods.
> >>=20
> >> - Dan
> >>=20
> >>=20
> >> ----------
> >> category: Technical
> >> document: draft-ietf-pana-pana-xx.txt
> >> messages: 105
> >> nosy: dforsber
> >> priority: Must Fix
> >> status: No Discussion
> >> title: Behaviour with NAP and ISP (two EAP authentications).
> >> ________________________________________________
> >> PANA Issues <pana_issues@danforsberg.info>
> >> http://danforsberg.info:8080/pana-issues/issue34
> >> ________________________________________________
> >>=20
> >> _______________________________________________
> >> Pana mailing list
> >> Pana@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/pana
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
>=20

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



From pana-admin@ietf.org  Mon Oct  6 09:07:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28471
	for <pana-archive@lists.ietf.org>; Mon, 6 Oct 2003 09:07:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V4o-0004el-3R; Mon, 06 Oct 2003 09:07:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V4F-0004cE-1k
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 09:06:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28431
	for <pana@ietf.org>; Mon, 6 Oct 2003 09:06:17 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V4D-0004sv-00
	for pana@ietf.org; Mon, 06 Oct 2003 09:06:25 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V4C-0004ss-00
	for pana@ietf.org; Mon, 06 Oct 2003 09:06:25 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h96D6Ot21266
	for <pana@ietf.org>; Mon, 6 Oct 2003 16:06:24 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T651e8efbbeac158f24077@esvir04nok.ntc.nokia.com>;
 Mon, 6 Oct 2003 16:06:23 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 6 Oct 2003 16:06:22 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue19] Result-Code AVP values?
Date: Mon, 6 Oct 2003 16:06:22 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D37@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOJCved1yCGadKCQLeQ8zA0HUHHFAC+XFYQAAF6aiA=
To: <Dan.Forsberg@nokia.com>, <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 06 Oct 2003 13:06:22.0826 (UTC) FILETIME=[A429A4A0:01C38C0A]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Just one more comment. The usage scenarios document chapter 3=20
(problem statement) says that the authentication agent (PAA)=20
chooses the backend authentication server based on the identity,=20
for example NAI..
- Dan

> -----Original Message-----
> From: ext Dan.Forsberg@nokia.com [mailto:Dan.Forsberg@nokia.com]
> Sent: 06 October, 2003 15:25
> To: alper@docomolabs-usa.com; pana@ietf.org
> Subject: RE: [Pana] [issue19] Result-Code AVP values?
>=20
>=20
> Ok. So do you want to say that realm based routing is outside=20
> the scope of PANA and in error case NAS must inform PaC in some=20
> other means than PANA protocol? I don't mind taking this error=20
> case away. Anyway, I'm curious of how 802.1X does handle this=20
> case?
>=20
> - Dan
>=20
> > -----Original Message-----
> > From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > Sent: 02 October, 2003 20:31
> > To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > Subject: Re: [Pana] [issue19] Result-Code AVP values?
> >=20
> >=20
> > >>>        PANA_REALM_NOT_SERVED                   3003
> > >>>           Error code from PAA to PaC.  The network=20
> > doesn't recognize
> > >>>           the realm.
> > >>=20
> > >> We don't have a place where PaC sends the realm information.
> > >> So, I can't see
> > >> where such an error would be returned to the PaC.
> > >=20
> > > The EAP-Response/Identity contains the realm if it is required. Or
> > > should we create a NAI AVP, that contains only the realm? Realm is
> > > needed to route the packet to the right AAA backend. If PAA
> > > functionality doesn't check the realm, NAS or for example=20
> the local
> > > AAA proxy will do it. But in the case of unknown realm the client
> > > should be notified.
> >=20
> > I should have said "We don't have a place where PaC sends the realm
> > information in PANA." You are right that EAP client ID can=20
> > have this, but
> > than it is the responsibility of EAP or EAP method to deal=20
> > with this. This
> > error case should not leak into PANA.
> >=20
> > Alper
> >=20
> >=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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


From exim@www1.ietf.org  Mon Oct  6 09:07:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28486
	for <pana-archive@odin.ietf.org>; Mon, 6 Oct 2003 09:07:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V4s-0004hg-Ev
	for pana-archive@odin.ietf.org; Mon, 06 Oct 2003 09:07:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h96D752l018066
	for pana-archive@odin.ietf.org; Mon, 6 Oct 2003 09:07:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V4r-0004hB-FU
	for pana-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 09:07:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28459
	for <pana-web-archive@ietf.org>; Mon, 6 Oct 2003 09:06:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V4p-0004tc-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 09:07:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V4p-0004tZ-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 09:07:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V4o-0004el-3R; Mon, 06 Oct 2003 09:07:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6V4F-0004cE-1k
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 09:06:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28431
	for <pana@ietf.org>; Mon, 6 Oct 2003 09:06:17 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V4D-0004sv-00
	for pana@ietf.org; Mon, 06 Oct 2003 09:06:25 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6V4C-0004ss-00
	for pana@ietf.org; Mon, 06 Oct 2003 09:06:25 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h96D6Ot21266
	for <pana@ietf.org>; Mon, 6 Oct 2003 16:06:24 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T651e8efbbeac158f24077@esvir04nok.ntc.nokia.com>;
 Mon, 6 Oct 2003 16:06:23 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 6 Oct 2003 16:06:22 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue19] Result-Code AVP values?
Date: Mon, 6 Oct 2003 16:06:22 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D37@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOJCved1yCGadKCQLeQ8zA0HUHHFAC+XFYQAAF6aiA=
To: <Dan.Forsberg@nokia.com>, <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 06 Oct 2003 13:06:22.0826 (UTC) FILETIME=[A429A4A0:01C38C0A]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Just one more comment. The usage scenarios document chapter 3=20
(problem statement) says that the authentication agent (PAA)=20
chooses the backend authentication server based on the identity,=20
for example NAI..
- Dan

> -----Original Message-----
> From: ext Dan.Forsberg@nokia.com [mailto:Dan.Forsberg@nokia.com]
> Sent: 06 October, 2003 15:25
> To: alper@docomolabs-usa.com; pana@ietf.org
> Subject: RE: [Pana] [issue19] Result-Code AVP values?
>=20
>=20
> Ok. So do you want to say that realm based routing is outside=20
> the scope of PANA and in error case NAS must inform PaC in some=20
> other means than PANA protocol? I don't mind taking this error=20
> case away. Anyway, I'm curious of how 802.1X does handle this=20
> case?
>=20
> - Dan
>=20
> > -----Original Message-----
> > From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > Sent: 02 October, 2003 20:31
> > To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > Subject: Re: [Pana] [issue19] Result-Code AVP values?
> >=20
> >=20
> > >>>        PANA_REALM_NOT_SERVED                   3003
> > >>>           Error code from PAA to PaC.  The network=20
> > doesn't recognize
> > >>>           the realm.
> > >>=20
> > >> We don't have a place where PaC sends the realm information.
> > >> So, I can't see
> > >> where such an error would be returned to the PaC.
> > >=20
> > > The EAP-Response/Identity contains the realm if it is required. Or
> > > should we create a NAI AVP, that contains only the realm? Realm is
> > > needed to route the packet to the right AAA backend. If PAA
> > > functionality doesn't check the realm, NAS or for example=20
> the local
> > > AAA proxy will do it. But in the case of unknown realm the client
> > > should be notified.
> >=20
> > I should have said "We don't have a place where PaC sends the realm
> > information in PANA." You are right that EAP client ID can=20
> > have this, but
> > than it is the responsibility of EAP or EAP method to deal=20
> > with this. This
> > error case should not leak into PANA.
> >=20
> > Alper
> >=20
> >=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-admin@ietf.org  Mon Oct  6 12:35:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10760
	for <pana-archive@lists.ietf.org>; Mon, 6 Oct 2003 12:35:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6YK6-0006n3-4H; Mon, 06 Oct 2003 12:35:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6YJi-0006mP-Kw
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 12:34:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10690
	for <pana@ietf.org>; Mon, 6 Oct 2003 12:34:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6YJh-0000ZF-00
	for pana@ietf.org; Mon, 06 Oct 2003 12:34:37 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6YJg-0000ZC-00
	for pana@ietf.org; Mon, 06 Oct 2003 12:34:36 -0400
Date: Mon, 06 Oct 2003 09:34:20 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBA6E79C.9E08%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6D33@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> Ok. So do you want to say that realm based routing is outside
> the scope of PANA and in error case NAS must inform PaC in some
> other means than PANA protocol?

Yes, I'm thinking that this should be happening transparent to PANA.

> I don't mind taking this error
> case away. Anyway, I'm curious of how 802.1X does handle this
> case?

I think this is also an EAP question. What would be the EAP behavior when
the NAS cannot recognize the EAP client identifier?

From your other message:
> Just one more comment. The usage scenarios document chapter 3
> (problem statement) says that the authentication agent (PAA)
> chooses the backend authentication server based on the identity,
> for example NAI..

If we were to expand "the authentication agent" from that text, actually it
should be the "NAS" (draft-ietf-aaa-eap) implementation which needs to deal
with AAA routing, not "PAA."

Alper




> 
> - Dan
> 
>> -----Original Message-----
>> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
>> Sent: 02 October, 2003 20:31
>> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
>> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>> 
>> 
>>>>>        PANA_REALM_NOT_SERVED                   3003
>>>>>           Error code from PAA to PaC.  The network
>> doesn't recognize
>>>>>           the realm.
>>>> 
>>>> We don't have a place where PaC sends the realm information.
>>>> So, I can't see
>>>> where such an error would be returned to the PaC.
>>> 
>>> The EAP-Response/Identity contains the realm if it is required. Or
>>> should we create a NAI AVP, that contains only the realm? Realm is
>>> needed to route the packet to the right AAA backend. If PAA
>>> functionality doesn't check the realm, NAS or for example the local
>>> AAA proxy will do it. But in the case of unknown realm the client
>>> should be notified.
>> 
>> I should have said "We don't have a place where PaC sends the realm
>> information in PANA." You are right that EAP client ID can
>> have this, but
>> than it is the responsibility of EAP or EAP method to deal
>> with this. This
>> error case should not leak into PANA.
>> 
>> 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 exim@www1.ietf.org  Mon Oct  6 12:35:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10775
	for <pana-archive@odin.ietf.org>; Mon, 6 Oct 2003 12:35:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6YK9-0006nj-9z
	for pana-archive@odin.ietf.org; Mon, 06 Oct 2003 12:35:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h96GZ5ep026139
	for pana-archive@odin.ietf.org; Mon, 6 Oct 2003 12:35:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6YK9-0006nW-4X
	for pana-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 12:35:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10712
	for <pana-web-archive@ietf.org>; Mon, 6 Oct 2003 12:34:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6YK7-0000Zk-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 12:35:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6YK7-0000Zh-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 12:35:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6YK6-0006n3-4H; Mon, 06 Oct 2003 12:35:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6YJi-0006mP-Kw
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 12:34:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10690
	for <pana@ietf.org>; Mon, 6 Oct 2003 12:34:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6YJh-0000ZF-00
	for pana@ietf.org; Mon, 06 Oct 2003 12:34:37 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6YJg-0000ZC-00
	for pana@ietf.org; Mon, 06 Oct 2003 12:34:36 -0400
Date: Mon, 06 Oct 2003 09:34:20 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBA6E79C.9E08%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6D33@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> Ok. So do you want to say that realm based routing is outside
> the scope of PANA and in error case NAS must inform PaC in some
> other means than PANA protocol?

Yes, I'm thinking that this should be happening transparent to PANA.

> I don't mind taking this error
> case away. Anyway, I'm curious of how 802.1X does handle this
> case?

I think this is also an EAP question. What would be the EAP behavior when
the NAS cannot recognize the EAP client identifier?

From your other message:
> Just one more comment. The usage scenarios document chapter 3
> (problem statement) says that the authentication agent (PAA)
> chooses the backend authentication server based on the identity,
> for example NAI..

If we were to expand "the authentication agent" from that text, actually it
should be the "NAS" (draft-ietf-aaa-eap) implementation which needs to deal
with AAA routing, not "PAA."

Alper




> 
> - Dan
> 
>> -----Original Message-----
>> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
>> Sent: 02 October, 2003 20:31
>> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
>> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>> 
>> 
>>>>>        PANA_REALM_NOT_SERVED                   3003
>>>>>           Error code from PAA to PaC.  The network
>> doesn't recognize
>>>>>           the realm.
>>>> 
>>>> We don't have a place where PaC sends the realm information.
>>>> So, I can't see
>>>> where such an error would be returned to the PaC.
>>> 
>>> The EAP-Response/Identity contains the realm if it is required. Or
>>> should we create a NAI AVP, that contains only the realm? Realm is
>>> needed to route the packet to the right AAA backend. If PAA
>>> functionality doesn't check the realm, NAS or for example the local
>>> AAA proxy will do it. But in the case of unknown realm the client
>>> should be notified.
>> 
>> I should have said "We don't have a place where PaC sends the realm
>> information in PANA." You are right that EAP client ID can
>> have this, but
>> than it is the responsibility of EAP or EAP method to deal
>> with this. This
>> error case should not leak into PANA.
>> 
>> 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-admin@ietf.org  Mon Oct  6 13:22:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13441
	for <pana-archive@lists.ietf.org>; Mon, 6 Oct 2003 13:22:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6Z3Y-0000aO-CI; Mon, 06 Oct 2003 13:22:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6Z3J-0000a0-7U
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 13:21:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13384
	for <pana@ietf.org>; Mon, 6 Oct 2003 13:21:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6Z3H-0001JL-00
	for pana@ietf.org; Mon, 06 Oct 2003 13:21:43 -0400
Received: from smtp005.mail.ukl.yahoo.com ([217.12.11.36])
	by ietf-mx with smtp (Exim 4.12)
	id 1A6Z3G-0001Id-00
	for pana@ietf.org; Mon, 06 Oct 2003 13:21:42 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp1.mail.vip.ukl.yahoo.com with SMTP; 6 Oct 2003 17:06:58 -0000
Message-ID: <003101c38c2c$4460f380$5a100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: <pana@ietf.org>
Date: Mon, 6 Oct 2003 10:07:01 -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.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Subject: [Pana] PANA-IPSEC draft ?
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hello,

draft-ietf-pana-ipsec-00.txt should have addressed most of the issues since
the last time.
I had problems accessing the archives sometime back. So, i am not sure this
addresses
all of the concerns. At least the major ones are taken care of. So, please
send me your
comments on the list.

thanks
-mohan


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


From exim@www1.ietf.org  Mon Oct  6 13:22:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13462
	for <pana-archive@odin.ietf.org>; Mon, 6 Oct 2003 13:22:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6Z3b-0000b5-MN
	for pana-archive@odin.ietf.org; Mon, 06 Oct 2003 13:22:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h96HM3Nu002289
	for pana-archive@odin.ietf.org; Mon, 6 Oct 2003 13:22:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6Z3b-0000aq-Gv
	for pana-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 13:22:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13402
	for <pana-web-archive@ietf.org>; Mon, 6 Oct 2003 13:21:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6Z3Z-0001Jm-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 13:22:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6Z3Z-0001Jj-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 13:22:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6Z3Y-0000aO-CI; Mon, 06 Oct 2003 13:22:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6Z3J-0000a0-7U
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 13:21:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13384
	for <pana@ietf.org>; Mon, 6 Oct 2003 13:21:34 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6Z3H-0001JL-00
	for pana@ietf.org; Mon, 06 Oct 2003 13:21:43 -0400
Received: from smtp005.mail.ukl.yahoo.com ([217.12.11.36])
	by ietf-mx with smtp (Exim 4.12)
	id 1A6Z3G-0001Id-00
	for pana@ietf.org; Mon, 06 Oct 2003 13:21:42 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp1.mail.vip.ukl.yahoo.com with SMTP; 6 Oct 2003 17:06:58 -0000
Message-ID: <003101c38c2c$4460f380$5a100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: <pana@ietf.org>
Date: Mon, 6 Oct 2003 10:07:01 -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.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Subject: [Pana] PANA-IPSEC draft ?
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello,

draft-ietf-pana-ipsec-00.txt should have addressed most of the issues since
the last time.
I had problems accessing the archives sometime back. So, i am not sure this
addresses
all of the concerns. At least the major ones are taken care of. So, please
send me your
comments on the list.

thanks
-mohan


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



From exim@www1.ietf.org  Mon Oct  6 13:33:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13851
	for <pana-archive@odin.ietf.org>; Mon, 6 Oct 2003 13:33:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6ZEG-0000yg-6E
	for pana-archive@odin.ietf.org; Mon, 06 Oct 2003 13:33:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h96HX4eT003755
	for pana-archive@odin.ietf.org; Mon, 6 Oct 2003 13:33:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6ZEG-0000yU-0w
	for pana-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 13:33:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13830
	for <pana-web-archive@ietf.org>; Mon, 6 Oct 2003 13:32:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6ZED-0001Rl-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 13:33:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6ZED-0001Ri-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 13:33:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6ZED-0000xI-ID; Mon, 06 Oct 2003 13:33:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6ZDW-0000wa-H8
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 13:32:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13821
	for <pana@ietf.org>; Mon, 6 Oct 2003 13:32:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6ZDU-0001RY-00
	for pana@ietf.org; Mon, 06 Oct 2003 13:32:16 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6ZDT-0001RT-00
	for pana@ietf.org; Mon, 06 Oct 2003 13:32:15 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h96HWAF1023677;
	Tue, 7 Oct 2003 02:32:10 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h96HWANS011475;
	Tue, 7 Oct 2003 02:32:10 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id CAA11474 ; Tue, 7 Oct 2003 02:32:10 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA28207; Tue, 7 Oct 2003 02:32:09 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA18958; Tue, 7 Oct 2003 02:32:09 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h96HW8qT006974;
	Tue, 7 Oct 2003 02:32:08 +0900 (JST)
Received: from steelhead ([159.119.168.104]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMC00G10JDI0Z@tsbpo1.po.toshiba.co.jp>; Tue,
 7 Oct 2003 02:32:07 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A6ZBJ-0001dR-00; Mon, 06 Oct 2003 10:30:01 -0700
Date: Mon, 06 Oct 2003 10:30:01 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New  [issue31] Init responsibility of for EAP level
 reauthentication?
In-reply-to: <BB988216.942A%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Dan.Forsberg@nokia.com, pana@ietf.org
Message-id: <20031006173000.GB5880@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20030918151320.GA9128@steelhead>
 <BB988216.942A%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Thu, Sep 25, 2003 at 11:29:26AM -0700, Alper Yegin wrote:
> Are we talking about restarting the EAP state machine, or engaging a
> EAP-method-specific re-auth mechanism?

The former.  

> 
> If former: PaC can send PANA-PAA-Discover to initiate, and PAA can send
> PANA-Start-Request to initiate or as a response.

I think this is not the only allowable sequence in the former case.
PAA can send PANA-Auth-Request to initiate EAP-based re-authentication
if the PAA already has an established PANA session for the PaC.  That
is why I mentioned race condition.

Yoshihiro Ohba

> 
> If latter: PAA can send PANA-Auth-Request. I don't think this is a valid
> case for PaC to send anything, because only the authenticator can send EAP
> requests. (how can the EAP peer initiate the EAP-method-level reauth?)
> 
> Alper
> 
> 
> 
> > For timer-based EAP level reauthentication, PAA should be responsible
> > for initiating the reauthentication because PaC does not know enough
> > information (such as grace period) to be able to perform the
> > reauthentication at an appropriate time.  On the other hand, if EAP
> > level reauthentication is to be performed for other reasons, I think
> > both PaC and PAA can initiate the reauthentication.
> > 
> > There would be one issue in the latter case.  What happens if both PaC
> > and PAA initate EAP level reauthentication at the same time?  When
> > this happens, the PaC will send a PANA-PAA-Discover message while the
> > PAA will send a PANA-Auth-Request message, according to the EAP level
> > reauthentication behavior described in section 4.4.  In this case, the
> > PAA can rely on the EAP restransmission (as a result multiple
> > PANA-Auth-Request message with carrying the same EAP message will be
> > generated) and simply ignore the received PANA-PAA-Discover message.
> > This way, the race condition can be resolved.
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Thu, Sep 18, 2003 at 04:33:05PM +0300, Dan.Forsberg@nokia.com wrote:
> >> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> >> 
> >> Is PaC or PAA responsible of initiating EAP level reauthentication? This
> >> MUST be clearly stated in the draft.
> >> 
> >> 
> >> ----------
> >> category: Technical
> >> document: draft-ietf-pana-pana-xx.txt
> >> messages: 86
> >> nosy: dforsber
> >> priority: Must Fix
> >> status: No Discussion
> >> title: Init responsibility of for EAP level reauthentication?
> >> ________________________________________________
> >> PANA Issues <pana_issues@danforsberg.info>
> >> http://danforsberg.info:8080/pana-issues/issue31
> >> ________________________________________________
> >> 
> >> _______________________________________________
> >> Pana mailing list
> >> Pana@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/pana
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> > 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

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



From pana-admin@ietf.org  Mon Oct  6 13:33:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13871
	for <pana-archive@lists.ietf.org>; Mon, 6 Oct 2003 13:33:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6ZED-0000xI-ID; Mon, 06 Oct 2003 13:33:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6ZDW-0000wa-H8
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 13:32:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13821
	for <pana@ietf.org>; Mon, 6 Oct 2003 13:32:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6ZDU-0001RY-00
	for pana@ietf.org; Mon, 06 Oct 2003 13:32:16 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6ZDT-0001RT-00
	for pana@ietf.org; Mon, 06 Oct 2003 13:32:15 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h96HWAF1023677;
	Tue, 7 Oct 2003 02:32:10 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h96HWANS011475;
	Tue, 7 Oct 2003 02:32:10 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id CAA11474 ; Tue, 7 Oct 2003 02:32:10 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA28207; Tue, 7 Oct 2003 02:32:09 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA18958; Tue, 7 Oct 2003 02:32:09 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h96HW8qT006974;
	Tue, 7 Oct 2003 02:32:08 +0900 (JST)
Received: from steelhead ([159.119.168.104]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMC00G10JDI0Z@tsbpo1.po.toshiba.co.jp>; Tue,
 7 Oct 2003 02:32:07 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A6ZBJ-0001dR-00; Mon, 06 Oct 2003 10:30:01 -0700
Date: Mon, 06 Oct 2003 10:30:01 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New  [issue31] Init responsibility of for EAP level
 reauthentication?
In-reply-to: <BB988216.942A%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Dan.Forsberg@nokia.com, pana@ietf.org
Message-id: <20031006173000.GB5880@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20030918151320.GA9128@steelhead>
 <BB988216.942A%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Thu, Sep 25, 2003 at 11:29:26AM -0700, Alper Yegin wrote:
> Are we talking about restarting the EAP state machine, or engaging a
> EAP-method-specific re-auth mechanism?

The former.  

> 
> If former: PaC can send PANA-PAA-Discover to initiate, and PAA can send
> PANA-Start-Request to initiate or as a response.

I think this is not the only allowable sequence in the former case.
PAA can send PANA-Auth-Request to initiate EAP-based re-authentication
if the PAA already has an established PANA session for the PaC.  That
is why I mentioned race condition.

Yoshihiro Ohba

> 
> If latter: PAA can send PANA-Auth-Request. I don't think this is a valid
> case for PaC to send anything, because only the authenticator can send EAP
> requests. (how can the EAP peer initiate the EAP-method-level reauth?)
> 
> Alper
> 
> 
> 
> > For timer-based EAP level reauthentication, PAA should be responsible
> > for initiating the reauthentication because PaC does not know enough
> > information (such as grace period) to be able to perform the
> > reauthentication at an appropriate time.  On the other hand, if EAP
> > level reauthentication is to be performed for other reasons, I think
> > both PaC and PAA can initiate the reauthentication.
> > 
> > There would be one issue in the latter case.  What happens if both PaC
> > and PAA initate EAP level reauthentication at the same time?  When
> > this happens, the PaC will send a PANA-PAA-Discover message while the
> > PAA will send a PANA-Auth-Request message, according to the EAP level
> > reauthentication behavior described in section 4.4.  In this case, the
> > PAA can rely on the EAP restransmission (as a result multiple
> > PANA-Auth-Request message with carrying the same EAP message will be
> > generated) and simply ignore the received PANA-PAA-Discover message.
> > This way, the race condition can be resolved.
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Thu, Sep 18, 2003 at 04:33:05PM +0300, Dan.Forsberg@nokia.com wrote:
> >> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> >> 
> >> Is PaC or PAA responsible of initiating EAP level reauthentication? This
> >> MUST be clearly stated in the draft.
> >> 
> >> 
> >> ----------
> >> category: Technical
> >> document: draft-ietf-pana-pana-xx.txt
> >> messages: 86
> >> nosy: dforsber
> >> priority: Must Fix
> >> status: No Discussion
> >> title: Init responsibility of for EAP level reauthentication?
> >> ________________________________________________
> >> PANA Issues <pana_issues@danforsberg.info>
> >> http://danforsberg.info:8080/pana-issues/issue31
> >> ________________________________________________
> >> 
> >> _______________________________________________
> >> Pana mailing list
> >> Pana@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/pana
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> > 
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

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


From pana-admin@ietf.org  Mon Oct  6 14:22:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15765
	for <pana-archive@lists.ietf.org>; Mon, 6 Oct 2003 14:22:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6Zzd-0002yc-Bz; Mon, 06 Oct 2003 14:22:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6ZzD-0002yF-Cv
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 14:21:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15723
	for <pana@ietf.org>; Mon, 6 Oct 2003 14:21:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6Zyy-0001vb-00
	for pana@ietf.org; Mon, 06 Oct 2003 14:21:20 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6Zyx-0001vY-00
	for pana@ietf.org; Mon, 06 Oct 2003 14:21:19 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h96ILIF1005424;
	Tue, 7 Oct 2003 03:21:18 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h96ILJkl028302;
	Tue, 7 Oct 2003 03:21:19 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA28299 ; Tue, 7 Oct 2003 03:21:18 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA18301; Tue, 7 Oct 2003 03:21:18 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA24291; Tue, 7 Oct 2003 03:21:17 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h96ILHqT021521;
	Tue, 7 Oct 2003 03:21:17 +0900 (JST)
Received: from steelhead ([159.119.168.104]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMC00H1ZLNEN2@tsbpo1.po.toshiba.co.jp>; Tue,
 7 Oct 2003 03:21:16 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A6Zx3-00027f-00; Mon, 06 Oct 2003 11:19:21 -0700
Date: Mon, 06 Oct 2003 11:19:20 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D22@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20031006181920.GD5880@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D22@esebe008.ntc.nokia.com>
Subject: [Pana] Re: [issue24] AVP alignment
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

The new text looks fine.

Yoshihiro Ohba

On Thu, Oct 02, 2003 at 10:20:43AM +0300, Dan.Forsberg@nokia.com wrote:
> Yoshihiro,
> 
> I had this already in my "newest" message format section.
> 
> Br,
> - Dan
> 
> 
> Dan Forsberg <dan.forsberg@nokia.com> added the comment:
> 
> Change from:
> 
> 9.2 AVP Header 
>  
>        0                   1                   2                   3 
>        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |                           AVP Code                            | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |   AVP Flags   |                  AVP Length                   | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |                         Vendor-Id (opt)                       | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |    Data ... 
>       +-+-+-+-+-+-+-+-+ 
> 
> Change to:
> 
> 9.2 AVP Header 
> 
>    Each AVP of type OctetString MUST be padded to align on a 32-bit
>    boundary, while other AVP types align naturally. A number of zero-
>    valued bytes are added to the end of the AVP Data field till a word
>    boundary is reached. The length of the padding is not reflected in
>    the AVP Length field. [DIAMETER]
> 
>    The fields in the AVP header MUST be sent in network byte order. The
>    format of the header is:
> 
>        0                   1                   2                   3 
>        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |                           AVP Code                            | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |   AVP Flags   |                  AVP Length                   | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |                         Vendor-Id (opt)                       | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |    Data ... 
>       +-+-+-+-+-+-+-+-+
> 
> 
> ----------
> nosy:  -dforsber, yoshihiro
> ________________________________________________
> PANA Issues <pana_issues@danforsberg.info>
> http://danforsberg.info:8080/pana-issues/issue24
> ________________________________________________

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


From exim@www1.ietf.org  Mon Oct  6 14:22:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15780
	for <pana-archive@odin.ietf.org>; Mon, 6 Oct 2003 14:22:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6Zzg-0002zI-WB
	for pana-archive@odin.ietf.org; Mon, 06 Oct 2003 14:22:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h96IM4fj011478
	for pana-archive@odin.ietf.org; Mon, 6 Oct 2003 14:22:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6Zzg-0002z3-Qp
	for pana-web-archive@optimus.ietf.org; Mon, 06 Oct 2003 14:22:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15741
	for <pana-web-archive@ietf.org>; Mon, 6 Oct 2003 14:21:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6Zze-0001vx-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 14:22:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6Zzd-0001vu-00
	for pana-web-archive@ietf.org; Mon, 06 Oct 2003 14:22:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6Zzd-0002yc-Bz; Mon, 06 Oct 2003 14:22:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6ZzD-0002yF-Cv
	for pana@optimus.ietf.org; Mon, 06 Oct 2003 14:21:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15723
	for <pana@ietf.org>; Mon, 6 Oct 2003 14:21:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6Zyy-0001vb-00
	for pana@ietf.org; Mon, 06 Oct 2003 14:21:20 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6Zyx-0001vY-00
	for pana@ietf.org; Mon, 06 Oct 2003 14:21:19 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h96ILIF1005424;
	Tue, 7 Oct 2003 03:21:18 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h96ILJkl028302;
	Tue, 7 Oct 2003 03:21:19 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA28299 ; Tue, 7 Oct 2003 03:21:18 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA18301; Tue, 7 Oct 2003 03:21:18 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA24291; Tue, 7 Oct 2003 03:21:17 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h96ILHqT021521;
	Tue, 7 Oct 2003 03:21:17 +0900 (JST)
Received: from steelhead ([159.119.168.104]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMC00H1ZLNEN2@tsbpo1.po.toshiba.co.jp>; Tue,
 7 Oct 2003 03:21:16 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A6Zx3-00027f-00; Mon, 06 Oct 2003 11:19:21 -0700
Date: Mon, 06 Oct 2003 11:19:20 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D22@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20031006181920.GD5880@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D22@esebe008.ntc.nokia.com>
Subject: [Pana] Re: [issue24] AVP alignment
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

The new text looks fine.

Yoshihiro Ohba

On Thu, Oct 02, 2003 at 10:20:43AM +0300, Dan.Forsberg@nokia.com wrote:
> Yoshihiro,
> 
> I had this already in my "newest" message format section.
> 
> Br,
> - Dan
> 
> 
> Dan Forsberg <dan.forsberg@nokia.com> added the comment:
> 
> Change from:
> 
> 9.2 AVP Header 
>  
>        0                   1                   2                   3 
>        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |                           AVP Code                            | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |   AVP Flags   |                  AVP Length                   | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |                         Vendor-Id (opt)                       | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |    Data ... 
>       +-+-+-+-+-+-+-+-+ 
> 
> Change to:
> 
> 9.2 AVP Header 
> 
>    Each AVP of type OctetString MUST be padded to align on a 32-bit
>    boundary, while other AVP types align naturally. A number of zero-
>    valued bytes are added to the end of the AVP Data field till a word
>    boundary is reached. The length of the padding is not reflected in
>    the AVP Length field. [DIAMETER]
> 
>    The fields in the AVP header MUST be sent in network byte order. The
>    format of the header is:
> 
>        0                   1                   2                   3 
>        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |                           AVP Code                            | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |   AVP Flags   |                  AVP Length                   | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |                         Vendor-Id (opt)                       | 
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>       |    Data ... 
>       +-+-+-+-+-+-+-+-+
> 
> 
> ----------
> nosy:  -dforsber, yoshihiro
> ________________________________________________
> PANA Issues <pana_issues@danforsberg.info>
> http://danforsberg.info:8080/pana-issues/issue24
> ________________________________________________

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



From pana-request@research.telcordia.com  Mon Oct  6 17:16:02 2003
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22759
	for <pana-archive@lists.ietf.org>; Mon, 6 Oct 2003 17:15:56 -0400 (EDT)
Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8])
	by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id h96LAPes000735;
	Mon, 6 Oct 2003 17:10:25 -0400 (EDT)
Received: (from slmgr@localhost)
	by donner.research.telcordia.com (8.8.8/8.8.8) id RAA13654;
	Mon, 6 Oct 2003 17:10:25 -0400 (EDT)
Resent-Date: Mon, 6 Oct 2003 17:10:25 -0400 (EDT)
X-Authentication-Warning: donner.research.telcordia.com: slmgr set sender to pana-request@research.telcordia.com using -f
Old-Return-Path: <yohba@tari.toshiba.com>
Date: Mon, 06 Oct 2003 14:08:32 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: New [issue22] PANA Message Types
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6C66@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@research.telcordia.com
Message-id: <20031006210832.GB8492@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@research.telcordia.com
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6C66@esebe008.ntc.nokia.com>
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi)
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper)
Resent-Message-ID: <ZEydLB.A.NVD.Bpdg_@donner>
Resent-From: pana@research.telcordia.com
X-Mailing-List: <pana@research.telcordia.com> 
X-Loop: pana@research.telcordia.com
List-Post: <mailto:pana@research.telcordia.com>
List-Help: <mailto:pana-request@research.telcordia.com?subject=help>
Precedence: list
Resent-Sender: pana-request@research.telcordia.com

Here is the text on this issue (note that PANA-Bind-{Request,Answer}
may be renamed to PANA-Result-{Request,Answer} according to Issue 29).

---
In Section 9.3.4,

change:

      PANA-Start-Answer ::= < PANA-Header: 3 >

to:

      PANA-Start-Answer ::= < PANA-Header: 2 >

In section 9.3.5,

change:

      PANA-Auth-Request ::= < PANA-Header: 4, REQ >
                                                                                
to
                                                                                
      PANA-Auth-Request ::= < PANA-Header: 3, REQ >

In Section 9.3.6,

change:

      PANA-Auth-Answer ::= < PANA-Header: 5 >

to:

      PANA-Auth-Answer ::= < PANA-Header: 3 >

In Section 9.3.7,

change:

      PANA-Bind-Request ::= < PANA-Header: 6, REQ, [FIN] >

to:

      PANA-Bind-Request ::= < PANA-Header: 4, REQ, [FIN] >

In Section 9.3.8,

change:

      PANA-Bind-Answer ::= < PANA-Header: 7, [FIN] >

to:

      PANA-Bind-Answer ::= < PANA-Header: 4, [FIN] >

In Section 9.3.9,

change:

      PANA-Reauth-Request ::= < PANA-Header: 8, REQ > 

to:

      PANA-Reauth-Request ::= < PANA-Header: 5, REQ > 

In Section 9.3.10,

change:

      PANA-Reauth-Answer ::= < PANA-Header: 9 >

to:

      PANA-Reauth-Answer ::= < PANA-Header: 5 >

In Section 9.3.11,

change:

      PANA-Termination-Request ::= < PANA-Header: 10, REQ >

to: 

      PANA-Termination-Request ::= < PANA-Header: 6, REQ >

In Section 9.3.12,

change:

      PANA-Termination-Answer ::= < PANA-Header: 11 >

to:

      PANA-Termination-Answer ::= < PANA-Header: 6>
----

Regards,
Yoshihiro Ohba


On Wed, Aug 27, 2003 at 06:26:14PM +0300, Dan.Forsberg@nokia.com wrote:
> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> 
> Currently PANA requests and answers have different message types AND
> requests also use the REQ flag. This is redundant. 
> 
> PANA should use the same message type for request and answers and
> differentiate them with the REQ flag.
> 
> 
> ----------
> category: Technical
> document: draft-ietf-pana-pana-xx.txt
> messages: 73
> nosy: dforsber
> priority: Must Fix
> status: No Discussion
> title: PANA Message Types
> ________________________________________________
> PANA Issues <pana_issues@danforsberg.info>
> http://danforsberg.info:8080/pana-issues/issue22
> ________________________________________________
> 



From pana-admin@ietf.org  Tue Oct  7 00:31:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05362
	for <pana-archive@lists.ietf.org>; Tue, 7 Oct 2003 00:31:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6jUz-0001f2-ND; Tue, 07 Oct 2003 00:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6jUK-0001d0-RZ
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 00:30:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05331
	for <pana@ietf.org>; Tue, 7 Oct 2003 00:30:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6jUI-0000UJ-00
	for pana@ietf.org; Tue, 07 Oct 2003 00:30:18 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6jUH-0000UG-00
	for pana@ietf.org; Tue, 07 Oct 2003 00:30:17 -0400
Date: Mon, 06 Oct 2003 21:30:04 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
Message-ID: <BBA78F5C.9E97%alper@docomolabs-usa.com>
In-Reply-To: <003101c38c2c$4460f380$5a100a0a@adithya>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] EP information
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


From PANA-IPsec draft:


3.0 Pre-requisites for IPsec SA establisment
  
   This document assumes that the following have already happened before
   the IPSEC SA is established.
     
     1) PANA client (PaC) learns the IP address of the Enforcement point
        (EP) during the PANA exchange.

Currently we don't have this feature in PANA. I think we can handle this by:

- Having an AVP for carrying the DI of EP(s). We can add a new field (or
flag?) to current device-ID AVP to indicate whether it belongs to PAA or one
of the EPs.
- This AVP MUST be included in PANA-Bind-Request when L2 or L3 ciphering
will be enabled after PANA. There may be more than one such AVP at a time
(for multiple access routers, for example).
- The address type in this AVP MUST match the ciphering type.

Comments?

Alper



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


From exim@www1.ietf.org  Tue Oct  7 00:31:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05377
	for <pana-archive@odin.ietf.org>; Tue, 7 Oct 2003 00:31:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6jV2-0001g3-Qb
	for pana-archive@odin.ietf.org; Tue, 07 Oct 2003 00:31:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h974V4vj006441
	for pana-archive@odin.ietf.org; Tue, 7 Oct 2003 00:31:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6jV2-0001fo-Ld
	for pana-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 00:31:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05343
	for <pana-web-archive@ietf.org>; Tue, 7 Oct 2003 00:30:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6jV0-0000Uc-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 00:31:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6jUz-0000UZ-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 00:31:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6jUz-0001f2-ND; Tue, 07 Oct 2003 00:31:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6jUK-0001d0-RZ
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 00:30:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05331
	for <pana@ietf.org>; Tue, 7 Oct 2003 00:30:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6jUI-0000UJ-00
	for pana@ietf.org; Tue, 07 Oct 2003 00:30:18 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6jUH-0000UG-00
	for pana@ietf.org; Tue, 07 Oct 2003 00:30:17 -0400
Date: Mon, 06 Oct 2003 21:30:04 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
Message-ID: <BBA78F5C.9E97%alper@docomolabs-usa.com>
In-Reply-To: <003101c38c2c$4460f380$5a100a0a@adithya>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] EP information
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


From PANA-IPsec draft:


3.0 Pre-requisites for IPsec SA establisment
  
   This document assumes that the following have already happened before
   the IPSEC SA is established.
     
     1) PANA client (PaC) learns the IP address of the Enforcement point
        (EP) during the PANA exchange.

Currently we don't have this feature in PANA. I think we can handle this by:

- Having an AVP for carrying the DI of EP(s). We can add a new field (or
flag?) to current device-ID AVP to indicate whether it belongs to PAA or one
of the EPs.
- This AVP MUST be included in PANA-Bind-Request when L2 or L3 ciphering
will be enabled after PANA. There may be more than one such AVP at a time
(for multiple access routers, for example).
- The address type in this AVP MUST match the ciphering type.

Comments?

Alper



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



From pana-admin@ietf.org  Tue Oct  7 01:50:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07584
	for <pana-archive@lists.ietf.org>; Tue, 7 Oct 2003 01:50:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6kjS-0004vV-Ld; Tue, 07 Oct 2003 01:50:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6kiy-0004u0-DG
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 01:49:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07551
	for <pana@ietf.org>; Tue, 7 Oct 2003 01:49:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6kiv-0001Jj-00
	for pana@ietf.org; Tue, 07 Oct 2003 01:49:29 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6kiu-0001Jf-00
	for pana@ietf.org; Tue, 07 Oct 2003 01:49:28 -0400
Date: Mon, 06 Oct 2003 22:49:15 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
Message-ID: <BBA7A1EB.9EA0%alper@docomolabs-usa.com>
In-Reply-To: <003101c38c2c$4460f380$5a100a0a@adithya>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Issue 32
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

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

Proposed text changes are below... Comments welcome.


From:

   Since PAA and PaC are one IP hop away from each other, PANA messages
   can be filtered whenever messages arrive at interfaces where they
   are not expected.


To:

   Since PAA and PaC are supposed to be one IP hop away, a simple
   TTL check can prevent off-link attacks. Furthermore, additional
   filtering can be enabled on the EPs. An EP may be able to filter
   unauthorized PAA advertisements when they are received on the
   access side of the network where only PaCs are connected.


From:

   Hence an 
   adversary can both eavesdrop the EAP messages and is also able to
   inject arbitrary messages which might confuse both the PaC and the
   PAA. 

To:

   Hence an 
   adversary can both eavesdrop the EAP messages and is also able to
   inject arbitrary messages which might confuse both the EAP peer on PaC
   and the EAP authenticator or authentication server on the PAA.


From:

   For further discussion about the
   importance of the session key generation refer to the next
   subsection (c) about compound authentication.

To:

   For further discussion about the
   importance of the session key generation refer to the next
   subsection (d) about compound authentication.


From:

   For the current version of the document an Integrity
   object is defined which is based on Diameter objects. The Integrity
   Object supports data-origin authentication, replay protection based
   on sequence numbers and integrity protection based on a keyed
   message digest. Confidentiality protection is not provided. The
   session keys (one for each direction) used for this object has to be
   provided by the EAP method.

To:

   For the current version of the document an itegrity object (MAC AVP) is
   defined which supports data-origin authentication, replay protection
   based on sequence numbers and integrity protection based on a keyed
   message digest. Confidentiality protection is not provided. The
   session keys used for this object have to be provided by the EAP method.


From:

   Instead HMAC-SHA1 is used per-default.

To:

   Instead HMAC-SHA1 is used by default.


From:

   To select the 
   security association for signaling message protection the Session
   ID

To:

   To select the 
   security association for signaling message protection the Session
   ID is conveyed


From:

   If an entity (PAA or PaC) looses its state (especially the current
   sequence number) then the entire PANA protocol has to be restarted.

To:

   If an entity (PAA or PaC) loses its state (especially the current
   sequence number) then the entire PANA protocol has to be restarted.



From:

   The lifetime of the PANA SA has to be bound to the refresh interval
   with an additional tolerance period. To provide fast re-
   authentication a separate security association (e.g. one stored at
   the local AAA server) should be used. By fast re-authentication we
   mean a new PANA protocol execution which does not involve the entire
   AAA communication. The ability to trigger such a protocol execution
   depends on the given EAP method and on the policy of the local
   network requesting authentication.

To:

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



From:

   Furthermore, a 
   derived session key might help to create the pre-requisites for
   network layer protection (for example IPsec).

To:

   Furthermore, a 
   derived session key might help to create the pre-requisites for
   network-layer protection (for example IPsec [PANA-IPSEC]).

Add to references:

   [PANA-IPSEC] M. Parthasarathy: "PANA enabling IPsec based Access
   Control," Internet Draft, Internet Engineering Task Force, October 2003.
   Work in progress.


From:

   Network access authentication is done for a very specific purpose
   and often charging procedures are involved which allow restricting
   network resource usage based on some policies. In mobility
   environments it is always possible that an end host suddenly
   disconnects without transmitting a disconnect message. If network
   access authentication as part of PANA is executed only at the
   beginning then an adversary can gain advantage of the installed
   packet filters to submit and receive data packets.
    
   Also for the network operator it might be desirable to enforce a
   disconnect based on some external events (e.g. because of
   insufficient funds, etc.).
    
   An additional motivation for detecting a disconnected end host is
   the ability to release resources (i.e. garbage collection). The PAA
   can remove per-session state information including installed
   security association, packet filters etc.

To:

   Network access authentication is done for a very specific purpose
   and often charging procedures are involved which allow restricting
   network resource usage based on some policies. In mobility
   environments it is always possible that an end host suddenly
   disconnects without transmitting a disconnect message. Operators
   are generally motivated to detect a disconnected end host as soon
   as possible in order to release resources (i.e., garbage collection).
   The PAA  can remove per-session state information including installed
   security association, packet filters, etc.


From:

   h) Periodic refresh messages

   Different procedures can be used for disconnect indication. PANA
   cannot assume link layer disconnect indication. Hence this
   functionality has to be provided at a higher layer. With this
   version of the draft we suggest to apply the soft-state principle
   found at other protocols (such as RSVP). Soft-state means that
   session state is kept alive as long as refresh messages refresh the
   state. If no new refresh messages are provided then the state
   automatically times out and resources are released. This process
   includes stopping accounting procedures.
    
   Based on the different environments where PANA could be used it is
   difficult to fix a refresh interval. Hence a default refresh
   interval of 30 seconds is suggested. Additionally there is the
   possibility to negotiation this interval once the PANA security
   association is established. A policy at the PAA and the PaC would
   ensure that the refresh interval is selected with a value which is
   either too high or too low. There is certainly a tradeoff between
   the refresh interval and the bandwidth consumption. To reduce the
   bandwidth consumption a small PANA message consisting only of a
   session identifier and the Integrity object is used. The session
   identifier refers to the state that has to be refreshed. Some
   environments do not need PANA refresh messages to detect orphan
   states. For these environments the refresh interval should be set to
   zero which effectively disables the usage of refresh messages. In
   case of IPsec protection a dead-peer mechanism can be used to detect
   inactivity (see [HBR03]).
    
   From a security point of view an adversary must not be able to
   inject, modify or replay refresh messages nor must he be able to
   change the refresh interval (e.g. setting it to zero) without
   detection. Hence these messages experience cryptographic protection.


To:

   h) Liveness test
    
   Network access authentication is done for a very specific purpose
   and often charging procedures are involved which allow restricting
   network resource usage based on some policies. In mobility
   environments it is always possible that an end host suddenly
   disconnects without transmitting a disconnect message. Operators
   are generally motivated to detect a disconnected end host as soon
   as possible in order to release resources (i.e., garbage collection).
   The PAA can remove per-session state information including installed
   security association, packet filters, etc.

        
   Different procedures can be used for disconnect indication. PANA
   cannot assume link-layer disconnect indication. Hence this
   functionality has to be provided at a higher layer. With this
   version of the draft we suggest to apply the soft-state principle
   found at other protocols (such as RSVP). Soft-state means that
   session state is kept alive as long as refresh messages refresh the
   state. If no new refresh messages are provided then the state
   automatically times out and resources are released. This process
   includes stopping accounting procedures.
    
   A PANA session is associated with a session lifetime. The session
   is terminated unless it is refreshed by a new round of EAP authentication
   before it expires. Therefore, at the latest a disconnected client
   can be detected when its lifetime expires. A disconnect may also be
   detected earlier by using PANA reauthentication messages. A request
   message can be generated by either PaC or PAA at any time and the peer
   must respond with an answer message. A successful round-trip of this
   exchange is a simple verification that the peer is alive. This test
   can be engaged when there is a possibility that the peer might have
   disconnected (e.g., after discontinuation of data traffic). Periodic
   use of this exchange as a keep-alive requires additional care
   as it might result in congestion and hence false alarms. This exchange
   is cryptographically protected when PANA SA is available in order
   to prevent threats associated with the abuse of this functionality.


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


From exim@www1.ietf.org  Tue Oct  7 01:50:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07599
	for <pana-archive@odin.ietf.org>; Tue, 7 Oct 2003 01:50:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6kjW-0004w4-Fj
	for pana-archive@odin.ietf.org; Tue, 07 Oct 2003 01:50:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h975o6CX018973
	for pana-archive@odin.ietf.org; Tue, 7 Oct 2003 01:50:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6kjW-0004vw-8w
	for pana-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 01:50:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07567
	for <pana-web-archive@ietf.org>; Tue, 7 Oct 2003 01:49:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6kjS-0001Jz-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 01:50:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6kjS-0001Jw-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 01:50:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6kjS-0004vV-Ld; Tue, 07 Oct 2003 01:50:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6kiy-0004u0-DG
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 01:49:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07551
	for <pana@ietf.org>; Tue, 7 Oct 2003 01:49:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6kiv-0001Jj-00
	for pana@ietf.org; Tue, 07 Oct 2003 01:49:29 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6kiu-0001Jf-00
	for pana@ietf.org; Tue, 07 Oct 2003 01:49:28 -0400
Date: Mon, 06 Oct 2003 22:49:15 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
Message-ID: <BBA7A1EB.9EA0%alper@docomolabs-usa.com>
In-Reply-To: <003101c38c2c$4460f380$5a100a0a@adithya>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Issue 32
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

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

Proposed text changes are below... Comments welcome.


From:

   Since PAA and PaC are one IP hop away from each other, PANA messages
   can be filtered whenever messages arrive at interfaces where they
   are not expected.


To:

   Since PAA and PaC are supposed to be one IP hop away, a simple
   TTL check can prevent off-link attacks. Furthermore, additional
   filtering can be enabled on the EPs. An EP may be able to filter
   unauthorized PAA advertisements when they are received on the
   access side of the network where only PaCs are connected.


From:

   Hence an 
   adversary can both eavesdrop the EAP messages and is also able to
   inject arbitrary messages which might confuse both the PaC and the
   PAA. 

To:

   Hence an 
   adversary can both eavesdrop the EAP messages and is also able to
   inject arbitrary messages which might confuse both the EAP peer on PaC
   and the EAP authenticator or authentication server on the PAA.


From:

   For further discussion about the
   importance of the session key generation refer to the next
   subsection (c) about compound authentication.

To:

   For further discussion about the
   importance of the session key generation refer to the next
   subsection (d) about compound authentication.


From:

   For the current version of the document an Integrity
   object is defined which is based on Diameter objects. The Integrity
   Object supports data-origin authentication, replay protection based
   on sequence numbers and integrity protection based on a keyed
   message digest. Confidentiality protection is not provided. The
   session keys (one for each direction) used for this object has to be
   provided by the EAP method.

To:

   For the current version of the document an itegrity object (MAC AVP) is
   defined which supports data-origin authentication, replay protection
   based on sequence numbers and integrity protection based on a keyed
   message digest. Confidentiality protection is not provided. The
   session keys used for this object have to be provided by the EAP method.


From:

   Instead HMAC-SHA1 is used per-default.

To:

   Instead HMAC-SHA1 is used by default.


From:

   To select the 
   security association for signaling message protection the Session
   ID

To:

   To select the 
   security association for signaling message protection the Session
   ID is conveyed


From:

   If an entity (PAA or PaC) looses its state (especially the current
   sequence number) then the entire PANA protocol has to be restarted.

To:

   If an entity (PAA or PaC) loses its state (especially the current
   sequence number) then the entire PANA protocol has to be restarted.



From:

   The lifetime of the PANA SA has to be bound to the refresh interval
   with an additional tolerance period. To provide fast re-
   authentication a separate security association (e.g. one stored at
   the local AAA server) should be used. By fast re-authentication we
   mean a new PANA protocol execution which does not involve the entire
   AAA communication. The ability to trigger such a protocol execution
   depends on the given EAP method and on the policy of the local
   network requesting authentication.

To:

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



From:

   Furthermore, a 
   derived session key might help to create the pre-requisites for
   network layer protection (for example IPsec).

To:

   Furthermore, a 
   derived session key might help to create the pre-requisites for
   network-layer protection (for example IPsec [PANA-IPSEC]).

Add to references:

   [PANA-IPSEC] M. Parthasarathy: "PANA enabling IPsec based Access
   Control," Internet Draft, Internet Engineering Task Force, October 2003.
   Work in progress.


From:

   Network access authentication is done for a very specific purpose
   and often charging procedures are involved which allow restricting
   network resource usage based on some policies. In mobility
   environments it is always possible that an end host suddenly
   disconnects without transmitting a disconnect message. If network
   access authentication as part of PANA is executed only at the
   beginning then an adversary can gain advantage of the installed
   packet filters to submit and receive data packets.
    
   Also for the network operator it might be desirable to enforce a
   disconnect based on some external events (e.g. because of
   insufficient funds, etc.).
    
   An additional motivation for detecting a disconnected end host is
   the ability to release resources (i.e. garbage collection). The PAA
   can remove per-session state information including installed
   security association, packet filters etc.

To:

   Network access authentication is done for a very specific purpose
   and often charging procedures are involved which allow restricting
   network resource usage based on some policies. In mobility
   environments it is always possible that an end host suddenly
   disconnects without transmitting a disconnect message. Operators
   are generally motivated to detect a disconnected end host as soon
   as possible in order to release resources (i.e., garbage collection).
   The PAA  can remove per-session state information including installed
   security association, packet filters, etc.


From:

   h) Periodic refresh messages

   Different procedures can be used for disconnect indication. PANA
   cannot assume link layer disconnect indication. Hence this
   functionality has to be provided at a higher layer. With this
   version of the draft we suggest to apply the soft-state principle
   found at other protocols (such as RSVP). Soft-state means that
   session state is kept alive as long as refresh messages refresh the
   state. If no new refresh messages are provided then the state
   automatically times out and resources are released. This process
   includes stopping accounting procedures.
    
   Based on the different environments where PANA could be used it is
   difficult to fix a refresh interval. Hence a default refresh
   interval of 30 seconds is suggested. Additionally there is the
   possibility to negotiation this interval once the PANA security
   association is established. A policy at the PAA and the PaC would
   ensure that the refresh interval is selected with a value which is
   either too high or too low. There is certainly a tradeoff between
   the refresh interval and the bandwidth consumption. To reduce the
   bandwidth consumption a small PANA message consisting only of a
   session identifier and the Integrity object is used. The session
   identifier refers to the state that has to be refreshed. Some
   environments do not need PANA refresh messages to detect orphan
   states. For these environments the refresh interval should be set to
   zero which effectively disables the usage of refresh messages. In
   case of IPsec protection a dead-peer mechanism can be used to detect
   inactivity (see [HBR03]).
    
   From a security point of view an adversary must not be able to
   inject, modify or replay refresh messages nor must he be able to
   change the refresh interval (e.g. setting it to zero) without
   detection. Hence these messages experience cryptographic protection.


To:

   h) Liveness test
    
   Network access authentication is done for a very specific purpose
   and often charging procedures are involved which allow restricting
   network resource usage based on some policies. In mobility
   environments it is always possible that an end host suddenly
   disconnects without transmitting a disconnect message. Operators
   are generally motivated to detect a disconnected end host as soon
   as possible in order to release resources (i.e., garbage collection).
   The PAA can remove per-session state information including installed
   security association, packet filters, etc.

        
   Different procedures can be used for disconnect indication. PANA
   cannot assume link-layer disconnect indication. Hence this
   functionality has to be provided at a higher layer. With this
   version of the draft we suggest to apply the soft-state principle
   found at other protocols (such as RSVP). Soft-state means that
   session state is kept alive as long as refresh messages refresh the
   state. If no new refresh messages are provided then the state
   automatically times out and resources are released. This process
   includes stopping accounting procedures.
    
   A PANA session is associated with a session lifetime. The session
   is terminated unless it is refreshed by a new round of EAP authentication
   before it expires. Therefore, at the latest a disconnected client
   can be detected when its lifetime expires. A disconnect may also be
   detected earlier by using PANA reauthentication messages. A request
   message can be generated by either PaC or PAA at any time and the peer
   must respond with an answer message. A successful round-trip of this
   exchange is a simple verification that the peer is alive. This test
   can be engaged when there is a possibility that the peer might have
   disconnected (e.g., after discontinuation of data traffic). Periodic
   use of this exchange as a keep-alive requires additional care
   as it might result in congestion and hence false alarms. This exchange
   is cryptographically protected when PANA SA is available in order
   to prevent threats associated with the abuse of this functionality.


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



From pana-admin@ietf.org  Tue Oct  7 04:17:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22815
	for <pana-archive@lists.ietf.org>; Tue, 7 Oct 2003 04:17:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6n1h-0004qw-7i; Tue, 07 Oct 2003 04:17:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6n1P-0004qP-JG
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 04:16:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22808
	for <pana@ietf.org>; Tue, 7 Oct 2003 04:16:34 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6n1M-0002Wg-00
	for pana@ietf.org; Tue, 07 Oct 2003 04:16:40 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6n1L-0002Wd-00
	for pana@ietf.org; Tue, 07 Oct 2003 04:16:39 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h978Gd628106
	for <pana@ietf.org>; Tue, 7 Oct 2003 11:16:39 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6522ac1213ac158f250bc@esvir05nok.ntc.nokia.com>;
 Tue, 7 Oct 2003 11:16:39 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 7 Oct 2003 11:16:38 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue19] Result-Code AVP values?
Date: Tue, 7 Oct 2003 11:16:30 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D42@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOMJ72zBRSbrndGShSeWY3LwRIaMAAg1C3Q
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 07 Oct 2003 08:16:38.0973 (UTC) FILETIME=[54FDEED0:01C38CAB]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 06 October, 2003 19:34
> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>=20
>=20
> > Ok. So do you want to say that realm based routing is outside
> > the scope of PANA and in error case NAS must inform PaC in some
> > other means than PANA protocol?
>=20
> Yes, I'm thinking that this should be happening transparent to PANA.
>=20
> > I don't mind taking this error
> > case away. Anyway, I'm curious of how 802.1X does handle this
> > case?
>=20
> I think this is also an EAP question. What would be the EAP=20
> behavior when
> the NAS cannot recognize the EAP client identifier?

You tell me?

- Dan

>=20
> From your other message:
> > Just one more comment. The usage scenarios document chapter 3
> > (problem statement) says that the authentication agent (PAA)
> > chooses the backend authentication server based on the identity,
> > for example NAI..
>=20
> If we were to expand "the authentication agent" from that=20
> text, actually it
> should be the "NAS" (draft-ietf-aaa-eap) implementation which=20
> needs to deal
> with AAA routing, not "PAA."
>=20
> Alper
>=20
>=20
>=20
>=20
> >=20
> > - Dan
> >=20
> >> -----Original Message-----
> >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> >> Sent: 02 October, 2003 20:31
> >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> >>=20
> >>=20
> >>>>>        PANA_REALM_NOT_SERVED                   3003
> >>>>>           Error code from PAA to PaC.  The network
> >> doesn't recognize
> >>>>>           the realm.
> >>>>=20
> >>>> We don't have a place where PaC sends the realm information.
> >>>> So, I can't see
> >>>> where such an error would be returned to the PaC.
> >>>=20
> >>> The EAP-Response/Identity contains the realm if it is required. Or
> >>> should we create a NAI AVP, that contains only the realm? Realm is
> >>> needed to route the packet to the right AAA backend. If PAA
> >>> functionality doesn't check the realm, NAS or for example=20
> the local
> >>> AAA proxy will do it. But in the case of unknown realm the client
> >>> should be notified.
> >>=20
> >> I should have said "We don't have a place where PaC sends the realm
> >> information in PANA." You are right that EAP client ID can
> >> have this, but
> >> than it is the responsibility of EAP or EAP method to deal
> >> with this. This
> >> error case should not leak into PANA.
> >>=20
> >> Alper
> >>=20
> >>=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
> >=20
>=20
>=20

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


From exim@www1.ietf.org  Tue Oct  7 04:17:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22830
	for <pana-archive@odin.ietf.org>; Tue, 7 Oct 2003 04:17:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6n1q-0004rh-OV
	for pana-archive@odin.ietf.org; Tue, 07 Oct 2003 04:17:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h978HAsW018700
	for pana-archive@odin.ietf.org; Tue, 7 Oct 2003 04:17:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6n1q-0004rX-4x
	for pana-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 04:17:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22812
	for <pana-web-archive@ietf.org>; Tue, 7 Oct 2003 04:17:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6n1n-0002Wm-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 04:17:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6n1n-0002Wj-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 04:17:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6n1h-0004qw-7i; Tue, 07 Oct 2003 04:17:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6n1P-0004qP-JG
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 04:16:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22808
	for <pana@ietf.org>; Tue, 7 Oct 2003 04:16:34 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6n1M-0002Wg-00
	for pana@ietf.org; Tue, 07 Oct 2003 04:16:40 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6n1L-0002Wd-00
	for pana@ietf.org; Tue, 07 Oct 2003 04:16:39 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h978Gd628106
	for <pana@ietf.org>; Tue, 7 Oct 2003 11:16:39 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6522ac1213ac158f250bc@esvir05nok.ntc.nokia.com>;
 Tue, 7 Oct 2003 11:16:39 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 7 Oct 2003 11:16:38 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue19] Result-Code AVP values?
Date: Tue, 7 Oct 2003 11:16:30 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D42@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOMJ72zBRSbrndGShSeWY3LwRIaMAAg1C3Q
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 07 Oct 2003 08:16:38.0973 (UTC) FILETIME=[54FDEED0:01C38CAB]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 06 October, 2003 19:34
> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>=20
>=20
> > Ok. So do you want to say that realm based routing is outside
> > the scope of PANA and in error case NAS must inform PaC in some
> > other means than PANA protocol?
>=20
> Yes, I'm thinking that this should be happening transparent to PANA.
>=20
> > I don't mind taking this error
> > case away. Anyway, I'm curious of how 802.1X does handle this
> > case?
>=20
> I think this is also an EAP question. What would be the EAP=20
> behavior when
> the NAS cannot recognize the EAP client identifier?

You tell me?

- Dan

>=20
> From your other message:
> > Just one more comment. The usage scenarios document chapter 3
> > (problem statement) says that the authentication agent (PAA)
> > chooses the backend authentication server based on the identity,
> > for example NAI..
>=20
> If we were to expand "the authentication agent" from that=20
> text, actually it
> should be the "NAS" (draft-ietf-aaa-eap) implementation which=20
> needs to deal
> with AAA routing, not "PAA."
>=20
> Alper
>=20
>=20
>=20
>=20
> >=20
> > - Dan
> >=20
> >> -----Original Message-----
> >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> >> Sent: 02 October, 2003 20:31
> >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> >>=20
> >>=20
> >>>>>        PANA_REALM_NOT_SERVED                   3003
> >>>>>           Error code from PAA to PaC.  The network
> >> doesn't recognize
> >>>>>           the realm.
> >>>>=20
> >>>> We don't have a place where PaC sends the realm information.
> >>>> So, I can't see
> >>>> where such an error would be returned to the PaC.
> >>>=20
> >>> The EAP-Response/Identity contains the realm if it is required. Or
> >>> should we create a NAI AVP, that contains only the realm? Realm is
> >>> needed to route the packet to the right AAA backend. If PAA
> >>> functionality doesn't check the realm, NAS or for example=20
> the local
> >>> AAA proxy will do it. But in the case of unknown realm the client
> >>> should be notified.
> >>=20
> >> I should have said "We don't have a place where PaC sends the realm
> >> information in PANA." You are right that EAP client ID can
> >> have this, but
> >> than it is the responsibility of EAP or EAP method to deal
> >> with this. This
> >> error case should not leak into PANA.
> >>=20
> >> Alper
> >>=20
> >>=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
> >=20
>=20
>=20

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



From pana-admin@ietf.org  Tue Oct  7 09:03:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29767
	for <pana-archive@lists.ietf.org>; Tue, 7 Oct 2003 09:03:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6rUS-0007mu-PB; Tue, 07 Oct 2003 09:03:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6rUQ-0007mh-H3
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 09:02:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29729
	for <pana@ietf.org>; Tue, 7 Oct 2003 09:02:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6rUO-00055y-00
	for pana@ietf.org; Tue, 07 Oct 2003 09:02:56 -0400
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6rUO-00055i-00
	for pana@ietf.org; Tue, 07 Oct 2003 09:02:56 -0400
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP
	id 38F4134A7F; Tue,  7 Oct 2003 15:00:53 +0200 (CEST)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id 92A513F40C; Tue,  7 Oct 2003 15:20:47 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003100715005323826
 ; Tue, 07 Oct 2003 15:00:53 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id 3F04A3F40C; Tue,  7 Oct 2003 15:20:47 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1A6rS0-000ECL-Uu; Tue, 07 Oct 2003 15:00:28 +0200
Date: Tue, 7 Oct 2003 15:00:28 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: pana@ietf.org
Subject: Re: [Pana] Issue 30
Message-ID: <20031007130028.GB54532@ipv6-5.int-evry.fr>
References: <20031002105839.GC38817@ipv6-5.int-evry.fr> <BBA1BC45.9ADB%alper@docomolabs-usa.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BBA1BC45.9ADB%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi alper,

On Thu, Oct 02, 2003 at 11:28:05AM -0700, Alper Yegin wrote:
> Hi Julien,
> 
> > I just want to note that if we use this mechanism we need a way to
> > to change the session-id. Actually at the second handover the third PAA
> > won't be able to retrieve the second PAA's identity.
> 
> Good point. How about if we immediately assign a new session-id on the new
> link. Please see below for another revision on the text:

it seems ok, 

thanks,

-- 
julien.bournelle@int-evry.fr

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


From exim@www1.ietf.org  Tue Oct  7 09:03:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29785
	for <pana-archive@odin.ietf.org>; Tue, 7 Oct 2003 09:03:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6rUc-0007ne-PR
	for pana-archive@odin.ietf.org; Tue, 07 Oct 2003 09:03:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h97D3AbD029979
	for pana-archive@odin.ietf.org; Tue, 7 Oct 2003 09:03:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6rUc-0007nS-GL
	for pana-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 09:03:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29752
	for <pana-web-archive@ietf.org>; Tue, 7 Oct 2003 09:03:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6rUb-00056H-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 09:03:09 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6rUa-00056D-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 09:03:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6rUS-0007mu-PB; Tue, 07 Oct 2003 09:03:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6rUQ-0007mh-H3
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 09:02:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29729
	for <pana@ietf.org>; Tue, 7 Oct 2003 09:02:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6rUO-00055y-00
	for pana@ietf.org; Tue, 07 Oct 2003 09:02:56 -0400
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6rUO-00055i-00
	for pana@ietf.org; Tue, 07 Oct 2003 09:02:56 -0400
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP
	id 38F4134A7F; Tue,  7 Oct 2003 15:00:53 +0200 (CEST)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id 92A513F40C; Tue,  7 Oct 2003 15:20:47 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003100715005323826
 ; Tue, 07 Oct 2003 15:00:53 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id 3F04A3F40C; Tue,  7 Oct 2003 15:20:47 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1A6rS0-000ECL-Uu; Tue, 07 Oct 2003 15:00:28 +0200
Date: Tue, 7 Oct 2003 15:00:28 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: pana@ietf.org
Subject: Re: [Pana] Issue 30
Message-ID: <20031007130028.GB54532@ipv6-5.int-evry.fr>
References: <20031002105839.GC38817@ipv6-5.int-evry.fr> <BBA1BC45.9ADB%alper@docomolabs-usa.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BBA1BC45.9ADB%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi alper,

On Thu, Oct 02, 2003 at 11:28:05AM -0700, Alper Yegin wrote:
> Hi Julien,
> 
> > I just want to note that if we use this mechanism we need a way to
> > to change the session-id. Actually at the second handover the third PAA
> > won't be able to retrieve the second PAA's identity.
> 
> Good point. How about if we immediately assign a new session-id on the new
> link. Please see below for another revision on the text:

it seems ok, 

thanks,

-- 
julien.bournelle@int-evry.fr

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



From pana-admin@ietf.org  Tue Oct  7 09:18:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00517
	for <pana-archive@lists.ietf.org>; Tue, 7 Oct 2003 09:18:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6riz-0008QV-80; Tue, 07 Oct 2003 09:18:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6rix-0008QA-VR
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 09:18:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00492
	for <pana@ietf.org>; Tue, 7 Oct 2003 09:17:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6riw-0005LW-00
	for pana@ietf.org; Tue, 07 Oct 2003 09:17:58 -0400
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6riv-0005Kv-00
	for pana@ietf.org; Tue, 07 Oct 2003 09:17:57 -0400
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP
	id 520C734F3C; Tue,  7 Oct 2003 15:13:19 +0200 (CEST)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id D859B3F424; Tue,  7 Oct 2003 15:33:13 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003100715131908070
 ; Tue, 07 Oct 2003 15:13:19 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id AF74E3F424; Tue,  7 Oct 2003 15:33:13 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1A6re3-000ED2-6t; Tue, 07 Oct 2003 15:12:55 +0200
Date: Tue, 7 Oct 2003 15:12:55 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Dan.Forsberg@nokia.com
Cc: alper@docomolabs-usa.com, pana@ietf.org
Subject: Re: [Pana] [issue19] Result-Code AVP values?
Message-ID: <20031007131255.GC54532@ipv6-5.int-evry.fr>
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D37@esebe008.ntc.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6D37@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi,


On Mon, Oct 06, 2003 at 04:06:22PM +0300, Dan.Forsberg@nokia.com wrote:
> Just one more comment. The usage scenarios document chapter 3 
> (problem statement) says that the authentication agent (PAA) 
> chooses the backend authentication server based on the identity, 
> for example NAI..

If we use Diameter as a backend authentication server, I guess that it
is the AAA server that say that it can't  authenticate a user from a 
particular realm.
So in this case, the PAA receives a message from the AAA server
explaining the problem. As such the PAA can respond with a Result-Code
PANA_REALM_NOT_SERVED.

Am I missing something ?

-- 
julien.bournelle@int-evry.fr

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


From exim@www1.ietf.org  Tue Oct  7 09:18:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00534
	for <pana-archive@odin.ietf.org>; Tue, 7 Oct 2003 09:18:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6rj1-0008SY-Sl
	for pana-archive@odin.ietf.org; Tue, 07 Oct 2003 09:18:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h97DI3dE032487
	for pana-archive@odin.ietf.org; Tue, 7 Oct 2003 09:18:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6rj1-0008R1-LC
	for pana-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 09:18:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00500
	for <pana-web-archive@ietf.org>; Tue, 7 Oct 2003 09:17:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6rj0-0005Li-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 09:18:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6riz-0005Lf-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 09:18:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6riz-0008QV-80; Tue, 07 Oct 2003 09:18:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6rix-0008QA-VR
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 09:18:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00492
	for <pana@ietf.org>; Tue, 7 Oct 2003 09:17:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6riw-0005LW-00
	for pana@ietf.org; Tue, 07 Oct 2003 09:17:58 -0400
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6riv-0005Kv-00
	for pana@ietf.org; Tue, 07 Oct 2003 09:17:57 -0400
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP
	id 520C734F3C; Tue,  7 Oct 2003 15:13:19 +0200 (CEST)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP
	id D859B3F424; Tue,  7 Oct 2003 15:33:13 +0200 (CEST)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003100715131908070
 ; Tue, 07 Oct 2003 15:13:19 +0200
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP
	id AF74E3F424; Tue,  7 Oct 2003 15:33:13 +0200 (CEST)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1A6re3-000ED2-6t; Tue, 07 Oct 2003 15:12:55 +0200
Date: Tue, 7 Oct 2003 15:12:55 +0200
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Dan.Forsberg@nokia.com
Cc: alper@docomolabs-usa.com, pana@ietf.org
Subject: Re: [Pana] [issue19] Result-Code AVP values?
Message-ID: <20031007131255.GC54532@ipv6-5.int-evry.fr>
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D37@esebe008.ntc.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6D37@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi,


On Mon, Oct 06, 2003 at 04:06:22PM +0300, Dan.Forsberg@nokia.com wrote:
> Just one more comment. The usage scenarios document chapter 3 
> (problem statement) says that the authentication agent (PAA) 
> chooses the backend authentication server based on the identity, 
> for example NAI..

If we use Diameter as a backend authentication server, I guess that it
is the AAA server that say that it can't  authenticate a user from a 
particular realm.
So in this case, the PAA receives a message from the AAA server
explaining the problem. As such the PAA can respond with a Result-Code
PANA_REALM_NOT_SERVED.

Am I missing something ?

-- 
julien.bournelle@int-evry.fr

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



From pana-admin@ietf.org  Tue Oct  7 13:55:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13765
	for <pana-archive@lists.ietf.org>; Tue, 7 Oct 2003 13:55:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w34-00066I-4H; Tue, 07 Oct 2003 13:55:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w2t-00063d-T4
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 13:54:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13666
	for <pana@ietf.org>; Tue, 7 Oct 2003 13:54:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w2r-0001P0-00
	for pana@ietf.org; Tue, 07 Oct 2003 13:54:49 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w2p-0001Ox-00
	for pana@ietf.org; Tue, 07 Oct 2003 13:54:48 -0400
Date: Tue, 07 Oct 2003 10:54:32 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBA84BE8.9F6C%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6D42@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

>> I think this is also an EAP question. What would be the EAP
>> behavior when
>> the NAS cannot recognize the EAP client identifier?

I think this case would be handled by the following text from the EAP spec:

         Implementation Note: The peer MAY obtain the Identity via user
         input.  It is suggested that the authenticator retry the
         Identity Request in the case of an invalid Identity or
         authentication failure to allow for potential typos on the part
         of the user.  It is suggested that the Identity Request be
         retried a minimum of 3 times before terminating the
         authentication.  The Notification Request MAY be used to
         indicate an invalid authentication attempt prior to
         transmitting a new Identity Request (optionally, the failure
         MAY be indicated within the message of the new Identity Request
         itself).

... And finally I think the EAP authenticator would send a Failure message.

Alper



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


From exim@www1.ietf.org  Tue Oct  7 13:55:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13781
	for <pana-archive@odin.ietf.org>; Tue, 7 Oct 2003 13:55:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w3F-00067R-3n
	for pana-archive@odin.ietf.org; Tue, 07 Oct 2003 13:55:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h97HtD4i023517
	for pana-archive@odin.ietf.org; Tue, 7 Oct 2003 13:55:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w3E-00067E-U3
	for pana-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 13:55:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13726
	for <pana-web-archive@ietf.org>; Tue, 7 Oct 2003 13:55:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w3C-0001Q9-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 13:55:10 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w3C-0001Q6-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 13:55:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w34-00066I-4H; Tue, 07 Oct 2003 13:55:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w2t-00063d-T4
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 13:54:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13666
	for <pana@ietf.org>; Tue, 7 Oct 2003 13:54:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w2r-0001P0-00
	for pana@ietf.org; Tue, 07 Oct 2003 13:54:49 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w2p-0001Ox-00
	for pana@ietf.org; Tue, 07 Oct 2003 13:54:48 -0400
Date: Tue, 07 Oct 2003 10:54:32 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBA84BE8.9F6C%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6D42@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>> I think this is also an EAP question. What would be the EAP
>> behavior when
>> the NAS cannot recognize the EAP client identifier?

I think this case would be handled by the following text from the EAP spec:

         Implementation Note: The peer MAY obtain the Identity via user
         input.  It is suggested that the authenticator retry the
         Identity Request in the case of an invalid Identity or
         authentication failure to allow for potential typos on the part
         of the user.  It is suggested that the Identity Request be
         retried a minimum of 3 times before terminating the
         authentication.  The Notification Request MAY be used to
         indicate an invalid authentication attempt prior to
         transmitting a new Identity Request (optionally, the failure
         MAY be indicated within the message of the new Identity Request
         itself).

... And finally I think the EAP authenticator would send a Failure message.

Alper



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



From exim@www1.ietf.org  Tue Oct  7 13:56:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13848
	for <pana-archive@odin.ietf.org>; Tue, 7 Oct 2003 13:56:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w42-0006EC-0C
	for pana-archive@odin.ietf.org; Tue, 07 Oct 2003 13:56:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h97Hu12G023934
	for pana-archive@odin.ietf.org; Tue, 7 Oct 2003 13:56:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w41-0006Dx-SB
	for pana-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 13:56:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13817
	for <pana-web-archive@ietf.org>; Tue, 7 Oct 2003 13:55:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w3z-0001Rf-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 13:55:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w3z-0001Rc-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 13:55:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w40-0006B5-ML; Tue, 07 Oct 2003 13:56:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w3E-000679-GT
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 13:55:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13723
	for <pana@ietf.org>; Tue, 7 Oct 2003 13:55:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w3C-0001Q3-00
	for pana@ietf.org; Tue, 07 Oct 2003 13:55:10 -0400
Received: from smtp002.mail.ukl.yahoo.com ([217.12.11.33])
	by ietf-mx with smtp (Exim 4.12)
	id 1A6w3B-0001Op-00
	for pana@ietf.org; Tue, 07 Oct 2003 13:55:09 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp1.mail.vip.ukl.yahoo.com with SMTP; 7 Oct 2003 17:06:42 -0000
Message-ID: <001901c38cf5$663ce990$5a100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Alper Yegin" <alper@docomolabs-usa.com>, <pana@ietf.org>
References: <BBA78F5C.9E97%alper@docomolabs-usa.com>
Subject: Re: [Pana] EP information
Date: Tue, 7 Oct 2003 10:06:38 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


>
> From PANA-IPsec draft:
>
>
> 3.0 Pre-requisites for IPsec SA establisment
>
>    This document assumes that the following have already happened before
>    the IPSEC SA is established.
>
>      1) PANA client (PaC) learns the IP address of the Enforcement point
>         (EP) during the PANA exchange.
>
> Currently we don't have this feature in PANA. I think we can handle this
by:
>
> - Having an AVP for carrying the DI of EP(s). We can add a new field (or
> flag?) to current device-ID AVP to indicate whether it belongs to PAA or
one
> of the EPs.
> - This AVP MUST be included in PANA-Bind-Request when L2 or L3 ciphering
> will be enabled after PANA. There may be more than one such AVP at a time
> (for multiple access routers, for example).
> - The address type in this AVP MUST match the ciphering type.
>
> Comments?
>
Sounds okay.

-mohan

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


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



From pana-admin@ietf.org  Tue Oct  7 14:01:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14179
	for <pana-archive@lists.ietf.org>; Tue, 7 Oct 2003 14:01:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w8r-0006Sc-GD; Tue, 07 Oct 2003 14:01:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w8L-0006Ri-If
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 14:00:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14097
	for <pana@ietf.org>; Tue, 7 Oct 2003 14:00:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w8J-0001Wa-00
	for pana@ietf.org; Tue, 07 Oct 2003 14:00:27 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w8I-0001WR-00
	for pana@ietf.org; Tue, 07 Oct 2003 14:00:26 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h97I0LF1013294;
	Wed, 8 Oct 2003 03:00:21 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h97I0LOp020202;
	Wed, 8 Oct 2003 03:00:21 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA20200 ; Wed, 8 Oct 2003 03:00:21 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA10808; Wed, 8 Oct 2003 03:00:20 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA14917; Wed, 8 Oct 2003 03:00:20 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h97I0JqT012414;
	Wed, 8 Oct 2003 03:00:19 +0900 (JST)
Received: from steelhead ([159.119.168.86]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HME005LMFCGRW@tsbpo1.po.toshiba.co.jp>; Wed,
 8 Oct 2003 03:00:18 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A6w6z-0003uq-00; Tue, 07 Oct 2003 10:59:05 -0700
Date: Tue, 07 Oct 2003 10:59:04 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 32
In-reply-to: <BBA7A1EB.9EA0%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: pana@ietf.org
Message-id: <20031007175904.GB14458@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <003101c38c2c$4460f380$5a100a0a@adithya>
 <BBA7A1EB.9EA0%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>


The new text looks good, except that there is some duplicate text in
section h).

Yoshihiro Ohba


On Mon, Oct 06, 2003 at 10:49:15PM -0700, Alper Yegin wrote:
> http://danforsberg.info:8080/pana-issues/issue32
> 
> Proposed text changes are below... Comments welcome.
> 
> 
> From:
> 
>    Since PAA and PaC are one IP hop away from each other, PANA messages
>    can be filtered whenever messages arrive at interfaces where they
>    are not expected.
> 
> 
> To:
> 
>    Since PAA and PaC are supposed to be one IP hop away, a simple
>    TTL check can prevent off-link attacks. Furthermore, additional
>    filtering can be enabled on the EPs. An EP may be able to filter
>    unauthorized PAA advertisements when they are received on the
>    access side of the network where only PaCs are connected.
> 
> 
> From:
> 
>    Hence an 
>    adversary can both eavesdrop the EAP messages and is also able to
>    inject arbitrary messages which might confuse both the PaC and the
>    PAA. 
> 
> To:
> 
>    Hence an 
>    adversary can both eavesdrop the EAP messages and is also able to
>    inject arbitrary messages which might confuse both the EAP peer on PaC
>    and the EAP authenticator or authentication server on the PAA.
> 
> 
> From:
> 
>    For further discussion about the
>    importance of the session key generation refer to the next
>    subsection (c) about compound authentication.
> 
> To:
> 
>    For further discussion about the
>    importance of the session key generation refer to the next
>    subsection (d) about compound authentication.
> 
> 
> From:
> 
>    For the current version of the document an Integrity
>    object is defined which is based on Diameter objects. The Integrity
>    Object supports data-origin authentication, replay protection based
>    on sequence numbers and integrity protection based on a keyed
>    message digest. Confidentiality protection is not provided. The
>    session keys (one for each direction) used for this object has to be
>    provided by the EAP method.
> 
> To:
> 
>    For the current version of the document an itegrity object (MAC AVP) is
>    defined which supports data-origin authentication, replay protection
>    based on sequence numbers and integrity protection based on a keyed
>    message digest. Confidentiality protection is not provided. The
>    session keys used for this object have to be provided by the EAP method.
> 
> 
> From:
> 
>    Instead HMAC-SHA1 is used per-default.
> 
> To:
> 
>    Instead HMAC-SHA1 is used by default.
> 
> 
> From:
> 
>    To select the 
>    security association for signaling message protection the Session
>    ID
> 
> To:
> 
>    To select the 
>    security association for signaling message protection the Session
>    ID is conveyed
> 
> 
> From:
> 
>    If an entity (PAA or PaC) looses its state (especially the current
>    sequence number) then the entire PANA protocol has to be restarted.
> 
> To:
> 
>    If an entity (PAA or PaC) loses its state (especially the current
>    sequence number) then the entire PANA protocol has to be restarted.
> 
> 
> 
> From:
> 
>    The lifetime of the PANA SA has to be bound to the refresh interval
>    with an additional tolerance period. To provide fast re-
>    authentication a separate security association (e.g. one stored at
>    the local AAA server) should be used. By fast re-authentication we
>    mean a new PANA protocol execution which does not involve the entire
>    AAA communication. The ability to trigger such a protocol execution
>    depends on the given EAP method and on the policy of the local
>    network requesting authentication.
> 
> To:
> 
>    The lifetime of the PANA SA has to be bound to the AAA-authorized
>    session lifetime with an additional tolerance period. Unless PANA state
>    is updated by executing another EAP authentication, PANA SA is removed
>    when the current session expires.
> 
> 
> 
> From:
> 
>    Furthermore, a 
>    derived session key might help to create the pre-requisites for
>    network layer protection (for example IPsec).
> 
> To:
> 
>    Furthermore, a 
>    derived session key might help to create the pre-requisites for
>    network-layer protection (for example IPsec [PANA-IPSEC]).
> 
> Add to references:
> 
>    [PANA-IPSEC] M. Parthasarathy: "PANA enabling IPsec based Access
>    Control," Internet Draft, Internet Engineering Task Force, October 2003.
>    Work in progress.
> 
> 
> From:
> 
>    Network access authentication is done for a very specific purpose
>    and often charging procedures are involved which allow restricting
>    network resource usage based on some policies. In mobility
>    environments it is always possible that an end host suddenly
>    disconnects without transmitting a disconnect message. If network
>    access authentication as part of PANA is executed only at the
>    beginning then an adversary can gain advantage of the installed
>    packet filters to submit and receive data packets.
>     
>    Also for the network operator it might be desirable to enforce a
>    disconnect based on some external events (e.g. because of
>    insufficient funds, etc.).
>     
>    An additional motivation for detecting a disconnected end host is
>    the ability to release resources (i.e. garbage collection). The PAA
>    can remove per-session state information including installed
>    security association, packet filters etc.
> 
> To:
> 
>    Network access authentication is done for a very specific purpose
>    and often charging procedures are involved which allow restricting
>    network resource usage based on some policies. In mobility
>    environments it is always possible that an end host suddenly
>    disconnects without transmitting a disconnect message. Operators
>    are generally motivated to detect a disconnected end host as soon
>    as possible in order to release resources (i.e., garbage collection).
>    The PAA  can remove per-session state information including installed
>    security association, packet filters, etc.
> 
> 
> From:
> 
>    h) Periodic refresh messages
> 
>    Different procedures can be used for disconnect indication. PANA
>    cannot assume link layer disconnect indication. Hence this
>    functionality has to be provided at a higher layer. With this
>    version of the draft we suggest to apply the soft-state principle
>    found at other protocols (such as RSVP). Soft-state means that
>    session state is kept alive as long as refresh messages refresh the
>    state. If no new refresh messages are provided then the state
>    automatically times out and resources are released. This process
>    includes stopping accounting procedures.
>     
>    Based on the different environments where PANA could be used it is
>    difficult to fix a refresh interval. Hence a default refresh
>    interval of 30 seconds is suggested. Additionally there is the
>    possibility to negotiation this interval once the PANA security
>    association is established. A policy at the PAA and the PaC would
>    ensure that the refresh interval is selected with a value which is
>    either too high or too low. There is certainly a tradeoff between
>    the refresh interval and the bandwidth consumption. To reduce the
>    bandwidth consumption a small PANA message consisting only of a
>    session identifier and the Integrity object is used. The session
>    identifier refers to the state that has to be refreshed. Some
>    environments do not need PANA refresh messages to detect orphan
>    states. For these environments the refresh interval should be set to
>    zero which effectively disables the usage of refresh messages. In
>    case of IPsec protection a dead-peer mechanism can be used to detect
>    inactivity (see [HBR03]).
>     
>    From a security point of view an adversary must not be able to
>    inject, modify or replay refresh messages nor must he be able to
>    change the refresh interval (e.g. setting it to zero) without
>    detection. Hence these messages experience cryptographic protection.
> 
> 
> To:
> 
>    h) Liveness test
>     
>    Network access authentication is done for a very specific purpose
>    and often charging procedures are involved which allow restricting
>    network resource usage based on some policies. In mobility
>    environments it is always possible that an end host suddenly
>    disconnects without transmitting a disconnect message. Operators
>    are generally motivated to detect a disconnected end host as soon
>    as possible in order to release resources (i.e., garbage collection).
>    The PAA can remove per-session state information including installed
>    security association, packet filters, etc.
> 
>         
>    Different procedures can be used for disconnect indication. PANA
>    cannot assume link-layer disconnect indication. Hence this
>    functionality has to be provided at a higher layer. With this
>    version of the draft we suggest to apply the soft-state principle
>    found at other protocols (such as RSVP). Soft-state means that
>    session state is kept alive as long as refresh messages refresh the
>    state. If no new refresh messages are provided then the state
>    automatically times out and resources are released. This process
>    includes stopping accounting procedures.
>     
>    A PANA session is associated with a session lifetime. The session
>    is terminated unless it is refreshed by a new round of EAP authentication
>    before it expires. Therefore, at the latest a disconnected client
>    can be detected when its lifetime expires. A disconnect may also be
>    detected earlier by using PANA reauthentication messages. A request
>    message can be generated by either PaC or PAA at any time and the peer
>    must respond with an answer message. A successful round-trip of this
>    exchange is a simple verification that the peer is alive. This test
>    can be engaged when there is a possibility that the peer might have
>    disconnected (e.g., after discontinuation of data traffic). Periodic
>    use of this exchange as a keep-alive requires additional care
>    as it might result in congestion and hence false alarms. This exchange
>    is cryptographically protected when PANA SA is available in order
>    to prevent threats associated with the abuse of this functionality.
> 
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Tue Oct  7 14:01:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14194
	for <pana-archive@odin.ietf.org>; Tue, 7 Oct 2003 14:01:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w8z-0006WS-Tg
	for pana-archive@odin.ietf.org; Tue, 07 Oct 2003 14:01:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h97I19Yi025066
	for pana-archive@odin.ietf.org; Tue, 7 Oct 2003 14:01:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w8z-0006WD-OA
	for pana-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 14:01:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14140
	for <pana-web-archive@ietf.org>; Tue, 7 Oct 2003 14:00:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w8s-0001XD-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 14:01:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w8s-0001XA-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 14:01:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w8r-0006Sc-GD; Tue, 07 Oct 2003 14:01:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w8L-0006Ri-If
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 14:00:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14097
	for <pana@ietf.org>; Tue, 7 Oct 2003 14:00:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w8J-0001Wa-00
	for pana@ietf.org; Tue, 07 Oct 2003 14:00:27 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w8I-0001WR-00
	for pana@ietf.org; Tue, 07 Oct 2003 14:00:26 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h97I0LF1013294;
	Wed, 8 Oct 2003 03:00:21 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h97I0LOp020202;
	Wed, 8 Oct 2003 03:00:21 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA20200 ; Wed, 8 Oct 2003 03:00:21 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA10808; Wed, 8 Oct 2003 03:00:20 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA14917; Wed, 8 Oct 2003 03:00:20 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h97I0JqT012414;
	Wed, 8 Oct 2003 03:00:19 +0900 (JST)
Received: from steelhead ([159.119.168.86]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HME005LMFCGRW@tsbpo1.po.toshiba.co.jp>; Wed,
 8 Oct 2003 03:00:18 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A6w6z-0003uq-00; Tue, 07 Oct 2003 10:59:05 -0700
Date: Tue, 07 Oct 2003 10:59:04 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue 32
In-reply-to: <BBA7A1EB.9EA0%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: pana@ietf.org
Message-id: <20031007175904.GB14458@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <003101c38c2c$4460f380$5a100a0a@adithya>
 <BBA7A1EB.9EA0%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>


The new text looks good, except that there is some duplicate text in
section h).

Yoshihiro Ohba


On Mon, Oct 06, 2003 at 10:49:15PM -0700, Alper Yegin wrote:
> http://danforsberg.info:8080/pana-issues/issue32
> 
> Proposed text changes are below... Comments welcome.
> 
> 
> From:
> 
>    Since PAA and PaC are one IP hop away from each other, PANA messages
>    can be filtered whenever messages arrive at interfaces where they
>    are not expected.
> 
> 
> To:
> 
>    Since PAA and PaC are supposed to be one IP hop away, a simple
>    TTL check can prevent off-link attacks. Furthermore, additional
>    filtering can be enabled on the EPs. An EP may be able to filter
>    unauthorized PAA advertisements when they are received on the
>    access side of the network where only PaCs are connected.
> 
> 
> From:
> 
>    Hence an 
>    adversary can both eavesdrop the EAP messages and is also able to
>    inject arbitrary messages which might confuse both the PaC and the
>    PAA. 
> 
> To:
> 
>    Hence an 
>    adversary can both eavesdrop the EAP messages and is also able to
>    inject arbitrary messages which might confuse both the EAP peer on PaC
>    and the EAP authenticator or authentication server on the PAA.
> 
> 
> From:
> 
>    For further discussion about the
>    importance of the session key generation refer to the next
>    subsection (c) about compound authentication.
> 
> To:
> 
>    For further discussion about the
>    importance of the session key generation refer to the next
>    subsection (d) about compound authentication.
> 
> 
> From:
> 
>    For the current version of the document an Integrity
>    object is defined which is based on Diameter objects. The Integrity
>    Object supports data-origin authentication, replay protection based
>    on sequence numbers and integrity protection based on a keyed
>    message digest. Confidentiality protection is not provided. The
>    session keys (one for each direction) used for this object has to be
>    provided by the EAP method.
> 
> To:
> 
>    For the current version of the document an itegrity object (MAC AVP) is
>    defined which supports data-origin authentication, replay protection
>    based on sequence numbers and integrity protection based on a keyed
>    message digest. Confidentiality protection is not provided. The
>    session keys used for this object have to be provided by the EAP method.
> 
> 
> From:
> 
>    Instead HMAC-SHA1 is used per-default.
> 
> To:
> 
>    Instead HMAC-SHA1 is used by default.
> 
> 
> From:
> 
>    To select the 
>    security association for signaling message protection the Session
>    ID
> 
> To:
> 
>    To select the 
>    security association for signaling message protection the Session
>    ID is conveyed
> 
> 
> From:
> 
>    If an entity (PAA or PaC) looses its state (especially the current
>    sequence number) then the entire PANA protocol has to be restarted.
> 
> To:
> 
>    If an entity (PAA or PaC) loses its state (especially the current
>    sequence number) then the entire PANA protocol has to be restarted.
> 
> 
> 
> From:
> 
>    The lifetime of the PANA SA has to be bound to the refresh interval
>    with an additional tolerance period. To provide fast re-
>    authentication a separate security association (e.g. one stored at
>    the local AAA server) should be used. By fast re-authentication we
>    mean a new PANA protocol execution which does not involve the entire
>    AAA communication. The ability to trigger such a protocol execution
>    depends on the given EAP method and on the policy of the local
>    network requesting authentication.
> 
> To:
> 
>    The lifetime of the PANA SA has to be bound to the AAA-authorized
>    session lifetime with an additional tolerance period. Unless PANA state
>    is updated by executing another EAP authentication, PANA SA is removed
>    when the current session expires.
> 
> 
> 
> From:
> 
>    Furthermore, a 
>    derived session key might help to create the pre-requisites for
>    network layer protection (for example IPsec).
> 
> To:
> 
>    Furthermore, a 
>    derived session key might help to create the pre-requisites for
>    network-layer protection (for example IPsec [PANA-IPSEC]).
> 
> Add to references:
> 
>    [PANA-IPSEC] M. Parthasarathy: "PANA enabling IPsec based Access
>    Control," Internet Draft, Internet Engineering Task Force, October 2003.
>    Work in progress.
> 
> 
> From:
> 
>    Network access authentication is done for a very specific purpose
>    and often charging procedures are involved which allow restricting
>    network resource usage based on some policies. In mobility
>    environments it is always possible that an end host suddenly
>    disconnects without transmitting a disconnect message. If network
>    access authentication as part of PANA is executed only at the
>    beginning then an adversary can gain advantage of the installed
>    packet filters to submit and receive data packets.
>     
>    Also for the network operator it might be desirable to enforce a
>    disconnect based on some external events (e.g. because of
>    insufficient funds, etc.).
>     
>    An additional motivation for detecting a disconnected end host is
>    the ability to release resources (i.e. garbage collection). The PAA
>    can remove per-session state information including installed
>    security association, packet filters etc.
> 
> To:
> 
>    Network access authentication is done for a very specific purpose
>    and often charging procedures are involved which allow restricting
>    network resource usage based on some policies. In mobility
>    environments it is always possible that an end host suddenly
>    disconnects without transmitting a disconnect message. Operators
>    are generally motivated to detect a disconnected end host as soon
>    as possible in order to release resources (i.e., garbage collection).
>    The PAA  can remove per-session state information including installed
>    security association, packet filters, etc.
> 
> 
> From:
> 
>    h) Periodic refresh messages
> 
>    Different procedures can be used for disconnect indication. PANA
>    cannot assume link layer disconnect indication. Hence this
>    functionality has to be provided at a higher layer. With this
>    version of the draft we suggest to apply the soft-state principle
>    found at other protocols (such as RSVP). Soft-state means that
>    session state is kept alive as long as refresh messages refresh the
>    state. If no new refresh messages are provided then the state
>    automatically times out and resources are released. This process
>    includes stopping accounting procedures.
>     
>    Based on the different environments where PANA could be used it is
>    difficult to fix a refresh interval. Hence a default refresh
>    interval of 30 seconds is suggested. Additionally there is the
>    possibility to negotiation this interval once the PANA security
>    association is established. A policy at the PAA and the PaC would
>    ensure that the refresh interval is selected with a value which is
>    either too high or too low. There is certainly a tradeoff between
>    the refresh interval and the bandwidth consumption. To reduce the
>    bandwidth consumption a small PANA message consisting only of a
>    session identifier and the Integrity object is used. The session
>    identifier refers to the state that has to be refreshed. Some
>    environments do not need PANA refresh messages to detect orphan
>    states. For these environments the refresh interval should be set to
>    zero which effectively disables the usage of refresh messages. In
>    case of IPsec protection a dead-peer mechanism can be used to detect
>    inactivity (see [HBR03]).
>     
>    From a security point of view an adversary must not be able to
>    inject, modify or replay refresh messages nor must he be able to
>    change the refresh interval (e.g. setting it to zero) without
>    detection. Hence these messages experience cryptographic protection.
> 
> 
> To:
> 
>    h) Liveness test
>     
>    Network access authentication is done for a very specific purpose
>    and often charging procedures are involved which allow restricting
>    network resource usage based on some policies. In mobility
>    environments it is always possible that an end host suddenly
>    disconnects without transmitting a disconnect message. Operators
>    are generally motivated to detect a disconnected end host as soon
>    as possible in order to release resources (i.e., garbage collection).
>    The PAA can remove per-session state information including installed
>    security association, packet filters, etc.
> 
>         
>    Different procedures can be used for disconnect indication. PANA
>    cannot assume link-layer disconnect indication. Hence this
>    functionality has to be provided at a higher layer. With this
>    version of the draft we suggest to apply the soft-state principle
>    found at other protocols (such as RSVP). Soft-state means that
>    session state is kept alive as long as refresh messages refresh the
>    state. If no new refresh messages are provided then the state
>    automatically times out and resources are released. This process
>    includes stopping accounting procedures.
>     
>    A PANA session is associated with a session lifetime. The session
>    is terminated unless it is refreshed by a new round of EAP authentication
>    before it expires. Therefore, at the latest a disconnected client
>    can be detected when its lifetime expires. A disconnect may also be
>    detected earlier by using PANA reauthentication messages. A request
>    message can be generated by either PaC or PAA at any time and the peer
>    must respond with an answer message. A successful round-trip of this
>    exchange is a simple verification that the peer is alive. This test
>    can be engaged when there is a possibility that the peer might have
>    disconnected (e.g., after discontinuation of data traffic). Periodic
>    use of this exchange as a keep-alive requires additional care
>    as it might result in congestion and hence false alarms. This exchange
>    is cryptographically protected when PANA SA is available in order
>    to prevent threats associated with the abuse of this functionality.
> 
> 
> _______________________________________________
> 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-admin@ietf.org  Tue Oct  7 14:45:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13844
	for <pana-archive@lists.ietf.org>; Tue, 7 Oct 2003 13:56:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w40-0006B5-ML; Tue, 07 Oct 2003 13:56:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A6w3E-000679-GT
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 13:55:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13723
	for <pana@ietf.org>; Tue, 7 Oct 2003 13:55:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A6w3C-0001Q3-00
	for pana@ietf.org; Tue, 07 Oct 2003 13:55:10 -0400
Received: from smtp002.mail.ukl.yahoo.com ([217.12.11.33])
	by ietf-mx with smtp (Exim 4.12)
	id 1A6w3B-0001Op-00
	for pana@ietf.org; Tue, 07 Oct 2003 13:55:09 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp1.mail.vip.ukl.yahoo.com with SMTP; 7 Oct 2003 17:06:42 -0000
Message-ID: <001901c38cf5$663ce990$5a100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Alper Yegin" <alper@docomolabs-usa.com>, <pana@ietf.org>
References: <BBA78F5C.9E97%alper@docomolabs-usa.com>
Subject: Re: [Pana] EP information
Date: Tue, 7 Oct 2003 10:06:38 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


>
> From PANA-IPsec draft:
>
>
> 3.0 Pre-requisites for IPsec SA establisment
>
>    This document assumes that the following have already happened before
>    the IPSEC SA is established.
>
>      1) PANA client (PaC) learns the IP address of the Enforcement point
>         (EP) during the PANA exchange.
>
> Currently we don't have this feature in PANA. I think we can handle this
by:
>
> - Having an AVP for carrying the DI of EP(s). We can add a new field (or
> flag?) to current device-ID AVP to indicate whether it belongs to PAA or
one
> of the EPs.
> - This AVP MUST be included in PANA-Bind-Request when L2 or L3 ciphering
> will be enabled after PANA. There may be more than one such AVP at a time
> (for multiple access routers, for example).
> - The address type in this AVP MUST match the ciphering type.
>
> Comments?
>
Sounds okay.

-mohan

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


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


From pana-admin@ietf.org  Tue Oct  7 20:06:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28612
	for <pana-archive@lists.ietf.org>; Tue, 7 Oct 2003 20:06:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A71q5-0007GW-5L; Tue, 07 Oct 2003 20:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A71pF-0007G5-Og
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 20:05:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28569
	for <pana@ietf.org>; Tue, 7 Oct 2003 20:05:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A71pD-0005ZC-00
	for pana@ietf.org; Tue, 07 Oct 2003 20:05:07 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A71pC-0005Z9-00
	for pana@ietf.org; Tue, 07 Oct 2003 20:05:07 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h98056F1019751
	for <pana@ietf.org>; Wed, 8 Oct 2003 09:05:06 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h98056aA017423
	for <pana@ietf.org>; Wed, 8 Oct 2003 09:05:06 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id KAA17420 ; Wed, 8 Oct 2003 09:05:05 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA02384; Wed, 8 Oct 2003 09:05:05 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA28456; Wed, 8 Oct 2003 09:05:04 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h98054qT028753
	for <pana@ietf.org>; Wed, 8 Oct 2003 09:05:04 +0900 (JST)
Received: from steelhead ([159.119.168.86]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HME002NYW8E57@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Wed,
 8 Oct 2003 09:05:03 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A71ny-0004a5-00 for <pana@ietf.org>; Tue, 07 Oct 2003 17:03:50 -0700
Date: Tue, 07 Oct 2003 17:03:50 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031008000350.GA17336@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.4i
Subject: [Pana] PANA specification snapshot
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

PANA specification revision 02 is now under editing.  
For your convenience, the latest snapshot can be found at:

http://www.toshiba.com/tari/pana/pana-spec.html

Regards,

Yoshihiro Ohba

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


From exim@www1.ietf.org  Tue Oct  7 20:06:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28627
	for <pana-archive@odin.ietf.org>; Tue, 7 Oct 2003 20:06:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A71q9-0007HB-9y
	for pana-archive@odin.ietf.org; Tue, 07 Oct 2003 20:06:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h98065v5027965
	for pana-archive@odin.ietf.org; Tue, 7 Oct 2003 20:06:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A71q9-0007Gy-52
	for pana-web-archive@optimus.ietf.org; Tue, 07 Oct 2003 20:06:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28589
	for <pana-web-archive@ietf.org>; Tue, 7 Oct 2003 20:05:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A71q7-0005Zm-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 20:06:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A71q6-0005Zj-00
	for pana-web-archive@ietf.org; Tue, 07 Oct 2003 20:06:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A71q5-0007GW-5L; Tue, 07 Oct 2003 20:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A71pF-0007G5-Og
	for pana@optimus.ietf.org; Tue, 07 Oct 2003 20:05:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28569
	for <pana@ietf.org>; Tue, 7 Oct 2003 20:05:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A71pD-0005ZC-00
	for pana@ietf.org; Tue, 07 Oct 2003 20:05:07 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A71pC-0005Z9-00
	for pana@ietf.org; Tue, 07 Oct 2003 20:05:07 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h98056F1019751
	for <pana@ietf.org>; Wed, 8 Oct 2003 09:05:06 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h98056aA017423
	for <pana@ietf.org>; Wed, 8 Oct 2003 09:05:06 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id KAA17420 ; Wed, 8 Oct 2003 09:05:05 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA02384; Wed, 8 Oct 2003 09:05:05 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA28456; Wed, 8 Oct 2003 09:05:04 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h98054qT028753
	for <pana@ietf.org>; Wed, 8 Oct 2003 09:05:04 +0900 (JST)
Received: from steelhead ([159.119.168.86]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HME002NYW8E57@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Wed,
 8 Oct 2003 09:05:03 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A71ny-0004a5-00 for <pana@ietf.org>; Tue, 07 Oct 2003 17:03:50 -0700
Date: Tue, 07 Oct 2003 17:03:50 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031008000350.GA17336@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.4i
Subject: [Pana] PANA specification snapshot
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

PANA specification revision 02 is now under editing.  
For your convenience, the latest snapshot can be found at:

http://www.toshiba.com/tari/pana/pana-spec.html

Regards,

Yoshihiro Ohba

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



From pana-admin@ietf.org  Wed Oct  8 02:07:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13852
	for <pana-archive@lists.ietf.org>; Wed, 8 Oct 2003 02:07:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77TR-0006ly-Bt; Wed, 08 Oct 2003 02:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77SV-0006d8-WF
	for pana@optimus.ietf.org; Wed, 08 Oct 2003 02:06:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12414
	for <pana@ietf.org>; Wed, 8 Oct 2003 02:05:54 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77SS-0000lN-00
	for pana@ietf.org; Wed, 08 Oct 2003 02:06:00 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77SR-0000lK-00
	for pana@ietf.org; Wed, 08 Oct 2003 02:05:59 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h98660t18954
	for <pana@ietf.org>; Wed, 8 Oct 2003 09:06:00 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65275ad0dfac158f23077@esvir03nok.nokia.com>;
 Wed, 8 Oct 2003 09:06:00 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 8 Oct 2003 09:05:59 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 8 Oct 2003 09:05:59 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] reference missing
Date: Wed, 8 Oct 2003 09:05:59 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D49@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] reference missing
Thread-Index: AcOJAIlbIUR8dhNMSiuVBW3OqXk12AEYYvIg
To: <yohba@tari.toshiba.com>, <pana@ietf.org>
X-OriginalArrivalTime: 08 Oct 2003 06:05:59.0737 (UTC) FILETIME=[3EDB3290:01C38D62]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi,

It is RFC2464. 

- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 02 October, 2003 19:14
> To: pana@ietf.org
> Subject: [Pana] reference missing
> 
> 
> In the following text in section 9.4.2, I can't find a reference to 
> [IPv6-ETHER].  What document it points to?
> 
> 
>    The first octet (8 bits) of the Device-Id (Code 1025) AVP data
>    contains the device type. Rest of the AVP data payload contains
>    the device data.  The content and format of data (including byte
>    and bit ordering) is expected to be specified in specific
>    documents.  For instance, [IPv6-ETHER].
>                                                               
>                   
> 
> Yoshihiro Ohba
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 

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


From exim@www1.ietf.org  Wed Oct  8 02:07:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13935
	for <pana-archive@odin.ietf.org>; Wed, 8 Oct 2003 02:07:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77TW-0006nc-Et
	for pana-archive@odin.ietf.org; Wed, 08 Oct 2003 02:07:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h986766T026121
	for pana-archive@odin.ietf.org; Wed, 8 Oct 2003 02:07:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77TV-0006n2-B3
	for pana-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 02:07:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13385
	for <pana-web-archive@ietf.org>; Wed, 8 Oct 2003 02:06:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77TR-0000m8-00
	for pana-web-archive@ietf.org; Wed, 08 Oct 2003 02:07:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77TR-0000m5-00
	for pana-web-archive@ietf.org; Wed, 08 Oct 2003 02:07:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77TR-0006ly-Bt; Wed, 08 Oct 2003 02:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77SV-0006d8-WF
	for pana@optimus.ietf.org; Wed, 08 Oct 2003 02:06:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12414
	for <pana@ietf.org>; Wed, 8 Oct 2003 02:05:54 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77SS-0000lN-00
	for pana@ietf.org; Wed, 08 Oct 2003 02:06:00 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77SR-0000lK-00
	for pana@ietf.org; Wed, 08 Oct 2003 02:05:59 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h98660t18954
	for <pana@ietf.org>; Wed, 8 Oct 2003 09:06:00 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65275ad0dfac158f23077@esvir03nok.nokia.com>;
 Wed, 8 Oct 2003 09:06:00 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 8 Oct 2003 09:05:59 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 8 Oct 2003 09:05:59 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] reference missing
Date: Wed, 8 Oct 2003 09:05:59 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D49@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] reference missing
Thread-Index: AcOJAIlbIUR8dhNMSiuVBW3OqXk12AEYYvIg
To: <yohba@tari.toshiba.com>, <pana@ietf.org>
X-OriginalArrivalTime: 08 Oct 2003 06:05:59.0737 (UTC) FILETIME=[3EDB3290:01C38D62]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

It is RFC2464. 

- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 02 October, 2003 19:14
> To: pana@ietf.org
> Subject: [Pana] reference missing
> 
> 
> In the following text in section 9.4.2, I can't find a reference to 
> [IPv6-ETHER].  What document it points to?
> 
> 
>    The first octet (8 bits) of the Device-Id (Code 1025) AVP data
>    contains the device type. Rest of the AVP data payload contains
>    the device data.  The content and format of data (including byte
>    and bit ordering) is expected to be specified in specific
>    documents.  For instance, [IPv6-ETHER].
>                                                               
>                   
> 
> Yoshihiro Ohba
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 

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



From pana-admin@ietf.org  Wed Oct  8 02:30:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02814
	for <pana-archive@lists.ietf.org>; Wed, 8 Oct 2003 02:30:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77ph-0000V2-Lw; Wed, 08 Oct 2003 02:30:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77op-0000Sy-4M
	for pana@optimus.ietf.org; Wed, 08 Oct 2003 02:29:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01758
	for <pana@ietf.org>; Wed, 8 Oct 2003 02:28:57 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77ol-0000vl-00
	for pana@ietf.org; Wed, 08 Oct 2003 02:29:03 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77ok-0000vi-00
	for pana@ietf.org; Wed, 08 Oct 2003 02:29:02 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h986T3619862
	for <pana@ietf.org>; Wed, 8 Oct 2003 09:29:03 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65276fd8faac158f2513e@esvir05nok.ntc.nokia.com>;
 Wed, 8 Oct 2003 09:28:58 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 8 Oct 2003 09:27:58 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 8 Oct 2003 09:27:58 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue19] Result-Code AVP values?
Date: Wed, 8 Oct 2003 09:27:58 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C594@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOM/B1rpYhD6yx7TMKrnfDz1Q8f4gAZwdXQ
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 08 Oct 2003 06:27:58.0700 (UTC) FILETIME=[5104FAC0:01C38D65]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

In PANA we retransmit requests because we want to have reliable=20
transport. So, the case where the authenticator retransmits the=20
EAP-Request/Identity is interpreted differently in PANA layer=20
(retransmissions for reliability).

The case of Notification Request is usable, but what does=20
"invalid authentication attempt" mean? Can we interpret it such=20
a way that it means "typo in the identity, user part" or "user=20
not recognized" or "realm not served"..

A result code in PANA for this (borrowed from Diameter) is clear
and works if the authenticator implementation doesn't support=20
this MAY part of the EAP doc.

- Dan


> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 07 October, 2003 20:55
> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>=20
>=20
> >> I think this is also an EAP question. What would be the EAP
> >> behavior when
> >> the NAS cannot recognize the EAP client identifier?
>=20
> I think this case would be handled by the following text from=20
> the EAP spec:
>=20
>          Implementation Note: The peer MAY obtain the=20
> Identity via user
>          input.  It is suggested that the authenticator retry the
>          Identity Request in the case of an invalid Identity or
>          authentication failure to allow for potential typos=20
> on the part
>          of the user.  It is suggested that the Identity Request be
>          retried a minimum of 3 times before terminating the
>          authentication.  The Notification Request MAY be used to
>          indicate an invalid authentication attempt prior to
>          transmitting a new Identity Request (optionally, the failure
>          MAY be indicated within the message of the new=20
> Identity Request
>          itself).
>=20
> ... And finally I think the EAP authenticator would send a=20
> Failure message.
>=20
> Alper
>=20
>=20
>=20

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


From exim@www1.ietf.org  Wed Oct  8 02:30:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02845
	for <pana-archive@odin.ietf.org>; Wed, 8 Oct 2003 02:30:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77pm-0000Vf-QG
	for pana-archive@odin.ietf.org; Wed, 08 Oct 2003 02:30:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h986U6Ie001960
	for pana-archive@odin.ietf.org; Wed, 8 Oct 2003 02:30:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77pm-0000VV-4j
	for pana-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 02:30:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02449
	for <pana-web-archive@ietf.org>; Wed, 8 Oct 2003 02:29:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77pi-0000xR-00
	for pana-web-archive@ietf.org; Wed, 08 Oct 2003 02:30:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77ph-0000xL-00
	for pana-web-archive@ietf.org; Wed, 08 Oct 2003 02:30:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77ph-0000V2-Lw; Wed, 08 Oct 2003 02:30:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A77op-0000Sy-4M
	for pana@optimus.ietf.org; Wed, 08 Oct 2003 02:29:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01758
	for <pana@ietf.org>; Wed, 8 Oct 2003 02:28:57 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77ol-0000vl-00
	for pana@ietf.org; Wed, 08 Oct 2003 02:29:03 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A77ok-0000vi-00
	for pana@ietf.org; Wed, 08 Oct 2003 02:29:02 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h986T3619862
	for <pana@ietf.org>; Wed, 8 Oct 2003 09:29:03 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65276fd8faac158f2513e@esvir05nok.ntc.nokia.com>;
 Wed, 8 Oct 2003 09:28:58 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 8 Oct 2003 09:27:58 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 8 Oct 2003 09:27:58 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] [issue19] Result-Code AVP values?
Date: Wed, 8 Oct 2003 09:27:58 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C594@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOM/B1rpYhD6yx7TMKrnfDz1Q8f4gAZwdXQ
To: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 08 Oct 2003 06:27:58.0700 (UTC) FILETIME=[5104FAC0:01C38D65]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

In PANA we retransmit requests because we want to have reliable=20
transport. So, the case where the authenticator retransmits the=20
EAP-Request/Identity is interpreted differently in PANA layer=20
(retransmissions for reliability).

The case of Notification Request is usable, but what does=20
"invalid authentication attempt" mean? Can we interpret it such=20
a way that it means "typo in the identity, user part" or "user=20
not recognized" or "realm not served"..

A result code in PANA for this (borrowed from Diameter) is clear
and works if the authenticator implementation doesn't support=20
this MAY part of the EAP doc.

- Dan


> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 07 October, 2003 20:55
> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>=20
>=20
> >> I think this is also an EAP question. What would be the EAP
> >> behavior when
> >> the NAS cannot recognize the EAP client identifier?
>=20
> I think this case would be handled by the following text from=20
> the EAP spec:
>=20
>          Implementation Note: The peer MAY obtain the=20
> Identity via user
>          input.  It is suggested that the authenticator retry the
>          Identity Request in the case of an invalid Identity or
>          authentication failure to allow for potential typos=20
> on the part
>          of the user.  It is suggested that the Identity Request be
>          retried a minimum of 3 times before terminating the
>          authentication.  The Notification Request MAY be used to
>          indicate an invalid authentication attempt prior to
>          transmitting a new Identity Request (optionally, the failure
>          MAY be indicated within the message of the new=20
> Identity Request
>          itself).
>=20
> ... And finally I think the EAP authenticator would send a=20
> Failure message.
>=20
> Alper
>=20
>=20
>=20

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



From pana-admin@ietf.org  Wed Oct  8 14:16:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00647
	for <pana-archive@lists.ietf.org>; Wed, 8 Oct 2003 14:16:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Iqu-0007pU-Fe; Wed, 08 Oct 2003 14:16:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Iq3-0007ne-CV
	for pana@optimus.ietf.org; Wed, 08 Oct 2003 14:15:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00531
	for <pana@ietf.org>; Wed, 8 Oct 2003 14:14:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Iq0-0002Bu-00
	for pana@ietf.org; Wed, 08 Oct 2003 14:15:04 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Ipz-0002Br-00
	for pana@ietf.org; Wed, 08 Oct 2003 14:15:04 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h98IEvF1026478;
	Thu, 9 Oct 2003 03:14:57 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h98IEvL1009386;
	Thu, 9 Oct 2003 03:14:57 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA09385 ; Thu, 9 Oct 2003 03:14:57 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA29606; Thu, 9 Oct 2003 03:14:57 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA16309; Thu, 9 Oct 2003 03:14:56 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h98IEuqT023288;
	Thu, 9 Oct 2003 03:14:56 +0900 (JST)
Received: from steelhead ([159.119.168.149]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMG00EBFAOUM8@tsbpo1.po.toshiba.co.jp>; Thu,
 9 Oct 2003 03:14:55 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A7Iog-0006HX-00; Wed, 08 Oct 2003 11:13:42 -0700
Date: Wed, 08 Oct 2003 11:13:42 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New  [issue31] Init responsibility of for EAP level
 reauthentication?
In-reply-to: <20031006173000.GB5880@steelhead>
To: Alper Yegin <alper@docomolabs-usa.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Message-id: <20031008181342.GC22704@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20030918151320.GA9128@steelhead>
 <BB988216.942A%alper@docomolabs-usa.com> <20031006173000.GB5880@steelhead>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

The race condition I mentioned is common to both initial EAP
authentication and EAP re-authentication, and this might be better
handled in a separate issue.

So I agree on the proposed text for issue 31 and let's close this
issue.

Yoshihiro Ohba


On Mon, Oct 06, 2003 at 10:30:01AM -0700, Yoshihiro Ohba wrote:
> On Thu, Sep 25, 2003 at 11:29:26AM -0700, Alper Yegin wrote:
> > Are we talking about restarting the EAP state machine, or engaging a
> > EAP-method-specific re-auth mechanism?
> 
> The former.  
> 
> > 
> > If former: PaC can send PANA-PAA-Discover to initiate, and PAA can send
> > PANA-Start-Request to initiate or as a response.
> 
> I think this is not the only allowable sequence in the former case.
> PAA can send PANA-Auth-Request to initiate EAP-based re-authentication
> if the PAA already has an established PANA session for the PaC.  That
> is why I mentioned race condition.
> 
> Yoshihiro Ohba
> 
> > 
> > If latter: PAA can send PANA-Auth-Request. I don't think this is a valid
> > case for PaC to send anything, because only the authenticator can send EAP
> > requests. (how can the EAP peer initiate the EAP-method-level reauth?)
> > 
> > Alper
> > 
> > 
> > 
> > > For timer-based EAP level reauthentication, PAA should be responsible
> > > for initiating the reauthentication because PaC does not know enough
> > > information (such as grace period) to be able to perform the
> > > reauthentication at an appropriate time.  On the other hand, if EAP
> > > level reauthentication is to be performed for other reasons, I think
> > > both PaC and PAA can initiate the reauthentication.
> > > 
> > > There would be one issue in the latter case.  What happens if both PaC
> > > and PAA initate EAP level reauthentication at the same time?  When
> > > this happens, the PaC will send a PANA-PAA-Discover message while the
> > > PAA will send a PANA-Auth-Request message, according to the EAP level
> > > reauthentication behavior described in section 4.4.  In this case, the
> > > PAA can rely on the EAP restransmission (as a result multiple
> > > PANA-Auth-Request message with carrying the same EAP message will be
> > > generated) and simply ignore the received PANA-PAA-Discover message.
> > > This way, the race condition can be resolved.
> > > 
> > > Yoshihiro Ohba
> > > 
> > > 
> > > On Thu, Sep 18, 2003 at 04:33:05PM +0300, Dan.Forsberg@nokia.com wrote:
> > >> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> > >> 
> > >> Is PaC or PAA responsible of initiating EAP level reauthentication? This
> > >> MUST be clearly stated in the draft.
> > >> 
> > >> 
> > >> ----------
> > >> category: Technical
> > >> document: draft-ietf-pana-pana-xx.txt
> > >> messages: 86
> > >> nosy: dforsber
> > >> priority: Must Fix
> > >> status: No Discussion
> > >> title: Init responsibility of for EAP level reauthentication?
> > >> ________________________________________________
> > >> PANA Issues <pana_issues@danforsberg.info>
> > >> http://danforsberg.info:8080/pana-issues/issue31
> > >> ________________________________________________
> > >> 
> > >> _______________________________________________
> > >> Pana mailing list
> > >> Pana@ietf.org
> > >> https://www1.ietf.org/mailman/listinfo/pana
> > > 
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > > 
> > 
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

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


From exim@www1.ietf.org  Wed Oct  8 14:16:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00662
	for <pana-archive@odin.ietf.org>; Wed, 8 Oct 2003 14:16:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Iqy-0007qQ-R0
	for pana-archive@odin.ietf.org; Wed, 08 Oct 2003 14:16:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h98IG4Gp030148
	for pana-archive@odin.ietf.org; Wed, 8 Oct 2003 14:16:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Iqy-0007qB-LR
	for pana-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 14:16:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00612
	for <pana-web-archive@ietf.org>; Wed, 8 Oct 2003 14:15:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Iqw-0002DM-00
	for pana-web-archive@ietf.org; Wed, 08 Oct 2003 14:16:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Iqv-0002DI-00
	for pana-web-archive@ietf.org; Wed, 08 Oct 2003 14:16:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Iqu-0007pU-Fe; Wed, 08 Oct 2003 14:16:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Iq3-0007ne-CV
	for pana@optimus.ietf.org; Wed, 08 Oct 2003 14:15:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00531
	for <pana@ietf.org>; Wed, 8 Oct 2003 14:14:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Iq0-0002Bu-00
	for pana@ietf.org; Wed, 08 Oct 2003 14:15:04 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Ipz-0002Br-00
	for pana@ietf.org; Wed, 08 Oct 2003 14:15:04 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h98IEvF1026478;
	Thu, 9 Oct 2003 03:14:57 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h98IEvL1009386;
	Thu, 9 Oct 2003 03:14:57 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA09385 ; Thu, 9 Oct 2003 03:14:57 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA29606; Thu, 9 Oct 2003 03:14:57 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA16309; Thu, 9 Oct 2003 03:14:56 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h98IEuqT023288;
	Thu, 9 Oct 2003 03:14:56 +0900 (JST)
Received: from steelhead ([159.119.168.149]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMG00EBFAOUM8@tsbpo1.po.toshiba.co.jp>; Thu,
 9 Oct 2003 03:14:55 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A7Iog-0006HX-00; Wed, 08 Oct 2003 11:13:42 -0700
Date: Wed, 08 Oct 2003 11:13:42 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] New  [issue31] Init responsibility of for EAP level
 reauthentication?
In-reply-to: <20031006173000.GB5880@steelhead>
To: Alper Yegin <alper@docomolabs-usa.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Message-id: <20031008181342.GC22704@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20030918151320.GA9128@steelhead>
 <BB988216.942A%alper@docomolabs-usa.com> <20031006173000.GB5880@steelhead>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

The race condition I mentioned is common to both initial EAP
authentication and EAP re-authentication, and this might be better
handled in a separate issue.

So I agree on the proposed text for issue 31 and let's close this
issue.

Yoshihiro Ohba


On Mon, Oct 06, 2003 at 10:30:01AM -0700, Yoshihiro Ohba wrote:
> On Thu, Sep 25, 2003 at 11:29:26AM -0700, Alper Yegin wrote:
> > Are we talking about restarting the EAP state machine, or engaging a
> > EAP-method-specific re-auth mechanism?
> 
> The former.  
> 
> > 
> > If former: PaC can send PANA-PAA-Discover to initiate, and PAA can send
> > PANA-Start-Request to initiate or as a response.
> 
> I think this is not the only allowable sequence in the former case.
> PAA can send PANA-Auth-Request to initiate EAP-based re-authentication
> if the PAA already has an established PANA session for the PaC.  That
> is why I mentioned race condition.
> 
> Yoshihiro Ohba
> 
> > 
> > If latter: PAA can send PANA-Auth-Request. I don't think this is a valid
> > case for PaC to send anything, because only the authenticator can send EAP
> > requests. (how can the EAP peer initiate the EAP-method-level reauth?)
> > 
> > Alper
> > 
> > 
> > 
> > > For timer-based EAP level reauthentication, PAA should be responsible
> > > for initiating the reauthentication because PaC does not know enough
> > > information (such as grace period) to be able to perform the
> > > reauthentication at an appropriate time.  On the other hand, if EAP
> > > level reauthentication is to be performed for other reasons, I think
> > > both PaC and PAA can initiate the reauthentication.
> > > 
> > > There would be one issue in the latter case.  What happens if both PaC
> > > and PAA initate EAP level reauthentication at the same time?  When
> > > this happens, the PaC will send a PANA-PAA-Discover message while the
> > > PAA will send a PANA-Auth-Request message, according to the EAP level
> > > reauthentication behavior described in section 4.4.  In this case, the
> > > PAA can rely on the EAP restransmission (as a result multiple
> > > PANA-Auth-Request message with carrying the same EAP message will be
> > > generated) and simply ignore the received PANA-PAA-Discover message.
> > > This way, the race condition can be resolved.
> > > 
> > > Yoshihiro Ohba
> > > 
> > > 
> > > On Thu, Sep 18, 2003 at 04:33:05PM +0300, Dan.Forsberg@nokia.com wrote:
> > >> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> > >> 
> > >> Is PaC or PAA responsible of initiating EAP level reauthentication? This
> > >> MUST be clearly stated in the draft.
> > >> 
> > >> 
> > >> ----------
> > >> category: Technical
> > >> document: draft-ietf-pana-pana-xx.txt
> > >> messages: 86
> > >> nosy: dforsber
> > >> priority: Must Fix
> > >> status: No Discussion
> > >> title: Init responsibility of for EAP level reauthentication?
> > >> ________________________________________________
> > >> PANA Issues <pana_issues@danforsberg.info>
> > >> http://danforsberg.info:8080/pana-issues/issue31
> > >> ________________________________________________
> > >> 
> > >> _______________________________________________
> > >> Pana mailing list
> > >> Pana@ietf.org
> > >> https://www1.ietf.org/mailman/listinfo/pana
> > > 
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > > 
> > 
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana

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



From pana-admin@ietf.org  Wed Oct  8 14:36:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01888
	for <pana-archive@lists.ietf.org>; Wed, 8 Oct 2003 14:36:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7JAH-0000Uh-1M; Wed, 08 Oct 2003 14:36:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7J9U-0000Tv-P5
	for pana@optimus.ietf.org; Wed, 08 Oct 2003 14:35:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01817
	for <pana@ietf.org>; Wed, 8 Oct 2003 14:35:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7J9S-0002Va-00
	for pana@ietf.org; Wed, 08 Oct 2003 14:35:10 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7J9R-0002VX-00
	for pana@ietf.org; Wed, 08 Oct 2003 14:35:09 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h98IZ8F1000707;
	Thu, 9 Oct 2003 03:35:08 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h98IZ8rt015182;
	Thu, 9 Oct 2003 03:35:08 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA15181 ; Thu, 9 Oct 2003 03:35:08 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA04416; Thu, 9 Oct 2003 03:35:07 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA03953; Thu, 9 Oct 2003 03:35:07 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h98IZ6qT025666;
	Thu, 9 Oct 2003 03:35:06 +0900 (JST)
Received: from steelhead ([159.119.168.149]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMG00EI3BMGM8@tsbpo1.po.toshiba.co.jp>; Thu,
 9 Oct 2003 03:35:05 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A7J87-0006K7-00; Wed, 08 Oct 2003 11:33:47 -0700
Date: Wed, 08 Oct 2003 11:33:46 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue17] Error handling
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D21@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20031008183346.GD22704@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D21@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

One more editorial change.

In section 4.1.7, 

change: 

 "(TBD: in addition, a
   non-acknowledged error notification message MAY be returned to the
   sender.)"

to:

 "In addition, a non-acknowledged error notification message MAY be
  returned to the sender.  See Section X for details."

Yoshihiro Ohba


On Thu, Oct 02, 2003 at 10:18:44AM +0300, Dan.Forsberg@nokia.com wrote:
> Dan Forsberg <dan.forsberg@nokia.com> added the comment:
> 
> Add new section:
> 
> X. Error handling
> 
>    PANA-error message MAY be sent by either PaC or PAA when a
>    badly formed PANA message is received or in case of other
>    errors.  If the cause of this error message was a request
>    message (e.g., PANA-PAA-Discover or *-Request), then the
>    request MAY be retransmitted immediately without waiting for
>    its retransmission timer to go off. If the cause of the
>    error was a response message, the receiver of the PANA-error
>    SHOULD NOT resend the same response until it receives the
>    next request.
> 
>    To defend against DoS attacks a timer MAY be used. One (1)
>    error notification is sent to each different sender each N
>    seconds. N is a configurable parameter.
>  
>    When an error message is sent unprotected with MAC AVP and
>    the lower-layer is insecure, the error message is treated as
>    an informational message.  The receiver of such an error
>    message MUST NOT change its state unless the error persists
>    and the PANA session is not making any progress.
> 
> 
> 
> Add new subsection:
> 
> 9.3.Y    PANA-Error
> 
>    PANA-error is sent either by the PaC or the PAA.
> 
>    PANA-Error ::= < PANA-Header: 12 >
>                    < Session-Id > 
> 		   < Result-Code >
>                    { Failed-AVP }
>                  * [ AVP ] 
>                0*1 < MAC >
> 
> 
> Add new subsection:
> 
> 9.4.Z    Failed-AVP AVP
> 
>    The Failed-AVP AVP is defined in [DIAMETER].
> 
> ________________________________________________
> PANA Issues <pana_issues@danforsberg.info>
> http://danforsberg.info:8080/pana-issues/issue17
> ________________________________________________
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Wed Oct  8 14:36:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01903
	for <pana-archive@odin.ietf.org>; Wed, 8 Oct 2003 14:36:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7JAK-0000VL-7n
	for pana-archive@odin.ietf.org; Wed, 08 Oct 2003 14:36:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h98Ia4Q0001935
	for pana-archive@odin.ietf.org; Wed, 8 Oct 2003 14:36:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7JAK-0000V8-3z
	for pana-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 14:36:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01852
	for <pana-web-archive@ietf.org>; Wed, 8 Oct 2003 14:35:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7JAH-0002WL-00
	for pana-web-archive@ietf.org; Wed, 08 Oct 2003 14:36:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7JAH-0002WI-00
	for pana-web-archive@ietf.org; Wed, 08 Oct 2003 14:36:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7JAH-0000Uh-1M; Wed, 08 Oct 2003 14:36:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7J9U-0000Tv-P5
	for pana@optimus.ietf.org; Wed, 08 Oct 2003 14:35:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01817
	for <pana@ietf.org>; Wed, 8 Oct 2003 14:35:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7J9S-0002Va-00
	for pana@ietf.org; Wed, 08 Oct 2003 14:35:10 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7J9R-0002VX-00
	for pana@ietf.org; Wed, 08 Oct 2003 14:35:09 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h98IZ8F1000707;
	Thu, 9 Oct 2003 03:35:08 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h98IZ8rt015182;
	Thu, 9 Oct 2003 03:35:08 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA15181 ; Thu, 9 Oct 2003 03:35:08 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA04416; Thu, 9 Oct 2003 03:35:07 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA03953; Thu, 9 Oct 2003 03:35:07 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h98IZ6qT025666;
	Thu, 9 Oct 2003 03:35:06 +0900 (JST)
Received: from steelhead ([159.119.168.149]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMG00EI3BMGM8@tsbpo1.po.toshiba.co.jp>; Thu,
 9 Oct 2003 03:35:05 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A7J87-0006K7-00; Wed, 08 Oct 2003 11:33:47 -0700
Date: Wed, 08 Oct 2003 11:33:46 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue17] Error handling
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D21@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20031008183346.GD22704@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D21@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

One more editorial change.

In section 4.1.7, 

change: 

 "(TBD: in addition, a
   non-acknowledged error notification message MAY be returned to the
   sender.)"

to:

 "In addition, a non-acknowledged error notification message MAY be
  returned to the sender.  See Section X for details."

Yoshihiro Ohba


On Thu, Oct 02, 2003 at 10:18:44AM +0300, Dan.Forsberg@nokia.com wrote:
> Dan Forsberg <dan.forsberg@nokia.com> added the comment:
> 
> Add new section:
> 
> X. Error handling
> 
>    PANA-error message MAY be sent by either PaC or PAA when a
>    badly formed PANA message is received or in case of other
>    errors.  If the cause of this error message was a request
>    message (e.g., PANA-PAA-Discover or *-Request), then the
>    request MAY be retransmitted immediately without waiting for
>    its retransmission timer to go off. If the cause of the
>    error was a response message, the receiver of the PANA-error
>    SHOULD NOT resend the same response until it receives the
>    next request.
> 
>    To defend against DoS attacks a timer MAY be used. One (1)
>    error notification is sent to each different sender each N
>    seconds. N is a configurable parameter.
>  
>    When an error message is sent unprotected with MAC AVP and
>    the lower-layer is insecure, the error message is treated as
>    an informational message.  The receiver of such an error
>    message MUST NOT change its state unless the error persists
>    and the PANA session is not making any progress.
> 
> 
> 
> Add new subsection:
> 
> 9.3.Y    PANA-Error
> 
>    PANA-error is sent either by the PaC or the PAA.
> 
>    PANA-Error ::= < PANA-Header: 12 >
>                    < Session-Id > 
> 		   < Result-Code >
>                    { Failed-AVP }
>                  * [ AVP ] 
>                0*1 < MAC >
> 
> 
> Add new subsection:
> 
> 9.4.Z    Failed-AVP AVP
> 
>    The Failed-AVP AVP is defined in [DIAMETER].
> 
> ________________________________________________
> PANA Issues <pana_issues@danforsberg.info>
> http://danforsberg.info:8080/pana-issues/issue17
> ________________________________________________
> 
> _______________________________________________
> 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-admin@ietf.org  Wed Oct  8 15:18:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04736
	for <pana-archive@lists.ietf.org>; Wed, 8 Oct 2003 15:18:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Jou-00043I-Rp; Wed, 08 Oct 2003 15:18:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Jos-000437-MX
	for pana@optimus.ietf.org; Wed, 08 Oct 2003 15:17:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04659
	for <pana@ietf.org>; Wed, 8 Oct 2003 15:17:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Jor-00035i-00
	for pana@ietf.org; Wed, 08 Oct 2003 15:17:57 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Joq-00035f-00
	for pana@ietf.org; Wed, 08 Oct 2003 15:17:56 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h98JHtF1009991
	for <pana@ietf.org>; Thu, 9 Oct 2003 04:17:55 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h98JHt4R027945
	for <pana@ietf.org>; Thu, 9 Oct 2003 04:17:55 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA27944 ; Thu, 9 Oct 2003 04:17:55 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA14446; Thu, 9 Oct 2003 04:17:54 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA16603; Thu, 9 Oct 2003 04:17:54 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h98JHrqT000992
	for <pana@ietf.org>; Thu, 9 Oct 2003 04:17:54 +0900 (JST)
Received: from steelhead ([159.119.168.149]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMG00EWNDLSM8@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Thu,
 9 Oct 2003 04:17:53 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A7JkS-0006Re-00 for <pana@ietf.org>; Wed, 08 Oct 2003 12:13:24 -0700
Date: Wed, 08 Oct 2003 12:13:23 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031008191323.GF22704@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.4i
Subject: [Pana] specification snapshot -02c
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

PANA specification snapshot -02c is available at:
http://www.toshiba.com/tari/pana/pana-spec.html

Diffs between consecutive snapshots are also provided (Thanks Dan for
suggesting this).

Yoshihiro Ohba


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


From exim@www1.ietf.org  Wed Oct  8 15:18:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04748
	for <pana-archive@odin.ietf.org>; Wed, 8 Oct 2003 15:18:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Jox-000443-QM
	for pana-archive@odin.ietf.org; Wed, 08 Oct 2003 15:18:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h98JI3rn015617
	for pana-archive@odin.ietf.org; Wed, 8 Oct 2003 15:18:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Jox-00043o-LJ
	for pana-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 15:18:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04673
	for <pana-web-archive@ietf.org>; Wed, 8 Oct 2003 15:17:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Jow-00035u-00
	for pana-web-archive@ietf.org; Wed, 08 Oct 2003 15:18:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Jow-00035r-00
	for pana-web-archive@ietf.org; Wed, 08 Oct 2003 15:18:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Jou-00043I-Rp; Wed, 08 Oct 2003 15:18:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Jos-000437-MX
	for pana@optimus.ietf.org; Wed, 08 Oct 2003 15:17:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04659
	for <pana@ietf.org>; Wed, 8 Oct 2003 15:17:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Jor-00035i-00
	for pana@ietf.org; Wed, 08 Oct 2003 15:17:57 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7Joq-00035f-00
	for pana@ietf.org; Wed, 08 Oct 2003 15:17:56 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h98JHtF1009991
	for <pana@ietf.org>; Thu, 9 Oct 2003 04:17:55 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h98JHt4R027945
	for <pana@ietf.org>; Thu, 9 Oct 2003 04:17:55 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA27944 ; Thu, 9 Oct 2003 04:17:55 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA14446; Thu, 9 Oct 2003 04:17:54 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA16603; Thu, 9 Oct 2003 04:17:54 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h98JHrqT000992
	for <pana@ietf.org>; Thu, 9 Oct 2003 04:17:54 +0900 (JST)
Received: from steelhead ([159.119.168.149]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMG00EWNDLSM8@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Thu,
 9 Oct 2003 04:17:53 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A7JkS-0006Re-00 for <pana@ietf.org>; Wed, 08 Oct 2003 12:13:24 -0700
Date: Wed, 08 Oct 2003 12:13:23 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031008191323.GF22704@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.4i
Subject: [Pana] specification snapshot -02c
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

PANA specification snapshot -02c is available at:
http://www.toshiba.com/tari/pana/pana-spec.html

Diffs between consecutive snapshots are also provided (Thanks Dan for
suggesting this).

Yoshihiro Ohba


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



From pana-admin@ietf.org  Thu Oct  9 02:36:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08668
	for <pana-archive@lists.ietf.org>; Thu, 9 Oct 2003 02:36:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7UP3-0005OC-D8; Thu, 09 Oct 2003 02:36:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7UOs-0005Nj-8K
	for pana@optimus.ietf.org; Thu, 09 Oct 2003 02:35:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08644
	for <pana@ietf.org>; Thu, 9 Oct 2003 02:35:41 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7UOo-0002OL-00
	for pana@ietf.org; Thu, 09 Oct 2003 02:35:46 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7UOn-0002OI-00
	for pana@ietf.org; Thu, 09 Oct 2003 02:35:45 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h996Zk610496
	for <pana@ietf.org>; Thu, 9 Oct 2003 09:35:46 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T652c9c6c4aac158f25048@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Thu, 9 Oct 2003 09:35:45 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 9 Oct 2003 09:35:45 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 9 Oct 2003 09:35:44 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D53@esebe008.ntc.nokia.com>
Thread-Topic: [issue36] Reauthentication race condition
Thread-Index: AcOOL4DIoFr0OYO8Qqyg2lgmJfUWlwAAAa1Q
To: <pana@ietf.org>
X-OriginalArrivalTime: 09 Oct 2003 06:35:45.0642 (UTC) FILETIME=[91C06CA0:01C38E2F]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue36] Reauthentication race condition
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

New submission from Dan Forsberg <dan.forsberg@nokia.com>:

> > > There would be one issue in the latter case.  What happens if both =
PaC
> > > and PAA initate EAP level reauthentication at the same time?  When
> > > this happens, the PaC will send a PANA-PAA-Discover message while =
the
> > > PAA will send a PANA-Auth-Request message, according to the EAP =
level
> > > reauthentication behavior described in section 4.4.  In this case, =
the
> > > PAA can rely on the EAP restransmission (as a result multiple
> > > PANA-Auth-Request message with carrying the same EAP message will =
be
> > > generated) and simply ignore the received PANA-PAA-Discover =
message.
> > > This way, the race condition can be resolved.
> > >=20
> > > Yoshihiro Ohba


----------
category: Technical
document: draft-ietf-pana-pana-xx.txt
messages: 125
nosy: dforsber
priority: Must Fix
status: Pending
title: Reauthentication race condition
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue36
________________________________________________

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


From exim@www1.ietf.org  Thu Oct  9 02:36:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08684
	for <pana-archive@odin.ietf.org>; Thu, 9 Oct 2003 02:36:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7UP8-0005PB-TB
	for pana-archive@odin.ietf.org; Thu, 09 Oct 2003 02:36:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h996a6kX020773
	for pana-archive@odin.ietf.org; Thu, 9 Oct 2003 02:36:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7UP8-0005Oo-2I
	for pana-web-archive@optimus.ietf.org; Thu, 09 Oct 2003 02:36:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08652
	for <pana-web-archive@ietf.org>; Thu, 9 Oct 2003 02:35:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7UP4-0002Oa-00
	for pana-web-archive@ietf.org; Thu, 09 Oct 2003 02:36:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7UP3-0002OX-00
	for pana-web-archive@ietf.org; Thu, 09 Oct 2003 02:36:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7UP3-0005OC-D8; Thu, 09 Oct 2003 02:36:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7UOs-0005Nj-8K
	for pana@optimus.ietf.org; Thu, 09 Oct 2003 02:35:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08644
	for <pana@ietf.org>; Thu, 9 Oct 2003 02:35:41 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7UOo-0002OL-00
	for pana@ietf.org; Thu, 09 Oct 2003 02:35:46 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7UOn-0002OI-00
	for pana@ietf.org; Thu, 09 Oct 2003 02:35:45 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h996Zk610496
	for <pana@ietf.org>; Thu, 9 Oct 2003 09:35:46 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T652c9c6c4aac158f25048@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Thu, 9 Oct 2003 09:35:45 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 9 Oct 2003 09:35:45 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 9 Oct 2003 09:35:44 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D53@esebe008.ntc.nokia.com>
Thread-Topic: [issue36] Reauthentication race condition
Thread-Index: AcOOL4DIoFr0OYO8Qqyg2lgmJfUWlwAAAa1Q
To: <pana@ietf.org>
X-OriginalArrivalTime: 09 Oct 2003 06:35:45.0642 (UTC) FILETIME=[91C06CA0:01C38E2F]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue36] Reauthentication race condition
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

New submission from Dan Forsberg <dan.forsberg@nokia.com>:

> > > There would be one issue in the latter case.  What happens if both =
PaC
> > > and PAA initate EAP level reauthentication at the same time?  When
> > > this happens, the PaC will send a PANA-PAA-Discover message while =
the
> > > PAA will send a PANA-Auth-Request message, according to the EAP =
level
> > > reauthentication behavior described in section 4.4.  In this case, =
the
> > > PAA can rely on the EAP restransmission (as a result multiple
> > > PANA-Auth-Request message with carrying the same EAP message will =
be
> > > generated) and simply ignore the received PANA-PAA-Discover =
message.
> > > This way, the race condition can be resolved.
> > >=20
> > > Yoshihiro Ohba


----------
category: Technical
document: draft-ietf-pana-pana-xx.txt
messages: 125
nosy: dforsber
priority: Must Fix
status: Pending
title: Reauthentication race condition
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue36
________________________________________________

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



From pana-admin@ietf.org  Thu Oct  9 12:15:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26320
	for <pana-archive@lists.ietf.org>; Thu, 9 Oct 2003 12:15:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dRO-0005gl-JV; Thu, 09 Oct 2003 12:15:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dQx-0005fh-4y
	for pana@optimus.ietf.org; Thu, 09 Oct 2003 12:14:35 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26271;
	Thu, 9 Oct 2003 12:14:25 -0400 (EDT)
Message-Id: <200310091614.MAA26271@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 09 Oct 2003 12:14:25 -0400
Subject: [Pana] I-D ACTION:draft-yacine-pana-paa2ep-prot-eval-00.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

--NextPart

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


	Title		: PANA PAA-EP protocol considerations
	Author(s)	: Y. Mghazli
	Filename	: draft-yacine-pana-paa2ep-prot-eval-00.txt
	Pages		: 21
	Date		: 2003-10-9
	
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 will identify a (preferably 
existing) protocol solution that allows the PAA to deliver the 
authorization information to one or more EPs when the PAA is 
separated from EPs. 
   
The present document aims at discussing the various protocol 
solutions available and identifying one, which better fits the whole 
PANA picture.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-yacine-pana-paa2ep-prot-eval-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-yacine-pana-paa2ep-prot-eval-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-yacine-pana-paa2ep-prot-eval-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.

--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:	<2003-10-9122445.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-yacine-pana-paa2ep-prot-eval-00.txt

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

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

--OtherAccess--

--NextPart--



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


From exim@www1.ietf.org  Thu Oct  9 12:15:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26337
	for <pana-archive@odin.ietf.org>; Thu, 9 Oct 2003 12:15:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dRS-0005hc-OJ
	for pana-archive@odin.ietf.org; Thu, 09 Oct 2003 12:15:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h99GF64k021914
	for pana-archive@odin.ietf.org; Thu, 9 Oct 2003 12:15:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dRS-0005hN-Fc
	for pana-web-archive@optimus.ietf.org; Thu, 09 Oct 2003 12:15:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26295
	for <pana-web-archive@ietf.org>; Thu, 9 Oct 2003 12:14:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7dRR-0000V0-00
	for pana-web-archive@ietf.org; Thu, 09 Oct 2003 12:15:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7dRQ-0000Ux-00
	for pana-web-archive@ietf.org; Thu, 09 Oct 2003 12:15:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dRO-0005gl-JV; Thu, 09 Oct 2003 12:15:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dQx-0005fh-4y
	for pana@optimus.ietf.org; Thu, 09 Oct 2003 12:14:35 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26271;
	Thu, 9 Oct 2003 12:14:25 -0400 (EDT)
Message-Id: <200310091614.MAA26271@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Thu, 09 Oct 2003 12:14:25 -0400
Subject: [Pana] I-D ACTION:draft-yacine-pana-paa2ep-prot-eval-00.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

--NextPart

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


	Title		: PANA PAA-EP protocol considerations
	Author(s)	: Y. Mghazli
	Filename	: draft-yacine-pana-paa2ep-prot-eval-00.txt
	Pages		: 21
	Date		: 2003-10-9
	
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 will identify a (preferably 
existing) protocol solution that allows the PAA to deliver the 
authorization information to one or more EPs when the PAA is 
separated from EPs. 
   
The present document aims at discussing the various protocol 
solutions available and identifying one, which better fits the whole 
PANA picture.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-yacine-pana-paa2ep-prot-eval-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-yacine-pana-paa2ep-prot-eval-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-yacine-pana-paa2ep-prot-eval-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.

--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:	<2003-10-9122445.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-yacine-pana-paa2ep-prot-eval-00.txt

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

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

--OtherAccess--

--NextPart--



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



From pana-admin@ietf.org  Thu Oct  9 12:32:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27138
	for <pana-archive@lists.ietf.org>; Thu, 9 Oct 2003 12:32:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dhp-0006L5-4B; Thu, 09 Oct 2003 12:32:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dhi-0006Kh-03
	for pana@optimus.ietf.org; Thu, 09 Oct 2003 12:31:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27113
	for <pana@ietf.org>; Thu, 9 Oct 2003 12:31:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7dhg-0000k1-00
	for pana@ietf.org; Thu, 09 Oct 2003 12:31:52 -0400
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7dhf-0000jR-00
	for pana@ietf.org; Thu, 09 Oct 2003 12:31:51 -0400
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id h99GVJSS010494
	for <pana@ietf.org>; Thu, 9 Oct 2003 18:31:19 +0200
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003100918311866:5986 ;
          Thu, 9 Oct 2003 18:31:18 +0200 
Message-ID: <3F858D56.1070206@alcatel.fr>
Date: Thu, 09 Oct 2003 18:31:18 +0200
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: pana@ietf.org
Subject: Re: [Pana] I-D ACTION:draft-yacine-pana-paa2ep-prot-eval-00.txt
References: <200310091614.MAA26271@ietf.org>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/09/2003 18:31:18,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/09/2003 18:31:19
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: by amavisd-new
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hello all,

Can people involved in the subject please have a look at this I-D and=20
comment on the list.

It would be great if we could hear opinions on the issues raised up=20
about the multiple PAAs deployments, but I guess the most important is=20
to discuss the PAA-EP protocol alternatives. this draft suggets SNMP as=20
the mandatory one.

Thanks,
Yacine



Internet-Drafts@ietf.org a =E9crit:
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>=20
>=20
> 	Title		: PANA PAA-EP protocol considerations
> 	Author(s)	: Y. Mghazli
> 	Filename	: draft-yacine-pana-paa2ep-prot-eval-00.txt
> 	Pages		: 21
> 	Date		: 2003-10-9
> =09
> The PANA Authentication Agent (PAA) does not necessarily act as an=20
> Enforcement Point (EP) to prevent unauthorized access or usage of the=20
> network. When a PANA Client (PaC) successfully authenticates itself=20
> to the PAA, EP(s) (e.g., access routers) will need to be suitably=20
> notified. The PANA working group will identify a (preferably=20
> existing) protocol solution that allows the PAA to deliver the=20
> authorization information to one or more EPs when the PAA is=20
> separated from EPs.=20
>   =20
> The present document aims at discussing the various protocol=20
> solutions available and identifying one, which better fits the whole=20
> PANA picture.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-yacine-pana-paa2ep-prot-eval-00=
.txt
>=20
> To remove yourself from the IETF Announcement list, send a message to=20
> ietf-announce-request with the word unsubscribe in the body of the messag=
e.
>=20
> Internet-Drafts are also available by anonymous FTP. Login with the usern=
ame
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-yacine-pana-paa2ep-prot-eval-00.txt".
>=20
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html=20
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-yacine-pana-paa2ep-prot-eval-00.txt".
> =09
> 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.
> 	=09
> 	=09
> 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 exim@www1.ietf.org  Thu Oct  9 12:32:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27153
	for <pana-archive@odin.ietf.org>; Thu, 9 Oct 2003 12:32:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dhs-0006Le-Ta
	for pana-archive@odin.ietf.org; Thu, 09 Oct 2003 12:32:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h99GW463024403
	for pana-archive@odin.ietf.org; Thu, 9 Oct 2003 12:32:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dhs-0006LW-Hf
	for pana-web-archive@optimus.ietf.org; Thu, 09 Oct 2003 12:32:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27117
	for <pana-web-archive@ietf.org>; Thu, 9 Oct 2003 12:31:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7dhr-0000k7-00
	for pana-web-archive@ietf.org; Thu, 09 Oct 2003 12:32:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7dhq-0000k4-00
	for pana-web-archive@ietf.org; Thu, 09 Oct 2003 12:32:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dhp-0006L5-4B; Thu, 09 Oct 2003 12:32:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7dhi-0006Kh-03
	for pana@optimus.ietf.org; Thu, 09 Oct 2003 12:31:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27113
	for <pana@ietf.org>; Thu, 9 Oct 2003 12:31:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7dhg-0000k1-00
	for pana@ietf.org; Thu, 09 Oct 2003 12:31:52 -0400
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7dhf-0000jR-00
	for pana@ietf.org; Thu, 09 Oct 2003 12:31:51 -0400
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id h99GVJSS010494
	for <pana@ietf.org>; Thu, 9 Oct 2003 18:31:19 +0200
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003100918311866:5986 ;
          Thu, 9 Oct 2003 18:31:18 +0200 
Message-ID: <3F858D56.1070206@alcatel.fr>
Date: Thu, 09 Oct 2003 18:31:18 +0200
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: pana@ietf.org
Subject: Re: [Pana] I-D ACTION:draft-yacine-pana-paa2ep-prot-eval-00.txt
References: <200310091614.MAA26271@ietf.org>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/09/2003 18:31:18,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/09/2003 18:31:19
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: by amavisd-new
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hello all,

Can people involved in the subject please have a look at this I-D and=20
comment on the list.

It would be great if we could hear opinions on the issues raised up=20
about the multiple PAAs deployments, but I guess the most important is=20
to discuss the PAA-EP protocol alternatives. this draft suggets SNMP as=20
the mandatory one.

Thanks,
Yacine



Internet-Drafts@ietf.org a =E9crit:
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>=20
>=20
> 	Title		: PANA PAA-EP protocol considerations
> 	Author(s)	: Y. Mghazli
> 	Filename	: draft-yacine-pana-paa2ep-prot-eval-00.txt
> 	Pages		: 21
> 	Date		: 2003-10-9
> =09
> The PANA Authentication Agent (PAA) does not necessarily act as an=20
> Enforcement Point (EP) to prevent unauthorized access or usage of the=20
> network. When a PANA Client (PaC) successfully authenticates itself=20
> to the PAA, EP(s) (e.g., access routers) will need to be suitably=20
> notified. The PANA working group will identify a (preferably=20
> existing) protocol solution that allows the PAA to deliver the=20
> authorization information to one or more EPs when the PAA is=20
> separated from EPs.=20
>   =20
> The present document aims at discussing the various protocol=20
> solutions available and identifying one, which better fits the whole=20
> PANA picture.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-yacine-pana-paa2ep-prot-eval-00=
.txt
>=20
> To remove yourself from the IETF Announcement list, send a message to=20
> ietf-announce-request with the word unsubscribe in the body of the messag=
e.
>=20
> Internet-Drafts are also available by anonymous FTP. Login with the usern=
ame
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-yacine-pana-paa2ep-prot-eval-00.txt".
>=20
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html=20
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-yacine-pana-paa2ep-prot-eval-00.txt".
> =09
> 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.
> 	=09
> 	=09
> 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-request@research.telcordia.com  Thu Oct  9 13:55:44 2003
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01521
	for <pana-archive@lists.ietf.org>; Thu, 9 Oct 2003 13:55:43 -0400 (EDT)
Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8])
	by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id h99Hnies024700;
	Thu, 9 Oct 2003 13:49:44 -0400 (EDT)
Received: (from slmgr@localhost)
	by donner.research.telcordia.com (8.8.8/8.8.8) id NAA04080;
	Thu, 9 Oct 2003 13:49:43 -0400 (EDT)
Resent-Date: Thu, 9 Oct 2003 13:49:43 -0400 (EDT)
X-Authentication-Warning: donner.research.telcordia.com: slmgr set sender to pana-request@research.telcordia.com using -f
Old-Return-Path: <yohba@tari.toshiba.com>
Date: Thu, 09 Oct 2003 10:48:16 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: New [issue25] Service Profile names
In-reply-to: <BB9878E8.9416%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Dan.Forsberg@nokia.com, pana@research.telcordia.com
Message-id: <20031009174816.GA8231@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Dan.Forsberg@nokia.com, pana@research.telcordia.com
User-Agent: Mutt/1.5.4i
References: <20030911175353.GI14569@steelhead>
 <BB9878E8.9416%alper@docomolabs-usa.com>
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi)
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper)
Resent-Message-ID: <ztRUCB.A.n_.3-Zh_@donner>
Resent-From: pana@research.telcordia.com
X-Mailing-List: <pana@research.telcordia.com> 
X-Loop: pana@research.telcordia.com
List-Post: <mailto:pana@research.telcordia.com>
List-Help: <mailto:pana-request@research.telcordia.com?subject=help>
Precedence: list
Resent-Sender: pana-request@research.telcordia.com

In the initial text I recently provided, one NAP-Information AVP and
zero or more ISP-Information AVPs can optionally be carried in
PANA-Start-Request, where each AVP includes a unique (IANA-assigned)
provider identifier and a provider name.

When there are multiple PAAs, this kind of information could 
be used by PaC to choose a PAA.  So this issue might result in 
re-consideration of the current PAA selection procedure:

  "There can be multiple PAAs on the link. The result does not depend
  on which PAA PaC chooses. By default PaC chooses the PAA that sent
  the first response."

Note that section 4 of draft-yacine-pana-paa2ep-prot-eval-00.txt also
addresses a similer issue.

Yoshihiro Ohba



On Thu, Sep 25, 2003 at 10:50:16AM -0700, Alper Yegin wrote:
> 
> This piece of data sounds informative and potentially useful. I presume if
> we wanted to have this support, we'd define a new AVP that carries some sort
> of an "identifier" and optionally carried in PANA-Start-Request. Do we have
> to define the format of the data this AVP embeds? What type of information
> would the data be carrying?
> 
> 
> Alper
> 
> 
> > I think more about this issue and now I tend to agree that the
> > proposed functionality might be useful even if there is one PAA on an
> > IP link.  First, there may be multiple IP links available at a
> > physical location (e.g., a hotspot).  In such a case, if
> > PANA-Start-Request messages sent by PAAs contain some profile
> > information, a PaC can use the information to choose an appropriate IP
> > link to start authentication.  Second, even if there is only one IP
> > link in a physical location and one PAA on the link, a PaC can use the
> > information to determine whether it starts authentication on the IP
> > link or not.
> > 
> > Yoshihiro Ohba
> > 
> > 
> > 
> > On Wed, Sep 10, 2003 at 02:22:14PM +0300, Dan.Forsberg@nokia.com wrote:
> >> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> >> 
> >>> From Reinaldo Penno:
> >> <klip>
> >>> 3) In section 4.2, paragraph 3 it is mentioned that
> >>> "The result does not depend on which PAA PaC chooses.
> >>> By default PaC chooses the PAA that sent the first
> >>> reponse"
> >>> 
> >>> This is the DHCP approach. Where all servers are
> >>> equally good. 
> >>> 
> >>> I would propose that we think about incorporating
> >>> something of the PPPoE protocol that is widespread,
> >>> since PANA is more related to the PPPoE model.
> >>> 
> >>> In the response of the Discovery message each PPPoE
> >>> server include all the Service Profile (names) it
> >>> supports (the definition is loose on purpose).
> >>> Nowadays it is usually a list of ISPs or bandwidth
> >>> packages a user can choose.
> >>> 
> >>> I would argue that in the case of PANA (and specially
> >>> in the case of NAP vs ISP authentication), PAA servers
> >>> might support a very different set of attributes and a
> >>> PaC might prefer one over the other if it new of each
> >>> choices.
> >>> 
> >>> We could have a AVP in PANA for that purpose in the
> >>> answer to the Discovery message. it seems very simple,
> >>> could be optional and will provide a crucial
> >>> functionality for people that use PPPoE to migrate to
> >>> PANA.
> >> 
> >> Yoshihiro Ohba:
> >> 
> >> When we dicussed NAP and ISP separate authentication, I think the
> >> assumption is that there is a single PAA the PaC sees, and the NAI is
> >> used to choose a particular ISP.  Why do you need multiple PAAs to
> >> support NAP and ISP separate authentication?
> >> 
> >> 
> >> ----------
> >> category: Technical
> >> document: draft-ietf-pana-pana-xx.txt
> >> messages: 80
> >> nosy: dforsber
> >> priority: May Fix
> >> status: Pending
> >> title: Service Profile names
> >> ________________________________________________
> >> PANA Issues <pana_issues@danforsberg.info>
> >> http://danforsberg.info:8080/pana-issues/issue25
> >> ________________________________________________
> >> 
> > 
> > 
> 



From pana-admin@ietf.org  Thu Oct  9 20:37:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18966
	for <pana-archive@lists.ietf.org>; Thu, 9 Oct 2003 20:37:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7lHA-0003sq-Vx; Thu, 09 Oct 2003 20:37:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7lH4-0003sL-5N
	for pana@optimus.ietf.org; Thu, 09 Oct 2003 20:36:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18948
	for <pana@ietf.org>; Thu, 9 Oct 2003 20:36:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7lH1-0006t0-00
	for pana@ietf.org; Thu, 09 Oct 2003 20:36:51 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7lH0-0006ss-00
	for pana@ietf.org; Thu, 09 Oct 2003 20:36:50 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9A0ahF1005357;
	Fri, 10 Oct 2003 09:36:43 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9A0ahMr019489;
	Fri, 10 Oct 2003 09:36:43 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id KAA19487 ; Fri, 10 Oct 2003 09:36:43 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA27798; Fri, 10 Oct 2003 09:36:42 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA16990; Fri, 10 Oct 2003 09:36:42 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9A0afqT007990;
	Fri, 10 Oct 2003 09:36:41 +0900 (JST)
Received: from steelhead ([159.119.168.78]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMI004K2N148T@tsbpo1.po.toshiba.co.jp>; Fri,
 10 Oct 2003 09:36:40 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A7lEq-00038Y-00; Thu, 09 Oct 2003 17:34:36 -0700
Date: Thu, 09 Oct 2003 17:34:36 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue34] Behaviour with NAP and ISP (two
 EAPauthentications).
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C58D@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: alper@docomolabs-usa.com, pana@ietf.org
Message-id: <20031010003436.GB11621@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, alper@docomolabs-usa.com,
 pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C58D@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Mon, Oct 06, 2003 at 04:03:42PM +0300, Dan.Forsberg@nokia.com wrote:
> I'm just thinking of what is the benefit of binding two EAP authentications into one PANA session? This already makes the system complex and we encounter problems like this. Where did this idea come from anyways? The original NAP and ISP scenario (coffee shop) for my understanding was related to issue25, not with two EAP authentications.

Although Issue 25 is related to NAP/ISP scenario, the NAP/ISP scenario
did not originally came up from issue 25.  When the NAP/ISP scenario
was discussed on the ML long before, we first tried to use sequenced
EAP methods within a single EAP authentication (one EAP method for NAP
authentication and the other EAP method for ISP authentication).
However, since the EAP WG decided not to allow sequence of methods
outside a tunneling method, we came up with our own solution (i.e.,
running two EAP authentications inside a single PANA session) as a
natural outcome.

Yoshihiro Ohba



> 
> If PaC sees only a "combined session", how does it know which EAP method to use for reauthentcation. EAP doesn't have sessions, so we can't say it's an EAP level issue. Looking from the network perspective the two separate EAP authentications may create separate sessions (different AAA backends) with different session lifetimes..
> 
> From Yoshihiro's email below:
> "On the other hand, consideration is needed for this approach to handle different session lifetimes for NAP and ISP, as you also mentioned below. One solution to deal with this is to perform both EAP-based re-authentications for both NAP and ISP with using the minimum value of the NAP and ISP session lifetimes as the PANA session lifetime (though this is not efficient when the difference between the NAP and ISP session lifetimes are large.)"
> 
> 
> - Dan
> 
> 
> > -----Original Message-----
> > From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > Sent: 02 October, 2003 21:54
> > To: Yoshihiro Ohba; Forsberg Dan (NRC/Helsinki)
> > Cc: pana@ietf.org
> > Subject: Re: [Pana] [issue34] Behaviour with NAP and ISP (two
> > EAPauthentications).
> > 
> > 
> > 
> > This is what we said in the requirements draft:
> > 
> >    Determining the authorization
> >    parameters as a result of two separate authentications is an
> >    operational issue and therefore it is outside the scope of PANA.
> > 
> > I think from PANA perspective, it is sufficient to enable two 
> > rounds of
> > authentication. But other than that, we should let the NAS 
> > mold NAP and ISP
> > authentication into a single "PANA session". How exactly this 
> > be done should
> > not be the concern of the base pana protocol. And once there 
> > is a session,
> > neither PAA nor PaC would see "ISP session" or "NAP session", 
> > it is just a
> > "combined session".
> > 
> > Cost (complexity) of separating NAP and ISP authentication 
> > beyond what we
> > already provide seems higher than the benefits, imo.
> > 
> > Alper
> > 
> > 
> > 
> > 
> > 
> > > This is an interesting issue.
> > > 
> > > Basically there are pros and cons as to whether using a 
> > distinct PANA
> > > session for each of two EAP authentication or using a single PANA
> > > session for two EAP authentications.
> > > 
> > > As you mentioned, using a distinct PANA session for each of NAP and
> > > ISP authentications will make it easier to handle different session
> > > lifetimes for NAP and ISP.  However, there would be the
> > > following cons in this approach:
> > > 
> > > o Which PANA SA should be used for bootstrapping IPsec and/or DHCP
> > > authentication?
> > > 
> > > o What happens if the PANA session from which IPsec and/or DHCP
> > > authentication are bootstrapped is terminated while the other PANA
> > > session still remains established.
> > > 
> > > Especially the latter issue would be more difficult to solve and I
> > > don't recommend this approach.
> > > 
> > > Using a singel PANA session for both NAP and ISP 
> > authentications does
> > > not have above the issues because there is only one PANA SA (and we
> > > already decided to use the MSK of the first successul EAP
> > > authentication with key derivation to derive the PANA SA).  
> > This also
> > > implies that when a PANA session is terminated, both NAP and ISP
> > > authorizations will be removed.  On the other hand, consideration is
> > > needed for this approach to handle different session 
> > lifetimes for NAP
> > > and ISP, as you also mentioned below.  One solution to deal 
> > with this
> > > is to perform both EAP-based re-authentications for both NAP and ISP
> > > with using the minimum value of the NAP and ISP session lifetimes as
> > > the PANA session lifetime (though this is not efficient when the
> > > difference between the NAP and ISP session lifetimes are large.)
> > > 
> > > What do you think?
> > > 
> > > Yoshihiro Ohba
> > > 
> > > 
> > > 
> > > On Wed, Oct 01, 2003 at 01:53:00PM +0300, 
> > Dan.Forsberg@nokia.com wrote:
> > >> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> > >> 
> > >> How does Session-Lifetime (or Session-Timeout) realate to 
> > NAP and ISP
> > >> authentications? When this lifetime expires PaC should probably
> > >> reauthenticate to NAP and ISP?
> > >> 
> > >> Clarification needed into the draft also for the case of session
> > >> terminateion. Does PaC or PAA terminate the part of the 
> > session that
> > >> relates to the ISP or NAP or both.
> > >> 
> > >> Would it be simpler to use PANA sessions with one EAP method only,
> > >> instead of two serial EAP methods in one session. Or 
> > should there be one
> > >> master session (NAP) and then subsessions (for ISPs). When 
> > the master
> > >> session is terminated, the subsessions are also 
> > terminated. PaC and PAA
> > >> can also terminate subsessions. Reauthentication should 
> > happen for all
> > >> the sessions because of independent EAP methods.
> > >> 
> > >> - Dan
> > >> 
> > >> 
> > >> ----------
> > >> category: Technical
> > >> document: draft-ietf-pana-pana-xx.txt
> > >> messages: 105
> > >> nosy: dforsber
> > >> priority: Must Fix
> > >> status: No Discussion
> > >> title: Behaviour with NAP and ISP (two EAP authentications).
> > >> ________________________________________________
> > >> PANA Issues <pana_issues@danforsberg.info>
> > >> http://danforsberg.info:8080/pana-issues/issue34
> > >> ________________________________________________
> > >> 
> > >> _______________________________________________
> > >> Pana mailing list
> > >> Pana@ietf.org
> > >> https://www1.ietf.org/mailman/listinfo/pana
> > > 
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > > 
> > 
> > 

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


From exim@www1.ietf.org  Thu Oct  9 20:37:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18981
	for <pana-archive@odin.ietf.org>; Thu, 9 Oct 2003 20:37:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7lHG-0003uX-Bm
	for pana-archive@odin.ietf.org; Thu, 09 Oct 2003 20:37:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9A0b6TE015032
	for pana-archive@odin.ietf.org; Thu, 9 Oct 2003 20:37:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7lHG-0003uM-0K
	for pana-web-archive@optimus.ietf.org; Thu, 09 Oct 2003 20:37:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18957
	for <pana-web-archive@ietf.org>; Thu, 9 Oct 2003 20:36:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7lHD-0006tE-00
	for pana-web-archive@ietf.org; Thu, 09 Oct 2003 20:37:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7lHD-0006tA-00
	for pana-web-archive@ietf.org; Thu, 09 Oct 2003 20:37:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7lHA-0003sq-Vx; Thu, 09 Oct 2003 20:37:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7lH4-0003sL-5N
	for pana@optimus.ietf.org; Thu, 09 Oct 2003 20:36:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18948
	for <pana@ietf.org>; Thu, 9 Oct 2003 20:36:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7lH1-0006t0-00
	for pana@ietf.org; Thu, 09 Oct 2003 20:36:51 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7lH0-0006ss-00
	for pana@ietf.org; Thu, 09 Oct 2003 20:36:50 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9A0ahF1005357;
	Fri, 10 Oct 2003 09:36:43 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9A0ahMr019489;
	Fri, 10 Oct 2003 09:36:43 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id KAA19487 ; Fri, 10 Oct 2003 09:36:43 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA27798; Fri, 10 Oct 2003 09:36:42 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA16990; Fri, 10 Oct 2003 09:36:42 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9A0afqT007990;
	Fri, 10 Oct 2003 09:36:41 +0900 (JST)
Received: from steelhead ([159.119.168.78]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMI004K2N148T@tsbpo1.po.toshiba.co.jp>; Fri,
 10 Oct 2003 09:36:40 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A7lEq-00038Y-00; Thu, 09 Oct 2003 17:34:36 -0700
Date: Thu, 09 Oct 2003 17:34:36 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue34] Behaviour with NAP and ISP (two
 EAPauthentications).
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C58D@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: alper@docomolabs-usa.com, pana@ietf.org
Message-id: <20031010003436.GB11621@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, alper@docomolabs-usa.com,
 pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C58D@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Mon, Oct 06, 2003 at 04:03:42PM +0300, Dan.Forsberg@nokia.com wrote:
> I'm just thinking of what is the benefit of binding two EAP authentications into one PANA session? This already makes the system complex and we encounter problems like this. Where did this idea come from anyways? The original NAP and ISP scenario (coffee shop) for my understanding was related to issue25, not with two EAP authentications.

Although Issue 25 is related to NAP/ISP scenario, the NAP/ISP scenario
did not originally came up from issue 25.  When the NAP/ISP scenario
was discussed on the ML long before, we first tried to use sequenced
EAP methods within a single EAP authentication (one EAP method for NAP
authentication and the other EAP method for ISP authentication).
However, since the EAP WG decided not to allow sequence of methods
outside a tunneling method, we came up with our own solution (i.e.,
running two EAP authentications inside a single PANA session) as a
natural outcome.

Yoshihiro Ohba



> 
> If PaC sees only a "combined session", how does it know which EAP method to use for reauthentcation. EAP doesn't have sessions, so we can't say it's an EAP level issue. Looking from the network perspective the two separate EAP authentications may create separate sessions (different AAA backends) with different session lifetimes..
> 
> From Yoshihiro's email below:
> "On the other hand, consideration is needed for this approach to handle different session lifetimes for NAP and ISP, as you also mentioned below. One solution to deal with this is to perform both EAP-based re-authentications for both NAP and ISP with using the minimum value of the NAP and ISP session lifetimes as the PANA session lifetime (though this is not efficient when the difference between the NAP and ISP session lifetimes are large.)"
> 
> 
> - Dan
> 
> 
> > -----Original Message-----
> > From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > Sent: 02 October, 2003 21:54
> > To: Yoshihiro Ohba; Forsberg Dan (NRC/Helsinki)
> > Cc: pana@ietf.org
> > Subject: Re: [Pana] [issue34] Behaviour with NAP and ISP (two
> > EAPauthentications).
> > 
> > 
> > 
> > This is what we said in the requirements draft:
> > 
> >    Determining the authorization
> >    parameters as a result of two separate authentications is an
> >    operational issue and therefore it is outside the scope of PANA.
> > 
> > I think from PANA perspective, it is sufficient to enable two 
> > rounds of
> > authentication. But other than that, we should let the NAS 
> > mold NAP and ISP
> > authentication into a single "PANA session". How exactly this 
> > be done should
> > not be the concern of the base pana protocol. And once there 
> > is a session,
> > neither PAA nor PaC would see "ISP session" or "NAP session", 
> > it is just a
> > "combined session".
> > 
> > Cost (complexity) of separating NAP and ISP authentication 
> > beyond what we
> > already provide seems higher than the benefits, imo.
> > 
> > Alper
> > 
> > 
> > 
> > 
> > 
> > > This is an interesting issue.
> > > 
> > > Basically there are pros and cons as to whether using a 
> > distinct PANA
> > > session for each of two EAP authentication or using a single PANA
> > > session for two EAP authentications.
> > > 
> > > As you mentioned, using a distinct PANA session for each of NAP and
> > > ISP authentications will make it easier to handle different session
> > > lifetimes for NAP and ISP.  However, there would be the
> > > following cons in this approach:
> > > 
> > > o Which PANA SA should be used for bootstrapping IPsec and/or DHCP
> > > authentication?
> > > 
> > > o What happens if the PANA session from which IPsec and/or DHCP
> > > authentication are bootstrapped is terminated while the other PANA
> > > session still remains established.
> > > 
> > > Especially the latter issue would be more difficult to solve and I
> > > don't recommend this approach.
> > > 
> > > Using a singel PANA session for both NAP and ISP 
> > authentications does
> > > not have above the issues because there is only one PANA SA (and we
> > > already decided to use the MSK of the first successul EAP
> > > authentication with key derivation to derive the PANA SA).  
> > This also
> > > implies that when a PANA session is terminated, both NAP and ISP
> > > authorizations will be removed.  On the other hand, consideration is
> > > needed for this approach to handle different session 
> > lifetimes for NAP
> > > and ISP, as you also mentioned below.  One solution to deal 
> > with this
> > > is to perform both EAP-based re-authentications for both NAP and ISP
> > > with using the minimum value of the NAP and ISP session lifetimes as
> > > the PANA session lifetime (though this is not efficient when the
> > > difference between the NAP and ISP session lifetimes are large.)
> > > 
> > > What do you think?
> > > 
> > > Yoshihiro Ohba
> > > 
> > > 
> > > 
> > > On Wed, Oct 01, 2003 at 01:53:00PM +0300, 
> > Dan.Forsberg@nokia.com wrote:
> > >> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> > >> 
> > >> How does Session-Lifetime (or Session-Timeout) realate to 
> > NAP and ISP
> > >> authentications? When this lifetime expires PaC should probably
> > >> reauthenticate to NAP and ISP?
> > >> 
> > >> Clarification needed into the draft also for the case of session
> > >> terminateion. Does PaC or PAA terminate the part of the 
> > session that
> > >> relates to the ISP or NAP or both.
> > >> 
> > >> Would it be simpler to use PANA sessions with one EAP method only,
> > >> instead of two serial EAP methods in one session. Or 
> > should there be one
> > >> master session (NAP) and then subsessions (for ISPs). When 
> > the master
> > >> session is terminated, the subsessions are also 
> > terminated. PaC and PAA
> > >> can also terminate subsessions. Reauthentication should 
> > happen for all
> > >> the sessions because of independent EAP methods.
> > >> 
> > >> - Dan
> > >> 
> > >> 
> > >> ----------
> > >> category: Technical
> > >> document: draft-ietf-pana-pana-xx.txt
> > >> messages: 105
> > >> nosy: dforsber
> > >> priority: Must Fix
> > >> status: No Discussion
> > >> title: Behaviour with NAP and ISP (two EAP authentications).
> > >> ________________________________________________
> > >> PANA Issues <pana_issues@danforsberg.info>
> > >> http://danforsberg.info:8080/pana-issues/issue34
> > >> ________________________________________________
> > >> 
> > >> _______________________________________________
> > >> Pana mailing list
> > >> Pana@ietf.org
> > >> https://www1.ietf.org/mailman/listinfo/pana
> > > 
> > > _______________________________________________
> > > Pana mailing list
> > > Pana@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/pana
> > > 
> > 
> > 

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



From pana-admin@ietf.org  Fri Oct 10 08:54:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25990
	for <pana-archive@lists.ietf.org>; Fri, 10 Oct 2003 08:54:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7wmP-0000vT-QT; Fri, 10 Oct 2003 08:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7wlh-0000s7-6o
	for pana@optimus.ietf.org; Fri, 10 Oct 2003 08:53:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25935
	for <pana@ietf.org>; Fri, 10 Oct 2003 08:53:04 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7wla-0002x6-00
	for pana@ietf.org; Fri, 10 Oct 2003 08:53:11 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7wla-0002x2-00
	for pana@ietf.org; Fri, 10 Oct 2003 08:53:10 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h9ACr8619074
	for <pana@ietf.org>; Fri, 10 Oct 2003 15:53:08 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65331c4420ac158f21083@esvir01nok.ntc.nokia.com> for <pana@ietf.org>;
 Fri, 10 Oct 2003 15:53:07 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 10 Oct 2003 15:53:06 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 10 Oct 2003 15:53:06 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5A0@esebe008.ntc.nokia.com>
Thread-Topic: EAP-Request/Identity & PANA-Start-Request
Thread-Index: AcOPLXLyy1iJorY5Ta2sGSs8J0VWlg==
To: <pana@ietf.org>
X-OriginalArrivalTime: 10 Oct 2003 12:53:06.0925 (UTC) FILETIME=[736BC9D0:01C38F2D]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] EAP-Request/Identity & PANA-Start-Request
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

PANA folks,

We have PANA-Start-Request/Answer messgae pair carrying Cookie.
Then we have the first PANA-Auth-Request/Answer message pair=20
carrying EAP-Request/Identity and EAP-Response/Identity. The=20
EAP-Request/Identity is generated in the PAA/NAS, because/which=20
at that point doesn't know the realm for the user. EAP header=20
also contains the identifier field which is somewhat analoguous=20
to PANA cookie. Why not to put the first EAP payload AVP into=20
the PANA-Start-Request message? This doesn't bring any new=20
requirements for the PAA to create state information, because=20
the EAP header identifier field can act similarly to PANA cookie=20
AVP... or in the extreme we could drop the cookie AVP and use=20
the EAP identifier field as the "cookie".

Let me hear your comments.

Br,
- Dan

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


From exim@www1.ietf.org  Fri Oct 10 08:54:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26007
	for <pana-archive@odin.ietf.org>; Fri, 10 Oct 2003 08:54:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7wmU-0000wW-WF
	for pana-archive@odin.ietf.org; Fri, 10 Oct 2003 08:54:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9ACs6fR003624
	for pana-archive@odin.ietf.org; Fri, 10 Oct 2003 08:54:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7wmU-0000wN-RH
	for pana-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 08:54:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25977
	for <pana-web-archive@ietf.org>; Fri, 10 Oct 2003 08:53:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7wmT-0002yK-00
	for pana-web-archive@ietf.org; Fri, 10 Oct 2003 08:54:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7wmT-0002yF-00
	for pana-web-archive@ietf.org; Fri, 10 Oct 2003 08:54:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7wmP-0000vT-QT; Fri, 10 Oct 2003 08:54:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7wlh-0000s7-6o
	for pana@optimus.ietf.org; Fri, 10 Oct 2003 08:53:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25935
	for <pana@ietf.org>; Fri, 10 Oct 2003 08:53:04 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7wla-0002x6-00
	for pana@ietf.org; Fri, 10 Oct 2003 08:53:11 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7wla-0002x2-00
	for pana@ietf.org; Fri, 10 Oct 2003 08:53:10 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.6) with ESMTP id h9ACr8619074
	for <pana@ietf.org>; Fri, 10 Oct 2003 15:53:08 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65331c4420ac158f21083@esvir01nok.ntc.nokia.com> for <pana@ietf.org>;
 Fri, 10 Oct 2003 15:53:07 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 10 Oct 2003 15:53:06 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 10 Oct 2003 15:53:06 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5A0@esebe008.ntc.nokia.com>
Thread-Topic: EAP-Request/Identity & PANA-Start-Request
Thread-Index: AcOPLXLyy1iJorY5Ta2sGSs8J0VWlg==
To: <pana@ietf.org>
X-OriginalArrivalTime: 10 Oct 2003 12:53:06.0925 (UTC) FILETIME=[736BC9D0:01C38F2D]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] EAP-Request/Identity & PANA-Start-Request
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

PANA folks,

We have PANA-Start-Request/Answer messgae pair carrying Cookie.
Then we have the first PANA-Auth-Request/Answer message pair=20
carrying EAP-Request/Identity and EAP-Response/Identity. The=20
EAP-Request/Identity is generated in the PAA/NAS, because/which=20
at that point doesn't know the realm for the user. EAP header=20
also contains the identifier field which is somewhat analoguous=20
to PANA cookie. Why not to put the first EAP payload AVP into=20
the PANA-Start-Request message? This doesn't bring any new=20
requirements for the PAA to create state information, because=20
the EAP header identifier field can act similarly to PANA cookie=20
AVP... or in the extreme we could drop the cookie AVP and use=20
the EAP identifier field as the "cookie".

Let me hear your comments.

Br,
- Dan

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



From pana-admin@ietf.org  Fri Oct 10 11:38:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03921
	for <pana-archive@lists.ietf.org>; Fri, 10 Oct 2003 11:38:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7zLA-0003DW-4E; Fri, 10 Oct 2003 11:38:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7zKT-00032h-Hq
	for pana@optimus.ietf.org; Fri, 10 Oct 2003 11:37:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03860
	for <pana@ietf.org>; Fri, 10 Oct 2003 11:37:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7zKS-0005CU-00
	for pana@ietf.org; Fri, 10 Oct 2003 11:37:20 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7zKR-0005CL-00
	for pana@ietf.org; Fri, 10 Oct 2003 11:37:19 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9AFbGF1005117;
	Sat, 11 Oct 2003 00:37:16 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9AFbDV8006684;
	Sat, 11 Oct 2003 00:37:13 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id AAA06682 ; Sat, 11 Oct 2003 00:37:13 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA25759; Sat, 11 Oct 2003 00:37:13 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA23896; Sat, 11 Oct 2003 00:37:12 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9AFbCqT027607;
	Sat, 11 Oct 2003 00:37:12 +0900 (JST)
Received: from steelhead ([159.119.168.131]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMJ0092TSPXWF@tsbpo1.po.toshiba.co.jp>; Sat,
 11 Oct 2003 00:37:11 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A7zI1-0003YV-00; Fri, 10 Oct 2003 08:34:49 -0700
Date: Fri, 10 Oct 2003 08:34:44 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5A0@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20031010153444.GB13449@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5A0@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 10, 2003 at 03:53:06PM +0300, Dan.Forsberg@nokia.com wrote:
> PANA folks,
> 
> We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> Then we have the first PANA-Auth-Request/Answer message pair 
> carrying EAP-Request/Identity and EAP-Response/Identity. The 
> EAP-Request/Identity is generated in the PAA/NAS, because/which 
> at that point doesn't know the realm for the user. EAP header 
> also contains the identifier field which is somewhat analoguous 
> to PANA cookie. Why not to put the first EAP payload AVP into 
> the PANA-Start-Request message? This doesn't bring any new 
> requirements for the PAA to create state information, because 
> the EAP header identifier field can act similarly to PANA cookie 
> AVP... or in the extreme we could drop the cookie AVP and use 
> the EAP identifier field as the "cookie".

There are two things we need to consider here:

o The first EAP Request sent by the EAP authenticator is not always
  EAP-Request/Identity, i.e., the use of EAP-Request/Identity is optional when
  the client identity can be obtained by some other means.

o EAP state machine (draft-ietf-eap-statemachines-00.{txt,ps}) does
  not allow an EAP authenticator to be stateless when sending the first EAP Request.

So in general PAA cannot be stateless when sending a PANA-Start-Request 
with piggybacking an EAP Request.

Yoshihiro Ohba



> 
> Let me hear your comments.
> 
> Br,
> - Dan
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Fri Oct 10 11:38:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03936
	for <pana-archive@odin.ietf.org>; Fri, 10 Oct 2003 11:38:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7zLG-0003EN-Oe
	for pana-archive@odin.ietf.org; Fri, 10 Oct 2003 11:38:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AFc9TQ012411
	for pana-archive@odin.ietf.org; Fri, 10 Oct 2003 11:38:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7zLE-0003E6-7C
	for pana-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 11:38:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03908
	for <pana-web-archive@ietf.org>; Fri, 10 Oct 2003 11:37:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7zLD-0005DL-00
	for pana-web-archive@ietf.org; Fri, 10 Oct 2003 11:38:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7zLC-0005DI-00
	for pana-web-archive@ietf.org; Fri, 10 Oct 2003 11:38:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7zLA-0003DW-4E; Fri, 10 Oct 2003 11:38:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7zKT-00032h-Hq
	for pana@optimus.ietf.org; Fri, 10 Oct 2003 11:37:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03860
	for <pana@ietf.org>; Fri, 10 Oct 2003 11:37:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7zKS-0005CU-00
	for pana@ietf.org; Fri, 10 Oct 2003 11:37:20 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7zKR-0005CL-00
	for pana@ietf.org; Fri, 10 Oct 2003 11:37:19 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9AFbGF1005117;
	Sat, 11 Oct 2003 00:37:16 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9AFbDV8006684;
	Sat, 11 Oct 2003 00:37:13 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id AAA06682 ; Sat, 11 Oct 2003 00:37:13 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA25759; Sat, 11 Oct 2003 00:37:13 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA23896; Sat, 11 Oct 2003 00:37:12 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9AFbCqT027607;
	Sat, 11 Oct 2003 00:37:12 +0900 (JST)
Received: from steelhead ([159.119.168.131]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMJ0092TSPXWF@tsbpo1.po.toshiba.co.jp>; Sat,
 11 Oct 2003 00:37:11 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A7zI1-0003YV-00; Fri, 10 Oct 2003 08:34:49 -0700
Date: Fri, 10 Oct 2003 08:34:44 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5A0@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20031010153444.GB13449@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5A0@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 10, 2003 at 03:53:06PM +0300, Dan.Forsberg@nokia.com wrote:
> PANA folks,
> 
> We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> Then we have the first PANA-Auth-Request/Answer message pair 
> carrying EAP-Request/Identity and EAP-Response/Identity. The 
> EAP-Request/Identity is generated in the PAA/NAS, because/which 
> at that point doesn't know the realm for the user. EAP header 
> also contains the identifier field which is somewhat analoguous 
> to PANA cookie. Why not to put the first EAP payload AVP into 
> the PANA-Start-Request message? This doesn't bring any new 
> requirements for the PAA to create state information, because 
> the EAP header identifier field can act similarly to PANA cookie 
> AVP... or in the extreme we could drop the cookie AVP and use 
> the EAP identifier field as the "cookie".

There are two things we need to consider here:

o The first EAP Request sent by the EAP authenticator is not always
  EAP-Request/Identity, i.e., the use of EAP-Request/Identity is optional when
  the client identity can be obtained by some other means.

o EAP state machine (draft-ietf-eap-statemachines-00.{txt,ps}) does
  not allow an EAP authenticator to be stateless when sending the first EAP Request.

So in general PAA cannot be stateless when sending a PANA-Start-Request 
with piggybacking an EAP Request.

Yoshihiro Ohba



> 
> Let me hear your comments.
> 
> Br,
> - Dan
> 
> _______________________________________________
> 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-admin@ietf.org  Fri Oct 10 13:55:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09687
	for <pana-archive@lists.ietf.org>; Fri, 10 Oct 2003 13:55:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81Th-0005PE-45; Fri, 10 Oct 2003 13:55:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81Sy-0005ND-Kg
	for pana@optimus.ietf.org; Fri, 10 Oct 2003 13:54:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09659
	for <pana@ietf.org>; Fri, 10 Oct 2003 13:54:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81Sw-0006v8-00
	for pana@ietf.org; Fri, 10 Oct 2003 13:54:14 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81Sv-0006v4-00
	for pana@ietf.org; Fri, 10 Oct 2003 13:54:13 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9AHsBF1008969;
	Sat, 11 Oct 2003 02:54:11 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9AHsBT1023304;
	Sat, 11 Oct 2003 02:54:11 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id CAA23301 ; Sat, 11 Oct 2003 02:54:11 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA29145; Sat, 11 Oct 2003 02:54:05 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA05357; Sat, 11 Oct 2003 02:54:05 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9AHs4qV001555;
	Sat, 11 Oct 2003 02:54:04 +0900 (JST)
Received: from steelhead ([159.119.168.131]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMJ00BUOZ21WJ@tsbpo1.po.toshiba.co.jp>; Sat,
 11 Oct 2003 02:54:04 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A81Rx-0003mn-00; Fri, 10 Oct 2003 10:53:13 -0700
Date: Fri, 10 Oct 2003 10:53:12 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031010175312.GC13449@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.4i
Subject: [Pana] comments on draft-ietf-pana-ipsec-00.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>


o When MSK is updated as a result of EAP re-authentication, what IKE
  should do?  There would be several alternatives:

  - Immediately update the ISAKMP SA by performing IKE phase 1
    negotiation with using a fresh IKE pre-shared key derived from the
    new MSK.

  - The ISAKMP SA is not immediately updated when the MSK is updated.
    In a future IKE phase 1 negotiation performed due to e.g.,
    expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
    derived from the latest MSK available at the time of the
    negotiation.

  - The ISAKMP SA is not immediately updated when the MSK is updated.
    In a future IKE phase 1 negotiation performed due to e.g.,
    expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
    derived from the initially derived MSK, not a new one.

I'm not sure which alternative is appropriate.


o In Sections 6 and 7.2, link-local address is used in outer headers
  in IPv6.  Should link-local address is also used in the case where
  PAA and EP are co-located and PANA runs over an IP-in-IP link (i.e.,
  PaC and PAA/EP are logically one IP-hop away but may be several IP
  hops away at a lower level)?  In such a case, I think using global
  IP address in outer headers of the IPsec tunnel makes sense.  Or
  should the IP-in-IP case be out of the scope of the document?


o In Section 5, replace "phase I" with "phase 1."

o In Section 9,

change:

   "If the PAA does not verify whether PaC is authorized to use an IP
   address, it is possible for the PaC to steal the traffic destined to
   some other PaC. The use of IPsec does not prevent this attack. PAA
   may use other mechanisms to prevent this attack."

to:
   
   "If the PAA does not verify whether PaC is authorized to use an IP
   address, it is possible for the PaC to steal the traffic destined to
   some other PaC. The use of IPsec does not prevent this attack. PAA
   may use other mechanisms such as SEND [SEND] to prevent this attack."
                                                                                
   Where [SEND] refers to draft-ietf-send-ipsec-01.txt.

o In Section 9,

   "When IPv6 is used, the SPD entries bypass all link-local traffic
   without applying IPsec. This should not be a limitation as the link-
   local address is used only by link-local services e.g.
   neighbor/router discovery, which uses a different mechanism to
   protect their traffic. Moreover, this limitation may not be there in
   the future if IPsec extends the SPD selectors to specify ICMP types."

The last sentence seems to imply that PANA can also be used for
bootstrapping IPsec for protecting IPv6 Router Discovery, which could
provide a method to securely performing IPv6 address autoconfiguration
without modifying the existing ESP or AH at all (just a modification
to SPD selectors).  I think it is worth mentioning that.


Yoshihiro Ohba

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


From exim@www1.ietf.org  Fri Oct 10 13:55:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09705
	for <pana-archive@odin.ietf.org>; Fri, 10 Oct 2003 13:55:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81Tl-0005QN-Kv
	for pana-archive@odin.ietf.org; Fri, 10 Oct 2003 13:55:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AHt5oo020846
	for pana-archive@odin.ietf.org; Fri, 10 Oct 2003 13:55:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81Tl-0005Q9-H7
	for pana-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 13:55:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09672
	for <pana-web-archive@ietf.org>; Fri, 10 Oct 2003 13:54:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81Tj-0006vP-00
	for pana-web-archive@ietf.org; Fri, 10 Oct 2003 13:55:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81Ti-0006vM-00
	for pana-web-archive@ietf.org; Fri, 10 Oct 2003 13:55:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81Th-0005PE-45; Fri, 10 Oct 2003 13:55:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81Sy-0005ND-Kg
	for pana@optimus.ietf.org; Fri, 10 Oct 2003 13:54:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09659
	for <pana@ietf.org>; Fri, 10 Oct 2003 13:54:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81Sw-0006v8-00
	for pana@ietf.org; Fri, 10 Oct 2003 13:54:14 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81Sv-0006v4-00
	for pana@ietf.org; Fri, 10 Oct 2003 13:54:13 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9AHsBF1008969;
	Sat, 11 Oct 2003 02:54:11 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9AHsBT1023304;
	Sat, 11 Oct 2003 02:54:11 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id CAA23301 ; Sat, 11 Oct 2003 02:54:11 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA29145; Sat, 11 Oct 2003 02:54:05 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA05357; Sat, 11 Oct 2003 02:54:05 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9AHs4qV001555;
	Sat, 11 Oct 2003 02:54:04 +0900 (JST)
Received: from steelhead ([159.119.168.131]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMJ00BUOZ21WJ@tsbpo1.po.toshiba.co.jp>; Sat,
 11 Oct 2003 02:54:04 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A81Rx-0003mn-00; Fri, 10 Oct 2003 10:53:13 -0700
Date: Fri, 10 Oct 2003 10:53:12 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031010175312.GC13449@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.4i
Subject: [Pana] comments on draft-ietf-pana-ipsec-00.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>


o When MSK is updated as a result of EAP re-authentication, what IKE
  should do?  There would be several alternatives:

  - Immediately update the ISAKMP SA by performing IKE phase 1
    negotiation with using a fresh IKE pre-shared key derived from the
    new MSK.

  - The ISAKMP SA is not immediately updated when the MSK is updated.
    In a future IKE phase 1 negotiation performed due to e.g.,
    expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
    derived from the latest MSK available at the time of the
    negotiation.

  - The ISAKMP SA is not immediately updated when the MSK is updated.
    In a future IKE phase 1 negotiation performed due to e.g.,
    expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
    derived from the initially derived MSK, not a new one.

I'm not sure which alternative is appropriate.


o In Sections 6 and 7.2, link-local address is used in outer headers
  in IPv6.  Should link-local address is also used in the case where
  PAA and EP are co-located and PANA runs over an IP-in-IP link (i.e.,
  PaC and PAA/EP are logically one IP-hop away but may be several IP
  hops away at a lower level)?  In such a case, I think using global
  IP address in outer headers of the IPsec tunnel makes sense.  Or
  should the IP-in-IP case be out of the scope of the document?


o In Section 5, replace "phase I" with "phase 1."

o In Section 9,

change:

   "If the PAA does not verify whether PaC is authorized to use an IP
   address, it is possible for the PaC to steal the traffic destined to
   some other PaC. The use of IPsec does not prevent this attack. PAA
   may use other mechanisms to prevent this attack."

to:
   
   "If the PAA does not verify whether PaC is authorized to use an IP
   address, it is possible for the PaC to steal the traffic destined to
   some other PaC. The use of IPsec does not prevent this attack. PAA
   may use other mechanisms such as SEND [SEND] to prevent this attack."
                                                                                
   Where [SEND] refers to draft-ietf-send-ipsec-01.txt.

o In Section 9,

   "When IPv6 is used, the SPD entries bypass all link-local traffic
   without applying IPsec. This should not be a limitation as the link-
   local address is used only by link-local services e.g.
   neighbor/router discovery, which uses a different mechanism to
   protect their traffic. Moreover, this limitation may not be there in
   the future if IPsec extends the SPD selectors to specify ICMP types."

The last sentence seems to imply that PANA can also be used for
bootstrapping IPsec for protecting IPv6 Router Discovery, which could
provide a method to securely performing IPv6 address autoconfiguration
without modifying the existing ESP or AH at all (just a modification
to SPD selectors).  I think it is worth mentioning that.


Yoshihiro Ohba

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



From pana-admin@ietf.org  Fri Oct 10 14:09:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10236
	for <pana-archive@lists.ietf.org>; Fri, 10 Oct 2003 14:09:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81hG-0006vd-1G; Fri, 10 Oct 2003 14:09:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81h7-0006vH-Oz
	for pana@optimus.ietf.org; Fri, 10 Oct 2003 14:08:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10213
	for <pana@ietf.org>; Fri, 10 Oct 2003 14:08:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81h5-00076E-00
	for pana@ietf.org; Fri, 10 Oct 2003 14:08:51 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81h4-000769-00
	for pana@ietf.org; Fri, 10 Oct 2003 14:08:50 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9AI8nF1012082
	for <pana@ietf.org>; Sat, 11 Oct 2003 03:08:49 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9AI8nO6027709
	for <pana@ietf.org>; Sat, 11 Oct 2003 03:08:49 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA27708 ; Sat, 11 Oct 2003 03:08:48 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA02808; Sat, 11 Oct 2003 03:08:48 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA23538; Sat, 11 Oct 2003 03:08:48 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9AI8lqT003908
	for <pana@ietf.org>; Sat, 11 Oct 2003 03:08:47 +0900 (JST)
Received: from steelhead ([159.119.168.131]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMJ00F07ZQL80@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Sat,
 11 Oct 2003 03:08:46 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A81gQ-0003oS-00 for <pana@ietf.org>; Fri, 10 Oct 2003 11:08:10 -0700
Date: Fri, 10 Oct 2003 11:08:10 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031010180810.GD13449@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.4i
Subject: [Pana] comment on draft-yacine-pana-paa2ep-prot-eval-00.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

In Section 4.3:

   "In general terms, the PAA-EP protocol needs to support the stateful
   model between the PAA and the EP(s) and some other mechanism for the
   EP to learn the policies currently in effect on that access network."

This statement seems to mention that stateful model is required for
PAA-EP protocol, however this is not consistent with the following 
statement in Section 6.2:

   "SNMP does not provide heartbeat mechanisms, nor a stateful model (see
   section 2), but this is not required by PANA."
                                                                                

Yoshihiro Ohba


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


From exim@www1.ietf.org  Fri Oct 10 14:09:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10251
	for <pana-archive@odin.ietf.org>; Fri, 10 Oct 2003 14:09:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81hJ-0006wL-7x
	for pana-archive@odin.ietf.org; Fri, 10 Oct 2003 14:09:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9AI95OX026671
	for pana-archive@odin.ietf.org; Fri, 10 Oct 2003 14:09:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81hJ-0006w6-4T
	for pana-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 14:09:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10218
	for <pana-web-archive@ietf.org>; Fri, 10 Oct 2003 14:08:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81hG-00076K-00
	for pana-web-archive@ietf.org; Fri, 10 Oct 2003 14:09:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81hG-00076H-00
	for pana-web-archive@ietf.org; Fri, 10 Oct 2003 14:09:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81hG-0006vd-1G; Fri, 10 Oct 2003 14:09:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A81h7-0006vH-Oz
	for pana@optimus.ietf.org; Fri, 10 Oct 2003 14:08:53 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10213
	for <pana@ietf.org>; Fri, 10 Oct 2003 14:08:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81h5-00076E-00
	for pana@ietf.org; Fri, 10 Oct 2003 14:08:51 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A81h4-000769-00
	for pana@ietf.org; Fri, 10 Oct 2003 14:08:50 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9AI8nF1012082
	for <pana@ietf.org>; Sat, 11 Oct 2003 03:08:49 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9AI8nO6027709
	for <pana@ietf.org>; Sat, 11 Oct 2003 03:08:49 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA27708 ; Sat, 11 Oct 2003 03:08:48 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA02808; Sat, 11 Oct 2003 03:08:48 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA23538; Sat, 11 Oct 2003 03:08:48 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9AI8lqT003908
	for <pana@ietf.org>; Sat, 11 Oct 2003 03:08:47 +0900 (JST)
Received: from steelhead ([159.119.168.131]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMJ00F07ZQL80@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Sat,
 11 Oct 2003 03:08:46 +0900 (JST)
Received: from yohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A81gQ-0003oS-00 for <pana@ietf.org>; Fri, 10 Oct 2003 11:08:10 -0700
Date: Fri, 10 Oct 2003 11:08:10 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031010180810.GD13449@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.4i
Subject: [Pana] comment on draft-yacine-pana-paa2ep-prot-eval-00.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

In Section 4.3:

   "In general terms, the PAA-EP protocol needs to support the stateful
   model between the PAA and the EP(s) and some other mechanism for the
   EP to learn the policies currently in effect on that access network."

This statement seems to mention that stateful model is required for
PAA-EP protocol, however this is not consistent with the following 
statement in Section 6.2:

   "SNMP does not provide heartbeat mechanisms, nor a stateful model (see
   section 2), but this is not required by PANA."
                                                                                

Yoshihiro Ohba


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



From pana-admin@ietf.org  Fri Oct 10 20:52:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02945
	for <pana-archive@lists.ietf.org>; Fri, 10 Oct 2003 20:52:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A87zF-00010b-TU; Fri, 10 Oct 2003 20:52:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A87ys-0000zQ-Fy
	for pana@optimus.ietf.org; Fri, 10 Oct 2003 20:51:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02927
	for <pana@ietf.org>; Fri, 10 Oct 2003 20:51:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A87yp-0005pw-00
	for pana@ietf.org; Fri, 10 Oct 2003 20:51:35 -0400
Received: from smtp801.mail.ukl.yahoo.com ([217.12.12.138])
	by ietf-mx with smtp (Exim 4.12)
	id 1A87yo-0005pq-00
	for pana@ietf.org; Fri, 10 Oct 2003 20:51:35 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp1.bt.mail.vip.ukl.yahoo.com with SMTP; 11 Oct 2003 00:42:06 -0000
Message-ID: <009b01c38f90$7f76caa0$5a100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <20031010175312.GC13449@steelhead>
Subject: Re: [Pana] comments on draft-ietf-pana-ipsec-00.txt
Date: Fri, 10 Oct 2003 17:42:03 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Yoshihiro,

Thanks for your comments.


>
> o When MSK is updated as a result of EAP re-authentication, what IKE
>   should do?  There would be several alternatives:
>
Do we know when reauthentication happens in practice ?

>   - Immediately update the ISAKMP SA by performing IKE phase 1
>     negotiation with using a fresh IKE pre-shared key derived from the
>     new MSK.
>
>   - The ISAKMP SA is not immediately updated when the MSK is updated.
>     In a future IKE phase 1 negotiation performed due to e.g.,
>     expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
>     derived from the latest MSK available at the time of the
>     negotiation.
>
>   - The ISAKMP SA is not immediately updated when the MSK is updated.
>     In a future IKE phase 1 negotiation performed due to e.g.,
>     expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
>     derived from the initially derived MSK, not a new one.
>
> I'm not sure which alternative is appropriate.
>
The option  1 or 2 seems better to me.  Do you think we should clarify this
in
the document ? At least this would help better inter-op i guess.

>
> o In Sections 6 and 7.2, link-local address is used in outer headers
>   in IPv6.  Should link-local address is also used in the case where
>   PAA and EP are co-located and PANA runs over an IP-in-IP link (i.e.,
>   PaC and PAA/EP are logically one IP-hop away but may be several IP
>   hops away at a lower level)?  In such a case, I think using global
>   IP address in outer headers of the IPsec tunnel makes sense.  Or
>   should the IP-in-IP case be out of the scope of the document?
>
I think IP-in-IP is out of scope. Do you see a scenario where PaC and PAA/EP
are connected via a tunnel ?

>
> o In Section 5, replace "phase I" with "phase 1."
>
okay.

> o In Section 9,
>
> change:
>
>    "If the PAA does not verify whether PaC is authorized to use an IP
>    address, it is possible for the PaC to steal the traffic destined to
>    some other PaC. The use of IPsec does not prevent this attack. PAA
>    may use other mechanisms to prevent this attack."
>
> to:
>
>    "If the PAA does not verify whether PaC is authorized to use an IP
>    address, it is possible for the PaC to steal the traffic destined to
>    some other PaC. The use of IPsec does not prevent this attack. PAA
>    may use other mechanisms such as SEND [SEND] to prevent this attack."
>
>    Where [SEND] refers to draft-ietf-send-ipsec-01.txt.
>
okay.

> o In Section 9,
>
>    "When IPv6 is used, the SPD entries bypass all link-local traffic
>    without applying IPsec. This should not be a limitation as the link-
>    local address is used only by link-local services e.g.
>    neighbor/router discovery, which uses a different mechanism to
>    protect their traffic. Moreover, this limitation may not be there in
>    the future if IPsec extends the SPD selectors to specify ICMP types."
>
> The last sentence seems to imply that PANA can also be used for
> bootstrapping IPsec for protecting IPv6 Router Discovery, which could
> provide a method to securely performing IPv6 address autoconfiguration
> without modifying the existing ESP or AH at all (just a modification
> to SPD selectors).  I think it is worth mentioning that.
>
Yeah, it is a possibility. But it really depends on what SEND standardizes.
Where do you want to mention this in the document ?

-thanks
mohan

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


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


From exim@www1.ietf.org  Fri Oct 10 20:52:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02961
	for <pana-archive@odin.ietf.org>; Fri, 10 Oct 2003 20:52:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A87zN-00011f-9U
	for pana-archive@odin.ietf.org; Fri, 10 Oct 2003 20:52:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9B0q9OB003937
	for pana-archive@odin.ietf.org; Fri, 10 Oct 2003 20:52:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A87zN-00011Q-3A
	for pana-web-archive@optimus.ietf.org; Fri, 10 Oct 2003 20:52:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02934
	for <pana-web-archive@ietf.org>; Fri, 10 Oct 2003 20:52:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A87zK-0005q5-00
	for pana-web-archive@ietf.org; Fri, 10 Oct 2003 20:52:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A87zK-0005q1-00
	for pana-web-archive@ietf.org; Fri, 10 Oct 2003 20:52:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A87zF-00010b-TU; Fri, 10 Oct 2003 20:52:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A87ys-0000zQ-Fy
	for pana@optimus.ietf.org; Fri, 10 Oct 2003 20:51:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02927
	for <pana@ietf.org>; Fri, 10 Oct 2003 20:51:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A87yp-0005pw-00
	for pana@ietf.org; Fri, 10 Oct 2003 20:51:35 -0400
Received: from smtp801.mail.ukl.yahoo.com ([217.12.12.138])
	by ietf-mx with smtp (Exim 4.12)
	id 1A87yo-0005pq-00
	for pana@ietf.org; Fri, 10 Oct 2003 20:51:35 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp1.bt.mail.vip.ukl.yahoo.com with SMTP; 11 Oct 2003 00:42:06 -0000
Message-ID: <009b01c38f90$7f76caa0$5a100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <20031010175312.GC13449@steelhead>
Subject: Re: [Pana] comments on draft-ietf-pana-ipsec-00.txt
Date: Fri, 10 Oct 2003 17:42:03 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yoshihiro,

Thanks for your comments.


>
> o When MSK is updated as a result of EAP re-authentication, what IKE
>   should do?  There would be several alternatives:
>
Do we know when reauthentication happens in practice ?

>   - Immediately update the ISAKMP SA by performing IKE phase 1
>     negotiation with using a fresh IKE pre-shared key derived from the
>     new MSK.
>
>   - The ISAKMP SA is not immediately updated when the MSK is updated.
>     In a future IKE phase 1 negotiation performed due to e.g.,
>     expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
>     derived from the latest MSK available at the time of the
>     negotiation.
>
>   - The ISAKMP SA is not immediately updated when the MSK is updated.
>     In a future IKE phase 1 negotiation performed due to e.g.,
>     expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
>     derived from the initially derived MSK, not a new one.
>
> I'm not sure which alternative is appropriate.
>
The option  1 or 2 seems better to me.  Do you think we should clarify this
in
the document ? At least this would help better inter-op i guess.

>
> o In Sections 6 and 7.2, link-local address is used in outer headers
>   in IPv6.  Should link-local address is also used in the case where
>   PAA and EP are co-located and PANA runs over an IP-in-IP link (i.e.,
>   PaC and PAA/EP are logically one IP-hop away but may be several IP
>   hops away at a lower level)?  In such a case, I think using global
>   IP address in outer headers of the IPsec tunnel makes sense.  Or
>   should the IP-in-IP case be out of the scope of the document?
>
I think IP-in-IP is out of scope. Do you see a scenario where PaC and PAA/EP
are connected via a tunnel ?

>
> o In Section 5, replace "phase I" with "phase 1."
>
okay.

> o In Section 9,
>
> change:
>
>    "If the PAA does not verify whether PaC is authorized to use an IP
>    address, it is possible for the PaC to steal the traffic destined to
>    some other PaC. The use of IPsec does not prevent this attack. PAA
>    may use other mechanisms to prevent this attack."
>
> to:
>
>    "If the PAA does not verify whether PaC is authorized to use an IP
>    address, it is possible for the PaC to steal the traffic destined to
>    some other PaC. The use of IPsec does not prevent this attack. PAA
>    may use other mechanisms such as SEND [SEND] to prevent this attack."
>
>    Where [SEND] refers to draft-ietf-send-ipsec-01.txt.
>
okay.

> o In Section 9,
>
>    "When IPv6 is used, the SPD entries bypass all link-local traffic
>    without applying IPsec. This should not be a limitation as the link-
>    local address is used only by link-local services e.g.
>    neighbor/router discovery, which uses a different mechanism to
>    protect their traffic. Moreover, this limitation may not be there in
>    the future if IPsec extends the SPD selectors to specify ICMP types."
>
> The last sentence seems to imply that PANA can also be used for
> bootstrapping IPsec for protecting IPv6 Router Discovery, which could
> provide a method to securely performing IPv6 address autoconfiguration
> without modifying the existing ESP or AH at all (just a modification
> to SPD selectors).  I think it is worth mentioning that.
>
Yeah, it is a possibility. But it really depends on what SEND standardizes.
Where do you want to mention this in the document ?

-thanks
mohan

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


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



From pana-admin@ietf.org  Mon Oct 13 05:09:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27514
	for <pana-archive@lists.ietf.org>; Mon, 13 Oct 2003 05:09:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A8yhL-0006pG-BX; Mon, 13 Oct 2003 05:09:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A8yh3-0006ou-Ct
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 05:08:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27501
	for <pana@ietf.org>; Mon, 13 Oct 2003 05:08:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8ygz-0000eF-00
	for pana@ietf.org; Mon, 13 Oct 2003 05:08:41 -0400
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8ygz-0000dy-00
	for pana@ietf.org; Mon, 13 Oct 2003 05:08:41 -0400
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id h9D981ST016849;
	Mon, 13 Oct 2003 11:08:07 +0200
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003101311075891:2117 ;
          Mon, 13 Oct 2003 11:07:58 +0200 
Message-ID: <3F8A6B6F.4050100@alcatel.fr>
Date: Mon, 13 Oct 2003 11:07:59 +0200
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: pana@ietf.org
Subject: Re: [Pana] comment on draft-yacine-pana-paa2ep-prot-eval-00.txt
References: <20031010180810.GD13449@steelhead>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/13/2003 11:07:58,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/13/2003 11:08:07,
	Serialize complete at 10/13/2003 11:08:07
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-2022-JP
X-Virus-Scanned: by amavisd-new
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

you're right Yoshi: some rewording may be needed here (I guess "MAY"
would be ok) in order to avoid misunderstandings. Anyway, the extract
below is quoted from the document scope and it says explicitly this
section does not deal with the PANA requirements identified in the PANA
REQ doc, which already passed a last call.

   The following section 4 presents some functions the PAA-EP protocol
   should offer, which have already been discussed on the mailing list.
   These are not mandatory at all, but one can consider them as "nice-
   to-have".

thanks,
Yacine



Yoshihiro Ohba a e'crit:
> In Section 4.3:
> 
>    "In general terms, the PAA-EP protocol needs to support the stateful
>    model between the PAA and the EP(s) and some other mechanism for the
>    EP to learn the policies currently in effect on that access network."
> 
> This statement seems to mention that stateful model is required for
> PAA-EP protocol, however this is not consistent with the following 
> statement in Section 6.2:
> 
>    "SNMP does not provide heartbeat mechanisms, nor a stateful model (see
>    section 2), but this is not required by PANA."
>                                                                                 
> 
> Yoshihiro Ohba
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 



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


From exim@www1.ietf.org  Mon Oct 13 05:10:05 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27539
	for <pana-archive@odin.ietf.org>; Mon, 13 Oct 2003 05:10:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A8yi0-0006qQ-Ca
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 05:09:44 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9D99ige026299
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 05:09:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A8yhx-0006q1-Ol
	for pana-web-archive@optimus.ietf.org; Mon, 13 Oct 2003 05:09:41 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27513
	for <pana-web-archive@ietf.org>; Mon, 13 Oct 2003 05:09:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A8yhL-0006pG-BX; Mon, 13 Oct 2003 05:09:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A8yh3-0006ou-Ct
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 05:08:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27501
	for <pana@ietf.org>; Mon, 13 Oct 2003 05:08:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8ygz-0000eF-00
	for pana@ietf.org; Mon, 13 Oct 2003 05:08:41 -0400
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A8ygz-0000dy-00
	for pana@ietf.org; Mon, 13 Oct 2003 05:08:41 -0400
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id h9D981ST016849;
	Mon, 13 Oct 2003 11:08:07 +0200
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003101311075891:2117 ;
          Mon, 13 Oct 2003 11:07:58 +0200 
Message-ID: <3F8A6B6F.4050100@alcatel.fr>
Date: Mon, 13 Oct 2003 11:07:59 +0200
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: pana@ietf.org
Subject: Re: [Pana] comment on draft-yacine-pana-paa2ep-prot-eval-00.txt
References: <20031010180810.GD13449@steelhead>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/13/2003 11:07:58,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/13/2003 11:08:07,
	Serialize complete at 10/13/2003 11:08:07
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-2022-JP
X-Virus-Scanned: by amavisd-new
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

you're right Yoshi: some rewording may be needed here (I guess "MAY"
would be ok) in order to avoid misunderstandings. Anyway, the extract
below is quoted from the document scope and it says explicitly this
section does not deal with the PANA requirements identified in the PANA
REQ doc, which already passed a last call.

   The following section 4 presents some functions the PAA-EP protocol
   should offer, which have already been discussed on the mailing list.
   These are not mandatory at all, but one can consider them as "nice-
   to-have".

thanks,
Yacine



Yoshihiro Ohba a e'crit:
> In Section 4.3:
> 
>    "In general terms, the PAA-EP protocol needs to support the stateful
>    model between the PAA and the EP(s) and some other mechanism for the
>    EP to learn the policies currently in effect on that access network."
> 
> This statement seems to mention that stateful model is required for
> PAA-EP protocol, however this is not consistent with the following 
> statement in Section 6.2:
> 
>    "SNMP does not provide heartbeat mechanisms, nor a stateful model (see
>    section 2), but this is not required by PANA."
>                                                                                 
> 
> Yoshihiro Ohba
> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 



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



From pana-admin@ietf.org  Mon Oct 13 07:59:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01324
	for <pana-archive@lists.ietf.org>; Mon, 13 Oct 2003 07:59:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A91Lp-0005Pm-N8; Mon, 13 Oct 2003 07:59:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A91Li-0005PU-6H
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 07:58:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01310
	for <pana@ietf.org>; Mon, 13 Oct 2003 07:58:45 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A91Lh-0001rZ-00
	for pana@ietf.org; Mon, 13 Oct 2003 07:58:53 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A91Lg-0001rW-00
	for pana@ietf.org; Mon, 13 Oct 2003 07:58:52 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9DBwov25517
	for <pana@ietf.org>; Mon, 13 Oct 2003 14:58:51 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65425da6d2ac158f24077@esvir04nok.ntc.nokia.com>;
 Mon, 13 Oct 2003 14:58:50 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 13 Oct 2003 14:58:50 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Mon, 13 Oct 2003 14:58:50 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D68@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] EAP-Request/Identity & PANA-Start-Request
Thread-Index: AcOPRGiloPnzNLm1TjGsGrAPaU9o0gCPFMVQ
To: <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 13 Oct 2003 11:58:50.0560 (UTC) FILETIME=[5DB72C00:01C39181]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Yoshihiro,

Your arguments are not exactly valid. 

We could also say that PaC sends always EAP-Payload AVP 
that contains EAP-Response/Identity in the PANA-Start-Answer 
message. I.e. no EAP-Request is necessarily needed from PAA.

PAA can itself create the EAP-Request thus the authenticator 
is not involved.

Otherwise PaC needs to send it's identity to the PAA out 
of the EAP so that PAA/NAS can contact the right authenticator.

- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 10 October, 2003 18:35
> To: Forsberg Dan (NRC/Helsinki)
> Cc: pana@ietf.org
> Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
>
>
> On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> Dan.Forsberg@nokia.com wrote:
> > PANA folks,
> >
> > We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> > Then we have the first PANA-Auth-Request/Answer message pair
> > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > EAP-Request/Identity is generated in the PAA/NAS, because/which
> > at that point doesn't know the realm for the user. EAP header
> > also contains the identifier field which is somewhat analoguous
> > to PANA cookie. Why not to put the first EAP payload AVP into
> > the PANA-Start-Request message? This doesn't bring any new
> > requirements for the PAA to create state information, because
> > the EAP header identifier field can act similarly to PANA cookie
> > AVP... or in the extreme we could drop the cookie AVP and use
> > the EAP identifier field as the "cookie".
>
> There are two things we need to consider here:
>
> o The first EAP Request sent by the EAP authenticator is not always
>   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> is optional when
>   the client identity can be obtained by some other means.
>
> o EAP state machine (draft-ietf-eap-statemachines-00.{txt,ps}) does
>   not allow an EAP authenticator to be stateless when sending
> the first EAP Request.
>
> So in general PAA cannot be stateless when sending a
> PANA-Start-Request
> with piggybacking an EAP Request.
>
> Yoshihiro Ohba
>
>
>
> >
> > Let me hear your comments.
> >
> > Br,
> > - Dan
> >
> > _______________________________________________
> > 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 exim@www1.ietf.org  Mon Oct 13 07:59:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01339
	for <pana-archive@odin.ietf.org>; Mon, 13 Oct 2003 07:59:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A91Lw-0005Qh-L7
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 07:59:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9DBx8Gi020867
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 07:59:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A91Lw-0005QK-Br
	for pana-web-archive@optimus.ietf.org; Mon, 13 Oct 2003 07:59:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01318
	for <pana-web-archive@ietf.org>; Mon, 13 Oct 2003 07:59:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A91Lv-0001rg-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 07:59:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A91Lv-0001rc-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 07:59:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A91Lp-0005Pm-N8; Mon, 13 Oct 2003 07:59:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A91Li-0005PU-6H
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 07:58:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01310
	for <pana@ietf.org>; Mon, 13 Oct 2003 07:58:45 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A91Lh-0001rZ-00
	for pana@ietf.org; Mon, 13 Oct 2003 07:58:53 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A91Lg-0001rW-00
	for pana@ietf.org; Mon, 13 Oct 2003 07:58:52 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9DBwov25517
	for <pana@ietf.org>; Mon, 13 Oct 2003 14:58:51 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65425da6d2ac158f24077@esvir04nok.ntc.nokia.com>;
 Mon, 13 Oct 2003 14:58:50 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Mon, 13 Oct 2003 14:58:50 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Mon, 13 Oct 2003 14:58:50 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D68@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] EAP-Request/Identity & PANA-Start-Request
Thread-Index: AcOPRGiloPnzNLm1TjGsGrAPaU9o0gCPFMVQ
To: <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 13 Oct 2003 11:58:50.0560 (UTC) FILETIME=[5DB72C00:01C39181]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Yoshihiro,

Your arguments are not exactly valid. 

We could also say that PaC sends always EAP-Payload AVP 
that contains EAP-Response/Identity in the PANA-Start-Answer 
message. I.e. no EAP-Request is necessarily needed from PAA.

PAA can itself create the EAP-Request thus the authenticator 
is not involved.

Otherwise PaC needs to send it's identity to the PAA out 
of the EAP so that PAA/NAS can contact the right authenticator.

- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 10 October, 2003 18:35
> To: Forsberg Dan (NRC/Helsinki)
> Cc: pana@ietf.org
> Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
>
>
> On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> Dan.Forsberg@nokia.com wrote:
> > PANA folks,
> >
> > We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> > Then we have the first PANA-Auth-Request/Answer message pair
> > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > EAP-Request/Identity is generated in the PAA/NAS, because/which
> > at that point doesn't know the realm for the user. EAP header
> > also contains the identifier field which is somewhat analoguous
> > to PANA cookie. Why not to put the first EAP payload AVP into
> > the PANA-Start-Request message? This doesn't bring any new
> > requirements for the PAA to create state information, because
> > the EAP header identifier field can act similarly to PANA cookie
> > AVP... or in the extreme we could drop the cookie AVP and use
> > the EAP identifier field as the "cookie".
>
> There are two things we need to consider here:
>
> o The first EAP Request sent by the EAP authenticator is not always
>   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> is optional when
>   the client identity can be obtained by some other means.
>
> o EAP state machine (draft-ietf-eap-statemachines-00.{txt,ps}) does
>   not allow an EAP authenticator to be stateless when sending
> the first EAP Request.
>
> So in general PAA cannot be stateless when sending a
> PANA-Start-Request
> with piggybacking an EAP Request.
>
> Yoshihiro Ohba
>
>
>
> >
> > Let me hear your comments.
> >
> > Br,
> > - Dan
> >
> > _______________________________________________
> > 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-admin@ietf.org  Mon Oct 13 11:20:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10963
	for <pana-archive@lists.ietf.org>; Mon, 13 Oct 2003 11:20:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A94UM-0006vC-6R; Mon, 13 Oct 2003 11:20:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A94To-0006uc-TF
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 11:19:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10949
	for <pana@ietf.org>; Mon, 13 Oct 2003 11:19:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A94Tn-0004GH-00
	for pana@ietf.org; Mon, 13 Oct 2003 11:19:27 -0400
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A94Tn-0004GE-00
	for pana@ietf.org; Mon, 13 Oct 2003 11:19:27 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h9DFJP712588;
	Mon, 13 Oct 2003 17:19:25 +0200 (MEST)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h9DFJOx19383;
	Mon, 13 Oct 2003 17:19:25 +0200 (MEST)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19)
	id <4DN1PQ0T>; Mon, 13 Oct 2003 17:19:16 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC029E@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>, pana@ietf.org
Date: Mon, 13 Oct 2003 17:19:19 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Pana] comments to pana-ipsec
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi mohan, 
hi all, 

working on a pana implementation (including packet filter creation and ipsec
sa establishment) we had to notice that there is a problem getting pana and
ike to interact. 

after pana authentication and key exchange is finished some parameters (such
as keys and ip address info) have to be provided to ike. using the freeswan
(pluto) and freebsd (racoon) ike implementations we noticed that these
parameter cannot be added dynamically. these implemenations require changes
to plaintext files and some other configuration steps which makes the
interworking difficult (without speaking about the performance impact).

is someone aware of an ike implementation which allows ike to be configured
dynamically (possible via an api)?

ciao
hannes

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


From exim@www1.ietf.org  Mon Oct 13 11:20:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10978
	for <pana-archive@odin.ietf.org>; Mon, 13 Oct 2003 11:20:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A94UT-0006w2-07
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 11:20:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9DFK8uu026650
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 11:20:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A94UR-0006vl-I6
	for pana-web-archive@optimus.ietf.org; Mon, 13 Oct 2003 11:20:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10959
	for <pana-web-archive@ietf.org>; Mon, 13 Oct 2003 11:19:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A94UP-0004GN-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 11:20:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A94UO-0004GK-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 11:20:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A94UM-0006vC-6R; Mon, 13 Oct 2003 11:20:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A94To-0006uc-TF
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 11:19:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10949
	for <pana@ietf.org>; Mon, 13 Oct 2003 11:19:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A94Tn-0004GH-00
	for pana@ietf.org; Mon, 13 Oct 2003 11:19:27 -0400
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A94Tn-0004GE-00
	for pana@ietf.org; Mon, 13 Oct 2003 11:19:27 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h9DFJP712588;
	Mon, 13 Oct 2003 17:19:25 +0200 (MEST)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h9DFJOx19383;
	Mon, 13 Oct 2003 17:19:25 +0200 (MEST)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19)
	id <4DN1PQ0T>; Mon, 13 Oct 2003 17:19:16 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC029E@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>, pana@ietf.org
Date: Mon, 13 Oct 2003 17:19:19 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Pana] comments to pana-ipsec
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi mohan, 
hi all, 

working on a pana implementation (including packet filter creation and ipsec
sa establishment) we had to notice that there is a problem getting pana and
ike to interact. 

after pana authentication and key exchange is finished some parameters (such
as keys and ip address info) have to be provided to ike. using the freeswan
(pluto) and freebsd (racoon) ike implementations we noticed that these
parameter cannot be added dynamically. these implemenations require changes
to plaintext files and some other configuration steps which makes the
interworking difficult (without speaking about the performance impact).

is someone aware of an ike implementation which allows ike to be configured
dynamically (possible via an api)?

ciao
hannes

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



From pana-admin@ietf.org  Mon Oct 13 12:28:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14044
	for <pana-archive@lists.ietf.org>; Mon, 13 Oct 2003 12:28:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A95Y9-0002nb-9E; Mon, 13 Oct 2003 12:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A95Xf-0002ma-Se
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 12:27:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14000
	for <pana@ietf.org>; Mon, 13 Oct 2003 12:27:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A95Xe-00053F-00
	for pana@ietf.org; Mon, 13 Oct 2003 12:27:30 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A95Xd-00053C-00
	for pana@ietf.org; Mon, 13 Oct 2003 12:27:29 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9DGRRF1006086;
	Tue, 14 Oct 2003 01:27:27 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9DGRRTc029797;
	Tue, 14 Oct 2003 01:27:27 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA29796 ; Tue, 14 Oct 2003 01:27:27 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA22128; Tue, 14 Oct 2003 01:27:27 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA10185; Tue, 14 Oct 2003 01:27:26 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9DGRQqT014600;
	Tue, 14 Oct 2003 01:27:26 +0900 (JST)
Received: from steelhead ([159.119.168.155]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMP00I1PF1O32@tsbpo1.po.toshiba.co.jp>; Tue,
 14 Oct 2003 01:27:25 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A95VD-000264-00; Mon, 13 Oct 2003 09:24:59 -0700
Date: Mon, 13 Oct 2003 09:24:59 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D68@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031013162459.GB7610@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D68@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Dan,

On Mon, Oct 13, 2003 at 02:58:50PM +0300, Dan.Forsberg@nokia.com wrote:
> Hi Yoshihiro,
> 
> Your arguments are not exactly valid. 
> 
> We could also say that PaC sends always EAP-Payload AVP 
> that contains EAP-Response/Identity in the PANA-Start-Answer 
> message. I.e. no EAP-Request is necessarily needed from PAA.

EAP does not allow EAP peers to unsolicitedly send EAP-Response.

> 
> PAA can itself create the EAP-Request thus the authenticator 
> is not involved.

The current EAP authenticator state machine on the NAS does not allow
lower-layer entity (e.g., PAA) to create an EAP Request on behalf of
the authenticator.

> 
> Otherwise PaC needs to send it's identity to the PAA out 
> of the EAP so that PAA/NAS can contact the right authenticator.

In some EAP environment where MAC address is used as a client
identifier, the identifier can be effectively obtained from the MAC
header that carries PANA message without using EAP-Identity exchange.

> 
> - Dan

Yoshihiro Ohba

> 
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 10 October, 2003 18:35
> > To: Forsberg Dan (NRC/Helsinki)
> > Cc: pana@ietf.org
> > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> >
> >
> > On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> > Dan.Forsberg@nokia.com wrote:
> > > PANA folks,
> > >
> > > We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> > > Then we have the first PANA-Auth-Request/Answer message pair
> > > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > > EAP-Request/Identity is generated in the PAA/NAS, because/which
> > > at that point doesn't know the realm for the user. EAP header
> > > also contains the identifier field which is somewhat analoguous
> > > to PANA cookie. Why not to put the first EAP payload AVP into
> > > the PANA-Start-Request message? This doesn't bring any new
> > > requirements for the PAA to create state information, because
> > > the EAP header identifier field can act similarly to PANA cookie
> > > AVP... or in the extreme we could drop the cookie AVP and use
> > > the EAP identifier field as the "cookie".
> >
> > There are two things we need to consider here:
> >
> > o The first EAP Request sent by the EAP authenticator is not always
> >   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> > is optional when
> >   the client identity can be obtained by some other means.
> >
> > o EAP state machine (draft-ietf-eap-statemachines-00.{txt,ps}) does
> >   not allow an EAP authenticator to be stateless when sending
> > the first EAP Request.
> >
> > So in general PAA cannot be stateless when sending a
> > PANA-Start-Request
> > with piggybacking an EAP Request.
> >
> > Yoshihiro Ohba
> >
> >
> >
> > >
> > > Let me hear your comments.
> > >
> > > Br,
> > > - Dan
> > >
> > > _______________________________________________
> > > 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 exim@www1.ietf.org  Mon Oct 13 12:28:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14059
	for <pana-archive@odin.ietf.org>; Mon, 13 Oct 2003 12:28:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A95YE-0002oY-99
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 12:28:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9DGS6W0010815
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 12:28:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A95YE-0002oM-2J
	for pana-web-archive@optimus.ietf.org; Mon, 13 Oct 2003 12:28:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14009
	for <pana-web-archive@ietf.org>; Mon, 13 Oct 2003 12:27:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A95YC-00053Y-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 12:28:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A95YC-00053V-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 12:28:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A95Y9-0002nb-9E; Mon, 13 Oct 2003 12:28:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A95Xf-0002ma-Se
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 12:27:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14000
	for <pana@ietf.org>; Mon, 13 Oct 2003 12:27:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A95Xe-00053F-00
	for pana@ietf.org; Mon, 13 Oct 2003 12:27:30 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A95Xd-00053C-00
	for pana@ietf.org; Mon, 13 Oct 2003 12:27:29 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9DGRRF1006086;
	Tue, 14 Oct 2003 01:27:27 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9DGRRTc029797;
	Tue, 14 Oct 2003 01:27:27 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA29796 ; Tue, 14 Oct 2003 01:27:27 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA22128; Tue, 14 Oct 2003 01:27:27 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA10185; Tue, 14 Oct 2003 01:27:26 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9DGRQqT014600;
	Tue, 14 Oct 2003 01:27:26 +0900 (JST)
Received: from steelhead ([159.119.168.155]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMP00I1PF1O32@tsbpo1.po.toshiba.co.jp>; Tue,
 14 Oct 2003 01:27:25 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A95VD-000264-00; Mon, 13 Oct 2003 09:24:59 -0700
Date: Mon, 13 Oct 2003 09:24:59 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D68@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031013162459.GB7610@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D68@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Dan,

On Mon, Oct 13, 2003 at 02:58:50PM +0300, Dan.Forsberg@nokia.com wrote:
> Hi Yoshihiro,
> 
> Your arguments are not exactly valid. 
> 
> We could also say that PaC sends always EAP-Payload AVP 
> that contains EAP-Response/Identity in the PANA-Start-Answer 
> message. I.e. no EAP-Request is necessarily needed from PAA.

EAP does not allow EAP peers to unsolicitedly send EAP-Response.

> 
> PAA can itself create the EAP-Request thus the authenticator 
> is not involved.

The current EAP authenticator state machine on the NAS does not allow
lower-layer entity (e.g., PAA) to create an EAP Request on behalf of
the authenticator.

> 
> Otherwise PaC needs to send it's identity to the PAA out 
> of the EAP so that PAA/NAS can contact the right authenticator.

In some EAP environment where MAC address is used as a client
identifier, the identifier can be effectively obtained from the MAC
header that carries PANA message without using EAP-Identity exchange.

> 
> - Dan

Yoshihiro Ohba

> 
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 10 October, 2003 18:35
> > To: Forsberg Dan (NRC/Helsinki)
> > Cc: pana@ietf.org
> > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> >
> >
> > On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> > Dan.Forsberg@nokia.com wrote:
> > > PANA folks,
> > >
> > > We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> > > Then we have the first PANA-Auth-Request/Answer message pair
> > > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > > EAP-Request/Identity is generated in the PAA/NAS, because/which
> > > at that point doesn't know the realm for the user. EAP header
> > > also contains the identifier field which is somewhat analoguous
> > > to PANA cookie. Why not to put the first EAP payload AVP into
> > > the PANA-Start-Request message? This doesn't bring any new
> > > requirements for the PAA to create state information, because
> > > the EAP header identifier field can act similarly to PANA cookie
> > > AVP... or in the extreme we could drop the cookie AVP and use
> > > the EAP identifier field as the "cookie".
> >
> > There are two things we need to consider here:
> >
> > o The first EAP Request sent by the EAP authenticator is not always
> >   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> > is optional when
> >   the client identity can be obtained by some other means.
> >
> > o EAP state machine (draft-ietf-eap-statemachines-00.{txt,ps}) does
> >   not allow an EAP authenticator to be stateless when sending
> > the first EAP Request.
> >
> > So in general PAA cannot be stateless when sending a
> > PANA-Start-Request
> > with piggybacking an EAP Request.
> >
> > Yoshihiro Ohba
> >
> >
> >
> > >
> > > Let me hear your comments.
> > >
> > > Br,
> > > - Dan
> > >
> > > _______________________________________________
> > > 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-admin@ietf.org  Mon Oct 13 14:45:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19696
	for <pana-archive@lists.ietf.org>; Mon, 13 Oct 2003 14:45:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97gk-00012z-0S; Mon, 13 Oct 2003 14:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97gZ-00012g-3L
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 14:44:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19676
	for <pana@ietf.org>; Mon, 13 Oct 2003 14:44:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A97gW-0006dn-00
	for pana@ietf.org; Mon, 13 Oct 2003 14:44:48 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A97gV-0006dk-00
	for pana@ietf.org; Mon, 13 Oct 2003 14:44:47 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9DIijF1005605;
	Tue, 14 Oct 2003 03:44:45 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9DIijlP007942;
	Tue, 14 Oct 2003 03:44:45 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA07941 ; Tue, 14 Oct 2003 03:44:45 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA16640; Tue, 14 Oct 2003 03:44:44 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA02253; Tue, 14 Oct 2003 03:44:43 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9DIihqT012694;
	Tue, 14 Oct 2003 03:44:43 +0900 (JST)
Received: from steelhead ([159.119.168.155]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMP00M2DLEHFH@tsbpo1.po.toshiba.co.jp>; Tue,
 14 Oct 2003 03:44:42 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A97fM-0002Lp-00; Mon, 13 Oct 2003 11:43:36 -0700
Date: Mon, 13 Oct 2003 11:43:36 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] comments on draft-ietf-pana-ipsec-00.txt
In-reply-to: <009b01c38f90$7f76caa0$5a100a0a@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031013184335.GC8264@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Mohan Parthasarathy <mohanp@sbcglobal.net>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031010175312.GC13449@steelhead>
 <009b01c38f90$7f76caa0$5a100a0a@adithya>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 10, 2003 at 05:42:03PM -0700, Mohan Parthasarathy wrote:
> Yoshihiro,
> 
> Thanks for your comments.
> 
> 
> >
> > o When MSK is updated as a result of EAP re-authentication, what IKE
> >   should do?  There would be several alternatives:
> >
> Do we know when reauthentication happens in practice ?

It can happen before authorization lifetime expires, where the
lifetime can be carried in a Session-Timeout attribute in RADIUS
Access-Accept.

> 
> >   - Immediately update the ISAKMP SA by performing IKE phase 1
> >     negotiation with using a fresh IKE pre-shared key derived from the
> >     new MSK.
> >
> >   - The ISAKMP SA is not immediately updated when the MSK is updated.
> >     In a future IKE phase 1 negotiation performed due to e.g.,
> >     expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
> >     derived from the latest MSK available at the time of the
> >     negotiation.
> >
> >   - The ISAKMP SA is not immediately updated when the MSK is updated.
> >     In a future IKE phase 1 negotiation performed due to e.g.,
> >     expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
> >     derived from the initially derived MSK, not a new one.
> >
> > I'm not sure which alternative is appropriate.
> >
> The option  1 or 2 seems better to me.  Do you think we should clarify this
> in
> the document ? At least this would help better inter-op i guess.

Yes, I think we should describe it for improving interoperability.
Maybe option 2 by default.

> 
> >
> > o In Sections 6 and 7.2, link-local address is used in outer headers
> >   in IPv6.  Should link-local address is also used in the case where
> >   PAA and EP are co-located and PANA runs over an IP-in-IP link (i.e.,
> >   PaC and PAA/EP are logically one IP-hop away but may be several IP
> >   hops away at a lower level)?  In such a case, I think using global
> >   IP address in outer headers of the IPsec tunnel makes sense.  Or
> >   should the IP-in-IP case be out of the scope of the document?
> >
> I think IP-in-IP is out of scope. Do you see a scenario where PaC and PAA/EP
> are connected via a tunnel ?

A possible scenario for this is that PANA can be used for
bootstrapping Mobile IPv6 Mobility Security Association (MSA) between
a moble node and a home agent.

> 
> >
> > o In Section 5, replace "phase I" with "phase 1."
> >
> okay.
> 
> > o In Section 9,
> >
> > change:
> >
> >    "If the PAA does not verify whether PaC is authorized to use an IP
> >    address, it is possible for the PaC to steal the traffic destined to
> >    some other PaC. The use of IPsec does not prevent this attack. PAA
> >    may use other mechanisms to prevent this attack."
> >
> > to:
> >
> >    "If the PAA does not verify whether PaC is authorized to use an IP
> >    address, it is possible for the PaC to steal the traffic destined to
> >    some other PaC. The use of IPsec does not prevent this attack. PAA
> >    may use other mechanisms such as SEND [SEND] to prevent this attack."
> >
> >    Where [SEND] refers to draft-ietf-send-ipsec-01.txt.
> >
> okay.
> 
> > o In Section 9,
> >
> >    "When IPv6 is used, the SPD entries bypass all link-local traffic
> >    without applying IPsec. This should not be a limitation as the link-
> >    local address is used only by link-local services e.g.
> >    neighbor/router discovery, which uses a different mechanism to
> >    protect their traffic. Moreover, this limitation may not be there in
> >    the future if IPsec extends the SPD selectors to specify ICMP types."
> >
> > The last sentence seems to imply that PANA can also be used for
> > bootstrapping IPsec for protecting IPv6 Router Discovery, which could
> > provide a method to securely performing IPv6 address autoconfiguration
> > without modifying the existing ESP or AH at all (just a modification
> > to SPD selectors).  I think it is worth mentioning that.
> >
> Yeah, it is a possibility. But it really depends on what SEND standardizes.
> Where do you want to mention this in the document ?

SEND provides a PKI-based method for protecting Router Discovery by
using digital certificates issued to routers from a trusted 3rd party, 
but does not specify a AAA-based method for protecting Router Discovery.
PANA can cover the latter case which is not covered by SEND.

Yoshihiro Ohba

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

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


From exim@www1.ietf.org  Mon Oct 13 14:45:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19711
	for <pana-archive@odin.ietf.org>; Mon, 13 Oct 2003 14:45:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97gp-00013g-EL
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 14:45:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9DIj7MD004062
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 14:45:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97gp-00013R-93
	for pana-web-archive@optimus.ietf.org; Mon, 13 Oct 2003 14:45:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19683
	for <pana-web-archive@ietf.org>; Mon, 13 Oct 2003 14:44:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A97gm-0006dt-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 14:45:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A97gl-0006dq-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 14:45:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97gk-00012z-0S; Mon, 13 Oct 2003 14:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97gZ-00012g-3L
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 14:44:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19676
	for <pana@ietf.org>; Mon, 13 Oct 2003 14:44:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A97gW-0006dn-00
	for pana@ietf.org; Mon, 13 Oct 2003 14:44:48 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A97gV-0006dk-00
	for pana@ietf.org; Mon, 13 Oct 2003 14:44:47 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9DIijF1005605;
	Tue, 14 Oct 2003 03:44:45 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9DIijlP007942;
	Tue, 14 Oct 2003 03:44:45 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA07941 ; Tue, 14 Oct 2003 03:44:45 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA16640; Tue, 14 Oct 2003 03:44:44 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA02253; Tue, 14 Oct 2003 03:44:43 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9DIihqT012694;
	Tue, 14 Oct 2003 03:44:43 +0900 (JST)
Received: from steelhead ([159.119.168.155]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMP00M2DLEHFH@tsbpo1.po.toshiba.co.jp>; Tue,
 14 Oct 2003 03:44:42 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A97fM-0002Lp-00; Mon, 13 Oct 2003 11:43:36 -0700
Date: Mon, 13 Oct 2003 11:43:36 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] comments on draft-ietf-pana-ipsec-00.txt
In-reply-to: <009b01c38f90$7f76caa0$5a100a0a@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031013184335.GC8264@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Mohan Parthasarathy <mohanp@sbcglobal.net>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031010175312.GC13449@steelhead>
 <009b01c38f90$7f76caa0$5a100a0a@adithya>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 10, 2003 at 05:42:03PM -0700, Mohan Parthasarathy wrote:
> Yoshihiro,
> 
> Thanks for your comments.
> 
> 
> >
> > o When MSK is updated as a result of EAP re-authentication, what IKE
> >   should do?  There would be several alternatives:
> >
> Do we know when reauthentication happens in practice ?

It can happen before authorization lifetime expires, where the
lifetime can be carried in a Session-Timeout attribute in RADIUS
Access-Accept.

> 
> >   - Immediately update the ISAKMP SA by performing IKE phase 1
> >     negotiation with using a fresh IKE pre-shared key derived from the
> >     new MSK.
> >
> >   - The ISAKMP SA is not immediately updated when the MSK is updated.
> >     In a future IKE phase 1 negotiation performed due to e.g.,
> >     expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
> >     derived from the latest MSK available at the time of the
> >     negotiation.
> >
> >   - The ISAKMP SA is not immediately updated when the MSK is updated.
> >     In a future IKE phase 1 negotiation performed due to e.g.,
> >     expiration of the ISAKMP SA lifetime, the IKE pre-shared key is
> >     derived from the initially derived MSK, not a new one.
> >
> > I'm not sure which alternative is appropriate.
> >
> The option  1 or 2 seems better to me.  Do you think we should clarify this
> in
> the document ? At least this would help better inter-op i guess.

Yes, I think we should describe it for improving interoperability.
Maybe option 2 by default.

> 
> >
> > o In Sections 6 and 7.2, link-local address is used in outer headers
> >   in IPv6.  Should link-local address is also used in the case where
> >   PAA and EP are co-located and PANA runs over an IP-in-IP link (i.e.,
> >   PaC and PAA/EP are logically one IP-hop away but may be several IP
> >   hops away at a lower level)?  In such a case, I think using global
> >   IP address in outer headers of the IPsec tunnel makes sense.  Or
> >   should the IP-in-IP case be out of the scope of the document?
> >
> I think IP-in-IP is out of scope. Do you see a scenario where PaC and PAA/EP
> are connected via a tunnel ?

A possible scenario for this is that PANA can be used for
bootstrapping Mobile IPv6 Mobility Security Association (MSA) between
a moble node and a home agent.

> 
> >
> > o In Section 5, replace "phase I" with "phase 1."
> >
> okay.
> 
> > o In Section 9,
> >
> > change:
> >
> >    "If the PAA does not verify whether PaC is authorized to use an IP
> >    address, it is possible for the PaC to steal the traffic destined to
> >    some other PaC. The use of IPsec does not prevent this attack. PAA
> >    may use other mechanisms to prevent this attack."
> >
> > to:
> >
> >    "If the PAA does not verify whether PaC is authorized to use an IP
> >    address, it is possible for the PaC to steal the traffic destined to
> >    some other PaC. The use of IPsec does not prevent this attack. PAA
> >    may use other mechanisms such as SEND [SEND] to prevent this attack."
> >
> >    Where [SEND] refers to draft-ietf-send-ipsec-01.txt.
> >
> okay.
> 
> > o In Section 9,
> >
> >    "When IPv6 is used, the SPD entries bypass all link-local traffic
> >    without applying IPsec. This should not be a limitation as the link-
> >    local address is used only by link-local services e.g.
> >    neighbor/router discovery, which uses a different mechanism to
> >    protect their traffic. Moreover, this limitation may not be there in
> >    the future if IPsec extends the SPD selectors to specify ICMP types."
> >
> > The last sentence seems to imply that PANA can also be used for
> > bootstrapping IPsec for protecting IPv6 Router Discovery, which could
> > provide a method to securely performing IPv6 address autoconfiguration
> > without modifying the existing ESP or AH at all (just a modification
> > to SPD selectors).  I think it is worth mentioning that.
> >
> Yeah, it is a possibility. But it really depends on what SEND standardizes.
> Where do you want to mention this in the document ?

SEND provides a PKI-based method for protecting Router Discovery by
using digital certificates issued to routers from a trusted 3rd party, 
but does not specify a AAA-based method for protecting Router Discovery.
PANA can cover the latter case which is not covered by SEND.

Yoshihiro Ohba

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

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



From pana-admin@ietf.org  Mon Oct 13 14:56:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20100
	for <pana-archive@lists.ietf.org>; Mon, 13 Oct 2003 14:56:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97rO-0001Ya-Hh; Mon, 13 Oct 2003 14:56:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97r5-0001SK-6J
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 14:55:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20070
	for <pana@ietf.org>; Mon, 13 Oct 2003 14:55:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A97r2-0006ky-00
	for pana@ietf.org; Mon, 13 Oct 2003 14:55:40 -0400
Received: from smtp803.mail.sc5.yahoo.com ([66.163.168.182])
	by ietf-mx with smtp (Exim 4.12)
	id 1A97r1-0006ku-00
	for pana@ietf.org; Mon, 13 Oct 2003 14:55:39 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 13 Oct 2003 18:55:38 -0000
Message-ID: <002e01c391bb$9b1a74a0$3d100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Tschofenig Hannes" <hannes.tschofenig@siemens.com>, <pana@ietf.org>
References: <2A8DB02E3018D411901B009027FD3A3F03BC029E@mchp905a.mch.sbs.de>
Subject: Re: [Pana] comments to pana-ipsec
Date: Mon, 13 Oct 2003 11:55:43 -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.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


> hi mohan,
> hi all,
>
> working on a pana implementation (including packet filter creation and
ipsec
> sa establishment) we had to notice that there is a problem getting pana
and
> ike to interact.
>
> after pana authentication and key exchange is finished some parameters
(such
> as keys and ip address info) have to be provided to ike. using the
freeswan
> (pluto) and freebsd (racoon) ike implementations we noticed that these
> parameter cannot be added dynamically. these implemenations require
changes
> to plaintext files and some other configuration steps which makes the
> interworking difficult (without speaking about the performance impact).
>
> is someone aware of an ike implementation which allows ike to be
configured
> dynamically (possible via an api)?
>
I don't know of an implementation. Others might know. But this is not
totally new.
In 3GPP2, IKE implementations had to provide an API where the pre-shared key
was derived outside of IKE  configuration. If i remember correctly it was
more like
an opaque ID_KEY_ID that is given to IKE (derived using FA, HA, etc.) for
presenting in phase I by FA to HA. Perhaps the standard ones don't have it
and
one had to implement it.

-mohan

> ciao
> hannes
>
> _______________________________________________
> 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 exim@www1.ietf.org  Mon Oct 13 14:56:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20116
	for <pana-archive@odin.ietf.org>; Mon, 13 Oct 2003 14:56:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97rT-0001ZV-25
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 14:56:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9DIu759006034
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 14:56:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97rS-0001ZF-Rv
	for pana-web-archive@optimus.ietf.org; Mon, 13 Oct 2003 14:56:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20078
	for <pana-web-archive@ietf.org>; Mon, 13 Oct 2003 14:55:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A97rP-0006l4-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 14:56:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A97rP-0006l1-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 14:56:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97rO-0001Ya-Hh; Mon, 13 Oct 2003 14:56:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A97r5-0001SK-6J
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 14:55:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20070
	for <pana@ietf.org>; Mon, 13 Oct 2003 14:55:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A97r2-0006ky-00
	for pana@ietf.org; Mon, 13 Oct 2003 14:55:40 -0400
Received: from smtp803.mail.sc5.yahoo.com ([66.163.168.182])
	by ietf-mx with smtp (Exim 4.12)
	id 1A97r1-0006ku-00
	for pana@ietf.org; Mon, 13 Oct 2003 14:55:39 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 13 Oct 2003 18:55:38 -0000
Message-ID: <002e01c391bb$9b1a74a0$3d100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Tschofenig Hannes" <hannes.tschofenig@siemens.com>, <pana@ietf.org>
References: <2A8DB02E3018D411901B009027FD3A3F03BC029E@mchp905a.mch.sbs.de>
Subject: Re: [Pana] comments to pana-ipsec
Date: Mon, 13 Oct 2003 11:55:43 -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.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> hi mohan,
> hi all,
>
> working on a pana implementation (including packet filter creation and
ipsec
> sa establishment) we had to notice that there is a problem getting pana
and
> ike to interact.
>
> after pana authentication and key exchange is finished some parameters
(such
> as keys and ip address info) have to be provided to ike. using the
freeswan
> (pluto) and freebsd (racoon) ike implementations we noticed that these
> parameter cannot be added dynamically. these implemenations require
changes
> to plaintext files and some other configuration steps which makes the
> interworking difficult (without speaking about the performance impact).
>
> is someone aware of an ike implementation which allows ike to be
configured
> dynamically (possible via an api)?
>
I don't know of an implementation. Others might know. But this is not
totally new.
In 3GPP2, IKE implementations had to provide an API where the pre-shared key
was derived outside of IKE  configuration. If i remember correctly it was
more like
an opaque ID_KEY_ID that is given to IKE (derived using FA, HA, etc.) for
presenting in phase I by FA to HA. Perhaps the standard ones don't have it
and
one had to implement it.

-mohan

> ciao
> hannes
>
> _______________________________________________
> 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-admin@ietf.org  Mon Oct 13 17:29:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00155
	for <pana-archive@lists.ietf.org>; Mon, 13 Oct 2003 17:29:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AFQ-0001cV-Hh; Mon, 13 Oct 2003 17:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AEc-0001bd-66
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 17:28:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00112
	for <pana@ietf.org>; Mon, 13 Oct 2003 17:27:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AEZ-0001Zs-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:28:07 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AEY-0001Zm-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:28:07 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9DLS5F1014085
	for <pana@ietf.org>; Tue, 14 Oct 2003 06:28:05 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9DLS5Ja000725
	for <pana@ietf.org>; Tue, 14 Oct 2003 06:28:05 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id GAA00724 ; Tue, 14 Oct 2003 06:28:05 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA24344; Tue, 14 Oct 2003 06:28:04 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA29857; Tue, 14 Oct 2003 06:28:04 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9DLS3qT013412
	for <pana@ietf.org>; Tue, 14 Oct 2003 06:28:04 +0900 (JST)
Received: from steelhead ([159.119.168.155]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMP00531SYQ19@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Tue,
 14 Oct 2003 06:28:02 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9AEA-0002j2-00 for <pana@ietf.org>; Mon, 13 Oct 2003 14:27:42 -0700
Date: Mon, 13 Oct 2003 14:27:42 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031013212742.GA10306@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.4i
Subject: [Pana] issue 23 and 25
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

There are two PANA draft -01 issues for which I'm not sure about the
consensus.

Issue 23: PANA Message type/AVP numbers and Diameter command codes/AVPs

Issue 25: Service Profile names

In addition, there is one remaining issue on Issue 19: whether 
Result Code "PANA_REALM_NOT_SERVED" should be supported or not.

Any comments?

Yoshihiro Ohba

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


From exim@www1.ietf.org  Mon Oct 13 17:29:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00171
	for <pana-archive@odin.ietf.org>; Mon, 13 Oct 2003 17:29:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AFX-0001dI-MJ
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 17:29:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9DLT7UF006270
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 17:29:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AFX-0001d3-GK
	for pana-web-archive@optimus.ietf.org; Mon, 13 Oct 2003 17:29:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00134
	for <pana-web-archive@ietf.org>; Mon, 13 Oct 2003 17:28:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AFV-0001am-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 17:29:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AFU-0001aj-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 17:29:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AFQ-0001cV-Hh; Mon, 13 Oct 2003 17:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AEc-0001bd-66
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 17:28:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00112
	for <pana@ietf.org>; Mon, 13 Oct 2003 17:27:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AEZ-0001Zs-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:28:07 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AEY-0001Zm-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:28:07 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9DLS5F1014085
	for <pana@ietf.org>; Tue, 14 Oct 2003 06:28:05 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9DLS5Ja000725
	for <pana@ietf.org>; Tue, 14 Oct 2003 06:28:05 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id GAA00724 ; Tue, 14 Oct 2003 06:28:05 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA24344; Tue, 14 Oct 2003 06:28:04 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA29857; Tue, 14 Oct 2003 06:28:04 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9DLS3qT013412
	for <pana@ietf.org>; Tue, 14 Oct 2003 06:28:04 +0900 (JST)
Received: from steelhead ([159.119.168.155]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMP00531SYQ19@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Tue,
 14 Oct 2003 06:28:02 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9AEA-0002j2-00 for <pana@ietf.org>; Mon, 13 Oct 2003 14:27:42 -0700
Date: Mon, 13 Oct 2003 14:27:42 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031013212742.GA10306@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.4i
Subject: [Pana] issue 23 and 25
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

There are two PANA draft -01 issues for which I'm not sure about the
consensus.

Issue 23: PANA Message type/AVP numbers and Diameter command codes/AVPs

Issue 25: Service Profile names

In addition, there is one remaining issue on Issue 19: whether 
Result Code "PANA_REALM_NOT_SERVED" should be supported or not.

Any comments?

Yoshihiro Ohba

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



From pana-admin@ietf.org  Mon Oct 13 17:42:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00841
	for <pana-archive@lists.ietf.org>; Mon, 13 Oct 2003 17:42:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AS0-0002O9-VG; Mon, 13 Oct 2003 17:42:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ARE-0002N3-VG
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 17:41:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00695
	for <pana@ietf.org>; Mon, 13 Oct 2003 17:41:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ARA-0001n6-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:41:09 -0400
Received: from smtp809.mail.sc5.yahoo.com ([66.163.168.188])
	by ietf-mx with smtp (Exim 4.12)
	id 1A9ARA-0001n2-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:41:08 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 13 Oct 2003 21:40:52 -0000
Message-ID: <009901c391d2$af8f2720$3d100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <20031010175312.GC13449@steelhead> <009b01c38f90$7f76caa0$5a100a0a@adithya> <20031013184335.GC8264@steelhead>
Subject: Re: [Pana] comments on draft-ietf-pana-ipsec-00.txt
Date: Mon, 13 Oct 2003 14:40:54 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

 > >
> > >
> > > o In Sections 6 and 7.2, link-local address is used in outer headers
> > >   in IPv6.  Should link-local address is also used in the case where
> > >   PAA and EP are co-located and PANA runs over an IP-in-IP link (i.e.,
> > >   PaC and PAA/EP are logically one IP-hop away but may be several IP
> > >   hops away at a lower level)?  In such a case, I think using global
> > >   IP address in outer headers of the IPsec tunnel makes sense.  Or
> > >   should the IP-in-IP case be out of the scope of the document?
> > >
> > I think IP-in-IP is out of scope. Do you see a scenario where PaC and
PAA/EP
> > are connected via a tunnel ?
>
> A possible scenario for this is that PANA can be used for
> bootstrapping Mobile IPv6 Mobility Security Association (MSA) between
> a moble node and a home agent.
>
Sure. But why does that require a MN and PAA/EP connected by a tunnel ?
The tunnel between MN and HA is similar to the Double IPsec case where
HA can be seen as the VPN gateway. I still don't understand.
Could  you clarify ?

 > > >
> > >    "When IPv6 is used, the SPD entries bypass all link-local traffic
> > >    without applying IPsec. This should not be a limitation as the
link-
> > >    local address is used only by link-local services e.g.
> > >    neighbor/router discovery, which uses a different mechanism to
> > >    protect their traffic. Moreover, this limitation may not be there
in
> > >    the future if IPsec extends the SPD selectors to specify ICMP
types."
> > >
> > > The last sentence seems to imply that PANA can also be used for
> > > bootstrapping IPsec for protecting IPv6 Router Discovery, which could
> > > provide a method to securely performing IPv6 address autoconfiguration
> > > without modifying the existing ESP or AH at all (just a modification
> > > to SPD selectors).  I think it is worth mentioning that.
> > >
> > Yeah, it is a possibility. But it really depends on what SEND
standardizes.
> > Where do you want to mention this in the document ?
>
> SEND provides a PKI-based method for protecting Router Discovery by
> using digital certificates issued to routers from a trusted 3rd party,
> but does not specify a AAA-based method for protecting Router Discovery.
> PANA can cover the latter case which is not covered by SEND.
>
Sure.  I will try to mention it in the document.

-mohan

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


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


From exim@www1.ietf.org  Mon Oct 13 17:42:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00856
	for <pana-archive@odin.ietf.org>; Mon, 13 Oct 2003 17:42:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AS3-0002P1-Sd
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 17:42:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9DLg3v2009229
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 17:42:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AS3-0002Om-Mg
	for pana-web-archive@optimus.ietf.org; Mon, 13 Oct 2003 17:42:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00795
	for <pana-web-archive@ietf.org>; Mon, 13 Oct 2003 17:41:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AS1-0001o0-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 17:42:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AS0-0001nx-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 17:42:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AS0-0002O9-VG; Mon, 13 Oct 2003 17:42:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ARE-0002N3-VG
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 17:41:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00695
	for <pana@ietf.org>; Mon, 13 Oct 2003 17:41:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ARA-0001n6-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:41:09 -0400
Received: from smtp809.mail.sc5.yahoo.com ([66.163.168.188])
	by ietf-mx with smtp (Exim 4.12)
	id 1A9ARA-0001n2-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:41:08 -0400
Received: from mail.atheros.com (HELO adithya) (mohanp@sbcglobal.net@65.212.155.130 with login)
  by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 13 Oct 2003 21:40:52 -0000
Message-ID: <009901c391d2$af8f2720$3d100a0a@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <20031010175312.GC13449@steelhead> <009b01c38f90$7f76caa0$5a100a0a@adithya> <20031013184335.GC8264@steelhead>
Subject: Re: [Pana] comments on draft-ietf-pana-ipsec-00.txt
Date: Mon, 13 Oct 2003 14:40:54 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 > >
> > >
> > > o In Sections 6 and 7.2, link-local address is used in outer headers
> > >   in IPv6.  Should link-local address is also used in the case where
> > >   PAA and EP are co-located and PANA runs over an IP-in-IP link (i.e.,
> > >   PaC and PAA/EP are logically one IP-hop away but may be several IP
> > >   hops away at a lower level)?  In such a case, I think using global
> > >   IP address in outer headers of the IPsec tunnel makes sense.  Or
> > >   should the IP-in-IP case be out of the scope of the document?
> > >
> > I think IP-in-IP is out of scope. Do you see a scenario where PaC and
PAA/EP
> > are connected via a tunnel ?
>
> A possible scenario for this is that PANA can be used for
> bootstrapping Mobile IPv6 Mobility Security Association (MSA) between
> a moble node and a home agent.
>
Sure. But why does that require a MN and PAA/EP connected by a tunnel ?
The tunnel between MN and HA is similar to the Double IPsec case where
HA can be seen as the VPN gateway. I still don't understand.
Could  you clarify ?

 > > >
> > >    "When IPv6 is used, the SPD entries bypass all link-local traffic
> > >    without applying IPsec. This should not be a limitation as the
link-
> > >    local address is used only by link-local services e.g.
> > >    neighbor/router discovery, which uses a different mechanism to
> > >    protect their traffic. Moreover, this limitation may not be there
in
> > >    the future if IPsec extends the SPD selectors to specify ICMP
types."
> > >
> > > The last sentence seems to imply that PANA can also be used for
> > > bootstrapping IPsec for protecting IPv6 Router Discovery, which could
> > > provide a method to securely performing IPv6 address autoconfiguration
> > > without modifying the existing ESP or AH at all (just a modification
> > > to SPD selectors).  I think it is worth mentioning that.
> > >
> > Yeah, it is a possibility. But it really depends on what SEND
standardizes.
> > Where do you want to mention this in the document ?
>
> SEND provides a PKI-based method for protecting Router Discovery by
> using digital certificates issued to routers from a trusted 3rd party,
> but does not specify a AAA-based method for protecting Router Discovery.
> PANA can cover the latter case which is not covered by SEND.
>
Sure.  I will try to mention it in the document.

-mohan

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


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



From pana-admin@ietf.org  Mon Oct 13 17:58:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01283
	for <pana-archive@lists.ietf.org>; Mon, 13 Oct 2003 17:58:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AhV-00031O-7m; Mon, 13 Oct 2003 17:58:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AhQ-000319-CI
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 17:57:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01261
	for <pana@ietf.org>; Mon, 13 Oct 2003 17:57:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AhN-0001zR-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:57:53 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AhM-0001zL-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:57:52 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9DLvpF1019963;
	Tue, 14 Oct 2003 06:57:51 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9DLvoXT008403;
	Tue, 14 Oct 2003 06:57:50 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id GAA08400 ; Tue, 14 Oct 2003 06:57:49 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA29949; Tue, 14 Oct 2003 06:57:48 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA02620; Tue, 14 Oct 2003 06:57:48 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9DLvlqT017956;
	Tue, 14 Oct 2003 06:57:47 +0900 (JST)
Received: from steelhead ([159.119.168.77]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMP00625UC9AW@tsbpo1.po.toshiba.co.jp>; Tue,
 14 Oct 2003 06:57:47 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9Aem-0002mE-00; Mon, 13 Oct 2003 14:55:12 -0700
Date: Mon, 13 Oct 2003 14:55:12 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] comments on draft-ietf-pana-ipsec-00.txt
In-reply-to: <009901c391d2$af8f2720$3d100a0a@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031013215512.GB10306@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Mohan Parthasarathy <mohanp@sbcglobal.net>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031010175312.GC13449@steelhead>
 <009b01c38f90$7f76caa0$5a100a0a@adithya> <20031013184335.GC8264@steelhead>
 <009901c391d2$af8f2720$3d100a0a@adithya>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Mohan,

Please see my comments inline.

On Mon, Oct 13, 2003 at 02:40:54PM -0700, Mohan Parthasarathy wrote:
>  > >
> > > >
> > > > o In Sections 6 and 7.2, link-local address is used in outer headers
> > > >   in IPv6.  Should link-local address is also used in the case where
> > > >   PAA and EP are co-located and PANA runs over an IP-in-IP link (i.e.,
> > > >   PaC and PAA/EP are logically one IP-hop away but may be several IP
> > > >   hops away at a lower level)?  In such a case, I think using global
> > > >   IP address in outer headers of the IPsec tunnel makes sense.  Or
> > > >   should the IP-in-IP case be out of the scope of the document?
> > > >
> > > I think IP-in-IP is out of scope. Do you see a scenario where PaC and
> PAA/EP
> > > are connected via a tunnel ?
> >
> > A possible scenario for this is that PANA can be used for
> > bootstrapping Mobile IPv6 Mobility Security Association (MSA) between
> > a moble node and a home agent.
> >
> Sure. But why does that require a MN and PAA/EP connected by a tunnel ?
> The tunnel between MN and HA is similar to the Double IPsec case where
> HA can be seen as the VPN gateway. I still don't understand.
> Could  you clarify ?

I also don't see a reason other than the WG scope reason to force to
use IP-in-IP for this case.  It might be better not to consider the
bootstrapping MSA scenario until required by MIPv6.  

> 
>  > > >
> > > >    "When IPv6 is used, the SPD entries bypass all link-local traffic
> > > >    without applying IPsec. This should not be a limitation as the
> link-
> > > >    local address is used only by link-local services e.g.
> > > >    neighbor/router discovery, which uses a different mechanism to
> > > >    protect their traffic. Moreover, this limitation may not be there
> in
> > > >    the future if IPsec extends the SPD selectors to specify ICMP
> types."
> > > >
> > > > The last sentence seems to imply that PANA can also be used for
> > > > bootstrapping IPsec for protecting IPv6 Router Discovery, which could
> > > > provide a method to securely performing IPv6 address autoconfiguration
> > > > without modifying the existing ESP or AH at all (just a modification
> > > > to SPD selectors).  I think it is worth mentioning that.
> > > >
> > > Yeah, it is a possibility. But it really depends on what SEND
> standardizes.
> > > Where do you want to mention this in the document ?
> >
> > SEND provides a PKI-based method for protecting Router Discovery by
> > using digital certificates issued to routers from a trusted 3rd party,
> > but does not specify a AAA-based method for protecting Router Discovery.
> > PANA can cover the latter case which is not covered by SEND.
> >
> Sure.  I will try to mention it in the document.

OK.

> 
> -mohan

Yoshihiro Ohba

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


From exim@www1.ietf.org  Mon Oct 13 17:58:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01298
	for <pana-archive@odin.ietf.org>; Mon, 13 Oct 2003 17:58:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AhX-000324-UB
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 17:58:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9DLw3tN011650
	for pana-archive@odin.ietf.org; Mon, 13 Oct 2003 17:58:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AhX-00031p-Po
	for pana-web-archive@optimus.ietf.org; Mon, 13 Oct 2003 17:58:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01267
	for <pana-web-archive@ietf.org>; Mon, 13 Oct 2003 17:57:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AhV-0001za-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 17:58:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AhU-0001zX-00
	for pana-web-archive@ietf.org; Mon, 13 Oct 2003 17:58:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AhV-00031O-7m; Mon, 13 Oct 2003 17:58:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9AhQ-000319-CI
	for pana@optimus.ietf.org; Mon, 13 Oct 2003 17:57:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01261
	for <pana@ietf.org>; Mon, 13 Oct 2003 17:57:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AhN-0001zR-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:57:53 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9AhM-0001zL-00
	for pana@ietf.org; Mon, 13 Oct 2003 17:57:52 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9DLvpF1019963;
	Tue, 14 Oct 2003 06:57:51 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9DLvoXT008403;
	Tue, 14 Oct 2003 06:57:50 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id GAA08400 ; Tue, 14 Oct 2003 06:57:49 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA29949; Tue, 14 Oct 2003 06:57:48 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA02620; Tue, 14 Oct 2003 06:57:48 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9DLvlqT017956;
	Tue, 14 Oct 2003 06:57:47 +0900 (JST)
Received: from steelhead ([159.119.168.77]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMP00625UC9AW@tsbpo1.po.toshiba.co.jp>; Tue,
 14 Oct 2003 06:57:47 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9Aem-0002mE-00; Mon, 13 Oct 2003 14:55:12 -0700
Date: Mon, 13 Oct 2003 14:55:12 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] comments on draft-ietf-pana-ipsec-00.txt
In-reply-to: <009901c391d2$af8f2720$3d100a0a@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031013215512.GB10306@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Mohan Parthasarathy <mohanp@sbcglobal.net>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031010175312.GC13449@steelhead>
 <009b01c38f90$7f76caa0$5a100a0a@adithya> <20031013184335.GC8264@steelhead>
 <009901c391d2$af8f2720$3d100a0a@adithya>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Mohan,

Please see my comments inline.

On Mon, Oct 13, 2003 at 02:40:54PM -0700, Mohan Parthasarathy wrote:
>  > >
> > > >
> > > > o In Sections 6 and 7.2, link-local address is used in outer headers
> > > >   in IPv6.  Should link-local address is also used in the case where
> > > >   PAA and EP are co-located and PANA runs over an IP-in-IP link (i.e.,
> > > >   PaC and PAA/EP are logically one IP-hop away but may be several IP
> > > >   hops away at a lower level)?  In such a case, I think using global
> > > >   IP address in outer headers of the IPsec tunnel makes sense.  Or
> > > >   should the IP-in-IP case be out of the scope of the document?
> > > >
> > > I think IP-in-IP is out of scope. Do you see a scenario where PaC and
> PAA/EP
> > > are connected via a tunnel ?
> >
> > A possible scenario for this is that PANA can be used for
> > bootstrapping Mobile IPv6 Mobility Security Association (MSA) between
> > a moble node and a home agent.
> >
> Sure. But why does that require a MN and PAA/EP connected by a tunnel ?
> The tunnel between MN and HA is similar to the Double IPsec case where
> HA can be seen as the VPN gateway. I still don't understand.
> Could  you clarify ?

I also don't see a reason other than the WG scope reason to force to
use IP-in-IP for this case.  It might be better not to consider the
bootstrapping MSA scenario until required by MIPv6.  

> 
>  > > >
> > > >    "When IPv6 is used, the SPD entries bypass all link-local traffic
> > > >    without applying IPsec. This should not be a limitation as the
> link-
> > > >    local address is used only by link-local services e.g.
> > > >    neighbor/router discovery, which uses a different mechanism to
> > > >    protect their traffic. Moreover, this limitation may not be there
> in
> > > >    the future if IPsec extends the SPD selectors to specify ICMP
> types."
> > > >
> > > > The last sentence seems to imply that PANA can also be used for
> > > > bootstrapping IPsec for protecting IPv6 Router Discovery, which could
> > > > provide a method to securely performing IPv6 address autoconfiguration
> > > > without modifying the existing ESP or AH at all (just a modification
> > > > to SPD selectors).  I think it is worth mentioning that.
> > > >
> > > Yeah, it is a possibility. But it really depends on what SEND
> standardizes.
> > > Where do you want to mention this in the document ?
> >
> > SEND provides a PKI-based method for protecting Router Discovery by
> > using digital certificates issued to routers from a trusted 3rd party,
> > but does not specify a AAA-based method for protecting Router Discovery.
> > PANA can cover the latter case which is not covered by SEND.
> >
> Sure.  I will try to mention it in the document.

OK.

> 
> -mohan

Yoshihiro Ohba

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



From pana-admin@ietf.org  Tue Oct 14 01:55:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14293
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 01:55:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9I97-0006Gz-48; Tue, 14 Oct 2003 01:55:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9I8N-0006G1-Vp
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 01:54:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14269
	for <pana@ietf.org>; Tue, 14 Oct 2003 01:54:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9I8K-00065H-00
	for pana@ietf.org; Tue, 14 Oct 2003 01:54:12 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9I8J-00065D-00
	for pana@ietf.org; Tue, 14 Oct 2003 01:54:12 -0400
Date: Mon, 13 Oct 2003 22:54:03 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBB0DD8B.A5ED%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA0143C594@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> In PANA we retransmit requests because we want to have reliable
> transport. So, the case where the authenticator retransmits the
> EAP-Request/Identity is interpreted differently in PANA layer
> (retransmissions for reliability).
> 
> The case of Notification Request is usable, but what does
> "invalid authentication attempt" mean? Can we interpret it such
> a way that it means "typo in the identity, user part" or "user
> not recognized" or "realm not served"..

Good points, but that does not mean they are problems for PANA to solve.

Generally I'm concerned about leaking EAP-layer events or actions into PANA.
But I think in this case, this is more of mapping an EAP lower-layer
(Diameter) event to PANA. While I wouldn't simply import all such events
from one to another, I think this one might be useful and not disruptive. On
the other hand, this error message is different from all the others. Those
are all PANA-specific.

Hmmm... Does anyone else care to comment on this?

Alper


> 
> A result code in PANA for this (borrowed from Diameter) is clear
> and works if the authenticator implementation doesn't support
> this MAY part of the EAP doc.
> 
> - Dan
> 
> 
>> -----Original Message-----
>> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
>> Sent: 07 October, 2003 20:55
>> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
>> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>> 
>> 
>>>> I think this is also an EAP question. What would be the EAP
>>>> behavior when
>>>> the NAS cannot recognize the EAP client identifier?
>> 
>> I think this case would be handled by the following text from
>> the EAP spec:
>> 
>>          Implementation Note: The peer MAY obtain the
>> Identity via user
>>          input.  It is suggested that the authenticator retry the
>>          Identity Request in the case of an invalid Identity or
>>          authentication failure to allow for potential typos
>> on the part
>>          of the user.  It is suggested that the Identity Request be
>>          retried a minimum of 3 times before terminating the
>>          authentication.  The Notification Request MAY be used to
>>          indicate an invalid authentication attempt prior to
>>          transmitting a new Identity Request (optionally, the failure
>>          MAY be indicated within the message of the new
>> Identity Request
>>          itself).
>> 
>> ... And finally I think the EAP authenticator would send a
>> Failure message.
>> 
>> Alper
>> 
>> 
>> 
> 
> 


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


From exim@www1.ietf.org  Tue Oct 14 01:55:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14308
	for <pana-archive@odin.ietf.org>; Tue, 14 Oct 2003 01:55:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9I9C-0006HZ-Us
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 01:55:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9E5t66h024150
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 01:55:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9I9C-0006HR-Kn
	for pana-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 01:55:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14280
	for <pana-web-archive@ietf.org>; Tue, 14 Oct 2003 01:54:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9I99-00065U-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 01:55:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9I98-00065R-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 01:55:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9I97-0006Gz-48; Tue, 14 Oct 2003 01:55:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9I8N-0006G1-Vp
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 01:54:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA14269
	for <pana@ietf.org>; Tue, 14 Oct 2003 01:54:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9I8K-00065H-00
	for pana@ietf.org; Tue, 14 Oct 2003 01:54:12 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9I8J-00065D-00
	for pana@ietf.org; Tue, 14 Oct 2003 01:54:12 -0400
Date: Mon, 13 Oct 2003 22:54:03 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBB0DD8B.A5ED%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA0143C594@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> In PANA we retransmit requests because we want to have reliable
> transport. So, the case where the authenticator retransmits the
> EAP-Request/Identity is interpreted differently in PANA layer
> (retransmissions for reliability).
> 
> The case of Notification Request is usable, but what does
> "invalid authentication attempt" mean? Can we interpret it such
> a way that it means "typo in the identity, user part" or "user
> not recognized" or "realm not served"..

Good points, but that does not mean they are problems for PANA to solve.

Generally I'm concerned about leaking EAP-layer events or actions into PANA.
But I think in this case, this is more of mapping an EAP lower-layer
(Diameter) event to PANA. While I wouldn't simply import all such events
from one to another, I think this one might be useful and not disruptive. On
the other hand, this error message is different from all the others. Those
are all PANA-specific.

Hmmm... Does anyone else care to comment on this?

Alper


> 
> A result code in PANA for this (borrowed from Diameter) is clear
> and works if the authenticator implementation doesn't support
> this MAY part of the EAP doc.
> 
> - Dan
> 
> 
>> -----Original Message-----
>> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
>> Sent: 07 October, 2003 20:55
>> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
>> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>> 
>> 
>>>> I think this is also an EAP question. What would be the EAP
>>>> behavior when
>>>> the NAS cannot recognize the EAP client identifier?
>> 
>> I think this case would be handled by the following text from
>> the EAP spec:
>> 
>>          Implementation Note: The peer MAY obtain the
>> Identity via user
>>          input.  It is suggested that the authenticator retry the
>>          Identity Request in the case of an invalid Identity or
>>          authentication failure to allow for potential typos
>> on the part
>>          of the user.  It is suggested that the Identity Request be
>>          retried a minimum of 3 times before terminating the
>>          authentication.  The Notification Request MAY be used to
>>          indicate an invalid authentication attempt prior to
>>          transmitting a new Identity Request (optionally, the failure
>>          MAY be indicated within the message of the new
>> Identity Request
>>          itself).
>> 
>> ... And finally I think the EAP authenticator would send a
>> Failure message.
>> 
>> Alper
>> 
>> 
>> 
> 
> 


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



From pana-request@research.telcordia.com  Tue Oct 14 02:20:22 2003
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27075
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 02:20:13 -0400 (EDT)
Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8])
	by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id h9E6AWes015535;
	Tue, 14 Oct 2003 02:10:32 -0400 (EDT)
Received: (from slmgr@localhost)
	by donner.research.telcordia.com (8.8.8/8.8.8) id CAA21258;
	Tue, 14 Oct 2003 02:10:32 -0400 (EDT)
Resent-Date: Tue, 14 Oct 2003 02:10:32 -0400 (EDT)
X-Authentication-Warning: donner.research.telcordia.com: slmgr set sender to pana-request@research.telcordia.com using -f
Old-Return-Path: <alper@docomolabs-usa.com>
Date: Mon, 13 Oct 2003 23:10:11 -0700
Subject: Re: New [issue25] Service Profile names
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Dan.Forsberg@nokia.com>, <pana@research.telcordia.com>
Message-ID: <BBB0E153.A5F6%alper@docomolabs-usa.com>
In-Reply-To: <20031009174816.GA8231@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi)
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper)
Resent-Message-ID: <weBx0B.A.BMF.XN5i_@donner>
Resent-From: pana@research.telcordia.com
X-Mailing-List: <pana@research.telcordia.com> 
X-Loop: pana@research.telcordia.com
List-Post: <mailto:pana@research.telcordia.com>
List-Help: <mailto:pana-request@research.telcordia.com?subject=help>
Precedence: list
Resent-Sender: pana-request@research.telcordia.com
Content-Transfer-Encoding: 7bit


I agree with the earlier text proposed for handling service profile
advertisements.

One question: does it make sense to allow PaC to optionally include an ISP
or NAP identifier in the PANA-start-answer to identify the binding between
the subsequent authentication and the service provider? This can be an
optional feature. When not stated, the realm as suggested by the EAP
identifier provides this information.

> In the initial text I recently provided, one NAP-Information AVP and
> zero or more ISP-Information AVPs can optionally be carried in
> PANA-Start-Request, where each AVP includes a unique (IANA-assigned)
> provider identifier and a provider name.
> 
> When there are multiple PAAs, this kind of information could
> be used by PaC to choose a PAA.  So this issue might result in
> re-consideration of the current PAA selection procedure:
> 
> "There can be multiple PAAs on the link. The result does not depend
> on which PAA PaC chooses. By default PaC chooses the PAA that sent
> the first response."

I'm still not convinced that an access network would have PAAs from
different NAPs on the same link. Are we talking about multiple PAAs run by
the same NAP but possibly handling AAA traffic for different ISPs? Maybe
this happens.... Nevertheless, I agree we can re-consider the above text. It
is kind of limiting without justification...

Alper


> 
> Note that section 4 of draft-yacine-pana-paa2ep-prot-eval-00.txt also
> addresses a similer issue.
> 
> Yoshihiro Ohba
> 
> 
> 
> On Thu, Sep 25, 2003 at 10:50:16AM -0700, Alper Yegin wrote:
>> 
>> This piece of data sounds informative and potentially useful. I presume if
>> we wanted to have this support, we'd define a new AVP that carries some sort
>> of an "identifier" and optionally carried in PANA-Start-Request. Do we have
>> to define the format of the data this AVP embeds? What type of information
>> would the data be carrying?
>> 
>> 
>> Alper
>> 
>> 
>>> I think more about this issue and now I tend to agree that the
>>> proposed functionality might be useful even if there is one PAA on an
>>> IP link.  First, there may be multiple IP links available at a
>>> physical location (e.g., a hotspot).  In such a case, if
>>> PANA-Start-Request messages sent by PAAs contain some profile
>>> information, a PaC can use the information to choose an appropriate IP
>>> link to start authentication.  Second, even if there is only one IP
>>> link in a physical location and one PAA on the link, a PaC can use the
>>> information to determine whether it starts authentication on the IP
>>> link or not.
>>> 
>>> Yoshihiro Ohba
>>> 
>>> 
>>> 
>>> On Wed, Sep 10, 2003 at 02:22:14PM +0300, Dan.Forsberg@nokia.com wrote:
>>>> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
>>>> 
>>>>> From Reinaldo Penno:
>>>> <klip>
>>>>> 3) In section 4.2, paragraph 3 it is mentioned that
>>>>> "The result does not depend on which PAA PaC chooses.
>>>>> By default PaC chooses the PAA that sent the first
>>>>> reponse"
>>>>> 
>>>>> This is the DHCP approach. Where all servers are
>>>>> equally good.
>>>>> 
>>>>> I would propose that we think about incorporating
>>>>> something of the PPPoE protocol that is widespread,
>>>>> since PANA is more related to the PPPoE model.
>>>>> 
>>>>> In the response of the Discovery message each PPPoE
>>>>> server include all the Service Profile (names) it
>>>>> supports (the definition is loose on purpose).
>>>>> Nowadays it is usually a list of ISPs or bandwidth
>>>>> packages a user can choose.
>>>>> 
>>>>> I would argue that in the case of PANA (and specially
>>>>> in the case of NAP vs ISP authentication), PAA servers
>>>>> might support a very different set of attributes and a
>>>>> PaC might prefer one over the other if it new of each
>>>>> choices.
>>>>> 
>>>>> We could have a AVP in PANA for that purpose in the
>>>>> answer to the Discovery message. it seems very simple,
>>>>> could be optional and will provide a crucial
>>>>> functionality for people that use PPPoE to migrate to
>>>>> PANA.
>>>> 
>>>> Yoshihiro Ohba:
>>>> 
>>>> When we dicussed NAP and ISP separate authentication, I think the
>>>> assumption is that there is a single PAA the PaC sees, and the NAI is
>>>> used to choose a particular ISP.  Why do you need multiple PAAs to
>>>> support NAP and ISP separate authentication?
>>>> 
>>>> 
>>>> ----------
>>>> category: Technical
>>>> document: draft-ietf-pana-pana-xx.txt
>>>> messages: 80
>>>> nosy: dforsber
>>>> priority: May Fix
>>>> status: Pending
>>>> title: Service Profile names
>>>> ________________________________________________
>>>> PANA Issues <pana_issues@danforsberg.info>
>>>> http://danforsberg.info:8080/pana-issues/issue25
>>>> ________________________________________________
>>>> 
>>> 
>>> 
>> 
> 



From pana-admin@ietf.org  Tue Oct 14 02:50:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27993
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 02:50:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9J0L-0001n2-LJ; Tue, 14 Oct 2003 02:50:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9IzT-0001lv-SL
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 02:49:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27974
	for <pana@ietf.org>; Tue, 14 Oct 2003 02:48:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9IzP-0006cd-00
	for pana@ietf.org; Tue, 14 Oct 2003 02:49:04 -0400
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9IzP-0006ca-00
	for pana@ietf.org; Tue, 14 Oct 2003 02:49:03 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by david.siemens.de (8.11.7/8.11.7) with ESMTP id h9E6n1k05201;
	Tue, 14 Oct 2003 08:49:02 +0200 (MEST)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h9E6n1x23671;
	Tue, 14 Oct 2003 08:49:01 +0200 (MEST)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19)
	id <4DN1PW1H>; Tue, 14 Oct 2003 08:48:53 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC02AC@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>, pana@ietf.org
Subject: RE: [Pana] comments to pana-ipsec
Date: Tue, 14 Oct 2003 08:48:50 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi mohan, 

thanks for pointing to work done at the 3gpp2. unfortunately i am only
familiar with 3gpp work where no such mechanisms are used. could you provide
a pointer to the document?

ciao
hannes


> -----Original Message-----
> From: Mohan Parthasarathy [mailto:mohanp@sbcglobal.net]
> Sent: Monday, October 13, 2003 8:56 PM
> To: Tschofenig Hannes; pana@ietf.org
> Subject: Re: [Pana] comments to pana-ipsec
> 
> 
> 
> > hi mohan,
> > hi all,
> >
> > working on a pana implementation (including packet filter 
> creation and
> ipsec
> > sa establishment) we had to notice that there is a problem 
> getting pana
> and
> > ike to interact.
> >
> > after pana authentication and key exchange is finished some 
> parameters
> (such
> > as keys and ip address info) have to be provided to ike. using the
> freeswan
> > (pluto) and freebsd (racoon) ike implementations we noticed 
> that these
> > parameter cannot be added dynamically. these implemenations require
> changes
> > to plaintext files and some other configuration steps which 
> makes the
> > interworking difficult (without speaking about the 
> performance impact).
> >
> > is someone aware of an ike implementation which allows ike to be
> configured
> > dynamically (possible via an api)?
> >
> I don't know of an implementation. Others might know. But this is not
> totally new.
> In 3GPP2, IKE implementations had to provide an API where the 
> pre-shared key
> was derived outside of IKE  configuration. If i remember 
> correctly it was
> more like
> an opaque ID_KEY_ID that is given to IKE (derived using FA, 
> HA, etc.) for
> presenting in phase I by FA to HA. Perhaps the standard ones 
> don't have it
> and
> one had to implement it.
> 
> -mohan
> 
> > ciao
> > hannes
> >
> > _______________________________________________
> > 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 exim@www1.ietf.org  Tue Oct 14 02:50:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28008
	for <pana-archive@odin.ietf.org>; Tue, 14 Oct 2003 02:50:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9J0P-0001nr-IG
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 02:50:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9E6o5A1006930
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 02:50:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9J0P-0001nh-0p
	for pana-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 02:50:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27987
	for <pana-web-archive@ietf.org>; Tue, 14 Oct 2003 02:49:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9J0L-0006d2-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 02:50:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9J0K-0006cz-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 02:50:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9J0L-0001n2-LJ; Tue, 14 Oct 2003 02:50:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9IzT-0001lv-SL
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 02:49:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27974
	for <pana@ietf.org>; Tue, 14 Oct 2003 02:48:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9IzP-0006cd-00
	for pana@ietf.org; Tue, 14 Oct 2003 02:49:04 -0400
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9IzP-0006ca-00
	for pana@ietf.org; Tue, 14 Oct 2003 02:49:03 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by david.siemens.de (8.11.7/8.11.7) with ESMTP id h9E6n1k05201;
	Tue, 14 Oct 2003 08:49:02 +0200 (MEST)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h9E6n1x23671;
	Tue, 14 Oct 2003 08:49:01 +0200 (MEST)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19)
	id <4DN1PW1H>; Tue, 14 Oct 2003 08:48:53 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC02AC@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>, pana@ietf.org
Subject: RE: [Pana] comments to pana-ipsec
Date: Tue, 14 Oct 2003 08:48:50 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi mohan, 

thanks for pointing to work done at the 3gpp2. unfortunately i am only
familiar with 3gpp work where no such mechanisms are used. could you provide
a pointer to the document?

ciao
hannes


> -----Original Message-----
> From: Mohan Parthasarathy [mailto:mohanp@sbcglobal.net]
> Sent: Monday, October 13, 2003 8:56 PM
> To: Tschofenig Hannes; pana@ietf.org
> Subject: Re: [Pana] comments to pana-ipsec
> 
> 
> 
> > hi mohan,
> > hi all,
> >
> > working on a pana implementation (including packet filter 
> creation and
> ipsec
> > sa establishment) we had to notice that there is a problem 
> getting pana
> and
> > ike to interact.
> >
> > after pana authentication and key exchange is finished some 
> parameters
> (such
> > as keys and ip address info) have to be provided to ike. using the
> freeswan
> > (pluto) and freebsd (racoon) ike implementations we noticed 
> that these
> > parameter cannot be added dynamically. these implemenations require
> changes
> > to plaintext files and some other configuration steps which 
> makes the
> > interworking difficult (without speaking about the 
> performance impact).
> >
> > is someone aware of an ike implementation which allows ike to be
> configured
> > dynamically (possible via an api)?
> >
> I don't know of an implementation. Others might know. But this is not
> totally new.
> In 3GPP2, IKE implementations had to provide an API where the 
> pre-shared key
> was derived outside of IKE  configuration. If i remember 
> correctly it was
> more like
> an opaque ID_KEY_ID that is given to IKE (derived using FA, 
> HA, etc.) for
> presenting in phase I by FA to HA. Perhaps the standard ones 
> don't have it
> and
> one had to implement it.
> 
> -mohan
> 
> > ciao
> > hannes
> >
> > _______________________________________________
> > 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-admin@ietf.org  Tue Oct 14 04:11:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29603
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 04:11:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9KGj-0006YQ-OB; Tue, 14 Oct 2003 04:11:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9KFq-0006Qu-U1
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 04:10:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29580
	for <pana@ietf.org>; Tue, 14 Oct 2003 04:09:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9KFo-00078T-00
	for pana@ietf.org; Tue, 14 Oct 2003 04:10:04 -0400
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9KFn-00078Q-00
	for pana@ietf.org; Tue, 14 Oct 2003 04:10:03 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h9E8A2709837;
	Tue, 14 Oct 2003 10:10:02 +0200 (MEST)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h9E8A0x16296;
	Tue, 14 Oct 2003 10:10:00 +0200 (MEST)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19)
	id <4DN1PXZS>; Tue, 14 Oct 2003 10:09:52 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC02B5@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Dan.Forsberg@nokia.com'" <Dan.Forsberg@nokia.com>, pana@ietf.org
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Tue, 14 Oct 2003 10:09:51 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi dan, 

there are several issues there: 

first, i like the idea of keeping the number of roundtrips at a minimum. i
think that it would be possible to have an option for submitting the
EAP-Request/Identity message immediately with the PANA-Start-Request by the
PAA after receiving the PANA-PAA-Discover message. it could be left to the
paa to skip the denial of service protection and to immediately start with
eap authentication (similar to the optional dos protection in ikev2). 

note that the discovery mechanisms is optional and therefore the
PANA-Auth-Request / PANA-Auth-Answer must still be able to perform the eap
identity exchange. 

yet another issue is whether to reuse something inside the eap header (e.g.
some identifier) as a cookie. i am not sure about this approach. 

ciao
hannes


> -----Original Message-----
> From: Dan.Forsberg@nokia.com [mailto:Dan.Forsberg@nokia.com]
> Sent: Friday, October 10, 2003 2:53 PM
> To: pana@ietf.org
> Subject: [Pana] EAP-Request/Identity & PANA-Start-Request
> 
> 
> PANA folks,
> 
> We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> Then we have the first PANA-Auth-Request/Answer message pair 
> carrying EAP-Request/Identity and EAP-Response/Identity. The 
> EAP-Request/Identity is generated in the PAA/NAS, because/which 
> at that point doesn't know the realm for the user. EAP header 
> also contains the identifier field which is somewhat analoguous 
> to PANA cookie. Why not to put the first EAP payload AVP into 
> the PANA-Start-Request message? This doesn't bring any new 
> requirements for the PAA to create state information, because 
> the EAP header identifier field can act similarly to PANA cookie 
> AVP... or in the extreme we could drop the cookie AVP and use 
> the EAP identifier field as the "cookie".
> 
> Let me hear your comments.
> 
> Br,
> - Dan
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Tue Oct 14 04:11:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29618
	for <pana-archive@odin.ietf.org>; Tue, 14 Oct 2003 04:11:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9KGq-0006Z2-VR
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 04:11:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9E8B8Rg025231
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 04:11:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9KGp-0006Ys-KW
	for pana-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 04:11:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29592
	for <pana-web-archive@ietf.org>; Tue, 14 Oct 2003 04:10:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9KGm-00078e-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 04:11:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9KGm-00078b-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 04:11:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9KGj-0006YQ-OB; Tue, 14 Oct 2003 04:11:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9KFq-0006Qu-U1
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 04:10:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29580
	for <pana@ietf.org>; Tue, 14 Oct 2003 04:09:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9KFo-00078T-00
	for pana@ietf.org; Tue, 14 Oct 2003 04:10:04 -0400
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9KFn-00078Q-00
	for pana@ietf.org; Tue, 14 Oct 2003 04:10:03 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h9E8A2709837;
	Tue, 14 Oct 2003 10:10:02 +0200 (MEST)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h9E8A0x16296;
	Tue, 14 Oct 2003 10:10:00 +0200 (MEST)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19)
	id <4DN1PXZS>; Tue, 14 Oct 2003 10:09:52 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC02B5@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Dan.Forsberg@nokia.com'" <Dan.Forsberg@nokia.com>, pana@ietf.org
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Tue, 14 Oct 2003 10:09:51 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi dan, 

there are several issues there: 

first, i like the idea of keeping the number of roundtrips at a minimum. i
think that it would be possible to have an option for submitting the
EAP-Request/Identity message immediately with the PANA-Start-Request by the
PAA after receiving the PANA-PAA-Discover message. it could be left to the
paa to skip the denial of service protection and to immediately start with
eap authentication (similar to the optional dos protection in ikev2). 

note that the discovery mechanisms is optional and therefore the
PANA-Auth-Request / PANA-Auth-Answer must still be able to perform the eap
identity exchange. 

yet another issue is whether to reuse something inside the eap header (e.g.
some identifier) as a cookie. i am not sure about this approach. 

ciao
hannes


> -----Original Message-----
> From: Dan.Forsberg@nokia.com [mailto:Dan.Forsberg@nokia.com]
> Sent: Friday, October 10, 2003 2:53 PM
> To: pana@ietf.org
> Subject: [Pana] EAP-Request/Identity & PANA-Start-Request
> 
> 
> PANA folks,
> 
> We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> Then we have the first PANA-Auth-Request/Answer message pair 
> carrying EAP-Request/Identity and EAP-Response/Identity. The 
> EAP-Request/Identity is generated in the PAA/NAS, because/which 
> at that point doesn't know the realm for the user. EAP header 
> also contains the identifier field which is somewhat analoguous 
> to PANA cookie. Why not to put the first EAP payload AVP into 
> the PANA-Start-Request message? This doesn't bring any new 
> requirements for the PAA to create state information, because 
> the EAP header identifier field can act similarly to PANA cookie 
> AVP... or in the extreme we could drop the cookie AVP and use 
> the EAP identifier field as the "cookie".
> 
> Let me hear your comments.
> 
> Br,
> - Dan
> 
> _______________________________________________
> 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-admin@ietf.org  Tue Oct 14 07:02:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03536
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 07:02:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9MwD-0005Wv-PA; Tue, 14 Oct 2003 07:02:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9MvM-0005WD-S5
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 07:01:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03482
	for <pana@ietf.org>; Tue, 14 Oct 2003 07:00:57 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9MvI-0000mV-00
	for pana@ietf.org; Tue, 14 Oct 2003 07:01:04 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9MvH-0000mS-00
	for pana@ietf.org; Tue, 14 Oct 2003 07:01:03 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9EB13v08514
	for <pana@ietf.org>; Tue, 14 Oct 2003 14:01:03 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65474f1b26ac158f24077@esvir04nok.ntc.nokia.com>;
 Tue, 14 Oct 2003 14:01:03 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 14 Oct 2003 14:01:02 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Tue, 14 Oct 2003 14:01:02 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5A8@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] EAP-Request/Identity & PANA-Start-Request
Thread-Index: AcORpunOYv9fIPHvRLOHJnAKThi98gAlW7CA
To: <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 14 Oct 2003 11:01:02.0770 (UTC) FILETIME=[752A2920:01C39242]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 13 October, 2003 19:25
> To: Forsberg Dan (NRC/Helsinki)
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
>
>
> Hi Dan,
>
> On Mon, Oct 13, 2003 at 02:58:50PM +0300,
> Dan.Forsberg@nokia.com wrote:
> > Hi Yoshihiro,
> >
> > Your arguments are not exactly valid.
> >
> > We could also say that PaC sends always EAP-Payload AVP
> > that contains EAP-Response/Identity in the PANA-Start-Answer
> > message. I.e. no EAP-Request is necessarily needed from PAA.
>
> EAP does not allow EAP peers to unsolicitedly send EAP-Response.

That is not a problem. The lower layer can generate an EAP-Request. 
Or the PAA can send it.

> >
> > PAA can itself create the EAP-Request thus the authenticator
> > is not involved.
>
> The current EAP authenticator state machine on the NAS does not allow
> lower-layer entity (e.g., PAA) to create an EAP Request on behalf of
> the authenticator.

That's fine, but what if the authenticator is on the AAA backend 
and NAS acts only as a pass-through.

I'm not coming up this by myself. See dratf-ietf-aaa-eap-02.txt 
section 2.2., the "preferred way" (second figure).

Another alternative is that the client sends User-Name or User-Realm 
AVP in PANA-Start-Answer from PaC to PAA. But I think that this 
"preferred way" is good to have. 

Do you see any problems in this? If there are, we have to notify the 
draft-ietf-aaa-eap-02.txt authors too.

- Dan

> >
> > Otherwise PaC needs to send it's identity to the PAA out
> > of the EAP so that PAA/NAS can contact the right authenticator.
>
> In some EAP environment where MAC address is used as a client
> identifier, the identifier can be effectively obtained from the MAC
> header that carries PANA message without using EAP-Identity exchange.
>
> >
> > - Dan
>
> Yoshihiro Ohba
>
> >
> > > -----Original Message-----
> > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: 10 October, 2003 18:35
> > > To: Forsberg Dan (NRC/Helsinki)
> > > Cc: pana@ietf.org
> > > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> > >
> > >
> > > On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> > > Dan.Forsberg@nokia.com wrote:
> > > > PANA folks,
> > > >
> > > > We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> > > > Then we have the first PANA-Auth-Request/Answer message pair
> > > > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > > > EAP-Request/Identity is generated in the PAA/NAS, because/which
> > > > at that point doesn't know the realm for the user. EAP header
> > > > also contains the identifier field which is somewhat analoguous
> > > > to PANA cookie. Why not to put the first EAP payload AVP into
> > > > the PANA-Start-Request message? This doesn't bring any new
> > > > requirements for the PAA to create state information, because
> > > > the EAP header identifier field can act similarly to PANA cookie
> > > > AVP... or in the extreme we could drop the cookie AVP and use
> > > > the EAP identifier field as the "cookie".
> > >
> > > There are two things we need to consider here:
> > >
> > > o The first EAP Request sent by the EAP authenticator is
> not always
> > >   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> > > is optional when
> > >   the client identity can be obtained by some other means.
> > >
> > > o EAP state machine
> (draft-ietf-eap-statemachines-00.{txt,ps}) does
> > >   not allow an EAP authenticator to be stateless when sending
> > > the first EAP Request.
> > >
> > > So in general PAA cannot be stateless when sending a
> > > PANA-Start-Request
> > > with piggybacking an EAP Request.
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > >
> > > >
> > > > Let me hear your comments.
> > > >
> > > > Br,
> > > > - Dan
> > > >
> > > > _______________________________________________
> > > > 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 exim@www1.ietf.org  Tue Oct 14 07:02:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03551
	for <pana-archive@odin.ietf.org>; Tue, 14 Oct 2003 07:02:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9MwM-0005Xj-Oj
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 07:02:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9EB2A44021306
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 07:02:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9MwM-0005XZ-Fm
	for pana-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 07:02:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03524
	for <pana-web-archive@ietf.org>; Tue, 14 Oct 2003 07:01:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9MwI-0000nR-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 07:02:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9MwH-0000nO-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 07:02:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9MwD-0005Wv-PA; Tue, 14 Oct 2003 07:02:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9MvM-0005WD-S5
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 07:01:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03482
	for <pana@ietf.org>; Tue, 14 Oct 2003 07:00:57 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9MvI-0000mV-00
	for pana@ietf.org; Tue, 14 Oct 2003 07:01:04 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9MvH-0000mS-00
	for pana@ietf.org; Tue, 14 Oct 2003 07:01:03 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9EB13v08514
	for <pana@ietf.org>; Tue, 14 Oct 2003 14:01:03 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T65474f1b26ac158f24077@esvir04nok.ntc.nokia.com>;
 Tue, 14 Oct 2003 14:01:03 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 14 Oct 2003 14:01:02 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Tue, 14 Oct 2003 14:01:02 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5A8@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] EAP-Request/Identity & PANA-Start-Request
Thread-Index: AcORpunOYv9fIPHvRLOHJnAKThi98gAlW7CA
To: <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 14 Oct 2003 11:01:02.0770 (UTC) FILETIME=[752A2920:01C39242]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 13 October, 2003 19:25
> To: Forsberg Dan (NRC/Helsinki)
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
>
>
> Hi Dan,
>
> On Mon, Oct 13, 2003 at 02:58:50PM +0300,
> Dan.Forsberg@nokia.com wrote:
> > Hi Yoshihiro,
> >
> > Your arguments are not exactly valid.
> >
> > We could also say that PaC sends always EAP-Payload AVP
> > that contains EAP-Response/Identity in the PANA-Start-Answer
> > message. I.e. no EAP-Request is necessarily needed from PAA.
>
> EAP does not allow EAP peers to unsolicitedly send EAP-Response.

That is not a problem. The lower layer can generate an EAP-Request. 
Or the PAA can send it.

> >
> > PAA can itself create the EAP-Request thus the authenticator
> > is not involved.
>
> The current EAP authenticator state machine on the NAS does not allow
> lower-layer entity (e.g., PAA) to create an EAP Request on behalf of
> the authenticator.

That's fine, but what if the authenticator is on the AAA backend 
and NAS acts only as a pass-through.

I'm not coming up this by myself. See dratf-ietf-aaa-eap-02.txt 
section 2.2., the "preferred way" (second figure).

Another alternative is that the client sends User-Name or User-Realm 
AVP in PANA-Start-Answer from PaC to PAA. But I think that this 
"preferred way" is good to have. 

Do you see any problems in this? If there are, we have to notify the 
draft-ietf-aaa-eap-02.txt authors too.

- Dan

> >
> > Otherwise PaC needs to send it's identity to the PAA out
> > of the EAP so that PAA/NAS can contact the right authenticator.
>
> In some EAP environment where MAC address is used as a client
> identifier, the identifier can be effectively obtained from the MAC
> header that carries PANA message without using EAP-Identity exchange.
>
> >
> > - Dan
>
> Yoshihiro Ohba
>
> >
> > > -----Original Message-----
> > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: 10 October, 2003 18:35
> > > To: Forsberg Dan (NRC/Helsinki)
> > > Cc: pana@ietf.org
> > > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> > >
> > >
> > > On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> > > Dan.Forsberg@nokia.com wrote:
> > > > PANA folks,
> > > >
> > > > We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> > > > Then we have the first PANA-Auth-Request/Answer message pair
> > > > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > > > EAP-Request/Identity is generated in the PAA/NAS, because/which
> > > > at that point doesn't know the realm for the user. EAP header
> > > > also contains the identifier field which is somewhat analoguous
> > > > to PANA cookie. Why not to put the first EAP payload AVP into
> > > > the PANA-Start-Request message? This doesn't bring any new
> > > > requirements for the PAA to create state information, because
> > > > the EAP header identifier field can act similarly to PANA cookie
> > > > AVP... or in the extreme we could drop the cookie AVP and use
> > > > the EAP identifier field as the "cookie".
> > >
> > > There are two things we need to consider here:
> > >
> > > o The first EAP Request sent by the EAP authenticator is
> not always
> > >   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> > > is optional when
> > >   the client identity can be obtained by some other means.
> > >
> > > o EAP state machine
> (draft-ietf-eap-statemachines-00.{txt,ps}) does
> > >   not allow an EAP authenticator to be stateless when sending
> > > the first EAP Request.
> > >
> > > So in general PAA cannot be stateless when sending a
> > > PANA-Start-Request
> > > with piggybacking an EAP Request.
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > >
> > > >
> > > > Let me hear your comments.
> > > >
> > > > Br,
> > > > - Dan
> > > >
> > > > _______________________________________________
> > > > 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-admin@ietf.org  Tue Oct 14 07:24:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04129
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 07:24:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9NHV-0006Yj-99; Tue, 14 Oct 2003 07:24:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9NHH-0006YW-2u
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 07:23:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04101
	for <pana@ietf.org>; Tue, 14 Oct 2003 07:23:38 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9NHG-0000xY-00
	for pana@ietf.org; Tue, 14 Oct 2003 07:23:46 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9NHF-0000xV-00
	for pana@ietf.org; Tue, 14 Oct 2003 07:23:45 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9EBNNZ07427
	for <pana@ietf.org>; Tue, 14 Oct 2003 14:23:28 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6547638150ac158f258e0@esvir05nok.ntc.nokia.com>;
 Tue, 14 Oct 2003 14:23:20 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 14 Oct 2003 14:23:20 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] issue 23 and 25
Date: Tue, 14 Oct 2003 14:23:19 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5A9@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] issue 23 and 25
Thread-Index: AcOR0SIhZG7jlshDT1K8ECM4+CtjEwActtEQ
To: <yohba@tari.toshiba.com>, <pana@ietf.org>
X-OriginalArrivalTime: 14 Oct 2003 11:23:20.0127 (UTC) FILETIME=[924AA4F0:01C39245]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 14 October, 2003 00:28
> To: pana@ietf.org
> Subject: [Pana] issue 23 and 25
>
>
> There are two PANA draft -01 issues for which I'm not sure about the
> consensus.
>
> Issue 23: PANA Message type/AVP numbers and Diameter command
> codes/AVPs

Let me give some background for this issue, since I submitted it.

One approach is that a NAS supports PANA functionality. A NAS 
can be a Diameter/Radius client. To better support interworking with the
PANA and NAS functionality, it would be good to distinguish the command
code and message type numbers. This way for example PANA message header 
parsing functionality can be added to a NAS almost as "link layer" and 
the PANA session handling functionality can be "migrated" into the NAS.

> Issue 25: Service Profile names
>
> In addition, there is one remaining issue on Issue 19: whether
> Result Code "PANA_REALM_NOT_SERVED" should be supported or not.

This has been discussed on another thread.

- Dan

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

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


From exim@www1.ietf.org  Tue Oct 14 07:24:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04144
	for <pana-archive@odin.ietf.org>; Tue, 14 Oct 2003 07:24:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9NHa-0006c9-Rk
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 07:24:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9EBO6hS025424
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 07:24:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9NHa-0006bz-Mx
	for pana-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 07:24:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04119
	for <pana-web-archive@ietf.org>; Tue, 14 Oct 2003 07:23:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9NHa-0000xi-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 07:24:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9NHZ-0000xf-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 07:24:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9NHV-0006Yj-99; Tue, 14 Oct 2003 07:24:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9NHH-0006YW-2u
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 07:23:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04101
	for <pana@ietf.org>; Tue, 14 Oct 2003 07:23:38 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9NHG-0000xY-00
	for pana@ietf.org; Tue, 14 Oct 2003 07:23:46 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9NHF-0000xV-00
	for pana@ietf.org; Tue, 14 Oct 2003 07:23:45 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9EBNNZ07427
	for <pana@ietf.org>; Tue, 14 Oct 2003 14:23:28 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6547638150ac158f258e0@esvir05nok.ntc.nokia.com>;
 Tue, 14 Oct 2003 14:23:20 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 14 Oct 2003 14:23:20 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] issue 23 and 25
Date: Tue, 14 Oct 2003 14:23:19 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5A9@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] issue 23 and 25
Thread-Index: AcOR0SIhZG7jlshDT1K8ECM4+CtjEwActtEQ
To: <yohba@tari.toshiba.com>, <pana@ietf.org>
X-OriginalArrivalTime: 14 Oct 2003 11:23:20.0127 (UTC) FILETIME=[924AA4F0:01C39245]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 14 October, 2003 00:28
> To: pana@ietf.org
> Subject: [Pana] issue 23 and 25
>
>
> There are two PANA draft -01 issues for which I'm not sure about the
> consensus.
>
> Issue 23: PANA Message type/AVP numbers and Diameter command
> codes/AVPs

Let me give some background for this issue, since I submitted it.

One approach is that a NAS supports PANA functionality. A NAS 
can be a Diameter/Radius client. To better support interworking with the
PANA and NAS functionality, it would be good to distinguish the command
code and message type numbers. This way for example PANA message header 
parsing functionality can be added to a NAS almost as "link layer" and 
the PANA session handling functionality can be "migrated" into the NAS.

> Issue 25: Service Profile names
>
> In addition, there is one remaining issue on Issue 19: whether
> Result Code "PANA_REALM_NOT_SERVED" should be supported or not.

This has been discussed on another thread.

- Dan

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

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



From pana-admin@ietf.org  Tue Oct 14 12:20:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17800
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 12:20:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9Rtx-0000Jx-8T; Tue, 14 Oct 2003 12:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9Rtq-0000JS-4s
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 12:19:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17775
	for <pana@ietf.org>; Tue, 14 Oct 2003 12:19:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Rto-0004wD-00
	for pana@ietf.org; Tue, 14 Oct 2003 12:19:52 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Rtn-0004w5-00
	for pana@ietf.org; Tue, 14 Oct 2003 12:19:52 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9EGJiF1025236;
	Wed, 15 Oct 2003 01:19:44 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9EGJimI027336;
	Wed, 15 Oct 2003 01:19:44 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA27334 ; Wed, 15 Oct 2003 01:19:44 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA27385; Wed, 15 Oct 2003 01:19:43 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA21847; Wed, 15 Oct 2003 01:19:43 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9EGJgsX008158;
	Wed, 15 Oct 2003 01:19:42 +0900 (JST)
Received: from steelhead ([159.119.168.104]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMR00B8M9CSG7@tsbpo1.po.toshiba.co.jp>; Wed,
 15 Oct 2003 01:19:41 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9RsF-00013U-00; Tue, 14 Oct 2003 09:18:15 -0700
Date: Tue, 14 Oct 2003 09:18:14 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5A8@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031014161814.GA3695@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5A8@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Dan,

On Tue, Oct 14, 2003 at 02:01:02PM +0300, Dan.Forsberg@nokia.com wrote:
> > >
> > > PAA can itself create the EAP-Request thus the authenticator
> > > is not involved.
> >
> > The current EAP authenticator state machine on the NAS does not allow
> > lower-layer entity (e.g., PAA) to create an EAP Request on behalf of
> > the authenticator.
> 
> That's fine, but what if the authenticator is on the AAA backend 
> and NAS acts only as a pass-through.
> 
> I'm not coming up this by myself. See dratf-ietf-aaa-eap-02.txt 
> section 2.2., the "preferred way" (second figure).

The passthrough authenticator behavior described in
dratf-ietf-aaa-eap-02.txt is explicitly supported in the EAP state
machines draft (draft-ietf-eap-statemachines-00.txt), but when this
happens, the initial EAP Request/Identity is always generated *at EAP
layer*, not at PANA layer. So the proposed approach will not work for
an implementation that is based on draft-ietf-eap-statemachines-00.txt.

> 
> Another alternative is that the client sends User-Name or User-Realm 
> AVP in PANA-Start-Answer from PaC to PAA. But I think that this 
> "preferred way" is good to have. 

I think the "preferred way" is automatically supported in the currrent
combination of PANA and EAP, i.e., the passthrough EAP authenticator
(that is co-located with PAA) generates the initial EAP
Request/Identity and passes it PAA, which then puts the message in a
PANA message and forwards it to the PaC.  

The issue we are discussing is: which PANA message should carry the
initial EAP Request/Identity and here is my suggestion:  

  "When a Cookie-AVP is carried in a PANA-Start-Request message, the
  initial EAP Request MUST NOT be carried in the PANA-Start-Request
  message in order for the PAA to be stateful.

  When a Cookie-AVP is not carried in a PANA-Start-Request message,
  the PAA does not need to be stateful.  In this case, the initial EAP
  Request message MAY be carried in the PANA-Start-Request message.
  If the initial EAP Request message is carried in the
  PANA-Start-Request message, an EAP Response message MUST be carried
  in the PANA-Start-Answer message returned to the PAA.
  
  In any case, PANA MUST NOT generate an EAP message on behalf of
  EAP peer or EAP authenticator."

I think this allows saving one round trip when PAA does not need to be
stateless.

What do you think?

Yoshihiro Ohba

> 
> Do you see any problems in this? If there are, we have to notify the 
> draft-ietf-aaa-eap-02.txt authors too.
> 
> - Dan
> 
> > >
> > > Otherwise PaC needs to send it's identity to the PAA out
> > > of the EAP so that PAA/NAS can contact the right authenticator.
> >
> > In some EAP environment where MAC address is used as a client
> > identifier, the identifier can be effectively obtained from the MAC
> > header that carries PANA message without using EAP-Identity exchange.
> >
> > >
> > > - Dan
> >
> > Yoshihiro Ohba
> >
> > >
> > > > -----Original Message-----
> > > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: 10 October, 2003 18:35
> > > > To: Forsberg Dan (NRC/Helsinki)
> > > > Cc: pana@ietf.org
> > > > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> > > >
> > > >
> > > > On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> > > > Dan.Forsberg@nokia.com wrote:
> > > > > PANA folks,
> > > > >
> > > > > We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> > > > > Then we have the first PANA-Auth-Request/Answer message pair
> > > > > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > > > > EAP-Request/Identity is generated in the PAA/NAS, because/which
> > > > > at that point doesn't know the realm for the user. EAP header
> > > > > also contains the identifier field which is somewhat analoguous
> > > > > to PANA cookie. Why not to put the first EAP payload AVP into
> > > > > the PANA-Start-Request message? This doesn't bring any new
> > > > > requirements for the PAA to create state information, because
> > > > > the EAP header identifier field can act similarly to PANA cookie
> > > > > AVP... or in the extreme we could drop the cookie AVP and use
> > > > > the EAP identifier field as the "cookie".
> > > >
> > > > There are two things we need to consider here:
> > > >
> > > > o The first EAP Request sent by the EAP authenticator is
> > not always
> > > >   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> > > > is optional when
> > > >   the client identity can be obtained by some other means.
> > > >
> > > > o EAP state machine
> > (draft-ietf-eap-statemachines-00.{txt,ps}) does
> > > >   not allow an EAP authenticator to be stateless when sending
> > > > the first EAP Request.
> > > >
> > > > So in general PAA cannot be stateless when sending a
> > > > PANA-Start-Request
> > > > with piggybacking an EAP Request.
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > >
> > > > >
> > > > > Let me hear your comments.
> > > > >
> > > > > Br,
> > > > > - Dan
> > > > >
> > > > > _______________________________________________
> > > > > 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 exim@www1.ietf.org  Tue Oct 14 12:20:37 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17819
	for <pana-archive@odin.ietf.org>; Tue, 14 Oct 2003 12:20:37 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9RuB-0000M1-Hn
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 12:20:16 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9EGKEdU001353
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 12:20:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9Ru8-0000Lk-2s
	for pana-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 12:20:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17786
	for <pana-web-archive@ietf.org>; Tue, 14 Oct 2003 12:20:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Ru6-0004wW-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 12:20:10 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Ru6-0004wR-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 12:20:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9Rtx-0000Jx-8T; Tue, 14 Oct 2003 12:20:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9Rtq-0000JS-4s
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 12:19:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17775
	for <pana@ietf.org>; Tue, 14 Oct 2003 12:19:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Rto-0004wD-00
	for pana@ietf.org; Tue, 14 Oct 2003 12:19:52 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Rtn-0004w5-00
	for pana@ietf.org; Tue, 14 Oct 2003 12:19:52 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9EGJiF1025236;
	Wed, 15 Oct 2003 01:19:44 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9EGJimI027336;
	Wed, 15 Oct 2003 01:19:44 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA27334 ; Wed, 15 Oct 2003 01:19:44 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA27385; Wed, 15 Oct 2003 01:19:43 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA21847; Wed, 15 Oct 2003 01:19:43 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9EGJgsX008158;
	Wed, 15 Oct 2003 01:19:42 +0900 (JST)
Received: from steelhead ([159.119.168.104]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMR00B8M9CSG7@tsbpo1.po.toshiba.co.jp>; Wed,
 15 Oct 2003 01:19:41 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9RsF-00013U-00; Tue, 14 Oct 2003 09:18:15 -0700
Date: Tue, 14 Oct 2003 09:18:14 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5A8@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031014161814.GA3695@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5A8@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Dan,

On Tue, Oct 14, 2003 at 02:01:02PM +0300, Dan.Forsberg@nokia.com wrote:
> > >
> > > PAA can itself create the EAP-Request thus the authenticator
> > > is not involved.
> >
> > The current EAP authenticator state machine on the NAS does not allow
> > lower-layer entity (e.g., PAA) to create an EAP Request on behalf of
> > the authenticator.
> 
> That's fine, but what if the authenticator is on the AAA backend 
> and NAS acts only as a pass-through.
> 
> I'm not coming up this by myself. See dratf-ietf-aaa-eap-02.txt 
> section 2.2., the "preferred way" (second figure).

The passthrough authenticator behavior described in
dratf-ietf-aaa-eap-02.txt is explicitly supported in the EAP state
machines draft (draft-ietf-eap-statemachines-00.txt), but when this
happens, the initial EAP Request/Identity is always generated *at EAP
layer*, not at PANA layer. So the proposed approach will not work for
an implementation that is based on draft-ietf-eap-statemachines-00.txt.

> 
> Another alternative is that the client sends User-Name or User-Realm 
> AVP in PANA-Start-Answer from PaC to PAA. But I think that this 
> "preferred way" is good to have. 

I think the "preferred way" is automatically supported in the currrent
combination of PANA and EAP, i.e., the passthrough EAP authenticator
(that is co-located with PAA) generates the initial EAP
Request/Identity and passes it PAA, which then puts the message in a
PANA message and forwards it to the PaC.  

The issue we are discussing is: which PANA message should carry the
initial EAP Request/Identity and here is my suggestion:  

  "When a Cookie-AVP is carried in a PANA-Start-Request message, the
  initial EAP Request MUST NOT be carried in the PANA-Start-Request
  message in order for the PAA to be stateful.

  When a Cookie-AVP is not carried in a PANA-Start-Request message,
  the PAA does not need to be stateful.  In this case, the initial EAP
  Request message MAY be carried in the PANA-Start-Request message.
  If the initial EAP Request message is carried in the
  PANA-Start-Request message, an EAP Response message MUST be carried
  in the PANA-Start-Answer message returned to the PAA.
  
  In any case, PANA MUST NOT generate an EAP message on behalf of
  EAP peer or EAP authenticator."

I think this allows saving one round trip when PAA does not need to be
stateless.

What do you think?

Yoshihiro Ohba

> 
> Do you see any problems in this? If there are, we have to notify the 
> draft-ietf-aaa-eap-02.txt authors too.
> 
> - Dan
> 
> > >
> > > Otherwise PaC needs to send it's identity to the PAA out
> > > of the EAP so that PAA/NAS can contact the right authenticator.
> >
> > In some EAP environment where MAC address is used as a client
> > identifier, the identifier can be effectively obtained from the MAC
> > header that carries PANA message without using EAP-Identity exchange.
> >
> > >
> > > - Dan
> >
> > Yoshihiro Ohba
> >
> > >
> > > > -----Original Message-----
> > > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: 10 October, 2003 18:35
> > > > To: Forsberg Dan (NRC/Helsinki)
> > > > Cc: pana@ietf.org
> > > > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> > > >
> > > >
> > > > On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> > > > Dan.Forsberg@nokia.com wrote:
> > > > > PANA folks,
> > > > >
> > > > > We have PANA-Start-Request/Answer messgae pair carrying Cookie.
> > > > > Then we have the first PANA-Auth-Request/Answer message pair
> > > > > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > > > > EAP-Request/Identity is generated in the PAA/NAS, because/which
> > > > > at that point doesn't know the realm for the user. EAP header
> > > > > also contains the identifier field which is somewhat analoguous
> > > > > to PANA cookie. Why not to put the first EAP payload AVP into
> > > > > the PANA-Start-Request message? This doesn't bring any new
> > > > > requirements for the PAA to create state information, because
> > > > > the EAP header identifier field can act similarly to PANA cookie
> > > > > AVP... or in the extreme we could drop the cookie AVP and use
> > > > > the EAP identifier field as the "cookie".
> > > >
> > > > There are two things we need to consider here:
> > > >
> > > > o The first EAP Request sent by the EAP authenticator is
> > not always
> > > >   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> > > > is optional when
> > > >   the client identity can be obtained by some other means.
> > > >
> > > > o EAP state machine
> > (draft-ietf-eap-statemachines-00.{txt,ps}) does
> > > >   not allow an EAP authenticator to be stateless when sending
> > > > the first EAP Request.
> > > >
> > > > So in general PAA cannot be stateless when sending a
> > > > PANA-Start-Request
> > > > with piggybacking an EAP Request.
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > >
> > > > >
> > > > > Let me hear your comments.
> > > > >
> > > > > Br,
> > > > > - Dan
> > > > >
> > > > > _______________________________________________
> > > > > 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-request@research.telcordia.com  Tue Oct 14 13:15:55 2003
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19672
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 13:15:43 -0400 (EDT)
Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8])
	by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id h9EHAAes014662;
	Tue, 14 Oct 2003 13:10:10 -0400 (EDT)
Received: (from slmgr@localhost)
	by donner.research.telcordia.com (8.8.8/8.8.8) id NAA12643;
	Tue, 14 Oct 2003 13:10:10 -0400 (EDT)
Resent-Date: Tue, 14 Oct 2003 13:10:10 -0400 (EDT)
X-Authentication-Warning: donner.research.telcordia.com: slmgr set sender to pana-request@research.telcordia.com using -f
Old-Return-Path: <yohba@tari.toshiba.com>
Date: Tue, 14 Oct 2003 10:08:34 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: New [issue25] Service Profile names
In-reply-to: <BBB0E153.A5F6%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@research.telcordia.com
Message-id: <20031014170834.GB3695@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
 pana@research.telcordia.com
User-Agent: Mutt/1.5.4i
References: <20031009174816.GA8231@steelhead>
 <BBB0E153.A5F6%alper@docomolabs-usa.com>
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi)
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper)
Resent-Message-ID: <2ym_PD.A.aFD.x3Cj_@donner>
Resent-From: pana@research.telcordia.com
X-Mailing-List: <pana@research.telcordia.com> 
X-Loop: pana@research.telcordia.com
List-Post: <mailto:pana@research.telcordia.com>
List-Help: <mailto:pana-request@research.telcordia.com?subject=help>
Precedence: list
Resent-Sender: pana-request@research.telcordia.com

On Mon, Oct 13, 2003 at 11:10:11PM -0700, Alper Yegin wrote:
> 
> I agree with the earlier text proposed for handling service profile
> advertisements.
> 
> One question: does it make sense to allow PaC to optionally include an ISP
> or NAP identifier in the PANA-start-answer to identify the binding between
> the subsequent authentication and the service provider? This can be an
> optional feature. When not stated, the realm as suggested by the EAP
> identifier provides this information.

I was also thinking the same thing and I think it makes sense in terms
of providing more flexibile way of ISP selection so that a client that
uses can choose an ISP among multiple choices with using a single NAI.

I'll provide additional text on this.

> 
> > In the initial text I recently provided, one NAP-Information AVP and
> > zero or more ISP-Information AVPs can optionally be carried in
> > PANA-Start-Request, where each AVP includes a unique (IANA-assigned)
> > provider identifier and a provider name.
> > 
> > When there are multiple PAAs, this kind of information could
> > be used by PaC to choose a PAA.  So this issue might result in
> > re-consideration of the current PAA selection procedure:
> > 
> > "There can be multiple PAAs on the link. The result does not depend
> > on which PAA PaC chooses. By default PaC chooses the PAA that sent
> > the first response."
> 
> I'm still not convinced that an access network would have PAAs from
> different NAPs on the same link. Are we talking about multiple PAAs run by
> the same NAP but possibly handling AAA traffic for different ISPs? 

I was assuming that multiple PAAs run by the same NAP but possibly
handling AAA traffic for different ISPs, but I think it is also
possible to have different NAPs on the same link, as NAP and ISP are
basically logical separation and what is applicable to ISP is also
logically applicable NAP.  But I think PANA design should not have to
care about details on how the service profiles are used.

> Maybe
> this happens.... Nevertheless, I agree we can re-consider the above text. It
> is kind of limiting without justification...

My opinion is that flexible choice of PAA (and EP) is possible as long
as the choice is consistent with data packet routing.  

Yoshihiro Ohba



> 
> Alper
> 
> 
> > 
> > Note that section 4 of draft-yacine-pana-paa2ep-prot-eval-00.txt also
> > addresses a similer issue.
> > 
> > Yoshihiro Ohba
> > 
> > 
> > 
> > On Thu, Sep 25, 2003 at 10:50:16AM -0700, Alper Yegin wrote:
> >> 
> >> This piece of data sounds informative and potentially useful. I presume if
> >> we wanted to have this support, we'd define a new AVP that carries some sort
> >> of an "identifier" and optionally carried in PANA-Start-Request. Do we have
> >> to define the format of the data this AVP embeds? What type of information
> >> would the data be carrying?
> >> 
> >> 
> >> Alper
> >> 
> >> 
> >>> I think more about this issue and now I tend to agree that the
> >>> proposed functionality might be useful even if there is one PAA on an
> >>> IP link.  First, there may be multiple IP links available at a
> >>> physical location (e.g., a hotspot).  In such a case, if
> >>> PANA-Start-Request messages sent by PAAs contain some profile
> >>> information, a PaC can use the information to choose an appropriate IP
> >>> link to start authentication.  Second, even if there is only one IP
> >>> link in a physical location and one PAA on the link, a PaC can use the
> >>> information to determine whether it starts authentication on the IP
> >>> link or not.
> >>> 
> >>> Yoshihiro Ohba
> >>> 
> >>> 
> >>> 
> >>> On Wed, Sep 10, 2003 at 02:22:14PM +0300, Dan.Forsberg@nokia.com wrote:
> >>>> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> >>>> 
> >>>>> From Reinaldo Penno:
> >>>> <klip>
> >>>>> 3) In section 4.2, paragraph 3 it is mentioned that
> >>>>> "The result does not depend on which PAA PaC chooses.
> >>>>> By default PaC chooses the PAA that sent the first
> >>>>> reponse"
> >>>>> 
> >>>>> This is the DHCP approach. Where all servers are
> >>>>> equally good.
> >>>>> 
> >>>>> I would propose that we think about incorporating
> >>>>> something of the PPPoE protocol that is widespread,
> >>>>> since PANA is more related to the PPPoE model.
> >>>>> 
> >>>>> In the response of the Discovery message each PPPoE
> >>>>> server include all the Service Profile (names) it
> >>>>> supports (the definition is loose on purpose).
> >>>>> Nowadays it is usually a list of ISPs or bandwidth
> >>>>> packages a user can choose.
> >>>>> 
> >>>>> I would argue that in the case of PANA (and specially
> >>>>> in the case of NAP vs ISP authentication), PAA servers
> >>>>> might support a very different set of attributes and a
> >>>>> PaC might prefer one over the other if it new of each
> >>>>> choices.
> >>>>> 
> >>>>> We could have a AVP in PANA for that purpose in the
> >>>>> answer to the Discovery message. it seems very simple,
> >>>>> could be optional and will provide a crucial
> >>>>> functionality for people that use PPPoE to migrate to
> >>>>> PANA.
> >>>> 
> >>>> Yoshihiro Ohba:
> >>>> 
> >>>> When we dicussed NAP and ISP separate authentication, I think the
> >>>> assumption is that there is a single PAA the PaC sees, and the NAI is
> >>>> used to choose a particular ISP.  Why do you need multiple PAAs to
> >>>> support NAP and ISP separate authentication?
> >>>> 
> >>>> 
> >>>> ----------
> >>>> category: Technical
> >>>> document: draft-ietf-pana-pana-xx.txt
> >>>> messages: 80
> >>>> nosy: dforsber
> >>>> priority: May Fix
> >>>> status: Pending
> >>>> title: Service Profile names
> >>>> ________________________________________________
> >>>> PANA Issues <pana_issues@danforsberg.info>
> >>>> http://danforsberg.info:8080/pana-issues/issue25
> >>>> ________________________________________________
> >>>> 
> >>> 
> >>> 
> >> 
> > 
> 



From pana-admin@ietf.org  Tue Oct 14 14:05:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21683
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 14:05:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TXa-00066S-Q1; Tue, 14 Oct 2003 14:05:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TWn-0005va-5D
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 14:04:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21556
	for <pana@ietf.org>; Tue, 14 Oct 2003 14:04:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TWk-00060X-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:04:10 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TWj-00060U-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:04:10 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9EI44F1022512;
	Wed, 15 Oct 2003 03:04:04 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9EI440x005908;
	Wed, 15 Oct 2003 03:04:04 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA05904 ; Wed, 15 Oct 2003 03:04:04 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA24994; Wed, 15 Oct 2003 03:04:03 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA00663; Wed, 15 Oct 2003 03:04:03 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9EI42sX008170;
	Wed, 15 Oct 2003 03:04:02 +0900 (JST)
Received: from steelhead ([159.119.168.104]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMR00F5QE6ORH@tsbpo1.po.toshiba.co.jp>; Wed,
 15 Oct 2003 03:04:02 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9TVn-0001Ec-00; Tue, 14 Oct 2003 11:03:11 -0700
Date: Tue, 14 Oct 2003 11:03:11 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue19] Result-Code AVP values?
In-reply-to: <BBB0DD8B.A5ED%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Dan.Forsberg@nokia.com, pana@ietf.org
Message-id: <20031014180311.GD3695@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C594@esebe008.ntc.nokia.com>
 <BBB0DD8B.A5ED%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

There are already three authentication results defined, i.e.,
PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
PANA_REALM_NOT_SERVED seems to be a bit inconsistent in design with
those three fundamental results.

In addition, the EAP state machine draft does not have an interface to
AAA to obtain detailed error information like REALM_NOT_SERVED, and
thus in actual implementations it is likely that
PANA_AUTHENTICATION_REJECTED is used instead of PANA_REALM_NOT_SERVED.

So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.

Yoshihiro Ohba


On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
> > In PANA we retransmit requests because we want to have reliable
> > transport. So, the case where the authenticator retransmits the
> > EAP-Request/Identity is interpreted differently in PANA layer
> > (retransmissions for reliability).
> > 
> > The case of Notification Request is usable, but what does
> > "invalid authentication attempt" mean? Can we interpret it such
> > a way that it means "typo in the identity, user part" or "user
> > not recognized" or "realm not served"..
> 
> Good points, but that does not mean they are problems for PANA to solve.
> 
> Generally I'm concerned about leaking EAP-layer events or actions into PANA.
> But I think in this case, this is more of mapping an EAP lower-layer
> (Diameter) event to PANA. While I wouldn't simply import all such events
> from one to another, I think this one might be useful and not disruptive. On
> the other hand, this error message is different from all the others. Those
> are all PANA-specific.
> 
> Hmmm... Does anyone else care to comment on this?
> 
> Alper
> 
> 
> > 
> > A result code in PANA for this (borrowed from Diameter) is clear
> > and works if the authenticator implementation doesn't support
> > this MAY part of the EAP doc.
> > 
> > - Dan
> > 
> > 
> >> -----Original Message-----
> >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> >> Sent: 07 October, 2003 20:55
> >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> >> 
> >> 
> >>>> I think this is also an EAP question. What would be the EAP
> >>>> behavior when
> >>>> the NAS cannot recognize the EAP client identifier?
> >> 
> >> I think this case would be handled by the following text from
> >> the EAP spec:
> >> 
> >>          Implementation Note: The peer MAY obtain the
> >> Identity via user
> >>          input.  It is suggested that the authenticator retry the
> >>          Identity Request in the case of an invalid Identity or
> >>          authentication failure to allow for potential typos
> >> on the part
> >>          of the user.  It is suggested that the Identity Request be
> >>          retried a minimum of 3 times before terminating the
> >>          authentication.  The Notification Request MAY be used to
> >>          indicate an invalid authentication attempt prior to
> >>          transmitting a new Identity Request (optionally, the failure
> >>          MAY be indicated within the message of the new
> >> Identity Request
> >>          itself).
> >> 
> >> ... And finally I think the EAP authenticator would send a
> >> Failure message.
> >> 
> >> 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 exim@www1.ietf.org  Tue Oct 14 14:05:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21708
	for <pana-archive@odin.ietf.org>; Tue, 14 Oct 2003 14:05:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TXc-00067M-Mo
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 14:05:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9EI54eo023515
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 14:05:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TXc-00067C-Hy
	for pana-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 14:05:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21648
	for <pana-web-archive@ietf.org>; Tue, 14 Oct 2003 14:04:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TXa-00061S-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 14:05:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TXZ-00061P-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 14:05:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TXa-00066S-Q1; Tue, 14 Oct 2003 14:05:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TWn-0005va-5D
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 14:04:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21556
	for <pana@ietf.org>; Tue, 14 Oct 2003 14:04:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TWk-00060X-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:04:10 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TWj-00060U-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:04:10 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9EI44F1022512;
	Wed, 15 Oct 2003 03:04:04 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9EI440x005908;
	Wed, 15 Oct 2003 03:04:04 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA05904 ; Wed, 15 Oct 2003 03:04:04 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA24994; Wed, 15 Oct 2003 03:04:03 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA00663; Wed, 15 Oct 2003 03:04:03 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9EI42sX008170;
	Wed, 15 Oct 2003 03:04:02 +0900 (JST)
Received: from steelhead ([159.119.168.104]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMR00F5QE6ORH@tsbpo1.po.toshiba.co.jp>; Wed,
 15 Oct 2003 03:04:02 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9TVn-0001Ec-00; Tue, 14 Oct 2003 11:03:11 -0700
Date: Tue, 14 Oct 2003 11:03:11 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue19] Result-Code AVP values?
In-reply-to: <BBB0DD8B.A5ED%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Dan.Forsberg@nokia.com, pana@ietf.org
Message-id: <20031014180311.GD3695@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C594@esebe008.ntc.nokia.com>
 <BBB0DD8B.A5ED%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

There are already three authentication results defined, i.e.,
PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
PANA_REALM_NOT_SERVED seems to be a bit inconsistent in design with
those three fundamental results.

In addition, the EAP state machine draft does not have an interface to
AAA to obtain detailed error information like REALM_NOT_SERVED, and
thus in actual implementations it is likely that
PANA_AUTHENTICATION_REJECTED is used instead of PANA_REALM_NOT_SERVED.

So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.

Yoshihiro Ohba


On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
> > In PANA we retransmit requests because we want to have reliable
> > transport. So, the case where the authenticator retransmits the
> > EAP-Request/Identity is interpreted differently in PANA layer
> > (retransmissions for reliability).
> > 
> > The case of Notification Request is usable, but what does
> > "invalid authentication attempt" mean? Can we interpret it such
> > a way that it means "typo in the identity, user part" or "user
> > not recognized" or "realm not served"..
> 
> Good points, but that does not mean they are problems for PANA to solve.
> 
> Generally I'm concerned about leaking EAP-layer events or actions into PANA.
> But I think in this case, this is more of mapping an EAP lower-layer
> (Diameter) event to PANA. While I wouldn't simply import all such events
> from one to another, I think this one might be useful and not disruptive. On
> the other hand, this error message is different from all the others. Those
> are all PANA-specific.
> 
> Hmmm... Does anyone else care to comment on this?
> 
> Alper
> 
> 
> > 
> > A result code in PANA for this (borrowed from Diameter) is clear
> > and works if the authenticator implementation doesn't support
> > this MAY part of the EAP doc.
> > 
> > - Dan
> > 
> > 
> >> -----Original Message-----
> >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> >> Sent: 07 October, 2003 20:55
> >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> >> 
> >> 
> >>>> I think this is also an EAP question. What would be the EAP
> >>>> behavior when
> >>>> the NAS cannot recognize the EAP client identifier?
> >> 
> >> I think this case would be handled by the following text from
> >> the EAP spec:
> >> 
> >>          Implementation Note: The peer MAY obtain the
> >> Identity via user
> >>          input.  It is suggested that the authenticator retry the
> >>          Identity Request in the case of an invalid Identity or
> >>          authentication failure to allow for potential typos
> >> on the part
> >>          of the user.  It is suggested that the Identity Request be
> >>          retried a minimum of 3 times before terminating the
> >>          authentication.  The Notification Request MAY be used to
> >>          indicate an invalid authentication attempt prior to
> >>          transmitting a new Identity Request (optionally, the failure
> >>          MAY be indicated within the message of the new
> >> Identity Request
> >>          itself).
> >> 
> >> ... And finally I think the EAP authenticator would send a
> >> Failure message.
> >> 
> >> 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-admin@ietf.org  Tue Oct 14 14:12:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22286
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 14:12:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TeL-0007S8-6v; Tue, 14 Oct 2003 14:12:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TeI-0007Rr-08
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 14:11:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22253
	for <pana@ietf.org>; Tue, 14 Oct 2003 14:11:48 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TeF-0006AJ-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:11:55 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TeE-0006AG-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:11:54 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9EIBpd05673
	for <pana@ietf.org>; Tue, 14 Oct 2003 21:11:51 +0300 (EET DST)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6548d981e2ac158f25461@esvir05nok.ntc.nokia.com>;
 Tue, 14 Oct 2003 21:11:51 +0300
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 14 Oct 2003 13:11:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] [issue19] Result-Code AVP values?
Date: Tue, 14 Oct 2003 13:11:24 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB8BB@daebe007.americas.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOSffKf38BrNnNJRkCzbqnadEy6NQAAHKTA
To: <yohba@tari.toshiba.com>, <alper@docomolabs-usa.com>
Cc: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
X-OriginalArrivalTime: 14 Oct 2003 18:11:25.0018 (UTC) FILETIME=[946C83A0:01C3927E]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> There are already three authentication results defined, i.e.,
> PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
> PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
> PANA_REALM_NOT_SERVED seems to be a bit inconsistent in design with
> those three fundamental results.


I agree with Yoshi's comment about not adding a REALM_NOT_SERVED
error code. A simple reject is sufficient.

-Basavaraj

> 
> In addition, the EAP state machine draft does not have an interface to
> AAA to obtain detailed error information like REALM_NOT_SERVED, and
> thus in actual implementations it is likely that
> PANA_AUTHENTICATION_REJECTED is used instead of PANA_REALM_NOT_SERVED.
> 
> So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
> 
> Yoshihiro Ohba
> 

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


From exim@www1.ietf.org  Tue Oct 14 14:12:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22301
	for <pana-archive@odin.ietf.org>; Tue, 14 Oct 2003 14:12:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TeO-0007Un-Ib
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 14:12:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9EIC4ns028757
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 14:12:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TeO-0007Ta-B7
	for pana-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 14:12:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22262
	for <pana-web-archive@ietf.org>; Tue, 14 Oct 2003 14:11:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TeL-0006AV-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 14:12:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TeL-0006AS-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 14:12:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TeL-0007S8-6v; Tue, 14 Oct 2003 14:12:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TeI-0007Rr-08
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 14:11:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22253
	for <pana@ietf.org>; Tue, 14 Oct 2003 14:11:48 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TeF-0006AJ-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:11:55 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TeE-0006AG-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:11:54 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9EIBpd05673
	for <pana@ietf.org>; Tue, 14 Oct 2003 21:11:51 +0300 (EET DST)
Received: from daebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6548d981e2ac158f25461@esvir05nok.ntc.nokia.com>;
 Tue, 14 Oct 2003 21:11:51 +0300
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Tue, 14 Oct 2003 13:11:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] [issue19] Result-Code AVP values?
Date: Tue, 14 Oct 2003 13:11:24 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF44024DB8BB@daebe007.americas.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOSffKf38BrNnNJRkCzbqnadEy6NQAAHKTA
To: <yohba@tari.toshiba.com>, <alper@docomolabs-usa.com>
Cc: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
X-OriginalArrivalTime: 14 Oct 2003 18:11:25.0018 (UTC) FILETIME=[946C83A0:01C3927E]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> There are already three authentication results defined, i.e.,
> PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
> PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
> PANA_REALM_NOT_SERVED seems to be a bit inconsistent in design with
> those three fundamental results.


I agree with Yoshi's comment about not adding a REALM_NOT_SERVED
error code. A simple reject is sufficient.

-Basavaraj

> 
> In addition, the EAP state machine draft does not have an interface to
> AAA to obtain detailed error information like REALM_NOT_SERVED, and
> thus in actual implementations it is likely that
> PANA_AUTHENTICATION_REJECTED is used instead of PANA_REALM_NOT_SERVED.
> 
> So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
> 
> Yoshihiro Ohba
> 

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



From pana-admin@ietf.org  Tue Oct 14 14:18:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22500
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 14:18:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9Tk9-0007e4-FF; Tue, 14 Oct 2003 14:18:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9Tjz-0007ds-KG
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 14:17:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22474
	for <pana@ietf.org>; Tue, 14 Oct 2003 14:17:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Tjx-0006EZ-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:17:49 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Tjw-0006EW-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:17:48 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9EIHlF1025330;
	Wed, 15 Oct 2003 03:17:47 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9EIHlqR009652;
	Wed, 15 Oct 2003 03:17:47 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA09649 ; Wed, 15 Oct 2003 03:17:46 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA28049; Wed, 15 Oct 2003 03:17:46 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA19533; Wed, 15 Oct 2003 03:17:46 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9EIHjsX010201;
	Wed, 15 Oct 2003 03:17:45 +0900 (JST)
Received: from steelhead ([159.119.168.104]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMR00G4IETJVF@tsbpo1.po.toshiba.co.jp>; Wed,
 15 Oct 2003 03:17:44 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9Tjl-0001GR-00; Tue, 14 Oct 2003 11:17:37 -0700
Date: Tue, 14 Oct 2003 11:17:37 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue 23 and 25
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5A9@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031014181737.GE3695@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5A9@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Tue, Oct 14, 2003 at 02:23:19PM +0300, Dan.Forsberg@nokia.com wrote:
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 14 October, 2003 00:28
> > To: pana@ietf.org
> > Subject: [Pana] issue 23 and 25
> >
> >
> > There are two PANA draft -01 issues for which I'm not sure about the
> > consensus.
> >
> > Issue 23: PANA Message type/AVP numbers and Diameter command
> > codes/AVPs
> 
> Let me give some background for this issue, since I submitted it.
> 
> One approach is that a NAS supports PANA functionality. A NAS 
> can be a Diameter/Radius client. To better support interworking with the
> PANA and NAS functionality, it would be good to distinguish the command
> code and message type numbers. This way for example PANA message header 
> parsing functionality can be added to a NAS almost as "link layer" and 
> the PANA session handling functionality can be "migrated" into the NAS.

This seems to suggest using different code space for Diameter command
codes and PANA message types, right?  What about using different code
space for Diameter AVP types and PANA AVP types?  I think the same
justification is also applicable to PANA AVP types.

Yoshihiro Ohba

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


From exim@www1.ietf.org  Tue Oct 14 14:18:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22515
	for <pana-archive@odin.ietf.org>; Tue, 14 Oct 2003 14:18:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TkC-0007em-MH
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 14:18:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9EII4Sp029426
	for pana-archive@odin.ietf.org; Tue, 14 Oct 2003 14:18:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9TkC-0007eX-Hr
	for pana-web-archive@optimus.ietf.org; Tue, 14 Oct 2003 14:18:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22483
	for <pana-web-archive@ietf.org>; Tue, 14 Oct 2003 14:17:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9TkA-0006El-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 14:18:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Tk9-0006Ei-00
	for pana-web-archive@ietf.org; Tue, 14 Oct 2003 14:18:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9Tk9-0007e4-FF; Tue, 14 Oct 2003 14:18:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9Tjz-0007ds-KG
	for pana@optimus.ietf.org; Tue, 14 Oct 2003 14:17:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22474
	for <pana@ietf.org>; Tue, 14 Oct 2003 14:17:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Tjx-0006EZ-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:17:49 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9Tjw-0006EW-00
	for pana@ietf.org; Tue, 14 Oct 2003 14:17:48 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9EIHlF1025330;
	Wed, 15 Oct 2003 03:17:47 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9EIHlqR009652;
	Wed, 15 Oct 2003 03:17:47 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA09649 ; Wed, 15 Oct 2003 03:17:46 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA28049; Wed, 15 Oct 2003 03:17:46 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA19533; Wed, 15 Oct 2003 03:17:46 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9EIHjsX010201;
	Wed, 15 Oct 2003 03:17:45 +0900 (JST)
Received: from steelhead ([159.119.168.104]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMR00G4IETJVF@tsbpo1.po.toshiba.co.jp>; Wed,
 15 Oct 2003 03:17:44 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9Tjl-0001GR-00; Tue, 14 Oct 2003 11:17:37 -0700
Date: Tue, 14 Oct 2003 11:17:37 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue 23 and 25
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5A9@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031014181737.GE3695@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5A9@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Tue, Oct 14, 2003 at 02:23:19PM +0300, Dan.Forsberg@nokia.com wrote:
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 14 October, 2003 00:28
> > To: pana@ietf.org
> > Subject: [Pana] issue 23 and 25
> >
> >
> > There are two PANA draft -01 issues for which I'm not sure about the
> > consensus.
> >
> > Issue 23: PANA Message type/AVP numbers and Diameter command
> > codes/AVPs
> 
> Let me give some background for this issue, since I submitted it.
> 
> One approach is that a NAS supports PANA functionality. A NAS 
> can be a Diameter/Radius client. To better support interworking with the
> PANA and NAS functionality, it would be good to distinguish the command
> code and message type numbers. This way for example PANA message header 
> parsing functionality can be added to a NAS almost as "link layer" and 
> the PANA session handling functionality can be "migrated" into the NAS.

This seems to suggest using different code space for Diameter command
codes and PANA message types, right?  What about using different code
space for Diameter AVP types and PANA AVP types?  I think the same
justification is also applicable to PANA AVP types.

Yoshihiro Ohba

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



From pana-request@research.telcordia.com  Tue Oct 14 15:05:47 2003
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24299
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 15:05:47 -0400 (EDT)
Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8])
	by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id h9EJ13es019564;
	Tue, 14 Oct 2003 15:01:03 -0400 (EDT)
Received: (from slmgr@localhost)
	by donner.research.telcordia.com (8.8.8/8.8.8) id PAA17779;
	Tue, 14 Oct 2003 15:01:03 -0400 (EDT)
Resent-Date: Tue, 14 Oct 2003 15:01:03 -0400 (EDT)
X-Authentication-Warning: donner.research.telcordia.com: slmgr set sender to pana-request@research.telcordia.com using -f
Old-Return-Path: <yohba@tari.toshiba.com>
Date: Tue, 14 Oct 2003 11:59:13 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: New [issue25] Service Profile names
In-reply-to: <BBB0E153.A5F6%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@research.telcordia.com
Message-id: <20031014185913.GF3695@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
 pana@research.telcordia.com
User-Agent: Mutt/1.5.4i
References: <20031009174816.GA8231@steelhead>
 <BBB0E153.A5F6%alper@docomolabs-usa.com>
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi)
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper)
Resent-Message-ID: <ZQAwSC.A.qVE.vfEj_@donner>
Resent-From: pana@research.telcordia.com
X-Mailing-List: <pana@research.telcordia.com> 
X-Loop: pana@research.telcordia.com
List-Post: <mailto:pana@research.telcordia.com>
List-Help: <mailto:pana-request@research.telcordia.com?subject=help>
Precedence: list
Resent-Sender: pana-request@research.telcordia.com

Here is the new text which reflects Alper's comments.

Yoshihiro Ohba

---
In Section 4.2, change

From:

"  When a PaC receives the PANA-Start-Request message in response to
   the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
   message. The PANA-Start-Answer message contains the initial sequence
   numbers in the tseq and rseq fields of the PANA header, a copy of
   the received Cookie as the PANA payload."

To:

"  A PANA-Start-Request can also contain zero or one NAP-Information
   AVP and zero or more ISP-Information AVPs to advertise the
   information on the NAP and/or ISPs.

   When a PaC receives the PANA-Start-Request message in response to
   the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
   message if it wishes to enter the authentication phase.  The
   PANA-Start-Answer message contains the initial sequence numbers in
   the tseq and rseq fields of the PANA header, a copy of the received
   Cookie (if any) as the PANA payload.  If the received
   PANA-Start-Request message contains a NAP-Information AVP and zero
   or more ISP-Information AVP, the PaC MAY additinally contain the
   received NAP-Information AVP and, if any, one of the received
   ISP-Information AVP(s) in the PANA-Start-Answer message to identify
   the binding between the subsequent authentication and the NAP/ISP.
   If the PaC does not contain a NAP-Information AVP or an
   ISP-Information AVP, the EAP peer identity or some default
   information MAY be used to identify the binding."


In Section 9.3.3, change

from:

"
      PANA-Start-Request ::= < PANA-Header: 2, REQ >
                    [ Cookie ]
                  * [ AVP ]
"

to:

"
      PANA-Start-Request ::= < PANA-Header: 2, REQ >
                    [ Cookie ]
		    [ NAP-Information ]
                  * [ ISP-Information ]
                  * [ AVP ]
"


In Section 9.3.4, change

from:

"     PANA-Start-Answer ::= < PANA-Header: 3 >
                    [ Cookie ]
                  * [ AVP ]"

to:

"     PANA-Start-Answer ::= < PANA-Header: 3 >
                    [ Cookie ]
		    [ NAP-Information ]
                    [ ISP-Information ]
                  * [ AVP ]"


Add the following sections:

"9.4.9 NAP-Information AVP

The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
contains one globally unique identifier of the NAP in a
Provider-Identifier AVP and one enterprise name of the NAP in a
Provider-Name AVP.  Its Data field has the following ABNF grammar:

      NAP-Information ::= < AVP Header: 1029 >
                           { Provider-Identifier }
                           { Provider-Name }
                         * [ AVP ]


9.4.10 ISP-Information AVP

The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
contains one globally unique identifier of the ISP in a
Provider-Identifier AVP and one enterprise name of the ISP in a
Provider-Name AVP.  Its Data field has the following ABNF grammar:

      ISP-Information ::= < AVP Header: 1030 >
                           { Provider-Identifier }
                           { Provider-Name }
                         * [ AVP ]


9.4.11 Provider-Identifier AVP 

The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
and contains an IANA assigned "SMI Network Management Private
Enterprise Codes" [IANAWEB] value, encoded in network byte order.
 

9.4.12 Provider-Name AVP 

The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
contains the UTF8-encoded name of the provider."




From pana-request@research.telcordia.com  Tue Oct 14 15:56:43 2003
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27385
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 15:56:36 -0400 (EDT)
Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8])
	by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id h9EJpges021726;
	Tue, 14 Oct 2003 15:51:42 -0400 (EDT)
Received: (from slmgr@localhost)
	by donner.research.telcordia.com (8.8.8/8.8.8) id PAA20019;
	Tue, 14 Oct 2003 15:51:42 -0400 (EDT)
Resent-Date: Tue, 14 Oct 2003 15:51:42 -0400 (EDT)
X-Authentication-Warning: donner.research.telcordia.com: slmgr set sender to pana-request@research.telcordia.com using -f
Old-Return-Path: <alper@docomolabs-usa.com>
Date: Tue, 14 Oct 2003 12:51:27 -0700
Subject: Re: New [issue25] Service Profile names
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Dan.Forsberg@nokia.com>, <pana@research.telcordia.com>
Message-ID: <BBB1A1CF.A6CD%alper@docomolabs-usa.com>
In-Reply-To: <20031014170834.GB3695@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi)
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper)
Resent-Message-ID: <wyOdjD.A.p4E.NPFj_@donner>
Resent-From: pana@research.telcordia.com
X-Mailing-List: <pana@research.telcordia.com> 
X-Loop: pana@research.telcordia.com
List-Post: <mailto:pana@research.telcordia.com>
List-Help: <mailto:pana-request@research.telcordia.com?subject=help>
Precedence: list
Resent-Sender: pana-request@research.telcordia.com
Content-Transfer-Encoding: 7bit

> I was assuming that multiple PAAs run by the same NAP but possibly
> handling AAA traffic for different ISPs, but I think it is also
> possible to have different NAPs on the same link, as NAP and ISP are
> basically logical separation and what is applicable to ISP is also
> logically applicable NAP.

I didn't think so. NAP is the owner of the access network (cables, routers,
switches, antennas, etc.) and there can only be one according to the current
models.

> But I think PANA design should not have to
> care about details on how the service profiles are used.

Alper



From pana-request@research.telcordia.com  Tue Oct 14 16:32:45 2003
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00948
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 16:32:44 -0400 (EDT)
Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8])
	by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id h9EKRles023398;
	Tue, 14 Oct 2003 16:27:47 -0400 (EDT)
Received: (from slmgr@localhost)
	by donner.research.telcordia.com (8.8.8/8.8.8) id QAA21555;
	Tue, 14 Oct 2003 16:27:46 -0400 (EDT)
Resent-Date: Tue, 14 Oct 2003 16:27:46 -0400 (EDT)
X-Authentication-Warning: donner.research.telcordia.com: slmgr set sender to pana-request@research.telcordia.com using -f
Old-Return-Path: <alper@docomolabs-usa.com>
Date: Tue, 14 Oct 2003 13:27:28 -0700
Subject: Re: New [issue25] Service Profile names
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Dan.Forsberg@nokia.com>, <pana@research.telcordia.com>
Message-ID: <BBB1AA40.A6E7%alper@docomolabs-usa.com>
In-Reply-To: <20031014185913.GF3695@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi)
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper)
Resent-Message-ID: <tpDWGC.A.qQF.BxFj_@donner>
Resent-From: pana@research.telcordia.com
X-Mailing-List: <pana@research.telcordia.com> 
X-Loop: pana@research.telcordia.com
List-Post: <mailto:pana@research.telcordia.com>
List-Help: <mailto:pana-request@research.telcordia.com?subject=help>
Precedence: list
Resent-Sender: pana-request@research.telcordia.com
Content-Transfer-Encoding: 7bit

I was thinking something in terms of this:

- If only a NAP-info is included in the PANA-start-answer, that means the
following authentication should be directed to particular NAP's AAA.
- If only a ISP-info is included in the PANA-start-answer, that means the
following authentication should be directed to particular ISP's AAA.
** in these cases, the NAP and ISP info overwrites whatever the EAP client
identifier may suggest. One *-info is included at a time when separate
authentication will take place.

- If both NAP-info and ISP-info are included, that means only one
authentication will take place. The *-info indicates the chosen service
combination. The authentication request is forwarded to ISP's AAA.

- If no *-info is included, that means the implicit selection depends on the
EAP client identifier.

We might also modify the f-flag logic. Maybe we can fold that logic to
PANA-start-request/answer exchange. PANA-start-request can signal the
capability to provide separate auth along with the list of ISPs/NAP.
PANA-start-answer can signal whether the PaC will do separate auths or not.
A flag in the message header can deliver this capability/choice.

Comments?

Alper



> Here is the new text which reflects Alper's comments.
> 
> Yoshihiro Ohba
> 
> ---
> In Section 4.2, change
> 
> From:
> 
> "  When a PaC receives the PANA-Start-Request message in response to
>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>  message. The PANA-Start-Answer message contains the initial sequence
>  numbers in the tseq and rseq fields of the PANA header, a copy of
>  the received Cookie as the PANA payload."
> 
> To:
> 
> "  A PANA-Start-Request can also contain zero or one NAP-Information
>  AVP and zero or more ISP-Information AVPs to advertise the
>  information on the NAP and/or ISPs.
> 
>  When a PaC receives the PANA-Start-Request message in response to
>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>  message if it wishes to enter the authentication phase.  The
>  PANA-Start-Answer message contains the initial sequence numbers in
>  the tseq and rseq fields of the PANA header, a copy of the received
>  Cookie (if any) as the PANA payload.  If the received
>  PANA-Start-Request message contains a NAP-Information AVP and zero
>  or more ISP-Information AVP, the PaC MAY additinally contain the
>  received NAP-Information AVP and, if any, one of the received
>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
>  the binding between the subsequent authentication and the NAP/ISP.
>  If the PaC does not contain a NAP-Information AVP or an
>  ISP-Information AVP, the EAP peer identity or some default
>  information MAY be used to identify the binding."
> 
> 
> In Section 9.3.3, change
> 
> from:
> 
> "
>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>                   [ Cookie ]
>                 * [ AVP ]
> "
> 
> to:
> 
> "
>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>                   [ Cookie ]
>    [ NAP-Information ]
>                 * [ ISP-Information ]
>                 * [ AVP ]
> "
> 
> 
> In Section 9.3.4, change
> 
> from:
> 
> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>                   [ Cookie ]
>                 * [ AVP ]"
> 
> to:
> 
> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>                   [ Cookie ]
>    [ NAP-Information ]
>                   [ ISP-Information ]
>                 * [ AVP ]"
> 
> 
> Add the following sections:
> 
> "9.4.9 NAP-Information AVP
> 
> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
> contains one globally unique identifier of the NAP in a
> Provider-Identifier AVP and one enterprise name of the NAP in a
> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> 
>     NAP-Information ::= < AVP Header: 1029 >
>                          { Provider-Identifier }
>                          { Provider-Name }
>                        * [ AVP ]
> 
> 
> 9.4.10 ISP-Information AVP
> 
> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
> contains one globally unique identifier of the ISP in a
> Provider-Identifier AVP and one enterprise name of the ISP in a
> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> 
>     ISP-Information ::= < AVP Header: 1030 >
>                          { Provider-Identifier }
>                          { Provider-Name }
>                        * [ AVP ]
> 
> 
> 9.4.11 Provider-Identifier AVP
> 
> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
> and contains an IANA assigned "SMI Network Management Private
> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
> 
> 
> 9.4.12 Provider-Name AVP
> 
> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
> contains the UTF8-encoded name of the provider."
> 
> 
> 



From pana-request@research.telcordia.com  Tue Oct 14 17:45:23 2003
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04214
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 17:45:22 -0400 (EDT)
Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8])
	by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id h9ELepes026601;
	Tue, 14 Oct 2003 17:40:51 -0400 (EDT)
Received: (from slmgr@localhost)
	by donner.research.telcordia.com (8.8.8/8.8.8) id RAA24945;
	Tue, 14 Oct 2003 17:40:51 -0400 (EDT)
Resent-Date: Tue, 14 Oct 2003 17:40:51 -0400 (EDT)
X-Authentication-Warning: donner.research.telcordia.com: slmgr set sender to pana-request@research.telcordia.com using -f
Old-Return-Path: <yohba@tari.toshiba.com>
Date: Tue, 14 Oct 2003 14:38:38 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: New [issue25] Service Profile names
In-reply-to: <BBB1AA40.A6E7%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@research.telcordia.com
Message-id: <20031014213838.GA6092@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
 pana@research.telcordia.com
User-Agent: Mutt/1.5.4i
References: <20031014185913.GF3695@steelhead>
 <BBB1AA40.A6E7%alper@docomolabs-usa.com>
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi)
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper)
Resent-Message-ID: <1pvVfB.A.oFG.i1Gj_@donner>
Resent-From: pana@research.telcordia.com
X-Mailing-List: <pana@research.telcordia.com> 
X-Loop: pana@research.telcordia.com
List-Post: <mailto:pana@research.telcordia.com>
List-Help: <mailto:pana-request@research.telcordia.com?subject=help>
Precedence: list
Resent-Sender: pana-request@research.telcordia.com

On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
> I was thinking something in terms of this:
> 
> - If only a NAP-info is included in the PANA-start-answer, that means the
> following authentication should be directed to particular NAP's AAA.
> - If only a ISP-info is included in the PANA-start-answer, that means the
> following authentication should be directed to particular ISP's AAA.
> ** in these cases, the NAP and ISP info overwrites whatever the EAP client
> identifier may suggest. One *-info is included at a time when separate
> authentication will take place.

OK.

> 
> - If both NAP-info and ISP-info are included, that means only one
> authentication will take place. The *-info indicates the chosen service
> combination. The authentication request is forwarded to ISP's AAA.

It seems natural for this case that separate authentication will take
place with using particular NAP's AAA and ISP's AAA.

> 
> - If no *-info is included, that means the implicit selection depends on the
> EAP client identifier.

It seems natural for this case that only one authentication will
take place with the authentication request being forwarded to ISP's
AAA.

> 
> We might also modify the f-flag logic. Maybe we can fold that logic to
> PANA-start-request/answer exchange. PANA-start-request can signal the
> capability to provide separate auth along with the list of ISPs/NAP.
> PANA-start-answer can signal whether the PaC will do separate auths or not.
> A flag in the message header can deliver this capability/choice.

Or can we use *-info contained in PANA-start-{request,answer} for that
purpose instead of definig a new flag?

Yoshihiro Ohba


> 
> Comments?
> 
> Alper
> 
> 
> 
> > Here is the new text which reflects Alper's comments.
> > 
> > Yoshihiro Ohba
> > 
> > ---
> > In Section 4.2, change
> > 
> > From:
> > 
> > "  When a PaC receives the PANA-Start-Request message in response to
> >  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >  message. The PANA-Start-Answer message contains the initial sequence
> >  numbers in the tseq and rseq fields of the PANA header, a copy of
> >  the received Cookie as the PANA payload."
> > 
> > To:
> > 
> > "  A PANA-Start-Request can also contain zero or one NAP-Information
> >  AVP and zero or more ISP-Information AVPs to advertise the
> >  information on the NAP and/or ISPs.
> > 
> >  When a PaC receives the PANA-Start-Request message in response to
> >  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >  message if it wishes to enter the authentication phase.  The
> >  PANA-Start-Answer message contains the initial sequence numbers in
> >  the tseq and rseq fields of the PANA header, a copy of the received
> >  Cookie (if any) as the PANA payload.  If the received
> >  PANA-Start-Request message contains a NAP-Information AVP and zero
> >  or more ISP-Information AVP, the PaC MAY additinally contain the
> >  received NAP-Information AVP and, if any, one of the received
> >  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
> >  the binding between the subsequent authentication and the NAP/ISP.
> >  If the PaC does not contain a NAP-Information AVP or an
> >  ISP-Information AVP, the EAP peer identity or some default
> >  information MAY be used to identify the binding."
> > 
> > 
> > In Section 9.3.3, change
> > 
> > from:
> > 
> > "
> >     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >                   [ Cookie ]
> >                 * [ AVP ]
> > "
> > 
> > to:
> > 
> > "
> >     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >                   [ Cookie ]
> >    [ NAP-Information ]
> >                 * [ ISP-Information ]
> >                 * [ AVP ]
> > "
> > 
> > 
> > In Section 9.3.4, change
> > 
> > from:
> > 
> > "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >                   [ Cookie ]
> >                 * [ AVP ]"
> > 
> > to:
> > 
> > "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >                   [ Cookie ]
> >    [ NAP-Information ]
> >                   [ ISP-Information ]
> >                 * [ AVP ]"
> > 
> > 
> > Add the following sections:
> > 
> > "9.4.9 NAP-Information AVP
> > 
> > The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
> > contains one globally unique identifier of the NAP in a
> > Provider-Identifier AVP and one enterprise name of the NAP in a
> > Provider-Name AVP.  Its Data field has the following ABNF grammar:
> > 
> >     NAP-Information ::= < AVP Header: 1029 >
> >                          { Provider-Identifier }
> >                          { Provider-Name }
> >                        * [ AVP ]
> > 
> > 
> > 9.4.10 ISP-Information AVP
> > 
> > The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
> > contains one globally unique identifier of the ISP in a
> > Provider-Identifier AVP and one enterprise name of the ISP in a
> > Provider-Name AVP.  Its Data field has the following ABNF grammar:
> > 
> >     ISP-Information ::= < AVP Header: 1030 >
> >                          { Provider-Identifier }
> >                          { Provider-Name }
> >                        * [ AVP ]
> > 
> > 
> > 9.4.11 Provider-Identifier AVP
> > 
> > The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
> > and contains an IANA assigned "SMI Network Management Private
> > Enterprise Codes" [IANAWEB] value, encoded in network byte order.
> > 
> > 
> > 9.4.12 Provider-Name AVP
> > 
> > The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
> > contains the UTF8-encoded name of the provider."
> > 
> > 
> > 
> 



From pana-request@research.telcordia.com  Tue Oct 14 17:49:51 2003
Received: from thumper.research.telcordia.com (thumper.research.telcordia.com [128.96.41.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04385
	for <pana-archive@lists.ietf.org>; Tue, 14 Oct 2003 17:49:50 -0400 (EDT)
Received: from donner.research.telcordia.com (donner-fddi.research.telcordia.com [192.4.5.8])
	by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id h9ELjJes026849;
	Tue, 14 Oct 2003 17:45:19 -0400 (EDT)
Received: (from slmgr@localhost)
	by donner.research.telcordia.com (8.8.8/8.8.8) id RAA25145;
	Tue, 14 Oct 2003 17:45:19 -0400 (EDT)
Resent-Date: Tue, 14 Oct 2003 17:45:19 -0400 (EDT)
X-Authentication-Warning: donner.research.telcordia.com: slmgr set sender to pana-request@research.telcordia.com using -f
Old-Return-Path: <yohba@tari.toshiba.com>
Date: Tue, 14 Oct 2003 14:43:44 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: New [issue25] Service Profile names
In-reply-to: <BBB1A1CF.A6CD%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@research.telcordia.com
Message-id: <20031014214344.GC6092@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
 pana@research.telcordia.com
User-Agent: Mutt/1.5.4i
References: <20031014170834.GB3695@steelhead>
 <BBB1A1CF.A6CD%alper@docomolabs-usa.com>
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (bambi)
X-RAVMilter-Version: 8.4.2(snapshot 20021217) (thumper)
Resent-Message-ID: <NzXRaD.A.wIG.u5Gj_@donner>
Resent-From: pana@research.telcordia.com
X-Mailing-List: <pana@research.telcordia.com> 
X-Loop: pana@research.telcordia.com
List-Post: <mailto:pana@research.telcordia.com>
List-Help: <mailto:pana-request@research.telcordia.com?subject=help>
Precedence: list
Resent-Sender: pana-request@research.telcordia.com

On Tue, Oct 14, 2003 at 12:51:27PM -0700, Alper Yegin wrote:
> > I was assuming that multiple PAAs run by the same NAP but possibly
> > handling AAA traffic for different ISPs, but I think it is also
> > possible to have different NAPs on the same link, as NAP and ISP are
> > basically logical separation and what is applicable to ISP is also
> > logically applicable NAP.
> 
> I didn't think so. NAP is the owner of the access network (cables, routers,
> switches, antennas, etc.) and there can only be one according to the current
> models.

Yes, you are right according to the current models.  (I just thought
that the access network could be shared among multiple NAPs...)

Yoshihiro Ohba





From pana-admin@ietf.org  Wed Oct 15 04:07:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19748
	for <pana-archive@lists.ietf.org>; Wed, 15 Oct 2003 04:07:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ggP-0002Y2-2L; Wed, 15 Oct 2003 04:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9gfy-0002X6-NA
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 04:06:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19716
	for <pana@ietf.org>; Wed, 15 Oct 2003 04:06:26 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9gfv-0000wj-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:06:31 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9gfv-0000wf-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:06:31 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9F86Ud14858
	for <pana@ietf.org>; Wed, 15 Oct 2003 11:06:30 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T654bd57791ac158f25461@esvir05nok.ntc.nokia.com>;
 Wed, 15 Oct 2003 11:06:17 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 15 Oct 2003 11:06:17 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] [issue19] Result-Code AVP values?
Date: Wed, 15 Oct 2003 11:06:17 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5AB@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOSfZam8ngFei1qTD+eCTaTXMzGUQAdIOGg
To: <yohba@tari.toshiba.com>, <alper@docomolabs-usa.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 15 Oct 2003 08:06:17.0773 (UTC) FILETIME=[360855D0:01C392F3]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I don't understand your arguments.

PANA_REALM_NOT_SERVED is seen as an error code (see the issue19), not
an authentication result code. No authentication can take place because 
of this error.

This has nothing to do with EAP or? The NAS/PAA can't route the AAA
message because it can't find the routing info for the realm. EAP is 
just carried in the AAA message (EAP-Payload AVP).

Do you think that this result code reveals too much for the PaC about 
the network side?

- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 14 October, 2003 21:03
> To: Alper Yegin
> Cc: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>
>
> There are already three authentication results defined, i.e.,
> PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
> PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
> PANA_REALM_NOT_SERVED seems to be a bit inconsistent in design with
> those three fundamental results.
>
> In addition, the EAP state machine draft does not have an interface to
> AAA to obtain detailed error information like REALM_NOT_SERVED, and
> thus in actual implementations it is likely that
> PANA_AUTHENTICATION_REJECTED is used instead of PANA_REALM_NOT_SERVED.
>
> So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
>
> Yoshihiro Ohba
>
>
> On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
> > > In PANA we retransmit requests because we want to have reliable
> > > transport. So, the case where the authenticator retransmits the
> > > EAP-Request/Identity is interpreted differently in PANA layer
> > > (retransmissions for reliability).
> > >
> > > The case of Notification Request is usable, but what does
> > > "invalid authentication attempt" mean? Can we interpret it such
> > > a way that it means "typo in the identity, user part" or "user
> > > not recognized" or "realm not served"..
> >
> > Good points, but that does not mean they are problems for
> PANA to solve.
> >
> > Generally I'm concerned about leaking EAP-layer events or
> actions into PANA.
> > But I think in this case, this is more of mapping an EAP lower-layer
> > (Diameter) event to PANA. While I wouldn't simply import
> all such events
> > from one to another, I think this one might be useful and
> not disruptive. On
> > the other hand, this error message is different from all
> the others. Those
> > are all PANA-specific.
> >
> > Hmmm... Does anyone else care to comment on this?
> >
> > Alper
> >
> >
> > >
> > > A result code in PANA for this (borrowed from Diameter) is clear
> > > and works if the authenticator implementation doesn't support
> > > this MAY part of the EAP doc.
> > >
> > > - Dan
> > >
> > >
> > >> -----Original Message-----
> > >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > >> Sent: 07 October, 2003 20:55
> > >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > >>
> > >>
> > >>>> I think this is also an EAP question. What would be the EAP
> > >>>> behavior when
> > >>>> the NAS cannot recognize the EAP client identifier?
> > >>
> > >> I think this case would be handled by the following text from
> > >> the EAP spec:
> > >>
> > >>          Implementation Note: The peer MAY obtain the
> > >> Identity via user
> > >>          input.  It is suggested that the authenticator retry the
> > >>          Identity Request in the case of an invalid Identity or
> > >>          authentication failure to allow for potential typos
> > >> on the part
> > >>          of the user.  It is suggested that the Identity
> Request be
> > >>          retried a minimum of 3 times before terminating the
> > >>          authentication.  The Notification Request MAY be used to
> > >>          indicate an invalid authentication attempt prior to
> > >>          transmitting a new Identity Request
> (optionally, the failure
> > >>          MAY be indicated within the message of the new
> > >> Identity Request
> > >>          itself).
> > >>
> > >> ... And finally I think the EAP authenticator would send a
> > >> Failure message.
> > >>
> > >> 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 exim@www1.ietf.org  Wed Oct 15 04:07:35 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19763
	for <pana-archive@odin.ietf.org>; Wed, 15 Oct 2003 04:07:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ggY-0002ZU-BE
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 04:07:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9F87AJu009878
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 04:07:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ggX-0002Z4-D1
	for pana-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 04:07:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19722
	for <pana-web-archive@ietf.org>; Wed, 15 Oct 2003 04:07:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ggU-0000wq-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 04:07:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ggU-0000wn-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 04:07:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ggP-0002Y2-2L; Wed, 15 Oct 2003 04:07:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9gfy-0002X6-NA
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 04:06:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19716
	for <pana@ietf.org>; Wed, 15 Oct 2003 04:06:26 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9gfv-0000wj-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:06:31 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9gfv-0000wf-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:06:31 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9F86Ud14858
	for <pana@ietf.org>; Wed, 15 Oct 2003 11:06:30 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T654bd57791ac158f25461@esvir05nok.ntc.nokia.com>;
 Wed, 15 Oct 2003 11:06:17 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 15 Oct 2003 11:06:17 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] [issue19] Result-Code AVP values?
Date: Wed, 15 Oct 2003 11:06:17 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5AB@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOSfZam8ngFei1qTD+eCTaTXMzGUQAdIOGg
To: <yohba@tari.toshiba.com>, <alper@docomolabs-usa.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 15 Oct 2003 08:06:17.0773 (UTC) FILETIME=[360855D0:01C392F3]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I don't understand your arguments.

PANA_REALM_NOT_SERVED is seen as an error code (see the issue19), not
an authentication result code. No authentication can take place because 
of this error.

This has nothing to do with EAP or? The NAS/PAA can't route the AAA
message because it can't find the routing info for the realm. EAP is 
just carried in the AAA message (EAP-Payload AVP).

Do you think that this result code reveals too much for the PaC about 
the network side?

- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 14 October, 2003 21:03
> To: Alper Yegin
> Cc: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>
>
> There are already three authentication results defined, i.e.,
> PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
> PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
> PANA_REALM_NOT_SERVED seems to be a bit inconsistent in design with
> those three fundamental results.
>
> In addition, the EAP state machine draft does not have an interface to
> AAA to obtain detailed error information like REALM_NOT_SERVED, and
> thus in actual implementations it is likely that
> PANA_AUTHENTICATION_REJECTED is used instead of PANA_REALM_NOT_SERVED.
>
> So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
>
> Yoshihiro Ohba
>
>
> On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
> > > In PANA we retransmit requests because we want to have reliable
> > > transport. So, the case where the authenticator retransmits the
> > > EAP-Request/Identity is interpreted differently in PANA layer
> > > (retransmissions for reliability).
> > >
> > > The case of Notification Request is usable, but what does
> > > "invalid authentication attempt" mean? Can we interpret it such
> > > a way that it means "typo in the identity, user part" or "user
> > > not recognized" or "realm not served"..
> >
> > Good points, but that does not mean they are problems for
> PANA to solve.
> >
> > Generally I'm concerned about leaking EAP-layer events or
> actions into PANA.
> > But I think in this case, this is more of mapping an EAP lower-layer
> > (Diameter) event to PANA. While I wouldn't simply import
> all such events
> > from one to another, I think this one might be useful and
> not disruptive. On
> > the other hand, this error message is different from all
> the others. Those
> > are all PANA-specific.
> >
> > Hmmm... Does anyone else care to comment on this?
> >
> > Alper
> >
> >
> > >
> > > A result code in PANA for this (borrowed from Diameter) is clear
> > > and works if the authenticator implementation doesn't support
> > > this MAY part of the EAP doc.
> > >
> > > - Dan
> > >
> > >
> > >> -----Original Message-----
> > >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > >> Sent: 07 October, 2003 20:55
> > >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > >>
> > >>
> > >>>> I think this is also an EAP question. What would be the EAP
> > >>>> behavior when
> > >>>> the NAS cannot recognize the EAP client identifier?
> > >>
> > >> I think this case would be handled by the following text from
> > >> the EAP spec:
> > >>
> > >>          Implementation Note: The peer MAY obtain the
> > >> Identity via user
> > >>          input.  It is suggested that the authenticator retry the
> > >>          Identity Request in the case of an invalid Identity or
> > >>          authentication failure to allow for potential typos
> > >> on the part
> > >>          of the user.  It is suggested that the Identity
> Request be
> > >>          retried a minimum of 3 times before terminating the
> > >>          authentication.  The Notification Request MAY be used to
> > >>          indicate an invalid authentication attempt prior to
> > >>          transmitting a new Identity Request
> (optionally, the failure
> > >>          MAY be indicated within the message of the new
> > >> Identity Request
> > >>          itself).
> > >>
> > >> ... And finally I think the EAP authenticator would send a
> > >> Failure message.
> > >>
> > >> 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-admin@ietf.org  Wed Oct 15 04:09:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19833
	for <pana-archive@lists.ietf.org>; Wed, 15 Oct 2003 04:09:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9giN-0002qv-8x; Wed, 15 Oct 2003 04:09:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ghV-0002jF-A4
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 04:08:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19792
	for <pana@ietf.org>; Wed, 15 Oct 2003 04:08:01 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ghS-0000xu-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:08:06 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ghR-0000xr-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:08:05 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9F885d16555
	for <pana@ietf.org>; Wed, 15 Oct 2003 11:08:05 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T654bd709a5ac158f21081@esvir01nok.ntc.nokia.com>;
 Wed, 15 Oct 2003 11:08:00 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 15 Oct 2003 11:07:59 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] issue 23 and 25
Date: Wed, 15 Oct 2003 11:07:59 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D73@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] issue 23 and 25
Thread-Index: AcOSf6Oz3/CpvtJoQZqItvPOyRdlbAAc5lPw
To: <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 15 Oct 2003 08:07:59.0706 (UTC) FILETIME=[72CA13A0:01C392F3]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I mean the same code space, but different numbers so that 
overlapping is not happening when processing PANA and AAA 
messages at the same application level.
- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 14 October, 2003 21:18
> To: Forsberg Dan (NRC/Helsinki)
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: Re: [Pana] issue 23 and 25
>
>
> On Tue, Oct 14, 2003 at 02:23:19PM +0300,
> Dan.Forsberg@nokia.com wrote:
> > > -----Original Message-----
> > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: 14 October, 2003 00:28
> > > To: pana@ietf.org
> > > Subject: [Pana] issue 23 and 25
> > >
> > >
> > > There are two PANA draft -01 issues for which I'm not
> sure about the
> > > consensus.
> > >
> > > Issue 23: PANA Message type/AVP numbers and Diameter command
> > > codes/AVPs
> >
> > Let me give some background for this issue, since I submitted it.
> >
> > One approach is that a NAS supports PANA functionality. A NAS
> > can be a Diameter/Radius client. To better support
> interworking with the
> > PANA and NAS functionality, it would be good to distinguish
> the command
> > code and message type numbers. This way for example PANA
> message header
> > parsing functionality can be added to a NAS almost as "link
> layer" and
> > the PANA session handling functionality can be "migrated"
> into the NAS.
>
> This seems to suggest using different code space for Diameter command
> codes and PANA message types, right?  What about using different code
> space for Diameter AVP types and PANA AVP types?  I think the same
> justification is also applicable to PANA AVP types.
>
> Yoshihiro Ohba
> 

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


From exim@www1.ietf.org  Wed Oct 15 04:09:32 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19848
	for <pana-archive@odin.ietf.org>; Wed, 15 Oct 2003 04:09:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9giT-0002u1-DU
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 04:09:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9F898jS011153
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 04:09:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9giQ-0002tK-K4
	for pana-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 04:09:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19821
	for <pana-web-archive@ietf.org>; Wed, 15 Oct 2003 04:08:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9giN-0000yN-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 04:09:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9giN-0000yK-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 04:09:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9giN-0002qv-8x; Wed, 15 Oct 2003 04:09:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ghV-0002jF-A4
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 04:08:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19792
	for <pana@ietf.org>; Wed, 15 Oct 2003 04:08:01 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ghS-0000xu-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:08:06 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ghR-0000xr-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:08:05 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9F885d16555
	for <pana@ietf.org>; Wed, 15 Oct 2003 11:08:05 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T654bd709a5ac158f21081@esvir01nok.ntc.nokia.com>;
 Wed, 15 Oct 2003 11:08:00 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 15 Oct 2003 11:07:59 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] issue 23 and 25
Date: Wed, 15 Oct 2003 11:07:59 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D73@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] issue 23 and 25
Thread-Index: AcOSf6Oz3/CpvtJoQZqItvPOyRdlbAAc5lPw
To: <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 15 Oct 2003 08:07:59.0706 (UTC) FILETIME=[72CA13A0:01C392F3]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I mean the same code space, but different numbers so that 
overlapping is not happening when processing PANA and AAA 
messages at the same application level.
- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 14 October, 2003 21:18
> To: Forsberg Dan (NRC/Helsinki)
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: Re: [Pana] issue 23 and 25
>
>
> On Tue, Oct 14, 2003 at 02:23:19PM +0300,
> Dan.Forsberg@nokia.com wrote:
> > > -----Original Message-----
> > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: 14 October, 2003 00:28
> > > To: pana@ietf.org
> > > Subject: [Pana] issue 23 and 25
> > >
> > >
> > > There are two PANA draft -01 issues for which I'm not
> sure about the
> > > consensus.
> > >
> > > Issue 23: PANA Message type/AVP numbers and Diameter command
> > > codes/AVPs
> >
> > Let me give some background for this issue, since I submitted it.
> >
> > One approach is that a NAS supports PANA functionality. A NAS
> > can be a Diameter/Radius client. To better support
> interworking with the
> > PANA and NAS functionality, it would be good to distinguish
> the command
> > code and message type numbers. This way for example PANA
> message header
> > parsing functionality can be added to a NAS almost as "link
> layer" and
> > the PANA session handling functionality can be "migrated"
> into the NAS.
>
> This seems to suggest using different code space for Diameter command
> codes and PANA message types, right?  What about using different code
> space for Diameter AVP types and PANA AVP types?  I think the same
> justification is also applicable to PANA AVP types.
>
> Yoshihiro Ohba
> 

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



From pana-admin@ietf.org  Wed Oct 15 04:48:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20640
	for <pana-archive@lists.ietf.org>; Wed, 15 Oct 2003 04:48:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hK6-000521-NI; Wed, 15 Oct 2003 04:48:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hJS-00051M-WD
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 04:47:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20600
	for <pana@ietf.org>; Wed, 15 Oct 2003 04:47:14 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hJP-0001IR-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:47:19 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hJP-0001IO-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:47:19 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9F8lKX23261
	for <pana@ietf.org>; Wed, 15 Oct 2003 11:47:20 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T654bfb08b6ac158f23076@esvir03nok.nokia.com>;
 Wed, 15 Oct 2003 11:47:19 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 15 Oct 2003 11:47:18 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Wed, 15 Oct 2003 11:47:18 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5AC@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] EAP-Request/Identity & PANA-Start-Request
Thread-Index: AcOSbx+EM3Ztk8cXTy6B4R05h1hFywAh6qTw
To: <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 15 Oct 2003 08:47:18.0741 (UTC) FILETIME=[F0E24050:01C392F8]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Yoshi,

See below.

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 14 October, 2003 19:18
> To: Forsberg Dan (NRC/Helsinki)
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
>
>
> Hi Dan,
>
> On Tue, Oct 14, 2003 at 02:01:02PM +0300,
> Dan.Forsberg@nokia.com wrote:
> > > >
> > > > PAA can itself create the EAP-Request thus the authenticator
> > > > is not involved.
> > >
> > > The current EAP authenticator state machine on the NAS
> does not allow
> > > lower-layer entity (e.g., PAA) to create an EAP Request
> on behalf of
> > > the authenticator.
> >
> > That's fine, but what if the authenticator is on the AAA backend
> > and NAS acts only as a pass-through.
> >
> > I'm not coming up this by myself. See dratf-ietf-aaa-eap-02.txt
> > section 2.2., the "preferred way" (second figure).
>
> The passthrough authenticator behavior described in
> dratf-ietf-aaa-eap-02.txt is explicitly supported in the EAP state
> machines draft (draft-ietf-eap-statemachines-00.txt), but when this
> happens, the initial EAP Request/Identity is always generated *at EAP
> layer*, not at PANA layer. So the proposed approach will not work for
> an implementation that is based on
> draft-ietf-eap-statemachines-00.txt.

Yes, I meant that the EAP layer is kicked to do it. I mixed EAP backend 
authenticator and passthrough authenticator. It's a bit misleading to use 
the same term for both entities.

> >
> > Another alternative is that the client sends User-Name or
> User-Realm
> > AVP in PANA-Start-Answer from PaC to PAA. But I think that this
> > "preferred way" is good to have.
>
> I think the "preferred way" is automatically supported in the currrent
> combination of PANA and EAP, i.e., the passthrough EAP authenticator
> (that is co-located with PAA) generates the initial EAP
> Request/Identity and passes it PAA, which then puts the message in a
> PANA message and forwards it to the PaC. 

Ok. 

>
> The issue we are discussing is: which PANA message should carry the
> initial EAP Request/Identity and here is my suggestion: 
>
>   "When a Cookie-AVP is carried in a PANA-Start-Request message, the
>   initial EAP Request MUST NOT be carried in the PANA-Start-Request
>   message in order for the PAA to be stateful.

I don't think that the Cookie makes PAA necessarily stateful. PAA could
use a timestamp and a hash of PaC's address, encrypt that with a secret 
key and use it as a cookie. When PAA checks the cookie, it decrypts it 
and checks the timestamp and address hash. No state required. I'm not a 
cookie expert, though.

>
>   When a Cookie-AVP is not carried in a PANA-Start-Request message,
>   the PAA does not need to be stateful.  In this case, the initial EAP
>   Request message MAY be carried in the PANA-Start-Request message.
>   If the initial EAP Request message is carried in the
>   PANA-Start-Request message, an EAP Response message MUST be carried
>   in the PANA-Start-Answer message returned to the PAA.
>  
>   In any case, PANA MUST NOT generate an EAP message on behalf of
>   EAP peer or EAP authenticator."

Just for clarification and for easier understanding what about: 
   "In any case, PANA MUST NOT generate an EAP message on behalf of
    EAP peer or EAP (passthrough) authenticator."

>
> I think this allows saving one round trip when PAA does not need to be
> stateless.

Ok, but I don't fully agree about the separation of Cookie and EAP-Request. 
See the comment above.

I guess you meant stateful?

- Dan

>
> What do you think?
>
> Yoshihiro Ohba
>
> >
> > Do you see any problems in this? If there are, we have to
> notify the
> > draft-ietf-aaa-eap-02.txt authors too.
> >
> > - Dan
> >
> > > >
> > > > Otherwise PaC needs to send it's identity to the PAA out
> > > > of the EAP so that PAA/NAS can contact the right authenticator.
> > >
> > > In some EAP environment where MAC address is used as a client
> > > identifier, the identifier can be effectively obtained
> from the MAC
> > > header that carries PANA message without using
> EAP-Identity exchange.
> > >
> > > >
> > > > - Dan
> > >
> > > Yoshihiro Ohba
> > >
> > > >
> > > > > -----Original Message-----
> > > > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > Sent: 10 October, 2003 18:35
> > > > > To: Forsberg Dan (NRC/Helsinki)
> > > > > Cc: pana@ietf.org
> > > > > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> > > > >
> > > > >
> > > > > On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> > > > > Dan.Forsberg@nokia.com wrote:
> > > > > > PANA folks,
> > > > > >
> > > > > > We have PANA-Start-Request/Answer messgae pair
> carrying Cookie.
> > > > > > Then we have the first PANA-Auth-Request/Answer message pair
> > > > > > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > > > > > EAP-Request/Identity is generated in the PAA/NAS,
> because/which
> > > > > > at that point doesn't know the realm for the user.
> EAP header
> > > > > > also contains the identifier field which is
> somewhat analoguous
> > > > > > to PANA cookie. Why not to put the first EAP
> payload AVP into
> > > > > > the PANA-Start-Request message? This doesn't bring any new
> > > > > > requirements for the PAA to create state
> information, because
> > > > > > the EAP header identifier field can act similarly
> to PANA cookie
> > > > > > AVP... or in the extreme we could drop the cookie
> AVP and use
> > > > > > the EAP identifier field as the "cookie".
> > > > >
> > > > > There are two things we need to consider here:
> > > > >
> > > > > o The first EAP Request sent by the EAP authenticator is
> > > not always
> > > > >   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> > > > > is optional when
> > > > >   the client identity can be obtained by some other means.
> > > > >
> > > > > o EAP state machine
> > > (draft-ietf-eap-statemachines-00.{txt,ps}) does
> > > > >   not allow an EAP authenticator to be stateless when sending
> > > > > the first EAP Request.
> > > > >
> > > > > So in general PAA cannot be stateless when sending a
> > > > > PANA-Start-Request
> > > > > with piggybacking an EAP Request.
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > Let me hear your comments.
> > > > > >
> > > > > > Br,
> > > > > > - Dan
> > > > > >
> > > > > > _______________________________________________
> > > > > > Pana mailing list
> > > > > > Pana@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/pana
> > > > >
> > >
>
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 

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


From exim@www1.ietf.org  Wed Oct 15 04:48:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20655
	for <pana-archive@odin.ietf.org>; Wed, 15 Oct 2003 04:48:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hKB-00052m-S1
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 04:48:08 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9F8m7T3019389
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 04:48:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hKB-00052a-2b
	for pana-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 04:48:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20615
	for <pana-web-archive@ietf.org>; Wed, 15 Oct 2003 04:47:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hK7-0001Ip-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 04:48:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hK7-0001Im-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 04:48:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hK6-000521-NI; Wed, 15 Oct 2003 04:48:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hJS-00051M-WD
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 04:47:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20600
	for <pana@ietf.org>; Wed, 15 Oct 2003 04:47:14 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hJP-0001IR-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:47:19 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hJP-0001IO-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:47:19 -0400
Received: from esvir03nok.nokia.com (esvir03nokt.ntc.nokia.com [172.21.143.35])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9F8lKX23261
	for <pana@ietf.org>; Wed, 15 Oct 2003 11:47:20 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir03nok.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T654bfb08b6ac158f23076@esvir03nok.nokia.com>;
 Wed, 15 Oct 2003 11:47:19 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Wed, 15 Oct 2003 11:47:18 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Wed, 15 Oct 2003 11:47:18 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5AC@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] EAP-Request/Identity & PANA-Start-Request
Thread-Index: AcOSbx+EM3Ztk8cXTy6B4R05h1hFywAh6qTw
To: <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 15 Oct 2003 08:47:18.0741 (UTC) FILETIME=[F0E24050:01C392F8]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Yoshi,

See below.

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 14 October, 2003 19:18
> To: Forsberg Dan (NRC/Helsinki)
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
>
>
> Hi Dan,
>
> On Tue, Oct 14, 2003 at 02:01:02PM +0300,
> Dan.Forsberg@nokia.com wrote:
> > > >
> > > > PAA can itself create the EAP-Request thus the authenticator
> > > > is not involved.
> > >
> > > The current EAP authenticator state machine on the NAS
> does not allow
> > > lower-layer entity (e.g., PAA) to create an EAP Request
> on behalf of
> > > the authenticator.
> >
> > That's fine, but what if the authenticator is on the AAA backend
> > and NAS acts only as a pass-through.
> >
> > I'm not coming up this by myself. See dratf-ietf-aaa-eap-02.txt
> > section 2.2., the "preferred way" (second figure).
>
> The passthrough authenticator behavior described in
> dratf-ietf-aaa-eap-02.txt is explicitly supported in the EAP state
> machines draft (draft-ietf-eap-statemachines-00.txt), but when this
> happens, the initial EAP Request/Identity is always generated *at EAP
> layer*, not at PANA layer. So the proposed approach will not work for
> an implementation that is based on
> draft-ietf-eap-statemachines-00.txt.

Yes, I meant that the EAP layer is kicked to do it. I mixed EAP backend 
authenticator and passthrough authenticator. It's a bit misleading to use 
the same term for both entities.

> >
> > Another alternative is that the client sends User-Name or
> User-Realm
> > AVP in PANA-Start-Answer from PaC to PAA. But I think that this
> > "preferred way" is good to have.
>
> I think the "preferred way" is automatically supported in the currrent
> combination of PANA and EAP, i.e., the passthrough EAP authenticator
> (that is co-located with PAA) generates the initial EAP
> Request/Identity and passes it PAA, which then puts the message in a
> PANA message and forwards it to the PaC. 

Ok. 

>
> The issue we are discussing is: which PANA message should carry the
> initial EAP Request/Identity and here is my suggestion: 
>
>   "When a Cookie-AVP is carried in a PANA-Start-Request message, the
>   initial EAP Request MUST NOT be carried in the PANA-Start-Request
>   message in order for the PAA to be stateful.

I don't think that the Cookie makes PAA necessarily stateful. PAA could
use a timestamp and a hash of PaC's address, encrypt that with a secret 
key and use it as a cookie. When PAA checks the cookie, it decrypts it 
and checks the timestamp and address hash. No state required. I'm not a 
cookie expert, though.

>
>   When a Cookie-AVP is not carried in a PANA-Start-Request message,
>   the PAA does not need to be stateful.  In this case, the initial EAP
>   Request message MAY be carried in the PANA-Start-Request message.
>   If the initial EAP Request message is carried in the
>   PANA-Start-Request message, an EAP Response message MUST be carried
>   in the PANA-Start-Answer message returned to the PAA.
>  
>   In any case, PANA MUST NOT generate an EAP message on behalf of
>   EAP peer or EAP authenticator."

Just for clarification and for easier understanding what about: 
   "In any case, PANA MUST NOT generate an EAP message on behalf of
    EAP peer or EAP (passthrough) authenticator."

>
> I think this allows saving one round trip when PAA does not need to be
> stateless.

Ok, but I don't fully agree about the separation of Cookie and EAP-Request. 
See the comment above.

I guess you meant stateful?

- Dan

>
> What do you think?
>
> Yoshihiro Ohba
>
> >
> > Do you see any problems in this? If there are, we have to
> notify the
> > draft-ietf-aaa-eap-02.txt authors too.
> >
> > - Dan
> >
> > > >
> > > > Otherwise PaC needs to send it's identity to the PAA out
> > > > of the EAP so that PAA/NAS can contact the right authenticator.
> > >
> > > In some EAP environment where MAC address is used as a client
> > > identifier, the identifier can be effectively obtained
> from the MAC
> > > header that carries PANA message without using
> EAP-Identity exchange.
> > >
> > > >
> > > > - Dan
> > >
> > > Yoshihiro Ohba
> > >
> > > >
> > > > > -----Original Message-----
> > > > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > Sent: 10 October, 2003 18:35
> > > > > To: Forsberg Dan (NRC/Helsinki)
> > > > > Cc: pana@ietf.org
> > > > > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> > > > >
> > > > >
> > > > > On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> > > > > Dan.Forsberg@nokia.com wrote:
> > > > > > PANA folks,
> > > > > >
> > > > > > We have PANA-Start-Request/Answer messgae pair
> carrying Cookie.
> > > > > > Then we have the first PANA-Auth-Request/Answer message pair
> > > > > > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > > > > > EAP-Request/Identity is generated in the PAA/NAS,
> because/which
> > > > > > at that point doesn't know the realm for the user.
> EAP header
> > > > > > also contains the identifier field which is
> somewhat analoguous
> > > > > > to PANA cookie. Why not to put the first EAP
> payload AVP into
> > > > > > the PANA-Start-Request message? This doesn't bring any new
> > > > > > requirements for the PAA to create state
> information, because
> > > > > > the EAP header identifier field can act similarly
> to PANA cookie
> > > > > > AVP... or in the extreme we could drop the cookie
> AVP and use
> > > > > > the EAP identifier field as the "cookie".
> > > > >
> > > > > There are two things we need to consider here:
> > > > >
> > > > > o The first EAP Request sent by the EAP authenticator is
> > > not always
> > > > >   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> > > > > is optional when
> > > > >   the client identity can be obtained by some other means.
> > > > >
> > > > > o EAP state machine
> > > (draft-ietf-eap-statemachines-00.{txt,ps}) does
> > > > >   not allow an EAP authenticator to be stateless when sending
> > > > > the first EAP Request.
> > > > >
> > > > > So in general PAA cannot be stateless when sending a
> > > > > PANA-Start-Request
> > > > > with piggybacking an EAP Request.
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > Let me hear your comments.
> > > > > >
> > > > > > Br,
> > > > > > - Dan
> > > > > >
> > > > > > _______________________________________________
> > > > > > Pana mailing list
> > > > > > Pana@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/pana
> > > > >
> > >
>
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 

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



From pana-admin@ietf.org  Wed Oct 15 04:58:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21064
	for <pana-archive@lists.ietf.org>; Wed, 15 Oct 2003 04:58:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hTp-0005rh-CY; Wed, 15 Oct 2003 04:58:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hTD-0005qU-Aq
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 04:57:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21010
	for <pana@ietf.org>; Wed, 15 Oct 2003 04:57:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hT9-0001Rh-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:57:23 -0400
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hT9-0001Re-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:57:23 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by david.siemens.de (8.11.7/8.11.7) with ESMTP id h9F8vNk25112;
	Wed, 15 Oct 2003 10:57:23 +0200 (MEST)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h9F8vJx27023;
	Wed, 15 Oct 2003 10:57:19 +0200 (MEST)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19)
	id <4DN1Q2X2>; Wed, 15 Oct 2003 10:57:10 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC02C3@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Wed, 15 Oct 2003 10:57:12 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-2022-jp"
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi yoshi, 
hi dan, 

i haven't seen a response to the proposal for making the denial of service
protection optional. 

ciao
hannes


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Tuesday, October 14, 2003 6:18 PM
> To: Dan.Forsberg@nokia.com
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> 
> 
> Hi Dan,
> 
> On Tue, Oct 14, 2003 at 02:01:02PM +0300, 
> Dan.Forsberg@nokia.com wrote:
> > > >
> > > > PAA can itself create the EAP-Request thus the authenticator
> > > > is not involved.
> > >
> > > The current EAP authenticator state machine on the NAS 
> does not allow
> > > lower-layer entity (e.g., PAA) to create an EAP Request 
> on behalf of
> > > the authenticator.
> > 
> > That's fine, but what if the authenticator is on the AAA backend 
> > and NAS acts only as a pass-through.
> > 
> > I'm not coming up this by myself. See dratf-ietf-aaa-eap-02.txt 
> > section 2.2., the "preferred way" (second figure).
> 
> The passthrough authenticator behavior described in
> dratf-ietf-aaa-eap-02.txt is explicitly supported in the EAP state
> machines draft (draft-ietf-eap-statemachines-00.txt), but when this
> happens, the initial EAP Request/Identity is always generated *at EAP
> layer*, not at PANA layer. So the proposed approach will not work for
> an implementation that is based on 
> draft-ietf-eap-statemachines-00.txt.
> 
> > 
> > Another alternative is that the client sends User-Name or 
> User-Realm 
> > AVP in PANA-Start-Answer from PaC to PAA. But I think that this 
> > "preferred way" is good to have. 
> 
> I think the "preferred way" is automatically supported in the currrent
> combination of PANA and EAP, i.e., the passthrough EAP authenticator
> (that is co-located with PAA) generates the initial EAP
> Request/Identity and passes it PAA, which then puts the message in a
> PANA message and forwards it to the PaC.  
> 
> The issue we are discussing is: which PANA message should carry the
> initial EAP Request/Identity and here is my suggestion:  
> 
>   "When a Cookie-AVP is carried in a PANA-Start-Request message, the
>   initial EAP Request MUST NOT be carried in the PANA-Start-Request
>   message in order for the PAA to be stateful.
> 
>   When a Cookie-AVP is not carried in a PANA-Start-Request message,
>   the PAA does not need to be stateful.  In this case, the initial EAP
>   Request message MAY be carried in the PANA-Start-Request message.
>   If the initial EAP Request message is carried in the
>   PANA-Start-Request message, an EAP Response message MUST be carried
>   in the PANA-Start-Answer message returned to the PAA.
>   
>   In any case, PANA MUST NOT generate an EAP message on behalf of
>   EAP peer or EAP authenticator."
> 
> I think this allows saving one round trip when PAA does not need to be
> stateless.
> 
> What do you think?
> 
> Yoshihiro Ohba
> 
> > 
> > Do you see any problems in this? If there are, we have to 
> notify the 
> > draft-ietf-aaa-eap-02.txt authors too.
> > 
> > - Dan
> > 
> > > >
> > > > Otherwise PaC needs to send it's identity to the PAA out
> > > > of the EAP so that PAA/NAS can contact the right authenticator.
> > >
> > > In some EAP environment where MAC address is used as a client
> > > identifier, the identifier can be effectively obtained 
> from the MAC
> > > header that carries PANA message without using 
> EAP-Identity exchange.
> > >
> > > >
> > > > - Dan
> > >
> > > Yoshihiro Ohba
> > >
> > > >
> > > > > -----Original Message-----
> > > > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > Sent: 10 October, 2003 18:35
> > > > > To: Forsberg Dan (NRC/Helsinki)
> > > > > Cc: pana@ietf.org
> > > > > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> > > > >
> > > > >
> > > > > On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> > > > > Dan.Forsberg@nokia.com wrote:
> > > > > > PANA folks,
> > > > > >
> > > > > > We have PANA-Start-Request/Answer messgae pair 
> carrying Cookie.
> > > > > > Then we have the first PANA-Auth-Request/Answer message pair
> > > > > > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > > > > > EAP-Request/Identity is generated in the PAA/NAS, 
> because/which
> > > > > > at that point doesn't know the realm for the user. 
> EAP header
> > > > > > also contains the identifier field which is 
> somewhat analoguous
> > > > > > to PANA cookie. Why not to put the first EAP 
> payload AVP into
> > > > > > the PANA-Start-Request message? This doesn't bring any new
> > > > > > requirements for the PAA to create state 
> information, because
> > > > > > the EAP header identifier field can act similarly 
> to PANA cookie
> > > > > > AVP... or in the extreme we could drop the cookie 
> AVP and use
> > > > > > the EAP identifier field as the "cookie".
> > > > >
> > > > > There are two things we need to consider here:
> > > > >
> > > > > o The first EAP Request sent by the EAP authenticator is
> > > not always
> > > > >   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> > > > > is optional when
> > > > >   the client identity can be obtained by some other means.
> > > > >
> > > > > o EAP state machine
> > > (draft-ietf-eap-statemachines-00.{txt,ps}) does
> > > > >   not allow an EAP authenticator to be stateless when sending
> > > > > the first EAP Request.
> > > > >
> > > > > So in general PAA cannot be stateless when sending a
> > > > > PANA-Start-Request
> > > > > with piggybacking an EAP Request.
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > Let me hear your comments.
> > > > > >
> > > > > > Br,
> > > > > > - Dan
> > > > > >
> > > > > > _______________________________________________
> > > > > > Pana mailing list
> > > > > > Pana@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/pana
> > > > >
> > > 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 

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


From exim@www1.ietf.org  Wed Oct 15 04:58:33 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21079
	for <pana-archive@odin.ietf.org>; Wed, 15 Oct 2003 04:58:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hTu-0005uq-Sw
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 04:58:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9F8wAIX022653
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 04:58:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hTt-0005tH-67
	for pana-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 04:58:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21041
	for <pana-web-archive@ietf.org>; Wed, 15 Oct 2003 04:57:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hTp-0001Si-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 04:58:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hTp-0001Sf-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 04:58:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hTp-0005rh-CY; Wed, 15 Oct 2003 04:58:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9hTD-0005qU-Aq
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 04:57:27 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21010
	for <pana@ietf.org>; Wed, 15 Oct 2003 04:57:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hT9-0001Rh-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:57:23 -0400
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9hT9-0001Re-00
	for pana@ietf.org; Wed, 15 Oct 2003 04:57:23 -0400
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by david.siemens.de (8.11.7/8.11.7) with ESMTP id h9F8vNk25112;
	Wed, 15 Oct 2003 10:57:23 +0200 (MEST)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h9F8vJx27023;
	Wed, 15 Oct 2003 10:57:19 +0200 (MEST)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19)
	id <4DN1Q2X2>; Wed, 15 Oct 2003 10:57:10 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC02C3@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Wed, 15 Oct 2003 10:57:12 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-2022-jp"
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi yoshi, 
hi dan, 

i haven't seen a response to the proposal for making the denial of service
protection optional. 

ciao
hannes


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Tuesday, October 14, 2003 6:18 PM
> To: Dan.Forsberg@nokia.com
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> 
> 
> Hi Dan,
> 
> On Tue, Oct 14, 2003 at 02:01:02PM +0300, 
> Dan.Forsberg@nokia.com wrote:
> > > >
> > > > PAA can itself create the EAP-Request thus the authenticator
> > > > is not involved.
> > >
> > > The current EAP authenticator state machine on the NAS 
> does not allow
> > > lower-layer entity (e.g., PAA) to create an EAP Request 
> on behalf of
> > > the authenticator.
> > 
> > That's fine, but what if the authenticator is on the AAA backend 
> > and NAS acts only as a pass-through.
> > 
> > I'm not coming up this by myself. See dratf-ietf-aaa-eap-02.txt 
> > section 2.2., the "preferred way" (second figure).
> 
> The passthrough authenticator behavior described in
> dratf-ietf-aaa-eap-02.txt is explicitly supported in the EAP state
> machines draft (draft-ietf-eap-statemachines-00.txt), but when this
> happens, the initial EAP Request/Identity is always generated *at EAP
> layer*, not at PANA layer. So the proposed approach will not work for
> an implementation that is based on 
> draft-ietf-eap-statemachines-00.txt.
> 
> > 
> > Another alternative is that the client sends User-Name or 
> User-Realm 
> > AVP in PANA-Start-Answer from PaC to PAA. But I think that this 
> > "preferred way" is good to have. 
> 
> I think the "preferred way" is automatically supported in the currrent
> combination of PANA and EAP, i.e., the passthrough EAP authenticator
> (that is co-located with PAA) generates the initial EAP
> Request/Identity and passes it PAA, which then puts the message in a
> PANA message and forwards it to the PaC.  
> 
> The issue we are discussing is: which PANA message should carry the
> initial EAP Request/Identity and here is my suggestion:  
> 
>   "When a Cookie-AVP is carried in a PANA-Start-Request message, the
>   initial EAP Request MUST NOT be carried in the PANA-Start-Request
>   message in order for the PAA to be stateful.
> 
>   When a Cookie-AVP is not carried in a PANA-Start-Request message,
>   the PAA does not need to be stateful.  In this case, the initial EAP
>   Request message MAY be carried in the PANA-Start-Request message.
>   If the initial EAP Request message is carried in the
>   PANA-Start-Request message, an EAP Response message MUST be carried
>   in the PANA-Start-Answer message returned to the PAA.
>   
>   In any case, PANA MUST NOT generate an EAP message on behalf of
>   EAP peer or EAP authenticator."
> 
> I think this allows saving one round trip when PAA does not need to be
> stateless.
> 
> What do you think?
> 
> Yoshihiro Ohba
> 
> > 
> > Do you see any problems in this? If there are, we have to 
> notify the 
> > draft-ietf-aaa-eap-02.txt authors too.
> > 
> > - Dan
> > 
> > > >
> > > > Otherwise PaC needs to send it's identity to the PAA out
> > > > of the EAP so that PAA/NAS can contact the right authenticator.
> > >
> > > In some EAP environment where MAC address is used as a client
> > > identifier, the identifier can be effectively obtained 
> from the MAC
> > > header that carries PANA message without using 
> EAP-Identity exchange.
> > >
> > > >
> > > > - Dan
> > >
> > > Yoshihiro Ohba
> > >
> > > >
> > > > > -----Original Message-----
> > > > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > > Sent: 10 October, 2003 18:35
> > > > > To: Forsberg Dan (NRC/Helsinki)
> > > > > Cc: pana@ietf.org
> > > > > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> > > > >
> > > > >
> > > > > On Fri, Oct 10, 2003 at 03:53:06PM +0300,
> > > > > Dan.Forsberg@nokia.com wrote:
> > > > > > PANA folks,
> > > > > >
> > > > > > We have PANA-Start-Request/Answer messgae pair 
> carrying Cookie.
> > > > > > Then we have the first PANA-Auth-Request/Answer message pair
> > > > > > carrying EAP-Request/Identity and EAP-Response/Identity. The
> > > > > > EAP-Request/Identity is generated in the PAA/NAS, 
> because/which
> > > > > > at that point doesn't know the realm for the user. 
> EAP header
> > > > > > also contains the identifier field which is 
> somewhat analoguous
> > > > > > to PANA cookie. Why not to put the first EAP 
> payload AVP into
> > > > > > the PANA-Start-Request message? This doesn't bring any new
> > > > > > requirements for the PAA to create state 
> information, because
> > > > > > the EAP header identifier field can act similarly 
> to PANA cookie
> > > > > > AVP... or in the extreme we could drop the cookie 
> AVP and use
> > > > > > the EAP identifier field as the "cookie".
> > > > >
> > > > > There are two things we need to consider here:
> > > > >
> > > > > o The first EAP Request sent by the EAP authenticator is
> > > not always
> > > > >   EAP-Request/Identity, i.e., the use of EAP-Request/Identity
> > > > > is optional when
> > > > >   the client identity can be obtained by some other means.
> > > > >
> > > > > o EAP state machine
> > > (draft-ietf-eap-statemachines-00.{txt,ps}) does
> > > > >   not allow an EAP authenticator to be stateless when sending
> > > > > the first EAP Request.
> > > > >
> > > > > So in general PAA cannot be stateless when sending a
> > > > > PANA-Start-Request
> > > > > with piggybacking an EAP Request.
> > > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > Let me hear your comments.
> > > > > >
> > > > > > Br,
> > > > > > - Dan
> > > > > >
> > > > > > _______________________________________________
> > > > > > Pana mailing list
> > > > > > Pana@ietf.org
> > > > > > https://www1.ietf.org/mailman/listinfo/pana
> > > > >
> > > 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 

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



From pana-admin@ietf.org  Wed Oct 15 12:26:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07730
	for <pana-archive@lists.ietf.org>; Wed, 15 Oct 2003 12:26:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9oTK-0001rz-IS; Wed, 15 Oct 2003 12:26:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9oSx-0001qC-02
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 12:25:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07676
	for <pana@ietf.org>; Wed, 15 Oct 2003 12:25:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oSv-0006xp-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:25:37 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oSu-0006xl-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:25:36 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9FGPOF1013142;
	Thu, 16 Oct 2003 01:25:24 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9FGPO9k029442;
	Thu, 16 Oct 2003 01:25:24 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA29436 ; Thu, 16 Oct 2003 01:25:24 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA00104; Thu, 16 Oct 2003 01:25:23 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA11896; Thu, 16 Oct 2003 01:25:22 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9FGPMib012732;
	Thu, 16 Oct 2003 01:25:22 +0900 (JST)
Received: from steelhead ([159.119.168.137]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMT0013H4A7T4@tsbpo1.po.toshiba.co.jp>; Thu,
 16 Oct 2003 01:25:21 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9oQt-0002H2-00; Wed, 15 Oct 2003 09:23:31 -0700
Date: Wed, 15 Oct 2003 09:23:30 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue19] Result-Code AVP values?
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5AB@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, alper@docomolabs-usa.com, pana@ietf.org
Message-id: <20031015162330.GA8002@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com,
 alper@docomolabs-usa.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5AB@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Wed, Oct 15, 2003 at 11:06:17AM +0300, Dan.Forsberg@nokia.com wrote:
> I don't understand your arguments.
> 
> PANA_REALM_NOT_SERVED is seen as an error code (see the issue19), not
> an authentication result code. No authentication can take place because 
> of this error.
> 
> This has nothing to do with EAP or? The NAS/PAA can't route the AAA
> message because it can't find the routing info for the realm. EAP is 
> just carried in the AAA message (EAP-Payload AVP).

OK.  I see what you mean.

It would depend on the behavior of of the EAP authenticator on the NAS
when the AAA message routing error happens.

If the authenticator generate an EAP Failure, the result code should
contain an authentication result.

If the authenticator generates a new EAP Request/Identity to give 
the EAP peer another chance to send a correct identity and 
no result code will be included.

(There would be another possibility: the authenticator retransmits the
initial EAP Request/Identity, but this will not work because the EAP
peer will retransmit the old EAP Response/Identity which contains the
old realm that caused the AAA message routing error.)

I don't see a case where a status code of a protocol error class 
is returned in the above scenarios.

> 
> Do you think that this result code reveals too much for the PaC about 
> the network side?

I believe error handling at PAA would be complicated if AAA errors are
revealed to PANA.  PAA should just interface to EAP, not to AAA.

Yoshihiro Ohba


> 
> - Dan
> 
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 14 October, 2003 21:03
> > To: Alper Yegin
> > Cc: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > Subject: Re: [Pana] [issue19] Result-Code AVP values?
> >
> >
> > There are already three authentication results defined, i.e.,
> > PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
> > PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
> > PANA_REALM_NOT_SERVED seems to be a bit inconsistent in design with
> > those three fundamental results.
> >
> > In addition, the EAP state machine draft does not have an interface to
> > AAA to obtain detailed error information like REALM_NOT_SERVED, and
> > thus in actual implementations it is likely that
> > PANA_AUTHENTICATION_REJECTED is used instead of PANA_REALM_NOT_SERVED.
> >
> > So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
> >
> > Yoshihiro Ohba
> >
> >
> > On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
> > > > In PANA we retransmit requests because we want to have reliable
> > > > transport. So, the case where the authenticator retransmits the
> > > > EAP-Request/Identity is interpreted differently in PANA layer
> > > > (retransmissions for reliability).
> > > >
> > > > The case of Notification Request is usable, but what does
> > > > "invalid authentication attempt" mean? Can we interpret it such
> > > > a way that it means "typo in the identity, user part" or "user
> > > > not recognized" or "realm not served"..
> > >
> > > Good points, but that does not mean they are problems for
> > PANA to solve.
> > >
> > > Generally I'm concerned about leaking EAP-layer events or
> > actions into PANA.
> > > But I think in this case, this is more of mapping an EAP lower-layer
> > > (Diameter) event to PANA. While I wouldn't simply import
> > all such events
> > > from one to another, I think this one might be useful and
> > not disruptive. On
> > > the other hand, this error message is different from all
> > the others. Those
> > > are all PANA-specific.
> > >
> > > Hmmm... Does anyone else care to comment on this?
> > >
> > > Alper
> > >
> > >
> > > >
> > > > A result code in PANA for this (borrowed from Diameter) is clear
> > > > and works if the authenticator implementation doesn't support
> > > > this MAY part of the EAP doc.
> > > >
> > > > - Dan
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > > >> Sent: 07 October, 2003 20:55
> > > >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > > >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > > >>
> > > >>
> > > >>>> I think this is also an EAP question. What would be the EAP
> > > >>>> behavior when
> > > >>>> the NAS cannot recognize the EAP client identifier?
> > > >>
> > > >> I think this case would be handled by the following text from
> > > >> the EAP spec:
> > > >>
> > > >>          Implementation Note: The peer MAY obtain the
> > > >> Identity via user
> > > >>          input.  It is suggested that the authenticator retry the
> > > >>          Identity Request in the case of an invalid Identity or
> > > >>          authentication failure to allow for potential typos
> > > >> on the part
> > > >>          of the user.  It is suggested that the Identity
> > Request be
> > > >>          retried a minimum of 3 times before terminating the
> > > >>          authentication.  The Notification Request MAY be used to
> > > >>          indicate an invalid authentication attempt prior to
> > > >>          transmitting a new Identity Request
> > (optionally, the failure
> > > >>          MAY be indicated within the message of the new
> > > >> Identity Request
> > > >>          itself).
> > > >>
> > > >> ... And finally I think the EAP authenticator would send a
> > > >> Failure message.
> > > >>
> > > >> 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 exim@www1.ietf.org  Wed Oct 15 12:26:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07745
	for <pana-archive@odin.ietf.org>; Wed, 15 Oct 2003 12:26:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9oTQ-0001st-Sc
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 12:26:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9FGQ8iG007237
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 12:26:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9oTQ-0001se-MF
	for pana-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 12:26:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07694
	for <pana-web-archive@ietf.org>; Wed, 15 Oct 2003 12:25:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oTP-0006yE-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 12:26:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oTO-0006yA-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 12:26:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9oTK-0001rz-IS; Wed, 15 Oct 2003 12:26:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9oSx-0001qC-02
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 12:25:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07676
	for <pana@ietf.org>; Wed, 15 Oct 2003 12:25:29 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oSv-0006xp-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:25:37 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oSu-0006xl-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:25:36 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9FGPOF1013142;
	Thu, 16 Oct 2003 01:25:24 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9FGPO9k029442;
	Thu, 16 Oct 2003 01:25:24 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA29436 ; Thu, 16 Oct 2003 01:25:24 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA00104; Thu, 16 Oct 2003 01:25:23 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA11896; Thu, 16 Oct 2003 01:25:22 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9FGPMib012732;
	Thu, 16 Oct 2003 01:25:22 +0900 (JST)
Received: from steelhead ([159.119.168.137]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMT0013H4A7T4@tsbpo1.po.toshiba.co.jp>; Thu,
 16 Oct 2003 01:25:21 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9oQt-0002H2-00; Wed, 15 Oct 2003 09:23:31 -0700
Date: Wed, 15 Oct 2003 09:23:30 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue19] Result-Code AVP values?
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5AB@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, alper@docomolabs-usa.com, pana@ietf.org
Message-id: <20031015162330.GA8002@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com,
 alper@docomolabs-usa.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5AB@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Wed, Oct 15, 2003 at 11:06:17AM +0300, Dan.Forsberg@nokia.com wrote:
> I don't understand your arguments.
> 
> PANA_REALM_NOT_SERVED is seen as an error code (see the issue19), not
> an authentication result code. No authentication can take place because 
> of this error.
> 
> This has nothing to do with EAP or? The NAS/PAA can't route the AAA
> message because it can't find the routing info for the realm. EAP is 
> just carried in the AAA message (EAP-Payload AVP).

OK.  I see what you mean.

It would depend on the behavior of of the EAP authenticator on the NAS
when the AAA message routing error happens.

If the authenticator generate an EAP Failure, the result code should
contain an authentication result.

If the authenticator generates a new EAP Request/Identity to give 
the EAP peer another chance to send a correct identity and 
no result code will be included.

(There would be another possibility: the authenticator retransmits the
initial EAP Request/Identity, but this will not work because the EAP
peer will retransmit the old EAP Response/Identity which contains the
old realm that caused the AAA message routing error.)

I don't see a case where a status code of a protocol error class 
is returned in the above scenarios.

> 
> Do you think that this result code reveals too much for the PaC about 
> the network side?

I believe error handling at PAA would be complicated if AAA errors are
revealed to PANA.  PAA should just interface to EAP, not to AAA.

Yoshihiro Ohba


> 
> - Dan
> 
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 14 October, 2003 21:03
> > To: Alper Yegin
> > Cc: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > Subject: Re: [Pana] [issue19] Result-Code AVP values?
> >
> >
> > There are already three authentication results defined, i.e.,
> > PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
> > PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
> > PANA_REALM_NOT_SERVED seems to be a bit inconsistent in design with
> > those three fundamental results.
> >
> > In addition, the EAP state machine draft does not have an interface to
> > AAA to obtain detailed error information like REALM_NOT_SERVED, and
> > thus in actual implementations it is likely that
> > PANA_AUTHENTICATION_REJECTED is used instead of PANA_REALM_NOT_SERVED.
> >
> > So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
> >
> > Yoshihiro Ohba
> >
> >
> > On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
> > > > In PANA we retransmit requests because we want to have reliable
> > > > transport. So, the case where the authenticator retransmits the
> > > > EAP-Request/Identity is interpreted differently in PANA layer
> > > > (retransmissions for reliability).
> > > >
> > > > The case of Notification Request is usable, but what does
> > > > "invalid authentication attempt" mean? Can we interpret it such
> > > > a way that it means "typo in the identity, user part" or "user
> > > > not recognized" or "realm not served"..
> > >
> > > Good points, but that does not mean they are problems for
> > PANA to solve.
> > >
> > > Generally I'm concerned about leaking EAP-layer events or
> > actions into PANA.
> > > But I think in this case, this is more of mapping an EAP lower-layer
> > > (Diameter) event to PANA. While I wouldn't simply import
> > all such events
> > > from one to another, I think this one might be useful and
> > not disruptive. On
> > > the other hand, this error message is different from all
> > the others. Those
> > > are all PANA-specific.
> > >
> > > Hmmm... Does anyone else care to comment on this?
> > >
> > > Alper
> > >
> > >
> > > >
> > > > A result code in PANA for this (borrowed from Diameter) is clear
> > > > and works if the authenticator implementation doesn't support
> > > > this MAY part of the EAP doc.
> > > >
> > > > - Dan
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > > >> Sent: 07 October, 2003 20:55
> > > >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > > >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > > >>
> > > >>
> > > >>>> I think this is also an EAP question. What would be the EAP
> > > >>>> behavior when
> > > >>>> the NAS cannot recognize the EAP client identifier?
> > > >>
> > > >> I think this case would be handled by the following text from
> > > >> the EAP spec:
> > > >>
> > > >>          Implementation Note: The peer MAY obtain the
> > > >> Identity via user
> > > >>          input.  It is suggested that the authenticator retry the
> > > >>          Identity Request in the case of an invalid Identity or
> > > >>          authentication failure to allow for potential typos
> > > >> on the part
> > > >>          of the user.  It is suggested that the Identity
> > Request be
> > > >>          retried a minimum of 3 times before terminating the
> > > >>          authentication.  The Notification Request MAY be used to
> > > >>          indicate an invalid authentication attempt prior to
> > > >>          transmitting a new Identity Request
> > (optionally, the failure
> > > >>          MAY be indicated within the message of the new
> > > >> Identity Request
> > > >>          itself).
> > > >>
> > > >> ... And finally I think the EAP authenticator would send a
> > > >> Failure message.
> > > >>
> > > >> 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-admin@ietf.org  Wed Oct 15 12:41:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08476
	for <pana-archive@lists.ietf.org>; Wed, 15 Oct 2003 12:41:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ohp-0003KS-4y; Wed, 15 Oct 2003 12:41:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ohB-0003AY-EV
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 12:40:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08424
	for <pana@ietf.org>; Wed, 15 Oct 2003 12:40:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oh9-0007C5-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:40:19 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oh8-0007Bt-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:40:19 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9FGeGF1016282;
	Thu, 16 Oct 2003 01:40:16 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9FGeGsg003587;
	Thu, 16 Oct 2003 01:40:16 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA03586 ; Thu, 16 Oct 2003 01:40:16 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA03218; Thu, 16 Oct 2003 01:40:16 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA18880; Thu, 16 Oct 2003 01:40:15 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9FGeFib015711;
	Thu, 16 Oct 2003 01:40:15 +0900 (JST)
Received: from steelhead ([159.119.168.137]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMT002034Z1TU@tsbpo1.po.toshiba.co.jp>; Thu,
 16 Oct 2003 01:40:14 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9ofv-0002Iv-00; Wed, 15 Oct 2003 09:39:03 -0700
Date: Wed, 15 Oct 2003 09:39:03 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5AC@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031015163903.GC8002@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5AC@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Dan,

On Wed, Oct 15, 2003 at 11:47:18AM +0300, Dan.Forsberg@nokia.com wrote:
> >
> > The issue we are discussing is: which PANA message should carry the
> > initial EAP Request/Identity and here is my suggestion: 
> >
> >   "When a Cookie-AVP is carried in a PANA-Start-Request message, the
> >   initial EAP Request MUST NOT be carried in the PANA-Start-Request
> >   message in order for the PAA to be stateful.
> 
> I don't think that the Cookie makes PAA necessarily stateful. PAA could
> use a timestamp and a hash of PaC's address, encrypt that with a secret 
> key and use it as a cookie. When PAA checks the cookie, it decrypts it 
> and checks the timestamp and address hash. No state required. I'm not a 
> cookie expert, though.

Sorry, that is a typo, "stateful" should read "stateless".

> 
> >
> >   When a Cookie-AVP is not carried in a PANA-Start-Request message,
> >   the PAA does not need to be stateful.  In this case, the initial EAP

This is the same typo, "stateful" should read "stateless".

> >   Request message MAY be carried in the PANA-Start-Request message.
> >   If the initial EAP Request message is carried in the
> >   PANA-Start-Request message, an EAP Response message MUST be carried
> >   in the PANA-Start-Answer message returned to the PAA.
> >  
> >   In any case, PANA MUST NOT generate an EAP message on behalf of
> >   EAP peer or EAP authenticator."
> 
> Just for clarification and for easier understanding what about: 
>    "In any case, PANA MUST NOT generate an EAP message on behalf of
>     EAP peer or EAP (passthrough) authenticator."

OK.

> 
> >
> > I think this allows saving one round trip when PAA does not need to be
> > stateless.
> 
> Ok, but I don't fully agree about the separation of Cookie and EAP-Request. 
> See the comment above.


After fixing the typo, I guess we are in agreement.

Yoshihiro Ohba


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


From exim@www1.ietf.org  Wed Oct 15 12:41:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08490
	for <pana-archive@odin.ietf.org>; Wed, 15 Oct 2003 12:41:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ohs-0003Mn-Vt
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 12:41:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9FGf4mx012935
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 12:41:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ohs-0003MY-QR
	for pana-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 12:41:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08450
	for <pana-web-archive@ietf.org>; Wed, 15 Oct 2003 12:40:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ohr-0007Cm-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 12:41:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ohq-0007Cj-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 12:41:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ohp-0003KS-4y; Wed, 15 Oct 2003 12:41:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ohB-0003AY-EV
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 12:40:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08424
	for <pana@ietf.org>; Wed, 15 Oct 2003 12:40:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oh9-0007C5-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:40:19 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oh8-0007Bt-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:40:19 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9FGeGF1016282;
	Thu, 16 Oct 2003 01:40:16 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9FGeGsg003587;
	Thu, 16 Oct 2003 01:40:16 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA03586 ; Thu, 16 Oct 2003 01:40:16 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA03218; Thu, 16 Oct 2003 01:40:16 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA18880; Thu, 16 Oct 2003 01:40:15 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9FGeFib015711;
	Thu, 16 Oct 2003 01:40:15 +0900 (JST)
Received: from steelhead ([159.119.168.137]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMT002034Z1TU@tsbpo1.po.toshiba.co.jp>; Thu,
 16 Oct 2003 01:40:14 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9ofv-0002Iv-00; Wed, 15 Oct 2003 09:39:03 -0700
Date: Wed, 15 Oct 2003 09:39:03 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5AC@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031015163903.GC8002@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5AC@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Dan,

On Wed, Oct 15, 2003 at 11:47:18AM +0300, Dan.Forsberg@nokia.com wrote:
> >
> > The issue we are discussing is: which PANA message should carry the
> > initial EAP Request/Identity and here is my suggestion: 
> >
> >   "When a Cookie-AVP is carried in a PANA-Start-Request message, the
> >   initial EAP Request MUST NOT be carried in the PANA-Start-Request
> >   message in order for the PAA to be stateful.
> 
> I don't think that the Cookie makes PAA necessarily stateful. PAA could
> use a timestamp and a hash of PaC's address, encrypt that with a secret 
> key and use it as a cookie. When PAA checks the cookie, it decrypts it 
> and checks the timestamp and address hash. No state required. I'm not a 
> cookie expert, though.

Sorry, that is a typo, "stateful" should read "stateless".

> 
> >
> >   When a Cookie-AVP is not carried in a PANA-Start-Request message,
> >   the PAA does not need to be stateful.  In this case, the initial EAP

This is the same typo, "stateful" should read "stateless".

> >   Request message MAY be carried in the PANA-Start-Request message.
> >   If the initial EAP Request message is carried in the
> >   PANA-Start-Request message, an EAP Response message MUST be carried
> >   in the PANA-Start-Answer message returned to the PAA.
> >  
> >   In any case, PANA MUST NOT generate an EAP message on behalf of
> >   EAP peer or EAP authenticator."
> 
> Just for clarification and for easier understanding what about: 
>    "In any case, PANA MUST NOT generate an EAP message on behalf of
>     EAP peer or EAP (passthrough) authenticator."

OK.

> 
> >
> > I think this allows saving one round trip when PAA does not need to be
> > stateless.
> 
> Ok, but I don't fully agree about the separation of Cookie and EAP-Request. 
> See the comment above.


After fixing the typo, I guess we are in agreement.

Yoshihiro Ohba


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



From pana-admin@ietf.org  Wed Oct 15 12:55:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09022
	for <pana-archive@lists.ietf.org>; Wed, 15 Oct 2003 12:55:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ovO-00047k-D5; Wed, 15 Oct 2003 12:55:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9oud-00044L-HE
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 12:54:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08953
	for <pana@ietf.org>; Wed, 15 Oct 2003 12:54:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oub-0007N9-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:54:13 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oua-0007N5-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:54:12 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9FGsAF1020303;
	Thu, 16 Oct 2003 01:54:10 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9FGsATK008648;
	Thu, 16 Oct 2003 01:54:10 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA08646 ; Thu, 16 Oct 2003 01:54:10 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA07069; Thu, 16 Oct 2003 01:54:09 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA24348; Thu, 16 Oct 2003 01:54:08 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9FGs8ib017705;
	Thu, 16 Oct 2003 01:54:08 +0900 (JST)
Received: from steelhead ([159.119.168.137]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMT0023X5M6YC@tsbpo1.po.toshiba.co.jp>; Thu,
 16 Oct 2003 01:54:07 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9ote-0002KS-00; Wed, 15 Oct 2003 09:53:14 -0700
Date: Wed, 15 Oct 2003 09:53:14 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue 23 and 25
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D73@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031015165314.GE8002@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D73@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Wed, Oct 15, 2003 at 11:07:59AM +0300, Dan.Forsberg@nokia.com wrote:
> I mean the same code space, but different numbers so that 
> overlapping is not happening when processing PANA and AAA 
> messages at the same application level.
> - Dan

That also works for me, as long as the same rule consistently applies
to both PANA message types and PANA AVP types.

Yoshihiro Ohba


> 
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 14 October, 2003 21:18
> > To: Forsberg Dan (NRC/Helsinki)
> > Cc: yohba@tari.toshiba.com; pana@ietf.org
> > Subject: Re: [Pana] issue 23 and 25
> >
> >
> > On Tue, Oct 14, 2003 at 02:23:19PM +0300,
> > Dan.Forsberg@nokia.com wrote:
> > > > -----Original Message-----
> > > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: 14 October, 2003 00:28
> > > > To: pana@ietf.org
> > > > Subject: [Pana] issue 23 and 25
> > > >
> > > >
> > > > There are two PANA draft -01 issues for which I'm not
> > sure about the
> > > > consensus.
> > > >
> > > > Issue 23: PANA Message type/AVP numbers and Diameter command
> > > > codes/AVPs
> > >
> > > Let me give some background for this issue, since I submitted it.
> > >
> > > One approach is that a NAS supports PANA functionality. A NAS
> > > can be a Diameter/Radius client. To better support
> > interworking with the
> > > PANA and NAS functionality, it would be good to distinguish
> > the command
> > > code and message type numbers. This way for example PANA
> > message header
> > > parsing functionality can be added to a NAS almost as "link
> > layer" and
> > > the PANA session handling functionality can be "migrated"
> > into the NAS.
> >
> > This seems to suggest using different code space for Diameter command
> > codes and PANA message types, right?  What about using different code
> > space for Diameter AVP types and PANA AVP types?  I think the same
> > justification is also applicable to PANA AVP types.
> >
> > Yoshihiro Ohba
> > 

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


From exim@www1.ietf.org  Wed Oct 15 12:55:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09037
	for <pana-archive@odin.ietf.org>; Wed, 15 Oct 2003 12:55:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ovS-00049N-Fm
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 12:55:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9FGt6x5015952
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 12:55:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ovS-00049C-8d
	for pana-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 12:55:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09006
	for <pana-web-archive@ietf.org>; Wed, 15 Oct 2003 12:54:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ovQ-0007Nr-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 12:55:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9ovQ-0007No-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 12:55:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9ovO-00047k-D5; Wed, 15 Oct 2003 12:55:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9oud-00044L-HE
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 12:54:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08953
	for <pana@ietf.org>; Wed, 15 Oct 2003 12:54:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oub-0007N9-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:54:13 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9oua-0007N5-00
	for pana@ietf.org; Wed, 15 Oct 2003 12:54:12 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9FGsAF1020303;
	Thu, 16 Oct 2003 01:54:10 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9FGsATK008648;
	Thu, 16 Oct 2003 01:54:10 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA08646 ; Thu, 16 Oct 2003 01:54:10 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA07069; Thu, 16 Oct 2003 01:54:09 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA24348; Thu, 16 Oct 2003 01:54:08 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9FGs8ib017705;
	Thu, 16 Oct 2003 01:54:08 +0900 (JST)
Received: from steelhead ([159.119.168.137]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMT0023X5M6YC@tsbpo1.po.toshiba.co.jp>; Thu,
 16 Oct 2003 01:54:07 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1A9ote-0002KS-00; Wed, 15 Oct 2003 09:53:14 -0700
Date: Wed, 15 Oct 2003 09:53:14 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue 23 and 25
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D73@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031015165314.GE8002@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D73@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Wed, Oct 15, 2003 at 11:07:59AM +0300, Dan.Forsberg@nokia.com wrote:
> I mean the same code space, but different numbers so that 
> overlapping is not happening when processing PANA and AAA 
> messages at the same application level.
> - Dan

That also works for me, as long as the same rule consistently applies
to both PANA message types and PANA AVP types.

Yoshihiro Ohba


> 
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 14 October, 2003 21:18
> > To: Forsberg Dan (NRC/Helsinki)
> > Cc: yohba@tari.toshiba.com; pana@ietf.org
> > Subject: Re: [Pana] issue 23 and 25
> >
> >
> > On Tue, Oct 14, 2003 at 02:23:19PM +0300,
> > Dan.Forsberg@nokia.com wrote:
> > > > -----Original Message-----
> > > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: 14 October, 2003 00:28
> > > > To: pana@ietf.org
> > > > Subject: [Pana] issue 23 and 25
> > > >
> > > >
> > > > There are two PANA draft -01 issues for which I'm not
> > sure about the
> > > > consensus.
> > > >
> > > > Issue 23: PANA Message type/AVP numbers and Diameter command
> > > > codes/AVPs
> > >
> > > Let me give some background for this issue, since I submitted it.
> > >
> > > One approach is that a NAS supports PANA functionality. A NAS
> > > can be a Diameter/Radius client. To better support
> > interworking with the
> > > PANA and NAS functionality, it would be good to distinguish
> > the command
> > > code and message type numbers. This way for example PANA
> > message header
> > > parsing functionality can be added to a NAS almost as "link
> > layer" and
> > > the PANA session handling functionality can be "migrated"
> > into the NAS.
> >
> > This seems to suggest using different code space for Diameter command
> > codes and PANA message types, right?  What about using different code
> > space for Diameter AVP types and PANA AVP types?  I think the same
> > justification is also applicable to PANA AVP types.
> >
> > Yoshihiro Ohba
> > 

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



From pana-admin@ietf.org  Wed Oct 15 14:24:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14547
	for <pana-archive@lists.ietf.org>; Wed, 15 Oct 2003 14:24:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9qJU-0000gt-Tq; Wed, 15 Oct 2003 14:24:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9qIp-0000fh-Pj
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 14:23:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14449
	for <pana@ietf.org>; Wed, 15 Oct 2003 14:23:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9qIn-0001Mk-00
	for pana@ietf.org; Wed, 15 Oct 2003 14:23:17 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9qIm-0001Mb-00
	for pana@ietf.org; Wed, 15 Oct 2003 14:23:16 -0400
Date: Wed, 15 Oct 2003 11:23:09 -0700
Subject: Re: [Pana] issue 23 and 25
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <Dan.Forsberg@nokia.com>
CC: <pana@ietf.org>
Message-ID: <BBB2DE9D.A85A%alper@docomolabs-usa.com>
In-Reply-To: <20031015165314.GE8002@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



First it was using the same codes for both PANA and Diameter. Now it is
using non-overlapping codes. I still don't see why we have to care about
these, and unnecessarily constraint ourselves. These two are separate
protocols. If a process uses both protocols, it better know what protocol a
received message belongs to.

Alper


> On Wed, Oct 15, 2003 at 11:07:59AM +0300, Dan.Forsberg@nokia.com wrote:
>> I mean the same code space, but different numbers so that
>> overlapping is not happening when processing PANA and AAA
>> messages at the same application level.
>> - Dan
> 
> That also works for me, as long as the same rule consistently applies
> to both PANA message types and PANA AVP types.
> 
> Yoshihiro Ohba
> 
> 
>> 
>>> -----Original Message-----
>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>> Sent: 14 October, 2003 21:18
>>> To: Forsberg Dan (NRC/Helsinki)
>>> Cc: yohba@tari.toshiba.com; pana@ietf.org
>>> Subject: Re: [Pana] issue 23 and 25
>>> 
>>> 
>>> On Tue, Oct 14, 2003 at 02:23:19PM +0300,
>>> Dan.Forsberg@nokia.com wrote:
>>>>> -----Original Message-----
>>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>>>> Sent: 14 October, 2003 00:28
>>>>> To: pana@ietf.org
>>>>> Subject: [Pana] issue 23 and 25
>>>>> 
>>>>> 
>>>>> There are two PANA draft -01 issues for which I'm not
>>> sure about the
>>>>> consensus.
>>>>> 
>>>>> Issue 23: PANA Message type/AVP numbers and Diameter command
>>>>> codes/AVPs
>>>> 
>>>> Let me give some background for this issue, since I submitted it.
>>>> 
>>>> One approach is that a NAS supports PANA functionality. A NAS
>>>> can be a Diameter/Radius client. To better support
>>> interworking with the
>>>> PANA and NAS functionality, it would be good to distinguish
>>> the command
>>>> code and message type numbers. This way for example PANA
>>> message header
>>>> parsing functionality can be added to a NAS almost as "link
>>> layer" and
>>>> the PANA session handling functionality can be "migrated"
>>> into the NAS.
>>> 
>>> This seems to suggest using different code space for Diameter command
>>> codes and PANA message types, right?  What about using different code
>>> space for Diameter AVP types and PANA AVP types?  I think the same
>>> justification is also applicable to PANA AVP types.
>>> 
>>> Yoshihiro Ohba
>>> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 


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


From exim@www1.ietf.org  Wed Oct 15 14:24:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14562
	for <pana-archive@odin.ietf.org>; Wed, 15 Oct 2003 14:24:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9qJZ-0000hY-DA
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 14:24:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9FIO52e002693
	for pana-archive@odin.ietf.org; Wed, 15 Oct 2003 14:24:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9qJZ-0000hM-7b
	for pana-web-archive@optimus.ietf.org; Wed, 15 Oct 2003 14:24:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14520
	for <pana-web-archive@ietf.org>; Wed, 15 Oct 2003 14:23:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9qJW-0001Ng-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 14:24:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9qJW-0001Nd-00
	for pana-web-archive@ietf.org; Wed, 15 Oct 2003 14:24:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9qJU-0000gt-Tq; Wed, 15 Oct 2003 14:24:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A9qIp-0000fh-Pj
	for pana@optimus.ietf.org; Wed, 15 Oct 2003 14:23:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14449
	for <pana@ietf.org>; Wed, 15 Oct 2003 14:23:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9qIn-0001Mk-00
	for pana@ietf.org; Wed, 15 Oct 2003 14:23:17 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A9qIm-0001Mb-00
	for pana@ietf.org; Wed, 15 Oct 2003 14:23:16 -0400
Date: Wed, 15 Oct 2003 11:23:09 -0700
Subject: Re: [Pana] issue 23 and 25
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <Dan.Forsberg@nokia.com>
CC: <pana@ietf.org>
Message-ID: <BBB2DE9D.A85A%alper@docomolabs-usa.com>
In-Reply-To: <20031015165314.GE8002@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



First it was using the same codes for both PANA and Diameter. Now it is
using non-overlapping codes. I still don't see why we have to care about
these, and unnecessarily constraint ourselves. These two are separate
protocols. If a process uses both protocols, it better know what protocol a
received message belongs to.

Alper


> On Wed, Oct 15, 2003 at 11:07:59AM +0300, Dan.Forsberg@nokia.com wrote:
>> I mean the same code space, but different numbers so that
>> overlapping is not happening when processing PANA and AAA
>> messages at the same application level.
>> - Dan
> 
> That also works for me, as long as the same rule consistently applies
> to both PANA message types and PANA AVP types.
> 
> Yoshihiro Ohba
> 
> 
>> 
>>> -----Original Message-----
>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>> Sent: 14 October, 2003 21:18
>>> To: Forsberg Dan (NRC/Helsinki)
>>> Cc: yohba@tari.toshiba.com; pana@ietf.org
>>> Subject: Re: [Pana] issue 23 and 25
>>> 
>>> 
>>> On Tue, Oct 14, 2003 at 02:23:19PM +0300,
>>> Dan.Forsberg@nokia.com wrote:
>>>>> -----Original Message-----
>>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>>>> Sent: 14 October, 2003 00:28
>>>>> To: pana@ietf.org
>>>>> Subject: [Pana] issue 23 and 25
>>>>> 
>>>>> 
>>>>> There are two PANA draft -01 issues for which I'm not
>>> sure about the
>>>>> consensus.
>>>>> 
>>>>> Issue 23: PANA Message type/AVP numbers and Diameter command
>>>>> codes/AVPs
>>>> 
>>>> Let me give some background for this issue, since I submitted it.
>>>> 
>>>> One approach is that a NAS supports PANA functionality. A NAS
>>>> can be a Diameter/Radius client. To better support
>>> interworking with the
>>>> PANA and NAS functionality, it would be good to distinguish
>>> the command
>>>> code and message type numbers. This way for example PANA
>>> message header
>>>> parsing functionality can be added to a NAS almost as "link
>>> layer" and
>>>> the PANA session handling functionality can be "migrated"
>>> into the NAS.
>>> 
>>> This seems to suggest using different code space for Diameter command
>>> codes and PANA message types, right?  What about using different code
>>> space for Diameter AVP types and PANA AVP types?  I think the same
>>> justification is also applicable to PANA AVP types.
>>> 
>>> Yoshihiro Ohba
>>> 
> 
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 


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



From pana-admin@ietf.org  Thu Oct 16 03:40:34 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23365
	for <pana-archive@lists.ietf.org>; Thu, 16 Oct 2003 03:40:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA2jr-0005OE-LZ; Thu, 16 Oct 2003 03:40:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA2jo-0005Ne-8k
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 03:40:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23337
	for <pana@ietf.org>; Thu, 16 Oct 2003 03:39:50 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA2jl-0001hg-00
	for pana@ietf.org; Thu, 16 Oct 2003 03:39:57 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA2jk-0001hd-00
	for pana@ietf.org; Thu, 16 Oct 2003 03:39:56 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9G7dud19721
	for <pana@ietf.org>; Thu, 16 Oct 2003 10:39:56 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6550e3abfbac158f21081@esvir01nok.ntc.nokia.com>;
 Thu, 16 Oct 2003 10:39:54 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 16 Oct 2003 10:39:54 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] [issue19] Result-Code AVP values?
Date: Thu, 16 Oct 2003 10:39:53 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5AE@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOTOPuygqUTjIcqQzSjLaq8fzpeVwAd9WsA
To: <yohba@tari.toshiba.com>
Cc: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 16 Oct 2003 07:39:54.0097 (UTC) FILETIME=[B0804E10:01C393B8]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 15 October, 2003 19:24
> To: Forsberg Dan (NRC/Helsinki)
> Cc: yohba@tari.toshiba.com; alper@docomolabs-usa.com; pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>
>
> On Wed, Oct 15, 2003 at 11:06:17AM +0300,
> Dan.Forsberg@nokia.com wrote:
> > I don't understand your arguments.
> >
> > PANA_REALM_NOT_SERVED is seen as an error code (see the
> issue19), not
> > an authentication result code. No authentication can take
> place because
> > of this error.
> >
> > This has nothing to do with EAP or? The NAS/PAA can't route the AAA
> > message because it can't find the routing info for the
> realm. EAP is
> > just carried in the AAA message (EAP-Payload AVP).
>
> OK.  I see what you mean.
>
> It would depend on the behavior of of the EAP authenticator on the NAS
> when the AAA message routing error happens.
>
> If the authenticator generate an EAP Failure, the result code should
> contain an authentication result.

How can EAP authenticator generate an error if it only passes the message 
for the AAA routing process and the error comes from the AAA routing?

[On the other thread we are discussing about using ISP and NAP identifiers. 
I think this problem relates to this discussion. We may need a similar 
error code there too (i.e. "unknown ISP/NAP identifier/realm").]

> If the authenticator generates a new EAP Request/Identity to give
> the EAP peer another chance to send a correct identity and
> no result code will be included.

How does the passthrough authenticator (NAS) know if the Identity is 
not correct when the syntax is perfect? Even the PAA/NAS may not know 
this but forwards the message to the AAA proxy/relay etc. Anyway, if the 
realm really isn't served, then the NAS/PAA receives this kind of error 
code. What happens then?

>
> (There would be another possibility: the authenticator retransmits the
> initial EAP Request/Identity, but this will not work because the EAP
> peer will retransmit the old EAP Response/Identity which contains the
> old realm that caused the AAA message routing error.)
>
> I don't see a case where a status code of a protocol error class
> is returned in the above scenarios.
>
> >
> > Do you think that this result code reveals too much for the
> PaC about
> > the network side?
>
> I believe error handling at PAA would be complicated if AAA errors are
> revealed to PANA.  PAA should just interface to EAP, not to AAA.

PANA and AAA are next to each other (or even glued together.. "upper 
layer PANA" and "lower layer PANA") and EAP is above them. Why to pass 
errors that the EAP doesn't know to the EAP? Instead AAA errors can 
be passed to PANA when necessary. EAP has limitations.

- Dan

>
> Yoshihiro Ohba
>
>
> >
> > - Dan
> >
> > > -----Original Message-----
> > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: 14 October, 2003 21:03
> > > To: Alper Yegin
> > > Cc: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > > Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > >
> > >
> > > There are already three authentication results defined, i.e.,
> > > PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
> > > PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
> > > PANA_REALM_NOT_SERVED seems to be a bit inconsistent in
> design with
> > > those three fundamental results.
> > >
> > > In addition, the EAP state machine draft does not have an
> interface to
> > > AAA to obtain detailed error information like
> REALM_NOT_SERVED, and
> > > thus in actual implementations it is likely that
> > > PANA_AUTHENTICATION_REJECTED is used instead of
> PANA_REALM_NOT_SERVED.
> > >
> > > So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > > On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
> > > > > In PANA we retransmit requests because we want to
> have reliable
> > > > > transport. So, the case where the authenticator
> retransmits the
> > > > > EAP-Request/Identity is interpreted differently in PANA layer
> > > > > (retransmissions for reliability).
> > > > >
> > > > > The case of Notification Request is usable, but what does
> > > > > "invalid authentication attempt" mean? Can we
> interpret it such
> > > > > a way that it means "typo in the identity, user part" or "user
> > > > > not recognized" or "realm not served"..
> > > >
> > > > Good points, but that does not mean they are problems for
> > > PANA to solve.
> > > >
> > > > Generally I'm concerned about leaking EAP-layer events or
> > > actions into PANA.
> > > > But I think in this case, this is more of mapping an
> EAP lower-layer
> > > > (Diameter) event to PANA. While I wouldn't simply import
> > > all such events
> > > > from one to another, I think this one might be useful and
> > > not disruptive. On
> > > > the other hand, this error message is different from all
> > > the others. Those
> > > > are all PANA-specific.
> > > >
> > > > Hmmm... Does anyone else care to comment on this?
> > > >
> > > > Alper
> > > >
> > > >
> > > > >
> > > > > A result code in PANA for this (borrowed from
> Diameter) is clear
> > > > > and works if the authenticator implementation doesn't support
> > > > > this MAY part of the EAP doc.
> > > > >
> > > > > - Dan
> > > > >
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > > > >> Sent: 07 October, 2003 20:55
> > > > >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > > > >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > > > >>
> > > > >>
> > > > >>>> I think this is also an EAP question. What would be the EAP
> > > > >>>> behavior when
> > > > >>>> the NAS cannot recognize the EAP client identifier?
> > > > >>
> > > > >> I think this case would be handled by the following text from
> > > > >> the EAP spec:
> > > > >>
> > > > >>          Implementation Note: The peer MAY obtain the
> > > > >> Identity via user
> > > > >>          input.  It is suggested that the
> authenticator retry the
> > > > >>          Identity Request in the case of an invalid
> Identity or
> > > > >>          authentication failure to allow for potential typos
> > > > >> on the part
> > > > >>          of the user.  It is suggested that the Identity
> > > Request be
> > > > >>          retried a minimum of 3 times before terminating the
> > > > >>          authentication.  The Notification Request
> MAY be used to
> > > > >>          indicate an invalid authentication attempt prior to
> > > > >>          transmitting a new Identity Request
> > > (optionally, the failure
> > > > >>          MAY be indicated within the message of the new
> > > > >> Identity Request
> > > > >>          itself).
> > > > >>
> > > > >> ... And finally I think the EAP authenticator would send a
> > > > >> Failure message.
> > > > >>
> > > > >> 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 exim@www1.ietf.org  Thu Oct 16 03:40:44 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23381
	for <pana-archive@odin.ietf.org>; Thu, 16 Oct 2003 03:40:44 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA2k8-0005QM-35
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 03:40:22 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9G7eHIV020778
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 03:40:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA2k2-0005P2-9t
	for pana-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 03:40:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23348
	for <pana-web-archive@ietf.org>; Thu, 16 Oct 2003 03:40:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA2jz-0001hu-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 03:40:11 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA2jz-0001hr-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 03:40:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA2jr-0005OE-LZ; Thu, 16 Oct 2003 03:40:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA2jo-0005Ne-8k
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 03:40:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23337
	for <pana@ietf.org>; Thu, 16 Oct 2003 03:39:50 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA2jl-0001hg-00
	for pana@ietf.org; Thu, 16 Oct 2003 03:39:57 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA2jk-0001hd-00
	for pana@ietf.org; Thu, 16 Oct 2003 03:39:56 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9G7dud19721
	for <pana@ietf.org>; Thu, 16 Oct 2003 10:39:56 +0300 (EET DST)
Received: from esebh004.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6550e3abfbac158f21081@esvir01nok.ntc.nokia.com>;
 Thu, 16 Oct 2003 10:39:54 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh004.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 16 Oct 2003 10:39:54 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] [issue19] Result-Code AVP values?
Date: Thu, 16 Oct 2003 10:39:53 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5AE@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] [issue19] Result-Code AVP values?
Thread-Index: AcOTOPuygqUTjIcqQzSjLaq8fzpeVwAd9WsA
To: <yohba@tari.toshiba.com>
Cc: <alper@docomolabs-usa.com>, <pana@ietf.org>
X-OriginalArrivalTime: 16 Oct 2003 07:39:54.0097 (UTC) FILETIME=[B0804E10:01C393B8]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 15 October, 2003 19:24
> To: Forsberg Dan (NRC/Helsinki)
> Cc: yohba@tari.toshiba.com; alper@docomolabs-usa.com; pana@ietf.org
> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>
>
> On Wed, Oct 15, 2003 at 11:06:17AM +0300,
> Dan.Forsberg@nokia.com wrote:
> > I don't understand your arguments.
> >
> > PANA_REALM_NOT_SERVED is seen as an error code (see the
> issue19), not
> > an authentication result code. No authentication can take
> place because
> > of this error.
> >
> > This has nothing to do with EAP or? The NAS/PAA can't route the AAA
> > message because it can't find the routing info for the
> realm. EAP is
> > just carried in the AAA message (EAP-Payload AVP).
>
> OK.  I see what you mean.
>
> It would depend on the behavior of of the EAP authenticator on the NAS
> when the AAA message routing error happens.
>
> If the authenticator generate an EAP Failure, the result code should
> contain an authentication result.

How can EAP authenticator generate an error if it only passes the message 
for the AAA routing process and the error comes from the AAA routing?

[On the other thread we are discussing about using ISP and NAP identifiers. 
I think this problem relates to this discussion. We may need a similar 
error code there too (i.e. "unknown ISP/NAP identifier/realm").]

> If the authenticator generates a new EAP Request/Identity to give
> the EAP peer another chance to send a correct identity and
> no result code will be included.

How does the passthrough authenticator (NAS) know if the Identity is 
not correct when the syntax is perfect? Even the PAA/NAS may not know 
this but forwards the message to the AAA proxy/relay etc. Anyway, if the 
realm really isn't served, then the NAS/PAA receives this kind of error 
code. What happens then?

>
> (There would be another possibility: the authenticator retransmits the
> initial EAP Request/Identity, but this will not work because the EAP
> peer will retransmit the old EAP Response/Identity which contains the
> old realm that caused the AAA message routing error.)
>
> I don't see a case where a status code of a protocol error class
> is returned in the above scenarios.
>
> >
> > Do you think that this result code reveals too much for the
> PaC about
> > the network side?
>
> I believe error handling at PAA would be complicated if AAA errors are
> revealed to PANA.  PAA should just interface to EAP, not to AAA.

PANA and AAA are next to each other (or even glued together.. "upper 
layer PANA" and "lower layer PANA") and EAP is above them. Why to pass 
errors that the EAP doesn't know to the EAP? Instead AAA errors can 
be passed to PANA when necessary. EAP has limitations.

- Dan

>
> Yoshihiro Ohba
>
>
> >
> > - Dan
> >
> > > -----Original Message-----
> > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: 14 October, 2003 21:03
> > > To: Alper Yegin
> > > Cc: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > > Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > >
> > >
> > > There are already three authentication results defined, i.e.,
> > > PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
> > > PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
> > > PANA_REALM_NOT_SERVED seems to be a bit inconsistent in
> design with
> > > those three fundamental results.
> > >
> > > In addition, the EAP state machine draft does not have an
> interface to
> > > AAA to obtain detailed error information like
> REALM_NOT_SERVED, and
> > > thus in actual implementations it is likely that
> > > PANA_AUTHENTICATION_REJECTED is used instead of
> PANA_REALM_NOT_SERVED.
> > >
> > > So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > > On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
> > > > > In PANA we retransmit requests because we want to
> have reliable
> > > > > transport. So, the case where the authenticator
> retransmits the
> > > > > EAP-Request/Identity is interpreted differently in PANA layer
> > > > > (retransmissions for reliability).
> > > > >
> > > > > The case of Notification Request is usable, but what does
> > > > > "invalid authentication attempt" mean? Can we
> interpret it such
> > > > > a way that it means "typo in the identity, user part" or "user
> > > > > not recognized" or "realm not served"..
> > > >
> > > > Good points, but that does not mean they are problems for
> > > PANA to solve.
> > > >
> > > > Generally I'm concerned about leaking EAP-layer events or
> > > actions into PANA.
> > > > But I think in this case, this is more of mapping an
> EAP lower-layer
> > > > (Diameter) event to PANA. While I wouldn't simply import
> > > all such events
> > > > from one to another, I think this one might be useful and
> > > not disruptive. On
> > > > the other hand, this error message is different from all
> > > the others. Those
> > > > are all PANA-specific.
> > > >
> > > > Hmmm... Does anyone else care to comment on this?
> > > >
> > > > Alper
> > > >
> > > >
> > > > >
> > > > > A result code in PANA for this (borrowed from
> Diameter) is clear
> > > > > and works if the authenticator implementation doesn't support
> > > > > this MAY part of the EAP doc.
> > > > >
> > > > > - Dan
> > > > >
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > > > >> Sent: 07 October, 2003 20:55
> > > > >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > > > >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > > > >>
> > > > >>
> > > > >>>> I think this is also an EAP question. What would be the EAP
> > > > >>>> behavior when
> > > > >>>> the NAS cannot recognize the EAP client identifier?
> > > > >>
> > > > >> I think this case would be handled by the following text from
> > > > >> the EAP spec:
> > > > >>
> > > > >>          Implementation Note: The peer MAY obtain the
> > > > >> Identity via user
> > > > >>          input.  It is suggested that the
> authenticator retry the
> > > > >>          Identity Request in the case of an invalid
> Identity or
> > > > >>          authentication failure to allow for potential typos
> > > > >> on the part
> > > > >>          of the user.  It is suggested that the Identity
> > > Request be
> > > > >>          retried a minimum of 3 times before terminating the
> > > > >>          authentication.  The Notification Request
> MAY be used to
> > > > >>          indicate an invalid authentication attempt prior to
> > > > >>          transmitting a new Identity Request
> > > (optionally, the failure
> > > > >>          MAY be indicated within the message of the new
> > > > >> Identity Request
> > > > >>          itself).
> > > > >>
> > > > >> ... And finally I think the EAP authenticator would send a
> > > > >> Failure message.
> > > > >>
> > > > >> 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-admin@ietf.org  Thu Oct 16 04:00:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23986
	for <pana-archive@lists.ietf.org>; Thu, 16 Oct 2003 04:00:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA33C-0006XL-5f; Thu, 16 Oct 2003 04:00:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA32W-0006WE-IN
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 03:59:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23888
	for <pana@ietf.org>; Thu, 16 Oct 2003 03:59:10 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA32T-0001sB-00
	for pana@ietf.org; Thu, 16 Oct 2003 03:59:17 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA32I-0001rx-00
	for pana@ietf.org; Thu, 16 Oct 2003 03:59:16 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9G7x6X05985
	for <pana@ietf.org>; Thu, 16 Oct 2003 10:59:06 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6550f53c54ac158f24077@esvir04nok.ntc.nokia.com>;
 Thu, 16 Oct 2003 10:59:05 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 16 Oct 2003 10:59:05 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] issue 23 and 25
Date: Thu, 16 Oct 2003 10:59:05 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5AF@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] issue 23 and 25
Thread-Index: AcOTSWwqN+oxtI+6RvaarEsbfTQ4IAAb1XiA
To: <alper@docomolabs-usa.com>, <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 16 Oct 2003 07:59:05.0714 (UTC) FILETIME=[5EEB1D20:01C393BB]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

There is no first and second. PANA borrows some AVPs from=20
RADIUS/Diameter, which we don't want to change, thus the=20
same codes. PANA has it's own AVPs, which we don't want to=20
overlap with Diameter/Radius AVPs, thus same code space,=20
but non-overlapping codes. PANA has it's own message types,=20
which can be seen as command codes. These should not overlap=20
with Radius/Diameter.

The process uses two separate protocols, but benefits in=20
many ways from having synergies between the protocols. To=20
give the process a name, we can call it a AAA application.=20
AAA application uses Diameter or Radius as the transport to=20
the network and PANA towards the client. PANA has also it's=20
transport (header processing) and application level stuff=20
(session handling). There are of course other ways to see/=20
think this, but AAA session and PANA session are very close=20
to each other. PAA can't live without the AAA part. EAP is=20
a tool to handle the authentication signaling, but doesn't=20
"know" about sessions.

- Dan


> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 15 October, 2003 21:23
> To: Yoshihiro Ohba; Forsberg Dan (NRC/Helsinki)
> Cc: pana@ietf.org
> Subject: Re: [Pana] issue 23 and 25
>=20
>=20
>=20
>=20
> First it was using the same codes for both PANA and Diameter.=20
> Now it is
> using non-overlapping codes. I still don't see why we have to=20
> care about
> these, and unnecessarily constraint ourselves. These two are separate
> protocols. If a process uses both protocols, it better know=20
> what protocol a
> received message belongs to.
>=20
> Alper
>=20
>=20
> > On Wed, Oct 15, 2003 at 11:07:59AM +0300,=20
> Dan.Forsberg@nokia.com wrote:
> >> I mean the same code space, but different numbers so that
> >> overlapping is not happening when processing PANA and AAA
> >> messages at the same application level.
> >> - Dan
> >=20
> > That also works for me, as long as the same rule=20
> consistently applies
> > to both PANA message types and PANA AVP types.
> >=20
> > Yoshihiro Ohba
> >=20
> >=20
> >>=20
> >>> -----Original Message-----
> >>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> >>> Sent: 14 October, 2003 21:18
> >>> To: Forsberg Dan (NRC/Helsinki)
> >>> Cc: yohba@tari.toshiba.com; pana@ietf.org
> >>> Subject: Re: [Pana] issue 23 and 25
> >>>=20
> >>>=20
> >>> On Tue, Oct 14, 2003 at 02:23:19PM +0300,
> >>> Dan.Forsberg@nokia.com wrote:
> >>>>> -----Original Message-----
> >>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> >>>>> Sent: 14 October, 2003 00:28
> >>>>> To: pana@ietf.org
> >>>>> Subject: [Pana] issue 23 and 25
> >>>>>=20
> >>>>>=20
> >>>>> There are two PANA draft -01 issues for which I'm not
> >>> sure about the
> >>>>> consensus.
> >>>>>=20
> >>>>> Issue 23: PANA Message type/AVP numbers and Diameter command
> >>>>> codes/AVPs
> >>>>=20
> >>>> Let me give some background for this issue, since I submitted it.
> >>>>=20
> >>>> One approach is that a NAS supports PANA functionality. A NAS
> >>>> can be a Diameter/Radius client. To better support
> >>> interworking with the
> >>>> PANA and NAS functionality, it would be good to distinguish
> >>> the command
> >>>> code and message type numbers. This way for example PANA
> >>> message header
> >>>> parsing functionality can be added to a NAS almost as "link
> >>> layer" and
> >>>> the PANA session handling functionality can be "migrated"
> >>> into the NAS.
> >>>=20
> >>> This seems to suggest using different code space for=20
> Diameter command
> >>> codes and PANA message types, right?  What about using=20
> different code
> >>> space for Diameter AVP types and PANA AVP types?  I think the same
> >>> justification is also applicable to PANA AVP types.
> >>>=20
> >>> Yoshihiro Ohba
> >>>=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
>=20

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


From exim@www1.ietf.org  Thu Oct 16 04:00:36 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24006
	for <pana-archive@odin.ietf.org>; Thu, 16 Oct 2003 04:00:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA33O-0006ZT-QQ
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 04:00:15 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9G80EZi025222
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 04:00:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA33J-0006YL-Fn
	for pana-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 04:00:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23924
	for <pana-web-archive@ietf.org>; Thu, 16 Oct 2003 03:59:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA33G-0001sk-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 04:00:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA33G-0001sh-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 04:00:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA33C-0006XL-5f; Thu, 16 Oct 2003 04:00:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA32W-0006WE-IN
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 03:59:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23888
	for <pana@ietf.org>; Thu, 16 Oct 2003 03:59:10 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA32T-0001sB-00
	for pana@ietf.org; Thu, 16 Oct 2003 03:59:17 -0400
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA32I-0001rx-00
	for pana@ietf.org; Thu, 16 Oct 2003 03:59:16 -0400
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9G7x6X05985
	for <pana@ietf.org>; Thu, 16 Oct 2003 10:59:06 +0300 (EET DST)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6550f53c54ac158f24077@esvir04nok.ntc.nokia.com>;
 Thu, 16 Oct 2003 10:59:05 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 16 Oct 2003 10:59:05 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] issue 23 and 25
Date: Thu, 16 Oct 2003 10:59:05 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5AF@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] issue 23 and 25
Thread-Index: AcOTSWwqN+oxtI+6RvaarEsbfTQ4IAAb1XiA
To: <alper@docomolabs-usa.com>, <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 16 Oct 2003 07:59:05.0714 (UTC) FILETIME=[5EEB1D20:01C393BB]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

There is no first and second. PANA borrows some AVPs from=20
RADIUS/Diameter, which we don't want to change, thus the=20
same codes. PANA has it's own AVPs, which we don't want to=20
overlap with Diameter/Radius AVPs, thus same code space,=20
but non-overlapping codes. PANA has it's own message types,=20
which can be seen as command codes. These should not overlap=20
with Radius/Diameter.

The process uses two separate protocols, but benefits in=20
many ways from having synergies between the protocols. To=20
give the process a name, we can call it a AAA application.=20
AAA application uses Diameter or Radius as the transport to=20
the network and PANA towards the client. PANA has also it's=20
transport (header processing) and application level stuff=20
(session handling). There are of course other ways to see/=20
think this, but AAA session and PANA session are very close=20
to each other. PAA can't live without the AAA part. EAP is=20
a tool to handle the authentication signaling, but doesn't=20
"know" about sessions.

- Dan


> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 15 October, 2003 21:23
> To: Yoshihiro Ohba; Forsberg Dan (NRC/Helsinki)
> Cc: pana@ietf.org
> Subject: Re: [Pana] issue 23 and 25
>=20
>=20
>=20
>=20
> First it was using the same codes for both PANA and Diameter.=20
> Now it is
> using non-overlapping codes. I still don't see why we have to=20
> care about
> these, and unnecessarily constraint ourselves. These two are separate
> protocols. If a process uses both protocols, it better know=20
> what protocol a
> received message belongs to.
>=20
> Alper
>=20
>=20
> > On Wed, Oct 15, 2003 at 11:07:59AM +0300,=20
> Dan.Forsberg@nokia.com wrote:
> >> I mean the same code space, but different numbers so that
> >> overlapping is not happening when processing PANA and AAA
> >> messages at the same application level.
> >> - Dan
> >=20
> > That also works for me, as long as the same rule=20
> consistently applies
> > to both PANA message types and PANA AVP types.
> >=20
> > Yoshihiro Ohba
> >=20
> >=20
> >>=20
> >>> -----Original Message-----
> >>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> >>> Sent: 14 October, 2003 21:18
> >>> To: Forsberg Dan (NRC/Helsinki)
> >>> Cc: yohba@tari.toshiba.com; pana@ietf.org
> >>> Subject: Re: [Pana] issue 23 and 25
> >>>=20
> >>>=20
> >>> On Tue, Oct 14, 2003 at 02:23:19PM +0300,
> >>> Dan.Forsberg@nokia.com wrote:
> >>>>> -----Original Message-----
> >>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> >>>>> Sent: 14 October, 2003 00:28
> >>>>> To: pana@ietf.org
> >>>>> Subject: [Pana] issue 23 and 25
> >>>>>=20
> >>>>>=20
> >>>>> There are two PANA draft -01 issues for which I'm not
> >>> sure about the
> >>>>> consensus.
> >>>>>=20
> >>>>> Issue 23: PANA Message type/AVP numbers and Diameter command
> >>>>> codes/AVPs
> >>>>=20
> >>>> Let me give some background for this issue, since I submitted it.
> >>>>=20
> >>>> One approach is that a NAS supports PANA functionality. A NAS
> >>>> can be a Diameter/Radius client. To better support
> >>> interworking with the
> >>>> PANA and NAS functionality, it would be good to distinguish
> >>> the command
> >>>> code and message type numbers. This way for example PANA
> >>> message header
> >>>> parsing functionality can be added to a NAS almost as "link
> >>> layer" and
> >>>> the PANA session handling functionality can be "migrated"
> >>> into the NAS.
> >>>=20
> >>> This seems to suggest using different code space for=20
> Diameter command
> >>> codes and PANA message types, right?  What about using=20
> different code
> >>> space for Diameter AVP types and PANA AVP types?  I think the same
> >>> justification is also applicable to PANA AVP types.
> >>>=20
> >>> Yoshihiro Ohba
> >>>=20
> >=20
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> >=20
>=20
>=20

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



From pana-admin@ietf.org  Thu Oct 16 04:13:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24432
	for <pana-archive@lists.ietf.org>; Thu, 16 Oct 2003 04:13:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA3Fl-0007i9-PI; Thu, 16 Oct 2003 04:13:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA3Er-0007ZP-Ic
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 04:12:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24364
	for <pana@ietf.org>; Thu, 16 Oct 2003 04:11:54 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA3En-00021B-00
	for pana@ietf.org; Thu, 16 Oct 2003 04:12:01 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA3Em-000215-00
	for pana@ietf.org; Thu, 16 Oct 2003 04:12:01 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9G8C0d26772
	for <pana@ietf.org>; Thu, 16 Oct 2003 11:12:00 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6551010de4ac158f21081@esvir01nok.ntc.nokia.com>;
 Thu, 16 Oct 2003 11:12:00 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 16 Oct 2003 11:11:59 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Thu, 16 Oct 2003 11:11:58 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D7C@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] EAP-Request/Identity & PANA-Start-Request
Thread-Index: AcOTOysZuzEVmYxgRGekFZxh9ytDewAgJcOw
To: <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 16 Oct 2003 08:11:59.0246 (UTC) FILETIME=[2BFABAE0:01C393BD]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Yoshi,

I don't know the EAP state machines, but I guess they are 
intepretations of the EAP protocol specification. 

You said that EAP-Request/Response Identity message exchange 
is optional. This seems to imply that the EAP authenticator
does not have to be stateful during identity "discovery"?
How does the authenticator skip the identity request/response 
part when the identity is known outside EAP already?

This is why I can't see your separation to stateless or 
stateful.

- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 15 October, 2003 19:39
> To: Forsberg Dan (NRC/Helsinki)
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
>
>
> Hi Dan,
>
> On Wed, Oct 15, 2003 at 11:47:18AM +0300,
> Dan.Forsberg@nokia.com wrote:
> > >
> > > The issue we are discussing is: which PANA message should
> carry the
> > > initial EAP Request/Identity and here is my suggestion:
> > >
> > >   "When a Cookie-AVP is carried in a PANA-Start-Request
> message, the
> > >   initial EAP Request MUST NOT be carried in the
> PANA-Start-Request
> > >   message in order for the PAA to be stateful.
> >
> > I don't think that the Cookie makes PAA necessarily
> stateful. PAA could
> > use a timestamp and a hash of PaC's address, encrypt that
> with a secret
> > key and use it as a cookie. When PAA checks the cookie, it
> decrypts it
> > and checks the timestamp and address hash. No state
> required. I'm not a
> > cookie expert, though.
>
> Sorry, that is a typo, "stateful" should read "stateless".
>
> >
> > >
> > >   When a Cookie-AVP is not carried in a
> PANA-Start-Request message,
> > >   the PAA does not need to be stateful.  In this case,
> the initial EAP
>
> This is the same typo, "stateful" should read "stateless".
>
> > >   Request message MAY be carried in the
> PANA-Start-Request message.
> > >   If the initial EAP Request message is carried in the
> > >   PANA-Start-Request message, an EAP Response message
> MUST be carried
> > >   in the PANA-Start-Answer message returned to the PAA.
> > > 
> > >   In any case, PANA MUST NOT generate an EAP message on behalf of
> > >   EAP peer or EAP authenticator."
> >
> > Just for clarification and for easier understanding what about:
> >    "In any case, PANA MUST NOT generate an EAP message on behalf of
> >     EAP peer or EAP (passthrough) authenticator."
>
> OK.
>
> >
> > >
> > > I think this allows saving one round trip when PAA does
> not need to be
> > > stateless.
> >
> > Ok, but I don't fully agree about the separation of Cookie
> and EAP-Request.
> > See the comment above.
>
>
> After fixing the typo, I guess we are in agreement.
>
> Yoshihiro Ohba
>
>
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 

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


From exim@www1.ietf.org  Thu Oct 16 04:13:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24447
	for <pana-archive@odin.ietf.org>; Thu, 16 Oct 2003 04:13:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA3Fq-0007jq-Q6
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 04:13:07 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9G8D6Na029740
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 04:13:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA3Fp-0007iZ-8H
	for pana-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 04:13:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24417
	for <pana-web-archive@ietf.org>; Thu, 16 Oct 2003 04:12:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA3Fm-00021n-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 04:13:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA3Fm-00021k-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 04:13:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA3Fl-0007i9-PI; Thu, 16 Oct 2003 04:13:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AA3Er-0007ZP-Ic
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 04:12:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24364
	for <pana@ietf.org>; Thu, 16 Oct 2003 04:11:54 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA3En-00021B-00
	for pana@ietf.org; Thu, 16 Oct 2003 04:12:01 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AA3Em-000215-00
	for pana@ietf.org; Thu, 16 Oct 2003 04:12:01 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9G8C0d26772
	for <pana@ietf.org>; Thu, 16 Oct 2003 11:12:00 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6551010de4ac158f21081@esvir01nok.ntc.nokia.com>;
 Thu, 16 Oct 2003 11:12:00 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Thu, 16 Oct 2003 11:11:59 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Subject: RE: [Pana] EAP-Request/Identity & PANA-Start-Request
Date: Thu, 16 Oct 2003 11:11:58 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D7C@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] EAP-Request/Identity & PANA-Start-Request
Thread-Index: AcOTOysZuzEVmYxgRGekFZxh9ytDewAgJcOw
To: <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 16 Oct 2003 08:11:59.0246 (UTC) FILETIME=[2BFABAE0:01C393BD]
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Yoshi,

I don't know the EAP state machines, but I guess they are 
intepretations of the EAP protocol specification. 

You said that EAP-Request/Response Identity message exchange 
is optional. This seems to imply that the EAP authenticator
does not have to be stateful during identity "discovery"?
How does the authenticator skip the identity request/response 
part when the identity is known outside EAP already?

This is why I can't see your separation to stateless or 
stateful.

- Dan

> -----Original Message-----
> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: 15 October, 2003 19:39
> To: Forsberg Dan (NRC/Helsinki)
> Cc: yohba@tari.toshiba.com; pana@ietf.org
> Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
>
>
> Hi Dan,
>
> On Wed, Oct 15, 2003 at 11:47:18AM +0300,
> Dan.Forsberg@nokia.com wrote:
> > >
> > > The issue we are discussing is: which PANA message should
> carry the
> > > initial EAP Request/Identity and here is my suggestion:
> > >
> > >   "When a Cookie-AVP is carried in a PANA-Start-Request
> message, the
> > >   initial EAP Request MUST NOT be carried in the
> PANA-Start-Request
> > >   message in order for the PAA to be stateful.
> >
> > I don't think that the Cookie makes PAA necessarily
> stateful. PAA could
> > use a timestamp and a hash of PaC's address, encrypt that
> with a secret
> > key and use it as a cookie. When PAA checks the cookie, it
> decrypts it
> > and checks the timestamp and address hash. No state
> required. I'm not a
> > cookie expert, though.
>
> Sorry, that is a typo, "stateful" should read "stateless".
>
> >
> > >
> > >   When a Cookie-AVP is not carried in a
> PANA-Start-Request message,
> > >   the PAA does not need to be stateful.  In this case,
> the initial EAP
>
> This is the same typo, "stateful" should read "stateless".
>
> > >   Request message MAY be carried in the
> PANA-Start-Request message.
> > >   If the initial EAP Request message is carried in the
> > >   PANA-Start-Request message, an EAP Response message
> MUST be carried
> > >   in the PANA-Start-Answer message returned to the PAA.
> > > 
> > >   In any case, PANA MUST NOT generate an EAP message on behalf of
> > >   EAP peer or EAP authenticator."
> >
> > Just for clarification and for easier understanding what about:
> >    "In any case, PANA MUST NOT generate an EAP message on behalf of
> >     EAP peer or EAP (passthrough) authenticator."
>
> OK.
>
> >
> > >
> > > I think this allows saving one round trip when PAA does
> not need to be
> > > stateless.
> >
> > Ok, but I don't fully agree about the separation of Cookie
> and EAP-Request.
> > See the comment above.
>
>
> After fixing the typo, I guess we are in agreement.
>
> Yoshihiro Ohba
>
>
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
> 

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



From pana-admin@ietf.org  Thu Oct 16 12:14:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08485
	for <pana-archive@lists.ietf.org>; Thu, 16 Oct 2003 12:14:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAAlF-000317-6I; Thu, 16 Oct 2003 12:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAAkU-00030D-Fl
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 12:13:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08465
	for <pana@ietf.org>; Thu, 16 Oct 2003 12:13:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAAkT-0006Iz-00
	for pana@ietf.org; Thu, 16 Oct 2003 12:13:13 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAAkS-0006Iq-00
	for pana@ietf.org; Thu, 16 Oct 2003 12:13:12 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9GGD5F1019831;
	Fri, 17 Oct 2003 01:13:05 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9GGD5Fg012534;
	Fri, 17 Oct 2003 01:13:05 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA12533 ; Fri, 17 Oct 2003 01:13:05 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA13895; Fri, 17 Oct 2003 01:13:04 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA23483; Fri, 17 Oct 2003 01:13:02 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9GGD1ib002356;
	Fri, 17 Oct 2003 01:13:01 +0900 (JST)
Received: from steelhead ([159.119.168.101]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMU00E49YDNC8@tsbpo1.po.toshiba.co.jp>; Fri,
 17 Oct 2003 01:13:00 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAAk5-0003b0-00; Thu, 16 Oct 2003 09:12:49 -0700
Date: Thu, 16 Oct 2003 09:12:49 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue19] Result-Code AVP values?
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5AE@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, alper@docomolabs-usa.com, pana@ietf.org
Message-id: <20031016161249.GA13220@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com,
 alper@docomolabs-usa.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5AE@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

I believe the issues you have addressed below are for Diameter EAP
application draft and EAP state machines.  As far as I know, when an
AAA message routing error occurs, the EAP authenticator on the NAS
will not receive any EAP message or a signal from AAA.  Instead, it
relies on a timeout event generated by itself ("aaaTimeout" variable
is defined in the EAP full authenticator state machine).  When the
timeout occurs, the EAP authenticator enters a final state
TIMEOUT_FAILURE2 with setting eapTimout = TRUE but without generating
an EAP Failure (This is a mandatory behavior defined in RFC3579).  

So the EAP authenticator on the NAS may not be able to generate any
EAP message when the AAA message routing error occurs.  

I would suggest creating a new PANA issue on how to handle the case in
which an EAP authenticator on the NAS fails to authenticate an EAP
peer without generating an EAP message.  We can continue the
discussion on whether AAA error needs to be leaked to PANA in the new
issue.

Can we close issue19?

Yoshihiro Ohba


On Thu, Oct 16, 2003 at 10:39:53AM +0300, Dan.Forsberg@nokia.com wrote:
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 15 October, 2003 19:24
> > To: Forsberg Dan (NRC/Helsinki)
> > Cc: yohba@tari.toshiba.com; alper@docomolabs-usa.com; pana@ietf.org
> > Subject: Re: [Pana] [issue19] Result-Code AVP values?
> >
> >
> > On Wed, Oct 15, 2003 at 11:06:17AM +0300,
> > Dan.Forsberg@nokia.com wrote:
> > > I don't understand your arguments.
> > >
> > > PANA_REALM_NOT_SERVED is seen as an error code (see the
> > issue19), not
> > > an authentication result code. No authentication can take
> > place because
> > > of this error.
> > >
> > > This has nothing to do with EAP or? The NAS/PAA can't route the AAA
> > > message because it can't find the routing info for the
> > realm. EAP is
> > > just carried in the AAA message (EAP-Payload AVP).
> >
> > OK.  I see what you mean.
> >
> > It would depend on the behavior of of the EAP authenticator on the NAS
> > when the AAA message routing error happens.
> >
> > If the authenticator generate an EAP Failure, the result code should
> > contain an authentication result.
> 
> How can EAP authenticator generate an error if it only passes the message 
> for the AAA routing process and the error comes from the AAA routing?

> 
> [On the other thread we are discussing about using ISP and NAP identifiers. 
> I think this problem relates to this discussion. We may need a similar 
> error code there too (i.e. "unknown ISP/NAP identifier/realm").]
> 
> > If the authenticator generates a new EAP Request/Identity to give
> > the EAP peer another chance to send a correct identity and
> > no result code will be included.
> 
> How does the passthrough authenticator (NAS) know if the Identity is 
> not correct when the syntax is perfect? Even the PAA/NAS may not know 
\> this but forwards the message to the AAA proxy/relay etc. Anyway, if the 
> realm really isn't served, then the NAS/PAA receives this kind of error 
> code. What happens then?
> 
> >
> > (There would be another possibility: the authenticator retransmits the
> > initial EAP Request/Identity, but this will not work because the EAP
> > peer will retransmit the old EAP Response/Identity which contains the
> > old realm that caused the AAA message routing error.)
> >
> > I don't see a case where a status code of a protocol error class
> > is returned in the above scenarios.
> >
> > >
> > > Do you think that this result code reveals too much for the
> > PaC about
> > > the network side?
> >
> > I believe error handling at PAA would be complicated if AAA errors are
> > revealed to PANA.  PAA should just interface to EAP, not to AAA.
> 
> PANA and AAA are next to each other (or even glued together.. "upper 
> layer PANA" and "lower layer PANA") and EAP is above them. Why to pass 
> errors that the EAP doesn't know to the EAP? Instead AAA errors can 
> be passed to PANA when necessary. EAP has limitations.
> 
> - Dan
> 
> >
> > Yoshihiro Ohba
> >
> >
> > >
> > > - Dan
> > >
> > > > -----Original Message-----
> > > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: 14 October, 2003 21:03
> > > > To: Alper Yegin
> > > > Cc: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > > > Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > > >
> > > >
> > > > There are already three authentication results defined, i.e.,
> > > > PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
> > > > PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
> > > > PANA_REALM_NOT_SERVED seems to be a bit inconsistent in
> > design with
> > > > those three fundamental results.
> > > >
> > > > In addition, the EAP state machine draft does not have an
> > interface to
> > > > AAA to obtain detailed error information like
> > REALM_NOT_SERVED, and
> > > > thus in actual implementations it is likely that
> > > > PANA_AUTHENTICATION_REJECTED is used instead of
> > PANA_REALM_NOT_SERVED.
> > > >
> > > > So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
> > > > > > In PANA we retransmit requests because we want to
> > have reliable
> > > > > > transport. So, the case where the authenticator
> > retransmits the
> > > > > > EAP-Request/Identity is interpreted differently in PANA layer
> > > > > > (retransmissions for reliability).
> > > > > >
> > > > > > The case of Notification Request is usable, but what does
> > > > > > "invalid authentication attempt" mean? Can we
> > interpret it such
> > > > > > a way that it means "typo in the identity, user part" or "user
> > > > > > not recognized" or "realm not served"..
> > > > >
> > > > > Good points, but that does not mean they are problems for
> > > > PANA to solve.
> > > > >
> > > > > Generally I'm concerned about leaking EAP-layer events or
> > > > actions into PANA.
> > > > > But I think in this case, this is more of mapping an
> > EAP lower-layer
> > > > > (Diameter) event to PANA. While I wouldn't simply import
> > > > all such events
> > > > > from one to another, I think this one might be useful and
> > > > not disruptive. On
> > > > > the other hand, this error message is different from all
> > > > the others. Those
> > > > > are all PANA-specific.
> > > > >
> > > > > Hmmm... Does anyone else care to comment on this?
> > > > >
> > > > > Alper
> > > > >
> > > > >
> > > > > >
> > > > > > A result code in PANA for this (borrowed from
> > Diameter) is clear
> > > > > > and works if the authenticator implementation doesn't support
> > > > > > this MAY part of the EAP doc.
> > > > > >
> > > > > > - Dan
> > > > > >
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > > > > >> Sent: 07 October, 2003 20:55
> > > > > >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > > > > >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > > > > >>
> > > > > >>
> > > > > >>>> I think this is also an EAP question. What would be the EAP
> > > > > >>>> behavior when
> > > > > >>>> the NAS cannot recognize the EAP client identifier?
> > > > > >>
> > > > > >> I think this case would be handled by the following text from
> > > > > >> the EAP spec:
> > > > > >>
> > > > > >>          Implementation Note: The peer MAY obtain the
> > > > > >> Identity via user
> > > > > >>          input.  It is suggested that the
> > authenticator retry the
> > > > > >>          Identity Request in the case of an invalid
> > Identity or
> > > > > >>          authentication failure to allow for potential typos
> > > > > >> on the part
> > > > > >>          of the user.  It is suggested that the Identity
> > > > Request be
> > > > > >>          retried a minimum of 3 times before terminating the
> > > > > >>          authentication.  The Notification Request
> > MAY be used to
> > > > > >>          indicate an invalid authentication attempt prior to
> > > > > >>          transmitting a new Identity Request
> > > > (optionally, the failure
> > > > > >>          MAY be indicated within the message of the new
> > > > > >> Identity Request
> > > > > >>          itself).
> > > > > >>
> > > > > >> ... And finally I think the EAP authenticator would send a
> > > > > >> Failure message.
> > > > > >>
> > > > > >> 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 exim@www1.ietf.org  Thu Oct 16 12:14:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08503
	for <pana-archive@odin.ietf.org>; Thu, 16 Oct 2003 12:14:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAAlJ-00031k-RB
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 12:14:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9GGE5Gu011632
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 12:14:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAAlJ-00031X-MO
	for pana-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 12:14:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08469
	for <pana-web-archive@ietf.org>; Thu, 16 Oct 2003 12:13:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAAlI-0006JY-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 12:14:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAAlI-0006JV-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 12:14:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAAlF-000317-6I; Thu, 16 Oct 2003 12:14:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAAkU-00030D-Fl
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 12:13:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08465
	for <pana@ietf.org>; Thu, 16 Oct 2003 12:13:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAAkT-0006Iz-00
	for pana@ietf.org; Thu, 16 Oct 2003 12:13:13 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAAkS-0006Iq-00
	for pana@ietf.org; Thu, 16 Oct 2003 12:13:12 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9GGD5F1019831;
	Fri, 17 Oct 2003 01:13:05 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9GGD5Fg012534;
	Fri, 17 Oct 2003 01:13:05 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA12533 ; Fri, 17 Oct 2003 01:13:05 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA13895; Fri, 17 Oct 2003 01:13:04 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA23483; Fri, 17 Oct 2003 01:13:02 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9GGD1ib002356;
	Fri, 17 Oct 2003 01:13:01 +0900 (JST)
Received: from steelhead ([159.119.168.101]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMU00E49YDNC8@tsbpo1.po.toshiba.co.jp>; Fri,
 17 Oct 2003 01:13:00 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAAk5-0003b0-00; Thu, 16 Oct 2003 09:12:49 -0700
Date: Thu, 16 Oct 2003 09:12:49 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] [issue19] Result-Code AVP values?
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA0143C5AE@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, alper@docomolabs-usa.com, pana@ietf.org
Message-id: <20031016161249.GA13220@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com,
 alper@docomolabs-usa.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA0143C5AE@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

I believe the issues you have addressed below are for Diameter EAP
application draft and EAP state machines.  As far as I know, when an
AAA message routing error occurs, the EAP authenticator on the NAS
will not receive any EAP message or a signal from AAA.  Instead, it
relies on a timeout event generated by itself ("aaaTimeout" variable
is defined in the EAP full authenticator state machine).  When the
timeout occurs, the EAP authenticator enters a final state
TIMEOUT_FAILURE2 with setting eapTimout = TRUE but without generating
an EAP Failure (This is a mandatory behavior defined in RFC3579).  

So the EAP authenticator on the NAS may not be able to generate any
EAP message when the AAA message routing error occurs.  

I would suggest creating a new PANA issue on how to handle the case in
which an EAP authenticator on the NAS fails to authenticate an EAP
peer without generating an EAP message.  We can continue the
discussion on whether AAA error needs to be leaked to PANA in the new
issue.

Can we close issue19?

Yoshihiro Ohba


On Thu, Oct 16, 2003 at 10:39:53AM +0300, Dan.Forsberg@nokia.com wrote:
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 15 October, 2003 19:24
> > To: Forsberg Dan (NRC/Helsinki)
> > Cc: yohba@tari.toshiba.com; alper@docomolabs-usa.com; pana@ietf.org
> > Subject: Re: [Pana] [issue19] Result-Code AVP values?
> >
> >
> > On Wed, Oct 15, 2003 at 11:06:17AM +0300,
> > Dan.Forsberg@nokia.com wrote:
> > > I don't understand your arguments.
> > >
> > > PANA_REALM_NOT_SERVED is seen as an error code (see the
> > issue19), not
> > > an authentication result code. No authentication can take
> > place because
> > > of this error.
> > >
> > > This has nothing to do with EAP or? The NAS/PAA can't route the AAA
> > > message because it can't find the routing info for the
> > realm. EAP is
> > > just carried in the AAA message (EAP-Payload AVP).
> >
> > OK.  I see what you mean.
> >
> > It would depend on the behavior of of the EAP authenticator on the NAS
> > when the AAA message routing error happens.
> >
> > If the authenticator generate an EAP Failure, the result code should
> > contain an authentication result.
> 
> How can EAP authenticator generate an error if it only passes the message 
> for the AAA routing process and the error comes from the AAA routing?

> 
> [On the other thread we are discussing about using ISP and NAP identifiers. 
> I think this problem relates to this discussion. We may need a similar 
> error code there too (i.e. "unknown ISP/NAP identifier/realm").]
> 
> > If the authenticator generates a new EAP Request/Identity to give
> > the EAP peer another chance to send a correct identity and
> > no result code will be included.
> 
> How does the passthrough authenticator (NAS) know if the Identity is 
> not correct when the syntax is perfect? Even the PAA/NAS may not know 
\> this but forwards the message to the AAA proxy/relay etc. Anyway, if the 
> realm really isn't served, then the NAS/PAA receives this kind of error 
> code. What happens then?
> 
> >
> > (There would be another possibility: the authenticator retransmits the
> > initial EAP Request/Identity, but this will not work because the EAP
> > peer will retransmit the old EAP Response/Identity which contains the
> > old realm that caused the AAA message routing error.)
> >
> > I don't see a case where a status code of a protocol error class
> > is returned in the above scenarios.
> >
> > >
> > > Do you think that this result code reveals too much for the
> > PaC about
> > > the network side?
> >
> > I believe error handling at PAA would be complicated if AAA errors are
> > revealed to PANA.  PAA should just interface to EAP, not to AAA.
> 
> PANA and AAA are next to each other (or even glued together.. "upper 
> layer PANA" and "lower layer PANA") and EAP is above them. Why to pass 
> errors that the EAP doesn't know to the EAP? Instead AAA errors can 
> be passed to PANA when necessary. EAP has limitations.
> 
> - Dan
> 
> >
> > Yoshihiro Ohba
> >
> >
> > >
> > > - Dan
> > >
> > > > -----Original Message-----
> > > > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: 14 October, 2003 21:03
> > > > To: Alper Yegin
> > > > Cc: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > > > Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > > >
> > > >
> > > > There are already three authentication results defined, i.e.,
> > > > PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
> > > > PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
> > > > PANA_REALM_NOT_SERVED seems to be a bit inconsistent in
> > design with
> > > > those three fundamental results.
> > > >
> > > > In addition, the EAP state machine draft does not have an
> > interface to
> > > > AAA to obtain detailed error information like
> > REALM_NOT_SERVED, and
> > > > thus in actual implementations it is likely that
> > > > PANA_AUTHENTICATION_REJECTED is used instead of
> > PANA_REALM_NOT_SERVED.
> > > >
> > > > So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
> > > > > > In PANA we retransmit requests because we want to
> > have reliable
> > > > > > transport. So, the case where the authenticator
> > retransmits the
> > > > > > EAP-Request/Identity is interpreted differently in PANA layer
> > > > > > (retransmissions for reliability).
> > > > > >
> > > > > > The case of Notification Request is usable, but what does
> > > > > > "invalid authentication attempt" mean? Can we
> > interpret it such
> > > > > > a way that it means "typo in the identity, user part" or "user
> > > > > > not recognized" or "realm not served"..
> > > > >
> > > > > Good points, but that does not mean they are problems for
> > > > PANA to solve.
> > > > >
> > > > > Generally I'm concerned about leaking EAP-layer events or
> > > > actions into PANA.
> > > > > But I think in this case, this is more of mapping an
> > EAP lower-layer
> > > > > (Diameter) event to PANA. While I wouldn't simply import
> > > > all such events
> > > > > from one to another, I think this one might be useful and
> > > > not disruptive. On
> > > > > the other hand, this error message is different from all
> > > > the others. Those
> > > > > are all PANA-specific.
> > > > >
> > > > > Hmmm... Does anyone else care to comment on this?
> > > > >
> > > > > Alper
> > > > >
> > > > >
> > > > > >
> > > > > > A result code in PANA for this (borrowed from
> > Diameter) is clear
> > > > > > and works if the authenticator implementation doesn't support
> > > > > > this MAY part of the EAP doc.
> > > > > >
> > > > > > - Dan
> > > > > >
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> > > > > >> Sent: 07 October, 2003 20:55
> > > > > >> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
> > > > > >> Subject: Re: [Pana] [issue19] Result-Code AVP values?
> > > > > >>
> > > > > >>
> > > > > >>>> I think this is also an EAP question. What would be the EAP
> > > > > >>>> behavior when
> > > > > >>>> the NAS cannot recognize the EAP client identifier?
> > > > > >>
> > > > > >> I think this case would be handled by the following text from
> > > > > >> the EAP spec:
> > > > > >>
> > > > > >>          Implementation Note: The peer MAY obtain the
> > > > > >> Identity via user
> > > > > >>          input.  It is suggested that the
> > authenticator retry the
> > > > > >>          Identity Request in the case of an invalid
> > Identity or
> > > > > >>          authentication failure to allow for potential typos
> > > > > >> on the part
> > > > > >>          of the user.  It is suggested that the Identity
> > > > Request be
> > > > > >>          retried a minimum of 3 times before terminating the
> > > > > >>          authentication.  The Notification Request
> > MAY be used to
> > > > > >>          indicate an invalid authentication attempt prior to
> > > > > >>          transmitting a new Identity Request
> > > > (optionally, the failure
> > > > > >>          MAY be indicated within the message of the new
> > > > > >> Identity Request
> > > > > >>          itself).
> > > > > >>
> > > > > >> ... And finally I think the EAP authenticator would send a
> > > > > >> Failure message.
> > > > > >>
> > > > > >> 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-admin@ietf.org  Thu Oct 16 13:00:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11072
	for <pana-archive@lists.ietf.org>; Thu, 16 Oct 2003 13:00:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AABTm-0005Xi-7L; Thu, 16 Oct 2003 13:00:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AABTM-0005Wo-AD
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 12:59:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10999
	for <pana@ietf.org>; Thu, 16 Oct 2003 12:59:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AABTK-00074T-00
	for pana@ietf.org; Thu, 16 Oct 2003 12:59:34 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AABTJ-00074Q-00
	for pana@ietf.org; Thu, 16 Oct 2003 12:59:33 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9GGxWF1000144;
	Fri, 17 Oct 2003 01:59:32 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9GGxWKq027264;
	Fri, 17 Oct 2003 01:59:32 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA27263 ; Fri, 17 Oct 2003 01:59:32 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA25112; Fri, 17 Oct 2003 01:59:31 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA00326; Fri, 17 Oct 2003 01:59:31 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9GGxUib013352;
	Fri, 17 Oct 2003 01:59:31 +0900 (JST)
Received: from steelhead ([159.119.168.101]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMV00F3W0J5P6@tsbpo1.po.toshiba.co.jp>; Fri,
 17 Oct 2003 01:59:30 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AABSA-0003fE-00; Thu, 16 Oct 2003 09:58:22 -0700
Date: Thu, 16 Oct 2003 09:58:22 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D7C@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031016165822.GB13220@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D7C@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Thu, Oct 16, 2003 at 11:11:58AM +0300, Dan.Forsberg@nokia.com wrote:
> Hi Yoshi,
> 
> I don't know the EAP state machines, but I guess they are 
> intepretations of the EAP protocol specification. 
> 
> You said that EAP-Request/Response Identity message exchange 
> is optional. This seems to imply that the EAP authenticator
> does not have to be stateful during identity "discovery"?

I think whether PAA becomes stateful or stateless during discovery and
initial handshake phase is implementation dependent (please see Note
below), and orthogonal to whether EAP-Request/Response Identity
exchange is performed or not.

When PAA is implemented to be stateless by using Cookie during
discovery and initial handshake phase, carrying the initial EAP
Request (which may or may not be an EAP Request/Identity) in
PANA-Start-Request will make the PAA stateful because the EAP
authenticator on the box will create a state at EAP layer when
generating the initial EAP Request.  I can't imagine how PAA can be
stateless while EAP authenticator has created a state.  Even if PAA
could be stateless when EAP authenticator has created a state, the
machine where the PAA and EAP authenticator are implemented becomes
stateful and this breaks the purpose of using Cookie.

Note: When PANA is implemented on point-to-point links, PAA can be
stateful because there is at most one PaC on each link and using
Cookie does not make much sense. Using Cookie (and PAA becomes
stateless) makes sense only when there can be multiple PaCs connected
to the same link at the same time.

> How does the authenticator skip the identity request/response 
> part when the identity is known outside EAP already?

The authenticator can immediately perform an EAP authentication method
when the identity is known outside EAP already.

Or if the identity is obtained in an EAP authentication method, the
authenticator can skip initial identity request/response exchange and
can immediately performs the EAP authentication method.

Yoshihiro Ohba


> 
> This is why I can't see your separation to stateless or 
> stateful.
> 
> - Dan
> 
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 15 October, 2003 19:39
> > To: Forsberg Dan (NRC/Helsinki)
> > Cc: yohba@tari.toshiba.com; pana@ietf.org
> > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> >
> >
> > Hi Dan,
> >
> > On Wed, Oct 15, 2003 at 11:47:18AM +0300,
> > Dan.Forsberg@nokia.com wrote:
> > > >
> > > > The issue we are discussing is: which PANA message should
> > carry the
> > > > initial EAP Request/Identity and here is my suggestion:
> > > >
> > > >   "When a Cookie-AVP is carried in a PANA-Start-Request
> > message, the
> > > >   initial EAP Request MUST NOT be carried in the
> > PANA-Start-Request
> > > >   message in order for the PAA to be stateful.
> > >
> > > I don't think that the Cookie makes PAA necessarily
> > stateful. PAA could
> > > use a timestamp and a hash of PaC's address, encrypt that
> > with a secret
> > > key and use it as a cookie. When PAA checks the cookie, it
> > decrypts it
> > > and checks the timestamp and address hash. No state
> > required. I'm not a
> > > cookie expert, though.
> >
> > Sorry, that is a typo, "stateful" should read "stateless".
> >
> > >
> > > >
> > > >   When a Cookie-AVP is not carried in a
> > PANA-Start-Request message,
> > > >   the PAA does not need to be stateful.  In this case,
> > the initial EAP
> >
> > This is the same typo, "stateful" should read "stateless".
> >
> > > >   Request message MAY be carried in the
> > PANA-Start-Request message.
> > > >   If the initial EAP Request message is carried in the
> > > >   PANA-Start-Request message, an EAP Response message
> > MUST be carried
> > > >   in the PANA-Start-Answer message returned to the PAA.
> > > > 
> > > >   In any case, PANA MUST NOT generate an EAP message on behalf of
> > > >   EAP peer or EAP authenticator."
> > >
> > > Just for clarification and for easier understanding what about:
> > >    "In any case, PANA MUST NOT generate an EAP message on behalf of
> > >     EAP peer or EAP (passthrough) authenticator."
> >
> > OK.
> >
> > >
> > > >
> > > > I think this allows saving one round trip when PAA does
> > not need to be
> > > > stateless.
> > >
> > > Ok, but I don't fully agree about the separation of Cookie
> > and EAP-Request.
> > > See the comment above.
> >
> >
> > After fixing the typo, I guess we are in agreement.
> >
> > Yoshihiro Ohba
> >
> >
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> > 

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


From exim@www1.ietf.org  Thu Oct 16 13:00:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11091
	for <pana-archive@odin.ietf.org>; Thu, 16 Oct 2003 13:00:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AABTu-0005YP-FL
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 13:00:10 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9GH09YS021343
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 13:00:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AABTq-0005YA-Jr
	for pana-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 13:00:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11042
	for <pana-web-archive@ietf.org>; Thu, 16 Oct 2003 12:59:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AABTo-00074x-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 13:00:04 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AABTo-00074t-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 13:00:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AABTm-0005Xi-7L; Thu, 16 Oct 2003 13:00:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AABTM-0005Wo-AD
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 12:59:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10999
	for <pana@ietf.org>; Thu, 16 Oct 2003 12:59:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AABTK-00074T-00
	for pana@ietf.org; Thu, 16 Oct 2003 12:59:34 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AABTJ-00074Q-00
	for pana@ietf.org; Thu, 16 Oct 2003 12:59:33 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9GGxWF1000144;
	Fri, 17 Oct 2003 01:59:32 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9GGxWKq027264;
	Fri, 17 Oct 2003 01:59:32 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA27263 ; Fri, 17 Oct 2003 01:59:32 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA25112; Fri, 17 Oct 2003 01:59:31 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA00326; Fri, 17 Oct 2003 01:59:31 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9GGxUib013352;
	Fri, 17 Oct 2003 01:59:31 +0900 (JST)
Received: from steelhead ([159.119.168.101]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMV00F3W0J5P6@tsbpo1.po.toshiba.co.jp>; Fri,
 17 Oct 2003 01:59:30 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AABSA-0003fE-00; Thu, 16 Oct 2003 09:58:22 -0700
Date: Thu, 16 Oct 2003 09:58:22 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D7C@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: yohba@tari.toshiba.com, pana@ietf.org
Message-id: <20031016165822.GB13220@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, yohba@tari.toshiba.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D7C@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Thu, Oct 16, 2003 at 11:11:58AM +0300, Dan.Forsberg@nokia.com wrote:
> Hi Yoshi,
> 
> I don't know the EAP state machines, but I guess they are 
> intepretations of the EAP protocol specification. 
> 
> You said that EAP-Request/Response Identity message exchange 
> is optional. This seems to imply that the EAP authenticator
> does not have to be stateful during identity "discovery"?

I think whether PAA becomes stateful or stateless during discovery and
initial handshake phase is implementation dependent (please see Note
below), and orthogonal to whether EAP-Request/Response Identity
exchange is performed or not.

When PAA is implemented to be stateless by using Cookie during
discovery and initial handshake phase, carrying the initial EAP
Request (which may or may not be an EAP Request/Identity) in
PANA-Start-Request will make the PAA stateful because the EAP
authenticator on the box will create a state at EAP layer when
generating the initial EAP Request.  I can't imagine how PAA can be
stateless while EAP authenticator has created a state.  Even if PAA
could be stateless when EAP authenticator has created a state, the
machine where the PAA and EAP authenticator are implemented becomes
stateful and this breaks the purpose of using Cookie.

Note: When PANA is implemented on point-to-point links, PAA can be
stateful because there is at most one PaC on each link and using
Cookie does not make much sense. Using Cookie (and PAA becomes
stateless) makes sense only when there can be multiple PaCs connected
to the same link at the same time.

> How does the authenticator skip the identity request/response 
> part when the identity is known outside EAP already?

The authenticator can immediately perform an EAP authentication method
when the identity is known outside EAP already.

Or if the identity is obtained in an EAP authentication method, the
authenticator can skip initial identity request/response exchange and
can immediately performs the EAP authentication method.

Yoshihiro Ohba


> 
> This is why I can't see your separation to stateless or 
> stateful.
> 
> - Dan
> 
> > -----Original Message-----
> > From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: 15 October, 2003 19:39
> > To: Forsberg Dan (NRC/Helsinki)
> > Cc: yohba@tari.toshiba.com; pana@ietf.org
> > Subject: Re: [Pana] EAP-Request/Identity & PANA-Start-Request
> >
> >
> > Hi Dan,
> >
> > On Wed, Oct 15, 2003 at 11:47:18AM +0300,
> > Dan.Forsberg@nokia.com wrote:
> > > >
> > > > The issue we are discussing is: which PANA message should
> > carry the
> > > > initial EAP Request/Identity and here is my suggestion:
> > > >
> > > >   "When a Cookie-AVP is carried in a PANA-Start-Request
> > message, the
> > > >   initial EAP Request MUST NOT be carried in the
> > PANA-Start-Request
> > > >   message in order for the PAA to be stateful.
> > >
> > > I don't think that the Cookie makes PAA necessarily
> > stateful. PAA could
> > > use a timestamp and a hash of PaC's address, encrypt that
> > with a secret
> > > key and use it as a cookie. When PAA checks the cookie, it
> > decrypts it
> > > and checks the timestamp and address hash. No state
> > required. I'm not a
> > > cookie expert, though.
> >
> > Sorry, that is a typo, "stateful" should read "stateless".
> >
> > >
> > > >
> > > >   When a Cookie-AVP is not carried in a
> > PANA-Start-Request message,
> > > >   the PAA does not need to be stateful.  In this case,
> > the initial EAP
> >
> > This is the same typo, "stateful" should read "stateless".
> >
> > > >   Request message MAY be carried in the
> > PANA-Start-Request message.
> > > >   If the initial EAP Request message is carried in the
> > > >   PANA-Start-Request message, an EAP Response message
> > MUST be carried
> > > >   in the PANA-Start-Answer message returned to the PAA.
> > > > 
> > > >   In any case, PANA MUST NOT generate an EAP message on behalf of
> > > >   EAP peer or EAP authenticator."
> > >
> > > Just for clarification and for easier understanding what about:
> > >    "In any case, PANA MUST NOT generate an EAP message on behalf of
> > >     EAP peer or EAP (passthrough) authenticator."
> >
> > OK.
> >
> > >
> > > >
> > > > I think this allows saving one round trip when PAA does
> > not need to be
> > > > stateless.
> > >
> > > Ok, but I don't fully agree about the separation of Cookie
> > and EAP-Request.
> > > See the comment above.
> >
> >
> > After fixing the typo, I guess we are in agreement.
> >
> > Yoshihiro Ohba
> >
> >
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> > 

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



From pana-admin@ietf.org  Thu Oct 16 15:10:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17488
	for <pana-archive@lists.ietf.org>; Thu, 16 Oct 2003 15:10:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADVb-0004AU-4i; Thu, 16 Oct 2003 15:10:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADUi-00048Q-Nq
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 15:09:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17325
	for <pana@ietf.org>; Thu, 16 Oct 2003 15:08:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADUf-0000qx-00
	for pana@ietf.org; Thu, 16 Oct 2003 15:09:05 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADUe-0000qu-00
	for pana@ietf.org; Thu, 16 Oct 2003 15:09:04 -0400
Date: Thu, 16 Oct 2003 12:08:54 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <Dan.Forsberg@nokia.com>
CC: <pana@ietf.org>
Message-ID: <BBB43AD6.A9A3%alper@docomolabs-usa.com>
In-Reply-To: <20031016161249.GA13220@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

> I believe the issues you have addressed below are for Diameter EAP
> application draft and EAP state machines.  As far as I know, when an
> AAA message routing error occurs, the EAP authenticator on the NAS
> will not receive any EAP message or a signal from AAA.  Instead, it
> relies on a timeout event generated by itself ("aaaTimeout" variable
> is defined in the EAP full authenticator state machine).  When the
> timeout occurs, the EAP authenticator enters a final state
> TIMEOUT_FAILURE2 with setting eapTimout =3D TRUE but without generating
> an EAP Failure (This is a mandatory behavior defined in RFC3579).
>=20
> So the EAP authenticator on the NAS may not be able to generate any
> EAP message when the AAA message routing error occurs.
>=20
> I would suggest creating a new PANA issue on how to handle the case in
> which an EAP authenticator on the NAS fails to authenticate an EAP
> peer without generating an EAP message.  We can continue the
> discussion on whether AAA error needs to be leaked to PANA in the new
> issue.
>=20
> Can we close issue19?

This is a good approach. I agree we should close issue 19, and open a more
specific one for this case.

Alper



>=20
> Yoshihiro Ohba
>=20
>=20
> On Thu, Oct 16, 2003 at 10:39:53AM +0300, Dan.Forsberg@nokia.com wrote:
>>> -----Original Message-----
>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>> Sent: 15 October, 2003 19:24
>>> To: Forsberg Dan (NRC/Helsinki)
>>> Cc: yohba@tari.toshiba.com; alper@docomolabs-usa.com; pana@ietf.org
>>> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>>>=20
>>>=20
>>> On Wed, Oct 15, 2003 at 11:06:17AM +0300,
>>> Dan.Forsberg@nokia.com wrote:
>>>> I don't understand your arguments.
>>>>=20
>>>> PANA_REALM_NOT_SERVED is seen as an error code (see the
>>> issue19), not
>>>> an authentication result code. No authentication can take
>>> place because
>>>> of this error.
>>>>=20
>>>> This has nothing to do with EAP or? The NAS/PAA can't route the AAA
>>>> message because it can't find the routing info for the
>>> realm. EAP is
>>>> just carried in the AAA message (EAP-Payload AVP).
>>>=20
>>> OK.  I see what you mean.
>>>=20
>>> It would depend on the behavior of of the EAP authenticator on the NAS
>>> when the AAA message routing error happens.
>>>=20
>>> If the authenticator generate an EAP Failure, the result code should
>>> contain an authentication result.
>>=20
>> How can EAP authenticator generate an error if it only passes the messag=
e
>> for the AAA routing process and the error comes from the AAA routing?
>=20
>>=20
>> [On the other thread we are discussing about using ISP and NAP identifie=
rs.
>> I think this problem relates to this discussion. We may need a similar
>> error code there too (i.e. "unknown ISP/NAP identifier/realm").]
>>=20
>>> If the authenticator generates a new EAP Request/Identity to give
>>> the EAP peer another chance to send a correct identity and
>>> no result code will be included.
>>=20
>> How does the passthrough authenticator (NAS) know if the Identity is
>> not correct when the syntax is perfect? Even the PAA/NAS may not know
> =A5> this but forwards the message to the AAA proxy/relay etc. Anyway, if t=
he
>> realm really isn't served, then the NAS/PAA receives this kind of error
>> code. What happens then?
>>=20
>>>=20
>>> (There would be another possibility: the authenticator retransmits the
>>> initial EAP Request/Identity, but this will not work because the EAP
>>> peer will retransmit the old EAP Response/Identity which contains the
>>> old realm that caused the AAA message routing error.)
>>>=20
>>> I don't see a case where a status code of a protocol error class
>>> is returned in the above scenarios.
>>>=20
>>>>=20
>>>> Do you think that this result code reveals too much for the
>>> PaC about
>>>> the network side?
>>>=20
>>> I believe error handling at PAA would be complicated if AAA errors are
>>> revealed to PANA.  PAA should just interface to EAP, not to AAA.
>>=20
>> PANA and AAA are next to each other (or even glued together.. "upper
>> layer PANA" and "lower layer PANA") and EAP is above them. Why to pass
>> errors that the EAP doesn't know to the EAP? Instead AAA errors can
>> be passed to PANA when necessary. EAP has limitations.
>>=20
>> - Dan
>>=20
>>>=20
>>> Yoshihiro Ohba
>>>=20
>>>=20
>>>>=20
>>>> - Dan
>>>>=20
>>>>> -----Original Message-----
>>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>>>> Sent: 14 October, 2003 21:03
>>>>> To: Alper Yegin
>>>>> Cc: Forsberg Dan (NRC/Helsinki); pana@ietf.org
>>>>> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>>>>>=20
>>>>>=20
>>>>> There are already three authentication results defined, i.e.,
>>>>> PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
>>>>> PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
>>>>> PANA_REALM_NOT_SERVED seems to be a bit inconsistent in
>>> design with
>>>>> those three fundamental results.
>>>>>=20
>>>>> In addition, the EAP state machine draft does not have an
>>> interface to
>>>>> AAA to obtain detailed error information like
>>> REALM_NOT_SERVED, and
>>>>> thus in actual implementations it is likely that
>>>>> PANA_AUTHENTICATION_REJECTED is used instead of
>>> PANA_REALM_NOT_SERVED.
>>>>>=20
>>>>> So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
>>>>>=20
>>>>> Yoshihiro Ohba
>>>>>=20
>>>>>=20
>>>>> On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
>>>>>>> In PANA we retransmit requests because we want to
>>> have reliable
>>>>>>> transport. So, the case where the authenticator
>>> retransmits the
>>>>>>> EAP-Request/Identity is interpreted differently in PANA layer
>>>>>>> (retransmissions for reliability).
>>>>>>>=20
>>>>>>> The case of Notification Request is usable, but what does
>>>>>>> "invalid authentication attempt" mean? Can we
>>> interpret it such
>>>>>>> a way that it means "typo in the identity, user part" or "user
>>>>>>> not recognized" or "realm not served"..
>>>>>>=20
>>>>>> Good points, but that does not mean they are problems for
>>>>> PANA to solve.
>>>>>>=20
>>>>>> Generally I'm concerned about leaking EAP-layer events or
>>>>> actions into PANA.
>>>>>> But I think in this case, this is more of mapping an
>>> EAP lower-layer
>>>>>> (Diameter) event to PANA. While I wouldn't simply import
>>>>> all such events
>>>>>> from one to another, I think this one might be useful and
>>>>> not disruptive. On
>>>>>> the other hand, this error message is different from all
>>>>> the others. Those
>>>>>> are all PANA-specific.
>>>>>>=20
>>>>>> Hmmm... Does anyone else care to comment on this?
>>>>>>=20
>>>>>> Alper
>>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>> A result code in PANA for this (borrowed from
>>> Diameter) is clear
>>>>>>> and works if the authenticator implementation doesn't support
>>>>>>> this MAY part of the EAP doc.
>>>>>>>=20
>>>>>>> - Dan
>>>>>>>=20
>>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
>>>>>>>> Sent: 07 October, 2003 20:55
>>>>>>>> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
>>>>>>>> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>>> I think this is also an EAP question. What would be the EAP
>>>>>>>>>> behavior when
>>>>>>>>>> the NAS cannot recognize the EAP client identifier?
>>>>>>>>=20
>>>>>>>> I think this case would be handled by the following text from
>>>>>>>> the EAP spec:
>>>>>>>>=20
>>>>>>>>          Implementation Note: The peer MAY obtain the
>>>>>>>> Identity via user
>>>>>>>>          input.  It is suggested that the
>>> authenticator retry the
>>>>>>>>          Identity Request in the case of an invalid
>>> Identity or
>>>>>>>>          authentication failure to allow for potential typos
>>>>>>>> on the part
>>>>>>>>          of the user.  It is suggested that the Identity
>>>>> Request be
>>>>>>>>          retried a minimum of 3 times before terminating the
>>>>>>>>          authentication.  The Notification Request
>>> MAY be used to
>>>>>>>>          indicate an invalid authentication attempt prior to
>>>>>>>>          transmitting a new Identity Request
>>>>> (optionally, the failure
>>>>>>>>          MAY be indicated within the message of the new
>>>>>>>> Identity Request
>>>>>>>>          itself).
>>>>>>>>=20
>>>>>>>> ... And finally I think the EAP authenticator would send a
>>>>>>>> Failure message.
>>>>>>>>=20
>>>>>>>> Alper
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> Pana mailing list
>>>>>> Pana@ietf.org
>>>>>> https://www1.ietf.org/mailman/listinfo/pana
>>>>>=20
>>>=20
>=20


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


From exim@www1.ietf.org  Thu Oct 16 15:10:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17505
	for <pana-archive@odin.ietf.org>; Thu, 16 Oct 2003 15:10:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADVi-0004BH-OE
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 15:10:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9GJAA7m016068
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 15:10:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADVi-0004B5-FB
	for pana-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 15:10:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17443
	for <pana-web-archive@ietf.org>; Thu, 16 Oct 2003 15:09:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADVf-0000ro-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 15:10:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADVf-0000rl-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 15:10:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADVb-0004AU-4i; Thu, 16 Oct 2003 15:10:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADUi-00048Q-Nq
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 15:09:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17325
	for <pana@ietf.org>; Thu, 16 Oct 2003 15:08:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADUf-0000qx-00
	for pana@ietf.org; Thu, 16 Oct 2003 15:09:05 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADUe-0000qu-00
	for pana@ietf.org; Thu, 16 Oct 2003 15:09:04 -0400
Date: Thu, 16 Oct 2003 12:08:54 -0700
Subject: Re: [Pana] [issue19] Result-Code AVP values?
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <Dan.Forsberg@nokia.com>
CC: <pana@ietf.org>
Message-ID: <BBB43AD6.A9A3%alper@docomolabs-usa.com>
In-Reply-To: <20031016161249.GA13220@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> I believe the issues you have addressed below are for Diameter EAP
> application draft and EAP state machines.  As far as I know, when an
> AAA message routing error occurs, the EAP authenticator on the NAS
> will not receive any EAP message or a signal from AAA.  Instead, it
> relies on a timeout event generated by itself ("aaaTimeout" variable
> is defined in the EAP full authenticator state machine).  When the
> timeout occurs, the EAP authenticator enters a final state
> TIMEOUT_FAILURE2 with setting eapTimout =3D TRUE but without generating
> an EAP Failure (This is a mandatory behavior defined in RFC3579).
>=20
> So the EAP authenticator on the NAS may not be able to generate any
> EAP message when the AAA message routing error occurs.
>=20
> I would suggest creating a new PANA issue on how to handle the case in
> which an EAP authenticator on the NAS fails to authenticate an EAP
> peer without generating an EAP message.  We can continue the
> discussion on whether AAA error needs to be leaked to PANA in the new
> issue.
>=20
> Can we close issue19?

This is a good approach. I agree we should close issue 19, and open a more
specific one for this case.

Alper



>=20
> Yoshihiro Ohba
>=20
>=20
> On Thu, Oct 16, 2003 at 10:39:53AM +0300, Dan.Forsberg@nokia.com wrote:
>>> -----Original Message-----
>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>> Sent: 15 October, 2003 19:24
>>> To: Forsberg Dan (NRC/Helsinki)
>>> Cc: yohba@tari.toshiba.com; alper@docomolabs-usa.com; pana@ietf.org
>>> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>>>=20
>>>=20
>>> On Wed, Oct 15, 2003 at 11:06:17AM +0300,
>>> Dan.Forsberg@nokia.com wrote:
>>>> I don't understand your arguments.
>>>>=20
>>>> PANA_REALM_NOT_SERVED is seen as an error code (see the
>>> issue19), not
>>>> an authentication result code. No authentication can take
>>> place because
>>>> of this error.
>>>>=20
>>>> This has nothing to do with EAP or? The NAS/PAA can't route the AAA
>>>> message because it can't find the routing info for the
>>> realm. EAP is
>>>> just carried in the AAA message (EAP-Payload AVP).
>>>=20
>>> OK.  I see what you mean.
>>>=20
>>> It would depend on the behavior of of the EAP authenticator on the NAS
>>> when the AAA message routing error happens.
>>>=20
>>> If the authenticator generate an EAP Failure, the result code should
>>> contain an authentication result.
>>=20
>> How can EAP authenticator generate an error if it only passes the messag=
e
>> for the AAA routing process and the error comes from the AAA routing?
>=20
>>=20
>> [On the other thread we are discussing about using ISP and NAP identifie=
rs.
>> I think this problem relates to this discussion. We may need a similar
>> error code there too (i.e. "unknown ISP/NAP identifier/realm").]
>>=20
>>> If the authenticator generates a new EAP Request/Identity to give
>>> the EAP peer another chance to send a correct identity and
>>> no result code will be included.
>>=20
>> How does the passthrough authenticator (NAS) know if the Identity is
>> not correct when the syntax is perfect? Even the PAA/NAS may not know
> =A5> this but forwards the message to the AAA proxy/relay etc. Anyway, if t=
he
>> realm really isn't served, then the NAS/PAA receives this kind of error
>> code. What happens then?
>>=20
>>>=20
>>> (There would be another possibility: the authenticator retransmits the
>>> initial EAP Request/Identity, but this will not work because the EAP
>>> peer will retransmit the old EAP Response/Identity which contains the
>>> old realm that caused the AAA message routing error.)
>>>=20
>>> I don't see a case where a status code of a protocol error class
>>> is returned in the above scenarios.
>>>=20
>>>>=20
>>>> Do you think that this result code reveals too much for the
>>> PaC about
>>>> the network side?
>>>=20
>>> I believe error handling at PAA would be complicated if AAA errors are
>>> revealed to PANA.  PAA should just interface to EAP, not to AAA.
>>=20
>> PANA and AAA are next to each other (or even glued together.. "upper
>> layer PANA" and "lower layer PANA") and EAP is above them. Why to pass
>> errors that the EAP doesn't know to the EAP? Instead AAA errors can
>> be passed to PANA when necessary. EAP has limitations.
>>=20
>> - Dan
>>=20
>>>=20
>>> Yoshihiro Ohba
>>>=20
>>>=20
>>>>=20
>>>> - Dan
>>>>=20
>>>>> -----Original Message-----
>>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>>>> Sent: 14 October, 2003 21:03
>>>>> To: Alper Yegin
>>>>> Cc: Forsberg Dan (NRC/Helsinki); pana@ietf.org
>>>>> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>>>>>=20
>>>>>=20
>>>>> There are already three authentication results defined, i.e.,
>>>>> PANA_SUCCESS, PANA_AUTHENTICATION_REJECTED and
>>>>> PANA_AUTHORIZATION_REJECTED.  Defining a more detailed result code
>>>>> PANA_REALM_NOT_SERVED seems to be a bit inconsistent in
>>> design with
>>>>> those three fundamental results.
>>>>>=20
>>>>> In addition, the EAP state machine draft does not have an
>>> interface to
>>>>> AAA to obtain detailed error information like
>>> REALM_NOT_SERVED, and
>>>>> thus in actual implementations it is likely that
>>>>> PANA_AUTHENTICATION_REJECTED is used instead of
>>> PANA_REALM_NOT_SERVED.
>>>>>=20
>>>>> So, my opinion is we don't need to define PANA_REALM_NOT_SERVED.
>>>>>=20
>>>>> Yoshihiro Ohba
>>>>>=20
>>>>>=20
>>>>> On Mon, Oct 13, 2003 at 10:54:03PM -0700, Alper Yegin wrote:
>>>>>>> In PANA we retransmit requests because we want to
>>> have reliable
>>>>>>> transport. So, the case where the authenticator
>>> retransmits the
>>>>>>> EAP-Request/Identity is interpreted differently in PANA layer
>>>>>>> (retransmissions for reliability).
>>>>>>>=20
>>>>>>> The case of Notification Request is usable, but what does
>>>>>>> "invalid authentication attempt" mean? Can we
>>> interpret it such
>>>>>>> a way that it means "typo in the identity, user part" or "user
>>>>>>> not recognized" or "realm not served"..
>>>>>>=20
>>>>>> Good points, but that does not mean they are problems for
>>>>> PANA to solve.
>>>>>>=20
>>>>>> Generally I'm concerned about leaking EAP-layer events or
>>>>> actions into PANA.
>>>>>> But I think in this case, this is more of mapping an
>>> EAP lower-layer
>>>>>> (Diameter) event to PANA. While I wouldn't simply import
>>>>> all such events
>>>>>> from one to another, I think this one might be useful and
>>>>> not disruptive. On
>>>>>> the other hand, this error message is different from all
>>>>> the others. Those
>>>>>> are all PANA-specific.
>>>>>>=20
>>>>>> Hmmm... Does anyone else care to comment on this?
>>>>>>=20
>>>>>> Alper
>>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>> A result code in PANA for this (borrowed from
>>> Diameter) is clear
>>>>>>> and works if the authenticator implementation doesn't support
>>>>>>> this MAY part of the EAP doc.
>>>>>>>=20
>>>>>>> - Dan
>>>>>>>=20
>>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
>>>>>>>> Sent: 07 October, 2003 20:55
>>>>>>>> To: Forsberg Dan (NRC/Helsinki); pana@ietf.org
>>>>>>>> Subject: Re: [Pana] [issue19] Result-Code AVP values?
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>>> I think this is also an EAP question. What would be the EAP
>>>>>>>>>> behavior when
>>>>>>>>>> the NAS cannot recognize the EAP client identifier?
>>>>>>>>=20
>>>>>>>> I think this case would be handled by the following text from
>>>>>>>> the EAP spec:
>>>>>>>>=20
>>>>>>>>          Implementation Note: The peer MAY obtain the
>>>>>>>> Identity via user
>>>>>>>>          input.  It is suggested that the
>>> authenticator retry the
>>>>>>>>          Identity Request in the case of an invalid
>>> Identity or
>>>>>>>>          authentication failure to allow for potential typos
>>>>>>>> on the part
>>>>>>>>          of the user.  It is suggested that the Identity
>>>>> Request be
>>>>>>>>          retried a minimum of 3 times before terminating the
>>>>>>>>          authentication.  The Notification Request
>>> MAY be used to
>>>>>>>>          indicate an invalid authentication attempt prior to
>>>>>>>>          transmitting a new Identity Request
>>>>> (optionally, the failure
>>>>>>>>          MAY be indicated within the message of the new
>>>>>>>> Identity Request
>>>>>>>>          itself).
>>>>>>>>=20
>>>>>>>> ... And finally I think the EAP authenticator would send a
>>>>>>>> Failure message.
>>>>>>>>=20
>>>>>>>> Alper
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> Pana mailing list
>>>>>> Pana@ietf.org
>>>>>> https://www1.ietf.org/mailman/listinfo/pana
>>>>>=20
>>>=20
>=20


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



From pana-admin@ietf.org  Thu Oct 16 15:22:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18560
	for <pana-archive@lists.ietf.org>; Thu, 16 Oct 2003 15:22:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADhA-0004q0-KH; Thu, 16 Oct 2003 15:22:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADgl-0004pk-45
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 15:21:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18477
	for <pana@ietf.org>; Thu, 16 Oct 2003 15:21:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADgj-0000yC-00
	for pana@ietf.org; Thu, 16 Oct 2003 15:21:33 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADgi-0000y9-00
	for pana@ietf.org; Thu, 16 Oct 2003 15:21:33 -0400
Date: Thu, 16 Oct 2003 12:21:21 -0700
Subject: Re: [Pana] issue 23 and 25
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <yohba@tari.toshiba.com>
CC: <pana@ietf.org>
Message-ID: <BBB43DC1.A9A8%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA0143C5AF@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> There is no first and second. PANA borrows some AVPs from
> RADIUS/Diameter, which we don't want to change, thus the
> same codes. PANA has it's own AVPs, which we don't want to
> overlap with Diameter/Radius AVPs, thus same code space,
> but non-overlapping codes. PANA has it's own message types,
> which can be seen as command codes. These should not overlap
> with Radius/Diameter.

IMO, borrowing formats is good enough. There is no requirement that we also
have to live in the same code space. This non-requirement has issues as I
had outlined earlier... (see "Issue23" thread). Your last statement above is
not valid. 

> 
> The process uses two separate protocols, but benefits in
> many ways from having synergies between the protocols. To
> give the process a name, we can call it a AAA application.
> AAA application uses Diameter or Radius as the transport to
> the network and PANA towards the client. PANA has also it's
> transport (header processing) and application level stuff
> (session handling). There are of course other ways to see/
> think this, but AAA session and PANA session are very close
> to each other. PAA can't live without the AAA part. EAP is

PAA does not assume a AAA backend protocol. So, yes, PAA can live without
RADIUS/Diameter, and still run PANA.

> a tool to handle the authentication signaling, but doesn't
> "know" about sessions.

Alper


> 
> - Dan
> 
> 
>> -----Original Message-----
>> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
>> Sent: 15 October, 2003 21:23
>> To: Yoshihiro Ohba; Forsberg Dan (NRC/Helsinki)
>> Cc: pana@ietf.org
>> Subject: Re: [Pana] issue 23 and 25
>> 
>> 
>> 
>> 
>> First it was using the same codes for both PANA and Diameter.
>> Now it is
>> using non-overlapping codes. I still don't see why we have to
>> care about
>> these, and unnecessarily constraint ourselves. These two are separate
>> protocols. If a process uses both protocols, it better know
>> what protocol a
>> received message belongs to.
>> 
>> Alper
>> 
>> 
>>> On Wed, Oct 15, 2003 at 11:07:59AM +0300,
>> Dan.Forsberg@nokia.com wrote:
>>>> I mean the same code space, but different numbers so that
>>>> overlapping is not happening when processing PANA and AAA
>>>> messages at the same application level.
>>>> - Dan
>>> 
>>> That also works for me, as long as the same rule
>> consistently applies
>>> to both PANA message types and PANA AVP types.
>>> 
>>> Yoshihiro Ohba
>>> 
>>> 
>>>> 
>>>>> -----Original Message-----
>>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>>>> Sent: 14 October, 2003 21:18
>>>>> To: Forsberg Dan (NRC/Helsinki)
>>>>> Cc: yohba@tari.toshiba.com; pana@ietf.org
>>>>> Subject: Re: [Pana] issue 23 and 25
>>>>> 
>>>>> 
>>>>> On Tue, Oct 14, 2003 at 02:23:19PM +0300,
>>>>> Dan.Forsberg@nokia.com wrote:
>>>>>>> -----Original Message-----
>>>>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>>>>>> Sent: 14 October, 2003 00:28
>>>>>>> To: pana@ietf.org
>>>>>>> Subject: [Pana] issue 23 and 25
>>>>>>> 
>>>>>>> 
>>>>>>> There are two PANA draft -01 issues for which I'm not
>>>>> sure about the
>>>>>>> consensus.
>>>>>>> 
>>>>>>> Issue 23: PANA Message type/AVP numbers and Diameter command
>>>>>>> codes/AVPs
>>>>>> 
>>>>>> Let me give some background for this issue, since I submitted it.
>>>>>> 
>>>>>> One approach is that a NAS supports PANA functionality. A NAS
>>>>>> can be a Diameter/Radius client. To better support
>>>>> interworking with the
>>>>>> PANA and NAS functionality, it would be good to distinguish
>>>>> the command
>>>>>> code and message type numbers. This way for example PANA
>>>>> message header
>>>>>> parsing functionality can be added to a NAS almost as "link
>>>>> layer" and
>>>>>> the PANA session handling functionality can be "migrated"
>>>>> into the NAS.
>>>>> 
>>>>> This seems to suggest using different code space for
>> Diameter command
>>>>> codes and PANA message types, right?  What about using
>> different code
>>>>> space for Diameter AVP types and PANA AVP types?  I think the same
>>>>> justification is also applicable to PANA AVP types.
>>>>> 
>>>>> Yoshihiro Ohba
>>>>> 
>>> 
>>> _______________________________________________
>>> Pana mailing list
>>> Pana@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/pana
>>> 
>> 
>> 
> 
> 


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


From exim@www1.ietf.org  Thu Oct 16 15:22:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18575
	for <pana-archive@odin.ietf.org>; Thu, 16 Oct 2003 15:22:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADhE-0004qd-Cl
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 15:22:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9GJM4aG018634
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 15:22:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADhE-0004qT-5j
	for pana-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 15:22:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18519
	for <pana-web-archive@ietf.org>; Thu, 16 Oct 2003 15:21:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADhC-0000yU-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 15:22:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADhC-0000yR-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 15:22:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADhA-0004q0-KH; Thu, 16 Oct 2003 15:22:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AADgl-0004pk-45
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 15:21:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18477
	for <pana@ietf.org>; Thu, 16 Oct 2003 15:21:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADgj-0000yC-00
	for pana@ietf.org; Thu, 16 Oct 2003 15:21:33 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AADgi-0000y9-00
	for pana@ietf.org; Thu, 16 Oct 2003 15:21:33 -0400
Date: Thu, 16 Oct 2003 12:21:21 -0700
Subject: Re: [Pana] issue 23 and 25
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <yohba@tari.toshiba.com>
CC: <pana@ietf.org>
Message-ID: <BBB43DC1.A9A8%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA0143C5AF@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> There is no first and second. PANA borrows some AVPs from
> RADIUS/Diameter, which we don't want to change, thus the
> same codes. PANA has it's own AVPs, which we don't want to
> overlap with Diameter/Radius AVPs, thus same code space,
> but non-overlapping codes. PANA has it's own message types,
> which can be seen as command codes. These should not overlap
> with Radius/Diameter.

IMO, borrowing formats is good enough. There is no requirement that we also
have to live in the same code space. This non-requirement has issues as I
had outlined earlier... (see "Issue23" thread). Your last statement above is
not valid. 

> 
> The process uses two separate protocols, but benefits in
> many ways from having synergies between the protocols. To
> give the process a name, we can call it a AAA application.
> AAA application uses Diameter or Radius as the transport to
> the network and PANA towards the client. PANA has also it's
> transport (header processing) and application level stuff
> (session handling). There are of course other ways to see/
> think this, but AAA session and PANA session are very close
> to each other. PAA can't live without the AAA part. EAP is

PAA does not assume a AAA backend protocol. So, yes, PAA can live without
RADIUS/Diameter, and still run PANA.

> a tool to handle the authentication signaling, but doesn't
> "know" about sessions.

Alper


> 
> - Dan
> 
> 
>> -----Original Message-----
>> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
>> Sent: 15 October, 2003 21:23
>> To: Yoshihiro Ohba; Forsberg Dan (NRC/Helsinki)
>> Cc: pana@ietf.org
>> Subject: Re: [Pana] issue 23 and 25
>> 
>> 
>> 
>> 
>> First it was using the same codes for both PANA and Diameter.
>> Now it is
>> using non-overlapping codes. I still don't see why we have to
>> care about
>> these, and unnecessarily constraint ourselves. These two are separate
>> protocols. If a process uses both protocols, it better know
>> what protocol a
>> received message belongs to.
>> 
>> Alper
>> 
>> 
>>> On Wed, Oct 15, 2003 at 11:07:59AM +0300,
>> Dan.Forsberg@nokia.com wrote:
>>>> I mean the same code space, but different numbers so that
>>>> overlapping is not happening when processing PANA and AAA
>>>> messages at the same application level.
>>>> - Dan
>>> 
>>> That also works for me, as long as the same rule
>> consistently applies
>>> to both PANA message types and PANA AVP types.
>>> 
>>> Yoshihiro Ohba
>>> 
>>> 
>>>> 
>>>>> -----Original Message-----
>>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>>>> Sent: 14 October, 2003 21:18
>>>>> To: Forsberg Dan (NRC/Helsinki)
>>>>> Cc: yohba@tari.toshiba.com; pana@ietf.org
>>>>> Subject: Re: [Pana] issue 23 and 25
>>>>> 
>>>>> 
>>>>> On Tue, Oct 14, 2003 at 02:23:19PM +0300,
>>>>> Dan.Forsberg@nokia.com wrote:
>>>>>>> -----Original Message-----
>>>>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
>>>>>>> Sent: 14 October, 2003 00:28
>>>>>>> To: pana@ietf.org
>>>>>>> Subject: [Pana] issue 23 and 25
>>>>>>> 
>>>>>>> 
>>>>>>> There are two PANA draft -01 issues for which I'm not
>>>>> sure about the
>>>>>>> consensus.
>>>>>>> 
>>>>>>> Issue 23: PANA Message type/AVP numbers and Diameter command
>>>>>>> codes/AVPs
>>>>>> 
>>>>>> Let me give some background for this issue, since I submitted it.
>>>>>> 
>>>>>> One approach is that a NAS supports PANA functionality. A NAS
>>>>>> can be a Diameter/Radius client. To better support
>>>>> interworking with the
>>>>>> PANA and NAS functionality, it would be good to distinguish
>>>>> the command
>>>>>> code and message type numbers. This way for example PANA
>>>>> message header
>>>>>> parsing functionality can be added to a NAS almost as "link
>>>>> layer" and
>>>>>> the PANA session handling functionality can be "migrated"
>>>>> into the NAS.
>>>>> 
>>>>> This seems to suggest using different code space for
>> Diameter command
>>>>> codes and PANA message types, right?  What about using
>> different code
>>>>> space for Diameter AVP types and PANA AVP types?  I think the same
>>>>> justification is also applicable to PANA AVP types.
>>>>> 
>>>>> Yoshihiro Ohba
>>>>> 
>>> 
>>> _______________________________________________
>>> Pana mailing list
>>> Pana@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/pana
>>> 
>> 
>> 
> 
> 


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



From pana-admin@ietf.org  Thu Oct 16 20:06:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00945
	for <pana-archive@lists.ietf.org>; Thu, 16 Oct 2003 20:06:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAI81-0002rz-En; Thu, 16 Oct 2003 20:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAI77-0002qh-4P
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 20:05:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00931
	for <pana@ietf.org>; Thu, 16 Oct 2003 20:04:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAI75-0004Q1-00
	for pana@ietf.org; Thu, 16 Oct 2003 20:05:03 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAI74-0004Py-00
	for pana@ietf.org; Thu, 16 Oct 2003 20:05:02 -0400
Date: Thu, 16 Oct 2003 17:04:56 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBB48038.AA02%alper@docomolabs-usa.com>
In-Reply-To: <BBB47CFF.A9FD%alper@docomolabs-usa.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Re: New [issue25] Service Profile names
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


[I'm resending this messsage. Apparently we were using the old mailing list
and it started bouncing....]

On 10/16/03 4:51 PM, "Alper Yegin" <alper@docomolabs-usa.com> wrote:

> 
> Here is another attempt...
> 
> Assuming:
> - PAA may optionally include *-info in the PANA-start-request to "advertise"
> the availability of service providers to the user.
> - PaC may optionally include its choice of service providers in
> PANA-start-answer, which effects the AAA routing. In the absence of *-info,
> service selection and AAA routing is based on the client identifier used
> within EAP conversation.
> - PAA may optionally enable NAP-ISP authentication separation.
> - PaC may optionally perform separate NAP and ISP authentication.
> 
> 
> How about this:
> - PAA advertises auth separation capability by using S-flag in
> PANA-start-request. PaC communicates its desire to separate them using the
> same flag in the PANA-start-answer.
> 
> - If S-flag is not set in the request, there will be only one round of
> authentication. PaC can indicate its choice of NAP and ISP by including
> their *-info in the  PANA-start-answer. AAA routing will be based on the
> ISP choice. 
> 
> - If S-flag is set, there may be two rounds of authentication, depending on
> the PaC's preference.
> - If PaC wants to enable separate authentication, it should turn on the
>   S-flag in PANA-start-answer. In that case, at most one *-info may be
>   included at once, and it dictates the service provider selection.
> - If PaC does not care about separate authentication, it unsets the S-flag
>   in PANA-start-answer, and this is same as if PAA never set the S-flag.
> 
> Does this make sense?
> 
> Alper
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
>>> I was thinking something in terms of this:
>>> 
>>> - If only a NAP-info is included in the PANA-start-answer, that means the
>>> following authentication should be directed to particular NAP's AAA.
>>> - If only a ISP-info is included in the PANA-start-answer, that means the
>>> following authentication should be directed to particular ISP's AAA.
>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP client
>>> identifier may suggest. One *-info is included at a time when separate
>>> authentication will take place.
>> 
>> OK.
>> 
>>> 
>>> - If both NAP-info and ISP-info are included, that means only one
>>> authentication will take place. The *-info indicates the chosen service
>>> combination. The authentication request is forwarded to ISP's AAA.
>> 
>> It seems natural for this case that separate authentication will take
>> place with using particular NAP's AAA and ISP's AAA.
>> 
>>> 
>>> - If no *-info is included, that means the implicit selection depends on the
>>> EAP client identifier.
>> 
>> It seems natural for this case that only one authentication will
>> take place with the authentication request being forwarded to ISP's
>> AAA.
>> 
>>> 
>>> We might also modify the f-flag logic. Maybe we can fold that logic to
>>> PANA-start-request/answer exchange. PANA-start-request can signal the
>>> capability to provide separate auth along with the list of ISPs/NAP.
>>> PANA-start-answer can signal whether the PaC will do separate auths or not.
>>> A flag in the message header can deliver this capability/choice.
>> 
>> Or can we use *-info contained in PANA-start-{request,answer} for that
>> purpose instead of definig a new flag?
>> 
>> Yoshihiro Ohba
>> 
>> 
>>> 
>>> Comments?
>>> 
>>> Alper
>>> 
>>> 
>>> 
>>>> Here is the new text which reflects Alper's comments.
>>>> 
>>>> Yoshihiro Ohba
>>>> 
>>>> ---
>>>> In Section 4.2, change
>>>> 
>>>> From:
>>>> 
>>>> "  When a PaC receives the PANA-Start-Request message in response to
>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>  message. The PANA-Start-Answer message contains the initial sequence
>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
>>>>  the received Cookie as the PANA payload."
>>>> 
>>>> To:
>>>> 
>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
>>>>  AVP and zero or more ISP-Information AVPs to advertise the
>>>>  information on the NAP and/or ISPs.
>>>> 
>>>>  When a PaC receives the PANA-Start-Request message in response to
>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>  message if it wishes to enter the authentication phase.  The
>>>>  PANA-Start-Answer message contains the initial sequence numbers in
>>>>  the tseq and rseq fields of the PANA header, a copy of the received
>>>>  Cookie (if any) as the PANA payload.  If the received
>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
>>>>  received NAP-Information AVP and, if any, one of the received
>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
>>>>  the binding between the subsequent authentication and the NAP/ISP.
>>>>  If the PaC does not contain a NAP-Information AVP or an
>>>>  ISP-Information AVP, the EAP peer identity or some default
>>>>  information MAY be used to identify the binding."
>>>> 
>>>> 
>>>> In Section 9.3.3, change
>>>> 
>>>> from:
>>>> 
>>>> "
>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>                   [ Cookie ]
>>>>                 * [ AVP ]
>>>> "
>>>> 
>>>> to:
>>>> 
>>>> "
>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>                   [ Cookie ]
>>>>    [ NAP-Information ]
>>>>                 * [ ISP-Information ]
>>>>                 * [ AVP ]
>>>> "
>>>> 
>>>> 
>>>> In Section 9.3.4, change
>>>> 
>>>> from:
>>>> 
>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>                   [ Cookie ]
>>>>                 * [ AVP ]"
>>>> 
>>>> to:
>>>> 
>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>                   [ Cookie ]
>>>>    [ NAP-Information ]
>>>>                   [ ISP-Information ]
>>>>                 * [ AVP ]"
>>>> 
>>>> 
>>>> Add the following sections:
>>>> 
>>>> "9.4.9 NAP-Information AVP
>>>> 
>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
>>>> contains one globally unique identifier of the NAP in a
>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>> 
>>>>     NAP-Information ::= < AVP Header: 1029 >
>>>>                          { Provider-Identifier }
>>>>                          { Provider-Name }
>>>>                        * [ AVP ]
>>>> 
>>>> 
>>>> 9.4.10 ISP-Information AVP
>>>> 
>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
>>>> contains one globally unique identifier of the ISP in a
>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>> 
>>>>     ISP-Information ::= < AVP Header: 1030 >
>>>>                          { Provider-Identifier }
>>>>                          { Provider-Name }
>>>>                        * [ AVP ]
>>>> 
>>>> 
>>>> 9.4.11 Provider-Identifier AVP
>>>> 
>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
>>>> and contains an IANA assigned "SMI Network Management Private
>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
>>>> 
>>>> 
>>>> 9.4.12 Provider-Name AVP
>>>> 
>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
>>>> contains the UTF8-encoded name of the provider."
>>>> 
>>>> 
>>>> 
>>> 
>> 
>> 


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


From exim@www1.ietf.org  Thu Oct 16 20:06:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00960
	for <pana-archive@odin.ietf.org>; Thu, 16 Oct 2003 20:06:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAI83-0002sb-GR
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 20:06:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9H063nf011068
	for pana-archive@odin.ietf.org; Thu, 16 Oct 2003 20:06:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAI83-0002sR-BT
	for pana-web-archive@optimus.ietf.org; Thu, 16 Oct 2003 20:06:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00936
	for <pana-web-archive@ietf.org>; Thu, 16 Oct 2003 20:05:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAI81-0004QG-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 20:06:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAI80-0004QD-00
	for pana-web-archive@ietf.org; Thu, 16 Oct 2003 20:06:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAI81-0002rz-En; Thu, 16 Oct 2003 20:06:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAI77-0002qh-4P
	for pana@optimus.ietf.org; Thu, 16 Oct 2003 20:05:05 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00931
	for <pana@ietf.org>; Thu, 16 Oct 2003 20:04:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAI75-0004Q1-00
	for pana@ietf.org; Thu, 16 Oct 2003 20:05:03 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAI74-0004Py-00
	for pana@ietf.org; Thu, 16 Oct 2003 20:05:02 -0400
Date: Thu, 16 Oct 2003 17:04:56 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBB48038.AA02%alper@docomolabs-usa.com>
In-Reply-To: <BBB47CFF.A9FD%alper@docomolabs-usa.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Re: New [issue25] Service Profile names
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


[I'm resending this messsage. Apparently we were using the old mailing list
and it started bouncing....]

On 10/16/03 4:51 PM, "Alper Yegin" <alper@docomolabs-usa.com> wrote:

> 
> Here is another attempt...
> 
> Assuming:
> - PAA may optionally include *-info in the PANA-start-request to "advertise"
> the availability of service providers to the user.
> - PaC may optionally include its choice of service providers in
> PANA-start-answer, which effects the AAA routing. In the absence of *-info,
> service selection and AAA routing is based on the client identifier used
> within EAP conversation.
> - PAA may optionally enable NAP-ISP authentication separation.
> - PaC may optionally perform separate NAP and ISP authentication.
> 
> 
> How about this:
> - PAA advertises auth separation capability by using S-flag in
> PANA-start-request. PaC communicates its desire to separate them using the
> same flag in the PANA-start-answer.
> 
> - If S-flag is not set in the request, there will be only one round of
> authentication. PaC can indicate its choice of NAP and ISP by including
> their *-info in the  PANA-start-answer. AAA routing will be based on the
> ISP choice. 
> 
> - If S-flag is set, there may be two rounds of authentication, depending on
> the PaC's preference.
> - If PaC wants to enable separate authentication, it should turn on the
>   S-flag in PANA-start-answer. In that case, at most one *-info may be
>   included at once, and it dictates the service provider selection.
> - If PaC does not care about separate authentication, it unsets the S-flag
>   in PANA-start-answer, and this is same as if PAA never set the S-flag.
> 
> Does this make sense?
> 
> Alper
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
>>> I was thinking something in terms of this:
>>> 
>>> - If only a NAP-info is included in the PANA-start-answer, that means the
>>> following authentication should be directed to particular NAP's AAA.
>>> - If only a ISP-info is included in the PANA-start-answer, that means the
>>> following authentication should be directed to particular ISP's AAA.
>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP client
>>> identifier may suggest. One *-info is included at a time when separate
>>> authentication will take place.
>> 
>> OK.
>> 
>>> 
>>> - If both NAP-info and ISP-info are included, that means only one
>>> authentication will take place. The *-info indicates the chosen service
>>> combination. The authentication request is forwarded to ISP's AAA.
>> 
>> It seems natural for this case that separate authentication will take
>> place with using particular NAP's AAA and ISP's AAA.
>> 
>>> 
>>> - If no *-info is included, that means the implicit selection depends on the
>>> EAP client identifier.
>> 
>> It seems natural for this case that only one authentication will
>> take place with the authentication request being forwarded to ISP's
>> AAA.
>> 
>>> 
>>> We might also modify the f-flag logic. Maybe we can fold that logic to
>>> PANA-start-request/answer exchange. PANA-start-request can signal the
>>> capability to provide separate auth along with the list of ISPs/NAP.
>>> PANA-start-answer can signal whether the PaC will do separate auths or not.
>>> A flag in the message header can deliver this capability/choice.
>> 
>> Or can we use *-info contained in PANA-start-{request,answer} for that
>> purpose instead of definig a new flag?
>> 
>> Yoshihiro Ohba
>> 
>> 
>>> 
>>> Comments?
>>> 
>>> Alper
>>> 
>>> 
>>> 
>>>> Here is the new text which reflects Alper's comments.
>>>> 
>>>> Yoshihiro Ohba
>>>> 
>>>> ---
>>>> In Section 4.2, change
>>>> 
>>>> From:
>>>> 
>>>> "  When a PaC receives the PANA-Start-Request message in response to
>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>  message. The PANA-Start-Answer message contains the initial sequence
>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
>>>>  the received Cookie as the PANA payload."
>>>> 
>>>> To:
>>>> 
>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
>>>>  AVP and zero or more ISP-Information AVPs to advertise the
>>>>  information on the NAP and/or ISPs.
>>>> 
>>>>  When a PaC receives the PANA-Start-Request message in response to
>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>  message if it wishes to enter the authentication phase.  The
>>>>  PANA-Start-Answer message contains the initial sequence numbers in
>>>>  the tseq and rseq fields of the PANA header, a copy of the received
>>>>  Cookie (if any) as the PANA payload.  If the received
>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
>>>>  received NAP-Information AVP and, if any, one of the received
>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
>>>>  the binding between the subsequent authentication and the NAP/ISP.
>>>>  If the PaC does not contain a NAP-Information AVP or an
>>>>  ISP-Information AVP, the EAP peer identity or some default
>>>>  information MAY be used to identify the binding."
>>>> 
>>>> 
>>>> In Section 9.3.3, change
>>>> 
>>>> from:
>>>> 
>>>> "
>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>                   [ Cookie ]
>>>>                 * [ AVP ]
>>>> "
>>>> 
>>>> to:
>>>> 
>>>> "
>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>                   [ Cookie ]
>>>>    [ NAP-Information ]
>>>>                 * [ ISP-Information ]
>>>>                 * [ AVP ]
>>>> "
>>>> 
>>>> 
>>>> In Section 9.3.4, change
>>>> 
>>>> from:
>>>> 
>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>                   [ Cookie ]
>>>>                 * [ AVP ]"
>>>> 
>>>> to:
>>>> 
>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>                   [ Cookie ]
>>>>    [ NAP-Information ]
>>>>                   [ ISP-Information ]
>>>>                 * [ AVP ]"
>>>> 
>>>> 
>>>> Add the following sections:
>>>> 
>>>> "9.4.9 NAP-Information AVP
>>>> 
>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
>>>> contains one globally unique identifier of the NAP in a
>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>> 
>>>>     NAP-Information ::= < AVP Header: 1029 >
>>>>                          { Provider-Identifier }
>>>>                          { Provider-Name }
>>>>                        * [ AVP ]
>>>> 
>>>> 
>>>> 9.4.10 ISP-Information AVP
>>>> 
>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
>>>> contains one globally unique identifier of the ISP in a
>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>> 
>>>>     ISP-Information ::= < AVP Header: 1030 >
>>>>                          { Provider-Identifier }
>>>>                          { Provider-Name }
>>>>                        * [ AVP ]
>>>> 
>>>> 
>>>> 9.4.11 Provider-Identifier AVP
>>>> 
>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
>>>> and contains an IANA assigned "SMI Network Management Private
>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
>>>> 
>>>> 
>>>> 9.4.12 Provider-Name AVP
>>>> 
>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
>>>> contains the UTF8-encoded name of the provider."
>>>> 
>>>> 
>>>> 
>>> 
>> 
>> 


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



From pana-admin@ietf.org  Fri Oct 17 03:12:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21861
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 03:12:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAOmF-00040V-7k; Fri, 17 Oct 2003 03:11:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAOlz-000404-OK
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 03:11:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21846
	for <pana@ietf.org>; Fri, 17 Oct 2003 03:11:32 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAOlv-0007ba-00
	for pana@ietf.org; Fri, 17 Oct 2003 03:11:39 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAOlu-0007bX-00
	for pana@ietf.org; Fri, 17 Oct 2003 03:11:38 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9H7BRd17691
	for <pana@ietf.org>; Fri, 17 Oct 2003 10:11:35 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6555efdc47ac158f25534@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Fri, 17 Oct 2003 10:11:19 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 17 Oct 2003 10:11:18 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Oct 2003 10:11:18 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D80@esebe008.ntc.nokia.com>
Thread-Topic: [issue37] Unknown realm problem propagation
Thread-Index: AcOUfQYkAKp1kbpIQ3Sx8tPzPeX4qQAAMIhA
To: <pana@ietf.org>
X-OriginalArrivalTime: 17 Oct 2003 07:11:18.0552 (UTC) FILETIME=[DC5EA980:01C3947D]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue37] Unknown realm problem propagation
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

New submission from Dan Forsberg <dan.forsberg@nokia.com>:

From Yoshihiro Ohba:
--------------------
I would suggest creating a new PANA issue on how to handle the case in
which an EAP authenticator on the NAS fails to authenticate an EAP
peer without generating an EAP message.  We can continue the
discussion on whether AAA error needs to be leaked to PANA in the new
issue.


----------
category: Technical
document: draft-ietf-pana-pana-xx.txt
messages: 129
nosy: dforsber
priority: Should Fix
status: Pending
title: Unknown realm problem propagation
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue37
________________________________________________

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


From exim@www1.ietf.org  Fri Oct 17 03:12:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21876
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 03:12:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAOmI-00041B-1L
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 03:12:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9H7C1Fe015441
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 03:12:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAOmH-00040y-RP
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 03:12:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21851
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 03:11:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAOmF-0007bg-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 03:11:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAOmF-0007bd-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 03:11:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAOmF-00040V-7k; Fri, 17 Oct 2003 03:11:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAOlz-000404-OK
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 03:11:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21846
	for <pana@ietf.org>; Fri, 17 Oct 2003 03:11:32 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAOlv-0007ba-00
	for pana@ietf.org; Fri, 17 Oct 2003 03:11:39 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAOlu-0007bX-00
	for pana@ietf.org; Fri, 17 Oct 2003 03:11:38 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9H7BRd17691
	for <pana@ietf.org>; Fri, 17 Oct 2003 10:11:35 +0300 (EET DST)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6555efdc47ac158f25534@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Fri, 17 Oct 2003 10:11:19 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 17 Oct 2003 10:11:18 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Oct 2003 10:11:18 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D80@esebe008.ntc.nokia.com>
Thread-Topic: [issue37] Unknown realm problem propagation
Thread-Index: AcOUfQYkAKp1kbpIQ3Sx8tPzPeX4qQAAMIhA
To: <pana@ietf.org>
X-OriginalArrivalTime: 17 Oct 2003 07:11:18.0552 (UTC) FILETIME=[DC5EA980:01C3947D]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [issue37] Unknown realm problem propagation
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

New submission from Dan Forsberg <dan.forsberg@nokia.com>:

From Yoshihiro Ohba:
--------------------
I would suggest creating a new PANA issue on how to handle the case in
which an EAP authenticator on the NAS fails to authenticate an EAP
peer without generating an EAP message.  We can continue the
discussion on whether AAA error needs to be leaked to PANA in the new
issue.


----------
category: Technical
document: draft-ietf-pana-pana-xx.txt
messages: 129
nosy: dforsber
priority: Should Fix
status: Pending
title: Unknown realm problem propagation
________________________________________________
PANA Issues <pana_issues@danforsberg.info>
http://danforsberg.info:8080/pana-issues/issue37
________________________________________________

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



From pana-admin@ietf.org  Fri Oct 17 03:27:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22180
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 03:27:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAP0o-0004Un-1v; Fri, 17 Oct 2003 03:27:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAP06-0004Sz-D9
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 03:26:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22138
	for <pana@ietf.org>; Fri, 17 Oct 2003 03:26:09 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAP03-0007iF-00
	for pana@ietf.org; Fri, 17 Oct 2003 03:26:15 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAP03-0007iC-00
	for pana@ietf.org; Fri, 17 Oct 2003 03:26:15 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9H7QFd06425
	for <pana@ietf.org>; Fri, 17 Oct 2003 10:26:16 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6555fd7d1cac158f25534@esvir05nok.ntc.nokia.com>;
 Fri, 17 Oct 2003 10:26:12 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 17 Oct 2003 10:26:12 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 17 Oct 2003 10:26:11 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] issue 23 and 25
Date: Fri, 17 Oct 2003 10:26:11 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5B1@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] issue 23 and 25
Thread-Index: AcOUGtrZo+YtSaSFR92WY8nrDfp5qgAY91CQ
To: <alper@docomolabs-usa.com>, <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 17 Oct 2003 07:26:11.0999 (UTC) FILETIME=[F0E7DAF0:01C3947F]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Ok, thanks. This was merely an attempt to simplify the overall=20
architecture and implementation requirements.
- Dan

> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 16 October, 2003 22:21
> To: Forsberg Dan (NRC/Helsinki); yohba@tari.toshiba.com
> Cc: pana@ietf.org
> Subject: Re: [Pana] issue 23 and 25
>=20
>=20
> > There is no first and second. PANA borrows some AVPs from
> > RADIUS/Diameter, which we don't want to change, thus the
> > same codes. PANA has it's own AVPs, which we don't want to
> > overlap with Diameter/Radius AVPs, thus same code space,
> > but non-overlapping codes. PANA has it's own message types,
> > which can be seen as command codes. These should not overlap
> > with Radius/Diameter.
>=20
> IMO, borrowing formats is good enough. There is no=20
> requirement that we also
> have to live in the same code space. This non-requirement has=20
> issues as I
> had outlined earlier... (see "Issue23" thread). Your last=20
> statement above is
> not valid.=20
>=20
> >=20
> > The process uses two separate protocols, but benefits in
> > many ways from having synergies between the protocols. To
> > give the process a name, we can call it a AAA application.
> > AAA application uses Diameter or Radius as the transport to
> > the network and PANA towards the client. PANA has also it's
> > transport (header processing) and application level stuff
> > (session handling). There are of course other ways to see/
> > think this, but AAA session and PANA session are very close
> > to each other. PAA can't live without the AAA part. EAP is
>=20
> PAA does not assume a AAA backend protocol. So, yes, PAA can=20
> live without
> RADIUS/Diameter, and still run PANA.
>=20
> > a tool to handle the authentication signaling, but doesn't
> > "know" about sessions.
>=20
> Alper
>=20
>=20
> >=20
> > - Dan
> >=20
> >=20
> >> -----Original Message-----
> >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> >> Sent: 15 October, 2003 21:23
> >> To: Yoshihiro Ohba; Forsberg Dan (NRC/Helsinki)
> >> Cc: pana@ietf.org
> >> Subject: Re: [Pana] issue 23 and 25
> >>=20
> >>=20
> >>=20
> >>=20
> >> First it was using the same codes for both PANA and Diameter.
> >> Now it is
> >> using non-overlapping codes. I still don't see why we have to
> >> care about
> >> these, and unnecessarily constraint ourselves. These two=20
> are separate
> >> protocols. If a process uses both protocols, it better know
> >> what protocol a
> >> received message belongs to.
> >>=20
> >> Alper
> >>=20
> >>=20
> >>> On Wed, Oct 15, 2003 at 11:07:59AM +0300,
> >> Dan.Forsberg@nokia.com wrote:
> >>>> I mean the same code space, but different numbers so that
> >>>> overlapping is not happening when processing PANA and AAA
> >>>> messages at the same application level.
> >>>> - Dan
> >>>=20
> >>> That also works for me, as long as the same rule
> >> consistently applies
> >>> to both PANA message types and PANA AVP types.
> >>>=20
> >>> Yoshihiro Ohba
> >>>=20
> >>>=20
> >>>>=20
> >>>>> -----Original Message-----
> >>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> >>>>> Sent: 14 October, 2003 21:18
> >>>>> To: Forsberg Dan (NRC/Helsinki)
> >>>>> Cc: yohba@tari.toshiba.com; pana@ietf.org
> >>>>> Subject: Re: [Pana] issue 23 and 25
> >>>>>=20
> >>>>>=20
> >>>>> On Tue, Oct 14, 2003 at 02:23:19PM +0300,
> >>>>> Dan.Forsberg@nokia.com wrote:
> >>>>>>> -----Original Message-----
> >>>>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> >>>>>>> Sent: 14 October, 2003 00:28
> >>>>>>> To: pana@ietf.org
> >>>>>>> Subject: [Pana] issue 23 and 25
> >>>>>>>=20
> >>>>>>>=20
> >>>>>>> There are two PANA draft -01 issues for which I'm not
> >>>>> sure about the
> >>>>>>> consensus.
> >>>>>>>=20
> >>>>>>> Issue 23: PANA Message type/AVP numbers and Diameter command
> >>>>>>> codes/AVPs
> >>>>>>=20
> >>>>>> Let me give some background for this issue, since I=20
> submitted it.
> >>>>>>=20
> >>>>>> One approach is that a NAS supports PANA functionality. A NAS
> >>>>>> can be a Diameter/Radius client. To better support
> >>>>> interworking with the
> >>>>>> PANA and NAS functionality, it would be good to distinguish
> >>>>> the command
> >>>>>> code and message type numbers. This way for example PANA
> >>>>> message header
> >>>>>> parsing functionality can be added to a NAS almost as "link
> >>>>> layer" and
> >>>>>> the PANA session handling functionality can be "migrated"
> >>>>> into the NAS.
> >>>>>=20
> >>>>> This seems to suggest using different code space for
> >> Diameter command
> >>>>> codes and PANA message types, right?  What about using
> >> different code
> >>>>> space for Diameter AVP types and PANA AVP types?  I=20
> think the same
> >>>>> justification is also applicable to PANA AVP types.
> >>>>>=20
> >>>>> Yoshihiro Ohba
> >>>>>=20
> >>>=20
> >>> _______________________________________________
> >>> Pana mailing list
> >>> Pana@ietf.org
> >>> https://www1.ietf.org/mailman/listinfo/pana
> >>>=20
> >>=20
> >>=20
> >=20
> >=20
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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


From exim@www1.ietf.org  Fri Oct 17 03:27:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22195
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 03:27:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAP0q-0004VV-FN
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 03:27:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9H7R4Mo017324
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 03:27:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAP0p-0004VE-V4
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 03:27:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22160
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 03:26:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAP0n-0007ig-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 03:27:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAP0n-0007id-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 03:27:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAP0o-0004Un-1v; Fri, 17 Oct 2003 03:27:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAP06-0004Sz-D9
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 03:26:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22138
	for <pana@ietf.org>; Fri, 17 Oct 2003 03:26:09 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAP03-0007iF-00
	for pana@ietf.org; Fri, 17 Oct 2003 03:26:15 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAP03-0007iC-00
	for pana@ietf.org; Fri, 17 Oct 2003 03:26:15 -0400
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9H7QFd06425
	for <pana@ietf.org>; Fri, 17 Oct 2003 10:26:16 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6555fd7d1cac158f25534@esvir05nok.ntc.nokia.com>;
 Fri, 17 Oct 2003 10:26:12 +0300
Received: from esebh005.NOE.Nokia.com ([172.21.138.86]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 17 Oct 2003 10:26:12 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 17 Oct 2003 10:26:11 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
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] issue 23 and 25
Date: Fri, 17 Oct 2003 10:26:11 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5B1@esebe008.ntc.nokia.com>
Thread-Topic: [Pana] issue 23 and 25
Thread-Index: AcOUGtrZo+YtSaSFR92WY8nrDfp5qgAY91CQ
To: <alper@docomolabs-usa.com>, <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
X-OriginalArrivalTime: 17 Oct 2003 07:26:11.0999 (UTC) FILETIME=[F0E7DAF0:01C3947F]
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Ok, thanks. This was merely an attempt to simplify the overall=20
architecture and implementation requirements.
- Dan

> -----Original Message-----
> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> Sent: 16 October, 2003 22:21
> To: Forsberg Dan (NRC/Helsinki); yohba@tari.toshiba.com
> Cc: pana@ietf.org
> Subject: Re: [Pana] issue 23 and 25
>=20
>=20
> > There is no first and second. PANA borrows some AVPs from
> > RADIUS/Diameter, which we don't want to change, thus the
> > same codes. PANA has it's own AVPs, which we don't want to
> > overlap with Diameter/Radius AVPs, thus same code space,
> > but non-overlapping codes. PANA has it's own message types,
> > which can be seen as command codes. These should not overlap
> > with Radius/Diameter.
>=20
> IMO, borrowing formats is good enough. There is no=20
> requirement that we also
> have to live in the same code space. This non-requirement has=20
> issues as I
> had outlined earlier... (see "Issue23" thread). Your last=20
> statement above is
> not valid.=20
>=20
> >=20
> > The process uses two separate protocols, but benefits in
> > many ways from having synergies between the protocols. To
> > give the process a name, we can call it a AAA application.
> > AAA application uses Diameter or Radius as the transport to
> > the network and PANA towards the client. PANA has also it's
> > transport (header processing) and application level stuff
> > (session handling). There are of course other ways to see/
> > think this, but AAA session and PANA session are very close
> > to each other. PAA can't live without the AAA part. EAP is
>=20
> PAA does not assume a AAA backend protocol. So, yes, PAA can=20
> live without
> RADIUS/Diameter, and still run PANA.
>=20
> > a tool to handle the authentication signaling, but doesn't
> > "know" about sessions.
>=20
> Alper
>=20
>=20
> >=20
> > - Dan
> >=20
> >=20
> >> -----Original Message-----
> >> From: ext Alper Yegin [mailto:alper@docomolabs-usa.com]
> >> Sent: 15 October, 2003 21:23
> >> To: Yoshihiro Ohba; Forsberg Dan (NRC/Helsinki)
> >> Cc: pana@ietf.org
> >> Subject: Re: [Pana] issue 23 and 25
> >>=20
> >>=20
> >>=20
> >>=20
> >> First it was using the same codes for both PANA and Diameter.
> >> Now it is
> >> using non-overlapping codes. I still don't see why we have to
> >> care about
> >> these, and unnecessarily constraint ourselves. These two=20
> are separate
> >> protocols. If a process uses both protocols, it better know
> >> what protocol a
> >> received message belongs to.
> >>=20
> >> Alper
> >>=20
> >>=20
> >>> On Wed, Oct 15, 2003 at 11:07:59AM +0300,
> >> Dan.Forsberg@nokia.com wrote:
> >>>> I mean the same code space, but different numbers so that
> >>>> overlapping is not happening when processing PANA and AAA
> >>>> messages at the same application level.
> >>>> - Dan
> >>>=20
> >>> That also works for me, as long as the same rule
> >> consistently applies
> >>> to both PANA message types and PANA AVP types.
> >>>=20
> >>> Yoshihiro Ohba
> >>>=20
> >>>=20
> >>>>=20
> >>>>> -----Original Message-----
> >>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> >>>>> Sent: 14 October, 2003 21:18
> >>>>> To: Forsberg Dan (NRC/Helsinki)
> >>>>> Cc: yohba@tari.toshiba.com; pana@ietf.org
> >>>>> Subject: Re: [Pana] issue 23 and 25
> >>>>>=20
> >>>>>=20
> >>>>> On Tue, Oct 14, 2003 at 02:23:19PM +0300,
> >>>>> Dan.Forsberg@nokia.com wrote:
> >>>>>>> -----Original Message-----
> >>>>>>> From: ext Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> >>>>>>> Sent: 14 October, 2003 00:28
> >>>>>>> To: pana@ietf.org
> >>>>>>> Subject: [Pana] issue 23 and 25
> >>>>>>>=20
> >>>>>>>=20
> >>>>>>> There are two PANA draft -01 issues for which I'm not
> >>>>> sure about the
> >>>>>>> consensus.
> >>>>>>>=20
> >>>>>>> Issue 23: PANA Message type/AVP numbers and Diameter command
> >>>>>>> codes/AVPs
> >>>>>>=20
> >>>>>> Let me give some background for this issue, since I=20
> submitted it.
> >>>>>>=20
> >>>>>> One approach is that a NAS supports PANA functionality. A NAS
> >>>>>> can be a Diameter/Radius client. To better support
> >>>>> interworking with the
> >>>>>> PANA and NAS functionality, it would be good to distinguish
> >>>>> the command
> >>>>>> code and message type numbers. This way for example PANA
> >>>>> message header
> >>>>>> parsing functionality can be added to a NAS almost as "link
> >>>>> layer" and
> >>>>>> the PANA session handling functionality can be "migrated"
> >>>>> into the NAS.
> >>>>>=20
> >>>>> This seems to suggest using different code space for
> >> Diameter command
> >>>>> codes and PANA message types, right?  What about using
> >> different code
> >>>>> space for Diameter AVP types and PANA AVP types?  I=20
> think the same
> >>>>> justification is also applicable to PANA AVP types.
> >>>>>=20
> >>>>> Yoshihiro Ohba
> >>>>>=20
> >>>=20
> >>> _______________________________________________
> >>> Pana mailing list
> >>> Pana@ietf.org
> >>> https://www1.ietf.org/mailman/listinfo/pana
> >>>=20
> >>=20
> >>=20
> >=20
> >=20
>=20
>=20
> _______________________________________________
> Pana mailing list
> Pana@ietf.org
> https://www1.ietf.org/mailman/listinfo/pana
>=20

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



From pana-admin@ietf.org  Fri Oct 17 08:03:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29027
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 08:03:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AATJt-0000Qh-9e; Fri, 17 Oct 2003 08:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AATJB-0000Q3-Mf
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 08:02:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28981
	for <pana@ietf.org>; Fri, 17 Oct 2003 08:02:08 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AATJA-0002gq-00
	for pana@ietf.org; Fri, 17 Oct 2003 08:02:16 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AATJA-0002gm-00
	for pana@ietf.org; Fri, 17 Oct 2003 08:02:16 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9HC2Fd16485
	for <pana@ietf.org>; Fri, 17 Oct 2003 15:02:15 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6556fa3414ac158f21081@esvir01nok.ntc.nokia.com> for <pana@ietf.org>;
 Fri, 17 Oct 2003 15:02:14 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 17 Oct 2003 15:02:13 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Oct 2003 15:02:02 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D85@esebe008.ntc.nokia.com>
Thread-Topic: about issue31
Thread-Index: AcOUpnnDXczXXAagT+65LjNCtrjQuA==
To: <pana@ietf.org>
X-OriginalArrivalTime: 17 Oct 2003 12:02:13.0757 (UTC) FILETIME=[807B92D0:01C394A6]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] about issue31
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi,

How are the sequence numbers handled in this case? Does =
PANA-PAA-Discover=20
message contain 0,0 or x,y?

Current issue31 suggestion:

   "When a PaC wants to initiate EAP-based re-authentication, it sends
   a unicast PANA-PAA-Discovery message to the PAA.  This message MUST
   contain a Session-Id AVP which is used for identifying the PANA
   session on the PAA. If the PAA already has an established PANA
   session for the PaC with the matching identifier, it sends a
   PANA-Auth-Request message containing the same identifier to start
   an authentication phase.  If the PAA can not recognize the session
   identifier, it proceeds with regular authentication by sending back
   PANA-Start-Request.  When the PAA initiates EAP-based
   re-authentication, it sends a PANA-Auth-Request message containing
   the session identifier for the PaC to enter an authentication
   phase. PAA SHOULD initiate EAP authentication before the current
   session lifetime expires."


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


From exim@www1.ietf.org  Fri Oct 17 08:03:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29042
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 08:03:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AATJv-0000Ra-Bg
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 08:03:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HC33LQ001705
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 08:03:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AATJv-0000RQ-7u
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 08:03:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29018
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 08:02:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AATJu-0002hP-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 08:03:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AATJt-0002hM-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 08:03:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AATJt-0000Qh-9e; Fri, 17 Oct 2003 08:03:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AATJB-0000Q3-Mf
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 08:02:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28981
	for <pana@ietf.org>; Fri, 17 Oct 2003 08:02:08 -0400 (EDT)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AATJA-0002gq-00
	for pana@ietf.org; Fri, 17 Oct 2003 08:02:16 -0400
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AATJA-0002gm-00
	for pana@ietf.org; Fri, 17 Oct 2003 08:02:16 -0400
Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9HC2Fd16485
	for <pana@ietf.org>; Fri, 17 Oct 2003 15:02:15 +0300 (EET DST)
Received: from esebh003.NOE.Nokia.com (unverified) by esvir01nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6556fa3414ac158f21081@esvir01nok.ntc.nokia.com> for <pana@ietf.org>;
 Fri, 17 Oct 2003 15:02:14 +0300
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh003.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6139);
	 Fri, 17 Oct 2003 15:02:13 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Oct 2003 15:02:02 +0300
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6D85@esebe008.ntc.nokia.com>
Thread-Topic: about issue31
Thread-Index: AcOUpnnDXczXXAagT+65LjNCtrjQuA==
To: <pana@ietf.org>
X-OriginalArrivalTime: 17 Oct 2003 12:02:13.0757 (UTC) FILETIME=[807B92D0:01C394A6]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] about issue31
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

How are the sequence numbers handled in this case? Does =
PANA-PAA-Discover=20
message contain 0,0 or x,y?

Current issue31 suggestion:

   "When a PaC wants to initiate EAP-based re-authentication, it sends
   a unicast PANA-PAA-Discovery message to the PAA.  This message MUST
   contain a Session-Id AVP which is used for identifying the PANA
   session on the PAA. If the PAA already has an established PANA
   session for the PaC with the matching identifier, it sends a
   PANA-Auth-Request message containing the same identifier to start
   an authentication phase.  If the PAA can not recognize the session
   identifier, it proceeds with regular authentication by sending back
   PANA-Start-Request.  When the PAA initiates EAP-based
   re-authentication, it sends a PANA-Auth-Request message containing
   the session identifier for the PaC to enter an authentication
   phase. PAA SHOULD initiate EAP authentication before the current
   session lifetime expires."


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



From pana-admin@ietf.org  Fri Oct 17 11:09:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05651
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 11:09:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWDt-0001Fq-5B; Fri, 17 Oct 2003 11:09:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWDq-0001FX-B4
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 11:08:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05640
	for <pana@ietf.org>; Fri, 17 Oct 2003 11:08:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWDn-0004Ee-00
	for pana@ietf.org; Fri, 17 Oct 2003 11:08:55 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWDm-0004Eb-00
	for pana@ietf.org; Fri, 17 Oct 2003 11:08:55 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9HF8nF1023730;
	Sat, 18 Oct 2003 00:08:49 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9HF8nQb028498;
	Sat, 18 Oct 2003 00:08:49 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id AAA28497 ; Sat, 18 Oct 2003 00:08:49 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA13295; Sat, 18 Oct 2003 00:08:49 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA05820; Sat, 18 Oct 2003 00:08:48 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9HF8mib008794;
	Sat, 18 Oct 2003 00:08:48 +0900 (JST)
Received: from steelhead ([159.119.168.142]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMW00M4TQ2MQ4@tsbpo1.po.toshiba.co.jp>; Sat,
 18 Oct 2003 00:08:47 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAWCz-00052x-00; Fri, 17 Oct 2003 08:08:05 -0700
Date: Fri, 17 Oct 2003 08:08:05 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
In-reply-to: <20031017150221.GF14788@steelhead>
To: Alper Yegin <alper@docomolabs-usa.com>,
        Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Message-id: <20031017150805.GG14788@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031014213838.GA6092@steelhead>
 <BBB47CFF.A9FD%alper@docomolabs-usa.com> <20031017150221.GF14788@steelhead>
Subject: [Pana] Re: New [issue25] Service Profile names
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

I forward my reply to the new list.

Yoshihiro Ohba


On Fri, Oct 17, 2003 at 08:02:21AM -0700,  wrote:
> On Thu, Oct 16, 2003 at 04:51:11PM -0700, Alper Yegin wrote:
> > 
> > Here is another attempt...
> > 
> > Assuming:
> > - PAA may optionally include *-info in the PANA-start-request to "advertise"
> > the availability of service providers to the user.
> > - PaC may optionally include its choice of service providers in
> > PANA-start-answer, which effects the AAA routing. In the absence of *-info,
> > service selection and AAA routing is based on the client identifier used
> > within EAP conversation.
> > - PAA may optionally enable NAP-ISP authentication separation.
> > - PaC may optionally perform separate NAP and ISP authentication.
> 
> OK.
> 
> >  
> > 
> > How about this:
> > - PAA advertises auth separation capability by using S-flag in
> > PANA-start-request. PaC communicates its desire to separate them using the
> > same flag in the PANA-start-answer.
> 
> OK.
> 
> > 
> > - If S-flag is not set in the request, there will be only one round of
> >   authentication. PaC can indicate its choice of NAP and ISP by including
> >   their *-info in the  PANA-start-answer. AAA routing will be based on the
> >   ISP choice. 
> 
> OK.
> 
> > 
> > - If S-flag is set, there may be two rounds of authentication, depending on
> >   the PaC's preference.
> >   - If PaC wants to enable separate authentication, it should turn on the
> >     S-flag in PANA-start-answer. In that case, at most one *-info may be
> >     included at once, and it dictates the service provider selection.
> 
> What does the above sentense mean?
> 
> - Either one ISP-info or one NAP-info may be included.
> 
> - One NAP-info and/or one ISP-info may be included.
> 
> (I guess you mean the latter.)
> 
> In addition, I'm currently assuming that one PAA is associated with a
> single NAP. In this case, including NAP-info in the answer may be
> redundant.
> 
> >   - If PaC does not care about separate authentication, it unsets the S-flag
> >     in PANA-start-answer, and this is same as if PAA never set the S-flag.
> 
> OK.
> 
> Yoshihiro Ohba
> 
> > 
> > Does this make sense?
> > 
> > Alper
> > 
> > 
> > 
> >  
> > 
> > 
> >  
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > > On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
> > >> I was thinking something in terms of this:
> > >> 
> > >> - If only a NAP-info is included in the PANA-start-answer, that means the
> > >> following authentication should be directed to particular NAP's AAA.
> > >> - If only a ISP-info is included in the PANA-start-answer, that means the
> > >> following authentication should be directed to particular ISP's AAA.
> > >> ** in these cases, the NAP and ISP info overwrites whatever the EAP client
> > >> identifier may suggest. One *-info is included at a time when separate
> > >> authentication will take place.
> > > 
> > > OK.
> > > 
> > >> 
> > >> - If both NAP-info and ISP-info are included, that means only one
> > >> authentication will take place. The *-info indicates the chosen service
> > >> combination. The authentication request is forwarded to ISP's AAA.
> > > 
> > > It seems natural for this case that separate authentication will take
> > > place with using particular NAP's AAA and ISP's AAA.
> > > 
> > >> 
> > >> - If no *-info is included, that means the implicit selection depends on the
> > >> EAP client identifier.
> > > 
> > > It seems natural for this case that only one authentication will
> > > take place with the authentication request being forwarded to ISP's
> > > AAA.
> > > 
> > >> 
> > >> We might also modify the f-flag logic. Maybe we can fold that logic to
> > >> PANA-start-request/answer exchange. PANA-start-request can signal the
> > >> capability to provide separate auth along with the list of ISPs/NAP.
> > >> PANA-start-answer can signal whether the PaC will do separate auths or not.
> > >> A flag in the message header can deliver this capability/choice.
> > > 
> > > Or can we use *-info contained in PANA-start-{request,answer} for that
> > > purpose instead of definig a new flag?
> > > 
> > > Yoshihiro Ohba
> > > 
> > > 
> > >> 
> > >> Comments?
> > >> 
> > >> Alper
> > >> 
> > >> 
> > >> 
> > >>> Here is the new text which reflects Alper's comments.
> > >>> 
> > >>> Yoshihiro Ohba
> > >>> 
> > >>> ---
> > >>> In Section 4.2, change
> > >>> 
> > >>> From:
> > >>> 
> > >>> "  When a PaC receives the PANA-Start-Request message in response to
> > >>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> > >>>  message. The PANA-Start-Answer message contains the initial sequence
> > >>>  numbers in the tseq and rseq fields of the PANA header, a copy of
> > >>>  the received Cookie as the PANA payload."
> > >>> 
> > >>> To:
> > >>> 
> > >>> "  A PANA-Start-Request can also contain zero or one NAP-Information
> > >>>  AVP and zero or more ISP-Information AVPs to advertise the
> > >>>  information on the NAP and/or ISPs.
> > >>> 
> > >>>  When a PaC receives the PANA-Start-Request message in response to
> > >>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> > >>>  message if it wishes to enter the authentication phase.  The
> > >>>  PANA-Start-Answer message contains the initial sequence numbers in
> > >>>  the tseq and rseq fields of the PANA header, a copy of the received
> > >>>  Cookie (if any) as the PANA payload.  If the received
> > >>>  PANA-Start-Request message contains a NAP-Information AVP and zero
> > >>>  or more ISP-Information AVP, the PaC MAY additinally contain the
> > >>>  received NAP-Information AVP and, if any, one of the received
> > >>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
> > >>>  the binding between the subsequent authentication and the NAP/ISP.
> > >>>  If the PaC does not contain a NAP-Information AVP or an
> > >>>  ISP-Information AVP, the EAP peer identity or some default
> > >>>  information MAY be used to identify the binding."
> > >>> 
> > >>> 
> > >>> In Section 9.3.3, change
> > >>> 
> > >>> from:
> > >>> 
> > >>> "
> > >>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> > >>>                   [ Cookie ]
> > >>>                 * [ AVP ]
> > >>> "
> > >>> 
> > >>> to:
> > >>> 
> > >>> "
> > >>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> > >>>                   [ Cookie ]
> > >>>    [ NAP-Information ]
> > >>>                 * [ ISP-Information ]
> > >>>                 * [ AVP ]
> > >>> "
> > >>> 
> > >>> 
> > >>> In Section 9.3.4, change
> > >>> 
> > >>> from:
> > >>> 
> > >>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> > >>>                   [ Cookie ]
> > >>>                 * [ AVP ]"
> > >>> 
> > >>> to:
> > >>> 
> > >>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> > >>>                   [ Cookie ]
> > >>>    [ NAP-Information ]
> > >>>                   [ ISP-Information ]
> > >>>                 * [ AVP ]"
> > >>> 
> > >>> 
> > >>> Add the following sections:
> > >>> 
> > >>> "9.4.9 NAP-Information AVP
> > >>> 
> > >>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
> > >>> contains one globally unique identifier of the NAP in a
> > >>> Provider-Identifier AVP and one enterprise name of the NAP in a
> > >>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> > >>> 
> > >>>     NAP-Information ::= < AVP Header: 1029 >
> > >>>                          { Provider-Identifier }
> > >>>                          { Provider-Name }
> > >>>                        * [ AVP ]
> > >>> 
> > >>> 
> > >>> 9.4.10 ISP-Information AVP
> > >>> 
> > >>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
> > >>> contains one globally unique identifier of the ISP in a
> > >>> Provider-Identifier AVP and one enterprise name of the ISP in a
> > >>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> > >>> 
> > >>>     ISP-Information ::= < AVP Header: 1030 >
> > >>>                          { Provider-Identifier }
> > >>>                          { Provider-Name }
> > >>>                        * [ AVP ]
> > >>> 
> > >>> 
> > >>> 9.4.11 Provider-Identifier AVP
> > >>> 
> > >>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
> > >>> and contains an IANA assigned "SMI Network Management Private
> > >>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
> > >>> 
> > >>> 
> > >>> 9.4.12 Provider-Name AVP
> > >>> 
> > >>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
> > >>> contains the UTF8-encoded name of the provider."
> > >>> 
> > >>> 
> > >>> 
> > >> 
> > > 
> > > 
> > 

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


From exim@www1.ietf.org  Fri Oct 17 11:09:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05666
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 11:09:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWDw-0001GU-CF
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 11:09:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HF944U004863
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 11:09:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWDw-0001GM-3f
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 11:09:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05644
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 11:08:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWDt-0004Ek-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 11:09:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWDt-0004Eh-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 11:09:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWDt-0001Fq-5B; Fri, 17 Oct 2003 11:09:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWDq-0001FX-B4
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 11:08:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05640
	for <pana@ietf.org>; Fri, 17 Oct 2003 11:08:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWDn-0004Ee-00
	for pana@ietf.org; Fri, 17 Oct 2003 11:08:55 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWDm-0004Eb-00
	for pana@ietf.org; Fri, 17 Oct 2003 11:08:55 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9HF8nF1023730;
	Sat, 18 Oct 2003 00:08:49 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9HF8nQb028498;
	Sat, 18 Oct 2003 00:08:49 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id AAA28497 ; Sat, 18 Oct 2003 00:08:49 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA13295; Sat, 18 Oct 2003 00:08:49 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA05820; Sat, 18 Oct 2003 00:08:48 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9HF8mib008794;
	Sat, 18 Oct 2003 00:08:48 +0900 (JST)
Received: from steelhead ([159.119.168.142]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMW00M4TQ2MQ4@tsbpo1.po.toshiba.co.jp>; Sat,
 18 Oct 2003 00:08:47 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAWCz-00052x-00; Fri, 17 Oct 2003 08:08:05 -0700
Date: Fri, 17 Oct 2003 08:08:05 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
In-reply-to: <20031017150221.GF14788@steelhead>
To: Alper Yegin <alper@docomolabs-usa.com>,
        Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Message-id: <20031017150805.GG14788@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031014213838.GA6092@steelhead>
 <BBB47CFF.A9FD%alper@docomolabs-usa.com> <20031017150221.GF14788@steelhead>
Subject: [Pana] Re: New [issue25] Service Profile names
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

I forward my reply to the new list.

Yoshihiro Ohba


On Fri, Oct 17, 2003 at 08:02:21AM -0700,  wrote:
> On Thu, Oct 16, 2003 at 04:51:11PM -0700, Alper Yegin wrote:
> > 
> > Here is another attempt...
> > 
> > Assuming:
> > - PAA may optionally include *-info in the PANA-start-request to "advertise"
> > the availability of service providers to the user.
> > - PaC may optionally include its choice of service providers in
> > PANA-start-answer, which effects the AAA routing. In the absence of *-info,
> > service selection and AAA routing is based on the client identifier used
> > within EAP conversation.
> > - PAA may optionally enable NAP-ISP authentication separation.
> > - PaC may optionally perform separate NAP and ISP authentication.
> 
> OK.
> 
> >  
> > 
> > How about this:
> > - PAA advertises auth separation capability by using S-flag in
> > PANA-start-request. PaC communicates its desire to separate them using the
> > same flag in the PANA-start-answer.
> 
> OK.
> 
> > 
> > - If S-flag is not set in the request, there will be only one round of
> >   authentication. PaC can indicate its choice of NAP and ISP by including
> >   their *-info in the  PANA-start-answer. AAA routing will be based on the
> >   ISP choice. 
> 
> OK.
> 
> > 
> > - If S-flag is set, there may be two rounds of authentication, depending on
> >   the PaC's preference.
> >   - If PaC wants to enable separate authentication, it should turn on the
> >     S-flag in PANA-start-answer. In that case, at most one *-info may be
> >     included at once, and it dictates the service provider selection.
> 
> What does the above sentense mean?
> 
> - Either one ISP-info or one NAP-info may be included.
> 
> - One NAP-info and/or one ISP-info may be included.
> 
> (I guess you mean the latter.)
> 
> In addition, I'm currently assuming that one PAA is associated with a
> single NAP. In this case, including NAP-info in the answer may be
> redundant.
> 
> >   - If PaC does not care about separate authentication, it unsets the S-flag
> >     in PANA-start-answer, and this is same as if PAA never set the S-flag.
> 
> OK.
> 
> Yoshihiro Ohba
> 
> > 
> > Does this make sense?
> > 
> > Alper
> > 
> > 
> > 
> >  
> > 
> > 
> >  
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > > On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
> > >> I was thinking something in terms of this:
> > >> 
> > >> - If only a NAP-info is included in the PANA-start-answer, that means the
> > >> following authentication should be directed to particular NAP's AAA.
> > >> - If only a ISP-info is included in the PANA-start-answer, that means the
> > >> following authentication should be directed to particular ISP's AAA.
> > >> ** in these cases, the NAP and ISP info overwrites whatever the EAP client
> > >> identifier may suggest. One *-info is included at a time when separate
> > >> authentication will take place.
> > > 
> > > OK.
> > > 
> > >> 
> > >> - If both NAP-info and ISP-info are included, that means only one
> > >> authentication will take place. The *-info indicates the chosen service
> > >> combination. The authentication request is forwarded to ISP's AAA.
> > > 
> > > It seems natural for this case that separate authentication will take
> > > place with using particular NAP's AAA and ISP's AAA.
> > > 
> > >> 
> > >> - If no *-info is included, that means the implicit selection depends on the
> > >> EAP client identifier.
> > > 
> > > It seems natural for this case that only one authentication will
> > > take place with the authentication request being forwarded to ISP's
> > > AAA.
> > > 
> > >> 
> > >> We might also modify the f-flag logic. Maybe we can fold that logic to
> > >> PANA-start-request/answer exchange. PANA-start-request can signal the
> > >> capability to provide separate auth along with the list of ISPs/NAP.
> > >> PANA-start-answer can signal whether the PaC will do separate auths or not.
> > >> A flag in the message header can deliver this capability/choice.
> > > 
> > > Or can we use *-info contained in PANA-start-{request,answer} for that
> > > purpose instead of definig a new flag?
> > > 
> > > Yoshihiro Ohba
> > > 
> > > 
> > >> 
> > >> Comments?
> > >> 
> > >> Alper
> > >> 
> > >> 
> > >> 
> > >>> Here is the new text which reflects Alper's comments.
> > >>> 
> > >>> Yoshihiro Ohba
> > >>> 
> > >>> ---
> > >>> In Section 4.2, change
> > >>> 
> > >>> From:
> > >>> 
> > >>> "  When a PaC receives the PANA-Start-Request message in response to
> > >>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> > >>>  message. The PANA-Start-Answer message contains the initial sequence
> > >>>  numbers in the tseq and rseq fields of the PANA header, a copy of
> > >>>  the received Cookie as the PANA payload."
> > >>> 
> > >>> To:
> > >>> 
> > >>> "  A PANA-Start-Request can also contain zero or one NAP-Information
> > >>>  AVP and zero or more ISP-Information AVPs to advertise the
> > >>>  information on the NAP and/or ISPs.
> > >>> 
> > >>>  When a PaC receives the PANA-Start-Request message in response to
> > >>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> > >>>  message if it wishes to enter the authentication phase.  The
> > >>>  PANA-Start-Answer message contains the initial sequence numbers in
> > >>>  the tseq and rseq fields of the PANA header, a copy of the received
> > >>>  Cookie (if any) as the PANA payload.  If the received
> > >>>  PANA-Start-Request message contains a NAP-Information AVP and zero
> > >>>  or more ISP-Information AVP, the PaC MAY additinally contain the
> > >>>  received NAP-Information AVP and, if any, one of the received
> > >>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
> > >>>  the binding between the subsequent authentication and the NAP/ISP.
> > >>>  If the PaC does not contain a NAP-Information AVP or an
> > >>>  ISP-Information AVP, the EAP peer identity or some default
> > >>>  information MAY be used to identify the binding."
> > >>> 
> > >>> 
> > >>> In Section 9.3.3, change
> > >>> 
> > >>> from:
> > >>> 
> > >>> "
> > >>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> > >>>                   [ Cookie ]
> > >>>                 * [ AVP ]
> > >>> "
> > >>> 
> > >>> to:
> > >>> 
> > >>> "
> > >>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> > >>>                   [ Cookie ]
> > >>>    [ NAP-Information ]
> > >>>                 * [ ISP-Information ]
> > >>>                 * [ AVP ]
> > >>> "
> > >>> 
> > >>> 
> > >>> In Section 9.3.4, change
> > >>> 
> > >>> from:
> > >>> 
> > >>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> > >>>                   [ Cookie ]
> > >>>                 * [ AVP ]"
> > >>> 
> > >>> to:
> > >>> 
> > >>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> > >>>                   [ Cookie ]
> > >>>    [ NAP-Information ]
> > >>>                   [ ISP-Information ]
> > >>>                 * [ AVP ]"
> > >>> 
> > >>> 
> > >>> Add the following sections:
> > >>> 
> > >>> "9.4.9 NAP-Information AVP
> > >>> 
> > >>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
> > >>> contains one globally unique identifier of the NAP in a
> > >>> Provider-Identifier AVP and one enterprise name of the NAP in a
> > >>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> > >>> 
> > >>>     NAP-Information ::= < AVP Header: 1029 >
> > >>>                          { Provider-Identifier }
> > >>>                          { Provider-Name }
> > >>>                        * [ AVP ]
> > >>> 
> > >>> 
> > >>> 9.4.10 ISP-Information AVP
> > >>> 
> > >>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
> > >>> contains one globally unique identifier of the ISP in a
> > >>> Provider-Identifier AVP and one enterprise name of the ISP in a
> > >>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> > >>> 
> > >>>     ISP-Information ::= < AVP Header: 1030 >
> > >>>                          { Provider-Identifier }
> > >>>                          { Provider-Name }
> > >>>                        * [ AVP ]
> > >>> 
> > >>> 
> > >>> 9.4.11 Provider-Identifier AVP
> > >>> 
> > >>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
> > >>> and contains an IANA assigned "SMI Network Management Private
> > >>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
> > >>> 
> > >>> 
> > >>> 9.4.12 Provider-Name AVP
> > >>> 
> > >>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
> > >>> contains the UTF8-encoded name of the provider."
> > >>> 
> > >>> 
> > >>> 
> > >> 
> > > 
> > > 
> > 

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



From pana-admin@ietf.org  Fri Oct 17 11:34:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06870
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 11:34:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWc5-0002Cc-1H; Fri, 17 Oct 2003 11:34:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWbr-0002Bw-BT
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 11:33:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06754
	for <pana@ietf.org>; Fri, 17 Oct 2003 11:33:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWbq-0004aF-00
	for pana@ietf.org; Fri, 17 Oct 2003 11:33:46 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWbp-0004a7-00
	for pana@ietf.org; Fri, 17 Oct 2003 11:33:45 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9HFXiF1000019;
	Sat, 18 Oct 2003 00:33:44 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9HFXip0007904;
	Sat, 18 Oct 2003 00:33:44 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id AAA07903 ; Sat, 18 Oct 2003 00:33:44 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA19913; Sat, 18 Oct 2003 00:33:43 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA06938; Sat, 18 Oct 2003 00:33:42 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9HFXfib013211;
	Sat, 18 Oct 2003 00:33:41 +0900 (JST)
Received: from steelhead ([159.119.168.142]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMW00J1FR830T@tsbpo1.po.toshiba.co.jp>; Sat,
 18 Oct 2003 00:33:40 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAWbA-00055K-00; Fri, 17 Oct 2003 08:33:04 -0700
Date: Fri, 17 Oct 2003 08:33:04 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] about issue31
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D85@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20031017153304.GH14788@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D85@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 17, 2003 at 03:02:02PM +0300, Dan.Forsberg@nokia.com wrote:
> Hi,
> 
> How are the sequence numbers handled in this case? Does PANA-PAA-Discover 
> message contain 0,0 or x,y?

I think it should be 0,0.  This is because PANA-PAA-Discovery is
always unprotected and PAA should avoid updating its rseq based on 
unprocted information as much as possible.

Yoshihiro Ohba


> 
> Current issue31 suggestion:
> 
>    "When a PaC wants to initiate EAP-based re-authentication, it sends
>    a unicast PANA-PAA-Discovery message to the PAA.  This message MUST
>    contain a Session-Id AVP which is used for identifying the PANA
>    session on the PAA. If the PAA already has an established PANA
>    session for the PaC with the matching identifier, it sends a
>    PANA-Auth-Request message containing the same identifier to start
>    an authentication phase.  If the PAA can not recognize the session
>    identifier, it proceeds with regular authentication by sending back
>    PANA-Start-Request.  When the PAA initiates EAP-based
>    re-authentication, it sends a PANA-Auth-Request message containing
>    the session identifier for the PaC to enter an authentication
>    phase. PAA SHOULD initiate EAP authentication before the current
>    session lifetime expires."
> 
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Fri Oct 17 11:34:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06900
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 11:34:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWc6-0002De-IJ
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 11:34:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HFY2Na008526
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 11:34:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWc6-0002DR-Co
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 11:34:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06795
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 11:33:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWc5-0004bU-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 11:34:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWc4-0004bQ-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 11:34:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWc5-0002Cc-1H; Fri, 17 Oct 2003 11:34:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAWbr-0002Bw-BT
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 11:33:47 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06754
	for <pana@ietf.org>; Fri, 17 Oct 2003 11:33:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWbq-0004aF-00
	for pana@ietf.org; Fri, 17 Oct 2003 11:33:46 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAWbp-0004a7-00
	for pana@ietf.org; Fri, 17 Oct 2003 11:33:45 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9HFXiF1000019;
	Sat, 18 Oct 2003 00:33:44 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9HFXip0007904;
	Sat, 18 Oct 2003 00:33:44 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id AAA07903 ; Sat, 18 Oct 2003 00:33:44 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA19913; Sat, 18 Oct 2003 00:33:43 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA06938; Sat, 18 Oct 2003 00:33:42 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9HFXfib013211;
	Sat, 18 Oct 2003 00:33:41 +0900 (JST)
Received: from steelhead ([159.119.168.142]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMW00J1FR830T@tsbpo1.po.toshiba.co.jp>; Sat,
 18 Oct 2003 00:33:40 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAWbA-00055K-00; Fri, 17 Oct 2003 08:33:04 -0700
Date: Fri, 17 Oct 2003 08:33:04 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] about issue31
In-reply-to: <FC5FF66A769AB044AED651C705EAA8EA015F6D85@esebe008.ntc.nokia.com>
To: Dan.Forsberg@nokia.com
Cc: pana@ietf.org
Message-id: <20031017153304.GH14788@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <FC5FF66A769AB044AED651C705EAA8EA015F6D85@esebe008.ntc.nokia.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 17, 2003 at 03:02:02PM +0300, Dan.Forsberg@nokia.com wrote:
> Hi,
> 
> How are the sequence numbers handled in this case? Does PANA-PAA-Discover 
> message contain 0,0 or x,y?

I think it should be 0,0.  This is because PANA-PAA-Discovery is
always unprotected and PAA should avoid updating its rseq based on 
unprocted information as much as possible.

Yoshihiro Ohba


> 
> Current issue31 suggestion:
> 
>    "When a PaC wants to initiate EAP-based re-authentication, it sends
>    a unicast PANA-PAA-Discovery message to the PAA.  This message MUST
>    contain a Session-Id AVP which is used for identifying the PANA
>    session on the PAA. If the PAA already has an established PANA
>    session for the PaC with the matching identifier, it sends a
>    PANA-Auth-Request message containing the same identifier to start
>    an authentication phase.  If the PAA can not recognize the session
>    identifier, it proceeds with regular authentication by sending back
>    PANA-Start-Request.  When the PAA initiates EAP-based
>    re-authentication, it sends a PANA-Auth-Request message containing
>    the session identifier for the PaC to enter an authentication
>    phase. PAA SHOULD initiate EAP authentication before the current
>    session lifetime expires."
> 
> 
> _______________________________________________
> 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-admin@ietf.org  Fri Oct 17 13:29:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11567
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 13:29:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAYPO-0008RY-08; Fri, 17 Oct 2003 13:29:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAYOw-0008R2-NJ
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 13:28:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11548
	for <pana@ietf.org>; Fri, 17 Oct 2003 13:28:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYOu-0005yu-00
	for pana@ietf.org; Fri, 17 Oct 2003 13:28:32 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYOt-0005yq-00
	for pana@ietf.org; Fri, 17 Oct 2003 13:28:31 -0400
Date: Fri, 17 Oct 2003 10:28:25 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <Dan.Forsberg@nokia.com>,
        <pana@ietf.org>
Message-ID: <BBB574C9.AA9C%alper@docomolabs-usa.com>
In-Reply-To: <20031017150805.GG14788@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Re: New [issue25] Service Profile names
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

>>> - If S-flag is set, there may be two rounds of authentication, depending on
>>>   the PaC's preference.
>>>   - If PaC wants to enable separate authentication, it should turn on the
>>>     S-flag in PANA-start-answer. In that case, at most one *-info may be
>>>     included at once, and it dictates the service provider selection.
>> 
>> What does the above sentense mean?
>> 
>> - Either one ISP-info or one NAP-info may be included.
>> 
>> - One NAP-info and/or one ISP-info may be included.
>> 
>> (I guess you mean the latter.)


I mean, there can be at most one info AVP (this AVP may be either ISP-info,
or AVP-info). Since there is a separate authentication round going on, each
round should be associated with a single service provider.

>> 
>> In addition, I'm currently assuming that one PAA is associated with a
>> single NAP. In this case, including NAP-info in the answer may be
>> redundant.

Including a NAP-info in the answer (when separate authentication is going
on) means that the supplied authentication info should be used with the NAP.
(NAP's AAA).

>> 
>>>   - If PaC does not care about separate authentication, it unsets the S-flag
>>>     in PANA-start-answer, and this is same as if PAA never set the S-flag.
>> 
>> OK.


Alper


>> 
>> Yoshihiro Ohba
>> 
>>> 
>>> Does this make sense?
>>> 
>>> Alper
>>> 
>>> 
>>> 
>>>  
>>> 
>>> 
>>>  
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
>>>>> I was thinking something in terms of this:
>>>>> 
>>>>> - If only a NAP-info is included in the PANA-start-answer, that means the
>>>>> following authentication should be directed to particular NAP's AAA.
>>>>> - If only a ISP-info is included in the PANA-start-answer, that means the
>>>>> following authentication should be directed to particular ISP's AAA.
>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP client
>>>>> identifier may suggest. One *-info is included at a time when separate
>>>>> authentication will take place.
>>>> 
>>>> OK.
>>>> 
>>>>> 
>>>>> - If both NAP-info and ISP-info are included, that means only one
>>>>> authentication will take place. The *-info indicates the chosen service
>>>>> combination. The authentication request is forwarded to ISP's AAA.
>>>> 
>>>> It seems natural for this case that separate authentication will take
>>>> place with using particular NAP's AAA and ISP's AAA.
>>>> 
>>>>> 
>>>>> - If no *-info is included, that means the implicit selection depends on
>>>>> the
>>>>> EAP client identifier.
>>>> 
>>>> It seems natural for this case that only one authentication will
>>>> take place with the authentication request being forwarded to ISP's
>>>> AAA.
>>>> 
>>>>> 
>>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
>>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
>>>>> capability to provide separate auth along with the list of ISPs/NAP.
>>>>> PANA-start-answer can signal whether the PaC will do separate auths or
>>>>> not.
>>>>> A flag in the message header can deliver this capability/choice.
>>>> 
>>>> Or can we use *-info contained in PANA-start-{request,answer} for that
>>>> purpose instead of definig a new flag?
>>>> 
>>>> Yoshihiro Ohba
>>>> 
>>>> 
>>>>> 
>>>>> Comments?
>>>>> 
>>>>> Alper
>>>>> 
>>>>> 
>>>>> 
>>>>>> Here is the new text which reflects Alper's comments.
>>>>>> 
>>>>>> Yoshihiro Ohba
>>>>>> 
>>>>>> ---
>>>>>> In Section 4.2, change
>>>>>> 
>>>>>> From:
>>>>>> 
>>>>>> "  When a PaC receives the PANA-Start-Request message in response to
>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>  message. The PANA-Start-Answer message contains the initial sequence
>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
>>>>>>  the received Cookie as the PANA payload."
>>>>>> 
>>>>>> To:
>>>>>> 
>>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
>>>>>>  information on the NAP and/or ISPs.
>>>>>> 
>>>>>>  When a PaC receives the PANA-Start-Request message in response to
>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>  message if it wishes to enter the authentication phase.  The
>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
>>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
>>>>>>  Cookie (if any) as the PANA payload.  If the received
>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
>>>>>>  received NAP-Information AVP and, if any, one of the received
>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
>>>>>>  If the PaC does not contain a NAP-Information AVP or an
>>>>>>  ISP-Information AVP, the EAP peer identity or some default
>>>>>>  information MAY be used to identify the binding."
>>>>>> 
>>>>>> 
>>>>>> In Section 9.3.3, change
>>>>>> 
>>>>>> from:
>>>>>> 
>>>>>> "
>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>                   [ Cookie ]
>>>>>>                 * [ AVP ]
>>>>>> "
>>>>>> 
>>>>>> to:
>>>>>> 
>>>>>> "
>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>                   [ Cookie ]
>>>>>>    [ NAP-Information ]
>>>>>>                 * [ ISP-Information ]
>>>>>>                 * [ AVP ]
>>>>>> "
>>>>>> 
>>>>>> 
>>>>>> In Section 9.3.4, change
>>>>>> 
>>>>>> from:
>>>>>> 
>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>                   [ Cookie ]
>>>>>>                 * [ AVP ]"
>>>>>> 
>>>>>> to:
>>>>>> 
>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>                   [ Cookie ]
>>>>>>    [ NAP-Information ]
>>>>>>                   [ ISP-Information ]
>>>>>>                 * [ AVP ]"
>>>>>> 
>>>>>> 
>>>>>> Add the following sections:
>>>>>> 
>>>>>> "9.4.9 NAP-Information AVP
>>>>>> 
>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
>>>>>> contains one globally unique identifier of the NAP in a
>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>> 
>>>>>>     NAP-Information ::= < AVP Header: 1029 >
>>>>>>                          { Provider-Identifier }
>>>>>>                          { Provider-Name }
>>>>>>                        * [ AVP ]
>>>>>> 
>>>>>> 
>>>>>> 9.4.10 ISP-Information AVP
>>>>>> 
>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
>>>>>> contains one globally unique identifier of the ISP in a
>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>> 
>>>>>>     ISP-Information ::= < AVP Header: 1030 >
>>>>>>                          { Provider-Identifier }
>>>>>>                          { Provider-Name }
>>>>>>                        * [ AVP ]
>>>>>> 
>>>>>> 
>>>>>> 9.4.11 Provider-Identifier AVP
>>>>>> 
>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
>>>>>> and contains an IANA assigned "SMI Network Management Private
>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
>>>>>> 
>>>>>> 
>>>>>> 9.4.12 Provider-Name AVP
>>>>>> 
>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
>>>>>> contains the UTF8-encoded name of the provider."
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
> 


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


From exim@www1.ietf.org  Fri Oct 17 13:30:47 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11660
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 13:30:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAYQj-0000Dr-Rt
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 13:30:26 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HHUPei000847
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 13:30:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAYQj-0000DV-Cu
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 13:30:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11617
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 13:30:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYPi-0005zi-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 13:29:22 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYPX-0005zZ-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 13:29:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAYPO-0008RY-08; Fri, 17 Oct 2003 13:29:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAYOw-0008R2-NJ
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 13:28:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11548
	for <pana@ietf.org>; Fri, 17 Oct 2003 13:28:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYOu-0005yu-00
	for pana@ietf.org; Fri, 17 Oct 2003 13:28:32 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYOt-0005yq-00
	for pana@ietf.org; Fri, 17 Oct 2003 13:28:31 -0400
Date: Fri, 17 Oct 2003 10:28:25 -0700
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <Dan.Forsberg@nokia.com>,
        <pana@ietf.org>
Message-ID: <BBB574C9.AA9C%alper@docomolabs-usa.com>
In-Reply-To: <20031017150805.GG14788@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Re: New [issue25] Service Profile names
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>>> - If S-flag is set, there may be two rounds of authentication, depending on
>>>   the PaC's preference.
>>>   - If PaC wants to enable separate authentication, it should turn on the
>>>     S-flag in PANA-start-answer. In that case, at most one *-info may be
>>>     included at once, and it dictates the service provider selection.
>> 
>> What does the above sentense mean?
>> 
>> - Either one ISP-info or one NAP-info may be included.
>> 
>> - One NAP-info and/or one ISP-info may be included.
>> 
>> (I guess you mean the latter.)


I mean, there can be at most one info AVP (this AVP may be either ISP-info,
or AVP-info). Since there is a separate authentication round going on, each
round should be associated with a single service provider.

>> 
>> In addition, I'm currently assuming that one PAA is associated with a
>> single NAP. In this case, including NAP-info in the answer may be
>> redundant.

Including a NAP-info in the answer (when separate authentication is going
on) means that the supplied authentication info should be used with the NAP.
(NAP's AAA).

>> 
>>>   - If PaC does not care about separate authentication, it unsets the S-flag
>>>     in PANA-start-answer, and this is same as if PAA never set the S-flag.
>> 
>> OK.


Alper


>> 
>> Yoshihiro Ohba
>> 
>>> 
>>> Does this make sense?
>>> 
>>> Alper
>>> 
>>> 
>>> 
>>>  
>>> 
>>> 
>>>  
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
>>>>> I was thinking something in terms of this:
>>>>> 
>>>>> - If only a NAP-info is included in the PANA-start-answer, that means the
>>>>> following authentication should be directed to particular NAP's AAA.
>>>>> - If only a ISP-info is included in the PANA-start-answer, that means the
>>>>> following authentication should be directed to particular ISP's AAA.
>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP client
>>>>> identifier may suggest. One *-info is included at a time when separate
>>>>> authentication will take place.
>>>> 
>>>> OK.
>>>> 
>>>>> 
>>>>> - If both NAP-info and ISP-info are included, that means only one
>>>>> authentication will take place. The *-info indicates the chosen service
>>>>> combination. The authentication request is forwarded to ISP's AAA.
>>>> 
>>>> It seems natural for this case that separate authentication will take
>>>> place with using particular NAP's AAA and ISP's AAA.
>>>> 
>>>>> 
>>>>> - If no *-info is included, that means the implicit selection depends on
>>>>> the
>>>>> EAP client identifier.
>>>> 
>>>> It seems natural for this case that only one authentication will
>>>> take place with the authentication request being forwarded to ISP's
>>>> AAA.
>>>> 
>>>>> 
>>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
>>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
>>>>> capability to provide separate auth along with the list of ISPs/NAP.
>>>>> PANA-start-answer can signal whether the PaC will do separate auths or
>>>>> not.
>>>>> A flag in the message header can deliver this capability/choice.
>>>> 
>>>> Or can we use *-info contained in PANA-start-{request,answer} for that
>>>> purpose instead of definig a new flag?
>>>> 
>>>> Yoshihiro Ohba
>>>> 
>>>> 
>>>>> 
>>>>> Comments?
>>>>> 
>>>>> Alper
>>>>> 
>>>>> 
>>>>> 
>>>>>> Here is the new text which reflects Alper's comments.
>>>>>> 
>>>>>> Yoshihiro Ohba
>>>>>> 
>>>>>> ---
>>>>>> In Section 4.2, change
>>>>>> 
>>>>>> From:
>>>>>> 
>>>>>> "  When a PaC receives the PANA-Start-Request message in response to
>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>  message. The PANA-Start-Answer message contains the initial sequence
>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
>>>>>>  the received Cookie as the PANA payload."
>>>>>> 
>>>>>> To:
>>>>>> 
>>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
>>>>>>  information on the NAP and/or ISPs.
>>>>>> 
>>>>>>  When a PaC receives the PANA-Start-Request message in response to
>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>  message if it wishes to enter the authentication phase.  The
>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
>>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
>>>>>>  Cookie (if any) as the PANA payload.  If the received
>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
>>>>>>  received NAP-Information AVP and, if any, one of the received
>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
>>>>>>  If the PaC does not contain a NAP-Information AVP or an
>>>>>>  ISP-Information AVP, the EAP peer identity or some default
>>>>>>  information MAY be used to identify the binding."
>>>>>> 
>>>>>> 
>>>>>> In Section 9.3.3, change
>>>>>> 
>>>>>> from:
>>>>>> 
>>>>>> "
>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>                   [ Cookie ]
>>>>>>                 * [ AVP ]
>>>>>> "
>>>>>> 
>>>>>> to:
>>>>>> 
>>>>>> "
>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>                   [ Cookie ]
>>>>>>    [ NAP-Information ]
>>>>>>                 * [ ISP-Information ]
>>>>>>                 * [ AVP ]
>>>>>> "
>>>>>> 
>>>>>> 
>>>>>> In Section 9.3.4, change
>>>>>> 
>>>>>> from:
>>>>>> 
>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>                   [ Cookie ]
>>>>>>                 * [ AVP ]"
>>>>>> 
>>>>>> to:
>>>>>> 
>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>                   [ Cookie ]
>>>>>>    [ NAP-Information ]
>>>>>>                   [ ISP-Information ]
>>>>>>                 * [ AVP ]"
>>>>>> 
>>>>>> 
>>>>>> Add the following sections:
>>>>>> 
>>>>>> "9.4.9 NAP-Information AVP
>>>>>> 
>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
>>>>>> contains one globally unique identifier of the NAP in a
>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>> 
>>>>>>     NAP-Information ::= < AVP Header: 1029 >
>>>>>>                          { Provider-Identifier }
>>>>>>                          { Provider-Name }
>>>>>>                        * [ AVP ]
>>>>>> 
>>>>>> 
>>>>>> 9.4.10 ISP-Information AVP
>>>>>> 
>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
>>>>>> contains one globally unique identifier of the ISP in a
>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>> 
>>>>>>     ISP-Information ::= < AVP Header: 1030 >
>>>>>>                          { Provider-Identifier }
>>>>>>                          { Provider-Name }
>>>>>>                        * [ AVP ]
>>>>>> 
>>>>>> 
>>>>>> 9.4.11 Provider-Identifier AVP
>>>>>> 
>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
>>>>>> and contains an IANA assigned "SMI Network Management Private
>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
>>>>>> 
>>>>>> 
>>>>>> 9.4.12 Provider-Name AVP
>>>>>> 
>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
>>>>>> contains the UTF8-encoded name of the provider."
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
> 


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



From pana-admin@ietf.org  Fri Oct 17 14:07:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13899
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 14:07:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAZ08-0002Nu-OU; Fri, 17 Oct 2003 14:07:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAYzt-0002NS-5d
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 14:06:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13861
	for <pana@ietf.org>; Fri, 17 Oct 2003 14:06:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYzq-0006dT-00
	for pana@ietf.org; Fri, 17 Oct 2003 14:06:42 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYzp-0006dQ-00
	for pana@ietf.org; Fri, 17 Oct 2003 14:06:42 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9HI6aF1002297;
	Sat, 18 Oct 2003 03:06:36 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9HI6akh022577;
	Sat, 18 Oct 2003 03:06:36 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA22576 ; Sat, 18 Oct 2003 03:06:36 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA02725; Sat, 18 Oct 2003 03:06:36 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA08455; Sat, 18 Oct 2003 03:06:35 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9HI6Zib016458;
	Sat, 18 Oct 2003 03:06:35 +0900 (JST)
Received: from steelhead ([159.119.168.86]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMW0008QYAXGH@tsbpo1.po.toshiba.co.jp>; Sat,
 18 Oct 2003 03:06:34 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAYxg-0000Jo-00; Fri, 17 Oct 2003 11:04:28 -0700
Date: Fri, 17 Oct 2003 11:04:28 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
In-reply-to: <BBB574C9.AA9C%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Message-id: <20031017180428.GA699@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031017150805.GG14788@steelhead>
 <BBB574C9.AA9C%alper@docomolabs-usa.com>
Subject: [Pana] Re: New [issue25] Service Profile names
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 17, 2003 at 10:28:25AM -0700, Alper Yegin wrote:
> >>> - If S-flag is set, there may be two rounds of authentication, depending on
> >>>   the PaC's preference.
> >>>   - If PaC wants to enable separate authentication, it should turn on the
> >>>     S-flag in PANA-start-answer. In that case, at most one *-info may be
> >>>     included at once, and it dictates the service provider selection.
> >> 
> >> What does the above sentense mean?
> >> 
> >> - Either one ISP-info or one NAP-info may be included.
> >> 
> >> - One NAP-info and/or one ISP-info may be included.
> >> 
> >> (I guess you mean the latter.)
> 
> 
> I mean, there can be at most one info AVP (this AVP may be either ISP-info,
> or AVP-info). Since there is a separate authentication round going on, each
> round should be associated with a single service provider.

I think each authentication round can be associated with a different
AAA, i.e., NAP authentication can use NAP's AAA and ISP authentication
can use ISP's AAA (possibly with using a different identity in each
authentication round).  Do you mean such a scenario should not be
supported?

Yoshihiro Ohba



> 
> >> 
> >> In addition, I'm currently assuming that one PAA is associated with a
> >> single NAP. In this case, including NAP-info in the answer may be
> >> redundant.
> 
> Including a NAP-info in the answer (when separate authentication is going
> on) means that the supplied authentication info should be used with the NAP.
> (NAP's AAA).
> 
> >> 
> >>>   - If PaC does not care about separate authentication, it unsets the S-flag
> >>>     in PANA-start-answer, and this is same as if PAA never set the S-flag.
> >> 
> >> OK.
> 
> 
> Alper
> 
> 
> >> 
> >> Yoshihiro Ohba
> >> 
> >>> 
> >>> Does this make sense?
> >>> 
> >>> Alper
> >>> 
> >>> 
> >>> 
> >>>  
> >>> 
> >>> 
> >>>  
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
> >>>>> I was thinking something in terms of this:
> >>>>> 
> >>>>> - If only a NAP-info is included in the PANA-start-answer, that means the
> >>>>> following authentication should be directed to particular NAP's AAA.
> >>>>> - If only a ISP-info is included in the PANA-start-answer, that means the
> >>>>> following authentication should be directed to particular ISP's AAA.
> >>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP client
> >>>>> identifier may suggest. One *-info is included at a time when separate
> >>>>> authentication will take place.
> >>>> 
> >>>> OK.
> >>>> 
> >>>>> 
> >>>>> - If both NAP-info and ISP-info are included, that means only one
> >>>>> authentication will take place. The *-info indicates the chosen service
> >>>>> combination. The authentication request is forwarded to ISP's AAA.
> >>>> 
> >>>> It seems natural for this case that separate authentication will take
> >>>> place with using particular NAP's AAA and ISP's AAA.
> >>>> 
> >>>>> 
> >>>>> - If no *-info is included, that means the implicit selection depends on
> >>>>> the
> >>>>> EAP client identifier.
> >>>> 
> >>>> It seems natural for this case that only one authentication will
> >>>> take place with the authentication request being forwarded to ISP's
> >>>> AAA.
> >>>> 
> >>>>> 
> >>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
> >>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
> >>>>> capability to provide separate auth along with the list of ISPs/NAP.
> >>>>> PANA-start-answer can signal whether the PaC will do separate auths or
> >>>>> not.
> >>>>> A flag in the message header can deliver this capability/choice.
> >>>> 
> >>>> Or can we use *-info contained in PANA-start-{request,answer} for that
> >>>> purpose instead of definig a new flag?
> >>>> 
> >>>> Yoshihiro Ohba
> >>>> 
> >>>> 
> >>>>> 
> >>>>> Comments?
> >>>>> 
> >>>>> Alper
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>>> Here is the new text which reflects Alper's comments.
> >>>>>> 
> >>>>>> Yoshihiro Ohba
> >>>>>> 
> >>>>>> ---
> >>>>>> In Section 4.2, change
> >>>>>> 
> >>>>>> From:
> >>>>>> 
> >>>>>> "  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>  message. The PANA-Start-Answer message contains the initial sequence
> >>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
> >>>>>>  the received Cookie as the PANA payload."
> >>>>>> 
> >>>>>> To:
> >>>>>> 
> >>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
> >>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
> >>>>>>  information on the NAP and/or ISPs.
> >>>>>> 
> >>>>>>  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>  message if it wishes to enter the authentication phase.  The
> >>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
> >>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
> >>>>>>  Cookie (if any) as the PANA payload.  If the received
> >>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
> >>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
> >>>>>>  received NAP-Information AVP and, if any, one of the received
> >>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
> >>>>>>  the binding between the subsequent authentication and the NAP/ISP.
> >>>>>>  If the PaC does not contain a NAP-Information AVP or an
> >>>>>>  ISP-Information AVP, the EAP peer identity or some default
> >>>>>>  information MAY be used to identify the binding."
> >>>>>> 
> >>>>>> 
> >>>>>> In Section 9.3.3, change
> >>>>>> 
> >>>>>> from:
> >>>>>> 
> >>>>>> "
> >>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>                   [ Cookie ]
> >>>>>>                 * [ AVP ]
> >>>>>> "
> >>>>>> 
> >>>>>> to:
> >>>>>> 
> >>>>>> "
> >>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>                   [ Cookie ]
> >>>>>>    [ NAP-Information ]
> >>>>>>                 * [ ISP-Information ]
> >>>>>>                 * [ AVP ]
> >>>>>> "
> >>>>>> 
> >>>>>> 
> >>>>>> In Section 9.3.4, change
> >>>>>> 
> >>>>>> from:
> >>>>>> 
> >>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>                   [ Cookie ]
> >>>>>>                 * [ AVP ]"
> >>>>>> 
> >>>>>> to:
> >>>>>> 
> >>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>                   [ Cookie ]
> >>>>>>    [ NAP-Information ]
> >>>>>>                   [ ISP-Information ]
> >>>>>>                 * [ AVP ]"
> >>>>>> 
> >>>>>> 
> >>>>>> Add the following sections:
> >>>>>> 
> >>>>>> "9.4.9 NAP-Information AVP
> >>>>>> 
> >>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
> >>>>>> contains one globally unique identifier of the NAP in a
> >>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
> >>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>> 
> >>>>>>     NAP-Information ::= < AVP Header: 1029 >
> >>>>>>                          { Provider-Identifier }
> >>>>>>                          { Provider-Name }
> >>>>>>                        * [ AVP ]
> >>>>>> 
> >>>>>> 
> >>>>>> 9.4.10 ISP-Information AVP
> >>>>>> 
> >>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
> >>>>>> contains one globally unique identifier of the ISP in a
> >>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
> >>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>> 
> >>>>>>     ISP-Information ::= < AVP Header: 1030 >
> >>>>>>                          { Provider-Identifier }
> >>>>>>                          { Provider-Name }
> >>>>>>                        * [ AVP ]
> >>>>>> 
> >>>>>> 
> >>>>>> 9.4.11 Provider-Identifier AVP
> >>>>>> 
> >>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
> >>>>>> and contains an IANA assigned "SMI Network Management Private
> >>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
> >>>>>> 
> >>>>>> 
> >>>>>> 9.4.12 Provider-Name AVP
> >>>>>> 
> >>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
> >>>>>> contains the UTF8-encoded name of the provider."
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>> 
> >>>> 
> >>>> 
> >>> 
> > 
> 

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


From exim@www1.ietf.org  Fri Oct 17 14:07:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13914
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 14:07:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAZ0B-0002PS-En
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 14:07:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HI733I009253
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 14:07:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAZ0A-0002P1-P0
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 14:07:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13885
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 14:06:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAZ08-0006dg-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 14:07:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAZ07-0006dc-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 14:06:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAZ08-0002Nu-OU; Fri, 17 Oct 2003 14:07:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAYzt-0002NS-5d
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 14:06:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13861
	for <pana@ietf.org>; Fri, 17 Oct 2003 14:06:35 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYzq-0006dT-00
	for pana@ietf.org; Fri, 17 Oct 2003 14:06:42 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAYzp-0006dQ-00
	for pana@ietf.org; Fri, 17 Oct 2003 14:06:42 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9HI6aF1002297;
	Sat, 18 Oct 2003 03:06:36 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9HI6akh022577;
	Sat, 18 Oct 2003 03:06:36 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA22576 ; Sat, 18 Oct 2003 03:06:36 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA02725; Sat, 18 Oct 2003 03:06:36 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA08455; Sat, 18 Oct 2003 03:06:35 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9HI6Zib016458;
	Sat, 18 Oct 2003 03:06:35 +0900 (JST)
Received: from steelhead ([159.119.168.86]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMW0008QYAXGH@tsbpo1.po.toshiba.co.jp>; Sat,
 18 Oct 2003 03:06:34 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAYxg-0000Jo-00; Fri, 17 Oct 2003 11:04:28 -0700
Date: Fri, 17 Oct 2003 11:04:28 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
In-reply-to: <BBB574C9.AA9C%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Message-id: <20031017180428.GA699@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031017150805.GG14788@steelhead>
 <BBB574C9.AA9C%alper@docomolabs-usa.com>
Subject: [Pana] Re: New [issue25] Service Profile names
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 17, 2003 at 10:28:25AM -0700, Alper Yegin wrote:
> >>> - If S-flag is set, there may be two rounds of authentication, depending on
> >>>   the PaC's preference.
> >>>   - If PaC wants to enable separate authentication, it should turn on the
> >>>     S-flag in PANA-start-answer. In that case, at most one *-info may be
> >>>     included at once, and it dictates the service provider selection.
> >> 
> >> What does the above sentense mean?
> >> 
> >> - Either one ISP-info or one NAP-info may be included.
> >> 
> >> - One NAP-info and/or one ISP-info may be included.
> >> 
> >> (I guess you mean the latter.)
> 
> 
> I mean, there can be at most one info AVP (this AVP may be either ISP-info,
> or AVP-info). Since there is a separate authentication round going on, each
> round should be associated with a single service provider.

I think each authentication round can be associated with a different
AAA, i.e., NAP authentication can use NAP's AAA and ISP authentication
can use ISP's AAA (possibly with using a different identity in each
authentication round).  Do you mean such a scenario should not be
supported?

Yoshihiro Ohba



> 
> >> 
> >> In addition, I'm currently assuming that one PAA is associated with a
> >> single NAP. In this case, including NAP-info in the answer may be
> >> redundant.
> 
> Including a NAP-info in the answer (when separate authentication is going
> on) means that the supplied authentication info should be used with the NAP.
> (NAP's AAA).
> 
> >> 
> >>>   - If PaC does not care about separate authentication, it unsets the S-flag
> >>>     in PANA-start-answer, and this is same as if PAA never set the S-flag.
> >> 
> >> OK.
> 
> 
> Alper
> 
> 
> >> 
> >> Yoshihiro Ohba
> >> 
> >>> 
> >>> Does this make sense?
> >>> 
> >>> Alper
> >>> 
> >>> 
> >>> 
> >>>  
> >>> 
> >>> 
> >>>  
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
> >>>>> I was thinking something in terms of this:
> >>>>> 
> >>>>> - If only a NAP-info is included in the PANA-start-answer, that means the
> >>>>> following authentication should be directed to particular NAP's AAA.
> >>>>> - If only a ISP-info is included in the PANA-start-answer, that means the
> >>>>> following authentication should be directed to particular ISP's AAA.
> >>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP client
> >>>>> identifier may suggest. One *-info is included at a time when separate
> >>>>> authentication will take place.
> >>>> 
> >>>> OK.
> >>>> 
> >>>>> 
> >>>>> - If both NAP-info and ISP-info are included, that means only one
> >>>>> authentication will take place. The *-info indicates the chosen service
> >>>>> combination. The authentication request is forwarded to ISP's AAA.
> >>>> 
> >>>> It seems natural for this case that separate authentication will take
> >>>> place with using particular NAP's AAA and ISP's AAA.
> >>>> 
> >>>>> 
> >>>>> - If no *-info is included, that means the implicit selection depends on
> >>>>> the
> >>>>> EAP client identifier.
> >>>> 
> >>>> It seems natural for this case that only one authentication will
> >>>> take place with the authentication request being forwarded to ISP's
> >>>> AAA.
> >>>> 
> >>>>> 
> >>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
> >>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
> >>>>> capability to provide separate auth along with the list of ISPs/NAP.
> >>>>> PANA-start-answer can signal whether the PaC will do separate auths or
> >>>>> not.
> >>>>> A flag in the message header can deliver this capability/choice.
> >>>> 
> >>>> Or can we use *-info contained in PANA-start-{request,answer} for that
> >>>> purpose instead of definig a new flag?
> >>>> 
> >>>> Yoshihiro Ohba
> >>>> 
> >>>> 
> >>>>> 
> >>>>> Comments?
> >>>>> 
> >>>>> Alper
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>>> Here is the new text which reflects Alper's comments.
> >>>>>> 
> >>>>>> Yoshihiro Ohba
> >>>>>> 
> >>>>>> ---
> >>>>>> In Section 4.2, change
> >>>>>> 
> >>>>>> From:
> >>>>>> 
> >>>>>> "  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>  message. The PANA-Start-Answer message contains the initial sequence
> >>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
> >>>>>>  the received Cookie as the PANA payload."
> >>>>>> 
> >>>>>> To:
> >>>>>> 
> >>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
> >>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
> >>>>>>  information on the NAP and/or ISPs.
> >>>>>> 
> >>>>>>  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>  message if it wishes to enter the authentication phase.  The
> >>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
> >>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
> >>>>>>  Cookie (if any) as the PANA payload.  If the received
> >>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
> >>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
> >>>>>>  received NAP-Information AVP and, if any, one of the received
> >>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
> >>>>>>  the binding between the subsequent authentication and the NAP/ISP.
> >>>>>>  If the PaC does not contain a NAP-Information AVP or an
> >>>>>>  ISP-Information AVP, the EAP peer identity or some default
> >>>>>>  information MAY be used to identify the binding."
> >>>>>> 
> >>>>>> 
> >>>>>> In Section 9.3.3, change
> >>>>>> 
> >>>>>> from:
> >>>>>> 
> >>>>>> "
> >>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>                   [ Cookie ]
> >>>>>>                 * [ AVP ]
> >>>>>> "
> >>>>>> 
> >>>>>> to:
> >>>>>> 
> >>>>>> "
> >>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>                   [ Cookie ]
> >>>>>>    [ NAP-Information ]
> >>>>>>                 * [ ISP-Information ]
> >>>>>>                 * [ AVP ]
> >>>>>> "
> >>>>>> 
> >>>>>> 
> >>>>>> In Section 9.3.4, change
> >>>>>> 
> >>>>>> from:
> >>>>>> 
> >>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>                   [ Cookie ]
> >>>>>>                 * [ AVP ]"
> >>>>>> 
> >>>>>> to:
> >>>>>> 
> >>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>                   [ Cookie ]
> >>>>>>    [ NAP-Information ]
> >>>>>>                   [ ISP-Information ]
> >>>>>>                 * [ AVP ]"
> >>>>>> 
> >>>>>> 
> >>>>>> Add the following sections:
> >>>>>> 
> >>>>>> "9.4.9 NAP-Information AVP
> >>>>>> 
> >>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
> >>>>>> contains one globally unique identifier of the NAP in a
> >>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
> >>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>> 
> >>>>>>     NAP-Information ::= < AVP Header: 1029 >
> >>>>>>                          { Provider-Identifier }
> >>>>>>                          { Provider-Name }
> >>>>>>                        * [ AVP ]
> >>>>>> 
> >>>>>> 
> >>>>>> 9.4.10 ISP-Information AVP
> >>>>>> 
> >>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
> >>>>>> contains one globally unique identifier of the ISP in a
> >>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
> >>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>> 
> >>>>>>     ISP-Information ::= < AVP Header: 1030 >
> >>>>>>                          { Provider-Identifier }
> >>>>>>                          { Provider-Name }
> >>>>>>                        * [ AVP ]
> >>>>>> 
> >>>>>> 
> >>>>>> 9.4.11 Provider-Identifier AVP
> >>>>>> 
> >>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
> >>>>>> and contains an IANA assigned "SMI Network Management Private
> >>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
> >>>>>> 
> >>>>>> 
> >>>>>> 9.4.12 Provider-Name AVP
> >>>>>> 
> >>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
> >>>>>> contains the UTF8-encoded name of the provider."
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>> 
> >>>> 
> >>>> 
> >>> 
> > 
> 

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



From pana-admin@ietf.org  Fri Oct 17 14:20:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14441
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 14:20:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAZCk-00033F-Br; Fri, 17 Oct 2003 14:20:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAZCX-00032K-8s
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 14:19:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14362
	for <pana@ietf.org>; Fri, 17 Oct 2003 14:19:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAZCU-0006nF-00
	for pana@ietf.org; Fri, 17 Oct 2003 14:19:46 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAZCU-0006nC-00
	for pana@ietf.org; Fri, 17 Oct 2003 14:19:46 -0400
Date: Fri, 17 Oct 2003 11:19:37 -0700
Subject: Re: [Pana] Re: New [issue25] Service Profile names
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBB580C9.AAC2%alper@docomolabs-usa.com>
In-Reply-To: <20031017180428.GA699@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> I think each authentication round can be associated with a different
> AAA, i.e., NAP authentication can use NAP's AAA and ISP authentication
> can use ISP's AAA (possibly with using a different identity in each
> authentication round).  Do you mean such a scenario should not be
> supported?

There is some misunderstanding. This is exactly what I'm trying to support
in the protocol design.

If PAA offers and PaC accepts to authenticte to NAP and ISP separately,
there will be two rounds of EAP authentication. Each round should be
associated with one service provider, whose identity is carried in a *-info
AVP. For example, in the first round, PaC can send NAP-info, in the second
round it can send ISP-info. My point was, NAP-info and ISP-info should not
be carried at the same time (round) in this case. (if you do, how will the
PAA know which AAA to contact? Would it be ISP's AAA, or NAP's AAA? Having a
single *-info makes it clear).

Alper




> 
> Yoshihiro Ohba
> 
> 
> 
>> 
>>>> 
>>>> In addition, I'm currently assuming that one PAA is associated with a
>>>> single NAP. In this case, including NAP-info in the answer may be
>>>> redundant.
>> 
>> Including a NAP-info in the answer (when separate authentication is going
>> on) means that the supplied authentication info should be used with the NAP.
>> (NAP's AAA).
>> 
>>>> 
>>>>>   - If PaC does not care about separate authentication, it unsets the
>>>>> S-flag
>>>>>     in PANA-start-answer, and this is same as if PAA never set the S-flag.
>>>> 
>>>> OK.
>> 
>> 
>> Alper
>> 
>> 
>>>> 
>>>> Yoshihiro Ohba
>>>> 
>>>>> 
>>>>> Does this make sense?
>>>>> 
>>>>> Alper
>>>>> 
>>>>> 
>>>>> 
>>>>>  
>>>>> 
>>>>> 
>>>>>  
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
>>>>>>> I was thinking something in terms of this:
>>>>>>> 
>>>>>>> - If only a NAP-info is included in the PANA-start-answer, that means
>>>>>>> the
>>>>>>> following authentication should be directed to particular NAP's AAA.
>>>>>>> - If only a ISP-info is included in the PANA-start-answer, that means
>>>>>>> the
>>>>>>> following authentication should be directed to particular ISP's AAA.
>>>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP
>>>>>>> client
>>>>>>> identifier may suggest. One *-info is included at a time when separate
>>>>>>> authentication will take place.
>>>>>> 
>>>>>> OK.
>>>>>> 
>>>>>>> 
>>>>>>> - If both NAP-info and ISP-info are included, that means only one
>>>>>>> authentication will take place. The *-info indicates the chosen service
>>>>>>> combination. The authentication request is forwarded to ISP's AAA.
>>>>>> 
>>>>>> It seems natural for this case that separate authentication will take
>>>>>> place with using particular NAP's AAA and ISP's AAA.
>>>>>> 
>>>>>>> 
>>>>>>> - If no *-info is included, that means the implicit selection depends on
>>>>>>> the
>>>>>>> EAP client identifier.
>>>>>> 
>>>>>> It seems natural for this case that only one authentication will
>>>>>> take place with the authentication request being forwarded to ISP's
>>>>>> AAA.
>>>>>> 
>>>>>>> 
>>>>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
>>>>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
>>>>>>> capability to provide separate auth along with the list of ISPs/NAP.
>>>>>>> PANA-start-answer can signal whether the PaC will do separate auths or
>>>>>>> not.
>>>>>>> A flag in the message header can deliver this capability/choice.
>>>>>> 
>>>>>> Or can we use *-info contained in PANA-start-{request,answer} for that
>>>>>> purpose instead of definig a new flag?
>>>>>> 
>>>>>> Yoshihiro Ohba
>>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>> Comments?
>>>>>>> 
>>>>>>> Alper
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> Here is the new text which reflects Alper's comments.
>>>>>>>> 
>>>>>>>> Yoshihiro Ohba
>>>>>>>> 
>>>>>>>> ---
>>>>>>>> In Section 4.2, change
>>>>>>>> 
>>>>>>>> From:
>>>>>>>> 
>>>>>>>> "  When a PaC receives the PANA-Start-Request message in response to
>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>>>  message. The PANA-Start-Answer message contains the initial sequence
>>>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
>>>>>>>>  the received Cookie as the PANA payload."
>>>>>>>> 
>>>>>>>> To:
>>>>>>>> 
>>>>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
>>>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
>>>>>>>>  information on the NAP and/or ISPs.
>>>>>>>> 
>>>>>>>>  When a PaC receives the PANA-Start-Request message in response to
>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>>>  message if it wishes to enter the authentication phase.  The
>>>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
>>>>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
>>>>>>>>  Cookie (if any) as the PANA payload.  If the received
>>>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
>>>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
>>>>>>>>  received NAP-Information AVP and, if any, one of the received
>>>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
>>>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
>>>>>>>>  If the PaC does not contain a NAP-Information AVP or an
>>>>>>>>  ISP-Information AVP, the EAP peer identity or some default
>>>>>>>>  information MAY be used to identify the binding."
>>>>>>>> 
>>>>>>>> 
>>>>>>>> In Section 9.3.3, change
>>>>>>>> 
>>>>>>>> from:
>>>>>>>> 
>>>>>>>> "
>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>                   [ Cookie ]
>>>>>>>>                 * [ AVP ]
>>>>>>>> "
>>>>>>>> 
>>>>>>>> to:
>>>>>>>> 
>>>>>>>> "
>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>                   [ Cookie ]
>>>>>>>>    [ NAP-Information ]
>>>>>>>>                 * [ ISP-Information ]
>>>>>>>>                 * [ AVP ]
>>>>>>>> "
>>>>>>>> 
>>>>>>>> 
>>>>>>>> In Section 9.3.4, change
>>>>>>>> 
>>>>>>>> from:
>>>>>>>> 
>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>                   [ Cookie ]
>>>>>>>>                 * [ AVP ]"
>>>>>>>> 
>>>>>>>> to:
>>>>>>>> 
>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>                   [ Cookie ]
>>>>>>>>    [ NAP-Information ]
>>>>>>>>                   [ ISP-Information ]
>>>>>>>>                 * [ AVP ]"
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Add the following sections:
>>>>>>>> 
>>>>>>>> "9.4.9 NAP-Information AVP
>>>>>>>> 
>>>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
>>>>>>>> contains one globally unique identifier of the NAP in a
>>>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>> 
>>>>>>>>     NAP-Information ::= < AVP Header: 1029 >
>>>>>>>>                          { Provider-Identifier }
>>>>>>>>                          { Provider-Name }
>>>>>>>>                        * [ AVP ]
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 9.4.10 ISP-Information AVP
>>>>>>>> 
>>>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
>>>>>>>> contains one globally unique identifier of the ISP in a
>>>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>> 
>>>>>>>>     ISP-Information ::= < AVP Header: 1030 >
>>>>>>>>                          { Provider-Identifier }
>>>>>>>>                          { Provider-Name }
>>>>>>>>                        * [ AVP ]
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 9.4.11 Provider-Identifier AVP
>>>>>>>> 
>>>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
>>>>>>>> and contains an IANA assigned "SMI Network Management Private
>>>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 9.4.12 Provider-Name AVP
>>>>>>>> 
>>>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
>>>>>>>> contains the UTF8-encoded name of the provider."
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> 
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Fri Oct 17 14:20:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14456
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 14:20:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAZCm-00033v-Mo
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 14:20:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HIK4s3011765
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 14:20:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAZCl-00033f-O7
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 14:20:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14386
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 14:19:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAZCj-0006na-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 14:20:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAZCi-0006nX-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 14:20:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAZCk-00033F-Br; Fri, 17 Oct 2003 14:20:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAZCX-00032K-8s
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 14:19:49 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14362
	for <pana@ietf.org>; Fri, 17 Oct 2003 14:19:39 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAZCU-0006nF-00
	for pana@ietf.org; Fri, 17 Oct 2003 14:19:46 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAZCU-0006nC-00
	for pana@ietf.org; Fri, 17 Oct 2003 14:19:46 -0400
Date: Fri, 17 Oct 2003 11:19:37 -0700
Subject: Re: [Pana] Re: New [issue25] Service Profile names
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBB580C9.AAC2%alper@docomolabs-usa.com>
In-Reply-To: <20031017180428.GA699@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> I think each authentication round can be associated with a different
> AAA, i.e., NAP authentication can use NAP's AAA and ISP authentication
> can use ISP's AAA (possibly with using a different identity in each
> authentication round).  Do you mean such a scenario should not be
> supported?

There is some misunderstanding. This is exactly what I'm trying to support
in the protocol design.

If PAA offers and PaC accepts to authenticte to NAP and ISP separately,
there will be two rounds of EAP authentication. Each round should be
associated with one service provider, whose identity is carried in a *-info
AVP. For example, in the first round, PaC can send NAP-info, in the second
round it can send ISP-info. My point was, NAP-info and ISP-info should not
be carried at the same time (round) in this case. (if you do, how will the
PAA know which AAA to contact? Would it be ISP's AAA, or NAP's AAA? Having a
single *-info makes it clear).

Alper




> 
> Yoshihiro Ohba
> 
> 
> 
>> 
>>>> 
>>>> In addition, I'm currently assuming that one PAA is associated with a
>>>> single NAP. In this case, including NAP-info in the answer may be
>>>> redundant.
>> 
>> Including a NAP-info in the answer (when separate authentication is going
>> on) means that the supplied authentication info should be used with the NAP.
>> (NAP's AAA).
>> 
>>>> 
>>>>>   - If PaC does not care about separate authentication, it unsets the
>>>>> S-flag
>>>>>     in PANA-start-answer, and this is same as if PAA never set the S-flag.
>>>> 
>>>> OK.
>> 
>> 
>> Alper
>> 
>> 
>>>> 
>>>> Yoshihiro Ohba
>>>> 
>>>>> 
>>>>> Does this make sense?
>>>>> 
>>>>> Alper
>>>>> 
>>>>> 
>>>>> 
>>>>>  
>>>>> 
>>>>> 
>>>>>  
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
>>>>>>> I was thinking something in terms of this:
>>>>>>> 
>>>>>>> - If only a NAP-info is included in the PANA-start-answer, that means
>>>>>>> the
>>>>>>> following authentication should be directed to particular NAP's AAA.
>>>>>>> - If only a ISP-info is included in the PANA-start-answer, that means
>>>>>>> the
>>>>>>> following authentication should be directed to particular ISP's AAA.
>>>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP
>>>>>>> client
>>>>>>> identifier may suggest. One *-info is included at a time when separate
>>>>>>> authentication will take place.
>>>>>> 
>>>>>> OK.
>>>>>> 
>>>>>>> 
>>>>>>> - If both NAP-info and ISP-info are included, that means only one
>>>>>>> authentication will take place. The *-info indicates the chosen service
>>>>>>> combination. The authentication request is forwarded to ISP's AAA.
>>>>>> 
>>>>>> It seems natural for this case that separate authentication will take
>>>>>> place with using particular NAP's AAA and ISP's AAA.
>>>>>> 
>>>>>>> 
>>>>>>> - If no *-info is included, that means the implicit selection depends on
>>>>>>> the
>>>>>>> EAP client identifier.
>>>>>> 
>>>>>> It seems natural for this case that only one authentication will
>>>>>> take place with the authentication request being forwarded to ISP's
>>>>>> AAA.
>>>>>> 
>>>>>>> 
>>>>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
>>>>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
>>>>>>> capability to provide separate auth along with the list of ISPs/NAP.
>>>>>>> PANA-start-answer can signal whether the PaC will do separate auths or
>>>>>>> not.
>>>>>>> A flag in the message header can deliver this capability/choice.
>>>>>> 
>>>>>> Or can we use *-info contained in PANA-start-{request,answer} for that
>>>>>> purpose instead of definig a new flag?
>>>>>> 
>>>>>> Yoshihiro Ohba
>>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>> Comments?
>>>>>>> 
>>>>>>> Alper
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> Here is the new text which reflects Alper's comments.
>>>>>>>> 
>>>>>>>> Yoshihiro Ohba
>>>>>>>> 
>>>>>>>> ---
>>>>>>>> In Section 4.2, change
>>>>>>>> 
>>>>>>>> From:
>>>>>>>> 
>>>>>>>> "  When a PaC receives the PANA-Start-Request message in response to
>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>>>  message. The PANA-Start-Answer message contains the initial sequence
>>>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
>>>>>>>>  the received Cookie as the PANA payload."
>>>>>>>> 
>>>>>>>> To:
>>>>>>>> 
>>>>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
>>>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
>>>>>>>>  information on the NAP and/or ISPs.
>>>>>>>> 
>>>>>>>>  When a PaC receives the PANA-Start-Request message in response to
>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>>>  message if it wishes to enter the authentication phase.  The
>>>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
>>>>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
>>>>>>>>  Cookie (if any) as the PANA payload.  If the received
>>>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
>>>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
>>>>>>>>  received NAP-Information AVP and, if any, one of the received
>>>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
>>>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
>>>>>>>>  If the PaC does not contain a NAP-Information AVP or an
>>>>>>>>  ISP-Information AVP, the EAP peer identity or some default
>>>>>>>>  information MAY be used to identify the binding."
>>>>>>>> 
>>>>>>>> 
>>>>>>>> In Section 9.3.3, change
>>>>>>>> 
>>>>>>>> from:
>>>>>>>> 
>>>>>>>> "
>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>                   [ Cookie ]
>>>>>>>>                 * [ AVP ]
>>>>>>>> "
>>>>>>>> 
>>>>>>>> to:
>>>>>>>> 
>>>>>>>> "
>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>                   [ Cookie ]
>>>>>>>>    [ NAP-Information ]
>>>>>>>>                 * [ ISP-Information ]
>>>>>>>>                 * [ AVP ]
>>>>>>>> "
>>>>>>>> 
>>>>>>>> 
>>>>>>>> In Section 9.3.4, change
>>>>>>>> 
>>>>>>>> from:
>>>>>>>> 
>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>                   [ Cookie ]
>>>>>>>>                 * [ AVP ]"
>>>>>>>> 
>>>>>>>> to:
>>>>>>>> 
>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>                   [ Cookie ]
>>>>>>>>    [ NAP-Information ]
>>>>>>>>                   [ ISP-Information ]
>>>>>>>>                 * [ AVP ]"
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Add the following sections:
>>>>>>>> 
>>>>>>>> "9.4.9 NAP-Information AVP
>>>>>>>> 
>>>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
>>>>>>>> contains one globally unique identifier of the NAP in a
>>>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>> 
>>>>>>>>     NAP-Information ::= < AVP Header: 1029 >
>>>>>>>>                          { Provider-Identifier }
>>>>>>>>                          { Provider-Name }
>>>>>>>>                        * [ AVP ]
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 9.4.10 ISP-Information AVP
>>>>>>>> 
>>>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
>>>>>>>> contains one globally unique identifier of the ISP in a
>>>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>> 
>>>>>>>>     ISP-Information ::= < AVP Header: 1030 >
>>>>>>>>                          { Provider-Identifier }
>>>>>>>>                          { Provider-Name }
>>>>>>>>                        * [ AVP ]
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 9.4.11 Provider-Identifier AVP
>>>>>>>> 
>>>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
>>>>>>>> and contains an IANA assigned "SMI Network Management Private
>>>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 9.4.12 Provider-Name AVP
>>>>>>>> 
>>>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
>>>>>>>> contains the UTF8-encoded name of the provider."
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> 
> 
> _______________________________________________
> 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-admin@ietf.org  Fri Oct 17 15:35:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18384
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 15:35:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAaNK-0006CZ-88; Fri, 17 Oct 2003 15:35:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAaMl-00068w-RX
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 15:34:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18164
	for <pana@ietf.org>; Fri, 17 Oct 2003 15:34:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAaMk-0007Q8-00
	for pana@ietf.org; Fri, 17 Oct 2003 15:34:26 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAaMj-0007Q0-00
	for pana@ietf.org; Fri, 17 Oct 2003 15:34:25 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9HJYJF1020764;
	Sat, 18 Oct 2003 04:34:19 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9HJYJbC016746;
	Sat, 18 Oct 2003 04:34:19 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA16745 ; Sat, 18 Oct 2003 04:34:18 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA21045; Sat, 18 Oct 2003 04:34:18 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA01392; Sat, 18 Oct 2003 04:34:18 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9HJYHib027323;
	Sat, 18 Oct 2003 04:34:17 +0900 (JST)
Received: from steelhead ([159.119.168.86]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMX000YK2D3GH@tsbpo1.po.toshiba.co.jp>; Sat,
 18 Oct 2003 04:34:16 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAaLM-0000Vo-00; Fri, 17 Oct 2003 12:33:00 -0700
Date: Fri, 17 Oct 2003 12:33:00 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Re: New [issue25] Service Profile names
In-reply-to: <BBB580C9.AAC2%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Message-id: <20031017193300.GA1853@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031017180428.GA699@steelhead>
 <BBB580C9.AAC2%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 17, 2003 at 11:19:37AM -0700, Alper Yegin wrote:
> > I think each authentication round can be associated with a different
> > AAA, i.e., NAP authentication can use NAP's AAA and ISP authentication
> > can use ISP's AAA (possibly with using a different identity in each
> > authentication round).  Do you mean such a scenario should not be
> > supported?
> 
> There is some misunderstanding. This is exactly what I'm trying to support
> in the protocol design.

OK. But...

> 
> If PAA offers and PaC accepts to authenticte to NAP and ISP separately,
> there will be two rounds of EAP authentication. Each round should be
> associated with one service provider, whose identity is carried in a *-info
> AVP. For example, in the first round, PaC can send NAP-info, in the second
> round it can send ISP-info. My point was, NAP-info and ISP-info should not
> be carried at the same time (round) in this case. (if you do, how will the
> PAA know which AAA to contact? Would it be ISP's AAA, or NAP's AAA? Having a
> single *-info makes it clear).

in the current design there is only one PANA-Start-Request/Answer exchange 
even when two EAP authentication rounds are performed in a PANA authentication 
phase.  How can we specify the two *-info AVPs in separate answer messages?

Yoshihiro Ohba

> 
> Alper
> 
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > 
> >> 
> >>>> 
> >>>> In addition, I'm currently assuming that one PAA is associated with a
> >>>> single NAP. In this case, including NAP-info in the answer may be
> >>>> redundant.
> >> 
> >> Including a NAP-info in the answer (when separate authentication is going
> >> on) means that the supplied authentication info should be used with the NAP.
> >> (NAP's AAA).
> >> 
> >>>> 
> >>>>>   - If PaC does not care about separate authentication, it unsets the
> >>>>> S-flag
> >>>>>     in PANA-start-answer, and this is same as if PAA never set the S-flag.
> >>>> 
> >>>> OK.
> >> 
> >> 
> >> Alper
> >> 
> >> 
> >>>> 
> >>>> Yoshihiro Ohba
> >>>> 
> >>>>> 
> >>>>> Does this make sense?
> >>>>> 
> >>>>> Alper
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>>  
> >>>>> 
> >>>>> 
> >>>>>  
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
> >>>>>>> I was thinking something in terms of this:
> >>>>>>> 
> >>>>>>> - If only a NAP-info is included in the PANA-start-answer, that means
> >>>>>>> the
> >>>>>>> following authentication should be directed to particular NAP's AAA.
> >>>>>>> - If only a ISP-info is included in the PANA-start-answer, that means
> >>>>>>> the
> >>>>>>> following authentication should be directed to particular ISP's AAA.
> >>>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP
> >>>>>>> client
> >>>>>>> identifier may suggest. One *-info is included at a time when separate
> >>>>>>> authentication will take place.
> >>>>>> 
> >>>>>> OK.
> >>>>>> 
> >>>>>>> 
> >>>>>>> - If both NAP-info and ISP-info are included, that means only one
> >>>>>>> authentication will take place. The *-info indicates the chosen service
> >>>>>>> combination. The authentication request is forwarded to ISP's AAA.
> >>>>>> 
> >>>>>> It seems natural for this case that separate authentication will take
> >>>>>> place with using particular NAP's AAA and ISP's AAA.
> >>>>>> 
> >>>>>>> 
> >>>>>>> - If no *-info is included, that means the implicit selection depends on
> >>>>>>> the
> >>>>>>> EAP client identifier.
> >>>>>> 
> >>>>>> It seems natural for this case that only one authentication will
> >>>>>> take place with the authentication request being forwarded to ISP's
> >>>>>> AAA.
> >>>>>> 
> >>>>>>> 
> >>>>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
> >>>>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
> >>>>>>> capability to provide separate auth along with the list of ISPs/NAP.
> >>>>>>> PANA-start-answer can signal whether the PaC will do separate auths or
> >>>>>>> not.
> >>>>>>> A flag in the message header can deliver this capability/choice.
> >>>>>> 
> >>>>>> Or can we use *-info contained in PANA-start-{request,answer} for that
> >>>>>> purpose instead of definig a new flag?
> >>>>>> 
> >>>>>> Yoshihiro Ohba
> >>>>>> 
> >>>>>> 
> >>>>>>> 
> >>>>>>> Comments?
> >>>>>>> 
> >>>>>>> Alper
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>>> Here is the new text which reflects Alper's comments.
> >>>>>>>> 
> >>>>>>>> Yoshihiro Ohba
> >>>>>>>> 
> >>>>>>>> ---
> >>>>>>>> In Section 4.2, change
> >>>>>>>> 
> >>>>>>>> From:
> >>>>>>>> 
> >>>>>>>> "  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>>>  message. The PANA-Start-Answer message contains the initial sequence
> >>>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
> >>>>>>>>  the received Cookie as the PANA payload."
> >>>>>>>> 
> >>>>>>>> To:
> >>>>>>>> 
> >>>>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
> >>>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
> >>>>>>>>  information on the NAP and/or ISPs.
> >>>>>>>> 
> >>>>>>>>  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>>>  message if it wishes to enter the authentication phase.  The
> >>>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
> >>>>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
> >>>>>>>>  Cookie (if any) as the PANA payload.  If the received
> >>>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
> >>>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
> >>>>>>>>  received NAP-Information AVP and, if any, one of the received
> >>>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
> >>>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
> >>>>>>>>  If the PaC does not contain a NAP-Information AVP or an
> >>>>>>>>  ISP-Information AVP, the EAP peer identity or some default
> >>>>>>>>  information MAY be used to identify the binding."
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> In Section 9.3.3, change
> >>>>>>>> 
> >>>>>>>> from:
> >>>>>>>> 
> >>>>>>>> "
> >>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>>>                   [ Cookie ]
> >>>>>>>>                 * [ AVP ]
> >>>>>>>> "
> >>>>>>>> 
> >>>>>>>> to:
> >>>>>>>> 
> >>>>>>>> "
> >>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>>>                   [ Cookie ]
> >>>>>>>>    [ NAP-Information ]
> >>>>>>>>                 * [ ISP-Information ]
> >>>>>>>>                 * [ AVP ]
> >>>>>>>> "
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> In Section 9.3.4, change
> >>>>>>>> 
> >>>>>>>> from:
> >>>>>>>> 
> >>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>>>                   [ Cookie ]
> >>>>>>>>                 * [ AVP ]"
> >>>>>>>> 
> >>>>>>>> to:
> >>>>>>>> 
> >>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>>>                   [ Cookie ]
> >>>>>>>>    [ NAP-Information ]
> >>>>>>>>                   [ ISP-Information ]
> >>>>>>>>                 * [ AVP ]"
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> Add the following sections:
> >>>>>>>> 
> >>>>>>>> "9.4.9 NAP-Information AVP
> >>>>>>>> 
> >>>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
> >>>>>>>> contains one globally unique identifier of the NAP in a
> >>>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
> >>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>>>> 
> >>>>>>>>     NAP-Information ::= < AVP Header: 1029 >
> >>>>>>>>                          { Provider-Identifier }
> >>>>>>>>                          { Provider-Name }
> >>>>>>>>                        * [ AVP ]
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 9.4.10 ISP-Information AVP
> >>>>>>>> 
> >>>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
> >>>>>>>> contains one globally unique identifier of the ISP in a
> >>>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
> >>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>>>> 
> >>>>>>>>     ISP-Information ::= < AVP Header: 1030 >
> >>>>>>>>                          { Provider-Identifier }
> >>>>>>>>                          { Provider-Name }
> >>>>>>>>                        * [ AVP ]
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 9.4.11 Provider-Identifier AVP
> >>>>>>>> 
> >>>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
> >>>>>>>> and contains an IANA assigned "SMI Network Management Private
> >>>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 9.4.12 Provider-Name AVP
> >>>>>>>> 
> >>>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
> >>>>>>>> contains the UTF8-encoded name of the provider."
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>> 
> >>> 
> >> 
> > 
> > _______________________________________________
> > 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 exim@www1.ietf.org  Fri Oct 17 15:35:30 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18416
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 15:35:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAaNN-0006Dn-2I
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 15:35:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HJZ4uM023909
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 15:35:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAaNM-0006DP-MX
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 15:35:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18278
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 15:34:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAaNL-0007Qs-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 15:35:03 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAaNK-0007Qp-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 15:35:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAaNK-0006CZ-88; Fri, 17 Oct 2003 15:35:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAaMl-00068w-RX
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 15:34:28 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18164
	for <pana@ietf.org>; Fri, 17 Oct 2003 15:34:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAaMk-0007Q8-00
	for pana@ietf.org; Fri, 17 Oct 2003 15:34:26 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAaMj-0007Q0-00
	for pana@ietf.org; Fri, 17 Oct 2003 15:34:25 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9HJYJF1020764;
	Sat, 18 Oct 2003 04:34:19 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9HJYJbC016746;
	Sat, 18 Oct 2003 04:34:19 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA16745 ; Sat, 18 Oct 2003 04:34:18 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA21045; Sat, 18 Oct 2003 04:34:18 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA01392; Sat, 18 Oct 2003 04:34:18 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9HJYHib027323;
	Sat, 18 Oct 2003 04:34:17 +0900 (JST)
Received: from steelhead ([159.119.168.86]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMX000YK2D3GH@tsbpo1.po.toshiba.co.jp>; Sat,
 18 Oct 2003 04:34:16 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAaLM-0000Vo-00; Fri, 17 Oct 2003 12:33:00 -0700
Date: Fri, 17 Oct 2003 12:33:00 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Re: New [issue25] Service Profile names
In-reply-to: <BBB580C9.AAC2%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Message-id: <20031017193300.GA1853@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031017180428.GA699@steelhead>
 <BBB580C9.AAC2%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 17, 2003 at 11:19:37AM -0700, Alper Yegin wrote:
> > I think each authentication round can be associated with a different
> > AAA, i.e., NAP authentication can use NAP's AAA and ISP authentication
> > can use ISP's AAA (possibly with using a different identity in each
> > authentication round).  Do you mean such a scenario should not be
> > supported?
> 
> There is some misunderstanding. This is exactly what I'm trying to support
> in the protocol design.

OK. But...

> 
> If PAA offers and PaC accepts to authenticte to NAP and ISP separately,
> there will be two rounds of EAP authentication. Each round should be
> associated with one service provider, whose identity is carried in a *-info
> AVP. For example, in the first round, PaC can send NAP-info, in the second
> round it can send ISP-info. My point was, NAP-info and ISP-info should not
> be carried at the same time (round) in this case. (if you do, how will the
> PAA know which AAA to contact? Would it be ISP's AAA, or NAP's AAA? Having a
> single *-info makes it clear).

in the current design there is only one PANA-Start-Request/Answer exchange 
even when two EAP authentication rounds are performed in a PANA authentication 
phase.  How can we specify the two *-info AVPs in separate answer messages?

Yoshihiro Ohba

> 
> Alper
> 
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> > 
> >> 
> >>>> 
> >>>> In addition, I'm currently assuming that one PAA is associated with a
> >>>> single NAP. In this case, including NAP-info in the answer may be
> >>>> redundant.
> >> 
> >> Including a NAP-info in the answer (when separate authentication is going
> >> on) means that the supplied authentication info should be used with the NAP.
> >> (NAP's AAA).
> >> 
> >>>> 
> >>>>>   - If PaC does not care about separate authentication, it unsets the
> >>>>> S-flag
> >>>>>     in PANA-start-answer, and this is same as if PAA never set the S-flag.
> >>>> 
> >>>> OK.
> >> 
> >> 
> >> Alper
> >> 
> >> 
> >>>> 
> >>>> Yoshihiro Ohba
> >>>> 
> >>>>> 
> >>>>> Does this make sense?
> >>>>> 
> >>>>> Alper
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>>  
> >>>>> 
> >>>>> 
> >>>>>  
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
> >>>>>>> I was thinking something in terms of this:
> >>>>>>> 
> >>>>>>> - If only a NAP-info is included in the PANA-start-answer, that means
> >>>>>>> the
> >>>>>>> following authentication should be directed to particular NAP's AAA.
> >>>>>>> - If only a ISP-info is included in the PANA-start-answer, that means
> >>>>>>> the
> >>>>>>> following authentication should be directed to particular ISP's AAA.
> >>>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP
> >>>>>>> client
> >>>>>>> identifier may suggest. One *-info is included at a time when separate
> >>>>>>> authentication will take place.
> >>>>>> 
> >>>>>> OK.
> >>>>>> 
> >>>>>>> 
> >>>>>>> - If both NAP-info and ISP-info are included, that means only one
> >>>>>>> authentication will take place. The *-info indicates the chosen service
> >>>>>>> combination. The authentication request is forwarded to ISP's AAA.
> >>>>>> 
> >>>>>> It seems natural for this case that separate authentication will take
> >>>>>> place with using particular NAP's AAA and ISP's AAA.
> >>>>>> 
> >>>>>>> 
> >>>>>>> - If no *-info is included, that means the implicit selection depends on
> >>>>>>> the
> >>>>>>> EAP client identifier.
> >>>>>> 
> >>>>>> It seems natural for this case that only one authentication will
> >>>>>> take place with the authentication request being forwarded to ISP's
> >>>>>> AAA.
> >>>>>> 
> >>>>>>> 
> >>>>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
> >>>>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
> >>>>>>> capability to provide separate auth along with the list of ISPs/NAP.
> >>>>>>> PANA-start-answer can signal whether the PaC will do separate auths or
> >>>>>>> not.
> >>>>>>> A flag in the message header can deliver this capability/choice.
> >>>>>> 
> >>>>>> Or can we use *-info contained in PANA-start-{request,answer} for that
> >>>>>> purpose instead of definig a new flag?
> >>>>>> 
> >>>>>> Yoshihiro Ohba
> >>>>>> 
> >>>>>> 
> >>>>>>> 
> >>>>>>> Comments?
> >>>>>>> 
> >>>>>>> Alper
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>>> Here is the new text which reflects Alper's comments.
> >>>>>>>> 
> >>>>>>>> Yoshihiro Ohba
> >>>>>>>> 
> >>>>>>>> ---
> >>>>>>>> In Section 4.2, change
> >>>>>>>> 
> >>>>>>>> From:
> >>>>>>>> 
> >>>>>>>> "  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>>>  message. The PANA-Start-Answer message contains the initial sequence
> >>>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
> >>>>>>>>  the received Cookie as the PANA payload."
> >>>>>>>> 
> >>>>>>>> To:
> >>>>>>>> 
> >>>>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
> >>>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
> >>>>>>>>  information on the NAP and/or ISPs.
> >>>>>>>> 
> >>>>>>>>  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>>>  message if it wishes to enter the authentication phase.  The
> >>>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
> >>>>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
> >>>>>>>>  Cookie (if any) as the PANA payload.  If the received
> >>>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
> >>>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
> >>>>>>>>  received NAP-Information AVP and, if any, one of the received
> >>>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
> >>>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
> >>>>>>>>  If the PaC does not contain a NAP-Information AVP or an
> >>>>>>>>  ISP-Information AVP, the EAP peer identity or some default
> >>>>>>>>  information MAY be used to identify the binding."
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> In Section 9.3.3, change
> >>>>>>>> 
> >>>>>>>> from:
> >>>>>>>> 
> >>>>>>>> "
> >>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>>>                   [ Cookie ]
> >>>>>>>>                 * [ AVP ]
> >>>>>>>> "
> >>>>>>>> 
> >>>>>>>> to:
> >>>>>>>> 
> >>>>>>>> "
> >>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>>>                   [ Cookie ]
> >>>>>>>>    [ NAP-Information ]
> >>>>>>>>                 * [ ISP-Information ]
> >>>>>>>>                 * [ AVP ]
> >>>>>>>> "
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> In Section 9.3.4, change
> >>>>>>>> 
> >>>>>>>> from:
> >>>>>>>> 
> >>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>>>                   [ Cookie ]
> >>>>>>>>                 * [ AVP ]"
> >>>>>>>> 
> >>>>>>>> to:
> >>>>>>>> 
> >>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>>>                   [ Cookie ]
> >>>>>>>>    [ NAP-Information ]
> >>>>>>>>                   [ ISP-Information ]
> >>>>>>>>                 * [ AVP ]"
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> Add the following sections:
> >>>>>>>> 
> >>>>>>>> "9.4.9 NAP-Information AVP
> >>>>>>>> 
> >>>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
> >>>>>>>> contains one globally unique identifier of the NAP in a
> >>>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
> >>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>>>> 
> >>>>>>>>     NAP-Information ::= < AVP Header: 1029 >
> >>>>>>>>                          { Provider-Identifier }
> >>>>>>>>                          { Provider-Name }
> >>>>>>>>                        * [ AVP ]
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 9.4.10 ISP-Information AVP
> >>>>>>>> 
> >>>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
> >>>>>>>> contains one globally unique identifier of the ISP in a
> >>>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
> >>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>>>> 
> >>>>>>>>     ISP-Information ::= < AVP Header: 1030 >
> >>>>>>>>                          { Provider-Identifier }
> >>>>>>>>                          { Provider-Name }
> >>>>>>>>                        * [ AVP ]
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 9.4.11 Provider-Identifier AVP
> >>>>>>>> 
> >>>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
> >>>>>>>> and contains an IANA assigned "SMI Network Management Private
> >>>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 9.4.12 Provider-Name AVP
> >>>>>>>> 
> >>>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
> >>>>>>>> contains the UTF8-encoded name of the provider."
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>> 
> >>> 
> >> 
> > 
> > _______________________________________________
> > 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-admin@ietf.org  Fri Oct 17 16:19:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22448
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 16:19:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAb3t-00007r-MA; Fri, 17 Oct 2003 16:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAb3R-000072-SZ
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 16:18:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22419
	for <pana@ietf.org>; Fri, 17 Oct 2003 16:18:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAb3Q-0000uG-00
	for pana@ietf.org; Fri, 17 Oct 2003 16:18:32 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAb3O-0000uC-00
	for pana@ietf.org; Fri, 17 Oct 2003 16:18:30 -0400
Date: Fri, 17 Oct 2003 13:18:21 -0700
Subject: Re: [Pana] Re: New [issue25] Service Profile names
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBB59C9D.AAEB%alper@docomolabs-usa.com>
In-Reply-To: <20031017193300.GA1853@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> in the current design there is only one PANA-Start-Request/Answer exchange
> even when two EAP authentication rounds are performed in a PANA authentication
> phase.  How can we specify the two *-info AVPs in separate answer messages?

You are right, I forgot that... How about including the other *-info in
PANA-Bind-answer at the end of first EAP authentication (or, in the first
PANA-auth-answer message following the PANA-binding)?

Alper




> 
> Yoshihiro Ohba
> 
>> 
>> Alper
>> 
>> 
>> 
>> 
>>> 
>>> Yoshihiro Ohba
>>> 
>>> 
>>> 
>>>> 
>>>>>> 
>>>>>> In addition, I'm currently assuming that one PAA is associated with a
>>>>>> single NAP. In this case, including NAP-info in the answer may be
>>>>>> redundant.
>>>> 
>>>> Including a NAP-info in the answer (when separate authentication is going
>>>> on) means that the supplied authentication info should be used with the
>>>> NAP.
>>>> (NAP's AAA).
>>>> 
>>>>>> 
>>>>>>>   - If PaC does not care about separate authentication, it unsets the
>>>>>>> S-flag
>>>>>>>     in PANA-start-answer, and this is same as if PAA never set the
>>>>>>> S-flag.
>>>>>> 
>>>>>> OK.
>>>> 
>>>> 
>>>> Alper
>>>> 
>>>> 
>>>>>> 
>>>>>> Yoshihiro Ohba
>>>>>> 
>>>>>>> 
>>>>>>> Does this make sense?
>>>>>>> 
>>>>>>> Alper
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>  
>>>>>>> 
>>>>>>> 
>>>>>>>  
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
>>>>>>>>> I was thinking something in terms of this:
>>>>>>>>> 
>>>>>>>>> - If only a NAP-info is included in the PANA-start-answer, that means
>>>>>>>>> the
>>>>>>>>> following authentication should be directed to particular NAP's AAA.
>>>>>>>>> - If only a ISP-info is included in the PANA-start-answer, that means
>>>>>>>>> the
>>>>>>>>> following authentication should be directed to particular ISP's AAA.
>>>>>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP
>>>>>>>>> client
>>>>>>>>> identifier may suggest. One *-info is included at a time when separate
>>>>>>>>> authentication will take place.
>>>>>>>> 
>>>>>>>> OK.
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> - If both NAP-info and ISP-info are included, that means only one
>>>>>>>>> authentication will take place. The *-info indicates the chosen
>>>>>>>>> service
>>>>>>>>> combination. The authentication request is forwarded to ISP's AAA.
>>>>>>>> 
>>>>>>>> It seems natural for this case that separate authentication will take
>>>>>>>> place with using particular NAP's AAA and ISP's AAA.
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> - If no *-info is included, that means the implicit selection depends
>>>>>>>>> on
>>>>>>>>> the
>>>>>>>>> EAP client identifier.
>>>>>>>> 
>>>>>>>> It seems natural for this case that only one authentication will
>>>>>>>> take place with the authentication request being forwarded to ISP's
>>>>>>>> AAA.
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
>>>>>>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
>>>>>>>>> capability to provide separate auth along with the list of ISPs/NAP.
>>>>>>>>> PANA-start-answer can signal whether the PaC will do separate auths or
>>>>>>>>> not.
>>>>>>>>> A flag in the message header can deliver this capability/choice.
>>>>>>>> 
>>>>>>>> Or can we use *-info contained in PANA-start-{request,answer} for that
>>>>>>>> purpose instead of definig a new flag?
>>>>>>>> 
>>>>>>>> Yoshihiro Ohba
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Comments?
>>>>>>>>> 
>>>>>>>>> Alper
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Here is the new text which reflects Alper's comments.
>>>>>>>>>> 
>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>> 
>>>>>>>>>> ---
>>>>>>>>>> In Section 4.2, change
>>>>>>>>>> 
>>>>>>>>>> From:
>>>>>>>>>> 
>>>>>>>>>> "  When a PaC receives the PANA-Start-Request message in response to
>>>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>>>>>  message. The PANA-Start-Answer message contains the initial sequence
>>>>>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
>>>>>>>>>>  the received Cookie as the PANA payload."
>>>>>>>>>> 
>>>>>>>>>> To:
>>>>>>>>>> 
>>>>>>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
>>>>>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
>>>>>>>>>>  information on the NAP and/or ISPs.
>>>>>>>>>> 
>>>>>>>>>>  When a PaC receives the PANA-Start-Request message in response to
>>>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>>>>>  message if it wishes to enter the authentication phase.  The
>>>>>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
>>>>>>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
>>>>>>>>>>  Cookie (if any) as the PANA payload.  If the received
>>>>>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
>>>>>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
>>>>>>>>>>  received NAP-Information AVP and, if any, one of the received
>>>>>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
>>>>>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
>>>>>>>>>>  If the PaC does not contain a NAP-Information AVP or an
>>>>>>>>>>  ISP-Information AVP, the EAP peer identity or some default
>>>>>>>>>>  information MAY be used to identify the binding."
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> In Section 9.3.3, change
>>>>>>>>>> 
>>>>>>>>>> from:
>>>>>>>>>> 
>>>>>>>>>> "
>>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>                 * [ AVP ]
>>>>>>>>>> "
>>>>>>>>>> 
>>>>>>>>>> to:
>>>>>>>>>> 
>>>>>>>>>> "
>>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>    [ NAP-Information ]
>>>>>>>>>>                 * [ ISP-Information ]
>>>>>>>>>>                 * [ AVP ]
>>>>>>>>>> "
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> In Section 9.3.4, change
>>>>>>>>>> 
>>>>>>>>>> from:
>>>>>>>>>> 
>>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>                 * [ AVP ]"
>>>>>>>>>> 
>>>>>>>>>> to:
>>>>>>>>>> 
>>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>    [ NAP-Information ]
>>>>>>>>>>                   [ ISP-Information ]
>>>>>>>>>>                 * [ AVP ]"
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> Add the following sections:
>>>>>>>>>> 
>>>>>>>>>> "9.4.9 NAP-Information AVP
>>>>>>>>>> 
>>>>>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
>>>>>>>>>> contains one globally unique identifier of the NAP in a
>>>>>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
>>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>>>> 
>>>>>>>>>>     NAP-Information ::= < AVP Header: 1029 >
>>>>>>>>>>                          { Provider-Identifier }
>>>>>>>>>>                          { Provider-Name }
>>>>>>>>>>                        * [ AVP ]
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 9.4.10 ISP-Information AVP
>>>>>>>>>> 
>>>>>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
>>>>>>>>>> contains one globally unique identifier of the ISP in a
>>>>>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
>>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>>>> 
>>>>>>>>>>     ISP-Information ::= < AVP Header: 1030 >
>>>>>>>>>>                          { Provider-Identifier }
>>>>>>>>>>                          { Provider-Name }
>>>>>>>>>>                        * [ AVP ]
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 9.4.11 Provider-Identifier AVP
>>>>>>>>>> 
>>>>>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
>>>>>>>>>> and contains an IANA assigned "SMI Network Management Private
>>>>>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 9.4.12 Provider-Name AVP
>>>>>>>>>> 
>>>>>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
>>>>>>>>>> contains the UTF8-encoded name of the provider."
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> 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 exim@www1.ietf.org  Fri Oct 17 16:19:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22466
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 16:19:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAb3w-00008h-6r
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 16:19:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HKJ4k2000529
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 16:19:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAb3w-00008S-0g
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 16:19:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22437
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 16:18:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAb3u-0000ug-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 16:19:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAb3t-0000ud-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 16:19:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAb3t-00007r-MA; Fri, 17 Oct 2003 16:19:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAb3R-000072-SZ
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 16:18:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22419
	for <pana@ietf.org>; Fri, 17 Oct 2003 16:18:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAb3Q-0000uG-00
	for pana@ietf.org; Fri, 17 Oct 2003 16:18:32 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAb3O-0000uC-00
	for pana@ietf.org; Fri, 17 Oct 2003 16:18:30 -0400
Date: Fri, 17 Oct 2003 13:18:21 -0700
Subject: Re: [Pana] Re: New [issue25] Service Profile names
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBB59C9D.AAEB%alper@docomolabs-usa.com>
In-Reply-To: <20031017193300.GA1853@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> in the current design there is only one PANA-Start-Request/Answer exchange
> even when two EAP authentication rounds are performed in a PANA authentication
> phase.  How can we specify the two *-info AVPs in separate answer messages?

You are right, I forgot that... How about including the other *-info in
PANA-Bind-answer at the end of first EAP authentication (or, in the first
PANA-auth-answer message following the PANA-binding)?

Alper




> 
> Yoshihiro Ohba
> 
>> 
>> Alper
>> 
>> 
>> 
>> 
>>> 
>>> Yoshihiro Ohba
>>> 
>>> 
>>> 
>>>> 
>>>>>> 
>>>>>> In addition, I'm currently assuming that one PAA is associated with a
>>>>>> single NAP. In this case, including NAP-info in the answer may be
>>>>>> redundant.
>>>> 
>>>> Including a NAP-info in the answer (when separate authentication is going
>>>> on) means that the supplied authentication info should be used with the
>>>> NAP.
>>>> (NAP's AAA).
>>>> 
>>>>>> 
>>>>>>>   - If PaC does not care about separate authentication, it unsets the
>>>>>>> S-flag
>>>>>>>     in PANA-start-answer, and this is same as if PAA never set the
>>>>>>> S-flag.
>>>>>> 
>>>>>> OK.
>>>> 
>>>> 
>>>> Alper
>>>> 
>>>> 
>>>>>> 
>>>>>> Yoshihiro Ohba
>>>>>> 
>>>>>>> 
>>>>>>> Does this make sense?
>>>>>>> 
>>>>>>> Alper
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>  
>>>>>>> 
>>>>>>> 
>>>>>>>  
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
>>>>>>>>> I was thinking something in terms of this:
>>>>>>>>> 
>>>>>>>>> - If only a NAP-info is included in the PANA-start-answer, that means
>>>>>>>>> the
>>>>>>>>> following authentication should be directed to particular NAP's AAA.
>>>>>>>>> - If only a ISP-info is included in the PANA-start-answer, that means
>>>>>>>>> the
>>>>>>>>> following authentication should be directed to particular ISP's AAA.
>>>>>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP
>>>>>>>>> client
>>>>>>>>> identifier may suggest. One *-info is included at a time when separate
>>>>>>>>> authentication will take place.
>>>>>>>> 
>>>>>>>> OK.
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> - If both NAP-info and ISP-info are included, that means only one
>>>>>>>>> authentication will take place. The *-info indicates the chosen
>>>>>>>>> service
>>>>>>>>> combination. The authentication request is forwarded to ISP's AAA.
>>>>>>>> 
>>>>>>>> It seems natural for this case that separate authentication will take
>>>>>>>> place with using particular NAP's AAA and ISP's AAA.
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> - If no *-info is included, that means the implicit selection depends
>>>>>>>>> on
>>>>>>>>> the
>>>>>>>>> EAP client identifier.
>>>>>>>> 
>>>>>>>> It seems natural for this case that only one authentication will
>>>>>>>> take place with the authentication request being forwarded to ISP's
>>>>>>>> AAA.
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
>>>>>>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
>>>>>>>>> capability to provide separate auth along with the list of ISPs/NAP.
>>>>>>>>> PANA-start-answer can signal whether the PaC will do separate auths or
>>>>>>>>> not.
>>>>>>>>> A flag in the message header can deliver this capability/choice.
>>>>>>>> 
>>>>>>>> Or can we use *-info contained in PANA-start-{request,answer} for that
>>>>>>>> purpose instead of definig a new flag?
>>>>>>>> 
>>>>>>>> Yoshihiro Ohba
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Comments?
>>>>>>>>> 
>>>>>>>>> Alper
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Here is the new text which reflects Alper's comments.
>>>>>>>>>> 
>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>> 
>>>>>>>>>> ---
>>>>>>>>>> In Section 4.2, change
>>>>>>>>>> 
>>>>>>>>>> From:
>>>>>>>>>> 
>>>>>>>>>> "  When a PaC receives the PANA-Start-Request message in response to
>>>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>>>>>  message. The PANA-Start-Answer message contains the initial sequence
>>>>>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
>>>>>>>>>>  the received Cookie as the PANA payload."
>>>>>>>>>> 
>>>>>>>>>> To:
>>>>>>>>>> 
>>>>>>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
>>>>>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
>>>>>>>>>>  information on the NAP and/or ISPs.
>>>>>>>>>> 
>>>>>>>>>>  When a PaC receives the PANA-Start-Request message in response to
>>>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
>>>>>>>>>>  message if it wishes to enter the authentication phase.  The
>>>>>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
>>>>>>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
>>>>>>>>>>  Cookie (if any) as the PANA payload.  If the received
>>>>>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
>>>>>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
>>>>>>>>>>  received NAP-Information AVP and, if any, one of the received
>>>>>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
>>>>>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
>>>>>>>>>>  If the PaC does not contain a NAP-Information AVP or an
>>>>>>>>>>  ISP-Information AVP, the EAP peer identity or some default
>>>>>>>>>>  information MAY be used to identify the binding."
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> In Section 9.3.3, change
>>>>>>>>>> 
>>>>>>>>>> from:
>>>>>>>>>> 
>>>>>>>>>> "
>>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>                 * [ AVP ]
>>>>>>>>>> "
>>>>>>>>>> 
>>>>>>>>>> to:
>>>>>>>>>> 
>>>>>>>>>> "
>>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>    [ NAP-Information ]
>>>>>>>>>>                 * [ ISP-Information ]
>>>>>>>>>>                 * [ AVP ]
>>>>>>>>>> "
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> In Section 9.3.4, change
>>>>>>>>>> 
>>>>>>>>>> from:
>>>>>>>>>> 
>>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>                 * [ AVP ]"
>>>>>>>>>> 
>>>>>>>>>> to:
>>>>>>>>>> 
>>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>    [ NAP-Information ]
>>>>>>>>>>                   [ ISP-Information ]
>>>>>>>>>>                 * [ AVP ]"
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> Add the following sections:
>>>>>>>>>> 
>>>>>>>>>> "9.4.9 NAP-Information AVP
>>>>>>>>>> 
>>>>>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
>>>>>>>>>> contains one globally unique identifier of the NAP in a
>>>>>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
>>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>>>> 
>>>>>>>>>>     NAP-Information ::= < AVP Header: 1029 >
>>>>>>>>>>                          { Provider-Identifier }
>>>>>>>>>>                          { Provider-Name }
>>>>>>>>>>                        * [ AVP ]
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 9.4.10 ISP-Information AVP
>>>>>>>>>> 
>>>>>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
>>>>>>>>>> contains one globally unique identifier of the ISP in a
>>>>>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
>>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>>>> 
>>>>>>>>>>     ISP-Information ::= < AVP Header: 1030 >
>>>>>>>>>>                          { Provider-Identifier }
>>>>>>>>>>                          { Provider-Name }
>>>>>>>>>>                        * [ AVP ]
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 9.4.11 Provider-Identifier AVP
>>>>>>>>>> 
>>>>>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
>>>>>>>>>> and contains an IANA assigned "SMI Network Management Private
>>>>>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 9.4.12 Provider-Name AVP
>>>>>>>>>> 
>>>>>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
>>>>>>>>>> contains the UTF8-encoded name of the provider."
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> 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-admin@ietf.org  Fri Oct 17 17:11:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24536
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 17:11:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAbsE-0002xp-4k; Fri, 17 Oct 2003 17:11:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAbrJ-0002wO-Ug
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 17:10:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24452
	for <pana@ietf.org>; Fri, 17 Oct 2003 17:09:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAbrH-0001VU-00
	for pana@ietf.org; Fri, 17 Oct 2003 17:10:03 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAbrG-0001VF-00
	for pana@ietf.org; Fri, 17 Oct 2003 17:10:02 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9HL97F1009506;
	Sat, 18 Oct 2003 06:09:07 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9HL979n009947;
	Sat, 18 Oct 2003 06:09:07 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id GAA09945 ; Sat, 18 Oct 2003 06:09:07 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA09512; Sat, 18 Oct 2003 06:09:06 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA16428; Sat, 18 Oct 2003 06:09:06 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9HL96ib008572;
	Sat, 18 Oct 2003 06:09:06 +0900 (JST)
Received: from steelhead ([159.119.168.86]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMX006BR6R4MH@tsbpo1.po.toshiba.co.jp>; Sat,
 18 Oct 2003 06:09:05 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAbpd-0000fl-00; Fri, 17 Oct 2003 14:08:21 -0700
Date: Fri, 17 Oct 2003 14:08:21 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Re: New [issue25] Service Profile names
In-reply-to: <BBB59C9D.AAEB%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Message-id: <20031017210821.GB1853@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031017193300.GA1853@steelhead>
 <BBB59C9D.AAEB%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 17, 2003 at 01:18:21PM -0700, Alper Yegin wrote:
> > in the current design there is only one PANA-Start-Request/Answer exchange
> > even when two EAP authentication rounds are performed in a PANA authentication
> > phase.  How can we specify the two *-info AVPs in separate answer messages?
> 
> You are right, I forgot that... How about including the other *-info in
> PANA-Bind-answer at the end of first EAP authentication (or, in the first
> PANA-auth-answer message following the PANA-binding)?

It can. On the other hand, there would be several other alternatives, too.

What I'm currently thinking is:

- When PaC sends a PANA-Start-Answer message with S-bit set, it can
contain one NAP-info and one ISP-info.

- PAA determines the order of NAP/ISP authentications.  It includes
either one ISP-info or one NAP-info in PANA-Auth-Request of each round
of EAP authentication in the determined order.

- PaC that receives the PANA-Auth-Request understands which
authentication is occuring and use an appopriate identity in each
round of EAP.

- In each round, once PAA receives the first PANA-Auth-Answer, it can
stop including the *-info.

The difference is that, in your scheme PaC determines the order and in 
the above scheme PAA determines the order.

Yoshihiro Ohba


> 
> Alper
> 
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> >> 
> >> Alper
> >> 
> >> 
> >> 
> >> 
> >>> 
> >>> Yoshihiro Ohba
> >>> 
> >>> 
> >>> 
> >>>> 
> >>>>>> 
> >>>>>> In addition, I'm currently assuming that one PAA is associated with a
> >>>>>> single NAP. In this case, including NAP-info in the answer may be
> >>>>>> redundant.
> >>>> 
> >>>> Including a NAP-info in the answer (when separate authentication is going
> >>>> on) means that the supplied authentication info should be used with the
> >>>> NAP.
> >>>> (NAP's AAA).
> >>>> 
> >>>>>> 
> >>>>>>>   - If PaC does not care about separate authentication, it unsets the
> >>>>>>> S-flag
> >>>>>>>     in PANA-start-answer, and this is same as if PAA never set the
> >>>>>>> S-flag.
> >>>>>> 
> >>>>>> OK.
> >>>> 
> >>>> 
> >>>> Alper
> >>>> 
> >>>> 
> >>>>>> 
> >>>>>> Yoshihiro Ohba
> >>>>>> 
> >>>>>>> 
> >>>>>>> Does this make sense?
> >>>>>>> 
> >>>>>>> Alper
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>>  
> >>>>>>> 
> >>>>>>> 
> >>>>>>>  
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
> >>>>>>>>> I was thinking something in terms of this:
> >>>>>>>>> 
> >>>>>>>>> - If only a NAP-info is included in the PANA-start-answer, that means
> >>>>>>>>> the
> >>>>>>>>> following authentication should be directed to particular NAP's AAA.
> >>>>>>>>> - If only a ISP-info is included in the PANA-start-answer, that means
> >>>>>>>>> the
> >>>>>>>>> following authentication should be directed to particular ISP's AAA.
> >>>>>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP
> >>>>>>>>> client
> >>>>>>>>> identifier may suggest. One *-info is included at a time when separate
> >>>>>>>>> authentication will take place.
> >>>>>>>> 
> >>>>>>>> OK.
> >>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> - If both NAP-info and ISP-info are included, that means only one
> >>>>>>>>> authentication will take place. The *-info indicates the chosen
> >>>>>>>>> service
> >>>>>>>>> combination. The authentication request is forwarded to ISP's AAA.
> >>>>>>>> 
> >>>>>>>> It seems natural for this case that separate authentication will take
> >>>>>>>> place with using particular NAP's AAA and ISP's AAA.
> >>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> - If no *-info is included, that means the implicit selection depends
> >>>>>>>>> on
> >>>>>>>>> the
> >>>>>>>>> EAP client identifier.
> >>>>>>>> 
> >>>>>>>> It seems natural for this case that only one authentication will
> >>>>>>>> take place with the authentication request being forwarded to ISP's
> >>>>>>>> AAA.
> >>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
> >>>>>>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
> >>>>>>>>> capability to provide separate auth along with the list of ISPs/NAP.
> >>>>>>>>> PANA-start-answer can signal whether the PaC will do separate auths or
> >>>>>>>>> not.
> >>>>>>>>> A flag in the message header can deliver this capability/choice.
> >>>>>>>> 
> >>>>>>>> Or can we use *-info contained in PANA-start-{request,answer} for that
> >>>>>>>> purpose instead of definig a new flag?
> >>>>>>>> 
> >>>>>>>> Yoshihiro Ohba
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> Comments?
> >>>>>>>>> 
> >>>>>>>>> Alper
> >>>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>>> Here is the new text which reflects Alper's comments.
> >>>>>>>>>> 
> >>>>>>>>>> Yoshihiro Ohba
> >>>>>>>>>> 
> >>>>>>>>>> ---
> >>>>>>>>>> In Section 4.2, change
> >>>>>>>>>> 
> >>>>>>>>>> From:
> >>>>>>>>>> 
> >>>>>>>>>> "  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>>>>>  message. The PANA-Start-Answer message contains the initial sequence
> >>>>>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
> >>>>>>>>>>  the received Cookie as the PANA payload."
> >>>>>>>>>> 
> >>>>>>>>>> To:
> >>>>>>>>>> 
> >>>>>>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
> >>>>>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
> >>>>>>>>>>  information on the NAP and/or ISPs.
> >>>>>>>>>> 
> >>>>>>>>>>  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>>>>>  message if it wishes to enter the authentication phase.  The
> >>>>>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
> >>>>>>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
> >>>>>>>>>>  Cookie (if any) as the PANA payload.  If the received
> >>>>>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
> >>>>>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
> >>>>>>>>>>  received NAP-Information AVP and, if any, one of the received
> >>>>>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
> >>>>>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
> >>>>>>>>>>  If the PaC does not contain a NAP-Information AVP or an
> >>>>>>>>>>  ISP-Information AVP, the EAP peer identity or some default
> >>>>>>>>>>  information MAY be used to identify the binding."
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> In Section 9.3.3, change
> >>>>>>>>>> 
> >>>>>>>>>> from:
> >>>>>>>>>> 
> >>>>>>>>>> "
> >>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>>>>>                   [ Cookie ]
> >>>>>>>>>>                 * [ AVP ]
> >>>>>>>>>> "
> >>>>>>>>>> 
> >>>>>>>>>> to:
> >>>>>>>>>> 
> >>>>>>>>>> "
> >>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>>>>>                   [ Cookie ]
> >>>>>>>>>>    [ NAP-Information ]
> >>>>>>>>>>                 * [ ISP-Information ]
> >>>>>>>>>>                 * [ AVP ]
> >>>>>>>>>> "
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> In Section 9.3.4, change
> >>>>>>>>>> 
> >>>>>>>>>> from:
> >>>>>>>>>> 
> >>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>>>>>                   [ Cookie ]
> >>>>>>>>>>                 * [ AVP ]"
> >>>>>>>>>> 
> >>>>>>>>>> to:
> >>>>>>>>>> 
> >>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>>>>>                   [ Cookie ]
> >>>>>>>>>>    [ NAP-Information ]
> >>>>>>>>>>                   [ ISP-Information ]
> >>>>>>>>>>                 * [ AVP ]"
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> Add the following sections:
> >>>>>>>>>> 
> >>>>>>>>>> "9.4.9 NAP-Information AVP
> >>>>>>>>>> 
> >>>>>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
> >>>>>>>>>> contains one globally unique identifier of the NAP in a
> >>>>>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
> >>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>>>>>> 
> >>>>>>>>>>     NAP-Information ::= < AVP Header: 1029 >
> >>>>>>>>>>                          { Provider-Identifier }
> >>>>>>>>>>                          { Provider-Name }
> >>>>>>>>>>                        * [ AVP ]
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> 9.4.10 ISP-Information AVP
> >>>>>>>>>> 
> >>>>>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
> >>>>>>>>>> contains one globally unique identifier of the ISP in a
> >>>>>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
> >>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>>>>>> 
> >>>>>>>>>>     ISP-Information ::= < AVP Header: 1030 >
> >>>>>>>>>>                          { Provider-Identifier }
> >>>>>>>>>>                          { Provider-Name }
> >>>>>>>>>>                        * [ AVP ]
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> 9.4.11 Provider-Identifier AVP
> >>>>>>>>>> 
> >>>>>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
> >>>>>>>>>> and contains an IANA assigned "SMI Network Management Private
> >>>>>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> 9.4.12 Provider-Name AVP
> >>>>>>>>>> 
> >>>>>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
> >>>>>>>>>> contains the UTF8-encoded name of the provider."
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>> 
> >>>>> 
> >>>> 
> >>> 
> >>> _______________________________________________
> >>> 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 exim@www1.ietf.org  Fri Oct 17 17:11:56 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24716
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 17:11:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAbsl-00031W-IA
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 17:11:36 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HLBZ3X011616
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 17:11:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAbsl-00031H-7o
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 17:11:35 -0400
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24535
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 17:11:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAbsE-0002xp-4k; Fri, 17 Oct 2003 17:11:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAbrJ-0002wO-Ug
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 17:10:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24452
	for <pana@ietf.org>; Fri, 17 Oct 2003 17:09:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAbrH-0001VU-00
	for pana@ietf.org; Fri, 17 Oct 2003 17:10:03 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAbrG-0001VF-00
	for pana@ietf.org; Fri, 17 Oct 2003 17:10:02 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9HL97F1009506;
	Sat, 18 Oct 2003 06:09:07 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9HL979n009947;
	Sat, 18 Oct 2003 06:09:07 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id GAA09945 ; Sat, 18 Oct 2003 06:09:07 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id GAA09512; Sat, 18 Oct 2003 06:09:06 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id GAA16428; Sat, 18 Oct 2003 06:09:06 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9HL96ib008572;
	Sat, 18 Oct 2003 06:09:06 +0900 (JST)
Received: from steelhead ([159.119.168.86]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HMX006BR6R4MH@tsbpo1.po.toshiba.co.jp>; Sat,
 18 Oct 2003 06:09:05 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AAbpd-0000fl-00; Fri, 17 Oct 2003 14:08:21 -0700
Date: Fri, 17 Oct 2003 14:08:21 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Re: New [issue25] Service Profile names
In-reply-to: <BBB59C9D.AAEB%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Message-id: <20031017210821.GB1853@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, Dan.Forsberg@nokia.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031017193300.GA1853@steelhead>
 <BBB59C9D.AAEB%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Fri, Oct 17, 2003 at 01:18:21PM -0700, Alper Yegin wrote:
> > in the current design there is only one PANA-Start-Request/Answer exchange
> > even when two EAP authentication rounds are performed in a PANA authentication
> > phase.  How can we specify the two *-info AVPs in separate answer messages?
> 
> You are right, I forgot that... How about including the other *-info in
> PANA-Bind-answer at the end of first EAP authentication (or, in the first
> PANA-auth-answer message following the PANA-binding)?

It can. On the other hand, there would be several other alternatives, too.

What I'm currently thinking is:

- When PaC sends a PANA-Start-Answer message with S-bit set, it can
contain one NAP-info and one ISP-info.

- PAA determines the order of NAP/ISP authentications.  It includes
either one ISP-info or one NAP-info in PANA-Auth-Request of each round
of EAP authentication in the determined order.

- PaC that receives the PANA-Auth-Request understands which
authentication is occuring and use an appopriate identity in each
round of EAP.

- In each round, once PAA receives the first PANA-Auth-Answer, it can
stop including the *-info.

The difference is that, in your scheme PaC determines the order and in 
the above scheme PAA determines the order.

Yoshihiro Ohba


> 
> Alper
> 
> 
> 
> 
> > 
> > Yoshihiro Ohba
> > 
> >> 
> >> Alper
> >> 
> >> 
> >> 
> >> 
> >>> 
> >>> Yoshihiro Ohba
> >>> 
> >>> 
> >>> 
> >>>> 
> >>>>>> 
> >>>>>> In addition, I'm currently assuming that one PAA is associated with a
> >>>>>> single NAP. In this case, including NAP-info in the answer may be
> >>>>>> redundant.
> >>>> 
> >>>> Including a NAP-info in the answer (when separate authentication is going
> >>>> on) means that the supplied authentication info should be used with the
> >>>> NAP.
> >>>> (NAP's AAA).
> >>>> 
> >>>>>> 
> >>>>>>>   - If PaC does not care about separate authentication, it unsets the
> >>>>>>> S-flag
> >>>>>>>     in PANA-start-answer, and this is same as if PAA never set the
> >>>>>>> S-flag.
> >>>>>> 
> >>>>>> OK.
> >>>> 
> >>>> 
> >>>> Alper
> >>>> 
> >>>> 
> >>>>>> 
> >>>>>> Yoshihiro Ohba
> >>>>>> 
> >>>>>>> 
> >>>>>>> Does this make sense?
> >>>>>>> 
> >>>>>>> Alper
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>>  
> >>>>>>> 
> >>>>>>> 
> >>>>>>>  
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>> 
> >>>>>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
> >>>>>>>>> I was thinking something in terms of this:
> >>>>>>>>> 
> >>>>>>>>> - If only a NAP-info is included in the PANA-start-answer, that means
> >>>>>>>>> the
> >>>>>>>>> following authentication should be directed to particular NAP's AAA.
> >>>>>>>>> - If only a ISP-info is included in the PANA-start-answer, that means
> >>>>>>>>> the
> >>>>>>>>> following authentication should be directed to particular ISP's AAA.
> >>>>>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP
> >>>>>>>>> client
> >>>>>>>>> identifier may suggest. One *-info is included at a time when separate
> >>>>>>>>> authentication will take place.
> >>>>>>>> 
> >>>>>>>> OK.
> >>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> - If both NAP-info and ISP-info are included, that means only one
> >>>>>>>>> authentication will take place. The *-info indicates the chosen
> >>>>>>>>> service
> >>>>>>>>> combination. The authentication request is forwarded to ISP's AAA.
> >>>>>>>> 
> >>>>>>>> It seems natural for this case that separate authentication will take
> >>>>>>>> place with using particular NAP's AAA and ISP's AAA.
> >>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> - If no *-info is included, that means the implicit selection depends
> >>>>>>>>> on
> >>>>>>>>> the
> >>>>>>>>> EAP client identifier.
> >>>>>>>> 
> >>>>>>>> It seems natural for this case that only one authentication will
> >>>>>>>> take place with the authentication request being forwarded to ISP's
> >>>>>>>> AAA.
> >>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> We might also modify the f-flag logic. Maybe we can fold that logic to
> >>>>>>>>> PANA-start-request/answer exchange. PANA-start-request can signal the
> >>>>>>>>> capability to provide separate auth along with the list of ISPs/NAP.
> >>>>>>>>> PANA-start-answer can signal whether the PaC will do separate auths or
> >>>>>>>>> not.
> >>>>>>>>> A flag in the message header can deliver this capability/choice.
> >>>>>>>> 
> >>>>>>>> Or can we use *-info contained in PANA-start-{request,answer} for that
> >>>>>>>> purpose instead of definig a new flag?
> >>>>>>>> 
> >>>>>>>> Yoshihiro Ohba
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> Comments?
> >>>>>>>>> 
> >>>>>>>>> Alper
> >>>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> 
> >>>>>>>>>> Here is the new text which reflects Alper's comments.
> >>>>>>>>>> 
> >>>>>>>>>> Yoshihiro Ohba
> >>>>>>>>>> 
> >>>>>>>>>> ---
> >>>>>>>>>> In Section 4.2, change
> >>>>>>>>>> 
> >>>>>>>>>> From:
> >>>>>>>>>> 
> >>>>>>>>>> "  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>>>>>  message. The PANA-Start-Answer message contains the initial sequence
> >>>>>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
> >>>>>>>>>>  the received Cookie as the PANA payload."
> >>>>>>>>>> 
> >>>>>>>>>> To:
> >>>>>>>>>> 
> >>>>>>>>>> "  A PANA-Start-Request can also contain zero or one NAP-Information
> >>>>>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
> >>>>>>>>>>  information on the NAP and/or ISPs.
> >>>>>>>>>> 
> >>>>>>>>>>  When a PaC receives the PANA-Start-Request message in response to
> >>>>>>>>>>  the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
> >>>>>>>>>>  message if it wishes to enter the authentication phase.  The
> >>>>>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
> >>>>>>>>>>  the tseq and rseq fields of the PANA header, a copy of the received
> >>>>>>>>>>  Cookie (if any) as the PANA payload.  If the received
> >>>>>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
> >>>>>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
> >>>>>>>>>>  received NAP-Information AVP and, if any, one of the received
> >>>>>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to identify
> >>>>>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
> >>>>>>>>>>  If the PaC does not contain a NAP-Information AVP or an
> >>>>>>>>>>  ISP-Information AVP, the EAP peer identity or some default
> >>>>>>>>>>  information MAY be used to identify the binding."
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> In Section 9.3.3, change
> >>>>>>>>>> 
> >>>>>>>>>> from:
> >>>>>>>>>> 
> >>>>>>>>>> "
> >>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>>>>>                   [ Cookie ]
> >>>>>>>>>>                 * [ AVP ]
> >>>>>>>>>> "
> >>>>>>>>>> 
> >>>>>>>>>> to:
> >>>>>>>>>> 
> >>>>>>>>>> "
> >>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
> >>>>>>>>>>                   [ Cookie ]
> >>>>>>>>>>    [ NAP-Information ]
> >>>>>>>>>>                 * [ ISP-Information ]
> >>>>>>>>>>                 * [ AVP ]
> >>>>>>>>>> "
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> In Section 9.3.4, change
> >>>>>>>>>> 
> >>>>>>>>>> from:
> >>>>>>>>>> 
> >>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>>>>>                   [ Cookie ]
> >>>>>>>>>>                 * [ AVP ]"
> >>>>>>>>>> 
> >>>>>>>>>> to:
> >>>>>>>>>> 
> >>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
> >>>>>>>>>>                   [ Cookie ]
> >>>>>>>>>>    [ NAP-Information ]
> >>>>>>>>>>                   [ ISP-Information ]
> >>>>>>>>>>                 * [ AVP ]"
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> Add the following sections:
> >>>>>>>>>> 
> >>>>>>>>>> "9.4.9 NAP-Information AVP
> >>>>>>>>>> 
> >>>>>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
> >>>>>>>>>> contains one globally unique identifier of the NAP in a
> >>>>>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
> >>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>>>>>> 
> >>>>>>>>>>     NAP-Information ::= < AVP Header: 1029 >
> >>>>>>>>>>                          { Provider-Identifier }
> >>>>>>>>>>                          { Provider-Name }
> >>>>>>>>>>                        * [ AVP ]
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> 9.4.10 ISP-Information AVP
> >>>>>>>>>> 
> >>>>>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
> >>>>>>>>>> contains one globally unique identifier of the ISP in a
> >>>>>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
> >>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
> >>>>>>>>>> 
> >>>>>>>>>>     ISP-Information ::= < AVP Header: 1030 >
> >>>>>>>>>>                          { Provider-Identifier }
> >>>>>>>>>>                          { Provider-Name }
> >>>>>>>>>>                        * [ AVP ]
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> 9.4.11 Provider-Identifier AVP
> >>>>>>>>>> 
> >>>>>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
> >>>>>>>>>> and contains an IANA assigned "SMI Network Management Private
> >>>>>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> 9.4.12 Provider-Name AVP
> >>>>>>>>>> 
> >>>>>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
> >>>>>>>>>> contains the UTF8-encoded name of the provider."
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>>> 
> >>>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>> 
> >>>>> 
> >>>> 
> >>> 
> >>> _______________________________________________
> >>> 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-admin@ietf.org  Fri Oct 17 21:13:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02448
	for <pana-archive@lists.ietf.org>; Fri, 17 Oct 2003 21:13:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAfeP-0005G0-CF; Fri, 17 Oct 2003 21:13:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAfdh-0005F5-OQ
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 21:12:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02430
	for <pana@ietf.org>; Fri, 17 Oct 2003 21:12:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAfdf-0003tt-00
	for pana@ietf.org; Fri, 17 Oct 2003 21:12:15 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAfde-0003tq-00
	for pana@ietf.org; Fri, 17 Oct 2003 21:12:14 -0400
Date: Fri, 17 Oct 2003 18:12:08 -0700
Subject: Re: [Pana] Re: New [issue25] Service Profile names
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBB5E178.AB2B%alper@docomolabs-usa.com>
In-Reply-To: <20031017210821.GB1853@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Letting the PAA control the order may be preferred, I guess.

Alper

> On Fri, Oct 17, 2003 at 01:18:21PM -0700, Alper Yegin wrote:
>>> in the current design there is only one PANA-Start-Request/Answer exchange
>>> even when two EAP authentication rounds are performed in a PANA
>>> authentication
>>> phase.  How can we specify the two *-info AVPs in separate answer messages?
>> 
>> You are right, I forgot that... How about including the other *-info in
>> PANA-Bind-answer at the end of first EAP authentication (or, in the first
>> PANA-auth-answer message following the PANA-binding)?
> 
> It can. On the other hand, there would be several other alternatives, too.
> 
> What I'm currently thinking is:
> 
> - When PaC sends a PANA-Start-Answer message with S-bit set, it can
> contain one NAP-info and one ISP-info.
> 
> - PAA determines the order of NAP/ISP authentications.  It includes
> either one ISP-info or one NAP-info in PANA-Auth-Request of each round
> of EAP authentication in the determined order.
> 
> - PaC that receives the PANA-Auth-Request understands which
> authentication is occuring and use an appopriate identity in each
> round of EAP.
> 
> - In each round, once PAA receives the first PANA-Auth-Answer, it can
> stop including the *-info.
> 
> The difference is that, in your scheme PaC determines the order and in
> the above scheme PAA determines the order.
> 
> Yoshihiro Ohba
> 
> 
>> 
>> Alper
>> 
>> 
>> 
>> 
>>> 
>>> Yoshihiro Ohba
>>> 
>>>> 
>>>> Alper
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>> Yoshihiro Ohba
>>>>> 
>>>>> 
>>>>> 
>>>>>> 
>>>>>>>> 
>>>>>>>> In addition, I'm currently assuming that one PAA is associated with a
>>>>>>>> single NAP. In this case, including NAP-info in the answer may be
>>>>>>>> redundant.
>>>>>> 
>>>>>> Including a NAP-info in the answer (when separate authentication is going
>>>>>> on) means that the supplied authentication info should be used with the
>>>>>> NAP.
>>>>>> (NAP's AAA).
>>>>>> 
>>>>>>>> 
>>>>>>>>>   - If PaC does not care about separate authentication, it unsets the
>>>>>>>>> S-flag
>>>>>>>>>     in PANA-start-answer, and this is same as if PAA never set the
>>>>>>>>> S-flag.
>>>>>>>> 
>>>>>>>> OK.
>>>>>> 
>>>>>> 
>>>>>> Alper
>>>>>> 
>>>>>> 
>>>>>>>> 
>>>>>>>> Yoshihiro Ohba
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Does this make sense?
>>>>>>>>> 
>>>>>>>>> Alper
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>  
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>  
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
>>>>>>>>>>> I was thinking something in terms of this:
>>>>>>>>>>> 
>>>>>>>>>>> - If only a NAP-info is included in the PANA-start-answer, that
>>>>>>>>>>> means
>>>>>>>>>>> the
>>>>>>>>>>> following authentication should be directed to particular NAP's AAA.
>>>>>>>>>>> - If only a ISP-info is included in the PANA-start-answer, that
>>>>>>>>>>> means
>>>>>>>>>>> the
>>>>>>>>>>> following authentication should be directed to particular ISP's AAA.
>>>>>>>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP
>>>>>>>>>>> client
>>>>>>>>>>> identifier may suggest. One *-info is included at a time when
>>>>>>>>>>> separate
>>>>>>>>>>> authentication will take place.
>>>>>>>>>> 
>>>>>>>>>> OK.
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> - If both NAP-info and ISP-info are included, that means only one
>>>>>>>>>>> authentication will take place. The *-info indicates the chosen
>>>>>>>>>>> service
>>>>>>>>>>> combination. The authentication request is forwarded to ISP's AAA.
>>>>>>>>>> 
>>>>>>>>>> It seems natural for this case that separate authentication will take
>>>>>>>>>> place with using particular NAP's AAA and ISP's AAA.
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> - If no *-info is included, that means the implicit selection
>>>>>>>>>>> depends
>>>>>>>>>>> on
>>>>>>>>>>> the
>>>>>>>>>>> EAP client identifier.
>>>>>>>>>> 
>>>>>>>>>> It seems natural for this case that only one authentication will
>>>>>>>>>> take place with the authentication request being forwarded to ISP's
>>>>>>>>>> AAA.
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> We might also modify the f-flag logic. Maybe we can fold that logic
>>>>>>>>>>> to
>>>>>>>>>>> PANA-start-request/answer exchange. PANA-start-request can signal
>>>>>>>>>>> the
>>>>>>>>>>> capability to provide separate auth along with the list of ISPs/NAP.
>>>>>>>>>>> PANA-start-answer can signal whether the PaC will do separate auths
>>>>>>>>>>> or
>>>>>>>>>>> not.
>>>>>>>>>>> A flag in the message header can deliver this capability/choice.
>>>>>>>>>> 
>>>>>>>>>> Or can we use *-info contained in PANA-start-{request,answer} for
>>>>>>>>>> that
>>>>>>>>>> purpose instead of definig a new flag?
>>>>>>>>>> 
>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> Comments?
>>>>>>>>>>> 
>>>>>>>>>>> Alper
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> Here is the new text which reflects Alper's comments.
>>>>>>>>>>>> 
>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>> 
>>>>>>>>>>>> ---
>>>>>>>>>>>> In Section 4.2, change
>>>>>>>>>>>> 
>>>>>>>>>>>> From:
>>>>>>>>>>>> 
>>>>>>>>>>>> "  When a PaC receives the PANA-Start-Request message in response
>>>>>>>>>>>> to
>>>>>>>>>>>>  the PANA-PAA-Discover message, it responds with a
>>>>>>>>>>>> PANA-Start-Answer
>>>>>>>>>>>>  message. The PANA-Start-Answer message contains the initial
>>>>>>>>>>>> sequence
>>>>>>>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
>>>>>>>>>>>>  the received Cookie as the PANA payload."
>>>>>>>>>>>> 
>>>>>>>>>>>> To:
>>>>>>>>>>>> 
>>>>>>>>>>>> "  A PANA-Start-Request can also contain zero or one
>>>>>>>>>>>> NAP-Information
>>>>>>>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
>>>>>>>>>>>>  information on the NAP and/or ISPs.
>>>>>>>>>>>> 
>>>>>>>>>>>>  When a PaC receives the PANA-Start-Request message in response to
>>>>>>>>>>>>  the PANA-PAA-Discover message, it responds with a
>>>>>>>>>>>> PANA-Start-Answer
>>>>>>>>>>>>  message if it wishes to enter the authentication phase.  The
>>>>>>>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
>>>>>>>>>>>>  the tseq and rseq fields of the PANA header, a copy of the
>>>>>>>>>>>> received
>>>>>>>>>>>>  Cookie (if any) as the PANA payload.  If the received
>>>>>>>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
>>>>>>>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
>>>>>>>>>>>>  received NAP-Information AVP and, if any, one of the received
>>>>>>>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to
>>>>>>>>>>>> identify
>>>>>>>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
>>>>>>>>>>>>  If the PaC does not contain a NAP-Information AVP or an
>>>>>>>>>>>>  ISP-Information AVP, the EAP peer identity or some default
>>>>>>>>>>>>  information MAY be used to identify the binding."
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> In Section 9.3.3, change
>>>>>>>>>>>> 
>>>>>>>>>>>> from:
>>>>>>>>>>>> 
>>>>>>>>>>>> "
>>>>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>>>                 * [ AVP ]
>>>>>>>>>>>> "
>>>>>>>>>>>> 
>>>>>>>>>>>> to:
>>>>>>>>>>>> 
>>>>>>>>>>>> "
>>>>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>>>    [ NAP-Information ]
>>>>>>>>>>>>                 * [ ISP-Information ]
>>>>>>>>>>>>                 * [ AVP ]
>>>>>>>>>>>> "
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> In Section 9.3.4, change
>>>>>>>>>>>> 
>>>>>>>>>>>> from:
>>>>>>>>>>>> 
>>>>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>>>                 * [ AVP ]"
>>>>>>>>>>>> 
>>>>>>>>>>>> to:
>>>>>>>>>>>> 
>>>>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>>>    [ NAP-Information ]
>>>>>>>>>>>>                   [ ISP-Information ]
>>>>>>>>>>>>                 * [ AVP ]"
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> Add the following sections:
>>>>>>>>>>>> 
>>>>>>>>>>>> "9.4.9 NAP-Information AVP
>>>>>>>>>>>> 
>>>>>>>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
>>>>>>>>>>>> contains one globally unique identifier of the NAP in a
>>>>>>>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
>>>>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>>>>>> 
>>>>>>>>>>>>     NAP-Information ::= < AVP Header: 1029 >
>>>>>>>>>>>>                          { Provider-Identifier }
>>>>>>>>>>>>                          { Provider-Name }
>>>>>>>>>>>>                        * [ AVP ]
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 9.4.10 ISP-Information AVP
>>>>>>>>>>>> 
>>>>>>>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
>>>>>>>>>>>> contains one globally unique identifier of the ISP in a
>>>>>>>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
>>>>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>>>>>> 
>>>>>>>>>>>>     ISP-Information ::= < AVP Header: 1030 >
>>>>>>>>>>>>                          { Provider-Identifier }
>>>>>>>>>>>>                          { Provider-Name }
>>>>>>>>>>>>                        * [ AVP ]
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 9.4.11 Provider-Identifier AVP
>>>>>>>>>>>> 
>>>>>>>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
>>>>>>>>>>>> and contains an IANA assigned "SMI Network Management Private
>>>>>>>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 9.4.12 Provider-Name AVP
>>>>>>>>>>>> 
>>>>>>>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
>>>>>>>>>>>> contains the UTF8-encoded name of the provider."
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> 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 exim@www1.ietf.org  Fri Oct 17 21:13:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02463
	for <pana-archive@odin.ietf.org>; Fri, 17 Oct 2003 21:13:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAfeS-0005Gd-OP
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 21:13:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9I1D4VS020243
	for pana-archive@odin.ietf.org; Fri, 17 Oct 2003 21:13:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAfeS-0005GQ-Hs
	for pana-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 21:13:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02445
	for <pana-web-archive@ietf.org>; Fri, 17 Oct 2003 21:12:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAfeP-0003uN-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 21:13:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAfeP-0003uK-00
	for pana-web-archive@ietf.org; Fri, 17 Oct 2003 21:13:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAfeP-0005G0-CF; Fri, 17 Oct 2003 21:13:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AAfdh-0005F5-OQ
	for pana@optimus.ietf.org; Fri, 17 Oct 2003 21:12:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02430
	for <pana@ietf.org>; Fri, 17 Oct 2003 21:12:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAfdf-0003tt-00
	for pana@ietf.org; Fri, 17 Oct 2003 21:12:15 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AAfde-0003tq-00
	for pana@ietf.org; Fri, 17 Oct 2003 21:12:14 -0400
Date: Fri, 17 Oct 2003 18:12:08 -0700
Subject: Re: [Pana] Re: New [issue25] Service Profile names
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBB5E178.AB2B%alper@docomolabs-usa.com>
In-Reply-To: <20031017210821.GB1853@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Letting the PAA control the order may be preferred, I guess.

Alper

> On Fri, Oct 17, 2003 at 01:18:21PM -0700, Alper Yegin wrote:
>>> in the current design there is only one PANA-Start-Request/Answer exchange
>>> even when two EAP authentication rounds are performed in a PANA
>>> authentication
>>> phase.  How can we specify the two *-info AVPs in separate answer messages?
>> 
>> You are right, I forgot that... How about including the other *-info in
>> PANA-Bind-answer at the end of first EAP authentication (or, in the first
>> PANA-auth-answer message following the PANA-binding)?
> 
> It can. On the other hand, there would be several other alternatives, too.
> 
> What I'm currently thinking is:
> 
> - When PaC sends a PANA-Start-Answer message with S-bit set, it can
> contain one NAP-info and one ISP-info.
> 
> - PAA determines the order of NAP/ISP authentications.  It includes
> either one ISP-info or one NAP-info in PANA-Auth-Request of each round
> of EAP authentication in the determined order.
> 
> - PaC that receives the PANA-Auth-Request understands which
> authentication is occuring and use an appopriate identity in each
> round of EAP.
> 
> - In each round, once PAA receives the first PANA-Auth-Answer, it can
> stop including the *-info.
> 
> The difference is that, in your scheme PaC determines the order and in
> the above scheme PAA determines the order.
> 
> Yoshihiro Ohba
> 
> 
>> 
>> Alper
>> 
>> 
>> 
>> 
>>> 
>>> Yoshihiro Ohba
>>> 
>>>> 
>>>> Alper
>>>> 
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>> Yoshihiro Ohba
>>>>> 
>>>>> 
>>>>> 
>>>>>> 
>>>>>>>> 
>>>>>>>> In addition, I'm currently assuming that one PAA is associated with a
>>>>>>>> single NAP. In this case, including NAP-info in the answer may be
>>>>>>>> redundant.
>>>>>> 
>>>>>> Including a NAP-info in the answer (when separate authentication is going
>>>>>> on) means that the supplied authentication info should be used with the
>>>>>> NAP.
>>>>>> (NAP's AAA).
>>>>>> 
>>>>>>>> 
>>>>>>>>>   - If PaC does not care about separate authentication, it unsets the
>>>>>>>>> S-flag
>>>>>>>>>     in PANA-start-answer, and this is same as if PAA never set the
>>>>>>>>> S-flag.
>>>>>>>> 
>>>>>>>> OK.
>>>>>> 
>>>>>> 
>>>>>> Alper
>>>>>> 
>>>>>> 
>>>>>>>> 
>>>>>>>> Yoshihiro Ohba
>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Does this make sense?
>>>>>>>>> 
>>>>>>>>> Alper
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>  
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>  
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On Tue, Oct 14, 2003 at 01:27:28PM -0700, Alper Yegin wrote:
>>>>>>>>>>> I was thinking something in terms of this:
>>>>>>>>>>> 
>>>>>>>>>>> - If only a NAP-info is included in the PANA-start-answer, that
>>>>>>>>>>> means
>>>>>>>>>>> the
>>>>>>>>>>> following authentication should be directed to particular NAP's AAA.
>>>>>>>>>>> - If only a ISP-info is included in the PANA-start-answer, that
>>>>>>>>>>> means
>>>>>>>>>>> the
>>>>>>>>>>> following authentication should be directed to particular ISP's AAA.
>>>>>>>>>>> ** in these cases, the NAP and ISP info overwrites whatever the EAP
>>>>>>>>>>> client
>>>>>>>>>>> identifier may suggest. One *-info is included at a time when
>>>>>>>>>>> separate
>>>>>>>>>>> authentication will take place.
>>>>>>>>>> 
>>>>>>>>>> OK.
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> - If both NAP-info and ISP-info are included, that means only one
>>>>>>>>>>> authentication will take place. The *-info indicates the chosen
>>>>>>>>>>> service
>>>>>>>>>>> combination. The authentication request is forwarded to ISP's AAA.
>>>>>>>>>> 
>>>>>>>>>> It seems natural for this case that separate authentication will take
>>>>>>>>>> place with using particular NAP's AAA and ISP's AAA.
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> - If no *-info is included, that means the implicit selection
>>>>>>>>>>> depends
>>>>>>>>>>> on
>>>>>>>>>>> the
>>>>>>>>>>> EAP client identifier.
>>>>>>>>>> 
>>>>>>>>>> It seems natural for this case that only one authentication will
>>>>>>>>>> take place with the authentication request being forwarded to ISP's
>>>>>>>>>> AAA.
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> We might also modify the f-flag logic. Maybe we can fold that logic
>>>>>>>>>>> to
>>>>>>>>>>> PANA-start-request/answer exchange. PANA-start-request can signal
>>>>>>>>>>> the
>>>>>>>>>>> capability to provide separate auth along with the list of ISPs/NAP.
>>>>>>>>>>> PANA-start-answer can signal whether the PaC will do separate auths
>>>>>>>>>>> or
>>>>>>>>>>> not.
>>>>>>>>>>> A flag in the message header can deliver this capability/choice.
>>>>>>>>>> 
>>>>>>>>>> Or can we use *-info contained in PANA-start-{request,answer} for
>>>>>>>>>> that
>>>>>>>>>> purpose instead of definig a new flag?
>>>>>>>>>> 
>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> Comments?
>>>>>>>>>>> 
>>>>>>>>>>> Alper
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> Here is the new text which reflects Alper's comments.
>>>>>>>>>>>> 
>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>> 
>>>>>>>>>>>> ---
>>>>>>>>>>>> In Section 4.2, change
>>>>>>>>>>>> 
>>>>>>>>>>>> From:
>>>>>>>>>>>> 
>>>>>>>>>>>> "  When a PaC receives the PANA-Start-Request message in response
>>>>>>>>>>>> to
>>>>>>>>>>>>  the PANA-PAA-Discover message, it responds with a
>>>>>>>>>>>> PANA-Start-Answer
>>>>>>>>>>>>  message. The PANA-Start-Answer message contains the initial
>>>>>>>>>>>> sequence
>>>>>>>>>>>>  numbers in the tseq and rseq fields of the PANA header, a copy of
>>>>>>>>>>>>  the received Cookie as the PANA payload."
>>>>>>>>>>>> 
>>>>>>>>>>>> To:
>>>>>>>>>>>> 
>>>>>>>>>>>> "  A PANA-Start-Request can also contain zero or one
>>>>>>>>>>>> NAP-Information
>>>>>>>>>>>>  AVP and zero or more ISP-Information AVPs to advertise the
>>>>>>>>>>>>  information on the NAP and/or ISPs.
>>>>>>>>>>>> 
>>>>>>>>>>>>  When a PaC receives the PANA-Start-Request message in response to
>>>>>>>>>>>>  the PANA-PAA-Discover message, it responds with a
>>>>>>>>>>>> PANA-Start-Answer
>>>>>>>>>>>>  message if it wishes to enter the authentication phase.  The
>>>>>>>>>>>>  PANA-Start-Answer message contains the initial sequence numbers in
>>>>>>>>>>>>  the tseq and rseq fields of the PANA header, a copy of the
>>>>>>>>>>>> received
>>>>>>>>>>>>  Cookie (if any) as the PANA payload.  If the received
>>>>>>>>>>>>  PANA-Start-Request message contains a NAP-Information AVP and zero
>>>>>>>>>>>>  or more ISP-Information AVP, the PaC MAY additinally contain the
>>>>>>>>>>>>  received NAP-Information AVP and, if any, one of the received
>>>>>>>>>>>>  ISP-Information AVP(s) in the PANA-Start-Answer message to
>>>>>>>>>>>> identify
>>>>>>>>>>>>  the binding between the subsequent authentication and the NAP/ISP.
>>>>>>>>>>>>  If the PaC does not contain a NAP-Information AVP or an
>>>>>>>>>>>>  ISP-Information AVP, the EAP peer identity or some default
>>>>>>>>>>>>  information MAY be used to identify the binding."
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> In Section 9.3.3, change
>>>>>>>>>>>> 
>>>>>>>>>>>> from:
>>>>>>>>>>>> 
>>>>>>>>>>>> "
>>>>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>>>                 * [ AVP ]
>>>>>>>>>>>> "
>>>>>>>>>>>> 
>>>>>>>>>>>> to:
>>>>>>>>>>>> 
>>>>>>>>>>>> "
>>>>>>>>>>>>     PANA-Start-Request ::= < PANA-Header: 2, REQ >
>>>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>>>    [ NAP-Information ]
>>>>>>>>>>>>                 * [ ISP-Information ]
>>>>>>>>>>>>                 * [ AVP ]
>>>>>>>>>>>> "
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> In Section 9.3.4, change
>>>>>>>>>>>> 
>>>>>>>>>>>> from:
>>>>>>>>>>>> 
>>>>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>>>                 * [ AVP ]"
>>>>>>>>>>>> 
>>>>>>>>>>>> to:
>>>>>>>>>>>> 
>>>>>>>>>>>> "     PANA-Start-Answer ::= < PANA-Header: 3 >
>>>>>>>>>>>>                   [ Cookie ]
>>>>>>>>>>>>    [ NAP-Information ]
>>>>>>>>>>>>                   [ ISP-Information ]
>>>>>>>>>>>>                 * [ AVP ]"
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> Add the following sections:
>>>>>>>>>>>> 
>>>>>>>>>>>> "9.4.9 NAP-Information AVP
>>>>>>>>>>>> 
>>>>>>>>>>>> The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
>>>>>>>>>>>> contains one globally unique identifier of the NAP in a
>>>>>>>>>>>> Provider-Identifier AVP and one enterprise name of the NAP in a
>>>>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>>>>>> 
>>>>>>>>>>>>     NAP-Information ::= < AVP Header: 1029 >
>>>>>>>>>>>>                          { Provider-Identifier }
>>>>>>>>>>>>                          { Provider-Name }
>>>>>>>>>>>>                        * [ AVP ]
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 9.4.10 ISP-Information AVP
>>>>>>>>>>>> 
>>>>>>>>>>>> The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
>>>>>>>>>>>> contains one globally unique identifier of the ISP in a
>>>>>>>>>>>> Provider-Identifier AVP and one enterprise name of the ISP in a
>>>>>>>>>>>> Provider-Name AVP.  Its Data field has the following ABNF grammar:
>>>>>>>>>>>> 
>>>>>>>>>>>>     ISP-Information ::= < AVP Header: 1030 >
>>>>>>>>>>>>                          { Provider-Identifier }
>>>>>>>>>>>>                          { Provider-Name }
>>>>>>>>>>>>                        * [ AVP ]
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 9.4.11 Provider-Identifier AVP
>>>>>>>>>>>> 
>>>>>>>>>>>> The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
>>>>>>>>>>>> and contains an IANA assigned "SMI Network Management Private
>>>>>>>>>>>> Enterprise Codes" [IANAWEB] value, encoded in network byte order.
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 9.4.12 Provider-Name AVP
>>>>>>>>>>>> 
>>>>>>>>>>>> The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
>>>>>>>>>>>> contains the UTF8-encoded name of the provider."
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> 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-admin@ietf.org  Tue Oct 21 09:38:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17066
	for <pana-archive@lists.ietf.org>; Tue, 21 Oct 2003 09:38:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwi3-0004jQ-1z; Tue, 21 Oct 2003 09:38:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwhv-0004eo-Hy
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 09:37:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17041
	for <pana@ietf.org>; Tue, 21 Oct 2003 09:37:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwht-0003Rx-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:37:53 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwhs-0003Rm-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:37:52 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9LDbiF1026389
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:37:45 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9LDbjgi022199
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:37:45 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA22198 ; Tue, 21 Oct 2003 22:37:44 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA16208; Tue, 21 Oct 2003 22:37:44 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA10939; Tue, 21 Oct 2003 22:37:44 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9LDbhqv012209
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:37:43 +0900 (JST)
Received: from steelhead ([159.119.168.84]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN400IJO0ITBA@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Tue,
 21 Oct 2003 22:37:42 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ABwhO-0001XI-00 for <pana@ietf.org>; Tue, 21 Oct 2003 06:37:22 -0700
Date: Tue, 21 Oct 2003 06:37:22 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031021133722.GA5577@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.4i
Subject: [Pana] issue23 proposed text
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

In section 9.1, 

change:

"  Message Type
                                                                            
     The Message Type field is three octets, and is used in order to
     communicate the message type with the message.  The 24-bit
     address space is managed by IANA [IANAWEB].
                                                                            
 
to:

"  Message Type
                                                                            
     The Message Type field is three octets, and is used in order to
     communicate the message type with the message.  The 24-bit
     address space is managed by IANA [IANAWEB]. PANA uses its own
     address space for this field."

In section 9.2,

change:

"  AVP Code
                                                                            
      The AVP Code, combined with the Vendor-Id field, identifies the
      attribute uniquely. AVP numbers are allocated by IANA [IANAWEB]."

to:

"  AVP Code
                                                                            
      The AVP Code, combined with the Vendor-Id field, identifies the
      attribute uniquely. AVP numbers are allocated by IANA [IANAWEB].
      PANA uses its own address space for this field."
                                                                            

                                                                            

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


From exim@www1.ietf.org  Tue Oct 21 09:38:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17101
	for <pana-archive@odin.ietf.org>; Tue, 21 Oct 2003 09:38:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwi8-0004mY-02
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 09:38:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LDc7fC018376
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 09:38:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwi7-0004mJ-SR
	for pana-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 09:38:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17048
	for <pana-web-archive@ietf.org>; Tue, 21 Oct 2003 09:37:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwi6-0003S6-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 09:38:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwi5-0003S2-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 09:38:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwi3-0004jQ-1z; Tue, 21 Oct 2003 09:38:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwhv-0004eo-Hy
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 09:37:55 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17041
	for <pana@ietf.org>; Tue, 21 Oct 2003 09:37:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwht-0003Rx-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:37:53 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwhs-0003Rm-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:37:52 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9LDbiF1026389
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:37:45 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9LDbjgi022199
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:37:45 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA22198 ; Tue, 21 Oct 2003 22:37:44 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA16208; Tue, 21 Oct 2003 22:37:44 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA10939; Tue, 21 Oct 2003 22:37:44 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9LDbhqv012209
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:37:43 +0900 (JST)
Received: from steelhead ([159.119.168.84]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN400IJO0ITBA@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Tue,
 21 Oct 2003 22:37:42 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ABwhO-0001XI-00 for <pana@ietf.org>; Tue, 21 Oct 2003 06:37:22 -0700
Date: Tue, 21 Oct 2003 06:37:22 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031021133722.GA5577@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.4i
Subject: [Pana] issue23 proposed text
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

In section 9.1, 

change:

"  Message Type
                                                                            
     The Message Type field is three octets, and is used in order to
     communicate the message type with the message.  The 24-bit
     address space is managed by IANA [IANAWEB].
                                                                            
 
to:

"  Message Type
                                                                            
     The Message Type field is three octets, and is used in order to
     communicate the message type with the message.  The 24-bit
     address space is managed by IANA [IANAWEB]. PANA uses its own
     address space for this field."

In section 9.2,

change:

"  AVP Code
                                                                            
      The AVP Code, combined with the Vendor-Id field, identifies the
      attribute uniquely. AVP numbers are allocated by IANA [IANAWEB]."

to:

"  AVP Code
                                                                            
      The AVP Code, combined with the Vendor-Id field, identifies the
      attribute uniquely. AVP numbers are allocated by IANA [IANAWEB].
      PANA uses its own address space for this field."
                                                                            

                                                                            

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



From pana-admin@ietf.org  Tue Oct 21 09:39:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17180
	for <pana-archive@lists.ietf.org>; Tue, 21 Oct 2003 09:39:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwiz-00055m-QV; Tue, 21 Oct 2003 09:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwip-00053E-SS
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 09:38:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17125
	for <pana@ietf.org>; Tue, 21 Oct 2003 09:38:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwin-0003T1-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:38:49 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwin-0003Sr-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:38:49 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9LDclF1026812
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:38:47 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9LDclHN022692
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:38:47 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA22691 ; Tue, 21 Oct 2003 22:38:46 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA16438; Tue, 21 Oct 2003 22:38:46 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA23554; Tue, 21 Oct 2003 22:38:45 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9LDcjqv012441
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:38:45 +0900 (JST)
Received: from steelhead ([159.119.168.84]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN400ILD0KJBA@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Tue,
 21 Oct 2003 22:38:44 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ABwhx-0001XT-00 for <pana@ietf.org>; Tue, 21 Oct 2003 06:37:57 -0700
Date: Tue, 21 Oct 2003 06:37:57 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031021133757.GB5577@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.4i
Subject: [Pana] issue25 revised text
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

In Section 4.2, change

From:

"  When a PaC receives the PANA-Start-Request message in response to
   the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
   message. The PANA-Start-Answer message contains the initial sequence
   numbers in the tseq and rseq fields of the PANA header, a copy of
   the received Cookie as the PANA payload."

To:

"  PAA MAY enable NAP-ISP authentication separation by setting the
   S-flag of the message header of the PANA-Start-Request.  Also, the
   PANA-Start-Request MAY contain zero or one NAP-Information AVP and
   zero or more ISP-Information AVPs to advertise the information on
   the NAP and/or ISPs.

   When a PaC receives the PANA-Start-Request message in response to
   the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
   message if it wishes to enter the authentication phase.  The
   PANA-Start-Answer message contains the initial sequence numbers in
   the tseq and rseq fields of the PANA header, a copy of the received
   Cookie (if any) as the PANA payload.

   If the S-flag of the received PANA-Start-Request message is not
   set, PaC MUST NOT set the S-flag in the PANA-Start-Answer message
   sent back to the PAA.  In this case, PaC can indicate its choice of
   ISP by including its ISP-Information AVP in the PANA-Start-Answer
   message. AAA routing will be based on the ISP choice if an
   ISP-Information AVP is specified in the PANA-Start-Answer message,
   otherwise it will be based on EAP identifier.

   If the S-flag of the received PANA-Start-Request message is set,
   PaC can indicate its desire to perform separate EAP authentication
   for NAP and ISP by setting the S-flag in the PANA-Start-Answer
   message. In this case, PaC can also indicate its choice of ISP by
   including its ISP-Information AVP in the PANA-Start-Answer message.
   AAA routing for NAP authentication will be based on the NAP.  AAA
   routing for ISP authentication will be based on the ISP choice if
   an ISP-Information AVP is specified in the PANA-Start-Answer
   message, otherwise it will be based on EAP identifier."

In Section 4.3 change

from:

"  A single PANA session can enable more than one EAP authentication.
   This is used to satisfy the separate NAP and ISP authentications
   scenario.  Each EAP authentication is delineated from the subsequent
   one.  The F-flag in the PANA header indicates if this was the final
   authentication from sender's perspective.  If the PAA enables two
   separate authentication, it should not set the F-flag in after the
   first EAP method.  This indicates PAA's willingness to offer another
   authentication method for NAP-ISP separation.  PaC can respond with
   the F-flag unset, indicating PaC's willingness to go through a
   second authentication method.  The PaC can optionally decline by
   setting the F-flag, and this concludes the PANA authentication.  If
   the PAA does not offer two levels of authentication, then it sets
   the F-flag even at the end of first EAP exchange.  In that case the
   PaC has no other option but to set the F-flag to mark the end of
   PANA authentication."

to:

"  A single PANA session can enable more than one EAP authentication.
   This is used to satisfy the separate NAP and ISP authentications
   scenario.  Each EAP authentication is delineated from the subsequent
   one.  The F-flag in the PANA header indicates if this was the final
   authentication from sender's perspective.  If the PAA enables two
   separate authentication, it should not set the F-flag in after the
   first EAP method.  This indicates PAA's willingness to offer another
   authentication method for NAP-ISP separation.  PaC can respond with
   the F-flag unset, indicating PaC's willingness to go through a
   second authentication method.  The PaC can optionally decline by
   setting the F-flag, and this concludes the PANA authentication.  If
   the PAA does not offer two levels of authentication, then it sets
   the F-flag even at the end of first EAP exchange.  In that case the
   PaC has no other option but to set the F-flag to mark the end of
   PANA authentication.

   PAA determines the execution order of NAP authentication and ISP
   authentication.  PAA can indicate which EAP authentication is
   currently occurring by including a NAP-Information or an
   ISP-Information AVP of the corresponding EAP authentication in
   PANA-Auth-Request messages. The PAA MAY stop including the AVP once
   it receives the first PANA-Auth-Answer message of the current EAP
   authentication."

In Section 9.1 change

from:

"  Flags
                                                                                
     The Flags field is eight bits.  The following bits are assigned:
                                                                                
     0 1 2 3 4 5 6 7
    +-+-+-+-+-+-+-+-+
    |R r r r F r r r|
    +-+-+-+-+-+-+-+-+"
                                                                                
To:
                                                                                
"  Flags
                                                                                
     The Flags field is eight bits.  The following bits are assigned:
                                                                                
     0 1 2 3 4 5 6 7
    +-+-+-+-+-+-+-+-+
    |R r r r F S r r|
    +-+-+-+-+-+-+-+-+"
                                                                                

In Section 9.1 

add:

"      S(eparate)
                   - When the S-flag is set in a PANA-Start-Request
                     message it indicates that PAA is willing to offer
                     separate EAP authentication for NAP and ISP.
                     When the S-flag is set in a PANA-Start-Answer
                     message it indicates that PaC accepts on
                     performing separate EAP authentication for NAP
                     and ISP."
 

In Section 9.3.3, change

from:

"
      PANA-Start-Request ::= < PANA-Header: 2, REQ >
                    [ Cookie ]
                  * [ AVP ]
"

to:

"
      PANA-Start-Request ::= < PANA-Header: 2, REQ >
                    [ Cookie ]
		    [ NAP-Information ]
                  * [ ISP-Information ]
                  * [ AVP ]
"


In Section 9.3.4, change

from:

"     PANA-Start-Answer ::= < PANA-Header: 3 >
                    [ Cookie ]
                  * [ AVP ]"

to:

"     PANA-Start-Answer ::= < PANA-Header: 3 >
                    [ Cookie ]
                    [ ISP-Information ]
                  * [ AVP ]"


Add the following sections:

"9.4.9 NAP-Information AVP

The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
contains one globally unique identifier of the NAP in a
Provider-Identifier AVP and one enterprise name of the NAP in a
Provider-Name AVP.  Its Data field has the following ABNF grammar:

      NAP-Information ::= < AVP Header: 1029 >
                           { Provider-Identifier }
                           { Provider-Name }
                         * [ AVP ]


9.4.10 ISP-Information AVP

The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
contains one globally unique identifier of the ISP in a
Provider-Identifier AVP and one enterprise name of the ISP in a
Provider-Name AVP.  Its Data field has the following ABNF grammar:

      ISP-Information ::= < AVP Header: 1030 >
                           { Provider-Identifier }
                           { Provider-Name }
                         * [ AVP ]


9.4.11 Provider-Identifier AVP 

The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
and contains an IANA assigned "SMI Network Management Private
Enterprise Codes" [IANAWEB] value, encoded in network byte order.
 

9.4.12 Provider-Name AVP 

The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
contains the UTF8-encoded name of the provider."

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


From exim@www1.ietf.org  Tue Oct 21 09:39:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17198
	for <pana-archive@odin.ietf.org>; Tue, 21 Oct 2003 09:39:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwj1-00057o-Ik
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 09:39:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LDd3R3019694
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 09:39:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwj1-00057U-Cl
	for pana-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 09:39:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17139
	for <pana-web-archive@ietf.org>; Tue, 21 Oct 2003 09:38:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwiz-0003TS-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 09:39:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwiy-0003TO-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 09:39:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwiz-00055m-QV; Tue, 21 Oct 2003 09:39:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwip-00053E-SS
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 09:38:51 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17125
	for <pana@ietf.org>; Tue, 21 Oct 2003 09:38:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwin-0003T1-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:38:49 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwin-0003Sr-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:38:49 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9LDclF1026812
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:38:47 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9LDclHN022692
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:38:47 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id YAA22691 ; Tue, 21 Oct 2003 22:38:46 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id WAA16438; Tue, 21 Oct 2003 22:38:46 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id WAA23554; Tue, 21 Oct 2003 22:38:45 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9LDcjqv012441
	for <pana@ietf.org>; Tue, 21 Oct 2003 22:38:45 +0900 (JST)
Received: from steelhead ([159.119.168.84]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN400ILD0KJBA@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Tue,
 21 Oct 2003 22:38:44 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ABwhx-0001XT-00 for <pana@ietf.org>; Tue, 21 Oct 2003 06:37:57 -0700
Date: Tue, 21 Oct 2003 06:37:57 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031021133757.GB5577@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.4i
Subject: [Pana] issue25 revised text
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

In Section 4.2, change

From:

"  When a PaC receives the PANA-Start-Request message in response to
   the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
   message. The PANA-Start-Answer message contains the initial sequence
   numbers in the tseq and rseq fields of the PANA header, a copy of
   the received Cookie as the PANA payload."

To:

"  PAA MAY enable NAP-ISP authentication separation by setting the
   S-flag of the message header of the PANA-Start-Request.  Also, the
   PANA-Start-Request MAY contain zero or one NAP-Information AVP and
   zero or more ISP-Information AVPs to advertise the information on
   the NAP and/or ISPs.

   When a PaC receives the PANA-Start-Request message in response to
   the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
   message if it wishes to enter the authentication phase.  The
   PANA-Start-Answer message contains the initial sequence numbers in
   the tseq and rseq fields of the PANA header, a copy of the received
   Cookie (if any) as the PANA payload.

   If the S-flag of the received PANA-Start-Request message is not
   set, PaC MUST NOT set the S-flag in the PANA-Start-Answer message
   sent back to the PAA.  In this case, PaC can indicate its choice of
   ISP by including its ISP-Information AVP in the PANA-Start-Answer
   message. AAA routing will be based on the ISP choice if an
   ISP-Information AVP is specified in the PANA-Start-Answer message,
   otherwise it will be based on EAP identifier.

   If the S-flag of the received PANA-Start-Request message is set,
   PaC can indicate its desire to perform separate EAP authentication
   for NAP and ISP by setting the S-flag in the PANA-Start-Answer
   message. In this case, PaC can also indicate its choice of ISP by
   including its ISP-Information AVP in the PANA-Start-Answer message.
   AAA routing for NAP authentication will be based on the NAP.  AAA
   routing for ISP authentication will be based on the ISP choice if
   an ISP-Information AVP is specified in the PANA-Start-Answer
   message, otherwise it will be based on EAP identifier."

In Section 4.3 change

from:

"  A single PANA session can enable more than one EAP authentication.
   This is used to satisfy the separate NAP and ISP authentications
   scenario.  Each EAP authentication is delineated from the subsequent
   one.  The F-flag in the PANA header indicates if this was the final
   authentication from sender's perspective.  If the PAA enables two
   separate authentication, it should not set the F-flag in after the
   first EAP method.  This indicates PAA's willingness to offer another
   authentication method for NAP-ISP separation.  PaC can respond with
   the F-flag unset, indicating PaC's willingness to go through a
   second authentication method.  The PaC can optionally decline by
   setting the F-flag, and this concludes the PANA authentication.  If
   the PAA does not offer two levels of authentication, then it sets
   the F-flag even at the end of first EAP exchange.  In that case the
   PaC has no other option but to set the F-flag to mark the end of
   PANA authentication."

to:

"  A single PANA session can enable more than one EAP authentication.
   This is used to satisfy the separate NAP and ISP authentications
   scenario.  Each EAP authentication is delineated from the subsequent
   one.  The F-flag in the PANA header indicates if this was the final
   authentication from sender's perspective.  If the PAA enables two
   separate authentication, it should not set the F-flag in after the
   first EAP method.  This indicates PAA's willingness to offer another
   authentication method for NAP-ISP separation.  PaC can respond with
   the F-flag unset, indicating PaC's willingness to go through a
   second authentication method.  The PaC can optionally decline by
   setting the F-flag, and this concludes the PANA authentication.  If
   the PAA does not offer two levels of authentication, then it sets
   the F-flag even at the end of first EAP exchange.  In that case the
   PaC has no other option but to set the F-flag to mark the end of
   PANA authentication.

   PAA determines the execution order of NAP authentication and ISP
   authentication.  PAA can indicate which EAP authentication is
   currently occurring by including a NAP-Information or an
   ISP-Information AVP of the corresponding EAP authentication in
   PANA-Auth-Request messages. The PAA MAY stop including the AVP once
   it receives the first PANA-Auth-Answer message of the current EAP
   authentication."

In Section 9.1 change

from:

"  Flags
                                                                                
     The Flags field is eight bits.  The following bits are assigned:
                                                                                
     0 1 2 3 4 5 6 7
    +-+-+-+-+-+-+-+-+
    |R r r r F r r r|
    +-+-+-+-+-+-+-+-+"
                                                                                
To:
                                                                                
"  Flags
                                                                                
     The Flags field is eight bits.  The following bits are assigned:
                                                                                
     0 1 2 3 4 5 6 7
    +-+-+-+-+-+-+-+-+
    |R r r r F S r r|
    +-+-+-+-+-+-+-+-+"
                                                                                

In Section 9.1 

add:

"      S(eparate)
                   - When the S-flag is set in a PANA-Start-Request
                     message it indicates that PAA is willing to offer
                     separate EAP authentication for NAP and ISP.
                     When the S-flag is set in a PANA-Start-Answer
                     message it indicates that PaC accepts on
                     performing separate EAP authentication for NAP
                     and ISP."
 

In Section 9.3.3, change

from:

"
      PANA-Start-Request ::= < PANA-Header: 2, REQ >
                    [ Cookie ]
                  * [ AVP ]
"

to:

"
      PANA-Start-Request ::= < PANA-Header: 2, REQ >
                    [ Cookie ]
		    [ NAP-Information ]
                  * [ ISP-Information ]
                  * [ AVP ]
"


In Section 9.3.4, change

from:

"     PANA-Start-Answer ::= < PANA-Header: 3 >
                    [ Cookie ]
                  * [ AVP ]"

to:

"     PANA-Start-Answer ::= < PANA-Header: 3 >
                    [ Cookie ]
                    [ ISP-Information ]
                  * [ AVP ]"


Add the following sections:

"9.4.9 NAP-Information AVP

The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
contains one globally unique identifier of the NAP in a
Provider-Identifier AVP and one enterprise name of the NAP in a
Provider-Name AVP.  Its Data field has the following ABNF grammar:

      NAP-Information ::= < AVP Header: 1029 >
                           { Provider-Identifier }
                           { Provider-Name }
                         * [ AVP ]


9.4.10 ISP-Information AVP

The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
contains one globally unique identifier of the ISP in a
Provider-Identifier AVP and one enterprise name of the ISP in a
Provider-Name AVP.  Its Data field has the following ABNF grammar:

      ISP-Information ::= < AVP Header: 1030 >
                           { Provider-Identifier }
                           { Provider-Name }
                         * [ AVP ]


9.4.11 Provider-Identifier AVP 

The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
and contains an IANA assigned "SMI Network Management Private
Enterprise Codes" [IANAWEB] value, encoded in network byte order.
 

9.4.12 Provider-Name AVP 

The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
contains the UTF8-encoded name of the provider."

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



From pana-admin@ietf.org  Tue Oct 21 09:55:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17634
	for <pana-archive@lists.ietf.org>; Tue, 21 Oct 2003 09:55:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwyU-00012L-6w; Tue, 21 Oct 2003 09:55:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwxa-0000iQ-HB
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 09:54:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17599
	for <pana@ietf.org>; Tue, 21 Oct 2003 09:53:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwxY-0003dg-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:54:04 -0400
Received: from web40010.mail.yahoo.com ([66.218.78.28])
	by ietf-mx with smtp (Exim 4.12)
	id 1ABwxX-0003dX-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:54:03 -0400
Message-ID: <20031021135332.93999.qmail@web40010.mail.yahoo.com>
Received: from [47.234.0.52] by web40010.mail.yahoo.com via HTTP; Tue, 21 Oct 2003 06:53:32 PDT
Date: Tue, 21 Oct 2003 06:53:32 -0700 (PDT)
From: Reinaldo Penno <rapenno@yahoo.com>
Subject: Re: [Pana] issue25 revised text
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
In-Reply-To: <20031021133757.GB5577@steelhead>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Yoshi,

I finally found comment to comment on this issue. In
PPPoE, the "Service-Profiles" tied to a specific ISP
are just names and descriptions. so, you can have even
*one* PPPoE server, offering several distinct services
such as "bandwidth 1024", "tunnelling", "video on
demand", etc, etc.

The same should apply to PANA.

The Service-Profiles in PPPoE are not just for
authentication. I mentioned in the first post that the
definition of the term was loose on purpose, and
that's where its power comes from. 

I'm not sure we can do this in this proposal. I'm not
sure after the IANA provider identifier we can convey
such information.

It seems we are trying to tie everything together for
the purposes of aithentication and in the process
distancing ourselves from the original meaning of the
field in PPPoE. If I'm wrong, please correct me.

The information contained in the packet should be (one
or more of) ISP + any services the ISP offers.
Something like

{ISP A}, {Gold, Silver, Bronze, Platinum}.
{ISP B}, {Video, Voice, VPN}

Can I do this with the current proposal?

thanks,

Reinaldo






--- Yoshihiro Ohba <yohba@tari.toshiba.com> wrote:
> In Section 4.2, change
> 
> From:
> 
> "  When a PaC receives the PANA-Start-Request
> message in response to
>    the PANA-PAA-Discover message, it responds with a
> PANA-Start-Answer
>    message. The PANA-Start-Answer message contains
> the initial sequence
>    numbers in the tseq and rseq fields of the PANA
> header, a copy of
>    the received Cookie as the PANA payload."
> 
> To:
> 
> "  PAA MAY enable NAP-ISP authentication separation
> by setting the
>    S-flag of the message header of the
> PANA-Start-Request.  Also, the
>    PANA-Start-Request MAY contain zero or one
> NAP-Information AVP and
>    zero or more ISP-Information AVPs to advertise
> the information on
>    the NAP and/or ISPs.
> 
>    When a PaC receives the PANA-Start-Request
> message in response to
>    the PANA-PAA-Discover message, it responds with a
> PANA-Start-Answer
>    message if it wishes to enter the authentication
> phase.  The
>    PANA-Start-Answer message contains the initial
> sequence numbers in
>    the tseq and rseq fields of the PANA header, a
> copy of the received
>    Cookie (if any) as the PANA payload.
> 
>    If the S-flag of the received PANA-Start-Request
> message is not
>    set, PaC MUST NOT set the S-flag in the
> PANA-Start-Answer message
>    sent back to the PAA.  In this case, PaC can
> indicate its choice of
>    ISP by including its ISP-Information AVP in the
> PANA-Start-Answer
>    message. AAA routing will be based on the ISP
> choice if an
>    ISP-Information AVP is specified in the
> PANA-Start-Answer message,
>    otherwise it will be based on EAP identifier.
> 
>    If the S-flag of the received PANA-Start-Request
> message is set,
>    PaC can indicate its desire to perform separate
> EAP authentication
>    for NAP and ISP by setting the S-flag in the
> PANA-Start-Answer
>    message. In this case, PaC can also indicate its
> choice of ISP by
>    including its ISP-Information AVP in the
> PANA-Start-Answer message.
>    AAA routing for NAP authentication will be based
> on the NAP.  AAA
>    routing for ISP authentication will be based on
> the ISP choice if
>    an ISP-Information AVP is specified in the
> PANA-Start-Answer
>    message, otherwise it will be based on EAP
> identifier."
> 
> In Section 4.3 change
> 
> from:
> 
> "  A single PANA session can enable more than one
> EAP authentication.
>    This is used to satisfy the separate NAP and ISP
> authentications
>    scenario.  Each EAP authentication is delineated
> from the subsequent
>    one.  The F-flag in the PANA header indicates if
> this was the final
>    authentication from sender's perspective.  If the
> PAA enables two
>    separate authentication, it should not set the
> F-flag in after the
>    first EAP method.  This indicates PAA's
> willingness to offer another
>    authentication method for NAP-ISP separation. 
> PaC can respond with
>    the F-flag unset, indicating PaC's willingness to
> go through a
>    second authentication method.  The PaC can
> optionally decline by
>    setting the F-flag, and this concludes the PANA
> authentication.  If
>    the PAA does not offer two levels of
> authentication, then it sets
>    the F-flag even at the end of first EAP exchange.
>  In that case the
>    PaC has no other option but to set the F-flag to
> mark the end of
>    PANA authentication."
> 
> to:
> 
> "  A single PANA session can enable more than one
> EAP authentication.
>    This is used to satisfy the separate NAP and ISP
> authentications
>    scenario.  Each EAP authentication is delineated
> from the subsequent
>    one.  The F-flag in the PANA header indicates if
> this was the final
>    authentication from sender's perspective.  If the
> PAA enables two
>    separate authentication, it should not set the
> F-flag in after the
>    first EAP method.  This indicates PAA's
> willingness to offer another
>    authentication method for NAP-ISP separation. 
> PaC can respond with
>    the F-flag unset, indicating PaC's willingness to
> go through a
>    second authentication method.  The PaC can
> optionally decline by
>    setting the F-flag, and this concludes the PANA
> authentication.  If
>    the PAA does not offer two levels of
> authentication, then it sets
>    the F-flag even at the end of first EAP exchange.
>  In that case the
>    PaC has no other option but to set the F-flag to
> mark the end of
>    PANA authentication.
> 
>    PAA determines the execution order of NAP
> authentication and ISP
>    authentication.  PAA can indicate which EAP
> authentication is
>    currently occurring by including a
> NAP-Information or an
>    ISP-Information AVP of the corresponding EAP
> authentication in
>    PANA-Auth-Request messages. The PAA MAY stop
> including the AVP once
>    it receives the first PANA-Auth-Answer message of
> the current EAP
>    authentication."
> 
> In Section 9.1 change
> 
> from:
> 
> "  Flags
>                                                     
>                            
>      The Flags field is eight bits.  The following
> bits are assigned:
>                                                     
>                            
>      0 1 2 3 4 5 6 7
>     +-+-+-+-+-+-+-+-+
>     |R r r r F r r r|
>     +-+-+-+-+-+-+-+-+"
>                                                     
>                            
> To:
>                                                     
>                            
> "  Flags
>                                                     
>                            
>      The Flags field is eight bits.  The following
> bits are assigned:
>                                                     
>                            
>      0 1 2 3 4 5 6 7
>     +-+-+-+-+-+-+-+-+
>     |R r r r F S r r|
>     +-+-+-+-+-+-+-+-+"
>                                                     
>                            
> 
> In Section 9.1 
> 
> add:
> 
> "      S(eparate)
>                    - When the S-flag is set in a
> PANA-Start-Request
>                      message it indicates that PAA
> is willing to offer
>                      separate EAP authentication for
> NAP and ISP.
>                      When the S-flag is set in a
> PANA-Start-Answer
>                      message it indicates that PaC
> accepts on
>                      performing separate EAP
> authentication 
=== message truncated ===



__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

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


From exim@www1.ietf.org  Tue Oct 21 09:55:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17649
	for <pana-archive@odin.ietf.org>; Tue, 21 Oct 2003 09:55:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwyW-00014J-2Q
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 09:55:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LDt3fm004101
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 09:55:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwyV-00013Y-RP
	for pana-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 09:55:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17618
	for <pana-web-archive@ietf.org>; Tue, 21 Oct 2003 09:54:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwyT-0003e6-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 09:55:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwyT-0003e3-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 09:55:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwyU-00012L-6w; Tue, 21 Oct 2003 09:55:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABwxa-0000iQ-HB
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 09:54:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17599
	for <pana@ietf.org>; Tue, 21 Oct 2003 09:53:55 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABwxY-0003dg-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:54:04 -0400
Received: from web40010.mail.yahoo.com ([66.218.78.28])
	by ietf-mx with smtp (Exim 4.12)
	id 1ABwxX-0003dX-00
	for pana@ietf.org; Tue, 21 Oct 2003 09:54:03 -0400
Message-ID: <20031021135332.93999.qmail@web40010.mail.yahoo.com>
Received: from [47.234.0.52] by web40010.mail.yahoo.com via HTTP; Tue, 21 Oct 2003 06:53:32 PDT
Date: Tue, 21 Oct 2003 06:53:32 -0700 (PDT)
From: Reinaldo Penno <rapenno@yahoo.com>
Subject: Re: [Pana] issue25 revised text
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
In-Reply-To: <20031021133757.GB5577@steelhead>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Yoshi,

I finally found comment to comment on this issue. In
PPPoE, the "Service-Profiles" tied to a specific ISP
are just names and descriptions. so, you can have even
*one* PPPoE server, offering several distinct services
such as "bandwidth 1024", "tunnelling", "video on
demand", etc, etc.

The same should apply to PANA.

The Service-Profiles in PPPoE are not just for
authentication. I mentioned in the first post that the
definition of the term was loose on purpose, and
that's where its power comes from. 

I'm not sure we can do this in this proposal. I'm not
sure after the IANA provider identifier we can convey
such information.

It seems we are trying to tie everything together for
the purposes of aithentication and in the process
distancing ourselves from the original meaning of the
field in PPPoE. If I'm wrong, please correct me.

The information contained in the packet should be (one
or more of) ISP + any services the ISP offers.
Something like

{ISP A}, {Gold, Silver, Bronze, Platinum}.
{ISP B}, {Video, Voice, VPN}

Can I do this with the current proposal?

thanks,

Reinaldo






--- Yoshihiro Ohba <yohba@tari.toshiba.com> wrote:
> In Section 4.2, change
> 
> From:
> 
> "  When a PaC receives the PANA-Start-Request
> message in response to
>    the PANA-PAA-Discover message, it responds with a
> PANA-Start-Answer
>    message. The PANA-Start-Answer message contains
> the initial sequence
>    numbers in the tseq and rseq fields of the PANA
> header, a copy of
>    the received Cookie as the PANA payload."
> 
> To:
> 
> "  PAA MAY enable NAP-ISP authentication separation
> by setting the
>    S-flag of the message header of the
> PANA-Start-Request.  Also, the
>    PANA-Start-Request MAY contain zero or one
> NAP-Information AVP and
>    zero or more ISP-Information AVPs to advertise
> the information on
>    the NAP and/or ISPs.
> 
>    When a PaC receives the PANA-Start-Request
> message in response to
>    the PANA-PAA-Discover message, it responds with a
> PANA-Start-Answer
>    message if it wishes to enter the authentication
> phase.  The
>    PANA-Start-Answer message contains the initial
> sequence numbers in
>    the tseq and rseq fields of the PANA header, a
> copy of the received
>    Cookie (if any) as the PANA payload.
> 
>    If the S-flag of the received PANA-Start-Request
> message is not
>    set, PaC MUST NOT set the S-flag in the
> PANA-Start-Answer message
>    sent back to the PAA.  In this case, PaC can
> indicate its choice of
>    ISP by including its ISP-Information AVP in the
> PANA-Start-Answer
>    message. AAA routing will be based on the ISP
> choice if an
>    ISP-Information AVP is specified in the
> PANA-Start-Answer message,
>    otherwise it will be based on EAP identifier.
> 
>    If the S-flag of the received PANA-Start-Request
> message is set,
>    PaC can indicate its desire to perform separate
> EAP authentication
>    for NAP and ISP by setting the S-flag in the
> PANA-Start-Answer
>    message. In this case, PaC can also indicate its
> choice of ISP by
>    including its ISP-Information AVP in the
> PANA-Start-Answer message.
>    AAA routing for NAP authentication will be based
> on the NAP.  AAA
>    routing for ISP authentication will be based on
> the ISP choice if
>    an ISP-Information AVP is specified in the
> PANA-Start-Answer
>    message, otherwise it will be based on EAP
> identifier."
> 
> In Section 4.3 change
> 
> from:
> 
> "  A single PANA session can enable more than one
> EAP authentication.
>    This is used to satisfy the separate NAP and ISP
> authentications
>    scenario.  Each EAP authentication is delineated
> from the subsequent
>    one.  The F-flag in the PANA header indicates if
> this was the final
>    authentication from sender's perspective.  If the
> PAA enables two
>    separate authentication, it should not set the
> F-flag in after the
>    first EAP method.  This indicates PAA's
> willingness to offer another
>    authentication method for NAP-ISP separation. 
> PaC can respond with
>    the F-flag unset, indicating PaC's willingness to
> go through a
>    second authentication method.  The PaC can
> optionally decline by
>    setting the F-flag, and this concludes the PANA
> authentication.  If
>    the PAA does not offer two levels of
> authentication, then it sets
>    the F-flag even at the end of first EAP exchange.
>  In that case the
>    PaC has no other option but to set the F-flag to
> mark the end of
>    PANA authentication."
> 
> to:
> 
> "  A single PANA session can enable more than one
> EAP authentication.
>    This is used to satisfy the separate NAP and ISP
> authentications
>    scenario.  Each EAP authentication is delineated
> from the subsequent
>    one.  The F-flag in the PANA header indicates if
> this was the final
>    authentication from sender's perspective.  If the
> PAA enables two
>    separate authentication, it should not set the
> F-flag in after the
>    first EAP method.  This indicates PAA's
> willingness to offer another
>    authentication method for NAP-ISP separation. 
> PaC can respond with
>    the F-flag unset, indicating PaC's willingness to
> go through a
>    second authentication method.  The PaC can
> optionally decline by
>    setting the F-flag, and this concludes the PANA
> authentication.  If
>    the PAA does not offer two levels of
> authentication, then it sets
>    the F-flag even at the end of first EAP exchange.
>  In that case the
>    PaC has no other option but to set the F-flag to
> mark the end of
>    PANA authentication.
> 
>    PAA determines the execution order of NAP
> authentication and ISP
>    authentication.  PAA can indicate which EAP
> authentication is
>    currently occurring by including a
> NAP-Information or an
>    ISP-Information AVP of the corresponding EAP
> authentication in
>    PANA-Auth-Request messages. The PAA MAY stop
> including the AVP once
>    it receives the first PANA-Auth-Answer message of
> the current EAP
>    authentication."
> 
> In Section 9.1 change
> 
> from:
> 
> "  Flags
>                                                     
>                            
>      The Flags field is eight bits.  The following
> bits are assigned:
>                                                     
>                            
>      0 1 2 3 4 5 6 7
>     +-+-+-+-+-+-+-+-+
>     |R r r r F r r r|
>     +-+-+-+-+-+-+-+-+"
>                                                     
>                            
> To:
>                                                     
>                            
> "  Flags
>                                                     
>                            
>      The Flags field is eight bits.  The following
> bits are assigned:
>                                                     
>                            
>      0 1 2 3 4 5 6 7
>     +-+-+-+-+-+-+-+-+
>     |R r r r F S r r|
>     +-+-+-+-+-+-+-+-+"
>                                                     
>                            
> 
> In Section 9.1 
> 
> add:
> 
> "      S(eparate)
>                    - When the S-flag is set in a
> PANA-Start-Request
>                      message it indicates that PAA
> is willing to offer
>                      separate EAP authentication for
> NAP and ISP.
>                      When the S-flag is set in a
> PANA-Start-Answer
>                      message it indicates that PaC
> accepts on
>                      performing separate EAP
> authentication 
=== message truncated ===



__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

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



From pana-admin@ietf.org  Tue Oct 21 11:42:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23892
	for <pana-archive@lists.ietf.org>; Tue, 21 Oct 2003 11:42:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABye0-0005y5-UY; Tue, 21 Oct 2003 11:42:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABydS-0005sJ-Ui
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 11:41:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23875
	for <pana@ietf.org>; Tue, 21 Oct 2003 11:41:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABydR-0005AW-00
	for pana@ietf.org; Tue, 21 Oct 2003 11:41:25 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABydQ-0005AT-00
	for pana@ietf.org; Tue, 21 Oct 2003 11:41:25 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9LFfMF1001150;
	Wed, 22 Oct 2003 00:41:22 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9LFfMPx015871;
	Wed, 22 Oct 2003 00:41:22 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id AAA15870 ; Wed, 22 Oct 2003 00:41:22 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA27729; Wed, 22 Oct 2003 00:41:22 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA04138; Wed, 22 Oct 2003 00:41:21 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9LFfLqv012458;
	Wed, 22 Oct 2003 00:41:21 +0900 (JST)
Received: from steelhead ([159.119.168.162]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN4006B268UQJ@tsbpo1.po.toshiba.co.jp>; Wed,
 22 Oct 2003 00:41:20 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ABybV-0001kv-00; Tue, 21 Oct 2003 08:39:25 -0700
Date: Tue, 21 Oct 2003 08:39:25 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue25 revised text
In-reply-to: <20031021135332.93999.qmail@web40010.mail.yahoo.com>
To: Reinaldo Penno <rapenno@yahoo.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031021153924.GD5577@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Reinaldo Penno <rapenno@yahoo.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031021133757.GB5577@steelhead>
 <20031021135332.93999.qmail@web40010.mail.yahoo.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Reinaldo,

I think it would be better to discuss the issue step-by-step.  That is
why I started from including provider identifier and name (and we have
reached a rough consensus on it).  I would suggest creating a new
issue to discuss whether more detailed service profile information
should be added or not.

Yoshihiro Ohba


On Tue, Oct 21, 2003 at 06:53:32AM -0700, Reinaldo Penno wrote:
> Hi Yoshi,
> 
> I finally found comment to comment on this issue. In
> PPPoE, the "Service-Profiles" tied to a specific ISP
> are just names and descriptions. so, you can have even
> *one* PPPoE server, offering several distinct services
> such as "bandwidth 1024", "tunnelling", "video on
> demand", etc, etc.
> 
> The same should apply to PANA.
> 
> The Service-Profiles in PPPoE are not just for
> authentication. I mentioned in the first post that the
> definition of the term was loose on purpose, and
> that's where its power comes from. 
> 
> I'm not sure we can do this in this proposal. I'm not
> sure after the IANA provider identifier we can convey
> such information.
> 
> It seems we are trying to tie everything together for
> the purposes of aithentication and in the process
> distancing ourselves from the original meaning of the
> field in PPPoE. If I'm wrong, please correct me.
> 
> The information contained in the packet should be (one
> or more of) ISP + any services the ISP offers.
> Something like
> 
> {ISP A}, {Gold, Silver, Bronze, Platinum}.
> {ISP B}, {Video, Voice, VPN}
> 
> Can I do this with the current proposal?
> 
> thanks,
> 
> Reinaldo
> 
> 
> 
> 
> 
> 
> --- Yoshihiro Ohba <yohba@tari.toshiba.com> wrote:
> > In Section 4.2, change
> > 
> > From:
> > 
> > "  When a PaC receives the PANA-Start-Request
> > message in response to
> >    the PANA-PAA-Discover message, it responds with a
> > PANA-Start-Answer
> >    message. The PANA-Start-Answer message contains
> > the initial sequence
> >    numbers in the tseq and rseq fields of the PANA
> > header, a copy of
> >    the received Cookie as the PANA payload."
> > 
> > To:
> > 
> > "  PAA MAY enable NAP-ISP authentication separation
> > by setting the
> >    S-flag of the message header of the
> > PANA-Start-Request.  Also, the
> >    PANA-Start-Request MAY contain zero or one
> > NAP-Information AVP and
> >    zero or more ISP-Information AVPs to advertise
> > the information on
> >    the NAP and/or ISPs.
> > 
> >    When a PaC receives the PANA-Start-Request
> > message in response to
> >    the PANA-PAA-Discover message, it responds with a
> > PANA-Start-Answer
> >    message if it wishes to enter the authentication
> > phase.  The
> >    PANA-Start-Answer message contains the initial
> > sequence numbers in
> >    the tseq and rseq fields of the PANA header, a
> > copy of the received
> >    Cookie (if any) as the PANA payload.
> > 
> >    If the S-flag of the received PANA-Start-Request
> > message is not
> >    set, PaC MUST NOT set the S-flag in the
> > PANA-Start-Answer message
> >    sent back to the PAA.  In this case, PaC can
> > indicate its choice of
> >    ISP by including its ISP-Information AVP in the
> > PANA-Start-Answer
> >    message. AAA routing will be based on the ISP
> > choice if an
> >    ISP-Information AVP is specified in the
> > PANA-Start-Answer message,
> >    otherwise it will be based on EAP identifier.
> > 
> >    If the S-flag of the received PANA-Start-Request
> > message is set,
> >    PaC can indicate its desire to perform separate
> > EAP authentication
> >    for NAP and ISP by setting the S-flag in the
> > PANA-Start-Answer
> >    message. In this case, PaC can also indicate its
> > choice of ISP by
> >    including its ISP-Information AVP in the
> > PANA-Start-Answer message.
> >    AAA routing for NAP authentication will be based
> > on the NAP.  AAA
> >    routing for ISP authentication will be based on
> > the ISP choice if
> >    an ISP-Information AVP is specified in the
> > PANA-Start-Answer
> >    message, otherwise it will be based on EAP
> > identifier."
> > 
> > In Section 4.3 change
> > 
> > from:
> > 
> > "  A single PANA session can enable more than one
> > EAP authentication.
> >    This is used to satisfy the separate NAP and ISP
> > authentications
> >    scenario.  Each EAP authentication is delineated
> > from the subsequent
> >    one.  The F-flag in the PANA header indicates if
> > this was the final
> >    authentication from sender's perspective.  If the
> > PAA enables two
> >    separate authentication, it should not set the
> > F-flag in after the
> >    first EAP method.  This indicates PAA's
> > willingness to offer another
> >    authentication method for NAP-ISP separation. 
> > PaC can respond with
> >    the F-flag unset, indicating PaC's willingness to
> > go through a
> >    second authentication method.  The PaC can
> > optionally decline by
> >    setting the F-flag, and this concludes the PANA
> > authentication.  If
> >    the PAA does not offer two levels of
> > authentication, then it sets
> >    the F-flag even at the end of first EAP exchange.
> >  In that case the
> >    PaC has no other option but to set the F-flag to
> > mark the end of
> >    PANA authentication."
> > 
> > to:
> > 
> > "  A single PANA session can enable more than one
> > EAP authentication.
> >    This is used to satisfy the separate NAP and ISP
> > authentications
> >    scenario.  Each EAP authentication is delineated
> > from the subsequent
> >    one.  The F-flag in the PANA header indicates if
> > this was the final
> >    authentication from sender's perspective.  If the
> > PAA enables two
> >    separate authentication, it should not set the
> > F-flag in after the
> >    first EAP method.  This indicates PAA's
> > willingness to offer another
> >    authentication method for NAP-ISP separation. 
> > PaC can respond with
> >    the F-flag unset, indicating PaC's willingness to
> > go through a
> >    second authentication method.  The PaC can
> > optionally decline by
> >    setting the F-flag, and this concludes the PANA
> > authentication.  If
> >    the PAA does not offer two levels of
> > authentication, then it sets
> >    the F-flag even at the end of first EAP exchange.
> >  In that case the
> >    PaC has no other option but to set the F-flag to
> > mark the end of
> >    PANA authentication.
> > 
> >    PAA determines the execution order of NAP
> > authentication and ISP
> >    authentication.  PAA can indicate which EAP
> > authentication is
> >    currently occurring by including a
> > NAP-Information or an
> >    ISP-Information AVP of the corresponding EAP
> > authentication in
> >    PANA-Auth-Request messages. The PAA MAY stop
> > including the AVP once
> >    it receives the first PANA-Auth-Answer message of
> > the current EAP
> >    authentication."
> > 
> > In Section 9.1 change
> > 
> > from:
> > 
> > "  Flags
> >                                                     
> >                            
> >      The Flags field is eight bits.  The following
> > bits are assigned:
> >                                                     
> >                            
> >      0 1 2 3 4 5 6 7
> >     +-+-+-+-+-+-+-+-+
> >     |R r r r F r r r|
> >     +-+-+-+-+-+-+-+-+"
> >                                                     
> >                            
> > To:
> >                                                     
> >                            
> > "  Flags
> >                                                     
> >                            
> >      The Flags field is eight bits.  The following
> > bits are assigned:
> >                                                     
> >                            
> >      0 1 2 3 4 5 6 7
> >     +-+-+-+-+-+-+-+-+
> >     |R r r r F S r r|
> >     +-+-+-+-+-+-+-+-+"
> >                                                     
> >                            
> > 
> > In Section 9.1 
> > 
> > add:
> > 
> > "      S(eparate)
> >                    - When the S-flag is set in a
> > PANA-Start-Request
> >                      message it indicates that PAA
> > is willing to offer
> >                      separate EAP authentication for
> > NAP and ISP.
> >                      When the S-flag is set in a
> > PANA-Start-Answer
> >                      message it indicates that PaC
> > accepts on
> >                      performing separate EAP
> > authentication 
> === message truncated ===
> 
> 
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com

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


From exim@www1.ietf.org  Tue Oct 21 11:42:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23910
	for <pana-archive@odin.ietf.org>; Tue, 21 Oct 2003 11:42:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABye3-0005zi-HO
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 11:42:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LFg3PR023042
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 11:42:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABye3-0005zZ-DW
	for pana-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 11:42:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23879
	for <pana-web-archive@ietf.org>; Tue, 21 Oct 2003 11:41:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABye2-0005Ag-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 11:42:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABye1-0005Ad-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 11:42:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABye0-0005y5-UY; Tue, 21 Oct 2003 11:42:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABydS-0005sJ-Ui
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 11:41:26 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23875
	for <pana@ietf.org>; Tue, 21 Oct 2003 11:41:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABydR-0005AW-00
	for pana@ietf.org; Tue, 21 Oct 2003 11:41:25 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABydQ-0005AT-00
	for pana@ietf.org; Tue, 21 Oct 2003 11:41:25 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9LFfMF1001150;
	Wed, 22 Oct 2003 00:41:22 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9LFfMPx015871;
	Wed, 22 Oct 2003 00:41:22 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id AAA15870 ; Wed, 22 Oct 2003 00:41:22 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA27729; Wed, 22 Oct 2003 00:41:22 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA04138; Wed, 22 Oct 2003 00:41:21 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9LFfLqv012458;
	Wed, 22 Oct 2003 00:41:21 +0900 (JST)
Received: from steelhead ([159.119.168.162]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN4006B268UQJ@tsbpo1.po.toshiba.co.jp>; Wed,
 22 Oct 2003 00:41:20 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ABybV-0001kv-00; Tue, 21 Oct 2003 08:39:25 -0700
Date: Tue, 21 Oct 2003 08:39:25 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue25 revised text
In-reply-to: <20031021135332.93999.qmail@web40010.mail.yahoo.com>
To: Reinaldo Penno <rapenno@yahoo.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031021153924.GD5577@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Reinaldo Penno <rapenno@yahoo.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031021133757.GB5577@steelhead>
 <20031021135332.93999.qmail@web40010.mail.yahoo.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Hi Reinaldo,

I think it would be better to discuss the issue step-by-step.  That is
why I started from including provider identifier and name (and we have
reached a rough consensus on it).  I would suggest creating a new
issue to discuss whether more detailed service profile information
should be added or not.

Yoshihiro Ohba


On Tue, Oct 21, 2003 at 06:53:32AM -0700, Reinaldo Penno wrote:
> Hi Yoshi,
> 
> I finally found comment to comment on this issue. In
> PPPoE, the "Service-Profiles" tied to a specific ISP
> are just names and descriptions. so, you can have even
> *one* PPPoE server, offering several distinct services
> such as "bandwidth 1024", "tunnelling", "video on
> demand", etc, etc.
> 
> The same should apply to PANA.
> 
> The Service-Profiles in PPPoE are not just for
> authentication. I mentioned in the first post that the
> definition of the term was loose on purpose, and
> that's where its power comes from. 
> 
> I'm not sure we can do this in this proposal. I'm not
> sure after the IANA provider identifier we can convey
> such information.
> 
> It seems we are trying to tie everything together for
> the purposes of aithentication and in the process
> distancing ourselves from the original meaning of the
> field in PPPoE. If I'm wrong, please correct me.
> 
> The information contained in the packet should be (one
> or more of) ISP + any services the ISP offers.
> Something like
> 
> {ISP A}, {Gold, Silver, Bronze, Platinum}.
> {ISP B}, {Video, Voice, VPN}
> 
> Can I do this with the current proposal?
> 
> thanks,
> 
> Reinaldo
> 
> 
> 
> 
> 
> 
> --- Yoshihiro Ohba <yohba@tari.toshiba.com> wrote:
> > In Section 4.2, change
> > 
> > From:
> > 
> > "  When a PaC receives the PANA-Start-Request
> > message in response to
> >    the PANA-PAA-Discover message, it responds with a
> > PANA-Start-Answer
> >    message. The PANA-Start-Answer message contains
> > the initial sequence
> >    numbers in the tseq and rseq fields of the PANA
> > header, a copy of
> >    the received Cookie as the PANA payload."
> > 
> > To:
> > 
> > "  PAA MAY enable NAP-ISP authentication separation
> > by setting the
> >    S-flag of the message header of the
> > PANA-Start-Request.  Also, the
> >    PANA-Start-Request MAY contain zero or one
> > NAP-Information AVP and
> >    zero or more ISP-Information AVPs to advertise
> > the information on
> >    the NAP and/or ISPs.
> > 
> >    When a PaC receives the PANA-Start-Request
> > message in response to
> >    the PANA-PAA-Discover message, it responds with a
> > PANA-Start-Answer
> >    message if it wishes to enter the authentication
> > phase.  The
> >    PANA-Start-Answer message contains the initial
> > sequence numbers in
> >    the tseq and rseq fields of the PANA header, a
> > copy of the received
> >    Cookie (if any) as the PANA payload.
> > 
> >    If the S-flag of the received PANA-Start-Request
> > message is not
> >    set, PaC MUST NOT set the S-flag in the
> > PANA-Start-Answer message
> >    sent back to the PAA.  In this case, PaC can
> > indicate its choice of
> >    ISP by including its ISP-Information AVP in the
> > PANA-Start-Answer
> >    message. AAA routing will be based on the ISP
> > choice if an
> >    ISP-Information AVP is specified in the
> > PANA-Start-Answer message,
> >    otherwise it will be based on EAP identifier.
> > 
> >    If the S-flag of the received PANA-Start-Request
> > message is set,
> >    PaC can indicate its desire to perform separate
> > EAP authentication
> >    for NAP and ISP by setting the S-flag in the
> > PANA-Start-Answer
> >    message. In this case, PaC can also indicate its
> > choice of ISP by
> >    including its ISP-Information AVP in the
> > PANA-Start-Answer message.
> >    AAA routing for NAP authentication will be based
> > on the NAP.  AAA
> >    routing for ISP authentication will be based on
> > the ISP choice if
> >    an ISP-Information AVP is specified in the
> > PANA-Start-Answer
> >    message, otherwise it will be based on EAP
> > identifier."
> > 
> > In Section 4.3 change
> > 
> > from:
> > 
> > "  A single PANA session can enable more than one
> > EAP authentication.
> >    This is used to satisfy the separate NAP and ISP
> > authentications
> >    scenario.  Each EAP authentication is delineated
> > from the subsequent
> >    one.  The F-flag in the PANA header indicates if
> > this was the final
> >    authentication from sender's perspective.  If the
> > PAA enables two
> >    separate authentication, it should not set the
> > F-flag in after the
> >    first EAP method.  This indicates PAA's
> > willingness to offer another
> >    authentication method for NAP-ISP separation. 
> > PaC can respond with
> >    the F-flag unset, indicating PaC's willingness to
> > go through a
> >    second authentication method.  The PaC can
> > optionally decline by
> >    setting the F-flag, and this concludes the PANA
> > authentication.  If
> >    the PAA does not offer two levels of
> > authentication, then it sets
> >    the F-flag even at the end of first EAP exchange.
> >  In that case the
> >    PaC has no other option but to set the F-flag to
> > mark the end of
> >    PANA authentication."
> > 
> > to:
> > 
> > "  A single PANA session can enable more than one
> > EAP authentication.
> >    This is used to satisfy the separate NAP and ISP
> > authentications
> >    scenario.  Each EAP authentication is delineated
> > from the subsequent
> >    one.  The F-flag in the PANA header indicates if
> > this was the final
> >    authentication from sender's perspective.  If the
> > PAA enables two
> >    separate authentication, it should not set the
> > F-flag in after the
> >    first EAP method.  This indicates PAA's
> > willingness to offer another
> >    authentication method for NAP-ISP separation. 
> > PaC can respond with
> >    the F-flag unset, indicating PaC's willingness to
> > go through a
> >    second authentication method.  The PaC can
> > optionally decline by
> >    setting the F-flag, and this concludes the PANA
> > authentication.  If
> >    the PAA does not offer two levels of
> > authentication, then it sets
> >    the F-flag even at the end of first EAP exchange.
> >  In that case the
> >    PaC has no other option but to set the F-flag to
> > mark the end of
> >    PANA authentication.
> > 
> >    PAA determines the execution order of NAP
> > authentication and ISP
> >    authentication.  PAA can indicate which EAP
> > authentication is
> >    currently occurring by including a
> > NAP-Information or an
> >    ISP-Information AVP of the corresponding EAP
> > authentication in
> >    PANA-Auth-Request messages. The PAA MAY stop
> > including the AVP once
> >    it receives the first PANA-Auth-Answer message of
> > the current EAP
> >    authentication."
> > 
> > In Section 9.1 change
> > 
> > from:
> > 
> > "  Flags
> >                                                     
> >                            
> >      The Flags field is eight bits.  The following
> > bits are assigned:
> >                                                     
> >                            
> >      0 1 2 3 4 5 6 7
> >     +-+-+-+-+-+-+-+-+
> >     |R r r r F r r r|
> >     +-+-+-+-+-+-+-+-+"
> >                                                     
> >                            
> > To:
> >                                                     
> >                            
> > "  Flags
> >                                                     
> >                            
> >      The Flags field is eight bits.  The following
> > bits are assigned:
> >                                                     
> >                            
> >      0 1 2 3 4 5 6 7
> >     +-+-+-+-+-+-+-+-+
> >     |R r r r F S r r|
> >     +-+-+-+-+-+-+-+-+"
> >                                                     
> >                            
> > 
> > In Section 9.1 
> > 
> > add:
> > 
> > "      S(eparate)
> >                    - When the S-flag is set in a
> > PANA-Start-Request
> >                      message it indicates that PAA
> > is willing to offer
> >                      separate EAP authentication for
> > NAP and ISP.
> >                      When the S-flag is set in a
> > PANA-Start-Answer
> >                      message it indicates that PaC
> > accepts on
> >                      performing separate EAP
> > authentication 
> === message truncated ===
> 
> 
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com

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



From pana-admin@ietf.org  Tue Oct 21 12:22:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25245
	for <pana-archive@lists.ietf.org>; Tue, 21 Oct 2003 12:22:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABzGj-0007GP-HJ; Tue, 21 Oct 2003 12:22:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABzFy-00070L-OR
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 12:21:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25165
	for <pana@ietf.org>; Tue, 21 Oct 2003 12:21:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABzFx-0005cX-00
	for pana@ietf.org; Tue, 21 Oct 2003 12:21:13 -0400
Received: from web40012.mail.yahoo.com ([66.218.78.30])
	by ietf-mx with smtp (Exim 4.12)
	id 1ABzFw-0005c9-00
	for pana@ietf.org; Tue, 21 Oct 2003 12:21:12 -0400
Message-ID: <20031021162041.94504.qmail@web40012.mail.yahoo.com>
Received: from [47.234.0.52] by web40012.mail.yahoo.com via HTTP; Tue, 21 Oct 2003 09:20:41 PDT
Date: Tue, 21 Oct 2003 09:20:41 -0700 (PDT)
From: Reinaldo Penno <rapenno@yahoo.com>
Subject: Re: [Pana] issue25 revised text
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: pana@ietf.org
In-Reply-To: <20031021153924.GD5577@steelhead>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

okay,

I'm not the way it is today, this would be that
useful. Yes, it will take care of some cases that
carriers face, but will be one more barrier to PPPoE
migration.

In general, I would like to see PANA as an easy
migration from PPPoX, so people have a compelling
reason to change and see it's not a major hassle. I
know I've already suggested very basic and important
things like IP address allocation and people
disagreed, but it would make PANA's success much more
likely.

regards,

Reinaldo

--- Yoshihiro Ohba <yohba@tari.toshiba.com> wrote:
> Hi Reinaldo,
> 
> I think it would be better to discuss the issue
> step-by-step.  That is
> why I started from including provider identifier and
> name (and we have
> reached a rough consensus on it).  I would suggest
> creating a new
> issue to discuss whether more detailed service
> profile information
> should be added or not.
> 
> Yoshihiro Ohba
> 
> 
> On Tue, Oct 21, 2003 at 06:53:32AM -0700, Reinaldo
> Penno wrote:
> > Hi Yoshi,
> > 
> > I finally found comment to comment on this issue.
> In
> > PPPoE, the "Service-Profiles" tied to a specific
> ISP
> > are just names and descriptions. so, you can have
> even
> > *one* PPPoE server, offering several distinct
> services
> > such as "bandwidth 1024", "tunnelling", "video on
> > demand", etc, etc.
> > 
> > The same should apply to PANA.
> > 
> > The Service-Profiles in PPPoE are not just for
> > authentication. I mentioned in the first post that
> the
> > definition of the term was loose on purpose, and
> > that's where its power comes from. 
> > 
> > I'm not sure we can do this in this proposal. I'm
> not
> > sure after the IANA provider identifier we can
> convey
> > such information.
> > 
> > It seems we are trying to tie everything together
> for
> > the purposes of aithentication and in the process
> > distancing ourselves from the original meaning of
> the
> > field in PPPoE. If I'm wrong, please correct me.
> > 
> > The information contained in the packet should be
> (one
> > or more of) ISP + any services the ISP offers.
> > Something like
> > 
> > {ISP A}, {Gold, Silver, Bronze, Platinum}.
> > {ISP B}, {Video, Voice, VPN}
> > 
> > Can I do this with the current proposal?
> > 
> > thanks,
> > 
> > Reinaldo
> > 
> > 
> > 
> > 
> > 
> > 
> > --- Yoshihiro Ohba <yohba@tari.toshiba.com> wrote:
> > > In Section 4.2, change
> > > 
> > > From:
> > > 
> > > "  When a PaC receives the PANA-Start-Request
> > > message in response to
> > >    the PANA-PAA-Discover message, it responds
> with a
> > > PANA-Start-Answer
> > >    message. The PANA-Start-Answer message
> contains
> > > the initial sequence
> > >    numbers in the tseq and rseq fields of the
> PANA
> > > header, a copy of
> > >    the received Cookie as the PANA payload."
> > > 
> > > To:
> > > 
> > > "  PAA MAY enable NAP-ISP authentication
> separation
> > > by setting the
> > >    S-flag of the message header of the
> > > PANA-Start-Request.  Also, the
> > >    PANA-Start-Request MAY contain zero or one
> > > NAP-Information AVP and
> > >    zero or more ISP-Information AVPs to
> advertise
> > > the information on
> > >    the NAP and/or ISPs.
> > > 
> > >    When a PaC receives the PANA-Start-Request
> > > message in response to
> > >    the PANA-PAA-Discover message, it responds
> with a
> > > PANA-Start-Answer
> > >    message if it wishes to enter the
> authentication
> > > phase.  The
> > >    PANA-Start-Answer message contains the
> initial
> > > sequence numbers in
> > >    the tseq and rseq fields of the PANA header,
> a
> > > copy of the received
> > >    Cookie (if any) as the PANA payload.
> > > 
> > >    If the S-flag of the received
> PANA-Start-Request
> > > message is not
> > >    set, PaC MUST NOT set the S-flag in the
> > > PANA-Start-Answer message
> > >    sent back to the PAA.  In this case, PaC can
> > > indicate its choice of
> > >    ISP by including its ISP-Information AVP in
> the
> > > PANA-Start-Answer
> > >    message. AAA routing will be based on the ISP
> > > choice if an
> > >    ISP-Information AVP is specified in the
> > > PANA-Start-Answer message,
> > >    otherwise it will be based on EAP identifier.
> > > 
> > >    If the S-flag of the received
> PANA-Start-Request
> > > message is set,
> > >    PaC can indicate its desire to perform
> separate
> > > EAP authentication
> > >    for NAP and ISP by setting the S-flag in the
> > > PANA-Start-Answer
> > >    message. In this case, PaC can also indicate
> its
> > > choice of ISP by
> > >    including its ISP-Information AVP in the
> > > PANA-Start-Answer message.
> > >    AAA routing for NAP authentication will be
> based
> > > on the NAP.  AAA
> > >    routing for ISP authentication will be based
> on
> > > the ISP choice if
> > >    an ISP-Information AVP is specified in the
> > > PANA-Start-Answer
> > >    message, otherwise it will be based on EAP
> > > identifier."
> > > 
> > > In Section 4.3 change
> > > 
> > > from:
> > > 
> > > "  A single PANA session can enable more than
> one
> > > EAP authentication.
> > >    This is used to satisfy the separate NAP and
> ISP
> > > authentications
> > >    scenario.  Each EAP authentication is
> delineated
> > > from the subsequent
> > >    one.  The F-flag in the PANA header indicates
> if
> > > this was the final
> > >    authentication from sender's perspective.  If
> the
> > > PAA enables two
> > >    separate authentication, it should not set
> the
> > > F-flag in after the
> > >    first EAP method.  This indicates PAA's
> > > willingness to offer another
> > >    authentication method for NAP-ISP separation.
> 
> > > PaC can respond with
> > >    the F-flag unset, indicating PaC's
> willingness to
> > > go through a
> > >    second authentication method.  The PaC can
> > > optionally decline by
> > >    setting the F-flag, and this concludes the
> PANA
> > > authentication.  If
> > >    the PAA does not offer two levels of
> > > authentication, then it sets
> > >    the F-flag even at the end of first EAP
> exchange.
> > >  In that case the
> > >    PaC has no other option but to set the F-flag
> to
> > > mark the end of
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

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


From exim@www1.ietf.org  Tue Oct 21 12:22:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25260
	for <pana-archive@odin.ietf.org>; Tue, 21 Oct 2003 12:22:29 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABzGr-0007Ib-NP
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 12:22:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LGM99i028051
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 12:22:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABzGr-0007IM-JK
	for pana-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 12:22:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25238
	for <pana-web-archive@ietf.org>; Tue, 21 Oct 2003 12:21:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABzGq-0005dO-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 12:22:08 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABzGp-0005dL-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 12:22:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABzGj-0007GP-HJ; Tue, 21 Oct 2003 12:22:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABzFy-00070L-OR
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 12:21:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25165
	for <pana@ietf.org>; Tue, 21 Oct 2003 12:21:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABzFx-0005cX-00
	for pana@ietf.org; Tue, 21 Oct 2003 12:21:13 -0400
Received: from web40012.mail.yahoo.com ([66.218.78.30])
	by ietf-mx with smtp (Exim 4.12)
	id 1ABzFw-0005c9-00
	for pana@ietf.org; Tue, 21 Oct 2003 12:21:12 -0400
Message-ID: <20031021162041.94504.qmail@web40012.mail.yahoo.com>
Received: from [47.234.0.52] by web40012.mail.yahoo.com via HTTP; Tue, 21 Oct 2003 09:20:41 PDT
Date: Tue, 21 Oct 2003 09:20:41 -0700 (PDT)
From: Reinaldo Penno <rapenno@yahoo.com>
Subject: Re: [Pana] issue25 revised text
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: pana@ietf.org
In-Reply-To: <20031021153924.GD5577@steelhead>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

okay,

I'm not the way it is today, this would be that
useful. Yes, it will take care of some cases that
carriers face, but will be one more barrier to PPPoE
migration.

In general, I would like to see PANA as an easy
migration from PPPoX, so people have a compelling
reason to change and see it's not a major hassle. I
know I've already suggested very basic and important
things like IP address allocation and people
disagreed, but it would make PANA's success much more
likely.

regards,

Reinaldo

--- Yoshihiro Ohba <yohba@tari.toshiba.com> wrote:
> Hi Reinaldo,
> 
> I think it would be better to discuss the issue
> step-by-step.  That is
> why I started from including provider identifier and
> name (and we have
> reached a rough consensus on it).  I would suggest
> creating a new
> issue to discuss whether more detailed service
> profile information
> should be added or not.
> 
> Yoshihiro Ohba
> 
> 
> On Tue, Oct 21, 2003 at 06:53:32AM -0700, Reinaldo
> Penno wrote:
> > Hi Yoshi,
> > 
> > I finally found comment to comment on this issue.
> In
> > PPPoE, the "Service-Profiles" tied to a specific
> ISP
> > are just names and descriptions. so, you can have
> even
> > *one* PPPoE server, offering several distinct
> services
> > such as "bandwidth 1024", "tunnelling", "video on
> > demand", etc, etc.
> > 
> > The same should apply to PANA.
> > 
> > The Service-Profiles in PPPoE are not just for
> > authentication. I mentioned in the first post that
> the
> > definition of the term was loose on purpose, and
> > that's where its power comes from. 
> > 
> > I'm not sure we can do this in this proposal. I'm
> not
> > sure after the IANA provider identifier we can
> convey
> > such information.
> > 
> > It seems we are trying to tie everything together
> for
> > the purposes of aithentication and in the process
> > distancing ourselves from the original meaning of
> the
> > field in PPPoE. If I'm wrong, please correct me.
> > 
> > The information contained in the packet should be
> (one
> > or more of) ISP + any services the ISP offers.
> > Something like
> > 
> > {ISP A}, {Gold, Silver, Bronze, Platinum}.
> > {ISP B}, {Video, Voice, VPN}
> > 
> > Can I do this with the current proposal?
> > 
> > thanks,
> > 
> > Reinaldo
> > 
> > 
> > 
> > 
> > 
> > 
> > --- Yoshihiro Ohba <yohba@tari.toshiba.com> wrote:
> > > In Section 4.2, change
> > > 
> > > From:
> > > 
> > > "  When a PaC receives the PANA-Start-Request
> > > message in response to
> > >    the PANA-PAA-Discover message, it responds
> with a
> > > PANA-Start-Answer
> > >    message. The PANA-Start-Answer message
> contains
> > > the initial sequence
> > >    numbers in the tseq and rseq fields of the
> PANA
> > > header, a copy of
> > >    the received Cookie as the PANA payload."
> > > 
> > > To:
> > > 
> > > "  PAA MAY enable NAP-ISP authentication
> separation
> > > by setting the
> > >    S-flag of the message header of the
> > > PANA-Start-Request.  Also, the
> > >    PANA-Start-Request MAY contain zero or one
> > > NAP-Information AVP and
> > >    zero or more ISP-Information AVPs to
> advertise
> > > the information on
> > >    the NAP and/or ISPs.
> > > 
> > >    When a PaC receives the PANA-Start-Request
> > > message in response to
> > >    the PANA-PAA-Discover message, it responds
> with a
> > > PANA-Start-Answer
> > >    message if it wishes to enter the
> authentication
> > > phase.  The
> > >    PANA-Start-Answer message contains the
> initial
> > > sequence numbers in
> > >    the tseq and rseq fields of the PANA header,
> a
> > > copy of the received
> > >    Cookie (if any) as the PANA payload.
> > > 
> > >    If the S-flag of the received
> PANA-Start-Request
> > > message is not
> > >    set, PaC MUST NOT set the S-flag in the
> > > PANA-Start-Answer message
> > >    sent back to the PAA.  In this case, PaC can
> > > indicate its choice of
> > >    ISP by including its ISP-Information AVP in
> the
> > > PANA-Start-Answer
> > >    message. AAA routing will be based on the ISP
> > > choice if an
> > >    ISP-Information AVP is specified in the
> > > PANA-Start-Answer message,
> > >    otherwise it will be based on EAP identifier.
> > > 
> > >    If the S-flag of the received
> PANA-Start-Request
> > > message is set,
> > >    PaC can indicate its desire to perform
> separate
> > > EAP authentication
> > >    for NAP and ISP by setting the S-flag in the
> > > PANA-Start-Answer
> > >    message. In this case, PaC can also indicate
> its
> > > choice of ISP by
> > >    including its ISP-Information AVP in the
> > > PANA-Start-Answer message.
> > >    AAA routing for NAP authentication will be
> based
> > > on the NAP.  AAA
> > >    routing for ISP authentication will be based
> on
> > > the ISP choice if
> > >    an ISP-Information AVP is specified in the
> > > PANA-Start-Answer
> > >    message, otherwise it will be based on EAP
> > > identifier."
> > > 
> > > In Section 4.3 change
> > > 
> > > from:
> > > 
> > > "  A single PANA session can enable more than
> one
> > > EAP authentication.
> > >    This is used to satisfy the separate NAP and
> ISP
> > > authentications
> > >    scenario.  Each EAP authentication is
> delineated
> > > from the subsequent
> > >    one.  The F-flag in the PANA header indicates
> if
> > > this was the final
> > >    authentication from sender's perspective.  If
> the
> > > PAA enables two
> > >    separate authentication, it should not set
> the
> > > F-flag in after the
> > >    first EAP method.  This indicates PAA's
> > > willingness to offer another
> > >    authentication method for NAP-ISP separation.
> 
> > > PaC can respond with
> > >    the F-flag unset, indicating PaC's
> willingness to
> > > go through a
> > >    second authentication method.  The PaC can
> > > optionally decline by
> > >    setting the F-flag, and this concludes the
> PANA
> > > authentication.  If
> > >    the PAA does not offer two levels of
> > > authentication, then it sets
> > >    the F-flag even at the end of first EAP
> exchange.
> > >  In that case the
> > >    PaC has no other option but to set the F-flag
> to
> > > mark the end of
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

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



From pana-admin@ietf.org  Tue Oct 21 14:28:20 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29335
	for <pana-archive@lists.ietf.org>; Tue, 21 Oct 2003 14:28:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC1Ee-00019U-95; Tue, 21 Oct 2003 14:28:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC1Dm-0000sP-0g
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 14:27:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29286
	for <pana@ietf.org>; Tue, 21 Oct 2003 14:26:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC1Dj-0007Bn-00
	for pana@ietf.org; Tue, 21 Oct 2003 14:27:03 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC1Di-0007Bh-00
	for pana@ietf.org; Tue, 21 Oct 2003 14:27:02 -0400
Date: Tue, 21 Oct 2003 11:26:59 -0700
Subject: Re: [Pana] issue23 proposed text
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <pana@ietf.org>
Message-ID: <BBBAC883.AE44%alper@docomolabs-usa.com>
In-Reply-To: <20031021133722.GA5577@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> In section 9.2,
> 
> change:
> 
> "  AVP Code
>                  
>     The AVP Code, combined with the Vendor-Id field, identifies the
>     attribute uniquely. AVP numbers are allocated by IANA [IANAWEB]."
> 
> to:
> 
> "  AVP Code
>                  
>     The AVP Code, combined with the Vendor-Id field, identifies the
>     attribute uniquely. AVP numbers are allocated by IANA [IANAWEB].
>     PANA uses its own address space for this field."

Maybe we can explain this a bit by saying "PANA uses its own address space
for this field although some of the AVP formats are borrowed from Diameter
protocol."

Alper


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


From exim@www1.ietf.org  Tue Oct 21 14:28:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29350
	for <pana-archive@odin.ietf.org>; Tue, 21 Oct 2003 14:28:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC1Eg-0001BQ-Nb
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 14:28:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LIS2oc004542
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 14:28:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC1Eg-0001BB-HW
	for pana-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 14:28:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29326
	for <pana-web-archive@ietf.org>; Tue, 21 Oct 2003 14:27:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC1Ed-0007Cl-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 14:28:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC1Ed-0007Ci-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 14:27:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC1Ee-00019U-95; Tue, 21 Oct 2003 14:28:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC1Dm-0000sP-0g
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 14:27:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29286
	for <pana@ietf.org>; Tue, 21 Oct 2003 14:26:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC1Dj-0007Bn-00
	for pana@ietf.org; Tue, 21 Oct 2003 14:27:03 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC1Di-0007Bh-00
	for pana@ietf.org; Tue, 21 Oct 2003 14:27:02 -0400
Date: Tue, 21 Oct 2003 11:26:59 -0700
Subject: Re: [Pana] issue23 proposed text
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <pana@ietf.org>
Message-ID: <BBBAC883.AE44%alper@docomolabs-usa.com>
In-Reply-To: <20031021133722.GA5577@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> In section 9.2,
> 
> change:
> 
> "  AVP Code
>                  
>     The AVP Code, combined with the Vendor-Id field, identifies the
>     attribute uniquely. AVP numbers are allocated by IANA [IANAWEB]."
> 
> to:
> 
> "  AVP Code
>                  
>     The AVP Code, combined with the Vendor-Id field, identifies the
>     attribute uniquely. AVP numbers are allocated by IANA [IANAWEB].
>     PANA uses its own address space for this field."

Maybe we can explain this a bit by saying "PANA uses its own address space
for this field although some of the AVP formats are borrowed from Diameter
protocol."

Alper


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



From pana-admin@ietf.org  Tue Oct 21 19:08:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17308
	for <pana-archive@lists.ietf.org>; Tue, 21 Oct 2003 19:08:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC5bg-0002N5-Bx; Tue, 21 Oct 2003 19:08:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC5bE-0002Cd-L0
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 19:07:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17186
	for <pana@ietf.org>; Tue, 21 Oct 2003 19:07:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC5b6-0004Hc-00
	for pana@ietf.org; Tue, 21 Oct 2003 19:07:28 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC5b5-0004HY-00
	for pana@ietf.org; Tue, 21 Oct 2003 19:07:27 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9LN7MF1007503;
	Wed, 22 Oct 2003 08:07:22 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9LN7M31002512;
	Wed, 22 Oct 2003 08:07:22 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id JAA02511 ; Wed, 22 Oct 2003 08:07:22 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA23722; Wed, 22 Oct 2003 08:07:22 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA27905; Wed, 22 Oct 2003 08:07:21 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9LN7Lqv017359;
	Wed, 22 Oct 2003 08:07:21 +0900 (JST)
Received: from steelhead ([159.119.168.162]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN4001F8QW67W@tsbpo1.po.toshiba.co.jp>; Wed,
 22 Oct 2003 08:07:20 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AC5Yj-0002Sl-00; Tue, 21 Oct 2003 16:05:01 -0700
Date: Tue, 21 Oct 2003 16:05:01 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue23 proposed text
In-reply-to: <BBBAC883.AE44%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031021230501.GL5577@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031021133722.GA5577@steelhead>
 <BBBAC883.AE44%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Tue, Oct 21, 2003 at 11:26:59AM -0700, Alper Yegin wrote:
> > In section 9.2,
> > 
> > change:
> > 
> > "  AVP Code
> >                  
> >     The AVP Code, combined with the Vendor-Id field, identifies the
> >     attribute uniquely. AVP numbers are allocated by IANA [IANAWEB]."
> > 
> > to:
> > 
> > "  AVP Code
> >                  
> >     The AVP Code, combined with the Vendor-Id field, identifies the
> >     attribute uniquely. AVP numbers are allocated by IANA [IANAWEB].
> >     PANA uses its own address space for this field."
> 
> Maybe we can explain this a bit by saying "PANA uses its own address space
> for this field although some of the AVP formats are borrowed from Diameter
> protocol."

OK.

Yoshihiro Ohba

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

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


From exim@www1.ietf.org  Tue Oct 21 19:08:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17323
	for <pana-archive@odin.ietf.org>; Tue, 21 Oct 2003 19:08:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC5bl-0002Ol-HJ
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 19:08:11 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9LN89Zf009215
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 19:08:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC5bl-0002OY-D6
	for pana-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 19:08:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17282
	for <pana-web-archive@ietf.org>; Tue, 21 Oct 2003 19:07:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC5bi-0004JO-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 19:08:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC5bh-0004JL-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 19:08:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC5bg-0002N5-Bx; Tue, 21 Oct 2003 19:08:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC5bE-0002Cd-L0
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 19:07:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17186
	for <pana@ietf.org>; Tue, 21 Oct 2003 19:07:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC5b6-0004Hc-00
	for pana@ietf.org; Tue, 21 Oct 2003 19:07:28 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC5b5-0004HY-00
	for pana@ietf.org; Tue, 21 Oct 2003 19:07:27 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9LN7MF1007503;
	Wed, 22 Oct 2003 08:07:22 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9LN7M31002512;
	Wed, 22 Oct 2003 08:07:22 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id JAA02511 ; Wed, 22 Oct 2003 08:07:22 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id IAA23722; Wed, 22 Oct 2003 08:07:22 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id IAA27905; Wed, 22 Oct 2003 08:07:21 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9LN7Lqv017359;
	Wed, 22 Oct 2003 08:07:21 +0900 (JST)
Received: from steelhead ([159.119.168.162]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN4001F8QW67W@tsbpo1.po.toshiba.co.jp>; Wed,
 22 Oct 2003 08:07:20 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AC5Yj-0002Sl-00; Tue, 21 Oct 2003 16:05:01 -0700
Date: Tue, 21 Oct 2003 16:05:01 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] issue23 proposed text
In-reply-to: <BBBAC883.AE44%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031021230501.GL5577@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Alper Yegin <alper@docomolabs-usa.com>,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031021133722.GA5577@steelhead>
 <BBBAC883.AE44%alper@docomolabs-usa.com>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

On Tue, Oct 21, 2003 at 11:26:59AM -0700, Alper Yegin wrote:
> > In section 9.2,
> > 
> > change:
> > 
> > "  AVP Code
> >                  
> >     The AVP Code, combined with the Vendor-Id field, identifies the
> >     attribute uniquely. AVP numbers are allocated by IANA [IANAWEB]."
> > 
> > to:
> > 
> > "  AVP Code
> >                  
> >     The AVP Code, combined with the Vendor-Id field, identifies the
> >     attribute uniquely. AVP numbers are allocated by IANA [IANAWEB].
> >     PANA uses its own address space for this field."
> 
> Maybe we can explain this a bit by saying "PANA uses its own address space
> for this field although some of the AVP formats are borrowed from Diameter
> protocol."

OK.

Yoshihiro Ohba

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

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



From pana-admin@ietf.org  Tue Oct 21 20:01:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20573
	for <pana-archive@lists.ietf.org>; Tue, 21 Oct 2003 20:01:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC6Qx-0000Ag-57; Tue, 21 Oct 2003 20:01:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC6Qe-0008Un-8j
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 20:00:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20516
	for <pana@ietf.org>; Tue, 21 Oct 2003 20:00:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC6QX-0005Qs-00
	for pana@ietf.org; Tue, 21 Oct 2003 20:00:37 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC6QW-0005Qp-00
	for pana@ietf.org; Tue, 21 Oct 2003 20:00:36 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9M00ZF1000676;
	Wed, 22 Oct 2003 09:00:35 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9M00Z8e012694;
	Wed, 22 Oct 2003 09:00:35 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id KAA12692 ; Wed, 22 Oct 2003 09:00:35 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA21708; Wed, 22 Oct 2003 09:00:34 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA26536; Wed, 22 Oct 2003 09:00:33 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9M00Wqv005738;
	Wed, 22 Oct 2003 09:00:32 +0900 (JST)
Received: from steelhead ([159.119.168.162]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN4004UATCTS3@tsbpo1.po.toshiba.co.jp>; Wed,
 22 Oct 2003 09:00:31 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AC6P0-0002Yf-00; Tue, 21 Oct 2003 16:59:02 -0700
Date: Tue, 21 Oct 2003 16:59:02 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031021235902.GQ5577@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.4i
Subject: [Pana] issue25 revised text [second shot]
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>


I revised the text further as follows:

- F-flag was removed.  (Since we have introduced S-flag, F-flag would
not be needed any more.)
  
- Allow PAA to include NSP-Information AVP in PANA-Auth-Request for
NAP authentication to unambiguously distinguish NAP authentication and
ISP authentication in the authentication phase, even when PaC did not
specify ISP-Information AVP during discovery and initial handshake
phase.

- Provider-Identifier AVP becomes optional in NAP-Information AVP so
that small NAPs do not need to obtain IANA-assigned
Provider-Identifier.

----
In Section 4.2, change

From:

"  When a PaC receives the PANA-Start-Request message in response to
   the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
   message. The PANA-Start-Answer message contains the initial sequence
   numbers in the tseq and rseq fields of the PANA header, a copy of
   the received Cookie as the PANA payload."

To:

"  PAA MAY enable NAP-ISP authentication separation by setting the
   S-flag of the message header of the PANA-Start-Request.  Also, the
   PANA-Start-Request MAY contain zero or one NAP-Information AVP and
   zero or more ISP-Information AVPs to advertise the information on
   the NAP and/or ISPs.

   When a PaC receives the PANA-Start-Request message in response to
   the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
   message if it wishes to enter the authentication phase.  The
   PANA-Start-Answer message contains the initial sequence numbers in
   the tseq and rseq fields of the PANA header, a copy of the received
   Cookie (if any) as the PANA payload.

   If the S-flag of the received PANA-Start-Request message is not
   set, PaC MUST NOT set the S-flag in the PANA-Start-Answer message
   sent back to the PAA.  In this case, PaC can indicate its choice of
   ISP by including its ISP-Information AVP in the PANA-Start-Answer
   message. AAA routing will be based on the ISP choice if an
   ISP-Information AVP is specified in the PANA-Start-Answer message,
   otherwise it will be based on EAP identifier.

   If the S-flag of the received PANA-Start-Request message is set,
   PaC can indicate its desire to perform separate EAP authentication
   for NAP and ISP by setting the S-flag in the PANA-Start-Answer
   message. In this case, PaC can also indicate its choice of ISP by
   including its ISP-Information AVP in the PANA-Start-Answer message.
   AAA routing for NAP authentication will be based on the NAP.  AAA
   routing for ISP authentication will be based on the ISP choice if
   an ISP-Information AVP is specified in the PANA-Start-Answer
   message, otherwise it will be based on EAP identifier."

In Section 4.3 change

from:

"  A single PANA session can enable more than one EAP authentication.
   This is used to satisfy the separate NAP and ISP authentications
   scenario.  Each EAP authentication is delineated from the subsequent
   one.  The F-flag in the PANA header indicates if this was the final
   authentication from sender's perspective.  If the PAA enables two
   separate authentication, it should not set the F-flag in after the
   first EAP method.  This indicates PAA's willingness to offer another
   authentication method for NAP-ISP separation.  PaC can respond with
   the F-flag unset, indicating PaC's willingness to go through a
   second authentication method.  The PaC can optionally decline by
   setting the F-flag, and this concludes the PANA authentication.  If
   the PAA does not offer two levels of authentication, then it sets
   the F-flag even at the end of first EAP exchange.  In that case the
   PaC has no other option but to set the F-flag to mark the end of
   PANA authentication."

to:

"  When PaC and PAA negotiated during the discovery and initial
   handshake phase to perform separate NAP and ISP authentications in
   a single PANA session, the PAA determines the execution order of NAP
   authentication and ISP authentication.  In this case, the PAA can
   indicate which EAP authentication is currently occurring by
   including a NAP-Information or an ISP-Information AVP of the
   corresponding EAP authentication in PANA-Auth-Request message. In
   the case where the PaC agreed to perform separate authentications
   but did not specify its ISP choice in PANA-Start-Answer message,
   the PAA MUST include its NAP-Information AVP in PANA-Auth-Request
   message when it performs NAP authentication so that the PaC can
   always distinguish ISP authentication from NAP authentication.  The
   PAA MAY stop including a NAP-Information or an ISP-Information AVP
   once it receives the first PANA-Auth-Answer message of the current
   EAP authentication."


In Figures 4 and 8, 

remove "// F-flag set".



In Section 9.1 change

from:

"  Flags
                                                                                
     The Flags field is eight bits.  The following bits are assigned:
                                                                                
     0 1 2 3 4 5 6 7
    +-+-+-+-+-+-+-+-+
    |R r r r F r r r|
    +-+-+-+-+-+-+-+-+"
                                                                                
To:
                                                                                
"  Flags
                                                                                
     The Flags field is eight bits.  The following bits are assigned:
                                                                                
     0 1 2 3 4 5 6 7
    +-+-+-+-+-+-+-+-+
    |R r r r S r r r|
    +-+-+-+-+-+-+-+-+"
                                                                                

In Section 9.1 

delete:

"      F(inish)
                   - F-flag in the PANA header indicates if this  was
                     the final authentication from sender's
                     perspective.  If PAA enables two separate
                     authentication, it should not set F-flag in the
                     PANA-Bind-Request message after the first EAP
                     method."
                                                                            

add:

"      S(eparate)
                   - When the S-flag is set in a PANA-Start-Request
                     message it indicates that PAA is willing to offer
                     separate EAP authentication for NAP and ISP.
                     When the S-flag is set in a PANA-Start-Answer
                     message it indicates that PaC accepts on
                     performing separate EAP authentication for NAP
                     and ISP."
 

In Section 9.3.3, change

from:

"
      PANA-Start-Request ::= < PANA-Header: 2, REQ >
                    [ Cookie ]
                  * [ AVP ]
"

to:

"
      PANA-Start-Request ::= < PANA-Header: 2, REQ >
                    [ Cookie ]
		    [ NAP-Information ]
                  * [ ISP-Information ]
                  * [ AVP ]
"


In Section 9.3.4, change

from:

"     PANA-Start-Answer ::= < PANA-Header: 3 >
                    [ Cookie ]
                  * [ AVP ]"

to:

"     PANA-Start-Answer ::= < PANA-Header: 3 >
                    [ Cookie ]
                    [ ISP-Information ]
                  * [ AVP ]"


In section 9.3.5, change

from:

"     PANA-Auth-Request ::= < PANA-Header: 4, REQ >
                    < Session-Id >
                    < EAP-Payload >
                  * [ AVP ]
                0*1 < MAC >"

to:
                                                                            
"     PANA-Auth-Request ::= < PANA-Header: 4, REQ >
                    < Session-Id >
                    < EAP-Payload >
                0*1 [ NAP-Information ]
                0*1 [ ISP-Information ]
                  * [ AVP ]
                0*1 < MAC >

      (Both NAP-Information and ISP-Information MUST NOT be included
       at the same time)"


Add the following sections:

"9.4.9 NAP-Information AVP

The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
contains zero or one globally unique identifier of the NAP in a
Provider-Identifier AVP and one enterprise name of the NAP in a
Provider-Name AVP.  Its Data field has the following ABNF grammar:

      NAP-Information ::= < AVP Header: 1029 >
                        0*1{ Provider-Identifier }
                           { Provider-Name }
                         * [ AVP ]


9.4.10 ISP-Information AVP

The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
contains one globally unique identifier of the ISP in a
Provider-Identifier AVP and one enterprise name of the ISP in a
Provider-Name AVP.  Its Data field has the following ABNF grammar:

      ISP-Information ::= < AVP Header: 1030 >
                           { Provider-Identifier }
                           { Provider-Name }
                         * [ AVP ]


9.4.11 Provider-Identifier AVP 

The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
and contains an IANA assigned "SMI Network Management Private
Enterprise Codes" [IANAWEB] value, encoded in network byte order.
 

9.4.12 Provider-Name AVP 

The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
contains the UTF8-encoded name of the provider."


----
Yoshihiro Ohba

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


From exim@www1.ietf.org  Tue Oct 21 20:01:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20588
	for <pana-archive@odin.ietf.org>; Tue, 21 Oct 2003 20:01:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC6R0-0000Cr-1k
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 20:01:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9M015Pe000784
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 20:01:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC6Qy-0000CI-FG
	for pana-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 20:01:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20549
	for <pana-web-archive@ietf.org>; Tue, 21 Oct 2003 20:00:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC6Qw-0005RU-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 20:01:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC6Qw-0005RR-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 20:01:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC6Qx-0000Ag-57; Tue, 21 Oct 2003 20:01:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC6Qe-0008Un-8j
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 20:00:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20516
	for <pana@ietf.org>; Tue, 21 Oct 2003 20:00:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC6QX-0005Qs-00
	for pana@ietf.org; Tue, 21 Oct 2003 20:00:37 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC6QW-0005Qp-00
	for pana@ietf.org; Tue, 21 Oct 2003 20:00:36 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9M00ZF1000676;
	Wed, 22 Oct 2003 09:00:35 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9M00Z8e012694;
	Wed, 22 Oct 2003 09:00:35 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id KAA12692 ; Wed, 22 Oct 2003 09:00:35 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA21708; Wed, 22 Oct 2003 09:00:34 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA26536; Wed, 22 Oct 2003 09:00:33 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9M00Wqv005738;
	Wed, 22 Oct 2003 09:00:32 +0900 (JST)
Received: from steelhead ([159.119.168.162]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN4004UATCTS3@tsbpo1.po.toshiba.co.jp>; Wed,
 22 Oct 2003 09:00:31 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AC6P0-0002Yf-00; Tue, 21 Oct 2003 16:59:02 -0700
Date: Tue, 21 Oct 2003 16:59:02 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031021235902.GQ5577@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.4i
Subject: [Pana] issue25 revised text [second shot]
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>


I revised the text further as follows:

- F-flag was removed.  (Since we have introduced S-flag, F-flag would
not be needed any more.)
  
- Allow PAA to include NSP-Information AVP in PANA-Auth-Request for
NAP authentication to unambiguously distinguish NAP authentication and
ISP authentication in the authentication phase, even when PaC did not
specify ISP-Information AVP during discovery and initial handshake
phase.

- Provider-Identifier AVP becomes optional in NAP-Information AVP so
that small NAPs do not need to obtain IANA-assigned
Provider-Identifier.

----
In Section 4.2, change

From:

"  When a PaC receives the PANA-Start-Request message in response to
   the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
   message. The PANA-Start-Answer message contains the initial sequence
   numbers in the tseq and rseq fields of the PANA header, a copy of
   the received Cookie as the PANA payload."

To:

"  PAA MAY enable NAP-ISP authentication separation by setting the
   S-flag of the message header of the PANA-Start-Request.  Also, the
   PANA-Start-Request MAY contain zero or one NAP-Information AVP and
   zero or more ISP-Information AVPs to advertise the information on
   the NAP and/or ISPs.

   When a PaC receives the PANA-Start-Request message in response to
   the PANA-PAA-Discover message, it responds with a PANA-Start-Answer
   message if it wishes to enter the authentication phase.  The
   PANA-Start-Answer message contains the initial sequence numbers in
   the tseq and rseq fields of the PANA header, a copy of the received
   Cookie (if any) as the PANA payload.

   If the S-flag of the received PANA-Start-Request message is not
   set, PaC MUST NOT set the S-flag in the PANA-Start-Answer message
   sent back to the PAA.  In this case, PaC can indicate its choice of
   ISP by including its ISP-Information AVP in the PANA-Start-Answer
   message. AAA routing will be based on the ISP choice if an
   ISP-Information AVP is specified in the PANA-Start-Answer message,
   otherwise it will be based on EAP identifier.

   If the S-flag of the received PANA-Start-Request message is set,
   PaC can indicate its desire to perform separate EAP authentication
   for NAP and ISP by setting the S-flag in the PANA-Start-Answer
   message. In this case, PaC can also indicate its choice of ISP by
   including its ISP-Information AVP in the PANA-Start-Answer message.
   AAA routing for NAP authentication will be based on the NAP.  AAA
   routing for ISP authentication will be based on the ISP choice if
   an ISP-Information AVP is specified in the PANA-Start-Answer
   message, otherwise it will be based on EAP identifier."

In Section 4.3 change

from:

"  A single PANA session can enable more than one EAP authentication.
   This is used to satisfy the separate NAP and ISP authentications
   scenario.  Each EAP authentication is delineated from the subsequent
   one.  The F-flag in the PANA header indicates if this was the final
   authentication from sender's perspective.  If the PAA enables two
   separate authentication, it should not set the F-flag in after the
   first EAP method.  This indicates PAA's willingness to offer another
   authentication method for NAP-ISP separation.  PaC can respond with
   the F-flag unset, indicating PaC's willingness to go through a
   second authentication method.  The PaC can optionally decline by
   setting the F-flag, and this concludes the PANA authentication.  If
   the PAA does not offer two levels of authentication, then it sets
   the F-flag even at the end of first EAP exchange.  In that case the
   PaC has no other option but to set the F-flag to mark the end of
   PANA authentication."

to:

"  When PaC and PAA negotiated during the discovery and initial
   handshake phase to perform separate NAP and ISP authentications in
   a single PANA session, the PAA determines the execution order of NAP
   authentication and ISP authentication.  In this case, the PAA can
   indicate which EAP authentication is currently occurring by
   including a NAP-Information or an ISP-Information AVP of the
   corresponding EAP authentication in PANA-Auth-Request message. In
   the case where the PaC agreed to perform separate authentications
   but did not specify its ISP choice in PANA-Start-Answer message,
   the PAA MUST include its NAP-Information AVP in PANA-Auth-Request
   message when it performs NAP authentication so that the PaC can
   always distinguish ISP authentication from NAP authentication.  The
   PAA MAY stop including a NAP-Information or an ISP-Information AVP
   once it receives the first PANA-Auth-Answer message of the current
   EAP authentication."


In Figures 4 and 8, 

remove "// F-flag set".



In Section 9.1 change

from:

"  Flags
                                                                                
     The Flags field is eight bits.  The following bits are assigned:
                                                                                
     0 1 2 3 4 5 6 7
    +-+-+-+-+-+-+-+-+
    |R r r r F r r r|
    +-+-+-+-+-+-+-+-+"
                                                                                
To:
                                                                                
"  Flags
                                                                                
     The Flags field is eight bits.  The following bits are assigned:
                                                                                
     0 1 2 3 4 5 6 7
    +-+-+-+-+-+-+-+-+
    |R r r r S r r r|
    +-+-+-+-+-+-+-+-+"
                                                                                

In Section 9.1 

delete:

"      F(inish)
                   - F-flag in the PANA header indicates if this  was
                     the final authentication from sender's
                     perspective.  If PAA enables two separate
                     authentication, it should not set F-flag in the
                     PANA-Bind-Request message after the first EAP
                     method."
                                                                            

add:

"      S(eparate)
                   - When the S-flag is set in a PANA-Start-Request
                     message it indicates that PAA is willing to offer
                     separate EAP authentication for NAP and ISP.
                     When the S-flag is set in a PANA-Start-Answer
                     message it indicates that PaC accepts on
                     performing separate EAP authentication for NAP
                     and ISP."
 

In Section 9.3.3, change

from:

"
      PANA-Start-Request ::= < PANA-Header: 2, REQ >
                    [ Cookie ]
                  * [ AVP ]
"

to:

"
      PANA-Start-Request ::= < PANA-Header: 2, REQ >
                    [ Cookie ]
		    [ NAP-Information ]
                  * [ ISP-Information ]
                  * [ AVP ]
"


In Section 9.3.4, change

from:

"     PANA-Start-Answer ::= < PANA-Header: 3 >
                    [ Cookie ]
                  * [ AVP ]"

to:

"     PANA-Start-Answer ::= < PANA-Header: 3 >
                    [ Cookie ]
                    [ ISP-Information ]
                  * [ AVP ]"


In section 9.3.5, change

from:

"     PANA-Auth-Request ::= < PANA-Header: 4, REQ >
                    < Session-Id >
                    < EAP-Payload >
                  * [ AVP ]
                0*1 < MAC >"

to:
                                                                            
"     PANA-Auth-Request ::= < PANA-Header: 4, REQ >
                    < Session-Id >
                    < EAP-Payload >
                0*1 [ NAP-Information ]
                0*1 [ ISP-Information ]
                  * [ AVP ]
                0*1 < MAC >

      (Both NAP-Information and ISP-Information MUST NOT be included
       at the same time)"


Add the following sections:

"9.4.9 NAP-Information AVP

The NAP-Information AVP (AVP Code: 1029) is of type Grouped, and
contains zero or one globally unique identifier of the NAP in a
Provider-Identifier AVP and one enterprise name of the NAP in a
Provider-Name AVP.  Its Data field has the following ABNF grammar:

      NAP-Information ::= < AVP Header: 1029 >
                        0*1{ Provider-Identifier }
                           { Provider-Name }
                         * [ AVP ]


9.4.10 ISP-Information AVP

The ISP-Information AVP (AVP Code: 1030) is of type Grouped, and
contains one globally unique identifier of the ISP in a
Provider-Identifier AVP and one enterprise name of the ISP in a
Provider-Name AVP.  Its Data field has the following ABNF grammar:

      ISP-Information ::= < AVP Header: 1030 >
                           { Provider-Identifier }
                           { Provider-Name }
                         * [ AVP ]


9.4.11 Provider-Identifier AVP 

The Provider-Identifier AVP (AVP Code: 1031) is of type Unsigned32,
and contains an IANA assigned "SMI Network Management Private
Enterprise Codes" [IANAWEB] value, encoded in network byte order.
 

9.4.12 Provider-Name AVP 

The Provider-Name AVP (AVP Code: 1032) is of type UTF8String, and
contains the UTF8-encoded name of the provider."


----
Yoshihiro Ohba

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



From pana-admin@ietf.org  Tue Oct 21 21:58:20 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23385
	for <pana-archive@lists.ietf.org>; Tue, 21 Oct 2003 21:58:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC8G8-0002Gx-Qp; Tue, 21 Oct 2003 21:58:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC8Fg-000236-0B
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 21:57:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23351
	for <pana@ietf.org>; Tue, 21 Oct 2003 21:57:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC8Fc-0006NO-00
	for pana@ietf.org; Tue, 21 Oct 2003 21:57:28 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC8Fc-0006NL-00
	for pana@ietf.org; Tue, 21 Oct 2003 21:57:28 -0400
Date: Tue, 21 Oct 2003 18:57:24 -0700
Subject: Re: [Pana] issue25 revised text [second shot]
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <pana@ietf.org>
Message-ID: <BBBB3214.AF01%alper@docomolabs-usa.com>
In-Reply-To: <20031021235902.GQ5577@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Yoshihiro,

> "  When PaC and PAA negotiated during the discovery and initial
>  handshake phase to perform separate NAP and ISP authentications in
>  a single PANA session, the PAA determines the execution order of NAP
>  authentication and ISP authentication.  In this case, the PAA can
>  indicate which EAP authentication is currently occurring by
>  including a NAP-Information or an ISP-Information AVP of the
>  corresponding EAP authentication in PANA-Auth-Request message. In
.... "in the first PANA-Auth-Request message sent to PaC"

>  the case where the PaC agreed to perform separate authentications
>  but did not specify its ISP choice in PANA-Start-Answer message,
>  the PAA MUST include its NAP-Information AVP in PANA-Auth-Request
>  message when it performs NAP authentication
... "and not include any service provider information AVP when it performs
ISP authentication" ...

> so that the PaC can
>  always distinguish ISP authentication from NAP authentication.  The
>  PAA MAY stop including a NAP-Information or an ISP-Information AVP
>  once it receives the first PANA-Auth-Answer message of the current
>  EAP authentication."

I think we can make this MAY a SHOULD. Once the authentication type is
agreed, I cannot think of why it should be exchanged again.

Btw, we can also make the Provider-identifier optional for the ISPs.

And finally, we should also add these new AVPs to the AVP Occurrence Table.

Alper



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


From exim@www1.ietf.org  Tue Oct 21 21:58:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23400
	for <pana-archive@odin.ietf.org>; Tue, 21 Oct 2003 21:58:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC8GA-0002Iu-KX
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 21:58:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9M1w2TG008850
	for pana-archive@odin.ietf.org; Tue, 21 Oct 2003 21:58:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC8GA-0002IW-EZ
	for pana-web-archive@optimus.ietf.org; Tue, 21 Oct 2003 21:58:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23371
	for <pana-web-archive@ietf.org>; Tue, 21 Oct 2003 21:57:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC8G7-0006Nv-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 21:57:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC8G7-0006Ns-00
	for pana-web-archive@ietf.org; Tue, 21 Oct 2003 21:57:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC8G8-0002Gx-Qp; Tue, 21 Oct 2003 21:58:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AC8Fg-000236-0B
	for pana@optimus.ietf.org; Tue, 21 Oct 2003 21:57:32 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23351
	for <pana@ietf.org>; Tue, 21 Oct 2003 21:57:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC8Fc-0006NO-00
	for pana@ietf.org; Tue, 21 Oct 2003 21:57:28 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AC8Fc-0006NL-00
	for pana@ietf.org; Tue, 21 Oct 2003 21:57:28 -0400
Date: Tue, 21 Oct 2003 18:57:24 -0700
Subject: Re: [Pana] issue25 revised text [second shot]
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <pana@ietf.org>
Message-ID: <BBBB3214.AF01%alper@docomolabs-usa.com>
In-Reply-To: <20031021235902.GQ5577@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yoshihiro,

> "  When PaC and PAA negotiated during the discovery and initial
>  handshake phase to perform separate NAP and ISP authentications in
>  a single PANA session, the PAA determines the execution order of NAP
>  authentication and ISP authentication.  In this case, the PAA can
>  indicate which EAP authentication is currently occurring by
>  including a NAP-Information or an ISP-Information AVP of the
>  corresponding EAP authentication in PANA-Auth-Request message. In
.... "in the first PANA-Auth-Request message sent to PaC"

>  the case where the PaC agreed to perform separate authentications
>  but did not specify its ISP choice in PANA-Start-Answer message,
>  the PAA MUST include its NAP-Information AVP in PANA-Auth-Request
>  message when it performs NAP authentication
... "and not include any service provider information AVP when it performs
ISP authentication" ...

> so that the PaC can
>  always distinguish ISP authentication from NAP authentication.  The
>  PAA MAY stop including a NAP-Information or an ISP-Information AVP
>  once it receives the first PANA-Auth-Answer message of the current
>  EAP authentication."

I think we can make this MAY a SHOULD. Once the authentication type is
agreed, I cannot think of why it should be exchanged again.

Btw, we can also make the Provider-identifier optional for the ISPs.

And finally, we should also add these new AVPs to the AVP Occurrence Table.

Alper



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



From pana-admin@ietf.org  Wed Oct 22 01:02:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27661
	for <pana-archive@lists.ietf.org>; Wed, 22 Oct 2003 01:02:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACB8D-000248-CE; Wed, 22 Oct 2003 01:02:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACB7X-0001tJ-IM
	for pana@optimus.ietf.org; Wed, 22 Oct 2003 01:01:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27633
	for <pana@ietf.org>; Wed, 22 Oct 2003 01:01:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACB7U-00004I-00
	for pana@ietf.org; Wed, 22 Oct 2003 01:01:16 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACB7T-00004E-00
	for pana@ietf.org; Wed, 22 Oct 2003 01:01:15 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9M51DF1021327;
	Wed, 22 Oct 2003 14:01:13 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9M51DtV011450;
	Wed, 22 Oct 2003 14:01:13 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id QAA11446 ; Wed, 22 Oct 2003 14:01:13 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id OAA05950; Wed, 22 Oct 2003 14:01:12 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id OAA04689; Wed, 22 Oct 2003 14:00:41 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9M50eqv005895;
	Wed, 22 Oct 2003 14:00:40 +0900 (JST)
Received: from steelhead ([159.119.168.62]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN5003N9792BN@tsbpo1.po.toshiba.co.jp>; Wed,
 22 Oct 2003 14:00:40 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ACB5P-0002sY-00; Tue, 21 Oct 2003 21:59:07 -0700
Date: Tue, 21 Oct 2003 21:59:07 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031022045907.GS5577@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.4i
Subject: [Pana] draft-ietf-pana-pana-02e
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

The latest snapshot has been updated to 02e and is available at
http://www.toshiba.com/tari/pana/pana-spec.html.

If there is no additional comments, I'll submit the snapshot as
draft-ietf-pana-pana-02.txt (after removing "Editorial Note:" tags).


Yoshihiro Ohba



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


From exim@www1.ietf.org  Wed Oct 22 01:02:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27676
	for <pana-archive@odin.ietf.org>; Wed, 22 Oct 2003 01:02:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACB8G-00026G-OV
	for pana-archive@odin.ietf.org; Wed, 22 Oct 2003 01:02:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9M524Qs008066
	for pana-archive@odin.ietf.org; Wed, 22 Oct 2003 01:02:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACB8G-000261-Jw
	for pana-web-archive@optimus.ietf.org; Wed, 22 Oct 2003 01:02:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27657
	for <pana-web-archive@ietf.org>; Wed, 22 Oct 2003 01:01:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACB8D-00004i-00
	for pana-web-archive@ietf.org; Wed, 22 Oct 2003 01:02:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACB8D-00004f-00
	for pana-web-archive@ietf.org; Wed, 22 Oct 2003 01:02:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACB8D-000248-CE; Wed, 22 Oct 2003 01:02:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACB7X-0001tJ-IM
	for pana@optimus.ietf.org; Wed, 22 Oct 2003 01:01:19 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27633
	for <pana@ietf.org>; Wed, 22 Oct 2003 01:01:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACB7U-00004I-00
	for pana@ietf.org; Wed, 22 Oct 2003 01:01:16 -0400
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACB7T-00004E-00
	for pana@ietf.org; Wed, 22 Oct 2003 01:01:15 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9M51DF1021327;
	Wed, 22 Oct 2003 14:01:13 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9M51DtV011450;
	Wed, 22 Oct 2003 14:01:13 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id QAA11446 ; Wed, 22 Oct 2003 14:01:13 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id OAA05950; Wed, 22 Oct 2003 14:01:12 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id OAA04689; Wed, 22 Oct 2003 14:00:41 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9M50eqv005895;
	Wed, 22 Oct 2003 14:00:40 +0900 (JST)
Received: from steelhead ([159.119.168.62]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HN5003N9792BN@tsbpo1.po.toshiba.co.jp>; Wed,
 22 Oct 2003 14:00:40 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ACB5P-0002sY-00; Tue, 21 Oct 2003 21:59:07 -0700
Date: Tue, 21 Oct 2003 21:59:07 -0700
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031022045907.GS5577@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.4i
Subject: [Pana] draft-ietf-pana-pana-02e
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

The latest snapshot has been updated to 02e and is available at
http://www.toshiba.com/tari/pana/pana-spec.html.

If there is no additional comments, I'll submit the snapshot as
draft-ietf-pana-pana-02.txt (after removing "Editorial Note:" tags).


Yoshihiro Ohba



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



From pana-admin@ietf.org  Thu Oct 23 06:00:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10879
	for <pana-archive@lists.ietf.org>; Thu, 23 Oct 2003 06:00:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACcGA-0000h0-6A; Thu, 23 Oct 2003 06:00:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACcG2-0000fB-RW
	for pana@optimus.ietf.org; Thu, 23 Oct 2003 05:59:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10844
	for <pana@ietf.org>; Thu, 23 Oct 2003 05:59:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACcFy-0004ai-00
	for pana@ietf.org; Thu, 23 Oct 2003 05:59:50 -0400
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACcFx-0004ae-00
	for pana@ietf.org; Thu, 23 Oct 2003 05:59:50 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h9N9xnc12817;
	Thu, 23 Oct 2003 11:59:49 +0200 (MEST)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id h9N9xmd10850;
	Thu, 23 Oct 2003 11:59:48 +0200 (MEST)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19)
	id <V3ZRCLAS>; Thu, 23 Oct 2003 11:59:37 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC033C@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Dan.Forsberg@nokia.com'" <Dan.Forsberg@nokia.com>, pana@ietf.org
Subject: RE: [Pana] [issue32] PANA Security considerations
Date: Thu, 23 Oct 2003 11:59:42 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi dan, 
hi alper, 

thanks for talking a look at the security consideration section. 
please see my comments inline:

> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> 
> From/through Alper Yegin:
> -------------------------
> 
> I have some editorial and technical comments on the security
> considerations section of the current PANA draft.
> 
> - a) Discovery message exchange
> ...
>    Since PAA and PaC are one IP hop away from each other, 
> PANA messages
>    can be filtered whenever messages arrive at interfaces where they
>    are not expected.
> 
> We should expand on this. Proposed addition "For example, EP may drop
> PANA-Start-Request messages when they are received from access side of
> the network where only PaCs can connect."

this is true for the current draft. however, adding the functionality
described in issue
12 this is not possible anymore. 


> 
> - b) EAP over PANA message exchange
> 
> Change:
> 
>    Hence an 
>    adversary can both eavesdrop the EAP messages and is also able to
>    inject arbitrary messages which might confuse both the PaC and the
>    PAA. 
> 
> To:
> 
>    Hence an 
>    adversary can both eavesdrop the EAP messages and is also able to
>    inject arbitrary messages which might confuse both the EAP 
> peer on PaC
>    and the EAP authenticator or the authentication server on the PAA.
> 
ok. 


> - c) PANA SA establishment
> 
> "subsection (c)" -> "subsection (d)"
> 
> "Integrity Object" -> "MAC AVP"
> 
> The session keys (one for each direction) used for this 
> object has to be
> provided by the EAP method.
> 
> We don't really require that the session keys are unidirectional.

i agree with you (since the 4-way handshake described in ieee 802.11i) does
not use separate keys for each direction either. 

however, we have to insure that reflection attacks are not possible. we have
to add some text on this issue somewhere. 

> 
> "per-default" -> "by default"
> 
> To select the security association for signaling message 
> protection the
> Session ID.
> 
> This sentence seems unfinished.

that's more than true. 

how about: 
"To select the security association for signaling message protection the
Session 
ID is used."



> 
> "looses" -> "loses"
> 
>    The lifetime of the PANA SA has to be bound to the refresh interval
>    with an additional tolerance period. To provide fast re-
>    authentication a separate security association (e.g. one stored at
>    the local AAA server) should be used. By fast re-authentication we
>    mean a new PANA protocol execution which does not involve 
> the entire
>    AAA communication. The ability to trigger such a protocol execution
>    depends on the given EAP method and on the policy of the local
>    network requesting authentication.
> 
> This paragraph is talking about couple of things. I suggest 
> we don't get
> into EAP-based fast reauth schemes in here (after all it should be all
> transparent to PANA). Instead we can say this:
> 
>    The lifetime of the PANA SA has to be bound to the refresh interval
>    with an additional tolerance period. Unless PANA state is 
> updated by
>    executing EAP authentication, PANA SA is removed when the current
>    session lifetime expires.

ok - sounds like a good idea to keep these things separate. 

>   
> g) Triggering a data protection protocol
> 
>    Furthermore, a derived session key might help to create the
>    pre-requisites for network layer protection (for example IPsec).
> 
> Let's add reference to PANA-IPsec draft here.

ok. 

> 
> h) Periodic refresh messages
> 
>    If network 
>    access authentication as part of PANA is executed only at the
>    beginning then an adversary can gain advantage of the installed
>    packet filters to submit and receive data packets.
> 
> This is not accurate. Because, one would either rely on physical
> security, or use crypto-based per-packet protection to prevent this
> possibility.

you are right. we should be more precise here. 

how about: 

If network access authentication as part of PANA is executed only at the
beginning then an adversary can gain advantage of the installed packet
filters to submit and receive data packets unless physical layer or
crypto-based per-packet protection is provided. 


> 
>    Different procedures can be used for disconnect indication. PANA
>    cannot assume link layer disconnect indication. Hence this
>    functionality has to be provided at a higher layer. With this
>    version of the draft we suggest to apply the soft-state principle
>    found at other protocols (such as RSVP). Soft-state means that
>    session state is kept alive as long as refresh messages refresh the
>    state. If no new refresh messages are provided then the state
>    automatically times out and resources are released. This process
>    includes stopping accounting procedures.
>     
>    Based on the different environments where PANA could be used it is
>    difficult to fix a refresh interval. Hence a default refresh
>    interval of 30 seconds is suggested. Additionally there is the
>    possibility to negotiation this interval once the PANA security
>    association is established. A policy at the PAA and the PaC would
>    ensure that the refresh interval is selected with a value which is
>    either too high or too low. There is certainly a tradeoff between
>    the refresh interval and the bandwidth consumption. To reduce the
>    bandwidth consumption a small PANA message consisting only of a
>    session identifier and the Integrity object is used. The session
>    identifier refers to the state that has to be refreshed. Some
>    environments do not need PANA refresh messages to detect orphan
>    states. For these environments the refresh interval should 
> be set to
>    zero which effectively disables the usage of refresh messages. In
>    case of IPsec protection a dead-peer mechanism can be used 
> to detect
>    inactivity (see [HBR03]).
>     
>    Refresh messages are sent from the PaC to the PAA.
> 
> This text is not aligned with the latest discussions. I presume it is
> referring to PANA-reauth as the refresh message... but we don't really
> suggest using periodic re-auth messages in the specification. There is
> only a PANA session lifetime, and that is not negotiated. We had a
> lengthy discussion on that.

true. this is old text. 

ciao
hannes

> 
> 
> ----------
> category: Technical
> document: draft-ietf-pana-pana-xx.txt
> messages: 94
> nosy: dforsber
> priority: Must Fix
> status: No Discussion
> title: PANA Security considerations
> ________________________________________________
> PANA Issues <pana_issues@danforsberg.info>
> http://danforsberg.info:8080/pana-issues/issue32
> ________________________________________________
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Thu Oct 23 06:00:31 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10895
	for <pana-archive@odin.ietf.org>; Thu, 23 Oct 2003 06:00:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACcGJ-0000k6-C8
	for pana-archive@odin.ietf.org; Thu, 23 Oct 2003 06:00:12 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NA0B4d002838
	for pana-archive@odin.ietf.org; Thu, 23 Oct 2003 06:00:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACcGE-0000it-5E
	for pana-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 06:00:06 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10850
	for <pana-web-archive@ietf.org>; Thu, 23 Oct 2003 05:59:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACcGA-0004at-00
	for pana-web-archive@ietf.org; Thu, 23 Oct 2003 06:00:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACcG9-0004ap-00
	for pana-web-archive@ietf.org; Thu, 23 Oct 2003 06:00:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACcGA-0000h0-6A; Thu, 23 Oct 2003 06:00:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACcG2-0000fB-RW
	for pana@optimus.ietf.org; Thu, 23 Oct 2003 05:59:54 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10844
	for <pana@ietf.org>; Thu, 23 Oct 2003 05:59:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACcFy-0004ai-00
	for pana@ietf.org; Thu, 23 Oct 2003 05:59:50 -0400
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACcFx-0004ae-00
	for pana@ietf.org; Thu, 23 Oct 2003 05:59:50 -0400
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h9N9xnc12817;
	Thu, 23 Oct 2003 11:59:49 +0200 (MEST)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id h9N9xmd10850;
	Thu, 23 Oct 2003 11:59:48 +0200 (MEST)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19)
	id <V3ZRCLAS>; Thu, 23 Oct 2003 11:59:37 +0200
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC033C@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Dan.Forsberg@nokia.com'" <Dan.Forsberg@nokia.com>, pana@ietf.org
Subject: RE: [Pana] [issue32] PANA Security considerations
Date: Thu, 23 Oct 2003 11:59:42 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi dan, 
hi alper, 

thanks for talking a look at the security consideration section. 
please see my comments inline:

> New submission from Dan Forsberg <dan.forsberg@nokia.com>:
> 
> From/through Alper Yegin:
> -------------------------
> 
> I have some editorial and technical comments on the security
> considerations section of the current PANA draft.
> 
> - a) Discovery message exchange
> ...
>    Since PAA and PaC are one IP hop away from each other, 
> PANA messages
>    can be filtered whenever messages arrive at interfaces where they
>    are not expected.
> 
> We should expand on this. Proposed addition "For example, EP may drop
> PANA-Start-Request messages when they are received from access side of
> the network where only PaCs can connect."

this is true for the current draft. however, adding the functionality
described in issue
12 this is not possible anymore. 


> 
> - b) EAP over PANA message exchange
> 
> Change:
> 
>    Hence an 
>    adversary can both eavesdrop the EAP messages and is also able to
>    inject arbitrary messages which might confuse both the PaC and the
>    PAA. 
> 
> To:
> 
>    Hence an 
>    adversary can both eavesdrop the EAP messages and is also able to
>    inject arbitrary messages which might confuse both the EAP 
> peer on PaC
>    and the EAP authenticator or the authentication server on the PAA.
> 
ok. 


> - c) PANA SA establishment
> 
> "subsection (c)" -> "subsection (d)"
> 
> "Integrity Object" -> "MAC AVP"
> 
> The session keys (one for each direction) used for this 
> object has to be
> provided by the EAP method.
> 
> We don't really require that the session keys are unidirectional.

i agree with you (since the 4-way handshake described in ieee 802.11i) does
not use separate keys for each direction either. 

however, we have to insure that reflection attacks are not possible. we have
to add some text on this issue somewhere. 

> 
> "per-default" -> "by default"
> 
> To select the security association for signaling message 
> protection the
> Session ID.
> 
> This sentence seems unfinished.

that's more than true. 

how about: 
"To select the security association for signaling message protection the
Session 
ID is used."



> 
> "looses" -> "loses"
> 
>    The lifetime of the PANA SA has to be bound to the refresh interval
>    with an additional tolerance period. To provide fast re-
>    authentication a separate security association (e.g. one stored at
>    the local AAA server) should be used. By fast re-authentication we
>    mean a new PANA protocol execution which does not involve 
> the entire
>    AAA communication. The ability to trigger such a protocol execution
>    depends on the given EAP method and on the policy of the local
>    network requesting authentication.
> 
> This paragraph is talking about couple of things. I suggest 
> we don't get
> into EAP-based fast reauth schemes in here (after all it should be all
> transparent to PANA). Instead we can say this:
> 
>    The lifetime of the PANA SA has to be bound to the refresh interval
>    with an additional tolerance period. Unless PANA state is 
> updated by
>    executing EAP authentication, PANA SA is removed when the current
>    session lifetime expires.

ok - sounds like a good idea to keep these things separate. 

>   
> g) Triggering a data protection protocol
> 
>    Furthermore, a derived session key might help to create the
>    pre-requisites for network layer protection (for example IPsec).
> 
> Let's add reference to PANA-IPsec draft here.

ok. 

> 
> h) Periodic refresh messages
> 
>    If network 
>    access authentication as part of PANA is executed only at the
>    beginning then an adversary can gain advantage of the installed
>    packet filters to submit and receive data packets.
> 
> This is not accurate. Because, one would either rely on physical
> security, or use crypto-based per-packet protection to prevent this
> possibility.

you are right. we should be more precise here. 

how about: 

If network access authentication as part of PANA is executed only at the
beginning then an adversary can gain advantage of the installed packet
filters to submit and receive data packets unless physical layer or
crypto-based per-packet protection is provided. 


> 
>    Different procedures can be used for disconnect indication. PANA
>    cannot assume link layer disconnect indication. Hence this
>    functionality has to be provided at a higher layer. With this
>    version of the draft we suggest to apply the soft-state principle
>    found at other protocols (such as RSVP). Soft-state means that
>    session state is kept alive as long as refresh messages refresh the
>    state. If no new refresh messages are provided then the state
>    automatically times out and resources are released. This process
>    includes stopping accounting procedures.
>     
>    Based on the different environments where PANA could be used it is
>    difficult to fix a refresh interval. Hence a default refresh
>    interval of 30 seconds is suggested. Additionally there is the
>    possibility to negotiation this interval once the PANA security
>    association is established. A policy at the PAA and the PaC would
>    ensure that the refresh interval is selected with a value which is
>    either too high or too low. There is certainly a tradeoff between
>    the refresh interval and the bandwidth consumption. To reduce the
>    bandwidth consumption a small PANA message consisting only of a
>    session identifier and the Integrity object is used. The session
>    identifier refers to the state that has to be refreshed. Some
>    environments do not need PANA refresh messages to detect orphan
>    states. For these environments the refresh interval should 
> be set to
>    zero which effectively disables the usage of refresh messages. In
>    case of IPsec protection a dead-peer mechanism can be used 
> to detect
>    inactivity (see [HBR03]).
>     
>    Refresh messages are sent from the PaC to the PAA.
> 
> This text is not aligned with the latest discussions. I presume it is
> referring to PANA-reauth as the refresh message... but we don't really
> suggest using periodic re-auth messages in the specification. There is
> only a PANA session lifetime, and that is not negotiated. We had a
> lengthy discussion on that.

true. this is old text. 

ciao
hannes

> 
> 
> ----------
> category: Technical
> document: draft-ietf-pana-pana-xx.txt
> messages: 94
> nosy: dforsber
> priority: Must Fix
> status: No Discussion
> title: PANA Security considerations
> ________________________________________________
> PANA Issues <pana_issues@danforsberg.info>
> http://danforsberg.info:8080/pana-issues/issue32
> ________________________________________________
> 
> _______________________________________________
> 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-admin@ietf.org  Thu Oct 23 10:29:20 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25622
	for <pana-archive@lists.ietf.org>; Thu, 23 Oct 2003 10:29:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACgSS-0003Ho-U9; Thu, 23 Oct 2003 10:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACgRo-0003AG-SC
	for pana@optimus.ietf.org; Thu, 23 Oct 2003 10:28:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25578
	for <pana@ietf.org>; Thu, 23 Oct 2003 10:28:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACgRm-0001CX-00
	for pana@ietf.org; Thu, 23 Oct 2003 10:28:18 -0400
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACgRl-0001CD-00
	for pana@ietf.org; Thu, 23 Oct 2003 10:28:18 -0400
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id h9NERVSS020525
	for <pana@ietf.org>; Thu, 23 Oct 2003 16:27:31 +0200
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003102316273045:5045 ;
          Thu, 23 Oct 2003 16:27:30 +0200 
Message-ID: <3F97E553.5030801@alcatel.fr>
Date: Thu, 23 Oct 2003 16:27:31 +0200
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: pana@ietf.org
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/23/2003 16:27:30,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/23/2003 16:27:31,
	Serialize complete at 10/23/2003 16:27:31
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Virus-Scanned: by amavisd-new
Content-Transfer-Encoding: 7bit
Subject: [Pana] access control information in the EP
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi all,


* Below is the DI definition quoted from [I-D.ietf-pana-requirements]:

    Device Identifier (DI)

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


* Recent [I-D.ietf-pana-pana] states the following for the DI AVP:

    The first octet (8 bits) of the Device-Id (Code 1025) AVP data
    contains the device type. Rest of the AVP data payload contains the
    device data.  The content and format of data (including byte and bit
    ordering) is expected to be specified in specific documents.  For
    instance, [RFC2464].

             UNKNOWN                           0
             IPV4_ADDRESS                      1
             IPV6_ADDRESS                      2
             L2_ADDRESS                        3

    For type 1 (IPv4 address), data size is 32 bits and for type 2 (IPv6
    address), data size is 128 bits.

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |     Type      |           Data...                             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+




let's try to figure out what are the infos needed to be transported by 
the PAA-to-EP protocol (say SNMP...) with the following couple of questions:

1) In order to police the network access of a client at the EP, are 
source addresses sufficient ? should the EP be capable to identify a 
specific flow with, e.g. the IP 5-tuple (srcAddr, destAddr, srcPort, 
destPort, L4Prot) ?

2) When Type=L2_ADDRESS, what are the various possible underlying link 
layer for the access network ?
FYI, http://www.iana.org/assignments/ianaiftype-mib gives a pretty 
exhaustive ;-) list of underlying interface types via the IANAifType 
definition.


Thanks,
Yacine El Mghazli



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


From exim@www1.ietf.org  Thu Oct 23 10:29:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25637
	for <pana-archive@odin.ietf.org>; Thu, 23 Oct 2003 10:29:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACgSU-0003It-TF
	for pana-archive@odin.ietf.org; Thu, 23 Oct 2003 10:29:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NET2UH012699
	for pana-archive@odin.ietf.org; Thu, 23 Oct 2003 10:29:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACgSU-0003Ik-GG
	for pana-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 10:29:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25603
	for <pana-web-archive@ietf.org>; Thu, 23 Oct 2003 10:28:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACgSS-0001Cz-00
	for pana-web-archive@ietf.org; Thu, 23 Oct 2003 10:29:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACgSR-0001Cw-00
	for pana-web-archive@ietf.org; Thu, 23 Oct 2003 10:28:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACgSS-0003Ho-U9; Thu, 23 Oct 2003 10:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACgRo-0003AG-SC
	for pana@optimus.ietf.org; Thu, 23 Oct 2003 10:28:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25578
	for <pana@ietf.org>; Thu, 23 Oct 2003 10:28:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACgRm-0001CX-00
	for pana@ietf.org; Thu, 23 Oct 2003 10:28:18 -0400
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACgRl-0001CD-00
	for pana@ietf.org; Thu, 23 Oct 2003 10:28:18 -0400
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id h9NERVSS020525
	for <pana@ietf.org>; Thu, 23 Oct 2003 16:27:31 +0200
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003102316273045:5045 ;
          Thu, 23 Oct 2003 16:27:30 +0200 
Message-ID: <3F97E553.5030801@alcatel.fr>
Date: Thu, 23 Oct 2003 16:27:31 +0200
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: pana@ietf.org
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/23/2003 16:27:30,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/23/2003 16:27:31,
	Serialize complete at 10/23/2003 16:27:31
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Virus-Scanned: by amavisd-new
Content-Transfer-Encoding: 7bit
Subject: [Pana] access control information in the EP
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi all,


* Below is the DI definition quoted from [I-D.ietf-pana-requirements]:

    Device Identifier (DI)

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


* Recent [I-D.ietf-pana-pana] states the following for the DI AVP:

    The first octet (8 bits) of the Device-Id (Code 1025) AVP data
    contains the device type. Rest of the AVP data payload contains the
    device data.  The content and format of data (including byte and bit
    ordering) is expected to be specified in specific documents.  For
    instance, [RFC2464].

             UNKNOWN                           0
             IPV4_ADDRESS                      1
             IPV6_ADDRESS                      2
             L2_ADDRESS                        3

    For type 1 (IPv4 address), data size is 32 bits and for type 2 (IPv6
    address), data size is 128 bits.

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |     Type      |           Data...                             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+




let's try to figure out what are the infos needed to be transported by 
the PAA-to-EP protocol (say SNMP...) with the following couple of questions:

1) In order to police the network access of a client at the EP, are 
source addresses sufficient ? should the EP be capable to identify a 
specific flow with, e.g. the IP 5-tuple (srcAddr, destAddr, srcPort, 
destPort, L4Prot) ?

2) When Type=L2_ADDRESS, what are the various possible underlying link 
layer for the access network ?
FYI, http://www.iana.org/assignments/ianaiftype-mib gives a pretty 
exhaustive ;-) list of underlying interface types via the IANAifType 
definition.


Thanks,
Yacine El Mghazli



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



From pana-admin@ietf.org  Thu Oct 23 14:46:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11971
	for <pana-archive@lists.ietf.org>; Thu, 23 Oct 2003 14:46:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACkTB-00049B-F9; Thu, 23 Oct 2003 14:46:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACkSj-000457-5c
	for pana@optimus.ietf.org; Thu, 23 Oct 2003 14:45:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11919
	for <pana@ietf.org>; Thu, 23 Oct 2003 14:45:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACkSg-0006NU-00
	for pana@ietf.org; Thu, 23 Oct 2003 14:45:30 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACkSf-0006NQ-00
	for pana@ietf.org; Thu, 23 Oct 2003 14:45:30 -0400
Date: Thu, 23 Oct 2003 11:45:21 -0700
Subject: Re: [Pana] access control information in the EP
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yacine.El_Mghazli@alcatel.fr>, <pana@ietf.org>
Message-ID: <BBBD6FD1.B1B7%alper@docomolabs-usa.com>
In-Reply-To: <3F97E553.5030801@alcatel.fr>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

> let's try to figure out what are the infos needed to be transported by
> the PAA-to-EP protocol (say SNMP...) with the following couple of questions:
> 
> 1) In order to police the network access of a client at the EP, are
> source addresses sufficient ? should the EP be capable to identify a
> specific flow with, e.g. the IP 5-tuple (srcAddr, destAddr, srcPort,
> destPort, L4Prot) ?

For basic network access authorization, source address based filtering is
sufficient (plus, the cryptographic binding where needed... which will
require to pass a key to the EP). I can see how one might want to extend on
this, especially if the AAA backend protocol is returning a detailed
authorization profile. In that case, in addition to being able to pass just
the source address, can we also pass a blob of data that contains a more
detailed filter? The format and usage details are not interesting for the
PAA2EP protocol, it just carries the stuff.

> 
> 2) When Type=L2_ADDRESS, what are the various possible underlying link
> layer for the access network ?
> FYI, http://www.iana.org/assignments/ianaiftype-mib gives a pretty
> exhaustive ;-) list of underlying interface types via the IANAifType
> definition.

I don't think the list size of the specifics of each link-type would impact
the PAA2EP protocol design. You don't have to provide specific format for
each. You can follow the lead of what RFC2461 did on that:

        Link-Layer Address
                     The variable length link-layer address.

                     The content and format of this field (including
                     byte and bit ordering) is expected to be specified
                     in specific documents that describe how IPv6
                     operates over different link layers.  For instance,
                     [IPv6-ETHER].

Alper


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


From exim@www1.ietf.org  Thu Oct 23 14:46:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11986
	for <pana-archive@odin.ietf.org>; Thu, 23 Oct 2003 14:46:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACkTD-0004BD-Uf
	for pana-archive@odin.ietf.org; Thu, 23 Oct 2003 14:46:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NIk3qP016061
	for pana-archive@odin.ietf.org; Thu, 23 Oct 2003 14:46:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACkTD-0004Ar-QT
	for pana-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 14:46:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11951
	for <pana-web-archive@ietf.org>; Thu, 23 Oct 2003 14:45:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACkTB-0006OI-00
	for pana-web-archive@ietf.org; Thu, 23 Oct 2003 14:46:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACkTA-0006OF-00
	for pana-web-archive@ietf.org; Thu, 23 Oct 2003 14:46:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACkTB-00049B-F9; Thu, 23 Oct 2003 14:46:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACkSj-000457-5c
	for pana@optimus.ietf.org; Thu, 23 Oct 2003 14:45:33 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11919
	for <pana@ietf.org>; Thu, 23 Oct 2003 14:45:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACkSg-0006NU-00
	for pana@ietf.org; Thu, 23 Oct 2003 14:45:30 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACkSf-0006NQ-00
	for pana@ietf.org; Thu, 23 Oct 2003 14:45:30 -0400
Date: Thu, 23 Oct 2003 11:45:21 -0700
Subject: Re: [Pana] access control information in the EP
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yacine.El_Mghazli@alcatel.fr>, <pana@ietf.org>
Message-ID: <BBBD6FD1.B1B7%alper@docomolabs-usa.com>
In-Reply-To: <3F97E553.5030801@alcatel.fr>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> let's try to figure out what are the infos needed to be transported by
> the PAA-to-EP protocol (say SNMP...) with the following couple of questions:
> 
> 1) In order to police the network access of a client at the EP, are
> source addresses sufficient ? should the EP be capable to identify a
> specific flow with, e.g. the IP 5-tuple (srcAddr, destAddr, srcPort,
> destPort, L4Prot) ?

For basic network access authorization, source address based filtering is
sufficient (plus, the cryptographic binding where needed... which will
require to pass a key to the EP). I can see how one might want to extend on
this, especially if the AAA backend protocol is returning a detailed
authorization profile. In that case, in addition to being able to pass just
the source address, can we also pass a blob of data that contains a more
detailed filter? The format and usage details are not interesting for the
PAA2EP protocol, it just carries the stuff.

> 
> 2) When Type=L2_ADDRESS, what are the various possible underlying link
> layer for the access network ?
> FYI, http://www.iana.org/assignments/ianaiftype-mib gives a pretty
> exhaustive ;-) list of underlying interface types via the IANAifType
> definition.

I don't think the list size of the specifics of each link-type would impact
the PAA2EP protocol design. You don't have to provide specific format for
each. You can follow the lead of what RFC2461 did on that:

        Link-Layer Address
                     The variable length link-layer address.

                     The content and format of this field (including
                     byte and bit ordering) is expected to be specified
                     in specific documents that describe how IPv6
                     operates over different link layers.  For instance,
                     [IPv6-ETHER].

Alper


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



From pana-admin@ietf.org  Thu Oct 23 21:40:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28663
	for <pana-archive@lists.ietf.org>; Thu, 23 Oct 2003 21:40:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACqvq-000846-MR; Thu, 23 Oct 2003 21:40:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACqv2-0007hj-Ut
	for pana@optimus.ietf.org; Thu, 23 Oct 2003 21:39:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28604
	for <pana@ietf.org>; Thu, 23 Oct 2003 21:39:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACquz-0003f0-00
	for pana@ietf.org; Thu, 23 Oct 2003 21:39:09 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACquz-0003eq-00
	for pana@ietf.org; Thu, 23 Oct 2003 21:39:09 -0400
Date: Thu, 23 Oct 2003 18:39:03 -0700
Subject: Re: [Pana] [issue32] PANA Security considerations
From: Alper Yegin <alper@docomolabs-usa.com>
To: Tschofenig Hannes <hannes.tschofenig@siemens.com>,
        "'Dan.Forsberg@nokia.com'" <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBBDD0C7.B229%alper@docomolabs-usa.com>
In-Reply-To: <2A8DB02E3018D411901B009027FD3A3F03BC033C@mchp905a.mch.sbs.de>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Hannes,

>> We should expand on this. Proposed addition "For example, EP may drop
>> PANA-Start-Request messages when they are received from access side of
>> the network where only PaCs can connect."
> 
> this is true for the current draft. however, adding the functionality
> described in issue
> 12 this is not possible anymore.

Yes, this is provided as one possible way. It is not assumed in all
deployments.


>> The session keys (one for each direction) used for this
>> object has to be
>> provided by the EAP method.
>> 
>> We don't really require that the session keys are unidirectional.
> 
> i agree with you (since the 4-way handshake described in ieee 802.11i) does
> not use separate keys for each direction either.
> 
> however, we have to insure that reflection attacks are not possible. we have
> to add some text on this issue somewhere.

Can you please elaborate (reflection attack?) and also provide some text...
(we probably won't have time to finalize it before the draft gets submitted
though....)

>> To select the security association for signaling message
>> protection the
>> Session ID.
>> 
>> This sentence seems unfinished.
> 
> that's more than true.
> 
> how about: 
> "To select the security association for signaling message protection the
> Session 
> ID is used."

Please see the latest version of the spec, which already includes the fix to
this issue.

>>    If network 
>>    access authentication as part of PANA is executed only at the
>>    beginning then an adversary can gain advantage of the installed
>>    packet filters to submit and receive data packets.
>> 
>> This is not accurate. Because, one would either rely on physical
>> security, or use crypto-based per-packet protection to prevent this
>> possibility.
> 
> you are right. we should be more precise here.
> 
> how about: 
> 
> If network access authentication as part of PANA is executed only at the
> beginning then an adversary can gain advantage of the installed packet
> filters to submit and receive data packets unless physical layer or
> crypto-based per-packet protection is provided.

I already did some rewriting on this as part of the proposed resolution.
Please see the latest text.

Alper


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


From exim@www1.ietf.org  Thu Oct 23 21:40:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28678
	for <pana-archive@odin.ietf.org>; Thu, 23 Oct 2003 21:40:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACqvw-000878-4E
	for pana-archive@odin.ietf.org; Thu, 23 Oct 2003 21:40:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9O1e8k1031184
	for pana-archive@odin.ietf.org; Thu, 23 Oct 2003 21:40:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACqvv-00085D-Mz
	for pana-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 21:40:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28641
	for <pana-web-archive@ietf.org>; Thu, 23 Oct 2003 21:39:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACqvp-0003fw-00
	for pana-web-archive@ietf.org; Thu, 23 Oct 2003 21:40:02 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACqvp-0003ft-00
	for pana-web-archive@ietf.org; Thu, 23 Oct 2003 21:40:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACqvq-000846-MR; Thu, 23 Oct 2003 21:40:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACqv2-0007hj-Ut
	for pana@optimus.ietf.org; Thu, 23 Oct 2003 21:39:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28604
	for <pana@ietf.org>; Thu, 23 Oct 2003 21:39:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACquz-0003f0-00
	for pana@ietf.org; Thu, 23 Oct 2003 21:39:09 -0400
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACquz-0003eq-00
	for pana@ietf.org; Thu, 23 Oct 2003 21:39:09 -0400
Date: Thu, 23 Oct 2003 18:39:03 -0700
Subject: Re: [Pana] [issue32] PANA Security considerations
From: Alper Yegin <alper@docomolabs-usa.com>
To: Tschofenig Hannes <hannes.tschofenig@siemens.com>,
        "'Dan.Forsberg@nokia.com'" <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBBDD0C7.B229%alper@docomolabs-usa.com>
In-Reply-To: <2A8DB02E3018D411901B009027FD3A3F03BC033C@mchp905a.mch.sbs.de>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Hannes,

>> We should expand on this. Proposed addition "For example, EP may drop
>> PANA-Start-Request messages when they are received from access side of
>> the network where only PaCs can connect."
> 
> this is true for the current draft. however, adding the functionality
> described in issue
> 12 this is not possible anymore.

Yes, this is provided as one possible way. It is not assumed in all
deployments.


>> The session keys (one for each direction) used for this
>> object has to be
>> provided by the EAP method.
>> 
>> We don't really require that the session keys are unidirectional.
> 
> i agree with you (since the 4-way handshake described in ieee 802.11i) does
> not use separate keys for each direction either.
> 
> however, we have to insure that reflection attacks are not possible. we have
> to add some text on this issue somewhere.

Can you please elaborate (reflection attack?) and also provide some text...
(we probably won't have time to finalize it before the draft gets submitted
though....)

>> To select the security association for signaling message
>> protection the
>> Session ID.
>> 
>> This sentence seems unfinished.
> 
> that's more than true.
> 
> how about: 
> "To select the security association for signaling message protection the
> Session 
> ID is used."

Please see the latest version of the spec, which already includes the fix to
this issue.

>>    If network 
>>    access authentication as part of PANA is executed only at the
>>    beginning then an adversary can gain advantage of the installed
>>    packet filters to submit and receive data packets.
>> 
>> This is not accurate. Because, one would either rely on physical
>> security, or use crypto-based per-packet protection to prevent this
>> possibility.
> 
> you are right. we should be more precise here.
> 
> how about: 
> 
> If network access authentication as part of PANA is executed only at the
> beginning then an adversary can gain advantage of the installed packet
> filters to submit and receive data packets unless physical layer or
> crypto-based per-packet protection is provided.

I already did some rewriting on this as part of the proposed resolution.
Please see the latest text.

Alper


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



From pana-admin@ietf.org  Mon Oct 27 02:48:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29672
	for <pana-archive@lists.ietf.org>; Mon, 27 Oct 2003 02:48:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE26b-0002Go-2J; Mon, 27 Oct 2003 02:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE25q-0002FI-JR
	for pana@optimus.ietf.org; Mon, 27 Oct 2003 02:47:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29652
	for <pana@ietf.org>; Mon, 27 Oct 2003 02:47:02 -0500 (EST)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE25m-0000Qr-00
	for pana@ietf.org; Mon, 27 Oct 2003 02:47:10 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE25l-0000Qm-00
	for pana@ietf.org; Mon, 27 Oct 2003 02:47:10 -0500
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9R7l9I27963
	for <pana@ietf.org>; Mon, 27 Oct 2003 09:47:09 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6589595528ac158f24cae@esvir04nok.ntc.nokia.com> for <pana@ietf.org>;
 Mon, 27 Oct 2003 09:47:09 +0200
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Mon, 27 Oct 2003 09:47:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Oct 2003 09:47:06 +0200
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5C3@esebe008.ntc.nokia.com>
Thread-Topic: Closed issues related to 01 version of the pana protocol draft.
Thread-Index: AcOcXoS8B4pyE3j0QH6ybVPahFOyMQ==
To: <pana@ietf.org>
X-OriginalArrivalTime: 27 Oct 2003 07:47:07.0146 (UTC) FILETIME=[852996A0:01C39C5E]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] Closed issues related to 01 version of the pana protocol draft.
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

FYI: I've closed all the issues related to 01 version of the=20
pana protocol draft. All these issues had state "text proposed"=20
or "accepted". Currently it is not clear, when an issue becomes
accepted. Anyway, at the moment issue tracker is a tool for
keeping track of what has been done and is currently open. Any=20
comments to this is welcome. See draft 02 for more details.

Issue tracker URL:
http://danforsberg.info:8080/pana-issues/


Br,
- Dan

ps. Hopefully we get soon IETF hosted issue tracker system.

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


From exim@www1.ietf.org  Mon Oct 27 02:48:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29687
	for <pana-archive@odin.ietf.org>; Mon, 27 Oct 2003 02:48:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE26g-0002HX-O3
	for pana-archive@odin.ietf.org; Mon, 27 Oct 2003 02:48:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9R7m6Xd008764
	for pana-archive@odin.ietf.org; Mon, 27 Oct 2003 02:48:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE26f-0002HH-OO
	for pana-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 02:48:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29669
	for <pana-web-archive@ietf.org>; Mon, 27 Oct 2003 02:47:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE26b-0000RI-00
	for pana-web-archive@ietf.org; Mon, 27 Oct 2003 02:48:02 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE26b-0000RE-00
	for pana-web-archive@ietf.org; Mon, 27 Oct 2003 02:48:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE26b-0002Go-2J; Mon, 27 Oct 2003 02:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE25q-0002FI-JR
	for pana@optimus.ietf.org; Mon, 27 Oct 2003 02:47:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29652
	for <pana@ietf.org>; Mon, 27 Oct 2003 02:47:02 -0500 (EST)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE25m-0000Qr-00
	for pana@ietf.org; Mon, 27 Oct 2003 02:47:10 -0500
Received: from mgw-x4.nokia.com ([131.228.20.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE25l-0000Qm-00
	for pana@ietf.org; Mon, 27 Oct 2003 02:47:10 -0500
Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36])
	by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9R7l9I27963
	for <pana@ietf.org>; Mon, 27 Oct 2003 09:47:09 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T6589595528ac158f24cae@esvir04nok.ntc.nokia.com> for <pana@ietf.org>;
 Mon, 27 Oct 2003 09:47:09 +0200
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Mon, 27 Oct 2003 09:47:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 27 Oct 2003 09:47:06 +0200
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA0143C5C3@esebe008.ntc.nokia.com>
Thread-Topic: Closed issues related to 01 version of the pana protocol draft.
Thread-Index: AcOcXoS8B4pyE3j0QH6ybVPahFOyMQ==
To: <pana@ietf.org>
X-OriginalArrivalTime: 27 Oct 2003 07:47:07.0146 (UTC) FILETIME=[852996A0:01C39C5E]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] Closed issues related to 01 version of the pana protocol draft.
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

FYI: I've closed all the issues related to 01 version of the=20
pana protocol draft. All these issues had state "text proposed"=20
or "accepted". Currently it is not clear, when an issue becomes
accepted. Anyway, at the moment issue tracker is a tool for
keeping track of what has been done and is currently open. Any=20
comments to this is welcome. See draft 02 for more details.

Issue tracker URL:
http://danforsberg.info:8080/pana-issues/


Br,
- Dan

ps. Hopefully we get soon IETF hosted issue tracker system.

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



From pana-admin@ietf.org  Mon Oct 27 04:46:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03813
	for <pana-archive@lists.ietf.org>; Mon, 27 Oct 2003 04:46:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE3wn-0004tz-UZ; Mon, 27 Oct 2003 04:46:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE3wV-0004sl-PJ
	for pana@optimus.ietf.org; Mon, 27 Oct 2003 04:45:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03776
	for <pana@ietf.org>; Mon, 27 Oct 2003 04:45:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE3wS-00020k-00
	for pana@ietf.org; Mon, 27 Oct 2003 04:45:40 -0500
Received: from colt-na7.alcatel.fr ([62.23.212.7] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE3wS-00020Q-00
	for pana@ietf.org; Mon, 27 Oct 2003 04:45:40 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id h9R9j5SS029478;
	Mon, 27 Oct 2003 10:45:05 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003102710450243:1808 ;
          Mon, 27 Oct 2003 10:45:02 +0100 
Message-ID: <3F9CE91F.60404@alcatel.fr>
Date: Mon, 27 Oct 2003 10:45:03 +0100
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Alper Yegin <alper@docomolabs-usa.com>
CC: pana@ietf.org
Subject: Re: [Pana] access control information in the EP
References: <BBBD6FD1.B1B7%alper@docomolabs-usa.com>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/27/2003 10:45:02,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/27/2003 10:45:04
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: by amavisd-new
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Alper:

Alper Yegin a =E9crit:
>>let's try to figure out what are the infos needed to be transported by
>>the PAA-to-EP protocol (say SNMP...) with the following couple of questio=
ns:
>>
>>1) In order to police the network access of a client at the EP, are
>>source addresses sufficient ? should the EP be capable to identify a
>>specific flow with, e.g. the IP 5-tuple (srcAddr, destAddr, srcPort,
>>destPort, L4Prot) ?
>=20
>=20
> For basic network access authorization, source address based filtering is
> sufficient (plus, the cryptographic binding where needed... which will
> require to pass a key to the EP). I can see how one might want to extend =
on
> this, especially if the AAA backend protocol is returning a detailed
> authorization profile. In that case, in addition to being able to pass ju=
st
> the source address, can we also pass a blob of data that contains a more
> detailed filter? The format and usage details are not interesting for the
> PAA2EP protocol, it just carries the stuff.

OK then what is needed once the working group has agreed on the right=20
candidate to use as the PAA-2-EP protocol (let's say SNMP) ?

SNMP transport generic objects: the content of these objects is=20
determined by the specific MIB modules design. does PANA need such=20
designs or only guidelines on the context using SNMP ?


>>2) When Type=3DL2=5FADDRESS, what are the various possible underlying link
>>layer for the access network ?
>>FYI, http://www.iana.org/assignments/ianaiftype-mib gives a pretty
>>exhaustive ;-) list of underlying interface types via the IANAifType
>>definition.
>=20
>=20
> I don't think the list size of the specifics of each link-type would impa=
ct
> the PAA2EP protocol design. You don't have to provide specific format for
> each. You can follow the lead of what RFC2461 did on that:
>=20
>         Link-Layer Address
>                      The variable length link-layer address.
>=20
>                      The content and format of this field (including
>                      byte and bit ordering) is expected to be specified
>                      in specific documents that describe how IPv6
>                      operates over different link layers.  For instance,
>                      [IPv6-ETHER].

I think this lattest point is strongly related to the previous one.

>=20
> Alper
>=20

Thanks,
Yacine

>=20



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


From exim@www1.ietf.org  Mon Oct 27 04:46:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03828
	for <pana-archive@odin.ietf.org>; Mon, 27 Oct 2003 04:46:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE3wq-0004uo-5p
	for pana-archive@odin.ietf.org; Mon, 27 Oct 2003 04:46:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9R9k4xk018894
	for pana-archive@odin.ietf.org; Mon, 27 Oct 2003 04:46:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE3wp-0004uf-JA
	for pana-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 04:46:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03790
	for <pana-web-archive@ietf.org>; Mon, 27 Oct 2003 04:45:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE3wm-000212-00
	for pana-web-archive@ietf.org; Mon, 27 Oct 2003 04:46:00 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE3wm-00020z-00
	for pana-web-archive@ietf.org; Mon, 27 Oct 2003 04:46:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE3wn-0004tz-UZ; Mon, 27 Oct 2003 04:46:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AE3wV-0004sl-PJ
	for pana@optimus.ietf.org; Mon, 27 Oct 2003 04:45:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03776
	for <pana@ietf.org>; Mon, 27 Oct 2003 04:45:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE3wS-00020k-00
	for pana@ietf.org; Mon, 27 Oct 2003 04:45:40 -0500
Received: from colt-na7.alcatel.fr ([62.23.212.7] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AE3wS-00020Q-00
	for pana@ietf.org; Mon, 27 Oct 2003 04:45:40 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id h9R9j5SS029478;
	Mon, 27 Oct 2003 10:45:05 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003102710450243:1808 ;
          Mon, 27 Oct 2003 10:45:02 +0100 
Message-ID: <3F9CE91F.60404@alcatel.fr>
Date: Mon, 27 Oct 2003 10:45:03 +0100
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Alper Yegin <alper@docomolabs-usa.com>
CC: pana@ietf.org
Subject: Re: [Pana] access control information in the EP
References: <BBBD6FD1.B1B7%alper@docomolabs-usa.com>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/27/2003 10:45:02,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 10/27/2003 10:45:04
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: by amavisd-new
Content-Transfer-Encoding: quoted-printable
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Alper:

Alper Yegin a =E9crit:
>>let's try to figure out what are the infos needed to be transported by
>>the PAA-to-EP protocol (say SNMP...) with the following couple of questio=
ns:
>>
>>1) In order to police the network access of a client at the EP, are
>>source addresses sufficient ? should the EP be capable to identify a
>>specific flow with, e.g. the IP 5-tuple (srcAddr, destAddr, srcPort,
>>destPort, L4Prot) ?
>=20
>=20
> For basic network access authorization, source address based filtering is
> sufficient (plus, the cryptographic binding where needed... which will
> require to pass a key to the EP). I can see how one might want to extend =
on
> this, especially if the AAA backend protocol is returning a detailed
> authorization profile. In that case, in addition to being able to pass ju=
st
> the source address, can we also pass a blob of data that contains a more
> detailed filter? The format and usage details are not interesting for the
> PAA2EP protocol, it just carries the stuff.

OK then what is needed once the working group has agreed on the right=20
candidate to use as the PAA-2-EP protocol (let's say SNMP) ?

SNMP transport generic objects: the content of these objects is=20
determined by the specific MIB modules design. does PANA need such=20
designs or only guidelines on the context using SNMP ?


>>2) When Type=3DL2=5FADDRESS, what are the various possible underlying link
>>layer for the access network ?
>>FYI, http://www.iana.org/assignments/ianaiftype-mib gives a pretty
>>exhaustive ;-) list of underlying interface types via the IANAifType
>>definition.
>=20
>=20
> I don't think the list size of the specifics of each link-type would impa=
ct
> the PAA2EP protocol design. You don't have to provide specific format for
> each. You can follow the lead of what RFC2461 did on that:
>=20
>         Link-Layer Address
>                      The variable length link-layer address.
>=20
>                      The content and format of this field (including
>                      byte and bit ordering) is expected to be specified
>                      in specific documents that describe how IPv6
>                      operates over different link layers.  For instance,
>                      [IPv6-ETHER].

I think this lattest point is strongly related to the previous one.

>=20
> Alper
>=20

Thanks,
Yacine

>=20



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



From pana-admin@ietf.org  Mon Oct 27 15:43:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08765
	for <pana-archive@lists.ietf.org>; Mon, 27 Oct 2003 15:43:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEECb-00083c-KK; Mon, 27 Oct 2003 15:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEECT-00082R-40
	for pana@optimus.ietf.org; Mon, 27 Oct 2003 15:42:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08724
	for <pana@ietf.org>; Mon, 27 Oct 2003 15:42:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEECR-0004EA-00
	for pana@ietf.org; Mon, 27 Oct 2003 15:42:51 -0500
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEECA-0004Cc-00
	for pana@ietf.org; Mon, 27 Oct 2003 15:42:35 -0500
Date: Mon, 27 Oct 2003 12:28:02 -0800
Subject: Re: [Pana] access control information in the EP
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yacine.El_Mghazli@alcatel.fr>
CC: <pana@ietf.org>
Message-ID: <BBC2BFD2.B557%alper@docomolabs-usa.com>
In-Reply-To: <3F9CE91F.60404@alcatel.fr>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Hi Yacine,

>>> 1) In order to police the network access of a client at the EP, are
>>> source addresses sufficient ? should the EP be capable to identify a
>>> specific flow with, e.g. the IP 5-tuple (srcAddr, destAddr, srcPort,
>>> destPort, L4Prot) ?
>> 
>> 
>> For basic network access authorization, source address based filtering is
>> sufficient (plus, the cryptographic binding where needed... which will
>> require to pass a key to the EP). I can see how one might want to extend on
>> this, especially if the AAA backend protocol is returning a detailed
>> authorization profile. In that case, in addition to being able to pass just
>> the source address, can we also pass a blob of data that contains a more
>> detailed filter? The format and usage details are not interesting for the
>> PAA2EP protocol, it just carries the stuff.
> 
> OK then what is needed once the working group has agreed on the right
> candidate to use as the PAA-2-EP protocol (let's say SNMP) ?
> 
> SNMP transport generic objects: the content of these objects is
> determined by the specific MIB modules design. does PANA need such
> designs or only guidelines on the context using SNMP ?

At the end, a vendor needs to understand what exactly should be implemented,
and what appears on the wire between the PAA and EP. In that sense,
guidelines would not be sufficient (unless they point to specific object
definitions) for providing interoperability.


It might be the case that the objects we need are already defined and used
in a similar context. Than pointing out which ones should be used for this
purpose might be sufficient. Otherwise, we'd need to define new objects
specifically for the PAA2EP communication.

Alper




> 
> 
>>> 2) When Type=L2_ADDRESS, what are the various possible underlying link
>>> layer for the access network ?
>>> FYI, http://www.iana.org/assignments/ianaiftype-mib gives a pretty
>>> exhaustive ;-) list of underlying interface types via the IANAifType
>>> definition.
>> 
>> 
>> I don't think the list size of the specifics of each link-type would impact
>> the PAA2EP protocol design. You don't have to provide specific format for
>> each. You can follow the lead of what RFC2461 did on that:
>> 
>>         Link-Layer Address
>>                      The variable length link-layer address.
>> 
>>                      The content and format of this field (including
>>                      byte and bit ordering) is expected to be specified
>>                      in specific documents that describe how IPv6
>>                      operates over different link layers.  For instance,
>>                      [IPv6-ETHER].
> 
> I think this lattest point is strongly related to the previous one.
> 
>> 
>> Alper
>> 
> 
> Thanks,
> Yacine
> 
>> 
> 
> 
> 
> 


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


From exim@www1.ietf.org  Mon Oct 27 15:43:29 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08780
	for <pana-archive@odin.ietf.org>; Mon, 27 Oct 2003 15:43:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEECj-00084Z-ML
	for pana-archive@odin.ietf.org; Mon, 27 Oct 2003 15:43:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RKh9Qb031025
	for pana-archive@odin.ietf.org; Mon, 27 Oct 2003 15:43:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEECj-00084K-Gh
	for pana-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 15:43:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08747
	for <pana-web-archive@ietf.org>; Mon, 27 Oct 2003 15:42:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEECh-0004EU-00
	for pana-web-archive@ietf.org; Mon, 27 Oct 2003 15:43:08 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEECh-0004ER-00
	for pana-web-archive@ietf.org; Mon, 27 Oct 2003 15:43:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEECb-00083c-KK; Mon, 27 Oct 2003 15:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEECT-00082R-40
	for pana@optimus.ietf.org; Mon, 27 Oct 2003 15:42:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08724
	for <pana@ietf.org>; Mon, 27 Oct 2003 15:42:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEECR-0004EA-00
	for pana@ietf.org; Mon, 27 Oct 2003 15:42:51 -0500
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEECA-0004Cc-00
	for pana@ietf.org; Mon, 27 Oct 2003 15:42:35 -0500
Date: Mon, 27 Oct 2003 12:28:02 -0800
Subject: Re: [Pana] access control information in the EP
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yacine.El_Mghazli@alcatel.fr>
CC: <pana@ietf.org>
Message-ID: <BBC2BFD2.B557%alper@docomolabs-usa.com>
In-Reply-To: <3F9CE91F.60404@alcatel.fr>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Yacine,

>>> 1) In order to police the network access of a client at the EP, are
>>> source addresses sufficient ? should the EP be capable to identify a
>>> specific flow with, e.g. the IP 5-tuple (srcAddr, destAddr, srcPort,
>>> destPort, L4Prot) ?
>> 
>> 
>> For basic network access authorization, source address based filtering is
>> sufficient (plus, the cryptographic binding where needed... which will
>> require to pass a key to the EP). I can see how one might want to extend on
>> this, especially if the AAA backend protocol is returning a detailed
>> authorization profile. In that case, in addition to being able to pass just
>> the source address, can we also pass a blob of data that contains a more
>> detailed filter? The format and usage details are not interesting for the
>> PAA2EP protocol, it just carries the stuff.
> 
> OK then what is needed once the working group has agreed on the right
> candidate to use as the PAA-2-EP protocol (let's say SNMP) ?
> 
> SNMP transport generic objects: the content of these objects is
> determined by the specific MIB modules design. does PANA need such
> designs or only guidelines on the context using SNMP ?

At the end, a vendor needs to understand what exactly should be implemented,
and what appears on the wire between the PAA and EP. In that sense,
guidelines would not be sufficient (unless they point to specific object
definitions) for providing interoperability.


It might be the case that the objects we need are already defined and used
in a similar context. Than pointing out which ones should be used for this
purpose might be sufficient. Otherwise, we'd need to define new objects
specifically for the PAA2EP communication.

Alper




> 
> 
>>> 2) When Type=L2_ADDRESS, what are the various possible underlying link
>>> layer for the access network ?
>>> FYI, http://www.iana.org/assignments/ianaiftype-mib gives a pretty
>>> exhaustive ;-) list of underlying interface types via the IANAifType
>>> definition.
>> 
>> 
>> I don't think the list size of the specifics of each link-type would impact
>> the PAA2EP protocol design. You don't have to provide specific format for
>> each. You can follow the lead of what RFC2461 did on that:
>> 
>>         Link-Layer Address
>>                      The variable length link-layer address.
>> 
>>                      The content and format of this field (including
>>                      byte and bit ordering) is expected to be specified
>>                      in specific documents that describe how IPv6
>>                      operates over different link layers.  For instance,
>>                      [IPv6-ETHER].
> 
> I think this lattest point is strongly related to the previous one.
> 
>> 
>> Alper
>> 
> 
> Thanks,
> Yacine
> 
>> 
> 
> 
> 
> 


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



From pana-admin@ietf.org  Mon Oct 27 16:35:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13358
	for <pana-archive@lists.ietf.org>; Mon, 27 Oct 2003 16:35:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEF0w-0003oF-TN; Mon, 27 Oct 2003 16:35:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEF0S-0003mJ-O0
	for pana@optimus.ietf.org; Mon, 27 Oct 2003 16:34:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13205
	for <pana@ietf.org>; Mon, 27 Oct 2003 16:34:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEF0Q-0005TG-00
	for pana@ietf.org; Mon, 27 Oct 2003 16:34:30 -0500
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEF0P-0005TC-00
	for pana@ietf.org; Mon, 27 Oct 2003 16:34:29 -0500
Date: Mon, 27 Oct 2003 13:20:21 -0800
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
CC: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>,
        Thomas Narten <narten@us.ibm.com>, <Margaret.Wasserman@nokia.com>
Message-ID: <BBC2CC15.B56D%alper@docomolabs-usa.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Draft agenda for IETF 58 PANA meeting
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


This is the draft agenda for the IETF 58 PANA WG meeting.
Comments welcome.

- Chairs

Protocol for Carrying Authentication for Network Access (PANA)

Tuesday, November 11 at 0900-1130
==================================

CHAIRS:    

  Basavaraj Patil <Basavaraj.Patil@nokia.com>
  Alper Yegin <alper@docomolabs-usa.com>

AGENDA:

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

2. PANA protocol update and open issues: 30 min, Yoshihiro Ohba

3. PAA-to-EP protocol considerations: 10 min, Yacine El Mghazli

4. PANA-IPsec I-D update: 10 min, Mohan Parthasarathy

5. PANA state machine considerations: 20 min, Dan Forsberg

6. Implementation report: 10 min, Victor Fajardo; 10 min, Hannes Tschofenig

7. Next steps: 5 min, Chairs/ADs



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


From exim@www1.ietf.org  Mon Oct 27 16:35:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13374
	for <pana-archive@odin.ietf.org>; Mon, 27 Oct 2003 16:35:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEF0y-0003p4-Gu
	for pana-archive@odin.ietf.org; Mon, 27 Oct 2003 16:35:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9RLZ45u014688
	for pana-archive@odin.ietf.org; Mon, 27 Oct 2003 16:35:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEF0y-0003op-AJ
	for pana-web-archive@optimus.ietf.org; Mon, 27 Oct 2003 16:35:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13285
	for <pana-web-archive@ietf.org>; Mon, 27 Oct 2003 16:34:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEF0w-0005UZ-00
	for pana-web-archive@ietf.org; Mon, 27 Oct 2003 16:35:02 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEF0v-0005UU-00
	for pana-web-archive@ietf.org; Mon, 27 Oct 2003 16:35:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEF0w-0003oF-TN; Mon, 27 Oct 2003 16:35:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEF0S-0003mJ-O0
	for pana@optimus.ietf.org; Mon, 27 Oct 2003 16:34:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13205
	for <pana@ietf.org>; Mon, 27 Oct 2003 16:34:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEF0Q-0005TG-00
	for pana@ietf.org; Mon, 27 Oct 2003 16:34:30 -0500
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEF0P-0005TC-00
	for pana@ietf.org; Mon, 27 Oct 2003 16:34:29 -0500
Date: Mon, 27 Oct 2003 13:20:21 -0800
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
CC: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>,
        Thomas Narten <narten@us.ibm.com>, <Margaret.Wasserman@nokia.com>
Message-ID: <BBC2CC15.B56D%alper@docomolabs-usa.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Draft agenda for IETF 58 PANA meeting
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


This is the draft agenda for the IETF 58 PANA WG meeting.
Comments welcome.

- Chairs

Protocol for Carrying Authentication for Network Access (PANA)

Tuesday, November 11 at 0900-1130
==================================

CHAIRS:    

  Basavaraj Patil <Basavaraj.Patil@nokia.com>
  Alper Yegin <alper@docomolabs-usa.com>

AGENDA:

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

2. PANA protocol update and open issues: 30 min, Yoshihiro Ohba

3. PAA-to-EP protocol considerations: 10 min, Yacine El Mghazli

4. PANA-IPsec I-D update: 10 min, Mohan Parthasarathy

5. PANA state machine considerations: 20 min, Dan Forsberg

6. Implementation report: 10 min, Victor Fajardo; 10 min, Hannes Tschofenig

7. Next steps: 5 min, Chairs/ADs



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



From pana-admin@ietf.org  Tue Oct 28 08:48:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20094
	for <pana-archive@lists.ietf.org>; Tue, 28 Oct 2003 08:48:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUCX-0005DK-AR; Tue, 28 Oct 2003 08:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUBb-0004sL-Pr
	for pana@optimus.ietf.org; Tue, 28 Oct 2003 08:47:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20008
	for <pana@ietf.org>; Tue, 28 Oct 2003 08:46:52 -0500 (EST)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEUBa-0002vE-00
	for pana@ietf.org; Tue, 28 Oct 2003 08:47:02 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEUBZ-0002v4-00
	for pana@ietf.org; Tue, 28 Oct 2003 08:47:01 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9SDkjI22740
	for <pana@ietf.org>; Tue, 28 Oct 2003 15:46:45 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T658fc8e88eac158f25bf6@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Tue, 28 Oct 2003 15:46:45 +0200
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 28 Oct 2003 15:46:45 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 Oct 2003 15:46:23 +0200
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6DC6@esebe008.ntc.nokia.com>
Thread-Topic: [Issue28] PANA state machines
Thread-Index: AcOdWeANexnkOAVZSyy/G+gs1fsMDA==
To: <pana@ietf.org>
X-OriginalArrivalTime: 28 Oct 2003 13:46:45.0580 (UTC) FILETIME=[ED5310C0:01C39D59]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [Issue28] PANA state machines
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi,

I've updated PANA state machines (PaC v0.4, PAA v0.3).=20
See the change logs and state machines:
http://danforsberg.info:8080/pana-issues/issue28

I hope I have incorporated all the comments received, but=20
there certainly are more issues to discuss.=20

PANA State machines will be discussed during the IETF=20
meeting. Please give comments and any feedback prior the
meeting so that we can have a constructive discussion also
during the meeting.

There is also this question of how we will incorporate=20
these lollipop state machines into the draft.

Br,
- Dan

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


From exim@www1.ietf.org  Tue Oct 28 08:48:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20111
	for <pana-archive@odin.ietf.org>; Tue, 28 Oct 2003 08:48:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUCa-0005EJ-J3
	for pana-archive@odin.ietf.org; Tue, 28 Oct 2003 08:48:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9SDm4Qg020096
	for pana-archive@odin.ietf.org; Tue, 28 Oct 2003 08:48:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUCa-0005E3-DV
	for pana-web-archive@optimus.ietf.org; Tue, 28 Oct 2003 08:48:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20061
	for <pana-web-archive@ietf.org>; Tue, 28 Oct 2003 08:47:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEUCZ-0002vr-00
	for pana-web-archive@ietf.org; Tue, 28 Oct 2003 08:48:03 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEUCY-0002vn-00
	for pana-web-archive@ietf.org; Tue, 28 Oct 2003 08:48:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUCX-0005DK-AR; Tue, 28 Oct 2003 08:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUBb-0004sL-Pr
	for pana@optimus.ietf.org; Tue, 28 Oct 2003 08:47:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20008
	for <pana@ietf.org>; Tue, 28 Oct 2003 08:46:52 -0500 (EST)
From: Dan.Forsberg@nokia.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEUBa-0002vE-00
	for pana@ietf.org; Tue, 28 Oct 2003 08:47:02 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEUBZ-0002v4-00
	for pana@ietf.org; Tue, 28 Oct 2003 08:47:01 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37])
	by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id h9SDkjI22740
	for <pana@ietf.org>; Tue, 28 Oct 2003 15:46:45 +0200 (EET)
Received: from esebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T658fc8e88eac158f25bf6@esvir05nok.ntc.nokia.com> for <pana@ietf.org>;
 Tue, 28 Oct 2003 15:46:45 +0200
Received: from esebe008.NOE.Nokia.com ([172.21.138.48]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 28 Oct 2003 15:46:45 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 Oct 2003 15:46:23 +0200
Message-ID: <FC5FF66A769AB044AED651C705EAA8EA015F6DC6@esebe008.ntc.nokia.com>
Thread-Topic: [Issue28] PANA state machines
Thread-Index: AcOdWeANexnkOAVZSyy/G+gs1fsMDA==
To: <pana@ietf.org>
X-OriginalArrivalTime: 28 Oct 2003 13:46:45.0580 (UTC) FILETIME=[ED5310C0:01C39D59]
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] [Issue28] PANA state machines
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi,

I've updated PANA state machines (PaC v0.4, PAA v0.3).=20
See the change logs and state machines:
http://danforsberg.info:8080/pana-issues/issue28

I hope I have incorporated all the comments received, but=20
there certainly are more issues to discuss.=20

PANA State machines will be discussed during the IETF=20
meeting. Please give comments and any feedback prior the
meeting so that we can have a constructive discussion also
during the meeting.

There is also this question of how we will incorporate=20
these lollipop state machines into the draft.

Br,
- Dan

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



From pana-admin@ietf.org  Tue Oct 28 09:27:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23230
	for <pana-archive@lists.ietf.org>; Tue, 28 Oct 2003 09:27:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUoI-0002pn-4T; Tue, 28 Oct 2003 09:27:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUnv-0002nP-OH
	for pana@optimus.ietf.org; Tue, 28 Oct 2003 09:26:39 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23119;
	Tue, 28 Oct 2003 09:26:27 -0500 (EST)
Message-Id: <200310281426.JAA23119@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 28 Oct 2003 09:26:27 -0500
Subject: [Pana] I-D ACTION:draft-ietf-pana-pana-02.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

--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
	Filename	: draft-ietf-pana-pana-02.txt
	Pages		: 71
	Date		: 2003-10-27
	
This document defines the Protocol for Carrying Authentication for 
Network Access (PANA), a link-layer agnostic transport for 
Extensible Authentication Protocol (EAP) to enable network access 
authentication between clients and access networks. PANA can carry 
any authentication method that can be specified as an EAP method, 
and can be used on any link that can carry IP. PANA covers the 
client-to-network access authentication part of an overall secure 
network access framework, which additionally includes other 
protocols and mechanisms for service provisioning, access control as 
a result of initial authentication, and accounting.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-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-pana-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:	<2003-10-28094735.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--



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


From exim@www1.ietf.org  Tue Oct 28 09:27:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23245
	for <pana-archive@odin.ietf.org>; Tue, 28 Oct 2003 09:27:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUoK-0002r4-4O
	for pana-archive@odin.ietf.org; Tue, 28 Oct 2003 09:27:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9SER4nG010968
	for pana-archive@odin.ietf.org; Tue, 28 Oct 2003 09:27:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUoK-0002qp-0Z
	for pana-web-archive@optimus.ietf.org; Tue, 28 Oct 2003 09:27:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23199
	for <pana-web-archive@ietf.org>; Tue, 28 Oct 2003 09:26:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEUoI-0003ih-00
	for pana-web-archive@ietf.org; Tue, 28 Oct 2003 09:27:02 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEUoI-0003ie-00
	for pana-web-archive@ietf.org; Tue, 28 Oct 2003 09:27:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUoI-0002pn-4T; Tue, 28 Oct 2003 09:27:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEUnv-0002nP-OH
	for pana@optimus.ietf.org; Tue, 28 Oct 2003 09:26:39 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23119;
	Tue, 28 Oct 2003 09:26:27 -0500 (EST)
Message-Id: <200310281426.JAA23119@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: pana@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Tue, 28 Oct 2003 09:26:27 -0500
Subject: [Pana] I-D ACTION:draft-ietf-pana-pana-02.txt
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

--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
	Filename	: draft-ietf-pana-pana-02.txt
	Pages		: 71
	Date		: 2003-10-27
	
This document defines the Protocol for Carrying Authentication for 
Network Access (PANA), a link-layer agnostic transport for 
Extensible Authentication Protocol (EAP) to enable network access 
authentication between clients and access networks. PANA can carry 
any authentication method that can be specified as an EAP method, 
and can be used on any link that can carry IP. PANA covers the 
client-to-network access authentication part of an overall secure 
network access framework, which additionally includes other 
protocols and mechanisms for service provisioning, access control as 
a result of initial authentication, and accounting.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-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-pana-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:	<2003-10-28094735.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--



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



From pana-admin@ietf.org  Tue Oct 28 21:01:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16361
	for <pana-archive@lists.ietf.org>; Tue, 28 Oct 2003 21:01:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEfdt-0000hl-H4; Tue, 28 Oct 2003 21:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEfdS-0000g7-Ig
	for pana@optimus.ietf.org; Tue, 28 Oct 2003 21:00:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16318
	for <pana@ietf.org>; Tue, 28 Oct 2003 21:00:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEfdP-0005uz-00
	for pana@ietf.org; Tue, 28 Oct 2003 21:00:31 -0500
Received: from mta4.srv.hcvlny.cv.net ([167.206.5.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEfdP-0005uw-00
	for pana@ietf.org; Tue, 28 Oct 2003 21:00:31 -0500
Received: from TOSHI2004 (ool-4350d5b6.dyn.optonline.net [67.80.213.182])
 by mta4.srv.hcvlny.cv.net
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with SMTP id <0HNH00K8BXJHDZ@mta4.srv.hcvlny.cv.net> for pana@ietf.org; Tue,
 28 Oct 2003 20:59:55 -0500 (EST)
Date: Tue, 28 Oct 2003 20:59:40 -0500
From: Victor Fajardo <vfajardo@optonline.net>
To: pana@ietf.org
Message-id: <049a01c39dc0$55c74430$b19dfea9@TOSHI2004>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
Content-type: multipart/alternative;
 boundary="Boundary_(ID_v2TAMfhMRXqAsU2dwxLonw)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [Pana] PANA implementation is now available under Open Diameter 1.0.5
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

--Boundary_(ID_v2TAMfhMRXqAsU2dwxLonw)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

Open Diameter Release 1.0.5 is now available. The main focus of this
release is the PANA implemenation and addition of new EAP mechanisms
specifically EAP-Archie.

Release Version : 1.0.5
Release Date    : 10/28/2003

The main features for this release are as follows:

1 PANA library

            A PANA implementation based on draft-ietf-pana-pana-01.txt
            document has now been included in the Open Diameter release.
            The API for this library as well as accompanying documentation
            can be found in the Open Diameter doc section. As noted in the draft,
            PANA must be used in conjunction with EAP. The sample code
            that comes with the PANA library shows usage information on
            how to integrate PANA and EAP. The PANA library uses the 
            EAP library that comes with the Open Diameter distribution.
            However, PANA and EAP libraries does not have hard dependecies.
            PAN can be used with other EAP implementations and vice versa.
            Additional notes and documentation, can be found in the PANA
            library directory. Also note that for windows, a PANA packet
            filtering driver is required. Building and installing the
            driver is also found in the documentations under the PANA 
            library directory. For linux/unix, PANA is required to run
            under priveledge (root/super user) mode since it is using
            PF_SOCKET sockets.

            Note that for linux and windows, the PANA library is 
            included in the opendiameter-1.0.5.tar.gz 
            distribution. In addition, the PANA library has a
            separate setup file for source and binaries under 
            windows. This is in pana-1.0.0.zip distribution.

2 EAP-Archie library

            An EAP-Archie implementation as defined in draft-jwalker-eap-archie-01.txt
            is now available under the Open Diameter umbrella. EAP-Archie 
            defines a new EAP authentication scheme and is built on around 
            the Open Diameter EAP library. Additional notes and documentation 
            can be found in the libeap/eap-archie directory. In particular, 
            the sample test code describes implementation details on EAP-Archie 
            state machine. EAP-Archie API is exposed via the header files in
            libeap/eap-archie directory. As with the rest of the Open Diameter
            libraries, EAP-Archie is available under windows and linux/unix.

3 Microsoft VC++ 7.1 Support

            Microsoft .NET 2003 support has now been added to the Open
            Diameter distribution. A solutions file can be found in the
            Solutions directory of the distribution. It is important to
            note that this migration has become mandatory since there
            has been run-time issues with Open Diameter and VC++ 6.0
            specially with the use of the boost libraries. Targets are
            now generated within the directory structure of the Solutions 
            directory. Output binaries can be found in Solutions/Debug or
            Solutions/Release directories and intermediate files as well
            as debug databases are found within thier respective sub-
            directories. Note also the paths to third-party libraries 
            and include files (ACE, Xerces and boosts) needs to be set 
            in the user options of the .NET environment. (i.e. Tools->
            Options->Projects->VC ++ Directories). Further details about 
            this build environment can be found in the docs directory
            under msvc-solution-usage.txt.

--Boundary_(ID_v2TAMfhMRXqAsU2dwxLonw)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1264" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>
<DIV>Open Diameter Release 1.0.5 is now available. The main focus of this</DIV>
<DIV>release is the PANA implemenation and addition of new EAP mechanisms</DIV>
<DIV>specifically EAP-Archie.<BR><BR>Release Version : 1.0.5<BR>Release 
Date&nbsp;&nbsp;&nbsp; : 10/28/2003<BR></DIV>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>The main 
features for this release are as follows:<BR><BR>1 PANA 
library<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
A PANA implementation based on 
draft-ietf-pana-pana-01.txt<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
document has now been included in the Open Diameter 
release.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
The API for this library as well as accompanying 
documentation<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
can be found in the Open Diameter doc section. As noted in the 
draft,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
PANA must be used in conjunction with EAP. The sample 
code<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that 
comes with the PANA library shows usage information 
on<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to 
integrate PANA and EAP. The PANA library uses the 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; EAP 
library that comes with the Open Diameter 
distribution.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
However, PANA and EAP libraries does not have hard 
dependecies.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
PAN can be used with other EAP implementations and vice 
versa.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Additional notes and documentation, can be found in the 
PANA<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
library directory. Also note that for windows, a PANA 
packet<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
filtering driver is required. Building and installing 
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; driver 
is also found in the documentations under the PANA 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; library 
directory. For linux/unix, PANA is required to 
run<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; under 
priveledge (root/super user) mode since it is 
using<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
PF_SOCKET 
sockets.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Note that for linux and windows, the PANA library is 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; included 
in the opendiameter-1.0.5.tar.gz 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
distribution. In addition, the PANA library has 
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; separate 
setup file for source and binaries under 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; windows. 
This is in pana-1.0.0.zip distribution.<BR><BR>2 EAP-Archie 
library<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
An EAP-Archie implementation as defined in 
draft-jwalker-eap-archie-01.txt<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
is now available under the Open Diameter umbrella. EAP-Archie 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defines a 
new EAP authentication scheme and is built on around 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Open 
Diameter EAP library. Additional notes and documentation 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; can be 
found in the libeap/eap-archie directory. In particular, 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the 
sample test code describes implementation details on EAP-Archie 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; state 
machine. EAP-Archie API is exposed via the header files 
in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
libeap/eap-archie directory. As with the rest of the Open 
Diameter<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
libraries, EAP-Archie is available under windows and linux/unix.<BR><BR>3 
Microsoft VC++ 7.1 
Support<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Microsoft .NET 2003 support has now been added to the 
Open<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Diameter distribution. A solutions file can be found in 
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Solutions directory of the distribution. It is important 
to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; note 
that this migration has become mandatory since 
there<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; has 
been run-time issues with Open Diameter and VC++ 
6.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
specially with the use of the boost libraries. Targets 
are<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; now 
generated within the directory structure of the Solutions 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
directory. Output binaries can be found in Solutions/Debug 
or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Solutions/Release directories and intermediate files as 
well<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; as 
debug databases are found within thier respective 
sub-<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
directories. Note also the paths to third-party libraries 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and 
include files (ACE, Xerces and boosts) needs to be set 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the 
user options of the .NET environment. (i.e. 
Tools-&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Options-&gt;Projects-&gt;VC ++ Directories). Further details about 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this 
build environment can be found in the docs 
directory<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
under msvc-solution-usage.txt.<BR></FONT></FONT></DIV></FONT></FONT><FONT 
face=Arial size=2></DIV></FONT></FONT></DIV></BODY></HTML>

--Boundary_(ID_v2TAMfhMRXqAsU2dwxLonw)--

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


From exim@www1.ietf.org  Tue Oct 28 21:01:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16378
	for <pana-archive@odin.ietf.org>; Tue, 28 Oct 2003 21:01:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEfdy-0000in-D6
	for pana-archive@odin.ietf.org; Tue, 28 Oct 2003 21:01:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9T216v0002767
	for pana-archive@odin.ietf.org; Tue, 28 Oct 2003 21:01:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEfdy-0000iY-8G
	for pana-web-archive@optimus.ietf.org; Tue, 28 Oct 2003 21:01:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16344
	for <pana-web-archive@ietf.org>; Tue, 28 Oct 2003 21:00:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEfdv-0005vg-00
	for pana-web-archive@ietf.org; Tue, 28 Oct 2003 21:01:03 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEfdu-0005vP-00
	for pana-web-archive@ietf.org; Tue, 28 Oct 2003 21:01:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEfdt-0000hl-H4; Tue, 28 Oct 2003 21:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEfdS-0000g7-Ig
	for pana@optimus.ietf.org; Tue, 28 Oct 2003 21:00:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16318
	for <pana@ietf.org>; Tue, 28 Oct 2003 21:00:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEfdP-0005uz-00
	for pana@ietf.org; Tue, 28 Oct 2003 21:00:31 -0500
Received: from mta4.srv.hcvlny.cv.net ([167.206.5.70])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEfdP-0005uw-00
	for pana@ietf.org; Tue, 28 Oct 2003 21:00:31 -0500
Received: from TOSHI2004 (ool-4350d5b6.dyn.optonline.net [67.80.213.182])
 by mta4.srv.hcvlny.cv.net
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with SMTP id <0HNH00K8BXJHDZ@mta4.srv.hcvlny.cv.net> for pana@ietf.org; Tue,
 28 Oct 2003 20:59:55 -0500 (EST)
Date: Tue, 28 Oct 2003 20:59:40 -0500
From: Victor Fajardo <vfajardo@optonline.net>
To: pana@ietf.org
Message-id: <049a01c39dc0$55c74430$b19dfea9@TOSHI2004>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
Content-type: multipart/alternative;
 boundary="Boundary_(ID_v2TAMfhMRXqAsU2dwxLonw)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [Pana] PANA implementation is now available under Open Diameter 1.0.5
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

--Boundary_(ID_v2TAMfhMRXqAsU2dwxLonw)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

Open Diameter Release 1.0.5 is now available. The main focus of this
release is the PANA implemenation and addition of new EAP mechanisms
specifically EAP-Archie.

Release Version : 1.0.5
Release Date    : 10/28/2003

The main features for this release are as follows:

1 PANA library

            A PANA implementation based on draft-ietf-pana-pana-01.txt
            document has now been included in the Open Diameter release.
            The API for this library as well as accompanying documentation
            can be found in the Open Diameter doc section. As noted in the draft,
            PANA must be used in conjunction with EAP. The sample code
            that comes with the PANA library shows usage information on
            how to integrate PANA and EAP. The PANA library uses the 
            EAP library that comes with the Open Diameter distribution.
            However, PANA and EAP libraries does not have hard dependecies.
            PAN can be used with other EAP implementations and vice versa.
            Additional notes and documentation, can be found in the PANA
            library directory. Also note that for windows, a PANA packet
            filtering driver is required. Building and installing the
            driver is also found in the documentations under the PANA 
            library directory. For linux/unix, PANA is required to run
            under priveledge (root/super user) mode since it is using
            PF_SOCKET sockets.

            Note that for linux and windows, the PANA library is 
            included in the opendiameter-1.0.5.tar.gz 
            distribution. In addition, the PANA library has a
            separate setup file for source and binaries under 
            windows. This is in pana-1.0.0.zip distribution.

2 EAP-Archie library

            An EAP-Archie implementation as defined in draft-jwalker-eap-archie-01.txt
            is now available under the Open Diameter umbrella. EAP-Archie 
            defines a new EAP authentication scheme and is built on around 
            the Open Diameter EAP library. Additional notes and documentation 
            can be found in the libeap/eap-archie directory. In particular, 
            the sample test code describes implementation details on EAP-Archie 
            state machine. EAP-Archie API is exposed via the header files in
            libeap/eap-archie directory. As with the rest of the Open Diameter
            libraries, EAP-Archie is available under windows and linux/unix.

3 Microsoft VC++ 7.1 Support

            Microsoft .NET 2003 support has now been added to the Open
            Diameter distribution. A solutions file can be found in the
            Solutions directory of the distribution. It is important to
            note that this migration has become mandatory since there
            has been run-time issues with Open Diameter and VC++ 6.0
            specially with the use of the boost libraries. Targets are
            now generated within the directory structure of the Solutions 
            directory. Output binaries can be found in Solutions/Debug or
            Solutions/Release directories and intermediate files as well
            as debug databases are found within thier respective sub-
            directories. Note also the paths to third-party libraries 
            and include files (ACE, Xerces and boosts) needs to be set 
            in the user options of the .NET environment. (i.e. Tools->
            Options->Projects->VC ++ Directories). Further details about 
            this build environment can be found in the docs directory
            under msvc-solution-usage.txt.

--Boundary_(ID_v2TAMfhMRXqAsU2dwxLonw)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1264" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>
<DIV>Open Diameter Release 1.0.5 is now available. The main focus of this</DIV>
<DIV>release is the PANA implemenation and addition of new EAP mechanisms</DIV>
<DIV>specifically EAP-Archie.<BR><BR>Release Version : 1.0.5<BR>Release 
Date&nbsp;&nbsp;&nbsp; : 10/28/2003<BR></DIV>
<DIV><FONT face=Arial size=2><FONT face="Times New Roman" size=3>The main 
features for this release are as follows:<BR><BR>1 PANA 
library<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
A PANA implementation based on 
draft-ietf-pana-pana-01.txt<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
document has now been included in the Open Diameter 
release.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
The API for this library as well as accompanying 
documentation<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
can be found in the Open Diameter doc section. As noted in the 
draft,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
PANA must be used in conjunction with EAP. The sample 
code<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that 
comes with the PANA library shows usage information 
on<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how to 
integrate PANA and EAP. The PANA library uses the 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; EAP 
library that comes with the Open Diameter 
distribution.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
However, PANA and EAP libraries does not have hard 
dependecies.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
PAN can be used with other EAP implementations and vice 
versa.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Additional notes and documentation, can be found in the 
PANA<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
library directory. Also note that for windows, a PANA 
packet<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
filtering driver is required. Building and installing 
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; driver 
is also found in the documentations under the PANA 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; library 
directory. For linux/unix, PANA is required to 
run<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; under 
priveledge (root/super user) mode since it is 
using<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
PF_SOCKET 
sockets.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Note that for linux and windows, the PANA library is 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; included 
in the opendiameter-1.0.5.tar.gz 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
distribution. In addition, the PANA library has 
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; separate 
setup file for source and binaries under 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; windows. 
This is in pana-1.0.0.zip distribution.<BR><BR>2 EAP-Archie 
library<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
An EAP-Archie implementation as defined in 
draft-jwalker-eap-archie-01.txt<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
is now available under the Open Diameter umbrella. EAP-Archie 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defines a 
new EAP authentication scheme and is built on around 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Open 
Diameter EAP library. Additional notes and documentation 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; can be 
found in the libeap/eap-archie directory. In particular, 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the 
sample test code describes implementation details on EAP-Archie 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; state 
machine. EAP-Archie API is exposed via the header files 
in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
libeap/eap-archie directory. As with the rest of the Open 
Diameter<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
libraries, EAP-Archie is available under windows and linux/unix.<BR><BR>3 
Microsoft VC++ 7.1 
Support<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Microsoft .NET 2003 support has now been added to the 
Open<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Diameter distribution. A solutions file can be found in 
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Solutions directory of the distribution. It is important 
to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; note 
that this migration has become mandatory since 
there<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; has 
been run-time issues with Open Diameter and VC++ 
6.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
specially with the use of the boost libraries. Targets 
are<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; now 
generated within the directory structure of the Solutions 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
directory. Output binaries can be found in Solutions/Debug 
or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Solutions/Release directories and intermediate files as 
well<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; as 
debug databases are found within thier respective 
sub-<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
directories. Note also the paths to third-party libraries 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and 
include files (ACE, Xerces and boosts) needs to be set 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the 
user options of the .NET environment. (i.e. 
Tools-&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Options-&gt;Projects-&gt;VC ++ Directories). Further details about 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this 
build environment can be found in the docs 
directory<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
under msvc-solution-usage.txt.<BR></FONT></FONT></DIV></FONT></FONT><FONT 
face=Arial size=2></DIV></FONT></FONT></DIV></BODY></HTML>

--Boundary_(ID_v2TAMfhMRXqAsU2dwxLonw)--

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



From pana-admin@ietf.org  Wed Oct 29 00:14:19 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25016
	for <pana-archive@lists.ietf.org>; Wed, 29 Oct 2003 00:14:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEief-0006NF-7J; Wed, 29 Oct 2003 00:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEieW-0006Il-VH
	for pana@optimus.ietf.org; Wed, 29 Oct 2003 00:13:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24902
	for <pana@ietf.org>; Wed, 29 Oct 2003 00:13:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEieT-0001Wy-00
	for pana@ietf.org; Wed, 29 Oct 2003 00:13:49 -0500
Received: from mta3.srv.hcvlny.cv.net ([167.206.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEieT-0001Ws-00
	for pana@ietf.org; Wed, 29 Oct 2003 00:13:49 -0500
Received: from TOSHI2004 (ool-4350d5b6.dyn.optonline.net [67.80.213.182])
 by mta3.srv.hcvlny.cv.net
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with SMTP id <0HNI00CF00N2N4@mta3.srv.hcvlny.cv.net> for pana@ietf.org; Tue,
 28 Oct 2003 22:06:44 -0500 (EST)
Date: Tue, 28 Oct 2003 22:06:14 -0500
From: Victor Fajardo <vfajardo@optonline.net>
To: pana@ietf.org
Message-id: <04c501c39dc9$ae9ba890$b19dfea9@TOSHI2004>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
Content-type: multipart/alternative;
 boundary="Boundary_(ID_wMWR02/q2Swul7lEJ3YDLw)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [Pana] PANA implementation supplemental information
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

--Boundary_(ID_wMWR02/q2Swul7lEJ3YDLw)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

The open source PANA implementation covered under the Open Diameter library (1.0.5) umbrella is located in:

http://www.opendiameter.org

-- Victor Fajardo

--Boundary_(ID_wMWR02/q2Swul7lEJ3YDLw)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1264" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>The open source PANA implementation&nbsp;covered 
under the Open Diameter library (1.0.5) umbrella is located in:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><A 
href="http://www.opendiameter.org">http://www.opendiameter.org</A></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>-- Victor Fajardo</FONT></DIV></BODY></HTML>

--Boundary_(ID_wMWR02/q2Swul7lEJ3YDLw)--

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


From exim@www1.ietf.org  Wed Oct 29 00:14:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25031
	for <pana-archive@odin.ietf.org>; Wed, 29 Oct 2003 00:14:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEieg-0006OF-Uj
	for pana-archive@odin.ietf.org; Wed, 29 Oct 2003 00:14:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9T5E263024557
	for pana-archive@odin.ietf.org; Wed, 29 Oct 2003 00:14:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEieg-0006O0-Pk
	for pana-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 00:14:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24950
	for <pana-web-archive@ietf.org>; Wed, 29 Oct 2003 00:13:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEiee-0001Xm-00
	for pana-web-archive@ietf.org; Wed, 29 Oct 2003 00:14:00 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEied-0001Xj-00
	for pana-web-archive@ietf.org; Wed, 29 Oct 2003 00:13:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEief-0006NF-7J; Wed, 29 Oct 2003 00:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEieW-0006Il-VH
	for pana@optimus.ietf.org; Wed, 29 Oct 2003 00:13:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24902
	for <pana@ietf.org>; Wed, 29 Oct 2003 00:13:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEieT-0001Wy-00
	for pana@ietf.org; Wed, 29 Oct 2003 00:13:49 -0500
Received: from mta3.srv.hcvlny.cv.net ([167.206.5.69])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEieT-0001Ws-00
	for pana@ietf.org; Wed, 29 Oct 2003 00:13:49 -0500
Received: from TOSHI2004 (ool-4350d5b6.dyn.optonline.net [67.80.213.182])
 by mta3.srv.hcvlny.cv.net
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with SMTP id <0HNI00CF00N2N4@mta3.srv.hcvlny.cv.net> for pana@ietf.org; Tue,
 28 Oct 2003 22:06:44 -0500 (EST)
Date: Tue, 28 Oct 2003 22:06:14 -0500
From: Victor Fajardo <vfajardo@optonline.net>
To: pana@ietf.org
Message-id: <04c501c39dc9$ae9ba890$b19dfea9@TOSHI2004>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
Content-type: multipart/alternative;
 boundary="Boundary_(ID_wMWR02/q2Swul7lEJ3YDLw)"
X-Priority: 3
X-MSMail-priority: Normal
Subject: [Pana] PANA implementation supplemental information
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

--Boundary_(ID_wMWR02/q2Swul7lEJ3YDLw)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

The open source PANA implementation covered under the Open Diameter library (1.0.5) umbrella is located in:

http://www.opendiameter.org

-- Victor Fajardo

--Boundary_(ID_wMWR02/q2Swul7lEJ3YDLw)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1264" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>The open source PANA implementation&nbsp;covered 
under the Open Diameter library (1.0.5) umbrella is located in:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2><A 
href="http://www.opendiameter.org">http://www.opendiameter.org</A></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>-- Victor Fajardo</FONT></DIV></BODY></HTML>

--Boundary_(ID_wMWR02/q2Swul7lEJ3YDLw)--

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



From pana-admin@ietf.org  Wed Oct 29 01:51:26 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27917
	for <pana-archive@lists.ietf.org>; Wed, 29 Oct 2003 01:51:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEkAX-000361-Hq; Wed, 29 Oct 2003 01:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEf87-0005KK-Lv
	for pana@optimus.ietf.org; Tue, 28 Oct 2003 20:28:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14593
	for <pana@ietf.org>; Tue, 28 Oct 2003 20:27:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEf80-0005H8-00
	for pana@ietf.org; Tue, 28 Oct 2003 20:28:04 -0500
Received: from [206.246.200.180] (helo=mail.mailsnare.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEf7z-0005Gu-00
	for pana@ietf.org; Tue, 28 Oct 2003 20:28:03 -0500
Received: from localhost (unknown [206.246.200.185])
	by anti-virus.mailsnare.net (Postfix) with ESMTP id D7A7E4050F
	for <pana@ietf.org>; Wed, 29 Oct 2003 01:26:15 +0000 (UTC)
Received: from mail.mailsnare.net ([206.246.200.166])
 by localhost (mail.mailsnare.net [206.246.200.185]) (amavisd-new, port 10024)
 with ESMTP id 26272-01 for <pana@ietf.org>;
 Tue, 28 Oct 2003 18:28:18 +0000 (GMT)
Received: from TOSHI2004 (ool-4350d5b6.dyn.optonline.net [67.80.213.182])
	by mail.mailsnare.net (Postfix) with SMTP id 859C910E6DD
	for <pana@ietf.org>; Wed, 29 Oct 2003 01:25:34 +0000 (UTC)
Message-ID: <044901c39dbb$e22f6d30$b19dfea9@TOSHI2004>
From: "Victor Fajardo" <vfajardo@msbx.net>
To: <pana@ietf.org>
Date: Tue, 28 Oct 2003 20:27:57 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0446_01C39D91.F917C850"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: [Pana] PANA implementation is now available under Open Diameter 1.0.5
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0446_01C39D91.F917C850
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Open Diameter Release 1.0.5 is now available. The main focus of this
release is the PANA implemenation and addition of new EAP mechanisms
specifically EAP-Archie.

Release Version : 1.0.5
Release Date    : 10/28/2003

The main features for this release are as follows:

1 PANA library

            A PANA implementation based on draft-ietf-pana-pana-01.txt
            document has now been included in the Open Diameter release.
            The API for this library as well as accompanying =
documentation
            can be found in the Open Diameter doc section. As noted in =
the draft,
            PANA must be used in conjunction with EAP. The sample code
            that comes with the PANA library shows usage information on
            how to integrate PANA and EAP. The PANA library uses the=20
            EAP library that comes with the Open Diameter distribution.
            However, PANA and EAP libraries does not have hard =
dependecies.
            PAN can be used with other EAP implementations and vice =
versa.
            Additional notes and documentation, can be found in the PANA
            library directory. Also note that for windows, a PANA packet
            filtering driver is required. Building and installing the
            driver is also found in the documentations under the PANA=20
            library directory. For linux/unix, PANA is required to run
            under priveledge (root/super user) mode since it is using
            PF_SOCKET sockets.

            Note that for linux and windows, the PANA library is=20
            included in the opendiameter-1.0.5.tar.gz=20
            distribution. In addition, the PANA library has a
            separate setup file for source and binaries under=20
            windows. This is in pana-1.0.0.zip distribution.

2 EAP-Archie library

            An EAP-Archie implementation as defined in =
draft-jwalker-eap-archie-01.txt
            is now available under the Open Diameter umbrella. =
EAP-Archie=20
            defines a new EAP authentication scheme and is built on =
around=20
            the Open Diameter EAP library. Additional notes and =
documentation=20
            can be found in the libeap/eap-archie directory. In =
particular,=20
            the sample test code describes implementation details on =
EAP-Archie=20
            state machine. EAP-Archie API is exposed via the header =
files in
            libeap/eap-archie directory. As with the rest of the Open =
Diameter
            libraries, EAP-Archie is available under windows and =
linux/unix.

3 Microsoft VC++ 7.1 Support

            Microsoft .NET 2003 support has now been added to the Open
            Diameter distribution. A solutions file can be found in the
            Solutions directory of the distribution. It is important to
            note that this migration has become mandatory since there
            has been run-time issues with Open Diameter and VC++ 6.0
            specially with the use of the boost libraries. Targets are
            now generated within the directory structure of the =
Solutions=20
            directory. Output binaries can be found in Solutions/Debug =
or
            Solutions/Release directories and intermediate files as well
            as debug databases are found within thier respective sub-
            directories. Note also the paths to third-party libraries=20
            and include files (ACE, Xerces and boosts) needs to be set=20
            in the user options of the .NET environment. (i.e. Tools->
            Options->Projects->VC ++ Directories). Further details about =

            this build environment can be found in the docs directory
            under msvc-solution-usage.txt.

------=_NextPart_000_0446_01C39D91.F917C850
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1264" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>
<DIV>Open Diameter Release 1.0.5 is now available. The main focus of =
this</DIV>
<DIV>release is the PANA implemenation and addition of new EAP =
mechanisms</DIV>
<DIV>specifically EAP-Archie.<BR><BR>Release Version : 1.0.5<BR>Release=20
Date&nbsp;&nbsp;&nbsp; : 10/28/2003<BR></DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>The main=20
features for this release are as follows:<BR><BR>1 PANA=20
library<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
A PANA implementation based on=20
draft-ietf-pana-pana-01.txt<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;=20
document has now been included in the Open Diameter=20
release.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
The API for this library as well as accompanying=20
documentation<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
can be found in the Open Diameter doc section. As noted in the=20
draft,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
PANA must be used in conjunction with EAP. The sample=20
code<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; that=20
comes with the PANA library shows usage information=20
on<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
how to=20
integrate PANA and EAP. The PANA library uses the=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
EAP=20
library that comes with the Open Diameter=20
distribution.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
However, PANA and EAP libraries does not have hard=20
dependecies.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
PAN can be used with other EAP implementations and vice=20
versa.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
Additional notes and documentation, can be found in the=20
PANA<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
library directory. Also note that for windows, a PANA=20
packet<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
filtering driver is required. Building and installing=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 driver=20
is also found in the documentations under the PANA=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
library=20
directory. For linux/unix, PANA is required to=20
run<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 under=20
priveledge (root/super user) mode since it is=20
using<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
PF_SOCKET=20
sockets.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
Note that for linux and windows, the PANA library is=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
included=20
in the opendiameter-1.0.5.tar.gz=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
distribution. In addition, the PANA library has=20
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
separate=20
setup file for source and binaries under=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
windows.=20
This is in pana-1.0.0.zip distribution.<BR><BR>2 EAP-Archie=20
library<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
An EAP-Archie implementation as defined in=20
draft-jwalker-eap-archie-01.txt<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
is now available under the Open Diameter umbrella. EAP-Archie=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
defines a=20
new EAP authentication scheme and is built on around=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the Open=20
Diameter EAP library. Additional notes and documentation=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
can be=20
found in the libeap/eap-archie directory. In particular,=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the=20
sample test code describes implementation details on EAP-Archie=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
state=20
machine. EAP-Archie API is exposed via the header files=20
in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

libeap/eap-archie directory. As with the rest of the Open=20
Diameter<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
libraries, EAP-Archie is available under windows and =
linux/unix.<BR><BR>3=20
Microsoft VC++ 7.1=20
Support<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
Microsoft .NET 2003 support has now been added to the=20
Open<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
Diameter distribution. A solutions file can be found in=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
Solutions directory of the distribution. It is important=20
to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
note=20
that this migration has become mandatory since=20
there<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; has=20
been run-time issues with Open Diameter and VC++=20
6.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
specially with the use of the boost libraries. Targets=20
are<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 now=20
generated within the directory structure of the Solutions=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
directory. Output binaries can be found in Solutions/Debug=20
or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

Solutions/Release directories and intermediate files as=20
well<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; as=20
debug databases are found within thier respective=20
sub-<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
directories. Note also the paths to third-party libraries=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
and=20
include files (ACE, Xerces and boosts) needs to be set=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
in the=20
user options of the .NET environment. (i.e.=20
Tools-&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
Options-&gt;Projects-&gt;VC ++ Directories). Further details about=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
this=20
build environment can be found in the docs=20
directory<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
under =
msvc-solution-usage.txt.<BR></FONT></FONT></DIV></FONT></FONT><FONT=20
face=3DArial size=3D2></DIV></FONT></BODY></HTML>

------=_NextPart_000_0446_01C39D91.F917C850--


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


From exim@www1.ietf.org  Wed Oct 29 01:51:27 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27932
	for <pana-archive@odin.ietf.org>; Wed, 29 Oct 2003 01:51:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEkAd-00036o-Fq
	for pana-archive@odin.ietf.org; Wed, 29 Oct 2003 01:51:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9T6p7WI011944
	for pana-archive@odin.ietf.org; Wed, 29 Oct 2003 01:51:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEkAd-00036Z-6F
	for pana-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 01:51:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27901
	for <pana-web-archive@ietf.org>; Wed, 29 Oct 2003 01:50:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEkAZ-0002hL-00
	for pana-web-archive@ietf.org; Wed, 29 Oct 2003 01:51:03 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEkAZ-0002hI-00
	for pana-web-archive@ietf.org; Wed, 29 Oct 2003 01:51:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEkAX-000361-Hq; Wed, 29 Oct 2003 01:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEf87-0005KK-Lv
	for pana@optimus.ietf.org; Tue, 28 Oct 2003 20:28:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14593
	for <pana@ietf.org>; Tue, 28 Oct 2003 20:27:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEf80-0005H8-00
	for pana@ietf.org; Tue, 28 Oct 2003 20:28:04 -0500
Received: from [206.246.200.180] (helo=mail.mailsnare.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEf7z-0005Gu-00
	for pana@ietf.org; Tue, 28 Oct 2003 20:28:03 -0500
Received: from localhost (unknown [206.246.200.185])
	by anti-virus.mailsnare.net (Postfix) with ESMTP id D7A7E4050F
	for <pana@ietf.org>; Wed, 29 Oct 2003 01:26:15 +0000 (UTC)
Received: from mail.mailsnare.net ([206.246.200.166])
 by localhost (mail.mailsnare.net [206.246.200.185]) (amavisd-new, port 10024)
 with ESMTP id 26272-01 for <pana@ietf.org>;
 Tue, 28 Oct 2003 18:28:18 +0000 (GMT)
Received: from TOSHI2004 (ool-4350d5b6.dyn.optonline.net [67.80.213.182])
	by mail.mailsnare.net (Postfix) with SMTP id 859C910E6DD
	for <pana@ietf.org>; Wed, 29 Oct 2003 01:25:34 +0000 (UTC)
Message-ID: <044901c39dbb$e22f6d30$b19dfea9@TOSHI2004>
From: "Victor Fajardo" <vfajardo@msbx.net>
To: <pana@ietf.org>
Date: Tue, 28 Oct 2003 20:27:57 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0446_01C39D91.F917C850"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: [Pana] PANA implementation is now available under Open Diameter 1.0.5
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

------=_NextPart_000_0446_01C39D91.F917C850
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Open Diameter Release 1.0.5 is now available. The main focus of this
release is the PANA implemenation and addition of new EAP mechanisms
specifically EAP-Archie.

Release Version : 1.0.5
Release Date    : 10/28/2003

The main features for this release are as follows:

1 PANA library

            A PANA implementation based on draft-ietf-pana-pana-01.txt
            document has now been included in the Open Diameter release.
            The API for this library as well as accompanying =
documentation
            can be found in the Open Diameter doc section. As noted in =
the draft,
            PANA must be used in conjunction with EAP. The sample code
            that comes with the PANA library shows usage information on
            how to integrate PANA and EAP. The PANA library uses the=20
            EAP library that comes with the Open Diameter distribution.
            However, PANA and EAP libraries does not have hard =
dependecies.
            PAN can be used with other EAP implementations and vice =
versa.
            Additional notes and documentation, can be found in the PANA
            library directory. Also note that for windows, a PANA packet
            filtering driver is required. Building and installing the
            driver is also found in the documentations under the PANA=20
            library directory. For linux/unix, PANA is required to run
            under priveledge (root/super user) mode since it is using
            PF_SOCKET sockets.

            Note that for linux and windows, the PANA library is=20
            included in the opendiameter-1.0.5.tar.gz=20
            distribution. In addition, the PANA library has a
            separate setup file for source and binaries under=20
            windows. This is in pana-1.0.0.zip distribution.

2 EAP-Archie library

            An EAP-Archie implementation as defined in =
draft-jwalker-eap-archie-01.txt
            is now available under the Open Diameter umbrella. =
EAP-Archie=20
            defines a new EAP authentication scheme and is built on =
around=20
            the Open Diameter EAP library. Additional notes and =
documentation=20
            can be found in the libeap/eap-archie directory. In =
particular,=20
            the sample test code describes implementation details on =
EAP-Archie=20
            state machine. EAP-Archie API is exposed via the header =
files in
            libeap/eap-archie directory. As with the rest of the Open =
Diameter
            libraries, EAP-Archie is available under windows and =
linux/unix.

3 Microsoft VC++ 7.1 Support

            Microsoft .NET 2003 support has now been added to the Open
            Diameter distribution. A solutions file can be found in the
            Solutions directory of the distribution. It is important to
            note that this migration has become mandatory since there
            has been run-time issues with Open Diameter and VC++ 6.0
            specially with the use of the boost libraries. Targets are
            now generated within the directory structure of the =
Solutions=20
            directory. Output binaries can be found in Solutions/Debug =
or
            Solutions/Release directories and intermediate files as well
            as debug databases are found within thier respective sub-
            directories. Note also the paths to third-party libraries=20
            and include files (ACE, Xerces and boosts) needs to be set=20
            in the user options of the .NET environment. (i.e. Tools->
            Options->Projects->VC ++ Directories). Further details about =

            this build environment can be found in the docs directory
            under msvc-solution-usage.txt.

------=_NextPart_000_0446_01C39D91.F917C850
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1264" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>
<DIV>Open Diameter Release 1.0.5 is now available. The main focus of =
this</DIV>
<DIV>release is the PANA implemenation and addition of new EAP =
mechanisms</DIV>
<DIV>specifically EAP-Archie.<BR><BR>Release Version : 1.0.5<BR>Release=20
Date&nbsp;&nbsp;&nbsp; : 10/28/2003<BR></DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>The main=20
features for this release are as follows:<BR><BR>1 PANA=20
library<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
A PANA implementation based on=20
draft-ietf-pana-pana-01.txt<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;=20
document has now been included in the Open Diameter=20
release.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
The API for this library as well as accompanying=20
documentation<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
can be found in the Open Diameter doc section. As noted in the=20
draft,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
PANA must be used in conjunction with EAP. The sample=20
code<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; that=20
comes with the PANA library shows usage information=20
on<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
how to=20
integrate PANA and EAP. The PANA library uses the=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
EAP=20
library that comes with the Open Diameter=20
distribution.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
However, PANA and EAP libraries does not have hard=20
dependecies.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
PAN can be used with other EAP implementations and vice=20
versa.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
Additional notes and documentation, can be found in the=20
PANA<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
library directory. Also note that for windows, a PANA=20
packet<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
filtering driver is required. Building and installing=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 driver=20
is also found in the documentations under the PANA=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
library=20
directory. For linux/unix, PANA is required to=20
run<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 under=20
priveledge (root/super user) mode since it is=20
using<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
PF_SOCKET=20
sockets.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
Note that for linux and windows, the PANA library is=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
included=20
in the opendiameter-1.0.5.tar.gz=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
distribution. In addition, the PANA library has=20
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
separate=20
setup file for source and binaries under=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
windows.=20
This is in pana-1.0.0.zip distribution.<BR><BR>2 EAP-Archie=20
library<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
An EAP-Archie implementation as defined in=20
draft-jwalker-eap-archie-01.txt<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
is now available under the Open Diameter umbrella. EAP-Archie=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
defines a=20
new EAP authentication scheme and is built on around=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the Open=20
Diameter EAP library. Additional notes and documentation=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
can be=20
found in the libeap/eap-archie directory. In particular,=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
the=20
sample test code describes implementation details on EAP-Archie=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
state=20
machine. EAP-Archie API is exposed via the header files=20
in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

libeap/eap-archie directory. As with the rest of the Open=20
Diameter<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
libraries, EAP-Archie is available under windows and =
linux/unix.<BR><BR>3=20
Microsoft VC++ 7.1=20
Support<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
Microsoft .NET 2003 support has now been added to the=20
Open<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
Diameter distribution. A solutions file can be found in=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
Solutions directory of the distribution. It is important=20
to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
note=20
that this migration has become mandatory since=20
there<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; has=20
been run-time issues with Open Diameter and VC++=20
6.0<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
specially with the use of the boost libraries. Targets=20
are<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 now=20
generated within the directory structure of the Solutions=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
directory. Output binaries can be found in Solutions/Debug=20
or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

Solutions/Release directories and intermediate files as=20
well<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; as=20
debug databases are found within thier respective=20
sub-<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
directories. Note also the paths to third-party libraries=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
and=20
include files (ACE, Xerces and boosts) needs to be set=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
in the=20
user options of the .NET environment. (i.e.=20
Tools-&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
Options-&gt;Projects-&gt;VC ++ Directories). Further details about=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
this=20
build environment can be found in the docs=20
directory<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
under =
msvc-solution-usage.txt.<BR></FONT></FONT></DIV></FONT></FONT><FONT=20
face=3DArial size=3D2></DIV></FONT></BODY></HTML>

------=_NextPart_000_0446_01C39D91.F917C850--


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



From pana-admin@ietf.org  Wed Oct 29 05:34:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01970
	for <pana-archive@lists.ietf.org>; Wed, 29 Oct 2003 05:34:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEneN-0006oA-9O; Wed, 29 Oct 2003 05:34:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEneI-0006nK-AF
	for pana@optimus.ietf.org; Wed, 29 Oct 2003 05:33:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01945
	for <pana@ietf.org>; Wed, 29 Oct 2003 05:33:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEneE-0005k6-00
	for pana@ietf.org; Wed, 29 Oct 2003 05:33:54 -0500
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEneE-0005jg-00
	for pana@ietf.org; Wed, 29 Oct 2003 05:33:54 -0500
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP id 778C635932
	for <pana@ietf.org>; Wed, 29 Oct 2003 11:24:52 +0100 (CET)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP id 630FF3F40C
	for <pana@ietf.org>; Wed, 29 Oct 2003 11:24:52 +0100 (CET)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003102911245206683
 for <pana@ietf.org>; Wed, 29 Oct 2003 11:24:52 +0100
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP id 47ED43F40C
	for <pana@ietf.org>; Wed, 29 Oct 2003 11:24:52 +0100 (CET)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1AEnUe-000C2o-Q6
	for <pana@ietf.org>; Wed, 29 Oct 2003 11:24:00 +0100
Date: Wed, 29 Oct 2003 11:24:00 +0100
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: pana@ietf.org
Message-ID: <20031029102400.GY38466@ipv6-5.int-evry.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA01946
Subject: [Pana] A little typo concerning MAC
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable

Hi all,

 there is a little typo in draft-02 of PANA:

Whereas it is written (=A7 4.1.6) that MAC AVP is calculated by:

MAC AVP value =3D HMAC_SHA1(PANA_MAC_Key, PANA_PDU)

in =A79.4.1 we can use HMAC_MD5 to calculate it.

--=20
julien.bournelle@int-evry.fr

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


From exim@www1.ietf.org  Wed Oct 29 05:34:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01985
	for <pana-archive@odin.ietf.org>; Wed, 29 Oct 2003 05:34:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEneQ-0006oy-Du
	for pana-archive@odin.ietf.org; Wed, 29 Oct 2003 05:34:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9TAY6qV026212
	for pana-archive@odin.ietf.org; Wed, 29 Oct 2003 05:34:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEneP-0006oh-QW
	for pana-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 05:34:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01964
	for <pana-web-archive@ietf.org>; Wed, 29 Oct 2003 05:33:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEneM-0005kI-00
	for pana-web-archive@ietf.org; Wed, 29 Oct 2003 05:34:02 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEneL-0005kF-00
	for pana-web-archive@ietf.org; Wed, 29 Oct 2003 05:34:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEneN-0006oA-9O; Wed, 29 Oct 2003 05:34:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEneI-0006nK-AF
	for pana@optimus.ietf.org; Wed, 29 Oct 2003 05:33:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01945
	for <pana@ietf.org>; Wed, 29 Oct 2003 05:33:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEneE-0005k6-00
	for pana@ietf.org; Wed, 29 Oct 2003 05:33:54 -0500
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEneE-0005jg-00
	for pana@ietf.org; Wed, 29 Oct 2003 05:33:54 -0500
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP id 778C635932
	for <pana@ietf.org>; Wed, 29 Oct 2003 11:24:52 +0100 (CET)
Received: from alpes.int-evry.fr (alpes.int-evry.fr [157.159.10.19])
	by spartebis.int-evry.fr (Postfix) with SMTP id 630FF3F40C
	for <pana@ietf.org>; Wed, 29 Oct 2003 11:24:52 +0100 (CET)
Received: from sparte.int-evry.fr ([157.159.10.11])
 by alpes.int-evry.fr (SAVSMTP 3.0.0.44) with SMTP id M2003102911245206683
 for <pana@ietf.org>; Wed, 29 Oct 2003 11:24:52 +0100
Received: from ipv6-5.int-evry.fr (ipv6-5.int-evry.fr [157.159.100.78])
	by sparte.int-evry.fr (Postfix) with ESMTP id 47ED43F40C
	for <pana@ietf.org>; Wed, 29 Oct 2003 11:24:52 +0100 (CET)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1AEnUe-000C2o-Q6
	for <pana@ietf.org>; Wed, 29 Oct 2003 11:24:00 +0100
Date: Wed, 29 Oct 2003 11:24:00 +0100
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: pana@ietf.org
Message-ID: <20031029102400.GY38466@ipv6-5.int-evry.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA01946
Subject: [Pana] A little typo concerning MAC
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi all,

 there is a little typo in draft-02 of PANA:

Whereas it is written (=A7 4.1.6) that MAC AVP is calculated by:

MAC AVP value =3D HMAC_SHA1(PANA_MAC_Key, PANA_PDU)

in =A79.4.1 we can use HMAC_MD5 to calculate it.

--=20
julien.bournelle@int-evry.fr

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



From pana-admin@ietf.org  Wed Oct 29 18:58:20 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15640
	for <pana-archive@lists.ietf.org>; Wed, 29 Oct 2003 18:58:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0CP-0002vE-J8; Wed, 29 Oct 2003 18:58:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0CM-0002ug-6x
	for pana@optimus.ietf.org; Wed, 29 Oct 2003 18:57:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15609
	for <pana@ietf.org>; Wed, 29 Oct 2003 18:57:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0CG-0007ib-00
	for pana@ietf.org; Wed, 29 Oct 2003 18:57:52 -0500
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0CF-0007iV-00
	for pana@ietf.org; Wed, 29 Oct 2003 18:57:51 -0500
Date: Wed, 29 Oct 2003 15:58:37 -0800
Subject: Re: [Pana] [Issue28] PANA state machines
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBC5942D.B91E%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6DC6@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit



On the PaC state machine:

- The discovery type where PaC receives an unsolicited PANA-start-request is
missing.
- EAP-based reauthentication initiated by PAA is missing.
- According to the latest PANA spec, when the PaC initiates the EAP-based
reauthentication, the PANA-Start-Request/Answer is skipped. This is not
reflected on the state machine.

On the PAA state machine:

- The message "Tx: Reauth Success" for WAIT_REAUTH_ANS to OPEN transition is
not defined by the PANA spec.
- The discovery type where PAA sends an unsolicited PANA-start-request is
missing.

Alper


> Hi,
> 
> I've updated PANA state machines (PaC v0.4, PAA v0.3).
> See the change logs and state machines:
> http://danforsberg.info:8080/pana-issues/issue28
> 
> I hope I have incorporated all the comments received, but
> there certainly are more issues to discuss.
> 
> PANA State machines will be discussed during the IETF
> meeting. Please give comments and any feedback prior the
> meeting so that we can have a constructive discussion also
> during the meeting.
> 
> There is also this question of how we will incorporate
> these lollipop state machines into the draft.
> 
> Br,
> - Dan
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Wed Oct 29 18:58:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15655
	for <pana-archive@odin.ietf.org>; Wed, 29 Oct 2003 18:58:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0CR-0002wA-MN
	for pana-archive@odin.ietf.org; Wed, 29 Oct 2003 18:58:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9TNw3n7011284
	for pana-archive@odin.ietf.org; Wed, 29 Oct 2003 18:58:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0CR-0002vv-Gy
	for pana-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 18:58:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15618
	for <pana-web-archive@ietf.org>; Wed, 29 Oct 2003 18:57:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0CO-0007is-00
	for pana-web-archive@ietf.org; Wed, 29 Oct 2003 18:58:00 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0CO-0007io-00
	for pana-web-archive@ietf.org; Wed, 29 Oct 2003 18:58:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0CP-0002vE-J8; Wed, 29 Oct 2003 18:58:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0CM-0002ug-6x
	for pana@optimus.ietf.org; Wed, 29 Oct 2003 18:57:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15609
	for <pana@ietf.org>; Wed, 29 Oct 2003 18:57:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0CG-0007ib-00
	for pana@ietf.org; Wed, 29 Oct 2003 18:57:52 -0500
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0CF-0007iV-00
	for pana@ietf.org; Wed, 29 Oct 2003 18:57:51 -0500
Date: Wed, 29 Oct 2003 15:58:37 -0800
Subject: Re: [Pana] [Issue28] PANA state machines
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
Message-ID: <BBC5942D.B91E%alper@docomolabs-usa.com>
In-Reply-To: <FC5FF66A769AB044AED651C705EAA8EA015F6DC6@esebe008.ntc.nokia.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



On the PaC state machine:

- The discovery type where PaC receives an unsolicited PANA-start-request is
missing.
- EAP-based reauthentication initiated by PAA is missing.
- According to the latest PANA spec, when the PaC initiates the EAP-based
reauthentication, the PANA-Start-Request/Answer is skipped. This is not
reflected on the state machine.

On the PAA state machine:

- The message "Tx: Reauth Success" for WAIT_REAUTH_ANS to OPEN transition is
not defined by the PANA spec.
- The discovery type where PAA sends an unsolicited PANA-start-request is
missing.

Alper


> Hi,
> 
> I've updated PANA state machines (PaC v0.4, PAA v0.3).
> See the change logs and state machines:
> http://danforsberg.info:8080/pana-issues/issue28
> 
> I hope I have incorporated all the comments received, but
> there certainly are more issues to discuss.
> 
> PANA State machines will be discussed during the IETF
> meeting. Please give comments and any feedback prior the
> meeting so that we can have a constructive discussion also
> during the meeting.
> 
> There is also this question of how we will incorporate
> these lollipop state machines into the draft.
> 
> Br,
> - Dan
> 
> _______________________________________________
> 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-admin@ietf.org  Wed Oct 29 19:42:21 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17160
	for <pana-archive@lists.ietf.org>; Wed, 29 Oct 2003 19:42:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0sy-0006fT-PG; Wed, 29 Oct 2003 19:42:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0sC-0006e9-4u
	for pana@optimus.ietf.org; Wed, 29 Oct 2003 19:41:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17134
	for <pana@ietf.org>; Wed, 29 Oct 2003 19:41:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0sA-00013m-00
	for pana@ietf.org; Wed, 29 Oct 2003 19:41:10 -0500
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0s9-00013i-00
	for pana@ietf.org; Wed, 29 Oct 2003 19:41:09 -0500
Date: Wed, 29 Oct 2003 16:41:57 -0800
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
CC: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>,
        Thomas Narten <narten@us.ibm.com>, <Margaret.Wasserman@nokia.com>
Message-ID: <BBC59E55.B92B%alper@docomolabs-usa.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Agenda for IETF 58 PANA meeting
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit


Protocol for Carrying Authentication for Network Access (PANA)

Tuesday, November 11 at 0900-1130
==================================

CHAIRS:    

  Basavaraj Patil <Basavaraj.Patil@nokia.com>
  Alper Yegin <alper@docomolabs-usa.com>

AGENDA:

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

2. PANA protocol update and open issues: 30 min, Yoshihiro Ohba

   draft-ietf-pana-pana-02.txt. See "Change History" section of the draft
   for the list of issues closed in this revision. Detailed issue
   descriptions can be found at http://danforsberg.info:8080/pana-issues/
   Newly closed issues and currently open issues will be covered in this
   presentation for confirming/achieving consensus.

3. PAA-to-EP protocol considerations: 15 min, Yacine El Mghazli
  
   draft-yacine-pana-paa2ep-prot-eval-00.txt. The objective is to gauge
   consensus of the WG on the selection of the PAA2EP protocol as proposed
   in this I-D. Furthermore, solution-oriented discussions will take place
   based on this proposal (I-D: TBD).

4. PANA-IPsec I-D update: 10 min, Mohan Parthasarathy

   draft-ietf-pana-ipsec-00.txt. Objective is to discuss the latest changes
   (see Revision Log) and confirm consensus.

5. PANA state machine considerations: 20 min, Dan Forsberg

   The discussions will be based on the state machine diagrams provided at
   http://danforsberg.info:8080/pana-issues/issue28.

6. Implementation report: 10 min, Victor Fajardo; 10 min, Hannes Tschofenig

   Reports from people who have been implementing the PANA specification.
   The former implementation was recently published at
   http://www.opendiameter.org/

7. Next steps: 5 min, Chairs/ADs


STATUS of WG I-Ds:

-  draft-ietf-pana-usage-scenarios-06.txt
   WG last call completed on 3/11/03. Draft is sent to ADs for IESG
   consideration.

-  draft-ietf-pana-requirements-07.txt
   WG last call completed on 6/12/03. Draft is sent to ADs for IESG
   consideration.

-  draft-ietf-pana-threats-eval-04.txt
   WG last call completed on 5/1/03. Draft is sent to ADs for IESG
   consideration.

-  draft-ietf-pana-pana-02.txt
   Work in progress. I-D will be discussed at IETF 58.

-  draft-ietf-pana-ipsec-00.txt
   Work in progress. I-D will be discussed at IETF 58.


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


From exim@www1.ietf.org  Wed Oct 29 19:42:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17175
	for <pana-archive@odin.ietf.org>; Wed, 29 Oct 2003 19:42:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0t0-0006g9-4q
	for pana-archive@odin.ietf.org; Wed, 29 Oct 2003 19:42:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9U0g2KW025667
	for pana-archive@odin.ietf.org; Wed, 29 Oct 2003 19:42:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0t0-0006fu-0F
	for pana-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 19:42:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17141
	for <pana-web-archive@ietf.org>; Wed, 29 Oct 2003 19:41:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0sy-000155-00
	for pana-web-archive@ietf.org; Wed, 29 Oct 2003 19:42:00 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0sx-000152-00
	for pana-web-archive@ietf.org; Wed, 29 Oct 2003 19:41:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0sy-0006fT-PG; Wed, 29 Oct 2003 19:42:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF0sC-0006e9-4u
	for pana@optimus.ietf.org; Wed, 29 Oct 2003 19:41:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17134
	for <pana@ietf.org>; Wed, 29 Oct 2003 19:41:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0sA-00013m-00
	for pana@ietf.org; Wed, 29 Oct 2003 19:41:10 -0500
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF0s9-00013i-00
	for pana@ietf.org; Wed, 29 Oct 2003 19:41:09 -0500
Date: Wed, 29 Oct 2003 16:41:57 -0800
From: Alper Yegin <alper@docomolabs-usa.com>
To: <pana@ietf.org>
CC: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>,
        Thomas Narten <narten@us.ibm.com>, <Margaret.Wasserman@nokia.com>
Message-ID: <BBC59E55.B92B%alper@docomolabs-usa.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Pana] Agenda for IETF 58 PANA meeting
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Protocol for Carrying Authentication for Network Access (PANA)

Tuesday, November 11 at 0900-1130
==================================

CHAIRS:    

  Basavaraj Patil <Basavaraj.Patil@nokia.com>
  Alper Yegin <alper@docomolabs-usa.com>

AGENDA:

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

2. PANA protocol update and open issues: 30 min, Yoshihiro Ohba

   draft-ietf-pana-pana-02.txt. See "Change History" section of the draft
   for the list of issues closed in this revision. Detailed issue
   descriptions can be found at http://danforsberg.info:8080/pana-issues/
   Newly closed issues and currently open issues will be covered in this
   presentation for confirming/achieving consensus.

3. PAA-to-EP protocol considerations: 15 min, Yacine El Mghazli
  
   draft-yacine-pana-paa2ep-prot-eval-00.txt. The objective is to gauge
   consensus of the WG on the selection of the PAA2EP protocol as proposed
   in this I-D. Furthermore, solution-oriented discussions will take place
   based on this proposal (I-D: TBD).

4. PANA-IPsec I-D update: 10 min, Mohan Parthasarathy

   draft-ietf-pana-ipsec-00.txt. Objective is to discuss the latest changes
   (see Revision Log) and confirm consensus.

5. PANA state machine considerations: 20 min, Dan Forsberg

   The discussions will be based on the state machine diagrams provided at
   http://danforsberg.info:8080/pana-issues/issue28.

6. Implementation report: 10 min, Victor Fajardo; 10 min, Hannes Tschofenig

   Reports from people who have been implementing the PANA specification.
   The former implementation was recently published at
   http://www.opendiameter.org/

7. Next steps: 5 min, Chairs/ADs


STATUS of WG I-Ds:

-  draft-ietf-pana-usage-scenarios-06.txt
   WG last call completed on 3/11/03. Draft is sent to ADs for IESG
   consideration.

-  draft-ietf-pana-requirements-07.txt
   WG last call completed on 6/12/03. Draft is sent to ADs for IESG
   consideration.

-  draft-ietf-pana-threats-eval-04.txt
   WG last call completed on 5/1/03. Draft is sent to ADs for IESG
   consideration.

-  draft-ietf-pana-pana-02.txt
   Work in progress. I-D will be discussed at IETF 58.

-  draft-ietf-pana-ipsec-00.txt
   Work in progress. I-D will be discussed at IETF 58.


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



From pana-admin@ietf.org  Thu Oct 30 05:23:22 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16236
	for <pana-archive@lists.ietf.org>; Thu, 30 Oct 2003 05:23:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF9xG-0001Zx-2o; Thu, 30 Oct 2003 05:23:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF9wq-0001UP-ON
	for pana@optimus.ietf.org; Thu, 30 Oct 2003 05:22:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16169
	for <pana@ietf.org>; Thu, 30 Oct 2003 05:22:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF9wm-0000od-00
	for pana@ietf.org; Thu, 30 Oct 2003 05:22:32 -0500
Received: from alc245.alcatel.be ([195.207.101.245] helo=relay4.alcatel.be)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF9wm-0000nb-00
	for pana@ietf.org; Thu, 30 Oct 2003 05:22:32 -0500
Received: from btm34m.sh.bel.alcatel.be (btm34m.sh.bel.alcatel.be [138.203.192.124])
	by relay4.alcatel.be (8.12.10/8.12.10) with ESMTP id h9UAM2n0029500
	for <pana@ietf.org>; Thu, 30 Oct 2003 11:22:02 +0100
Received: from alcatel.be (bt0pxa [138.203.85.210])
	by btm34m.sh.bel.alcatel.be (8.8.8p2+Sun/8.8.8/1.1) with ESMTP id LAA20610
	for <pana@ietf.org>; Thu, 30 Oct 2003 11:22:01 +0100 (MET)
Message-ID: <3FA0E649.85641DC@alcatel.be>
Date: Thu, 30 Oct 2003 11:22:01 +0100
From: nagi reddy jonnala <Nagi_Reddy.Jonnala@alcatel.be>
Organization: Alcatel Telecom
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: pana@ietf.org
References: <BBC5942D.B91E%alper@docomolabs-usa.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.37
Content-Transfer-Encoding: 7bit
Subject: [Pana] Comments on PANA usage scenarios draft
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

All,


1) I understand the use of PANA to access the network. Do we
intend to use this mechanism in the application layers too? For
example, consider a case of  a website wants to authenticate
its users. Remember, we can access the network(internet)
but this website needs more authentication. and a webpage in
the website needs further authentication.

Do we plan to use PANA in this hierarchical model?

2) Section 4.1 - PANA with physical layer security mentions the below:

" In DSL networks, there are a number of deployment models with respect
   to client configuration and client authentication.  In DSL networks
   where PPP or PPPoE is used for both configuration and authentication,
   PANA may not be required.  On the other hand, there are some DSL
   networks that use some configuration method other than PPP or PPPoE,
   i.e., DHCP or static configuration.  Such networks use either an ad-
   hoc network access authentication method such as http-redirect with
   web-based login or no authentication method at all."

I believe 802.1x authentication mechanism is used in these DSL networks
assuming that user devices are connected by IPoE.

I didn't get the point here - why http-direct with web-based login method
is used?

-Nagi.






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


From exim@www1.ietf.org  Thu Oct 30 05:23:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16262
	for <pana-archive@odin.ietf.org>; Thu, 30 Oct 2003 05:23:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF9xI-0001bW-7G
	for pana-archive@odin.ietf.org; Thu, 30 Oct 2003 05:23:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9UAN4F6006165
	for pana-archive@odin.ietf.org; Thu, 30 Oct 2003 05:23:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF9xI-0001bM-36
	for pana-web-archive@optimus.ietf.org; Thu, 30 Oct 2003 05:23:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16197
	for <pana-web-archive@ietf.org>; Thu, 30 Oct 2003 05:22:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF9xE-0000pc-00
	for pana-web-archive@ietf.org; Thu, 30 Oct 2003 05:23:00 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF9xE-0000pZ-00
	for pana-web-archive@ietf.org; Thu, 30 Oct 2003 05:23:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF9xG-0001Zx-2o; Thu, 30 Oct 2003 05:23:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AF9wq-0001UP-ON
	for pana@optimus.ietf.org; Thu, 30 Oct 2003 05:22:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16169
	for <pana@ietf.org>; Thu, 30 Oct 2003 05:22:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF9wm-0000od-00
	for pana@ietf.org; Thu, 30 Oct 2003 05:22:32 -0500
Received: from alc245.alcatel.be ([195.207.101.245] helo=relay4.alcatel.be)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AF9wm-0000nb-00
	for pana@ietf.org; Thu, 30 Oct 2003 05:22:32 -0500
Received: from btm34m.sh.bel.alcatel.be (btm34m.sh.bel.alcatel.be [138.203.192.124])
	by relay4.alcatel.be (8.12.10/8.12.10) with ESMTP id h9UAM2n0029500
	for <pana@ietf.org>; Thu, 30 Oct 2003 11:22:02 +0100
Received: from alcatel.be (bt0pxa [138.203.85.210])
	by btm34m.sh.bel.alcatel.be (8.8.8p2+Sun/8.8.8/1.1) with ESMTP id LAA20610
	for <pana@ietf.org>; Thu, 30 Oct 2003 11:22:01 +0100 (MET)
Message-ID: <3FA0E649.85641DC@alcatel.be>
Date: Thu, 30 Oct 2003 11:22:01 +0100
From: nagi reddy jonnala <Nagi_Reddy.Jonnala@alcatel.be>
Organization: Alcatel Telecom
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: pana@ietf.org
References: <BBC5942D.B91E%alper@docomolabs-usa.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.37
Content-Transfer-Encoding: 7bit
Subject: [Pana] Comments on PANA usage scenarios draft
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

All,


1) I understand the use of PANA to access the network. Do we
intend to use this mechanism in the application layers too? For
example, consider a case of  a website wants to authenticate
its users. Remember, we can access the network(internet)
but this website needs more authentication. and a webpage in
the website needs further authentication.

Do we plan to use PANA in this hierarchical model?

2) Section 4.1 - PANA with physical layer security mentions the below:

" In DSL networks, there are a number of deployment models with respect
   to client configuration and client authentication.  In DSL networks
   where PPP or PPPoE is used for both configuration and authentication,
   PANA may not be required.  On the other hand, there are some DSL
   networks that use some configuration method other than PPP or PPPoE,
   i.e., DHCP or static configuration.  Such networks use either an ad-
   hoc network access authentication method such as http-redirect with
   web-based login or no authentication method at all."

I believe 802.1x authentication mechanism is used in these DSL networks
assuming that user devices are connected by IPoE.

I didn't get the point here - why http-direct with web-based login method
is used?

-Nagi.






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



From pana-admin@ietf.org  Thu Oct 30 07:23:23 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19576
	for <pana-archive@lists.ietf.org>; Thu, 30 Oct 2003 07:23:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFBpM-0005ud-MH; Thu, 30 Oct 2003 07:23:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFBoP-0005so-77
	for pana@optimus.ietf.org; Thu, 30 Oct 2003 07:22:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19549
	for <pana@ietf.org>; Thu, 30 Oct 2003 07:21:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFBoO-0002HV-00
	for pana@ietf.org; Thu, 30 Oct 2003 07:22:00 -0500
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFBoN-0002HS-00
	for pana@ietf.org; Thu, 30 Oct 2003 07:21:59 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by goliath.siemens.de (8.11.7/8.11.7) with ESMTP id h9UCLrF07639;
	Thu, 30 Oct 2003 13:21:55 +0100 (MET)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id h9UCLqd19283;
	Thu, 30 Oct 2003 13:21:52 +0100 (MET)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <VRGVWPC0>; Thu, 30 Oct 2003 13:21:31 +0100
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC03A0@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'nagi reddy jonnala'" <Nagi_Reddy.Jonnala@alcatel.be>, pana@ietf.org
Subject: RE: [Pana] Comments on PANA usage scenarios draft
Date: Thu, 30 Oct 2003 13:21:37 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi, 

regarding your first question. if you need additional authentication and
authorization for the access to a web site then you might want to reusing
existing mechanisms. pana does not provide mechanisms to use eap to
authenticate yourself to a web server. 

ciao
hannes


> -----Original Message-----
> From: nagi reddy jonnala [mailto:Nagi_Reddy.Jonnala@alcatel.be]
> Sent: Thursday, October 30, 2003 11:22 AM
> To: pana@ietf.org
> Subject: [Pana] Comments on PANA usage scenarios draft
> 
> 
> All,
> 
> 
> 1) I understand the use of PANA to access the network. Do we
> intend to use this mechanism in the application layers too? For
> example, consider a case of  a website wants to authenticate
> its users. Remember, we can access the network(internet)
> but this website needs more authentication. and a webpage in
> the website needs further authentication.
> 
> Do we plan to use PANA in this hierarchical model?
> 
> 2) Section 4.1 - PANA with physical layer security mentions the below:
> 
> " In DSL networks, there are a number of deployment models 
> with respect
>    to client configuration and client authentication.  In DSL networks
>    where PPP or PPPoE is used for both configuration and 
> authentication,
>    PANA may not be required.  On the other hand, there are some DSL
>    networks that use some configuration method other than PPP 
> or PPPoE,
>    i.e., DHCP or static configuration.  Such networks use 
> either an ad-
>    hoc network access authentication method such as http-redirect with
>    web-based login or no authentication method at all."
> 
> I believe 802.1x authentication mechanism is used in these 
> DSL networks
> assuming that user devices are connected by IPoE.
> 
> I didn't get the point here - why http-direct with web-based 
> login method
> is used?
> 
> -Nagi.
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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 exim@www1.ietf.org  Thu Oct 30 07:23:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19591
	for <pana-archive@odin.ietf.org>; Thu, 30 Oct 2003 07:23:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFBpP-0005vZ-3l
	for pana-archive@odin.ietf.org; Thu, 30 Oct 2003 07:23:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9UCN3uf022779
	for pana-archive@odin.ietf.org; Thu, 30 Oct 2003 07:23:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFBpO-0005vK-Vp
	for pana-web-archive@optimus.ietf.org; Thu, 30 Oct 2003 07:23:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19570
	for <pana-web-archive@ietf.org>; Thu, 30 Oct 2003 07:22:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFBpO-0002I4-00
	for pana-web-archive@ietf.org; Thu, 30 Oct 2003 07:23:02 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFBpO-0002I1-00
	for pana-web-archive@ietf.org; Thu, 30 Oct 2003 07:23:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFBpM-0005ud-MH; Thu, 30 Oct 2003 07:23:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFBoP-0005so-77
	for pana@optimus.ietf.org; Thu, 30 Oct 2003 07:22:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19549
	for <pana@ietf.org>; Thu, 30 Oct 2003 07:21:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFBoO-0002HV-00
	for pana@ietf.org; Thu, 30 Oct 2003 07:22:00 -0500
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFBoN-0002HS-00
	for pana@ietf.org; Thu, 30 Oct 2003 07:21:59 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by goliath.siemens.de (8.11.7/8.11.7) with ESMTP id h9UCLrF07639;
	Thu, 30 Oct 2003 13:21:55 +0100 (MET)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id h9UCLqd19283;
	Thu, 30 Oct 2003 13:21:52 +0100 (MET)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <VRGVWPC0>; Thu, 30 Oct 2003 13:21:31 +0100
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC03A0@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'nagi reddy jonnala'" <Nagi_Reddy.Jonnala@alcatel.be>, pana@ietf.org
Subject: RE: [Pana] Comments on PANA usage scenarios draft
Date: Thu, 30 Oct 2003 13:21:37 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi, 

regarding your first question. if you need additional authentication and
authorization for the access to a web site then you might want to reusing
existing mechanisms. pana does not provide mechanisms to use eap to
authenticate yourself to a web server. 

ciao
hannes


> -----Original Message-----
> From: nagi reddy jonnala [mailto:Nagi_Reddy.Jonnala@alcatel.be]
> Sent: Thursday, October 30, 2003 11:22 AM
> To: pana@ietf.org
> Subject: [Pana] Comments on PANA usage scenarios draft
> 
> 
> All,
> 
> 
> 1) I understand the use of PANA to access the network. Do we
> intend to use this mechanism in the application layers too? For
> example, consider a case of  a website wants to authenticate
> its users. Remember, we can access the network(internet)
> but this website needs more authentication. and a webpage in
> the website needs further authentication.
> 
> Do we plan to use PANA in this hierarchical model?
> 
> 2) Section 4.1 - PANA with physical layer security mentions the below:
> 
> " In DSL networks, there are a number of deployment models 
> with respect
>    to client configuration and client authentication.  In DSL networks
>    where PPP or PPPoE is used for both configuration and 
> authentication,
>    PANA may not be required.  On the other hand, there are some DSL
>    networks that use some configuration method other than PPP 
> or PPPoE,
>    i.e., DHCP or static configuration.  Such networks use 
> either an ad-
>    hoc network access authentication method such as http-redirect with
>    web-based login or no authentication method at all."
> 
> I believe 802.1x authentication mechanism is used in these 
> DSL networks
> assuming that user devices are connected by IPoE.
> 
> I didn't get the point here - why http-direct with web-based 
> login method
> is used?
> 
> -Nagi.
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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-admin@ietf.org  Thu Oct 30 07:45:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20139
	for <pana-archive@lists.ietf.org>; Thu, 30 Oct 2003 07:45:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFCAg-0000BH-S9; Thu, 30 Oct 2003 07:45:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFC9n-00008j-Pu
	for pana@optimus.ietf.org; Thu, 30 Oct 2003 07:44:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20110
	for <pana@ietf.org>; Thu, 30 Oct 2003 07:43:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFC9m-0002Yk-00
	for pana@ietf.org; Thu, 30 Oct 2003 07:44:07 -0500
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFC9m-0002Yh-00
	for pana@ietf.org; Thu, 30 Oct 2003 07:44:06 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h9UCi4c04548;
	Thu, 30 Oct 2003 13:44:04 +0100 (MET)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id h9UCi3d21183;
	Thu, 30 Oct 2003 13:44:04 +0100 (MET)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <VRGVWPQ6>; Thu, 30 Oct 2003 13:43:51 +0100
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC03A4@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Alper Yegin'" <alper@docomolabs-usa.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Date: Thu, 30 Oct 2003 13:43:56 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Pana] PANA state machine
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi alper, 
hi dan,

we have implemented a fairly simple state machine in our pana
implementation. the pana state machine is effectively a subset of dan's
state machine and for the core part we fully agree with dan's description.

ciao
hannes

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


From exim@www1.ietf.org  Thu Oct 30 07:45:25 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20154
	for <pana-archive@odin.ietf.org>; Thu, 30 Oct 2003 07:45:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFCAi-0000C4-76
	for pana-archive@odin.ietf.org; Thu, 30 Oct 2003 07:45:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9UCj49U000738
	for pana-archive@odin.ietf.org; Thu, 30 Oct 2003 07:45:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFCAi-0000Bp-1n
	for pana-web-archive@optimus.ietf.org; Thu, 30 Oct 2003 07:45:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20133
	for <pana-web-archive@ietf.org>; Thu, 30 Oct 2003 07:44:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFCAh-0002ai-00
	for pana-web-archive@ietf.org; Thu, 30 Oct 2003 07:45:03 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFCAg-0002af-00
	for pana-web-archive@ietf.org; Thu, 30 Oct 2003 07:45:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFCAg-0000BH-S9; Thu, 30 Oct 2003 07:45:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFC9n-00008j-Pu
	for pana@optimus.ietf.org; Thu, 30 Oct 2003 07:44:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20110
	for <pana@ietf.org>; Thu, 30 Oct 2003 07:43:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFC9m-0002Yk-00
	for pana@ietf.org; Thu, 30 Oct 2003 07:44:07 -0500
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFC9m-0002Yh-00
	for pana@ietf.org; Thu, 30 Oct 2003 07:44:06 -0500
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h9UCi4c04548;
	Thu, 30 Oct 2003 13:44:04 +0100 (MET)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail3.siemens.de (8.11.7/8.11.7) with ESMTP id h9UCi3d21183;
	Thu, 30 Oct 2003 13:44:04 +0100 (MET)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <VRGVWPQ6>; Thu, 30 Oct 2003 13:43:51 +0100
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC03A4@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Alper Yegin'" <alper@docomolabs-usa.com>, Dan.Forsberg@nokia.com,
        pana@ietf.org
Date: Thu, 30 Oct 2003 13:43:56 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Pana] PANA state machine
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

hi alper, 
hi dan,

we have implemented a fairly simple state machine in our pana
implementation. the pana state machine is effectively a subset of dan's
state machine and for the core part we fully agree with dan's description.

ciao
hannes

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



From exim@www1.ietf.org  Thu Oct 30 11:17:24 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29006
	for <pana-archive@odin.ietf.org>; Thu, 30 Oct 2003 11:17:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFFTr-0007Ye-Iy
	for pana-archive@odin.ietf.org; Thu, 30 Oct 2003 11:17:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9UGH36H029046
	for pana-archive@odin.ietf.org; Thu, 30 Oct 2003 11:17:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFFTr-0007YP-FA
	for pana-web-archive@optimus.ietf.org; Thu, 30 Oct 2003 11:17:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28982
	for <pana-web-archive@ietf.org>; Thu, 30 Oct 2003 11:16:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFFTq-0005ls-00
	for pana-web-archive@ietf.org; Thu, 30 Oct 2003 11:17:02 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFFTq-0005lp-00
	for pana-web-archive@ietf.org; Thu, 30 Oct 2003 11:17:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFFTo-0007Xk-VW; Thu, 30 Oct 2003 11:17:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFFSt-0007T9-Eg
	for pana@optimus.ietf.org; Thu, 30 Oct 2003 11:16:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28927
	for <pana@ietf.org>; Thu, 30 Oct 2003 11:15:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFFSs-0005kb-00
	for pana@ietf.org; Thu, 30 Oct 2003 11:16:02 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFFSr-0005kN-00
	for pana@ietf.org; Thu, 30 Oct 2003 11:16:01 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9UGFkF1024053;
	Fri, 31 Oct 2003 01:15:46 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9UGFkB2010790;
	Fri, 31 Oct 2003 01:15:46 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA10788 ; Fri, 31 Oct 2003 01:15:45 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA25337; Fri, 31 Oct 2003 01:15:45 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA24010; Fri, 31 Oct 2003 01:15:44 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9UGFitb020947;
	Fri, 31 Oct 2003 01:15:44 +0900 (JST)
Received: from steelhead ([159.119.168.182]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HNK00F67VU6QI@tsbpo1.po.toshiba.co.jp>; Fri,
 31 Oct 2003 01:15:43 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AFFR1-0003aS-00; Thu, 30 Oct 2003 08:14:07 -0800
Date: Thu, 30 Oct 2003 08:14:07 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Comments on PANA usage scenarios draft
In-reply-to: <3FA0E649.85641DC@alcatel.be>
To: nagi reddy jonnala <Nagi_Reddy.Jonnala@alcatel.be>
Cc: pana@ietf.org
Message-id: <20031030161407.GC13032@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: nagi reddy jonnala <Nagi_Reddy.Jonnala@alcatel.be>,
 pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <BBC5942D.B91E%alper@docomolabs-usa.com>
 <3FA0E649.85641DC@alcatel.be>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Thanks Nagi for your comments.  Please see my comments inline.

On Thu, Oct 30, 2003 at 11:22:01AM +0100, nagi reddy jonnala wrote:
> All,
> 
> 
> 1) I understand the use of PANA to access the network. Do we
> intend to use this mechanism in the application layers too? For
> example, consider a case of  a website wants to authenticate
> its users. Remember, we can access the network(internet)
> but this website needs more authentication. and a webpage in
> the website needs further authentication.
> 
> Do we plan to use PANA in this hierarchical model?

I think web-based authentication works fine for this case, and I
don't think PANA is needed beyond network access authentication.

> 
> 2) Section 4.1 - PANA with physical layer security mentions the below:
> 
> " In DSL networks, there are a number of deployment models with respect
>    to client configuration and client authentication.  In DSL networks
>    where PPP or PPPoE is used for both configuration and authentication,
>    PANA may not be required.  On the other hand, there are some DSL
>    networks that use some configuration method other than PPP or PPPoE,
>    i.e., DHCP or static configuration.  Such networks use either an ad-
>    hoc network access authentication method such as http-redirect with
>    web-based login or no authentication method at all."
> 
> I believe 802.1x authentication mechanism is used in these DSL networks
> assuming that user devices are connected by IPoE.

IEEE 802.1X is designed to work over a IEEE 802 LAN segment where
there is no bridge between Authenticator and Supplicant.  IEEE 802.1X
could be used in Ethernet-based DSL but only when the 802.1X
Authenticator is located on the first hop Ethernet bridge, which means
IEEE 802.1X has topology constraint.


> 
> I didn't get the point here - why http-direct with web-based login method
> is used?

http-redirect with web-based login is just an example of ad-hoc
authentication method in this case where PPP or PPPoE is not used 
for configurating or authenticating a client.

Yoshihiro Ohba

> 
> -Nagi.
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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-admin@ietf.org  Thu Oct 30 12:04:49 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29005
	for <pana-archive@lists.ietf.org>; Thu, 30 Oct 2003 11:17:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFFTo-0007Xk-VW; Thu, 30 Oct 2003 11:17:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AFFSt-0007T9-Eg
	for pana@optimus.ietf.org; Thu, 30 Oct 2003 11:16:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28927
	for <pana@ietf.org>; Thu, 30 Oct 2003 11:15:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFFSs-0005kb-00
	for pana@ietf.org; Thu, 30 Oct 2003 11:16:02 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AFFSr-0005kN-00
	for pana@ietf.org; Thu, 30 Oct 2003 11:16:01 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id h9UGFkF1024053;
	Fri, 31 Oct 2003 01:15:46 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id h9UGFkB2010790;
	Fri, 31 Oct 2003 01:15:46 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id BAA10788 ; Fri, 31 Oct 2003 01:15:45 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id BAA25337; Fri, 31 Oct 2003 01:15:45 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id BAA24010; Fri, 31 Oct 2003 01:15:44 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id h9UGFitb020947;
	Fri, 31 Oct 2003 01:15:44 +0900 (JST)
Received: from steelhead ([159.119.168.182]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HNK00F67VU6QI@tsbpo1.po.toshiba.co.jp>; Fri,
 31 Oct 2003 01:15:43 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AFFR1-0003aS-00; Thu, 30 Oct 2003 08:14:07 -0800
Date: Thu, 30 Oct 2003 08:14:07 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Comments on PANA usage scenarios draft
In-reply-to: <3FA0E649.85641DC@alcatel.be>
To: nagi reddy jonnala <Nagi_Reddy.Jonnala@alcatel.be>
Cc: pana@ietf.org
Message-id: <20031030161407.GC13032@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: nagi reddy jonnala <Nagi_Reddy.Jonnala@alcatel.be>,
 pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <BBC5942D.B91E%alper@docomolabs-usa.com>
 <3FA0E649.85641DC@alcatel.be>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>

Thanks Nagi for your comments.  Please see my comments inline.

On Thu, Oct 30, 2003 at 11:22:01AM +0100, nagi reddy jonnala wrote:
> All,
> 
> 
> 1) I understand the use of PANA to access the network. Do we
> intend to use this mechanism in the application layers too? For
> example, consider a case of  a website wants to authenticate
> its users. Remember, we can access the network(internet)
> but this website needs more authentication. and a webpage in
> the website needs further authentication.
> 
> Do we plan to use PANA in this hierarchical model?

I think web-based authentication works fine for this case, and I
don't think PANA is needed beyond network access authentication.

> 
> 2) Section 4.1 - PANA with physical layer security mentions the below:
> 
> " In DSL networks, there are a number of deployment models with respect
>    to client configuration and client authentication.  In DSL networks
>    where PPP or PPPoE is used for both configuration and authentication,
>    PANA may not be required.  On the other hand, there are some DSL
>    networks that use some configuration method other than PPP or PPPoE,
>    i.e., DHCP or static configuration.  Such networks use either an ad-
>    hoc network access authentication method such as http-redirect with
>    web-based login or no authentication method at all."
> 
> I believe 802.1x authentication mechanism is used in these DSL networks
> assuming that user devices are connected by IPoE.

IEEE 802.1X is designed to work over a IEEE 802 LAN segment where
there is no bridge between Authenticator and Supplicant.  IEEE 802.1X
could be used in Ethernet-based DSL but only when the 802.1X
Authenticator is located on the first hop Ethernet bridge, which means
IEEE 802.1X has topology constraint.


> 
> I didn't get the point here - why http-direct with web-based login method
> is used?

http-redirect with web-based login is just an example of ad-hoc
authentication method in this case where PPP or PPPoE is not used 
for configurating or authenticating a client.

Yoshihiro Ohba

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


