From pana-admin@ietf.org  Mon Dec  1 04:02:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02273
	for <pana-archive@lists.ietf.org>; Mon, 1 Dec 2003 04:02:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQjwQ-0002RP-JY; Mon, 01 Dec 2003 04:02:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQjvv-0002Qg-BG
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 04:01:31 -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 EAA02248
	for <pana@ietf.org>; Mon, 1 Dec 2003 04:01:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQjvs-0005os-00
	for pana@ietf.org; Mon, 01 Dec 2003 04:01:28 -0500
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQjvs-0005of-00
	for pana@ietf.org; Mon, 01 Dec 2003 04:01:28 -0500
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2657.72)
	id <XVWPSWFZ>; Mon, 1 Dec 2003 04:00:58 -0500
Message-ID: <9E3BA3946476AD4EB94672712B12A85F042039@ftmail.lab.flarion.com>
From: Soliman Hesham <H.Soliman@flarion.com>
To: "'Alper Yegin'" <aeyegin@hotmail.com>, alper@docomolabs-usa.com,
        Yoshihiro.Ohba@tais.com, mohanp@sbcglobal.net
Cc: aboba@internaut.com, jari.arkko@piuha.net, kempf@docomolabs-usa.com,
        pana@ietf.org
Subject: RE: [Pana] IP address configuration
Date: Mon, 1 Dec 2003 04:00:48 -0500 
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>


 > >=> I think this might be treading in unchartered items ;)
 > >I mean, is securing ND really part of the PANA charter?
 > 
 > If I have a secure channel between the two end-points,
 > I'd try yo carry as much of my communication as possible
 > inside this channel, unless this creates additional unjustified
 > complexity. This is where I'm coming from... I don't think
 > this solves 100% of the problems associated with securing
 > ND and router discovery, but I think it can help...

=> ok. It's worth considering the impacts on the IP stack and
the communication media (multicast with IPsec) though. I
was hoping that PANA can be independent of the IP stack
implementation as much as possible for ease of deployment.
In any case since this does not solve the major problems
with ND (DAD and NAs) there is likely to be a need to have SEND
anyway for those links that need it. So doubling the security
of the RA might not be that worthwhile given the impacts 
on all the other ND messages. 

 > The outer address is only needed to shuttle
 > real data packets to the EP. Also,  from the PANA perspective,
 > it'd be a much cleaner architecture if there is only one IP 
 > address visible
 > and it is used as the device ID. Filters on the EP are only 
 > aware of this
 > address. And there is no reason to change this address in 
 > time... These
 > all say "link-local" to me...
 > On the other hand, do you see any issues with using a 
 > link-local address
 > as ther outer address of the IPsec tunnel?

=> Not really, I just didn't think we needed to assume 
that the outer address is different from the inner one.
The requirements listed above can be met with any 
IP address that doesn't have to change too often. Of course
when L2 security is available the DI can just be a MAC
address. 

Hesham


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


From exim@www1.ietf.org  Mon Dec  1 04:02:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02293
	for <pana-archive@odin.ietf.org>; Mon, 1 Dec 2003 04:02:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQjwc-0002TR-MQ
	for pana-archive@odin.ietf.org; Mon, 01 Dec 2003 04:02:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB192ESw009497
	for pana-archive@odin.ietf.org; Mon, 1 Dec 2003 04:02:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQjwa-0002Sq-AZ
	for pana-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 04:02: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 EAA02262
	for <pana-web-archive@ietf.org>; Mon, 1 Dec 2003 04:01:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQjwX-0005rZ-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 04:02:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQjwX-0005rW-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 04:02:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQjwQ-0002RP-JY; Mon, 01 Dec 2003 04:02:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQjvv-0002Qg-BG
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 04:01:31 -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 EAA02248
	for <pana@ietf.org>; Mon, 1 Dec 2003 04:01:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQjvs-0005os-00
	for pana@ietf.org; Mon, 01 Dec 2003 04:01:28 -0500
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQjvs-0005of-00
	for pana@ietf.org; Mon, 01 Dec 2003 04:01:28 -0500
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2657.72)
	id <XVWPSWFZ>; Mon, 1 Dec 2003 04:00:58 -0500
Message-ID: <9E3BA3946476AD4EB94672712B12A85F042039@ftmail.lab.flarion.com>
From: Soliman Hesham <H.Soliman@flarion.com>
To: "'Alper Yegin'" <aeyegin@hotmail.com>, alper@docomolabs-usa.com,
        Yoshihiro.Ohba@tais.com, mohanp@sbcglobal.net
Cc: aboba@internaut.com, jari.arkko@piuha.net, kempf@docomolabs-usa.com,
        pana@ietf.org
Subject: RE: [Pana] IP address configuration
Date: Mon, 1 Dec 2003 04:00:48 -0500 
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>


 > >=> I think this might be treading in unchartered items ;)
 > >I mean, is securing ND really part of the PANA charter?
 > 
 > If I have a secure channel between the two end-points,
 > I'd try yo carry as much of my communication as possible
 > inside this channel, unless this creates additional unjustified
 > complexity. This is where I'm coming from... I don't think
 > this solves 100% of the problems associated with securing
 > ND and router discovery, but I think it can help...

=> ok. It's worth considering the impacts on the IP stack and
the communication media (multicast with IPsec) though. I
was hoping that PANA can be independent of the IP stack
implementation as much as possible for ease of deployment.
In any case since this does not solve the major problems
with ND (DAD and NAs) there is likely to be a need to have SEND
anyway for those links that need it. So doubling the security
of the RA might not be that worthwhile given the impacts 
on all the other ND messages. 

 > The outer address is only needed to shuttle
 > real data packets to the EP. Also,  from the PANA perspective,
 > it'd be a much cleaner architecture if there is only one IP 
 > address visible
 > and it is used as the device ID. Filters on the EP are only 
 > aware of this
 > address. And there is no reason to change this address in 
 > time... These
 > all say "link-local" to me...
 > On the other hand, do you see any issues with using a 
 > link-local address
 > as ther outer address of the IPsec tunnel?

=> Not really, I just didn't think we needed to assume 
that the outer address is different from the inner one.
The requirements listed above can be met with any 
IP address that doesn't have to change too often. Of course
when L2 security is available the DI can just be a MAC
address. 

Hesham


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



From pana-admin@ietf.org  Mon Dec  1 11:42:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17019
	for <pana-archive@lists.ietf.org>; Mon, 1 Dec 2003 11:42:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQr7Z-0000fO-Qi; Mon, 01 Dec 2003 11:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQr7Q-0000eS-4L
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 11:41:54 -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 LAA16977
	for <pana@ietf.org>; Mon, 1 Dec 2003 11:41:37 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQr7P-0004sn-00
	for pana@ietf.org; Mon, 01 Dec 2003 11:41:51 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQr7O-0004sK-00
	for pana@ietf.org; Mon, 01 Dec 2003 11:41:50 -0500
Subject: Re: [Pana] IP address configuration
To: aeyegin@hotmail.com
Cc: aboba@internaut.com, jari.arkko@piuha.net, kempf@docomolabs-usa.com,
        mohanp@sbcglobal.net, pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OFA6F44551.F7B41C86-ON88256DEF.0055A839@tais.net>
Date: Mon, 1 Dec 2003 08:40:58 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/01/2003 08:41:51 AM
MIME-Version: 1.0
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>






>When configuration of post-PANA address occurs before IKE/IKEv2,
>it might be difficult to support the ISP selection model over shared
media.
>So supporting this case only would be a limitation.

I presume by "ISP selection" you are referring to the ability to allocate
an IP address from the address pool of the selected ISP.

Yes, the IPsec tunnel is bound to the PANA session, hence it implies
the selected ISP. As such, this can be leveraged during the address
allocation to identify the right address pool, ISP, etc.

But this is not the only way. Even if the address configuration takes
place outside the IPsec tunnel, some other identifier that is bound
to the PANA session can be used during the process. For example,
the source address of DHCP request (the DI of PaC) or the client
ID field set to PANA session ID might help.


I believe that DHCP should occur over the routing context where the address
is actually used.
When DHCP is performed outside the IPsec tunnel, the address assigned by
the DHCP server is
intended for the use outside the IPsec tunnel. RFC3456 is a special case in
which DHCP
for inner address allocation is allowed to run outside the IPsec tunnel,
with an assumption that the DHCP SA in RFC3456 is tightly associated with
the subsequently
created IPsec SA.



>When configuration of post-PANA address occurs inside the IPsec tunnel
>or inside IKE/IKEv2, it would be able to support the ISP selection model
>over shared media.  At least post-PANA address configuration is supported
>inside IKEv2 with Configuration Payload exchange. Post-PANA address
>configuration with DHCPv4 inside IPsec tunnel is supported by IKE +
>RFC3456. I am not really sure if there is no problem
>with other schemes for post-PANA address configuration inside IPsec
tunnel.

>I have a concern on allowing a PaC to specify wildcard address range in
>IPsec SA negotiation for the purpose of running Neighbor Discovery inside
>the IPsec tunnel, especially when the PaC is also a router,
>it could totally affect routing behavior.

Could you please elaborate on this....

Allowing PaC to specify wildcard address range as traffic selector means
that
any traffic can be forwarded to the PaC. Traffic selector is used for
constructing
SPD but sometimes also used for creating routing table when the IPsec
tunnel is associated
with a dedicated logical IP interface (such as ipsec0, ipsec1,... in
Linux). As a consequence,
I think it is possible that EP forwards all packets that are received from
ISPs or
other PaCs to the PaC that specified wildcard address range as traffic
selector.
If the PaC itself is a router and has another interface to the Internet, it
could totally
change the routing behavior.  This would be an extreme case, but I believe
it is not a
good idea in general to rely on a solution that uses wildcard address range
as traffic selector
for PaC.


Yoshihiro Ohba



Alper

_________________________________________________________________
>From the hottest toys to tips on keeping fit this winter, you$BCM(Bl find a
range of helpful holiday info here.
http://special.msn.com/network/happyholidays.armx






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


From exim@www1.ietf.org  Mon Dec  1 11:42:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17038
	for <pana-archive@odin.ietf.org>; Mon, 1 Dec 2003 11:42: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 1AQr7e-0000hJ-1W
	for pana-archive@odin.ietf.org; Mon, 01 Dec 2003 11:42:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1Gg6w9002677
	for pana-archive@odin.ietf.org; Mon, 1 Dec 2003 11:42:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQr7d-0000h6-PC
	for pana-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 11:42: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 LAA16992
	for <pana-web-archive@ietf.org>; Mon, 1 Dec 2003 11:41:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQr7c-0004tF-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 11:42:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQr7c-0004tC-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 11:42:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQr7Z-0000fO-Qi; Mon, 01 Dec 2003 11:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQr7Q-0000eS-4L
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 11:41:54 -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 LAA16977
	for <pana@ietf.org>; Mon, 1 Dec 2003 11:41:37 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQr7P-0004sn-00
	for pana@ietf.org; Mon, 01 Dec 2003 11:41:51 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQr7O-0004sK-00
	for pana@ietf.org; Mon, 01 Dec 2003 11:41:50 -0500
Subject: Re: [Pana] IP address configuration
To: aeyegin@hotmail.com
Cc: aboba@internaut.com, jari.arkko@piuha.net, kempf@docomolabs-usa.com,
        mohanp@sbcglobal.net, pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OFA6F44551.F7B41C86-ON88256DEF.0055A839@tais.net>
Date: Mon, 1 Dec 2003 08:40:58 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/01/2003 08:41:51 AM
MIME-Version: 1.0
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>






>When configuration of post-PANA address occurs before IKE/IKEv2,
>it might be difficult to support the ISP selection model over shared
media.
>So supporting this case only would be a limitation.

I presume by "ISP selection" you are referring to the ability to allocate
an IP address from the address pool of the selected ISP.

Yes, the IPsec tunnel is bound to the PANA session, hence it implies
the selected ISP. As such, this can be leveraged during the address
allocation to identify the right address pool, ISP, etc.

But this is not the only way. Even if the address configuration takes
place outside the IPsec tunnel, some other identifier that is bound
to the PANA session can be used during the process. For example,
the source address of DHCP request (the DI of PaC) or the client
ID field set to PANA session ID might help.


I believe that DHCP should occur over the routing context where the address
is actually used.
When DHCP is performed outside the IPsec tunnel, the address assigned by
the DHCP server is
intended for the use outside the IPsec tunnel. RFC3456 is a special case in
which DHCP
for inner address allocation is allowed to run outside the IPsec tunnel,
with an assumption that the DHCP SA in RFC3456 is tightly associated with
the subsequently
created IPsec SA.



>When configuration of post-PANA address occurs inside the IPsec tunnel
>or inside IKE/IKEv2, it would be able to support the ISP selection model
>over shared media.  At least post-PANA address configuration is supported
>inside IKEv2 with Configuration Payload exchange. Post-PANA address
>configuration with DHCPv4 inside IPsec tunnel is supported by IKE +
>RFC3456. I am not really sure if there is no problem
>with other schemes for post-PANA address configuration inside IPsec
tunnel.

>I have a concern on allowing a PaC to specify wildcard address range in
>IPsec SA negotiation for the purpose of running Neighbor Discovery inside
>the IPsec tunnel, especially when the PaC is also a router,
>it could totally affect routing behavior.

Could you please elaborate on this....

Allowing PaC to specify wildcard address range as traffic selector means
that
any traffic can be forwarded to the PaC. Traffic selector is used for
constructing
SPD but sometimes also used for creating routing table when the IPsec
tunnel is associated
with a dedicated logical IP interface (such as ipsec0, ipsec1,... in
Linux). As a consequence,
I think it is possible that EP forwards all packets that are received from
ISPs or
other PaCs to the PaC that specified wildcard address range as traffic
selector.
If the PaC itself is a router and has another interface to the Internet, it
could totally
change the routing behavior.  This would be an extreme case, but I believe
it is not a
good idea in general to rely on a solution that uses wildcard address range
as traffic selector
for PaC.


Yoshihiro Ohba



Alper

_________________________________________________________________
>From the hottest toys to tips on keeping fit this winter, you$BCM(Bl find a
range of helpful holiday info here.
http://special.msn.com/network/happyholidays.armx






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



From pana-admin@ietf.org  Mon Dec  1 12:24:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18741
	for <pana-archive@lists.ietf.org>; Mon, 1 Dec 2003 12:24:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQrmC-0003SB-Ue; Mon, 01 Dec 2003 12:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQrlI-0003NX-UX
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 12: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 MAA18608;
	Mon, 1 Dec 2003 12:22:48 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrlG-0005Yj-00; Mon, 01 Dec 2003 12:23:02 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrlF-0005Yd-00; Mon, 01 Dec 2003 12:23:01 -0500
Subject: Re: [Pana] PAA-2-EP protocol requirements
To: alper@docomolabs-usa.com
Cc: Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        MORAND Lionel FTRD/DAC/ISS <lionel.morand@francetelecom.com>,
        pana@ietf.org, pana-admin@ietf.org, Yacine.El_Mghazli@alcatel.fr,
        Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OFFA154088.AAD261F8-ON88256DEF.005C2C7A@tais.net>
Date: Mon, 1 Dec 2003 09:21:49 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/01/2003 09:23:02 AM
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>






   > below are some other PAA-2-EP functionnalities (open list). should we
   > consider them as also required ? not required at all ? supported
   > elsewhere ? any alternative ?
   >
   > a) Inactive peer detection:
   > The protocol used between PAA and EP should be able to detect inactive
   > peer within an appropriate time period. This can be achieved by having
   > both the EP and remote PAA constantly verify their connection to each
   > other via keep-alive messages: a heartbeat in fact.

   I'm not sure how much "explicit support" we need for this from the
   PAA2EP
   protocol. There can always be ad-hoc solutions to this. For example,
   running
   some request-reply messages between the PAA and EP can be used as a
   keep-alive. I can imagine an implementation resorting to such techniques
   when the protocol does not have a dedicated facility....


Yes, some SMNP implementation can support small value (order of seconds)
for
miminum polling inverval.  This would be sufficient for inactive peer
detection, but
not sufficient for detecting _rebooted_ peer when rebooting can complete
within
SNMP polling interval. Rebooting detection is needed when EP store
PaC information (including accounting information) in volatile memory.

So we might need to define some rebooting counters in SNMP MIB in order to
detect
rebooting peers, or if such a MIB already exists we might just specify the
use of
the MIB for both inactive/rebooted peer detection.



   >
   > b) Stateful approach:
   > The protocol must allow to maintain some states in the PAA in order
   for
   > an EP that went down and came back up, or an EP that is being
   introduced
   > in the network to (re-)synchronize with the PAA.

   We can assume PAA always has the associated state. It'd have a list of
   authorized PaCs and their attributes... I don't think this is something
   for
   PAA2EP protocol to worry about...

   > 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.
   >
   > c) Accounting/Feedback from the EPs:
   > The PAA must have an efficient way to to get the accounting
   information
   > of PaC from EP since the PAA may be a client of the AAA backend
   > infrastructure.

   Getting statistics from the EP makes sense. For example, in the case of
   SNMP, if we get the counters from the EP this is good enough. The AAA
   client
   sitting on the PAA can turn these into accoutning records.

I agree.  Should we eliminate the case where EP itself directly sends
accounting records
to the accounting server?  I am asking because AAA clients for
authentication sessions
and accounting sessions can be separated entities in Diameter, as long as
there is a way to
associate an accounting session with an authentication session.


Yoshihiro Ohba



   Alper



   >
   > d) ????
   >
   >
   > thanks,
   > Yacine El Mghazli
   >
   >
   >




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


From exim@www1.ietf.org  Mon Dec  1 12:24:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18758
	for <pana-archive@odin.ietf.org>; Mon, 1 Dec 2003 12:24:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQrmG-0003T3-1C
	for pana-archive@odin.ietf.org; Mon, 01 Dec 2003 12:24:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1HO4Hj013328
	for pana-archive@odin.ietf.org; Mon, 1 Dec 2003 12:24:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQrmF-0003St-Qi
	for pana-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 12:24: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 MAA18717
	for <pana-web-archive@ietf.org>; Mon, 1 Dec 2003 12:23:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrmE-0005Zp-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 12:24:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrmE-0005Zl-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 12:24:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQrmC-0003SB-Ue; Mon, 01 Dec 2003 12:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQrlI-0003NX-UX
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 12: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 MAA18608;
	Mon, 1 Dec 2003 12:22:48 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrlG-0005Yj-00; Mon, 01 Dec 2003 12:23:02 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrlF-0005Yd-00; Mon, 01 Dec 2003 12:23:01 -0500
Subject: Re: [Pana] PAA-2-EP protocol requirements
To: alper@docomolabs-usa.com
Cc: Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        MORAND Lionel FTRD/DAC/ISS <lionel.morand@francetelecom.com>,
        pana@ietf.org, pana-admin@ietf.org, Yacine.El_Mghazli@alcatel.fr,
        Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OFFA154088.AAD261F8-ON88256DEF.005C2C7A@tais.net>
Date: Mon, 1 Dec 2003 09:21:49 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/01/2003 09:23:02 AM
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>






   > below are some other PAA-2-EP functionnalities (open list). should we
   > consider them as also required ? not required at all ? supported
   > elsewhere ? any alternative ?
   >
   > a) Inactive peer detection:
   > The protocol used between PAA and EP should be able to detect inactive
   > peer within an appropriate time period. This can be achieved by having
   > both the EP and remote PAA constantly verify their connection to each
   > other via keep-alive messages: a heartbeat in fact.

   I'm not sure how much "explicit support" we need for this from the
   PAA2EP
   protocol. There can always be ad-hoc solutions to this. For example,
   running
   some request-reply messages between the PAA and EP can be used as a
   keep-alive. I can imagine an implementation resorting to such techniques
   when the protocol does not have a dedicated facility....


Yes, some SMNP implementation can support small value (order of seconds)
for
miminum polling inverval.  This would be sufficient for inactive peer
detection, but
not sufficient for detecting _rebooted_ peer when rebooting can complete
within
SNMP polling interval. Rebooting detection is needed when EP store
PaC information (including accounting information) in volatile memory.

So we might need to define some rebooting counters in SNMP MIB in order to
detect
rebooting peers, or if such a MIB already exists we might just specify the
use of
the MIB for both inactive/rebooted peer detection.



   >
   > b) Stateful approach:
   > The protocol must allow to maintain some states in the PAA in order
   for
   > an EP that went down and came back up, or an EP that is being
   introduced
   > in the network to (re-)synchronize with the PAA.

   We can assume PAA always has the associated state. It'd have a list of
   authorized PaCs and their attributes... I don't think this is something
   for
   PAA2EP protocol to worry about...

   > 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.
   >
   > c) Accounting/Feedback from the EPs:
   > The PAA must have an efficient way to to get the accounting
   information
   > of PaC from EP since the PAA may be a client of the AAA backend
   > infrastructure.

   Getting statistics from the EP makes sense. For example, in the case of
   SNMP, if we get the counters from the EP this is good enough. The AAA
   client
   sitting on the PAA can turn these into accoutning records.

I agree.  Should we eliminate the case where EP itself directly sends
accounting records
to the accounting server?  I am asking because AAA clients for
authentication sessions
and accounting sessions can be separated entities in Diameter, as long as
there is a way to
associate an accounting session with an authentication session.


Yoshihiro Ohba



   Alper



   >
   > d) ????
   >
   >
   > thanks,
   > Yacine El Mghazli
   >
   >
   >




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



From pana-admin@ietf.org  Mon Dec  1 12:39:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19325
	for <pana-archive@lists.ietf.org>; Mon, 1 Dec 2003 12:39: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 1AQs0i-0004Wc-G0; Mon, 01 Dec 2003 12:39:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQrzk-0004PB-Ts
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 12:38:00 -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 MAA19244
	for <pana@ietf.org>; Mon, 1 Dec 2003 12:37:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrzj-0005ic-00
	for pana@ietf.org; Mon, 01 Dec 2003 12:37:59 -0500
Received: from fep01-svc.mail.telepac.pt ([194.65.5.200])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrzi-0005iO-00
	for pana@ietf.org; Mon, 01 Dec 2003 12:37:58 -0500
Received: from escritorio1 ([213.13.202.81]) by fep01-svc.mail.telepac.pt
          (InterMail vM.5.01.04.13 201-253-122-122-113-20020313) with SMTP
          id <20031201173726.DFRD15844.fep01-svc.mail.telepac.pt@escritorio1>
          for <pana@ietf.org>; Mon, 1 Dec 2003 17:37:26 +0000
Message-ID: <001b01c3b831$d11e0660$ef74fea9@escritorio1>
From: "Joaquim Moreira" <moreirasantos@mail.telepac.pt>
To: <pana@ietf.org>
Date: Mon, 1 Dec 2003 17:37:39 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0018_01C3B831.D0F4AC70"
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] Questions
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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_0018_01C3B831.D0F4AC70
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello !

My membership number is 489376.

Let me put some questions. I need to be clear up:
1 - Have PANA goals to E2E clients only or to mobility ones, too ?
2 - EAP protocol, I think will be the authentication method adopted by =
PANA. Am I wrong ? The two modes of EAP protocol (EAP-MD5 and EAP-TLS ?) =
What are the most important problems with EAP for PANA goals ? If the =
answer to the first question includes mobility, what will be the =
protocol ? WEP ?=20
3 - IPSec - the two modes of operation (tunnel and E2E with IPSec) will =
be guaranteed with a good QoS?
4 - The last one: 802.1x stack: EAP/LAN <---> EAP/RADIUS, how will be =
doing this connectivity ?

Chairs,

Jo=E3o Moreira 
------=_NextPart_000_0018_01C3B831.D0F4AC70
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.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV>Hello !<BR><BR>My membership number is 489376.</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Let me put some questions. I need to be =
clear=20
up:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>1 - Have PANA goals to E2E clients only =
or to=20
mobility ones, too ?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2 - EAP protocol, I think will be the=20
authentication method adopted by PANA. Am I wrong ? The two modes of EAP =

protocol (EAP-MD5 and EAP-TLS ?) What are the most important problems =
with EAP=20
for PANA goals ? If the answer to the first question includes mobility, =
what=20
will be the protocol ? WEP ?&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>3 - IPSec - the two modes of operation =
(tunnel and=20
E2E&nbsp;with IPSec) will be guaranteed with a good QoS?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>4 - The last one: 802.1x stack: EAP/LAN =
&lt;---&gt;=20
EAP/RADIUS, how will be doing this connectivity ?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Chairs,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Jo=E3o=20
Moreira</FONT>&nbsp;</DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0018_01C3B831.D0F4AC70--


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


From exim@www1.ietf.org  Mon Dec  1 12:39:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19365
	for <pana-archive@odin.ietf.org>; Mon, 1 Dec 2003 12:39:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQs0y-0004aZ-Sy
	for pana-archive@odin.ietf.org; Mon, 01 Dec 2003 12:39:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1HdGAP017633
	for pana-archive@odin.ietf.org; Mon, 1 Dec 2003 12:39:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQs0y-0004aH-NU
	for pana-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 12:39:16 -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 MAA19298
	for <pana-web-archive@ietf.org>; Mon, 1 Dec 2003 12:39:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQs0x-0005je-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 12:39:15 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQs0w-0005jQ-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 12:39:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQs0i-0004Wc-G0; Mon, 01 Dec 2003 12:39:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQrzk-0004PB-Ts
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 12:38:00 -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 MAA19244
	for <pana@ietf.org>; Mon, 1 Dec 2003 12:37:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrzj-0005ic-00
	for pana@ietf.org; Mon, 01 Dec 2003 12:37:59 -0500
Received: from fep01-svc.mail.telepac.pt ([194.65.5.200])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQrzi-0005iO-00
	for pana@ietf.org; Mon, 01 Dec 2003 12:37:58 -0500
Received: from escritorio1 ([213.13.202.81]) by fep01-svc.mail.telepac.pt
          (InterMail vM.5.01.04.13 201-253-122-122-113-20020313) with SMTP
          id <20031201173726.DFRD15844.fep01-svc.mail.telepac.pt@escritorio1>
          for <pana@ietf.org>; Mon, 1 Dec 2003 17:37:26 +0000
Message-ID: <001b01c3b831$d11e0660$ef74fea9@escritorio1>
From: "Joaquim Moreira" <moreirasantos@mail.telepac.pt>
To: <pana@ietf.org>
Date: Mon, 1 Dec 2003 17:37:39 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0018_01C3B831.D0F4AC70"
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] Questions
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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_0018_01C3B831.D0F4AC70
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello !

My membership number is 489376.

Let me put some questions. I need to be clear up:
1 - Have PANA goals to E2E clients only or to mobility ones, too ?
2 - EAP protocol, I think will be the authentication method adopted by =
PANA. Am I wrong ? The two modes of EAP protocol (EAP-MD5 and EAP-TLS ?) =
What are the most important problems with EAP for PANA goals ? If the =
answer to the first question includes mobility, what will be the =
protocol ? WEP ?=20
3 - IPSec - the two modes of operation (tunnel and E2E with IPSec) will =
be guaranteed with a good QoS?
4 - The last one: 802.1x stack: EAP/LAN <---> EAP/RADIUS, how will be =
doing this connectivity ?

Chairs,

Jo=E3o Moreira 
------=_NextPart_000_0018_01C3B831.D0F4AC70
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.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV>Hello !<BR><BR>My membership number is 489376.</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Let me put some questions. I need to be =
clear=20
up:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>1 - Have PANA goals to E2E clients only =
or to=20
mobility ones, too ?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2 - EAP protocol, I think will be the=20
authentication method adopted by PANA. Am I wrong ? The two modes of EAP =

protocol (EAP-MD5 and EAP-TLS ?) What are the most important problems =
with EAP=20
for PANA goals ? If the answer to the first question includes mobility, =
what=20
will be the protocol ? WEP ?&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>3 - IPSec - the two modes of operation =
(tunnel and=20
E2E&nbsp;with IPSec) will be guaranteed with a good QoS?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>4 - The last one: 802.1x stack: EAP/LAN =
&lt;---&gt;=20
EAP/RADIUS, how will be doing this connectivity ?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Chairs,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Jo=E3o=20
Moreira</FONT>&nbsp;</DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0018_01C3B831.D0F4AC70--


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



From pana-admin@ietf.org  Mon Dec  1 12:57:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20026
	for <pana-archive@lists.ietf.org>; Mon, 1 Dec 2003 12:57:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQsI9-0005cV-Iq; Mon, 01 Dec 2003 12:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQsHr-0005cC-Fv
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 12:56: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 MAA19994
	for <pana@ietf.org>; Mon, 1 Dec 2003 12:56:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsHp-0005zC-00
	for pana@ietf.org; Mon, 01 Dec 2003 12:56:41 -0500
Received: from fep04-svc.mail.telepac.pt ([194.65.5.203])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsHo-0005yQ-00
	for pana@ietf.org; Mon, 01 Dec 2003 12:56:40 -0500
Received: from escritorio1 ([213.13.202.81]) by fep04-svc.mail.telepac.pt
          (InterMail vM.5.01.04.13 201-253-122-122-113-20020313) with SMTP
          id <20031201175603.JFVI17497.fep04-svc.mail.telepac.pt@escritorio1>
          for <pana@ietf.org>; Mon, 1 Dec 2003 17:56:03 +0000
Message-ID: <000d01c3b834$6b6afe10$ef74fea9@escritorio1>
From: "Joaquim Moreira" <moreirasantos@mail.telepac.pt>
To: <pana@ietf.org>
Date: Mon, 1 Dec 2003 17:56:17 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000A_01C3B834.6B44D870"
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] Questions
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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_000A_01C3B834.6B44D870
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello !

My membership number is 489376.

Let me put some questions. I need to be clear up:
1 - Have PANA goals to E2E clients only or to mobility ones, too ?
2 - EAP protocol, I think will be the authentication method adopted by =
PANA. Am I wrong ? The two modes of EAP protocol (EAP-MD5 and EAP-TLS ?) =
What are the most important problems with EAP for PANA goals ? If the =
answer to the first question includes mobility, what will be the =
protocol ? WEP ?=20
3 - IPSec - the two modes of operation (tunnel and E2E with IPSec) will =
be guaranteed with a good QoS?
4 - The last one: 802.1x stack: EAP/LAN <---> EAP/RADIUS, how will be =
doing this connectivity ?

Chairs,

Jo=E3o Moreira 
------=_NextPart_000_000A_01C3B834.6B44D870
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.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV>Hello !<BR><BR>My membership number is 489376.</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Let me put some questions. I need to be =
clear=20
up:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>1 - Have PANA goals to E2E clients only =
or to=20
mobility ones, too ?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2 - EAP protocol, I think will be the=20
authentication method adopted by PANA. Am I wrong ? The two modes of EAP =

protocol (EAP-MD5 and EAP-TLS ?) What are the most important problems =
with EAP=20
for PANA goals ? If the answer to the first question includes mobility, =
what=20
will be the protocol ? WEP ?&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>3 - IPSec - the two modes of operation =
(tunnel and=20
E2E&nbsp;with IPSec) will be guaranteed with a good QoS?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>4 - The last one: 802.1x stack: EAP/LAN =
&lt;---&gt;=20
EAP/RADIUS, how will be doing this connectivity ?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Chairs,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Jo=E3o =
Moreira</FONT>&nbsp;</DIV></DIV></BODY></HTML>

------=_NextPart_000_000A_01C3B834.6B44D870--


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


From exim@www1.ietf.org  Mon Dec  1 12:57:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20041
	for <pana-archive@odin.ietf.org>; Mon, 1 Dec 2003 12:57: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 1AQsID-0005d9-3J
	for pana-archive@odin.ietf.org; Mon, 01 Dec 2003 12:57:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1Hv5pi021639
	for pana-archive@odin.ietf.org; Mon, 1 Dec 2003 12:57:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQsIC-0005cw-Tl
	for pana-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 12:57: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 MAA20003
	for <pana-web-archive@ietf.org>; Mon, 1 Dec 2003 12:56:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsIB-0005zP-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 12:57:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsIA-0005zM-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 12:57:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQsI9-0005cV-Iq; Mon, 01 Dec 2003 12:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQsHr-0005cC-Fv
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 12:56: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 MAA19994
	for <pana@ietf.org>; Mon, 1 Dec 2003 12:56:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsHp-0005zC-00
	for pana@ietf.org; Mon, 01 Dec 2003 12:56:41 -0500
Received: from fep04-svc.mail.telepac.pt ([194.65.5.203])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsHo-0005yQ-00
	for pana@ietf.org; Mon, 01 Dec 2003 12:56:40 -0500
Received: from escritorio1 ([213.13.202.81]) by fep04-svc.mail.telepac.pt
          (InterMail vM.5.01.04.13 201-253-122-122-113-20020313) with SMTP
          id <20031201175603.JFVI17497.fep04-svc.mail.telepac.pt@escritorio1>
          for <pana@ietf.org>; Mon, 1 Dec 2003 17:56:03 +0000
Message-ID: <000d01c3b834$6b6afe10$ef74fea9@escritorio1>
From: "Joaquim Moreira" <moreirasantos@mail.telepac.pt>
To: <pana@ietf.org>
Date: Mon, 1 Dec 2003 17:56:17 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000A_01C3B834.6B44D870"
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] Questions
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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_000A_01C3B834.6B44D870
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello !

My membership number is 489376.

Let me put some questions. I need to be clear up:
1 - Have PANA goals to E2E clients only or to mobility ones, too ?
2 - EAP protocol, I think will be the authentication method adopted by =
PANA. Am I wrong ? The two modes of EAP protocol (EAP-MD5 and EAP-TLS ?) =
What are the most important problems with EAP for PANA goals ? If the =
answer to the first question includes mobility, what will be the =
protocol ? WEP ?=20
3 - IPSec - the two modes of operation (tunnel and E2E with IPSec) will =
be guaranteed with a good QoS?
4 - The last one: 802.1x stack: EAP/LAN <---> EAP/RADIUS, how will be =
doing this connectivity ?

Chairs,

Jo=E3o Moreira 
------=_NextPart_000_000A_01C3B834.6B44D870
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.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV>Hello !<BR><BR>My membership number is 489376.</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Let me put some questions. I need to be =
clear=20
up:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>1 - Have PANA goals to E2E clients only =
or to=20
mobility ones, too ?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2 - EAP protocol, I think will be the=20
authentication method adopted by PANA. Am I wrong ? The two modes of EAP =

protocol (EAP-MD5 and EAP-TLS ?) What are the most important problems =
with EAP=20
for PANA goals ? If the answer to the first question includes mobility, =
what=20
will be the protocol ? WEP ?&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>3 - IPSec - the two modes of operation =
(tunnel and=20
E2E&nbsp;with IPSec) will be guaranteed with a good QoS?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>4 - The last one: 802.1x stack: EAP/LAN =
&lt;---&gt;=20
EAP/RADIUS, how will be doing this connectivity ?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Chairs,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Jo=E3o =
Moreira</FONT>&nbsp;</DIV></DIV></BODY></HTML>

------=_NextPart_000_000A_01C3B834.6B44D870--


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



From pana-admin@ietf.org  Mon Dec  1 15:31:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27541
	for <pana-archive@lists.ietf.org>; Mon, 1 Dec 2003 15:31:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQuhK-00075r-NL; Mon, 01 Dec 2003 15:31:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQugq-00071y-Iz
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 15:30:40 -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 PAA27401
	for <pana@ietf.org>; Mon, 1 Dec 2003 15:30:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQugp-0007lM-00
	for pana@ietf.org; Mon, 01 Dec 2003 15:30:39 -0500
Received: from smtp804.mail.ukl.yahoo.com ([217.12.12.141])
	by ietf-mx with smtp (Exim 4.12)
	id 1AQugo-0007kA-00
	for pana@ietf.org; Mon, 01 Dec 2003 15:30:38 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login)
  by smtp1.bt.mail.vip.ukl.yahoo.com with SMTP; 1 Dec 2003 20:30:07 -0000
Message-ID: <006f01c3b849$ee3770c0$681067c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
References: <006701c3b848$325a2330$681067c0@adithya>
Subject: Re: [Pana] IP address configuration
Date: Mon, 1 Dec 2003 12:30:13 -0800
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

> 
> I took people off from cc and to fields.
> 
> A more general comment here. I tried to catch up with 
> about 50 emails on the pana mailing list and found that 
> the scenarios we are talking about with PANA+IPSec and IP
> address configuration etc. are becoming a bit complex.
> 
> I'm not up-to-date with all the documents, but it seems 
> that we have too many moving parts and architectural
> decisions that do not all affect plain PANA.
> 
I almost agree with this. But we are at a point to see what IP addresses
are used by PANA protocol itself as PANA runs over IP. Next
comes the question of  how the client acquires these IP addresses - before
or after PANA ? Then we agreed to document some access control
mechanism to prevent the service theft mentioned in the THREATS draft.
Perhaps we should stop here. At least the discussion should have two
separate threads. One is about address configuration and the access
control mechanism associated with it. Second one (might be out of
scope as mentioned by others) about using PANA to do much
more like securing RD/ND etc. 

So, large part of the discussion might still be in scope i think.

-mohan

> Br,
> - Dan
> 
> > -----Original Message-----
> > From: pana-admin@ietf.org [mailto:pana-admin@ietf.org]On Behalf Of ext
> > Mohan Parthasarathy
> > Sent: 26 November, 2003 21:53
> > To: Alper Yegin; Soliman Hesham; Yoshihiro.Ohba@tais.com
> > Cc: Bernard Aboba; Jari Arkko; James Kempf; pana@ietf.org
> > Subject: Re: [Pana] IP address configuration
> > 
> > 
> > 
> > > >> I'm trying to figure out how we can:
> > > >> - just maintain one DI for the PaC, and that is used as the
> > > >> local end-point
> > > >> of the IPsec tunnel (when IPsec-based access control is used)
> > > >
> > > >> - any other IP address can be configured inside this 
> > tunnel. Router
> > > >> discovery, ND, and DHCP can be run inside the tunnel. These
> > > >> IP addresses
> > > >> should not be used as PANA DI.
> > > >>
> > > >> I think supporting DHCP-based or autoconf based address
> > > >> configuration is
> > > >> required. Additional methods, like IKE-based address config,
> > > >> is nice to
> > > >> have.
> > > >
> > > > => When you talk about the IPsec tunnel are you always
> > > > referring to the use of IPsec for access control? I mean
> > > > you're never referring to a tunnel to a remote VPN in a
> > > > corporate many hops away, right?
> > >
> > > Yes, I'm not talking about a VPN tunnel to some corporate network.
> > >
> > > >
> > > > If the above is correct I don't know how stateless address
> > > > autoconfig is expected to work through that tunnel
> > >
> > > This is what I'm trying to understand too. What are the 
> > issues there?
> > >
> > It has been defined before e.g. ISATAP. But i  can see a few problems
> > here.
> > 
> > 1) How do you  send unsolicited RAs to so many PaCs ? Normally
> > it is sent to all-nodes multicast address that reaches all 
> > PaCs. Now, you
> > have to send multiple of them each with different protection for each
> > of the PaC. Solicited RAs work. So, this would be a limitation.
> > 
> > 2) The secure channel is between PaC and the AR. Two nodes cannot
> >      communicate with each other in a secure fashion. But 
> > this may not be
> >     a big limitation as the only on-link prefix is the 
> > link-local prefix
> > which is
> >     any way not used for normal communication.
> > 
> > -mohan
> > 
> > > > and why
> > > > it needs to??
> > >
> > > Running router discovery and neighbor discovery (for DAD) 
> > inside the IPsec
> > > tunnel would provide additional security to the network. 
> > This ensures, for
> > > example, PaC does not receive unauthorized router advertisements.
> > >
> > > > A node could use one address only, same in
> > > > the outer and inner src fields. What am I missing?
> > >
> > > It could. But in the case of IPv6, using the link-local 
> > address as the
> > outer
> > > address, and the global address as the inner address makes 
> > sense to me.
> > >
> > > Alper
> > >
> > > >
> > > >
> > > > Hesham
> > > >
> > >
> > >
> > > _______________________________________________
> > > Pana mailing 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  Mon Dec  1 15:31:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27606
	for <pana-archive@odin.ietf.org>; Mon, 1 Dec 2003 15:31:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQuhQ-00079H-72
	for pana-archive@odin.ietf.org; Mon, 01 Dec 2003 15:31:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1KVGuG027473
	for pana-archive@odin.ietf.org; Mon, 1 Dec 2003 15:31:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQuhP-00078t-Oc
	for pana-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 15:31:15 -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 PAA27481
	for <pana-web-archive@ietf.org>; Mon, 1 Dec 2003 15:31:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQuhN-0007m6-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 15:31:13 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQuhM-0007m3-00
	for pana-web-archive@ietf.org; Mon, 01 Dec 2003 15:31:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQuhK-00075r-NL; Mon, 01 Dec 2003 15:31:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQugq-00071y-Iz
	for pana@optimus.ietf.org; Mon, 01 Dec 2003 15:30:40 -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 PAA27401
	for <pana@ietf.org>; Mon, 1 Dec 2003 15:30:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQugp-0007lM-00
	for pana@ietf.org; Mon, 01 Dec 2003 15:30:39 -0500
Received: from smtp804.mail.ukl.yahoo.com ([217.12.12.141])
	by ietf-mx with smtp (Exim 4.12)
	id 1AQugo-0007kA-00
	for pana@ietf.org; Mon, 01 Dec 2003 15:30:38 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login)
  by smtp1.bt.mail.vip.ukl.yahoo.com with SMTP; 1 Dec 2003 20:30:07 -0000
Message-ID: <006f01c3b849$ee3770c0$681067c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: <Dan.Forsberg@nokia.com>, <pana@ietf.org>
References: <006701c3b848$325a2330$681067c0@adithya>
Subject: Re: [Pana] IP address configuration
Date: Mon, 1 Dec 2003 12:30:13 -0800
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

> 
> I took people off from cc and to fields.
> 
> A more general comment here. I tried to catch up with 
> about 50 emails on the pana mailing list and found that 
> the scenarios we are talking about with PANA+IPSec and IP
> address configuration etc. are becoming a bit complex.
> 
> I'm not up-to-date with all the documents, but it seems 
> that we have too many moving parts and architectural
> decisions that do not all affect plain PANA.
> 
I almost agree with this. But we are at a point to see what IP addresses
are used by PANA protocol itself as PANA runs over IP. Next
comes the question of  how the client acquires these IP addresses - before
or after PANA ? Then we agreed to document some access control
mechanism to prevent the service theft mentioned in the THREATS draft.
Perhaps we should stop here. At least the discussion should have two
separate threads. One is about address configuration and the access
control mechanism associated with it. Second one (might be out of
scope as mentioned by others) about using PANA to do much
more like securing RD/ND etc. 

So, large part of the discussion might still be in scope i think.

-mohan

> Br,
> - Dan
> 
> > -----Original Message-----
> > From: pana-admin@ietf.org [mailto:pana-admin@ietf.org]On Behalf Of ext
> > Mohan Parthasarathy
> > Sent: 26 November, 2003 21:53
> > To: Alper Yegin; Soliman Hesham; Yoshihiro.Ohba@tais.com
> > Cc: Bernard Aboba; Jari Arkko; James Kempf; pana@ietf.org
> > Subject: Re: [Pana] IP address configuration
> > 
> > 
> > 
> > > >> I'm trying to figure out how we can:
> > > >> - just maintain one DI for the PaC, and that is used as the
> > > >> local end-point
> > > >> of the IPsec tunnel (when IPsec-based access control is used)
> > > >
> > > >> - any other IP address can be configured inside this 
> > tunnel. Router
> > > >> discovery, ND, and DHCP can be run inside the tunnel. These
> > > >> IP addresses
> > > >> should not be used as PANA DI.
> > > >>
> > > >> I think supporting DHCP-based or autoconf based address
> > > >> configuration is
> > > >> required. Additional methods, like IKE-based address config,
> > > >> is nice to
> > > >> have.
> > > >
> > > > => When you talk about the IPsec tunnel are you always
> > > > referring to the use of IPsec for access control? I mean
> > > > you're never referring to a tunnel to a remote VPN in a
> > > > corporate many hops away, right?
> > >
> > > Yes, I'm not talking about a VPN tunnel to some corporate network.
> > >
> > > >
> > > > If the above is correct I don't know how stateless address
> > > > autoconfig is expected to work through that tunnel
> > >
> > > This is what I'm trying to understand too. What are the 
> > issues there?
> > >
> > It has been defined before e.g. ISATAP. But i  can see a few problems
> > here.
> > 
> > 1) How do you  send unsolicited RAs to so many PaCs ? Normally
> > it is sent to all-nodes multicast address that reaches all 
> > PaCs. Now, you
> > have to send multiple of them each with different protection for each
> > of the PaC. Solicited RAs work. So, this would be a limitation.
> > 
> > 2) The secure channel is between PaC and the AR. Two nodes cannot
> >      communicate with each other in a secure fashion. But 
> > this may not be
> >     a big limitation as the only on-link prefix is the 
> > link-local prefix
> > which is
> >     any way not used for normal communication.
> > 
> > -mohan
> > 
> > > > and why
> > > > it needs to??
> > >
> > > Running router discovery and neighbor discovery (for DAD) 
> > inside the IPsec
> > > tunnel would provide additional security to the network. 
> > This ensures, for
> > > example, PaC does not receive unauthorized router advertisements.
> > >
> > > > A node could use one address only, same in
> > > > the outer and inner src fields. What am I missing?
> > >
> > > It could. But in the case of IPv6, using the link-local 
> > address as the
> > outer
> > > address, and the global address as the inner address makes 
> > sense to me.
> > >
> > > Alper
> > >
> > > >
> > > >
> > > > Hesham
> > > >
> > >
> > >
> > > _______________________________________________
> > > Pana mailing 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  Tue Dec  2 05:23:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10778
	for <pana-archive@lists.ietf.org>; Tue, 2 Dec 2003 05:23:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR7gL-0007Yb-PH; Tue, 02 Dec 2003 05:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR7ff-0007Xf-3v
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 05:22:19 -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 FAA10765
	for <pana@ietf.org>; Tue, 2 Dec 2003 05:22:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7fb-0004XW-00
	for pana@ietf.org; Tue, 02 Dec 2003 05:22:15 -0500
Received: from na5.alcatel.fr ([194.133.58.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7fa-0004XI-00
	for pana@ietf.org; Tue, 02 Dec 2003 05:22:15 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB2ALU7F019307;
	Tue, 2 Dec 2003 11:21:30 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120211212682:3113 ;
          Tue, 2 Dec 2003 11:21:26 +0100 
Message-ID: <3FCC67A7.6000604@alcatel.fr>
Date: Tue, 02 Dec 2003 11:21:27 +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 <aeyegin@hotmail.com>
Cc: alper@docomolabs-usa.com, pana@ietf.org, lionel.morand@francetelecom.com,
        yohba@tari.toshiba.com, Julien.Bournelle@int-evry.fr
Subject: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol requirements)
References: <Law12-F66K6J2DJkhYU00023329@hotmail.com>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:21:26,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:21:30
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Alcanet-MTA-scanned-and-authorized: yes
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

hi Alper,

Alper Yegin a =E9crit:
>=20
> (sorry for the late and batched responses due to my travels)
>=20
>=20
>> > I'm not sure how much "explicit support" we need for this from the=20
>> PAA2EP
>> > protocol. There can always be ad-hoc solutions to this. For example,=20
>> running
>> > some request-reply messages between the PAA and EP can be used as a
>> > keep-alive. I can imagine an implementation resorting to such=20
>> techniques
>> > when the protocol does not have a dedicated facility....
>>
>> ok. my feeling is you think it's not a requirement at all :-)
>=20
>=20
> I don't think it is a hard requirement on the PAA2EP protocol.
> It may be a requirement of the architecture which can be satisfied
> by other means...

what is required then ? is the following sounds correct:

the PAA-2-EP protocol must enable the PAA to detect inactive EPs. this=20
does not mean that the PAA-2-EP protocol must support a heartbeat=20
mechanism or any other specific feature.
if yes, it is a good point, but the only requirement is that the=20
PAA-2-EP protocol must not prevent to address this problem by other=20
means (see above).

thanks,
Yacine


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


From exim@www1.ietf.org  Tue Dec  2 05:23:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10796
	for <pana-archive@odin.ietf.org>; Tue, 2 Dec 2003 05: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 1AR7gR-0007ZG-AH
	for pana-archive@odin.ietf.org; Tue, 02 Dec 2003 05:23:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2AN7A7029090
	for pana-archive@odin.ietf.org; Tue, 2 Dec 2003 05:23:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR7gP-0007Z5-Ps
	for pana-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 05:23: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 FAA10775
	for <pana-web-archive@ietf.org>; Tue, 2 Dec 2003 05:22:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7gM-0004Xg-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 05:23:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7gM-0004Xd-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 05: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 1AR7gL-0007Yb-PH; Tue, 02 Dec 2003 05:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR7ff-0007Xf-3v
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 05:22:19 -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 FAA10765
	for <pana@ietf.org>; Tue, 2 Dec 2003 05:22:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7fb-0004XW-00
	for pana@ietf.org; Tue, 02 Dec 2003 05:22:15 -0500
Received: from na5.alcatel.fr ([194.133.58.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7fa-0004XI-00
	for pana@ietf.org; Tue, 02 Dec 2003 05:22:15 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB2ALU7F019307;
	Tue, 2 Dec 2003 11:21:30 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120211212682:3113 ;
          Tue, 2 Dec 2003 11:21:26 +0100 
Message-ID: <3FCC67A7.6000604@alcatel.fr>
Date: Tue, 02 Dec 2003 11:21:27 +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 <aeyegin@hotmail.com>
Cc: alper@docomolabs-usa.com, pana@ietf.org, lionel.morand@francetelecom.com,
        yohba@tari.toshiba.com, Julien.Bournelle@int-evry.fr
Subject: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol requirements)
References: <Law12-F66K6J2DJkhYU00023329@hotmail.com>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:21:26,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:21:30
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Alcanet-MTA-scanned-and-authorized: yes
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

hi Alper,

Alper Yegin a =E9crit:
>=20
> (sorry for the late and batched responses due to my travels)
>=20
>=20
>> > I'm not sure how much "explicit support" we need for this from the=20
>> PAA2EP
>> > protocol. There can always be ad-hoc solutions to this. For example,=20
>> running
>> > some request-reply messages between the PAA and EP can be used as a
>> > keep-alive. I can imagine an implementation resorting to such=20
>> techniques
>> > when the protocol does not have a dedicated facility....
>>
>> ok. my feeling is you think it's not a requirement at all :-)
>=20
>=20
> I don't think it is a hard requirement on the PAA2EP protocol.
> It may be a requirement of the architecture which can be satisfied
> by other means...

what is required then ? is the following sounds correct:

the PAA-2-EP protocol must enable the PAA to detect inactive EPs. this=20
does not mean that the PAA-2-EP protocol must support a heartbeat=20
mechanism or any other specific feature.
if yes, it is a good point, but the only requirement is that the=20
PAA-2-EP protocol must not prevent to address this problem by other=20
means (see above).

thanks,
Yacine


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



From pana-admin@ietf.org  Tue Dec  2 05:42:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11321
	for <pana-archive@lists.ietf.org>; Tue, 2 Dec 2003 05:42: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 1AR7yk-000073-Hf; Tue, 02 Dec 2003 05: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 1AR7yQ-00006B-62
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 05:41:42 -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 FAA11295;
	Tue, 2 Dec 2003 05:41:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7yM-0004ku-00; Tue, 02 Dec 2003 05:41:38 -0500
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7yL-0004kH-00; Tue, 02 Dec 2003 05:41:37 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB2Af07F007918;
	Tue, 2 Dec 2003 11:41:01 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120211405635:3348 ;
          Tue, 2 Dec 2003 11:40:56 +0100 
Message-ID: <3FCC6C38.5040708@alcatel.fr>
Date: Tue, 02 Dec 2003 11:40:56 +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: Yoshihiro.Ohba@tais.com
Cc: alper@docomolabs-usa.com, Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        MORAND Lionel FTRD/DAC/ISS <lionel.morand@francetelecom.com>,
        pana@ietf.org, pana-admin@ietf.org,
        Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Accounting from the EPs (was Re: [Pana] PAA-2-EP protocol requirements)
References: <OFFA154088.AAD261F8-ON88256DEF.005C2C7A@tais.net>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:40:56,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:41:00,
	Serialize complete at 12/02/2003 11:41:00
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Alcanet-MTA-scanned-and-authorized: yes
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 and al,

>    > c) Accounting/Feedback from the EPs:
>    > The PAA must have an efficient way to to get the accounting
>    information
>    > of PaC from EP since the PAA may be a client of the AAA backend
>    > infrastructure.
> 
>    Getting statistics from the EP makes sense. For example, in the case of
>    SNMP, if we get the counters from the EP this is good enough. The AAA
>    client
>    sitting on the PAA can turn these into accoutning records.
> 
> I agree.  Should we eliminate the case where EP itself directly sends
> accounting records to the accounting server?  I am asking because AAA clients for
> authentication sessions and accounting sessions can be separated entities in Diameter, as long as
> there is a way to
> associate an accounting session with an authentication session.
> 

I agree. this is an important issue: is polling sufficient for the AA 
purposes ?

FYI, SNMP provides event-based notifications. I'm not sure if an SNMP 
agents (EPs) can send records periodically to the manager (PAA)...


Yacine


> 
> Yoshihiro Ohba
> 
> 
> 
>    Alper
> 
> 
> 
>    >
>    > d) ????
>    >
>    >
>    > thanks,
>    > Yacine El Mghazli
>    >
>    >
>    >
> 
> 
> 
> 



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


From exim@www1.ietf.org  Tue Dec  2 05:42:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11336
	for <pana-archive@odin.ietf.org>; Tue, 2 Dec 2003 05: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 1AR7yn-000096-89
	for pana-archive@odin.ietf.org; Tue, 02 Dec 2003 05:42:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2Ag5Rk000554
	for pana-archive@odin.ietf.org; Tue, 2 Dec 2003 05:42:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR7yn-00008r-1V
	for pana-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 05:42: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 FAA11311
	for <pana-web-archive@ietf.org>; Tue, 2 Dec 2003 05:41:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7yj-0004lT-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 05:42:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7yj-0004lQ-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 05:42:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR7yk-000073-Hf; Tue, 02 Dec 2003 05: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 1AR7yQ-00006B-62
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 05:41:42 -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 FAA11295;
	Tue, 2 Dec 2003 05:41:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7yM-0004ku-00; Tue, 02 Dec 2003 05:41:38 -0500
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR7yL-0004kH-00; Tue, 02 Dec 2003 05:41:37 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB2Af07F007918;
	Tue, 2 Dec 2003 11:41:01 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120211405635:3348 ;
          Tue, 2 Dec 2003 11:40:56 +0100 
Message-ID: <3FCC6C38.5040708@alcatel.fr>
Date: Tue, 02 Dec 2003 11:40:56 +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: Yoshihiro.Ohba@tais.com
Cc: alper@docomolabs-usa.com, Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        MORAND Lionel FTRD/DAC/ISS <lionel.morand@francetelecom.com>,
        pana@ietf.org, pana-admin@ietf.org,
        Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Accounting from the EPs (was Re: [Pana] PAA-2-EP protocol requirements)
References: <OFFA154088.AAD261F8-ON88256DEF.005C2C7A@tais.net>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:40:56,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:41:00,
	Serialize complete at 12/02/2003 11:41:00
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Alcanet-MTA-scanned-and-authorized: yes
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 and al,

>    > c) Accounting/Feedback from the EPs:
>    > The PAA must have an efficient way to to get the accounting
>    information
>    > of PaC from EP since the PAA may be a client of the AAA backend
>    > infrastructure.
> 
>    Getting statistics from the EP makes sense. For example, in the case of
>    SNMP, if we get the counters from the EP this is good enough. The AAA
>    client
>    sitting on the PAA can turn these into accoutning records.
> 
> I agree.  Should we eliminate the case where EP itself directly sends
> accounting records to the accounting server?  I am asking because AAA clients for
> authentication sessions and accounting sessions can be separated entities in Diameter, as long as
> there is a way to
> associate an accounting session with an authentication session.
> 

I agree. this is an important issue: is polling sufficient for the AA 
purposes ?

FYI, SNMP provides event-based notifications. I'm not sure if an SNMP 
agents (EPs) can send records periodically to the manager (PAA)...


Yacine


> 
> Yoshihiro Ohba
> 
> 
> 
>    Alper
> 
> 
> 
>    >
>    > d) ????
>    >
>    >
>    > thanks,
>    > Yacine El Mghazli
>    >
>    >
>    >
> 
> 
> 
> 



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



From pana-admin@ietf.org  Tue Dec  2 05:50:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11633
	for <pana-archive@lists.ietf.org>; Tue, 2 Dec 2003 05:50: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 1AR86U-0000jP-0I; Tue, 02 Dec 2003 05:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR86K-0000ir-Fh
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 05:49: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 FAA11605;
	Tue, 2 Dec 2003 05:49:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR86G-0004rR-00; Tue, 02 Dec 2003 05:49:48 -0500
Received: from colt-na7.alcatel.fr ([62.23.212.7] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR86F-0004rG-00; Tue, 02 Dec 2003 05:49:48 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB2An77F017428;
	Tue, 2 Dec 2003 11:49:07 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120211490573:3442 ;
          Tue, 2 Dec 2003 11:49:05 +0100 
Message-ID: <3FCC6E22.2020700@alcatel.fr>
Date: Tue, 02 Dec 2003 11:49:06 +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: Yoshihiro.Ohba@tais.com
Cc: alper@docomolabs-usa.com, Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        MORAND Lionel FTRD/DAC/ISS <lionel.morand@francetelecom.com>,
        pana@ietf.org, pana-admin@ietf.org,
        Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol requirements)
References: <OFFA154088.AAD261F8-ON88256DEF.005C2C7A@tais.net>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:49:05,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:49:07
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Alcanet-MTA-scanned-and-authorized: yes
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

hi Yoshi:

Yoshihiro.Ohba@tais.com a =E9crit:
>    > a) Inactive peer detection:
>    > The protocol used between PAA and EP should be able to detect inacti=
ve
>    > peer within an appropriate time period. This can be achieved by havi=
ng
>    > both the EP and remote PAA constantly verify their connection to each
>    > other via keep-alive messages: a heartbeat in fact.
>=20
>    I'm not sure how much "explicit support" we need for this from the
>    PAA2EP
>    protocol. There can always be ad-hoc solutions to this. For example,
>    running
>    some request-reply messages between the PAA and EP can be used as a
>    keep-alive. I can imagine an implementation resorting to such techniqu=
es
>    when the protocol does not have a dedicated facility....
>=20
>=20
> Yes, some SMNP implementation can support small value (order of seconds)
> for
> miminum polling inverval.  This would be sufficient for inactive peer
> detection, but
> not sufficient for detecting =5Frebooted=5F peer when rebooting can compl=
ete
> within
> SNMP polling interval. Rebooting detection is needed when EP store
> PaC information (including accounting information) in volatile memory.
>=20
> So we might need to define some rebooting counters in SNMP MIB in order to
> detect
> rebooting peers, or if such a MIB already exists we might just specify the
> use of
> the MIB for both inactive/rebooted peer detection.


I'm not sure to rightly understand what you mean here, please can you=20
elaborate ?

thanks in advance,
Yacine


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


From exim@www1.ietf.org  Tue Dec  2 05:50:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11648
	for <pana-archive@odin.ietf.org>; Tue, 2 Dec 2003 05:50: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 1AR86X-0000k7-9d
	for pana-archive@odin.ietf.org; Tue, 02 Dec 2003 05:50:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2Ao5OK002849
	for pana-archive@odin.ietf.org; Tue, 2 Dec 2003 05:50:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR86W-0000js-Qe
	for pana-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 05:50: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 FAA11619
	for <pana-web-archive@ietf.org>; Tue, 2 Dec 2003 05:49:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR86T-0004rj-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 05:50:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR86S-0004rg-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 05:50:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR86U-0000jP-0I; Tue, 02 Dec 2003 05:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR86K-0000ir-Fh
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 05:49: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 FAA11605;
	Tue, 2 Dec 2003 05:49:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR86G-0004rR-00; Tue, 02 Dec 2003 05:49:48 -0500
Received: from colt-na7.alcatel.fr ([62.23.212.7] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR86F-0004rG-00; Tue, 02 Dec 2003 05:49:48 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB2An77F017428;
	Tue, 2 Dec 2003 11:49:07 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120211490573:3442 ;
          Tue, 2 Dec 2003 11:49:05 +0100 
Message-ID: <3FCC6E22.2020700@alcatel.fr>
Date: Tue, 02 Dec 2003 11:49:06 +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: Yoshihiro.Ohba@tais.com
Cc: alper@docomolabs-usa.com, Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        MORAND Lionel FTRD/DAC/ISS <lionel.morand@francetelecom.com>,
        pana@ietf.org, pana-admin@ietf.org,
        Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol requirements)
References: <OFFA154088.AAD261F8-ON88256DEF.005C2C7A@tais.net>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:49:05,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 11:49:07
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Alcanet-MTA-scanned-and-authorized: yes
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

hi Yoshi:

Yoshihiro.Ohba@tais.com a =E9crit:
>    > a) Inactive peer detection:
>    > The protocol used between PAA and EP should be able to detect inacti=
ve
>    > peer within an appropriate time period. This can be achieved by havi=
ng
>    > both the EP and remote PAA constantly verify their connection to each
>    > other via keep-alive messages: a heartbeat in fact.
>=20
>    I'm not sure how much "explicit support" we need for this from the
>    PAA2EP
>    protocol. There can always be ad-hoc solutions to this. For example,
>    running
>    some request-reply messages between the PAA and EP can be used as a
>    keep-alive. I can imagine an implementation resorting to such techniqu=
es
>    when the protocol does not have a dedicated facility....
>=20
>=20
> Yes, some SMNP implementation can support small value (order of seconds)
> for
> miminum polling inverval.  This would be sufficient for inactive peer
> detection, but
> not sufficient for detecting =5Frebooted=5F peer when rebooting can compl=
ete
> within
> SNMP polling interval. Rebooting detection is needed when EP store
> PaC information (including accounting information) in volatile memory.
>=20
> So we might need to define some rebooting counters in SNMP MIB in order to
> detect
> rebooting peers, or if such a MIB already exists we might just specify the
> use of
> the MIB for both inactive/rebooted peer detection.


I'm not sure to rightly understand what you mean here, please can you=20
elaborate ?

thanks in advance,
Yacine


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



From pana-admin@ietf.org  Tue Dec  2 06:20:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12358
	for <pana-archive@lists.ietf.org>; Tue, 2 Dec 2003 06:20: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 1AR8ZX-00027X-0B; Tue, 02 Dec 2003 06:20:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR8Yp-00024l-Sh
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 06:19:20 -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 GAA12295
	for <pana@ietf.org>; Tue, 2 Dec 2003 06:19:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8Yl-00059a-00
	for pana@ietf.org; Tue, 02 Dec 2003 06:19:15 -0500
Received: from colt-na7.alcatel.fr ([62.23.212.7] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8Yl-00059K-00
	for pana@ietf.org; Tue, 02 Dec 2003 06:19:15 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB2BIL7G015784;
	Tue, 2 Dec 2003 12:18:29 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120212181938:3787 ;
          Tue, 2 Dec 2003 12:18:19 +0100 
Message-ID: <3FCC74FB.7010400@alcatel.fr>
Date: Tue, 02 Dec 2003 12:18:19 +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 <aeyegin@hotmail.com>
Cc: alper@docomolabs-usa.com, pana@ietf.org, lionel.morand@francetelecom.com,
        yohba@tari.toshiba.com, Julien.Bournelle@int-evry.fr
Subject: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol requirements)
References: <Law12-F66K6J2DJkhYU00023329@hotmail.com>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 12:18:19,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 12:18:29,
	Serialize complete at 12/02/2003 12:18:29
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Alcanet-MTA-scanned-and-authorized: yes
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 Alper:

 >> anyway, these questions bring up some PANA framework issues related to
 >> the EP-PAA relation when we have multiple PAAs in the access network:
 >> * can a given EP relate to multiple PAAs ?
 >
 >
 > I think we had discussed that there may be multiple PAAs on a link,
 > but the PaC will run PANA with one of them. So, I guess yes, an EP
 > might be associated with more than one PAA.
 >
 >> * does a given PAA configure all the EPs with the same rules ?
 >
 > The provisioning info pushed to EPs for a given PaC would be the
 > same.
 >
 >> * or only the one which treat the traffic coming from the PaC ?
 >
 >
 > Well, PAA decides which EPs should receive the information. And this
 > depends on the topology. For a multi-access link with multiple access
 > routers as EPs, each router will be provisioned with the PaC-specific
 > info.
 >
 > On the other hand, if a switch is the EP, as a L2 access device there is
 > only one connected to PaC and that single device is the EP. It will be
 > provisioned with the PaC-specific info.

my understanding is the following:

PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network. 
For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by 
configuring the concerned EPs. depending on the topology, there could be 
more than one.

does it look correct ?

 >> * inter-PAAs communication ?
 >
 >
 > Why do we need this for?

for exemple: context transfer between PAAs for mobility handling (in 
order to avoid re-authentication, which would reduce the handover perf).
this is strongly dependent of the relation between PAA and EPs discussed 
above.

 > Alper

Yacine

 >> etc...
 >>
 >> comments on these "issues" are warmly welcome !
 >>
 >>
 >>
 >> >>c) Accounting/Feedback from the EPs:
 >> >>The PAA must have an efficient way to to get the accounting 
information
 >> >>of PaC from EP since the PAA may be a client of the AAA backend
 >> >>infrastructure.
 >> >
 >> >
 >> > Getting statistics from the EP makes sense. For example, in the 
case of
 >> > SNMP, if we get the counters from the EP this is good enough. The
 >> AAA client
 >> > sitting on the PAA can turn these into accoutning records.
 >>
 >> should the PAA poll the EPs to get these counters when needed (the
 >> SNMP way...) or the EPs are supposed to send them periodically ?
 >>
 >> anyway, this should be somehow a requirement.
 >>
 >>
 >> > Alper
 >> >
 >>
 >> thanks,
 >> yacine
 >>
 >> >>d) ????
 >> >>
 >> >>
 >> >>thanks,
 >> >>Yacine El Mghazli
 >> >>
 >> >>
 >> >>
 >> >>
 >> >>
 >> >>
 >> >>_______________________________________________
 >> >>Pana mailing 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
 >
 >
 > _________________________________________________________________
 > Set yourself up for fun at home!  Get tips on home entertainment
 > equipment, video game reviews, and more here.
 > http://special.msn.com/home/homeent.armx
 >
 >




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


From exim@www1.ietf.org  Tue Dec  2 06:20:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12376
	for <pana-archive@odin.ietf.org>; Tue, 2 Dec 2003 06:20: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 1AR8Zi-0002FT-1n
	for pana-archive@odin.ietf.org; Tue, 02 Dec 2003 06:20:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2BKDaX008633
	for pana-archive@odin.ietf.org; Tue, 2 Dec 2003 06:20:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR8Zg-0002Er-7k
	for pana-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 06:20: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 GAA12328
	for <pana-web-archive@ietf.org>; Tue, 2 Dec 2003 06:19:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8Zc-0005AK-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 06:20:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8Zb-0005AF-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 06:20:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR8ZX-00027X-0B; Tue, 02 Dec 2003 06:20:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR8Yp-00024l-Sh
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 06:19:20 -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 GAA12295
	for <pana@ietf.org>; Tue, 2 Dec 2003 06:19:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8Yl-00059a-00
	for pana@ietf.org; Tue, 02 Dec 2003 06:19:15 -0500
Received: from colt-na7.alcatel.fr ([62.23.212.7] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8Yl-00059K-00
	for pana@ietf.org; Tue, 02 Dec 2003 06:19:15 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB2BIL7G015784;
	Tue, 2 Dec 2003 12:18:29 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120212181938:3787 ;
          Tue, 2 Dec 2003 12:18:19 +0100 
Message-ID: <3FCC74FB.7010400@alcatel.fr>
Date: Tue, 02 Dec 2003 12:18:19 +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 <aeyegin@hotmail.com>
Cc: alper@docomolabs-usa.com, pana@ietf.org, lionel.morand@francetelecom.com,
        yohba@tari.toshiba.com, Julien.Bournelle@int-evry.fr
Subject: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol requirements)
References: <Law12-F66K6J2DJkhYU00023329@hotmail.com>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 12:18:19,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/02/2003 12:18:29,
	Serialize complete at 12/02/2003 12:18:29
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Alcanet-MTA-scanned-and-authorized: yes
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 Alper:

 >> anyway, these questions bring up some PANA framework issues related to
 >> the EP-PAA relation when we have multiple PAAs in the access network:
 >> * can a given EP relate to multiple PAAs ?
 >
 >
 > I think we had discussed that there may be multiple PAAs on a link,
 > but the PaC will run PANA with one of them. So, I guess yes, an EP
 > might be associated with more than one PAA.
 >
 >> * does a given PAA configure all the EPs with the same rules ?
 >
 > The provisioning info pushed to EPs for a given PaC would be the
 > same.
 >
 >> * or only the one which treat the traffic coming from the PaC ?
 >
 >
 > Well, PAA decides which EPs should receive the information. And this
 > depends on the topology. For a multi-access link with multiple access
 > routers as EPs, each router will be provisioned with the PaC-specific
 > info.
 >
 > On the other hand, if a switch is the EP, as a L2 access device there is
 > only one connected to PaC and that single device is the EP. It will be
 > provisioned with the PaC-specific info.

my understanding is the following:

PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network. 
For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by 
configuring the concerned EPs. depending on the topology, there could be 
more than one.

does it look correct ?

 >> * inter-PAAs communication ?
 >
 >
 > Why do we need this for?

for exemple: context transfer between PAAs for mobility handling (in 
order to avoid re-authentication, which would reduce the handover perf).
this is strongly dependent of the relation between PAA and EPs discussed 
above.

 > Alper

Yacine

 >> etc...
 >>
 >> comments on these "issues" are warmly welcome !
 >>
 >>
 >>
 >> >>c) Accounting/Feedback from the EPs:
 >> >>The PAA must have an efficient way to to get the accounting 
information
 >> >>of PaC from EP since the PAA may be a client of the AAA backend
 >> >>infrastructure.
 >> >
 >> >
 >> > Getting statistics from the EP makes sense. For example, in the 
case of
 >> > SNMP, if we get the counters from the EP this is good enough. The
 >> AAA client
 >> > sitting on the PAA can turn these into accoutning records.
 >>
 >> should the PAA poll the EPs to get these counters when needed (the
 >> SNMP way...) or the EPs are supposed to send them periodically ?
 >>
 >> anyway, this should be somehow a requirement.
 >>
 >>
 >> > Alper
 >> >
 >>
 >> thanks,
 >> yacine
 >>
 >> >>d) ????
 >> >>
 >> >>
 >> >>thanks,
 >> >>Yacine El Mghazli
 >> >>
 >> >>
 >> >>
 >> >>
 >> >>
 >> >>
 >> >>_______________________________________________
 >> >>Pana mailing 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
 >
 >
 > _________________________________________________________________
 > Set yourself up for fun at home!  Get tips on home entertainment
 > equipment, video game reviews, and more here.
 > http://special.msn.com/home/homeent.armx
 >
 >




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



From pana-admin@ietf.org  Tue Dec  2 06:21:17 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12424
	for <pana-archive@lists.ietf.org>; Tue, 2 Dec 2003 06:21:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR8aT-0002GJ-TD; Tue, 02 Dec 2003 06:21:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR8ZV-000279-CU
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 06:20: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 GAA12321
	for <pana@ietf.org>; Tue, 2 Dec 2003 06:19:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8ZR-0005A9-00
	for pana@ietf.org; Tue, 02 Dec 2003 06:19:57 -0500
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8ZQ-00059r-00
	for pana@ietf.org; Tue, 02 Dec 2003 06:19:57 -0500
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP
	id C1E46340FE; Tue,  2 Dec 2003 12:16:32 +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 DEF7C3F4E6; Tue,  2 Dec 2003 12:15:20 +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 M2003120212150504821
 ; Tue, 02 Dec 2003 12:15:05 +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 3C6603F4B9; Tue,  2 Dec 2003 12:13:25 +0100 (CET)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1AR8SC-00075G-Ci; Tue, 02 Dec 2003 12:12:28 +0100
Date: Tue, 2 Dec 2003 12:12:28 +0100
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Alper Yegin <aeyegin@hotmail.com>
Cc: pana@ietf.org
Subject: Re: [Pana] Re: PAA-2-EP protocol requirements
Message-ID: <20031202111228.GN14833@ipv6-5.int-evry.fr>
References: <LAW12-F74CV3EJnl1At00012116@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <LAW12-F74CV3EJnl1At00012116@hotmail.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 Sun, Nov 30, 2003 at 02:41:30PM -0800, Alper Yegin wrote:
> >If we want to use IPsec between PaC and EP, the EP must be a router. AS
> >the PAA must be located exactly one IP hop away from the PaC, there must
> >be no EP between PaC and PAA. So it means that EP, PaC and PAA are
> >on the same IP subnet (Am I wrong ?). So, I wonder if it a valid scenario 
> >to have
> >multiple EPs per PAA if we use IPsec.
> 
> If the access routers are used as EP and there are more than one....
> PAA may be co-located with one of the access routers, or may be hosted
> on a dedicated server on the same multi-access link shared by the access
> routers and PaCs.

ok, but I wonder if people think useful to have multiple AR advertising
the same IP subnet. (Do I miss 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 Dec  2 06:21:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12439
	for <pana-archive@odin.ietf.org>; Tue, 2 Dec 2003 06:21:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR8aV-0002IG-FW
	for pana-archive@odin.ietf.org; Tue, 02 Dec 2003 06:21:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2BL3JC008808
	for pana-archive@odin.ietf.org; Tue, 2 Dec 2003 06:21:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR8aU-0002H7-Tu
	for pana-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 06:21: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 GAA12411
	for <pana-web-archive@ietf.org>; Tue, 2 Dec 2003 06:20:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8aQ-0005B6-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 06:20:59 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8aQ-0005B3-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 06:20:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR8aT-0002GJ-TD; Tue, 02 Dec 2003 06:21:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AR8ZV-000279-CU
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 06:20: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 GAA12321
	for <pana@ietf.org>; Tue, 2 Dec 2003 06:19:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8ZR-0005A9-00
	for pana@ietf.org; Tue, 02 Dec 2003 06:19:57 -0500
Received: from herculanum.int-evry.fr ([157.159.11.15])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AR8ZQ-00059r-00
	for pana@ietf.org; Tue, 02 Dec 2003 06:19:57 -0500
Received: from sparte.int-evry.fr (spartebis.int-evry.fr [157.159.10.20])
	by herculanum.int-evry.fr (Postfix) with ESMTP
	id C1E46340FE; Tue,  2 Dec 2003 12:16:32 +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 DEF7C3F4E6; Tue,  2 Dec 2003 12:15:20 +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 M2003120212150504821
 ; Tue, 02 Dec 2003 12:15:05 +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 3C6603F4B9; Tue,  2 Dec 2003 12:13:25 +0100 (CET)
Received: from jb by ipv6-5.int-evry.fr with local (Exim id 1AR8SC-00075G-Ci; Tue, 02 Dec 2003 12:12:28 +0100
Date: Tue, 2 Dec 2003 12:12:28 +0100
From: Julien Bournelle <Julien.Bournelle@int-evry.fr>
To: Alper Yegin <aeyegin@hotmail.com>
Cc: pana@ietf.org
Subject: Re: [Pana] Re: PAA-2-EP protocol requirements
Message-ID: <20031202111228.GN14833@ipv6-5.int-evry.fr>
References: <LAW12-F74CV3EJnl1At00012116@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <LAW12-F74CV3EJnl1At00012116@hotmail.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 Sun, Nov 30, 2003 at 02:41:30PM -0800, Alper Yegin wrote:
> >If we want to use IPsec between PaC and EP, the EP must be a router. AS
> >the PAA must be located exactly one IP hop away from the PaC, there must
> >be no EP between PaC and PAA. So it means that EP, PaC and PAA are
> >on the same IP subnet (Am I wrong ?). So, I wonder if it a valid scenario 
> >to have
> >multiple EPs per PAA if we use IPsec.
> 
> If the access routers are used as EP and there are more than one....
> PAA may be co-located with one of the access routers, or may be hosted
> on a dedicated server on the same multi-access link shared by the access
> routers and PaCs.

ok, but I wonder if people think useful to have multiple AR advertising
the same IP subnet. (Do I miss 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 Dec  2 17:13:28 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16801
	for <pana-archive@lists.ietf.org>; Tue, 2 Dec 2003 17:13:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARIlR-0004Tq-Uq; Tue, 02 Dec 2003 17:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARIlH-0004Rn-Lv
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 17:12: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 RAA16597
	for <pana@ietf.org>; Tue, 2 Dec 2003 17:12:37 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARIlF-0003Cp-00
	for pana@ietf.org; Tue, 02 Dec 2003 17:12:49 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARIlE-0003B8-00
	for pana@ietf.org; Tue, 02 Dec 2003 17:12:48 -0500
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol requirements)
To: Yacine.El_Mghazli@alcatel.fr
Cc: alper@docomolabs-usa.com, Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        MORAND Lionel FTRD/DAC/ISS <lionel.morand@francetelecom.com>,
        pana@ietf.org, Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net>
Date: Tue, 2 Dec 2003 14:12:12 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/02/2003 02:12:49 PM
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



Assume that:

- PAA performs SNMP-based polling to detect inactive EPs at every 60
seconds.
   Say the last polling occured at time T.

- Some EP rebooted after T.  The reboot procedure completes before T+60=
.

- At the next polling time, PAA will receives response from the reboote=
d
EP.
  Unless there is some reboot detection mechanism, PAA will not realize=

that
  the EP has been rebooted, and as a result states will not be synchron=
ized
between EP and PAA.

I thought that PAA should get reboot counter from EP and check it in
polling procedure, and
this could be used for both inactive peer detection and reboot detectio=
n
mechanisms.
I've checked RFC3411 and there is snmpEngineBoot MIB that can be used a=
s
the reboot counter.

On the other hand, it is also possible that EP can send SNMP trap to no=
tify
PAA after rebooting.
This could be used for reboot detection mechanism (in passive manner) b=
ut
not for inactive peer
detection mechanism.


Yoshihiro Ohba




   hi Yoshi:

   Yoshihiro.Ohba@tais.com a =E9crit:
   >    > a) Inactive peer detection:
   >    > The protocol used between PAA and EP should be able to detect=

   inactive
   >    > peer within an appropriate time period. This can be achieved =
by
   having
   >    > both the EP and remote PAA constantly verify their connection=
 to
   each
   >    > other via keep-alive messages: a heartbeat in fact.
   >
   >    I'm not sure how much "explicit support" we need for this from =
the
   >    PAA2EP
   >    protocol. There can always be ad-hoc solutions to this. For
   example,
   >    running
   >    some request-reply messages between the PAA and EP can be used =
as a
   >    keep-alive. I can imagine an implementation resorting to such
   techniques
   >    when the protocol does not have a dedicated facility....
   >
   >
   > Yes, some SMNP implementation can support small value (order of
   seconds)
   > for
   > miminum polling inverval.  This would be sufficient for inactive p=
eer
   > detection, but
   > not sufficient for detecting _rebooted_ peer when rebooting can
   complete
   > within
   > SNMP polling interval. Rebooting detection is needed when EP store=

   > PaC information (including accounting information) in volatile mem=
ory.
   >
   > So we might need to define some rebooting counters in SNMP MIB in
   order to
   > detect
   > rebooting peers, or if such a MIB already exists we might just spe=
cify
   the
   > use of
   > the MIB for both inactive/rebooted peer detection.


   I'm not sure to rightly understand what you mean here, please can yo=
u
   elaborate ?

   thanks in advance,
   Yacine



=



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


From exim@www1.ietf.org  Tue Dec  2 17:13:44 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16840
	for <pana-archive@odin.ietf.org>; Tue, 2 Dec 2003 17:13:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARIlp-0004Zv-TV
	for pana-archive@odin.ietf.org; Tue, 02 Dec 2003 17:13:28 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2MDPCG017593
	for pana-archive@odin.ietf.org; Tue, 2 Dec 2003 17:13:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARIlp-0004Zc-LH
	for pana-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 17:13:25 -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 RAA16727
	for <pana-web-archive@ietf.org>; Tue, 2 Dec 2003 17:12:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARIlb-0003Ez-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 17:13:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARIla-0003Ev-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 17:13:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARIlR-0004Tq-Uq; Tue, 02 Dec 2003 17:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARIlH-0004Rn-Lv
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 17:12: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 RAA16597
	for <pana@ietf.org>; Tue, 2 Dec 2003 17:12:37 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARIlF-0003Cp-00
	for pana@ietf.org; Tue, 02 Dec 2003 17:12:49 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARIlE-0003B8-00
	for pana@ietf.org; Tue, 02 Dec 2003 17:12:48 -0500
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol requirements)
To: Yacine.El_Mghazli@alcatel.fr
Cc: alper@docomolabs-usa.com, Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        MORAND Lionel FTRD/DAC/ISS <lionel.morand@francetelecom.com>,
        pana@ietf.org, Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net>
Date: Tue, 2 Dec 2003 14:12:12 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/02/2003 02:12:49 PM
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



Assume that:

- PAA performs SNMP-based polling to detect inactive EPs at every 60
seconds.
   Say the last polling occured at time T.

- Some EP rebooted after T.  The reboot procedure completes before T+60=
.

- At the next polling time, PAA will receives response from the reboote=
d
EP.
  Unless there is some reboot detection mechanism, PAA will not realize=

that
  the EP has been rebooted, and as a result states will not be synchron=
ized
between EP and PAA.

I thought that PAA should get reboot counter from EP and check it in
polling procedure, and
this could be used for both inactive peer detection and reboot detectio=
n
mechanisms.
I've checked RFC3411 and there is snmpEngineBoot MIB that can be used a=
s
the reboot counter.

On the other hand, it is also possible that EP can send SNMP trap to no=
tify
PAA after rebooting.
This could be used for reboot detection mechanism (in passive manner) b=
ut
not for inactive peer
detection mechanism.


Yoshihiro Ohba




   hi Yoshi:

   Yoshihiro.Ohba@tais.com a =E9crit:
   >    > a) Inactive peer detection:
   >    > The protocol used between PAA and EP should be able to detect=

   inactive
   >    > peer within an appropriate time period. This can be achieved =
by
   having
   >    > both the EP and remote PAA constantly verify their connection=
 to
   each
   >    > other via keep-alive messages: a heartbeat in fact.
   >
   >    I'm not sure how much "explicit support" we need for this from =
the
   >    PAA2EP
   >    protocol. There can always be ad-hoc solutions to this. For
   example,
   >    running
   >    some request-reply messages between the PAA and EP can be used =
as a
   >    keep-alive. I can imagine an implementation resorting to such
   techniques
   >    when the protocol does not have a dedicated facility....
   >
   >
   > Yes, some SMNP implementation can support small value (order of
   seconds)
   > for
   > miminum polling inverval.  This would be sufficient for inactive p=
eer
   > detection, but
   > not sufficient for detecting _rebooted_ peer when rebooting can
   complete
   > within
   > SNMP polling interval. Rebooting detection is needed when EP store=

   > PaC information (including accounting information) in volatile mem=
ory.
   >
   > So we might need to define some rebooting counters in SNMP MIB in
   order to
   > detect
   > rebooting peers, or if such a MIB already exists we might just spe=
cify
   the
   > use of
   > the MIB for both inactive/rebooted peer detection.


   I'm not sure to rightly understand what you mean here, please can yo=
u
   elaborate ?

   thanks in advance,
   Yacine



=



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



From pana-admin@ietf.org  Tue Dec  2 17:33:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18797
	for <pana-archive@lists.ietf.org>; Tue, 2 Dec 2003 17:33: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 1ARJ4n-0005fY-3k; Tue, 02 Dec 2003 17:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARJ4Y-0005fE-UZ
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 17:32:47 -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 RAA18709
	for <pana@ietf.org>; Tue, 2 Dec 2003 17:32:32 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARJ4W-000443-00
	for pana@ietf.org; Tue, 02 Dec 2003 17:32:44 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARJ4V-000434-00
	for pana@ietf.org; Tue, 02 Dec 2003 17:32:44 -0500
Subject: Re: Accounting from the EPs (was Re: [Pana] PAA-2-EP protocol requirements)
To: Yacine.El_Mghazli@alcatel.fr
Cc: alper@docomolabs-usa.com, Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        MORAND Lionel FTRD/DAC/ISS <lionel.morand@francetelecom.com>,
        pana@ietf.org, Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OFF2E5BC8F.9D6DD390-ON88256DF0.007AD1D0@tais.net>
Date: Tue, 2 Dec 2003 14:32:12 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/02/2003 02:32:44 PM
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 and al,

   >    > c) Accounting/Feedback from the EPs:
   >    > The PAA must have an efficient way to to get the accounting
   >    information
   >    > of PaC from EP since the PAA may be a client of the AAA backend
   >    > infrastructure.
   >
   >    Getting statistics from the EP makes sense. For example, in the
   case of
   >    SNMP, if we get the counters from the EP this is good enough. The
   AAA
   >    client
   >    sitting on the PAA can turn these into accoutning records.
   >
   > I agree.  Should we eliminate the case where EP itself directly sends
   > accounting records to the accounting server?  I am asking because AAA
   clients for
   > authentication sessions and accounting sessions can be separated
   entities in Diameter, as long as
   > there is a way to
   > associate an accounting session with an authentication session.
   >

   I agree. this is an important issue: is polling sufficient for the AA
   purposes ?


I think polling from PAA is sufficient, except for the case where EP
notifies
the presense of PaC (which can be supported by using SNMP trap or
PANA-PAA-Discover message
sent from EP on behalf of PaC).  So far I have not come up with a counter
case where polling is
insufficient.

Yoshihiro Ohba





   FYI, SNMP provides event-based notifications. I'm not sure if an SNMP
   agents (EPs) can send records periodically to the manager (PAA)...


   Yacine








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


From exim@www1.ietf.org  Tue Dec  2 17:33:43 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18847
	for <pana-archive@odin.ietf.org>; Tue, 2 Dec 2003 17:33:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARJ5D-0005ib-Ie
	for pana-archive@odin.ietf.org; Tue, 02 Dec 2003 17:33:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2MXR6h021975
	for pana-archive@odin.ietf.org; Tue, 2 Dec 2003 17:33:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARJ5D-0005iM-5t
	for pana-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 17:33:27 -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 RAA18749
	for <pana-web-archive@ietf.org>; Tue, 2 Dec 2003 17:33:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARJ5A-00046L-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 17:33:24 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARJ4p-00045I-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 17:33:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARJ4n-0005fY-3k; Tue, 02 Dec 2003 17:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARJ4Y-0005fE-UZ
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 17:32:47 -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 RAA18709
	for <pana@ietf.org>; Tue, 2 Dec 2003 17:32:32 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARJ4W-000443-00
	for pana@ietf.org; Tue, 02 Dec 2003 17:32:44 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARJ4V-000434-00
	for pana@ietf.org; Tue, 02 Dec 2003 17:32:44 -0500
Subject: Re: Accounting from the EPs (was Re: [Pana] PAA-2-EP protocol requirements)
To: Yacine.El_Mghazli@alcatel.fr
Cc: alper@docomolabs-usa.com, Julien Bournelle <Julien.Bournelle@int-evry.fr>,
        MORAND Lionel FTRD/DAC/ISS <lionel.morand@francetelecom.com>,
        pana@ietf.org, Yoshihiro Ohba <yohba@tari.toshiba.com>
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OFF2E5BC8F.9D6DD390-ON88256DF0.007AD1D0@tais.net>
Date: Tue, 2 Dec 2003 14:32:12 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/02/2003 02:32:44 PM
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 and al,

   >    > c) Accounting/Feedback from the EPs:
   >    > The PAA must have an efficient way to to get the accounting
   >    information
   >    > of PaC from EP since the PAA may be a client of the AAA backend
   >    > infrastructure.
   >
   >    Getting statistics from the EP makes sense. For example, in the
   case of
   >    SNMP, if we get the counters from the EP this is good enough. The
   AAA
   >    client
   >    sitting on the PAA can turn these into accoutning records.
   >
   > I agree.  Should we eliminate the case where EP itself directly sends
   > accounting records to the accounting server?  I am asking because AAA
   clients for
   > authentication sessions and accounting sessions can be separated
   entities in Diameter, as long as
   > there is a way to
   > associate an accounting session with an authentication session.
   >

   I agree. this is an important issue: is polling sufficient for the AA
   purposes ?


I think polling from PAA is sufficient, except for the case where EP
notifies
the presense of PaC (which can be supported by using SNMP trap or
PANA-PAA-Discover message
sent from EP on behalf of PaC).  So far I have not come up with a counter
case where polling is
insufficient.

Yoshihiro Ohba





   FYI, SNMP provides event-based notifications. I'm not sure if an SNMP
   agents (EPs) can send records periodically to the manager (PAA)...


   Yacine








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



From pana-admin@ietf.org  Tue Dec  2 19:28:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25606
	for <pana-archive@lists.ietf.org>; Tue, 2 Dec 2003 19:28: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 1ARKs5-0002L1-Mw; Tue, 02 Dec 2003 19:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKr8-0002K1-Qn
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 19:27: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 TAA25565
	for <pana@ietf.org>; Tue, 2 Dec 2003 19:26:48 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr7-0006O6-00
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:01 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr6-0006Nj-01
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:00 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF35987E83.66850C9C-ON88256DF0.0081DC42@tais.net>
Date: Tue, 2 Dec 2003 16:26:45 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/02/2003 04:27:01 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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>


Issue: It is possible for both PaC and PAA to simultaneously initiate EAP
(re)authentication. How can PANA handle the case?

Proposed resolution presented in the IETF58 meeting:
  PAA is always the winner.

Based on the proposed resolution, I have the following text to be included
at the end of section 4.1:

"It is possible that both PAA and PaC initiate the discovery and initial
handshake procedure at the same time, i.e., PAA sends a PANA-Start-Request
message while PaC sends a PANA-PAA-Discover message.
To resolve the race condition, PAA SHOULD silently discard the
PANA-PAA-Discover message received from the PaC after it has sent a
PANA-Start-Request message with creating a state for the PaC."

The issue is described in
http://www.danforsberg.info:8080/pana-issues/issue36

Any comments?

Yoshihiro Ohba



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


From exim@www1.ietf.org  Tue Dec  2 19:28:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25650
	for <pana-archive@odin.ietf.org>; Tue, 2 Dec 2003 19:28: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 1ARKs9-0002N0-4i
	for pana-archive@odin.ietf.org; Tue, 02 Dec 2003 19:28:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB30S5L3009102
	for pana-archive@odin.ietf.org; Tue, 2 Dec 2003 19:28:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKs8-0002MG-RY
	for pana-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 19:28: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 TAA25580
	for <pana-web-archive@ietf.org>; Tue, 2 Dec 2003 19:27:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKs7-0006OV-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 19:28:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKs6-0006OM-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 19:28:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKs5-0002Kl-3v; Tue, 02 Dec 2003 19:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKr8-0002Jr-Ch
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 19:27: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 TAA25559
	for <pana@ietf.org>; Tue, 2 Dec 2003 19:26:47 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr6-0006Ny-00
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:00 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr5-0006Nj-00
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:00 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF0D15AF05.800AB2CE-ON88256DF0.007DA42A@tais.net>
Date: Tue, 2 Dec 2003 16:26:28 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/02/2003 04:27:00 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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>

In the IETF58 PANA meeting, the following resolution was proposed:


-A single Session-Lifetime is bound to a PANA session

-When  NAP and ISP have different authorization lifetimes, the smaller one
relates to the Session-Lifetime

-When EAP re-authentication occurs, both NAP and ISP authentications will
be performed.

I would like to propose the following text to be added at the end of
section 4.9:

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

The issue is described in
http://www.danforsberg.info:8080/pana-issues/issue34.

Comments are appreciated.

Yoshihiro Ohba



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



From pana-admin@ietf.org  Tue Dec  2 20:14:43 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25607
	for <pana-archive@lists.ietf.org>; Tue, 2 Dec 2003 19:28: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 1ARKs5-0002Kt-DK; Tue, 02 Dec 2003 19:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKr8-0002Jw-Mt
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 19:27: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 TAA25562
	for <pana@ietf.org>; Tue, 2 Dec 2003 19:26:48 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr6-0006O1-00
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:00 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr6-0006Nj-00
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:00 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF8C3F6992.BC9B151B-ON88256DF0.007FA863@tais.net>
Date: Tue, 2 Dec 2003 16:26:39 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/02/2003 04:27:01 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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>


Several comments were made on Issue 37 in the IETF58 PANA meeting.
Here is the summary:

- It is possible to propagate the event of AAA message routing error in
PANA message without need to change AAA protocols.

- If we take a look at another EAP transport protocol, IEEE 802.1X does not
carry the AAA message routing error.

- EAP state machines draft does not define an interface to propagate the
AAA message routing error to EAP transport protocols.  As a result, if PANA
supports propagation of the AAA error, PAA will need to have a direct
interface to AAA protocols, in addition to the interface to EAP. This will
complicate implementations.

I prefer not supporting this type of error message in PANA, from
implementation perspective.

The issue is described in
http://www.danforsberg.info:8080/pana-issues/issue37

Any comments?

Yoshihiro Ohba




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


From exim@www1.ietf.org  Tue Dec  2 20:14:43 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25646
	for <pana-archive@odin.ietf.org>; Tue, 2 Dec 2003 19:28: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 1ARKs9-0002My-3i
	for pana-archive@odin.ietf.org; Tue, 02 Dec 2003 19:28:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB30S4j9009074
	for pana-archive@odin.ietf.org; Tue, 2 Dec 2003 19:28:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKs8-0002MF-Qm
	for pana-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 19:28: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 TAA25576
	for <pana-web-archive@ietf.org>; Tue, 2 Dec 2003 19:27:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKs6-0006OS-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 19:28:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKs6-0006OL-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 19:28:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKs5-0002L1-Mw; Tue, 02 Dec 2003 19:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKr8-0002K1-Qn
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 19:27: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 TAA25565
	for <pana@ietf.org>; Tue, 2 Dec 2003 19:26:48 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr7-0006O6-00
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:01 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr6-0006Nj-01
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:00 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF35987E83.66850C9C-ON88256DF0.0081DC42@tais.net>
Date: Tue, 2 Dec 2003 16:26:45 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/02/2003 04:27:01 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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>


Issue: It is possible for both PaC and PAA to simultaneously initiate EAP
(re)authentication. How can PANA handle the case?

Proposed resolution presented in the IETF58 meeting:
  PAA is always the winner.

Based on the proposed resolution, I have the following text to be included
at the end of section 4.1:

"It is possible that both PAA and PaC initiate the discovery and initial
handshake procedure at the same time, i.e., PAA sends a PANA-Start-Request
message while PaC sends a PANA-PAA-Discover message.
To resolve the race condition, PAA SHOULD silently discard the
PANA-PAA-Discover message received from the PaC after it has sent a
PANA-Start-Request message with creating a state for the PaC."

The issue is described in
http://www.danforsberg.info:8080/pana-issues/issue36

Any comments?

Yoshihiro Ohba



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



From exim@www1.ietf.org  Tue Dec  2 20:14:44 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25651
	for <pana-archive@odin.ietf.org>; Tue, 2 Dec 2003 19:28: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 1ARKs9-0002Mz-4Q
	for pana-archive@odin.ietf.org; Tue, 02 Dec 2003 19:28:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB30S59a009088
	for pana-archive@odin.ietf.org; Tue, 2 Dec 2003 19:28:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKs8-0002MH-SR
	for pana-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 19:28: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 TAA25578
	for <pana-web-archive@ietf.org>; Tue, 2 Dec 2003 19:27:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKs6-0006OQ-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 19:28:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKs6-0006OK-00
	for pana-web-archive@ietf.org; Tue, 02 Dec 2003 19:28:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKs5-0002Kt-DK; Tue, 02 Dec 2003 19:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKr8-0002Jw-Mt
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 19:27: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 TAA25562
	for <pana@ietf.org>; Tue, 2 Dec 2003 19:26:48 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr6-0006O1-00
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:00 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr6-0006Nj-00
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:00 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF8C3F6992.BC9B151B-ON88256DF0.007FA863@tais.net>
Date: Tue, 2 Dec 2003 16:26:39 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/02/2003 04:27:01 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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>


Several comments were made on Issue 37 in the IETF58 PANA meeting.
Here is the summary:

- It is possible to propagate the event of AAA message routing error in
PANA message without need to change AAA protocols.

- If we take a look at another EAP transport protocol, IEEE 802.1X does not
carry the AAA message routing error.

- EAP state machines draft does not define an interface to propagate the
AAA message routing error to EAP transport protocols.  As a result, if PANA
supports propagation of the AAA error, PAA will need to have a direct
interface to AAA protocols, in addition to the interface to EAP. This will
complicate implementations.

I prefer not supporting this type of error message in PANA, from
implementation perspective.

The issue is described in
http://www.danforsberg.info:8080/pana-issues/issue37

Any comments?

Yoshihiro Ohba




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



From pana-admin@ietf.org  Tue Dec  2 20:14:44 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25605
	for <pana-archive@lists.ietf.org>; Tue, 2 Dec 2003 19:28: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 1ARKs5-0002Kl-3v; Tue, 02 Dec 2003 19:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKr8-0002Jr-Ch
	for pana@optimus.ietf.org; Tue, 02 Dec 2003 19:27: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 TAA25559
	for <pana@ietf.org>; Tue, 2 Dec 2003 19:26:47 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr6-0006Ny-00
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:00 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKr5-0006Nj-00
	for pana@ietf.org; Tue, 02 Dec 2003 19:27:00 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF0D15AF05.800AB2CE-ON88256DF0.007DA42A@tais.net>
Date: Tue, 2 Dec 2003 16:26:28 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/02/2003 04:27:00 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
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>

In the IETF58 PANA meeting, the following resolution was proposed:


-A single Session-Lifetime is bound to a PANA session

-When  NAP and ISP have different authorization lifetimes, the smaller one
relates to the Session-Lifetime

-When EAP re-authentication occurs, both NAP and ISP authentications will
be performed.

I would like to propose the following text to be added at the end of
section 4.9:

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

The issue is described in
http://www.danforsberg.info:8080/pana-issues/issue34.

Comments are appreciated.

Yoshihiro Ohba



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


From pana-admin@ietf.org  Wed Dec  3 10:34:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20146
	for <pana-archive@lists.ietf.org>; Wed, 3 Dec 2003 10:34: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 1ARZ0v-00033X-5C; Wed, 03 Dec 2003 10:34:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARZ0f-0002zv-36
	for pana@optimus.ietf.org; Wed, 03 Dec 2003 10:33:50 -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 KAA20095
	for <pana@ietf.org>; Wed, 3 Dec 2003 10:33:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARZ0c-00034R-00
	for pana@ietf.org; Wed, 03 Dec 2003 10:33:46 -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 1ARZ0b-00034I-00
	for pana@ietf.org; Wed, 03 Dec 2003 10:33:46 -0500
Date: Wed, 03 Dec 2003 07:34:24 -0800
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol
	requirements)
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yacine.El_Mghazli@alcatel.fr>, Alper Yegin <aeyegin@hotmail.com>
CC: <pana@ietf.org>, <lionel.morand@francetelecom.com>,
        <yohba@tari.toshiba.com>, <Julien.Bournelle@int-evry.fr>
Message-ID: <BBF34280.E278%alper@docomolabs-usa.com>
In-Reply-To: <3FCC67A7.6000604@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

>>> ok. my feeling is you think it's not a requirement at all :-)
>> 
>> 
>> I don't think it is a hard requirement on the PAA2EP protocol.
>> It may be a requirement of the architecture which can be satisfied
>> by other means...
> 
> what is required then ?

Identification of how inactive EPs can be detected when a particular PAA2EP
protocol is used. Again, this may or may not involve an explicit/dedicated
feature of the base protocol.

I don't think we really need to develop new things in here. This problem is
not specific to PANA. It's not like EPs are going to crash more often
because PANA is running in the network ;)


Alper




> is the following sounds correct:
> 
> the PAA-2-EP protocol must enable the PAA to detect inactive EPs. this
> does not mean that the PAA-2-EP protocol must support a heartbeat
> mechanism or any other specific feature.
> if yes, it is a good point, but the only requirement is that the
> PAA-2-EP protocol must not prevent to address this problem by other
> means (see above).
> 
> thanks,
> Yacine
> 
> 
> _______________________________________________
> Pana mailing 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 Dec  3 11:02:04 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21161
	for <pana-archive@odin.ietf.org>; Wed, 3 Dec 2003 11:02:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARZRl-0004ft-1Z
	for pana-archive@odin.ietf.org; Wed, 03 Dec 2003 11:01:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3G1m81017959
	for pana-archive@odin.ietf.org; Wed, 3 Dec 2003 11:01:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARZRk-0004fQ-5M
	for pana-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 11:01:48 -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 LAA21048
	for <pana-web-archive@ietf.org>; Wed, 3 Dec 2003 11:01:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARZRh-0003Rb-00
	for pana-web-archive@ietf.org; Wed, 03 Dec 2003 11:01:45 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARZEa-0003CM-00
	for pana-web-archive@ietf.org; Wed, 03 Dec 2003 10:48:12 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1ARZ4f-0006Ip-Hq
	for pana-web-archive@ietf.org; Wed, 03 Dec 2003 10:37:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARZ0v-00033X-5C; Wed, 03 Dec 2003 10:34:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARZ0f-0002zv-36
	for pana@optimus.ietf.org; Wed, 03 Dec 2003 10:33:50 -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 KAA20095
	for <pana@ietf.org>; Wed, 3 Dec 2003 10:33:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARZ0c-00034R-00
	for pana@ietf.org; Wed, 03 Dec 2003 10:33:46 -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 1ARZ0b-00034I-00
	for pana@ietf.org; Wed, 03 Dec 2003 10:33:46 -0500
Date: Wed, 03 Dec 2003 07:34:24 -0800
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol
	requirements)
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yacine.El_Mghazli@alcatel.fr>, Alper Yegin <aeyegin@hotmail.com>
CC: <pana@ietf.org>, <lionel.morand@francetelecom.com>,
        <yohba@tari.toshiba.com>, <Julien.Bournelle@int-evry.fr>
Message-ID: <BBF34280.E278%alper@docomolabs-usa.com>
In-Reply-To: <3FCC67A7.6000604@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

>>> ok. my feeling is you think it's not a requirement at all :-)
>> 
>> 
>> I don't think it is a hard requirement on the PAA2EP protocol.
>> It may be a requirement of the architecture which can be satisfied
>> by other means...
> 
> what is required then ?

Identification of how inactive EPs can be detected when a particular PAA2EP
protocol is used. Again, this may or may not involve an explicit/dedicated
feature of the base protocol.

I don't think we really need to develop new things in here. This problem is
not specific to PANA. It's not like EPs are going to crash more often
because PANA is running in the network ;)


Alper




> is the following sounds correct:
> 
> the PAA-2-EP protocol must enable the PAA to detect inactive EPs. this
> does not mean that the PAA-2-EP protocol must support a heartbeat
> mechanism or any other specific feature.
> if yes, it is a good point, but the only requirement is that the
> PAA-2-EP protocol must not prevent to address this problem by other
> means (see above).
> 
> thanks,
> Yacine
> 
> 
> _______________________________________________
> Pana mailing 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 Dec  3 11:30:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22261
	for <pana-archive@lists.ietf.org>; Wed, 3 Dec 2003 11:30: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 1ARZt3-0006aZ-F5; Wed, 03 Dec 2003 11:30:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARZsB-0006ZJ-7z
	for pana@optimus.ietf.org; Wed, 03 Dec 2003 11:29: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 LAA22154
	for <pana@ietf.org>; Wed, 3 Dec 2003 11:28:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARZsA-0003rj-00
	for pana@ietf.org; Wed, 03 Dec 2003 11:29:06 -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 1ARZs9-0003rg-00
	for pana@ietf.org; Wed, 03 Dec 2003 11:29:05 -0500
Date: Wed, 03 Dec 2003 08:30:06 -0800
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol
	requirements)
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yacine.El_Mghazli@alcatel.fr>, Alper Yegin <aeyegin@hotmail.com>
CC: <pana@ietf.org>, <lionel.morand@francetelecom.com>,
        <yohba@tari.toshiba.com>, <Julien.Bournelle@int-evry.fr>
Message-ID: <BBF34F8E.E283%alper@docomolabs-usa.com>
In-Reply-To: <3FCC74FB.7010400@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

> my understanding is the following:
> 
> PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
> For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
> configuring the concerned EPs. depending on the topology, there could be
> more than one.
> 
> does it look correct ?

Yes. This is what I'm thinking.

> 
>>> * inter-PAAs communication ?
>> 
>> 
>> Why do we need this for?
> 
> for exemple: context transfer between PAAs for mobility handling (in
> order to avoid re-authentication, which would reduce the handover perf).
> this is strongly dependent of the relation between PAA and EPs discussed
> above.

I cannot see the relation. I think changing PAAs due to mobility and
enabling fast reauthentication via context transfers is orthogonal to the
PAA2EP protocol.

Alper
 



> 
>> Alper
> 
> Yacine
> 
>>> etc...
>>> 
>>> comments on these "issues" are warmly welcome !
>>> 
>>> 
>>> 
>>>>> c) Accounting/Feedback from the EPs:
>>>>> The PAA must have an efficient way to to get the accounting
> information
>>>>> of PaC from EP since the PAA may be a client of the AAA backend
>>>>> infrastructure.
>>>> 
>>>> 
>>>> Getting statistics from the EP makes sense. For example, in the
> case of
>>>> SNMP, if we get the counters from the EP this is good enough. The
>>> AAA client
>>>> sitting on the PAA can turn these into accoutning records.
>>> 
>>> should the PAA poll the EPs to get these counters when needed (the
>>> SNMP way...) or the EPs are supposed to send them periodically ?
>>> 
>>> anyway, this should be somehow a requirement.
>>> 
>>> 
>>>> Alper
>>>> 
>>> 
>>> thanks,
>>> yacine
>>> 
>>>>> d) ????
>>>>> 
>>>>> 
>>>>> thanks,
>>>>> Yacine El Mghazli
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Pana mailing 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
>> 
>> 
>> _________________________________________________________________
>> Set yourself up for fun at home!  Get tips on home entertainment
>> equipment, video game reviews, and more here.
>> http://special.msn.com/home/homeent.armx
>> 
>> 
> 
> 
> 
> 


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


From exim@www1.ietf.org  Wed Dec  3 11:30:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22280
	for <pana-archive@odin.ietf.org>; Wed, 3 Dec 2003 11:30: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 1ARZt8-0006cK-J1
	for pana-archive@odin.ietf.org; Wed, 03 Dec 2003 11:30:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3GU69N025435
	for pana-archive@odin.ietf.org; Wed, 3 Dec 2003 11:30:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARZt8-0006cA-Af
	for pana-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 11:30: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 LAA22221
	for <pana-web-archive@ietf.org>; Wed, 3 Dec 2003 11:29:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARZt7-0003uD-00
	for pana-web-archive@ietf.org; Wed, 03 Dec 2003 11:30:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARZt6-0003uA-00
	for pana-web-archive@ietf.org; Wed, 03 Dec 2003 11:30:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARZt3-0006aZ-F5; Wed, 03 Dec 2003 11:30:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARZsB-0006ZJ-7z
	for pana@optimus.ietf.org; Wed, 03 Dec 2003 11:29: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 LAA22154
	for <pana@ietf.org>; Wed, 3 Dec 2003 11:28:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARZsA-0003rj-00
	for pana@ietf.org; Wed, 03 Dec 2003 11:29:06 -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 1ARZs9-0003rg-00
	for pana@ietf.org; Wed, 03 Dec 2003 11:29:05 -0500
Date: Wed, 03 Dec 2003 08:30:06 -0800
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol
	requirements)
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yacine.El_Mghazli@alcatel.fr>, Alper Yegin <aeyegin@hotmail.com>
CC: <pana@ietf.org>, <lionel.morand@francetelecom.com>,
        <yohba@tari.toshiba.com>, <Julien.Bournelle@int-evry.fr>
Message-ID: <BBF34F8E.E283%alper@docomolabs-usa.com>
In-Reply-To: <3FCC74FB.7010400@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

> my understanding is the following:
> 
> PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
> For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
> configuring the concerned EPs. depending on the topology, there could be
> more than one.
> 
> does it look correct ?

Yes. This is what I'm thinking.

> 
>>> * inter-PAAs communication ?
>> 
>> 
>> Why do we need this for?
> 
> for exemple: context transfer between PAAs for mobility handling (in
> order to avoid re-authentication, which would reduce the handover perf).
> this is strongly dependent of the relation between PAA and EPs discussed
> above.

I cannot see the relation. I think changing PAAs due to mobility and
enabling fast reauthentication via context transfers is orthogonal to the
PAA2EP protocol.

Alper
 



> 
>> Alper
> 
> Yacine
> 
>>> etc...
>>> 
>>> comments on these "issues" are warmly welcome !
>>> 
>>> 
>>> 
>>>>> c) Accounting/Feedback from the EPs:
>>>>> The PAA must have an efficient way to to get the accounting
> information
>>>>> of PaC from EP since the PAA may be a client of the AAA backend
>>>>> infrastructure.
>>>> 
>>>> 
>>>> Getting statistics from the EP makes sense. For example, in the
> case of
>>>> SNMP, if we get the counters from the EP this is good enough. The
>>> AAA client
>>>> sitting on the PAA can turn these into accoutning records.
>>> 
>>> should the PAA poll the EPs to get these counters when needed (the
>>> SNMP way...) or the EPs are supposed to send them periodically ?
>>> 
>>> anyway, this should be somehow a requirement.
>>> 
>>> 
>>>> Alper
>>>> 
>>> 
>>> thanks,
>>> yacine
>>> 
>>>>> d) ????
>>>>> 
>>>>> 
>>>>> thanks,
>>>>> Yacine El Mghazli
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Pana mailing 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
>> 
>> 
>> _________________________________________________________________
>> Set yourself up for fun at home!  Get tips on home entertainment
>> equipment, video game reviews, and more here.
>> http://special.msn.com/home/homeent.armx
>> 
>> 
> 
> 
> 
> 


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



From pana-admin@ietf.org  Wed Dec  3 20:53:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20834
	for <pana-archive@lists.ietf.org>; Wed, 3 Dec 2003 20:53: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 1ARifs-0006hb-By; Wed, 03 Dec 2003 20:53:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARifr-0006hH-CS
	for pana@optimus.ietf.org; Wed, 03 Dec 2003 20:52:59 -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 UAA20775
	for <pana@ietf.org>; Wed, 3 Dec 2003 20:52:43 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifo-0006NE-00
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:56 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifo-0006M3-00
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:56 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF71E02608.6AC22A11-ON88256DF2.000940E8@tais.net>
Date: Wed, 3 Dec 2003 17:52:48 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/03/2003 05:52:57 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Pana] Issue2: Downgrading protection
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>


Issue2. Downgrading protection. This is an EAP problem. Use EAP-GSSAPI to
negotiate EAP in secure way.

The consensus in the IETF58 meeting is that this is an EAP issue
and not a PANA problem.  The PANA draft already has the following
text in the Security Considerations section. However, if this is not a PANA
problem, do we still need the text in PANA draft?


"  e) Preventing downgrading attacks
   EAP supports a number of different EAP methods for authentication and
   therefore it might be required to agree on a specific mechanism.  An
   unprotected negotiation mechanism is supported in EAP and a secure
   negotiation procedure for the GSS-API methods. The support of the
   GSS-API as an EAP method is described in [I-D.aboba-pppext-eapgss]. A
   protected negotiation is supported by the GSS-API with RFC 2478
   [RFC2478]. If desired, such a protection can also be offered by PANA
   by repeating the list of supported EAP methods protected with the
   PANA SA. This type of protection is similar to the protected
   negotiation described in [RFC3329].
   This issue requires further investigation especially since the EAP
   protocol is executed between different endpoints than the PANA
   protocol."

The issue can be found at:
http://www.danforsberg.info:8080/pana-issues/issue2
Yoshihiro Ohba



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


From exim@www1.ietf.org  Wed Dec  3 20:53:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20868
	for <pana-archive@odin.ietf.org>; Wed, 3 Dec 2003 20:53: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 1ARig2-0006j5-8I
	for pana-archive@odin.ietf.org; Wed, 03 Dec 2003 20:53:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB41rAve025849
	for pana-archive@odin.ietf.org; Wed, 3 Dec 2003 20:53:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARig0-0006iX-MN
	for pana-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 20:53:08 -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 UAA20789
	for <pana-web-archive@ietf.org>; Wed, 3 Dec 2003 20:52:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifx-0006Na-00
	for pana-web-archive@ietf.org; Wed, 03 Dec 2003 20:53:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifx-0006NU-00
	for pana-web-archive@ietf.org; Wed, 03 Dec 2003 20:53:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARifs-0006hT-2Y; Wed, 03 Dec 2003 20:53:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARifq-0006hC-L1
	for pana@optimus.ietf.org; Wed, 03 Dec 2003 20:52: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 UAA20770
	for <pana@ietf.org>; Wed, 3 Dec 2003 20:52:42 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifn-0006N6-00
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:55 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifn-0006M3-00
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:55 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OFD082057F.F9E5BD70-ON88256DF2.000437DF@tais.net>
Date: Wed, 3 Dec 2003 17:52:21 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/03/2003 05:52:56 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Pana] Issue16: Multihoming support
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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 issue is related to PaC that has multiple interfaces on the same IP
link.

In the IETF58 meeting, a resolution was proposed for multihomed host to use
separate PANA session for each interface.  Here is the proposed text for
the PANA draft:

In Section 2, Change:


"  PANA Session:
      PANA session is defined as the exchange of messages between the
      PANA Client (PaC) and the PANA Authentication Agent (PAA) to
      authenticate a user (PaC) for network access. If the
      authentication is unsuccessful, the session is terminated. The
      session is considered as active until there is a disconnect
      indication by the PaC or the PAA terminates it."

To:

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

Issue16 can be found at:
http://www.danforsberg.info:8080/pana-issues/issue16

Yoshihiro Ohba



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



From exim@www1.ietf.org  Wed Dec  3 20:53:25 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20883
	for <pana-archive@odin.ietf.org>; Wed, 3 Dec 2003 20:53: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 1ARig1-0006in-1X
	for pana-archive@odin.ietf.org; Wed, 03 Dec 2003 20:53:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB41r9hV025832
	for pana-archive@odin.ietf.org; Wed, 3 Dec 2003 20:53:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARig0-0006iY-SE
	for pana-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 20:53:08 -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 UAA20792
	for <pana-web-archive@ietf.org>; Wed, 3 Dec 2003 20:52:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARify-0006Nd-00
	for pana-web-archive@ietf.org; Wed, 03 Dec 2003 20:53:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifx-0006NV-00
	for pana-web-archive@ietf.org; Wed, 03 Dec 2003 20:53:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARifs-0006hb-By; Wed, 03 Dec 2003 20:53:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARifr-0006hH-CS
	for pana@optimus.ietf.org; Wed, 03 Dec 2003 20:52:59 -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 UAA20775
	for <pana@ietf.org>; Wed, 3 Dec 2003 20:52:43 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifo-0006NE-00
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:56 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifo-0006M3-00
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:56 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF71E02608.6AC22A11-ON88256DF2.000940E8@tais.net>
Date: Wed, 3 Dec 2003 17:52:48 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/03/2003 05:52:57 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Pana] Issue2: Downgrading protection
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>


Issue2. Downgrading protection. This is an EAP problem. Use EAP-GSSAPI to
negotiate EAP in secure way.

The consensus in the IETF58 meeting is that this is an EAP issue
and not a PANA problem.  The PANA draft already has the following
text in the Security Considerations section. However, if this is not a PANA
problem, do we still need the text in PANA draft?


"  e) Preventing downgrading attacks
   EAP supports a number of different EAP methods for authentication and
   therefore it might be required to agree on a specific mechanism.  An
   unprotected negotiation mechanism is supported in EAP and a secure
   negotiation procedure for the GSS-API methods. The support of the
   GSS-API as an EAP method is described in [I-D.aboba-pppext-eapgss]. A
   protected negotiation is supported by the GSS-API with RFC 2478
   [RFC2478]. If desired, such a protection can also be offered by PANA
   by repeating the list of supported EAP methods protected with the
   PANA SA. This type of protection is similar to the protected
   negotiation described in [RFC3329].
   This issue requires further investigation especially since the EAP
   protocol is executed between different endpoints than the PANA
   protocol."

The issue can be found at:
http://www.danforsberg.info:8080/pana-issues/issue2
Yoshihiro Ohba



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



From pana-admin@ietf.org  Wed Dec  3 20:54:15 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20974
	for <pana-archive@lists.ietf.org>; Wed, 3 Dec 2003 20:54:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARigq-0006oc-P9; Wed, 03 Dec 2003 20:54:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARifv-0006hx-QJ
	for pana@optimus.ietf.org; Wed, 03 Dec 2003 20:53: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 UAA20773
	for <pana@ietf.org>; Wed, 3 Dec 2003 20:52:42 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifo-0006NA-00
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:56 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifn-0006M3-01
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:55 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OFCBB1893C.B950D13A-ON88256DF2.0007EA39@tais.net>
Date: Wed, 3 Dec 2003 17:52:33 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/03/2003 05:52:56 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Pana] Issue12: Supporting network access authentication for ad-hoc networks
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>


Issue12: authentication in ad-hoc network scenario. Should PANA support
ad-hoc network scenario where there can be multiple untrusted IP nodes in
between PaC and PAA.

If my understanding is correct, the consensus in the IETF58 meeting was
that the scenario is out of scope of PANA WG, and thus we don't have
consider the scenario.
This issue will be rejected.

Any objection?

The issue can be found at:
http://www.danforsberg.info:8080/pana-issues/issue12

Yoshihiro Ohba



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


From exim@www1.ietf.org  Wed Dec  3 20:54:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20989
	for <pana-archive@odin.ietf.org>; Wed, 3 Dec 2003 20:54:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARigv-0006rm-U8
	for pana-archive@odin.ietf.org; Wed, 03 Dec 2003 20:54:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB41s5Rb026388
	for pana-archive@odin.ietf.org; Wed, 3 Dec 2003 20:54:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARigv-0006rX-PB
	for pana-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 20:54: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 UAA20938
	for <pana-web-archive@ietf.org>; Wed, 3 Dec 2003 20:53:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARigt-0006Q3-00
	for pana-web-archive@ietf.org; Wed, 03 Dec 2003 20:54:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARigs-0006Pp-00
	for pana-web-archive@ietf.org; Wed, 03 Dec 2003 20:54:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARigq-0006oc-P9; Wed, 03 Dec 2003 20:54:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARifv-0006hx-QJ
	for pana@optimus.ietf.org; Wed, 03 Dec 2003 20:53: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 UAA20773
	for <pana@ietf.org>; Wed, 3 Dec 2003 20:52:42 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifo-0006NA-00
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:56 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifn-0006M3-01
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:55 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OFCBB1893C.B950D13A-ON88256DF2.0007EA39@tais.net>
Date: Wed, 3 Dec 2003 17:52:33 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/03/2003 05:52:56 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Pana] Issue12: Supporting network access authentication for ad-hoc networks
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>


Issue12: authentication in ad-hoc network scenario. Should PANA support
ad-hoc network scenario where there can be multiple untrusted IP nodes in
between PaC and PAA.

If my understanding is correct, the consensus in the IETF58 meeting was
that the scenario is out of scope of PANA WG, and thus we don't have
consider the scenario.
This issue will be rejected.

Any objection?

The issue can be found at:
http://www.danforsberg.info:8080/pana-issues/issue12

Yoshihiro Ohba



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



From pana-admin@ietf.org  Wed Dec  3 21:39:51 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20833
	for <pana-archive@lists.ietf.org>; Wed, 3 Dec 2003 20:53: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 1ARifs-0006hT-2Y; Wed, 03 Dec 2003 20:53:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARifq-0006hC-L1
	for pana@optimus.ietf.org; Wed, 03 Dec 2003 20:52: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 UAA20770
	for <pana@ietf.org>; Wed, 3 Dec 2003 20:52:42 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifn-0006N6-00
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:55 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARifn-0006M3-00
	for pana@ietf.org; Wed, 03 Dec 2003 20:52:55 -0500
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OFD082057F.F9E5BD70-ON88256DF2.000437DF@tais.net>
Date: Wed, 3 Dec 2003 17:52:21 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/03/2003 05:52:56 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Pana] Issue16: Multihoming support
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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 issue is related to PaC that has multiple interfaces on the same IP
link.

In the IETF58 meeting, a resolution was proposed for multihomed host to use
separate PANA session for each interface.  Here is the proposed text for
the PANA draft:

In Section 2, Change:


"  PANA Session:
      PANA session is defined as the exchange of messages between the
      PANA Client (PaC) and the PANA Authentication Agent (PAA) to
      authenticate a user (PaC) for network access. If the
      authentication is unsuccessful, the session is terminated. The
      session is considered as active until there is a disconnect
      indication by the PaC or the PAA terminates it."

To:

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

Issue16 can be found at:
http://www.danforsberg.info:8080/pana-issues/issue16

Yoshihiro Ohba



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


From pana-admin@ietf.org  Thu Dec  4 11:28:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03466
	for <pana-archive@lists.ietf.org>; Thu, 4 Dec 2003 11:28:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARwKe-0000JT-Pg; Thu, 04 Dec 2003 11:28:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARwKK-0000Iw-KX
	for pana@optimus.ietf.org; Thu, 04 Dec 2003 11:27:40 -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 LAA03411
	for <pana@ietf.org>; Thu, 4 Dec 2003 11:27:22 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARwKG-0004Hb-00
	for pana@ietf.org; Thu, 04 Dec 2003 11:27:36 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARwKG-0004Gc-00
	for pana@ietf.org; Thu, 04 Dec 2003 11:27:36 -0500
Subject: Re: Accounting from the EPs (was Re: [Pana] PAA-2-EP protocol requirements)
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF3AC7668F.842A88D0-ON88256DF2.005A0FD2@tais.net>
Date: Thu, 4 Dec 2003 08:27:00 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/04/2003 08:27:36 AM
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>

FYI..  There is some interesting case where polling from PAA to EP might be
inefficient.

Yoshihiro Ohba


----- Forwarded by Yoshihiro Ohba/CSE/IRV/TOSHIBA-TAIS on 2003/12/04 08:23
-----
                                                                                   
                      Yoshihiro Ohba                                               
                                               To:      jari.arkko@piuha.net       
                      2003/12/03 09:23         cc:      alper@docomolabs-usa.com,  
                                               jari.arkko@piuha.net, John Loughney 
                                               <john.loughney@nokia.com>,          
                                               Yoshihiro Ohba                      
                                               <yohba@tari.toshiba.com>            
                                               Subject: Re: Accounting from the    
                                               EPs (was Re: [Pana] PAA-2-EP        
                                               protocol requirements)(Document     
                                               link: Yoshihiro Ohba)               
                                                                                   







   Yoshihiro.Ohba@tais.com wrote:
   >
   > In the former case, polling EP to obtain accounting records on a
   particular
   > PaC can be triggered when disconnected requests are received from the
   home
   > AAA.

   For the disconnect request, I was asking more about the existence
   of a message in PANA that would kill the session from an EP. I suppose
   such a message must exist already.

   > In the latter case, there would be a performance issue when there are
   a
   > large number of clients that need realtime accounting. However, I
   think the
   > performance issue equally holds in non-polling scheme in which EPs
   > periodically send accounting records to PAA.
   >
   > Or I may be misunderstanding the definition of polling.

   No, you got it right. RFC 2975 Section 2.3.5 summarizes btw
   the accounting data collection model pros and cons.

   But I was primarily thinking about how to implement something
   like the Granted-Service-Unit AVP from draft-ietf-aaa-diameter-cc
   if the EPs are only polled.

   --Jari


The authorization model based on Granted-Service-Unit AVP is interesting.
Especially when the maximum number of octets is used as an authorization
parameter, I agree that some notification from EP to PAA would be needed to
indicate that the PaC has spent the maximum number of input/output/total
octets and thus the EP has forcefully shutdown the data path for the PaC.
Using polling model for this type of authorization model might be
inefficient.

Yoshihiro Ohba






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


From exim@www1.ietf.org  Thu Dec  4 11:28:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03481
	for <pana-archive@odin.ietf.org>; Thu, 4 Dec 2003 11:28: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 1ARwKk-0000KA-Dc
	for pana-archive@odin.ietf.org; Thu, 04 Dec 2003 11:28:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB4GS6Yc001240
	for pana-archive@odin.ietf.org; Thu, 4 Dec 2003 11:28:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARwKk-0000Jv-9q
	for pana-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 11:28: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 LAA03427
	for <pana-web-archive@ietf.org>; Thu, 4 Dec 2003 11:27:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARwKh-0004Hz-00
	for pana-web-archive@ietf.org; Thu, 04 Dec 2003 11:28:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARwKh-0004Hw-00
	for pana-web-archive@ietf.org; Thu, 04 Dec 2003 11:28:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARwKe-0000JT-Pg; Thu, 04 Dec 2003 11:28:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARwKK-0000Iw-KX
	for pana@optimus.ietf.org; Thu, 04 Dec 2003 11:27:40 -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 LAA03411
	for <pana@ietf.org>; Thu, 4 Dec 2003 11:27:22 -0500 (EST)
From: Yoshihiro.Ohba@tais.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARwKG-0004Hb-00
	for pana@ietf.org; Thu, 04 Dec 2003 11:27:36 -0500
Received: from zmsvr04.tais.net ([12.106.80.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARwKG-0004Gc-00
	for pana@ietf.org; Thu, 04 Dec 2003 11:27:36 -0500
Subject: Re: Accounting from the EPs (was Re: [Pana] PAA-2-EP protocol requirements)
To: pana@ietf.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF3AC7668F.842A88D0-ON88256DF2.005A0FD2@tais.net>
Date: Thu, 4 Dec 2003 08:27:00 -0800
X-MIMETrack: Serialize by Router on zmsvr04/tais_external(Release 5.0.9a |January 7, 2002) at
 12/04/2003 08:27:36 AM
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>

FYI..  There is some interesting case where polling from PAA to EP might be
inefficient.

Yoshihiro Ohba


----- Forwarded by Yoshihiro Ohba/CSE/IRV/TOSHIBA-TAIS on 2003/12/04 08:23
-----
                                                                                   
                      Yoshihiro Ohba                                               
                                               To:      jari.arkko@piuha.net       
                      2003/12/03 09:23         cc:      alper@docomolabs-usa.com,  
                                               jari.arkko@piuha.net, John Loughney 
                                               <john.loughney@nokia.com>,          
                                               Yoshihiro Ohba                      
                                               <yohba@tari.toshiba.com>            
                                               Subject: Re: Accounting from the    
                                               EPs (was Re: [Pana] PAA-2-EP        
                                               protocol requirements)(Document     
                                               link: Yoshihiro Ohba)               
                                                                                   







   Yoshihiro.Ohba@tais.com wrote:
   >
   > In the former case, polling EP to obtain accounting records on a
   particular
   > PaC can be triggered when disconnected requests are received from the
   home
   > AAA.

   For the disconnect request, I was asking more about the existence
   of a message in PANA that would kill the session from an EP. I suppose
   such a message must exist already.

   > In the latter case, there would be a performance issue when there are
   a
   > large number of clients that need realtime accounting. However, I
   think the
   > performance issue equally holds in non-polling scheme in which EPs
   > periodically send accounting records to PAA.
   >
   > Or I may be misunderstanding the definition of polling.

   No, you got it right. RFC 2975 Section 2.3.5 summarizes btw
   the accounting data collection model pros and cons.

   But I was primarily thinking about how to implement something
   like the Granted-Service-Unit AVP from draft-ietf-aaa-diameter-cc
   if the EPs are only polled.

   --Jari


The authorization model based on Granted-Service-Unit AVP is interesting.
Especially when the maximum number of octets is used as an authorization
parameter, I agree that some notification from EP to PAA would be needed to
indicate that the PaC has spent the maximum number of input/output/total
octets and thus the EP has forcefully shutdown the data path for the PaC.
Using polling model for this type of authorization model might be
inefficient.

Yoshihiro Ohba






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



From pana-admin@ietf.org  Thu Dec  4 13:51:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08389
	for <pana-archive@lists.ietf.org>; Thu, 4 Dec 2003 13:51:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyZ4-000282-CS; Thu, 04 Dec 2003 13:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyJj-0000xx-Q4
	for pana@optimus.ietf.org; Thu, 04 Dec 2003 13:35: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 NAA06930
	for <pana@ietf.org>; Thu, 4 Dec 2003 13:14:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARxzm-0005nG-00
	for pana@ietf.org; Thu, 04 Dec 2003 13:14:34 -0500
Received: from na5.alcatel.fr ([194.133.58.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARxzl-0005ms-00
	for pana@ietf.org; Thu, 04 Dec 2003 13:14:33 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB4IE07F001456;
	Thu, 4 Dec 2003 19:14:00 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120419135880:6829 ;
          Thu, 4 Dec 2003 19:13:58 +0100 
Message-ID: <3FCF7967.4080807@alcatel.fr>
Date: Thu, 04 Dec 2003 19:13:59 +0100
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Yoshihiro.Ohba@tais.com
CC: pana@ietf.org
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol requirements)
References: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net>
In-Reply-To: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/04/2003 19:13:58,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/04/2003 19:14:00
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Alcanet-MTA-scanned-and-authorized: yes
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

thanks yoshi, I much better understand the problem now. please see below=20
some comments inline:

Yoshihiro.Ohba@tais.com wrote:

>=20
> Assume that:
>=20
> - PAA performs SNMP-based polling to detect inactive EPs at every 60
> seconds.
>    Say the last polling occured at time T.
>=20
> - Some EP rebooted after T.  The reboot procedure completes before T+60.
>=20
> - At the next polling time, PAA will receives response from the rebooted
> EP.
>   Unless there is some reboot detection mechanism, PAA will not realize
> that
>   the EP has been rebooted,=20

since the EP is empty after rebooting, the first packet coming from any=20
of the PaC will be considered as unauthorized and trigger a "New PaC=20
notification" (PANA auth request message, SNMP trap, or whatever...) to=20
the PAA. hence, it is sufficient fot the PAA to be rapidly aware of the=20
problem.

> and as a result states will not be synchronized
> between EP and PAA.

in a recent discussion on the stateful/stateless appoach, we (mostly=20
alper) agreed that the PAA does not maintain any EP state --> no=20
synchronisation anyway.

I would say: once the PAA is aware the EP has rebooted, it should send=20
again the set of rules to this EP, based on the PaC states, which are=20
maintained in the PAA.

thanks,
yacine



> I thought that PAA should get reboot counter from EP and check it in
> polling procedure, and
> this could be used for both inactive peer detection and reboot detection
> mechanisms.
> I've checked RFC3411 and there is snmpEngineBoot MIB that can be used as
> the reboot counter.
>=20
> On the other hand, it is also possible that EP can send SNMP trap to noti=
fy
> PAA after rebooting.
> This could be used for reboot detection mechanism (in passive manner) but
> not for inactive peer
> detection mechanism.
>=20
>=20
> Yoshihiro Ohba
>=20
>=20
>=20
>=20
>    hi Yoshi:
>=20
>    Yoshihiro.Ohba@tais.com a =E9crit:
>    >    > a) Inactive peer detection:
>    >    > The protocol used between PAA and EP should be able to detect
>    inactive
>    >    > peer within an appropriate time period. This can be achieved by
>    having
>    >    > both the EP and remote PAA constantly verify their connection to
>    each
>    >    > other via keep-alive messages: a heartbeat in fact.
>    >
>    >    I'm not sure how much "explicit support" we need for this from the
>    >    PAA2EP
>    >    protocol. There can always be ad-hoc solutions to this. For
>    example,
>    >    running
>    >    some request-reply messages between the PAA and EP can be used as=
 a
>    >    keep-alive. I can imagine an implementation resorting to such
>    techniques
>    >    when the protocol does not have a dedicated facility....
>    >
>    >
>    > Yes, some SMNP implementation can support small value (order of
>    seconds)
>    > for
>    > miminum polling inverval.  This would be sufficient for inactive peer
>    > detection, but
>    > not sufficient for detecting =5Frebooted=5F peer when rebooting can
>    complete
>    > within
>    > SNMP polling interval. Rebooting detection is needed when EP store
>    > PaC information (including accounting information) in volatile memor=
y.
>    >
>    > So we might need to define some rebooting counters in SNMP MIB in
>    order to
>    > detect
>    > rebooting peers, or if such a MIB already exists we might just speci=
fy
>    the
>    > use of
>    > the MIB for both inactive/rebooted peer detection.
>=20
>=20
>    I'm not sure to rightly understand what you mean here, please can you
>    elaborate ?
>=20
>    thanks in advance,
>    Yacine
>=20
>=20
>=20
>=20
>=20
>=20



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


From exim@www1.ietf.org  Thu Dec  4 13:51:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08404
	for <pana-archive@odin.ietf.org>; Thu, 4 Dec 2003 13:51: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 1ARyZ8-0002Ab-RK
	for pana-archive@odin.ietf.org; Thu, 04 Dec 2003 13:51:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB4Ip6Fd008335
	for pana-archive@odin.ietf.org; Thu, 4 Dec 2003 13:51:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyZ8-0002AM-Mo
	for pana-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 13:51: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 NAA08353
	for <pana-web-archive@ietf.org>; Thu, 4 Dec 2003 13:50:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyZ6-0006Op-00
	for pana-web-archive@ietf.org; Thu, 04 Dec 2003 13:51:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyZ5-0006Ol-00
	for pana-web-archive@ietf.org; Thu, 04 Dec 2003 13: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 1ARyZ4-000282-CS; Thu, 04 Dec 2003 13:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyJj-0000xx-Q4
	for pana@optimus.ietf.org; Thu, 04 Dec 2003 13:35: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 NAA06930
	for <pana@ietf.org>; Thu, 4 Dec 2003 13:14:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARxzm-0005nG-00
	for pana@ietf.org; Thu, 04 Dec 2003 13:14:34 -0500
Received: from na5.alcatel.fr ([194.133.58.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARxzl-0005ms-00
	for pana@ietf.org; Thu, 04 Dec 2003 13:14:33 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB4IE07F001456;
	Thu, 4 Dec 2003 19:14:00 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120419135880:6829 ;
          Thu, 4 Dec 2003 19:13:58 +0100 
Message-ID: <3FCF7967.4080807@alcatel.fr>
Date: Thu, 04 Dec 2003 19:13:59 +0100
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Yoshihiro.Ohba@tais.com
CC: pana@ietf.org
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol requirements)
References: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net>
In-Reply-To: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/04/2003 19:13:58,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/04/2003 19:14:00
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Alcanet-MTA-scanned-and-authorized: yes
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

thanks yoshi, I much better understand the problem now. please see below=20
some comments inline:

Yoshihiro.Ohba@tais.com wrote:

>=20
> Assume that:
>=20
> - PAA performs SNMP-based polling to detect inactive EPs at every 60
> seconds.
>    Say the last polling occured at time T.
>=20
> - Some EP rebooted after T.  The reboot procedure completes before T+60.
>=20
> - At the next polling time, PAA will receives response from the rebooted
> EP.
>   Unless there is some reboot detection mechanism, PAA will not realize
> that
>   the EP has been rebooted,=20

since the EP is empty after rebooting, the first packet coming from any=20
of the PaC will be considered as unauthorized and trigger a "New PaC=20
notification" (PANA auth request message, SNMP trap, or whatever...) to=20
the PAA. hence, it is sufficient fot the PAA to be rapidly aware of the=20
problem.

> and as a result states will not be synchronized
> between EP and PAA.

in a recent discussion on the stateful/stateless appoach, we (mostly=20
alper) agreed that the PAA does not maintain any EP state --> no=20
synchronisation anyway.

I would say: once the PAA is aware the EP has rebooted, it should send=20
again the set of rules to this EP, based on the PaC states, which are=20
maintained in the PAA.

thanks,
yacine



> I thought that PAA should get reboot counter from EP and check it in
> polling procedure, and
> this could be used for both inactive peer detection and reboot detection
> mechanisms.
> I've checked RFC3411 and there is snmpEngineBoot MIB that can be used as
> the reboot counter.
>=20
> On the other hand, it is also possible that EP can send SNMP trap to noti=
fy
> PAA after rebooting.
> This could be used for reboot detection mechanism (in passive manner) but
> not for inactive peer
> detection mechanism.
>=20
>=20
> Yoshihiro Ohba
>=20
>=20
>=20
>=20
>    hi Yoshi:
>=20
>    Yoshihiro.Ohba@tais.com a =E9crit:
>    >    > a) Inactive peer detection:
>    >    > The protocol used between PAA and EP should be able to detect
>    inactive
>    >    > peer within an appropriate time period. This can be achieved by
>    having
>    >    > both the EP and remote PAA constantly verify their connection to
>    each
>    >    > other via keep-alive messages: a heartbeat in fact.
>    >
>    >    I'm not sure how much "explicit support" we need for this from the
>    >    PAA2EP
>    >    protocol. There can always be ad-hoc solutions to this. For
>    example,
>    >    running
>    >    some request-reply messages between the PAA and EP can be used as=
 a
>    >    keep-alive. I can imagine an implementation resorting to such
>    techniques
>    >    when the protocol does not have a dedicated facility....
>    >
>    >
>    > Yes, some SMNP implementation can support small value (order of
>    seconds)
>    > for
>    > miminum polling inverval.  This would be sufficient for inactive peer
>    > detection, but
>    > not sufficient for detecting =5Frebooted=5F peer when rebooting can
>    complete
>    > within
>    > SNMP polling interval. Rebooting detection is needed when EP store
>    > PaC information (including accounting information) in volatile memor=
y.
>    >
>    > So we might need to define some rebooting counters in SNMP MIB in
>    order to
>    > detect
>    > rebooting peers, or if such a MIB already exists we might just speci=
fy
>    the
>    > use of
>    > the MIB for both inactive/rebooted peer detection.
>=20
>=20
>    I'm not sure to rightly understand what you mean here, please can you
>    elaborate ?
>=20
>    thanks in advance,
>    Yacine
>=20
>=20
>=20
>=20
>=20
>=20



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



From pana-admin@ietf.org  Thu Dec  4 14:07:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08938
	for <pana-archive@lists.ietf.org>; Thu, 4 Dec 2003 14:07:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyoX-0002o2-QF; Thu, 04 Dec 2003 14:07:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyoI-0002nA-Vq
	for pana@optimus.ietf.org; Thu, 04 Dec 2003 14:06:47 -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 OAA08881
	for <pana@ietf.org>; Thu, 4 Dec 2003 14:06:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyoG-0006c6-00
	for pana@ietf.org; Thu, 04 Dec 2003 14:06:44 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyoF-0006c3-00
	for pana@ietf.org; Thu, 04 Dec 2003 14:06:43 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB4J6cY9026288;
	Fri, 5 Dec 2003 04:06:38 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB4J6c4i016328;
	Fri, 5 Dec 2003 04:06:38 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA16327 ; Fri, 5 Dec 2003 04:06:37 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA06740; Fri, 5 Dec 2003 04:06:37 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA16742; Fri, 5 Dec 2003 04:06:37 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB4J6a61010744;
	Fri, 5 Dec 2003 04:06:36 +0900 (JST)
Received: from steelhead ([159.119.168.136]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPD00HTJX2YB9@tsbpo1.po.toshiba.co.jp>; Fri,
 5 Dec 2003 04:06:35 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ARylx-0004Hi-00; Thu, 04 Dec 2003 11:04:21 -0800
Date: Thu, 04 Dec 2003 11:04:21 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol
 requirements)
In-reply-to: <3FCF7967.4080807@alcatel.fr>
To: Yacine.El_Mghazli@alcatel.fr
Cc: pana@ietf.org
Message-id: <20031204190420.GB15321@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Yacine.El_Mghazli@alcatel.fr, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net>
 <3FCF7967.4080807@alcatel.fr>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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, Dec 04, 2003 at 07:13:59PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> thanks yoshi, I much better understand the problem now. please see below 
> some comments inline:
> 
> Yoshihiro.Ohba@tais.com wrote:
> 
> >
> >Assume that:
> >
> >- PAA performs SNMP-based polling to detect inactive EPs at every 60
> >seconds.
> >   Say the last polling occured at time T.
> >
> >- Some EP rebooted after T.  The reboot procedure completes before T+60.
> >
> >- At the next polling time, PAA will receives response from the rebooted
> >EP.
> >  Unless there is some reboot detection mechanism, PAA will not realize
> >that
> >  the EP has been rebooted, 
> 
> since the EP is empty after rebooting, the first packet coming from any 
> of the PaC will be considered as unauthorized and trigger a "New PaC 
> notification" (PANA auth request message, SNMP trap, or whatever...) to 
> the PAA. hence, it is sufficient fot the PAA to be rapidly aware of the 
> problem.

But the "new PaC notification" is used only when the PAA is the
initiator of the PANA authentication.  PAA might not able to rely on
the "new PaC notification" from EP if the authentication policy of the
access network allows PaC-initiated PANA authentication only.


> 
> >and as a result states will not be synchronized
> >between EP and PAA.
> 
> in a recent discussion on the stateful/stateless appoach, we (mostly 
> alper) agreed that the PAA does not maintain any EP state --> no 
> synchronisation anyway.

My understanding is a bit differnet.  PAA needs to mainmain EP state
anyway, but the exact method for maintaining EP state is left to
implementations and does not need to be standardized in the PANA WG
(but I think it would be helpful if we could have some implementation
guidance about the method).

Yoshihiro Ohba

> 
> I would say: once the PAA is aware the EP has rebooted, it should send 
> again the set of rules to this EP, based on the PaC states, which are 
> maintained in the PAA.
> 
> thanks,
> yacine
> 

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


From exim@www1.ietf.org  Thu Dec  4 14:07:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08973
	for <pana-archive@odin.ietf.org>; Thu, 4 Dec 2003 14:07: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 1ARyob-0002rM-NW
	for pana-archive@odin.ietf.org; Thu, 04 Dec 2003 14:07:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB4J75ke010986
	for pana-archive@odin.ietf.org; Thu, 4 Dec 2003 14:07:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyoa-0002r5-MA
	for pana-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 14:07: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 OAA08907
	for <pana-web-archive@ietf.org>; Thu, 4 Dec 2003 14:06:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyoY-0006cP-00
	for pana-web-archive@ietf.org; Thu, 04 Dec 2003 14:07:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyoX-0006cM-00
	for pana-web-archive@ietf.org; Thu, 04 Dec 2003 14:07:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyoX-0002o2-QF; Thu, 04 Dec 2003 14:07:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyoI-0002nA-Vq
	for pana@optimus.ietf.org; Thu, 04 Dec 2003 14:06:47 -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 OAA08881
	for <pana@ietf.org>; Thu, 4 Dec 2003 14:06:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyoG-0006c6-00
	for pana@ietf.org; Thu, 04 Dec 2003 14:06:44 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyoF-0006c3-00
	for pana@ietf.org; Thu, 04 Dec 2003 14:06:43 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB4J6cY9026288;
	Fri, 5 Dec 2003 04:06:38 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB4J6c4i016328;
	Fri, 5 Dec 2003 04:06:38 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA16327 ; Fri, 5 Dec 2003 04:06:37 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA06740; Fri, 5 Dec 2003 04:06:37 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA16742; Fri, 5 Dec 2003 04:06:37 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB4J6a61010744;
	Fri, 5 Dec 2003 04:06:36 +0900 (JST)
Received: from steelhead ([159.119.168.136]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPD00HTJX2YB9@tsbpo1.po.toshiba.co.jp>; Fri,
 5 Dec 2003 04:06:35 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ARylx-0004Hi-00; Thu, 04 Dec 2003 11:04:21 -0800
Date: Thu, 04 Dec 2003 11:04:21 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol
 requirements)
In-reply-to: <3FCF7967.4080807@alcatel.fr>
To: Yacine.El_Mghazli@alcatel.fr
Cc: pana@ietf.org
Message-id: <20031204190420.GB15321@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Yacine.El_Mghazli@alcatel.fr, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net>
 <3FCF7967.4080807@alcatel.fr>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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, Dec 04, 2003 at 07:13:59PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> thanks yoshi, I much better understand the problem now. please see below 
> some comments inline:
> 
> Yoshihiro.Ohba@tais.com wrote:
> 
> >
> >Assume that:
> >
> >- PAA performs SNMP-based polling to detect inactive EPs at every 60
> >seconds.
> >   Say the last polling occured at time T.
> >
> >- Some EP rebooted after T.  The reboot procedure completes before T+60.
> >
> >- At the next polling time, PAA will receives response from the rebooted
> >EP.
> >  Unless there is some reboot detection mechanism, PAA will not realize
> >that
> >  the EP has been rebooted, 
> 
> since the EP is empty after rebooting, the first packet coming from any 
> of the PaC will be considered as unauthorized and trigger a "New PaC 
> notification" (PANA auth request message, SNMP trap, or whatever...) to 
> the PAA. hence, it is sufficient fot the PAA to be rapidly aware of the 
> problem.

But the "new PaC notification" is used only when the PAA is the
initiator of the PANA authentication.  PAA might not able to rely on
the "new PaC notification" from EP if the authentication policy of the
access network allows PaC-initiated PANA authentication only.


> 
> >and as a result states will not be synchronized
> >between EP and PAA.
> 
> in a recent discussion on the stateful/stateless appoach, we (mostly 
> alper) agreed that the PAA does not maintain any EP state --> no 
> synchronisation anyway.

My understanding is a bit differnet.  PAA needs to mainmain EP state
anyway, but the exact method for maintaining EP state is left to
implementations and does not need to be standardized in the PANA WG
(but I think it would be helpful if we could have some implementation
guidance about the method).

Yoshihiro Ohba

> 
> I would say: once the PAA is aware the EP has rebooted, it should send 
> again the set of rules to this EP, based on the PaC states, which are 
> maintained in the PAA.
> 
> thanks,
> yacine
> 

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



From pana-admin@ietf.org  Thu Dec  4 14:22:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09728
	for <pana-archive@lists.ietf.org>; Thu, 4 Dec 2003 14:22:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARz33-0004BU-80; Thu, 04 Dec 2003 14:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyJl-0000xx-3w
	for pana@optimus.ietf.org; Thu, 04 Dec 2003 13:35:13 -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 NAA06978
	for <pana@ietf.org>; Thu, 4 Dec 2003 13:16:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARy1p-0005on-00
	for pana@ietf.org; Thu, 04 Dec 2003 13:16:41 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARy1n-0005ok-00
	for pana@ietf.org; Thu, 04 Dec 2003 13:16:40 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB4IGZY9014080
	for <pana@ietf.org>; Fri, 5 Dec 2003 03:16:35 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB4IGZWm000613
	for <pana@ietf.org>; Fri, 5 Dec 2003 03:16:35 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA00608 ; Fri, 5 Dec 2003 03:16:35 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA25560; Fri, 5 Dec 2003 03:16:34 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA16164; Fri, 5 Dec 2003 03:16:34 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB4IGX61004494
	for <pana@ietf.org>; Fri, 5 Dec 2003 03:16:34 +0900 (JST)
Received: from steelhead ([159.119.168.136]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPD00HDCURJB9@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Fri,
 5 Dec 2003 03:16:33 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ARxzx-00048T-00 for <pana@ietf.org>; Thu, 04 Dec 2003 10:14:45 -0800
Date: Thu, 04 Dec 2003 10:14:45 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031204181445.GA15321@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] Issue35: 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>

Text for issue35 is proposed below.  (Issue35 can be found at:
http://danforsberg.info:8080/pana-issues/issue35)

Add the following section in Section 4:

"4.X  Support for Separate EP  (X:TBD)

  PANA allows PAA and EP to be separate entities.  In this
  case, if data traffic protection needs to be initiated after
  successful PANA authentication phase, PaC needs to know the device
  identifier of EP(s) so that it is able to establish a security
  association with each EP to protect data traffic.

  To this end, when a Protection-Capability AVP with either
  L2_PROTECTION or IPSEC_PROTECTION in the AVP payload is carried in a
  PANA-Bind-Request message and if there is an EP that has a different
  device identifier than that of the PAA, one or more EP-Device-Id AVPs
  MUST also be carried in the PANA-Bind-Request message.  In this
  case, if one EP has the same device identifier as the PAA, an
  EP-Device-Id AVP that contains the device identifier of the
  EP (i.e., the PAA) MUST also be included in the PANA-Bind-Request."


Add the following item in Section 4.1.1:

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

Add the following item in Section 4.1.5:

  "*  List of device identifiers of EPs."


Change the PANA-Bind-Request ABNF in section 9.3.6 to:


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

Add the following section:

"9.4.15 EP-Device-Id AVP
                                                                                
   The EP-Device-Id AVP (AVP Code: 1038) contains the device
   identifier of an EP.  The payload format of the EP-Device-Id AVP is
   the same as that of the Device-Id AVP (see Section 9.4.3)."
                                                                                
 
Update the AVP occurrence table in Section 9.5 to:

"
                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      Result-Code         |  0  |  0  |  0  |  0  |  1  |  0  |  0  |
      Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  |  0  |
      Termination-Cause   |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
      EAP-Payload         |  0  |  0  |  1  |  1  |  1  |  0  |  0  |
      MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
      Device-Id           |  0  |  0  |  0  |  0  |  1+ |  1+ | 0-1 |
      Cookie              | 0-1 | 0-1 |  0  |  0  |  0  |  0  |  0  |
      Protection-Cap.     |  0  |  0  |  0  |  0  | 0-1 |  0  |  0  |
      Session-Lifetime    |  0  |  0  |  0  |  0  | 0-1 |  0  |  0  |
      Failed-AVP          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
      ISP-Information     |  0+ | 0-1 | 0-1 |  0  |  0  |  0  |  0  |
      NAP-Information     | 0-1 |  0  | 0-1 |  0  |  0  |  0  |  0  |
      EP-Device-Id        |  0  |  0  |  0  |  0  |  0+ |  0  |  0  |
      --------------------+-----+-----+-----+-----+-----+-----+-----+

                          +-------------------------------+
                          |      Message                  |
                          |       Type                    |
                          +------+------+-----+-----+-----+
      Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
      --------------------+------+------+-----+-----+-----+
      Result-Code         |  0   |  0   |  0  |  0  |  1  |
      Session-Id          |  1   |  1   |  1  |  1  |  1  |
      Termination-Cause   |  0   |  0   |  1  |  0  |  0  |
      EAP-Payload         | 0-1  | 0-1  |  0  |  0  |  0  |
      MAC                 | 0-1  | 0-1  | 0-1 | 0-1 | 0-1 |
      Device-Id           |  1+  |  1+  |  0  |  0  |  0  |
      Cookie              |  0   |  0   |  0  |  0  |  0  |
      Protection-Cap.     |  0   |  0   |  0  |  0  |  0  |
      Session-Lifetime    |  0   |  0   |  0  |  0  |  0  |
      Failed-AVP          |  0   |  0   |  0  |  0  |  1  |
      ISP-Information     |  0   |  0   |  0  |  0  |  0  |
      NAP-Information     |  0   |  0   |  0  |  0  |  0  |
      EP-Device-Id        |  0   |  0   |  0  |  0  |  0  |
      --------------------+------+------+-----+-----+-----+
"
                                                                                











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


From exim@www1.ietf.org  Thu Dec  4 14:22:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09743
	for <pana-archive@odin.ietf.org>; Thu, 4 Dec 2003 14:22:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARz38-0004G5-0H
	for pana-archive@odin.ietf.org; Thu, 04 Dec 2003 14:22:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB4JM5uJ016363
	for pana-archive@odin.ietf.org; Thu, 4 Dec 2003 14:22:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARz36-0004Ff-Pv
	for pana-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 14:22: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 OAA09685
	for <pana-web-archive@ietf.org>; Thu, 4 Dec 2003 14:21:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARz33-0006u1-00
	for pana-web-archive@ietf.org; Thu, 04 Dec 2003 14:22:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARz33-0006tu-00
	for pana-web-archive@ietf.org; Thu, 04 Dec 2003 14:22:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARz33-0004BU-80; Thu, 04 Dec 2003 14:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyJl-0000xx-3w
	for pana@optimus.ietf.org; Thu, 04 Dec 2003 13:35:13 -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 NAA06978
	for <pana@ietf.org>; Thu, 4 Dec 2003 13:16:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARy1p-0005on-00
	for pana@ietf.org; Thu, 04 Dec 2003 13:16:41 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARy1n-0005ok-00
	for pana@ietf.org; Thu, 04 Dec 2003 13:16:40 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB4IGZY9014080
	for <pana@ietf.org>; Fri, 5 Dec 2003 03:16:35 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB4IGZWm000613
	for <pana@ietf.org>; Fri, 5 Dec 2003 03:16:35 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id DAA00608 ; Fri, 5 Dec 2003 03:16:35 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id DAA25560; Fri, 5 Dec 2003 03:16:34 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id DAA16164; Fri, 5 Dec 2003 03:16:34 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB4IGX61004494
	for <pana@ietf.org>; Fri, 5 Dec 2003 03:16:34 +0900 (JST)
Received: from steelhead ([159.119.168.136]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPD00HDCURJB9@tsbpo1.po.toshiba.co.jp> for pana@ietf.org; Fri,
 5 Dec 2003 03:16:33 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ARxzx-00048T-00 for <pana@ietf.org>; Thu, 04 Dec 2003 10:14:45 -0800
Date: Thu, 04 Dec 2003 10:14:45 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
To: pana@ietf.org
Message-id: <20031204181445.GA15321@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] Issue35: 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>

Text for issue35 is proposed below.  (Issue35 can be found at:
http://danforsberg.info:8080/pana-issues/issue35)

Add the following section in Section 4:

"4.X  Support for Separate EP  (X:TBD)

  PANA allows PAA and EP to be separate entities.  In this
  case, if data traffic protection needs to be initiated after
  successful PANA authentication phase, PaC needs to know the device
  identifier of EP(s) so that it is able to establish a security
  association with each EP to protect data traffic.

  To this end, when a Protection-Capability AVP with either
  L2_PROTECTION or IPSEC_PROTECTION in the AVP payload is carried in a
  PANA-Bind-Request message and if there is an EP that has a different
  device identifier than that of the PAA, one or more EP-Device-Id AVPs
  MUST also be carried in the PANA-Bind-Request message.  In this
  case, if one EP has the same device identifier as the PAA, an
  EP-Device-Id AVP that contains the device identifier of the
  EP (i.e., the PAA) MUST also be included in the PANA-Bind-Request."


Add the following item in Section 4.1.1:

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

Add the following item in Section 4.1.5:

  "*  List of device identifiers of EPs."


Change the PANA-Bind-Request ABNF in section 9.3.6 to:


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

Add the following section:

"9.4.15 EP-Device-Id AVP
                                                                                
   The EP-Device-Id AVP (AVP Code: 1038) contains the device
   identifier of an EP.  The payload format of the EP-Device-Id AVP is
   the same as that of the Device-Id AVP (see Section 9.4.3)."
                                                                                
 
Update the AVP occurrence table in Section 9.5 to:

"
                          +-----------------------------------------+
                          |        Message                          |
                          |          Type                           |
                          +-----+-----+-----+-----+-----+-----+-----+
      Attribute Name      | PSR | PSA | PAR | PAN | PBR | PBA | PDI |
      --------------------+-----+-----+-----+-----+-----+-----+-----+
      Result-Code         |  0  |  0  |  0  |  0  |  1  |  0  |  0  |
      Session-Id          |  0  |  0  |  1  |  1  |  1  |  1  |  0  |
      Termination-Cause   |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
      EAP-Payload         |  0  |  0  |  1  |  1  |  1  |  0  |  0  |
      MAC                 |  0  |  0  | 0-1 | 0-1 | 0-1 | 0-1 |  0  |
      Device-Id           |  0  |  0  |  0  |  0  |  1+ |  1+ | 0-1 |
      Cookie              | 0-1 | 0-1 |  0  |  0  |  0  |  0  |  0  |
      Protection-Cap.     |  0  |  0  |  0  |  0  | 0-1 |  0  |  0  |
      Session-Lifetime    |  0  |  0  |  0  |  0  | 0-1 |  0  |  0  |
      Failed-AVP          |  0  |  0  |  0  |  0  |  0  |  0  |  0  |
      ISP-Information     |  0+ | 0-1 | 0-1 |  0  |  0  |  0  |  0  |
      NAP-Information     | 0-1 |  0  | 0-1 |  0  |  0  |  0  |  0  |
      EP-Device-Id        |  0  |  0  |  0  |  0  |  0+ |  0  |  0  |
      --------------------+-----+-----+-----+-----+-----+-----+-----+

                          +-------------------------------+
                          |      Message                  |
                          |       Type                    |
                          +------+------+-----+-----+-----+
      Attribute Name      | PRAR | PRAA | PTR | PTA | PER |
      --------------------+------+------+-----+-----+-----+
      Result-Code         |  0   |  0   |  0  |  0  |  1  |
      Session-Id          |  1   |  1   |  1  |  1  |  1  |
      Termination-Cause   |  0   |  0   |  1  |  0  |  0  |
      EAP-Payload         | 0-1  | 0-1  |  0  |  0  |  0  |
      MAC                 | 0-1  | 0-1  | 0-1 | 0-1 | 0-1 |
      Device-Id           |  1+  |  1+  |  0  |  0  |  0  |
      Cookie              |  0   |  0   |  0  |  0  |  0  |
      Protection-Cap.     |  0   |  0   |  0  |  0  |  0  |
      Session-Lifetime    |  0   |  0   |  0  |  0  |  0  |
      Failed-AVP          |  0   |  0   |  0  |  0  |  1  |
      ISP-Information     |  0   |  0   |  0  |  0  |  0  |
      NAP-Information     |  0   |  0   |  0  |  0  |  0  |
      EP-Device-Id        |  0   |  0   |  0  |  0  |  0  |
      --------------------+------+------+-----+-----+-----+
"
                                                                                











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



From pana-admin@ietf.org  Fri Dec  5 08:27:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04386
	for <pana-archive@lists.ietf.org>; Fri, 5 Dec 2003 08:27: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 1ASFz2-0003wq-T5; Fri, 05 Dec 2003 08:27:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASFyU-0003wN-Gw
	for pana@optimus.ietf.org; Fri, 05 Dec 2003 08:26:26 -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 IAA04353
	for <pana@ietf.org>; Fri, 5 Dec 2003 08:26:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASFyT-00015K-00
	for pana@ietf.org; Fri, 05 Dec 2003 08:26:25 -0500
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASFyS-00014U-00
	for pana@ietf.org; Fri, 05 Dec 2003 08:26:24 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB5DP87H017022;
	Fri, 5 Dec 2003 14:25:34 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120514253218:4419 ;
          Fri, 5 Dec 2003 14:25:32 +0100 
Message-ID: <3FD0874C.4000505@alcatel.fr>
Date: Fri, 05 Dec 2003 14:25:32 +0100
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: pana@ietf.org
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol requirements)
References: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net> <3FCF7967.4080807@alcatel.fr> <20031204190420.GB15321@steelhead>
In-Reply-To: <20031204190420.GB15321@steelhead>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/05/2003 14:25:32,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/05/2003 14:25:34,
	Serialize complete at 12/05/2003 14:25:34
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-Alcanet-MTA-scanned-and-authorized: yes
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 Ohba wrote:
> On Thu, Dec 04, 2003 at 07:13:59PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> 
>>thanks yoshi, I much better understand the problem now. please see below 
>>some comments inline:
>>
>>Yoshihiro.Ohba@tais.com wrote:
>>
>>
>>>Assume that:
>>>
>>>- PAA performs SNMP-based polling to detect inactive EPs at every 60
>>>seconds.
>>>  Say the last polling occured at time T.
>>>
>>>- Some EP rebooted after T.  The reboot procedure completes before T+60.
>>>
>>>- At the next polling time, PAA will receives response from the rebooted
>>>EP.
>>> Unless there is some reboot detection mechanism, PAA will not realize
>>>that
>>> the EP has been rebooted, 
>>
>>since the EP is empty after rebooting, the first packet coming from any 
>>of the PaC will be considered as unauthorized and trigger a "New PaC 
>>notification" (PANA auth request message, SNMP trap, or whatever...) to 
>>the PAA. hence, it is sufficient fot the PAA to be rapidly aware of the 
>>problem.
> 
> 
> But the "new PaC notification" is used only when the PAA is the
> initiator of the PANA authentication.  PAA might not able to rely on
> the "new PaC notification" from EP if the authentication policy of the
> access network allows PaC-initiated PANA authentication only.
> 

I cant see any reason for preventing this notif since it can be useful
for detecting such an EP has rebooted. it doesnt mean that the PAA
initiates a PANA auth at all, it only re-configure the EP with the set
of rules it lost during the reboot.

anyway your MIB object (reboot counter, etc.) could work either...

> 
> 
>>>and as a result states will not be synchronized
>>>between EP and PAA.
>>
>>in a recent discussion on the stateful/stateless appoach, we (mostly 
>>alper) agreed that the PAA does not maintain any EP state --> no 
>>synchronisation anyway.
> 
> 
> My understanding is a bit differnet.  PAA needs to mainmain EP state
> anyway, but the exact method for maintaining EP state is left to
> implementations and does not need to be standardized in the PANA WG
> (but I think it would be helpful if we could have some implementation
> guidance about the method).

keeping an EP state in the PAA means the PAA knows what's the current EP
configuration without polling the EP. so far, it's impossible because we
said the EP can be managed by another PAA.

the PAA keeps the PaC state and configure the EPs accordingly, it can
re-configure the EPs, is needed and based on the PaC state it keeps.
that may be what you mean by implementation concern. do you agree ?

finally: for sure, nothing will be standardized in the PANA WG since we
will reuse existing stuff. the only thing here is to determine weither a
stateful approach is needed. for now, it seems not to be the case and I
would like to avoid misunderstandings.

> 
> Yoshihiro Ohba
> 

thank you,
yacine

> 
>>I would say: once the PAA is aware the EP has rebooted, it should send 
>>again the set of rules to this EP, based on the PaC states, which are 
>>maintained in the PAA.
>>
>>thanks,
>>yacine
>>
> 
> 



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


From exim@www1.ietf.org  Fri Dec  5 08:27:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04408
	for <pana-archive@odin.ietf.org>; Fri, 5 Dec 2003 08:27:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASFz6-0003xb-Sp
	for pana-archive@odin.ietf.org; Fri, 05 Dec 2003 08:27:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB5DR48p015217
	for pana-archive@odin.ietf.org; Fri, 5 Dec 2003 08: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 1ASFz6-0003xM-Oj
	for pana-web-archive@optimus.ietf.org; Fri, 05 Dec 2003 08: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 IAA04367
	for <pana-web-archive@ietf.org>; Fri, 5 Dec 2003 08:26:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASFz5-00015x-00
	for pana-web-archive@ietf.org; Fri, 05 Dec 2003 08:27:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASFz5-00015t-00
	for pana-web-archive@ietf.org; Fri, 05 Dec 2003 08:27:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASFz2-0003wq-T5; Fri, 05 Dec 2003 08:27:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASFyU-0003wN-Gw
	for pana@optimus.ietf.org; Fri, 05 Dec 2003 08:26:26 -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 IAA04353
	for <pana@ietf.org>; Fri, 5 Dec 2003 08:26:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASFyT-00015K-00
	for pana@ietf.org; Fri, 05 Dec 2003 08:26:25 -0500
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASFyS-00014U-00
	for pana@ietf.org; Fri, 05 Dec 2003 08:26:24 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hB5DP87H017022;
	Fri, 5 Dec 2003 14:25:34 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003120514253218:4419 ;
          Fri, 5 Dec 2003 14:25:32 +0100 
Message-ID: <3FD0874C.4000505@alcatel.fr>
Date: Fri, 05 Dec 2003 14:25:32 +0100
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: pana@ietf.org
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol requirements)
References: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net> <3FCF7967.4080807@alcatel.fr> <20031204190420.GB15321@steelhead>
In-Reply-To: <20031204190420.GB15321@steelhead>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/05/2003 14:25:32,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/05/2003 14:25:34,
	Serialize complete at 12/05/2003 14:25:34
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-Alcanet-MTA-scanned-and-authorized: yes
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 Ohba wrote:
> On Thu, Dec 04, 2003 at 07:13:59PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> 
>>thanks yoshi, I much better understand the problem now. please see below 
>>some comments inline:
>>
>>Yoshihiro.Ohba@tais.com wrote:
>>
>>
>>>Assume that:
>>>
>>>- PAA performs SNMP-based polling to detect inactive EPs at every 60
>>>seconds.
>>>  Say the last polling occured at time T.
>>>
>>>- Some EP rebooted after T.  The reboot procedure completes before T+60.
>>>
>>>- At the next polling time, PAA will receives response from the rebooted
>>>EP.
>>> Unless there is some reboot detection mechanism, PAA will not realize
>>>that
>>> the EP has been rebooted, 
>>
>>since the EP is empty after rebooting, the first packet coming from any 
>>of the PaC will be considered as unauthorized and trigger a "New PaC 
>>notification" (PANA auth request message, SNMP trap, or whatever...) to 
>>the PAA. hence, it is sufficient fot the PAA to be rapidly aware of the 
>>problem.
> 
> 
> But the "new PaC notification" is used only when the PAA is the
> initiator of the PANA authentication.  PAA might not able to rely on
> the "new PaC notification" from EP if the authentication policy of the
> access network allows PaC-initiated PANA authentication only.
> 

I cant see any reason for preventing this notif since it can be useful
for detecting such an EP has rebooted. it doesnt mean that the PAA
initiates a PANA auth at all, it only re-configure the EP with the set
of rules it lost during the reboot.

anyway your MIB object (reboot counter, etc.) could work either...

> 
> 
>>>and as a result states will not be synchronized
>>>between EP and PAA.
>>
>>in a recent discussion on the stateful/stateless appoach, we (mostly 
>>alper) agreed that the PAA does not maintain any EP state --> no 
>>synchronisation anyway.
> 
> 
> My understanding is a bit differnet.  PAA needs to mainmain EP state
> anyway, but the exact method for maintaining EP state is left to
> implementations and does not need to be standardized in the PANA WG
> (but I think it would be helpful if we could have some implementation
> guidance about the method).

keeping an EP state in the PAA means the PAA knows what's the current EP
configuration without polling the EP. so far, it's impossible because we
said the EP can be managed by another PAA.

the PAA keeps the PaC state and configure the EPs accordingly, it can
re-configure the EPs, is needed and based on the PaC state it keeps.
that may be what you mean by implementation concern. do you agree ?

finally: for sure, nothing will be standardized in the PANA WG since we
will reuse existing stuff. the only thing here is to determine weither a
stateful approach is needed. for now, it seems not to be the case and I
would like to avoid misunderstandings.

> 
> Yoshihiro Ohba
> 

thank you,
yacine

> 
>>I would say: once the PAA is aware the EP has rebooted, it should send 
>>again the set of rules to this EP, based on the PaC states, which are 
>>maintained in the PAA.
>>
>>thanks,
>>yacine
>>
> 
> 



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



From pana-admin@ietf.org  Fri Dec  5 12:09:47 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14048
	for <pana-archive@lists.ietf.org>; Fri, 5 Dec 2003 12:09:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASJRt-0003YH-Ey; Fri, 05 Dec 2003 12:09:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASJQy-0003Wt-0n
	for pana@optimus.ietf.org; Fri, 05 Dec 2003 12:08: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 MAA14007
	for <pana@ietf.org>; Fri, 5 Dec 2003 12:07:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASJQw-00051z-00
	for pana@ietf.org; Fri, 05 Dec 2003 12:08:02 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASJQv-00051q-00
	for pana@ietf.org; Fri, 05 Dec 2003 12:08:02 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB5H7uY9029924;
	Sat, 6 Dec 2003 02:07:56 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB5H7uwL029424;
	Sat, 6 Dec 2003 02:07:56 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id CAA29423 ; Sat, 6 Dec 2003 02:07:55 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA21197; Sat, 6 Dec 2003 02:07:55 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA00623; Sat, 6 Dec 2003 02:07:55 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB5H7r6b025418;
	Sat, 6 Dec 2003 02:07:54 +0900 (JST)
Received: from steelhead ([159.119.168.170]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPF00DYAM914C@tsbpo1.po.toshiba.co.jp>; Sat,
 6 Dec 2003 02:07:53 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ASJQb-0005lG-00; Fri, 05 Dec 2003 09:07:41 -0800
Date: Fri, 05 Dec 2003 09:07:41 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol
 requirements)
In-reply-to: <3FD0874C.4000505@alcatel.fr>
To: Yacine.El_Mghazli@alcatel.fr
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031205170741.GC20964@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Yacine.El_Mghazli@alcatel.fr,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net>
 <3FCF7967.4080807@alcatel.fr> <20031204190420.GB15321@steelhead>
 <3FD0874C.4000505@alcatel.fr>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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, Dec 05, 2003 at 02:25:32PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> Yoshihiro Ohba wrote:
> > On Thu, Dec 04, 2003 at 07:13:59PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> > 
> >>thanks yoshi, I much better understand the problem now. please see below 
> >>some comments inline:
> >>
> >>Yoshihiro.Ohba@tais.com wrote:
> >>
> >>
> >>>Assume that:
> >>>
> >>>- PAA performs SNMP-based polling to detect inactive EPs at every 60
> >>>seconds.
> >>>  Say the last polling occured at time T.
> >>>
> >>>- Some EP rebooted after T.  The reboot procedure completes before T+60.
> >>>
> >>>- At the next polling time, PAA will receives response from the rebooted
> >>>EP.
> >>> Unless there is some reboot detection mechanism, PAA will not realize
> >>>that
> >>> the EP has been rebooted, 
> >>
> >>since the EP is empty after rebooting, the first packet coming from any 
> >>of the PaC will be considered as unauthorized and trigger a "New PaC 
> >>notification" (PANA auth request message, SNMP trap, or whatever...) to 
> >>the PAA. hence, it is sufficient fot the PAA to be rapidly aware of the 
> >>problem.
> > 
> > 
> > But the "new PaC notification" is used only when the PAA is the
> > initiator of the PANA authentication.  PAA might not able to rely on
> > the "new PaC notification" from EP if the authentication policy of the
> > access network allows PaC-initiated PANA authentication only.
> > 
> 
> I cant see any reason for preventing this notif since it can be useful
> for detecting such an EP has rebooted. it doesnt mean that the PAA
> initiates a PANA auth at all, it only re-configure the EP with the set
> of rules it lost during the reboot.

There is some problem with using "new PaC notification" for rebooted
EP detection.  The rebooted EP cannot generate the notification until
it sees some packet originated by the PaC.  

> 
> anyway your MIB object (reboot counter, etc.) could work either...
> 
> > 
> > 
> >>>and as a result states will not be synchronized
> >>>between EP and PAA.
> >>
> >>in a recent discussion on the stateful/stateless appoach, we (mostly 
> >>alper) agreed that the PAA does not maintain any EP state --> no 
> >>synchronisation anyway.
> > 
> > 
> > My understanding is a bit differnet.  PAA needs to mainmain EP state
> > anyway, but the exact method for maintaining EP state is left to
> > implementations and does not need to be standardized in the PANA WG
> > (but I think it would be helpful if we could have some implementation
> > guidance about the method).
> 
> keeping an EP state in the PAA means the PAA knows what's the current EP
> configuration without polling the EP. so far, it's impossible because we
> said the EP can be managed by another PAA.
> 
> the PAA keeps the PaC state and configure the EPs accordingly, it can
> re-configure the EPs, is needed and based on the PaC state it keeps.
> that may be what you mean by implementation concern. do you agree ?

Yes.

> 
> finally: for sure, nothing will be standardized in the PANA WG since we
> will reuse existing stuff. the only thing here is to determine weither a
> stateful approach is needed. for now, it seems not to be the case and I
> would like to avoid misunderstandings.

I believe that stateful approach is needed in total solution (i.e.,
PAA-EP protocol plus application that runs on top of the PAA-EP
protocol).  But this does not mean PAA-EP protocol itself needs to be
stateful.  If the application can maintain statefulness on top of
stateless PAA-EP protocol by using application-level polling, etc.,
that is fine.

Yoshihiro Ohba


> 
> > 
> > Yoshihiro Ohba
> > 
> 
> thank you,
> yacine
> 
> > 
> >>I would say: once the PAA is aware the EP has rebooted, it should send 
> >>again the set of rules to this EP, based on the PaC states, which are 
> >>maintained in the PAA.
> >>
> >>thanks,
> >>yacine
> >>
> > 
> > 
> 
> 

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


From exim@www1.ietf.org  Fri Dec  5 12:09:49 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14063
	for <pana-archive@odin.ietf.org>; Fri, 5 Dec 2003 12:09:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASJSQ-0003Yz-2k
	for pana-archive@odin.ietf.org; Fri, 05 Dec 2003 12:09:34 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB5H9YZV013696
	for pana-archive@odin.ietf.org; Fri, 5 Dec 2003 12:09:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASJSP-0003Yp-Uv
	for pana-web-archive@optimus.ietf.org; Fri, 05 Dec 2003 12:09: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 MAA14039
	for <pana-web-archive@ietf.org>; Fri, 5 Dec 2003 12:09:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASJSO-00053j-00
	for pana-web-archive@ietf.org; Fri, 05 Dec 2003 12:09:32 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASJSO-00053g-00
	for pana-web-archive@ietf.org; Fri, 05 Dec 2003 12:09:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASJRt-0003YH-Ey; Fri, 05 Dec 2003 12:09:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASJQy-0003Wt-0n
	for pana@optimus.ietf.org; Fri, 05 Dec 2003 12:08: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 MAA14007
	for <pana@ietf.org>; Fri, 5 Dec 2003 12:07:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASJQw-00051z-00
	for pana@ietf.org; Fri, 05 Dec 2003 12:08:02 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASJQv-00051q-00
	for pana@ietf.org; Fri, 05 Dec 2003 12:08:02 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB5H7uY9029924;
	Sat, 6 Dec 2003 02:07:56 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB5H7uwL029424;
	Sat, 6 Dec 2003 02:07:56 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id CAA29423 ; Sat, 6 Dec 2003 02:07:55 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id CAA21197; Sat, 6 Dec 2003 02:07:55 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id CAA00623; Sat, 6 Dec 2003 02:07:55 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB5H7r6b025418;
	Sat, 6 Dec 2003 02:07:54 +0900 (JST)
Received: from steelhead ([159.119.168.170]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPF00DYAM914C@tsbpo1.po.toshiba.co.jp>; Sat,
 6 Dec 2003 02:07:53 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ASJQb-0005lG-00; Fri, 05 Dec 2003 09:07:41 -0800
Date: Fri, 05 Dec 2003 09:07:41 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: Inactive EP detection (was Re: [Pana] PAA-2-EP protocol
 requirements)
In-reply-to: <3FD0874C.4000505@alcatel.fr>
To: Yacine.El_Mghazli@alcatel.fr
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031205170741.GC20964@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Yacine.El_Mghazli@alcatel.fr,
 Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <OF08ECF71C.FDABE38A-ON88256DF0.00771FC3@tais.net>
 <3FCF7967.4080807@alcatel.fr> <20031204190420.GB15321@steelhead>
 <3FD0874C.4000505@alcatel.fr>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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, Dec 05, 2003 at 02:25:32PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> Yoshihiro Ohba wrote:
> > On Thu, Dec 04, 2003 at 07:13:59PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> > 
> >>thanks yoshi, I much better understand the problem now. please see below 
> >>some comments inline:
> >>
> >>Yoshihiro.Ohba@tais.com wrote:
> >>
> >>
> >>>Assume that:
> >>>
> >>>- PAA performs SNMP-based polling to detect inactive EPs at every 60
> >>>seconds.
> >>>  Say the last polling occured at time T.
> >>>
> >>>- Some EP rebooted after T.  The reboot procedure completes before T+60.
> >>>
> >>>- At the next polling time, PAA will receives response from the rebooted
> >>>EP.
> >>> Unless there is some reboot detection mechanism, PAA will not realize
> >>>that
> >>> the EP has been rebooted, 
> >>
> >>since the EP is empty after rebooting, the first packet coming from any 
> >>of the PaC will be considered as unauthorized and trigger a "New PaC 
> >>notification" (PANA auth request message, SNMP trap, or whatever...) to 
> >>the PAA. hence, it is sufficient fot the PAA to be rapidly aware of the 
> >>problem.
> > 
> > 
> > But the "new PaC notification" is used only when the PAA is the
> > initiator of the PANA authentication.  PAA might not able to rely on
> > the "new PaC notification" from EP if the authentication policy of the
> > access network allows PaC-initiated PANA authentication only.
> > 
> 
> I cant see any reason for preventing this notif since it can be useful
> for detecting such an EP has rebooted. it doesnt mean that the PAA
> initiates a PANA auth at all, it only re-configure the EP with the set
> of rules it lost during the reboot.

There is some problem with using "new PaC notification" for rebooted
EP detection.  The rebooted EP cannot generate the notification until
it sees some packet originated by the PaC.  

> 
> anyway your MIB object (reboot counter, etc.) could work either...
> 
> > 
> > 
> >>>and as a result states will not be synchronized
> >>>between EP and PAA.
> >>
> >>in a recent discussion on the stateful/stateless appoach, we (mostly 
> >>alper) agreed that the PAA does not maintain any EP state --> no 
> >>synchronisation anyway.
> > 
> > 
> > My understanding is a bit differnet.  PAA needs to mainmain EP state
> > anyway, but the exact method for maintaining EP state is left to
> > implementations and does not need to be standardized in the PANA WG
> > (but I think it would be helpful if we could have some implementation
> > guidance about the method).
> 
> keeping an EP state in the PAA means the PAA knows what's the current EP
> configuration without polling the EP. so far, it's impossible because we
> said the EP can be managed by another PAA.
> 
> the PAA keeps the PaC state and configure the EPs accordingly, it can
> re-configure the EPs, is needed and based on the PaC state it keeps.
> that may be what you mean by implementation concern. do you agree ?

Yes.

> 
> finally: for sure, nothing will be standardized in the PANA WG since we
> will reuse existing stuff. the only thing here is to determine weither a
> stateful approach is needed. for now, it seems not to be the case and I
> would like to avoid misunderstandings.

I believe that stateful approach is needed in total solution (i.e.,
PAA-EP protocol plus application that runs on top of the PAA-EP
protocol).  But this does not mean PAA-EP protocol itself needs to be
stateful.  If the application can maintain statefulness on top of
stateless PAA-EP protocol by using application-level polling, etc.,
that is fine.

Yoshihiro Ohba


> 
> > 
> > Yoshihiro Ohba
> > 
> 
> thank you,
> yacine
> 
> > 
> >>I would say: once the PAA is aware the EP has rebooted, it should send 
> >>again the set of rules to this EP, based on the PaC states, which are 
> >>maintained in the PAA.
> >>
> >>thanks,
> >>yacine
> >>
> > 
> > 
> 
> 

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



From pana-admin@ietf.org  Mon Dec  8 18:38:23 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12846
	for <pana-archive@lists.ietf.org>; Mon, 8 Dec 2003 18:38: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 1ATUwz-0003hI-1b; Mon, 08 Dec 2003 18:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUwh-0003a3-Ou
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 18:37:44 -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 SAA12769
	for <pana@ietf.org>; Mon, 8 Dec 2003 18:37:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUwe-0001mq-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:37:40 -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 1ATUwd-0001mk-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:37:40 -0500
Date: Mon, 08 Dec 2003 15:39:00 -0800
Subject: Re: [Pana] Issue16: Multihoming support
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yoshihiro.Ohba@tais.com>, <pana@ietf.org>
Message-ID: <BBFA4B94.E76C%alper@docomolabs-usa.com>
In-Reply-To: <OFD082057F.F9E5BD70-ON88256DF2.000437DF@tais.net>
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

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

I think the last part is not clear enough. What we really mean is each
*physical* interface needs to use separate PANA sessions to access the
network. Logical interfaces with different IP addresses might still be bound
to the same physical interface and hence not require separate PANA
instances.

I think the second half starting from "A distinct PANA session..." can be
replaced by:

    A distinct PANA session needs to be associated with each physical
    interface of a PaC. A PaC can maintain multiple PANA sessions at the
    same time, one for each interface that is authorized to access the
    network. 

Alper

    


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


From exim@www1.ietf.org  Mon Dec  8 18:38:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12861
	for <pana-archive@odin.ietf.org>; Mon, 8 Dec 2003 18:38: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 1ATUx9-0003i7-UU
	for pana-archive@odin.ietf.org; Mon, 08 Dec 2003 18:38:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8NcBeO014257
	for pana-archive@odin.ietf.org; Mon, 8 Dec 2003 18:38:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUx9-0003hs-Of
	for pana-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 18:38: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 SAA12814
	for <pana-web-archive@ietf.org>; Mon, 8 Dec 2003 18:37:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUx6-0001nM-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 18:38:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUx6-0001nI-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 18:38:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUwz-0003hI-1b; Mon, 08 Dec 2003 18:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUwh-0003a3-Ou
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 18:37:44 -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 SAA12769
	for <pana@ietf.org>; Mon, 8 Dec 2003 18:37:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUwe-0001mq-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:37:40 -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 1ATUwd-0001mk-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:37:40 -0500
Date: Mon, 08 Dec 2003 15:39:00 -0800
Subject: Re: [Pana] Issue16: Multihoming support
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yoshihiro.Ohba@tais.com>, <pana@ietf.org>
Message-ID: <BBFA4B94.E76C%alper@docomolabs-usa.com>
In-Reply-To: <OFD082057F.F9E5BD70-ON88256DF2.000437DF@tais.net>
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

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

I think the last part is not clear enough. What we really mean is each
*physical* interface needs to use separate PANA sessions to access the
network. Logical interfaces with different IP addresses might still be bound
to the same physical interface and hence not require separate PANA
instances.

I think the second half starting from "A distinct PANA session..." can be
replaced by:

    A distinct PANA session needs to be associated with each physical
    interface of a PaC. A PaC can maintain multiple PANA sessions at the
    same time, one for each interface that is authorized to access the
    network. 

Alper

    


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



From pana-admin@ietf.org  Mon Dec  8 18:40:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12976
	for <pana-archive@lists.ietf.org>; Mon, 8 Dec 2003 18:40:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUyx-0003q0-Ux; Mon, 08 Dec 2003 18:40:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUyG-0003o2-PI
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 18:39:20 -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 SAA12913
	for <pana@ietf.org>; Mon, 8 Dec 2003 18:39:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUyD-0001pc-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:39:17 -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 1ATUyC-0001pX-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:39:17 -0500
Date: Mon, 08 Dec 2003 15:40:37 -0800
Subject: Re: [Pana] Issue2: Downgrading protection
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yoshihiro.Ohba@tais.com>, <pana@ietf.org>
Message-ID: <BBFA4BF5.E76E%alper@docomolabs-usa.com>
In-Reply-To: <OF71E02608.6AC22A11-ON88256DF2.000940E8@tais.net>
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 12/3/03 5:52 PM, "Yoshihiro.Ohba@tais.com" <Yoshihiro.Ohba@tais.com>
wrote:

> 
> Issue2. Downgrading protection. This is an EAP problem. Use EAP-GSSAPI to
> negotiate EAP in secure way.
> 
> The consensus in the IETF58 meeting is that this is an EAP issue
> and not a PANA problem.  The PANA draft already has the following
> text in the Security Considerations section. However, if this is not a PANA
> problem, do we still need the text in PANA draft?

I suggest we remove that text from the draft.

Alper



> 
> 
> "  e) Preventing downgrading attacks
>  EAP supports a number of different EAP methods for authentication and
>  therefore it might be required to agree on a specific mechanism.  An
>  unprotected negotiation mechanism is supported in EAP and a secure
>  negotiation procedure for the GSS-API methods. The support of the
>  GSS-API as an EAP method is described in [I-D.aboba-pppext-eapgss]. A
>  protected negotiation is supported by the GSS-API with RFC 2478
>  [RFC2478]. If desired, such a protection can also be offered by PANA
>  by repeating the list of supported EAP methods protected with the
>  PANA SA. This type of protection is similar to the protected
>  negotiation described in [RFC3329].
>  This issue requires further investigation especially since the EAP
>  protocol is executed between different endpoints than the PANA
>  protocol."
> 
> The issue can be found at:
> http://www.danforsberg.info:8080/pana-issues/issue2
> 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 Dec  8 18:40:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12991
	for <pana-archive@odin.ietf.org>; Mon, 8 Dec 2003 18:40: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 1ATUz2-0003tn-K3
	for pana-archive@odin.ietf.org; Mon, 08 Dec 2003 18:40:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8Ne7IZ014971
	for pana-archive@odin.ietf.org; Mon, 8 Dec 2003 18:40:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUz0-0003sT-Dr
	for pana-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 18:40: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 SAA12951
	for <pana-web-archive@ietf.org>; Mon, 8 Dec 2003 18:39:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUyx-0001qd-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 18:40:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUyx-0001qa-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 18:40:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUyx-0003q0-Ux; Mon, 08 Dec 2003 18:40:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUyG-0003o2-PI
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 18:39:20 -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 SAA12913
	for <pana@ietf.org>; Mon, 8 Dec 2003 18:39:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUyD-0001pc-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:39:17 -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 1ATUyC-0001pX-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:39:17 -0500
Date: Mon, 08 Dec 2003 15:40:37 -0800
Subject: Re: [Pana] Issue2: Downgrading protection
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yoshihiro.Ohba@tais.com>, <pana@ietf.org>
Message-ID: <BBFA4BF5.E76E%alper@docomolabs-usa.com>
In-Reply-To: <OF71E02608.6AC22A11-ON88256DF2.000940E8@tais.net>
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 12/3/03 5:52 PM, "Yoshihiro.Ohba@tais.com" <Yoshihiro.Ohba@tais.com>
wrote:

> 
> Issue2. Downgrading protection. This is an EAP problem. Use EAP-GSSAPI to
> negotiate EAP in secure way.
> 
> The consensus in the IETF58 meeting is that this is an EAP issue
> and not a PANA problem.  The PANA draft already has the following
> text in the Security Considerations section. However, if this is not a PANA
> problem, do we still need the text in PANA draft?

I suggest we remove that text from the draft.

Alper



> 
> 
> "  e) Preventing downgrading attacks
>  EAP supports a number of different EAP methods for authentication and
>  therefore it might be required to agree on a specific mechanism.  An
>  unprotected negotiation mechanism is supported in EAP and a secure
>  negotiation procedure for the GSS-API methods. The support of the
>  GSS-API as an EAP method is described in [I-D.aboba-pppext-eapgss]. A
>  protected negotiation is supported by the GSS-API with RFC 2478
>  [RFC2478]. If desired, such a protection can also be offered by PANA
>  by repeating the list of supported EAP methods protected with the
>  PANA SA. This type of protection is similar to the protected
>  negotiation described in [RFC3329].
>  This issue requires further investigation especially since the EAP
>  protocol is executed between different endpoints than the PANA
>  protocol."
> 
> The issue can be found at:
> http://www.danforsberg.info:8080/pana-issues/issue2
> 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 Dec  8 18:41:13 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13092
	for <pana-archive@lists.ietf.org>; Mon, 8 Dec 2003 18:41:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUzt-0003yb-FU; Mon, 08 Dec 2003 18:41:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUzT-0003xX-BM
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 18:40:35 -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 SAA12974
	for <pana@ietf.org>; Mon, 8 Dec 2003 18:40:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUzQ-0001rh-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:40:32 -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 1ATUzP-0001re-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:40:31 -0500
Date: Mon, 08 Dec 2003 15:41:52 -0800
Subject: Re: [Pana] Issue34: Behaviour with NAP and ISP (two EAP
	authentications)
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yoshihiro.Ohba@tais.com>, <pana@ietf.org>
Message-ID: <BBFA4C40.E76F%alper@docomolabs-usa.com>
In-Reply-To: <OF0D15AF05.800AB2CE-ON88256DF0.007DA42A@tais.net>
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 IETF58 PANA meeting, the following resolution was proposed:
> 
> 
> -A single Session-Lifetime is bound to a PANA session
> 
> -When  NAP and ISP have different authorization lifetimes, the smaller one
> relates to the Session-Lifetime
> 
> -When EAP re-authentication occurs, both NAP and ISP authentications will
> be performed.
> 
> I would like to propose the following text to be added at the end of
> section 4.9:
> 
> "When separate EAP authentications are performed for ISP and NAP in a
> single PANA session, it is possible that different authorization lifetime
> values are associated with the two authentications. In this case, the
> smaller authorization lifetime value MUST be used for calculating the PANA
> Session-Lifetime value. As a result, when EAP-based re-authentication
> occurs, both NAP and ISP authentications will be performed in the same
> re-authentication procedure."
> 
> The issue is described in
> http://www.danforsberg.info:8080/pana-issues/issue34.
> 
> Comments are appreciated.

This makes sense to me.

Alper



> 
> 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 Dec  8 18:41:15 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13107
	for <pana-archive@odin.ietf.org>; Mon, 8 Dec 2003 18:41:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUzv-000420-7S
	for pana-archive@odin.ietf.org; Mon, 08 Dec 2003 18:41:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8Nf3k1015489
	for pana-archive@odin.ietf.org; Mon, 8 Dec 2003 18:41:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUzv-00041i-06
	for pana-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 18:41: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 SAA13041
	for <pana-web-archive@ietf.org>; Mon, 8 Dec 2003 18:40:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUzr-0001sB-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 18:40:59 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUzr-0001s7-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 18:40:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUzt-0003yb-FU; Mon, 08 Dec 2003 18:41:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATUzT-0003xX-BM
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 18:40:35 -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 SAA12974
	for <pana@ietf.org>; Mon, 8 Dec 2003 18:40:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATUzQ-0001rh-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:40:32 -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 1ATUzP-0001re-00
	for pana@ietf.org; Mon, 08 Dec 2003 18:40:31 -0500
Date: Mon, 08 Dec 2003 15:41:52 -0800
Subject: Re: [Pana] Issue34: Behaviour with NAP and ISP (two EAP
	authentications)
From: Alper Yegin <alper@docomolabs-usa.com>
To: <Yoshihiro.Ohba@tais.com>, <pana@ietf.org>
Message-ID: <BBFA4C40.E76F%alper@docomolabs-usa.com>
In-Reply-To: <OF0D15AF05.800AB2CE-ON88256DF0.007DA42A@tais.net>
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 IETF58 PANA meeting, the following resolution was proposed:
> 
> 
> -A single Session-Lifetime is bound to a PANA session
> 
> -When  NAP and ISP have different authorization lifetimes, the smaller one
> relates to the Session-Lifetime
> 
> -When EAP re-authentication occurs, both NAP and ISP authentications will
> be performed.
> 
> I would like to propose the following text to be added at the end of
> section 4.9:
> 
> "When separate EAP authentications are performed for ISP and NAP in a
> single PANA session, it is possible that different authorization lifetime
> values are associated with the two authentications. In this case, the
> smaller authorization lifetime value MUST be used for calculating the PANA
> Session-Lifetime value. As a result, when EAP-based re-authentication
> occurs, both NAP and ISP authentications will be performed in the same
> re-authentication procedure."
> 
> The issue is described in
> http://www.danforsberg.info:8080/pana-issues/issue34.
> 
> Comments are appreciated.

This makes sense to me.

Alper



> 
> 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 Dec  8 19:43:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16066
	for <pana-archive@lists.ietf.org>; Mon, 8 Dec 2003 19:43:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATVxs-0006U7-Lk; Mon, 08 Dec 2003 19:43:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATVxi-0006Tr-W2
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 19:42:51 -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 TAA16049
	for <pana@ietf.org>; Mon, 8 Dec 2003 19:42:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATVxX-00034r-00
	for pana@ietf.org; Mon, 08 Dec 2003 19:42:39 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATVx7-00033j-00
	for pana@ietf.org; Mon, 08 Dec 2003 19:42:13 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB90cpY9010988;
	Tue, 9 Dec 2003 09:38:51 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB90cpRs013089;
	Tue, 9 Dec 2003 09:38:51 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id KAA13088 ; Tue, 9 Dec 2003 09:38:50 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA11647; Tue, 9 Dec 2003 09:38:50 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA15127; Tue, 9 Dec 2003 09:38:49 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB90cm6b011436;
	Tue, 9 Dec 2003 09:38:49 +0900 (JST)
Received: from steelhead ([159.119.168.123]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPL00HCBR4NVD@tsbpo1.po.toshiba.co.jp>; Tue,
 9 Dec 2003 09:38:48 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ATVtE-0001c0-00; Mon, 08 Dec 2003 16:38:12 -0800
Date: Mon, 08 Dec 2003 16:38:12 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue16: Multihoming support
In-reply-to: <BBFA4B94.E76C%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro.Ohba@tais.com, pana@ietf.org
Message-id: <20031209003812.GG27979@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@tais.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <OFD082057F.F9E5BD70-ON88256DF2.000437DF@tais.net>
 <BBFA4B94.E76C%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 Mon, Dec 08, 2003 at 03:39:00PM -0800, Alper Yegin wrote:
> > To:
> > 
> > "  PANA Session:
> >     PANA session is defined as the exchange of messages between the PANA
> >     Client (PaC) and the PANA Authentication Agent (PAA) to authenticate
> >     a user (PaC) for network access. If the authentication is
> >     unsuccessful, the session is terminated. The session is considered as
> >     active until there is a disconnect indication by the PaC or the PAA
> >     terminates it. A distinct PANA session is associated with a pair of
> >     device identifiers of PaC and PAA. For example, if the PaC has two
> >     interfaces connected to the same IP link with different IP addresses
> >     and IP address is used as a device identifer, a distinct PANA session
> >     will be created per interface if both interfaces addresses need to be
> >     authorized for network access."
> 
> I think the last part is not clear enough. What we really mean is each
> *physical* interface needs to use separate PANA sessions to access the
> network. Logical interfaces with different IP addresses might still be bound
> to the same physical interface and hence not require separate PANA
> instances.

I think it depends on the routing context where PANA is performed.
When PANA runs over the routing context of the physical interface
only, I agree that separate PANA sessions are not needed for the
logical interfaces.  But when PANA runs over the routing context of
logical interface (additional PANA may or may not be running over the
routing context of the physical interface), I think separate PANA
sessions might be needed.

> 
> I think the second half starting from "A distinct PANA session..." can be
> replaced by:
> 
>     A distinct PANA session needs to be associated with each physical
>     interface of a PaC. A PaC can maintain multiple PANA sessions at the
>     same time, one for each interface that is authorized to access the
>     network. 

Does a PaC need to maintain multiple PANA sessions in this case even
when those physical interfaces share the same device identifier?

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  Mon Dec  8 19:50:14 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16425
	for <pana-archive@odin.ietf.org>; Mon, 8 Dec 2003 19:50:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATW4c-0006mD-8V
	for pana-archive@odin.ietf.org; Mon, 08 Dec 2003 19:49:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB90nwMq026043
	for pana-archive@odin.ietf.org; Mon, 8 Dec 2003 19:49:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATW4c-0006ly-3t
	for pana-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 19:49: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 TAA16295
	for <pana-web-archive@ietf.org>; Mon, 8 Dec 2003 19:49:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATW4a-0003Cb-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 19:49:56 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATW4Z-0003Bk-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 19:49:55 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1ATVyO-0001UG-JL
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 19:43:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATVxs-0006U7-Lk; Mon, 08 Dec 2003 19:43:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATVxi-0006Tr-W2
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 19:42:51 -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 TAA16049
	for <pana@ietf.org>; Mon, 8 Dec 2003 19:42:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATVxX-00034r-00
	for pana@ietf.org; Mon, 08 Dec 2003 19:42:39 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATVx7-00033j-00
	for pana@ietf.org; Mon, 08 Dec 2003 19:42:13 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB90cpY9010988;
	Tue, 9 Dec 2003 09:38:51 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB90cpRs013089;
	Tue, 9 Dec 2003 09:38:51 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id KAA13088 ; Tue, 9 Dec 2003 09:38:50 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA11647; Tue, 9 Dec 2003 09:38:50 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id JAA15127; Tue, 9 Dec 2003 09:38:49 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB90cm6b011436;
	Tue, 9 Dec 2003 09:38:49 +0900 (JST)
Received: from steelhead ([159.119.168.123]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPL00HCBR4NVD@tsbpo1.po.toshiba.co.jp>; Tue,
 9 Dec 2003 09:38:48 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ATVtE-0001c0-00; Mon, 08 Dec 2003 16:38:12 -0800
Date: Mon, 08 Dec 2003 16:38:12 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue16: Multihoming support
In-reply-to: <BBFA4B94.E76C%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro.Ohba@tais.com, pana@ietf.org
Message-id: <20031209003812.GG27979@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@tais.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <OFD082057F.F9E5BD70-ON88256DF2.000437DF@tais.net>
 <BBFA4B94.E76C%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 Mon, Dec 08, 2003 at 03:39:00PM -0800, Alper Yegin wrote:
> > To:
> > 
> > "  PANA Session:
> >     PANA session is defined as the exchange of messages between the PANA
> >     Client (PaC) and the PANA Authentication Agent (PAA) to authenticate
> >     a user (PaC) for network access. If the authentication is
> >     unsuccessful, the session is terminated. The session is considered as
> >     active until there is a disconnect indication by the PaC or the PAA
> >     terminates it. A distinct PANA session is associated with a pair of
> >     device identifiers of PaC and PAA. For example, if the PaC has two
> >     interfaces connected to the same IP link with different IP addresses
> >     and IP address is used as a device identifer, a distinct PANA session
> >     will be created per interface if both interfaces addresses need to be
> >     authorized for network access."
> 
> I think the last part is not clear enough. What we really mean is each
> *physical* interface needs to use separate PANA sessions to access the
> network. Logical interfaces with different IP addresses might still be bound
> to the same physical interface and hence not require separate PANA
> instances.

I think it depends on the routing context where PANA is performed.
When PANA runs over the routing context of the physical interface
only, I agree that separate PANA sessions are not needed for the
logical interfaces.  But when PANA runs over the routing context of
logical interface (additional PANA may or may not be running over the
routing context of the physical interface), I think separate PANA
sessions might be needed.

> 
> I think the second half starting from "A distinct PANA session..." can be
> replaced by:
> 
>     A distinct PANA session needs to be associated with each physical
>     interface of a PaC. A PaC can maintain multiple PANA sessions at the
>     same time, one for each interface that is authorized to access the
>     network. 

Does a PaC need to maintain multiple PANA sessions in this case even
when those physical interfaces share the same device identifier?

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  Mon Dec  8 21:52:16 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21853
	for <pana-archive@lists.ietf.org>; Mon, 8 Dec 2003 21:52:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATXyh-000339-Tw; Mon, 08 Dec 2003 21:51:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATXyT-000324-2l
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 21:51:45 -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 VAA21772
	for <pana@ietf.org>; Mon, 8 Dec 2003 21:51:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATXyQ-0005UW-00
	for pana@ietf.org; Mon, 08 Dec 2003 21:51:42 -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 1ATXyP-0005UT-00
	for pana@ietf.org; Mon, 08 Dec 2003 21:51:41 -0500
Date: Mon, 08 Dec 2003 18:53:03 -0800
Subject: Re: [Pana] Issue16: Multihoming support
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Yoshihiro.Ohba@tais.com>, <pana@ietf.org>
Message-ID: <BBFA790F.E7A5%alper@docomolabs-usa.com>
In-Reply-To: <20031209003812.GG27979@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 the last part is not clear enough. What we really mean is each
>> *physical* interface needs to use separate PANA sessions to access the
>> network. Logical interfaces with different IP addresses might still be bound
>> to the same physical interface and hence not require separate PANA
>> instances.
> 
> I think it depends on the routing context where PANA is performed.
> When PANA runs over the routing context of the physical interface
> only, I agree that separate PANA sessions are not needed for the
> logical interfaces.  But when PANA runs over the routing context of
> logical interface (additional PANA may or may not be running over the
> routing context of the physical interface), I think separate PANA
> sessions might be needed.

Agreed. 

> 
>> 
>> I think the second half starting from "A distinct PANA session..." can be
>> replaced by:
>> 
>>     A distinct PANA session needs to be associated with each physical
>>     interface of a PaC. A PaC can maintain multiple PANA sessions at the
>>     same time, one for each interface that is authorized to access the
>>     network. 
> 
> Does a PaC need to maintain multiple PANA sessions in this case even
> when those physical interfaces share the same device identifier?

Like two interfaces (that are connected to separate links) sharing the same
MAC address or IP address? Regardless, PaC should have two separate PANA
sessions. 

Alper


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


From exim@www1.ietf.org  Mon Dec  8 21:52:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21868
	for <pana-archive@odin.ietf.org>; Mon, 8 Dec 2003 21:52: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 1ATXyl-000346-OW
	for pana-archive@odin.ietf.org; Mon, 08 Dec 2003 21:52:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB92q3Wa011776
	for pana-archive@odin.ietf.org; Mon, 8 Dec 2003 21:52:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATXyl-00033r-De
	for pana-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 21:52: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 VAA21819
	for <pana-web-archive@ietf.org>; Mon, 8 Dec 2003 21:51:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATXyi-0005VG-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 21:52:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATXyi-0005VD-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 21:52:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATXyh-000339-Tw; Mon, 08 Dec 2003 21:51:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATXyT-000324-2l
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 21:51:45 -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 VAA21772
	for <pana@ietf.org>; Mon, 8 Dec 2003 21:51:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATXyQ-0005UW-00
	for pana@ietf.org; Mon, 08 Dec 2003 21:51:42 -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 1ATXyP-0005UT-00
	for pana@ietf.org; Mon, 08 Dec 2003 21:51:41 -0500
Date: Mon, 08 Dec 2003 18:53:03 -0800
Subject: Re: [Pana] Issue16: Multihoming support
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Yoshihiro.Ohba@tais.com>, <pana@ietf.org>
Message-ID: <BBFA790F.E7A5%alper@docomolabs-usa.com>
In-Reply-To: <20031209003812.GG27979@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 the last part is not clear enough. What we really mean is each
>> *physical* interface needs to use separate PANA sessions to access the
>> network. Logical interfaces with different IP addresses might still be bound
>> to the same physical interface and hence not require separate PANA
>> instances.
> 
> I think it depends on the routing context where PANA is performed.
> When PANA runs over the routing context of the physical interface
> only, I agree that separate PANA sessions are not needed for the
> logical interfaces.  But when PANA runs over the routing context of
> logical interface (additional PANA may or may not be running over the
> routing context of the physical interface), I think separate PANA
> sessions might be needed.

Agreed. 

> 
>> 
>> I think the second half starting from "A distinct PANA session..." can be
>> replaced by:
>> 
>>     A distinct PANA session needs to be associated with each physical
>>     interface of a PaC. A PaC can maintain multiple PANA sessions at the
>>     same time, one for each interface that is authorized to access the
>>     network. 
> 
> Does a PaC need to maintain multiple PANA sessions in this case even
> when those physical interfaces share the same device identifier?

Like two interfaces (that are connected to separate links) sharing the same
MAC address or IP address? Regardless, PaC should have two separate PANA
sessions. 

Alper


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



From pana-admin@ietf.org  Mon Dec  8 22:26:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23273
	for <pana-archive@lists.ietf.org>; Mon, 8 Dec 2003 22:26:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATYVe-0004Yg-LQ; Mon, 08 Dec 2003 22:26:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATYVM-0004Y7-MA
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 22:25:44 -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 WAA23215
	for <pana@ietf.org>; Mon, 8 Dec 2003 22:25:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYVJ-00069X-00
	for pana@ietf.org; Mon, 08 Dec 2003 22:25:41 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYVI-00069U-00
	for pana@ietf.org; Mon, 08 Dec 2003 22:25:40 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB93PXY9027560;
	Tue, 9 Dec 2003 12:25:35 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB93PXQJ024072;
	Tue, 9 Dec 2003 12:25:33 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id NAA24054 ; Tue, 9 Dec 2003 12:25:33 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id MAA23261; Tue, 9 Dec 2003 12:25:29 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id MAA26593; Tue, 9 Dec 2003 12:25:26 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB93PPTv025580;
	Tue, 9 Dec 2003 12:25:25 +0900 (JST)
Received: from steelhead ([159.119.168.123]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPL001KXYUBUW@tsbpo1.po.toshiba.co.jp>; Tue,
 9 Dec 2003 12:25:24 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ATYUF-0003Cp-00; Mon, 08 Dec 2003 19:24:35 -0800
Date: Mon, 08 Dec 2003 19:24:35 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue16: Multihoming support
In-reply-to: <BBFA790F.E7A5%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Yoshihiro.Ohba@tais.com,
        pana@ietf.org
Message-id: <20031209032435.GI27979@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>, Yoshihiro.Ohba@tais.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031209003812.GG27979@steelhead>
 <BBFA790F.E7A5%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 Mon, Dec 08, 2003 at 06:53:03PM -0800, Alper Yegin wrote:
> >> I think the second half starting from "A distinct PANA session..." can be
> >> replaced by:
> >> 
> >>     A distinct PANA session needs to be associated with each physical
> >>     interface of a PaC. A PaC can maintain multiple PANA sessions at the
> >>     same time, one for each interface that is authorized to access the
> >>     network. 
> > 
> > Does a PaC need to maintain multiple PANA sessions in this case even
> > when those physical interfaces share the same device identifier?
> 
> Like two interfaces (that are connected to separate links) sharing the same
> MAC address or IP address? Regardless, PaC should have two separate PANA
> sessions. 

When two physical interfaces with sharing the same MAC address or IP
address are connected to the same IP link and the shared address is
used as the device identifier, should the PaC have two separate PANA
sessions?  I think it can share a PANA session in this particular
case.  I mean that the other layer's addresses that are not used as
device identifier may be different among the interfaces but the PAA
and EP does not care the difference since they are not used for access
control.  That is another reason for why I mentioned "pair of device
identifiers of PaC and PAA" in the proposed text.

Yoshihiro Ohba


> 
> Alper
> 

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


From exim@www1.ietf.org  Mon Dec  8 22:26:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23288
	for <pana-archive@odin.ietf.org>; Mon, 8 Dec 2003 22:26: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 1ATYVi-0004a8-Kj
	for pana-archive@odin.ietf.org; Mon, 08 Dec 2003 22:26:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB93Q6Uu017609
	for pana-archive@odin.ietf.org; Mon, 8 Dec 2003 22:26:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATYVi-0004Zw-Fe
	for pana-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 22:26: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 WAA23252
	for <pana-web-archive@ietf.org>; Mon, 8 Dec 2003 22:25:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYVf-0006A1-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 22:26:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYVe-00069y-00
	for pana-web-archive@ietf.org; Mon, 08 Dec 2003 22:26:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATYVe-0004Yg-LQ; Mon, 08 Dec 2003 22:26:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATYVM-0004Y7-MA
	for pana@optimus.ietf.org; Mon, 08 Dec 2003 22:25:44 -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 WAA23215
	for <pana@ietf.org>; Mon, 8 Dec 2003 22:25:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYVJ-00069X-00
	for pana@ietf.org; Mon, 08 Dec 2003 22:25:41 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYVI-00069U-00
	for pana@ietf.org; Mon, 08 Dec 2003 22:25:40 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB93PXY9027560;
	Tue, 9 Dec 2003 12:25:35 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB93PXQJ024072;
	Tue, 9 Dec 2003 12:25:33 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id NAA24054 ; Tue, 9 Dec 2003 12:25:33 +0900
Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id MAA23261; Tue, 9 Dec 2003 12:25:29 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id MAA26593; Tue, 9 Dec 2003 12:25:26 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB93PPTv025580;
	Tue, 9 Dec 2003 12:25:25 +0900 (JST)
Received: from steelhead ([159.119.168.123]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPL001KXYUBUW@tsbpo1.po.toshiba.co.jp>; Tue,
 9 Dec 2003 12:25:24 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ATYUF-0003Cp-00; Mon, 08 Dec 2003 19:24:35 -0800
Date: Mon, 08 Dec 2003 19:24:35 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue16: Multihoming support
In-reply-to: <BBFA790F.E7A5%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Yoshihiro.Ohba@tais.com,
        pana@ietf.org
Message-id: <20031209032435.GI27979@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>, Yoshihiro.Ohba@tais.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031209003812.GG27979@steelhead>
 <BBFA790F.E7A5%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 Mon, Dec 08, 2003 at 06:53:03PM -0800, Alper Yegin wrote:
> >> I think the second half starting from "A distinct PANA session..." can be
> >> replaced by:
> >> 
> >>     A distinct PANA session needs to be associated with each physical
> >>     interface of a PaC. A PaC can maintain multiple PANA sessions at the
> >>     same time, one for each interface that is authorized to access the
> >>     network. 
> > 
> > Does a PaC need to maintain multiple PANA sessions in this case even
> > when those physical interfaces share the same device identifier?
> 
> Like two interfaces (that are connected to separate links) sharing the same
> MAC address or IP address? Regardless, PaC should have two separate PANA
> sessions. 

When two physical interfaces with sharing the same MAC address or IP
address are connected to the same IP link and the shared address is
used as the device identifier, should the PaC have two separate PANA
sessions?  I think it can share a PANA session in this particular
case.  I mean that the other layer's addresses that are not used as
device identifier may be different among the interfaces but the PAA
and EP does not care the difference since they are not used for access
control.  That is another reason for why I mentioned "pair of device
identifiers of PaC and PAA" in the proposed text.

Yoshihiro Ohba


> 
> Alper
> 

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



From pana-admin@ietf.org  Tue Dec  9 13:50:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07486
	for <pana-archive@lists.ietf.org>; Tue, 9 Dec 2003 13:50:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATmvq-0002eL-1c; Tue, 09 Dec 2003 13:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATmvK-0002dj-NM
	for pana@optimus.ietf.org; Tue, 09 Dec 2003 13:49:31 -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 NAA07445
	for <pana@ietf.org>; Tue, 9 Dec 2003 13:49:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATmvI-0005Eg-00
	for pana@ietf.org; Tue, 09 Dec 2003 13:49:28 -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 1ATmvH-0005Ed-00
	for pana@ietf.org; Tue, 09 Dec 2003 13:49:27 -0500
Date: Tue, 09 Dec 2003 10:50:48 -0800
Subject: Re: [Pana] Issue16: Multihoming support
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Yoshihiro.Ohba@tais.com>, <pana@ietf.org>
Message-ID: <BBFB5988.E844%alper@docomolabs-usa.com>
In-Reply-To: <20031209032435.GI27979@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 the second half starting from "A distinct PANA session..." can be
>>>> replaced by:
>>>> 
>>>>     A distinct PANA session needs to be associated with each physical
>>>>     interface of a PaC. A PaC can maintain multiple PANA sessions at the
>>>>     same time, one for each interface that is authorized to access the
>>>>     network. 
>>> 
>>> Does a PaC need to maintain multiple PANA sessions in this case even
>>> when those physical interfaces share the same device identifier?
>> 
>> Like two interfaces (that are connected to separate links) sharing the same
>> MAC address or IP address? Regardless, PaC should have two separate PANA
>> sessions. 
> 
> When two physical interfaces with sharing the same MAC address or IP
> address are connected to the same IP link and the shared address is
> used as the device identifier, should the PaC have two separate PANA
> sessions?  

This is a scenario where you need some magic to make the link-layer and IP
work just to send/receive regular data packets. If these two interfaces will
appear as one to the link-layer or network-layer, than I think it should
appear as one to the PANA protocol as well. [details depend on your magic..]

But I don't think we need to get into these non-standard variations in the
PANA protocol specification... [a sanity check to make sure we are not
breaking them is useful though...]

> I think it can share a PANA session in this particular
> case.  I mean that the other layer's addresses that are not used as
> device identifier may be different among the interfaces but the PAA
> and EP does not care the difference since they are not used for access
> control.  That is another reason for why I mentioned "pair of device
> identifiers of PaC and PAA" in the proposed text.

Alper

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


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


From exim@www1.ietf.org  Tue Dec  9 13:50:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07501
	for <pana-archive@odin.ietf.org>; Tue, 9 Dec 2003 13:50: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 1ATmvt-0002fS-35
	for pana-archive@odin.ietf.org; Tue, 09 Dec 2003 13:50:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB9Io5sW010248
	for pana-archive@odin.ietf.org; Tue, 9 Dec 2003 13:50:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATmvs-0002fD-Up
	for pana-web-archive@optimus.ietf.org; Tue, 09 Dec 2003 13:50: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 NAA07474
	for <pana-web-archive@ietf.org>; Tue, 9 Dec 2003 13:49:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATmvq-0005F8-00
	for pana-web-archive@ietf.org; Tue, 09 Dec 2003 13:50:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATmvq-0005F5-00
	for pana-web-archive@ietf.org; Tue, 09 Dec 2003 13:50:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATmvq-0002eL-1c; Tue, 09 Dec 2003 13:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATmvK-0002dj-NM
	for pana@optimus.ietf.org; Tue, 09 Dec 2003 13:49:31 -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 NAA07445
	for <pana@ietf.org>; Tue, 9 Dec 2003 13:49:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATmvI-0005Eg-00
	for pana@ietf.org; Tue, 09 Dec 2003 13:49:28 -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 1ATmvH-0005Ed-00
	for pana@ietf.org; Tue, 09 Dec 2003 13:49:27 -0500
Date: Tue, 09 Dec 2003 10:50:48 -0800
Subject: Re: [Pana] Issue16: Multihoming support
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Yoshihiro.Ohba@tais.com>, <pana@ietf.org>
Message-ID: <BBFB5988.E844%alper@docomolabs-usa.com>
In-Reply-To: <20031209032435.GI27979@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 the second half starting from "A distinct PANA session..." can be
>>>> replaced by:
>>>> 
>>>>     A distinct PANA session needs to be associated with each physical
>>>>     interface of a PaC. A PaC can maintain multiple PANA sessions at the
>>>>     same time, one for each interface that is authorized to access the
>>>>     network. 
>>> 
>>> Does a PaC need to maintain multiple PANA sessions in this case even
>>> when those physical interfaces share the same device identifier?
>> 
>> Like two interfaces (that are connected to separate links) sharing the same
>> MAC address or IP address? Regardless, PaC should have two separate PANA
>> sessions. 
> 
> When two physical interfaces with sharing the same MAC address or IP
> address are connected to the same IP link and the shared address is
> used as the device identifier, should the PaC have two separate PANA
> sessions?  

This is a scenario where you need some magic to make the link-layer and IP
work just to send/receive regular data packets. If these two interfaces will
appear as one to the link-layer or network-layer, than I think it should
appear as one to the PANA protocol as well. [details depend on your magic..]

But I don't think we need to get into these non-standard variations in the
PANA protocol specification... [a sanity check to make sure we are not
breaking them is useful though...]

> I think it can share a PANA session in this particular
> case.  I mean that the other layer's addresses that are not used as
> device identifier may be different among the interfaces but the PAA
> and EP does not care the difference since they are not used for access
> control.  That is another reason for why I mentioned "pair of device
> identifiers of PaC and PAA" in the proposed text.

Alper

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


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



From pana-admin@ietf.org  Tue Dec  9 14:30:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09209
	for <pana-archive@lists.ietf.org>; Tue, 9 Dec 2003 14:30: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 1ATnYZ-00048B-3i; Tue, 09 Dec 2003 14:30:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATnYL-00046t-Mx
	for pana@optimus.ietf.org; Tue, 09 Dec 2003 14:29:49 -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 OAA09104
	for <pana@ietf.org>; Tue, 9 Dec 2003 14:29:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATnYJ-0005pD-00
	for pana@ietf.org; Tue, 09 Dec 2003 14:29:47 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATnYI-0005pA-00
	for pana@ietf.org; Tue, 09 Dec 2003 14:29:46 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB9JTgY9017391;
	Wed, 10 Dec 2003 04:29:42 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB9JTgqR010575;
	Wed, 10 Dec 2003 04:29:42 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA10574 ; Wed, 10 Dec 2003 04:29:41 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA03485; Wed, 10 Dec 2003 04:29:41 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA14759; Wed, 10 Dec 2003 04:29:40 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB9JTdwT028822;
	Wed, 10 Dec 2003 04:29:40 +0900 (JST)
Received: from steelhead ([159.119.168.123]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPN00G8G7HDW5@tsbpo1.po.toshiba.co.jp>; Wed,
 10 Dec 2003 04:29:38 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ATnX9-0004FP-00; Tue, 09 Dec 2003 11:28:35 -0800
Date: Tue, 09 Dec 2003 11:28:35 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue16: Multihoming support
In-reply-to: <BBFB5988.E844%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Yoshihiro.Ohba@tais.com,
        pana@ietf.org
Message-id: <20031209192835.GI13320@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>, Yoshihiro.Ohba@tais.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031209032435.GI27979@steelhead>
 <BBFB5988.E844%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, Dec 09, 2003 at 10:50:48AM -0800, Alper Yegin wrote:
> > 
> > When two physical interfaces with sharing the same MAC address or IP
> > address are connected to the same IP link and the shared address is
> > used as the device identifier, should the PaC have two separate PANA
> > sessions?  
> 
> This is a scenario where you need some magic to make the link-layer and IP
> work just to send/receive regular data packets. If these two interfaces will
> appear as one to the link-layer or network-layer, than I think it should
> appear as one to the PANA protocol as well. [details depend on your magic..]

Right.

> 
> But I don't think we need to get into these non-standard variations in the
> PANA protocol specification... [a sanity check to make sure we are not
> breaking them is useful though...]

Of cource introducing non-standard variation was not my intention. I
just thought that defining a PANA session based on a pair of device
identifiers is sufficient since it covers all standard variations
regardless of which layer's device identifier is used and how the
device identifers are assigned to (physical or logical) interfaces.

Yoshihiro Ohba


> 
> > I think it can share a PANA session in this particular
> > case.  I mean that the other layer's addresses that are not used as
> > device identifier may be different among the interfaces but the PAA
> > and EP does not care the difference since they are not used for access
> > control.  That is another reason for why I mentioned "pair of device
> > identifiers of PaC and PAA" in the proposed text.
> 
> Alper
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> >> 
> >> Alper
> >> 
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> > 
> 

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


From exim@www1.ietf.org  Tue Dec  9 14:30:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09227
	for <pana-archive@odin.ietf.org>; Tue, 9 Dec 2003 14:30: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 1ATnYe-00049x-NA
	for pana-archive@odin.ietf.org; Tue, 09 Dec 2003 14:30:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB9JU8uZ015989
	for pana-archive@odin.ietf.org; Tue, 9 Dec 2003 14:30:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATnYe-00049o-E7
	for pana-web-archive@optimus.ietf.org; Tue, 09 Dec 2003 14:30:08 -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 OAA09112
	for <pana-web-archive@ietf.org>; Tue, 9 Dec 2003 14:29:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATnYb-0005ps-00
	for pana-web-archive@ietf.org; Tue, 09 Dec 2003 14:30:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATnYb-0005pp-00
	for pana-web-archive@ietf.org; Tue, 09 Dec 2003 14:30:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATnYZ-00048B-3i; Tue, 09 Dec 2003 14:30:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATnYL-00046t-Mx
	for pana@optimus.ietf.org; Tue, 09 Dec 2003 14:29:49 -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 OAA09104
	for <pana@ietf.org>; Tue, 9 Dec 2003 14:29:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATnYJ-0005pD-00
	for pana@ietf.org; Tue, 09 Dec 2003 14:29:47 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATnYI-0005pA-00
	for pana@ietf.org; Tue, 09 Dec 2003 14:29:46 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hB9JTgY9017391;
	Wed, 10 Dec 2003 04:29:42 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hB9JTgqR010575;
	Wed, 10 Dec 2003 04:29:42 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA10574 ; Wed, 10 Dec 2003 04:29:41 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA03485; Wed, 10 Dec 2003 04:29:41 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA14759; Wed, 10 Dec 2003 04:29:40 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hB9JTdwT028822;
	Wed, 10 Dec 2003 04:29:40 +0900 (JST)
Received: from steelhead ([159.119.168.123]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPN00G8G7HDW5@tsbpo1.po.toshiba.co.jp>; Wed,
 10 Dec 2003 04:29:38 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1ATnX9-0004FP-00; Tue, 09 Dec 2003 11:28:35 -0800
Date: Tue, 09 Dec 2003 11:28:35 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Issue16: Multihoming support
In-reply-to: <BBFB5988.E844%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Yoshihiro.Ohba@tais.com,
        pana@ietf.org
Message-id: <20031209192835.GI13320@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>, Yoshihiro.Ohba@tais.com, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <20031209032435.GI27979@steelhead>
 <BBFB5988.E844%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, Dec 09, 2003 at 10:50:48AM -0800, Alper Yegin wrote:
> > 
> > When two physical interfaces with sharing the same MAC address or IP
> > address are connected to the same IP link and the shared address is
> > used as the device identifier, should the PaC have two separate PANA
> > sessions?  
> 
> This is a scenario where you need some magic to make the link-layer and IP
> work just to send/receive regular data packets. If these two interfaces will
> appear as one to the link-layer or network-layer, than I think it should
> appear as one to the PANA protocol as well. [details depend on your magic..]

Right.

> 
> But I don't think we need to get into these non-standard variations in the
> PANA protocol specification... [a sanity check to make sure we are not
> breaking them is useful though...]

Of cource introducing non-standard variation was not my intention. I
just thought that defining a PANA session based on a pair of device
identifiers is sufficient since it covers all standard variations
regardless of which layer's device identifier is used and how the
device identifers are assigned to (physical or logical) interfaces.

Yoshihiro Ohba


> 
> > I think it can share a PANA session in this particular
> > case.  I mean that the other layer's addresses that are not used as
> > device identifier may be different among the interfaces but the PAA
> > and EP does not care the difference since they are not used for access
> > control.  That is another reason for why I mentioned "pair of device
> > identifiers of PaC and PAA" in the proposed text.
> 
> Alper
> 
> > 
> > Yoshihiro Ohba
> > 
> > 
> >> 
> >> Alper
> >> 
> > 
> > _______________________________________________
> > Pana mailing list
> > Pana@ietf.org
> > https://www1.ietf.org/mailman/listinfo/pana
> > 
> 

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



From pana-admin@ietf.org  Fri Dec 12 08:12:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07444
	for <pana-archive@lists.ietf.org>; Fri, 12 Dec 2003 08:12:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUn5M-0001Py-V4; Fri, 12 Dec 2003 08:12:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUn5G-0001PS-H1
	for pana@optimus.ietf.org; Fri, 12 Dec 2003 08:11:54 -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 IAA07363
	for <pana@ietf.org>; Fri, 12 Dec 2003 08:11:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUn5F-0004EQ-00
	for pana@ietf.org; Fri, 12 Dec 2003 08:11:53 -0500
Received: from na5.alcatel.fr ([194.133.58.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUn5E-0004Dm-00
	for pana@ietf.org; Fri, 12 Dec 2003 08:11:52 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hBCDAd7G001019;
	Fri, 12 Dec 2003 14:11:03 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003121214104811:3792 ;
          Fri, 12 Dec 2003 14:10:48 +0100 
Message-ID: <3FD9BE57.2000305@alcatel.fr>
Date: Fri, 12 Dec 2003 14:10:47 +0100
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Alper Yegin <aeyegin@hotmail.com>, pana@ietf.org,
        lionel.morand@francetelecom.com, yohba@tari.toshiba.com,
        Julien.Bournelle@int-evry.fr
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol	requirements)
References: <BBF34F8E.E283%alper@docomolabs-usa.com>
In-Reply-To: <BBF34F8E.E283%alper@docomolabs-usa.com>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/12/2003 14:10:48,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/12/2003 14:11:03,
	Serialize complete at 12/12/2003 14:11:03
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Alcanet-MTA-scanned-and-authorized: yes
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 all,

does the working group foresee deployment scenarios where we have 
multiple PAAs in the same IP subnet ?

thanks,
Yacine



Alper Yegin wrote:

>>my understanding is the following:
>>
>>PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
>>For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
>>configuring the concerned EPs. depending on the topology, there could be
>>more than one.
>>
>>does it look correct ?
> 
> 
> Yes. This is what I'm thinking.
> 
> 
>>>>* inter-PAAs communication ?
>>>
>>>
>>>Why do we need this for?
>>
>>for exemple: context transfer between PAAs for mobility handling (in
>>order to avoid re-authentication, which would reduce the handover perf).
>>this is strongly dependent of the relation between PAA and EPs discussed
>>above.
> 
> 
> I cannot see the relation. I think changing PAAs due to mobility and
> enabling fast reauthentication via context transfers is orthogonal to the
> PAA2EP protocol.
> 
> Alper
>  
> 
> 
> 
> 
>>>Alper
>>
>>Yacine
>>
>>
>>>>etc...
>>>>
>>>>comments on these "issues" are warmly welcome !
>>>>
>>>>
>>>>
>>>>
>>>>>>c) Accounting/Feedback from the EPs:
>>>>>>The PAA must have an efficient way to to get the accounting
>>
>>information
>>
>>>>>>of PaC from EP since the PAA may be a client of the AAA backend
>>>>>>infrastructure.
>>>>>
>>>>>
>>>>>Getting statistics from the EP makes sense. For example, in the
>>
>>case of
>>
>>>>>SNMP, if we get the counters from the EP this is good enough. The
>>>>
>>>>AAA client
>>>>
>>>>>sitting on the PAA can turn these into accoutning records.
>>>>
>>>>should the PAA poll the EPs to get these counters when needed (the
>>>>SNMP way...) or the EPs are supposed to send them periodically ?
>>>>
>>>>anyway, this should be somehow a requirement.
>>>>
>>>>
>>>>
>>>>>Alper
>>>>>
>>>>
>>>>thanks,
>>>>yacine
>>>>
>>>>
>>>>>>d) ????
>>>>>>
>>>>>>
>>>>>>thanks,
>>>>>>Yacine El Mghazli
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>_______________________________________________
>>>>>>Pana mailing 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
>>>
>>>
>>>_________________________________________________________________
>>>Set yourself up for fun at home!  Get tips on home entertainment
>>>equipment, video game reviews, and more here.
>>>http://special.msn.com/home/homeent.armx
>>>
>>>
>>
>>
>>
>>
> 
> 



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


From exim@www1.ietf.org  Fri Dec 12 08:12:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07463
	for <pana-archive@odin.ietf.org>; Fri, 12 Dec 2003 08:12:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUn5Q-0001Qe-4w
	for pana-archive@odin.ietf.org; Fri, 12 Dec 2003 08:12:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCDC40f005488
	for pana-archive@odin.ietf.org; Fri, 12 Dec 2003 08:12:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUn5P-0001QR-Ux
	for pana-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 08:12: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 IAA07389
	for <pana-web-archive@ietf.org>; Fri, 12 Dec 2003 08:12:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUn5P-0004Fj-00
	for pana-web-archive@ietf.org; Fri, 12 Dec 2003 08:12:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUn5O-0004Ff-00
	for pana-web-archive@ietf.org; Fri, 12 Dec 2003 08:12:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUn5M-0001Py-V4; Fri, 12 Dec 2003 08:12:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUn5G-0001PS-H1
	for pana@optimus.ietf.org; Fri, 12 Dec 2003 08:11:54 -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 IAA07363
	for <pana@ietf.org>; Fri, 12 Dec 2003 08:11:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUn5F-0004EQ-00
	for pana@ietf.org; Fri, 12 Dec 2003 08:11:53 -0500
Received: from na5.alcatel.fr ([194.133.58.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUn5E-0004Dm-00
	for pana@ietf.org; Fri, 12 Dec 2003 08:11:52 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hBCDAd7G001019;
	Fri, 12 Dec 2003 14:11:03 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003121214104811:3792 ;
          Fri, 12 Dec 2003 14:10:48 +0100 
Message-ID: <3FD9BE57.2000305@alcatel.fr>
Date: Fri, 12 Dec 2003 14:10:47 +0100
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Alper Yegin <aeyegin@hotmail.com>, pana@ietf.org,
        lionel.morand@francetelecom.com, yohba@tari.toshiba.com,
        Julien.Bournelle@int-evry.fr
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol	requirements)
References: <BBF34F8E.E283%alper@docomolabs-usa.com>
In-Reply-To: <BBF34F8E.E283%alper@docomolabs-usa.com>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/12/2003 14:10:48,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/12/2003 14:11:03,
	Serialize complete at 12/12/2003 14:11:03
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Alcanet-MTA-scanned-and-authorized: yes
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 all,

does the working group foresee deployment scenarios where we have 
multiple PAAs in the same IP subnet ?

thanks,
Yacine



Alper Yegin wrote:

>>my understanding is the following:
>>
>>PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
>>For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
>>configuring the concerned EPs. depending on the topology, there could be
>>more than one.
>>
>>does it look correct ?
> 
> 
> Yes. This is what I'm thinking.
> 
> 
>>>>* inter-PAAs communication ?
>>>
>>>
>>>Why do we need this for?
>>
>>for exemple: context transfer between PAAs for mobility handling (in
>>order to avoid re-authentication, which would reduce the handover perf).
>>this is strongly dependent of the relation between PAA and EPs discussed
>>above.
> 
> 
> I cannot see the relation. I think changing PAAs due to mobility and
> enabling fast reauthentication via context transfers is orthogonal to the
> PAA2EP protocol.
> 
> Alper
>  
> 
> 
> 
> 
>>>Alper
>>
>>Yacine
>>
>>
>>>>etc...
>>>>
>>>>comments on these "issues" are warmly welcome !
>>>>
>>>>
>>>>
>>>>
>>>>>>c) Accounting/Feedback from the EPs:
>>>>>>The PAA must have an efficient way to to get the accounting
>>
>>information
>>
>>>>>>of PaC from EP since the PAA may be a client of the AAA backend
>>>>>>infrastructure.
>>>>>
>>>>>
>>>>>Getting statistics from the EP makes sense. For example, in the
>>
>>case of
>>
>>>>>SNMP, if we get the counters from the EP this is good enough. The
>>>>
>>>>AAA client
>>>>
>>>>>sitting on the PAA can turn these into accoutning records.
>>>>
>>>>should the PAA poll the EPs to get these counters when needed (the
>>>>SNMP way...) or the EPs are supposed to send them periodically ?
>>>>
>>>>anyway, this should be somehow a requirement.
>>>>
>>>>
>>>>
>>>>>Alper
>>>>>
>>>>
>>>>thanks,
>>>>yacine
>>>>
>>>>
>>>>>>d) ????
>>>>>>
>>>>>>
>>>>>>thanks,
>>>>>>Yacine El Mghazli
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>_______________________________________________
>>>>>>Pana mailing 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
>>>
>>>
>>>_________________________________________________________________
>>>Set yourself up for fun at home!  Get tips on home entertainment
>>>equipment, video game reviews, and more here.
>>>http://special.msn.com/home/homeent.armx
>>>
>>>
>>
>>
>>
>>
> 
> 



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



From pana-admin@ietf.org  Fri Dec 12 14:01:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20203
	for <pana-archive@lists.ietf.org>; Fri, 12 Dec 2003 14:01:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsX8-0001eA-DL; Fri, 12 Dec 2003 14:01:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsWq-0001dD-7b
	for pana@optimus.ietf.org; Fri, 12 Dec 2003 14:00:44 -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 OAA20153
	for <pana@ietf.org>; Fri, 12 Dec 2003 14:00:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsWn-000494-00
	for pana@ietf.org; Fri, 12 Dec 2003 14:00:41 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsWn-000490-00
	for pana@ietf.org; Fri, 12 Dec 2003 14:00:41 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBCJ0NY9025496;
	Sat, 13 Dec 2003 04:00:23 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBCJ0N2G003343;
	Sat, 13 Dec 2003 04:00:23 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA03341 ; Sat, 13 Dec 2003 04:00:22 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA28537; Sat, 13 Dec 2003 04:00:22 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA07939; Sat, 13 Dec 2003 04:00:21 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hBCJ0KwT014959;
	Sat, 13 Dec 2003 04:00:21 +0900 (JST)
Received: from steelhead ([159.119.168.194]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPS00M3AQ4I21@tsbpo1.po.toshiba.co.jp>; Sat,
 13 Dec 2003 04:00:19 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AUk9d-0003xL-00; Fri, 12 Dec 2003 02:04:13 -0800
Date: Fri, 12 Dec 2003 02:04:13 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol
 requirements)
In-reply-to: <3FD9BE57.2000305@alcatel.fr>
To: Yacine.El_Mghazli@alcatel.fr
Cc: Alper Yegin <alper@docomolabs-usa.com>, Alper Yegin <aeyegin@hotmail.com>,
        pana@ietf.org, lionel.morand@francetelecom.com, yohba@tari.toshiba.com,
        Julien.Bournelle@int-evry.fr
Message-id: <20031212100413.GF30546@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Yacine.El_Mghazli@alcatel.fr,
 Alper Yegin <alper@docomolabs-usa.com>, Alper Yegin <aeyegin@hotmail.com>,
 pana@ietf.org, lionel.morand@francetelecom.com, yohba@tari.toshiba.com,
 Julien.Bournelle@int-evry.fr
User-Agent: Mutt/1.5.4i
References: <BBF34F8E.E283%alper@docomolabs-usa.com>
 <3FD9BE57.2000305@alcatel.fr>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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 think multiple PAAs in the same IP subnet will be important when
realizing a network selection over a shared medium without depending
on L2-based selection techniques such as PPPoE discovery.  Of cource,
more work would be needed for establishing an appropriate routing
context and assigning an IP address for use of a selected network.

Yoshihiro Ohba


On Fri, Dec 12, 2003 at 02:10:47PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> hi all,
> 
> does the working group foresee deployment scenarios where we have 
> multiple PAAs in the same IP subnet ?
> 
> thanks,
> Yacine
> 
> 
> 
> Alper Yegin wrote:
> 
> >>my understanding is the following:
> >>
> >>PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
> >>For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
> >>configuring the concerned EPs. depending on the topology, there could be
> >>more than one.
> >>
> >>does it look correct ?
> >
> >
> >Yes. This is what I'm thinking.
> >
> >
> >>>>* inter-PAAs communication ?
> >>>
> >>>
> >>>Why do we need this for?
> >>
> >>for exemple: context transfer between PAAs for mobility handling (in
> >>order to avoid re-authentication, which would reduce the handover perf).
> >>this is strongly dependent of the relation between PAA and EPs discussed
> >>above.
> >
> >
> >I cannot see the relation. I think changing PAAs due to mobility and
> >enabling fast reauthentication via context transfers is orthogonal to the
> >PAA2EP protocol.
> >
> >Alper
> > 
> >
> >
> >
> >
> >>>Alper
> >>
> >>Yacine
> >>
> >>
> >>>>etc...
> >>>>
> >>>>comments on these "issues" are warmly welcome !
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>>c) Accounting/Feedback from the EPs:
> >>>>>>The PAA must have an efficient way to to get the accounting
> >>
> >>information
> >>
> >>>>>>of PaC from EP since the PAA may be a client of the AAA backend
> >>>>>>infrastructure.
> >>>>>
> >>>>>
> >>>>>Getting statistics from the EP makes sense. For example, in the
> >>
> >>case of
> >>
> >>>>>SNMP, if we get the counters from the EP this is good enough. The
> >>>>
> >>>>AAA client
> >>>>
> >>>>>sitting on the PAA can turn these into accoutning records.
> >>>>
> >>>>should the PAA poll the EPs to get these counters when needed (the
> >>>>SNMP way...) or the EPs are supposed to send them periodically ?
> >>>>
> >>>>anyway, this should be somehow a requirement.
> >>>>
> >>>>
> >>>>
> >>>>>Alper
> >>>>>
> >>>>
> >>>>thanks,
> >>>>yacine
> >>>>
> >>>>
> >>>>>>d) ????
> >>>>>>
> >>>>>>
> >>>>>>thanks,
> >>>>>>Yacine El Mghazli
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>_______________________________________________
> >>>>>>Pana mailing 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
> >>>
> >>>
> >>>_________________________________________________________________
> >>>Set yourself up for fun at home!  Get tips on home entertainment
> >>>equipment, video game reviews, and more here.
> >>>http://special.msn.com/home/homeent.armx
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
> >
> 
> 

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


From exim@www1.ietf.org  Fri Dec 12 14:01:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20231
	for <pana-archive@odin.ietf.org>; Fri, 12 Dec 2003 14:01:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsXC-0001gN-VQ
	for pana-archive@odin.ietf.org; Fri, 12 Dec 2003 14:01:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCJ16J6006466
	for pana-archive@odin.ietf.org; Fri, 12 Dec 2003 14: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 1AUsXC-0001gD-Ph
	for pana-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 14: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 OAA20176
	for <pana-web-archive@ietf.org>; Fri, 12 Dec 2003 14:01:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsXA-00049v-00
	for pana-web-archive@ietf.org; Fri, 12 Dec 2003 14:01:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsXA-00049s-00
	for pana-web-archive@ietf.org; Fri, 12 Dec 2003 14:01:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsX8-0001eA-DL; Fri, 12 Dec 2003 14:01:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsWq-0001dD-7b
	for pana@optimus.ietf.org; Fri, 12 Dec 2003 14:00:44 -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 OAA20153
	for <pana@ietf.org>; Fri, 12 Dec 2003 14:00:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsWn-000494-00
	for pana@ietf.org; Fri, 12 Dec 2003 14:00:41 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsWn-000490-00
	for pana@ietf.org; Fri, 12 Dec 2003 14:00:41 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBCJ0NY9025496;
	Sat, 13 Dec 2003 04:00:23 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBCJ0N2G003343;
	Sat, 13 Dec 2003 04:00:23 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id EAA03341 ; Sat, 13 Dec 2003 04:00:22 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id EAA28537; Sat, 13 Dec 2003 04:00:22 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id EAA07939; Sat, 13 Dec 2003 04:00:21 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hBCJ0KwT014959;
	Sat, 13 Dec 2003 04:00:21 +0900 (JST)
Received: from steelhead ([159.119.168.194]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HPS00M3AQ4I21@tsbpo1.po.toshiba.co.jp>; Sat,
 13 Dec 2003 04:00:19 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AUk9d-0003xL-00; Fri, 12 Dec 2003 02:04:13 -0800
Date: Fri, 12 Dec 2003 02:04:13 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol
 requirements)
In-reply-to: <3FD9BE57.2000305@alcatel.fr>
To: Yacine.El_Mghazli@alcatel.fr
Cc: Alper Yegin <alper@docomolabs-usa.com>, Alper Yegin <aeyegin@hotmail.com>,
        pana@ietf.org, lionel.morand@francetelecom.com, yohba@tari.toshiba.com,
        Julien.Bournelle@int-evry.fr
Message-id: <20031212100413.GF30546@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Yacine.El_Mghazli@alcatel.fr,
 Alper Yegin <alper@docomolabs-usa.com>, Alper Yegin <aeyegin@hotmail.com>,
 pana@ietf.org, lionel.morand@francetelecom.com, yohba@tari.toshiba.com,
 Julien.Bournelle@int-evry.fr
User-Agent: Mutt/1.5.4i
References: <BBF34F8E.E283%alper@docomolabs-usa.com>
 <3FD9BE57.2000305@alcatel.fr>
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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 think multiple PAAs in the same IP subnet will be important when
realizing a network selection over a shared medium without depending
on L2-based selection techniques such as PPPoE discovery.  Of cource,
more work would be needed for establishing an appropriate routing
context and assigning an IP address for use of a selected network.

Yoshihiro Ohba


On Fri, Dec 12, 2003 at 02:10:47PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> hi all,
> 
> does the working group foresee deployment scenarios where we have 
> multiple PAAs in the same IP subnet ?
> 
> thanks,
> Yacine
> 
> 
> 
> Alper Yegin wrote:
> 
> >>my understanding is the following:
> >>
> >>PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
> >>For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
> >>configuring the concerned EPs. depending on the topology, there could be
> >>more than one.
> >>
> >>does it look correct ?
> >
> >
> >Yes. This is what I'm thinking.
> >
> >
> >>>>* inter-PAAs communication ?
> >>>
> >>>
> >>>Why do we need this for?
> >>
> >>for exemple: context transfer between PAAs for mobility handling (in
> >>order to avoid re-authentication, which would reduce the handover perf).
> >>this is strongly dependent of the relation between PAA and EPs discussed
> >>above.
> >
> >
> >I cannot see the relation. I think changing PAAs due to mobility and
> >enabling fast reauthentication via context transfers is orthogonal to the
> >PAA2EP protocol.
> >
> >Alper
> > 
> >
> >
> >
> >
> >>>Alper
> >>
> >>Yacine
> >>
> >>
> >>>>etc...
> >>>>
> >>>>comments on these "issues" are warmly welcome !
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>>c) Accounting/Feedback from the EPs:
> >>>>>>The PAA must have an efficient way to to get the accounting
> >>
> >>information
> >>
> >>>>>>of PaC from EP since the PAA may be a client of the AAA backend
> >>>>>>infrastructure.
> >>>>>
> >>>>>
> >>>>>Getting statistics from the EP makes sense. For example, in the
> >>
> >>case of
> >>
> >>>>>SNMP, if we get the counters from the EP this is good enough. The
> >>>>
> >>>>AAA client
> >>>>
> >>>>>sitting on the PAA can turn these into accoutning records.
> >>>>
> >>>>should the PAA poll the EPs to get these counters when needed (the
> >>>>SNMP way...) or the EPs are supposed to send them periodically ?
> >>>>
> >>>>anyway, this should be somehow a requirement.
> >>>>
> >>>>
> >>>>
> >>>>>Alper
> >>>>>
> >>>>
> >>>>thanks,
> >>>>yacine
> >>>>
> >>>>
> >>>>>>d) ????
> >>>>>>
> >>>>>>
> >>>>>>thanks,
> >>>>>>Yacine El Mghazli
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>_______________________________________________
> >>>>>>Pana mailing 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
> >>>
> >>>
> >>>_________________________________________________________________
> >>>Set yourself up for fun at home!  Get tips on home entertainment
> >>>equipment, video game reviews, and more here.
> >>>http://special.msn.com/home/homeent.armx
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
> >
> 
> 

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



From pana-admin@ietf.org  Fri Dec 12 14:16:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20882
	for <pana-archive@lists.ietf.org>; Fri, 12 Dec 2003 14:16:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsle-0002QU-4o; Fri, 12 Dec 2003 14:16:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUslR-0002Q2-1q
	for pana@optimus.ietf.org; Fri, 12 Dec 2003 14:15:49 -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 OAA20853
	for <pana@ietf.org>; Fri, 12 Dec 2003 14:15:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUslO-0004eD-00
	for pana@ietf.org; Fri, 12 Dec 2003 14:15:46 -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 1AUslI-0004dY-00
	for pana@ietf.org; Fri, 12 Dec 2003 14:15:41 -0500
Date: Fri, 12 Dec 2003 11:16:29 -0800
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol
	requirements)
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <Yacine.El_Mghazli@alcatel.fr>
CC: <pana@ietf.org>, <lionel.morand@francetelecom.com>,
        <Julien.Bournelle@int-evry.fr>
Message-ID: <BBFF540D.EBDE%alper@docomolabs-usa.com>
In-Reply-To: <20031212100413.GF30546@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

Hi Yoshi,

I don't fully understand this scenario. Normally there is one physical
network, owned by one NAP. That NAP puts a PAA, and enables PaC select from
a set of ISPs. 

You seem to suggest multiple NAPs sharing the same physical access network.
I don't think this is a realistic scenario.

Alper



> I think multiple PAAs in the same IP subnet will be important when
> realizing a network selection over a shared medium without depending
> on L2-based selection techniques such as PPPoE discovery.  Of cource,
> more work would be needed for establishing an appropriate routing
> context and assigning an IP address for use of a selected network.
> 
> Yoshihiro Ohba
> 
> 
> On Fri, Dec 12, 2003 at 02:10:47PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
>> hi all,
>> 
>> does the working group foresee deployment scenarios where we have
>> multiple PAAs in the same IP subnet ?
>> 
>> thanks,
>> Yacine
>> 
>> 
>> 
>> Alper Yegin wrote:
>> 
>>>> my understanding is the following:
>>>> 
>>>> PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
>>>> For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
>>>> configuring the concerned EPs. depending on the topology, there could be
>>>> more than one.
>>>> 
>>>> does it look correct ?
>>> 
>>> 
>>> Yes. This is what I'm thinking.
>>> 
>>> 
>>>>>> * inter-PAAs communication ?
>>>>> 
>>>>> 
>>>>> Why do we need this for?
>>>> 
>>>> for exemple: context transfer between PAAs for mobility handling (in
>>>> order to avoid re-authentication, which would reduce the handover perf).
>>>> this is strongly dependent of the relation between PAA and EPs discussed
>>>> above.
>>> 
>>> 
>>> I cannot see the relation. I think changing PAAs due to mobility and
>>> enabling fast reauthentication via context transfers is orthogonal to the
>>> PAA2EP protocol.
>>> 
>>> Alper
>>> 
>>> 
>>> 
>>> 
>>> 
>>>>> Alper
>>>> 
>>>> Yacine
>>>> 
>>>> 
>>>>>> etc...
>>>>>> 
>>>>>> comments on these "issues" are warmly welcome !
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>>> c) Accounting/Feedback from the EPs:
>>>>>>>> The PAA must have an efficient way to to get the accounting
>>>> 
>>>> information
>>>> 
>>>>>>>> of PaC from EP since the PAA may be a client of the AAA backend
>>>>>>>> infrastructure.
>>>>>>> 
>>>>>>> 
>>>>>>> Getting statistics from the EP makes sense. For example, in the
>>>> 
>>>> case of
>>>> 
>>>>>>> SNMP, if we get the counters from the EP this is good enough. The
>>>>>> 
>>>>>> AAA client
>>>>>> 
>>>>>>> sitting on the PAA can turn these into accoutning records.
>>>>>> 
>>>>>> should the PAA poll the EPs to get these counters when needed (the
>>>>>> SNMP way...) or the EPs are supposed to send them periodically ?
>>>>>> 
>>>>>> anyway, this should be somehow a requirement.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> Alper
>>>>>>> 
>>>>>> 
>>>>>> thanks,
>>>>>> yacine
>>>>>> 
>>>>>> 
>>>>>>>> d) ????
>>>>>>>> 
>>>>>>>> 
>>>>>>>> thanks,
>>>>>>>> Yacine El Mghazli
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> Pana mailing 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
>>>>> 
>>>>> 
>>>>> _________________________________________________________________
>>>>> Set yourself up for fun at home!  Get tips on home entertainment
>>>>> equipment, video game reviews, and more here.
>>>>> http://special.msn.com/home/homeent.armx
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> _______________________________________________
> Pana mailing 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 Dec 12 14:16:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20898
	for <pana-archive@odin.ietf.org>; Fri, 12 Dec 2003 14:16:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUslh-0002RN-23
	for pana-archive@odin.ietf.org; Fri, 12 Dec 2003 14:16:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCJG5gD009375
	for pana-archive@odin.ietf.org; Fri, 12 Dec 2003 14:16:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUslg-0002R7-RD
	for pana-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 14: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 OAA20857
	for <pana-web-archive@ietf.org>; Fri, 12 Dec 2003 14:16:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsle-0004eu-00
	for pana-web-archive@ietf.org; Fri, 12 Dec 2003 14:16:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUsle-0004er-00
	for pana-web-archive@ietf.org; Fri, 12 Dec 2003 14:16:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUsle-0002QU-4o; Fri, 12 Dec 2003 14:16:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUslR-0002Q2-1q
	for pana@optimus.ietf.org; Fri, 12 Dec 2003 14:15:49 -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 OAA20853
	for <pana@ietf.org>; Fri, 12 Dec 2003 14:15:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUslO-0004eD-00
	for pana@ietf.org; Fri, 12 Dec 2003 14:15:46 -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 1AUslI-0004dY-00
	for pana@ietf.org; Fri, 12 Dec 2003 14:15:41 -0500
Date: Fri, 12 Dec 2003 11:16:29 -0800
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol
	requirements)
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, <Yacine.El_Mghazli@alcatel.fr>
CC: <pana@ietf.org>, <lionel.morand@francetelecom.com>,
        <Julien.Bournelle@int-evry.fr>
Message-ID: <BBFF540D.EBDE%alper@docomolabs-usa.com>
In-Reply-To: <20031212100413.GF30546@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

Hi Yoshi,

I don't fully understand this scenario. Normally there is one physical
network, owned by one NAP. That NAP puts a PAA, and enables PaC select from
a set of ISPs. 

You seem to suggest multiple NAPs sharing the same physical access network.
I don't think this is a realistic scenario.

Alper



> I think multiple PAAs in the same IP subnet will be important when
> realizing a network selection over a shared medium without depending
> on L2-based selection techniques such as PPPoE discovery.  Of cource,
> more work would be needed for establishing an appropriate routing
> context and assigning an IP address for use of a selected network.
> 
> Yoshihiro Ohba
> 
> 
> On Fri, Dec 12, 2003 at 02:10:47PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
>> hi all,
>> 
>> does the working group foresee deployment scenarios where we have
>> multiple PAAs in the same IP subnet ?
>> 
>> thanks,
>> Yacine
>> 
>> 
>> 
>> Alper Yegin wrote:
>> 
>>>> my understanding is the following:
>>>> 
>>>> PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
>>>> For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
>>>> configuring the concerned EPs. depending on the topology, there could be
>>>> more than one.
>>>> 
>>>> does it look correct ?
>>> 
>>> 
>>> Yes. This is what I'm thinking.
>>> 
>>> 
>>>>>> * inter-PAAs communication ?
>>>>> 
>>>>> 
>>>>> Why do we need this for?
>>>> 
>>>> for exemple: context transfer between PAAs for mobility handling (in
>>>> order to avoid re-authentication, which would reduce the handover perf).
>>>> this is strongly dependent of the relation between PAA and EPs discussed
>>>> above.
>>> 
>>> 
>>> I cannot see the relation. I think changing PAAs due to mobility and
>>> enabling fast reauthentication via context transfers is orthogonal to the
>>> PAA2EP protocol.
>>> 
>>> Alper
>>> 
>>> 
>>> 
>>> 
>>> 
>>>>> Alper
>>>> 
>>>> Yacine
>>>> 
>>>> 
>>>>>> etc...
>>>>>> 
>>>>>> comments on these "issues" are warmly welcome !
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>>> c) Accounting/Feedback from the EPs:
>>>>>>>> The PAA must have an efficient way to to get the accounting
>>>> 
>>>> information
>>>> 
>>>>>>>> of PaC from EP since the PAA may be a client of the AAA backend
>>>>>>>> infrastructure.
>>>>>>> 
>>>>>>> 
>>>>>>> Getting statistics from the EP makes sense. For example, in the
>>>> 
>>>> case of
>>>> 
>>>>>>> SNMP, if we get the counters from the EP this is good enough. The
>>>>>> 
>>>>>> AAA client
>>>>>> 
>>>>>>> sitting on the PAA can turn these into accoutning records.
>>>>>> 
>>>>>> should the PAA poll the EPs to get these counters when needed (the
>>>>>> SNMP way...) or the EPs are supposed to send them periodically ?
>>>>>> 
>>>>>> anyway, this should be somehow a requirement.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> Alper
>>>>>>> 
>>>>>> 
>>>>>> thanks,
>>>>>> yacine
>>>>>> 
>>>>>> 
>>>>>>>> d) ????
>>>>>>>> 
>>>>>>>> 
>>>>>>>> thanks,
>>>>>>>> Yacine El Mghazli
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> Pana mailing 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
>>>>> 
>>>>> 
>>>>> _________________________________________________________________
>>>>> Set yourself up for fun at home!  Get tips on home entertainment
>>>>> equipment, video game reviews, and more here.
>>>>> http://special.msn.com/home/homeent.armx
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
> 
> _______________________________________________
> Pana mailing 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 Dec 12 17:45:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00558
	for <pana-archive@lists.ietf.org>; Fri, 12 Dec 2003 17:45:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUw1u-0004wK-Sm; Fri, 12 Dec 2003 17: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 1AUw1A-0004qK-OS
	for pana@optimus.ietf.org; Fri, 12 Dec 2003 17:44:16 -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 RAA00516
	for <pana@ietf.org>; Fri, 12 Dec 2003 17:44:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUw18-0003Jc-00
	for pana@ietf.org; Fri, 12 Dec 2003 17:44:14 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUw17-0003JZ-00
	for pana@ietf.org; Fri, 12 Dec 2003 17:44:13 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBCMi2Y9025124;
	Sat, 13 Dec 2003 07:44:02 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBCMi2NI020514;
	Sat, 13 Dec 2003 07:44:02 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id HAA20512 ; Sat, 13 Dec 2003 07:44:02 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA24742; Sat, 13 Dec 2003 07:44:02 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA26482; Sat, 13 Dec 2003 07:44:01 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hBCMi0wT010063;
	Sat, 13 Dec 2003 07:44:00 +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 <0HPT003B60H94E@tsbpo1.po.toshiba.co.jp>; Sat,
 13 Dec 2003 07:43:59 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AUw0J-0004vN-00; Fri, 12 Dec 2003 14:43:23 -0800
Date: Fri, 12 Dec 2003 14:43:23 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol
 requirements)
In-reply-to: <BBFF540D.EBDE%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Yacine.El_Mghazli@alcatel.fr,
        pana@ietf.org, lionel.morand@francetelecom.com,
        Julien.Bournelle@int-evry.fr
Message-id: <20031212224323.GG30546@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>, Yacine.El_Mghazli@alcatel.fr,
 pana@ietf.org, lionel.morand@francetelecom.com, Julien.Bournelle@int-evry.fr
User-Agent: Mutt/1.5.4i
References: <20031212100413.GF30546@steelhead>
 <BBFF540D.EBDE%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, Dec 12, 2003 at 11:16:29AM -0800, Alper Yegin wrote:
> Hi Yoshi,
> 
> I don't fully understand this scenario. Normally there is one physical
> network, owned by one NAP. That NAP puts a PAA, and enables PaC select from
> a set of ISPs. 
> 
> You seem to suggest multiple NAPs sharing the same physical access network.
> I don't think this is a realistic scenario.

I did not actually think about multiple NAPs.  What I was thinking is
a model where there is only one NAP, but each PAA is owned by a
different ISP and performs only ISP authentication for the ISP. In
this case, the NAP just provides the ISPs the physical location to put
their PAAs and EPs, and no NAP authentication is performed.

Yoshihiro Ohba

> 
> Alper
> 
> 
> 
> > I think multiple PAAs in the same IP subnet will be important when
> > realizing a network selection over a shared medium without depending
> > on L2-based selection techniques such as PPPoE discovery.  Of cource,
> > more work would be needed for establishing an appropriate routing
> > context and assigning an IP address for use of a selected network.
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Fri, Dec 12, 2003 at 02:10:47PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> >> hi all,
> >> 
> >> does the working group foresee deployment scenarios where we have
> >> multiple PAAs in the same IP subnet ?
> >> 
> >> thanks,
> >> Yacine
> >> 
> >> 
> >> 
> >> Alper Yegin wrote:
> >> 
> >>>> my understanding is the following:
> >>>> 
> >>>> PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
> >>>> For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
> >>>> configuring the concerned EPs. depending on the topology, there could be
> >>>> more than one.
> >>>> 
> >>>> does it look correct ?
> >>> 
> >>> 
> >>> Yes. This is what I'm thinking.
> >>> 
> >>> 
> >>>>>> * inter-PAAs communication ?
> >>>>> 
> >>>>> 
> >>>>> Why do we need this for?
> >>>> 
> >>>> for exemple: context transfer between PAAs for mobility handling (in
> >>>> order to avoid re-authentication, which would reduce the handover perf).
> >>>> this is strongly dependent of the relation between PAA and EPs discussed
> >>>> above.
> >>> 
> >>> 
> >>> I cannot see the relation. I think changing PAAs due to mobility and
> >>> enabling fast reauthentication via context transfers is orthogonal to the
> >>> PAA2EP protocol.
> >>> 
> >>> Alper
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>>>> Alper
> >>>> 
> >>>> Yacine
> >>>> 
> >>>> 
> >>>>>> etc...
> >>>>>> 
> >>>>>> comments on these "issues" are warmly welcome !
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>>>>> c) Accounting/Feedback from the EPs:
> >>>>>>>> The PAA must have an efficient way to to get the accounting
> >>>> 
> >>>> information
> >>>> 
> >>>>>>>> of PaC from EP since the PAA may be a client of the AAA backend
> >>>>>>>> infrastructure.
> >>>>>>> 
> >>>>>>> 
> >>>>>>> Getting statistics from the EP makes sense. For example, in the
> >>>> 
> >>>> case of
> >>>> 
> >>>>>>> SNMP, if we get the counters from the EP this is good enough. The
> >>>>>> 
> >>>>>> AAA client
> >>>>>> 
> >>>>>>> sitting on the PAA can turn these into accoutning records.
> >>>>>> 
> >>>>>> should the PAA poll the EPs to get these counters when needed (the
> >>>>>> SNMP way...) or the EPs are supposed to send them periodically ?
> >>>>>> 
> >>>>>> anyway, this should be somehow a requirement.
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>>>> Alper
> >>>>>>> 
> >>>>>> 
> >>>>>> thanks,
> >>>>>> yacine
> >>>>>> 
> >>>>>> 
> >>>>>>>> d) ????
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> thanks,
> >>>>>>>> Yacine El Mghazli
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> _______________________________________________
> >>>>>>>> Pana mailing 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
> >>>>> 
> >>>>> 
> >>>>> _________________________________________________________________
> >>>>> Set yourself up for fun at home!  Get tips on home entertainment
> >>>>> equipment, video game reviews, and more here.
> >>>>> http://special.msn.com/home/homeent.armx
> >>>>> 
> >>>>> 
> >>>> 
> >>>> 
> >>>> 
> >>>> 
> >>> 
> >>> 
> >> 
> >> 
> > 
> > _______________________________________________
> > Pana mailing 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  Fri Dec 12 17:45:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00573
	for <pana-archive@odin.ietf.org>; Fri, 12 Dec 2003 17:45:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUw21-0004x8-0E
	for pana-archive@odin.ietf.org; Fri, 12 Dec 2003 17:45:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBCMj8cO019032
	for pana-archive@odin.ietf.org; Fri, 12 Dec 2003 17:45:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUw20-0004wt-Jx
	for pana-web-archive@optimus.ietf.org; Fri, 12 Dec 2003 17:45:08 -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 RAA00530
	for <pana-web-archive@ietf.org>; Fri, 12 Dec 2003 17:45:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUw1y-0003KR-00
	for pana-web-archive@ietf.org; Fri, 12 Dec 2003 17:45:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUw1x-0003KO-00
	for pana-web-archive@ietf.org; Fri, 12 Dec 2003 17:45:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AUw1u-0004wK-Sm; Fri, 12 Dec 2003 17: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 1AUw1A-0004qK-OS
	for pana@optimus.ietf.org; Fri, 12 Dec 2003 17:44:16 -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 RAA00516
	for <pana@ietf.org>; Fri, 12 Dec 2003 17:44:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUw18-0003Jc-00
	for pana@ietf.org; Fri, 12 Dec 2003 17:44:14 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AUw17-0003JZ-00
	for pana@ietf.org; Fri, 12 Dec 2003 17:44:13 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBCMi2Y9025124;
	Sat, 13 Dec 2003 07:44:02 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBCMi2NI020514;
	Sat, 13 Dec 2003 07:44:02 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id HAA20512 ; Sat, 13 Dec 2003 07:44:02 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id HAA24742; Sat, 13 Dec 2003 07:44:02 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id HAA26482; Sat, 13 Dec 2003 07:44:01 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hBCMi0wT010063;
	Sat, 13 Dec 2003 07:44:00 +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 <0HPT003B60H94E@tsbpo1.po.toshiba.co.jp>; Sat,
 13 Dec 2003 07:43:59 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AUw0J-0004vN-00; Fri, 12 Dec 2003 14:43:23 -0800
Date: Fri, 12 Dec 2003 14:43:23 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol
 requirements)
In-reply-to: <BBFF540D.EBDE%alper@docomolabs-usa.com>
To: Alper Yegin <alper@docomolabs-usa.com>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, Yacine.El_Mghazli@alcatel.fr,
        pana@ietf.org, lionel.morand@francetelecom.com,
        Julien.Bournelle@int-evry.fr
Message-id: <20031212224323.GG30546@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>, Yacine.El_Mghazli@alcatel.fr,
 pana@ietf.org, lionel.morand@francetelecom.com, Julien.Bournelle@int-evry.fr
User-Agent: Mutt/1.5.4i
References: <20031212100413.GF30546@steelhead>
 <BBFF540D.EBDE%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, Dec 12, 2003 at 11:16:29AM -0800, Alper Yegin wrote:
> Hi Yoshi,
> 
> I don't fully understand this scenario. Normally there is one physical
> network, owned by one NAP. That NAP puts a PAA, and enables PaC select from
> a set of ISPs. 
> 
> You seem to suggest multiple NAPs sharing the same physical access network.
> I don't think this is a realistic scenario.

I did not actually think about multiple NAPs.  What I was thinking is
a model where there is only one NAP, but each PAA is owned by a
different ISP and performs only ISP authentication for the ISP. In
this case, the NAP just provides the ISPs the physical location to put
their PAAs and EPs, and no NAP authentication is performed.

Yoshihiro Ohba

> 
> Alper
> 
> 
> 
> > I think multiple PAAs in the same IP subnet will be important when
> > realizing a network selection over a shared medium without depending
> > on L2-based selection techniques such as PPPoE discovery.  Of cource,
> > more work would be needed for establishing an appropriate routing
> > context and assigning an IP address for use of a selected network.
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Fri, Dec 12, 2003 at 02:10:47PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
> >> hi all,
> >> 
> >> does the working group foresee deployment scenarios where we have
> >> multiple PAAs in the same IP subnet ?
> >> 
> >> thanks,
> >> Yacine
> >> 
> >> 
> >> 
> >> Alper Yegin wrote:
> >> 
> >>>> my understanding is the following:
> >>>> 
> >>>> PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
> >>>> For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
> >>>> configuring the concerned EPs. depending on the topology, there could be
> >>>> more than one.
> >>>> 
> >>>> does it look correct ?
> >>> 
> >>> 
> >>> Yes. This is what I'm thinking.
> >>> 
> >>> 
> >>>>>> * inter-PAAs communication ?
> >>>>> 
> >>>>> 
> >>>>> Why do we need this for?
> >>>> 
> >>>> for exemple: context transfer between PAAs for mobility handling (in
> >>>> order to avoid re-authentication, which would reduce the handover perf).
> >>>> this is strongly dependent of the relation between PAA and EPs discussed
> >>>> above.
> >>> 
> >>> 
> >>> I cannot see the relation. I think changing PAAs due to mobility and
> >>> enabling fast reauthentication via context transfers is orthogonal to the
> >>> PAA2EP protocol.
> >>> 
> >>> Alper
> >>> 
> >>> 
> >>> 
> >>> 
> >>> 
> >>>>> Alper
> >>>> 
> >>>> Yacine
> >>>> 
> >>>> 
> >>>>>> etc...
> >>>>>> 
> >>>>>> comments on these "issues" are warmly welcome !
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>>>>> c) Accounting/Feedback from the EPs:
> >>>>>>>> The PAA must have an efficient way to to get the accounting
> >>>> 
> >>>> information
> >>>> 
> >>>>>>>> of PaC from EP since the PAA may be a client of the AAA backend
> >>>>>>>> infrastructure.
> >>>>>>> 
> >>>>>>> 
> >>>>>>> Getting statistics from the EP makes sense. For example, in the
> >>>> 
> >>>> case of
> >>>> 
> >>>>>>> SNMP, if we get the counters from the EP this is good enough. The
> >>>>>> 
> >>>>>> AAA client
> >>>>>> 
> >>>>>>> sitting on the PAA can turn these into accoutning records.
> >>>>>> 
> >>>>>> should the PAA poll the EPs to get these counters when needed (the
> >>>>>> SNMP way...) or the EPs are supposed to send them periodically ?
> >>>>>> 
> >>>>>> anyway, this should be somehow a requirement.
> >>>>>> 
> >>>>>> 
> >>>>>> 
> >>>>>>> Alper
> >>>>>>> 
> >>>>>> 
> >>>>>> thanks,
> >>>>>> yacine
> >>>>>> 
> >>>>>> 
> >>>>>>>> d) ????
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> thanks,
> >>>>>>>> Yacine El Mghazli
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> 
> >>>>>>>> _______________________________________________
> >>>>>>>> Pana mailing 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
> >>>>> 
> >>>>> 
> >>>>> _________________________________________________________________
> >>>>> Set yourself up for fun at home!  Get tips on home entertainment
> >>>>> equipment, video game reviews, and more here.
> >>>>> http://special.msn.com/home/homeent.armx
> >>>>> 
> >>>>> 
> >>>> 
> >>>> 
> >>>> 
> >>>> 
> >>> 
> >>> 
> >> 
> >> 
> > 
> > _______________________________________________
> > Pana mailing 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  Sun Dec 14 19:18:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03314
	for <pana-archive@lists.ietf.org>; Sun, 14 Dec 2003 19:18: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 1AVgQy-0000TW-Ir; Sun, 14 Dec 2003 19:18:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVgQo-0000T1-Cs
	for pana@optimus.ietf.org; Sun, 14 Dec 2003 19:17:50 -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 TAA03264;
	Sun, 14 Dec 2003 19:17:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVgQm-0006t5-00; Sun, 14 Dec 2003 19:17:48 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVgQm-0006t0-00; Sun, 14 Dec 2003 19:17:48 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBF0HjY9024113;
	Mon, 15 Dec 2003 09:17:46 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBF0HjiE010065;
	Mon, 15 Dec 2003 09:17:45 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id KAA10062 ; Mon, 15 Dec 2003 09:17:45 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA03597; Mon, 15 Dec 2003 09:17:45 +0900 (JST)
Received: from isl.rdc.toshiba.co.jp by toshiba.co.jp id JAA03834; Mon, 15 Dec 2003 09:17:44 +0900 (JST)
Received: from localhost (inoue@flowerpark [133.196.16.25])
	by isl.rdc.toshiba.co.jp (8.11.7/8.11.6/1.4) with ESMTP id hBF0Hh125636;
	Mon, 15 Dec 2003 09:17:43 +0900 (JST)
To: nemo@ietf.org, mip6@ietf.org, mipshop@ietf.org, mip4@ietf.org,
        pana@ietf.org
In-Reply-To: Your message of "Sat, 13 Dec 2003 10:55:08 +0900"
	<20031213105508E.inoue@isl.rdc.toshiba.co.jp>
References: <20031213105508E.inoue@isl.rdc.toshiba.co.jp>
X-Mailer: Mew version 1.93 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20031215091743J.inoue@isl.rdc.toshiba.co.jp>
Date: Mon, 15 Dec 2003 09:17:43 +0900
From: Atsushi Inoue <inoue@isl.rdc.toshiba.co.jp>
X-Dispatcher: imput version 980905(IM100)
Lines: 126
Content-Transfer-Encoding: 7bit
Subject: [Pana] Call for participation: ICMU2004 Jan.8-9 at Yokosuka Japan
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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

         (Apologies if you receive multiple copies)
                    CALL FOR Participation
                    ======================
           First International Conference 
   on Mobile Computing and Ubiquitous Networking (ICMU 2004) 

        January 8 and 9, 2004
        NTT DoCoMo R&D Center, Yokosuka Research Park, Yokosuka, JAPAN

	Co-sponsored by IPSJ SIG-MBL (Informaiton Processing Society
	of Japan, Special Interest Group of Mobile Computing and
	Ubiquitous Networking) and IPSJ SG-BCC (Study Group of
	Broadcast Communicaiton and Computing) 

Advanced Program:
~~~~~~~~~~~~~~~~~
        See http://www.ipsj.or.jp/sig/mbl/icmu2004/

Scope
~~~~~~
Mobile computing aims at ubiquitous user access to computer 
application. To make it possible, networking technology which enables 
Internet access anytime and everywhere, i.e. ubiquitous networking is 
necessary. It is obvious that with the accelerating trends towards 
mobile networks, ad-hoc networks, and wireless networks, mobile 
computing and ubiquitous networking will play an important role in 
future network. This conference is aimed at providing researchers and 
practitioners in this hot research area a forum for discussion and 
collaboration. Authors are invited to submit papers addressing, but 
not limited to, the following topics:

 -  Applications and services for mobile computing 
 - Network architectures, protocols, or service models for ubiquitous
   networking 
 - Network management for ubiquitous networking 
 - Data management for mobile computing 
 - Security in mobile computing and ubiquitous networking 
 - Wireless and mobile communications 
 - Nomadic computing 
 - Ad-hoc networks 
 - Mobile Internetworking 
 - Performance evaluation for mobile computing and ubiquitous 
   networking systems 
 - Location Based Service 
 - Broadcast Communication 

Location and Date:
~~~~~~~~~~~~~~~~~~
The location of the NTT DoCoMo R&D Center is in the heart of Yokosuka
Research Park(YRP) where a lot of wireless communication related
research institutes are established. YRP is really the heart of
wireless communications research in Japan. Japanese old city Kamakura,
a famous historic city, is 30 minutes by train. Beginning of the year
is one of the best seasons for visiting Japan.  

---
Susumu ISHIHARA
  Faculty of Engineering, Shizuoka University
  3-5-1 Johoku, Hamamatsu 432-8561, JAPAN
  ishiahra@ishilab.net   http://www.ishilab.net/



         (Apologies if you receive multiple copies)
                    CALL FOR Participation
                    ======================
           First International Conference 
   on Mobile Computing and Ubiquitous Networking (ICMU 2004) 

        January 8 and 9, 2004
        NTT DoCoMo R&D Center, Yokosuka Research Park, Yokosuka, JAPAN

	Co-sponsored by IPSJ SIG-MBL (Informaiton Processing Society
	of Japan, Special Interest Group of Mobile Computing and
	Ubiquitous Networking) and IPSJ SG-BCC (Study Group of
	Broadcast Communicaiton and Computing) 

Advanced Program:
~~~~~~~~~~~~~~~~~
        See http://www.ipsj.or.jp/sig/mbl/icmu2004/

Scope
~~~~~~
Mobile computing aims at ubiquitous user access to computer 
application. To make it possible, networking technology which enables 
Internet access anytime and everywhere, i.e. ubiquitous networking is 
necessary. It is obvious that with the accelerating trends towards 
mobile networks, ad-hoc networks, and wireless networks, mobile 
computing and ubiquitous networking will play an important role in 
future network. This conference is aimed at providing researchers and 
practitioners in this hot research area a forum for discussion and 
collaboration. Authors are invited to submit papers addressing, but 
not limited to, the following topics:

 -  Applications and services for mobile computing 
 - Network architectures, protocols, or service models for ubiquitous
   networking 
 - Network management for ubiquitous networking 
 - Data management for mobile computing 
 - Security in mobile computing and ubiquitous networking 
 - Wireless and mobile communications 
 - Nomadic computing 
 - Ad-hoc networks 
 - Mobile Internetworking 
 - Performance evaluation for mobile computing and ubiquitous 
   networking systems 
 - Location Based Service 
 - Broadcast Communication 

Location and Date:
~~~~~~~~~~~~~~~~~~
The location of the NTT DoCoMo R&D Center is in the heart of Yokosuka
Research Park(YRP) where a lot of wireless communication related
research institutes are established. YRP is really the heart of
wireless communications research in Japan. Japanese old city Kamakura,
a famous historic city, is 30 minutes by train. Beginning of the year
is one of the best seasons for visiting Japan.  

---
Susumu ISHIHARA
  Faculty of Engineering, Shizuoka University
  3-5-1 Johoku, Hamamatsu 432-8561, JAPAN
  ishiahra@ishilab.net   http://www.ishilab.net/




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


From exim@www1.ietf.org  Sun Dec 14 19:18:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03332
	for <pana-archive@odin.ietf.org>; Sun, 14 Dec 2003 19:18:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVgR2-0000V8-6B
	for pana-archive@odin.ietf.org; Sun, 14 Dec 2003 19:18:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBF0I4ti001920
	for pana-archive@odin.ietf.org; Sun, 14 Dec 2003 19:18:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVgR2-0000Ut-1q
	for pana-web-archive@optimus.ietf.org; Sun, 14 Dec 2003 19:18: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 TAA03277
	for <pana-web-archive@ietf.org>; Sun, 14 Dec 2003 19:18:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVgR0-0006tX-00
	for pana-web-archive@ietf.org; Sun, 14 Dec 2003 19:18:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVgR0-0006tU-00
	for pana-web-archive@ietf.org; Sun, 14 Dec 2003 19:18:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVgQy-0000TW-Ir; Sun, 14 Dec 2003 19:18:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVgQo-0000T1-Cs
	for pana@optimus.ietf.org; Sun, 14 Dec 2003 19:17:50 -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 TAA03264;
	Sun, 14 Dec 2003 19:17:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVgQm-0006t5-00; Sun, 14 Dec 2003 19:17:48 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVgQm-0006t0-00; Sun, 14 Dec 2003 19:17:48 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBF0HjY9024113;
	Mon, 15 Dec 2003 09:17:46 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBF0HjiE010065;
	Mon, 15 Dec 2003 09:17:45 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id KAA10062 ; Mon, 15 Dec 2003 09:17:45 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id JAA03597; Mon, 15 Dec 2003 09:17:45 +0900 (JST)
Received: from isl.rdc.toshiba.co.jp by toshiba.co.jp id JAA03834; Mon, 15 Dec 2003 09:17:44 +0900 (JST)
Received: from localhost (inoue@flowerpark [133.196.16.25])
	by isl.rdc.toshiba.co.jp (8.11.7/8.11.6/1.4) with ESMTP id hBF0Hh125636;
	Mon, 15 Dec 2003 09:17:43 +0900 (JST)
To: nemo@ietf.org, mip6@ietf.org, mipshop@ietf.org, mip4@ietf.org,
        pana@ietf.org
In-Reply-To: Your message of "Sat, 13 Dec 2003 10:55:08 +0900"
	<20031213105508E.inoue@isl.rdc.toshiba.co.jp>
References: <20031213105508E.inoue@isl.rdc.toshiba.co.jp>
X-Mailer: Mew version 1.93 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20031215091743J.inoue@isl.rdc.toshiba.co.jp>
Date: Mon, 15 Dec 2003 09:17:43 +0900
From: Atsushi Inoue <inoue@isl.rdc.toshiba.co.jp>
X-Dispatcher: imput version 980905(IM100)
Lines: 126
Content-Transfer-Encoding: 7bit
Subject: [Pana] Call for participation: ICMU2004 Jan.8-9 at Yokosuka Japan
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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

         (Apologies if you receive multiple copies)
                    CALL FOR Participation
                    ======================
           First International Conference 
   on Mobile Computing and Ubiquitous Networking (ICMU 2004) 

        January 8 and 9, 2004
        NTT DoCoMo R&D Center, Yokosuka Research Park, Yokosuka, JAPAN

	Co-sponsored by IPSJ SIG-MBL (Informaiton Processing Society
	of Japan, Special Interest Group of Mobile Computing and
	Ubiquitous Networking) and IPSJ SG-BCC (Study Group of
	Broadcast Communicaiton and Computing) 

Advanced Program:
~~~~~~~~~~~~~~~~~
        See http://www.ipsj.or.jp/sig/mbl/icmu2004/

Scope
~~~~~~
Mobile computing aims at ubiquitous user access to computer 
application. To make it possible, networking technology which enables 
Internet access anytime and everywhere, i.e. ubiquitous networking is 
necessary. It is obvious that with the accelerating trends towards 
mobile networks, ad-hoc networks, and wireless networks, mobile 
computing and ubiquitous networking will play an important role in 
future network. This conference is aimed at providing researchers and 
practitioners in this hot research area a forum for discussion and 
collaboration. Authors are invited to submit papers addressing, but 
not limited to, the following topics:

 -  Applications and services for mobile computing 
 - Network architectures, protocols, or service models for ubiquitous
   networking 
 - Network management for ubiquitous networking 
 - Data management for mobile computing 
 - Security in mobile computing and ubiquitous networking 
 - Wireless and mobile communications 
 - Nomadic computing 
 - Ad-hoc networks 
 - Mobile Internetworking 
 - Performance evaluation for mobile computing and ubiquitous 
   networking systems 
 - Location Based Service 
 - Broadcast Communication 

Location and Date:
~~~~~~~~~~~~~~~~~~
The location of the NTT DoCoMo R&D Center is in the heart of Yokosuka
Research Park(YRP) where a lot of wireless communication related
research institutes are established. YRP is really the heart of
wireless communications research in Japan. Japanese old city Kamakura,
a famous historic city, is 30 minutes by train. Beginning of the year
is one of the best seasons for visiting Japan.  

---
Susumu ISHIHARA
  Faculty of Engineering, Shizuoka University
  3-5-1 Johoku, Hamamatsu 432-8561, JAPAN
  ishiahra@ishilab.net   http://www.ishilab.net/



         (Apologies if you receive multiple copies)
                    CALL FOR Participation
                    ======================
           First International Conference 
   on Mobile Computing and Ubiquitous Networking (ICMU 2004) 

        January 8 and 9, 2004
        NTT DoCoMo R&D Center, Yokosuka Research Park, Yokosuka, JAPAN

	Co-sponsored by IPSJ SIG-MBL (Informaiton Processing Society
	of Japan, Special Interest Group of Mobile Computing and
	Ubiquitous Networking) and IPSJ SG-BCC (Study Group of
	Broadcast Communicaiton and Computing) 

Advanced Program:
~~~~~~~~~~~~~~~~~
        See http://www.ipsj.or.jp/sig/mbl/icmu2004/

Scope
~~~~~~
Mobile computing aims at ubiquitous user access to computer 
application. To make it possible, networking technology which enables 
Internet access anytime and everywhere, i.e. ubiquitous networking is 
necessary. It is obvious that with the accelerating trends towards 
mobile networks, ad-hoc networks, and wireless networks, mobile 
computing and ubiquitous networking will play an important role in 
future network. This conference is aimed at providing researchers and 
practitioners in this hot research area a forum for discussion and 
collaboration. Authors are invited to submit papers addressing, but 
not limited to, the following topics:

 -  Applications and services for mobile computing 
 - Network architectures, protocols, or service models for ubiquitous
   networking 
 - Network management for ubiquitous networking 
 - Data management for mobile computing 
 - Security in mobile computing and ubiquitous networking 
 - Wireless and mobile communications 
 - Nomadic computing 
 - Ad-hoc networks 
 - Mobile Internetworking 
 - Performance evaluation for mobile computing and ubiquitous 
   networking systems 
 - Location Based Service 
 - Broadcast Communication 

Location and Date:
~~~~~~~~~~~~~~~~~~
The location of the NTT DoCoMo R&D Center is in the heart of Yokosuka
Research Park(YRP) where a lot of wireless communication related
research institutes are established. YRP is really the heart of
wireless communications research in Japan. Japanese old city Kamakura,
a famous historic city, is 30 minutes by train. Beginning of the year
is one of the best seasons for visiting Japan.  

---
Susumu ISHIHARA
  Faculty of Engineering, Shizuoka University
  3-5-1 Johoku, Hamamatsu 432-8561, JAPAN
  ishiahra@ishilab.net   http://www.ishilab.net/




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



From pana-admin@ietf.org  Mon Dec 15 08:56:38 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08338
	for <pana-archive@lists.ietf.org>; Mon, 15 Dec 2003 08:56:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVtCg-0004Ga-Ky; Mon, 15 Dec 2003 08:56:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVtCS-0004FS-DN
	for pana@optimus.ietf.org; Mon, 15 Dec 2003 08:55: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 IAA08292
	for <pana@ietf.org>; Mon, 15 Dec 2003 08:55:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVtCQ-0004rx-00
	for pana@ietf.org; Mon, 15 Dec 2003 08:55:50 -0500
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVtCQ-0004rP-00
	for pana@ietf.org; Mon, 15 Dec 2003 08:55:50 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hBFDo17F021702;
	Mon, 15 Dec 2003 14:50:01 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003121514495873:4112 ;
          Mon, 15 Dec 2003 14:49:58 +0100 
Message-ID: <3FDDBC07.8010806@alcatel.fr>
Date: Mon, 15 Dec 2003 14:49:59 +0100
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: Alper Yegin <alper@docomolabs-usa.com>, pana@ietf.org,
        lionel.morand@francetelecom.com, Julien.Bournelle@int-evry.fr
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol requirements)
References: <20031212100413.GF30546@steelhead> <BBFF540D.EBDE%alper@docomolabs-usa.com> <20031212224323.GG30546@steelhead>
In-Reply-To: <20031212224323.GG30546@steelhead>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/15/2003 14:49:58,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/15/2003 14:50:01,
	Serialize complete at 12/15/2003 14:50:01
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-Alcanet-MTA-scanned-and-authorized: yes
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 Ohba wrote:

> On Fri, Dec 12, 2003 at 11:16:29AM -0800, Alper Yegin wrote:
> 
>>Hi Yoshi,
>>
>>I don't fully understand this scenario. Normally there is one physical
>>network, owned by one NAP. That NAP puts a PAA, and enables PaC select from
>>a set of ISPs. 
>>
>>You seem to suggest multiple NAPs sharing the same physical access network.
>>I don't think this is a realistic scenario.
> 
> 
> I did not actually think about multiple NAPs.  What I was thinking is
> a model where there is only one NAP, but each PAA is owned by a
> different ISP and performs only ISP authentication for the ISP. In
> this case, the NAP just provides the ISPs the physical location to put
> their PAAs and EPs, and no NAP authentication is performed.

see the folowing message on the same subject:
ftp://ftp.research.telcordia.com/pub/Group.archive/pana/webview/msg01956.html

yacine


> Yoshihiro Ohba
> 
> 
>>Alper
>>
>>
>>
>>
>>>I think multiple PAAs in the same IP subnet will be important when
>>>realizing a network selection over a shared medium without depending
>>>on L2-based selection techniques such as PPPoE discovery.  Of cource,
>>>more work would be needed for establishing an appropriate routing
>>>context and assigning an IP address for use of a selected network.
>>>
>>>Yoshihiro Ohba
>>>
>>>
>>>On Fri, Dec 12, 2003 at 02:10:47PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
>>>
>>>>hi all,
>>>>
>>>>does the working group foresee deployment scenarios where we have
>>>>multiple PAAs in the same IP subnet ?
>>>>
>>>>thanks,
>>>>Yacine
>>>>
>>>>
>>>>
>>>>Alper Yegin wrote:
>>>>
>>>>
>>>>>>my understanding is the following:
>>>>>>
>>>>>>PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
>>>>>>For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
>>>>>>configuring the concerned EPs. depending on the topology, there could be
>>>>>>more than one.
>>>>>>
>>>>>>does it look correct ?
>>>>>
>>>>>
>>>>>Yes. This is what I'm thinking.
>>>>>
>>>>>
>>>>>
>>>>>>>>* inter-PAAs communication ?
>>>>>>>
>>>>>>>
>>>>>>>Why do we need this for?
>>>>>>
>>>>>>for exemple: context transfer between PAAs for mobility handling (in
>>>>>>order to avoid re-authentication, which would reduce the handover perf).
>>>>>>this is strongly dependent of the relation between PAA and EPs discussed
>>>>>>above.
>>>>>
>>>>>
>>>>>I cannot see the relation. I think changing PAAs due to mobility and
>>>>>enabling fast reauthentication via context transfers is orthogonal to the
>>>>>PAA2EP protocol.
>>>>>
>>>>>Alper
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>Alper
>>>>>>
>>>>>>Yacine
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>etc...
>>>>>>>>
>>>>>>>>comments on these "issues" are warmly welcome !
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>>c) Accounting/Feedback from the EPs:
>>>>>>>>>>The PAA must have an efficient way to to get the accounting
>>>>>>
>>>>>>information
>>>>>>
>>>>>>
>>>>>>>>>>of PaC from EP since the PAA may be a client of the AAA backend
>>>>>>>>>>infrastructure.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>Getting statistics from the EP makes sense. For example, in the
>>>>>>
>>>>>>case of
>>>>>>
>>>>>>
>>>>>>>>>SNMP, if we get the counters from the EP this is good enough. The
>>>>>>>>
>>>>>>>>AAA client
>>>>>>>>
>>>>>>>>
>>>>>>>>>sitting on the PAA can turn these into accoutning records.
>>>>>>>>
>>>>>>>>should the PAA poll the EPs to get these counters when needed (the
>>>>>>>>SNMP way...) or the EPs are supposed to send them periodically ?
>>>>>>>>
>>>>>>>>anyway, this should be somehow a requirement.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Alper
>>>>>>>>>
>>>>>>>>
>>>>>>>>thanks,
>>>>>>>>yacine
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>>d) ????
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>thanks,
>>>>>>>>>>Yacine El Mghazli
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>_______________________________________________
>>>>>>>>>>Pana mailing 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
>>>>>>>
>>>>>>>
>>>>>>>_________________________________________________________________
>>>>>>>Set yourself up for fun at home!  Get tips on home entertainment
>>>>>>>equipment, video game reviews, and more here.
>>>>>>>http://special.msn.com/home/homeent.armx
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>_______________________________________________
>>>Pana mailing 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 Dec 15 08:56:41 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08353
	for <pana-archive@odin.ietf.org>; Mon, 15 Dec 2003 08:56:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVtCl-0004HN-U4
	for pana-archive@odin.ietf.org; Mon, 15 Dec 2003 08:56:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBFDuBXi016443
	for pana-archive@odin.ietf.org; Mon, 15 Dec 2003 08:56:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVtCk-0004H8-Oe
	for pana-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 08:56:10 -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 IAA08313
	for <pana-web-archive@ietf.org>; Mon, 15 Dec 2003 08:56:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVtCj-0004sh-00
	for pana-web-archive@ietf.org; Mon, 15 Dec 2003 08:56:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVtCj-0004se-00
	for pana-web-archive@ietf.org; Mon, 15 Dec 2003 08:56:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVtCg-0004Ga-Ky; Mon, 15 Dec 2003 08:56:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVtCS-0004FS-DN
	for pana@optimus.ietf.org; Mon, 15 Dec 2003 08:55: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 IAA08292
	for <pana@ietf.org>; Mon, 15 Dec 2003 08:55:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVtCQ-0004rx-00
	for pana@ietf.org; Mon, 15 Dec 2003 08:55:50 -0500
Received: from gc-na5.alcatel.fr ([64.208.49.5] helo=smail3.alcatel.fr)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVtCQ-0004rP-00
	for pana@ietf.org; Mon, 15 Dec 2003 08:55:50 -0500
Received: from frmail30.netfr.alcatel.fr (frmail30.netfr.alcatel.fr [155.132.182.163])
	by smail3.alcatel.fr (ALCANET/NETFR) with ESMTP id hBFDo17F021702;
	Mon, 15 Dec 2003 14:50:01 +0100
Received: from alcatel.fr ([172.25.72.141])
          by frmail30.netfr.alcatel.fr (Lotus Domino Release 5.0.9a)
          with ESMTP id 2003121514495873:4112 ;
          Mon, 15 Dec 2003 14:49:58 +0100 
Message-ID: <3FDDBC07.8010806@alcatel.fr>
Date: Mon, 15 Dec 2003 14:49:59 +0100
From: Yacine.El_Mghazli@alcatel.fr
Organization: Alcatel R&I
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-gb, fr-fr, en, fr
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Cc: Alper Yegin <alper@docomolabs-usa.com>, pana@ietf.org,
        lionel.morand@francetelecom.com, Julien.Bournelle@int-evry.fr
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol requirements)
References: <20031212100413.GF30546@steelhead> <BBFF540D.EBDE%alper@docomolabs-usa.com> <20031212224323.GG30546@steelhead>
In-Reply-To: <20031212224323.GG30546@steelhead>
X-MIMETrack: Itemize by SMTP Server on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/15/2003 14:49:58,
	Serialize by Router on FRMAIL30/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at
 12/15/2003 14:50:01,
	Serialize complete at 12/15/2003 14:50:01
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-Alcanet-MTA-scanned-and-authorized: yes
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 Ohba wrote:

> On Fri, Dec 12, 2003 at 11:16:29AM -0800, Alper Yegin wrote:
> 
>>Hi Yoshi,
>>
>>I don't fully understand this scenario. Normally there is one physical
>>network, owned by one NAP. That NAP puts a PAA, and enables PaC select from
>>a set of ISPs. 
>>
>>You seem to suggest multiple NAPs sharing the same physical access network.
>>I don't think this is a realistic scenario.
> 
> 
> I did not actually think about multiple NAPs.  What I was thinking is
> a model where there is only one NAP, but each PAA is owned by a
> different ISP and performs only ISP authentication for the ISP. In
> this case, the NAP just provides the ISPs the physical location to put
> their PAAs and EPs, and no NAP authentication is performed.

see the folowing message on the same subject:
ftp://ftp.research.telcordia.com/pub/Group.archive/pana/webview/msg01956.html

yacine


> Yoshihiro Ohba
> 
> 
>>Alper
>>
>>
>>
>>
>>>I think multiple PAAs in the same IP subnet will be important when
>>>realizing a network selection over a shared medium without depending
>>>on L2-based selection techniques such as PPPoE discovery.  Of cource,
>>>more work would be needed for establishing an appropriate routing
>>>context and assigning an IP address for use of a selected network.
>>>
>>>Yoshihiro Ohba
>>>
>>>
>>>On Fri, Dec 12, 2003 at 02:10:47PM +0100, Yacine.El_Mghazli@alcatel.fr wrote:
>>>
>>>>hi all,
>>>>
>>>>does the working group foresee deployment scenarios where we have
>>>>multiple PAAs in the same IP subnet ?
>>>>
>>>>thanks,
>>>>Yacine
>>>>
>>>>
>>>>
>>>>Alper Yegin wrote:
>>>>
>>>>
>>>>>>my understanding is the following:
>>>>>>
>>>>>>PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
>>>>>>For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
>>>>>>configuring the concerned EPs. depending on the topology, there could be
>>>>>>more than one.
>>>>>>
>>>>>>does it look correct ?
>>>>>
>>>>>
>>>>>Yes. This is what I'm thinking.
>>>>>
>>>>>
>>>>>
>>>>>>>>* inter-PAAs communication ?
>>>>>>>
>>>>>>>
>>>>>>>Why do we need this for?
>>>>>>
>>>>>>for exemple: context transfer between PAAs for mobility handling (in
>>>>>>order to avoid re-authentication, which would reduce the handover perf).
>>>>>>this is strongly dependent of the relation between PAA and EPs discussed
>>>>>>above.
>>>>>
>>>>>
>>>>>I cannot see the relation. I think changing PAAs due to mobility and
>>>>>enabling fast reauthentication via context transfers is orthogonal to the
>>>>>PAA2EP protocol.
>>>>>
>>>>>Alper
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>Alper
>>>>>>
>>>>>>Yacine
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>etc...
>>>>>>>>
>>>>>>>>comments on these "issues" are warmly welcome !
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>>c) Accounting/Feedback from the EPs:
>>>>>>>>>>The PAA must have an efficient way to to get the accounting
>>>>>>
>>>>>>information
>>>>>>
>>>>>>
>>>>>>>>>>of PaC from EP since the PAA may be a client of the AAA backend
>>>>>>>>>>infrastructure.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>Getting statistics from the EP makes sense. For example, in the
>>>>>>
>>>>>>case of
>>>>>>
>>>>>>
>>>>>>>>>SNMP, if we get the counters from the EP this is good enough. The
>>>>>>>>
>>>>>>>>AAA client
>>>>>>>>
>>>>>>>>
>>>>>>>>>sitting on the PAA can turn these into accoutning records.
>>>>>>>>
>>>>>>>>should the PAA poll the EPs to get these counters when needed (the
>>>>>>>>SNMP way...) or the EPs are supposed to send them periodically ?
>>>>>>>>
>>>>>>>>anyway, this should be somehow a requirement.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>Alper
>>>>>>>>>
>>>>>>>>
>>>>>>>>thanks,
>>>>>>>>yacine
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>>d) ????
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>thanks,
>>>>>>>>>>Yacine El Mghazli
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>_______________________________________________
>>>>>>>>>>Pana mailing 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
>>>>>>>
>>>>>>>
>>>>>>>_________________________________________________________________
>>>>>>>Set yourself up for fun at home!  Get tips on home entertainment
>>>>>>>equipment, video game reviews, and more here.
>>>>>>>http://special.msn.com/home/homeent.armx
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>_______________________________________________
>>>Pana mailing 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 Dec 15 15:57:31 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29276
	for <pana-archive@lists.ietf.org>; Mon, 15 Dec 2003 15:57:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVzm0-0006ct-7c; Mon, 15 Dec 2003 15:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVzle-0006bT-Cv
	for pana@optimus.ietf.org; Mon, 15 Dec 2003 15:56:38 -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 PAA29099
	for <pana@ietf.org>; Mon, 15 Dec 2003 15:56:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVzlc-00003J-00
	for pana@ietf.org; Mon, 15 Dec 2003 15:56:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AVzl3-00000R-00
	for pana@ietf.org; Mon, 15 Dec 2003 15:56: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 1AVzl2-0007mm-00
	for pana@ietf.org; Mon, 15 Dec 2003 15:56:00 -0500
Date: Mon, 15 Dec 2003 12:57:07 -0800
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol
	requirements)
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Yacine.El_Mghazli@alcatel.fr>, <pana@ietf.org>,
        <lionel.morand@francetelecom.com>, <Julien.Bournelle@int-evry.fr>
Message-ID: <BC036023.EDAA%alper@docomolabs-usa.com>
In-Reply-To: <20031212224323.GG30546@steelhead>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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 did not actually think about multiple NAPs.  What I was thinking is
> a model where there is only one NAP, but each PAA is owned by a
> different ISP and performs only ISP authentication for the ISP. In
> this case, the NAP just provides the ISPs the physical location to put
> their PAAs and EPs, and no NAP authentication is performed.

This is different than the current NAS model. If we have to extend/modify
the design to support such a scenario, we need to understand if it qualifies
to justify that action. Why would anyone not use the current NAS model and
resort to something like that?

Alper




> 
> Yoshihiro Ohba
> 
>> 
>> Alper
>> 
>> 
>> 
>>> I think multiple PAAs in the same IP subnet will be important when
>>> realizing a network selection over a shared medium without depending
>>> on L2-based selection techniques such as PPPoE discovery.  Of cource,
>>> more work would be needed for establishing an appropriate routing
>>> context and assigning an IP address for use of a selected network.
>>> 
>>> Yoshihiro Ohba
>>> 
>>> 
>>> On Fri, Dec 12, 2003 at 02:10:47PM +0100, Yacine.El_Mghazli@alcatel.fr
>>> wrote:
>>>> hi all,
>>>> 
>>>> does the working group foresee deployment scenarios where we have
>>>> multiple PAAs in the same IP subnet ?
>>>> 
>>>> thanks,
>>>> Yacine
>>>> 
>>>> 
>>>> 
>>>> Alper Yegin wrote:
>>>> 
>>>>>> my understanding is the following:
>>>>>> 
>>>>>> PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
>>>>>> For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
>>>>>> configuring the concerned EPs. depending on the topology, there could be
>>>>>> more than one.
>>>>>> 
>>>>>> does it look correct ?
>>>>> 
>>>>> 
>>>>> Yes. This is what I'm thinking.
>>>>> 
>>>>> 
>>>>>>>> * inter-PAAs communication ?
>>>>>>> 
>>>>>>> 
>>>>>>> Why do we need this for?
>>>>>> 
>>>>>> for exemple: context transfer between PAAs for mobility handling (in
>>>>>> order to avoid re-authentication, which would reduce the handover perf).
>>>>>> this is strongly dependent of the relation between PAA and EPs discussed
>>>>>> above.
>>>>> 
>>>>> 
>>>>> I cannot see the relation. I think changing PAAs due to mobility and
>>>>> enabling fast reauthentication via context transfers is orthogonal to the
>>>>> PAA2EP protocol.
>>>>> 
>>>>> Alper
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>>> Alper
>>>>>> 
>>>>>> Yacine
>>>>>> 
>>>>>> 
>>>>>>>> etc...
>>>>>>>> 
>>>>>>>> comments on these "issues" are warmly welcome !
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>>> c) Accounting/Feedback from the EPs:
>>>>>>>>>> The PAA must have an efficient way to to get the accounting
>>>>>> 
>>>>>> information
>>>>>> 
>>>>>>>>>> of PaC from EP since the PAA may be a client of the AAA backend
>>>>>>>>>> infrastructure.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Getting statistics from the EP makes sense. For example, in the
>>>>>> 
>>>>>> case of
>>>>>> 
>>>>>>>>> SNMP, if we get the counters from the EP this is good enough. The
>>>>>>>> 
>>>>>>>> AAA client
>>>>>>>> 
>>>>>>>>> sitting on the PAA can turn these into accoutning records.
>>>>>>>> 
>>>>>>>> should the PAA poll the EPs to get these counters when needed (the
>>>>>>>> SNMP way...) or the EPs are supposed to send them periodically ?
>>>>>>>> 
>>>>>>>> anyway, this should be somehow a requirement.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> Alper
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> thanks,
>>>>>>>> yacine
>>>>>>>> 
>>>>>>>> 
>>>>>>>>>> d) ????
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> thanks,
>>>>>>>>>> Yacine El Mghazli
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Pana mailing 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
>>>>>>> 
>>>>>>> 
>>>>>>> _________________________________________________________________
>>>>>>> Set yourself up for fun at home!  Get tips on home entertainment
>>>>>>> equipment, video game reviews, and more here.
>>>>>>> http://special.msn.com/home/homeent.armx
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> Pana mailing 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 Dec 15 15:57:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29294
	for <pana-archive@odin.ietf.org>; Mon, 15 Dec 2003 15:57:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVzm6-0006eJ-1s
	for pana-archive@odin.ietf.org; Mon, 15 Dec 2003 15:57:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBFKv5De025553
	for pana-archive@odin.ietf.org; Mon, 15 Dec 2003 15:57:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVzm5-0006e4-OQ
	for pana-web-archive@optimus.ietf.org; Mon, 15 Dec 2003 15:57: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 PAA29224
	for <pana-web-archive@ietf.org>; Mon, 15 Dec 2003 15:57:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVzm4-00006g-00
	for pana-web-archive@ietf.org; Mon, 15 Dec 2003 15:57:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AVzm2-00006W-00
	for pana-web-archive@ietf.org; Mon, 15 Dec 2003 15:57:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVzm2-00006S-00
	for pana-web-archive@ietf.org; Mon, 15 Dec 2003 15:57:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVzm0-0006ct-7c; Mon, 15 Dec 2003 15:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AVzle-0006bT-Cv
	for pana@optimus.ietf.org; Mon, 15 Dec 2003 15:56:38 -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 PAA29099
	for <pana@ietf.org>; Mon, 15 Dec 2003 15:56:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AVzlc-00003J-00
	for pana@ietf.org; Mon, 15 Dec 2003 15:56:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AVzl3-00000R-00
	for pana@ietf.org; Mon, 15 Dec 2003 15:56: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 1AVzl2-0007mm-00
	for pana@ietf.org; Mon, 15 Dec 2003 15:56:00 -0500
Date: Mon, 15 Dec 2003 12:57:07 -0800
Subject: Re: Multiple PAAs Issues (was Re: [Pana] PAA-2-EP protocol
	requirements)
From: Alper Yegin <alper@docomolabs-usa.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
CC: <Yacine.El_Mghazli@alcatel.fr>, <pana@ietf.org>,
        <lionel.morand@francetelecom.com>, <Julien.Bournelle@int-evry.fr>
Message-ID: <BC036023.EDAA%alper@docomolabs-usa.com>
In-Reply-To: <20031212224323.GG30546@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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> I did not actually think about multiple NAPs.  What I was thinking is
> a model where there is only one NAP, but each PAA is owned by a
> different ISP and performs only ISP authentication for the ISP. In
> this case, the NAP just provides the ISPs the physical location to put
> their PAAs and EPs, and no NAP authentication is performed.

This is different than the current NAS model. If we have to extend/modify
the design to support such a scenario, we need to understand if it qualifies
to justify that action. Why would anyone not use the current NAS model and
resort to something like that?

Alper




> 
> Yoshihiro Ohba
> 
>> 
>> Alper
>> 
>> 
>> 
>>> I think multiple PAAs in the same IP subnet will be important when
>>> realizing a network selection over a shared medium without depending
>>> on L2-based selection techniques such as PPPoE discovery.  Of cource,
>>> more work would be needed for establishing an appropriate routing
>>> context and assigning an IP address for use of a selected network.
>>> 
>>> Yoshihiro Ohba
>>> 
>>> 
>>> On Fri, Dec 12, 2003 at 02:10:47PM +0100, Yacine.El_Mghazli@alcatel.fr
>>> wrote:
>>>> hi all,
>>>> 
>>>> does the working group foresee deployment scenarios where we have
>>>> multiple PAAs in the same IP subnet ?
>>>> 
>>>> thanks,
>>>> Yacine
>>>> 
>>>> 
>>>> 
>>>> Alper Yegin wrote:
>>>> 
>>>>>> my understanding is the following:
>>>>>> 
>>>>>> PAA-1 and PAA-2 authenticate the PaCs via PANA in the access network.
>>>>>> For each PaC authenticated by PAA-1, PAA-1 authorize this PaC traffic by
>>>>>> configuring the concerned EPs. depending on the topology, there could be
>>>>>> more than one.
>>>>>> 
>>>>>> does it look correct ?
>>>>> 
>>>>> 
>>>>> Yes. This is what I'm thinking.
>>>>> 
>>>>> 
>>>>>>>> * inter-PAAs communication ?
>>>>>>> 
>>>>>>> 
>>>>>>> Why do we need this for?
>>>>>> 
>>>>>> for exemple: context transfer between PAAs for mobility handling (in
>>>>>> order to avoid re-authentication, which would reduce the handover perf).
>>>>>> this is strongly dependent of the relation between PAA and EPs discussed
>>>>>> above.
>>>>> 
>>>>> 
>>>>> I cannot see the relation. I think changing PAAs due to mobility and
>>>>> enabling fast reauthentication via context transfers is orthogonal to the
>>>>> PAA2EP protocol.
>>>>> 
>>>>> Alper
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>>> Alper
>>>>>> 
>>>>>> Yacine
>>>>>> 
>>>>>> 
>>>>>>>> etc...
>>>>>>>> 
>>>>>>>> comments on these "issues" are warmly welcome !
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>>> c) Accounting/Feedback from the EPs:
>>>>>>>>>> The PAA must have an efficient way to to get the accounting
>>>>>> 
>>>>>> information
>>>>>> 
>>>>>>>>>> of PaC from EP since the PAA may be a client of the AAA backend
>>>>>>>>>> infrastructure.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Getting statistics from the EP makes sense. For example, in the
>>>>>> 
>>>>>> case of
>>>>>> 
>>>>>>>>> SNMP, if we get the counters from the EP this is good enough. The
>>>>>>>> 
>>>>>>>> AAA client
>>>>>>>> 
>>>>>>>>> sitting on the PAA can turn these into accoutning records.
>>>>>>>> 
>>>>>>>> should the PAA poll the EPs to get these counters when needed (the
>>>>>>>> SNMP way...) or the EPs are supposed to send them periodically ?
>>>>>>>> 
>>>>>>>> anyway, this should be somehow a requirement.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> Alper
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> thanks,
>>>>>>>> yacine
>>>>>>>> 
>>>>>>>> 
>>>>>>>>>> d) ????
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> thanks,
>>>>>>>>>> Yacine El Mghazli
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Pana mailing 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
>>>>>>> 
>>>>>>> 
>>>>>>> _________________________________________________________________
>>>>>>> Set yourself up for fun at home!  Get tips on home entertainment
>>>>>>> equipment, video game reviews, and more here.
>>>>>>> http://special.msn.com/home/homeent.armx
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> Pana mailing 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 Dec 18 00:03:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23133
	for <pana-archive@lists.ietf.org>; Thu, 18 Dec 2003 00:03:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWqJQ-0005xO-E1; Thu, 18 Dec 2003 00:03:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWqIh-0005x6-4G
	for pana@optimus.ietf.org; Thu, 18 Dec 2003 00:02:15 -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 AAA23118
	for <pana@ietf.org>; Thu, 18 Dec 2003 00:02:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWqIe-00011I-00
	for pana@ietf.org; Thu, 18 Dec 2003 00:02:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWqIe-00011B-00
	for pana@ietf.org; Thu, 18 Dec 2003 00:02:12 -0500
Received: from smtp811.mail.sc5.yahoo.com ([66.163.170.81])
	by ietf-mx with smtp (Exim 4.12)
	id 1AWqId-000118-00
	for pana@ietf.org; Thu, 18 Dec 2003 00:02:11 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.59.194 with login)
  by smtp811.mail.sc5.yahoo.com with SMTP; 18 Dec 2003 05:02:10 -0000
Message-ID: <003c01c3c524$17642740$6901a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: <pana@ietf.org>
Date: Wed, 17 Dec 2003 21:02:09 -0800
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Pana] Unique identifier per session
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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,

PANA session ID uniquely identifies a session. But, it also does not change
across a reauthentication.
The PANA-IPsec draft needs something unique to identify the pre-shared keys
within a sub-session.
Two possibilities.

1) During re-authentication, change the session ID also in reauth-answer.
2) Invent another ID that changes with every reauth and hence uniquely
identifies the keys derived
    during a reauth.

Any other possibilities ?

-mohan


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


From exim@www1.ietf.org  Thu Dec 18 00:03:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23148
	for <pana-archive@odin.ietf.org>; Thu, 18 Dec 2003 00:03:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWqJZ-0005y5-Bi
	for pana-archive@odin.ietf.org; Thu, 18 Dec 2003 00:03:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBI539MX022935
	for pana-archive@odin.ietf.org; Thu, 18 Dec 2003 00:03:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWqJZ-0005xq-4O
	for pana-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 00:03: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 AAA23127
	for <pana-web-archive@ietf.org>; Thu, 18 Dec 2003 00:03:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWqJW-00011X-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 00:03:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWqJV-00011Q-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 00:03:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWqJV-00011N-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 00:03:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWqJQ-0005xO-E1; Thu, 18 Dec 2003 00:03:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWqIh-0005x6-4G
	for pana@optimus.ietf.org; Thu, 18 Dec 2003 00:02:15 -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 AAA23118
	for <pana@ietf.org>; Thu, 18 Dec 2003 00:02:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWqIe-00011I-00
	for pana@ietf.org; Thu, 18 Dec 2003 00:02:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWqIe-00011B-00
	for pana@ietf.org; Thu, 18 Dec 2003 00:02:12 -0500
Received: from smtp811.mail.sc5.yahoo.com ([66.163.170.81])
	by ietf-mx with smtp (Exim 4.12)
	id 1AWqId-000118-00
	for pana@ietf.org; Thu, 18 Dec 2003 00:02:11 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@64.172.59.194 with login)
  by smtp811.mail.sc5.yahoo.com with SMTP; 18 Dec 2003 05:02:10 -0000
Message-ID: <003c01c3c524$17642740$6901a8c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: <pana@ietf.org>
Date: Wed, 17 Dec 2003 21:02:09 -0800
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] Unique identifier per session
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hello,

PANA session ID uniquely identifies a session. But, it also does not change
across a reauthentication.
The PANA-IPsec draft needs something unique to identify the pre-shared keys
within a sub-session.
Two possibilities.

1) During re-authentication, change the session ID also in reauth-answer.
2) Invent another ID that changes with every reauth and hence uniquely
identifies the keys derived
    during a reauth.

Any other possibilities ?

-mohan


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



From pana-admin@ietf.org  Thu Dec 18 10:05:37 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25674
	for <pana-archive@lists.ietf.org>; Thu, 18 Dec 2003 10:05:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzi3-0006eu-FG; Thu, 18 Dec 2003 10:05:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzh9-0006Uz-K3
	for pana@optimus.ietf.org; Thu, 18 Dec 2003 10:04: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 KAA25407
	for <pana@ietf.org>; Thu, 18 Dec 2003 10:04:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzh5-0005va-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:04:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWzh4-0005vG-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:04:03 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzh3-0005uh-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:04:01 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBIF3xY9014975;
	Fri, 19 Dec 2003 00:03:59 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBIF3xUD009922;
	Fri, 19 Dec 2003 00:03:59 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id AAA09917 ; Fri, 19 Dec 2003 00:03:58 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA00085; Fri, 19 Dec 2003 00:03:58 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA04316; Fri, 19 Dec 2003 00:03:58 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hBIF3vPj011648;
	Fri, 19 Dec 2003 00:03:57 +0900 (JST)
Received: from steelhead ([159.119.168.117]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HQ3008GNJ6JK6@tsbpo1.po.toshiba.co.jp>; Fri,
 19 Dec 2003 00:03:56 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AWzgP-0002MX-00; Thu, 18 Dec 2003 07:03:21 -0800
Date: Thu, 18 Dec 2003 07:03:21 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Unique identifier per session
In-reply-to: <003c01c3c524$17642740$6901a8c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: pana@ietf.org
Message-id: <20031218150321.GA8927@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Mohan Parthasarathy <mohanp@sbcglobal.net>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <003c01c3c524$17642740$6901a8c0@adithya>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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, Dec 17, 2003 at 09:02:09PM -0800, Mohan Parthasarathy wrote:
> Hello,
> 
> PANA session ID uniquely identifies a session. But, it also does not change
> across a reauthentication.
> The PANA-IPsec draft needs something unique to identify the pre-shared keys
> within a sub-session.
> Two possibilities.
> 
> 1) During re-authentication, change the session ID also in reauth-answer.
> 2) Invent another ID that changes with every reauth and hence uniquely
> identifies the keys derived
>     during a reauth.

I think it does not make sense to change the PANA Session-ID 
across (re-)authentications just for this purpose.

How about using <PANA Session-Id> | <N> as the IKE pre-shared key
identifier, where N is the number of EAP-based re-authentications
occured for the Session-ID?

Yoshihiro Ohba


> 
> Any other possibilities ?
> 
> -mohan
> 
> 
> _______________________________________________
> Pana mailing 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 Dec 18 10:05:41 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25701
	for <pana-archive@odin.ietf.org>; Thu, 18 Dec 2003 10:05:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWziC-0006fs-A5
	for pana-archive@odin.ietf.org; Thu, 18 Dec 2003 10:05:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIF5CLe025652
	for pana-archive@odin.ietf.org; Thu, 18 Dec 2003 10:05:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWziC-0006ff-0o
	for pana-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 10:05: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 KAA25600
	for <pana-web-archive@ietf.org>; Thu, 18 Dec 2003 10:05:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzi9-000620-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 10:05:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWzi8-00061j-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 10:05:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzi8-00061g-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 10:05:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzi3-0006eu-FG; Thu, 18 Dec 2003 10:05:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWzh9-0006Uz-K3
	for pana@optimus.ietf.org; Thu, 18 Dec 2003 10:04: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 KAA25407
	for <pana@ietf.org>; Thu, 18 Dec 2003 10:04:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzh5-0005va-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:04:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWzh4-0005vG-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:04:03 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWzh3-0005uh-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:04:01 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBIF3xY9014975;
	Fri, 19 Dec 2003 00:03:59 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBIF3xUD009922;
	Fri, 19 Dec 2003 00:03:59 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id AAA09917 ; Fri, 19 Dec 2003 00:03:58 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id AAA00085; Fri, 19 Dec 2003 00:03:58 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id AAA04316; Fri, 19 Dec 2003 00:03:58 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hBIF3vPj011648;
	Fri, 19 Dec 2003 00:03:57 +0900 (JST)
Received: from steelhead ([159.119.168.117]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HQ3008GNJ6JK6@tsbpo1.po.toshiba.co.jp>; Fri,
 19 Dec 2003 00:03:56 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AWzgP-0002MX-00; Thu, 18 Dec 2003 07:03:21 -0800
Date: Thu, 18 Dec 2003 07:03:21 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Unique identifier per session
In-reply-to: <003c01c3c524$17642740$6901a8c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: pana@ietf.org
Message-id: <20031218150321.GA8927@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
Mail-Followup-To: Mohan Parthasarathy <mohanp@sbcglobal.net>, pana@ietf.org
User-Agent: Mutt/1.5.4i
References: <003c01c3c524$17642740$6901a8c0@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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan Parthasarathy wrote:
> Hello,
> 
> PANA session ID uniquely identifies a session. But, it also does not change
> across a reauthentication.
> The PANA-IPsec draft needs something unique to identify the pre-shared keys
> within a sub-session.
> Two possibilities.
> 
> 1) During re-authentication, change the session ID also in reauth-answer.
> 2) Invent another ID that changes with every reauth and hence uniquely
> identifies the keys derived
>     during a reauth.

I think it does not make sense to change the PANA Session-ID 
across (re-)authentications just for this purpose.

How about using <PANA Session-Id> | <N> as the IKE pre-shared key
identifier, where N is the number of EAP-based re-authentications
occured for the Session-ID?

Yoshihiro Ohba


> 
> Any other possibilities ?
> 
> -mohan
> 
> 
> _______________________________________________
> Pana mailing 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 Dec 18 10:34:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29318
	for <pana-archive@lists.ietf.org>; Thu, 18 Dec 2003 10:34:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX0A5-0008Kv-9r; Thu, 18 Dec 2003 10:34:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX09v-0008Kk-DY
	for pana@optimus.ietf.org; Thu, 18 Dec 2003 10:33:51 -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 KAA29313
	for <pana@ietf.org>; Thu, 18 Dec 2003 10:33:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX09n-0001zo-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:33:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX09N-0001zc-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:33:18 -0500
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX09N-0001zO-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:33:17 -0500
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id hBIFX6703232;
	Thu, 18 Dec 2003 16:33:06 +0100 (MET)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail2.siemens.de (8.11.7/8.11.7) with ESMTP id hBIFX5P25822;
	Thu, 18 Dec 2003 16:33:05 +0100 (MET)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <YT366P76>; Thu, 18 Dec 2003 16:32:42 +0100
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC052D@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
        Mohan Parthasarathy
	 <mohanp@sbcglobal.net>
Cc: pana@ietf.org
Subject: RE: [Pana] Unique identifier per session
Date: Thu, 18 Dec 2003 16:32:50 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-2022-jp"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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, 

the problem i currently see is the following: 
for mobility and for rekyeing in pana itself you need to have the ability to
uniquely identify a session key (in both directions: pac-> paa and
pac<-paa). the session identifier itself is not able to provide this
functionality since it is not supposed to change. all (let's say most)
security protocols have a concept to differentiate the different versions of
a key. kerberos, for example, calls it key version number. ike and ikev2
have spis. i think we can reuse the same concepts as other security
protocols do -> no rocket science issues here. 

this issue is applicable to both, pana and pana-ipsec. 

in order to get the key naming right we need to look at some other
protocols. let me try to propose a small text until next week. 

ciao
hannes

btw, to be honest bernard aboba discussed this issue with me at a phone
conference some time ago. unfortunately, i was very busy and i had no time
to tackle this issue. 

> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Thursday, December 18, 2003 4:03 PM
> To: Mohan Parthasarathy
> Cc: pana@ietf.org
> Subject: Re: [Pana] Unique identifier per session
> 
> 
> On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan Parthasarathy wrote:
> > Hello,
> > 
> > PANA session ID uniquely identifies a session. But, it also 
> does not change
> > across a reauthentication.
> > The PANA-IPsec draft needs something unique to identify the 
> pre-shared keys
> > within a sub-session.
> > Two possibilities.
> > 
> > 1) During re-authentication, change the session ID also in 
> reauth-answer.
> > 2) Invent another ID that changes with every reauth and 
> hence uniquely
> > identifies the keys derived
> >     during a reauth.
> 
> I think it does not make sense to change the PANA Session-ID 
> across (re-)authentications just for this purpose.
> 
> How about using <PANA Session-Id> | <N> as the IKE pre-shared key
> identifier, where N is the number of EAP-based re-authentications
> occured for the Session-ID?
> 
> Yoshihiro Ohba
> 
> 
> > 
> > Any other possibilities ?
> > 
> > -mohan
> > 
> > 
> > _______________________________________________
> > Pana mailing 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 Dec 18 10:35:27 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29358
	for <pana-archive@odin.ietf.org>; Thu, 18 Dec 2003 10: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 1AX0Aw-0008Od-V6
	for pana-archive@odin.ietf.org; Thu, 18 Dec 2003 10:34:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIFYswa032274
	for pana-archive@odin.ietf.org; Thu, 18 Dec 2003 10:34:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX0Aw-0008OT-KF
	for pana-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 10:34:54 -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 KAA29337
	for <pana-web-archive@ietf.org>; Thu, 18 Dec 2003 10:34:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX0Ap-00020h-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 10:34:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX0AP-00020W-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 10:34:22 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX0AP-00020D-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 10:34:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX0A5-0008Kv-9r; Thu, 18 Dec 2003 10:34:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX09v-0008Kk-DY
	for pana@optimus.ietf.org; Thu, 18 Dec 2003 10:33:51 -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 KAA29313
	for <pana@ietf.org>; Thu, 18 Dec 2003 10:33:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX09n-0001zo-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:33:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX09N-0001zc-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:33:18 -0500
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX09N-0001zO-00
	for pana@ietf.org; Thu, 18 Dec 2003 10:33:17 -0500
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id hBIFX6703232;
	Thu, 18 Dec 2003 16:33:06 +0100 (MET)
Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99])
	by mail2.siemens.de (8.11.7/8.11.7) with ESMTP id hBIFX5P25822;
	Thu, 18 Dec 2003 16:33:05 +0100 (MET)
Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2657.72)
	id <YT366P76>; Thu, 18 Dec 2003 16:32:42 +0100
Message-ID: <2A8DB02E3018D411901B009027FD3A3F03BC052D@mchp905a.mch.sbs.de>
From: Tschofenig Hannes <hannes.tschofenig@siemens.com>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
        Mohan Parthasarathy
	 <mohanp@sbcglobal.net>
Cc: pana@ietf.org
Subject: RE: [Pana] Unique identifier per session
Date: Thu, 18 Dec 2003 16:32:50 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

hi all, 

the problem i currently see is the following: 
for mobility and for rekyeing in pana itself you need to have the ability to
uniquely identify a session key (in both directions: pac-> paa and
pac<-paa). the session identifier itself is not able to provide this
functionality since it is not supposed to change. all (let's say most)
security protocols have a concept to differentiate the different versions of
a key. kerberos, for example, calls it key version number. ike and ikev2
have spis. i think we can reuse the same concepts as other security
protocols do -> no rocket science issues here. 

this issue is applicable to both, pana and pana-ipsec. 

in order to get the key naming right we need to look at some other
protocols. let me try to propose a small text until next week. 

ciao
hannes

btw, to be honest bernard aboba discussed this issue with me at a phone
conference some time ago. unfortunately, i was very busy and i had no time
to tackle this issue. 

> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> Sent: Thursday, December 18, 2003 4:03 PM
> To: Mohan Parthasarathy
> Cc: pana@ietf.org
> Subject: Re: [Pana] Unique identifier per session
> 
> 
> On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan Parthasarathy wrote:
> > Hello,
> > 
> > PANA session ID uniquely identifies a session. But, it also 
> does not change
> > across a reauthentication.
> > The PANA-IPsec draft needs something unique to identify the 
> pre-shared keys
> > within a sub-session.
> > Two possibilities.
> > 
> > 1) During re-authentication, change the session ID also in 
> reauth-answer.
> > 2) Invent another ID that changes with every reauth and 
> hence uniquely
> > identifies the keys derived
> >     during a reauth.
> 
> I think it does not make sense to change the PANA Session-ID 
> across (re-)authentications just for this purpose.
> 
> How about using <PANA Session-Id> | <N> as the IKE pre-shared key
> identifier, where N is the number of EAP-based re-authentications
> occured for the Session-ID?
> 
> Yoshihiro Ohba
> 
> 
> > 
> > Any other possibilities ?
> > 
> > -mohan
> > 
> > 
> > _______________________________________________
> > Pana mailing 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 Dec 18 18:01:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25965
	for <pana-archive@lists.ietf.org>; Thu, 18 Dec 2003 18:01:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX78f-0005rm-W7; Thu, 18 Dec 2003 18: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 1AX78E-0005qN-M4
	for pana@optimus.ietf.org; Thu, 18 Dec 2003 18: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 SAA25912
	for <pana@ietf.org>; Thu, 18 Dec 2003 18:00:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX78B-0006qV-00
	for pana@ietf.org; Thu, 18 Dec 2003 18:00:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX78A-0006qM-00
	for pana@ietf.org; Thu, 18 Dec 2003 18:00:31 -0500
Received: from smtp812.mail.sc5.yahoo.com ([66.163.170.82])
	by ietf-mx with smtp (Exim 4.12)
	id 1AX78A-0006qA-00
	for pana@ietf.org; Thu, 18 Dec 2003 18:00:30 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login)
  by smtp812.mail.sc5.yahoo.com with SMTP; 18 Dec 2003 23:00:29 -0000
Message-ID: <009101c3c5ba$bb444bb0$681067c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <003c01c3c524$17642740$6901a8c0@adithya> <20031218150321.GA8927@steelhead>
Subject: Re: [Pana] Unique identifier per session
Date: Thu, 18 Dec 2003 15:00:28 -0800
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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 Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan Parthasarathy wrote:
> > Hello,
> >
> > PANA session ID uniquely identifies a session. But, it also does not
change
> > across a reauthentication.
> > The PANA-IPsec draft needs something unique to identify the pre-shared
keys
> > within a sub-session.
> > Two possibilities.
> >
> > 1) During re-authentication, change the session ID also in
reauth-answer.
> > 2) Invent another ID that changes with every reauth and hence uniquely
> > identifies the keys derived
> >     during a reauth.
>
> I think it does not make sense to change the PANA Session-ID
> across (re-)authentications just for this purpose.
>
> How about using <PANA Session-Id> | <N> as the IKE pre-shared key
> identifier, where N is the number of EAP-based re-authentications
> occured for the Session-ID?
>
 Can N go out of sync between the PAA and PaC ?
I am assuming that "N" is implicitly and independently arrived by PaC and
PAA.

1) PAA sends a reauth request
2) PaC sends a reauth answer and increments N by 1. This message is lost.
3) PAA retransmits reauth request
4) PaC sends a reauth answer and increments N by 1. This message is
successful.
5) PAA increments N by 1.

As you can see, N is out of sync. Is the above possible ? From what i can
understand
about retransmissions (section 4.1.4 of PANA protocol), the above looks
possible.


-mohan

> Yoshihiro Ohba
>
>
> >
> > Any other possibilities ?
> >
> > -mohan
> >
> >
> > _______________________________________________
> > Pana mailing 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 Dec 18 18:01:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25980
	for <pana-archive@odin.ietf.org>; Thu, 18 Dec 2003 18:01:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX78k-0005sW-23
	for pana-archive@odin.ietf.org; Thu, 18 Dec 2003 18:01:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBIN166F022596
	for pana-archive@odin.ietf.org; Thu, 18 Dec 2003 18: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 1AX78j-0005sN-T5
	for pana-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 18:01: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 SAA25943
	for <pana-web-archive@ietf.org>; Thu, 18 Dec 2003 18:01:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX78h-0006rb-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 18:01:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX78g-0006rU-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 18:01:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX78f-0006rR-00
	for pana-web-archive@ietf.org; Thu, 18 Dec 2003 18:01:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX78f-0005rm-W7; Thu, 18 Dec 2003 18: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 1AX78E-0005qN-M4
	for pana@optimus.ietf.org; Thu, 18 Dec 2003 18: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 SAA25912
	for <pana@ietf.org>; Thu, 18 Dec 2003 18:00:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX78B-0006qV-00
	for pana@ietf.org; Thu, 18 Dec 2003 18:00:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX78A-0006qM-00
	for pana@ietf.org; Thu, 18 Dec 2003 18:00:31 -0500
Received: from smtp812.mail.sc5.yahoo.com ([66.163.170.82])
	by ietf-mx with smtp (Exim 4.12)
	id 1AX78A-0006qA-00
	for pana@ietf.org; Thu, 18 Dec 2003 18:00:30 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login)
  by smtp812.mail.sc5.yahoo.com with SMTP; 18 Dec 2003 23:00:29 -0000
Message-ID: <009101c3c5ba$bb444bb0$681067c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <003c01c3c524$17642740$6901a8c0@adithya> <20031218150321.GA8927@steelhead>
Subject: Re: [Pana] Unique identifier per session
Date: Thu, 18 Dec 2003 15:00:28 -0800
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan Parthasarathy wrote:
> > Hello,
> >
> > PANA session ID uniquely identifies a session. But, it also does not
change
> > across a reauthentication.
> > The PANA-IPsec draft needs something unique to identify the pre-shared
keys
> > within a sub-session.
> > Two possibilities.
> >
> > 1) During re-authentication, change the session ID also in
reauth-answer.
> > 2) Invent another ID that changes with every reauth and hence uniquely
> > identifies the keys derived
> >     during a reauth.
>
> I think it does not make sense to change the PANA Session-ID
> across (re-)authentications just for this purpose.
>
> How about using <PANA Session-Id> | <N> as the IKE pre-shared key
> identifier, where N is the number of EAP-based re-authentications
> occured for the Session-ID?
>
 Can N go out of sync between the PAA and PaC ?
I am assuming that "N" is implicitly and independently arrived by PaC and
PAA.

1) PAA sends a reauth request
2) PaC sends a reauth answer and increments N by 1. This message is lost.
3) PAA retransmits reauth request
4) PaC sends a reauth answer and increments N by 1. This message is
successful.
5) PAA increments N by 1.

As you can see, N is out of sync. Is the above possible ? From what i can
understand
about retransmissions (section 4.1.4 of PANA protocol), the above looks
possible.


-mohan

> Yoshihiro Ohba
>
>
> >
> > Any other possibilities ?
> >
> > -mohan
> >
> >
> > _______________________________________________
> > Pana mailing 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  Sat Dec 27 10:53:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14641
	for <pana-archive@lists.ietf.org>; Sat, 27 Dec 2003 10:53:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AaGkP-0004vN-9R; Sat, 27 Dec 2003 10:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AaGjk-0004v3-RZ
	for pana@optimus.ietf.org; Sat, 27 Dec 2003 10:52:20 -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 KAA14630
	for <pana@ietf.org>; Sat, 27 Dec 2003 10:52:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AaGjX-0001wQ-00
	for pana@ietf.org; Sat, 27 Dec 2003 10:52:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AaGhV-0001tE-00
	for pana@ietf.org; Sat, 27 Dec 2003 10:50:03 -0500
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AaGdF-0001n6-00
	for pana@ietf.org; Sat, 27 Dec 2003 10:45:37 -0500
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 hBRFjZ700500
	for <pana@ietf.org>; Sat, 27 Dec 2003 16:45:36 +0100 (MET)
Received: from Harald (lnxekv1-05.esn.sbs.de [149.246.36.5])
	by mail1.siemens.de (8.11.7/8.11.7) with SMTP id hBRFjVL19245
	for <pana@ietf.org>; Sat, 27 Dec 2003 16:45:31 +0100 (MET)
From: "Hannes Tschofenig" <Hannes.Tschofenig@siemens.com>
To: <pana@ietf.org>
Date: Sat, 27 Dec 2003 16:45:31 +0100
Message-ID: <LMECINBNNIOBMMPEOHCLCEBICAAA.Hannes.Tschofenig@siemens.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
In-Reply-To: <003c01c3c524$17642740$6901a8c0@adithya>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by thoth.sbs.de id hBRFjZ700500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] EAP keying issues and PANA
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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,

an interesting issue with a relationship to the EAP keying work was raise=
d.
i have tried (in this first shot) to write a short text on the EAP keying
issues as they appear in PANA.

this text also includes some discussion parts where further input is
required (denoted as FOR DISCUSSION).

ciao
hannes

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

Protocol Communication Overview
-------------------------------------------

This section discusses EAP keying issues and is therefore strongly aligne=
d
with Section 1.3 of [EAP-Keying]. There the entire EAP communication is
separated into three steps. Note that the first step is actually not part=
 of
EAP itself.

- Discovery phase (phase 0)
- EAP authentication, key derivation and transport (phase 1)
- Unicast security association establishment (phase 2)

The discovery phase in PANA has the goal to find the PAA in the visited
network. This step is very hard to secure in a roaming environment. In ma=
ny
cases an additional security protection at this step would add denial of
service vulnerabilities. However, to prevent very basic denial of service
attacks, whereby an adversary floods the PAA with bogus requests, a cooki=
e
exchange is used. In PANA no capability discovery takes place at phase 0.

Phase 1 is subdivided into two phases: Phase 1a and phase 1b. In phase 1a
the PAA starts sending the initial EAP packet and thereby initiates the
authentication procedure. The PAA might implement some EAP methods or in
many cases not even a single one - it acts as a passthrough device which
interacts with a backend authentication server.

EAP methods might provide key derivation and mutual authentication. PANA
leaves the choice to network architects which EAP methods to mandate. Thi=
s
is necessary to fullfil the requirements of the larger number of deployme=
nt
scenarios. In case of wireless networks without physical or link layer
security the suggestions of [EAP-KEYING] with regard to EAP methods shoul=
d
be followed. Methods which provide session key establishment and mutual
authentication are mandated.

Since the key derivation takes place between the EAP peer and the EAP ser=
ver
it is (in many cases) necessary to transport the keying material from the
EAP server to the Authenticator (which corresponds to the PAA in PANA). T=
his
step is referred as phase 1b. If the EAP server and the Authenticator are
co-located then this step is replaced by an API call.

Since PANA signaling messages need protection a PANA SA needs to be
established between the PaC and the PAA whereby new keying material needs=
 to
be derived from the key provided by the EAP method. This step is a slight
deviation from IEEE 802.1X since PANA does not automatically create secur=
ity
associations for data traffic protection.
With the help of EAP session keys are in place and PANA needs to create,
delete and update the parameters of the PANA SA.

PANA makes a more fine-grain separation in phase 2. Parts of phase 2a are
accomplished within PANA and some parts are delegated towards IKE if IPse=
c
SA establishment is desired (see [PANA-IPsec]). Phase 2b does not exist i=
n
PANA. We will address the differences in more details in this section.

Figure 1 shows the communication overview. The figure is taken from
[EAP-Keying] and modified accordingly. The "Unicast Secure association
(phase 2a)" is replaced by the abstract term PANA Phase 2 to avoid a
terminology confusion.


   EAP peer/PaC               Authenticator/PAA           Auth. Server
   ------------               -----------------           ------------
      |<----------------------------->|                               |
      |     Discovery (phase 0)       |                               |
      |<----------------------------->|<----------------------------->|
      |   EAP auth (phase 1a)         |  AAA pass-through (optional)  |
      |                               |                               |
      |                               |<----------------------------->|
      |                               |       AAA-Key transport       |
      |                               |      (optional; phase 1b)     |
      |<----------------------------->|                               |
      |  PANA Phase 2                 |                               |
      |                               |                               |
      |<----------------------------->|                               |
      | IKE/IPsec SA establishment    |                               |
      | (optional)                    |                               |
      |                               |                               |

                            Figure 1: Communication Overview

Figure 1 ignores the fact that the Authenticator/PAA can physically be
separated from the Enforcement Point (EP). In this case IKE would not run
between the PaC and the PAA.

Phase 2 is executed after a successful EAP exchange in phase 1 (including
the transport of keying material to the Authenticator).

This phase accomplishes the following tasks (compared with the list
described in Section 1.3 of [EAP-KEYING]):

- Since PANA does not negotiate parameters during the discovery phase it =
is
not possible to confirm them. No cipher suite negotiation takes place in
PANA.

- PANA securely provides an exchange of parameters and usage modes as par=
t
of the PANA-Bind-Request message (such as Device-Id, Lifetime,
Protection-Cap AVPs).

- PANA does not derive further session keys for protection of data traffi=
c.
If an IPsec has to be established then IKE or IKEv2 is used.

- Mutual key confirmation (PAA to PaC with the help of the PANA-Bind-Requ=
est
and PaC to PAA with the help of the PANA-Bind-Answer message) is provided.
This ensure that both, the PaC and the PAA, successfully executed EAP and=
,
in the case of the PAA, were able to create the necessary keys and parame=
ter
for the PANA SA.

- The PANA SA is active immediately after the PANA SA is established (i.e=
.,
after the EAP method was successfully executed and session keys are
available).

- PANA also offers a mechanism for terminating access and to delete the
established state with the help of the PANA-Termination-Request and
PANA-Termination-Answer message. Without sending such a message the PAA a=
nd
the PaC delete their established state after lifetime expiration.

Security Associations
--------------------------

Several different security associations are created as part of the PANA
exchange. We will describe of them in some level of detail whereby some P=
ANA
specific aspects might lead to discussions.

- EAP SA

First, there is the EAP SA which is described in Section 3.1 of
[EAP-KEYING]. Due to the nature of EAP there are some restrictions on the
EAP SA such as the missing lifetime negotiation, no SA delete operation e=
tc.
Some EAP methods provide enhanced functionality by establishing additiona=
l
state which is subject to special optimizations such as "fast resume". A
detailed discussion of these issues is beyond the scope of PANA.

- AAA-Key SA / PANA SA

The AAA-Key SA described in Section 3.2 of [EAP-KEYING] seems to be the
counterpart of the PANA SA. This security association exists between the =
PaC
and the PAA. The following parameters constitute this AAA-Key SA:

      - the EAP peer name
      - the NAS/authenticator name
      - the AAA-Key
      - the AAA-Key maximum lifetime (if known)
      - the AAA attributes sent in the Access-Accept

The subsequent paragraph is an attempt to map the text in [EAP-KEYING] to
PANA.

For the PANA-SA at the PAA would have the following parameters:
     - AAA attributes (obtained via the Access-Accept)
     - Lifetime (optional?)
     - Key of the PANA SA (derived from the AAA-Key)
     - Socket-Pair information (Src/Dst IP address, Src/Port, UDP protoco=
l)
     - Session ID
The PANA-SA at the PaC contains similar attributes except for the AAA
attributes since they are invisible to the PaC.

The lifetime of the PANA SA is determined by a number of parameters. The
Lifetime AVP transmitted to the PaC is an indication for the PaC about th=
e
time duration granted for network access (and therefore also for the
lifetime of the security association).

The identities used for the PaC and the PAA are less clearly described in
PANA (and also in the EAP context). Some of these issues will be discusse=
d
again in the context of "key naming".

The identity of the NAS (in the IEEE context) or PAA (in PANA) has to be
mapped to attributes in the AAA infrastructure. Hence, within RADIUS the =
NAS
is identified by the NAS-Identifier, NAS-IP-Address and NAS-IPv6-Address
attributes. Although these attributes are kept very flexible it needs to =
be
ensured that they match to the PANA context.

---

FOR DISCUSSION: Should the PANA SA be bound to a specific PaC <-> PAA? Th=
is
is particularly of interest for mobility. It needs to be evaluated whethe=
r
the discussion in the EAP keying design team (or within the EAP working
group in general) is an issue here or even in general (e.g., a virtual NA=
S).

FOR DISCUSSION: Should a new key be derived after the lifetime of the PAN=
A
SA expires (as part of a re-authentication procedure)? This should then
require that the Lifetime AVP is mandatory in order for the PaC to perfor=
m
the same computation/protocol action. What protocol interaction is requir=
ed
for rekeying? It should be noted that the expiration of the PANA SA lifet=
ime
is not necessarily the same as a regular SA expiration. The lifetime refe=
rs
more likely to the authorization decision or some other security policy
based aspects of reauthentication interval. A clarification would be
necessary and helpful.

---

- Unicast Secure Association SA / IPsec SA

In [EAP-KEYING] a "unicast secure association SA" seems to be a link laye=
r
specific security association which is used to protect the data traffic
itself. In the PANA context the equivalent would be an IPsec SA. Since PA=
NA
IPsec uses IKE or IKEv2, it would be necessary to consider also the state
established with these protocols.

The content of the "unicast secure association SA" is described as

      - the peer port identifier (Calling-Station-Id)
      - the NAS port identifier (Called-Station-Id)
      - the unicast Transient Session Keys (TSKs)
      - the unicast secure association peer nonce
      - the unicast secure association authenticator nonce
      - the negotiated unicast capabilities and unicast ciphersuite.

For PANA IPsec usage three SAs are of relevance:
- PANA-IKE-SA
- IKE-SA/ISAKMP SA
- IPsec SA

Each of these SAs have different attributes and a different lifetime.

The content of the IPsec SA and the IKE-SA/ISAKMP SA is described in the
relevant IPsec working group documents and will not be repeated here.

The PANA-IKE-SA, which is the state information used as input to the IKE =
/
IKEv2 exchange, is of interest here. The following information is necessa=
ry:

    - the PANA-SA derived key (which is indirectly used as a pre-shared
secret for IKE/IKEv2)
    - the identities of the PaC (IP address) and EP (also IP address) (bo=
th
IP addresses are
       made available to both entities during the PANA protocol execution=
).
    - the Session ID

---

FOR DISCUSSION: A key derived from the PANA SA key should be used as inpu=
t
to the key derivation function for the IKE preshared secret key and not t=
he
MSK. Mutual key confirmation is provided for the PANA SA key.

---

>From authorization point of view it is necessary to ensure that the IPsec
SA, IKE-SA/ISAKMP-SA and the PANA-IKE-SA does not remain active after the
PANA context is removed since otherwise network resources could be consum=
ed
without authorization. Since the PaC is able to send a terminate message =
at
any time there is a need for a good API between the PAA/EP and the IKE/IP=
sec
daemon.

---

FOR DISCUSSION:
Should a newly derived key for the PANA SA lead to a new key for the
PANA-IKE SA?  My preference is NO. The PaC should, however, be able to
create a new IPsec SA at any time during the lifetime of a PANA SA.
Should the PAA be able to force the PaC to create a new IPsec SA?
Should it be possible to create more than one IPsec SA between the PaC an=
d
the EP at the same time (for example to support different quality of serv=
ice
classes)?

---



"Key Naming"
------------------

This section discusses aspects of selecting a security associations befor=
e
applying protection to signaling messages or to data traffic itself. A ne=
w
term ("key naming") was invented to describe this selection of a security
association as part of the work done in the EAP working group.

To avoid confusion with new terms, a possible definition is included here=
:

Key Naming: "Parameters used to index (=3D to select, or to point to) a
security association in order to protection the corresponding cryptograph=
ic
computation. The computation might be applied for inbound and for outboun=
d
traffic."

As a well-known example, IPsec is used to describe the meaning of key
naming. Not that inbound and outbound processing is different.  For inbou=
nd
processing an IPsec SA is selected using the destination IP address, SPI =
and
protocol type (ESP, AH).
For outbound processing the IPsec SA is selected based on the installed
policies which highly differ from environment to environment. A typical
policy might protect all traffic between a source IP address and a given
destination IP address. The applicable policy then points to the IPsec SA
that has to be applied. In some cases even more than one IPsec SA might b=
e
applied.

>From this example it can easily be seen that key naming has to consider
inbound and outbound processing separately for most protocols.

Section 3.5 of [EAP-KEYING] describes the following key names:

"EAP SA name:
 The EAP security association is uniquely named with <EAP peer name, EAP
server name, EAP Method Type, EAP peer nonce, EAP server nonce>."

Please note that the EAP SA is created as a result of a full EAP protocol
run between the EAP peer and EAP server. It is for further study why an E=
AP
SA needs to be named.

"AAA-Key Name:
The AAA-Key is named by the concatenation of the EAP SA name, "AAA-Key" a=
nd
the authenticator name."

For PANA the key naming of the EAP SA is not of interest here. The
definition of the AAA-Key name sounds like an input for a key derivation
function rather than information to select a security association. The PA=
NA
SA name which should be equivalent to the AAA-Key name is selected as
follows:

Inbound processing:
The PAA is able to select the PANA security association of an incoming
signaling message based on the session identifier.
The PaC is able to select the PANA SA of an incoming signaling message al=
so
based on the session identifier included in the header of the PANA signal=
ing
message.

Note that in both cases it would be possible to use the socket pair for t=
he
same purpose.

Outbound processing:
For outbound processing at the PAA the socket is used to determine where =
to
send the message. The socket is selected either based on a reply which is
pending or based on information from the AAA infrastructure. State must b=
e
stored to bind a message arriving from the PaC (e.g., an EAP payload in t=
he
PANA-Auth-Answer message) and the EAP message send to the EAP server via =
the
AAA infrastructure.

TBD: What information elements are used here exactly to provide these
multiplexing capabilities?

For outbound processing at the PaC we have to consider a case where the P=
aC
is equipped with multiple interfaces and hence has to select the correct
one. At the end a socket is used to select which interface to send the
messages but to deal with IP address changes at the interfaces the Sessio=
n
Identifier is used to as an intermediate pointer. Furthermore, policies
determine at which interface a message needs to be send in general (e.g.,
reauthentication or an incoming request from the PAA which requires a
response).

-----

FOR DISCUSSION: If the PaC has to run a new re-authentication step then a
new EAP SA is created. As a consequence a new key for the PANA SA is
created. This is at least true for a full EAP protocol run (but it might =
not
be true for a "fast resume" since the desired properties have not been
described yet).

If two PANA SAs (with overlapping lifetime) exist in parallel then you ne=
ed
a way to identify which SA to select. Two mechanisms are possible:
- A key version number as in Kerberos which is increased and allows to
select the refer to the latest version of the key. For the purpose of key
naming both values, the session identifier and the key version number, wo=
uld
be required.
- A new identifier (e.g., SPI) such as in IPsec which itself has no order=
ing
property. Additionally the lifetime of the security association is requir=
ed
to determine the most recent one.

Based on this, the following procedure is necessary to see whether
- Is this a problem in PANA itself?
- Is this a problem for PANA-IPsec handling?
- If so, then which approach should be chosen in PANA:
   a) key version number
   b) modification of the identifier (the session identifier in our case)=
;
This could mean that a new session identifier is created once a new key i=
s
available.

-----

For other protocols (such as IKE) rekeying turned out to be complex with =
a
number of failure cases. For IPsec SAs rekeying considerations are
dealt-with in IKE/IKEv2 itself. PANA, however, needs to make sure that bo=
th
views of the world are consistent based on the unreliable channel provide=
d
with UDP (and the various error cases of the different protocols). It sho=
uld
not be possible to create a protocol sequence whereby the PaC and the PAA
established different state.

Please note that the usage of the session identifier in the PANA protocol=
 is
different from the one in PANA-IPsec handling. The session identifier
shipped to the EP mainly helps to associate the established PANA session
(and therefore the EAP authentication and authorization) to the accountin=
g
mechanisms at the EP.

TBD: What mechanisms are available in IKE to indicate different keys? Tak=
e a
look at the PANA IPsec draft. IKE itself does not address different versi=
ons
of the pre-shared secret. The API used by IKE/IKEv2 must be able to provi=
de
this functionality.

EAP Keying requirements
-------------------------------

Section 4.2.3 of [EAP-KEYING] lists a few requirements which have to be m=
et
by the protocols using EAP. We will briefly list the requirements and
mention whether we believe that the individual requirement is met. Beyond
the requirements listed below a number of other requirements are discusse=
d
in [EAP-KEYING] which are also relevant for PANA, such as AAA and EAP met=
hod
requirements.

- Mutual proof of possession

PANA provides mutual proof of possession (i.e., mutual key confirmation) =
of
a key derived from the AAA-Key (or more precisely from the MSK which is
transported to the PAA via the AAA infrastructure).

- Key Naming

Every protocol provides mechanisms to select the security associations. P=
ANA
should be/is no different here. A previous section discusses some of the
issues which need to be addressed with regard to key naming and different
versions of the key.

- Creation and Deletion

This requirement mainly addresses the creation and deletion of phase 2
security associations. [EAP-KEYING] tightly binds the successful executio=
n
of phase 2 with security associations for securing the data traffic. This
is, however, not the case in PANA since these are separate protocols. Som=
e
questions have been raised in this context in previous sections. Deletion=
 of
the IPsec SAs MUST be accomplished indirectly with a PANA termination
message.

- Integrity and Replay Protection

Once the EAP exchange is successfully finished PANA signaling messages ca=
n
be integrity and replay protected.

- Direct operation

This requirement is highly tight to the IEEE environment where a link lay=
er
security associations are established. Hence the requirement is made that
the protocol must only run between these two entities and not between oth=
er
parties.

For PANA this is, however, not the case since the EP might be physically
separated and hence it is required to transfer derived keys to the EP. Th=
e
transfer is controlled by the PAA and hence it is not possible by an
unauthorized entity to query the PAA for keys.
Furthermore, the IPsec SA and the IKE-SA/ISAKMP SA is not available to th=
e
PAA itself.

- Derivation of transient session keys

In case of PANA the PANA protocol itself does not establish the IPsec SAs
directly.

- TSK freshness

As mentioned in the previous section PANA itself does not derive unicast
(and multicast) transient session keys. IPsec is responsible for this
purpose and provides these capabilities. IPsec SAs can be reestablished
independently of a PANA protocol.

- Bi-directional operation

This requirement addresses the establishment of uni-directional security
associations for protection of data traffic. Again, this requirement is n=
ot
directly applicable to PANA. IKE/IKEv2, however, establishes two separate
uni-lateral security associations.

- Secure capabilities negotiation

PANA does not negotiate capabilities during phase 0. However, some form o=
f
limited capability negotiation takes place secured with the PANA exchange.
Cipher suites are not negotiated in PANA.

References
-------------

[EAP-KEYING]  	B. Aboba, D. Simon, J. Arkko and H. Levkowetz: "EAP Key
Management Framework", <draft-ietf-eap-keying-00.txt>, (work in progress)=
,
October, 2003.

[PANA-IPsec]	M. Parthasarathy: =93PANA enabling IPsec based Access Contro=
l =93,
<draft-ietf-pana-ipsec-00.txt>, (work in progress), October 2003.




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


From exim@www1.ietf.org  Sat Dec 27 10:59:42 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14734
	for <pana-archive@odin.ietf.org>; Sat, 27 Dec 2003 10:59:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AaGqO-00054D-Mm
	for pana-archive@odin.ietf.org; Sat, 27 Dec 2003 10:59:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBRFxCjD019473
	for pana-archive@odin.ietf.org; Sat, 27 Dec 2003 10:59:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AaGqO-000540-G1
	for pana-web-archive@optimus.ietf.org; Sat, 27 Dec 2003 10:59: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 KAA14723
	for <pana-web-archive@ietf.org>; Sat, 27 Dec 2003 10:59:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AaGqH-00022v-00
	for pana-web-archive@ietf.org; Sat, 27 Dec 2003 10:59:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AaGo1-00020B-00
	for pana-web-archive@ietf.org; Sat, 27 Dec 2003 10:56:47 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AaGko-0001x9-00
	for pana-web-archive@ietf.org; Sat, 27 Dec 2003 10:53:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AaGkP-0004vN-9R; Sat, 27 Dec 2003 10:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AaGjk-0004v3-RZ
	for pana@optimus.ietf.org; Sat, 27 Dec 2003 10:52:20 -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 KAA14630
	for <pana@ietf.org>; Sat, 27 Dec 2003 10:52:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AaGjX-0001wQ-00
	for pana@ietf.org; Sat, 27 Dec 2003 10:52:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AaGhV-0001tE-00
	for pana@ietf.org; Sat, 27 Dec 2003 10:50:03 -0500
Received: from thoth.sbs.de ([192.35.17.2])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AaGdF-0001n6-00
	for pana@ietf.org; Sat, 27 Dec 2003 10:45:37 -0500
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 hBRFjZ700500
	for <pana@ietf.org>; Sat, 27 Dec 2003 16:45:36 +0100 (MET)
Received: from Harald (lnxekv1-05.esn.sbs.de [149.246.36.5])
	by mail1.siemens.de (8.11.7/8.11.7) with SMTP id hBRFjVL19245
	for <pana@ietf.org>; Sat, 27 Dec 2003 16:45:31 +0100 (MET)
From: "Hannes Tschofenig" <Hannes.Tschofenig@siemens.com>
To: <pana@ietf.org>
Date: Sat, 27 Dec 2003 16:45:31 +0100
Message-ID: <LMECINBNNIOBMMPEOHCLCEBICAAA.Hannes.Tschofenig@siemens.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
In-Reply-To: <003c01c3c524$17642740$6901a8c0@adithya>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by thoth.sbs.de id hBRFjZ700500
Content-Transfer-Encoding: quoted-printable
Subject: [Pana] EAP keying issues and PANA
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

hi all,

an interesting issue with a relationship to the EAP keying work was raise=
d.
i have tried (in this first shot) to write a short text on the EAP keying
issues as they appear in PANA.

this text also includes some discussion parts where further input is
required (denoted as FOR DISCUSSION).

ciao
hannes

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

Protocol Communication Overview
-------------------------------------------

This section discusses EAP keying issues and is therefore strongly aligne=
d
with Section 1.3 of [EAP-Keying]. There the entire EAP communication is
separated into three steps. Note that the first step is actually not part=
 of
EAP itself.

- Discovery phase (phase 0)
- EAP authentication, key derivation and transport (phase 1)
- Unicast security association establishment (phase 2)

The discovery phase in PANA has the goal to find the PAA in the visited
network. This step is very hard to secure in a roaming environment. In ma=
ny
cases an additional security protection at this step would add denial of
service vulnerabilities. However, to prevent very basic denial of service
attacks, whereby an adversary floods the PAA with bogus requests, a cooki=
e
exchange is used. In PANA no capability discovery takes place at phase 0.

Phase 1 is subdivided into two phases: Phase 1a and phase 1b. In phase 1a
the PAA starts sending the initial EAP packet and thereby initiates the
authentication procedure. The PAA might implement some EAP methods or in
many cases not even a single one - it acts as a passthrough device which
interacts with a backend authentication server.

EAP methods might provide key derivation and mutual authentication. PANA
leaves the choice to network architects which EAP methods to mandate. Thi=
s
is necessary to fullfil the requirements of the larger number of deployme=
nt
scenarios. In case of wireless networks without physical or link layer
security the suggestions of [EAP-KEYING] with regard to EAP methods shoul=
d
be followed. Methods which provide session key establishment and mutual
authentication are mandated.

Since the key derivation takes place between the EAP peer and the EAP ser=
ver
it is (in many cases) necessary to transport the keying material from the
EAP server to the Authenticator (which corresponds to the PAA in PANA). T=
his
step is referred as phase 1b. If the EAP server and the Authenticator are
co-located then this step is replaced by an API call.

Since PANA signaling messages need protection a PANA SA needs to be
established between the PaC and the PAA whereby new keying material needs=
 to
be derived from the key provided by the EAP method. This step is a slight
deviation from IEEE 802.1X since PANA does not automatically create secur=
ity
associations for data traffic protection.
With the help of EAP session keys are in place and PANA needs to create,
delete and update the parameters of the PANA SA.

PANA makes a more fine-grain separation in phase 2. Parts of phase 2a are
accomplished within PANA and some parts are delegated towards IKE if IPse=
c
SA establishment is desired (see [PANA-IPsec]). Phase 2b does not exist i=
n
PANA. We will address the differences in more details in this section.

Figure 1 shows the communication overview. The figure is taken from
[EAP-Keying] and modified accordingly. The "Unicast Secure association
(phase 2a)" is replaced by the abstract term PANA Phase 2 to avoid a
terminology confusion.


   EAP peer/PaC               Authenticator/PAA           Auth. Server
   ------------               -----------------           ------------
      |<----------------------------->|                               |
      |     Discovery (phase 0)       |                               |
      |<----------------------------->|<----------------------------->|
      |   EAP auth (phase 1a)         |  AAA pass-through (optional)  |
      |                               |                               |
      |                               |<----------------------------->|
      |                               |       AAA-Key transport       |
      |                               |      (optional; phase 1b)     |
      |<----------------------------->|                               |
      |  PANA Phase 2                 |                               |
      |                               |                               |
      |<----------------------------->|                               |
      | IKE/IPsec SA establishment    |                               |
      | (optional)                    |                               |
      |                               |                               |

                            Figure 1: Communication Overview

Figure 1 ignores the fact that the Authenticator/PAA can physically be
separated from the Enforcement Point (EP). In this case IKE would not run
between the PaC and the PAA.

Phase 2 is executed after a successful EAP exchange in phase 1 (including
the transport of keying material to the Authenticator).

This phase accomplishes the following tasks (compared with the list
described in Section 1.3 of [EAP-KEYING]):

- Since PANA does not negotiate parameters during the discovery phase it =
is
not possible to confirm them. No cipher suite negotiation takes place in
PANA.

- PANA securely provides an exchange of parameters and usage modes as par=
t
of the PANA-Bind-Request message (such as Device-Id, Lifetime,
Protection-Cap AVPs).

- PANA does not derive further session keys for protection of data traffi=
c.
If an IPsec has to be established then IKE or IKEv2 is used.

- Mutual key confirmation (PAA to PaC with the help of the PANA-Bind-Requ=
est
and PaC to PAA with the help of the PANA-Bind-Answer message) is provided.
This ensure that both, the PaC and the PAA, successfully executed EAP and=
,
in the case of the PAA, were able to create the necessary keys and parame=
ter
for the PANA SA.

- The PANA SA is active immediately after the PANA SA is established (i.e=
.,
after the EAP method was successfully executed and session keys are
available).

- PANA also offers a mechanism for terminating access and to delete the
established state with the help of the PANA-Termination-Request and
PANA-Termination-Answer message. Without sending such a message the PAA a=
nd
the PaC delete their established state after lifetime expiration.

Security Associations
--------------------------

Several different security associations are created as part of the PANA
exchange. We will describe of them in some level of detail whereby some P=
ANA
specific aspects might lead to discussions.

- EAP SA

First, there is the EAP SA which is described in Section 3.1 of
[EAP-KEYING]. Due to the nature of EAP there are some restrictions on the
EAP SA such as the missing lifetime negotiation, no SA delete operation e=
tc.
Some EAP methods provide enhanced functionality by establishing additiona=
l
state which is subject to special optimizations such as "fast resume". A
detailed discussion of these issues is beyond the scope of PANA.

- AAA-Key SA / PANA SA

The AAA-Key SA described in Section 3.2 of [EAP-KEYING] seems to be the
counterpart of the PANA SA. This security association exists between the =
PaC
and the PAA. The following parameters constitute this AAA-Key SA:

      - the EAP peer name
      - the NAS/authenticator name
      - the AAA-Key
      - the AAA-Key maximum lifetime (if known)
      - the AAA attributes sent in the Access-Accept

The subsequent paragraph is an attempt to map the text in [EAP-KEYING] to
PANA.

For the PANA-SA at the PAA would have the following parameters:
     - AAA attributes (obtained via the Access-Accept)
     - Lifetime (optional?)
     - Key of the PANA SA (derived from the AAA-Key)
     - Socket-Pair information (Src/Dst IP address, Src/Port, UDP protoco=
l)
     - Session ID
The PANA-SA at the PaC contains similar attributes except for the AAA
attributes since they are invisible to the PaC.

The lifetime of the PANA SA is determined by a number of parameters. The
Lifetime AVP transmitted to the PaC is an indication for the PaC about th=
e
time duration granted for network access (and therefore also for the
lifetime of the security association).

The identities used for the PaC and the PAA are less clearly described in
PANA (and also in the EAP context). Some of these issues will be discusse=
d
again in the context of "key naming".

The identity of the NAS (in the IEEE context) or PAA (in PANA) has to be
mapped to attributes in the AAA infrastructure. Hence, within RADIUS the =
NAS
is identified by the NAS-Identifier, NAS-IP-Address and NAS-IPv6-Address
attributes. Although these attributes are kept very flexible it needs to =
be
ensured that they match to the PANA context.

---

FOR DISCUSSION: Should the PANA SA be bound to a specific PaC <-> PAA? Th=
is
is particularly of interest for mobility. It needs to be evaluated whethe=
r
the discussion in the EAP keying design team (or within the EAP working
group in general) is an issue here or even in general (e.g., a virtual NA=
S).

FOR DISCUSSION: Should a new key be derived after the lifetime of the PAN=
A
SA expires (as part of a re-authentication procedure)? This should then
require that the Lifetime AVP is mandatory in order for the PaC to perfor=
m
the same computation/protocol action. What protocol interaction is requir=
ed
for rekeying? It should be noted that the expiration of the PANA SA lifet=
ime
is not necessarily the same as a regular SA expiration. The lifetime refe=
rs
more likely to the authorization decision or some other security policy
based aspects of reauthentication interval. A clarification would be
necessary and helpful.

---

- Unicast Secure Association SA / IPsec SA

In [EAP-KEYING] a "unicast secure association SA" seems to be a link laye=
r
specific security association which is used to protect the data traffic
itself. In the PANA context the equivalent would be an IPsec SA. Since PA=
NA
IPsec uses IKE or IKEv2, it would be necessary to consider also the state
established with these protocols.

The content of the "unicast secure association SA" is described as

      - the peer port identifier (Calling-Station-Id)
      - the NAS port identifier (Called-Station-Id)
      - the unicast Transient Session Keys (TSKs)
      - the unicast secure association peer nonce
      - the unicast secure association authenticator nonce
      - the negotiated unicast capabilities and unicast ciphersuite.

For PANA IPsec usage three SAs are of relevance:
- PANA-IKE-SA
- IKE-SA/ISAKMP SA
- IPsec SA

Each of these SAs have different attributes and a different lifetime.

The content of the IPsec SA and the IKE-SA/ISAKMP SA is described in the
relevant IPsec working group documents and will not be repeated here.

The PANA-IKE-SA, which is the state information used as input to the IKE =
/
IKEv2 exchange, is of interest here. The following information is necessa=
ry:

    - the PANA-SA derived key (which is indirectly used as a pre-shared
secret for IKE/IKEv2)
    - the identities of the PaC (IP address) and EP (also IP address) (bo=
th
IP addresses are
       made available to both entities during the PANA protocol execution=
).
    - the Session ID

---

FOR DISCUSSION: A key derived from the PANA SA key should be used as inpu=
t
to the key derivation function for the IKE preshared secret key and not t=
he
MSK. Mutual key confirmation is provided for the PANA SA key.

---

>From authorization point of view it is necessary to ensure that the IPsec
SA, IKE-SA/ISAKMP-SA and the PANA-IKE-SA does not remain active after the
PANA context is removed since otherwise network resources could be consum=
ed
without authorization. Since the PaC is able to send a terminate message =
at
any time there is a need for a good API between the PAA/EP and the IKE/IP=
sec
daemon.

---

FOR DISCUSSION:
Should a newly derived key for the PANA SA lead to a new key for the
PANA-IKE SA?  My preference is NO. The PaC should, however, be able to
create a new IPsec SA at any time during the lifetime of a PANA SA.
Should the PAA be able to force the PaC to create a new IPsec SA?
Should it be possible to create more than one IPsec SA between the PaC an=
d
the EP at the same time (for example to support different quality of serv=
ice
classes)?

---



"Key Naming"
------------------

This section discusses aspects of selecting a security associations befor=
e
applying protection to signaling messages or to data traffic itself. A ne=
w
term ("key naming") was invented to describe this selection of a security
association as part of the work done in the EAP working group.

To avoid confusion with new terms, a possible definition is included here=
:

Key Naming: "Parameters used to index (=3D to select, or to point to) a
security association in order to protection the corresponding cryptograph=
ic
computation. The computation might be applied for inbound and for outboun=
d
traffic."

As a well-known example, IPsec is used to describe the meaning of key
naming. Not that inbound and outbound processing is different.  For inbou=
nd
processing an IPsec SA is selected using the destination IP address, SPI =
and
protocol type (ESP, AH).
For outbound processing the IPsec SA is selected based on the installed
policies which highly differ from environment to environment. A typical
policy might protect all traffic between a source IP address and a given
destination IP address. The applicable policy then points to the IPsec SA
that has to be applied. In some cases even more than one IPsec SA might b=
e
applied.

>From this example it can easily be seen that key naming has to consider
inbound and outbound processing separately for most protocols.

Section 3.5 of [EAP-KEYING] describes the following key names:

"EAP SA name:
 The EAP security association is uniquely named with <EAP peer name, EAP
server name, EAP Method Type, EAP peer nonce, EAP server nonce>."

Please note that the EAP SA is created as a result of a full EAP protocol
run between the EAP peer and EAP server. It is for further study why an E=
AP
SA needs to be named.

"AAA-Key Name:
The AAA-Key is named by the concatenation of the EAP SA name, "AAA-Key" a=
nd
the authenticator name."

For PANA the key naming of the EAP SA is not of interest here. The
definition of the AAA-Key name sounds like an input for a key derivation
function rather than information to select a security association. The PA=
NA
SA name which should be equivalent to the AAA-Key name is selected as
follows:

Inbound processing:
The PAA is able to select the PANA security association of an incoming
signaling message based on the session identifier.
The PaC is able to select the PANA SA of an incoming signaling message al=
so
based on the session identifier included in the header of the PANA signal=
ing
message.

Note that in both cases it would be possible to use the socket pair for t=
he
same purpose.

Outbound processing:
For outbound processing at the PAA the socket is used to determine where =
to
send the message. The socket is selected either based on a reply which is
pending or based on information from the AAA infrastructure. State must b=
e
stored to bind a message arriving from the PaC (e.g., an EAP payload in t=
he
PANA-Auth-Answer message) and the EAP message send to the EAP server via =
the
AAA infrastructure.

TBD: What information elements are used here exactly to provide these
multiplexing capabilities?

For outbound processing at the PaC we have to consider a case where the P=
aC
is equipped with multiple interfaces and hence has to select the correct
one. At the end a socket is used to select which interface to send the
messages but to deal with IP address changes at the interfaces the Sessio=
n
Identifier is used to as an intermediate pointer. Furthermore, policies
determine at which interface a message needs to be send in general (e.g.,
reauthentication or an incoming request from the PAA which requires a
response).

-----

FOR DISCUSSION: If the PaC has to run a new re-authentication step then a
new EAP SA is created. As a consequence a new key for the PANA SA is
created. This is at least true for a full EAP protocol run (but it might =
not
be true for a "fast resume" since the desired properties have not been
described yet).

If two PANA SAs (with overlapping lifetime) exist in parallel then you ne=
ed
a way to identify which SA to select. Two mechanisms are possible:
- A key version number as in Kerberos which is increased and allows to
select the refer to the latest version of the key. For the purpose of key
naming both values, the session identifier and the key version number, wo=
uld
be required.
- A new identifier (e.g., SPI) such as in IPsec which itself has no order=
ing
property. Additionally the lifetime of the security association is requir=
ed
to determine the most recent one.

Based on this, the following procedure is necessary to see whether
- Is this a problem in PANA itself?
- Is this a problem for PANA-IPsec handling?
- If so, then which approach should be chosen in PANA:
   a) key version number
   b) modification of the identifier (the session identifier in our case)=
;
This could mean that a new session identifier is created once a new key i=
s
available.

-----

For other protocols (such as IKE) rekeying turned out to be complex with =
a
number of failure cases. For IPsec SAs rekeying considerations are
dealt-with in IKE/IKEv2 itself. PANA, however, needs to make sure that bo=
th
views of the world are consistent based on the unreliable channel provide=
d
with UDP (and the various error cases of the different protocols). It sho=
uld
not be possible to create a protocol sequence whereby the PaC and the PAA
established different state.

Please note that the usage of the session identifier in the PANA protocol=
 is
different from the one in PANA-IPsec handling. The session identifier
shipped to the EP mainly helps to associate the established PANA session
(and therefore the EAP authentication and authorization) to the accountin=
g
mechanisms at the EP.

TBD: What mechanisms are available in IKE to indicate different keys? Tak=
e a
look at the PANA IPsec draft. IKE itself does not address different versi=
ons
of the pre-shared secret. The API used by IKE/IKEv2 must be able to provi=
de
this functionality.

EAP Keying requirements
-------------------------------

Section 4.2.3 of [EAP-KEYING] lists a few requirements which have to be m=
et
by the protocols using EAP. We will briefly list the requirements and
mention whether we believe that the individual requirement is met. Beyond
the requirements listed below a number of other requirements are discusse=
d
in [EAP-KEYING] which are also relevant for PANA, such as AAA and EAP met=
hod
requirements.

- Mutual proof of possession

PANA provides mutual proof of possession (i.e., mutual key confirmation) =
of
a key derived from the AAA-Key (or more precisely from the MSK which is
transported to the PAA via the AAA infrastructure).

- Key Naming

Every protocol provides mechanisms to select the security associations. P=
ANA
should be/is no different here. A previous section discusses some of the
issues which need to be addressed with regard to key naming and different
versions of the key.

- Creation and Deletion

This requirement mainly addresses the creation and deletion of phase 2
security associations. [EAP-KEYING] tightly binds the successful executio=
n
of phase 2 with security associations for securing the data traffic. This
is, however, not the case in PANA since these are separate protocols. Som=
e
questions have been raised in this context in previous sections. Deletion=
 of
the IPsec SAs MUST be accomplished indirectly with a PANA termination
message.

- Integrity and Replay Protection

Once the EAP exchange is successfully finished PANA signaling messages ca=
n
be integrity and replay protected.

- Direct operation

This requirement is highly tight to the IEEE environment where a link lay=
er
security associations are established. Hence the requirement is made that
the protocol must only run between these two entities and not between oth=
er
parties.

For PANA this is, however, not the case since the EP might be physically
separated and hence it is required to transfer derived keys to the EP. Th=
e
transfer is controlled by the PAA and hence it is not possible by an
unauthorized entity to query the PAA for keys.
Furthermore, the IPsec SA and the IKE-SA/ISAKMP SA is not available to th=
e
PAA itself.

- Derivation of transient session keys

In case of PANA the PANA protocol itself does not establish the IPsec SAs
directly.

- TSK freshness

As mentioned in the previous section PANA itself does not derive unicast
(and multicast) transient session keys. IPsec is responsible for this
purpose and provides these capabilities. IPsec SAs can be reestablished
independently of a PANA protocol.

- Bi-directional operation

This requirement addresses the establishment of uni-directional security
associations for protection of data traffic. Again, this requirement is n=
ot
directly applicable to PANA. IKE/IKEv2, however, establishes two separate
uni-lateral security associations.

- Secure capabilities negotiation

PANA does not negotiate capabilities during phase 0. However, some form o=
f
limited capability negotiation takes place secured with the PANA exchange.
Cipher suites are not negotiated in PANA.

References
-------------

[EAP-KEYING]  	B. Aboba, D. Simon, J. Arkko and H. Levkowetz: "EAP Key
Management Framework", <draft-ietf-eap-keying-00.txt>, (work in progress)=
,
October, 2003.

[PANA-IPsec]	M. Parthasarathy: =93PANA enabling IPsec based Access Contro=
l =93,
<draft-ietf-pana-ipsec-00.txt>, (work in progress), October 2003.




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



From pana-admin@ietf.org  Tue Dec 30 02:31:52 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13848
	for <pana-archive@lists.ietf.org>; Tue, 30 Dec 2003 02:31:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbELH-00041X-KI; Tue, 30 Dec 2003 02:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbEKU-0003xN-W2
	for pana@optimus.ietf.org; Tue, 30 Dec 2003 02:30:15 -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 CAA13818
	for <pana@ietf.org>; Tue, 30 Dec 2003 02:30:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbEKQ-0003rh-00
	for pana@ietf.org; Tue, 30 Dec 2003 02:30:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbEId-0003iS-00
	for pana@ietf.org; Tue, 30 Dec 2003 02:28:19 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbEHw-0003g7-00
	for pana@ietf.org; Tue, 30 Dec 2003 02:27:36 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBU7RXY9020215;
	Tue, 30 Dec 2003 16:27:33 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBU7RXmQ029662;
	Tue, 30 Dec 2003 16:27:33 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id SAA29655 ; Tue, 30 Dec 2003 16:27:33 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id QAA16908; Tue, 30 Dec 2003 16:27:32 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id QAA09765; Tue, 30 Dec 2003 16:27:32 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hBU7RVpn007905;
	Tue, 30 Dec 2003 16:27:31 +0900 (JST)
Received: from steelhead ([159.119.168.63]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HQP00K8X61TPM@tsbpo1.po.toshiba.co.jp>; Tue,
 30 Dec 2003 16:27:30 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AbEEo-0007YB-00; Mon, 29 Dec 2003 23:24:22 -0800
Date: Mon, 29 Dec 2003 23:24:22 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Unique identifier per session
In-reply-to: <009101c3c5ba$bb444bb0$681067c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031230072422.GA8328@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: <003c01c3c524$17642740$6901a8c0@adithya>
 <20031218150321.GA8927@steelhead> <009101c3c5ba$bb444bb0$681067c0@adithya>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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,

On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan Parthasarathy wrote:
> 
> > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan Parthasarathy wrote:
> > > Hello,
> > >
> > > PANA session ID uniquely identifies a session. But, it also does not
> change
> > > across a reauthentication.
> > > The PANA-IPsec draft needs something unique to identify the pre-shared
> keys
> > > within a sub-session.
> > > Two possibilities.
> > >
> > > 1) During re-authentication, change the session ID also in
> reauth-answer.
> > > 2) Invent another ID that changes with every reauth and hence uniquely
> > > identifies the keys derived
> > >     during a reauth.
> >
> > I think it does not make sense to change the PANA Session-ID
> > across (re-)authentications just for this purpose.
> >
> > How about using <PANA Session-Id> | <N> as the IKE pre-shared key
> > identifier, where N is the number of EAP-based re-authentications
> > occured for the Session-ID?
> >
>  Can N go out of sync between the PAA and PaC ?
> I am assuming that "N" is implicitly and independently arrived by PaC and
> PAA.
> 
> 1) PAA sends a reauth request
> 2) PaC sends a reauth answer and increments N by 1. This message is lost.
> 3) PAA retransmits reauth request
> 4) PaC sends a reauth answer and increments N by 1. This message is
> successful.
> 5) PAA increments N by 1.

Which type of "reauth" do you mean?  I am assuming that the IKE
pre-shared key is updated when an EAP-based re-authentication occurs.
When the other type of reauthentication based on
PANA-Reauth-Request/Answer exchange occurs, I don't think the IKE
pre-shared key needs to be updated because there is no change in the
EAP Master Session Key in this case.  For EAP-based re-authentication,
synchronization on EAP Master Session Key derivation can be made
because PANA-Bind-Request that carries an EAP-Success message is
acknowledged with PANA-Bind-Answer message.

Yoshihiro Ohba



> 
> As you can see, N is out of sync. Is the above possible ? From what i can
> understand
> about retransmissions (section 4.1.4 of PANA protocol), the above looks
> possible.
> 
> 
> -mohan
> 
> > Yoshihiro Ohba
> >
> >
> > >
> > > Any other possibilities ?
> > >
> > > -mohan
> > >
> > >
> > > _______________________________________________
> > > Pana mailing 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  Tue Dec 30 02:34:52 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14022
	for <pana-archive@odin.ietf.org>; Tue, 30 Dec 2003 02:34:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbEOU-0004CW-Fr
	for pana-archive@odin.ietf.org; Tue, 30 Dec 2003 02:34:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBU7YMNd016149
	for pana-archive@odin.ietf.org; Tue, 30 Dec 2003 02:34:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbEOU-0004CO-3o
	for pana-web-archive@optimus.ietf.org; Tue, 30 Dec 2003 02:34:22 -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 CAA14007
	for <pana-web-archive@ietf.org>; Tue, 30 Dec 2003 02:34:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbEOQ-0003yf-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 02:34:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbEMU-0003w3-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 02:32:19 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbELZ-0003tY-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 02:31:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbELH-00041X-KI; Tue, 30 Dec 2003 02:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbEKU-0003xN-W2
	for pana@optimus.ietf.org; Tue, 30 Dec 2003 02:30:15 -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 CAA13818
	for <pana@ietf.org>; Tue, 30 Dec 2003 02:30:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbEKQ-0003rh-00
	for pana@ietf.org; Tue, 30 Dec 2003 02:30:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbEId-0003iS-00
	for pana@ietf.org; Tue, 30 Dec 2003 02:28:19 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbEHw-0003g7-00
	for pana@ietf.org; Tue, 30 Dec 2003 02:27:36 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBU7RXY9020215;
	Tue, 30 Dec 2003 16:27:33 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBU7RXmQ029662;
	Tue, 30 Dec 2003 16:27:33 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id SAA29655 ; Tue, 30 Dec 2003 16:27:33 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id QAA16908; Tue, 30 Dec 2003 16:27:32 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id QAA09765; Tue, 30 Dec 2003 16:27:32 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hBU7RVpn007905;
	Tue, 30 Dec 2003 16:27:31 +0900 (JST)
Received: from steelhead ([159.119.168.63]) by tsbpo1.po.toshiba.co.jp
 (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4)
 with ESMTP id <0HQP00K8X61TPM@tsbpo1.po.toshiba.co.jp>; Tue,
 30 Dec 2003 16:27:30 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1AbEEo-0007YB-00; Mon, 29 Dec 2003 23:24:22 -0800
Date: Mon, 29 Dec 2003 23:24:22 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Unique identifier per session
In-reply-to: <009101c3c5ba$bb444bb0$681067c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031230072422.GA8328@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: <003c01c3c524$17642740$6901a8c0@adithya>
 <20031218150321.GA8927@steelhead> <009101c3c5ba$bb444bb0$681067c0@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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Hi Mohan,

On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan Parthasarathy wrote:
> 
> > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan Parthasarathy wrote:
> > > Hello,
> > >
> > > PANA session ID uniquely identifies a session. But, it also does not
> change
> > > across a reauthentication.
> > > The PANA-IPsec draft needs something unique to identify the pre-shared
> keys
> > > within a sub-session.
> > > Two possibilities.
> > >
> > > 1) During re-authentication, change the session ID also in
> reauth-answer.
> > > 2) Invent another ID that changes with every reauth and hence uniquely
> > > identifies the keys derived
> > >     during a reauth.
> >
> > I think it does not make sense to change the PANA Session-ID
> > across (re-)authentications just for this purpose.
> >
> > How about using <PANA Session-Id> | <N> as the IKE pre-shared key
> > identifier, where N is the number of EAP-based re-authentications
> > occured for the Session-ID?
> >
>  Can N go out of sync between the PAA and PaC ?
> I am assuming that "N" is implicitly and independently arrived by PaC and
> PAA.
> 
> 1) PAA sends a reauth request
> 2) PaC sends a reauth answer and increments N by 1. This message is lost.
> 3) PAA retransmits reauth request
> 4) PaC sends a reauth answer and increments N by 1. This message is
> successful.
> 5) PAA increments N by 1.

Which type of "reauth" do you mean?  I am assuming that the IKE
pre-shared key is updated when an EAP-based re-authentication occurs.
When the other type of reauthentication based on
PANA-Reauth-Request/Answer exchange occurs, I don't think the IKE
pre-shared key needs to be updated because there is no change in the
EAP Master Session Key in this case.  For EAP-based re-authentication,
synchronization on EAP Master Session Key derivation can be made
because PANA-Bind-Request that carries an EAP-Success message is
acknowledged with PANA-Bind-Answer message.

Yoshihiro Ohba



> 
> As you can see, N is out of sync. Is the above possible ? From what i can
> understand
> about retransmissions (section 4.1.4 of PANA protocol), the above looks
> possible.
> 
> 
> -mohan
> 
> > Yoshihiro Ohba
> >
> >
> > >
> > > Any other possibilities ?
> > >
> > > -mohan
> > >
> > >
> > > _______________________________________________
> > > Pana mailing 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  Tue Dec 30 06:59:29 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20662
	for <pana-archive@lists.ietf.org>; Tue, 30 Dec 2003 06:59: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 1AbIWa-0003jW-MB; Tue, 30 Dec 2003 06:59:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbIVU-0003jB-Ag
	for pana@optimus.ietf.org; Tue, 30 Dec 2003 06:58: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 GAA20622
	for <pana@ietf.org>; Tue, 30 Dec 2003 06:57:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbIVG-00036v-00
	for pana@ietf.org; Tue, 30 Dec 2003 06:57:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbIRK-00033t-00
	for pana@ietf.org; Tue, 30 Dec 2003 06:53:35 -0500
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbIOb-0002zr-00
	for pana@ietf.org; Tue, 30 Dec 2003 06:50:45 -0500
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by david.siemens.de (8.11.7/8.11.7) with ESMTP id hBUBoGr13716;
	Tue, 30 Dec 2003 12:50:16 +0100 (MET)
Received: from joe (lnxekv1-25.esn.sbs.de [149.246.36.25])
	by mail2.siemens.de (8.11.7/8.11.7) with ESMTP id hBUBoEP08191;
	Tue, 30 Dec 2003 12:50:14 +0100 (MET)
From: "Hannes Tschofenig" <Hannes.Tschofenig@siemens.com>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
        "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>
Cc: <pana@ietf.org>
Subject: RE: [Pana] Unique identifier per session
Date: Tue, 30 Dec 2003 12:47:59 +0100
Message-ID: <000c01c3ceca$e21ec990$010aa8c0@joe>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <20031230072422.GA8328@steelhead>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 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

hi yoshi,=20
hi mohan,=20

i tried to raise the same question with my text: is it necessary to =
update
the ike preshared secret with every re-authentication protocol run?=20

we have multiple re-authentication procedures here:=20

- PANA re-authentication
- EAP full re-authentication (full run between the eap peer and the eap
server)
- EAP 'fast resume'
- EAP run between the eap peer and the local aaa server (based on cached
keys) (in some cases you could draw a relationship between 'fast resume'
here.=20

at the discussion in the eap keying design team i was not able to figure =
out
whether a fast resume actually produces new session keys.=20

i would argue to update the PANA SA if an EAP run produces new keys. we =
have
to discuss how we can handle rekeying (i.e., where multiple PANA SAs are
concurrently active) within PANA at least.

hence, i would strongly argue against executing a new IKE exchange =
wheneven
you do one of these re-authentication steps. that would certainly hit
performance and is not necessary and even the entrophy argument does not
hold here since you can always create new IPsec SAs based on a quick =
mode
exchange.=20

a few comments on the ability to have multiple IKE pre-shared secrets
currently for IKE protocol runs:=20

ike does not support this type of scenario easily. as stated in =
[ipsec-pana]
in aggressive mode you could use the ID_KEY_ID with the (session id ||
version number) as a key name. this would ensure that you always select =
the
most recent key and in case of failures it would be possible to fallback =
to
the previous sa. however, this does not work with ike main mode =
(pre-shared
secret authentication) since the ID payload is sent after authentication
(with message 5). this already caused problems in road warrior cases.=20

from this point of view it would be good to use aggressive mode only =
(also
from the number of messages). however, the availability of aggressive =
mode
in existing implementations is not widespread.=20

ciao
hannes


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]=20
> Sent: Dienstag, 30. Dezember 2003 08:24
> To: Mohan Parthasarathy
> Cc: Yoshihiro Ohba; pana@ietf.org
> Subject: Re: [Pana] Unique identifier per session
>=20
>=20
> Hi Mohan,
>=20
> On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan Parthasarathy wrote:
> >=20
> > > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan=20
> Parthasarathy wrote:
> > > > Hello,
> > > >
> > > > PANA session ID uniquely identifies a session. But, it also does
> not
> > change
> > > > across a reauthentication.
> > > > The PANA-IPsec draft needs something unique to identify the
> pre-shared
> > keys
> > > > within a sub-session.
> > > > Two possibilities.
> > > >
> > > > 1) During re-authentication, change the session ID also in
> > reauth-answer.
> > > > 2) Invent another ID that changes with every reauth and hence
> uniquely
> > > > identifies the keys derived
> > > >     during a reauth.
> > >
> > > I think it does not make sense to change the PANA=20
> Session-ID across=20
> > > (re-)authentications just for this purpose.
> > >
> > > How about using <PANA Session-Id> | <N> as the IKE pre-shared key=20
> > > identifier, where N is the number of EAP-based re-authentications=20
> > > occured for the Session-ID?
> > >
> >  Can N go out of sync between the PAA and PaC ?
> > I am assuming that "N" is implicitly and independently=20
> arrived by PaC
> and
> > PAA.
> >=20
> > 1) PAA sends a reauth request
> > 2) PaC sends a reauth answer and increments N by 1. This message is
> lost.
> > 3) PAA retransmits reauth request
> > 4) PaC sends a reauth answer and increments N by 1. This message is=20
> > successful.
> > 5) PAA increments N by 1.
>=20
> Which type of "reauth" do you mean?  I am assuming that the=20
> IKE pre-shared key is updated when an EAP-based=20
> re-authentication occurs. When the other type of=20
> reauthentication based on PANA-Reauth-Request/Answer exchange=20
> occurs, I don't think the IKE pre-shared key needs to be=20
> updated because there is no change in the EAP Master Session=20
> Key in this case.  For EAP-based re-authentication,=20
> synchronization on EAP Master Session Key derivation can be=20
> made because PANA-Bind-Request that carries an EAP-Success=20
> message is acknowledged with PANA-Bind-Answer message.
>=20
> Yoshihiro Ohba
>=20
>=20
>=20
> >=20
> > As you can see, N is out of sync. Is the above possible ?=20
> From what i
> can
> > understand
> > about retransmissions (section 4.1.4 of PANA protocol), the above
> looks
> > possible.
> >=20
> >=20
> > -mohan
> >=20
> > > Yoshihiro Ohba
> > >
> > >
> > > >
> > > > Any other possibilities ?
> > > >
> > > > -mohan
> > > >
> > > >
> > > > _______________________________________________
> > > > Pana mailing list
> > > > Pana@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pana
> > >
> > > _______________________________________________
> > > 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  Tue Dec 30 07:08:43 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20827
	for <pana-archive@odin.ietf.org>; Tue, 30 Dec 2003 07:08:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbIfU-0004AX-HA
	for pana-archive@odin.ietf.org; Tue, 30 Dec 2003 07:08:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBUC8Ci1016019
	for pana-archive@odin.ietf.org; Tue, 30 Dec 2003 07:08:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbIfU-0004AI-CP
	for pana-web-archive@optimus.ietf.org; Tue, 30 Dec 2003 07:08: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 HAA20815
	for <pana-web-archive@ietf.org>; Tue, 30 Dec 2003 07:08:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbIfL-0003Os-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 07:08:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbIbA-0003Fz-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 07:03:45 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbIWt-0003AN-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 06:59:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbIWa-0003jW-MB; Tue, 30 Dec 2003 06:59:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbIVU-0003jB-Ag
	for pana@optimus.ietf.org; Tue, 30 Dec 2003 06:58: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 GAA20622
	for <pana@ietf.org>; Tue, 30 Dec 2003 06:57:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbIVG-00036v-00
	for pana@ietf.org; Tue, 30 Dec 2003 06:57:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbIRK-00033t-00
	for pana@ietf.org; Tue, 30 Dec 2003 06:53:35 -0500
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbIOb-0002zr-00
	for pana@ietf.org; Tue, 30 Dec 2003 06:50:45 -0500
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11])
	by david.siemens.de (8.11.7/8.11.7) with ESMTP id hBUBoGr13716;
	Tue, 30 Dec 2003 12:50:16 +0100 (MET)
Received: from joe (lnxekv1-25.esn.sbs.de [149.246.36.25])
	by mail2.siemens.de (8.11.7/8.11.7) with ESMTP id hBUBoEP08191;
	Tue, 30 Dec 2003 12:50:14 +0100 (MET)
From: "Hannes Tschofenig" <Hannes.Tschofenig@siemens.com>
To: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>,
        "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>
Cc: <pana@ietf.org>
Subject: RE: [Pana] Unique identifier per session
Date: Tue, 30 Dec 2003 12:47:59 +0100
Message-ID: <000c01c3ceca$e21ec990$010aa8c0@joe>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <20031230072422.GA8328@steelhead>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

hi yoshi,=20
hi mohan,=20

i tried to raise the same question with my text: is it necessary to =
update
the ike preshared secret with every re-authentication protocol run?=20

we have multiple re-authentication procedures here:=20

- PANA re-authentication
- EAP full re-authentication (full run between the eap peer and the eap
server)
- EAP 'fast resume'
- EAP run between the eap peer and the local aaa server (based on cached
keys) (in some cases you could draw a relationship between 'fast resume'
here.=20

at the discussion in the eap keying design team i was not able to figure =
out
whether a fast resume actually produces new session keys.=20

i would argue to update the PANA SA if an EAP run produces new keys. we =
have
to discuss how we can handle rekeying (i.e., where multiple PANA SAs are
concurrently active) within PANA at least.

hence, i would strongly argue against executing a new IKE exchange =
wheneven
you do one of these re-authentication steps. that would certainly hit
performance and is not necessary and even the entrophy argument does not
hold here since you can always create new IPsec SAs based on a quick =
mode
exchange.=20

a few comments on the ability to have multiple IKE pre-shared secrets
currently for IKE protocol runs:=20

ike does not support this type of scenario easily. as stated in =
[ipsec-pana]
in aggressive mode you could use the ID_KEY_ID with the (session id ||
version number) as a key name. this would ensure that you always select =
the
most recent key and in case of failures it would be possible to fallback =
to
the previous sa. however, this does not work with ike main mode =
(pre-shared
secret authentication) since the ID payload is sent after authentication
(with message 5). this already caused problems in road warrior cases.=20

from this point of view it would be good to use aggressive mode only =
(also
from the number of messages). however, the availability of aggressive =
mode
in existing implementations is not widespread.=20

ciao
hannes


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]=20
> Sent: Dienstag, 30. Dezember 2003 08:24
> To: Mohan Parthasarathy
> Cc: Yoshihiro Ohba; pana@ietf.org
> Subject: Re: [Pana] Unique identifier per session
>=20
>=20
> Hi Mohan,
>=20
> On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan Parthasarathy wrote:
> >=20
> > > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan=20
> Parthasarathy wrote:
> > > > Hello,
> > > >
> > > > PANA session ID uniquely identifies a session. But, it also does
> not
> > change
> > > > across a reauthentication.
> > > > The PANA-IPsec draft needs something unique to identify the
> pre-shared
> > keys
> > > > within a sub-session.
> > > > Two possibilities.
> > > >
> > > > 1) During re-authentication, change the session ID also in
> > reauth-answer.
> > > > 2) Invent another ID that changes with every reauth and hence
> uniquely
> > > > identifies the keys derived
> > > >     during a reauth.
> > >
> > > I think it does not make sense to change the PANA=20
> Session-ID across=20
> > > (re-)authentications just for this purpose.
> > >
> > > How about using <PANA Session-Id> | <N> as the IKE pre-shared key=20
> > > identifier, where N is the number of EAP-based re-authentications=20
> > > occured for the Session-ID?
> > >
> >  Can N go out of sync between the PAA and PaC ?
> > I am assuming that "N" is implicitly and independently=20
> arrived by PaC
> and
> > PAA.
> >=20
> > 1) PAA sends a reauth request
> > 2) PaC sends a reauth answer and increments N by 1. This message is
> lost.
> > 3) PAA retransmits reauth request
> > 4) PaC sends a reauth answer and increments N by 1. This message is=20
> > successful.
> > 5) PAA increments N by 1.
>=20
> Which type of "reauth" do you mean?  I am assuming that the=20
> IKE pre-shared key is updated when an EAP-based=20
> re-authentication occurs. When the other type of=20
> reauthentication based on PANA-Reauth-Request/Answer exchange=20
> occurs, I don't think the IKE pre-shared key needs to be=20
> updated because there is no change in the EAP Master Session=20
> Key in this case.  For EAP-based re-authentication,=20
> synchronization on EAP Master Session Key derivation can be=20
> made because PANA-Bind-Request that carries an EAP-Success=20
> message is acknowledged with PANA-Bind-Answer message.
>=20
> Yoshihiro Ohba
>=20
>=20
>=20
> >=20
> > As you can see, N is out of sync. Is the above possible ?=20
> From what i
> can
> > understand
> > about retransmissions (section 4.1.4 of PANA protocol), the above
> looks
> > possible.
> >=20
> >=20
> > -mohan
> >=20
> > > Yoshihiro Ohba
> > >
> > >
> > > >
> > > > Any other possibilities ?
> > > >
> > > > -mohan
> > > >
> > > >
> > > > _______________________________________________
> > > > Pana mailing list
> > > > Pana@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/pana
> > >
> > > _______________________________________________
> > > 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  Tue Dec 30 14:11:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03774
	for <pana-archive@lists.ietf.org>; Tue, 30 Dec 2003 14:11:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbPGf-0001BB-Oa; Tue, 30 Dec 2003 14:11:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbPG4-0001AN-3a
	for pana@optimus.ietf.org; Tue, 30 Dec 2003 14:10:24 -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 OAA03741
	for <pana@ietf.org>; Tue, 30 Dec 2003 14:10:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbPG0-0003Jt-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:10:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbPE6-0003GE-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:08:23 -0500
Received: from smtp813.mail.sc5.yahoo.com ([66.163.170.83])
	by ietf-mx with smtp (Exim 4.12)
	id 1AbPCW-0003Du-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:06:44 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login)
  by smtp813.mail.sc5.yahoo.com with SMTP; 30 Dec 2003 19:06:42 -0000
Message-ID: <003501c3cf08$12569ce0$681067c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <003c01c3c524$17642740$6901a8c0@adithya> <20031218150321.GA8927@steelhead> <009101c3c5ba$bb444bb0$681067c0@adithya> <20031230072422.GA8328@steelhead>
Subject: Re: [Pana] Unique identifier per session
Date: Tue, 30 Dec 2003 11:06:46 -0800
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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,
>
> On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan Parthasarathy wrote:
> >
> > > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan Parthasarathy wrote:
> > > > Hello,
> > > >
> > > > PANA session ID uniquely identifies a session. But, it also does not
> > change
> > > > across a reauthentication.
> > > > The PANA-IPsec draft needs something unique to identify the
pre-shared
> > keys
> > > > within a sub-session.
> > > > Two possibilities.
> > > >
> > > > 1) During re-authentication, change the session ID also in
> > reauth-answer.
> > > > 2) Invent another ID that changes with every reauth and hence
uniquely
> > > > identifies the keys derived
> > > >     during a reauth.
> > >
> > > I think it does not make sense to change the PANA Session-ID
> > > across (re-)authentications just for this purpose.
> > >
> > > How about using <PANA Session-Id> | <N> as the IKE pre-shared key
> > > identifier, where N is the number of EAP-based re-authentications
> > > occured for the Session-ID?
> > >
> >  Can N go out of sync between the PAA and PaC ?
> > I am assuming that "N" is implicitly and independently arrived by PaC
and
> > PAA.
> >
> > 1) PAA sends a reauth request
> > 2) PaC sends a reauth answer and increments N by 1. This message is
lost.
> > 3) PAA retransmits reauth request
> > 4) PaC sends a reauth answer and increments N by 1. This message is
> > successful.
> > 5) PAA increments N by 1.
>
> Which type of "reauth" do you mean?  I am assuming that the IKE
> pre-shared key is updated when an EAP-based re-authentication occurs.
> When the other type of reauthentication based on
> PANA-Reauth-Request/Answer exchange occurs, I don't think the IKE
> pre-shared key needs to be updated because there is no change in the
> EAP Master Session Key in this case.

Okay.

>  For EAP-based re-authentication,
> synchronization on EAP Master Session Key derivation can be made
> because PANA-Bind-Request that carries an EAP-Success message is
> acknowledged with PANA-Bind-Answer message.
>
I am still not clear i guess. When does the PaC increment "N" ? Assume that
PaC increments "N" as soon as it sends the PANA-Bind-Answer message.
Now, if this message is lost. PANA-Bind-Request will be retransmitted by the
PAA. PaC will send the PANA-Bind-Answer message and this time it should
not increment "N" because it is not a new  EAP re-authentication. So,
PaC increments "N" by 1 only for the first PANA-Bind-Answer message sent
as a result of EAP reauthentication. This extra state seems a bit tricky to
me.
And this also assumes that PANA-Bind-Request message will not be used
for anything else in the future.  Is that a safe assumption ?

Carrying extra information in the PANA-Bind-Request information seems less
error prone to me. Perhaps i am missing something ...

-mohan

> Yoshihiro Ohba
>
>
>
> >
> > As you can see, N is out of sync. Is the above possible ? From what i
can
> > understand
> > about retransmissions (section 4.1.4 of PANA protocol), the above looks
> > possible.
> >
> >
> > -mohan
> >
> > > Yoshihiro Ohba
> > >
> > >
> > > >
> > > > Any other possibilities ?
> > > >
> > > > -mohan
> > > >
> > > >
> > > > _______________________________________________
> > > > Pana mailing 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  Tue Dec 30 14:15:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04042
	for <pana-archive@odin.ietf.org>; Tue, 30 Dec 2003 14:15: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 1AbPKM-0001JX-Pb
	for pana-archive@odin.ietf.org; Tue, 30 Dec 2003 14:14:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBUJEovY005045
	for pana-archive@odin.ietf.org; Tue, 30 Dec 2003 14:14:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbPKM-0001JI-K5
	for pana-web-archive@optimus.ietf.org; Tue, 30 Dec 2003 14:14:50 -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 OAA03962
	for <pana-web-archive@ietf.org>; Tue, 30 Dec 2003 14:14:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbPKK-0003lh-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 14:14:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbPIU-0003a7-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 14:12:55 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbPGh-0003R3-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 14:11:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbPGf-0001BB-Oa; Tue, 30 Dec 2003 14:11:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbPG4-0001AN-3a
	for pana@optimus.ietf.org; Tue, 30 Dec 2003 14:10:24 -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 OAA03741
	for <pana@ietf.org>; Tue, 30 Dec 2003 14:10:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbPG0-0003Jt-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:10:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbPE6-0003GE-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:08:23 -0500
Received: from smtp813.mail.sc5.yahoo.com ([66.163.170.83])
	by ietf-mx with smtp (Exim 4.12)
	id 1AbPCW-0003Du-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:06:44 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login)
  by smtp813.mail.sc5.yahoo.com with SMTP; 30 Dec 2003 19:06:42 -0000
Message-ID: <003501c3cf08$12569ce0$681067c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Yoshihiro Ohba" <yohba@tari.toshiba.com>
Cc: <pana@ietf.org>
References: <003c01c3c524$17642740$6901a8c0@adithya> <20031218150321.GA8927@steelhead> <009101c3c5ba$bb444bb0$681067c0@adithya> <20031230072422.GA8328@steelhead>
Subject: Re: [Pana] Unique identifier per session
Date: Tue, 30 Dec 2003 11:06:46 -0800
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> Hi Mohan,
>
> On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan Parthasarathy wrote:
> >
> > > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan Parthasarathy wrote:
> > > > Hello,
> > > >
> > > > PANA session ID uniquely identifies a session. But, it also does not
> > change
> > > > across a reauthentication.
> > > > The PANA-IPsec draft needs something unique to identify the
pre-shared
> > keys
> > > > within a sub-session.
> > > > Two possibilities.
> > > >
> > > > 1) During re-authentication, change the session ID also in
> > reauth-answer.
> > > > 2) Invent another ID that changes with every reauth and hence
uniquely
> > > > identifies the keys derived
> > > >     during a reauth.
> > >
> > > I think it does not make sense to change the PANA Session-ID
> > > across (re-)authentications just for this purpose.
> > >
> > > How about using <PANA Session-Id> | <N> as the IKE pre-shared key
> > > identifier, where N is the number of EAP-based re-authentications
> > > occured for the Session-ID?
> > >
> >  Can N go out of sync between the PAA and PaC ?
> > I am assuming that "N" is implicitly and independently arrived by PaC
and
> > PAA.
> >
> > 1) PAA sends a reauth request
> > 2) PaC sends a reauth answer and increments N by 1. This message is
lost.
> > 3) PAA retransmits reauth request
> > 4) PaC sends a reauth answer and increments N by 1. This message is
> > successful.
> > 5) PAA increments N by 1.
>
> Which type of "reauth" do you mean?  I am assuming that the IKE
> pre-shared key is updated when an EAP-based re-authentication occurs.
> When the other type of reauthentication based on
> PANA-Reauth-Request/Answer exchange occurs, I don't think the IKE
> pre-shared key needs to be updated because there is no change in the
> EAP Master Session Key in this case.

Okay.

>  For EAP-based re-authentication,
> synchronization on EAP Master Session Key derivation can be made
> because PANA-Bind-Request that carries an EAP-Success message is
> acknowledged with PANA-Bind-Answer message.
>
I am still not clear i guess. When does the PaC increment "N" ? Assume that
PaC increments "N" as soon as it sends the PANA-Bind-Answer message.
Now, if this message is lost. PANA-Bind-Request will be retransmitted by the
PAA. PaC will send the PANA-Bind-Answer message and this time it should
not increment "N" because it is not a new  EAP re-authentication. So,
PaC increments "N" by 1 only for the first PANA-Bind-Answer message sent
as a result of EAP reauthentication. This extra state seems a bit tricky to
me.
And this also assumes that PANA-Bind-Request message will not be used
for anything else in the future.  Is that a safe assumption ?

Carrying extra information in the PANA-Bind-Request information seems less
error prone to me. Perhaps i am missing something ...

-mohan

> Yoshihiro Ohba
>
>
>
> >
> > As you can see, N is out of sync. Is the above possible ? From what i
can
> > understand
> > about retransmissions (section 4.1.4 of PANA protocol), the above looks
> > possible.
> >
> >
> > -mohan
> >
> > > Yoshihiro Ohba
> > >
> > >
> > > >
> > > > Any other possibilities ?
> > > >
> > > > -mohan
> > > >
> > > >
> > > > _______________________________________________
> > > > Pana mailing 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  Tue Dec 30 14:15:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04083
	for <pana-archive@lists.ietf.org>; Tue, 30 Dec 2003 14:15:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbPKa-0001L3-85; Tue, 30 Dec 2003 14:15:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbPKR-0001Jf-7F
	for pana@optimus.ietf.org; Tue, 30 Dec 2003 14:14:55 -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 OAA03977
	for <pana@ietf.org>; Tue, 30 Dec 2003 14:14:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbPKO-0003mR-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:14:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbPIZ-0003b2-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:13:00 -0500
Received: from smtp813.mail.sc5.yahoo.com ([66.163.170.83])
	by ietf-mx with smtp (Exim 4.12)
	id 1AbPGt-0003RN-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:11:16 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login)
  by smtp813.mail.sc5.yahoo.com with SMTP; 30 Dec 2003 19:11:14 -0000
Message-ID: <005701c3cf08$b43b0280$681067c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Tschofenig Hannes" <hannes.tschofenig@siemens.com>
Cc: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <003e01c3cf08$220951f0$681067c0@adithya>
Subject: Re: [Pana] Unique identifier per session
Date: Tue, 30 Dec 2003 11:11:18 -0800
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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 tried to raise the same question with my text: is it necessary to
update
> the ike preshared secret with every re-authentication protocol run?
>
> we have multiple re-authentication procedures here:
>
> - PANA re-authentication
> - EAP full re-authentication (full run between the eap peer and the eap
> server)
> - EAP 'fast resume'
> - EAP run between the eap peer and the local aaa server (based on cached
> keys) (in some cases you could draw a relationship between 'fast resume'
> here.
>
> at the discussion in the eap keying design team i was not able to figure
out
> whether a fast resume actually produces new session keys.
>
> i would argue to update the PANA SA if an EAP run produces new keys. we
have
> to discuss how we can handle rekeying (i.e., where multiple PANA SAs are
> concurrently active) within PANA at least.
>
> hence, i would strongly argue against executing a new IKE exchange
wheneven
> you do one of these re-authentication steps. that would certainly hit
> performance and is not necessary and even the entrophy argument does not
> hold here since you can always create new IPsec SAs based on a quick mode
> exchange.
>
Agreed.

> a few comments on the ability to have multiple IKE pre-shared secrets
> currently for IKE protocol runs:
>
> ike does not support this type of scenario easily. as stated in
[ipsec-pana]
> in aggressive mode you could use the ID_KEY_ID with the (session id ||
> version number) as a key name. this would ensure that you always select
the

What do you mean by version number ?

> most recent key and in case of failures it would be possible to fallback
to
> the previous sa. however, this does not work with ike main mode
(pre-shared
> secret authentication) since the ID payload is sent after authentication
> (with message 5). this already caused problems in road warrior cases.
>
> from this point of view it would be good to use aggressive mode only (also
> from the number of messages). however, the availability of aggressive mode
> in existing implementations is not widespread.
>
My next update (soon to be out) already clarifies that only aggressive mode
 MUST be supported because of the problem you mention above with main-mode.

-mohan

> ciao
> hannes
>
>
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Dienstag, 30. Dezember 2003 08:24
> > To: Mohan Parthasarathy
> > Cc: Yoshihiro Ohba; pana@ietf.org
> > Subject: Re: [Pana] Unique identifier per session
> >
> >
> > Hi Mohan,
> >
> > On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan Parthasarathy wrote:
> > >
> > > > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan
> > Parthasarathy wrote:
> > > > > Hello,
> > > > >
> > > > > PANA session ID uniquely identifies a session. But, it also does
> > not
> > > change
> > > > > across a reauthentication.
> > > > > The PANA-IPsec draft needs something unique to identify the
> > pre-shared
> > > keys
> > > > > within a sub-session.
> > > > > Two possibilities.
> > > > >
> > > > > 1) During re-authentication, change the session ID also in
> > > reauth-answer.
> > > > > 2) Invent another ID that changes with every reauth and hence
> > uniquely
> > > > > identifies the keys derived
> > > > >     during a reauth.
> > > >
> > > > I think it does not make sense to change the PANA
> > Session-ID across
> > > > (re-)authentications just for this purpose.
> > > >
> > > > How about using <PANA Session-Id> | <N> as the IKE pre-shared key
> > > > identifier, where N is the number of EAP-based re-authentications
> > > > occured for the Session-ID?
> > > >
> > >  Can N go out of sync between the PAA and PaC ?
> > > I am assuming that "N" is implicitly and independently
> > arrived by PaC
> > and
> > > PAA.
> > >
> > > 1) PAA sends a reauth request
> > > 2) PaC sends a reauth answer and increments N by 1. This message is
> > lost.
> > > 3) PAA retransmits reauth request
> > > 4) PaC sends a reauth answer and increments N by 1. This message is
> > > successful.
> > > 5) PAA increments N by 1.
> >
> > Which type of "reauth" do you mean?  I am assuming that the
> > IKE pre-shared key is updated when an EAP-based
> > re-authentication occurs. When the other type of
> > reauthentication based on PANA-Reauth-Request/Answer exchange
> > occurs, I don't think the IKE pre-shared key needs to be
> > updated because there is no change in the EAP Master Session
> > Key in this case.  For EAP-based re-authentication,
> > synchronization on EAP Master Session Key derivation can be
> > made because PANA-Bind-Request that carries an EAP-Success
> > message is acknowledged with PANA-Bind-Answer message.
> >
> > Yoshihiro Ohba
> >
> >
> >
> > >
> > > As you can see, N is out of sync. Is the above possible ?
> > From what i
> > can
> > > understand
> > > about retransmissions (section 4.1.4 of PANA protocol), the above
> > looks
> > > possible.
> > >
> > >
> > > -mohan
> > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > >
> > > > > Any other possibilities ?
> > > > >
> > > > > -mohan
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Pana mailing 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  Tue Dec 30 14:18:59 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04386
	for <pana-archive@odin.ietf.org>; Tue, 30 Dec 2003 14:18:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbPNv-0001QU-EK
	for pana-archive@odin.ietf.org; Tue, 30 Dec 2003 14:18:31 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBUJIVIT005476
	for pana-archive@odin.ietf.org; Tue, 30 Dec 2003 14:18:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbPNv-0001QF-8l
	for pana-web-archive@optimus.ietf.org; Tue, 30 Dec 2003 14:18:31 -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 OAA04353
	for <pana-web-archive@ietf.org>; Tue, 30 Dec 2003 14:18:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbPNs-00046A-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 14:18:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbPM9-0003yi-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 14:16:42 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbPKZ-0003oU-00
	for pana-web-archive@ietf.org; Tue, 30 Dec 2003 14:15:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbPKa-0001L3-85; Tue, 30 Dec 2003 14:15:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbPKR-0001Jf-7F
	for pana@optimus.ietf.org; Tue, 30 Dec 2003 14:14:55 -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 OAA03977
	for <pana@ietf.org>; Tue, 30 Dec 2003 14:14:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbPKO-0003mR-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:14:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbPIZ-0003b2-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:13:00 -0500
Received: from smtp813.mail.sc5.yahoo.com ([66.163.170.83])
	by ietf-mx with smtp (Exim 4.12)
	id 1AbPGt-0003RN-00
	for pana@ietf.org; Tue, 30 Dec 2003 14:11:16 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login)
  by smtp813.mail.sc5.yahoo.com with SMTP; 30 Dec 2003 19:11:14 -0000
Message-ID: <005701c3cf08$b43b0280$681067c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Tschofenig Hannes" <hannes.tschofenig@siemens.com>
Cc: "Yoshihiro Ohba" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <003e01c3cf08$220951f0$681067c0@adithya>
Subject: Re: [Pana] Unique identifier per session
Date: Tue, 30 Dec 2003 11:11:18 -0800
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

  > i tried to raise the same question with my text: is it necessary to
update
> the ike preshared secret with every re-authentication protocol run?
>
> we have multiple re-authentication procedures here:
>
> - PANA re-authentication
> - EAP full re-authentication (full run between the eap peer and the eap
> server)
> - EAP 'fast resume'
> - EAP run between the eap peer and the local aaa server (based on cached
> keys) (in some cases you could draw a relationship between 'fast resume'
> here.
>
> at the discussion in the eap keying design team i was not able to figure
out
> whether a fast resume actually produces new session keys.
>
> i would argue to update the PANA SA if an EAP run produces new keys. we
have
> to discuss how we can handle rekeying (i.e., where multiple PANA SAs are
> concurrently active) within PANA at least.
>
> hence, i would strongly argue against executing a new IKE exchange
wheneven
> you do one of these re-authentication steps. that would certainly hit
> performance and is not necessary and even the entrophy argument does not
> hold here since you can always create new IPsec SAs based on a quick mode
> exchange.
>
Agreed.

> a few comments on the ability to have multiple IKE pre-shared secrets
> currently for IKE protocol runs:
>
> ike does not support this type of scenario easily. as stated in
[ipsec-pana]
> in aggressive mode you could use the ID_KEY_ID with the (session id ||
> version number) as a key name. this would ensure that you always select
the

What do you mean by version number ?

> most recent key and in case of failures it would be possible to fallback
to
> the previous sa. however, this does not work with ike main mode
(pre-shared
> secret authentication) since the ID payload is sent after authentication
> (with message 5). this already caused problems in road warrior cases.
>
> from this point of view it would be good to use aggressive mode only (also
> from the number of messages). however, the availability of aggressive mode
> in existing implementations is not widespread.
>
My next update (soon to be out) already clarifies that only aggressive mode
 MUST be supported because of the problem you mention above with main-mode.

-mohan

> ciao
> hannes
>
>
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > Sent: Dienstag, 30. Dezember 2003 08:24
> > To: Mohan Parthasarathy
> > Cc: Yoshihiro Ohba; pana@ietf.org
> > Subject: Re: [Pana] Unique identifier per session
> >
> >
> > Hi Mohan,
> >
> > On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan Parthasarathy wrote:
> > >
> > > > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan
> > Parthasarathy wrote:
> > > > > Hello,
> > > > >
> > > > > PANA session ID uniquely identifies a session. But, it also does
> > not
> > > change
> > > > > across a reauthentication.
> > > > > The PANA-IPsec draft needs something unique to identify the
> > pre-shared
> > > keys
> > > > > within a sub-session.
> > > > > Two possibilities.
> > > > >
> > > > > 1) During re-authentication, change the session ID also in
> > > reauth-answer.
> > > > > 2) Invent another ID that changes with every reauth and hence
> > uniquely
> > > > > identifies the keys derived
> > > > >     during a reauth.
> > > >
> > > > I think it does not make sense to change the PANA
> > Session-ID across
> > > > (re-)authentications just for this purpose.
> > > >
> > > > How about using <PANA Session-Id> | <N> as the IKE pre-shared key
> > > > identifier, where N is the number of EAP-based re-authentications
> > > > occured for the Session-ID?
> > > >
> > >  Can N go out of sync between the PAA and PaC ?
> > > I am assuming that "N" is implicitly and independently
> > arrived by PaC
> > and
> > > PAA.
> > >
> > > 1) PAA sends a reauth request
> > > 2) PaC sends a reauth answer and increments N by 1. This message is
> > lost.
> > > 3) PAA retransmits reauth request
> > > 4) PaC sends a reauth answer and increments N by 1. This message is
> > > successful.
> > > 5) PAA increments N by 1.
> >
> > Which type of "reauth" do you mean?  I am assuming that the
> > IKE pre-shared key is updated when an EAP-based
> > re-authentication occurs. When the other type of
> > reauthentication based on PANA-Reauth-Request/Answer exchange
> > occurs, I don't think the IKE pre-shared key needs to be
> > updated because there is no change in the EAP Master Session
> > Key in this case.  For EAP-based re-authentication,
> > synchronization on EAP Master Session Key derivation can be
> > made because PANA-Bind-Request that carries an EAP-Success
> > message is acknowledged with PANA-Bind-Answer message.
> >
> > Yoshihiro Ohba
> >
> >
> >
> > >
> > > As you can see, N is out of sync. Is the above possible ?
> > From what i
> > can
> > > understand
> > > about retransmissions (section 4.1.4 of PANA protocol), the above
> > looks
> > > possible.
> > >
> > >
> > > -mohan
> > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > > >
> > > > > Any other possibilities ?
> > > > >
> > > > > -mohan
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Pana mailing 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 Dec 31 04:07:39 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01540
	for <pana-archive@lists.ietf.org>; Wed, 31 Dec 2003 04:07:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbcJi-0005iH-Ci; Wed, 31 Dec 2003 04:07:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbcJH-0005f8-Iv
	for pana@optimus.ietf.org; Wed, 31 Dec 2003 04:06:35 -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 EAA01411
	for <pana@ietf.org>; Wed, 31 Dec 2003 04:06:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbcJE-0000Ie-00
	for pana@ietf.org; Wed, 31 Dec 2003 04:06:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbcHK-0000B8-00
	for pana@ietf.org; Wed, 31 Dec 2003 04:04:35 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbcFd-00005y-00
	for pana@ietf.org; Wed, 31 Dec 2003 04:02:49 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBV92nY9027694;
	Wed, 31 Dec 2003 18:02:49 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBV92nsx021221;
	Wed, 31 Dec 2003 18:02:49 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id UAA21220 ; Wed, 31 Dec 2003 18:02:48 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id SAA10561; Wed, 31 Dec 2003 18:02:48 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id SAA21274; Wed, 31 Dec 2003 18:02:48 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hBV92lpn011755;
	Wed, 31 Dec 2003 18:02:47 +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 <0HQR00J2554LP7@tsbpo1.po.toshiba.co.jp>; Wed,
 31 Dec 2003 18:02:46 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1Abbqj-00088g-00; Wed, 31 Dec 2003 00:37:05 -0800
Date: Wed, 31 Dec 2003 00:37:05 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Unique identifier per session
In-reply-to: <003501c3cf08$12569ce0$681067c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031231083705.GC29855@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: <003c01c3c524$17642740$6901a8c0@adithya>
 <20031218150321.GA8927@steelhead> <009101c3c5ba$bb444bb0$681067c0@adithya>
 <20031230072422.GA8328@steelhead> <003501c3cf08$12569ce0$681067c0@adithya>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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, Dec 30, 2003 at 11:06:46AM -0800, Mohan Parthasarathy wrote:
> >  For EAP-based re-authentication,
> > synchronization on EAP Master Session Key derivation can be made
> > because PANA-Bind-Request that carries an EAP-Success message is
> > acknowledged with PANA-Bind-Answer message.
> >
> I am still not clear i guess. When does the PaC increment "N" ? Assume that
> PaC increments "N" as soon as it sends the PANA-Bind-Answer message.
> Now, if this message is lost. PANA-Bind-Request will be retransmitted by the
> PAA. PaC will send the PANA-Bind-Answer message and this time it should
> not increment "N" because it is not a new  EAP re-authentication. So,
> PaC increments "N" by 1 only for the first PANA-Bind-Answer message sent
> as a result of EAP reauthentication. This extra state seems a bit tricky to
> me.

OK, now I understand your point.  Constructing a key name by using
implicit information might be tricky as you mentioned above.

> And this also assumes that PANA-Bind-Request message will not be used
> for anything else in the future.  Is that a safe assumption ?
> 
> Carrying extra information in the PANA-Bind-Request information seems less
> error prone to me. Perhaps i am missing something ...

I agree.  Carrying extra information is robuster and I think this also
covers the scenario where EAP-based re-authentication may not always
generate a new MSK (as mentioned by Hannes.)

Yoshihiro Ohba


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


From exim@www1.ietf.org  Wed Dec 31 04:11:10 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01719
	for <pana-archive@odin.ietf.org>; Wed, 31 Dec 2003 04:11:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbcND-00068R-KL
	for pana-archive@odin.ietf.org; Wed, 31 Dec 2003 04:10:40 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBV9AdDi023580
	for pana-archive@odin.ietf.org; Wed, 31 Dec 2003 04:10:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbcNB-00068F-Hd
	for pana-web-archive@optimus.ietf.org; Wed, 31 Dec 2003 04:10:37 -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 EAA01615
	for <pana-web-archive@ietf.org>; Wed, 31 Dec 2003 04:10:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbcN9-0000VU-00
	for pana-web-archive@ietf.org; Wed, 31 Dec 2003 04:10:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbcLK-0000RH-00
	for pana-web-archive@ietf.org; Wed, 31 Dec 2003 04:08:43 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbcJo-0000Og-00
	for pana-web-archive@ietf.org; Wed, 31 Dec 2003 04:07:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbcJi-0005iH-Ci; Wed, 31 Dec 2003 04:07:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbcJH-0005f8-Iv
	for pana@optimus.ietf.org; Wed, 31 Dec 2003 04:06:35 -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 EAA01411
	for <pana@ietf.org>; Wed, 31 Dec 2003 04:06:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbcJE-0000Ie-00
	for pana@ietf.org; Wed, 31 Dec 2003 04:06:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbcHK-0000B8-00
	for pana@ietf.org; Wed, 31 Dec 2003 04:04:35 -0500
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbcFd-00005y-00
	for pana@ietf.org; Wed, 31 Dec 2003 04:02:49 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id hBV92nY9027694;
	Wed, 31 Dec 2003 18:02:49 +0900 (JST)
Received: (from root@localhost)
	by tsb-wall.toshiba.co.jp  id hBV92nsx021221;
	Wed, 31 Dec 2003 18:02:49 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id UAA21220 ; Wed, 31 Dec 2003 18:02:48 +0900
Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp 
	id SAA10561; Wed, 31 Dec 2003 18:02:48 +0900 (JST)
Received: from tsb-sgw.toshiba.co.jp by toshiba.co.jp id SAA21274; Wed, 31 Dec 2003 18:02:48 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp
	by tsb-sgw.toshiba.co.jp  with ESMTP id hBV92lpn011755;
	Wed, 31 Dec 2003 18:02:47 +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 <0HQR00J2554LP7@tsbpo1.po.toshiba.co.jp>; Wed,
 31 Dec 2003 18:02:46 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian))
 id 1Abbqj-00088g-00; Wed, 31 Dec 2003 00:37:05 -0800
Date: Wed, 31 Dec 2003 00:37:05 -0800
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] Unique identifier per session
In-reply-to: <003501c3cf08$12569ce0$681067c0@adithya>
To: Mohan Parthasarathy <mohanp@sbcglobal.net>
Cc: Yoshihiro Ohba <yohba@tari.toshiba.com>, pana@ietf.org
Message-id: <20031231083705.GC29855@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: <003c01c3c524$17642740$6901a8c0@adithya>
 <20031218150321.GA8927@steelhead> <009101c3c5ba$bb444bb0$681067c0@adithya>
 <20031230072422.GA8328@steelhead> <003501c3cf08$12569ce0$681067c0@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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

On Tue, Dec 30, 2003 at 11:06:46AM -0800, Mohan Parthasarathy wrote:
> >  For EAP-based re-authentication,
> > synchronization on EAP Master Session Key derivation can be made
> > because PANA-Bind-Request that carries an EAP-Success message is
> > acknowledged with PANA-Bind-Answer message.
> >
> I am still not clear i guess. When does the PaC increment "N" ? Assume that
> PaC increments "N" as soon as it sends the PANA-Bind-Answer message.
> Now, if this message is lost. PANA-Bind-Request will be retransmitted by the
> PAA. PaC will send the PANA-Bind-Answer message and this time it should
> not increment "N" because it is not a new  EAP re-authentication. So,
> PaC increments "N" by 1 only for the first PANA-Bind-Answer message sent
> as a result of EAP reauthentication. This extra state seems a bit tricky to
> me.

OK, now I understand your point.  Constructing a key name by using
implicit information might be tricky as you mentioned above.

> And this also assumes that PANA-Bind-Request message will not be used
> for anything else in the future.  Is that a safe assumption ?
> 
> Carrying extra information in the PANA-Bind-Request information seems less
> error prone to me. Perhaps i am missing something ...

I agree.  Carrying extra information is robuster and I think this also
covers the scenario where EAP-based re-authentication may not always
generate a new MSK (as mentioned by Hannes.)

Yoshihiro Ohba


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



From pana-admin@ietf.org  Wed Dec 31 06:25:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09506
	for <pana-archive@lists.ietf.org>; Wed, 31 Dec 2003 06:25:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbeTG-0004Sb-CG; Wed, 31 Dec 2003 06:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbeSz-0004RZ-If
	for pana@optimus.ietf.org; Wed, 31 Dec 2003 06:24:45 -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 GAA09490
	for <pana@ietf.org>; Wed, 31 Dec 2003 06:24:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbeSv-0001YZ-00
	for pana@ietf.org; Wed, 31 Dec 2003 06:24:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbeR3-0001W3-00
	for pana@ietf.org; Wed, 31 Dec 2003 06:22:46 -0500
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbePV-0001Tl-00
	for pana@ietf.org; Wed, 31 Dec 2003 06:21:09 -0500
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 hBVBL6r12878;
	Wed, 31 Dec 2003 12:21:06 +0100 (MET)
Received: from verena (lnxekv1-16.esn.sbs.de [149.246.36.16])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id hBVBL4L01860;
	Wed, 31 Dec 2003 12:21:05 +0100 (MET)
From: "Hannes Tschofenig" <Hannes.Tschofenig@siemens.com>
To: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, <pana@ietf.org>
Subject: RE: [Pana] Unique identifier per session
Date: Wed, 31 Dec 2003 12:27:15 +0100
Message-ID: <000001c3cf91$0b5d3050$320aa8c0@verena>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <005701c3cf08$b43b0280$681067c0@adithya>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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, 

please see my comments inline:

> -----Original Message-----
> From: Mohan Parthasarathy [mailto:mohanp@sbcglobal.net] 
> Sent: Dienstag, 30. Dezember 2003 20:11
> To: Tschofenig Hannes
> Cc: Yoshihiro Ohba; pana@ietf.org
> Subject: Re: [Pana] Unique identifier per session
> 
> 
>   > i tried to raise the same question with my text: is it 
> necessary to update
> > the ike preshared secret with every re-authentication protocol run?
> >
> > we have multiple re-authentication procedures here:
> >
> > - PANA re-authentication
> > - EAP full re-authentication (full run between the eap peer and the
> eap
> > server)
> > - EAP 'fast resume'
> > - EAP run between the eap peer and the local aaa server (based on
> cached
> > keys) (in some cases you could draw a relationship between 'fast
> resume'
> > here.
> >
> > at the discussion in the eap keying design team i was not able to
> figure
> out
> > whether a fast resume actually produces new session keys.
> >
> > i would argue to update the PANA SA if an EAP run produces new keys.
> we
> have
> > to discuss how we can handle rekeying (i.e., where multiple PANA SAs
> are
> > concurrently active) within PANA at least.
> >
> > hence, i would strongly argue against executing a new IKE exchange
> wheneven
> > you do one of these re-authentication steps. that would 
> certainly hit 
> > performance and is not necessary and even the entrophy argument does
> not
> > hold here since you can always create new IPsec SAs based on a quick
> mode
> > exchange.
> >
> Agreed.
> 
> > a few comments on the ability to have multiple IKE 
> pre-shared secrets 
> > currently for IKE protocol runs:
> >
> > ike does not support this type of scenario easily. as stated in
> [ipsec-pana]
> > in aggressive mode you could use the ID_KEY_ID with the 
> (session id || 
> > version number) as a key name. this would ensure that you always
> select
> the
> 
> What do you mean by version number ?

if you have multiple IKE pre-shared secrets concurrently then you need to
have a way to distinguish a more recent key from an older one.
additionally you need to indicate this somehow. when entity A selects 
key X then entity B needs to know that X was selected. 

the key version number could be an integer which is increased by one if you
add a new version of the key.

> 
> > most recent key and in case of failures it would be possible to
> fallback
> to
> > the previous sa. however, this does not work with ike main mode
> (pre-shared
> > secret authentication) since the ID payload is sent after
> authentication
> > (with message 5). this already caused problems in road 
> warrior cases.
> >
> > from this point of view it would be good to use aggressive mode only
> (also
> > from the number of messages). however, the availability of 
> aggressive
> mode
> > in existing implementations is not widespread.
> >
> My next update (soon to be out) already clarifies that only 
> aggressive mode  MUST be supported because of the problem you 
> mention above with main-mode.

great.

ciao
hannes

> 
> -mohan
> 
> > ciao
> > hannes
> >
> >
> > > -----Original Message-----
> > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: Dienstag, 30. Dezember 2003 08:24
> > > To: Mohan Parthasarathy
> > > Cc: Yoshihiro Ohba; pana@ietf.org
> > > Subject: Re: [Pana] Unique identifier per session
> > >
> > >
> > > Hi Mohan,
> > >
> > > On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan 
> Parthasarathy wrote:
> > > >
> > > > > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan
> > > Parthasarathy wrote:
> > > > > > Hello,
> > > > > >
> > > > > > PANA session ID uniquely identifies a session. But, it also
> does
> > > not
> > > > change
> > > > > > across a reauthentication.
> > > > > > The PANA-IPsec draft needs something unique to identify the
> > > pre-shared
> > > > keys
> > > > > > within a sub-session.
> > > > > > Two possibilities.
> > > > > >
> > > > > > 1) During re-authentication, change the session ID also in
> > > > reauth-answer.
> > > > > > 2) Invent another ID that changes with every reauth 
> and hence
> > > uniquely
> > > > > > identifies the keys derived
> > > > > >     during a reauth.
> > > > >
> > > > > I think it does not make sense to change the PANA
> > > Session-ID across
> > > > > (re-)authentications just for this purpose.
> > > > >
> > > > > How about using <PANA Session-Id> | <N> as the IKE pre-shared
> key
> > > > > identifier, where N is the number of EAP-based
> re-authentications
> > > > > occured for the Session-ID?
> > > > >
> > > >  Can N go out of sync between the PAA and PaC ?
> > > > I am assuming that "N" is implicitly and independently
> > > arrived by PaC
> > > and
> > > > PAA.
> > > >
> > > > 1) PAA sends a reauth request
> > > > 2) PaC sends a reauth answer and increments N by 1. This message
> is
> > > lost.
> > > > 3) PAA retransmits reauth request
> > > > 4) PaC sends a reauth answer and increments N by 1. This message
> is
> > > > successful.
> > > > 5) PAA increments N by 1.
> > >
> > > Which type of "reauth" do you mean?  I am assuming that the IKE 
> > > pre-shared key is updated when an EAP-based re-authentication 
> > > occurs. When the other type of reauthentication based on 
> > > PANA-Reauth-Request/Answer exchange occurs, I don't think the IKE 
> > > pre-shared key needs to be updated because there is no 
> change in the 
> > > EAP Master Session Key in this case.  For EAP-based 
> > > re-authentication, synchronization on EAP Master Session Key 
> > > derivation can be made because PANA-Bind-Request that carries an 
> > > EAP-Success message is acknowledged with PANA-Bind-Answer message.
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > >
> > > >
> > > > As you can see, N is out of sync. Is the above possible ?
> > > From what i
> > > can
> > > > understand
> > > > about retransmissions (section 4.1.4 of PANA protocol), 
> the above
> > > looks
> > > > possible.
> > > >
> > > >
> > > > -mohan
> > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > >
> > > > > >
> > > > > > Any other possibilities ?
> > > > > >
> > > > > > -mohan
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Pana mailing 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 Dec 31 06:29:08 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09605
	for <pana-archive@odin.ietf.org>; Wed, 31 Dec 2003 06:29:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbeWm-0004Yh-HI
	for pana-archive@odin.ietf.org; Wed, 31 Dec 2003 06:28:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBVBSe2u017522
	for pana-archive@odin.ietf.org; Wed, 31 Dec 2003 06:28:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbeWm-0004YX-CD
	for pana-web-archive@optimus.ietf.org; Wed, 31 Dec 2003 06:28:40 -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 GAA09588
	for <pana-web-archive@ietf.org>; Wed, 31 Dec 2003 06:28:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbeWi-0001dE-00
	for pana-web-archive@ietf.org; Wed, 31 Dec 2003 06:28:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbeUt-0001bt-00
	for pana-web-archive@ietf.org; Wed, 31 Dec 2003 06:26:44 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbeTG-0001Zx-00
	for pana-web-archive@ietf.org; Wed, 31 Dec 2003 06:25:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbeTG-0004Sb-CG; Wed, 31 Dec 2003 06:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbeSz-0004RZ-If
	for pana@optimus.ietf.org; Wed, 31 Dec 2003 06:24:45 -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 GAA09490
	for <pana@ietf.org>; Wed, 31 Dec 2003 06:24:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbeSv-0001YZ-00
	for pana@ietf.org; Wed, 31 Dec 2003 06:24:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbeR3-0001W3-00
	for pana@ietf.org; Wed, 31 Dec 2003 06:22:46 -0500
Received: from david.siemens.de ([192.35.17.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbePV-0001Tl-00
	for pana@ietf.org; Wed, 31 Dec 2003 06:21:09 -0500
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 hBVBL6r12878;
	Wed, 31 Dec 2003 12:21:06 +0100 (MET)
Received: from verena (lnxekv1-16.esn.sbs.de [149.246.36.16])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id hBVBL4L01860;
	Wed, 31 Dec 2003 12:21:05 +0100 (MET)
From: "Hannes Tschofenig" <Hannes.Tschofenig@siemens.com>
To: "'Mohan Parthasarathy'" <mohanp@sbcglobal.net>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, <pana@ietf.org>
Subject: RE: [Pana] Unique identifier per session
Date: Wed, 31 Dec 2003 12:27:15 +0100
Message-ID: <000001c3cf91$0b5d3050$320aa8c0@verena>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <005701c3cf08$b43b0280$681067c0@adithya>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi mohan, 

please see my comments inline:

> -----Original Message-----
> From: Mohan Parthasarathy [mailto:mohanp@sbcglobal.net] 
> Sent: Dienstag, 30. Dezember 2003 20:11
> To: Tschofenig Hannes
> Cc: Yoshihiro Ohba; pana@ietf.org
> Subject: Re: [Pana] Unique identifier per session
> 
> 
>   > i tried to raise the same question with my text: is it 
> necessary to update
> > the ike preshared secret with every re-authentication protocol run?
> >
> > we have multiple re-authentication procedures here:
> >
> > - PANA re-authentication
> > - EAP full re-authentication (full run between the eap peer and the
> eap
> > server)
> > - EAP 'fast resume'
> > - EAP run between the eap peer and the local aaa server (based on
> cached
> > keys) (in some cases you could draw a relationship between 'fast
> resume'
> > here.
> >
> > at the discussion in the eap keying design team i was not able to
> figure
> out
> > whether a fast resume actually produces new session keys.
> >
> > i would argue to update the PANA SA if an EAP run produces new keys.
> we
> have
> > to discuss how we can handle rekeying (i.e., where multiple PANA SAs
> are
> > concurrently active) within PANA at least.
> >
> > hence, i would strongly argue against executing a new IKE exchange
> wheneven
> > you do one of these re-authentication steps. that would 
> certainly hit 
> > performance and is not necessary and even the entrophy argument does
> not
> > hold here since you can always create new IPsec SAs based on a quick
> mode
> > exchange.
> >
> Agreed.
> 
> > a few comments on the ability to have multiple IKE 
> pre-shared secrets 
> > currently for IKE protocol runs:
> >
> > ike does not support this type of scenario easily. as stated in
> [ipsec-pana]
> > in aggressive mode you could use the ID_KEY_ID with the 
> (session id || 
> > version number) as a key name. this would ensure that you always
> select
> the
> 
> What do you mean by version number ?

if you have multiple IKE pre-shared secrets concurrently then you need to
have a way to distinguish a more recent key from an older one.
additionally you need to indicate this somehow. when entity A selects 
key X then entity B needs to know that X was selected. 

the key version number could be an integer which is increased by one if you
add a new version of the key.

> 
> > most recent key and in case of failures it would be possible to
> fallback
> to
> > the previous sa. however, this does not work with ike main mode
> (pre-shared
> > secret authentication) since the ID payload is sent after
> authentication
> > (with message 5). this already caused problems in road 
> warrior cases.
> >
> > from this point of view it would be good to use aggressive mode only
> (also
> > from the number of messages). however, the availability of 
> aggressive
> mode
> > in existing implementations is not widespread.
> >
> My next update (soon to be out) already clarifies that only 
> aggressive mode  MUST be supported because of the problem you 
> mention above with main-mode.

great.

ciao
hannes

> 
> -mohan
> 
> > ciao
> > hannes
> >
> >
> > > -----Original Message-----
> > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > Sent: Dienstag, 30. Dezember 2003 08:24
> > > To: Mohan Parthasarathy
> > > Cc: Yoshihiro Ohba; pana@ietf.org
> > > Subject: Re: [Pana] Unique identifier per session
> > >
> > >
> > > Hi Mohan,
> > >
> > > On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan 
> Parthasarathy wrote:
> > > >
> > > > > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan
> > > Parthasarathy wrote:
> > > > > > Hello,
> > > > > >
> > > > > > PANA session ID uniquely identifies a session. But, it also
> does
> > > not
> > > > change
> > > > > > across a reauthentication.
> > > > > > The PANA-IPsec draft needs something unique to identify the
> > > pre-shared
> > > > keys
> > > > > > within a sub-session.
> > > > > > Two possibilities.
> > > > > >
> > > > > > 1) During re-authentication, change the session ID also in
> > > > reauth-answer.
> > > > > > 2) Invent another ID that changes with every reauth 
> and hence
> > > uniquely
> > > > > > identifies the keys derived
> > > > > >     during a reauth.
> > > > >
> > > > > I think it does not make sense to change the PANA
> > > Session-ID across
> > > > > (re-)authentications just for this purpose.
> > > > >
> > > > > How about using <PANA Session-Id> | <N> as the IKE pre-shared
> key
> > > > > identifier, where N is the number of EAP-based
> re-authentications
> > > > > occured for the Session-ID?
> > > > >
> > > >  Can N go out of sync between the PAA and PaC ?
> > > > I am assuming that "N" is implicitly and independently
> > > arrived by PaC
> > > and
> > > > PAA.
> > > >
> > > > 1) PAA sends a reauth request
> > > > 2) PaC sends a reauth answer and increments N by 1. This message
> is
> > > lost.
> > > > 3) PAA retransmits reauth request
> > > > 4) PaC sends a reauth answer and increments N by 1. This message
> is
> > > > successful.
> > > > 5) PAA increments N by 1.
> > >
> > > Which type of "reauth" do you mean?  I am assuming that the IKE 
> > > pre-shared key is updated when an EAP-based re-authentication 
> > > occurs. When the other type of reauthentication based on 
> > > PANA-Reauth-Request/Answer exchange occurs, I don't think the IKE 
> > > pre-shared key needs to be updated because there is no 
> change in the 
> > > EAP Master Session Key in this case.  For EAP-based 
> > > re-authentication, synchronization on EAP Master Session Key 
> > > derivation can be made because PANA-Bind-Request that carries an 
> > > EAP-Success message is acknowledged with PANA-Bind-Answer message.
> > >
> > > Yoshihiro Ohba
> > >
> > >
> > >
> > > >
> > > > As you can see, N is out of sync. Is the above possible ?
> > > From what i
> > > can
> > > > understand
> > > > about retransmissions (section 4.1.4 of PANA protocol), 
> the above
> > > looks
> > > > possible.
> > > >
> > > >
> > > > -mohan
> > > >
> > > > > Yoshihiro Ohba
> > > > >
> > > > >
> > > > > >
> > > > > > Any other possibilities ?
> > > > > >
> > > > > > -mohan
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Pana mailing 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 Dec 31 12:38:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18990
	for <pana-archive@lists.ietf.org>; Wed, 31 Dec 2003 12:38:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbkID-0006KQ-HB; Wed, 31 Dec 2003 12:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbkHG-00063H-T3
	for pana@optimus.ietf.org; Wed, 31 Dec 2003 12:37: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 MAA18975
	for <pana@ietf.org>; Wed, 31 Dec 2003 12:36:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbkHF-0005kx-00
	for pana@ietf.org; Wed, 31 Dec 2003 12:37:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbkFQ-0005ej-00
	for pana@ietf.org; Wed, 31 Dec 2003 12:35:09 -0500
Received: from smtp803.mail.sc5.yahoo.com ([66.163.168.182])
	by ietf-mx with smtp (Exim 4.12)
	id 1AbkDc-0005XY-00
	for pana@ietf.org; Wed, 31 Dec 2003 12:33:16 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login)
  by smtp803.mail.sc5.yahoo.com with SMTP; 31 Dec 2003 17:33:11 -0000
Message-ID: <002f01c3cfc4$2cdee290$681067c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Hannes Tschofenig" <Hannes.Tschofenig@siemens.com>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <000001c3cf91$0b5d3050$320aa8c0@verena>
Subject: Re: [Pana] Unique identifier per session
Date: Wed, 31 Dec 2003 09:33:16 -0800
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
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: pana-admin@ietf.org
Errors-To: pana-admin@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>,
	<mailto:pana-request@ietf.org?subject=unsubscribe>
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Post: <mailto:pana@ietf.org>
List-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

 > >
> > > a few comments on the ability to have multiple IKE
> > pre-shared secrets
> > > currently for IKE protocol runs:
> > >
> > > ike does not support this type of scenario easily. as stated in
> > [ipsec-pana]
> > > in aggressive mode you could use the ID_KEY_ID with the
> > (session id ||
> > > version number) as a key name. this would ensure that you always
> > select
> > the
> >
> > What do you mean by version number ?
>
> if you have multiple IKE pre-shared secrets concurrently then you need to
> have a way to distinguish a more recent key from an older one.
> additionally you need to indicate this somehow. when entity A selects
> key X then entity B needs to know that X was selected.
>
> the key version number could be an integer which is increased by one if
you
> add a new version of the key.
>
How do you propose to exchange this information between PAA and PaC ?
See the other discussion between me and Yoshihiro. Explicit communication
seems better. I think this should be another AVP. What do you think ?

-mohan

> >
> > > most recent key and in case of failures it would be possible to
> > fallback
> > to
> > > the previous sa. however, this does not work with ike main mode
> > (pre-shared
> > > secret authentication) since the ID payload is sent after
> > authentication
> > > (with message 5). this already caused problems in road
> > warrior cases.
> > >
> > > from this point of view it would be good to use aggressive mode only
> > (also
> > > from the number of messages). however, the availability of
> > aggressive
> > mode
> > > in existing implementations is not widespread.
> > >
> > My next update (soon to be out) already clarifies that only
> > aggressive mode  MUST be supported because of the problem you
> > mention above with main-mode.
>
> great.
>
> ciao
> hannes
>
> >
> > -mohan
> >
> > > ciao
> > > hannes
> > >
> > >
> > > > -----Original Message-----
> > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: Dienstag, 30. Dezember 2003 08:24
> > > > To: Mohan Parthasarathy
> > > > Cc: Yoshihiro Ohba; pana@ietf.org
> > > > Subject: Re: [Pana] Unique identifier per session
> > > >
> > > >
> > > > Hi Mohan,
> > > >
> > > > On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan
> > Parthasarathy wrote:
> > > > >
> > > > > > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan
> > > > Parthasarathy wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > PANA session ID uniquely identifies a session. But, it also
> > does
> > > > not
> > > > > change
> > > > > > > across a reauthentication.
> > > > > > > The PANA-IPsec draft needs something unique to identify the
> > > > pre-shared
> > > > > keys
> > > > > > > within a sub-session.
> > > > > > > Two possibilities.
> > > > > > >
> > > > > > > 1) During re-authentication, change the session ID also in
> > > > > reauth-answer.
> > > > > > > 2) Invent another ID that changes with every reauth
> > and hence
> > > > uniquely
> > > > > > > identifies the keys derived
> > > > > > >     during a reauth.
> > > > > >
> > > > > > I think it does not make sense to change the PANA
> > > > Session-ID across
> > > > > > (re-)authentications just for this purpose.
> > > > > >
> > > > > > How about using <PANA Session-Id> | <N> as the IKE pre-shared
> > key
> > > > > > identifier, where N is the number of EAP-based
> > re-authentications
> > > > > > occured for the Session-ID?
> > > > > >
> > > > >  Can N go out of sync between the PAA and PaC ?
> > > > > I am assuming that "N" is implicitly and independently
> > > > arrived by PaC
> > > > and
> > > > > PAA.
> > > > >
> > > > > 1) PAA sends a reauth request
> > > > > 2) PaC sends a reauth answer and increments N by 1. This message
> > is
> > > > lost.
> > > > > 3) PAA retransmits reauth request
> > > > > 4) PaC sends a reauth answer and increments N by 1. This message
> > is
> > > > > successful.
> > > > > 5) PAA increments N by 1.
> > > >
> > > > Which type of "reauth" do you mean?  I am assuming that the IKE
> > > > pre-shared key is updated when an EAP-based re-authentication
> > > > occurs. When the other type of reauthentication based on
> > > > PANA-Reauth-Request/Answer exchange occurs, I don't think the IKE
> > > > pre-shared key needs to be updated because there is no
> > change in the
> > > > EAP Master Session Key in this case.  For EAP-based
> > > > re-authentication, synchronization on EAP Master Session Key
> > > > derivation can be made because PANA-Bind-Request that carries an
> > > > EAP-Success message is acknowledged with PANA-Bind-Answer message.
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > >
> > > > >
> > > > > As you can see, N is out of sync. Is the above possible ?
> > > > From what i
> > > > can
> > > > > understand
> > > > > about retransmissions (section 4.1.4 of PANA protocol),
> > the above
> > > > looks
> > > > > possible.
> > > > >
> > > > >
> > > > > -mohan
> > > > >
> > > > > > Yoshihiro Ohba
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Any other possibilities ?
> > > > > > >
> > > > > > > -mohan
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Pana mailing 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 Dec 31 12:41:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19091
	for <pana-archive@odin.ietf.org>; Wed, 31 Dec 2003 12:41:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbkKw-0006R5-GT
	for pana-archive@odin.ietf.org; Wed, 31 Dec 2003 12:40:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBVHeore024735
	for pana-archive@odin.ietf.org; Wed, 31 Dec 2003 12:40:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbkKw-0006Qs-7l
	for pana-web-archive@optimus.ietf.org; Wed, 31 Dec 2003 12:40:50 -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 MAA19081
	for <pana-web-archive@ietf.org>; Wed, 31 Dec 2003 12:40:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbkKu-0005tM-00
	for pana-web-archive@ietf.org; Wed, 31 Dec 2003 12:40:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbkJ5-0005rD-00
	for pana-web-archive@ietf.org; Wed, 31 Dec 2003 12:38:56 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbkIE-0005nX-00
	for pana-web-archive@ietf.org; Wed, 31 Dec 2003 12:38:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbkID-0006KQ-HB; Wed, 31 Dec 2003 12:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AbkHG-00063H-T3
	for pana@optimus.ietf.org; Wed, 31 Dec 2003 12:37: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 MAA18975
	for <pana@ietf.org>; Wed, 31 Dec 2003 12:36:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AbkHF-0005kx-00
	for pana@ietf.org; Wed, 31 Dec 2003 12:37:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AbkFQ-0005ej-00
	for pana@ietf.org; Wed, 31 Dec 2003 12:35:09 -0500
Received: from smtp803.mail.sc5.yahoo.com ([66.163.168.182])
	by ietf-mx with smtp (Exim 4.12)
	id 1AbkDc-0005XY-00
	for pana@ietf.org; Wed, 31 Dec 2003 12:33:16 -0500
Received: from unknown (HELO adithya) (mohanp@sbcglobal.net@192.103.16.104 with login)
  by smtp803.mail.sc5.yahoo.com with SMTP; 31 Dec 2003 17:33:11 -0000
Message-ID: <002f01c3cfc4$2cdee290$681067c0@adithya>
From: "Mohan Parthasarathy" <mohanp@sbcglobal.net>
To: "Hannes Tschofenig" <Hannes.Tschofenig@siemens.com>
Cc: "'Yoshihiro Ohba'" <yohba@tari.toshiba.com>, <pana@ietf.org>
References: <000001c3cf91$0b5d3050$320aa8c0@verena>
Subject: Re: [Pana] Unique identifier per session
Date: Wed, 31 Dec 2003 09:33:16 -0800
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 > >
> > > a few comments on the ability to have multiple IKE
> > pre-shared secrets
> > > currently for IKE protocol runs:
> > >
> > > ike does not support this type of scenario easily. as stated in
> > [ipsec-pana]
> > > in aggressive mode you could use the ID_KEY_ID with the
> > (session id ||
> > > version number) as a key name. this would ensure that you always
> > select
> > the
> >
> > What do you mean by version number ?
>
> if you have multiple IKE pre-shared secrets concurrently then you need to
> have a way to distinguish a more recent key from an older one.
> additionally you need to indicate this somehow. when entity A selects
> key X then entity B needs to know that X was selected.
>
> the key version number could be an integer which is increased by one if
you
> add a new version of the key.
>
How do you propose to exchange this information between PAA and PaC ?
See the other discussion between me and Yoshihiro. Explicit communication
seems better. I think this should be another AVP. What do you think ?

-mohan

> >
> > > most recent key and in case of failures it would be possible to
> > fallback
> > to
> > > the previous sa. however, this does not work with ike main mode
> > (pre-shared
> > > secret authentication) since the ID payload is sent after
> > authentication
> > > (with message 5). this already caused problems in road
> > warrior cases.
> > >
> > > from this point of view it would be good to use aggressive mode only
> > (also
> > > from the number of messages). however, the availability of
> > aggressive
> > mode
> > > in existing implementations is not widespread.
> > >
> > My next update (soon to be out) already clarifies that only
> > aggressive mode  MUST be supported because of the problem you
> > mention above with main-mode.
>
> great.
>
> ciao
> hannes
>
> >
> > -mohan
> >
> > > ciao
> > > hannes
> > >
> > >
> > > > -----Original Message-----
> > > > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]
> > > > Sent: Dienstag, 30. Dezember 2003 08:24
> > > > To: Mohan Parthasarathy
> > > > Cc: Yoshihiro Ohba; pana@ietf.org
> > > > Subject: Re: [Pana] Unique identifier per session
> > > >
> > > >
> > > > Hi Mohan,
> > > >
> > > > On Thu, Dec 18, 2003 at 03:00:28PM -0800, Mohan
> > Parthasarathy wrote:
> > > > >
> > > > > > On Wed, Dec 17, 2003 at 09:02:09PM -0800, Mohan
> > > > Parthasarathy wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > PANA session ID uniquely identifies a session. But, it also
> > does
> > > > not
> > > > > change
> > > > > > > across a reauthentication.
> > > > > > > The PANA-IPsec draft needs something unique to identify the
> > > > pre-shared
> > > > > keys
> > > > > > > within a sub-session.
> > > > > > > Two possibilities.
> > > > > > >
> > > > > > > 1) During re-authentication, change the session ID also in
> > > > > reauth-answer.
> > > > > > > 2) Invent another ID that changes with every reauth
> > and hence
> > > > uniquely
> > > > > > > identifies the keys derived
> > > > > > >     during a reauth.
> > > > > >
> > > > > > I think it does not make sense to change the PANA
> > > > Session-ID across
> > > > > > (re-)authentications just for this purpose.
> > > > > >
> > > > > > How about using <PANA Session-Id> | <N> as the IKE pre-shared
> > key
> > > > > > identifier, where N is the number of EAP-based
> > re-authentications
> > > > > > occured for the Session-ID?
> > > > > >
> > > > >  Can N go out of sync between the PAA and PaC ?
> > > > > I am assuming that "N" is implicitly and independently
> > > > arrived by PaC
> > > > and
> > > > > PAA.
> > > > >
> > > > > 1) PAA sends a reauth request
> > > > > 2) PaC sends a reauth answer and increments N by 1. This message
> > is
> > > > lost.
> > > > > 3) PAA retransmits reauth request
> > > > > 4) PaC sends a reauth answer and increments N by 1. This message
> > is
> > > > > successful.
> > > > > 5) PAA increments N by 1.
> > > >
> > > > Which type of "reauth" do you mean?  I am assuming that the IKE
> > > > pre-shared key is updated when an EAP-based re-authentication
> > > > occurs. When the other type of reauthentication based on
> > > > PANA-Reauth-Request/Answer exchange occurs, I don't think the IKE
> > > > pre-shared key needs to be updated because there is no
> > change in the
> > > > EAP Master Session Key in this case.  For EAP-based
> > > > re-authentication, synchronization on EAP Master Session Key
> > > > derivation can be made because PANA-Bind-Request that carries an
> > > > EAP-Success message is acknowledged with PANA-Bind-Answer message.
> > > >
> > > > Yoshihiro Ohba
> > > >
> > > >
> > > >
> > > > >
> > > > > As you can see, N is out of sync. Is the above possible ?
> > > > From what i
> > > > can
> > > > > understand
> > > > > about retransmissions (section 4.1.4 of PANA protocol),
> > the above
> > > > looks
> > > > > possible.
> > > > >
> > > > >
> > > > > -mohan
> > > > >
> > > > > > Yoshihiro Ohba
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > Any other possibilities ?
> > > > > > >
> > > > > > > -mohan
> > > > > > >
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > Pana mailing 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



