Re: [Pana] and network selection

Yoshihiro Ohba <yohba@tari.toshiba.com> Thu, 04 November 2004 20:58 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04145 for <pana-archive@lists.ietf.org>; Thu, 4 Nov 2004 15:58:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPoWp-0004vY-5G; Thu, 04 Nov 2004 15:48:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPoTY-0003UK-J9 for pana@megatron.ietf.org; Thu, 04 Nov 2004 15:44:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03070 for <pana@ietf.org>; Thu, 4 Nov 2004 15:44:55 -0500 (EST)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPoj9-0006Hq-4I for pana@ietf.org; Thu, 04 Nov 2004 16:01:03 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134]) by inet-tsb.toshiba.co.jp with ESMTP id iA4Kijbv017862; Fri, 5 Nov 2004 05:44:45 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp id iA4Kijnf021735; Fri, 5 Nov 2004 05:44:45 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id FAA21734 ; Fri, 5 Nov 2004 05:44:45 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp id FAA18272; Fri, 5 Nov 2004 05:44:44 +0900 (JST)
Received: from tsb-sgw2.toshiba.co.jp by toshiba.co.jp id iA4KiiOo022701; Fri, 5 Nov 2004 05:44:44 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp by tsb-sgw2.toshiba.co.jp with ESMTP id iA4KiiuY011547; Fri, 5 Nov 2004 05:44:44 +0900 (JST)
Received: from steelhead ([172.30.24.114]) by tsbpo1.po.toshiba.co.jp (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4) with ESMTP id <0I6O00KY49MGZL@tsbpo1.po.toshiba.co.jp>; Fri, 5 Nov 2004 05:44:43 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian)) id 1CPDBx-0002Vm-00; Tue, 02 Nov 2004 20:56:17 -0800
Date: Tue, 02 Nov 2004 23:56:17 -0500
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] and network selection
In-reply-to: <F17FB067A86B2D488382C923C532EAA7024A4D5C@exch01.bridgewatersys.com>
To: Avi Lior <avi@bridgewatersystems.com>
Message-id: <20041103045617.GA919@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset="iso-2022-jp"
Content-disposition: inline
Mail-Followup-To: Avi Lior <avi@bridgewatersystems.com>, 'Yoshihiro Ohba' <yohba@tari.toshiba.com>, 'Alper Yegin' <alper.yegin@samsung.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040907i
References: <F17FB067A86B2D488382C923C532EAA7024A4D5C@exch01.bridgewatersys.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Cc: 'Alper Yegin' <alper.yegin@samsung.com>, 'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
Sender: pana-bounces@ietf.org
Errors-To: pana-bounces@ietf.org

Hi Avi,

On Thu, Nov 04, 2004 at 02:06:52PM -0500, Avi Lior wrote:
> Hi Yoshihiro,
> 
> > Network selection based on EAP occurs always after completion 
> > of network selection in PANA in its discovery and handshake 
> > phase (this is guaranteed because section 5.12.1 of 
> > pana-pana-06 explcitly prohibits piggybacking EAP-Request in 
> > PANA-Start-Request messsage). This means that network 
> > selection based on EAP is only performed under the chosen ISP.
> 
> I am a bit confused here.  So let me ask you a few questions:
> 
> What is the purpose of ISP-Information?

It is used by the PaC to choose an ISP.

> How does the PAA know what ISP-Information to provide to the PaC?

It is assumed that the PAA knows which ISPs are available in the
visited network.  The PAA does not have to advertise the list of home
ISPs that are not directly connected to the visited network.

> If the PAA has a relationship with hunderds of ISPs does it send all the
> ISPs?

Yes.  But I assume that only the list of ISPs in the visited network
is advertised (not the home ISPs with which the visited network ISPs
have relationship), and I don't think there are hundreds of ISPs in
the visited network in most cases.

> How does the PaC select which ISP?

This is up to implementation.

> 
> Note: the visited network may not have a direct relationship with the home
> network 

The home ISP network information is not advertised in PANA, assuming
that the subsribers has a knowledge on which ISP in the visited
network has direct/indirect relationship with its home ISP.

> So it will send a list of intermediaries to the PaC.  The PaC may not be
> able to select the intermediaries because it wouldn't necessarily know the
> routing.  It knows its home network for sure but it may not know other
> relationships.

This list of intermediaries are carried in EAP message (note: PANA
itself does not support any intermediaries selection) and this happens
after the PaC chooses an ISP in the visited network through PANA.  So
if you use EAP-based network selection during PANA authentication
phase, you can choose an intermediary in the scope of the chosen ISP.

> 
> When we do EAP based authentication in AAA we use the User-Name the NAI to
> determine how to route the AAA requests to the Home Network.  How is this
> invisioned to work when PANA and AAA work together.

You just specify a correct NAI in an EAP-Request/Identity or an EAP
method-specific identity message during PANA authentication phase.

> 
> When we do the authentication part, the AAA will use the NAI that was
> provided by the device to route the authentication requests.  This may be
> totally different then the ISP selected during the discovery phase.

When the PaC chooses an ISP, it is the responsibility of the PaC to 
specify an NAI in EAP that is routed correctly through the chosen ISP.

> 
> So what is the purpose of doing ISP selection in the discovery phase? 

To provide the PaC a way to choose an ISP without relying on the
NAI-based selection, which requires different identifies for choosing
different ISPs.  Since PANA has ISP selection mechanism, the PaC can
use the same identity ohba@visa.com and still choose an ISP among
multiple ISPs, as long as those ISPs have relationship with visa.com.

Regards,

Yoshihiro Ohba



> 
> 
> > -----Original Message-----
> > From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com] 
> > Sent: Tuesday, November 02, 2004 9:32 PM
> > To: Avi Lior
> > Cc: 'Alper Yegin'; pana@ietf.org
> > Subject: Re: [Pana] and network selection
> > 
> > 
> > Hi Avi,
> > 
> > I think network selection in PANA (that is ISP selection) and 
> > the network selection based on EAP (that is intermediary network
> > selection) does not conflict each other for the following reason:
> > 
> > Network selection based on EAP occurs always after completion 
> > of network selection in PANA in its discovery and handshake 
> > phase (this is guaranteed because section 5.12.1 of 
> > pana-pana-06 explcitly prohibits piggybacking EAP-Request in 
> > PANA-Start-Request messsage). This means that network 
> > selection based on EAP is only performed under the chosen ISP.
> > 
> > I agree that we should clarify somethign like this in the 
> > PANA specification draft.
> > 
> > Regards,
> > 
> > Yoshihiro Ohba
> > 
> > 
> > On Wed, Nov 03, 2004 at 03:22:46PM -0500, Avi Lior wrote:
> > > 
> > > Issues with Network Selection.
> > > 
> > > PANA provides its own network selection and EAP also provides a 
> > > network discover mechanism 
> > > (draft-adrangi-eap-network-discovery-05.txt)
> > > 
> > > These may conflict with each other.  Furthermore, the PAA 
> > may not know 
> > > that the EAP payload contains network discovery material.
> > > 
> > > What happens if both are used?  Is it something that PANA 
> > needs to be 
> > > concerned about? Do we need to say something about this in 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