Re: [Pana] and network selection
Yoshihiro Ohba <yohba@tari.toshiba.com> Tue, 09 November 2004 15:36 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 KAA10297 for <pana-archive@lists.ietf.org>; Tue, 9 Nov 2004 10:36:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRXp6-0007JX-9Y; Tue, 09 Nov 2004 10:22:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRXfu-0003jP-77 for pana@megatron.ietf.org; Tue, 09 Nov 2004 10:12:50 -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 KAA06800 for <pana@ietf.org>; Tue, 9 Nov 2004 10:12:48 -0500 (EST)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRXgf-00063A-8o for pana@ietf.org; Tue, 09 Nov 2004 10:13:38 -0500
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134]) by inet-tsb.toshiba.co.jp with ESMTP id iA9FCiUD001162; Wed, 10 Nov 2004 00:12:44 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp id iA9FCifS024061; Wed, 10 Nov 2004 00:12:44 +0900 (JST)
Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id AAA24057 ; Wed, 10 Nov 2004 00:12:44 +0900
Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp id AAA03530; Wed, 10 Nov 2004 00:12:43 +0900 (JST)
Received: from tsb-sgw2.toshiba.co.jp by toshiba.co.jp id iA9FChVG027015; Wed, 10 Nov 2004 00:12:43 +0900 (JST)
Received: from tsbpo1.po.toshiba.co.jp by tsb-sgw2.toshiba.co.jp with ESMTP id iA9FChuY022261; Wed, 10 Nov 2004 00:12:43 +0900 (JST)
Received: from steelhead (iVPN01-103.mobile.toshiba.co.jp) by tsbpo1.po.toshiba.co.jp (Sun Internet Mail Server sims.3.5.1999.01.13.19.49.p4) with ESMTP id <0I6X00IVR3L4C2@tsbpo1.po.toshiba.co.jp>; Wed, 10 Nov 2004 00:12:42 +0900 (JST)
Received: from ohba by steelhead with local (Exim 3.36 #1 (Debian)) id 1CRXX4-0001rs-00; Tue, 09 Nov 2004 07:03:42 -0800
Date: Tue, 09 Nov 2004 10:03:42 -0500
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Pana] and network selection
In-reply-to: <F17FB067A86B2D488382C923C532EAA7024A4D83@exch01.bridgewatersys.com>
To: Avi Lior <avi@bridgewatersystems.com>
Message-id: <20041109150341.GK2826@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset="iso-2022-jp"
Content-disposition: inline
Mail-Followup-To: Avi Lior <avi@bridgewatersystems.com>, "'jari.arkko@piuha.net'" <jari.arkko@piuha.net>, Alper Yegin <alper.yegin@samsung.com>, 'Yoshihiro Ohba' <yohba@tari.toshiba.com>, pana@ietf.org
User-Agent: Mutt/1.5.6+20040907i
References: <F17FB067A86B2D488382C923C532EAA7024A4D83@exch01.bridgewatersys.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: Alper Yegin <alper.yegin@samsung.com>, 'Yoshihiro Ohba' <yohba@tari.toshiba.com>, "'jari.arkko@piuha.net'" <jari.arkko@piuha.net>, 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
On Mon, Nov 08, 2004 at 05:06:16PM -0500, Avi Lior wrote: > One more thing to add to Jarri's comments: > > One method maybe better than the other but both method can be used at the > same time right? What can go wrong. What if they conflict. I've read draft-adrangi-eap-network-discovery and I agree that they can conflict if EAP-based network selection is used for ISP selection instead of AAA intermediary selection. > > Or do we say if one is used the other shouldn't be used. I think so. It is the responsibility of implementation to avoid such conflict. Yoshihiro Ohba > > > > > -----Original Message----- > > From: Jari Arkko [mailto:jari.arkko@piuha.net] > > Sent: Monday, November 08, 2004 4:56 PM > > To: Alper Yegin > > Cc: 'Avi Lior'; 'Yoshihiro Ohba'; pana@ietf.org > > Subject: Re: [Pana] and network selection > > > > > > Alper Yegin wrote: > > > > > PANA allows ISP discovery as early as PANA-Start-Request. > > Depending on > > > the deployment this message may be sent unsolicited, but it is > > > unicast. > > > > > > I agree that the enabling discovery as early as possible (at the > > > lowest possible layer) is more optimal. When that's not possible > > > (e.g., lack of supporting technology) you need to keep popping up > > > layers to accomplish that. If using PANA, then you are > > done. If not, > > > then you can fall back to EAP-based discovery. > > > > Yes. Two things remain, however: > > > > (1) Does someone have an answer as to how all this can be > > accomplished in the current AAA protocols while > > still allowing the local access provider to have > > a proxy AND roaming? I'm not quite sure how the > > destination realm value is set in the case of > > Diameter EAP, for instance. > > > > (2) We need to consider this in light of Avi's question, > > which was what additional value the PANA ISP selection > > provides over things that already exist in EAP. I > > personally do not believe you absolutely need to > > have additional value, but of course it would be > > useful if you could demonstrate, for instance, that > > your "L2" network selection scheme is better than > > what exists in 802.1X. > > > > Speaking of multicast packets, how does a PANA client > > know that it needs to initiate a PANA exchange? What > > if you added a new PANA multicast message that told > > the client about this and carries the ISP/ASP info > > within it? > > > > --Jari > > _______________________________________________ Pana mailing list Pana@ietf.org https://www1.ietf.org/mailman/listinfo/pana
- [Pana] and network selection Avi Lior
- Re: [Pana] and network selection Yoshihiro Ohba
- RE: [Pana] and network selection Avi Lior
- Re: [Pana] and network selection Yoshihiro Ohba
- Re: [Pana] and network selection Jari Arkko
- Re: [Pana] and network selection Yoshihiro Ohba
- Re: [Pana] and network selection Jari Arkko
- RE: [Pana] and network selection Avi Lior
- Re: [Pana] and network selection Jari Arkko
- RE: [Pana] and network selection Alper Yegin
- RE: [Pana] and network selection Alper Yegin
- Re: [Pana] and network selection Jari Arkko
- RE: [Pana] and network selection Avi Lior
- RE: [Pana] and network selection Avi Lior
- Re: [Pana] and network selection Yoshihiro Ohba
- Re: [Pana] and network selection Yoshihiro Ohba
- RE: [Pana] and network selection Alper Yegin
- RE: [Pana] and network selection Avi Lior
- RE: [Pana] and network selection Mohan Parthasarathy
- Re: [Pana] and network selection Jari Arkko
- Re: [Pana] and network selection Jari Arkko
- Re: [Pana] and network selection Yoshihiro Ohba
- Re: [Pana] and network selection Jari Arkko
- Re: [Pana] and network selection Yoshihiro Ohba
- RE: [Pana] and network selection Alper Yegin
- RE: [Pana] and network selection Alper Yegin